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_CGJB01JBLC21 | Transfer Category 029: Listed Derivatives Class Data |
| Transaction Code | S_ABA_72000051 | IMG Activity: SIMG_CGJB01JBLC21 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC21 | Transfer Category 029: Class Data - Listed Derivatives |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC21 |
Receiver Structure
The receiver structure is comprised of the following parts:
- Class data
- Mode field
Classes are transferred in a single, flat data record. Only the class number (RANL) is required for positive identification. You must assign this number externally, that is, you must set the number range for the respective product type to 'external'.
The mode field controls whether the class is created (MODE='I') or changed (MODE = 'U').
Check Concept for Transfer of Class Data for Listed Derivatives
The system carries out different checks depending on the check-level you specify:
- 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 supposed to be inserted, but already exists in the database, the system changes 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 the mode field (for example, if a record is supposed to be inserted, but already exists 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.
Special Notes
- Assignment of exchanges
In order to maintain the stock price for a class in a particular exchange, you must assign the exchange to the class. This can be done in the online transaction for each exchange.
In an external data transfer, a class is always assigned all available exchanges. If the class is updated, it will be reassigned to all exchanges.
- Number assignment
External number assignment is obligatory for class data. The number range assigned to the product type must therefore be external.
Make sure that the class number is delivered with leading zeros.
Further Notes
The listed derivative 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 class data for listed derivatives.
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_CGJB01JBLC21 | 0 | I070004706 | External Data Transfer |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20020204 |
| SAP Release Created in |
