SAP SEO_CLASS_COPY Function Module for









SEO_CLASS_COPY is a standard seo class copy 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 class copy FM, simply by entering the name SEO_CLASS_COPY into the relevant SAP transaction such as SE37 or SE38.

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



Function SEO_CLASS_COPY 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_CLASS_COPY'"
EXPORTING
CLSKEY = "
* SUPPRESS_COMMIT = SEOX_FALSE "
NEW_CLSKEY = "
* ACCESS_PERMISSION = SEOX_TRUE "
* SAVE = SEOX_TRUE "
* SUPPRESS_CORR = SEOX_FALSE "
* SUPPRESS_DIALOG = SEOX_FALSE "
* AUTHORITY_CHECK = SEOX_TRUE "
* LIFECYCLE_MANAGER = "
* LOCK_HANDLE = "

IMPORTING
NEW_CLASS = "

CHANGING
* CORRNR = "Request/Task
* DEVCLASS = "Package

EXCEPTIONS
NOT_EXISTING = 1 DELETED = 2 IS_INTERFACE = 3 NOT_COPIED = 4 DB_ERROR = 5 NO_ACCESS = 6
.



IMPORTING Parameters details for SEO_CLASS_COPY

CLSKEY -

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

SUPPRESS_COMMIT -

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

NEW_CLSKEY -

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

ACCESS_PERMISSION -

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

SAVE -

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

SUPPRESS_CORR -

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

SUPPRESS_DIALOG -

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

AUTHORITY_CHECK -

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

LIFECYCLE_MANAGER -

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

LOCK_HANDLE -

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

EXPORTING Parameters details for SEO_CLASS_COPY

NEW_CLASS -

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

CHANGING Parameters details for SEO_CLASS_COPY

CORRNR - Request/Task

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

DEVCLASS - Package

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

EXCEPTIONS details

NOT_EXISTING -

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

DELETED -

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

IS_INTERFACE -

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

NOT_COPIED -

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

DB_ERROR -

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

NO_ACCESS -

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

Copy and paste ABAP code example for SEO_CLASS_COPY 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, "   
lv_corrnr  TYPE TRKORR, "   
lv_new_class  TYPE VSEOCLASS, "   
lv_not_existing  TYPE VSEOCLASS, "   
lv_suppress_commit  TYPE SEOX_BOOLEAN, "   SEOX_FALSE
lv_deleted  TYPE SEOX_BOOLEAN, "   
lv_devclass  TYPE DEVCLASS, "   
lv_new_clskey  TYPE SEOCLSKEY, "   
lv_is_interface  TYPE SEOCLSKEY, "   
lv_access_permission  TYPE SEOX_BOOLEAN, "   SEOX_TRUE
lv_save  TYPE SEOX_BOOLEAN, "   SEOX_TRUE
lv_not_copied  TYPE SEOX_BOOLEAN, "   
lv_db_error  TYPE SEOX_BOOLEAN, "   
lv_suppress_corr  TYPE SEOX_BOOLEAN, "   SEOX_FALSE
lv_no_access  TYPE SEOX_BOOLEAN, "   
lv_suppress_dialog  TYPE SEOX_BOOLEAN, "   SEOX_FALSE
lv_authority_check  TYPE SEOX_BOOLEAN, "   SEOX_TRUE
lv_lifecycle_manager  TYPE IF_ADT_LIFECYCLE_MANAGER, "   
lv_lock_handle  TYPE IF_ADT_LOCK_HANDLE. "   

  CALL FUNCTION 'SEO_CLASS_COPY'  "
    EXPORTING
         CLSKEY = lv_clskey
         SUPPRESS_COMMIT = lv_suppress_commit
         NEW_CLSKEY = lv_new_clskey
         ACCESS_PERMISSION = lv_access_permission
         SAVE = lv_save
         SUPPRESS_CORR = lv_suppress_corr
         SUPPRESS_DIALOG = lv_suppress_dialog
         AUTHORITY_CHECK = lv_authority_check
         LIFECYCLE_MANAGER = lv_lifecycle_manager
         LOCK_HANDLE = lv_lock_handle
    IMPORTING
         NEW_CLASS = lv_new_class
    CHANGING
         CORRNR = lv_corrnr
         DEVCLASS = lv_devclass
    EXCEPTIONS
        NOT_EXISTING = 1
        DELETED = 2
        IS_INTERFACE = 3
        NOT_COPIED = 4
        DB_ERROR = 5
        NO_ACCESS = 6
. " SEO_CLASS_COPY




ABAP code using 7.40 inline data declarations to call FM SEO_CLASS_COPY

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_suppress_commit) = SEOX_FALSE.
 
 
 
 
 
DATA(ld_access_permission) = SEOX_TRUE.
 
DATA(ld_save) = SEOX_TRUE.
 
 
 
DATA(ld_suppress_corr) = SEOX_FALSE.
 
 
DATA(ld_suppress_dialog) = SEOX_FALSE.
 
DATA(ld_authority_check) = SEOX_TRUE.
 
 
 


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!