SAP PRICAT_HANDLE_CH_MANAGEMENT Function Module for PRICAT: Check and Start Change Management
PRICAT_HANDLE_CH_MANAGEMENT is a standard pricat handle ch management SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PRICAT: Check and Start Change Management 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 pricat handle ch management FM, simply by entering the name PRICAT_HANDLE_CH_MANAGEMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: PRICAT
Program Name: SAPLPRICAT
Main Program: SAPLPRICAT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRICAT_HANDLE_CH_MANAGEMENT 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 'PRICAT_HANDLE_CH_MANAGEMENT'"PRICAT: Check and Start Change Management.
EXPORTING
* IV_KZ_REPORT = C_YES "Aufruf aus Report
EXCEPTIONS
APPL_LOG_ERROR = 1
IMPORTING Parameters details for PRICAT_HANDLE_CH_MANAGEMENT
IV_KZ_REPORT - Aufruf aus Report
Data type: XFELDDefault: C_YES
Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
APPL_LOG_ERROR - Fehler in der Protokolverarbeitung
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRICAT_HANDLE_CH_MANAGEMENT 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_kz_report | TYPE XFELD, " C_YES | |||
| lv_appl_log_error | TYPE XFELD. " |
|   CALL FUNCTION 'PRICAT_HANDLE_CH_MANAGEMENT' "PRICAT: Check and Start Change Management |
| EXPORTING | ||
| IV_KZ_REPORT | = lv_iv_kz_report | |
| EXCEPTIONS | ||
| APPL_LOG_ERROR = 1 | ||
| . " PRICAT_HANDLE_CH_MANAGEMENT | ||
ABAP code using 7.40 inline data declarations to call FM PRICAT_HANDLE_CH_MANAGEMENT
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.| DATA(ld_iv_kz_report) | = C_YES. | |||
Search for further information about these or an SAP related objects