SAP EXIT_SAPLOIJ_EL_C_001 Function Module for Customer screen PBO
EXIT_SAPLOIJ_EL_C_001 is a standard exit saploij el c 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Customer screen PBO 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 exit saploij el c 001 FM, simply by entering the name EXIT_SAPLOIJ_EL_C_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XOIJ
Program Name: SAPLXOIJ
Main Program: SAPLXOIJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLOIJ_EL_C_001 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 'EXIT_SAPLOIJ_EL_C_001'"Customer screen PBO.
EXPORTING
IS_OIJ_EL_DOC_MOT = "TSW Details header / internal structure (table type)
IS_OIJ_EL_CP_LAYT = "Structure Charter party and laytime/demurrage (table type)
IV_TRTYP = "Transaction type
IV_DYNNR = "ABAP program, number of current screen
IMPORTING Parameters details for EXIT_SAPLOIJ_EL_C_001
IS_OIJ_EL_DOC_MOT - TSW Details header / internal structure (table type)
Data type: ROIJ_EL_DOC_MOTOptional: No
Call by Reference: Yes
IS_OIJ_EL_CP_LAYT - Structure Charter party and laytime/demurrage (table type)
Data type: ROIJ_EL_CP_LAYTOptional: No
Call by Reference: Yes
IV_TRTYP - Transaction type
Data type: TRTYPOptional: No
Call by Reference: Yes
IV_DYNNR - ABAP program, number of current screen
Data type: SY-DYNNROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLOIJ_EL_C_001 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_is_oij_el_doc_mot | TYPE ROIJ_EL_DOC_MOT, " | |||
lv_is_oij_el_cp_layt | TYPE ROIJ_EL_CP_LAYT, " | |||
lv_iv_trtyp | TYPE TRTYP, " | |||
lv_iv_dynnr | TYPE SY-DYNNR. " |
  CALL FUNCTION 'EXIT_SAPLOIJ_EL_C_001' "Customer screen PBO |
EXPORTING | ||
IS_OIJ_EL_DOC_MOT | = lv_is_oij_el_doc_mot | |
IS_OIJ_EL_CP_LAYT | = lv_is_oij_el_cp_layt | |
IV_TRTYP | = lv_iv_trtyp | |
IV_DYNNR | = lv_iv_dynnr | |
. " EXIT_SAPLOIJ_EL_C_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLOIJ_EL_C_001
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 DYNNR FROM SY INTO @DATA(ld_iv_dynnr). | ||||
Search for further information about these or an SAP related objects