| Status |
| ||||||||
| Owner | Soumen Laru | ||||||||
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach of Profit Centres into S/4 HANA. Profit Centres
The document details out the field list, extraction criteria, scoping, mapping of cost centre object
Profit Centres will be constructed based on the target design and a DCT(Constructed data based on Data Collection Template) will be provided to Syniti for subsequent processing. Along with the DCT, a mapping file of legacy(ECC) to target(S4) will be provided for dependent master and transaction objects.Cost Centres will be extracted from Source and based on the list of cost centres from the cost centre mapping sheet, target cost centre data file will be
Conversion Scope
Profit Centres which will be listed as part of scope list with new numbering will be in scope of migration.
List of source systems and approximate number of recordsNote: All the Profit Centres to be migrated will be collected. Therefore, Profit Centres are not going to be extracted from source and details given below is given for information purpose only.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Profit Centre | 6,423 | S4HANA | TBD |
| WP2 | Profit Centre | 5,768 | S4HANA | TBD |
Additional Information
Multi-language Requirement
In the Syensqo Profit Centres, the following four language keys must be maintained:
- English (EN)
- French (FR)
- Italian (IT)
- Chinese (ZN)
Note: For certain countries it may be required to also maintain account descriptions for certain Profit Centres in local language as per regulatory requirement (e.g. Japanese) in the respective country. Such requests must be backed by supporting evidence of the underlying regulatory requirement.
Such data will be collected as part of DCT for the translation texts for Profit Centres.
Document Management
Legal Requirement
Special Requirements
Target Design
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Label | Data Type | Length | Requirement | Syensqo Requirement R = Required : Mandatory field. O = Optional: Not mandatory. If a value is entered it doesn't impact Business Process. C = Conditional: Not mandatory. If a value is entered it impacts Business Process or Reporting. S = System: System generates the value. NU = Not Used |
|---|---|---|---|---|---|---|---|
| CEPC | PRCTR | PRCTR | Profit Center | CHAR | 10 | Organizational unit in controlling used for internal reporting and responsibility accounting. The Profit center represents in syensqo context either a Plant or a GBS 'non Plant'. The Syensqo PC codification must follow the naming convention. "1 + 4 "" Digit #1 = GBU Indicator S=SPEC. POLYMERS or C=COMPOSITE MATERIALS or N=NOVECARE or T=TECHNOLOGY SOLUTIONS or B=CBS From digit 2 to 5 : 4 char. Company Code OR Plant Code. Illustration : S1001 | R |
| CEPC | DATBI | DATBI | Valid To Date | DATS | 8 | Date until which the Profit Center is valid. | R |
| CEPC | KOKRS | KOKRS | Controlling Area | CHAR | 4 | Identifies a self-contained organizational structure for which costs and revenues can be managed. Only 1 controlling used for all legal entities. Same value across all systems (same in 3 boxes : Global instance + Composites + China). | R |
| CEPC | DATAB | DATAB | Valid-From Date | DATS | 8 | Date from which the Profit Center is valid. | R |
| CEPC | VERAK | VERAPC | Person Responsible for Profit Center | CHAR | 20 | Name or ID of the person responsible for managing the Profit Center. |
| NU | ||||||
| CEPC | VERAK_USER | VERAPC_USER | User Responsible for the Profit Center | CHAR | 12 | SAP user ID of the responsible person. |
| NU | ||||||
| CEPC | WAERS | WAERS | Currency Key | CUKY | 5 | Currency used in the Profit Center. Will follow the legal entity one. |
| NU | ||||||
| CEPC | LAND1 | LAND1 | Country Key | CHAR | 3 | Country code related to the Profit Center's location. |
| C | ||||||
| CEPC | NAME1 | NAME1_GP | Name 1 | CHAR | 35 | First line of the name or company name of the Profit Center. Description of the Profit center. |
| NU | ||||||
| CEPC | NAME2 | NAME2_GP | Name 2 | CHAR | 35 | Second line of the name or company name. |
| NU | ||||||
| CEPC | NAME3 | NAME3_GP | Name 3 | CHAR | 35 | Third line of the name or additional details. |
| NU | ||||||
| CEPC | NAME4 | NAME4_GP | Name 4 | CHAR | 35 | Fourth line of the name or additional details. |
| NU | ||||||
| CEPC | ORT01 | ORT01_GP | City | CHAR | 35 | City name in the Profit Center address. |
| C | ||||||
| CEPC | ORT02 | ORT02_GP | District | CHAR | 35 | District or region in the address. |
| C | ||||||
| CEPC | STRAS | STRAS_GP | Street and House Number | CHAR | 35 | Street name and house number of the Profit Center location. |
| NU | ||||||
| CEPC | PFACH | PFACH | PO Box | CHAR | 10 | PO Box address. |
| NU | ||||||
| CEPC | PSTLZ | PSTLZ | Postal Code | CHAR | 10 | Postal code for the street address. |
| NU | ||||||
| CEPC | PSTL2 | PSTL2 | P.O. Box Postal Code | CHAR | 10 | Postal code associated with the PO Box. |
| NU | ||||||
| CEPC | SPRAS | SPRAS | Language Key | LANG | 1 | Language key used in texts and descriptions. |
| R | ||||||
| CEPC | TELBX | TELBX | Telebox number | CHAR | 15 | Telebox number (rarely used). |
| NU | ||||||
| CEPC | TELF1 | TELF1 | First telephone number | CHAR | 16 | Primary contact phone number. |
| NU | ||||||
| CEPC | TELF2 | TELF2 | Second telephone number | CHAR | 16 | Secondary contact phone number. |
| NU | ||||||
| CEPC | TELFX | TELFX | Fax Number | CHAR | 31 | Fax number. |
| NU | ||||||
| CEPC | TELTX | TELTX | Teletex number | CHAR | 30 | Teletex number (obsolete). |
| NU | ||||||
| CEPC | TELX1 | TELX1 | Telex number | CHAR | 30 | Telex number (obsolete). |
| NU | |||||||
| CEPC | KHINR | PHINR | Profit center area | CHAR | 12 | Profit center area | NU |
| CEPC | BUKRS | BUKRS | Company Code | CHAR | 4 | Associated company code for reporting. |
| NU | ||||||
| CEPC | TXJCD | TXJCD | Tax Jurisdiction | CHAR | 15 | Tax jurisdiction code used for tax reporting. |
| NU | ||||||
| CEPC | REGIO | REGIO | Region (State, Province, County) | CHAR | 3 | State or regional subdivision (used in address). |
| NU | |||||||
| CEPC | LOCK_IND | LOCK_IND | Lock indicator | CHAR | 1 | Indicates if the Profit Center is locked for processing. If locked : no posting possible. | C |
| CEPCT |
| KTEXT | KTEXT | Name |
| CHAR |
| 20 | Profit |
| Center Name | R | ||
| CEPCT | LTEXT | LTEXT | Long Text |
| CHAR | 40 | Profit Center Long Text | R |
| CEPCT | MCTXT | MCTXT | Profit Center Text |
| CHAR | 20 | Profit Center Text |
| R |
Data Cleansing
ID
Criticality
Error Message/Report Description
Rule
Output
Source System
1.
Can load, but business process will fail
Lock any Profit Centre not being used for last 5 years
TBD
Report
PF2 / WP2
Note: Cleansing mau not be necessary as the ex
Note: Cleansing is applicable only for business and as the data for this object is collected, cleansing is not relevant for data conversion. It just helps business to reduce the mapping requirements.
ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
N/A |
Conversion Process
Conversion Process
The high-level process is represented by the diagram below:
Note: When Data Source denotes DCT, no relevancy and extract rules to be applied in Syniti tool. DCT records will be collected by business Data Consultant.
Data Privacy and Sensitivity
Extraction
Extract data from a source into . There are 2 possibilities:
- The data exists. connects to the source and loads the data into . There are 3 methods:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in
The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads
Extraction Run Sheet
Req #
Requirement description
Team responsible
1.
Ensure source tables CEPC and CEPCT are extracted in tool according to the agreed cut-off date in the project plan
Ensure DCT is collected for the Profit Centres based on the collection template
Data team
2.
Perform preliminary completeness check documented in section 5.2.8.1.1
Data team
3.
Raise issues as defects if Req # 1 to 2 are not met
Data team
4.
Repeat Req # 1 to 3 if required
Data team
5.
Report extraction result to person in charge of APOI conversion
Data team
Selection Screen
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules
Extraction Run Sheet
Req # | Requirement description | Team responsible |
1. | Ensure DCT is collected for the Profit Centres based on the collection template | Data team |
Selection Screen
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| N/A |
Data Collection Template (DCT)
Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.DCT Rules and will be used by the data collectors.
Note: Constructed data will be imported into ADM Data Construction page.
There will be two pages -
1. Main page to contain the Profit Centre details with EN Language key Description
2. Detailed Page will contain descriptions in various languages as they are collected.
| Table Name | Field Name | Field description | Rule |
| CEPC | PRCTR | Profit Center | This field must be 5 digits. It must follow the naming convention described in governance rules applied |
| CEPC | DATBI | Valid To Date | 31.12.9999 by default. If a PC has a end date : this field can be updated with the accurate values. Select Last day of a month period at least (not a date during a period). |
| CEPC | KOKRS | Controlling Area | 1 unique value for all PC. |
| CEPC | DATAB | Valid-From Date | Date of the creation of the Prof.center during the run. Date of the go live for the ones Mass loaded as part of the Syway cut over |
| CEPC | LAND1 | Country Key | Collected as required |
| CEPC | ORT01 | City | Collected as required |
| CEPC | ORT02 | District | Collected as required |
| CEPC | SPRAS | Language Key | Collected as required |
| CEPC | KHINR | Profit center area | Collected as required |
| CEPC | LOCK_IND | Lock indicator | Case to tick if a Profit center must be blocked for posting : obsolete PC or PC created by mistake. |
Descriptions will be collected on multiple languages and therefore a detail page to created and linked to the main page
| Table Name | Field Name | Field description | Rule |
| CEPC | KOKRS | Controlling Area | 1 unique value for all PC. |
| CEPC | PRCTR | Profit Center | This field must be 5 digits. It must follow the naming convention described in governance rules applied |
| CEPCT | DATBI | Valid To Date | |
| CEPCT | SPRAS | Language Key | In the Syensqo Profit centers, the following four language keys must be maintained: - English (EN) - French (FR) - Italian (IT) - Chinese (ZN) Additionally, fill in the name and description for the language key; |
| CEPCT | KTEXT | Name | Max Length: 20 |
| CEPCT | LTEXT | Long Text | Max Length: 40 |
| CEPCT | MCTXT | Profit Center Text | Max Length: 20 |
Extraction Dependencies
Item # | Step description | Team responsible |
1. | N/A |
Transformation
The Target fields are mapped to the applicable DCT field that will be its source.
Note: as this object is DCT, the mapping rule for all the fields is 'Copy' as described in the transform rule section. However, some reports are to be created and executed to ensure integrity in the data collected in DCT as described in 'Pre-load Data Validation' section.
This step identifies the transformation activity required to allow to make the data Target ready:
- Prepare target-ready data in the target structure and format that is required for loading via prescribed Load Tool in the load section.
- Produce the preload reports as requested in the 'Preload Data Validation' section.
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 toolMigrate. | Data team |
2. | In tool, select the Trial Balance object PY. | Data team |
3. | Go to Process Area Launch and Process the Object - Trial Balance object - R4 Trial Balance PY. | Data team |
4. | Launch the Objects to execute transformation. | Data team |
5. | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Data team |
6. | Generate Pre-Load reports . | Data team |
7. | Generate data load count. | Data team |
8. | Log errors as defects, if any and address resolutions. Close defects. | Data team |
9. | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
10. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
11. | Analyse and resolve any pre-load defects logged by business. | Data team |
12. | Repeat steps 6 to 11 if necessary | Data team |
13. | 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 |
| 1 | DCT/ECC | CEPC | PRCTR | Profit Center | S/4HANA | CEPC | PRCTR | Profit Center | Copy From DCT as-is |
| 2 | DCT/ECC | CEPC | DATBI | Valid To Date | S/4HANA | CEPC | DATBI | Valid To |
Field Name | Field description | Rule |
CEPC-PRCTR | Profit Centre | Business to enter content as per data type and length permitted |
Suggestion to add:
Decimal validation - Check table TCURX for the document currency key and if Decimals (TCURX-CURRDEC) is ‘0’, validate that no decimal value is populated.
Extraction Dependencies
Item # | Step description | Team responsible |
1. | Any period / year end close activities have been fully completed | Business |
2. | Reconciliation for intercompany payables have been completed, and adjustment made in legacy SAP system | Business |
3. | Reconciliation of migrated Purchase Order is completed before the extraction of Accounts Payable Open Items | Business and Data |
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:
- 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
- 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 toolMigrate. | Data team |
2. | In tool, select the Trial Balance object PY. | Data team |
3. | Go to Process Area Launch and Process the Object - Trial Balance object - R4 Trial Balance PY. | Data team |
4. | Launch the Objects to execute transformation. | Data team |
5. | Monitor the transformation progress and ensure performance and completion is within allowed timeframe | Data team |
6. | Generate Pre-Load reports . | Data team |
7. | Generate data load count. | Data team |
8. | Log errors as defects, if any and address resolutions. Close defects. | Data team |
9. | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
10. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
11. | Analyse and resolve any pre-load defects logged by business. | Data team |
12. | Repeat steps 6 to 11 if necessary | Data team |
13. | Proceed to pre-load validations | Data team |
Transformation Rules
| Date | Copy From DCT as-is |
| 3 | DCT/ECC | CEPC |
| KOKRS | Controlling Area | S/4HANA | CEPC |
| KOKRS | Controlling Area | Copy From DCT as-is |
| 4 | DCT/ECC | CEPC |
| DATAB | Valid-From Date |
| S/4HANA | CEPC |
| DATAB | Valid-From Date | Copy From DCT as-is |
| 8 | DCT/ECC | CEPC |
| LAND1 |
| Country Key | S/4HANA | CEPC |
| LAND1 |
| Country Key | Copy From DCT as-is |
| 13 | DCT/ECC | CEPC |
| ORT01 |
| City | S/4HANA | CEPC |
| ORT01 |
| City | Copy From DCT as-is |
| 14 | DCT/ECC | CEPC |
| ORT02 |
| District | S/4HANA | CEPC |
| ORT02 |
| District | Copy From DCT as-is |
| 19 | DCT/ECC | CEPC |
| SPRAS |
| Language Key | S/4HANA | CEPC |
| SPRAS |
| Language Key | Copy From DCT as-is |
| 27 | DCT/ECC | CEPC |
| KHINR | Profit center area | S/4HANA | CEPC |
| KHINR | Profit center area |
| Copy From DCT as- |
| is |
| 30 | DCT/ECC | CEPC |
| LOCK_IND | Lock indicator | S/4HANA | CEPC |
| LOCK_IND | Lock indicator |
| Copy From DCT as-is |
| 31 | DCT/ECC |
| CEPCT |
| KTEXT |
| Name | S/4HANA |
| CEPCT |
| KTEXT |
| Name | Copy From DCT as-is |
| 32 | DCT/ECC |
| CEPCT |
| LTEXT |
| Long Text | S/4HANA |
| CEPCT |
| LTEXT |
| Long Text | Copy From DCT as-is |
| 33 | DCT/ECC |
| CEPCT |
| MCTXT | Profit Center Text | S/4HANA |
| CEPCT |
| MCTXT | Profit Center Text |
| Copy From DCT as-is |
Transformation Mapping
Mapping Table Name | Mapping Table Description |
Profit Centre | Mapping of legacy Profit Center to target system value |
Person Responsible | Mapping of legacy Person Responsible to New Person Responsible |
User ID | Mapping of legacy User ID |
Hierarchy Group | Mapping of Legacy Hierarchy Group to Hierarchy Group |
Transformation Dependencies
List the steps that need to occur before transformation can commenceEnsure Profit Centre hierarchies are loaded into target S/4HANA
Pre-Load Validation
Project Team
Completeness
Task
Action
Generation of
Pre-load reports
Mandatory field check.
Profit Centres are mapped to new values
Profit Centre Hierarchy Mapped to new values
Person Responsible / HR positions mapped to new values
Record Count
Confirm the record counts in preload summary report
Total Records:
Valid Records:
Invalid 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.
Review the data report to ensure mapping value is not missing in tool.
Capture errors in the Data Error report.
Business
Completeness
Confirm the Preload File contains all the records in scope of migration ( Based on list of profit centres mapped from old to new )
Accuracy
Transformation Mapping
Note: No Mapping applicable here as this data object is a collect object.
Mapping Table Name | Mapping Table Description |
N/A |
Transformation Dependencies
List the steps that need to occur before transformation can commence| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Ensure all the fields and values are imported into ADM Construction page correctly | Data Team |
| 2 | Ensure Profit Centre hierarchies are loaded into target S/4HANA | Data Team |
Pre-Load Validation
Project Team
Completeness
Task | Action |
Generation of | Mandatory field check.
|
Record Count | Record Count
|
Accuracy
Task | Action |
Mandatory field mapping and transformation | Review the data report to ensure mapping value is not missing in tool. |
Business
Completeness
| Task | Action |
|---|---|
| Verify record count in Pre-load reports by region | Confirm the Preload File contains all the records in scope of migration based on the DCT (Data Construction Template) |
Accuracy
| Task | Action |
|---|---|
| Conversion accuracy | Verify Profit Centres are transformed accurately as per endorsed transformation/mapping rules. Review error reports in tool for any mismatch or missing transformed values. |
Load
Loading will be done through migration cockpit and therefore, data from the transformation export view to be exported into the load file format.
export views to be prepared based on the field list from the load template attached.
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
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 using LTMC cockpit object of Profit Centre.
- 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_DCT, 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)
Additional export view for the descriptions in additional languages to be created as is from detail page DCT
Note: Description translation will be loaded using tcode SE63. LSMW will be created based on the tcode SE63 to enable mass upload of this data. However, further checks will be done to check if some Fiori App could be used for uploading.
Load Run Sheet
Item | Step description | Team responsible |
1 | Ensure the load tools are transported into the correct tool instance. | Data team |
2 | Ensure DCTs and all required mappings are submitted and complete | Data team |
3 | Ensure Pre-load sign-offs are obtained. | Data team |
4 | Execute upload of Profit Centre Object using Migration Cockpit Object for Profit Centre Upload | Data team |
5 | Generate the post load reports in tool. | Data team |
6 | Log errors as defects, if any and address resolutions. Close defects. | Data team |
7 | Resolve defects by reupload and re-generate post load reports if necessary. | Data team |
8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
9 | Repeat steps 5 to 7 if necessary. | Data team |
Load Phase and Dependencies
Configuration
Item # | Configuration item |
1. | Controlling Area |
2. | Standard Hierarchy is Maintained |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1068 | Profit Centre Group (Alt, Std Hierarchy) |
Error Handling
Error type | Error description | Action taken |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Reconciliation of Record Count | Check Record count between DCT, Preload file and target extracted data from tables CEPC and CEPCT. A Summary report to be added in the post-load report |
Accuracy
| Task | Action |
|---|---|
| Check values in key fields for accuracy | Refer to the post-load file and Manual check of the Loaded data using KE53 and SE16N |
Business
Completeness
| Task | Action |
|---|---|
| Record Count Check | Business to check Post-Load File and Summary report in post-load |
Accuracy
| Task | Action |
|---|---|
| Spot check | Spot check some sample records from the post-load report to be picked for checking in SAP transaction code KE53 to verify accuracy of the data. |
Verify Profit Centres are transformed accurately as per endorsed transformation/mapping rules.
Review error reports in tool for any mismatch or missing transformed values.
In legacy system, execute ECC tcode SE16N to display table CEPC to confirm copied fields are accurately copied.
If any of the sum is different, raise defect and flag the relevant record as error.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 using LTMC cockpit object of Profit Centre.
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE)
Load Run Sheet
Item
Step description
Team responsible
1
Ensure the load tools are transported into the correct tool instance.
Data team
2
Ensure DCTs and all required mappings are submitted and complete
Data team
3
Ensure Pre-load sign-offs are obtained.
Data team
4
Execute upload of Profit Centre Object using Migration Cockpit Object for Profit Centre Upload
Data team
5
Generate the post load reports in tool.
Data team
6
Log errors as defects, if any and address resolutions. Close defects.
Data team
7
Resolve defects by reupload and re-generate post load reports if necessary.
Data team
8
Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.
Business
9
Repeat steps 5 to 7 if necessary.
Data team
Load Phase and Dependencies
Configuration
Item # | Configuration item |
1. | Controlling Area |
2. | Standard Hierarchy is Maintained |
3. | Currencies (currency keys, decimal places in currencies) |
Conversion Objects
Error Handling
Error type | Error description | Action taken |
P | Posting period is blocked for posting | Review project / cutover plan and ensure posting periods can be opened for postings |
Profit Centre does not exist | Profit centre does not exist in company code | Ensure the profit centre mapping is correct and or create the profit centre if it is valid |
Post-Load Validation
Project Team
Completeness
Total number of records loaded for TB Balance ( PY ) will be generated in the Post-load reports in tool based on the target table and fields mentioned in section 3.
The reconciliation needs to be executed on the total number of ‘valid’ records and currency amount per company code in the source compared to total number of records and currency amount in S/4HANA
Record Count
Check the sum of record count of the open items in the load file is the same as S/4HANA. The record count for TB Balance ( PY ) will be done on the group basis. The fields in the group are consist of: Company Code, Vendor Account
Check Amount in Document Currency and Local Currency
Check on line item level that the sum of the amount in Document Currency and Local Currency in the load file is the same as posted in S/4HANA. If any of the sum is different, flag the record as error.
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
Completeness
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 FS10N – Vendor Line Item Display or equivalent report in Fiori App to display loaded TB Balance ( PY ) in S/4HANA and compare results against the pre-load reports generated from tool.Accuracy
Key Assumptions
- Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
- is in scope based on data design and any exception requested by business.
Change log
| Change History | ||
|---|---|---|
|
Workflow history
| Workflow Report | ||||||
|---|---|---|---|---|---|---|
|