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
Copyright © Oracle Corporation, 2000. All rights reserved.
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
Copyright © Oracle Corporation, 2000. All rights reserved.
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
Copyright © Oracle Corporation, 2000. All rights reserved.
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 Can’t I See My PO in OPM? ......................................................................................8-24Why Can’t 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
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsiv
Regulatory Label Tables......................................................................................................10-10Summary..............................................................................................................................10-12
Copyright © Oracle Corporation, 2000. All rights reserved.
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data Modeling Release 11i Table of Contentsvi
Related Publications
Additional Publications
• System release bulletins
• Installation and user’s guides
• OPM Technical Reference Manuals
• read.me files
• Oracle Magazine
Copyright © Oracle Corporation, 2000. All rights reserved.
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 Can’t 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 component”and 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.
Copyright © Oracle Corporation, 2000. All rights reserved.
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
Copyright © Oracle Corporation, 2000. All rights reserved.
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data ModelingChapter 1 - Page 1
Oracle ProcessManufacturing Data ModelingChapter 1
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data ModelingChapter 1 - Page 2
Oracle Process Manufacturing Data Modeling
Copyright © Oracle Corporation, 2000. All rights reserved.®
Oracle Process Manufacturing DataModeling
Oracle Process Manufacturing DataModeling
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data ModelingChapter 1 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data ModelingChapter 1 - Page 4
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
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
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data ModelingChapter 1 - Page 5
Agenda
Copyright © Oracle Corporation, 2000. All rights reserved.®
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)
Copyright © Oracle Corporation, 2000. All rights reserved.
Oracle Process Manufacturing Data ModelingChapter 1 - Page 6
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 1
Database and Object DesignChapter 2
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 2
Database and Object Design
Copyright © Oracle Corporation, 2000. All rights reserved.®
Database and Object DesignDatabase and Object Design
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
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
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 4
Ten Schemas
Copyright © Oracle Corporation, 2000. All rights reserved.®
Ten SchemasTen Schemas
GMA—System Administration
GMD—Product Development
GME—Process Execution
GMF—Financials
GMI—Inventory Management
GML—Logistics
GMP—Process Planning
GR—Regulatory Management
GMW—OPM Portal
PMI—Process 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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 5
The APPS Schema
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 6
Table Attributes: OPM Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 7
Table Attributes: OPM Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 8
Table Attributes
Copyright © Oracle Corporation, 2000. All rights reserved.®
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 access“who” and “when” information by using the path Help > About This Record.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 9
Table Attributes
Copyright © Oracle Corporation, 2000. All rights reserved.®
Table AttributesTable 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” and“when” information captured is for the batch process and the requestor.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 10
Table Attributes
Copyright © Oracle Corporation, 2000. All rights reserved.®
Table AttributesTable 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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 11
Table Attributes: Text_Code
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 12
Table Attributes: Delete_Mark
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 13
Primary Keys
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 14
Primary Keys
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 15
Indexes
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 16
Foreign Keys
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 17
Surrogate IDs
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 18
Surrogate IDs
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 19
Sequences
Copyright © Oracle Corporation, 2000. All rights reserved.®
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;
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 20
Stored Procedures, Views, and Triggers
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 21
Null Columns
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 22
Multilanguage Support (MLS)
Copyright © Oracle Corporation, 2000. All rights reserved.®
Multilanguage Support (MLS)Multilanguage Support (MLS)
OP_PRSL_TYP_B OP_PRSL_TYP_TL
OP_PRSL_TYP_VL
OP_PRSL_TYP
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 23
Multilanguage Support
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 24
Reading a Technical Reference Manual (TRM)
Copyright © Oracle Corporation, 2000. All rights reserved.®
Reading a Technical Reference Manual(TRM)
Reading a Technical Reference Manual(TRM)
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 25
Reading a TRM
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 26
Reading a TRM
Copyright © Oracle Corporation, 2000. All rights reserved.®
Reading a TRMReading 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
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 27
Reading a TRM
Copyright © Oracle Corporation, 2000. All rights reserved.®
Reading a TRMReading 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
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 28
Reading a TRM
Copyright © Oracle Corporation, 2000. All rights reserved.®
Reading a TRMReading 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
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 29
Reading a TRM
Copyright © Oracle Corporation, 2000. All rights reserved.®
Reading a TRMReading 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
Copyright © Oracle Corporation, 2000. All rights reserved.
Database and Object DesignChapter 2 - Page 30
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 1
System SetupChapter 3
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 2
System Setup
Copyright © Oracle Corporation, 2000. All rights reserved.®
System SetupSystem Setup
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 4
Essential System Setup
Copyright © Oracle Corporation, 2000. All rights reserved.®
Essential System SetupEssential System Setup
Define users
Document ordering Assign organizations to users
Set profile values
Define the organization structure
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 5
System Administrative Module Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
System Administrative Module TablesSystem Administrative Module Tables
• Unit of measure• Miscellaneous• Unit of measure• Miscellaneous
• Organization• Text
SY_UOMS_MST
SY_UOMS_STD
SY_UOMS_TYP
SY_GEOG_MST
SY_DOCS_MST
SY_DOCS_SEQ
*HR_ORGANIZATION_UNITS_VL
SY_ORGN_MST
SY_ORGN_USR
SY_ADDR_MST
SY_PARA_CDS_TL
SY_TEXT_HDR
SY_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.
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 6
System Administrative Relationships
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 7
Common Modules Interface
Copyright © Oracle Corporation, 2000. All rights reserved.®
Common Modules Interface
Receiving Sales Order
Production Management
AccountsPayable
AccountsReceivableOracleOracle
ApplicationApplicationModulesModules
OPMOPMModulesModules
Purchasing
General ledgerGeneral ledger
InventoryManagement
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 8
Data Synchronized to OPM
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 9
Data Synchronized from OPM
Copyright © Oracle Corporation, 2000. All rights reserved.®
Data Synchronized from OPMData Synchronized from OPM
• Accounts Receivable (AR) Update• General Ledger (GL) Update
Oracle Tables OPM Tables
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 10
AP FOB Codes
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 11
FOB Code Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
FOB Code Field MappingFOB Code Field Mapping
FOB Codes• Accounts Receivable Lookups• Purchase Order Lookups
FOB Codes• Accounts Receivable Lookups• Purchase Order Lookups
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 12
FOB Code Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 13
AP Invoice Terms
Copyright © Oracle Corporation, 2000. All rights reserved.®
AP Invoice TermsAP Invoice Terms
OPM Immediate Interfaceor
OPM Periodic Interfacemonthly, weekly, daily, hourly, by minute
Oracle TableOracle Table OPM TableOPM Table
OP_TERM_MSTAP_TERMS_LINES
AP_TERMS
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 14
AP Terms Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 15
Salesreps
Copyright © Oracle Corporation, 2000. All rights reserved.®
OP_SLSR_MST
SalesrepsSalesreps
OPM Immediate Interfaceor
OPM Periodic Interfacemonthly, weekly, daily, hourly, by minute
Oracle TableOracle Table OPM TablesOPM Tables
RA_SALESREPSOP_SLSR_MST_INT
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 16
Salesrep Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
Salesrep Field MappingSalesrep Field Mapping
Sales Reps
RA_SALESREPS OP_SLSR_MSTname slsrep_codename slsrep_name
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 17
Customers
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
OPM Immediate Interfaceor
OPM Periodic Interfacemonthly, weekly, daily, hourly, by minute
Oracle TablesOracle Tables OPM TableOPM Table
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 18
Customer Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 19
Vendors
Copyright © Oracle Corporation, 2000. All rights reserved.®
VendorsVendors
OPM Immediate Interfaceor
OPM Periodic Interfacemonthly, weekly, daily, hourly, by minute
Oracle TablesOracle Tables OPM TableOPM Table
PO_VENDOR_SITES
PO_VENDORS
SY_ADDR_MST
PO_VEND_MST
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 20
Vendor Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 21
Data Triggered to OPM
Copyright © Oracle Corporation, 2000. All rights reserved.®
Data Triggered to OPMData Triggered to OPM
Currency CodesExchange Rate TypeExchange Rate
Oracle Tables OPM Tables
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 22
Data Triggered Over from OPM
Copyright © Oracle Corporation, 2000. All rights reserved.®
Data Triggered Over from OPMData Triggered Over from OPM
Oracle Tables OPM Tables
ItemItem/Lot ConversionUOM TypeUOMUOM Conversion
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 23
Currency Codes
Copyright © Oracle Corporation, 2000. All rights reserved.®
Currency CodesCurrency Codes
Trigger
Oracle TableOracle Table OPM TablesOPM Tables
FND_CURRIENCIES GL_CURR_MST
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 24
Currency Code Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
Currency Code Field MappingCurrency Code Field Mapping
Currencies
FND_CURRENCIES GL_CURR_MSTcurrency_code currency_codename currency_descriptionprecision decimal_precision
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 25
Exchange Rate Types
Copyright © Oracle Corporation, 2000. All rights reserved.®
Exchange Rate TypesExchange Rate Types
Trigger
Oracle TableOracle Table OPM TablesOPM Tables
GL_DAILY_CONVERSION_TYPES
GL_RATE_TYP
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 26
Exchange Rate Type Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 27
Exchange Rates
Copyright © Oracle Corporation, 2000. All rights reserved.®
Exchange RatesExchange Rates
Trigger
Oracle TableOracle Table OPM TablesOPM TablesGL_DAILY_CONVERSION_RATES
GL_XCHG_RTE
Oracle TableOracle Table OPM TableOPM Table
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 28
Exchange Rate Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 29
OPM UOM Types
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM UOM TypesOPM UOM Types
Trigger
Oracle TableOracle Table OPM TableOPM Table
MTL_UOM_CLASSES SY_UOMS_TYP
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 30
UOM Type Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
UOM Type Field MappingUOM Type Field Mapping
Unit of Measure Types
MTL_UOM_CLASSES SY_UOMS_TYPuom_class um_typedescription type_desc
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 31
OPM UOM
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM UOMOPM UOM
Trigger
Oracle TableOracle Table OPM TableOPM Table
MTL_UNITS_OF_MEASURE
SY_UOMS_MST
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 32
OPM UOM Conversions
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM UOM ConversionsOPM UOM Conversions
Trigger
Oracle TablesOracle Tables OPM TableOPM Table
MTL_UOM_CONVERSIONS SY_UOMS_MST
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 33
Unit of Measure Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 34
OPM Inventory to Oracle Inventory
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM Inventory toOracle Inventory
OPM Inventory toOracle Inventory
Trigger
OPM TableOPM Table Oracle TablesOracle Tables
IC_ITEM_MST
MTL_ITEM_CATEGORIES
MTL_SYSTEM_ITEMS
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 35
Item Field Mapping
Copyright © Oracle Corporation, 2000. All rights reserved.®
Item Field MappingItem Field Mapping
Items
MTL_SYSTEM_ITEMS IC_ITEM_MSTsegment1 item_nodescription item_desc1primary_uom_code item_um
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 36
OPM Item/Lot Conversions
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM Item/Lot ConversionsOPM Item/Lot Conversions
Trigger
Oracle TableOracle Table OPM TableOPM Table
MTL_UOM_CLASS_CONVERSIONS
IC_ITEM _CNV
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 37
Item/Lot Conversion
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
System SetupChapter 3 - Page 38
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 1
InventoryChapter 4
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 2
Inventory
Copyright © Oracle Corporation, 2000. All rights reserved.®
InventoryInventory
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 4
Inventory Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
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)
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 5
Inventory Module Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
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_INV
IC_PERD_BAL
IC_WHSE_STS
IC_ITEM_MST
IC_ITEM_CNV
IC_WHSE_MST
IC_LOCT_MST
IC_LOCT_INV
IC_JRNL_MST
IC_ADJS_JNL
IC_TRAN_PND
IC_TRAN_CMP
IC_TRAN_ARC
IC_TEXT_HDR
IC_TEXT_TBL_TL
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 6
Inventory Relationships
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 7
Document Types
Copyright © Oracle Corporation, 2000. All rights reserved.®
Document TypesDocument TypesAlways Completed• CREI—Create immediately• ADJI—Adjust immediately• MOVI—Move immediately• STSI—Status immediately• GRDI—Grade immediately• Mass versions of above (mult. tx)• POSR—PO Stock receipt• RTRN—PO return• PICY—Physical Inventory Cycle
No• PIPH—Physical Inventory
Physical
Always Completed• CREI—Create immediately• ADJI—Adjust immediately• MOVI—Move immediately• STSI—Status immediately• GRDI—Grade immediately• Mass versions of above (mult. tx)• POSR—PO Stock receipt• RTRN—PO return• PICY—Physical Inventory Cycle
No• PIPH—Physical Inventory
Physical
Begin as Pending• PROD—Batch• OPSO—Sales Order• OPSP—Shipment• PORD—Purchase
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 8
Pending and Completed Transactions
Copyright © Oracle Corporation, 2000. All rights reserved.®
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 client’s business,ic_tran_pnd can grow rapidly and begin to impact performance adversely.
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 9
Inventory Setup Data
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 10
Inventory Transactions
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 11
Inventory Transactions
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 12
Transaction Flow
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 13
Pending to Completed Transactions
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 14
Pending to Completed Transactions
Copyright © Oracle Corporation, 2000. All rights reserved.®
Pending to Completed TransactionsPending to Completed Transactions
When you update a transaction from “pending” to“completed,” 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.
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 15
Physical Inventory
Copyright © Oracle Corporation, 2000. All rights reserved.®
Physical InventoryPhysical Inventory
• Counting of inventory• Physical Count—Replacement method• Cycle Count—Variance method• Transaction-based systems
• Counting of inventory• Physical Count—Replacement method• Cycle Count—Variance 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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 16
Physical Inventory Process Flow
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 17
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
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
Copyright © Oracle Corporation, 2000. All rights reserved.
InventoryChapter 4 - Page 18
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 1
New Product DevelopmentChapter 5
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 2
New Product Development
Copyright © Oracle Corporation, 2000. All rights reserved.®
New Product DevelopmentNew Product Development
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 4
Formulas
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 5
Routings
Copyright © Oracle Corporation, 2000. All rights reserved.®
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.
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 6
Formula Module Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Formula Module TablesFormula Module Tables
• Routings• Routings• Formulas• Effectivities
FM_ROUT_HDR
FM_ROUT_DTL
FM_ROUT_DEP
FM_ACTV_MST
* CR_RSRC_MST
FM_OPRN_MST
FM_OPRN_DTL
FM_ROUT_MTL
FM_FORM_MST
FM_MATL_DTL
FM_FORM_EFF
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 7
Formula Relationships
Copyright © Oracle Corporation, 2000. All rights reserved.®
Formula RelationshipsFormula Relationships
FM_FORM_MST
#* Unique IDFM_ROUT_HDR
#* Unique ID
FM_MATL_DTL
#* Unique IDFM_FORM_EFF
#* Unique IDFM_ROUT_DTL
#* Unique ID
FM_ROUT_DEP
#* Unique IDFM_ROUT_MTL
#* Unique ID
Formula RelationshipsThe effectivity in the middle is what connects formula and routing. Becausecreation of a batch requires an effectivity, the batch must derive both formula(what?) and the routing (how?) in generating rows for the batch.
The formula table relation (mst_dtl) appears simple. However, ingredientrows in fm_matl_dtl can represent items that have their own formula. If aningredient indicates that it is a phantom, then, depending on setup, creating abatch can cause generation of multiple batches.
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 8
Formula/Effectivity Structure
Copyright © Oracle Corporation, 2000. All rights reserved.®
Formula/Effectivity StructureFormula/Effectivity Structure
Production FormulaFM_FORM_MSTFM_FORM_DTL
Route
Lab FormulaLM_FORM_HDRLM_FORM_DTLLM_FORM_DAT
Batch
Effectivity
Upload to ProductionUpload to Production
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 9
Laboratory Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
Laboratory ManagementLaboratory Management
• Technical parameters define the attribute(chemical property) of an item (density, pH)
• Technical parameters are defined in theLM_TECH_HDR, LM_TECH_DTL, and LM_ITEM_DATtables.
• They are set up in a sequence and then tied to theitem.
• Technical parameters define the attribute(chemical property) of an item (density, pH)
• Technical parameters are defined in theLM_TECH_HDR, LM_TECH_DTL, and LM_ITEM_DATtables.
• They are set up in a sequence and then tied to theitem.
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 10
Laboratory Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
Laboratory ManagementLaboratory Management
• The Lab Spreadsheet is based on four tables:– LM_SPRD_DTL
– LM_SPRD_FLS
– LM_SPRD_PRM
– LM_SPRD_TEC
• Item-specific technical parameters are entered intothe spreadsheet and then manipulated.
• Once the numbers are modified, the spreadsheetdetails any cost change or attribute changes.
• The Lab Spreadsheet is based on four tables:– LM_SPRD_DTL
– LM_SPRD_FLS
– LM_SPRD_PRM
– LM_SPRD_TEC
• Item-specific technical parameters are entered intothe spreadsheet and then manipulated.
• Once the numbers are modified, the spreadsheetdetails any cost change or attribute changes.
Laboratory Management• LM_SPRD_DTL: Table used to store Laboratory Spreadsheet detail
information• LM_SPRD_FLS: This table records the files in which a user has saved
Laboratory Spreadsheets.• LM_SPRD_PRM: Table used to store the technical parameter definitions
that belong with the spreadsheet• LM_SPRD_TEC: Table used to store the values of the technical
parameters on the spreadsheet
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 11
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
SummarySummary
In this lesson, you should have learned how to:• Describe the construction of a formula• Explain routings• Identify how to make correct versions and
combinations available for production
In this lesson, you should have learned how to:• Describe the construction of a formula• Explain routings• Identify how to make correct versions and
combinations available for production
Copyright © Oracle Corporation, 2000. All rights reserved.
New Product DevelopmentChapter 5 - Page 12
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 1
Quality ManagementChapter 6
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 2
Quality Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
Quality ManagementQuality Management
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
After completing this lesson, you should be able toexplain the Quality Workflows and the related tables.After completing this lesson, you should be able toexplain the Quality Workflows and the related tables.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 4
Oracle Workflow: Overview
Copyright © Oracle Corporation, 2000. All rights reserved.®
Oracle Workflow: OverviewOracle Workflow: Overview
By using Oracle Workflow, you can route informationaccording to a set of business rules.By using Oracle Workflow, you can route informationaccording to a set of business rules.
Workflow Processes DescriptionA workflow is a process containing several steps that include activities, roles,and decisions that are needed to complete a business process.With Oracle Workflow, you can automate and continuously improve businessprocesses by routing information according to a set of business rules. Thisinformation can be transmitted to individuals both inside and outside yourenterprise on a need-to-know basis.Oracle Workflow enables you to let people receive notifications of itemsawaiting their attention through electronic mail, using a Web browser, or usingthe Notification Summary window in Oracle Applications.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 5
Sample Approval Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Sample Approval WorkflowSample Approval Workflow
The sample approval workflow is composed of threesubordinate workflows:• Sample creation notification workflow• Assay testing process workflow• Sample disposition workflow
The sample approval workflow is composed of threesubordinate workflows:• Sample creation notification workflow• Assay testing process workflow• Sample disposition workflow
OPM Quality Sample Subordinate WorkflowsThe OPM Quality Sample Workflow consists of three subordinate workflows:
• Sample Creation Notification Workflow: This workflow sends anotification and initiates the Sample Approval Process Workflow.
• Sample Approval Process Workflow: This workflow is used to find assayspecifications, initiate the Assay Testing Process Workflow, and sendsinventory status notification.
• Assay Testing Process Workflow: This workflow is used to update assaystatus and accumulate assay results for the Sample Approval ProcessWorkflow.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 6
OPM Quality Views
Copyright © Oracle Corporation, 2000. All rights reserved.®
QC_SPEC_MSTQC_SPEC_MST
qcqc_spec_id_spec_id
OPM Quality ViewsOPM Quality Views
QC_ASSY_VALQC_ASSY_VAL
qcassyqcassy__valval_id_id
QC_ASSY_TYPQC_ASSY_TYP
qcassyqcassy__typtyp_id_id
QC_SMPL_MSTQC_SMPL_MST
sample_idsample_id
*1
item_id
lot_id
whse_code
location
*2
orgn_id
batch_id
formula_id
formulaline_id
routing_id
routingstep_id
opm_id
*3
item_id
vendor_id
cust_id
sample_no
sample_desc
*1, *2, *3
qc_spec_id
sample_id
assay_code
test_result
final mark
*1, *2, *3
qcassy_typ_id
assay_code
text_spec
preference
*1, *2, *3
QC_RSLT_MSTQC_RSLT_MST
qcqc_result_id_result_id
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 7
OPM Quality Sample Approval Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM Quality Sample Approval WorkflowOPM Quality Sample Approval Workflow
Inventoryincreases and validspecifications exist.
(QC_SPEC_MST which is a list from QC_ASSY_TYP)
Createsamples.
(QC_SMPL_MST)
Sample creationSample creationnotificationnotificationworkflowworkflow
Assay testingAssay testingprocessprocessworkflowworkflow
Enter testresults.
(QC_RSLT_MST)
SampleSampledispositiondispositionworkflowworkflow
Change item lotstatus or grade.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 8
Sample Creation Notification Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Sample Creation Notification WorkflowSample Creation Notification Workflow
Increase to Inventory IC_TRAN_PNDIC_TRAN_CMP
ReceiptReceiptPO_RECV_HDRPO_RECV_HDRPO_RECV_DTLPO_RECV_DTL
PM_MATL_DTLPM_MATL_DTLPM_BTCH_HDRPM_BTCH_HDR
Production BatchProduction Batch
InventoryInventoryAdjustmentAdjustmentIC_JRNL_MSTIC_JRNL_MSTIC_ADJS_JNLIC_ADJS_JNL
Sample Creation Notification WorkflowThe Sample Creation Notification Workflow process consists of the followingsteps:
1. The workflow begins when OPM transacts inventory requiring an assay.2. The Notifier is found and notification is sent.3. The Sample Approval Workflow is initiated if the notifier creates a sample
from the notification or creates a sample independent of the workflow.4. The workflow ends.
The transactions are derived from the receipts, production batches, andinventory adjustments.The transaction tables include:IC_TRAN_PND
IC_TRAN_CMP
IC_LOCT_INV
IC_SUMM_INV
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 9
Sample Creation Notification Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Search forQuality
Specification(QC_SPEC_MST)
Sample Creation Notification WorkflowSample Creation Notification Workflow
Notify Sample Collector
No Specification, workflow ends
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 10
Assay Testing Process Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Sample is collected
Assay Testing Process WorkflowAssay Testing Process Workflow
Sample data
entered in OPM
(QC_SMPL_MST)
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 11
Assay Testing Process Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Assay Testing Process WorkflowAssay Testing Process Workflow
Samplesare
testedNotifytesters
Assay Testing Process WorkflowThe Assay Testing Process Workflow consists of the following steps:
1. The workflow starts when an assay is required for new material. It isinitiated from the Sample Approval Process Workflow.
2. The Notifier is found and notification is sent.3. The status of the assay is updated to Notified.4. When the assay is completed, the assay status is updated to Completed,
otherwise the status is Time Out.5. Assay results are accumulated for the Sample Approval Process Workflow.6. The workflow ends.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 12
Sample Disposition Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Approver assigns sample
disposition(update to
QC_RSLT_MST)
Approver verifiesresults
Sample Disposition WorkflowSample Disposition Workflow
Resultsentered in OPM
(QC_RSLT_MST)
Sample Disposition Process Workflow1 The Sample Approver can open the Sample Results window to verify the
assay results.2. The workflow continually checks assay test disposition as follows:
If Snooze is detected, the workflow initiates the Assay Testing Process Workflow for timed-out assays and repeats steps 2 through 4 of the Sample CreationNotification Workflow.If Partial Retest is detected, the workflow initiates the Assay Testing ProcessWorkflow for selected assays and repeats steps 2 through 4 of the SampleCreation Notification Workflow.If Complete Retest is detected, the workflow initiates the Assay Testing ProcessWorkflow for all assays and repeats steps 2 through 4 of the Sample CreationNotification Workflow.If Accept or Reject is detected, the workflow proceeds to step 3.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 13
Sample Disposition Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Completeretest
Partialretest
Sample Disposition WorkflowSample Disposition Workflow
Reinitiateworkflow
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 14
Sample Disposition Workflow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Workflowends
Rejected Workflowends
Accepted
Inventory is
manually updated
Inventory is
manually updated
Sample Disposition WorkflowSample Disposition Workflow
Sample Dispostion Process Workflow (continued)3. The workflow finds the Inventory Approver and sends notification to this
user that the inventory has been accepted or rejected. The InventoryApprover can open the Quantities window (in the Inventory application) toassign a Grade to the material tested.
4. The workflow ends.When you update Grade or Status, it updates the Inventory tables in theInventory Quantity form. This makes an entry in the Inventory transactiontables.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 15
Assays and Units of Measure
Copyright © Oracle Corporation, 2000. All rights reserved.®
Assays and Units of MeasureAssays and Units of Measure
• A specification consists of a number of assays.• The assays are stored in the table QC_ASSY_TYP.• The QC_UOM_MST table contains chemistry-related
units of measure.• These UOMs are used for lab testing procedures.
• A specification consists of a number of assays.• The assays are stored in the table QC_ASSY_TYP.• The QC_UOM_MST table contains chemistry-related
units of measure.• These UOMs are used for lab testing procedures.
Copyright © Oracle Corporation, 2000. All rights reserved.
Quality ManagementChapter 6 - Page 16
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
SummarySummary
In this lesson, you should have learned how toexplain the Quality Workflows and the related tables.In this lesson, you should have learned how toexplain the Quality Workflows and the related tables.
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 1
Production Management andProcess Operation ControlChapter 7
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 2
Production Management and Process OperationControl
Copyright © Oracle Corporation, 2000. All rights reserved.®
Production Management and ProcessOperation Control
Production Management and ProcessOperation Control
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
After completing this lesson, you should be able todo the following:• Recognize the results of creating a batch• Observe changes as the batch progresses• Discover the results of tracking Process
Operations Control (POC) data
After completing this lesson, you should be able todo the following:• Recognize the results of creating a batch• Observe changes as the batch progresses• Discover the results of tracking Process
Operations Control (POC) data
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 4
Production Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
Production ManagementProduction Management
• Includes material side of production• Uses Batches and Firm Planned Orders (FPOs)• Includes material side of production• Uses Batches and Firm Planned Orders (FPOs)
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 5
Production Batch Cycle
Copyright © Oracle Corporation, 2000. All rights reserved.®
Production Batch CycleInventoryshortagecheck*
Allocation OptionsEdit transactions
Inventoryshortagecheck*
Allocationcheck
Allocation OptionsUser-initiatedPick lots/locationEdit transactions
Allocation OptionsEdit transactions
WIP Certified Closed
Auto-allocation*
Release
UnreleaseCancel
EnterCertify Close
*If enabled
Pending
Production Batch Cycle• Sources of Batches are Manual Entry, Generated from Firm Planned
Order, From Approval of MRP Recommendation, or Through ProductionAPI Create Batch.
• Taking a batch through its entire cycle is a complex set of tasks. Itinvolves not only setting up the batch correctly and taking it throughmultiple stages but, in addition, generating many inventory transactions.
• For example, an ingredient is automatic release and lot-controlled, andauto-allocation is being used. When the batch is released one or morecompleted inventory transactions can be generated. These completedtransactions can later be modified in quantity, or lot assigned, and thusresult in reversing transactions, and new completed transactions.
• A complex and long-duration batch can generate hundreds of transactions.• There is also an event log kept with transactions capturing event_id
involved with the transactions.
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 6
Production Module Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Production Module TablesProduction Module Tables
• Firm Planned Orders• Batches
PM_BTCH_HDR
PM_MATL_DTL
PM_HIST_HDR
Production Module TablesWhether a production order is an FPO or Batch, only three basic tables areinvolved.The _hdr and _dtl contain the situation and controls for products andingredients.The _hist_hdr tracks the events that occur for the batch, such as release,certify, and close. This allows analysis of the batch, as well as postmortemreview.
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 7
Data in Production Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
Data in Production Management
PM_HIST_HDR PM_BTCH_HDR
PM_MATL_DTL
IC_TRAN_PND
•Batch and FPO Header•FKs to SY_ORGN_MST, IC_WHSE_MST, FM_FORM_EFF, FM_FORM_MST, FM_ROUT_HDR
•Ingredient, Product, Byproduct Lines•FKs to PM_BTCH_HDR, SY_UOMS_MST, IC_ITEM_MST
•Inventory Transactions•FK relationship to PM_MATL_DTL not actually defined in database
•History of batch updates that have financial implications•Foreign Keys (FKs) to PM_BTCH_HDR and IC_WHSE_MST
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 8
Batch Relationships
Copyright © Oracle Corporation, 2000. All rights reserved.®
Batch Relationships
FM_ROUTE_HDR
#* Unique ID
FM_MATL_DTL
#* Unique ID
PM_MATL_DTL#* Unique ID
FM_FORM_MST
#* Unique ID
FM_FORM_EFF
#* Unique ID
PM_BTCH_HDR
#* Unique ID
PM_HIST_HDR#* Unique ID
Batch Relationships• A batch is created by choosing an effectivity with material details coming
from the formula, and resource details coming from the routing.• The actual lines on the formula are created as lines for the material for the
batch.• For financial purpioses another table, Batch history, is created to record
the date and time of events such as Release the batch, Certify the batch.
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 9
Batch Type in Production
Copyright © Oracle Corporation, 2000. All rights reserved.®
Batch Type in ProductionBatch Type in Production
Batches are distinguished from FPOs by the value inPM_BTCH_HDR.batch_type
10 = Firm Planned Order 0 = Batch
Batches are distinguished from FPOs by the value inPM_BTCH_HDR.batch_type
10 = Firm Planned Order 0 = Batch
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 10
Batch Status
Copyright © Oracle Corporation, 2000. All rights reserved.®
Batch StatusBatch Status
Batch and FPO status is identified byPM_BTCH_HDR.batch_status
-3 = Converted FPO-1 = Canceled 1 = Pending 2 = WIP 3 = Certified 4 = Closed
Batch and FPO status is identified byPM_BTCH_HDR.batch_status
-3 = Converted FPO-1 = Canceled 1 = Pending 2 = WIP 3 = Certified 4 = Closed
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 11
Reversal of Completed Transactions and Audit Trail
Copyright © Oracle Corporation, 2000. All rights reserved.®
Reversal of Completed Transactions andAudit Trail
• Completed transactions (representing events thathave actually occurred) are never updated orchanged.
• Instead, when you edit a quantity, for example, atransaction is created that reverses the originaltransaction, and a new transaction is created forthe new quantity.
• This provides a complete audit trail.
• Completed transactions (representing events thathave actually occurred) are never updated orchanged.
• Instead, when you edit a quantity, for example, atransaction is created that reverses the originaltransaction, and a new transaction is created forthe new quantity.
• This provides a complete audit trail.
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 12
Reversal of Completed Transactions and Audit Trail
Copyright © Oracle Corporation, 2000. All rights reserved.®
Reversal of Completed Transactions andAudit Trail
• A transaction is created for 100 pounds. The rowin ic_tran_pnd would look like this:
ITEM_ID LOT_ID TRANS_QTY TRANS_UM
123 456 100 LB
• If the quantity is then changed to 90 pounds, twoadditional rows would be created:
ITEM_ID LOT_ID TRANS_QTY TRANS_UM
123 456 100 LB
123 456 -100 LB
123 456 90 LB
• A transaction is created for 100 pounds. The rowin ic_tran_pnd would look like this:
ITEM_ID LOT_ID TRANS_QTY TRANS_UM
123 456 100 LB
• If the quantity is then changed to 90 pounds, twoadditional rows would be created:
ITEM_ID LOT_ID TRANS_QTY TRANS_UM
123 456 100 LB
123 456 -100 LB
123 456 90 LB
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 13
Process Operations Control Concepts
Copyright © Oracle Corporation, 2000. All rights reserved.®
Process Operations Control Concepts
Routing StepsRouting Steps
WIPPending Certified Closed
Production CycleProduction Cycle
Tracks:• Resource usage• WIP status• Step cycle time
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 14
Process Operations Control
Copyright © Oracle Corporation, 2000. All rights reserved.®
Process Operations ControlProcess Operations Control
• Includes non-material side of production• Uses Batch Steps (Operations), Batch Step Details
(Resources/Activities), Resource Transactions
• Includes non-material side of production• Uses Batch Steps (Operations), Batch Step Details
(Resources/Activities), Resource Transactions
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 15
Important Data in POC
Copyright © Oracle Corporation, 2000. All rights reserved.®
Important Data in POC
PM_BTCH_HDR PM_ROUT_DTL
PM_OPRN_DTL
PC_TRAN_PND
• Batch Steps• FKs to PM_BTCH_HDR, FM_ROUT_DTL, FM_OPRN_MST
• Batch Step Details• FKs to PM_ROUT_DTL, FM_OPRN_DTL, CR_RSRC_MST, FM_ACTV_MST, SY_UOMS_MST, CM_ALYS_MST, CM_CMPT_MST
• Resource Transactions• FKs to SY_ORGN_MST, SY_UOMS_MST, SY_REAS_CDS
• Batch Header• FKs to SY_ORGN_MST, IC_WHSE_MST, FM_FORM_EFF, FM_FORM_MST, FM_ROUT_HDR
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 16
Process Operation Control Module Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Process Operation Control Module TablesProcess Operation Control Module Tables
PM_ROUT_DEP
PM_ROUT_DTL
PC_TRAN_PND
PM_OPRN_WIP
PM_OPRN_DTL
PM_ROUT_MTL
POC Data
Process Operation Control Module TablesIf POC data is being captured, then other tables track the consumption ofresources by operation. There is even a new _tran_pnd which is not forinventory but resources, and eventually costing of a batch by material andresources.
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 17
Batch with POC Relationships
Copyright © Oracle Corporation, 2000. All rights reserved.®
Batch with POC RelationshipsBatch with POC RelationshipsFM_ROUT_HDR#* Unique ID
FM_MATL_DTL#* Unique ID
PM_FORM_EFF#* Unique ID
FM_ROUTE_DTL#* Unique ID
FM_FORM_MST#* Unique ID
PM_BTCH_HDR#* Unique ID
PM_HIST_HDR#* Unique ID
PM_ROUTE_DTL#* Unique ID
PM_MATL_DTL#* Unique ID
PM_ROUT_DEP#* Unique ID
PM_ROUT_MTL#* Unique ID
PC_TRAN_PND#* Unique ID
PM_OPRN_WIP#* Unique ID
PM_OPRN_DTL#* Unique ID
Batch with POC RelationshipsIf POC data capture is turned on, you can see the increase in complexity.There is also a great increase in data input requirements. This is one reasonwhy the first APIs (application program interfaces) were done for ProductionManagement (PM) and POC. For clients with a high volume of data, capture ofdata for ingredient consumption, product output and resource usage must beautomated. This means that the data capture programs must be interfaced to thedatabase through the APIs.
Copyright © Oracle Corporation, 2000. All rights reserved.
Production Management and Process Operation ControlChapter 7 - Page 18
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
SummarySummary
In this lesson, you should have learned how to:• Recognize the results of creating a batch• Observe changes as the batch progresses• Discover the results of tracking POC data
In this lesson, you should have learned how to:• Recognize the results of creating a batch• Observe changes as the batch progresses• Discover the results of tracking POC data
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 1
Purchase ManagementChapter 8
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 2
Purchase Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
Purchase ManagementPurchase Management
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
After completing this lesson, you should be able todo the following:• Describe the Oracle Process Manufacturing
Purchasing flow• Identify the OPM Purchasing and Receiving/Return
tables• Explain the integration between Oracle Purchasing
and OPM Receiving• Identify Oracle Purchasing documents and the
OPM equivalent• Explain data synchronization between Oracle
Applications and OPM
After completing this lesson, you should be able todo the following:• Describe the Oracle Process Manufacturing
Purchasing flow• Identify the OPM Purchasing and Receiving/Return
tables• Explain the integration between Oracle Purchasing
and OPM Receiving• Identify Oracle Purchasing documents and the
OPM equivalent• Explain data synchronization between Oracle
Applications and OPM
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 4
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
• Identify OPM Purchasing setup tables• Recognize key triggers on Purchasing and OPM
tables• Analyze why synchronization does not occur• Identify tax tables and tax location
• Identify OPM Purchasing setup tables• Recognize key triggers on Purchasing and OPM
tables• Analyze why synchronization does not occur• Identify tax tables and tax location
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 5
OPM Purchasing Flow
Copyright © Oracle Corporation, 2000. All rights reserved.®
PO_RECV_DTL
Purchasing TablesPurchasing Tables Inventory TablesInventory Tables
OPM Purchasing FlowOPM Purchasing Flow
PO_RECV_HDR
PO_ORDR_DTL
PO_ORDR_HDR
PO_ RTRN _DTL
PO_RTRN_HDR
IC_TRAN_PND
IC_LOCT_INV
IC_SUMM_INV
OPM Purchasing Flow• While the PO is pending, it is is held in ic_tran_pnd.• Once a receipt or return is executed, it is updated in ic_summ_inv and
ic_loct_inv.
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 6
OPM Purchasing Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM Purchasing Tables
PO HeaderPO_ORDR_HDR
Order LinesPO_ORDR_DTL
InventoryTransactionsIC_TRAN_PND
GL DistributionPO_DIST_DTL
Acquisition Costs
PO_COST_DTL
popo_id_id (PK) (PK)
polinepoline_id_id (PK) (PK)
doc_type = PORDdoc_type = PORDdoc_id =doc_id = popo_id_id
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 7
OPM Receiving/Return Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM Receiving/Return Tables
Receipt HeaderPO_RECV_HDR
Return HeaderPO_RTRN_HDR
Receive/ReturnHistory
PO_RECV_HST
InventoryTransactionsIC_TRAN_PND
doc_type =RECV orRTRN
doc_id = recv_idor return_id
ReceiptDetail
PO_RECV_DTL
ReturnDetail
PO_RTRN_DTL
recvrecv_id_id (PK) (PK)
return_idreturn_id (PK) (PK)
OPM Receiving/Return TablesAn option on return is to reopen the line, which will not reopen the Oracle PO.But the line does remain open on the OPM side.
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 8
Purchasing Integration
Copyright © Oracle Corporation, 2000. All rights reserved.®
Purchasing IntegrationPurchasing Integration
Enterpurchase orders
Receiveinventory items
Receivenon-inventory items
Update receiptinformation in
Oracle Purchasing
Oracle PurchasingOracle Purchasing OPM ReceivingOPM Receiving
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 9
Purchasing Documents
Copyright © Oracle Corporation, 2000. All rights reserved.®
Purchasing Documents
Standard Purchase Orders
Scheduled Releases
Blanket Releases
Purchase Orders
Oracle PurchasingOracle Purchasing OPMOPM
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 10
Purchasing Documents
Copyright © Oracle Corporation, 2000. All rights reserved.®
Purchasing Documents
Planned Purchase Orders Blanket Purchase Orders
Oracle PurchasingOracle Purchasing OPMOPM
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 11
Purchasing Documents
Copyright © Oracle Corporation, 2000. All rights reserved.®
Purchasing Documents
Oracle documents with no OPM equivalent• Contract Purchase Order• Blanket Purchase Order• Requisition• RFQ and Quotation
Oracle documents with no OPM equivalent• Contract Purchase Order• Blanket Purchase Order• Requisition• RFQ and Quotation
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 12
Data Synchronization
Copyright © Oracle Corporation, 2000. All rights reserved.®
Data entered inData entered in APPSAPPS OPMOPM
OrganizationsOrganizations � �
SuppliersSuppliers �
FOB CodesFOB Codes �
Payment TermsPayment Terms �
AccountsAccounts �
Account Mapping Account Mapping �
Data SynchronizationData Synchronization
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 13
Data Synchronization through Triggers
Copyright © Oracle Corporation, 2000. All rights reserved.®
Data entered inData entered in APPSAPPS OPMOPM
Units of MeasureUnits of Measure �
ItemsItems �
Warehouses (Locations)Warehouses (Locations) �
Freight TermsFreight Terms �
CarriersCarriers �
Currencies Currencies �
Exchange RatesExchange Rates �
Data Synchronization through TriggersData Synchronization through Triggers
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 14
Integration Highlights
Copyright © Oracle Corporation, 2000. All rights reserved.®
Integration HighlightsIntegration Highlights
Maintain integration to other OPM Modules• Material Requirements Planning (can also create
Requisitions from MRP)• Costing/Manufacturing Acting Controller (MAC)• Inventory
Maintain integration to other OPM Modules• Material Requirements Planning (can also create
Requisitions from MRP)• Costing/Manufacturing Acting Controller (MAC)• Inventory
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 15
OPM Purchasing Setup Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
OPM Purchasing Setup TablesOPM Purchasing Setup Tables
• PO_COST_MST: Acquisition Costs• PO_VEND_CLS
• PO_VGLD_CLS
• PO_VTRD_CLS
• PO_VEND_MST and PO_VEND_ASC: Vendor tablespopulated automatically from Accounts Payable
• PO_COST_MST: Acquisition Costs• PO_VEND_CLS
• PO_VGLD_CLS
• PO_VTRD_CLS
• PO_VEND_MST and PO_VEND_ASC: Vendor tablespopulated automatically from Accounts Payable
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 16
PO Synchronization
Copyright © Oracle Corporation, 2000. All rights reserved.®
PO Synchronization
• Approved Standard POs, Releases, and PlannedPOs are copied over to OPM PO tables
• OPM Common Purchasing Synchronization:Request log shows errors
• OPM Common Purchasing PO ResubmissionReport: Used to resubmit approved POs back toOPM if an issue occurred
• Approved Standard POs, Releases, and PlannedPOs are copied over to OPM PO tables
• OPM Common Purchasing Synchronization:Request log shows errors
• OPM Common Purchasing PO ResubmissionReport: Used to resubmit approved POs back toOPM if an issue occurred
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 17
Common Purchasing Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Common Purchasing Tables
Mapping betweenOPM and Oracle Apps
CPG_ORAGEMS_MAPPING
OPM PO LinesPO_ORDR_DTL
Oracle PO LinesPO_LINES_ALL
orPO_RELEASES_ALL
PurchasingInterface
CPG_PURCHASING_INTERFACE
Acquisition CostsEntered in OracleCPG_COST_DTL
OPM PO HeaderPO_ORDR_HDR Oracle PO Headers
PO_HEADERS_ALL
PO Acquisition CostPO_COST_DTL
Oracle PO Lines-ShipmentsPO_LINE_
LOCATIONS_ALL
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 18
Common Purchasing Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
PurchasingInterface
CPG_PURCHASING_INTERFACE
Common Purchasing Tables
OPM BlanketOrder (BPO) Header
PO_BPOS_HDR
OPM BPO Release SchedulePO_RELS_SCH
Interface for Planned POsInterface for Planned POs(stored in OPM BPO Tables)(stored in OPM BPO Tables)
Oracle PO LinesPO_LINES_ALL
orPO_RELEASES_ALL
Oracle PO HeadersPO_HEADERS_ALL
Mapping betweenOPM and Oracle Apps
CPG_ORAGEMS_MAPPING
OPM BPO LinesPO_BPOS_DTL
Oracle PO Lines-ShipmentsPO_LINE_
LOCATIONS_ALL
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 19
Common Purchasing Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Common Purchasing TablesCommon Purchasing Tables
• CPG_ORAGEMS_MAPPING: Maintains links betweenOracle PO and POs created in OPM
• CPG_PURCHASING_INTERFACE: Contains PO datato be sent over to OPM
• CPG_COST_DTL: Acquisitions Costs enteredagainst Oracle PO
• CPG_ORAGEMS_MAPPING: Maintains links betweenOracle PO and POs created in OPM
• CPG_PURCHASING_INTERFACE: Contains PO datato be sent over to OPM
• CPG_COST_DTL: Acquisitions Costs enteredagainst Oracle PO
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 20
Common Purchasing Triggers
Copyright © Oracle Corporation, 2000. All rights reserved.®
Common Purchasing TriggersCommon Purchasing Triggers
• Key triggers on Oracle Purchasing tables• Triggers on OPM Purchasing tables• Triggers perform several functions:
– Insert rows into interface tables– Invoke concurrent manager request to
synchronize data– Perform validation of data
• Key triggers on Oracle Purchasing tables• Triggers on OPM Purchasing tables• Triggers perform several functions:
– Insert rows into interface tables– Invoke concurrent manager request to
synchronize data– Perform validation of data
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 21
Key Triggers on Oracle PO Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Key Triggers on Oracle PO Tables
• Table: PO_LINE_LOCATIONS_ARCHIVE_ALLgml_po_line_locs_arch_all_t1:
Inserts data into the Purchasing InterfaceTable (cpg_purchasing_interface) whenPO is Approved
• Table: PO_HEADERS_ARCHIVE_ALLgml_po_headers_archive_all_t1:Invokes concurrent manager request tosynchronize data between OPM and APPS
• Table: PO_LINE_LOCATIONS_ARCHIVE_ALLgml_po_line_locs_arch_all_t1:
Inserts data into the Purchasing InterfaceTable (cpg_purchasing_interface) whenPO is Approved
• Table: PO_HEADERS_ARCHIVE_ALLgml_po_headers_archive_all_t1:Invokes concurrent manager request tosynchronize data between OPM and APPS
Key Triggers on Oracle PO TablesPO_LINES_LOCATIONS_ALL is copied intoPO_LINES_LOCATIONS_ARCHIVE_ALL all when the approval takesplace.
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 22
Triggers on OPM Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Triggers on OPM Tables
Table: PO_RECV_DTLgml_po_recv_dtl_t3:Inserts receiving information intorcv_header_interface andrcv_transactions_interface tables
Table: PO_RECV_DTLgml_po_recv_dtl_t3:Inserts receiving information intorcv_header_interface andrcv_transactions_interface tables
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 23
Validation Triggers
Copyright © Oracle Corporation, 2000. All rights reserved.®
Validation TriggersValidation Triggers
Table: RCV_TRANSACTIONS_INTERFACEgml_rcv_transactions_interf_t1:Prevents user from receiving OPM items, inOracle Receiving
Table: RCV_TRANSACTIONS_INTERFACEgml_rcv_transactions_interf_t1:Prevents user from receiving OPM items, inOracle Receiving
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 24
Why Can’t I See My PO in OPM?
Copyright © Oracle Corporation, 2000. All rights reserved.®
Why Can’t I See My PO in OPM?Why Can’t I See My PO in OPM?
• Are the items on the PO flagged as “Inventory” inthe Oracle Apps Item Master?
• Does the PO have an Approved status?• Are there rows in the
CPG_PURCHASING_INTERFACE table? If so, look atthe column INVALID_IND.– N means PO was not processed– Y means PO failed validation– P means PO should be in OPM
• Are the items on the PO flagged as “Inventory” inthe Oracle Apps Item Master?
• Does the PO have an Approved status?• Are there rows in the
CPG_PURCHASING_INTERFACE table? If so, look atthe column INVALID_IND.– N means PO was not processed– Y means PO failed validation– P means PO should be in OPM
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 25
Why Can’t I See My PO in OPM?
Copyright © Oracle Corporation, 2000. All rights reserved.®
Why Can’t I See My PO in OPM?Why Can’t I See My PO in OPM?
Is the concurrent manager running? Did OPMCommon Purchasing Synchronization complete (witheither Normal or Error status)? Check the log file.• GL Calendar must be opened for the period• Inventory Calendar must be in Oracle Inventory• Control Purchasing periods must be in Oracle
Purchasing
Is the concurrent manager running? Did OPMCommon Purchasing Synchronization complete (witheither Normal or Error status)? Check the log file.• GL Calendar must be opened for the period• Inventory Calendar must be in Oracle Inventory• Control Purchasing periods must be in Oracle
Purchasing
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 26
Why Can’t I See My Receipt Information in Oracle PO?
Copyright © Oracle Corporation, 2000. All rights reserved.®
Why Can’t I See My Receipt Informationin Oracle PO?
Why Can’t I See My Receipt Informationin Oracle PO?
• Was the Receiving Transaction Processor inOracle Purchasing submitted after Receipt?
• If the Receiving Transaction Processor in OraclePurchasing is run and you still do not see theReceipt, check the PO_INTERFACE_ERRORS table.
Note: The Receiving Transaction Processor in OraclePurchasing must be run manually.
• Was the Receiving Transaction Processor inOracle Purchasing submitted after Receipt?
• If the Receiving Transaction Processor in OraclePurchasing is run and you still do not see theReceipt, check the PO_INTERFACE_ERRORS table.
Note: The Receiving Transaction Processor in OraclePurchasing must be run manually.
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 27
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
SummarySummary
In this lesson, you should have learned how to:• Describe the Oracle Process Manufacturing
Purchasing flow• Identify the OPM Purchasing and Receiving/Return
tables• Explain the integration between Oracle Purchasing
and OPM receiving• Identify Oracle Purchasing documents and the
OPM equivalents• Explain data synchronization between Oracle
Applications and OPM
In this lesson, you should have learned how to:• Describe the Oracle Process Manufacturing
Purchasing flow• Identify the OPM Purchasing and Receiving/Return
tables• Explain the integration between Oracle Purchasing
and OPM receiving• Identify Oracle Purchasing documents and the
OPM equivalents• Explain data synchronization between Oracle
Applications and OPM
Copyright © Oracle Corporation, 2000. All rights reserved.
Purchase ManagementChapter 8 - Page 28
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
SummarySummary
In this lesson, you should have learned how to:• Identify the OPM Purchasing setup tables• Recognize key triggers on Purchasing and OPM
tables• Analyze why synchronization does not occur• Identify tax tables and tax location
In this lesson, you should have learned how to:• Identify the OPM Purchasing setup tables• Recognize key triggers on Purchasing and OPM
tables• Analyze why synchronization does not occur• Identify tax tables and tax location
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 1
Order FulfillmentChapter 9
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 2
Order Fulfillment
Copyright © Oracle Corporation, 2000. All rights reserved.®
Order FulfillmentOrder Fulfillment
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
After completing this lesson, you should be able todo the following:• Identify the tables used in Order Fulfillment• Recognize tables for processing transactions and
reports• Define the sales order processing and sales order
transaction flows• Describe the flow from sales order processing to
Oracle Receivables• Review of important tables in the Logistics Data
Model
After completing this lesson, you should be able todo the following:• Identify the tables used in Order Fulfillment• Recognize tables for processing transactions and
reports• Define the sales order processing and sales order
transaction flows• Describe the flow from sales order processing to
Oracle Receivables• Review of important tables in the Logistics Data
Model
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 4
Order Fulfillment Setup Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Order Fulfillment Setup TablesOrder Fulfillment Setup Tables
• OP_ALOT_PRM
• OP_CGLD_CLS
• OP_COMMISSION
• OP_COMM_CDS
• OP_CTRD_CLS
• OP_CUST_CLS
• OP_FOBC_MST
• OP_FRGT_MTH
• OP_GNRC_ITM
• OP_HOLD_CDS
• OP_ALOT_PRM
• OP_CGLD_CLS
• OP_COMMISSION
• OP_COMM_CDS
• OP_CTRD_CLS
• OP_CUST_CLS
• OP_FOBC_MST
• OP_FRGT_MTH
• OP_GNRC_ITM
• OP_HOLD_CDS
• OP_LKBX_MST
• OP_PKGD_ITM
• OP_PORT_MST
• OP_SHIP_MST
• OP_SHIP_MTH
• OP_SLSR_CLS
• OP_SLSR_MST
• OP_TERM_MST
• OP_TXCU_ASC
• OP_LKBX_MST
• OP_PKGD_ITM
• OP_PORT_MST
• OP_SHIP_MST
• OP_SHIP_MTH
• OP_SLSR_CLS
• OP_SLSR_MST
• OP_TERM_MST
• OP_TXCU_ASC
Order Fulfillment Setup TableThe OP_LKBX_MST is for a stand-alone install only
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 5
Commission Code Structure
Copyright © Oracle Corporation, 2000. All rights reserved.®
Commission Code StructureCommission Code Structure
OP_COMMISSION
(new header table)
Sales Rep MasterOP_SLSR_MST
Commission CodeDetail
OP_COMM_CDS
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 6
MLS Setup Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
MLS Setup Tables
• Order Status– OP_ORDR_STATUS
– OP_ORDR_STS_B
– OP_ORDR_STS_TL
• Presales Order Type– OP_PRSL_HDR
– OP_PRSL_TYP_B
– OP_PRSL_TYP_TL
• Order Status– OP_ORDR_STATUS
– OP_ORDR_STS_B
– OP_ORDR_STS_TL
• Presales Order Type– OP_PRSL_HDR
– OP_PRSL_TYP_B
– OP_PRSL_TYP_TL
• Order Type– OP_ORDR_TYPE
– OP_ORDR_TYP_B
– OP_ORDR_TYP_TL
• Order Type– OP_ORDR_TYPE
– OP_ORDR_TYP_B
– OP_ORDR_TYP_TL
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 7
Pricing Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Pricing TablesPricing Tables
Price List HeaderOP_PRCE_MST
Price List ItemsOP_PRCE_ITM
Price BreaksOP_PRCE_BRK
Price EffectivityOP_PRCE_EFF
Contract Tables mirror this relationship.
PricelistPricelist_id_id (PK) (PK) Price_idPrice_id (PK) (PK)
PriceffPriceff_id_id (PK) (PK)
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 8
Tables for Processing and Reports
Copyright © Oracle Corporation, 2000. All rights reserved.®
Tables for Processing and ReportsTables for Processing and Reports
• OP_TRAN_TMP: Used during automatic inventoryallocation in Shipping. Holds information on lotsthat may be allocated.
• OP_UPDT_BAL_WK: Table used by UpdateCustomer Balance report.
• These tables may or may not contain data at anypoint in time.
• OP_TRAN_TMP: Used during automatic inventoryallocation in Shipping. Holds information on lotsthat may be allocated.
• OP_UPDT_BAL_WK: Table used by UpdateCustomer Balance report.
• These tables may or may not contain data at anypoint in time.
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 9
Sales Order Processing Flow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Sales Order Processing FlowSales Order Processing Flow
ReceiveCustomer
Order
CreateSales Order
AllocateProduct
CreateRelease
Shipment
InvoiceCustomer
Manual Entry CopyManual Entry CopyUser Order Profile (EDI)User Order Profile (EDI)
Allocate MaterialAllocate Material Allocate MaterialAllocate Material
Sales Order Processing FlowIf material is lot-controlled, it must be allocated to a lot or lots before theshipment can be released.
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 10
Customer Master and Related Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Customer Master and Related Tables
Customer Master
OP_CUST_MSTcust_id (PK)
Customer Carriers
OP_CUST_SHP
Customer ItemsOP_CUST_ITM
CustomerContacts
OP_CUST_CON
AddressesSY_ADDR_MST
CustomerAssociation
OP_CUST_ASC
custitem_id (PK)
contact_id (PK)
custship_id (PK)
addr_id (PK)
Customer Master and Related Tables• Addresses, Contacts, and Customers are created in AR.• Contacts and Customers have additional fields that can be added and
modified from the OPM side.
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 11
Sales Order Transaction Flow
Copyright © Oracle Corporation, 2000. All rights reserved.®
Sales Order Transaction FlowSales Order Transaction Flow
OP_BILL_LAD
Sales Order TablesSales Order Tables Inventory TablesInventory Tables
OP_ORDR_DTL
OP_ORDR_HDR
IC_TRAN_PND
IC_LOCT_INV
IC_SUMM_INV
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 12
Order/Shipment Transaction Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Order/Shipment Transaction Tables
Order HeaderOP_ORDR_HDR
Shipment Header
OP_BILL_LAD
Order and Shipment DetailOP_ORDR_DTL Inventory
TransactionsIC_TRAN_PND
Order Headerand LineCharges
OP_ORDR_CHGTaxes for Order
and ShippingLines
OP_INVC_CHG
Audit Table ofOrder Line
ChangesOP_AUDT_DTL
order_id (PK)
bol_id (PK)
line_id (PK)
doc_type = ‘OPSO’doc_id = order_id or
bol_id
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 13
Order Profile (+BSO) Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Order Profile (+BSO) Tables
Profile HeaderOP_PRSL_HDR
ProfileOrder LinesOP_PRSL_DTL
Profile Headerand LineCharges
OP_PRSL_CHG
ReleaseSchedule
(for BSO’s)OP_RELS_SCH
presales_presales_ordord_id_id (PK) (PK)
In 11In 11ii, these tables, these tablesalso store Blanket also store Blanket Sales Orders(BSO)Sales Orders(BSO)presales_presales_ordlineordline_id_id (PK) (PK)
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 14
GEMMS Sales Order Processing to Oracle Receivables
Copyright © Oracle Corporation, 2000. All rights reserved.®
OP_BILL_LAD
OP_ORDR_DTL
OP_ORDR_HDR
GEMMS Sales Order Processing toOracle Receivables
GEMMS Sales Order Processing toOracle Receivables
Global Enterprise Manufacturing Management System (GEMMS) TablesGlobal Enterprise Manufacturing Management System (GEMMS) Tables
Oracle TablesOracle Tables
GEMMS Immediate InterfaceGEMMS Immediate Interface
GEMMS Periodic InterfaceGEMMS Periodic Interfacemonthly, weekly, daily, hourly, by minutemonthly, weekly, daily, hourly, by minute
AR UpdateAR Update AutoInvoiceAutoInvoice
RA_INTERFACE_ERRORS
RA_INTERFACE_LINES
RA_CUSTOMER_TRX_LINES
RA_CUSTOMER_TRX
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 15
Tax Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Tax TablesTax Tables
• Codes/Classes– TX_CALC_MST
– TX_TAXA_STS
– TX_TXRE_CDS
– TX_TXRP_CLS
• Tax Locations– TX_TLOC_CDS
– TX_TLOC_ASC
– TX_TOFR_ASC
• Codes/Classes– TX_CALC_MST
– TX_TAXA_STS
– TX_TXRE_CDS
– TX_TXRP_CLS
• Tax Locations– TX_TLOC_CDS
– TX_TLOC_ASC
– TX_TOFR_ASC
• Tax Rates– TX_TAXA_MST
– TX_TAXA_DTL
• Tax Rates– TX_TAXA_MST
– TX_TAXA_DTL
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 16
Tax Locations
Copyright © Oracle Corporation, 2000. All rights reserved.®
Tax LocationsTax Locations
Tax LocationsTX_TLOC_CDS
AssociatedTax LocationsTX_TOFR_ASC
Tax Authoritiesfor AssociatedTax LocationsTX_TLOC_ASC
Tax AuthoritiesTX_TAXA_MST
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 17
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
SummarySummary
In this lesson, you should have learned how to:• Identify the tables used in Order Fulfillment• Recognize tables for processing transactions and
reports• Define the sales order processing and sales order
transaction flows• Describe the flow from sales order processing to
Oracle Receivables• Review important tables in the Logistics Data
Model
In this lesson, you should have learned how to:• Identify the tables used in Order Fulfillment• Recognize tables for processing transactions and
reports• Define the sales order processing and sales order
transaction flows• Describe the flow from sales order processing to
Oracle Receivables• Review important tables in the Logistics Data
Model
Copyright © Oracle Corporation, 2000. All rights reserved.
Order FulfillmentChapter 9 - Page 18
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 1
Regulatory ManagementChapter 10
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 2
Regulatory Management
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory ManagementRegulatory Management
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 3
Objectives
Copyright © Oracle Corporation, 2000. All rights reserved.®
ObjectivesObjectives
After completing this module, you should be able todo the following:• Recognize the Regulatory Management concepts
and identify the Setup tables• Understand Material Safety Data Sheets• Identify Document and Item tables
After completing this module, you should be able todo the following:• Recognize the Regulatory Management concepts
and identify the Setup tables• Understand Material Safety Data Sheets• Identify Document and Item tables
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 4
Regulatory Setup Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory Setup TablesRegulatory Setup Tables
• Regulatory Management consists mostly of setup,or reference tables.
• These reference tables contains information aboutan item, such as:– Phrases– Toxicity– Classes– Hazard groups
• Regulatory Management consists mostly of setup,or reference tables.
• These reference tables contains information aboutan item, such as:– Phrases– Toxicity– Classes– Hazard groups
Regulatory Setup TablesRefer to the Technical Reference Manuals for the full list of table names.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 5
Material Safety Data Sheet (MSDS)
Copyright © Oracle Corporation, 2000. All rights reserved.®
Material Safety Data Sheet (MSDS)Material Safety Data Sheet (MSDS)
• Material Safety Data Sheets are documents thatprovide information about hazardous materials.
• An MSDS is a compilation of information culledfrom data stored in tables.
• An MSDS is built based on an item, and itsingredients.
• Material Safety Data Sheets are documents thatprovide information about hazardous materials.
• An MSDS is a compilation of information culledfrom data stored in tables.
• An MSDS is built based on an item, and itsingredients.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 6
Regulatory Document Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory Document TablesRegulatory Document Tables
• Document tables are used to create the MSDStemplate.
• Each table contains a different piece of thetemplate information.
• Document tables are used to create the MSDStemplate.
• Each table contains a different piece of thetemplate information.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 7
Regulatory Document Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory Document TablesRegulatory Document Tables
• GR_DOCUMENT_CODES
• GR_DOCUMENT_DETAILS
• GR_DOCUMENT_HEADINGS
• GR_DOCUMENT_PRINT
• GR_DOCUMENT_STRUCTURES
• GR_DOCUMENT_CODES
• GR_DOCUMENT_DETAILS
• GR_DOCUMENT_HEADINGS
• GR_DOCUMENT_PRINT
• GR_DOCUMENT_STRUCTURES
• GR_DOCUMENT_CODES: Contains the date format and determineswhether detailed ingredient, toxic, and exposure information displays orprints on the document. Also allows customization of the appearance ofthe detailed elements.
• GR_DOCUMENT_DETAILS: Contains each phrase as it will display orprint on the document.
• GR_DOCUMENT_HEADINGS: Contains the headings and subheadingslinked to a document.
• GR_DOCUMENT_PRINT: Contains print information for the document byItem Code, Document Code, and Date.
• GR_DOCUMENT_STRUCTURES: Contains detailed breakdown about howthe document will display or print. A row of date format and detailedingredient, toxic, and exposure information information must be defined inthe Document Code entity before structure details are built.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 8
Regulatory Item Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory Item TablesRegulatory Item Tables
• Item tables contain specific information about anitem.
• This information is pulled into a documentstructure template to create the MSDS document.
• Item tables contain specific information about anitem.
• This information is pulled into a documentstructure template to create the MSDS document.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 9
Regulatory Item Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory Item TablesRegulatory Item Tables
• GR_ITEM_GENERAL
• GR_ITEM_DOC_STATUSES
• GR_ITEM_DISCLOSURES
• GR_ITEM_CONCENTRATIONS
• GR_ITEM_PROPERTIES
• GR_ITEM_RISK_PHRASES
• GR_ITEM_SAFETY_PHRASES
• GR_ITEM_TOXIC
• GR_ITEM_GENERAL
• GR_ITEM_DOC_STATUSES
• GR_ITEM_DISCLOSURES
• GR_ITEM_CONCENTRATIONS
• GR_ITEM_PROPERTIES
• GR_ITEM_RISK_PHRASES
• GR_ITEM_SAFETY_PHRASES
• GR_ITEM_TOXIC
• GR_ITEM_GENERAL: Stores regulatory information that furtheridentifies the item. It also stores flags that govern what data displays onthe MSDS.
• GR_ITEM_DOC_STATUSES: Contains the last change date and ItemDocument Status.
• GR_ITEM_DISCLOSURES: Contains Disclosure information for theitem.
• GR_ITEM_CONCENTRATIONS: A temporary table used during thedocument build process.
• GR_ITEM_PROPERTIES: Contains the characteristics of the item suchas physical properties, transport, and country-specific information.
• GR_ITEM_RISK_PHRASES: Contains the Standard European RiskPhrase for the item. Multiple rows of Risk Phrase information can exist foreach item.
• GR_ITEM_SAFETY_PHRASES: Contains the European Safety Phrase forthe item. Multiple rows of Safety Phrase information can exist for eachitem.
• GR_ITEM_TOXIC: This entity holds the toxicity information recorded foran item. There can be multiple rows of toxic information for each item.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 10
Regulatory Label Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory Label TablesRegulatory Label Tables
• Label tables are placeholders for information thatwill be in the MSDS.
• Information is pulled from the items tables to thedocument structure template, and is placed in theappropriate section based on where the label tellsit to go.
• Label tables are placeholders for information thatwill be in the MSDS.
• Information is pulled from the items tables to thedocument structure template, and is placed in theappropriate section based on where the label tellsit to go.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 11
Regulatory Label Tables
Copyright © Oracle Corporation, 2000. All rights reserved.®
Regulatory Label TablesRegulatory Label Tables
• GR_LABELS
• GR_LABEL_CLASSES
• GR_LABEL_CLASS_RESPS
• GR_LABEL_PROD_CLASSES
• GR_LABEL_PROPERTIES
• GR_LABELS
• GR_LABEL_CLASSES
• GR_LABEL_CLASS_RESPS
• GR_LABEL_PROD_CLASSES
• GR_LABEL_PROPERTIES
• GR_LABELS: Contains many field name classes, each containing manyrows that define the format and text for each line on the document. Forexample, a field name of Boiling will determine how and where thephysical characteristics of boiling point display on the document.
• GR_LABEL_CLASSES: The field name class groups the field name codestogether into like areas such as Header, Physical, and Transport. Althoughwe will distribute the application with a number of predefined field nameclasses, users can add to them.
• GR_LABEL_CLASS_RESPS: Contains the Responsibility Code that canbe assigned to the field name. Primarily used for security purposes in theapplication. For example, someone responsible for transportationinformation will only have field names that are linked to thatresponsibility and can navigate only to the Transportation form.
• GR_LABEL_PROD_CLASSES: Contains the product classes that will notprint the field name code and associated information.
• GR_LABEL_PROPERTIES: Contains the display properties for the fieldname for each item code. For example, the field name Color has a displayproperty of text or phrase entry, and boiling point has display properties oftext, low range, high range, and temperature scale.
Copyright © Oracle Corporation, 2000. All rights reserved.
Regulatory ManagementChapter 10 - Page 12
Summary
Copyright © Oracle Corporation, 2000. All rights reserved.®
SummarySummary
In this module, you should have learned how to:• Recognize the Regulatory Management concepts
and identify the Setup tables• Understand Material Safety Data Sheets• Identify Document and Item tables
In this module, you should have learned how to:• Recognize the Regulatory Management concepts
and identify the Setup tables• Understand Material Safety Data Sheets• Identify Document and Item tables