Search Results pjm_task_wip_acct_classes

Overview

The WIP_ACCOUNTING_CLASSES table is a core master data table within the Oracle E-Business Suite Work in Process (WIP) module. It serves as the central repository for defining and storing accounting class definitions, which are fundamental to the cost accounting and financial transaction processing for manufacturing work orders. Each accounting class acts as a template, mapping specific cost elements of a production job—such as material, resource, and overhead—to their corresponding general ledger (GL) accounts. This linkage ensures that all manufacturing costs and variances are posted to the correct financial accounts, enabling accurate inventory valuation, cost of goods sold calculation, and financial reporting. Its role is critical for both discrete and, in certain configurations, repetitive manufacturing.

Key Information Stored

The table's primary key is a composite of CLASS_CODE and ORGANIZATION_ID, enforcing uniqueness of class definitions per manufacturing organization. The most significant columns are the foreign keys to the GL_CODE_COMBINATIONS table, which define the specific general ledger accounts for each cost component. These include MATERIAL_ACCOUNT, RESOURCE_ACCOUNT, OVERHEAD_ACCOUNT, and OUTSIDE_PROCESSING_ACCOUNT for charging costs, and their corresponding variance accounts (e.g., MATERIAL_VARIANCE_ACCOUNT, RESOURCE_VARIANCE_ACCOUNT) for capturing deviations from standards. Additional columns may include descriptive attributes and control flags that define the class's behavior and usage within the WIP module.

Common Use Cases and Queries

A primary use case is the setup and maintenance of cost accounting structures during implementation. Analysts query this table to audit or report on the GL account mappings for all accounting classes in an organization. A common reporting requirement is to list all accounts associated with a specific class or to identify classes using a particular GL account segment value. Sample SQL to retrieve the full account mapping for a class is:

• SELECT wac.class_code, wac.material_account, wac.resource_account, wac.overhead_account FROM wip_accounting_classes wac WHERE wac.organization_id = :p_org_id AND wac.class_code = :p_class_code;

Another critical use case is troubleshooting job cost transactions; support personnel often join this table to WIP_DISCRETE_JOBS to verify the accounts used by a specific work order.

Related Objects

The table maintains extensive relationships with other EBS objects, primarily through foreign key constraints. The WIP_DISCRETE_JOBS table references it via CLASS_CODE and ORGANIZATION_ID, assigning an accounting class to each discrete job. It is referenced by WIP_PARAMETERS at the organization level. Crucially, numerous foreign keys link its account columns (e.g., MATERIAL_ACCOUNT, OVERHEAD_VARIANCE_ACCOUNT) to GL_CODE_COMBINATIONS.CODE_COMBINATION_ID. Furthermore, it integrates with other modules, as evidenced by references from AHL_ROUTES_B (Service), PJM_PROJECT_PARAMETERS (Project Manufacturing), and PJM_TASK_WIP_ACCT_CLASSES, highlighting its role in cross-module financial consistency.