Results for “formula_vers”

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

Overview

GMF_XLA_BATCH_HDR_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the GMF – Process Manufacturing Financials product family. It functions as a Subledger Accounting (SLA) batch header view, consolidating batch-level manufacturing attributes with their associated recipe, routing, and formula definitions. The view provides the accounting engine and downstream reporting layers with a single, denormalized row per production batch, resolving the recipe validity rule, recipe header, routing header, and formula master references that would otherwise require multi-table joins. In releases 12.1.1 and 12.2.2 the object is documented as VALID and its metadata is published through ETRM. Because it exposes descriptive identifiers alongside surrogate keys, it is commonly used in reconciliation reports, SLA event diagnostics, and integration extracts where batch context must be presented without navigating the full Process Manufacturing data model. A user searching for "routing_vers" typically arrives here because the view is one of the few supported APPS-level objects that surfaces the routing version alongside batch, recipe, and formula version information in a single query.

Underlying Base Objects

The view is defined over five referenced base objects, all resolved through APPS synonyms in 12.2.2: GME_BATCH_HEADER, GMD_RECIPE_VALIDITY_RULES, GMD_RECIPES_B, GMD_ROUTINGS_B, and FM_FORM_MST_B. GME_BATCH_HEADER is the driving table, supplying batch identity and status. It joins to GMD_RECIPE_VALIDITY_RULES through RECIPE_VALIDITY_RULE_ID using an outer join, and the validity rule then links to the recipe header (GMD_RECIPES_B) via RECIPE_ID. Routing and formula associations are likewise outer joins: BATCH_ID's parent row may or may not carry a ROUTING_ID or FORMULA_ID, so the view preserves batches lacking routing or formula definitions rather than dropping them. This outer-join pattern is significant for reporting, because batches created without an assigned routing still appear with null routing columns. The recipe join is effectively mandatory once a validity rule exists, which reflects the tight coupling between batches and recipes in Process Manufacturing.

Key Columns

• BATCH_ID / BATCH_NO / BATCH_STATUS – surrogate key, user-facing batch number, and the batch status code. These are the primary reporting dimensions and the fields most often joined back to GME_BATCH_HEADER.
• RECIPE_ID / RECIPE_NO / RECIPE_VERSION – recipe identity and version inherited through the validity rule.
• ROUTING_ID / ROUTING_NO / ROUTING_VERS / ROUTING_CLASS – routing identity, routing number, the routing version (the column the searcher sought), and the routing class used to categorize routing definitions.
• FORMULA_ID / FORMULA_NO / FORMULA_VERS – formula master identity, formula number, and formula version for the batch.

The presence of parallel version columns for recipe, routing, and formula makes the view especially convenient for version-audit and traceability queries.

Common Use Cases and Queries

Typical uses include batch-to-routing traceability, version reconciliation across recipe/routing/formula, and SLA diagnostic reporting. A representative query to list batches with their routing versions is:

• SELECT batch_no, batch_status, routing_no, routing_vers, routing_class, recipe_no, formula_no FROM apps.gmf_xla_batch_hdr_v WHERE routing_vers IS NOT NULL ORDER BY batch_no;
• Filtering by a specific version: SELECT batch_no, routing_no, routing_vers FROM apps.gmf_xla_batch_hdr_v WHERE routing_vers = :version;
• Identifying batches missing routing assignments: SELECT batch_id, batch_no FROM apps.gmf_xla_batch_hdr_v WHERE routing_id IS NULL;

Because the underlying joins use outer joins on routing and formula, queries should test for nulls where those attributes are mandatory for business purposes. The view is not designed for high-volume transactional updates and should be treated strictly as a query and extract source.