SAP OIUGT_CREATE_TRANSLATIONS Function Module for Graphical Tool Create Node/Entity Primary Key Translation ITAB









OIUGT_CREATE_TRANSLATIONS is a standard oiugt create translations SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Graphical Tool Create Node/Entity Primary Key Translation ITAB 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 oiugt create translations FM, simply by entering the name OIUGT_CREATE_TRANSLATIONS into the relevant SAP transaction such as SE37 or SE38.

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



Function OIUGT_CREATE_TRANSLATIONS 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 'OIUGT_CREATE_TRANSLATIONS'"Graphical Tool Create Node/Entity Primary Key Translation ITAB
  EXPORTING
   GRAPHICAL_VIEW =  "Graphical Tool Graphical View
*  FL = '99' "Flag: Use of values in value tables

TABLES
   ALL_NVALS =  "All Node Values
   TRANSLATION_ITAB =  "Graphical Tool Node/Entity Primary Key Translation ITAB Type

EXCEPTIONS
   INVALID_GRAPHICAL_VIEW = 1    MISSING_NODE_CATEGORY = 2    MISSING_PRIMARY_KEY = 3    EMPTY_ALL_NVALS = 4
.



IMPORTING Parameters details for OIUGT_CREATE_TRANSLATIONS

GRAPHICAL_VIEW - Graphical Tool Graphical View

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

FL - Flag: Use of values in value tables

Data type: NETVALSFL
Default: '99'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for OIUGT_CREATE_TRANSLATIONS

ALL_NVALS - All Node Values

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

TRANSLATION_ITAB - Graphical Tool Node/Entity Primary Key Translation ITAB Type

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

EXCEPTIONS details

INVALID_GRAPHICAL_VIEW - Missing Graphical View Entry In OIUGT_TYPE

Data type:
Optional: No
Call by Reference: Yes

MISSING_NODE_CATEGORY - Missing && entry in NVALS to designate Node Type

Data type:
Optional: No
Call by Reference: Yes

MISSING_PRIMARY_KEY - Missing primary key entry in NVALS

Data type:
Optional: No
Call by Reference: Yes

EMPTY_ALL_NVALS - Internal table ALL_NVALS is empty

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIUGT_CREATE_TRANSLATIONS 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_all_nvals  TYPE STANDARD TABLE OF NVALS_TAB, "   
lv_graphical_view  TYPE OIUGT_GRAPHICAL_VIEW, "   
lv_invalid_graphical_view  TYPE OIUGT_GRAPHICAL_VIEW, "   
lv_fl  TYPE NETVALSFL, "   '99'
lt_translation_itab  TYPE STANDARD TABLE OF OIUGT_NODE_TRANSLATION_ITAB, "   
lv_missing_node_category  TYPE OIUGT_NODE_TRANSLATION_ITAB, "   
lv_missing_primary_key  TYPE OIUGT_NODE_TRANSLATION_ITAB, "   
lv_empty_all_nvals  TYPE OIUGT_NODE_TRANSLATION_ITAB. "   

  CALL FUNCTION 'OIUGT_CREATE_TRANSLATIONS'  "Graphical Tool Create Node/Entity Primary Key Translation ITAB
    EXPORTING
         GRAPHICAL_VIEW = lv_graphical_view
         FL = lv_fl
    TABLES
         ALL_NVALS = lt_all_nvals
         TRANSLATION_ITAB = lt_translation_itab
    EXCEPTIONS
        INVALID_GRAPHICAL_VIEW = 1
        MISSING_NODE_CATEGORY = 2
        MISSING_PRIMARY_KEY = 3
        EMPTY_ALL_NVALS = 4
. " OIUGT_CREATE_TRANSLATIONS




ABAP code using 7.40 inline data declarations to call FM OIUGT_CREATE_TRANSLATIONS

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_fl) = '99'.
 
 
 
 
 


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!