SAP CIF_BOM_CHANGED Function Module for NOTRANSL: PPM: Änderungsübertragung - BOM wurde geändert
CIF_BOM_CHANGED is a standard cif bom changed 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: PPM: Änderungsübertragung - BOM wurde geändert 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 cif bom changed FM, simply by entering the name CIF_BOM_CHANGED into the relevant SAP transaction such as SE37 or SE38.
Function Group: PGS3
Program Name: SAPLPGS3
Main Program: SAPLPGS3
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CIF_BOM_CHANGED 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 'CIF_BOM_CHANGED'"NOTRANSL: PPM: Änderungsübertragung - BOM wurde geändert.
EXPORTING
OBJECT_KEY = "CHT: Object Key
* DATE = SY-DATUM "
* TIME = SY-UZEIT "
IMPORTING Parameters details for CIF_BOM_CHANGED
OBJECT_KEY - CHT: Object Key
Data type: CUXREF-OBJKEYOptional: No
Call by Reference: No ( called with pass by value option)
DATE -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
TIME -
Data type: SY-UZEITDefault: SY-UZEIT
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CIF_BOM_CHANGED 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_object_key | TYPE CUXREF-OBJKEY, " | |||
| lv_date | TYPE SY-DATUM, " SY-DATUM | |||
| lv_time | TYPE SY-UZEIT. " SY-UZEIT |
|   CALL FUNCTION 'CIF_BOM_CHANGED' "NOTRANSL: PPM: Änderungsübertragung - BOM wurde geändert |
| EXPORTING | ||
| OBJECT_KEY | = lv_object_key | |
| DATE | = lv_date | |
| TIME | = lv_time | |
| . " CIF_BOM_CHANGED | ||
ABAP code using 7.40 inline data declarations to call FM CIF_BOM_CHANGED
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 OBJKEY FROM CUXREF INTO @DATA(ld_object_key). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_date). | ||||
| DATA(ld_date) | = SY-DATUM. | |||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_time). | ||||
| DATA(ld_time) | = SY-UZEIT. | |||
Search for further information about these or an SAP related objects