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.
Believe or not, there is a fine graded Message Handling concept in SAP TM. Messages sent through BOPF – FBI- FPM Environment may have certain visibility settings. This is a control demand based on user experitse or area. Key users may want different level of message detailization than other users for example. You can setup the minimum severity, level of detail or problem class to display, such as to display errors only or even warnings raised by validations. You can activate to save an application log, which can become handy during troubleshooting.
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.
If you ever worked with SAP GUI, you know the strong built-in capability which validates user input format based on the underlying Domain settings (DOMA) embedded into the Data Elemenet behind the user input field. Everything is automatic, comes out-of-the box.
XML Views represent the layout much better than JS Views in UI5. By default, lists etc. load a restricted number of items through aggregation binding. You can extend this without programming within XML Views. It requires configuration of the binding with the length parameter. This will set the $top option in the underlying OData query.
You want to disable caching at the client side. For example the web browser of the end user will not store the server response data You collected and sent back in Your Data Provider class. After project generation in SEGW transaction, the DPC_EXT class is ready to implement the method redefinitions to build responses for the client(get_entity,get_entityset etc.).