Related questions

3 Answers

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.

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)