opm data modeling

Oracle ProcessManufacturing Data ModelingRelease 11iStudent Guide

14746GC10

Edition 1.0

December 2000

M014243

Copyright Oracle Corporation, 2000. All rights reserved.

This documentation contains proprietary information of Oracle Corporation. It is provided under a licenseagreement containing restrictions on use and disclosure and is also protected by copyright law. Reverseengineering of the software is prohibited. If this documentation is delivered to a U.S. Government Agency of theDepartment of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

Restricted Rights Legend

Use, duplication or disclosure by the Government is subject to restrictions for commercial computer softwareand shall be deemed to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii)of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).

This material or any portion of it may not be copied in any form or by any means without the express priorwritten permission of the Education Products group of Oracle Corporation. Any other copying is a violation ofcopyright law and may result in civil and/or criminal penalties.

If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it isdelivered with Restricted Rights, as defined in FAR 52.227-14, Rights in Data-General, including Alternate III(June 1987).

The information in this document is subject to change without notice. If you find any problems in thedocumentation, please report them in writing to Worldwide Education Services, Oracle Corporation, 500 OracleParkway, Box SB-6, Redwood Shores, CA 94065. Oracle Corporation does not warrant that this document iserror-free.

Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle Corporation.

All other products or company names are used for identification purposes only, and may be trademarks of theirrespective owners.

Author

Michele-Andrea Fields

Technical Contributors and Reviewers

Leslie Hershey, Ralph Kindred, Glen Ruhl, Bill Stearns

This book was published using:

Oracle Tutor


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsi

Table of Contents

Oracle Process Manufacturing Data Modeling...................................................................1-1Oracle Process Manufacturing Data Modeling....................................................................1-2Objectives ............................................................................................................................1-3Agenda.................................................................................................................................1-5

Database and Object Design .................................................................................................2-1Database and Object Design ................................................................................................2-2Objectives ............................................................................................................................2-3Ten Schemas........................................................................................................................2-4The APPS Schema...............................................................................................................2-5Table Attributes: OPM Tables.............................................................................................2-6Table Attributes ...................................................................................................................2-8Table Attributes: Text_Code ...............................................................................................2-11Table Attributes: Delete_Mark ............................................................................................2-12Primary Keys .......................................................................................................................2-13Indexes.................................................................................................................................2-15Foreign Keys........................................................................................................................2-16Surrogate IDs.......................................................................................................................2-17Sequences ............................................................................................................................2-19Stored Procedures, Views, and Triggers..............................................................................2-20Null Columns.......................................................................................................................2-21Multilanguage Support (MLS).............................................................................................2-22Multilanguage Support ........................................................................................................2-23Reading a Technical Reference Manual (TRM) ..................................................................2-24Reading a TRM ...................................................................................................................2-25Summary..............................................................................................................................2-30

System Setup ..........................................................................................................................3-1System Setup .......................................................................................................................3-2Objectives ............................................................................................................................3-3Essential System Setup ........................................................................................................3-4System Administrative Module Tables................................................................................3-5System Administrative Relationships ..................................................................................3-6Common Modules Interface ................................................................................................3-7Data Synchronized to OPM .................................................................................................3-8Data Synchronized from OPM ............................................................................................3-9AP FOB Codes ....................................................................................................................3-10FOB Code Field Mapping....................................................................................................3-11AP Invoice Terms ................................................................................................................3-13AP Terms Field Mapping ....................................................................................................3-14Salesreps ..............................................................................................................................3-15Salesrep Field Mapping .......................................................................................................3-16Customers ............................................................................................................................3-17Customer Field Mapping .....................................................................................................3-18Vendors................................................................................................................................3-19Vendor Field Mapping.........................................................................................................3-20Data Triggered to OPM .......................................................................................................3-21Data Triggered Over from OPM..........................................................................................3-22Currency Codes ...................................................................................................................3-23Currency Code Field Mapping ............................................................................................3-24Exchange Rate Types ..........................................................................................................3-25Exchange Rate Type Field Mapping....................................................................................3-26Exchange Rates....................................................................................................................3-27


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsii

Exchange Rate Field Mapping.............................................................................................3-28OPM UOM Types................................................................................................................3-29UOM Type Field Mapping ..................................................................................................3-30OPM UOM ..........................................................................................................................3-31OPM UOM Conversions .....................................................................................................3-32Unit of Measure Field Mapping...........................................................................................3-33OPM Inventory to Oracle Inventory....................................................................................3-34Item Field Mapping .............................................................................................................3-35OPM Item/Lot Conversions.................................................................................................3-36Item/Lot Conversion............................................................................................................3-37Summary..............................................................................................................................3-38

Inventory ................................................................................................................................4-1Inventory..............................................................................................................................4-2Objectives ............................................................................................................................4-3Inventory Management ........................................................................................................4-4Inventory Module Tables.....................................................................................................4-5Inventory Relationships .......................................................................................................4-6Document Types..................................................................................................................4-7Pending and Completed Transactions..................................................................................4-8Inventory Setup Data ...........................................................................................................4-9Inventory Transactions ........................................................................................................4-10Transaction Flow .................................................................................................................4-12Pending to Completed Transactions ....................................................................................4-13Physical Inventory ...............................................................................................................4-15Physical Inventory Process Flow.........................................................................................4-16Summary..............................................................................................................................4-17

New Product Development....................................................................................................5-1New Product Development..................................................................................................5-2Objectives ............................................................................................................................5-3Formulas ..............................................................................................................................5-4Routings...............................................................................................................................5-5Formula Module Tables.......................................................................................................5-6Formula Relationships .........................................................................................................5-7Formula/Effectivity Structure ..............................................................................................5-8Laboratory Management......................................................................................................5-9Summary..............................................................................................................................5-11

Quality Management .............................................................................................................6-1Quality Management ...........................................................................................................6-2Objectives ............................................................................................................................6-3Oracle Workflow: Overview................................................................................................6-4Sample Approval Workflow................................................................................................6-5OPM Quality Views ............................................................................................................6-6OPM Quality Sample Approval Workflow .........................................................................6-7Sample Creation Notification Workflow.............................................................................6-8Assay Testing Process Workflow........................................................................................6-10Sample Disposition Workflow.............................................................................................6-12Assays and Units of Measure...............................................................................................6-15Summary..............................................................................................................................6-16

Production Management and Process Operation Control .................................................7-1Production Management and Process Operation Control ....................................................7-2Objectives ............................................................................................................................7-3Production Management ......................................................................................................7-4Production Batch Cycle .......................................................................................................7-5Production Module Tables...................................................................................................7-6Data in Production Management .........................................................................................7-7


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsiii

Batch Relationships .............................................................................................................7-8Batch Type in Production ....................................................................................................7-9Batch Status .........................................................................................................................7-10Reversal of Completed Transactions and Audit Trail..........................................................7-11Process Operations Control Concepts..................................................................................7-13Process Operations Control .................................................................................................7-14Important Data in POC ........................................................................................................7-15Process Operation Control Module Tables ..........................................................................7-16Batch with POC Relationships ............................................................................................7-17Summary..............................................................................................................................7-18

Purchase Management ..........................................................................................................8-1Purchase Management .........................................................................................................8-2Objectives ............................................................................................................................8-3OPM Purchasing Flow.........................................................................................................8-5OPM Purchasing Tables ......................................................................................................8-6OPM Receiving/Return Tables............................................................................................8-7Purchasing Integration .........................................................................................................8-8Purchasing Documents ........................................................................................................8-9Data Synchronization...........................................................................................................8-12Data Synchronization through Triggers...............................................................................8-13Integration Highlights ..........................................................................................................8-14OPM Purchasing Setup Tables ............................................................................................8-15PO Synchronization .............................................................................................................8-16Common Purchasing Tables ................................................................................................8-17Common Purchasing Triggers .............................................................................................8-20Key Triggers on Oracle PO Tables......................................................................................8-21Triggers on OPM Tables .....................................................................................................8-22Validation Triggers..............................................................................................................8-23Why Cant I See My PO in OPM? ......................................................................................8-24Why Cant I See My Receipt Information in Oracle PO? ...................................................8-26Summary..............................................................................................................................8-27

Order Fulfillment...................................................................................................................9-1Order Fulfillment .................................................................................................................9-2Objectives ............................................................................................................................9-3Order Fulfillment Setup Tables ...........................................................................................9-4Commission Code Structure ................................................................................................9-5MLS Setup Tables ...............................................................................................................9-6Pricing Tables ......................................................................................................................9-7Tables for Processing and Reports.......................................................................................9-8Sales Order Processing Flow ...............................................................................................9-9Customer Master and Related Tables ..................................................................................9-10Sales Order Transaction Flow..............................................................................................9-11Order/Shipment Transaction Tables ....................................................................................9-12Order Profile (+BSO) Tables...............................................................................................9-13GEMMS Sales Order Processing to Oracle Receivables.....................................................9-14Tax Tables ...........................................................................................................................9-15Tax Locations ......................................................................................................................9-16Summary..............................................................................................................................9-17

Regulatory Management.......................................................................................................10-1Regulatory Management......................................................................................................10-2Objectives ............................................................................................................................10-3Regulatory Setup Tables......................................................................................................10-4Material Safety Data Sheet (MSDS)....................................................................................10-5Regulatory Document Tables ..............................................................................................10-6Regulatory Item Tables........................................................................................................10-8


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsiv

Regulatory Label Tables......................................................................................................10-10Summary..............................................................................................................................10-12


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsv

Preface

Profile

Prerequisites

Oracle Process Manufacturing Foundation, Release 11

How This Course Is Organized

Oracle Process Manufacturing Data Modeling Release 11i is an instructor-ledcourse featuring lecture and hands-on exercises. Online demonstrations andwritten practice sessions reinforce the concepts and skills introduced.


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsvi

Related Publications

Additional Publications

System release bulletins

Installation and users guides

OPM Technical Reference Manuals

read.me files

Oracle Magazine


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsvii

Typographic Conventions

Typographic Conventions in Text

Convention Element ExampleBold italic Glossary term (if

there is a glossary)The algorithm inserts the new key.

Caps andlowercase

Buttons,check boxes,triggers,windows

Click the Executable button.Select the Cant Delete Card check box.Assign a When-Validate-Item trigger to theORD block.Open the Master Schedule window.

Courier new,case sensitive(default islowercase)

Code output,directory names,filenames,passwords,pathnames,URLs,user input,usernames

Code output: debug.set (I, 300);Directory: bin (DOS), $FMHOME (UNIX)Filename: Locate the init.ora file.Password: User tiger as your password.Pathname: Open c:\my_docs\projectsURL: Go to http://www.oracle.comUser input: Enter 300Username: Log on as scott

Initial cap Graphics labels(unless the term is aproper noun)

Customer address (but Oracle Payables)

Italic Emphasized wordsand phrases,titles of books andcourses,variables

Do not save changes to the database.For further information, see Oracle7 ServerSQL Language Reference Manual.Enter [email protected],where user_id is the name of the user.

Quotationmarks

Interface elementswith long namesthat have onlyinitial caps;lesson and chaptertitles in cross-references

Select Include a reusable module componentand click Finish.

This subject is covered in Unit II, Lesson 3,Working with Objects.

Uppercase SQL columnnames, commands,functions, schemas,table names

Use the SELECT command to viewinformation stored in the LAST_NAMEcolumn of the EMP table.

Convention Element ExampleArrow Menu paths Select File> Save.


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsviii

Brackets Key names Press [Enter].

Commas Key sequences Press and release keys one at a time:[Alternate], [F], [D]

Plus signs Key combinations Press and hold these keys simultaneously:[Ctrl]+[Alt]+[Del]

Typographic Conventions in Code

Convention Element ExampleCaps andlowercase

Oracle Formstriggers

When-Validate-Item

Lowercase Column names,table names

SELECT last_nameFROM s_emp;

Passwords DROP USER scottIDENTIFIED BY tiger;

PL/SQL objects OG_ACTIVATE_LAYER(OG_GET_LAYER

(prod_pie_layer))

Lowercaseitalic

Syntax variables CREATE ROLE role

Uppercase SQL commands andfunctions

SELECT useridFROM emp;

Typographic Conventions in Navigation Paths

This course uses simplified navigation paths, such as the following example, todirect you through Oracle Applications.

(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve

This simplified path translates to the following:

1. (N) From the Navigator window, select Invoice > Entry > Invoice BatchesSummary.

2. (M) From the menu, select Query > Find.

3. (B) Click the Approve button.

Notations :

(N) = Navigator

(M) = Menu

(T) = Tab


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsix

(I) = Icon

(H) = Hyperlink

(B) = Button

Typographical Conventions in Help System Paths

This course uses a navigation path convention to represent actions you performto find pertinent information in the Oracle Applications Help System.

The following help navigation path, for example

(Help) General Ledger > Journals > Enter Journals

represents the following sequence of actions:

1. In the navigation frame of the help system window, expand the GeneralLedger entry.

2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals.

4. Review the Enter Journals topic that appears in the document frame of thehelp system window.

Getting Help

Oracle Applications provides you with a complete online help facility.

Whenever you need assistance, simply choose an item from the Help menu topinpoint the type of information you want.

To display help for a current window:

1. Choose Window Help from the Help menu, click the Help button on thetoolbar, or hold down the Control key and type 'h'.

A web browser window appears, containing search and navigation frames onthe left, and a frame that displays help documents on the right.

The document frame provides information on the window containing thecursor. The navigation frame displays the top-level topics for yourresponsibility, arranged in a tree control.

2. If the document frame contains a list of topics associated with the window,click on a topic of interest to display more detailed information.


Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsx

3. You can navigate to other topics of interest in the help system, or chooseClose from your web browser's File menu to close help.

Searching for Help

You can perform a search to find the Oracle Applications help information youwant. Simply enter your query in the text field located in the top-left frame of thebrowser window when viewing help, then click the adjacent Find button.

A list of titles, ranked by relevance and linked to the documents in question, isreturned from your search in the right-hand document frame. Click on whichevertitle seems to best answer your needs to display the complete document in thisframe. If the document doesn't fully answer your questions, use your browser'sBack button to return to the list of titles and try another.


Oracle Process Manufacturing Data ModelingChapter 1 - Page 1

Oracle ProcessManufacturing Data ModelingChapter 1



Oracle Process Manufacturing Data Modeling


Oracle Process Manufacturing DataModeling

Oracle Process Manufacturing DataModeling



Objectives


ObjectivesObjectives

After completing this course, you should be able todo the following: Describe Oracle Process Manufacturing (OPM)

database tables Explain primary keys and foreign keys Identify pending versus completed transactions Recognize the document-based transaction

concept Compare relationships between OPM forms and

OPM tables

After completing this course, you should be able todo the following: Describe Oracle Process Manufacturing (OPM)

database tables Explain primary keys and foreign keys Identify pending versus completed transactions Recognize the document-based transaction

concept Compare relationships between OPM forms and

OPM tables



Objectives



After completing this course, you should be able todo the following: Identify essential table relationships Describe shared tables with other Oracle

applications Specify reports for Discoverer or SQL Plus Validate results of OPM functions Investigate performance issues Address product functionality gaps Handle functionality gaps

Investigate proposed interfaces Determine impact of proposed bolt-ons

After completing this course, you should be able todo the following: Identify essential table relationships Describe shared tables with other Oracle

applications Specify reports for Discoverer or SQL Plus Validate results of OPM functions Investigate performance issues Address product functionality gaps Handle functionality gaps

Investigate proposed interfaces Determine impact of proposed bolt-ons



Agenda


AgendaAgenda

Defining Database and Object Design Reading a Technical Reference Manual Listing system setup Describing the Inventory Module Explaining the New Product Development Modules Understanding the Quality Module Recognizing results and changes in the

Production Module Describing the Purchase Order and Order

Fulfillment Modules Understanding Regulatory Management and

Material Safety Data Sheets (MSDS)

Defining Database and Object Design Reading a Technical Reference Manual Listing system setup Describing the Inventory Module Explaining the New Product Development Modules Understanding the Quality Module Recognizing results and changes in the

Production Module Describing the Purchase Order and Order

Fulfillment Modules Understanding Regulatory Management and

Material Safety Data Sheets (MSDS)


Database and Object DesignChapter 2 - Page 1

Database and Object DesignChapter 2



Database and Object Design


Database and Object DesignDatabase and Object Design



Objectives



After completing this lesson, you should be able todo the following: Demonstrate a working knowledge of the overall

schemas Define naming conventions List common table characteristics Use a technical reference manual

After completing this lesson, you should be able todo the following: Demonstrate a working knowledge of the overall

schemas Define naming conventions List common table characteristics Use a technical reference manual



Ten Schemas


Ten SchemasTen Schemas

GMASystem Administration

GMDProduct Development

GMEProcess Execution

GMFFinancials

GMIInventory Management

GMLLogistics

GMPProcess Planning

GRRegulatory Management

GMWOPM Portal

PMIProcess ManufacturingIntelligence

Each OPM application has its own schema; in otherwords, it is the owner of all of the database objects ituses, including tables, indexes, and sequences.

Each OPM application has its own schema; in otherwords, it is the owner of all of the database objects ituses, including tables, indexes, and sequences.

Ten SchemasA major division of any Oracle database is a tablespace. For example, data andindexes for the data reside in different tablespaces to allow for performancetuning through placement in storage media and amounts of storage provided.Placing the OPM modules in different schemas also provides separatetablespaces and the enhanced ability to tune applications.



The APPS Schema


The APPS SchemaThe APPS Schema

GL

PER

GMIAPPS

The Application connects tothe database as the APPSuser, which recognizes allother application databaseobjects through synonyms.Though GMI owns the OPMInventory tables, user APPShas full privileges to GMItables.All packages, procedures,triggers, and views are createdin and owned by the APPSschema.

The Application connects tothe database as the APPSuser, which recognizes allother application databaseobjects through synonyms.Though GMI owns the OPMInventory tables, user APPShas full privileges to GMItables.All packages, procedures,triggers, and views are createdin and owned by the APPSschema.

The APPS user is a database sign on account that does not own all the tables ofthe applications but uses synonyms to access the objects owned by any of theschemas.



Table Attributes: OPM Tables


Table Attributes: OPM TablesTable Attributes: OPM Tables

Table Naming: MM_FFFF_TTT MM = Module FFFF = Object/Function TTT = Type, or hierarchy, of information stored

(MST, HDR, DTL, CLS)Example:ic_item_mst ..... ic = Inventory ControlThis table is the Item Master.

Table Naming: MM_FFFF_TTT MM = Module FFFF = Object/Function TTT = Type, or hierarchy, of information stored

(MST, HDR, DTL, CLS)Example:ic_item_mst ..... ic = Inventory ControlThis table is the Item Master.



Table Attributes: OPM Tables


Table Attributes: OPM TablesTable Attributes: OPM TablesSome new extensions to basic table names are: _TL: Translation involved; for example,

op_text_tbl_tl _VL: MLS view _WK: Temporary work table, as in indented bills of

material (BOMs) _B: When a new table is created to make a primary

key unique, the _B (the base, non-translateable data) was added to the original table; for example, op_ordr_typ_b _INT: An interface table that holds the entries

being synchronized; for example,op_cust_mst_int

_ALL: For multiple organizations to show results for alloperating units; for example, ap_invoices_all

Some new extensions to basic table names are: _TL: Translation involved; for example,

op_text_tbl_tl _VL: MLS view _WK: Temporary work table, as in indented bills of

material (BOMs) _B: When a new table is created to make a primary

key unique, the _B (the base, non-translateable data) was added to the original table; for example, op_ordr_typ_b _INT: An interface table that holds the entries

being synchronized; for example,op_cust_mst_int

_ALL: For multiple organizations to show results for alloperating units; for example, ap_invoices_all

Table Attributes: OPM TablesIn Oracle Applications 11i, your system must be appropriate for multipleorganizations.



Table Attributes


Table AttributesTable Attributes

In addition, all tables contain the columns: CREATED_BY

CREATION_DATE LAST_UPDATED_BY

LAST_UPDATE_LOGIN

LAST_UPDATE_DATE

These are called Who columns, and they provideinformation to the user.Help > About This Record on any OPM form.

In addition, all tables contain the columns: CREATED_BY

CREATION_DATE LAST_UPDATED_BY

LAST_UPDATE_LOGIN

LAST_UPDATE_DATE

These are called Who columns, and they provideinformation to the user.Help > About This Record on any OPM form.

Table AttributesWhen signed on to an application form with a record retrieved, you can accesswho and when information by using the path Help > About This Record.



Table Attributes



Tables involved in concurrent processing contain thefollowing columns: PROGRAM_APPLICATION_ID

PROGRAM_ID

PROGRAM_UPDATE_DATE

REQUEST_ID

Tables involved in concurrent processing contain thefollowing columns: PROGRAM_APPLICATION_ID

PROGRAM_ID

PROGRAM_UPDATE_DATE

REQUEST_ID

Table Attributes (continued)When a batch approach is used to add or modify table rows, the who andwhen information captured is for the batch process and the requestor.



Table Attributes



Many tables also contain the columns: TEXT_CODE

DELETE_MARK

TRANS_COUNT

Many tables also contain the columns: TEXT_CODE

DELETE_MARK

TRANS_COUNT

Table Attributes (continued)TEXT_CODE references text associated with a row.DELETE_MARK indicates that the row is marked for delete but has not beenphysically deleted.TRANS_COUNT records the number of updates to a row.



Table Attributes: Text_Code


Table Attributes: Text_CodeTable Attributes: Text_Code

TEXT_CODE

Links individual rows to central text tables definedby module. For example, IC_TEXT_TBL_TL is fortext in the Inventory Control module.

A numeric sequence generated by the system. To associate text with an item definition, the item

would be stored in IC_ITEM_MST, the text inIC_TEXT_TBL, with the tables joined by theTEXT_CODE column.

TEXT_CODE

Links individual rows to central text tables definedby module. For example, IC_TEXT_TBL_TL is fortext in the Inventory Control module.

A numeric sequence generated by the system. To associate text with an item definition, the item

would be stored in IC_ITEM_MST, the text inIC_TEXT_TBL, with the tables joined by theTEXT_CODE column.



Table Attributes: Delete_Mark


Table Attributes: Delete_MarkTable Attributes: Delete_Mark

OPM deletes rows logically rather than physically:Each table contains a column named DELETE_MARK. 0 (default value) = not deleted 1 = deleted 1 created by using Mark for Purge accessed from

the OPM Action menuUsers will not see these rows in OPM sessions unlessthe precise key values are typed.OPM also provides an Unmark for Purge function.

OPM deletes rows logically rather than physically:Each table contains a column named DELETE_MARK. 0 (default value) = not deleted 1 = deleted 1 created by using Mark for Purge accessed from

the OPM Action menuUsers will not see these rows in OPM sessions unlessthe precise key values are typed.OPM also provides an Unmark for Purge function.



Primary Keys


Primary KeysPrimary Keys

OPM utilizes both primary keys and indexes. A primary key is one or more columns in a table

that combine to make each row unique.

OPM utilizes both primary keys and indexes. A primary key is one or more columns in a table

that combine to make each row unique.

Primary KeysWhen first designed, relational databases did not use indexes. Performanceconsiderations, especially in very large databases, dictated the use of indexes toachieve acceptable response.A primary key ensures that there are no duplicate rows in a table with the samebasic identifiers. For example, if a sales order has two lines with the same itemordered, the primary key needs a distinctive value, which in this case isline_id not line_no.



Primary Keys


Primary KeysPrimary Keys

Primary keys ensure unique values in each table. IC_ITEM_MST_PK = ITEM_ID

This keeps item_id unique throughout thedatabase.

SY_ADDR_MST_PK = ADDR_ID

This keeps each address unique to avoidduplicates.

Primary keys ensure unique values in each table. IC_ITEM_MST_PK = ITEM_ID

This keeps item_id unique throughout thedatabase.

SY_ADDR_MST_PK = ADDR_ID

This keeps each address unique to avoidduplicates.

Primary Keys (continued)The very definition of a primary key is that it must be unique. This is validatedby the database.



Indexes


IndexesIndexes

An index is one or more columns from a table, butan index does not have to be unique.

Indexes often consist of surrogate columns whichmay be foreign keys.

An index is one or more columns from a table, butan index does not have to be unique.

Indexes often consist of surrogate columns whichmay be foreign keys.



Foreign Keys


Foreign KeysForeign Keys

Foreign keys ensure referential integrity at the databaselevel, instead of just adding them through the code.

Examples of foreign key relationships: SY_UOMS_MST_SY_UOMS_TYP_FK1 (UM_TYPE) IC_ITEM_CNV_SY_UOMS_TYP_FK (UM_TYPE) IC_ITEM_MST_SY_UOMS_MST_FK1 (ITEM_UM) IC_ITEM_MST_SY_UOMS_MST_FK2 (ITEM_UM2)

Foreign keys ensure referential integrity at the databaselevel, instead of just adding them through the code.

Examples of foreign key relationships: SY_UOMS_MST_SY_UOMS_TYP_FK1 (UM_TYPE) IC_ITEM_CNV_SY_UOMS_TYP_FK (UM_TYPE) IC_ITEM_MST_SY_UOMS_MST_FK1 (ITEM_UM) IC_ITEM_MST_SY_UOMS_MST_FK2 (ITEM_UM2)

Foreign KeysThe last two rows above are for two different references from ic_item_mstto sy_uoms_mst, because with dual units of measure, one item uses twodifferent units of measure.



Surrogate IDs


Surrogate IDsSurrogate IDs

A surrogate is an ID or identifier column used byOPM to: Join header and detail tables Enhance database search performance (for

example, formula_id).An OPM table may use IDs from other tables (forexample, item_id) to comprise an index. In thesecases, there is a foreign reference to another table.

A surrogate is an ID or identifier column used byOPM to: Join header and detail tables Enhance database search performance (for

example, formula_id).An OPM table may use IDs from other tables (forexample, item_id) to comprise an index. In thesecases, there is a foreign reference to another table.

Surrogate IDsThe term surrogate means a substitute for something else. For example, a lotnumber or lot number/sublot number combination can be represented bylot_id, which is a system assigned number. When a sales order line isallocated to a specific lot/sublot, then lot_id is stored in the transaction,which allocates the lot to the line.



Surrogate IDs


Surrogate IDsSurrogate IDs

Surrogate IDs are controlled by defining them asstandard Oracle sequences.Example:You add a new formula to OPM. Because there is aformula_id column that is defined as a sequence,the next available number is returned making the IDunique.

Surrogate IDs are controlled by defining them asstandard Oracle sequences.Example:You add a new formula to OPM. Because there is aformula_id column that is defined as a sequence,the next available number is returned making the IDunique.

Surrogate IDs (continued)If a batch process adds a row to a table controlled by a sequence, a call must bemade to a routine to get the next sequence value to store in the new row.



Sequences


SequencesSequences

GEM5_CRITERIA_ID_S GEM5_CYCLE_ID_S GEM5_CYCL_ADT_ID_S GEM5_CYCL_MSC_ID_S GEM5_DOC_ID_S GEM5_ITEM_CDT_ID_S GEM5_ITEM_ID_S

GEM5_CRITERIA_ID_S GEM5_CYCLE_ID_S GEM5_CYCL_ADT_ID_S GEM5_CYCL_MSC_ID_S GEM5_DOC_ID_S GEM5_ITEM_CDT_ID_S GEM5_ITEM_ID_S

GEM5_LINE_ID_S GEM5_LOT_ID_S GEM5_PLNTINV_ID_S GEM5_POSTING_ID_S GEM5_PURGE_ID_S GEM5_SUMM_INV_ID_S GEM5_TRANS_ID_S

GEM5_LINE_ID_S GEM5_LOT_ID_S GEM5_PLNTINV_ID_S GEM5_POSTING_ID_S GEM5_PURGE_ID_S GEM5_SUMM_INV_ID_S GEM5_TRANS_ID_S

Syntax: select sequence_name.nextval fromsys.dual;Syntax: select sequence_name.nextval fromsys.dual;



Stored Procedures, Views, and Triggers


Stored Procedures, Views, and TriggersStored Procedures, Views, and Triggers

Packages and procedures Views TriggersStored code and OPM views are installed and ownedby the APPS user. The application accesses objectsowned by other application schemas, so referencescan be resolved at compile or run time.No matter which applications the customer haspurchased, the entire database is always installed.

Packages and procedures Views TriggersStored code and OPM views are installed and ownedby the APPS user. The application accesses objectsowned by other application schemas, so referencescan be resolved at compile or run time.No matter which applications the customer haspurchased, the entire database is always installed.



Null Columns


Null ColumnsNull Columns

If a column is defined as NOT NULL, some valuemust be stored in the column.

This can lead to scenarios in which zeros andblank spaces are stored in columns. Therefore, with foreign keys, and a primary key

defined for every OPM table, these types ofvalues cannot be stored according to datamodelling standards.

Thus, columns that store optional values aredefined as NULL (allowing Null values).

If a column is defined as NOT NULL, some valuemust be stored in the column.

This can lead to scenarios in which zeros andblank spaces are stored in columns. Therefore, with foreign keys, and a primary key

defined for every OPM table, these types ofvalues cannot be stored according to datamodelling standards.

Thus, columns that store optional values aredefined as NULL (allowing Null values).

Null ColumnsThe primary impact of null values is to reduce storage and to facilitate writingretrieval code such as SQL*Plus.



Multilanguage Support (MLS)


Multilanguage Support (MLS)Multilanguage Support (MLS)

OP_PRSL_TYP_B OP_PRSL_TYP_TL

OP_PRSL_TYP_VL

OP_PRSL_TYP



Multilanguage Support


Multilanguage SupportMultilanguage Support

The _VL table is the view to the _B (Base) and _TL(Translation) tables

The synonym is the table name that the user sees To SELECT from a table, the results are from the

_VL

To UPDATE, DELETE, or INSERT in a table: The _VL table reads the command. The _VL table fires a trigger called a

table_handler. The _B and/or _TL tables are modified.

The _VL table is the view to the _B (Base) and _TL(Translation) tables

The synonym is the table name that the user sees To SELECT from a table, the results are from the

_VL

To UPDATE, DELETE, or INSERT in a table: The _VL table reads the command. The _VL table fires a trigger called a

table_handler. The _B and/or _TL tables are modified.



Reading a Technical Reference Manual (TRM)


Reading a Technical Reference Manual(TRM)

Reading a Technical Reference Manual(TRM)



Reading a TRM


Reading a TRMReading a TRM

A TRM shows table details including: Foreign keys Table column definitions Indexes Sequences

A TRM shows table details including: Foreign keys Table column definitions Indexes Sequences

Reading a Technical Reference ManualPrimary keys are indicated in the Column Definitions, as well as in the Indexsection.



Reading a TRM



Foreign keys detail: The table on which the key is primary The primary column name The associated foreign key name

Foreign keys detail: The table on which the key is primary The primary column name The associated foreign key name



Reading a TRM



Column descriptions detail: Each column that is found in the table The name, Null/Not Null, type/format, and

description for each column Standard Who columns Descriptive Flexfield columns Any valid values that can be set in the column

Column descriptions detail: Each column that is found in the table The name, Null/Not Null, type/format, and

description for each column Standard Who columns Descriptive Flexfield columns Any valid values that can be set in the column



Reading a TRM



Indexes detail: The index name The index type and sequence The column name for the index

Indexes detail: The index name The index type and sequence The column name for the index



Reading a TRM



Sequences detail: The name of the sequence The column for which the sequence was derived

Sequences detail: The name of the sequence The column for which the sequence was derived



Summary


SummarySummary

In this lesson, you should have learned how to: Demonstrate a working knowledge of overall

schemas Define naming conventions List common table characteristics Describe database features used in controls Use a technical reference manual

In this lesson, you should have learned how to: Demonstrate a working knowledge of overall

schemas Define naming conventions List common table characteristics Describe database features used in controls Use a technical reference manual


System SetupChapter 3 - Page 1

System SetupChapter 3



System Setup


System SetupSystem Setup



Objectives



After completing this lesson, you should be able todo the following: List the overall structure of the database Name primary system support tables Define the OPM Financials setup

After completing this lesson, you should be able todo the following: List the overall structure of the database Name primary system support tables Define the OPM Financials setup



Essential System Setup


Essential System SetupEssential System Setup

Define users

Document ordering Assign organizations to users

Set profile values

Define the organization structure



System Administrative Module Tables


System Administrative Module TablesSystem Administrative Module Tables

Unit of measure Miscellaneous Unit of measure Miscellaneous

Organization Text

SY_UOMS_MSTSY_UOMS_STDSY_UOMS_TYP

SY_GEOG_MSTSY_DOCS_MSTSY_DOCS_SEQ

*HR_ORGANIZATION_UNITS_VLSY_ORGN_MSTSY_ORGN_USR

SY_ADDR_MSTSY_PARA_CDS_TLSY_TEXT_HDRSY_TEXT_TBL_TL

System Administrative Module Tables All addresses for all modules are in the SY Address Master. Once you have defined paragraphs, and entered text into them, the text is

stored in the SY_Text table. Document ordering determines whether a number is set manually or

automatically.



System Administrative Relationships


System Administrative RelationshipsSystem Administrative Relationships

HR_ORGANIZATIONS_UNITS_VLorganization_id

FND_USERuser_id

SY_ORGN_MSTorgn_code

PS_OPER_PCLplanning_class

SY_ORGN_USRuser_id,orgn_code

System Administrative Relationships The table is now required, but only needs the user ID plugged in. This diagram involves tables from four different modules.



Common Modules Interface


Common Modules Interface

Receiving Sales Order

Production Management

AccountsPayable

AccountsReceivableOracleOracle

ApplicationApplicationModulesModules

OPMOPMModulesModules

Purchasing

General ledgerGeneral ledger

InventoryManagement



Data Synchronized to OPM


Data Synchronized to OPMData Synchronized to OPM

Accounts Payable (AP) Freight on Board (FOB) codesAccounts Payabke (AP) TermsSalesrepsCustomersVendorsInvoice Price (only used in Actual Costing)

Oracle Tables OPM Tables



Data Synchronized from OPM


Data Synchronized from OPMData Synchronized from OPM

Accounts Receivable (AR) Update General Ledger (GL) Update




AP FOB Codes


AP FOB CodesAP FOB Codes

Oracle TableOracle Table OPM TableOPM Table

OPM Immediate Interfaceor

OPM Periodic Interfacemonthly, weekly, daily, hourly, by minute

PO_LOOKUP_CODES OP_FOBC_MST



FOB Code Field Mapping


FOB Code Field MappingFOB Code Field Mapping

FOB Codes Accounts Receivable Lookups Purchase Order Lookups

FOB Codes Accounts Receivable Lookups Purchase Order Lookups



FOB Code Field Mapping


FOB Code Field MappingFOB Code Field Mapping

FOB Codes

AR_LOOKUPS PO_LOOKUP_CODESlookup_code lookup_codelookup_type lookup_typedescription description

PO_LOOKUPS OP_FOBC_MSTlookup_code fob_codedescription fob_name



AP Invoice Terms


AP Invoice TermsAP Invoice Terms




OP_TERM_MSTAP_TERMS_LINES

AP_TERMS



AP Terms Field Mapping


AP Terms Field MappingAP Terms Field Mapping

AP_TERMS OP_TERM_MSTname terms_codedescription terms_desc

AP_TERMS_LINESdiscount_percent discount_ratediscount_days discount_daysdue_days net_days



Salesreps


OP_SLSR_MST

SalesrepsSalesreps



Oracle TableOracle Table OPM TablesOPM Tables

RA_SALESREPSOP_SLSR_MST_INT



Salesrep Field Mapping


Salesrep Field MappingSalesrep Field Mapping

Sales Reps

RA_SALESREPS OP_SLSR_MSTname slsrep_codename slsrep_name



Customers


AP_BANK_ACCOUNTS

AR_CUSTOMER_PROFILES

RA_TERRIRTORIES

RA_CONTACTS

RA_PHONES

RA_SITE_USES

SY_ADDR_MST

RA_CUSTOMERS

OP_CUST_MST_INT

OP_CUST_MSTRA_ADDRESSES

CustomersCustomers



Oracle TablesOracle Tables OPM TableOPM Table



Customer Field Mapping


Customer Field MappingCustomer Field MappingCustomers

RA_CUSTOMERS OP_CUST_MSTcustomer_name cust_namecustomer_number cust_no

RA_SITE_USESlocation cust_nosite_use_code bill_ind, ship_indship_partial backorder_indfob_point fob_codeship_via frtbill_mthdtax_code taxloc_codestatus inactive_ind

RA_ADDRESSES SY_ADDR_MSTaddress1 addr1address2 addr2address3 addr3city addr4state state_codepostal_code postal_codecountry country_code



Vendors


VendorsVendors




PO_VENDOR_SITES

PO_VENDORS

SY_ADDR_MST

PO_VEND_MST



Vendor Field Mapping


Vendor Field MappingVendor Field MappingVendors

PO_VENDORS PO_VEND_MSTvendor_name vendor_namesegment1 vendor_no

PO_VENDOR_SITESvendor_site_code vendor_nopurchasing_site_flag ship_indpay_site_flag payment_ind

SY_ADDR_MSTaddress_line1 addr1address_line2 addr2address_line3 addr3city addr4state state_codecountry country_codezip postal_code



Data Triggered to OPM


Data Triggered to OPMData Triggered to OPM

Currency CodesExchange Rate TypeExchange Rate




Data Triggered Over from OPM


Data Triggered Over from OPMData Triggered Over from OPM


ItemItem/Lot ConversionUOM TypeUOMUOM Conversion



Currency Codes


Currency CodesCurrency Codes

Trigger


FND_CURRIENCIES GL_CURR_MST



Currency Code Field Mapping


Currency Code Field MappingCurrency Code Field Mapping

Currencies

FND_CURRENCIES GL_CURR_MSTcurrency_code currency_codename currency_descriptionprecision decimal_precision



Exchange Rate Types


Exchange Rate TypesExchange Rate Types

Trigger


GL_DAILY_CONVERSION_TYPES

GL_RATE_TYP



Exchange Rate Type Field Mapping


Exchange Rate Type Field MappingExchange Rate Type Field Mapping

Exchange Rate Types

GL_DAILY_CONVERSION_TYPES GL_RATE_TYPEconversion_type rate_type_codedescription rate_type_description



Exchange Rates


Exchange RatesExchange Rates

Trigger

Oracle TableOracle Table OPM TablesOPM TablesGL_DAILY_CONVERSION_RATES

GL_XCHG_RTE




Exchange Rate Field Mapping


Exchange Rate Field MappingExchange Rate Field Mapping

Exchange Rates

GL_DAILY_CONVERSION_RATES GL_XCHG_RTEfrom_currency_code from_currency_codeconversion_date exchange_rate_dateconversion_rate exchange_rateconversion_type rate_type_code

GL_SETS_OF_BOOKScurrency_code to_currency_code



OPM UOM Types


OPM UOM TypesOPM UOM Types

Trigger


MTL_UOM_CLASSES SY_UOMS_TYP



UOM Type Field Mapping


UOM Type Field MappingUOM Type Field Mapping

Unit of Measure Types

MTL_UOM_CLASSES SY_UOMS_TYPuom_class um_typedescription type_desc



OPM UOM


OPM UOMOPM UOM

Trigger


MTL_UNITS_OF_MEASURE

SY_UOMS_MST



OPM UOM Conversions


OPM UOM ConversionsOPM UOM Conversions

Trigger


MTL_UOM_CONVERSIONS SY_UOMS_MST



Unit of Measure Field Mapping


Unit of Measure Field MappingUnit of Measure Field Mapping

Units of Measure

MTL_UNITS_OF_MEASURE SY_UOMS_MSTuom_code um_codeunit_of_measure um_descuom_class um_typeMTL_UOM_CONVERSIONSuom_code um_codeunit_of_measure um_descuom_class um_typeconversion_rate std_factor



OPM Inventory to Oracle Inventory


OPM Inventory toOracle Inventory

OPM Inventory toOracle Inventory

Trigger

OPM TableOPM Table Oracle TablesOracle Tables

IC_ITEM_MST

MTL_ITEM_CATEGORIES

MTL_SYSTEM_ITEMS



Item Field Mapping


Item Field MappingItem Field Mapping

Items

MTL_SYSTEM_ITEMS IC_ITEM_MSTsegment1 item_nodescription item_desc1primary_uom_code item_um



OPM Item/Lot Conversions


OPM Item/Lot ConversionsOPM Item/Lot Conversions

Trigger


MTL_UOM_CLASS_CONVERSIONS

IC_ITEM _CNV



Item/Lot Conversion


Item/Lot ConversionItem/Lot Conversion

Item/Lot Conversions: Interclass ConversionsMTL_UOM_CLASS_CONVERSIONS IC_ITEM_MSTinventory_item_id item_idfrom_uom_code item_umto_uom_code item_um2

IC_ITEM_CNVconversion_rate type_factorinventory_item_id item_id



Summary


SummarySummary

In this lesson, you should have learned how to: List the overall structure of the database Name primary system support tables Define the OPM Financials setup

In this lesson, you should have learned how to: List the overall structure of the database Name primary system support tables Define the OPM Financials setup


InventoryChapter 4 - Page 1

InventoryChapter 4



Inventory


InventoryInventory



Objectives



After completing this lesson, you should be able todo the following: Describe inventory relationships Relate inventory transactions to events that

caused them

After completing this lesson, you should be able todo the following: Describe inventory relationships Relate inventory transactions to events that

caused them



Inventory Management


Inventory ManagementInventory Management

Item

Warehouse

Location

Lot

Sublot

Status

Grade

Inventory ManagementAn inventory instance of an item is stored in a location (warehouse orwarehouse location):

May be lot controlled May be status controlled (good, bad, and so on) May be grade controlled (highest price, medium, and so on)



Inventory Module Tables


Inventory Module TablesInventory Module Tables

Inv Create/Adjust/Move Inv Status/Grade Inv Summary

Inv Create/Adjust/Move Inv Status/Grade Inv Summary

Items Warehouse/Location Lots

IC_LOTS_STS* QC_GRAD_MST

IC_SUMM_INVIC_PERD_BALIC_WHSE_STS

IC_ITEM_MSTIC_ITEM_CNV

IC_WHSE_MSTIC_LOCT_MSTIC_LOCT_INV

IC_JRNL_MSTIC_ADJS_JNLIC_TRAN_PNDIC_TRAN_CMPIC_TRAN_ARC

IC_TEXT_HDRIC_TEXT_TBL_TL



Inventory Relationships


Inventory RelationshipsInventory Relationships

Grade appliesGrade appliesto lotto lot

Status appliesStatus appliesto locationto location

IC_SUMM_INVitem_id, whse_code, qc_grade

IC_LOTS_MSTitem_id, lot_id

IC_LOCT_MSTwhse_code,location

IC_LOTS_STSlot_status

QC_GRAD_MSTqc_grade

IC_ITEM_MSTitem_id

IC_LOCT_INVitem_id, lot_id, whse_code, location

IC_WHSE_MSTwhse_code

Inventory Relationships IC_SUMM_INV contains totals of Items, Warehouse Codes, QC Grade,

and contains many more transactions totals. It is not summed from the detail.



Document Types


Document TypesDocument TypesAlways Completed CREICreate immediately ADJIAdjust immediately MOVIMove immediately STSIStatus immediately GRDIGrade immediately Mass versions of above (mult. tx) POSRPO Stock receipt RTRNPO return PICYPhysical Inventory Cycle

No PIPHPhysical Inventory

Physical

Always Completed CREICreate immediately ADJIAdjust immediately MOVIMove immediately STSIStatus immediately GRDIGrade immediately Mass versions of above (mult. tx) POSRPO Stock receipt RTRNPO return PICYPhysical Inventory Cycle

No PIPHPhysical Inventory

Physical

Begin as Pending PRODBatch OPSOSales Order OPSPShipment PORDPurchase

Order

Inventory Transfers XFER

Document Types The first column of document types are some of the ones that get totaled

on ic_summ_inv. These document types all involve inventory transactions that are recorded

in one of two different tables. The Always completed type go to the ic_tran_cmp table. The Begin as pending type start in the ic_tran_pnd table

The completed indicator is changed from 0 to 1 when it iscompleted.

Purging completed transactions will move them to the ic_tran_cmptable.



Pending and Completed Transactions


Pending and Completed TransactionsPending and Completed Transactions

Pending transactions may happen. Completed transactions have already happened. Table ic_tran_cmp only contains completed

transactions. Table ic_tran_pnd contains pending

transactions and transactions marked completed. Pending and completed transactions indicate the

documents which produced the transactions.

Pending transactions may happen. Completed transactions have already happened. Table ic_tran_cmp only contains completed

transactions. Table ic_tran_pnd contains pending

transactions and transactions marked completed. Pending and completed transactions indicate the

documents which produced the transactions.

Pending and Completed TransactionsA purging facility in OPM moves formerly pending transactions, whencompleted, from ic_tran_pnd to ic_tran_cmp to reduce the size ofic_tran_pnd. Depending on the nature of the clients business,ic_tran_pnd can grow rapidly and begin to impact performance adversely.



Inventory Setup Data


Inventory Setup DataInventory Setup Data

Setup information Items Item/Lot conversions Warehouse Location Lots/Sublots Classes/Types

Setup information Items Item/Lot conversions Warehouse Location Lots/Sublots Classes/Types

Inventory Tables

IC_ITEM_MST - Item Master TableIC_ITEM_CNV - Item/Lot Conversion TableIC_WHSE_MST - Warehouse Definition TableIC_LOCT_MST - Location MasterIC_LOTS_MST - Lot Master



Inventory Transactions


Inventory TransactionsInventory Transactions

Immediate or journaled transactions Mass or singular transactions

Create Adjust Move Grade Status

Immediate or journaled transactions Mass or singular transactions

Create Adjust Move Grade Status

Inventory Transaction Tables

IC_JRNL_MST - Journal MasterIC_ADJS_JNL - Journal Details

IC_TRAN_CMP - Completed Transaction TableIC_TRAN_PND - Pending/Completed Transaction TableIC_TRAN_ARC - Archived Transaction Table



Inventory Transactions


Inventory TransactionsInventory Transactions

Transaction sources Inventory transactions Purchase orders, receipts, and returns Sales orders and shipping Production batches

Pending and completed transactions

Transaction sources Inventory transactions Purchase orders, receipts, and returns Sales orders and shipping Production batches

Pending and completed transactions



Transaction Flow


Transaction FlowTransaction Flow

Inventory Journal TablesInventory Journal Tables Inventory TablesInventory Tables

IC_SUMM_INV

IC_JRNL_MST

IC_ADJS_JNL

IC_TRAN_CMP

IC_LOCT_INV



Pending to Completed Transactions


Pending to Completed TransactionsPending to Completed Transactions

Pending Transactions ic_tran_pnd

Completed Transactionsic_tran_cmp

Pending Transactions ic_tran_pnd

Completed Transactionsic_tran_cmp



Pending to Completed Transactions


Pending to Completed TransactionsPending to Completed Transactions

When you update a transaction from pending tocompleted, the pending transaction is updated to indicatethat it is no longer pending. The pending transactionbecomes a completed transaction, or a new completedtransaction is created.

Pending transactions with offsetting completed transactionsare stored in the Pending Transactions table ic_tran_pndwith a flag to indicate completed status. Completedtransactions created through Inventory > Quantities orPhysical Inventory > Count Entry are stored in a CompletedTransactions database table called ic_tran_cmp.



Physical Inventory


Physical InventoryPhysical Inventory

Counting of inventory Physical CountReplacement method Cycle CountVariance method Transaction-based systems

Counting of inventory Physical CountReplacement method Cycle CountVariance method Transaction-based systems

Physical Inventory Tables

IC_RANK_MST - ABC Rank TableIC_ITEM_CDT - Scheduled Cycle Count Date per Item/WhseIC_CYCL_MSC - Miscellaneous Cycle Count ItemsIC_CYCL_HDR - Cycle Count Definition TableIC_CYCL_DTL - Cycle Count Detail Table (Frozen Quantities)IC_PHYS_CNT - Physical/Cycle Count Results TableIC_CYCL_ADT - Cycle Audit Table



Physical Inventory Process Flow


Create ABC rank

IC_RANK_MST

Initialize ABC rank schedule

IC_ITEM_CDT

Definecycle count orphysical countIC_CYCL_HDRIC_PHYS_CNT

Addmiscellaneous

itemsIC_CYCL_MSC

Initiatecycle count

orphysical countIC_CYCL_DTL

Cycle countand

physical countentry

IC_PHYS_CNT

Run theaudit report

and populateIC_CYCL_ADT

(Cycle Counts Only)

Post resultsand createcompleted transactionIC_TRAN_CMP

Physical Inventory Process FlowPhysical Inventory Process Flow



Summary


SummarySummary

In this lesson, you should have learned how to: Describe inventory relationships Relate inventory transactions to events that

caused them

In this lesson, you should have learned how to: Describe inventory relationships Relate inventory transactions to events that

caused them


New Product DevelopmentChapter 5 - Page 1

New Product DevelopmentChapter 5



New Product Development


New Product DevelopmentNew Product Development



Objectives



After completing this lesson, you should be able todo the following: Describe the construction of a formula Explain routings Identify how to make correct versions and

combinations available for production

After completing this lesson, you should be able todo the following: Describe the construction of a formula Explain routings Identify how to make correct versions and

combinations available for production

ObjectivesIn this lesson, we will see how formulas, routings, and effectivities are stored.



Formulas


Formulas

Basis for making products

FinishedGood

RawMaterial 3

RawMaterial 2

RawMaterial 1

RawMaterial 4

PackageIntermediate

Formulas The formula describes the what aspects of products. Formulas work from the fm_form_mst and fm_matl_dtl tables. The line type set in the fm_form_mst table. This is differentiated as

1=product/coproduct; -1=ingredient; 2=byprod. The table fm_form_mst also contains the field phantom_type. The phantom_type can be Not a Phantom, Automatic, or Manual.



Routings


RoutingsRoutings

Transformation steps to make productsTransformation steps to make products

Blending Extrusion Pack Routing=+ +

Resources + Activities = Operations

Blender Run Blender Blending+ =

A Group of Operations = Routing

Routings The routing describes how the product is made. From a cost perspective, both the formula and routing (if used) are

important in determining cost of goods sold. There are multiple operations in a route. One of the operations could be a

test. A Formula + a Route = a Recipe.



Formula Module Tables


Formula Module TablesFormula Module Tables

Routings Routings Formulas Effectivities

FM_ROUT_HDRFM_ROUT_DTL

FM_ROUT_DEPFM_ACTV_MST* CR_RSRC_MSTFM_OPRN_MSTFM_OPRN_DTLFM_ROUT_MTL

FM_FORM_MSTFM_MATL_DTL

FM_FORM_EFF



Formula Relationships


Formula RelationshipsFormula Relationships

FM_FORM_MST#* Unique ID

FM_ROUT_HDR#* Unique ID

FM_MATL_DTL#* Unique ID

FM_FORM_EFF#* Unique ID

FM_ROUT_DTL#* Unique ID

FM_ROUT_DEP#* Unique ID

FM_ROUT_MTL#* Unique ID

Formula RelationshipsThe effectivity in the middle is what connects formula and routing. Becausecreation of a batch requires an effect

opm data modeling

Documents

oracle products

restricted rights software

restricted rights legenduse

technical data

federal law

object design

violation ofcopyright

department of defense