SAP AKB_GET_OBJECT_INFO Function Module for









AKB_GET_OBJECT_INFO is a standard akb get object info 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 akb get object info FM, simply by entering the name AKB_GET_OBJECT_INFO 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): Remote-Enabled
Update:



Function AKB_GET_OBJECT_INFO 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 'AKB_GET_OBJECT_INFO'"
  EXPORTING
   OBJ_TYPE =  "Object Type
   OBJ_NAME =  "Object Name in Object Directory
*  SUB_TYPE =  "
*  SUB_NAME =  "
*  USER_PERMISSIONS = ' ' "
*  CHECK_CLASSFREEZING = ' ' "
*  CHECK_TRKORR = ' ' "
*  RFCDEST =  "
*  USE_FALLBACK = ' ' "

 IMPORTING
   OBJECT =  "Object in AKB Context
   COMPONENT =  "Application Component
   PACKET =  "Application Package

EXCEPTIONS
   OBJECT_NOT_FOUND = 1    RFC_ERROR = 2
.



IMPORTING Parameters details for AKB_GET_OBJECT_INFO

OBJ_TYPE - Object Type

Data type: TROBJTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

OBJ_NAME - Object Name in Object Directory

Data type: SOBJ_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

SUB_TYPE -

Data type: TROBJTYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUB_NAME -

Data type: SEOCPDLONG
Optional: Yes
Call by Reference: No ( called with pass by value option)

USER_PERMISSIONS -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHECK_CLASSFREEZING -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHECK_TRKORR -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

RFCDEST -

Data type: RFCDEST
Optional: Yes
Call by Reference: No ( called with pass by value option)

USE_FALLBACK -

Data type: FLAG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for AKB_GET_OBJECT_INFO

OBJECT - Object in AKB Context

Data type: AKB_OBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

COMPONENT - Application Component

Data type: UFPS_POSID
Optional: No
Call by Reference: No ( called with pass by value option)

PACKET - Application Package

Data type: DEVCLASS
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OBJECT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for AKB_GET_OBJECT_INFO 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_object  TYPE AKB_OBJECT, "   
lv_obj_type  TYPE TROBJTYPE, "   
lv_object_not_found  TYPE TROBJTYPE, "   
lv_obj_name  TYPE SOBJ_NAME, "   
lv_component  TYPE UFPS_POSID, "   
lv_rfc_error  TYPE UFPS_POSID, "   
lv_packet  TYPE DEVCLASS, "   
lv_sub_type  TYPE TROBJTYPE, "   
lv_sub_name  TYPE SEOCPDLONG, "   
lv_user_permissions  TYPE FLAG, "   ' '
lv_check_classfreezing  TYPE FLAG, "   ' '
lv_check_trkorr  TYPE FLAG, "   ' '
lv_rfcdest  TYPE RFCDEST, "   
lv_use_fallback  TYPE FLAG. "   ' '

  CALL FUNCTION 'AKB_GET_OBJECT_INFO'  "
    EXPORTING
         OBJ_TYPE = lv_obj_type
         OBJ_NAME = lv_obj_name
         SUB_TYPE = lv_sub_type
         SUB_NAME = lv_sub_name
         USER_PERMISSIONS = lv_user_permissions
         CHECK_CLASSFREEZING = lv_check_classfreezing
         CHECK_TRKORR = lv_check_trkorr
         RFCDEST = lv_rfcdest
         USE_FALLBACK = lv_use_fallback
    IMPORTING
         OBJECT = lv_object
         COMPONENT = lv_component
         PACKET = lv_packet
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        RFC_ERROR = 2
. " AKB_GET_OBJECT_INFO




ABAP code using 7.40 inline data declarations to call FM AKB_GET_OBJECT_INFO

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_user_permissions) = ' '.
 
DATA(ld_check_classfreezing) = ' '.
 
DATA(ld_check_trkorr) = ' '.
 
 
DATA(ld_use_fallback) = ' '.
 


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!