SAP CSO_D_ADDRESS_DIALOGUE_EXEC Function Module for NOTRANSL: Erfassungsdialog CPD Kundenadresse
CSO_D_ADDRESS_DIALOGUE_EXEC is a standard cso d address dialogue exec SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Erfassungsdialog CPD Kundenadresse 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 cso d address dialogue exec FM, simply by entering the name CSO_D_ADDRESS_DIALOGUE_EXEC into the relevant SAP transaction such as SE37 or SE38.
Function Group: WSSD_ADDR
Program Name: SAPLWSSD_ADDR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CSO_D_ADDRESS_DIALOGUE_EXEC 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 'CSO_D_ADDRESS_DIALOGUE_EXEC'"NOTRANSL: Erfassungsdialog CPD Kundenadresse.
EXPORTING
* PI_NO_SCREEN_IF_OK = "Checkbox
* PI_START_MESSAGE = "SAP Retail Store: Sales Order: Return Structure
* PI_USAGE = "SAP Retail Store Sales Order: Usage, Intended Purpose
* PI_ACTIVITY = "SAP Retail Store Sales Order: Operating Mode in Doc. Dialog
IMPORTING
PE_ADDRESS_OK = "Checkbox
PE_RETURN = "SAP Retail Store: Sales Order: Return Structure
CHANGING
PIE_ADDR = "SAP Retail Store Sales Order: Address Data Screen Fields
IMPORTING Parameters details for CSO_D_ADDRESS_DIALOGUE_EXEC
PI_NO_SCREEN_IF_OK - Checkbox
Data type: WISO_HNDL-XFIELDOptional: Yes
Call by Reference: Yes
PI_START_MESSAGE - SAP Retail Store: Sales Order: Return Structure
Data type: WISO_RETURNOptional: Yes
Call by Reference: Yes
PI_USAGE - SAP Retail Store Sales Order: Usage, Intended Purpose
Data type: WISO_HNDL-PROG_USAGEOptional: Yes
Call by Reference: Yes
PI_ACTIVITY - SAP Retail Store Sales Order: Operating Mode in Doc. Dialog
Data type: W_WISO_ACTIVITYOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CSO_D_ADDRESS_DIALOGUE_EXEC
PE_ADDRESS_OK - Checkbox
Data type: WISO_HNDL-XFIELDOptional: No
Call by Reference: No ( called with pass by value option)
PE_RETURN - SAP Retail Store: Sales Order: Return Structure
Data type: WISO_RETURNOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for CSO_D_ADDRESS_DIALOGUE_EXEC
PIE_ADDR - SAP Retail Store Sales Order: Address Data Screen Fields
Data type: WISO_ADDROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CSO_D_ADDRESS_DIALOGUE_EXEC 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_pie_addr | TYPE WISO_ADDR, " | |||
| lv_pe_address_ok | TYPE WISO_HNDL-XFIELD, " | |||
| lv_pi_no_screen_if_ok | TYPE WISO_HNDL-XFIELD, " | |||
| lv_pe_return | TYPE WISO_RETURN, " | |||
| lv_pi_start_message | TYPE WISO_RETURN, " | |||
| lv_pi_usage | TYPE WISO_HNDL-PROG_USAGE, " | |||
| lv_pi_activity | TYPE W_WISO_ACTIVITY. " |
|   CALL FUNCTION 'CSO_D_ADDRESS_DIALOGUE_EXEC' "NOTRANSL: Erfassungsdialog CPD Kundenadresse |
| EXPORTING | ||
| PI_NO_SCREEN_IF_OK | = lv_pi_no_screen_if_ok | |
| PI_START_MESSAGE | = lv_pi_start_message | |
| PI_USAGE | = lv_pi_usage | |
| PI_ACTIVITY | = lv_pi_activity | |
| IMPORTING | ||
| PE_ADDRESS_OK | = lv_pe_address_ok | |
| PE_RETURN | = lv_pe_return | |
| CHANGING | ||
| PIE_ADDR | = lv_pie_addr | |
| . " CSO_D_ADDRESS_DIALOGUE_EXEC | ||
ABAP code using 7.40 inline data declarations to call FM CSO_D_ADDRESS_DIALOGUE_EXEC
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 XFIELD FROM WISO_HNDL INTO @DATA(ld_pe_address_ok). | ||||
| "SELECT single XFIELD FROM WISO_HNDL INTO @DATA(ld_pi_no_screen_if_ok). | ||||
| "SELECT single PROG_USAGE FROM WISO_HNDL INTO @DATA(ld_pi_usage). | ||||
Search for further information about these or an SAP related objects