| Status | Revision in Progress |
|---|---|
| Owner | VIDWANS-ext, Sauradh |
| Stakeholders |
Purpose
T
The purpose of this document is to define the conversion approach to create Bond Transactions in S/4 HANA.
Bond are Debt Instruments where the company borrow funds from the market by Issuing Bonds. Bonds are either issued at Par i.e. 100% of the value of the bonds, or at Discount i.e for eg 98% of the value or at Premium i.e. 102% of the value of the Bond. The Premium or Discount on the Bond is amortized over the life of the Bond.
These instruments are create under a certain Product Type (Instrument Number) and a Transaction Type (Kind of action i.e. buying or selling) against a counterparty (BP Number) in a Company Code for a Security ID and held in a Security Account.
For loading Bonds, SAP has provided a standard BAPI which will have all the necessary fields for successful creation of Bonds. The said BAPI has various Sub-Sections which will form a Load Template and a mapping rule between the DCT and BAPI load format.
BAPI Name : BAPI_FTR_SECURITY_CREATE
Key Fields of the BAPI used in the DCT are as under:
Key Field | Description |
COMPANY_CODE | Company Code in which this deal must be created. |
PRODUCT_TYPE | This is the Product Type for which the deal needs to be created. |
TRANSACTION_TYPE |
|
PARTNER | This is the counterparty with which the deal is booked. However there needs to be a check table which needs conversion between Quantum BP number vs SAP BP Number. |
CONTRACT_DATE |
|
TRADER | This defines the trader who concluded the deal. |
PORTFOLIO | This is a code to be used for bucketing these deals under the same kind of transactions. It is used for reporting purposes. |
VALUATION_CLASS | This defines the Valuation Class under which this deal needs to be Accounted for i.e. IFRS, US GAAP, etc. |
Security Class ID Number | This is the name of Security in itself. In our Case it can be Stock Held External Companies or Stock held in subsidiaries. There will be separate Security Classes for this. |
Securities Account | This is the Depository Account that will hold the equity shares for investment. |
Position Value Date | This is the Value Date on which the position is valued at |
Calculation Date | This is the Calculation Date for Accrued Interest Calculation |
Nominal Amount | This is the Amount invested to buy the given Equity Shares of Entities. |
Characteristics | This field holds the Legacy Quantum Deal Number |
Conversion Scope
The scope of this document covers the approach for converting active Bonds from Legacy Source System (Quantum) into S/4HANA. The relevancy criteria is not applicable for this object as the relevant data will be provided by business in a DCT (Data Collection Template).
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
Quantum | Live Bond Investment Contracts | 100 <TBC> | S4HANA | 100 <TBC> |
Additional Information
Multi-language Requirement
Document Management
Legal Requirement
Special Requirements
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
Data Cleansing
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
| Req # | Requirement Description | Team Responsible |
|---|---|---|
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
Transformation
The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in
- Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation
Transformation Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram) | |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.