CIF Error - Doubled Input/Output Nodes

[Former Member]

Hi All,

Has anyone seen this error when trying to CIF over Purchase Orders:

'Doubled input/output nodes.

Order type 2 order number 4500.... Method

Follow Up error

Thanks

Rob

[Former Member · Accepted solution]

Hi,

Pl try the OSS notes below.

Note 1340400 - CIF purchase orders: double input/output nodes [2]

1339783 - CIF purchase orders: double input/output nodes

Regards,

Senthilrajan

[Former Member · Accepted solution]

This was implemented and it did not work.

[Former Member]

Hi,

Hi check in queue purchase orders for normal purchase order check whether transportation lane exists in APO from vendor to plant and in case of stock transfer orders check if transportation lane is there between supplying and destination plant.

As we can create Stock transfer orders manually in R/3/ECC without info record but in APO we need to have transportation lane.

[Former Member]

I checke the transportation lanes and they were created.

I also implemented the suggested OSS note and it still did not work.

[Former Member]

Hi,

What did you do to fix this error?

Thanks a lot.

Ria

[Former Member]

Hi Rob,

I have the same issue: When Cifing the PO/PR i'm getting the error "Order type 2 Order number xxxxxxxxxxx Method". Can you please provide us how this issue was fixed. It will be very helpful.

Regards

KRN

Edited by: KRN on Oct 14, 2010 3:48 PM

[Former Member]

Dear SAP Colleagues,

I have also encountered this issue.

Actions that I have done:

- checked the logs and identified the orders that were causing the error.

- checked TL = existing

Kindly provide next steps.

Thank you.

Boi001

[Former Member]

Hi Rob,

Identify the purchase order No/Stock transfer order number

for the item through application logs and check the accuracy

of the order.

If any errors needs to be corrected. There are incorrect

entries due to dual processing of these purchase orders.

Also try resetting the queues and check

Regards

R. Senthil Mareeswaran.

[Former Member]

thanks senthil,

same issue faced and solved.