The following points provide a general approach to mapping individual
attributes:
Attribute comments can improve the readability of your map. However,
Map Designer Express does not automatically generate a comment for
an attribute. Table 18 provides some suggested standards for attribute comments
based on the type of transformation associated with the destination
attribute.
Situation
| Setting for Attribute Comment
|
If the child business object is not mapped
| =No mapping
|
Set Value transformation
| =SET VALUE(value)
|
Move transformation
| =MOVE
|
Join transformation
| =JOIN(srcAttr1, srcAttr2,
...)
|
Split transformation
| =SPLIT(srcAttr[index])
|
For
child business objects, when the mapping is done without calling a
submap to indicate the object has to be expanded to see its attributes
| =Mapping here
|
If the code to call the
submap is generated
| =SUBMAP(mapName)
|
If the attribute's mapping contains Mapping API calls that implement
relationships, such as:
-
retrieveInstances()
-
retrieveParticipants()
-
maintainSimpleIdentityRelationship()
-
maintainCompositeRelationship()
- All other methods in the IdentityRelationship class
except foreignKeyLookup() and
foreignKeyXref()
| =Relationship(type)
where type can be:
|
If the attribute's mapping
contains
foreignKeyLookup()
| =foreignKeyLookup()
|
If the attribute's mapping contains
foreignKeyXref()
| =foreignKeyXref()
|
Custom transformation that is not one of those listed above
(relationship or foreign key)
| =CUSTOM(summary)
|
If the attribute's code does not contain anything except setting the
verb
| =SET VERB
|