SAP FVD_MAP_CP_CHGPTR_WRITE Function Module for Create and Write Change Pointers
FVD_MAP_CP_CHGPTR_WRITE is a standard fvd map cp chgptr write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create and Write Change Pointers 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 chgptr write FM, simply by entering the name FVD_MAP_CP_CHGPTR_WRITE 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_CHGPTR_WRITE 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_CHGPTR_WRITE'"Create and Write Change Pointers.
EXPORTING
* I_BUKRS = "Company Code
* I_ALE_EXP_GROUP = '99' "ALE Processing Group
I_FLG_UPDATE_TASK = "'X' = Asynchrone Verbuchung, ' ' = Synchrone Verbuchung
* I_SARCHIV = "Archiving Category Indicator
* I_RANL = "Contract Number
* I_TAB_VDARL_KEY = "Table Type for Key VDARL
* I_TAB = "Tabelle mit Darlehnsnummern
* I_TCODE = "Transaction Code
* I_CHGCATG = "Change Pointer: Change Category
* I_CHGCATGSUB = "Change Sub-Category
* I_TAB_CHGCATG = "Änderungstypen und Änderungs-Subtypen
EXCEPTIONS
NOT_ACTIVE = 1 ERROR = 2
IMPORTING Parameters details for FVD_MAP_CP_CHGPTR_WRITE
I_BUKRS - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
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_UPDATE_TASK - 'X' = Asynchrone Verbuchung, ' ' = Synchrone Verbuchung
Data type: FLAGOptional: No
Call by Reference: No ( called with pass by value option)
I_SARCHIV - Archiving Category Indicator
Data type: SARCHIVOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RANL - Contract Number
Data type: RANLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_VDARL_KEY - Table Type for Key VDARL
Data type: TRTY_VDARL_KEYOptional: Yes
Call by Reference: Yes
I_TAB - Tabelle mit Darlehnsnummern
Data type: ANY TABLEOptional: Yes
Call by Reference: Yes
I_TCODE - Transaction Code
Data type: TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHGCATG - Change Pointer: Change Category
Data type: TB_CHGCATGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHGCATGSUB - Change Sub-Category
Data type: TB_CHGCATGSUBOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_CHGCATG - Änderungstypen und Änderungs-Subtypen
Data type: TRTY_RCHGCATGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_ACTIVE - Änderungszeiger sind nicht aktiviert
Data type:Optional: No
Call by Reference: Yes
ERROR - Internal Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_MAP_CP_CHGPTR_WRITE 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_i_bukrs | TYPE BUKRS, " | |||
| lv_not_active | TYPE BUKRS, " | |||
| lv_i_ale_exp_group | TYPE TB_ALE_EXP_GROUP, " '99' | |||
| lv_i_flg_update_task | TYPE FLAG, " | |||
| lv_error | TYPE FLAG, " | |||
| lv_i_sarchiv | TYPE SARCHIV, " | |||
| lv_i_ranl | TYPE RANL, " | |||
| lv_i_tab_vdarl_key | TYPE TRTY_VDARL_KEY, " | |||
| lv_i_tab | TYPE ANY TABLE, " | |||
| lv_i_tcode | TYPE TCODE, " | |||
| lv_i_chgcatg | TYPE TB_CHGCATG, " | |||
| lv_i_chgcatgsub | TYPE TB_CHGCATGSUB, " | |||
| lv_i_tab_chgcatg | TYPE TRTY_RCHGCATG. " |
|   CALL FUNCTION 'FVD_MAP_CP_CHGPTR_WRITE' "Create and Write Change Pointers |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_ALE_EXP_GROUP | = lv_i_ale_exp_group | |
| I_FLG_UPDATE_TASK | = lv_i_flg_update_task | |
| I_SARCHIV | = lv_i_sarchiv | |
| I_RANL | = lv_i_ranl | |
| I_TAB_VDARL_KEY | = lv_i_tab_vdarl_key | |
| I_TAB | = lv_i_tab | |
| I_TCODE | = lv_i_tcode | |
| I_CHGCATG | = lv_i_chgcatg | |
| I_CHGCATGSUB | = lv_i_chgcatgsub | |
| I_TAB_CHGCATG | = lv_i_tab_chgcatg | |
| EXCEPTIONS | ||
| NOT_ACTIVE = 1 | ||
| ERROR = 2 | ||
| . " FVD_MAP_CP_CHGPTR_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM FVD_MAP_CP_CHGPTR_WRITE
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'. | |||
Search for further information about these or an SAP related objects