Document Links

Introduction

This Data Flow Specification (DFS) defines the end-to-end data flow required to meet the following requirements:

SyWay have decided to perform planning for PPM in SAC rather than in S/4. The requirements above reflect the planning models and related stories for planning. The flows for each process are described with the separate functional specifications linked above.

The Item planning is retracted back into S/4 to enable availability control. The master data is created in S/4 which forms the backbone for the planning models. 

There is no business content in Datasphere for this area, however, all of the CDS views are extraction enabled.

The business content in SAC has been recently been re-created. The modelling will reflect the concepts in this latest version, eg using the UUID's.

Gaps

Data Flow Diagram

Source System Extractors

The Item and Bucket hierarchy will not be extracted but rather built in DSP via the Parent UUID. This will work perfectly for the SAC planning component but the DSP reporting component will need to be tested.

All of the above are considered as Tier 1 and only maintained in RoW. 

Inbound Layer

No inbound field adjustments are applied. Standard technical fields (load date/time, source system) are retained as delivered.

/SYQ/ replaced by SYQ

Harmonisation Layer

2VR_Auths → 2VR_S4HARM_SYQI_AuthorizationUser

Purpose: 

Assigns Item UUID to authorised users where there is sensitive project. Will be read and added to ProjectPortfolioItem Read/Write fields

2VR_TScore → 2VR_S4HARM_SYQI_Scoring

Purpose: 

Global Parameter table used in scoring

2VR_TStrat → 2VR_S4HARM_SYQI_Strategic

Purpose: 

Parameter table used in scoring. Detail by GBU

2VR_TRiskM → 2VR_S4HARM_SYQI_Risk_Mag

Purpose: 

Master data table to map the key to a value

2VR_TRiskL → 2VR_S4HARM_SYQI_Risk_Lkd

Purpose: 

Master data table to map the key to a value

2VR_TRegM → 2VR_S4HARM_SYQI_Reg_Mag

Purpose: 

Master data table to map the key to a value

2VR_TRegL → 2VR_S4HARM_SYQI_Reg_Lkd

Purpose: 

Master data table to map the key to a value

2VR_TRegT → 2VR_S4HARM_SYQI_RegTimeHz

Purpose: 

Master data table to map the key to a value

Propagation Layer

Join with long texts (excluding Z07)

Create Odata connection to fill the master data required by SAC planning

2VR_LeadLed → 3VR_PrjAct

Purpose: 

Restrict to PPM relevant data

Filter:

where project <> ''

Comments:

Ensure we have commitments in this view

Data Migration approach:

Normally stored in a separate model, however, as this is seamless planning and the data will need to be amended along with new data, it will have to be loaded as normal data in the same model.

• Subject to change in planning process
• Needs to be displayed in the same version when planning
• potentially could identify using an audit trail

Comments:

Long texts are required from STXL

Types of projects:

Expenditure on capital (Capex), which always is managed via a project using PPM

Capital maintenance is assigned to a project

Operation expenditure (Opex) can be managed via PPM but does not have to be - eg finance only projects

Master data:

When attributes need to be planned, we will try and plan as measures rather than attributes

Scoring:

This is a separate model

• Financial driven projects read from the Business Case

3VR_Bucket - 2VR_SPOD_I2MPPM_I_ProjectPortfolioBucket

Purpose:

Read data from planning model to be used further in DSP

Project Score is calculated according to 3 methodologies, determined by ; Financial, Risk or Regulatory.

• • Retrieve Item Scoring Methodology from Investment Reason on PPM Item Planning Transaction Data

How is this score used (attribute or measure) - prioritisation as a number to be sorted

Calculation - sac planning action vs DSP persisted vs on the fly

Include value in snapshot - read score when snapping (better to persist)

I have split this into 3 views for simplicity, but they could be combined

3VR_Item - 3VR_SPOD_I2MPPM_ProjectPortfolioItem

Purpose:

Planning model made available for reporting

Item master data

Purpose:

Read data from planning model to be used further in DSP

Scoring:

• • Perform lookups from Scoring MD to values (the lookup function is more for fuzzy logic)
  • Read accuracy % from Item MD Planning
  • Derive current Phase, WBS Element Description linked to active Decision Point
  • Derive in-flight, Set to 'X' if Item Status = Z002 Approved or Z003 TECO, else blank
  • Derive current Decision Point, it is when the /RPM/DECISION-ACTIVE = X transitive attributes showing attributes like dates
  • Restricted users for sensitive projects reading from P_PPM_AUTHORIZATIONBYUSER

Source Views:

I_ProjectPortfolioItem

4MP_item

2VR_TScore

2VR_TStra

2VR_TRiskL

2VR_TRiskM

2VR_TRegL

2VR_TRegM

2VR_TRegT

Join:

Using the attributes, read the master data scoring tables and update the value (attribute vs measure v matrix view)

Formula:

Risk Matrix score = (Starting Risk = RISK_MAGNITUDE_VALUE * RISK_LKLHD_VALUE) -  (Residual Risk = RISK_MAGNITUDE_VALUE  * RISK_LKLHD_VALUE)

Reg Matrix Score = REG_MAGNITUDE_VALUE  REG_LKLHD_VALUE  * REG_TIME_HORIZON_FACTOR

3VR_ItemSS -> 3TL_SPOD_I2MPPM_ItemSS

Purpose:

Perform a snapshot of the data at a particular point in time.
To cater for attributes that can change over time, these attributes will be moved to dimensions.

Source:

3VR_Item

Transformation flow:

Graphical flow

Formula:

Add a timestamp and derive the SnapShot ID

Process:

Adhoc - scheduled via a task chain triggered by an API step in a SAC multi-action

Quarterly - scheduled via a task chain based on time

Stage gate - scheduled via a task chain based on a table extracted from S/4 - TBC

3VR_Score -> 3TL_SPOD_I2MPPM_Score

Purpose:

Project Score is calculated according to 3 methodologies, determined by ; Financial, Risk or Regulatory.

How is this score used (attribute or measure) - prioritisation as a number to be sorted

Include value in snapshot - read score when snapping (better to persist)

Source:

Item

Business case

Scoring

Strategy

Parameter:

Restricted to Items in the Item Planning form

Transformation flow:

Suggest using SQL as easy to perform complex calculations

Read above views and 

Case itemtype when

• • Fin:   read 2VR_Score(blue) calculating Intensity Index = Initial Starting Point + NPV / Cost Weighting * (NPV / Project Cost (FEC)) * MIRR Weighting / MIRR Comparison Rate * MIRR^MIRR Exponent
  • Risk: read 2VR_Score(blue) calculating Intensity Index = Initial Starting Point + Delta PL/Cost Weighting * (Risk Reduction / (Project Cost (FEC) * 10^6)) + Log(Cost) Weighting * (Log (Project Cost (FEC) * 10^6)) ^ Log(Cost) Exponent
  • Reg: read 2VR_Score(blue) calculating Intensity Index = (Initial Starting Point + Delta PL/Cost Weighting * ((Matrix Score ) / (Project Cost (FEC) * 10^6)) + Log(Cost) Weighting * (Log (Project Cost (FEC) * 10^6)) ^ Log(Cost) Exponent)

Read 2VR_Score where Project Score calculating Unweighted Project Score = 1 / (1 + EXP (-((Intensity Index + Index Offset) - Location Parameter) / Scale Parameter)) * PES Range + PES Minimum

Read 2VR_Strat where GBU = Item GBU, Buss Driver = Item Buss Driver calculating Score = Unweighted Project Score * WGHTG_FACTOR

Target:

3TL_Score with only ItemUUID and score

Trigger:

Can be initiated from the planning form for Item

However, if an ad-hoc request is required for all projects, then a identical Transformation Flow will be required without parameters

Reporting Layer

If you want to show the external format and text in SAP Analytic Cloud instead of the internal format the modelling in the Analytic Model needs to be done like this example:

4MP_Item 

Purpose:

This is for planning

Functional Spec:

ERP-2665 Data Model - PPM Items

Comments:

Include live data 3VF_PrjAct (must be exposed for consumption)

Outbound Layer

When retracting, you cannot filter on the company code, even if in the model, as restricted to the fields in the API.

Options: play with having 2 fin view types which can be corrected on the API mapping. 

Maybe the guids have a number range sequence