Results for “source_code”

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

Overview

WIPBV_JOB_CLOSE_VARIANCE_TXNS is a read-only Oracle EBS view owned by the APPS schema in the Work in Process (WIP) product. It exposes the population of WIP transaction records that represent job close variance transactions — the accounting events generated when a discrete job is closed and any residual balance remaining on the job is written off to variance accounts. In Oracle EBS 12.1.1 and 12.2.2 the view serves as a reporting and integration convenience layer, isolating a single transaction type from the much larger WIP_TRANSACTIONS table and joining the corresponding lookup meaning so that the transaction type is presented in a human-readable form.

The view text includes the WITH READ ONLY clause, confirming that it cannot be used for DML. It also embeds a row-level security predicate, '_SEC:TR.ORGANIZATION_ID' IS NOT NULL, which is resolved at runtime by the EBS security framework so that users only see transactions belonging to organizations they are authorized to access. This makes the view suitable for multi-org aware reporting without additional filtering logic being written by the developer.

Underlying Base Objects

Two objects are referenced in the view definition:

• WIP_TRANSACTIONS — accessed through an APPS synonym. This is the core WIP transaction table in which every material, resource, and completion transaction against a discrete job is recorded. The view filters this table on TRANSACTION_TYPE = 6, the internal code for the job close variance transaction type.
• MFG_LOOKUPS — the manufacturing lookups view. The view joins on LOOKUP_TYPE = 'WIP_TRANSACTION_TYPE' and LOOKUP_CODE = TR.TRANSACTION_TYPE to retrieve the MEANING for the transaction type code.

Because the driving table is WIP_TRANSACTIONS and the join to MFG_LOOKUPS is a lookup-code equality, the view is effectively a filtered, denormalized projection of WIP_TRANSACTIONS restricted to job close variance rows. No aggregation is performed; one row in the view corresponds to one transaction row in WIP_TRANSACTIONS.

Key Columns

• TRANSACTION_ID — primary identifier for the WIP transaction.
• MEANING — the lookup meaning for transaction type 6 (for example, "Job Close Variance"), sourced from MFG_LOOKUPS.
• TRANSACTION_DATE — the date on which the variance transaction was created.
• SOURCE_CODE — identifies the source system or process that generated the transaction.
• REFERENCE — the free-text reference associated with the transaction.
• ORGANIZATION_ID — the inventory organization in which the transaction occurred; subject to the security predicate.
• WIP_ENTITY_ID — the discrete job (WIP entity) against which the variance was recognized. This is the join key back to WIP_ENTITIES for job and assembly context.
• ACCT_PERIOD_ID — the accounting period to which the transaction was assigned, used for period-based reporting and cost accounting reconciliations.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — the standard WHO columns, which also allow audit-style tracking of when the transaction record was created or last changed.

Although the metadata lists additional columns such as TRANSACTION_TYPE, DESCRIPTION, MFG_ORDER_ID, and the date/WHO columns under their display names, the SELECT list in the view text maps the meaningful operational columns to TRANSACTION_DATE, SOURCE_CODE, REFERENCE, ORGANIZATION_ID, WIP_ENTITY_ID, and ACCT_PERIOD_ID.

Common Use Cases and Queries

Typical uses include period-close reporting of job close variances, reconciliation of WIP variance account balances back to source transactions, and extraction of variance events into a data warehouse.

Variances by organization and accounting period:

• Query: SELECT organization_id, acct_period_id, COUNT(*) txn_count, MIN(transaction_date), MAX(transaction_date) FROM apps.wipbv_job_close_variance_txns GROUP BY organization_id, acct_period_id ORDER BY acct_period_id;

Variances for a specific job:

• Query: SELECT transaction_id, transaction_date, source_code, reference, acct_period_id FROM apps.wipbv_job_close_variance_txns WHERE wip_entity_id = :job_id ORDER BY transaction_date;

Detail joined to job context:

• Query: SELECT v.transaction_id, e.wip_entity_name, v.transaction_date, v.meaning, v.acct_period_id FROM apps.wipbv_job_close_variance_txns v, apps.wip_entities e WHERE v.wip_entity_id = e.wip_entity_id AND v.organization_id = :org_id;

Because the view is read-only and enforces organization security through the embedded _SEC predicate, it can be queried directly in reports and concurrent programs in both 12.1.1 and 12.2.2 without risk of data modification, though performance benefits from an index on WIP_TRANSACTIONS (TRANSACTION_TYPE, ORGANIZATION_ID) or (WIP_ENTITY_ID).