Search Results cst_xla_pvt




Overview
Explore in AI Chat

Overview

APPS.CST_XLA_PVT (Package Body) is a private utility package within the Oracle E-Business Suite Cost Management module that serves as the primary integration layer between Cost Management (CST) transactional data and the Subledger Accounting (XLA) engine. In EBS 12.1.1 and 12.2.2, all subledgers must create accounting events, event entities, and journal entries through the common XLA framework rather than posting directly to the General Ledger. CST_XLA_PVT performs this role for inventory, receiving, work in process, and cost update transactions. The package identifies accounting-relevant cost transactions, constructs the corresponding XLA event structures, and submits them to the accounting program interfaces. The package carries a private (PVT) API classification, indicating that it is intended for internal invocation by Cost Management and Subledger Accounting programs rather than for direct use by customer extensions.

Key Procedures and Functions

The package exposes ten documented procedures and functions, organized around event creation and policy determination:

  • CREATE_INVXLAEVENT — Creates XLA accounting events for inventory material transactions.
  • CREATE_RCVXLAEVENT — Creates XLA accounting events for purchasing receipt transactions.
  • CREATE_WIPXLAEVENT — Creates XLA accounting events for discrete work in process transactions.
  • CREATE_WIPUPDATEXLAEVENT — Creates XLA accounting events arising from WIP cost updates.
  • CREATE_COSTUPDATEXLAEVENT — Creates XLA accounting events for cost update transactions that revalue inventory balances.
  • CREATEBULK_WIPXLAEVENT — Provides a bulk-processing variant for WIP event creation, improving throughput when large volumes of WIP transactions must be converted into accounting events.
  • BLUEPRINT_SLA_HOOK_WRAP — Acts as the Subledger Accounting blueprint hook wrapper, enabling the application of SLA blueprint customizations and accounting rules during event generation.
  • STANDARD_POLICY — Determines the accounting policy applicable under standard costing conditions.
  • MO_POLICY — Determines the accounting policy applicable to manufacturing order contexts.
  • INV_ORG_POLICY — Determines the accounting policy based on inventory organization parameters.

Tables Accessed

Table access is broad and spans inventory, receiving, WIP, and XLA interface schema. Transaction sources include MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_ACCOUNTS, CST_COGS_EVENTS, RCV_TRANSACTIONS, RCV_ACCOUNTING_EVENTS, WIP_TRANSACTIONS, WIP_TRANSACTION_ACCOUNTS, and WIP_COST_TXN_INTERFACE. The package reads setup and context from MTL_PARAMETERS, PJM_ORG_PARAMETERS, FND_PROFILE, and FND_GLOBAL, and manages batch processing information through FND_CONCURRENT_REQUESTS. Event mapping to XLA event types is resolved through CST_XLA_INV_EVENT_MAP, CST_XLA_RCV_EVENT_MAP, and CST_XLA_WIP_EVENT_MAP. Events and their supporting structures are then populated into numerous XLA global temporary tables, including XLA_EVENTS_GT, XLA_AE_HEADERS_GT, XLA_AE_LINES_GT, XLA_TRANSACTION_ACCTS_GT, XLA_ACCT_PROG_DOCS_GT, and related validation and balance tables, before being handed to the XLA accounting programs. Customer-specific accounting logic may be injected through the CST_PRJMFG_ACCT_HOOK and CST_ACCT_INFO_V objects, which the package also references.

Usage Notes

CST_XLA_PVT is not a user-facing API and is not designed for direct invocation from forms or custom code. It is normally called by the Cost Management Create Accounting program and related concurrent processes that drive subledger accounting for inventory, receiving, and WIP in EBS 12.1.1 and 12.2.2. The package name appears in the "show dependent code" metadata of many XLA objects, and it is referenced by fifteen other packages, confirming its role as a shared internal service. Because some procedures support bulk mode, it is suited to high-volume period-end accounting runs. Technical consultants and developers typically encounter CST_XLA_PVT when diagnosing subledger accounting failures, tracing how cost transactions become XLA events, or reviewing affected objects prior to patching. Any extension of its behavior should be pursued through supported Subledger Accounting customization mechanisms rather than by modifying the package body itself.