SAP SEO_COMPONENT_BY_INHERITANCE Function Module for Vererbte Komponente lesen









SEO_COMPONENT_BY_INHERITANCE is a standard seo component by inheritance SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Vererbte Komponente lesen 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 component by inheritance FM, simply by entering the name SEO_COMPONENT_BY_INHERITANCE into the relevant SAP transaction such as SE37 or SE38.

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



Function SEO_COMPONENT_BY_INHERITANCE 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_COMPONENT_BY_INHERITANCE'"Vererbte Komponente lesen
  EXPORTING
   CPDKEY =  "
*  VERSION = SEOC_VERSION_INACTIVE "
*  STATE = '1' "
*  WITH_ENHANCEMENTS = SEOX_FALSE "

 IMPORTING
   RELTYPE =  "
   RELKEY =  "
   CMPTYPE =  "
   CMPKEY =  "
   EXPOSURE =  "Sichtbarkeit der Komponente bzw. der Implementierungsbeziehung
   IS_ENHANCEMENT_COMP =  "
   IS_LOCAL_COMPONENT =  "X = means it's not inherited, it's local

EXCEPTIONS
   NOT_EXISTING = 1    MODEL_ONLY = 2
.



IMPORTING Parameters details for SEO_COMPONENT_BY_INHERITANCE

CPDKEY -

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

VERSION -

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

STATE -

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

WITH_ENHANCEMENTS -

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

EXPORTING Parameters details for SEO_COMPONENT_BY_INHERITANCE

RELTYPE -

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

RELKEY -

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

CMPTYPE -

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

CMPKEY -

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

EXPOSURE - Sichtbarkeit der Komponente bzw. der Implementierungsbeziehung

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

IS_ENHANCEMENT_COMP -

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

IS_LOCAL_COMPONENT - X = means it's not inherited, it's local

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

EXCEPTIONS details

NOT_EXISTING -

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

MODEL_ONLY -

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

Copy and paste ABAP code example for SEO_COMPONENT_BY_INHERITANCE 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_cpdkey  TYPE SEOCPDKEY, "   
lv_reltype  TYPE SEORELTYPE, "   
lv_not_existing  TYPE SEORELTYPE, "   
lv_relkey  TYPE SEORELKEY, "   
lv_version  TYPE SEOVERSION, "   SEOC_VERSION_INACTIVE
lv_model_only  TYPE SEOVERSION, "   
lv_state  TYPE SEOSTATE, "   '1'
lv_cmptype  TYPE SEOCMPTYPE, "   
lv_cmpkey  TYPE SEOCMPKEY, "   
lv_with_enhancements  TYPE SEOX_BOOLEAN, "   SEOX_FALSE
lv_exposure  TYPE SEOEXPOSE, "   
lv_is_enhancement_comp  TYPE SEOX_BOOLEAN, "   
lv_is_local_component  TYPE SEOX_BOOLEAN. "   

  CALL FUNCTION 'SEO_COMPONENT_BY_INHERITANCE'  "Vererbte Komponente lesen
    EXPORTING
         CPDKEY = lv_cpdkey
         VERSION = lv_version
         STATE = lv_state
         WITH_ENHANCEMENTS = lv_with_enhancements
    IMPORTING
         RELTYPE = lv_reltype
         RELKEY = lv_relkey
         CMPTYPE = lv_cmptype
         CMPKEY = lv_cmpkey
         EXPOSURE = lv_exposure
         IS_ENHANCEMENT_COMP = lv_is_enhancement_comp
         IS_LOCAL_COMPONENT = lv_is_local_component
    EXCEPTIONS
        NOT_EXISTING = 1
        MODEL_ONLY = 2
. " SEO_COMPONENT_BY_INHERITANCE




ABAP code using 7.40 inline data declarations to call FM SEO_COMPONENT_BY_INHERITANCE

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) = SEOC_VERSION_INACTIVE.
 
 
DATA(ld_state) = '1'.
 
 
 
DATA(ld_with_enhancements) = SEOX_FALSE.
 
 
 
 


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!