Thanks for making such a good content. I have one question, I know ABAP and JAVASCRIPT. Which one should I go for SAP UI5 or RAP or Which one is good as per SAP perspective. Do we have any Limitation in RAP. Its so confusing always.
Thanks for these wonderfully crafted videos. One questions, in which version of S4HANA on premise, these different artifacts of RAP such as Metadata Extensions, behavior definitions etc are covered? Is it immediately after edition 2021?
Hi Bro, I always wonder about your learnings. I just want to know from where you are learning all these advanced technologies. If you could suggest on this, it will be more helpful for my technical growth.
Hi brother, What are the prerequisites to leans Abap rap???..... I don't know odata knowledge....can i learn rap with out odata knowledge........ waiting for your reply.....thanks in advance
It's not mandatory to know OData to learn RAP. But if you idea then it will be good. Somewhere your application failed then we can easily analyze the things .You can watch below playlist if you want to learn OData : - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-YP0I0qC26oI.html
I didn't tell that in context diff between RAP and CAP . I told instead of SEGW we have to use RAP. This will help you further RAP vs CAP :- www.linkedin.com/posts/ram-niwas-04_sapdevelopment-saprap-sapcap-activity-7196392710474219520-gD8s?
Certainly! When localizing your RAP (ABAP RESTful Application Programming) application in Visual Studio Code (VS Code), you need to consider both the backend and frontend aspects. Let’s break it down: Backend Localization (SE63): For backend localization, use transaction code SE63. Create or modify the translation for your texts (labels, messages, etc.) in the desired languages (e.g., ‘EN’ and ‘AR’). Ensure that you use the correct text elements (e.g., @i18n>RequestNo) in your RAP annotations. The backend localization ensures that the correct language is used based on the user’s logon language. Frontend Localization (UI5): In your UI5 app, use the i18n model to handle frontend localization. Define your texts in the i18n.properties files for each language. Use the appropriate keys (e.g., RequestNo) in your UI5 views. The frontend localization ensures that the UI displays the correct language based on the user’s preferences. Remember to synchronize the backend and frontend translations to achieve consistent localization.
