Results for “wipbv_accounting_classes”

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

Overview

The WIPBV_ACCOUNTING_CLASSES view is a read-only, business-facing reporting object owned by the APPS schema in Oracle E-Business Suite. It is shipped with the Work in Process (WIP) module and exposes the accounting class definitions configured per organization, together with resolved lookup meanings and the flexfield account identifiers that drive cost accounting for discrete and repetitive manufacturing transactions.

In Oracle EBS 12.1.1 and 12.2.2, the view functions as a denormalized presentation layer over WIP_ACCOUNTING_CLASSES. It joins lookup tables and organization tables so that reports, concurrent programs, and integration interfaces can present accounting class data with human-readable descriptions rather than raw lookup codes. Because the view is defined with WITH READ ONLY, it is intended strictly for query and reporting; all maintenance is performed against the base table through the WIP Accounting Classes form.

The view is particularly relevant to the search term completion_cost_source, since it resolves that column through a lookup join, exposing its decoded meaning directly to consumers.

Underlying Base Objects

The view is defined over four documented base objects, combined with outer joins to three lookup aliases derived from MFG_LOOKUPS:

• WIP_ACCOUNTING_CLASSES (synonym) — the primary table supplying accounting class attributes, class codes, account flexfield IDs, cost type, and WHO audit columns.
• MTL_PARAMETERS (synonym) — joined on ORGANIZATION_ID to supply ORGANIZATION_CODE.
• HR_ALL_ORGANIZATION_UNITS (synonym) — joined on ORGANIZATION_ID to supply the organization name (AL.NAME).
• MFG_LOOKUPS (view) — referenced three times, once for each lookup type: WIP_CLASS_TYPE, CST_COMPLETION_COST_SRC, and CST_SYSTEM_COMPLETION_OPTIONS.

The inner join on MTL_PARAMETERS, combined with the predicate '_SEC:AC.ORGANIZATION_ID' IS NOT NULL, enforces organization-level security so that only organizations accessible to the querying responsibility are returned. The lookup joins are outer joins, so an accounting class with no matching lookup code still appears, with a null meaning.

Key Columns

• CLASS_CODE / ORGANIZATION_ID — the composite key identifying an accounting class within an organization.
• CLASS_TYPE — decoded through WIP_CLASS_TYPE (for example, standard, average, or the various completion classes).
• COMPLETION_COST_SOURCE — the costing source used when completing assemblies; its meaning is resolved via the CST_COMPLETION_COST_SRC lookup (LO2.MEANING).
• SYSTEM_OPTION_ID — decoded through CST_SYSTEM_COMPLETION_OPTIONS (LO3.MEANING).
• ORGANIZATION_CODE / ORGANIZATION_NAME — human-readable organization identifiers.
• Account flexfield columns — MATERIAL_ACCOUNT, MATERIAL_VARIANCE_ACCOUNT, MATERIAL_OVERHEAD_ACCOUNT, RESOURCE_ACCOUNT, RESOURCE_VARIANCE_ACCOUNT, OUTSIDE_PROCESSING_ACCOUNT, OUTSIDE_PROC_VARIANCE_ACCOUNT, OVERHEAD_ACCOUNT, OVERHEAD_VARIANCE_ACCOUNT, STD_COST_ADJUSTMENT_ACCOUNT, BRIDGING_ACCOUNT, and EXPENSE_ACCOUNT.
• COST_TYPE_ID and WHO columns — cost type reference and standard audit fields.

Common Use Cases and Queries

Typical uses include validating cost accounting configuration before go-live, auditing which completion cost source is assigned across organizations, and feeding account mappings into interfaces or reconciliation reports.

The following query lists accounting classes and their decoded completion cost source for a given organization:

SELECT class_code, organization_code, class_type, completion_cost_source
FROM apps.wipbv_accounting_classes
WHERE organization_id = :org_id
ORDER BY class_code;

To identify classes configured with a specific completion cost source, filter on the meaning supplied by the lookup join:

SELECT organization_code, class_code, completion_cost_source
FROM apps.wipbv_accounting_classes
WHERE completion_cost_source = 'CURRENT';

Because the view is read-only, it is safe to consume directly in custom reports, BI Publisher data templates, and integration extracts without risk of inadvertent DML against the underlying configuration.