Maintaining Source Fields 

Prerequisites

The source structures must have been defined before you maintain the source fields.

Procedure

You have the following options: You can create the source fields:

...

       1.      From the list of steps, choose Maintain source fields.
The LSM Workbench: Source fields screen appears.

       2.      Choose Change.

       3.      Position the cursor on the associated source structure if you want to define a field for the first time. For any additional field definitions, make sure to enter the new field below the original cursor position.

       4.      Choose Create Field.
A dialog box appears.

       5.      Fill in the following fields:
Field name
Field text
Field length
Field type: Character field, numeric field, packed field, or date field.

       6.      Choose Continue.

 

You can also maintain source fields in table format:

...

       1.      Position the cursor on a source structure or on a source field already created.

       2.      Choose Table maintenance.

       3.      Enter the field name, type, length, and field description.
If you enter the field name only and then choose Enter, the system will assign the following values:
Field type: 'C'
Field length: 10
Field description in accordance with the field name.

●      By choosing Extras ® Non-allocated source fields, you can display the source fields that have not been allocated yet, i.e., you can see whether there is data that has been neglected.

●      If you want to run a migration test with a limited number of data, set an indicator for Selection parameters underRead/convert data.

●      If data for several source structures is included in one file, the value of the respective source structure has to be specified under Identifying field content.

 

If you choose the Fields with the Same Name option, all source fields that appear more than once are displayed. In this way, you can easily identify the key fields of dependent structures. It also allows you to see whether there are identical names in different source structures. In the latter case, you should change the relevant names, so that all non-key fields of the source structures are globally unique. All fields with the same names are used as keys.