..........................................................................................
..........................................................................................
Oracler Inventory
..........................................................................................
Technical Reference Manual
..........................................................................................
..........................................................................................
Release 11i
..........................................................................................
..........................................................................................
Volume 1
..........................................................................................
..........................................................................................
..........................................................................................
CAUTION!See back cover for important information.
..........................................................................................
This document contains proprietary, confidential information
that is the exclusive property of Oracle Corporation.
..........................................................................................
..........................................................................................
..........................................................................................
..........................................................................................
..........................................................................................
Oracler Inventory Technical Reference ManualRELEASE 11i VOLUME
1
December 1999
Major Contributors: Milan Bhatia, Sureshbabu Chennalath, Siva
Dirisala, Karthik Gnanamurthy, Manju Juneja, Guangjie Li, Mani
Rana, Dav Santoro, Shelly Sia Contributors: Christopher Andrews,
Jill Arehart, Christina Ravaglia
This Technical Reference Manual (TRM) in any form, software or
printed matter, contains proprietary information of Oracle
Corporation; it i provided under an Oracle Corporation agreement
containing restrictions on use and disclosure and is also protected
by copyright, patent, an other intellectual property law.
Restrictions applicable to this TRM include, but are not limited
to: (a) exercising either the same degree of ca safeguard the
confidentiality of this TRM as you exercise to safeguard the
confidentiality of your own most important Confidential Informatio
a reasonable degree of care, whichever is greater; (b) maintaining
agreements with your employees and agents that protect the
Confidential Information of third parties such as Oracle
Corporation and instructing such employees and agents of these
requirements for this TRM; (c) restricting disclosure of this TRM
to those of your employees who have a need to know consistent with
the purposes for which this TRM w disclosed to you; (d) maintaining
this TRM at all times on your premises; (e) not removing or
destroying any proprietary or confidential lege or markings placed
upon this TRM in whatever form, software or printed matter; and (f)
not reproducing or transmitting this TRM in any for by any means,
electronic or mechanical, for any purpose, without the express
written permission of Oracle Corporation. You should not use TRM in
any form, software or printed matter, to create software that
performs the same or similar functions as any Oracle Corporation
produ
The information in this TRM is subject to change without notice.
If you find any problems in the TRM in any form, software or
printed matt please report them to us in writing. Oracle
Corporation does not warrant that this TRM is errorfree. This TRM
is provided to customer as with no warranty of any kind. This TRM
does not constitute Documentation as that term is defined in
Oracles agreements.
Reverse engineering of the Programs (software and documentation)
associated with this TRM are prohibited. The Programs associated
with TRM are not intended for use in any nuclear, aviation, mass
transit, medical, or other inherently dangerous applications. It
shall be licensee responsibility to take all appropriate failsafe,
backup, redundancy and other measures to ensure the safe use of
such applications if the Programs are used for such purposes, and
Oracle disclaims liability for any damages caused by such use of
the Programs.
Restricted Rights Legend This TRM and the Programs associated
with this TRM delivered subject to the DOD FAR Supplement are
commercial computer software an use, duplication and disclosure of
the TRM and the Programs associated with this TRM shall be subject
to the licensing restrictions set forth in applicable Oracle
license agreement. Otherwise, this TRM and the Programs associated
with this TRM delivered subject to the Federal Acquisition
Regulations are restricted computer software and use, duplication
and disclosure of the TRM and the Programs associated with TRM
shall be subject to the restrictions in FAR 52.22714, Rights in
Data General, including Alternate III (June 1987). Oracle
Corporation Oracle Parkway, Redwood City, CA 94065.
Oracle is a registered trademark, and Context, Financial
Analyzer, Oracle7, Oracle8, Oracle Alert, Oracle Applications,
Oracle Discoverer, Orac Financials, Object Library, Oracle Work in
Process, Oracle Workflow, SmartClient, PL/SQL, SQL*Calc, SQL*Forms,
SQL*Loader, SQL*Menu, SQL*Net, SQL*Plus, SQL*Report,
SQL*ReportWriter, Oracle Web Employees, and SQL*QMX are trademarks
or registered trademarks of Oracl Corporation. All other company or
product names are mentioned for identification purposes only, and
may be trademarks of their respective owners..
CAUTION
T
his Technical Reference Manual in any form software or printed
matter contains proprietary, confidential information that is the
exclusive property of Oracle Corporation. If you do not have a
valid contract with Oracle for the use of this Technical Reference
Manual or have not signed a nondisclosure agreement with Oracle
covering this Technical Reference Manual, then you received this
document in an unauthorized manner and are not legally entitled to
possess or read it. Use, duplication, and disclosure are subject to
restrictions stated in your contract with Oracle Corporation.
ContentsVOLUME 1
Chapter 1
Introduction
11
Chapter 2
HighLevel Design Overview of HighLevel Design . . . . . . . . .
. . . . . . . . . . . . . . . . . . Summary Database Diagram . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . Database
Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . Public Table List . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . Forms and Table
View List . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . Internal View List . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . Single Organization View List
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Module
List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
21 22 26 29 2 37 2 51 2 56 2 59 2 60
Chapter 3
Detailed Design . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . 3 1 Overview of Detailed Design .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2 Table
and View Definitions . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . 3 3 Index
Oracle Proprietary, Confidential InformationUse Restricted by
ContractContents v
VOLUME 2
Table and View Definitions (continued) . . . . . . . . . . . . .
. . . . . . . . 3 361 Index
Oracle Proprietary, Confidential InformationUse Restricted by
Contractvi Oracle Inventory Technical Reference Manual
Oracle Proprietary, Confidential InformationUse Restricted by
ContractContents vii
Oracle Proprietary, Confidential InformationUse Restricted by
Contractviii Oracle Inventory Technical Reference Manual
CHAPTER
1
Introduction
T
he Oracle Payables Applications Technical Reference Manual
provides the information you need to understand the underlying
structure of Oracle Inventory. After reading this manual, you
should be able to convert your existing applications data,
integrate your existing applications with Inventory, and write
custom reports for Inventory, as well as read data that you need to
perform other tasks. This chapter introduces you to the Oracle
Payables Applications Technical Reference Manual, and explains how
to use it.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractIntroduction 11
IntroductionAt Oracle, we design and build applications using
Oracle Designer, our systems design technology that provides a
complete environment to support developers through all stages of a
systems life cycle. Because we use a repositorybased design
toolset, all the information regarding the underlying structure and
processing of our applications is available to us online. Using
Oracle Designer, we can present this information to you in the form
of a technical reference manual. This Oracle Payables Applications
Technical Reference Manual contains detailed, uptodate information
about the underlying structure of Oracle Inventory. As we design
and build new releases of Oracle Inventory, we update our Oracle
Designer repository to reflect our enhancements. As a result, we
can always provide you with an Oracle Payables Applications
Technical Reference Manual that contains the latest technical
information as of the publication date. Note that after the
publication date we may have added new indexes to Oracle Inventory
to improve performance. About this Manual This manual describes the
Oracle Applications Release 11i data model, as used by Oracle
Inventory; it discusses the database we include with a fresh
install of Oracle Applications Release 11i. If you have not yet
upgraded to Release 11i, your database may differ from the database
we document in this book. If you have upgraded from a previous
release, you might find it helpful to use this manual with the
appropriate Oracle Applications Product Update Notes manual. The
product update notes list database changes and seed data changes in
Oracle Inventory between releases. The Oracle Applications Product
Update Notes Release 11 manual describes the changes between
Release 10.7 and Release 11, and the Oracle Applications Product
Update Notes Release 11i manual describes the changes between
Release 11 and Release 11i. You can contact your Oracle
representative to confirm that you have the latest technical
information for Oracle Inventory. You can also use OracleMetaLink
which is accessible through Oracles Support Web Center
(http://www.oracle.com/support/elec_sup).
Oracle Proprietary, Confidential InformationUse Restricted by
Contract12 Oracle Inventory Technical Reference Manual
Finding the Latest InformationThe Oracle Payables Applications
Technical Reference Manual contains the latest information as of
the publication date. For the latest information we encourage you
to use OracleMetaLink which is accessible through Oracles Support
Web Center (http://www.oracle.com/support/elec_sup).
AudienceThe Oracle Payables Applications Technical Reference
Manual provides useful guidance and assistance to: Technical End
Users Consultants Systems Analysts System Administrators Other MIS
professionals This manual assumes that you have a basic
understanding of structured analysis and design, and of relational
databases. It also assumes that you are familiar with Oracle
Application Object Library and Inventory. If you are not familiar
with the above products, we suggest that you attend one or more of
the training classes available through Oracle Education (see: Other
Information Sources: page 1 8).
How This Manual is OrganizedThis manual contains two major
sections, HighLevel Design and Detailed Design. HighLevel Design
This section, Chapter 2, contains database diagrams and lists each
database table and view that Oracle Inventory uses. This chapter
also has a list of modules.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractIntroduction 13
Detailed Design This section, Chapter 3, contains a detailed
description of the Oracle Inventory database design, including
information about each database table and view you might need for
your custom reporting or other data requirements.
Oracle Proprietary, Confidential InformationUse Restricted by
Contract14 Oracle Inventory Technical Reference Manual
How to Use This ManualThe Oracle Payables Applications Technical
Reference Manual is a single, centralized source for all the
information you need to know about the underlying structure and
processing of Inventory. For example, you can use this manual when
you need to: Convert existing application data Integrate your
Oracle Inventory application with your other applications systems
Write custom reports Define alerts against Oracle Applications
tables Configure your Oracle SelfService Web Applications Create
views for decision support queries using query tools Create
business views for Oracle Discoverer You need not read this manual
cover to cover. Use the table of contents and index to quickly
locate the information you need.
How Not To Use This ManualDo not use this manual to plan
modifications You should not use this manual to plan modifications
to Inventory. Modifying Oracle Inventory limits your ability to
upgrade to future releases of your Oracle Inventory application. In
addition, it interferes with our ability to give you the
highquality support you deserve. We have constructed Inventory so
that you can customize it to fit your needs without programming,
and you can integrate it with your existing applications through
interface tables. However, should you require program
modifications, you should contact our support team (see: Other
Information Sources: page 1 8). They can put you in touch with
Oracle Services, the professional consulting organization of
Oracle. Their team of experienced applications professionals can
make the modifications you need while ensuring upward compatibility
with future product releases.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractIntroduction 15
Do not write data into noninterface tables Oracle reserves the
right to change the structure of Oracle Applications tables, and to
change the meaning of, add, or delete lookup codes and data in
future releases. Do not write data directly into or change data in
noninterface tables using SQL*Plus or other programming tools
because you risk corrupting your database and interfering with our
ability to support you. Moreover, this version of the Oracle
Payables Applications Technical Reference Manual does not contain
complete information about the dependencies between Oracle
Inventory applications tables. Therefore, you should write data
into only those tables we identify as interface tables. If you
write data into other noninterface tables, you risk violating your
data integrity since you might not fulfill all the data
dependencies in your Oracle Inventory application. You are
responsible for the support and upgrade of the logic within the
procedures that you write, which may be affected by changes between
releases of Oracle Applications. Do not rely on upward
compatibility of the data model Oracle reserves the right to change
the structure of Oracle Inventory tables, and to change the meaning
of, add, or delete lookup codes and other data in future releases.
We do not guarantee the upward compatibility of the Oracle
Inventory data model. For example, if you write a report that
identifies concurrent requests that end in Error status by
selecting directly from Oracle Application Object Library tables,
we do not guarantee that your report will work properly after an
upgrade.
About Oracle Application Object LibraryThe Oracle Payables
Applications Technical Reference Manual may contain references to
tables that belong to Oracle Application Object Library. Oracle
Application Object Library is a collection of prebuilt application
components and facilities for building Oracle Applications and
extensions to Oracle Applications. Oracle Application Coding
Standards use the Oracle Application Object Library and contains
shared components including but not limited to forms, subroutines,
concurrent programs and reports, database tables and objects,
messages, menus, responsibilities, flexfield definitions and online
help.
Oracle Proprietary, Confidential InformationUse Restricted by
Contract16 Oracle Inventory Technical Reference Manual
Attention: Oracle does not support any customization of Oracle
Application Object Library tables or modules, not even by Oracle
consultants. (Oracle Application Object Library tables generally
have names beginning with FND_%.) Accordingly, this manual does not
contain detailed information about most Oracle Application Object
Library tables used by Inventory.
A Few Words About TerminologyThe following list provides you
with definitions for terms that we use throughout this manual:
Relationship A relationship describes any significant way in which
two tables may be associated. For example, rows in the Journal
Headers table may have a onetomany relationship with rows in the
Journal Lines table. Database Diagram A database diagram is a
graphic representation of application tables and the relationships
between them. Summary Database Diagram A summary database diagram
shows the most important application tables and the relationships
between them. It omits tables and relationships that contribute
little to the understanding of the application data model.
Typically, a summary database diagram shows tables that contain key
reference and transaction data. Module A module is a program or
procedure that implements one or more business functions, or parts
of a business function, within an application. Modules include
forms, concurrent programs and reports, and subroutines.
Application Building Block An application building block is a set
of tables and modules (forms, reports, and concurrent programs)
that implement closelyrelatedOracle Proprietary, Confidential
InformationUse Restricted by ContractIntroduction 17
database objects and their associated processing. Said another
way, an application building block is a logical unit of an
application. QuickCodes QuickCodes let you define general purpose,
static lists of values for window fields. QuickCodes allow you to
base your program logic on lookup codes while displaying
userfriendly names in a list of values window. QuickCodes simplify
name and language changes by letting you change the names your end
users see, while the codes in your underlying programs remain the
same. Form A form is a module comprised of closely related windows
that are used together to perform a task. For example, the Enter
Journals form in Oracle General Ledger includes the Enter Journals
window, the Batch window, and the More Actions window among others.
The Enter Journals window is the main window, and from it, you can
use buttons to navigate to other windows in the form. The form name
usually corresponds to the main window in the form, and is
frequently a window you open directly from the Navigator.
Other Information SourcesThere are additional information
sources, including other documentation, training and support
services, that you can use to increase your knowledge and
understanding of Oracle Designer, Oracle Application Object
Library, and Inventory. We want to make these products easy for you
and your staff to understand and use. Oracle Designer Online
Documentation The online help for Oracle Designer describes how you
can use Oracle Designer for your development needs. Oracle
Applications Developers Guide This guide contains the coding
standards followed by the Oracle Applications development staff. It
describes the Oracle Application Object Library components needed
to implement the Oracle Applications user interface described in
the Oracle Applications User Interface Standards. It also provides
information to help you build yourOracle Proprietary, Confidential
InformationUse Restricted by Contract18 Oracle Inventory Technical
Reference Manual
custom Developer forms so that they integrate with Oracle
Applications. Oracle Applications User Interface Standards This
manual contains the user interface (UI) standards followed by the
Oracle Applications development staff. It describes the UI for the
Oracle Applications products and how to apply this UI to the design
of an application built using Oracle Forms 6. Oracle Inventory User
Guide Your user guide provides you with all the information you
need to use your Release 11i Oracle Inventory application. Each
user guide is organized for fast, easy access to detailed
information in a function and taskoriented organization. Oracle
SelfService Web Applications Online Documentation This
documentation describes how Oracle SelfService Web Applications
enable companies to provide a selfservice and secure Web interface
for employees, customers, and suppliers. Employees can change their
personal status, submit expense reports, or request supplies.
Customers can check on their orders, and suppliers can share
production schedules with their trading partners. This
documentation is available in HTML only. Oracle Applications
Flexfields Guide This guide provides flexfields planning, setup and
reference information for the Oracle Inventory implementation team,
as well as for users responsible for the ongoing maintenance of
Oracle Applications product data. This manual also provides
information on creating custom reports on flexfields data. Oracle
Workflow Guide This manual explains how to define new workflow
business processes as well as customize existing Oracle
Applicationsembedded workflow processes. You also use this guide to
complete the setup steps necessary for any Oracle Applications
product that includes workflowenabled processes.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractIntroduction 19
Oracle Alert User Guide This manual explains how to define
periodic and event alerts to monitor the status of your Oracle
Applications data. Multiple Reporting Currencies in Oracle
Applications If you use the Multiple Reporting Currencies feature
to report and maintain accounting records in more than one
currency, use this manual before implementing Oracle Inventory.
This manual details additional steps and setup considerations for
implementing Oracle Inventory with this feature. Multiple
Organizations in Oracle Applications If you use the Oracle
Applications Multiple Organization Support feature to use multiple
sets of books for one Oracle Inventory installation, use this guide
to learn about setting up and using Oracle Inventory with this
feature. This book describes the Oracle Applications organization
model, which defines business units and the relationships between
them in an arbitrarily complex enterprise. Functional and technical
overviews of multiple organizations are presented, as well as
information about how to set up and implement this feature set in
the relevant Oracle Applications products. Oracle Manufacturing,
Distribution, Sales and Service Open Interfaces Manual This manual
contains uptodate information about integrating with other Oracle
Manufacturing applications and with your other systems. This
documentation includes open interfaces found in Oracle
Manufacturing. Oracle Applications Messages Manual The Oracle
Applications Messages Manual contains the text of numbered error
messages in Oracle Applications. (Oracle Applications messages
begin with the prefix APP.) It also provides information on the
actions you take if you get a message. Note: This manual is
available only in HTML format.
Oracle Proprietary, Confidential InformationUse Restricted by
Contract1 10 Oracle Inventory Technical Reference Manual
Installation and System AdministrationOracle Applications
Installation Release Notes This manual contains a road map to the
components of the release, including instructions about where to
access the Release 11i documentation set. Oracle Applications
Concepts Designed to be the first book the user reads to prepare
for an installation of Oracle Applications. It explains the
technology stack, architecture, features and terminology for Oracle
Applications Release 11i. This book also introduces the concepts
behind and major uses of Applicationswide features such as MRC,
BIS, languages and character sets (NLS, MLS), BIS, SelfService Web
Applications and so on. Installing Oracle Applications Describes
the OneHour Install process, the method by which Release 11i will
be installed. This manual includes all howto steps, screen shots
and information about Applicationswide postinstall tasks. Using the
AD Utilities This manual contains howto steps, screen shots and
other information required to run the various AD utilities such as
AutoInstall, AutoPatch, AD Administration, AD Controller, Relink
and so on. It also contains information about when and why you
should use these utilities. Upgrading Oracle Applications This
manual contains all the product specific pre and postupgrade steps
that are required to upgrade products from Release 10.7 (NCA, SC
and charactermode) or Release 11 of Oracle Applications. This
manual also contains an overview chapter that describes all the
tasks necessary to prepare and complete a upgrade of Oracle
Applications. Oracle Applications System Administrators Guide This
manual provides planning and reference information for the Oracle
Applications System Administrator. It contains information on how
to define security, customize menus and manage concurrent
processing.Oracle Proprietary, Confidential InformationUse
Restricted by ContractIntroduction 1 11
Oracle Applications Product Update Notes This book contains a
summary of each new feature we added since Release 11, as well as
information about database changes and seed data changes that may
affect your operations or any custom reports you have written. If
you are upgrading from Release 10.7 you also need to read Oracle
Applications Product Update Notes Release 11. Oracle SelfService
Web Applications Implementation Manual This manual describes the
setup steps for Oracle SelfService Web Applications and the Web
Applications Dictionary. Oracle Applications Implementation Wizard
User Guide If you are implementing more than one Oracle product,
you can use the Oracle Applications Implementation Wizard to
coordinate your setup activities. This guide describes how to use
the wizard.
Other InformationTraining Oracle Education offers a complete set
of training courses to help you and your staff master Oracle
Applications. We can help you develop a training plan that provides
thorough training for both your project team and your end users. We
will work with you to organize courses appropriate to your job or
area of responsibility. Training professionals can show you how to
plan your training throughout the implementation process so that
the right amount of information is delivered to key people when
they need it the most. You can attend courses at any one of our
many Educational Centers, or you can arrange for our trainers to
teach at your facility. In addition, we can tailor standard courses
or develop custom courses to meet your needs. Support From onsite
support to central support, our team of experienced professionals
provides the help and information you need to keep Inventory
working for you. This team includes your Technical Representative,
Account Manager, and Oracles large staff of consultants and support
specialists with expertise in your businessOracle Proprietary,
Confidential InformationUse Restricted by Contract1 12 Oracle
Inventory Technical Reference Manual
area, managing an Oracle server, and your hardware and software
environment.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractIntroduction 1 13
About OracleOracle Corporation develops and markets an
integrated line of software products for database management,
applications development, decision support, and office automation,
as well as Oracle Applications, an integrated suite of more than 75
software modules for financial management, supply chain management,
manufacturing, project systems, human resources, and sales and
service management. Oracle products are available for mainframes,
minicomputers, personal computers, network computers, and personal
digital assistants, allowing organizations to integrate different
computers, different operating systems, different networks, and
even different database management systems, into a single, unified
computing and information resource. Oracle is the worlds leading
supplier of software for information management, and the worlds
second largest software company. Oracle offers its database, tools,
and applications products, along with related consulting,
education, and support services, in over 145 countries around the
world.
Thank YouThanks for using Oracle Inventory and this technical
reference manual! We appreciate your comments and feedback. At the
back of this manual is a Readers Comment Form that you can use to
explain what you like or dislike about Inventory or this technical
reference manual. Mail your comments to the following address or
call us directly at (650) 5067000. Oracle Applications
Documentation Manager Oracle Corporation 500 Oracle Parkway Redwood
Shores, California 94065 U.S.A. Or, send electronic mail to
[email protected].
Oracle Proprietary, Confidential InformationUse Restricted by
Contract1 14 Oracle Inventory Technical Reference Manual
CHAPTER
2
HighLevel Design
T
his chapter presents a highlevel design for Oracle Inventory
that satisfies the business needs we specify during Strategy and
Analysis. It contains database diagrams for Oracle Inventory
application building blocks, lists of database tables and views,
and a list of modules.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 21
Overview of HighLevel DesignDuring HighLevel Design, we define
the application components (tables, views, and modules) we need to
build our application. We specify what application components
should do without specifying the details of how they should do it.
You can refer to this HighLevel Design chapter to quickly acquaint
yourself with the tables, views, and modules that comprise Oracle
Inventory applications. And, you can prepare yourself to understand
the detailed design and implementation of Oracle Inventory.
Summary Database DiagramThe Summary Database Diagram section
graphically represents the most important application tables and
the relationships between them. It omits tables and relationships
that contribute little to the understanding of the application data
model. Typically, a summary database diagram shows tables that
contain key reference and transaction data. We prepare a summary
database diagram to describe, at a conceptual level, the key
information on which our business depends. Later, we refine this
summary database diagram, breaking it into multiple database
diagrams (generally, one per application building block) to
represent all the tables and relationships we need to implement our
application in the database. Review the Summary Database Diagram
section to see at a glance the major tables and relationships on
which your Oracle Inventory application depends.
Database DiagramsThe Database Diagrams section graphically
represents all Oracle Inventory applications tables and the
relationships between them, organized by building block. Use this
section to quickly learn what tables each Oracle Inventory
application building block uses, and how those tables interrelate.
Then, you can refer to the Table and View Definitions sections of
Chapter 3 for more detailed information about each of those
tables.Oracle Proprietary, Confidential InformationUse Restricted
by Contract22 Oracle Inventory Technical Reference Manual
Table ListsThe Table List sections list the Oracle Inventory
applications tables. Because a product might not include at least
one table for each type, this Technical Reference Manual might not
include each of the following sections. Public Tables Use the
Public Table List section to quickly identify the tables you are
most interested in. Then, you can refer to the Table and View
Definitions sections of Chapter 3 for more detailed information
about those tables. In addition, this manual may contain full
documentation for one or more of the following Application Object
Library tables: FND_DUAL, FND_CURRENCIES, and FND_COMMON_LOOKUPS.
Internal Tables This section includes a list of private, internal
tables used by Oracle Inventory; we do not provide additional
documentation for these tables.
View ListsThe View List sections list the Oracle Inventory
views, with one section for each type of view. Because a product
might not include at least one view for each type, this Technical
Reference Manual might not include each of the following sections.
Use this section to quickly identify the views you are most
interested in. Then, you can refer to the Table and View
Definitions sections of Chapter 3 for more detailed information
about those views. Public Views This section lists views that may
be useful for your custom reporting or other data requirements. The
list includes a description of the view, and the page in Chapter 3
that gives detailed information about the public view.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 23
Web Views This section lists views that you may need to
configure your SelfService Web applications. The list includes a
description of the view, and the page in Chapter 3 that gives
detailed information about the web view. Internal Views This
section includes each private, internal view that Oracle Inventory
uses. SingleOrganization Views This section lists the Oracle
Inventory views that we added to take the place of various tables
that are now partitioned by operating unit, to support multiple
sets of books within a single installation of Oracle Inventory.
Multiple Reporting Currency Views This list includes views that
were created to support the Multiple Reporting Currencies
feature.
Module ListThe Module List section briefly describes each of the
Oracle Inventory applications modules. This section lists forms,
reports, and concurrent programs. A form is a module comprised of
closely related windows that are used together to perform a task.
For example, the Enter Journals form in Oracle General Ledger
includes the Enter Journals window, the Batch window, and the More
Actions window. The Enter Journals window is the main window, and
from it, you can use buttons to navigate to other windows in the
form. The form name usually corresponds to the main window in the
form, and is frequently a window you can open directly from the
Navigator. The Reports and Concurrent Programs lists include
processes you can submit from the Submit Requests window or other
windows, as well as processes that are submitted automatically by
Oracle Inventory. Use your users guide to learn more about reports
and concurrent processes.Oracle Proprietary, Confidential
InformationUse Restricted by Contract24 Oracle Inventory Technical
Reference Manual
Summary Database DiagramThis Summary Database Diagram
graphically represents the most important Oracle Inventory
applications tables and the relationships between them. It
describes, at a conceptual level, the key information on which your
Oracle Inventory application depends. This diagram does not
represent the complete database implementation of Oracle Inventory
applications tables. It shows tables that contain key reference and
transaction data, and omits tables and relationships that
contribute little to the understanding of the Oracle Inventory
applications data model. For example, a foreign key relationship
shown between two tables may actually be implemented by an
intervening table, not shown in this diagram. For more detailed
graphical representations of Oracle Inventory applications tables
and the relationships between them, see the Database Diagrams
section in this chapter.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 25
Database Diagramming ConventionsWe use the following notational
conventions in our database diagrams:Figure 2 1 Database Diagram
Conventions
Server Model Diagram Elements and Notation
Recursive foreign key (Pig's Ear)
Title Bar Column/attribute details section Relational Table
Foreign key constraint
Arc
EMPPrimary key column (#*) Mandatory column (*)
# * EMPNO * DEPTNO
Delete rule indicator
DEPTValues in the foreign key must match the primary key
# * DEPTNO * DNAME
Mandatory and Optional Foreign KeysA value entered in the column
in the foreign key must match a value in the primary key column. 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 Proprietary, Confidential InformationUse Restricted by
Contract26 Oracle Inventory Technical Reference Manual
Tables are the basic unit of storage in the database. A hand
symbol preceding the title in the tables title bar indicates that
the table is not owned by this application but shared with another.
Foreign key constraint is a type of referential integrity
constraint for checking the integrity of data entered in a specific
column or set of columns. This specified column or set of columns
is known as the foreign key. 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. Arcs 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.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 27
Database DiagramsThis section graphically represents all Oracle
Inventory tables and the relationships between them, organized by
building block. Use this section to quickly learn what tables each
Oracle Inventory application building block uses, and how these
tables interrelate. Then, you can refer to the Table and View
Definitions sections of Chapter 3 for more detailed information
about each of those tables. This section contains a database
diagram for each of the following Oracle Inventory application
building blocks: Diagram 1 Diagram 2 Diagram 3: Diagram 4: Diagram
5: Diagram 6: Diagram 7: Diagram 8 Diagram 9: Diagram 10: Diagram
11: Diagram 12 Diagram 13 Diagram 14 Diagram 15 Diagram 16 Diagram
17 Diagram 18 Diagram 29 Diagram 20 Diagram 21 Inventory
Organization Parameters Inventory Setup Units of Measure Item
Categories Item Catalog Item Master Transaction Setup Ship Methods
Miscellaneous Transactions Subinventory Transfer Transactions
InterOrganization Transfer Transactions Available to Promise Demand
and Reservation Kanban ABC Analysis Physical Inventory Cycle Count
Inventory Replenishment Serial Genealogy Move Orders Material
Shortage Messages
Oracle Proprietary, Confidential InformationUse Restricted by
Contract28 Oracle Inventory Technical Reference Manual
Some tables, especially important reference tables, appear in
more than one database diagram. When several functional areas use a
table, we show that table in each appropriate database diagram.
Inventory Organization Parameters Diagram 1 shows the tables and
relationships that Inventory uses to define inventory organization
parameters. Inventory Setup Diagram 2 shows the tables and
relationships used in setting up Inventory. Units of Measure
Diagram 3 represents the tables and relationships in which
Inventory maintains information pertaining to units of measure, as
well as the conversion factors used to convert quantities from one
unit of measure to another. Note that conversions between units of
measure in different classes are carried out in three steps. (1)
The quantity in terms of the source unit of measure is converted to
a quantity in terms of the base unit of measure in its class using
a conversion factor in MTL_UOM_CONVERSIONS. (2) The sources base
UOM quantity is converted to a quantity in terms of the
destinations base UOM using a conversion factor in
MTL_UOM_CLASS_CONVERSION. (3) The destinations base UOM quantity is
converted to the final destination UOM quantity using a conversion
factor in MTL_UOM_CONVERSIONS. Item Categories Diagram 4 shows the
tables and relationships that Inventory uses to maintain category
information for items. Note that each item may be assigned to a
single category within a category set but may be assigned to many
category sets. A category set may be restricted to a list of valid
categories using the table MTL_CATEGORY_SET_VALID_CATS.
Additionally, functional areas (i.e. Inventory, Purchasing), etc.)
may have default category sets defined. Each item used by the
functional area will be assigned to (at least) that default
category set. Item Catalog Diagram 5 shows the tables and
relationships that Inventory uses to implement the Item Catalog.
Each catalog group is defined inOracle Proprietary, Confidential
InformationUse Restricted by ContractHighLevel Design 29
MTL_ITEM_CATALOG_GROUPS. The descriptive elements associated
with the catalog group are defined in MTL_DESCRIPTIVE ELEMENTS. The
values of those descriptive elements for each item assigned to the
catalog group are stored in MTL_DESCR_ELEMENT_VALUES. Recommended
aliases and recommended categories to be used with the items
assigned to a catalog group are stored in MTL_ICG_ALIASES and
MTL_ICG_CATEGORIES. Item Master Diagram 6 shows the tables and
relationships through which Inventory implements the Item Master.
Each item attribute for which the user may enter a value is defined
in MTL_ITEM_ATTRIBUTES. Many attributes may only be set when a
specific application is installed. These dependencies are defined
in MTL_ATTR_APPL_DEPENDENCIES. This diagram also indicates the
relationship between an item status, the status attribute values
and a pending status for an item. Transaction Setup Diagram 7 shows
the tables and relationships that Inventory uses to maintain both
predefined transaction source types and transaction types and
userdefined transaction source types and transaction types.
Transaction source types are stored in MTL_TXN_SOURCE_TYPES.
Transaction types are stored in MTL_TRANSACTION_TYPES. The
relationship indicates that predefined transaction types will be
defined with a predefined transaction source type. Userdefined
transaction types may have either a predefined source type or a
userdefined source type. The transaction action for a transaction
type is defined as a lookup in MFG_LOOKUPS. Ship Methods Diagram 8
shows the tables and relationships that Inventory uses to define
interorganization shipping methods. Miscellaneous Transactions
Diagram 9 shows the tables and relationships Inventory uses to
perform miscellaneous issues to and receipts from accounts. Not
that one account of the debit/credit distribution account pair is
that associated with the subinventory of the material being
transacted. TheOracle Proprietary, Confidential InformationUse
Restricted by Contract2 10 Oracle Inventory Technical Reference
Manual
other distribution account is specified at the time of the
transaction by the user. Subinventory Transfer Transactions Diagram
10 shows the tables and relationships through which Inventory
performs subinventory transfer transactions. The transaction may be
performed as either a predefined transaction type or userdefined
transaction type. Note that each subinventory transfer is carried
out as two separate transactions, creating two records in
MTL_MATERIAL_TRANSACTIONS. The first record represents an issue
from the source subinventory, and the second record is a receipt by
the destination subinventory. Only the subinventories and locators
can differ between the two transactions. Inventory derives the
debit distribution account from the transacted materials source
subinventory and the credit account from the materials destination
subinventory. InterOrganization Transfer Transactions Diagram 11
shows the tables and relationships Inventory uses to transact
interorganization transfers. Note that each direct
interorganization transfer is carried out as two separate
transactions, creating two records in MTL_MATERIAL_TRANSACTIONS.
One record represents and issue from the source organization, and
the other record is a receipt by the destination organization.
Revision, lot numbers and serial numbers must be identical in both
issue and receipt transactions for direct transfers. Note that
intransit transfers will also generate a record in
RCV_SHIPMENT_HEADERS and receipt will generate receiving
transaction. Available to Promise Diagram 12 shows the tables and
relationships in which Inventory holds information used in
compiling Available to Promise information. Tables that store
supply information include MTL_ONHAND_QUANTITIES, MTL_SUPPLY,
MTL_MATERIAL_TRANSACTIONS_TEMP, MRP_SCHEDULE_DATES,
MTL_USER_SUPPLY, WIP_REPETITIVE_SCHEDULES, and WIP_DISCRETE_JOBS.
Demand information comes from MTL_DEMAND,
WIP_REQUIREMENT_OPERATIONS and MTL_USER_DEMAND.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 11
Demand and Reservation Diagram 13 shows the tables and
relationships that Inventory uses to maintain demand and
reservation information. Note that Inventory writes a unique sales
order identifier into MTL_SALES_ORDERS after entry of demand from
the new sales order into MTL_DEMAND or MTL_DEMAND_INTERFACE. Also,
demand and reservations from sales orders are either automatically
entered by Oracle Order Entry (if the reservation is placed online)
or loaded from MTL_DEMAND_INTERFACE, where external demand may be
defined. Inventory adjusts reservation information in MTL_DEMAND
after execution of material transactions. Kanban Diagram 14 shows
the tables and relationships Inventory uses to enter and maintain
kanban cards for kanban supply locations and to define
replenishment chains, called pull sequences, for these locations.
ABC Analysis Diagram 15 represents the tables and relationships
that define and maintain ABC classifications for Inventory. The ABC
compile header in MTL_ABC_COMPILE_HEADERS identifies the criteria
used for the compile. The results of the compile are stored in
MTL_ABC_COMPILES. Items are assigned to ABC assignment groups,
which combine a set of ABC classes and (optionally) an ABC compile.
Physical Inventory Diagram 16 represents the tables and
relationships that Inventory uses to perform physical inventory
adjustments. Cycle Count Diagram 17 shows the tables and
relationships that Inventory uses to perform cycle count scheduling
and adjustments. A cycle count may use an ABC analysis as a basis
for classifying an item or items may be assigned directly to a
cycle count class. Schedule requests, both manual and automatic,
are stored in MTL_CC_SCHEDULE_REQUESTS and the count requests
generated from them are stored in MTL_CYCLE_COUNT_ENTRIES.
Adjustments based on those entries are written toOracle
Proprietary, Confidential InformationUse Restricted by Contract2 12
Oracle Inventory Technical Reference Manual
MTL_MATERIAL_TRANSACTIONS when approved by the user if approval
is require or when entered if no approval is required. Inventory
Replenishment Diagram 18 shows the tables and relationships that
Inventory uses to maintain subinventory replenishment information.
Suppose you want to write a custom application to generate cycle
counts based on item and location rather than item. To see how
cycle count requests are generated, you turn to Diagram 3 to see
the table structure for cycle counting. You see that
MTL_CC_SCHEDULE_REQUESTS holds the requested counts for cycle count
items, subinventories, lots, item revisions, and locators. Turning
to the Table and View Definitions section in Chapter 3, you learn
that schedule requests partially or fully specify the SKUs to cycle
count. By inserting the subinventory and locators that you want to
count into MTL_CC_SCHEDULE_REQUESTS, the cycle count generation
process explodes the count requests that fully specify the SKUs to
be counted. The MTL_CC_SCHEDULE_REQUESTS definition gives you the
column names that you need to update with your custom application.
To generate cycle counts by location, create a custom application
that selects the subinventory and locators to be counted, then
insert the subinventory, locator, and additional cycle count
information into MTL_CC_SCHEDULE_REQUESTS. Serial Genealogy Diagram
19 shows the tables and relationships that Inventory uses to build
serial genealogy. Move Orders Diagram 20 shows the tables and
relationships that Inventory uses to create and transact move
orders. Material Shortage Messages Diagram 21 shows the tables and
relationships that Inventory uses to generate material shortage
messages.
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 13
How to Use These Database DiagramsHere is an example of how you
might use these database diagrams: Suppose you want to write a
custom application to generate cycle counts based on item and
location rather than item. To see how cycle count requests are
generated, you turn to Diagram 3 to see the table structure for
cycle counting. You see that MTL_CC_SCHEDULE_REQUESTS holds the
requested counts for cycle count items, subinventories, lots, item
revisions, and locators. Turning to the Table and View Definitions
section in Chapter 3, you learn that schedule requests partially or
fully specify the SKUs to cycle count. By inserting the
subinventory and locators that you want to count into
MTL_CC_SCHEDULE_REQUESTS, the cycle count generation process
explodes the count requests that fully specify the SKUs to be
counted. The MTL_CC_SCHEDULE_REQUESTS definition gives you the
column names that you need to update with your custom application.
To generate cycle counts by location, create a custom application
that selects the subinventory and locators to be counted, then
insert the subinventory, locator, and additional cycle count
information into MTL_CC_SCHEDULE_REQUESTS.
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 14 Oracle Inventory Technical Reference Manual
Diagram 1: Inventory Organization Parameters
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 15
Diagram 2: Inventory Setup
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 16 Oracle Inventory Technical Reference Manual
Diagram 3: Units of Measure
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 17
Diagram 4: Item Categories
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 18 Oracle Inventory Technical Reference Manual
Diagram 5: Item Catalog
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 19
Diagram 6: Item Master
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 20 Oracle Inventory Technical Reference Manual
Diagram 7: Transaction Setup
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 21
Diagram 8: Ship Methods
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 22 Oracle Inventory Technical Reference Manual
Diagram 9: Miscellaneous Transactions
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 23
Diagram 10: Subinventory Transfer Transactions
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 24 Oracle Inventory Technical Reference Manual
Diagram 11: InterOrganization Transfer Transactions
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 25
Diagram 12: Available to Promise
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 26 Oracle Inventory Technical Reference Manual
Diagram 13: Demand and Reservation
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 27
Diagram 14: Kanban
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 28 Oracle Inventory Technical Reference Manual
Diagram 15: ABC Analysis
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 29
Diagram 16: Physical Inventory
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 30 Oracle Inventory Technical Reference Manual
Diagram 17: Cycle Count
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 31
Diagram 18: Inventory Replenishment
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 32 Oracle Inventory Technical Reference Manual
Diagram 19: Serial Genealogy
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 33
Diagram 20: Move Orders
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 34 Oracle Inventory Technical Reference Manual
Diagram 21: Material Shortage Messages
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 35
Public Table ListThis section lists each public database table
that Oracle Inventory uses and provides a brief description of each
of those tables. The page reference is to the table description in
Chapter 3. Note that public tables are not necessarily intended for
write access by custom code; Oracle Corporation supports write
access using only standard Oracle Applications forms, reports, and
programs, or any SQL write access to tables explicitly documented
as API tables. For more information, see the How Not To Use This
Manual section of this books Introduction. Oracle Inventory uses
the following Public tables: Table NameAP_INVOICES_ALL
AP_TAX_CODES_ALL AR_LOCATION_COMBINATIONS AR_VAT_TAX_ALL_B
Description Detailed invoice records (See page 3 7) Tax code
information (See page 3 15) Defines each distinct tax authority
(See page 3 18) Tax codes defined in the Tax Codes and Rates window
(See page 3 21) Bills of material (See page 3 25) Workday calendars
(See page 3 28) Workday calendar dates (See page 3 30) Workday
calendar weekly start dates (See page 3 32) Workday calendar yearly
start dates (See page 3 33) Deleted entities in BOM and INV (See
page 3 34) Errors occurring when deleting entities (See page 3 36)
Delete groups of BOM and INV entities (See page 3 37) SQL
statements used to check and delete entities (See page 3 39)
Component and operations to be deleted (See page 3 41) Resources
associated with departments (See page 3 43) Exception sets (See
page 3 45)
BOM_BILL_OF_MATERIALS BOM_CALENDARS BOM_CALENDAR_DATES
BOM_CAL_WEEK_START_DATES BOM_CAL_YEAR_START_DATES
BOM_DELETE_ENTITIES BOM_DELETE_ERRORS BOM_DELETE_GROUPS
BOM_DELETE_SQL_STATEMENTS
BOM_DELETE_SUB_ENTITIES BOM_DEPARTMENT_RESOURCES
BOM_EXCEPTION_SETS
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 36 Oracle Inventory Technical Reference Manual
BOM_INVENTORY_COMPONENTS BOM_OPERATIONAL_ROUTINGS
BOM_OPERATION_RESOURCES BOM_OPERATION_SEQUENCES BOM_PARAMETERS
BOM_PERIOD_START_DATES BOM_RESOURCES
Bill of material components (See page 3 46) Routings (See page 3
51) Resources on operations (See page 3 54) Routing operations (See
page 3 56) Bills of material parameters (See page 3 59) Workday
calendar period start dates (See page 3 61) Resources, overheads,
material cost codes, and material overheads (See page 3 62)
Substitute components (See page 3 65) Resource availability
information (See page 3 67) Activity definition associated with
activity costing (See page 3 69) Cost elements definition (See page
3 71) Stores cost group definitions (See page 3 72) Stores cost
type definitions (See page 3 74) Cost update history (See page 3
76) Item cost summary (See page 3 78) Interface table for item cost
(See page 3 80) Item cost detail information (See page 3 82)
Interface table for item cost detail information (See page 3 85)
Stores the item cost and quantity in a period and organization cost
group. (See page 3 88) Holds information about periodic costing
open and closed periods for each legal entity. (See page 3 90)
Standard cost history (See page 3 91) (See page 3 95) (See page 3
98)
BOM_SUBSTITUTE_COMPONENTS CRP_AVAILABLE_RESOURCES
CST_ACTIVITIES
CST_COST_ELEMENTS CST_COST_GROUPS CST_COST_TYPES
CST_COST_UPDATES CST_ITEM_COSTS CST_ITEM_COSTS_INTERFACE
CST_ITEM_COST_DETAILS CST_ITEM_CST_DTLS_INTERFACE
CST_PAC_ITEM_COSTS
CST_PAC_PERIODS
CST_STANDARD_COSTS EDW_CST_COGS_F EDW_CST_COGS_FSTG
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 37
EDW_MTL_UOM_CLS_CONV_F EDW_MTL_UOM_CLS_CONV_FSTG
EDW_MTL_UOM_CONV_F EDW_MTL_UOM_CONV_FSTG ENG_ECN_APPROVAL_LISTS
ENG_ENGINEERING_CHANGES ENG_REVISED_ITEMS FA_CATEGORIES_B
(See page 3 101) (See page 3 102) (See page 3 104) (See page 3
105) Engineering change order approval lists (See page 3 107)
Engineering change orders (See page 3 108) Pending and implemented
revised items (See page 3 110) Default financial information for
asset categories (base MLS table) (See page 3 113) Systemwide
controls that affect all assets (See page 3 116) Oracle Financials
system parameters and defaults (See page 3 117) Applications
registered with Oracle Application Object Library (No table
definition) Concurrent requests information(No table definition)
Currencies enabled for use at your site (See page 3 123) ORACLE
accounts for applications assigned to various data groups (No table
definition) Structure names for descriptive flexfields (No table
definition) Dummy base table used by a form block that does not
have a real base table (for commit purposes) (See page 3 126) Valid
values for flexfield segments (No table definition) Value sets used
by both key and descriptive flexfields (No table definition) Key
flexfield segments setup information and correspondences between
table columns and key flexfield segments (No table definition) Key
flexfield structure information (No table definition)
FA_SYSTEM_CONTROLS FINANCIALS_SYSTEM_PARAMS_ALL
FND_APPLICATION
FND_CONCURRENT_REQUESTS FND_CURRENCIES FND_DATA_GROUP_UNITS
FND_DESCR_FLEX_CONTEXTS
FND_DUAL
FND_FLEX_VALUES FND_FLEX_VALUE_SETS
FND_ID_FLEX_SEGMENTS
FND_ID_FLEX_STRUCTURES
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 38 Oracle Inventory Technical Reference Manual
FND_PRODUCT_DEPENDENCIES
Dependencies of Oracle Applications products installed at your
site (No table definition) Oracle Applications products installed
at your site (No table definition) User profile options (No table
definition) Values of user profile options defined at different
profile levels (No table definition) Responsibilities (No table
definition) Territories, also known as countries (No table
definition) Application users (No table definition) Account
combinations (See page 3 127) Foreign currency daily conversion
rate types (See page 3 131) Encumbrance type definitions (See page
3 132) Import journal entry batches (See page 3 133) Journal entry
categories (See page 3 137) Journal entry sources (See page 3 138)
Calendar period definitions (See page 3 140) Calendar definitions
(See page 3 142) Set of books definitions (See page 3 143)
Organization unit definitions. (See page 3 146) Work location
definitions. (See page 3 149) Additional attributes of an
organization, dependent on class or organization information type.
(See page 3 152) Plan names (See page 3 155) Forecast entries (See
page 3 157) Forecast names and sets (See page 3 161) Items in a
forecast (See page 3 163)
FND_PRODUCT_INSTALLATIONS
FND_PROFILE_OPTIONS FND_PROFILE_OPTION_VALUES
FND_RESPONSIBILITY FND_TERRITORIES FND_USER GL_CODE_COMBINATIONS
GL_DAILY_CONVERSION_TYPES
GL_ENCUMBRANCE_TYPES GL_INTERFACE GL_JE_CATEGORIES_TL
GL_JE_SOURCES_TL GL_PERIODS GL_PERIOD_SETS GL_SETS_OF_BOOKS
HR_ALL_ORGANIZATION_UNITS HR_LOCATIONS_ALL
HR_ORGANIZATION_INFORMATION
MRP_DESIGNATORS MRP_FORECAST_DATES MRP_FORECAST_DESIGNATORS
MRP_FORECAST_ITEMS
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 39
MRP_GROSS_REQUIREMENTS MRP_PARAMETERS
MRP_PLANNING_EXCEPTION_SETS MRP_PLANS MRP_RECOMMENDATIONS
MRP_RELIEF_INTERFACE
Gross requirements (See page 3 165) Planning parameters (See
page 3 168) Controls for a set of exception messages (See page 3
171) Settings for a specific plan name (See page 3 174) MRP plan
recommendations (See page 3 180) Interface table to relieve the
master schedule tables (See page 3 187) Master production schedule
and master demand schedule (See page 3 190) Schedule names (See
page 3 194) Master scheduled items (See page 3 196) Assigns abc
classes to abc groups (See page 3 198) Assigns items to abc classes
in an abc group (See page 3 200) Defines abc groups (See page 3
201) Inventory ABC classes (See page 3 203) ABC descending value
compile data (See page 3 204) ABC compile header data (See page 3
205) Stores the material overhead subelements (See page 3 208) ATP
computation rules (See page 3 209) Dependencies between item
attributes and Oracle products (See page 3 213) BIS table that
stores inventory turns data by organization, accounting period and
Inventory item id for open periods and closed periods (See page 3
214) Items returned by item searches (See page 3 215) Code
combinations table for item categories (See page 3 216) Categories
table holding translated Description column for Item Categories
(See page 3 218)
MRP_SCHEDULE_DATES
MRP_SCHEDULE_DESIGNATORS MRP_SCHEDULE_ITEMS
MTL_ABC_ASSGN_GROUP_CLASSES MTL_ABC_ASSIGNMENTS
MTL_ABC_ASSIGNMENT_GROUPS MTL_ABC_CLASSES MTL_ABC_COMPILES
MTL_ABC_COMPILE_HEADERS MTL_ACTUAL_COST_SUBELEMENT MTL_ATP_RULES
MTL_ATTR_APPL_DEPENDENCIES
MTL_BIS_INV_BY_PERIOD
MTL_CATALOG_SEARCH_ITEMS MTL_CATEGORIES_B
MTL_CATEGORIES_TL
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 40 Oracle Inventory Technical Reference Manual
MTL_CATEGORY_ACCOUNTS
Asset and expense accounts by item category, by subinventory
(See page 3 219) Category Sets (See page 3 221) A table holding
translated Name and Description columns for Category Sets (See page
3 223) Valid categories for category sets (See page 3 224) Cycle
Count Entries Interface data (See page 3 225) Cycle Count Entries
Interface process errors (See page 3 230) Defines cycle count
schedule requests (See page 3 231) Cross references count entry
requests (See page 3 234) Serial Numbers for Cycle Count Entries.
(See page 3 235) Defines subinventories to be used in subinventory
level cycle count (See page 3 237) Customer Items Interface (See
page 3 238) Customer Items Cross References Interface (See page 3
244) Customer item commodity codes (See page 3 249) Stores
information concerning the assignment of countries to economic
zones. (See page 3 251) Assign cross references to items (See page
3 252) (not currently used) (See page 3 254) Define cross reference
types (See page 3 256) Actual cost information by element, by level
(See page 3 257) Cost of a transaction by element, by level (See
page 3 259) Customer item Information (See page 3 260)
Relationships between customer items and inventory items (See page
3 263)
MTL_CATEGORY_SETS_B MTL_CATEGORY_SETS_TL
MTL_CATEGORY_SET_VALID_CATS MTL_CC_ENTRIES_INTERFACE
MTL_CC_INTERFACE_ERRORS
MTL_CC_SCHEDULE_REQUESTS MTL_CC_SCHED_COUNT_XREFS
MTL_CC_SERIAL_NUMBERS MTL_CC_SUBINVENTORIES
MTL_CI_INTERFACE MTL_CI_XREFS_INTERFACE
MTL_COMMODITY_CODES MTL_COUNTRY_ASSIGNMENTS
MTL_CROSS_REFERENCES MTL_CROSS_REFERENCES_INTERFACE
MTL_CROSS_REFERENCE_TYPES MTL_CST_ACTUAL_COST_DETAILS
MTL_CST_TXN_COST_DETAILS MTL_CUSTOMER_ITEMS
MTL_CUSTOMER_ITEM_XREFS
MTL_CYCLE_COUNT_CLASSES Defines cycle count classes (See page 3
265) Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 41
MTL_CYCLE_COUNT_ENTRIES MTL_CYCLE_COUNT_HEADERS
MTL_CYCLE_COUNT_ITEMS MTL_DEFAULT_CATEGORY_SETS
Defines cycle count entries (See page 3 267) Defines cycle count
header information (See page 3 271) Defines items to be used in
cycle count (See page 3 275) Default category set for a particular
functional area (See page 3 277) Sales order demand and
reservations (See page 3 279) Sales order demand and reservations
(See page 3 285) Temporary demand storage for the transaction
processor (See page 3 287) Descriptive element definitions for an
item catalog group (See page 3 301) Stores the descriptive element
values for a particular item (See page 3 303) Not used currently
(See page 3 305) Stores information concerning all the economic
zones. (See page 3 306) Corresponding transalation table for
MTL_ECONOMIC_ZONES_B. (See page 3 307) External component
information of an inventory item (See page 3 308) Category account
definitions for legal entity (See page 3 310) Forecast rules for
forecast processes (See page 3 311) Account alias definition (See
page 3 314) Recommended item aliases for items in an item catalog
group (See page 3 316) Recommended item categories for items in an
item catalog group (See page 3 317) Intercompany relationships (See
page 3 318) Item open interface errors (See page 3 320)
MTL_DEMAND MTL_DEMAND_HISTORIES MTL_DEMAND_INTERFACE
MTL_DESCRIPTIVE_ELEMENTS
MTL_DESCR_ELEMENT_VALUES
MTL_DESC_ELEM_VAL_INTERFACE MTL_ECONOMIC_ZONES_B
MTL_ECONOMIC_ZONES_TL
MTL_EXT_OBJECTS
MTL_FISCAL_CAT_ACCOUNTS
MTL_FORECAST_RULES MTL_GENERIC_DISPOSITIONS MTL_ICG_ALIASES
MTL_ICG_CATEGORIES
MTL_INTERCOMPANY_PARAMETERS MTL_INTERFACE_ERRORS
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 42 Oracle Inventory Technical Reference Manual
MTL_INTERFACE_PROC_CONTROLS MTL_INTERORG_PARAMETERS
MTL_INTERORG_SHIP_METHODS
Interface Processes Control Parameters (See page 3 321)
Interorganization relationships (See page 3 323) Relationships
between shipping networks and shipment methods (See page 3 326)
Item attributes table (See page 3 328) Item catalog groups (See
page 3 331) Define item assignments to categories (See page 3 333)
Interface table for item categories; used internally by the item
open interface (See page 3 335) Not currently used (See page 3 337)
Definitions for stock locators (See page 3 339) Inventory item
receiving and shipping locator default values (See page 3 342) Item
revisions (See page 3 343) Item revisions interface (See page 3
345) Material status definitions (See page 3 347) Inventory item
receiving and shipping subinventory default values (See page 3 348)
Itemsubinventory assignments (See page 3 350) (currently not used)
(See page 3 352) Item template definitions (See page 3 355) Item
attributes and attribute values for a template (See page 3 357)
Kanban Cards (See page 3 363) Kanban Card Activity (See page 3 366)
Temporary table used to print kanban cards (See page 3 369) Kanban
Pull Sequences (See page 3 370)
MTL_ITEM_ATTRIBUTES MTL_ITEM_CATALOG_GROUPS MTL_ITEM_CATEGORIES
MTL_ITEM_CATEGORIES_INTERFACE
MTL_ITEM_CHILD_INFO_INTERFACE MTL_ITEM_LOCATIONS
MTL_ITEM_LOC_DEFAULTS
MTL_ITEM_REVISIONS MTL_ITEM_REVISIONS_INTERFACE MTL_ITEM_STATUS
MTL_ITEM_SUB_DEFAULTS
MTL_ITEM_SUB_INVENTORIES MTL_ITEM_SUB_INVS_INTERFACE
MTL_ITEM_TEMPLATES MTL_ITEM_TEMPL_ATTRIBUTES
MTL_KANBAN_CARDS MTL_KANBAN_CARD_ACTIVITY
MTL_KANBAN_CARD_PRINT_TEMP
MTL_KANBAN_PULL_SEQUENCES
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 43
MTL_LE_ECONOMIC_ZONES
Stores information concerning the assignment of legal entity to
economic zones. (See page 3 373) Lot number definitions (See page 3
374) Define manufacturers (See page 3 376) Material transaction
table (See page 3 377) Temporary table for processing material
transactions (See page 3 384) Unit allocations among repetitive
schedules (See page 3 390) Define manufacturer part numbers (See
page 3 391) Movement parameter values (See page 3 393) Stores all
relevant information for movement statistics transactions. (See
page 3 395) Major events that have occurred relevant to an object
(See page 3 401) Genealogy information about an object and its
parents (See page 3 402) FIFO quantities by control level and
receipt (See page 3 404) Temporary table for onhand quantity
queries (See page 3 406) Multiorganization inventory report
temporary table (See page 3 408) Stores the elemental cost for a
given transaction in a period (See page 3 409) Stores the material
overhead subelements that are charged for a given transaction in a
particular period. (See page 3 411) Transaction details for a
period (See page 3 412) Inventory control options and defaults (See
page 3 413) History of itemstatus assignments (See page 3 419)
MTL_LOT_NUMBERS MTL_MANUFACTURERS MTL_MATERIAL_TRANSACTIONS
MTL_MATERIAL_TRANSACTIONS_TEMP
MTL_MATERIAL_TXN_ALLOCATIONS
MTL_MFG_PART_NUMBERS MTL_MOVEMENT_PARAMETERS
MTL_MOVEMENT_STATISTICS
MTL_OBJECT_EVENTS
MTL_OBJECT_GENEALOGY
MTL_ONHAND_QUANTITIES
MTL_ONHAND_QUANTITY_TEMP
MTL_ORG_REPORT_TEMP
MTL_PAC_ACTUAL_COST_DETAILS
MTL_PAC_COST_SUBELEMENTS
MTL_PAC_TXN_COST_DETAILS MTL_PARAMETERS
MTL_PENDING_ITEM_STATUS
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 44 Oracle Inventory Technical Reference Manual
MTL_PERIOD_SUMMARY
Period summary inventory values for subinventories (See page 3
421) (See page 3 422) Physical inventory adjustments (See page 3
423) Physical inventory definitions (See page 3 425) Physical
inventory tag definitions (See page 3 427) Physical inventory
specific subinventories (See page 3 429) Picking Rule Definitions
(See page 3 430) Planner code definitions (See page 3 432)
Transaction history purges (See page 3 433) (not currently used)
(See page 3 434) (not currently used) (See page 3 435) (not
currently used) (See page 3 436) (not currently used) (See page 3
437) (not currently used) (See page 3 438) Item relationships (See
page 3 439) Not currently used (See page 3 441) Replenishment
header information (See page 3 443) Replenishment header interface
information (See page 3 446) Replenishment line information (See
page 3 449) Replenishment line interface information (See page 3
452) Reservations (See page 3 454) Reservations Interface (See page
3 457) Routing revisions (See page 3 464) Routing revisions
interface table (See page 3 466) Safety stocks (See page 3 468)
MTL_PER_CLOSE_DTLS MTL_PHYSICAL_ADJUSTMENTS
MTL_PHYSICAL_INVENTORIES MTL_PHYSICAL_INVENTORY_TAGS
MTL_PHYSICAL_SUBINVENTORIES MTL_PICKING_RULES MTL_PLANNERS
MTL_PURGE_HEADER MTL_QOH_ITEM_TMP MTL_QOH_LOCATOR_TMP
MTL_QOH_LOT_TMP MTL_QOH_REV_TMP MTL_QOH_SUB_TMP MTL_RELATED_ITEMS
MTL_RELATED_ITEMS_INTERFACE MTL_REPLENISH_HEADERS
MTL_REPLENISH_HEADERS_INT
MTL_REPLENISH_LINES MTL_REPLENISH_LINES_INT MTL_RESERVATIONS
MTL_RESERVATIONS_INTERFACE MTL_RTG_ITEM_REVISIONS
MTL_RTG_ITEM_REVS_INTERFACE MTL_SAFETY_STOCKS
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 45
MTL_SALES_ORDERS MTL_SEASONALITY_INDICES
MTL_SECONDARY_INVENTORIES MTL_SECONDARY_LOCATORS
MTL_SECONDARY_LOCS_INTERFACE MTL_SERIAL_NUMBERS
MTL_SERIAL_NUMBERS_INTERFACE
Local definitions of sales orders (See page 3 470) Seasonality
indices (See page 3 472) Subinventory definitions (See page 3 473)
Itemsubinventorylocator assignments (See page 3 476) (not currently
used) (See page 3 477) Serial number definitions (See page 3 479)
Temporary serial number storage for transactions processor (See
page 3 482) Temporary serial number holding table (See page 3 483)
Shortage Parameters (See page 3 484) Shortage Check Statements (See
page 3 488) Shortage Check Temporary Table (See page 3 489) THIS
TABLE IS OBSOLETE WITH THE NEW ORDER MANAGEMENT SYSTEM. IT IS USED
ONLY FOR DATA MIGRATION FROM THIS TABLE TO THE NEW ORDER MANAGEMENT
SYSTEM. RMA headers and lines for OE interface (Seepage 3 490) THIS
TABLE IS OBSOLETE WITH THE NEW ORDER MANAGEMENT SYSTEM. IT IS USED
ONLY FOR DATA MIGRATION FROM THIS TABLE TO THE NEW ORDER MANAGEMENT
SYSTEM. RMA receipt transactions (See page 2 46) Item status code
attribute values (See page 3 494) Stores information which
determines the statistical type data for each legal entity. (See
page 3 495) Transaction summaries (See page 3 496) Stores incoming
supply information (See page 3 497) Temporary table containing ATP
details returned from ATP userexit (See page 3 502) Inventory item
definitions (See page 3 505) Inventory items interface table (See
page 3 524)
MTL_SERIAL_NUMBERS_TEMP MTL_SHORT_CHK_PARAM
MTL_SHORT_CHK_STATEMENTS MTL_SHORT_CHK_TEMP
MTL_SO_RMA_INTERFACE
MTL_SO_RMA_RECEIPTS
MTL_STATUS_ATTRIBUTE_VALUES MTL_STAT_TYPE_USAGES
MTL_SUMMARY_TEMP MTL_SUPPLY MTL_SUPPLY_DEMAND_TEMP
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_INTERFACE
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 46 Oracle Inventory Technical Reference Manual
MTL_SYSTEM_ITEMS_TL
Translations table table holding item descriptions in multiple
languages (See page 3 539) Gateway for externally generated
material transactions (See page 3 540) Material transaction
distributions (See page 3 549) Temporary lot storage for
transaction processor (See page 3 552) Temporary lot numbers
holding table (See page 3 553) Transaction lot numbers (See page 3
555) Inventory Transaction Reasons Table (See page 3 556) Inventory
Transaction Types Table (See page 3 557) Stores transaction cost by
element and by level for transactions to be imported through the
transaction interface (See page 3 559) Move Order headers table
(See page 3 560) Move order lines table (See page 3 562) Valid
transaction source types (See page 3 565) Unit of measure
definitions (See page 3 567) Serial number transactions (See page 3
569) Unit of measure classes (See page 3 571) Conversions between
base units of two different classes (See page 3 572) Unit of
measure conversion table for both default and item specific
conversions (See page 3 574) External demand information to be
considered in ATP (See page 3 576) External supply information to
be considered in ATP (See page 3 578) Organization access rules
table (See page 3 580)
MTL_TRANSACTIONS_INTERFACE
MTL_TRANSACTION_ACCOUNTS MTL_TRANSACTION_LOTS_INTERFACE
MTL_TRANSACTION_LOTS_TEMP MTL_TRANSACTION_LOT_NUMBERS
MTL_TRANSACTION_REASONS MTL_TRANSACTION_TYPES
MTL_TXN_COST_DET_INTERFACE
MTL_TXN_REQUEST_HEADERS MTL_TXN_REQUEST_LINES
MTL_TXN_SOURCE_TYPES MTL_UNITS_OF_MEASURE_TL MTL_UNIT_TRANSACTIONS
MTL_UOM_CLASSES_TL MTL_UOM_CLASS_CONVERSIONS
MTL_UOM_CONVERSIONS
MTL_USER_DEMAND
MTL_USER_SUPPLY
ORG_ACCESS
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 47
ORG_ACCT_PERIODS
Organization accounting period definition table (See page 3 581)
Freight codes (See page 3 583) General Ledger transfer information
for each batch (See page 3 585) Cost Allocation key flexfield
combinations table. (See page 3 586) Implementationdefined
classifications of expenditures charged to projects and tasks (See
page 3 588) End Item Model/Unit Numbers (See page 3 590) Change
History of Serial Number Model/Unit Number Associations (See page 3
592) Buyers table (See page 3 593) Purchase order distributions
(See page 3 595) Hazardous classes (See page 3 602) Document
headers (for purchase orders, purchase agreements, quotations,
RFQs) (See page 3 604) Purchase document lines (for purchase
orders, purchase agreements, quotations, RFQs) (See page 3 612)
Document shipment schedules (for purchase orders, purchase
agreements, quotations, RFQs) (See page 3 618) Purchase order
releases (See page 3 626) Requisition Import interface table (See
page 3 631) Requisition headers (See page 3 639) Requisition lines
(See page 3 643) Purchasing options (See page 3 650) United Nations
numbers (See page 3 655) Suppliers (See page 3 657) Supplier sites
(See page 3 664)
ORG_FREIGHT_TL ORG_GL_BATCHES
PAY_COST_ALLOCATION_KEYFLEX
PA_EXPENDITURE_TYPES
PJM_UNIT_NUMBERS PJM_UNIT_SERIAL_HISTORY
PO_AGENTS PO_DISTRIBUTIONS_ALL PO_HAZARD_CLASSES_B
PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
PO_RELEASES_ALL PO_REQUISITIONS_INTERFACE_ALL
PO_REQUISITION_HEADERS_ALL PO_REQUISITION_LINES_ALL
PO_SYSTEM_PARAMETERS_ALL PO_UN_NUMBERS_B PO_VENDORS
PO_VENDOR_SITES_ALL
RA_ADDRESSES_ALL Customer address information (See page 3 669)
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 48 Oracle Inventory Technical Reference Manual
RA_CUSTOMERS RA_CUST_TRX_TYPES_ALL
Customer information (See page 3 674) Transaction type for
invoices, commitments and credit memos (See page 3 679) Invoicing
and accounting rules (See page 3 683) Information about salespeople
(See page 3 685) Business purpose of a customer address (See page 3
688) Payment Term information (See page 3 693) Territory
information (See page 3 695) Receiving lots interface table (See
page 3 697) Organizationlevel receiving controls (See page 3 698)
Receiving routing headers (See page 3 701) Receiving serial
interface table (See page 3 702) Shipment and receipt header
information (See page 3 703) Receiving shipment line information
(See page 3 707) Receiving transactions (See page 3 711) Receiving
transactions interface table (See page 3 717) Order header
information (See page 3 725) Order lines (See page 3 732) Order
types (See page 3 741) Price lists (See page 3 744) Requests to
process cost transactions (See page 3 746) Discrete jobs (See page
3 751) Information common to jobs and schedules (See page 3 757)
Work orderless flow schedules (See page 3 759) Production lines
(See page 3 763) Shop floor move transactions (See page 3 765)
RA_RULES RA_SALESREPS_ALL RA_SITE_USES_ALL RA_TERMS_B
RA_TERRITORIES RCV_LOTS_INTERFACE RCV_PARAMETERS
RCV_ROUTING_HEADERS RCV_SERIALS_INTERFACE RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES RCV_TRANSACTIONS RCV_TRANSACTIONS_INTERFACE
SO_HEADERS_ALL SO_LINES_ALL SO_ORDER_TYPES_115_ALL SO_PRICE_LISTS_B
WIP_COST_TXN_INTERFACE WIP_DISCRETE_JOBS WIP_ENTITIES
WIP_FLOW_SCHEDULES WIP_LINES WIP_MOVE_TRANSACTIONS
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 49
Forms and Table View ListThis section lists supplementary views
that are not essential to the Release 11i data model, but simplify
coding or improve performance of Developer/2000. For example, many
of these views are used as base tables in Oracle Inventory forms.
Warning: We do not recommend you query or alter data using these
views. Furthermore, these views may change dramatically in
subsequent minor or major releases of Oracle Inventory. Oracle
Inventory uses the following Forms and Table views: HR_EMPLOYEES
HR_EMPLOYEES_CURRENT_V HR_ORGANIZATION_UNITS
MTL_ABC_ASSGNMNT_GROUPS_ALL_V MTL_ABC_ASSGN_GROUP_CLASSES_V
MTL_ABC_ASSIGNMENTS_V MTL_ABC_ASSIGNMENT_GROUPS_V
MTL_ABC_CLASSES_ALL_V MTL_ABC_CLASSES_V MTL_ABC_CLASSES_VAL_V
MTL_ABC_COMPILES_V MTL_ABC_COMPILE_HEADERS_V
MTL_ALL_PRIMARY_UOMS_VV MTL_CATALOG_SEARCH_ITEMS_ALL_V
MTL_CATEGORIES_V MTL_CATEGORY_ACCOUNTS_V MTL_CATEGORY_SETS_V
MTL_CATEGORY_SET_VALID_CATS_V MTL_CC_SUBINVENTORIES_ALL_V
MTL_COMMODITY_CODES_ACTIVE_V MTL_COMMODITY_CODES_ALL_V
MTL_CROSS_REFERENCES_VOracle Proprietary, Confidential
InformationUse Restricted by Contract2 50 Oracle Inventory
Technical Reference Manual
MTL_CUSTOMER_ITEMS_ACTIVE_V MTL_CUSTOMER_ITEMS_ALL_V
MTL_CUSTOMER_ITEM_XREFS_V MTL_CYCLE_COUNT_CLASSES_ALL_V
MTL_CYCLE_COUNT_CLASSES_V MTL_CYCLE_COUNT_ENTRIES_ALL_V
MTL_CYCLE_COUNT_ENTRIES_V MTL_CYCLE_COUNT_HEADERS_ALL_V
MTL_CYCLE_COUNT_HEADERS_V MTL_CYCLE_COUNT_HEADERS_VAL_V
MTL_CYCLE_COUNT_ITEMS_ALL_V MTL_CYCLE_COUNT_ITEMS_V
MTL_DEFAULT_CATEGORY_SETS_FK_V MTL_DEMAND_HISTORY_V
MTL_DEMAND_INTERFACE_V MTL_DEMAND_V MTL_DESCR_ELEMENT_VALUES_V
MTL_DESCR_ELEM_VAL_V MTL_EMPLOYEES_CURRENT_VIEW MTL_EMPLOYEES_VIEW
MTL_INTERCOMPANY_PARAMETERS_V MTL_INTERFACE_PROC_CONTROLS_V
MTL_ITEM_ATTRIBUTES_V MTL_ITEM_ATTRIBUTE_NAMES_V
MTL_ITEM_ATTRIBUTE_VALUES_V MTL_ITEM_ATTR_APPL_INST_V
MTL_ITEM_ATTR_FIELDS_V MTL_ITEM_CATALOG_GROUPS_V
MTL_ITEM_CATEGORIES_V MTL_ITEM_CATEGORIES_VIEWOracle Proprietary,
Confidential InformationUse Restricted by ContractHighLevel Design
2 51
MTL_ITEM_FLEXFIELDS MTL_ITEM_ORG_CATEG_V MTL_ITEM_ORG_REV_V
MTL_ITEM_REVISIONS_ALL_V MTL_ITEM_SUB_AST_TRK_VAL_V
MTL_ITEM_SUB_EXP_VAL_V MTL_ITEM_SUB_INVENTORIES_ALL_V
MTL_ITEM_SUB_TRK_VAL_V MTL_ITEM_SUB_VAL_V MTL_ITEM_TEMPLATES_ALL_V
MTL_ITEM_TEMPL_ATTRIBUTES_V MTL_ITEM_UOMS_VIEW MTL_KANBAN_CARDS_V
MTL_KANBAN_CARD_ACTIVITY_V MTL_KANBAN_PULL_SEQUENCES_V
MTL_LOT_DEMAND_VAL_V MTL_LOT_ISSUES_VAL_V MTL_LOT_NUMBERS_ALL_V
MTL_MATERIAL_TXNS_VAL_V MTL_MFG_PART_NUMBERS_ALL_V
MTL_MOVEMENT_PARAMETERS_V MTL_ONHAND_ITEMS_V
MTL_ONHAND_LOCATOR_LOT_V MTL_ONHAND_LOCATOR_V MTL_ONHAND_LOT_V
MTL_ONHAND_REV_V MTL_ONHAND_SUB_V MTL_ORGANIZATIONS
MTL_ORG_ASSIGN_V MTL_ORG_REPORT_TEMP_FK_VOracle Proprietary,
Confidential InformationUse Restricted by Contract2 52 Oracle
Inventory Technical Reference Manual
MTL_PARAMETERS_VIEW MTL_PERIOD_SUMMARY_V
MTL_PHYSICAL_ADJUSTMENTS_V MTL_PHYSICAL_INVENTORIES_V
MTL_PHYSICAL_INVENTORY_TAGS_V MTL_PHYSICAL_SUBINVENTORIES_V
MTL_PRIMARY_UOMS_VV MTL_PROJECT_V MTL_QOH_ITEM_ALL_V
MTL_QOH_LOC_ALL_V MTL_QOH_LOT_ALL_V MTL_QOH_REV_ALL_V
MTL_QOH_SUB_ALL_V MTL_RELATED_ITEMS_ALL_V
MTL_REPLENISH_HEADERS_VIEW MTL_REPLENISH_LINES_VIEW
MTL_RESERVATIONS_ALL_V MTL_RESERVATIONS_INTERFACE_V
MTL_RESERVATIONS_V MTL_SAFETY_STOCKS_VIEW
MTL_SECONDARY_INVENTORIES_FK_V MTL_SECONDARY_LOCATORS_ALL_V
MTL_SERIAL_NUMBERS_ALL_V MTL_SERIAL_NUMBERS_VAL_V
MTL_SHIPPING_NETWORK_VIEW MTL_SHORT_SUMMARY_V
MTL_STAT_ATTRIB_VALUES_ALL_V MTL_SUBINVENTORIES_ALL_V
MTL_SUBINVENTORIES_TRK_VAL_V MTL_SUBINVENTORIES_VAL_VOracle
Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 53
MTL_SUB_AST_TRK_VAL_V MTL_SUB_EXP_VAL_V MTL_SUB_TRK_ALL_V
MTL_SUMMARY_TEMP_V MTL_SUPPLIER_SITES_V MTL_SYSTEM_ITEMS_FVL
MTL_TASK_V MTL_TRANSACTIONS_INTERFACE_V MTL_TRANSACTIONS_TEMP_ALL_V
MTL_TRANSACTION_LOT_VAL_V MTL_TRANSACTION_REASONS_VAL_V
MTL_TRAN_TYPES_SYS_VAL_VIEW MTL_TRAN_TYPES_USER_VAL_VIEW
MTL_TRX_TYPES_VIEW MTL_TXN_SOURCE_TYPES_ALL_V
MTL_TXN_SRC_FOR_TRAN_TYPE_VIEW MTL_UNITS_OF_MEASURE_VV
MTL_UNIT_TRANSACTIONS_ALL_V MTL_UOM_CONVERSIONS_VIEW
MTL_VENDOR_LOT_VIEW ORG_ACCESS_V ORG_ACCT_PERIODS_V
ORG_ENABLED_FREIGHT_VAL_V ORG_FREIGHT_CODE_ALL_V ORG_GL_BATCHES_V
ORG_ORGANIZATION_DEFINITIONS ORG_ORGANIZATION_DEFINITIONS2
PER_PEOPLE_X
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 54 Oracle Inventory Technical Reference Manual
Internal View ListThis section lists each private, internal view
that Oracle Inventory uses. Warning: Oracle Corporation does not
support access to Oracle Applications data using these views,
except from standard Oracle Applications forms, reports, and
programs. Oracle Inventory uses the following internal views:
CST_DETAIL_COSTS_FOR_GL_VIEW CST_ITEM_COSTS_FOR_GL_VIEW
CST_ITEM_COSTS_VIEW CST_PROJ_EXP_TYPES_VAL_V MTL_ATT_QTY_V
MTL_CATEGORIES_B_KFV MTL_CATEGORY_SETS_ALL_V MTL_CC_GRAPH_DAY_V
MTL_CC_GRAPH_MONTH_V MTL_CC_GRAPH_PERIOD_V MTL_CC_GRAPH_QTR_V
MTL_CC_GRAPH_V MTL_CC_GRAPH_WK_V MTL_CC_SCHEDULES_V
MTL_CROSS_REFERENCES_SRW_V MTL_CST_TXN_COST_DETAILS_V
MTL_DEFAULT_SETS_VIEW MTL_DEMAND_HISTORY_ITEMS_V
MTL_DEMAND_INTERFACE_VIEW MTL_DEMAND_OM_VIEW
MTL_FORECAST_DATES_COST_V MTL_GENERIC_DISPOSITIONS_KFV
MTL_GROSS_REQ_COST_V MTL_GROUP_ATPS_VIEW
MTL_GROUP_ITEM_ATPS_VIEWOracle Proprietary, Confidential
InformationUse Restricted by ContractHighLevel Design 2 55
MTL_ITEM_CATALOG_GROUPS_KFV MTL_ITEM_LOCATIONS_KFV
MTL_ITEM_LOCATIONS_VIEW MTL_ITEM_LOT_QUANTITIES_VIEW
MTL_ITEM_QUANTITIES_VIEW MTL_ITEM_REVISIONS_ORG_VAL_V
MTL_ITEM_REV_HIGHDATE_V MTL_ITEM_SUB_AST_VAL_V
MTL_ITEM_SUB_EXP_TRK_VAL_V MTL_ITEM_SUB_TRK_ALL_V
MTL_LOT_NUMBERS_SRW_V MTL_LOT_NUMBERS_VAL_V
MTL_MATERIAL_TXNS_TEMP_VIEW MTL_NEGATIVE_VIEW MTL_OBJECT_NUMBERS_V
MTL_ONHAND_QTY_COST_V MTL_PARAMETERS_ALL_V MTL_PERIODS
MTL_PHY_ADJ_COST_V MTL_PHY_INV_TAGS_COST_V MTL_PROJECT_DEMAND_VIEW
MTL_QOH_ITEM_V MTL_QOH_LOCATOR_V MTL_QOH_LOT_V MTL_QOH_REV_V
MTL_QOH_SUB_V MTL_RELATED_ITEMS_VIEW MTL_ROUTING_REV_HIGHDATE_V
MTL_SALES_ORDERS_KFV MTL_SECINV_QUANTITIES_VIEWOracle Proprietary,
Confidential InformationUse Restricted by Contract2 56 Oracle
Inventory Technical Reference Manual
MTL_SERIAL_NUMBERS_SRW_V MTL_SUB_AST_VAL_V MTL_SUB_EXP_TRK_VAL_V
MTL_SYSTEM_ITEMS_B_KFV MTL_SYSTEM_ITEMS_FKEYS_V
MTL_TRANSACTION_LOTS_VIEW MTL_TRANSACTION_REASONS_ALL_V
MTL_TRANSACT_INTERFACE_VIEW MTL_UNITS_OF_MEASURE_AV
MTL_UOM_CLASSES_AV MTL_UOM_CLASSES_VV MTL_UOM_CLASS_CONV_VAL_V
MTL_UOM_CONVERSIONS_VAL_V ORG_ACCESS_VIEW ORG_FREIGHT_CODE_VAL_V
ORG_ORGANIZATION_DEF_MRC_V ORG_ORG_DEFINITIONS_ALL_V
PA_ORGANIZATIONS_EXPEND_V PA_PROJECTS_EXPEND_V PA_TASKS_EXPEND_V
PO_VENDORS_VIEW
Oracle Proprietary, Confidential InformationUse Restricted by
ContractHighLevel Design 2 57
Single Organization View ListMultiOrganization Support is a
feature that allows you to implement multiple sets of books within
a single installation of Oracle Payables, Oracle Receivables,
Oracle Purchasing, Oracle Order Management, and Oracle Shipping
Execution. Instead of using multiple installations to provide data
security, data is secured by operating unit. In Release 10.7, we
added a column, ORG_ID, to each base table that requires
partitioning by operating unit, including all transaction tables
and many reference tables, then renamed these tables to end with
the suffix _ALL. Then, to take the place of the renamed table, we
create a view (named like the Release 10.6 or earlier table)
containing a WHERE clause that automatically restricts data to a
single operating unit. The WHERE clause relies upon the value of an
Oracle global variable to indicate the current organization. If you
want to retrieve all information, regardless of operating unit,
query the _ALL table. For example, if you are running a
crossorganization report, you probably want to query the _ALL
table. However, if you want to report against only a single
organization or operating unit, query the corresponding
crossorganizational view, using the familiar 10.6style table name.
The view definition will automatically retrieve only data for your
current operating unit. Additional Information: Multiple
Organizations in Oracle Applications
Oracle Inventory uses the following Single Organization views:
PO_REQUISITIONS_INTERFACE SO_HEADERS SO_LINES
Oracle Proprietary, Confidential InformationUse Restricted by
Contract2 58 Oracle Inventory Technical Reference Manual
Module ListThis section lists each form, report, and concurrent
program comprising Oracle Inventory.
FormsBOMFDCAL BOMFDCON BOMFDDEL BOMFDEXS BOMFDMCC CSTFDATY
CSTFDCTP CSTFDMOD CSTFDOVH CSTFQSCH FNDNLDCX GLXACCMB GLXRTDLY
GLXRTPER GLXSTBKS GLXSTCAL GLXSTPTY INVAAACP INVADAAS INVADACA
INVADACL INVADAGR INVADCSC INVADCYC INVADPAP INVADPPI
Define Workday Calendar Define Delete Constraint Delete Item
Information Define Workday Exception Sets Define Material
SubElements Define Activity Define Cost Type Define Item Overhead
Defaults Define Overhead View Item Standard Cost History Define
Currency GL Accounts Daily Rates Period Rates Set of Books
Accounting Calendar Period Types Define ABC Compiles Assign ABC
Items Update ABC Assignments Define ABC Classes Define ABC Groups
Enter Manual Schedule Requests Define Cycle Count Approve Physical
Inventory Adjustments Define Physical Inventor