Results for “cst_inquiry_types”

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

Overview

CST_INQUIRY_TYPES is a reference (setup) table owned by the BOM schema in Oracle E-Business Suite, holding the definitions of the item cost inquiry types presented through the Cost Inquiry and related inquiry screens. Each row describes one inquiry type — its internal name, display captions, the underlying view that supplies its data, and the flexfield context used for descriptive columns. In EBS 12.1.1 the table exists under the same BOM ownership and structure; in 12.2.2 the documented physical schema reflects thirty columns, including the editioning column ZD_EDITION_NAME introduced by the Online Patching (AD_ZD) infrastructure.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone — that is, a hub-like reference object rather than a link or satellite. The heuristic suggests treating UNIQUE_ID as the durable business key of an inquiry-type hub, with descriptive and audit attributes (caption prompts, view name, flags, dates) carried as satellite context.

Key Information Stored

The documented primary key is CST_INQUIRY_TYPES_PK, defined on the surrogate identifier UNIQUE_ID. Two business-key candidates are documented as unique indexes: CST_INQUIRY_TYPES_U1 (UNIQUE_ID, ZD_EDITION_NAME) and CST_INQUIRY_TYPES_U2 (INQUIRY_NAME, ZD_EDITION_NAME), establishing INQUIRY_NAME as the natural (user-facing) key of an inquiry type, protected per edition.

The most operationally significant columns include:

• UNIQUE_ID — surrogate primary key; the internal row identifier used by foreign references and by the UK1 constraint noted in the ETRM excerpt.
• INQUIRY_NAME — the business key and internal name of the inquiry type; constrained by CST_INQUIRY_TYPES_UK1 in the documented metadata.
• DESCRIPTION — user-visible description of the inquiry type.
• USER_DEFINED — indicates whether the inquiry type is seeded by Oracle or created by the customer.
• TEMPLATE_TYPE and GUI_TEMPLATE_TYPE — control the display template used by the forms/HTML rendering layer.
• VIEW_NAME — the database view that supplies rows for the inquiry, binding the setup row to its data source.
• COLUMN1_HEADING, COLUMN2_HEADING, DESCRIPTION_COLUMN_HEADING — report/column captions for the inquiry output.
• GUI_COL1_PROMPT_TOP, GUI_COL1_PROMPT_BOTTOM, GUI_COL2_PROMPT_TOP, GUI_COL2_PROMPT_BOTTOM, GUI_DESC_PROMPT — GUI prompt text for the inquiry's selection criteria.
• INVENTORY_FLAG — controls whether inventory-related costing data is included.
• DISABLE_DATE — the date on which the inquiry type is end-dated and no longer offered.
• FLEXFIELD_APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME — identify the descriptive flexfield context applied to the inquiry.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request audit columns populated when the row is maintained or refreshed.
• ZD_EDITION_NAME — Online Patching edition discriminator, part of both unique indexes in 12.2.2.

Common Use Cases and Queries

Cost analysts and implementers query this table to enumerate the available cost inquiry types, confirm which are Oracle-seeded versus user-defined, and verify the view and flexfield bindings before extending a custom inquiry. A typical listing filters out disabled rows:

• SELECT unique_id, inquiry_name, description, view_name FROM bom.cst_inquiry_types WHERE disable_date IS NULL;
• SELECT inquiry_name, user_defined, template_type FROM bom.cst_inquiry_types ORDER BY inquiry_name;
• Join to the underlying inquiry view using the value in VIEW_NAME for ad hoc cost analysis or custom reporting.
• Reconcile against FND_DESCRIPTIVE_FLEXS via FLEXFIELD_APPLICATION_ID / DESCRIPTIVE_FLEXFIELD_NAME when customizing prompts.

In 12.2.2, queries executed against the table directly should be aware that the editioning column ZD_EDITION_NAME participates in the unique indexes; standard EBS queries generally rely on the editioning view exposed by the application.

Related Objects

Because the vault classification is standalone, there are no documented foreign keys radiating from CST_INQUIRY_TYPES. The significant related objects are therefore functional and metadata-level dependencies:

• CST_INQUIRY_TYPES_PK / CST_INQUIRY_TYPES_U1 / CST_INQUIRY_TYPES_U2 — the primary and unique constraints that enforce UNIQUE_ID and INQUIRY_NAME.
• FND_DESCRIPTIVE_FLEXS — joined on APPLICATION_ID = FLEXFIELD_APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_APPLICATION_ID and PROGRAM_ID for the maintaining program.
• FND_CONCURRENT_REQUESTS — matched on REQUEST_ID for audit of the last refresh run.
• FND_APPLICATION — resolves the application identifiers to application names.
• BOM.CST_ITEM_COSTS and the Cost Inquiry inquiry views named in VIEW_NAME — the primary consumers of the setup rows at runtime.

Together these objects position CST_INQUIRY_TYPES as the configuration hub that drives how item cost inquiry is presented across the Bills of Material and Cost Management modules.