Every ABAP handler must implement the same function module interface. The function module interface guarantees that the business object router Y_XR_RFC_DO_VERB_NEXTGEN can pass business object data to and from ABAP handlers. The interface is:
*"*"Local interface: *" IMPORTING *" VALUE(PROC_FUNC_1) LIKE RS38L-NAME OPTIONAL *" VALUE(PROC_FUNC_2) LIKE RS38L-NAME OPTIONAL *" VALUE(OBJECT_NAME) LIKE YXR_LOG_H-OBJ_NAME OPTIONAL *" VALUE(OBJECT_VERB) LIKE YXR_CHANGE-OBJ_VERB OPTIONAL *" VALUE(ARCHIVE) OPTIONAL *" VALUE(TEXT) LIKE T100-TEXT OPTIONAL *" EXPORTING *" VALUE(RETURN_TEXT) LIKE YXR_EVENT-OBJ_KEY *" VALUE(RFCRC) LIKE YXR_RFCRC-YXR_RFCRC *" TABLES *" RFC_STRUCTURE STRUCTURE YXR_RFC_S *" EXCEPTIONS *" NOT_FOUND *" ERROR_PROCESSING
In the importing section of the interface, you can communicate values such as the ABAP handler name, business object name, and business object.
The exporting section of the interface is used to communicate the results of the ABAP handler processing. The return code RFCRC parameter is a single field used to determine the code a connector returns. The possible values are:
RC = 0 (success, VALCHANGE)
RC = 1 (failure, FAIL)
The RETURN_TEXT parameter is a 120-character free text field that is written to by the connector or logged as an error message in the return status descriptor. If the ABAP handler does not provide a value for this parameter, then Y_XR_RFC_DO_VERB_NEXTGEN supplies default text depending on the return code.