Understanding the Mapping Process
Mapping translates values from the source data to the format of the target source by using default target values, transformations, translation sets, and map rules to facilitate the process.
This section discusses:
Target field default value setup.
Translation set setup.
Transformation creation.
Map rule setup.
Target field default values allow you to set up values, which can be reused across multiple maps, to map to the target field. This allows having a central location for updating a target field value. For example, the target field default value for EFF_STATUS is set to A, and is used in 100 maps. At runtime, A is inserted into the target field for all those maps. If the value for EFF_STATUS is changed to Active, the value is updated once and when the 100 maps are run again, the new value will be inserted into the target field. No changes are necessary at the map level.
A default with no value is initialized to a blank, a zero, or the appropriate PeopleSoft null value.
When setting default values, consider the target field data type format:
Character fields are used for names, codes, and letter values.
Uppercase converts the field value to uppercase and signifies that no other formatting options apply to the field. Mixed case stores uppercase and lowercase characters as entered.
Number fields and signed number fields are fixed in field length and allow the entry of positive numbers.
Only signed numbers allow the entry of negative numbers.
Date fields contain calendar dates.
A date field has a field length of 10 characters and is maintained by the system.
The default format of a date field is defined by the database and can be overridden by your browser settings.
The following table discusses data type format considerations:
|
Source Field |
Target Field |
Required Considerations |
User Warning |
|---|---|---|---|
|
Date |
Date |
NA |
NA |
|
Date |
DateTime |
NA |
NA |
|
Char |
Char |
Truncation occurs as needed. |
NA |
|
Char |
Number |
Data must be numeric in the character source field. |
Appears when the character field is greater than the number in bytes. |
|
Number |
Number |
NA |
Appears when the numeric field is smaller in integer positions, decimals, or if the source is signed and the target is not. |
|
Number |
Char |
Character must be big enough. |
NA |
|
DateTime |
Date |
NA |
NA |
|
DateTime |
DateTime |
NA |
NA |
|
Time |
Time |
NA |
NA |
|
Long |
Long |
NA |
NA |
Note: The default value assigned must match the target field format or an error occurs at runtime. For example, you cannot assign a value of 7A to a numeric field. Specific error messages display during the save if a datatype conversion error occurs.
Use translation sets to define equivalent values or a code set for data conversion. For example: EA equals Each, GAL equals Gallon, and IN equals Inch. Translation sets make the data values consistent.
When data is copied from the source to the target, the data can be transformed by using edits, look ups, or PeopleCode. Transformations enable you to change a column's value. The Transformation Wizard guides you through the process of creating transformations.
You can create rules to be used by the AutoMapper feature in the map field detail definition where it attempts to match source fields with target fields. Use rules to assign correct default values to target fields when creating maps. By using map rules, you can assign a literal default, transformation, source field, or a translation set to a target field. If the map rule is required, you cannot override the rule when you define map field details.