Results for “inventory”

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

Overview

The APPS.PO_WF_PO_CHARGE_ACC package is a PL/SQL workflow utility that supports the Oracle Purchasing approval and document management flow in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to determine and validate the charge account that will be applied to a purchasing document line or distribution during workflow processing. Depending on the destination type of the transaction, the package builds the appropriate charge account for expense, inventory, or shop floor (WIP) destinations, and validates that the resulting accounting flexfield combination is valid before the workflow proceeds.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user and relies on APPS synonyms to access the underlying tables. The header comment (POXWPCAS.pls, 120.4) and the original authorship note (Imran Ali, 1997) confirm this is a long-standing, core Purchasing component that has been maintained across multiple EBS releases.

Key Procedures and Functions

The package exposes 18 documented procedures and functions. The central routines include:

• CHECK_DESTINATION_TYPE — Reads the workflow item attribute destination_type_code to determine the destination and returns one of EXPENSE, INVENTORY, or SHOP_FLOOR.
• INVENTORY — Builds the inventory charge account and returns SUCCESS or FAILURE based on whether account generation completes.
• EXPENSE — Builds the expense charge account, likewise returning SUCCESS or FAILURE.
• CHECK_TYPE_OF_WIP, JOB_WIP, SCHEDULE — Support shop floor destinations, distinguishing discrete job versus repetitive schedule WIP and generating the corresponding charge account.
• IS_PO_PROJECT_RELATED, IS_ENCUMBRANCE_ON — Determine whether the purchase order is project-related and whether encumbrance accounting is enabled, influencing account derivation logic.
• IS_DEST_ACCOUNTS_FLOW_TYPE, IS_SPS_DISTRIBUTION, GET_SPS_CHARGE_ACCOUNT, IS_DEST_CHARGE_ACC_NULL — Evaluate distribution and destination account flow characteristics, including special handling for SPS (Supplier-Part-Site) distributions.
• ARE_COAS_SAME, SET_NULL_RESP_ID, RESET_RESP_ID — Compare charts of accounts and temporarily manage the responsibility context during account validation.
• VALIDATE_COMBINATION — Confirms the generated accounting flexfield combination is valid against GL_CODE_COMBINATIONS.
• DEBUG_ON, DEBUG_OFF — Toggle diagnostic output for troubleshooting.

Tables Accessed

The package references the following tables through APPS synonyms:

• FINANCIALS_SYSTEM_PARAMETERS, FINANCIALS_SYSTEM_PARAMS_ALL — Supply ledger and accounting configuration such as encumbrance settings and default accounts.
• FND_RESPONSIBILITY — Used when setting or resetting the responsibility context for account validation.
• GL_CODE_COMBINATIONS — Validates the derived accounting flexfield combination.
• MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS — Provide inventory organization, subinventory, and item attributes required to build inventory and WIP charge accounts.
• PO_SYSTEM_PARAMETERS — Supplies Purchasing configuration affecting account derivation.
• RCV_PARAMETERS — Provides receiving parameters used in destination logic.
• WF_ITEM_ACTIVITY_STATUSES — Reads workflow activity state and item attributes such as destination type.
• WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES — Supply WIP job and schedule information for shop floor charge accounts.

Usage Notes

PO_WF_PO_CHARGE_ACC is invoked as part of the Oracle Purchasing workflow, specifically during activities that require a charge account to be derived and validated before an order can be approved or processed. The procedures are designed to be called as workflow function activities, receiving itemtype, itemkey, actid, and funcmode parameters and returning a result value such as EXPENSE, INVENTORY, SHOP_FLOOR, SUCCESS, or FAILURE. Two other packages reference this package, indicating it is a shared dependency within the Purchasing workflow framework. Customizations that modify charge account derivation should account for the package's reliance on item attributes and system parameters, and the DEBUG_ON/DEBUG_OFF routines are useful when diagnosing account generation failures.