DBA Data[Home] [Help] [Dependency Information]


VIEW: APPS.GMD_MBR_RECIPE_HEADER_V1

Object Details
Object Name: GMD_MBR_RECIPE_HEADER_V1
Object Type: VIEW
Owner: APPS
FND Design Data: ViewGMD.GMD_MBR_RECIPE_HEADER_V1
Subobject Name:
Status: VALID

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle
applications data using this object, except from standard Oracle Applications programs.

View Type

Internal

[View Source]

Columns
Name Datatype Length Mandatory Comments
RECIPE_ID NUMBER (15) Yes Recipe ID - Primary Key, Unique Identifier for a Recipe
RECIPE_DESCRIPTION VARCHAR2 (240) Yes Recipe Description
RECIPE_NO VARCHAR2 (32) Yes Recipe Number - Along with Recipe Version, part of the Alternate Key for the Recipe.
RECIPE_VERSION NUMBER (5) Yes Recipe Version - Along with Recipe Number, part of the Alternate Key for the Recipe.
OWNER_ORGANIZATION_ID NUMBER (15) Yes OPM Organization code that owns this Recipe. Users who wish to modify this Recipe must have access to this organization.
CREATION_ORGANIZATION_ID NUMBER (15) Yes OPM Organization code of the user that created this Recipe. Listed for the purpose of Recipe history & auditability.
FORMULA_ID NUMBER (10) Yes The Formula ID associated with this Recipe. A Formula is required in order to create a Recipe.
ROUTING_ID NUMBER (15)
The Routing ID associated with this Recipe. It is optional to associate a Routing with a Recipe.
PROJECT_ID NUMBER (15)
Project ID field. Not used yet, but will be used to associate a Recipe with a Project in a future release
RECIPE_STATUS VARCHAR2 (30) Yes The Status of the Recipe header (different than the status on the Validity Rules). The combination of the Recipe and Validity Rule status will be used to determine what a Recipe can be used for. See the GMD_STATUS table for a list of possible Status's.
PLANNED_PROCESS_LOSS NUMBER

The Planned Process Loss, derived from the Routing or Routing Class tables, if defined.
CONTIGUOUS_IND NUMBER (5)
This is the contiguous indicator column description
OWNER_ID NUMBER (15) Yes User ID of the Recipe owner
OWNER_LAB_TYPE VARCHAR2 (4)
Laboratory associated with the Recipe (optional).
CALCULATE_STEP_QUANTITY NUMBER (5)
Determines whether or not Step Quantities will be automatically calculated for this Recipe. Step Material Association and Step Dependencies are necessary for this calculation to be accurate.
FORMULA_NO VARCHAR2 (32) Yes Formula number
FORMULA_DESC1 VARCHAR2 (240) Yes Formula Description
FORMULA_DESC2 VARCHAR2 (240)
Formula Description
FORMULA_VERS NUMBER
Yes Formula Version
FORMULA_TYPE NUMBER (5) Yes 0=std formula; 1=packaged item formula
FORMULA_SCALE_TYPE NUMBER (5) Yes Controls scaling behavior of formula. 0=Formula cannot be scaled, 1=Formula can be scaled
FORMULA_CLASS VARCHAR2 (8)
Formula class. No programatic support (fm_form_cls).
FORMULA_FMCONTROL_CLASS VARCHAR2 (8)
Not currently used. (fn_fmct_cls).
FORMULA_INACTIVE_IND NUMBER (5) Yes Inactive indicator. 0=Active, 1=Inactive.
FORMULA_STATUS VARCHAR2 (30)
Formula Status
FORMULA_OWNER_ID NUMBER (15)
Owner Identifier
FORMULA_TOTAL_INPUT_QTY NUMBER

Total Input Quantity
FORMULA_TOTAL_OUTPUT_QTY NUMBER

Total Output Quantity
FORMULA_UOM VARCHAR2 (3)
Formula Unit of Measure
FORMULA_OWNER_ORGANIZATION_ID NUMBER (15) Yes Inventory organization id
MASTER_FORMULA_ID NUMBER (15)
Parent formula id
ROUTING_NO VARCHAR2 (32)
Routing number
ROUTING_VERS NUMBER (5)
Routing Version
ROUTING_CLASS VARCHAR2 (4)
User defined class for routings.
ROUTING_QTY NUMBER

Used in ratio with formula and batch qty to scale individual step requirements.
ROUTING_ITEM_UM VARCHAR2 (4)
Uom of routing qty
ROUTING_INACTIVE_IND NUMBER (5)
Not used
ROUTING_EFFECTIVE_START_DATE VARCHAR2 (4000)
Date from which this routing is valid
ROUTING_EFFECTIVE_END_DATE VARCHAR2 (4000)
Date to which this Routing is valid
ROUTING_ROUTING_OWNER_ID NUMBER (15)
User id for this routings Owner
ROUTING_PROCESS_LOSS NUMBER

Planned process loss forthis routing
ROUTING_STATUS VARCHAR2 (30)
Routing Status
ROUT_ENFORCE_STEP_DEPENDENCY NUMBER (5)
This column indicates if the step dependencies have to be enforced in the batches
ROUTING_DESC VARCHAR2 (240)
Routing Description
ROUTING_UOM VARCHAR2 (3)
Routing UOM in 3 characters
ROUTING_OWNER_ORGANIZATION_ID NUMBER (15)
Inventory Organization Id
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT RECIPE_ID
,      RECIPE_DESCRIPTION
,      RECIPE_NO
,      RECIPE_VERSION
,      OWNER_ORGANIZATION_ID
,      CREATION_ORGANIZATION_ID
,      FORMULA_ID
,      ROUTING_ID
,      PROJECT_ID
,      RECIPE_STATUS
,      PLANNED_PROCESS_LOSS
,      CONTIGUOUS_IND
,      OWNER_ID
,      OWNER_LAB_TYPE
,      CALCULATE_STEP_QUANTITY
,      FORMULA_NO
,      FORMULA_DESC1
,      FORMULA_DESC2
,      FORMULA_VERS
,      FORMULA_TYPE
,      FORMULA_SCALE_TYPE
,      FORMULA_CLASS
,      FORMULA_FMCONTROL_CLASS
,      FORMULA_INACTIVE_IND
,      FORMULA_STATUS
,      FORMULA_OWNER_ID
,      FORMULA_TOTAL_INPUT_QTY
,      FORMULA_TOTAL_OUTPUT_QTY
,      FORMULA_UOM
,      FORMULA_OWNER_ORGANIZATION_ID
,      MASTER_FORMULA_ID
,      ROUTING_NO
,      ROUTING_VERS
,      ROUTING_CLASS
,      ROUTING_QTY
,      ROUTING_ITEM_UM
,      ROUTING_INACTIVE_IND
,      ROUTING_EFFECTIVE_START_DATE
,      ROUTING_EFFECTIVE_END_DATE
,      ROUTING_ROUTING_OWNER_ID
,      ROUTING_PROCESS_LOSS
,      ROUTING_STATUS
,      ROUT_ENFORCE_STEP_DEPENDENCY
,      ROUTING_DESC
,      ROUTING_UOM
,      ROUTING_OWNER_ORGANIZATION_ID
FROM APPS.GMD_MBR_RECIPE_HEADER_V1;

Dependencies

[top of page]

APPS.GMD_MBR_RECIPE_HEADER_V1 references the following:

SchemaAPPS
ViewFM_FORM_MST_VL
PL/SQL PackageFND_DATE - show dependent code
PL/SQL PackageFND_TIMEZONES - show dependent code
ViewGMD_RECIPES_VL
ViewGMD_ROUTINGS_VL
ViewGMD_STATUS_VL

APPS.GMD_MBR_RECIPE_HEADER_V1 is not referenced by any database object