Supply Chain Planning and Collaboration

Get Involved. Join the Conversation.


  • Victor Cota


    If you want to delete all members you can use the ESS Job "Purge Data Repository" and select the Source System and Entity that you want to delete, as a recommendation you should delete the staging tables with the ESS JOB "Purge Staging Data" .

    If you want to delete selected level members you must use the FBDI with the DELETE FLAG with the value YES.



  • Silvia Cosentino

    Hi Roy

    Thank you very much


  • Roy Amozeg

    Something to try is to use 'Administer Planning Security' to give read-only access to MRP users 

    You might need to create separate roles for MRP and MPS planners and then assign different privileges by role


  • Phillip Brown

    We found in the end it was a result of the the worksheet resorting on the save function, then reverting to the origonal layout on the refresh. A bug was raised for this and a patch applied which fixed the issue. Phillip

  • Paul Keating

    Thanks Kevin - nice work.


  • Prashul Agrawal

    Hi Ramesh,

    The MAPE calculated using seeded measures it time independent. If you need time dependent, you need to create custom measure having MAPE function in the expression and passing the required measures in its syntax.

    You can take archive 1 week ago, 2 week ago and refer in custom measures similar to seeded Monthly measures.

  • Prashul Agrawal

    Thanks Venkatesh, this helps.

    Is it possible to delete the existing combinations in cloud. By loading the measure data in Target mode with just one record, though it delete the existing data but combinations still remain and show in table.

    As for some customers and items combinations which are no more sold and no forecast is coming, then they should not appear in table.

    Even using advanced filter options, not able to remove them, as if we apply condition on Product level -> Replace with - 'Sales Forecast' is not null.

    This condition applies filter only at item level, so if this item has forecast for any one customer, table displays all combinations of this item against every customer for which it was sold previously.

    Even we apply same condition to customer and product dimension, the condition at combination of these two does not apply.

    Please suggest if any suitable way?


    Hello Roy,


    Thanks for the update. Yes, I agree with your point that any pegging and release of PO can't be done in S&OP. I think we can get clear picture of on hand, PO's and safety stock in S&OP (Aggregate Build Plan) also as part of supply review cycle on S&OP we can review the supply plan to get clear picture.


    Sharath M

  • Roy Amozeg

    Yes, you can see all supply as well as demand in S&OP and also get exceptions 

    However there are differences between S&OP and Supply Planning in certain areas. For example S&OP does not generate pegging and it does not generate planned orders that you can release to execution

    There are more differences.. This was just an example


  • Dina Jacobs - SCP Customer Direct

    Hello Krishna!!

    Is it a Daily plan and what version are you on?

    There is a known issue with those 3 measures “Adjusted Price”, “Discounted Price”, and “Discount Percentage”.  For aggregate plans (Planning Time Level of week or month) it might work. 

    The possible workaround for one of the above measures.

    Create user-defined measures for the price discount in history and in the future.  My suggestion:

    1. Create a user-defined measure named “Discount Percentage History” by duplicating the provided “Discount Percentage”, setting the Edit Range to “History” and checking the “Shared Measure” option on the Advanced tab, Properties sub-tab.
    2. Create a user-defined measure named “Discount Percentage Future” by duplicating the provided “Discount Percentage”, setting the Edit Range to “Future” and leaving the “Shared Measure” option unchecked.
    3. Modify the expression for the provided “Discount Percentage Calculated” measure to use either the “Discount Percentage History” or “Discount Percentage Future”.  This could be as simple as: IF(NVL(Discount Percentage History), Discount Percentage Future, Discount Percentage History)
    4. Use the “Discount Percentage Calculated” as a causal factor in the Forecasting Profile.
    5. Add the two new measures to the Measure Catalog.
    6. Run the plan with the “Refresh with current data” option selected.
    7. Populate values for “Discount Percentage History” and “Discount Percentage Future”.
    8. Run the plan with the forecast profile selected.


    Dina Jacobs

  • Ramesh Choudhary

    Hi Cherry,

    Thanks for your suggestion on this matter.

    We are internally discussing on this and shall update in case we have further doubts or questions.




  • Ramesh Choudhary

    Hi Paul,

    Thanks for the information.

    Actually we had thought in same direction what you described above.

    One issues we found is with catalog .  'Planning Functional Area' catalog needs to be controlled at 'Master' control and in order to control it at 'Master' level, 
    the Attribute 'Planning Method' also needs to be controlled at 'Master level'.
    Hence we will not be able to assign the item with different planning method in different organizations.

    In our business case, we might plan item in one organization (MRP Planned) and might not plan (Not Planned) in other organization in a particular month.

    So how will achieve our requirement if we follow 'Planning Method' attribute approach.

    Can you please help us if you have an idea to tackle this situation.

    Please let me know if i am missing anything.



  • Venkatesh Periketi

    Check if matrix, data DYD tables are getting populated?

  • Krushna Sahoo

    Shipment history at same level is there. Adjusted history works as expected.
    Adjusted Price update also works in same table for future period.

  • Venkatesh Periketi

    Hi Krushna,

    I believe for the measure you are trying to edit data doesn't have any combination (matrix) data loaded at lowest level for the particular time bucket. 

    Adjusted Price (Granularity ID # 135 - org+item+time+customer+dc+salesrep)

    So validate if the data is loaded at the lowest levels for this Granularity.


    Venkatesh Periketi