SAP OIJC_GET_UOM_F4_HELP Function Module for OIL-TSW: F4 value help on UoM within the TSW









OIJC_GET_UOM_F4_HELP is a standard oijc get uom f4 help SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OIL-TSW: F4 value help on UoM within the TSW 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 oijc get uom f4 help FM, simply by entering the name OIJC_GET_UOM_F4_HELP into the relevant SAP transaction such as SE37 or SE38.

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



Function OIJC_GET_UOM_F4_HELP 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 'OIJC_GET_UOM_F4_HELP'"OIL-TSW: F4 value help on UoM within the TSW
EXPORTING
* I_TWERK = "
* I_LWERK = "
* I_MATNR = "
* I_DIMID = "

IMPORTING
E_RETURNCODE = "

TABLES
T_OIJUOM = "

EXCEPTIONS
NO_IMPORT_PARAMETER = 1 IMPORT_DIMID_INVALID = 2 IMPORT_TWERK_INVALID = 3 IMPORT_LWERK_INVALID = 4 IMPORT_MATNR_INVALID = 5 UNEXPECTED_CASE = 6
.



IMPORTING Parameters details for OIJC_GET_UOM_F4_HELP

I_TWERK -

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

I_LWERK -

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

I_MATNR -

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

I_DIMID -

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

EXPORTING Parameters details for OIJC_GET_UOM_F4_HELP

E_RETURNCODE -

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

TABLES Parameters details for OIJC_GET_UOM_F4_HELP

T_OIJUOM -

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

EXCEPTIONS details

NO_IMPORT_PARAMETER -

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

IMPORT_DIMID_INVALID -

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

IMPORT_TWERK_INVALID -

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

IMPORT_LWERK_INVALID -

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

IMPORT_MATNR_INVALID -

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

UNEXPECTED_CASE -

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

Copy and paste ABAP code example for OIJC_GET_UOM_F4_HELP 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_twerk  TYPE OIJTS-WERK, "   
lt_t_oijuom  TYPE STANDARD TABLE OF ROIJUOM, "   
lv_e_returncode  TYPE C, "   
lv_no_import_parameter  TYPE C, "   
lv_i_lwerk  TYPE OIJLOCMAT-PWERK, "   
lv_import_dimid_invalid  TYPE OIJLOCMAT, "   
lv_i_matnr  TYPE MARA-MATNR, "   
lv_import_twerk_invalid  TYPE MARA, "   
lv_i_dimid  TYPE T006D-DIMID, "   
lv_import_lwerk_invalid  TYPE T006D, "   
lv_import_matnr_invalid  TYPE T006D, "   
lv_unexpected_case  TYPE T006D. "   

  CALL FUNCTION 'OIJC_GET_UOM_F4_HELP'  "OIL-TSW: F4 value help on UoM within the TSW
    EXPORTING
         I_TWERK = lv_i_twerk
         I_LWERK = lv_i_lwerk
         I_MATNR = lv_i_matnr
         I_DIMID = lv_i_dimid
    IMPORTING
         E_RETURNCODE = lv_e_returncode
    TABLES
         T_OIJUOM = lt_t_oijuom
    EXCEPTIONS
        NO_IMPORT_PARAMETER = 1
        IMPORT_DIMID_INVALID = 2
        IMPORT_TWERK_INVALID = 3
        IMPORT_LWERK_INVALID = 4
        IMPORT_MATNR_INVALID = 5
        UNEXPECTED_CASE = 6
. " OIJC_GET_UOM_F4_HELP




ABAP code using 7.40 inline data declarations to call FM OIJC_GET_UOM_F4_HELP

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 WERK FROM OIJTS INTO @DATA(ld_i_twerk).
 
 
 
 
"SELECT single PWERK FROM OIJLOCMAT INTO @DATA(ld_i_lwerk).
 
 
"SELECT single MATNR FROM MARA INTO @DATA(ld_i_matnr).
 
 
"SELECT single DIMID FROM T006D INTO @DATA(ld_i_dimid).
 
 
 
 


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!