The purpose of this document is to define the conversion approach to create Portfolio Item in S/4 HANA.
PPM Item: A PPM Item is a proxy of project in PPM which is used to plan, evaluate, and monitor Spend (Capex and Opex) within Syensqo’s portfolio. In SyWay, PPM Items are created under the lowest level bucket.
The scope of this document covers the approach for converting applicable active Projects to Portfolio Items from Legacy Source Systems into S/4HANA following the Portfolio Item Master Data Design Standard.
This is a completely new object for Syensqo, with the data being sourced using a DCT (Data Collection Template).
The DCT will contain transformed data from source system for Capital and Budget Managed Operating PS Project Definitions in scope for migration, extensive enrichment will be necessary to produce properly formatted data load sheets for S/4 HANA.
Relevancy Criteria
The data from legacy system includes:
The data from legacy system excludes
Also exclude, Operating Expense projects without budget, including the following proposed project profile in S/4:
a. Open Project for Statistical Expenses - replaced by project definitions with profile ZPS0003 - Statistical Expense.
b. Open Recharge Projects - replaced by project definitions with profile ZPS0004 - Intercompany Recharges.
c. Open Project definitions with profile ZPS0005 - Provisional Projects.
The migration for these excluded Operating Expense project without budget is dealt with in CNV-1024 Project Definition
Additionally, there may be Items included in the DCT which does not have any existing Project Systems objects. as well as
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 | Relevant PS Projects | TBD | S/4 Hana | TBD |
| WP2 | Relevant PS Projects | TBD | S/4 Hana | TBD |
| DCT | S/4 Hana | TBD |
Item is to be migrated into a single instance of S/4 Hana only with the determination of which instance dependent on the company code maintained in the area field of the item. Area will be maintained based upon the converted Company Code of the legacy Project Definition.
For items the following scenarios with the PS Project definition with WBS element hierarchy is automatically created on loading of the PPM item.
Capital project is a project that has any WBS elements with a Investment Profile. PRPS-IZWEK
Budgeted Opex is any other project that has any WBS elements with budget. WBS has entry in BPGE for value type 41
IT Project is a project that has a WBS element one of the following criteria
R&I Project is a project meeting one of the following criteria,
Industrial projects
Facilities Projects
Table JEST:
Field "Object number" = Key in the object numbers of Project
Field "Status Inactive" = blank,
Field Status = I0046 (Closed)
If status Closed is active further check for postings in the agreed timeframe)
Get All WBS elements
Table PRPS
Field PSPHI For closed projects numbers, Result WBS numbers for closed projects.
Check for postings
Table RPSCO / COSP:
Field "Object number" = Key in the object numbers of WBS
Field "Fiscal Year" = the agreed timeframe.
Result = Object numbers that have cost in agreed timeframe.
If count is greater than 0 then the project needs to be migrated.
Additional Information
All item names and texts will be maintained in a single language as entered, with no requirement for translation.
Not applicable
Not applicable
Not applicable
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. If standard upload is used some system generated fields must be maintained in the transformation.
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| /RPM/ITEM_D | EXTERNAL_ID | /RPM/TV_EXTID | ID | CHAR | 24 | System Generated |
| /RPM/ITEM_D | PARENT_ID | /RPM/TV_EXTID | Parent Bucket ID | CHAR | 24 | Mandatory |
| /RPM/ITEM_D | PORTFOLIO_ID | /RPM/TV_EXTID | Portfolio ID | CHAR | 24 | Mandatory |
| /RPM/ITEM_D | ITEM_TYPE | /RPM/TV_ITEM_ID | Type | CHAR | 15 | Mandatory |
| CGPL_TEXT | TEXT1 | CGPL_TEXT1 | Name | CHAR | 40 | Mandatory |
| STXL | CLUSTD (LTEXT for identification in Transformation)) | CLUSTD | Item Description | CLUSTD | Conditional | |
| /RPM/ITEM_D | STATUS | /RPM/TV_STATUS_COMMON | Item Status | CHAR | 5 | Mandatory |
| /RPM/ITEM_D | PLANNED_START | RPM_TV_PLAN_START | Planned Start | DATS | 8 | Mandatory |
| /RPM/ITEM_D | PLANNED_FINISH | RPM_TV_PLAN_FINISH | Planned Finish | DATS | 8 | Mandatory |
| /RPM/ITEM_D | CATEGORY | RPM_PROJECT_CATEGORY | Investment Reason | NUMC | 4 | Mandatory |
| /RPM/ITEM_D | SUBCATEGORY | RPM_PROJ_SUBCATEGORY | Sub Business Driver | NUMC | 4 | Mandatory |
| /RPM/ITEM_D | TTYPE | RPM_PROJECTTYPE | Main Business Driver | NUMC | 4 | Mandatory |
| /RPM/ITEM_D | PTYPE | RPM_PROJECT_TECHTYPE | Investment Category | NUMC | 4 | Mandatory |
| /RPM/ITEM_D | GEOGRAPHY | RPM_TV_PROJECT_GEOGRAPHY | Company Code | CHAR | 4 | Mandatory |
| /RPM/ITEM_D | CURRENCY | RPM_TV_CURRENCY | CURRENCY | CUKY | 5 | System Generated |
| /RPM/ITEM_D | UNIT | RPM_TV_UNIT | Unit | UNIT | 3 | System Generated |
| /RPM/ITEM_D | CAP_PERIODTYPE | /RPM/TV_CAP_PERIOD_TYPE | Capacity Period Breakdown | NUMC | 2 | System Generated |
| /RPM/ITEM_D | PERIODTYPE | /RPM/TV_PERIOD_TYPE | Fin Period Breakdown | NUMC | 2 | System Generated |
| /RPM/ITEM_D | INITIATIVE_ID | INM_TV_EXTID | INITIATIVE ID | CHAR | 24 | Conditional |
| /RPM/ITEM_D | ZXX2 | Spending Range | NUMC | 2 | Mandatory | |
| /RPM/ITEM_D | ZXX3 | GBU Market Hierarchy | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX4 | End User Market | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX5 | Corporate Hierarchy | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX6 | Cluster | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX7 | Product Hierarchy | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX10 | Export Control | NUMC | 2 | Mandatory | |
| STXL | CLUSTD (Justification for identification in Transformation) | Justification (Export Control) | CLUST | Mandatory | ||
| /RPM/ITEM_D | ZXX11 | Need-to-know | CHAR | 1 | Mandatory | |
| /RPM/ITEM_D | ZXX14 | HROBJID | Project Owner | NUMC | 8 | Mandatory |
| /RPM/ITEM_D | ZXX15 | STEXT | Project Owner | STEXT | 40 | Mandatory |
| /RPM/ITEM_D | ZXX16 | HROBJID | Project Financial Controller | NUMC | 8 | Mandatory |
| /RPM/ITEM_D | ZXX17 | STEXT | Project Financial Controller | STEXT | 40 | Mandatory |
| /RPM/ITEM_D | ZXX37 | Scoring Methodology | System Generated | |||
| /RPM/ITEM_D | ZXX18 | Starting Risk Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX19 | Starting Risk Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX20 | Residual Risk Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX21 | Residual Risk Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX22 | Regulatory Mandated Magnitude | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX23 | Regulatory Mandated Likelihood | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX24 | Regulatory Mandated Time Horizon (to start project) | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX25 | Capitalization Date | DATS | 8 | Conditional | |
| /RPM/ITEM_D | ZXX26 | PRCTR | Profit Centre | CHAR | 10 | Mandatory |
| /RPM/ITEM_D | ZXX27 | WeGo ID | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX29 | Budget Provision | CHAR | 10 | Conditional | |
| /RPM/ITEM_D | ZXX30 | Opportunity ID | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX31 | Archetype | NUMC | 2 | Conditional | |
| /RPM/ITEM_D | ZXX32 | Must Do Justification | NUMC | 2 | Mandatory | |
| /RPM/ITEM_D | ZXX33 | PS_PSPID | Legacy Project ID | CHAR | 24 | Conditional |
| /RPM/ITEM_D | ZXX34 | WERKS_D | Plant | CHAR | 4 | Mandatory |
| /RPM/ITEM_D | ZXX35 | Idea ID | CHAR | 40 | Conditional | |
| /RPM/ITEM_D | ZXX36 | Subsidy | CHAR | 1 | Conditional | |
| STXL | CLUSTD (Sub_Relevance for identification in Transformation) | CLUSTD | Subsidy Relevance | CLUSTD | Conditional | |
| STXL | CLUSTD (Key_Assump for identification in Transformation) | CLUSTD | Key Assumptions | CLUSTD | Conditional | |
| STXL | CLUSTD (Variation for identification in Transformation)) | CLUSTD | Variations | CLUSTD | Conditional | |
| STXL | CLUSTD (Other for identification in Transformation)) | CLUSTD | Other Information | CLUSTD | Conditional |
Decision Point Table
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| /RPM/DECISION | DECISION_ID | /RPM/TV_EXTID | ID | CHAR | 24 | Mandatory |
| /RPM/DECISION | ITEM_ID | /RPM/TV_EXTID | ITEM_ID | CHAR | 24 | Mandatory |
| CGPL_TEXT | TEXT1 | NAME | CHAR | 40 | Mandatory | |
| /RPM/DECISION | STATUS | /RPM/TV_STATUS_COMMON | STATUS | CHAR | 5 | Conditional |
| /RPM/DECISION | PLAN_START | RPM_TV_PLAN_START | Planned Start Date | DATS | 8 | Conditional |
| /RPM/DECISION | PLAN_FINISH | RPM_TV_PLAN_FINISH | Planned Finish Date | DATS | 8 | Conditional |
| /RPM/DECISION | ACTUAL_START | RPM_TV_ACTUAL_START | Actual Start Date | DATS | 8 | System Generated |
| /RPM/DECISION | ACTUAL_FINISH | RPM_TV_ACTUAL_FINISH | Actual Finish Date | DATS | 8 | System Generated |
| /RPM/DECISION | ZXXX01 | Variation Reference | Conditional |
Item Authorizations (Required only where Need-to-know = yes)
| Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
|---|---|---|---|---|---|---|
| ACO_USER | ITEM_ID | /RPM/TV_EXTID | ID | CHAR | 24 | Conditional |
| ACO_USER | ACTIVITY | ACO_ACTVT | Activity | CHAR | 10 | Conditional |
| ACO_USER | USER | ACO_USER_ID | User | CHAR | 12 | Conditional |
Relationship between /RPM/ITEM_D and CGPL_TEXT is the field /RPM/ITEM_D-GUID one to one.
Relationship between /RPM/ITEM_D and /RPM/DECISION is the field /RPM/ITEM_D-GUID one item to many decision points.
Relationship between /RPM/ITEM_D and ACO_USER is the field /RPM/ITEM_D-GUID one item to optional many users.
| ID | Criticality | Error Message/Report Description | Rule | Output | Source System |
|---|
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

Extract data from a source into Syniti Migrate. There are 2 possibilities:
The agreed Relevancy criteria is applied to the extracted records as reference point to identify the records that are applicable for the data construction in the DCT.
| Req # | Requirement Description | Team Responsible |
|---|---|---|
| 1 | Extract data from source system based on relevancy rule | SyWay Data Team |
| Selection Ref Screen | Parameter Name | Selection Type | Requirement | Value to be entered/set |
|---|---|---|---|---|
| Not Applicable |
Target Ready Data Collection Template will be created for Portfolio Item data with exception of some fields which require transformation as mentioned in the transformation rule.
Note: All rules specified below should be documented as a tooltip in the DC Page.
Portfolio Item DCT Rules
| Field Name | Field Description | Rule |
|---|---|---|
| SNRO | Item Serial Number | This field is display only and is filled with a sequential number when user adds a item record |
| PARENT_ID | Parent Bucket ID | Unique Identifier for the Item's parent Bucket. In SyWay it is the ID of the L3 bucket where item is assigned. Dropdown list from the Buckets maintained in CNV_1113 Portfolio Bucket Hierarchy It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| ITEM_TYPE | Type | Item types define the structure and behavior of the portfolio item. In Syway item types will be based on the function and number of phases of the project. Refer configuration table field /RPM/ITEM_TYPE- ITEM_TYPE for allowed values. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| TEXT1 | Name | Short description of the PPM Item It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| LTEXT | Item Description | Long Description, this field is used to provide a concise description of the PPM Item. Entered where information is available |
| STATUS | Item Status | Represents status of an item Refer configuration table field /RPM/ITEM_STATUS- STATUS against ITEM_TYPE for the allowed values of the selected Item Type. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| PLANNED_START | Planned Start | Baseline start date of the item/ project used for planning within the portfolio/ bucket. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| PLANNED_FINNISH | Planned Finish | Expected Delivery Date. Baseline finish date of the item/ project used for planning within the portfolio/ bucket. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| CATEGORY | Investment Reason | In Syway, Investment Reason is level-3 category of investment. Refer configuration table field RPM_PROJ_CAT- CATEGORY for the allowed values. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| GEOGRAPHY | Company Code | In SyWay, this field Represents Company code; the legal entity in which the Syway Project will be executed. Refer configuration table field V_DPR_AREA- AREA for the allowed values. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| INITIATIVE_ID | INITIATIVE ID | Internal ID of Initiative where Item must be linked to Initiative Dropdown list from the Initiatives maintained in CNV_1023 Portfolio Initiatives This is an optional field |
| ZXX2 | Spending Range | The Capex spending range used for reporting the project size. Dropdown values from /SYQ/T_SPND_RNGE It is a Required Field: Preload Check to be done to confirm that this field is in filled the Data Collection Template |
| ZXX3 | GBU Market Hierarchy | GBU Market Hierarchy is a GBU-led Market segmentation, applied to both customer and product combination. To be selected only for applicable PPM Items. Dropdown values from /SYQ/T_BU_DMN Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX4 | End User Market | Node of GBU Market Hierarchy used for reporting To be selected only for applicable PPM Items Dropdown values from /SYQ/T_END_USR_MKT Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX5 | Corporate Hierarchy | Corporate-led Market segmentation used for reporting To be selected only for applicable PPM Items. Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX6 | Cluster | In SyWay, Used to group items together for reporting where a budget allocation is made at an aggregated level, and actuals are collected against individual related items. |
| ZXX7 | Product Hierarchy | Reference to the product hierarchy node ( at any level) required for reporting. It is a required field when Item Type is related to either IS or R&I project. Refer table HRRP_NODE- NODEVALUE where HRRP_NODE- NODETYPE = N and HRYTYPE = MD01" Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| ZXX10 | Export Control | To identify if the project is applicable for regulatory governance. This is a dropdown field from /SYQ/T_EXPORT_CNTL This is a required field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| Justification | Justification (Export Control) | This field captures the justification for the relevance of export control (long text field). This is a required field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| ZXX11 | Need-to-know | This field indicates confidential projects. Access will be restricted if selection is "Yes" Options are Yes/No It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| ZXX14 | Project Owner | This field stores Position of the Project Owner for the PPM Item and is mandatory for all SyWay business functions. Refer configuration table field TCJ04-PS_VERNR for field validation. Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| ZXX16 | Project Financial Controller | This field represent Position of the Project Financial Controller for a project and is mandatory for all SyWay business functions. Refer configuration table field TCJ05-ASTNR for field validation. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| ZXX18 | Starting Risk Magnitude | For the Risk managed project - this field define the risk magnitude at the start of project. This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field /SYQ/T_RISK_MAGNITUDE Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| ZXX19 | Starting Risk Likelihood | For the Risk managed project - this field define the risk likelihood at the start of project. This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field /SYQ/T_RISK_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX20 | Residual Risk Magnitude | For the Risk managed ongoing approved project - this field defines remaining risk magnitude. This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field from /SYQ/T_RISK_MAGNITUDE Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX21 | Residual Risk Likelihood | For the Risk managed ongoing approved project - this field defines remaining risk likelihood. This field is required to be maintained if Scoring Methodology = Risk This is a dropdown field from /SYQ/T_RISK_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX22 | Regulatory Mandated Magnitude | Impact of regulatory compliance on project delivery. This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_MAGNITUDE Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX23 | Regulatory Mandated Likelihood | Probability of impact due to regulatory compliance. This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_LKLHD Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX24 | Regulatory Mandated Time Horizon (to start project) | Regulatory defined deadline by which a project must commence. This field is required to be maintained if Scoring Methodology = Regulatory This is a dropdown field from /SYQ/T_REG_TIME_HORIZON Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX25 | Capitalization Date | Stores the capitalization date for the purpose of "Depreciation forecast", This date is mandatory for the Capital Projects Item types. Item Types are Z001,Z002, Z003, Z008, Z009, Z011 Preload Check to be done to confirm that this field is filled the Data Collection Template when required |
| ZXX26 | Profit Center | Profit Centre represents the GBU/Plant where the project is performed., Profit centre on PPM item will be validated with the PC on the Parent Bucket to check they belong to the same group. This will ensure PPM items are created under correct GBU bucket. Refer master table field CEPC-PRCTR for Profit center list. the Data Collection Template, It is a Required Field: Preload Check to be done to confirm that this field is filled, and is aligned with the PC on the Parent Bucket, first character of the Profit centers must match |
| ZXX27 | WeGo ID | This stores the WEGO project ID for reporting for R&I related projects in WEGO. This is an optional field for migration |
| ZXX29 | Budget Provision | Used to group those PPM Items where the budget is drawn from the Budget provision Item. Selection of existing Item Serial Numbers where the item type is Budget Provision Field content to be verified in Preload check, field can contain only Item numbers of item type Budget Provision. |
| ZXX30 | Opportunity ID | If IS or R&I PPM item is created with reference to a CRM Opportunity, the corresponding Opportunity ID will be entered. This is an optional field. |
| ZXX31 | Archetype | This field represent Archetype of the R&I PPM item. This is a dropdown field from /SYQ/T_ARCHETYPE Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| ZXX32 | Must Do Justification | This field provides input to the ranking of items in the prioritization dashboard. and is relevant across all PPM item types. |
| ZXX33 | Legacy Project ID | Legacy Project ID refers to the project identifier used in the previous SAP system before migration to the current S/4 HANA platform. It will be mandatory for the cutover projects only. Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| ZXX34 | Plant | Plant represent a site of the PPM Item. Mandatory for all PPM Items. It is a Required Field: Preload Check to be done to confirm that this field is filled in the Data Collection Template |
| ZXX35 | Idea ID | Field to store the Idea number where this is known. This is an optional field for migration |
| ZXX36 | Subsidy | Use this checkbox if the project is eligible for government or institutional subsidies. This is an optional field for migration |
| Sub_Relevance | Subsidy Relevance | This field is used to provide a concise description of the Subsidy Relevance. (This is a long text field) Required If Subsidy field is selected. Preload Check to be done to confirm that this field is filled in the Data Collection Template when required. |
| Key_Assump | Key Assumptions | This field is used to provide key Assumptions related to projects. (This is a long text field) Conditional for Items where assumptions are to be maintained, This is an optional field for migration |
| Variations | Variations | This field is used to provide details about key project variations. (This is a long text field) Conditional for Items where assumptions are to be maintained, This is an optional field for migration |
| Other | Other Information | This field is used to provide additional details about project. (This is a long text field) This is an optional field for migration |
| ACT_DPCPT | Active Decision Point | Indicates the currently active Decision Point (Stage Gate) for the item. To be selected if item is not initial phase Drop down field from /RPM/ITEM_PHASE based on selected ITEM_TYPE |
| Instance | Instance | Instance where the item is to be loaded. |
Decision Point. The list of decision points for an item is based on configuration table /RPM/ITEM_PHASE-PHASE_ID for ITEM_TYPE, when item is added to this DCT the full list of decision points for the item type must be added to the DCT.
| Field Name | Field Description | Rule |
|---|---|---|
| SNRO | Item Serial Number | Unique Identifier Item serial numbers It is a dropdown of the Item numbers maintained in the main DCT |
| DECISION_ID | Decision Point ID | Once the User selects the Item number the full list of Decision points relevant to the Item type is to be displayed. System generated Parent ID of the Decision Point This is a display only field |
| NAME | Decision Point Description | Name of the decision point, part of the customization and can't be changed. This is a display only field |
| PLAN_START | Decision Point Planned Start Date | This field stores the plan start date of a decision point for the items where there is SG tracking required |
| PLAN_FINISH | Decision Point Planned End Date | This field stores the plan finish date of a decision point where SG tacking is required |
| ACTUAL_START | Decision Point Actual Start Date | This field stores the actual start date of a decision point derived from the initiation date of respective stage gate approval. |
| ACTUAL_FINISH | Decision Point Actual End Date | This field stores the actual finish date of a decision point derived from the approved date of respective stage gate approval. |
| ZXXX01 | Variation Reference | This field stores the identifier and short description of Variation required to variation budget approval |
Authorization - For "Need-to-know" projects, named users will be added manually.
| Field Name | Field Description | Rule |
|---|---|---|
| SNRO | Item Serial Number | Unique Identifier Item serial numbers It is a dropdown of the Item numbers maintained in the main DCT and marked as Need to Know. |
| USER_ID | SAP User Name | Named user who should have read access to the Need to Know Item |
In conjunction with DCT business user will be provided with Person Responsible / Applicant list for reference.
List the steps that need to occur before extraction can commence
| Item # | Step Description | Team Responsible |
|---|
The Target fields are mapped to the applicable Legacy field that will be its source,. This identifies the transformation activity required to allow Syniti Migrate
to make the data Target ready:
| Item # | Step Description | Team 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 |
8 | Re-transform and re-validate the Pre-load reports if necessary. | Data team |
9 | Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off. | Business |
10 | Analyze and resolve any pre-load defects logged by business. | Data team |
11 | Repeat steps 7 to 10 if necessary | Data team |
12 | Proceed to pre-load validations | Data team |
Transformation Rules
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | PARENT_ID | Parent Bucket ID | S/4 Hana | /RPM/ITEM_D | PARENT_ID | Parent Bucket ID | Manually copy from Non ECC source | |
| 2 | S/4 Hana | /RPM/ITEM_D | PORTFOLIO_ID | Portfolio ID | Global Default "SYENSQO" | ||||
| 3 | WP2 | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Apply first successful rule If PROJ-PSPID start with RR* then capture in DCT. If any WBS elements PRPS-USER0 starts with IT then Z009 IF PROJ-ZINV = B4 Then Z011 IF PROJ-ZINV = B1, H1, or H2 Then Z013 IF PROJ-PSPID 4&5 Character of Project ID is /J: Then Z001 If PROJ-PSPID 4&5 Character of Project ID is /M: then Z002 f PROJ-PSPID 4&5 Character of Project ID is /C: then Z003 If no WBS elements is Capital, PRPS-IMPRF="" then Item type PRPS-Z010 | |||
| 4 | PF2 | PROJ | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Apply first successful rule only If PROJ-PSPID start with R-then capture in DCT. Investment Reason = H0 then Z009 IF PROJ-ZINV = B4 Then Z011 IF PROJ-ZINV = B1, B5, H1, or H2 Then Z013 IF PROJ-PSPID 4&5 Character of Project ID is /J: Then Z001 If PROJ-PSPID 4&5 Character of Project ID is /M: then Z002 f PROJ-PSPID 4&5 Character of Project ID is /C: then Z003 If no WBS elements is Capital, PRPS-IMPRF="" then Item type PRPS-Z010 | ||
| 5 | DCT | ITEM_TYPE | Type | S/4 Hana | /RPM/ITEM_D | ITEM_TYPE | Type | Manually copy from Non ECC source | |
| 6 | WP2/PF2 | PROJ | TEXT1 | Project Description | S/4 Hana | CGPL_TEXT | TEXT1 | Name | Copy source to target |
| 7 | DCT | TEXT1 | Name | S/4 Hana | CGPL_TEXT | TEXT1 | Name | Manually copy from Non ECC source | |
| 8 | WP2/PF2 | STXL | LTEXT | Long Description | S/4 Hana | STXL | LTEXT | Description | Copy source to target |
| 9 | DCT | LTEXT | Item Description | S/4 Hana | STXL | LTEXT | Description | Manually copy from Non ECC source | |
| 10 | DCT | STATUS | Item Status | S/4 Hana | /RPM/ITEM_D | STATUS | Item Status | Manually copy from Non ECC source | |
| 11 | WP2/PF2 | PROJ | PLFAZ | Project planned start date | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Copy from source, format YYYYMMDD |
| 12 | DCT | PLANNED_START | Planned Start | S/4 Hana | /RPM/ITEM_D | PLANNED_START | Planned Start | Manually copy from Non ECC source | |
| 13 | WP2/PF2 | PROJ | PLSEZ | Project planned finish date | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Copy from source, format YYYYMMDD |
| 14 | DCT | PLANNED_FINISH | Planned Finish | S/4 Hana | /RPM/ITEM_D | PLANNED_FINISH | Planned Finish | Manually copy from Non ECC source | |
| 15 | DCT | CATEGORY | Investment Reason | S/4 Hana | /RPM/ITEM_D | CATEGORY | Investment Reason | Manually copy from Non ECC source | |
| 16 | S/4 Hana | /RPM/ITEM_D | SUBCATEGORY | Sub Business Driver | Value Mapping: Investment Reason Based on the Category field | ||||
| 17 | S/4 Hana | /RPM/ITEM_D | TTYPE | Main Business Driver | Value Mapping: Investment Reason Based on the Category field | ||||
| 18 | S/4 Hana | /RPM/ITEM_D | PTYPE | Investment Category | Value Mapping: Investment Reason Based on the Category field | ||||
| 19 | WP2/PF2 | PROJ | VBUKR | Company code | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Company Code | Value Mapping: Old to New Company Code |
| 20 | DCT | GEOGRAPHY | Company code | S/4 Hana | /RPM/ITEM_D | GEOGRAPHY | Company Code | Manually copy from Non ECC source | |
| 21 | WP2/PF2 | PROJ | PWHIE | WBS currency | S/4 Hana | /RPM/ITEM_D | CURRENCY | CURRENCY | Copy from Source |
| 22 | DCT | Currency | Currency | S/4 Hana | /RPM/ITEM_D | CURRENCY | CURRENCY | If Legacy Project ID field is empty then Value Mapping: Currency From Company Code | |
| 23 | S/4 Hana | /RPM/ITEM_D | UNIT | Unit | Default to "TAG"(Day) | ||||
| 24 | S/4 Hana | /RPM/ITEM_D | CAP_PERIODTYPE | Capacity Period Breakdown | Default to "12"(Annually) | ||||
| 25 | S/4 Hana | /RPM/ITEM_D | PERIODTYPE | Fin Period Breakdown | Default to "12"(Annually) | ||||
| 26 | DCT | INITIATIVE_ID | INITIATIVE ID | S/4 Hana | /RPM/ITEM_D | INITIATIVE_ID | INITIATIVE ID | Manually copy from Non ECC source | |
| 27 | DCT | ZXX2 | Spending Range | S/4 Hana | /RPM/ITEM_D | ZXX2 | Spending Range | Manually copy from Non ECC source | |
| 28 | DCT | ZXX3 | GBU Market Hierarchy | S/4 Hana | /RPM/ITEM_D | ZXX3 | GBU Market Hierarchy | Manually copy from Non ECC source | |
| 29 | DCT | ZXX4 | End User market | S/4 Hana | /RPM/ITEM_D | ZXX4 | End User Market | Manually copy from Non ECC source | |
| 30 | DCT | ZXX5 | Corporate Hierarchy | S/4 Hana | /RPM/ITEM_D | ZXX5 | Corporate Hierarchy | Manually copy from Non ECC source | |
| 31 | DCT | ZXX6 | Cluster | S/4 Hana | /RPM/ITEM_D | ZXX6 | Cluster | Manually copy from Non ECC source | |
| 32 | DCT | ZXX7 | Product Hierarchy | S/4 Hana | /RPM/ITEM_D | ZXX7 | Product Hierarchy | Manually copy from Non ECC source | |
| 33 | DCT | ZXX10 | Export control | S/4 Hana | /RPM/ITEM_D | ZXX10 | Export Control | Manually copy from Non ECC source | |
| 34 | DCT | Justification | Justification (Export Control) | S/4 Hana | STXL | Justification | Justification (Export Control) | Manually copy from Non ECC source | |
| 35 | DCT | ZXX11 | Need-to-know | S/4 Hana | /RPM/ITEM_D | ZXX11 | Need-to-know | Manually copy from Non ECC source | |
| 36 | WP2/PF2 | PROJ | ZZ_POSIT | Position of the person responsible | S/4 Hana | /RPM/ITEM_D | ZXX14 | Project Owner | Value Mapping: Old Position ID to New Position ID |
| 37 | DCT | ZXX14 | Project Owner | S/4 Hana | /RPM/ITEM_D | ZXX14 | Project Owner | Manually copy from Non ECC source | |
| 38 | S/4 Hana | /RPM/ITEM_D | ZXX15 | Project Owner | Value Mapping: Position Name from Position Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001 | ||||
| 39 | DCT | ZXX16 | Project Financial Controller Position ID | S/4 Hana | /RPM/ITEM_D | ZXX16 | Project Financial Controller Position ID | Manually copy from Non ECC source | |
| 40 | S/4 Hana | /RPM/ITEM_D | ZXX17 | Project Financial Controller Position Name | Value Mapping: Position Name from Position Mapped from table field HRP1000-STEXT where HRP1000-OBJID= ZX001 | ||||
| 41 | S/4 Hana | /RPM/ITEM_D | ZXX37 | Scoring Methodology | Value Mapping: Investment Reason Based on the Category field | ||||
| 42 | DCT | ZXX18 | Starting risk Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX18 | Starting risk Magnitude | Manually copy from Non ECC source | |
| 43 | DCT | ZXX19 | Starting risk Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX19 | Starting risk Likelihood | Manually copy from Non ECC source | |
| 44 | DCT | ZXX20 | Residual risk Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX20 | Residual risk Magnitude | Manually copy from Non ECC source | |
| 45 | DCT | ZXX21 | Residual risk Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX21 | Residual risk Likelihood | Manually copy from Non ECC source | |
| 46 | DCT | ZXX22 | Regulatory Mandated Magnitude | S/4 Hana | /RPM/ITEM_D | ZXX22 | Regulatory Mandated Magnitude | Manually copy from Non ECC source | |
| 47 | DCT | ZXX23 | Regulatory Mandated Likelihood | S/4 Hana | /RPM/ITEM_D | ZXX23 | Regulatory Mandated Likelihood | Manually copy from Non ECC source | |
| 48 | DCT | ZXX24 | Regulatory Mandated Time Horizon (to start project) | S/4 Hana | /RPM/ITEM_D | ZXX24 | Regulatory Mandated Time Horizon (to start project) | Manually copy from Non ECC source | |
| 49 | DCT | ZXX25 | Capitalization Date | S/4 Hana | /RPM/ITEM_D | ZXX25 | Capitalization Date | Manually copy from Non ECC source | |
| 50 | WP2/PF2 | PROJ | PRCTR | Profit Center | S/4 Hana | /RPM/ITEM_D | ZXX26 | Profit Centre | Value Mapping: Profit Center Old to New |
| 51 | DCT | ZXX26 | Profit Centre | S/4 Hana | /RPM/ITEM_D | ZXX26 | Profit Centre | Manually copy from Non ECC source | |
| 52 | WP2/PF2 | PRPS | ZZ_WEGO_ID | WEGO ID | S/4 Hana | /RPM/ITEM_D | ZXX27 | Wego ID | If all WBS Elements for the PSPID record has the same WEGO Number only. |
| 53 | DCT | ZXX27 | WeGo ID | S/4 Hana | /RPM/ITEM_D | ZXX27 | WeGo ID | Manually copy from Non ECC source | |
| 54 | DCT | ZXX29 | Budget Provision | S/4 Hana | /RPM/ITEM_D | ZXX29 | Budget Provision | Manually copy from Non ECC source | |
| 55 | DCT | ZXX30 | Opportunity ID | S/4 Hana | /RPM/ITEM_D | ZXX30 | Opportunity ID | Manually copy from Non ECC source | |
| 56 | DCT | ZXX31 | Archetype | S/4 Hana | /RPM/ITEM_D | ZXX31 | Archetype | Manually copy from Non ECC source | |
| 57 | DCT | ZXX32 | Must Do Justification | S/4 Hana | /RPM/ITEM_D | ZXX32 | Must Do Justification | Manually copy from Non ECC source | |
| 58 | WP2/PF2 | PROJ | PSPID | ID | S/4 Hana | /RPM/ITEM_D | ZXX33 | Legacy Project ID (For existing records this is the key for related DCT values) For additional Items not from source this will be empty. | Copy From Source |
| 59 | WP2/PF2 | PROJ | WERKS | Plant | S/4 Hana | /RPM/ITEM_D | ZXX34 | Plant | Value Mapping: Old Plant to New |
| 60 | DCT | ZXX34 | Plant | S/4 Hana | /RPM/ITEM_D | ZXX34 | Plant | Manually copy from Non ECC source | |
| 61 | DCT | ZXX35 | Idea ID | S/4 Hana | /RPM/ITEM_D | ZXX35 | Idea ID | Manually copy from Non ECC source | |
| 62 | DCT | ZXX36 | Subsidy | S/4 Hana | /RPM/ITEM_D | ZXX36 | Subsidy | Manually copy from Non ECC source | |
| 63 | DCT | Sub_Relevance | Subsidy Relevance | S/4 Hana | STXL | Sub_Relevance | Subsidy Relevance | Manually copy from Non ECC source | |
| 64 | DCT | Key_Assump | Key Assumptions | S/4 Hana | STXL | Key_Assump | Key Assumptions | Manually copy from Non ECC source | |
| 65 | DCT | Variations | Variations | S/4 Hana | STXL | Variations | Variations | Manually copy from Non ECC source | |
| 66 | DCT | Other | Other Information | S/4 Hana | STXL | Other | Other Information | Manually copy from Non ECC source |
List of Custom Target Reports for this object is maintained here: Conversion Specification - Custom Reports Register.
The Standard template for the upload of Item that can be used for the upload of Items, this includes ability to upload of custom fields, into S/4 Hana: Item Load File.xlsx - Google Sheets
In addition to the fields mapped to the target fields the following is required for the automatic creation of the PS projects if the standard upload program is used
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 66 | S/4 Hana | Upload program | CREATE_CPROJECT | Create Project | If the Legacy ID exists or if Item Type is Capital Lease, Direct Asset Purchase or Capital Spares, then field is X else it remains blank | ||||
| 67 | S/4 | S/4 Hana | Upload program | CPRO_TEMPLATE | Project Template to be used | If CREATE_CPROJECT is active then field must be set. Select PS_TEMPLATE from /RPM/PSPTIT_MAP using ITEM_TYPE | |||
| 68 | S/4 | S/4 Hana | Upload program | PS_LOGSYSTEM | Logical System | If CREATE_CPROJECT is active then field must be set. Select OBL_TYPE from /RPM/PSPTIT_MAP using ITEM_TYPE |
For items types with multiple decision points the active decision point must be updated as part of the item create. If using the standard upload this is done using the Item Decision Point work sheet.
If using the standard upload program Decision Point sheet the active decision point can only be set by changing the statuses of the preceding decision points to end state and the active decision point to start state.
In addition users may have maintained Decision point dates in the DCT, these updated dates are to be included in the requirement
The expectation is that there will be multiple records for each loaded item.
/RPM/ITEM_PHASE-PHASE_ID for ITEM_TYPE.
Determination of Preceding decision point
Preceding decision point determined /RPM/ITEM_PHASE-PHASE_ID for ITEM_TYPE.
Determination Decision Point Status
Decision point start status /RPM/DP_STATUS-START_STATUS = X for ITEM_TYPE and PHASE_ID
Decision point start status /RPM/DP_STATUS-END_STATUS = X for ITEM_TYPE and PHASE_ID
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | S/4 Hana | /RPM/DECISION | ITEM | Item ID | |||||
| 2 | S/4 Hana | /RPM/DECISION | DECISION_ID | Decision Point ID | The List of decision points for each item is based on the item type as per | ||||
| 3 | S/4 Hana | /RPM/DECISION | NAME | Decision Point Name | Decision Point Name from RPM/PHASE_T using ITEM_TYPE and DECISION_ID | ||||
| 4 | S/4 Hana | /RPM/DECISION | STATUS | Decision Point Status | Decision point start status for preceding decision points /RPM/DP_STATUS-END_STATUS = X for ITEM_TYPE and PHASE_ID Decision point start status for active decision point /RPM/DP_STATUS-START_STATUS = X for ITEM_TYPE and PHASE_ID | ||||
| 5 | DCT | Decision Point | PLAN_START | Decision Point Planned Start Date | S/4 Hana | /RPM/DECISION | PLAN_START | Decision Point Planned Start Date | Manually copy from Non ECC source |
| 6 | DCT | Decision Point | PLAN_FINISH | Decision Point Planned End Date | S/4 Hana | /RPM/DECISION | PLAN_FINISH | Decision Point Planned End Date | Manually copy from Non ECC source |
| 7 | DCT | Decision Point | ACTUAL_START | Decision Point Actual Start Date | S/4 Hana | /RPM/DECISION | ACTUAL_START | Decision Point Actual Start Date | Manually copy from Non ECC source |
| 8 | DCT | Decision Point | ACTUAL_FINISH | Decision Point Actual End Date | S/4 Hana | /RPM/DECISION | ACTUAL_FINISH | Decision Point Actual End Date | Manually copy from Non ECC source |
| 9 | DCT | Decision Point | ZXXX01 | Variation Reference | S/4 Hana | /RPM/DECISION | ZXXX01 | Variation Reference | Manually copy from Non ECC source |
For items with Need to know flag set the authorization to display the item is restricted to named users only. If using the standard upload this is done using the Item Authorization work sheet.
| Rule # | Source system | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
|---|---|---|---|---|---|---|---|---|---|
| 1 | DCT | Authorization | SNRO | Item Serial Number | S/4 Hana | ACO_USER | ITEM_ID | Object ID | Manually copy from Non ECC source |
| 2 | S/4 Hana | ACO_USER | ACTIVITY | Activity | Default to activity "READ" | ||||
| 3 | DCT | Authorization | USER_ID | SAP User Name | S/4 Hana | ACO_USER | USER | User ID | Manually copy from Non ECC source |
| Mapping Table Name | Mapping Table Description |
|---|---|
| Company Code | Value Mapping: Old to New Company Code |
| T001 | Value Mapping: Currency From Company Code |
| HRP1000 | Value Mapping: Position Name from Position Value Mapping: Old Position ID to New Position ID |
| Plant | Value Mapping: Old Plant to New |
| Profit Center | Value Mapping: Profit Center Old to New |
| Investment Reason | Value Mapping: Investment Reason to Other fields. |
| Item # | Step Description | Team Responsible |
|---|---|---|
1 | Ensure all the fields that require value mapping, as stipulated. Mapping tables, have the correct values mapped and imported into tool. | Data Team |
| Task | Action |
|---|---|
| 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. |
| Task | Action |
|---|---|
Conversion Accuracy | SyWay I2M Data Team to verify that all fields below meet pass the 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. |
| Task | Action |
|---|---|
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. |
| 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 (and signed-off DCT data). |
The load process includes:
| Item # | Step Description | Team Responsible |
|---|---|---|
| 1 | Load using transaction RPM_DX_ITEM | SyWay Data Team |
| 2 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay Data Team |
| 3 | Load 3 records for < > to validate if data is loaded successfully without errors | SyWay Data Team |
| 4 | Proceed with full load if steps 2 and 3 are validated | SyWay Data Team |
| 5 | Validate few records loaded by accessing Portfolio Item App | SyWay Data Team |
| 6 | Validate few records loaded by accessing PS Project App | SyWay Data Team |
| 7 | Generate post load report if step 5 is validated | SyWay Data Team |
| 8 | Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off. | Business |
Load Phase and Dependencies
Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence
Key Configuration requirement
| Item # | Configuration Item |
|---|---|
| 1 | Override Default Global Settings (Master Switches 0002 Switched off - Item will have manual ID) |
| 2 | Define Currency Units |
| 3 | Item Types |
| 4 | Item Type Status |
| 5 | Configure Fields for Mass Import |
| 6 | Category |
| 7 | Sub-Category |
| 8 | Technology Type |
| 9 | Group |
| 10 | Area |
| 11 | Object Link |
| 12 | Plant |
| 13 | DFM Object Links |
| 14 | Map Item Types to PS Project |
| Object # | Preceding Object Conversion Approach |
|---|---|
| 1113 | Portfolio Bucket Hierarchy |
1073 | Profit Centre |
1019 | Template Projects |
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 |
|---|---|---|
Invalid Data | Invalid Portfolio | Validate DCT content |
Invalid Data | Invalid Bucket ID (Parent ID does not exist) | Validate DCT content |
| Invalid Data | Invalid Item Type | Validate Transformation rules and DCT values |
| Invalid Data | Invalid dates | Validate format of the date fields. |
| Invalid Data | More that one Item per GBU/Company Code/Plant for Capital Lease Item Type | Remove Duplicate values from DCT |
| Invalid Data | More that one Item per GBU/Company Code/Plant for Direct Asset Purchase Item Type | Remove Duplicate values from DCT |
| Invalid Data | More that one Item per GBU/Company Code/Plant for Capital Spares Item Type | Remove Duplicate values from DCT |
| Task | Action |
|---|---|
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.). |
| Task | Action |
|---|---|
Conversion Accuracy | Verify that the Portfolio Item in target S/4 HANA were loaded correctly via Standard Portfolio Item display and table /RPM/ITEM_D |
Conversion Accuracy | Verify that the Project Definition in target were created correctly as per project template using transaction CN41n |
Conversion Accuracy | Verify that the WBS Structure in target were created correctly as per project template using transaction CN41n |
| Task | Action |
|---|---|
| Verify Count | Extract Item details from Item App in S/4 Hana |
| Verify Count | Extract Project Definitions from Project Definitions App in S/4 Hana, to be same as Item count |
| Task | Action |
|---|---|
| Verify Accuracy | Extract Item details from Item App in S/4 Hana and compare |
| Extract Project details from Project in S/4 Hana and compare to expected results |
Any additional key assumptions.
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.