Instructor Guide

11i Manufacturing Functional
Foundation
Instructor Guide
D12333GC10
Edition 1.0
May 2001
D32897
Copyright © Oracle Corporation, 2001. All rights reserved.
This documentation contains proprietary information of Oracle Corporation. It is provided under a license
agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse
engineering of the software is prohibited. If this documentation is delivered to a U.S. Government Agency of the
Department 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 software
and 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 prior
written permission of the Education Products group of Oracle Corporation. Any other copying is a violation of
copyright 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 is
delivered 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 the
documentation, please report them in writing to Worldwide Education Services, Oracle Corporation, 500 Oracle
Parkway, Box SB-6, Redwood Shores, CA 94065. Oracle Corporation does not warrant that this document is
error-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 their
respective owners.
Author
Amy Sonczalla, Bill Figini, Bill Sawyer, Leanne Vakoc
Technical Contributors and Reviewers
Charles Pirnat, Tom Marik, Mani Rana, Prasanth Pala, Sachin Patel, Arvydas
Nakas
This book was published using:
Oracle Tutor
Table of Contents
Applications Architecture .....................................................................................................1-1

Applications Architecture ....................................................................................................1-2
Objectives ............................................................................................................................1-3
Applications Network Architecture .....................................................................................1-4
Desktop Tier ........................................................................................................................1-5
Forms Client Applet ............................................................................................................1-6
JInitiator...............................................................................................................................1-7
Application Tier...................................................................................................................1-8
Web Server ..........................................................................................................................1-9
Forms Server........................................................................................................................1-10
Concurrent Processing Server..............................................................................................1-11
Accessing Concurrent Processing Output............................................................................1-12
Reports Server .....................................................................................................................1-13
Administration Server..........................................................................................................1-14
Database Tier.......................................................................................................................1-15
Database Architecture..........................................................................................................1-16
Oracle Applications Database Objects.................................................................................1-17
APPS Schema ......................................................................................................................1-18
Additional Schemas .............................................................................................................1-19
Multiple Organizations Views .............................................................................................1-20
Multiple Reporting Currencies ............................................................................................1-21
File System Architecture .....................................................................................................1-22
APPL_TOP..........................................................................................................................1-23
Product Directories ..............................................................................................................1-25
Admin Directory..................................................................................................................1-26
Bin Directory .......................................................................................................................1-27
Forms Directory...................................................................................................................1-28
Help Directory .....................................................................................................................1-29
HTML Directory..................................................................................................................1-30
Include Directory .................................................................................................................1-31
Java Directory......................................................................................................................1-32
Lib Directory .......................................................................................................................1-33
Log and Out Directories ......................................................................................................1-34
Media Directory...................................................................................................................1-35
Mesg Directory ....................................................................................................................1-36
Patch Directory ....................................................................................................................1-37
PLSQL and Resource Directories........................................................................................1-38
Reports Directory.................................................................................................................1-39
SQL Directory .....................................................................................................................1-40
AD Directory .......................................................................................................................1-41
AU Directory .......................................................................................................................1-42
Admin Directory..................................................................................................................1-43
Admin Directory Text Files.................................................................................................1-44
Common Components Directory .........................................................................................1-45
Copying Java Files: apps.zip ...............................................................................................1-46
Technology Stack Directories..............................................................................................1-47
Database Data Files .............................................................................................................1-48
File Types ............................................................................................................................1-49
Naming Standards................................................................................................................1-51
Database Objects .................................................................................................................1-52
Forms File Standards ...........................................................................................................1-55
PL/SQL Packages, Procedures and Source Files .................................................................1-56
11i Manufacturing Functional Foundation Table of Contents

i
Reserved Words...................................................................................................................1-57
Summary..............................................................................................................................1-58
Applications Basics ................................................................................................................2-1
Applications Basics .............................................................................................................2-2
Objectives ............................................................................................................................2-3
Basic Applications Tools.....................................................................................................2-4
Overview of Concurrent Processing ....................................................................................2-6
Overview of Flexfields ........................................................................................................2-7
Overview of Alerts ..............................................................................................................2-8
Overview of Workflow........................................................................................................2-9
Summary..............................................................................................................................2-10
ERDs and Applications Technology.....................................................................................3-1
ERDs and Applications Technology....................................................................................3-2
Objectives ............................................................................................................................3-3
Entity Relationship Diagrams (ERDs).................................................................................3-4
What is an Entity?................................................................................................................3-5
Entities and Instances ..........................................................................................................3-6
Attributes .............................................................................................................................3-7
Relationships .......................................................................................................................3-8
Drawing Entities in ERDs....................................................................................................3-10
Drawing Attributes in ERDs................................................................................................3-11
Drawing Relationships in ERDs ..........................................................................................3-12
Perspectives of Relationships in ERDs................................................................................3-13
Reading Relationships in ERDs...........................................................................................3-14
Oracle Applications ERD Standards....................................................................................3-15
Key Flexfields......................................................................................................................3-18
Descriptive Flexfields ..........................................................................................................3-22
Flexfield Values...................................................................................................................3-24
Concurrent Managers...........................................................................................................3-27
Concurrent Processing .........................................................................................................3-30
Concurrent Manager Advanced Schedules ..........................................................................3-33
Standard Request Submission..............................................................................................3-35
Workflow.............................................................................................................................3-38
Function Security.................................................................................................................3-41
Login Security .....................................................................................................................3-43
AuditTrail ............................................................................................................................3-45
User Profiles ........................................................................................................................3-47
Document Sequences, Folders, Documents on the Navigator .............................................3-49
Attachments .........................................................................................................................3-51
Document Management and Help .......................................................................................3-53
AOL Data Dictionary Information.......................................................................................3-55
Currency and Language .......................................................................................................3-58
Summary..............................................................................................................................3-60
Development Topics...............................................................................................................4-1
Development Topics............................................................................................................4-2
Objectives ............................................................................................................................4-3
Interface Options .................................................................................................................4-4
Interface Table Diagram ......................................................................................................4-6
API Diagram........................................................................................................................4-8
Development Standards .......................................................................................................4-10
Summary..............................................................................................................................4-12
Exploring Applications Database .........................................................................................5-1
Exploring Applications Database ........................................................................................5-2
Objectives ............................................................................................................................5-3
Exploration Basics ...............................................................................................................5-4

ii
Listing Scripts......................................................................................................................5-6
Description Scripts...............................................................................................................5-27
Configuration Scripts...........................................................................................................5-32
Summary..............................................................................................................................5-43
11i Manufacturing Functional Foundation: Overview.......................................................6-1
11i Manufacturing Functional Foundation: Overview.........................................................6-2
Objectives ............................................................................................................................6-3
Agenda.................................................................................................................................6-4
Application Development Standards ...................................................................................6-6
The Applications Server Directory Structure.......................................................................6-7
Database Naming Conventions............................................................................................6-8
Development Standards .......................................................................................................6-10
Summary..............................................................................................................................6-12
Agenda.................................................................................................................................6-13
Entity Relationship Diagram Definitions.............................................................................6-14
Primary Key.........................................................................................................................6-15
Foreign Key .........................................................................................................................6-16
Primary Key Relationships ..................................................................................................6-18
Foreign Key Example ..........................................................................................................6-19
Database Diagramming Conventions ..................................................................................6-20
Practice Setup ......................................................................................................................6-21
Practice Overview................................................................................................................6-23
Practice 1 .............................................................................................................................6-24
Practice 1 Solution...............................................................................................................6-25
Practice 2 .............................................................................................................................6-26
Practice 3 .............................................................................................................................6-28
Practice 4 .............................................................................................................................6-30
Agenda.................................................................................................................................6-32
Oracle Manufacturing Applications.....................................................................................6-33
Oracle Inventory ..................................................................................................................6-34
Oracle Bills of Material .......................................................................................................6-36
Oracle Engineering ..............................................................................................................6-38
Oracle Cost Management.....................................................................................................6-40
Oracle Work in Process .......................................................................................................6-42
Oracle Work in Process Transactions ..................................................................................6-43
Oracle Purchasing................................................................................................................6-44
Purchasing Transactions ......................................................................................................6-46
Agenda.................................................................................................................................6-47
Importing Information .........................................................................................................6-48
Open Interface Model ..........................................................................................................6-50
Managing Open Interface Processing ..................................................................................6-52
Data Conversion ..................................................................................................................6-53
Detailed Conversion Plan ....................................................................................................6-54
Designing the Conversion Process.......................................................................................6-56
Developing Conversion Programs .......................................................................................6-58
Performing the Conversion..................................................................................................6-59
Summary..............................................................................................................................6-60
11i Manufacturing Functional Foundation: Inventory ......................................................7-1
11i Manufacturing Functional Foundation: Inventory.........................................................7-2
Objectives ............................................................................................................................7-3
Agenda.................................................................................................................................7-4
Oracle Inventory ..................................................................................................................7-6
Oracle Inventory Database Summary Diagram ...................................................................7-8

iii
Inventory Organizations ......................................................................................................7-9
Oracle Inventory: Organizations..........................................................................................7-10
Defining Organizations........................................................................................................7-12
Defining Organization Parameters for Additional Information ...........................................7-13
Locators and Subinventories................................................................................................7-14
Oracle Inventory: Subinventories and Locators...................................................................7-15
Defining Subinventories ......................................................................................................7-17
Defining Locators ................................................................................................................7-18
Oracle Inventory: Item Master.............................................................................................7-19
Defining Items .....................................................................................................................7-21
Degree of Item Control ........................................................................................................7-22
Oracle Inventory Item Controls ...........................................................................................7-23
Defining Item Controls ........................................................................................................7-25
Oracle Inventory Item Status ...............................................................................................7-26
Life Cycle of a Part: Using Item Status and Attributes........................................................7-28
Defining Item Status Codes .................................................................................................7-29
Item Categories Example.....................................................................................................7-30
Oracle Inventory: Item Categories.......................................................................................7-31
Defining Item Categories.....................................................................................................7-33
Oracle Inventory: Item Catalogs..........................................................................................7-34
Defining Item Catalogs........................................................................................................7-36
Practice 1 Setup ...................................................................................................................7-37
Practice 1 .............................................................................................................................7-39
Agenda.................................................................................................................................7-41
Oracle Inventory Transaction Flow .....................................................................................7-42
Oracle Inventory: Inventory Transactions and Item Controls.............................................7-44
Physical Inventory Process ..................................................................................................7-46
Oracle Inventory: Physical Inventory ..................................................................................7-47
Defining Physical Inventory ................................................................................................7-49
ABC Analysis Overview .....................................................................................................7-50
Oracle Inventory: ABC Analysis .........................................................................................7-51
Defining an ABC Compile ..................................................................................................7-53
Cycle Count Overview.........................................................................................................7-54
Oracle Inventory: Cycle Count ............................................................................................7-55
Oracle Inventory: Demand and Reservation Information ....................................................7-57
Practice 2 Setup ...................................................................................................................7-59
Practice 2 .............................................................................................................................7-60
Agenda.................................................................................................................................7-62
Oracle Applications Open Interfaces for Inventory .............................................................7-63
Major Tables: Open Interfaces.............................................................................................7-64
Inventory Transactions Open Interface Tables ....................................................................7-65
Open Interfaces: Inventory Setups.......................................................................................7-66
Inventory Setups Open Interface Tables..............................................................................7-67
Summary..............................................................................................................................7-68
11i Manufacturing Functional Foundation: Purchasing....................................................8-1
11i Manufacturing Functional Foundation: Purchasing.......................................................8-2
Objectives ............................................................................................................................8-3
Agenda.................................................................................................................................8-4
Oracle Purchasing Overview ...............................................................................................8-6
Purchasing Process Flow .....................................................................................................8-8
Agenda.................................................................................................................................8-9
Oracle Purchasing: Entity Relationships .............................................................................8-10
Suppliers ..............................................................................................................................8-12
Suppliers Window ...............................................................................................................8-13

iv
Oracle Purchasing: Requisitions ..........................................................................................8-14
Requisitions Window...........................................................................................................8-16
Purchasing Documents ........................................................................................................8-17
Oracle Purchasing: Purchasing Documents .........................................................................8-19
Purchase Orders Window ....................................................................................................8-21
Receiving .............................................................................................................................8-22
Receiving Transactions........................................................................................................8-24
Practice 1 Setup ...................................................................................................................8-25
Practice 1 .............................................................................................................................8-27
Agenda.................................................................................................................................8-29
Purchasing Open Interfaces .................................................................................................8-30
Purchasing Open Interface Tables .......................................................................................8-32
Summary..............................................................................................................................8-33
11i Manufacturing Functional Foundation: BOM and Engineering ...............................9-1
11i Manufacturing Functional Foundation: BOM and Engineering ....................................9-2
Objectives ............................................................................................................................9-3
Agenda.................................................................................................................................9-4
Oracle Bills of Material .......................................................................................................9-6
Oracle Bills of Material/Engineering Bills of Material Structures ......................................9-8
Defining a Bill of Material...................................................................................................9-10
Item Revision Control..........................................................................................................9-11
Oracle Bills of Material/Engineering Resources and Departments......................................9-12
Outside Processing Example ...............................................................................................9-13
Defining a Routing ..............................................................................................................9-14
Oracle Bills of Material/Engineering Routings ...................................................................9-15
Practice 1 Setup ...................................................................................................................9-17
Practice 1 .............................................................................................................................9-19
Practice 2 .............................................................................................................................9-21
Agenda.................................................................................................................................9-23
Oracle Engineering ..............................................................................................................9-24
Oracle BOM/Engineering Change Control..........................................................................9-26
Practice 3 Setup ...................................................................................................................9-28
Practice 3 .............................................................................................................................9-30
Agenda.................................................................................................................................9-32
Oracle Bills of Material/Engineering Open Interfaces.........................................................9-33
Oracle BOM/Engineering Interface Tables .........................................................................9-34
Summary..............................................................................................................................9-35
11i Manufacturing Functional Foundation: Work in Process ...........................................10-1
11i Manufacturing Functional Foundation: Work in Process ..............................................10-2
Objectives ............................................................................................................................10-3
Agenda.................................................................................................................................10-4
Discrete Versus Repetitive Manufacturing Process............................................................10-6
Oracle Work in Process Overview.......................................................................................10-7
Oracle Work in Process Operations.....................................................................................10-9
Oracle Work in Process: Discrete Jobs................................................................................10-11
Oracle Work in Process: Repetitive Schedules....................................................................10-13
Repetitive Schedules Summary Report ...............................................................................10-15
Agenda.................................................................................................................................10-16
Oracle WIP Transactions .....................................................................................................10-17
Oracle WIP Material Transactions.......................................................................................10-19
Material Transactions Window............................................................................................10-21
Oracle WIP: Move Transactions..........................................................................................10-22
Move Transactions Window................................................................................................10-24

v
Oracle WIP: Resource Transactions ....................................................................................10-25
Resource Transaction Window............................................................................................10-27
Oracle WIP: Completion Transactions ................................................................................10-28
Completion Transactions window .......................................................................................10-30
Oracle WIP: Work Order-less Completions ........................................................................10-31
Work Order-less Completions Window...............................................................................10-33
Practice 1 Setup ...................................................................................................................10-34
Practice 1 .............................................................................................................................10-36
Agenda.................................................................................................................................10-39
Oracle WIP: Open Interfaces ...............................................................................................10-40
Oracle WIP Transactions Open Interface Tables.................................................................10-41
Summary..............................................................................................................................10-42
11i Manufacturing Functional Foundation: Cost Management ........................................11-1
11i Manufacturing Functional Foundation: Cost Management ...........................................11-2
Objectives ............................................................................................................................11-3
Agenda.................................................................................................................................11-4
Oracle Cost Management.....................................................................................................11-6
Cost Information..................................................................................................................11-8
Agenda.................................................................................................................................11-9
Cost Type: Standard ............................................................................................................11-10
Cost Types: Average, FIFO, LIFO ......................................................................................11-12
Oracle Cost Management Resource and Overhead Costs....................................................11-14
Item Cost Summary and Details ..........................................................................................11-16
Practice 1 Setup ...................................................................................................................11-17
Practice 1 .............................................................................................................................11-19
Agenda.................................................................................................................................11-21
Oracle Cost Management Open Interfaces ..........................................................................11-22
Oracle Cost Management Interface Tables..........................................................................11-23
Summary..............................................................................................................................11-24

vi
Preface
Profile
Before You Begin This Course
Before you begin this course, you should have the following qualifications:
• Ability to perform queries and display data using SQL*Plus
• Thorough knowledge and proficiency in navigating Oracle applications
• Working experience with at least one of the Oracle Manufacturing

application modules
• Working experience with Oracle Applications System Administration,

Flexfields, Alerts, and Workflow
Prerequisites
1) At least one of the following Oracle application courses:
• Inventory
• Bills of Material
• Engineering
• Work in Process
• Purchasing
• Cost Management
2) Ability to perform queries and display data with SQL and SQL*Plus
How This Course Is Organized
This is an instructor-led course featuring lecture and hands-on exercises. Online

demonstrations and written practice sessions reinforce the concepts and skills
introduced.

vii
Related Publications
Oracle Publications
Title Part Number
Installation manuals by platform
Oracle Application Object Library/Workflow Manual A80844-01
Oracle Inventory Technical Reference Manual A90206-01
Oracle Bills of Material Technical Reference Manual A90198-01
Oracle Engineering Technical Reference Manual A90177-01
Oracle Work in Process Technical Reference Manual A81185-01
Additional Publications
• System release bulletins
• Installation and user’s guides
• readme files
• Oracle Magazine

viii
Typographic Conventions
Typographic Conventions in Text
Convention Element Example

Bold italic Glossary term (if The algorithm inserts the new key.
there is a glossary)
Caps and Buttons, Click the Executable button.

lowercase check boxes, Select the Can’t Delete Card check box.
triggers, Assign a When-Validate-Item trigger to the
windows ORD block.
Open the Master Schedule window.
Courier new, Code output, Code output: debug.set (‘I”, 300);

case sensitive directory names, Directory: bin (DOS), $FMHOME (UNIX)
(default is filenames, Filename: Locate the init.ora file.
lowercase) passwords, Password: User tiger as your password.
pathnames, Pathname: Open c:\my_docs\projects
URLs, URL: Go to http://www.oracle.com
user input,
User input: Enter 300
usernames
Username: Log on as scott
Initial cap Graphics labels Customer address (but Oracle Payables)

(unless the term is a
proper noun)
Italic Emphasized words Do not save changes to the database.

and phrases, For further information, see Oracle7 Server
titles of books and SQL Language Reference Manual.
courses, Enter user_id@us.oracle.com,
variables where user_id is the name of the user.
Quotation Interface elements Select “Include a reusable module component”
marks with long names and click Finish.
that have only
initial caps; This subject is covered in Unit II, Lesson 3,
lesson and chapter “Working with Objects.”
titles in cross-
references
Uppercase SQL column Use the SELECT command to view

names, commands, information stored in the LAST_NAME
functions, schemas, column of the EMP table.
table names

ix
Arrow Menu paths Select File—> Save.
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

Caps and Oracle Forms When-Validate-Item
lowercase triggers
Lowercase Column names, SELECT last_name
table names FROM s_emp;
Passwords DROP USER scott

IDENTIFIED BY tiger;
PL/SQL objects OG_ACTIVATE_LAYER
(OG_GET_LAYER
(‘prod_pie_layer’))
Lowercase Syntax variables CREATE ROLE role

italic
Uppercase SQL commands and SELECT userid
functions FROM emp;
Typographic Conventions in Navigation Paths
This course uses simplified navigation paths, such as the following example, to
direct 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 Batches
Summary.
2. (M) From the menu, select Query > Find.
3. (B) Click the Approve button.
Notations :
(N) = Navigator
(M) = Menu

x
(T) = Tab
(I) = Icon
(H) = Hyperlink
(B) = Button
Typographical Conventions in Help System Paths
This course uses a “navigation path” convention to represent actions you perform
to 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 General
Ledger 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 the
help 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 to
pinpoint 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 the
toolbar, or hold down the Control key and type 'h'.
A web browser window appears, containing search and navigation frames on

the left, and a frame that displays help documents on the right.
The document frame provides information on the window containing the

cursor. The navigation frame displays the top-level topics for your
responsibility, 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.

xi
3. You can navigate to other topics of interest in the help system, or choose
Close 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 you
want. Simply enter your query in the text field located in the top-left frame of the
browser window when viewing help, then click the adjacent Find button.
A list of titles, ranked by relevance and linked to the documents in question, is

returned from your search in the right-hand document frame. Click on whichever
title seems to best answer your needs to display the complete document in this
frame. If the document doesn't fully answer your questions, use your browser's
Back button to return to the list of titles and try another.

xii
Applications Architecture
Chapter 1
Chapter 1 - Page 1
Copyright  Oracle Corporat ion, 2001. All right s reserved.
ILT Schedule: Timing Topic

120 minutes Lecture
120 minutes Total
Chapter 1 - Page 2
Objectives
Objectives
After completing this lesson, you should be able to

do the following:
• Describe Applications network architecture
• Describe Applications database architecture
• Describe Applications file system architecture
• Describe Applications naming standards
Chapter 1 - Page 3
Applications Network Architecture
Applications Network Architecture
Desktop Application Database

Web
Server
Forms
Browser Server
Client Concurrent Processing

Server
Applet Data
Reports Server
Server
Admin
Browser Server
Oracle Applications uses the Internet computing architecture. The Internet

computing architecture shifts software administration from the desktop
onto the middle tier, which resides in the data center with the database
server, thus lowering administration costs.
The Internet computing architecture is a multi-tier computing model where

various functions of the Oracle Applications architecture are distributed
among multiple levels, or tiers. Although many physical machines may be
used in a configuration, scalability is derived from processing capabilities
on three separate levels: the desktop tier, the application tier, and the
database tier.
Chapter 1 - Page 4
Desktop Tier
Desktop Tier
Desktop
Browser
Client
Applet
Browser
®
The client interface is provided through a Java applet using a Java-

enabled web browser. The client can download the applet on demand and
the applet is cached locally for future use.
Forms Client Applet

The Forms Client Applet is a component of Oracle’s Developer application
development tool. The applet sends user requests to the forms server and
handles such responses as screen updates, pop-up lists, and cursor
movement. It can display any Oracle Applications screen and supports
field-level validation, multiple coordinated windows, and data entry aids
like lists of values.
Web Browser/JInitiator
The Forms Client Applet must run within a Java Virtual Machine (JVM) on
the desktop. For Oracle Applications the JVM is supplied by the JInitiator
program, which works in conjunction with the web browser.
Chapter 1 - Page 5
Forms Client Applet
Forms Client Applet
Desktop
Web
Client Server
Applet
Forms
JAR files Server
Java JAR files Concurrent Processing

Enabled JAR files Server
Browser
Reports
with Server
JInitiator
Admin
Server
The Forms Client Applet is a general-purpose applet that supports all

Oracle Applications products including those with customizations and
extensions. The Forms Client is packaged as Java ARchive (JAR) files
that contain all the Java classes typically required to run Oracle
Applications forms. JAR files are digitally signed and should not be
opened or expanded on-site.
The required and commonly used JAR files are downloaded from the Web
Server once at the beginning of the client’s first session. Afterwards it
remains in the browser’s local disk cache, ready for future sessions until
an updated version is released. All updates are installed on the application
tier and downloaded to the client automatically through the use of
JInitiator. Other less commonly used JAR files are downloaded as
needed.
Chapter 1 - Page 6
JInitiator
JInitiator
Desktop
Web
Client Server
Applet
Forms
Server
Java Concurrent Processing

Enabled Server
Browser
Reports
with Server
JInitiator
Admin
Server
JInitiator is Oracle's Java Virtual Machine (JVM) that is implemented on

the desktop client as a plug-in (Netscape Communicator) or ActiveX
component (Microsoft Internet Explorer). JInitiator allows Oracle
Applications to run under the most current Java code set and is the
preferred method of accessing Oracle Applications.
When an end-user enters the desired Oracle Applications signon URL

within the web browser, the browser will execute Oracle JInitiator. If
Oracle JInitiator has not been previously installed, the browser will
download the necessary installation executable to the desktop client.
Once installed, Oracle JInitiator will run the Forms Client Applet and start
an Oracle Applications session.
Chapter 1 - Page 7
Application Tier
Application Tier
Application
Web
Server
Forms
Server
Concurrent Processing
Server
Reports
Server
Admin
Server
The Application Tier is the location of servers that provide the business
logic and code processing. This tier is sometimes referred to as the middle
tier. There are five servers that comprise the application tier:
• The Web Server

• The Forms Server
• The Concurrent Processing Server
• The Reports Server
• The Admin Server
This tier provides the communication between the desktop tier and the
database tier. The application tier also supports load balancing among
multiple forms servers to provide optimal scalability and processing.
Chapter 1 - Page 8
Web Server
Web Server
Application
Web
Server
Forms
Server
Server
Reports
Server
Admin
Server
The Web Server processes the requests it receives over the network from
the desktop clients. The Web Server consists of an HTTP listener, load
balancer, and needed modules.
1 The HTTP listener accepts incoming HTTP requests (URLs) from
desktop tier (browsers). If possible, the HTTP listener services the
request itself, for example, by returning a simple HTML web page.
2 If the page referenced by the URL needs some kind of advanced
processing, e.g. PL/SQL or Java, the listener passes the request on
to the module.
3 The load balancer determines the least loaded Forms Server name
and passes the information back to the desktop tier by means of a
dynamically created HTML page.
4 The desktop tier can then connect directly to the Forms Server by
the name it has been provided.
5 From this point on, all communication is between the client tier and
the Forms Server with the Forms Server handling the
communication with the Oracle8i database.
Chapter 1 - Page 9
Forms Server
Forms Server
Application
Web
Server
Forms
Server
Server
Reports
Server
Admin
Server
The Forms Server hosts the Oracle Applications forms and the forms
runtime engine. The Forms Server is a Developer Server component that
mediates the communication between the desktop tier and the Oracle8i
database, displaying client screens and causing changes in the database
records based on user actions. Data is cached on the forms server and
provided to the client as needed, such as when scrolling through multiple
order lines. The Forms Server communicates with the desktop tier in one
of three ways:
• a TCP/IP connection
• a standard HTTP connection
• a secure HTTPS connection
The Forms Server communicates with the Oracle8i database using Net8.
Chapter 1 - Page 10
Concurrent Processing Server
Concurrent Processing Server
Application
Web
Server
Forms
Server
Server
Reports
Server
Admin
Server
Most interaction with Oracle Applications data is done through Oracle

Applications forms. There are also reporting programs and data updating
programs that periodically need to be run. These programs may contain a
very large number of computations, so to ensure that they do not interfere
with interactive operations, they can be configured to run on a separate
machine called the Concurrent Processing Server.
Processes that run on the Concurrent Processing Server are called

concurrent programs, and operate in the background while users continue
to work on other tasks. You submit a request to run concurrent programs
through Oracle Applications forms. This inserts a row into a database
table specifying the program to be run. A monitoring process reads the
table and assigns the request to one of several concurrent managers
running on one or more Concurrent Processing Servers. The concurrent
manager then runs the program generating log and output files on the
Concurrent Processing Server.
Chapter 1 - Page 11
Accessing Concurrent Processing Output
Accessing Concurrent Processing Output
Application
Web
Server
Forms
Server
Server
Reports
Server
Admin
Server
The Concurrent Processing Server communicates with the Oracle8i

database using Net8. The results of a concurrent report are passed back
to the Web Review Agent. The Web Review Agent passes a file
containing the entire report to the Forms Server. The Forms Server
passes the report back to the user’s browser a page at time.
You can use system settings to control the size of the files and pages
passed through the system.
Chapter 1 - Page 12
Reports Server
Reports Server
Application
Web
Server
Forms
Server
Server
Reports
Server
Admin
Server
The Reports Server is used to produce reports for Oracle Business

Intelligence System (BIS) products. This server is automatically installed
on the same node as the Concurrent Processing Server, and its reports
are contained in the same directory with regular concurrent processing
reports. However, reports generated by the Reports Server are monitored
and administered separately from concurrent reports.
Chapter 1 - Page 13
Administration Server
Administration Server
Application
Web
Server
Forms
Server
Server
Reports
Server
Admin
Server
The administration server is the machine from which you maintain the data
in your Oracle Applications database. You carry out the following
operations from this server:
Installing and upgrading the database

This is only done when installing a new release or upgrading to a new
release.
Applying database updates

Most bug fixes consist of new files and scripts that update database
objects. Use AutoPatch to update software on the database and the
application tier servers.
Maintaining the Applications data

Some features such as multi-lingual support and Multiple Reporting
Currencies require regular maintenance to ensure updates are propagated
to the additional schemas used by these features. The AD Administration
program allows you to do this and other file system and database
maintenance tasks.
Chapter 1 - Page 14
Database Tier
Database Tier
Database
Data
Server
The database tier holds all the data stored and maintained by the Oracle
Applications system. It also contains some processing code that is stored
in the database to optimize performance. In Release 11i the database also
includes the Oracle Applications help files.
More specifically, the database tier contains Oracle8i Server files and an
Oracle Applications database instance that physically stores the tables,
indexes, and other database objects for your installation.
By definition the data server does not communicate directly with the
desktop tier, but rather with the servers on the application tier that mediate
these communications.
Chapter 1 - Page 15
Database Architecture
Database Architecture
Oracle8i Oracle Applications

Database File System
Business data Processing Programs
Within its multi-tier architecture, Oracle Applications stores its business

data in Oracle8i database tables. Additional database objects such as
indexes and views are used when processing these tables. Other objects
like code modules in the form of stored procedures and Help files are also
contained in the database.
Chapter 1 - Page 16
Oracle Applications Database Objects
Oracle Applications Database Objects
Data Objects Code Objects
Tables Triggers
Views
Packages
Indexes
Synonyms
Sequences
®
Oracle Applications uses an Oracle8i database to store its database

objects. These objects store both business data as well as some of the
code modules. In general, each application module has its own set of
database objects. These objects can be broadly defined into two
categories.
Data objects are used for storing and accessing business data. These
objects include tables, indexes, and sequences.
Code objects are used to process the data. Code objects are stored in
the database and used for optimizing application processing. Code objects
include triggers, packages, synonyms and views.
Chapter 1 - Page 17
APPS Schema
APPS Schema
APPS Schema
INV Schema
Views
Triggers
GL Schema
Synonyms
Packages
Oracle Applications is tightly integrated. A procedure in one schema may

access data in a second schema and call a function in a third. To
accomplish this, the procedure needs access to all three schemas.
However, maintaining the access rights to all three is time-consuming and
error prone. Using the APPS schema solves this problem.
Each product’s schema grants full privileges to the APPS schema. The
APPS schema has synonyms to all base product tables and sequences.
Tthe APPS schema contains all code objects which access the data
objects in the product schemas.
Chapter 1 - Page 18
Additional Schemas
Additional Schemas
HR APPLSYSPUB APPLSYS
PAY APPS
AOL
PER
AD
The data objects for some products are combined within a single schema.
For example, tables for the Human Resources products (PER, PAY, etc.)
are combined under the HR schema; tables for the Application
Technology Layer products (AOL, AD, etc.) are combined under the
APPLSYS schema.
There is an additional schema, APPLSYSPUB, that is used only during

the signon process which does not actually own any database objects. It
only has access to 1 database object, FND_USER_VIEW, and it only has
select rights on it.
The APPS_MRC schema is used if you install the Multiple Reporting

Currencies option.
Chapter 1 - Page 19
Multiple Organizations Views
Multiple Organizations Views
SO_Headers_All Table
Eastern Region
View
Western Region
View
Org_Id
Column
®
You can support multiple organizations running any Oracle Applications

product with a single installation. These different organizations can reflect
different sets of books, different business groups, legal entities, operating
units or inventory organizations. Organizations that share the same
functional currency, Accounting Flexfield, and calendar can post to the
same set of books.
When you run any Oracle Applications product, you first choose an
organization either implicitly by choosing a responsibility or explicitly in a
Choose Organization window. After you have chosen a particular
organization, all forms and reports display information for that organization
only.
This Multiple Organization Architecture is a virtual partitioning solution

which secures information by operating unit using views within the APPS
schema. These view definitions use the values in the Org_Id column to
guarantee that only the information appropriate for that organization is
returned to the user.
Chapter 1 - Page 20
Multiple Reporting Currencies
Multiple Reporting Currencies
Primary Set of Books Reporting Set of Books

Currency: Currency:
USD BEF
Primary Responsibility Reporting Responsibility
STANDARD Data MRC Data

Group Group
APPS Schema APPS_MRC Schema

®
The Multiple Reporting Currencies (MRC) feature allows you to report and
maintain accounting records at the transaction level in more than one
functional currency. You do this by defining one or more reporting sets of
books in addition to your primary set of books. In your reporting sets of
books, you maintain records in a functional currency other than your
primary functional currency. The data for the reporting set of books is
stored in its own schema having its own tables and views.
MRC is supported for the following products: General Ledger, Fixed

Assets, Cash Management, Cost Management, Global Accounting
Engine, Accounts Payable, Projects, Purchasing, and Accounts
Receivable.
Chapter 1 - Page 21
File System Architecture
File System Architecture
<env name>APPL < env name >ORA <env name>DB

< env name >COMN < env name >DATA
(to Product (to Log / (to Oracle8 (to Oracle (to Oracle
Directories) Out and and Tools Applications 8i Files)
Java Files) Files) Database Data
Files)
Oracle Applications stores files within several different file systems.

Through the next several slides, we will discuss the contents of each of
these file systems.
Chapter 1 - Page 22
APPL_TOP
APPL_TOP
<env name>APPL
<db name>.
name>.env
env admin au fnd inv
11.5.0 11.5.0 11.5.0 11.5.0
Administrative Files Product Files
The Oracle Applications file system contains the product files for Oracle
Applications itself. The top level directory path is defined in an
environment variable APPL_TOP.
For both an installation and upgrade of Oracle Applications, Rapid Install

creates the new APPL_TOP, or top Applications directory and defaults the
APPL_TOP directory value to <db name>APPL. This variable is used in
subsequent directory definitions, and is also used as a term to refer to a
particular Oracle Applications file system.
Technical note:
The <db name>.env file is a very important file containing parameters
defining the Oracle Applications environment. Typically, Rapid Install
creates the <db name>.env file during the installation. Many of the
parameters located in the <db name>.env file define important directories
within the Oracle Applications file structure. For example, the APPL_TOP
directory is identified in the environment parameter APPL_TOP. Additional
parameters point to product top directories.
Chapter 1 - Page 23
APPL_TOP
APPL_TOP
<env name>APPL
<db name>.
name>.env
env admin au fnd inv
11.5.0 11.5.0 11.5.0 11.5.0
Administrative Files Product Files
Each product has its own subdirectory. Since products can exist at
different version levels, the version is typically reflected in the subdirectory
name. Keep in mind that multiple releases and product versions cannot
exist in a single APPL_TOP directory.
The product subdirectory name is defined in an environment variable

<PROD>_TOP, where < PROD> is the product short name.
For example, the paths to these directories would be defined in the

following declarations in the <db name>.env file:
AU_TOP=APPL_TOP/au/11.5.0
FND_TOP =APPL_TOP/fnd/11.5.0
INV_TOP=APPL_TOP/inv/11.5.0
Chapter 1 - Page 24
Product Directories
Product Directories
<PROD>_TOP
admin help java media patch resource
bin html lib mesg plsql sql
forms include log out reports
The product directory contains many subdirectories that group the

different files for that product. A typical product directory will have the
subdirectories shown, however, there may be differences based upon
configuration.
Chapter 1 - Page 25
Admin Directory
Admin Directory
<PROD>_TOP
driver import odf sql
The admin subdirectory contains files used by AutoUpgrade to upgrade

products to the current release. The admin subdirectory has several
subdirectories of its own:
driver: the upgrade driver files (.drv). The upgrade process is divided into
several phases. Phase driver files specify processing by phase. Example
files: glseq.drv creates sequences for the General Ledger (GL) product
during the sequence phase; glfile.drv, lists the GL files needed to run the
application, gldep.drv, specifies dependencies between GL and other
products so that upgrade jobs between products are processed in the
correct order.
import: the import files used to upgrade seed data.
odf: the object description files used to create tables and other database
objects.
sql: the SQL scripts and PL/SQL scripts used to upgrade data.
Chapter 1 - Page 26
Bin Directory
Bin Directory
<PROD>_TOP
The concurrent programs, other C language programs and shell scripts for
each product are stored in its respective bin directory. Of particular
importance to Oracle Applications are the FND_TOP/bin and AD_TOP/bin
directories. Some of the programs you will find here include:
f60webmx: the applications form processor (in FND_TOP/bin)

FNDLIBR: the concurrent manager (in FND_TOP/bin)
startmgr: a Unix shell script to start the concurrent manager (in
FND_TOP/bin)
fdfcmp: the flexfield compiler (in FND_TOP/bin)
FNDMDGEN: a message file generator (in FND_TOP/bin)
adadmin: the AD Administration utility (in AD_TOP/bin)
adpatch: the AutoPatch utility (in AD_TOP/bin)
Chapter 1 - Page 27
Forms Directory
Forms Directory
<PROD>_TOP
US
The forms directory contains Oracle Forms files. Oracle Forms may be
portable source files (.fmb files) or generated runtime files (.fmx files). The
installation utility generates form files by converting the .fmb source file to
.fmx runtime files. The source files are stored in AU_TOP/forms so
generation of runtime files can be done more easily.
A subdirectory exists for the language(s) installed. This subdirectory is

named according to the language, e.g., /US for American English forms,
/D for German forms, /F for French forms.
Chapter 1 - Page 28
Help Directory
Help Directory
<PROD>_TOP
US
The help directory contains the online help source files. These files are
imported into the database during an install or an upgrade to optimize the
performance of online help. Under the help directory, there is a language
directory to store the help files for each language in which your are
running Oracle Applications.
Chapter 1 - Page 29
HTML Directory
HTML Directory
<PROD>_TOP
The html subdirectory contains HTML, Javascript, and Java Server Page
files used by various products. These files are used primarily by products
that have a Self-Service interface. The Javascript (.js) and Java Server
Page (.jsp) files are kept in the main directory. HTML files are kept in
subdirectories by language.
Chapter 1 - Page 30
Include Directory
Include Directory
<PROD>_TOP
The include directory contains header (.h) files. These files may be
required by the files contained in the lib directory for the relinking process.
Note: Not all products have an include directory.
Chapter 1 - Page 31
Java Directory
Java Directory
<PROD>_TOP
make jar
*.jar
®
This directory is used to initially store Java files. During installation or

upgrade, the files are copied to the directory identified by the JAVA_TOP
environment variable (this directory is defined in the environment file you
create during the installation process). This is done to optimize
processing.
For each product that uses Java, there will be one or more Java ARchive
(JAR) files under the jar directory. There will also be a product specific
.dep file under the make directory that specifies the dependencies
between this product and other products using Java.
Chapter 1 - Page 32
Lib Directory
Lib Directory
<PROD>_TOP
At some time, you may need to relink Applications programs, for example
if you upgrade the Oracle8i server. The lib subdirectory contains files
pertinent to the process of relinking Applications programs:
object files: (.o files), one for each C program to relink.
library file: (.a file) the compiled C code common to that product’s
programs.
makefile: (.mk file) specifying how to relink the .o file(s) with the .a file(s)
to create the newly linked C programs.
Chapter 1 - Page 33
Log and Out Directories
Log and Out Directories
<PROD>_TOP
When the concurrent managers run Oracle Applications reports or data

update programs, they write output files as well as diagnostic log files and
temporary files, to directories defined during the installation process.
There are two methods for storing log and output files: 1) in each product’s
log and out directories, which is the default or 2) a common log and output
subdirectory.
The log directory holds concurrent log files from each concurrent request
as well as the concurrent manager log files. The out directory holds the
concurrent report output files.
The default locations for these two files are <PROD>_TOP/log and
<PROD>_TOP/out, but you can change the default directory and the
default file names by changing the APPLLOG and APPLOUT environment
variables in the <db name>.env file.
You can consolidate all product log and out files into one directory by
defining the APPLCSF environment variable in the <db name>.env. This
parameter identifies a directory to hold all log and output files.
Chapter 1 - Page 34
Media Directory
Media Directory
<PROD>_TOP
The Applications Forms Client Applet displays graphics in the form of .gif
files. The media directory contains all product specific .gif files.
Chapter 1 - Page 35
Mesg Directory
Mesg Directory
<PROD>_TOP
forms include log US.msg

US.msg reports
Applications forms display messages at the bottom of the screen and in

pop-up boxes. Applications concurrent programs also print messages in
their log and output files.
These messages can be translated into different languages and are stored
in message files separate from the forms and programs. Each product’s
mesg directory contains one or more files for the language-specific
messages that the product uses:
• .msb files contain the binary messages used at runtime.

• a standard American English install will contain a US.msb file.
• an equivalent German message file will be titled D.msb.
Chapter 1 - Page 36
Patch Directory
Patch Directory
<PROD>_TOP

115
driver sql odf import

®
Any updates to Oracle Applications data or data model use a directory

named patch to store the patch files. Patch files are grouped by release
within the following subdirectories:
• driver: contains the driver files (.drv). Phase driver files specify
processing by phase.
• sql: contains sql (.sql) and PL/SQL (.pls) scripts used to update the
database.
• odf: contains object description files (.odf) to update the data
model.
• import: contains lct and slt files to update the seed data.
Chapter 1 - Page 37
PLSQL and Resource Directories
PLSQL and Resource Directories
<PROD>_TOP
These directories are used for unloading PL/SQL libraries used by

Applications reports and forms.
• The files in the plsql subdirectory (.pll files) are used by Oracle
Reports.
• The files in the resource subdirectory (.pll and .plx files) are used by
Oracle Forms.
After these files are unloaded, they are moved to equivalent subdirectories
under the AU_TOP directory.
Note: Not all products have PL/SQL libraries.
Chapter 1 - Page 38
Reports Directory
Reports Directory
<PROD>_TOP
US
This directory contains the report files for this product. For each report
there is a portable binary .rdf file. The AD Administration utility can
regenerate these reports by converting them to their executable format
(.rex files) and then back to portable format. This is usually recommended
so the PL/SQL is optimally compiled for the platform.
Reports for non-English languages are stored in their own language-

specific directory under the reports directory.
Chapter 1 - Page 39
SQL Directory
SQL Directory
<PROD>_TOP
There are many SQL*Plus scripts used by Oracle Applications for

concurrent processing. These scripts typically produce reports or perform
concurrent processing. These scripts are stored as .sql files in this
subdirectory.
Chapter 1 - Page 40
AD Directory
AD Directory
<env name>APPL
<db name>.
name>.env
env admin au ad fnd
11.5.0 11.5.0 11.5.0 11.5.0
admin bin lib
AD stands for Applications DBA. The Applications DBA product is a set of

tools for installing, upgrading, and administering the Oracle Applications
environment. The ad directory contains utilities such as AutoUpgrade,
AutoPatch (adpatch) and the AD Administration (adadmin) utility.
Chapter 1 - Page 41
AU Directory
AU Directory
<env name>APPL
<db name>.
name>.env
env admin au ad fnd
11.5.0 11.5.0 11.5.0 11.5.0
admin forms plsql resource java reports
AU stands for Application Utilities. The AU_TOP directory contains

product files that are consolidated in a single location for optimal
processing. These files include:
• PL/SQL libraries used by Oracle Reports. These are also stored in

the products’ plsql subdirectories.
• PL/SQL libraries used by Oracle Forms. These are also stored in
the products’ resource subdirectories.
• Oracle Forms source files. These are also stored in the products’
forms subdirectories.
• A copy of all Java files used by JInitiator when regenerating the
desktop client jar files. The public copy of all Java files are stored in
JAVA_TOP.
Chapter 1 - Page 42
Admin Directory
Admin Directory
<env name>APPL
<db name>.
name>.env
env admin au ad fnd
11.5.0
adovars .env
adovars. adrelink preupg restart
adconfig..txt
adconfig adsetenv log <db name>
applprod.. txt
applprod out
applora.. txt
applora
log out restart
®
The APPL_TOP/admin directory contains files and scripts used by the

AutoUpgrade utility during the upgrade process. These include:
• a custom environment file defining certain file locations
(adovars.env)
• scripts run during the upgrade
• text files read by AutoUpgrade
• a preupg directory containing product-specific pre-upgrade scripts
• log and out directories for upgrade log and output files
• a restart directory where AD programs create restart files
Most AD programs put their log, out and restart files in a separate <db
name> subdirectory. The value for <db name> comes from the
TWO_TASK or ORACLE_SID parameters. Some programs when run from
the command line, cannot access the <db name> value and therefore
store their log, out, and restart files in the log, out and restart directories
directly under the APPL_TOP/admin directory.
Chapter 1 - Page 43
Admin Directory Text Files
Admin Directory Text Files
<env name>APPL
<db name>.
name>.env
env admin au ad fnd
11.5.0
adovars .env
adovars. adrelink preupg restart
adconfig..txt
adconfig adsetenv log <db name>
applprod.. txt
applprod out
applora.. txt
applora
log out restart
®
There are many text files stored under the admin directory. These files are
used by many different utilities. Some of the files include:
• adconfig.txt: environmental configuration variable values

• adlinkbk.txt: files adrelink should backup rather than delete
• applcust.txt: registered customizations
• applora.txt: minimum or required settings for database initialization
parameters
• applprod.txt: products available in this release
• applterr.txt: territory description for Localizations
Chapter 1 - Page 44
Common Components Directory
Common Components Directory
< env name>COMN
xml jdbc java out log html admin**

admin util
oracle apps.zip
Apache JRE118
*.zip
apps US WebTools
mrp gl fnd icx *contains

(unzipped into) Rapid
jar jar jar html Install
scripts
fndewt.jar
fndewt.jar icxcabo.zip
icxcabo .zip
fndswing.jar
fndswing .jar
®
The <env name>COMN, or COMMON_TOP, directory contains directories

and files that are used across products or are used in conjunction with
other third-party products. This directory also contains the consolidated
log and output directories used by concurrent processing.
Unlike previous releases, Release 11i supports the placement of the java
directory (JAVA_TOP) and the HTML directory (OAH_TOP) anywhere in
your file system.
Note: Unlike APPL_TOP, there is no environment variable that points

directly to COMMON_TOP. However, if a standard installation or upgrade
is done, the environment variable OAD_TOP will point to the directory that
is COMMON_TOP.
Chapter 1 - Page 45
Copying Java Files: apps.zip
Copying Java Files: apps.zip
< env name>APPL < env name>COMN
java
au
11.5.0 apps.zip jdbc xml oracle
apps
java
fa gl
apps.zip
jar jar
Oracle Applications Release 11i makes extensive use of Java. Many

Oracle Applications products use Java on the front end for forms and on
the back end for data processing. Java files are installed into Oracle
Applications product directories and then copied to directories under the
Common Components directory to facilitate processing.
Apps.zip is a patchable archive of all Java class files required by Oracle

Applications. Individual Java class files are never present on the file
system. Apps.zip is located in AU_TOP/java and a public copy is stored
under JAVA_TOP. The public copy is the one utilized in a web server
environment, as the web server can see the JAVA_TOP stored apps.zip
but, for security reasons, cannot access the APPL_TOP apps.zip directly.
Chapter 1 - Page 46
Technology Stack Directories
Technology Stack Directories
<env name>ORA <env name>DB
8.0 iAS 8.1
forms60 graphics60 Apache bin lib
(Oracle8i)
java
Apache modplsql BC4J
reports60
jserv perl
To take advantage of the technology stack components’ latest features,

there are multiple ORACLE_HOME directories under the Technology
Stack directories. This slide shows which technology stack components
are located in each directory.
Chapter 1 - Page 47
Database Data Files
Database Data Files
Disk 1
cntrl01
log01a
log02a
Disk 2 rbs01 Disk 3
cntrl02
cntrl03
log01b Disk 4
log02b product
system01 temp01 data
ctxd01
product
index
The <env name>DATA file system contains the .dbf files that comprise the
Oracle Applications database itself. The Rapid Install utility installs all the
system, data, and index files across four disks. You can specify mount
points and directory names during the installation. Oracle Applications
Release 11i uses an Oracle8i database server.
Chapter 1 - Page 48
File Types
File Types
• Executables and component files

• DataMerge files
• Forms files
• Java ARchive files
• Log and output files
• PL/SQL files
• Reports files
• Message files
The Oracle Applications file system contains a variety of files. This list
describes some of the types of files you will find in the file system:
.a Library files that contain compiled C code

.ctl DataMerge control file
.dat DataMerge Import/Export parameter file
.dmp Import/Export data export file
.drv Driver files
.env Environment files in UNIX
.exp DataMerge data export file
.fmb Binary forms files
.fmx Executable forms files
.h C header files
.jar Java Archive files
.log Log files
Chapter 1 - Page 49
File Types
File Types
• Executables and component files

• DataMerge files
• Forms files
• Java ARchive files
• Log and output files
• PL/SQL files
• Reports files
• Message files
.msb Binary message files

.o Object files us ed t o relink Applicat ions
.odf Object Des cript ion Files
.out Output files
.pdf Acrobat files or report output
.plb PL/SQL package bodies
.pll PL/ SQL s hared libraries
.pls PL/SQL package specifications
.rdf Oracle Reports files (non-executable)
.req Log files from a concurrent reques t
.rex Oracle Reports executables
.sql SQL*Plus s cripts
Chapter 1 - Page 50
Naming Standards
Naming Standards
• Database objects
• Form file standards
• PL/SQL packages and procedures
• Reserved words
INSTRUCTOR NOTE:
The definitive source of information on Naming Standards is the Oracle

Applications Developer's Guide, Release 11i. In Chapter 31 of that
manual, it discusses these items in much more detail.
Chapter 1 - Page 51
Database Objects
Database Objects
• Includes a header with name, purpose, arguments,

special usage notes, and creation/update history.
• Tables - prod_objects
• Views - table_V or table_criteria_V
• Triggers - table_Ti
• Synonyms - table or view
• Constraints - table_PK, table_Ui, or table_Fi
Tables: prod is the short name of the product. objects is the object stored
in the table and should be plural. The table name should be 20 characters
or less.
View: table is the name of the root table the view is based on. The criteria
is a qualifier of the objects shown by the view. Use the criteria qualifier if
using table name alone is not unique, the view is based on a join of 2 or
more tables, the view contains a WHERE clause, or the view is unusual.
Triggers: table is the name of the table on which the trigger is based, and
i is a unique ID starting at 1.
Synonyms: Your synonym should have the same name as the table or
view it is based on.
Constraints: _PK is for Primary Keys. _Ui is for unique indexes. _Fi is
for foreign keys. table is the name of the table on which the constraint is
created, while I is a unique id starting at 1. You should name all of your
constraints so that you can enable or disable them easily.
Chapter 1 - Page 52
Database Objects
Database Objects
• Packages - prod_module or prod_description

• Procedures - verb_noun
• Table Handler - table_PKG
• Private Pkgs - package_PRIVATE
• Forms PL/SQL - prod_verb_noun
Packages: prod is the product short name, module is a functional

module, and description is a one or two word explanation of the purpose.
Stored package names should be 24 characters or less.
Packaged Procedures: verb_noun is a brief explanation of the purpose.
Table Handler Package and Procedures: table is the name of the table
on which the package acts. The package name should be 24 characters
or less.
Private Packages: package is the name of the owning package.
Forms PL/SQL Program Units: prod is the product short name, and
verb_noun is a brief explanation of the purpose.
Chapter 1 - Page 53
Database Objects
Database Objects
• PL/SQL Vars. - variable or X_variable

• PL/SQL Global - G_variable
PL/SQL Variables: variable should be a logical, meaningful, and concise

name. Precede variable name with X when the variable is used in a SQL
statement, so that there is no possibility of conflicts with database object
names or confusion as to which are PL/SQL variables and which are
database
objects.
PL/SQL Global Variables: variable should be a logical, meaningful, and

concise name. Precede variable name with G to distinguish global
variables from local variables.
Chapter 1 - Page 54
Forms File Standards
Forms File Standards
• Forms Files - pppggxxx.fmb
ppp is the two or three character product short name, gg

is a two–character abbreviation for the functional group,
and xxx is a three–character abbreviation for the
explanation of the purpose.
fmb is the suffix for the source binary file, and fmx is the
suffix for the executable binary file.
All file names must be no greater than 8 chars in length plus a three
character extension (FILENAME.ext). The files names must be all caps
except for the extension. This will provide a consistent naming scheme
across all platforms.
Chapter 1 - Page 55
PL/SQL Packages, Procedures and Source Files
PL/SQL Packages, Procedures and

Source Files
• PL/SQL Stored Package Source File Names

pppgxxxs.pls or pppgxxxb.pls
• PL/SQL Table Handlers Source File Names
pppgixxs.pls or pppgixxb.pls
• PL/SQL Library File Names
pppggxxx.pll, pppggxxx.plx, or pppggxxx.pld
• Icon File Names
ppxxxxxx.ico or ppxxxxxx.bmp
PL/SQL packages and procedures are documented slightly differently.

Packages do not have Arguments sections and procedures do not need to
have History sections. Begin all SQL and PL/SQL files with the following
lines (after the copyright header):
SET VERIFY OFF
WHENEVER SQLERROR EXIT FAILURE ROLLBACK;
End all SQL and PL/SQL files with the following lines:
COMMIT;
EXIT;
ppp is the two or three character product short name, gg is a one or two
character abbreviation for the functional group, and xxx is a character
abbreviation for the explanation of the purpose. s indicate a specification
file, and b indicates a body file. Each file defines only one package
specification or body.
Chapter 1 - Page 56
Reserved Words
Reserved Words
In addition to all words reserved by Oracle8, PL/SQL,

and Oracle Forms, do not use any words that begin
with the following letters (including the words
themselves):
• FOLDER
• CALENDAR
• APPCORE
Chapter 1 - Page 57
Summary
Summary
In this lesson, you should have learned how to:

• Describe Applications network architecture.
• Describe Applications database architecture.
• Describe Applications file system architecture.
• Describe Applications naming standards.
Chapter 1 - Page 58
Applications Basics
Chapter 2
Applications Basics
Chapter 2 - Page 1
Applications Basics
Applications Basics

60 minutes Lecture
60 minutes Total
Applications Basics
Chapter 2 - Page 2
Objectives
Objectives

do the following:
• Use basic Applications tools
• Describe concurrent processing
• Describe flexfields
• Describe alerts
• Describe workflow
Applications Basics
Chapter 2 - Page 3
Basic Applications Tools
• (Help) About Oracle Applications

• (Help) Record History
• (Help) Diagnostics è Examine
• (Help) Diagnostics è Examine … choose
$DESCRIPTIVE_FLEXFIELD$ block
$ENVIRONMENT$ block
$PROFILES$ block
• (Help) Diagnostics è Examine … choose SYSTEM
block … choose LAST_QUERY field
The purpose of the commands shown above.
* Shows Applications version, Form shortname, Form version

* Shows primary table/view form is using
* Shows values of fields not visible on form
* Shows user-friendly names of Descriptive Flexfields
* Shows values of primary environment variables
* Shows value in effect for any given profile option for that user.
* Shows the SELECT statement that was last executed by your form.
Note: Should also mention the FORM_STATUS and ERROR_ITEM
fields in this block.
Applications Basics
Chapter 2 - Page 4
• (Help) Diagnostics è Display Database Error

• (Help) Diagnostics è Trace (checkbox)
• (Navigate) Concurrent è Program è Define
• Utilities: SQL Trace profile option
The purpose of the commands shown above.
* Shows any database error message.

* Turning on/off forms tracing. Trace file (*.trc) is put into
user_dump_dest. If user does not know value of user_dump_dest,
they can look at the init.ora file ($ORACLE_HOME/dbs) or run this
statement. select name, value from v$parameter where name =
‘user_dump_dest’;
* You can do two things here. You can check the "Enable Trace"
checkbox. This will turn on SQL tracing at the session level for the
program. For Oracle Reports, you can also put the line
"TRACEOPTS=TRACE_ALL" into the "Options" field. This will do
Reports runtime tracing.
* This profile option can only be set by the System Administrator.
Applications Basics
Chapter 2 - Page 5
Overview of Concurrent Processing
Overview of Concurrent Processing
• Concurrent requests
• Concurrent programs
• Concurrent managers
Applications is undergoing a transformation. Prior to 11i, most user

interaction was done through forms. In 11i, the bulk of the interaction is
done through the self-service web forms. Concurrent Processing is in
place to support the forms-based users.
For forms-based users, they can run reports from the data entered into the
system. When a report is needed, the command to run the report is a
concurrent request. The program that generates the report is a concurrent
program. Concurrent programs are controlled by a concurrent manager.
Each time a users request a concurrent program to be run, their request is

inserted into a database table, and is uniquely identified by a request ID.
Concurrent managers read requests from this table.
A concurrent request proceeds through three, possibly four, life cycle

stages or phases. Within each phase, a request’s condition or status may
change. The various phases that a concurrent request can go through are
Pending, Running, Completed, and Inactive.
Applications Basics
Chapter 2 - Page 6
Overview of Flexfields
Overview of Flexfields
• Key flexfields
• Descriptive flexfields
A flexfield is a field made up of sub–fields, or segments. A flexfield

appears on your form as a pop–up window that contains a prompt for each
segment. Each segment has a name and a set of valid values. There are
two types of flexfields: key flexfields and descriptive flexfields.
Most organizations use ”codes” made up of meaningful segments

(intelligent keys) to identify general ledger accounts, part numbers, and
other business entities. Each segment of the code can represent a
characteristic of the entity. Oracle Applications store these ”codes” in key
flexfields. Key flexfields are flexible enough to let any organization use the
code scheme they want, without programming.
Descriptive flexfields provide customizable ”expansion space” on your

forms. You can use descriptive flexfields to track additional information,
important and unique to your business, that would not otherwise be
captured by the form.
Applications Basics
Chapter 2 - Page 7
Overview of Alerts
Overview of Alerts
• Event alerts
• Periodic alerts
Oracle Alert is your complete exception control solution. You can define
one of two types of alerts: an event alert or a periodic alert. An event alert
immediately notifies you of activity in your database as it occurs. A
periodic alert, on the other hand, checks the database for information
according to a schedule you define.
An exception reporting system should do the following:

* Keep you informed of database exception conditions, as they
occur.
* Take predefined actions when it finds exceptions in your database,
without user intervention.
* Perform routine database tasks automatically, according to the
schedule you define.
* Do all of the above through simple use of your email, both direct
emails and distribution lists.
Applications Basics
Chapter 2 - Page 8
Overview of Workflow
Overview of Workflow
• Oracle Workflow Builder

• Workflow Engine
• Workflow Definition Loader
• Email integration and internet-enabled workflow
• Workflow Monitor
Oracle Workflow lets you automate and continuously improve business

processes, routing information of any type according to business rules you
can easily change to people both inside and outside your enterprise.
* Oracle Workflow Builder lets you create, view, or modify a business

process with simple drag and drop operations.
* The Workflow Engine embedded in the Oracle8 server monitors
workflow states and coordinates the routing of activities for a
process.
* The Workflow Definitions Loader is a utility program that moves
workflow definitions between the database and a flat file.
* Email users can receive notifications of outstanding work items and
can respond to those notifications. And, any user with access to a
standard Web browser can be included in a workflow.
* Workflow administrators and users can view the progress of a work
item in a workflow process by connecting to the Workflow Monitor
using a standard Web browser that supports Java.
Applications Basics
Chapter 2 - Page 9
Summary
Summary

• Use basic Applications tools.
• Describe the basics of concurrent processing.
• Describe the basics of flexfields.
• Describe the basics of alerts.
• Describe the basics of workflow.
Applications Basics
Chapter 2 - Page 10
ERDs and Applications
Technology
Chapter 3
ERDs and Applications Technology

Chapter 3 - Page 1

60 minutes Lecture
60 minutes Total

Chapter 3 - Page 2
Objectives
Objectives

do the following:
• Read and understand Entity Relationship
Diagrams (ERDs)
• Read and understand Oracle Applications'
Applications Technology ERDs

Chapter 3 - Page 3
Entity Relationship Diagrams (ERDs)
Entity Relationship Diagrams (ERDs)
• It describes exactly the information needs of the

business.
• It facilitates discussion.
• It helps to prevent mistakes, misunderstanding.
• It forms important “Technical Reference”
documentation.
• It is the basis for the physical creation of database
objects within the Oracle Applications database.
Entity Relationship Diagrams, or ERDs, emerged from the work of Dr.

Peter Chen and others during the 1970s. They were looking for a means
to simplify the representation of large and complex data storage concepts.
ERDs are conceptual models that show entities and relationships. While it
really is that simple, we should answer the question, why?

Chapter 3 - Page 4
What is an Entity?
What is an Entity?
• An Entity is:
– “Something” of significance to the business
about which data must be known.
– A name for the things that you can list.
– Usually a noun.
• Examples: objects, events
• Entities have instances.
In Oracle Applications, entities are going to be tables.

Chapter 3 - Page 5
Entities and Instances
Entities and Instances
PERSON John Doe

PRODUCT 2.5 x 35 mm copper nail
PRODUCT TYPE nail
EMPLOYMENT CONTRACT my previous contract
JOB violinist
SKILL LEVEL fluent
TICKET RESERVATION tonight: Hamlet in the Royal
PURCHASE the CD I bought yesterday
ELECTION for parliament next fall
PRINTER PREFERENCE …
DOCUMENT VERSION ...
®
In Oracle Applications, instances are the records stored in the table

(entity).

Chapter 3 - Page 6
Attributes
Attributes
• Also represents something of significance to the

business
• Is a single valued property detail of an entity
• Is a specific piece of information that:
– Describes
– Quantifies
– Qualifies
– Classifies
– Specifies
an entity.
®
In Oracle Applications, attributes are the columns of the table (entity).

Chapter 3 - Page 7
Relationships
Relationships
• Also represent something of significance to the

business
• Express how entities are mutually related
• Always exist between two entities (or one entity
twice)
• Always have two perspectives
• Are named at both ends
In Oracle Applications, relationships are the primary key, foreign keys, and
unique indexes that are maintained on the table (entity).

Chapter 3 - Page 8
Relationships
Relationships
JOB manager
EMPLOYEE cook
Shintaro waitress
dish washer
Jill financial controller
Adam
Ahmed porter
waiter
Maria
piano player
Numerical observation:
• All EMPLOYEES have a JOB
• No EMPLOYEE has more than one JOB
• Not all JOBS are held by an EMPLOYEE
• Some JOBS are held by more than one EMPLOYEE
®
To equate this diagram to Oracle Applications, you make some simple

conversions.
• EMPLOYEE and JOB are tables.
• The EMPLOYEE table has several records, Shintaro, Jill, Ahmed,
Adam, and Maria.
• The JOB table has several records, manager, waitress, cook, dish
washer, financial controller, waiter, porter, and piano player.
NOTE: This is an incomplete ERD in that the attributes used to connect

the EMPLOYEE to the JOB are not detailed.

Chapter 3 - Page 9
Drawing Entities in ERDs
Drawing Entities in ERDs
• Drawn as a “softbox”
• Name singular
EMPLOYEE JOB
• Name inside
ELECTION
• Neither size,
nor position
has a special TICKET
meaning ORDER
RESERVATION
JOB ASSIGNMENT
During design, entities usually lead to tables.

®

Chapter 3 - Page 10
Drawing Attributes in ERDs
Drawing Attributes in ERDs
EMPLOYEE JOB
* Family Name * Title
* Address o Description
o Birth Date
o Shoe Size
o Email
Mandatory attribute, that is, known and

* available for every instance
o Optional attribute, that is, unknown or
unimportant to know for some instances
During design, attributes lead to columns.

®

Chapter 3 - Page 11
Drawing Relationships in ERDs
Drawing Relationships in ERDs
An employee has exactly one job
EMPLOYEE JOB
has
held by
Jobs are held by one or more employees
During design, relationships lead to foreign keys.

®

Chapter 3 - Page 12
Perspectives of Relationships in ERDs
Perspectives of Relationships in ERDs
mandatory: optional:
EMPLOYEE has JOB
held by

Chapter 3 - Page 13
Reading Relationships in ERDs
Reading Relationships in ERDs
P split into Q
part of
“Each P may be split into one or more Qs”
“Each Q must be part of exactly one P”

®

Chapter 3 - Page 14
Oracle Applications ERD Standards
TABLE Table Name
# Primary Key Column 1

…
# Primary Key Column n
Let's start with the basics. Oracle Applications ERDs do not use
"softboxes". They use regular rectangles. This has no impact on reading
Oracle Applications ERDs other than the shape change.
At the top of each entity, or Table, will be the Table Name. Beneath the
Table Name is the primary key columns for that Table. There will always
be at least 1 column, and there may be several.
Generally, Oracle Applications does not list mandatory columns. These

are too numerous to include. However, sometimes for sake of clarity, a
mandatory column will be included. If so, that column will be marked with
an asterisk ().
NOTE: Generally, Oracle Applications ERDs use size to indicate

importance and relative sizing to other Tables. This is done in the most
generic of uses. For almost any case, you could easily find a customer,
who because of the special case of their business needs, has Tables that
aren't sized in the proportions shown. Use this as a simple guide.

Chapter 3 - Page 15
Table Name 1
Foreign Key
Constraint Recursive
Foreign Key
Delete Rule
Indicator
Table Name 2

This diagram shows how Oracle Applications ERDs diagram relationships.

Oracle Applications ERDs use solid lines to indicate mandatory
relationships where a value entered in the column in the foreign key must
match a value in the primary key column. Applications ERDs use dashed
lines (- - - - -) to indicate optional relationships where a value entered in
the column in the foreign key must match either a value in the primary key
column, or else it must be null. Oracle Applications ERDs also have
recursive foreign keys or pig's ears.
The Delete Rule Indicator determines the action to be taken when an

attempt is made to delete a related row in a join table. A line through the
foreign key constraint, as shown on the above diagram, indicates that this
action is restricted.
NOTE: Oracle Applications ERDs are not always clear on foreign key
relationships. For example, Table 2's primary key is the foreign key into
Table 1 even though it may not be part of Table 1's primary key. As such,
the foreign key relationship would be implied rather than explicitly
described.

Chapter 3 - Page 16
Table Name 1 Table Name 2
# Primary Key Col. 1 # Primary Key Col. 1
Table Name 3

Oracle Applications ERDs use an arc. The arc, shown above with circles
and an arc, is used to specify that, for any given row in a table, a value
must be entered in one of the arc columns. The remaining columns within
the arc must be null.
On the next several pages, I’ve reproduced the slides from the Applied
Technology ERDs. The single best source of the actual diagrams is the
AOL Technical Reference Manual (TRM). An online copy of that TRM has
been provided in your student materials. Reference that as a better and
more complete source.
NOTE: Over the course of the next several slides, we are going to
reproduce the ERD diagrams for Applications Technology objects.
Because of the limitation of Powerpoint, these diagrams will be simplified
compared to normal ERDs.

Chapter 3 - Page 17
Key Flexfields
Key Flexfields
FND_IFS
FND_S AV FND_SFA FND_IFSTR
FND_FVS FND_FVRS
FND_FERL FND_FVR
FND_FVQ
FND_FVRL
FND_V AT
FND_FIRL
FND_CIFS
FND_S AT FND_CIF
FND_IF
FND_APP FND_TAB WF_RP V FND_FWP

®
The diagram above shows the Key Flexfields ERD. Because of its size,
we had to compress its presentation. The following listing gives you the
information key for the diagram above.
Abbrev. Table Name

FND_IFS FND_ID_FLEX_SEGMENTS
Primary Keys: APPLICATION_ID
ID_FLEX_CODE
ID_FLEX_NUM
APPLICATION_COLUMN_NAME
FND_SAV FND_SEGMENT_ATTRIBUTE_VALUES
ID_FLEX_CODE
ID_FLEX_NUM
SEGMENT_ATTRIBUTE_TYPE
FND_SFA FND_SHORTHAND_FLEX_ALIASES
ID_FLEX_CODE

Chapter 3 - Page 18
ID_FLEX_NUM
ALIAS_NAME
FND_IFSTR FND_ID_FLEX_STRUCTURES
ID_FLEX_CODE
ID_FLEX_NUM
FND_FVS FND_FLEX_VALUE_SETS
Primary Keys: FLEX_VALUE_SET_ID
FND_FVRS FND_FLEX_VALIDATION_RULE_STATS
ID_FLEX_CODE
ID_FLEX_NUM
FND_FERL FND_FLEX_EXCLUDE_RULE_LINES
Primary Keys: RULE_LINE_ID
FND_FVR FND_FLEX_VALIDATION_RULES
ID_FLEX_CODE
ID_FLEX_NUM
FLEX_VALIDATION_RULE_NAME
FND_FVQ FND_FLEX_VALIDATION_QUALIFIERS
ID_FLEX_APPLICATION_ID
ID_FLEX_CODE
VALUE_ATTRIBUTE_TYPE
FND_FVRL FND_FLEX_VALIDATION_RULE_LINES
FND_VAT FND_VALUE_ATTRIBUTE_TYPES
ID_FLEX_CODE

Chapter 3 - Page 19
VALUE_ATTRIBUTE_TYPE
FND_FIRL FND_FLEX_INCLUDE_RULE_LINES
FND_CIFS FND_COMPILED_ID_FLEX_STRUCTS
ID_FLEX_CODE
ID_FLEX_NUM
COMPILER_VERSION_NUM
SEQUENCE
LANGUAGE
FND_SAT FND_SEGMENT_ATTRIBUTE_TYPES
ID_FLEX_CODE
FND_CIF FND_COMPILED_ID_FLEXS
ID_FLEX_CODE
SEQUENCE
LANGUAGE
FND_IF FND_ID_FLEXS
ID_FLEX_CODE
FND_APP FND_APPLICATION
FND_TAB FND_TABLES
TABLE_ID
WF_RPV WF_RUNNABLE_PROCESSES_V
FND_FWP FND_FLEX_WORKFLOW_PROCESSES

Chapter 3 - Page 20
ID_FLEX_CODE
ID_FLEX_NUM
WF_ITEM_TYPE

Chapter 3 - Page 21
Descriptive Flexfields
Descriptive Flexfields
FND_DESCR_FLEX_COLUMN_USAGES
FND_FLEX_VALUE_SE TS FND_DES CR_FLEX_CONTEXTS
FND_COMPILED_DESCRIPTIVE_FLEXS FND_DEFAULT_CONTE XT_FIELDS
FND_DESCRIPTIVE _FLEXS
FND_TABLES
FND_APP LICATION
The diagram above shows the Descriptive Flexfields ERD. Because of its
size, we had to compress its presentation. The following listing gives you
the information key for the diagram above.
Table Name
FND_DESCR_FLEX_COLUMN_USAGES
DESCRIPTIVE_FLEXFIELD_NAME
DESCRIPTIVE_FLEX_CONTEXT_CODE
FND_FLEX_VALUE_SETS
FND_DESCR_FLEX_CONTEXTS
DESCRIPTIVE_FLEX_CONTEXT_CODE
FND_COMPILED_DESCRIPTIVE_FLEXS

Chapter 3 - Page 22
SEQUENCE
LANGUAGE
FND_DEFAULT_CONTEXT_FIELDS
DEFAULT_CONTEXT_FIELD_NAME
FND_DESCRIPTIVE_FLEXS
FND_TABLES
TABLE_ID
FND_APPLICATION

Chapter 3 - Page 23
Flexfield Values
Flexfield Values
FND_FVH FND_FVS
FND_IFS
FND_FVNH
FND_FH
FND_FV
FND_FVE
FND_FVRL
FND_FVR
FND_FVRU
FND_RES P FND_TAB FND_FVT
The diagram above shows the Flexfield Value Sets ERD. Because of its
Abbrev. Table Name

FND_FVH FND_FLEX_VALUE_HIERARCHIES
PARENT_FLEX_VALUE
CHILD_FLEX_VALUE_LOW
CHILD_FLEX_VALUE_HIGH
FND_FVS FND_FLEX_VALUE_SETS
FND_IFS FND_ID_FLEX_SEGMENTS
ID_FLEX_CODE
ID_FLEX_NUM
FND_FVNH FND_FLEX_VALUE_NORM_HIERARCHY

Chapter 3 - Page 24
PARENT_FLEX_VALUE
RANGE_ATTRIBUTE
CHILD_FLEX_VALUE_LOW
CHILD_FLEX_VALUE_HIGH
FND_FH FND_FLEX_HIERARCHIES
HIERARCHY_ID
FND_FV FND_FLEX_VALUES
Primary Keys: FLEX_VALUE_ID
FND_FVE FND_FLEX_VALIDATION_EVENTS
EVENT_CODE
FND_FVRL FND_FLEX_VALUE_RULE_LINES
Primary Keys: FLEX_VALUE_RULE_ID
INCLUDE_EXCLUDE_INDICATOR
FLEX_VALUE_LOW
FLEX_VALUE_HIGH
FND_FVR FND_FLEX_VALUE_RULES
Primary Keys: FLEX_VALUE_RULE_ID
FND_FVRU FND_FLEX_VALUE_RULE_USAGES
RESPONSIBILITY_ID
FLEX_VALUE_RULE_ID
FND_RESP FND_RESPONSIBILITY
RESPONSIBILITY_ID
FND_TAB FND_TABLES
TABLE_ID

Chapter 3 - Page 25
FND_FVT FND_FLEX_VALIDATION_TABLES

Chapter 3 - Page 26
Concurrent Managers
Concurrent Managers
FND_CCR
FND_CCL
FND_CPG FND_CRC FND_O ID FND_USE R
FND_CQC
FND_CR
FND_NDS FND_CPR FND_DG FND_CQP
FND_CQ
FND_CPP FND_CPS FND_CQS FND_CTP
FND_APP
®
The diagram above shows the Concurrent Managers ERD. Because of its
Abbrev. Table Name

FND_CCR FND_CONCURRENT_COMPLEX_RULES
COMPLEX_RULE_ID
FND_CCL FND_CONCURRENT_COMPLEX_LINES
COMPLEX_RULE_ID
COMPLEX_RULE_LINE_ID
FND_CPG FND_CONCURRENT_PROGRAMS
CONCURRENT_PROGRAM_ID
FND_CRC FND_CONCURRENT_REQUEST_CLASS
REQUEST_CLASS_ID

Chapter 3 - Page 27
FND_OID FND_ORACLE_USERID
Primary Keys: ORACLE_ID
FND_USER FND_USER
Primary Keys: USER_ID
FND_CQC FND_CONCURRENT_QUEUE_CONTENT
Primary Keys: QUEUE_APPLICATION_ID
CONCURRENT_QUEUE_ID
TYPE_CODE
TYPE_APPLICATION_ID
TYPE_ID
FND_CR FND_CONCURRENT_REQUESTS
Primary Keys: REQUEST_ID
FND_NDS FND_NODES
Primary Keys: NODE_NAME
FND_CPR FND_CONCURRENT_PROCESSES
Primary Keys: CONCURRENT_PROCESS_ID
FND_DG FND_DATA_GROUPS
Primary Keys: DATA_GROUP_ID
FND_CQP FND_CONCURRENT_QUEUE_PARAMS
CONCURRENT_QUEUE_ID
NAME
FND_CQ FND_CONCURRENT_QUEUES
CONCURRENT_QUEUE_ID
FND_CPP FND_CONC_PROCESSOR_PROGRAMS
Primary Keys: PROCESSOR_APPLICATION_ID
CONCURRENT_PROCESSOR_ID
PROGRAM_APPLICATION_ID

Chapter 3 - Page 28
FND_CPS FND_CONCURRENT_PROCESSORS
CONCURRENT_PROCESSOR_ID
FND_CQS FND_CONCURRENT_QUEUE_SIZE
CONCURRENT_QUEUE_ID
PERIOD_APPLICATION_ID
CONCURRENT_TIME_PERIOD_ID
FND_CTS FND_CONCURRENT_TIME_PERIODS
CONCURRENT_TIME_PERIOD_ID

Chapter 3 - Page 29
FND_CPA FND_CRA FND_RRL
FND_CR
FND_CD FND_RES
FND_CRC FND_DGU
FND_LOG FND_DG FND_O ID
FND_USR FND_CRC
FND_CPS FND_CPG
FND_EXE
The diagram above shows the Concurrent Processing ERD. Because of

its size, we had to compress its presentation. The following listing gives
you the information key for the diagram above.
Abbrev. Table Name

FND_CPA FND_CONC_PP_ACTIONS
Primary Keys: CONCURRENT_REQUEST_ID
FND_CRA FND_CONC_REQUEST_ARGUMENTS
FND_RRL FND_RUN_REQ_LANGUAGES
Primary Keys: PARENT_REQUEST_ID
NLS_LANGUAGE
FND_CR FND_CONCURRENT_REQUESTS
FND_CD FND_CONFLICT_DOMAINS
Primary Keys: CD_ID

Chapter 3 - Page 30
FND_RES FND_RESPONSIBILITY
RESPONSIBILITY_ID
FND_CRC FND_CONC_RELEASE_CLASSES
RELEASE_CLASS_ID
FND_DGU FND_DATA_GROUP_UNITS
DATA_GROUP_ID
FND_LOG FND_LOGINS
Primary Keys: LOGIN_ID
FND_USR FND_USER
FND_CRC FND_CONCURRENT_REQUEST_CLASS
REQUEST_CLASS_ID
FND_CPS FND_CONCURRENT_PROGRAM_SERIAL
Primary Keys: RUNNING_APPLICATION_ID
RUNNING_CONCURRENT_PROGRAM_ID
TO_RUN_APPLICATION_ID
TO_RUN_CONCURRENT_PROGRAM_ID
FND_EXE FND_EXECUTABLES

Chapter 3 - Page 31
EXECUTABLE_ID

Chapter 3 - Page 32
Concurrent Manager Advanced Schedules
Concurrent Manager Advanced

Schedules
FND_CONC_RELEASE_CLASSES
FND_CONC_REL_CONJ_MEMBE RS FND_CONC_RELEASE_DISJS
FND_CONC_REL_DISJ _MEMBE RS
FND_CONC_RELEASE_S TATES FND_CONC_RELEASE_P ERIODS
FND_CONC_STATE_LO OKUP S FND_CONC_STATE _LO OKUP _TYPES
The diagram above shows the Concurrent Manager Advanced Scheduling

ERD. Because of its size, we had to compress its presentation. The
following listing gives you the information key for the diagram above.
Table Name
FND_CONC_RELEASE_CLASSES
RELEASE_CLASS_ID
FND_CONC_REL_CONJ_MEMBERS
Primary Keys: CLASS_APPLICATION_ID
RELEASE_CLASS_ID
DISJUNCTION_APPLICATION_ID
DISJUNCTION_ID
FND_CONC_RELEASE_DISJS
DISJUNCTION_ID
FND_CONC_REL_DISJ_MEMBERS
Primary Keys: DISJUNCTION_APPLICATION_ID

Chapter 3 - Page 33
DISJUNCTION_ID
PERIOD_OR_STATE_FLAG
NEGATION_FLAG
STATE_APPLICATION_ID
STATE_ID
PERIOD_APPLICATION_ID
PERIOD_ID
FND_CONC_RELEASE_STATES
CONCURRENT_STATE_ID
FND_CONC_RELEASE_PERIODS
CONCURRENT_PERIOD_ID
FND_CONC_STATE_LOOKUPS
Primary Keys: LOOKUP_TYPE_ID
LOOKUP_VALUE
FND_CONC_STATE_LOOKUP_TYPES
Primary Keys: LOOKUP_TYPE_ID

Chapter 3 - Page 34
Standard Request Submission
Standard Request Submission

FND_RGU
FND_RS
FND_RSS FND_RRA FND_RG
FND_RSP FND_RSA
FND_RR FND_DF
FND_CPG FND_RES
FND_APP
®
The diagram above shows the Standard Request Submission ERD.

Because of its size, we had to compress its presentation. The following
listing gives you the information key for the diagram above.
Abbrev. Table Name

FND_RGU FND_REQUEST_GROUP_UNITS
REQUEST_GROUP_ID
REQUEST_UNIT_TYPE
UNIT_APPLICATION_ID
REQUEST_UNIT_ID
FND_RS FND_REQUEST_SETS
REQUEST_SET_ID
FND_RSS FND_REQUEST_SET_STAGES
Primary Keys: SET_APPLICATION_ID
REQUEST_SET_ID
REQUEST_SET_STAGE_ID

Chapter 3 - Page 35
FND_RRA FND_RUN_REQ_PP_ACTIONS
REQUEST_SET_PROGRAM_ID
SET_APPLICATION_ID
REQUEST_SET_ID
SEQUENCE
FND_RG FND_REQUEST_GROUPS
REQUEST_GROUP_ID
FND_RSP FND_REQUEST_SET_PROGRAMS
Primary Keys: SET_APPLICATION_ID
REQUEST_SET_ID
FND_RSA FND_REQUEST_SET_PROGRAM_ARGS
REQUEST_SET_ID
DESCRIPTIVE_FLEX_APPL_ID
FND_RR FND_RUN_REQUESTS
SET_APPLICATION_ID
REQUEST_SET_ID
FND_DF FND_DESCRIPTIVE_FLEXS

Chapter 3 - Page 36
RESPONSIBILITY_ID

Chapter 3 - Page 37
Workflow
Workflow
WF_AA WF_AAV
WF_ACT WF_PA WF_AT
WF_IAS
WF_ITY WF_ITM
WF_IA WF_IAV
WF_MA WF_NA
WF_MS G WF_NO T
WF_RR WF_RRA
The diagram above shows the Workflow ERD. Because of its size, we
had to compress its presentation. The following listing gives you the
Abbrev. Table Name

WF_AA WF_ACTIVITY_ATTRIBUTES
Primary Keys: ACTIVITY_ITEM_TYPE
ACTIVITY_NAME
ACTIVITY_VERSION
NAME
WF_AAV WF_ACTIVITY_ATTR_VALUES
Primary Keys: PROCESS_ACTIVITY_ID
NAME
WF_ACT WF_ACTIVITIES
Primary Keys: ITEM_TYPE
NAME
VERSION
WF_PA WF_PROCESS_ACTIVITIES

Chapter 3 - Page 38
Primary Keys: INSTANCE_ID
WF_AT WF_ACTIVITY_TRANSISTIONS
Primary Keys: FROM_PROCESS_ACTIVITY
RESULT_CODE
TO_PROCESS_ACTIVITY
WF_IAS WF_ITEM_ACTIVITY_STATUSES
ITEM_KEY
PROCESS_ACTIVITY
WF_ITY WF_ITEM_TYPES
Primary Keys: NAME
WF_ITM WF_ITEMS
ITEM_KEY
WF_IA WF_ITEM_ATTRIBUTES
NAME
WF_IAV WF_ITEM_ATTRIBUTE_VALUES
ITEM_KEY
NAME
WF_MA WF_MESSAGE_ATTRIBUTES
Primary Keys: MESSAGE_TYPE
MESSAGE_NAME
NAME
WF_NA WF_NOTIFICATION_ATTRIBUTES
Primary Keys: NOTIFICATION_ID
NAME
WF_MSG WF_MESSAGES
Primary Keys: TYPE

Chapter 3 - Page 39
NAME
WF_NOT WF_NOTIFICATIONS
Primary Keys: NOTIFICATION_ID
WF_RR WF_ROUTING_RULES
Primary Keys: RULE_ID
WF_RRA WF_ROUTING_RULE_ATTRIBUTES
Primary Keys: RULE_ID
NAME
TYPE

Chapter 3 - Page 40
Function Security
Function Security
FND_MENU_ENTRIES FND_E NABLED_PLSQL
FND_MENUS
FND_FORM_FUNCTIONS FND_RES P_FUNCTIONS
FND_FORM FND_RES PONSIBILITY
FND_APPLICATION
The diagram above shows the Function Security ERD. Because of its
Table Name
FND_MENU_ENTRIES
Primary Keys: MENU_ID
ENTRY_SEQUENCE
FND_ENABLED_PLSQL
Primary Keys: PLSQL_TYPE
PLSQL_NAME
FND_MENUS
Primary Keys: MENU_ID
FND_FORM_FUNCTIONS
Primary Keys: FUNCTION_ID
FND_RESP_FUNCTIONS

Chapter 3 - Page 41
RESPONSIBILITY_ID
ACTION_ID
RULE_TYPE
FND_FORM
FORM_ID
FND_RESPONSIBILITY
RESPONSIBILITY_ID
FND_APPLICATION

Chapter 3 - Page 42
Login Security
Login Security
FND_URG FND_RES
FND_S G FND_APP
FND_DGU FND_AS
FND_O ID FND_DG FND_SESS
FND_LSF FND_LR
FND_LOG FND_UL
FND_USER
The diagram above shows the Login Security ERD. Because of its size,
we had to compress its presentation. The following listing gives you the
Abbrev. Table Name

FND_URG FND_USER_RESP_GROUPS
RESPONSIBILITY_ID
RESPONSIBILITY_APPLICATION_ID
SECURITY_GROUP_ID
RESPONSIBILITY_ID
FND_SG FND_SECURITY_GROUPS
Primary Keys: SECURITY_GROUP_ID

Chapter 3 - Page 43
FND_DGU FND_DATA_GROUP_UNITS
DATA_GROUP_ID
FND_AS FND_APPLICATION_SERVERS
Primary Keys: SERVER_ID
FND_SESS FND_SESSIONS
Primary Keys: SESSION_ID
FND_LRF FND_LOGIN_RESP_FORMS
LOGIN_RESP_ID
FORM_APPL_ID
FORM_ID
START_TIME
FND_LR FND_LOGIN_RESPONSIBILITIES
LOGIN_RESP_ID
FND_LOG FND_LOGINS
FND_UL FND_UNSUCCESSFUL_LOGINS
ATTEMPT_TIME
LOGIN_NAME
TERMINAL_ID
FND_USER FND_USER

Chapter 3 - Page 44
AuditTrail
AuditTrail
FND_O RACLE_USERID FND_AUDIT_SCHEMA
FND_COLUMNS FND_AUDIT_COLUMNS
FND_TABLES FND_AUDIT_TABLES
FND_AUDIT_GROUPS
The diagram above shows the AuditTrail ERD. Because of its size, we
Table Name
FND_ORACLE_USERID
FND_AUDIT_SCHEMA
Primary Keys: SCHEMA_ID
FND_COLUMNS
TABLE_ID
COLUMN_ID
FND_AUDIT_COLUMNS
Primary Keys: TABLE_APP_ID
TABLE_ID
COLUMN_ID
SCHEMA_ID

Chapter 3 - Page 45
FND_TABLES
TABLE_ID
FND_AUDIT_TABLES
Primary Keys: AUDIT_GROUP_ID
AUDIT_GROUP_APP_ID
TABLE_APP_ID
TABLE_ID
FND_AUDIT_GROUPS
AUDIT_GROUP_ID

Chapter 3 - Page 46
User Profiles
User Profiles
FND_P RO FILE_OPTION_VALUE S
FND_USE R_ RE SP_GROUPS
FND_P RO FILE_OPTIONS FND_USE R
FND_RES PONSIBILITY
FND_APPLICATION
The diagram above shows the User Profiles ERD. Because of its size, we
Table Name
FND_PROFILE_OPTION_VALUES
PROFILE_OPTION_ID
LEVEL_ID
LEVEL_VALUE
LEVEL_VALUE_APPLICATION_ID
FND_USER_RESP_GROUPS
RESPONSIBILITY_ID
RESPONSIBILITY_APPLICATION_ID
SECURITY_GROUP_ID
FND_PROFILE_OPTIONS
PROFILE_OPTION_ID

Chapter 3 - Page 47
FND_USER
FND_RESPONSIBILITY
RESPONSIBILITY_ID
FND_APPLICATION

Chapter 3 - Page 48
Document Sequences, Folders, Documents on the
Navigator
Document Sequences, Folders,

Documents on the Navigator
FND_DOC_S EQUENCE_ASSIGNMENTS FND_DOC_S EQ_CATE GORIES
FND_DOC_S EQ_AUDIT
FND_DOC_S EQ_USERS FND_DOCUMENT_S EQUENCES
FND_DEFAULT_FOLDE RS FND_USE R_ DE SKTOP _OBJS
FND_FOLDER_COLUMNS
FND_FOLDERS FND_DES KTOP _OBJECTS

®
The diagram above shows the Document Sequences, Folders, and

Documents on the Navigator ERDs. Because of their size, we had to
compress the presentation. The following listing gives you the information
key for the diagrams above.
Table Name
FND_DOC_SEQUENCE_ASSIGNMENTS
Primary Keys: DOC_SEQUENCE_ASSIGNMENT_ID
FND_DOC_SEQUENCE_CATEGORIES
CODE
FND_DOC_SEQUENCE_AUDIT
Primary Keys: DOC_SEQUENCE_ID
DOC_SEQUENCE_VALUE
FND_DOC_SEQUENCE_USERS
DOC_SEQUENCE_ASSIGNMENT_ID

Chapter 3 - Page 49
USER_ID
FND_DOCUMENT_SEQUENCES
FND_DEFAULT_FOLDERS
Primary Keys: FOLDER_ID
FND_FOLDER_COLUMNS
SEQUENCE
FND_FOLDERS
FND_USER_DESKTOP_OBJECTS
Primary Keys: DESKTOP_OBJECT_ID
FND_DESKTOP_OBJECTS
Primary Keys: DESKTOP_OBJECT_ID

Chapter 3 - Page 50
Attachments
Attachments
FND_AD
FND_DOCT FND_DST
FND_DOC FND_DLT
FND_DLR
FND_DC FND_DD
FND_DCU FND_DE
FND_AF FND_AB FND_ABE
The diagram above shows the Attachments ERD. Because of its size, we
Abbrev. Table Name

FND_AD FND_ATTACHED_DOCUMENTS
Primary Keys: ATTACHED_DOCUMENT_ID
FND_DOCT FND_DOCUMENTS_TL
Primary Keys: DOCUMENT_ID
LANGUAGE
FND_DST FND_DOCUMENTS_SHORT_TEXT
Primary Keys: MEDIA_ID
FND_DOC FND_DOCUMENTS
Primary Keys: DOCUMENT_ID
FND_DLT FND_DOCUMENTS_LONG_TEXT

Chapter 3 - Page 51
FND_DLR FND_DOCUMENTS_LONG_RAW
FND_DC FND_DOCUMENT_CATEGORIES
Primary Keys: CATEGORY_ID
FND_DD FND_DOCUMENT_DATATYPES
Primary Keys: DATATYPE_ID
LANGUAGE
FND_DCU FND_DOC_CATEGORY_USAGES
Primary Keys: DOC_CATEGORY_USAGE_ID
FND_DE FND_DOCUMENT_ENTITIES
Primary Keys: DOC_ENTITY_ID
FND_AF FND_ATTACHMENT_FUNCTIONS
Primary Keys: ATTACHMENT_FUNCTION_ID
FND_AB FND_ATTACHMENT_BLOCKS
Primary Keys: ATTACHMENT_BLK_ID
FND_ABE FND_ATTACHMENT_BLK_ENTITIES
Primary Keys: ATTACHMENT_BLK_ENTITY_ID

Chapter 3 - Page 52
Document Management and Help
Document Management and Help
FND_DNODES FND_DPRODS FND_DFUNC
FND_DPFS
FND_DFP
FND_DPP S
FND_LOBACC FND_LOBS FND_HDOC
FND_HTREE FND_HTAR
The diagram above shows the Document Management and Help ERDs.
Because of their size, we had to compress the presentation. The following
listing gives you the information key for the diagrams above.
Abbrev. Table Name

FND_DNODES FND_DM_NODES
Primary Keys: NODE_ID
FND_DPRODS FND_DM_PRODUCTS
Primary Keys: PRODUCT_ID
FND_DFUNC FND_DM_FUNCTIONS
Primary Keys: FUNCTION_ID
FND_DPFS FND_DM_PRODUCT_FUNCTION_SYNTAX
Primary Keys: PRODUCT_FUNCTION_ID
FND_DFP FND_DM_FUNCTION_PARAMETERS
Primary Keys: PARAMETER_ID
FND_DPPS FND_DM_PRODUCT_PARAM_SYNTAX

Chapter 3 - Page 53
Primary Keys: PRODUCT_PARAMETER_ID
FND_LOBACC FND_LOB_ACCESS
Primary Keys: ACCESS_ID
FND_LOBS FND_LOBS
Primary Keys: FILE_ID
FND_HDOC FND_HELP_DOCUMENTS
FND_HTREE FND_HELP_TREE
FND_HTAR FND_HELP_TARGETS
TARGET_NAME

Chapter 3 - Page 54
AOL Data Dictionary Information
AOL Data Dictionary Information

FND_APPLICATION
FND_V CO LS FND_V IEWS FND_SEQS FND_TABLES
FND_P KCOLS FND_P KE YS
FND_FKCOLS FND_FKEYS
FND_INCO LS FND_INDEXES
FND_COLUMNS
The diagram above shows the AOL Data Dictionary ERD. Because of its
Table Name
FND_APPLICATION
FND_VIEW_COLUMNS
VIEW_ID
COLUMN_SEQUENCE
FND_VIEWS
VIEW_ID
FND_SEQUENCES
SEQUENCE_ID

Chapter 3 - Page 55
FND_TABLES
TABLE_ID
FND_PRIMARY_KEY_COLUMNS
TABLE_ID
PRIMARY_KEY_ID
PRIMARY_KEY_SEQUENCE
FND_PRIMARY_KEYS
TABLE_ID
PRIMARY_KEY_ID
FND_FOREIGN_KEY_COLUMNS
TABLE_ID
FOREIGN_KEY_ID
FOREIGN_KEY_SEQUENCE
FND_FOREIGN_KEYS
TABLE_ID
FOREIGN_KEY_ID
FND_INDEX_COLUMNS
TABLE_ID
INDEX_ID
COLUMN_SEQUENCE
FND_INDEXES
TABLE_ID
INDEX_ID
FND_COLUMNS

Chapter 3 - Page 56
TABLE_ID
COLUMN_ID

Chapter 3 - Page 57
Currency and Language
Currency and Language
FND_LOO KUP_VALUES FND_LANGUAG ES
FND_LOO KUP_TYP ES FND_NEW_MES SAGES
FND_APPLICATION
The diagram above shows the Currency and Language ERD. Because of
its size, we had to compress its presentation. The following listing gives
you the information key for the diagram above.
Table Name
FND_LOOKUP_VALUES
Primary Keys: LOOKUP_TYPE
LANGUAGE
LOOKUP_CODE
SECURITY_GROUP_ID
VIEW_APPLICATION_ID
FND_LANGUAGES
Primary Keys: LANGUAGE_CODE
FND_LOOKUP_TYPES
Primary Keys: LOOKUP_TYPE
SECURITY_GROUP_ID
VIEW_APPLICATION_ID
FND_NEW_MESSAGES

Chapter 3 - Page 58
LANGUAGE_CODE
MESSAGE_NAME
FND_APPLICATION

Chapter 3 - Page 59
Summary
Summary

• Read and understand Entity Relationship
Diagrams (ERDs).
• Read and understand Oracle Applications'
Applications Technology ERDs.

Chapter 3 - Page 60
Development Topics
Chapter 4
Development Topics
Chapter 4 - Page 1
Development Topics
Development Topics

60 minutes Lecture
60 minutes Total
Development Topics
Chapter 4 - Page 2
Objectives
Objectives

do the following:
• Describe the interface options available within
Oracle Applications
• Describe solid standards for using these
interfaces
Development Topics
Chapter 4 - Page 3
Interface Options
Interface Options
• What is an interface?
• Interface Tables
• Application Programming Interfaces (APIs)
• Other methods
We are going to use the following definition for interfaces. An interface will
allow you to:
import data from a variety of environments, including your

own system, previous systems, data collection devices,
external systems, and others in the easiest way possible.
review the results of import runs, including validation,

review, update, re-imports, and error identification.
export data from Oracle Applications products for use in

other systems.
Given these broad characteristics, let's explore the methods by which we

can bring data in an Oracle Applications instance while adhering to our
definition.
1. INTERFACE TABLES
Throughout Oracle Applications' products, Oracle developers have

developed Interface Tables and programs. The Interface Tables allow you
Development Topics
Chapter 4 - Page 4
to load your data, and then to run an Application concurrent program.
That concurrent program will take the data from the Interface Table,
validate it, and import it into your Applications' instance.
This sort of interface satisfies all of our requirements. It is relatively easy,

just get your data into the Interface Table. Two, it checks the data before
importing it. And three, in many cases, these same tables are used to
export data, where appropriate.
There are numerous Interface Tables in the Oracle Applications products.

In fact, they are too numerous to mention here. Refer to the appropriate
product course for detailed information on these Interface Tables and their
usage.
2. APPLICATIONS PROGRAMMING INTERFACES (APIs)
Sometimes you want or need tighter integration to Oracle Applications

than can be provided with Interface Tables. In those cases, Oracle
Applications provides APIs.
APIs allow for tight integration into the Oracle Applications product. There
are also 3rd-party products that integrate into Oracle Applications and
extend its integration capabilities.
While more complex than Interface Tables, APIs do provide a pre-defined

method to integrate into Oracle Applications.
3. OTHER METHODS
This seems like a catch all category, and it is. Oracle Applications also
provides other methods for data import and export. The most common of
these is through spreadsheets.
Several Oracle Applications products allow for data upload and download
via spreadsheets. The spreadsheet formats are pre-defined. But, the
mechanics of the upload or download are quite simple.
Any else? Oracle Applications also support data uploads and downloads
to Oracle Discoverer and word processing files. While I think that covers
the bases, Oracle Applications is a growing product that adapts to new
and evolving standards. So, who knows. By the time you read this, there
may be new standards that have been released, or are just about to make
their appearance.
Development Topics
Chapter 4 - Page 5
Interface Table Diagram
Interface Table Diagram
Data Source
Loader
Validate
Maintain Interface Errors
Table Table
Concurrent
Program
Destination
Product
Here is a basic example of the Interface Table methodology.
The first thing to note is the Loader (in some cases also called, Feeders).
The Loader is responsible for uploading and downloading data from the
Interface Table. It should also be noted that some Interface Tables are
Inbound-only, some are Outbound-only, and some are both.
There are no restrictions on your Loader. As long as it can ultimately

communicate with the Interface Table in your Oracle Applications'
instance, you can use it as a loader. This is also the basic mechanism
that is used for transferring data with spreadsheets, word processing files,
and others.
Once the data is into the Interface Table, it must be validated. Validation
is generally handled through a concurrent program. In some cases this
concurrent program is part of the import process. In others, it is a
separate validation program.
In either case, invalid data is separated and noted. This can be done
through the generation of a report. It can also be done by moving the
invalid records into an Error Table.
Development Topics
Chapter 4 - Page 6
Once validation is complete, there may need to be maintenance on the
data to correct errors or inconsistencies. This is typically done by a form
built by the product development team for this purpose.
With the data ready to go, the concurrent program takes the data from the
Interface Table and loads it into the Application. As noted previously,
validation may be occurring at this point or separately.
IMPORTANT NOTE:
It is critical to note how the data is imported. At NO TIME are you writing
data into or from the product tables. The only tables you write or read are
the Interface Tables.
Development Topics
Chapter 4 - Page 7
API Diagram
API Diagram
Data Source
Return Return
Call
Error Result
Business
Object API
Perform
Business
Function
Destination
Product
Here is a basic example of the API methodology.
It should be noted that this method is distinctly different from the Interface
Table methodology. First off, the data is not staged. The data is sent
directly through the API. This has an implication. API methods are for
single-record data importing. Interface Tables are for mass data
importing. Of course, you could do mass imports with API, but it will be
slower, and performance is always a concern.
Another implication is that the API communicates directly with the Data
Source, letting it know if the import was successful. This implies that the
Data Source must be more than a data source. It must be able to handle
unsuccessful attempts to move data into the product.
Using an API also implies a bigger responsibility of programs and code

outside of Oracle Applications. The Data Source must handle errors, must
handle data maintenance, and all the other jobs that our interfaces must
do.
IMPORTANT NOTE:
data into or from the product tables. Only the API writes or reads from the
Development Topics
Chapter 4 - Page 8
product tables. The API is responsible for communicating with your data
source.
Development Topics
Chapter 4 - Page 9
Development Standards
• Document
• Follow the documentation
• Adhere to the rules
• Check your data
DOCUMENT:
One of the most overlooked part of any interface project is documentation.

Why? Mostly because it is the unglamorous part of the process. But, it is
absolutely critical to your success.
Oracle Applications is a mission critical application. You are maintaining

the data that runs your company on it. Having a system that is not
documented is a glaring hole in your long-term viability. All this
vulnerability, and it turns out to be simple to collect the basics.
1. Document the source of your data. Where is it coming from,

and most importantly, how do you reproduce that source (if it
is not self-maintaining).
2. Document the method by which you move data from the
source to the Interface Table or to which API. Are you using
SQL*Loader, spreadsheets, C programs?
3. Document the data format. A simple description by column of
the data your are moving.
FOLLOW THE DOCUMENTATION:
Development Topics
Chapter 4 - Page 10
It is quite amazing when you consider that the interfaces, both Interface
Tables and APIs, are documented in their product manuals. Use these
sources. If you do not have the manual on the interface you are trying to
use, you are missing the center of the puzzle.
ADHERE TO THE RULES:
Read the descriptions of the Interface Tables and APIs. Follow what the
documentation says. Don't assume that you can short-cut the process,
even though your short-cut "seems" to do the same. Oracle Applications
is a complex, inter-related product. Those assumptions are not safe.
data into or from the product tables. Only the API writes or reads from the
product tables or the concurrent programs that service the Interface Table.
Do not wite or read directly!
CHECK YOUR DATA:
The single biggest cause of problems with Interface Tables and APIs is
misformatted data. You are either NOT putting the right data into the right
columns of the Interface Table. Or, you are not passing the proper
arguments in the proper format to the API. In over 90% of the problems
with the interfaces, the net result is data. Check it!
Development Topics
Chapter 4 - Page 11
Summary
Summary

• Describe the interface options available within
Oracle Applications.
• Describe solid standards for using these
interfaces.
Development Topics
Chapter 4 - Page 12
Exploring Applications
Database
Chapter 5
Exploring Applications Database

Chapter 5 - Page 1

60 minutes Demonstration
60 minutes Total

Chapter 5 - Page 2
Objectives
Objectives

do the following:
• Use SQL scripts to explore Oracle Applications
database objects
In the chapters on the "Applications Architecture" and "ERDs and

Applications Technology", there is an assumption that the student knows
how to use SQL*Plus to explore and confirm the statements made.
This lesson is in place to help those students who need some assistance
with those skills. It will also help those students who don't need help,
because it will add a trick or two that they might not have seen.

Chapter 5 - Page 3
Exploration Basics
Exploration Basics
• Logging in to SQL*Plus
• Running SQL scripts
• Listing scripts
• Description scripts
• Configuration scripts
LOGGING IN TO SQL*PLUS:
Logging in to SQL*Plus is dependent upon where you are trying to do the

login. Basically, you can login to SQL*Plus from the machine where the
database is running or from another machine. Getting all the details of
this set-up is well beyond the scope of this class. You need SQL*Net
guides to configure your settings if you need help with this.
What this section does cover is the usernames and passwords that are
defaults on your database. (NOTE: These are only the defaults.
Usernames and passwords can be changed. In fact, Oracle recommends
that these passwords be changed.)
Default Username Default Password

======================= ===========================
APPS APPS
APPLSYSPUB PUB
APPLSYS APPS
<PROD> <PROD> (examples follows)
GL GL
AR AR
SYSTEM MANAGER

Chapter 5 - Page 4
SYS CHANGE_ON_INSTALL
The most important username/password to the student is that for the

APPS schema. This is the username/password that will be used for
running our exploration scripts.
RUNNING SQL SCRIPTS:
To run a SQL script, you can do 1 of 2 things. From the command line,
put at @ followed by the script name at the end of the command. For
example:
sqlplus apps/apps @script1.sql
The other method is to invoke the script inside of SQL*Plus by typing @

followed by the script name. For example:
$ sqlplus apps/apps
SQL*Plus: Release 8.1.6.0.0 - Production on Wed Jan 24 08:30:19
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Connected to:
Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
With the Partitioning option
JServer Release 8.1.6.1.0 - Production
SQL> @script1.sql
TYPES OF SCRIPTS:
There are 3 major categories that clearly delineate the scripts we will use
to explore the database, listing scripts, description scripts, and
configuration scripts.
Listing scripts help us determine the name of something specific. Listing

scripts will be used to show us that something exists, or a list of all the
things of a given type that exist. Description scripts are used to give us
details about any given object. Configuration scripts are used to give us
information about how our database and its environment are setup.

Chapter 5 - Page 5
Listing Scripts
Listing Scripts
• Count Database Objects by Type

• List Product Dependencies
• List Pinned Objects
• List Objects
What follows are several scripts that will list the various objects in your
database. These scripts are:
1. Count Database Objects by Type

2. List Product Dependencies
3. List Pinned Objects
4. Various List Object Scripts, including List Database Links,
Functions, Indexes, Java Classes, Java Resources,
Java Source, LOBs, Packages, Package Bodies,
Procedures, Sequences, Synonyms, Tables, Triggers,
Types, and Views.
The scripts are reproduced here for your use. We give them default
names, but you are welcome to rename them when you use them on your
database.
SCRIPT = Count Objects by Type

NAME = CNTOBJS.sql
DESCRIPT= This script will count the various database objects
by type that are present in the Applications
database where the script is run.

Chapter 5 - Page 6
REM ***** COUNT OBJECTS BY TYPE
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'COUNT OBJECTS BY TYPE' SKIP 2
COL DateInf FORMAT A19 HEADING 'Runtime Information'

COL Object_Type FORMAT A18 HEADING 'Object Type'
COL Status FORMAT A7 HEADING 'Status'
COL Objcnt FORMAT 9999999999 HEADING 'Count'
SET PAGESIZE 1000

SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Owner_List PROMPT 'Input Schema to Count or %
for All: '
SELECT to_char(sysdate,'DD-MM-YYYY HH24:MI:SS')

DateInf FROM sys.dual;
REPHEADER OFF
BREAK ON REPORT
COMPUTE SUM OF Objcnt ON REPORT
SELECT object_type, status, count(*) objcnt

FROM DBA_OBJECTS
WHERE Owner like '&&Owner_List'
GROUP BY object_type, status;
SCRIPT = List Product Dependencies

NAME = LISTPRODDEP.sql
DESCRIPT= Many Applications products depend upon
functionality from other Applications products.
These relationships are called Dependencies.
This script will list, by product, the additional

Chapter 5 - Page 7
products that are needed for the original
product to run.
REM ***** LIST PRODUCT DEPENDENCIES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST PRODUCT DEPENDENCIES' SKIP 2

COL Application FORMAT A38 HEADING 'Application'
COL Requires FORMAT A38 HEADING 'Requires the
Application'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0

REPHEADER OFF
BREAK ON APPLICATION SKIP 2
SELECT a3.application_name Application,

a4.application_name Requires
FROM fnd_application a1, fnd_application a2,
fnd_application_tl a3, fnd_application_tl a4,
fnd_oracle_userid o1, fnd_oracle_userid o2,
fnd_product_dependencies fpd
WHERE
a2.application_id=fpd.required_application_id
AND a1.application_id=fpd.application_id
AND o2.oracle_id=fpd.required_oracle_id
AND o1.oracle_id=fpd.oracle_id
AND a2.application_id=a4.application_id
AND a1.application_id=a3.application_id

Chapter 5 - Page 8
ORDER BY 1,2;
SCRIPT = List Pinned Objects

NAME = LISTPINNED.sql
DESCRIPT= In order to improve performance, Oracle
Applications pins into memory many of its
PL*SQL packages. This has implications for
performance and patching. Performance will
improve with pinned packages. And for
patching, a package must be unpinned, updated,
and then re-pinned in order for the patch to
be effective. This script lists the currently
pinned packages.
REM ***** LIST PINNED OBJECTS
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST PINNED OBJECTS' SKIP 2

COL Type FORMAT A12 HEADING 'Type'
COL Object FORMAT A36 HEADING 'Object'
COL Loads FORMAT 99990 HEADING 'Loads'
COL Execs FORMAT 9999990 HEADING 'Execs'
COL Kept FORMAT A4 Heading 'Kept'
COL "TOTAL SPACE (K)" FORMAT A20
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0

REPHEADER OFF
SELECT owner || '.' || name OBJECT , type,

Chapter 5 - Page 9
to_char(sharable_mem/1024,'9,999.9')
"SPACE(K)", loads, executions execs, kept
FROM v$db_object_cache
WHERE type in ('FUNCTION','PACKAGE',
'PACKAGE BODY','PROCEDURE')
AND owner not in ('SYS')
ORDER BY owner, name;
SELECT to_char(sum(sharable_mem)/1024,'9,999,999.9')
"TOTAL SPACE (K)"
FROM v$db_object_cache
WHERE type in ('FUNCTION','PACKAGE',
'PACKAGE BODY','PROCEDURE')
AND owner not in ('SYS');
SCRIPT = LIST DATABASE LINKS

NAME = LISTDBLINKS.sql
DESCRIPT= This script lists all database links.
REM ***** LIST DATABASE LINKS
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST DATABASE LINKS' SKIP 2

COL Owner FORMAT A30 HEADING 'Owner'
COL DB_Link FORMAT A50 HEADING 'Database Link'
SET PAGESIZE 66
SET LINESIZE 85
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Owner_List PROMPT 'Input Owner or % for All: '
ACCEPT Link_List PROMPT 'Input DB Link or % for All: '


Chapter 5 - Page 10
REPHEADER OFF
BREAK ON OWNER SKIP 2
COMPUTE COUNT OF DB_LINK ON OWNER
SELECT Owner, DB_Link FROM DBA_DB_LINKS

AND DB_Link like '&&Link_List'
ORDER BY Owner, DB_Link;
SCRIPT = LIST FUNCTIONS

NAME = LISTFUNCS.sql
DESCRIPT= This script will list all functions.
REM ***** LIST FUNCTIONS
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST FUNCTIONS' SKIP 2

COL Object_Name FORMAT A40 HEADING 'Function Name'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Function Name or % for
All: '
ACCEPT Status_List PROMPT 'Input Status or % for All:
'

REPHEADER OFF

Chapter 5 - Page 11
COMPUTE COUNT OF OBJECT_NAME ON OWNER
SELECT Owner, Object_Name, Status

FROM DBA_OBJECTS
WHERE Object_Type='FUNCTION'
AND Owner like '&&Owner_List'
AND Object_Name like '&&Name_List'
AND Status like '&&Status_List'
ORDER BY Owner, Object_Name;
SCRIPT = LIST INDEXES

NAME = LISTINDEXES.sql
DESCRIPT= This script lists all indexes.
REM ***** LIST INDEXES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST INDEXES' SKIP 2

COL Index_Name FORMAT A30 HEADING 'Index Name'
COL Table_Name FORMAT A30 HEADING 'Table Name'
COL Uniqueness FORMAT A10 Heading 'Uniqueness'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Index_List PROMPT 'Input Index Name or % for
All: '
ACCEPT Table_List PROMPT 'Input Table Name or % for
All: '
'

Chapter 5 - Page 12
REPHEADER OFF
COMPUTE COUNT OF INDEX_NAME ON OWNER
SELECT Owner, Index_Name, Table_Name, Uniqueness,

Status
FROM DBA_INDEXES
AND Index_Name like '&&Index_List'
AND Table_Name like '&&Table_List'
ORDER BY Owner, Index_Name;
SCRIPT = LIST JAVA CLASSES

NAME = LISTJCLASSES.sql
DESCRIPT= This script lists all Java Class objects.
REM ***** LIST JAVA CLASSES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST JAVA CLASSES' SKIP 2

COL Java_Name FORMAT A60 HEADING 'Name'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF

Chapter 5 - Page 13
ACCEPT Object_List PROMPT 'Input Java Class Name or %
for All: '
'

REPHEADER OFF
COMPUTE COUNT OF STATUS ON OWNER
SELECT Owner, DBMS_JAVA.LONGNAME(Object_Name)

Java_Name, Status
FROM DBA_OBJECTS
AND 2 like '&&Object_List'
AND Object_Type = 'JAVA CLASS'
ORDER BY Owner, 2;
SCRIPT = LIST JAVA RESOURCES

NAME = LISTJRES.sql
DESCRIPT= This script lists all Java Resource objects.
REM ***** LIST JAVA RESOURCES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST JAVA RESOURCES' SKIP 2

COL Java_Name FORMAT A60 HEADING 'Long Name'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0

Chapter 5 - Page 14
SET VERIFY OFF
ACCEPT Object_List PROMPT 'Input Java Resource Name or
% for All: '
'

REPHEADER OFF

Java_Name, Status
FROM DBA_OBJECTS
AND Object_Type = 'JAVA RESOURCE'
ORDER BY Owner, 2;
SCRIPT = LIST JAVA SOURCES

NAME = LISTJSRC.sql
DESCRIPT= This script lists all Java Source objects.
REM ***** LIST JAVA SOURCES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST JAVA SOURCES' SKIP 2

COL Java_Name FORMAT A60 HEADING 'Long Name'
SET PAGESIZE 66

Chapter 5 - Page 15
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Object_List PROMPT 'Input Java Source Name or %
for All: '
'

REPHEADER OFF

Java_Name, Status
FROM DBA_OBJECTS
AND Object_Type = 'JAVA SOURCE'
ORDER BY Owner, 2;
SCRIPT = LIST LOBs

NAME = LISTLOBS.sql
DESCRIPT= This scripts lists all LOB objects.
REM ***** LIST LOBS
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST LOBS' SKIP 2

COL Table_Name FORMAT A30 HEADING 'Table'

Chapter 5 - Page 16
COL Column_Name FORMAT A60 HEADING 'LOB Column or
Attribute'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Table_List PROMPT 'Input Table Name or % for
All: '
ACCEPT Col_List PROMPT 'Input Column Name/Attribute or
% for All: '

REPHEADER OFF
COMPUTE COUNT OF COLUMN_NAME ON OWNER
SELECT Owner, Table_Name, Column_Name

FROM DBA_LOBS
AND Table_Name like '&&Table_List'
AND Column_Name like '&&Col_List'
ORDER BY Owner, Table_Name, Column_Name;
SCRIPT = LIST PACKAGES

NAME = LISTPKGS.sql
DESCRIPT= This script lists all Packages.
REM ***** LIST PACKAGES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST PACKAGES' SKIP 2


Chapter 5 - Page 17
COL Object_Name FORMAT A40 HEADING 'Package Name'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input PAckage Name or % for
All: '
'

REPHEADER OFF

FROM DBA_OBJECTS
WHERE Object_Type='PACKAGE'
SCRIPT = LIST PACKAGE BODIES

NAME = LISTPKBODS.sql
DESCRIPT= This script lists all Package Bodies.
REM ***** LIST PACKAGE BODIES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST PACKAGE BODIES' SKIP 2

Chapter 5 - Page 18
COL Object_Name FORMAT A40 HEADING 'Package Body Name'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Package Body Name or %
for All: '
'

REPHEADER OFF

FROM DBA_OBJECTS
WHERE Object_Type='PACKAGE BODY'
SCRIPT = LIST PROCEDURES

NAME = LISTPROCS.sql
DESCRIPT= This script lists all Procedures.
REM ***** LIST PROCEDURES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST PROCEDURES' SKIP 2

Chapter 5 - Page 19
COL Object_Name FORMAT A40 HEADING 'Procedure Name'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Procedure Name or % for
All: '
'

REPHEADER OFF

FROM DBA_OBJECTS
WHERE Object_Type='PROCEDURE'
SCRIPT = LIST SEQUENCES

NAME = LISTSEQS.sql
DESCRIPT= This script lists all Sequences.
REM ***** LIST SEQUENCES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST SEQUENCES' SKIP 2

Chapter 5 - Page 20
COL Sequence_Owner FORMAT A30 HEADING 'Owner'
COL Sequence_Name FORMAT A30 HEADING 'Sequence'
COL Min_Value FORMAT 9999999990 HEADING 'Min Value'
COL Max_Value FORMAT 9999999990 HEADING 'Max Value'
COL Increment_By FORMAT 9999999990 HEADING 'Increment'
COL Cycle_Flag FORMAT A5 HEADING 'Cycle'
COL Order_Flag FORMAT A5 HEADING 'Order'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Sequence Name or % for
All: '

REPHEADER OFF
BREAK ON SEQUENCE_OWNER SKIP 2
COMPUTE COUNT OF SEQUENCE_NAME ON SEQUENCE_OWNER
SELECT Sequence_Owner, Sequence_Name, Min_Value,

Max_Value,
Increment_By, Cycle_Flag, Order_Flag
FROM DBA_SEQUENCES
WHERE Sequence_Owner like '&&Owner_List'
AND Sequence_Name like '&&Name_List'
ORDER BY Sequence_Owner, Sequence_Name;
SCRIPT = LIST SYNONYMS

NAME = LISTSYNS.sql
DESCRIPT= This script lists all Synonyms.
REM ***** LIST SYNONYMS
CLEAR COMPUTES

Chapter 5 - Page 21
CLEAR BREAKS
REPHEADER LEFT 'LIST SYNONYMS' SKIP 2

COL Synonym_Name FORMAT A30 HEADING 'Synonym'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Synonym Name or % for
All: '

REPHEADER OFF
COMPUTE COUNT OF SYNONYM_NAME ON OWNER
SELECT Owner, Synonym_Name

FROM DBA_SYNONYMS
AND Synonym_Name like '&&Name_List'
ORDER BY Owner, Synonym_Name;
SCRIPT = LIST TABLES

NAME = LISTTABLES.sql
DESCRIPT= This script lists all Tables.
REM ***** LIST TABLES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST TABLES' SKIP 2

Chapter 5 - Page 22
COL Table_Name FORMAT A30 HEADING 'Table'
COL Num_Rows FORMAT 9999999990 HEADING '# of Rows'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Table Name or % for
All: '

REPHEADER OFF
COMPUTE COUNT OF TABLE_NAME ON OWNER
SELECT Owner, Table_Name, Num_Rows

FROM DBA_TABLES
AND Table_Name like '&&Name_List'
ORDER BY Owner, Table_Name;
SCRIPT = LIST TRIGGERS

NAME = LISTTRIGS.sql
DESCRIPT= This script lists all Triggers.
REM ***** LIST
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST ' SKIP 2

Chapter 5 - Page 23
COL Trigger_Name FORMAT A30 HEADING 'Trigger'
COL Trigger_Type FORMAT A16 HEADING 'Trigger Type'
COL Triggering_Event FORMAT A30 HEADING 'Triggering
Event'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Trigger Name or % for
All: '
ACCEPT Type_List PROMPT 'Input Trigger Type or % for
All: '
ACCEPT Event_List PROMPT 'Input Triggering Event or %
for All: '
'

REPHEADER OFF
COMPUTE COUNT OF TRIGGER_NAME ON OWNER
SELECT Owner, Trigger_Name, Trigger_Type,

Triggering_Event, Status
FROM DBA_TRIGGERS
AND Trigger_Name like '&&Name_List'
AND Trigger_Type like '&&Type_List'
AND Triggering_Event like '&&Event_List'
ORDER BY Owner, Trigger_Name;
SCRIPT = LIST TYPES

NAME = LISTTYPES.sql

Chapter 5 - Page 24
DESCRIPT= This script lists all Types.
REM ***** LIST TYPES
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST TYPES' SKIP 2

COL Type_Name FORMAT A30 HEADING 'Type'
COL Typecode FORMAT A27 HEADING 'Type Code'
COL Attributes FORMAT 9999999990 HEADING '# of Attr'
COL Methods FORMAT 9999999990 HEADING '# of Meth'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input Type Name or % for All:
'

REPHEADER OFF
COMPUTE COUNT OF TYPE_NAME ON OWNER
SELECT Owner, Type_Name, Typecode, Attributes, Methods

FROM DBA_TYPES
AND Type_Name like '&&Name_List'
ORDER BY Owner, Type_Name;
SCRIPT = LIST VIEWS

NAME = LISTVIEWS.sql

Chapter 5 - Page 25
DESCRIPT= This script lists all Views.
REM ***** LIST VIEWS
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'LIST VIEWS' SKIP 2

COL View_Name FORMAT A30 HEADING 'View'
COL View_Type FORMAT A30 HEADING 'View Type'
COL Text_Length FORMAT 9999999990 HEADING 'Length'
SET PAGESIZE 66
SET LINESIZE 132
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Name_List PROMPT 'Input View Name or % for All:
'

REPHEADER OFF
COMPUTE COUNT OF VIEW_NAME ON OWNER
SELECT Owner, View_Name, View_Type, Text_Length

FROM DBA_VIEWS
AND View_Name like '&&Name_List'
ORDER BY Owner, View_Name;

Chapter 5 - Page 26
Description Scripts
Description Scripts
• Describe Database Configuration

• Describe Database Users
• Describe Objects
What follows are several scripts that will describe the various objects in
your database. These scripts are:
1. Describe Database Configuration

2. Describe Database Users
3. Various Describe Object Scripts, including List Database Links,
Functions, Indexes, Java Classes, Java Resources,
Java Source, LOBs, Packages, Package Bodies,
Procedures, Sequences, Synonyms, Tables, Triggers,
Types, and Views.
NOTE: In this discussion, we are not going to give you samples of the
scripts for description. That would be too lengthy. Rather, we will discuss
the Database Views that maintain the information you need. Those static
views are discussed at the end of the scripts.
The scripts are reproduced here for your use. We give them default
names, but you are welcome to rename them when you use them on your
database.
SCRIPT = Describe Database Configuration

Chapter 5 - Page 27
NAME = DESCDBCONF.sql
DESCRIPT=This script will report on the configuration of the
database as it currently existings.
REM ***** DESCRIBE DATABASE CONFIGURATION
CLEAR COMPUTES
CLEAR BREAKS
SET HEADING ON
SET PAGES 1000
SET LINESIZE 80
SET VERIFY OFF
COL Segment_Name FORMAT A12

COL TSpace FORMAT A10
COL Initial FORMAT 99999999
COL Next FORMAT 99999999
COL Min FORMAT 999999
COL Max FORMAT 999999
COL Pct FORMAT 990
COL Status FORMAT A10
COL Bytes FORMAT 999999999
COL File_Name FORMAT A37
COL ID FORMAT 99
BREAK ON TSPACE
REPHEADER LEFT 'Database Configration' SKIP 2

REPHEADER OFF
SELECT ' ' FROM SYS.DUAL;

SELECT 'ROLLBACK SEGMENTS:' FROM SYS.DUAL;
SELECT Segment_Name, Tablespace_Name TSpace,

Initial_Extent "INITIAL", Next_Extent "NEXT",

Chapter 5 - Page 28
Min_Extents Min, Max_Extents Max,
Pct_Increase Pct, Status
FROM DBA_ROLLBACK_SEGS
ORDER BY Tablespace_Name, Segment_Name;
SELECT 'TABLESPACES:' FROM SYS.DUAL;
SELECT Tablespace_Name TSpace,

Initial_Extent "INITIAL", Next_Extent "NEXT",
Min_Extents Min, Max_Extents Max,
Pct_Increase Pct, Status
FROM DBA_TABLESPACES
ORDER BY Tablespace_Name;
SELECT 'DATAFILES:' FROM SYS.DUAL;
SELECT Tablespace_Name TSpace, File_Name,

File_Id "ID", Bytes, Status
FROM DBA_DATA_FILES
ORDER BY Tablespace_Name;
SCRIPT = Describe Database Users

NAME = DESCUSERS.sql
DESCRIPT=This script will describe database users/schemas
REM ***** DESCRIBE DATABASE USERS
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'DESCRIBE DATABASE USERS' SKIP 2
COL User_ID FORMAT 9990 HEADING 'ID'

COL Username FORMAT A12 HEADING 'Username'
COL DT FORMAT A1 HEADING ''
COL Default_Tablespace FORMAT A15 HEADING 'Default'
COL TT FORMAT A1 HEADING ''
COL Temporary_Tablespace FORMAT A12 HEADING
'Temporary'

Chapter 5 - Page 29
COL Profile FORMAT A18 HEADING 'Profile'
COL Created FORMAT A9 HEADING 'Created'
SET PAGESIZE 1000

SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF
ACCEPT Owner_List PROMPT 'Input User or % for All: '

REPHEADER OFF
SELECT User_ID, substr(Username,1,12) Username,

decode(Default_Tablespace,'SYSTEM','*',null)
DT, Default_Tablespace,
decode(Temporary_tablespace,'SYSTEM','*',
null) TT, Temporary_Tablespace, Profile,
Created
FROM DBA_USERS
WHERE Username like upper('&&User_List')
ORDER BY Username;
DATABASE STATIC VIEWS:
For the objects stored in your Applications database, you will want to know
which static view, maintained by the Database, will give you the
information that you need. The following table shows that information.
Object Type Static View

DB Links DBA_DB_LINKS
Functions DBA_SOURCE, Where Type='FUNCTION'
Indexes DBA_INDEXES
Java Classes DBA_SOURCE, Where Type='JAVA CLASS'
Java Resource DBA_SOURCE, Where Type='JAVA RESOURCE'
Java Source DBA_SOURCE, Where Type='JAVA SOURCE'
LOBs DBA_LOBS
Packages DBA_SOURCE, Where Type='PACKAGE'

Chapter 5 - Page 30
Package Bodies DBA_SOURCE, Where Type='PACKAGE BODY'
Procedures DBA_SOURCE, Where Type='PROCEDURE'
Sequences DBA_SEQUENCES
Synonyms DBA_SYNONYMS
Tables DBA_TABLES
Triggers DBA_TRIGGERS
Types DBA_TYPES
Views DBA_VIEWS
Use the Listing Scripts as templates for Description scripts that you may
want to create. Also, use the DESCRIBE command in SQL*Plus to get
detailed descriptions of the available columns of these static data
dictionary views.

Chapter 5 - Page 31
Configuration Scripts
Configuration Scripts
• Applications Configuration Script

• Report Imminent Extent Failure
• Report User Space
What follows are several scripts that will report on your current
configuration of your database. These scripts are:
1. Applications Configuration Script

2. Report Table Sizes
3. Report Imminent Extent Failure
4. Report User Space
With little doubt, the most useful configuration script is the Applications
Configuration Script. This scripts useful is enhanced because it is actually
shipped with the Application. The script is reproduced here for study, but
you can find this script in ANY Applications instance in the file
$AD_TOP/sql/adutconf.sql
REM $Header: adutconf.sql 115.11 2000/03/07 22:22:08 rlotero ship $

REM +===============================================+
REM | Copyright (c) 1996 Oracle Corporation |
REM | All rights reserved. |
REM +===============================================+
REM NAME
REM adutconf.sql

Chapter 5 - Page 32
REM DESCRIPTION
REM Utility script to display configuration of Applications
REM +===============================================+
SPOOL adutconf.lst
SET VERIFY OFF

SET PAGES 9999
SET LINES 80
COL application_id FORMAT 99990 HEADING "ID"

COL application_name FORMAT a40 HEADING "Name"
COL application_prefix FORMAT a6 HEADING "Prefix"
COL application_short_name FORMAT a10 HEADING "Short name"
COL apps FORMAT a8 HEADING "Product"
COL basepath FORMAT a8 HEADING "Basepath"
COL crby FORMAT 99990 HEADING "By"
COL creation FORMAT a11 HEADING "Created"
COL current_size FORMAT 999999990 HEADING "Size (K)"
COL data_group_id FORMAT 99990 HEADING "ID"
COL data_group_name FORMAT a29 HEADING "Data Group Name"
COL default_group_flag FORMAT a4 HEADING "Dflt"
COL in_dba_users FORMAT a13 HEADING "In DBA_USERS?"
COL initial_extent FORMAT 9999990 HEADING "Initial (K)"
COL index_tablespace FORMAT a12 HEADING "Index TS"
COL install_group_num FORMAT 90 HEADING "IGN"
COL installed_flag FORMAT a9 HEADING "Type"
COL language_code FORMAT a4 HEADING "Code"
COL luby FORMAT 99990 HEADING "By"
COL next_extent FORMAT 9999990 HEADING "Next (K)"
COL nls_language FORMAT a30 HEADING "NLS Language"
COL number_of_extents FORMAT 9999990 HEADING "Num Extents"
COL max_extents FORMAT 9999990 HEADING "Max X"
COL min_extents FORMAT 9999990 HEADING "Min X"
COL module_db_status FORMAT a9 HEADING "DB Status"
COL module_short_name FORMAT a8 HEADING "Module"
COL module_version FORMAT a8 HEADING "Version"
COL oracle_id FORMAT 99990 HEADING "ID"
COL oracle_username FORMAT a12 HEADING "Schema"

Chapter 5 - Page 33
COL owner FORMAT a10 HEADING "Owner"
COL product_group_id FORMAT 990 HEADING "ID"
COL product_group_name FORMAT a28 HEADING "Product Group
Name"
COL product_group_type FORMAT a10 HEADING "Type"
COL product_version FORMAT a8 HEADING "Version"
COL argument1 FORMAT a20 HEADING "Arguments"
COL release_name FORMAT a12 HEADING "Release"
COL read_only_flag FORMAT a4 HEADING "Type"
COL sizing_factor FORMAT 99990 HEADING "Size%"
COL segment_name FORMAT a10 HEADING "Name"
COL status FORMAT a9 HEADING "Status"
COL tablespace FORMAT a12 HEADING "Main TS"
COL tablespace_name FORMAT a10 HEADING "Tablespace"
COL temporary_tablespace FORMAT a12 HEADING "Temp TS"
COL default_tablespace FORMAT a12 HEADING "Default TS"
COL updated FORMAT a11 HEADING "Updated"
prompt
prompt Oracle Applications Database Configuration Report
prompt
prompt
prompt All dates are shown in DD-MM-YYYY FORMAT
prompt
set head off

select 'Report Date : '||to_char(sysdate,'DD-MM-YYYY HH24:MI:SS')
, 'Database name: '||value database
from v$parameter where name='db_name';
set head on
prompt --> Sql*Plus PAUSE setting

prompt
show pause
prompt
prompt --> Sql*Plus NEWPAGE setting
prompt

Chapter 5 - Page 34
show newpage
prompt
prompt --> Rollback Segment Information
select dr.segment_name, dr.owner, dr.tablespace_name,

dr.initial_extent/1024 initial_extent,
dr.next_extent/1024 next_extent,
dr.min_extents, dr.max_extents,
dr.status
from dba_rollback_segs dr
order by 1;
prompt --> Rollback Segment Sizes
select ext.segment_name, ext.owner, ext.tablespace_name,

sum(ext.bytes)/1024 current_size,
count(*) number_of_extents
from dba_extents ext
where ext.segment_type = 'ROLLBACK'
group by ext.segment_name, ext.owner, ext.tablespace_name
order by 1;
prompt
prompt --> Start of Application Information Gathering
prompt
prompt --> Product Group Information
select product_group_id, product_group_name, release_name,

product_group_type, argument1
from fnd_product_groups;
prompt --> Multi-Org enabled?
set head off

select decode(multi_org_flag,'N','No','Y','Yes','No')

Chapter 5 - Page 35
set head on
prompt --> Existing Operating Units
select ORGANIZATION_ID, NAME

from hr_operating_units
order by ORGANIZATION_ID;
prompt --> Multi-Currency enabled?
set head off

select decode(multi_currency_flag,'N','No','Y','Yes','No')
set head on
prompt --> Registered Applications
select application_id, application_short_name, basepath

from fnd_application
order by application_id
/
prompt --> Registered ORACLE Schemas
select fou.oracle_id, fou.oracle_username

, fou.install_group_num, fou.read_only_flag
, decode(nvl(du.username,' X '),' X ','No','Yes') in_dba_users
, nvl(du.default_tablespace,'Unknown') default_tablespace
, nvl(du.temporary_tablespace,'Unknown') temporary_tablespace
from dba_users du, fnd_oracle_userid fou
where du.username(+) = fou.oracle_username
order by 1
/
prompt --> Product Installation Status and other product information
select decode(nvl(a.APPLICATION_short_name,'Not Found'),

'SQLAP','AP','SQLGL','GL','OFA','FA',
'Not Found','id '||to_char(fpi.application_id),

Chapter 5 - Page 36
a.APPLICATION_short_name) apps,
decode(nvl(o.ORACLE_username,'Not Found'),
'Not Found','id '||to_char(fpi.oracle_id),
o.ORACLE_username) ORACLE_username,
decode(fpi.status,'I','Installed','S','Shared',
'N','Inactive',fpi.status) status,
fpi.db_status, fpi.install_group_num,
fpi.product_version, fpi.sizing_factor,
fpi.tablespace, fpi.index_tablespace
from fnd_oracle_userid o, fnd_application a, fnd_product_installations fpi
where fpi.application_id = a.application_id(+)
and fpi.oracle_id = o.oracle_id(+)
order by 1,2
/
prompt --> Localization Module Information
select decode(a.APPLICATION_short_name,
'SQLAP','AP','SQLGL','GL','OFA','FA',
a.APPLICATION_short_name) apps
, o.ORACLE_username
, fmi.module_short_name
, fmi.module_version
, decode(fmi.status,'I','Installed','S','Shared',
'N','Inactive',fmi.status) status
, decode(fmi.db_status,'I','Installed',
'N','Inactive',db_status) module_db_status
from fnd_oracle_userid o, fnd_application a, fnd_module_installations fmi
where fmi.application_id = a.application_id(+)
and fmi.oracle_id = o.oracle_id(+)
order by 1,2,3
/
prompt --> Registered Data Groups
select data_group_id,
data_group_name
, decode(default_group_flag,'N','No','Y','Yes',
default_group_flag) default_group_flag

Chapter 5 - Page 37
, to_char(creation_date,'DD-MM-YYYY') creation, created_by crby
, to_char(last_update_date,'DD-MM-YYYY') updated,
last_updated_by luby
from fnd_data_groups
order by data_group_id
/
prompt --> Base language and other Installed languages
select decode(installed_flag,'I','Installed','B','Base','Unknown')
installed_flag,
language_code, nls_language from fnd_languages
where installed_flag in ('I','B')
order by installed_flag;
prompt --> Setting of NLS_NCHAR_CHARACTERSET'
set head off

select VALUE NLS_NCHAR_CHARACTERSET from
V$NLS_PARAMETERS
WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET';
set head on
prompt --> Setting of NLS_CHARACTERSET
set head off

select VALUE NLS_CHARACTERSET from V$NLS_PARAMETERS
where PARAMETER = 'NLS_CHARACTERSET';
set head on
prompt --> Setting of NLS_DATE_FORMAT
set head off

select VALUE NLS_DATE_FORMAT from V$NLS_PARAMETERS
where PARAMETER = 'NLS_DATE_FORMAT';
set head on
prompt --> Setting of NLS_NUMERIC_CHARACTERS

Chapter 5 - Page 38
set head off
select VALUE NLS_NUMERIC_CHARACTERS from
V$NLS_PARAMETERS
where PARAMETER = 'NLS_NUMERIC_CHARACTERS';
set head on
prompt --> Setting of NLS_LANGUAGE
set head off

select VALUE NLS_LANGUAGE from V$NLS_PARAMETERS
where PARAMETER = 'NLS_LANGUAGE';
set head on
prompt --> Setting of NLS_SORT
set head off

select VALUE NLS_SORT from V$NLS_PARAMETERS
where PARAMETER = 'NLS_SORT';
set head on
prompt --> Replication Package Installed?
set head off

select decode(count(*), 0, ' Not Installed ', ' Yes, Installed ')
from all_objects
where object_name in ( 'REPCOLUMN');
set head on
prompt
prompt --> End of Application Information Gathering
spool off
exit;
SCRIPT = REPORT IMMINENT EXTENT FAILURE

NAME = REPEXTFAIL.sql
DESCRIPT=This script will report on imminent next extent
failures.

Chapter 5 - Page 39
REM ***** REPORT IMMINENT EXTENT FAILURE
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'REPORT IMMINENT EXTENT FAILURE' SKIP 2

COL Tablespace FORMAT A10 HEADING "Tablespace"
COL Type FORMAT ALL HEADING "Object Type"
COL Name FORMAT A30 HEADING "Object Name"
COL Partition_Name FORMAT A10 HEADING "Partition"
COL Next_Extent FORMAT 9,999,999,999 HEADING "Next
Extent (b)"
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF

REPHEADER OFF
BREAK ON TABLESPACE
SELECT dbas.Tablespace_Name tablespace,

decode(dbas.segment_type,'TABLE PARTITION',
'TABLE','INDEX PARTITION', 'INDEX',
dbas.segment_type) Type, dbas.segment_name
name, nvl(dbas.partition_name, 'N/A')
Partition_Name, dbas.next_extent
Next_Extent
FROM dba_segments dbas, dba_free_space dbafs
WHERE dbas.segment_type in ('TABLE', 'INDEX',
'TABLE PARTITION', 'INDEX PARTITION')
AND dbafs.tablespace_name =
dbas.tablespace_name
GROUP BY dbas.tablespace_name,

Chapter 5 - Page 40
dbas.segment_type, dbas.segment_name,
dbas.partition_name, dbas.next_extent
HAVING max(dbafs.bytes) < dbas.next_extent
ORDER BY 1,2,3,4;
SCRIPT = REPORT USER SPACE

NAME = REPUSRSPACE.sql
DESCRIPT=This script will report on space usage by user
REM ***** REPORT USER SPACE
CLEAR COMPUTES
CLEAR BREAKS
REPHEADER LEFT 'REPORT USER SPACE' SKIP 2

COL Tablespace FORMAT A15 HEADING 'Tablespace'
COL Username FORMAT A15 HEADING 'User Name'
COL Usage FORMAT 999,999,999 HEADING 'Usage'
COL Quota FORMAT 999,999,999 HEADING 'Quota'
COL Percent FORMAT 9,999.9 HEADING '%'
SET PAGESIZE 66
SET LINESIZE 80
SET NEWPAGE 0
SET VERIFY OFF

REPHEADER OFF
BREAK ON TABLESPACE SKIP 1

COMPUTE SUM OF USAGE ON TABLESPACE
COMPUTE SUM OF QUOTA ON TABLESPACE
SELECT dbatq.tablespace_name TABLESPACE,

dbatq.username, dbatq.bytes Usage,

Chapter 5 - Page 41
dbatq.max_bytes QUOTE
FROM dba_ts_quotas dbatq, dba_users dbau,
dba_tablespaces dbat
WHERE dbau.username = dbatq.username
AND dbat.tablespace_name =
dbatq.tablespace_name
AND dbat.status = 'ONLINE'
AND (dbatq.bytes > 0 or dbatq.max_bytes > 0)
ORDER BY dbatq.tablespace_name, dbatq.username;

Chapter 5 - Page 42
Summary
Summary

• Use SQL scripts to explore Oracle Applications
database objects.

Chapter 5 - Page 43

Chapter 5 - Page 44
Foundation: Overview
Chapter 6
11i Manufacturing Functional Foundation: Overview

Chapter 6 - Page 1
11i Manufacturing Functional Foundation:

Overview
Copyright  Oracle Corporation, 2001. All rights reserved.

Chapter 6 - Page 2
Objectives
Objectives
After completing this lesson, you should be able to do

the following:
• Describe application development standards
• Discuss Entity Relationship Diagrams (ERDs)
• Describe the Oracle manufacturing applications
• Describe the benefits of using and the methods for
managing your open interface processing
• Discuss data conversion
Topics
This unit describes the database tables that are affected by setup activities
within certain Oracle Manufacturing applications.
At the end of this unit, you should be able to identify these tables within each
application setup definition and explain the major columns within each table.
Additionally, you should be able to understand and use an entity relationship
diagram from an application technical reference manual to assist you in further
exploring these database table relationships.

Chapter 6 - Page 3
Agenda
Agenda
• Application development standards

• Entity Relationship Diagram (ERD) definitions
• Oracle manufacturing applications
• Open interfaces and data conversion

Chapter 6 - Page 4
Agenda
Agenda

• Entity Relationship Diagram definitions

Chapter 6 - Page 5
Application Development Standards
Application Development Standards
• Applications server directory structure

• Database object naming conventions:
– Database object names
– Table and view names
– Column names
– Index names
• Development standards:
– WHO columns
– Column order
• Program naming standards

Chapter 6 - Page 6
The Applications Server Directory Structure
The Applications Server Directory

Structure
$APPL_TOP
applsys.
applsys.env fnd inv “custom”
1.0
1.0
bin lib forms ......

®
The Directory Structure of Oracle Applications Product Files

In the basic directory structure, a top applications directory holds one set of
product files. You create this directory and set the environment variable
$APPL_TOP to point to it. AutoInstall sets up a directory tree for each fully
installed or dependent product under this directory.
A product directory tree starts with a directory that uses the short name of the
product, such as inv for Oracle Inventory. It also contains a version directory
and various subdirectories for product files.
If you will be using custom code and programs, you need to set up a separate
directory to hold the custom code so that it will not be overwritten during a
system upgrade by the AutoInstall program.

Chapter 6 - Page 7
Database Naming Conventions
Database Naming Conventions
Naming Standards
Oracle uses certain standards to create tables, columns, views, and indexes.
Following these guidelines makes it easier for you to understand the application
data structures that support them.
Database objects (tables, views, or indexes) should be:
• Unique across all applications
• Prefixed with the application short name
• Plural
• End-user oriented
• Concise (avoid unnecessary abbreviations)
• Unambiguous
Column names should be:
• Unprefixed if not a primary key column
• Singular
• End-user oriented
• Concise (avoid unnecessary abbreviations)
• Unambiguous
Index names should:
• Reflect the name of the table they index (prefix is the table name)
• Be identified as unique indexes by using the suffix _Um, where m is a
number

Chapter 6 - Page 8
• Be identified as nonunique indexes by using the suffix _Nm, where m is a
number
Note: One method used to name custom indexes is to begin with “99” and work
backwards. If you name a custom index “N4,” and then in Oracle’s next release
an index named “N4” is used, it will overwrite your custom index.

Chapter 6 - Page 9
Standards for Development

Column Names
All tables must have the following column names in order to facilitate the WHO
query:
LAST_UPDATE_DATE LAST_UPDATED_BY
LAST_UPDATE_LOGIN CREATION_DATE
CREATED_BY
The following columns should be included, although they are not required:
REQUEST_ID PROGRAM_APPLICATION_ID
PROGRAM_ID PROGRAM_UPDATE_DATE
Column Order
Order the table columns according to the following priorities:
Primary key columns (major to minor)
WHO columns
Required columns
Foreign keys
Optional columns
Attributes (descriptive flexfield columns)
LONG data types
Standards in Programming

Chapter 6 - Page 10
Standard Abbreviations
Standard abbreviations make applications easier to understand. The following is
a partial list of common abbreviations used in Oracle Applications:
AVG Average
ID System-generated unique identifier
LEN Length
MAX Maximum
MIN Minimum
MISC Miscellaneous
NUM End-user-visible number
SEQ Sequence
SPEC Specification
UOM Unit of measure
Program Names
You use program naming guidelines to identify the application, location, and
function of a program. The general program name format is AAAGGDDD,
where:
AAA is a three-character application prefix, using “X” to fill blanks
GG is a two-character group building-block identification
DDD is a three-character letter form description
All program names must be made up of eight characters. Use uppercase letters
for the program name and lowercase letters for extensions.

Chapter 6 - Page 11
Summary
Summary
In this lesson, you have learned how to use:

• Directory structure of Oracle Application files
• Database object naming conventions:
– Database object names
– Table and view names
– Column names
– Index names
• Application development and program naming
standards

Chapter 6 - Page 12
Agenda
Agenda


Chapter 6 - Page 13
Entity Relationship Diagram Definitions
Entity Relationship Diagram Definitions
• Primary key
• Foreign Key
• Diagramming Conventions

Chapter 6 - Page 14
Primary Key
Primary Key
PO_HEADERS_ALL Table
PO_HEADER_ID VENDOR_ID APPROVED_FLAG ...
123 57 Y .. .
124 58 N ...
. .. . .. . .. .. .
The primary key of the table is the column or set

of columns that makes every row in that table
unique.
®
Description
Good relational database design ensures data integrity and minimizes data
redundancy. These goals are accomplished by storing the details of an entity
(such as item, supplier, and category) only once, and maintaining relationships
between that entity and other entities in the database that need access to its
details. For example, an item description is stored only once, but bills of
material that use that item as a component need access to its description. The
database design maintains a relationship between the table that stores the item
attributes (MTL_SYSTEM_ITEMS_B) and the table that represents the bills of
material component (BOM_INVENTORY_COMPONENTS). Since items and
components are called entities, these relationships are referred to as entity
relationships.

Chapter 6 - Page 15
Foreign Key
Foreign Key
PO_LINES_ALL Table
PO_LINE_ID PO_HEADER_ID LINE_NUM ITEM_ID ...
587 123 1 1024 .. .
588 123 2 957 .. .
589 124 3 587 .. .
A foreign key within one table references a

primary key that has been previously defined
elsewhere in the database.
®
Description
In a relational database, foreign key relationships are represented by storing a
matching element of data in both tables. Most often, it is the data element (or
combination of elements) that uniquely identifies an entity, the primary key,
stored in another table to indicate the relationship between tables. When the
primary key from one table is stored in another table, it is referred to as the
foreign key. For example, the primary key of the MTL_SYSTEM_ITEMS_B
table (INVENTORY_ITEM_ID/ ORGANIZATION_ID) is stored as a foreign
key in BOM_INVENTORY_COMPONENTS table. Refer to the application
Technical Reference Manual (TRM) for the complete listing of foreign keys.
Multiple Products with Shared Entities
• Items:
– Bills of Material/Engineering
– Planning
– Inventory
– Order Management
– Work in Process
• Locations:
– Inventory
– Master Scheduling/MRP
– Oracle Payables
– Purchasing

Chapter 6 - Page 16
• Organizations
• Salespersons:
– Oracle Order Management
– Oracle Receivables
• Sets of Books:
– Fixed Assets
– General Ledger
– Inventory
– Payables
– Purchasing
– Project Accounting
– Receivables
– Work in Process

Chapter 6 - Page 17
Primary Key Relationships
Primary Key Relationships

PO_HEADERS_ALL
PO_HEADER_ID VENDOR_ID APPROVED_FLAG .. .
123 57 Y ...
124 58 N ...
. .. . .. . .. .. .
PO_LINES_ALL
PO_LINE_ID PO_HEADER_ID LINE_NUM ITEM_ID ...

587 123 1 1024 .. .
588 123 2 957 .. .
589 124 3 587 .. .
Note
In the example in the slide, PO_HEADER_ID is the primary key in the
PO_HEADERS_ALL table and the foreign key in the PO_LINES_ALL table.

Chapter 6 - Page 18
Foreign Key Example
Foreign Key Example
Primary Key Table Primary Key Column Foreign Key Column
PO_HEADERS_ALL PO_HEADER_ID FROM_HEADER_ID

PO_VENDORS VENDOR_ID VENDOR_ID
PO_VENDOR_CONTACTS VENDOR_CONTACT_ID VENDOR_CONTACT_ID
PO_VENDOR_SITES VENDOR_SITE_ID VENDOR_SITE_ID
PO_HEADERS_ALL table contains information for

your purchasing documents. Each row contains
buyer information, supplier information, notes,
foreign currency information, terms and
conditions information, and the document status.
®
Note
You can refer to each individual application Technical Reference Manual
(TRM) for the full list of tables with their primary and foreign keys. For the
example above, refer to the Oracle Purchasing Technical Reference Manual.
You can find a list of these manuals in the Related Publications section of the
preface.

Chapter 6 - Page 19
Database Diagramming Conventions
Database Diagramming Conventions

Optionality
Must be relationship
May be relationship
Types of Table Relationships
Each row in Table A
may be related to a row
A B in Table B
Each row in Table A

must be related to a
A B row in Table B; a row
in Table B may be
related to one or more
rows in Table A
B
Each row in Table A
must be related to a
A row in either Table B
or Table C, but not
both
C
Database Diagrams
A database diagram or entity relationship diagram (ERD) graphically represents
the database tables of an application and the relationships among them. By
understanding these diagrams, you can learn which tables are used by a
particular application and how these tables interrelate.
The major tables and their relationships are discussed within each Oracle
application module, with reference to the ERD.
Additionally, each Oracle application module has a technical reference manual
that details these relationships. Refer to these technical reference manuals for
additional information regarding the database table relationships. For the
purpose of this course, the primary tables selected are based on the core
manufacturing tasks performed in a business environment.

Chapter 6 - Page 20
Practice Setup
Practice Setup
1. Create a new user name for yourself, and assign

the following responsibilities to it:
– Manufacturing, Vision Operations
– System Administrator
– Application Developer
2. Sign back onto the system with your new user
name.
Add Yourself as a User

1 With System Administrator responsibility, navigate to define a new user.
(N) Security > User > Define
2 Enter a new user name APPS## (where ## is your terminal number) and a
description for yourself.
3 Enter a temporary password - “first” works well. You will need to re-enter it
to confirm it.
4 Select “Baker, Catherine” from the List of Values in the “Person” field to
the right of the User Name field. You will get a Caution screen - click OK.
5 Select a Customer and a Supplier in the appropriate fields from the List of
Values.
6 In the Responsibility region, use the List of Values (LOV) to select the
following Responsibilities:
– System Administrator
– Manufacturing, Vision Operations (USA)
– Application Developer
7 Save your work.
8 Close the form.
Log on as Yourself
(N) (M) File > Log On

Chapter 6 - Page 21
1 Enter your new user name and the temporary password you selected. The
system informs you that the password has expired. Enter “Oracle” as the
new password.
2 Select Manufacturing, Vision Operations responsibility.
Instructor Note
Perform the following setup and practices if they have not been performed in
the Technical Foundation segment of this course.

Chapter 6 - Page 22
Practice Overview
Practice Overview
1 Find the code values for the days of the week.

2 Find the user id that corresponds to your user
name. Find your encrypted password.
(For extra credit, decrypt the password.)
3 Find Determine what responsibilities are assigned
to your user name.

Chapter 6 - Page 23
Practice 1
Practice 1
Instructions
Enter the following values for Tables, Keys, and Columns:
• Tables: fnd_lookups
• Keys: lookup_type
• Columns: lookup_type, lookup_code, meaning

Chapter 6 - Page 24
Practice 1 Solution
Practice 1 Solution
SQL Code Solution

SELECT
substr(lookup_type,1,15) “Type”,
substr(lookup_code,1,5) “Code”,
substr(meaning,1,15) “Meaning”
FROM
fnd_lookups
WHERE
lookup_type LIKE ‘DAY_OF_WEEK’

Chapter 6 - Page 25
Practice 2
Practice 2

name. Find your encrypted password.
(For extra credit, decrypt the password.)
Instructions
• Tables: fnd_user
• Keys: user_name
• Columns: user_name, user_id, encrypted_user_password

Chapter 6 - Page 26
Practice 2 Solution
Practice 2 Solution

name.
SQL Code Solution

SELECT
substr(user_name,1,10) “Name”,
substr(user_id,1,10) “ID”,
substr(encrypted_user_password,1,70) “Password”
FROM
fnd_user
WHERE
user_name LIKE ‘&UserName%’

Chapter 6 - Page 27
Practice 3
Practice 3

to your user name.
Instructions
• Tables: fnd_user, fnd_user_responsibility, fnd_responsibility_tl
• Keys: user_name, responsibility_id, application_id, user_id
• Columns: user_name, responsibility_name

Chapter 6 - Page 28
Practice 3 Solution
Practice 3 Solution

to your user name.
SQL Code Solution

SELECT
substr(usr.user_name,1,10) “User Name”,
substr(res.responsibility_name,1,55) “Resp Name”
FROM
fnd_user usr,
fnd_responsibility_tl res,
fnd_user_resp_group ur
WHERE
usr.user_name LIKE ‘&UserName%’ AND
res.responsibility_id = ur.responsibility_id AND
ur.user_id = usr.user_id

Chapter 6 - Page 29
Practice 4
Practice 4
Find the Inventory Organizations in the Vision

database and their parent organizations.
Instructions
• Tables: mtl_parameters, hr_all_organization_units
• Keys: organization_id
• Columns: organization_id, organization_code, name,
master_organization_id

Chapter 6 - Page 30
Practice 4 Solution
Practice 4 Solution
Find the Inventory Organizations in the Vision

database and their parent organizations.
SQL Code Solution

SELECT
• substr(org.organization_id,1,5) “ID”,
• substr(org.organization_code,1,5) “Code”,
• substr(hr.name,1,30) “Name”,
• substr(org.master_organization_id,1,10) “Parent”
FROM
• mtl_parameters org,
• hr_all_organization_units hr
WHERE
• hr.organization_id = org.organization_id

Chapter 6 - Page 31
Agenda
Agenda


Chapter 6 - Page 32
Oracle Manufacturing Applications
Oracle Manufacturing Applications
• Inventory
• Bills of Material
• Engineering
• Cost Management
• Work in Process
• Purchasing
Lesson Overview
The core Oracle Manufacturing applications major functionalities will be
discussed at a very high level to facilitate the database table discussions. For
detailed application information, attend an individual class covering detailed
content specific to that application module.

Chapter 6 - Page 33
Oracle Inventory
Oracle Inventory
Supplier
Transfer
Inventory
Shipment
Receive Deliver Shop floor
Order entry
Internal
shipment Expense
Inventory Inspect
®
Description
Oracle Inventory maintains quantities on hand using a variety of stock
maintenance tools, controlled transactions, and planning methods.
Organization and Item Definition
• Set up inventory structure.
• Define stock and nonstock parts.
• Establish planning and purchasing attributes.
• Track inventory by item, item revision, serial number, or lot number.
Transactions and Maintenance
• Receive parts from and return parts to suppliers.
• Transfer inventory between organizations directly or as in-transit
shipments.
• Add material overhead to the cost of a part.
• Conduct inventory cycle counts based on ABC classification.
• Record physical inventory counts and adjustments.
• Process miscellaneous issues and receipts.
• Transfer material between subinventories.
• Receive and inspect material returned from a customer.
• Track lots and serial numbers for an item.
• Return repaired or substitute items to a customer.

Chapter 6 - Page 34
Forecasting and Planning
• Generate forecasts for future product demand.
• Generate or modify requisitions using the min/max or the reorder point
planning methods.

Chapter 6 - Page 35
Oracle Bills of Material
• The Oracle engineering products are Oracle Bills

of Material and Oracle Engineering.
• You use Oracle Bills of Material to:
– Create and maintain production bills of
materials
– Create and maintain production resources,
departments, routings, and lead times
– Perform mass changes
– Delete product information
– Maintain the workday calendar
Oracle
Bills of Material
®
Description
Oracle Bills of Material develops and maintains manufacturing bills of material
(BOMs) and routings to drive planning, costing, and work-in-process tracking.
Routings
• Specify department and resources usage.
• Define shop floor controls.
• Maintain multiple revisions of routings.
• Define Dybanic, lot-based flow routing for operation flexibility.
Bills of Material
• Define component usage, yield, and material control.
• Integrate with routings for point-of-use definition.
• Maintain multiple revisions of bills of material.
Lead Time
Calculate manufacturing lead time to produce goods from routing standards.
Standard Cost
Calculate standard costs from bills of material and routings.
Views and Reports
• Perform a single-level explosion of bills of material (or fully indented
explosions).
• Choose to include or exclude costs in the explosion.

Chapter 6 - Page 36
• Compare two bills of material or alternative versions of the same bill of
material.
Maintenance
You can efficiently manage upwards of 1000 inventory organization structures
in a single Application instance, using organization hierarchies. Organization
hierarchies: by establishing hierarchies, you can group organizations together to
perform a number of processes across all organizations at any level in the
hierarchy. These processes include:
• establishing common bills
• deleting BOMs
• viewing item usage
• exporting multilevel BOMS

Chapter 6 - Page 37
Oracle Engineering
Oracle Engineering
• Create and maintain engineering items

• Create and maintain engineering bills of materials
• Create and maintain engineering resources,
• Transfer engineering product information to
production
• Process engineering change orders
• Perform mass changes
• Delete product information
Oracle Engineering
®
Description
Oracle Engineering interacts with other Oracle manufacturing applications to
provide a cohesive integrated business solution. Oracle Engineering helps you
define product and process specifications. It also provides the information
required for effective planning and execution.
Oracle Oracle Engineering
• Define engineering and manufacturing bills of material.
• Define engineering and manufacturing routings.
• Manage product changes with engineering change orders (ECOs).
• Create new design specifications using Oracle Engineering.
• Determine resource availability using the workday calendar.
• Specify detailed resource use.
Introducing New Products
• Define engineering items, BOMs, and routings to prototype new product
designs.
• Calculate lead times and release engineering prototypes to manufacturing.
Defining Planning Bills
• Define planning bills to assist with sales strategy.
• Provide BOM maintenance.
Managing Engineering Changes

Chapter 6 - Page 38
• Define and implement engineering changes to prototype and production
items.
• Schedule ECOs manually or with imbedded workflow, or to correspond to
the planned use-up of a specific item.
• Create ECOs across large organization structures at any given level in an
organization hierarchy.
Deleting Obsolete Information
Delete obsolete item and ECO information.

Chapter 6 - Page 39
Oracle Cost Management
Item Analysis Audit trail

costs
Inventory Production Profitability
Description
Oracle Cost Management automatically performs the cost accounting for all
your Oracle Inventory, Work in Process, and Purchasing transactions. At any
time, your inventory and work-in-process costs are up-to-date, and your
inventory value matches the cumulative total of your accounting transactions.
Standard Costing
• Oracle Cost Management supports standard costing for inventory, bills of
material, and work-in-process costing.
• You may use standard costing for one organization and average costing for
another organization.
Average Costing
• Oracle Cost Management supports average costing for inventory, bills of
material, and work-in-process costing. Average costs are automatically
updated as transactions are processed.
• If you have Oracle Bills of Material installed, you can transact your
inventory at average, and use the standard cost features for product cost
simulations and budgeting.
Extensive Cost Simulation Capability
Create unlimited sets of product costs, called cost types. Each cost type has its
own items and specific cost controls for the items.

Chapter 6 - Page 40
Copy from one cost type to another, mass edit a cost type, run item cost and
comparison reports, roll up costs, or update frozen standard costs by cost type.
Each cost type may have its own activities and activity-based costs.
Simultaneous Open Periods
Set up and maintain simultaneous open periods.
Run transactions for the next period and still report inventory balances and
quantities from the prior open period using historical inventory valuation
reports.
This gives you the flexibility to reconcile and analyze the period before you
close it, while you continue to conduct business in the subsequent period.
Period Close and General Ledger Transfer
Close the earliest open period at any time. Closing a period automatically
transfers summary or detailed information to the general ledger.
Perform interim general ledger transfers at any time, without closing a period.
The general ledger transfer passes all accounting entries not transferred since
the last period close.
Accruals Booked on Receipt
Oracle Purchasing updates the accounts payable accrual accounts automatically
and accrues your uninvoiced receipts.

Chapter 6 - Page 41
Oracle Work in Process
Oracle Work in Process
Manufacturing methods include:

• Discrete manufacturing
• Repetitive manufacturing
Work in Process Functionality

Oracle Work in Process supports discrete, repetitive, assemble-to-order, work
order-less, or a combination of these manufacturing methods
Manufacturing Support
Build discrete jobs, both standard and nonstandard (prototype, rework,
maintenance, and special projects)
Production Scheduling
Load and sequence repetitive production by assembly and production line
Material Control
Issue and return components from and to inventory
Shop Floor Control
Move assemblies between and within operations

Chapter 6 - Page 42
Oracle Work in Process Transactions
Oracle Work in Process Transactions
Inventory Work in Process
Issue
material
Jobs and
Raw material
schedules
inventory
Complete
finished
assemblies Move assemblies on
the shop floor and
charge resources
Finished goods
Scrap rejected
subinventory assemblies
Description
Oracle Work in Process tracks material and production activity on the shop
floor to facilitate inventory control, job scheduling, and costing.
Material Issue
Record material issues to discrete jobs, repetitive schedules, or nonstandard
jobs.
Shop Floor Move
Record production activity and job completions.
Resource Charging
• Charge multiple resources option.
• Charge resources automatically (based on shop floor moves) or manually, at
either standard or actual labor rates.
Other Transactions
• Cost material using standard cost.
• Use repetitive schedules to simplify material and production reporting.
• Use lot and serial number controlled parts in production moves.

Chapter 6 - Page 43
Oracle Purchasing
Oracle Purchasing
ve
Manually ppro Automatically
A
create create
PO
Requisition
pool
Maintain documents
Accept Revise Control
Receive against PO Match invoices in Payables

®
Description
Oracle Purchasing is a comprehensive procurement solution, designed to reduce
administration costs while focusing on value analysis, strategic supply base
management, and contract negotiation.
Requisitioning
• Replace paper processing with online requisition generation, purchase order
creation, and document approval.
• Regulate document access, control or modification activity, and approval
based on organizational signature and security policies.
• Minimize data entry time with time-saving templates, express processing
functions, and default infrastructures.
Purchasing
• Control purchasing activity and enable accurate automatic pricing using an
approved supplier list.
• Consolidate purchase requirements from multiple warehouses, plants, or
locations.
Receiving
Receive production items, Maintenance, Receipt and Overhead (MRO) items,
and services using a common flexible receiving process.
Business Communication
• Facilitate communication between requesters, buyers, receiving staff, and
accounts payable staff using online inquiries and notes.

Chapter 6 - Page 44
• Provide access to purchasing information to related functions (marketing,
finance, legal, master scheduling, inventory management, production, cost
accounting, customer order entry) on an optional basis.
• Manage historical data.

Chapter 6 - Page 45
Purchasing Transactions
Purchasing Transactions
• Suppliers
• Requisitions
• Purchase orders
• Receipt and delivery
Transaction Functionality
Purchasing provides you with request for quotation (RFQ) and quotation
features to handle your sourcing needs. You can create an RFQ from
requisitions, match supplier quotations to your RFQ, and automatically copy
quotation information to purchase orders.
Additionally, you are able to:
• Review all your purchases with your suppliers to negotiate better discounts
• Create purchase orders simply by entering a supplier and item details
Purchasing provides you with the features you need to satisfy your receipt,
inspection, transfer, and delivery needs.

Chapter 6 - Page 46
Agenda
Agenda


Chapter 6 - Page 47
Importing Information
Oracle Manufacturing applications import programs

provide the features you need to fill the following
basic integration needs:
• Import data more easily by using a format that is
consistent with the structure of your new system
• Import from a variety of environments
• Review the results of an import program
Basic Importing Needs
Oracle Manufacturing applications import programs provide the features you
need to fill the following basic integration needs:
To import information in the easiest way possible, the format must be consistent
with the structure of the new system.
Import information from a variety of environments, including your own and
other accounting systems.
Import historical data from your previous manufacturing, sales order, or other
management systems to keep your records consistent and up-to-date.
Review the results of your import run. Identify which data has been successfully
imported and any errors that may have occurred during the import process.
Choosing a Feeder Program
You must choose a tool for writing a feeder program to extract data from your
existing application system’s printed reports, flat file, relational database, or
other repository of application information. Use your feeder program to
populate an Oracle application import table with the information you want to
introduce to your Oracle manufacturing system.
SQL*Loader is a powerful and easy-to-use tool that you can use to write a
feeder program. It enables you to map elements of a character-delimited or
fixed-format file, such as a listing or flat file, and to specify which columns of
which tables they populate.

Chapter 6 - Page 48
Benefits of open interfaces:

• Using open interfaces to facilitate integration
• Converting static data
Importing Information (continued)

Benefits of Using Open Interfaces
When you use open interfaces to facilitate integration, you can:
• Integrate applications from different suppliers with Oracle Applications
• Integrate your custom applications with Oracle Applications
• Integrate data from numerous sources, such as data-collection devices
• Ensure validity of any data in your system through use of a common
validation function, regardless of the source of the data
Oracle Applications open interfaces simplify the process of converting data that
is relatively static from a prior system to Oracle Applications.
Do not bypass the open interfaces process. When Oracle Applications are used
to perform a manufacturing function, any change you make may update many
tables at once. Oracle Applications then perform an audit to ensure that all of
the changes are valid. If you modify Oracle Applications data using SQL*Plus,
you can change a row in one table without changing rows in all necessary
related tables. In this case, you violate the ability to audit and may potentially
destroy the integrity of your data.

Chapter 6 - Page 49
Open Interface Model
Open Interface Model

Source
Source
application
application
Temp
Temp
tables
tables Load Validate
Errors
Interface table
Maintain table (optional)
Process
Destination
Destination
application
application
®
Oracle Applications Open Interface Model

Source Application
The source application, or feeder system, is the application that supplies the data
you want to import into Oracle Applications.
Interface Table
The interface table is the intermediary table where the data from your source
application temporarily resides. To load data into an Oracle application, you
must enter data into this table.
VALIDATE Function
The VALIDATE function is a set of programs used by Oracle Applications to
ensure the integrity of inbound data before the data is moved from the interface
table to the permanent application tables. The VALIDATE function inserts rows
into the errors table or updates the error column in the interface table if
validation fails. The VALIDATE function resides in the destination application.
Errors Table
•Stores all errors found by the VALIDATE and PROCESS functions
•Enables you to see several errors for the same data row at once
•Resides in the destination application
•Several open interface tables in an application can share an errors table.
•Instead of an errors table, some Oracle Applications open interfaces use an
error column in the interface table and a log file or report to list the error. For
example, Oracle General Ledger Journal Import always generates a report.

Chapter 6 - Page 50
•Entries in an error table or error report are the output of the VALIDATE
process.
•All Oracle Applications open interfaces have either an errors table or an error
column and a log/report file.
•LOAD Function
•The LOAD function is a program or set of programs that selects and
accumulates data from your source application and inserts it into the Oracle
Applications interface table.
•The programming languages and tools used in the LOAD function depend on
the hardware and system software of your source application. For example,
Oracle functions in Oracle Applications that load an open interface are written
in Pro*C or PL/SQL.
•If you are importing data from an application that is not Oracle, you would
probably use a procedural language available on the source application, convert
it into an ASCII file, and use SQL*Loader to insert the data into the Oracle
interface table.
•PROCESS Function
•The PROCESS function, or import function, is the program or set of programs
that processes the data from the interface table into the destination tables. It also
inserts rows into the errors table or updates the error column in the interface
table if processing errors are encountered.
•The PROCESS function resides in the destination application.
•Although the VALIDATE function and the PROCESS function meet two
distinct needs, they are frequently invoked through the same concurrent process.
Rows are validated first, and then the valid rows are processed.
•MAINTAIN Function
•The MAINTAIN function is a form-based program that you can use to query,
update, and resubmit interface table rows. Some Oracle Applications interfaces
do not have a form-based MAINTAIN function. In those cases, you can review
the log file or report for errors, or you can use SQL*Plus to query up and
correct errors.
•If there is a high volume of errors, you may find it preferable to delete all rows
in the interface table, fix the problem in the LOAD function, and reimport. The
MAINTAIN function resides in the destination application.

Chapter 6 - Page 51
Managing Open Interface Processing
Using Oracle Applications, you can tailor your

concurrent process parameters for frequently used
interfaces to fit the size and load of your system. All
of the parameters listed affect the process function as
described earlier.
• Batch size
• Launching multiple concurrent processes
• General prerequisites

Using Oracle Applications, you can tailor your concurrent process parameters for
frequently used interfaces to fit the size and load of your system. All of the
parameters listed affect the PROCESS function as described earlier.
Batch Size
For frequently used open interfaces, you can use Oracle Applications to determine
the batch size—that is, the number of rows you want processed in one batch. You
set the batch size to reflect your system’s memory restrictions during processing.
Launching Multiple Concurrent Processes
For high-volume interfaces, you can use some Oracle applications to launch more
than one concurrent process to handle the processing of your data.
General Prerequisites
Before you perform an open interface, you should be familiar with the forms used
to populate the data tables from within the application. It is advisable to walk
through, or to work with a functional user to walk through, the forms entry for
data population before trying to perform an open interface from the back end.

Chapter 6 - Page 52
Data Conversion
Data Conversion
Data Conversions
The purpose of this section is to give you an understanding of how to perform
data conversions from external systems to Oracle Applications products. The
emphasis in this section is on conversion methodology, not on one specific
conversion (for example, item conversion).

Chapter 6 - Page 53
Detailed Conversion Plan
Detailed Conversion Plan
Movement of Data
Plan the movement of data from an external system to Oracle Applications with
a conversion project plan. Develop a detailed conversion plan for each entity,
listing all design, development, testing, and conversion tasks. Include resource,
software, and hardware requirements to successfully convert each entity.
Designing the Conversion Process
• Determine what data to convert (for example, convert only active data).
• Document business objectives.
• Specify time constraints for the conversion, especially for dynamic data.
• Determine the appropriate conversion method; do not overlook manual data
entry.
• Perform data mapping.
• Install all hardware and software required for the conversion.
• Scope all coding efforts, including the cleanup of existing data, extract
programs, translation programs, validation programs, and migrating
programs.
• Determine the testing requirements.
Developing Programs for Conversion
• Write extract and import programs.
• Write scripts to create any interface or translation tables in Oracle RDBMS.
• Write validation, translation, and migration programs.

Chapter 6 - Page 54
• Write verification scripts and reports.
Performing the Conversion
• Clean up existing data before conversion.
• Extract and format data from original source.
• Create interface tables in Oracle RDBMS.
• Validate and translate data.
• Import validated data into production tables.
• Run reports.

Chapter 6 - Page 55
There are seven steps you should consider when

designing your conversion process.
1
2
3
4
5
6
7
Data Verification
For each converted entity, design a conversion process from data extraction
through data verification. Consider business objectives and dependencies for
each point in the process.
Reduce the time required to execute the conversion process with accurate
designs. Plan resources effectively with reasonable time estimates and good
design specifications. Be sure to clean up the database before conversion.
Steps for Design
1 Examine the business objectives and requirements to determine the data to
be converted.
2 Map the source data to the Oracle applications.
3 Identify the tools used to extract and import data. Do not disregard manual
data entry.
4 Define flat-file configuration.
5 Identify any interface tables to create.
6 Design any translation and validation programs.
7 List the testing phases and procedures.
Instructor Note
These are points to bring up with your students, because each question is
particular to a customer’s conversion. The goal is to help students consider
issues that are critical to their conversion while you explain the conversion
method.

Chapter 6 - Page 56
• What groups in the company must be involved in determining the business
objectives?
• What technical resources (software and hardware skills) are currently
available in the company?
• What resources can own each of the design steps?

Chapter 6 - Page 57
Developing Conversion Programs
Developing Conversion Programs
1. Write extract and import programs

2. Write scripts to create interface and translation
tables
3. Write validation scripts
4. Write verification scripts and reports
Leveraging the Existing Interfaces

Leverage the existing interfaces in Oracle Applications to convert data. Write
programs using detailed design specifications to convert entities where an open
interface does not exist.
Review, test, and tune the performance of each program to ensure a clean and
timely conversion. Identify any performance problems before the conversion
date.
Steps to Develop Programs
1 Write an extract program from an external system and format the data into a
flat file.
2 Write SQL scripts and SQL*Loader files to create interface tables and
upload the data into the interface tables.
3 Write translation, validation, and import programs. Remember to populate
the WHO columns.
4 Write verification programs or reports.

Chapter 6 - Page 58
• Extract and format data

• Create temporary interface tables
• Upload data to interface tables
• Run translation programs
• Run validation programs
• Migrate data into production tables
• Run verification scripts
• Run application reports to verify converted data
Ensuring Integrity
After designing and developing all elements of the conversion, perform the
conversion. Manage any time constraints and ensure the integrity of the
converted data. Minimize the time required to actually convert from the original
system to Oracle Applications by reviewing all programs and designs before
executing the conversion process.
Steps to Perform Conversion
1 Create a unique application username, and use it to populate the WHO
columns.
2 Extract data from the original source; load and format the data in a flat file.
3 Create temporary tables using SQL*Loader scripts.
4 Use SQL*Loader scripts to upload the data into interface tables.
5 Run translation programs on data in the interface tables.
6 Run validation programs on data in the interface tables.
7 Migrate translated and validated data into the production tables.
8 Run verification scripts.
9 Run application reports to verify converted data.

Chapter 6 - Page 59
Summary
Summary
In this lesson, you have learned how to:

• Describe application development standards
• Discuss Entity Relationship Diagrams (ERDs)
• Describe the Oracle manufacturing applications
• Describe the benefits of using and the methods for
managing your open interface processing
• Discuss data conversion
Topics
This unit describes the database tables that are affected by setup activities
within certain Oracle Manufacturing applications.
At the end of this unit, you should be able to identify these tables within each
application setup definition and explain the major columns within each table.
Additionally, you should be able to understand and use an entity relationship
diagram from an application technical reference manual to assist you in further
exploring these database table relationships.

Chapter 6 - Page 60
Foundation: Inventory
Chapter 7
11i Manufacturing Functional Foundation: Inventory

Chapter 7 - Page 1

Inventory

Chapter 7 - Page 2
Objectives
Objectives

do the following:
• Discuss inventory item definition activities
• Identify the major tables used in an item definition
• Discuss inventory transaction activities
• Identify the major tables used in inventory
transactions
• Run queries in SQL*Plus against the appropriate
database tables to find a particular inventory item,
its status, and its cycle count activity
• Discuss the open interfaces for inventory
Lesson Aim
The aim of this lesson is to provide the student an overview of the item
definition process in Oracle Inventory and discuss the database tables that are
populated as a result of item setup activity.
Instructor Note
The primary key for each of the ERD tables is in each table definition in the
Notes section of the slides. Example: ‘The primary key is INVENTORY_ID,
ORGANIZATION_ID’, where there are two elements that make up the primary
key. Some _INTERFACE and _TEMP names may not have a primary key
associated with it.
An “(o)” following a primary key name indicates that element to be optional.
Example: ‘WIP_ENTITY_ID, OPERATION_SEQ_NUM,
REPETITIVE_SCHEDULE_ID (o)’. In this example it indicates that the
REPETITIVE_SCHEDULE_ID is part of the primary key when you reference
specific Repetitive schedules tables and not part of the primary key when you
reference Discrete job tables.

Chapter 7 - Page 3
Agenda
Agenda
• Item definition
• Inventory transactions
• Open interfaces

Chapter 7 - Page 4
Agenda
Agenda
• Item definition
• Open interfaces

Chapter 7 - Page 5
Oracle Inventory
Oracle Inventory
Supplier
Transfer
Inventory
Shipment
Receive Deliver Shop floor
Order entry
Internal
shipment Expense
Inventory Inspect
®
Description
Oracle Inventory maintains quantities on hand using a variety of stock
maintenance tools, controlled transactions, and planning methods.
Organization and Item Definition
• Set up inventory structure.
• Group inventory organizations into multilevel, hierarchical trees for
managing large organization structures.
• Define stock and nonstock parts.
• Establish planning and purchasing attributes.
• Track inventory by item, item revision, serial number, or lot number.
Transactions and Maintenance
• Receive parts from and return parts to suppliers.
• Transfer inventory between organizations directly or as in-transit shipments.
• Create move orders for subinventory transfers.
• Receive alerts or notifications about material shortages.
• Add material overhead to the cost of a part.
• Conduct inventory cycle counts based on ABC classification.
• Record physical inventory counts and adjustments.
• Track serial controlled items from receipt through work in process and
inventory to the customer sale.
Forecasting and Planning

Chapter 7 - Page 6
• Generate forecasts for future product demand.
• Generate requisitions using the min/max or the reorder point planning
methods.

Chapter 7 - Page 7
Oracle Inventory Database Summary Diagram
Oracle Inventory Database Summary Diagram

HR_ALL_ORGANIZATION_UNITS MTL_PARAMETERS
MTL_SYSTEM_ITEMS_TL
MTL_SYSTEM_ITEMS_B
SUBINVENTORY
LOCATOR MTL_MATERIAL_TRANSACTIONS
MTL_TRANSACTION_ACCOUNTS MTL_ONHAND_QUANTITIES
®
Oracle Inventory Item Definition

An item definition is defined for inventory items (part numbers), engineering
items (bills of material), and purchasing items (outside processing). For each
item definition, you can specify cost information, unit of measure, lead times,
physical attributes, and other pertinent business information related to each
unique item.
An item is defined in an item master organization. Then, you assign it to other
organizations that need to recognize this item.
(N) Inventory > Items > Item Master

Chapter 7 - Page 8
Inventory Organizations
Inventory Organizations
Enterprise
Vision Seattle Boston Dallas

Operations
Master Org
Organizations

Chapter 7 - Page 9
Oracle Inventory: Organizations
Oracle Inventory: Organizations
MTL_INTERORG_
MTL_PARAMETERS
PARAMETERS
HR_ORGANIZATION_
GL_SETS_OF_BOOKS
INFORMATION
GL_CODE_ HR_ALL_ORGANIZATION_UNITS
COMBINATIONS
MTL_PARAMETERS
MTL_PARAMETERS is an inventory organization with which an item is
associated. The primary key is the ORGANIZATION_ID.
MTL_INTERORG_PARAMETERS
This table identifies the receiving organizations linked to a particular
organization. You must define the interorganizational relationship before you
perform any interorganization transfers.
Units of measure, distance, transfer charge, and accounting information are also
specified in this table. The primary key is FROM_ORGANIZATION_ID,
TO_ORGANIZATION_ID.
GL_SETS_OF_BOOKS
GL_SETS_OF_BOOKS stores information about the sets of books you define
in your general ledger application. Each row includes the set of books name,
description, functional currency, and other information. This table corresponds
to the Define Set of Books form. The primary key is SET_OF_BOOKS_ID.
GL_CODE_COMBINATIONS
This table stores valid Accounting Flexfield segment value combinations for
each accounting flexfield structure within your general ledger application. The
primary key is CODE_COMBINATION_ID.
HR_ALL_ORGANIZATION_UNITS
HR_ALL_ORGANIZATION_UNITS stores generic information about
organizations. An organization can be used for various purposes in Oracle

Chapter 7 - Page 10
Manufacturing applications. For example, one organization can represent a
business group, an ECO department, a planning organization, and an inventory
organization. The primary key is ORGANIZATION_ID.

Chapter 7 - Page 11
Defining Organizations
Defining Organizations
The first organization you must set up is the Business

Group, to which all other organizations belong.
Organization
Organization
(N) Inventory > Setup > Organizations > Organizations

Chapter 7 - Page 12
Defining Organization Parameters for Additional
Information
Defining Organization Parameters for

Additional Information
You can define and update default inventory and
costing parameters for your current organization.
Inventory
Inventory Parameters
Parameters (M1)
(M1)
(N) Inventory > Setup > Organizations > Organizations (B) Others

Chapter 7 - Page 13
Locators and Subinventories
Locators and Subinventories
Locator: Sub Inv

Recv Dept. R Dept.
Locator: Organization
Sub Inv.
Eng Dept. Seattle Stores
Locator: Sub Inv.

Annex MRB

Chapter 7 - Page 14
Oracle Inventory: Subinventories and Locators
Oracle Inventory:
Subinventories and Locators
MTL_SYSTEM_ITEMS_B
MTL_SYSTEM_ITEMS_TL
MTL_SECONDARY_INVENTORIES
MTL_ITEM_SUB_INVENTORIES
MTL_ITEM_LOCATIONS
MTL_SECONDARY_LOCATORS
MTL_PARAMETERS
®
MTL_SYSTEM_ITEMS_B
MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the
definitions for inventory items, engineering items, and purchasing items. The
flexfield code is MSTK. The primary key for an item is the
INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could
be defined in more than one organization. Each row represents an item in an
organization.
MTL_SYSTEM_ITEMS_TL
MTL_SYSTEM_ITEMS_TL is a table holding translated Description column
for Items. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID,
LANGUAGE.
each accounting flexfield structure within your general ledger application. The
primary key is CODE_COMBINATION_ID.
MTL_SECONDARY_INVENTORIES is the definition table for the
subinventory. Subinventories are assigned to items, indicating a list of valid
places in which this item may be located. The primary key is
SECONDARY_INVENTORY_NAME, ORGANIZATION_ID.
MTL_ITEM_SUB_INVENTORIES

Chapter 7 - Page 15
MTL_ITEM_SUB_INVENTORIES maintains a listing of subinventories
assigned to an inventory or engineering item. The subinventories make up the
valid list of subinventories when transacting a specific item if the user has
specified that the item must use subinventories from a predefined list. The
primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID,
SECONDARY_INVENTORY
MTL_ITEM_LOCATIONS
MTL_ITEM_LOCATIONS is the definition table for stock locators. The
associated attributes describe the subinventory to which this locator belongs,
and the locator physical capacity. The primary key is
INVENTORY_LOCATION_ID, ORGANIZATION_ID.
MTL_SECONDARY_LOCATORS
MTL_SECONDARY_LOCATORS stores all locators within a subinventory for
a specific item. The locators make up the valid list of locators when transacting
that specific item to/from the subinventory when the user has specified that the
item must use locators from a predefined list. The primary key is
INVENTORY_ITEM_ID, ORGANIZATION_ID,
SECONDARY_LOCATORS.
MTL_PARAMETERS

Chapter 7 - Page 16
Defining Subinventories
Defining Subinventories
Subinventories are unique physical or logical

separations of material inventory, such as raw
inventory, finished goods, or defective material.
Subinventories
Subinventories Summary
Summary (M1)
(M1)
(N) Inventory > Setup > Organizations > Subinventories

Chapter 7 - Page 17
Defining Locators
Defining Locators
You use locators to identify physical areas where

you store inventory items. Item quantities can be
tracked by locator. Items can also be restricted to
specific locators.
Stock
Stock Locators
Locators (M1)
(M1)
(N) Inventory > Setup > Organizations > Stock Locators

Chapter 7 - Page 18
Oracle Inventory: Item Master
Oracle Inventory: Item Master
MTL_ITEM_ATTRIBUTES
MTL_SYSTEM_ITEMS_B
MTL_ITEM_TEMPL_ATTRIBUTES
MTL_ITEM_STATUS
MTL_ITEM_TEMPLATES
MTL_STATUS_ATTRIBUTE_VALUES
MTL_PARAMETERS
MTL_SYSTEM_ITEMS_B
organization.
MTL_ITEM_ATTRIBUTES
MTL_ITEM_ATTRIBUTES stores the item attributes, their user-friendly
names if the item is maintained at the item or item/organization level, and the
kind of validation required for each attribute. This table is seeded on install or
upgrade. The primary key is ATTRIBUTE_NAME.
MTL_ITEM_TEMPL_ATTRIBUTES
MTL_ITEM_TEMPL_ATTRIBUTES stores the attributes and attribute values
for a template. When a template is created, a row is inserted for each available
item attribute. When the template is applied to an item, the enabled attribute
values are propagated to the item. The primary key is TEMPLATE_ID,
ATTRIBUTE_NAME.
MTL_ITEM_STATUS
MTL_ITEM_STATUS is the definition table for a material status code. The
status code is a required item attribute and indicates the item status (for
example, active, pending, or obsolete). You may define as many additional
status codes as you want. The values of the individual status attributes

Chapter 7 - Page 19
associated with an item status are stored in
MTL_STATUS_ATTRIBUTE_VALUES. The primary key is
INVENTORY_ITEM_STATUS_CODE.
MTL_ITEM_TEMPLATES
MTL_ITEM_TEMPLATES is the definition table for item templates. It
contains the user-defined name and description. When the template is applied to
an item, the enabled item attributes are propagated to the item. The primary key
is TEMPLATE_ID.
MTL_STATUS_ATTRIBUTE_VALUES stores the attribute values associated
with an item status code. One record is created for each of the function-enabling
attributes for each defined item status code. The primary key is
INVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME.
MTL_PARAMETERS

Chapter 7 - Page 20
Defining Items
Defining Items
When you apply a template to an item, you

overlay or default in the set of attribute values to
the item definition. You can apply the same or
different templates to an item multiple times.
Item
Item Template
Template (M1)
(M1)
(N) Inventory > Setup > Items > Templates

Chapter 7 - Page 21
Degree of Item Control
Degree of Item Control
No control?
Credit card or
Supplier control?
petty cash
Item list
POs/suppliers
on-hand
no item #’s
Defined Defined
expense items stock items

Chapter 7 - Page 22
Oracle Inventory Item Controls
Oracle Inventory Item Controls
MTL_SYSTEM_ITEMS_B
MTL_LOT_NUMBERS MTL_SERIAL_NUMBERS MTL_ITEM_REVISIONS
MTL_SYSTEM_ITEMS_B
organization.
MTL_ITEM_REVISIONS
MTL_ITEM_REVISIONS stores revision levels for an inventory item. When an
item is defined, a starting revision record is written out to the table; every item
will have at least one revision. The primary key is INVENTORY_ITEM_ID,
ORGANIZATION_ID, REVISION.
MTL_SERIAL_NUMBERS
MTL_SERIAL_NUMBERS stores the definition and current status of all serial
numbers in Oracle Inventory. These serial numbers are also used in other areas
of Oracle Manufacturing applications.
A serial number can have one of four statuses:
• Defined, but not used
• Resides in stores
• Issued out of stores
• Resides in transit

Chapter 7 - Page 23
The primary key is INVENTORY_ID, SERIAL_NUMBER,
CURRENT_ORGANIZATION_ID.
MTL_LOT_NUMBERS
MTL_LOT_NUMBERS stores the definition and expiration date of all lot
numbers in inventory. A lot number can exist in more than one organization or
for different items. The primary key is INVENTORY_ITEM_ID,
ORGANIZATION_ID, LOT_NUMBER.

Chapter 7 - Page 24
Defining Item Controls
Defining Item Controls
You can choose between centralized and

decentralized control of item attributes. Defining
attribute controls does not determine the value of
an attribute, only the level at which it is
controlled.
Item
Item Attribute
Attribute Controls
Controls
(N) Inventory > Setup > Items > Attribute Controls

Chapter 7 - Page 25
Oracle Inventory Item Status
Oracle Inventory Item Status
MTL_PENDING_ITEM_STATUS
MTL_SYSTEM_ITEMS_B MTL_ITEM_STATUS
MTL_ITEM_ATTRIBUTES
MTL_SYSTEM_ITEMS_B
organization.
MTL_ITEM_ATTRIBUTES
MTL_ITEM_ATTRIBUTES stores the item attributes, their user-friendly
names if the attribute is maintained at the item or item/organization level, if the
attribute is controlled by an item’s status, and the kind of validation required for
each attribute. This table is seeded on install or upgrade. The top eight item
attributes are as follows:
1 Stockable
2 Transactable
3 BOM allowed
4 WIP allowed
5 Purchasable
6 OE Orderable
7 Internal Orderable
8 Billable
The primary key is ATTRIBUTE_NAME.

Chapter 7 - Page 26
MTL_STATUS_ATTRIBUTE_VALUES stores the attribute values associated
with an item status code. One record is created for each of the function-enabling
attributes for each defined item status code. The primary key is
INVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME.
MTL_ITEM_STATUS
MTL_ITEM_STATUS is the definition table for a material status code. The
status code is a required item attribute and indicates the item status (for
example, active, pending, or obsolete). You may define as many additional
status codes as you want. The values of the individual status attributes
associated with an item’s status are stored in
MTL_STATUS_ATTRIBUTE_VALUES. The primary key is
INVENTORY_ITEM_STATUS_CODE.
MTL_PENDING_ITEM_STATUS
MTL_PENDING_ITEM_STATUS is used to define and store the history of the
item statuses that have been or will be assigned to an item. This table maintains
the status history for each item. This table also stores pending status
information. The primary key is INVENTORY_ITEM_ID,
ORGANIZATION_ID, STATUS_CODE, EFFECTIVE_DATE.

Chapter 7 - Page 27
Life Cycle of a Part: Using Item Status and Attributes
Life Cycle of a Part:

Using Item Status and Attributes
Prototype Ramp Up Live Ramp Down Obsolete
1. Stock N Y Y Y N
2. Trans N Y Y Y N
3. BOM Y Y Y Y Y
4. WIP N Y Y N N
5. Pur N Y Y N N
6. OE N N Y Y N
7. Intern N N Y Y N
8. Bill N N Y Y N
Life Cycle of a Part

This graph depicts the usage of MTL_ITEM_STATUS and
MTL_ITEM_ATTRIBUTES to indicate the stages an item (or part) may go
through in its life cycle. For example: If a part is still in the prototype stage, it
will not be stockable (1 Stock) or there will be no transaction activity allowed
(2. Trans). However, it will be defined in the bill of material (3. BOM) in order
to build the prototype part originally. The remaining categories illustrate the
following:
5. Pur—part cannot be purchased
6. OE—part cannot be ordered
7. Intern—part cannot be ordered internally
8. Bill—part cannot be invoiced

Chapter 7 - Page 28
Defining Item Status Codes
Defining Item Status Codes
You can use statuses to provide default values for

certain item attributes to control the functionality
of an item. When you update the values for a
status, all items to which it is assigned are also
updated.
Item
Item Status
Status
(N) Inventory > Setup > Items > Status Codes

Chapter 7 - Page 29
Item Categories Example
Item Categories
Example
Category Set
Item Type Country of Origin Size

x1 steel U.S. big
x2 wire Canada medium
x3 steel Canada small
x4 office supplies U.S. big
Categories
Category Sets and Categories

There are an infinite number of categories for any item.

Chapter 7 - Page 30
Oracle Inventory: Item Categories
Oracle Inventory: Item Categories
MTL_ITEM_CATEGORIES MTL_SYSTEM_ITEMS_B
MTL_CATEGORY_
SET_VALID_CATS
MTL_CATEGORIES_B MTL_CATEGORY_
SETS_B
FND_ID_FLEX_
STRUCTURES
MTL_CATEGORIES_TL MTL_CATEGORY_SETS_TL
MTL_DEFAULT_
CATEGORY_SETS
®
MTL_SYSTEM_ITEMS_B
organization.
FND_ID_FLEX_STRUCTURES
FND_ID_FLEX_STRUCTURES stores structure information about key
flexfields. The primary key is APPLICATION_ID, ID_FLEX_CODE,
ID_FLEX_NUM.
MTL_CATEGORIES_B
MTL_CATEGORIES_B is the code combinations table for item categories.
Items are grouped into categories within the context of a category set to provide
flexible grouping schemes. The primary key is CATEGORY_ID.
The item category is a key flexfield with a flexfield code of MCAT.
MTL_CATEGORIES_TL
MTL_CATEGORIES_TL is a table holding translated Description column for
Item Categories. The primary key is CATEGORY_ID, LANGUAGE.
MTL_CATEGORY_SETS_B
MTL_CATEGORY_SETS_B contains the entity definition for category sets. A
category set is a categorization scheme for a group of items. Items can be

Chapter 7 - Page 31
assigned to different categories in different category sets, but can be assigned to
only one category within a category set. The primary key is
CATEGORY_SET_ID.
MTL_CATEGORY_SETS_TL
MTL_CATEGORY_SETS_TL is a table holding translated Name and
Description columns for Category Sets. The primary key is
CATEGORY_SET_ID, LANGUAGE.
MTL_CATEGORY_SET_VALID_CATS
MTL_CATEGORY_SET_VALID_CATS defines the valid category list for a
particular category set. If category validation is required, the list of valid
categories is stored in this table and is used to restrict category selection for the
category set. The primary key is CATEGORY_SET_ID, CATEGORY_ID.
MTL_DEFAULT_CATEGORY_SETS
MTL_DEFAULT_CATEGORY_SETS stores the identifier of the category set
that acts as the default for a particular functional area. This information is used
to determine the mandatory category sets for an item. It is also used to provide a
default category set for forms and reports that require a category set field value
or parameter. The primary key is FUNCTIONAL_AREA_ID,
CATEGORY_SET_ID.
MTL_ITEM_CATEGORIES
MTL_ITEM_CATEGORIES stores the item assignments to categories within a
category set. For each assignment, this table stores the item, category set, and
the category. Items can be assigned to multiple categories and category sets, but
can be assigned to only one category in a given category set.
This table is populated through either the Define Item or the Update Item/Org
Attributes forms. It can also be populated by performing item assignments when
a category set is defined. The primary key is INVENTORY_ITEM_ID,
ORGANIZATION_ID, CATEGORY_SET_ID.

Chapter 7 - Page 32
Defining Item Categories
Defining Item Categories
You can define an unlimited number of categories

and group subsets of your categories into
category sets. A category can belong to multiple
category sets.
Categories
(N) Inventory > Setup > Items > Categories > Category Codes

Chapter 7 - Page 33
Oracle Inventory: Item Catalogs
Oracle Inventory: Item Catalogs
MTL_SYSTEM_ITEMS_B
MTL_DESCR_ELEMENT_VALUES
MTL_DESCRIPTIVE_ELEMENTS
MTL_ITEM_CATALOG_GROUPS
MTL_ITEM_CATALOG_GROUPS
MTL_ITEM_CATALOG_GROUPS is the entity table for item catalog groups.
An item catalog group consists of items that can be described by the same set of
descriptive elements or item properties. The item catalog group assignment for
an item is done at the item master organization level.
The item catalog group is a key flexfield. The flexfield code is MICG. The
primary key is ITEM_CATALOG_GROUP_ID.
MTL_DESCRIPTIVE_ELEMENTS
MTL_DESCRIPTIVE_ELEMENTS stores the descriptive element definitions
for an item catalog group. Descriptive elements are defining properties used to
describe the catalog group. The primary key is
ITEM_CATALOG_GROUP_ID, ELEMENT_NAME.
MTL_DESCR_ELEMENT_VALUES
MTL_DESCR_ELEMENT_VALUES stores the descriptive element values for
a specific item. An item can only be assigned to one item catalog group and will
only have descriptive elements for a single catalog group. The primary key is
INVENTORY_ITEM_ID, ELEMENT_NAME.
MTL_SYSTEM_ITEMS_B

Chapter 7 - Page 34
organization.

Chapter 7 - Page 35
Defining Item Catalogs
Defining Item Catalogs

When you define descriptive elements for an item
catalog group, you specify whether the value of a
particular descriptive element can be
concatenated and used as an item's description.
When you assign an item to a catalog group, you
choose descriptive elements that apply to the
item, and assign values to the descriptive
elements.
Item
Item Catalog
CatalogGroups
Groups
(N) Inventory > Setup > Items > Catalog Groups

Chapter 7 - Page 36
Practice 1 Setup
Practice 1 Setup
1 Create seven items of the following variety:

– Planning Item (Quantity 1)
– Finished Goods (Quantity 2)
– Purchased Items (Quantity 4)
2 Verify items for the correct template and
organization assignment.
Setup Instructions
Create Seven Items
1. Navigate to the Master Item form.
(N) Inventory > Items > Master Items (note: select M1-Seattle Manufacturing as
your default)
• Name the item and fill in the description (note: item number is case
sensitive).
• Apply the Item Template for each item as shown in the example table
below.
[M]Tools > Copy From
• Select the correct template for each item from list of values, and Click the
Done button.
• Assign Unit of Measure as shown in the example table below.
• Select the Lead Time tab and enter 2 for processing lead time.
• Save your work.
[M]Tools > Organization Assignment
• Assign Item to the M1-Seattle Manufacturing organization.
• Save your work.
• Repeat step 1for the additional six items, substituting the appropriate
Template for each.
Example:

Chapter 7 - Page 37
Item Template Used UOM
##-salsa Planning Item Each
##-hot Finished Good Each
##-mild Finished Good Each
##-habanero Purchase Item Ounce
##-jalapeno Purchase Item Ounce
##-garlic Purchase Item Ounce
##-tomato Purchase Item Ounce
Verify Items for Correct Template and Organization Assignment
2. Navigate to the Find Organization Items form.
(N) Inventory > Items > Organization Items (Ensure you are in the M1
organization)
• Find your item numbers.
• Select the Bill of Material tab.
• Ensure each item has the BOM ALLOWED box checked.

Chapter 7 - Page 38
Practice 1
Practice 1
Find your items, their descriptions, and determine the

values of the eight Item Attributes that make up the
Item Status Code.
Instructions
• Tables: mtl_system_items, mtl_parameters
• Keys: segmentl, organization_code, organization_id
• Columns: purchasing_item_flag, internal_order_enabled_flag,
customer_order_enabled_flag, stock_enabled_flag, bom_enabled_flag,
build_in_wip_flag, mtl_transactions_enabled_flag, invoiceable_item_flag

Chapter 7 - Page 39
Practice 1 Solution
Practice 1 Solution
Find your items, their descriptions, and determine the

values of the eight Item Attributes that make up the
Item Status Code.
SQL Code Solution

SELECT
• substr(inv.segment1,1,15) “Item”,
• substr(inv.description,1,20) “Description”,
• inv.purchasing_item_flag,
• inv.customer_order_enabled_flag,
• inv.internal_order_enabled_flag,
• inv.stock_enabled_flag,
• inv.bom_enabled_flag,
• inv.build_in_wip_flag,
• inv.mtl_transactions_enabled_flag,
• inv.invoiceable_item_flag
FROM
• mtl_system_items inv,
• mtl_parameters org
WHERE
• inv.segment1 LIKE ‘&Item%’ AND
• org.organization_code LIKE ‘&OrgCode%’ AND
• org.organization_id = inv.organization_id

Chapter 7 - Page 40
Agenda
Agenda
• Item definition
• Open interfaces

Chapter 7 - Page 41
Oracle Inventory Transaction Flow
Oracle Inventory Transaction Flow
Inventory,
Order entry Receiving
WIP
RCV_
RCV
TRANSACTIONS_
processor
INTERFACE
MTL_ MTL_MATERIAL_ MTL_ MTL_

TRANSACTIONS_ TRANSACTIONS_ MATERIAL_ TRANSACTION_
INTERFACE TEMP TRANSACTIONS ACCOUNTS
TXN TXN Cost

processor worker processor
MTL_TRANSACTIONS_INTERFACE
This is the interface point between non-Inventory applications and the Inventory
transaction module.
The Transaction Manager concurrent program polls this table at a user-specified
process interval and submits the transaction workers to process them.
Processing consists of data derivation, validation, and transfer of records from
MTL_TRANSACTIONS_INTERFACE,
MTL_TRANSACTION_LOTS_INTERFACE, and
MTL_SERIAL_NUMBERS_INTERFACE into their respective TEMP tables,
from where they are processed by the transaction processor.
MTL_MATERIAL_TRANSACTIONS_TEMP
This table is the gateway for all material transactions. Records are processed
from this table into Inventory through the transaction processor. All Inventory
transaction forms write directly to this table. Outside applications must write
transaction records to MTL_TRANSACTSIONS_INTERFACE to be processed
through MTL_MATERIAL_TRANSACTIONS_TEMP and the transaction
processor by the Transaction Worker concurrent program.
MTL_MATERIAL_TRANSACTIONS
This table stores a record of every material transaction or cost update performed
in Inventory.
Records are inserted into this table either through the transaction processor or
by the standard cost program. The primary key is TRANSACTION_ID.
MTL_TRANSACTION_ACCOUNTS

Chapter 7 - Page 42
This table holds the accounting information for each material transaction in
MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information
to track the financial impact of your quantity moves.
Instructor Note
There is no primary key for this table in the TRM.

Chapter 7 - Page 43
Oracle Inventory: Inventory Transactions and Item
Controls
Oracle Inventory:
Inventory Transactions and Item Controls
MTL_SYSTEM_ITEMS_B
MTL_SERIAL_ MTL_LOT_NUMBERS
NUMBERS
MTL_ITEM_
REVISIONS
MTL_UNIT_ MTL_TRANSACTION_
TRANSACTIONS LOT_NUMBERS
®
MTL_UNIT_TRANSACTIONS
MTL_UNIT_TRANSACTIONS stores a record of every material transaction of
a serialized unit in Oracle Inventory. Records are inserted into this table through
the transaction processor. The primary key is TRANSACTION_ID,
SERIAL_NUMBER.
MTL_SERIAL_NUMBERS
MTL_SERIAL_NUMBERS stores the definition and current status of all serial
numbers in Oracle Inventory. These serial numbers are also used in other areas
of Oracle Manufacturing applications. The primary key is
INVENTORY_ITEM_ID, SERIAL_NUMBER,
CURRENT_ORGANIZATION_ID.
MTL_TRANSACTION_LOT_NUMBERS
MTL_TRANSACTION_LOT_NUMBERS stores lot number information for
transactions in the MTL_MATERIAL_TRANSACTIONS table. The primary
key is TRANSACTION_ID, LOT_NUMBER.
MTL_LOT_NUMBERS
MTL_LOT_NUMBERS stores the definition and expiration date of all lot
numbers in Oracle Inventory. The primary key is INVNETORY_ITEM_ID,
ORGANIZATION_ID, LOT_NUMBER.
MTL_ITEM_REVISIONS

Chapter 7 - Page 44
MTL_ITEM_REVISIONS stores the revision levels for an inventory item.
When an item is defined, a starting revision record is written to this table so that
every item has at least one revision. The primary key is
INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION.
MTL_SYSTEM_ITEMS_B
primary key for an item is the INVENTORY_ITEM_ID and the
ORGANIZATION_ID.

Chapter 7 - Page 45
Physical Inventory Process
Physical Inventory Process

Define physical inventory
Take snapshot of on-hand quantities
Generate tags
Count items
Void tags
Approve counts
Run adjustment program
Purge physical inventory
Define physical inventory

®
Overview of Physical Inventory

A physical inventory is a periodic reconciliation of system on-hand balances
with physical counts in inventory. You can perform a physical inventory
whenever you choose to verify the accuracy of your system on-quantities. This
count can be performed for the entire organization or for particular
subinventories within an organization.

Chapter 7 - Page 46
Oracle Inventory: Physical Inventory
Oracle Inventory: Physical Inventory

MTL_MATERIAL_
MTL_SYSTEM_ITEMS_B
TRANSACTIONS
MTL_PHYSICAL_
INVENTORIES
MTL_ MTL_PHYSICAL_
MTL_
PHYSICAL_ SUBINVENTORIES
PHYSICAL_
INVENTORY_
ADJUSTMENTS
TAGS
MTL_
SECONDARY_
INVENTORIES
MTL_PHYSICAL_SUBINVENTORIES
MTL_PHYSICAL_SUBINVENTORIES specifies which subinventories are
involved in a physical inventory when the physical inventory does not include
all subinventories. The primary key is ORGANIZATION_ID,
PHYSICAL_INVENTORY_ID, SUBINVENTORY.
subinventory. Subinventories are assigned to items, indicating a list of valid
places in which this item is located. The primary key is
SECONDARY_INVENTORY_NAME, ORGANIZATION_ID.
MTL_PHYSICAL_INVENTORY_TAGS
MTL_PHYSICAL_INVENTORY_TAGS stores information regarding physical
inventory tags, including tag number, SKU information, tag quantity, and a
pointer to the corresponding adjustment in
MTL_PHYSICAL_ADJUSTMENTS. A change to this table can require a
change to MTL_PHYSICAL_ADJUSTMENTS to ensure that the information
therein remains consistent with its tags. The primary key is TAG_ID.
MTL_PHYSICAL_ADJUSTMENTS
MTL_PHYSICAL_ADJUSTMENTS contains all information about the
adjustment transactions, including the size of the necessary adjustment, the
accounts to which the adjustment transaction was posted, and the approval
status of each transaction. The primary key is ADJUSTMENT_ID.

Chapter 7 - Page 47
MTL_MATERIAL_TRANSACTIONS stores a record of every material
transaction or cost update performed in Inventory. Records are inserted into this
table either through the transaction processor or by the standard cost update
program. The primary key is TRANSACTION_ID.
MTL_SYSTEM_ITEMS_B
ORGANIZATION_ID.

Chapter 7 - Page 48
Defining Physical Inventory
Defining Physical Inventory

You can define and maintain an unlimited number
of physical inventories in Oracle Inventory. A
physical inventory is identified by a unique name
you assign. You use this name to identify any
activity, such as adjustments, pertaining to this
physical inventory.
Define
Define Physical
Physical Inventory
Inventory (M1)
(M1)
(N) Inventory > Counting > Physical Inventory > Physical Inventories

Chapter 7 - Page 49
ABC Analysis Overview
ABC Analysis Overview
Computer Printer Mouse

Item A Item B Item C
Overview of ABC Analysis

ABC Analysis is a method of determining the relative value of items in your
inventory sites. An ABC Analysis involves ranking your items according to a
criterion and then grouping items into classes. ABC refers to the rankings you
assign your items as a result of this analysis, where A items are more valuable
than B items, and so on.

Chapter 7 - Page 50
Oracle Inventory: ABC Analysis
Oracle Inventory: ABC Analysis

MTL_SYSTEM_ITEMS_B MTL_SECONDARY INVENTORIES
MTL_ABC_COMPILES
MTL_ABC_ MTL_ABC_COMPILE_
ASSIGNMENTS HEADERS
MTL_ABC_
MTL_ABC_ MTL_ABC_ASSGN_ ASSIGNMENT_
CLASSES GROUP_CLASSES GROUPS
MTL_ABC_CLASSES
MTL_ABC_CLASSES contains information about ABC classes. Each row in
this table defines an ABC class. An ABC class is a category under which items
with similar metrics are put together. An ABC class can be used in more than
one ABC group, but only once within a given group. The primary key is
ABC_CLASS_ID.
MTL_ABC_ASSIGNMENT_GROUPS
MTL_ABC_ASSIGNMENT_GROUPS contains information for ABC groups.
Each row in this table defines an ABC group and is populated by the Define
ABC Group table. Oracle Inventory uses this information as the basis for ABC
class assignment and item assignment. The primary key is
ASSIGNMENT_GROUP_ID.
MTL_ABC_ASSGN_GROUP_CLASSES
MTL_ABC_ASSIGN_GROUP_CLASSES stores information about the ABC
classes assigned to an ABC group. An ABC class can be assigned to one or
more ABC groups, but can be used only once in each ABC group. The primary
key is ASSIGNMENT_GROUP_ID, ABC_CLASS_ID.
MTL_ABC_ASSIGNMENTS
MTL_ABC_ASSIGNMENTS holds assignments of inventory items to ABC
classes and ABC groups. Oracle Inventory uses this information to load the
cycle count process. The primary key is INVENTORY_ITEM_ID,
ASSIGNMENT_GROUP_ID, ABC_CLASS_ID.
MTL_ABC_COMPILE_HEADERS

Chapter 7 - Page 51
MTL_ABC_COMPILE_HEADERS contains information used for, and that
results from, an ABC compile or an ABC analysis. It holds user-specified
information, such as the current compile option and cost code chosen, the
results of an ABC analysis, the cumulative quantity, and the cumulative value.
Oracle Inventory uses this information during the ABC compile process to
determine the compile criterion and attributes used for the compile. The primary
key is COMPILE_ID.
MTL_ABC_COMPILES
MTL_ABC_COMPILES stores information about each item within an ABC
compiler. Each row includes an item's sequence number relative to other items
in the given compiler, based on the criteria defined in
MTL_ABC_COMPILE_HEADERS. The primary key is
INVENTORY_ITEM_ID, COMPILE_ID.
MTL_SYSTEM_ITEMS_B
ORGANIZATION_ID.

Chapter 7 - Page 52
Defining an ABC Compile
Defining an ABC Compile

You can define and compile an ABC analysis for
your entire organization or for a specific
subinventory within your organization.
ABC Compile (M1)
A 33
B 126
C 905
(N) Inventory > ABC Codes > ABC Compiles

Chapter 7 - Page 53
Cycle Count Overview
Cycle Count Overview

Day 1 of Cycle Count
High-Value Item to Count

Low-Value Item to Count


Cycle Counting
Cycle counting is the periodic counting of individual items throughout the year.
Count items of higher value more frequently than items of lower value. Perform
cycle counting instead of performing physical inventory. You can use both
techniques to verify the accuracy of on-hand quantities and values.

Chapter 7 - Page 54
Oracle Inventory: Cycle Count
Oracle Inventory: Cycle Count

MTL_CC_ MTL_
SCHED_COUNT SYSTEM_ITEMS_B
XREFS
MTL_CC_
SCHEDULE_
REQUESTS
MTL_CYCLE_
COUNT_ MTL_CYCLE_
ENTRIES COUNT_ITEMS
MTL_
MTL_CYCLE_ MTL_CYCLE_
MATERIAL_
COUNT_HEADERS COUNT_
TRANSACTIONS
CLASSES
MTL_SYSTEM_ITEMS_B
ORGANIZATION_ID.
MTL_CYCLE_COUNT_ITEMS
MTL_CYCLE_COUNT_ITEMS stores information about all items eligible for
cycle counting within the scope of a cycle count name. Oracle Inventory uses
this information to direct the cycle count scheduling process, and as a validation
table when entering manual schedule requests. The primary key is
CYCLE_COUNT_HEADER_ID, INVENTORY_ITEM_ID.
MTL_CYCLE_COUNT_CLASSES
MTL_CYCLE_COUNT_CLASSES stores information about cycle count
classes, such as associated cycle count name, approval tolerance limits, and
minimum counting frequency. Oracle Inventory uses Cycle Count Classes as a
unit for specifying and defaulting cycle count attributes. The primary key is
ABC_CLASS_ID, CYCLE_COUNT_HEADER_ID.
MTL_CYCLE_COUNT_HEADERS
MTL_CYCLE_COUNT_HEADERS stores information about cycle count
names. Oracle Inventory uses this information to track defined cycle count
names, to indicate tolerance/approval limits, cycle count calendar and exception
set, ABC initialization information, scheduling options, and recount options.
The primary key is CYCLE_COUNT_HEADER_ID.

Chapter 7 - Page 55
MTL_CC_SCHEDULE_REQUESTS
MTL_CC_SCHEDULE_REQUESTS stores cycle count schedule requests.
Oracle Inventory uses this information to feed the count generation process and
generate Cycle Count Requests that show up in the Count List Reports. The
primary key is CYCLE_COUNT_SCHEDULE_ID.
MTL_CC_SCHED_COUNT_XREFS
MTL_CC_SCHED_COUNT_XREFS links cycle counts entered to the schedule
request that generated it. Oracle Inventory uses this information to determine
when a schedule request has been completed and to update its status. The
primary key is CYCLE_COUNT_SCHEDULE_ID,
CYCLE_COUNT_ENTRY_ID.
MTL_CYCLE_COUNT_ENTRIES
MTL_CYCLE_COUNT_ENTRIES stores the actual counts of a cycle count. A
row in this table without a count is considered to be a count request. Oracle
Inventory uses this information to determine and store cycle count adjustments,
recounts, and approval requirements. The primary key is
CYCLE_COUNT_ENTRY_ID.
transaction or cost update performed in Inventory. Records are inserted into this
table either through the transaction processor or by the standard cost update
program. The primary key is TRANSACTION_ID.

Chapter 7 - Page 56
Oracle Inventory: Demand and Reservation Information
Oracle Inventory:
Demand and Reservation Information
MTL_SYSTEM_ITEMS_B
OE_ORDER_HEADERS_ALL
OE_ORDER_LINES_ALL
MTL_SALES_ORDERS
MTL_
GL_CODE_COMBINATIONS DEMAND_
MTL_ INTERFACE
MATERIAL_
TRANSACTIONS MTL_GENERIC_
DISPOSITIONS
MTL_DEMAND
MTL_DEMAND
MTL_DEMAND stores demand and reservation information used in Available
to Promise, Planning, and other manufacturing functions. Four row types are
stored in this table:
• Summary Demand rows
• Dependent Demand rows
• Open Demand rows
• Reservation rows
The primary key is INVENTORY_ITEM_ID, DEMAND_SOURCE_TYPE,
DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE (o),
DEMAND_SOURCE_DELIVERY (o), COMPONENT_SEQUENCE_ID (o).
MTL_SALES_ORDERS
MTL_SALES_ORDERS stores the Oracle Inventory local definition of sales
orders and maps sales orders between Oracle Inventory and other Oracle
Manufacturing applications. The primary key is SALES_ORDER_ID.
OE_ORDER_HEADERS_ALL
OE_ORDER_HEADERS_ALL stores header information for orders in Oracle
Order Management. The primary key is HEADER_ID.
OE-ORDER_LINES_ALL
OE_ORDER_LINES_ALL stores information for all order lines in Oracle
Order Management. The primary key is LINE-ID.

Chapter 7 - Page 57
each accounting flexfield structure within your general ledger application.
Available material can be reserved against a valid Accounting Flexfield
combination. The primary key is CODE_COMBINATION_ID.
MTL_GENERIC_DISPOSITIONS
MTL_GENERIC_DISPOSITIONS stores the user-defined account alias. An
account alias provides a method to use accounting numbers and makes it easier
to transact account issues and receipts. Available inventory can be reserved
against an account alias. The primary key is DISPOSITION_ID,
ORGANIZATION_ID.
transaction or cost update performed in Inventory. An issue transaction to an
account number or account alias can relieve a reservation against the account
number or alias. The primary key is TRANSACTION_ID.
MTL_DEMAND_INTERFACE
MTL_DEMAND_INTERFACE is the interface point between non-Inventory
applications and the Oracle Inventory demand module. Records inserted into
this table are processed by the Demand Manager concurrent program.
MTL_SYSTEM_ITEMS_B
ORGANIZATION_ID.

Chapter 7 - Page 58
Practice 2 Setup
Practice 2 Setup
1 Create several miscellaneous transactions for your

items.
2 Determine your on-hand quantities per
subinventory.
Setup Instructions
Create Miscellaneous Transactions
1. Navigate to the Miscellaneous Transaction form.
(N) Inventory > Transactions > Miscellaneous Transaction
• Select Miscellaneous Receipts from the list of values in the Type field.
• Click Transaction Lines.
• Enter your item numbers for your Purchased items (NOT Planning or
Fnished Good items).
• Select a subinventory (Stores, RIP or Floor Stock) and reasonable quantity
for each item.
• In the Account field, enter “%”, press the tab key and select an account
number.
• Save your work.
Determine On-hand Quantities
2. Navigate to the Find On-hand Quantities form.
(N) Inventory > On-hand, Availability > On-hand Quantity
• Enter each item number you received and verify the on-hand quantity.

Chapter 7 - Page 59
Practice 2
Practice 2
Determine your items’ on-hand quantities from the

tables.
Instructions
• Tables: mtl_system_items, mtl_onhand_quantities, mtl_parameters
• Keys: segmentl, organization_code, organization_id, inventory_item_id
• Columns: inventory_item_id, organization_id, subinventory_code, revision,
locator_id, transaction_quantity

Chapter 7 - Page 60
Practice 2 Solution
Practice 2 Solution
Determine your items’ on-hand quantities from the

tables.
SQL Code Solution

SELECT
• substr(inv.segment1,1,15) “Item Number”,
• substr(onh.inventory_item_id,1,10) “Item ID”,
• substr(onh.organization_id,1,6) “Org ID”,
• substr(onh.subinventory_code,1,10) “SubInv”,
• substr(onh.revision,1,5) “Rev”,
• substr(onh.locator_id,1,8) “Locator”,
• substr(onh.transaction_quantity,1,15) “Trans Quant”
FROM
• mtl_system_items inv,
• mtl_onhand_quantities onh,
• mtl_parameters org
WHERE
• org.organization_code LIKE ‘&OrgCode%’ AND
• org.organization_id = inv.organization_id AND
• inv.inventory_item_id = onh.inventory_item_id AND
• inv.organization_id = onh.organization_id

Chapter 7 - Page 61
Agenda
Agenda
• Item definition
• Open interfaces

Chapter 7 - Page 62
Oracle Applications Open Interfaces for Inventory
Oracle Applications
Open Interfaces for Inventory
• Open Transaction Interface

• Open Demand Interface
• Open Replenishment Interface
• Open Item Interface
• Customer Item Interface
Oracle Inventory
Open Transaction Interface
This interface is used as an integration point with Oracle Order Management for
shipment transactions. Oracle Order Management uses the Inventory interface
program to populate the interface tables with transactions submitted through the
Confirm Shipments window.
Open Demand Interface
This interface program provides all the functions you need to interface an
external order entry system with Oracle Inventory and Oracle Manufacturing
applications.
Open Replenishment Interface
This allows you to load replenishment requests from external systems, such as a
bar-code application. Such requests may be in the form of stock-take counts or
requisition requests for subinventories in which you do not track quantities.
Open Item Interface
You can import items from any source into Oracle Inventory and Oracle
Engineering using this interface
Customer Item Interface
You can import customer items and customer item cross-references into Oracle
Inventory to achieve faster order processing and shipments.

Chapter 7 - Page 63
Major Tables: Open Interfaces
Major Tables:
Open Interfaces
• Transactions
• Demand Interface
• Replenishment
Transactions
You can load transactions from external applications and feeder systems using
this interface. These transactions could include sales order shipment
transactions from an external order entry system, or they could be simple
material issues, receipts, or transfers that are loaded from data collection
devices.
This is also used as an integration point with Oracle Order Management for
shipment transactions. The Oracle Order Management Inventory Interface
program populates the interface tables with transactions submitted through the
Ship Confirm window.
Open Demand Interface
This is a two-way interface that lets you have visibility as well as reserve
demand that is created in external applications for forecasting, planning, and
order-promising purposes. This includes the option to automatically check ATP
when adding demand to verify availability.
Open Replenishment Interface
Using this interface, you can load replenishment requests from external systems
such as a bar-code application. Such requests may be in the form of stock-take
counts or requisition requests for subinventories in which you do not track
quantities.

Chapter 7 - Page 64
Inventory Transactions Open Interface Tables
Inventory Transactions
Open Interface Tables
Interface Data Flow Table, Table, View, or Module name
Name Direction View, or
Process
Transactions Inbound Table MTL_TRANSACTIONS_INTERFACE
MTL_SERIAL_NUMBERS_INTERFACE
MTL_TRANSACION_LOTS_INTERFACE
Demand Inbound Table MTL_DEMAND_INTERFACE
Interface
Replenishment Inbound Table MTL_REPLENISH_HEADERS_INT
MTL_REPLENISH_LINES_INT

Chapter 7 - Page 65
Open Interfaces: Inventory Setups
Open Interfaces: Inventory Setups
• Open Item Interface

• Customer Item and Customer Item Cross-Reference
Open Interface
Open Item Interface

You can import items from any source into Oracle Inventory and Oracle
Engineering using the Item Interface. This will convert inventory items from
another inventory system, migrate assembly and component items from a legacy
manufacturing system, convert purchase items from a custom purchasing
system, and import new items from a Product Data Management package.
Customer Item and Customer Item Cross-Reference Open Interface
Today’s manufacturing environment requires a close working relationship
between customers and suppliers. Suppliers must be able to react quickly to
their customer’s often-changing requirements. By cross-referencing your own
inventory items with your suppliers, you can achieve faster order processing and
shipments by placing orders using their internal item numbers.
You can import customer items and customer item cross-references from any
legacy system into Oracle Inventory using this interface. The interface process
will ensure that the imported customer items and cross-references contain the
same detail as the items entered manually using the Customer Items and
Customer Item Cross- References windows.

Chapter 7 - Page 66
Inventory Setups Open Interface Tables
Inventory Setups Open Interface Tables
Interface Data Flow Table, View,

Table, View, or Module Name
Name Direction or Process
MTL_SYSTEM_ITEMS_INTERFACE
Item Inbound Table
MTL_ITEMS_REVISIONS_INTERFACE
Customer Item Inbound Table MTL_CI_INTERFACE
Customer Item
Inbound Table MTL_CI_XREFS_INTERFACE
Cross-Reference

Chapter 7 - Page 67
Summary
Summary
In this lesson, you have learned how to relate the

major tables to inventory item definition,
transactions, and open interfaces.
• Organizations
• Subinventories and locators
• Item master
• Item controls
• Item status
• Item category
• Item catalog
• ABC class
• Interface tables
®

Chapter 7 - Page 68
Foundation: Purchasing
Chapter 8
11i Manufacturing Functional Foundation: Purchasing

Chapter 8 - Page 1

Purchasing

Chapter 8 - Page 2
Objectives
Objectives

do the following:
• Discuss purchasing activity from requisition to
receipt of goods
• Identify the major tables used in purchasing and
receiving
• Run a query in SQL*Plus against the appropriate
database tables to review a purchase order and
receipt for a given item
• Discuss the open interfaces for purchasing
Lesson Aim
The aim of this lesson is to provide the student an overview of the flow of
purchasing activity from the requisition stage to the receipt stage and discuss the
database tables that are populated as a result of these activities.
Instructor Note
associated with it.

Chapter 8 - Page 3
Agenda
Agenda
• Overview
• Entity Relationship Diagrams (ERDs)
• Open interfaces

Chapter 8 - Page 4
Agenda
Agenda
• Overview
• Open interfaces

Chapter 8 - Page 5
Oracle Purchasing Overview
Oracle Purchasing Overview
ve
Manually ppro
A
create AutoCreate
PO
Requisition
pool
Maintain documents
Accept Revise Control
Receive against PO Match invoices in Payables

®
Description
Oracle Purchasing is a comprehensive procurement solution, designed to reduce
administration costs while focusing on value analysis, strategic supply base
management, and contract negotiation.
Requisitioning
• Replace paper processing with online requisition generation, purchase order
creation, and document approval.
• Regulate document access, control or modification activity, and approval
based on organizational signature and security policies.
• Minimize data entry time with time-saving templates, express processing
functions, and default infrastructures.
Purchasing
• Control purchasing activity and enable accurate automatic pricing using an
approved supplier list.
• Consolidate purchase requirements from multiple warehouses, plants, or
locations.
Receiving
Receive production items, Maintenance, Receipt and Overhead (MRO) items,
and services using a common flexible receiving process.
Business Communication
• Facilitate communication between requesters, buyers, receiving staff, and
accounts payable staff using online inquiries and notes.

Chapter 8 - Page 6
• Provide access to purchasing information to related functions (marketing,
finance, legal, master scheduling, inventory management, production, cost
accounting, or customer order entry) on an optional basis.
• Manage historical data.

Chapter 8 - Page 7
Purchasing Process Flow
Purchasing Process Flow
Requisition
RFQ
Quote
Blanket
Contract PO
PO
Standard Blanket PO
PO Release
Purchasing Overview
A requisition is generated either manually or by the system, which is ultimately
turned into a purchase order by the buyer. Sometimes the buyer decides a
Request for Quotation (RFQ) is required by other suppliers to determine the
best price for the goods or services requested. Once the quote is received back,
that information is used to finalize the purchase order.

Chapter 8 - Page 8
Agenda
Agenda
• Overview
• Open interfaces

Chapter 8 - Page 9
Oracle Purchasing: Entity Relationships
Oracle Purchasing: Entity Relationships
PO -VENDORS RCV_SHIPMENT_HEADERS
PO _VENDOR_SITE S_ALL
RCV_SHIPMENT_LINE S
PO _HE ADERS_ ALL
RCV_TRANSACTIONS
PO _LINES_ALL
PO_VENDORS
This table stores information about your suppliers. Oracle Purchasing uses this
information to determine active suppliers. The primary key is VENDOR_ID.
RCV_SHIPMENT_HEADERS
This table stores common information about the source of your receipts or
expected receipts. You group your receipts by the source type and the source of
the receipt. Oracle Purchasing does not allow you to group receipts from
different sources under one receipt header. The primary key is
SHIPMENT_HEADER_ID.
PO_VENDOR_SITES_ALL
This table stores information about supplier sites. Oracle Purchasing uses this
information to store supplier address information. The primary key is
VENDOR_SITE_ID.
RCV_SHIPMENT_LINES
This table stores information about items that have been shipped or received
from a specific receipt source. This table also stores information about the
default destination for in-transit shipments. The primary key is
SHIPMENT_LINE_ID.
PO_HEADERS_ALL
PO_HEADERS_ALL contains information for your purchasing documents.
Each row contains buyer information, supplier information, notes, foreign
currency information, terms and conditions information, and the document

Chapter 8 - Page 10
status. Oracle Purchasing uses this information to record information related to
a complete document. The primary key is PO-HEADER_ID.
RCV_TRANSACTIONS
This table stores historical information about receiving transactions that you
have performed. When you enter a receiving transaction and the receiving
transaction processor processes your transaction, the transaction is recorded in
this table.
Once a row has been inserted into this table, it will never be updated. When you
correct a transaction, the net transaction quantity is maintained in
RCV_SUPPLY. The original transaction does not get updated. You can only
delete rows from this table using the Purge feature of Oracle Purchasing. The
primary key is TRANSACTION_ID.
PO_LINES_ALL
PO_LINES_ALL stores current information about each purchase order line.
You need one row for each line you attach to a document. Each row includes
the line number, item number and category unit, price, tax information, and
quantity ordered for the line. Oracle Purchasing uses this information to record
and update item and price information for purchase orders, quotations, and
RFQs. The primary key is PO_LINE_ID.

Chapter 8 - Page 11
Suppliers
Suppliers
PO _VENDORS HR_EMPLOYEES
PO _VENDOR_SITE S_ALL
PO _VENDOR_CONTACTS
PO_VENDORS
This table stores information about your suppliers. Oracle Purchasing uses this
information to determine active suppliers. The primary key is VENDOR_ID.
HR_EMPLOYEES
HR_EMPLOYEES is a view that contains information about employees. You
must have a row for each requestor, requisition preparer, approver, buyer, or
receiver who uses Oracle Purchasing. The primary key is EMPLOYEE_ID (o).
PO_VENDOR_SITES_ALL
This table stores information about supplier sites. Oracle Purchasing uses this
information to store supplier address information. The primary key is
VENDOR_SITE_ID.
PO_VENDOR_CONTACTS
This table stores information about supplier site contacts. The primary key is
VENDOR_CONTACT_ID.

Chapter 8 - Page 12
Suppliers Window
Suppliers Window
You can set up suppliers in the Suppliers

window to record information about individuals
and companies from whom you purchase
goods and services.
Suppliers
Suppliers (Vision
(Vision Operations)
Operations)
(N) Purchasing > Supply Base > Suppliers

Chapter 8 - Page 13
Oracle Purchasing: Requisitions
Oracle Purchasing: Requisitions
PO _RE QUIS ITIO N_ HE ADERS_ALL HR_EMPLOYEE S
PO _RE QUIS ITIO N_ LINES_ALL MTL_S YSTEM_ITEMS_ B
PO _REQ_DISTRIBUTIO NS _ALL GL_CODE_COMBINATIONS
PO_REQUISITION_HEADERS_ALL
PO_REQUISITION_HEADERS_ALL stores information about requisition
headers. Each row contains the requisition number, preparer status, and
description. It is one of three tables that stores requisition information. The
primary key is REQUISITION_HEADER_ID.
HR_EMPLOYEES
HR_EMPLOYEES is a view that contains information about employees. You
must have a row for each requestor, requisition preparer, approver, buyer, or
receiver who uses Oracle Purchasing. The primary key is EMPLOYEE_ID (o).
PO_REQUISITION_LINES_ALL
This table stores information about requisition lines. Each row contains the line
number, item number, item category, item description, need-by date, deliver-to
location, item quantities, units, prices, requestor, notes, and suggested supplier
information for the requisition line. This table is one of three tables that stores
requisition information. The primary key is REQUISITION_LINE_ID.
MTL_SYSTEM_ITEMS_B
primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID.
PO_REQ_DISTRIBUTIONS_ALL
PO_REQ_DISTRIBUTIONS_ALL stores information about the accounting
distributions associated with each requisition line. Each requisition line must
have at least one accounting distribution. Each row includes the Accounting

Chapter 8 - Page 14
Flexfield ID and requisition line quantity. This table is one of three tables that
stores requisition information. The primary key is DISTRIBUTION_ID.
each accounting flexfield structure within your general ledger application.
GL_CODE_COMBINATIONS is populated by the system when a new
accounting flexfield combination is used, either through dynamic insertion or
manually.
This table references the CODE_COMBINATION_ID, which is the foreign key
used throughout Oracle Applications when tracking an accounting flexfield
combination. The primary key is CODE_COMBINATION_ID.

Chapter 8 - Page 15
Requisitions Window
Requisitions Window
With on-line requisitions, you can centralize your

purchasing department, source your requisitions
with the best suppliers, and ensure that you
obtain the appropriate management approval
before creating purchase orders from requisitions.
Requisitions (Vision Operations)
req uisitio
n
(N) Purchasing > Requisitions > Requisitions

Chapter 8 - Page 16
Purchasing Documents
Purchasing Documents
• Standard purchase orders

• Contract purchase orders
• Blanket purchase orders
• Planned purchase orders
Purchasing Documents Overview

Standard Purchase Orders
You generally create standard purchase orders for one-time purchase of various
items. You create standard purchase orders when you know the details of the
goods or services you require. Each standard purchase order line can have
multiple shipments, and you can distribute the quantity of each shipment across
multiple accounts.
Contract Purchase Orders
A contract purchase agreement is an agreement between you and a supplier for
unspecified goods or services. This agreement may include terms and
conditions, committed amount, and effective and expiration dates.
Blanket Purchase Orders
With blanket purchase agreements and releases, you can negotiate a stable,
long-term contract while maintaining flexible delivery schedules and order
quantity commitments. You create blanket purchase agreements when you
know the details of the goods or services you plan to buy from a specific
supplier in a period, but you do not yet know the detail of your delivery
schedules.
Planned Purchase Orders
You create a planned purchase order when you want to establish a long-term
agreement with a single supplier to buy goods or services. Planned purchase
orders include tentative delivery schedules and accounting distributions. You

Chapter 8 - Page 17
schedule releases against the planned purchase order to actually order the goods
or services.

Chapter 8 - Page 18
Oracle Purchasing: Purchasing Documents
Oracle Purchasing: Purchasing Documents
PO _HE ADERS_ ALL
PO _
PO _LINES_ALL RELEASES_ ALL
PO _LINE_LOCATIONS_ALL
PO _DISTRIBUTIONS_ALL
®
PO_HEADERS_ALL
PO_HEADERS_ALL contains information for your purchasing documents.
Each row contains buyer information, supplier information, notes, foreign
currency information, terms and conditions information, and the document
status. Oracle Purchasing uses this information to record information related to
a complete document. The primary key is PO-HEADER_ID.
PO_LINES_ALL
PO_LINES_ALL stores current information about each purchase order line.
You need one row for each line you attach to a document. Each row includes
the line number, item number and category unit, price, tax information, and
quantity ordered for the line. Oracle Purchasing uses this information to record
and update item and price information for purchase orders, quotations, and
RFQs. The primary key is PO_LINE_ID.
PO_LINE_LOCATIONS_ALL
This table contains information about purchase order shipment schedules and
blanket agreement price breaks. You must have one row for each schedule or
price break you attach to a document line. Each row contains the location,
quantity, and dates for each shipment schedule. Oracle Purchasing uses this
information to record delivery schedule information for purchase orders and
price break information for blanket purchase orders, quotations, and RFQs. The
primary key is LINE_LOCATION_ID.
PO_DISTRIBUTIONS_ALL

Chapter 8 - Page 19
PO_DISTRIBUTIONS_ALL contains accounting information for a purchase
order shipment line. Oracle Purchasing uses this information to record
accounting and requisition information for purchase orders and releases. It is
one of five tables that stores purchase orders and releases. The primary key is
PO_DISTRIBUTION_ID.
PO_RELEASES_ALL
This table contains information about blanket and planned purchase order
releases. You need one row for each release you issue for a blanket or planned
purchase order. Each row includes the buyer, date, release status, and release
number. Each release must have at least one purchase order shipment
(PO_LINE_LOCATIONS_ALL). The primary key is PO_RELEASE_ID.

Chapter 8 - Page 20
Purchase Orders Window
Purchase Orders Window
Purchasing provides the Purchase Orders window

that you can use to enter Standard and Planned
purchase orders as well as to enter Blanket and
Contract purchase agreements.
Purchase Orders (Vision Operations)
e
pu rcha s
ord e r
(N) Purchasing > Purchase Orders > Purchase Orders

Chapter 8 - Page 21
Receiving
Receiving
RCV_SHIPMENT_
HEADERS
PO _LINE_ RCV_SHIPMENT_ MTL_S YSTEM_

LOCATIONS_ALL LINES ITE MS_B
PO _ RCV_ MTL_MATERIAL_
DIS TRIBUTIO NS_ALL TRANSACTIONS TRANSACTIONS
RCV_SUPPLY
RCV_SHIPMENT_HEADERS
This table stores common information about the source of your receipts or
expected receipts. You group your receipts by the source type and the source of
the receipt. Oracle Purchasing does not allow you to group receipts from
different sources under one receipt header. The primary key is
SHIPMENT_HEADER_ID.
RCV_SHIPMENT_LINES
This table stores information about items that have been shipped or received
from a specific receipt source. It also stores information about the default
destination for in-transit shipments. The primary key is SHIPMENT_LINE_ID.
PO_LINE_LOCATIONS_ALL
This table contains information about purchase order shipment schedules and
blanket agreement price breaks. You must have one row for each schedule or
price break you attach to a document line. Each row contains the location,
quantity, and dates for each shipment schedule. Oracle Purchasing uses this
information to record delivery schedule information for purchase orders, and
price break information for blanket purchase orders, quotations, and RFQs. The
primary key is LINE_LOCATION_ID.
RCV_TRANSACTIONS
This table stores historical information about receiving transactions you have
performed. Once a row is inserted into this table, it will never be updated. When
you correct a transaction, the net transaction quantity is maintained in
RCV_SUPPLY. The original transaction quantity is not updated. You can delete

Chapter 8 - Page 22
rows from this table using the purge feature of Oracle Purchasing. The primary
code is TRANSACTION_ID.
transaction or cost update performed in Oracle Inventory. Records are inserted
into this table either through the transaction processor or by the standard cost
update program. The primary key is TRANSACTION_ID.
MTL_SYSTEM_ITEMS_B
PO_DISTRIBUTIONS_ALL
PO_DISTRIBUTIONS_ALL contains accounting information for a purchase
order shipment line. Oracle Purchasing uses this information to record
accounting and requisition information for purchase orders and releases. It is
one of five tables that stores purchase orders and releases. The primary key is
PO_DISTRIBUTION_ID.
RCV_SUPPLY
This table stores information about on-hand quantities in receiving and
inspection. Oracle Purchasing uses the table to track item, quantity, location and
source information for each receiving transaction. The primary key is
SUPPLY_TYPE_CODE, SUPPLY_SOURCE_ID.

Chapter 8 - Page 23
Receiving Transactions
Receiving Transactions
One of the many receiving transactions is the
receipt. With the receipt you can display the
supplier shipments and inter-organization
shipments corresponding to your search criteria.
You can receive goods into a receiving location or
to their final destination.
Receipts (M1)
(N) Purchasing > Receiving > Receipts

Chapter 8 - Page 24
Practice 1 Setup
Practice 1 Setup
1 Find your item purchase requisitions from the

planned orders you released from the Planner’s
Workbench.
2 Create a manual requisition if you do not find any
requisitions in the summary form.
3 Create a purchase order from one of the
requisitions.
Setup Instructions
1 Navigate to the Requisition Summary Window
(N) Purchasing > Requisitions > Requisitions Summary
– Enter the item number in the “Item, Rev” field for one of your released
orders
– Note the requisition number, go to step 3
– If you do not find your requisition, go to step 2
2 Create a manual requisition
(N) Purchasing > Requisitions > Requisitions
– Click in the Item field and enter one of your purchased item numbers,
Click the tab key
– Scroll or tab horizontally to fill in the Quantity, Price (less than $10.00)
and Need-By date (use LOV) fields
– Save your work
– Click the Approve button
– Click OK to Submit for Approval
– Click the OK button after the submitted window appears
– Repeat step 1 above
3 Create a purchase order
(N) > Purchasing > Autocreate

Chapter 8 - Page 25
– Clear the form with the Clear button (if a field remains, click in it and
select the blank to clear it)
– Search for your requisition by requisition number “Ctrl-Click” the line
you wish to create (it will highlight blue/green)
– Click the Automatic button
– In the New Document form, select Advantage Corp from the LOV
– If the Supplier Site field is blank, select the US site from the LOV
– Click the Create button
– Record your document number (the PO number) from the dialog box
that appears, then click OK
– If a window for new search criteria opens, click OK
– In the AutoCreate PO form, Click the “Approv…” button (if additional
information is needed, use LOV in that field to select it)
– In the Approve Document form, Click “OK” (this will take a little while
so take a short stretch break)

Chapter 8 - Page 26
Practice 1
Practice 1
For each purchase order line, find the quantity of the

items that you ordered.
Instructions
• Tables: po_lines_all, po_line_locations_all, mtl_system_items_b
• Keys: segment1, organization_id, item_id, po_line_id, inventory_item_id
• Columns: segment1, item_description, quantity

Chapter 8 - Page 27
Practice 1 Solution
Practice 1 Solution
For each purchase order line, find the quantity of the

items that you ordered.
SQL Code Solution

SELECT
• substr(po.item_description,1,30) “Description”,
• substr(ln.quantity,1,10) “Quantity”
FROM
• po_lines_all po,
• po_line_locations_all ln,
• mtl_system_items_b inv
WHERE
• inv.organization_id = 207 AND
• po.item_id = inv.inventory_item_id AND
• ln.po_line_id = po.po_line_id

Chapter 8 - Page 28
Agenda
Agenda
• Overview
• Open interfaces

Chapter 8 - Page 29
Purchasing Open Interfaces
Purchasing Open Interfaces
• Open Requisitions Interface

• Purchasing Documents Open Interface
• Receiving Open Interface
Oracle Purchasing
Open Requisitions Interface
You can automatically import requisitions from other Oracle applications or
other systems using this interface. This allows you to integrate your Oracle
Purchasing application with new or existing applications, such as material
requirements planning, inventory management, and production control systems.
Your Oracle Purchasing application automatically validates your data and
imports your requisitions. You can import requisitions as often as you want.
Then, you can review these requisitions, approve or reserve funds for them if
necessary, and place them on purchase orders or internal sales orders.
Purchasing Documents Open Interface
You can automatically import and update standard purchase orders, price/sales
catalog information, and responses to request for quotations (RFQs) from
suppliers through this interface. The Purchasing Documents Open Interface uses
the Applications Program Interfaces (APIs) to process document data in the
Oracle Applications interface table to ensure that it is valid before importing it
into Oracle Purchasing. After the data is validated, the program converts the
information in the interface table into the into the appropriate document in
Purchasing.
Receiving Open Interface
You can automatically import receipt information from other Oracle
applications or other systems using the Receiving Open Interface. This interface
lets you integrate your Oracle Purchasing application with new or existing

Chapter 8 - Page 30
applications. For example, you can load bar-coded and other receiving
information from scanners and radio frequency devices, and the Receiving
Open Interface validates the integrity of the new data before updating
Purchasing and Inventory. Advance shipment notices sent from suppliers are
also validated in the Receiving Open Interface.

Chapter 8 - Page 31
Purchasing Open Interface Tables
Purchasing Open Interface Tables

Process
Requisitions Inbound Table PO_REQUISITIONS_INTERFACE_ALL
PO_REQ_DIST_INTERFACE_ALL
Purchasing Inbound Table PO_HEADERS_INTERFACE
Documents PO_LINES_INTERFACE
Receiving Inbound Table RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE

Chapter 8 - Page 32
Summary
Summary

major tables to purchasing and receiving
transactions:
• Suppliers
• Requisitions
• Purchasing documents
• Delivery and receipt
• Open interfaces

Chapter 8 - Page 33

Chapter 8 - Page 34
Foundation: BOM and
Engineering
Chapter 9
11i Manufacturing Functional Foundation: BOM and Engineering

Chapter 9 - Page 1
11i Manufacturing Functional Foundation: BOM and
Engineering

BOM and Engineering

Chapter 9 - Page 2
Objectives
Objectives

do the following:
• Discuss bill of material/engineering setup definition
activities
• Identify the major tables used in a BOM definition
database tables to find a particular bill of material
and its routing
Lesson Aim
The aim of this lesson is to provide the student an overview of the setup
definition process in Oracle Engineering and Bills of Material and discuss the
database tables that are populated as a result of the setup activity.
Instructor Note
associated with it.

Chapter 9 - Page 3
Agenda
Agenda
• Oracle Bills of Material

• Oracle Engineering
• Open interfaces

Chapter 9 - Page 4
Agenda
Agenda

• Open interfaces

Chapter 9 - Page 5
• The Oracle engineering products are

Oracle Bills of Material and Oracle
Engineering.
• You use Oracle Bills of Material to:
– Create and maintain production bills of
materials
– Create and maintain production
resources, departments, routings, and
lead times
– Perform mass changes
– Delete product information
– Maintain the workday calendar
®
Description
Oracle Bills of Material develops and maintains manufacturing bills of material
(BOMs) and routings to drive planning, costing, and work-in-process tracking.
Routings
• Specify department and resources usage.
• Define shop floor controls.
• Maintain multiple revisions of routings.
• Define dynamic, lot based flow routing for operation flexibility.
Bills of Material
• Define component usage, yield, and material control.
• Integrate with routings for point-of-use definition.
• Maintain multiple revisions of bills of material.
Lead Time
Calculate manufacturing lead time to produce goods from routing standards.
Standard Cost
Calculate standard costs from bills of material and routings.
Views and Reports
• Perform a single-level explosion of bills of material (or fully indented
explosions).
• Choose to include or exclude costs in the explosion.

Chapter 9 - Page 6
• Compare two bills of material or alternative versions of the same bill of
material.

Chapter 9 - Page 7
Oracle Bills of Material/Engineering Bills of Material
Structures
Oracle Bills of Material/Engineering

Bills of Material Structures
MTL_ MTL_
ITEM_ SECONDARY_
BOM_
LOCATIONS INVENTORIES
INVENTORY_
COMPONENTS
MTL_
BOM_BILL_OF_ MTL_ SYSTEM_
MATERIALS ITEM_ ITEMS_B
PRIMARY REVISIONS
BILL
ALTERNATE
BILL
BOM_
OPERATION_ BOM_ALTERNATE_
SEQUENCES DESIGNATORS
®
MTL_SYSTEM_ITEMS_B
item attribute BOM_ENABLED allows an item to be used in bills of material.
The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID.
BOM_BILL_OF_MATERIALS
BOM_BILL_OF_MATERIALS stores information about manufacturing and
engineering bills of material. Each row represents a unique manufacturing or
engineering bill and is defined by its primary key, BILL_SEQUENCE_ID.
BOM_ALTERNATE_DESIGNATORS
BOM_ALTERNATE_DESIGNATORS stores the alternate designators used to
define alternate bills of material and routings. The primary key is
ALTERNATE_DESIGNATOR_CODE (o), ORGANIZATION_ID
BOM_INVENTORY_COMPONENTS
BOM_INVENTORY_COMPONENTS stores information about bill of material
components. COMPONENT_SEQUENCE_ID uniquely identifies each row.
There is one row per component on an operation within a given date range. The
primary key is COMPONENT_SEQUENCE_ID.
BOM_OPERATION_SEQUENCES

Chapter 9 - Page 8
BOM_OPERATION_SEQUENCES stores information about routing
operations. You can define multiple operations for a routing. You must specify
the department in which every operation must occur.
The Routing Define form prevents overlapping effective dates for the same
operation. The primary key is OPERATION_SEQUENCE_ID.
MTL_ITEM_LOCATIONS
associated attributes describe which subinventory this locator belongs to, what
the locator physical capacity is, and so on. The locator is a key flexfield; the
flexfield code is MTLL. The primary key is INVENTORY_LOCATION_ID,
ORGANIZATION_ID.
subinventory. A subinventory is a section of inventory such as raw material or
finished goods. Subinventories are assigned to items, indicating a list of valid
places where this item will physically exist in inventory. The primary key is
SECONDARY_LOCATION_NAME, ORGANIZATION_ID.
MTL_ITEM_REVISIONS
MTL_ITEM_REVISIONS stores revision levels for an inventory item. When an
item is defined, a starting revision record is written out to this table, so every
item will at least have one starting revision. The presence of an engineering
change notice code in this table indicates that the engineering system issued the
revision through the implementation process. Along with the engineering
change order, an implementation date and initiation date will be stored. The
primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION.

Chapter 9 - Page 9
Defining a Bill of Material
Defining a Bill of Material
You
You can
can create
create bills
bills of
of material
material for
for your
your parent
parent when
when
entering
entering all your component information for
all your component information for that
that bill.
bill.
Bills
Bills of
of Material
Material (M1)
(M1)
(N) Bills of Materials > Bills > Bills

Chapter 9 - Page 10
Item Revision Control
Item Revision Control
As part of creating your bill of material, you can enter

the revision and effective date for that bill.
Item
Item Revisions
Revisions (M1)
(M1)
(N) Bills of Materials > Bills > Bills (B) Revision

Chapter 9 - Page 11
Oracle Bills of Material/Engineering Resources and
Departments

Resources and Departments
BOM_RESOURCES
BOM_
DEPARTMENT_
RESOURCES
BOM_DEPARTMENTS
BOM_RESOURCES
BOM_RESOURCES stores information about material and outside processing
resources. It also stores overhead, material overheads, and material
subelements. COST_ELEMENT_ID determines the resource type. The primary
key is RESOURCE_ID.
BOM_DEPARTMENTS
BOM_DEPARTMENTS stores department information. DEPARTMENT_ID is
the primary key that uniquely identifies each row. You can assign a delivery
location for each department used, which is used with outside processing
resources. The primary key is DEPARTMENT_ID.
BOM_DEPARTMENT_RESOURCES
BOM_DEPARTMENT_RESOURCES stores information about resources that
you assign to a department. You can use these resources on routing operations.
The primary key is DEPARTMENT_ID, RESOURCE_ID.

Chapter 9 - Page 12
Outside Processing Example
Outside Processing
Example
B C
Part B is sent for outside processing, and then combined
with Part C to make Part A.
Routing Steps
WIP completion of Part B
Completion of Step 1 signals a requisition for a purchase order for an outside
service
Receive goods back into WIP for completion

Chapter 9 - Page 13
Defining a Routing
Defining a Routing
Bills of material specify the operations and their

sequence.
Routings (M1)
(N) Bills of Materials > Routings > Routings

Chapter 9 - Page 14
Oracle Bills of Material/Engineering Routings

Routings
BOM_ BOM_
OPERATION_ RESOURCES
RESOURCES
BOM_
OPERATION_ BOM_
SEQUENCES OPERATIONAL_
MTL_
ROUTINGS SYSTEM_
PRIMARY ITEMS_B
ROUTING
ALTERNATE
MTL_RTG_
ROUTING
ITEM_
REVISIONS
BOM_ALTERNATE_
DESIGNATIONS
®
MTL_SYSTEM_ITEMS_B
primary key is INVENTORY_ID, ORGANIZATION_ID.
BOM_OPERATIONAL_ROUTINGS
BOM_OPERATIONAL_ROUTINGS stores information about manufacturing
and engineering routings. The primary key is ROUTING_SEQUENCE_ID.
BOM_ALTERNATE_DESIGNATORS
BOM_ALTERNATE_DESIGNATORS stores the alternate designators you use
to define alternate bills of material and routings. The primary code is
ALTERNATE_DESIGNATOR_CODE (o), ORGANIZATION_ID.
MTL_RTG_ITEM_REVISIONS
MTL_RTG_ITEM_REVISIONS stores revision levels for routings. A revision
must be inserted into this table when a routing is defined; every routing has at
least one valid revision. The primary key is INVENTORY_ITEM_ID,
ORGANIZATION_ID, PROCESS_REVISION.
BOM_OPERATION_SEQUENCES
BOM_OPERATION_SEQUENCES stores information about routing
operations. You can define multiple operations for a routing. You must specify
the department in which every operation must occur. The primary key is
OPERATION_SEQUENCE_ID.
BOM_OPERATION_RESOURCES

Chapter 9 - Page 15
BOM_OPERATION_RESOURCES stores information about resources you
require to complete operations on routings. You can assign multiple resources
or assign the same resource multiple times at any operation. The primary key is
OPERATION_SEQUENCE_ID, RESOURCE_SEQ_NUM.
BOM_RESOURCES
BOM_RESOURCES stores information about material and outside processing
resources. It also stores overhead, material overheads, and material
subelements. COST_ELEMENT_ID determines the resource type. The primary
key is RESOURCE_ID.

Chapter 9 - Page 16
Practice 1 Setup
Practice 1 Setup
1 Using the following structure, create Bill(s) of

Material in M1-Seattle, using the seven items you
created.
Plan Item
FG 1 FG 2
PP1 PP2 PP3 PP1 PP2 PP4
2 Verify your BOM using the Indented BOM form.

®
Setup Instructions
• Assign Planning percentages for Finished Good 1 and Finished Good 2
when constructing the Plan Item BOM.
• Vary your QPAs for Purchased Parts 1 through 4 as it suits you, when
building the two finished good BOMs.
• Optionally, assign yields to the purchased parts (values must be between 0
and 1).
Create Bills of Material
1. Navigate to the Bills of Material window.
(N) Bills of Materials > Bills > Bills
• Type in the Item Number for the parent item in the single BOM. Hit the
Tab key. The item description will fill in automatically.
• Place the cursor in the Component Region field.
• Enter the appropriate Component Item Number and hit the Tab key.
• For the two Standard bills, place cursor in “Quantity” field and change
quantity per assembly (QPA) as appropriate.
• Select the Component Details tab. Change the Planning Percentage for the
planning bill and yield values for the Standard bills as appropriate.
• Save your work.
• Repeat step 1 for the remaining BOMs.
Verify Bills of Material

Chapter 9 - Page 17
2. Navigate to the Find Indented Bills form.
(N) Bills of Materials > Bills > Indented Bills
• Enter your planning item number in the item field and press the Tab key.
• Click the Find button.
• Expand your BOM using the ‘++’ button (functions exactly like the
Navigator window).
• Inspect the various tabs available.
• Return to the Indented Bills form, and enter a quantity greater than 1 in the
Quantity field, check the Use Planning percentage box and re-inspect your
BOM. Click on the Quantities tab and see your allocation by planning
percentage.

Chapter 9 - Page 18
Practice 1
Practice 1
For each Bill of Material, find the items and determine

their attached components and quantities.
Instructions
• Tables: mtl_system_items, bom_bill_of_materials,
bom_inventory_components, mtl_system_items
• Keys: segment1, organization_id, inventory_item_id, assembly_item_id,
bill_sequence_id, component_item_id
• Columns: segment1, component_quantity, segmentl

Chapter 9 - Page 19
Practice 1 Solution
Practice 1 Solution
For each Bill of Material, find the items and determine

their attached components and quantities.
SQL Code Solution

SELECT
• substr(iasy.segment1,1,10) “Assembly”,
• substr(icmp.segment1,1,15) “Component”,
• substr(comp.component_quantity,1,5) “Quant”
FROM
• mtl_system_items iasy,
• bom_bill_of_materials bom,
• bom_inventory_components comp,
• mtl_system_items icmp
WHERE
• iasy.segment1 LIKE ‘&Item%’ AND
• iasy.organization_id = 207 AND
• iasy.inventory_item_id = bom.assembly_item_id AND
• iasy.organization_id = bom.organization_id AND
• bom.bill_sequence_id = comp.bill_sequence_id AND
• comp.component_item_id = icmp.inventory_item_id AND
• icmp.organization_id = 207

Chapter 9 - Page 20
Practice 2
Practice 2
Create resources, departments and routings, in M1-

Seattle, for the assemblies in your Bills of Material.
Setup Instructions
Create Resources
1. Navigate to the Resources form.
(N) Bills of Materials > Routings > Resources
• Enter ##-res as your resource.
• Enter a description for your resource.
• Select Machine as Type.
• Select HR (hour) as UOM.
• Select WIP Move Charge Type.
• Save your work.
Create Departments
2. Navigate to Departments form.
(N) Bills of Materials > Routings > Departments
• Enter ##-dep as your Department.
• Enter Description for your Department.
• Click Resource button.
• Enter your Resource in the Resource field.
• Uncheck the Available 24 Hours box.
• Enter 10 in the Units field.
• Select the Shifts button.

Chapter 9 - Page 21
• In the Shift Number field, enter a 1.
• Save your work.
Create Routings
3. Navigate to the Routings form.
(N) Bills of Materials > Routings > Routings
• Enter the Item Number of one of your Finished Goods in the Item field.
• Enter a 10 in the Seq field in the Operations Region.
• Enter your department name in the Department field.
• Click the Operation Resources button.
• Enter a 1 in the Seq field.
• Enter your resource in Resource field from list of values.
• Enter a 4 in the Usage field.
• Select the Scheduling tab, enter a 5 in the Assigned Units field.
• Ensure that the Schedule field is set to yes.
• Repeat step 3 for your second Finished Good.

Chapter 9 - Page 22
Agenda
Agenda

• Open interfaces

Chapter 9 - Page 23
Oracle Engineering
Oracle Engineering
• Create and maintain engineering items

• Create and maintain engineering bills of materials
• Create and maintain engineering resources,
• Transfer engineering product information to
production
• Process engineering change orders
• Perform mass changes
• Delete product information
Description
Oracle Engineering interacts with other Oracle manufacturing applications to
provide a cohesive integrated business solution. Oracle Engineering helps you
define product and process specifications. It also provides the information
required for effective planning and execution.
Oracle Engineering
• Define engineering and manufacturing bills of material.
• Define engineering and manufacturing routings.
• Manage product changes with engineering change orders (ECOs).
• Create new design specifications using Oracle Engineering.
• Determine resource availability.
• Specify detailed resource use.
Introducing New Products
• Define engineering items, BOMs, and routings to prototype new product
designs.
• Calculate lead times and release engineering prototypes to manufacturing.
Defining Planning Bills
• Define planning bills to assist with sales strategy.
• Provide BOM maintenance.
Managing Engineering Changes

Chapter 9 - Page 24
• Define and implement engineering changes to prototype and production
items.
• Schedule ECOs manually with imbedded workflow, or to correspond to the
planned use-up of a specific item.
• Create ECOs across large organization structures at any given level in an
organization hierarchy.
Deleting Obsolete Information
Delete obsolete item and ECO information.

Chapter 9 - Page 25
Oracle BOM/Engineering Change Control
Oracle BOM/Engineering Change Control

BOM_
ENG_CURRENT_
INVENTORY_
SCHEDULED_DATES
COMPONENTS
BOM_BILL_OF_ MTL_
MATERIALS SYSTEM_
PRIMARY ITEMS_B
ENG_ BILL
REVISED_
COMPONENTS ENG_
ALTERNATE
REVISED_ BILL
ITEMS
ENG_
CHANGE_
ORDER_
REVISIONS ENG_ENGINEERING_CHANGES
®
ENG_ENGINEERING_CHANGES
ENG_ENGINEERING_CHANGES stores information about engineering
change order headers. Each row includes the unique identifier of the ECO, a
description, change order type, the reason and priority codes, the status and the
requestor, approval list and approval status, implementation costs, and
cancellation information. The primary key is CHANGE_NOTICE,
ORGANIZATION_ID.
ENG_CHANGE_ORDER_REVISIONS
ENG_CHANGE_ORDER_REVISIONS stores information about the user-
defined revisions of an engineering change order. It is a child table of
ENG_ENGINEERING_CHANGES. The primary key is REVISION_ID.
ENG_REVISED_ITEMS
ENG_REVISED_ITEMS stores information about the revised items (usually
assemblies) on an engineering change order. It is a child table of
ENG_ENGINEERING_CHANGES. The primary key is
REVISED_ITEM_SEQUENCE_ID.
ENG_CURRENT_SCHEDULED_DATES
ENG_CURRENT_SCHEDULED_DATES stores information about the
effective date for each revised item on an engineering change order. Each time
the effective date for a revised item on an ECO is changed, a new row is
inserted into this table. The primary key is SCHEDULE_ID,
REVISED_ITEM_SEQUENCE_ID (o).
BOM_BILL_OF_MATERIALS

Chapter 9 - Page 26
engineering bills of material. Each row represents a unique manufacturing or
engineering bill and is defined by the BILL_SEQUENCE_ID primary key.
BOM_INVENTORY_COMPONENTS
BOM_INVENTORY_COMPONENTS stores information about bill of material
components. The primary key, COMPONENT_SEQUENCE_ID, uniquely
identifies each row. There is one row per component on an operation within a
given date range.
ENG_REVISED_COMPONENTS
ENG_REVISED_COMPONENTS stores information about the implemented
and canceled revised components on an engineering change order. The primary
key is COMPONENT_SEQUENCE_ID.
MTL_SYSTEM_ITEMS_B

Chapter 9 - Page 27
Practice 3 Setup
Practice 3 Setup
1 Create an ECO, substituting one item in one of

your BOMs with another available item. Set the
effective date to a week from today.
2 Verify your indented BOM to view the impending
change.
3 Implement your ECO, then re-verify your indented
BOM.
Setup Instructions
Create an ECO
1. Navigate to the Engineering Change Orders form.
(N) Engineering > ECOs > ECOs
• Enter ##-eco in the first field on the header form. In the other header fields,
enter any values you choose from the list of values (Caution: Do NOT use
the New Prod change type; it is set up for a Workflow process).
• Click the Revised Items button and enter the item number of the BOM you
wish to change.
• Optionally, enter a new revision.
• Enter an effective date of a week from today.
• Click the Components button.
• Go to the Action field and select Disable from the list of values.
• Enter the item number of the component you wish to disable.
• Return to the Action field, and select Add from the list of values.
• Enter the item number of your new component.
• Enter the new sequence for the component.
• Return to the header form, and change the approval status to Approved, if
necessary.
• Save your work.
• Record your ECO number _____________.

Chapter 9 - Page 28
Verify Indented BOM
2. Navigate to the Find Indented Bills form.
(N) Bills of Materials > Bills > Indented Bills
• Enter the top level item for the BOM you’re changing via ECO.
• Set your Display Option drop down menu from Future and Current to All.
• Clear the Implemented Only check box.
• Click the Find button.
• Expand your BOM and select the Effectivity tab to view pending date
changes.
• Select the ECO tab to view the pending changes.
Implement Your ECO
3. Navigate to the Engineering Change Orders form.
(N) Engineering > ECOs > ECOs
• Query your ECO.
• Fromthe Tools menu, select Implement.
• Select Yes and OK.
• Repeat step 2 (Verify Indented BOM) to view the change to the Bill of
Material.

Chapter 9 - Page 29
Practice 3
Practice 3
Find the revised items included in your ECO.
Instructions
• Tables: eng_engineering_changes, mtl_system_items, eng_revised_items
• Keys: change_notice, revised_item_id, inventory_item_id,
• Columns: change_notice, segmentl

Chapter 9 - Page 30
Practice 3 Solution
Practice 3 Solution
Find the revised items included in your ECO.
SQL Code Solution

SELECT
• substr(eco.change_notice,1,10) “ECO #”,
• substr(itm.segment1,1,5) “Item#”
FROM
• eng_engineering_changes eco,
• mtl_system_items itm,
• eng_revised_items rev
WHERE
• eco.change_notice LIKE ‘&ECO%’ AND
• eco.change_notice = rev.change_notice AND
• rev.revised_item_id = itm.inventory_item_id AND
• rev.organization_id = itm.organization_id

Chapter 9 - Page 31
Agenda
Agenda

• Open interfaces

Chapter 9 - Page 32
Oracle Bills of Material/Engineering Open Interfaces

Open Interfaces
• Open Bills of Material Interface

• Open Routing Interface
Open Bills of Material Interface

With this interface, you can convert manufacturing bills of material from legacy
manufacturing systems, migrate marketing bills of material from custom sales
order entry systems, import new engineering bills from Product Data
Management (PDM) systems, add members to product families, and export
BOM data for a particular assembly to all organizations, at any given level
under an organization hierarchy.
Open Routing Interface
This interface allows you to convert manufacturing routings from legacy
manufacturing systems, import new engineering routings from PDM systems, or
update and delete existing routings.
Instructor Note
In the Open Bills of Material Interfaces definition, the export functionality has
been added. An Application Program Interface (API) is available to perform this
function. Its name, BOM_EXPORT_TAB, appears in the table on the next
page.

Chapter 9 - Page 33
Oracle BOM/Engineering Interface Tables
Oracle BOM/Engineering Interface Tables

Interface Data Flow Table, View, Table, View, or Module name
MFG Outbound View BOM_CALANDAR_MONTHS_VIEW
Calendar
Bill of Inbound/ Table BOM_BILL_OF_MTLS_INTERFACE
Material Outbound BOM_INVENTORY_COMPS_INTERFACE
BOM_REF_DESGS_INTERFACE
BOM_SUB_COMPS_INTERFACE
BOM_ITEMS_REVISIONS_INTERFACE
BOM_EXPORT_TAB
Routings Inbound Table BOM_OP_ROUTINGS_INTERFACE
BOM_OP_SEQUENCES_INTERFACE
BOM_OP_RESOURCES_INTERFACE
ECO Inbound Table ENG_ENG_CHANGES_INTERFACE
ENG_ECO_REVISIONS_INTERFACE
ENG_REVISED_ITEMS_INTERFACE
ENG_INVENTORY_COMPS_INTERFACE
ENG_REF_DESGS_INTERFACE
ENG_SUB_COMPS_INTERFACE
®
Exporting BOM Data

BOM_EXPORT_TAB is a PL/SQL table, which stores exploded bill
information for the specified assembly and for all subordinate organizations in a
specified organization hierarchy.

Chapter 9 - Page 34
Summary
Summary

major tables to BOM/Engineering setup definition.
• Bill of material structures
• Resources and departments
• Routings
• Engineering change control
• Interface tables

Chapter 9 - Page 35

Chapter 9 - Page 36
Foundation: Work in Process
Chapter 10
11i Manufacturing Functional Foundation: Work in Process

Chapter 10 - Page 1
11i Manufacturing Functional Foundation: Work in
Process

Work in Process

Chapter 10 - Page 2
Objectives
Objectives

do the following:
• Discuss the flow of inventory through a factory
• Identify the major tables used in material move and
completion transactions
database tables to review material transactions
against a particular inventory item
Lesson Aim
The aim of this lesson is to provide the student an overview of the flow of
inventory through a factory and the resulting transactions that occur in Oracle
Inventory, and discuss the database tables that are populated as a result of these
activities.
Instructor Note
associated with it.

Chapter 10 - Page 3
Agenda
Agenda
• Discrete jobs and repetitive schedules

• Work in process transactions
• Open interfaces

Chapter 10 - Page 4
Agenda
Agenda

• Open interfaces

Chapter 10 - Page 5
Discrete Versus Repetitive Manufacturing Process
Discrete Versus Repetitive

Manufacturing Process
Discrete Manufacturing Repetitive Manufacturing

Making assemblies in batches or Making assemblies continuously over a
groups predefined amount of time
Defining jobs (work orders) Defining repetitive schedules
Detailed scheduling Repetitive line scheduling
Charging the job Charging the repetitive assembly or line
Job Costing Period Costing
Discrete Manufacturing Versus Repetitive Manufacturing

A discrete job is a production order for the manufacture of a specific (discrete)
quantity of an assembly, using specific materials and resources, within a limited
range of time.
In repetitive manufacturing, you produce on a continuous or semicontinuous
basis over a predefined length of time.

Chapter 10 - Page 6
Oracle Work in Process Overview
Oracle Work in Process Overview

MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
WIP_REPETITIVE_ WIP_
ITEMS OPERATIONS
WIP_REPETITIVE_ WIP_DISCRETE_ WIP_FLOW_

SCHEDULES JOBS SCHEDULES
®
MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
WIP_ENTITIES stores information about each discrete job or repetitive
assembly. Each row includes a unique discrete job or repetitive assembly name,
entity type, and the assembly built by the job or by the repetitive assembly. The
primary key is WIP_ENTITY_ID.
WIP_REPETITIVE_ITEMS
WIP_REPETITIVE_ITEMS stores your repetitive assemblies and the
production lines on which you build each assembly. Each row represents a
particular assembly/line combination. The primary key is WIP_ENTITY_ID,
LINE_ID.
WIP_REPETITIVE_SCHEDULES
WIP_REPETITIVE_SCHEDULES stores repetitive schedule information.
Oracle Work in Process uses this information to control repetitive production.
The primary key is REPETITIVE_SCHEDULE_ID.
WIP_DISCRETE_JOBS
WIP_DISCRETE_JOBS stores information about discrete jobs. Each row
represents a discrete job. Oracle Work in Process uses this information to
control discrete production. The primary key is WIP_ENTITY_ID.

Chapter 10 - Page 7
WIP_OPERATIONS
WIP_OPERATIONS stores information about the operations for your discrete
jobs and repetitive schedules. Oracle Work in Process uses this information to
control and monitor your assembly production on the shop floor. The primary
key is WIP_ENTITY_ID, OPERATION_SEQ_NUM,
REPETITIVE_SCHEDULE_ID (o).
WIP_FLOW_SCHEDULES
WIP_FLOW_SCHEDULES stores Work Order-less Flow schedule
information. Each row represents a Flow schedule and contains information
about the assembly being built. The primary key is WIP_ENTITY_ID.
Instructor Note
The full definition and explanation of Flow Schedules will be available when
that product has been added to this course.

Chapter 10 - Page 8
Oracle Work in Process Operations
Oracle Work in Process Operations

WIP_REQUIREMENT_OPERATIONS
MTL_
SYSTEM_
ITEMS_B
WIP_
WIP_ DISCRETE_JOBS
REPETITIVE_
SCHEDULES MTL_
ITEM_
LOCATIONS
WIP_OPERATION_ WIP_
RESOURCES SHOP_FLOOR_
STATUSES
WIP_OPERATIONS
®
WIP_REQUIREMENT_OPERATIONS stores information about the material
requirements for jobs or schedules. Oracle Work in Process uses this
information to track the material used in a job or schedule. The primary key is
INVENTORY_ITEM_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM,
WIP_OPERATIONS
MTL_SYSTEM_ITEMS_B
MTL_ITEM_LOCATIONS

Chapter 10 - Page 9
associated attributes describe which subinventory this locator belongs to, what
the locator physical capacity is, etc. The primary key is
INVENTORY_LOCATION_ID, ORGANIZATION_ID.
WIP_OPERATION_RESOURCES
WIP_OPERATION_RESOURCES stores information about the resources
associated with an operation for a job or a repetitive schedule. Oracle Work in
Process uses this information to schedule jobs and repetitive schedules, and to
charge resources to jobs and schedules. The primary key is WIP_ENTITY_ID,
OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM,
WIP_DISCRETE_JOBS
WIP_SHOP_FLOOR_STATUSES
This table stores the status codes that you assign to a discrete job or repetitive
schedule. Each row contains the operation sequence number and intraoperation
step to which you assign the status. The primary key is WIP_ENTITY_ID,
OPERATION_SEQ_NUM, SHOP_FLOOR_STATUS_CODE, LINE_ID,
INTRAOPERATION_STEP_TYPE.

Chapter 10 - Page 10
Oracle Work in Process: Discrete Jobs
Oracle Work in Process: Discrete Jobs

MTL_SYSTEM_ITEMS_B
MTL_MATERIAL_
TRANSACTIONS WIP_ENTITIES
WIP_
WIP_ ACCOUNTING_
WIP_ CLASSES
OPERATION_ REQUIREMENT_
RESOURCES OPERATIONS
WIP_
DISCRETE_
JOBS WIP_WORK_
ORDER_
INTERFACE
WIP_OPERATIONS
WIP_DISCRETE_JOBS
represents a discrete job. It also contains the information about the assembly
being built, the revision of the assembly, the job quantity, the job status,
accounting information, and job schedule dates. Oracle Work in Process uses
this information to control discrete production. The primary key is
WIP_ENTITY_ID.
WIP_OPERATIONS

WIP_WORK_ORDER_INTERFACE
WIP_WORK_ORDER_INTERFACE enables you to import Discrete job and
Repetitive schedule header information, and Discrete job operations, material,
resource, and scheduling information from any source, using a single process.
There is no primary key associated with this interface.
WIP_ACCOUNTING_CLASSES
This table stores accounting flexfield information for standard discrete jobs,
nonstandard asset jobs, nonstandard expense jobs, and repetitive assemblies.
Oracle Work in Process stores a general ledger account for each cost element
associated with a class. The CLASS_CODE column uniquely identifies each
class. Oracle Work in Process uses this information to create the journal entries
that post cost transactions. The primary key is CLASS_CODE,
ORGANIZATION_ID.
MTL_SYSTEM_ITEMS_B
This is the definition table for items. This table holds the definitions for
inventory items, engineering items, and purchasing items. Each item is initially
defined in an item master organization. Then you assign the item to other
organizations that need to recognize this item. A row is inserted for each new
organization to which the item is assigned. The primary key is
INVENTORY_ITEM_ID, ORGANIZATION_ID.

Oracle Work in Process: Repetitive Schedules
Oracle Work in Process: Repetitive Schedules

MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
MTL_MATERIAL_ WIP_
WIP_REPETITIVE_ITEMS ACCOUNTING_
TRANSACTIONS
CLASSES
WIP_OPERATIONS
WIP_
WIP_ WORK_ORDER_
REPETITIVE_ INTERFACE
WIP_ WIP_ SCHEDULES
REQUIREMENT_ OPERATION_
OPERATIONS RESOURCES
WIP_REPETITIVE_ITEMS
WIP_REPETITIVE_ITEMS stores your repetitive assemblies and the
production lines on which you build each assembly. Each row represents a
particular assembly/line combination and includes information such as the line
priority, the accounting class associated with the line, the line speed, the line’s
supply type, if the line is used in calculating the assembly’s lead time, the
completion subinventory and locator for a line, and the alternate bill and routing
you use for a particular line. Oracle Work in Process uses this information when
you define repetitive schedules. Oracle Master Schedule/MRP and Oracle
Capacity use this information when mass loading repetitive schedules and
running capacity loads on repetitive schedules. The primary key is
WIP_ENTITY_ID, LINE_ID.
WIP_OPERATIONS
jobs and repetitive schedules. Each row represents a specific operation and
includes an operation sequence number to order the operations for a job or
repetitive schedule. Oracle Work in Process uses this information to control and
monitor your assembly production on the shop floor. The primary key is

WIP_ENTITY_ID, OPERATION_SEQ_NUM,
WIP_ACCOUNTING_CLASSES
This table stores accounting flexfield information for standard discrete jobs,
nonstandard asset jobs, nonstandard expense jobs, and repetitive assemblies.
Oracle Work in Process stores a general ledger account for each cost element
associated with a class. The CLASS_CODE column uniquely identifies each
class. Oracle Work in Process uses this information to create the journal entries
that post cost transactions. The primary key is CLASS_CODE,
ORAGANIZATION_ID.
MTL_SYSTEM_ITEMS_B
This is the definition table for items. This table holds the definitions for
inventory items, engineering items, and purchasing items. Each item is initially
defined in an item master organization. Then you assign the item to other
organizations that need to recognize this item. A row is inserted for each new
organization to which the item is assigned. The primary key is
INVENTORY_ITEM_ID, ORGANIZATION_ID.

Repetitive Schedules Summary Report
Repetitive Schedules Summary Report
You
You can
can display
display the
the assemblies
assemblies with
with their
their statuses
statuses for
for
aa repetitive
repetitive line.
line.
Repetitive
Repetitive Schedules
Schedules Summary
Summary (M1)
(M1)
(N) WIP > Repetitive > Repetitive Schedules

Agenda
Agenda

• Open interfaces

Oracle WIP Transactions
Inventory Work in Process
Issue
material
Jobs and
Raw material
schedules
inventory Complete
finished
assemblies Move assemblies on
the shop floor and
charge resources
Finished goods
Scrap rejected
subinventory assemblies
Work in Process Transactions

Work in Process supports discrete, project, repetitive, flow, assemble-to-order,
work order-less, or a combination of these manufacturing methods.
Manufacturing Support
Build discrete jobs, both standard and nonstandard (prototype, rework,
maintenance, and special projects).
Production Scheduling
Load and sequence repetitive production by assembly and production line.
Material Control
Issue and return components from and to inventory.
Shop Floor Control
Move assemblies between and within operations.
Transaction Functionality
Oracle Work in Process tracks material and production activity on the shop
floor to facilitate inventory control, job scheduling, and costing.
Material Issue
Record material issues to discrete jobs, repetitive schedules, nonstandard jobs,
or flow schedules.
Shop Floor Move
Record production activity including operation moves, job completions and
over-completions, and scrap transactions.

Resource Charging
• Charge multiple resources option.
• Charge resources automatically (based on shop floor moves) or manually, at
either standard or actual labor rates.
Outside Processing
Enables you to include supplier-sourced components and resources in your
manufacturing processes.
Integration with Oracle Quality
You can collect quality data as you complete and return assemblies.
Workflow Alerts and Messages
• You can use workflow-based alerts and messaging to identify and eliminate
inventory shortage situations within Oracle Work in Process.
• You can trigger alerts to key personnel when an item is moved into
inventory, when a shortage exists, or when it is completed.
Other Transactions
• Cost material using standard cost.
• Use repetitive schedules to simplify material and production reporting.
• Use lot and serial number controlled parts in production moves.

Oracle WIP Material Transactions
Oracle WIP Material Transactions

MTL_
TRANSACTION_
ACCOUNTS
MTL_ WIP_
WIP_
MATERIAL_TXN REQUIREMENT_
OPERATIONS
ALLOCATIONS OPERATIONS
MTL_
MATERIAL_ WIP_DISCRETE_JOBS
TRANSACTIONS
®
MTL_MATERIAL_TXN_ALLOCATIONS
This table stores the repetitive schedules charged by a material transaction. Each
row contains the quantity transacted to each schedule for a given transaction.
Oracle Work in Process uses this information to report changes to individual
schedules for multischedule material transactions. The primary key is
TRANSACTION_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID.
This table holds the accounting information for each material transaction in
MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information
to track the financial impact of quantity moves. (There is no primary key for
this table.)
This table stores a record of every material transaction, including issues and
returns of component items in Work in Process. Records are inserted into this
table through the transaction processor. The primary key is
TRANSACTION_ID.
This table stores information about the material requirements for jobs or
schedules. Oracle Work in Process uses this information to track the material
used in a job or schedule. The primary key is INVENTORY_ITEM_ID,
WIP_OPERATIONS

WIP_OPERATIONS stores information about the operations of your discrete
This table stores repetitive schedule information. Oracle Work in Process uses
this information to control repetitive production. The primary key is
REPETITIVE_SCHEDULE_ID.
WIP_DISCRETE_JOBS
This table stores information about discrete jobs. Each row represents a discrete
job. Oracle Work in Process uses this information to control discrete
production. The primary key is WIP_ENTITY_ID.

Material Transactions Window
Material Transactions Window
You can issue components from inventory to

jobs and return issued components from jobs
to inventory.
WIP
WIP Material
Material Transactions
Transactions (M1)
(M1)
(N) WIP > Material Transactions > WIP Material Transactions

Oracle WIP: Move Transactions
Oracle WIP: Move Transactions

WIP_TXN_
ALLOCATIONS
WIP_MOVE_TXN_ WIP_REPETITIVE_
ALLOCATIONS SCHEDULES
WIP_
OPERATIONS
WIP_
DISCRETE_JOBS
WIP_
TRANSACTIONS WIP_
OPERATION_
RESOURCES
WIP_MOVE_ MTL_MATERIAL_
TRANSACTIONS TRANSACTIONS
®
WIP_DISCRETE_JOBS
This table stores a record of every material transaction, including issues and
returns of component items in Work in Process. Records are inserted into this
table through the transaction processor. The primary key is
TRANSACTION_ID.
WIP_OPERATIONS

WIP_MOVE_TXN_ALLOCATIONS
This table stores Move quantity information for single shop floor Move
transactions that transcend multiple repetitive schedules. The primary key is
TRANSACTION_ID, REPETITIVE_SCHEDULE_ID.
WIP_TXN_ALLOCATIONS
WIP_TXN_ALLOCATIONS stores resource information for single resource
cost transactions that transcend multiple repetitive schedules. Oracle Work in
Process allocates resource charges to repetitive schedules based on a FIFO
algorithm. The primary key is TRANSACTION_ID,
WIP_TRANSACTIONS
This table stores information about each resource transaction in Oracle Work in
Process. Oracle Work in Process uses this information to track resources and to
calculate values stored in WIP_TRANSACTION_ACCOUNTS. The primary
key is TRANSACTION_ID.
WIP_MOVE_TRANSACTIONS
WIP_MOVE_TRANSACTIONS stores information about shop floor move
transactions. Each row represents a single move transaction and includes a
unique transaction ID, a transaction date, the job or repetitive schedule in which
the move occurs, the quantity moved, the from and to operation sequence
numbers, operation codes, and intraoperation steps. Oracle Work in Process
uses this information to track move transactions. The primary key is
TRANSACTION_ID.

Move Transactions Window
Move Transactions Window
You can move the assemblies you are building

from one operation step to another.
Move
Move Transactions
Transactions (M1)
(M1)
(N) WIP > Move Transactions > Move Transactions

Oracle WIP: Resource Transactions
Oracle WIP: Resource Transactions

WIP_TXN_ WIP_
ALLOCATIONS WIP_ REPETITIVE_
COST_TXN_ SCHEDULES
INTERFACE
WIP_OPERATION_
RESOURCE_
USAGE
WIP_
OPERATION_
RESOURCES
WIP_TRANSACTIONS
WIP_OPERATION_ WIP_
OVERHEADS OPERATIONS WIP_
DISCRETE_
WIP_ JOBS
TRANSACTION_
ACCOUNTS
®
WIP_DISCRETE_JOBS
WIP_OPERATIONS

WIP_TRANSACTIONS
WIP_TRANSACTIONS stores information about each resource transaction in
Oracle Work in Process. Oracle Work in Process uses this information to track
resources and to calculate values stored in
WIP_TRANSACTION_ACCOUNTS. The primary key is
TRANSACTION_ID.
WIP_COST_TXN_INTERFACE
WIP_COST_TXN_INTERFACE contains information about cost transactions
that Oracle Work in Process needs to process. Oracle Work in Process uses this
table to support all resource cost transactions, including transactions you
process from other systems. The primary key is TRANSACTION_ID (o).
WIP_TRANSACTION_ACCOUNTS
WIP_TRANSACTION_ACCOUNTS holds the accounting information for
each resource transaction in WIP_TRANSACTIONS. These tables are joined
by the TRANSACTION_ID column, and there are at least two rows (debit and
credit) for each transaction of a costed resource. Oracle Work in Process uses
this information to track the financial impact of resource transactions. There is
no primary key.
WIP_TXN_ALLOCATIONS
WIP_TXN_ALLOCATIONS stores resource information for single resource
cost transactions that transcend multiple repetitive schedules. Oracle Work in
Process allocates resource charges to repetitive schedules based on a FIFO
algorithm. The primary key is TRANSACTION_ID,
WIP_OPERATION_RESOURCE_USAGE
WIP_OPERATION_RESOURCE_USAGE stores information about the use of
resources associated with job and schedule operations. Each row represents a
resource usage in a valid shift for that particular resource. There is no primary
key.
WIP_OPERATION_OVERHEADS
WIP_OPERATION_OVERHEADS stores information about resource-based
and departmental overhead costs for jobs in an average costing organization.
The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM,
OVERHEAD_ID, RESOURCE_SEQ_NUM, BASIS_TYPE.

Resource Transaction Window
Resource Transaction Window
You can use this form to charge resources.
Resource Transactions (M1)
(N) WIP > Resource Transactions > Resource Transactions

Oracle WIP: Completion Transactions
Oracle WIP: Completion Transactions

MTL_ WIP_
MATERIAL_TXN_ REPETITIVE_
ALLOCATIONS SCHEDULES
MTL_
TRANSACTION
ACCOUNTS
MTL_MATERIAL_
WIP_FLOW_
TRANSACTIONS_
SCHEDULES
TEMP
MTL_MATERIAL_
TRANSACTIONS
WIP_DISCRETE_
JOBS
WIP_DISCRETE_JOBS
MTL_MATERIAL_TRANSACTIONS_TEMP is the gateway for all material
transactions. Transfer records are stored in this table as a single record. The
primary key is TRANSACTION_HEADER_ID (o).
MTL_TRANSACTION_ACCOUNTS holds the accounting information for
each material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle
Inventory uses this information to track the financial impact of quantity moves.
There is no primary key for this table.

MTL_MATERIAL_TXN_ALLOCATIONS
MTL_MATERIAL_TXN_ALLOCATIONS stores the repetitive schedules
charged by a material transaction. Each row contains the quantity transacted to
each schedule for a given transaction. Oracle Work in Process uses this
information to report changes to individual schedules for multischedule material
transactions. the Primary key is TRANSACTION_ID,
REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID.
WIP_FLOW_SCHEDULES
information. Each row represents a Flow schedule and contains information
about the assembly being built. The primary key is WIP_ENTITY_ID
Instructor Note
The full definition and explanation of Flow Schedules will be available when
that product has been added to this course.

Completion Transactions window
Completion Transactions window
You can complete assemblies from jobs into

inventory, and you can return completed
assemblies from inventory to jobs.
Completion Transactions (M1)
(N) WIP . Material Transactions > Completion Transactions

Oracle WIP: Work Order-less Completions
Oracle WIP: Work Order-less Completions

MTL_
TRANSACTIONS_ WIP_PERIOD_
INTERFACE BALANCES
MTL_MATERIAL_
TRANSACTIONS
MTL_MATERIAL_ WIP_
TRANSACTIONS_ WIP_
FLOW_
TEMP SCHEDULES TRANSACTIONS
BOM_
BILL_OF_
WIP_ENTITIES
MATERIALS
BOM_
OPERATIONAL_
ROUTINGS
®
WIP_FLOW_SCHEDULES
information. Each row represents a Flow schedule. Oracle Work in Process uses
this information to control Flow schedule production. The primary key is
WIP_ENTITY_ID.
MTL_TRANSACTIONS_INTERFACE
MTL_TRANSACTION_INTERFACE is the interface point between non
Oracle Inventory applications and the Oracle Inventory transaction module.
Transaction Manager concurrent program polls this table at a user specified
process interval, and submits the Transaction Workers to process them. There is
no primary key for this table.
MTL_MATERIAL_TRANSACTIONS_TEMP is the gateway for all material
transactions. Transfer records are stored in this table as a single record. The
primary key is TRANSACTION_HEADER_ID.
BOM_BILL_OF_MATERIAS

engineering bills of material. Each row in this table represents a unique
manufacturing or engineering bill. The primary key is BILL_SEQUENCE_ID.
BOM_OPERATIONAL_ROUTINGS
BOM_OPERATIONAL_ROUTINGS stores information about manufacturing
and engineering routings. The primary key is ROUTING_SEQUENCE_ID.
WIP_PERIOD_BALANCES
WIP_PERIOD_BALANCES stores summary accounting information for jobs and
schedules. Each row represents job or schedule charges within a given accounting
period, and contains the summary values for each cost element. The primary key
is ACCT_PERIOD_ID, WIP_ENTITY_ID.
WIP_TRANSACTIONS
WIP_TRANSACTIONS stores information about each resource transaction in
Oracle Work in Process. Oracle Work in Process uses this information to track
resources and to calculate values stored in
WIP_TRANSACTION_ACCOUNTS. The primary key is
TRANSACTION_ID.
WIP_ENTITIES
WIP_ENTITIES stores information about jobs, repetitive assemblies, and flow
schedules. Each row includes a unique entity name, the entity type, and the
assembly being built. The primary key is WIP_ENTITY_ID.

Work Order-less Completions Window
Work Order-less Completions Window
You can complete or return assemblies to or from

inventory. You can scrap assemblies from or return
scrapped assemblies to any operation.
Work Order-less Completions (M1)
(N) WIP > Material Transactions > Work Order-less Completions

Practice 1 Setup
Practice 1 Setup
Create and release a discrete job for one of your

assembly planned orders.
Setup Instructions
Navigate to the Discrete Jobs window.
. (N)WIP > Discrete > Discrete Jobs
• Enter your assembly number in the Assembly field and choose Find.
• In the Discrete Job Summary window, select one of your jobs and Open it
• Record your job number
• Change the status of your job to “Released” from the LOV
• Click in the Bill box for a list of regions and select Routing
• Enter a Completion Subinventory from the LOV
• Save your work
• Check the operation and component information for your assembly
• Navigate to the Material Requirements window.
(N) WIP-> Job/Schedule Details->Material Requirements
• Change some of your components to Push supply type.
• Save your work.
• Navigate to the WIP Material Transaction window.
(N) WIP > Material Transactions > WIP Material Transactions
• Enter your job number and click Continue (you should see your Push
components in the window for issue); then select Done.
• Navigate to the Move Transactions window.

(N) WIP > Move Transactions -> Move Transactions
• Enter your job number.
• Select Transaction Type of Complete (note default information in the
Operations region).
• In the Operations region, click in From (Seq) box and perform LOV
(information is defaulted in).
• In Transaction region, enter the full Quantity to complete all assemblies
• Save your work.
• Navigate to the following windows, enter your job number and review the
fields in the windows (note: only released jobs can be entered in these
windows):
– Resource Transaction window which is used only for manual resource
transactions can be accessed with the Resources button in the Move
Transaction window.
– Completion Transaction window is used for routine completion
transactions when assemblies are available to complete in the last
routing operation in the To Move intra-operational step.

Practice 1
Practice 1

Instructions
• Tables: wip_discret_jobs, mtl_system_items_b, mfg_lookups
• Keys: segment1, organization_id, inventory_item_id, primary_item_id,
status_type
• Columns: lookup_type, lookup_code, meaning, wip_entity_id, description,
start_quantity, quantity_completed, scheduled_completion_date

Practice 1 Solution
Practice 1 Solution

SQL Code Solution (to find the correct status type)

SELECT
• substr(lookup_type,1,15) “Type”,
• substr(lookup_code,1,5) “Code”,
• substr(meaning,1,15) “Meaning”,
FROM
• mfg_lookups
WHERE
• lookup_type LIKE ‘WIP_JOB_STATUS’
SQL Code Solution (to find the job)
SELECT
• substr(wip.wip_entity_id,1,10) “Job”,
• substr(wip.description,1,10) “Desc”,
• substr(wip.start_quantity,1,5) “Quant”,
• substr(wip.quantity_completed,1,5) “Comp”,
• substr(wip.scheduled_completion_date,1,10) “Date”,
FROM
• wip_discrete_jobs wip,
• mtl_system_item_b inv
WHERE

• inv.inventory_item_id = wip.primary_item_id AND
• wip.organization_id = inv.organization_id AND
• wip.status_type = 4

Agenda
Agenda

• Open interfaces

Oracle WIP: Open Interfaces
Oracle WIP: Open Interfaces
• Work Order Interface

• Open Move Transaction Interface
• Open Resource Transaction Interface
Work Order Interface

Using this interface, you can import:
• planned orders for new Discrete jobs
• Discrete job operations, components, resources, resource usage, and
scheduling details
• update and reschedule recommendations for existing Discrete jobs, and
suggested Repetitive schedules.
Oracle Work in Process uses this information to automatically create Discrete
jobs and pending Repetitive schedules, or to update existing Discrete jobs. This
interface consists of two tables: Open Job and Schedule Interface table and WIP
Job Details Interface table.
Open Move Transaction Interface
You can use external data collection devices such as bar-code readers,
automated test equipment, cell controllers, and other manufacturing execution
systems to collect move transactions or combined move and completion/return
transactions.
Open Resource Transaction Interface
This interface enables you to use external data collection devices such as bar-
code readers, payroll systems, and time-card entry forms to collect resource and
overhead transactions.

Oracle WIP Transactions Open Interface Tables

Open Interface Tables

Process
Moves Inbound Table WIP_MOVE_TXN_INTERFACE
Resource Inbound Table WIP_COST_TXN_INTERFACE
Work Order Inbound/ Process MTL_TRANACTIONS_INTERFACE
Interface Outbound and MTL_SERIAL_NUMBERS_INTERFACE
Table MTL_TRANSACTION_LOTS_INTERFACE
Stored Procedures
LOAD_INTERFACE and LOAD_WIP
and WIP_SCHEDULING_INTERFACE

Summary
Summary

major tables to Work in Process inventory
transactions:
• Discrete jobs
• Repetitive schedules
• Material transactions:
– Move
– Resource
– Completion
– Work Order-less Completions
• Open interfaces

Foundation: Cost
Management
Chapter 11
11i Manufacturing Functional Foundation: Cost Management

Chapter 11 - Page 1
11i Manufacturing Functional Foundation: Cost
Management

Cost Management

Chapter 11 - Page 2
Objectives
Objectives

do the following:
• Discuss costing setup definition activities
• Identify the major tables used in cost resources
and overhead definitions
database tables to find the cost of a particular item
Lesson Aim
The aim of this lesson is to provide the student an overview of the setup
definition process in Oracle Cost and discuss the database tables that are
populated as a result of the costing setup activity.
Instructor Note
associated with it.

Chapter 11 - Page 3
Agenda
Agenda
• Overview
• Open interfaces

Chapter 11 - Page 4
Agenda
Agenda
• Overview
• Open interfaces

Chapter 11 - Page 5
Item Analysis Audit trail

costs
Inventory Production Profitability
Description
Oracle Cost Management automatically performs the cost accounting for all
your Oracle Inventory, Work in Process, and Purchasing transactions. Your
inventory and work-in-process costs are up-to-date, and your inventory value
matches the cumulative total of your accounting transactions.
Standard Costing
• Oracle Cost Management supports standard costing for inventory, bills of
material, and work-in-process costing.
• Organizations that use Oracle Work in Process must use standard costing. If
you use Oracle Inventory without Oracle Work in Process, you can choose
either standard or average costing.
• You may use standard costing for one organization and average costing for
another organization.
Average Costing
• Oracle Cost Management supports average costing for inventory. Average
costs
are automatically updated as transactions are processed.
• If you have Oracle Bills of Material installed and do not use Oracle Work in
Process for your organization, you may transact your inventory at average, and
use the standard cost features for product cost simulations and budgeting.
Extensive Cost Simulation Capability

Chapter 11 - Page 6
• Create unlimited sets of product costs, called cost types. Each cost type has its
own items and specific cost controls for the items.
• Copy from one cost type to another, mass edit a cost type, run item cost and
comparison reports, roll up costs, or update frozen standard costs by cost type.
Each cost type may have its own activities and activity-based costs.
Simultaneous Open Periods
• Set up and maintain simultaneous open periods.
• Run transactions for the next period and still report inventory balances and
quantities from the prior open period using historical inventory valuation
reports. This gives you the flexibility to reconcile and analyze the period
before you close it, while you continue to conduct business in the subsequent
period.
Period Close and General Ledger Transfer
• Close the earliest open period at any time. Closing a period automatically
transfers summary or detailed information to the general ledger.
• Perform interim general ledger transfers at any time, without closing a period.
The general ledger transfer passes all accounting entries not transferred since
the last period close.
Accruals Booked on Receipt
Oracle Purchasing updates the accounts payable accrual accounts automatically
and accrues your uninvoiced receipts.

Chapter 11 - Page 7
Cost Information
Cost Information
Cost rollup
Engineering
information
Cost update
Cost Processes
There are two main processes in defining costs: cost updates and cost rollups.
Costs are defined at the item level and the cost rollup process will determine
costs at the higher levels as defined in the bill of material. Typically, a series of
cost rollups are performed in order to:
• determine appropriate cost information at the higher bill of material levels
• perform a cost update to freeze costs for the next period, when final costs
seem appropriate.
Each of these processes runs exclusively to avoid conflict in processing, since
there is a general ledger impact. As items are sold, a cost variance for a gain or
loss is recorded in the general ledger.

Chapter 11 - Page 8
Agenda
Agenda
• Overview
• Open interfaces

Chapter 11 - Page 9
Cost Type: Standard
Cost Type: Standard
MTL_SYSTEM_ITEMS_B
CST_COST_
CST_COST_TYPES ELEMENTS
BOM_
CST_ITEM_COSTS CST_ACTIVITIES RESOURCES
CST_ITEM_COST_DETAILS
MTL_SYSTEM_ITEMS_B
CST_COST_TYPES
CST_COST_TYPES stores the cost type definition. Cost types represent sets of
costs, frozen cost, or next year’s cost. The table is seeded with the following
costs types:
• Frozen: The organization uses the standard costing method.
• Pending: For standard cost organizations, Pending charges to the frozen
cost.
• Average: The organization uses the average costing method.
• FIFO: The organization uses the FIFO costing method.
• LIFO: The organization uses the LIFO costing method.
You can define as many additional cost types as you want. The primary key is
COST_TYPE_ID.
CST_ITEM_COSTS
CST_ITEM_COSTS stores the cost control information. The Define Item Cost
window inserts information into this table. The primary key is
INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID.
CST_COST_ELEMENTS

CST_COST_ELEMENTS stores the cost element information. It is seeded with
five cost elements: Material, Material Overhead, Resource, Outside Processing,
and Overhead. The primary key is COST_ELEMENT_ID.
CST_ITEM_COST_DETAILS
CST_ITEM_COST_DETAILS stores detailed cost information for an item for a
cost type. It is the child table of CST_ITEM_COSTS. The primary key is
CST_ACTIVITIES
CST_ACTIVITIES stores activity definitions. An activity can be organization-
specific or shared among all organizations. The primary key is ACTIVITY_ID.
BOM_RESOURCES
BOM_RESOURCES stores information about all cost subelements, resources,
overhead, material overheads, and material subelements. COST_ELEMENT_ID
determines the resource type. The primary key is RESOURCE_ID.

Cost Types: Average, FIFO, LIFO
Cost Types: Average, FIFO, LIFO
MTL_SYSTEM_ITEMS_B
CST_COST_
CST_COST_TYPES ELEMENTS
BOM_
CST_ITEM_COSTS CST_ACTIVITIES RESOURCES
CST_QUANTITY_LAYERS
CST_LAYER_
COST_DETAILS
®
MTL_SYSTEM_ITEMS_B
CST_COST_TYPES
costs, frozen cost, or next year’s cost. The table is seeded with the following
costs types:
cost.
COST_TYPE_ID.
CST_ITEM_COSTS
CST_ITEM_COSTS stores the cost control information. The Define Item Cost
form inserts information into this table. The primary key is
CST_COST_ELEMENTS

CST_COST_ELEMENTS stores the cost element information. It is seeded with
five cost elements: Material, Material Overhead, Resource, Outside Processing,
and Overhead. The primary key is COST_ELEMENT_ID.
CST_QUANTITY_LAYERS
CST_QUANTITY_LAYERS stores item average cost, FIFO, and LIFO
information by cost layer. This table is only used for average costing, FIFO, and
LIFO organizations. The primary key is LAYER_ID.
CST_LAYER_COST_DETAILS
CST_LAYER_COST_DETAILS stores detailed cost information by element
and level. It is a child table of CST_QUANTITY_LAYERS. The primary key is
LAYER_ID, COST_ELEMENT_ID, LEVEL_TYPE.
CST_ACTIVITIES
CST_ACTIVITIES stores activity definitions. An activity can be organization-
specific or shared among all organizations. The primary key is ACTIVITY_ID.
BOM_RESOURCES
BOM_RESOURCES stores information about all cost subelements, resources,
overhead, material overheads, and material subelements. COST_ELEMENT_ID
determines the resource type. The primary key is RESOURCE_ID.

Oracle Cost Management Resource and Overhead
Costs

Resource and Overhead Costs
CST_COST_TYPES
CST_
RESOURCE_
COSTS
BOM_RESOURCES
MATERIAL OVERHEAD
CST_
MATERIAL RESOURCE/
OUTSIDE RESOURCE_ BOM_
OVERHEAD PROCESSING OVERHEADS DEPARTMENTS
CST_DEPARTMENT_OVERHEADS
®
BOM_DEPARTMENTS
BOM_DEPARTMENTS stores department information. DEPARTMENT_ID is
the primary key and uniquely identifies each row.
CST_RESOURCE_COSTS
CST_RESOURCE_COSTS stores resource and outside processing resource unit
costs by a cost type. The primary key is RESOURCE_ID, COST_TYPE_ID.
CST_COST_TYPES
costs, frozen cost, and next year’s cost. The table is seeded with the following
costs types:
cost.
COST_TYPE_ID.
CST_RESOURCE_OVERHEADS

CST_RESOURCE_OVERHEADS stores the list of resources to which an
overhead applies. The cost processor looks at this table to find the overheads
that need to be absorbed. The primary key is COST_TYPE_ID,
RESOURCE_ID, OVERHEAD_ID.
CST_DEPARTMENT_OVERHEADS
CST_DEPARTMENT_OVERHEADS stores overhead rates for a cost type.
You can define overhead rates in the Define Overhead window. The primary
key is DEPARTMENT_ID, COST_TYPE_ID, OVERHEAD_ID.
BOM_RESOURCES
BOM_RESOURCES stores information about resources, overhead, material
overheads, and material subelements. COST_ELEMENT_ID determines the
resource type. The primary key is RESOURCE_ID.

Item Cost Summary and Details
Item Cost Summary and Details

Oracle Cost Management is a full absorption, perpetual and
periodic cost system for purchasing, inventory, and work in
process transactions. Cost Management automatically costs
and values all inventory, work in process, and purchasing
transactions.
Item
Item Costs
Costs Summary
Summary (M1)
(M1)
Current Item
Item Costs
Costs Details
Details (M1)
(M1)
Engineering
Frozen
Pending Current
(N) Cost > Item Costs > Item Costs

Practice 1 Setup
Practice 1 Setup
1 Assign Material and Material Overhead costs to your

purchased items.
2 Assign Resource costs.
3 Perform an Assembly Cost Rollup on your two Finished
Goods.
4 Perform a Standard Cost Update for your Items.
Setup Instructions
1 Assign Material and Material Overhead costs.
(N) Cost > Item Costs > Item Costs (B) New
a Enter your Finished Good item numbers, enter a cost type of Pending.
b Save your work.
c Enter your a Purchased item number, enter a cost type of Pending.
d Click the Costs button.
e Enter Material as your Cost Element.
f Select an Amount.
g Go to the next row down and select Material Overhead as your Cost
Element.
i Select Mat’l Mgmt as your SubElement.
j Select Total Value as your Basis.
k Enter any decimal percentage ( e.g. 5% = .05) in the Rate/Amount field.
l Save your work.
Repeat steps c through i for the remainder of your purchased items.
2 Assign Resource costs
(N) Bills of Materials > Routings > Resources
a Query up your resource.
b Click the Costed & Standard Rate check boxes.

c Select the Absorption Account field, enter % and press the tab key.
d Select one of the account numbers.
e Select the Variance Account field, enter % and press the tab key.
f Select one of the account numbers.
g Click the Rates button, and select Pending as the Cost Type.
h Enter a rate.
i Save your work.
3 Perform Assembly Cost Rollup
N) Cost > Item Costs > Assembly Cost Rollup
a Select Single Request
b Select Cost Rollup - Print Report GUI for Request Name
c In the Parameters form, select:
1) Cost Type = Pending
2) Range = Range of Items
3) Item From = Your Lower Finished Good Item (##-hot)
4) Item To = Your Upper Finished Good Item (##-mild)
d Submit you request.
e View your request.
f When your request is complete, place your cursor on your job, click the
View Output button and see the rollup result.
g Return to the Item Costs screen, query up all of your items, and note the
difference between Frozen and Pending costs.
4 Perform Standard Cost Update
(N) Cost > Item Costs > Standard Cost Update > Update Costs
a Select Cost Type of Pending.
b Adjustment Account Alias of Std Cost Var
c Description: update ## cost.
d Item Range: Range of Items
e Update Option: Overhead, resource, activity and item cost
f Item From: Your Lowest Item (##-garlic)
g Item To: Your Upper Item (##-tomato)
h Click the Submit Request button.
i When your request is complete, return to the Item Costs screen, query
your items and note Cost Update by using the horizontal scroll bar
below the table of item records.

Practice 1
Practice 1
Find the material and material overhead costs associated with

your items.
Instructions
• Tables: mtl_system_items_b, cst_item_costs, cst_cost_types
• Keys: segment1, cost_type, organization_id, cost_type_id, ventory_item_id
• Columns: segment1, material_cost, material_overhead_cost, cost_type_id

Practice 1 Solution
Practice 1 Solution
Find the material and material overhead costs associated with

your items.
SQL Code Solution

SELECT
• substr(cst.material_cost,1,10) “Cost”,
• substr(cst.material_overhead_cost,1,10) “Overhead”,
• substr(typ.cost_type,1,10) “Type”
FROM
• mtl_system_items_b inv,
• cst_item_costs cst,
• cst_cost_types typ
WHERE
• typ.cost_type LIKE ‘&Type%’ AND
• cst.organization_id = inv.organization_id AND
• inv.inventory_item_id = cst.inventory_item_id AND
• cst.cost_type_id = typ.cost_type_id

Agenda
Agenda
• Overview
• Open interfaces

Oracle Cost Management Open Interfaces

Open Interfaces
• Item Cost Inquiry

• MFG Cost Reporting
Item Cost Inquiry Open Interface

You can create user-defined inquiries by associating a template type for each
query. The template type determines which columns are displayed in the View
Item Costs Summary window. For more detailed information, refer to the
Oracle Bills of Material Technical Reference Manual.
MFG Cost Reporting Open Interface
You can set detail options for all relevant Item Cost Reports information by
using this interface. A detail option specifies how to summarize item costs and
which template to use to display the item costs. For more detailed information,
refer to the Oracle Bills of Material Technical Reference Manual.

Oracle Cost Management Interface Tables
Oracle Cost Management Interface Tables
Interface Data Flow Table, View, Table, View, or Module name

Item Cost Outbound View CST_INQUIRY_TYPES
Inquiry CSTFQVIC (View Item Cost Information)
MFG Cost Outbound View CST_REPORT_TYPES
Reporting CSTRFICR (Inventory Valuation Report)

Summary
Summary

major tables to Cost Management setup definitions:
• Cost Information
• Resources and Overhead
• Interface Tables


Instructor Guide

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Instructor Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

11i Manufacturing Functional

Restricted Rights Legend

Amy Sonczalla, Bill Figini, Bill Sawyer, Leanne Vakoc

Technical Contributors and Reviewers

This book was published using:

Applications Architecture .....................................................................................................1-1

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

• Ability to perform queries and display data using SQL*Plus

• Thorough knowledge and proficiency in navigating Oracle applications

• Working experience with at least one of the Oracle Manufacturing

• Working experience with Oracle Applications System Administration,

1) At least one of the following Oracle application courses:

How This Course Is Organized

This is an instructor-led course featuring lecture and hands-on exercises. Online

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Title Part Number

Installation manuals by platform

Oracle Application Object Library/Workflow Manual A80844-01

Oracle Inventory Technical Reference Manual A90206-01

Oracle Bills of Material Technical Reference Manual A90198-01

Oracle Engineering Technical Reference Manual A90177-01

Oracle Work in Process Technical Reference Manual A81185-01

• System release bulletins

• Installation and user’s guides

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Convention Element Example

Caps and Buttons, Click the Executable button.

Courier new, Code output, Code output: debug.set (‘I”, 300);

Initial cap Graphics labels Customer address (but Oracle Payables)

Italic Emphasized words Do not save changes to the database.

Uppercase SQL column Use the SELECT command to view

Convention Element Example

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Commas Key sequences Press and release keys one at a time:

Typographic Conventions in Code

Convention Element Example

Passwords DROP USER scott

Lowercase Syntax variables CREATE ROLE role

Typographic Conventions in Navigation Paths

This simplified path translates to the following:

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

3. (B) Click the Approve button.

Copyright © Oracle Corporation, 2001. All rights reserved.

11i Manufacturing Functional Foundation Table of Contents

Typographical Conventions in Help System Paths

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions: