INPUT INVENTORY COUNT IN SAP MM MODULE

PHYSICAL STOCK CALCULATION IN SAP IS CALLED INVENTORY COUNT IN SAP MM.

Using menu:


Logistics -> Materials Management -> Physical Inventory -> Inventory Count
 
Using tcode: MI04
 
 

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
JFKJKHGK
 

Explore User Exits (Enhancement) For Any Module Of SAP

aHTC Hero Android Phone (Sprint)1) ENTER TCODE SE81 IN COMMAND FIELD. NOW PRESS ENTER.

2) NOW DOUBLE CLICK ON THE SD HIERARCHY , CLICK ON EDIT MENU AND NOW               CLICK     ON  SELECT SUBTREE +/- .

3)  NOW CLICK ON INFORMATION SYATEM OR PRESS SHIFT + F4 .

 

                                                                                       
4) NOW FOLLOW THE PATH 
           Repository Information System ---> Enhancements -----> Customer Exits ---->                                            (Double Click) enhancement .

5) NOW YOU CAN SEE THE COMPLETE LIST OF EXITS AND ITS DESCRIPTION ,IN THE SCREEN.

TCODES FOR EXCISE , TAX AND REGISTERS ( CIN and CENVAT )

Transaction codes for Tax and Excise Registers  (CIN & CENVAT)

J1I2 - Prepare a sales tax register


J1I3 - Create outgoing excise invoices in batches

J1I5 - Update the RG 1 and Part I registers

J1IEX - Incoming Excise Invoices (central transaction)

J1IEX_C - Capture an incoming excise invoice (excise clerk)

J1IEX_P - Post an incoming excise invoice (excise supervisor)

J1IF01 - Create a subcontracting challana

J1IF11 - Change a subcontracting challan

J1IF12 - Display a subcontracting challan

J1IF13 - Complete, reverse, or recredit a subcontracting challan

J1IFQ - Reconcile quantities for subcontracting challans

J1IFR - List subcontracting challans

J1IH - Make a CENVAT adjustment posting

J1IIN - Create an outgoing excise invoice

J1IJ - Assign excise invoices to a delivery for sales from depots

J1INJV - Adjust withholding tax Item

J1INREP - Reprint a withholding tax certificate for a vendor

J1IQ - Year-End Income Tax Depreciation Report

J1IR - Download register data

J1IS - Process an excise invoice (outgoing) for other movements

J1IU - Process exemption forms

J1IW - Verify and post an incoming excise invoice

J1IX - Create an incoming excise invoice (without reference to purchase order)

J2I8 - Transfer excise duty to CENVAT account

J2IU - Remit excise duty fortnightly

J2I9 - Monthly CENVAT return

J1IG - Excise invoice entry at depot

J1IGA - Create additional excise entry at depot

J2I5 - Extract data for excise registers

J2I6 - Print excise registers

CREATE APPEND STRUCTURE IN ABAP DATA DICTIONARY

APPEND STRUCTRURES :


             APPEND STRUCTURES ARE USED ONLY TO ENHANCE STANDARD TABLES.  STANDARD TABLES MAY HAVE INCLUDE STRUCTURES ALREADY CREATED , BUT IF WE WANT TO ADD SOME MORE FIELDS TO THE STANDARD TABLES, WE NEED TO GO FOR APPEND STRUCTURES.

            APPEND STRUCTURES SHOULD BE ADDED AT THE END OF A STANDARD TABLE. THIS IS A MUST. BECAUSE WE SHOULD NOT CHANGE THE ORIGINAL STANDARD TABLE IN THE MIDDLE.

• ONE THING YOU SHOULD KEEP IN MIND THAT IT MUST BE CREATED IN CUSTOMER NAMESPACE.
• AND THE OTHETHING IS THAT NAME OF APPEND STRUCTURE MUST BE STARTS WITH  ZZ OR YY 
• Let's starts with  BKPF (Account Document Header) Table .

1) On EASY ACCESS Screen use TCODE SE11 .  Now display the table BKPF . And click on append   structure.

2)  Now click on Create Append .

3) Now Give append name startting with ZZ or YY and press enter.

4) Now define field and components for build the append structure .
now save and activate it.

LSMW - Legacy System Migration Workbench

                      The Legacy system migration workbench ( LSMW ) is an R/3-based tool that supports single or periodic data transfer from your non-SAP system to R/3 .It is a component of the R/3 System and, therefore, is independent from the platform.

                      The data is loaded via the standard interfaces of the applications.This will include all checks that are run for online transactions. Invalid data will be rejected.

Core Functions of LSMW


Importing legacy data from PC spreadsheet tables or sequential files.
Converting data from its original ( legacy system ) format to the target (R\3) format.
Importing the data using standard interfaces of R\3 ( IDOC inbound processing , batch input , direct input )

Which data can be migrated using LSMW ?

• By means of standard transfer programs: a wide range of master data (e.g G/L accounts , customer master , vendor master , material master) and transaction data (e.g financial documents , sales order )
•     By means of recording of transactions: further data objects (if the transaction can be run in batch input mode)
  
  

    
The main advantages of the LSMW:

• Part of R/3 and thus independent of individual platforms
• A variety of technical possibilities of data conversion:
• Data consistency due to standard import techniques:

                 
                          Batch input
                     
                         Direct input

                         BAPIs (Business Application Programming Interfaces)

                         IDocs (Intermediate Documents)

• Generation of the conversion program on the basis of defined rules
• Clear interactive process guide
• Interface for data in spreadsheet format
• Creation of data migration objects on the basis of recorded transactions
• Charge-free for SAP customers and SAP partners

Prior to using LSMW, it is recommended to perform some


conceptual tasks.


Process Flow:
 
 

The following should be taken into account:

• 
  
  Make sure that the R/3 Customizing has been completed.

• Analyze the data that exists in your legacy system (LS) and which of it (from a business point of view) will be required in the future as well.
•  Identify the transaction(s) in the R/3 System that you want to use to transfer the data to this system.
• Process the respective transaction in R/3 manually using test data of the
• legacy system and note which fields must be filled. Maybe there are required fields that do not correspond to a data field in the legacy system. In this case, assigning a fixed value or constant or setting up a field as an optional field perhaps is useful for the data transfer .
• Carry out mapping on paper, that is, allocate the source fields and R/3 fields to each other. You can do this by using the object overview after you defined the object.
• Determine the conversion rule according to which the field contents of the source fields are to be converted into R/3 fields.
• Define the way in which the data is to be extracted from the non-SAP system. (The LSMW does not extract any data itself) .
• Which format does the legacy data have? Decide which standard import technique you want to use, or if you should define an extra "object class” by means of recording.
• In case only a part of your legacy system is to be replaced with the R/3 System, you have to determine the functions that are to be covered by the R/3 System and those to be covered by the legacy system. If necessary,a concept of the data flows and interface architecture has to be created.

Objects of LSMW

• Project
• Sub-project
• Object
• Structure Relationship
• Field - Assignment

 Project

Definition

All the data of an application system that is to be transferred to the SAP R/3 System.

Use

In the LSMW, the project serves as an organizational unit used to combine mapping and field assignments.

Structure

The project consists of:

• Sub project
• Business object (object)
• Structure relationships
• Field assignments

Integration

A project can have any number of sub projects assigned to it.


Sub-Project

Definition


An organizational unit subordinated to the project.

Integration

A sub project can have any number of objects.

Example

Data migration in a company with several plants in which data is organized in different ways. In this case, the complete migration of data would be the project. The sub projects would comprise the data in the individual plants.

Object
 
Definition


                  An object is a unit combined from the business point of view, which is used to transfer the data of a project to the SAP R/3 System.

Structure

An object consists of the following elements:

• Tables involved in the project and in the SAP R/3 System
• Structure(s) for transfer of data
•  Relationship between data at the table and field level
• Field assignments for conversion of data.

Integration

                 An object is assigned to a sub project. For example, customer master,material master, or financial documents are objects.

Structure Relationship

Definition


Structure relationships are mappings between structured trees.

Use

                     The mappings between the trees have to make sense. This means, the structures of the data to be migrated (referred to as "source structures" ) have to be created within the hierarchy in a way that they can be allocated to the structures in the R/3 System (referred to as target structures" ).

Field Assignment :

Definition


                                     A collection of rules that define how the field contents are to be onverted during data migration from the legacy system to the SAP R/3 System.

Use

                                 The field assignments use placeholders and conversion rules in order to ensure both flexibility and consistency of data. In migration customizing, you assign values to the placeholders and select the processing types for the conversion rules.

Structure


The field assignments are distinguished by the different levels of reference:

•         At the highest level, there is the domain, which is defined by the field type, field length, and value tables, or by means of fixed values.
•        At the second level, there are the data elements, which are defined by the domain as well as by language-dependent texts.
•      At the lowest level, there are the fields, which are defined by field names and data elements. The field-related rules refer to them.

                                  The placeholders and conversion rules defined by the field assignments are either linked to the target field directly or through the domain.

Example for Batch Upload :

Material master data transfer using LSMW for transaction mm01.

• Enter the Name for the project, subproject and object and press create button.
  
  
  

                                 As soon as you have create the project, you have to record the transaction,

(ctrl + F2) in this case its going to be mm01.

                                           Once you are through with the recording, maintain the field properties, by double clicking on the 3rd column of any field. This needs to be done for all the fields for which you made an entry during recording. Then go to LSMW, press ctrl + f8 for the corresponding project.

When you are done with maintaining the Object attributes( you have to mention the

name of the recording in Batch Input Recording ), now the next step is to maintain source attributes.

Select No.2 Radio option and Press F8 and in the next screen you have to mention the source structure by clicking create button and then save it.

Go back and by default No.3 Radio option must have been selected, if not select No.3

Radio option “Maintain source field”. In the source field screen, create the field, by pressing ctrl + F3 for all the fields that you made an entry during recording.

Go back and select No.5, “Maintain Field Mapping and conversion rules” and press ctrl F8.
Click Assign Source Field for each field in a structure and map it to the Project structure.

Go back and select No: 7 Radio option “Specify files” , press CTRL F8 , then create entry for Legacy Data, specify the file name and then save it.

Go back and select No:8 radio option “Assign files” and press CTRL F8 , then go to No.9

“Read Data”, execute it and enter the value for no.of transaction(say 1-999999), execute it.

Then Select No:10 “Display read data” to check whether value from .txt file is properly

assigned to the corresponding fields in the structure.

Follow the previous procedure for Step 10-12. Create the Batch Input

Session and Run the Batch input session.

• The Legacy System Migration Workbench (LSMW) is a tool that supports data migration from non-SAP systems to the SAP R/3 System. It is a component of the R/3 System.

• 
  The LSMW supports a one-time transfer of data (initial data load) and also offers a restricted support of permanent interfaces. Thus, a periodic transfer of data is possible. The LSMW, however, does not include any functions for monitoring of permanent interfaces. The tool does not support any data export interfaces (outbound interfaces).

DIFFERENCE BETWEEN ELEMENATRY & COLLECTILE SEARCH HELP

1) Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).


2) Collective search helps combine several elementary search helps. Collective search help thus can offer several alternative search paths.


3) An elementary search help defines the standard flow of an input help.


4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with collective search help.


5) A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.


6) Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in collective search help, they are expanded to the level of the elementary search helps when the input help is called.

ABAP SYSTEM VARIABLE

                                  SYSTEM VARIABLES HAVE BEEN PREDEFINED BY SAP . IT IS ALSO USED TO PASS INFORMATION TO FUNCTION MODULES  OR THE ABAP SYSTEM FIELDS ARE ACTIVE IN ALL ABAP PROGRAMS. THEY ARE FILLED BY THE RUNTIME ENVIRONMENT AND YOU CAN QUERY THEIR VALUES IN A PROGRAM TO FIND OUT PARTICULAR STATE OF THE SYSTEM. ALTHOUGHT THEY ARE VARIABLE,

                                       YOU SHOULD NOT ASSIGN YOUR OWN VALUES TO THEM, SINCE THEY MAY OVERWRITE INFORMATION IMPORTANT FOR THE NORMAL FOR THE PROGRAM.

1 )  FIRST ON EASY ACCESS SCREEN TCODE SE11 . THEN GO TO DATATYPES AND PRESS F4  .  NOW CLICK ON SEARCH DATA STRUCTURE .

2)  NOW CLICK ON  INFORMATION SYSTEM BUTTON .

3) IN THE STRUCTURE NAME WRITE SYST AND EXECUTE .

4 ) NOW CLICK ON STRUCTURE NAME SYST AND  ACCEPT .

5) NOW CLICK ON DISPLAY.

6) THE GIVEN BELOW IS TOTAL NO. OF SYS. FIELD OF SAP.

 IF YOU DON'T WANT TO FOLLOW THE WHOLE PROCEDURE THEN ALSO JUST

GOTO  TCODE SE11---> DATA TYPE ---> simply  type there  SYST ---> CLICK ON DISPLAY

THANK YOU .