| Status | Approved |
|---|---|
| Owner | Maytingsari Tjahjo |
| Stakeholders |
Purpose
The purpose of this document is to define the conversion approach to migrate the balance below from legacy system to S/4HANA, so Project manager is able to know the entire cost of its active OPEX project:
- Active OPEX WBS
- Only certain closed OPEX project types (e.g. R&I, Maintenance OPEX) that have cost in current year.
Note: OPEX projects that are just used to get a breakdown of CC costs (current internal orders) aren't required for Portfolio reporting - they aren't real projects delivering an outcome. Hence the closed OPEX other that R&I and Maintenance OPEX that have cost in CY, no need to be migrated.
R&I OPEX is required to be settled to COPA (PSG) to allow reporting by market drivers, product, customer, GBU, company code, etc.
For To-Be design, Internal order will be mapped to either to real or statistical OPEX WBS. Whether it will need to be statistical or real WBS, this depends on what is the IO currently used for today. (Awaiting Matthias (CO Lead) on this). Business must identify which I/O master data and balance that must be migrated. Then new real/statistical OPEX WBS will be created for these I/O and subsequently load its balance.
Conversion Scope
The scope of this document covers the approach for converting active OPEX WBS element and also certain closed OPEX project types (e.g. R&I, Maintenance OPEX) that have cost in current year from Legacy Source Systems into S/4HANA.
The relevancy rules for this object 9032 will follow the relevancy rule in conversion specification:
- 1024 (Project Definition (CAPEX, OPEX))
- 1026 (WBS - CAPEX, OPEX, Statistical)
All the relevant WBS Elements (after applying the approved relevancy rules) that have received primary and secondary transactions posted to the cost elements within the WBS Elements will be migrated as below:
Group 1 (Go live 1 July 2028):
- Accumulated balances up to 31 Dec 2027 (Prior Year)
All the financial transactions posted of all open WBS Elements up to 31 Dec 2027 will be totaled into the one single value and then be posted to the relevant WBS Elements in S/4HANA and subsequently run settlement from WBS to Cost Center.
- Accumulated balances from 1 Jan 2028 till 30 June 2028 (Current Year)
All the financial transactions posted of all open WBS Elements and closed WBS OPEX project types (e.g. R&I, Maintenance OPEX) from 1 Jan 2028 till 30 Jun 2028 will be totaled into the one single value and be posted to the relevant WBS Elements in S/4HANA. Then run settlement from WBS to Cost Center.
Group 2 (Go live 1 Jan 2029):
- Accumulated balances up to 31 Dec 2027 (Prior Year)
All the financial transactions posted of all open WBS Elements as of 31 Dec 2027 will be totaled into the one single value and be posted to the relevant WBS Elements in S/4HANA. Then run settlement from WBS to Cost Center.
- Accumulated balances from 1 Jan 2028 till 30 Dec 2028 (Prior Year)
All the financial transactions posted of all open WBS Elements from 1 Jan 2028 till 31 Dec 2028 will be totaled into the one single value and be posted to the relevant WBS Elements in S/4HANA. Then run settlement from WBS to Cost Center.
Primary transactions refer to original postings from all sources whether it is debit or credit.
Secondary transactions refer to allocations from sources such as allocations from payroll, work orders, other WBS Elements or cost centers. These postings will be subject to any settlement rules set up in the individual WBS Element.
The scope of this document will therefore extract the settlement transactions from each individual WBS Element to provide a base for posting to the S/4HANA WBS Elements as at end of last month before go live. The total of the transactions will be used to compare to the balance in the Cost Center that is used for settlement. The total of the settlement transactions will also be reconciled against the total costs posted to the WBS Element to ensure that all costs have been captured.
The data from legacy system includes:
Any WBS Element that is not closed will be migrated. Of the remaining, a WBS Element that is not marked for deletion will be migrated.
- Only certain closed OPEX project types (e.g. R&I, Maintenance OPEX) that have cost in current year must also be migrated.
The data from legacy system excludes:
- All OPEX WBS with status as Closed (CLSD).
- All OPEX WBS that are marked for deletion.
- Closed OPEX project types (other than R&I, Maintenance OPEX) that have cost in current year.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 and WP2 | OPEX Project level exclusions based on following relevancy rules:
| S/4HANA | ||
| PF2 and WP2 |
Exceptions:
| S/4HANA | ||
PF2 and WP2 | Extraction of the Sender Credit values from settlement that uses primary cost elements for settlement (Table COSP) | S/4HANA | ||
PF2 and WP2 | Extraction of the Sender Credit values from settlement that uses secondary cost elements for settlement (Table COSS) | S/4HANA |
There will be 3 SAP boxes:
a. CUI box (US, GB, DE)
b. China box
c. ROW (Rest of the World) box
Please refer to file "Entreprise Structure Catalog" to see which company codes belongs to which SAP boxes.
In terms of data migration, below is the guideline:
- Non CUI objects : Migration to US system by Syniti
- CUI objects : Manual cleansing/separate migration cockpit (Syniti is not certified)
Additional Information
Multi-language Requirement
N/A
Document Management
N/A
Legal Requirement
N/A
Special Requirements
Target Design
There are two types of costs in the WBS Elements:
- Costs that are sourced from primary and secondary cost elements.
- The secondary cost elements cannot be used to post costs to S/4HANA. In many cases, the secondary cost element will form part of the total for the WBS Element. These costs (Table COSS) must be considered but the use of a primary cost element will be used to post these costs to the WBS Element in S/4HANA. The Primary Cost Total (COSP) table in source system (PF2 and WP2) also shows the values that have been settled to the receiver, be it an Asset Under Construction or a Cost Centre or a General Ledger Account. In this object 9032, the receiver is Cost Center.
There is no need to replicate the postings that have occurred in the source system. The value that has been settled to the receiver object can be used to post with a selected General Ledger account. The settlement can then also use this account to clear the balance at the level. The offset General Ledger account will still be used to balance the journal entries.
The technical design of the target for this conversion approach.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| ACDOCA | RBUKRS | BUKRS | Company Code | CHAR | 4 | Mandatory |
| Ledger Group | CHAR | 4 | Not used | |||
| ACDOCA | AWREF | AWREF | Reference Doc. Number | CHAR | 16 | Mandatory |
| ACDOCA | DOCLN | DOCLN6 | Line Item Number | Number | 6 | Mandatory |
| ACDOCA | RACCT | RACCT | G/L Account | CHAR | 10 | Mandatory |
| ACDOCA | GKONT | GKONT | Offsetting Account | CHAR | 10 | Mandatory |
| ACDOCA | BLART | BLART | Document Type | CHAR | 2 | Mandatory |
| ACDOCA | BUDAT | BUDAT | Posting Date in the document | DATS | 8 | Mandatory |
| ACDOCA | BLDAT | BLDAT | Document Date | DATS | 8 | Mandatory |
| BSEG | XREF3 | XREF3 | Reference key for line item | CHAR | 20 | Conditional |
| Accounting Principle | CHAR | 4 | Not used | |||
| BKPF | BKTXT | BKTXT | Header Text | CHAR | 25 | Optional |
| ACDOCA | SGTXT | SGTXT | Item Text | CHAR | 50 | Optional |
| ACDOCA | RWCUR | FINS_CURRW | Transaction Currency | CUKY | 5 | Mandatory |
| ACDOCA | WSL | Amount | CURR | 23 | Mandatory | |
| ACDOCA | RHCUR | FINS_CURRH | Company Code Currency | CUKY | 5 | Mandatory |
| ACDOCA | HSL | Amount | CURR | 23 | Mandatory | |
| ACDOCA | RKCUR | FINS_CURRK | Group Currency | CUKY | 5 | Mandatory |
| ACDOCA | KSL | Amount | CURR | 23 | Mandatory | |
| Freely Defined Currency | CUKY | 5 | Not used | |||
| Amount | CURR | 23 | Not used | |||
| (OBSOLETE) Tax Code | CHAR | 2 | Not used | |||
| (OBSOLETE) Tax Jurisdiction | Text | 15 | Not used | |||
| ACDOCA | RASSC | RASSC | Company ID of Trading Partner | Text | 80 | Optional |
| ACDOCA | ZUONR | DZUONR | Assignment Number | CHAR | 18 | Optional |
| ACDOCA | RMVCT | RMVCT | Transaction Type | Text | 80 | Optional |
| ACDOCA | PERNR | PERNR_D | Personnel Number of Employee | Text | 80 | Not used |
| ACDOCA | VALUT | VALUT | Value Date | DATS | 8 | Optional |
| ACDOCA | HBKID | HBKID | Short Key for House Bank | CHAR | 5 | Optional |
| ACDOCA | HKTID | HKTID | ID for Account Details | CHAR | 5 | Optional |
| ACDOCA | RCNTR | KOSTL | Cost Center | CHAR | 10 | Conditional |
| ACDOCA | PRCTR | PRCTR | Profit Center | CHAR | 10 | Conditional |
| ACDOCA | SEGMENT | FB_SEGMENT | Segment | Text | 80 | Not used |
| ACDOCA | PS_PSP_PNR | PS_PSP_PNR | WBS Element | CHAR | 80 | Conditional |
| ACDOCA | AUFNR | AUFNR | Order Number | CHAR | 12 | Conditional |
Data Cleansing
There will be cleansing required outside of that handled in the following DCA’s
- 1024 - Project Definition (CAPEX, OPEX)
- 1026 - WBS - CAPEX, OPEX, Statistical
- Conversion Approach - PPM Items
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|---|---|---|---|---|
Conversion Process
The high-level process is represented by the diagram below:
Data Privacy and Sensitivity
N/AExtraction
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
Extraction run sheet for legacy WBS Elements settling to Cost Centers.
| Req # | Requirement Description | Team Responsible | ||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1. | Extract data from source systems based on the current relevancy rules that apply to the Project and WBS Element Master Data. For each relevant WBS Element extract the object number from source systems with WBS Elements from table PRPS. | Data Team | ||||||||||||||||||||||||||||||||||||||||||||
| 2. | The following tables will be used to extract the settlement data:
To ensure that all costs have been collected via these tables (COSP & COSS), run a report (transaction code CJI3) to extract all the costs posted to the WBS Element/s to reconcile against the totals extracted from table COSP & COSS. Compare and agree the reconciliation values before progressing further to the next steps. For each open Project, confirm that the final balance is zero which will ensure that the settlement costs represent all the postings (debit and credit) within the Project by WBS Element. Extract the transactions by business transaction type. Use table AUFK to reconcile the settlement costs against actual posting extracts (extract by year by period by settlement transaction for each Project. | Data Team | ||||||||||||||||||||||||||||||||||||||||||||
| 3. | Go to source systems (PF2 and WP2) Primary Costs Total (Table COSP)
Go to source system (PF2 and WP2) Secondary Costs Total (Table COSS)
From the above, system will generate report as below. The report will need to be summarized by object number by total for all the fiscal years.
| Data Team | ||||||||||||||||||||||||||||||||||||||||||||
| 4. | Step #3 provides what needs to be posted for each WBS Element. These can be split across cost elements, but the proposal is to use one Cost Element for both posting and settlement (GL account TBD) | Data Team | ||||||||||||||||||||||||||||||||||||||||||||
| 5. | Extract the Settlement Rule object from table COBRB in source systems (PF2 and WP2) to find the settlement objects for the above project.
System will provide a report as below that will include the following fields:
Extract the Cost Centre numbers from this report. Retrieve the Object number for all the settlement objects and retrieve the values from the COSP table. The journal is to post to the WBS will be: Dr. WBS Cr. Cost Centre Then settlement will be: Dr. CTR Cr. WBS So that net effect on both account and Cost Centre is zero - but WBS is left with a balance | Data Team | ||||||||||||||||||||||||||||||||||||||||||||
| 6. | Extraction and posting will require one posting at year end and once the overall balance has been agreed above, extract and post and settle with one settlement transaction in the previous year. Explain for the CY | 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.
A DCT will be required to collect the transactions posted to the WBS Elements/Project that are not in PF2 and WP2 but have been selected in the DCT for master data for Projects and WBS Elements- OPEX.
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
| Field Name | Field Description | Rule |
|---|---|---|
ACDOCA-POSID | WBS Element | To be prepopulated based on WBS element load with new WBS number. |
ACDOCA-WSL | Amount | For previous year actuals, total all transaction values and post as a single transaction with the posting date of the 31 Dec of the previous year. For current year actuals, total all transaction values by month and post as a single transaction with the posting date of the last month end of each month |
ACDOCA-BUDAT | Posting Date | For previous year actuals, total all transaction values and post as a single transaction with the posting date of the 31 Dec of the previous year. For current year actuals, total all transaction values by month and post as a single transaction with the posting date of the last month end of each month |
ACDOCA-POPER | Posting Period | Enter Posting Period. This should default in the DCT based on Posting Date |
ACDOCA-GJAHR | Fiscal Year | Enter fiscal year. This should default based on Posting Date |
ACDOCA-BLART | Document Type | Use Document Type “SA” (TBC) or "UE"? |
ACDOCA-BLDAT | Document Date | Same as Posting Date |
ACDOCA-BKTXT | Header Text | TBC |
ACDOCA-RBUKRS | Company Code | Enter Company Code |
ACDOCA-RACCT | GL Account | Default to GL XXXXX (TBC) |
ACDOCA-RWCUR | Currency | Enter Local Currency. Group currency will be calculated. |
ACDOCA-SGTXT | Item Text | Migration transaction TBC |
Extraction Dependencies
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1. | All OPEX WBS element cleansing has been completed in PF2 and WP2 | Business |
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. | In ADMM, select Object 9032 and launch this to execute transformation | Syniti Team |
| 2. | Perform transformation for all relevant WBS Elements. Legacy WBS Element is mapped to S/4HANA WBS elements in mapping table. | Syniti Team |
| 3. | Generate Pre-Load reports in ADMM for the extracted WBS Element amounts. | Syniti Team |
| 4. | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
| 5. | Analyze and resolve any pre-load defects logged by business. | Data Team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1. | PF2 and WP2 | COSP | OBJNR | Object Number | S/4HANA | ACDOCA | POSID | WBS Element Number | COSP Object Number will identify the WBS Element from PF2 and WP2 (PRPS table) which will map to the S/4HANA WBS Element identified in WBS mapping table. |
| 2. | PF2 and WP2 | COSS | OBJNR | Object Number | S/4HANA | ACDOCA | POSID | WBS Element Number | COSS Object Number will identify the WBS Element from PF2 and WP2 (PRPS table) which will map to the S/4HANA WBS Element identified in WBS mapping table. |
| 3. | PF2 and WP2 | COSP | BUKRS | Company Code | S/4HANA | ACDOCA | RBUKRS | Company Code | Mapping table from legacy company code to S/4HANA Company Code. |
| 4. | PF2 and WP2 | COSS | BUKRS | Company Code | S/4HANA | ACDOCA | RBUKRS | Company Code | Mapping table from legacy company code to S/4HANA Company Code. |
| 5. | PF2 and WP2 | PRPS | PRCTR | Profit Center | S/4HANA | ACDOCA | PRCTR | Profit Center | Map Legacy Profit Centre to the S/4 HANA Profit Centers. |
| 6. | PF2 and WP2 | COSP | GJAHR | Fiscal Year | S/4HANA | ACDOCA | GJAHR | Fiscal Year | |
| 7. | PF2 and WP2 | COSS | GJAHR | Fiscal Year | S/4HANA | ACDOCA | GJAHR | Fiscal Year | |
| 8. | N/A | N/A | N/A | N/A | S/4HANA | ACDOCA | RACCT | Account Number | Use GL Account to post to the new WBS Element. TBC |
| 9. | PF2 and WP2 | COSP | WTGxxx | Value Transaction Curr | S/4HANA | ACDOCA | POPER | Posting Period | |
| 10. | PF2 and WP2 | COSS | WTGxxx | Value Transaction Curr | S/4HANA | ACDOCA | POPER | Posting Period | |
| 11. | N/A | S/4HANA | ACDOCA | BUDAT | Posting Date | ||||
| 12. | N/A | S/4HANA | ACDOCA | BLDAT | Document Date | ||||
| 13. | PF2 and WP2 | COSP | WTGxxx | Value Transaction Curr | S/4HANA | ACDOCA | WSL | Amount in Transaction Currency | xx represents all periods for previous years. Value type (COSP-WRTTP) must be “4” and Dr/Cr Indicator (COSP-BEKNZ) set to “O - Special: Sender credit from settlement”. Once the data is collected the signage must be changed prior to posting. As most of the settlement amounts will be a negative amount, this value must be changed to a positive amount before posting back to the S/4HANA WBS Element. If the settlement amount is a positive value, it must be changed to a negative value. Logic will be required to determine the posting period from the field name WTGxxx, with xx being the posting month. E.g. 001,002,003, etc. Note: Please ensure when extracting this field, it must read from column "Value" (not column "Value Unconverted"), because column "Value" is showing the correct value for all currencies (including currency with 0 decimal, such as JPY, KRW, etc)) In the table below, the column "Value" is showing the correct value (i.e. JPY 19.680.000)., but the amount in column "Value Unconverted" is incorrect (JPY 196.800). |
| 14. | PF2 and WP2 | COSS | WTGxxx | Value Transaction Curr | S/4HANA | ACDOCA | WSL | Amount in Transaction Currency | xx represents all periods for previous years. Value type (COSP-WRTTP) must be “4” and Dr/Cr Indicator (COSP-BEKNZ) set to “O - Special: Sender credit from settlement”. Once the data is collected the signage must be changed prior to posting. As most of the settlement amounts will be a negative amount, this value must be changed to a positive amount before posting back to the S/4HANA WBS Element. If the settlement amount is a positive value, it must be changed to a negative value. Logic will be required to determine the posting period from the field name WTGxxx, with xx being the posting month. E.g. 001,002,003, etc. Note: Please ensure when extracting this field, it must read from column "Value" (not column "Value Unconverted"), because column "Value" is showing the correct value for all currencies (including currency with 0 decimal, such as JPY, KRW, etc)) In the table below, the column "Value" is showing the correct value (i.e. JPY 19.680.000)., but the amount in column "Value Unconverted" is incorrect (JPY 196.800).
|
| 15. | N/A | S/4HANA | ACDOCA | BLART | Document Type | Default to UE? TBC | |||
| 16. | N/A | S/4HANA | ACDOCA | USNAM | User Name | Default to data migration user ID | |||
| 17. | N/A | S/4HANA | ACDOCA | SGTXT | Item Text | Specify source WBS Element | |||
| 18. | PF2 and WP2 | S/4HANA | ACDOCA | BKTXT | Header Text | Default to “Data Object 9032” | |||
| 19. | PF2 and WP2 | S/4HANA | ACDOCA | RACCT | Offsetting GL Account | Use the Offset GL Account used for GL Balance migration - (TBC). This will be used for migration for transactions that will eventually settle to Cost Centre. |
Transformation Mapping
| Mapping Table Name | Mapping Table Description |
|---|---|
Company code | Mapping of legacy company code to S/4HANA company code |
Cost Centre | Map legacy Cost Centres to S/4HANA Cost Centres |
GL Accounts | Map legacy GL Accounts to S/4HANA GL Accounts |
Profit Centre | Map legacy Profit Centre to S/4HANA Profit Centre |
WBS Elements | Map legacy WBS Elements to S/4HANA WBS Elements |
Currency | Map legacy currency to S4/HANA currency code |
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 in Section "Mapping tables", have the correct values mapped. | Data Team |
Pre-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
Verify Counts | Data team to verify the load count is the same as per identified data from Primary Cost Total COSP file and Secondary Cost Total COSS file. |
Validate | Validate that the extracted values from both tables agree with the total transaction costs excluding settlement for each individual WBS Element |
Accuracy
| Task | Action |
|---|---|
| Validate | Validate that the extracted values from both tables agree with the total transaction costs excluding settlement for each individual WBS Element |
| Validate | Validate that the extracted values are identical to those values settled to the Receiver. |
| Reconcile | Total by Asset number to compare to the WBS Element value to be posted. The value to be posted against the WBS Element must agree with the value shown for the relevant Asset Under Construction. See section "Extraction run sheet for legacy WBS element settling to AUCs. |
Business
Completeness
| Task | Action |
|---|---|
| Verify counts | Business will use the preload report to validate the number of WBS Elements that will migrate values. |
Accuracy
| Task | Action |
|---|---|
| Validate | Validate that the extracted values are identical to those values posted to the WBS Element |
Load
The load process includes:
- Execute the automated data load into target system using load tool or product the load file if the load must be done manually
- Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation
Load Run Sheet
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1. | Ensure Pre-Load signoffs are obtained. | Data Team |
| 2. | Load a small number of records to verify that the process is stable and will load all records as expected. | Syniti Team |
| 3. | If the above is successful, load all remaining records. | Syniti Team |
| 4. | If the above is unsuccessful, review errors and determine whether the error is data related, or system related. | Data Team |
| 5. | After correction, load corrected file or run corrected program to load data. | Syniti Team |
| 6. | Prepare report for Post Load Validation. | Syniti Team |
| 7. | Validate Post Load report. | Business |
Load Phase and Dependencies
Configuration
| Item # | Configuration Item |
|---|---|
| 1. | Cost Element Groups |
| 2. | Settlement Profiles |
| 3. | Allocation Structures |
| 4. | Settlement cost elements used for settlement available in all company codes in scope |
| 5. | Number ranges for settlement documents to be set up. This is manual config. |
Conversion Objects
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1024 | Project Definition (CAPEX, OPEX) |
| 1025 | Project Text & Documents (attachments) |
| 1026 | WBS - CAPEX, OPEX, Statistical |
Error Handling
| Error Type | Error Description | Action Taken |
|---|---|---|
| Configuration | Document type does not exist in S/4HANA | Engage Functional team to fix the error in the system |
Post-Load Validation
Project Team
Completeness
| Task | Action |
|---|---|
| Verify Counts | Data team to verify the load count is the same as per identified data from Pre Load file |
Accuracy
| Task | Action |
|---|---|
| Verify values | Ensure the Pre-Load report values are the same as in the Post Load Report. These values have to be verified before settling the costs to the AUCs. |
Settlement to Cost Centres:
Run CJ88 to settle any costs that uniquely settle to mapped cost centres (if required). For settlement to Cost Centres the category of the Cost Centre must either be cost category ? (To be confirmed)
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
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.
- All WBS Elements will have a zero balance. If this is not true, there must be a BAU activity to ensure there is a zero balance.
- All costs in source system SAP-PE1 (Primary Costs Total Table COSP and Secondary Costs Total Table COSS) will represent the total transactional costs that have been posted to the respective WBS Element.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||