SAP ISU_PARTNER_READ_DEF_ADDRESS Function Module for Determines Standard Address from Partner Data
ISU_PARTNER_READ_DEF_ADDRESS is a standard isu partner read def address 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 Standard Address from Partner Data 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 partner read def address FM, simply by entering the name ISU_PARTNER_READ_DEF_ADDRESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: ES01
Program Name: SAPLES01
Main Program: SAPLES01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_PARTNER_READ_DEF_ADDRESS 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_PARTNER_READ_DEF_ADDRESS'"Determines Standard Address from Partner Data.
EXPORTING
* X_VALDT = "Validity Date for Changes (Direct Input)
X_PARTNER_DATA = "
IMPORTING
E_ADDRESS = "BP: Addresses with Addr. Data (Read)
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLES01_001 Duplicate Check: Business Partner
EXIT_SAPLES01_030 Before PBO Customer Subscreen
EXIT_SAPLES01_031 After PAI Customer Subscreen
IMPORTING Parameters details for ISU_PARTNER_READ_DEF_ADDRESS
X_VALDT - Validity Date for Changes (Direct Input)
Data type: BUSHDR_DI-VALDTOptional: Yes
Call by Reference: Yes
X_PARTNER_DATA -
Data type: ISU01_PARTNER_DATAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_PARTNER_READ_DEF_ADDRESS
E_ADDRESS - BP: Addresses with Addr. Data (Read)
Data type: BUS020_EXTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_PARTNER_READ_DEF_ADDRESS 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_x_valdt | TYPE BUSHDR_DI-VALDT, " | |||
| lv_e_address | TYPE BUS020_EXT, " | |||
| lv_x_partner_data | TYPE ISU01_PARTNER_DATA. " |
|   CALL FUNCTION 'ISU_PARTNER_READ_DEF_ADDRESS' "Determines Standard Address from Partner Data |
| EXPORTING | ||
| X_VALDT | = lv_x_valdt | |
| X_PARTNER_DATA | = lv_x_partner_data | |
| IMPORTING | ||
| E_ADDRESS | = lv_e_address | |
| . " ISU_PARTNER_READ_DEF_ADDRESS | ||
ABAP code using 7.40 inline data declarations to call FM ISU_PARTNER_READ_DEF_ADDRESS
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 VALDT FROM BUSHDR_DI INTO @DATA(ld_x_valdt). | ||||
Search for further information about these or an SAP related objects