" Vocabulary Annotation FunctionĭATA: lo_fun_param TYPE REF TO /iwbep/if_mgw_vocan_fun_param. " Vocabulary Annotation CollectionĭATA: lo_function TYPE REF TO /iwbep/if_mgw_vocan_function. " Vocabulary AnnotationĭATA: lo_collection TYPE REF TO /iwbep/if_mgw_vocan_collection. " Vocabulary Annotation TargetĭATA: lo_annotation TYPE REF TO /iwbep/if_mgw_vocan_annotation. " Vocabulary Annotation TargetĭATA: lo_ann_target2 TYPE REF TO /iwbep/if_mgw_vocan_ann_target.
Add annotations snapgene code#
Where we can start to redefine the DEFINE method.Īfter calling the DEFINE method of the superclass the code starts with some definitions.ĭATA: lo_ann_target TYPE REF TO /iwbep/if_mgw_vocan_ann_target. This opens the ABAP Development Tools in Eclipse In order to create these annoations we are going to implement the DEFINE method of the model provider extenstion class (MPC_EXT) of our OData service implementation. In the Service Builder we expand the folder Runtime Artifacts, select the class with the extension MPC_EXT class and select Go to ABAP Workbench from the context menue. The gross amount is highlighted as a data point (green) whereas the title of the object page is titled as SalesOrder (blue). Here some information from the sales order header such as Salesorder number, Customer number, lifecycle status and the last change date is shown in the header of the object page (red). When clicking on on list entry we are using the navigation property ToItems and the details of the selected sales order is displayed on the object page. The header of this list is named SalesOrders. OData service development with SAP Gateway – code-based service development – Part Iįrom the entity set SalesOrderSet we show the columns Salesorder, Customer and Gross amount together with the C urrency by default. This app uses the OData service that I have described in my blog
The following screen shot shows the first screen of the resulting SAP Fiori application which is based on the List Report Page and Object Page from Fiori elements (aka Smart Templates). When upgrading to SAP NetWeaver 750 or higher you can move your implementation into CDS as well. The use case as mentioned above for this scenario are customers and partners that want to build OData services based on SAP NetWeaver 740 where no support for annotations in CDS views is available.
I found however that there is not much information available around this topic … so I decided to write this blog. To add support for annotaions in 740 backends you can used code based implementation. So you can start building CDS views for your OData services in 740. Nevertheless customers and partners can leverage CDS views as a datasource for OData services already in SAP NetWeaver 740 if they are using service implementation using CDS views as mapped datasources. While with SAP NetWeaver 750 and higher you can add annotations within the CDS DDL source code there is no such support available for SAP NetWeaver 740. In a recent partner workshop I was asked how one can add annotations to an OData service when your system runs on top of SAP NetWeaver 740.
0 kommentar(er)
