Status
Owner	Maytingsari Tjahjo
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach to migrate the balance of Capex Project/WBS from legacy system to S/4HANA, so the Project Manager is able to know the total cost of CAPEX Project in scope.

Conversion Scope

There are 2 group go-live as below:

Group 1 go-live (1 July 2028) (Source System: PF2)
Group 2 go-live (1 Jan 2029) (Source System: WP2)

Note: There is possibility to shift into 1 go live date, this option is currently still being considered.

Relevancy rules:

Below are the criteria of CAPEX projects that are in scope. This document covers the approach for migrating the balance of CAPEX Projects below for the company codes in scope from Legacy Source Systems into S/4HANA:

Active CAPEX Project/WBS as per cutover date (i.e. 30 June 2028 for Grp 1 & 31 Dec 2028 for Grp 2)
Closed CAPEX Project/WBS that have cost in current year (From a portfolio level perspective, there needs to be full current year costs to be able to track against the annual budget allocation)

Conversion specs 1026 will provide the list of the WBS CAPEX that meet the above criteria.

The relevancy rules for this object will follow the relevancy rule in conversion specification 1026 (WBS - CAPEX, OPEX, Statistical) in migrating the balance of CAPEX projects as below:

Group 1 go live (1 July 2028) to migrate the above WBS for:

- Accumulated balance up to 31 Dec 2026
- Accumulated balance from 1 Jan 2027-31 Dec 2027
- Monthly balance from 1 Jan 2028 till 30 June 2028. The monthly balance is required for forecasting purpose, monthly trend report and sleeping AUC report.

It is expected that the balance of the WBS Elements is zero on 31 Dec 2027 and 30 Jun 2028, implying that the settlement transactions will be equal to all the primary and other secondary transactions posted to the relevant WBS Element.

Group 2 go live (1 Jan 2029) to migrate the above WBS for:

- Accumulated balance up to 31 Dec 2026
- Accumulated balance from 1 Jan 2027-31 Dec 2027
- Monthly balance from 1 Jan 2028 till 31 Dec 2028. The monthly balance is required for forecasting purpose, monthly trend report and sleeping AUC report.

All the relevant WBS Elements (after applying the approved relevancy rules) open as at end of last month before go live that have received primary and secondary transactions posted to the cost elements within the WBS Elements

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.

It is expected that the balance of the WBS Elements is zero at end of last month before go-live, implying that the settlement transactions will be equal to all the primary and other secondary transactions posted to the relevant WBS Element.

All these transactions will be totaled by each extraction by WBS and posted to the original G/L account (which will be mapped to new G/L in S4/HANA) into the one single value and then be posted to the relevant WBS Elements in S/4HANA. The approach will also run SAP settlement by each extraction to the relevant Asset Under Construction.

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 Asset Under Construction 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. Therefore, the scope will extend to the reconciliation of the legacy AUC values.

Below is the list of AUC classes for SyWay:

Z1100 Intangible-AUC
Z1101 Intangible-R&I under construction
Z1300 Tangible-AUC

The data from legacy system includes:

Relevancy rules of object 1026 (WBS - CAPEX, OPEX, Statistical)

The data from legacy system excludes:

All WBS CAPEX with an out-of-scope company code will not be migrated.
All closed WBS CAPEX as at the end of the previous fiscal year will not be migrated.
All WBS CAPEX marked for deletion will not be migrated.
All WBS CAPEX marked as statistical will not be migrated.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
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

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

Due to compliance requirement, there will be 3 SAP instances as below:

SAP instance for Rest of the World (ROW)
SAP instance for China
SAP instance for CUI

Project actual cost balance will be migrated to respective SAP instances based on the company codes. Please refer to column "Company Code" and "Instance" in Enterprise Structure Catalog - Google Sheets (worksheet 10. Company code)

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 (AUC) or a Cost Centre or a General Ledger Account. In this object 9032, the receiver is AUC.

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 for real posting:

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
ACDOCA	RBUKRS	BUKRS	Company Code	CHAR	4	Mandatory
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
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	FINS_VWCUR12	Amount in Transaction Currency	CURR	23	Mandatory
ACDOCA	RHCUR	FINS_CURRH	Company Code Currency	CUKY	5	Mandatory
ACDOCA	HSL	FINS_VHCUR12	Amount in Company Code Currency	CURR	23	Mandatory
ACDOCA	RKCUR	FINS_CURRK	Global Currency	CUKY	5	Mandatory
ACDOCA	KSL	FINS_VKCUR12	Amount in Global Currency	CURR	23	Mandatory
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

The technical design of the target for this conversion approach for statistical posting (T.code KAFD).

There is no standard Data Migration Cockpit to post statistical posting (Transaction code KAFD). Hence there are 2 options as below:

Option 1: Create custom cockpit object

Option 2: Create LSMW

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
COEP	PSPNR	PS_POSID	WBS Element	CHAR	24	Mandatory
COEP	PERIO	CO_PERIO	Period	NUMC	3	Mandatory
COEP	GJAHR	GJAHR	Fiscal year	NUMC	4	Mandatory
COEP	KSTAR	KSTAR	Cost element	CHAR	10	Mandatory
COEP	WTGBTR	WTGXXX	Total Value in Transaction Currency	CURR	23 (2 decimal)	Mandatory
COEP	TWAER	TWAER	Transaction Currency	CUKY	5	Mandatory
COEP	WKGBTR	WKGXXX	Total Value in Controlling Area Currency	CURR	23 (2 decimal)	System generated
COEP	KWAER	KWAER	Controlling area currency	CUKY	5	System generated
COEP	WOGBTR	WOGXXX	Total Value in Object Currency	CURR	23 (2 decimal)	System generated
COEP	OWAER	OWAER	Object Currency	CUKY	5	System generated

Data Cleansing

There will be cleansing required in the following DCA:

1024 - Project Definition (CAPEX, OPEX)
1026 - WBS - CAPEX, OPEX, Statistical

ID

Criticality

C1 - Data cannot be loaded to SAP

C2 - Data can be loaded into SAP but not Business Ready

C3 - Errors that do not impact Go-Live or do not validate any standard

Error Message/Report Description

Rule

Output

Source System

Cleansing Settlement to GL account (which is mapped to Reconciliation Account type A)

C2

Settlement value to the GL account (which is mapped to Reconciliation Account type A) must be cleansed by Business.

Action item:

Instead of settled to the Balance Sheet GL account (which is FXA Reconciliation Account), business must settle to AUC number

Extract table COBRB:

Company codes in scope in Group 2 go live

Object Number: PR*

Field KONTY (Acct Assignment Category) = G/L

Field HKONT (G/L account) = 21900100

List of WBS that is settled to GL 21900100 (FA recon account)

WP2

Ensure there is no partial capitalization from AUC to Final Asset

Conversion Process

The high-level process is represented by the diagram below:

Note: DCT is not required for this object 9032. DCT is shown in table below, for reference only, just in case in the future data migration, DCT is required.

SyWay Project > CNV-9031 Project-Actual GL Line Items (PNL-WBS for AuC) > image-2025-6-19_15-22-36.png

Process	Activity
Extract	Extract involves collecting data from the source. There are 2 possible methods at this stage of process: 1. If the source is a system, extract means to pull the required data from source systems into repository. There are 2 steps for this method: a. Perform full data extraction from relevant tables in the source system(s). b. Apply relevancy criteria for filtering the data that will be applicable according to target system. 2. If the source is not a system, the data will need to be manually collected by business. This is to be done using DCT (Data Collection Template).
Transform	There are 2 steps of Transform activities that can happen: Perform mapping and data transformation rules. Some data will need to be mapped to the to-be values and/or updated according to the rules as per design requirement in target system. The WBS mapping (Current vs To-Be) will be provided by conversion object 1026 (WBS - CAPEX, OPEX, Statistical). 2. Prepare load-ready data in the structure and format that is required for loading via standard Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation.
Load	This process includes: 1. Execute the automated data load into target system using load tool. Note: There may be some cases where the load is done manually as part of business activities. 2. Once the data is loaded to target system, it will be extracted out and prepared for Post Load Data Validation.

Data Privacy and Sensitivity

N/A

Extraction

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

The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if Syniti MIgrate 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 Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

A. Extraction Run Sheet for legacy WBS Elements settling to AUCs

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:

Primary Cost Total (COSP) table
Secondary Cost Total (COSS) table

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.

Data Team

3.

Go to source systems (PF2 and WP2) Primary Costs Total (Table COSP)

Field	Value
Object Numbers	For each relevant WBS Element extract the object number from source system from table PRPS. Enter the extracted number in the field of this table.
Year	1900 up to the FY of the last month before go-live date
Value Type	04
Cost Element	Leave it blank
Dr/CR Indicator	O
Value transaction currency for each period for each year	WTG01 to WTG16

Go to source system (PF2 and WP2) Secondary Costs Total (Table COSS)

Field	Value
Object Numbers	For each relevant WBS Element extract the object number from source system from table PRPS. Enter the extracted number in the field of this table.
Year	1900 up to the FY of the last month before go-live date
Value Type	04
Cost Element	Leave it blank
Dr/CR Indicator	O
Value transaction currency for each period for each year	WTG01 to WTG16

From the above, system will generate report as below.

The report will need to be summarized by object number as below:

Group 1 Go live (1 July 2028):

Accumulated balances up to 31 Dec 2026
Accumulated balances 1 Jan - 31 Dec 2027
Monthly balance from 1 Jan 2028 till 30 June 2028

Group 2 Go live (1 Jan 2029):

Accumulated balances up to 31 Dec 2026
Accumulated balances up to 1 Jan - 31 Dec 2027
Monthly balance from 1 Jan 2028 till 31 Dec 2028

Field	Value
Object Numbers	PR*******
Fiscal Year	There will be values for each Fiscal Year.
Value Type	04
Cost Element	The cost element to which the transaction was posted.
Dr/CR Indicator	O
Value transaction currency for each period for each year	WTG01 to WTG16
Company Code	Company code where the transaction was posted

Data Team

4.

Step #3 provides what needs to be posted for each WBS Element. These must be posted by using the original cost element (which will be mapped to S/4HANA cost element).

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.

Field	Value
Object Numbers	Enter the same Object Numbers as the above steps for Primary Costs (Table COSP) and Secondary Costs (Table COSS).
Account Assignment Category	FXA (Fixed Asset)

System will provide a report as below that will include the following fields:

Field	Example
Object Numbers	PR********
Account Assignment Category	Fixed Asset
Company Code	Company code where the transaction was posted
Asset	This will show both (the Final asset and the AUC) if any values have been posted to the final asset. This is applicable for object 9031.

Extract the asset numbers from this report.

Data Team

6.

Extract the fixed asset values from table ANEP in source systems (PF2 and WP2) to check what has been posted to the Asset under Construction (AUC).

Field	Description	Value
ANEP-BUKRS	Company Code	Company code from the above step.
ANEP-ANLN1	Asset Number	Asset numbers from the above step.
ANEP-GJAHR	Fiscal Year	1900 up to the FY of the last month before go-live date
ANEP-AFABE	Depreciation Area	01

System will generate as below:

Field	Description	Value
ANEP-BUKRS	Company Code	Company code from the above step.
ANEP-ANLN1	Asset Number	Asset numbers from the above step.
ANEP-GJAHR	Fiscal Year	Fiscal year posting for each year
ANEP-AFABE	Depreciation Area	01
ANEP-BWASL	Transaction Type	Transaction types that are used for posting
ANEP-ANBTR	Amount Posted	Amount posted

This report will need to be summarized by asset number as below:

Group 1 Go live (1 July 2028):

Accumulated balances up to 31 Dec 2026
Accumulated balances 1 Jan-31 Dec 2027
Monthly balance from 1 Jan 2028 till 30 June 2028

Group 2 Go live (1 Jan 2029):

Accumulated balances up to 31 Dec 2026
Accumulated balances 1 Jan-31 Dec 2027
Monthly balance from 1 Jan 2028 till 31 Dec 2028

Check against the WBS Element postings (CJI3) before loading into S/4HANA.

Check

Action

Balance remains in AUC where the value in the AUC equals with the value in the WBS.

Postings must be made to the WBS and settle to the AUC.

Balance remains in the AUC but the value in the AUC does not equal the total postings in the WBS.

Postings must be made to the WBS and the AUC but only up to the value in the AUC. Investigate why the postings are different. This is due mainly to partial settlement to a fixed asset based on Transaction Types 338 (Retirement transfer of PY acquisition from investment measure) and 339 (Acquiring transfer of CY acquisition from investment measure).

Example:

The posting we should make to the Projects is under transaction type 116 (Internal settlement of acquisition to AuC) for $100,000, however transaction types 160 (Credit memo in following year), 338 and 339 (total $60,000), have been used to partially capitalize this AUC to Final asset. Therefore, we only need to post $40,000 as AUC balance. But because we need to post all the costs to the Project, the remainder balance ($60,000) needs to be posted as Statistical Posting (T.code KAFD) to expense account for fixed assets where the AUC has been partially settled to a or several fixed assets.

No balance in the AUC

No requirement to post any postings to the WBS Element or the AUC. The probable reason is that the AUC has been fully settled to a fixed asset.

Post statistical posting (T.code KAFD) the same amount as fixed asset amount.

Data Team

7.

Run transaction code S_ALR_87011963 (Asset Balances report) for all AUC assets within the relevant company code. Check each individual asset balance before making any posting to a WBS Element.

Data Team

8.

Group 1 Go live (1 July 2028):

Accumulated balances up to 31 Dec 2027 (Prior Year)

Once the AUC balance up to 31 Dec 2027 has been agreed, a posting will be required (document type 9*) and run settlement (CJ8G)

Monthly balance from 1 Jan 2028 till 30 June 2028 (Current Year)

Once the AUC monthly balance from 1 Jan 2028-30 Jun 2028 has been agreed, a posting will be required (document type 9*) and run settlement (CJ8G)

Group 2 Go live (1 Jan 2029):

Accumulated balances up to 31 Dec 2027 (Prior Year)

Once the AUC balance up to 31 Dec 2027 has been agreed, a posting will be required (document type 9*) and run settlement (CJ8G)

Monthly balance from 1 Jan 2028 till 31 Dec 2028 (Prior Year)

Once the AUC monthly balance up from 1 Jan 2028-31 Dec 2028 has been agreed, a posting will be required (document type 9*) and run settlement (CJ8G)

Data Team

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

Data Collection Template (DCT)

N/A

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1.	All CAPEX 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 Syniti Migrate to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in Syniti Migrate.
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 9031 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. This mapping will be provided by conversion object 1026 (WBS - CAPEX, OPEX, Statistical).
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. This mapping will be provided by conversion object 1026 (WBS - CAPEX, OPEX, Statistical).
3.	PF2 and WP2	COSP	BUKRS	Company Code	S/4HANA	ACDOCA	RBUKRS	Company Code	Conversion specs mapping "Company Code" (BUKRS: Old Company Code to New Company Code)
4.	PF2 and WP2	COSS	BUKRS	Company Code	S/4HANA	ACDOCA	RBUKRS	Company Code	Conversion specs mapping "Company Code" (BUKRS: Old Company Code to New Company Code)
5.	PF2 and WP2	PRPS	PRCTR	Profit Center	S/4HANA	ACDOCA	PRCTR	Profit Center	Conversion specs mapping "Profit Centre" (PRCTR: Old Profit Centre to New Profit Centre)
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	WTGxx	Value Transaction Curr	S/4HANA	ACDOCA	POPER	Posting Period
10.	PF2 and WP2	COSS	WTGxx	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	WTGxx	Value Transaction Curr	S/4HANA	ACDOCA	WSL	Amount in Transaction Currency	xx represents all periods for previous years. Value type (COSS-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. The extraction must refer as below: Group 1 go live (1 July 2028) to migrate the above WBS for: Accumulated balance up to 31 Dec 2026 Accumulated balance from 1 Jan 2027-31 Dec 2027 Monthly balance from 1 Jan 2028 till 30 June 2028 Group 2 go live (1 Jan 2029) to migrate the above WBS for: Accumulated balance up to 31 Dec 2026 Accumulated balance from 1 Jan 2027-31 Dec 2027 Monthly balance from 1 Jan 2028 till 31 Dec 2028 After extraction then statistical posting must be done, please refer to Appendix A. Note: Currency Adjustment During Migration (TCURX Consideration): In SAP, the TCURX table defines the number of decimal places used for each currency. This impacts how amounts are stored internally in database tables versus how they are displayed externally in user interfaces or reports. Currencies such as JPY (Japanese Yen), KRW (Korean Won), or VND (Vietnamese Dong) are typically configured with no decimal places (TCURX-CURRDEC = 0). Understanding and correctly applying the TCURX rules is essential during data migration to ensure financial consistency between ECC and S/4HANA. Internal vs External Currency Representation example: External Amount The amount value as displayed to users in SAP screens and reports. 96015 JPY Internal Amount The amount value stored in database tables for computation. 960.15 JPY Multiplied by factor = 10² if target has 2 decimals During data migration, these internal (technical) amounts must be converted to external amounts to ensure accuracy and consistency in the target S/4HANA system. Conversion Formula: External Amount = Internal Amount * 10 to the power (2 - Number of decimals for the currency in TCURX table)
	PF2 and WP2	COSP	WOGxx	Value in object currency (company code currency)	S/4HANA	ACDOCA	HSL	Amount in company code currency	xx represents all periods for previous years. Value type (COSS-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 WOGxxx, 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).
	PF2 and WP2	COSP	WKGxx	Value in controlling area currency	S/4HANA	ACDOCA	KSL	Amount in global currency	To be confirmed what exchange rate to be used for loading amount in EUR (as legacy system does not have group currency)
14.	PF2 and WP2	COSS	WTGxx	Value Transaction Curr	S/4HANA	ACDOCA	WSL	Amount in Transaction Currency	xx represents all periods for previous years. Value type (COSS-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. The extraction must refer as below: Group 1 go live (1 July 2028) to migrate the above WBS for: Accumulated balance up to 31 Dec 2026 Accumulated balance from 1 Jan 2027-31 Dec 2027 Monthly balance from 1 Jan 2028 till 30 June 2028 Group 2 go live (1 Jan 2029) to migrate the above WBS for: Accumulated balance up to 31 Dec 2026 Accumulated balance from 1 Jan 2027-31 Dec 2027 Monthly balance from 1 Jan 2028 till 31 Dec 2028 After extraction then statistical posting must be done, please refer to Appendix A. Note: Currency Adjustment During Migration (TCURX Consideration): In SAP, the TCURX table defines the number of decimal places used for each currency. This impacts how amounts are stored internally in database tables versus how they are displayed externally in user interfaces or reports. Currencies such as JPY (Japanese Yen), KRW (Korean Won), or VND (Vietnamese Dong) are typically configured with no decimal places (TCURX-CURRDEC = 0). Understanding and correctly applying the TCURX rules is essential during data migration to ensure financial consistency between ECC and S/4HANA. Internal vs External Currency Representation example: External Amount The amount value as displayed to users in SAP screens and reports. 96015 JPY Internal Amount The amount value stored in database tables for computation. 960.15 JPY Multiplied by factor = 10² if target has 2 decimals During data migration, these internal (technical) amounts must be converted to external amounts to ensure accuracy and consistency in the target S/4HANA system. Conversion Formula: External Amount = Internal Amount * 10 to the power (2 - Number of decimals for the currency in TCURX table)
	PF2 and WP2	COSS	WOGxx	Value in object currency (company code currency)	S/4HANA	ACDOCA	HSL	Amount in company code currency	xx represents all periods for previous years. Value type (COSS-WRTTP) must be “4” and Dr/Cr Indicator (COSS-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 WOGxx, with xx being the posting month. E.g. 01,02,03 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 8.774.093)., but the amount in column "Value Unconverted" is incorrect (JPY 87740.93)
	PF2 and WP2	COSS	WKGxx	Value in controlling area currency	S/4HANA	ACDOCA	KSL	Amount in global currency	To be confirmed what exchange rate to be sued for loading amount in EUR
15.	N/A				S/4HANA	ACDOCA	BLART	Document Type	Default to 9*
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 legacy WBS Element
18.	PF2 and WP2				S/4HANA	ACDOCA	BKTXT	Header Text	Default to “Data Object 9031”
19.	PF2 and WP2				S/4HANA	ACDOCA	RACCT	Offsetting GL Account	GL account that is used for mapping AUC reconciliation account. Awaiting Alex to advise on the AUC take-on account.

Transformation Mapping

Conversion Specification - Transformation Mapping Register - Google Sheets

Mapping Table Name	Mapping Table Description
Company code	BUKRS: Old Company Code to New Company Code
Cost Centre	KOSTL: Old Cost Centers to New Cost Centers
GL Accounts	HKONT: Old GL Accounts to New GL Accounts
Profit Centre	PRCTR: Old Profit Centre to New Profit Centre
Asset Number	ANLN1: Old Asset number to New Asset number (Map old Asset number to S/4HANA Fixed Asset number for CAPEX WBS Elements that have changed status to TECO)
WBS Elements	POSID: Old WBS Elements to New WBS Elements

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

The following pre-load validations will be performed by Project Team.

This is to validate the total transactional movement in each open WBS Element. Validate the financial movement of all transactions excluding settlement transactions by WBS Element by Cost Element (GL Account) for the open WBS Elements as the closing balance.

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

The following pre-load validations will be performed by the 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

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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Pre Cutover

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1.	Asset Classes
2.	Cost Element Groups
3.	Settlement Profiles
4.	Allocation Structures
5.	Previous Asset Fiscal Year to be opened
6.	Current Asset Fiscal Year to be opened
7.	Settlement cost elements used for settlement available in all company codes in scope
8.	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 Note: WBS release to generate AUC master
1067	GL Account Operational CoA (incl. secondary CE)
1074	Cost Centre
1073	Profit Centre
1022	Portfolio Item

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
Configuration	Document type does not exist in S/4HANA	Engage Functional team to fix the error in the system
Master Data	AUC take-on account does not exist	Ask GL team to create AUC take-on account
Technical Setup	Load tool refuses to load the data (whether that is LTMC, BDC or customized upload tool)	Fix the issue

Post-Load Validation

Project Team

The following post-load validations will be performed by the 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.

Post Load Activities

A. Settlement to Assets under Construction (AUC)

After validating the WBS Element transaction movements for count and accuracy, run settlement. Ensure that all Settlement objects have been created. For AUCs this will take place during the conversion from CRTD (Created) to REL (Released) status. This will provide balances to the AUCs.

For this data object, the settlement needs to be executed as below:

Group 1 Go live (1 July 2028):

Accumulated balance up to 31 Dec 2026
- Execute settlement with posting date 31.12.2026. The Asset Fiscal Year 2026 must be opened.

Accumulated balances from 1 Jan-31 Dec 2027
- Execute settlement with posting date 31.12.2027. The Asset Fiscal Year 2027 must be opened.
Monthly balance from 1 Jan 2028 till 30 June 2028
- Execute settlement for Current Fiscal Year with posting date as month end (e.g. 31 Jan 2028, 29 Feb 2028, etc.). The Asset Fiscal Year 2028 must be opened.

Group 2 Go live (1 Jan 2029):

Accumulated balances up to 31 Dec 2026

- Execute settlement with posting date 31.12.2026. The Asset Fiscal Year 2026 must be open.
Accumulated balances from 1 Jan-31 Dec 2027
- Execute settlement with posting date 31.12.2027. The Asset Fiscal Year 2027 must be opened.

Monthly balance from 1 Jan 2028 till 31 Dec 2028 (Prior Year)

- Execute settlement with posting date as month end (e.g. 31 Jan 2028, 29 Feb 2028, etc.). The Asset Fiscal Year 2028 must be open.

SAP Transaction CJ88 will be used to settle all the WBS Element costs to their respective settlement objects. For those that are settling to the AUCs a reconciliation must be created that will compare the AUCs in the legacy systems (PF2 and WP2) to those that are now in S/4HANA. Table ANLC will be used for this comparison.

The previous Fiscal year cannot be closed until the AUC reconciliation for the previous year is completed and balanced.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
Verify Counts	Business to verify the load count is the same as per identified data from Post Load Report.

Accuracy

Task	Action
Verify values	Ensure the Post Load report values are exactly the same as in the Pre Load report. These values have to be verified before settling the costs to the AUCs.

Appendix:

Reconciliation process for Assets under Construction (AUC):

Step

Description

Team responsible

1.

Identify all AUC asset classes

Use SAP Table ANKA – Asset Classes: General Data to identify all the AUC Asset Classes

Data Team

2.

Identify all assets under the AUC Asset Classes

Apply the results from the above table to identify all assets in legacy systems in table ANLA that are classified as Assets Under Construction.

Data Team

3.

Identify all the above Assets Under Construction that have a previous year balance.

The AUC may be restricted to only the ones with balances. Use table ANLC to gather year end balances.

When running the report in Table ANLC it must run by Company Code by selected asset number. If it is run by asset number alone, all assets from across all regions will be selected.

Data Team

4.

Identify all the above Assets Under Construction that have a current year balance.

Reconcile the results from the above report to identify any new AUC’s that may have been created in the current year.

Data Team

5.

Identify the monthly movements of all the above Assets Under Construction that have a previous or current year balance

Use table ANEP to extract all the monthly movements

Data Team

6.

This table shows all the fields that are to be extracted:

Table	Field	Field	Field	Field
ANKA	ANLKL	XOPVW	XINVM	TXK20
ANLA	BUKRS	ANLN1	ANLKL	XOPVW
		TXT50	XINVM
ANLC	BUKRS	ANLN1	ANLN2	GJAHR
	AFABE		KANSW	ANSWL
ANEP	BUKRS	ANLN1	ANLN2	GJAHR
	BELNR	BZDAT	ANBTR

Field Name	Description
ANKA-ANLKL	Asset Class
ANKA-XOPVW	Line Item Settlement
ANKA-XINVM	Investment Measure
ANKA-TXK20	Short Text
ANLA-BUKRS	Company Code
ANLA-ANLN1	Asset
ANLA-ANLKL	Asset Class
ANLA-XOPVW	Line Item Settlement
ANLA-TXT50	Text
ANLA-XINVM	Investment Measure
ANLC-BUKRS	Company Code
ANLC-ANLN1	Asset Number
ANLC-ANLN2	Sub Number
ANLC-GJAHR	Fiscal Year
ANLC-AFABE	Depreciation Area
ANLC-KANSW	Cumulative Acquisition Value
ANLC-ANSWL	Asset Value Transaction
ANEP-BUKRS	Company Code
ANEP-ANLN1	Asset
ANEP-ANLN2	Sub Number
ANEP-GJAHR	Fiscal Year
ANEP-BELNR	Document Number
ANEP-BZDAT	Asset Valuation Date
ANEP-ANBTR	Amount

Data Team

7.

Identify from which cost object the Asset Under Construction received financial postings

Apply the asset number and company code to this table to receive the results.

This will provide the cost object that will require the primary financial postings.

Table	Field	Field	Field	Field
COBRB	OBJNR	BUKRS	ANLN1	ANLN2

Explanation of the above fields:

Field Name	Description
COBRB-OBJNR	Object Number
COBRB-BUKRS	Company Code
COBRB-ANLN1	Asset Number
COBRB-ANLN2	Sub Number

This will provide the Object Number from which we can identify the real WBS Element in Table PRPS or the Internal Order number in table AUFK.

Data Team

8.

Settle the cost object financial postings to the new Asset Under Construction

From there, these financial postings can be settled into the new S/4HANA AUC.

The new AUC will be created when the cost object is released (from CRTD to REL).

Data Team

9.

Identify the cost object to which the settlement rule applies.

Use table COBRB restricted to the WBS Elements selected above

Data Team

10.

Identify the internal and external financial postings in each WBS Element.

Use tables COSP and COSS to collect the monthly movement by WBS Element by cost element by object currency.

Data Team

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
WBS is in scope based on data design and any exception requested by business.
All WBS Elements/Internal Orders 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 systems PF2 and WP2 (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.

Any additional key assumptions.

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

A. Extraction Run Sheet for legacy WBS Elements settling to AUCs

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Pre Cutover

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Completeness

Accuracy

Identify all AUC asset classes

Identify all assets under the AUC Asset Classes

Identify all the above Assets Under Construction that have a previous year balance.

Identify all the above Assets Under Construction that have a current year balance.

Identify the monthly movements of all the above Assets Under Construction that have a previous or current year balance

Identify from which cost object the Asset Under Construction received financial postings

Settle the cost object financial postings to the new Asset Under Construction

Identify the cost object to which the settlement rule applies.

Identify the internal and external financial postings in each WBS Element.

Key Assumptions

See also

Change log

Workflow history