Results for “gl_cost_mthd”

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

Overview

The OPI_OPM_GL_CALENDAR_V view is a read-only database object owned by the APPS schema in Oracle E-Business Suite. It resides in the OPI (Operations Intelligence) product family, the reporting and analytics layer historically associated with Oracle Process Manufacturing (OPM). Its documented purpose is to expose Oracle General Ledger calendar data for Oracle Process Manufacturing companies. In effect, the view bridges the OPM costing and shop-floor world with the GL accounting calendar, allowing reporting tools, concurrent programs, and ad hoc queries to retrieve period definitions side-by-side with the costing method assigned to a given set of books.

The view is marked VALID in the ETRM 12.2.2 metadata, which confirms that the underlying definition compiles successfully against the referenced dictionary objects. Users searching on the term gl_cost_mthd are typically trying to reconcile OPM inventory and manufacturing costs with the GL periods in which those costs are accounted, making this view a natural entry point.

Underlying Base Objects

The view definition joins three public General Ledger and costing dictionary objects:

• GL_PERIODS — supplies the individual period rows, including PERIOD_TYPE, PERIOD_YEAR, QUARTER_NUM, PERIOD_NUM, PERIOD_NAME, START_DATE, and END_DATE.
• GL_SETS_OF_BOOKS — supplies the set of books context, linking PERIOD_SET_NAME and ACCOUNTED_PERIOD_TYPE to the ledger definition.
• GL_PLCY_MST — the cost policy master, which contributes the GL_COST_MTHD (costing method) attribute and is matched on SET_OF_BOOKS_NAME.

The join conditions are GP.PERIOD_SET_NAME = GSB.PERIOD_SET_NAME, GSB.NAME = GPM.SET_OF_BOOKS_NAME, and GP.PERIOD_TYPE = GSB.ACCOUNTED_PERIOD_TYPE. Adjustment periods are excluded through the predicate GP.ADJUSTMENT_PERIOD_FLAG <> 'Y', so only standard, non-adjustment accounting periods are returned. The ETRM metadata does not document a direct OPM base table; the mapping to OPM companies is achieved through the cost policy master and the ledger name.

Key Columns

The view exposes nine columns, each carrying specific meaning:

• CO_CODE — the company code, identifying the OPM or GL entity associated with the period context.
• PERIOD_TYPE — the accounting period type, such as Month, Quarter, or Year, as defined on the set of books.
• PERIOD_YEAR — the fiscal or calendar year of the period.
• QUARTER_NUM — the quarter number within the year.
• PERIOD_NUM — the sequence number of the period within its year.
• PERIOD_NAME — the human-readable period label, commonly used in reporting headers.
• START_DATE and END_DATE — the effective date boundaries of the period, essential for date-range transaction filtering.
• GL_COST_MTHD — the GL costing method tied to the set of books; this is the column most frequently targeted by searches on gl_cost_mthd.

Common Use Cases and Queries

This view is typically used to drive period-based cost reporting, to validate that transaction dates fall within open GL periods, and to retrieve the costing method in force for a ledger. A representative query returns period and costing method information for a specific year:

• SELECT co_code, period_name, start_date, end_date, gl_cost_mthd FROM apps.opi_opm_gl_calendar_v WHERE period_type = 'Month' AND period_year = 2023 ORDER BY period_num;
• SELECT DISTINCT gl_cost_mthd FROM apps.opi_opm_gl_calendar_v; — used to enumerate the costing methods present across ledgers.
• SELECT period_name, start_date, end_date FROM apps.opi_opm_gl_calendar_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND end_date; — to identify the currently open period.

Because the view is defined over GL tables and the cost policy master, it is also a convenient join partner when reconciling OPM cost transactions against GL period boundaries in custom Operations Intelligence reports.