Search Results unearned_batch_name




Overview
Explore in AI Chat

Overview

PA_DRAFT_REVENUES_O is a single-organization (Single-Org) security view in the Oracle E-Business Suite Projects (PA) module. It exposes draft revenue records generated during the revenue generation and accrual process, prior to the transfer of those distributions to Oracle General Ledger or Oracle Receivables. The "_O" suffix indicates the view is intended for use in a single-operating-unit context, in contrast to the multi-org (_ALL) and related _M views that operate alongside it in the standard multi-org architecture.

The view inherits its definition directly from PA_DRAFT_REVENUES_ALL, filtered by organization through the ORG_ID column. Because the view is documented as "Not implemented in this database," no stored implementation exists to inspect in the instance from which the ETRM metadata was drawn; however, the view text remains definitive and portable across Oracle EBS 12.1.1 and 12.2.2, where the same single-org filtering pattern is applied.

From a reporting and integration standpoint, PA_DRAFT_REVENUES_O provides a controlled, organization-scoped projection of the draft revenue stream. It is the preferred object for single-org queries, custom reports, and interfaces that must respect the session's operating unit without manually applying multi-org predicates.

Underlying Base Objects

The documented definition references only one base object: PA_DRAFT_REVENUES_ALL. No additional base tables, joins, or aggregations are documented. The view is therefore a thin row-filtering layer, not a denormalized reporting construct.

The filtering predicate compares ORG_ID against the organization implied by the session's CLIENT_INFO, resolving to the value extracted from USERENV('CLIENT_INFO'). The NVL/DECODE construction yields -99 when the organization context is absent, which conventionally means "no rows" for single-org views in Oracle Projects. This design ensures that a session operating in one organization sees only its own draft revenues, while the underlying _ALL view remains the source of record.

Key Columns

Common Use Cases and Queries

The principal use cases are revenue accrual reconciliation, audit of unbilled receivables and unearned revenue account assignments, and troubleshooting of transfer rejections. A representative query to trace accounting combinations for unreleased draft revenue is shown below.

SELECT PROJECT_ID, DRAFT_REVENUE_NUM, UNBILLED_CODE_COMBINATION_ID, UNEARNED_CODE_COMBINATION_ID, UNBILLED_RECEIVABLE_DR, UNEARNED_REVENUE_CR FROM PA_DRAFT_REVENUES_O WHERE TRANSFER_STATUS_CODE IS NULL AND GENERATION_ERROR_FLAG = 'N';

For diagnostics of rejected transfers: SELECT PROJECT_ID, DRAFT_REVENUE_NUM, TRANSFER_REJECTION_REASON, PA_PERIOD_NAME FROM PA_DRAFT_REVENUES_O WHERE TRANSFER_STATUS_CODE = 'R';

Because the view enforces organization security, callers must run it under a session with a valid operating unit context; otherwise the -99 comparison returns no rows. Queries spanning multiple organizations should target PA_DRAFT_REVENUES_ALL instead.