SAP SDU_SPECCAT_ADD Function Module for UDM Create Specialization type

Search SAP Function Modules

SDU_SPECCAT_ADD is a standard sdu speccat add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for UDM Create Specialization type 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 sdu speccat add FM, simply by entering the name SDU_SPECCAT_ADD into the relevant SAP transaction such as SE37 or SE38.

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

Function SDU_SPECCAT_ADD 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 'SDU_SPECCAT_ADD'"UDM Create Specialization type
  EXPORTING
*  AS4LOCAL = 'A' "Validity
   ENTID =  "Entity type
*  SPECID = ' ' "Specialization type number
   POPUP =  "Flag: 'X' Enter name in dialog box
*  GRAPHIC_MODE = ' ' "Graphic mode

 IMPORTING
   OK_CODE =  "OK code that cannot be processed
   SPECCAT_INFO =  "Specialization type information

EXCEPTIONS
   NOT_FOUND = 1    ALREADY_EXISTS = 2    NAME_NOT_VALID = 3    NOT_EXECUTED = 4    NOT_SPECIFIED = 5    PERMISSION_FAILURE = 6 

.

IMPORTING Parameters details for SDU_SPECCAT_ADD

AS4LOCAL - Validity

Data type: DM45L-AS4LOCAL
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENTID - Entity type

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

SPECID - Specialization type number

Data type: DM45L-SPEZID
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

POPUP - Flag: 'X' Enter name in dialog box

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

GRAPHIC_MODE - Graphic mode

Data type: SY-INPUT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SDU_SPECCAT_ADD

OK_CODE - OK code that cannot be processed

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

SPECCAT_INFO - Specialization type information

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

EXCEPTIONS details

NOT_FOUND - Specialization type not found

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

ALREADY_EXISTS - Object already exists

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

NAME_NOT_VALID - Name does not follow naming convention

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

NOT_EXECUTED - Action was cancelled without saving

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

NOT_SPECIFIED - Name missing

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

PERMISSION_FAILURE - Access not possible

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

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

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