SAP OIUH_AUTHORIZATION_CHECK Function Module for SAP Oil & Gaz Transaction Common Functions

Search SAP Function Modules

OIUH_AUTHORIZATION_CHECK is a standard oiuh authorization check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAP Oil & Gaz Transaction Common Functions 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 oiuh authorization check FM, simply by entering the name OIUH_AUTHORIZATION_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function OIUH_AUTHORIZATION_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 'OIUH_AUTHORIZATION_CHECK'"SAP Oil & Gaz  Transaction Common Functions
  EXPORTING
*  I_PROGRAM_NAME =  "ABAP program, current main program
   I_TRANSACTION_CODE =  "ABAP program, current transaction code

 IMPORTING
   E_READ_ACCESS =  "User has Read authorization to Program or Transaction
   E_CREATE_ACCESS =  "User has Create authorization to Program or Transaction
   E_CHANGE_ACCESS =  "User has Change authorization to Program or Transaction
   E_DELETE_ACCESS =  "User has Delete authorization to Program or Transaction
   E_APPROVE_ACCESS =  "User has Approve authorization to Program or Transaction

EXCEPTIONS
   PROG_OR_TRANSACTION_NOT_DEFINE = 1 

.

IMPORTING Parameters details for OIUH_AUTHORIZATION_CHECK

I_PROGRAM_NAME - ABAP program, current main program

Data type: SY-REPID
Optional: Yes
Call by Reference: Yes

I_TRANSACTION_CODE - ABAP program, current transaction code

Data type: SY-TCODE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for OIUH_AUTHORIZATION_CHECK

E_READ_ACCESS - User has Read authorization to Program or Transaction

Data type: CHAR1
Optional: No
Call by Reference: Yes

E_CREATE_ACCESS - User has Create authorization to Program or Transaction

Data type: CHAR1
Optional: No
Call by Reference: Yes

E_CHANGE_ACCESS - User has Change authorization to Program or Transaction

Data type: CHAR1
Optional: No
Call by Reference: Yes

E_DELETE_ACCESS - User has Delete authorization to Program or Transaction

Data type: CHAR1
Optional: No
Call by Reference: Yes

E_APPROVE_ACCESS - User has Approve authorization to Program or Transaction

Data type: CHAR1
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PROG_OR_TRANSACTION_NOT_DEFINE - Program or Transaction not in table OIUH_AUTH_OBJ_BY_APPLICATION

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

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

ABAP code using 7.40 inline data declarations to call FM OIUH_AUTHORIZATION_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