RSADRLSM02

Skip to end of metadata

 Created by Ciaran Heffron, last modified on Jul 20, 2015

Go to start of metadata

Purpose
This wiki is to give information related to the Business Address Services report RSADRLSM02.

Overview
SAP customers can have very large amount of addresses for their business, due to these large amounts of data and
new ways of receiving, updating and using address information, errors can occur and these errors could are costly. So
for any company good address quality is a desirable asset. The report RSADRLSM02 is used for the import and update
of reference data in the SAP regional structure (the regional structure is used to check whether the postal data for an
address is correct, the postal data is postal codes, cities, streets, etc.). 

Section 1
The SAP regional structure is delivered empty and must be filled by the customer, this means that the customer is
responsible for obtaining the country-specific data for filling the regional structure. Also customers are
responsible maintaining it. This country-specific postal data can usually be obtained from the relevant country's post
organization or an third party source. Here is a diagram of the flow of this information into the SAP system:

   

Section 2
The first step in this process is that the format of the reference data must be converted into a form that the report
RSADRLSM02 can run with, the LSM Workbench can be used for this.  

Section 3
The next step is that RSADRLSM02 should be run and the source file or files with the normalized data should be
specified. The SAP regional structure is then filled during the first import. For each time the report is run after
this, difference tables are filled with the new/different regional structure data, this data will then be used when the
Quarterly Adjustment is run.

Section 4
Any differences that may occur when the reference data is updated in the SAP regional structure are stored on the
database. The Quarterly Adjustment reports (RSADRQU1, RSADRQU2 and RSADRQU3) should then be run in
succession in order to adjust the addresses stored in the database according to the new regional structure data.

Section 5
It is very important that the latest version of the report is being used, the latest version of the report can be found in
note 333899. The correction instructions for the report are continuously updated in the note, please be aware that this
note cannot be implemented with SNOTE. 

Related Content
Related Documents
SAP Help - BC-SRV-ADR

Related Notes
333899 - Latest version of report RSADRLSM02

132948 - Transfer programs for the R/3 regional structure

333954 - Conversion postal code data using LSM Workbench 1.0

334096 - Converting postal code data with LSM Workbench as of V1.5

1467097 - Collective Note: Quarterly Adjustment programs

LSMW : Data Migration-City (RSADRLSM02)

Define Number Ranges for Cities

1.     Access the activity using one of the following navigation options:

Transaction code SRN1
SAP CRM IMG menu SAP NetWeaver > Application Server > Basis Services > Address
Management > Regional Structure/City File > Cities > Maintain Number
Ranges for Cities
2.     Choose Change intervals.
3.     Choose Insert Line  (F6)and enter the number range.
N From number To number NR Ext
o Status
01 000000000001 999999999999 0 X
4.     Choose the Ext  flag for the number range.
5.     Choose Save (Ctrl + S).

Data Migration – Step by Step

Transaction
LSMW
code

1.   Creating a transfer project

Start the LSM Workbench with Transaction ‘LSMW’. On the initial screen create a project, a subproject and
a transfer project. Press F8 to continue.

2.   Maintaining object attributes

Depending on the type of data to be converted and whether you want to create one or more files with
converted regional structure data you have to determine a certain object type at this point. For City
migration, user object type 0612.

3.   Defining source structures

 Here, you have to specify the data structure of the source data to be converted. This will usually be flat
structures, equally positioned next to each other. No field specification occurs here.

4.   Defining source fields

Enter the source data of the respective fields for each defined structure. Strictly observe the instructions of
the provider to avoid an incorrect reading of field contents.

5.   Maintenance of structure relationships

Enter the source structures on which target structures are to be mapped. Depending on the object type
selected for the data conversion different target structures are provided. The assignment can be performed
intuitively.

6.   Field mapping and conversion rule

Here, the source data is mapped to the target data field by field. It is possible to map the same source field to
several target fields. You can also define rules and specify fixed values. You should be very careful to avoid
problems with the data transfer. That is, you should take all special features in the field contents of the
source data into account, for example, and possibly caught through monitoring, particularly if this concerns
key values incompatible to the SAP system.

You must fill the following fields with values: 

For cities: LANGU, STATUS, CITY_CODE, REGION, REGIOGROUP, CITY_NAME
7.     Specify Files
In this step you describe all files to be used in the following steps:

      
If your legacy data is on the PC:

1. In change mode, position the cursor on the line “Legacy data — on PC (frontend)”.
2. Select Add entry. 
A popup is displayed.

    3.   Specify file path (F4 help), file name and description and other properties.
      
In Converted Data :
   1.   Specify Logical Path (F4 help)
   2.   Specify Logical File (F4 help)

     
Create Logical Path
Transaction code FILE
   1.   Select logical file Path Definition from the right side menu and then click on new entries.
         Write the name of the path and its description. Then save it.
   2.   Choose the path and double click on Assignment of Physical path to Logical path.
   3.   Click on new entries and choose Syntax group UNIX with Phisical path <FILENAME>.
         Then save the entry.

     
Create Logical File
Transaction
FILE
code
  1.   Double click on “Logical File Name Definition, Cross-Client. And then select New Entries
  2.   Give the name of the file, which should reflect its function.
   3.    Input Converted File Name from LSMW to field Physical File.
   4.    Input New Logical Path Name to field Logical Path
     
8.   Assign Files
The system automatically defaults the filename to the source structure
9.   Reading and converting data
Having performed the preparations described above the source files can now be read and filtered concerning
the defined source structures. Then the determined data records have to be converted. As a result, the target
files for the use in report RSADRLSM02 are generated.
10.  Start Direct Input Program
Input your Logical File Name to field log. file name city.
Regional structure – RSADRLSM02

This is the first part of my blog about LSMW migration

The business case:
The SAP regional structure is delivered empty and must be filled by the customer, this means that the customer
is responsible for obtaining the country-specific data for filling the regional structure. Also customers are
responsible maintaining it. This country-specific postal data can usually be obtained from the relevant country’s
post organization or an third party source.
Example described below- filling the regional structure for the country Germany.
Step 1. File in form:
CITY_CODE/REGION/CITY_NAME/CITYP_CODE/POST_CODE
Step 2. Program LSMW
1. Maintain Object Attributes
Object                        0602
Method                      0000
Program Name           RSADRLSM02
Program Type            D

2. Maintain Source Fields

Like file from pkt 1.
3. Maintain Structure Relations
Depend of target – mandatory two first.

4. Maintain Field Mapping and Conversion Rules

ADR_LSM0.DATA_ID        CT
ADR_LSM0.LANGU           D
ADR_LSM0.STATUS           Constant ‘’
ADR_LSM0.CITY_CODE   file
ADR_LSM0.REGION          file
ADR_LSM0.CITY_NAME  file
ADR_LSM0.CITY_CODE   file
ADR_LSM0.POST_CODE   file
ADR_LSM0.FLAG_DELIV Constant ‘X’
ADR_LSM1.DATA_ID         PC
ADR_LSM1.LANGU           D
ADR_LSM1.STATUS           Constant ‘’
ADR_LSM1.CITY_CODE   file
ADR_LSM1.REGION          file
ADR_LSM1.CITY_NAME file
ADR_LSM1.CITY_CODE   file
ADR_LSM1.POST_CODE   file
ADR_LSM1.FLAG_DELIV Constant ‘X’
5. Specify Files till convert Data – standard LSMW process
6. Start Direct Input Program [RSADRLSM02]

a. log. file name city                  LSMW Specify Files->Converted Data

b. log. file name postal codes    LSMW Specify Files->Converted Data
c. log. file name log                   free file name

Read log if everything is OK!

Step 3. Important Settings
1. OY17 -> Details for country             City file active[x] and/or Street postcode [x]
2. SRN1- > Intervals                             Like intervals in file (CITYP_CODE)
Related Documents