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_CGJB01JBLC20 | Transfer Category 021: Forward Rate Agreement |
| Transaction Code | S_ABA_72000054 | IMG Activity: SIMG_CGJB01JBLC20 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC20 | Transfer Category 021: Forward Rate Agreement |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC20 |
Receiver Structure
The receiver structure comprises three parts:
- Financial transaction master record
- Financial transaction item (additional flow)
- Mode field
Each data record transferred to SAP Banking is interpreted as a master record or an item record, depending on the filled fields. The mode field must always be filled in (with 'I' for insert or 'U' for update).
The company code (BUKRS) and the financial transaction number (RFHA) must be filled in for each record since they uniquely identify the transaction.
An FRA consists of a master record and potentially several item records (additional flows).
Header and Item Structure
- External data transfer sequence
When FRAs are transferred, the master record is followed by the corresponding item records.
If a transaction has already been created, you can later create or change items for this transaction without sending the master record again.
- Identification of master/item records
SAP Banking identifies the transferred records based on the contents of selected fields in the receiver structure.
Fields Meaning Master Item
BUKRS Company code X X
RFHA Financial trans. X X
SGSART Product type X
SFHAART Transaction type X
SFHAZBA Flow type X
When you transfer a master record, you must fill in the product type (SGSART) and the financial transaction type (SFHAART) as well as the key fields of the transaction (BUKRS, RFHA). Leave the flow type (SFHAZBA) empty.
The item records transfer additional flows (such as charges) for the transaction. You can recognize an item by its flow type (SFHAZBA).
Check concept for an FRA transfer
The system carries out different checks depending on the validation level you have specified :
- Check level O
No checks
- Check level 1
No checks
- Check level 2
No checks
- Check level 3
Check of req/opt fields, fixed values and value tables; check against database. The system does not override the mode field (for example, if a record is to be inserted, but already exists in the database, the system does not change the mode field. Instead, an error message is displayed, and the system marks the record in question as erroneous.)
Special Features
- Number assignment
Number assignment must be external. The number range assigned to the transaction type must therefore also be external.
Note that leading zeros must be delivered with the financial transaction number.
- Processing Category
Settlement activities are not supported. You must therefore assign processing category 00101 to the transaction type.
Note that field selection information is not included in the transfer. If necessary, define the field selection in Customizing as "blank" for the affected transactions (meaning 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_CGJB01JBLC20 | 0 | I070004706 | External Data Transfer |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990928 |
| SAP Release Created in |
