CCR: Planned Orders: Error # /SAPAPO/CIF161

[Former Member]

G'day Team,

The end client I am working with has CCR error # : /SAPAPO/CIF161."Order XXX difference for receipt date: 24.05.2010 23:59:59(APO) <-> 24.05.2010 08:29:06"

The client is utilising SNP PDS with a duration of one day; hence NO PP/DS PDS. I had checked on OSS Notes and found note 815509 - Activation of comparison of order end date for planned order.

This was applied to DEV and tested and worked ok.

In the "T" system the number of planned orders increases daily as the ECC Dates are matched, but times are different.

ALL masterdata has been checked and is OK (NB: Client utilises Master Recipes & Prod Versions).

Can any SDN team advise whether there is other OSS to apply, or can recommend use of CIFDelta3 to BADi out the error message 161 as a superfluous error?

Our SNP Go-live in next few weeks so rapid response appreciated.

Many thanks,

Andy Gosling

SAP APO SNP CIF Consultant

[Former Member · Accepted solution]

Hi Andy Gosling,

Could you check whether OSS note 453244 is applicable to

fix your issue. (check also the related notes under this note)

Regards

R. Senthil mareeswaran.

[Former Member · Accepted solution]

G'day Sentil,

Thanks for your prompt response. I meant to add in the original Question that the client is using APO SCM 7.0 and neither of these OSS Notes are applicale for release.

The other info I meant to add is when Error #161 is rectified by Send to ECC... The Planned order is NOT transferred to ECC and not updated with APO Date_Time.

Any other thoughts? BADI on the CIFDELTA3?

Andy Gosling

[Former Member · Accepted solution]

Hi,

I meant to add in the original Question that the client is using APO SCM 7.0 and neither of these OSS Notes are applicale for release.

Most of the BADI and UserExit notes are release independent, so you can implement them or ask SAP to up-port the note.

The other info I meant to add is when Error #161 is rectified by Send to ECC... The Planned order is NOT transferred to ECC and not updated with APO Date_Time.

Please check if the queue is stopped in R/3 inbound.

Any other thoughts? BADI on the CIFDELTA3?

Methods in BADI /SAPAPO/CIF_DELTA3 can be used based on your requirements. Are the end dates of orders really different or CCR is wrongly showing the error?

Regards,

Chirag

[Former Member · Accepted solution]

G'day Chirag,

The ECC6 (R/3) queue is Not stopped inbound to ECC... I am utilising the /SAPAPO/CQ and all queues are clear & active.

I understand the BADi's are avail in the release SCM7.0 and wonder if you have direction on which BADi to aply.. is it CIFDELTA3 or a diff BADi..

The client would not normally expect error as Sceduling in ECC6 in Fixed horizon (APO terms: PP/DS horizon) and the planned orders in Future (SNP horizon) are too far out to schedule to Time... AGAIN the dates are primarily OK. ie: they match ECC & APO.

PldOrder end dates are in discrepancy between APO & ECC... mainly on time only.

Look forward to feedback soonish,

Andy Gosling

SAP APO SNP CIF Consultant

[Former Member · Accepted solution]

Hello Andy,

You can use Method RELEVANT_FOR_COMPARE_R3_ORDER of BADI CIFDELTA3.

In this method structure CS_COMP has information regarding the things which need to be compared. So for instance if you donot want CCR to compare end dates you can write "CLEAR cs_comp-order_end_date." inside this method.

The table CT_R3_ORDER has information regarding the orders to be compared. So, probably based on the information in this table you can switch off the comparison for order end dates/due date.

Regards,

Chirag