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.

1182 - Trader Authorisation - DCT Rules

Field Name	Field Description	Rule
1-RDEALER	Trader	Trader ID number will be generated based on the external or internal number ranging.
VTBTRA1-BUKRS	Company Code	The company code/entity of the source. The value mapping of the source and target Company codes to be maintained separately
VTBTRA1-RANTYP	Contract Type	Contract type value will be derived through value mapping
VTBTRA1-SANLF	Product Category	The Product Category will be picked from allowed values as per configuration
VTBTRA1-SGSART	Product Type	The Product type will be picked from allowed values as per configuration
VTBTRA1-SFHAART	Transaction Type	The Transaction type will be picked from allowed values as per configuration
VTBTRA1-AUTHOR	Authorisation indicator for Treasury Product	This will be based on the authorisation and will be captured in the DCT page.

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
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 DCT 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	DCT	S4HANA	VTBTRA1	RDEALER	Trader	As per DCT
02	NA	NA	NA	DCT	S4HANA	VTBTRA1	BUKRS	Company Code	From Value mapping
03	NA	NA	NA	DCT	S4HANA	VTBTRA1	RANTYP	Contract Type	From value mapping
04	NA	NA	NA	DCT	S4HANA	VTBTRA1	SANLF	Product Category	As per DCT
05	NA	NA	NA	DCT	S4HANA	VTBTRA1	SGSART	Product Type	As per DCT
06	NA	NA	NA	DCT	S4HANA	VTBTRA1	SFHAART	Transaction Type	As per DCT
07	NA	NA	NA	DCT	S4HANA	VTBTRA1	AUTHOR	Authorisation indicator for Treasury Product	As per DCT

Transformation Mapping

Below value mapping tables should be constructed in Syniti  

Mapping Table Name	Mapping Table Description
Company Code	Mapping Table for Quantum company/entity code to S4HANA entity code

Transformation Dependencies

List the steps that need to occur before transformation can commence

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 DCT from business has been received and maintained in Syniti	Syniti/Data team
5	Confirm on the extracted values	Syniti, Data and business

Pre-Load Validation

Project Team

The Pre Load validations are performed by Project Team

Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. Limit Master is having a valid limit type Limit Master is having a valid start and end date The end date is in the future The company code assigned to limit master is as per scope Limit is assigned to a valid business partner Limit Master is assigned to a valid limit product group The trader id in the Limit Master is from allowed values The date fields are as per DD.MM.YYYY or DD/MM/YYYY format
Record Count	Record Count Confirm the record counts in preload summary report Total Records:  Valid Records: Invalid Records:
Business Confirmation	Data team after the initial validation of Pre-Load validation based on the pre agreed validation checklist To send the Pre-Load file to the Business Representatives for all plants/valuation area in scope for conversion Business Representatives to validate the pre-load file Agree with data team on the next steps for erroneous records

Accuracy

Task	Action
Mandatory field mapping and transformation	Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.  Mandatory field check. Company Code is rightly picked up Business Partner with treasury role is correctly picked up
Business Value Checks	The total values as per the DCT and pre-load value are matching for the fields containing the limit amounts
Records in Errors	Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

The following pre-load validations will be performed by business.

Completeness

Task	Action
Check Data load register count	Business Data Owner/s to verify that the total number of relevant records to be converted as per DCT is equal to the total number of records in the Preload file.

Accuracy

Task	Action
Conversion accuracy	To check and validate the load files with all the transformation and mapping rules, to be signed off.

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
3. Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done using LTMC cockpit object of Limit Master (Limit Products)
4. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE) 

Load Run Sheet

Item #	Step Description	Team Responsible
1	Go to load file and pick 5 data records, load manually without any tool. See what happens. If all okay, proceed with the next step.	Data team
2	Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay.	Data team
3	Proceed with the full load if steps one and two were succeed else fix the issue with records	Data team
4	Validate few records loaded by accessing standard transactions from S/4HNA e.g. TBL3 or TBL1 to view limits.	Data team
5	Generate post load report if step 5 is validated	Data team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 1 to 5 if necessary.	Data team

Load Phase and Dependencies

The load phase for this object is ideally relevant for pre-cutover Phase 4

Configuration

Below configurations must exist to facilitate the conversion of this object.

Item #	Configuration Item
01	Company Codes relevant for Treasury
02	Trader IDs

Conversion Objects

Object #	Preceding Object Conversion Approach
CNV-3040	BP with Treasury role (note: the conversion object number will change as this is under Change Request)
CNV-1182	Trader Authorisations

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
Valid Master	Business Partner is not having a valid treasury role	Ensure that Business Partner is updated
Missing Trader Authorisation	Trader ID used for Limit Master is missing authorisation	Update the trader authorisations
Validity date	Validity date of the limit is in past	Check the Limit master and correct the dates

Post-Load Validation

Project Team

The following post load validations will be done by Project Team

Completeness

Task	Action
Reconciliation of Record Count	Record Count - Count and check how many records were loaded vs. Records in the load file (Each mock has it's own data record count) Check for logs from Load and fix erroneous records, if any.

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report.

Business

The following post load validations will be done by business.

Completeness

Task	Action
Record Count Check	Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations Business may also run transaction code TBL3 or TBL1 to cross check the Limit Masters

Accuracy

Task	Action
Field Checks	Check the fields to ensure that Limit Masters against Limit Types have been properly maintained Check the other key fields such as Portfolio, Trader IDs etc.
Value Check	Check the values  The limit amounts by the limit types are matching as per the pre-load files

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.
• Trader authorisation data will be provided in the DCT page.

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