Purpose

The purpose of this document is to define the conversion approach to create conversion for Object 1182 - Trader Authorisation in S/4 HANA.

Trader Authorisation is a key control mechanism designed to manage who is allowed to create, modify, and approve financial transactions. It ensures segregation of duties, mitigates operational risk, and enforces compliance with internal policies and external regulations.

The 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 1182- Trader Authorisation, to be used in treasury module of S4HANA.

Key tables and fields: 

The table mentioned below is the the main table used for trader authorisations in S4.

• VTBTRA1 - Trader Authorisation - This table stores information related to Trader, company code, Contract type, Product category, Product type, Transaction type and authorisation indicator. The purpose of these fields are as listed below
  • RDEALER - Trader : This field contains the Trader ID of the in-house trader responsible for the transaction.
  • BUKRS - Company code: The company code for which the financial transaction is being performed
  • RANTYP - Contract Type: The contract type is an indicator which helps identify the nature of the contract e.g. "2 - Securities", "5 - Foreign Exchange", "5 - Money Market", "6 - Derivatives", "T - Trade Finance" etc.,
  • SANLF - 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
  • SGSART - Product Type: The product type allows the subdivision of a product category. Here user must specify which product types the trader assignment must be extended. The product types enable you 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.
  • SFHAART - Transaction Type: 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, or purchase and sale of bonds. It needs to be specified which transaction types the trader assignment must be extended.
  • AUTHOR - Authorisation Indicator for Treasury Product: Identifier to mention if the trader is authorised or not.

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 sourced from Quantum and transformed as applicable for S4HANA in Syniti and load using migration cockpit in S4HANA

Conversion Scope

The scope of this document covers the approach for converting active Treasury - Trader Authorisation from Legacy Source Systems (Quantum) into S/4HANA following the Master Data Design Standard - DD-FUN-050 Master Data Standard_1182 - Trader Authorisation

The data from legacy system includes:

1. Active records for Trader Authorisation which are still in use/valid and have validity date is greater than the cutover date.
2. Trader Authorisation relates to the authorisation to traders with regards to contract type, product category, product type, transaction type etc.

The data from legacy system excludes:

1. All trader authorisations which have expired i.e. which have a validity date in the past and are not in use in any exposure

Additional Information

Multi-language Requirement

None

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

As the conversion involves a source system which is non-SAP (Quantum), the below area needs special handling:

1. Extraction of Trader Authorisation from source system i.e. Quantum is to be done manually.
2. Cleansing (if any) to be done by the business team to identify all relevant records for migration.
3. The extracted records to be converted into a DCT and stored in the Syniti for Transformation
4. Below Value mapping tables to be created in Syniti:
1. Counterparty to Business Partner 
2. Assignment of product type and categories to the correct Traders 
5. Amount and date format from source system to align with S4HANA 

Target Design

The Target design of the object 1182 - Trader Authorisation Master Data based on the MDS - DD-FUN-050 Master Data Standard_1182 - Trader Authorisation is as below
The technical design of the target for this conversion approach. 

The technical design of the target for this conversion approach.

Data Cleansing

For the purpose of the Object 1182- Trader Authorisation, the data cleansing should happen in the source systems i.e. Quantum as per below cleansing activity. The business cleansing is expected to be done by the business.

1. Identify all in active records for Limits which are not valid and have validity date in the past
2. Identify all records which may still be having a validity date in the future but are against the counterparties which are nor relevant for migration

Exclude such records from the extraction from the Quantum and populate in the DCT

Conversion Process

The generic high-level process steps for the conversion are as below:

1. Extraction:
1. Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
2. 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
2. Transform 
1. Transform fields by applying the fields and value mapping in the Syniti 
2. Generate and validate Pre-load files
3. Load
1. Load the validated Pre-load file using SAP's LTMC / migration cockpit or the custom upload program as applicable. 

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)

Trader Authorisation - 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

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.
• Trader Authorisation is in scope based on data design and any exception requested by business.

See also

Change log