Hello Ram,
Below will describe how you can handle attachments as part of Media Information :
How To Upload and Download Files Using SAP NW Gateway SP06
How to Read Photo from SAP system using SAP Gateway
Uploading Files to SAP GW, Downloading Files from SAP GW - New Techniques
Regards,
Ashwin
Hello Ram Pathak,
Your URI will not hit get_entityset, If you want to hit get entity set then try keeping brackets empty..
Hi everybody,
"you are not authorized to create project"
Could you please help me to solve this issue?
Many thanks in advance!
Best
Ali
Hello Ali,
You do not have authorization to create the project. Please take the logs of SU53 and share it with Basis/Security team so that they can assign the missing authorizations.
Regards,
Ashwin
Hi Ashwin,
Many thanks for your prompt suport!
Display the authorization looks like:
It seems that I do not have the authorization to create the project.
I will share it shortly with the basis team.
Regards,
Ali
Hi Shreedhar,
In the URL section, try removing the Entityset('VehicleDetail?$format=json') and pass only the service URL.
Regards,
Ekansh
Hello,
My question is about best practices when you create a oData service in order to build a fiori app based on this service.
I know that the normal way would be to create a oData independently to the app that use the service, but when I look at standard fiori app, I can see that they build one oData service for one Fiori app. The oData service is not build to be reuse by another application.
For example, for the sales order, the header look like this :
order number
customer number
customer name
customer address
Ship to number
ship to name
Ship to address
total amount
currency
As you can see, custom and ship to name and address are in the entity header, although there should be only the customer and ship to number and an association to an entity customer with the name and address :
Header
order number
customer number
Ship to number
total amount
currency
Customer
customer number
customer name
customer address
the second model looks better and is more like a database model, but the SAPUI5 application is easier to develop with the first model. Also, with the second model, we would have to implement more methods (basic relation) in order to improve performance.
I started my development with the first option (the oData look like what I want to display in the screen instead of a database model), but I would like to know if it is a good practice.
thank you
You can have a look here.
SAPUI5 – Best practises- Do’s & don’t do’s
FIORI is a UI5 application.So , UI5 best practices are also applicable hence sharing the doc.
If there is no navigation from once screen to another screen(and if you are not expecting it in future ) , there is no point in keeping them as separate entity and consume them using odata association . Let it be a win-win design in terms of flexibility and performance .
Cheers
Thanks Sreehari,
you said : "If there is no navigation from once screen to another screen(and if you are not expecting it in future ) "
But :
1. Even if there is no navigation from one screen to another, we could expect to have a oData with multiple entities and select from all theses entities to build our screen. in the example that I gave, select header entity, customer entity for customer and customer entity for ship to.
2. I can't expect what will happen in the future, that's why it may be more interesting to have a oData model which is more flexible.
As I don't have a lot of experience in SAPUI5/oData, I can't have the necessary distance to know what is the best practice.
Thanks a Lot Ekash.
Issue is resolved now 
.. hats off to you
HI Louis,
From the perspective of Fiori app, the general principle is "one app per use case".
From the perspective of ODATA services, the general principle is "one service per app".
In addition to the sites mentioned by Krishna, you can also refer to to the following site for understanding UX and Fiori design principles - https://designthinkingwithsap.com/ .
Thanks,
Indrajit
Hi All,
As mentioned in most of the POST to make the service secure, it needs to configure to SSL under Security Requirement tab.
My issue was with Basis configuration and they resolved it.
I was thinking of oData design (the outside-in model you talked about). I didn't find any documentation from SAP that say clearly to use this model (the entity attributes are defined according to the screen).
Hi experts,
I am facing an issue that I can't figure out.
I will try to simplify my problem to make it understandable:
I have two entities, demand and position.
Each position is link to one demand and a demand can be link to several positions.
Demand's table is stored in a real database, when position is stored in a cluster database. The id of the cluster is saved in demand.
I can't have a direct access to the positions because I need to know the id of the cluster, so all my URL are build this way :
.../DemandSet('0')/PositionSet
But when I call this URL, it calls PositionSet_GetEntity instead of PositionSet_GestEntitySet. Does someone have an explanation?
Really appreciate youre help !
Please let me know if you need more information from me.
What about the cardinality ? 1 , 1:N ?
yes 1, 1:N
If you follow the principle of "one service per app", it is up to you whether you want to design the UI first or ODATA model first.
A typical sequence of design and development of Fiori app is -
-> Using SAP Fiori prototyping kit, create mock up of the UI first.
-> Based on the UI mockup, generate an EDMX file as a dummy for the ODATA model and use it for Fiori app UI development using Web IDE.
-> Parallaly another developer can develop the ODATA at the backend.
-> Replace the EDMX file by the actual ODATA model in the Fiori app
Can you share the screen shot of association and navigation created between the entities ?
Good mrg to all of you. i need a help for my query, which is i faced my current company.
my client want to deliver the selected line items from the order.i.e.,, for a particular sales order having 10 line items i want to deliver only 2nd and 5 th line items only. how to this? any one help this query.
Hello experts,
I am having a problem with setting my specific entity as "subscribeable" in my odata service. I am working with two different SAP systems (one is a sandbox and the other is the actual development system).
In my Sandbox system (Version SAPGWFND 740)
It's working just fine. Ticking the checkbox and Generating automatically created the SubscriptionCollection (and NotificationCollection) entities and sets my entity ticked as Subscribable = true in the Define method in the MPC class
However in my Development system (GW_CORE 200 version). Despite ticking the "subscribeable" checkbox nothing seems to be working. The SubscriptionCollection entity is not created, the entity is not set to Subscribeable in the Define method in the MPC, etc.
I am not sure if different versions of the NW Gateway will cause a difference in this. It should also be noted that the Sandbox system was a stand-alone NW Gateway system while the Development system is a Solman system + NW gateway. I am not sure if that is a factor as well.
Kindly advise and warm regards.