Results for “wip_cost_txn_interface_v”

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

Overview

APPS.WIP_COST_TXN_INTERFACE_V is a foreign-key resolution view published by Oracle Work in Process (WIP). It presents the rows of the WIP cost transaction interface table enriched with the descriptive attributes that the base table stores only as numeric identifiers. In a standard Oracle E-Business Suite 12.1.1 or 12.2.2 environment the view is registered as VALID in the APPS schema and is used wherever a cost transaction must be displayed or verified with human-readable context rather than raw IDs and codes.

The view is a reporting and integration aid rather than a transactional object. It does not itself stage or post cost transactions; the underlying interface table performs that function. The view's contribution is to translate lookup codes, organization identifiers, resource and department identifiers, and entity references into their meanings and names, so that diagnostics, reconciliations, and outbound extracts can be produced without repeated joins. Because it exposes the interface columns plus derived meanings, it is commonly the object of choice for Oracle Discoverer workbooks, BI Publisher data templates, and ad hoc SQL during cost manager troubleshooting.

The view also exposes an ORGANIZATION_NAME, an ORGANIZATION_CODE, and a set of *_MEANING columns derived from MFG_LOOKUPS. The keywords relevant to the requesting user, receiving_account_id, relate to the cost accounting interface columns concerning receiving and valuation accounts. The view's documented reference list includes WIP_COST_TXN_INTERFACE, BOM_RESOURCES, HR_ALL_ORGANIZATION_UNITS, MFG_LOOKUPS, PA_PROJECTS_ALL, PA_TASKS, PO_HEADERS_ALL, WIP_ENTITIES, and WIP_OPERATION_RESOURCES, reflecting the foreign-key relationships that the view resolves.

Underlying Base Objects

The principal base object is the interface table WIP_COST_TXN_INTERFACE, aliased WCTI in the view text. Every column prefixed with WCTI. originates there, including TRANSACTION_ID, SOURCE_CODE, SOURCE_LINE_ID, PROCESS_PHASE, PROCESS_STATUS, TRANSACTION_TYPE, ORGANIZATION_ID, WIP_ENTITY_ID, LINE_ID, PRIMARY_ITEM_ID, REPETITIVE_SCHEDULE_ID, ACCT_PERIOD_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_ID, DEPARTMENT_ID, EMPLOYEE_ID, and the resource rate, quantity, UOM, and currency columns.

The lookup meanings PROCESS_PHASE_MEANING, PROCESS_STATUS_MEANING, TRANSACTION_TYPE_MEANING, RESOURCE_TYPE_MEANING, BASIS_TYPE_MEANING, AUTOCHARGE_TYPE_MEANING, and STANDARD_RATE_FLAG_MEANING are resolved from the MFG_LOOKUPS view. Organization names come from HR_ALL_ORGANIZATION_UNITS, and WIP entity names from WIP_ENTITIES. Resource-level defaults used in the NEW_RES_ADDED decode are drawn from WIP_OPERATION_RESOURCES, while the functional currency flag is obtained from BOM_RESOURCES. Project and task references, and purchasing header references, are represented by PA_PROJECTS_ALL and PA_TASKS and PO_HEADERS_ALL respectively, which support the foreign-key resolution for project and receiving-related identifiers.

Key Columns

The view reproduces the interface table's primary and audit columns, including ROW_ID, TRANSACTION_ID, GROUP_ID, REQUEST_ID, and the standard WHO columns. The following columns carry the greatest reporting value:

• TRANSACTION_TYPE and TRANSACTION_TYPE_MEANING — the cost transaction category and its decoded description.
• PROCESS_PHASE, PROCESS_STATUS, and their meanings — the lifecycle position of the interface row.
• ORGANIZATION_ID, ORGANIZATION_CODE, ORGANIZATION_NAME — the manufacturing organization in raw and descriptive form.
• WIP_ENTITY_ID, WIP_ENTITY_NAME, ENTITY_TYPE, LINE_ID, LINE_CODE — the work order or repetitive schedule context.
• RESOURCE_ID, RESOURCE_CODE, RESOURCE_TYPE, RESOURCE_TYPE_MEANING, DEPARTMENT_ID, DEPARTMENT_CODE — the resource and department charged.
• TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY, PRIMARY_UOM, and the rate and currency columns — the monetary and quantity basis of the transaction.
• NEW_RES_ADDED — a decoded flag computed from WIP_OPERATION_RESOURCES indicating whether the resource was added on the fly.

Common Use Cases and Queries

Typical scenarios include reconciling pending cost transactions by process status, investigating rows that failed to post, and extracting interface data for external costing or analytical applications. The following query lists transactions for a given organization with resolved meanings:

• SELECT transaction_id, transaction_type_meaning, process_status_meaning, wip_entity_name, resource_code, transaction_quantity, actual_resource_rate FROM apps.wip_cost_txn_interface_v WHERE organization_code = :org AND process_status <> 7 ORDER BY transaction_id;
• SELECT transaction_id, source_code, error_code, error_explanation FROM apps.wip_cost_txn_interface_v WHERE process_status = 3 AND creation_date >= SYSDATE - 30;
• SELECT organization_code, transaction_type_meaning, COUNT(*) FROM apps.wip_cost_txn_interface_v GROUP BY organization_code, transaction_type_meaning;

For receiving-related research, joining the view to PO_HEADERS_ALL on the purchasing header identifier embedded in the interface row allows a cost transaction to be traced back to its source receipt, and account identifiers such as receiving_account_id can be validated against the purchasing and receiving accounting distributions before the cost manager processes the group.