SEO_DISPLAY_COMPONENT_DYNPRO SAP Function module

SEO_DISPLAY_COMPONENT_DYNPRO 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 SEO_DISPLAY_COMPONENT_DYNPRO into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SEO_CMPPOPUP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SEO_DISPLAY_COMPONENT_DYNPRO - SEO DISPLAY COMPONENT DYNPRO

CALL FUNCTION 'SEO_DISPLAY_COMPONENT_DYNPRO' "
  EXPORTING
    compo =                     " if_oo_component  Object Reference
    action =                    " seoaction     Processing type
  IMPORTING
    attribute =                 " vseoattrib    ....
    method =                    " vseomethod    Generated Table for View VSEOMETHOD
    event =                     " vseoevent     Generated Table for View &
  EXCEPTIONS
    POPUP_CANCELLED = 1         "
    .  "  SEO_DISPLAY_COMPONENT_DYNPRO

ABAP code example for Function Module SEO_DISPLAY_COMPONENT_DYNPRO

The ABAP code below is a full code listing to execute function module SEO_DISPLAY_COMPONENT_DYNPRO 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_attribute  
 
 TYPE VSEOATTRIB
,
ld_method  
 
 TYPE VSEOMETHOD
,
ld_event  
 
 TYPE VSEOEVENT
.


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

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

CALL FUNCTION 'SEO_DISPLAY_COMPONENT_DYNPRO'
  EXPORTING
    compo =                      ld_compo
    action =                     ld_action
  IMPORTING
    attribute =                  ld_attribute
    method =                     ld_method
    event =                      ld_event
  EXCEPTIONS
    POPUP_CANCELLED =            1
    .  "  SEO_DISPLAY_COMPONENT_DYNPRO

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_attribute
 
 TYPE VSEOATTRIB ,
ld_compo
 
 TYPE IF_OO_COMPONENT ,
ld_method
 
 TYPE VSEOMETHOD ,
ld_action
 
 TYPE SEOACTION ,
ld_event
 
 TYPE VSEOEVENT .


ld_compo = 'Check type of data required'.
ld_action = 'Check type of data required'.