SAP OI0_VALIDATE_EDET Function Module for Validate External Detail entries from Service.









OI0_VALIDATE_EDET is a standard oi0 validate edet SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Validate External Detail entries from Service. 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 oi0 validate edet FM, simply by entering the name OI0_VALIDATE_EDET into the relevant SAP transaction such as SE37 or SE38.

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



Function OI0_VALIDATE_EDET 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 'OI0_VALIDATE_EDET'"Validate External Detail entries from Service.
  EXPORTING
*  COUNTRY =  "Proxy Data Element (Generated)
*  REGION =  "Proxy Data Element (Generated)
*  DISTRICT =  "Proxy Data Element (Generated)
*  CITY =  "Proxy Data Element (Generated)
*  EDET_CHECK = 'X' "Set ' ' if only MoT needs to be checked
*  MOT =  "Proxy Data Element (Generated)
*  EXTBOL =  "Proxy Structure (Generated)
*  BYPASS =  "Indicator: assignment of functional areas is permitted
   ADDTEXT =  "Char 30

CHANGING
   CT_MESSAGE_LOG =  "Table with BAPI Return Information
.



IMPORTING Parameters details for OI0_VALIDATE_EDET

COUNTRY - Proxy Data Element (Generated)

Data type: SAPPLCO_COUNTRY_CODE
Optional: Yes
Call by Reference: Yes

REGION - Proxy Data Element (Generated)

Data type: SAPPLCO_REGION_CODE_CONTENT
Optional: Yes
Call by Reference: Yes

DISTRICT - Proxy Data Element (Generated)

Data type: SAPPLCO_REGIONAL_STRUCTURE_DIS
Optional: Yes
Call by Reference: Yes

CITY - Proxy Data Element (Generated)

Data type: SAPPLCO_REGIONAL_STRUCTURE_CIT
Optional: Yes
Call by Reference: Yes

EDET_CHECK - Set SPACE if only MoT needs to be checked

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: Yes

MOT - Proxy Data Element (Generated)

Data type: SAPPLCO_TRANSPORT_MODE_CODE
Optional: Yes
Call by Reference: Yes

EXTBOL - Proxy Structure (Generated)

Data type: SAPPLCO_TRANSPORTATION_DOCUME1
Optional: Yes
Call by Reference: Yes

BYPASS - Indicator: assignment of functional areas is permitted

Data type: SAPPLCO_INDICATOR
Optional: Yes
Call by Reference: Yes

ADDTEXT - Char 30

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

CHANGING Parameters details for OI0_VALIDATE_EDET

CT_MESSAGE_LOG - Table with BAPI Return Information

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

Copy and paste ABAP code example for OI0_VALIDATE_EDET 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_country  TYPE SAPPLCO_COUNTRY_CODE, "   
lv_ct_message_log  TYPE BAPIRETTAB, "   
lv_region  TYPE SAPPLCO_REGION_CODE_CONTENT, "   
lv_district  TYPE SAPPLCO_REGIONAL_STRUCTURE_DIS, "   
lv_city  TYPE SAPPLCO_REGIONAL_STRUCTURE_CIT, "   
lv_edet_check  TYPE CHAR1, "   'X'
lv_mot  TYPE SAPPLCO_TRANSPORT_MODE_CODE, "   
lv_extbol  TYPE SAPPLCO_TRANSPORTATION_DOCUME1, "   
lv_bypass  TYPE SAPPLCO_INDICATOR, "   
lv_addtext  TYPE CHAR100. "   

  CALL FUNCTION 'OI0_VALIDATE_EDET'  "Validate External Detail entries from Service.
    EXPORTING
         COUNTRY = lv_country
         REGION = lv_region
         DISTRICT = lv_district
         CITY = lv_city
         EDET_CHECK = lv_edet_check
         MOT = lv_mot
         EXTBOL = lv_extbol
         BYPASS = lv_bypass
         ADDTEXT = lv_addtext
    CHANGING
         CT_MESSAGE_LOG = lv_ct_message_log
. " OI0_VALIDATE_EDET




ABAP code using 7.40 inline data declarations to call FM OI0_VALIDATE_EDET

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_edet_check) = 'X'.
 
 
 
 
 


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!