lsmw

Former Member · ‎10-11-2007

hi,

can anybody provide d best example and step by step procedure for performing lsmw,he r she will be definately rewarded.

Former Member · ‎10-11-2007

Hi ,

No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.

The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.

More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.

The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.

So although it was designed for uploading of legacy data it is not restricted to this use.

We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.

The SAP transaction code is 'LSMW' for SAP version 4.6x.

For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.

You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.

If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw

The LSM Workbench carries out the following tasks:

Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)

Converts the data from the source format into the target format

Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is

STEPS OF LSMW:....

Example for xk01 (create vendor)

Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.

1. TCode : LSMW.

2. Enter Project name, sub project name and object name.

Execute.

3. Maintain object attributes.

Execute

select Batch Input recording

goto->Recording overview

create

recording name.

enter transaction code.

start recording

do recording as per ur choice.

save + back.

enter recording name in lsmw screen.

save + back

Now there will be 14 steps.

2. MAINTAIN SOURCE STRUCTURES.

Here you have to enter the name of internal table.

display change

create

save + back

3. MAINTAIN SOURCE FIELDS.

display change

select structure

source_fields->copy fields.

a dialogue window will come .

select -> from data file

apply source fields

enter No. of fields

length of fields

attach file

save + back

4. MAINTAIN STRUCTURE RELATIONS

display change

save + back

5. MAINTAN FIELD MAPPING & CONVERSION RULE

display change

click on source field, select exact field from structue and enter

repeat these steps for all fields.

save+back

6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED

execute

save + back

7. SPECIFY FILES.

display change

click on legacy data

attah flat file

give description

select tabulatore

enter

save + back

8. ASSIGN FILE

execute

display change

save + back

9. IMPORT DATA.

execute

display change

save + back

10. DISPLAY IMPORTED DATA

enter ok, it willl show records only.

back

11. CONVERT DATA

execute

display change

save + back

12. DISPLAY CONVERTED DATA

execute

display change

save + back

13. CREATE BATCH INPUT SESSION

tick keep batch input folder

F8

back

14. RUN BATCH INPUT SESSION.

sm35 will come

Object name will be shown here

select object & process *-- Tips by Dipika

Rward is use full.....

thanks.

Former Member · ‎10-11-2007

hi ric,

just have a look in forum by giving the word lsmw in search option,

friend no need to ask everyone , whatever the response u get all the stuff is from forum itself.

better to search in forum first.

Many-many threads available for ur post

Thanks

Former Member · ‎10-11-2007

Hi

Principles of LSM Workbench• Basic Principles of LSM workbench:-

– Most of the functions should reside in R/3. No collection of individual programs on different platforms.

– The quality and consistence of the data imported into R/3 should be more important than speed and performance of data migration.

– Existing knowledge and coding should be used.

– The developed ”mapping" and rules should be reusable and thus be used repeatedly in projects.

Features of LSMW

• Features:-

Integrated in R/3 and thus independent of individual platforms

The import technique to be used in an individual case, depends on the business object as well as on the availability of standard input programs

Data consistency due to standard import techniques:Batch input

Direct input

BAPIs (Business Application Programming Interfaces)

IDocs (Intermediate Documents)

Structured way of working, because you have to finish every step before starting the next step

Pre-requisites for LSMW

• Make sure that SAP customizing is finished.

• Run the relevant transaction in the SAP system manually with test data from the legacy system and see which fields must be filled. There may be required fields that do not correspond to data fields in the legacy system. In such a case, one should better assign a fixed value or establish an optional field for data transfer.

• Map the fields in advance in written form: Assign the source fields to the target fields.

• Determine the form in which non-SAP data will be transferred into the SAP system (e.g. via "Move" or according to a rule).

Import methods…

Preferred methods of input are described in order of preference:

1. IDOC’s

Advantages: Fast to load, easy processing, low programming for standard IDOC’s

Disadvantages: Good knowledge of IDOC processing required, time consuming if changes have to be made to a created IDOC

2. BAPI’s

Advantages: Fast to load, easy processing, logical interface for functional/end user based on the business processes involved.

Disadvantages: Not always complete with all input fields of a transaction

3. Standard/Direct Input

Advantages: Well tested method, Fast to load, easy processing.

Disadvantages: No enjoy transactions, not always complete with all input fields of a transaction.

4. Batch Input

Advantages: Easy modifiable, all fields are available, easy re-processing.

Disadvantages: Comparatively slow, to use new screens or tabs a new recording has to be created, not easily usable for enjoy transactions, dependant on user settings, difference in foreground and background processing may occur.

Step 1 - Enter transaction LSMW

Enter the transaction code (LSMW) or add this transaction to your favourites (right-click with your mouse on the Favourites map in the start menu and choose Insert transaction, type lsmw and press enter), since LSMW is an additional transaction, it is not available in the standard SAP menu.

Step 2 – project, subproject, objects

At the initial screen, you can create a new project, corresponding subprojects and objects via Edit -> Create new entry. Alternatively you can select from an existing project

• Project: An ID with a maximum of 10 characters to name your data transfer project. If you want to transfer data from several legacy systems, you may create a project e.g. for every legacy system

• Subproject: An ID with a maximum of 10 characters that is used as further structuring attribute

• Object: An ID with a maximum of 10 characters to name the business object

- At the initial screen, ‘All Objects’ provides a list of all projects created already.

- ‘My Objects’ displays a list of all objects you created personally

- ‘All Project Objects’ displays all objects of the selected project as tree structure.

- ‘Project Documentation’ displays any documentation written for the individual pop-ups and processing steps. You can print the project documentation out, send it and save it in various file formats.

- Select ‘Documentation’ to enter your notes. After clicking, a popup is displayed in which you can write down your personal documentation.

Initial Screen

By clicking the button execute or pressing the F8 key on your keyboard you go to the object, you selected.

By clicking the button create a new object for the selected project and subproject with the name entered in the object field is created.

By positioning the cursor on an entry and clicking on the button documentation, you can add change or delete comments.

Administration - list of existing projects

In the initial screen, you can display the administration functions via the menu path Goto Administration. Here you can find a list of all existing projects.

It enables you to create, process, display, delete, copy or rename projects, subprojects, objects and reusable rules.

By double-clicking on an entry you can branch to the entry display.

Step 3 – Execute

Once the project and subproject along with the object are determined we execute to find the list of steps to be performed for data transfer

Process steps• The number of process steps is dynamic and shall depend on factors like input method

• By clicking the ‘User menu’ button one can select – deselect the Process steps

• To proceed through the processing steps one needs to start from the first one and execute each of them

• A step can be skipped by selecting the next available processing steps’ radio button

Maintain object attributes

Application Toolbar in Process steps

User Menu: Here you can make an individual selection from the displayed processing steps. Pressing button ‘Main steps’ automatically activates all processing steps mandatory for a data conversion.

Numbers On or Off: You can activate or deactivate the numbering of the individual processing steps.

Double click = Display or Double click = Change: Here, you can determine whether display mode or change mode is selected by double clicking.

Object overview: Displays all object information for the selected object.

Information includes object information, source structures, target structures, structure relations, source fields, target fields, field mapping.

Action log: Displays a detailed overview for all processing steps already carried out. You can reset the action log via the menu path Extras -> Reset Action Log. This action is stored with a reference to the user and the date.

Maintain Source structures

In the step ‘Maintain Source Structures’ you define the structures of the object with name, description and the hierarchical relationships:

Click on Change button. You can now define, change, reassign or delete structures. All these functions are available via pushbuttons.

When you define more than one structure, a popup is displayed querying the relations between the structures: equal/subordinate?

Note: For migration objects created via transaction recording, you may only define one structure per recording, since only one flat target structure per recording is available.

Maintain source fields

In the step ‘Maintain Source Fields’, fields are created and maintained for the source structure defined in the preceding step

Use source fieldnames with the same names as the target fieldnames as much as possible, because it allows you to use the ‘auto-field mapping’ function in step 5 ‘Maintain field mapping and conversion rules’.

Maintain source fields

Different possible ways of defining and maintaining the source fields:

Make sure that you are in change mode and the cursor is positioned on a source structure or an existing source field

1. Create Individual source fields - By clicking on the button ‘Create source field’ you can specify the field name, field label, field length and field type

During data read, you can specify whether date values are converted into the internal date format (YYYYMMDD) and amount fields are converted into the calculation format (1234.56)

‘Selection Parameter’ can be set during Read/Convert data. If you select this indicator, the corresponding field is made available as selection parameter when reading or converting data.

2. Maintain Source Fields in Table Form – Clicking on the ‘Table Maintenance’ button displays the fields in a tabular format.

Different possible ways of defining and maintaining the source fields:

• 3. Copy Source Fields from Other Sources : By selecting ‘Copy Source Fields’ displays the following options:

- Upload (Text separated with Tabs) – The source field description is stored in a text file the columns of which are separated by tabs

- Copy from Another Object – Source field can be copied from source structure of another object

- Copy from Data Repository – Source field can be copied from a structure in SAP Data Repository

- From Data File (Field Name in 1 Line) - Source fields can be copied from a data file which should be stored on the PC in the form of text separated by tabs and contain the fields in the first line.

Maintain structure relations In the step ‘Maintain Structure Relations’, the structural relationships between source and target structures are defined. The possible target structures are defined during the selection of the object type and the import technique

To define structural relationships, position the cursor on the field target structures. Clicking create Relationship button opens a window that displays the existing source structures for selection

If you want to change the relation, remove the existing relation first. In addition, you can use Check to check the structural relationships for errors

Maintain Field mapping & conversion rules

• In the step ‘Maintain Field Mapping and Conversion Rules’, you assign source fields to target fields and define how the field contents will be converted

• All fields of target structure, which you selected in the previous step, will be displayed.

• For each target field the following information is displayed:

- Field description

- Assigned source fields (if any)

- Rule type (fixed value, translation etc.)

- Coding

Maintain Field mapping & conversion rules

Layout determination

The layout of the ‘Maintain field mapping’ screen can be determined. i.e. we can decide whether the ‘Global data’, ‘Technical fields’ should be displayed

Maintain Field mapping & conversion rules

To assign a source field, position the cursor on a target field in the tree structure and select Assign source field.

This displays a list of all available source fields for selection. You can assign the fields by double-clicking on them as well

After assigning the source fields, you define the conversion rules. The default rule is ‘Move’. However, you can select various standard techniques via pushbutton:

By clicking this button, after clicking once on a target field (in blue), LSMW displays the list of available source fields, by choosing one the standard rule ‘move’ is used to link the 2 fields

By clicking this button, after clicking once on a target field (in blue), the source field is deleted from the target field

By clicking this button, the display of this step can be changed. There are possibilities to show or hide several aspects of the field mapping

By clicking this button, a syntax check is performed for the conversion program, generated from the field mapping

These 3 buttons, which are available for every target field, display the help function (‘I’), the possible entries (?) and the last one displays the documentation in LSMW

Maintain Fixed values, translations…In the step ‘Maintain Fixed Values, Translations, User-Defined Routines’, you can process the reusable rules of a project, which are defined at project level, so they are the same for all objects

Fixed value: Here you can specify the length, type flag for lowercase/uppercase and value in addition to the name of the field.

Translation: Here you can enter information on the source field and the target field. If you are creating a new translation you have to save data first before you can change it

User Defined Routines: This routine can be re-used in other objects of the project. The system adds in ‘ur_’ to the name that you suggest to use for this routine. It opens up an editor wherein you can enter your ABAP code

Process Step- Specify File

In the step ‘Specify Files’, you describe all files to be used

If your legacy data is on the PC: In change mode, position the cursor on the line ‘Legacy data On the PC (Front-end)’. Select Add entry. A popup is displayed. Specify file path, file name and description and other properties

If your legacy data is on the R/3 server: In change mode, position the cursor on the line ‘ Legacy data On the R/3 server (application server)’. Select Add entry. A popup is displayed. Specify file path, file name and description and other properties

File for Imported data: Here, the file name is entered with file extension ’.lsmw.read’.

File for Converted data: Here, the file name is entered with file extension ’.lsmw.conv’. This file

will contain all your converted data after applying the conversion rules if any.

Process Step – Assign File

In the step ‘Assign Files’, you can assign the file name in step 7 declared as source file to the target structure defined in step 2 .

If you click on the Assign File button, after clicking once on a target structure (in yellow), LSMW displays the list of available source files.

If you click on the Delete Assignment button, after clicking once on a target structure (in yellow), the source file is deleted from the target structure.

Process step – read data

In the step ’Read Data’, the file specified in previous step is, as linked to the target structures in . Even though you can select a range of transaction numbers, the whole file is being read, only the amount of transactions written is influenced. So for tests it is easier to read all data and convert only a certain range, because in that step the program stops after finishing the range.

Process Step – Display read data

In the step ‘Display Read Data’, you can display the read data, choosing to show all read data or an interval as shown above. The data are shown as the source structures, in case more source structures are being used in one transaction, the hierarchy of the transaction is displayed by the use of a different colour legend. By clicking on one of the lines, you proceed to the field level of the line, where you can check the read data as shown below.

Process Step – Convert data

In the step ‘Convert Data’, works like the step ‘read data’, but uses the conversion program instead of the read program. You can define a range of transactions to be converted, at the end of this range the conversion program stops running.

Note: It is recommended that when you load big amount of data in production, load the first 10 records so that you can check and change when necessary.

Process Step - Display converted data

In the step ‘Display Converted Data’, you can display the converted data, choosing to show all converted data or an interval as shown above. The data are shown as the target structures, in case more target structures are being used in one transaction, the hierarchy of the transaction is displayed by the use of a different colour legend. By clicking on one of the lines, you proceed to the field level of the line, where you can check the converted data as shown below.

Process Step

After the step ‘Display Converted Data’ the exact content of the next steps may differ, depending on the import technique that you have chosen in step 1. The steps displayed by the program for the different import techniques are:

Standard batch input or recording:

Generate batch input session

Run batch input session

Standard direct input:

Start direct input session

BAPI or IDoc:Start IDoc creation

Start IDoc processing

Create IDoc overview

Start IDoc post-processing

reward if usefull

former_member235056 · ‎10-11-2007

Dear friend,

Pls find this examples,

Step-by-Step Guide for Using LSMW to Update Customer Master Records

by Mitresh Kundalia,

SAP Practice Manager, Quality Systems & Software (QSandS.com)

Business Case:

As a part of reorganization and to better serve the customer needs, you are regrouping many of the customers. In SAP terms, you are changing the Sales Office, Sales Group and Customer Groups for specific Customer Master Records. Typically, you would maintain customer records with transaction XD02 to update ‘Sales View’. You would enter Customer Key (Customer No, Sales Organization, Distribution Channel, and Division) and update relevant fields on Sales View screen.

This document contains Step-by-step instructions to use LSMW to update Customer Master Records. It has two demonstration examples - one using Batch Recording and another using standard SAP Object.

Note! The screenprints in this article are from IDES Release 4.6. They may differ slightly in other versions.

Demo Example 1

LSMW to Update Customer Master Records with Transaction Recording

Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as

CUST_obj .

The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure 2. To complete your data conversion, you need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.

Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by ‘Numbers on’ icon or hidden by ‘Numbers off’ icon. You can execute a step by double-clicking on the row. Toggle icon ‘Doubleclick=Display’ or ‘Doubleclick=Edit’, makes the step in ‘display’ mode or ‘change’ mode.

Step 1: Maintain Object attributes

In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.

Object type ‘Transaction Recording’

The system calls the transaction code XD02 and prompts you to complete the Change

Customer transaction, as shown in Figure 4. Enter the key customer information (I entered customer number 1000, sales organization 1000, distribution channel 01, and division 00) and choose ‘Sales’ view within ‘Sales area data’. Make changes to these three fields (I entered, sales office 1010, sales group 110, and customer group 01) and save the transaction.

Transaction recording for Transaction Code ‘XD02’

Once the transaction is completed, R/3 records the flow of screens and fields and saves the information.

Transaction recording overview

Note that the fields are populated with default values. The values you entered when you recorded the transaction are set by default.

Note that if you have more fields in the recording than needed, you can remove them by clicking ‘Remove Screen field’ icon.

Observe that the transaction-recording process stores field names in a technical format. By pressing the F1 key on individual screen fields and then pressing the F9 key, the system displays technical names. You then can replace the technical names with

descriptive names. Double-click on the field RF02D-KUNNR and enter the name as KUNNR and the description as Customer Account Number and remove the default value.

Field attributes

Similarly, double-click on all other fields with default values and make appropriate changes. Once you have made changes, the recording overview screen looks like what you see in Figure 7.

Transaction Recording Overview – with screen field attributes

Save your changes. When you go back to the initial screen, you will see that the initial screen steps have changed. Since you want to import data via the BDC method, the Direct Input and IDoc-related steps are hidden, as they are not relevant.

Step 2. Maintain Source Structures

Give a name and a description to the source structure .

Source Structure

Step 3. Maintain Source Fields

In this step, you need to list what fields are present in the source structure. The easiest way is to click on ‘Table Maintenance’ icon

to enter Fieldname, Type and Length for each field as shown in Figure 9.

Source fields of source Structure

Note that your input file will have four fields as key fields and you need to update three fields in the system.

Step 4: Maintain Structure Relations

Execute a step to ‘Maintain Structure Relations’. (See Figure 10.) Since, there is only one Source and Target Structure, the relationship is defaulted automatically.

Structure Relation

Step 5: Maintain field mapping and conversion rules

Field RF02D-D0310 represents that you chose ‘Sales view’ for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of ‘X’.

If your source file already has the field value, you choose rule ‘Source Field’.

Keep cursor on field ‘KUNNR’ and click on ‘Assign Source field’ icon to choose source field CUSTOMER from structure XD02S .

Assign source fields

Similarly, assign ‘Source Field’ rules to the remaining fields. Once all the fields are mapped, you should have an overview screen.

Field mapping and Conversion rules overview

Step 6: Maintain fixed values, translations, user-defined routines

You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.

Step 7: Specify files

In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt.

File attributes

Create an Excel file (Figure 14) with your data and save it as a Tab-delimited text file on your local drive (C:\) and name it XD02. txt.

Source data in Excel file (saved as Tab delimited file)

Step 8: Assign files

Execute step ‘Assign Files’ (Figure 15) and the system automatically defaults the filename to the source structure.

Assign file to Source Structure

Step 9: Read data

In this step, LSMW reads the data (Figure 16) from the source file (from your PC’s local drive). You have the option to read only selected rows and convert data values to Internal format.

Read Data

Step 10: Display read data

This step (Figure 17) is optional. If required, you can review the field contents for the rows of data read.

Display Read Data

Step 11: Convert data

This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.

Step 12: Display Converted data

Again this is an optional step to view how the source data is converted to internal SAP format

Display Converted Data

Step 13: Create batch input session

Once the source data is converted in an internal format, you can create a batch session to process updates.

Create Batch Input Session

Step 14: Run Batch Input Session

You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in

the system. You can confirm this by viewing the customer master records (XD03).

Note! Browsing thru these 14 steps, you may get a feeling that this is a very lengthy and time-consuming activity. However, for

the purposes of demonstration, I have made it detailed. Although it looks lengthy, actually it takes hardly few hours from start-to-

finish! After playing around with few simple LSMW scripts, you will find it so easy to change and create more complex ones.

Demo Example 2

LSMW to Update Customer Master Records with Standard Object

As an alternative to using ‘Transaction Recording’, you could also use a standard SAP object to update Customer Master Records.

Business Object ‘0050’ is already pre-defined in the system with standard Batch Input Interface Program ‘RFBIDE00’.

Create an Object CUST_OBJ within Project as LSMW_DEMO and Subproject as CUSTOMERS .

LSMW Object with Standard SAP Object

Note! For the Demo example 2, I will list only those steps that are different from the first demo example.

Step 1: Maintain Object attributes

You will be updating the customer master records with the help of Standard Batch Input; therefore, choose radio-button Standard Batch/Direct Input as shown in Figure 21. Enter Object ‘0050’ for Customer Master records and default method ‘0000’ and click

on Save.

Standard Batch/Direct Input Object Attributes

Step 4: Maintain Structure Relations

Sales view of Customer Master is stored in table KNVV. Accordingly, you need to update structure BKNVV. However, in addition, the Standard Object ‘0050’ also requires updates to BGR00, BKN00 and BKNA1 structures. (If you do not maintain Structure

relations for mandatory entries, you might get a message such as ‘Target structure BKNA1 needs a relation to a source structure’.)

Even though you don’t want to update any fields in these structures, you need to create a relationship with source structures. In

all, you need to create relationship for four target structures.

Create relationship between source structures XD02S with these target structures with icon ‘Create Relationship’ .

Keep Cursor on these four target structures and click on icon ‘Create Relation’ and structure relations are maintained .

Structure Relation

Step 5: Maintain field mapping and conversion rules

– Keep your cursor on ‘TCODE’ field and click on ‘Insert Rule’ icon

LSMW Conversion Rules

Choose radio button ‘Constant’ to enter value ‘XD02’ transaction code.

– Keep your cursor on field ‘KUNNR’ and click on ‘Assign source field’ icon

Choose source field ‘Customer’ from source structure ‘XD02S’. (See Figure 24.)

Assign Source fields

– Similarly, choose source fields for Sales Organization, Distribution Channel, and Division.

-Field Mapping and Conversion Rules

– Scroll down to structure BKNVV fields and assign source fields to three fields Sales Office, Sales Group, and Customer Group .

Field Mapping and Conversion Rules

Save and go back to main screen.

Step 12: Display Converted data

When you convert data, LSMW automatically converts into the appropriate structure layouts, as required by Standard program

(RFBIDE00).

Converted data into multiple structures

Note that if you had only one record in source file, the converted file has four records.

Earlier, creating this input file, so that the standard interface program can read it, was a big nightmare, the primary reason being

that it could have multiple record layouts. Even for a simple conversion with one input record, you would have to create this

complex file with many record layouts. The advantage of LSMW is that it prepares these multi-layout files automatically.

Step 13: Create batch input session

Once source data is converted in internal format, you can create a BDC session to process the updates .

Create BDC Session

BDC Session ‘CUST_OBJ’ created

Summary

Once BDC session is processed successfully, SAP updates the customer master records with relevant changes. Review these

specific customers (transaction code XD03) and confirm that the changes are correctly reflected in the master records.

Regards,

Ameet