SAP KEIY_READ_PRECP1 Function Module for NOTRANSL: Planversionen für Top-Objekt lesen
KEIY_READ_PRECP1 is a standard keiy read precp1 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: Planversionen für Top-Objekt 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 precp1 FM, simply by entering the name KEIY_READ_PRECP1 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_PRECP1 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_PRECP1'"NOTRANSL: Planversionen für Top-Objekt lesen.
EXPORTING
ID_TOP = "Top Object
* ID_VERSN = "Version
IMPORTING
ET_PRECP1 = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING Parameters details for KEIY_READ_PRECP1
ID_TOP - Top Object
Data type: J_OBJNROptional: No
Call by Reference: Yes
ID_VERSN - Version
Data type: VERSNOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for KEIY_READ_PRECP1
ET_PRECP1 - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: KEIY_TT_PRECP1Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for KEIY_READ_PRECP1 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_top | TYPE J_OBJNR, " | |||
| lv_et_precp1 | TYPE KEIY_TT_PRECP1, " | |||
| lv_id_versn | TYPE VERSN. " |
|   CALL FUNCTION 'KEIY_READ_PRECP1' "NOTRANSL: Planversionen für Top-Objekt lesen |
| EXPORTING | ||
| ID_TOP | = lv_id_top | |
| ID_VERSN | = lv_id_versn | |
| IMPORTING | ||
| ET_PRECP1 | = lv_et_precp1 | |
| . " KEIY_READ_PRECP1 | ||
ABAP code using 7.40 inline data declarations to call FM KEIY_READ_PRECP1
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