SAP SEO_COMPONENT_CHECK Function Module for
SEO_COMPONENT_CHECK is a standard seo component check 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 seo component check FM, simply by entering the name SEO_COMPONENT_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEOH
Program Name: SAPLSEOH
Main Program: SAPLSEOH
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SEO_COMPONENT_CHECK 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_CHECK'".
EXPORTING
* DB_CHECK_REFCLIFS = SEOX_TRUE "
* WITH_REFCLIFS_CHECK = SEOX_TRUE "
TABLES
GOOD_CLIFS = "
* GOOD_ATTRIBUTES = "
* GOOD_METHODS = "
* GOOD_EVENTS = "
* GOOD_PARAMETERS = "
* GOOD_EXCEPTIONS = "
* BAD_ATTRIBUTES = "
* BAD_METHODS = "
* BAD_EVENTS = "
* BAD_PARAMETERS = "
* BAD_EXCEPTIONS = "
* BAD_CLIFS = "
* GOOD_REFCLIFS = "
COMP_ATTRIBUTES = "
COMP_METHODS = "
COMP_EVENTS = "
SUBCOMP_PARAMETERS = "
SUBCOMP_EXCEPTIONS = "
* ERRORS = "
EXCEPTIONS
ERROR_OCCURED = 1
IMPORTING Parameters details for SEO_COMPONENT_CHECK
DB_CHECK_REFCLIFS -
Data type: SEOX-FLAGDefault: SEOX_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WITH_REFCLIFS_CHECK -
Data type: SEOX-FLAGDefault: SEOX_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SEO_COMPONENT_CHECK
GOOD_CLIFS -
Data type: VSEOCLIFOptional: No
Call by Reference: No ( called with pass by value option)
GOOD_ATTRIBUTES -
Data type: VSEOATTRIBOptional: Yes
Call by Reference: No ( called with pass by value option)
GOOD_METHODS -
Data type: VSEOMETHODOptional: Yes
Call by Reference: No ( called with pass by value option)
GOOD_EVENTS -
Data type: VSEOEVENTOptional: Yes
Call by Reference: No ( called with pass by value option)
GOOD_PARAMETERS -
Data type: VSEOPARAMOptional: Yes
Call by Reference: No ( called with pass by value option)
GOOD_EXCEPTIONS -
Data type: VSEOEXCEPOptional: Yes
Call by Reference: No ( called with pass by value option)
BAD_ATTRIBUTES -
Data type: VSEOATTRIBOptional: Yes
Call by Reference: No ( called with pass by value option)
BAD_METHODS -
Data type: VSEOMETHODOptional: Yes
Call by Reference: No ( called with pass by value option)
BAD_EVENTS -
Data type: VSEOEVENTOptional: Yes
Call by Reference: No ( called with pass by value option)
BAD_PARAMETERS -
Data type: VSEOPARAMOptional: Yes
Call by Reference: No ( called with pass by value option)
BAD_EXCEPTIONS -
Data type: VSEOEXCEPOptional: Yes
Call by Reference: No ( called with pass by value option)
BAD_CLIFS -
Data type: VSEOCLIFOptional: Yes
Call by Reference: No ( called with pass by value option)
GOOD_REFCLIFS -
Data type: VSEOCLIFOptional: Yes
Call by Reference: No ( called with pass by value option)
COMP_ATTRIBUTES -
Data type: VSEOATTRIBOptional: No
Call by Reference: No ( called with pass by value option)
COMP_METHODS -
Data type: VSEOMETHODOptional: No
Call by Reference: No ( called with pass by value option)
COMP_EVENTS -
Data type: VSEOEVENTOptional: No
Call by Reference: No ( called with pass by value option)
SUBCOMP_PARAMETERS -
Data type: VSEOPARAMOptional: No
Call by Reference: No ( called with pass by value option)
SUBCOMP_EXCEPTIONS -
Data type: VSEOEXCEPOptional: No
Call by Reference: No ( called with pass by value option)
ERRORS -
Data type: RPYGSEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_OCCURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SEO_COMPONENT_CHECK 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: | ||||
| lt_good_clifs | TYPE STANDARD TABLE OF VSEOCLIF, " | |||
| lv_error_occured | TYPE VSEOCLIF, " | |||
| lv_db_check_refclifs | TYPE SEOX-FLAG, " SEOX_TRUE | |||
| lt_good_attributes | TYPE STANDARD TABLE OF VSEOATTRIB, " | |||
| lt_good_methods | TYPE STANDARD TABLE OF VSEOMETHOD, " | |||
| lt_good_events | TYPE STANDARD TABLE OF VSEOEVENT, " | |||
| lt_good_parameters | TYPE STANDARD TABLE OF VSEOPARAM, " | |||
| lt_good_exceptions | TYPE STANDARD TABLE OF VSEOEXCEP, " | |||
| lt_bad_attributes | TYPE STANDARD TABLE OF VSEOATTRIB, " | |||
| lt_bad_methods | TYPE STANDARD TABLE OF VSEOMETHOD, " | |||
| lt_bad_events | TYPE STANDARD TABLE OF VSEOEVENT, " | |||
| lt_bad_parameters | TYPE STANDARD TABLE OF VSEOPARAM, " | |||
| lt_bad_exceptions | TYPE STANDARD TABLE OF VSEOEXCEP, " | |||
| lt_bad_clifs | TYPE STANDARD TABLE OF VSEOCLIF, " | |||
| lv_with_refclifs_check | TYPE SEOX-FLAG, " SEOX_TRUE | |||
| lt_good_refclifs | TYPE STANDARD TABLE OF VSEOCLIF, " | |||
| lt_comp_attributes | TYPE STANDARD TABLE OF VSEOATTRIB, " | |||
| lt_comp_methods | TYPE STANDARD TABLE OF VSEOMETHOD, " | |||
| lt_comp_events | TYPE STANDARD TABLE OF VSEOEVENT, " | |||
| lt_subcomp_parameters | TYPE STANDARD TABLE OF VSEOPARAM, " | |||
| lt_subcomp_exceptions | TYPE STANDARD TABLE OF VSEOEXCEP, " | |||
| lt_errors | TYPE STANDARD TABLE OF RPYGSER. " |
|   CALL FUNCTION 'SEO_COMPONENT_CHECK' " |
| EXPORTING | ||
| DB_CHECK_REFCLIFS | = lv_db_check_refclifs | |
| WITH_REFCLIFS_CHECK | = lv_with_refclifs_check | |
| TABLES | ||
| GOOD_CLIFS | = lt_good_clifs | |
| GOOD_ATTRIBUTES | = lt_good_attributes | |
| GOOD_METHODS | = lt_good_methods | |
| GOOD_EVENTS | = lt_good_events | |
| GOOD_PARAMETERS | = lt_good_parameters | |
| GOOD_EXCEPTIONS | = lt_good_exceptions | |
| BAD_ATTRIBUTES | = lt_bad_attributes | |
| BAD_METHODS | = lt_bad_methods | |
| BAD_EVENTS | = lt_bad_events | |
| BAD_PARAMETERS | = lt_bad_parameters | |
| BAD_EXCEPTIONS | = lt_bad_exceptions | |
| BAD_CLIFS | = lt_bad_clifs | |
| GOOD_REFCLIFS | = lt_good_refclifs | |
| COMP_ATTRIBUTES | = lt_comp_attributes | |
| COMP_METHODS | = lt_comp_methods | |
| COMP_EVENTS | = lt_comp_events | |
| SUBCOMP_PARAMETERS | = lt_subcomp_parameters | |
| SUBCOMP_EXCEPTIONS | = lt_subcomp_exceptions | |
| ERRORS | = lt_errors | |
| EXCEPTIONS | ||
| ERROR_OCCURED = 1 | ||
| . " SEO_COMPONENT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM SEO_COMPONENT_CHECK
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.| "SELECT single FLAG FROM SEOX INTO @DATA(ld_db_check_refclifs). | ||||
| DATA(ld_db_check_refclifs) | = SEOX_TRUE. | |||
| "SELECT single FLAG FROM SEOX INTO @DATA(ld_with_refclifs_check). | ||||
| DATA(ld_with_refclifs_check) | = SEOX_TRUE. | |||
Search for further information about these or an SAP related objects