Results for “cst_pac_ael_gl_wip_v”

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

Overview

CST_PAC_AEL_GL_WIP_V is an APPS-owned, VALID database view within the Oracle E-Business Suite environment, catalogued under the BOM (Bills of Material) product family. It functions as a specialized reporting and reconciliation view that bridges the Cost Management accounting engine and the Oracle General Ledger for Work-in-Process (WIP) transactions. Specifically, the view consolidates accounting event data generated by subledger costing activities and aligns it with the corresponding General Ledger journal postings.

Its role is central to the "PAC" (Period Average Cost / actual costing) subledger-to-GL reconciliation model. By joining Cost Management accounting headers and lines (CST_AE_HEADERS and CST_AE_LINES) to GL journal headers and lines, the view presents both subledger accounting entries and the resulting GL postings on a single row. This makes it a natural candidate for audit trails, subledger reconciliation reports, and drill-down queries that must map a specific WIP transaction to its journal entry in the general ledger. Because it also surfaces organization, cost group, cost type, resource, and WIP entity context, it supports detailed variance and cost-element analysis.

Underlying Base Objects

The view is defined over a substantial join across the Cost Management, WIP, GL, and reference-data schemas. The documented base objects include:

• Cost Management accounting objects: CST_AE_HEADERS, CST_AE_LINES, CST_COST_ELEMENTS, CST_LE_COST_TYPES, CST_COST_GROUPS, CST_COST_GROUP_ASSIGNMENTS, and CST_COST_TYPES.
• WIP and manufacturing objects: WIP_TRANSACTIONS, WIP_ENTITIES, WIP_LINES, WIP_FLOW_SCHEDULES, BOM_DEPARTMENTS, BOM_RESOURCES, and MTL_TRANSACTION_REASONS.
• General Ledger objects: GL_JE_HEADERS, GL_JE_LINES, GL_IMPORT_REFERENCES, GL_PERIOD_STATUSES, and GL_DAILY_CONVERSION_TYPES.
• Reference and security objects: ORG_ORGANIZATION_DEFINITIONS, MTL_SYSTEM_ITEMS_KFV, PO_HEADERS, MFG_LOOKUPS, HR_GENERAL, and HR_SECURITY.

The view's SELECT list confirms an ordered join anchored on GL_JE_LINES and GL_JE_HEADERS, flowed back through GL_IMPORT_REFERENCES and CST_AE_HEADERS/CST_AE_LINES to the WIP transaction detail. Lookups are resolved through MFG_LOOKUPS (aliased LU1 through LU5), and department, resource, line, and schedule attributes are drawn from the BOM and WIP tables. HR_SECURITY governs organization-level access through ORG_ORGANIZATION_DEFINITIONS.

Key Columns

The view exposes a wide column set that spans accounting, WIP, and GL context. Notable columns include:

• Accounting identity: ACCOUNTING_DATE, SET_OF_BOOKS_ID, LEGAL_ENTITY, COST_TYPE_ID, COST_TYPE, COST_GROUP_ID, COST_GROUP, PRIMARY_COST_METHOD, and COST_ELEMENT_ID/COST_ELEMENT.
• Subledger amounts: CURRENCY_CODE, ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_CONVERSION_RATE.
• GL linkage: GL_SL_LINK_ID, GL_TRANSFER_RUN_ID, JE_HEADER_ID, JE_LINE_NUM, and CODE_COMBINATION_ID.
• WIP transaction context: WIP_ENTITY_ID, WIP_ENTITY_NAME, LINE_ID, LINE_CODE, TRANSACTION_ID, TRANSACTION_TYPE, TRANSACTION_DATE, TRANSACTION_QUANTITY, TRANSACTION_UOM, PRIMARY_QUANTITY, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_CODE, DEPARTMENT_CODE, and SCHEDULE_NUMBER.
• Reference and audit fields: SOURCE_TABLE, SOURCE_ID, DESCRIPTION, REASON_NAME, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

The 706 literal in the second column position and the 'WIP TRX' literal in the transaction-category position are constant descriptors used to identify the source application and transaction class respectively.

Common Use Cases and Queries

Typical usage centers on reconciliation and audit. A common pattern filters by accounting period and organization to compare subledger versus GL balances for WIP resource and overhead transactions.

• Reconciling CST_AE_LINES to GL_JE_LINES by examining rows where GL_SL_LINK_ID is null (unposted) versus populated (posted).
• Drilling from a WIP transaction to its GL journal entry using WIP_ENTITY_ID, TRANSACTION_ID, and JE_HEADER_ID.
• Analyzing WIP cost by resource, department, and cost element for variance reporting.

For example, a reconciliation query could select ORGANIZATION_CODE, ACCOUNTING_DATE, TRANSACTION_TYPE, RESOURCE_CODE, COST_ELEMENT, ACCOUNTED_DR, ACCOUNTED_CR, JE_HEADER_ID, and JE_LINE_NUM from CST_PAC_AEL_GL_WIP_V where ACCOUNTING_DATE between the period start and end dates and SET_OF_BOOKS_ID equals the target ledger. Because the view joins high-volume transaction and journal tables, queries should be constrained by date and organization and supported by the underlying indexes on CST_AE_HEADERS, CST_AE_LINES, and GL_JE_LINES.