SAP CF_BT_FHM_CHECK_CHANGES Function Module for NOTRANSL: Check, ob FHM-Zuordnungen in Plan-Änderungstransaktionen verände
CF_BT_FHM_CHECK_CHANGES is a standard cf bt fhm check changes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Check, ob FHM-Zuordnungen in Plan-Änderungstransaktionen verände 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 cf bt fhm check changes FM, simply by entering the name CF_BT_FHM_CHECK_CHANGES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CFBT
Program Name: SAPLCFBT
Main Program: SAPLCFBT
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CF_BT_FHM_CHECK_CHANGES 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 'CF_BT_FHM_CHECK_CHANGES'"NOTRANSL: Check, ob FHM-Zuordnungen in Plan-Änderungstransaktionen verände.
TABLES
CHANGES_IN_PLAN = "
TABLES Parameters details for CF_BT_FHM_CHECK_CHANGES
CHANGES_IN_PLAN -
Data type: PLAN_CHECKOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CF_BT_FHM_CHECK_CHANGES 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_changes_in_plan | TYPE STANDARD TABLE OF PLAN_CHECK. " |
|   CALL FUNCTION 'CF_BT_FHM_CHECK_CHANGES' "NOTRANSL: Check, ob FHM-Zuordnungen in Plan-Änderungstransaktionen verände |
| TABLES | ||
| CHANGES_IN_PLAN | = lt_changes_in_plan | |
| . " CF_BT_FHM_CHECK_CHANGES | ||
ABAP code using 7.40 inline data declarations to call FM CF_BT_FHM_CHECK_CHANGES
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