SAP COM_PR_ADD_CHANGED_SETTYPE_ALL Function Module for
COM_PR_ADD_CHANGED_SETTYPE_ALL is a standard com pr add changed settype all 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 add changed settype all FM, simply by entering the name COM_PR_ADD_CHANGED_SETTYPE_ALL into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_PRODUCT_SET
Program Name: SAPLCOM_PRODUCT_SET
Main Program: SAPLCOM_PRODUCT_SET
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COM_PR_ADD_CHANGED_SETTYPE_ALL 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_ADD_CHANGED_SETTYPE_ALL'".
EXPORTING
* IV_PRODUCT_GUID = "Internal Unique ID of Product
IV_SETTYPE = "Product Set Type GUID
* IV_UPDATE_TYPE = "Change Type
IMPORTING Parameters details for COM_PR_ADD_CHANGED_SETTYPE_ALL
IV_PRODUCT_GUID - Internal Unique ID of Product
Data type: COMT_PRODUCT_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SETTYPE - Product Set Type GUID
Data type: COMT_FRGTYPE_GUIDOptional: No
Call by Reference: Yes
IV_UPDATE_TYPE - Change Type
Data type: UPDATE_TYPEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for COM_PR_ADD_CHANGED_SETTYPE_ALL 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_iv_product_guid | TYPE COMT_PRODUCT_GUID, " | |||
| lv_iv_settype | TYPE COMT_FRGTYPE_GUID, " | |||
| lv_iv_update_type | TYPE UPDATE_TYPE. " |
|   CALL FUNCTION 'COM_PR_ADD_CHANGED_SETTYPE_ALL' " |
| EXPORTING | ||
| IV_PRODUCT_GUID | = lv_iv_product_guid | |
| IV_SETTYPE | = lv_iv_settype | |
| IV_UPDATE_TYPE | = lv_iv_update_type | |
| . " COM_PR_ADD_CHANGED_SETTYPE_ALL | ||
ABAP code using 7.40 inline data declarations to call FM COM_PR_ADD_CHANGED_SETTYPE_ALL
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