Search Results update_fact

Overview

ISC_DBI_BSA_OBJECTS_C is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technology Reference Manual) as an OTHER API rather than a public, supported interface. The name components indicate its role: "ISC" designates the Supply Chain Intelligence/Information Discovery family of applications, "DBI" denotes Daily Business Intelligence, and "BSA" refers to the Balanced Scorecard Analytics or Business Summary Aggregate area. The package therefore belongs to the Daily Business Intelligence for Supply Chain collection layer, responsible for populating and refreshing summary fact data that feeds DBI dashboards and balanced scorecard reporting.

The package is a facts collection program wrapper: it marshals transactional and master data from the Oracle Order Management and Receivables table families into a DBI staging and summary fact table, so that pre-aggregated performance indicators for order capture, blanket agreements, and customer activity are available without querying high-volume base tables at report run time. The source header comment (ISCSCFAS.pls 120.0, dated 2005/08/30, marked noship) confirms it originates from the DBI Supply Chain facts collection layer and has been carried forward largely unchanged into the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The ETRM metadata documents two public procedures. Parameter lists are intentionally omitted here; only purposes are described.

• LOAD_FACT — Performs the initial or full collection pass for the BSA objects fact. It reads the source order, blanket, and customer records and inserts the corresponding rows into the DBI fact and temporary staging tables. It is the entry point used when no prior fact data exists for the period being collected, or when a complete rebuild of the summary is required.
• UPDATE_FACT — Performs the incremental refresh. It reconciles the existing fact content against the current state of the source tables, inserting new qualifying rows, amending changed measures, and removing rows that no longer satisfy the collection criteria. This is the procedure most commonly scheduled on a recurring basis and is the object of the user's search term.

Both procedures follow the standard concurrent-program PL/SQL signature convention, accepting the errbuf and retcode OUT parameters that report completion status and messages back to the Concurrent Manager.

Tables Accessed

The package operates across three functional groups of tables, resolved through APPS synonyms:

• Order and blanket agreement sources: OE_BLANKET_HEADERS_ALL, OE_BLANKET_HEADERS_EXT, OE_BLANKET_LINES_ALL, OE_BLANKET_LINES_EXT, and ISC_CURR_BSA_ORDER_LINES. These supply the agreement-level and line-level transactional detail that the BSA facts measure.
• Customer and reference data: HZ_CUST_ACCOUNTS, JTF_RS_SRP_GROUPS, OE_REASONS, and FII_TIME_DAY. These provide the customer, resource group, reason, and calendar dimensions needed to slice the facts by account, sales resource, and day.
• DBI fact and staging targets: ISC_DBI_BSA_ORDER_LINES_F, ISC_DBI_TMP_BSA_ORDER_LINES, and ISC_BOOK_SUM2_F. The _F table is the published fact target, while the _TMP table is used for intermediate staging during collection. DBMS_SQL is referenced for dynamic SQL construction within the collection logic.

Usage Notes

ISC_DBI_BSA_OBJECTS_C is not intended for direct invocation by end users or custom forms. It is executed by the DBI Supply Chain facts collection concurrent programs, typically scheduled through the Daily Business Intelligence administrator responsibility or invoked by the higher-level DBI collection driver after the underlying source tables have been refreshed. In 12.1.1 and 12.2.2 the package is shipped as a noship-originated internal object, and no other package in the documented metadata references it, reinforcing its position at the top of the dependency chain rather than as a reusable utility.

Because it is classified as OTHER, customizations that call or wrap these procedures are not covered by Oracle support. Any modification to collection timing, source filters, or the fact target should be assessed against the DBI collection dependencies, since the LOAD_FACT and UPDATE_FACT procedures work as a pair — LOAD_FACT for initial population and UPDATE_FACT for scheduled incremental maintenance — and inconsistent execution ordering can leave the BSA fact tables out of step with the underlying order and blanket agreement data.