SAP OIJ_EL_TICKET_DEFAULT_PLANTS Function Module for Default plants from documents into tickets

Search SAP Function Modules

OIJ_EL_TICKET_DEFAULT_PLANTS is a standard oij el ticket default plants SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Default plants from documents into tickets 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 el ticket default plants FM, simply by entering the name OIJ_EL_TICKET_DEFAULT_PLANTS into the relevant SAP transaction such as SE37 or SE38.

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

Function OIJ_EL_TICKET_DEFAULT_PLANTS 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_EL_TICKET_DEFAULT_PLANTS'"Default plants from documents into tickets
  EXPORTING
   I_MVSCENARIO =  "TSW: Define Movement scenarios
   I_OIJNOMH =  "OIL-TSW: Nomination header table
   I_OIJNOMI =  "OIL-TSW: Nomination item
*  I_IDOC_PLANTS =  "Plants to use for icketing

CHANGING
   I_TICKET_HEADER =  "Universal ticket table processing Structure
   I_TICKET_ITEM =  "Universal ticket item table processing structure

EXCEPTIONS
   ERROR_DEFAULTING_PLANTS = 1 

.

IMPORTING Parameters details for OIJ_EL_TICKET_DEFAULT_PLANTS

I_MVSCENARIO - TSW: Define Movement scenarios

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

I_OIJNOMH - OIL-TSW: Nomination header table

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

I_OIJNOMI - OIL-TSW: Nomination item

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

I_IDOC_PLANTS - Plants to use for icketing

Data type: OIJ_TKT_IDOC_PLANTS
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for OIJ_EL_TICKET_DEFAULT_PLANTS

I_TICKET_HEADER - Universal ticket table processing Structure

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

I_TICKET_ITEM - Universal ticket item table processing structure

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

EXCEPTIONS details

ERROR_DEFAULTING_PLANTS -

Data type:
Optional: No
Call by Reference: Yes

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

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