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

Function FTR_RULESET_DBUPDATE 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 'FTR_RULESET_DBUPDATE'"Update Rules in the Database.
EXPORTING
PI_RULESET_KEY = "FTR Rule Management: DB Key of Rule
PI_RULESET_UPD = "FTR Regelverwaltung. Regeln modifizieren
PI_RULESET_DEL = "FTR Regelverwaltung. Regeln löschen
PI_RULESET_INS = "FTR Regelverwaltung. Regeln neu
PI_RULESET_OLD = "FTR Regelverwaltung. Regeln neu
PI_RULESET_NEW = "FTR Regelverwaltung. Regeln neu
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for FTR_RULESET_DBUPDATE
PI_RULESET_KEY - FTR Rule Management: DB Key of Rule
Data type: VTS_RULESET_KEYOptional: No
Call by Reference: No ( called with pass by value option)
PI_RULESET_UPD - FTR Regelverwaltung. Regeln modifizieren
Data type: VTS_RULESET_DBOptional: No
Call by Reference: No ( called with pass by value option)
PI_RULESET_DEL - FTR Regelverwaltung. Regeln löschen
Data type: VTS_RULESET_DBOptional: No
Call by Reference: No ( called with pass by value option)
PI_RULESET_INS - FTR Regelverwaltung. Regeln neu
Data type: VTS_RULESET_DBOptional: No
Call by Reference: No ( called with pass by value option)
PI_RULESET_OLD - FTR Regelverwaltung. Regeln neu
Data type: VTS_RULESET_DBOptional: No
Call by Reference: No ( called with pass by value option)
PI_RULESET_NEW - FTR Regelverwaltung. Regeln neu
Data type: VTS_RULESET_DBOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FAILED - Update failed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_RULESET_DBUPDATE 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_failed | TYPE STRING, " | |||
| lv_pi_ruleset_key | TYPE VTS_RULESET_KEY, " | |||
| lv_pi_ruleset_upd | TYPE VTS_RULESET_DB, " | |||
| lv_pi_ruleset_del | TYPE VTS_RULESET_DB, " | |||
| lv_pi_ruleset_ins | TYPE VTS_RULESET_DB, " | |||
| lv_pi_ruleset_old | TYPE VTS_RULESET_DB, " | |||
| lv_pi_ruleset_new | TYPE VTS_RULESET_DB. " |
|   CALL FUNCTION 'FTR_RULESET_DBUPDATE' "Update Rules in the Database |
| EXPORTING | ||
| PI_RULESET_KEY | = lv_pi_ruleset_key | |
| PI_RULESET_UPD | = lv_pi_ruleset_upd | |
| PI_RULESET_DEL | = lv_pi_ruleset_del | |
| PI_RULESET_INS | = lv_pi_ruleset_ins | |
| PI_RULESET_OLD | = lv_pi_ruleset_old | |
| PI_RULESET_NEW | = lv_pi_ruleset_new | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " FTR_RULESET_DBUPDATE | ||
ABAP code using 7.40 inline data declarations to call FM FTR_RULESET_DBUPDATE
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