Results for “check_db_version”

8 results




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

Overview

CST_UTILITY_PUB is the public utility package of the Oracle EBS Cost Management (CST) module. It provides a shared library of low-level helper routines that other Cost Management APIs, concurrent programs, and transactional processes call to resolve cost accounts, evaluate system flags, retrieve category and event identifiers, and write diagnostic messages to the concurrent manager log. The package is classified as a public (PUB) API in the APPS schema and is documented in ETRM for both release 12.1.1 and 12.2.2. Its header comment carries the RDBMS version marker $Header: CSTUTILB.pls 120.6.12010000.2, confirming its presence across the 12.1.x code line and its continued shipment in 12.2.x. The extensive reuse of this package — it is referenced by 45 other packages — reflects its role as a foundational service layer rather than a user-facing transaction API.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions. The account and configuration lookups are the most significant:

  • GET_DIRECT_ITEM_CHARGE_ACCT — the routine targeted by the "get_direct_item_charge_acct" search. It returns the direct item charge account used when a material transaction must be charged directly to an item-related account rather than through the standard cost element hierarchy.
  • GET_STD_CG_ACCT_FLAG — returns the flag governing whether the standard cost group account derivation applies.
  • GETTXNCATEGORYID — resolves the transaction category identifier used to associate transactions with cost categories.
  • GET_CONTEXT_VALUE — retrieves context values required by cost derivation logic.
  • GET_RECEIPT_EVENT_INFO — supplies receipt event information, supporting the mapping of receiving events to accounting events.
  • GET_ZEROCOSTISSUE_FLAG — indicates whether zero-cost issues are permitted.
  • INSERT_MTA — inserts rows into the material transaction accounts table, writing the accounting distributions produced by transaction costing.
  • WRITELOGMESSAGES — loops through the FND message stack and writes each message to the concurrent manager log via FND_FILE.PUT_LINE, using the standard FND_API compatible-call and return-status conventions.
  • GET_RET_STS_SUCCESS, GET_RET_STS_ERROR, GET_RET_STS_UNEXP_ERROR, GET_TRUE, GET_FALSE, GET_LOG, GET_ZEROCOSTISSUE_FLAG, CHECK_DB_VERSION — small accessor functions returning standardized constants, log handles, and version validation results.

Tables Accessed

All table access is performed through APPS synonyms. The account derivation routines read GL_CODE_COMBINATIONS for valid account combinations, CST_COST_ELEMENTS and CST_CAT_ELE_EXP_ASSOCS for cost element and category expense association rules, and GL_ENCUMBRANCE_TYPES where encumbrance accounting applies. Transaction processing touches MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_ACCOUNTS, MTL_SYSTEM_ITEMS_B, MTL_ITEM_CATEGORIES, MTL_DEFAULT_CATEGORY_SETS, MTL_SECONDARY_INVENTORIES, and MTL_PARAMETERS to establish item, category, and inventory context. Manufacturing integration draws on BOM_RESOURCES and WIP_DISCRETE_JOBS, while subledger integration uses CST_XLA_RCV_EVENT_MAP to link receiving events to XLA accounting events. FND_CURRENCIES supplies currency attributes.

Usage Notes

CST_UTILITY_PUB is not invoked directly by end users. It is called from Cost Management concurrent programs (for example, transaction cost processing and period close routines), from Cost Management forms through their underlying APIs, and from custom extensions that require the same account derivation rules as standard costing. Because the package is a PUB interface, custom code may call it, but callers should observe the standard FND_API conventions — passing an API version and inspecting the returned status — as the documented procedures follow that pattern. In 12.2.x, the account derivation functions remain relevant because they continue to supply the accounts consumed by the Subledger Accounting (XLA) engine, with CST_XLA_RCV_EVENT_MAP bridging receiving events to SLA event processing.