SAP CUDB_RESTRICT_DOM Function Module for NOTRANSL: Teilt der DDB eine Wertebereichseinschränkung für ein Merkmal mi

Search SAP Function Modules

CUDB_RESTRICT_DOM is a standard cudb restrict dom 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: Teilt der DDB eine Wertebereichseinschränkung für ein Merkmal mi 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 restrict dom FM, simply by entering the name CUDB_RESTRICT_DOM 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_RESTRICT_DOM 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_RESTRICT_DOM'"NOTRANSL: Teilt der DDB eine Wertebereichseinschränkung für ein Merkmal mi
  EXPORTING
   ATINN =  "
*  AUTHOR =  "Number of Dependency
   INSTANCE =  "Object index
*  KNTYPE =  "Global knowledge area (such as 'DI' for dialog)
   RFLAG =  "Restriction flag for characteristic (0,1,2,3)
*  SEGM =  "Net to which dependency belongs
*  TRIGGER =  "Reference to trigger list
*  UNCSTR = ' ' "Indicator:'X' <=> value set unrestricted

 IMPORTING
   FACT_INDEX =  "New fact instance number

TABLES
   DOMAIN =  "Value set restriction for characteristic

EXCEPTIONS
   INTERNAL_ERROR = 1    UNKNOWN_INSTANCE = 2 

.

IMPORTING Parameters details for CUDB_RESTRICT_DOM

ATINN -

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

AUTHOR - Number of Dependency

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

INSTANCE - Object index

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

KNTYPE - Global knowledge area (such as 'DI' for dialog)

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

RFLAG - Restriction flag for characteristic (0,1,2,3)

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

SEGM - Net to which dependency belongs

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

TRIGGER - Reference to trigger list

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

UNCSTR - Indicator:'X' <=> value set unrestricted

Data type: CUDBT_DOMAIN-UNCSTR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CUDB_RESTRICT_DOM

FACT_INDEX - New fact instance number

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

TABLES Parameters details for CUDB_RESTRICT_DOM

DOMAIN - Value set restriction for characteristic

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

EXCEPTIONS details

INTERNAL_ERROR - Internal Processing Error

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

UNKNOWN_INSTANCE - Instance not defined

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

Copy and paste ABAP code example for CUDB_RESTRICT_DOM 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.

ABAP code using 7.40 inline data declarations to call FM CUDB_RESTRICT_DOM

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.

Search for further information about these or an SAP related objects