SAP COM_PR_CHBADI_GET_CHANGED_COMP Function Module for









COM_PR_CHBADI_GET_CHANGED_COMP is a standard com pr chbadi get changed comp 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 com pr chbadi get changed comp FM, simply by entering the name COM_PR_CHBADI_GET_CHANGED_COMP into the relevant SAP transaction such as SE37 or SE38.

Function Group: COM_PRODUCT_CHANGE_EVENT
Program Name: SAPLCOM_PRODUCT_CHANGE_EVENT
Main Program: SAPLCOM_PRODUCT_CHANGE_EVENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function COM_PR_CHBADI_GET_CHANGED_COMP 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 'COM_PR_CHBADI_GET_CHANGED_COMP'"
EXPORTING
IS_CHANGED_COMP = "

IMPORTING
EV_UPDATE_TYPE = "Change Type
EV_PROD_COMP_TYPE = "
EV_PROD_ORG_TYPE = "
EV_COMP_KEY = "

EXCEPTIONS
INTERNAL_ERROR = 1
.



IMPORTING Parameters details for COM_PR_CHBADI_GET_CHANGED_COMP

IS_CHANGED_COMP -

Data type: COMT_CHANGED_PR_COMP
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for COM_PR_CHBADI_GET_CHANGED_COMP

EV_UPDATE_TYPE - Change Type

Data type: UPDATE_TYPE
Optional: No
Call by Reference: Yes

EV_PROD_COMP_TYPE -

Data type: COMT_PROD_COMP_TYPE
Optional: No
Call by Reference: Yes

EV_PROD_ORG_TYPE -

Data type: COMT_PR_ORG_TYPE
Optional: No
Call by Reference: Yes

EV_COMP_KEY -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for COM_PR_CHBADI_GET_CHANGED_COMP 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_ev_update_type  TYPE UPDATE_TYPE, "   
lv_internal_error  TYPE UPDATE_TYPE, "   
lv_is_changed_comp  TYPE COMT_CHANGED_PR_COMP, "   
lv_ev_prod_comp_type  TYPE COMT_PROD_COMP_TYPE, "   
lv_ev_prod_org_type  TYPE COMT_PR_ORG_TYPE, "   
lv_ev_comp_key  TYPE COMT_PR_ORG_TYPE. "   

  CALL FUNCTION 'COM_PR_CHBADI_GET_CHANGED_COMP'  "
    EXPORTING
         IS_CHANGED_COMP = lv_is_changed_comp
    IMPORTING
         EV_UPDATE_TYPE = lv_ev_update_type
         EV_PROD_COMP_TYPE = lv_ev_prod_comp_type
         EV_PROD_ORG_TYPE = lv_ev_prod_org_type
         EV_COMP_KEY = lv_ev_comp_key
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " COM_PR_CHBADI_GET_CHANGED_COMP




ABAP code using 7.40 inline data declarations to call FM COM_PR_CHBADI_GET_CHANGED_COMP

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!