Keep incomplete work separate until it is ready

A buyer may need to enter a request in stages and return later. Draft-enabled RAP gives the user a draft lifecycle; the RAP runtime orchestrates draft handling rather than asking the application to write the draft table directly.

Enable draft handling

with draft;

define behavior for ZR_PURCHASE_REQUEST alias Request
  persistent table zpurchase_request
  draft table zpurchase_request_d
  lock master
{
  create;
  update;
  draft action Edit;
  draft action Activate;
  draft action Discard;
}

This is an instructional fragment, not a complete draft BO. Draft tables require the correct technical fields and relationship to the active model; ADT-generated artifacts are a safer starting point than hand-building the table from this excerpt. Activate moves validated draft data into the active lifecycle; Discard abandons the draft.

Draft adds persistence, locking, authorization, and service considerations. Use it when users need an edit-and-resume workflow, not as a default for every BO.

Sources

• SAP Samples: BDEF draft handling
• ABAP Keyword Documentation: RAP draft handling

with draft;
define behavior for ZR_PURCHASE_REQUEST alias Request
  persistent table zpurchase_request
  draft table zpurchase_request_d
  lock master
{
  create;
  update;
  draft action Edit;
  draft action Activate;
  draft action Discard;
}