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_CGJB01JBLC10 | Transfer Category 008: Security Order |
| Transaction Code | S_ABA_72000079 | IMG Activity: SIMG_CGJB01JBLC10 |
| Created on | 19990121 | |
| Customizing Attributes | SIMG_CGJB01JBLC10 | Transfer Category 008: Security Order |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CGJB01JBLC10 |
General Information about the Transfer Category 'Security Order'
Security orders can be transferred to the SAP Banking data pool using receiver structure JBIUWPO. Note, however, that this transfer category is relevant only for SAP Banking customers who use the data pool exclusively, and are not using the SAP Treasury and Risk Management (TRM) component.
Receiver structure
The data transfer supplies data to the following tables:
- VWBEKI Security order (header)
- VWBEPI Security order (item)
- VWORDE Security order (historical order data)
The receiver structure is composed of the following parts:
- Header
- Item
- Additional flow
- Mode field
For each data record imported into SAP Banking, only one of the three parts 1, 2 or 3, may be filled. The mode field must always be filled.
Example
Receiver structure Header Item Additional flow Mode field
Data record (order 1) X X
Data record X X
Data record X X
Data record X X
Data record (order 2) X X
and so on.
Header and Item Structure
An order involves at least two data records. For each order, you must first transfer a header data record and an item. As many additional flows may be transferred as desired (charges, for example).
An order always has to be complete, regardless of whether you are creating or changing one (by complete we mean with header, items, and all additional flows). It is not possible to transfer individual additional flows seperately without the corresponding order.
Normal Procedures
- A security order is identified by the keys BUKRS (company code) and NORDEXT (external order number).
- Each order refers to exactly one class (security ID number). A product type is preset by the class.
- External data transfer sequence
For each order, the header data record must be transferred first, and then the corresponding items. The additional flows follow.
- Identifying headers, items, and additional flows for orders
SAP Banking uses the contents of selected fields in the receiver structure to identify headers, items, and additional flows:
Filled fields Meaning Derivation
RANL/RLDEPO Security ID number/account Header
SBEWART Flow type (category buy/sell) Item
SBEWART Flow type (no buy/sell) Additional flow
Derivation is linked to a check to ensure that a filled security ID number and security account number together characterize a header data record only when the flow type is not filled at the same time (similar to deriving an item data record).
- Mode field (MODE)
Header, items, and additional flows all have to be sent in the same mode (I = insert; U = update). For example, to change the additional flow of an order, the header, the item, and the additional flow have to be transferred with MODE = U.
- Reversal record
Reversal records are exceptions to the header/item principle. You must transfer a single data record, which contains the identification of the order (BUKRS and NORDEXT), the reversal record indicator (SSTORNO =1), and the mode field (MODE =I).
Required/Optional Fields
The following amount fields and currency fields can be transferred, or completed automatically by the system:
Class is unit-quoted
- ASTUECK Number of units (required field)
- KWKURS Price (required field)
Security price per item - SRUNIT Unit (optional field)
Currency of the security price. If the field is not filled, the system first takes the price currency SSWHR. If SSWHR is not filled, then the system takes the issue currency. - SSWHR Price currency (optional field)
If the field is not filled, the system takes the issue currency. - BSWHR Price amount (optional field)
Amount in price currency. If the field is not filled, the amount is calculated from the price (KWKURS) and the number of units (ASTUECK). - SCWHR Settlement currency (optional)
If the field is not filled, the system takes the issue currency.
- BCWHR Settlement amount (optional field)
Amount in settlement currency. If the field is not filled, the amount is calculated from the amount in price currency (BSWHR) and the exchange rate between SSWHR and SCWHR according to table TCURR. The exchange rate is stored in KURS1.
- SBWHR Postion currency (optional field)
If the field is not filled, the system takes the issue currency. - BBWHR Amount in postion currency (optional field)
If the field is not filled, the amount is calculated from the settlement amount (BCWHR) and the exchange rate between SCWHR and SBWHR according to table TCURR. - BHWHR Amount in local currency (optional field)
If the field is not filled, the amount will be calculated from the settlement amount (BCWHR) and the exchange rate between SCWHR and the local currency according to table TCURR. The exchange rate is stored in KURS2.
Class is percentage-quoted
- BNWHR: Nominal amount (required field)
Always in issue currency - PWKURS Security price (required field)
- SNWHR Currency of nominal amount (optional field)
Is automatically completed by the system. Must be either initial or the same as the issue currency. - SBWHR Position currency (optional)
Is automatically completed by the system. Must be either initial or the same as the issue currency. - BBWHR Amount in postion currency (optional field)
If the field is not filled, the amount is calculated from the nominal amount (BNWHR) and the price (PWKURS). - SCWHR Settlement currency (optional field)
If the field is not filled, the system takes the issure currency.
- BCWHR Settlement amount (optional field)
Amount in settlement currency. If the field is not filled, the amount is is calculated from the amount in price currency (BSWHR) and the exchange rate between SSWHR and SCWHR according to table TCURR. The exchange rate is stored in KURS1.
- BHWHR Amount in local currency (optional field)
If the field is not filled, the amount is calculated from the settlement amount (BCWHR) and the exchange rate between SCWHR and the local currency according to table TCURR. The exchange rate is stored in KURS2.
Additional flows
- BSWHR Price value (required field)
Payment amount of additional flow - SSWHR Price currency (required field)
Currency of the payment amount. Can only be settlement currency (SCWHR) or issue currency. - SBWHR Position currency (optional field)
Automatically completed by the system. Must be either initial or the same as the issue currency. - BBWHR Amount in position currency (optional field)
If the field is not filled, the amount is calculated from the settlement currency (BCWHR) and the exchange rate between SCWHR and the position currency (SBWHR) according to table TCURR. - BCWHR Settlement amount (does not have to be transferred)
Amount in settlement currency. Is automatically calculated from the amount in price currency (BSWHR) and the exchange rate between the price currency (SSWHR) and settlement currency (SCWHR) according to table TCURR. The exchange rate is stored in KURS1.
- SCWHR Settlement currency (optional field)
If the field is not filled, the system takes the issue currency. - BHWHR Amount in local cuurency (optional field)
If the field is not filled, the amount is calculated from the settlement amount (BCWHR) and the exchange rate between the settlement currency (SCWHR) and the local currency according to table TCURR. The exchange rate is stored in KURS2.
In cases where position flows are generated based on a position value that is read (for example, when creating a position change), proceed with utmost care. The system always reads the most current position value on the database (including all of the orders on the database). This means that orders that are being processed in the same block as the position change are not included in the position value. If a position value is changed afterwards (for example, backdated orders), the position flows generated from the original position value will not be changed. In this case you would have to retransfer the relevant position change in update mode, or reverse the record and create it anew. Thus, it is important that you import corporate actions, such as split functions, in a separate transfer run after the orders.
Creation of Foreign Currency and Security Floating Average Prices
Forex a
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_CGJB01JBLC10 | 0 | I070004706 | External Data Transfer |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 19990928 |
| SAP Release Created in |
