Skip to Content

LSMW with BAPI Method | Error B1500 "The IDoc interface is not complete for message type &"

Hello,

our goal is to mass update the eMail-Adress for SAP user (SU01) as this is prohibited by SU3 (SAP rules).

We have "successfully" created a LSMW Project following blog of Jürgen (LINK) using:

  • BAPI method "BAPI_USER_CHANGE"
  • BusinessObject "USER"
  • Message type (IDOC) "USERCHANGE"

Problem:

Every step in LSMW could be executed w/o failure EXCEPT step 14 (execute IDOC - see Screenshot1)

  • IDOC was execution was canceled with Error status 51
  • Error message: B1500 "The IDoc interface is not complete for message type &"

Question:

does anyone know what could be the source of this error?

kind regards
Jörg

-----------------------------------------------------------------------------------------------------------------

Screenshot1 (LSMW)

Screenshot2 (WE21)

Screenshot3 (WE20)

syrrc.png (44.5 kB)
xwc0t.png (30.0 kB)
b3oab.png (27.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jan 17 at 02:25 PM

    Hello, Jörg

    It appears BAPI > ALE interface is not fully implemented.
    While you can proceed and add the message type USERCHANGE to the Inbound Process code BAPI in the WE42 transaction. You'll see that in Transaction WE57 that the FM BAPI_IDOC_INPUT1 is assigned for the message type USERCHANGE / USERCHANGE01. However

    it still will not work.

    When you run the consistency check for the BAPI-ALE interface in transaction BDBG the processing function module to execute the IDOC posting as defined in table TBDBE, hasn't been created. The Check consistency shows tat the "The function module IDOC_INPUT_USERCHANGE does not exist yet.". This is the root cause.

    As the object is in the SAP namespace a correction/generation of the interface and function modules would require a repair. Best course of action would be to either (a) Create a BDC recording of SU01 transaction as a LSMW project and map your source data for the updates or (b) copy the BOR object USER in SWO1 and create the BAPI ALE interface in the customer name space. The BAPI transaction project tab provides a wizard for these option (b) steps.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 10, 2018 at 02:59 PM

    Hello, Jörg,

    I think I'd check the process code that is used here, that is BAPI. Open its definition in transaction WE42 ( or by doubleclicking on it in your Inbound parameter screen). Make sure the FM that is attached to this process code (field Identification) exists. In my system the FM is BAPI_IDOC_INPUT1 (but I think I have older SAP version than you)

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 17 at 02:26 PM

    Meanwhile SAP Basis found "SAP Standard mass maintenance function" (SU10) and took over this reuqest :-)

    Add comment
    10|10000 characters needed characters exceeded