Showing results for 
Search instead for 
Did you mean: 

Another 'How do I lock resource with Gateway' Question - and SAP UX roadmap 2015Q3

0 Kudos

Hi Experts,

So far, based on various discussions/blogs in SCN, it looks like future direction application development is going to be sap Fiori UX (i.e. gateway/UI5 combo).

So what is going to happen to state-full application development in the future ?

I am not sure if this means we have to ditch state-full application development or Gatway/UI5 is going to support State-full application development.

What is going to be the direction for complex standard SAP applications that requires pessimistic locking ? will SAP use fiori or FPM ?

Every time I see discussions about concurrency control with Gateway/UI5 - only answer seems to be convincing customers to use optimistic locking or tricking soft state to make application state-full.

I did notice this slide in SAP UX roadmap 2015Q3

  • SAPUI5
    • Creation of consumer-grade, stateless apps
  • Floorplan Manager / Web Dynpro ABAP
    • Creation of functional, stateful apps

Meanwhile Fiori floor plans have details on how to display locked records.

(look for pessimistic locking at the bottom of the page). This is really confusing.

So My question is

For complex state-full applications that requires locking, should I still stick with Floor Plan Manager ?

Or is there a new feature or option coming in the future to support complex state-full application in sap Fiori (i.e. gateway/ui5)?

Is there any SAP document that gives clear distinctions for these kind of UX decisions (specifically for developers) ?



Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Just to add - I noticed a slide in SAP Teched 2015 about coming support for fully transnational application in Fiori. I am searching for slide and couldn't find it.

I agree that ABAP channels could be the solution we are looking for.

Active Contributor
0 Kudos

Hi Joseph,

I personally do not expect SAP to support stateful behavior for Fiori. Because this would go against REST/OData.

More than an actual pessimistic locking, I think what is required is a notification that someone is already editing it. I would expect a solution by SAP based on websockets and notifications in future.



Active Participant
0 Kudos

Hi Austin,

UI5 resides on OData protocol,which is REST = stateless. Not designed to support stateful applications.In upcoming years SAP most probably will not lets you to keep data between interactions,because they still not support and ready with OData v3 and  v4 in SAP GW.  (In and php this is different,there you can keep data in the context between interactios).Fully agree, really hard to implement UI5 apps to call functions and frameworks which were built as result of 10 years development,having multiple object layers all including their individual buffering=state. Like function group memory. You need to save your data in z tables first in UI5,and call the functions / APIs afterwards with this data. Lot of the functions and BAPIs don't let you to save business documents having errors,but what to do with your UI5 data then, which would lost after the roundtrip ? No other choice just Z tables. Using old functions managing complex documents with different fragments you need to use still FPM. Thats why for example SAP needs to rewrite most common apllications as code name S/4 for HANA ,Simple Finance etc.Believe me, due complexity and amount of 10-20 years of source code done,the full rewrite will never be happen. Instead we'll use and develop SAP GUI,BSP,WebDynpro,FPM,UI5 paralell at the same time. But again sg new can be sold to customers,which is looking nice. One advantage is that EP portal can be ignored in future in lot of cases,instead FLP and NW Business client can be combined. Enough from the stories,I hope I could answer your question.

You can lock your Z table entries with a flag,called change version,and remove this flag when user explicitly saves the document in UI5. Of course add change user:) as table component too,to be able to decide who is locking the entry.