Think RICEFW with LCNC way

[Pankaj1]

Hi Experts,

Does it make senses to think of RICEFW objects(ABAP developments) from LCNC perspective?
For example: making an ALV(ABAP report) or module pool or workflows via Appgyver/BAS/Process automation instead of ABAP approach.

How we can compare the benefits specially cost i.e. doing development with LCNC costs $X this much etc.?

Also, one more concern different from above question that can we utilize on-premise OData in Appgyver?

[Pankaj1]

Thanks 9958e4b6df99431a84a41b015b639ac8
After analyzing it so far, i also have the same thought on this topic. I believe we can't strictly say do RICEFW this way but if any user wants to create an app which he/she thinks fulfill the job of a let's say.. report.. by developing a LCNC app, it should be fine.

[SergioG_TX]

Hi Pankaj,

Personally I do not think you should think of RICEFW for LCNC. The reason for that is bc you have 2 different technology stacks and you're doing a different implementation. You could instead use a tech spec specifying the screens for your application, the data sources, the behavior of the app, the security implemented and any integration to other systems. you can use any OData or REST API to feed data to your LCNC application.

There are plenty of examples and documentation about AppGyver now. Here are some I have done

https://blogs.sap.com/2022/01/06/appgyver-to-code-or-not-to-code-that-is-the-question/

https://blogs.sap.com/2022/01/14/appgyver-master-detail-scenario/

https://blogs.sap.com/2022/05/22/dadiambored-no-code-challenge/