Oracle BPM uses transactions to control the steps throughout it’s processes. In the Oracle BPEL processes you are able to use a checkpoint to explicit force a dehydration during your process.

Oracle BPMN doesn’t have a specific activity to perform the same. However you can force a dehydration by using a timer catch event in your process. Setting the timer to 2 seconds is sufficient.
(I think this might actually be 1 second, but the manual claims that the duration should be more than 1 second so we use 2 seconds to be sure).

Oracle BPM Catch Timer Event

Oracle BPM Catch Timer Event

Overview of where transactions occur in Oracle BPM/BPEL (source: Oracle performance tuning guide):

• Mid-process breakpoint activities (e.g. receive, onMessage, onAlarm, wait),
• A non-idempotent (i.e. non-retryable) invoke,
• A non-blocking (i.e. asynchronous) invoke,
• Explicit dehydration (in BPEL only), i.e. the checkpoint() call,
• An asynchronous queue (e.g. JMS), and
• A Timer Catch Event with duration of more than one second.