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>

SourceScope

Source Approx No. of Records

Target SystemTarget 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.

TableFieldData ElementField DescriptionData TypeLengthRequirement
VTBTRA1RDEALERRDEALERTraderCHAR12Mandatory
VTBTRA1BUKRSBUKRSCompany CodeCHAR4Mandatory
VTBTRA1RANTYPRANTYPContract TypeCHAR1Conditional
VTBTRA1SANLFSANLFProduct CategoryNUMC3Conditional
VTBTRA1SGSARTVVSARTProduct TypeCHAR3Conditional
VTBTRA1SFHAARTTB_SFHAARTTransaction TypeCHAR3Conditional
VTBTRA1AUTHORTB_AUTHORAuthorisation indicator for Treasury ProductCHAR1Mandatory


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:

IDCriticalityError Message/Report DescriptionRuleOutputSource 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

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

<TBS - Rules may change after final design confirmation as the selection is conditional> 

Field NameField DescriptionRule

1-RDEALER

Trader

Trader ID number as per pre-configured value

VTBTRA1-BUKRS

Company Code

The source Company Code or Entity ID of the Quantum for which a trader ID needs authorisation. 

(To be checked against the Company Code in scope for treasury)

VTBTRA1-RANTYP

Contract Type

Select only one Contract Type from the pre-configured value if the trader authorisation is only relevant for that Contract Type else leave blank. 

Note - If Contract Type is not specified then Product Categories relevant to all Contract Type will be picked up.

VTBTRA1-SANLF

Product Category

Select only one Product Category of a Contract Type as per pre-configured value if the trader authorisation is only relevant for that Contract Type and Product Category combination else leave blank. 

Note - If Product Category is not specified for a Contract Type, then all Product Categories and Product Types under the Product Category will be picked up.

VTBTRA1-SGSART

Product Type

Select only one Product Type of Product Category of a Contract Type as per pre-configured value if the trader authorisation is only relevant for that Contract Type, Product Category and Product Type combination else leave blank. 

Note - If Product Type is not specified for a Contract Type, then all Product Categories, Product Types and Transaction Type under the Product Type will be picked up.

VTBTRA1-SFHAART

Transaction Type

Select the transaction type that are relevant for selected Trader ID, Company Code, Product Category, Product Type. Select at the Product Type level if the Trader Authorisation is applicable for all transaction types of a product type.

VTBTRA1-AUTHOR

Authorisation indicator for Treasury Product

This indicator is to set to provide the authorisation at the desired level. This can be at overall level or at specific level

Repeat the data row in the DCT for the combination of Trader ID, Company Code if the authorisation is to be provided only at specific transaction type for a product type or product category for a contract type.

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 DescriptionTeam 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/Functional 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/Functional Team

13.   

Repeat steps 5 to 11 if necessary

Syniti/Data team

14.   

Proceed to pre-load validations

Data team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic

01

NA

NA

NA

DCT

S4HANA

VTBTRA1

RDEALER

Trader

As per DCT

02

NA

NA

NA

DCT

S4HANA

VTBTRA1

BUKRS

Company Code

As per DCT

03

NA

NA

NA

DCT

S4HANA

VTBTRA1

RANTYP

Contract Type

As per DCT

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 DescriptionTeam 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 Data team followed by the Project Team (business).

Completeness

TaskAction

Generation of
Pre-load reports

Mandatory field check.

Check the correctness of the following fields

  • Company code transformation
  • Trader ID
  • Contract type mapping where applicable
  • Authorisation indicator as per DCT at specified level such as Transaction Type, Product Type, Product Category, Contract Type etc.

Record Count

Confirm the record counts in preload summary report against the relevancy rules applied

  • Total Records: 
  • Valid Records:
  • Invalid Records:

i.e. check the total records and target ready records.

Business Confirmation

Preload will be generated for all company code / plants/valuation area in scope for conversion in the respective wave.

Data team will perform the initial validation of Pre-Load report based on the pre agreed validation checklist. Any errors found in the validation will be corrected and the preload file will be regenerated and validated.

The Pre-Load file(s) will be sent to the Business Representatives for their validation and sign off. Any errors found in the validation will be corrected and the preload file will be regenerated and validated.


Accuracy

TaskAction

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
  • Trader ID is as per DCT
  • Contract type is as per DCT


Business Value Checks

NA

Records in Errors

Review and correct the errors.  Rectify all valid errors. Unresolved errors should be discussed and agreed with business, with proper justification for exclusion. 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

TaskAction

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

TaskAction

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 manual or automated data load into target system using load tool.
  2. Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
  3. 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)
  4. The Syniti team should perform a round of post load reconciliation before sending it to the data team for further validation.

Load Run Sheet

Item #Step DescriptionTeam 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.

Syniti Team / 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. These records can be sent to the data team for a quick validation, before the full load is executed.

Syniti Team / Data team

3

Proceed with the full load if steps one and two were successful, else fix the records with errors and rerun the load.

Syniti Team / Data team

4

Validate few records loaded by accessing standard transactions from S/4HANA e.g. check table VTBTRA1 or via T Code TBT1 (selective) to check the loaded records in the system.

Syniti Team / Data team

5

Generate post load report if step 3 and 4 are satisfactory.

Syniti team

6

Log errors as defects, if any and address resolutions. Close defects.

Data team/Functional team

7

Resolve defects by reupload and re-generate post load reports if necessary.

Syniti team /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.

Syniti team /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

03

Contract type mapping

04

Product category assignment to Contract Type

05

Product type assignment to Product Category

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)

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 TypeError DescriptionAction Taken

Valid Master 

Business Partner is not having a valid treasury role

Ensure that Business Partner is updated

Value Mapping error

Incomplete configuration

Create or rectify configuration

Post-Load Validation

Project Team

The following post load validations will be done by Project Team

Completeness

TaskAction

Reconciliation of Record Count

Record Count - Count and check how many records were loaded vs. Records in the load file (Each mock has its own data record count). Check legacy Vs Preload Vs Post load.

Check for logs from Load and fix erroneous records, if any.


Accuracy

TaskAction

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

TaskAction

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

Check all the value mappings have captured the configuration values correctly. Check the values for correctness (where applicable).

Business may also run transaction code TBT1 to check the trader authorisation values 


Accuracy

TaskAction

Field Checks

Check the fields to ensure that the trader authorisations have been maintained correctly

Check the assignment of contract type, Product category, Product type and transaction type.

Value Check

NA


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 by the business in the DCT page with granularity by Company Code, Trader ID, Contract Type, Product Category, Product Type and Transaction type, where a Trader ID for a Company needs to have multiple authorisations.
  • A custom program will be used to load the values as provided in the DCT

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