Results for “online_report_id”

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

Overview

PO_ONLINE_REPORT_TEXT is a Purchasing (PO) module table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the PO schema. As its description states, the table stores "Online report errors" — it captures the diagnostic text and contextual detail generated when an online Receiving or Purchasing transaction produces errors during processing. Rather than persisting user-facing transaction data, PO_ONLINE_REPORT_TEXT acts as a companion log that links error messages back to a specific receiving transaction, allowing forms, concurrent programs, and reports to surface meaningful feedback to the user.

From a Data Vault modeling perspective, the mined FK structure classifies this table as satellite-leaning. That is a heuristic suggestion, not an enforced design: the table's natural affinities — a composite primary key tied to a parent identifier and heavy descriptive text content — are characteristic of a satellite attached to a core hub/link around receiving transactions.

Key Information Stored

The table's surrogate/business primary key is PO_ONLINE_REPORT_TEXT_PK, a composite of ONLINE_REPORT_ID and SEQUENCE. Together these uniquely identify each error text line within a single report run.

• ONLINE_REPORT_ID – the identifier grouping all text lines belonging to one online report instance.
• SEQUENCE – ordering key that positions each line within a report.
• TEXT_LINE / LINE_NUM – the actual error message text and its line number.
• TRANSACTION_ID – foreign key to RCV_TRANSACTIONS, tying the error to the originating receiving transaction.
• TRANSACTION_LEVEL, TRANSACTION_TYPE, TRANSACTION_UOM, TRANSACTION_LOCATION, TRANSACTION_DATE – contextual attributes describing what kind of transaction failed and where.
• SHIPMENT_NUM, DISTRIBUTION_NUM, DISTRIBUTION_TYPE – identify the specific shipment or distribution affected.
• QUANTITY – the quantity involved in the failing transaction line.
• MESSAGE_TYPE, SHOW_IN_PSA_FLAG – classify the message and control whether it is displayed in the Purchasing Summary/PSA interface.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – identify the concurrent request/program that generated the error.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) – audit trail.

Common Use Cases and Queries

Typical uses include retrieving error text for a failed receiving transaction, diagnosing batch receipt processing, and feeding error detail into operational reports.

SELECT t.text_line, t.line_num, t.message_type
FROM   po.po_online_report_text t
WHERE  t.transaction_id = :transaction_id
ORDER  BY t.sequence;

Joining to RCV_TRANSACTIONS exposes the transaction context:

SELECT r.transaction_id, r.transaction_type, t.text_line
FROM   rcv_transactions r,
       po.po_online_report_text t
WHERE  r.transaction_id = t.transaction_id
AND    t.show_in_psa_flag = 'Y';

Filtering on REQUEST_ID or PROGRAM_ID supports concurrent-program troubleshooting and error accounting reports.

Related Objects

• RCV_TRANSACTIONS – joined via PO_ONLINE_REPORT_TEXT.TRANSACTION_ID = RCV_TRANSACTIONS.TRANSACTION_ID; the primary parent relation.
• PO_ONLINE_REPORT_TEXT_PK – composite primary key on (ONLINE_REPORT_ID, SEQUENCE) enforcing uniqueness.
• PO Receiving forms and Receiving Transaction APIs – consume this table to present online errors to users.
• FND_CONCURRENT_REQUESTS – related through REQUEST_ID for concurrent-process diagnosis.
• RCV_SHIPMENT_HEADERS / RCV_SHIPMENT_LINES – contextual parents referenced via shipment and distribution numbers.