SAP OIJ_TKT_OUTPUT_ITEM Function Module for TSW Ticket Item Output determination

Search SAP Function Modules

OIJ_TKT_OUTPUT_ITEM is a standard oij tkt output item SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TSW Ticket Item Output determination 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 oij tkt output item FM, simply by entering the name OIJ_TKT_OUTPUT_ITEM into the relevant SAP transaction such as SE37 or SE38.

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

Function OIJ_TKT_OUTPUT_ITEM 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 'OIJ_TKT_OUTPUT_ITEM'"TSW Ticket Item Output determination
  EXPORTING
   IS_TKT_HEADER =  "TSW Universal ticket table Update Structure
   IS_TKT_ITEM =  "TSW  ticket item table Communication Structure
   IV_TRTYP =  "Transaction type
*  IV_SIMULATION = ' ' "boolean variable (X=true, -=false, space=unknown)

 IMPORTING
   EV_OBJKEY =  "Object key
   EV_OUT_PROCEDURE =  "Procedure (pricing, output control, acct. det., costing,...)
   ET_TKT_PARTNER =  "Nomination Partner role data table for output determination
   ET_OUT_PARTNER =  "Table type for output doc partner functions
   ET_RETURN =  "Return parameter table

EXCEPTIONS
   TKT_TYP_NOT_FOUND = 1    PARTNER_NOT_FOUND = 2 

.

IMPORTING Parameters details for OIJ_TKT_OUTPUT_ITEM

IS_TKT_HEADER - TSW Universal ticket table Update Structure

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

IS_TKT_ITEM - TSW ticket item table Communication Structure

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

IV_TRTYP - Transaction type

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

IV_SIMULATION - boolean variable (X=true, -=false, space=unknown)

Data type: BOOLEAN
Default: SPACE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for OIJ_TKT_OUTPUT_ITEM

EV_OBJKEY - Object key

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

EV_OUT_PROCEDURE - Procedure (pricing, output control, acct. det., costing,...)

Data type: T683-KALSM
Optional: No
Call by Reference: Yes

ET_TKT_PARTNER - Nomination Partner role data table for output determination

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

ET_OUT_PARTNER - Table type for output doc partner functions

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

ET_RETURN - Return parameter table

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

EXCEPTIONS details

TKT_TYP_NOT_FOUND - Ticket Type not found

Data type:
Optional: No
Call by Reference: Yes

PARTNER_NOT_FOUND - Partner not found

Data type:
Optional: No
Call by Reference: Yes

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

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