cancel
Showing results for 
Search instead for 
Did you mean: 

We need to avoid rescheduling of Production order in APO

0 Kudos

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?

Accepted Solutions (0)

Answers (5)

Answers (5)

0 Kudos

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

0 Kudos

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:

    1. No retransfer
    2. Objects changed in SAP R/3 are not retransferred to SAP R/3 after they have been rescheduled in SAP APO.
    3. Always retransfer
    4. Objects changed in SAP R/3 are retransferred to SAP R/3 both after the initial data transfer and after online transfer to SAP APO. This setting has a negative effect on performance during the initial data transfer. Therefore, you should check whether your business process actually requires this setting. For example, a retransfer after the initial data transfer is not required if you only want to carry out optimization in SAP APO after the initial data transfer.
    5. Retransfer only after online transfer

Please let me know if this helps.

Regards

Ashutosh Shende

0 Kudos

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

Former Member
0 Kudos

HI;

I think it is CCR Issue for the Consistency check with data base.

Regards;

A.S.KUMAR

0 Kudos

Thanks ARAVA,

But there is no issue in CCR and no inconsistency found during consistency check.

Thanks & Regards,

Anubrata Bhattacharya

marianoc
Active Contributor
0 Kudos

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

Former Member
0 Kudos

Hi Mariano,

These solutions are really old stuff (release 3.1 and 5.1)!

Thanks, Marius

marianoc
Active Contributor
0 Kudos

Hi Marius,

The OSS note just provide the BAdI description. The idea is to explore the BAdI and check if he can control this bahviour.

Kind Regards,

Mariano

0 Kudos

Thanks Mariano,

It is really helpful and I am trying to implement BADI and lets see what will happen.

0 Kudos

Thanks Maius for the reference.

I found the note 161028 is helpful but I would like to add that we are using PPDS heuristics not SNP heuristics. So there is no question of SNP planned order.

Thanks and Regards

Anubrata Bhattacharya

Former Member
0 Kudos

Hello,

Please read with more attention. This note is exactly for pl.orders generated by PPDS (not for SNP)!

Thanks, Marius


Former Member
0 Kudos

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