Search Results cycle_count

Overview

OPI_DBI_BOUNDS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under ETRM as an OTHER object. It belongs to the Oracle Process Manufacturing (OPM) and Discrete Inventory business intelligence integration layer, where it manages the boundary conditions and transaction cut-offs used by the extract, transform, load (ETL) processes that populate the operational reporting tables. The package establishes, maintains, and validates the "bounds" — typically date and transaction identifier ranges — that determine which material transaction records are eligible for costing, costing rollups, and downstream analytics. It also centralises logging of concurrent program execution into OPI_DBI_CONC_PROG_RUN_LOG and performs organisation-level ledger data loading for OPM organisations. The header comment (OPIINVBNDB.pls, version 120.10, dated 2006) indicates the file has been stable and largely unchanged through the 12.1.1 and 12.2.2 releases, with the standard `$Header` line recognised by AD patch tooling.

Key Procedures and Functions

The package exposes 14 documented procedures and functions. The main entry point, MAINTAIN_OPI_DBI_LOGS, accepts an ETL type and load type and orchestrates logging of the run cycle; it deletes prior entries from OPI_DBI_CONC_PROG_RUN_LOG when an initial load is detected. CALL_ETL_SPECIFIC_BOUND dispatches the appropriate boundary-setting logic based on the requested ETL type.

• SETUP_INV_MMT_BOUNDS, SETUP_COGS_MMT_BOUNDS, SETUP_CC_MMT_BOUNDS, and SETUP_INV_WTA_BOUNDS configure bounds against material transaction and transaction account data for inventory, cost of goods sold, cycle count, and WIP transaction sources respectively.
• CREATE_FIRST_MMT_BOUNDS and SET_MMT_NEW_BOUNDS create an initial material transaction boundary and advance it to a new range after a successful run.
• SET_SYSDATE_BOUNDS derives bounds directly from the current system date.
• SET_LOAD_SUCCESSFUL records the completion state of an ETL load.
• PRINT_OPI_ORG_BOUNDS and BOUNDS_UNCOSTED provide diagnostic output and flag uncosted transactions.
• LOAD_OPM_ORG_LEDGER_DATA loads organisation-to-ledger relationships for OPM organisations.
• WRITE emits formatted debug messages governed by the AFLOG_ENABLED and AFLOG_MODULE profile options.

Tables Accessed

The package references seven tables via APPS synonyms. OPI_DBI_CONC_PROG_RUN_LOG stores the execution log for the DBI concurrent programs and is the object users commonly search when troubleshooting "opi_dbi_conc_prog_run_log". MTL_MATERIAL_TRANSACTIONS supplies the material transaction rows used to derive inventory bounds, while WIP_TRANSACTION_ACCOUNTS provides the accounting distributions used by SETUP_INV_WTA_BOUNDS. MTL_PARAMETERS supplies inventory organisation configuration, and GMF_FISCAL_POLICIES supplies the fiscal calendar needed to align date-based bounds with OPM accounting periods. OPI_DBI_ORG_LE_TEMP is the staging table used by LOAD_OPM_ORG_LEDGER_DATA, and DUAL supports isolated computations inside the bound-setting routines.

Usage Notes

OPI_DBI_BOUNDS_PKG is invoked indirectly by the DBI ETL concurrent programs rather than directly by end users. The CONC_* globals (CONC_PROGRAM_ID, CONC_REQUEST_ID, CONC_LOGIN_ID, PROG_APPL_ID) confirm the package runs within a concurrent manager session, and the package writes its progress to OPI_DBI_CONC_PROG_RUN_LOG so that concurrent program output can be reviewed from the standard Requests form. It is referenced by eight other packages, indicating it is a shared utility layer within the OPM/DBI suite. Custom code should not be modified without a registered CEMLI, and sites upgrading to 12.2.2 should verify existing bound records in OPI_DBI_CONC_PROG_RUN_LOG before re-running initial loads.