Ansicht
Dokumentation

IDFI_MT940_C - Map Data for MT940 Bank Statement Import

rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Map the information for the structured account owner tag (tag 86) for the MT940 bank statement import process.

You can manually map which data/information in the bank statement file shall be imported as part of tag 86.

Note: The mapping is used only for the structured information.

The following use cases and examples explain to you how you can do the mapping in this cluster view:

Use Case 1:

You fill out onlythe Tag 86 screen by entering the country/region code, the bank key, and you define a delimiter that is used to separate parts of the information (subtags) you are going to provide to the account owner. In addition, you can also specify the offset and length of the external operation if needed.

You leave the fields in the Transaction Codeand Subtagsscreen empty.

In this case, the data for tag 86 is imported using the standard logic, only the delimiter is called from this activity.

Use Case 2:

You fill out the Tag 86 screen fields as explained in use case 1. On the Transaction Code screen, you enter UNALLOCATED as the external transaction and no other external transaction is entered. You leave the fields in the Subtagsscreen empty.

In this case, all the data for tag 86 is imported into the FEBRE table with the selected delimiter during the MT940 bank statement import process.

Use Case 3:

You fill out the Tag 86 screen fields as explained in use case 1. On the Transaction Code screen, you enter UNALLOCATED as the external transaction and no other external transaction is entered. On the Subtagsscreen, you enter UNALLOCATED in the Subtag Name field. If you do so, the Append Memo Line checkbox is selected. You can also specify the offset of the subtag content (for example, you enter 2 in the field).

In this case, each subtag content is imported into the FEBRE table with the selected delimiter during the MT940 bank statement import process. Since you entered an offset for the subtag content, the imported content does not contain the first 2 characters. Example: subtag content is 21VS:123456; the imported content will be VS:123456.

Use Case 4:

You fill out the Tag 86 screen fields as explained in use case 1. On the Transaction Code screen, you enter some external transaction IDs, and an UNALLOCATED entry. On the Subtagsscreen, you enter subtag names, and specify for each entry, to which table and field you want the data to be imported.

Example:

You enter External Transaction: 021, and an UNALLOCATED entry

On the Subtagsscreen you enter subtag 20 with mapping to FEBEP-BUTXT and subtag 21 with mapping to FEBEP-KKREF. For the subtag 21 entry, you also select the Append Memo Linecheckbox.

Subtag Name	Mapping To	Append Memo Line
20	FEBEP-BUTXT
21	FEBEP-KKREF	x

During the MT940 bank statement import, the system searches for the 021 external transaction ID, and:

• inserts subtag 20 data into FEBE-BUTXT, but not into the FEBRE table.

• inserts subtag 21 data into FEBE-KKREF, and also into the FEBRE table.

Use Case 5:

You fill out the Tag 86 screen fields as explained in use case 1. On the Transaction Code screen, you enter some external transaction IDs, and an UNALLOCATED entry. On the Subtagsscreen, you enter subtag names for the UNALLOCATED external transaction, and specify for each entry, to which table and field you want the data to be imported.

Example:

You enter External Transaction: UNALLOCATED

On the Subtagsscreen you enter subtag 90 with mapping to FEBEP-BUTXT and subtag 91 with mapping to FEBEP-KKREF. For the subtag 91 entry, you also select the Append Memo Linecheckbox.

Subtag Name	Mapping To	Append Memo Line
90	FEBEP-BUTXT
91	FEBEP-KKREF	x

During the MT940 bank statement import, the system searches for the 080 external transaction ID. If this transaction is not defined in the Transaction Codescreen or as a subtag on the Subtagsscreen for the UNALLOCATED external transaction, the system imports its data into the FEBRE table.

Use Case 6:

You fill out the Tag 86 screen fields as explained in use case 1. On the Transaction Code screen, you enter some external transaction IDs, and an UNALLOCATED entry. On the Subtagsscreen, you enter subtag names for an external transaction, and specify for each entry, to which table and field you want the data to be imported. In addition, you also create an UNALLOCATED entry at subtag level.

Example:

External Transaction	External Trans. Descr.
021	Description 1
UNALLOCATED	Description 2

For external transaction UNALLOCATED, you do not specify any subtags, and for external transaction 021, you enter the following subtags:

Subtag Name	Mapping To	Append Memo Line
20	FEBEP-BUTXT
21	FEBEP-KKREF	x
UNALLOCATED		x

During the import, the system finds external transaction 021 and imports data as follows:

• Subtag 20 is imported to FEBEP-BUTXT, but not to FEBRE.

• Subtag 21 is imported to FEBEP-KKREF and added to FEBRE.

• Other subtag data is added to FEBRE.

 

 

 

 

General Data in Customer Master   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 8514 Date: 20240523 Time: 195630     sap01-206 ( 137 ms )