SAP ALV_OPTIMIZE_OUTPUT Function Module for









ALV_OPTIMIZE_OUTPUT is a standard alv optimize output 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 alv optimize output FM, simply by entering the name ALV_OPTIMIZE_OUTPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function ALV_OPTIMIZE_OUTPUT 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 'ALV_OPTIMIZE_OUTPUT'"
  EXPORTING
   IT_ALV_DATA =  "ALV Data Sheet
*  IT_ALV_ITEM_DATA =  "ALV Item Table (Hierarchical Sequence List)
*  IT_FIELDS_NO_OPTIMIZATION =  "Fields to Be Excluded from Optimization
*  IV_STRUCTURE_NAME =  "Structure Name for ALV Field Catalog Creation
*  IS_VARIANT =  "Layout

 IMPORTING
   EX_FIELDCAT_CHANGED =  "'X' = Field Catalog Has Been Changed by Optimizer

CHANGING
*  CH_FIELDCAT =  "Field Catalog for List Viewer Control
*  CH_FIELDCAT_OLD =  "Field Catalog for ListViewer in Reuse ALV Format

EXCEPTIONS
   FAILED = 1
.



IMPORTING Parameters details for ALV_OPTIMIZE_OUTPUT

IT_ALV_DATA - ALV Data Sheet

Data type: TABLE
Optional: No
Call by Reference: Yes

IT_ALV_ITEM_DATA - ALV Item Table (Hierarchical Sequence List)

Data type: TABLE
Optional: Yes
Call by Reference: Yes

IT_FIELDS_NO_OPTIMIZATION - Fields to Be Excluded from Optimization

Data type: STRING_TABLE
Optional: Yes
Call by Reference: Yes

IV_STRUCTURE_NAME - Structure Name for ALV Field Catalog Creation

Data type: CLIKE
Optional: Yes
Call by Reference: Yes

IS_VARIANT - Layout

Data type: DISVARIANT
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ALV_OPTIMIZE_OUTPUT

EX_FIELDCAT_CHANGED - 'X' = Field Catalog Has Been Changed by Optimizer

Data type: XFELD
Optional: No
Call by Reference: Yes

CHANGING Parameters details for ALV_OPTIMIZE_OUTPUT

CH_FIELDCAT - Field Catalog for List Viewer Control

Data type: LVC_T_FCAT
Optional: Yes
Call by Reference: Yes

CH_FIELDCAT_OLD - Field Catalog for ListViewer in Reuse ALV Format

Data type: SLIS_T_FIELDCAT_ALV
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

FAILED - Field Catalog(s) and Structure Name Are Blank

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ALV_OPTIMIZE_OUTPUT 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_failed  TYPE STRING, "   
lv_ch_fieldcat  TYPE LVC_T_FCAT, "   
lv_it_alv_data  TYPE TABLE, "   
lv_ex_fieldcat_changed  TYPE XFELD, "   
lv_ch_fieldcat_old  TYPE SLIS_T_FIELDCAT_ALV, "   
lv_it_alv_item_data  TYPE TABLE, "   
lv_it_fields_no_optimization  TYPE STRING_TABLE, "   
lv_iv_structure_name  TYPE CLIKE, "   
lv_is_variant  TYPE DISVARIANT. "   

  CALL FUNCTION 'ALV_OPTIMIZE_OUTPUT'  "
    EXPORTING
         IT_ALV_DATA = lv_it_alv_data
         IT_ALV_ITEM_DATA = lv_it_alv_item_data
         IT_FIELDS_NO_OPTIMIZATION = lv_it_fields_no_optimization
         IV_STRUCTURE_NAME = lv_iv_structure_name
         IS_VARIANT = lv_is_variant
    IMPORTING
         EX_FIELDCAT_CHANGED = lv_ex_fieldcat_changed
    CHANGING
         CH_FIELDCAT = lv_ch_fieldcat
         CH_FIELDCAT_OLD = lv_ch_fieldcat_old
    EXCEPTIONS
        FAILED = 1
. " ALV_OPTIMIZE_OUTPUT




ABAP code using 7.40 inline data declarations to call FM ALV_OPTIMIZE_OUTPUT

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



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!