SAP K_LOGSYSTEM_GET Function Module for Determine Logical System for Object
K_LOGSYSTEM_GET is a standard k logsystem 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 Logical System for 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 logsystem get FM, simply by entering the name K_LOGSYSTEM_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: KALL
Program Name: SAPLKALL
Main Program: SAPLKALL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function K_LOGSYSTEM_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_LOGSYSTEM_GET'"Determine Logical System for Object.
EXPORTING
I_KOKRS = "Controlling Area
I_OBJNR = "Object Number
* I_OBJ_LOGSYS = "Logical System from Object Master (COIOB)
* I_TKA01 = "Controlling Area Control Data
* I_T000 = "Client Control Data
IMPORTING
E_LOGSYS = "Logical System for Transaction Data
E_LOGSYS_MASTER = "Logical System for Master Data Maintenance
E_LOGSYS_LOCAL = "Logical System of Current Client
E_LOGSYS_CENTRAL = "Central System of Controlling Area
IMPORTING Parameters details for K_LOGSYSTEM_GET
I_KOKRS - Controlling Area
Data type: TKA01-KOKRSOptional: No
Call by Reference: Yes
I_OBJNR - Object Number
Data type: ONR00-OBJNROptional: No
Call by Reference: Yes
I_OBJ_LOGSYS - Logical System from Object Master (COIOB)
Data type: T000-LOGSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TKA01 - Controlling Area Control Data
Data type: TKA01Optional: Yes
Call by Reference: Yes
I_T000 - Client Control Data
Data type: T000Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for K_LOGSYSTEM_GET
E_LOGSYS - Logical System for Transaction Data
Data type: T000-LOGSYSOptional: No
Call by Reference: Yes
E_LOGSYS_MASTER - Logical System for Master Data Maintenance
Data type: T000-LOGSYSOptional: No
Call by Reference: Yes
E_LOGSYS_LOCAL - Logical System of Current Client
Data type: T000-LOGSYSOptional: No
Call by Reference: Yes
E_LOGSYS_CENTRAL - Central System of Controlling Area
Data type: T000-LOGSYSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for K_LOGSYSTEM_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.| DATA: | ||||
| lv_i_kokrs | TYPE TKA01-KOKRS, " | |||
| lv_e_logsys | TYPE T000-LOGSYS, " | |||
| lv_i_objnr | TYPE ONR00-OBJNR, " | |||
| lv_e_logsys_master | TYPE T000-LOGSYS, " | |||
| lv_i_obj_logsys | TYPE T000-LOGSYS, " | |||
| lv_e_logsys_local | TYPE T000-LOGSYS, " | |||
| lv_i_tka01 | TYPE TKA01, " | |||
| lv_e_logsys_central | TYPE T000-LOGSYS, " | |||
| lv_i_t000 | TYPE T000. " |
|   CALL FUNCTION 'K_LOGSYSTEM_GET' "Determine Logical System for Object |
| EXPORTING | ||
| I_KOKRS | = lv_i_kokrs | |
| I_OBJNR | = lv_i_objnr | |
| I_OBJ_LOGSYS | = lv_i_obj_logsys | |
| I_TKA01 | = lv_i_tka01 | |
| I_T000 | = lv_i_t000 | |
| IMPORTING | ||
| E_LOGSYS | = lv_e_logsys | |
| E_LOGSYS_MASTER | = lv_e_logsys_master | |
| E_LOGSYS_LOCAL | = lv_e_logsys_local | |
| E_LOGSYS_CENTRAL | = lv_e_logsys_central | |
| . " K_LOGSYSTEM_GET | ||
ABAP code using 7.40 inline data declarations to call FM K_LOGSYSTEM_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.| "SELECT single KOKRS FROM TKA01 INTO @DATA(ld_i_kokrs). | ||||
| "SELECT single LOGSYS FROM T000 INTO @DATA(ld_e_logsys). | ||||
| "SELECT single OBJNR FROM ONR00 INTO @DATA(ld_i_objnr). | ||||
| "SELECT single LOGSYS FROM T000 INTO @DATA(ld_e_logsys_master). | ||||
| "SELECT single LOGSYS FROM T000 INTO @DATA(ld_i_obj_logsys). | ||||
| "SELECT single LOGSYS FROM T000 INTO @DATA(ld_e_logsys_local). | ||||
| "SELECT single LOGSYS FROM T000 INTO @DATA(ld_e_logsys_central). | ||||
Search for further information about these or an SAP related objects