Results for “stage_seq”

6 results




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

Overview

APPS.PSB_WS_QUERY_PROFILES_V is a database view in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the APPS schema and registered under the FND Design Data reference PSB.PSB_WS_QUERY_PROFILES_V. It belongs to the Public Sector Budgeting (PSB) product family and is classified as an internal Oracle view ("Oracle Internal Use Only"). Oracle Corporation explicitly does not support direct access to this object except from standard Oracle Applications programs, so it must be treated as an implementation detail rather than a supported integration surface.

Functionally, the view presents worksheet-level query profile configuration, including user-specific ordering preferences. It exposes the columns used to drive sort behavior within the PSB worksheet summary and Excel-based reporting framework, evidenced by its downstream dependency on APPS.PSB_EXCEL_PVT. Its status is VALID in the documented release.

Underlying Base Objects

The view is defined over two base tables, both in the APPS schema:

The view is referenced by APPS.PSB_EXCEL_PVT, which is the Excel integration package that consumes the profile rows when building worksheet output. No additional base objects are documented in the ETRM metadata.

Key Columns

  • ROW_ID (ROWID) — the physical row identifier; useful for correlated updates but not stable across reorganization.
  • WORKSHEET_ID (NUMBER) — identifies the worksheet the profile applies to.
  • USER_ID (NUMBER) — the FND_USER identifier owning the profile.
  • PROFILE_TYPE (VARCHAR2) — categorical discriminator for the profile record.
  • STAGE_SEQ (NUMBER) — sequencing attribute used to order profile stages.
  • TEMPLATE_ID / TEMPLATE_NAME — the summary template applied to the worksheet, resolved from PSB_SUMMARY_TEMPLATES.
  • YEAR_FLAG, SERVICE_PACKAGE_FLAG, ACCOUNT_FLAG, CURRENCY_FLAG — indicator flags controlling which dimension attributes participate in the worksheet query layout.
  • ORDER_BY_COLUMN1 … ORDER_BY_COLUMN5 (VARCHAR2(30)) — the first five sort column expressions. These are the columns most commonly searched, including ORDER_BY_COLUMN1.
  • ORDER_BY_COLUMN_NAME1 … ORDER_BY_COLUMN_NAME5 (VARCHAR2(30)) — human-readable display names corresponding positionally to the ORDER_BY_COLUMN1..5 entries.

Each ORDER_BY_COLUMNn column is paired positionally with ORDER_BY_COLUMN_NAMEn, allowing up to five levels of multi-column sorting per profile row.

Common Use Cases and Queries

The principal use case is diagnosing worksheet sort behavior — identifying why a worksheet's summary or Excel export orders rows in a given sequence. The following query retrieves the ordering configuration for a specific user and worksheet:

  • SELECT worksheet_id, user_id, profile_type, order_by_column1, order_by_column_name1, order_by_column2, order_by_column_name2 FROM apps.psb_ws_query_profiles_v WHERE user_id = :p_user_id ORDER BY worksheet_id;

To audit templates and their associated sort definitions:

  • SELECT template_id, template_name, order_by_column1, order_by_column_name1 FROM apps.psb_ws_query_profiles_v WHERE template_id = :p_template_id;

Because the view is flagged Oracle Internal Use Only, any query should be limited to read-only diagnostics and should not be embedded in custom production code. Standard Oracle Applications programs — notably PSB_EXCEL_PVT — remain the supported access path.