data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.RTG_PLANPRDS

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.RTG_PLANPRDS

Table FPSINPUT.RTG_PLANPRDS"

Prd and planprd have a many-to-many relationship. Multiple prds share the same planprd when those prds are interchangeable to ship to a customer despite their different processing. These prds could use different routes or even be different technologies or have different wafer sizes but if the customer does not care then they share a planprd. On the other hand, a prd can have multiple planprds when there are different varieties based on recipes or durables used at a particular time that matter to the customer.

  • Schema: FPSINPUT

  • Tablespace: FPSDATA

  • Primary key: PLANPRD

  • Foreign keys: RTG_PLANPRDS_CUSTOMER: CUSTOMER REFERENCES FPSINPUT.GEN_CUSTOMERS (CUSTOMER)


Column

Type

Nullable

Comment

PLANPRD

VARCHAR2(64)

N

Planning product used for all planning purposes. All lots with the same planprd are interchangeable to ship to the customer regardless of their prd, route, technology, wafer size, etc. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS.

CUSTOMER

VARCHAR2(64)

Customer who will accept shipment of the lot. Currently this only used for grouping and filtering but in the future we might want to allow a customer to view a Dashboard only including their products. (* from FPSINPUT.GEN_CUSTOMERS)

OVR_BEST_PRD

VARCHAR2(64)

The is_best_record_for_planprd value is automatically calculated in RTG_ACTIVE_PRD_ROUTES but if you wish to override the calculation and force a specific prd to be the best then you can populate this column.