Skip to Content
Actions

Delivery Complete Indicator of PO and Goods Receipt

December 31, 2009 | 3,310 Views |
 enterprise resource planningsap erp logistics materials management
Follow

Before ECC 6.0 Enhancement Package 4, the system logic has been explained in notes below:

SAP Note No. 1093582

1. Question

Which effects has the “delivery completed” indicator?

Answer

  • Although a further delivery is not expected, it is still possible.

SAP Note No. 856279
  • However, another delivery up to the purchase order quantity (including overdelivery tolerance) is still possible.

From both notes, the system logic is that the “Delivery completed” indicator specifies whether a purchase order item is considered closed. This means that no more goods receipts are EXPECTED for this item. If the delivery completed indicator is set, the open purchase order quantity becomes zero, even if the full quantity has not been delivered. It is still possible to post goods receipts of remaining quantities, but these no longer change the open purchase order quantity.

There were a few of doubts regarding the functionality of DCI (delivery complete indicator). One common opinion is if the DCI is set for the purchase order, the further GR should be prevented. Originally in this circumstance, the workaround is to block the line item in PO. You can set the blocking indicator by selecting the item and then
choosing Edit -> Block if you do not want to allow subsequent functions for the item.

As of ECC 6.0 Enhancement Package 4, the Enhancement Spot MB_GOODSMOVEMENT has been extended. There is new BADi MB_GOODSMOVEMENT_DCI which could be implemented to check DCI and issue M7344.

image

There is already SAP standard implementation:

image

The codings are:

image

In customizing transaction OMCQ, set message M7433 as “E”:

image

Now if doing GR for a PO which has DCI set, there will be error M7433 to prevent the GR:

image

This new functionality of EhP4 makes it possible to control the GR by according to DCI.

To report this post you need to login first.

14 Comments

You must be Logged on to comment or reply to a post.

  1. Warren Nash
    Good blog Jimmy.  So many people out there are very frustrated with SAP functionality.  As I believe the indicator is only used to update the status of the PO, rather than not to allow future GR’s.

    Regards

    Warren Nash

    (0) 
      1. Raviraj sharma
        Very  Useful Blog,  This  issue  has even left me red – faced in front of a client.  we too had to  implement the BADI with out own logic  earlier. guess now we can use this  solution.

        -Raviraj

        (0) 
  5. Vijay Deshpande

    Dear Jimmy,

    It’s really useful information.

    So many consultants and Business uers are confused about this functionality. They misunderstood the SAP intention thereby leading to frustration about incorrect usage of this.

    Hope this new change servers our customer better

    Thanks for nice explanation

    Vijay

    (0) 
  11. Lin Carol

    Hi Jimmy,

    I check and makesure we have the new BADI: MB_GOODSMOVEMENT_DCI and set M7433 that you talk about. But it doesn’t work in my system (ECC6.0 ehancement 4). Did you know what item I should check again? In fact, I send incident to SAP and they asked me to follow snote.1316983

    I want to know if I have new BADI: MB_GOODSMOVEMENT_DCI in my system. Do I still need to follow snote.1316983 to create an Z* customer exits.

    Regards,

    Carol Lin

    (0) 
  12. Narayana N

    Hi Jimmy Zhang,

    We have implemented this and found working fine for forward transactions. But when we try to cancel the GR, system gives the same error message M7433. Is there any solution in standard SAP, apart from writing logic in the BADi?

    Thanks,

    Narayana N

    (0) 

Leave a Reply