| Status | |
|---|---|
| Owner | |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach for Object 1207 – IC Agreement. The IC Agreements are managed in PAPM (Profitability and Performance Management). The process of transfer pricing and mark up will be managed in PAPM.
This 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 1207- IC Agreement, to be used in SAP PAPM.
Key tables and fields:
The key tables used for the object IC Agreements are “IC Agreements”, “Transactional Partners”, “Transactional object PLIs”, “Benchmark Studies” and “Benchmark Study Versions”. Please Note: These tables are in PAPM system, which is hosted on public cloud.
The relevant tables and their fields are as below:
Table – IC Agreements
- Description – This field is used to specify a description of the intercompany agreement.
- Document Number - This field is used to specify the document number of the intercompany agreement
- IDUUID – ID - This field is used as the unique identifier for each record.
- PLI Name – This field is used to specify the Profit Level Indicator (PLI). Since this field is an association, it can only take values from the PLI Names master data entity
- PLI Name Comment – This field is used to provide comments or additional information about the PLI.
- Tested Party - This field is used to specify the tested party in the agreement. Since this field is an association, it can only take values from the Tested Parties master data entity
- Transfer Pricing Activity - This field is used to specify the transfer pricing activity related to the agreement. Since this field is an association, it can only take values from the Transfer Pricing Activities master data entity
- Transfer Pricing Method – This field is used to specify the transfer pricing method. Since this field is an association, it can only take values from the Transfer Pricing Methods master data entity.
- Transfer Pricing Method Comment - This field is used to provide comments or additional information about the transfer pricing method.
- Valid From - This field is used to specify the start date for the validity of the agreement
- Valid To – This field is used to specify the end date for the validity of the agreement.
Table – Transactional Partners
- Benchmark Study – This field is used to specify which version of the benchmark study associated with the transactional partner. Since this field is an association, it can only take values from the Benchmark Studies master data entity.
- Business Division – This field is used to specify the business division of the transactional partner. Since this field is an association, it can only take values from the Business Divisions master data entity.
- Company – This field is used to specify the company associated with the transactional partner. Since this field is an association, it can only take values from the Companies master data entity
- Functional and Risk Profile – This field is used to specify the functional and risk profile of the transactional partner of the company, based on the roles, responsibilities, and associated risks. Since this field is an association, it can only take values from the Functional and Risk Profiles master data entity.
- IC Agreement Number – This field is used to specify the number of the IC agreement that is used for the transactional partner. Since this field is an association, it can only take values from the IC Agreements master data entity.
- IDUUID – This field is used to uniquely identify each record
- IS Sender – This field is used to indicate whether the transactional partner is a sender in the transaction.
- IS Receiver – This field is used to indicate whether the transactional partner is a receiver in the transaction.
- IS Tested Entity – This field is used to specify whether the transactional partner is a tested entity or not
Table – Transactional Object PLIs
- IC Transactional Partner – This field is used to specify the transactional partner in an IC agreement. Since this field is an association, it can only take values from the Transactional Partners master data entity.
- IDUUID – This field is used to uniquely identify each record
- PLI Value comment – This field is used to provide additional comments or details about the PLI value
- Target PLI Value – This field is used to specify the target value for the product group's PLI
- Transactional Object – This field is used to specify the transactional object associated with the PLI. Since this field is an association, it can only take values from the Transactional Objects master data entity.
Table – Bench Mark Studies
- Description – This field is used to provide a description of the benchmark study.
- Geographic Region – This field is used to specify the geographic region associated with the benchmark study. Since this field is an association, it can only take values from the Geographic Regions master data entity.
- IDUUID – This field is used to uniquely identify each record.
- Industry – This field is used to specify the industry related to the benchmark study. Since this field is an association, it can only take values from the industries master data entity.
- PLI Name – This field is used to specify the Profit Level Indicator (PLI) name for the benchmark study. Since this field is an association, it can only take values from the PLI Names master data entity.
- Transfer Pricing Activity – This field to specify the transfer pricing activity. Since this field is an association, it can only take values from the Transfer Pricing Activities master data entity.
- Transfer Pricing Method – This field is used to specify the transfer pricing method. Since this field is an association, it can only take values from the Transfer Pricing Methods master data entity
Table – Benchmark Study Versions
- Benchmark Study Name – This field is used to specify the name of the benchmark study associated with the version. Since this field is an association, it can only take values from the Benchmark Studies master data entity.
- Benchmark Study Version - This field is used to specify the version of benchmark study that is used.
- Start Year - This field is used to specify the start year of the benchmark study version.
- End Year – This field is used to specify the end year of the benchmark study version.
- IDUUID – This field is used to uniquely identify each record
- PLI First Quartile - This field to specify the 25th percentile of the profit level indicator, setting the lowest boundary of the arm’s length range for acceptable profitability.
- PLI Maximum - This field is used to identify the highest value of the profit level indicator in a benchmark study.
- PLI Median – This field is used to determine the median profit level indicator.
- PLI Minimum - This field is used to identify the lowest value of profit level indicator in a benchmark study.
- PLI Third Quartile - This field is used to specify the 75th percentile of the profit level indicator, setting the upper boundary of the arm’s length range for acceptable profitability.
- Study Version Comment – This field is used to provide any comments or details regarding the benchmark study version.
The transfer pricing function and IC agreements are planned to be carried out in PAPM. Currently in legacy, the transfer pricing is an offline activity managed through excel and PDF’s. The target design is, that the business will provide information in the templates and this will be uploaded to PAPM by the PAPM functional team. The template will be provided in a DCT page and stored in Syniti; however, the data will not be loaded via Syniti.
Conversion Scope
The scope of this document covers the approach for converting active IC Agreements from Legacy Source Systems into PAPM following the MDS for Object-1207 - DD-FUN-050 Master Data Standard-3XXX – Intercompany Agreements.
The relevancy criteria are 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 |
Excel and PDF’s | IC Agreements | XXXX <TBC> | PAPM | XXXX <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 (Excel / PDFs), the below areas need special handling:
- The relevant records to be provided in a predefined template and stored in Syniti for Transformation
Target Design
The technical design of the target for this object will be as below.
Please Note: The data type length is not provided in the MDS as there is no length specification in the respective tables in PAPM system. However, during discussion with Nixon it was understood that the maximum length provided by the system is 23 and hence this has been considered in the conversion spec.
Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
IC Agreements | Description | N/A | Description | CHAR | 23 | Required |
IC Agreements | Document Number | N/A | Document Number | CHAR | 23 | Required |
IC Agreements | IDUUID | N/A | ID | CHAR | 23 | System Generated |
IC Agreements | PLI Name | N/A | PLI Name | CHAR | 23 | Required |
IC Agreements | PLI Name Comment | N/A | PLI Name Comment | CHAR | 23 | Optional |
IC Agreements | Tested Party | N/A | Tested Party | CHAR | 23 | Required |
IC Agreements | Transfer Pricing Activity | N/A | Transfer Pricing Activity | CHAR | 23 | Required |
IC Agreements | Transfer Pricing Method | N/A | Transfer Pricing Method | CHAR | 23 | Required |
IC Agreements | Transfer Pricing Method Comment | N/A | Transfer Pricing Method Comment | CHAR | 23 | Optional |
IC Agreements | Valid From | N/A | Valid From | DATE | 8 | Required |
IC Agreements | Valid To | N/A | Valid To | DATE | 8 | Required |
Transactional Partners | Benchmark Study | N/A | Benchmark Study | CHAR | 23 | Required |
Transactional Partners | Business Division | N/A | Business Division | CHAR | 23 | Required |
Transactional Partners | Company | N/A | Company | CHAR | 23 | Required |
Transactional Partners | Functional and Risk Profile | N/A | Functional and Risk Profile | CHAR | 23 | Required |
Transactional Partners | IC Agreement Number | N/A | IC Agreement Number | CHAR | 23 | Required |
Transactional Partners | ID | N/A | ID | CHAR | 23 | Required |
Transactional Partners | IS Sender | N/A | IS Sender | CHAR | 23 | Required |
Transactional Partners | IS Receiver | N/A | IS Receiver | CHAR | 23 | Required |
Transactional Partners | IS Tested Entity | N/A | IS Tested Entity | CHAR | 23 | Required |
Transactional Object PLIs | IC Transactional Partner | N/A | IC Transactional Partner | CHAR | 23 | Required |
Transactional Object PLIs | IDUUID | N/A | ID | CHAR | 23 | Required |
Transactional Object PLIs | PLI Value comment | N/A | PLI Value comment | CHAR | 23 | Optional |
Transactional Object PLIs | Target PLI Value | N/A | Target PLI Value | CHAR | 23 | Required |
Transactional Object PLIs | Transactional Object | N/A | Transactional Object | CHAR | 23 | Required |
Benchmark Studies | Description | N/A | Description | CHAR | 23 | Required |
Benchmark Studies | Geographic Region | N/A | Geographic Region | CHAR | 23 | Required |
Benchmark Studies | IDUUID | N/A | IDUUID | CHAR | 23 | Required |
Benchmark Studies | Industry | N/A | Industry | CHAR | 23 | Required |
Benchmark Studies | PLI Name | N/A | PLI Name | CHAR | 23 | Required |
Benchmark Studies | Transfer Pricing Activity | N/A | Transfer Pricing Activity | CHAR | 23 | Required |
Benchmark Studies | Transfer Pricing Method | N/A | Transfer Pricing Method | CHAR | 23 | Required |
Benchmark Study Versions | Benchmark Study Name | N/A | Benchmark Study Name | CHAR | 23 | Required |
Benchmark Study Versions | Benchmark Study Version | N/A | Benchmark Study Version | CHAR | 23 | Required |
Benchmark Study Versions | Start Year | N/A | Start Year | NUMC | 4 | Required |
Benchmark Study Versions | End Year | N/A | End Year | NUMC | 4 | Required |
Benchmark Study Versions | IDUUID | N/A | ID | CHAR | 23 | Required |
Benchmark Study Versions | PLI First Quartile | N/A | PLI First Quartile | CHAR | 23 | Required |
Benchmark Study Versions | PLI Maximum | N/A | PLI Maximum | CHAR | 23 | Required |
Benchmark Study Versions | PLI Median | N/A | PLI Median | CHAR | 23 | Required |
Benchmark Study Versions | PLI Minimum | N/A | PLI Minimum | CHAR | 23 | Required |
Benchmark Study Versions | PLI Third Quartile | N/A | PLI Third Quartile | CHAR | 23 | Required |
Benchmark Study Versions | Study Version Comment | N/A | Study Version Comment | CHAR | 23 | Optional |
Data Cleansing
For the purpose of the Object 1207- IC Agreements, the data cleansing activity is not applicable. It is expected that relevant records will be provided in DCT by business.
Conversion Process
For object 1207 – IC Agreements - the conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business. The data collected in the template will be uploaded into PAPM by the PAPM functional team. Syniti will be only used for capturing the data in the DCT.
Data Privacy and Sensitivity
None
Extraction
For object 1207- IC Agreement, the extraction is not applicable as this will be a DCT provided by business.
Selection Screen
Not applicable
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for object 1207- IC Agreements data with exception of some fields which require transformation as mentioned in the transformation rule.
1207- IC Agreements - DCT Rules
Field Name | Field Description | Rule |
Description | Description | This is a Required field |
Document Number | Document Number | This is a Required field Provide the document number of the intercompany agreement |
IDUUID | ID | This is a System Generated field |
PLI Name | PLI Name | This is a Required field |
PLI Name Comment | PLI Name Comment | This is an Optional field |
Tested Party | Tested Party | This is a Required field Please enter values as maintained in the tested parties master data entity |
Transfer Pricing Activity | Transfer Pricing Activity | This is a Required field Please enter values as maintained in the transfer pricing activity master data entity |
Transfer Pricing Method | Transfer Pricing Method | This is a Required field Please enter values as maintained in the transfer pricing method master data entity |
Transfer Pricing Method Comment | Transfer Pricing Method Comment | This is a Optional field |
Valid From | Valid From | This is a Required field Enter the start date for the validity of the agreement. |
Valid To | Valid To | This is a Required field Enter the end date for the validity of the agreement |
Benchmark Study | Benchmark Study | This is a Required field Please enter values as maintained in the Benchmark studies master data entity |
Business Division | Business Division | This is a Required field Please enter values as maintained in the Business Division master data entity |
Company | Company | This is a Required field Please enter values as maintained in the company master data entity |
Functional and Risk Profile | Functional and Risk Profile | This is a Required field Please enter values as maintained in the functional and risk profile master data entity |
IC Agreement Number | IC Agreement Number | This is a Required field Please enter values as maintained in the IC Agreements master data entity |
ID | ID | This is a Required field |
IS Sender | IS Sender | This is a Required field Indicate whether the transactional partner is a sender in the transaction. |
IS Receiver | IS Receiver | This is a Required field Indicate whether the transactional partner is a receiver in the transaction. |
IS Tested Entity | IS Tested Entity | This is a Required field Specify whether the transactional partner is a tested entity or not |
IC Transactional Partner | IC Transactional Partner | This is a Required field Please enter values as maintained in the transactional Partners master data entity. |
IDUUID | ID | This is a Required field |
PLI Value comment | PLI Value comment | This is an Optional field |
Target PLI Value | Target PLI Value | This is a Required field Specify the target value for the product group's PLI |
Transactional Object | Transactional Object | This is a Required field Please enter values as maintained in the transactional object master data entity. |
Description | Description | This is a Required field Provide the description of the benchmark study |
Geographic Region | Geographic Region | This is a Required field Please enter values as maintained in the Geographic region object master data entity. |
IDUUID | IDUUID | This is a Required field |
Industry | Industry | This is a Required field Please enter values as maintained in the Industries master data entity. |
PLI Name | PLI Name | This is a Required field Please enter values as maintained in the PLI names master data entity. |
Transfer Pricing Activity | Transfer Pricing Activity | This is a Required field Please enter values as maintained in the transfer pricing activities master data entity. |
Transfer Pricing Method | Transfer Pricing Method | This is a Required field Please enter values as maintained in the transfer pricing method master data entity. |
Benchmark Study Name | Benchmark Study Name | This is a Required field Please enter values as maintained in the Benchmark Study Name object master data entity. |
Benchmark Study Version | Benchmark Study Version | This is a Required field Specify the version of benchmark study that is used. |
Start Year | Start Year | This is a Required field Specify the start year of the benchmark study version |
End Year | End Year | This is a Required field Specify the end year of the benchmark study version. |
IDUUID | ID | This is a Required field |
PLI First Quartile | PLI First Quartile | This is a Required field Specify the 25th percentile of the profit level indicator, setting the lowest boundary of the arm’s length range for acceptable profitability. |
PLI Maximum | PLI Maximum | This is a Required field Enter the highest value of the profit level indicator in a benchmark study. |
PLI Median | PLI Median | This is a Required field |
PLI Minimum | PLI Minimum | This is a Required field Enter the lowest value of profit level indicator in a benchmark study. |
PLI Third Quartile | PLI Third Quartile | This is a Required field Specify the 75th percentile of the profit level indicator, setting the upper boundary of the arm’s length range for acceptable profitability. |
Study Version Comment | Study Version Comment | This is an Optional field Provide any comments or details regarding the benchmark study version. |
Extraction Dependencies
For object 1207- IC Agreements no extraction dependencies are applicable as this is DCT and the object is Master Data by nature.
Transformation
The data will be loaded to PAPM and hence the correct values after transformation will need to be provided by the business in the DCT page.
Transformation Run Sheet
Not Applicable
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 | PAPM | IC Agreements | Description | Description | As per DCT |
02 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | Document Number | Document Number | As per DCT |
03 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | ID | IDUUID | As per DCT |
04 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | PLI Name | PLI Name | As per DCT |
05 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | PLI Name Comment | PLI Name Comment | As per DCT |
06 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | Tested Party | Tested Party | As per DCT |
07 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | Transfer Pricing Activity | Transfer Pricing Activity | As per DCT |
08 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | Transfer Pricing Method | Transfer Pricing Method | As per DCT |
09 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | Transfer Pricing Method Comment | Transfer Pricing Method Comment | As per DCT |
10 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | Valid From | Valid From | As per DCT |
11 | NA | NA | NA | CONSTRUCT | PAPM | IC Agreements | Valid To | Valid To | As per DCT |
12 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | Benchmark Study | Benchmark Study | As per DCT |
13 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | Business Division | Business Division | As per DCT |
14 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | Company | Company | As per DCT |
15 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | Functional and Risk Profile | Functional and Risk Profile | As per DCT |
16 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | IC Agreement Number | IC Agreement Number | As per DCT |
17 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | ID | ID | As per DCT |
18 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | IS Sender | IS Sender | As per DCT |
19 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | IS Receiver | IS Receiver | As per DCT |
20 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Partners | IS Tested Entity | IS Tested Entity | As per DCT |
21 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Object PLIs | IC Transactional Partner | IC Transactional Partner | As per DCT |
22 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Object PLIs | ID | IDUUID | As per DCT |
23 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Object PLIs | PLI Value comment | PLI Value comment | As per DCT |
24 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Object PLIs | Target PLI Value | Target PLI Value | As per DCT |
25 | NA | NA | NA | CONSTRUCT | PAPM | Transactional Object PLIs | Transactional Object | Transactional Object | As per DCT |
26 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Studies | Description | Description | As per DCT |
27 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Studies | Geographic Region | Geographic Region | As per DCT |
28 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Studies | IDUUID | IDUUID | As per DCT |
29 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Studies | Industry | Industry | As per DCT |
30 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Studies | PLI Name | PLI Name | As per DCT |
31 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Studies | Transfer Pricing Activity | Transfer Pricing Activity | As per DCT |
32 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Studies | Transfer Pricing Method | Transfer Pricing Method | As per DCT |
33 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | Benchmark Study Name | Benchmark Study Name | As per DCT |
34 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | Benchmark Study Version | Benchmark Study Version | As per DCT |
35 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | Start Year | Start Year | As per DCT |
36 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | End Year | End Year | As per DCT |
37 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | ID | ID | As per DCT |
38 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | PLI First Quartile | PLI First Quartile | As per DCT |
39 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | PLI Maximum | PLI Maximum | As per DCT |
40 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | PLI Median | PLI Median | As per DCT |
41 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | PLI Minimum | PLI Minimum | As per DCT |
42 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | PLI Third Quartile | PLI Third Quartile | As per DCT |
43 | NA | NA | NA | CONSTRUCT | PAPM | Benchmark Study Versions | Study Version Comment | Study Version Comment | As per DCT |
Transformation Mapping
Not Applicable
Transformation Dependencies
Not Applicable
Pre-Load Validation
Project Team
The Pre Load validations are performed by the Project Team.
Completeness
Task | Action |
Generation of | Mandatory Field Check.
|
Record Count | Record Count Confirm the record counts in preload summary report
|
Business Confirmation | Business Representatives to validate the pre-load file Agree with functional team on the next steps for erroneous records corrections. |
Accuracy
Task | Action |
Mandatory field mapping and transformation | Ensure that the data provided in the DCT page is accurate and as per the proposed design. |
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. |
Key Fields Check | Check IC Agreement numbers, validity etc. |
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:
- The functional team will upload the template into the PAPM system.
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. | Functional 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. | Functional team |
03 | Proceed with the full load if steps one and two were succeed else fix the issue with records | Functional team |
04 | Validate few records loaded by accessing standard transactions in PAPM | Functional team |
05 | Generate post load report if step 5 is validated | Functional team |
06 | Log errors as defects, if any and address resolutions. Close defects. | Functional team |
07 | Resolve defects by reupload and re-generate post load reports if necessary. | Functional 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. | Functional team |
Load Phase and Dependencies
The load phase for the object 1207- IC Agreements is Pre-Cutover Phase 5
Configuration
All relevant configurations should exist in the PAPM system.
Conversion Objects
Not Applicable
Error Handling
All errors will be rectified in the PAPM system
Post-Load Validation
Project Team
The following post load validations will be done by the 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 its 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. Post load report will be generated from the PAPM system. 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 PAPM functional Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations Business may also run transaction codes in PAPM to spot check few records. |
Accuracy
Task | Action |
Field Checks | Check the key fields such as IC Agreement number, validity etc. |
Key Assumptions
- All relevant configuration will be available in the PAPM system.
- Business will provide the DCT at a granular level.
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.