SAP CACS_PATCH_MANAGER_UI Function Module for Patch Manager: Interface









CACS_PATCH_MANAGER_UI is a standard cacs patch manager ui SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Patch Manager: Interface 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 cacs patch manager ui FM, simply by entering the name CACS_PATCH_MANAGER_UI into the relevant SAP transaction such as SE37 or SE38.

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



Function CACS_PATCH_MANAGER_UI 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 'CACS_PATCH_MANAGER_UI'"Patch Manager: Interface
  EXPORTING
   ID_DYNNR =  "Current Screen Number
*  ID_STARTX =  "Predefined Type
*  ID_STARTY =  "Predefined Type
*  ID_ENDX =  "Predefined Type
*  ID_ENDY =  "Predefined Type
.



IMPORTING Parameters details for CACS_PATCH_MANAGER_UI

ID_DYNNR - Current Screen Number

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

ID_STARTX - Predefined Type

Data type: I
Optional: Yes
Call by Reference: Yes

ID_STARTY - Predefined Type

Data type: I
Optional: Yes
Call by Reference: Yes

ID_ENDX - Predefined Type

Data type: I
Optional: Yes
Call by Reference: Yes

ID_ENDY - Predefined Type

Data type: I
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for CACS_PATCH_MANAGER_UI 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_id_dynnr  TYPE SYDYNNR, "   
lv_id_startx  TYPE I, "   
lv_id_starty  TYPE I, "   
lv_id_endx  TYPE I, "   
lv_id_endy  TYPE I. "   

  CALL FUNCTION 'CACS_PATCH_MANAGER_UI'  "Patch Manager: Interface
    EXPORTING
         ID_DYNNR = lv_id_dynnr
         ID_STARTX = lv_id_startx
         ID_STARTY = lv_id_starty
         ID_ENDX = lv_id_endx
         ID_ENDY = lv_id_endy
. " CACS_PATCH_MANAGER_UI




ABAP code using 7.40 inline data declarations to call FM CACS_PATCH_MANAGER_UI

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!