| Status | |
|---|---|
| Owner | BAJAJ-ext, Manoj |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to create conversion for Object 1201 - BP Group Assignment for Inbound Correspondence
The primary function of this transaction of this object is to facilitate the assignment of inbound financial messages/ deals (coming from external systems like trading platforms) to existing or new TRM transactions in S/4HANA. This assignment is to a business partner group. This is maintained in the system using Transaction Code FTR_INB_ASSIGN and it is different from the correspondence tab of the BP Counterparty Company Code Data.
This document details out the field list, extraction criteria, scoping, mapping, transformation logic, generation of the pre-load file and loading of the same with respect to the object 1201- BP Group Assignment for Inbound Correspondence, to be used in treasury module of S4HANA.
Key tables and fields:
The main table used for object BP Group Assignment for Inbound Correspondence is TCORT_INB_ASSIGN and its key fields are as below:
- PARTNR - Partner - This denotes the Business Partner Number.
- COMPANY_CODE - Company Code - The company code for which the assignment is being done for Inbound Correspondence for a group of business partners
- RECIPIENT_TYPE - Recipient Type - The business partner's role type, that will determine whether the correspondence is meant to be sent or received. In Syensquo's context this is either
- Counterparty, or
- Depository
- PRODUCT_CAT- Product Category - The product category is an internal key that controls processing of the objects defined by the product type. The user must specify which product categories the trader assignment must be extended
- PRODUCT_TYPE - Product Type - The product type allows the subdivision of a product category. Here user must specify which product types of the trader assignment must be extended. The product types enable to give the products company-specific names e.g. stocks can be grouped into domestic stocks and foreign stocks; bonds can be divided into fixed-interest bonds, variable-interest bonds, and zero bonds.
- TRANSACTION_TYPE - Transaction Type - The financial transaction type specifies which types of transactions can be carried out with a certain product type. It needs to be specified which transaction types the trader assignment must be extended. Such as
- investment and borrowing of fixed-term deposits,
- deposits at notice,
- purchase and sale of bonds.
- FUNCTION_IN - Correspondence Class - It denotes Type of Treasury related correspondence between a Company Code and a business partner, assigned with treasury roles. The correspondence class is related to the business transactions of the available message formats, such as SWIFT messages. Correspondence classes are used as configuration terms that control the channel, format, and other attributes of TRM (Treasury, Risk Management) correspondence communication.
- BPGROUP - Business Partner Group ID - This is an ID that is created for a group of Business Partners and is used to assign to a correspondence class for the combination of Product Category, Product Type, Transaction Type. The Business Partner grouping is based on the role of the Business Partner and in Syensquo's context this applies to Business Partners with Counterparty or Depository roles
The treasury function in legacy is carried out in the Quantum system and therefore for the conversion of this object, the data/details need to be provided by business in a Data Collection Template (hereinafter referred to as DCT) and transformed as applicable for S4HANA in Syniti and load using a custom program <TBC> as no LTMC is available for this object.
Conversion Scope
The scope of this document covers the approach for maintaining active assignments of inbound correspondences to a Treasury Business Partner, or a group of Business Partners having Counterparty or Depository Role for the object 1201 - BP Group Assignment for Inbound Correspondence
into S/4HANA following "DD-FUN-050 Master Data Standard_1201 - BP Group Assignment for Inbound Correspondence".
List of source systems and approximate number of records
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
Quantum | Business Partner Group Assignment for Inbound Correspondence | NA | 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 (Quantum), the below areas need special handling:
- The relevant records to be provided into a DCT and stored in the Syniti for Transformation
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| TCORT_INB_ASSIGN | PARTNER | BP_PARTNR_NEW | Business Partner Number | CHAR | 10 | Conditional |
| TCORT_INB_ASSIGN | COMPANY_CODE | BUKRS | Company Code | CHAR | 4 | Conditional |
| TCORT_INB_ASSIGN | RECIPIENT_TYPE | FTR_RECIPIENT_TYPE | Recipient/Sender Type | CHAR | 15 | Conditional |
| TCORT_INB_ASSIGN | PRODUCT_CAT | SANLF | Product Category | NUMC | 3 | Conditional |
| TCORT_INB_ASSIGN | PRODUCT_TYPE | VVSART | Product Type | CHAR | 3 | Conditional |
| TCORT_INB_ASSIGN | TRANSACTION_TYPE | TB_SFHAART | Transaction Type | CHAR | 3 | Conditional |
| TCORT_INB_ASSIGN | FUNCTION_IN | FTR_FUNCTION | Correspondence Class | CHAR | 15 | Conditional |
| TCORT_INB_ASSIGN | BPGROUP | FTR_BPGRP | Business Partner Group ID | CHAR | 15 | Mandatory |
Data Cleansing
For the purpose of the Object 1201- BP Group Assignment for Inbound Correspondence, the data cleansing is not applicable. It is expected that relevant records will be provided in DCT by business.
However, for the purpose of the checking the DCT, below preload validation reports are applicable:
ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
1 | Medium | Business Partner Role | Check the Business Partner used in the DCT is having a Role (Field: RLTYP) as either TR0151(Counterparty) or TR0152 (Depository), reference table - BUT100 | Show records in error | DCT |
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 / migration cockpit or the custom upload program as applicable.
However, with respect to object 1201- BP Group Assignment for Inbound Correspondence - the conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business. This DCT will be used for transformation and generation of the pre-load file. The load will be done via a custom program <TBC> as there is no LTMC available for this object.
Data Privacy and Sensitivity
NoneExtraction
For object 1201- BP Group Assignment for Inbound Correspondence, the extraction is not applicable as this will be a DCT provided by business.
Selection Screen
Not applicable
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for object 1201- BP Group Assignment for Inbound Correspondence data with exception of some fields which require transformation as mentioned in the transformation rule.1201- BP Group Assignment for Inbound Correspondence - DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| PARTNER | Business Partner Number | This is Conditional field For the DCT purpose, please indicate a business partner number if the Incoming Correspondence is to be specifically assigned to a Business Partner of Counterparty or Depository role. If not filled, then the assignment is applicable to all the business partners. |
| COMPANY_CODE | Company Code | This is Conditional field For the DCT purpose, please indicate a Company Coder if the Incoming Correspondence is to be specifically assigned to a Business Partner of Counterparty or Depository role of a Company Code. If not filled, then the assignment is applicable to all the Company Codes. |
| RECIPIENT_TYPE | Recipient/Sender Type | This is Conditional field For the DCT purpose, please indicate a role if the assignment is to be specific to Counterparty or Depository. If left blank, then it is applicable to all. |
| PRODUCT_CAT | Product Category | This is Conditional field For the DCT purpose, please indicate a value if the assignment is to be specific at the Product Category level. If left blank, then it is applicable to all Product Categories. |
| PRODUCT_TYPE | Product Type | This is Conditional field For the DCT purpose, please indicate a value if the assignment is to be specific at the Product Type level. If left blank, then it is applicable to all Product Types. |
| TRANSACTION_TYPE | Transaction Type | This is Conditional field For the DCT purpose, please indicate a value if the assignment is to be specific at the Transaction Type level. If left blank, then it is applicable to all Transaction Types. |
| FUNCTION_IN | Correspondence Class | This is Conditional field For the DCT purpose, please indicate a value if the assignment is to be specific for a Correspondence class. If left blank, then it is applicable to all available Correspondence classes. |
| BPGROUP | Business Partner Group ID | This is Mandatory field The applicable value from the available configuration as per design needs to be populated in the DCT |
Extraction Dependencies
For object 1201- BP Group Assignment for Inbound Correspondence no extraction dependencies are applicable as this is DCT and the object is Master Data 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 Migrate 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 Migrate
- 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
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.