SAP SPECIALPER_ASSIGNMENT Function Module for NOTRANSL: Genehmigungsdialog









SPECIALPER_ASSIGNMENT is a standard specialper assignment 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: Genehmigungsdialog 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 specialper assignment FM, simply by entering the name SPECIALPER_ASSIGNMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function SPECIALPER_ASSIGNMENT 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 'SPECIALPER_ASSIGNMENT'"NOTRANSL: Genehmigungsdialog
  EXPORTING
   I_AKTYP =  "Activity Category
*  I_PHASE =  "Maintenance Processing Stage
*  I_INITFLG = ' ' "
*  I_DARKFLG = ' ' "
   I_K_OBJEKT =  "Indicator: For Which Object the Permit Was Created
*  I_IWERK =  "Maintenance Planning Plant
   I_OBJNR =  "Object Number
*  I_AUFNR =  "Order Number
*  I_TPLNR =  "Functional Location
*  I_EQUNR =  "Equipment Number
   I_STXT =  "Short Text
*  I_CAUFVD =  "Order data

 IMPORTING
   E_UPDFLG =  "

EXCEPTIONS
   NO_PERMITS = 1
.



IMPORTING Parameters details for SPECIALPER_ASSIGNMENT

I_AKTYP - Activity Category

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

I_PHASE - Maintenance Processing Stage

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

I_INITFLG -

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

I_DARKFLG -

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

I_K_OBJEKT - Indicator: For Which Object the Permit Was Created

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

I_IWERK - Maintenance Planning Plant

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

I_OBJNR - Object Number

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

I_AUFNR - Order Number

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

I_TPLNR - Functional Location

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

I_EQUNR - Equipment Number

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

I_STXT - Short Text

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

I_CAUFVD - Order data

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

EXPORTING Parameters details for SPECIALPER_ASSIGNMENT

E_UPDFLG -

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

EXCEPTIONS details

NO_PERMITS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SPECIALPER_ASSIGNMENT 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_i_aktyp  TYPE AKTYP, "   
lv_e_updflg  TYPE IMPRM_FLAG_TYPE, "   
lv_no_permits  TYPE IMPRM_FLAG_TYPE, "   
lv_i_phase  TYPE PM_PHASE, "   
lv_i_initflg  TYPE IMPRM_FLAG_TYPE, "   SPACE
lv_i_darkflg  TYPE IMPRM_FLAG_TYPE, "   SPACE
lv_i_k_objekt  TYPE K_OBJEKT, "   
lv_i_iwerk  TYPE IWERK, "   
lv_i_objnr  TYPE IMPRM_OBJNR_TYPE, "   
lv_i_aufnr  TYPE AUFNR, "   
lv_i_tplnr  TYPE TPLNR, "   
lv_i_equnr  TYPE EQUNR, "   
lv_i_stxt  TYPE KTX01, "   
lv_i_caufvd  TYPE CAUFVD. "   

  CALL FUNCTION 'SPECIALPER_ASSIGNMENT'  "NOTRANSL: Genehmigungsdialog
    EXPORTING
         I_AKTYP = lv_i_aktyp
         I_PHASE = lv_i_phase
         I_INITFLG = lv_i_initflg
         I_DARKFLG = lv_i_darkflg
         I_K_OBJEKT = lv_i_k_objekt
         I_IWERK = lv_i_iwerk
         I_OBJNR = lv_i_objnr
         I_AUFNR = lv_i_aufnr
         I_TPLNR = lv_i_tplnr
         I_EQUNR = lv_i_equnr
         I_STXT = lv_i_stxt
         I_CAUFVD = lv_i_caufvd
    IMPORTING
         E_UPDFLG = lv_e_updflg
    EXCEPTIONS
        NO_PERMITS = 1
. " SPECIALPER_ASSIGNMENT




ABAP code using 7.40 inline data declarations to call FM SPECIALPER_ASSIGNMENT

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_i_initflg) = ' '.
 
DATA(ld_i_darkflg) = ' '.
 
 
 
 
 
 
 
 
 


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!