Search Results bom_resource_flex_fences_u1

Overview

BOM.BOM_RESOURCE_FLEX_FENCES is an Oracle E-Business Suite table that stores resource flexibility fence definitions used by Oracle Bills of Material and Oracle Capacity. A flexibility fence defines a tolerance percentage by which the current available capacity of a specific resource — or of a production line associated with a department — may be increased beyond the standard capacity. Because the tolerance is only valid from a defined future horizon, each row couples the tolerance percentage with the number of fence days that must elapse before the tolerance becomes applicable. In practice, the table answers the planning question: "Given that a resource will not be needed until N days from now, by what percentage may its capacity be stretched?" This allows capacity planners and the planning engine to model controlled overloading of constrained resources in the medium- and long-term horizon without over-committing near-term capacity.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, while its unique index is held separately in APPS_TS_TX_IDX. The documented owner is the BOM schema and the object carries a VALID status in ETRM for both 12.1.1 and 12.2.2.

Under a Data Vault modeling heuristic, the FK structure (DEPARTMENT_ID referencing BOM_DEPARTMENTS) combined with a composite unique business key suggests this table behaves as a link candidate — associating a department, a resource, and a fence horizon — rather than a pure reference hub. This classification is a modeling suggestion only; the physical implementation remains a standard EBS transactional table.

Key Information Stored

The most operationally significant columns are:

• DEPARTMENT_ID — Numeric identifier of the department (production line context) to which the fence applies. Part of the unique business key and the sole documented foreign key, referencing BOM_DEPARTMENTS.
• RESOURCE_ID — Unique identifier of the resource whose capacity is being flexed. Part of the unique business key.
• FENCE_DAYS — Number of days in the time fence; the horizon after which the tolerance becomes effective. Part of the unique business key.
• TOLERANCE_PERCENTAGE — The percentage by which present capacity of the resource or line may be increased beyond the fence horizon. This is the core planning value of the row.
• ATTRIBUTE_CATEGORY — Descriptive flexfield structure-defining column, enabling site-specific extension of the table.
• ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments (VARCHAR2(150) each) available for customer-defined data.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard Who columns providing audit and concurrency context.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program request context, identifying the process that last touched the row.

The documented unique index BOM_RESOURCE_FLEX_FENCES_U1 spans (DEPARTMENT_ID, RESOURCE_ID, FENCE_DAYS), making that triplet the business-key candidate. No separate surrogate primary-key column is documented; the unique index effectively enforces one tolerance definition per department, resource, and fence horizon.

Common Use Cases and Queries

Typical usage includes capacity planning reports that show, per resource, the tolerance percentage applicable at each fence horizon, and validation queries confirming that no duplicate fence definitions exist for a resource. A representative query joining the fence definition back to its department is:

• SELECT f.department_id, f.resource_id, f.fence_days, f.tolerance_percentage FROM bom.bom_resource_flex_fences f WHERE f.fence_days >= :horizon ORDER BY f.department_id, f.resource_id, f.fence_days;
• Joining to BOM_DEPARTMENTS to resolve the department name: SELECT d.department_code, f.resource_id, f.fence_days, f.tolerance_percentage FROM bom.bom_resource_flex_fences f, bom.bom_departments d WHERE f.department_id = d.department_id;
• Audit queries filtering on last_update_date to identify fence definitions recently changed by a named user or concurrent program.

Reporting is frequently performed through the resource and department capacity windows in Oracle Capacity and Oracle Bills of Material, which read this table rather than querying it directly.

Related Objects

• BOM.BOM_DEPARTMENTS — Referenced via BOM_RESOURCE_FLEX_FENCES.DEPARTMENT_ID; the parent department/line definition.
• BOM.BOM_RESOURCES — Parent of RESOURCE_ID; supplies resource attributes such as capacity, UOM, and availability.
• BOM.BOM_RESOURCE_CHARGES and BOM.BOM_RESOURCE_SHIFTS — Sibling resource tables used together with flex fences in capacity rollups.
• BOM.BOM_CALENDARS / BOM.BOM_SHIFT_TIMES — Calendar and shift definitions that determine base capacity before tolerance is applied.
• BOM.BOM_DEPARTMENT_RESOURCES — Associates resources to departments and underpins the department-resource pairing.
• BOM Resource and Capacity concurrent programs — Processes such as resource rollup and capacity load populate and read fence data during planning runs.