SAP SCSM_UPDATE_SUPERCLASS_TABLE Function Module for









SCSM_UPDATE_SUPERCLASS_TABLE is a standard scsm update superclass table 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 scsm update superclass table FM, simply by entering the name SCSM_UPDATE_SUPERCLASS_TABLE into the relevant SAP transaction such as SE37 or SE38.

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



Function SCSM_UPDATE_SUPERCLASS_TABLE 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 'SCSM_UPDATE_SUPERCLASS_TABLE'"
EXPORTING
* SCHEME = SCHEME_BC "Name of semantic for representing system relationships
CLASS = "CCMS Class Names
* SUPER_SCHEME = SCHEME_BC "Name of semantic for representing system relationships
SUPER_CLASS = "CCMS Class Names
* EXTENDED_NAMING = CSM_NO "Indicates whether a CCMS class is the active version
* ABAP_CLASS = "Object Type Name
* JAVA_CLASS = "CCMS Class Names

EXCEPTIONS
CONFLICTING_PARENT_CLASS = 1 CIRCULAR_CLASS_HIERARCHY = 2 EXTENDED_NAMING_ALREADY_ON = 3 SUPERCLASS_OBSOLETE_OR_INVALID = 4 INCONSISTENT_CLASS_HIERARCHY = 5
.



IMPORTING Parameters details for SCSM_UPDATE_SUPERCLASS_TABLE

SCHEME - Name of semantic for representing system relationships

Data type: CSMSMNTC
Default: SCHEME_BC
Optional: Yes
Call by Reference: Yes

CLASS - CCMS Class Names

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

SUPER_SCHEME - Name of semantic for representing system relationships

Data type: CSMSMNTC
Default: SCHEME_BC
Optional: Yes
Call by Reference: Yes

SUPER_CLASS - CCMS Class Names

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

EXTENDED_NAMING - Indicates whether a CCMS class is the active version

Data type: CSMACTIVE
Default: CSM_NO
Optional: Yes
Call by Reference: Yes

ABAP_CLASS - Object Type Name

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

JAVA_CLASS - CCMS Class Names

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

EXCEPTIONS details

CONFLICTING_PARENT_CLASS -

Data type:
Optional: No
Call by Reference: Yes

CIRCULAR_CLASS_HIERARCHY -

Data type:
Optional: No
Call by Reference: Yes

EXTENDED_NAMING_ALREADY_ON -

Data type:
Optional: No
Call by Reference: Yes

SUPERCLASS_OBSOLETE_OR_INVALID -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_CLASS_HIERARCHY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCSM_UPDATE_SUPERCLASS_TABLE 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_scheme  TYPE CSMSMNTC, "   SCHEME_BC
lv_conflicting_parent_class  TYPE CSMSMNTC, "   
lv_class  TYPE CSMCLASS, "   
lv_circular_class_hierarchy  TYPE CSMCLASS, "   
lv_super_scheme  TYPE CSMSMNTC, "   SCHEME_BC
lv_extended_naming_already_on  TYPE CSMSMNTC, "   
lv_super_class  TYPE CSMCLASS, "   
lv_superclass_obsolete_or_invalid  TYPE CSMCLASS, "   
lv_extended_naming  TYPE CSMACTIVE, "   CSM_NO
lv_inconsistent_class_hierarchy  TYPE CSMACTIVE, "   
lv_abap_class  TYPE SEOCLSNAME, "   
lv_java_class  TYPE CSMCLASS. "   

  CALL FUNCTION 'SCSM_UPDATE_SUPERCLASS_TABLE'  "
    EXPORTING
         SCHEME = lv_scheme
         CLASS = lv_class
         SUPER_SCHEME = lv_super_scheme
         SUPER_CLASS = lv_super_class
         EXTENDED_NAMING = lv_extended_naming
         ABAP_CLASS = lv_abap_class
         JAVA_CLASS = lv_java_class
    EXCEPTIONS
        CONFLICTING_PARENT_CLASS = 1
        CIRCULAR_CLASS_HIERARCHY = 2
        EXTENDED_NAMING_ALREADY_ON = 3
        SUPERCLASS_OBSOLETE_OR_INVALID = 4
        INCONSISTENT_CLASS_HIERARCHY = 5
. " SCSM_UPDATE_SUPERCLASS_TABLE




ABAP code using 7.40 inline data declarations to call FM SCSM_UPDATE_SUPERCLASS_TABLE

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_scheme) = SCHEME_BC.
 
 
 
 
DATA(ld_super_scheme) = SCHEME_BC.
 
 
 
 
DATA(ld_extended_naming) = CSM_NO.
 
 
 
 


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!