Search Results standard_policy

Overview

CST_XLA_PVT is the private helper package within the Oracle E-Business Suite Cost Management (CST) module that bridges inventory, receiving, and Work in Process (WIP) transaction data to the Subledger Accounting (SLA / XLA) engine. Its central business function is the creation of accounting events—termed SLA events—for the various cost-bearing transactions that originate in Oracle Inventory, Oracle Purchasing receiving, and Oracle Work in Process. Because these events feed the Create Accounting process, CST_XLA_PVT is a foundational component of the accounting lifecycle for supply chain transactions.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the calling schema rather than its owner. This design supports Oracle's convention of keeping private (PVT) packages callable from within the EBS application stack while respecting security context. The package defines several PL/SQL record and collection types—t_cst_inv_event_info, t_xla_inv_trx_info, t_xla_rcv_trx_info, and t_xla_wip_trx_info—which serve as structured containers for the transaction attributes required to generate an SLA event, such as transaction date, transaction type, organization, ledger, and encumbrance flags.

The package is referenced by 15 other packages within the EBS codebase, confirming its role as a shared internal utility rather than a standalone API.

Key Procedures and Functions

The documented program units (10 total) fall into two functional groups:

• STANDARD_POLICY, MO_POLICY, INV_ORG_POLICY — Policy routines that determine accounting treatment based on organizational or transaction classification context. These are the routines most closely associated with the user's search term "standard_policy." STANDARD_POLICY applies the standard accounting policy for a given transaction, while MO_POLICY and INV_ORG_POLICY apply Manufacturing Organization and Inventory Organization-specific variations, respectively. Together they resolve which accounting policy governs a transaction before event creation proceeds.
• CREATE_RCVXLAEVENT, CREATE_INVXLAEVENT, CREATE_WIPXLAEVENT — Routines that construct SLA events for receiving, inventory, and WIP transactions respectively. These are the core builders that translate transaction data into the SLA event structure.
• CREATEBULK_WIPXLAEVENT — A bulk-processing variant of WIP SLA event creation, used to process multiple WIP transactions in a single invocation for performance.
• CREATE_COSTUPDATEXLAEVENT, CREATE_WIPUPDATEXLAEVENT — Routines that generate SLA events for cost update transactions and WIP cost update transactions, ensuring that revaluation and cost adjustment activity is captured by Subledger Accounting.
• BLUEPRINT_SLA_HOOK_WRAP — A wrapper for the blueprint SLA hook, exposing hook logic used during event generation.

Tables Accessed

Via APPS synonyms, the package reads and writes the following documented tables:

• Transaction source tables: MTL_MATERIAL_TRANSACTIONS, MTL_TRANSACTION_ACCOUNTS, RCV_TRANSACTIONS, RCV_ACCOUNTING_EVENTS, WIP_TRANSACTIONS, WIP_TRANSACTION_ACCOUNTS, and WIP_COST_TXN_INTERFACE supply the underlying transaction data and account references.
• Event mapping tables: CST_XLA_INV_EVENT_MAP, CST_XLA_RCV_EVENT_MAP, and CST_XLA_WIP_EVENT_MAP associate source transactions with the correct SLA event definitions and event types.
• Cost and organizational parameters: CST_COGS_EVENTS, MTL_PARAMETERS, and PJM_ORG_PARAMETERS supply organizational and costing context, including policy-relevant attributes.
• Infrastructure tables: FND_CONCURRENT_REQUESTS and XLA_ACCT_PROG_DOCS_GT support concurrent processing and the global temporary staging of accounting program documents.

Usage Notes

CST_XLA_PVT is a private package (classification PVT) and is not intended for direct invocation by end users. It is called internally by cost management and subledger accounting processes, most notably during the Create Accounting and Transfer Transactions to SLA concurrent programs. The standard cost processor and receiving accounting workflows invoke the CREATE_*XLAEVENT routines to register events, with the policy routines (STANDARD_POLICY and its organization-specific peers) resolving accounting treatment beforehand. Custom or extension code in Oracle EBS 12.1.1 and 12.2.2 should not call the package's internal routines directly; instead, integration should occur through the supported SLA and Cost Management APIs. The CUSTOMER-based cost update programs and WIP costing processes rely on CREATE_COSTUPDATEXLAEVENT and CREATE_WIPUPDATEXLAEVENT to ensure cost adjustments reach the subledger.