Status
Owner	KOHN-ext, Jacob
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 create <Data Object> in S/4 HANA.

Summarise how the data is currently utilized and set up in the legacy system/s and how object is intended to be represented in S/4, and any other relevant information

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.

The data from legacy system includes:

1. Level 1 WBS element budgets for open Projects
2. Level 1 WBS element budgets for closed Projects with postings in the agreed timeframe.
3. Relevancy Criteria 2
4. Relevancy Criteria n

The data from legacy system excludes:

1. Exclusion Criteria 1
2. Exclusion Criteria 2
3. Exclusion Criteria n

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)

Additional Information

Multi-language Requirement

Not Applicable

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
BPJA	LEDNR	BP_LEDNR	Ledger	CHAR	4	System Generated
BPJA	OBJNR	BP_OBJEKT	Object number	CHAR	22	Mandatory
BPJA	TRGKZ	BP_TRGKZ	Object indicator	CHAR	1	System Generated
BPJA	WRTTP	CO_WRTTP	Value Type	CHAR	2	System Generated
BPJA	GJAHR	GJAHR	Fiscal Year	NUMC	4	Mandatory
BPJA	VERSN	BP_VERSION	Version	CHAR	3	Mandatory
BPJA	VORGA	BP_VORGANG	Budget Type	CHAR	4	Mandatory
BPJA	TWAER	TWAER	Transaction Currency	CUKY	5	Mandatory
BPJA	WTJHR	BP_WJT	Transaction Currency Annual value	CURR	21	Mandatory
BPJA	WLJHR	BP_WJL	Ledger Value Currency Annual value	CURR	21	Mandatory
BPJA	WTJHV	BP_WJTV	Transaction Currency Annual distributed value	CURR	21	System Generated
?BPJA	WLJHV	BP_WJLV	Ledger Value Currency Distributed annual value	CURR	21	System Generated
/RPM/FIN_PLAN	EXTERNAL_ID	/RPM/TV_EXTID	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 (This is used in upload)
/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 (This is used in upload)
/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

Data Cleansing

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

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

Conversion Process

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Is there privacy and sensitivity concerns for project budgets?

Extraction

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

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

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

Data Collection Template (DCT)

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

<Object> DCT Rules

Field Name	Field Description	Rule
Item ID	PPM item to which budget is to be assigned	Budget will

Extraction Dependencies

List the steps that need to occur before extraction can commence

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:

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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. 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

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

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

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

Post-Load Validation

Project Team

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

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

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log