SAP ISU_IDE_POPUP_POD Function Module for Selection Popup for Identification of PoD
ISU_IDE_POPUP_POD is a standard isu ide popup pod SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Selection Popup for Identification of PoD 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 popup pod FM, simply by entering the name ISU_IDE_POPUP_POD into the relevant SAP transaction such as SE37 or SE38.
Function Group: EIDE_SWITCH_TEMPLATES
Program Name: SAPLEIDE_SWITCH_TEMPLATES
Main Program: SAPLEIDE_SWITCH_TEMPLATES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_IDE_POPUP_POD 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_POPUP_POD'"Selection Popup for Identification of PoD.
EXPORTING
X_PARTNER = "Business Partner Number
* X_KEYDATE = SY-DATUM "Move-in Date for Switch
IMPORTING
Y_POD_INT = "Internal Key for Point of Delivery
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for ISU_IDE_POPUP_POD
X_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
X_KEYDATE - Move-in Date for Switch
Data type: EIDEMOVEINDATEDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_IDE_POPUP_POD
Y_POD_INT - Internal Key for Point of Delivery
Data type: INT_UIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Nothing found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_IDE_POPUP_POD 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_not_found | TYPE STRING, " | |||
| lv_x_partner | TYPE BU_PARTNER, " | |||
| lv_y_pod_int | TYPE INT_UI, " | |||
| lv_x_keydate | TYPE EIDEMOVEINDATE. " SY-DATUM |
|   CALL FUNCTION 'ISU_IDE_POPUP_POD' "Selection Popup for Identification of PoD |
| EXPORTING | ||
| X_PARTNER | = lv_x_partner | |
| X_KEYDATE | = lv_x_keydate | |
| IMPORTING | ||
| Y_POD_INT | = lv_y_pod_int | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " ISU_IDE_POPUP_POD | ||
ABAP code using 7.40 inline data declarations to call FM ISU_IDE_POPUP_POD
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_x_keydate) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects