Field Map Instructions & Guidelines

Data Type Enter the type of data covered on this field map. For master data, enter Master Data - <category>. For other data, enter description.

<Bus App> FIELDS

Field Data Table Name Field Name Data Type No. of Char's No. of Decimal Places <Bus App> Field Use

<Bus App> FIELDS (cont.)

Org. Level <Bus App> Usage As Is Usage Project Usage

The remaining Data Conversion/Cleansing & Non-<Bus App> Application/Legacy System Mapping sections are required to be REVIEWED by Target's Legacy System Experts

DATA CONVERSION/EDITING LOGIC

Conversion/ Mapping Rule

NON-<Bus App> APPLICATION/LEGACY SYSTEM FIELDS

Source Table Name Source Field Name Source Field Format Source Field Length Source Field Use Source Business Logic

Data Element Information Short Text

Go to screen in <Bus App>.Highlight field.Press F1 or click on Help to open.

Enter table name from field data section in Help screen.

Go to screen in <Bus App>.Highlight field.Press F1 or click Help to open.

Enter field name from field data section in Help screen.

Go to screen in <Bus App>.Highlight field.Press F1 or click Help to open.

Enter short text from data element screen.

Go to screen in <Bus App>.Highlight field.Press F1 or click on Help to open.

Enter data type from data element screen.

Go to screen in <Bus App>.Highlight field.Press F1 or click on Help to open.

Enter No. of characters from data element screen.

The number of decimal places required for a numeric data type field.

Acceptable values for this cell are:R - Required entryO - Optional entry

Validations/Error Messages

Specify whether the data is Company, Client, or Plant related.

Describe how the <Bus App> system uses the field. In many cases, you can cut and paste the help description for the field from <Bus App> system. Identify if the field is a primary key. (unique key)

If the field usage is different from what <Bus App> has intended for the field, you need to document the existing implementation intention. You'll have to identify the domain for the primary key. The characteristic of the differences must be listed here in full.

If the field usage is different from what <Bus App> has intended for the field, you need to document the future implementation intention (ongoing project). The characteristic of the differences must be listed here in full. You'll have to identify the domain for the primary key.

Define any specific validations or error messages for the specific fields

Conversion/Editing Logic (including Default Value if not given)

Enter any logic to be followed by the conversion developer, such as: Handling of field lengths that are not equal, default values to use if the legacy field is empty or not valid, legacy fields to be used in conversion that do not directly map to <Bus App> fields. Please refer to list of values if any.

Enter one of the following conversion rule:R0 - System Generated.R1 - Fill with Legacy's system.R2 - Fill with default, select value based on conversion logic.R3 - Fill with Legacy if available, else fill with default.R4 - Fill from prior screen.R9 - No Conversion. Manual online entry post go-live. If you do not know yet what rule to put in, leave this column blank.

nop-<Bus App> Application/Legacy

System

Source Screen or Program Name or ID

Validations/Error Messages

Enter the name of the non-<Bus App> application/legacy system, from which this legacy field will be extracted

Enter the name or ID of the legacy screen, report or other output you are using to identify this legacy field.

Enter the name or ID of the legacy system table or file where this field is located.

Enter the name or ID of the legacy field that maps to the <Bus App> field already entered on this row.

Enter the format of the legacy field.Examples are:alpha - full text, alpha - abbreviated textdate (indicate exact format)alphanumeric (indicate exact sequence using a for alpha character, n for numeric character)numeric (indicate any hyphens, slashes, spaces, etc.)

Enter the exact number of characters allowed for this field on the source table or file.

Acceptable values for this cell are:R - Required entryO - Optional entry

Define any specific business logic required for the specific field, including any cross reference logic needed to convert source field to target field

Define any specific validations or error messages for the specific fields