Could DN(delivery note) be requirement rather than receipt?

[gino_zhu]

Hi, All,

I have problem when using subcontractor location funcationality with SCM5.0.

The issue is caused by the way of using DN. In my case, DN is created in ECC side via VL31N and passed to APO as PO memo. Actually DN is used as kind of purchasing document in this way which means when DN created nothing happen yet. So there are still requirements for component from this DN for subcontractor.

While unfortunately in SAP standard design, DN means goods ready but not delivered yet and also means the requirements has been fulfilled before DN creation.

Since the way of using DN can not be changed, is there any technical way to keep the corresponding requirements after passing to APO?

Any ideas, highly appreciated!

[srinivas_krishnamoorthy · Accepted solution]

Based on my experience, departing from SAP design will bite you in the foot moving ahead. From the text of the Q, it looks that the delivery note is more of a order status rather the receipt element. I am not sure exactly the reason why want DN to be a requirement rather than receipt. If you do, then CIF user exits can be explored to map to appropriate ATP category in APO side. In our design DNs are like PO memos (ASNs) and continues to be in receipt side under TLB confirmed KF (for PO). This creates a requirement automatically from the supplying location.