Search Results bic_lc_setup_all




Overview
Explore in AI Chat

Overview

BIC_LC_SETUP_ALL is a table owned by the BIC schema (Customer Intelligence) in Oracle E-Business Suite 12.1.1 and 12.2.2. The product line is documented as obsolete, meaning Oracle no longer actively develops or supports Customer Intelligence functionality within the standard EBS footprint. Despite this status, the table remains VALID in the data dictionary, and legacy installations may still reference it for historical reporting, migration, or archival purposes.

The table is described as holding "Lifecycle related Setup information." In practice, this suggests it stored configuration or staging parameters that governed how lifecycle processing—typically customer lifecycle analytics and derived measures—was defined and executed within the BIC product. It captures stage-level definitions along with comparison operators and threshold values used during analysis.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. This is a modeling suggestion only: the table does not participate in a conventional hub-and-link topology as mined from its foreign key structure, but rather behaves as an independent or loosely coupled reference/setup entity. Analysts modeling this into a vault would likely treat it as a standalone satellite or reference table rather than a core hub.

Key Information Stored

The table contains 15 documented columns, with the most significant summarized below:

The unique index BIC_LC_SETUP_U1 (STAGE_ID, ZD_EDITION_NAME) establishes the business-key candidate. Notably, there is no single-column surrogate primary key documented; the unique index serves as the effective identifier.

Common Use Cases and Queries

Because the BIC product is obsolete, primary use cases involve data extraction, historical analysis, and migration off the legacy schema. Typical patterns include:

  • Reporting on lifecycle stage thresholds configured per organization.
  • Auditing which stages were active or customized prior to decommissioning.
  • Migrating setup definitions into a supported analytics platform.

A representative query joining to the stage definition might resemble:

  • SELECT s.STAGE_ID, s.STAGE_CODE, s.STAGE_NAME, s.MEASURE_VALUE1, s.MEASURE_VALUE1_OP FROM BIC.BIC_LC_SETUP_ALL s WHERE s.STAGE_ID = :stage_id;

When querying in a 12.2 environment, analysts should filter or be aware of ZD_EDITION_NAME to avoid returning rows from multiple editions during the online patching cycle.

Related Objects

  • ECE_STAGE — Joined via STAGE_ID; provides the stage master definition.
  • FND_SECURITY_GROUPS — Joined via SECURITY_GROUP_ID; controls row-level access.
  • BIC_LC_SETUP_U1 — The unique index enforcing (STAGE_ID, ZD_EDITION_NAME).
  • Other BIC lifecycle and staging tables that share the STAGE_ID and SECURITY_GROUP_ID keys, used together in setup and processing flows.

Given its obsolete status and standalone classification, dependency analysis should focus on these two documented foreign keys and the unique index rather than a broad relational web.