Results for “res_seq_num”

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

Overview

The view CST_XLA_WIP_OP_RESOURCE_REF_V is an APPS-owned database view within the Oracle E-Business Suite (EBS) environment, specifically delivered under the BOM – Bills of Material product module. Its primary function is to serve as a reference and reporting mechanism for Work in Process (WIP) operation resource data, particularly in the context of the Subledger Accounting (XLA) architecture and Cost Management (CST) integration. The name itself indicates it is a Costing (CST) object related to XLA and WIP operation resources. The view presents a denormalized and renamed subset of columns from the base WIP_OPERATION_RESOURCES table, providing an interface that is semantically aligned with the data structures expected by the XLA accounting engine. In the context of Oracle EBS 12.1.1 and 12.2.2, this view acts as a critical bridge, allowing accounting processes to retrieve the necessary resource sequencing and identification information required to create and validate accounting entries for WIP transactions. It abstracts the underlying complexity of the base table, ensuring that the XLA schema can consistently reference operation resource data using a standard naming convention.

Underlying Base Objects

The view is defined over a single base object: the WIP_OPERATION_RESOURCES table, accessed via a synonym in the APPS schema. The WIP_OPERATION_RESOURCES table is a core WIP table that stores the resources assigned to operations within a work order or repetitive schedule. The view does not perform any joins or aggregations; instead, it is a straightforward projection that renames columns for compatibility with the Subledger Accounting data model. Specifically, the view aliases columns such as RESOURCE_SEQ_NUM to RES_SEQ_NUM, OPERATION_SEQ_NUM to OP_RES_OP_SEQ_NUM, WIP_ENTITY_ID to OP_RES_WIP_ENTITY_ID, and REPETITIVE_SCHEDULE_ID to OP_RES_REP_SCHED_ID. It also decodes the PHANTOM_FLAG into a more readable 'Y'/'N' value, stored as RES_PHANTOM_FLAG. The inclusion of the ATTRIBUTE_CATEGORY and fifteen ATTRIBUTE columns (all prefixed with OP_RES_ATTRIBUTE) indicates that the view exposes the full set of descriptive flexfield (DFF) attributes associated with the operation resource. This structure is typical of XLA reference views, which are designed to provide a stable, version-independent interface to transactional data.

Key Columns

The view exposes a total of 24 columns, each serving a specific role in the accounting reference context:

• RES_SEQ_NUM: The resource sequence number. This is the column returned when a user searches for "res_seq_num". It uniquely identifies a resource assignment within an operation. The view maps this from the base column RESOURCE_SEQ_NUM.
• OP_RES_OP_SEQ_NUM: The operation sequence number (renamed from OPERATION_SEQ_NUM), identifying the operation to which the resource belongs.
• OP_RES_WIP_ENTITY_ID: The Work in Process entity identifier, linking the resource to a specific work order.
• OP_RES_REP_SCHED_ID: The repetitive schedule identifier, used when the resource is part of a repetitive manufacturing schedule.
• RES_SCHEDULE_TYPE: Derived from SCHEDULED_FLAG, this indicates the scheduling type of the resource.
• RES_PHANTOM_FLAG: A decoded flag ('Y' or 'N') derived from PHANTOM_FLAG, indicating if the resource is associated with a phantom operation.
• RES_PHANTOM_OP_SEQ_NUM: The phantom operation sequence number.
• RES_PHANTOM_ITEM_ID: The phantom item identifier.
• OP_RES_ATTRIBUTE_CATEGORY and OP_RES_ATTRIBUTE1 through 15: The descriptive flexfield context and attribute columns, allowing additional user-defined information to be captured and referenced by accounting rules.

Common Use Cases and Queries

This view is typically used by Oracle Subledger Accounting (SLA) and Cost Management processes to obtain resource-level details for WIP accounting events. For example, when creating accounting entries for resource transactions, the SLA engine may query this view to get the resource sequence and attributes. A common query to retrieve resource information for a specific work order might look like this:

SELECT res_seq_num,
       op_res_op_seq_num,
       op_res_wip_entity_id,
       res_phantom_flag,
       op_res_attribute1
FROM   apps.cst_xla_wip_op_resource_ref_v
WHERE  op_res_wip_entity_id = &wip_entity_id
ORDER BY op_res_op_seq_num, res_seq_num;

Another scenario involves using the view to report on phantom resources within a repetitive schedule:

SELECT res_seq_num,
       op_res_rep_sched_id,
       res_phantom_flag
FROM   apps.cst_xla_wip_op_resource_ref_v
WHERE  op_res_rep_sched_id = &schedule_id
AND    res_phantom_flag = 'Y';

In custom integrations or extensions, this view provides a reliable, documented interface to WIP operation resource data without directly accessing the WIP_OPERATION_RESOURCES table, thereby reducing the risk of breakage during upgrades. It is particularly valuable in versions 12.1.1 and 12.2.2 where the XLA architecture relies on such reference views for data extraction and transformation.