A rap bo interface is a layer on top of the base bo that is an interface for stable consumption and is usually released as api. Direct access to sap standard database tables (like kna1) is replaced by. All views connected via associations and compositions must be exposed;
In a bdef extension with the addition using interface, only. Discover best practices for local and remote event consumption I was wondering about the sense of base views in an rap context:
Since we are done with cds views now we will start creating composite cds views. In this blog post, i would like to share my knowledge on how operation augmentation can be used to implement consumption specific requirement in rap abap. Most of the documentation and tutorials i read claim that in rap a single entity should be composed out of. Rap relies heavily on core data services (cds) views to define and consume database objects.
Otherwise, respective projections won’t be available after. There are two views which we will be creating going further composite view and. Learn how to effectively consume abap rap events in this comprehensive guide.