Search Results outside_proc_variance_account




Overview
Explore in AI Chat

Overview

AX_WIP_JOBS_V1 is a view belonging to the AX - Global Accounting Engine product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates standard (discrete) and repetitive job information sourced from Work in Process entities together with their associated material transactions. The view is designed to surface the work-in-process entity identifiers, the class code of each job, and the full set of accounting flexfield accounts configured for that entity, including material, resource, overhead, outside processing, and their corresponding variance accounts.

Within the Global Accounting Engine, this view serves as a reporting and integration bridge between WIP transaction activity and the accounting distribution logic. By exposing both the job definition and the transaction identifier in a single row, it allows the accounting engine and downstream reporting tools to correlate a specific material transaction against the job's configured costing accounts. This is particularly relevant for organizations that need to trace how outside processing and variance balances are derived at the job level.

Underlying Base Objects

The view is defined as a UNION of two SELECT statements. The first branch joins WIP_DISCRETE_JOBS (aliased WDJ) to MTL_MATERIAL_TRANSACTIONS (MMT), matching MMT.TRANSACTION_SOURCE_ID to WDJ.WIP_ENTITY_ID. This branch exposes discrete job accounting attributes.

The second branch joins WIP_REPETITIVE_SCHEDULES (WRS), WIP_REPETITIVE_ITEMS (WRI), and MTL_MATERIAL_TRANSACTIONS (MMT). The join conditions require WRI.WIP_ENTITY_ID equal to WRS.WIP_ENTITY_ID, WRI.LINE_ID equal to WRS.LINE_ID, MMT.TRANSACTION_SOURCE_ID equal to WRS.WIP_ENTITY_ID, and MMT.REPETITIVE_LINE_ID equal to WRS.LINE_ID. This branch exposes repetitive schedule accounting attributes while preserving the same column projection as the discrete branch.

Notably, the documented ETRM metadata for release 12.2.2 shows no owner and no documented referenced base objects, and states that the view is "Not implemented in this database." The view text nevertheless references WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, WIP_REPETITIVE_ITEMS, and MTL_MATERIAL_TRANSACTIONS as its underlying physical sources.

Key Columns

Common Use Cases and Queries

The primary use case is auditing and reporting on job-level account assignments, especially for outside processing and its variance account. A representative query retrieves the outside processing variance account for all transactions of a given organization:

SELECT WIP_ENTITY_ID,
       ORGANIZATION_ID,
       CLASS_CODE,
       OUTSIDE_PROCESSING_ACCOUNT,
       OUTSIDE_PROC_VARIANCE_ACCOUNT,
       TRANSACTION_ID
FROM   AX_WIP_JOBS_V1
WHERE  ORGANIZATION_ID = :org_id
ORDER  BY WIP_ENTITY_ID;

Another common scenario joins the view to the accounting distributions for a specific transaction to reconcile the variance account actually posted:

SELECT J.WIP_ENTITY_ID,
       J.OUTSIDE_PROC_VARIANCE_ACCOUNT,
       T.TRANSACTION_ID
FROM   AX_WIP_JOBS_V1 J,
       MTL_MATERIAL_TRANSACTIONS T
WHERE  T.TRANSACTION_ID = J.TRANSACTION_ID
AND    J.CLASS_CODE = :class_code;

Because the view distinguishes discrete and repetitive entities via CLASS_CODE sourced from WIP_DISCRETE_JOBS and WIP_REPETITIVE_ITEMS respectively, it is also used to compare account setups between standard and repetitive manufacturing environments. Given its status as "Not implemented in this database" in the documented environment, availability should be confirmed against the target instance before reliance in production reporting.