Maintaining mapping elements

Use the Payment/Receipt Elements (tfcmg0123m000) session to maintain mapping elements that are used to derive the values of XML elements when the SEPA XML file is generated.

After the layout has been initialized, all the data elements that are defined in the minimum dataset that is mandatory according to the EPC rulebooks are included in the default XML tags. By default, many of these tags have been mapped to predefined data elements; other tags are generated.

To view or maintain mapping details, in the XML Payment/Receipt Layouts (tfcmg0524m000) session, select the XML tag line and use the appropriate menu to start the Payment/Receipt Elements (tfcmg0123m000) details session.

If, in the details session, Map to Payment Element is selected, you can start the Payment/Receipt Elements (tfcmg0123m000) session through the appropriate menu to check the list of available payment/receipt elements.

A payment element refers to the information that is available in LN that can be attributed to a payment, for example, payment batch, pay-to business partner, or the IBAN of the business partner’s bank account. In LN this could be either of the following:

Table field, such as Payment Batch (tfcmg103.btno)
Variable, such as the Suffix (Norma 68 or 34-1) field in the Process Payments (tfcmg1240m000) session

Payment element descriptions are generated at runtime in the user language, if available; otherwise they are generated in English.

The syntax of the description is: Table Name / field1 name / field 2 name ...

Example

Composed Payments/Pay-to Business Partner/Address Code/Name

On the XML Payment/Receipt Layout Lines (tfcmg0125m000) tab, select the XML tag and, on the appropriate menu, click Payment/Receipt Elements.
The Payment/Receipt Elements (tfcmg0123m000) session is displayed. In this case, only the used elements are shown.
For example, IBAN is mapped to payment element 011003000000 – Composed Payments/Pay-from Bank/IBAN.

Field	Description
Element	The element code
Description	Description of the payment element in the user language, if available; otherwise it is in English. The descriptions are based on the field descriptions from which the elements are derived. The syntax is `Table/Field1/Field2...`
Receipt/ Payment	Indicates whether the payment method refers to a payment or a receipt.
Data Type	Attribute Boolean Date Decimal Number Node String UTC Date
Map to Payment Element	If this check box is selected, the element is used for mapping, but only if the Process... command in the Payment/Receipt Elements (tfcmg0123m000)) has been executed. By default, only mapped elements are shown. To change the mapping, select or clear the Map to Payment Element check box.

The payment/receipt mapping elements are in turn mapped to tables in LN, which is predefined and cannot be changed.

Mapping to a payment/receipt element is shown as a path separated by the separator defined in the layout header. Therefore, in this example, the IBAN code is retrieved first through the composed payments, then the bank, and finally through the IBAN number (table tfcmg001.iban).

To view all available mapping elements for the selected layout line, on the appropriate menu, click Only Used Elements.

To define other mappings, select or clear the Map to Payment Element check box.
After you change a mapping, on the appropriate menu, click Process... to actualize the mapping.
After you have completed the changes in the layout and the mappings, in the XML Payment/Receipt Layouts (tfcmg0524m000) session, on the appropriate menu, click Activate Layout.
If an error occurs, a report is printed and the activation stops.

In addition to checking the correctness of the layout lines, the activation process generates an internal (system) sequence called Sort Sequence. This sequence determines the order in which the final payment file is generated.