SAP OIUGT_GET_NODE_CROSS_REFERENCE Function Module for Graphical Tool Retrieve Node Cross Reference Information









OIUGT_GET_NODE_CROSS_REFERENCE is a standard oiugt get node cross reference 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 Retrieve Node Cross Reference Information 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 get node cross reference FM, simply by entering the name OIUGT_GET_NODE_CROSS_REFERENCE 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_GET_NODE_CROSS_REFERENCE 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_GET_NODE_CROSS_REFERENCE'"Graphical Tool Retrieve Node Cross Reference Information
EXPORTING
GRAPHICAL_VIEW = "Graphical Tool Graphical View
NODE_CATEGORY = "Graphical Tool Node Category
NODE_KEY = "Graphical Tool Node Key
* ID = "Identifier for graphical objects
* PRIMARY_KEY = "Primary Key for Node
* SEARCH_TERM = "Text for Node Search Term
* TOOL_TIP = "Text for Tool Tip

IMPORTING
NODE_XREF = "Graphical Tool Node Type Cross Reference

TABLES
NVALS = "Table Type for NET_NVALS

EXCEPTIONS
NO_CROSS_REFERENCE_FOUND = 1
.



IMPORTING Parameters details for OIUGT_GET_NODE_CROSS_REFERENCE

GRAPHICAL_VIEW - Graphical Tool Graphical View

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

NODE_CATEGORY - Graphical Tool Node Category

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

NODE_KEY - Graphical Tool Node Key

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

ID - Identifier for graphical objects

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

PRIMARY_KEY - Primary Key for Node

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

SEARCH_TERM - Text for Node Search Term

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

TOOL_TIP - Text for Tool Tip

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

EXPORTING Parameters details for OIUGT_GET_NODE_CROSS_REFERENCE

NODE_XREF - Graphical Tool Node Type Cross Reference

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

TABLES Parameters details for OIUGT_GET_NODE_CROSS_REFERENCE

NVALS - Table Type for NET_NVALS

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

EXCEPTIONS details

NO_CROSS_REFERENCE_FOUND - No Node Cross Reference Was Found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIUGT_GET_NODE_CROSS_REFERENCE 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_nvals  TYPE STANDARD TABLE OF NVALS_TAB, "   
lv_node_xref  TYPE OIUGT_NODE_XREF, "   
lv_graphical_view  TYPE OIUGT_GRAPHICAL_VIEW, "   
lv_no_cross_reference_found  TYPE OIUGT_GRAPHICAL_VIEW, "   
lv_node_category  TYPE OIUGT_NODE_XREF-NODE_CATEGORY, "   
lv_node_key  TYPE OIUGT_NODE_XREF-NODE_KEY, "   
lv_id  TYPE NET_NVALS-ID, "   
lv_primary_key  TYPE NET_NVALS-VAL, "   
lv_search_term  TYPE NET_NVALS-VAL, "   
lv_tool_tip  TYPE NET_NVALS-VAL. "   

  CALL FUNCTION 'OIUGT_GET_NODE_CROSS_REFERENCE'  "Graphical Tool Retrieve Node Cross Reference Information
    EXPORTING
         GRAPHICAL_VIEW = lv_graphical_view
         NODE_CATEGORY = lv_node_category
         NODE_KEY = lv_node_key
         ID = lv_id
         PRIMARY_KEY = lv_primary_key
         SEARCH_TERM = lv_search_term
         TOOL_TIP = lv_tool_tip
    IMPORTING
         NODE_XREF = lv_node_xref
    TABLES
         NVALS = lt_nvals
    EXCEPTIONS
        NO_CROSS_REFERENCE_FOUND = 1
. " OIUGT_GET_NODE_CROSS_REFERENCE




ABAP code using 7.40 inline data declarations to call FM OIUGT_GET_NODE_CROSS_REFERENCE

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 NODE_CATEGORY FROM OIUGT_NODE_XREF INTO @DATA(ld_node_category).
 
"SELECT single NODE_KEY FROM OIUGT_NODE_XREF INTO @DATA(ld_node_key).
 
"SELECT single ID FROM NET_NVALS INTO @DATA(ld_id).
 
"SELECT single VAL FROM NET_NVALS INTO @DATA(ld_primary_key).
 
"SELECT single VAL FROM NET_NVALS INTO @DATA(ld_search_term).
 
"SELECT single VAL FROM NET_NVALS INTO @DATA(ld_tool_tip).
 


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!