Search Results aso_er_data_bin_fact

Overview

ASO_ER_DATA_BIN_FACT is a fact table within the ASO (Order Capture) module of Oracle E-Business Suite, documented as storing information required for Bin and Alert Reports. In the Order Capture architecture, "bins" refer to grouped result sets used by the Oracle Business Intelligence / Daily Business Intelligence (DBI) reporting layer that ships with EBS, where transactional and party-related metrics are pre-aggregated into category bins so that alerts, thresholds, and exception conditions can be evaluated efficiently. This table therefore functions as a reporting staging structure rather than a transactional base table.

The ETRM metadata assigns ASO_ER_DATA_BIN_FACT a heuristic Data Vault classification of satellite-leaning. This suggests that the table is best modelled as a satellite attached to a parent hub or link, holding descriptive and measurable attributes keyed by a surrogate identifier, rather than functioning as an independent hub of unique business entities or a link resolving many-to-many relationships. Its single outward foreign key to HZ_PARTIES reinforces this reading: the party reference is the dimensional anchor, while the remaining columns carry the fact-like payload.

The implementation note states that the table is "Not implemented in this database," indicating that it is seeded or created only when the relevant DBI/ETRM reporting features are enabled, and may be absent in a standard OLTP-only EBS instance.

Key Information Stored

The documented metadata identifies a small set of confirmed columns. The most important are:

• FACT_ID — the surrogate primary key, enforced by constraint ASO_ER_DATA_BIN_FACT_PK. This is the internal, system-generated identifier and is not a business key.
• PARTY_ID — foreign key to HZ_PARTIES. This is the principal business-key candidate, linking each fact row to a specific trading party (customer, prospect, or organisation) registered in the TCA (Trading Community Architecture) registry.

Based on the table's stated purpose, the remaining payload columns hold the measures and bin classifications consumed by Bin and Alert Reports — for example, categorical bin assignments, counts, monetary amounts, alert flag or severity values, and period or date-effective references used to scope each bin evaluation. Because Bin and Alert Reports operate on a per-party basis, PARTY_ID and FACT_ID together form the natural access path: the surrogate key supports the physical constraint, while PARTY_ID supports the meaningful query predicate. Where unique indexes exist beyond the primary key, they would most plausibly be composite indexes over PARTY_ID combined with the report's bin or period discriminators, though the metadata documents only the primary key explicitly.

Common Use Cases and Queries

The principal use case is the generation of Bin and Alert Reports, where rows are aggregated by party to determine which threshold categories a customer falls into. A typical query joins the fact table to the TCA registry to obtain party names alongside bin values:

• Party-level bin reporting: select all fact rows for a list of parties, joining ASO_ER_DATA_BIN_FACT.PARTY_ID to HZ_PARTIES.PARTY_ID to resolve PARTY_NAME and PARTY_NUMBER for presentation.
• Alert evaluation: filter fact rows by alert-related criterion columns and group by PARTY_ID to surface parties breaching configured thresholds.
• Extract patterns: because multiple EDW metadata tables reference FACT_ID, the table also serves as a source for warehouse extraction. A join pattern of the form ASO_ER_DATA_BIN_FACT f JOIN EDW_FACTS_MD m ON m.FACT_ID = f.FACT_ID resolves warehouse fact definitions against the EBS fact rows.
• Referential integrity checks: anti-joins against HZ_PARTIES identify orphaned fact rows where the referenced party has been merged or purged.

Queries should be written against FACT_ID and PARTY_ID only, as other columns are not confirmed in the available metadata.

Related Objects

The following objects are the most significant dependencies, drawn from the documented foreign key relationships:

• HZ_PARTIES — referenced by ASO_ER_DATA_BIN_FACT.PARTY_ID; the primary dimensional parent holding party identity.
• EDW_FACTS_MD — references ASO_ER_DATA_BIN_FACT.FACT_ID; warehouse fact metadata.
• EDW_FACT_ATTRIBUTES_MD — references FACT_ID; defines fact attribute metadata.
• EDW_FACT_HIER_MD — references FACT_ID; holds fact hierarchy definitions.
• EDW_FACT_DIM_RELATIONS_MD — references FACT_ID; maps facts to dimensions.
• EDW_CALSUM4_BSC — references FACT_ID; balanced scorecard calendar summary.
• EDW_SEC_FACT_INFO_T and EDW_SEC_ITEMSET_INFO_T — reference FACT_ID; warehouse security information sets.
• EDW_SEC_REF_INFO_T and EDW_CDI_DIM_MISSING_KEYS — reference FACT_ID for security references and missing-key diagnostics.

These EDW-prefixed objects confirm that ASO_ER_DATA_BIN_FACT participates in the EBS data warehouse metadata layer, with FACT_ID acting as the shared join column across the analytic infrastructure.