cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to do the (CCR in APO) comparison/reconciliation of transaction data PO and PR in APO

Former Member
0 Kudos

 

Hi Gurus,

Unable to do the (CCR in APO) comparison/reconciliation of transaction data PO and PR in APO Due to the error 181-Schedule line does not exist in APO ,Error code 182-Schedule line without external number does not exist in R/3.

kindly suggest me ,what we need to do corrective action from ECC side and APO side.

Regards,

Babu

Accepted Solutions (0)

Answers (2)

Answers (2)

ravi_malpani
Active Participant
0 Kudos

Hi Babu,

As rightly pointed by Sourabh, most of the errors will get reconciled automatically.

Error 181: When you select the order and click on "Push to APO", if the entry vanishes from CCR then note that the Preq would appear as firmed in APO (with application PPDS).

Error 182: Most common reason is wrong master data in R3. Eg. Material does not exist at the source plant defined by source list or Material is blocked for planning at source plant or Matl master maintenance is not complete at source plant. You can identify the reason from the error queue you will see in SCM queue manager.

Regards,

Ravi

sourabh_jain66
Active Contributor
0 Kudos

Hi Babu,

First make sure that order is not set with deletion flag, you can check some random orders for this.

Steps to be followed:

1) for all entries with error "181-Schedule line does not exist in APO" click on "Send to APO". similarly for entries with error "182-Schedule line without external number does not exist in R/3" click on "Send to R/3", most likely this type of issue get resolved with this step only, if not.


2) Next you need to go to transaction code /n/sapapo/cq, check what all messages you are getting there. Correct the error if you are able to understand it from here i.e. rfc connection is not set, no active IM exists etc..


3) In case you are not able to understand or correct the issue from CQ, then you need to go and check in transaction code CFG1 in ECC, and /n/sapapo/c3 in APO, check in ECC with object CIF and log class "only very important logs".


In APO object "CIFSCM" and log class "only very important logs".

Most probably you will be able to get exact or directional reason of the issue.

Hope this helps.

Rgds

Sourabh