Currently I am going through openSAP course on Build Your Own SAP Fiori App in the Cloud and there come across one question about creation of EDMX file.
There are different ways to create edmx file as answered in the course discussion forum by Yoram Friedman
This is a common scenario in many big projects, since you do want to work on the UI in parallel to the team creating the business logic. The best solution is to reach an early agreement on the “interface” between the two and use this as a starting point. If at this stage you want to generate an EDMX schema you can’t do it from the service as the service does not exist yet. You need to either use a third party EDMX generator or use the WebIDE ODATA Model Editor (which is not part of this specific training)
Check out this video: https://www.youtube.com/watch?v=xs0cSan05mw
Now in case if you are not able to use 3rd party EDMX generator tools or find it difficult to use SAP Web IDE OData Model Editor and want to leverage the efforts of OData modelling done on backend OData developer team then there is simple way for it.
Assuming that backend developers (SAP Gateway OData developers) at least started creating OData service using transaction SEGW with properly defined OData artifacts such as entity, entitySet, association/navigation etc. but they do not want to spend time to implement complete backend logic. In such scenarios, if OData service is registered then in Gateway Client transaction /IWFND/GW_CLIENT using $metadata query we can see the complete metadata of OData service as shown below.
You can either select menu Goto –>Service Metadata
Or after executing $metadata, click on Response in Browser
In both cases, it will open the metadata file in the browser as shown below,
Now you can simply save this file as .edmx or .xml and can easily use it for creation of mock data inside your Fiori application from SAP Web IDE.
As shown below, we can use .xml or .edmx file
you can refer 5 easy steps to create a Fiori app using an EDMX file & testing it by leveraging the #SAPWebIDE mock service by Jitendra Kansal for further steps and details.