SAP OIJB_TICKET_AUTHORIZE Function Module for Authorize ticket data access
OIJB_TICKET_AUTHORIZE is a standard oijb ticket authorize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Authorize ticket data access 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 oijb ticket authorize FM, simply by entering the name OIJB_TICKET_AUTHORIZE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJB
Program Name: SAPLOIJB
Main Program: SAPLOIJB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJB_TICKET_AUTHORIZE 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 'OIJB_TICKET_AUTHORIZE'"Authorize ticket data access.
EXPORTING
IV_ACTIVITY = "Activity
IV_TICKET_TYPE = "OIL-TSW: Ticket type
EXCEPTIONS
NO_AUTHORIZATION = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOIJB_001 TSW: user exits for customer
EXIT_SAPLOIJB_002 TSW: user exits for customer handling of mvmt scenairo
EXIT_SAPLOIJB_003 TSW : User exits to do Rebrands
IMPORTING Parameters details for OIJB_TICKET_AUTHORIZE
IV_ACTIVITY - Activity
Data type: TACT-ACTVTOptional: No
Call by Reference: Yes
IV_TICKET_TYPE - OIL-TSW: Ticket type
Data type: OIJ_EL_TICKET_H-TICKET_TYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_AUTHORIZATION - No authorization forTicket data access
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJB_TICKET_AUTHORIZE 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_iv_activity | TYPE TACT-ACTVT, " | |||
| lv_no_authorization | TYPE TACT, " | |||
| lv_iv_ticket_type | TYPE OIJ_EL_TICKET_H-TICKET_TYPE. " |
|   CALL FUNCTION 'OIJB_TICKET_AUTHORIZE' "Authorize ticket data access |
| EXPORTING | ||
| IV_ACTIVITY | = lv_iv_activity | |
| IV_TICKET_TYPE | = lv_iv_ticket_type | |
| EXCEPTIONS | ||
| NO_AUTHORIZATION = 1 | ||
| . " OIJB_TICKET_AUTHORIZE | ||
ABAP code using 7.40 inline data declarations to call FM OIJB_TICKET_AUTHORIZE
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.| "SELECT single ACTVT FROM TACT INTO @DATA(ld_iv_activity). | ||||
| "SELECT single TICKET_TYPE FROM OIJ_EL_TICKET_H INTO @DATA(ld_iv_ticket_type). | ||||
Search for further information about these or an SAP related objects