SAP OIJ_EL_A_TICKETS_MAINTAIN Function Module for Maintenance of ticket tables









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

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



Function OIJ_EL_A_TICKETS_MAINTAIN 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_A_TICKETS_MAINTAIN'"Maintenance of ticket tables
EXPORTING
* I_COMMIT = 'X' "
* I_UPDATE_HEADER = 'X' "
* I_UPDATE_ITEMS = 'X' "
* I_UPDATE_UOM = 'X' "
* I_UPDATE_ERROR_LOG = 'X' "
* I_UPDATE_DOC_FLOW = 'X' "

CHANGING
I_TICKET_HEADER = "Universal ticket table processing Structure

TABLES
* T_OIJ_EL_TICKET_I = "Universal ticket item table
* T_OIJ_EL_TCKET_UOM = "Universal ticket additional units of measure
* T_OIJ_EL_ERROR_LOG = "OIL-TSW: Error log for ticketing process
* T_OIJ_EL_DOC_FLOW = "OI-TSW: Document flow
.



IMPORTING Parameters details for OIJ_EL_A_TICKETS_MAINTAIN

I_COMMIT -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_UPDATE_HEADER -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_UPDATE_ITEMS -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_UPDATE_UOM -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_UPDATE_ERROR_LOG -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_UPDATE_DOC_FLOW -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for OIJ_EL_A_TICKETS_MAINTAIN

I_TICKET_HEADER - Universal ticket table processing Structure

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

TABLES Parameters details for OIJ_EL_A_TICKETS_MAINTAIN

T_OIJ_EL_TICKET_I - Universal ticket item table

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

T_OIJ_EL_TCKET_UOM - Universal ticket additional units of measure

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

T_OIJ_EL_ERROR_LOG - OIL-TSW: Error log for ticketing process

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

T_OIJ_EL_DOC_FLOW - OI-TSW: Document flow

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

Copy and paste ABAP code example for OIJ_EL_A_TICKETS_MAINTAIN 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_i_commit  TYPE C, "   'X'
lv_i_ticket_header  TYPE OIJ_EL_TICKET_H_STR, "   
lt_t_oij_el_ticket_i  TYPE STANDARD TABLE OF OIJ_EL_TICKET_I_STR, "   
lv_i_update_header  TYPE C, "   'X'
lt_t_oij_el_tcket_uom  TYPE STANDARD TABLE OF OIJ_EL_TICKET_UOM_STR, "   
lv_i_update_items  TYPE C, "   'X'
lt_t_oij_el_error_log  TYPE STANDARD TABLE OF OIJ_EL_ERROR_LOG_STR, "   
lv_i_update_uom  TYPE C, "   'X'
lt_t_oij_el_doc_flow  TYPE STANDARD TABLE OF OIJ_EL_DOC_FLOW_STR, "   
lv_i_update_error_log  TYPE C, "   'X'
lv_i_update_doc_flow  TYPE C. "   'X'

  CALL FUNCTION 'OIJ_EL_A_TICKETS_MAINTAIN'  "Maintenance of ticket tables
    EXPORTING
         I_COMMIT = lv_i_commit
         I_UPDATE_HEADER = lv_i_update_header
         I_UPDATE_ITEMS = lv_i_update_items
         I_UPDATE_UOM = lv_i_update_uom
         I_UPDATE_ERROR_LOG = lv_i_update_error_log
         I_UPDATE_DOC_FLOW = lv_i_update_doc_flow
    CHANGING
         I_TICKET_HEADER = lv_i_ticket_header
    TABLES
         T_OIJ_EL_TICKET_I = lt_t_oij_el_ticket_i
         T_OIJ_EL_TCKET_UOM = lt_t_oij_el_tcket_uom
         T_OIJ_EL_ERROR_LOG = lt_t_oij_el_error_log
         T_OIJ_EL_DOC_FLOW = lt_t_oij_el_doc_flow
. " OIJ_EL_A_TICKETS_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM OIJ_EL_A_TICKETS_MAINTAIN

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.

DATA(ld_i_commit) = 'X'.
 
 
 
DATA(ld_i_update_header) = 'X'.
 
 
DATA(ld_i_update_items) = 'X'.
 
 
DATA(ld_i_update_uom) = 'X'.
 
 
DATA(ld_i_update_error_log) = 'X'.
 
DATA(ld_i_update_doc_flow) = 'X'.
 


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!