Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-DP (Application Component) Transaction Data Pool⤷
JBDC (Package) Customizing IS-B Data Pool
IMG Activity
| ID | SIMG_CGJB01JBLC18 | Transfer Category 012: Foreign Exchange |
| Transaction Code | S_ABA_72000077 | IMG Activity: SIMG_CGJB01JBLC18 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC18 | Transfer Category 012: Foreign Exchange |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC18 |
Receiver Structure
The receiver structure is composed of the following parts:
- Financial transaction master
- Financial transaction item (additional flows only)
Each data record imported into SAP Banking is either interpreted as a master record or an item record, depending on which fields are filled. The mode field must always be filled (I for insert or for update). A foreign currency transaction consists of a master and possibly several items (additional flows).
Header and Item Structure
- Order (sequence) in external data transfer
In the external data transfer of foreign exchange transactions, the master record has to be tranferred first, and then, in the following records, any items (addition flows) for the master.
If a transaction has already been created, single items can later be added or changed, without having to transfer the master anew.
- Identifying master records and item records
SAP Banking identifies the transferred records according to the content of selected fields in the receiver structure.
Example
Receiver structure Master Item Mode field
Data record X X
Data record X X
Data record X X (additional flow)
Data record X X
Data record X X (additional flow 1)
Data record X X (additional flow 2)
Reversal
To reverse a foreign exchange transaction, a master record in change mode must be sent with the following fields:
- BUKRS company code
- RFHA transaction number
Note that the financial transaction number must be delivered with leading zeros. - SAKTIV active status
The indicator must be filled with value '3' for reversal. - MODE Mode
The indicator must be filled with value 'U' for update.
Master record: required fields
- BUKRS company code
- RFHA transaction number
External number assignment is to be used. The number range, to which the transaction is to be assigned, must also be external. Note that leading zeros must be delivered with the financial transaction number. - SGSART product type
- SFHAART transaction type
Settlement transactions are not supported. Processing category 00102 must be assigned to the transaction type. - DZTERM payment date
The value date of the foreign exchange transaction indicates the date on which the payments take place. - MODE mode
The indicator must be filled with the value 'U' for update or 'I' for insert. - BZBETR1 payment amount in payment currency - sale
- BZBETR2 payment amount in payment currency - purchase
- WGSCHFT1 currency - sale
- WGSCHFT2 currency - purchase
- DVTRAB contract date
Date on which the respective contract was completed. - KONTRH business partner number (central business partner)
Note that the business partner number must be delivered in full with leading zeros. You must deliver either field KONTRH or field EXTPARTNR. - EXTPARTNR external business partner number (optional field)
You can deliver this in place of KONTRH. If you transfer field EXTPARTNR, then field KONTRH is derived automatically and filled using the business partner information. Note that the external business partner number must always be transferred in its full length with leading zeros.
The flow type (SFHAZBA) must remain empty
Item record: required fields
Additional flows (for example, charges) for the transaction are delivered in the items. An item is recognized by means of the flow type (SFHAZBA).
- BUKRS company code
- RFHA transaction number
Number assignment must take place externally. The number range assigned to the transaction type must therefore be external. Note that leading zeros must be delivered with the financial transaction number. - DZTERM payment date
The value date of a foreign currency transaction indicates the date on which the payments take place. - MODE mode
The indicator must be filled with value 'U' for update, or 'I' for insert. - BZBETR payment amount in payment currency
- WZBETR payment currency
- SFHAZBA flow type
For example: Charges, commission. You need to assign the flow type to the transaction type (SFHAART) in Customizing. - SSIGN direction
+ = inflow, - = outflow
Check Concept for Foreign Exchange Transfer
Different checks are carried out, depending on the validation level set.
- Validation 0
Not supported
- Validation 1
Not supported
- Validation 2
Check of required/optional fields, fixed values, and value tables; check against database, mode field overridden (if a record is to be added that already exists on the database, the mode field is changed to U).
- Validation 3
Check of required/optional fields, fixed values, and value tables; check against database, mode field is not overridden (if a record that is to be added already exists on the database, then the mode field will not be changed. Instead, an error message is shown and the relevant record is marked as incorrect).
Special Features
Note that no field selection information is included in data transfer. If required, in Customizing store an 'initial' field selection for the relevant transaction (which means you set all field selection entries to 'not specified').
Business Attributes
| ASAP Roadmap ID | 308 | Transfer Data to Live System |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CGJB01JBLC18 | 0 | I070004706 | External Data Transfer |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20020204 |
| SAP Release Created in |
