TXW_VIEW_SEGMENT_EXECUTE SAP Function module - Execute view for a single segment

TXW_VIEW_SEGMENT_EXECUTE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name TXW_VIEW_SEGMENT_EXECUTE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: TXW5
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM TXW_VIEW_SEGMENT_EXECUTE - TXW VIEW SEGMENT EXECUTE

CALL FUNCTION 'TXW_VIEW_SEGMENT_EXECUTE' "Execute view for a single segment
  EXPORTING
    it_sourcefiles =            " txw_vdt_sourcefile_t  Table of Sourcefiles for a view
    id_tax_view =               " txw_vb_params-tax_view  Data file view
    is_params =                 " txw_vb_params  Parameters for DART Viewbuilder
*   id_tab_num = 0              " i             start number for table generation
  EXCEPTIONS
    NO_AUTHORITY = 1            "               No authority
    INVALID_VIEW = 2            "               View not valid
    SEGMENT_NOT_FOUND = 3       "               Segment not found
    .  "  TXW_VIEW_SEGMENT_EXECUTE

ABAP code example for Function Module TXW_VIEW_SEGMENT_EXECUTE

The ABAP code below is a full code listing to execute function module TXW_VIEW_SEGMENT_EXECUTE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_it_sourcefiles) = 'Check type of data required'.


DATA(ld_id_tax_view) = some text here

DATA(ld_is_params) = 'Check type of data required'.

DATA(ld_id_tab_num) = 'Check type of data required'.
.

CALL FUNCTION 'TXW_VIEW_SEGMENT_EXECUTE'
  EXPORTING
    it_sourcefiles =             ld_it_sourcefiles
    id_tax_view =                ld_id_tax_view
    is_params =                  ld_is_params
*   id_tab_num =                 ld_id_tab_num
  EXCEPTIONS
    NO_AUTHORITY =               1
    INVALID_VIEW =               2
    SEGMENT_NOT_FOUND =          3
    .  "  TXW_VIEW_SEGMENT_EXECUTE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_it_sourcefiles
 
 TYPE TXW_VDT_SOURCEFILE_T ,
ld_id_tax_view
 
 TYPE TXW_VB_PARAMS-TAX_VIEW ,
ld_is_params
 
 TYPE TXW_VB_PARAMS ,
ld_id_tab_num
 
 TYPE I .


ld_it_sourcefiles = 'Check type of data required'.

ld_id_tax_view = some text here
ld_is_params = 'Check type of data required'.
ld_id_tab_num = 'Check type of data required'.