SAP PA_MULTI_PACKAGE_CHECK Function Module for









PA_MULTI_PACKAGE_CHECK is a standard pa multi package check 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 pa multi package check FM, simply by entering the name PA_MULTI_PACKAGE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function PA_MULTI_PACKAGE_CHECK 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 'PA_MULTI_PACKAGE_CHECK'"
EXPORTING
I_CLIENT_PGMID = "Program ID in requests and tasks
I_CLIENT_OBJ_TYPE = "Object Type
I_CLIENT_OBJ_KEY = "Generic Key for Development Elements
* I_EXPLAIN = ABAP_FALSE "
* I_ANALYSE_PROPAGATION_IN_PINFS = ABAP_FALSE "

IMPORTING
E_CLIENT_OBJ_PACKAGE = "Package Name
E_ALL_CHECKS_OK = "
E_EXPLAIN = "

CHANGING
C_CHECK_OBJECT_TAB = "

EXCEPTIONS
CLIENT_PACKAGE_NOT_FOUND = 1 SERVER_PACKAGE_NOT_FOUND = 2 CLIENT_HIERARCHY_LOOP = 3 SERVER_HIERARCHY_LOOP = 4
.



IMPORTING Parameters details for PA_MULTI_PACKAGE_CHECK

I_CLIENT_PGMID - Program ID in requests and tasks

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

I_CLIENT_OBJ_TYPE - Object Type

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

I_CLIENT_OBJ_KEY - Generic Key for Development Elements

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

I_EXPLAIN -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

I_ANALYSE_PROPAGATION_IN_PINFS -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PA_MULTI_PACKAGE_CHECK

E_CLIENT_OBJ_PACKAGE - Package Name

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

E_ALL_CHECKS_OK -

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

E_EXPLAIN -

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

CHANGING Parameters details for PA_MULTI_PACKAGE_CHECK

C_CHECK_OBJECT_TAB -

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

EXCEPTIONS details

CLIENT_PACKAGE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

SERVER_PACKAGE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

CLIENT_HIERARCHY_LOOP -

Data type:
Optional: No
Call by Reference: Yes

SERVER_HIERARCHY_LOOP -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PA_MULTI_PACKAGE_CHECK 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_i_client_pgmid  TYPE PGMID, "   
lv_c_check_object_tab  TYPE PAKCHEKTB2, "   
lv_e_client_obj_package  TYPE DEVCLASS, "   
lv_client_package_not_found  TYPE DEVCLASS, "   
lv_e_all_checks_ok  TYPE FLAG, "   
lv_i_client_obj_type  TYPE TROBJTYPE, "   
lv_server_package_not_found  TYPE TROBJTYPE, "   
lv_e_explain  TYPE CL_PAK_EXPLAIN, "   
lv_i_client_obj_key  TYPE ELEMGENKEY, "   
lv_client_hierarchy_loop  TYPE ELEMGENKEY, "   
lv_i_explain  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_server_hierarchy_loop  TYPE ABAP_BOOL, "   
lv_i_analyse_propagation_in_pinfs  TYPE ABAP_BOOL. "   ABAP_FALSE

  CALL FUNCTION 'PA_MULTI_PACKAGE_CHECK'  "
    EXPORTING
         I_CLIENT_PGMID = lv_i_client_pgmid
         I_CLIENT_OBJ_TYPE = lv_i_client_obj_type
         I_CLIENT_OBJ_KEY = lv_i_client_obj_key
         I_EXPLAIN = lv_i_explain
         I_ANALYSE_PROPAGATION_IN_PINFS = lv_i_analyse_propagation_in_pinfs
    IMPORTING
         E_CLIENT_OBJ_PACKAGE = lv_e_client_obj_package
         E_ALL_CHECKS_OK = lv_e_all_checks_ok
         E_EXPLAIN = lv_e_explain
    CHANGING
         C_CHECK_OBJECT_TAB = lv_c_check_object_tab
    EXCEPTIONS
        CLIENT_PACKAGE_NOT_FOUND = 1
        SERVER_PACKAGE_NOT_FOUND = 2
        CLIENT_HIERARCHY_LOOP = 3
        SERVER_HIERARCHY_LOOP = 4
. " PA_MULTI_PACKAGE_CHECK




ABAP code using 7.40 inline data declarations to call FM PA_MULTI_PACKAGE_CHECK

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_i_explain) = ABAP_FALSE.
 
 
DATA(ld_i_analyse_propagation_in_pinfs) = ABAP_FALSE.
 


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!