Search Results msc_st_supplier_flex_fences




Overview
Explore in AI Chat

Overview

MSC_ST_SUPPLIER_FLEX_FENCES is a staging table in the MSC schema of Oracle Advanced Supply Chain Planning (ASCP). It serves as the temporary landing area for records collected from source systems before they are validated, cleansed, and promoted into the base planning table MSC_SUPPLIER_FLEX_FENCES. In Oracle EBS 12.1.1 and 12.2.2, this staging pattern is standard across the MSC collection infrastructure: the collection program extracts data from a source instance, writes it to an MSC_ST_* table, applies validation and transformation logic, and then inserts or updates the corresponding base table consumed by the planning engine.

Supplier flex fences define time-based thresholds (fence days) and tolerance percentages that control how supply chain planning engines respond to changes in supplier commitments, capacity, or lead times. The staging table therefore carries the raw, source-qualified representation of those fences—vendor identity, item, organization context, and source instance metadata—prior to planner-facing use.

From a Data Vault modeling perspective, the metadata classifies this table as standalone, with no inbound dependencies beyond a single foreign key to PN_COMPANIES_ALL. Heuristically, the base table MSC_SUPPLIER_FLEX_FENCES is best understood as a satellite keyed by supplier/site/item/organization combinations, while the staging table functions as a transient landing structure rather than a persistent hub or link.

Key Information Stored

The table contains 32 documented columns. The most significant business columns include:

No explicit surrogate primary key or unique index is documented in the supplied metadata; business-key candidates are the combination of supplier, site, item, and organization. The collection-control columns (BATCH_ID, REFRESH_ID, PROCESS_FLAG) separate rows per collection run.

Common Use Cases and Queries

Typical uses center on diagnosing collection failures and verifying fence data before it reaches the planning engine.

  • Identifying rows that failed validation: SELECT * FROM msc.msc_st_supplier_flex_fences WHERE process_flag = 'E';
  • Reviewing collected fences by source instance and batch: filter on SR_INSTANCE_ID and BATCH_ID.
  • Reconciling staged rows against the base table MSC_SUPPLIER_FLEX_FENCES by supplier, site, item, and organization.
  • Reporting on fence coverage by organization or vendor using ORGANIZATION_CODE and VENDOR_NAME.
  • Auditing load errors through ERROR_TEXT and the request identifiers (REQUEST_ID, PROGRAM_ID).

Related Objects

  • MSC_SUPPLIER_FLEX_FENCES — the base planning table this staging table feeds.
  • PN_COMPANIES_ALL — referenced via the documented foreign key MSC_ST_SUPPLIER_FLEX_FENCES.COMPANY_ID → PN_COMPANIES_ALL.
  • MSC_ST_SUPPLIERS / MSC_ST_SUPPLIER_SITES — companion staging tables supplying vendor and site context.
  • MSC_ST_ITEMS — provides inventory item context for INVENTORY_ITEM_ID.
  • MSC_SYSTEM_ITEMS / MSC_ORG_ASSIGNMENTS — define item-organization relationships used during validation.
  • MSC_COLLECTIONS / MSC_REFRESH_IDS — collection-run control structures referenced via REFRESH_ID and BATCH_ID.