Skip to Content
-1

BDC is Saving Production Order In spite of errors (CO11N)

Hi Experts,

I have recorded BDC for CO11N, But it not exiting on the error messages.

Means in tcode if any error is coming, it is not allowing to save the order. but in BDC in spite of error it saving the order.

Any kind of help will be appreciated.

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    May 18, 2017 at 12:34 PM

    I have solved the problem.

    Goto V_160M table and Changed Warning & Information messages to Error.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 12, 2017 at 07:05 PM

    It cannot happened..! you might be missing something here..

    Add comment
    10|10000 characters needed characters exceeded

  • May 15, 2017 at 05:19 AM

    Read OSS note 1999131 - Batch input has problem for CO11 and CO11N

    Add comment
    10|10000 characters needed characters exceeded

  • May 15, 2017 at 05:23 AM

    CO11N Behavior: If error in goods movement(due to any reason), then standard is NOT allowing us to save the order.

    BDC Behavour : In return table throwing messages as error goods movement, order saved.

    I have tested in 'A' mode but it is saving the order in-spite of errors.

    Add comment
    10|10000 characters needed characters exceeded

  • May 15, 2017 at 05:36 AM

    Right now i don't have note access. Please see the screen shot.

    What check boxes should i need to check.

    Add comment
    10|10000 characters needed characters exceeded

    • An Excerpt from OSS Note 1999131:

      "

      Resolution

      We would recommend you using the BAPI BAPI_PRODORDCONF_CREATE_TT (BAPI_PROCORDCONF_CREATE_TT for process order) for batch input.

      However, if you do need to work with transaction code SHDB, you could specify the system to work with the CALL TRANSACTION mode by setting the checkbox 'Not a Batch Input Session'. In this case, the system does the confirmations in the dialog mode. The pop-up will not be prevented in this case. You may also consider setting the BDC Option Parameter (nobabinpt) when calling BDC records."