| Status |
| ||||||
|---|---|---|---|---|---|---|---|
| Owner | GANESAN-ext, Shivkumar | ||||||
| Stakeholders |
Purpose
Purpose
The purpose of this document is to define the conversion approach to create Assignment of Profiles and BP Groups to External Recipients (object 1199) in S/4 HANA.
Assignment of Profiles and BP Groups to External Recipients is a master data in Treasury and Risk Management module of S4HANA. This assignment is important to ensure that the financial transactions are processed accurately and efficiently.
The assignment of profiles and BP groups to external recipients in SAP is crucial for managing business partner communication and ensuring that the system can derive the necessary business attributes and technical attributes. This process is essential for maintaining the integrity and consistency of the SAP Treasury Risk Management system, which is designed to control correspondence activities. By assigning the appropriate profiles and BP groups, organizations can streamline their communication processes, improve data accuracy, and enhance overall efficiency in managing business relationships., the transaction code to Assignment of Profiles and BP Groups to External Recipients is FTR_EXT_ASSIGN.
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 1199- Assignment of Profiles and BP Groups to External Recipients, to be used in treasury module of S4HANA.
Key tables and fields:
The following table is involved in S4HANA with respect to the assignment of Profiles and BP Groups to External Recipients.
Table TCORT_EXT_ASSIGN (Treasury: BIC Codes / Account Numbers for Business Partners) holds the BIC information. The key fields of this table are:
- PARTNER – Business Partner Number – This field provides the unique identification number of the business partner.
- COMPANY_CODE – Company Code - The company code is an organisational unit within financial accounting.
- RECIPIENT TYPE – Recipient / Sender Type – This field captures the partner or acting party information, who can receive/send correspondence. The correspondence recipient type is mainly used to differentiate between internal and external recipients/senders. It is also a control parameter used in the creation of outgoing/incoming messages. E.g. “Controller Email”.
- CORR_CATEGORY – Correspondence Category - Tells the system whether the correspondence is created due some activity on a deal or a securities account transfer. However, here only correspondence for deal activity is relevant.
- CONTRACT_TYPE – Contract Type - The contract type is an internal key used for the different application areas in Treasury. Here user must specify which contract types the payment detail assignment must be extended. Possible entries are:
- 2 = Securities
- 4 = Foreign exchange
- 5 = Money market
- T = Trade Finance
- PRODUCT_CAT – Product Category -The product category is an internal key that controls processing of the objects defined by the product type. Here user must specify which product categories the profile and BP Group for the said BP must be extended. When defining the product types in customizing, you assign a specific product category to each product type. The available product categories are predefined in the system.
- PRODUCT_TYPE – Product Type – The product type allows you to subdivide a product category. Here user must specify which profile and BP Group for the said BP must be extended. The product types enable you to give the products company-specific names. For example, stocks can be grouped into domestic stocks and foreign stocks; bonds can be divided into fixed-interest bonds, variable-interest bonds, and zero bonds.
- TRANSACTION_TYPE – Financial 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. Here user must specify which transaction types the profile and BP Group for the said BP must be extended
- ACTIVITY_CAT – Transaction Activity Category – The transaction activity category determines: how the particular activity is interpreted and processed by the system which transitions to activities in other activity categories are possible. Here user must specify which Activity Category the profile and BP Group for the said BP must be extended.
- CORR_NUMBER - 1 Byte Unsigned Integer – It is the internally assigned number to each unique combination based on the number of profiles assigned.
- PROFILE - SWIFT/BIC for International Payments – Used as a configuration term to control the communication settings of a group of business partners.
- BPGROUP - Business Partner Group ID – This is an ID that is created for a group of Business Partners and is used to assign to a correspondence class for the combination of Product Category, Product Type, Transaction Type. The Business Partner grouping is based on the role of the Business Partner and in Syensqo this is applicable only to Business Partners with Counterparty i.e. they are not relevant for Depository roles.
- CORR_ADDTYPE - Alternative Address for Correspondence – The correspondence address indicates the address to which business partner correspondence should be sent. The Address ID indicated here uniquely identifies a valid business partner address for the business partner master record. If an alternative address is not indicated, the role-dependent standard address is used for creating correspondence.
The treasury function in legacy is carried out in the Quantum system and therefore for the conversion of this object i.e. BIC assignment to BP, 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.
Note Security Account field i.e. "SEC_ACCOUNT" is not relevant for the object.
Conversion Scope
The scope of this document covers the approach for converting active Treasury – Profile and BP Group assignments to BP from Legacy Source Systems (Quantum) into S/4HANA following the Master Data Design Standard - DD-FUN-050 Master Data Standard_1199 – Assignment of Profiles and BP Groups to External Recipients.
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 Profile and BP Group assignment to External Recipients | 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:
- Extraction of Profile and BP Groups assignment to BP from source system i.e. Quantum is to be done manually.
- Cleansing by business team to identify valid records in the source system i.e. to ensure that only active records are provided in DCT.
The extracted records to be converted into a DCT and stored in the Syniti for transformation
Target Design
The Target design of the object 1199 – Assignment of Profiles and BP Groups to External Recipients on the MDS - DD-FUN-050 Master Data Standard_1199 – Assignment of Profiles and BP Groups to External Recipients is as below
The technical design of the target for this conversion approach.
Table TCORT_EXT_ASSIGN - Treasury: BIC Codes / Account Numbers for Business Partners
Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
TCORT_EXT_ASSIGN | PARTNR | BP_PARTNR_NEW | Business Partner Number | CHAR | 10 | Mandatory |
TCORT_EXT_ASSIGN | COMPANY_CODE | BUKRS | Company Code | CHAR | 4 | Conditional |
TCORT_EXT_ASSIGN | RECIPIENT TYPE | FTR_RECIPIENT_TYPE | Recipient/Sender Type | CHAR | 15 | Conditional |
TCORT_EXT_ASSIGN | CORR_CATEGORY | FTR_COCAT | Correspondence Object Category | CHAR | 2 | System Generated |
TCORT_EXT_ASSIGN | CONTRACT_TYPE | RANTYP | Contract Type | CHAR | 1 | Conditional |
TCORT_EXT_ASSIGN | PRODUCT_CAT | SANLF | Product Category | NUMC | 3 | Conditional |
TCORT_EXT_ASSIGN | PRODUCT_TYPE | VVSART | Product Type | CHAR | 3 | Conditional |
TCORT_EXT_ASSIGN | TRANSACTION_TYPE | TB_SFHAART | Financial Transaction Type | CHAR | 3 | Conditional |
TCORT_EXT_ASSIGN | ACTIVITY_CAT | TB_SFGZUTY | Transaction Activity Category | NUMC | 2 | Conditional |
TCORT_EXT_ASSIGN | CORR_NUMBER | INT1 | 1 Byte Unsigned Integer | INT1 | 3 | System Generated |
TCORT_EXT_ASSIGN | PROFILE | FTR_PROFILE | Correspondence Profile | CHAR | 15 | Required |
TCORT_EXT_ASSIGN | BPGROUP | FTR_BPGRP | Business Partner Group ID | CHAR | 15 | Required |
TCORT_EXT_ASSIGN | CORR_ADDTYPE | TB_CORR_AD_NEW | Alternative Address for Correspondence | CHAR | 10 | Conditional |
Data Cleansing
For the purpose of the Object 1201- BP Group Assignment for Inbound Correspondence, the data cleansing is not applicable. It is expected that relevant records will be provided in DCT by business.
Conversion Process
The generic high-level process steps for the conversion are as below:
- Extraction:
- Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
- 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
- Transform
- Transform fields by applying the fields and value mapping in the Syniti
- Generate and validate Pre-load files
- Load
- Load the validated Pre-load file using SAP's LTMC or the custom upload program as applicable.
However, with respect to object 1199 - Assignment of Profiles and BP Groups to External Recipients - 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.
Data Privacy and Sensitivity
None
Extraction
Extract data from a source into Syniti. There are 2 possibilities:
- The data exists. Syniti connects to the source and loads the data into Syniti. There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if Syniti; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
- 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 1199-Assignment of Profiles and BP Groups to External Recipients 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 Profile and BP Group Assignment to External Parties for relevant Company Codes | Business |
Selection Screen
Not applicable
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Object 1199- Assignment of Profiles and BP Groups to External Recipients with exception of some fields which require transformation as mentioned in the transformation rule.
1199 – Assignment of Profiles and BP Groups to External Recipients DCT Rules
Note:
- 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 |
TCORT_EXT_ASSIGN - PARTNR | Business Partner Number | This is a Mandatory field. The business partner as per the scope in TRM for this object, which is relevant for BIC assignment. For the DCT purpose, please indicate a business partner number for which the assignment is relevant. If not filled, then the assignment will become applicable to all the business partners. |
TCORT_EXT_ASSIGN - COMPANY_CODE | Company Code | This is a conditional field Refers to the company code for which this assignment is being carried out. Please note: If this field is left blank then a record assigned to BP will become relevant for all Company Codes. Hence in the DCT it is important to provide the company code information. If not filled, then the assignment is applicable to all the Company Codes. |
| TCORT_EXT_ASSIGN-RECIPIENT_TYPE | Receipient/Sender Type | This is a conditional field Any partner or acting party who can receive/send correspondence. For the DCT purpose, please indicate a role if the assignment is to be specific to Counterparty (TR0151). If left blank, then it is applicable to all. |
TCORT_EXT_ASSIGN - CORR_CATEGORY | Correspondence Object Category | This is a system generated field. The system derives this based on the configuration. As the field is system generated. The user should leave this field as blank. Tells the system whether the correspondence is created due some activity on a deal or a securities account transfer. However, here only correspondence for deal activity is relevant |
TCORT_EXT_ASSIGN - CONTRACT_TYPE | Contract Type | This is a conditional field. Please Note: For the DCT purpose, please indicate a value if the assignment is to be specific at the Contract Type level. If left blank, then it will become applicable to all Contract Types. The contract type is an internal key used for the different application areas in Treasury. Here user must specify which contract types the payment detail assignment must be extended. |
TCORT_EXT_ASSIGN - PRODUCT_CAT | Product Category | This is a conditional field Please Note: For the DCT purpose, please indicate a value if the assignment is to be specific at the Product Category level. If left blank, then it will become applicable to all Product Categories. The product category is an internal key that controls processing of the objects defined by the product type. Here user must specify which product categories the profile and BP Group for the said BP must be extended |
TCORT_EXT_ASSIGN - PRODUCT_TYPE | Product Type | This is a conditional field Please Note: For the DCT purpose, please indicate a value if the assignment is to be specific at the Product Type level. If left blank, then it will become applicable to all Product Types. The product type allows you to subdivide a product category. Here the user must specify which profile and BP Group for the said BP must be extended. The product types enable you to give the products company-specific names. |
TCORT_EXT_ASSIGN - TRANSACTION_TYPE | Financial Transaction Type | This is a conditional field. Please Note: For the DCT purpose, please indicate a value if the assignment is to be specific at the Financial transaction Type level. If left blank, then it will become applicable to all Financial transaction Types. 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. Here user must specify which transaction types the profile and BP Group for the said BP must be extended |
TCORT_EXT_ASSIGN - ACTIVITY_CAT | Transaction Activity Category | This is a conditional field. The transaction activity category determines: how the particular activity is interpreted and processed by the system which transitions to activities in other activity categories are possible. Here user must specify which Activity Category the profile and BP Group for the said BP must be extended. Please Note: For the DCT purpose, please indicate a value if the assignment is to be specific at the Transaction Activity Category level. If left blank, then it will become applicable to all Product Categories. |
TCORT_EXT_ASSIGN - CORR_NUMBER | 1 Byte Unsigned Integer | This is a system generated field. The system derives this based on the configuration. As the field is system generated. The user should leave this field as blank. It is the internally assigned number to each unique combination based on the number of profiles assigned. |
TCORT_EXT_ASSIGN - PROFILE | Correspondence Profile | This is a required field. Used as a configuration term to control the communication settings of a group of business partners. |
TCORT_EXT_ASSIGN - BPGROUP | Business Partner Group ID | This is a required field. The applicable value from the available configuration as per design needs to be populated in the DCT. For this object it is relevant for counterparties only. Name of the group of all business partners using the same business settings, such as counter confirmation behaviour of the communication or status relevance of a message. It is used for the business partner group to define the business settings and business attribute definitions of a correspondence for a group of business partners. |
TCORT_EXT_ASSIGN - CORR_ADDTYPE | Alternative Address for Correspondence | This is a conditional field The correspondence address indicates the address to which business partner correspondence should be sent. The Address ID indicated here uniquely identifies a valid business partner address for the business partner master record. If an alternative address is not indicated, the role-dependent standard address is used for creating correspondence. |
Extraction Dependencies
For object 1199- Assignment of Profiles and BP Groups to External Recipients, 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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- Values are transformed according to the rules defined in Syniti
- 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 | TCORT_EXT_ASSIGN | PARTNR | Business Partner NumberAs per Value mapping | Step 1 - Compare the BP Number in the DCT with BP XREFF - BPEXT field Step 2 - Find the BP Number for the match BP XREFF - PARTNER Field Step 3 - Pass the BP Number fetched from BP XREFF in table BUT100 to check if Role "TR0151" is assigned to the BP Step 4 - If the condition matches, then replace the BP Number in the DCT field PARTNR |
02 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | COMPANY_CODE | Company Code | As per Value mapping |
03 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | RECIPIENT TYPE | Recipient/Sender Type | As per DCT |
04 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | CORR_CATEGORY | Correspondence Object Category | System Generated. Leave it blank |
05 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | CONTRACT_TYPE | Contract Type | As per DCT |
06 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | PRODUCT_CAT | Product Category | As per DCT |
07 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | PRODUCT_TYPE | Product Type | As per DCT |
08 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | TRANSACTION_TYPE | Financial Transaction Type | As per DCT |
09 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | ACTIVITY_CAT | Transaction Activity Category | As per DCT |
10 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | CORR_NUMBER | 1 Byte Unsigned Integer | System Generated. Leave it blank |
11 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | PROFILE | Correspondence Profile | As per DCT |
12 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | BPGROUP | Business Partner Group ID | As per DCT |
13 | NA | NA | NA | CONSTRUCT | S4HANA | TCORT_EXT_ASSIGN | CORR_ADDTYPE | Alternative Address for Correspondence | As per DCT |
Transformation Mapping
Mapping Table Name | Mapping Table Description |
Business Partner | Mapping Table for Quantum counterparty/partner code to S4HANA Business Partner |
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. This object should be made relevant only for counter parties i.e. for role TR0151.
Completeness
Task | Action |
Generation of | Mandatory field check.
|
Record Count | Record Count Confirm the record counts in preload summary report
|
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.
|
Business Value Checks |
|
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:
- 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.
- 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. FTR_EXT_ASSIGN | 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 1199-Assignment of Profiles and BP Groups to External Recipients
Configuration
Below configurations should exist
Item # | Configuration Item |
01 | Company Code (Check Table: T001) |
02 | Business Partner (Check Table: BUT000) |
03 | Recipient/Sender Type - Field RECIPIENT_TYPE (Check Table - TCORFC_REC_TYPE) |
04 | Product Category - FieldPRODUCT_CAT (Check Table: TZAF) |
05 | Correspondence profile (Check Table: TCORFC_PROFILE) |
06 | BP Group (Check Table: (Check Table: TCORC_BUSGRP) |
07 | Alternative address for Correspondence (Check Table: TB009) |
Conversion Objects
Object # | Preceding Object Conversion Approach |
CNV- 3018 | Business Partners - FI Vendor (FLVN00) |
CNV- 3021 | Business Partners - Partner with Vendor Account (TR0604) |
| CNV-3040 | Business Partner - Counterparty (TR0151) |
| 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 |
Post-Load Validation
Project Team
The following post load validations will be done by Project Team. This object should be made relevant only for counter parties i.e. for role TR0151.
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 1199 is in scope based on data design and any exception requested by business.
- Only the relevant records for BIC Accounts to BP 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
| Change History | ||
|---|---|---|
|