Status
Owner	BAJAJ-ext, Manoj
Stakeholders	PILLAY-ext, Lawrence

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 trader authorisation is being performed
• RANTYP - Contract Type: The contract type is an indicator which helps identify the nature of the contract. The possible values are
  • "2" - Securities
  • "4" - Foreign Exchange
  • "5" - Money Market
  • "6" - Derivatives
  •  "T "- Trade Finance
• 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 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.
• SFHAART - 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.
• 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 or provided by business in a DCT and transformed as applicable for S4HANA in Syniti and load using a custom program (LSMW) as no LTMC is available for this object.

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

<to be confirmed as it is possible that the information relevant for this object may not be available in Quantum as this object is more of a technical setup for S4> It is assumed that only relevant information will be provided by the business in the DCT

List of source systems and approximate number of records <number of company codes to be confirmed>

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
Quantum	Trader Authorisation Information	<TBC>	S4HANA	<TBC>

Note: The approximate number yet to be confirmed but it is estimated to be not more than 100 records.

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 areas need special handling:

1. Extraction of Trader Authorisation from source system i.e. Quantum- Not applicable
2. The relevant records to be provided into a DCT and stored in the Syniti for Transformation

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.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
VTBTRA1	RDEALER	RDEALER	Trader	CHAR	12	Mandatory
VTBTRA1	BUKRS	BUKRS	Company Code	CHAR	4	Mandatory
VTBTRA1	RANTYP	RANTYP	Contract Type	CHAR	1	Conditional
VTBTRA1	SANLF	SANLF	Product Category	NUMC	3	Conditional
VTBTRA1	SGSART	VVSART	Product Type	CHAR	3	Conditional
VTBTRA1	SFHAART	TB_SFHAART	Transaction Type	CHAR	3	Conditional
VTBTRA1	AUTHOR	TB_AUTHOR	Authorisation indicator for Treasury Product	CHAR	1	Mandatory

Data Cleansing

For the purpose of the Object 1182- Trader Authorisation, the data cleansing is not applicable. It is expected that relevant records will be provided in DCT by business for the purpose of creating Trader Authorisations in S4

However, for the purpose of the checking the DCT, below cleansing reports are applicable:

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1	Medium	Trader ID	Check the Trader ID (Field: REDEALER) in the DCT is valid.	Show records in error	DCT
2	Medium	Company Code	Check the Company Code is as per scope of the Treasury	Show records in error	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. 

However, with respect to object 1182- Trader Authorisations - 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 (LSMW) as there is no LTMC available for this object.

Data Privacy and Sensitivity

None

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

For object 1182, the extraction is not applicable as this will be a DCT provided by business.

Selection Screen

Not applicable for this object as this will be a DCT from business.

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Trader Authorisation data with exception of some fields which require transformation as mentioned in the transformation rule.

Trader Authorisation - DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

Not applicable for this object

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

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

Not applicable for this object

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:

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

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

Change log