SAP SLVC_CHOMP_RENDERER_TABLES Function Module for
SLVC_CHOMP_RENDERER_TABLES is a standard slvc chomp renderer tables SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for slvc chomp renderer tables FM, simply by entering the name SLVC_CHOMP_RENDERER_TABLES into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLVC_WIN_EXPORT
Program Name: SAPLSLVC_WIN_EXPORT
Main Program: SAPLSLVC_WIN_EXPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SLVC_CHOMP_RENDERER_TABLES pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'SLVC_CHOMP_RENDERER_TABLES'".
EXPORTING
IT_OUTPUT_FILES = "
IS_ALV_BDS = "Structure for BDS Template List Display
IT_MIME_MAPPING = "ALV: Mime Mapping
* I_OBJECTKEY = "Business Document Service: Object Key
IMPORTING
E_URL = "URL
E_OBJECTKEY = "Business Document Service: Object Key
TABLES
IT_BINARY = "Contains MIME data for WWW client
IT_TEXT = "Contains HTML for WWW client
EXCEPTIONS
ERROR = 1 BDS_ERROR = 2 TABLE_FORMAT_ERROR = 3
IMPORTING Parameters details for SLVC_CHOMP_RENDERER_TABLES
IT_OUTPUT_FILES -
Data type: LVC_T_FILSOptional: No
Call by Reference: Yes
IS_ALV_BDS - Structure for BDS Template List Display
Data type: LVC_S_BDSOptional: No
Call by Reference: Yes
IT_MIME_MAPPING - ALV: Mime Mapping
Data type: LVC_T_MIMAOptional: No
Call by Reference: Yes
I_OBJECTKEY - Business Document Service: Object Key
Data type: BDS_OBJIDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SLVC_CHOMP_RENDERER_TABLES
E_URL - URL
Data type: CHAR1024Optional: No
Call by Reference: Yes
E_OBJECTKEY - Business Document Service: Object Key
Data type: BDS_TYPEIDOptional: No
Call by Reference: Yes
TABLES Parameters details for SLVC_CHOMP_RENDERER_TABLES
IT_BINARY - Contains MIME data for WWW client
Data type: W3MIMEOptional: No
Call by Reference: Yes
IT_TEXT - Contains HTML for WWW client
Data type: W3HTMLOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BDS_ERROR - Not supported
Data type:Optional: No
Call by Reference: Yes
TABLE_FORMAT_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SLVC_CHOMP_RENDERER_TABLES Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_error | TYPE STRING, " | |||
| lv_e_url | TYPE CHAR1024, " | |||
| lt_it_binary | TYPE STANDARD TABLE OF W3MIME, " | |||
| lv_it_output_files | TYPE LVC_T_FILS, " | |||
| lt_it_text | TYPE STANDARD TABLE OF W3HTML, " | |||
| lv_bds_error | TYPE W3HTML, " | |||
| lv_is_alv_bds | TYPE LVC_S_BDS, " | |||
| lv_e_objectkey | TYPE BDS_TYPEID, " | |||
| lv_it_mime_mapping | TYPE LVC_T_MIMA, " | |||
| lv_table_format_error | TYPE LVC_T_MIMA, " | |||
| lv_i_objectkey | TYPE BDS_OBJID. " |
|   CALL FUNCTION 'SLVC_CHOMP_RENDERER_TABLES' " |
| EXPORTING | ||
| IT_OUTPUT_FILES | = lv_it_output_files | |
| IS_ALV_BDS | = lv_is_alv_bds | |
| IT_MIME_MAPPING | = lv_it_mime_mapping | |
| I_OBJECTKEY | = lv_i_objectkey | |
| IMPORTING | ||
| E_URL | = lv_e_url | |
| E_OBJECTKEY | = lv_e_objectkey | |
| TABLES | ||
| IT_BINARY | = lt_it_binary | |
| IT_TEXT | = lt_it_text | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| BDS_ERROR = 2 | ||
| TABLE_FORMAT_ERROR = 3 | ||
| . " SLVC_CHOMP_RENDERER_TABLES | ||
ABAP code using 7.40 inline data declarations to call FM SLVC_CHOMP_RENDERER_TABLES
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects