SAP FSCD_V412_EXAMPLE Function Module for XI: Response to Read ICDA by ID
FSCD_V412_EXAMPLE is a standard fscd v412 example SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for XI: Response to Read ICDA by ID 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 fscd v412 example FM, simply by entering the name FSCD_V412_EXAMPLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FSCD_XI_EVENTS
Program Name: SAPLFSCD_XI_EVENTS
Main Program: SAPLFSCD_XI_EVENTS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FSCD_V412_EXAMPLE 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 'FSCD_V412_EXAMPLE'"XI: Response to Read ICDA by ID.
EXPORTING
in = "
CHANGING
out = "
IMPORTING Parameters details for FSCD_V412_EXAMPLE
in -
Data type: VKK_ICDA_DATA_DETOptional: No
Call by Reference: Yes
CHANGING Parameters details for FSCD_V412_EXAMPLE
out -
Data type: FSCD_ICDA_IDRP_MESSAGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FSCD_V412_EXAMPLE 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_in | TYPE VKK_ICDA_DATA_DET, " | |||
| lv_out | TYPE FSCD_ICDA_IDRP_MESSAGE. " |
|   CALL FUNCTION 'FSCD_V412_EXAMPLE' "XI: Response to Read ICDA by ID |
| EXPORTING | ||
| in | = lv_in | |
| CHANGING | ||
| out | = lv_out | |
| . " FSCD_V412_EXAMPLE | ||
ABAP code using 7.40 inline data declarations to call FM FSCD_V412_EXAMPLE
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