Search Results chv_org_options_u1

Overview

PO.CHV_ORG_OPTIONS is a Supplier Scheduling configuration table in Oracle E-Business Suite, holding the scheduling options and default values that drive Supplier Scheduling behavior for a given ship-to organization. The table is owned by the PO (Purchasing) schema, is registered under the FND Design Data object CHV.CHV_ORG_OPTIONS, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. It is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and it defines how cumulative (CUM) quantities, plan and ship schedule bucket patterns, and default planning designators are applied when Supplier Scheduling processes ship-to organizations.

In Data Vault modeling terms, the heuristic classification of CHV_ORG_OPTIONS is standalone. It carries a single-part primary key, CHV_ORG_OPTIONS_PK, defined on ORGANIZATION_ID, and there are no documented foreign key relationships to other tables. This suggests it is best modeled as a single-hub/satellite construct where ORGANIZATION_ID acts as the natural business key, with the remaining attributes behaving as descriptive satellite data. It is not a link table, since no association between multiple hubs is represented.

Key Information Stored

The table contains 35 documented columns. Its most significant attributes are:

• ORGANIZATION_ID — NUMBER; the schedule organization unique identifier. This is both the primary key of CHV_ORG_OPTIONS_PK and the single column of the unique index CHV_ORG_OPTIONS_U1, making it the definitive business key for the row.
• ENABLE_CUM_FLAG — VARCHAR2; indicates whether CUM tracking is enabled for the organization.
• RTV_UPDATE_CUM_FLAG — VARCHAR2; controls whether return-to-vendor (RTV) transactions are included in CUM calculations.
• PLAN_BUCKET_PATTERN_ID — NUMBER; the default plan schedule bucket pattern.
• SHIP_BUCKET_PATTERN_ID — NUMBER; the default ship schedule bucket pattern.
• PLAN_SCHEDULE_TYPE — VARCHAR2(25); the default plan schedule sub-type.
• SHIP_SCHEDULE_TYPE — VARCHAR2(25); the default ship schedule sub-type.
• MRP_COMPILE_DESIGNATOR — VARCHAR2(10); the default MRP plan.
• MPS_SCHEDULE_DESIGNATOR — VARCHAR2(10); the default MPS plan.
• DRP_COMPILE_DESIGNATOR — VARCHAR2(10); the default DRP plan.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — VARCHAR2 descriptive flexfield segments, with ATTRIBUTE_CATEGORY at length 30 and the ATTRIBUTE columns at length 150.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE, capturing the last concurrent request that modified the row.

The surrogate/primary key ORGANIZATION_ID doubles as the unique business-key candidate identified by the CHV_ORG_OPTIONS_U1 index; no separate surrogate is present. All other attributes are descriptive and belong conceptually to a satellite keyed on ORGANIZATION_ID.

Common Use Cases and Queries

This table is queried most often to determine how CUM management and schedule defaults are configured for a ship-to organization. A typical lookup retrieves the CUM flags and bucket patterns for a given organization:

• SELECT organization_id, enable_cum_flag, rtv_update_cum_flag, plan_bucket_pattern_id, ship_bucket_pattern_id FROM po.chv_org_options WHERE organization_id = :org_id;
• Reports listing all organizations where CUM tracking is enabled: SELECT organization_id FROM po.chv_org_options WHERE enable_cum_flag = 'Y';
• Validating default planning designators (MRP/MPS/DRP) per ship-to organization for Supplier Scheduling setup audits.
• Joining to organization and scheduling-bucket setup tables to surface the effective plan and ship schedule types for a scheduling run.
• Auditing the ATTRIBUTE flexfield segments and standard Who/REQUEST_ID columns to trace when and by which concurrent program the options were last changed.

Related Objects

The documented FK/PK relationship metadata describes CHV_ORG_OPTIONS as standalone, with the primary key CHV_ORG_OPTIONS_PK on ORGANIZATION_ID and the unique index CHV_ORG_OPTIONS_U1 on the same column. Because there are no formally declared foreign keys, related objects are associated functionally through ORGANIZATION_ID and through the scheduling setup identifiers referenced by the descriptive columns. Significant related objects include:

• HR_OPERATING_UNITS / HR_ALL_ORGANIZATION_UNITS — joined on ORGANIZATION_ID to resolve the ship-to organization name.
• PO.CHV_SCHEDULE_BUCKET_PATTERNS (bucket pattern definitions) — referenced by PLAN_BUCKET_PATTERN_ID and SHIP_BUCKET_PATTERN_ID.
• MRP/MPS/DRP plan definition views — referenced by the COMPILE_DESIGNATOR columns (MRP_COMPILE_DESIGNATOR, MPS_SCHEDULE_DESIGNATOR, DRP_COMPILE_DESIGNATOR).
• PO.CHV_SCHEDULE_TYPES and related Supplier Scheduling subtype lookups — referenced by PLAN_SCHEDULE_TYPE and SHIP_SCHEDULE_TYPE.
• CHV_ORG_OPTIONS API/SQL stored procedures used by the Supplier Scheduling forms and concurrent programs to read and maintain these defaults.

Because the table is standalone and keyed solely on ORGANIZATION_ID, join columns are consistently ORGANIZATION_ID when correlating to organization master data, and the *_PATTERN_ID, *_DESIGNATOR, and *_TYPE columns when resolving related scheduling setup entities.