SAP IDOC_TAB_GENERATE_HTML Function Module for









IDOC_TAB_GENERATE_HTML is a standard idoc tab generate html 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 idoc tab generate html FM, simply by entering the name IDOC_TAB_GENERATE_HTML into the relevant SAP transaction such as SE37 or SE38.

Function Group: EDID
Program Name: SAPLEDID
Main Program: SAPLEDID
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function IDOC_TAB_GENERATE_HTML 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 'IDOC_TAB_GENERATE_HTML'"
EXPORTING
IDOC_TYPE = "IDoc Type
* RELEASE = SY-SAPRL "SAP Release
* VERSION = '3' "
* DOCU_SETTINGS = "

CHANGING
* FILE = "

TABLES
IDOC_STRUCT = "
SEGMENTS = "Segments
SEGMENT_STRUCTURE = "Segment structures
TEXT_FRAMESET = "
TEXT_INDEX = "
TEXT_DOCU = "

EXCEPTIONS
INTERNAL_ERROR = 1 ILLEGAL_STRUCT_TYPE = 2
.



IMPORTING Parameters details for IDOC_TAB_GENERATE_HTML

IDOC_TYPE - IDoc Type

Data type: LEDID_IDOC_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

RELEASE - SAP Release

Data type: SY-SAPRL
Default: SY-SAPRL
Optional: Yes
Call by Reference: No ( called with pass by value option)

VERSION -

Data type: EDI_VERREC-VERSION
Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOCU_SETTINGS -

Data type: EDI_USR
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for IDOC_TAB_GENERATE_HTML

FILE -

Data type: CHAR70
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for IDOC_TAB_GENERATE_HTML

IDOC_STRUCT -

Data type: LEDID_T_IDOC_STRUCT
Optional: No
Call by Reference: No ( called with pass by value option)

SEGMENTS - Segments

Data type: LEDID_T_SEGMENT
Optional: No
Call by Reference: No ( called with pass by value option)

SEGMENT_STRUCTURE - Segment structures

Data type: LEDID_T_SEGMENT_STRUCT
Optional: No
Call by Reference: No ( called with pass by value option)

TEXT_FRAMESET -

Data type: LINE
Optional: No
Call by Reference: No ( called with pass by value option)

TEXT_INDEX -

Data type: LINE
Optional: No
Call by Reference: No ( called with pass by value option)

TEXT_DOCU -

Data type: LINE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INTERNAL_ERROR - Internal Error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ILLEGAL_STRUCT_TYPE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for IDOC_TAB_GENERATE_HTML 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_file  TYPE CHAR70, "   
lv_idoc_type  TYPE LEDID_IDOC_TYPE, "   
lt_idoc_struct  TYPE STANDARD TABLE OF LEDID_T_IDOC_STRUCT, "   
lv_internal_error  TYPE LEDID_T_IDOC_STRUCT, "   
lv_release  TYPE SY-SAPRL, "   SY-SAPRL
lt_segments  TYPE STANDARD TABLE OF LEDID_T_SEGMENT, "   
lv_illegal_struct_type  TYPE LEDID_T_SEGMENT, "   
lv_version  TYPE EDI_VERREC-VERSION, "   '3'
lt_segment_structure  TYPE STANDARD TABLE OF LEDID_T_SEGMENT_STRUCT, "   
lv_docu_settings  TYPE EDI_USR, "   
lt_text_frameset  TYPE STANDARD TABLE OF LINE, "   
lt_text_index  TYPE STANDARD TABLE OF LINE, "   
lt_text_docu  TYPE STANDARD TABLE OF LINE. "   

  CALL FUNCTION 'IDOC_TAB_GENERATE_HTML'  "
    EXPORTING
         IDOC_TYPE = lv_idoc_type
         RELEASE = lv_release
         VERSION = lv_version
         DOCU_SETTINGS = lv_docu_settings
    CHANGING
         FILE = lv_file
    TABLES
         IDOC_STRUCT = lt_idoc_struct
         SEGMENTS = lt_segments
         SEGMENT_STRUCTURE = lt_segment_structure
         TEXT_FRAMESET = lt_text_frameset
         TEXT_INDEX = lt_text_index
         TEXT_DOCU = lt_text_docu
    EXCEPTIONS
        INTERNAL_ERROR = 1
        ILLEGAL_STRUCT_TYPE = 2
. " IDOC_TAB_GENERATE_HTML




ABAP code using 7.40 inline data declarations to call FM IDOC_TAB_GENERATE_HTML

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.

 
 
 
 
"SELECT single SAPRL FROM SY INTO @DATA(ld_release).
DATA(ld_release) = SY-SAPRL.
 
 
 
"SELECT single VERSION FROM EDI_VERREC INTO @DATA(ld_version).
DATA(ld_version) = '3'.
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!