SAP PA_DETERMINE_AKB_INTERFACE Function Module for

Search SAP Function Modules

PA_DETERMINE_AKB_INTERFACE is a standard pa determine akb interface 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 determine akb interface FM, simply by entering the name PA_DETERMINE_AKB_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

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

Function PA_DETERMINE_AKB_INTERFACE 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_DETERMINE_AKB_INTERFACE'"
  EXPORTING
   I_OBJ_TYPE =  "Object Type
   I_OBJ_NAME =  "Object Name in Object Directory
*  I_TRANSPORT_REQUEST =  "Request/Task
*  I_DIALOG =  "Dialog
*  I_CREATE_AKB_INTERFACE = 'X' "

 IMPORTING
   E_AKB_INTERFACE =  "Package Interface
   E_TRANSPORT_REQUEST =  "Request/Task

EXCEPTIONS
   CANCELED = 1    NOT_AUTHORIZED = 2    NOT_EXISTING = 3    MAIN_PACKAGE_NOT_PART_OF_AKB = 4    INTERNAL_ERROR = 5 

.

IMPORTING Parameters details for PA_DETERMINE_AKB_INTERFACE

I_OBJ_TYPE - Object Type

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

I_OBJ_NAME - Object Name in Object Directory

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

I_TRANSPORT_REQUEST - Request/Task

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

I_DIALOG - Dialog

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

I_CREATE_AKB_INTERFACE -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PA_DETERMINE_AKB_INTERFACE

E_AKB_INTERFACE - Package Interface

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

E_TRANSPORT_REQUEST - Request/Task

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

EXCEPTIONS details

CANCELED - Function aborted

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED - Insufficient authorization

Data type:
Optional: No
Call by Reference: Yes

NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

MAIN_PACKAGE_NOT_PART_OF_AKB -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Internal Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PA_DETERMINE_AKB_INTERFACE 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.

ABAP code using 7.40 inline data declarations to call FM PA_DETERMINE_AKB_INTERFACE

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