Lesson 18 Practice — Add Work Notes to the Support Issue BO

Your Support Issue application is currently a single-node draft-enabled RAP BO:

Issue

Extend it to:

Issue
└── Work Notes

A Work Note belongs to exactly one Issue.

The child must participate in:

managed behavior
draft
locking
authorization
DCL
projection
OData V4
Fiori Elements
EML

---

Practice information

Time	About 3 hours
Prerequisite	Lesson 18 guided exercise
Root	ZR_ISSUE_###
Child active table	ZISSNOTE_###
Child CDS	ZR_ISSUE_NOTE_###
Child draft table	ZDISSNOTE_###
Child projection	ZC_ISSUE_NOTE_###
EML class	ZCL_ISSUE_COMP_###

---

1. Target BO

Build:

Issue
└── Work Notes

Use:

Issue
→ root

Work Note
→ child

Cardinality:

Issue 1
→
0..* Work Notes

---

2. Create Child Persistence

Create:

ZISSNOTE_###

Required fields:

client
note_uuid
issue_uuid
note_no
note_text
note_category
local_last_changed_at

Recommended types:

client                → ABAP client type
note_uuid             → SYSUUID_X16
issue_uuid            → SYSUUID_X16
note_no               → NUMC(4)
note_text             → CHAR(255)
note_category         → CHAR(20)
local_last_changed_at → ABP_LOCINST_LASTCHANGE_TSTMPL

Technical key:

client + note_uuid

---

3. Create the Child CDS Entity

Create:

ZR_ISSUE_NOTE_###

Requirements:

define view entity
not root
select from ZISSNOTE_###
@AccessControl.authorizationCheck: #CHECK
association to parent ZR_ISSUE_###

Expose:

_Note parent association
NoteUuid
IssueUuid
NoteNo
NoteText
NoteCategory
LocalLastChangedAt

Use a sensible actual association name such as:

_Issue

---

4. Model the To-Parent Association

Use the child:

IssueUuid

to identify the root Issue key.

The ON condition must cover the complete root key.

Expose the association exactly once in the child select list.

---

5. Add Composition to the Issue Root

Modify:

ZR_ISSUE_###

Add:

composition [0..*]

to:

ZR_ISSUE_NOTE_###

Use an association name such as:

_Notes

Expose _Notes in the root select list.

---

6. Protect Child Reads

Create Access Control for:

ZR_ISSUE_NOTE_###

Use the parent Issue's:

ResponsibleUser

through the to-parent association.

Required read rule:

parent ResponsibleUser
=
current user

Do not hard-code a user ID.

---

Base Behavior

7. Create-Enable the Composition

In the Issue root behavior add:

association _Notes

with:

create
with draft

The child must be created through the parent.

---

8. Add Child Behavior

Add another define behavior block in the same base BDEF.

Requirements:

persistent table = ZISSNOTE_###
draft table = ZDISSNOTE_###
lock dependent by parent
authorization dependent by parent
ETag master = LocalLastChangedAt
update
delete
managed numbering for NoteUuid
IssueUuid read-only
NoteNo mandatory on create
NoteNo read-only on update
parent association with draft
complete persistence mapping

Do not add normal:

create;

to the child.

---

9. Generate Child Draft Table

Place the cursor on:

ZDISSNOTE_###

Use:

Ctrl+1

Generate the draft table.

Activate it.

Do not manually maintain the draft administration fields.

---

10. Activate the Base Composition

Activate:

ZISSNOTE_###
ZR_ISSUE_NOTE_###
child Access Control
modified ZR_ISSUE_###
ZDISSNOTE_###
modified base BDEF
related behavior artifacts

Do not proceed until the base BO activates cleanly.

---

EML Composition Challenge

11. Create ZCL_ISSUE_COMP_###

Implement:

IF_OO_ADT_CLASSRUN

Rules:

external EML consumer
no IN LOCAL MODE
no direct SQL writes

---

12. Find an Owned Issue

Use a protected read against:

ZR_ISSUE_###

Find one Issue owned by the current user.

Use an existing practice Issue if available.

Store its:

Uuid

---

13. Create a Work Note by Association

Use:

CREATE BY \_Notes

Create:

NoteNo       = 0001
NoteText     = Initial troubleshooting note
NoteCategory = TECHNICAL

Do not supply:

NoteUuid
IssueUuid

Inspect:

MAPPED
FAILED
REPORTED

---

14. Prove Managed Child Numbering

From:

MAPPED

retrieve the generated:

NoteUuid

associated with your child %cid.

The consumer must not generate the UUID itself.

---

15. Commit the Child

Use:

COMMIT ENTITIES

with response handling.

Verify:

Work Note persisted
parent Issue unchanged except BO-wide change metadata

---

16. Read by Association

Use EML to read:

Issue
BY \_Notes

Request:

RESULT
LINK
FAILED

Output the returned Work Notes.

---

17. Explain LINK

Use your runtime result to identify:

source Issue key
→
target Work Note key

Do not infer the relationship from internal-table ordering.

---

Deep Create Challenge

18. Create an Issue and Two Notes Together

Create:

one new Issue
two Work Notes

inside one:

MODIFY ENTITIES

Requirements:

root %cid
CREATE BY \_Notes
child %cid_ref
child %target
two child %cid values

Do not split the operation just to obtain the root UUID.

---

19. Deep Create Evidence

Before commit inspect:

MAPPED root component
MAPPED note component
FAILED
REPORTED

After commit verify:

one Issue
two related Work Notes

---

Projection Layer

20. Create Child Projection

Create:

ZC_ISSUE_NOTE_###

Requirements:

projection on ZR_ISSUE_NOTE_###
#CHECK
metadata extensions enabled
all Work Note fields projected
parent association redirected to ZC_ISSUE_###

Use:

redirected to parent

---

21. Redirect Root Composition

Modify:

ZC_ISSUE_###

Expose:

_Notes

and redirect it to:

ZC_ISSUE_NOTE_###

Use:

redirected to composition child

---

22. Protect Projection Child Reads

Create Access Control for:

ZC_ISSUE_NOTE_###

Inherit access conditions from:

ZR_ISSUE_NOTE_###

Do not repeat the same ownership expression manually.

---

Projection Behavior

23. Extend the Root Projection BDEF

Expose:

_Notes

with:

create
with draft

---

24. Add Child Projection Behavior

Add behavior for:

ZC_ISSUE_NOTE_###

Expose:

use etag
use update
use delete
use association parent with draft

Do not use:

use create

for the child.

---

Service and UI

25. Add Work Notes to the Service

Modify:

ZUI_ISSUE_###

Expose:

ZC_ISSUE_NOTE_###

with alias:

WorkNotes

Keep the existing OData V4 UI Service Binding.

Reload it after activation.

---

26. Add the Work Notes Facet

Modify the root Issue metadata.

Add a facet:

type = #LINEITEM_REFERENCE
targetElement = _Notes
label = Work Notes

Choose a sensible position after the main Issue details.

---

27. Create Child Metadata

Create Metadata Extension for:

ZC_ISSUE_NOTE_###

Add line-item metadata for:

NoteNo
NoteText
NoteCategory

---

Fiori Draft Runtime

28. Create a Draft Work Note

Open an owned Issue.

Choose:

Edit

Create one Work Note in the child facet.

Before Save verify:

ZISSNOTE_###
→ no new active row

ZDISSNOTE_###
→ draft Work Note exists

---

29. Save the Composition Tree

Choose:

Save

Expected:

Issue draft activates
Work Note draft activates
active Work Note appears
draft Work Note disappears

---

30. Discard a Child Modification

Edit the Issue again.

Change or delete the Work Note.

Before Save, inspect active and draft state.

Choose:

Cancel / Discard

Expected:

active Work Note unchanged
draft modification removed

---

31. Verify the Root Total ETag

Capture the Issue root:

LastChangedAt

Change and save only a Work Note.

Read:

LastChangedAt

again.

Expected:

root total ETag changed

---

Repair Tasks

32. Wrong Relationship Type

Temporarily reason about replacing:

composition

with:

association

Restore the composition.

Identify the whole–part semantics that would be lost.

---

33. Missing To-Parent Association

Break the child:

association to parent

Run syntax check.

Restore the direct parent relationship.

---

34. Incorrect Child Create

Try to reason about adding:

create;

to the managed child.

Restore the correct model:

create through root association

---

35. Missing Lock Dependency

Break:

lock dependent by

Repair it.

Identify the actual lock master.

---

36. Missing Authorization Dependency

Break:

authorization dependent by

Repair it.

Identify the actual authorization master.

---

37. Missing Draft Association

Remove:

with draft

from one side of the behavior relationship.

Restore it.

Explain why active/draft navigation must remain state-consistent.

---

38. Projection Not Redirected

Remove one:

redirected to parent

or:

redirected to composition child

statement.

Repair the projection hierarchy.

---

39. Child Missing from Service

Remove:

WorkNotes

from the Service Definition.

Reload the service binding.

Restore the child exposure.

---

Submission Checklist

40. Checklist

• ZISSNOTE_### created.
• Note UUID is technical key.
• Issue UUID stored as parent reference.
• ZR_ISSUE_NOTE_### created.
• Child is not root.
• Child has association to parent.
• Issue root has [0..*] composition.
• Base child DCL protects reads.
• Root BDEF create-enables _Notes.
• Root association uses with draft.
• Child behavior uses lock dependency.
• Child behavior uses authorization dependency.
• Child has own ETag master.
• Child UUID numbering is managed.
• Child draft table generated.
• Child parent association uses with draft.
• CREATE BY \_Notes works.
• Child UUID returned in MAPPED.
• Read-by-association works.
• LINK returned.
• Deep create uses %cid_ref.
• ZC_ISSUE_NOTE_### created.
• Child projection redirects parent.
• Root projection redirects child composition.
• Child projection DCL inherits base conditions.
• Root projection BDEF exposes child create.
• Child projection BDEF exposes update/delete.
• Work Notes exposed in Service Definition.
• Existing OData V4 binding reused.
• Work Notes facet appears.
• Child line-item metadata appears.
• New Work Note exists only in draft persistence before Save.
• Save activates Work Note.
• Discard keeps active Work Note unchanged.
• Root total ETag changes after active Work Note modification.

---

41. End-of-Practice Model

You should now be able to implement:

Issue
  │
  │ composition
  ↓
Work Note

through all RAP layers:

persistence
CDS composition
to-parent association
base behavior
create by association
lock dependency
authorization dependency
draft
projection redirection
OData service
Fiori child facet
EML deep create

That is the core pattern for a managed multi-node RAP Business Object.