SAP CUDB_UNSPECIALIZE_INSTANCE Function Module for NOTRANSL: Spezialisierung einer Instanz zurückziehen









CUDB_UNSPECIALIZE_INSTANCE is a standard cudb unspecialize instance SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Spezialisierung einer Instanz zurückziehen 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 cudb unspecialize instance FM, simply by entering the name CUDB_UNSPECIALIZE_INSTANCE into the relevant SAP transaction such as SE37 or SE38.

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



Function CUDB_UNSPECIALIZE_INSTANCE 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 'CUDB_UNSPECIALIZE_INSTANCE'"NOTRANSL: Spezialisierung einer Instanz zurückziehen
EXPORTING
INSTANCE = "Instance
KNTYPE = "Author of master data
SEGM = "Author of dependency net
AUTHOR = "
TRIGGER = "Reference to justifying facts
ITYPE = "Type of value assignment retracted

EXCEPTIONS
FAIL = 1 INTERNAL_ERROR = 2
.



IMPORTING Parameters details for CUDB_UNSPECIALIZE_INSTANCE

INSTANCE - Instance

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

KNTYPE - Author of master data

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

SEGM - Author of dependency net

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

AUTHOR -

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

TRIGGER - Reference to justifying facts

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

ITYPE - Type of value assignment retracted

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

EXCEPTIONS details

FAIL - No authorization to retract value

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

INTERNAL_ERROR - Internal Processing Error

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

Copy and paste ABAP code example for CUDB_UNSPECIALIZE_INSTANCE 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_fail  TYPE STRING, "   
lv_instance  TYPE DDB_C02-INSTANCE, "   
lv_kntype  TYPE TMS_JUST-KNTYPE, "   
lv_internal_error  TYPE TMS_JUST, "   
lv_segm  TYPE TMS_JUST-SEGM, "   
lv_author  TYPE TMS_JUST-AUTHOR, "   
lv_trigger  TYPE TMS_JUST-TRIGGER, "   
lv_itype  TYPE DDB_ITP. "   

  CALL FUNCTION 'CUDB_UNSPECIALIZE_INSTANCE'  "NOTRANSL: Spezialisierung einer Instanz zurückziehen
    EXPORTING
         INSTANCE = lv_instance
         KNTYPE = lv_kntype
         SEGM = lv_segm
         AUTHOR = lv_author
         TRIGGER = lv_trigger
         ITYPE = lv_itype
    EXCEPTIONS
        FAIL = 1
        INTERNAL_ERROR = 2
. " CUDB_UNSPECIALIZE_INSTANCE




ABAP code using 7.40 inline data declarations to call FM CUDB_UNSPECIALIZE_INSTANCE

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 INSTANCE FROM DDB_C02 INTO @DATA(ld_instance).
 
"SELECT single KNTYPE FROM TMS_JUST INTO @DATA(ld_kntype).
 
 
"SELECT single SEGM FROM TMS_JUST INTO @DATA(ld_segm).
 
"SELECT single AUTHOR FROM TMS_JUST INTO @DATA(ld_author).
 
"SELECT single TRIGGER FROM TMS_JUST INTO @DATA(ld_trigger).
 
 


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!