SAP OIUY3_TX_JE_END Function Module for Royalty 2.0 - Texas GLO/TAMU - JE Interface - End









OIUY3_TX_JE_END is a standard oiuy3 tx je end SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Royalty 2.0 - Texas GLO/TAMU - JE Interface - End 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 oiuy3 tx je end FM, simply by entering the name OIUY3_TX_JE_END into the relevant SAP transaction such as SE37 or SE38.

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



Function OIUY3_TX_JE_END 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 'OIUY3_TX_JE_END'"Royalty 2.0 - Texas GLO/TAMU - JE Interface - End
EXPORTING
I_BCREC = "Batch Control

TABLES
* RET_MESG = "Return parameter

EXCEPTIONS
NOT_FOUND = 1 INCONSISTENT = 2 OUT_OF_BALANCE = 3 LINEITEM_POST_FAILED = 4 R3FI_POST_FAILED = 5
.



IMPORTING Parameters details for OIUY3_TX_JE_END

I_BCREC - Batch Control

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

TABLES Parameters details for OIUY3_TX_JE_END

RET_MESG - Return parameter

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

EXCEPTIONS details

NOT_FOUND - Record is not available in Database

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

INCONSISTENT - Validation of information failed

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

OUT_OF_BALANCE - Batch Debits does not equal Batch Credits

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

LINEITEM_POST_FAILED - Posting in PRA Lineitem tables failed

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

R3FI_POST_FAILED - Posting R3 FI Document failed

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

Copy and paste ABAP code example for OIUY3_TX_JE_END 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_bcrec  TYPE OIUH_RV_BC, "   
lt_ret_mesg  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_not_found  TYPE BAPIRET2, "   
lv_inconsistent  TYPE BAPIRET2, "   
lv_out_of_balance  TYPE BAPIRET2, "   
lv_lineitem_post_failed  TYPE BAPIRET2, "   
lv_r3fi_post_failed  TYPE BAPIRET2. "   

  CALL FUNCTION 'OIUY3_TX_JE_END'  "Royalty 2.0 - Texas GLO/TAMU - JE Interface - End
    EXPORTING
         I_BCREC = lv_i_bcrec
    TABLES
         RET_MESG = lt_ret_mesg
    EXCEPTIONS
        NOT_FOUND = 1
        INCONSISTENT = 2
        OUT_OF_BALANCE = 3
        LINEITEM_POST_FAILED = 4
        R3FI_POST_FAILED = 5
. " OIUY3_TX_JE_END




ABAP code using 7.40 inline data declarations to call FM OIUY3_TX_JE_END

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!