Sap APO Message no. /SAPAPO/CIF168 Error 168 from the Reconcile report CCR CIF_DELTAREPORT3

[Former Member]

Hi,

/SAPAPO/CCR - CIF_DELTAREPORT3

Could you please help us with this issue we are facing all the time when changing process orders from CM25 in ECC.

No issue when doing It in tr. COR2 but instead CM25

It seems that came up after our upgrade to EHP8 in ECC and APO EHP4

We have try to locate the error normally in SLG1 but without any luck, it just went through both systems without any further error details and placed in CCR to updated from there.

It`s a big bussines flow for production that should run smoothly and not be updated manually.

Could you share some experience I will be gratefull.

Thanks in advance

Best regards

Claus

[Former Member]

Hi,

Yes normally we change the dates and the order qty from the planning board.

Steps:

Thats means we are changing the order by pressing the icon with the pen and then jump into COR2 where we can change the qty and dates and then push the buttom "Scheduling".

There`s no "Save" in there for COR2 so we have to go one step back into CM25 and then push save in the overview, which means that we can do It for several orders and confirm the result by their end with pressing "Save" for all orders.

Yes! We did this correction for a long time which Sap recomended on that time. And this is still active in the system.

/SAPAPO/CL_EX_CIF_IP

Planned/process orders: Determine order dates in CCR

OSS message 445045 / 2012.

Best regards

Claus

[rupesh_brahmankar]

Hello,

If it was working before then it should also work now. It may be due to upgrade.

As you are changing an order in your ERP system but the APO system does not trigger a re-explosion of the order.

Please have a look on these SAP notes

793626 - Maintaining scheduled status in APO

2181954 - Maintaining scheduled status in APO after re-explosion

1559394 - PDS re-explosion after a change in the ERP system

The BAdI method suggested by note 793626 should be de-activated.

The new solution contains the old logic and the code which considers the re-explosion.

Implement a BAdI in SAP APO. Follow the steps below:

1. Start transaction SE19 in SAP APO.

2. Enter an implementation name and choose Create.

3. Enter a short text.

4. Enter "/SAPAPO/CL_EX_CIF_IP" as a definition name and choose Save. Select a customer-specific package that ensures transport in accordance with the requirements of your system landscape.

5. Go to the Interface tab.6. Double-click the "ORDER_INB_MODIFY_AFTER_MERGE" method.

7. Implement the enhancement source code in accordance with the correction instructions from note 2181954.

8. Save and activate the enhancement source code.

9. Press F3 to go back.

10. Activate the enhancement.

Or you can open a message to SAP.

Best Regards,

R.Brahmankar