Results for “variance_account”

36 results




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

Overview

APPS.PO_WF_PO_FLEXBUILDER_UPGRADE is a PL/SQL package that supports the Oracle Purchasing Oracle Workflow integration during the transition from the older Account Generator technology to the Key Flexfield (FlexBuilder) framework. Within Oracle E-Business Suite 12.1.1 and 12.2.2, the package is declared with AUTHID CURRENT_USER, meaning its database objects and SQL statements execute under the privileges of the calling user rather than the package owner. The sole responsibility of the package is to generate accounting key flexfield combinations required by a purchasing document — charge, budget, variance, and accrual accounts — so that existing purchasing workflow activity definitions can continue to function after the FlexBuilder upgrade. The four procedures follow the standard Oracle Workflow PL/SQL procedure signature convention, receiving an item type, item key, activity identifier, and function mode, and returning a single result value of SUCCESS or FAILURE.

Key Procedures and Functions

The package exposes four documented procedures, each corresponding to a distinct account generation requirement within the purchasing workflow:

  • CHARGE_ACCOUNT — Generates the charge account for a purchasing document line or distribution. The comment block explicitly states its purpose as generating a charge account for the flex builder upgrade, returning FAILURE if account generation fails and SUCCESS otherwise.
  • BUDGET_ACCOUNT — Generates the budget account associated with the purchasing transaction. It follows the same workflow-callable contract and returns the same SUCCESS/FAILURE result indicators.
  • VARIANCE_ACCOUNT — Generates the variance account used when purchase order and invoice or receipt amounts diverge and a variance posting is required.
  • ACCRUAL_ACCOUNT — Generates the accrual account, the account to which received-not-invoiced and accrued liability amounts are posted during the purchasing period-end and accrual reconciliation cycle. This procedure is the direct object of the user's "accrual_account" search.

The documented ETRM classification for the package is "OTHER," reflecting its role as an internal upgrade utility rather than a public application programming interface.

Tables Accessed

The ETRM metadata records no referenced tables through APPS synonyms for this package. This is consistent with a workflow utility that derives its input values from the Workflow item attributes associated with the item type and item key passed to each procedure, rather than issuing direct SQL against stored purchasing tables. Any key flexfield combination validation occurs through the standard flexfield APIs invoked at run time. Because the metadata documents no table access, the package should be regarded as a lightweight workflow integration layer that delegates persistence to the workflow engine and to the flexfield combination tables managed by the AOL schema.

Usage Notes

PO_WF_PO_FLEXBUILDER_UPGRADE is invoked from Oracle Workflow activity definitions embedded in the purchasing workflow processes. Oracle Workflow calls each procedure with the standard itemtype, itemkey, actid, and funcmode parameters, and interprets the returned result value to determine transition success or failure. It is not intended to be called directly from a client form or a concurrent program; the header indicates creation dates in 1997 with later revisions, distinguishing it as legacy upgrade infrastructure retained for backward compatibility in release 12. The package is referenced by zero other packages according to the documented metadata, so its integration surface is limited to Workflow metadata definitions. When diagnosing account generation problems in purchasing workflows for accrual, charge, budget, or variance accounts, the Workflow administrator should inspect the activity function assignments referencing these procedures and verify that the function mode is RUN and that the returned result is SUCCESS before investigating downstream accounting entries.