SAP CN_LDST_CURRENT_OBJECT_GET Function Module for NOTRANSL: Globale Objektdaten lesen
CN_LDST_CURRENT_OBJECT_GET is a standard cn ldst current object 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 NOTRANSL: Globale Objektdaten lesen 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 cn ldst current object get FM, simply by entering the name CN_LDST_CURRENT_OBJECT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CN_LDST
Program Name: SAPLCN_LDST
Main Program: SAPLCN_LDST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CN_LDST_CURRENT_OBJECT_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 'CN_LDST_CURRENT_OBJECT_GET'"NOTRANSL: Globale Objektdaten lesen.
IMPORTING
EV_APPLICATION = "Application of Language-Dependent Short Texts
EV_OBJECT = "Indicator for Object Type
EV_OBJNR = "Object Number
EXCEPTIONS
NO_VALUES = 1
EXPORTING Parameters details for CN_LDST_CURRENT_OBJECT_GET
EV_APPLICATION - Application of Language-Dependent Short Texts
Data type: CNLDST_APPLICOptional: No
Call by Reference: Yes
EV_OBJECT - Indicator for Object Type
Data type: CNLDST_OBJECTOptional: No
Call by Reference: Yes
EV_OBJNR - Object Number
Data type: J_OBJNROptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_VALUES -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CN_LDST_CURRENT_OBJECT_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_no_values | TYPE STRING, " | |||
| lv_ev_application | TYPE CNLDST_APPLIC, " | |||
| lv_ev_object | TYPE CNLDST_OBJECT, " | |||
| lv_ev_objnr | TYPE J_OBJNR. " |
|   CALL FUNCTION 'CN_LDST_CURRENT_OBJECT_GET' "NOTRANSL: Globale Objektdaten lesen |
| IMPORTING | ||
| EV_APPLICATION | = lv_ev_application | |
| EV_OBJECT | = lv_ev_object | |
| EV_OBJNR | = lv_ev_objnr | |
| EXCEPTIONS | ||
| NO_VALUES = 1 | ||
| . " CN_LDST_CURRENT_OBJECT_GET | ||
ABAP code using 7.40 inline data declarations to call FM CN_LDST_CURRENT_OBJECT_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