From 0e09bb1c3adbadd4152bd429541191a105ca2992 Mon Sep 17 00:00:00 2001
From: Daniel Reger <16720986+danrega@users.noreply.github.com>
Date: Wed, 7 Dec 2022 10:26:47 +0100
Subject: [PATCH] Fix typo in EML sheet

---
 08_EML_ABAP_for_RAP.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/08_EML_ABAP_for_RAP.md b/08_EML_ABAP_for_RAP.md
index 8ea5298..24c2fd3 100644
--- a/08_EML_ABAP_for_RAP.md
+++ b/08_EML_ABAP_for_RAP.md
@@ -1041,7 +1041,7 @@ instances](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?
         the RAP interaction phase and the early phase of the [RAP save sequence](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenrap_save_seq_glosry.htm "Glossary Entry").
     -   In this case, you can use `%key` to hold the preliminary
         keys or use a preliminary ID in the dedicated component
-        [`%key`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapderived_types_pid.htm)
+        [`%pid`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapderived_types_pid.htm)
         which is of type `ABP_BEHV_PID` and
         only available in late numbering scenarios.
     -   Similar to above, to uniquely identify RAP BO instances in late