ABAP handler creation

For each IDoc object definition that you develop, you must support it by developing a custom ABAP handler.

You can use either standard IDocs or custom IDocs for the Advanced event processing interface. After defining the custom IDoc for an integration scenario, create an ABAP handler (function module) for each operation of the business object that must be supported.

Each function should have the following interface to ensure that adapter can call it: 
*" IMPORTING
*" VALUE(OBJECT_KEY_IN) LIKE /CWLD/LOG_HEADER-OBJ_KEY OPTIONAL
*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD OPTIONAL
*" VALUE(LOG_NUMBER) LIKE /CWLD/LOG_HEADER-LOG_NR OPTIONAL
*" EXPORTING
*" VALUE(OBJECT_KEY_OUT) LIKE /CWLD/LOG_HEADER-OBJ_KEY
*" VALUE(RETURN_CODE) LIKE /CWLD/RFCRC_STRU-RFCRC
*" VALUE(RETURN_TEXT) LIKE /CWLD/LOG_HEADER-OBJ_KEY
*" TABLES
*" IDOC_DATA STRUCTURE EDID4
*" LOG_INFO STRUCTURE /CWLD/EVENT_INFO
The following table provides information about the parameters:
Table 1. Interface parameters
Parameter Description
OBJECT_KEY_IN Should be no value.
INPUT_METHOD Indicates whether the IDoc should be processed in a dialog (that is, through Call Transaction).
Possible values are:
  • " " - Background (no dialog)
  • "A" - Show all screens
  • "E" - Start the dialog on the screen where the error occurred
  • "N" Default
LOG_NUMBER Log Number.
OBJECT_KEY_OUT Customer ID returned from the calling transaction.
RETURN_CODE
  • 0 - Successful.
  • 1 - Failed to retrieve.
  • 2 - Failed to create, update, or delete.
RETURN_TEXT Message describing the return code.
IDOC_DATA Table containing one entry for each IDoc data segment.
The following fields are relevant to the inbound function module:
  • Docnum - The IDoc number.
  • Segnam - The segment name.
  • Sdata - The segment data.
LOG_INFO Table containing details regarding events processed with either a success or error message.