Operation/Phase 0XXX/ is scheduling a non-existent resource (cap. ID 1XXXXXXX) - Message no. /SAPAPO/RRP527

[forecasttoplan_gtproject]

Hi Experts!

We are having problems to integrate production order on APO side when one of the operations has one work center with pooled capacity (which means there is another work center, assigned to a different routing, which uses the same capacity). 

1 – Creation a planned order in APO for a product that has 3 operations and one of them has pooled capacity.

2 – Planned order is successfully integrated in ECC

3 – Then, inside RRP3 we mark this planned order to be converted into a production Order. On ECC side the production order is created.

4 – Then the production order gets stuck in /SAPAPO/CPP tcode during the integration from ECC to APO. The error message displayed on queue:

- Operation/Phase 0XXX/ is scheduling a non-existent resource (cap. ID 1XXXXXXX) - Message no. /SAPAPO/RRP527

- Order 000099999999: Conversion failed - Message no. /SAPAPO/RRP516

As consequence, the production order is never integrated on APO side.

Similar to it, if we create a production order direct on ECC side via CO01, we face the same issue.

The PDS integration is OK! The capacity were integrated in APO as Resource and the Work Center are also correctly integrated.

Does anyone knows how to solve this issue?

Do I have to apply special configuration when we want to work with pooled capacity in APO?

[rupesh_brahmankar3 · Accepted solution]

Hello,

Please run the report /sapapo/change_bsg_resource program directly on APO system

The problem occurs if the work center which is changed is a pool capacity and note 629366 is implemented in system.

Please impalement OSS note    834771 - Operation/Phase x occupies non-existent resource

Best Regards,

R.Brahmankar

[forecasttoplan_gtproject · Accepted solution]

Hello,

We run the report as you recommended (not in test mode), but it seems nothing has changed.

We also checked about the note 629366 and nothing was implemented.

The note 834771 is obsolete and we already implemented note 1048794, which is the updated version.

However none of these points could solve our issue?

Do you have any other recommendation?

Best regards,

[rupesh_brahmankar3 · Accepted solution]

Hello,

I would suggest open an OSS message to SAP.

Best Regards,

R.Brahmankar