SAP OIUH_JE_INTERFACE Function Module for Journal Entry Creation Interface for PRA sub-systems (R3E onward)

Search SAP Function Modules

OIUH_JE_INTERFACE is a standard oiuh je interface SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Journal Entry Creation Interface for PRA sub-systems (R3E onward) 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 oiuh je interface FM, simply by entering the name OIUH_JE_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

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

Function OIUH_JE_INTERFACE 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 'OIUH_JE_INTERFACE'"Journal Entry Creation Interface for PRA sub-systems (R3E onward)
  EXPORTING
   IF_OPERATION =  "Operation to performed by Interace

CHANGING
*  CS_JEINTF_STR =  "PRA Journal Entries

EXCEPTIONS
   FAILED = 1    INVALID_OPERATION = 2    BNA_FAILED = 3    JETBL_INS_FAILED = 4    BCTBL_INS_FAILED = 5    OUT_OF_BALANCE = 6 

.

IMPORTING Parameters details for OIUH_JE_INTERFACE

IF_OPERATION - Operation to performed by Interace

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

CHANGING Parameters details for OIUH_JE_INTERFACE

CS_JEINTF_STR - PRA Journal Entries

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

EXCEPTIONS details

FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_OPERATION - Invalid Ooperation Code sent by caller

Data type:
Optional: No
Call by Reference: Yes

BNA_FAILED - Operation Batch Number Assign Failed

Data type:
Optional: No
Call by Reference: Yes

JETBL_INS_FAILED - DB Insert failure in OIUH_RV_JEINTF

Data type:
Optional: No
Call by Reference: Yes

BCTBL_INS_FAILED - DB Insert failure in OIUH_RV_BC

Data type:
Optional: No
Call by Reference: Yes

OUT_OF_BALANCE - Out of Balance batches exist

Data type:
Optional: No
Call by Reference: Yes

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

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