Results for “concurrent”

8 results




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

Overview

The concurrent program IBW_FACT_POPULATION belongs to the IBW - Oracle Web Analytics product family within Oracle E-Business Suite. Its user-facing name is Web Analytics: Fact Population Program. As documented, the program migrates data from a temporary schema into the Web Analytics fact/transaction schema. In practice, this places it at the boundary between the staging area where collected or intermediate data accumulates and the analytical tables that support Web Analytics reporting and aggregation. Because the target is a fact/transaction schema, the program is best understood as a data movement and consolidation step rather than a report generator or a transactional interface. The ETRM metadata for 12.2.2 explicitly records the program's Enabled flag as No, which indicates that in the documented environment the program is not active by default and would require deliberate enablement before it could be scheduled or submitted through standard concurrent processing.

Execution Details

The documented execution method for IBW_FACT_POPULATION is PL/SQL Stored Procedure, with an Argument Method of Standard. The executable is named IBW_FACT_POPULATION, and the execution filename given in the metadata is IBW_OE_PVT.offline_engine. This indicates that the concurrent program is bound to the offline_engine routine in the IBW_OE_PVT package. Because the execution method is a stored procedure rather than a host program or Java class, execution occurs entirely within the database tier under the privileges of the submitting user, subject to the standard concurrent manager security model. No subroutine name is documented separately, meaning the executable reference itself resolves to the intended PL/SQL entry point. Administrators reviewing this program in the Concurrent Programs form should expect the executable IBW_FACT_POPULATION to point at the IBW_OE_PVT.offline_engine PL/SQL routine.

How to Run

Like other concurrent programs, IBW_FACT_POPULATION would normally be submitted through the Standard Request Submission (SRS) window or an equivalent web-based submission page, such as the Submit Requests form. However, because the documented Enabled flag is No, it would not appear among submittable requests unless an administrator first enables it through the Concurrent Programs definition. With an Argument Method of Standard, any parameters defined for the program would be presented as ordinary SRS parameters and validated against their defined value sets. The ETRM excerpt does not enumerate specific parameters, so the parameter list should be confirmed directly in the concurrent program definition before any submission. Scheduling considerations matter here: because the program moves data into the Web Analytics fact schema, it should be run only during an appropriate batch window when the source temporary schema is populated and the target schema is not in active use.

Related Objects

The program operates across two schemas: the temporary schema holding source data and the Web Analytics fact/transaction schema receiving it. Related components typically include the Web Analytics collection and processing programs that populate the temporary schema, as well as the fact and transaction tables targeted by the migration. The owning PL/SQL package, IBW_OE_PVT, is the principal related code object, with offline_engine as the invoked routine. Analysis and reporting objects that consume the resulting fact data are also functionally related, since they depend on the migrated records being current. When troubleshooting, DBAs commonly review concurrent manager logs, the request output for the program, and the state of both source and target schemas to confirm the migration completed correctly.