SAP SEO_GET_INTERFACE_TYPEINFO Function Module for get typeinfo of section









SEO_GET_INTERFACE_TYPEINFO is a standard seo get interface typeinfo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for get typeinfo of section processing and below is the pattern details for this FM, 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 seo get interface typeinfo FM, simply by entering the name SEO_GET_INTERFACE_TYPEINFO into the relevant SAP transaction such as SE37 or SE38.

Function Group: SEOQ
Program Name: SAPLSEOQ
Main Program: SAPLSEOQ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SEO_GET_INTERFACE_TYPEINFO 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 'SEO_GET_INTERFACE_TYPEINFO'"get typeinfo of section
  EXPORTING
   CLSKEY =  "Key structure of a class
*  VERSION = '1' "Version indicator (active/inactive)

TABLES
   INTERFACE =  "Generated table for view VSEOCLASS
   SOURCE =  "ABAP Source
   ATTRIBUTES =  "Generated table for view VSEOATTRIB
   METHODS =  "Generated Table for View VSEOMETHOD
   EVENTS =  "Generated table for the view VSEOEVENT
   PARAMS =  "Generated table for view VSEOPARAM
   EXCEPS =  "Generated table for the view VSEOEXCEP
   ALIASES =  "Alias definition
   TYPEPLS =  "Type group application
   METARELS =  "Meta relationship

EXCEPTIONS
   INTERFACE_NOT_EXISTING = 1    SOURCE_NOT_EXISTING = 2    PERMISSION_FAILURE = 3
.



IMPORTING Parameters details for SEO_GET_INTERFACE_TYPEINFO

CLSKEY - Key structure of a class

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

VERSION - Version indicator (active/inactive)

Data type: SEOVERSION
Default: '1'
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SEO_GET_INTERFACE_TYPEINFO

INTERFACE - Generated table for view VSEOCLASS

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

SOURCE - ABAP Source

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

ATTRIBUTES - Generated table for view VSEOATTRIB

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

METHODS - Generated Table for View VSEOMETHOD

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

EVENTS - Generated table for the view VSEOEVENT

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

PARAMS - Generated table for view VSEOPARAM

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

EXCEPS - Generated table for the view VSEOEXCEP

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

ALIASES - Alias definition

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

TYPEPLS - Type group application

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

METARELS - Meta relationship

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

EXCEPTIONS details

INTERFACE_NOT_EXISTING - Interface does not exist

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

SOURCE_NOT_EXISTING -

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

PERMISSION_FAILURE -

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

Copy and paste ABAP code example for SEO_GET_INTERFACE_TYPEINFO 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_clskey  TYPE SEOCLSKEY, "   
lt_interface  TYPE STANDARD TABLE OF SEO_NA_INT, "   
lv_interface_not_existing  TYPE SEO_NA_INT, "   
lt_source  TYPE STANDARD TABLE OF ABAPTXT255, "   
lv_version  TYPE SEOVERSION, "   '1'
lt_attributes  TYPE STANDARD TABLE OF SEO_NA_ATT, "   
lv_source_not_existing  TYPE SEO_NA_ATT, "   
lt_methods  TYPE STANDARD TABLE OF SEO_NA_MET, "   
lv_permission_failure  TYPE SEO_NA_MET, "   
lt_events  TYPE STANDARD TABLE OF SEO_NA_EVT, "   
lt_params  TYPE STANDARD TABLE OF SEO_NA_PAR, "   
lt_exceps  TYPE STANDARD TABLE OF SEO_NA_EXC, "   
lt_aliases  TYPE STANDARD TABLE OF SEO_NA_ALI, "   
lt_typepls  TYPE STANDARD TABLE OF SEO_NA_DFR, "   
lt_metarels  TYPE STANDARD TABLE OF SEO_NA_REL. "   

  CALL FUNCTION 'SEO_GET_INTERFACE_TYPEINFO'  "get typeinfo of section
    EXPORTING
         CLSKEY = lv_clskey
         VERSION = lv_version
    TABLES
         INTERFACE = lt_interface
         SOURCE = lt_source
         ATTRIBUTES = lt_attributes
         METHODS = lt_methods
         EVENTS = lt_events
         PARAMS = lt_params
         EXCEPS = lt_exceps
         ALIASES = lt_aliases
         TYPEPLS = lt_typepls
         METARELS = lt_metarels
    EXCEPTIONS
        INTERFACE_NOT_EXISTING = 1
        SOURCE_NOT_EXISTING = 2
        PERMISSION_FAILURE = 3
. " SEO_GET_INTERFACE_TYPEINFO




ABAP code using 7.40 inline data declarations to call FM SEO_GET_INTERFACE_TYPEINFO

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.

 
 
 
 
DATA(ld_version) = '1'.
 
 
 
 
 
 
 
 
 
 
 


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!