If you are a Duet Enterprise 1.0 customer and you are planning to develop your own custom solution, then this blog is for you.
In the past couple of month I have seen some questions coming across my desk and the forum that indicate that not all of you are using the latest development approach recommended by SAP. If you are starting a new development project I would like to point you to the most current and relevant resources available:
Start with the Development Introduction and pay special attention to the fact that the OData Service needs to be built with the Service Builder. If you are not yet using this tool, then upgrade your system and use the Service Builder (transaction SEGW) for all new development.
In chapter 4, the guide outlines the Code-based Implementation approach. You are not limited to this approach. You can build your OData Service in various ways the Service Builder allows you to, including the code-free approaches via the RFC/BOR Mapping feature. Some limitations are documented in note 1834091.
SAP NetWeaver Gateway 2.0 SP7:
The above documents mention SAP NetWeaver Gateway 2.0 SP5 as the minimum requirement. By now SP7 is available and should be applied as it contains a number of fixes for the BDC Browser, including the following notes:
1825793: ODC SOAP Bridge – Read call does not work
1838165: BDC Browser: Long names causing problems
1835385: Handling filterable flags for entity sets in BDC
1825315: Handling filterable flags for properties in BDC Browser
1841026: Changes in the READ/DELETE/UPDATE/LIST templates
1853703: Composite Key Handling in BDC Browser
Duet Enterprise Forum:
Should you have any questions or face challenges during your development, then check out our Duet Enterprise Forum where you might find answers and can post your questions.