Demantra - S&OP (Sales & Operational Planning)Sales & Operational Planning module of Demantra has got a complete makeover by Oracle, in Demantra's 7.2 release Oracle launched integrated S&OP module as Supply Chain Planning offering. S&OP module has been integrated with ASCP (Advanced Supply Chain Planning), SNO (Strategic Network Optimization) and IO (Inventory Optimization) of APS suite, along with seamless integration with Oracle EBS R12.0.4.
High Level Data Flow in S&OP:
Data flow in S&OP can vary based on whether ASCP or SNO or Both are used in the process. We will go through one of the possible scenarios here and will then later focus on integration with ASCP & SNO separately.
- Collection of Shipment & Booking history (old DM feature)
- Download History data into Demantra using seeded workflow "EBS Full Download"
- Demand Review:
- Generate Forecast - Shipment & Booking
- Generate Consensus Forecast
- Submit Consensus Forecast to Planning applications (SNO/ASCP/IO etc.)
- Supply Chain Planning
- Generate Assignment Set(sourcing rules) from SNO Plan based on Consensus Forecast
- Generate Safety Stock plan from IO, using Consensus Forecast and Accuracy
- Create ASCP Plan with Assignment Set from SNO, Safety Stocks from IO and Demand Schedule from Demantra - Demand Review process
- Make ASCP plan available for S&OP (new check box in ASCP plan options)
- Supply Plan Review
- Download Supply Plan names/members into Demantra S&OP using seeded workflow "Load Plan Scenarios"
- Download Supply Plan data using seeded Level Method "Load Scenario Plan Data"
- Exceptions are detected automatically as part of Load data workflow and S&OP users are intimated with Tasks/Alerts
- In case for removal of Exceptions Supply plan needs to be re-launched after making recommended changes, then Supply plan is re-run and re-downloaded into Demantra
- Once Exceptions are handled and are taken care of, then next step is taken
- S&OP Executive Review
- Review Key Performance Indicators (KPIs) as per the S&OP plan/scenarios
- Review Supply plan scenarios and Exceptions
- S&OP committee finalizes S&OP Plan
- Publish the Final Plan and archive it, for future references
You can refer to Oracle's documentation on S&OP module available on Oracle Metalink for getting into details. ( Refer to previous post for whereabouts of Demantra http://oracledemantra.blogspot.com/2008/07/demantra-documentation-on-metalink.html)
10 comments:
Thanks. Im Inspired again.
Hi,
Im a fresher and i have knowlege of sql,pl-sql and want to learn Demantra.Can you suggest how to start.
Thanks
Raj
CA,USA
there are lot of documentation available on net, follow that. Also you should install demo version on your laptop may be for learning purpose.
You should read articles and blogs related to product as well.
Regards
Raj
Your post is very informative. The post described Sales & Operational brilliantly. The diagram depicts the entire flow. This helps us to learn the entire procedure. This is very well written post. Keep it up. Thanks for the post.
Hi,
Can you please help me with following questions,
After Supply review & Executive review, a plan approved and this Final Plan is published.
1) Where is this plan published i.e to which applications / modules final plan gets published to.
2) What are the data / series flowing with this published plan to above application/s. (kindly list all the data)
3) Are there any pre-seeded workflows available for such export, if yes, which one.
Thanks & Regards,
Annie.
Hi Annie,
Once a supply plan has been reviewed and approved, the corresponding Consensus demand forecast is fed to Operations plan(production plan). In terms of modules, Consensus Forecast is published to ASCP module. ASCP module is used for Production plan run and then planned orders are released to supply planing for make or buy.
Data series which is used for Demantra to ASCP publication is "Consensus Forecast" in standard integration. Depending on implementation series name could vary and also you may need to publish this data to modules like IO, SNO or APCC too.
There are handful of standard workflows like "Upload Local Forecast" which are available for publishing Consensus Fcst to ASCP.
Hope this helps.
That is helpful, Thank You, though now i am little confused,
1)
After Demand review, 'Consensus Forecast' is sent to ASCP. So, When we publish the final plan, after executive review the 'Consensus forecast' which goes to ASCP is different or must have been changed in supply review or executive review ??
If yes, is there any transactional data getting changed, as this transactional changes will not flow back to ascp/ebs ?.
Also After Demand Review when Demantra sends Consensus forecast to ASCP, what ASCP sends back is a Plan (production/inventory/manufacturing), true right?
So will ASCP need to run a new plan using the 'Consensus forecast' sent from demantra after executive review.
2)
Say If EBS & ASCP are on same instance and Demantra on another instance (separate box), thn is it possible to use standard integration using DB-Link or do i need a customized integration.
Thanks & Regards,
Annie
1. Yes, that is true. Approved consensus fcst feeds the operational ASCP plan. You may also consider having a S&OP specific ASCP plan which is more aggregated and meant for RCCP planning. The Constrained Fcst and planned production output from that plan could feed into S&OP review and later the approved consensus is fed to ASCP operational plan.
2. Std integration for S&OP would work if Demantra and ASCP are on same DB. Otherwise you are looking at custom builds.
Hope this helps.
HI Raj,
could you please explain me what is the difference between DM,S&OP,SNO,PTP modules and there functionality . if you have any internet link please provide me.
Thanks
Gagan
Post a Comment