SAP CACS_GET_PACKDEPEND Function Module for NOTRANSL: Liefert alle Abhängigkeiten zwischen Paketen
CACS_GET_PACKDEPEND is a standard cacs get packdepend SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Liefert alle Abhängigkeiten zwischen Paketen 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 get packdepend FM, simply by entering the name CACS_GET_PACKDEPEND into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_PACKAGES
Program Name: SAPLCACS_PACKAGES
Main Program: SAPLCACS_PACKAGES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_GET_PACKDEPEND 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_GET_PACKDEPEND'"NOTRANSL: Liefert alle Abhängigkeiten zwischen Paketen.
IMPORTING
T_REQY = "Package Dependencies
T_REQN = "Package Dependencies
EXPORTING Parameters details for CACS_GET_PACKDEPEND
T_REQY - Package Dependencies
Data type: TCACS_PACKDEPOptional: No
Call by Reference: Yes
T_REQN - Package Dependencies
Data type: TCACS_PACKDEPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_GET_PACKDEPEND 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_t_reqy | TYPE TCACS_PACKDEP, " | |||
| lv_t_reqn | TYPE TCACS_PACKDEP. " |
|   CALL FUNCTION 'CACS_GET_PACKDEPEND' "NOTRANSL: Liefert alle Abhängigkeiten zwischen Paketen |
| IMPORTING | ||
| T_REQY | = lv_t_reqy | |
| T_REQN | = lv_t_reqn | |
| . " CACS_GET_PACKDEPEND | ||
ABAP code using 7.40 inline data declarations to call FM CACS_GET_PACKDEPEND
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