ARCHITECTAdvanced
RAP Basics
Master ABAP RAP fundamentals with CDS root views, behavior definitions, managed and unmanaged scenarios, actions, determinations, validations, EML, draft, locking, authorization and service binding.
Overview
Master ABAP RAP fundamentals with CDS root views, behavior definitions, managed and unmanaged scenarios, actions, determinations, validations, EML, draft, locking, authorization and service binding.
Lessons in this topic
- Behavior Implementation and Behavior PoolUnderstand where custom RAP logic is implemented in behavior pools.
- Managed vs Unmanaged ScenariosChoosing the right RAP flavour.
- Actions, Determinations and ValidationsBusiness logic hooks in behaviour implementations.
- Actions, Determinations and ValidationsUse actions for explicit operations, determinations for automatic derivation and validations for business checks.
- EML: Entity Manipulation LanguageUse EML to read and modify RAP business objects safely.
- Draft, Locking and Authorization in RAPUnderstand draft-enabled apps, locks and authorization checks in RAP.
- RAP Architecture: CDS, Behavior and Service ExposureUnderstand the core RAP building blocks: CDS entity, behavior definition, behavior implementation, service definition and service binding.
- Managed vs Unmanaged RAP ScenariosChoose managed or unmanaged RAP based on persistence and business logic control.
- Root Entity, Child Entity and CompositionModel business objects using root entities, child entities and composition relationships.
- Behavior Definition: CRUD, Fields and FeaturesUnderstand how behavior definitions control what users can do with a RAP business object.
- Service Definition, Service Binding and OData ExposureExpose RAP business objects as OData services using service definition and service binding.
Interview questions covered
- How does RAP fit S/4HANA Clean Core?
- Difference between managed and unmanaged.
- What is a determination?
- How do you expose a RAP service to Fiori?
- What is the difference between action, determination and validation in RAP?
- RAP action returns 'business logic disabled'. Why?
- App needs offline capability. Approach?
- How would you design a RAP business object with header and items?
- What is RAP?
- How do you migrate a classic transaction to RAP?
- What is the role of behavior definition in RAP?
- What is RAP in SAP ABAP?
- Explain the difference between managed and unmanaged RAP business objects.
- Why should direct database updates be avoided for RAP business objects?
- When would you choose managed RAP and when would you choose unmanaged RAP?