SAP FTR_RULESET_CD_DISPLAY Function Module for Display Change Documents for a Rule Object
FTR_RULESET_CD_DISPLAY is a standard ftr ruleset cd display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Change Documents for a Rule Object 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 cd display FM, simply by entering the name FTR_RULESET_CD_DISPLAY 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:

Function FTR_RULESET_CD_DISPLAY 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_CD_DISPLAY'"Display Change Documents for a Rule Object.
EXPORTING
PI_RULESET_ID = "FTR Rule Management: Rule ID
PI_RULESET_CAT = "FTR Rule Management: Rule Category
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for FTR_RULESET_CD_DISPLAY
PI_RULESET_ID - FTR Rule Management: Rule ID
Data type: TB_RULESET_IDOptional: No
Call by Reference: Yes
PI_RULESET_CAT - FTR Rule Management: Rule Category
Data type: TB_RULESET_CATOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILED - Nzeige der Änderungsbelege fehlgeschlagen
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_RULESET_CD_DISPLAY 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_id | TYPE TB_RULESET_ID, " | |||
| lv_pi_ruleset_cat | TYPE TB_RULESET_CAT. " |
|   CALL FUNCTION 'FTR_RULESET_CD_DISPLAY' "Display Change Documents for a Rule Object |
| EXPORTING | ||
| PI_RULESET_ID | = lv_pi_ruleset_id | |
| PI_RULESET_CAT | = lv_pi_ruleset_cat | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " FTR_RULESET_CD_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM FTR_RULESET_CD_DISPLAY
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