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

Purpose

The purpose of this document is to define the conversion approach to create Securities Account (object 1185) in S/4 HANA.

Securities Account is a master data in Treasury and Risk Management module of S4HANA, that serves as a central place to log all details of securities held by an entity. This master data facilitates the recording and management of buying, selling, and other events related to securities. In S4HANA, the transaction code to create a Security Account is TRS_SEC_ACC

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 1185- Securities Account, to be used in treasury module of S4HANA.

Key tables and fields: 

There are two tables involved in S4HANA with respect to the maintenance of Securities Account.

These tables are TWD01 (Treasury: Securities Account Master Data) and TRST_SECACC_BANK (Payment Details for Securities Account).  The payment details for the securities transaction are firstly checked in Securities account. If the same is not available, it is sourced from Business Partner master data.

Table TWD01 stores master data related to securities accounts, which are essential for managing financial instruments like bonds, stocks, and other securities. The key fields of this table are:

• BUKRS - Company Code - The company code is an organizational unit within financial accounting. This field along with Security Account (RLDEPO) acts as primary key for link with table for Payment Details (Table: TRST_SECACC_BANK)
• RLDEPO -Securities Account - Securities account identifier. An ID to be entered as per agreed design i.e. external number at the time of creating a Security Account. This field is also referenced along with BUKRS (Company Codes) in the table TRST_SECACC_BANK
  
• XLDEPO - Securities Account ID - Is the field to store the description of the Security Account
• SECACC_TYPE - Securities Acct Type - Each securities account type relates to a securities account category such as
  • Asset Securities Account,
  • Issuance Securities Account
  • Lending Securities Account
• RDPBANK - Depository Bank - The business partner with depository bank role with which a Security account is to be created.
• VERKONTO - Clearing Account - Account number of the cash clearing account for the depository bank. It also represents the securities account number for US securities accounts. It is free text field
• RDEPOTNR - Sec.acct number - This represents the number of the securities account at the depository bank. It is a free text field.
• EXT_SEC_ACC_NO - External Securities Account ID - The external securities account ID describes the number under which the securities account is managed by the depository bank. It also serves as the identifier for the securities account in case of external securities account statement load. It is a free text field.
• RPORTB- Portfolio - portfolio is an organizational element to group together various treasury transactions for reporting purposes.
• RGSBER-Business Area - It is an organisational unit used for internal reporting within a company code

Table TRST_SECACC_BANK stores payment details for securities accounts, which are used in managing financial instruments like stocks and bonds. It links to the TWD01 and gets updated while creating a Security Account. Its key fields are:

• BUKRS - Company Code - The company code is an organizational unit within financial accounting. This field along with Security Account (RLDEPO) acts as primary key for links back to table TWD01
• RLDEPO -Securities Account - Securities account identifier. An ID to be entered as per agreed design i.e. external number at the time of creating a Security Account. This field along with Company code (BUKRS) acts as primary key for links back to table TWD01
• CURRENCY - Payment Currency - Specifies the currency in which payments are made or received. 
• VALID_FROM - Payment Details Effective From - Indicates the start date from which the payment details are valid.
• DIS_FLOWTYPE - Update Type - Defines the update type for payment flows, used to categorise the Cash Flows.
• HOUSEBANK - House Bank - House bank of the company code 
• ACCOUNT - House Bank Account ID - The Account ID of the House bank which is to be used for the Security Account
• RPZAHL - Payer/Payee - Represents the payer/payee involved in the transaction.  Incoming and outgoing payments are settled using this business partner.
• RPBANK - Partner Bank - This field helps to identify the bank details of the Business partner
• SZART - Payment Transactions - This check box identifies if the payment posting happens via customer or vendor subledger
• ZLSCH - Payment Method - The payment method determines how payments are to be made, e.g. by check, bank transfer or bill of exchange.
• SPAYRQ - Payment request - This indicator is used to determine whether a payment request is to be created or not. If the indicator is not flagged, then no payment request is generated.

• ZWELS - Payment Methods - This field is only applicable to determine the payment method if the same is not identified in the Payer/Payee item details

The treasury function in legacy is carried out in the Quantum system and therefore for the conversion of this object i.e. Security Accounts, the data/details need to be sourced from Quantum and transformed as applicable for S4HANA in Syniti and load using a custom program as the LTMC for this object is not available in the Data Migration Cockpit.

Conversion Scope

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

The relevancy criteria is not applicable for this object as the relevant data will be provided by business in a DCT (Data Collection Template)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
Quantum	Active and in use Securities Accounts	100 <TBC>	S4HANA	100 <TBC>

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, the below area needs special handling:

1. Extraction of Securities Accounts from source system i.e. Quantum is to be done manually.
2. Cleansing by business team to mark the Securities Accounts in the source system to ensure that only active records are provided in DCT.
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. Source and target company code
5. Amount and date format from source system to align with S4HANA 
6. As the target structure in S4HANA involves two tables-(TWD01 and TRST_SECACC_BANK), the load file needs to have the linkage at the Company Code and Security Account number.

 Target Design

The Target design of the object 1185 - Securities Account Master Data based on the MDS - DD-FUN-050 Master Data Standard_1185 - Securities Account is as below

<Note: The target design can change subject to business confirmation after 

The technical design of the target for this conversion approach. 

Table TWD01 -Treasury: Securities Account Master Data

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
TWD01	BUKRS	BUKRS	Company Code	CHAR	4	Mandatory
TWD01	RLDEPO	VRLDEPO	Securities Account	CHAR	10	Mandatory
TWD01	XLDEPO	XLDEPO	Securities Account ID	CHAR	30	Mandatory
TWD01	SECACC_TYPE	TPM_ SECACC_TYPE	Securities Acct Type	CHAR	3	Mandatory
TWD01	RDPBANK	RDEPOTBANK	Depository Bank	CHAR	10	Mandatory
TWD01	VERKONTO	VERKONTO	Clearing Account	CHAR	15	Mandatory
TWD01	RDEPOTNR	ABNKR	Sec.acct number	CHAR	15	Mandatory
TWD01	EXT_SEC_ACC_NO	EXT_SEC_ACC_NO	External Securities Account ID	CHAR	35	Mandatory
TWD01	RPORTB	RPORTB	Portfolio	CHAR	10	Conditional
TWD01	RGSBER	GSBER	Business Area	CHAR	4	Not to be used

Table - TRST_SECACC_BANK - Payment Details for Securities Account

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
TRST_SECACC_BANK	CURRENCY	TPM_PAYMENT_CURR	Payment Currency	CUKY	5	Mandatory
TRST_SECACC_BANK	VALID_FROM	TPM_VALID_PAYMENT_INFO	Payment Details Effective From	DATS	8	Conditional
TRST_SECACC_BANK	DIS_FLOWTYPE	TPM_DIS_FLOWTYPE	Update Type	CHAR	8	Conditional
TRST_SECACC_BANK	HOUSEBANK	TB_RHABK1	House Bank	CHAR	5	Mandatory
TRST_SECACC_BANK	ACCOUNT	TB_RHKTID	House Bank Account	CHAR	5	Mandatory
TRST_SECACC_BANK	RPZAHL	TB_RPZAHL_NEW	Payer/Payee	CHAR	10	Mandatory
TRST_SECACC_BANK	RPBANK	TB_RPBANK	Partner Bank	CHAR	4	Mandatory
TRST_SECACC_BANK	SZART	TB_SZART	Payment Transaction	CHAR	1	Not to be used
TRST_SECACC_BANK	ZLSCH	DZLSCH	Payment Method	CHAR	1	Mandatory
TRST_SECACC_BANK	SPAYRQ	TB_SPAYRQ	Payment request	CHAR	1	Conditional
TRST_SECACC_BANK	ZWELS	DZWELS	Payment Methods	CHAR	10	Not to be used

Note: 

• The fields BUKRS and RLDEPO are the common fields linking the tables TWD01 and TRST_SECACC_BANK

Data - Pre Load Validation Report

 For the purpose of the Object 1185- Securities Accounts Master Data, the below preload validation reports will be used in Synitii based on the DCT provided by the business.  

1. The Depository Banks ID mentioned against the Security Accounts in DCT: Check that a Business Partner with Depository Bank role exists in S4HANA
2. The House Banks and Bank IDs assigned to the Security Accounts in the DCT are available in S4HANA

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
01	High	Depository Bank Check	Check Depository Bank ID created as Business Partner with role TR0152	Show records in error	Not applicable,  Check against S4 Configuration/Master Data
02	Medium	House Bank, Bank IDs check	Check the House Bank and Bank IDs given in the DCT are available as master records in table T012 and T012K respectively	Show records in error	Not applicable,  Check against S4 Configuration/Master Data

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 or the custom upload program as applicable. 

However, with respect to object 1185- Securities Accounts Master Data - the conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business based on the source data from Quantum system. This DCT will be used for transformation and generation of the pre-load file. 

The load will be done via a custom program <to be confirmed>, as LTMC for this object is not available as of now.

As there are two tables involved, the custom program should be able to link the information via the common fields i.e. BUKRS (Company Codes) and RLDEPO (Securities Account). 

Data Privacy and Sensitivity

None

Extraction

Extract data from a source into Syniti. There are 2 possibilities:

1. The data exists. Syniti connects to the source and loads the data into Syniti. 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 Syniti; 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 Syniti. This is to be conducted using DCT (Data Collection Template) in Syniti.

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

In case of the object 1185-Securities Account, the data is to be provided in a DCT by the business, therefore extraction related activity is outside Syniti. 

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
01	Extract from relevant tables/details from Quantum all relevant information required to populate the DCT for Securities Account for relevant Company Codes	Business

Selection Screen

Not applicable

Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Object 1185- Securities Account Master data with exception of some fields which require transformation as mentioned in the transformation rule.

1185- Securities Account DCT Rules

Note:

• Only the fields which are marked as Required or Conditional in the MDS for this object have been considered below
• Business Users to provide the values in the DCT.
• DCT checks only the field length and field behaviour (mandatory/optional etc.) checks, therefore Users must provide valid Configuration values where applicable 

Field Name	Field Description	Rule
TWD01-BUKRS	Company Code	The Company Code as per the scope for TRM, for which a Security Account Master Data to be created
TWD01-RLDEPO	Securities Account	This is going to be external number i.e. not generated by the System. A Security Account number must be provided
TWD01-XLDEPO	Securities Account ID	Description of the Security Account ID. It is free text field
TWD01-SECACC_TYPE	Securities Acct Type	Must be selected as AKT - For Assets Security Account or PAS - For Issued debts Security Account
TWD01-RDPBANK	Depository Bank	Business Partner number of S4HANA with the Depository Bank Role TR0152
TWD01-VERKONTO	Clearing Account	This is the Account number of the cash clearing account for the depository bank. This is a free text field, but it must correspond to actual Cash Clearing Account
TWD01-RDEPOTNR	Sec.acct number	The number of the securities account at the depository bank. This is a free text field but should correspond to actual Security Account Number at the Depository Bank
TWD01-EXT_SEC_ACC_NO	External Securities Account ID	This is external securities account ID under which the securities account is managed by the depository bank. This is a free text field
TWD01-RPORTB	Portfolio	An organizational element to group together various treasury transactions for reporting purposes. It must be selected from the list of portfolios maintain in system for a company code.
TRST_SECACC_BANK-CURRENCY	Payment Currency	Currency key to denote the currency in which payment flows will be maintained
TRST_SECACC_BANK-VALID_FROM	Payment Details Effective from	Date field to indicate the valid from date of the Payment Details. Date format to be YYYYMMDD
TRST_SECACC_BANK-DIS_FLOWTYPE	Update Type	The update types carry information on flows in the parallel valuation areas and in securities account management for the securities area. It should be from available Update Type as created in the to be system.
TRST_SECACC_BANK-HOUSEBANK	House Bank	The House Bank ID. It must be available for the Company Code for which a Security Account is being created
TRST_SECACC_BANK-ACCOUNT	House Bank Account	The Account ID of the House Bank. It should exist as Master Data for the House Bank ID used in the security account.
TRST_SECACC_BANK-RPZAHL	Payer/Payee	The business partner ID for which a Security Account is being created. It must be available as Master Data
TRST_SECACC_BANK-RPBANK	Partner Bank	The bank detail as maintained in the Business Partner master data.
TRST_SECACC_BANK-ZLSCH	Payment Method	Payment Method as per the config value
TRST_SECACC_BANK-SPAYRQ	Payment request	It is a conditional field, to be filled with X only if a payment request is required to be generated for a Security Account

Extraction Dependencies

For object 1185- Securities Accounts no extraction dependencies is applicable as this is DCT and a Master Data by nature.

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

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 CONSTRUCT 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	CONSTRUCT	S4HANA	TWD01	BUKRS	Company Code	As per DCT
02	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	RLDEPO	Securities Account	As per DCT
03	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	XLDEPO	Securities Account ID	As per DCT
04	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	SECACC_TYPE	Securities Acct Type	As per DCT (either AKT or PAS)
05	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	RDPBANK	Depository Bank	As per DCT
06	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	VERKONTO	Clearing Account	As per DCT
07	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	RDEPOTNR	Sec.acct number	As per DCT
08	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	EXT_SEC_ACC_NO	External Securities Account ID	As per DCT
09	NA	NA	NA	CONSTRUCT	S4HANA	TWD01	RPORTB	Portfolio	Value Mapping - TWPOB
10	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	CURRENCY	Payment Currency	As per DCT
11	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	VALID_FROM	Payment Details Effective from	As per DCT. To be filled up only if for same currency different payment details are maintained for different effective dates
12	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	DIS_FLOWTYPE	Update Type	As per DCT- Check against TRGV_DFTSOURCAS3 It is to be filled up in DCT  only if for same currency different payment details are maintained for different update types
13	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	HOUSEBANK	House Bank	As per DCT - Check against T012
14	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	ACCOUNT	House Bank Account	As per DCT - Check against T012K
15	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	RPZAHL	Payer/Payee	As per DCT
16	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	RPBANK	Partner Bank	As per DCT - Check against LFBK
17	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	ZLSCH	Payment Method	As per DCT - Check against LFB1
18	NA	NA	NA	CONSTRUCT	S4HANA	TRST_SECACC_BANK	SPAYRQ	Payment request	As per DCT

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
Company Code	Source (Quantum) and Target (S4HANA) mapping of Company Codes
Business Partner	Mapping Table for Quantum counterparty/partner code to S4HANA Business Partner
TWPOB	Portfolio

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. Company Code for which a Security Account master is being created is part of the scope Security Account number is available  Security Account ID is available Security Account Type is not blank The Business Partner ID used in Depository Bank is available with role TR0152 Clearing Account Number is available Security Account Number is available  External Security Account ID is available Payment Currency is available  Security Account Type is not blank The Business Partner ID used in Depository Bank is available with role TR0152
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 TR0152 is correctly picked up
Business Value Checks	The fields value as per the DCT, and pre-load fields are matching for the key fields.
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 produce the load file if the loading of records to be done via a custom program <TBC>, as LTMC for this object is not available as of now. 
2. 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
01	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
02	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
03	Proceed with the full load if steps one and two were succeed else fix the issue with records	Data team
04	Validate few records loaded by accessing standard transactions from S/4HNA e.g.  FWDP	Data team
05	Generate post load report if step 5 is validated	Data team
06	Log errors as defects, if any and address resolutions. Close defects.	Data team
07	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
08	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
09	Repeat steps 1 to 5 if necessary.	Data team

Load Phase and Dependencies

The load phase for the object 1185-Securities Account is Pre-Cutover Phase 5

Configuration

Below configurations should exist 

Item #	Configuration Item
01	Company Codes relevant for Treasury
02	Portfolio Types
03	House Bank
04	House Bank Ids
05	Payment Methods
06	Update Types

Conversion Objects

Object #	Preceding Object Conversion Approach
CNV-1182	Trader Authorisations
CNV-1198	Assign BIC to Business Partner
CNV-1199	Assignment of Profiles and BP Groups to External Recipients
CNV-1200	Inbound Process: Correspondence Class Assignment
CNV-1201	BP Group Assignment for Inbound Correspondence
CNV-1202	Treasury Business Partner Issuer - TR0150
CNV-1203	Treasury Business Partner Depository Bank - TR0152

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
Update Type	Update Type (Valid Up to) date is in the past	Check the Security Account's update type field value and correct the record
House Bank Accuount	The house bank entered in the record does not belong to the Company Code	Check the record and correct the values

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 FWDP to cross check the records created for Securities Account

Accuracy

Task	Action
Field Checks	Check the fields to ensure that Security Accounts against Depository Banks and Clearing Accounts have been properly maintained  Check the other key fields such as Portfolio, Valid from, Update Types as applicable

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Object 1185 is in scope based on data design and any exception requested by business.
• Only the relevant records for Security Accounts will be provided by business (sourced from Quantum) in the DCT 
• The load will be done via a custom program <TBC> for this object is not available as of now. 

See also

Change log