SAP OIUGT_DN_GET_SCREEN_FIELDS Function Module for Delivery Network Retrieve Screen Fields









OIUGT_DN_GET_SCREEN_FIELDS is a standard oiugt dn get screen fields SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delivery Network Retrieve Screen Fields 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 dn get screen fields FM, simply by entering the name OIUGT_DN_GET_SCREEN_FIELDS into the relevant SAP transaction such as SE37 or SE38.

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



Function OIUGT_DN_GET_SCREEN_FIELDS 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_DN_GET_SCREEN_FIELDS'"Delivery Network Retrieve Screen Fields
IMPORTING
DN_NO = "Delivery network number
PRD_DT = "Production date
DISPLAY_INFO = "Delivery Network - EPG Allocation View Display
FREQUENCY_CODE = "Frequency
MATNR = "Material number
STARTING_MP_NO = "Measurement point number
STARTING_WL_NO = "Well ID number
STARTING_WC_NO = "Well Completion Number
UP_OR_DOWN = "'U' or 'D' - Upstream or Downstream
.



EXPORTING Parameters details for OIUGT_DN_GET_SCREEN_FIELDS

DN_NO - Delivery network number

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

PRD_DT - Production date

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

DISPLAY_INFO - Delivery Network - EPG Allocation View Display

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

FREQUENCY_CODE - Frequency

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

MATNR - Material number

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

STARTING_MP_NO - Measurement point number

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

STARTING_WL_NO - Well ID number

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

STARTING_WC_NO - Well Completion Number

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

UP_OR_DOWN - 'U' or 'D' - Upstream or Downstream

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

Copy and paste ABAP code example for OIUGT_DN_GET_SCREEN_FIELDS 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_dn_no  TYPE OIU_DN_NO, "   
lv_prd_dt  TYPE OIU_PRD_DT, "   
lv_display_info  TYPE OIUGT_PR_DISPLAY, "   
lv_frequency_code  TYPE OIU_FREQ_CD, "   
lv_matnr  TYPE MATNR, "   
lv_starting_mp_no  TYPE OIU_MP_NO, "   
lv_starting_wl_no  TYPE OIU_WL_NO, "   
lv_starting_wc_no  TYPE OIU_WC_NO, "   
lv_up_or_down  TYPE SY-MARKY. "   

  CALL FUNCTION 'OIUGT_DN_GET_SCREEN_FIELDS'  "Delivery Network Retrieve Screen Fields
    IMPORTING
         DN_NO = lv_dn_no
         PRD_DT = lv_prd_dt
         DISPLAY_INFO = lv_display_info
         FREQUENCY_CODE = lv_frequency_code
         MATNR = lv_matnr
         STARTING_MP_NO = lv_starting_mp_no
         STARTING_WL_NO = lv_starting_wl_no
         STARTING_WC_NO = lv_starting_wc_no
         UP_OR_DOWN = lv_up_or_down
. " OIUGT_DN_GET_SCREEN_FIELDS




ABAP code using 7.40 inline data declarations to call FM OIUGT_DN_GET_SCREEN_FIELDS

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 MARKY FROM SY INTO @DATA(ld_up_or_down).
 


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!