any available BADI for Delta Report correction in SAP APO?

[Former Member]

Dear Experts,

I hope you can help us on this topics:

we implemented successufully ZXCIFUSERU09 in SAP APO in order to change the location of certain PO we are transferring from R3 to APO. This is mainly needed to avoid to create in APO all the plants we are using in R3 for performance/sizing reason.

Now we are trying to apply the same logic in delta report too in order to be sure delta report will give us only the real exception and not the list of orders where via exit ZXCIFUSERU09 we changed the location.

This is to avoid delta report is showing inconsistency that are not

true .

Dop you have any idea wich is the correct exit in APO we can use to do that? we tried with method RELEVANT_FOR_COMPARE_R3_PO but this called after the comparison with R3 data have been already done and so it cannot help us.

Thank you in advance for your feedback,

Barbara

[Former Member]

Hello DB49,

thank you for your answer we have further investigated and we think the issue is in method

RELEVANT_FOR_COMPARE_R3_PO

where structure CT_APO_ORDER is empty . Do we need to add the data in this table as per your experience with other similar methods ro not?

We tried to add the data and result is that the comparison is done between the 2 structures:

CT_APO_ORDER and CT_R3_ORDER but for the first schedule line only! it seems a bug as the report is comparing both the lines in CT_APO_ORDER with the same schedule line in CT_R3_ORDER...

Do you think we need to add the data in CT_APO_ORDER or the data sould be already there and we only need to manipulate them?

Based on your reply and our test that I would like to ask SAP to correct the method as it seems a bug.

I also found Note 1363487 - BADI /SAPAPO/CIF_DELTA3 - add parameter CT_APO_ORDER that is confirm the structure CT_APO_ORDER should contain APO po data,....

Thank you very much for your feedback!

regards,

Barbara

[Former Member]

Barbara,

Sorry, but as I said earlier, I am not an ABAPer.

I can say that I have seen comparisons done where a transactional field from R/3 is compared with a similar transactional field in APO, and if they differ in a predefined way, they are excluded from error reporting (This I know, because I generally write the functional specs). I have no idea how the programmers solve the problem (nor do I want to know!). Only after the programmers publish their Technical specs do I become aware of the fact that they used a BADI/method, and which one.

Best Regards,

DB49

[Former Member]

Dear Dogboy49,

we tried to implement the method and we apply the same logic we inserted in exit for PO inbound.

we chage the location of the PO from X to Y.

result is that in the delta report the inconsistency is shown anyway but in location Y instead of location X (even if for us is not true... the inconsistency should not be shown at all neither in location X nor in location Y).

thank you for your feeback.

Barbara

[Former Member]

Barbara,

I have never seen RELEVANT_FOR_COMPARE_R3_PO used, but I have seen similar functionality successfully executed for some of the other methods in that same BADI (such as RELEVANT_FOR_COMPARE_R3_STOCK or RELEVANT_FOR_COMPARE_R3_SLS). I am not an ABAPer, but it sounds like you may have something illogical in your code. This BADI should work, and is designed to support this type of requirement.

Perhaps one of the ABAP experts in this forum will be able to give you more detail.

Best Regards,

DB49

[Former Member]

Barbara,

.....but this called after the comparison with R3 data have been already done 

Where did you get that information? Or more importantly, what makes you think that this method cannot help you?

Best Regards,

DB49