Search Results batchstep_resource_id

Overview

GMF_XLA_BATCH_RSRC_V is a Subledger Accounting (SLA) reporting view owned by the APPS schema in Oracle E-Business Suite, and shipped as part of the GMF – Process Manufacturing Financials product family. It is a denormalized projection that consolidates batch execution data with the recipe, routing, formula, and resource master definitions that govern a batch. Its primary purpose is to supply the resource-level context that Oracle Subledger Accounting requires when generating accounting events and journal entries for process manufacturing batch transactions.

The view is not a transactional table. It provides a read-only, join-enriched representation of batch step resources, allowing SLA event models, cost analysis reports, and downstream integrations to resolve the resource, recipe, routing, and formula attributes associated with a given batch resource line without traversing the underlying normalization themselves.

Underlying Base Objects

The view is defined over the following synonyms, each resolving to a base table in the Process Manufacturing schema:

• GME_BATCH_HEADER — the driving batch header, supplying BATCH_ID, BATCH_NO, BATCH_STATUS, and the foreign keys to recipe validity rules, routing, formula, and organization.
• GME_BATCH_STEP_RESOURCES — the batch step resource lines; BSR.BATCHSTEP_RESOURCE_ID is the unique resource line identifier and the column most frequently searched for.
• CR_RSRC_MST — the resource master, providing RESOURCES, RESOURCE_DESC, and RESOURCE_CLASS.
• GMD_RECIPES_B — the recipe header, providing RECIPE_ID, RECIPE_NO, and RECIPE_VERSION.
• GMD_RECIPE_VALIDITY_RULES — joined with the outer (+) operator to resolve the recipe validity rule governing the batch.
• GMD_ROUTINGS_B — the routing header, providing ROUTING_NO, ROUTING_VERS, and ROUTING_CLASS; also outer-joined.
• FM_FORM_MST_B — the formula master, supplying FORMULA_ID, FORMULA_NO, and FORMULA_VERS.

The join between GME_BATCH_HEADER and GME_BATCH_STEP_RESOURCES is on both BATCH_ID and ORGANIZATION_ID, and the resource line is further joined to CR_RSRC_MST on the RESOURCES code.

Key Columns

• BATCH_ID / BATCH_NO / BATCH_STATUS — batch identity and current status.
• BATCHSTEP_RESOURCE_ID — the surrogate key of the batch step resource record; the primary lookup column for callers tracing a specific resource consumption or charge line back to its batch.
• RESOURCES / RESOURCE_DESC / RESOURCE_CLASS — resource code, description, and the resource class used for cost rollup and accounting classification.
• RECIPE_ID / RECIPE_NO / RECIPE_VERSION — the recipe controlling the batch.
• ROUTING_ID / ROUTING_NO / ROUTING_VERS / ROUTING_CLASS — routing definition associated with the batch.
• FORMULA_ID / FORMULA_NO / FORMULA_VERS — formula master reference.

Common Use Cases and Queries

Typical usage includes SLA event diagnostics, batch cost and resource utilization reporting, and reconciliation of batch step resources against recipe and routing definitions. To resolve a specific resource line:

• SELECT batch_no, batchstep_resource_id, resources, resource_desc, resource_class FROM apps.gmf_xla_batch_rsrc_v WHERE batchstep_resource_id = :p_id;
• SELECT batch_no, batchstep_resource_id, resources, resource_desc FROM apps.gmf_xla_batch_rsrc_v WHERE batch_id = :p_batch_id ORDER BY batchstep_resource_id;
• SELECT batch_no, resources, resource_class, recipe_no, routing_no, formula_no FROM apps.gmf_xla_batch_rsrc_v WHERE resource_class = :p_class AND batch_status < 4;

Because the view is READ ONLY and VALID, it is safe for ad-hoc queries and reporting extracts, but it must never be used as a DML target. Queries should constrain on BATCH_ID, BATCHSTEP_RESOURCE_ID, or ORGANIZATION_ID to avoid full scans across the batch history.