Mirror of Oracle documentation
Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.
always enabled. They are not allowed to be disabled from the UI . Mandatory Jobs are part of the Nightly and Hourly cycles but not the Adhoc cycle.
Warning Codes and Error Codes
Shell-script-based jobs (jobs of type REST_EXEC ), in addition to the ERROR or COMPLETED status, can also move to a COMPLETED with Warning status. This status essentially indicates that even though the Job has completed, there may be certain corrective actions for Oracle Operations or the Customer to take. A notification of type JobCompletedWithWarning will also be created. Batch Schedules accomplish this by defining which exit codes are to be used as warning codes in the System Options tab.
Similarly, error codes can be defined for shell-script-based jobs to provide a better description on the error itself.
Format
Key = WarningCodeXXX or ErrorCodeXXX ( where XXX is the exit code).
Value = Description of the warning or error.
Auto-retry
For ReST-based jobs, there is a way to have POM auto-retry the Job (up to 4 times more) in cases of a known error. To do so, the error messages provided at the time of error are compared with a known list of restartable error messages. If the error exists in this list, then the Job will be retried by POM, without any manual intervention.
The wait time between such restarts also increases, allowing ample time for the system to resolve the Job successfully. For instance, the first restart will take place after a 30-second wait, while the second restart will take place after waiting for 40 seconds after the second failure, the third restart after 50 seconds after the third failure and the final restart after a full minute after the fourth failure.
This list of restartable error messages is defined for each Job type (ReST-based) as a System Option. Because System Options can be edited through the POM UI, it allows for Customers to add to this list post-deployment.
Note
Unlike other System Options, the restartable error message system option behaves slightly differently. The original list of error messages provided by Oracle is always retained internally and merged (removing duplicates) with the list modified by the Customer.
Format
Key = XXXRestartableErrorMessages (where XXX is the Job Type)
Value = A list of comma-separated error messages. If the response contains one of those error messages, POM will retry the job for a maximum of 3 attempts.
Every Job is associated with a Job Type that defines the kind of work performed by that Job.
The following Job Types are supported by POM out-of-the-box.
Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.
Note
Custom job types can be created using the Job Type feature of the System Configuration screen. See Generic ReST Jobs for more information.
Job Type Description REST_EXEC Refers to Merch and RI Restful-based jobs that are wrappers for shellscript based Jobs. BDI Indicative of BDI Jobs. POM invokes a BDI Process and tracks its (Bulk Data execution for this type of Jobs. Integration) RI Refers to DIS (Data Intelligence Services) Jobs for the RI Schedule. POM (Retail Insights) invokes RI endpoints and tracks their execution. RASE Refers to DIS (Data Intelligence Services) Jobs for the RSP Schedule. The (Retail Advanced wrapper endpoints invoked here are the same as the ones used by the RI Science Engine) job type. RPAS Indicative of RPAS-WebService Jobs for the RPAS schedule. POM invokes (Retail Predictive RPAS endpoints to start and track RPAS batches. Application Server) OB Indicative of OB-WebService Jobs for the OB schedule. POM invokes OB (Order Broker) endpoints to start and track OB batches. OMS Indicative of OMS-WebService Jobs for the OMS schedule. POM invokes (Order Management OMS endpoints to start and track OMS batches. System) DUMMY Mock Job Type that doesn’t call any executable. It is used for Jobs that are meant to be used as placeholders. Such Jobs are automatically skipped by the Execution Engine. RDS Indicative of RDS Jobs. POM invokes RDS endpoints to start and track (Retail Data Services) these Jobs.
Long Running Jobs
When a Job execution time exceeds a certain threshold, that Job is classified as a Long Running Job. POM provides certain controls on how to define this threshold, both at a Schedule and a Job level.
If a Threshold Run Time is specified for the job on the Edit Job window on the Batch Administration screen, then a job is deemed long-running if its current run time exceeds that value. Otherwise, if a Threshold Run Time is not specified, then the job is deemed long-running when its current run time exceeds the Long Run Average Time Multiplier (specified on the Edit Settings window of the System Configuration screen) times the average run time of that job + Long Running Tolerance Level. The value for the Long Running Tolerance Level can be overridden by changing the value of batch schedule variable
defaultLongRunningToleranceLevel on the System Options screen accessed from the System Configuration screen. The value is in seconds.
For example, if a job’s average run time is 3 minutes, and the Long Run Average Time Multiplier is 3 and the Long Running Tolerance Level is 6 minutes, then the job is considered long running if it has been running for at least 15 minutes. A notification is sent when a job is deemed long-running.
Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.
Batch Cycle
A Batch Cycle is the container in which Flows, Processes and Jobs are setup. There are three types of Batch Cycles.
Adhoc / Standalone Cycle
The Flows and Processes defined in this Cycle can run multiple times a day on an as-needed basis. Such invocations can run independent of other Processes and Flows on other Cycles.
Example: A Flow can be defined whose main responsibility is to purge data in database tables to boost performance. This Flow can then be run every 15 minutes without impacting Flows or Processes on other Cycles.
Recurring / Hourly Cycles
Recurring or Hourly Cycles are specialized Batch Cycles with the following properties
-
A Batch Schedule can have a maximum of 24 Hourly Cycles.
-
The Flows and Processes defined on an Hourly Cycle are replicated across all the defined Hourly Cycles. Dependencies are built between these batch entities, to ensure that unless it is completed in a prior cycle, it will not run in the next cycle.
-
All the Hourly Cycles are meant to be run prior to running the Nightly Flow. Once the Nightly Flow starts, all the Jobs on the Hourly Cycles are marked completed.
Example: The Sales processing Jobs in RMS support trickle processing by running every 30 minutes during the store trading hours. The schedule is pre-loaded with 24 Hourly Cycles. The Hourly Cycles are time triggered from the Scheduler or through ReST APIs externally. Based on the client’s business operations, the individual flows of each cycle need to be scheduled.
Note
If there are any errors on the Hourly Cycles, then the Nightly Cycle will not start until they are resolved.
Nightly Cycle
This Batch Cycle contains the set of Jobs that are executed at end of the business day. All of these Processes and Jobs belong to the default Nightly Flow of this Cycle. Once the Nightly Flow has started, all the loaded Flows and Processes on the Hourly Cycles are marked complete.
The Nightly Flow can be time-triggered or triggered using Schedule Links. It can be timetriggered through the POM Scheduler or externally through the ReST API.
Batch Dependencies
A dependency is a construct that prevents the execution of a Job, until a condition is satisfied.
Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.
| Type | Description |
|---|---|
| Internal Dependency | Internal dependencies are the dependencies between Jobs of the same Batch Schedule. |
| Inter-schedule Dependency | Inter-Schedule dependencies are the dependencies between Jobs of different schedules running on the same POM instance. |
| External Dependency | External dependencies are dependencies between processes running on external systems, such as a Customer’s system and Jobs running on the POM schedule. |
| Custom Dependency | Dependency between Nightly jobs and Adhoc Flows/Processes. A Custom Dependency can be created on the Job Detail screen in the Nightly cycle through the Batch Administration screen. |
Batch Schedule Links
Schedule Links or Execution Links, allow a Job from one Schedule, to trigger the Nightly Cycle of a different Schedule.
Batch Metadata
All information from the Batch Schedule spreadsheet is referred to as the Batch metadata. This information is modifiable from the POM UI on the Batch Administration Screen.
Batch Scheduler Day
Simply stated, this is a single copy of the Batch metadata or an instance of the Batch Schedule that is associated with a business date. All executions of batches for that business date are recorded on that Scheduler Day or Schedule Instance. Without a Scheduler Day, no Flows or Processes can be run.
A Batch Scheduler Day is marked Closed at the completion of all the Batch Jobs of the Nightly Cycle. The business date is then incremented by one, and a new Scheduler Day is created for the next day.
If however, there are Adhoc Flows or Processes executing when the Nightly Cycle completes, the closure of the Scheduler Day is then deferred until the completion of the running batches. Also, no new execution requests are allowed between the nightly completion and the creation of the next scheduler day. It is a common scenario where, at the time of New Scheduler Day creation, one of the batch schedule’s Job Agents is down due to patching or other reasons. POM skips the Agent initialization during New Scheduler Day creation if an Agent is unavailable. POM then attempts the initialization again prior to invoking a Job on that Agent.
Implementation Guide G58508-01 Copyright© 2026, Oracle and/or its affiliates.
In this guide
- Guide: POM Implementation Guide
- Previous: 10 Invoking POM Services
- Next: 3 Integration