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

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:

1. 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.

Data Cleansing

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:

1. The data exists. connects to the source and loads the data into . There are 3 methods:
   1. Perform full data extraction from relevant tables in the source system(s).
   2. Perform extraction through the application layer.
   3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. 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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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:

1. Perform value mapping and data transformation rules.
   1. Legacy values are mapped to the to-be values (this could include a default value)
   2. Values are transformed according to the rules defined in
2. 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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

See also

Change log