Results for “cst_pac_wip_txn_v”

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

Overview

CST_PAC_WIP_TXN_V is an APPS-owned reporting view that consolidates Work in Process (WIP) transaction activity for cost management, cost accounting, and period-close reporting within Oracle EBS 12.1.1 and 12.2.2. The view joins the WIP_TRANSACTIONS table to a wide set of descriptive reference objects, resolving surrogate identifiers into human-readable values such as organization code, WIP entity name, department code, resource code, transaction type meaning, activity name, reason name, project number, and task number. It therefore serves as a denormalized, presentation-layer source for operational and financial reporting rather than as a transaction entry object.

Because it exposes both the actual and standard resource rates alongside the standard rate flag and the usage rate or amount, the view is a frequent discovery target for users searching for the standard_resource_rate column. In the documented projection, this appears as STANDARD_RESOURCE_RATE, with ACTUAL_RESOURCE_RATE and CURRENCY_ACTUAL_RESOURCE_RATE provided for comparison. The view is defined with STATUS VALID and is classified under the BOM - Bills of Material product family, reflecting the shared manufacturing data model that underpins WIP and cost collection.

Underlying Base Objects

The documented view metadata identifies the following referenced objects: BOM_DEPARTMENTS, BOM_RESOURCES, CST_ACTIVITIES, CST_COST_GROUPS, CST_COST_GROUP_ASSIGNMENTS, FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, MFG_LOOKUPS, MRP_GET_PROJECT, MTL_PROJECT_V, MTL_TASK_V, MTL_TRANSACTION_REASONS, ORG_ORGANIZATION_DEFINITIONS, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_SECURITY, PA_TASK_UTILS, PER_PEOPLE_F, PO_HEADERS, WIP_JOB_ASSY_LINE_V, WIP_TRANSACTIONS, and XLE_FIRSTPARTY_INFORMATION_V.

The driving table is WIP_TRANSACTIONS (aliased WT in the view text), which supplies the transaction facts: transaction identifier, type, date, quantity, rates, currency details, and accounting period. Descriptive attributes are joined from CST_COST_GROUPS and CST_COST_GROUP_ASSIGNMENTS (legal entity, cost group, organization), ORG_ORGANIZATION_DEFINITIONS (organization code and name), WIP_JOB_ASSY_LINE_V (WIP entity name and line code), BOM_DEPARTMENTS (department code), BOM_RESOURCES (resource code), CST_ACTIVITIES (activity), MTL_TRANSACTION_REASONS (reason name), PER_PEOPLE_F and HR packages (employee name and number), and PO_HEADERS (PO number). Lookup meanings are resolved through MFG_LOOKUPS multiple times. Project and task context is derived through MTL_PROJECT_V, MTL_TASK_V, and the PA and MRP utility packages, while XLE_FIRSTPARTY_INFORMATION_V supplies the first-party (legal entity) name. Security and profile logic from HR_SECURITY, HR_GENERAL, PA_SECURITY, and FND_PROFILE governs row-level visibility.

Key Columns

• ROW_ID, TRANSACTION_ID, GROUP_ID, LINE_ID — Unique row and transaction identifiers used for drill-down and reconciliation.
• LEGAL_ENTITY, NAME, COST_GROUP_ID, COST_GROUP, ORGANIZATION_ID — Cost organization and cost group context.
• ORGANIZATION_CODE, ORGANIZATION_NAME — Resolved inventory organization descriptors.
• WIP_ENTITY_ID, WIP_ENTITY_NAME, LINE_CODE — Work order/job and assembly line identification.
• DEPARTMENT_ID, DEPARTMENT_CODE, RESOURCE_ID, RESOURCE_CODE — Department and resource context for resource transactions.
• TRANSACTION_TYPE, TRANSACTION_TYPE_MEANING, TRANSACTION_DATE, ACCT_PERIOD_ID — Transaction classification, date, and accounting period.
• STANDARD_RATE_FLAG, STANDARD_RATE_MEANING — Indicates whether the standard rate applies; the meaning is suppressed for transaction type 2.
• USAGE_RATE_OR_AMOUNT, BASIS_TYPE, BASIS_TYPE_MEANING — Rate or amount basis for the resource charge.
• TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY, PRIMARY_UOM — Entered and primary quantities.
• ACTUAL_RESOURCE_RATE, STANDARD_RESOURCE_RATE, CURRENCY_ACTUAL_RESOURCE_RATE — Resource rate comparison columns, the primary target for the standard_resource_rate search.
• CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE — Currency and conversion detail.
• PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER, PO_NUMBER, REASON_NAME — Project, purchasing, and reason references.
• EMPLOYEE_ID, EMPLOYEE_NUM, ACTIVITY_ID, ACTIVITY — Employee and activity attribution.
• ATTRIBUTE1 through ATTRIBUTE15, REQUEST_ID, PROGRAM_ID — Descriptive flexfield and concurrent program audit columns.

Common Use Cases and Queries

Typical uses include resource rate variance analysis, WIP transaction inquiry by department or job, period-close verification of collected resource charges, and reconciliation between actual and standard rates. A representative query retrieving resource rates for a job follows:

SELECT organization_code, wip_entity_name, department_code, resource_code, transaction_date, transaction_quantity, actual_resource_rate, standard_resource_rate, currency_code FROM cst_pac_wip_txn_v WHERE wip_entity_name = :p_wip_entity_name AND transaction_type_meaning = 'Resource' ORDER BY transaction_date, resource_code;

To analyze variance between standard and actual resource rates:

SELECT department_code, resource_code, SUM(transaction_quantity) qty, AVG(actual_resource_rate) avg_actual, AVG(standard_resource_rate) avg_standard FROM cst_pac_wip_txn_v WHERE acct_period_id = :p_period_id GROUP BY department_code, resource_code ORDER BY department_code, resource_code;

Because the view resolves security through HR and PA packages, results are automatically filtered by the responsibility's organization and project access, making it suitable for self-service and cost-accounting reports without additional access logic.