PA_GET_PACKAGE_INTERFACE_NAMES SAP Function module

PA_GET_PACKAGE_INTERFACE_NAMES is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name PA_GET_PACKAGE_INTERFACE_NAMES into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: PA_PACKAGE_SERVICES
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM PA_GET_PACKAGE_INTERFACE_NAMES - PA GET PACKAGE INTERFACE NAMES

CALL FUNCTION 'PA_GET_PACKAGE_INTERFACE_NAMES' "
  EXPORTING
    i_package_name =            " devclass      Package Name
*   i_local_objects_author = SY-UNAME  " author
*   i_language = SY-LANGU       " sy-langu      Language for short text
*   i_db_stored_intf_only = SPACE  " flag
  IMPORTING
    e_interface_list =          " pifdesclis    List of Package Interfaces
  EXCEPTIONS
    API_INIT_FAILED = 1         "               Cannot initialize package API
    API_FAILURE = 2             "
    .  "  PA_GET_PACKAGE_INTERFACE_NAMES

ABAP code example for Function Module PA_GET_PACKAGE_INTERFACE_NAMES

The ABAP code below is a full code listing to execute function module PA_GET_PACKAGE_INTERFACE_NAMES including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_interface_list  
 
 TYPE PIFDESCLIS
.


DATA(ld_i_package_name) = 'Check type of data required'.

DATA(ld_i_local_objects_author) = 'Check type of data required'.

DATA(ld_i_language) = 'Check type of data required'.

DATA(ld_i_db_stored_intf_only) = 'Check type of data required'.
.

CALL FUNCTION 'PA_GET_PACKAGE_INTERFACE_NAMES'
  EXPORTING
    i_package_name =             ld_i_package_name
*   i_local_objects_author =     ld_i_local_objects_author
*   i_language =                 ld_i_language
*   i_db_stored_intf_only =      ld_i_db_stored_intf_only
  IMPORTING
    e_interface_list =           ld_e_interface_list
  EXCEPTIONS
    API_INIT_FAILED =            1
    API_FAILURE =                2
    .  "  PA_GET_PACKAGE_INTERFACE_NAMES

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_interface_list
 
 TYPE PIFDESCLIS ,
ld_i_package_name
 
 TYPE DEVCLASS ,
ld_i_local_objects_author
 
 TYPE AUTHOR ,
ld_i_language
 
 TYPE SY-LANGU ,
ld_i_db_stored_intf_only
 
 TYPE FLAG .


ld_i_package_name = 'Check type of data required'.
ld_i_local_objects_author = 'Check type of data required'.
ld_i_language = 'Check type of data required'.
ld_i_db_stored_intf_only = 'Check type of data required'.