| Status | |
|---|---|
| Owner | BAJAJ-ext, Manoj |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create Business Partner - Counterparty (Object 3040) in S/4 HANA.
Counterparty represents organisation or person with whom a Treasury Transaction is being entered. Counterparty is used as an object while creating Transactions/Instruments such as Money Market deals, Foreign Exchange contracts, Securities etc. in Treasury and Risk Management module of S4HANA.
It is therefore created as a Business Partner with the specific role as Counterparty - Role ID TR0151 using the Transaction Code BP. While the General Data such as name, address, contact details, identifications and controls are created like a general BP role i.e. 000000, the Company Code Data will be maintained once the BP Role TR0151 is maintained.
Company Code data under Counterparty Role for a business partner includes the payment details and its assignment to standing instructions, authorisations (by contract/product category/types, transaction types) and derived flows.
The below table explains the Role Matrix, applicable S4HANA tables and related Conversion Objects
| Role | Description | Table | Conversion Object |
|---|---|---|---|
| 000000 | General Role Business Partner Role - General view Customers + Suppliers (including name and address standards, languages, emails, formats, identifications etc.) | BUT000 | CNV-3007 |
| TR0151 | Counterparty Role - assignment to a Business Partner and validity dates | BUT100 | CNV-3040 |
| TR0151 | Counterparty Role - Company Code Data: Payment Details | VTBSTC1 | |
| TR0151 | Counterparty Role - Company Code Data: Assignment of Payment Details as Standing Instructions | VTBSTA1 | |
| TR0151 | Counterparty Role - Company Code Data: Authorisations | VTBSTA3 | |
| TR0151 | Counterparty Role - Company Code Data: Derived Flow | VTBSTA4 |
The key fields for the above mentioned S4HANA tables pertaining to CNV-3040 - Business Partner Counterparty are explained below:
- Table BUT100 - Role assignment:
- PARTNER - Business Partner Number - unique identifier of the Business partner which can be internally assigned by SAP or externally assigned by user. For Intercompany Business Partner, it will be externally assigned. Others will be internally assigned following the number ranges by the groups as specified in the CNV-3007
- RLTYP - Business Partner Role - This field is to select the Partner Role. For Counterparty the role to be used is TR0151
- VALID_FROM - Validity Start of a BP Role
- VALID_TO - Validity End of a BP Role
- Table VTBSTC1 - Counterparty -Company Code Data- Payment Details
- WAERS - Currency Key - Currency for which the payment detail is being maintained
- ZAHLVID - Identification of Payment Details - This ID is created for a currency and is used in the assignment to "standing instructions" in the Table VTBSTA1
- BVTYP - Partner Bank Details - The payment details ID for a business partner. This is also the ID which is referenced in the Security Account Master Data (CNV-1185)
- HBKID - House bank - House bank of the company code
- HKTID - Account Id - Bank Account ID under the House Bank
- ZLSCH - Payment Method - The mode of payment
- SZART - Payment Transaction - Indicator to be selected if the payment is to be made via Customer/Vendor subledger. In this case the BP being extended to Counterparty role should also be created with role FLCU00
- RPZAHL - Payer/payee - Identifies the business partner for payment. Incoming and outgoing payments are settled using this business partner.
- SPAYRQ - Generate Payment Request - This is a checkbox field. This is flagged if a payment request is required to be generated.
- ZWELS - List of Payment Methods - This field is to specify applicable payment methods in case a particular payment method is not specified in the field ZLSCH
- Table VTBSTA1 - Counterparty - Company Code Data- Assignment of Payment Detail IDs to Standing Instructions.
- WAERS - Currency Key - Currency of payment for which the payment detail is being maintained. This along with Company Code and Business partner will be the link with table VTBSTC1
- RANTYP - Contract Type - is a key that identifies/groups products category and its subtypes. The possible entries for a contract type in Treasury modules are:
2 = Securities
4 = Foreign exchange
5 = Money market
T = Trade Finance
- SANLF - Product Category - Product category governs processing logic for each product type used in treasury module
- SGSART - Product Type - a sub key under Product Category which is assigned to a financial transaction in SAP TRM. This is used to further classify a product type, example - Bonds can be Fixed or variable Interest rates bonds
- SFHAART- Financial Transaction Types - The financial transaction type specifies which types of transactions can be carried out with a certain product type, such as
- investment and borrowing of fixed-term deposits,
- deposits at notice,
- purchase and sale of bonds.
- SSIGN - Direction - This is to indicate if the assignment is of incoming or outgoing nature
- ZAHLVID - Identification of Payment Details - This ID is as created in table VTBSTC1 and is assigned to a combination of Contract Type (RANTYP), Product Category (SANLF), Product Type (SGSART) and Financial Transaction Type (SFHAART)
- Table VTBSTA3 - Counterparty -Company Code Data- Authorisations
- This table stores authorisations for transactions related to a counterparty. These authorisations can be defined at multiple levels:
- Contract Type (RANTYP)
- Product Category (SANLF) under a Contract Type
- Product Type (SGSART) under a Product Category
- Transaction Type (SFHAART) under a Product Type
The same field explanations as in table VTBSTA1 apply to VTBSTA3. The field indicating authorisation in the table VTBSTA3 is AUTHOR, This indicator shows that a business partner has been authorized to conclude transactions. The indicator must be viewed in connection with the business partner, the role category, the company code, the contract type, the product category and the product type.
- This table stores authorisations for transactions related to a counterparty. These authorisations can be defined at multiple levels:
Note: The Authorisations being maintained at the Counterparty is not to be assumed as same which have been maintained in the Trader Authorisations (Object-1182)
- Table VTBSTA4 - Counterparty -Company Code Data- Derived Flows
- The table stores derived flows applicable for transactions related to a counterparty. This can be defined at multiple levels:
- Contract Type (RANTYP)
- Product Category (SANLF) under a Contract Type
- Product Type (SGSART) under a Product Category
- Transaction Type (SFHAART) under a Product Type
- The table stores derived flows applicable for transactions related to a counterparty. This can be defined at multiple levels:
The same field explanations as in table VTBSTA1 apply to VTBSTA4. The field indicating Derived flow in the table VTBSTA4 is SABVERF.
Note: For the different sections of the Counterparty-Company Code data, the fields PARTNER (Business Partner Number) and BUKRS (Company Codes) are the common linkage between tables VTBSTC1, VTBSTA1, VTBSTA3 and VTBSTA4.
The treasury function in legacy is carried out in the Quantum system and therefore for the data related to Counterparty will be provided by business in a Data Collection Template (DCT). which will be transformed in Syniti to generate a preload file as the per the to-be S4HANA design. The load will be part of the Business Partner Load (Object 3007) for the General Data and Counterparty- Company Code data using the LTMC <TBC as the available LTMC for Business Partner- Treasury is only Direct Transfer>. The function module is CNV_OT_APPL_FI_TRM_BP_ROLE and the BAPI/API is FTB_BUPA_DARK_MAINTAIN_INTERN.
Conversion Scope
The scope of this document covers the approach for converting active Counterparties from Legacy Source System (Quantum) into S/4HANA following the MDS for Object-3040 - DD-FUN-050 Master Data Standard-3XXX-Consolidated Business Partner.
The relevancy criteria is not applicable for this object as the relevant data will be provided by business in a DCT (Data Collection Template), however as the general data of Counterparties will be part of the object 3007, it needs to be ensured from deduplication perspective.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
Quantum | Active and in use Counterparties | 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 Counterparty 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 Counterparties are provided in DCT
- Separate DCTs to be provided i.e. for General Role and Counterparty Role including the Company Code data
- The extracted records to be converted into a DCT and stored in the Syniti for Transformation
- Below Value mapping tables to be created in Syniti:
- Counterparty to Business Partner
- Source and target company code
- Amount and date format from source system to align with S4HANA
- As the target structure in S4HANA involves dependency on the Object 3007 (Business Partner- General Data), including the Counterparty that may also be an intercompany customer/vendor, all other Roles should have been loaded before Counterparty role
Target Design
The Target design of the object 3040 - Business Partner Counterparty a based on the MDS - DD-FUN-050 Master Data Standard-3XXX-Consolidated Business Partner.
<Note: The target design can change subject to business confirmation of the target design for Treasury Module>
The technical design of the target for this conversion approach for Object 3040- Business Partner - Counterparty is as below:
Table: BUT100 - Counterparty Role TR0151 - assignment to a Business Partner.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| BUT100 | PARTNER | BU_PARTNER | Business Partner Number | CHAR | 10 | Mandatory |
| BUT100 | RLTYP | BU_PARTNERROLE | BP Role | CHAR | 6 | Mandatory |
| BUT100 | VALID_FROM | BU_ROLE_VALID_FROM | Validity Start of a BP Role | DEC | 15 | Mandatory |
| BUT100 | VALID_TO | BU_ROLE_VALID_TO | Validity End of a BP Role | DEC | 15 | Mandatory |
Table: VTBSTC1 - Counterparty Company Code Data - Payment Details
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| VTBSTC1 | PARTNER | BP_PARTNER_NEW | Business Partner Number | CHAR | 10 | Mandatory |
| VTBSTC1 | BUKRS | BUKRS | Company Code | CHAR | 4 | Mandatory |
| VTBSTC1 | WAERS | WAERS | Currency | CUKY | 5 | Mandatory |
| VTBSTC1 | ZAHLVID | TB_ZAHLVID | Identification of Payment Details (Standing Instructions) | CHAR | 10 | Mandatory |
| VTBSTC1 | BVTYP | TB_RPBANK | Partner Bank Details | CHAR | 4 | Conditional |
| VTBSTC1 | HBKID | HBKID | Short key for a house bank | CHAR | 5 | Mandatory |
| VTBSTC1 | HKTID | HKTID | ID for account details | CHAR | 5 | Mandatory |
| VTBSTC1 | ZLSCH | DZLSCH | Payment Method | CHAR | 1 | Mandatory |
| VTBSTC1 | SZART | TB_SZART | Payment Transaction | CHAR | 1 | Not in use |
| VTBSTC1 | RPZAHL | TB_RPZAHL_NEW | Payer/payee | CHAR | 10 | Conditional |
| VTBSTC1 | SPAYRQ | TB_SPAYRQ | Generate Payment Request | CHAR | 1 | Conditional |
| VTBSTC1 | ZWELS | DZWELS | List of Respected Payment Methods | CHAR | 10 | Conditional |
Table: VTBSTA1 - Counterparty Company Code Data - Assignment of Payment Details as Standing Instructions
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| VTBSTA1 | BUKRS | BUKRS | Company Code | CHAR | 4 | Mandatory |
| VTBSTA1 | PARTNR | BP_PARTNER_NEW | Business Partner Number | CHAR | 10 | Mandatory |
| VTBSTA1 | WAERS | WAERS | Currency | CUKY | 5 | Mandatory |
| VTBSTA1 | RANTYP | RANTYP | Contract Type | CHAR | 1 | Conditional |
| VTBSTA1 | SANLF | SANLF | Product Category | NUMC | 3 | Conditional |
| VTBSTA1 | SGSART | VVSART | Product Type | CHAR | 3 | Conditional |
| VTBSTA1 | SFHAART | TB_SFHAART | Financial Transaction Type | CHAR | 3 | Conditional |
| VTBSTA1 | SSIGN | TB_SSIGN | Direction of Flow | CHAR | 1 | Conditional |
| VTBSTA1 | ZAHLVID | TB_ZAHLVID | Identification of Payment Details (Standing Instructions) | CHAR | 10 | Mandatory |
Table: VTBSTA3 - Counterparty Company Code Data - Authorisations
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| VTBSTA3 | BUKRS | BUKRS | Company Code | CHAR | 4 | Mandatory |
| VTBSTA3 | PARTNR | BP_PARTNER_NEW | Business Partner Number | CHAR | 10 | Mandatory |
| VTBSTA3 | RANTYP | RANTYP | Contract Type | CHAR | 1 | Conditional |
| VTBSTA3 | SANLF | SANLF | Product Category | NUMC | 3 | Conditional |
| VTBSTA3 | SGSART | VVSART | Product Type | CHAR | 3 | Conditional |
| VTBSTA3 | SFHAART | TB_SFHAART | Financial Transaction Type | CHAR | 3 | Conditional |
| VTBSTA3 | AUTHOR | TB_AUTHOR | Authorization indicator for Treasury product | CHAR | 1 | Mandatory |
Table: VTBSTA4 - Counterparty Company Code Data - Derived Flows
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| VTBSTA4 | BUKRS | BUKRS | Company Code | CHAR | 4 | Conditional |
| VTBSTA4 | PARTNR | BP_PARTNER_NEW | Business Partner Number | CHAR | 10 | Conditional |
| VTBSTA4 | RANTYP | RANTYP | Contract Type | CHAR | 1 | Conditional |
| VTBSTA4 | SANLF | SANLF | Product Category | NUMC | 3 | Conditional |
| VTBSTA4 | SGSART | VVSART | Product Type | CHAR | 3 | Conditional |
| VTBSTA4 | SFHAART | TB_SFHAART | Financial Transaction Type | CHAR | 3 | Conditional |
| VTBSTA4 | SABVERF | TB_SABVERF | Procedure for Generating Derived Flows | CHAR | 5 | Conditional |
Note - The fields PARTNER and BUKRS are the common fields across the tables associated with maintaining the Company Code data of a Counterparty Business partner as described above.
Data Cleansing
For the Object 3040 - Business Partner 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
- The General Data View of Counterparty will be handled together with the Object 3007 (Business Partner- General) and therefore same de-duplication/cleansing rules will be followed
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.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
| 01 | High | Validity Start Date Check | Check if Business Partner RLTYP Not Equal to Blank, then the validity date start aligns with the available role type | Records showing misaligned validity start date | Not applicable. Check against S4 Configuration/Master Data |
| 02 | Medium | ||||
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 3040- Business Partner Counterparty Master Data - the conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business based on the source data from Quantum system. This DCT will be used for transformation and generation of the pre-load file.
Data Privacy and Sensitivity
Not applicableExtraction
Extract data from a source into Syniti. There are 2 possibilities:
- The data exists. Syniti connects to the source and loads the data into Syniti. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti; 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 Syniti. This is to be conducted using DCT (Data Collection Template) in Syniti.
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
In case of the object 3040- Business Partner Counterparty, the data is to be provided in a DCT by the business, therefore extraction related activity is not carried out via Syniti
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 Counterparties for relevant Company Codes. This extraction is supplement to the general data of Counterparty already prepared for creation as Business Partner General Role [Object-3007 - Business Partners - General (Role 000000)] | 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 3040 - Business Partner Counterparty data in a Data Collection Template (DCT) by business.
This DCT is to be prepared in addition to the DCT containing the General Data such as Name, Address, Contact Details, Payment Information, Identification Numbers etc., which will be provided against the object 3007 - Business Partners - General (Role 000000)
Object 3040- Business Partner Counterparty- DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| BUT100-PARTNER | Business Partner Number | This is a required field. This number is internally generated by the system (will be available once General Role -000000 is created) For Intercompany Counterparty, the BP number is to be assigned externally. |
| BUT100-RLTYP | Business Partner Role | This is a required field. Business Partner that needs to be created as Counterparty should be assigned to role TR0151 |
| BUT100-VALID_FROM | Validity Start of a BP Role | This is a required field. Though the date format is YYYYMMDDHHMMSS, in the DCT provide YYYYMMDD as real value and HHMMSS can be left blank Example: 20250101 |
| BUT100-VALID_TO | Validity End of a BP Role | This is a required field. Though the date format is YYYYMMDDHHMMSS, in the DCT provide YYYYMMDD as real value and HHMMSS can be left blank. If the actual end date is not known, then a generic end date of year 9999 can be provided. Example: 99991231 Note: The end date should not be prior to the cutover/go live date. |
| Counterparty Role - Company Code Data - Payment Details | ||
| VTBSTC1-PARTNER | Business Partner Number | This is a required field. This number is the same as entered for Role extension against field BUT100-PARTNER |
| VTBSTC1-BUKRS | Company Code | This is a required field. The four character Company Code in the S4HANA for which this counterparty is being extended/created |
| VTBSTC1-WAERS | Currency Key | This is a required field. The currency key in which the payment details to be created. The currency key is as per ISO standard. |
| VTBSTC1-ZAHLVID | Identification of Payment Details (Standing Instructions) | This is a required field. The field will be used as Payment Detail ID to be assigned to Standing Instructions. This is a free text field (length: 10 Chars) |
| VTBSTC1-BVTYP | Partner Bank Details | This is a conditional field. This is to be populated only if a Payment Method requires Bank details of the Business partner as maintained in the General Data |
| VTBSTC1-HBKID | Short key for a house bank | This is a required field. House bank of the company code which will be used for the payments to this Counterparty |
| VTBSTC1-HKTID | ID for account details | This is a required field. This is the Bank account ID available under the house bank. DCT to be populated with relevant account ID |
| VTBSTC1-ZLSCH | Payment Method | This is a required field. The payment method determines how payments are to be made, e.g. by check, bank transfer or bill of exchange. DCT to be populated with an appropriate payment method from the available configured values. |
| VTBSTC1-SZART | Payment Transaction | This field is "Not to be used' as per the MDS Leave blank Note: This field is to be used only if posting is made to Customer or Vendor. Not planned to use for Syway. |
| VTBSTC1-RPZAHL | Payer/payee | This is a conditional field. The Payer/Payee ID for payment in case of Incoming and outgoing payments are to be settled using this business partner. This is to be entered if posting is made to Customer or Vendor |
| VTBSTC1-SPAYRQ | Generate Payment Request | This is a conditional field. This is a checkbox field. Put X only if a payment request is to be generated else leave blank |
| VTBSTC1-ZWELS | List of Respected Payment Methods | This is a conditional field. This field is for listing payments methods (from pre-configured values), only to be filed when a specific payment method is not provided against the field: VTBSTC1-ZLSCH (Payment method) |
Counterparty Role - Company Code Data - Assignment of Payment Details as Standing Instructions | ||
| VTBSTA1-BUKRS | Company Code | This is a required field. This number is the same as entered for Role extension against field BUT100-PARTNER |
| VTBSTA1-PARTNR | Business Partner Number | This is a required field. The four character Company Code in the S4HANA for which this counterparty is being extended/created |
| VTBSTA1-WAERS | Currency | This is a required field. The currency key in which the payment details to be created. The currency key is as per ISO standard. |
| VTBSTA1-RANTYP | Contract Type | This is a conditional field The contract type to indicate if this is for Securities, FX etc. To be selected from the available configured values for the Contract Type. Note - This is a conditional field. If populated at Contract Type level, then applies to all the Product categories, product types, transaction types under the said Contract Type. However, can also be selected only at Transaction Type level or product Type level too. For the DCT purpose this must be specified if the Payment details assignment to Standing Instructions is to be at the combination of Contract Type + Product Category + Product Type + Financial Transaction Type. |
| VTBSTA1-SANLF | Product Category | This is a conditional field The Product Categories as available under a contract type. To be selected from the available configured values of Product Category against a Contract Type. Note - This is a conditional field. If populated at Product Category level, then applies to all the product types, transaction types under the said Product Category. For the DCT purpose this must be specified if the Payment details assignment to Standing Instructions is to be at the combination of Product Category + Product Type + Financial Transaction Type |
| VTBSTA1-SGSART | Product Type | This is a conditional field The Product Type as available under a Product Category. To be selected from the available configured values of Product Types against a Product Category. Note - This is a conditional field. If populated at Product Type level, then applies to all the transaction types under the said Product Type. For the DCT purpose this must be specified if the Payment details assignment to Standing Instructions is to be at the combination of Product Type + Financial Transaction Type |
| VTBSTA1-SFHAART | Financial Transaction Type | This is a conditional field The Financial Transaction Type as available under a Product Type. To be selected from the available configured values of Financial Transaction Types against a Product Type For the DCT purpose this must be specified if the Payment details assignment to Standing Instructions is to be at the combination of Contract Type + Product Category + Product Type + Financial Transaction Type |
| VTBSTA1-SSIGN | Direction | This is a conditional field This field to be entered as + for inflow or - for outflow |
| VTBSTA1-ZAHLVID | Payment Details ID | This is a required field Payment Detail ID as created against the VTBSTC1-ZAHLVID is to be entered here as standing instruction against the combination of Contract Type, Product Category, Product Type, Financial Transaction Types as applicable. |
Counterparty Role - Company Code Data - Authorisation | ||
| VTBSTA3-BUKRS | Company Code | This is a required field. This number is the same as entered for Role extension against field BUT100-PARTNER |
| VTBSTA3-PARTNR | Business Partner Number | This is a required field. The four character Company Code in the S4HANA for which this counterparty is being extended/created |
| VTBSTA3-RANTYP | Contract Type | This is a conditional field The contract type to indicate if this is for Securities, FX etc. To be selected from the available configured values for the Contract Type. Note - This is a conditional field. If populated at Contract Type level, then applies to all the Product categories, product types, transaction types under the said Contract Type. However, can also be selected only at Transaction Type level or product Type level too. For the DCT purpose this must be specified if the Authorisation for this Counterparty is to be maintained at the combination of Contract Type + Product Category + Product Type + Financial Transaction Type. |
| VTBSTA3-SANLF | Product Category | This is a conditional field The Product Categories as available under a contract type. To be selected from the available configured values of Product Category against a Contract Type. Note - This is a conditional field. If populated at Product Category level, then applies to all the product types, transaction types under the said Product Category. For the DCT purpose this must be specified if the Authorisation for this Counterparty is to be maintained at combination of Contract Type + Product Category + Product Type + Financial Transaction Type |
| VTBSTA3-SGSART | Product Type | This is a conditional field The Product Type as available under a Product Category. To be selected from the available configured values of Product Types against a Product Category. Note - This is a conditional field. If populated at Product Type level, then applies to all the transaction types under the said Product Type. For the DCT purpose this must be specified if the Authorisation for this Counterparty is to be maintained at combination of Contract Type + Product Category + Product Type + Financial Transaction Type |
| VTBSTA3-SFHAART | Financial Transaction Type | This is a conditional field The Financial Transaction Type as available under a Product Type. To be selected from the available configured values of Financial Transaction Types against a Product Type For the DCT purpose this must be specified if the Authorisation for this Counterparty is to be maintained at combination of Contract Type + Product Category + Product Type + Financial Transaction Type |
| VTBSTA3-AUTHOR | Authorization indicator for Treasury product | This is a required field This is the checkbox field to indicate the authorisation. The value to be populated here is X |
Counterparty Role - Company Code Data - Derived Flow | ||
| VTBSTA4-BUKRS | Company Code | This is a conditional field This number is the same as entered for Role extension against field BUT100-PARTNER This is required to be provided in DCT if any derived flow (automatic flow) need to be generated |
| VTBSTA4-PARTNR | Business Partner Number | This is a conditional field The four character Company Code in the S4HANA for which this counterparty is being extended/created This is required to be provided in DCT if any derived flow (automatic flow) need to be generated |
| VTBSTA4-RANTYP | Contract Type | This is a conditional field The contract type to indicate if this is for Securities, FX etc. To be selected from the available configured values for the Contract Type. Note - This is a conditional field. If populated at Contract Type level, then applies to all the Product categories, product types, transaction types under the said Contract Type. However, can also be selected only at Transaction Type level or product Type level too. For the DCT purpose this must be specified if the derived flow for this Counterparty is to be maintained at the combination of Contract Type + Product Category + Product Type + Financial Transaction Type. |
| VTBSTA4-SANLF | Product Category | This is a conditional field The Product Categories as available under a contract type. To be selected from the available configured values of Product Category against a Contract Type. Note - This is a conditional field. If populated at Product Category level, then applies to all the product types, transaction types under the said Product Category. For the DCT purpose this must be specified if the derived flow for this Counterparty is to be maintained at combination of Contract Type + Product Category + Product Type + Financial Transaction Type |
| VTBSTA4-SGSART | Product Type | This is a conditional field The Product Type as available under a Product Category. To be selected from the available configured values of Product Types against a Product Category. Note - This is a conditional field. If populated at Product Type level, then applies to all the transaction types under the said Product Type. For the DCT purpose this must be specified if the derived flow for this Counterparty is to be maintained at combination of Contract Type + Product Category + Product Type + Financial Transaction Type |
| VTBSTA4-SFHAART | Financial Transaction Type | This is a conditional field The Financial Transaction Type as available under a Product Type. To be selected from the available configured values of Financial Transaction Types against a Product Type For the DCT purpose this must be specified if the derived flow for this Counterparty is to be maintained at combination of Contract Type + Product Category + Product Type + Financial Transaction Type |
| VTBSTA4-SABVERF | Procedure for Generating Derived Flows | This is a conditional field To be populated with a pre-configured value of derived flow against the combination of Contract Type + Product Category + Product Type + Financial Transaction Type, as applicable |
Extraction Dependencies
For object 3040- Business Partner no extraction dependencies is applicable for as the extraction is via DCT and this is Master Data object by nature
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 Syniti 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 Syniti
- 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 |
|---|---|---|---|---|---|---|---|---|---|
01 | NA | NA | NA | CONSTRUCT | S4HANA | BUT100 | PARTNER | Business Partner Number | As per DCT, Check against XREF of Business Partner |
02 | NA | NA | NA | CONSTRUCT | S4HANA | BUT100 | RLTYP | BP Role | TR0151 |
NA | NA | NA | CONSTRUCT | S4HANA | BUT100 | VALID_FROM | Validity Start of a BP Role | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | BUT100 | VALID_TO | Validity End of a BP Role | As per DCT Check the Validity End date is not < Cutover date | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | PARTNER | Business Partner Number | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | BUKRS | Company Code | As per DCT (Should be same as entered for table BUT100) | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | WAERS | Currency Key | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | ZAHLVID | Identification of Payment Details (Standing Instructions) | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | BVTYP | Partner Bank Details | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | HBKID | Short key for a house bank | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | HKTID | ID for account details | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | ZLSCH | Payment Method | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | SZART | Payment Transaction | Leave Blank | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | RPZAHL | Payer/payee | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | SPAYRQ | Generate Payment Request | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTC1 | ZWELS | List of Respected Payment Methods | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | BUKRS | Company Code | As per DCT (Should be same as entered for table BUT100 and VTBSTC1) | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | PARTNR | Business Partner Number | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | WAERS | Currency | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | RANTYP | Contract Type | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | SANLF | Product Category | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | SGSART | Product Type | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | SFHAART | Financial Transaction Type | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | SSIGN | Direction | As per DCT | |
NA | NA | NA | CONSTRUCT | S4HANA | VTBSTA1 | ZAHLVID | Payment Details ID | As per DCT | |
Transformation Mapping
Use the exact name and reference this section in the “Transformation rules” above| 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
The following pre-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
Business
The following pre-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
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
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Configuration
List the Configurations required before loading can commence
| 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
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 |
|---|---|---|
Post-Load Validation
Project Team
The following post-load validations will be performed by the Project Team.Completeness
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
Business
The following post-load validations will be performed by the business.Completeness
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
Accuracy
| Task | Action |
|---|---|
| title | specific details of what and how the task needs to be performed e.g. which reports are being used etc. |
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- Data Object is in scope based on data design and any exception requested by business.
Any additional key assumptions.
See also
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.