Status	Approved
Owner	KOHN-ext, Jacob
Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Project Budget in S/4 HANA.

Conversion Scope

The scope of this document covers the approach for converting Project Budgets from Legacy Source Systems into Project and Item Budgets in S/4HANA.

For items created with legacy project id's the budget for the item will be the annual budget of the level 1 WBS element from the legacy system with some enrichment requirements, there is also requirement to capture budget for items which is not available in source system.

The data from legacy system includes:

Level 1 WBS element budgets for S/4 PPM Items with Legacy Project ID as created in CNV-1022 Portfolio Item

The data from legacy system excludes:

Additionally, there will be Items included in the DCT which does not have Budget in the legacy system

Projects with legacy ID
- IT Projects
- R&I Projects

Projects with no legacy ID
- Direct Asset purchases for which an Item is created for GBU/Company Code/Plant combination
- Capital Spare for which an item is created for GBU/Company Code/Plant combination
- Capital Lease for which an item is created for GBU/Company Code/Plant combination
- Cluster Item
- Budget Provision Item

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Annual WBS Budget values for projects migrated through CNV-1022 PPM Items	5000	S/4 Hana	4000
WP2	Annual WBS Budget values for projects migrated through CNV-1022 PPM Items	9000	S/4 Hana	6000
DCT	Annual WBS Budget values for projects which have no budget in Source (e.g. IT and R&I)

After loading the budget to the PPM Item the budget is transferred to the level 1 WBS element where the WBS elements have been created.

Selection Logic

Get Legacy Project Internal number ( from table PROJ using the Legacy Project ID from the S/4 PPM item

Get Level 1 WBS Object Number ( ) from table PRPS legacy using the Legacy Project internal number and Stufe="1"

Get Budget Value ( ) and Year ( ) from table BPJA using Level 1 WBS Object Number, Value Type ="41" and Budget Type =

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
/RPM/FIN_PLAN	EXTERNAL_ID	/RPM/TV_EXTID	Item ID	CHAR	24	Mandatory
/RPM/FIN_PLAN	FIN_VIEW_ID	/RPM/TV_FIN_VIEW	Financial View Type	NUM	2	Mandatory
/RPM/FIN_PLAN	FIN_VIEW_DESC	/RPM/TV_FIN_VIEW_DESC	Financial View Name	CHAR	40	Mandatory
/RPM/FIN_PLAN	CATEGORY_ID	/RPM/TV_FIN_CATG	Financial Category	CHAR	15	Mandatory
/RPM/FIN_PLAN	CATEGORY_TEXT	/RPM/TV_FIN_CATG_T	Financial Category text	CHAR	80	Mandatory
/RPM/FIN_PLAN	GROUP_ID	/RPM/TV_FIN_GRP	Financial Group	CHAR	15	Mandatory
/RPM/FIN_PLAN	GROUP_TEXT	/RPM/TV_FIN_GRP_T	Financial Group text	CHAR	80	Mandatory
/RPM/FIN_PLAN	PERIOD	/RPM/TV_START_DATE	Start Date	DATS	8	Mandatory
/RPM/FIN_PLAN	AMOUNT	/RPM/TV_CURR_AMOUNT	Financial Amount	NUM	26	Mandatory
/RPM/FIN_PLAN	CURRENCY	/RPM/TV_CURRENCY	Currency	CHAR	5	Mandatory
/RPM/FIN_PLAN	PERIOD_TYPE	/RPM/TV_PER_CONVFACTOR	Period Conversion Factor	NUM	2	Mandatory
BPJA	OBJNR	BP_OBJEKT	Object number	CHAR	22	Mandatory
BPJA	WRTTP	CO_WRTTP	Value Type	CHAR	2	Mandatory
BPJA	GJAHR	GJAHR	Fiscal Year	NUMC	4	Mandatory
BPJA	VORGA	BP_VORGANG	Budget Type	CHAR	4	Mandatory
BPJA	TWAER	TWAER	Transaction Currency	CUKY	5	Mandatory
BPJA	WTJHR	BP_WJT	Annual value	CURR	21	Mandatory

Data Cleansing

Cleansing is done on the master data objects to which the budgets relate, no specific budget cleansing is required.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Data Privacy and Sensitivity

Is there privacy and sensitivity concerns for project budgets?

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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system	SyWay Data Team
1	Ensure DCT is collected	Data Team
2	Perform preliminary completeness check, data quality check.	Data Team
3	Raise issues as defects if Req # 1 to 2 are not met	Data Team
4	Repeat Req # 1 to 3 if required	Data Team

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
Not Applicable

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Project Budget data with exception of some fields which require transformation as mentioned in the transformation rule.

Project Budget DCT Rules

Item Level

Field Name	Field Description	Rule
EXTERNAL_ID	PPM Item ID	This is a dropdown field of PPM Items The values are restricted to the PPM items created in CNV-1022, for selection both the item number and Name is to be displayed.
SG_CATEGORY	Suggested Financial Category
CATEGORY_TEXT	Financial Category text	This is a dropdown field that differentiates between the Capital and Operating Financial Categories.
YEAR	Fiscal Year	This is the fiscal year to which the budget is assigned
AMOUNT	Financial Amount	The Approved funding value for the year

WBS Level

Field Name	Field Description	Rule
PSPID	Project Definition	This is a dropdown field of Project Definitions The values are restricted to the Project Definitions created in CNV-1022, for selection both the item number and Name is to be displayed.
POSID	WBS Element	This is a dropdown field of Phase level WBS Elements of the project selected PRPS with STUFE = 2 and PSPHI = PSPID
YEAR	Fiscal Year	This is the fiscal year to which the budget is assigned
WTJHR	Amount	The budget assigned to the phase

Extraction Dependencies

Item #	Step Description	Team Responsible

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	Execute and Load and perform Transformation	Data Team
2	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
3	Review and Validate Error and Preload Reports	Data Team
4	Generate data load count.	Data team
5	Generate Load Files	Data Team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Re-transform and re-validate the Pre-load reports if necessary.	Data team
8	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
9	Analyze and resolve any pre-load defects logged by business.	Data team
10	Repeat steps 7 to 10 if necessary	Data team
11	Proceed to pre-load validations	Data team

Transformation Rules

Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
WP2/PF2	PROJ	PSPID	Project ID	S/4 Hana	/RPM/ITEM_D	EXTERNAL_ID	Item ID	Select the ID field from /RPM/ITEM_D where legacy project ID = PSPID
				S/4 Hana	/RPM/FIN_PLAN	FIN_VIEW_ID	Financial View Type	Default to Approved Funding
				S/4 Hana		FIN_VIEW_DESC	Financial View Name	If required read from
				S/4 Hana	/RPM/FIN_CAT	CATEGORY_ID	Financial Category	Select from CATEGORY_T using CATEGORY_TEXT
				S/4 Hana	/RPM/FIN_GROUP	GROUP_ID	Financial Group	Default
				S/4 Hana		GROUP_TEXT	Financial Group text	Select from /RPM/FIN_GROUPST using CATEGORY_ID and GROUP_ID
WP2/PF2	BPJA	GJAHR		S/4 Hana	/RPM/FIN_PLAN	PERIOD	Start Date	Convert year into yyyymmdd by adding 0101
WP2/PF2	BPJA	BP_WJT		S/4 Hana	/RPM/FIN_PLAN	AMOUNT	Financial Amount	Copy from Source
WP2/PF2	BPJA	TWAER		S/4 Hana	/RPM/FIN_PLAN	CURRENCY	Currency	Copy from Source
				S/4 Hana	/RPM/FIN_PLAN	PERIOD_TYPE	Period Conversion Factor	Default value "12"
DCT	Item	EXTERNAL_ID	Item ID					Manually copy from Non ECC source
DCT	Item	CATEGORY_TEXT	Financial Category text			CATEGORY_TEXT		Manually copy from Non ECC source, this will always be filled by users.
DCT	Item	YEAR	Fiscal Year	S/4 Hana		PERIOD		Convert year into yyyymmdd by adding 0101 to
DCT	Item	AMOUNT	Financial Amount	S/4 Hana	BPGA	AMOUNT		Manually copy from Non ECC source
DCT	WBS	PSPID	WBS Element	S/4 Hana	BPGA	PSPID
DCT	WBS	YEAR	Fiscal Year	S/4 Hana	BPGA	YEAR
DCT	WBS	WTJHR	Amount	S/4 Hana	BPGA	WTJHR

Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field
DCT	WBS	PSPID	WBS Element	S/4 Hana	BPGA	PSPID
DCT	WBS	YEAR	Fiscal Year	S/4 Hana	BPGA	YEAR
DCT	WBS	WTJHR	Amount	S/4 Hana	BPGA	WTJHR

Transformation Mapping

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
	Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool.	Syway Data Team

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Record Count	SyWay I2M Data Team to verify that the total number of relevant records in the Preload and Load Sheets.

Accuracy

Task

Action

Conversion Accuracy

SyWay I2M Data Team to verify that all fields below meet pass the checks:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Text Length Checks

Review Error Reports

Review and correct the errors. Achieve a zero-error record count as much as possible.

Business

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules.

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible
1	Propose use of standard load program RPM_DX_FINPLAN	SyWay I2M Data Team
2	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay I2M Data Team
3	Proceed with full load if steps 2 and 3 are validated	SyWay I2M Data Team
4	Validate few records loaded by accessing Portfolio Initiative App	SyWay I2M Data Team
5	Generate post load report if step 5 is validated	SyWay I2M Data Team
6	Execute program for transfer from PPM to PS	SyWay I2M Data Team
7	Validate few records loaded by accessing Portfolio Initiative App	SyWay I2M Data Team
8	Generate post load report if step 7 is validated	SyWay I2M Data Team

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Financial Category
2	Financial Group
3	Financial View
4	Period Conversion Factor
5	PS Budget Profile

Conversion Objects

Object #	Preceding Object Conversion Approach
1022	Portfolio Item

Error Handling

Error Type	Error Description	Action Taken
Invalid Data	Item number does not exist	Validate Transformation rules and DCT values
Invalid Data	Financial Category does not exist	Validate transformation rules
Invalid Data	Financial Group does not exist	Validate transformation rules
Invalid Data	Financial View does not exist	Validate transformation rules

Post-Load Validation

Project Team

Completeness

Task	Action
Verify Count Item	SyWay I2M Data Team to verify the record count created in target S/4 HANA by accessing post load reports or standard reports from S/4 HANA.
Verify Logs Item	Check if there is data that failed to load for PPM Item and perform the necessary actions (e.g. register as post load issue or attempt to the record again, etc.).
Verify Count WBS	SyWay I2M Data Team to verify the record count created in target S/4 HANA by accessing post load reports or standard reports from S/4 HANA.
Verify Logs WBS	Check if there is data that failed to load for PPM Item and perform the necessary actions (e.g. register as post load issue or attempt to the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	Verify that the approved funding were loaded to S/4 HANA correctly via table /rpm/fin_plan
Conversion Accuracy	Verify that the budget were loaded to S/4 HANA correctly via table BPGE

Business

Completeness

Task	Action
Verify Item Budget	Extract approved funding from PPM ???
Verify Level 1 WBS element Budget	Extract budget from PS report??

Accuracy

Task	Action
Verify Accuracy	Verify approved funding for PPM objects align with expected values
Verify Accuracy	Verify budget for level 1 WBS elements align with related PPM items.

Key Assumptions

Project Budget is in scope based on data design and any exception requested by business.

Change log

Version	Published	Changed By
CURRENT (v. 10)	Dec 08, 2025 14:08	KOHN-ext, Jacob
v. 18	Dec 08, 2025 14:05	KOHN-ext, Jacob
v. 17	Dec 08, 2025 14:02	KOHN-ext, Jacob
v. 16	Nov 20, 2025 09:40	KOHN-ext, Jacob
v. 15	Nov 19, 2025 14:18	KOHN-ext, Jacob
v. 14	Nov 19, 2025 14:13	KOHN-ext, Jacob
v. 13	Nov 19, 2025 13:08	KOHN-ext, Jacob
v. 12	Nov 19, 2025 08:01	KOHN-ext, Jacob
v. 11	Nov 17, 2025 16:00	KOHN-ext, Jacob
v. 10	Nov 17, 2025 13:59	KOHN-ext, Jacob

Go to Page History

Apr 01, 2026	Actor	Type	Activity	Version
Approved	KOHN-ext, Jacob	Comment	commented 1:51 pm WTJHR
		Comment	commented 1:51 pm remove
		Comment	commented 1:50 pm OBJNR
		Comment	commented 1:34 pm KBPP_EXTERN_UPDATE_CO
		Comment	commented 1:19 pm Update link
Mar 27, 2026
	KOHN-ext, Jacob	Comment	commented 8:51 am Add currency from item as a display field
Mar 24, 2026
	KOHN-ext, Jacob	Comment	commented 10:41 am Restrict items further to only multi phase items of type Z001 Industrial with Qualification Z002 Industrial w/out Qualification Z004 New Product Introduction Z005 Product & Process Improvement Z008 IT Full Lifecycle Project Z017 New Application Development
	KOHN-ext, Jacob	Comment	commented 10:37 am Phases displayed is restricted to Exclude phase SG01 from All item types
Jan 13, 2026
	KOHN-ext, Jacob	Comment	commented 11:31 am Add upload template
	KOHN-ext, Jacob	Comment	commented 11:20 am to be added in next revision Suggested The Function module is KBPP_EXTERN_UPDATE_CO
Dec 15, 2025
	TAN-ext, Charmaine	State	changed state to Approved at 1:52 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v19

Workflow history

Space shortcuts

Page tree

CNV-9033 Project Budget

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log