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


VIEW: APPS.PMIFV_FORMULA_SUMMARY_V

Object Details
Object Name: PMIFV_FORMULA_SUMMARY_V
Object Type: VIEW
Owner: APPS
FND Design Data: ViewPMI.PMIFV_FORMULA_SUMMARY_V
Subobject Name:
Status: VALID

View Type

A Business Intelligence System view


The product and effectivity information for a formula including routing information. This does not contain ingredient information.


[View Source]

Columns
Name Datatype Length Mandatory Comments
FORMULA_NO VARCHAR2 (32) Yes Alphanumeric formula name or number.
FORMULA_VERSION NUMBER
Yes Formula version.
FORMULA_TYPE NUMBER (5) Yes 0=std formula; 1=packaged item formula (these are not currently used).
FORMULA_TYPE_MEANING VARCHAR2 (80)
0=std formula; 1=packaged item formula (these are not currently used).
SCALE_TYPE NUMBER (5) Yes Controls scaling behavior of formula. 0=Formula cannot be scaled, 1=Formula can be scaled.
FORMULA_DESC1 VARCHAR2 (240) Yes Formula description.
FORMULA_DESC2 VARCHAR2 (240)
Formula comment.
FORMULA_CLASS VARCHAR2 (8)
Formula class. No programatic support (fm_form_cls).
FORMULA_CONTROL_CLASS VARCHAR2 (8)
Not currently used. (fn_fmct_cls).
FORMULA_ID NUMBER (10) Yes Surrogate for formula_no + formula_vers.
FORMULA_EFECTIVITY_ID NUMBER (15)
Surrogate key for this effectivity row.
ORGNIZATION_CODE VARCHAR2 (4)
The organization which can use the formula/routing. This is blank if all organizations can use the formula/routing.
EFFECTIVITY_ITEM_ID NUMBER (15)
Surrogate key for the item which is produced by the formula.
EFECTIVITY_ROUTING_ID NUMBER (15)
Surrogate key for the routing/routing version to be used, if any.
EFFECTIVITY_FORMULA_ID NUMBER (10)
Surrogate key for the formula /formula version to be used.
EFFECTIVITY_CUST_ID NUMBER

Surrogate key for the customer for which this effectivity is used, if any.
EFFECTIVITY_FORMULA_USE VARCHAR2 (30)
The purpose for which the formula/routing can be used. 0=Prod, 1=MRP, 2=Costing, 3=MSDS.
EFF_FORMULA_USE_MEANING VARCHAR2 (80)
The purpose for which the formula/routing can be used. 0=Prod, 1=MRP, 2=Costing, 3=MSDS.
EFFECTIVITY_END_DATE DATE

The end date of the effectivity.
EFFECTIVITY_START_DATE DATE

The start date of the effectivity.
MIN_OUTPUT_QTY_PRIMARY_UOM NUMBER

The minimum qty for which this effectivity can be used, expressed in the primary UOM of an item.
MAX_OUTPUT_QTY_PRIMARY_UOM NUMBER

The maximum qty for which this effectivity can be used, expressed in the primary UOM of an item.
MIN_OUTPUT_QTY_EFF_UOM NUMBER

The minimum qty for which this effectivity can be used, expressed in the UOM entered in the item_um column.
MAX_OUTPUT_QTY_EFF_UOM NUMBER

The maximum qty for which this effectivity can be used, expressed in the UOM entered in the item_um column.
PRODUCT_QTY NUMBER

Standard batch size for this rec.
PRODUCT_UOM VARCHAR2 (4)
UOM for min_qty and max_qty.
EFFECTIVITY_PREFERENCE NUMBER (15)
Preference indicator used by MRP to select which effectiviity to use if more than one meets the requirements. MRP will select the effectivity with the lowest number in this column.
PRODUCT_ITEM_NO VARCHAR2 (32)
Name of the item.
PRODUCT_DESC1 VARCHAR2 (70)
Short description of the item that is displayed during the item look up.
PRODUCT_DESC2 VARCHAR2 (70)
Short description of the item that is not displayed during the item look up.
CUSTOMER_NO VARCHAR2 (4000)
Unique identifier of a customer.
CUSTOMER_NAME VARCHAR2 (40)
Customer name
ROUTING_NO VARCHAR2 (32)
Routing name.
ROUTING_VERSION NUMBER (5)
Routing version.
ROUTING_DESCRIPTION VARCHAR2 (240)
Routing description.
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_UOM VARCHAR2 (4)
Uom of routing qty.
CREATED_BY NUMBER (15) Yes Standard who column
CREATION_DATE DATE
Yes Standard who column
LAST_UPDATE_DATE DATE
Yes Standard who column
LAST_UPDATED_BY NUMBER (15) Yes Standard who column
Query Text

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


SELECT FORMULA_NO
,      FORMULA_VERSION
,      FORMULA_TYPE
,      FORMULA_TYPE_MEANING
,      SCALE_TYPE
,      FORMULA_DESC1
,      FORMULA_DESC2
,      FORMULA_CLASS
,      FORMULA_CONTROL_CLASS
,      FORMULA_ID
,      FORMULA_EFECTIVITY_ID
,      ORGNIZATION_CODE
,      EFFECTIVITY_ITEM_ID
,      EFECTIVITY_ROUTING_ID
,      EFFECTIVITY_FORMULA_ID
,      EFFECTIVITY_CUST_ID
,      EFFECTIVITY_FORMULA_USE
,      EFF_FORMULA_USE_MEANING
,      EFFECTIVITY_END_DATE
,      EFFECTIVITY_START_DATE
,      MIN_OUTPUT_QTY_PRIMARY_UOM
,      MAX_OUTPUT_QTY_PRIMARY_UOM
,      MIN_OUTPUT_QTY_EFF_UOM
,      MAX_OUTPUT_QTY_EFF_UOM
,      PRODUCT_QTY
,      PRODUCT_UOM
,      EFFECTIVITY_PREFERENCE
,      PRODUCT_ITEM_NO
,      PRODUCT_DESC1
,      PRODUCT_DESC2
,      CUSTOMER_NO
,      CUSTOMER_NAME
,      ROUTING_NO
,      ROUTING_VERSION
,      ROUTING_DESCRIPTION
,      ROUTING_CLASS
,      ROUTING_QTY
,      ROUTING_ITEM_UOM
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
FROM APPS.PMIFV_FORMULA_SUMMARY_V;

Dependencies

[top of page]

APPS.PMIFV_FORMULA_SUMMARY_V references the following:

SchemaAPPS
SynonymFM_FORM_EFF
SynonymFM_FORM_MST
SynonymFM_ROUT_HDR
PL/SQL PackageFND_PROFILE - show dependent code
SynonymIC_ITEM_MST
SynonymOP_CUST_MST
PL/SQL PackagePMI_COST_ANALZ_PACK - show dependent code
PL/SQL PackagePMI_SECURITY_PKG - show dependent code
SynonymSY_ORGN_MST

APPS.PMIFV_FORMULA_SUMMARY_V is not referenced by any database object