PO resulting from PR is getting struck SMQ1 R/3

[Former Member]

Hi All,

Currently we are in ECC 5.0 & APO 5.1

Here we are converting Subcontracting Purchase requisition to Subcontracting Purchase order through MD04. Here in R/3 it is converting properly but the replication of the same to APO is failing with a Queue error 'Exception condition"Source_Invalid" raised' at R/3 outbound.

Kindly revert back ASAP.

Edited by: venkat1215 on Jul 20, 2010 12:35 PM

[Former Member]

issue is closed.

Regards,

Venkat

[Former Member]

Hi All,

we solved this issue,we didn't check location of that material.

Thanks to all for giving valuable answers.

Regards,

Venkat.

[Former Member]

Hi Venkat,

What is the procurement type of the material in APO--- E or F or X

Reason for error: For a SUBCON PO created in ECC, when sending it from ECC to APO, in APO, there is an internal planned order created with the same SUBCON PO#, For this internal planned order, the source of supply is a PDS or a PPM.

To check the internal planned order:

(1) go to RRP3

(2) Select any past SUBCON PO and click on CONTEXT icon on the top

2 ways of solving the problem:

(1) Create a valid PPM or a PDS for this product location and then create and send a new SUBCON PO. It should go over to APO

(2) To solve your problem without creating any PDS or PPM, set your procurement type to F and send a new SUBCON PO

Let us know if you still have problems

Thanks

Kumar

[Former Member]

Hi ,

Please check if the subcontracting PR is having valid source.

When PR goes to SAP ECC, it must be caputring the source automatically.

However, in APO if there are invalid sources ( i.e. transaportation lanes created automatically from the external procurement relationships but the contracts are not valid).

Regards

Datta

[Former Member]

Hi Venkat,

Please check on the following

1) Check whether the source of supply is maintained correctly

2) Check the purchase info record of the item whether

maintained properly

3) Check is there any line item whose schedule lines are

deleted by users or having different storage locations

4) Check the application log generated to determine the

exact error

5) Check valid integration model exists

Regards

R. Senthil Mareeswaran.