Thanks for the Input. Love those calls :) Would like if you would speak about "what can RAP and what RAP cannot" a little bit slower and maybe with more examples :) Maybe more painful points to be more transparent. Thanks!
@TheThop13 жыл бұрын
Hardly developers need optional parameter in CDS views
@tanmoymondal17263 жыл бұрын
Hi All...Thank you to the team for the session!
@finetechie55503 жыл бұрын
Thanks for sharing on LinkedIn
@NelsonMauricioMirandaGuardiola3 жыл бұрын
This was an excellent video. RAP is pretty nice but it has high steep learning and it will take time to adapt to this technology. Check EML as an example. I also think that it seems not ready yet but for me It's the right path. I'm excited for the future of ABAP. Keep going guys. You are doing a great job.
@sunilbestha77192 жыл бұрын
Do u think ABAP has future. I don't think so. Its just the matter of time. SAP is leaning more towards open source platforms something which ABAP consultants must be worried about
@dumakhumalo35778 ай бұрын
Is this correct? RAP can also be used as a BAPI, also in background jobs?
@sapdevs8 ай бұрын
The RAP business object becomes the API replacing the BAPI. We can use EML(Entity Manipulation Language) to interact with that RAP business objects, which is just new ABAP syntax that allows you to perform CRUD operations on the RAP business object. So instead of calling the BAPI function module, you would just use statements like MODIFY ENTITY...