SAP OM_ADDITIONAL_AUTHORITY_CHECK Function Module for









OM_ADDITIONAL_AUTHORITY_CHECK is a standard om additional authority check 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 om additional authority check FM, simply by entering the name OM_ADDITIONAL_AUTHORITY_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function OM_ADDITIONAL_AUTHORITY_CHECK 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 'OM_ADDITIONAL_AUTHORITY_CHECK'"
  EXPORTING
   SCENARIO =  "
   USERNAME =  "
   TCODE =  "
   CHANGEMODE =  "

 IMPORTING
   TCODE_IS_VALID =  "
.



IMPORTING Parameters details for OM_ADDITIONAL_AUTHORITY_CHECK

SCENARIO -

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

USERNAME -

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

TCODE -

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

CHANGEMODE -

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

EXPORTING Parameters details for OM_ADDITIONAL_AUTHORITY_CHECK

TCODE_IS_VALID -

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

Copy and paste ABAP code example for OM_ADDITIONAL_AUTHORITY_CHECK 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_scenario  TYPE HROMSCEN, "   
lv_tcode_is_valid  TYPE FLAG, "   
lv_username  TYPE SYUNAME, "   
lv_tcode  TYPE TCODE, "   
lv_changemode  TYPE OMACTMODE. "   

  CALL FUNCTION 'OM_ADDITIONAL_AUTHORITY_CHECK'  "
    EXPORTING
         SCENARIO = lv_scenario
         USERNAME = lv_username
         TCODE = lv_tcode
         CHANGEMODE = lv_changemode
    IMPORTING
         TCODE_IS_VALID = lv_tcode_is_valid
. " OM_ADDITIONAL_AUTHORITY_CHECK




ABAP code using 7.40 inline data declarations to call FM OM_ADDITIONAL_AUTHORITY_CHECK

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



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!