ploading Customer Master Extended Address using BAPI method By Ansumesh Kumar Samal, IBM Readers of this post

can refer to my earlier post Uploading Customer Master Data using Direct Input Method for detailed level of explanation of each LSMW steps. Customer Master Data is the key object in all Order-To-Cash related operations f or an organization. It consists of several category/types of data among which Cu stomer Address data is one. Almost all type of customer master data can be migrated to SAP using Standard Ba tch/Direct Input Method (Using program: RFBIDE00). Even Customer Address can als o be migrated using program standard program RFBIDE00.However there are few spec ific reasons which lead us to use different approach for uploading Customer Mast er Extended Address Data, Reason There are many additional address fields which are not available in the structur e of standard program RFBIDE00.In an alternative approach we created one more LS MW object using BAPI method available under LSMW and used Business Object BUS400 1 & Method SAVEREPLICA for address migration. All detailed steps with screen-sho ts are given below. Source System: File from Presentation Server Target System: SAP ECC. Prerequisite Data cleansing is performed Customers are already created in the system through customer master load L SMW for all account groups All configuration data should be available in the system. User s executing conversion should have access to XD01/VD01/FD32 transaction Doing Customer address load using BAPI method will generate IDOC, and by generat ed IDOC data will be posted/migrated to SAP. Below shown configuration is required for doing this LSMW object. One port needs to be created. Destination system details (Partner and Partner Type) needs to b e provided as shown below LSMW Details Step by Step. LSMW : Initial Screen Create One project ZDEMO_O2C and a sub-project OTC under that in t-code LSMW Create a LSMW object 2_CUSTOM_ADDRESS under sub-project OTC Click on Execute button which will display initial screen with all the available steps for all techniques. However after first step based on the techniques used for the LSMW, few steps will be removed. STEP 1: Maintain Object Attributes Based on the LSMW techniques the below are the final steps which we need to exec ute for ADDRESS load. STEP 2: Maintain Source Structures Create source structure name as CUSTOMER_ ADDRESS for Structure of Legacy data c ustomer address respectively. STEP 3: Maintain Source Fields Created all source fields under above Source Structure. And one important point here i.e. field sequence under the source structure should be created in the sam e sequence what it is given by the customer in the flat file. Click here for the file format. Before uploading we saved the XLS file into TXT format and then pa ssed to the LSMW object. TEP 4: Maintain Structure Relations

Here in this step we need to map the custom source structure created by us with the standard structure available in the standard program interface. We need not to map the custom source structure with all available standard structures which are in scope. We need to consider those source structures of standard program wh ich contains any of the source fields that defined in step number 3 above STEP 5: Maintain field mappings and conversion rules This is a very important step and needs to be done very carefully. Here we need to carry out mapping between each and every custom sources fields with the stand ard structure fields. Use menu path EXTRAS-> Auto field mapping and also do manually mapping where eve r required For manual mapping put the cursor on the destination structure field and then cl ick on Source field button as shown below. For example OBJ_TYPE

Click on Rule button to insert initial check Rule. Now after rule insertion, mapping looks like below. There are also few other possible features are available under Rule button which can be used according and effectively based on the requirement. STEP 6: Maintain Fixed Values, Translations, User-Defined Routines If there are more than one LSMW object which makes use of a similar section of c ode, in that case a global routine can be defined at this steps which will be ac cessible by all LSMW objects under a LSMW Project. Double click on the routine, you can see the source code. STEP 7: Specify Files In this step we specify the path and different other attributes of the input fla t file which is there in your presentation server of the system. Create one source file with following properties.

File contents: Select data for one source structure (table) Radio button. Delimiter: Select as per the source file (In my case TAB as already expl ained) File structure: Check Field names at start of file if 1st row belongs to the f iled names. File type: Check record end marker radio butto n. Code page: Check ASCII radio button. At the end of this step two files will be created in the application server as s hown above. First file will contain data which read from presentation server. Second file will contain data which is the converted format of read data in LSMW program format. STEP 8: Assign Files Assign the respective files defined in previous step to the custom source struct ures for LSMW object. So that when ever data read from the flat file, Read data sit in respective fields under the custom source structure STEP 9: Read Data

The Data has to be read from the Presentation Server to the Application Server f iles for each LSMW objects. When we execute this step data read from the present ation server and store in respective files which explained in earlier step. STEP 10: Display read data The data read can also be displayed by executing this step. STEP 11: Convert Data Execute the this step to convert the read data into a format for posting which s ystem can understand and LSMW program can process STEP 12: Display converted data The data converted following the above step are store in a respective file in th e application server as mentioned in earlier step can also be displayed by execu ting this step. STEP 13: Start IDOC Generation Execute this step to generate IDOC based on the converted file content Information message will be displayed as shown below STEP 13: Start IDOC Processing Execute to see and process the generated IDOC and its posting status message

RED highlight sections are our result sections which are actually additional add ress fields we have update through this method.

Note: Here we have updated customer address for all existing customers in the sy stem. There was a separate LSMW object which created all customers in the system . That time one record got created in table KNA1.So while doing Address LSMW by this method, we need to have same data related to customer (Example Customer nam e) and it will be updated in table ADRC EX: Say during customer master LOAD we have customer name as GBS Pvt Ltd and dur ing address load we are providing a different customer name. Then the same custo mer number will have two different names in tables KNA1 and ADRC respectively. T his point needs to be considered