SAP KEIY_READ_PRECP0 Function Module for NOTRANSL: Customizing für Objektart lesen
KEIY_READ_PRECP0 is a standard keiy read precp0 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: Customizing für Objektart 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 keiy read precp0 FM, simply by entering the name KEIY_READ_PRECP0 into the relevant SAP transaction such as SE37 or SE38.
Function Group: KEIY
Program Name: SAPLKEIY
Main Program: SAPLKEIY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function KEIY_READ_PRECP0 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 'KEIY_READ_PRECP0'"NOTRANSL: Customizing für Objektart lesen.
EXPORTING
ID_OBART = "Object Type
ID_KOKRS = "Controlling Area
IMPORTING
ET_PRECP0 = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING Parameters details for KEIY_READ_PRECP0
ID_OBART - Object Type
Data type: J_OBARTOptional: No
Call by Reference: Yes
ID_KOKRS - Controlling Area
Data type: KOKRSOptional: No
Call by Reference: Yes
EXPORTING Parameters details for KEIY_READ_PRECP0
ET_PRECP0 - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: KEIY_TT_PRECP0Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for KEIY_READ_PRECP0 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_id_obart | TYPE J_OBART, " | |||
| lv_et_precp0 | TYPE KEIY_TT_PRECP0, " | |||
| lv_id_kokrs | TYPE KOKRS. " |
|   CALL FUNCTION 'KEIY_READ_PRECP0' "NOTRANSL: Customizing für Objektart lesen |
| EXPORTING | ||
| ID_OBART | = lv_id_obart | |
| ID_KOKRS | = lv_id_kokrs | |
| IMPORTING | ||
| ET_PRECP0 | = lv_et_precp0 | |
| . " KEIY_READ_PRECP0 | ||
ABAP code using 7.40 inline data declarations to call FM KEIY_READ_PRECP0
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