Creating a field mapping
To create a field mapping:
- Select Release Management > Configuration > Field Mappings.
- Click Create.
-
Specify this information:
- Name
- Review or specify the unique name of the field mapping. Separate field mappings can be required for shipment schedules, sequence schedules, sequential call-offs, planning schedules, or shipments of a specific trading partner. The names of the field mappings for a trading partner must be assigned to the trading partner mapping on the Trading Partner Mappings page.
- Description
- Review or specify an explanatory description of the field mapping.
- Accounting Entity
- The accounting entity is a corporation or a subset of a corporation. The accounting entity is independent in regard to one or more operational functions or accounting functions. An accounting entity produces a P&L and balance sheet from a complete, balanced set of transactions, and is often a legal entity. An accounting entity is defined within a tenant and can contain locations. The field entry is disabled. The accounting entity is automatically set when you save the data. The default is the accounting entity where you are currently working.
-
Click the Create button of the table to add a field mapping line.
A new field mapping line is displayed.
-
Specify this information:
- Direction
- This field defines the valid message direction for the
trading-partner-specific field mapping. The message direction can be selected for
shipment schedules, sequence schedule, sequential call-offs, planning schedules, or
shipments:
-
Inbound: The field mapping is valid
for incoming
ShipmentSchedule
,SequenceSchedule
, andPlanningSchedule BOD
messages from Transformation orShipment BOD
messages from the ERP system that are processed by Release Management. -
Outbound: The field mapping is valid
for outgoing
ShipmentSchedule
,SequenceSchedule
, orPlanningSchedule BOD
messages from Release Management that are sent to the ERP system or to Transformation. - Both: The field mapping is valid for incoming and outgoing BOD messages.
Note: For shipment schedules, sequence schedules, and planning schedules the message direction is Inbound, Outbound, or Both. For sequential call-offs and shipments the message direction is Inbound. -
Inbound: The field mapping is valid
for incoming
- When editing, select the message direction from the drop-down list.
- Field Name
- This field defines the name of the plan field that is mapped to internal or trading-partner-specific information of the Reference ID field. The field can be a field in the plan header, in the order lines, in the sequential call-offs, or in the shipments. The message direction determines whether the plan field is the target field or the source field of the mapping.
- When editing, select the plan field from the drop-down list.
- Reference ID
- This field contains the reference ID in the reference lists of
ShipmentSchedule
,SequenceSchedule
,PlanningSchedule
, andShipment BODs
. The reference ID is used to access the trading-partner-specific information that must be mapped to the plan field. The plan field is defined in the Field Name field. The message direction determines whether the Reference ID field is the source field or the target field of the mapping. - When editing, select the reference ID field from the drop-down list.
- To add further field mapping lines, repeat steps 4–5.
- To edit a field mapping line, click the fields and edit the entries as required.
- To delete a field mapping line, select the field mapping line and click Delete.
-
Click Save to save the field mapping.
A notification displays that the field mapping has been saved successfully.