Results for “refresh_mode_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_OBJECTS is a table owned by the BIS schema within Oracle E-Business Suite, generally categorized under the Applications BIS product module. It functions as a registry of database and application objects that participate in the Business Intelligence System (BIS) refresh framework. Each row describes an individual object, its type, the application that owns it, and the parameters governing how that object is refreshed within the BIS data warehouse environment. The table therefore acts as metadata describing other objects, rather than holding transactional business data itself.

From a heuristic Data Vault modeling perspective, the supplied relationship data classifies this object as standalone, with no downstream foreign-key references and a single outbound reference to JTF_TASK_DEPENDS through the DEPENDENCY_ID column. This pattern suggests that BIS_OBJECTS behaves primarily as a reference or registry table, and in Data Vault terms would be modeled most naturally as a satellite attached to a hub keyed on the object identity, or as a standalone reference table if no stable business hub is defined. The classification is a modeling suggestion only and should be validated against actual usage and cardinality in each deployment.

Key Information Stored

The documented physical schema for release 12.1.1 shows 17 columns. The most significant columns for identification and refresh management are:

• OBJECT_NAME – the logical name of the registered object, serving as the primary business-key candidate.
• DATABASE_OBJECT_NAME and DATABASE_OBJECT_LONGNAME – the physical database object identifier (and its extended form), resolving the logical name to the actual schema object.
• OBJECT_TYPE_CODE – the classification of the object (for example table, view, or similar construct).
• APPLICATION_ID and REFRESH_APPLICATION_ID – the owning application and the application responsible for performing the refresh.
• DEPENDENT_OBJECT_NAME – the name of an object upon which this object depends.
• DEPENDENCY_ID – the foreign-key reference to JTF_TASK_DEPENDS, linking the object to the task dependency framework.
• REFRESH_PROCESS_ID – the identifier of the refresh process associated with the object.
• REFRESH_MODE_CODE – the mode governing how the refresh is executed (for example full versus incremental).
• LAST_REFRESH_TIME – the timestamp of the most recent refresh, used for monitoring and scheduling.
• DESCRIPTION – free-text description of the object and its purpose.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – standard EBS audit columns tracking the creation and last modification of each row.

The table does not expose an explicit surrogate primary key in the documented metadata; OBJECT_NAME combined with APPLICATION_ID, or DATABASE_OBJECT_NAME, are the practical unique-identifier candidates. Where a database-level unique index is defined, it should be treated as the authoritative business key.

Common Use Cases and Queries

BIS_OBJECTS is primarily consulted for dependency analysis, refresh monitoring, and impact assessment within the BIS environment. Typical scenarios include identifying objects that have not been refreshed recently, tracing which application owns a given database object, and enumerating refresh modes for scheduling and capacity planning.

• List objects and their last refresh times: SELECT OBJECT_NAME, OBJECT_TYPE_CODE, LAST_REFRESH_TIME FROM BIS.BIS_OBJECTS ORDER BY LAST_REFRESH_TIME DESC;
• Find objects owned by a specific application: SELECT OBJECT_NAME, OBJECT_TYPE_CODE FROM BIS.BIS_OBJECTS WHERE APPLICATION_ID = :app_id;
• Identify objects with a particular refresh mode: SELECT OBJECT_NAME, REFRESH_MODE_CODE FROM BIS.BIS_OBJECTS WHERE REFRESH_MODE_CODE = :mode;
• Resolve a database object to its logical registration: SELECT OBJECT_NAME, APPLICATION_ID FROM BIS.BIS_OBJECTS WHERE DATABASE_OBJECT_NAME = :db_name;
• Dependency analysis joining to the task dependency framework: SELECT o.OBJECT_NAME, o.DEPENDENT_OBJECT_NAME FROM BIS.BIS_OBJECTS o WHERE o.DEPENDENCY_ID IS NOT NULL;

Related Objects

The principal documented relationship is the outbound foreign key from BIS_OBJECTS.DEPENDENCY_ID to the JTF_TASK_DEPENDS table, which supplies the task-dependency definition linked to each registered object. Beyond that reference, the BIS_OBJECTS registry is consumed by the BIS refresh processes and by applications that query object metadata for scheduling and reporting. Related objects of interest typically include the BIS refresh-log and BIS object-type lookup tables, the Oracle Applications registry tables keyed by APPLICATION_ID, and the Object Dependency framework surrounding JTF_TASK_DEPENDS. Join keys follow the conventions shown: DEPENDENCY_ID for task dependencies, APPLICATION_ID and REFRESH_APPLICATION_ID for application context, and OBJECT_NAME or DATABASE_OBJECT_NAME for resolving the registered object to its physical counterpart.