Query on BAPI -LSMW

Question

Hi All,
I have a requirement on LSMW,  Can any body send me step-by-step procedure
to create SD-pricing conditions by using BAPI in LSMW.
Thanks,
Naga

Answer 1

hi naga,
FOR BAPI/IDOC METHOD, WE NEED TO MAINTAIN IDOC INBOUND PROCESSING EXPLICITLY. IN THE INITIAL TRANSACTION OF LSMW, GO TO SETTINGS AND CLICK IDOC INBOUND PROCESSING. WE NEED TO PERFORM THE FOLLOWING STEPS.
     DEFINE OR SELECT A FILE PORT FOR TRANSPORTING THE FILE. OPTIONALLY, YOU CAN ALSO CREATE A TRFC PORT.
     THE PARTNER TYPE HAS TO BE DEFINED OR SELECTED.
     THE PARTNER NUMBER HAS TO BE DEFINED OR SELECTED.
     IDOC INBOUND PROCESSING MUST BE ACTIVATED AND THE WORKFLOW CUSTOMIZING MUST BE CHECKED. BOTH OF THESE TASKS ARE PERFORMED ONCE IN EACH SYSTEM.
EXPORTING AND IMPORTING
EXPORTING - IT IS A GOOD IDEA TO PERFORM THE MIGRATION FROM A LEGACY SYSTEM TO THE SAP SYSTEM IN A TEST SYSTEM FIRST. THIS FUNCTION IS USED TO TRANSFER THE FIELD ASSIGNMENTS DEVELOPED TO THE PRODUCTION SYSTEM.
IMPORTING - IMPORT THE MAPPING AND FIELD ASSIGNMENTS INTO A DIFFERENT SAP SYSTEM.
1) MAINTAINING OBJECT ATTRIBUTES
SPECIFY WHETHER THE DATA IS TO BE TRANSFERRED ONCE OR PERIODICALLY. AND THEN SPECIFY WHICH METHOD YOU GONNA USE FOR THE DATA TRANSFER.
2) MAINTAING SOURCE STRUCTURE
WE CAN CREATE SOURCE STRUCTURES EITHER AT THE SAME LEVEL OR AT THE LOWER LEVEL.
3) MAINTAINING SOURCE FIELDS
WE CAN DIRECTLY CREATE THE SOURCE FIELDS. OR WE CAN COPY THE FIELDS USING THE FOLLOWING METHODS.
     UPLOAD – TAB DELIMITED TEXT
     COPY FROM OTHER OBJECT
     COPY FROM DATA REPOSITORY – FROM A STRUCTURE OF ABAP DICTIONARY.
     FROM DATA FILE.
4) MAINTAING STRUCTURE RELATIONS
HERE WE ARE ESTABLISHING THE STRUCTURE RELATIONSHIPS BETWEEN THE PROJECT AND THE SAP SYSTEM.
5) MAINTAIN FIELD MAPPING AND CONVERSION RULES
HERE WE ARE MAINTAINING THE FILED RELATIONSHIP BETWEEN THE SOURCE AND TARGET STRUCTURE.
AUTO FIELD MAPPING
AUTO FIELD MAPPING IS USEFUL IN CASE IF FIELDS WITH IDENTICAL OR SIMILAR NAMES/DESCRIPTIONS EXIST IN THE SOURCE AND TARGET STRUCTURES. THIS IS PARTICULARLY THE CASE IF DATA IS TRANSFERRED FROM ONE SAP SYSTEM TO ANOTHER SAP SYSTEM.
CONVERSION RULES
THE DEFAULE CONVERSION RULE IS TRANSFER (MOVE).
INITIAL, CONSTANT, TRANSFER (MOVE), PREFIX, SUFFIX, CONCATENATION, TRANSFER LEFT- ALIGNED, ABAP CODE, X FIELD, MOVE WITH LEADING ZEROS, [(R) FIXED VALUE, TRANSLATION AND USER-DEFINED ROUTINE].
THERE IS A CHECKBOX ‘ONLY IF SOURCE FIELD NOT INITIAL’.
GLOBAL VARIABLES
WE CAN USE THESE GLOBAL VARIABLES IN ABAP CODE.
G_PROJECT     CURRENT PROJECT                     
G_SUBPROJ     CURRENT SUBPROJECT                 
G_OBJECT     CURRENT OBJECT                      
G_RECORD     CURRENT TARGET STRUCTURE                 
PROCESSING TIMES
__BEGIN_OF_PROCESSING__     BEFORE PROCESSING OF DATA IS STARTED.
__BEGIN_OF_RECORD__     BEFORE THE CONVERSION RULE FOR A SOURCE STRUCTURE IS APPLIED.
__END_OF_RECORD     AFTER THE CONVERSION RULE FOR A SOURCE STRUCTURE HAS BEEN APPLIED.
__END_OF_TRANSACTION__     AFTER PROCESSING OF THE TRANSACTION HAS BEEN COMPLETED.                       
__END_OF_PROCESSING__     AFTER PROCESSING OF DATA HAS BEEN COMPLETED.                       
__BEGIN_OF_TRANSACTION__     BEFORE PROCESSING OF DATA FOR A TRANSACTION IS STARTED                       
GLOBAL FUNCTIONS
TRANSFER_RECORD.     THE CURRENT RECORD (THAT IS, THE RECORD FOR THE CURRENT TARGET  STRUCTURE) IS TRANSFERRED TO THE OUTPUT BUFFER.
TRANSFER_THIS_RECORD '...'.     A RECORD OF A DIFFERENT TARGET STRUCTURE IS TRANSFERRED TO THE OUTPUT BUFFER. THE NAME OF THE TARGET STRUCTURE HAS TO BE SPECIFIED AS ARGUMENT BETWEEN QUOTATION MARKS.
AT_FIRST_TRANSFER_RECORD.     THE CURRENT RECORD IS TRANSFERRED TO THE OUTPUT BUFFER IF IT IS THE FIRST TRANSACTION INVOLVED.
ON_CHANGE_TRANSFER_RECORD.     THE CURRENT RECORD IS TRANSFERRED TO THE OUTPUT BUFFER IF IT HAS CHANGED AS COMPARED TO THE LAST RECORD.
TRANSFER_TRANSACTION.     THE CURRENT TRANSACTION IS WRITTEN TO THE OUTPUT FILE. THIS TRANSFERS ALL THE RECORDS OF THE OUTPUT BUFFER TO THE OUTPUT FILE.
SKIP_RECORD.     THE CURRENT RECORD IS NOT TRANSFERRED TO THE OUTPUT BUFFER.
SKIP_TRANSACTION.     THE CURRENT TRANSACTION IS NOT WRITTEN TO THE OUTPUT FILE.
6) MAINTAIN FIXED VALUES, TRANSALTIONS, USER-DEFINED ROUTINES
REUSABLE RULES ALLOW YOU TO DEFINE CONVERSION RULES THAT CAN BE USED SEVERAL TIMES.
7) SPECIFY FILES
WE CAN SPECIFY FILES IN PC OR IN APPLICATION SERVER. IN CASE YOUR DATA IS STORED IN MULTIPLE SETS OF FILES, YOU CAN SPECIFY A WILDCARD (*) FOR THE NAME OF YOUR FILE. A WILDCARD CAN BE USED EVERY TIME THE FILES FOR SEVERAL IMPORT RUNS COME FROM DIFFERENT FILES; WITH THE FILE NAME BEING DIFFERENT IS SOME CHARACTERS ONLY.
FOR READ DATA, THE FILE NAME IS IN THE FORMAT OF PROJECT_SBPROJ_OBJ.LSMW.READ
FOR CONVERTED DATA, THE FILE NAME IS IN THE FORMAT OF PROJECT_SBPROJ_OBJ.LSMW.CONV
8) ASSIGN FILES
ASSIGNS THE FILES ALREADY DEFINED TO THE SOURCE STRUCTURES.
CONVERSION PROGRAM - /1CADMC/SAP_LSMW_CONV_OBJN.
9) READ DATA
THE FILES MUST HAVE BEEN SPECIFIED BEFORE AND MADE KNOWN TO THE LSMW. IN THIS STEP, THE DATA IS READ INTO THE APPLICATION SERVER.
WE CAN READ THE SELECTED DATA BY GIVING TRANSACTION NUMBER.
10) CONVERT DATA
THE FILE OF READ DATA IS TRANSFERRED TO THE FILE OF CONVERTED DATA DURING MIGRATION.
WHEN THE LSMW OBJECT IS BASED ON A BAPI OR AN IDOC, ADDITIONAL SELECTION PARAMETERS ARE AVAILABLE ON THE SELECTION SCREEN OF THE DATA CONVERSION PROGRAM:
CREATE IDOCS DIRECTLY:     IDOCS ARE COLLECTED AND THEN PASSED FOR IDOC GENERATION PACKAGE BY PACKAGE.
NO. OF IDOCS PER PACKAGE:     THE DEFAULT IS 50 (THIS VALUE CAN BE CHANGED).
THE ABOVE MENTIONED STEPS ARE COMMON FOR ALL THE TYPES OF IMPORTING METHODS IN LSMW.
IN THE CASE OF STANDARD BATCH INPUT/ BATCH INPUT RECORDING, CREATING BATCH INPUT SESSION AND PROCESSING THAT.
IN THE CASE OF STANDARD DIRECT INPUT, START A DIRECT INPUT SESSION.
IN THE CASE OF BAPI/ IDOC,
     STARTING IDOC GENERATION
     STARTING IDOC PROCESSING
     CREATING AN IDOC OVERVIEW
     STARTING IDOC POSTPROCESSING
FOR DIRECT INPUT METHOD, WE CAN USE EITHER THE PROGRAM RMDATIND OR THE TRANSACTION BMV0.
STARTING IDOC GENERATION FIRST, THE FILE WITH THE CONVERTED DATA IS READ. THE PACKETS OF INFORMATION IN THIS FILE ARE THEN SAVED TO THE SAP DATABASE IN IDOC FORMAT, BUT NOT TO THE DATABASE OF THE CORRESPONDING APPLICATION. THE SYSTEM ASSIGNS A NUMBER TO EACH IDOC. THE FILE WITH THE CONVERTED DATA IS THEN DELETED.
STARTING IDOC PROCESSING THE IDOCS CREATED IN THE FIRST STEP ARE SENT TO THE ASSOCIATED APPLICATION PROGRAM. THIS APPLICATION PROGRAM CHECKS THE DATA AND UPDATES IT IN THE APPLICATION DATABASE, IF NECESSARY.
Pls reward if helpful.