Stakeholders

Status

pagestatus

Percentage Progress | Vectors (Formerly: SP Percentage progress bar)

backgroundColor	0052CC
percentage	100

Owner

Maytingsari Tjahjo

GOTTIPATI-ext, Madhu

Stakeholders

LARU-ext, Soumen NADAR-ext, Parvati AGGARWAL-ext, Vikhyat PILLAY-ext, Lawrence BIDALIA-ext, Kuldeep BECHTER-ext, Alex

Purpose

The purpose of this document is to define the conversion approach to migrate the balance of active OPEX WBS Projects in scope from legacy system to to S/4HANA, so Project manager is Business User are able to know the entire cost of its active OPEX project.

Only certain closed OPEX project types (e.g. R&I, Maintenance OPEX) that have cost in current year must also be migrated.

For To-Be design, Internal order will be mapped to either to real or statistical OPEX WBS. 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.

Group 1 (Go live 1 July 2028):

Extract accumulated balances up to 31 Dec 2026
- All the financial transactions posted of all open WBS Elements as of 31 Dec 2026 will be totaled into the one single value and then be posted to the relevant WBS Elements in S/4HANA. Then run settlement from WBS to Cost Center.
Extract monthly balances from 1 Jan 2027 till 31 Dec 2027
- All the financial transactions posted of all open WBS Elements from 1 Jan 2027 till 31 Dec 2027 will be totaled by month into the one single value and then be posted to the relevant WBS Elements in S/4HANA in each posting period. Then run settlement from WBS to Cost Center.
Extract monthly balances from 1 Jan 2028 till 30 Jun 2028
- All the financial transactions posted of all open WBS Elements from 1 Jan 2028 till 30 Jun 2028 will be totaled by month into the one single value and then be posted to the relevant WBS Elements in S/4HANA in each posting period. Only certain closed OPEX project types (e.g. R&I, Maintenance OPEX) that have cost in current year must also be migrated. Then run settlement from WBS to Cost Center.

Group 2 (Go live 1 Jan 2029):

Extract accumulated balances up to 31 Dec 2027
- All the financial transactions posted of all open WBS Elements as of 31 Dec 2027 will be totaled into the one single value and then be posted to the relevant WBS Elements in S/4HANA. Then run settlement from WBS to Cost Center.
Extract monthly balances from 1 Jan 2028 till 31 Dec 2028
- All the financial transactions posted of all open WBS Elements from 1 Jan 2028 till 31 Dec 2028 will be totaled by month into the one single value and then be posted to the relevant WBS Elements in S/4HANA in each posting period. Only certain closed OPEX project types (e.g. R&I, Maintenance OPEX) that have cost in current year must also be migrated. Then run settlement from WBS to Cost Center.

Conversion Scope

The scope of this document covers the approach for converting active OPEX WBS element from Legacy Source Systems into S/4HANA.

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.

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:

All OPEX WBS with status not equal to Closed (CLSD).
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).

List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2 and WP2

OPEX Project level exclusions based on following relevancy rules:

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

S/4HANAPF2 and WP2

Any WBS element that is not closed as at the end of the previous fiscal year will be migrated. After eliminating all closed WBS elements, the relevancy rule will look for any WBS element that is not marked for deletion as at the end of the previous fiscal year for migration.

Exceptions:

Any closed WBS element that exists within an open Project.
Any WBS element that is marked for deletion that exists in an open Project.
Any closed WBS element that is affected by an open Projects.

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

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.

projects 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.

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

Active OPEX Project/WBS as per cutover date (i.e. 30 June 2028 for Grp 1 & 31 Dec 2028 for Grp 2)
Closed OPEX Project/WBS (exclude "Recharge Cost", "Provision" and "Statistical" WBS) that have cost in current year (the reporting year aligned with go-live, covering the collection of monthly balances)

Conversion specs 1026 will provide the list of the WBS OPEX 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 OPEX projects as below:

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

- Accumulated balance up to 31 Dec 2026 (Statistical Posting)
- Accumulated balance from 1 Jan 2027-31 Dec 2027. (Statistical Posting)
- Monthly balance from 1 Jan 2028 till 30 June 2028. (Statistical Posting)

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

- Accumulated balance up to 31 Dec 2026. (Statistical Posting)
- Accumulated balance from 1 Jan 2027-31 Dec 2027. (Statistical Posting)
- Monthly balance from 1 Jan 2028 till 31 Dec 2028. (Statistical Posting)

The above balance will be posted as Statistical Posting to avoid double count from Trial Balance loading.

The data from legacy system includes:

OPEX Project
CAPEX Project which has OPEX WBS. ~~Note: IS & R&I CAPEX projects have component OPEX that settled to PSG whereas IT projects have component OPEX that settled to Cost Center~~

The data from legacy system excludes:

Recharge WBS
Provision WBS
Statistical WBS

Appendix A

Group 1 go live:

Assumption: WBS OPEX always zero at month end

Based on the WBS list from Conversion Specs#1026, post the financial transactions up to 31 Dec 2026 into one single value by WBS and by original G/L expense as a statistical posting.

Migration of Project OPEX Balances - Group 1 Go Live (Part 1)

Fiscal Year	Total Cost WBS OPEX
Acc balance up to 31 Dec 2026	100

Step 1 (Statistical Posting Transaction Code KAFD) to avoid double count from Trial Balance load

Dr/Cr	G/L	Amount	Object	Translation Date
Dr	Transformed Cost Element	100	WBS	31-Dec-26

Based on the WBS list from Conversion Specs#1026, post the financial transactions from 1 Jan-31 Dec 2027 into one single value by WBS and by original G/L expense as a statistical posting.

Migration of Project OPEX Balances - Group 1 Go Live (Part 2)

Fiscal Year	Total Cost WBS OPEX
Acc balance Jan-Dec 2027	30

Step 1 (Statistical Posting Transaction Code KAFD) to avoid double count from Trial Balance load

Dr/Cr	G/L	Amount	Object	Translation Date
Dr	Transformed Cost Element	30	WBS	31-Dec-27

Based on the WBS list from Conversion Specs#1026, post the financial transactions monthly balance from 1 Jan-30 June 2028 into one single value by month, by WBS and by original G/L expense as a statistical posting.

Migration of Project OPEX balances - Group 1 Go LIve (Part 3)

Fiscal Year	Total Cost WBS OPEX
Jan-28	70
Feb-28	80
Mar-28	60
Apr-28	90
May-28	50
Jun-28	20

Step 1 (Statistical Posting Transaction Code KAFD) to avoid double count from Trial Balance load.

Dr/Cr	G/L	Amount	Object	Translation Date
Dr	Transformed Cost Element	70	WBS	31-Jan-28
Dr	Transformed Cost Element	80	WBS	29-Feb-28
Dr	Transformed Cost Element	60	WBS	31-Mar-28
Dr	Transformed Cost Element	90	WBS	30-Apr-28
Dr	Transformed Cost Element	50	WBS	31-May-28
Dr	Transformed Cost Element	20	WBS	30-Jun-28

Group 2 go live:

Based on the WBS list from Conversion Specs#1026, post the financial transactions up to 31 Dec 2026 into one single value by WBS and by original G/L expense as a statistical posting.

Migration of Project OPEX Balances - Group 2 Go live (Part 1)

Fiscal Year	Total Cost WBS OPEX
Up to 31 Dec 2026	150

Step 1 (Statistical Posting Transaction Code KAFD) to avoid double count from Trial Balance load

Dr/Cr	G/L	Amount	Object	Translation Date
Dr	Transformed Cost Element	150	WBS	31-Dec-26

Based on the WBS list from Conversion Specs#1026, post the financial transactions from 1 Jan 2027-31 Dec 2027 into one single value by WBS and by original G/L expense as a statistical posting.

Migration of Project OPEX Balances - Group 2 Go live (Part 2)

Fiscal Year	Total Cost WBS OPEX
Acc balance Jan-Dec 2027	90

Step 1 (Statistical Posting Transaction Code KAFD) to avoid double count from Trial Balance load

Dr/Cr	G/L	Amount	Object	Translation Date
Dr	Transformed Cost Element	90	WBS	31-Dec-27

Based on the WBS list from Conversion Specs#1026, post the financial transactions monthly balance from 1 Jan 2028-30 June 2028 into one single value by month, by WBS and by original G/L expense as a statistical posting.

Migration of Project OPEX Balances Group 2 Go live (Part 3)

Fiscal Year	Total Cost of WBS OPEX
Jan-28	20
Feb-28	50
Mar-28	60
Apr-28	70
May-28	10
Jun-28	90
Jul-28	100
Aug-28	40
Sept-28	80
Oct-28	15
Nov-28	35
Dec-28	25

Step 1 (Statistical Posting Transaction Code KAFD) to avoid double count from Trial Balance load

Dr/Cr	G/L	Amount	Object	Translation Date
Dr	Transformed Cost Element	20	WBS	31-Jan-28
Dr	Transformed Cost Element	50	WBS	29-Feb-28
Dr	Transformed Cost Element	60	WBS	31-Mar-28
Dr	Transformed Cost Element	70	WBS	30-Apr-28
Dr	Transformed Cost Element	10	WBS	31-May-28
Dr	Transformed Cost Element	90	WBS	30-Jun-28
Dr	Transformed Cost Element	100	WBS	31-Jul-28
Dr	Transformed Cost Element	40	WBS	31-Aug-28
Dr	Transformed Cost Element	80	WBS	30-Sept-28
Dr	Transformed Cost Element	15	WBS	31-Oct-28
Dr	Transformed Cost Element	35	WBS	30-Nov-28
Dr	Transformed Cost Element	25	WBS	31-Dec-28

The total of the legacy settlement transactions (COSP / COSS) will also be reconciled against the total costs posted to the WBS Element to ensure that all costs have been captured.

List of source systems and approximate number of records.

Source	Scope	Target System
PF2	Extraction of Project cost values for primary cost elements (COSP)	S/4HANA
WP2	Extraction of Project cost values for primary cost elements (COSP)	S/4HANA
PF2	Extraction of Project cost values for secondary cost elements (COSS)	S/4HANA
WP2	Extraction of Project cost values for secondary cost elements (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

Project OPEX actual cost 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

The technical design of the target for this conversion approach for statistical posting (Transaction code KAFD) is as below:

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
COEP	OBJNR	J_OBJNR	Object Number	CHAR	22	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
	WWERT	WWERT_D	Translation Date	DATS	8	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
COEP	WRTTP	CO_WRTTP	Value Type	CHAR	2	System generated
COEP	VRGNG	CO_VORGANG	Business Transaction	CHAR	4	System generated
COEP	VERSN	VERSN	Version	CHAR	3	System generated

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

Data Cleansing

ID

Criticality

Error Message/Report Description

Rule

Output

Source System

1

C2 (Data can be loaded into SAP but not Business Ready)

Report that shows OPEX WBS with its balances on at the end of month

Action item:

In ECC, Business must settle OPEX WBS if the OPEX WBS balance is not zero at the end of month.

Run transaction code CJI3, the balance of WBS OPEX in scope must be zero.

List of WBS with its balance

PF2 and WP2

2

C2 (Data can be loaded into SAP but not Business Ready)

Report that shows if any balances left for Works order

Action item:

In ECC, Business must settle all Work order costs to WBS if the WO balances is not zero at the end of the month

Run transaction code KOB1, the balance of WO in scope must be zero

List of Works order with its Balance

PF2 and WP2

TableFieldData ElementField DescriptionData TypeLengthRequirement

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

IDCriticalityError Message/Report DescriptionRuleOutputSource System

Conversion Process

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

Image RemovedImage Added

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

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

;

1. 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 .

This is to be conducted using DCT (Data Collection Template) in

1. source system extract/report.

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.

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.
Go to source system (PF2 and WP2) Secondary Costs Total (Table COSS)
Req # Requirement Description Team Responsible 1. Data Team Responsible
21.
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.
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
a. Get the list of WBS in scope from Conversion Specs#1026.
b. Then extract the object numbers of these WBS Elements from table PRPS from source systems.
c. Execute table COBRB by specifying the object numbers (from point b) and field "Account Assignment Category" = All settlement receiver excluding FXA and excluding WBS that is settled to WBS in the same project
Field Value
Object Numbers
Enter the Object Numbers as the above steps
Account Assignment Category
All settlement receiver excluding FXA and excluding WBS that is settled to WBS in the same project

Syniti Team

The following tables will be used to extract the settlement data:
Primary Cost Total (COSP) table
Secondary Cost Total (COSS) table

2.
Go to source systems to get the Primary Costs Total (Table COSP) and Secondary cost total (Table COSS)
Retrieve the object numbers from Step 1 then extract the values from the COSP and COSS table.
3.
Go to source systems (PF2 and WP2) Primary Costs Total (Table COSP)
Field Value
Object Numbers
For each relevant WBS Element extract
Enter 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
Object Currency value for each period for each year WOG01 to WOG16
numbers (from Step 1c)
Fiscal Year
Refer to Appendix A
Group 1 go live (1 July 2028) to migrate the above WBS for:
Accumulated balance up to 31 Dec 2026 (Statistical Posting)
Accumulated balance from 1 Jan 2027-31 Dec 2027. (Statistical Posting)
Monthly balance from 1 Jan 2028 till 30 June 2028. (Statistical Posting)
Group 2 go live (1 Jan 2029) to migrate the above WBS for:
Accumulated balance up to 31 Dec 2026. (Statistical Posting)
Accumulated balance from 1 Jan 2027-31 Dec 2027. (Statistical Posting)
Monthly balance from 1 Jan 2028 till 31 Dec 2028. (Statistical Posting)
Value Type                   04 (Actual)
Cost Element
FieldValueObject NumbersFor 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 Type04Cost Element
Leave it blank
Dr/CR
Indicator
Indicator
OObject Currency value for each period for each yearWOG01 to WOG16
From the above, system will generate report as below.
≠O (Special: Sender credit from settlement)
Go to source system to get the Secondary Costs Total (Table COSS) The report will need to be summarized by object number by total for all the fiscal years.
Field Value
Object Numbers
PR***Fiscal YearThere will be values for each Fiscal Year.Value Type04Cost ElementThe cost element to which the transaction was posted.Dr/CR IndicatorOObject Currency value for each period for each yearWOG01 to WOG16Company CodeCompany code where the transaction was posted
Data Team4.
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
Enter the object numbers (from Step 1c)
Fiscal Year
Refer to Appendix A
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.
Value Type 04 (Actual)
Cost Element Leave it blank
Dr/CR Indicator ≠O (Special: Sender credit from settlement)
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.
Field Value
Object Numbers PR*
Fiscal Year Corresponding Fiscal Year will be shown
Value Type 04 (Actual)
Cost Element The cost element to which the transactions were posted.
Dr/CR Indicator ≠O (Special: Sender credit from settlement)
Value transaction currency WTG001 to WTG016
Company Code Company code where the transaction was posted
Syniti Team3.
Step #2 provides what needs to be posted for each WBS Element. The posting must use the original cost elements, that will be mapped to S/4 cost element.
Syniti Team4.
Once the balance has been agreed above, post statistical posting by WBS and by original G/L as described in Appendix A
Syniti
5.
Extract the Settlement Rule object from table COBRB in source systems (PF2 and WP2) to find the settlement objects for the above project.
FieldValueObject Numbers
Enter the same Object Numbers as the above steps for Primary Costs (Table COSP) and Secondary Costs (Table COSS).
System will provide a report as below that will include the following fields:
FieldExampleObject NumbersPR******Account Assignment Category
Will return one of the following
Fixed Asset
Cost Centre
GL Account
Company Code Company code where the transaction was postedG/L Account If the Account Assignment is SK, an entry will appear in this fieldCost Centre   If the Account Assignment is KS, an entry will appear in this field. This is applicable for object 9032.AssetIf the Account Assignment is AN, an entry will appear in this field. This will possibly show both (the Final asset and the AUC) if any values have been posted to the final asset.
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 Team6.
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 NameField DescriptionRule

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

N/A.

Extraction Dependencies

Item #	Step Description	Team Responsible
1.	List of WBS in scope from Conversion Specs#1026	Data Team

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 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. Legacy G/L is mapped to S/4HAN GL 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

Extraction Dependencies

Item #Step DescriptionTeam Responsible1.All OPEX WBS element cleansing has been completed in PF2 and WP2Business

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.
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
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 DescriptionTeam Responsible1.

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 systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1.PF2 and WP2COSPOBJNRObject NumberS/4HANAACDOCAPOSIDWBS Element NumberCOSP 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 WP2COSSOBJNRObject NumberS/4HANAACDOCAPOSIDWBS Element NumberCOSS 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 WP2COSPBUKRSCompany CodeS/4HANAACDOCARBUKRSCompany Code

Mapping table from legacy company code to S/4HANA Company Code.

4.PF2 and WP2COSSBUKRSCompany CodeS/4HANAACDOCARBUKRSCompany Code

Mapping table from legacy company code to S/4HANA Company Code.

5.PF2 and WP2PRPSPRCTRProfit CenterS/4HANAACDOCAPRCTRProfit CenterMap Legacy Profit Centre to the S/4 HANA Profit Centers.6.PF2 and WP2COSPGJAHRFiscal YearS/4HANAACDOCAGJAHRFiscal Year7.PF2 and WP2COSSGJAHRFiscal YearS/4HANAACDOCAGJAHRFiscal Year8.N/AN/AN/AN/AS/4HANAACDOCARACCTAccount NumberUse GL Account to post to the new WBS Element. TBC9.PF2 and WP2COSPWOGxxValue Obj CurrS/4HANAACDOCAPOPERPosting Period

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	COEP	OBJNR	Object 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	COEP	OBJNR	Object 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	GJAHR	Fiscal Year	S/4HANA	COEP	GJAHR	Fiscal Year	Copy from source
4.	PF2 and WP2	COSS	GJAHR	Fiscal Year	S/4HANA	COEP	GJAHR	Fiscal Year	Copy from source
5.	PF2 and WP2	COSP	KSTAR	Cost Element	S/4HANA	COEP	KSTAR	Cost Element	Refer to Mapping legacy GL Accounts to S/4HANA GL Accounts
6.	PF2 and WP2	COSS	KSTAR	Cost Element	S/4HANA	COEP	KSTAR	Cost Element	Refer to Mapping legacy GL Accounts to S/4HANA GL Accounts
7.	PF2 and WP2	COSP	WTGxxx	Value in Transaction currency	S/4HANA	COEP	PERIO	Posting Period	The COSP source table stores period-based data in a columnar format, where each period is represented by an amount column suffixed with values such as 01, 02, and so on. To prepare the data for each period, these columns must be pivoted using the remaining attribute columns as qualifiers. The corresponding period numbers will also be derived during this pivoting process.
8.	PF2 and WP2	COSS	WTGxxx	Value in Transaction currency	S/4HANA	COEP	PERIO	Posting Period	The COSS source tables store period-based data in a columnar format, where each period is represented by an Amount column suffixed with values such as 01, 02, and so on. To prepare the data for each period, these columns must be pivoted using the remaining attribute columns as qualifiers. The corresponding period numbers will also be derived during this pivoting process.
9.	PF2 and WP2	COSP	WTGxxx	Value in Transaction Curr for relevant period Note: xxx represent the period	S/4HANA	COEP	WTGBTR	Total Value 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”. 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)

10.

PF2 and WP2

COSS

WOGxx

WTGxxx

Value

Obj

in Transaction Curr

S/4HANAACDOCAPOPERPosting Period11.N/A

for relevant period

Note:

xxx represent the period

S/4HANA

ACDOCABUDATPosting Date12.N/AS/4HANAACDOCABLDATDocument Date13.PF2 and WP2COSPWOGxxValue Obj CurrS/4HANAACDOCAWSLAmount 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 WOGxx, with xx being the posting month. E.g. 01,02,03

14.PF2 and WP2COSSWOGxxValue Obj CurrS/4HANAACDOCAWSLAmount 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 WOGxx, with xx being the posting month. E.g. 01,02,03

15.N/AS/4HANAACDOCABLARTDocument TypeDefault to UE? TBC16.N/AS/4HANAACDOCAUSNAMUser NameDefault to data migration user ID17.N/AS/4HANAACDOCASGTXTItem Text

Specify source WBS Element

18.PF2 and WP2S/4HANAACDOCABKTXTHeader Text

Default to “Data Object 9032”

19.PF2 and WP2S/4HANAACDOCARACCTOffsetting 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 NameMapping 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 commenceItem #Step DescriptionTeam Responsible1.Ensure all the fields that require value mapping, as stipulated in Section "Mapping tables", have the correct values mapped.Data Team

COEP	WTGBTR	Total Value in Transaction 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”. 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)
11.	PF2 and WP2	COSP	TWAER	Transaction Currency	S/4HANA	COEP	TWAER	Transaction Currency	Copy from source
12.	PF2 and WP2	COSS	TWAER	Transaction Currency	S/4HANA	COEP	TWAER	Transaction Currency	Copy from source
13.					S/4HANA		WWERT	Translation Date	Pls refer to Appendix A to assign the Translation Date for each extraction. System will use Translation Date to convert it to Company Code Currency and Group Currency.

List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.

Transformation Mapping

Mapping Table Name	Mapping Table Description
GL Accounts	Mapping legacy GL Accounts to S/4HANA GL Accounts
WBS Elements	Mapping legacy WBS Elements to S/4HANA 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

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 (COSP and COSS) agree with the total transaction costs in transaction code CJI3 (by excluding "Dr/Cr Indicator" as "≠O") 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 actual cost of OPEX Project must be the same as total amount in CJI3 (by excluding settlement i.e. by excluding "Dr/Cr Indicator" as "=O") = Table COEP.

Total actual cost of WBS must be the same as total settlement amount (Total amount with value type 4 and Dr/Cr indicator O of table COSP and COSS).

Business

Completeness

Task	Action
Verify counts	Business will use the preload report to validate the number of WBS Elements that will migrate values.
Validate	Validate that the extracted values from both tables (COSP and COSS) with value type 4 and "Dr/Cr Indicator" as "=O" agree with the total transaction costs in transaction code CJI3 (by excluding "Dr/Cr Indicator" as "O") for each individual WBS Element.

Accuracy

Task

Action

Validate

Validate that the extracted values are identical to those values posted to the WBS Element

Reconcile

Total actual cost of OPEX Project must be the same as total amount in CJI3 (by excluding settlement i.e. by excluding "Dr/Cr Indicator" as "=O") = Table COEP.

Total actual cost of WBS must be the same as total settlement amount (Total amount with value type 4 and Dr/Cr indicator =O of table COSP and COSS).

Pre-Load Validation

Project Team

Completeness

TaskAction

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

TaskActionValidateValidate that the extracted values from both tables agree with the total transaction costs excluding settlement for each individual WBS ElementValidateValidate 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

TaskActionVerify 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

load tool.
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

Cutover 4 : These objects will be loaded in Release 4.

Syniti Team7.Validate Post Load report.Business

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Number range has been assigned for transaction code KAFD
2	Ensure steps in OSS 2852746 - Trnsaction KAFD: No Line Items created - SAP for Me have been completed. This is to have KAFD posting reflected correctly in COEP and CJI3.

Conversion Objects

Object #	Preceding Object Conversion Approach
1024	Project Definition (CAPEX, OPEX)
1026	WBS - CAPEX, OPEX, Statistical

Error Handling

Error Type	Error Description	Action Taken
Missing number range	Number range has not been assigned for transaction code KAFD	Engage Functional team to fix the error in the system
Missing WBS	WBS has not been created in S/4HANA hence WBS balance cannot be loaded	Engage I2M Data team to create the relevant WBS.
Missing GL account	GL account has not been created in S/4HANA	Engage GL Data team to create the relevant GL.
	Due to certain reason, statistical posting must be reversed	Data team to execute transaction code KAFL

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. This value must be verified before posting KAFD.

Business

Item #Configuration Item1.Cost Element Groups2.Settlement Profiles3.Allocation Structures4.Settlement cost elements used for settlement available in all company codes in scope5.Number ranges for settlement documents to be set up. This is manual config.

Conversion Objects

Object #Preceding Object Conversion Approach1024Project Definition (CAPEX, OPEX)1025Project Text & Documents (attachments)1026WBS - CAPEX, OPEX, Statistical

Error Handling

Error TypeError DescriptionAction TakenConfigurationDocument type does not exist in S/4HANAEngage Functional team to fix the error in the system

Post-Load Validation

Project Team

Completeness

Task	Action
Verify Counts	Data team Business to verify the load count is the same as per identified data from Pre Post Load fileReports

Accuracy

Task	Action
Verify values	Ensure the Pre-Post 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

TaskAction

Accuracy

TaskAction

Preload Report.

Reconcile

Total actual cost of OPEX Project must be the same as total amount in CJI3 (by excluding settlement i.e. by excluding "Dr/Cr Indicator" as "≠O") = Table COEP.

Total actual cost of WBS must be the same as total settlement amount (Total amount with value type 4 and Dr/Cr indicator ≠O of table COSP and COSS).

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

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.
~~Ensure steps in OSS 2852746 - Trnsaction KAFD: No Line Items created - SAP for Me have been completed. This is to have KAFD posting reflected correctly in COEP and CJI3.~~

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Apr 07, 2026	Actor	Type	Activity	Version
Approved	VILLI-ext, Ramaraj	Comment	commented 1:44 pm GOTTIPATI-ext, Madhu Could you please mention the Target table for this field?
Approved	VILLI-ext, Ramaraj	Comment	commented 1:43 pm GOTTIPATI-ext, Madhu Could you please mention the Target table for this field?
Mar 02, 2026
	TAN-ext, Charmaine	State	changed state to Approved at 3:10 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v78
Feb 18, 2026
Peer Review	BIDALIA-ext, Kuldeep	State	gave Peer Review approval at 11:17 am
	GOTTIPATI-ext, Madhu	State	assigned approval Peer Review to BIDALIA-ext, Kuldeep at 10:34 am
	GOTTIPATI-ext, Madhu	State	assigned approval Peer Review to AGGARWAL-ext, Vikhyat at 9:55 am
	UPADHYAY-ext, Anjali	State	gave Peer Review approval at 6:47 am

numbers (from Step 1c)
Fiscal Year	Refer to Appendix A Group 1 go live (1 July 2028) to migrate the above WBS for: Accumulated balance up to 31 Dec 2026 (Statistical Posting) Accumulated balance from 1 Jan 2027-31 Dec 2027. (Statistical Posting) Monthly balance from 1 Jan 2028 till 30 June 2028. (Statistical Posting) Group 2 go live (1 Jan 2029) to migrate the above WBS for: Accumulated balance up to 31 Dec 2026. (Statistical Posting) Accumulated balance from 1 Jan 2027-31 Dec 2027. (Statistical Posting) Monthly balance from 1 Jan 2028 till 31 Dec 2028. (Statistical Posting)
Value Type	04 (Actual)
Cost Element

Enter the object numbers (from Step 1c)
Fiscal Year	Refer to Appendix A 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.
Value Type	04 (Actual)
Cost Element	Leave it blank
Dr/CR Indicator	≠O (Special: Sender credit from settlement)

Field	Value
Object Numbers	PR*******
Fiscal Year	Corresponding Fiscal Year will be shown
Value Type	04 (Actual)
Cost Element	The cost element to which the transactions were posted.
Dr/CR Indicator	≠O (Special: Sender credit from settlement)
Value transaction currency	WTG001 to WTG016
Company Code	Company code where the transaction was posted

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 6

New Version Current

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Multi-language Requirement

Document Management

Legal Requirement

Target Design

Data Cleansing

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Transformation

Transformation Run Sheet

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history