DFM Calculated Finish Dates

[Former Member]

Hi Experts

Please assist.

I have a requirement to maintain Decision Flow Management Settings as follows :

When we create an item we enter a planned start date.

This planned start date is mapped to cProjects Project Definition as a 'must start on date'

This works fine.

Then we plan durations on a task.

The duration through bottom up scheduling is rolled up to the cProject Phase as 'Calculated start' and 'calculated finish dates'

The calculated late finish date on my cProject Phase must DFM to the 'Forecast Decision Date' on the Item's Decision Point.

I have tested this and the problem is that the calculated finish date on the phase does not map to the item's decision point, UNLESS i click on the phase in 'Portfolio Management' and make a dummy change, then only does the date move to the forecast decision date on the items decision point

I would like to know what i am perhaps doing incorrect as i only want to plan a duration on the task and have the calculated late finish date map to forecast decision date on the item decision point without having to trigger the phase in portfolio management.

The config i have done is as follows :

SPRO > RPM > Global Customizing > Portfolio Independent Settings > Map Item Type to cProjects Project Type & > Map Item Template to cProject Template

Entries : I have mapped my item decision points to my cProject Phases.

Decision Point : 00001 Mapped to cProject Phase : 200000000000000000312009ZSIMFEL

Then in Base System Interfaces > Decision Flow Management >

Define Object Link types :

Object type : 0INMCPROPHASE

Frames Per Object Type : Frame 1 "Basic Data"

Fields per frame : CALCULATED_LATE_FINISH_DATE, 'Active' tick is on

Maintain Object for Synchronization

Category : cProjects,xRPM,DFM

Source Grouping : Project Phase

Target Grouping : Portfolio Item Decision Point

Inactive : False

Category : DFM

Source Grouping : Project Phase

Target Grouping : Portfolio Item Decision Point

Inactive : False

Attribute Synchronization

Define Scenario ID :

Standard Mapping

000000000000001 Initial Create

000000000000002 Horizontal Synchronization

000000000000003 Default Attributes on Create

Maintain Attributes for Synchronization Scenario's

Source Grouping : Project Phase

Target Grouping : Portfolio Item Decision Point

Oper/Sync : Create Target Object and Sync , Create with Default Values from UI , Update

Scenario Id for each entry : Horizontal.

*i have tried different scenario ID's.

Maintain Field Mappings

Main Group : PDCP - Project Definition

Sub Group : PPCP - Project Phase

Field Mapping :

Scenario ID Source Field Target Main Grouping Target Sub Grouping Target Field

Std Mapping CALCULATED_LATE_FINISH_DATE PPODP - Item Decision Point PPODP FORECAST_DEC_DATE

I have maintained this setting for these Scenario ID's as well :

Initial Create

Horizontal Synchronization

Default Attribute on Create

Please assist as soon as possible.

Kind Regards,

Ihsaan Mayet

Edited by: Ihsaan Mayet on Mar 28, 2011 3:37 PM

[Former Member · Accepted solution]

Hi, Ihsaan.

I am implementing PPM 5.0 and I am facing a similar problem. It makes no sense to have to simulate a "fake" change in the phase to have the synchronization executed. I talked to our ABAP/WebDynpro team and they told me it seems to be a bug. The system should trigger the synchronization when you save the changes.

So, what I suggest you is to go ahead and create an OSS message to SAP.

Sorry to not be able to help you...

Regards,

Ivanna