Core Configuration on Learn Oracle OTM

Saved Queries/Conditions

Wed, 20 Jul 2016 21:30:00 +0000

Saved Queries in OTM help to query specific records in a screen or add conditions to custom logic while creating an Agent or similar configuration. They can be reused across multiple OTM features including recurring processes and business monitors.

Start here — this is foundational: Saved Queries and Conditions are arguably the most important configuration concept in OTM for both UI customisation and automation. Almost every advanced OTM feature — Agents, Business Monitors, Recurring Processes, Action Checks, and custom Workbenches — requires a Saved Query or Condition to define which records the logic should act on. Without a solid grasp of how to build and reuse queries, you cannot effectively configure any of these features.

Beyond automation, Saved Queries power the everyday user experience: they let you build pre-filtered finder screens that surface only the records relevant to a specific role or workflow — for example, a shipment coordinator who should only see shipments in their region, or an approver who only sees invoices within their approval threshold. A well-designed set of Saved Queries is often the difference between an OTM implementation that users actually adopt and one they work around.

Invest time here before moving to Agents, Business Monitors, or any other automation topic. Every hour spent mastering Saved Queries will save you many hours of troubleshooting downstream.

Type 1: User in Finder Query

Refnums

Fri, 07 Jul 2017 18:37:00 +0000

OTM provides the flexibility to associate custom attributes — also called refnums — to every transaction object such as Order Base, Order Release, and Shipment. Developers can use these refnums to store client-specific values like source system information, custom dates, and other custom fields. Note that newer versions of OTM also have attribute (flex field) columns for the same purpose, which are covered in a separate post.

To create a refnum, navigate to the specific business object menu. For a Shipment refnum:

Flex fields

Thu, 06 Apr 2017 22:10:00 +0000

OTM provides attribute columns (Char, Number, Date, and Currency) on most major transaction tables such as ORDER_RELEASE and SHIPMENT to store custom data alongside standard fields. Flex Fields are definitions applied to these attribute columns that control how the field behaves in the UI — including whether it shows a free-text entry, a query-driven dropdown, or a standard lookup list. Once defined, a Flex Field can be added to a Manager Layout so that users can enter data directly from the screen.

Status Types

Fri, 07 Jul 2017 20:10:00 +0000

In OTM, transaction objects like Order Release and Shipment have a ‘Status’ button on the header screen that shows values describing the current state of that object in the transaction lifecycle.

For example, if you want to track the tender status of a shipment, you can review shipment status ‘SECURE RESOURCES’ and its values at each stage in the tender lifecycle. When a shipment is originally created, it might have a status like ‘SECURE RESOURCES_NOT STARTED’. Once tendered to a carrier, this status changes to ‘SECURE RESOURCES_TENDERED’. Once the carrier accepts the tender, the status changes to ‘SECURE RESOURCES_ACCEPTED’, and so on. These status values give users clear information about what actions are required next.

Business Numbers

Sun, 15 Feb 2026 19:04:00 +0000

Business Number Rules control how OTM generates IDs for business objects such as Order Bases, Order Releases, Shipments, and Invoices. OTM provides default XID sequences for all objects, but you can create custom rules when business requirements call for a specific format or numbering range.

Business Process Automation > Power Data > Business Numbers > Business Number Rule

Every rule definition consists of one or more instructions enclosed in braces { }. Literal text, if any, appears outside the braces. For example, the default rule for the invoice ID is: