SAP EXCHANGE_STMNT_CUSTOMISING Function Module for Customsing for exchange statement
EXCHANGE_STMNT_CUSTOMISING is a standard exchange stmnt customising SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Customsing for exchange statement 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 exchange stmnt customising FM, simply by entering the name EXCHANGE_STMNT_CUSTOMISING into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIAG
Program Name: SAPLOIAG
Main Program: SAPLOIAG
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXCHANGE_STMNT_CUSTOMISING 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 'EXCHANGE_STMNT_CUSTOMISING'"Customsing for exchange statement.
EXPORTING
* ACTION = 'U' "
* KAPPL = ' ' "
VIEW = "
IMPORTING Parameters details for EXCHANGE_STMNT_CUSTOMISING
ACTION -
Data type:Default: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)
KAPPL -
Data type: T681A-KAPPLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
VIEW -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXCHANGE_STMNT_CUSTOMISING 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_action | TYPE STRING, " 'U' | |||
| lv_kappl | TYPE T681A-KAPPL, " ' ' | |||
| lv_view | TYPE T681A. " |
|   CALL FUNCTION 'EXCHANGE_STMNT_CUSTOMISING' "Customsing for exchange statement |
| EXPORTING | ||
| ACTION | = lv_action | |
| KAPPL | = lv_kappl | |
| VIEW | = lv_view | |
| . " EXCHANGE_STMNT_CUSTOMISING | ||
ABAP code using 7.40 inline data declarations to call FM EXCHANGE_STMNT_CUSTOMISING
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_action) | = 'U'. | |||
| "SELECT single KAPPL FROM T681A INTO @DATA(ld_kappl). | ||||
| DATA(ld_kappl) | = ' '. | |||
Search for further information about these or an SAP related objects