on 02-24-2015 3:01 PM
Currently the production orders are created in ECC with reference to the plan orders transferred from APO. These orders are transferred back to APO as part of standard CIF. Since ECC is the owner of Production orders, we don’t want APO influencing any changes in production order. But there are situations when the APO is rescheduling the production order by automatically triggering heuristics after getting the changes in capacity from ECC via CIF. That is impacting with the schedule of orders already planned by business in ECC. One such known issue is when the capacity of resource has change during the time when order is scheduled. How should we avoid this?
Hi Anubrata,
Could you please tell which PPDS heuristic(Standard or custom) you are using which is automatically triggered after the capacity change.
Also where and how are you changing the capacity..
Regards
Ashutosh Shende
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anubrata,
Have you checked the configuration in publication of planning results.in transaction /SAPAPO/CP3
Any settings that you make here only apply to the publication type In-House Production. You can specify whether, and in what circumstances, changes to planned orders or production orders in SAP R/3 that lead to rescheduling in SAP APO are automatically retransferred to SAP R/3.
Automatic retransfer is useful if the dates for the orders need to agree in both systems at a particular point in time.
You can choose between three settings:
Please let me know if this helps.
Regards
Ashutosh Shende
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashutosh,
Thanks for answer which is helpful.
Here the business process needs the retransfer but we have to stop the heuristics being automatically triggered in APO after the capacity changes. For that I think a BADI implementation would be helpful. Please note we are not using optimizer here, we are using PPDS heuristics.
Thanks & Regards,
Anubrata Bhattacharya
HI;
I think it is CCR Issue for the Consistency check with data base.
Regards;
A.S.KUMAR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Please read this note that explains how to implement BAdI: /SAPAPO/CL_EX_CIF_IP in order to change this standard behaviour.
586685
- Activating retention of activity dates
Please take a look of this thread:
Kind Regards,
Mariano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anubrata,
Please check note 161028. This is the standard behaviour. If the SKU is X0 have to be planned by APO!
This note describes a modification proposal for the following purpose;
When a planned order is imported into R/3 via the interface, it is never scheduled in R/3 (detailed scheduling: esp. generation of capacity requirements).
This is the current design of APO <-> R/3 interface.
However, for such special requirements that the planned order should 'always' be scheduled, you can apply the following source code change.
This modification enables you to always automatically schedule the planned order that comes over the interface from APO for 'change' and 'create'. If capacity planning is activated, then also capacity requirements are determined in R/3.
This functionality only works for PP/DS planned orders and not for SNP planned orders. For SNP orders the SNP PPM will always be reexploded after a changed planned order is send back from R/3 to APO and then the order will be rescheduled in APO again.
Hope that can help you.
Thanks.
Regards, Marius
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
4 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.