Versions Compared

Old Version 9

changes.mady.by.user KOHN-ext, Jacob

Saved on

compared with

New Version Current

changes.mady.by.user NADAR-ext, Parvati

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Peer Review

Owner

NADAR-ext, Parvati  

Stakeholders

KOHN-ext, Jacob STEFANESCU-ext, Aurelia UPADHYAY-ext, Anjali AGGARWAL-ext, Vikhyat 

Purpose

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

Portfolio Initiatives represents a Program of work in EPPM. A Portfolio Initiative is group of related projects (Portfolio Items) potentially belonging to different Portfolio Buckets for reporting purposes.


Conversion Scope

The scope of this document covers the approach for uploading the  Portfolio Initiatives into S/4HANA following the Portfolio Initiatives Master Data Design Standard 

This is a completely new object for Syensqo with the data being sourced using DCT (Data Collection Template).

No action is required for the Initiative decision points from a data migration perspective.

List of source systems and approximate number of records

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

DCT

All Records


S/4HANA?


Replicate Initiative to Other Instances: Migration load to be done to ROW instance with replication of Global Initiatives to other S/4 Hana instances (CUI and China) done by batch job as per the business process.  Local initiatives will not be replicated in other instances.

To be included in cut-over strategy document. 

In the Global The Initiative is created. This means the Initiative includes PPM items (Projects) from other instances. then the Initiative is replicated in CUI and China instance. This is to allow the assignment of China and CUI specific PPM items to the  Global Initiative. The Initiative reporting is performed in the SAC reporting tool.reporting is performed in the SAC reporting tool.


Additional Information

Multi-language Requirement

Initiative  Global Initiative names and texts will be maintained in English Language only.

Document Management

 

A Local initiative in China, will be maintained in the Chinese language.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable


Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
INM_INITIATIVEGUIDINM_TV_GUIDUnique IdentifierRAW16System generated
INM_INITIATIVEITEM_GUIDRPM_TV_GUIDGuid for application objectsRAW16System generated
INM_INITIATIVEDPR_GUID

DPR_TV_GUID

Application Object GUIDRAW16System generated
INM_INITIATIVEEXTERNAL_IDINM_TV_EXTIDInitiative IDCHAR24Mandatory, System generated
CRM_JESTSTAT

CRM_J_STATUS

System statusCHAR5Mandatory
/RPM/ITEM_DPORTFOLIO_GUID/RPM/TV_GUIDGuid for application objectsRAW16System generated
/RPM/ITEM_DPORTFOLIOPARENT_IDGUID

/RPM/TV_

EXTID

GUID

Portfolio Parent Bucket IDCHARRAW2416Mandatory
/RPM/ITEM_DBUCKET_ID/RPM/TV_EXTIDParent Bucket IDCHAR24MandatoryINM_INITIATIVEITEM_TYPE/RPM/TV_ITEM_IDInitiative TypeCHAR15Mandatory
CGPL_TEXTNAMECGPL_TEXT1Initiative NameCHAR40Mandatory
STXLCLUSTDSTXLDUMMY2Initiative DescriptionLRAW7902Conditional
RPM_OBJ_LINKOBJECT_KEYRPM_TV_OBL_OBJECT_KEYKey of the linked objectSTRING0System generated
/RPM/ITEM_DCurrency keyRPM_TV_CURRENCYCurrency keyCUKY5Mandatory
/RPM/ITEM_DPLANNED_STARTRPM_TV_PLAN_STARTPlanned StartDATS8Optional
/RPM/ITEM_DPLANNED_FINISHRPM_TV_PLAN_FINISHPlanned FinishDATS8Optional
/RPM/ITEM_DCAPSYPROG_PERIODTYPE/RPM/TV_CAP_PERIOD_TYPEMGR
Program ManagerCapacity Period BreakdownNUMC28Mandatory
/RPM/ITEM_DUNITRPM_TV_UNITUnitCHAR3Mandatory
/RPM/ITEM_DPERIODTYPE/RPM/TV_PERIOD_TYPEFinancial Period BreakdownNUMC2Mandatory
ZX002STEXTProgram Manager Position NameSTEXT40System generated
STXLCLUSTDSTXLDUMMY2Next StepsLRAW7902Conditional
STXLCLUSTDSTXLDUMMY2StatusLRAW7902Conditional/RPM/ITEM_DZX001HROBJIDProgram ManagerNUMC8Mandatory
/RPM/ITEM_DZX002SYIMPER_CDSTEXTProgram Manager Position NameSTEXT40System generated

Data Cleansing

Not applicable, as data object Portfolio initiatives does not exist in legacy system and will be collected specifically for data migration.

IDCriticalityError Message/Report DescriptionRuleOutputSource System

Conversion Process

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

Image Removed

Data Privacy and Sensitivity

Not Applicable.

 Imperative CodeNUMC4Conditional

   Relationship between INM_INITIATIVE and CGPL_TEXT is the field INM_INITIATIVE-GUID.

   STXL long text table, to read data from CLUSTD use FM READ_TEXT with object = CGPL_TEXT

   Relationship between INM_INITIATIVE and CRM_JEST is the field INM_INITIATIVE-GUID. Status number from CRM_JEST table to TJ02 table provides description for the status

Data Cleansing

Not applicable, as data object Portfolio initiatives does not exist in legacy system and will be collected specifically for data migration.

IDCriticalityError Message/Report DescriptionRuleOutputSource System








Conversion Process

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

Image Added

Data Privacy and Sensitivity

Not Applicable.

Extraction

Extract data from a source into Syniti Migrate. 

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 DescriptionTeam Responsible
1Ensure DCT is collected for InitiativesData Team
2Perform preliminary completeness checkData 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

Not Applicable
Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set

None


Data Collection Template (DCT)

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

DCT Rules

Field NameField DescriptionRule
EXTERNAL_IDInitiative ID

Unique Identifier for the Initiative, system generated number. (IN-999999)


STATSystem status

Represent the system status of an initiative.  Default Status is set upon creation of PPM Initiative. It can be modified by the Program Manager at any point during the Initiative's lifecycle.

Dropdown to TJ02T (language = EN) table, display with text

Initial status = I1700 - (CRTE -Created), Status released  - I1701 - (REL -Released), Status Locked - I1705 - (LCKD - Locked)

Note: First-time initiatives are always loaded with a status=I1700 CRTE

It is a Required Field 

PORTFOLIO_IDPortfolio IDUnique  Identifier for the Portfolio, Defaulted to "Syensqo"
BUCKET_IDParent Bucket ID

Unique Identifier for the initiative's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assigned.

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template

ITEM_TYPEInitiative Type

Initiative types define the structure and behavior of the portfolio initiative. In Syway there will be only 2 Initiative types.
Global Initiative will be in ROW and will include Items from other Instance (China) will be replicated to all instances. 
Local Initiative will include items from only 1 instances.

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template

Dropdown from config table: /RPM/ITEM_TYPE, where Master_ITEM = X with text from /RPM/ITEM_TYPE_T restrict to Z*

TEXT1Initiative Name

Name of the Initiative.

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template

CLUSTDInitiative Description Conditional for initiatives long text where additional program information is required.
PLANNED_STARTPlanned Start

Planned start of Initiative

Conditional in format (YYYYMMDD)

PLANNED_FINISHPlanned Finish

Planned Finish of Initiative

Conditional in format (YYYYMMDD)

SYPROG_MGRProgram Manager

This field represent Position of the Program Manager and is mandatory for all Initiatives to determine the responsibility

It is a Required Field: Preload Check to be done to confirm that this is field in the Data Collection Template

RPM_OBJ_LINKKey of the linked object

Relationship of Portfolio Items to a given Portfolio Initiative/program. 

Preload Check to be done to confirm that this is field in the Data Collection Template

NEXT_STEPSNext Steps

Long-text description, this field is used to provide a textual information on the next steps for Initiatives

This is a Conditional field..

STATUSStatus

Long-text description to describe the status of the Initiatives

This is a Conditional field.

SYIMPER_CDImperative Code

The Imperative attribute within the PPM Initiative is used to define and classify the associated Strategic Mission/Objective.

This is a Conditional field. 

Dropdown with description required.

Table: /SYQ/T_IMPERATIVE 

Field: IMPER_CD - Imperative Code, IMPER_DESC - Imperative Description, ACTIVE-ACTIVE

Object Link - Item to Initiative

Use FM /RPM/CREATE_OBJ_LINK or /RPM/OBJECT_LINK_MODIFY to create the object link between the initiative and the item(s).

Step: 

a. Upload item as per CNV-1022

b. Upload Initiative

c. Object link, item to initiative

Extraction Dependencies

No Dependencies for Extract

Item #Step DescriptionTeam Responsible

None


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:

  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
  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 DescriptionTeam Responsible

1

Obtain DCT Sign-off from Business

Data Team

2

Execute and Load and perform Transformation 

Data Team

3

Monitor the transformation progress and ensure performance and completion is within allowed timeframe

Data team

4

Review and Validate Error and Preload Reports

Data Team

5

Generate data load count.

Data team

6

Generate Load Files

Data Team

7

Log errors as defects, if any and address resolutions. Close defects.Data team
8Re-transform and re-validate the Pre-load reports if necessary.Data team
9Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.Business
10Analyse and resolve any pre-load defects logged by business.Data team
11Repeat steps 7 to 10 if necessaryData team
12Proceed to pre-load validationsData team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCT


S/4 HanaINM_INITIATIVEEXTERNAL_IDInitiative IDSystem generated
2



S/4 HanaINM_INITIATIVESTATSystem status

Initial status = I1700 - (CRTE -Created)

Status released  - I1701 - (REL -Released)

Status Locked -

I1705 - (LCKD - Locked)

Note: First-time initiatives are always loaded with a status=I1700 CRTE

3DCT
PORTFOLIO_IDPortfolio IDS/4 Hana/RPM/ITEM_DPORTFOLIO_IDPortfolio IDCopy from source to target system
4DCT
BUCKET IDParent Bucket IDS/4 Hana/RPM/ITEM_DBUCKET_IDParent Bucket IDCopy from source to target system
5DCT

Extraction

Extract data from a source into . 

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 DescriptionTeam Responsible1Ensure DCT is collected for BucketsData Team2Perform preliminary completeness checkData Team3

Raise issues as defects if Req # 1 to 2 are not met

Data Team4

Repeat Req # 1 to 3 if required

Data Team

Selection Screen

Not Applicable
Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/setNone

Data Collection Template (DCT)

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

DCT Rules

Field NameField DescriptionRuleEXTERNAL_IDInitiative IDUnique Identifier for the Initiative, system generated number. (IN-999999)STATSystem statusRepresent the system status of an initiative.  Default Status is set upon creation of PPM Initiative. It can be modified by the Program Manager at any point during the Initiative's lifecycle.PORTFOLIO_IDPortfolio IDLocked and Defaulted "Syensqo"BUCKET_IDParent Bucket IDUnique Identifier for the initiative's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assignedITEM_TYPEInitiative TypeInitiative types define the structure and behavior of the portfolio initiative. In Syway there will be only one Initiative type.TEXT1Initiative NameName of the Initiative.CLUSTDInitiative DescriptionConditional for initiatives where additional program information is requiredPLANNED_STARTPlanned Start

Planned start of Initiative

Optional Format (YYYYMMDD)

PLANNED_FINISHPlanned Finish

Planned Finish of Initiative

Optional Format (YYYYMMDD)

ZX001Program ManagerThis field represent Position of the Program Manager and is mandatory for all Initiatives to determine the responsibility

Object Link - Item to Initiative

Extraction Dependencies

No Dependencies for Extract

Item #Step DescriptionTeam ResponsibleNone

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:

  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
  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 DescriptionTeam Responsible

1

Obtain DCT Sign-off from Business

Data Team

2

Execute and Load and perform Transformation 

Data Team

3

Monitor the transformation progress and ensure performance and completion is within allowed timeframe

Data team

4

Review and Validate Error and Preload Reports

Data Team

5

Generate data load count.

Data team

6

Generate Load Files

Data Team

7

Log errors as defects, if any and address resolutions. Close defects.Data team8Re-transform and re-validate the Pre-load reports if necessary.Data team9Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.Business10Analyse and resolve any pre-load defects logged by business.Data team11Repeat steps 7 to 10 if necessaryData team12Proceed to pre-load validationsData team

Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic1DCTEXTERNAL_IDInitiative ID



S/4 HanaINM_INITIATIVE
EXTERNAL
ITEM_
ID
TYPEInitiative
ID
TypeCopy from source to target system
2
6DCT
STAT

NAME
System status
Initiative NameS/4 Hana
INM
CGPL_
INITIATIVE
TEXT
STAT
NAME
System status
Initiative NameCopy from source to target system
3
7DCT
PORTFOLIO_IDPortfolio ID



S/4 Hana
INM_INITIATIVEPORTFOLIO_IDPortfolio IDCopy from source to target system4DCTBUCKET IDParent Bucket ID
/RPM/ITEM_DCURRENCYCurrency keyDefault "EUR"
8DCT
PLANNED_STARTPlanned StartS/4 Hana
INM_INITIATIVEBUCKET_ID
/RPM/ITEM_DPLANNED_STARTPlanned Start
Parent Bucket ID
Copy from source to target system
5
9DCT
PLANNED_FINISHPlanned FinishS/4 Hana
INM_INITIATIVEITEM_TYPEInitiative TypeDefault "Z001"
/RPM/ITEM_DPLANNED_FINISHPlanned FinishCopy from source to target system
10
6DCTNAMEInitiative Name




S/4 Hana
INM_INITIATIVENAMEInitiative NameCopy from source to target system7DCT8DCTPLANNED_STARTPlanned Start
/RPM/ITEM_DCAP_PERIODTYPECapacity Period BreakdownDefault to "12"(Annually)
11



S/4 Hana
INM_INITIATIVECURRENCYCurrency keyDefault "EUR"
/RPM/ITEM_DUNITUnitDefault to "TAG"(Day)
12



S/4 Hana
INM_INITIATIVEPLANNED_STARTPlanned StartCopy from source to target system9DCTPLANNED_FINISHPlanned Finish
/RPM/ITEM_DPERIODTYPEFinancial Period BreakdownDefault to "12"(Annually)
13DCT
SYPROG_MGRProgram ManagerS/4 Hana
INM_INITIATIVEPLANNED_FINISHPlanned Finish
/RPM/ITEM_DSYPROG_MGRProgram ManagerCopy from source to target system
10
14



S/4 Hana
INM_INITIATIVECAP_PERIODTYPECapacity Period BreakdownDefault to "12"(Annually)11S/4 HanaINM_INITIATIVEUNITUnitDefault to "TAG"(Day)12
/RPM/ITEM_DZX002Program Manager Position NameValue Mapping: Position Name from Position
Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001
17DCT
CLUSTDInitiative DescriptionS/4 Hana
INM_INITIATIVE
STXL
PERIODTYPEFinancial Period BreakdownDefault to "12"(Annually)13DCTZX001
CLUSTDInitiative DescriptionCopy from source to target system
18DCT
NEXT_STEPSNext Steps
Program Manager
S/4 Hana
INM
STXLNEXT_
INITIATIVE
STEPS
ZX001
Next Steps
Program Manager
Copy from source to target system
14
19DCT
STATUSStatusS/4 Hana
INM_INITIATIVE
STXL
ZX002Program Manager Position NameValue Mapping: Position Name from Position
Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001
STATUSStatusCopy from source to target system
20DCT
SYIMPER_CDImperative Code
17DCTLTEXTInitiative Description
S/4 Hana
INM_INITIATIVELTEXT
/RPM/ITEM_DSYIMPER_CDImperative Code
Initiative Description
Copy from source to target system

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

Standard Initiative upload template

Transformation Mapping


Mapping Table NameMapping Table Description

HRP1000

Infotype 1000 DB Table

Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Position table HRP1000 has been maintained (HRP1000)
2Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool

Data Team 


Pre-Load Validation

Project Team

Completeness

TaskAction

Verify Record Count

SyWay I2M Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.


Accuracy

TaskAction

Conversion Accuracy

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

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks

Review Error Reports

Review and correct the errors.  Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source (DCT) data.

Business

Completeness

TaskAction

Verify Record Count

Business Data Owner/s to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

TaskAction

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 (and signed-off DCT data).


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
  3. Migration load to be done to ROW instance with replication of Global Initiatives to other S/4 Hana instances done by batch job as per business process.   To be included in cut-over strategy document. 
  4. Object link initiative to item.

Load Run Sheet

Item #Step DescriptionTeam Responsible

1

Go to RPM_DX_INITIATIVE

SyWay I2M Data Team

2

Load 3 records for < > to validate if data is loaded successfully without errors

SyWay I2M Data Team

3

Load 3 records for < > to validate if data is loaded successfully without errors

SyWay I2M Data Team

4

Proceed with full load if steps 2 and 3 are validated

SyWay I2M Data Team

5

Validate few records loaded by accessing Portfolio Initiative App

SyWay I2M Data Team

6

Generate post load report if step 5 is validated

SyWay I2M Data Team


Load Phase and Dependencies


Configuration


Item #Configuration Item
1Initiative Type 
2Override Default Global Settings  (Master Switches  0002   Switched off - Portfolio & Bucket will have manual ID)
3Define Currency Units
4Define Period Types
5Define Capacity Units
6Configure Fields for Mass Import
7Custom table /SYQ/T_IMPERATIVE

Conversion Objects

Object #Preceding Object Conversion Approach
1113Portfolio Bucket Hierarchy
1022Portfolio Item

Error Handling


Invalid Data

Invalid Portfolio

Validate DCT default content

Invalid Data

Invalid Bucket ID

Validate DCT default content

Invalid date formatInvalid datesValidate DCT default content
Invalid DataInvalid Initiative typeValidate DCT default content


Post-Load Validation

Project Team

Completeness

TaskAction

Verify Count

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

Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

Accuracy

TaskAction
Conversion AccuracyVerify that the Portfolio Initiatives in target S/4 HANA were loaded correctly via Initiative Dashboard App display and table V_INM_INIT_DB in S/4 HANA

Business

Completeness

TaskAction

Verify Count

Extract Initiative details from Initiative dashboard App in S/4 HANA

Accuracy

TaskAction
Verify AccuracyExtract Initiative details from Initiative dashboard App in S/4 HANA


Key Assumptions

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

Jira Task:



See also

Change log

Change History
limit10