SAP FM_RULE_EXISTING_CHECK Function Module for
FM_RULE_EXISTING_CHECK is a standard fm rule existing check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fm rule existing check FM, simply by entering the name FM_RULE_EXISTING_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMKT
Program Name: SAPLFMKT
Main Program: SAPLFMKT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_RULE_EXISTING_CHECK 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 'FM_RULE_EXISTING_CHECK'".
EXPORTING
IP_FIKRS_NEW = "
IP_GJAHR_NEW = "
IP_FIKRS_OLD = "
IP_GJAHR_OLD = "
IP_BI = "
IP_SN = "
IP_TGT_EQ_SRC = "
IP_EINS = "
IP_RING = "
IMPORTING
OP_BI_EXISTS = "
OP_SN_EXISTS = "
TABLES
IT_FONDS = "
EXCEPTIONS
ERROR_OCCURED = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLFMKT_001 Derive Collective Expenditures Subsection in Budget
EXIT_SAPLFMKT_002 Do not use! Check of Eligibility of Cmmt Item Type in Cover Pool
IMPORTING Parameters details for FM_RULE_EXISTING_CHECK
IP_FIKRS_NEW -
Data type: FM01-FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
IP_GJAHR_NEW -
Data type: BKPF-GJAHROptional: No
Call by Reference: No ( called with pass by value option)
IP_FIKRS_OLD -
Data type: FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
IP_GJAHR_OLD -
Data type: GJAHROptional: No
Call by Reference: No ( called with pass by value option)
IP_BI -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
IP_SN -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
IP_TGT_EQ_SRC -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
IP_EINS -
Data type: XFELDOptional: No
Call by Reference: Yes
IP_RING -
Data type: XFELDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FM_RULE_EXISTING_CHECK
OP_BI_EXISTS -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
OP_SN_EXISTS -
Data type: FMDY-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FM_RULE_EXISTING_CHECK
IT_FONDS -
Data type: RANGE_C10Optional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FM_RULE_EXISTING_CHECK 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: | ||||
| lt_it_fonds | TYPE STANDARD TABLE OF RANGE_C10, " | |||
| lv_ip_fikrs_new | TYPE FM01-FIKRS, " | |||
| lv_op_bi_exists | TYPE FMDY-XFELD, " | |||
| lv_error_occured | TYPE FMDY, " | |||
| lv_ip_gjahr_new | TYPE BKPF-GJAHR, " | |||
| lv_op_sn_exists | TYPE FMDY-XFELD, " | |||
| lv_ip_fikrs_old | TYPE FIKRS, " | |||
| lv_ip_gjahr_old | TYPE GJAHR, " | |||
| lv_ip_bi | TYPE FMDY-XFELD, " | |||
| lv_ip_sn | TYPE FMDY-XFELD, " | |||
| lv_ip_tgt_eq_src | TYPE FMDY-XFELD, " | |||
| lv_ip_eins | TYPE XFELD, " | |||
| lv_ip_ring | TYPE XFELD. " |
|   CALL FUNCTION 'FM_RULE_EXISTING_CHECK' " |
| EXPORTING | ||
| IP_FIKRS_NEW | = lv_ip_fikrs_new | |
| IP_GJAHR_NEW | = lv_ip_gjahr_new | |
| IP_FIKRS_OLD | = lv_ip_fikrs_old | |
| IP_GJAHR_OLD | = lv_ip_gjahr_old | |
| IP_BI | = lv_ip_bi | |
| IP_SN | = lv_ip_sn | |
| IP_TGT_EQ_SRC | = lv_ip_tgt_eq_src | |
| IP_EINS | = lv_ip_eins | |
| IP_RING | = lv_ip_ring | |
| IMPORTING | ||
| OP_BI_EXISTS | = lv_op_bi_exists | |
| OP_SN_EXISTS | = lv_op_sn_exists | |
| TABLES | ||
| IT_FONDS | = lt_it_fonds | |
| EXCEPTIONS | ||
| ERROR_OCCURED = 1 | ||
| . " FM_RULE_EXISTING_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FM_RULE_EXISTING_CHECK
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 FIKRS FROM FM01 INTO @DATA(ld_ip_fikrs_new). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_op_bi_exists). | ||||
| "SELECT single GJAHR FROM BKPF INTO @DATA(ld_ip_gjahr_new). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_op_sn_exists). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_ip_bi). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_ip_sn). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_ip_tgt_eq_src). | ||||
Search for further information about these or an SAP related objects