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_CGJB01JBLC22 | Transfer Category 007: Securities - Class Data |
| Transaction Code | S_ABA_72000075 | IMG Activity: SIMG_CGJB01JBLC22 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC22 | Transfer Category 007: Securities - Class Data |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC22 |
Receiver Structure
The receiver structure is comprised of fields for class data and the mode field.
In the class data you can differentiate between different record types based on the data which they transfer:
- Master and condition header
- Condition items
- Subscription deadlines for subscription rights
- Exchange assignments
The system recognizes a record type based on the fields filled in the receiver structure. For a condition item, the field SKOART (condition type) is filled; for a deadline for subscription rights, the field RANL2 (referenced security ID) is filled; and for an exchange assignment, the field RHANDPL (exchange) is filled. If none of these fields is filled, the system assumes it is dealing with data for the master and condition header.
Depending on the record type, product type and condition type, the required/optional control determines which fields in the receiver structure are needed. The securities ID number (RANL) must be specified for all record types. This number can only be assigned externally, that is, you must set the number range for the respective product type to external. Also ensure the class numbers are delivered with leading zeros.
Header and Item Structure
All data records for a class must be transferred in a block. Each class can only have one data record with the category 'master' and one with the category 'condition header'. Several condition items, subscription deadlines and exchange allocations are possible, however. If the data for the master and condition header is not yet available in the system, or if the data is to be changed, this data record must be transferred first. Any condition items, subscription deadlines or exchange assignments which follow must be transferred in adjoining blocks; the blocks can be in any order, however.
As in the online transaction, exchanges must be transferred in update mode ('U').
Special Notes
In the online transaction, the system creates the condition interest rate adjustment for bonds with a variable interest rate using a separate screen. During external data transfer, you must assign the following values to the various selection options for interest rate adjustment and interest rate fixing in the fields SVMETH and SFMETH:
Interest adjust. Interest fixing SVMETH SFMETH
Period start Adjust. date 6 8
Period start Period start 6 6
Period start Period end 6 3
Period start Exp. date 6 9
Frequency Adjust. date 1 8
Frequency First adjust. 1 1
Single date Adjust. date 5 8
Single date First adjust. 5 1
Per table entry Adjust. date 7 8
Fields DZANP (1st interest rate adjustment date) and DZFEST (1st interest rate fixing date) correspond to fields DVALUT and DFAELL in the receiver structure.
It is also possible to use formulas for variable interest rates in conjunction with external data transfer. The system stores the constant and variable interest rates of the variables V1 to V4 in fields PKOND_V1 to PKOND_V4 and SZREF_V1 to SZREF_V4 of the receiver structure. All other fields in the detail screen for the formula correspond to identically named fields in the receiver structure.
Check Concept for Security Class Transfer
Different checks are carried out depending on the validation level you have specified :
- Check level O
No checks
- Check level 1
Checks required/optional fields, fixed values, and value tables
- Check level 2
Check of required/optional fields, fixed values and value tables; check against database. The system overrides the mode field (for example, if a record is to be inserted which already exists in the database, the system sets the mode field to 'U').
- Check level 3
Check of required/optional fields, fixed values and value tables; check against database. The system does not override mode field (for example, if a record is to be inserted which is already in the database, the system does not change the mode field. Instead, the system displays an error message and marks the record in question as erroneous).
Restrictions
In comparison with online entry, it is no longer possible to specify more than two secondary indices, to maintain more than one partial payment for a stock, to create right of notice for classes, or to make entries in the note book.
Further Notes
The security class data is grouped in Corporate Finance Management under the business object Financial Product. This business object provides the BAPIs (Business Application Interfaces) BAPI_FP_CREATEFROMDATA and BAPI_FP_CHANGE, which you can use to create or change class data. From Banking Release 4.62, you can use these BAPIs as an alternative to the data transfer of security class data.
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_CGJB01JBLC22 | 0 | I070004706 | External Data Transfer |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20020204 |
| SAP Release Created in |
