SAP ISU_IDE_DETERMINE_OPAREA Function Module for Determines the Current Operational Area for the Point of Delivery

Search SAP Function Modules

ISU_IDE_DETERMINE_OPAREA is a standard isu ide determine oparea SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines the Current Operational Area for the Point of Delivery 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 isu ide determine oparea FM, simply by entering the name ISU_IDE_DETERMINE_OPAREA into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_IDE_DETERMINE_OPAREA 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 'ISU_IDE_DETERMINE_OPAREA'"Determines the Current Operational Area for the Point of Delivery
  EXPORTING
*  X_POD_INT =  "Internal Point of Delivery Key
*  X_POD_EXT =  "Point of Delivery ID
   X_KEYDATE =  "Date
*  X_BY_DIST_SERVICE =  "By Current Distributor

 IMPORTING
   Y_OPAREA =  "Operational area

EXCEPTIONS
   NOT_FOUND = 1    PARAMETER_ERROR = 2    SYSTEM_ERROR = 3    INVALID_DATE = 4    GENERAL_FAULT = 5 

.

IMPORTING Parameters details for ISU_IDE_DETERMINE_OPAREA

X_POD_INT - Internal Point of Delivery Key

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

X_POD_EXT - Point of Delivery ID

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

X_KEYDATE - Date

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

X_BY_DIST_SERVICE - By Current Distributor

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

EXPORTING Parameters details for ISU_IDE_DETERMINE_OPAREA

Y_OPAREA - Operational area

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

EXCEPTIONS details

NOT_FOUND - NOT_FOUND

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

PARAMETER_ERROR - PARAMETER_ERROR

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

SYSTEM_ERROR - SYSTEM_ERROR

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

INVALID_DATE - INVALID_DATE

Data type:
Optional: No
Call by Reference: Yes

GENERAL_FAULT - GENERAL_FAULT

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_IDE_DETERMINE_OPAREA 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.

ABAP code using 7.40 inline data declarations to call FM ISU_IDE_DETERMINE_OPAREA

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.

Search for further information about these or an SAP related objects