Search Results rev_col_flag

Overview

PA_CI_TYPES_B is the core definition table within the Oracle Projects (PA) module that stores control item type definitions. Control items are a foundational construct in Oracle Projects used to represent change orders, issues, risks, action items, and similar project control records. Each row in PA_CI_TYPES_B defines a distinct control item type that the customer creates, along with the behavioral rules governing how control items of that type are numbered, approved, resolved, and reported. The table resides in the PA schema and is marked VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the ETRM heuristic classifies PA_CI_TYPES_B as hub-leaning. This is a reasonable suggestion: the table functions as a business-concept hub that anchors a stable CI_TYPE_ID business key, with descriptive flags and attributes that could be modeled as satellites in a dimensional warehouse. Downstream transactional tables reference the hub through foreign key relationships, consistent with standard hub-and-satellite patterns.

Key Information Stored

The 44-column structure centers on configuration and control flags rather than transactional data. The most significant columns include:

• CI_TYPE_ID — The surrogate primary key (PA_CI_TYPES_B_PK) that uniquely identifies each control item type. It is also the primary business-key candidate, as evidenced by the unique index PA_CI_TYPES_B_U1 on (CI_TYPE_ID, ZD_EDITION_NAME).
• CI_TYPE_CLASS_CODE — Classifies the control item type (for example, change order, issue, or risk), driving much of the downstream behavior.
• AUTO_NUMBER_FLAG and PREFIX_AUTO_NUMBER — Control whether control items receive system-generated numbers and the prefix applied to them.
• APPROVAL_REQUIRED_FLAG and APPROVAL_TYPE_CODE — Determine whether a type requires approval workflow and what approval mechanism is used.
• RESOLUTION_REQUIRED_FLAG — Indicates whether a control item of this type must be formally resolved before closure.
• SOURCE_ATTRS_ENABLED_FLAG and ALLOW_ALL_USAGE_FLAG — Govern whether source attributes are captured and whether all usage contexts are permitted.
• CLASSIFICATION_CATEGORY, REASON_CATEGORY, RESOLUTION_CATEGORY — Reference category codes used to classify, justify, and resolve control items; REASON_CATEGORY carries an FK to PA_CLASS_CATEGORIES.
• IMPACT_BUDGET_TYPE_CODE, COST_COL_FLAG, REV_COL_FLAG, DIR_COST_REG_FLAG, SUPP_COST_REG_FLAG, DIR_REG_REV_COL_FLAG — Determine how control items impact budget types and cost/revenue accounting.
• SUBCONTRACTOR_REPORTING_FLAG — Enables subcontractor reporting for the type.
• START_DATE_ACTIVE / END_DATE_ACTIVE and RECORD_VERSION_NUMBER — Provide date-effective validity ranges and optimistic locking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — The standard Oracle flexfield (descriptive flexfield) columns for customer-defined extensibility. The trailing ZD_EDITION_NAME column supports edition-based redefinition in 12.2.

Common Use Cases and Queries

Implementation teams query this table to inventory configured control item types, validate that approval and resolution flags align with business process requirements, and audit the flexfield and category assignments. A typical lookup retrieves active types:

• SELECT ci_type_id, ci_type_class_code, auto_number_flag, approval_required_flag FROM pa_ci_types_b WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);
• Joining to TL for translatable names: SELECT b.ci_type_id, t.name, b.ci_type_class_code FROM pa_ci_types_b b, pa_ci_types_tl t WHERE b.ci_type_id = t.ci_type_id AND t.language = USERENV('LANG');
• Reporting the volume of control items per type: SELECT b.ci_type_id, COUNT(c.control_item_id) FROM pa_ci_types_b b, pa_control_items c WHERE b.ci_type_id = c.ci_type_id GROUP BY b.ci_type_id;
• Auditing usage configuration via PA_CI_TYPE_USAGE and impact settings via PA_CI_IMPACT_TYPE_USAGE.

Related Objects

PA_CI_TYPES_B is referenced by several dependent tables through CI_TYPE_ID foreign keys:

• PA_CONTROL_ITEMS — The primary transactional table storing individual control items; joins on CI_TYPE_ID.
• PA_CI_TYPES_TL — The translation table providing language-specific names and descriptions, joined on CI_TYPE_ID.
• PA_CI_TYPE_USAGE — Defines where each control item type may be used, joined on CI_TYPE_ID.
• PA_CI_IMPACT_TYPE_USAGE — Controls budget/impact type applicability, joined on CI_TYPE_ID.
• PA_CI_SUPPLIER_DETAILS — Holds supplier-related detail for control item types, joined on CI_TYPE_ID.
• PA_PT_CO_IMPL_STATUSES — Manages implementation statuses for change orders, joined on CI_TYPE_ID.
• PA_OBJ_STATUS_LISTS — References the type via PCB_CI_TYPE_ID.
• PA_CLASS_CATEGORIES — Referenced by PA_CI_TYPES_B via REASON_CATEGORY, forming the sole outbound foreign key.

Together these relationships establish PA_CI_TYPES_B as the configuration hub that underpins the entire Oracle Projects control item framework.