SAP FVD_MAP_CP_ALE_PROCESS_SET Function Module for Set Status of Loans After ALE Export
FVD_MAP_CP_ALE_PROCESS_SET is a standard fvd map cp ale process set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Status of Loans After ALE Export 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 fvd map cp ale process set FM, simply by entering the name FVD_MAP_CP_ALE_PROCESS_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_MAP_CHGPTR
Program Name: SAPLFVD_MAP_CHGPTR
Main Program: SAPLFVD_MAP_CHGPTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_MAP_CP_ALE_PROCESS_SET 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 'FVD_MAP_CP_ALE_PROCESS_SET'"Set Status of Loans After ALE Export.
EXPORTING
I_DATE_FROM = "From Date
I_MODE = "Neuer Status der Änderungszeiger: 'P' = Verarbeitet, 'E' = Fehlerhaft
* I_FLG_UPDATE_TASK = "'X' = Asynchrone Verbuchung, ' ' = Synchrone Verbuchung
I_TIME_FROM = "Time From
I_DATE_TO = "To Date
I_TIME_TO = "Time To
I_TAB_VDARL_KEY = "Loan Key
* I_ALE_EXP_GROUP = '99' "ALE Processing Group
* I_FLG_NOT_PROCESSED = 'X' "Nicht verarbeitete Änderungszeiger berücksichtigen
* I_FLG_PROCESSED = "Verarbeitete Änderungszeiger berücksichtigen
* I_FLG_ERROR = "Fehlerhaft verarbeitete Änderungszeiger berücksichtigen
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for FVD_MAP_CP_ALE_PROCESS_SET
I_DATE_FROM - From Date
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
I_MODE - Neuer Status der Änderungszeiger: 'P' = Verarbeitet, 'E' = Fehlerhaft
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
I_FLG_UPDATE_TASK - 'X' = Asynchrone Verbuchung, ' ' = Synchrone Verbuchung
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TIME_FROM - Time From
Data type: TIMSOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE_TO - To Date
Data type: DATSOptional: No
Call by Reference: No ( called with pass by value option)
I_TIME_TO - Time To
Data type: TIMSOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_VDARL_KEY - Loan Key
Data type: TRTY_VDARL_KEYOptional: No
Call by Reference: Yes
I_ALE_EXP_GROUP - ALE Processing Group
Data type: TB_ALE_EXP_GROUPDefault: '99'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_NOT_PROCESSED - Nicht verarbeitete Änderungszeiger berücksichtigen
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_PROCESSED - Verarbeitete Änderungszeiger berücksichtigen
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_ERROR - Fehlerhaft verarbeitete Änderungszeiger berücksichtigen
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR - Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_MAP_CP_ALE_PROCESS_SET 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_error | TYPE STRING, " | |||
| lv_i_date_from | TYPE DATS, " | |||
| lv_i_mode | TYPE CHAR1, " | |||
| lv_i_flg_update_task | TYPE FLAG, " | |||
| lv_i_time_from | TYPE TIMS, " | |||
| lv_i_date_to | TYPE DATS, " | |||
| lv_i_time_to | TYPE TIMS, " | |||
| lv_i_tab_vdarl_key | TYPE TRTY_VDARL_KEY, " | |||
| lv_i_ale_exp_group | TYPE TB_ALE_EXP_GROUP, " '99' | |||
| lv_i_flg_not_processed | TYPE FLAG, " 'X' | |||
| lv_i_flg_processed | TYPE FLAG, " | |||
| lv_i_flg_error | TYPE FLAG. " |
|   CALL FUNCTION 'FVD_MAP_CP_ALE_PROCESS_SET' "Set Status of Loans After ALE Export |
| EXPORTING | ||
| I_DATE_FROM | = lv_i_date_from | |
| I_MODE | = lv_i_mode | |
| I_FLG_UPDATE_TASK | = lv_i_flg_update_task | |
| I_TIME_FROM | = lv_i_time_from | |
| I_DATE_TO | = lv_i_date_to | |
| I_TIME_TO | = lv_i_time_to | |
| I_TAB_VDARL_KEY | = lv_i_tab_vdarl_key | |
| I_ALE_EXP_GROUP | = lv_i_ale_exp_group | |
| I_FLG_NOT_PROCESSED | = lv_i_flg_not_processed | |
| I_FLG_PROCESSED | = lv_i_flg_processed | |
| I_FLG_ERROR | = lv_i_flg_error | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " FVD_MAP_CP_ALE_PROCESS_SET | ||
ABAP code using 7.40 inline data declarations to call FM FVD_MAP_CP_ALE_PROCESS_SET
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_i_ale_exp_group) | = '99'. | |||
| DATA(ld_i_flg_not_processed) | = 'X'. | |||
Search for further information about these or an SAP related objects