Skip to Content

Reservations cleared even if COGI errors exist

Here the situation.

I have an order for 10, sent this to ME via MEINT. I have material that is to be consumed at op1, for a total of 10, stock qty is 8. I consume at op1, complete at op1, and move to op2. I complete at op2. Completion of production order sent across with clear_res set to X, FIN_COMP set to 1. MEINT processes everything fine, however I didn't have enough stock so we get an COGI error. The production order is confirmed and closed with qty of 10, and reservations are released. We do not want the reservations to release because we got a COGI error. How do we stop the release of the reservations if we get COGI errors?

Thanks

Rusty

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Feb 22, 2016 at 04:25 PM

    Hi Rusty,

    What about using CT520 hook point at pre_complete? With this you can make sure that the needed Qty is assembled at the operation and no COGI error would happen.

    Br, Alex.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Rusty,

      Then could you please share the confirmation message sent from ME as well as the error on ERP side?

      I wonder whether function module CO_MES_PRODORDCONF_CREATE_TT is used in the scenario as per Note 1555198.

      Br, Alex.

  • Feb 23, 2016 at 04:17 PM

    Here's the original problem from OSS note

    ME/MII sent confirmation with quantity of zero with unknown reason.

    ME/MII keeps sending confirmation with quantity "0" to ECC once operator confirmed all operations with full yield quantity.

    This dummy confirmation with quantity "zero" will set FINAL GI indicator as per OSS note 540392 #14, regardless whether there is outstanding COGI errors.

    Message was edited by: Alexander Teslyuk

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 23, 2016 at 04:26 PM

    Add comment
    10|10000 characters needed characters exceeded