Using the SAP Netweaver Innovation Package 7.51 sp1 you can implement new data models easily with CDS including full CRUD support, where change operations are managed by the BOPF framework. The BOPF Object is generated based on the Object Model annotations you put in the CDS View at activation.
This solution using SADL shows a BOPF adoptation/consumption, but also demonstrates how-to create your own consumer / framework asking SADL for CDS entity metainformation (Annotations). You have no more boundaries, your only blocker is your own creativity 🙂
“Fiori Elements” is a great opportunity for rapid application development for simple scenarios. In lot of cases ABAP developers maintain domain fixed values to have a drop-down list automatically generated by one of the UI technologies like GUI and WebDynpro. Domain fixed value often represent a Status or something like that, where we can say the values are static. In case of OData services and UI5 such control is not generated automatically, but you need to put annotations in your CDS View to make this working. We’ll use CDS Views in the below snippets, to retrive domain low fixed values and their description. The approach below is not the only one, which can lead to the same result. At the end the Object Page template in Fiori Elements ( or your app importing annotation file) will consider the annotations and display a proper value help.
Fiori applications can retrieve texts and translations both from the backend system and from i18n resource bundle files of the application. However might happen, that these changes do not become immediately active, when users relaunch the applicaion.
Yes, We – developers – are end users in the context of transport management. We use variety of transactions on the surface, like ADT, SE80, SE09, STMS etc. to push our changes to test and production systems. We not developed that transactions, which manage changes variety of object types in the ABAP,BSP repository, DDIC etc, and their transport.
Transport requests, right ? Spending decades with Transport Organizer (SE09…) and import queues (STMS), standard extensions to prevent release with special magic logic. Pretty familiar for all of us. Companies with development guidelines, include variety of rules, what should be the proper description for a transport request. Hunting the right request based on the name. Using external tools to administer business requirements and map corresponding requests. Developers put references in the source code based on predefined rules.
Sometimes You have to recognize, that a where-used list for a given repository object, like constant interfac members, messages or data elements etc. are not working, but You are sure, there must some results. SAP has dedicated index tables for that cross-references, which might not be up to date for whatever reason. Upgrades or broken jobs, which are automatically scheduled after installation at certain events, like accessing the object navigator at first time. They are very time-consuming jobs.
Generating applications using the templates wizard in VSCode
A system connection to onPremise ABAP system may not be established, caused by self-signed certificate of backend System/OData service. This is the case with developer edition of ABAP Systems, or connecting sandbox systems.
Done on Fresh Win 10 installation, nothing installed on the system so far
I need templates for application generation and Source Code Management like Git
VSCode unfortunately provides no support for Adaptation project and WYSIWYG layout editor by Fiori Toolkit, like Business Application Studio(BAS) does. This time no additional feature of BAS is required, I just want to use it for greenfield Fiori development. If you want to do adaptations, you have to go for BAS (decision point) – 16.07.2021
Salvation after 5+ years and variety of technological marriages, ABAP RAP is here finally. Fiori and WebAPI development can take a deep breath. This post is about common and uncommon snippets for ABAP RAP. This post is updated on regular manner.