| Status | |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Stock Transactions in S/4 HANA.
Stock are equity investments where the company acquires shares of entities. These entities can be either subsidiaries or external companies that are either listed on the stock exchange or closely held. Such investments will have an investment value as part of the Units or number of shares purchased at a given rate per share.
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.
Conversion Scope
The scope of this document covers the approach for converting active Stocks 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 | Active Stock Investment Contracts | 100 <TBC> | S4HANA | 100 <TBC> |
Additional Information
Multi-language Requirement
Not Applicable
Document Management
Not Applicable
Legal Requirement
Not Applicable
Special Requirements
As the conversion involves a source system which is non-SAP, the below area needs special handling:
- Extraction of Stock data from source system i.e. Quantum is to be done manually
- Cleansing by business team in the source system (Quantum) to ensure that only active and in use records for Stocks are provided in DCT
- The extracted records to be converted into a DCT and stored in the Syniti for Transformation
- Below Configuration Check Tables needs to be referenced in Syniti to validate the data in the DCT:
- Counterparty to Business Partner - BUT000
- Company Code - T001
- Product Type - TZPA
- Transaction Type - AT10
- Trader - TZDEA
- Portfolio Code - TWPOB
- General Valuation Class - TRGC_COM_VALCL
- Security Account – TWD01
- Security ID – VWPANLA
- Amount and date format from source system to align with S4HANA
- As the target structure in S4HANA involves dependency on various Configuration and BP Master Data objects (CNV 3040), all this data needs to be loaded before Transactions Data loads.
Target Design
For a Transaction Load DCT, since there are no standard LTMC objects that we can use for loading this data, we will be using BAPI’s for this purpose. In a BAPI there are multiple fields, off which all are not necessary to be utilized as part of DCT.
In this section, we will see the full list of fields that are part of the BAPI and DCT. This section will also explain field by field mapping of the BAPI structure and where the data will come from for each field for the BAPI.
The technical design of the target for this conversion approach.
| Table Name | Field | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|
| VTBFHA | BUKRS | COMPANY_CODE | CHAR | 4 | This is a Required Field |
| VTBFHA | RFHA | TRANSACTION NUMBER | CHAR | 10 | This is Internal Field |
| VTBFHA | SGSART | PRODUCT_TYPE | CHAR | 3 | This is a Required Field |
| VTBFHA | SFHAART | TRANSACTION_TYPE | CHAR | 3 | This is a Required Field |
| VTBFHA | KONTRH | PARTNER | CHAR | 10 | This is a Required Field |
| VTBFHA | DBLFZ | CONTRACT_DATE | DATS | 8 | This is a Required Field |
| VTBFHA | RPORTB | PORTFOLIO | CHAR | 10 | This is a Required Field |
| VTBFHA | ZUOND | ASSIGNMENT | CHAR | 18 | This is Optional Field |
| VTBFHA | REFER | INTERNAL_REFERENCE | CHAR | 16 | This is Optional Field |
| VTBFHA | MERKM | CHARACTERISTICS | CHAR | 25 | This is Required Field |
| VTBFHA | FACILITYBUKRS | VALUATION_CLASS | NUMC | 4 | This is a Required Field |
| VTBFHA | RANL | SECURITY_ID | CHAR | 13 | This is a Required Field |
| VTBFHA | RLDEPO | SECURITY_ACCOUNT | CHAR | 10 | This is a Required Field |
| VTBFHAPO | BUKRS | COMPANY_CODE | CHAR | 4 | This is a Required Field |
| VTBFHAPO | RFHA | TRANSACTION NUMBER | CHAR | 10 | This is Internal Field |
| VTBFHAPO | RFHAZU | Transaction Activity | NUMC | 5 | This is Internal Field |
| VTBFHAPO | DCRDAT | ENTERED ON | DATS | 8 | This is Internal Field |
| VTBFHAPO | TCRTIM | ENTRY TIME | TIMS | 6 | This is Internal Field |
| VTBFHAPO | RFHAZB | TRANSACTION FLOW | NUMC | 4 | This is Internal Field |
| VTBFHAPO | DBESTAND | POSITION_VALUE_DATE | DATS | 8 | This is a Required Field |
| VTBFHAPO | BNWHR | NOMINAL_AMOUNT | DEC | 23 | This is a Required Field |
| VTBFHAPO | ASTUECK | NUMBER_UNITS | DEC | 15 | This is a Required Field |
| VTBFHAPO | WZBETR | PAYMENT_CURRENCY | CHAR | 5 | This is a Required Field |
| VTBFHAPO | DZTERM | PAYMENT_DATE | DATS | 8 | This is a Required Field |
| VTBFHAPO | BZBETR | PAYMENT_AMOUNT | DEC | 23 | This is a Required Field |
| VTBFHAPO | RHANDPL | EXCHANGE | CHAR | 10 | This is Optional Field |
| VTBFHAZU | BUKRS | COMPANY_CODE | CHAR | 4 | This is a Required Field |
| VTBFHAZU | RFHA | TRANSACTION NUMBER | CHAR | 10 | This is Internal Field |
| VTBFHAZU | RFHAZU | TRANSACTION ACTIVITY | NUMC | 5 | This is Internal Field |
| VTBFHAZU | RDEALER | TRADER | CHAR | 12 | This is Optional Field |
| VTBFHAZU | NORDEXT | EXTERNAL_REFERENCE | CHAR | 16 | This is Optional Field |
The DCT Target fields are based on below main Treasury Tables:
- VTBFHA
- VTBFHAPO
- VTBFHAZU
The primary linkage between the tables are Company Code and Deal Number (RFHA). In addition to this, Characteristics Field will be used to link up Quantum Data with SAP as a primary key. Each SAP deal will correspond to the Quantum Deal.
In the above table we saw fields in the DCT.
Data Cleansing
For the Object 9109 – Treasury Stocks no specific data cleansing is applicable due to below reasons/assumptions:
- The Source System is Quantum and therefore it will be a manual extract of relevant data in a DCT form
Data- Pre Load Validation Report
However, for the purpose of the object 3040 - Business Parter Counterparty, below validations reports should be available in Syniti so that the data as provided in DCT is validated before generating the pre-load file.
Criticality | Error Message/Report Description | Rule | Output |
|---|---|---|---|
High | Company Code is valid | Check if BUKRS is valid as per Company Codes created in the system in Table T001 | Invalid Company Code |
High | PRODUCT_TYPE | Check if VVSART is valid as per Product Types created in the system in Table TZPA. | Invalid Product Type |
High | TRANSACTION_TYPE | Check if SFHAART is valid as per Transaction Types created in the system in Table AT10 | Invalid Transaction Type |
High | PARTNER | Check if KUNNR is valid as per Business Partners created in the system under CNV 3040 Business Partner Counterparty | Invalid Partner |
High | CONTRACT_DATE | Check if DVTRAB is valid in YYYYMMDD Format and is < or = Load Date | Contract Date greater than Load Date |
High | PORTFOLIO | Check if RPORTB is valid as per Portfolio Code created in the system in Table TWPOB | Invalid Portfolio Code |
High | VALUATION_CLASS | Check if TPM_COM_VAL_CLASS is valid as per Company Codes created in the system in Table TRGC_COM_VALCL | Invalid Valuation Class |
High | SECURITY_ID | Check if VVRANLW is valid as per Security ID created in the system in Table VWPANLA | Invalid Security ID |
High | SECURITY_ACCOUNT | Check if VRLDEPO is valid as per Security Account created in the system in Table TWD01 | Invalid Security Account |
High | POSITION_VALUE_DATE | Check if DBESTAND is valid in YYYYMMDD Format and is > or = Contract Date | Position Value date greater than Contract date |
High | PAYMENT_DATE | Check if DVALUT is valid in YYYYMMDD Format and is > or = Contract Date | Payment date greater than Contract date |
Apart from the above, a custom report is required to be created for this. The report needs to have row reference for each STOCK loaded under this CNV and display the standard BAPI return messages successful as well as failed. This will make sure all the deposits successfully pass all checks. An additional check is needed if
- All dates loaded are correctly transformed into the deals created
- Payment Details are not going blank and if yes, the BAPI will return a warning for the same. If this warning appears, it will signify the BP Master Maintenance has been missed. Such records must fail and the maintenance needs to be done at the BP Master.
Conversion Process
The generic high-level process steps for the conversion are as below:
- Extraction:
- Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
- DCT: The DCT to be prepared if the data to be transformed and is part of the load file is not available in the Source system
- Transform
- Transform fields by applying the fields and value mapping in the Syniti
- Generate and validate Pre-load files
- Load
- Load the validated Pre-load file using SAP's LTMC or the custom upload program as applicable.
However, with respect to Object 9109 – Treasury Stocks DCT will be used for transformation and generation of the pre-load file.
Data Privacy and Sensitivity
Not Applicable
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 |
|---|---|---|
01 | Extract from relevant tables/reports from Quantum all relevant information required to populate the DCT for Treasury Stocks for relevant Company Codes. This extraction is dependent on the extraction, validation and load of Master Data Object CNV 3040 BP Master, CNV 1184 Security Class and CNV 1185 Security Account. It is also dependent on completion of configuration for items like Company Code, Product Type, Transaction Type, Portfolio Codes, General Valuation Class. | Business |
Selection Screen
Not applicable as the extraction is manual activity to be performed by business in Quantum system.Data Collection Template (DCT)
Target Ready Data Collection Template will be created for 9109 – Treasury Stocks with exception of some fields which require transformation as mentioned in the transformation rule.
9109 – Treasury Stocks DCT Rules
| Field Name | Field Description | Data Type | Length | Rule |
|---|---|---|---|---|
BUKRS | COMPANY_CODE | Same as Target Design | This is a Required field. This data will be captured by business. It is the Company Code under which a Stock is to be created. In DCT, S4HANA number to be populated based upon the list of Company Codes. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Validation check needs to be done with check table T001 | |
SGSART | PRODUCT_TYPE | Same as Target Design | This is a Required field. This data will be captured by business. It is the Product Type under which a Stock is to be created. In DCT, S4HANA number is defaulted to “EAP”. Validation check needs to be done with check table TZPA | |
SFHAART | TRANSACTION_TYPE | Same as Target Design | This is a Required field. This data will be captured by business. It is the Transaction Type under which a Stock is to be created. In DCT, S4HANA number is defaulted to “100”. Validation check needs to be done with check table AT10 | |
KONTRH | PARTNER | CHAR | 20 | This is a Required field. This data will be captured by business for Counterparties. A validation is needed to check the BP number captured in the DCT is valid one and is present as per CNV 3040 - Business Partner Counterparty. Validation check needs to be done with check table BUT100 |
DBLFZ | CONTRACT_DATE | Same as Target Design | This is a Required field. Date format is YYYYMMDD. Contract Date will always be LESS Than the Load Date. This check needs to be implemented. Example: 99991231 | |
RDEALER | TRADER | Same as Target Design | This is Optional Field. This data will be captured by business. It is the Trader who concludes the Stock. In DCT, S4HANA Trader Code needs to be populated based upon the list of configured Traders. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Validation check needs to be done with check table TZDEA | |
RPORTB | PORTFOLIO | Same as Target Design | This is a Required field. This data will be captured by business. It is the Portfolio Code to bucket all Stock under for reporting purposes.In DCT, S4HANA Portfolio Codes needs to be populated based upon the list of Portfolio's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Validation check needs to be done with check table TWPOB | |
ZUOND | ASSIGNMENT | Same as Target Design | This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. | |
NORDEXT | EXTERNAL_REFERENCE | Same as Target Design | This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. | |
REFER | INTERNAL_REFERENCE | Same as Target Design | This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. | |
MERKM | CHARACTERISTICS | Same as Target Design | This is a Required field. This field will have value for Legacy Quantum Contract Number. | |
FACILITYBUKRS | VALUATION_CLASS | Same as Target Design | This is a Required field. This data will be captured by business. It is the Valuation Class under which a Stock is to be accounted for. In DCT, S4HANA GVC number needs to be populated based upon the list of GVC's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System. | |
RANL | SECURITY_ID | Same as Target Design | This is a Required field. This data will be captured by business for Security ID's. A validation is needed to check the Security ID number captured in the DCT is valid one and is present as per CNV 1184 - Securities Class. Validation check needs to be done with check table VWPANLA | |
RLDEPO | SECURITY_ACCOUNT | Same as Target Design | This is a Required field. This data will be captured by business for Security Accounts. A validation is needed to check the Security Account number captured in the DCT is valid one and is present as per CNV 1185 - Securities Account Validation check needs to be done with check table TWD01 | |
DBESTAND | POSITION_VALUE_DATE | Same as Target Design | This is a Required field Date format is YYYYMMDD. Position Value Date will always be Greater Than the Contract Date. This check needs to be implemented. Example: 99991231 | |
BNWHR | NOMINAL_AMOUNT | Same as Target Design | This is a Required field. This is the amount for which the Stock is created and needs to be provided by business. Amounts needs to be rounded to 2 decimal places. Standard BADI will automatically round it to 2 decimals. However the BAPI will fail if amount is with more than 5 decimals places. Hence a Pre Validation check needs to be created to check the decimal places are correct. | |
ASTUECK | NUMBER_UNITS | Same as Target Design | This is a Required field. This is the number of shares held and needs to be provided by Business This field needs to be populated and the logic is value in this fied should be > 0 | |
WZBETR | PRICE_UNIT | Same as Target Design | This is a Required field. This data will be captured by business. It is the Currency of the Stock Currency Codes are ISO standards hence it will be same in all Treasury systems. Still a Validation check is needed in Syniti to check if a valid Currency Code is used in the DCT | |
DZTERM | PAYMENT_DATE | Same as Target Design | This is a Required field Date format is YYYYMMDD. Payment Date will always be Greater Than the Contract Date. This check needs to be implemented. Example: 99991231 | |
BZBETR | PAYMENT_AMOUNT | Same as Target Design | This is a Required field. This is the amount for which Payment needs to be done and needs to be provided by business. Amounts needs to be rounded to 2 decimal places. Standard BADI will automatically round it to 2 decimals. However the BAPI will fail if amount is with more than 5 decimals places. Hence a Pre Validation check needs to be created to check the decimal places are correct. | |
RHANDPL | EXCHANGE | Same as Target Design | This is a Optional field. This is a freely maintainable field. No validations needed for this field. | |
Extraction Dependencies
For object 9114- Treasury Stocks dependencies are applicable as under
| Item # | Step Description | Team Responsible |
|---|---|---|
0001 | TRM Business Partner | Data Team/Functional Treasury Team |
0002 | TRM Security Class | Data Team/Functional Treasury Team |
0003 | TRM Security ID | Data Team/Functional Treasury Team |
0004 | Treasury Configuration | Functional Treasury Team |
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 |
|---|---|---|
1 | Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti | Data team |
2 | Ensure that signed off value mappings have been maintained in the Syniti | Syniti team |
3 | Confirm the value mappings as maintained in the Syniti | Data team |
4 | Ensure that Signed off CONSTRUCT from business has been received and maintained in Syniti | Syniti/Data team |
5 | Execute transformation for the object | Syniti team |
6 | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Syniti/Data team |
7. | Generate Pre-Load reports. | Syniti team |
8. | Generate data load count. | Syniti team |
9. | Log errors as defects, if any and address resolutions. Close defects. | Syniti/Data team |
10. | Re-transform and re-validate the Pre-load reports if necessary. | Syniti/Data team |
11. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
12. | Analyse and resolve any pre-load defects logged by business. | Syniti/Data team |
13. | Repeat steps 5 to 11 if necessary | Syniti/Data team |
14. | Proceed to pre-load validations | Data team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | BUKRS | COMPANY_CODE | From DCT field "BUKRS” |
| 2 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | RFHA | TRANSACTION NUMBER | Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA |
| 3 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | SGSART | PRODUCT_TYPE | From DCT field "SGSART" |
| 4 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | SFHAART | TRANSACTION_TYPE | From DCT field "SFHAART" |
| 5 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | KONTRH | PARTNER | Step 1 - Compare the BP Number in the DCT with BP XREFF - BPEXT field Step 2 - Find the BP Number for the match BP XREFF - PARTNER Field Step 3 - Pass the BP Number fetched from BP XREFF in table BUT100 to check if Role "TR0151" is assigned to the BP Step 4 - If the condition matches, then replace the BP Number in the DCT field PARTNR |
| 6 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | DBLFZ | CONTRACT_DATE | From DCT field "DBLFZ" |
| 7 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | TB_TVTRAB | CONTRACT_TIME | System Time at the time of Data Load |
| 8 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | RPORTB | PORTFOLIO | From DCT field "RPORTB" |
| 9 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | ZUOND | ASSIGNMENT | From DCT field "ZUOND" |
| 10 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | REFER | INTERNAL_REFERENCE | From DCT field "REFER" |
| 11 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | MERKM | CHARACTERISTICS | From DCT field "MERKM" |
| 12 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | TB_DCRDAT | ENTRY_DATE | Date on which the data is getting loaded. |
| 13 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | FACILITYBUKRS | VALUATION_CLASS | From DCT field "FACILITYBUKRS” |
| 14 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | RANL | SECURITY_ID | From DCT field "RANL" |
| 15 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHA | RLDEPO | SECURITY_ACCOUNT | From DCT field "RLDEPO" |
| 16 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | BUKRS | COMPANY_CODE | From DCT field "BUKRS” |
| 17 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | RFHA | TRANSACTION NUMBER | Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA |
| 18 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | RFHAZU | Transaction Activity | Internal Field generated by SAP. Use Internally generated Sequential Number |
| 19 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | DCRDAT | ENTERED ON | Internal Field generated by SAP. Use System Date while you generate your report |
| 20 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | TCRTIM | ENTRY TIME | Internal Field generated by SAP Use System Time when you generate your report. |
| 21 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | RFHAZB | TRANSACTION FLOW | Internal Field generated by SAP. Use Internally generated Sequential Number |
| 22 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | DBESTAND | POSITION_VALUE_DATE | From DCT field "DBESTAND" |
| 23 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | BNWHR | NOMINAL_AMOUNT | From DCT field "BNWHR" |
| 24 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | ASTUECK | NUMBER_UNITS | From DCT field "ASTUECK" |
| 25 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | DZTERM | PAYMENT_DATE | From DCT field "DZTERM" |
| 26 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | WZBETR | PAYMENT_CURRENCY | From DCT field "WZBETR" |
| 27 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | BZBETR | PAYMENT_AMOUNT | From DCT field "BNWHR" |
| 28 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAPO | RHANDPL | EXCHANGE | From DCT field "RHANDPL" |
| 29 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAZU | BUKRS | COMPANY_CODE | From DCT field "BUKRS” |
| 30 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAZU | RFHA | TRANSACTION NUMBER | Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA |
| 31 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAZU | RFHAZU | TRANSACTION ACTIVITY | Internal Field generated by SAP. Use Internally generated Sequential Number |
| 32 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAZU | RDEALER | TRADER | From DCT field "RDEALER" |
| 33 | NA | NA | NA | CONSTRUCT | S4HANA | VTBFHAZU | NORDEXT | EXTERNAL_REFERENCE | From DCT field "NORDEXT" |
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Business Partner | Mapping Table for Quantum counterparty/partner code to S4HANA Business Partner |
Security Class | Mapping Table for Quantum Security Numbers to S4HANA Security Class |
Security Account | Mapping Table for Quantum Depository Account to S4HANA Security Account |
Transformation Dependencies
List the steps that need to occur before transformation can commence
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti | Data team |
2 | Ensure that signed off value mappings have been maintained in the Syniti | Syniti team |
3 | Confirm the value mappings as maintained in the Syniti | Data team |
4 | Ensure that Signed off DCT from business has been received and maintained in Syniti | Syniti/Data team |
5 | Confirm on the extracted values | Syniti, Data and business |
Pre-Load Validation
Project Team
The Pre Load validations are performed by Project TeamCompleteness
| Task | Action |
|---|---|
Generation of | Mandatory field check.
|
Record Count | Record Count Confirm the record counts in preload summary report
|
Business Confirmation | Data team after the initial validation of Pre-Load validation based on the pre agreed validation checklist To send the Pre-Load file to the Business Representatives for all plants/valuation area in scope for conversion Business Representatives to validate the pre-load file Agree with data team on the next steps for erroneous records |
Accuracy
| Task | Action |
|---|---|
Mandatory field mapping and transformation | Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.
|
Business Value Checks | All dates, Amount and Interest Rate for the Stocks are accurately populated in the deal as per DCT. |
Records in Errors | Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data. |
Business
The following pre-load validations will be performed by business.
Completeness
| Task | Action |
|---|---|
Check Data load register count | Business Data Owner/s to verify that the total number of relevant records to be converted as per DCT is equal to the total number of records in the Preload file. |
Key Fields Check | Business to check some key fields such as validity end date, Start an End Date, Amount, Interest Rate, etc., are correctly populated against the DCT |
Accuracy
| Task | Action |
|---|---|
Conversion accuracy | To check and validate the load files with all the transformation and mapping rules, to be signed off. |
Load
As explained earlier, there are 2 subsections of the BAPI which needs to be loaded in the system. Below are the details how data from DCT correspond to the BAPI structure.
However, the transformation is also needed for the base DCT Fields which will have table details. In the below sections you will find 2 kinds of information i.e. the Value Fields in the BAPI and also the overall BAPI fields and how they are transformed.
BAPI Main Flow Data Structure:
| Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|
| BAPI_FTR_SECURITY_CREATE | BUKRS | COMPANY_CODE | From DCT field "BUKRS” |
| BAPI_FTR_SECURITY_CREATE | VVSART | PRODUCT_TYPE | From DCT field "SGSART" |
| BAPI_FTR_SECURITY_CREATE | TB_SFHAART | TRANSACTION_TYPE | From DCT field "SFHAART" |
| BAPI_FTR_SECURITY_CREATE | TB_KUNNR_NEW | PARTNER | From DCT field "KONTRH" |
| BAPI_FTR_SECURITY_CREATE | TB_DVTRAB | CONTRACT_DATE | From DCT field "DBLFZ" |
| BAPI_FTR_SECURITY_CREATE | TB_TVTRAB | CONTRACT_TIME | System Time at the time of Data Load |
| BAPI_FTR_SECURITY_CREATE | RDEALER | TRADER | From DCT field "RDEALER" |
| BAPI_FTR_SECURITY_CREATE | RPORTB | PORTFOLIO | From DCT field "RPORTB" |
| BAPI_FTR_SECURITY_CREATE | TB_ZUOND | ASSIGNMENT | From DCT field "ZUOND" |
| BAPI_FTR_SECURITY_CREATE | TB_NORDEXT | EXTERNAL_REFERENCE | From DCT field "NORDEXT" |
| BAPI_FTR_SECURITY_CREATE | TB_REFER | INTERNAL_REFERENCE | From DCT field "REFER" |
| BAPI_FTR_SECURITY_CREATE | TB_MERKM | CHARACTERISTICS | From DCT field "MERKM" |
| BAPI_FTR_SECURITY_CREATE | TB_DCRDAT | ENTRY_DATE | Date on which the data is getting loaded. |
| BAPI_FTR_SECURITY_CREATE | TPM_COM_VAL_CLASS | VALUATION_CLASS | From DCT field "FACILITYBUKRS” |
| BAPI_FTR_SECURITY_CREATE | VVRANLW | SECURITY_ID | From DCT field "RANL" |
| BAPI_FTR_SECURITY_CREATE | VRLDEPO | SECURITY_ACCOUNT | From DCT field "RLDEPO" |
| BAPI_FTR_SECURITY_CREATE | TB_DBESTAND | POSITION_VALUE_DATE | From DCT field "DBESTAND" |
| BAPI_FTR_SECURITY_CREATE | BAPITM_BNWHR | NOMINAL_AMOUNT | From DCT field "BNWHR" |
| BAPI_FTR_SECURITY_CREATE | TB_ASTUECK | NUMBER_UNITS | From DCT field "ASTUECK" |
| BAPI_FTR_SECURITY_CREATE | DVALUT | PAYMENT_DATE | From DCT field "DZTERM" |
| BAPI_FTR_SECURITY_CREATE | BAPITM_BZBETR | PAYMENT_AMOUNT | From DCT field "BNWHR" |
| BAPI_FTR_SECURITY_CREATE | VVRHANDPL | EXCHANGE | From DCT field "RHANDPL" |
Now we will check the fields in the BAPI and the data logic how it will correspond to the DCT.
This BAPI has a simulation run provision. As part of the Pre-Load check when all the Syniti ADMM checks are performed, before making the production run of all the Stocks, a simulation run should be performed and all the standard BAPI errors needs to be documented.
A custom report, if required needs to be created for this. The report needs to have row reference and display the standard BAPI return messages successful as well as failed. This will make sure all the deposits successfully pass all checks.
Note: It is also assumed that the DCT will not bring in Payment Details of Stocks. This information will be loaded as part of CNV 3040 – Business Partner Counterparty and CNV . Under this CNV1185 – Security Account, Payment SI details are created and assigned to this instrument. If this is done, once the BAPI is executed, it will automatically get assigned to the deal as part of Standard BAPI processing. A Data Pre-Validation check has been introduced for this step.
The load process includes:
- Execute the automated data load into target system using "BAPI_FTR_SECURITY_CREATE" and use the DCT File vs structure section of this document to populate the BAPI details.
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE)
Load Run Sheet
Item # | Step Description | Team Responsible |
|---|---|---|
01 | Go to load file and pick 5 data records, load manually without any tool. See what happens. If all okay, proceed with the next step. | Data team |
02 | Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay. | Data team |
03 | Proceed with the full load if steps one and two were succeed else fix the issue with records | Data team |
04 | Validate few records loaded by accessing standard transactions from S/4HNA e.g. FTR_EDIT or check in the tables - VTBFHA, VTBFHAZU or VTBFHAPO | Data team |
05 | Generate post load report if step 5 is validated | Data team |
06 | Log errors as defects, if any and address resolutions. Close defects. | Data team |
07 | Resolve defects by reupload and re-generate post load reports if necessary. | Data team |
08 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
09 | Repeat steps 1 to 5 if necessary. | Data team |
Load Phase and Dependencies
The load phase for the object 9109-Treasury Stocks is Pre-Cutover Phase 3
Configuration
Item # | Configuration Item |
|---|---|
01 | Company Codes relevant for Treasury- Field BUKRS (Check Table: T001) |
02 | Treasury Business Partners - BUT100 |
03 | House Bank Ids- Field HKTID (Check Table: T012K) |
04 | Payment Methods- Field ZLSCH (Check Table: T042Z) |
05 | Contract Type - Field RANTYP |
06 | Product Category- Field SANLF (Check Table: TZAF) |
07 | Product Type- Field SGSART (Check Table: TZPA) |
08 | Financial Transaction Types- Field SFHAART (Check Table: AT10) |
09 | Portfolio Code - Check Table: TWPOB |
10 | General Valuation Class - Check Table: TRGC_COM_VALCL |
11 | Security Class – Check Table : VWPANLA |
12 | Security Account – TWD01 |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
CNV-3007 | Business Partner - General Role |
CNV-1083 | Bank Master |
CNV-1184 | Security Class |
CNV-1185 | Security Account |
CNV-3040 | Business Partner - Counterparty |
CNV-1203 | Business Partner - Depository |
Error Handling
The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management
Error Type | Error Description | Action Taken |
|---|---|---|
Valid Master | Business Partner is not having a valid treasury role i.e. TR0151 | Ensure that Business Partner is updated with correct role |
Invalid Company Code | Company Code in the DCT is invalid based on the check table T001 | Ensure correct Company Code is supplied to the BAPI |
Invalid Product Type | Product Type in the DCT is invalid based on the check table TZPA | Ensure correct Product Type is supplied to the BAPI |
Invalid Transaction Type | Transaction Type in the DCT is invalid based on the check table AT10 | Ensure correct Transaction Type is supplied to the BAPI |
Invalid Trader | Trader in the DCT is invalid based on the check table TZDEA | Ensure correct Trader is supplied to the BAPI |
Invalid Portfolio Code | Portfolio Code in the DCT is invalid based on the check table TWPOB | Ensure correct Portfolio Code is supplied to the BAPI |
Invalid Interest Calculation Method | Interest Calculation Method is invalid as per the Custom Check Table | Ensure correct Interest Calculation method is supplied to the BAPI |
Invalid Frequency Category | Frequency Category is invalid as per the Custom Check Table | Ensure correct Frequency Category is supplied to the BAPI |
Post-Load Validation
Project Team
The following post load validations will be done by Project TeamCompleteness
| Task | Action |
|---|---|
Reconciliation of Record Count | Record Count - Count and check how many records were loaded vs. Records in the load file (Each mock has it's own data record count) Check for logs from Load and fix erroneous records, if any. |
Accuracy
| Task | Action |
|---|---|
Check values in key fields for accuracy | Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report. |
Business
The following post load validations will be done by business.Completeness
| Task | Action |
|---|---|
Record Count Check | Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations Business may also run transaction code FTR_EDIT to cross check the records created for Counterparties |
Accuracy
| Task | Action |
|---|---|
Field Checks | Check key fields to ensure that Business Partner - Counterparty has been maintained with proper details such as
|
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- All configuration items like Company Code, Product Type, Transaction Type, etc are approved by business and pre-configured before this data can be loaded
- All Bank Account information is approved by business and loaded in the system. Same are also created as SI details in BP master and assigned to the correct Product Type/Transaction Type combination in the BP master as these will be auto loaded in the deal and will not be part of the DCT.
See also
CNV-3007: Business Partner General - CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base
CNV-3040: Business Partner Counterparty - CNV-3040 Business Partners - Counterparty - SyWay Project - Syensqo - Wiki knowledge base
CNV-1184: Security Class - CNV-1184 Securities Class - SyWay Project - Syensqo - Wiki knowledge base
CNV-1185: Security Account - CNV-1185 Securities Account - SyWay Project - Syensqo - Wiki knowledge base
CNV-1203: Business Partner Depository - CNV-1203: Business Partner Depository - SyWay Project - Syensqo - Wiki knowledge base