SAP OIUH_JELJ110 Function Module for Business Logic Je01









OIUH_JELJ110 is a standard oiuh jelj110 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Business Logic Je01 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 jelj110 FM, simply by entering the name OIUH_JELJ110 into the relevant SAP transaction such as SE37 or SE38.

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



Function OIUH_JELJ110 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_JELJ110'"Business Logic Je01
EXPORTING
P_ACCT_NM = "
P_VERSION_NO = "
P_WARNING_IND = "
P_ACCT_NO = "
P_ACCT_STS = "
P_ACTIVITY_IND = "
P_CALLED_BY_IND = "
P_COMMIT_IND = "
P_CO_NO = "
P_TYPE_CD = "
P_USER_ID = "

IMPORTING
P_O_ACCT_NM = "
P_O_ACCT_STS = "

EXCEPTIONS
GOBACK = 1 WARNING = 2 FAILED = 3
.



IMPORTING Parameters details for OIUH_JELJ110

P_ACCT_NM -

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

P_VERSION_NO -

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

P_WARNING_IND -

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

P_ACCT_NO -

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

P_ACCT_STS -

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

P_ACTIVITY_IND -

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

P_CALLED_BY_IND -

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

P_COMMIT_IND -

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

P_CO_NO -

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

P_TYPE_CD -

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

P_USER_ID -

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

EXPORTING Parameters details for OIUH_JELJ110

P_O_ACCT_NM -

Data type:
Optional: No
Call by Reference: Yes

P_O_ACCT_STS -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

GOBACK -

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

WARNING -

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

FAILED -

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

Copy and paste ABAP code example for OIUH_JELJ110 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_goback  TYPE STRING, "   
lv_p_acct_nm  TYPE STRING, "   
lv_p_o_acct_nm  TYPE STRING, "   
lv_p_version_no  TYPE STRING, "   
lv_p_warning_ind  TYPE STRING, "   
lv_warning  TYPE STRING, "   
lv_p_acct_no  TYPE STRING, "   
lv_p_o_acct_sts  TYPE STRING, "   
lv_failed  TYPE STRING, "   
lv_p_acct_sts  TYPE STRING, "   
lv_p_activity_ind  TYPE STRING, "   
lv_p_called_by_ind  TYPE STRING, "   
lv_p_commit_ind  TYPE STRING, "   
lv_p_co_no  TYPE STRING, "   
lv_p_type_cd  TYPE STRING, "   
lv_p_user_id  TYPE STRING. "   

  CALL FUNCTION 'OIUH_JELJ110'  "Business Logic Je01
    EXPORTING
         P_ACCT_NM = lv_p_acct_nm
         P_VERSION_NO = lv_p_version_no
         P_WARNING_IND = lv_p_warning_ind
         P_ACCT_NO = lv_p_acct_no
         P_ACCT_STS = lv_p_acct_sts
         P_ACTIVITY_IND = lv_p_activity_ind
         P_CALLED_BY_IND = lv_p_called_by_ind
         P_COMMIT_IND = lv_p_commit_ind
         P_CO_NO = lv_p_co_no
         P_TYPE_CD = lv_p_type_cd
         P_USER_ID = lv_p_user_id
    IMPORTING
         P_O_ACCT_NM = lv_p_o_acct_nm
         P_O_ACCT_STS = lv_p_o_acct_sts
    EXCEPTIONS
        GOBACK = 1
        WARNING = 2
        FAILED = 3
. " OIUH_JELJ110




ABAP code using 7.40 inline data declarations to call FM OIUH_JELJ110

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



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!