Web item Custom Extension allows you to display your own HTML. You do this by creating an ABAP class that implements the relevant properties and parameters from ABAP interface IF_BICS_CONS_WEBITEM_CUST_EXIT. More information: ABAP Interface IF_BICS_CONS_WEBITEM_CUST_EXIT
ABAP class CL_BICS_CONS_WEBITEM_CUST_EXIT implements the above-mentioned interface. Complex Example: Displaying the XML of Two Data Providersuses this ABAP class More information: Complex Example: Displaying the XML of Two Data Providers
Creating an ABAP Class
You can also use the Object Navigator from the ABAP Workbench (transaction SE80) to generate a class. More information: Object Navigator
Debugging the ABAP Class
For test purposes, you can debug the ABAP class. As the ABAP class is called implicitly by the Java-based BEx Web runtime (and not in the SAP GUI or using an http request), the ABAP class can only be debugged if its internal system state is displayed in the form of messages.
To display these messages in a BEx Web application, use function module RRMS_MESSAGE_HANDLING. You can use generic message BRAIN 143 ("Technical Information: &1&2&3&4") here to display up to four parameters. You can also use any other message of your choice:
CALL FUNCTION 'RRMS_MESSAGE_HANDLING' EXPORTING I_CLASS = 'BRAIN' I_TYPE = 'S' I_NUMBER = '143' I_MSGV1 = sy-msgv1 I_MSGV2 = sy-msgv2 I_MSGV3 = sy-msgv3 I_MSGV4 = sy-msgv4.