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_CGJB01JBLC12 | Transfer Category 022: Swaps |
| Transaction Code | S_ABA_72000053 | IMG Activity: SIMG_CGJB01JBLC12 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC12 | Transfer Category 022: Swaps |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC12 |
Receiver Structure
The receiver structure is composed of four parts:
- Financial transaction master
- Financial transaction item (conditions)
- Flows (additional flows/capital flows)
- Mode field
Each dataset transferred to SAP Banking is interpreted either as a master or a position, regardless of filled fields. The mode field must always be filled ('I' for insert or 'U' for update).
The company code (BUKRS) and the financial transaction number (RFHA) have to be filled in every record, as they identify the transaction.
A swap consists of a master, several items (conditions for the incoming/outgoing sides, and possibly additional flows (additional flows/capital flows).
Header and Item Structures
- Sequence for external data transfer
With external data transfer of swaps, the master has to be transferred first. With datasets thereafter, items and additional flows can be transferred in any order.
After transactions have been created, you can later create or change single items and flows for the transaction without having to transfer the master anew.
- Identification of master, item, and flow records
SAP Banking identifies the transferred records according to the contents of selected fields in the receiver structure.
Field Meaning Master Item Flow
BUKRS Company code X X X
RFHA Financial trans. no. X X X
SGSART Product type X
SFHAART Transaction type X
SKOART Conditions type X
SFHAZBA Flow type X
When transferring a master, in addition to the key fields of the transaction (BUKRS,RFHA), the product type (SGSART) and financial transaction type (SFHAART) must also be filled. Condition type (SKOART) and flow type (SFHAZBA) have to remain empty.
Conditions (interest rate, interest rate adjustment) are recognized in item records by means of their condition type (SKOART).
In the flow records, additional flows (for example, charges) or capital flows (nominal capital increases) are transferred. An item is recognized by means of its flow type (SFHAZBA).
Check Routine for Swap Transfers
Different types of checks are made, depending on the validation level you define:
- Validation 0
Not supported
- Validation 1
Not supported
- Validation 2 Not supported
- Validation 3
Checks required/optional fields, fixed values, value tables. Checks against database and mode field cannot be overridden (if a record is to be added that already exists on the database, the mode field will not be reset. Instead, an error message appears and the record will be marked as incorrect).
Special Features
- Number assignment
Number assignment has to be made externally. The number range to be assigned to the transaction type must also be external.
Note that with financial transaction numbers, the preceeding zeros are also transferred.
- Processing category
Settlement procedures are not supported. Processing category 00001 must therefore be assigned to the transaction type.
Note that within data transfer, the system cannot take into account field selection information. If appropriate, in Customizing store an 'initial' field selection for the affected transaction (which means you set all field selection entries to 'not specified').
Prerequisites
As certain flows and conditions are automatically generated when creating a swap, certain Customizing settings are required for the transfer:
A flow type of category 'nominal capital increase' has to be assigned to the transaction type for the incoming and outgoing sides.
Condition types of categories 'final repayment' and 'interest rate adjustment' have to be assigned to the transaction type for the incoming and outgoing sides.
Required/Optional Fields
Note the following regarding the conditions check:
The following key fields (receiver structure) need to be delivered for conditions:
- BUKRS : Company code
- RFHA : Financial transaction number
- RKONDGR : Side
- SKOART : Conditions type
- DGUEL_KP : Validity date
- NSTUFE : Level number (only with individual dates, otherwise zero)
Interest conditions with single dates: Single dates have to be given interest conditions. Differentiation occurs by means of level numbers (NSTUFE). The first single date must be given the level '00'. If you want to use a formula (SFORMREF) or an interest rate (PKOND), it has to be delivered with each item.
Formulas: A formula is specified using field SFORMREF. The different parts of the formula are delivered to the receiver fields MIN_PKOND, MIN_SZSREF, MAX_PKOND, MAX_SZSREF, (V1-V4)_PKOND, (V1-V4)_SZSREF, SRUNDUNG and PRUNIT.
Interest rate adjustment conditions are created automatically. If special interest rate adjustments are to be made, a condition item has to be delivered (the process is the same as the online transaction for other interest rate adjustments).
When checking flows, pay special attention to the following:
The following key fields (receiver structure) have to be delivered with a flow:
- BUKRS : Company code
- RFHA : Financial transaction number
- DZTERM : Payment date
- SFHAZBA : Flow type
Additional flows: The +/- sign (SSIGN) must be filled.
Capital flows: In addition to the payment date (DZTERM), the calculation date (DVALUT) must also be filled. The side (RKONDGR) is a required field. With capital reductions, there is no check to see whether there is enough nominal capital available.
Business Attributes
| ASAP Roadmap ID | 308 | Transfer Data to Live System |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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_CGJB01JBLC12 | 0 | I070004706 | External Data Transfer |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990928 |
| SAP Release Created in |
