SAP OIJ_EL_C_CHECK_INCOMPLETION Function Module for Check incomplation setting
OIJ_EL_C_CHECK_INCOMPLETION is a standard oij el c check incompletion SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check incomplation setting 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 c check incompletion FM, simply by entering the name OIJ_EL_C_CHECK_INCOMPLETION into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJ_EL_C
Program Name: SAPLOIJ_EL_C
Main Program: SAPLOIJ_EL_C
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function OIJ_EL_C_CHECK_INCOMPLETION 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_C_CHECK_INCOMPLETION'"Check incomplation setting.
EXPORTING
* CALLED_FROM = 'SD' "Version number components
POSNR = "Sales document item
IS_CP_LAYT = "Structure Charter party and laytime and demurrage agreement
CHANGING
INCOMPLETION = "IS-OIL TSW: Activate incompletion for sales and purchasing
TABLES
* T_VBUV = "Structure for Internal Table XVBUV
* T_DOC_MOT = "OIL-TSW: TSW Details header / internal structure
* T_DOC_M_MOT = "OIL TSW: Multiple MoT internal structure
EXCEPTIONS
DATA_INCOMPLETE = 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_SAPLOIJ_EL_C_001 Customer screen PBO
EXIT_SAPLOIJ_EL_C_002 Customer screen PAI
IMPORTING Parameters details for OIJ_EL_C_CHECK_INCOMPLETION
CALLED_FROM - Version number components
Data type: CHAR2Default: 'SD'
Optional: No
Call by Reference: Yes
POSNR - Sales document item
Data type: VBAP-POSNROptional: No
Call by Reference: Yes
IS_CP_LAYT - Structure Charter party and laytime and demurrage agreement
Data type: ROIJ_EL_CP_LAYTOptional: No
Call by Reference: Yes
CHANGING Parameters details for OIJ_EL_C_CHECK_INCOMPLETION
INCOMPLETION - IS-OIL TSW: Activate incompletion for sales and purchasing
Data type: TOIJ_EL_INCOMPOptional: No
Call by Reference: Yes
TABLES Parameters details for OIJ_EL_C_CHECK_INCOMPLETION
T_VBUV - Structure for Internal Table XVBUV
Data type: VBUVVBOptional: Yes
Call by Reference: Yes
T_DOC_MOT - OIL-TSW: TSW Details header / internal structure
Data type: ROIJ_EL_DOC_MOTOptional: Yes
Call by Reference: Yes
T_DOC_M_MOT - OIL TSW: Multiple MoT internal structure
Data type: ROIJ_EL_DOC_M_MOTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DATA_INCOMPLETE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJ_EL_C_CHECK_INCOMPLETION 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: | ||||
lt_t_vbuv | TYPE STANDARD TABLE OF VBUVVB, " | |||
lv_called_from | TYPE CHAR2, " 'SD' | |||
lv_incompletion | TYPE TOIJ_EL_INCOMP, " | |||
lv_data_incomplete | TYPE TOIJ_EL_INCOMP, " | |||
lv_posnr | TYPE VBAP-POSNR, " | |||
lt_t_doc_mot | TYPE STANDARD TABLE OF ROIJ_EL_DOC_MOT, " | |||
lv_is_cp_layt | TYPE ROIJ_EL_CP_LAYT, " | |||
lt_t_doc_m_mot | TYPE STANDARD TABLE OF ROIJ_EL_DOC_M_MOT. " |
  CALL FUNCTION 'OIJ_EL_C_CHECK_INCOMPLETION' "Check incomplation setting |
EXPORTING | ||
CALLED_FROM | = lv_called_from | |
POSNR | = lv_posnr | |
IS_CP_LAYT | = lv_is_cp_layt | |
CHANGING | ||
INCOMPLETION | = lv_incompletion | |
TABLES | ||
T_VBUV | = lt_t_vbuv | |
T_DOC_MOT | = lt_t_doc_mot | |
T_DOC_M_MOT | = lt_t_doc_m_mot | |
EXCEPTIONS | ||
DATA_INCOMPLETE = 1 | ||
. " OIJ_EL_C_CHECK_INCOMPLETION |
ABAP code using 7.40 inline data declarations to call FM OIJ_EL_C_CHECK_INCOMPLETION
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_called_from) | = 'SD'. | |||
"SELECT single POSNR FROM VBAP INTO @DATA(ld_posnr). | ||||
Search for further information about these or an SAP related objects