Results for “operation_id”

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

Overview

The PSB_WS_SUBMIT_COMMENTS table belongs to the PSB (Public Sector Budgeting) product family within Oracle E-Business Suite. In the ETRM metadata, PSB is flagged as Obsolete, meaning the product is no longer actively shipped or supported in current EBS releases; the table therefore exists as a legacy artifact retained for historical continuity rather than as an actively populated transactional object. Its stated purpose is to "store comments for review groups sent during the Submit Worksheet process" — that is, user-authored narrative text associated with a budget worksheet at the moment the worksheet is routed into the review and approval cycle.

The physical schema documented for ETRM 12.1.1 shows an owner of PSB and only three columns: OPERATION_ID, WORKSHEET_ID, and COMMENTS. The table is defined by the primary key constraint PSB_WS_SUBMIT_COMMENTS_PK, which enforces uniqueness on OPERATION_ID. The metadata explicitly records that the object is "not implemented in this database," a common ETRM annotation indicating that the table is documented from the data model but absent from the specific database instance being profiled. The heuristic Data Vault classification mined from the FK structure is standalone; from a modeling perspective, this suggests treating the object as a self-contained satellite of worksheet submission activity, keyed by a surrogate operation identifier rather than linked through a formal hub-and-link topology.

Key Information Stored

Because the documented physical schema is deliberately narrow, the significant columns are limited to the following:

• OPERATION_ID — the surrogate primary key and the sole column comprising PSB_WS_SUBMIT_COMMENTS_PK. It uniquely identifies each stored comment record associated with a submit operation. As no unique business index is documented beyond the PK, OPERATION_ID serves as the only guaranteed identifier.
• WORKSHEET_ID — the foreign-key-style reference to the budget worksheet to which the comment applies. This is the principal business-key candidate for retrieval and is the column most likely to be joined against worksheet header tables during reporting.
• COMMENTS — free-form narrative text captured at submit time for the benefit of review groups. It holds the substantive content: reviewer notes, justification, or instructions accompanying the worksheet submission.

No audit columns (created-by, creation-date, last-updated-by) are documented for this object, which is consistent with its narrow purpose as a transient comment repository rather than a fully audited transactional entity.

Common Use Cases and Queries

Typical use of the table centers on reconstructing the narrative history attached to a worksheet submission. Reporting queries would retrieve comments by worksheet or review the text captured under a specific operation:

• Listing all submission comments for a given worksheet: SELECT OPERATION_ID, WORKSHEET_ID, COMMENTS FROM PSB_WS_SUBMIT_COMMENTS WHERE WORKSHEET_ID = :p_worksheet_id;
• Locating a specific comment payload by operation key: SELECT COMMENTS FROM PSB_WS_SUBMIT_COMMENTS WHERE OPERATION_ID = :p_operation_id;
• Audit-style extracts joining submission comments to worksheet headers to determine which review groups received narrative input.

Because the object is obsolete and unpopulated in the profiled database, these patterns are chiefly relevant to historical data migration, archival reporting, or reconciliation during an upgrade from a legacy PSB implementation.

Related Objects

In the absence of a mined FK set, the following relationships are inferred from the documented column semantics and PSB worksheet processing flow:

• PSB_WS_SUBMIT_COMMENTS_PK — the primary key constraint enforcing uniqueness on OPERATION_ID.
• Worksheet master tables referenced by WORKSHEET_ID — the header entity to which each comment is attached.
• Worksheet operation/log tables sharing the OPERATION_ID key space — companion records produced by the same submit operation.
• Review group definition tables — the recipients of the comments during the Submit Worksheet process described in the object definition.
• PSB worksheet submission APIs — the programmatic entry points that insert rows into this table at submit time.

Analysts should confirm actual join columns against the PSB data model of their specific release, since the available metadata documents only the three columns above and no explicit dependencies.