Search Results oe_retrobill_requests
Overview
The OE_RETROBILL_REQUESTS table is a core configuration and control object within the Oracle Order Management (ONT) product of Oracle E-Business Suite. It stores the definitions of retro-bill requests, which are used to apply price, promotion, or agreement adjustments to orders that have already been booked or invoiced. In Oracle EBS, retro-billing enables organizations to capture backdated pricing changes — for example when a customer-specific agreement, freight term, or discount is negotiated after the original order was entered — and to propagate those changes through the order and billing lifecycle. The table therefore acts as the master record of "what retro-bill action should be performed, against which items and customers, and when."
Because the table stores request definitions that are executed and referenced by downstream processes, and which are scoped by attributes such as order type, inventory item, and sold-to organization, the metadata classifies it heuristically as a standalone object within a Data Vault model. In practice this suggests modeling the table as its own hub-like entity keyed by RETROBILL_REQUEST_ID, with descriptive attributes (name, description, execution mode, dates, flags) carried as satellites, and the ORDER_TYPE_ID foreign key represented as a link to the order type reference data. This classification reflects that the table is neither a pure transaction link nor a dependent child of a larger parent, but a self-contained definition object.
Key Information Stored
The table contains 34 documented columns. The most significant are:
- RETROBILL_REQUEST_ID — the surrogate primary key and the single column enforcing the unique index OE_RETROBILL_REQUEST_U1. This is the business-key candidate that uniquely identifies each retro-bill request.
- NAME — the user-defined name of the retro-bill request, typically used to identify the request in the Order Management responsibility.
- DESCRIPTION — free-text description of the request's purpose or scope.
- EXECUTION_MODE — controls how the request is applied (for example, whether it runs immediately or is scheduled).
- ORDER_TYPE_ID — foreign key to SO_ORDER_TYPES_115_ALL, restricting the request to a specific order type.
- RETROBILL_REASON_CODE — the reason or category associated with the retro-bill action.
- EXECUTION_DATE — the date on which the request is intended to execute.
- INVENTORY_ITEM_ID — the item to which the retro-bill applies, when the request is item-specific.
- SOLD_TO_ORG_ID — the customer (sold-to organization) targeted by the request.
- REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATED_DATE — concurrent program context identifying the submission that created or last processed the request.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns for auditability.
The fifteen ATTRIBUTE1–ATTRIBUTE15 columns provide the usual flexible descriptive-flexfield extension capability for customer-specific data.
Common Use Cases and Queries
The table is most commonly queried to inspect which retro-bill requests are defined, to audit their execution status, and to join them to order types, items, and customers for reporting. A typical lookup resolves the order type name and the request definition:
- List active requests with their order type:
SELECT r.retrobill_request_id, r.name, r.execution_mode, t.name order_type
FROM ont.oe_retrobill_requests r, ont.so_order_types_115_all t
WHERE r.order_type_id = t.order_type_id; - Find item-specific requests for a given organization:
SELECT * FROM ont.oe_retrobill_requests WHERE inventory_item_id = :item AND sold_to_org_id = :cust; - Audit requests by concurrent program / last run:
SELECT name, execution_date, program_id, program_updated_date
FROM ont.oe_retrobill_requests WHERE program_updated_date > SYSDATE - 30;
These queries support pricing reconciliation, promotion auditing, and troubleshooting of retro-billing schedules.
Related Objects
- SO_ORDER_TYPES_115_ALL — referenced by ORDER_TYPE_ID; the primary documented foreign-key relationship.
- OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — order and line tables to which retro-bill price adjustments are ultimately applied.
- OE_PRICE_ADJUSTMENTS — stores the calculated adjustments arising from executed retro-bill requests.
- FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — join via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID for execution context.
- OE_RETROBILL_PUB — the public API used to process and submit retro-bill logic against the requests defined here.
- MTL_SYSTEM_ITEMS_B — resolves INVENTORY_ITEM_ID to item details.
- HZ_CUST_ACCOUNTS — resolves SOLD_TO_ORG_ID to customer information.
-
Table: OE_RETROBILL_REQUESTS
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_RETROBILL_REQUESTS, object_name:OE_RETROBILL_REQUESTS, status:VALID, product: ONT - Order Management , description: Retrobill requests table. , implementation_dba_data: ONT.OE_RETROBILL_REQUESTS ,
-
Table: OE_RETROBILL_REQUESTS
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_RETROBILL_REQUESTS, object_name:OE_RETROBILL_REQUESTS, status:VALID, product: ONT - Order Management , description: Retrobill requests table. , implementation_dba_data: ONT.OE_RETROBILL_REQUESTS ,
-
SYNONYM: APPS.OE_RETROBILL_REQUESTS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:OE_RETROBILL_REQUESTS, status:VALID,
-
SYNONYM: APPS.OE_RETROBILL_REQUESTS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:OE_RETROBILL_REQUESTS, status:VALID,
-
VIEW: ONT.OE_RETROBILL_REQUESTS#
12.2.2
owner:ONT, object_type:VIEW, object_name:OE_RETROBILL_REQUESTS#, status:VALID,
-
VIEW: ONT.OE_RETROBILL_REQUESTS#
12.2.2
-
PACKAGE: APPS.OE_RETROBILL_PVT
12.1.1
owner:APPS, object_type:PACKAGE, object_name:OE_RETROBILL_PVT, status:VALID,
-
PACKAGE: APPS.OE_RETROBILL_PVT
12.2.2
owner:APPS, object_type:PACKAGE, object_name:OE_RETROBILL_PVT, status:VALID,
-
TABLE: ONT.OE_RETROBILL_REQUESTS
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_RETROBILL_REQUESTS, object_name:OE_RETROBILL_REQUESTS, status:VALID,
-
TABLE: ONT.OE_RETROBILL_REQUESTS
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_RETROBILL_REQUESTS, object_name:OE_RETROBILL_REQUESTS, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.OE_RETROBILL_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:OE_RETROBILL_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.OE_RETROBILL_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:OE_RETROBILL_PVT, status:VALID,
-
PACKAGE: APPS.OE_RETROBILL_PVT
12.1.1
-
APPS.OE_RETROBILL_PVT SQL Statements
12.1.1
-
PACKAGE: APPS.OE_RETROBILL_PVT
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.OE_RETROBILL_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.OE_RETROBILL_PVT
12.1.1
-
APPS.OE_RETROBILL_PVT dependencies on OE_RETROBILL_REQUESTS
12.2.2
-
TABLE: ONT.OE_PRICE_ADJUSTMENTS
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PRICE_ADJUSTMENTS, object_name:OE_PRICE_ADJUSTMENTS, status:VALID,
-
PACKAGE BODY: APPS.OE_RETROBILL_PVT
12.2.2
-
TABLE: ONT.OE_PRICE_ADJUSTMENTS
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PRICE_ADJUSTMENTS, object_name:OE_PRICE_ADJUSTMENTS, status:VALID,
-
APPS.OE_RETROBILL_PVT dependencies on OE_RETROBILL_REQUESTS
12.1.1
-
APPS.OE_RETROBILL_PVT dependencies on OE_RETROBILL_REQUESTS
12.1.1
-
APPS.OE_RETROBILL_PVT dependencies on OE_RETROBILL_REQUESTS
12.2.2
-
TABLE: ONT.OE_PRICE_ADJS_HISTORY
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PRICE_ADJS_HISTORY, object_name:OE_PRICE_ADJS_HISTORY, status:VALID,
-
TABLE: ONT.OE_PRICE_ADJS_HISTORY
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PRICE_ADJS_HISTORY, object_name:OE_PRICE_ADJS_HISTORY, status:VALID,
-
APPS.OE_RETROBILL_PVT dependencies on OE_ORDER_TYPES_V
12.1.1
-
APPS.OE_RETROBILL_PVT dependencies on OE_ORDER_TYPES_V
12.2.2
-
APPS.OE_RETROBILL_PVT dependencies on OE_HEADER_ADJ_UTIL
12.2.2
-
APPS.OE_RETROBILL_PVT dependencies on OE_HEADER_ADJ_UTIL
12.1.1
-
TABLE: ONT.OE_ORDER_LINES_HISTORY
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_ORDER_LINES_HISTORY, object_name:OE_ORDER_LINES_HISTORY, status:VALID,
-
APPS.OE_RETROBILL_PVT dependencies on QP_UTIL_PUB
12.1.1
-
APPS.OE_RETROBILL_PVT dependencies on QP_UTIL_PUB
12.2.2
-
APPS.OE_RETROBILL_PVT dependencies on OE_ORDER_BOOK_UTIL
12.1.1
-
TABLE: ONT.OE_ORDER_LINES_HISTORY
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_ORDER_LINES_HISTORY, object_name:OE_ORDER_LINES_HISTORY, status:VALID,
-
APPS.OE_RETROBILL_PVT dependencies on OE_ORDER_BOOK_UTIL
12.2.2
-
TABLE: ONT.OE_ORDER_LINES_ALL
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_ORDER_LINES_ALL, object_name:OE_ORDER_LINES_ALL, status:VALID,
-
APPS.OE_RETROBILL_PVT dependencies on OE_RETROBILL_PVT
12.1.1
-
TABLE: ONT.OE_ORDER_LINES_ALL
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_ORDER_LINES_ALL, object_name:OE_ORDER_LINES_ALL, status:VALID,
-
APPS.OE_RETROBILL_PVT dependencies on OE_ORDER_PVT
12.1.1