Results for “warning_message_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_DISTRIBUTION_WARNINGS is a Projects (PA) module table in Oracle EBS 12.1.1 and 12.2.2 that stores warning messages generated when exceptions are encountered during the Draft Revenue Generation and Draft Invoice Generation processes. When the revenue or invoice generation concurrent programs detect conditions that prevent normal distribution processing — for example, missing rate information, invalid account combinations, or unbalanced distribution lines — the programs do not necessarily fail outright. Instead, they record a diagnostic warning row tied to the affected draft revenue or draft invoice, allowing the process to complete while surfacing exceptions for review.

The heuristically mined Data Vault classification for this table is link. This is a reasonable modeling suggestion: the table sits at the intersection of two parent entities (draft invoices and draft revenues), both referenced via PROJECT_ID combined with the respective draft number, and its primary purpose is to record a relationship plus contextual descriptive attributes. In practice the table behaves as an associative or bridging table that links a project distribution event to a warning condition, rather than a standalone hub of a core business concept or a pure descriptive satellite.

Key Information Stored

The table contains 16 documented columns in the 12.2.2 physical schema. The most significant columns are:

• PROJECT_ID — Identifies the project associated with the warning; participates in both foreign key relationships.
• DRAFT_REVENUE_NUM — The draft revenue number to which the warning applies; joins to PA_DRAFT_REVENUES_ALL.
• DRAFT_INVOICE_NUM — The draft invoice number to which the warning applies; joins to PA_DRAFT_INVOICES_ALL.
• WARNING_MESSAGE — The full text of the exception message presented to the user.
• WARNING_MESSAGE_CODE — A code that categorizes or identifies the specific warning condition, useful for filtering and grouping.
• AGREEMENT_ID — Links the warning to the project agreement under which the distribution was attempted.
• TASK_ID — Identifies the task context for the warning, where the exception is task-specific.
• REQUEST_ID — The concurrent request that generated the warning, enabling traceback to the originating run.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — Audit columns identifying the concurrent program that produced the record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail.

The documented schema does not present a single surrogate primary key column; identification is effectively driven by the combination of PROJECT_ID with DRAFT_REVENUE_NUM or DRAFT_INVOICE_NUM, which serve as the business-key candidates reflected in the foreign key definitions.

Common Use Cases and Queries

Because warnings are written during draft revenue and draft invoice generation, the most common use case is post-run diagnostics: locating why a distribution was incomplete or unbalanced. A typical query joins warnings to the draft revenue to retrieve descriptive project context:

• Investigate warnings for a project: SELECT warning_message_code, warning_message FROM pa_distribution_warnings WHERE project_id = :project_id;
• Trace warnings to a concurrent request: SELECT * FROM pa_distribution_warnings WHERE request_id = :request_id; — useful when a batch generation produces partial results.
• Join to draft revenues: SELECT w.warning_message, r.* FROM pa_distribution_warnings w, pa_draft_revenues_all r WHERE w.project_id = r.project_id AND w.draft_revenue_num = r.draft_revenue_num;
• Join to draft invoices: SELECT w.warning_message, i.* FROM pa_distribution_warnings w, pa_draft_invoices_all i WHERE w.project_id = i.project_id AND w.draft_invoice_num = i.draft_invoice_num;
• Warning frequency reporting: grouping by WARNING_MESSAGE_CODE over a date range using CREATION_DATE helps identify recurring configuration or setup problems.

Related Objects

The table’s foreign key relationships define its primary dependencies, and other PA objects supply supporting context:

• PA_DRAFT_INVOICES_ALL — Referenced via PROJECT_ID and DRAFT_INVOICE_NUM; provides the draft invoice header for invoice-generation warnings.
• PA_DRAFT_REVENUES_ALL — Referenced via PROJECT_ID and DRAFT_REVENUE_NUM; provides the draft revenue header for revenue-generation warnings.
• PA_PROJECTS_ALL — Supplies project descriptive attributes resolved from PROJECT_ID.
• PA_TASKS — Resolves TASK_ID to the task name and structure.
• PA_AGREEMENTS_ALL — Resolves AGREEMENT_ID to the project agreement.
• FND_CONCURRENT_REQUESTS — Resolves REQUEST_ID and program columns to the concurrent program run.
• Draft Revenue Generation and Draft Invoice Generation concurrent programs — The producers that populate this table; reviewing their output through this table is standard operational practice.

Together these relationships make PA_DISTRIBUTION_WARNINGS a diagnostic bridge between the distribution-generation programs and the transactional draft entities they process.