Results for “end_date_type”

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

Overview

GMD_RECIPE_GENERATION is a table in the Oracle E-Business Suite Process Manufacturing Product Development module (GMD). Its documented purpose is "Recipe Generation for automatic creation," meaning it stores the control parameters that drive the automatic generation of process manufacturing recipes. Rather than holding recipe formulations themselves, this table functions as a configuration and driver object: each row defines a generation request specifying which recipe uses to create (production, planning, costing, regulatory, technical), the organization, the effective date window, and the naming and validity rules applied during generation.

The table resides in the GMD schema and is classified as VALID in the ETRM 12.1.1 / 12.2.2 documentation. Its documented physical schema in ETRM 12.2.2 contains 22 columns. From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This indicates that GMD_RECIPE_GENERATION has no documented foreign-key dependencies to other tables, and it is best modeled as an independent hub-like construct keyed by its own identifier, with the descriptive attributes (dates, flags, organization) carried alongside. No link or satellite relationships are documented for this object.

Key Information Stored

The primary key of the table is GMD_RECIPE_GENERATION_PK, defined on the column RECIPE_GENERATION_ID. A unique index, GMD_RECIPE_GENERATION_U1, is also documented on RECIPE_GENERATION_ID, making that column both the surrogate primary key and the only documented business-key candidate.

The most significant remaining columns fall into several groups:

• Recipe use flags: RECIPE_USE_PROD, RECIPE_USE_PLAN, RECIPE_USE_COST, RECIPE_USE_REG, and RECIPE_USE_TECH indicate which recipe types the generation process should produce — production, planning, costing, regulatory, and technical recipes respectively.
• Creation control: CREATION_TYPE distinguishes the mode of automatic creation, while RECIPE_NAMING_CONVENTION defines the naming pattern applied to generated recipes.
• Validity window: START_DATE, START_DATE_TYPE, END_DATE, END_DATE_TYPE, and NUM_OF_DAYS define when generated recipes become effective and how their end dates are derived. MANAGING_VALIDITY_RULES governs enforcement of these validity rules.
• Organization and calendar context: ORGN_CODE and ORGANIZATION_ID identify the inventory organization in which recipes are generated, and COST_CALENDAR names the costing calendar used for cost-related generation.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS WHO-column auditing.

Common Use Cases and Queries

Typical usage centers on inspecting or auditing automatic recipe generation runs. A common reporting pattern lists all generation definitions for an organization with their validity windows:

• SELECT recipe_generation_id, orgn_code, creation_type, start_date, end_date, start_date_type FROM gmd_recipe_generation WHERE organization_id = :org_id;
• SELECT recipe_generation_id, recipe_use_prod, recipe_use_plan, recipe_use_cost, recipe_use_reg, recipe_use_tech FROM gmd_recipe_generation WHERE creation_type = :type;
• SELECT recipe_generation_id, recipe_naming_convention, managing_validity_rules, cost_calendar FROM gmd_recipe_generation ORDER BY last_update_date DESC;

These queries support troubleshooting why a recipe was or was not generated, verifying that validity rules and naming conventions are configured correctly, and producing audit reports of generation activity by organization and date range.

Related Objects

The ETRM metadata documents no foreign keys for GMD_RECIPE_GENERATION, consistent with its standalone Data Vault classification. Consequently, no join columns to other tables are asserted in the reference documentation. Related objects in the Process Manufacturing Product Development module would logically include the recipe and recipe-validity tables in the GMD schema (for example, recipe header and recipe validity entities) and the concurrent program that consumes the generation parameters; however, since no FK or PK relationship data is documented for this table, any such associations should be validated directly against the Oracle EBS data model before being relied upon in queries.