SAP FVD_PROD_ATTR_UPDATE Function Module for Database Update Attributes
FVD_PROD_ATTR_UPDATE is a standard fvd prod attr update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Database Update Attributes 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 prod attr update FM, simply by entering the name FVD_PROD_ATTR_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVDC_PROD_ATTR_DB
Program Name: SAPLFVDC_PROD_ATTR_DB
Main Program: SAPLFVDC_PROD_ATTR_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function FVD_PROD_ATTR_UPDATE 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_PROD_ATTR_UPDATE'"Database Update Attributes.
EXPORTING
* I_FLG_CLIENT_SPECIFIED = "
* I_TAB_ATTRIBUTE_OLD = "Table Type for Attributes (Old)
* I_TAB_ATTRIBUTE_NEW = "Table Type for Attributes (New)
* I_TAB_ATTRIBUTET_OLD = "Table Type for Attribute Text (Old)
* I_TAB_ATTRIBUTET_NEW = "Table Type for Attribute Text (New)
* I_TAB_ATTRTREE_OLD = "Table Type for Attribute Tree (Old)
* I_TAB_ATTRTREE_NEW = "Table Type for Attribute Tree (New)
* I_TAB_ATTRFIELD_OLD = "Table Type for Attribute Fields (Old)
* I_TAB_ATTRFIELD_NEW = "Table Type for Attribute Fields (New)
EXCEPTIONS
DATABASE_ERROR = 1
IMPORTING Parameters details for FVD_PROD_ATTR_UPDATE
I_FLG_CLIENT_SPECIFIED -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRIBUTE_OLD - Table Type for Attributes (Old)
Data type: TRTY_ATTRIBUTEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRIBUTE_NEW - Table Type for Attributes (New)
Data type: TRTY_ATTRIBUTEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRIBUTET_OLD - Table Type for Attribute Text (Old)
Data type: TRTY_ATTRIBUTETOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRIBUTET_NEW - Table Type for Attribute Text (New)
Data type: TRTY_ATTRIBUTETOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRTREE_OLD - Table Type for Attribute Tree (Old)
Data type: TRTY_ATTRTREEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRTREE_NEW - Table Type for Attribute Tree (New)
Data type: TRTY_ATTRTREEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRFIELD_OLD - Table Type for Attribute Fields (Old)
Data type: TRTY_ATTRFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_ATTRFIELD_NEW - Table Type for Attribute Fields (New)
Data type: TRTY_ATTRFIELDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DATABASE_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_PROD_ATTR_UPDATE 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_database_error | TYPE STRING, " | |||
| lv_i_flg_client_specified | TYPE BOOLE-BOOLE, " | |||
| lv_i_tab_attribute_old | TYPE TRTY_ATTRIBUTE, " | |||
| lv_i_tab_attribute_new | TYPE TRTY_ATTRIBUTE, " | |||
| lv_i_tab_attributet_old | TYPE TRTY_ATTRIBUTET, " | |||
| lv_i_tab_attributet_new | TYPE TRTY_ATTRIBUTET, " | |||
| lv_i_tab_attrtree_old | TYPE TRTY_ATTRTREE, " | |||
| lv_i_tab_attrtree_new | TYPE TRTY_ATTRTREE, " | |||
| lv_i_tab_attrfield_old | TYPE TRTY_ATTRFIELD, " | |||
| lv_i_tab_attrfield_new | TYPE TRTY_ATTRFIELD. " |
|   CALL FUNCTION 'FVD_PROD_ATTR_UPDATE' "Database Update Attributes |
| EXPORTING | ||
| I_FLG_CLIENT_SPECIFIED | = lv_i_flg_client_specified | |
| I_TAB_ATTRIBUTE_OLD | = lv_i_tab_attribute_old | |
| I_TAB_ATTRIBUTE_NEW | = lv_i_tab_attribute_new | |
| I_TAB_ATTRIBUTET_OLD | = lv_i_tab_attributet_old | |
| I_TAB_ATTRIBUTET_NEW | = lv_i_tab_attributet_new | |
| I_TAB_ATTRTREE_OLD | = lv_i_tab_attrtree_old | |
| I_TAB_ATTRTREE_NEW | = lv_i_tab_attrtree_new | |
| I_TAB_ATTRFIELD_OLD | = lv_i_tab_attrfield_old | |
| I_TAB_ATTRFIELD_NEW | = lv_i_tab_attrfield_new | |
| EXCEPTIONS | ||
| DATABASE_ERROR = 1 | ||
| . " FVD_PROD_ATTR_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM FVD_PROD_ATTR_UPDATE
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.| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_client_specified). | ||||
Search for further information about these or an SAP related objects