SAP K_OBJECT_INFORMATION_GET Function Module for Determine Information on a Controlling Object

Search SAP Function Modules

K_OBJECT_INFORMATION_GET is a standard k object information get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Information on a Controlling Object 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 k object information get FM, simply by entering the name K_OBJECT_INFORMATION_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function K_OBJECT_INFORMATION_GET 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 'K_OBJECT_INFORMATION_GET'"Determine Information on a Controlling Object
  EXPORTING
   I_OBJNR =  "Object Number
*  I_GJAHR =  "Fiscal Year

 IMPORTING
   E_OBART =  "Object Type
   E_KOKRS =  "Controlling Area
   E_BUKRS =  "Company Code
   E_FIKRS =  "FM Area
   E_OWAER =  "Object Currency
   E_CURTP =  "Currency Type of the Object Currency
   E_CURK1 =  "Key 1 for Currency Type
   E_CURK2 =  "Key 2 for Currency Type

EXCEPTIONS
   OBJECT_NOT_FOUND = 1    OBJECT_CURRENCY_INCONSISTENT = 2    ORGUNIT_ERROR = 3 

.

IMPORTING Parameters details for K_OBJECT_INFORMATION_GET

I_OBJNR - Object Number

Data type: COEP-OBJNR
Optional: No
Call by Reference: Yes

I_GJAHR - Fiscal Year

Data type: COEP-GJAHR
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for K_OBJECT_INFORMATION_GET

E_OBART - Object Type

Data type: IONR-OBART
Optional: No
Call by Reference: No ( called with pass by value option)

E_KOKRS - Controlling Area

Data type: COEP-KOKRS
Optional: No
Call by Reference: No ( called with pass by value option)

E_BUKRS - Company Code

Data type: COEP-BUKRS
Optional: No
Call by Reference: No ( called with pass by value option)

E_FIKRS - FM Area

Data type: FM01-FIKRS
Optional: No
Call by Reference: No ( called with pass by value option)

E_OWAER - Object Currency

Data type: COEP-OWAER
Optional: No
Call by Reference: No ( called with pass by value option)

E_CURTP - Currency Type of the Object Currency

Data type: ACCCR-CURTP
Optional: No
Call by Reference: No ( called with pass by value option)

E_CURK1 - Key 1 for Currency Type

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

E_CURK2 - Key 2 for Currency Type

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

EXCEPTIONS details

OBJECT_NOT_FOUND - Object Not Found

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

OBJECT_CURRENCY_INCONSISTENT - Object Currency Does Not Match Currency Type

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

ORGUNIT_ERROR - Inconsistency in an Organizational Unit

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

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

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