SAP FSCD_SAMPLE_V401 Function Module for XI: Interface for Notification about a Dunning Level Change
FSCD_SAMPLE_V401 is a standard fscd sample v401 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: Interface for Notification about a Dunning Level Change 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 sample v401 FM, simply by entering the name FSCD_SAMPLE_V401 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_SAMPLE_V401 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_SAMPLE_V401'"XI: Interface for Notification about a Dunning Level Change.
EXPORTING
IT_DUNNING_PROGRESSION_INFO = "Interface for XI Message to Change Dunning Level
CHANGING
CS_DUNNING_PROGRESSION_XI = "XI Data
IMPORTING Parameters details for FSCD_SAMPLE_V401
IT_DUNNING_PROGRESSION_INFO - Interface for XI Message to Change Dunning Level
Data type: FSCDINFCO_V001_SEND_TOptional: No
Call by Reference: Yes
CHANGING Parameters details for FSCD_SAMPLE_V401
CS_DUNNING_PROGRESSION_XI - XI Data
Data type: FSCD_DUNN_PROG_BULK_NOTIF_OUTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FSCD_SAMPLE_V401 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_cs_dunning_progression_xi | TYPE FSCD_DUNN_PROG_BULK_NOTIF_OUT, " | |||
| lv_it_dunning_progression_info | TYPE FSCDINFCO_V001_SEND_T. " |
|   CALL FUNCTION 'FSCD_SAMPLE_V401' "XI: Interface for Notification about a Dunning Level Change |
| EXPORTING | ||
| IT_DUNNING_PROGRESSION_INFO | = lv_it_dunning_progression_info | |
| CHANGING | ||
| CS_DUNNING_PROGRESSION_XI | = lv_cs_dunning_progression_xi | |
| . " FSCD_SAMPLE_V401 | ||
ABAP code using 7.40 inline data declarations to call FM FSCD_SAMPLE_V401
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