All topics
RAP_CDS_ODATAintermediate

EML

Use RAP Entity Manipulation Language to read and modify RAP business objects directly from ABAP with type-safe operations. Learn READ/MODIFY ENTITIES, create-by-association, actions, MAPPED/FAILED/REPORTED, local mode and transaction handling with COMMIT ENTITIES.

Overview

Use RAP Entity Manipulation Language to read and modify RAP business objects directly from ABAP with type-safe operations. Learn READ/MODIFY ENTITIES, create-by-association, actions, MAPPED/FAILED/REPORTED, local mode and transaction handling with COMMIT ENTITIES.

Lessons in this topic

Interview questions covered

  • A mass-upload program inserts purchase requests directly into the BO tables. Requests appear in the app without status or number and some violate rules. How do you rewrite it?
  • What is EML, which statements does it have, and why should programs use EML instead of updating tables directly?
  • Explain %cid, %cid_ref, MAPPED, FAILED and REPORTED using a deep create of a header with two items.
  • Your EML MODIFY returns no FAILED entries, but the data is not saved. Why, and how should the program evaluate results?
  • What does IN LOCAL MODE skip, what does it not skip, and why is it needed inside a behavior pool?
  • A purchase request action must create a budget reservation in a finance BO, but the user lacks finance authorization. A developer wants to use IN LOCAL MODE or write the table directly. What do you advise?
  • How do two RAP business objects stay consistent when an action in one creates data in the other?
  • A program creates records in two RAP BOs and commits after each. When the second fails, orphans remain. How do you fix the program?
  • Why must EML-based tests of validations call COMMIT ENTITIES, and how do you keep such tests isolated?
  • Design a test suite for a RAP business object before go-live. What must it cover?

Related topics

Interview questions on this topic