Oracle Financials Functional Foundation Release 11 Volume 1 Instructor Guide

Oracle Financials Functional
Foundation Release 11
Volume 1 Instructor Guide
.......................................................................................
14010GC11
Production 1.1
May 1999
M08712
Authors
Suzanne Brown
Chacko Pulivelil
Technical Contributors
and Reviewers
Andrea Auld
Laura Finkelstein
Rick Neidert
Anne Ristau
Publisher
Stephanie Jones-Collins
Copyright Oracle Corporation, 1999. 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 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 Education
Products, Oracle Corporation, 500 Oracle Parkway, Box SB-6, Redwood Shores,
CA 94065. Oracle Corporation does not warrant that this document is error-free.
Oracle is a registered trademark and Oracle Activity Management Gateway,
Oracle Alert, Oracle Application Object Library, Oracle Assets, Oracle Bills of
Material, Oracle Capacity, Oracle Cash Management, Oracle Cost Management,
Oracle EDI Gateway, Oracle Engineering, Oracle Financial Analyzer, Oracle
Financials, Oracle GEMMS, Oracle General Ledger, Oracle Human Resources,
Oracle Inventory, Oracle Master Scheduling, Oracle MRP, Oracle Order Entry,
Oracle Payables, Oracle Payroll, Oracle Personal Time and Expense, Oracle
Product Configurator, Oracle Project Billing, Oracle Project Costing, Oracle
Purchasing, Oracle Quality, Oracle Receivables, Oracle Sales and
Compensation, Oracle Sales and Marketing, Oracle Self-Service Web
Applications, Oracle Service, Oracle Supply Chain Planning, Oracle Supplier
Scheduling, Oracle Time Management, Oracle Training Administration, Oracle
Web Customers, Oracle Web Employees, Oracle Web Suppliers, Oracle
Workflow, Oracle Work in Process, Pro*C, Pro*COBOL, Pro*FORTRAN,
SQL*Plus, and SQL*Loader 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.
Contents
.....................................................................................................................................................
Preface
Profile xiii
Related Publications xv
Typographic Conventions xvi
Lesson 1: Course Introduction
Course Objectives 1-2
Agenda 1-3
Oracle Applications Products Overview 1-4
Product Overview 1-5
Oracle Financials Functional Foundation 1-6
Summary 1-7
Lesson 2: Naming Conventions, Directory Structures, and Standards
Objectives 2-2
Overview 2-3
The Three-Tier Architecture of Release 11 Applications 2-4
Reading the Entity Relationship Diagram 2-5
Using Tools to Find Technical Information 2-6
Registry of Application Tables 2-8
Standards and Naming Conventions 2-9
Program Naming Conventions 2-12
Application Registry 2-13
Form Server Directory Structure 2-14
Database Server Directory Structure 2-15
Summary 2-16
Lesson 3: Application Object Library: Security, Concurrent Processing,
and Flexfields
Objectives 3-2
Application Object Library: Overview 3-3
Application Object Library 3-5
Application Object Library: Security 3-6
Security Tables: Menus 3-7
.....................................................................................................................................................
Oracle Financials Functional Foundation Release 11
iii
Contents
.....................................................................................................................................................
Security Tables: Data Groups 3-11

Application Security: Request Group Tables 3-14
Security Tables: Responsibility Tables 3-17
Security Tables: Application User Tables 3-20
Application Object Library: Profile Options 3-22
Security Tables: Profile Option Tables 3-24
Security: Folders 3-26
Security Tables: Folder Tables 3-27
Practice 3-1 Overview 3-29
Concurrent Requests, Programs, and Managers 3-31
Request ID 3-33
Concurrent Processing Tables 3-34
Application Object Library: Concurrent Managers 3-36
Balancing Process Workload 3-38
Concurrent Manager Table Relationships 3-39
Application Object Library: Flexfields 3-43
Descriptive Flexfields 3-44
Defining Descriptive Flexfields 3-45
Descriptive Flexfields: Table Relationship 3-47
Key Flexfields 3-53
Defining Key Flexfields 3-54
Key Flexfield Table Relationships 3-56
Summary 3-60
Lesson 4: Financial Applications: An Overview
Objectives 4-2
Oracle General Ledger 4-3
Oracle Purchasing 4-4
Oracle Accounts Payable 4-5
Oracle Fixed Assets 4-6
Oracle Inventory 4-7
.....................................................................................................................................................
iv
Contents
.....................................................................................................................................................
Oracle Order Entry 4-8

Oracle Receivables 4-9
Integration Among the Oracle Financial Applications 4-10
Processes That Pass Data Among Applications 4-12
Financial Data Passed to General Ledger by Other Modules 4-14
The Sources of Default Accounts 4-16
The Multi-Org Architecture 4-18
Multiple Reporting Currencies 4-22
Summary 4-24
Lesson 5: Oracle General Ledger
Objectives 5-2
Oracle General Ledger Overview 5-3
Oracle General Ledger 5-4
General Ledger: Currency, Calendar, and Chart of Accounts 5-6
General Ledger: Journal Entries 5-10
General Ledger: Budget 5-16
Multiple Reporting Currencies 5-19
Multiple Reporting Currencies: Setup Tables 5-20
Multiple Reporting Currencies Tables 5-23
GL Interface Table 5-27
Summary 5-28
Lesson 6: Oracle Purchasing
Objectives 6-2
Oracle Purchasing Overview 6-3
Oracle Purchasing: Operating Units 6-7
Oracle Purchasing: Purchasing Agent Tables 6-9
Oracle Purchasing: Items Table 6-11
Oracle Purchasing: Vendor Information Tables 6-12
Oracle Purchasing: Purchase Requisition Tables 6-16
Oracle Purchasing: Purchase Orders, Requests for Quotes, and Quotations 6-20
Oracle Purchasing: Purchase Order Tables 6-21
.....................................................................................................................................................
v
Contents
.....................................................................................................................................................
Oracle Purchasing: Receiving Default Information 6-26

Oracle Purchasing: Receiving Tables 6-29
Tables for Passing Material Receipts to GL 6-36
Summary 6-38
Lesson 7: Oracle Payables
Objectives 7-2
Oracle Payables Overview 7-3
Oracle Payables: Setup Table 7-8
Oracle Payables: Vendor Information Tables 7-9
Types of Invoices 7-10
Oracle Payables: Invoice Tables 7-11
Payment Methods 7-16
Oracle Payables: Payment Tables 7-17
MRC Tables Used in Payables 7-22
Oracle Payables: Posting Invoices in General Ledger 7-24
Summary 7-25
Lesson 8: Oracle Fixed Assets
Objectives 8-2
Maintaining Accurate Asset Inventory 8-3
Oracle Assets Overview 8-4
Asset Types 8-9
Oracle Assets: Setup Tables 8-10
Using Mass Additions 8-14
Oracle Assets: Asset Addition/Definition Tables 8-16
Oracle Assets: Depreciation Tables 8-21
Summary 8-23
.....................................................................................................................................................
vi
Contents
.....................................................................................................................................................
Lesson 9: Oracle Inventory

Objectives 9-2
Overview of Oracle Inventory 9-3
Oracle Inventory Overview 9-4
Oracle Inventory: Organizations and Default Accounts 9-6
Oracle Inventory: Subinventories and Default Accounts 9-9
Oracle Inventory: Item Tables 9-10
Oracle Inventory: Transaction Tables 9-14
Oracle Inventory: Physical Inventory Tables 9-19
Oracle Inventory: Cycle Count Tables 9-21
Inventory to General Ledger: Data Transfer 9-22
Summary 9-23
Lesson 10: Oracle Order Entry
Objectives 10-2
Oracle Order Processing Business Flow 10-3
Delivery-Based Shipping 10-9
Oracle Order Entry: Operating Units and Customer Profile Class Tables 10-10
Oracle Order Entry: Customer Tables 10-12
Oracle Order Entry: Items Table 10-18
Oracle Order Entry: Order Cycle Tables 10-19
Oracle Order Entry: Price List and Discount Tables 10-23
Oracle Order Entry: Order Types Table 10-28
The Order Process 10-30
Oracle Order Entry: Orders Tables 10-31
Oracle Order Entry: Pick List Tables 10-35
Delivery-Based Shipping Tables 10-38
Inventory Tables Updated on Confirming Shipment 10-43
Data Transfer from Order Entry to General Ledger 10-47
Data Transfer from Order Entry to Accounts Receivable 10-48
Summary 10-49
.....................................................................................................................................................
vii
Contents
.....................................................................................................................................................
Lesson 11: Oracle Receivables

Objectives 11-2
Oracle Receivables Overview 11-3
Oracle Receivables: Customer Tables 11-6
Transaction Classes 11-15
Oracle Receivables: Customer Invoices 11-16
Oracle Receivables: Payments (Cash Receipts) 11-23
Data Transfer from Receivable to General Ledger 11-29
Summary 11-30
Lesson 12: Open Interfaces
Objectives 12-2
Importing Information 12-3
Open Interface Model 12-5
Managing Open Interface Processing 12-7
Oracle Interface Example: GL Journal Import 12-8
The GL_INTERFACE Table 12-11
Oracle Interfaces: General Ledger 12-12
Oracle Applications Open Interfaces for Assets 12-13
Oracle Applications Open Interface for Order Entry 12-15
Oracle Applications Open Interfaces for Payables 12-17
Oracle Applications Open Interfaces for Purchasing 12-19
Oracle Applications Open Interfaces for Receivables 12-21
Data Conversion Overview 12-23
Data Conversion Project Plan 12-24
Designing the Conversion Process 12-26
Developing Programs for Conversion 12-28
Performing the Conversion 12-29
Summary 12-30
.....................................................................................................................................................
viii
Contents
.....................................................................................................................................................
Lesson 13: Oracle Self-Service Web Applications

Objectives 13-2
Oracle Self-Service Web Applications 13-3
Overview of OSSWA 13-4
The Self-Service Business Model 13-6
Advantages of Using OSSWA 13-7
Differentiating OSSWA from NCA 13-8
Product Integration 13-11
Web Transactions Dependencies 13-12
Summary 13-15
Appendix A: Table Relationship Diagrams
Security Table Relationships A-2
Concurrent Request Table Relationships A-3
Concurrent Manager Table Relationships A-4
Security: Descriptive Flexfield Table Relationships A-5
Security: Key Flexfield Table Relationships A-6
General Ledger Table Relationships A-7
Oracle Purchasing Table Relationships A-8
Oracle Purchasing Table Relationships: Material Receipts A-9
Oracle Accounts Payable Table Relationships A-10
Oracle Accounts Payable Table Relationships: Invoices A-11
Oracle Accounts Payable Table Relationships: Payments A-12
Oracle Fixed Assets Table Relationships A-13
Oracle Fixed Assets Table Relationships: Assets A-14
Oracle Inventory Table Relationships A-15
Oracle Order Entry Table Relationships A-16
Oracle Order Entry Table Relationships: Picking/Shipping A-17
Oracle Accounts Receivable Table Relationships A-18
.....................................................................................................................................................
ix
Contents
.....................................................................................................................................................
Appendix B: Database Tables and Their Primary and Foreign Key

Relationships
Appendix C: Practices and Solutions
Practice 3-1 C-2
Practice 3-1 Solutions C-5
Practice 3-2 C-13
Practice 3-3 C-15
Practice 5-1 C-19
Practice 6-1 C-22
Practice 7-1 C-26
Practice 8-1 C-30
Practice 9-1 C-34
Practice 10-1 C-38
Practice 11-1 C-43
Practice 12-1 C-45
Practice 13-1 C-52
.....................................................................................................................................................
x
Preface
.................................
Profile
.....................................................................................................................................................
Profile
Before You Begin This Course
Before you begin this course, you should have the following qualifications:
Ability to query and display data by using SQL*Plus
Working experience with at least one of the Oracle financial application modules
Prerequisites
At least one of the following Oracle Applications courses:
General Ledger
Purchasing
Payables
Assets
Receivables
Order Entry
Inventory
How This Course Is Organized
Oracle Financials Functional Foundation is an instructor-led course featuring lecture
and hands-on exercises. Online demonstrations and written practice sessions reinforce
the concepts and skills introduced.
Lesson 3: Application Object Library: Security, Concurrent Processing, and
Flexfields
Lesson 10: Oracle Order Entry
Lesson 11: Oracle Receivables
Lesson 12: Open Interfaces
Lesson 13: Oracle Self-Service Web Applications
Appendix A: Table Relationship Diagrams
Appendix B: Database Tables and Their Primary and Foreign Key Relationships
Appendix C: Practices and Solutions
.....................................................................................................................................................
xiii
Preface
.....................................................................................................................................................
Course Objectives
After completing this course, you should be able to do the following:
Describe the directory structure for Oracle Applications product files
Read and evaluate entity relationship diagrams for the following Oracle
Applications financial modules:
Application Object Library (AOL)
General Ledger
Purchasing
Payables
Assets
Inventory
Order Entry
Receivables
Use an open interface
Discuss the functionality of Oracle Self-Service Web Applications
.....................................................................................................................................................
xiv
Related Publications
.....................................................................................................................................................
Related Publications
Oracle Publications
Title
Installation manuals by platform
Oracle Applications System Administrators Guide
Oracle Applications Flexfields Guide
Oracle Application Object Library/Workflow Technical Reference
Manual
Oracle Financials Open Interfaces Guide
Oracle Assets Technical Reference Manual
Oracle General Ledger Applications Technical Reference Manual
Oracle Payables Applications Technical Reference Manual
Oracle Receivables Applications Technical Reference Manual
Oracle Order Entry/Shipping Technical Reference Manual
Oracle Purchasing Technical Reference Manual
Oracle Inventory Technical Reference Manual
Part Numbers
A58194-01
A58188-01
A58192-01
A58482-01
A58484-01
A58486-01
A58487-01
A58489-01
A58300-02
A58301-01
A58299-01
Additional Publications
System release bulletins
Installation and users guides
read.me files
International Oracle Users Group (IOUG) articles
Oracle Magazine
.....................................................................................................................................................
xv
Preface
.....................................................................................................................................................
Typographic Conventions
Typographic Conventions in Text
Convention
Bold italic
Caps and lowercase
Element
Glossary term (if
there is a glossary)
Buttons,
check boxes,
triggers,
windows
Courier new,
case sensitive
(default is
lowercase)
Code output,
directory names,
file names,
passwords, path
names,
URLs,
user input, user
names
Initial cap
Graphics labels
(unless the term is a
proper noun)
Emphasized words
and phrases,
titles of books
and courses,
variables
Italic
Quotation marks
Uppercase
Interface elements
with long names
that have only
initial caps; lesson
and chapter titles in
cross-references
SQL column
names, commands,
functions, schemas,
table names
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger . . .
Open the Master Schedule window.
Code output: debug.seti(I,300);
Directory: bin (DOS), $FMHOME (UNIX)
File name: Locate the init.ora file.
Password: Use tiger as your password.
Path name: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
User name: Log on as scott
Customer address (but Oracle Payables)
Do not save changes to the database.

For further information, see Oracle7 Server
SQL Language Reference Manual.
Enter user_id@us.oracle.com, where
user_id is the name of the user.
Select Include a reusable module
component and click Finish.
This subject is covered in Unit II, Lesson 3,
Working with Objects.
Use the SELECT command to view

information stored in the LAST_NAME
column of the EMP table.
.....................................................................................................................................................
xvi
Typographic Conventions
.....................................................................................................................................................
Convention
Arrow
Brackets
Commas
Element
Menu paths
Key names
Key sequences
Plus signs
Key combinations
Example
Select File>Save.
Press [Enter].
Press and release these keys one at a time:
[Alt], [F], [D]
Press and hold these keys simultaneously:
[Ctrl]+[Alt]+[Del]
Typographic Conventions in Code

Convention
Caps and lowercase
Lowercase
Element
Oracle Forms
triggers
Column names,
table names
Passwords
PL/SQL objects
Lowercase italic
Uppercase
Syntax variables
SQL commands
and functions
Example
When-Validate-Item
SELECT last_name
FROM s_emp;
DROP USER scott
IDENTIFIED BY tiger;
OG_ACTIVATE_LAYER
(OG_GET_LAYER (prod_pie_layer))
CREATE ROLE role
SELECT userid
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 bar, select Query>Find.
3 (B) Click the Approve button.
N = Navigator, M = Menu, B = Button
.....................................................................................................................................................
xvii
Preface
.....................................................................................................................................................
.....................................................................................................................................................
xviii
1
.................................
Course Introduction

.....................................................................................................................................................
Course Objectives
Course Objectives
After completing this course, you should be able to

do the following:
Describe the directory structure for Oracle

Applications product files
Read and evaluate entity relationship diagrams

(ERDs) for Oracle Applications financial modules

Discuss the functionality of Oracle Financial
Applications and how they integrate with each
other
Course Objectives
After completing this course, you should be able to do the following:
Describe the directory structure for Oracle Applications product files
Read and evaluate entity relationship diagrams for the following Oracle
Applications financial modules:
Application Object Library (AOL)
General Ledger
Purchasing
Payables
Assets
Inventory
Order Entry
Receivables
Discuss the functionality of Oracle Self-Service Web Applications
.....................................................................................................................................................
1-2
Agenda
.....................................................................................................................................................
Agenda
Day 1
Course Overview
Tools for Researching Technical Information
Directory Structures/Naming Conventions and Standards
Application Object Library (Security, Concurrent Processing and Flexfields)
Day 2
Accounting Overview
General Ledger
Purchasing
Day 3
Accounts Payable
Fixed Assets
Inventory
Order Entry
Day 4
Accounts Receivables
Open Interfaces
Oracle Self-Service Web Applications
.....................................................................................................................................................
1-3

.....................................................................................................................................................
Oracle Applications Products Overview

Oracle Applications
Products Overview
Manufacturing
Financials
Projects
Human Resources
Front Office Applications
Supply Chain Management
Oracle Applications Overview

Use Oracle Applications to meet the unique information requirements of your
enterprise. Oracle Applications products are divided into the following categories:
Manufacturing applications
Financial applications
Projects
Human Resources
Front Office applications
Supply Chain management
.....................................................................................................................................................
1-4
Product Overview
.....................................................................................................................................................
Product Overview
Oracle Applications
Product Overview
Financials
Oracle Financial Applications

Oracle Financials consists of an integrated suite of applications designed to manage
and record the financial impact of transactions occurring in a business environment
and to use the information to produce financial statements.
Oracle Financial Applications products include:
General Ledger
Purchasing
Accounts Payable
Fixed Assets
Inventory
Order Entry
Accounts Receivable
.....................................................................................................................................................
1-5

.....................................................................................................................................................
Oracle Financials Functional Foundation

Oracle Financials
Functional Foundation
This course covers the following financial
applications modules:
General Ledger
Purchasing
Payables
Assets
Inventory
Order Entry
Receivables
References
Oracle references that complement the learning in this course include the following
manuals:
Technical reference and implementation manuals for each module
Oracle Applications System Administrators Guide
Oracle Financials Open Interfaces Guide
Oracle Application Object Library/Workflow Technical Reference Manual
Oracle Applications Flexfields Guide
.....................................................................................................................................................
1-6
Summary
.....................................................................................................................................................
Summary
Summary
This course covers the basic functionality of the

core financial application modules. The basic
concepts of security, directory structures, and
flexfields are reviewed.
The instructor will demonstrate a series of

simulated financial transactions that occur in a
typical business environment and discuss the
relationships between the database tables being
populated by those transactions. The students will
then use SQL*Plus to answer functional questions
by querying the tables.
.....................................................................................................................................................
1-7

.....................................................................................................................................................
.....................................................................................................................................................
1-8
2
.................................
Naming Conventions,
Directory Structures, and
Standards

.....................................................................................................................................................
Objectives
Objectives
After completing this lesson, you should be able to

do the following:
List some tools that help in finding technical

information about the application.
Describe the manner in which forms files are

stored on the forms server and program/report
files are stored on the database server.
Discuss naming conventions used by Oracle

application development for database objects and
application programs.
Lesson Aim
In this lesson, you will learn how to read an entity relationship diagram, which will
help you understand the table relationship diagrams in this book, and entity
relationship diagrams in the technical reference manuals. You will also learn some
tools that can help you to research table and column relationships online. The
discussion of forms and database server directory structures will help you to find the
location of form and program files used by the applications. Information on naming
conventions used by Oracle application developers is provided to assist you in
identifying the functional purpose of an object such as a table, column or program
when looking at its name in a technical reference manual.
.....................................................................................................................................................
2-2
Overview
.....................................................................................................................................................
Overview
Overview
This lesson covers the following topics:
The three-tier architecture of release 11

applications
How to read an Entity Relationship Diagram

Tools for researching information
Server directory structures
Database object naming conventions
Program naming standards
.....................................................................................................................................................
2-3

.....................................................................................................................................................
The Three-Tier Architecture of Release 11 Applications

Network Computing Architecture
Desktop
client
tier
Client interface applet
Application
tier
Database
tier
Three-Tier Architecture
The Network Computing Architecture (NCA) gives Oracle Applications a framework
for multi-tier, distributed processing of financial data. The client tier consists of a Java
applet or browser installed on the client PC. The middle tier consists of the application
forms, which reside on a separate forms server. The database tier consists of all of the
database files, as well as all report and program files utilized by the application.
In release 11, the client interface is provided through a Java applet. The client can
download the applet on demand, or cache the applet locally and download only when
the applet is updated. All software updates are installed on the application tier and
downloaded to the client automatically. Shifting software administration from the
desktop to the application and database tiers provides both a graphical user interface
and lowered administration costs.
Instructor Note
For more information on the three-tier architecture, refer the students to the Installing
and Administering Oracle Applications course.
.....................................................................................................................................................
2-4
Reading the Entity Relationship Diagram

.....................................................................................................................................................
Reading the Entity Relationship Diagram

Reading an Entity Relationship Diagram
A
Each row in table A

related one-to-one with a
row in table B
Each row in table A

related many-to-one with
a row in table B
B
A
C
Each row in table A

related many to one with
a row in either table B or
table C, but not both
Must be
relationship
May be
relationship
Entity Relationship Diagrams

An entity relationship diagram illustrates the relationships among the major and
shared tables within an application. Each table summary includes the major columns
and primary key information.
The major key data is used in tables in multiple products. The relationship can be oneto-many or many-to-one. The method of diagramming the table relationships is called
an entity relationship diagram (ERD).
Good relational database design ensures data integrity and minimizes data redundancy.
This is done by storing the details of an entity (such as item, vendor, 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.
In a relational database, these 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.
.....................................................................................................................................................
2-5

.....................................................................................................................................................
Using Tools to Find Technical Information

Tools For Researching Information
All Oracle applications provide the following tools to

help you find technical information:
Help
About Oracle Applications
Help
About This Record
Help
Tools
Examine
Application Developer Responsibility
Researching Technical Information on Applications

Oracle Applications provide a number of tools for finding technical information on the
application you are using. These are discussed in the following subsections:
Version Information Use the following path to determine product (version of the
application, application object library, forms, and RDBMS), log in and form (form
application, form executable, form version, and last modified date) information:
(M) Help>About Oracle Application
The Name of the Form You Are Looking At To determine the name of the form
you are looking at, use the following path to open the About Oracle Applications
window. The name of the form you see is the name of a forms executable file that is
stored on the forms server and whose existence is registered in the database:
(M) Help>About Oracle Applications
Properties of a Field in a Form Place the cursor in the field whose properties are
to be examined and then use the following path to determine its properties:
(M) Help>Tools>Properties>Item
Instructor Note
Please demonstrate the tools and explain their significance while covering this topic.
Log in to the application as a system administrator and query a record in the Users
window:
(N) Security>User>Define
.....................................................................................................................................................
2-6
Using Tools to Find Technical Information

.....................................................................................................................................................
Researching Technical Information on Applications (continued)

The Table Being Updated When You Enter Information in the Current Form and
Who Last Updated This Record To determine the table being updated by your
actions within the form, use the following navigation path:
(M) Help>About This Record
Note: In some cases this screen displays the name of a table with a _V or _VL at the
end, which means that the form is actually looking at a view of the table, possibly for
security reasons.
The Value of the Primary Key for the Current Record These values are
generally not visible on the form. Use the following navigation path to determine the
value in any column in the table behind the form:
(M) Help>Tools>Examine
The Examine Field and Variable Values window opens. Select the appropriate block
and field combination whose value is to be determined.
Instructor Note
The Name of the Database Instance to Which You Are Connected In each form,
use the following path to access some generic blocks such as $ENVIRONMENT$,
$PROFILE$ and $DESCRIPTIVE_FLEXFIELD$:
(M) Help>Tools>Examine
Instructor Note
To determine the database you are connected to, select $ENVIRONMENT$ as the
Block value and TWO_TASK as the Field value.
Descriptions and Data Types of the Columns in Any Application Table Behind
the Current Form With Application Developer as your responsibility, use the
following navigation path to open the Tables window. Using this window, you can
view complete details about any of the tables available in the application database:
(N) Application>Database>Table
In the Table window, execute a query to fetch the table whose details are to be viewed.
.....................................................................................................................................................
2-7

.....................................................................................................................................................
Registry of Application Tables

Registry of Application Tables/Columns
FND_TABLES
TABLE_ID
TABLE_NAME
FND_COLUMNS
TABLE_ID
COLUMN_ID
COLUMN_NAME
COLUMN_TYPE
WIDTH
NULL_ALLOWED_FLAG
DESCRIPTION
Table Registry
When you install the application, the AutoInstall process registers all of the
application tables and their associated columns in FND_TABLES and
FND_COLUMNS as shown in the preceding diagram.
Instructor Note
Have participants write a SQL script to list the names of all the tables containing a
column named APPLICATION_ID.
Select t.table_id,
From fnd_tables t,
fnd_columns c
Where c.column_name = APPLICATION_ID
and c.table_id = t.table_id;
Discussion question: Will this SQL script list every table that references an
application?
Answer: No, because an application may be referenced in a column that has a different
name.
.....................................................................................................................................................
2-8
Standards and Naming Conventions

.....................................................................................................................................................

Database Naming Conventions
Database Objects
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
Instructor Note
Table names in Purchasing start with PO (Purchase Order), or RCV (Receiving).
Table names in Inventory start with MTL (Material).
Table names in Order Entry start with SO (Sales Orders).
Table names in Receivables start with AR (Accounts Receivable), or RA (Revenue
Accounting).
Table names in Application Object Library start with FND (Foundation).
.....................................................................................................................................................
2-9

.....................................................................................................................................................
Database Objects (continued)

Column names should be:
Unprefixed if not a primary key column
Singular
End-user oriented
Concise (avoid unnecessary abbreviations)
Unambiguous
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 are required when the table will be updated by a program.
These are the program WHO columns.
REQUEST_ID
PROGRAM_APPLICATION_ID
PROGRAM_ID
PROGRAM_UPDATE_DATE
Column Order Order the table columns according to the following priorities:
1 Primary key columns (major to minor)
2 WHO columns
3 Required columns
4 Foreign keys
5 Optional columns
6 Attributes (descriptive flexfield columns)
7 LONG datatypes
.....................................................................................................................................................
2-10

.....................................................................................................................................................
Database Objects (continued)

Indexes 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
Be identified as nonunique indexes by using the suffix _Nm, where m is a number
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
Instructor Note
1 Most primary and foreign keys are not registered at the database level. These
relationships are enforced at the application level only.
2 Primary keys are usually (but not always) identified by _ID. User visible numbers
are usually (but not always) stored in columns with suffix _NUM or _NUMBER.
Please note that Oracle Purchasing stores user visible numbers in a column called
SEGMENT1.
3 To name custom indexes, begin with 99 and work backwards. This would ensure
that you dont overwrite one of the predefined indexes in the application. This
would also ensure that your custom index would live through upgrades. For
example, if you name a custom index N4 and then in Oracles next release (or in
a patch), an index named N4 is used, it will overwrite your custom index.
.....................................................................................................................................................
2-11

.....................................................................................................................................................
Program Naming Conventions

Program Naming Conventions
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 should be made up of eight characters. Use uppercase letters for
the program name and lowercase letters for extensionsfor example, FNDSCURS for
the Active Users Report.
Instructor Note
Please demonstrate the execution file name of FNDSCURS (responsibility: System
Administrator) as it appears when queried from the Concurrent Program Executable
window.
(N) Concurrent>Program>Executable
FND indicates Application Object Library.
SC indicates security.
URS indicates a little bit about what the program does.
.....................................................................................................................................................
2-12
Application Registry
.....................................................................................................................................................
The AutoInstall process registers each of the applications, for which you have
purchased a license, in a table called FND_APPLICATION. The value in the basepath
column indicates the name of the environment variable whose value, as defined in the
environment files on the Forms and Database servers, indicates the top level
subdirectory under which the form or program files for that application are stored.
Instructor Note
Please demonstrate that the environment variable for Application Object Library is
FND_TOP (responsibility: System Administrator).
(N) Application>Register
Run a general query to populate the window.
.....................................................................................................................................................
2-13

.....................................................................................................................................................
Form Server Directory Structure

Forms Server Directory Structure
$APPL_TOP
Environment File
$FND_TOP
$GL_TOP
FORMS
FORMS
US
FRENCH
US
XXX.fmx
XXX.fmx
XXX.fmx
Directory Structure of Form Server

The AutoInstall process installs the forms for each application in a separate
subdirectory on the Forms server. It also registers the name of each of the forms
installed on the Forms Server in the FND_FORMS table in the database.
Instructor Note
Open the Forms window and perform a general query to display a list of forms that
have already been registered (responsibility: Application Developer).
(N) Application>Form
.....................................................................................................................................................
2-14
Database Server Directory Structure

.....................................................................................................................................................
Database Server Directory Structure

Sample Database Server Directory
Structure
$APPL_TOP
$FND_TOP
BIN
REPORTS
APPS.ENV
SQL
$APPLCSF
LOG
OUT
requestor.request_id
lrequest_id.req
The Directory Structure of Oracle Applications Product Files

The AutoInstall process creates a directory structure on the database server for report
and program files for each application. This directory structure is depicted in the slide.
$APPL_TOP and $FND_TOP, and so on are environment variables whose value is
defined in the environment file (usually APPS.ENV). The subdirectory in which a file
is stored is determined by the application that owns the program, and the method of
execution of the program (Immediate, Spawned, or Oracle Reports).
The AutoInstall process registers the name of the of the executable file in the
FND_EXECUTABLES table.
While running programs and reports, Oracle applications always generate a log file.
Sometimes, an output file is also generated. The AutoInstall process provides you with
the option of storing log and output files in subdirectories under each application (to
enhance security) or in a common subdirectory whose location is identified by the
value of the $APPLCSF environment variable (Application Common Subdirectory for
Files).
Instructor Note
Please see the instructor notes after the lesson summary. These notes document how to
demonstrate the links between what the user sees and the directory structure on the
database server.
.....................................................................................................................................................
2-15

.....................................................................................................................................................
Summary
Summary
In this lesson, you should have learned the following:
Release 11 three-tier architecture

How to read an entity relationship diagram
Tools
Standards and naming conventions
Form Server directory structure
Database server directory Structure
Instructor Note
This instructor demonstration illustrates the link between an executable file on the
server and a concurrent program. Use the System Administrator responsibility for the
purpose of this demonstration.
1 Navigate to the Submit Request window and select the Active Users report as the
request to be run.
(N) Requests>Run
2 Close the Submit Request window without running the report.
3 Navigate to the Concurrent Programs window and query up the Active Users
report and show that it references the FNDSCURS executable.
(N) Concurrent>Program>Define
4 Navigate to the Concurrent Program Executable window. Query up the
FNDSCURS executable and show that it is owned by Application Object Library,
its execution method is Oracle Reports, and that it uses the FNDSCURS execution
file name.
.....................................................................................................................................................
2-16
Summary
.....................................................................................................................................................
Instructor Note (continued)

5 Navigate to the Applications window and query up the Application Object Library
application. Show that the value in the basepath column is FND_TOP, the name of
the environment variable whose value as defined in APPLSYS.ENV determines
that name of the subdirectory under which all of the files for Application Object
Library programs are stored.
(N)Application>Register
6 Log into UNIX by selecting the VT420 icon.
7 At the UNIX prompt, type cd $APPL_TOP.
8 Type pwd to show where you are.
9 Type ls to list the contents of the APPL_TOP subdirectory and point out the env
file.
10 Type more apps.env to list the contents of the environment file, and point out
the definition of $APPL_TOP, $FND_TOP, $GL_TOP, and so on.
11 Type cd $FND_TOP to change directories to the application object library
subdirectory.
12 Type pwd to show where you are.
13 Type ls to show directory contents.
14 Type cd reports to switch to the subdirectory containing the executable files
for programs whose execution method is Oracle Reports.
15 Type ls to list directory contents and point out that you see FNDSCURS.rdf,
which is the file used when you run the Active Users report that you showed in
step 1.
.....................................................................................................................................................
2-17

.....................................................................................................................................................

This instructor note describes how to demonstrate the link between a concurrent
program run by a user and the location of log and output files on the database server
(Responsibility: System Administrator).
1 Open the Submit Requests window ((N) Request>Run) and select the Active
Users report from the list.
2 Click the Submit Request button and note the REQUEST ID displayed in the
pop-up window.
3 (M) Help>View My Requests to determine if the request is completed. When
the request is completed, show the log and output file by clicking the Log and
Output buttons in the View Requests screen, for your request.
4 Log into UNIX, using the VT420 icon.
5 Change directories to the common output directory for log and output files by
typing cd $APPLCSF.
6 Type ls to list the contents of the subdirectory and look for a subdirectory called
out, or something similar.
7 To get into the out subdirectory, type cd out.
8 To list the files in the subdirectory, type ls. Note that your output file is shown, an
is named REQUESTOR.request_id.
9 List the contents of the output file by typing more REQUESTOR.request_id
(the name of your output file).
.....................................................................................................................................................
2-18
3
.................................
Application Object
Library: Security,
Concurrent Processing,
and Flexfields
Lesson 3: Application Object Library: Security, Concurrent Processing, and Flexfields

.....................................................................................................................................................
Objectives
Objectives

do the following:
Discuss the major security tables and their

columns
Discuss the tables used for storing profile option

data
Discuss the tables used for storing folder

information
Describe the tables used for concurrent

processing
Discuss the tables used for storing flexfield data

.....................................................................................................................................................
3-2
Application Object Library: Overview

.....................................................................................................................................................

Oracle Applications are constructed and

maintained using Application Object Library
(AOL). Applications system administrators use
AOL to manage applications security, establish
operating profiles, and administer concurrent
processing.
The three main areas of AOL are:

Applications security
Operating profiles
Concurrent processing
Application Object Library Overview

System administrators use AOL to manage applications security, administer the
concurrent processing facility, and establish operating profiles.
Security Controlling what application users can do is one of the major tasks facing
system administrators. The section on security covers users, responsibilities, menus,
data groups and request groups, as well as profile options and folder forms. This
section also covers the relationships between the application tables in which
information about these objects is stored. Students will do a practice exercise in the
application to create these objects, link them together and explore how the tables being
updated are related.
Concurrent Processing The section on concurrent processing covers the execution
of reports and programs. This section covers the registry of concurrent programs, the
tables which are updated when a concurrent process is submitted, the definition of a
customized concurrent manager, and the tables that hold the concurrent manager
definition.
.....................................................................................................................................................
3-3

.....................................................................................................................................................
Application Object Library Overview (continued)

Descriptive Flexfields The section on descriptive flexfields (pop-up windows that
capture implementation specific data) covers the tables which store the descriptive
flexfield definition. The instructor will describe the process of defining a descriptive
flexfield, and explain the tables that store the definition.
Key Flexfields The section on key flexfields covers the tables which store key
flexfield definition. Key flexfields are multi-part unique identifiers such as account
numbers and item identifiers that are defined as part of your implementation to enable
you to adapt Oracle applications to reflect the manner in which you do business. The
instructor will describe the process of defining key flexfields, and explain the tables
that store the key flexfield definition.
.....................................................................................................................................................
3-4
Application Object Library

.....................................................................................................................................................
Application Object Library

AOL: Applications Security
User
Security
rules
Application 1
Application 2
Application 3
Application 4
.
.
.
Security
rules
Program 1
Program 2
Program 3
Program 4
.
.
.
Applications Security
Applications security begins with setting up a user with a system login and password
and defining the responsibilities that the user has.
A responsibility is like a job description, granting access to all or part of the
functionality of an application. Each responsibility determines which reports and
concurrent programs can be run, and which applications data those reports and
programs can access.
A single user can have access to multiple responsibilities, and multiple users can share
the same responsibility, thereby accessing or modifying the same data.
Additional security features can be implemented through the use of profile options,
which can be used to control the availability of buttons, the manner in which data is
displayed, and the processing of transactions.
Folder forms provide another method by which you can control what users can do in
the application. Using Folder forms, you can control the layout and query criteria
associated with the data in a form.
Note: Refer to Appendix A Table Relationship Diagrams for a complete diagram
illustrating the relationships among all of the major security tables.
.....................................................................................................................................................
3-5

.....................................................................................................................................................
Application Object Library: Security

Application Object Library: Security
Application user
Responsibility
Menu
Data group
Determines the
forms and tables
you can view
Identifies you as a
database user
Request group
Determines the
reports and
programs you
can run
Security: An Overview
When logging into the application, you have to choose the responsibility level at
which you plan to work. The responsibility you select controls three things:
Menus The forms you have access to.
The forms you have access to determine the tables you can access.
Data Group When you are in a form that looks at a table that belongs to a specific
application, what database user does the application think that you are?
Request Group The reports and programs you can run.
Almost all application security is established at the responsibility level, rather than at
the user level.
Instructor Note
Please demonstrate Practice 3-1 and describe what is happening from a functional
perspective. This practice covers how to create menus, data groups, request groups,
responsibilities, and users. When the students perform this practice on their own, they
will become familiar with security concepts as well as the basics of table relationships
in a relational database.
.....................................................................................................................................................
3-6
Security Tables: Menus

.....................................................................................................................................................

AOL: Function Security
MENU ENTRIES (TL)
FUNCTION
executes
belongs to
SUB MENU
references
consists of
referenced
defined as
MENUS (TL)
assigned to
FORM FUNCTIONS
calls
opens
RESPONSIBILITY (TL)
owned by
defined as
FORM (TL)
owner of
has
owned by
APPLICATION (TL)
Menu Tables
Menus control the forms that are accessible to application users. Security can be
enforced by defining appropriate menus, which can then be attached to
responsibility(ies). The major tables storing menu information are:
FND_APPLICATION
FND_APPLICATION_TL
FND_FORM
FND_FORM_FUNCTIONS
FND_MENUS
FND_MENU_ENTRIES
FND_MENU_ENTRIES_TL
.....................................................................................................................................................
3-7

.....................................................................................................................................................
FND_APPLICATION
This table stores information on all the applications in the application registry. This
table is populated by the AutoInstall process for all the applications for which you
purchased a license. In the course of the implementation, it is useful to create a custom
application record in this table, which can then become part of the primary key
identifying the objects (for example, responsibilities, and request groups) created in
the course of implementation. This will protect the objects created during the
implementation from being overwritten during an upgrade.
Each row includes information such as name and description of the application, and
application short name. The value in the BASEPATH column is the name of an
environment variable whose value is defined in the environment files on the Forms
and Database servers. It identifies the top-level subdirectory for the application.
Major Columns
APPLICATION_ID (PK)
DESCRIPTION
BASEPATH
Instructor Note
Navigate to the Applications window (responsibility: System Administrator):
FND_APPLICATION_TL
This table stores translated information about all the applications registered with
Applications Object Library. Each row includes the language the row is translated to,
the name and description of the application, and the application identifier, which
uniquely identifies the application. You need one row for each application in each of
the installed languages.
Note: The application name is stored in this table, not in the FND_APPLICATION
table.
Major Columns
APPLICATION_ID (PK)
LANGUAGE
APPLICATION_NAME
SOURCE_LANG
.....................................................................................................................................................
3-8

.....................................................................................................................................................
FND_FORM
This table stores information on registered application forms. This table is populated
by the AutoInstall process for all the forms belonging to all the applications for which
you purchased a license. Each row in the table includes names (actual SQL*Forms
form name, and the EasyForm form title) and a description of the form. Please note
that this table has a two-part primary key APPLICATION_ID/FORM_ID.
Major Columns
APPLICATION_ID (PK)
FORM_ID (PK)
FORM_NAME
Instructor Note
Navigate to the Forms window (responsibility: Application Developer):
(N) Application>Form
FND_FORM_FUNCTIONS
This table stores information about form functions. A form function references a form
and includes any parameters to passed to the form (for example,
QUERY_ONLY = YES for data entry forms). This table is populated by the
AutoInstall process for all the forms functions used in the seeded menus delivered
with the application. Form functions are referenced in menus.
Major Columns
FUNCTION_ID (PK)
FUNCTION_NAME
APPLICATION_ID
FORM_ID
PARAMETERS
The form referenced by the form function is uniquely identified by
APPLICATION_ID and FORM_ID.
Instructor Note
Navigate to the Form Functions window (responsibility: System Administrator):
(N) Application>Function
.....................................................................................................................................................
3-9

.....................................................................................................................................................
FND_MENUS
This table stores the menu header information.
Major Columns
MENU_ID (PK)
MENU_NAME
Instructor Note
Navigate to the Menus window (responsibility: System Administrator):
(N) Application>Menu
FND_MENU_ENTRIES
This table stores information about individual entries in the menus in the
FND_MENUS table. A menu entry can be another menu as defined in FND_MENUS
or a form function from FND_FORM_FUNCTIONS. You must have one row for each
menu choice (entry) in each Navigator window.
Major Columns
MENU_ID (PK)
ENTRY_SEQUENCE (PK)
SUB_MENU_ID
FUNCTION_ID
FND_MENU_ENTRIES_TL
This table stores name information on menu entries in each language for which you
have created a menu entry. You must have one row for each menu choice (entry) in
each Navigator window. You must have a prompt for each menu entry so that the menu
compiles correctly. The prompt is what the user sees in the menu.
Major Columns
MENU_ID (PK)
ENTRY_SEQUENCE (PK)
LANGUAGE (PK)
PROMPT
DESCRIPTION
.....................................................................................................................................................
3-10
Security Tables: Data Groups

.....................................................................................................................................................

AOL: Data Groups
RESPONSIBILITY
accessing
owned by
accessed by
defined for
DATA GROUP UNITS

accessing
owner of
APPLICATION (TL)
in
accessed by
ORACLE ID
associated
with
has
DATA GROUP
Data Group Tables

The major data group tables used by Oracle Applications are as follows:
FND_ORACLE_USERID
FND_APPLICATION
FND_DATA_GROUPS
FND_DATA_GROUP_UNITS
FND_ORACLE_USERID
This table stores the registry of Oracle database schemas. This table is populated by
the Autoinstall process with the name and ID of all owners of application tables, along
with a superuser (APPS), which has insert, update, and delete access to all
application tables through grants and synonyms.
Major Columns
ORACLE_ID
ORACLE_USERNAME
DESCRIPTION
Instructor Note
Navigate to the Oracle Users window (responsibility: System Administrator):
(N) Security>Oracle>Register
.....................................................................................................................................................
3-11

.....................................................................................................................................................
FND_APPLICATION
This table stores information on all the applications in the application registry. This
table is populated by the AutoInstall process for all the applications for which you
purchased a license.
Major Columns
APPLICATION_ID (PK)
APPLICATION_NAME
DESCRIPTION
Instructor Note
Navigate to the Applications window (responsibility: System Administrator):
FND_DATA_GROUPS
This table stores information about different data groups. A data group provides the
link to a database user. A data group consists of a list of applications whose tables are
accessed by the users of a responsibility through the forms in their menus. The name
of a database user is associated with each application to indicate the level of database
access. Users of the responsibility attached to the data group appear to the database as
database user associated with that application in the datagroup. The AutoInstall
process creates a data group called Standard, which lists the database user as
APPS for all the installed applications for which you have a license.
Major Columns
DATA_GROUP_ID (PK)
DATA_GROUP_NAME
DESCRIPTION
Instructor Note
Navigate to the Data Groups window (responsibility: System Administrator):
(N) Security>Oracle>DataGroup
.....................................................................................................................................................
3-12

.....................................................................................................................................................
FND_DATA_GROUP_UNITS
This table stores information about Oracle database accounts associated with various
applications under different data groups. This information is used to determine which
Oracle username is being submitted to be associated with a concurrent request when
the request is submitted by a given user responsibility.
Major Columns
DATA_GROUP_ID (PK)
APPLICATION_ID (PK)
ORACLE_ID
.....................................................................................................................................................
3-13

.....................................................................................................................................................
Application Security: Request Group Tables

Application Security: Request Groups
FND_REQUEST_GROUPS
FND_REQUEST_GROUP_UNITS
FND_CONCURRENT_PROGRAMS
FND_EXECUTABLES
Request Group Tables

The major request group tables used by Oracle Applications are as follows:
FND_EXECUTABLES
FND_REQUEST_GROUPS
.....................................................................................................................................................
3-14
Application Security: Request Group Tables

.....................................................................................................................................................
FND_EXECUTABLES
This table stores the registry of concurrent program executables. The execution file
name column contains the name of a file physically stored on the database server. An
executable is uniquely identified by APPLICATION_ID and EXECUTABLE_ID
wherever this executable is referenced in other tables. The AutoInstall process
populates this table with records for all executable files for all of the applications for
which you purchased a license.
Major Columns
APPLICATION_ID (PK)
EXECUTABLE_ID (PK)
EXECUTABLE_NAME
EXECUTION_METHOD_CODE
EXECUTION_FILE_NAME
Instructor Note
Navigate to the Concurrent Program Executable window (responsibility: System
Administrator):
This table stores information about concurrent programs set up using the Concurrent
Programs window. Each row includes details such as the name and description of the
concurrent program, the execution method, and whether the program is constrained. If
the SRS_FLAG is set to Y, then the program name registered here can be viewed
through the Standard Request Submission Form. The AutoInstall process populates
this table with records for all of the standard concurrent programs (canned reports, and
so on) for all of the applications for which you purchased a license.
Major Columns
APPLICATION_ID (PK)
CONCURRENT_PROGRAM_ID
CONCURRENT_PROGRAM_NAME
EXECUTABLE_APPLICATION_ID
EXECUTABLE_ID
SRS_FLAG
USER_CONCURRENT_PROGRAM_NAME *
* This is the name that the user sees in the Standard Request Submission window.
Instructor Note
Navigate to the Concurrent Programs window (responsibility: System Administrator):
(N) Concurrent>Program>Define
.....................................................................................................................................................
3-15

.....................................................................................................................................................
FND_REQUEST_GROUPS
This table stores information header information about request groups. The request
group is uniquely identified by APPLICATION_ID and REQUEST_GROUP_ID.
When creating request groups during an implementation, the application name
referenced as part of the request group name should be a custom application name
created during the implementation to protect the request group from being overwritten
during an upgrade.
Major Columns
APPLICATION_ID (PK)
REQUEST_GROUP_ID (PK)
REQUEST_GROUP_NAME
DESCRIPTION
Instructor Note
Navigate to the Request Groups window (responsibility: System Administrator):
(N) Security>Responsibility>Request
This table stores information about the specific reports and programs to be included in
a request group. For the purpose of efficiency, when creating a request group, you can
identify its members as an individual program (REQUEST_UNIT_TYPE = P), or all
the programs associated with a specific application (REQUEST_UNIT_TYPE = A),
or a request set (REQUEST_UNIT_TYPE = S), which is a set of programs defined by
a system administrator that will be executed in a specified sequence. The
REQUEST_UNIT_ID identifies a concurrent program from
FND_CONCURRENT_PROGRAMS if REQUEST_UNIT_TYPE = P, an application
from FND_APPLICATIONS if REQUEST_UNIT_TYPE = A, or a request set from
FND_REQUEST_SETS if REQUEST_UNIT_TYPE = S.
Major Columns
APPLICATION_ID (PK)
REQUEST_GROUP_ID (PK)
REQUEST_UNIT_TYPE (PK)
UNIT_APPLICATION_ID (PK)
REQUEST_UNIT_ID
.....................................................................................................................................................
3-16
Security Tables: Responsibility Tables

.....................................................................................................................................................

Oracle Application Object
Library: Security
FND_RESPONSIBILITY
assigned
to
FND_USER
has
associated
with
FND_USER_
RESPONSIBILITY
associated
FND_RESP_
FUNCTIONS
Responsibility Tables
The major tables storing responsibility data are as follows:
FND_RESPONSIBILITY
FND_RESP_FUNCTIONS
FND_RESPONSIBILITY
This table stores the definition of a responsibility, and identifies the menu, data group,
and request group associated with that responsibility. A responsibility may be defined
to access either the standard applications or the Self-Service Web Applications. If the
value in the VERSION column = 4, then the responsibility is intended to access the
standard application forms. If the value in the VERSION column is W, then the
responsibility will be able to access Self-Service Web Applications forms. A
responsibility cannot access both the standard forms and Self-Service Web
Applications from the same menu. This table has a two-part primary key, consisting of
APPLICATION_ID and RESPONSIBILITY_ID. When creating new responsibilities
as part of an implementation, the APPLICATION_ID referenced in the table should be
a custom application so the responsibility records specific to your implementation
survive an upgrade.
.....................................................................................................................................................
3-17

.....................................................................................................................................................
FND_RESPONSIBILITY (continued)
This table is populated during the AutoInstall process and any upgrades process with
superuser responsibility records for each application for which you have purchased
a license. Oracle recommends that as part of your implementation process that you
review the menus associated with these superuser responsibilities and create new
responsibilities for your implementation which use those menus but exclude specific
submenus/functions (see FND_RESP_FUNCTIONS).
Major Columns
APPLICATION_ID (PK)
RESPONSIBILITY_ID (PK)
RESPONSIBILITY_NAME
RESPONSIBILITY_KEY
MENU_ID
DATA_GROUP_ID
DATA_GROUP_APPLICATION_ID
REQUEST_GROUP_ID
GROUP_APPLICATION_ID
VERSION
Instructor Note
Navigate to the Responsibilities window (responsibility: System Administrator):
(N)Security>Responsibility>Define
FND_RESPONSIBILITY_TL
This table stores the translated information about responsibilities in multiple
languages.
Major Columns
APPLICATION_ID (PK)
LANGUAGE
RESPONSIBILITY_NAME
SOURCE_LANG
.....................................................................................................................................................
3-18

.....................................................................................................................................................
FND_RESP_FUNCTIONS
This table identifies the specific submenus or functions to exclude from the menu
associated with the given responsibility. If RULE_TYPE = F, you are excluding a form
function. The ACTION_ID in this case is the FORM_FUNCTION_ID from
FND_FORM_FUNCTIONS table. If RULE_TYPE = M, you are excluding a
submenu. The ACTION_ID in this case is a MENU_ID from FND_MENUS table.
Major Columns
APPLICATION_ID (PK)
RULE_TYPE (PK)
ACTION_ID (PK)
Instructor Note
Navigate to the Responsibility window (responsibility: System Administrator):
(N) Security>Responsibility>Define
.....................................................................................................................................................
3-19

.....................................................................................................................................................
Security Tables: Application User Tables

Library: Security
FND_RESPONSIBILITY
assigned
to
FND_USER
has
associated
with
FND_USER_
RESPONSIBILITY
PER_ALL_PEOPLE_F
associated
FND_RESP_
FUNCTIONS
Application User Tables

The major tables storing application user information are:
PER_ALL_PEOPLE_F
FND_USER
FND_USER_RESPONSIBILITY
Instructor Note
PER_ALL_PEOPLE_F is an HRMS application table.
PER_ALL_PEOPLE_F
This is the table that holds personal information for employees, contacts, and other
people. Although this table is owned by Human Resources, employee information is
stored in this table for purchase requisitioners, buyers, order entry sales people, and so
on.
Major Columns
PERSON_ID (PK)
FULL_NAME
.....................................................................................................................................................
3-20
Security Tables: Application User Tables

.....................................................................................................................................................
FND_USER
This table stores the application user information. Each row includes the users
username (what a user types in at the signon screen), password and information on
when the user should change the password. Customer and supplier information entered
in this window is used to identify users who will access the application using SelfService Web Applications. Employee information is used by applications such as
purchasing to determine what the application user is allowed to do within the
application (approval limits for purchase orders, and so on).
Major Columns
USER_ID (PK)
USER_NAME
CUSTOMER_ID (for OSSWA)
SUPPLIER_ID (for OSSWA)
EMPLOYEE_ID
Instructor Note
Navigate to the Users window (responsibility: System Administrator):
FND_USER_RESPONSIBILITY
This table stores information about the responsibilities that are assigned to a user in
each application. Responsibilities for a user are specified in the Responsibilities
alternate region in the Users window. A user can access more than one responsibility;
the same responsibility can be accessed by more than one user.
Major Columns
USER_ID (PK)
APPLICATION_ID (PK)
Instructor Note
Navigate to the Users window (responsibility: System Administrator):
.....................................................................................................................................................
3-21

.....................................................................................................................................................
Application Object Library: Profile Options

AOL: Operating Profiles
User
Affects a
specific user
Overrides
Responsibility
Application
Affects users
of the same
responsibility
Affects users
of a given
application
Affects users
at a given site
Site
Operating Profiles
Applications system administrators use operating profiles to cause applications to
react in different ways for different users. For example, a system administrator would
set up only specific users to have access to a particular screen that contains secure
information.
Profile levels are a hierarchy, with the user at the highest level, followed by
responsibility, application, and finally site. Higher-level options override lower-level
options. For example, if a site-level printer value is Atlanta, but your user level
printer is Boston, then your reports are printed on the Boston printer.
.....................................................................................................................................................
3-22
Application Object Library: Profile Options

.....................................................................................................................................................
AOL: Operating Profiles
User
Responsibility
Application
Site
Printer:
Boston
Audit trail:
Inactive
Report copies: 2
Changed
at user
level
Printer:
Atlanta
Audit trail:
Inactive
Report copies: 1
Printer:
Atlanta
Audit trail:
Active
Report copies: 1
Changed at
application
level
Printer:
Atlanta
Audit trail:
Inactive
Report copies: 1
Profile Options
Common User Profile Levels

The following list of user profile options affects all Oracle Applications products.
Only those options are listed that you can view or change at the user level by using the
Personal Profile Values window. These user profile options affect your user interface
and the behavior of Oracle Applications features such as concurrent processing and
flexfields.
Printer: You can select which printer prints your reports. If a printer cannot be
selected, contact your system administrator. Printers must be registered with
Oracle applications.
Folders: Allow Customization.
Folder: Your system administrator can control whether you can create or
customize a folder definition layout in a folder block.
Flexfields, Autoskip: You can save keystrokes when entering data in your
flexfields by automatically skipping to the next segment as soon as you enter a
valid value into a segment.
Currency, Thousands Separator: You can separate your currency amounts in
thousands by placing a thousands separator; for example, a comma every three
digits (or 103 power).
.....................................................................................................................................................
3-23

.....................................................................................................................................................
Security Tables: Profile Option Tables

Library: Profile Options
APP
LEVEL
FND_PROFILE_OPTION_VALUES
SITE
RESP
LEVEL
LEVEL
defined
for
defined
for
have
FND_
PROFILE_
OPTIONS
identified
with
have
defined
for
USER
LEVEL
defined
for
have
FND_RESPONSIBILITY
owned by
using
owner of
FND_APPLICATION
Tables Storing Profile Options

The major profile option tables used by Oracle Applications are as follows:
FND_PROFILE_OPTIONS
FND_PROFILE_OPTIONS
This table stores information the profile options created by the Oracle application
developers to control how the applications function. The AutoInstall process populates
this table with all of the predefined profile options. Each profile option is uniquely
identified by APPLICATION_ID and PROFILE_OPTION_ID. If you create new
profile options during an implementation, the APPLICATION_ID should be that of a
custom application so that the records will not be overwritten during an upgrade.
.....................................................................................................................................................
3-24
Security Tables: Profile Option Tables

.....................................................................................................................................................
FND_PROFILE_OPTIONS (continued)
Major Columns
APPLICATION_ID (PK)
PROFILE_OPTION_ID
PROFILE_OPTION_NAME
DESCRIPTION
SQL_VALIDATION
Instructor Note
Navigate to the Profiles window (responsibility: Application Developer):
(N) Profile
This table stores values for user profile options set up from the System Profile Values
window. AOL uses the information in this table to operate applications according to
user profiles.
Major Columns
APPLICATION_ID (PK)
PROFILE_OPTION_ID
LEVEL_ID
LEVEL_VALUE
PROFILE_OPTION_VALUE
Instructor Note
Navigate to the System Profile Values window (responsibility: System Administrator):
(N) Profile>System
In the Find System Profile Values window, select the Responsibility check box. Use
the LOV to pick a responsibility (for example, GL, Vision Operations) in the
Responsibility field. In the Profile Field, use the LOV to pick a profile (for example,
Journals: Allow Posting During Journal Entry). Click the Find button to populate the
System Profile Values window.
.....................................................................................................................................................
3-25

.....................................................................................................................................................
Security: Folders
Folders
Folder forms can be identified by the folder icon in the upper left corner of the form. A
folder provides a means of limiting what is displayed in the form by controlling the
Query criteria as well as the layout. A folder definition can be assigned to a group of
users at the responsibility level, or directly to a user, thus limiting the records/columns
that a user sees from the underlying table. For example, you could define a folder in
the Enter Journals window, displayed above, which shows only the journal entries
whose source is Payables. You can then assign the folder to the Payables Manager
responsibility.
Whenever a user with the Payables Manager responsibility accesses the Enter Journal
window, he or she would see only journal entries which came from Payables. The
ability to modify a folder is controlled through the setting of the Folders: Allow
Customization profile option which can be set to No at the responsibility level so that
only managers or the system administrator can modify folder definitions.
.....................................................................................................................................................
3-26
Security Tables: Folder Tables

.....................................................................................................................................................
Security Tables: Folder Tables

Library: Folders
FND_FOLDERS
have
designated as
be part of
FND_FOLDER_COLUMNS
accessing
FND_DEFAULT_FOLDER
Folder Tables
The following tables store folder information:
FND_FOLDERS
FND_FOLDER_COLUMNS
FND_DEFAULT_FOLDERS
FND_FOLDERS
This table contains the definition of a folder, including the query criteria
Major Columns
FOLDER_ID (PK)
OBJECT
NAME
WHERE_CLAUSE
.....................................................................................................................................................
3-27

.....................................................................................................................................................
FND_FOLDER_COLUMNS
This table identifies the specific columns from the view behind the folder form which
should be displayed when this folder is chosen.
Major Columns
FOLDER_ID (PK)
ITEM_NAME
FND_DEFAULT_FOLDERS
This table links a specific folder definition to a user. Whenever the assigned user
enters a folder form, he or she sees only the default attached folder.
Major Columns
FOLDER_ID
USER_ID
.....................................................................................................................................................
3-28
Practice 3-1 Overview

.....................................................................................................................................................

This practice covers the following topics:
Creating a custom application

Creating a concurrent program
Creating a data group
Creating a custom form function
Creating a menu
Creating a request group
Creating a responsibility
Creating a user
Performing This Practice

For detailed instructions on completing this practice, see Practice 3-1 in Appendix C,
Practices and Solutions.
.....................................................................................................................................................
3-29

.....................................................................................................................................................

This practice covers writing a SQL*Plus script to list

user details.

.....................................................................................................................................................
3-30
Concurrent Requests, Programs, and Managers

.....................................................................................................................................................
Concurrent Requests, Programs, and Managers

Concurrent Requests, Programs,
and Managers
Request Table
User submits
request to run
program abc
Run program ...

Run program ...
Run program ...
Run program abc
Run program ...
Concurrent
manager
Concurrent
manager
starts
program abc
Concurrent Processing
Concurrent processing simultaneously executes programs running in the background
with online operations. Oracle Applications programs can run concurrently with each
other as well as with other programs; they are referred to as concurrent programs.
Requests to run Oracle Applications programsfor example, to run an Oracle General
Ledger reportare concurrent requests. Each concurrent request inserts a row into a
database table (FND_CONCURRENT_REQUESTS) maintained by the Oracle
Application Object Library. Concurrent managers read requests from the requests
table and start concurrent programs.
When you run a concurrent program, the system must determine the application that
owns the program and its execution method. The identity of the application that owns
the program determines the name of the subdirectory under which reports and
programs for that application are stored. The method of execution determines the
subdirectory in the applications directory structure that contains the executable file
for the concurrent program.
Instructor Note
The link between the name of a concurrent program run by the user and an executable
file on the database server was discussed in Lesson 2. You may want to review
Lesson 2.
.....................................................................................................................................................
3-31

.....................................................................................................................................................
Concurrent Processing (continued)

You, as a user, can run any request available in the request group associated with the
responsibility you are logged in with. You can specify resubmission intervals for the
request so that it will run on some periodic basis without human intervention.
You can also view your request output, diagnostic information about your request, and
the log file associated with your request.
Depending upon the setting of the profile option controlling your report access level,
you can also see the output of the request submitted by other users who are logged in
using the same responsibility as you.
The system administrator can view information about concurrent requests, and can
also do the following:
Change the priority of a request to a lower number so that it runs sooner (not
faster: a three hour request still takes three hours).
Put a request on hold or take it off of hold.
Cancel a request.
Change the resubmission options for a request.
Instructor Note
Demonstrate the process for running a concurrent request. The demonstration would
set the stage for the tables discussed in the following subsections.
.....................................................................................................................................................
3-32
Request ID
.....................................................................................................................................................
Request ID
Requests
(N) Concurrent>Requests
The Request ID
Oracle Applications assigns a request ID to each request submission so that you can
identify the results of the request when it is complete.
You can use the request ID to query for your request output in the Requests window.
Oracle Applications also assigns a new request ID number to each resubmission of a
request and displays the request ID in the log file of the previous request.
.....................................................................................................................................................
3-33

.....................................................................................................................................................
Concurrent Processing Tables

Oracle Application Object Library:
Concurrent Processing
requestor
FND_RESPONSIBILITY of
submitted
from
accessing
tools via
assigned
accessed by
to
FND_ORACLE_
USER_ID
FND_USER
has
associated
with
FND_USER_
RESPONSIBILITY
FND_CONCURRENT_
REQUESTS
for
associated
with
FND_CONCURRENT_
PROGRAMS
executed by
having
FND_EXECUTABLES

Oracle Applications uses the following major tables for storing information related to
concurrent processing. The following pages detail the significance of these tables and
their roles.
FND_CONCURRENT_REQUESTS
FND_USER
FND_RESPONSIBILITY
FND_ORACLE_USER_ID
FND_CONCURRENT_QUEUES
Instructor Note
Most of these tables (FND_EXECUTABLES, FND_CONCURRENT_PROGRAMS,
FND_USER, FND_RESPONSIBILITY, and FND_ORACLE_USER_ID) have
already been discussed earlier in this lesson.
.....................................................................................................................................................
3-34

.....................................................................................................................................................
FND_CONCURRENT_REQUESTS
This table stores all of the information about any given concurrent request as entered
using the Requests window. A record is written to this table each time a request is
submitted. Application Object Library automatically updates this table as the request
status changes. To monitor performance you need to query this table to find items
hindering performance (for example, request submitted with no arguments).
Major Columns
REQUEST_ID (PK)
REQUEST_DATE
REQUESTED_BY
PRIORITY
ORACLE_ID
PROGRAM_APPLICATION_ID
CONCURRENT_PROGRAM_ID
RESPONSIBILITY_APPLICATION_ID
RESPONSIBILITY_ID
ACTUAL_START_DATE
REQUEST_CLASS_APPLICATION_ID
CONCURRENT_REQUEST_CLASS_ID
ACTUAL_COMPLETION_DATE
ARGUMENT 1 .... 25
Instructor Note
Navigate to the Requests window (responsibility: System Administrator):
(N) Concurrent>Requests
.....................................................................................................................................................
3-35

.....................................................................................................................................................
Application Object Library: Concurrent Managers

Concurrent Requests, Programs,
and Managers
Request Table
User submits
request to run
program abc
Run program ...

Run program ...
Run program ...
Run program abc
Run program ...
Concurrent
manager
Concurrent
manager
starts
program abc
Specialized Concurrent Managers

Specialized concurrent managers are usually defined to spread out the processing
workload. For example, you may have certain programs that you want to run only
during the night because they take a long time to complete.
An internal manager (that manages all of the concurrent managers) and a single
concurrent manager called the standard manager (that runs 24 hours a day, seven days
a week and can run any program) are available after you install Oracle Applications.
If you need to create a specialized concurrent manager, you must do the following:
1 Define workshifts.
2 Define a concurrent manager and specify its cache size and the workshifts during
which it should operate. For each workshift, you should specify the number of
processes that can be run concurrently (target processes), and how often the
concurrent manager should check the queue for caching the processes to be run
(sleep seconds).
3 Optionally, define specialization rules to identify the programs that the concurrent
manager can run.
.....................................................................................................................................................
3-36
Application Object Library: Concurrent Managers

.....................................................................................................................................................
Specialized Concurrent Managers (continued)

When you first create a concurrent manager, it can run any program. The
specialization rules limit the manager so that it can run only the programs that meet the
specified criteria.
There are two kinds of specialization rules:
Standard Specialization Rules This type of specialization rule has elements that
are connected using the OR logical operator, which means that the request will be
run as long as it meets any of the specialization rule requirements.
Combined or Complex Specialization Rules This type of specialization rule has
elements that are connected using the AND logical operator. This means that in
order for a request to be run by a manager, it must meet all of the specialization rule
requirements.
Instructor Note
Set up a customized concurrent manager that will operate between 10:00 pm and 2:00
am Monday through Friday and run only certain requests. At each step talk about the
tables being updated in the process (responsibility: System Administrator). For
detailed steps and class discussion questions, please see the Instructor Note at the end
of this lesson.
1 From the Work Shift window, define two work shifts, Weeknight late1 and
Weeknight late2. Define them to run from 22:00 to 23:59 Monday through Friday
and 00:00 to 02:00 Tuesday through Saturday.
2 From the Concurrent Managers window, create a custom concurrent manager
called XX Specialized Manager. Choose FNDLIBR as the program library. Enter a
cache size of 4.
3 Open the Work Shifts window. Select the Weeknight late1, and Weeknight late2
work shifts and assign target processes of 3 and sleep seconds of 60.
4 From the Specialization Rules window, include the Active Users program and the
user VISION.
5 Open the Combined Specialization Rules window and create a combined rule
called Active Responsibilities Report with the description Active
Responsibilities Report only when submitted by TGREEN. Include user
TGREEN and the Active Responsibilities report.
6 Open the Concurrent Managers window and query up XX Specialized Manager.
Now open the Specialization Rules window and include your combined rule as
part of the specialization rules. Save and close the Specialization Rules window.
.....................................................................................................................................................
3-37

.....................................................................................................................................................
Balancing Process Workload

Cache Size, Target Processes,
and Sleep Seconds
1
Cache
size
2
3
4
10
20
30
40
50
60
Seconds
Cache size: 4
Target processes: 3
Sleep seconds: 60
Balancing Process Workload

The cache size and the number of target processes along with sleep seconds determine
the processing efficiency of the concurrent manager.
Cache Size Cache size specifies the buffer size which determines the number of
requests a concurrent manager should remember each time it checks the list of waiting
requests.
Processes Processes determines the maximum number of concurrent requests that a
manager can run at any one time. All the request picked up by the concurrent manager
(based on the cache size) will be available for processing. However, the actual number
of requests processed at any given time will depend on the number of target processes
you specify. In the example illustrated in the slide, the concurrent manager will
remember four (since cache size = 4). However, only three of those will be processed
simultaneously (since process = 3) The remaining request will be cached until one of
the request is processed.
Sleep Seconds The interval after which the concurrent manager will look for
requests for caching. A sleep second value of 60 seconds means that the concurrent
manager will look for processes after every 60 seconds to fill up the cache.
In the example depicted in the slide, process 1 finishes after 20 seconds. Process 4
starts at this time. All the cached processes are completed in 50 seconds. During the
remaining 10 seconds, the concurrent manager remains idle.
.....................................................................................................................................................
3-38
Concurrent Manager Table Relationships

.....................................................................................................................................................

Concurrent Managers
FND_CONCURRENT_TIME_PERIODS
Work shift
constrains time of
Concurrent Manager
specialized
with
run during
specializing
FND_CONCURRENT_
QUEUE_CONTENT
Rules
assigned to
runs
during
FND_CONCURRENT_
QUEUE_SIZE
Assigned work shift
Concurrent Manager Tables

Oracle Applications use the following major concurrent manager tables.
FND_CONCURRENT_QUEUE_SIZE
FND_CONCURRENT_QUEUE_CONTENT
FND_CONCURRENT_COMPLEX_RULES
FND_CONCURRENT_COMPLEX_LINES
This table stores information about concurrent processing work shifts. Each row
contains the name of the work shift and the days and times it covers. Work shifts can
be assigned to hours in a day, days in a week, or specific days in the year.
When work shifts overlap, the work shift with the more specific time period takes
effect for the overlapping time period. For example, a work shift on January 1
overrides a work shift from 9:00 a.m. to 5:00 p.m. on Monday through Friday.
When work shifts with the same priority overlap, the work shift with the largest
number of target processes takes effect.
.....................................................................................................................................................
3-39

.....................................................................................................................................................
FND_CONCURRENT_TIME_PERIODS (continued)
Major Columns
APPLICATION_ID (PK)
CONCURRENT_TIME_PERIOD_ID (PK)
CONCURRENT_TIME_PERIOD_NAME
START_TIME
END_TIME
FROM_WEEK_DAY
TO_WEEK_DAY
SPECIFIC_DATE
Instructor Note
Navigate to the Work Shifts window (responsibility: System Administrator):
(N) Concurrent>Manager>Work Shifts
This table stores information about concurrent managers. Each row includes the name
and description of a concurrent manager, as well as the values that identify the
program library attached to the manager. CACHE_SIZE contains the buffer size (how
many requests a concurrent manager should remember each time it checks the list of
waiting requests).
Major Columns
APPLICATION_ID (PK)
CONCURRENT_QUEUE_ID (PK)
CONCURRENT_QUEUE_NAME
DESCRIPTION
CACHE_SIZE
PROCESSOR_APPLICATION_ID
CONCURRENT_PROCESSOR_ID
Instructor Note
Navigate to the Concurrent Managers window (responsibility: System Administrator):
(N) Concurrent>Manager>Define
.....................................................................................................................................................
3-40

.....................................................................................................................................................
FND_CONCURRENT_QUEUE_SIZE
This table stores information about the work shifts assigned to a concurrent manager.
AOL uses the information in this table to allow system administrators to tailor
concurrent processing throughput to the needs of the site. MAX_PROCESSES
indicate the number of requests a manager can run during the specified work shift.
Major Columns
QUEUE_APPLICATION_ID (PK)
CONCURRENT_TIME_PERIOD_ID (PK)
MAX_PROCESSES
SLEEP_SECONDS
Instructor Note
Navigate to the Work Shifts window (responsibility: System Administrator):
(N) Concurrent>Manager>Define (B) Work Shifts
FND_CONCURRENT_QUEUE_CONTENT
This table stores information about standard specialization rules. AOL uses this
information to control the requests a concurrent manager can process.
Major Columns
QUEUE_APPLICATION_ID (PK)
TYPE_CODE (PK) *
TYPE_APPLICATION_ID (PK)
TYPE_ID (PK)
INCLUDE_FLAG
* Indicates inclusion of a program (P), user (U), combined rule (C), and so on.
Instructor Note
Navigate to the Specialization Rules window (responsibility: System Administrator):
(N) Concurrent>Manager>Define (B) Specialization Rules
.....................................................................................................................................................
3-41

.....................................................................................................................................................
FND_CONCURRENT_COMPLEX_RULES
This table stores information related to the combined specialization rules. AOL uses
this information to determine the requests a concurrent manager can process.
Major Columns
APPLICATION_ID (PK)
COMPLEX_RULE_ID
COMPLEX_RULE_NAME
Instructor Note
Navigate to the Combined Specialization Rules window (responsibility: System
Administrator):
(N) Concurrent>Manager>Rule
FND_CONCURRENT_COMPLEX_LINES
This table stores information related to the rule lines that make up combined
specialization rules. AOL uses this information to determine the requests a concurrent
manager can process.
Major Columns
APPLICATION_ID (PK)
COMPLEX_RULE_ID (PK)
COMPLEX_RULE-LINE_ID
INCLUDE_FLAG
TYPE_CODE
TYPE_APPLICATION_ID
TYPE_ID
Instructor Note
Navigate to the Combined Specialization Rules window (responsibility: System
Administrator):
.....................................................................................................................................................
3-42
Application Object Library: Flexfields

.....................................................................................................................................................
Application Object Library: Flexfields

Adapting Oracle Applications
Oracle General Ledger
Oracle Assets
Application
windows
User-defined flexfield windows
Using Flexfields to Adapt Applications

A flexfield is a multi-segment pop-up window that opens from a regular Oracle
Applications window. Defining and using flexfields enables you to adapt Oracle
Applications to reflect your own business environment. You can easily define
flexfields to extend Oracle Applications functionality without custom programming.
Different Types of Flexfields
There are two types of flexfields, key flexfields and descriptive flexfields. Key
flexfields are used to define your own structure for many identifiers required by
Oracle Applications, while descriptive flexfields are used to gather additional
information in a form beyond the information explicitly required by Oracle
Applications.
.....................................................................................................................................................
3-43

.....................................................................................................................................................
Descriptive Flexfields
__ Sale Information ________________________
Transaction
3987
Payment Type
CC
Customer Jane Doe

Item COM-876-LTN
Description Computer - Monitor - Light Tan
Payment Type CK
Store 54321
Dept 987
Number 1028
Second ID MC 4565-3939
[]
Payment Type CC
Store 54321
Dept 987
Number 4958-2938-4747
Exp. Dt 12 - 99
Using Descriptive Flexfields

You use descriptive flexfields to collect information beyond that required by Oracle
Applications. Using descriptive flexfields enables you to gather additional specialized
information required by your business. The use of descriptive flexfields is optional.
A descriptive flexfield appears on a form as a single-space field enclosed by brackets.
If the flexfield is enabled, it opens when you click in the bracketed field.
A descriptive flexfield offers you several options:
You can define a basic structure that asks the same questions for each record
(called global segments).
You can define a structure which contains a question (the context question), the
answer to which controls what other questions are asked (the context segments).
You can define a structure, which includes global segments and a context question
with context segments.
The example shows a descriptive flexfield that gathers different payment information
based on the type of payment: check (CK) or credit card (CC).
.....................................................................................................................................................
3-44
Defining Descriptive Flexfields

.....................................................................................................................................................

Descriptive Flexfields/Attribute Columns
Record 2
Record 1
AGE
GENDER
37
F
HOW?
SHOES
WALK
ATHLETIC
VENDOR
NIKE
AGE
43
GENDER
HOW?
M
DRIVE
CAR MAKE
HONDA
CAR MODEL
CIVIC
GL_JE_SOURCES
SOURCE_NAME ATTRIBUTE1 ATTRIBUTE2 CONTEXT ATTRIBUTE3 ATTRIBUTE4
PAYABLES
37
WALK
ATHLETIC
NIKE
INVENTORY
43
DRIVE
HONDA
CIVIC
GL_JE_SOURCES_DFV
SOURCE_NAME
AGE GENDER HOW? SHOES
PAYABLES
37
WALK ATHLETIC NIKE
VENDOR CAR MAKE
INVENTORY
43
DRIVE
HONDA
CAR MODEL
CIVIC

1 Attend the Oracle Flexfields class.
2 Plan. Look at the flexfield registry and determine the number of attribute columns
available. Decide what your questions and answers will be and if there will be a list
of correct answers. If you decide to use a list of answers, determine where that list
will come froman existing application table or a custom list.
3 Create value set definitions to describe what the answers to your questions will
look like (data type, width, and so on) and where they will come from. In the
example, the age answer is unvalidated, the shoes and car make answers are
validated against an independent list of values, the car model answer is validated
against a list of answers dependent on the car make and vendor answer is
validated against a list of values in the PO_VENDORS table.
4 Define the descriptive flexfield structure.
a Define the global segments. Specify segment name, the attribute column the
stored data will be stored in, and the value set whose definition controls where
the list of answers comes from and what it looks like. In the example in the
slide, age and gender are global segments.
b Define the context question (How do you get to work?).
.....................................................................................................................................................
3-45

.....................................................................................................................................................
Defining Descriptive Flexfields (continued)

c Define each of the possible answers to the context question. Each of these
answers will have a set of questions associated with it.
d For each of the answers to the context question, define the segments and
questions associated with the answers. In the example, walk has the shoes
and vendor questions and drive has the car make and car model questions.
e Compile the structure. Compiling creates a view as illustrated in the slide. The
columns in the view have the same names as the segments. The view is
normally used for reporting.
5 Define the lists of values for all the answers where the validation type is
independent or dependent. In the example, this would include shoes, car make, and
car model.
.....................................................................................................................................................
3-46
Descriptive Flexfields: Table Relationship

.....................................................................................................................................................

FND_DESCR_FLEX_COLUMN_USAGES
validated
against
a portion of
used by
made up of
FND_FLEX_VALUE_SETS
FND_FLEX_
FND_FLEX_
VALIDATION_ NONE
VALUES
TABLES
TABLE
used by
FND_DESCR_
FLEX_CONTEXT
a
portion
of
using
APPLICATIONS
TABLE
FND_DESCRIPTIVE_FLEXS
Descriptive Flexfield Tables

descriptive flexfields. The following pages detail the significance of these tables and
their roles.
FND_DESCRIPTIVE_FLEXS_TL
FND_FLEX_VALUE_SETS
FND_DESCR_FLEX_CONTEXTS
FND_DESCR_FLEX_CONTEXTS_TL
FND_FLEX_VALUES
.....................................................................................................................................................
3-47

.....................................................................................................................................................
This table contains the registry of descriptive flexfields as defined by Oracle
application developers. Each row includes the name of the table that contains the
descriptive flexfield columns, the title of the flexfield by which the user identifies the
flexfield, and the name of the field that contains the structure definition. The
AutoInstall process populates this table. Please note that descriptive flexfield title is
not stored in this table, but in the FND_DESCRIPTIVE_FLEXS_TL table.
Major Columns
APPLICATION_ID (PK)
DESCRIPTIVE_FLEXFIELD_NAME (PK)
APPLICATION_TABLE_NAME
TITLE
TABLE_APPLICATION_ID
CONTEXT_COLUMN_NAME
Instructor Note
Navigate to the Descriptive Flexfield window (responsibility: Application Developer):
(N) Flexfield>Descriptive>Register
FND_DESCRIPTIVE_FLEXS_TL
This table stores translated setup information about descriptive flexfields. Each row
includes the name and title of the descriptive flexfield, the reference field prompt, the
identifier of the application with which the flexfield is registered, and the language
code representing the language this information is stored in. You need one row for
each descriptive flexfield in each of the installed language. Please note that descriptive
flexfield title is stored in this table, not in the FND_DESCRIPTIVE_FLEXS table.
Major Columns
APPLICATION_ID (PK)
LANGUAGE
SOURCE_LANG
TITLE
.....................................................................................................................................................
3-48

.....................................................................................................................................................
FND_FLEX_VALUE_SETS
This table stores the name and description of the value set, as well as the type of
validation. There are six types of validation:
F = Table
I = Independent
D = Dependent
N = None
V = Special
P = Pair
This table is used by both key and descriptive flexfields. AOL uses this table to assign
groups of valid values to flexfield segments.
Major Columns
FLEX_VALUE_SET_ID (PK)
FLEX_VALUE_SET_NAME
FORMAT_TYPE
MAXIMUM_SIZE
VALIDATION_TYPE
PARENT_FLEX_VALUE_SET_ID
DEPENDANT_DEFAULT_VALUE
Instructor Note
Navigate to the Value Sets window (responsibility: System Administrator):
(N) Application>Validation>Set
.....................................................................................................................................................
3-49

.....................................................................................................................................................
FND_FLEX_VALIDATION_TABLES
This table stores information on key and descriptive flexfield validation tables. Each
row includes values identifying table validated value set, the application owning the
value set, and the name of the application table used as the validation table
(APPLICATION_TABLE_NAME). Each row also includes the names of the columns
that contain ID type values and meanings as well as the size and the type of each of
these columns, and additional columns to display for List of Values. AOL uses the
information in this table to allow users to use application tables to ensure that flexfield
segments contain valid values.
Major Columns
APPLICATION_ID
VALUE_COLUMN_NAME
VALUE_COLUMN_TYPE
VALUE_COLUMN_SIZE
ID_COLUMN_NAME
ID_COLUMN_TYPE
MEANING_COLUMN_NAME
MEANING_COLUMN_SIZE
MEANING_COLUMN_TYPE
MAXIMUM_SIZE
FND_DESCR_FLEX_CONTEXTS
This table stores context field values (also known as structure names) for descriptive
flexfields. For each value of DESCRIPTIVE_FLEX_CONTEXT_CODE in this table,
there will be one or more records in the FND_DESCR_FLEX_COLUMN_USAGES
table.
Major Columns
APPLICATION_ID (PK)
DESCRIPTIVE_FLEX_CONTEXT_CODE (PK)
GLOBAL_FLAG
Instructor Note
Navigate to the Descriptive Flexfield Segments window (responsibility: System
Administrator):
(N) Application>Flexfield>Descriptive>Segments
.....................................................................................................................................................
3-50

.....................................................................................................................................................
FND_DESCR_FLEX_CONTEXTS_TL
This table stores context field values (also known as structure names) for descriptive
flexfields in each of the installed languages. Each row includes an application
identifier, the descriptive flexfield name, context field value, a description of the
context field value and the language code indicating what language the value is in.
Major Columns
APPLICATION_ID (PK)
LANGUAGE (PK)
DESCRIPTIVE_FLEX_CONTEXT_NAME
SOURCE_LANG
This table stores information on each of the segments for a
DESCRIPTIVE_FLEX_CONTEXT_CODE in FND_DESCR_FLEX_CONTEXTS
table. Each record contains the name of the segment, the name of the ATTRIBUTE
column its values populate and the identity of the value set the segment uses.
Major Columns
APPLICATION_ID (PK)
APPLICATION_COLUMN_NAME (PK)
END_USER_COLUMN_NAME
FLEX_VALUE_SET_ID
DEFAULT_TYPE
DEFAULT_VALUE
SECURITY_ENABLED_FLAG
Instructor Note
Navigate to the Segments Summary window (responsibility: System Administrator):
(N) Application>Flexfield>Descriptive>Segments (B) Segments
.....................................................................................................................................................
3-51

.....................................................................................................................................................
FND_FLEX_VALUES
This table stores valid values for key and descriptive flexfield segments (entered from
the Segment Values window) to ensure that the user enters valid values in the flexfield
segments. AOL uses this table when you define values for value sets with a validation
type of Independent or Dependent.
Major Columns
FLEX_VALUE_ID
FLEX_VALUE
PARENT_FLEX_VALUE_LOW
PARENT_FLEX_VALUE_HIGH
Instructor Note
Navigate to the Segments Values window (responsibility: System Administrator):
(N) Application>Validation>Values (Values alternate region for descriptive
flexfield)
.....................................................................................................................................................
3-52
Key Flexfields
.....................................................................................................................................................
Key Flexfields
Key Flexfields
__ Sales Information ______________________

Transaction 3987
Standard
window
Payment Type
Customer Jane Doe

Item COM-876-LTN
[]
Description Computer - Monitor - Light Tan

Key
flexfield
window
__ Item Information _______________

COM
Item
Color
Computer
876
Monitor
LTN
Light tan
Using Key Flexfields

You use key flexfields to define your own structure for many identifiers required by
Oracle Applications. Generally, the identifier you create using a key flexfield is
required by the application (for example, the Accounting flexfield builds the account
number used by Oracle General Ledger).
A key flexfield appears as a normal field on a window. Any existing value for the key
appears in the field as a concatenated value having segment separators. When the
cursor moves into the flexfield, the entire window opens to allow entry of new data or
to display the existing data.
A key flexfield structure usually consists of multiple segments, each of which contains
meaningful information. The resulting combinations of values from these segments,
therefore, function as intelligent keys.
Many key flexfields are used by multiple applications. For example, the Accounting
Flexfield is used by both Oracle General Ledger and Oracle Payables.
.....................................................................................................................................................
3-53

.....................................................................................................................................................
Defining Key Flexfields

Key Flexfield Example: Locations
West
East
WHSE.SHELF.BIN.DRAWER
W01.S002.B05.D009
WHSE.SHELF.PALLET
W001.S12.P12
COMBINATIONS TABLE
STRUCTURE COMBINATION_ID SEGMENT1 SEGMENT2 SEGMENT3
EAST
0001
W01
S002
B05
WEST
0002
W001
S12
P12
ONHAND QUANTITIES TABLE

ITEM
BEAR
QUANTITY
15
LOCATION
0001
Key Flexfields
Key flexfields are multi-part unique identifiers that allow you to adapt the Oracle
Applications to reflect the way your company does business. Key flexfields are used
for account numbers, item identifiers, asset categories, and so on.
The example above does not exist in Oracle Applications, but provides a basis for
discussion. The combination which identifies a warehouse location for the East coast
warehouse has four segments, whose values are stored in SEGMENTS14 of a
combination table. For each record in the combinations table there is a unique record
identifier or combination ID. When the warehouse location is referenced in other
tables, what is stored is the combination ID, rather than the actual segment values.
This enables companies implementing the Oracle Applications to adapt the
applications to reflect their companies account numbers, item identifiers, and so on,
without customization.
1 Attend the Oracle Flexfields class.
2 Plan. Look at the flexfield registry and determine the number of SEGMENTS
available. Decide what your SEGMENTS will be based on your reporting needs.
.....................................................................................................................................................
3-54

.....................................................................................................................................................
Defining Key Flexfields (continued)

3 Create value set definitions to describe the values for each of your segments will
look like. For instance, in the example, segment1 of the EAST structure is three
characters long and allows alpha characters.
4 Define the key flexfield structure.
a Define the structure name and any information about the structure (is dynamic
insertion allowed, and so on).
b Define each of the segments in the structure, including the name of the
segment, the SEGMENTX column in the combinations table in which values
for that segment will be stored, and the value set associated with the segment,
which defines what values for that segment will look like.
c Compile the structure. Compiling the structure creates a view of the
combination table, in which the columns will have the same label as the
segments (for example, for the East structure, the columns in the view will be
labelled WHSE, SHELF, BIN, DRAWER).
5 Define the lists of values for each of your segments.
.....................................................................................................................................................
3-55

.....................................................................................................................................................
Key Flexfield Table Relationships

Key Flexfields
represented by
FND_ID_FLEXS
for
COMBINATIONS
TABLE
made
FND_ID_
up of
FND_ID_
FLEX_
FLEX_SEGMENTS
STRUCTURES a
portion
of
used
by
validated by
FND_FLEX_VALUE_SETS
FND_FLEX_
FND_FLEX_
VALIDATION_ NONE
VALUES
TABLES
Key Flexfield Tables

key flexfields. The following pages detail the significance of these tables and their
roles.
FND_ID_FLEXS
FND_ID_FLEX_STRUCTURES
FND_ID_FLEX_STRUCTURES_TL
FND_ID_FLEX_SEGMENTS
FND_FLEX_VALUE_SETS
FND_FLEX_VALUES
Instructor Note
FND_FLEX_VALUE_SETS and FND_FLEX_VALUES are discussed earlier in this
lesson.
.....................................................................................................................................................
3-56

.....................................................................................................................................................
FND_ID_FLEXS
This table stores registration information about key flexfields predefined by the Oracle
Application Developers. Each row includes the code that identifies the key flexfield,
the title of the flexfield (by which a user identifies the flexfield), the name of the
combinations table that contains the key flexfield data, and the name of the column in
the combinations table that identifies which structure a specific combination belongs
to. This table is populated by the AutoInstall process.
Major Columns
APPLICATION_ID (PK)
ID_FLEX_CODE (PK)
ID_FLEX_NAME
DYNAMIC_INSERTS_FEASIBLE_FLAG
Instructor Note
Navigate to the Key Flexfields window (responsibility: Application Developer):
(N) Flexfield>Key>Register
This table stores the header information about a specific structure for a specific key
flexfield. A structure for a particular key flexfield is identified by ID_FLEX_CODE
and ID_FLEX_NUM. Dynamic insertion is the option to allow creation of new
combinations where the combinations are used (such as the creation of an account
number in the journal entry window) rather than in the combinations form. Not all key
flexfields allow dynamic insertion. Cross validation is a process of identifying invalid
combinations that could not be created through the dynamic insertion process.
Note: To support multiple languages, the ID_FLEX_STRUCTURE_NAME column is
set to NULL in Release 11. The FND_ID_FLEX_STRUCTURES_TL table stores the
name.
.....................................................................................................................................................
3-57

.....................................................................................................................................................
FND_ID_FLEX_STRUCTURES (continued)
Major Columns
APPLICATION_ID (PK)
ID_FLEX_CODE (PK)
ID_FLEX_NUM (PK)
ID_FLEX_STRUCTURE_NAME
CROSS_SEGMENT_VALIDATION_FLAG
DYNAMIC_INSERTS_ALLOWED_FLAG
STRUCTURE_VIEW_NAME
Instructor Note
Navigate to the Key Flexfields window (responsibility: System Administrator):
(N) Application>Flexfields>Key>Segment
It is advisable to fill in the value of STRUCTURE_VIEW_NAME column and not
allow the default because it may be overwritten in a future upgrade. Use the same
value as the default, but add _KFV to the end of the name to stand for key flexfield
view. This keeps the integrity for any upgrades.
FND_ID_FLEX_STRUCTURES_TL
This view contains information about key flexfields in each of the installed languages.
Each row includes an application identifier, key flexfield code, structure number,
structure name, description of the structure, the shorthand window prompt, and the
language code indicating the language the information is in. You need one row for
each structure for every key flexfield in each of the installed languages.
ID_FLEX_STRUCTURE_NAME is stored in this table.
Major Columns
APPLICATION_ID(PK)
ID_FLEX_CODE (PK)
ID_FLEX_NUM (PK)
LANGUAGE
ID_FLEX_STRUCTURE_NAME
Instructor Note
This is a view and cannot be accessed from any of the windows.
.....................................................................................................................................................
3-58

.....................................................................................................................................................
FND_ID_FLEX_SEGMENTS
This table stores information about the segments associated with a specific structure of
a specific key flexfield. The structure is uniquely identified by ID_FLEX_CODE and
ID_FLEX_NUM. The information for each segment includes the segment number, the
segment name, the name of the SEGMENTX column in the combinations table where
values for that segment will be stored, and the value set which defines what the values
for the segment will look like and where they are stored.
Major Columns
APPLICATION_ID (PK)
ID_FLEX_CODE (PK)
ID_FLEX_NUM (PK)
SEGMENT_NUM
SEGMENT_NAME
APPLICATION_COLUMN_NAME
FLEX_VALUE_SET_ID
Instructor Note
Navigate to the Segments Summary window (responsibility: System Administrator):
(N) Application>Flexfields>Key>Segment (B) Segments
FND_FLEX_VALUE_SETS
This table stores the name and description of the value set, as well as the type of value
set entered from the Value Sets window.
Instructor Note
Navigate to the Value Sets window (responsibility: System Administrator):
(N) Application>Validation>Set
For a more detailed discussion of this table, please see Descriptive Flexfields:
Table Relationship section.
FND_FLEX_VALUES
This table stores valid values for descriptive and key flexfield segments (entered from
the Segment Values window) to ensure that the user enters valid values in the flexfield
segments.
Instructor Note
Navigate to the Segments Values window (responsibility: System Administrator):
(N) Application>Validation>Values (Values alternate region for key flexfield)
.....................................................................................................................................................
3-59

.....................................................................................................................................................
Summary
Summary
Application Object Library (AOL) contains all of

the common functions that Oracle Applications
modules share.
System administrators use AOL to manage

applications security, administer the concurrent
processing facility, and establish operating
profiles.
.....................................................................................................................................................
3-60

.....................................................................................................................................................

Based on the given business scenario, use SQL*Plus

to answer user inquiries.

Instructor Note
Set up a customized concurrent manager that will operate between 10:00 p.m.
and 2:00 a.m. Monday through Friday and run only certain requests. At each step talk
about the tables being updated in the process (responsibility: System Administrator).
1 Open the Work Shift window. Define two work shifts, Weeknight late1 and
Weeknight late2. Define the former to run from 22:00 to 23:59 Monday through
Friday and the latter to run from 00:00 to 02:00 Tuesday through Saturday. Save
the work shifts you have defined.
(N) Concurrent>Manager>Workshifts
2 Open the Concurrent Managers window. Create a custom concurrent manager
called XX Specialized Manager. Use your custom application as part of the name
and explain that this will protect this managers definition from being overwritten
during an upgrade. Choose FNDLIBR as the program library. Enter a cache size of
4 and explain that this manager can hold a maximum of four requests in memory at
any given time. Save your concurrent manager.
.....................................................................................................................................................
3-61

.....................................................................................................................................................

3 Click the Workshifts button to open the Work Shifts window. Select the Weeknight
late1, and Weeknight late2 work shifts and specify target processes of 3, which is
how many programs the manager can run at any given time. Assign sleep seconds
of 60, which is how often the manager will check the queue. Save, and close the
Work Shifts window.
4 Quiz the students on the programs this manager can now run.
Answer: Any program because specialization rules have not been assigned to this
manager.
5 Click the Specialization Rules button. Include the Active users program and the
user VISION. Save and Close the Specialization Rules window. Quiz the students
on the programs this manager can now run.
Answer: The Active Users program, regardless of who submitted it, and any
program submitted by user VISION.
6 Open the Combined Specialization Rules window and create a combined rule
called Active Responsibilities report only when submitted by TGREEN. Use
your application as part of the name. Include user TGREEN and the Active
Responsibilities report.
7 Open the Concurrent Managers window. Query up XX Specialized Manager and
click the Specialization Rules button to open the Specialization Rules window.
Include your combined rule in the specialization rules. Save and close the
Specialization Rules window.
8 Quiz the students on what this manager can now run.
Answer: The Active Users report regardless of who submitted it, anything
submitted by user Vision, and the Active Responsibilities report only if submitted
by user TGREEN.
9 Ask the students to name the manager that would run the Active Users report if
someone submitted it right now.
Answer: Whichever manager is available, unless you specialize the Standard
manager by excluding the Active users report from the list of programs that the
Standard manager can run.
.....................................................................................................................................................
3-62
4
.................................
Financial Applications:
An Overview

.....................................................................................................................................................
Objectives
Objectives

do the following:
List the Oracle Financial applications
Explain the Multi-Org Architecture
List the primary business functions that can be

performed using each Oracle Financial application
Explain the the use of Multiple reporting
currencies in Oracle Applications
Lesson Aim
The Oracle Financial applications discussed in this class include:
General Ledger
Purchasing
Accounts Payable
Fixed Assets
Inventory
Order Entry
Accounts Receivable
.....................................................................................................................................................
4-2

.....................................................................................................................................................

Oracle General Ledger is the central repository for

accounting information, receiving transactions from
financial subledgers.
Oracle
General Ledger
Manufacturing
subledgers
Financial
subledgers
General Ledger
Oracle General Ledger is the central repository for all of your financial information.
All of the other applications feed data to Oracle General Ledger, and your financial
reports, such as your income statement and balance sheet, are generated out of General
Ledger. The primary General Ledger functions discussed in this course are:
Journal Entries
Budget Information
Account Balances
.....................................................................................................................................................
4-3

.....................................................................................................................................................
Oracle Purchasing
Oracle Purchasing
Oracle
Inventory
Oracle
Payables
Oracle
Purchasing
Oracle
Order Entry
Oracle
General Ledger
Purchasing
The primary Purchasing functions discussed in this course are:
Supplier definition
Purchase requisition processing
Purchase order processing
Receipt of purchased material
Transfer of material receipt information to the General Ledger
.....................................................................................................................................................
4-4
Oracle Accounts Payable

.....................................................................................................................................................

Invoices
Purchase Orders
Vendors
Oracle Purchasing
Oracle Assets
Oracle Payables
Employees
Oracle Human
Resources
Invoice
payments
Units of measure
item information
Oracle
Inventory
Accounts Payable
Oracle Accounts Payable is fully integrated with Oracle Purchasing and Oracle
General Ledger. The primary Accounts Payable functions discussed in this course are:
Processing of supplier invoices/matching
Payment of supplier invoices
Transfer of invoice and payment information from Accounts Payable to General
Ledger
.....................................................................................................................................................
4-5

.....................................................................................................................................................
Oracle Fixed Assets

Oracle Fixed Assets
Invoice
lines
Supplier
information
Oracle Payables
Oracle Purchasing
Oracle Assets
Employees
Oracle Human
Resources
Journal
entries
Oracle General
Ledger
Units of measure
item information
Oracle
Inventory
Fixed Assets
The Oracle Fixed Assets module enables you to manage tracking and financial
information about both expensed and depreciable assets. Oracle Fixed Assets is fully
integrated with Oracle Accounts Payable. The primary Fixed Assets functions
discussed in this course are:
Asset Additions
Depreciation
Transfer of asset addition and depreciation information from Fixed Assets to
General Ledger
.....................................................................................................................................................
4-6
Oracle Inventory
.....................................................................................................................................................
Oracle Inventory
Oracle Inventory
Oracle
General Ledger
Oracle
Payables
External
systems
Oracle
Inventory
Oracle
Assets
Oracle
Receivables
Inventory
The Oracle Inventory module enables you to define your parts, including item
attributes and cost information. The primary Oracle Inventory functions discussed in
this course include:
Item definition
Item costing
Processing of material transactions: receipts and shipments
Transfer of material transaction information from Inventory to General Ledger
.....................................................................................................................................................
4-7

.....................................................................................................................................................
Oracle Order Entry

Oracle Order Entry
Returns, Credits,
Booked orders
Oracle Receivables
Internal
requisitions
Oracle Purchasing
Oracle Order Entry

Set of books
Units of measure item
Exchange rates
information
ATP/on-hand information
Oracle General
Ledger
Oracle
Inventory
Order Entry
The Order Entry module is fully integrated with Oracle Inventory to process material
shipments, and with Oracle Receivables for creation of customer invoices. The
primary Oracle Order Entry functions which are discussed in this course include:
Customer definition
Order processing
Transfer of shipment information to Oracle Inventory
Transfer of order information to Oracle Receivables for the purpose of creating
customer invoices
.....................................................................................................................................................
4-8
Oracle Receivables
.....................................................................................................................................................
Oracle Receivables
Oracle Receivables
Costs
Inventory
Oracle
Inventory
Inventory relief
RMAs receiving
Receipts
Adjustments
Orders
Return material
authorizations
Oracle
Order
Entry
Oracle Receivables
Receivables
The Receivables module is fully integrated with Oracle Order Entry so that customer
invoices can be created automatically from sales order information. The primary
Oracle Receivables functions that are discussed in this course include:
Processing of customer invoices
Processing of cash receipts
Transfer of customer invoice and cash receipt information from Oracle
Receivables to General Ledger
.....................................................................................................................................................
4-9

.....................................................................................................................................................
Integration Among the Oracle Financial Applications

Oracle Financials: General Workflow
Purchasing
Shared items
Acct. Generator
Matching
Inventory
Accrued
Receipts
Accounts
Payable
Mass Additions
Expense
Liabilities
Cash out
Fixed
Assets
Asset Transactions
Depreciation
Shared items
Inventory
Interface
Shared items
Order Entry
Auto accounting
Receivables interface
Auto invoices
Material receipts
Material shipments
COGs
Std. cost adjustments
Physical inventory
adjustments
General Ledger
Accounts
Receivable
A/R Assets
Sales revenue
Cash receipts
Financial statements
Integration of Oracle Financial Applications

A general overview of the data flow between the various Oracle Financial modules is
shown in the diagram above. A brief discussion of the shared entities, functions, and
what data is passed by each module to the General Ledger is included here for the
purpose of better understanding how data flows through the application tables. Where
appropriate in the sections on individual applications, a brief description is provided
regarding how that module passes data to the General Ledger.
Shared Entities
Vendors Vendors are defined in the PO_VENDORS table, discussed in the
purchasing section of this book. Vendor information is stored in a table, which is
shared by Purchasing, Accounts Payable, and Fixed Assets.
Account Numbers
Account numbers are defined in the GL_CODE_COMBINATIONS table discussed in
the General Ledger section of this book. Account numbers are referenced by all
applications.
.....................................................................................................................................................
4-10
Integration Among the Oracle Financial Applications

.....................................................................................................................................................
Shared Entities (continued)

Items Items are defined in the MTL_SYSTEM_ITEMS table, discussed in both the
purchasing and inventory sections of this manual. Item information is stored in a table,
which is shared by Purchasing, Inventory, Order Entry, and Accounts Receivable.
Customers Customers are defined in the RA_CUSTOMERS table, discussed in
both the Order Entry and Receivables sections of this manual. Customer information is
stored in a table, which is shared by Order Entry and Accounts Receivable.
Functions
In order to automate the process of generating account numbers in feeder systems,
Oracle Financial applications provide functions that can be set up during your
implementation to generate account numbers based on information entered in a screen.
There are two of these functions:
Account Generator The Account Generator (Flexbuilder in release 10.7) in release
11 can be used by the purchasing module to generate purchase order distribution
accounts, by Fixed Assets to generate various asset accounts, and by the Shipment
interface between order entry and inventory to generate the cost of goods sold account.
The Account Generator function takes parameters from the purchase order or
whatever as inputs and uses these to determine the appropriate account number.
AutoAccounting The AutoAccounting function is used by the Receivables module
to determine the appropriate account numbers for sales revenue, accounts receivable,
freight and taxes, based on inputs such as the salesperson, the item being invoiced, and
the type of invoice.
.....................................................................................................................................................
4-11

.....................................................................................................................................................
Processes That Pass Data Among Applications

Data Flow Among Applications
Oracle
Purchasing
Oracle Inventory
Oracle
Accounts Payable
Oracle
Order Entry
Oracle
Fixed Assets
Oracle
Accounts
Receivable
Purchasing to Accounts Payable

Data is copied out of purchasing tables into Accounts Payable tables when invoices
are received and matched against purchase order shipments.
Accounts Payable to Fixed Assets
When invoice information is entered in the Accounts Payable module for an item
which will become a fixed asset, such as a vehicle or a building, the MassAdditions
process can be used to create asset records from information entered in on the
Accounts Payable invoice. The MassAdditions process may use the Account
Generator function to determine the appropriate asset accounts.
Order Entry to Inventory
When material is shipped, the Inventory Interface process passes shipment
information from Oracle Order Entry to Oracle Inventory to decrement inventory item
quantities and to record cost of goods sold and a decrease in inventory asset value.
This process may use the Account Generator function to determine the appropriate
cost of goods sold account.
.....................................................................................................................................................
4-12
Processes That Pass Data Among Applications

.....................................................................................................................................................
Order Entry to Accounts Receivable

Once orders have been shipped, the Receivables interface and AutoInvoice processes
may be run to generate customer invoice records automatically from Sales order
information. The AutoInvoice process may use the AutoAccounting function
described above to determine the appropriate sales revenue, freight revenue, tax
revenue, accounts receivable, and account numbers.
.....................................................................................................................................................
4-13

.....................................................................................................................................................
Financial Data Passed to General Ledger by Other

Modules
Data Flow to General Ledger
Purchasing
Order Entry
Inventory
material shipping
accrued receipts
General Ledger
material receipts,
shipments, COGS
sales revenue,
expense, liability,
cash out
asset addition, transfers, accounts receivable,
cash in
depreciation, retirement
Payables
Assets
Receivables
Data Flow to General Ledger

Oracle General Ledger is the central repository for accounting information, receiving
transactions from other Oracle applications.
Purchasing
The only information passed to General Ledger by the purchasing module is accrued
receipt information (asset information for material received but not yet delivered, and
liability information for material received but not yet billed).
Accounts Payable
The Accounts Payable module passes expense and liability information from invoices
and cash and liability information from payments to the General Ledger.
Fixed Assets
The Fixed Asset module passes information about asset additions, asset transfers, asset
depreciation, and asset retirement to the General Ledger.
.....................................................................................................................................................
4-14
Financial Data Passed to General Ledger by Other Modules

.....................................................................................................................................................
Inventory
The Inventory module passes financial information about material receipts, material
shipments, cost of goods sold, changes in inventory asset value due to standard cost
adjustments, and changes in inventory asset value due to physical inventory
adjustments to the General Ledger.
Order Entry
The Order Entry module does not pass any information directly to the General Ledger.
When material is shipped, order entry passes information through the inventory
interface to the Inventory module to record the shipment, and Oracle Inventory then
passes that information on to the General Ledger.
Accounts Receivable
The Accounts Receivable module passes sales revenue and accounts receivable
information from customer invoices, and miscellaneous revenue, cash, and accounts
receivable information from cash receipts to the General Ledger.
.....................................................................................................................................................
4-15

.....................................................................................................................................................
The Sources of Default Accounts

Sources of Default Accounts
Payables
Oracle
Applications
Accounts Payable liability

Cash account to be credited
Discounts taken
Sales, tax, freight revenue

Accounts Receivable
Cash account to be debited
Receivables
Inventory
Inventory asset value

Inventory Assets received,
but not delivered to Inventory
Liability for materials received,
but not invoiced
Purchase price to standard
cost variance
Purchasing
Default Account Sources

To minimize data entry errors, Oracle Applications provides many sources of default
account information. These sources provide the default accounts that are utilized for
subledger transactions, but can sometimes be overridden on the transaction itself.
Note: This is not a comprehensive list, but is intended merely to provide examples of
how accounting transactions may be automated.
Material Receipt (Purchasing/Inventory)
Inventory asset value
Default from the subinventory into which the material is received.
(MTL_SECONDARY_INVENTORIES)
Inventory assets received but not delivered to inventory
Default from the inventory organization into which material is received.
(RCV_PARAMETERS)
Liability for material received but not invoiced
Default from the inventory organization into which the material was received.
(MTL_PARAMETERS)
Purchase price to standard cost variance
Default from the inventory organization referenced on the purchase order shipment
(MTL_PARAMETERS).
.....................................................................................................................................................
4-16
The Sources of Default Accounts

.....................................................................................................................................................
Default Account Sources (continued)

Accounts Payable
Accounts Payable liability
Defined as a default account at the operating unit level.
(FINANCIALS_SYSTEM_PARAMS_ALL) can be overridden at the supplier site
level (PO_VENDOR_SITES_ALL) and on the invoice itself.
Invoice price to purchase price variance
Default from the inventory organization referenced on the purchase order shipment
(MTL_PARAMETERS)
Cash account to be credited when payment information is posted to General
Ledger.
Defined as a default for the bank account against which the payment is generated.
(AP_BANK_ACCOUNTS)
Discounts taken
Defined as a default at the operating unit level.
(FINANCIALS_SYSTEM_PARAMS_ALL)
Accounts Receivable
Sales Revenue, Tax Revenue, Freight Revenue, Accounts Receivable
The sales revenue account can be generated using the AutoAccounting function,
which has RA_SALESREPS, RA_TRX_TYPES_ALL, and
MTL_SYSTEM_ITEMS as sources for segment values.
Cash account to be debited when cash receipts are posted to General Ledger
Defined as a default for a receipt method.
(AR_RECEIPT_METHOD_ACCOUNTS)
.....................................................................................................................................................
4-17

.....................................................................................................................................................
The Multi-Org Architecture

Multi-Org
Database
Set of books
Legal entity
Legal entity
Operating unit
Operating unit
Inventory org
Subinventory
Operating unit
Inventory org
Subinventory
Multi-Org Architecture
From Release 10.6 forward, Oracle applications offer a multi-organization
architecture, which allows implementation of some security features for multiple
operating units that all record data within a single General Ledger set of books. This
security enables segregation of data by operating unit within the Purchasing, Accounts
Payable, Order Entry, and Accounts Receivable applications.
For example, if a computer manufacturing company with one set of books had two
operating units: the laptop operating unit and the desktop operating unit, Oracle
applications could be set up so that purchase orders, invoices, and so on, entered by
personnel in the laptop operating unit would not be visible to personnel in the desktop
operating unit.
The general structure of the multiple operating unit structure is shown in the diagram
above. The scope of each level is indicated below:
Database Instance
Database instance is an installation of Oracle Application tables.
.....................................................................................................................................................
4-18

.....................................................................................................................................................
General Ledger Set of Books

A ledger into which journal entries are entered for one or more operating units for a
business organization using a single currency, calendar, and chart of accounts
combination.
Access to the data in a set of books is controlled through the users responsibility, by
using the GL Set of Books ID profile option. All the tables in General Ledger contain a
column for SET_OF_BOOKS_ID. When looking at a window in General Ledger, the
user is actually looking at a view, and seeing only the rows where the value in the
SET_OF_BOOKS_ID column corresponds to the setting of the profile option for the
responsibility they are logged in under.
A company may have multiple business entities (lines of business, product lines,
geographical regions), that record journal entries within the same set of books, but
produce separate balance sheets. Each of these business entities would correspond to a
balancing segment value in the account numbers in the chart of accounts. For
example, the account numbers for Line-of-Business A might all start with 01, while
the account numbers for Line-of-Business B might start with 02. When generating a
financial statement for Line of Business A, the report would include account balances
for only those account numbers that start with 01. Revenue and expenses are closed
out to retained earnings separately for each balancing segment value.
Access to specific account numbers can be implemented using value security rules,
which can be set up so that users of a responsibility can only see a subset of account
numbers in the chart of accounts. Continuing with the example above, if a user is
logged in using a responsibility such as Accounts Payable for Line of Business A,
he or she would not see any account numbers which start with 02 for use on invoice
distributions.
Legal Entity
At the current time, legal entity is a placeholder in the multi-org structure, and is
reserved primarily for implementation of features in the future. It does not necessarily
correspond to a governmental reporting entity.
.....................................................................................................................................................
4-19

.....................................................................................................................................................
Operating Unit
Operating units segregate data within Purchasing, Accounts Payable, Order Entry, and
Accounts Receivables. Excepting supplier and customer header records, all data
within these applications (purchase orders, vendor invoices, and so on) can be
segregated by operating unit. Please note that supplier and customer header records are
visible across all operating units. Each operating unit passes financial data to one and
only one set of books. However, multiple operating units can pass data into the same
set of books.
Security at the operating unit level is implemented through a profile option called
MO: operating unit, which is set at the responsibility level. All the tables in
Purchasing, Accounts Payable, Order Entry, and Accounts Receivables (exception:
vendors and customers tables) contain a column called ORG_ID. When a user is
looking at a window in these applications, he or she is actually looking at a view of the
underlying table. The window will show only those records where the value in the
ORG_ID column corresponds to the value of the profile option for the responsibility
the user is logged in under.
Security by operating unit applies to all functions within Purchasing, Accounts
Payable, Order Entry, and Accounts Receivables (exception: receipt of purchased
material). Receipt of material is controlled at the inventory organization level.
Inventory Organization
Inventory organizations separate inventory information primarily for the purposes of
material requirements planning and for segregating inventory asset value. An
inventory organization can be defined by physical location, product line, or whatever
division of material asset value best suits the customers needs.
Each inventory organization passes data to one and only one General Ledger set of
books. However, multiple inventory organizations can pass data into the same General
Ledger set of books.
Security at the inventory organization level can be controlled by a profile option or
through choosing an inventory organization prior to entering an inventory window. A
popup window is displayed for selecting the inventory organization. Material against a
purchase order is received into an inventory organization identified at the shipment
level. This inventory organization controls the account numbers that are utilized for
material asset value, the value of inventory assets received but not yet delivered to
inventory, uninvoiced receipt liability, purchase order to standard cost variance, and
invoice to purchase order variance.
.....................................................................................................................................................
4-20

.....................................................................................................................................................
Subinventory
A subinventory subdivides an inventory organization in order to segregate inventory
asset value. Subinventories do not pass data to General Ledger. However, they provide
a source of default account numbers for handling of material asset value.
.....................................................................................................................................................
4-21

.....................................................................................................................................................
Multiple Reporting Currencies

Primary Subledger
SoB 1 (MPX)
DEM 100 @ MPX 500
Operating Unit
Conversion of
transaction
amounts using
daily rates
Transfer to GL
Primary General Ledger
SoB 1 (MPX)
DEM 100 @ MPX 500
Reporting Subledger
SoB2 (US$)
DEM 100 @US$ 66
Transfer to GL
Reporting General Ledger

SoB2 (US$)
DEM 100 @US$ 66
Copy and conversion

of manual journal
entries using
daily rates

The Multiple Reporting Currencies (MRC) feature enables you to report in multiple
currencies at the transaction level. MRC ensures that each transaction is correctly
rounded and completely balanced within a reporting currency. You can define as many
reporting currencies as your business requires. Each transaction can then be viewed or
reported in any of the reporting currencies by changing your responsibility. In the
Oracle subledgers, you will only be able to view or report transactions. However, in
Oracle General Ledger, you can choose to view, report, update, or delete transactions.
.....................................................................................................................................................
4-22

.....................................................................................................................................................
Multiple Reporting Currencies (continued)

Typically, you will need the Multiple Reporting Currencies feature in the following
situations:
If you operate in a country with an unstable currency and you need to concurrently
manage your business in both your local currency and a hard currency. Multiple
Reporting Currencies will allow you to maintain your transaction in both the local
currency and a hard currency.
If you operate in a European country whose primary reporting currency will be
changed to euros. Use the Multiple Reporting Currencies feature to automatically
maintain your transactions in parallel in more than one currency (for example, in
euros as well as your local currency). This approach will allow you to smoothly
transition from your local currency to euros. Multiple Reporting Currencies also
provides you with an easy interface to enter exchange rates between your local
currency, the euro, and an external currency.
If you need to restate your amounts for management reporting purposes using a
budget exchange rate while still preserving each transaction at its actual exchange
rate for legal and fiscal reporting.
If you need to maintain nonmonetary accounts, such as fixed assets and inventory
at their true historical exchange rates, and use these rates to calculate depreciation.
General Approach
When entering transactions in your standard application, all accounted amounts are
converted to your reporting currencies at the appropriate daily rates. The conversion is
based on the currency conversion type you have defined for the source or category. In
the subledgers, this conversion information is stored in subtables. In the General
Ledger, the entire journal entry is duplicated in the reporting set of books, with the
appropriate converted amounts. A prerequisite is that the reporting set of books must
have the same chart of accounts and the calendar as your standard set of books.
Consider the following example: Your main set of books is in Mexican pesos (MXP)
and your reporting set of books is in US$. You enter a transaction of DEM 100. The
subledger will automatically convert DEM 100 into both MXP and US$ at the
appropriate exchange rates. You will then be able to view the transaction in both the
MXP and the US$ sets of books.
.....................................................................................................................................................
4-23

.....................................................................................................................................................
Summary
Summary
The primary business functions of Oracle

The Multi-Org Architecture implemented in Oracle

The use of Multiple reporting currencies in Orcale

Applications
.....................................................................................................................................................
4-24
5
.................................

.....................................................................................................................................................
Objectives
Objectives

do the following:
Read and evaluate an Oracle General Ledger entity

relationship diagram
Distinguish the major tables by business function

State the major column names in each of the major
tables
Lesson Aim
In this lesson, you will learn to read and evaluate an Oracle General Ledger entity
relationship diagram (ERD).
You will also learn about the major business functions of the General Ledger module
and learn how the application stores the information in the most frequently used tables.
This information facilitates the solution of implementation issues such as data
conversion, as well as other tasks such as customizing reports and creating new
application forms for your end users.
.....................................................................................................................................................
5-2
Oracle General Ledger Overview

.....................................................................................................................................................
Oracle General Ledger Overview

Oracle Financials: General Workflow
Purchasing
Shared items
Acct. Generator
Matching
V
E
N
D
O
R
S
Accrued
Receipts
Accounts
Payable
Mass Additions
Fixed
Assets
Inventory
Expense
Liabilities
Cash out
Asset Transactions
Depreciation
Shared items
Inventory
Interface
Shared items
Order Entry
Auto accounting
Receivables interface
Auto invoices
Material receipts
Material shipments
COGs
Std. cost adjustments
Physical inventory
adjustments
General Ledger
Accounts
Receivable
A/R Assets
Sales revenue
Cash receipts
C
U
S
T
O
M
E
R
S
Financial statements
Oracle General Ledger: The Central Repository

Manufacturing, Human Resources, and Financial applications pass information to the
general ledger. The following table shows the different types of transactions by
application module.
Application
Payables
Receivables
Assets
Purchasing
Inventory
Transaction Type
Payments and invoices
Debit memos, credit memos, on-account credits, invoices,
chargebacks, receipts, adjustments, guarantees, and other receipts
and deposits
Deferred and standard depreciation expense transactions and asset
transaction information
Accrued receipts
Inventory and work-in-process transactions
.....................................................................................................................................................
5-3

.....................................................................................................................................................

Set of Books
Currency
Calendar
Set
of
books
Chart of
accounts

Each numerical value in the general ledger must fall into one of the following three
categories:
Actuals
Encumbrances
Budgets
The General Ledger module is where your chart of accounts, fiscal calendar, and
currency are defined in a relationship known as a set of books. You can define more
than one set of books in which this information may vary according to the needs of
your enterprise.
For example, you may have a manufacturing plant in Europe that requires a different
currency and fiscal calendar than your manufacturing plant in the United States.
Therefore you would set up two different sets of books for these manufacturing plants.
The set of books relationship contains what is known as the three Cs: Currency,
Calendar, and Chart of Accounts.
.....................................................................................................................................................
5-4

.....................................................................................................................................................
Subledgers
GL Interface
Data Table
Oracle
Assets
GL_JE_Batches
GL_JE_Headers
GL_JE_Lines
Data Tables
Journal
Import
Oracle General Ledger (continued)

As the central repository for financial information, General Ledger receives
information from various subledgers. Information can be gathered and stored in
individual applications, including the general ledger, until it is posted, which is a
formal activity that occurs during an update task. However, this process does not affect
consolidated financial calculations.
The type of data that can be found in General Ledger must be of type A for Actual, B
for Budget, or E for Encumbrance.
Two main functions are performed in Oracle General Ledger: budgets and journals.
Journals Journal entries are actual recording of financial transactions. You must
post all journals to the general ledger. You can import journals from outside systems or
enter journals manually.
Budgets You can budget at all levels of the corporation using data entered manually
or imported from external spreadsheets. You can also copy budget data to speed the
preparation of your forecasting process.
.....................................................................................................................................................
5-5

.....................................................................................................................................................
General Ledger: Currency, Calendar, and Chart of

Accounts
Set of Books Tables
GL_PERIODS
GL_PERIOD_SETS
FND_CURRENCIES
GL_SETS_OF_BOOKS
GL_CODE_COMBINATIONS
Set of Books Tables

The major tables storing currency, calendar, and chart of account information are as
follows:
FND_CURRENCIES
GL_PERIOD_SETS
GL_PERIODS
GL_SETS_OF_BOOKS
Instructor Note
FND_CURRENCIES, and FND_ID_FLEX_STRUCTURES are owned by
Application Object Library.
.....................................................................................................................................................
5-6
General Ledger: Currency, Calendar, and Chart of Accounts

.....................................................................................................................................................
FND_CURRENCIES
This table stores information about currencies. Each row includes a currency code,
name of the currency, the territory code of the issuing country, precision, the symbol
denoting the currency and descriptive flexfield attribute columns. AOL uses the
information in this table to display dynamic currency values. The Multiple Reporting
Currencies feature uses this table to determine conversion rates.
Major Columns
CURRENCY CODE (PK)
ISSUING_TERRITORY_CODE
SYMBOL
ENABLED_FLAG
ATTRIBUTE 1 .... 15
DERIVE_TYPE *
DERIVE_FACTOR **
* Indicates whether the currency has a special relationship with other currencies.
Possible values are EURO, EMU (European Monetary Union) and NULL.
** Multiple applied to the base currency to derive this currency. Only used for the
derived currency in a relationship.
Instructor Note
Navigate to the Currencies window (responsibility: General Ledger, Vision
Operations):
(N) Setup>Currencies>Define
GL_PERIOD_SETS
This table stores the calendars that are defined by using the Accounting Calendar
window. Each row includes the name and description of your calendar. There is a
one-to-many relationship between a row in this table and rows in the GL_PERIODS
table. A GL_PERIOD_SET defines a grouping of GL_PERIODS. For example, a
period set could be a quarter, with 3 defined month GL periods; or a period set could
be a year, with 12 defined month GL periods.
Major Columns
PERIOD_SET_NAME (PK)
DESCRIPTION
Instructor Note
Navigate to the Accounting Calendar window (responsibility: General Ledger, Vision
Operations):
(N) Setup>Financials>Calendar>Accounting
.....................................................................................................................................................
5-7

.....................................................................................................................................................
GL_PERIODS
This table stores information about the accounting periods defined for a specific
accounting calendar. Each row includes the start date and end date of the period, the
period type, the fiscal year, and the period number. There is a one-to-many relationship
between a row in this table and rows in the GL_PERIOD_SETS table.
Major Columns
PERIOD_SET_NAME (PK)
PERIOD_NAME (PK)
START_DATE
END_DATE
PERIOD_NUM
QUARTER_NUM
Instructor Note
Navigate to the Accounting Calendar window (responsibility: General Ledger, Vision
Operations):
(N) Setup>Financials>Calendar>Accounting
This table stores structure information about key flexfields as entered from the Key
Flexfield Segments window. A structure is the entire definition of all the columns and
the meaning of the key flexfield. Structure definitions for the accounting flexfield are
stored in this table in records where ID_FLEX_CODE = GL#. The accounting key
flexfield can have multiple structures, each identified by a unique combination of
ID_FLEX_CODE and ID_FLEX_NUM.
Instructor Note
Navigate to the Key Flexfields window (responsibility: System Administrator):
(N) Application>Flexfields>Key>Segment
For a more detailed discussion of this table, please refer to Lesson 4.
.....................................................................................................................................................
5-8
General Ledger: Currency, Calendar, and Chart of Accounts

.....................................................................................................................................................
GL_SETS_OF_BOOKS
This table stores information about the sets of books you define in the Oracle General
Ledger application. Each row includes the set of books name, description, and
functional currency. The MRC_SOB_TYPE_CODE column in this table indicates the
reporting currency option you specified for the set of books.
Major Columns
SET_OF_BOOKS_ID (PK)
NAME
CURRENCY_CODE
CHART_OF_ACCOUNTS_ID
PERIOD_SET_NAME
RET_EARN_CODE_COMBINATION_ID
MRC_SOB_TYPE_CODE*
* Multiple Reporting Currency set of books type (Parent, Reporting, None)
Instructor Note
Navigate to the Set of Books window (responsibility: General Ledger, Vision
Operations):
(N) Setup>Financials>Books>Define
.....................................................................................................................................................
5-9

.....................................................................................................................................................
General Ledger: Journal Entries

Journal Entries
GL_BALANCES
consists of
creates
references
created by
GL_CODE_
GL_JE_LINES
COMBINATIONS
creates
in
assigned to
GL_
INTERFACE
composed of
created by
GL_JE_HEADERS
creates
in
composed of
created by
GL_JE_BATCHES
creates
Journal Entry Tables

The major tables storing journal entries related information are as follows:
GL_JE_BATCHES
GL_JE_HEADERS
GL_JE_LINES
GL_BALANCES
.....................................................................................................................................................
5-10

.....................................................................................................................................................
GL_JE_BATCHES
This table stores details of journal entry batches (a grouping of journal entries). In
General Ledger, journal entries are posted in batches. Each row in this table includes
the batch name, status, running total debits and credits for all entries in the batch, and
other information.
Major Columns
JE_BATCH_ID (PK)
NAME
STATUS *
ACTUAL_FLAG **
DEFAULT_PERIOD_NAME
POSTED_DATE
DESCRIPTION
SET_OF_BOOKS_ID
POSTING_RUN_ID (Posting sequence number)
* Posted or Unposted
** A = Actuals, B = Budgets, and E = Encumbrance
Instructor Note
Navigate to the Batch window (responsibility: General Ledger, Vision Operations):
(N) Journals>Enter (B) New Batch
.....................................................................................................................................................
5-11

.....................................................................................................................................................
GL_JE_HEADERS
This table stores journal entry information. There is a one-to-many relationship
between journal entry batches and journal entries. Each row in this table includes the
associated batch ID, journal entry name and description, and other information about
the journal entry.
Major Columns
JE_HEADER_ID (PK)
SET_OF_BOOKS_ID
JE_CATEGORY
JE_SOURCE
PERIOD_NAME
NAME
CURRENCY_CODE
STATUS
ACTUAL_FLAG
JE_BATCH_ID
POSTED_DATE
DESCRIPTION
Instructor Note
Navigate to the Journals window (responsibility: General Ledger, Vision Operations):
(N) Journals>Enter (B) New Journal
.....................................................................................................................................................
5-12

.....................................................................................................................................................
GL_JE_LINES
This table stores journal entry lines. There is a one-to-many relationship between
journal entries and journal entry lines. This table contains the information about the
account and amount for each line of the entry.
Major Columns
JE_HEADER_ID (PK)
JE_LINE_NUM (PK)
SET_OF_BOOKS_ID
CODE_COMBINATION_ID
PERIOD_NAME
EFFECTIVE _DATE
STATUS
ENTERED_DR
ENTERED_CR
ACCOUNTED_DR
ACCOUNTED_CR
DESCRIPTION
STAT_AMOUNT
ENTERED_DR and ENTERED_CR store the value of the entered currency;
ACCOUNTED_DR and ACCOUNTED_CR store the value of the calculated journal
in the base currency.
Instructor Note
Navigate to the Journals window (responsibility: General Ledger, Vision Operations):
(N) Journals>Enter (B) New Journal
.....................................................................................................................................................
5-13

.....................................................................................................................................................
This table stores valid account combinations for each accounting flexfield structure in
Oracle General Ledger. Associated with each account are certain codes and flags,
including whether the account is enabled and whether detail posting or detail
budgeting is allowed. This table references the CODE_COMBINATION_ID, which is
the foreign key used by Oracle Applications in tracking an account combination.
Major Columns
CODE_COMBINATION_ID (PK)
ACCOUNT_TYPE
ENABLED_FLAG
SEGMENT1....SEGMENT30
Note: FND_ID_FLEX_SEGMENTS table stores information about which column in
the GL_CODE_COMBINATIONS table is used for storing each segment of the
accounting flexfield structure.
GL_BALANCES
This table stores net debit and net credit information for detail and summary accounts.
The information is stored for both actual and budget amounts. It also stores functional
currency, foreign currency, and statistical balances for each accounting period that has
ever been opened. GL_BALANCES is populated by the system during the GL Post
and Summary Account Template Definition. It is used for standard account inquiries
and for Financial Statement Generator (FSG) reporting.
Note: This table stores activity rather than the actual balance.
Use the following formula to calculate the period-to-date balance:
(PERIOD_NET_DR - PERIOD_NET_CR) = Period-to-Date Balance
Use the following formula to calculate the year-to-date balance:

(BEGIN_BALANCE_DR - BEGIN_BALANCE_CR) +
(PERIOD_NET_DR - PERIOD_NET_CR) = Year-to-Date Balance
.....................................................................................................................................................
5-14

.....................................................................................................................................................
GL_BALANCES (continued)
Major Columns
CODE_COMBINATION_ID
CURRENCY_CODE (PK)
PERIOD_NAME (PK)
ACTUAL_FLAG (PK
ENCUMBRANCE_TYPE_ID (PK)
TRANSLATED_FLAG (PK)
BUDGET_VERSION_ID (PK)
PERIOD_NET_DR
PERIOD_NET_CR
QUARTER_TO_DATE_DR
QUARTER_TO_DATE_CR
*PROJECT_TO_DATE_DR
*PROJECT_TO_DATE_CR
BEGIN_BALANCE_DR
BEGIN_BALANCE_CR
TEMPLATE_ID
* These columns retain the life-to-date balance.
.....................................................................................................................................................
5-15

.....................................................................................................................................................
General Ledger: Budget

Budgets
GL_BUDGETS
has
references
GL_BUDGET_VERSIONS
assigned to
associated with
GL_BUDGET_ASSIGNMENTS
includes
assigned to
assigned to
contain
GL_BUDGET_ENTITIES
Budget Tables
The following major tables store budget related information.
GL_BUDGET_ENTITIES
GL_BUDGETS
GL_BUDGET_VERSIONS
GL_BALANCES
GL_BUDGET_ENTITIES
This table stores information about budget organizations. Each row includes the
organization name, description, set of books ID, and optional password.
Major Columns
BUDGET_ENTITY_ID (PK)
SET_OF_BOOKS_ID
NAME
Instructor Note
Navigate to the Define Budget Organization window (responsibility: General Ledger,
Vision Operations):
(N) Budgets>Define>Organization
.....................................................................................................................................................
5-16
General Ledger: Budget

.....................................................................................................................................................
This table stores the accounts that are assigned to each budget organization. Each row
includes the currency assigned to the account and the entry code for the account.
Major Columns
CURRENCY_CODE (PK)
ENTRY_CODE *
BUDGET_ENTITY_ID
BUDGET_VERSION_ID
* The entry code is to determine the accounting balance, whether it is an entered or a
calculated amount.
Instructor Note
Navigate to the Account Assignments window (responsibility: General Ledger, Vision
Operations):
(N) Budgets>Define>Organization (B) Assignments
Oracle General Ledger.
Instructor Note
This table is discussed in detail earlier in this lesson.
.....................................................................................................................................................
5-17

.....................................................................................................................................................
GL_BUDGETS
This table stores information about your budgets. Each row includes a budget name,
first and last period names, date created, and status.
Major Columns
BUDGET_TYPE (PK)
BUDGET_NAME (PK)
SET_OF_BOOKS_ID
STATUS
FIRST_VALID_PERIOD_NAME
LAST_VALID_PERIOD_NAME
DESCRIPTION
Instructor Note
Navigate to the Define Budget window (responsibility: General Ledger, Vision
Operations):
(N) Budgets>Define>Budget
GL_BUDGET_VERSIONS
This table stores information about the different versions of budgets that you have
created. There is one row in this table for each row in the GL_BUDGETS table.
Major Columns
BUDGET_VERSION_ID (PK)
BUDGET_TYPE
BUDGET_NAME
VERSION_NUM
STATUS
GL_BALANCES
This table stores actual, budget, and encumbrance balances for detail and summary
accounts.
Instructor Note
This table is discussed in detail earlier in this lesson.
.....................................................................................................................................................
5-18

.....................................................................................................................................................

MRC Setup Steps
GL Enable and/or Define Primary SoB
GL Enable and/or Define Reporting Currencies
GL Define Reporting SoBs
GL Assign Reporting SoBs to Primary SoB
GL Define Conversion Options for each Application
GL Define General Ledger Conversion Rules
SA Define Reporting Responsibilities
SA Assign Reporting SoBs to Reporting Responsibilities
Setup Steps
The following must be performed to set up MRC in your applications:
Enable or define primary set of books
Enable and/or define reporting currencies
Define reporting sets of books
Assign reporting sets of books to primary set of books
Define conversion options for each application
Define General Ledger conversion rules
Define reporting responsibilities
Assign reporting sets of books to reporting responsibilities
Note: Daily rates are used to convert primary set of books transactions to the
appropriate reporting currencies. If you do not currently maintain daily rates, you must
do so when you implement MRC.
.....................................................................................................................................................
5-19

.....................................................................................................................................................
Multiple Reporting Currencies: Setup Tables

MRC: Setup Tables
GL_SETS_OF_BOOKS
FND_CURRENCIES
GL_MC_BOOK_ASSIGNMENTS
GL_MC_REPORTING_OPTIONS
GL_MC_CONVERSION_RULES
Setup Tables
The following tables are used to store MRC setup information:
GL_SETS_OF_BOOKS
FND_CURRENCIES
GL_SETS_OF_BOOKS
This table stores information about the primary and reporting sets of books you use for
MRC. The MRC_SOB_TYPE_CODE column in this table indicates the reporting
currency option you specified for the set of books. For more information on this table,
see General Ledger: Currency, Calendar, and Chart of Accounts.
.....................................................................................................................................................
5-20
Multiple Reporting Currencies: Setup Tables

.....................................................................................................................................................
FND_CURRENCIES
This table stores information about currencies. The Multiple Reporting Currencies
feature uses this table to determine conversion rates. For more information on this
table, see General Ledger: Currency, Calendar, and Chart of Accounts.
This table stores information on the reporting sets of books assigned to a primary set
of books.
Major Columns
PRIMARY_SET_OF_BOOKS_ID
REPORTING_SET_OF_BOOKS_ID
FIRST_MRC_PERIOD
Instructor Note
Navigate to the Assign Reporting Sets of Books window (responsibility: General
Ledger, Vision Operations):
(N) Setup>Financials>Books>Assign
This table stores reporting currency information for each primary set of books. There
is one row in this table for each reporting currency of a particular set of books.
Major Columns
REPORTING_OPTION_ID (PK)
PRIMARY_SET_OF_BOOKS_ID
REPORTING_SET_OF_BOOKS_ID
PRIMARY_CURRENCY_CODE
REPORTING_CURRENCY_CODE
AP_SECONDARY_SET_OF_BOOKS_ID
CONVERSION_TYPE
Instructor Note
Navigate to the Conversion Options window (responsibility: General Ledger, Vision
Operations):
(N) Setup>Financials>Books>Assign (B)Conversion Options
.....................................................................................................................................................
5-21

.....................................................................................................................................................
This table stores information on the conversion rules that Oracle General Ledger uses
for the Multiple Reporting Currencies feature. Each row stores the primary set of
books ID, the reporting set of books ID, the source name, the category name,
conversion type, the date basis, and the conversion rule. The conversion rule specifies
if the source and category combination should be transferred to the reporting set of
books.
Major Columns
PRIMARY_SET_OF_BOOKS_ID (PK)
REPORTING_SET_OF_BOOKS_ID (PK)
JE_SOURCE_NAME (PK)
JE_CATEGORY_NAME (PK)
CONVERSION_RULE
DATE_BASIS
CONVERSION_TYPE
Instructor Note
Navigate to the Conversion Options window (responsibility: General Ledger, Vision
Operations):
(N) Setup>Financials>Books>Assign (B) Conversion Options (B) GL
Conversion Rules
The tables that are impacted while defining a responsibility have already been
discussed in an earlier lesson.
.....................................................................................................................................................
5-22
Multiple Reporting Currencies Tables

.....................................................................................................................................................

MRC: Setup Tables
GL_PERIOD_STATUSES
FND_DAILY_ CONVERSION_TYPES
GL_ DAILY_RATES
GL_ DAILY_RATES_INTERFACE

The following tables are used by the Multiple Reporting Currencies feature:
GL_PERIOD_STATUSES
GL_DAILY_CONVERSION_TYPES
GL_DAILY_RATES
GL_DAILY_RATES_INTERFACE
.....................................................................................................................................................
5-23

.....................................................................................................................................................
GL_PERIOD_STATUSES
This table stores the statuses for your accounting periods. While using MRC, you must
open/close accounting periods in your primary set of books and in each of your
reporting sets of books. Each row in this table includes the accounting period name
status, and application ID since other applications maintain their calendars in this
table.
Major Columns
APPLICATION_ID (PK)
PERIOD_NAME (PK)
CLOSING_STATUS *
* O = open, C = closed, F = future enterable, P = permanently closed, N = never
opened
Instructor Note
Navigate to the Open and Close Periods window (responsibility: General Ledger,
Vision Operations):
(N) Setup>Open/Close
GL_DAILY_CONVERSION_TYPES
This table stores daily conversion rate types and their descriptions.
Major Columns
CONVERSION_TYPE (PK)
USER_CONVERSION_TYPE
Instructor Note
Navigate to the Conversion Rate Types window (responsibility: General Ledger,
Vision Operations):
(N) Setup>Currencies>Rates>Types
.....................................................................................................................................................
5-24

.....................................................................................................................................................
GL_DAILY_RATES
If you use the Multiple Reporting Currencies feature in General Ledger, your daily
rates are used to convert the journals for your primary set of books to the appropriate
reporting currencies when the journals are copied to your reporting sets of books. Your
daily rates must be defined before you post journals in your primary set of books.
The GL_DAILY_RATES table stores the daily conversion rates for foreign currency
transactions.You should not insert data directly into this table, but should use the
GL_DAILY_RATES_INTERFACE table to load rates into it.
Major Columns
FROM_CURRENCY (PK)
TO_CURRENCY (PK)
CONVERSION_DATE (PK)
CONVERSION_TYPE (PK)
CONVERSION_RATE
Instructor Note
Navigate to the Daily Rates window (responsibility: General Ledger, Vision
Operations):
(N) Setup>Currencies>Rates>Daily
.....................................................................................................................................................
5-25

.....................................................................................................................................................
GL_DAILY_RATES_INTERFACE
The GL_DAILY_RATES table stores the daily conversion rates for foreign currency
transactions. However, you should not insert data directly into this table, but should
use the GL_DAILY_RATES_INTERFACE table to load rates into it. The daily
conversion rates which will automatically be copied into the GL_DAILY_RATES
table by database triggers on GL_DAILY_RATES_INTERFACE table. You do not
need to run any import programs. You only need to develop an automated process that
populates the interface table with your daily rates information.
Major Columns
FROM_CURRENCY (PK)
TO_CURRENCY (PK)
FROM_CONVERSION_DATE (PK)
TO_CONVERSION_DATE (PK)
USER_CONVERSION_TYPE (PK)
CONVERSION_RATE
MODE_FLAG
INVERSE_CONVERSION_RATE
USER_ID
LAUNCH_RATE_CHANGE
.....................................................................................................................................................
5-26
GL Interface Table
.....................................................................................................................................................
GL Interface Table
GL Interface
Subledgers
GL Interface
Data Table
Oracle
Assets
GL_JE_Batches
GL_JE_Headers
GL_JE_Lines
Data Tables
Journal
Import
GL_INTERFACE
This is the table used to import journal entry batches through Journal Import. Insert
rows into this table and then use the Import Journals window to create journal batches.
Major Columns
STATUS
SET_OF_BOOKS_ID
ACCOUNTING_DATE
CURRENCY_CODE
ACTUAL_FLAG
USER_JE_CATEGORY_NAME
USER_JE_SOURCE_NAME
GROUP_ID
Note: All of the Oracle Financial applications except Fixed Assets interface with the
General Ledger through this table. Fixed Assets posts directly to the batches, headers,
and lines tables.
.....................................................................................................................................................
5-27

.....................................................................................................................................................
Summary
Summary
General Ledger records and organizes accounting

transactions and manages fiscal responsibilities
for the enterprise for:
Actuals
Budgets
Encumbrances
Major activities in the General Ledger module

include:
Budgeting
Journal entry and posting
.....................................................................................................................................................
5-28

.....................................................................................................................................................

Given the business scenario described, use SQL*Plus

to answer the user inquiries that follow the scenario.

.....................................................................................................................................................
5-29

.....................................................................................................................................................
.....................................................................................................................................................
5-30
6
.................................
Oracle Purchasing

.....................................................................................................................................................
Objectives
Objectives

do the following:
Read and evaluate an Oracle Purchasing entity


Name the major columns in each of the
major tables
Lesson Aim
In this lesson, you will learn about the major business functions of the Purchasing
module and learn how the application stores the information in the most frequently
used tables. This information facilitates the solution of implementation issues such as
data conversion as well as other tasks such as customizing reports and creating new
application forms for your end users.
.....................................................................................................................................................
6-2
Oracle Purchasing Overview

.....................................................................................................................................................

Supplier Management
Requisition
PO
Issue RFQs
Receipt
Record quotation
Assess Supplier Performance


Oracle Purchasing is a comprehensive procurement solution, designed to reduce
administration costs while focusing on value analysis, strategic supply base
management, and contract negotiation. Oracle Purchasing satisfies the following
business needs, explained on the next few pages.
Supplier Management
Maintain supplier master file.
Create requests for quotations from suppliers.
Record supplier price quotes.
Approve quotes for use on purchasing documents.
.....................................................................................................................................................
6-3

.....................................................................................................................................................
Requisitions
Other
Systems
Inventory
WIP
MRP
Demand
Import/Reschedule
Requisitions
Manually
Create
Create Internal
Sales Order
Order Entry
Supplier
Requisition
Requisition
Pool
Oracle Purchasing Overview (continued)

Requisitions
Replace paper processing with online requisition generation, purchase order
creation, and document approval.
Create requisitions manually or import them from external systems.
Create internal or vendor requisitions.
Minimize data entry time with time-saving templates, express processing
functionality, and default infrastructures.
.....................................................................................................................................................
6-4

.....................................................................................................................................................
l
Purchase Orders
Manually create
Auto create
PO
Maintain documents
Accept
Receive against PO
Revise
Requisition
pool
Control
Match invoices in Payables

Purchase Orders
Create purchase orders from either online or paper requisitions, or enter purchase
orders without requisitions.
Cancel and close purchase orders.
Identify when and where shipments are to be received.
Consolidate purchase requirements from multiple warehouses, plants, or locations.
.....................................................................................................................................................
6-5

.....................................................................................................................................................
Receiving
Shipment
Transfer
Inventory
Supplier
Receive
Deliver
Shop floor
Order
Entry
Inventory
Internal
shipment
Expense
Inspect

Receiving
Record receipt and delivery of goods.
Record quality inspection results.
Deliver goods to inventory or to the requestor.
.....................................................................................................................................................
6-6
Oracle Purchasing: Operating Units

.....................................................................................................................................................
Oracle Purchasing: Operating Units

Operating Units
HR_ORGANIZATION_UNITS
described by
ORG CLASSIFICATION
used in
used in
describes
HR_ORGANIZATION_INFORMATION
classified by
exist for
ORG INFO TYPE
BY CLASS
HR_ORG_INFORMATION_TYPES
Operating Units and Organization Tables

The following tables store operating unit and organization related information:
This table holds the definitions that identify operating units. Additional information
about classifications and information types for each operating unit is stored in
HR_ORGANIZATION_INFORMATION.
.....................................................................................................................................................
6-7

.....................................................................................................................................................
HR_ORGANIZATION_UNITS (continued)
Major Columns
ORGANIZATION_ID (PK)
BUSINESS_GROUP_ID
LOCATION_ID
NAME
TYPE
ATTRIBUTE 1...25
Instructor Note
Navigate to the Organization window (responsibility: Purchasing, Vision Operations):
(N) Setup>Organizations>Organizations
This table is used to hold two distinct sets of organization information. When
ORG_INFORMATION_CONTEXT is set to CLASS, this table acts as an intersection
between organizations and organization classifications. When
ORG_INFORMATION_CONTEXT is set to an information type held in
HR_ORG_INFORMATION_TYPES, the ORG_INFORMATION1-20 columns hold
details for the specific information type.
Major Columns
ORG_INFORMATION_ID (PK)
ORG_INFORMATION_CONTEXT
ORGANIZATION_ID
ORG_INFORMATION 1 ... 20
ATTRIBUTE_CATEGORY
ATTRIBUTE1 ... 20
Instructor Note
Navigate to the Organization window (responsibility: Purchasing, Vision Operations)
(N) Setup>Organizations>Organizations (Organization Classifications region)
For a more detailed discussion of Multi-Org, please see Lesson 4.
.....................................................................................................................................................
6-8
Oracle Purchasing: Purchasing Agent Tables

.....................................................................................................................................................
Oracle Purchasing: Purchasing Agent Tables

Purchasing Agents
HR_EMPLOYEES
is a
defined as
PO_AGENTS
Purchasing Agent Tables

The major tables storing requisitioners and purchasing agents information for Oracle
Purchasing are:
PER_PEOPLE_F
PO_AGENTS
PER_PEOPLE_F
This is the table that holds personal information for employees, contacts, and other
people that is set up by using the People window.
Major Columns
PERSON_ID (PK)
FULL_NAME
Instructor Note
Navigate to the People window (responsibility: Human Resources, Vision Enterprises)
(N) People>Enter and Maintain
If HRMS or Payroll is not installed, you can access this window from Purchasing
(responsibility: Purchasing, Vision Operations):
(N) Setup>Personnel>Employees
.....................................................................................................................................................
6-9

.....................................................................................................................................................
PO_AGENTS
This table contains information about buyers and purchasing managers. You need one
row for each employee who has purchasing responsibilities in your organization. You
define a buyer by entering a default Item Category and Ship-To Location.
Oracle Purchasing uses this information to determine active buyers and to provide
defaults to the autocreate purchase orders and RFQs search criteria.
Major Columns
AGENT_ID (PK)
LOCATION_ID
CATEGORY_ID
AUTHORIZATION_LIMIT
Instructor Note
Navigate to the Buyers window (responsibility: Purchasing, Vision Operations)
(N) Setup>Personnel>Buyers
AGENT_ID column has the same value as the EMPLOYEE_ID in the
HR_EMPLOYEES view for the corresponding employee.
.....................................................................................................................................................
6-10
Oracle Purchasing: Items Table

.....................................................................................................................................................
Oracle Purchasing: Items Table

Items
MTL_RELATED_ITEMS
ORG_ORGANIZATION_DEFINITIONS
MTL_SECONDARY_
SUBINVENTORIES
MTL_SYSTEM_ITEMS
MTL_UNITS_OF_MEASURE
PO_AGENTS
PO_LINES_ALL
PO_APPROVED_SUPPLIER_LIST
Items Table
Oracle Purchasing gets item information from the MTL_SYSTEM_ITEMS table,
which is owned by Oracle Inventory.
MTL_SYSTEM_ITEMS
This table stores item definitions for purchased items.
Major Columns
INVENTORY_ITEM_ID (PK)
DESCRIPTION
BUYER_ID
SEGMENT1 ... 20
Instructor Note
Navigate to the Master Item window (responsibility: Purchasing, Vision Operations):
(N) Items>Master Items
.....................................................................................................................................................
6-11

.....................................................................................................................................................
Oracle Purchasing: Vendor Information Tables

Suppliers
PO_VENDORS
HR_EMPLOYEES
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
Vendor Information Tables

The following major tables store vendor information:
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
PO_VENDORS
This table stores information about your suppliers. Each row includes the vendor name
as well as purchasing, receiving, payment, accounting, tax, classification, and other
general information. VENDOR_ID is the unique system-generated number that is
invisible to the user (primary key). SEGMENT1 is the system-generated or manually
assigned number used to identify the vendor in forms and reports.
Vendor header information is visible across all operating units.
.....................................................................................................................................................
6-12

.....................................................................................................................................................
PO_VENDORS (continued)
Major Columns
VENDOR_ID (PK)
VENDOR_NAME
SEGMENT1
EMPLOYEE_ID
TERMS_ID
TYPE_1099
VENDOR_TYPE_LOOKUP_CODE
PARENT_VENDOR_ID
SHIP_TO_LOCATION_ID *
BILL_TO_LOCATION_ID *
PAY_GROUP
* These columns have a foreign key to HR_LOCATIONS.
Instructor Note
Navigate to the Suppliers Summary window (responsibility: Purchasing, Vision
Operations):
(N) Supply Base>Suppliers
.....................................................................................................................................................
6-13

.....................................................................................................................................................
PO_VENDOR_SITES_ALL
This table stores information about supplier sites. Each row includes the site address,
vendor reference, purchasing, payment, bank, default liability account, and other
general information. Supplier sites are visible only to the operating unit that created
them.
Major Columns
VENDOR_SITE_ID (PK)
VENDOR_ID
PAY_SITE_FLAG [Y/N]
PURCHASING_SITE_FLAG [Y/N]
VENDOR_SITE_CODE
ADDRESS_LINE1
ADDRESS_LINE2
ADDRESS_LINE3
CITY
STATE
ZIP
AREA_CODE
PHONE
ORG_ID (operating unit)
ACCTS_PAY_CCID
PREPAY_CCID
Instructor Note
Navigate to the Supplier Sites window (responsibility: Purchasing, Vision
Operations):
(N) Supply Base>Suppliers>Open>Sites Alternate region>Open
.....................................................................................................................................................
6-14

.....................................................................................................................................................
PO_VENDOR_CONTACTS
This table stores information about contacts for a supplier site.
Major Columns
VENDOR_CONTACT_ID (PK)
VENDOR_SITE_ID
FIRST_NAME
MIDDLE_NAME
LAST_NAME
AREA_CODE
PHONE
Instructor Note
Navigate to the Supplier Sites window (responsibility: Purchasing, Vision
Operations):
(N) Supply Base>Suppliers>Open>Sites alternate region>Open
>Contacts alternate region
.....................................................................................................................................................
6-15

.....................................................................................................................................................
Oracle Purchasing: Purchase Requisition Tables

Oracle Purchasing Documents
In Oracle Purchasing, there are five types of

purchasing documents:
Request for quote (RFQs)

Quotation
Standard purchase order
Blanket purchase order
Planned purchase order
Purchase Requisition Tables

The following are the major tables that store purchase requisition information:
PO_REQUISITION_HEADERS_ALL
PO_REQUISITION_LINES_ALL
PO_REQ_DISTRIBUTIONS_ALL
MTL_SYSTEM_ITEMS
.....................................................................................................................................................
6-16

.....................................................................................................................................................
PO_REQUISITION_HEADERS_ALL
This table stores information about requisition headers. Each row contains the
requisition number, preparer, status, and description.
Major Columns
REQUISITION_HEADER_ID (PK)
SEGMENT1 .... 5
AUTHORIZATION_STATUS
DESCRIPTION
PREPARER_ID
TYPE_LOOKUP_CODE (Internal or Purchase)
Instructor Note
Navigate to the Requisitions window (responsibility: Purchasing, Vision Operations):
(N) Requisitions>Requisitions
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, requester, notes, the ID of the suggested vendor
from whom to buy the item.
Major Columns
REQUISITION_LINE_ID (PK)
REQUISITION_HEADER_ID
LINE_NUM
LINE_TYPE_ID
CATEGORY_ID
ITEM_DESCRIPTION
UNIT_MEAS_LOOKUP_CODE
UNIT_PRICE
.....................................................................................................................................................
6-17

.....................................................................................................................................................
PO_REQUISITION_LINES_ALL (continued)
Major Columns (continued)
QUANTITY
TO_PERSON_ID
ITEM_ID
DESTINATION_ORGANIZATION_ID *
VENDOR_ID
DELIVER_TO_LOCATION_ID
SOURCE_TYPE_CODE
LINE_LOCATION_ID
ORG_ID
* DESTINATION_ORGANIZATION_ID is an inventory organization, not an
operating unit.
Instructor Note
Navigate to the Requisitions window (responsibility: Purchasing, Vision Operations):
(N) Requisitions>Requisitions
.....................................................................................................................................................
6-18

.....................................................................................................................................................
PO_REQ_DISTRIBUTIONS_ALL
This table 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 Flexfield ID and requisition line quantity. This
table is populated by the Account Generator, if enabled.
Major Columns
DISTRIBUTION_ID (PK)
REQUISITION_LINE_ID
SET_OF_BOOKS_ID
CODE_COMBINATION_ID
REQ_LINE_QUANTITY
ORG_ID
PROJECT_ID
TASK_ID
Instructor Note
Navigate to the Distributions window (responsibility: Purchasing, Vision Operations):
(N) Requisitions>Requisitions (B) Distributions
Major Columns
SEGMENT1 ... SEGMENT30
MTL_SYSTEM_ITEMS
This table stores item definitions for purchased items.
Instructor Note
This table is discussed in more detail earlier in this lesson.
.....................................................................................................................................................
6-19

.....................................................................................................................................................
Oracle Purchasing: Purchase Orders, Requests for

Quotes, and Quotations
Oracle Purchasing Documents
In Oracle Purchasing, there are five types of

purchasing documents:
Request for quote (RFQs)

Quotation
Standard purchase order
Blanket purchase order
Planned purchase order
Purchase Orders, Requests for Quotes, and Quotations

Requests for Quotes: A request for quote (RFQ) is sent to a supplier from the
buyer to estimate an anticipated purchase order.
Quotations: Information that is quoted by the supplier in response to an RFQ.
Standard Purchase Orders: Basic purchase order for inventory or expense items.
Blanket Purchase Orders: A purchase order for either inventory or expense items
where there is a commitment to a supplier for a specific not to exceed dollar
amount. Blanket purchase order releases are performed for specific dollar amounts
to facilitate the purchase of goods.
Planned Purchase Orders: Usually used for inventory items in the material
planning process. Similar to blanket purchase orders, except that the planned
purchase order has an end date and a series of deliveries specified. Planned
purchase order releases are performed for specific dollar amounts to facilitate the
purchase of goods.
.....................................................................................................................................................
6-20
Oracle Purchasing: Purchase Order Tables

.....................................................................................................................................................

Purchase Order
charged for
charged to
PO_DISTRIBUTIONS_ALL
delivery info for
PO_LINES_ALL
shipment schedule/
price breaks for
contains
consists of
PO_LINE_LOCATIONS_ALL
for shipment to
used on
PO_HEADERS_ALL
addressed
to
released by
released for
the contact for
PO_VENDORS_CONTACTS
employer
of
working
at
PO_RELEASES_ALL
PO_VENDOR_SITES_ALL
for
PO_VENDORS
having
Purchase Order Tables

The following are the major tables that store purchase order information:
PO_HEADERS_ALL
PO_LINES_ALL
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_RELEASES_ALL
.....................................................................................................................................................
6-21

.....................................................................................................................................................
PO_HEADERS_ALL
All of the header information for all seven types of purchasing documents is stored in
this table. Each row contains buyer information, supplier information, brief notes,
foreign currency information, terms and conditions information, and document status.
Major Columns
PO_HEADER_ID (PK)
SEGMENT1
AGENT_ID
TYPE_LOOKUP_CODE *
VENDOR_ID
VENDOR_SITE_ID
CREATION_DATE
PRINTED_DATE
FROM_HEADER_ID **
* STANDARD, BLANKET, and so on
** Refers to a quotation from which this purchase order was created.
Instructor Note
Navigate to the Purchase Orders window (responsibility: Purchasing, Vision
Operations):
(N) Purchase Orders>Purchase Orders
.....................................................................................................................................................
6-22

.....................................................................................................................................................
PO_LINES_ALL
In this table, you need one row for each line that 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. For
RFQs, this table holds delivery and need-by information. For quotes, this table holds
the dates when the supplier is able to deliver the items requested, as well as any type of
price breakdown information.
Major Columns
PO_LINE_ID (PK)
PO_HEADER_ID
LINE_NUM
ORG_ID
ITEM_DESCRIPTION
UNIT_MEAS_LOOKUP_CODE
UNIT_PRICE
QUANTITY
LINE_TYPE_ID
ITEM_ID
CATEGORY_ID
Instructor Note
Navigate to the Purchase Orders window (responsibility: Purchasing, Vision
Operations):
(N) Purchase Orders>Purchase Orders
.....................................................................................................................................................
6-23

.....................................................................................................................................................
This table contains information about purchase order shipment schedules and blanket
agreement price breaks. You need one row for each schedule or price break that you
attach to a document line.
Major Columns
LINE_LOCATION_ID (PK)
PO_HEADER_ID
PO_LINE_ID
QUANTITY
QUANTITY_RECEIVED
QUANTITY_ACCEPTED
QUANTITY_REJECTED
QUANTITY_BILLED
QUANTITY_CANCELLED
SHIP_TO_ORGANIZATION_ID (inventory organization)
SHIP_TO_LOCATION_ID
ORG_ID
APPROVED_FLAG
NEED_BY_DATE
PROMISED_DATE
LAST_ACCEPT_DATE
SHIPMENT_NUM
Each row contains the location, quantity, and dates for each scheduled shipment.
Oracle Purchasing uses this information to record delivery schedule information for
purchase orders and price break information for blanket purchase orders and
quotations. This table is updated when material is received against a purchase order
shipment, or when an invoice is received for that shipment.
Instructor Note
Navigate to the Shipments window (responsibility: Purchasing: Vision Operations):
(N) Purchase Orders>Purchase Orders (B) Shipments
.....................................................................................................................................................
6-24

.....................................................................................................................................................
This table contains accounting information for a purchase order shipment line. You
need one row for each distribution you attach to a purchase order shipment. For
manually created purchase orders, this table is populated by the Account Generator, if
enabled.
Major Columns
PO_DISTRIBUTION_ID (PK)
PO_HEADER_ID
PO_LINE_ID
LINE_LOCATION_ID
SET_OF_BOOKS_ID
CODE_COMBINATION_ID
QUANTITY_ORDERED
QUANTITY_DELIVERED
QUANTITY_BILLED
QUANTITY_CANCELLED
AMOUNT_BILLED
DESTINATION_ORGANIZATION_ID
DELIVER_TO_PERSON_ID
DESTINATION_SUBINVENTORY
ORG_ID
REQ_DISTRIBUTION_ID
Instructor Note
Navigate to the Distributions window (responsibility: Purchasing: Vision Operations):
(N) Purchase Orders>Purchase Orders (B) Shipments (B) Distributions
PO_VENDORS
This table stores information about your suppliers. You need one row for each supplier
you define. Each row includes the supplier name as well as purchasing, receiving,
payment, accounting, tax, classification, and general information. Oracle Purchasing
uses this table to determine active suppliers.
.....................................................................................................................................................
6-25

.....................................................................................................................................................
Oracle Purchasing: Receiving Default Information

Receiving Default Information
RCV_PARAMETERS
ORG_ORGANIZATION_
DEFINITIONS
MTL_SECONDARY_
INVENTORIES
GL_SETS_OF_BOOKS
MTL_PARAMETERS
Receiving Default Information Tables

There are two types of purchased material receipts: receipt of inventory material and
receipt of expense material. However, whenever you receive material, you receive it
into an inventory organization as identified by the
DESTINATION_ORGANIZATION_ID in the PO_LINE_LOCATIONS_ALL table.
The default information associated with receipt of material is stored in the tables
described below. These tables are owned by Oracle Inventory:
MTL_PARAMETERS
RCV_PARAMETERS
MTL_SECONDARY_INVENTORIES
.....................................................................................................................................................
6-26
Oracle Purchasing: Receiving Default Information

.....................................................................................................................................................
MTL_PARAMETERS
This table contains the default account code combinations for Inventory AP accrual
and PO/STD cost variance.
Major Columns
AP_ACCRUAL_ACCOUNT
PURCHASE_PRICE_VAR_ACCOUNT
Instructor Note
Open the Organization window (responsibility: Purchasing, Vision Operations):
Query on the Vision Operations Inventory Organization. Click Inventory Organization
at the bottom of the window. Click the Open button. Select Inventory Information.
Select the Other Account alternative region.
RCV_PARAMETERS
This table stores receiving options for each organization in which you want to receive
items. It contains one row for each organization.
Major Columns
DAYS_EARLY_RECEIPT_ALLOWED
RECEIVING_ROUTING_ID
RECEIVING_ACCOUNT
ENFORCE_SHIP_TO_LOCATION_CODE
Instructor Note
Open the Organization window (responsibility: Purchasing, Vision Operations):
Query on the Vision Operations Inventory Organization. Click Inventory Organization
at the bottom of the window. Click the Open button. Select Receiving Information.
.....................................................................................................................................................
6-27

.....................................................................................................................................................
This table provides the definition table for the subinventories. A subinventory is a
subset of an inventory organization, for example raw material, finished goods, and so
on. When you receive inventory material and deliver it to stores, the default inventory
asset account is determined from this table.
Major Columns
SECONDARY_INVENTORY_NAME (PK)
MATERIAL_ACCOUNT
Instructor Note
Open the Subinventories window (responsibility: Inventory, Vision Operations):
(N) Setup>Organizations>Subinventories
In the popup window, select Vision Operations Inventory Organization. Query on
Stores subinventory. Click the Open button. Select the Accounts alternative region.
.....................................................................................................................................................
6-28
Oracle Purchasing: Receiving Tables

.....................................................................................................................................................

Receiving
PO_HEADERS_ALL
placed
with
supplier
for
consists of
PO_VENDORS
supplier of
shipped by
composed of
delivery
information for
RCV_SHIPMENT_HEADERS
actual
receipt for
scheduled
receipt for
grouped
by
RCV_SHIPMENT_LINES
transaction
source for
delivered by
MTL_MATERIAL_
TRANSACTIONS
transacted against
a child
of
a
parent
of
delivered against
generates
updates inventory information for
RCV_SUPPLY
RCV_TRANSACTIONS
contains on-hand balances for

generates
Receiving Subinventory Tables

The following tables store receiving information.
RCV_SHIPMENT_LINES
RCV_TRANSACTIONS
MTL_MATERIAL_TRANSACTIONS
MTL_ONHAND_QUANTITIES
MTL_TRANSACTION_ACCOUNTS
RCV_SUPPLY
PO_VENDORS
.....................................................................................................................................................
6-29

.....................................................................................................................................................
This table stores common information about the source of your receipts or expected
receipts.
Major Columns
SHIPMENT_HEADER_ID (PK)
RECEIPT_SOURCE_CODE
VENDOR_ID
VENDOR_SITE_ID
RECEIPT_NUM
PACKING_SLIP
SHIP_TO_LOCATION_ID
SHIPPED_DATE
ORGANIZATION_ID
Instructor Note
Open the Receipts window (responsibility: Purchasing, Vision Operations):
(N) Receiving>Receipts
.....................................................................................................................................................
6-30

.....................................................................................................................................................
RCV_SHIPMENT_LINES
This table stores information about items that have been shipped and/or received from
a specific receipt source. It also stores information about the default destination for intransit shipments. A record is written to this table when you receive material against a
purchase order shipment as identified in PO_LINE_LOCATIONS_ALL.
Major Columns
SHIPMENT_LINE_ID (PK)
SHIPMENT_HEADER_ID
LINE_NUM
CATEGORY_ID
QUANTITY_SHIPPED
QUANTITY_RECEIVED
UNIT_OF_MEASURE
ITEM_DESCRIPTION
ITEM_ID
PO_HEADER_ID
PO_LINE_ID
PO_LINE_LOCATION_ID
PO_RELEASE_ID
PO_DISTRIBUTION_ID
TO_ORGANIZATION_ID
TO_SUBINVENTORY
PO_RELEASE_ID
SHIPMENT_LINE_STATUS_CODE
Instructor Note
Open the Receipts window (responsibility: Purchasing, Vision Operations):
(N) Receiving>Receipts
.....................................................................................................................................................
6-31

.....................................................................................................................................................
RCV_TRANSACTIONS
This table stores historical information about receiving transactions you have
performed. When you receive material from the receiving windows, the Receiving
Transaction Processor runs to update this table.
Major Columns
TRANSACTION_ID (PK)
TRANSACTION_TYPE
TRANSACTION_DATE
QUANTITY
UNIT_OF_MEASURE
SHIPMENT_HEADER_ID
SHIPMENT_LINE_ID
INSPECTION_STATUS_CODE
PO_DISTRIBUTION_ID
PO_LINE_LOCATION_ID
DELIVER_TO_PERSON_ID
ORGANIZATION_ID
SUBINVENTORY
PO_HEADER_ID
Instructor Note
Open the Receipt Headers Summary window (responsibility: Purchasing, Vision
Operations):
(N) Receiving>Receiving Transactions Summary
.....................................................................................................................................................
6-32

.....................................................................................................................................................
This table stores a record of every material transaction and cost update performed in
Oracle Inventory. Records are inserted through either the transaction processor or the
standard cost update program. When you receive inventory material, the Receiving
Transaction Processor updates this table.
Major Columns
TRANSACTION_ID (PK)
INVENTORY_ITEM_ID
ORGANIZATION_ID
RCV_TRANSACTION_ID
Instructor Note
Open the Material Transactions window (responsibility: Inventory, Vision
Operations):
(N) Transactions>Material Transactions
.....................................................................................................................................................
6-33

.....................................................................................................................................................
This table stores quantity-on-hand information by control level and location. When
you receive purchased inventory material and deliver it to a subinventory, this table
gets updated.
Major Columns
DATE_RECEIVED (PK)
TRANSACTION_QUANTITY
SUBINVENTORY_CODE
REVISION
Instructor Note
Open the Item On-hand Quantities window (responsibility: Inventory, Vision
Operations):
(N) Onhand, Availability>Onhand Quantities
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. After you have received purchased
inventory material and records have been written to
MTL_MATERIAL_TRANSACTIONS, the Cost Manager runs to create records in
this table for the accounts and amounts associated with the receipt. The Cost Manager
uses the default accounts from MTL_SECONDARY_INVENTORIES,
MTL_PARAMETERS and RCV_PARAMETERS tables.
Major Columns
TRANSACTION_ID
INVENTORY_ITEM_ID
ORGANIZATION_ID
REFERENCE _ACCOUNT
BASE_TRANSACTION_VALUE
Instructor Note
Open the Material Transaction Distributions window (responsibility: Inventory, Vision
Operations):
(N) Transactions>Material Transactions (B) Distributions
.....................................................................................................................................................
6-34

.....................................................................................................................................................
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 standard receiving transaction. Compared to the
RCV_TRANSACTIONS table, this table records the net (or final adjustment) receipt
quantity of the receiving transactions.
Major Columns
SUPPLY_TYPE_CODE (PK)
SUPPLY_SOURCE_ID (PK)
SHIPMENT_HEADER_ID
RCV_TRANSACTION_ID
ITEM_ID
QUANTITY
UNIT_OF_MEASURE
LOCATION_ID
PO_VENDORS
This table stores information about your suppliers. Each row includes the vendor name
as well as purchasing, receiving, payment, accounting, tax, classification, and other
general information.
This table contains information about purchase order shipment schedules and blanket
agreement price breaks. You need one row for each schedule or price break that you
attach to a document line.
This table contains accounting information for a purchase order shipment line. You
need one row for each distribution you attach to a purchase order shipment. This table
is used by the Standard and Planned Purchase Orders and by the Planned and Blanket
Purchase Order Releases.
.....................................................................................................................................................
6-35

.....................................................................................................................................................
Tables for Passing Material Receipts to GL

Passing Material Receipt Information to
General Ledger
Purchasing
Inventory
Writes records directly
Transfer of Information by
GL_INTERFACE
Journal Import
General Ledger
15
Material Receipts from Purchasing to GL

GL_INTERFACE table is used to pass material receipt information from Purchasing
to Oracle General Ledger.
Material Receipts from Inventory to GL
The following tables are used to pass material receipt information from Inventory to
GL_INTERFACE
ORG_GL_BATCHES
.....................................................................................................................................................
6-36
Tables for Passing Material Receipts to GL

.....................................................................................................................................................
GL_INTERFACE
This table is used to import journal entry batches through journal import.
Major Columns
STATUS
SET_OF_BOOKS_ID
ACCOUNTING_DATE
CURRENCY_CODE
DATE_CREATED
CREATED_BY
USER_JE_CATEGORY_NAME
USER_JE_SOURCE_NAME
BUDGET_VERSION_ID
JE_HEADER_ID
CODE_COMBINATION_ID
ORG_GL_BATCHES
This table holds history rows for every batch of transactions that have been interfaced
to the GL_INTERFACE table. When you run the Inventory transfer to GL process, a
new row is inserted into this table by using the next GL_BATCH_ID number. The
same GL_BATCH_ID number is used to mark the records in
MTL_TRANSACTION_ACCOUNTS whose information has been passed to the
GL_INTERFACE table.
Major Columns
ACCT_PERIOD_ID
GL_BATCH_DATE
LAST_UPDATE_LOGIN
GL_BATCH_ID (PK)
Instructor Note
Navigate to the General Ledger Transfers window (responsibility: Inventory, Vision
Operations):
(N) Accounting Close Cycle>View General Ledger Transfers
.....................................................................................................................................................
6-37

.....................................................................................................................................................
Summary
Summary
In this lesson, you should have learned that Oracle

Purchasing performs the following business
functions:
Supplier (vendor) management

Requisitions
Purchase orders
Receipts
This lesson presented the table relationships for
these business functions.
.....................................................................................................................................................
6-38

.....................................................................................................................................................


.....................................................................................................................................................
6-39

.....................................................................................................................................................
.....................................................................................................................................................
6-40
7
.................................
Oracle Payables

.....................................................................................................................................................
Objectives
Objectives

do the following:
Read and evaluate an Oracle Payables entity


Name the major columns in each of the major
tables
Lesson Aim
In this lesson, you will learn about the relationship between Oracle Payables tables.
You will also learn about the major business functions of the Payables module and
how the application stores the information in the most frequently used tables. This
information facilitates the solution of implementation issues such as data conversion
as well as other tasks such as customizing reports and creating new application forms
for your end users.
.....................................................................................................................................................
7-2
Oracle Payables Overview

.....................................................................................................................................................

Overview
Invoice
Enter
invoice
Payables
Reconcile
payments
Journal
Entries
Create PO
Enter
requisition
Enter
vendor

Oracle Payables manages the complete accounts payable process, from supplier entry
to payment reconciliation.
Oracle Payables contains five major areas:
Enter Suppliers
Enter Invoices
Approve Invoices
Pay Invoices
.....................................................................................................................................................
7-3

.....................................................................................................................................................
Enter Suppliers
Parent
supplier
Supplier A
Supplier site
Supplier site
Supplier B
Supplier site
Supplier site
contract
Supplier site
Supplier site
contract
Creating and Managing Suppliers

Enter suppliers and their addresses.
Review supplier information online and submit reports.
Merge duplicate suppliers.
.....................................................................................................................................................
7-4

.....................................................................................................................................................
Enter Invoices
Receive
invoices
Match invoice
to
Purchase order
PO
Invoice
Enter invoice
Enter basic
information
Enter detailed
information
Maintain invoices
File invoices
Entering Invoices
Enter invoices with complete account charges individually or in batches.
Enter invoice payment and accounting details.
Record asset information and integrate with Oracle Assets (submit Mass
Additions).
Match invoices to purchase orders to verify quantities and prices being billed.
Process recurring invoices for routine payments such as rent.
.....................................................................................................................................................
7-5

.....................................................................................................................................................
Approve Invoices
Approve
invoice
Batch approval
Individual approval
Print approval report

or review it online
Review invoices
on hold
Resolve
exceptions
Approving Invoices
Approve invoices.
Respond to invoice queries.
Submit invoice reports.
.....................................................................................................................................................
7-6

.....................................................................................................................................................
Pay Invoices
Select
approved
invoice
Pay invoice
Record manual
payment
Create manual
payment outside
Oracle Payables
Run
payments
in batch
Confirm payment batch:

Confirm checks
Update invoice
payment history
Format payments:
Print checks
Load EFT data
Modify payment batch:
Remove/add invoices
Modify payment details
Create
single
payments
Create computergenerated
payment
Paying Invoices Manually and Automatically

Record manual checks or wire transfers.
Create QuickChecks.
Pay invoices automatically in a payment batch.
Stop and void payments.
.....................................................................................................................................................
7-7

.....................................................................................................................................................
Oracle Payables: Setup Table

Accounts Payable Setup Information
FINANCIALS_SYSTEM_PARAMS_ALL
ACCTS_PAY_CODE_COMBINATION_ID
DISC_TAKEN_CODE_COMBINATION_ID
TERMS_ID
PAYMENT_METHOD_LOOKUP_CODE
ORG_ID
Payable Setup Table

FINANCIALS_SYSTEM_PARAMS_ALL table stores the setup information used by
Oracle Payables.
FINANCIALS_SYSTEM_PARAMS_ALL
This table contains options and defaults you share between Oracle Payables and
Oracle Purchasing applications. You can define these options from the Define
Financial Options window, based on the way you run your business. These defaults are
defined for each operating unit within Oracle Payables, and provide many of the
default settings used when you create a supplier.
Major Columns
ACCTS_PAY_CODE_COMBINATION_ID
DISC_TAKEN_CODE_COMBINATION_ID
TERMS_ID
ORG_ID
Instructor Note
Navigate to the Financial Options window (responsibility: Payables, Vision
Operations):
(N) Setup>Options>Financials
.....................................................................................................................................................
7-8
Oracle Payables: Vendor Information Tables

.....................................................................................................................................................
Oracle Payables: Vendor Information Tables

Vendor Information
PO_VENDORS
HR_EMPLOYEES
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
Vendor Information Tables

The following major tables store vendor information:
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
Instructor Note
These tables are discussed in Lesson 6.
.....................................................................................................................................................
7-9

.....................................................................................................................................................
Types of Invoices
Invoice Types
QuickMatch
PO Default
Standard
Credit Memo
Debit Memo
Mixed
Prepayments
Invoice Types
QuickMatch An invoice you enter for matching to a purchase order. You enter a PO
number and Oracle Payables automatically provides supplier information and matches
to each shipment on the purchase order.
PO Default An invoice you enter for matching to a purchase order. You enter a PO
number and Oracle Payable automatically provides supplier information.
Standard An invoice from a supplier representing an amount due for goods or
services purchased. Standard invoices can be either matched to a PO or not matched
(for example, a utility bill).
Credit Memo A memo from a supplier representing a credit amount toward goods
or services for which you have already been invoiced.
Debit Memo An invoice you enter to record a credit for a supplier who does not
send you a credit memo.
Mixed An invoice you enter for matching to both purchase orders and invoices. You
can enter either a positive or a negative amount for a Mixed Invoice.
Prepayments A type of invoice you enter to pay an advance payment for expenses
to a supplier or employee QuickMatch an invoice you enter for matching to a purchase
order. You enter a PO number, and Oracle Payables automatically provides supplier
information and matches to each shipment on the purchase order.
.....................................................................................................................................................
7-10
Oracle Payables: Invoice Tables

.....................................................................................................................................................

Invoices
AP_PAYMENT_
SCHEDULES_ALL
AP_INVOICES_ALL
AP_HOLDS_ALL
AP_INVOICE_DISTRIBUTIONS_ALL
Oracle Payables: Invoice Information Tables

The major tables used for storing information on supplier invoices are as follows:
AP_INVOICES_ALL
AP_PAYMENT_SCHEDULES_ALL
AP_HOLDS_ALL
.....................................................................................................................................................
7-11

.....................................................................................................................................................
AP_INVOICES_ALL
This table contains records for invoices that you enter from your suppliers. It has one
row for each invoice. To be approved, the total amount of the invoice stored in
AP_INVOICES_ALL must be fully distributed to general ledger accounts in
AP_INVOICE_DISTRIBUTIONS_ALL and must be fully scheduled for payment in
AP_PAYMENT_SCHEDULES_ALL.
Major Columns
INVOICE_ID (PK)
VENDOR_ID
VENDOR_SITE_ID
INVOICE_NUM
INVOICE_DATE
INVOICE_AMOUNT
AMOUNT_PAID
SET_OF_BOOKS_ID
INVOICE_CURRENCY_CODE
PAYMENT_CURRENCY_CODE
INVOICE_TYPE_LOOKUP_CODE
PAYMENT_STATUS_FLAG [Y/P/N]
PO_HEADER_ID
ORG_ID
Instructor Note
Navigate to the Invoices window (responsibility: Payables, Vision Operations):
(N) Invoices>Entry>Invoices
.....................................................................................................................................................
7-12

.....................................................................................................................................................
This table holds the distribution line information that you enter for invoices. There is a
row for each invoice distribution. If matching is used, distribution information is
copied from PO_DISTRIBUTIONS during the matching process.
Major Columns
INVOICE_ID (PK)
DISTRIBUTION_LINE_NUMBER (PK)
DIST_CODE_COMBINATION_ID (Expense account)
ACCTS_PAY_CODE_COMBINATION_ID (Liability account)
ACCOUNTING_DATE
ASSETS_ADDITION_FLAG *
ASSETS_TRACKING_FLAG *
ORG_ID
AMOUNT (Foreign currency)
BASE_AMOUNT (Functional currency)
PO_DISTRIBUTION_ID
* If these flags are set to Y, the invoice information can be processed by the Mass
Addition process to create Fixed Asset records.
Instructor Note
Navigate to the Distributions window (responsibility: Payables, Vision Operations):
(N) Invoices>Entry>Invoices (B) Distributions
.....................................................................................................................................................
7-13

.....................................................................................................................................................
AP_PAYMENT_SCHEDULES_ALL
This table contains information about scheduled payments for an invoice. Oracle
Payables uses this information to determine when to make payments on an invoice and
how much to pay in an automatic payment batch.
Major Columns
INVOICE_ID (PK)
PAYMENT_NUM (PK)
PAYMENT_PRIORITY
PAYMENT_STATUS_FLAG
AMOUNT_REMAINING
DUE_DATE
DISCOUNT_DATE
HOLD_FLAG
ORG_ID
Instructor Note
Navigate to the Scheduled Payments window (responsibility: Payables, Vision
Operations):
(N) Invoices>Entry>Invoices (B) Scheduled Payments
.....................................................................................................................................................
7-14

.....................................................................................................................................................
AP_HOLDS_ALL
This table contains information about holds that you or the system place on an invoice.
An invoice may have multiple records in this table. An invoice is not paid until all
holds placed on it have been released.
Major Columns
INVOICE_ID
HOLD_LOOKUP_CODE
HELD_BY
HOLD_DATE
HOLD_REASON
RELEASE_LOOKUP_CODE *
RELEASE_REASON
ORG_ID
* An invoice is on hold if there is a record in this table where
RELEASE_LOOKUP_CODE is NULL.
Instructor Note
Navigate to the Invoice Holds window (responsibility: Payables, Vision Operations):
(N) Invoices>Entry>Invoices (B) Holds
.....................................................................................................................................................
7-15

.....................................................................................................................................................
Payment Methods
Payment Methods
Manual
QuickCheck
Payment Batch
Payment Methods
Manual Payments When you create a payment outside of Oracle Payables, you can
record the payment in Oracle Payables and update the invoices that you paid.
QuickCheck You can create and print a computer generated payment to pay a single
supplier for one or more invoices.
Payment Batch You can use payment batches to create payments for multiple
invoices that meet the selection criteria you specify. In addition to controlling which
invoices Oracle Payables selects for payment in the batch, you can set limits on
payment amounts and decide to take applicable discounts. Payment batches require an
additional step called confirmation where you identify to Oracle Payables that all
checks have printed successfully.
.....................................................................................................................................................
7-16
Oracle Payables: Payment Tables

.....................................................................................................................................................

Payments
AP_INVOICE_PAYMENTS_ALL
payment for
paid by
AP_CHECKS_ALL
AP_CHECKS_ALL
distributed as
payment lines for
AP_BANK_BRANCHES
AP_BANK_BRANCHES
AP_PAYMENT_
AP_PAYMENT_
DISTRIBUTIONS_ALL
DISTRIBUTIONS_ALL
composed of
branch of
distributed for
distributed by
assigned to
defined with
AP_BANK_
AP_BANK_
ACCOUNTS_ALL
ACCOUNTS_ALL
pays to
assigned to
PO_VENDORS
PO_VENDORS
location for
located at
PO_VENDOR_SITES
PO_VENDOR_SITES
entered for
pays to
scheduled payment for
AP_INVOICES_ALL
AP_INVOICES_ALL
scheduled for payment by
AP_PAYMENT_
AP_PAYMENT_
SCHEDULES_ALL
SCHEDULES_ALL
Payment Tables
The following tables store information pertaining to the payments made against
invoices:
AP_BANK_BRANCHES
AP_BANK_ACCOUNTS
AP_CHECKS_ALL
AP_PAYMENT_DISTRIBUTIONS_ALL
.....................................................................................................................................................
7-17

.....................................................................................................................................................
AP_BANK_BRANCHES
This table stores information about the bank branches you define while setting up
banks. You need a row for each bank branch you use. A bank branch may have
multiple bank accounts.
Major Columns
BANK_BRANCH_ID (PK)
BANK_NAME
BANK_BRANCH_NAME
BANK_NUMBER
Instructor Note
Navigate to the Banks window (responsibility: Payables, Vision Operations):
(N) Setup>Payment>Banks
AP_BANK_ACCOUNTS
This table stores information about your bank accounts. You need to have one row for
each bank account you define.
Major Columns
BANK_ACCOUNT_ID
BANK_ACCOUNT_NAME
BANK_ACCOUNT_NUM
BANK_BRANCH_ID
SET_OF_BOOKS_ID
CURRENCY_CODE
ACCOUNT_TYPE
CODE_COMBINATION_ID *
* This identifies the General Ledger cash account that will be credited when a
payment is generated against this bank account.
Instructor Note
Navigate to the Bank Accounts window (responsibility: Payables, Vision Operations):
(N) Setup>Payment>Banks (B) Accounts
.....................................................................................................................................................
7-18

.....................................................................................................................................................
AP_CHECKS_ALL
This table stores information about payments issued to suppliers. Each row includes
the supplier name, address, and bank account name for auditing purposes, in case any
of them changes after you make the payment. Please note that payments may be made
through EDI or an electronic funds transfer, and are not always checks.
Major Columns
CHECK_ID (PK)
CURRENCY_CODE
AMOUNT (Foreign currency)
BANK_ACCOUNT_ID
BANK_ACCOUNT_NAME
CHECK_DATE
CHECK_NUMBER
PAYMENT_METHOD_LOOKUP_CODE *
PAYMENT_TYPE_FLAG [A/M/Q]
DATED]
VENDOR_ID
VENDOR_SITE_ID
VENDOR_NAME
CHECK_STOCK_ID
CHECK_FORMAT_ID
ORG_ID
* CHECK/CLEARING/EFT/WIRE/MANUAL FUTURE DATED/FUTURE
Instructor Note
Navigate to the Payments window (responsibility: Payables, Vision Operations):
(N) Payments>Entry>Payments
.....................................................................................................................................................
7-19

.....................................................................................................................................................
This table contains records of invoice payments that you make to suppliers. Oracle
Payables updates this table when you confirm an automatic payment batch, enter a
manual payment, or process a Quick Payment. Void payments are also entered into this
table as a negative of the original payment line. This table provides the link between a
payment (CHECK_ID) and the invoice(s) paid by that payment.
Major Columns
INVOICE_PAYMENT_ID (PK)
CHECK_ID
INVOICE_ID
AMOUNT
ACCOUNTING_DATE
ACCRUAL_POSTED_FLAG
CASH_POSTED_FLAG
PAYMENT_NUM
PERIOD_NAME
SET_OF_BOOKS_ID
DISCOUNT_LOST
DISCOUNT_TAKEN
ORG_ID
Instructor Note
Navigate to the Select Invoices window (responsibility: Payables, Vision Operations):
(N) Payments>Entry>Payments (B) Enter/Adjust Invoices
.....................................................................................................................................................
7-20

.....................................................................................................................................................
AP_PAYMENT_DISTRIBUTIONS_ALL
This table stores information for the payment distributions created when you confirm a
payment batch, record a manual payment, or create a Quick Payment. At least one
payment distribution (CASH) is created for each payment on an invoice. Additional
records are created for DISCOUNT, GAIN, and LOSS when appropriate.
ROUNDING distributions are created during foreign currency transactions.
Major Columns
INVOICE_PAYMENT_ID (PK)
PAYMENT_LINE_NUMBER (PK)
DIST_CODE_COMBINATION_ID *
ACCTS_PAY_CODE_COMBINATION_ID **
AMOUNT (payment currency)
ORG_ID
* Cash account to be debited.
** Liability account.
Instructor Note
This table is not accessible through application windows.
.....................................................................................................................................................
7-21

.....................................................................................................................................................
MRC Tables Used in Payables

GL_PERIOD_STATUSES
GL_DAILY_RATES

The following tables are referenced by Payables for using MRC with the subledgers
that support MRC:
GL_PERIOD_STATUSES
GL_DAILY_RATES
GL_PERIOD_STATUSES
This table stores the statuses for your accounting periods.
If you are using MRC with Payables, you must open and close periods in your primary
set of books only. MRC automatically opens and closes periods in all of the associated
reporting sets of books. You cannot close a period until you have posted all
outstanding transactions to General Ledger in both your primary and associated
reporting sets of books.
Each row in this table includes the accounting period name status, and application ID
since other applications maintain their calendars in this table. For more information on
this table, please see Lesson 5, Oracle General Ledger.
.....................................................................................................................................................
7-22

.....................................................................................................................................................
GL_DAILY_RATES
This table stores the daily conversion rates for foreign currency transactions. The
AutoRate program uses the exchange rate information in this table to enter exchange
rates for any foreign currency invoices or payments that have no exchange rates.
AutoRate cannot update exchange rates unless you have first defined exchange rates in
the GL Daily Rates table that match the invoice or payment currency, rate date, and
rate type. For more information on this table, please see Lesson 5, Oracle General
Ledger.
.....................................................................................................................................................
7-23

.....................................................................................................................................................
Oracle Payables: Posting Invoices in General Ledger

Passing Payables Information to
General Ledger
Payables
Payables transfer to GL
GL_INTERFACE
Journal Import
General Ledger
Transferring Payables Information to General Ledger

The GL_INTERFACE table is used while passing payables information to Oracle
General Ledger.
In order for invoice information to be passed to Oracle General Ledger, the invoice
must be approved. In order for payment information to be passed to Oracle General
Ledger, payment batches must have been confirmed.
.....................................................................................................................................................
7-24
Summary
.....................................................................................................................................................
Summary
Summary
In this lesson, you should have learned about the

following Oracle Payables business functions:
Creating and managing suppliers (vendors)

Entering and approving invoices
Paying invoices manually and automatically
Creating journal entries
.....................................................................................................................................................
7-25

.....................................................................................................................................................



.....................................................................................................................................................
7-26
8
.................................
Oracle Fixed Assets

.....................................................................................................................................................
Objectives
Objectives

do the following:
Read and evaluate an Oracle Assets entity


State the major columns in each of the major
tables
Lesson Aim
In this lesson, you will learn about the relationship between the most frequently used
Oracle Assets tables.
You will also learn about the major business functions of the Assets module and how
the application stores the information in the most frequently used tables. This
information facilitates the solution of implementation issues such as data conversion
as well as other tasks such as customizing reports and creating new application forms
for your end users.
.....................................................................................................................................................
8-2
Maintaining Accurate Asset Inventory

.....................................................................................................................................................

Oracle Assets
Oracle Assets is a complete asset management

system solution that helps you maintain accurate
property and equipment inventory, and ensures
that you always select the appropriate accounting
method. Flexible location codes help you locate
assets quickly, or learn which assets reside at a
specific location.
The five major areas of Oracle Assets include:
Adding assets
Making adjustments
Transferring assets
Depreciation
Retirement

Oracle Assets is a complete asset management solution that helps you maintain
accurate property and equipment inventory, and ensures that you always select the best
accounting and tax strategies.
Flexible location codes help you locate assets quickly or learn which assets reside
at a specific location.
Productivity is improved by creating assets automatically from payables invoice
distribution lines or construction-in-process (CIP) asset lines in Oracle Projects.
Oracle Assets manages your CIP projects from inception to completion. You can
track all of the expenditures you incur during the life cycle of a construction
project and capitalize them upon completion.
You can store additional customized information in descriptive flexfields without
programming.
You can easily adjust the units or financial information of an asset or group of
assets. Oracle Assets has the flexibility to conform to the tax and accounting laws
of different countries (through asset revaluation) to accommodate fluctuating
economies, unplanned depreciation, and other unforeseen circumstances.
Viewing Asset Information You can view descriptive or financial information
about your assets online at any time.
.....................................................................................................................................................
8-3

.....................................................................................................................................................
Oracle Assets Overview

Oracle Assets: Adding Assets
Automated
addition
PO
Invoice
Purchasing
CIP
Cost additions
Payables
Detail
Additions
Add asset from

invoice line
Assets
Mass Additions
Manual
addition
QuickAdditions
Adding Assets
Add assets manually by using one of two methods: Quick Additions for speedy asset
entry by using default information, or Detail Additions for adding complex assets by
using detailed information.
Use the fully automated MassAdditions to add assets and perform cost adjustments
directly from invoice information in Oracle Payables.
Add CIP assets that originated in Oracle Assets or externally from Oracle Projects.
.....................................................................................................................................................
8-4

.....................................................................................................................................................
Making Adjustments
Mass Change
Owned Leased
Revaluation
Adjustments
Reclassification
Life: ten years
Life: two years

Financial Information
Adjustment
Unit Adjustment
Making Adjustments
Mass Change: Change financial information for a group of assets
Reclassification: Change the category for an asset
Unit Adjustment: Change the number of units for an asset
Financial Information Adjustment: Correct an error or update financial
information for an asset
Revaluation: Revalue one or more assets to reflect inflation or deflation
.....................................................................................................................................................
8-5

.....................................................................................................................................................
Transferring Assets
Location
Employees
GL Number
Company 09
Region
23
Cost Center 99
Account
03
Product
343
Depreciation
expense
account
GL Number
Company
14
Region
30
Cost Center 11
Account
77
Product
222
Transferring Assets
Transfer all or part of your assets in the same corporate book between general ledger
accounts, locations, and employees.
Back date transfers to a prior period or make them effective in the current accounting
period.
Move groups of assets by using Mass Transfers between general ledger depreciation
expense accounts, locations, or employees.
Undo a new transfer at any time before you run depreciation.
.....................................................................................................................................................
8-6

.....................................................................................................................................................
Depreciation
Asset
Journal
entry
Period 1: $120,000
Period 4: $60,000
Period 8: $10,000
General
Ledger
Depreciation
Run depreciation, create journal entries, project depreciation expense, and calculate
gains and losses independently for any of your depreciation books.
Use any of the standard depreciation methods provided, or define your own. You can
depreciate your assets by using different methods for each book.
When you run depreciation, Oracle Assets calculates depreciation expense and
adjustments, updates the accumulated and year-to-date depreciation, and automatically
closes the current depreciation period.
.....................................................................................................................................................
8-7

.....................................................................................................................................................
Retirement
Asset
Partial cost
Full cost
Partial unit
Entire unit
Full retirement
Partial retirement
Retired assets
Retirement
Retire assets fully or partially, by units or cost, and in the current or previous
accounting periods. You can retire an asset from any depreciation book without
affecting other books.
Specify the details of how to create journal entries for retirements. You can define
multiple accounts for each component of the gain/loss amount, or set up a single
gain/loss account for retirement journal entries.
You can reinstate retired assets. Oracle Assets creates all of the necessary journal
entries for your general ledger.
Retire a group of assets by using Mass Retirements.
.....................................................................................................................................................
8-8
Asset Types
.....................................................................................................................................................
Asset Types
Asset Types
Expensed
Capitalized
Construction-in-process
Expensed
Expensed asset type refers to items that do not depreciate; the entire cost is charged in
a single period to an expense account. Oracle Assets tracks expensed items, but does
not create journal entries for them. Oracle Assets does not depreciate expensed assets,
even if the Depreciate check box in the Books and Mass Additions Prepare windows is
selected for that asset.
Capitalized
Assets included on the company balance sheet. Capitalized assets usually depreciate.
They are charged to an asset cost clearing account.
Construction-in-Process
Unfinished assets being built, but not yet in use and not yet depreciating. Once you
capitalize a construction-in-process asset, Oracle Assets begins depreciating it. They
are charged to a construction-in-process clearing account.
.....................................................................................................................................................
8-9

.....................................................................................................................................................
Oracle Assets: Setup Tables

Fixed Assets Setup Tables
rules for a date range for
FA_CATEGORY_
BOOK_DEFAULTS
the category and book of
FA_CATEGORY_BOOKS
an instance of
a category for
assets in
the category of
the depreciation book of
FA_BOOK_CONTROLS
FA_CATEGORIES
Setup Tables
The following tables store setup information for Oracle Assets:
FA_BOOK_CONTROLS
FA_CATEGORIES
FA_CATEGORY_BOOKS
FA_CATEGORY_BOOK_DEFAULTS
FA_BOOK_CONTROLS
This table contains the definition of an asset book. An Asset book in Fixed Assets is
used for tracking and maintaining information about your fixed assets. There are three
types of asset books, as identified by BOOK_CLASS column: Corporate, Tax, and
Budget. A Corporate book passes asset addition and depreciation entries to a General
Ledger set of books, as defined by SET_OF_BOOKS_ID.
.....................................................................................................................................................
8-10

.....................................................................................................................................................
FA_BOOK_CONTROLS (continued)
Major Columns
BOOK_TYPE_CODE (PK)
BOOK_TYPE_NAME
BOOK_CLASS
SET_OF_BOOKS_ID
LAST_DEPRN_RUN_RATE
DEPRN_CALENDAR
GL_POSTING_ALLOWED_FLAG
ALLOW_MASS_CHANGES
ALLOW_DEPRN_ADJUSTMENTS
ACCOUNTING_FLEX_STRUCTURE
DISTRIBUTION_SOURCE_BOOK
Instructor Note
1 Navigate to the Book Controls window (responsibility: Assets, Vision Operations):
(N) Setup>Asset System>Book Controls
2 FA_MC_BOOK_CONTROLS table, an MRC subtable of
FA_BOOK_CONTROLS, stores control information that affects all assets in a
reporting depreciation book.
.....................................................................................................................................................
8-11

.....................................................................................................................................................
FA_CATEGORIES
This table contains information about asset categories. Asset categories are a key
flexfield, like account numbers.
Major Columns
CATEGORY_ID(PK)
SEGMENT1..7
SUMMARY_FLAG
ENABLED_FLAG
OWNED_LEASED
CATEGORY_TYPE
CAPITALIZE_FLAG
DESCRIPTION
Instructor Note
Navigate to the Asset Categories window (responsibility: Assets, Vision Operations):
(N) Setup>Asset System>Asset Categories
.....................................................................................................................................................
8-12

.....................................................................................................................................................
FA_CATEGORY_BOOKS
This table provides default account information for assets belonging to a specific asset
category tracked in a specific asset book. The Asset Category window inserts a row in
this table for each book in which you use an asset category. For example, if you define
a category for three depreciation books, Oracle Assets inserts three rows into this
table.
Major Columns
CATEGORY_ID (PK)
BOOK_TYPE_CODE (PK)
ASSET_CLEARING_ACCT
ASSET_COST_ACCOUNT
ASSET_CLEARING_ACCT_CCID
ASSET_COST_ACCOUNT_CCID
Instructor Note
Navigate to the Asset Categories window (responsibility: Assets, Vision Operations):
(N) Setup>Asset System>Asset Categories
FA_CATEGORY_BOOK_DEFAULTS
This table provides default information for processing assets belonging to a specific
asset category tracked in a specific asset book.
Major Columns
CATEGORY_ID
BOOK_TYPE_CODE
LIFE_IN_MONTHS
DEPRN_METHOD
DEPRECIATE_FLAG
STL_METHOD_CODE
Instructor Note
Navigate to the Default Depreciation Rules window (responsibility: Assets, Vision
Operations):
(N) Setup>Asset System>Book Controls (B) Default Rules
.....................................................................................................................................................
8-13

.....................................................................................................................................................
Using Mass Additions

Oracle Assets: Adding Assets
Automated
addition
PO
Invoice
Purchasing
CIP
Cost Additions
Payables
Detail
Additions
Add Asset from

invoice line
Assets
Mass Additions
Manual
Addition
QuickAdditions
Adding Assets
There are multiple methods for adding assets information to Oracle Fixed Assets:
Quick Additions and Mass Additions.
Quick Additions: Use the Quick Additions process to add information through a
single window.
Mass Additions: The Mass Additions process takes invoice information entered in
Oracle Accounts Payable and uses it to create asset records.
How to Add Asset Records Using Mass Addition Process
1 Enter an invoice in Accounts Payable where the invoice distribution account has
been identified as an asset clearing account in FA_CATEGORY_BOOKS. This
will cause the ASSETS_ADDITION and ASSETS_TRACKING flags in
AP_INVOICE_DISTRIBUTIONS_ALL to be set to yes, indicating that the record
can be processed by the Mass Additions process.
2 Approve the invoice in Accounts Payable.
3 Post the invoice information from Accounts Payable to General Ledger.
.....................................................................................................................................................
8-14
Using Mass Additions

.....................................................................................................................................................
How to Add Asset Records Using Mass Addition Process (continued)

4 In Accounts Payable, run the Mass Additions Create process and report. This
process creates records in the FA_MASS_ADDITIONS table.
5 In the Fixed Assets module, perform the Prepare Mass Additions process to
prepare records in the FA_MASS_ADDITIONS table to be transferred to the
Fixed Assets module.
6 In the Fixed Assets module, run the Post Mass Additions process. This process
creates records in the FA_ADDITIONS, FA_TRANSACTION_HEADERS,
FA_BOOKS, FA_ASSET_HISTORY, and FA_DISTRIBUTION_HISTORY
tables.
7 In the Fixed Assets module, run the depreciation process. This closes the period
and creates records in FA_DEPRN_DETAILS. Depreciation can only be run once
during an asset period.
8 In the Fixed Assets module, run the Create Journal Entries process. This process
will create journal entries for asset additions, depreciation and retirements directly
in GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES tables, bypassing
the GL_INTERFACE table. Fixed Assets is the only application which does not
use the GL_INTERFACE table to pass journal information into General Ledger.
.....................................................................................................................................................
8-15

.....................................................................................................................................................
Oracle Assets: Asset Addition/Definition Tables

Additions
FA_CATEGORIES
FA_ASSET_HISTORY
FA_TRANSACTION_
HEADERS
FA_ADDITIONS
FA_MASS_ADDITIONS
FA_DEPRN_DETAIL
FA_DISTRIBUTION_
HISTORY
FA_BOOKS
FA_BOOK_CONTROLS
Fixed Assets Tables

The following are the major tables storing fixed asset information:
FA_MASS_ADDITIONS
FA_ADDITIONS
FA_TRANSACTION_HEADERS
FA_BOOKS
FA_ASSET_HISTORY
FA_DISTRIBUTION_HISTORY
.....................................................................................................................................................
8-16

.....................................................................................................................................................
FA_MASS_ADDITIONS
This table stores information on assets you want to automatically add to Oracle Assets
from another system. You can use this table to load assets for system conversions.
When you run the mass additions create process, Oracle Assets inserts one row into
this table for each invoice line it selects from Oracle Payables.
When you run the mass additions post process, Oracle Asset creates assets or
adjustments from any rows in which POSTING_STATUS is POST.
Major Columns
MASS_ADDITION_ID (PK)
ASSET_NUMBER
DESCRIPTION
ASSET_CATEGORY_ID
MANUFACTURER_NAME
SERIAL_NUMBER
MODEL_NUMBER
BOOK_TYPE_CODE
FIXED_ASSETS_COST
POSTING_STATUS
ATTRIBUTE1 ... 30
Instructor Note
1 Navigate to the Mass Additions Summary window (responsibility: Assets, Vision
Operations):
(N) Mass Additions>Prepare Mass Additions (B) Find
2 FA_MC_MASS_RATES table stores exchange rate information that Oracle Assets
uses during the mass additions posting process in an MRC environment.
.....................................................................................................................................................
8-17

.....................................................................................................................................................
FA_ADDITIONS
This table contains descriptive information to help you identify your assets. When you
add an asset, Oracle Assets inserts a row into this table and into
FA_ASSET_HISTORY. When you change the asset information stored in
FA_ADDITIONS, Oracle Assets updates it in this table and creates a new row in
FA_ASSET_HISTORY.
Major Columns
ASSET_ID (PK)
ASSET_NUMBER
ASSET_KEY_CCID
TAG_NUMBER
MANUFACTURER_NAME
SERIAL_NUMBER
MODEL_NUMBER
LEASE_ID
CURRENT_UNITS
ASSET_TYPE [CAP/EXP/CIP]
DESCRIPTION
ASSET_CATEGORY_ID
Instructor Note
Navigate to the Assets window (responsibility: Assets, Vision Operations):
(N) Assets>Asset Workbench
FA_TRANSACTION_HEADERS
This table tracks all of the transactions performed in Oracle Assets. If you are writing
any reports, this table is the driver for all transactions. Oracle Assets inserts rows into
this table each time you enter a transaction.
Major Columns
TRANSACTION_HEADER_ID (PK)
BOOK_TYPE_CODE
ASSET_ID
TRANSACTION_TYPE_CODE
TRANSACTION_DATE_ENTERED
TRANSACTION_NAME
DATE_EFFECTIVE
.....................................................................................................................................................
8-18

.....................................................................................................................................................
FA_BOOKS
This table contains most of the information that Oracle Assets needs to calculate
depreciation for a specific asset and book. A record is created when a new asset is
added and when an asset is modified. The current record is always the one where
DATE_INEFFECTIVE is NULL.
Major Columns
TRANSACTION_HEADER_ID_IN (PK)
TRANSACTION_HEADER_ID_OUT
ASSET_ID
BOOK_TYPE_CODE
DATE_PLACED_IN_SERVICE
DEPRN_START_DATE
DATE_INEFFECTIVE
DATE_EFFECTIVE
LIFE_IN_MONTHS
ADJUSTED_COST
COST
ORIGINAL_COST
SALVAGE_VALUE
CAPITALIZE_FLAG
DEPRECIATE_FLAG
DEPRN_METHOD_CODE
Instructor Note
1 Navigate to the Books window (responsibility: Assets, Vision Operations):
(N) Assets>Asset Workbench>Books
2 FA_MC_BOOKS, an MRC subtable of FA_BOOKS, stores currency and financial
information about assets in each reporting book associated with the parent record
in FA_BOOKS.
.....................................................................................................................................................
8-19

.....................................................................................................................................................
FA_ASSET_HISTORY
This table contains information about asset reclassification, capitalizations, unit
adjustments, and partial unit retirements. Each change creates a record in the table for
auditing. However, the DATE_INEFFECTIVE field of the last entry is populated
when a new record is added. The current active record can always be found by looking
for DATE_INEFFECTIVE is NULL.
Major Columns
ASSET_ID (PK)
DATE_EFFECTIVE (PK)
DATE_INEFFECTIVE
CATEGORY_ID
ASSET_TYPE [CAP/EXP/CIP]
UNITS
TRANSACTION_HEADER_ID_IN
FA_DISTRIBUTION_HISTORY
This table contains information about the employee, location, and accounting flexfield
values you assign to an asset. The depreciation program uses this information to
allocate depreciation expenses, and the Transfers form uses it to maintain an audit trail
of asset transfers. The current record is the one where DATE_INEFFECTIVE is
NULL.
Major Columns
BOOK_TYPE_CODE
ASSET_ID
UNITS_ASSIGNED
ASSIGNED_TO
DATE_EFFECTIVE
DATE_INEFFECTIVE
CODE_COMBINATION_ID
LOCATION_ID
TRANSACTION_HEADER_ID_IN
Instructor Note
Navigate to the Mass Additions Summary window (responsibility: Assets, Vision
Operations):
(N) Asset>Asset System (B) Assignments
.....................................................................................................................................................
8-20
Oracle Assets: Depreciation Tables

.....................................................................................................................................................
Oracle Assets: Depreciation Tables

Depreciation
FA_DEPRN_PERIODS
FA_DEPRN_DETAIL
FA_DISTRIBUTION_
HISTORY
FA_BOOKS
Depreciation Tables
The following are the major tables storing depreciation details:
FA_DEPRN_DETAIL
FA_DEPRN_PERIODS
.....................................................................................................................................................
8-21

.....................................................................................................................................................
FA_DEPRN_DETAIL
This table contains the depreciation amounts that the depreciation program charges to
the depreciation expense account for a particular asset and accounting period. The
program looks at the FA_DEPRN_PERIODS table to determine whether depreciation
has been run for a particular book.
Major Columns
BOOK_TYPE_CODE (PK)
ASSET_ID (PK)
PERIOD_COUNTER (PK)
DEPRN_SOURCE_CODE [B/D]
DEPRN_RUN_DATE
DEPRN_AMOUNT
YTD_DEPRN
DEPRN_RESERVE
JE_HEADER_ID
FA_DEPRN_PERIOD
Instructor Note
FA_MC_DEPRN_DETAIL, an MRC subtable of FA_DEPRN_DETAIL table, stores
currency and financial information about asset depreciation in each reporting book.
FA_DEPRN_PERIODS
This table contains information about your depreciation periods.
Major Columns
BOOK_TYPE_CODE (PK)
PERIOD_NAME
PERIOD_COUNTER (PK)
Instructor Note
FA_MC_DEPRN_PERIODS, an MRC subtable of FA_DEPRN_PERIODS table,
stores information on depreciation periods for each reporting book.
.....................................................................................................................................................
8-22
Summary
.....................................................................................................................................................
Summary
Summary
You can maintain an accurate asset inventory by

using Oracle Assets.
You can calculate depreciation and create journal

entries by using Oracle Assets.
You can manage spending by using Oracle Assets.

You can maintain tax books by using Oracle
Assets.
.....................................................................................................................................................
8-23

.....................................................................................................................................................


.....................................................................................................................................................
8-24
9
.................................
Oracle Inventory

.....................................................................................................................................................
Objectives
Objectives

do the following:
Understand the relationship between Oracle

Inventory tables

State the major column names in each of the major
tables
Lesson Aim
In this lesson, you will learn about the relationship between the most frequently used
Oracle Inventory tables.
You will also learn about the major business functions of the Inventory module and
learn how the application stores the information in the most frequently used tables.
.....................................................................................................................................................
9-2
Overview of Oracle Inventory

.....................................................................................................................................................
Overview of Oracle Inventory

Overview
There are five major financial areas of Oracle

Inventory:
Organization and item definition

Item costs
Material transactions
Physical inventory
Cycle count
Overview
Oracle Inventory is a complete inventory management application which helps you to
control your inventory, ensures that you have an adequate supply, and increase
warehouse productivity.
.....................................................................................................................................................
9-3

.....................................................................................................................................................
Oracle Inventory Overview

Organization and Item Definition
Subinventory
Item
Subinventory
Item
Organization and Item Definition

Define organizations such as plants, service centers, and warehouses.
Define subinventories for each stockroom, including work in process, and finished
goods inventories.
Catalog items using multiple descriptive elements for easy identification and access.
Use multiple templates to simplify item definition and maintenance of item attributes.
Use any number of descriptive elements to classify your items within a catalog.
.....................................................................................................................................................
9-4
Oracle Inventory Overview

.....................................................................................................................................................
Material Movement
Shipment
Transfer
Inventory
Supplier
Receive
Deliver
Shop floor
Order
entry
Inventory
Internal
shipment
Expense
Inspect
Material Movement
Receive parts from suppliers.
Ship parts to customers.
Physical Inventory
Perform physical inventory adjustments.
Cycle Count
Perform inventory 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.
.....................................................................................................................................................
9-5

.....................................................................................................................................................
Oracle Inventory: Organizations and Default Accounts

Organizations
MTL_SECONDARY_
INVENTORIES
user of
material account for

MTL_PARAMETERS
defaults and
controls for
under
subject of
for
GL_SETS_OF_BOOKS
for
user of
Inventory Organizations and Default Accounts Tables

The following tables store organization unit and default account related information:
MTL_PARAMETERS
RCV_PARAMETERS
.....................................................................................................................................................
9-6
Oracle Inventory: Organizations and Default Accounts

.....................................................................................................................................................
This table holds the definitions that identify inventory organizations. Additional
information about classifications and information types for each organization is stored
in HR_ORGANIZATION_INFORMATION.
Major Columns
BUSINESS_GROUP_ID
LOCATION_ID
NAME
TYPE
ATTRIBUTE 1...25
Instructor Note
Navigate to the Organization window (responsibility: Inventory, Vision Operations):
This table is used to hold two distinct sets of organization information. When
ORG_INFORMATION_CONTEXT is set to CLASS this table acts as an intersection
between organizations and organization classifications. When
ORG_INFORMATION_CONTEXT is set to an information type held in
HR_ORG_INFORMATION_TYPES, the ORG_INFORMATION1-20 columns hold
details for the specific information type.
Major Columns
ORG_INFORMATION_ID (PK)
ORG_INFORMATION_CONTEXT
ORGANIZATION_ID
ORG_INFORMATION 1 ... 20
ATTRIBUTE_CATEGORY
ATTRIBUTE1 ... 20
Instructor Note
Navigate to the Organization window (responsibility: Inventory, Vision Operations):
(N) Setup>Organizations>Organizations (Organization Classifications region)
.....................................................................................................................................................
9-7

.....................................................................................................................................................
MTL_PARAMETERS
This table maintains a set of default options like general ledger accounts, locator, lots,
serial controls, inter-organization options and costing methods. Each organizations
item master and costing organizations are maintained in this table.
Major Columns
MASTER_ORGANIZATION_ID
PRIMARY_COST_METHOD
COST_ORGANIZATION_ID
AP_ACCRUAL_ACCOUNT
DEFAULT_PICKING_RULE_ID
GENERAL_LEDGER_UPDATE_CODE
MATERIAL_OVERHEAD_ACCOUNT
PURCHASE_PRICE_VAR_ACCOUNT
Instructor Note
Navigate to the Organization Parameters window (responsibility: Inventory, Vision
Operations):
(N) Setup>Organizations>Organizations (Place cursor on an Inventory
Organization) (B) Others>Choose Inventory Information>Other Accounts
Alternate Region
RCV_PARAMETERS
This table stores receiving options for each organization in which you want to receive
items. It contains one row for each organization.
Major Columns
DAYS_EARLY_RECEIPT_ALLOWED
RECEIVING_ROUTING_ID
RECEIVING_ACCOUNT
ENFORCE_SHIP_TO_LOCATION_CODE
Instructor Note
Navigate to the Receiving Options window (responsibility: Inventory, Vision
Operations):
(N) Setup>Organizations>Organizations (Place cursor on an Inventory
Organization) (B) Others>Choose Receiving Information
.....................................................................................................................................................
9-8
Oracle Inventory: Subinventories and Default Accounts

.....................................................................................................................................................
Oracle Inventory: Subinventories and Default Accounts

Subinventories
MTL_SECONDARY_
INVENTORIES
user of
material account for

MTL_PARAMETERS
defaults and
controls for
under
subject of
for
GL_SETS_OF_BOOKS
for
user of
Subinventories and Default Accounts Tables

MTL_SECONDARY_INVENTORIES table stores subinventories and default
account information.
This table is the definition table for subinventories. Subinventories are assigned to
items, indicating a list of valid places in which this item is located. This table includes
default accounts for inventory material asset value.
Major Columns
SECONDARY_INVENTORY_NAME (PK)
MATERIAL_ACCOUNT
Instructor Note
Navigate to the Subinventories Summary window (responsibility: Inventory, Vision
Operations):
(N) Setup>Organizations>Subinventories
.....................................................................................................................................................
9-9

.....................................................................................................................................................
Oracle Inventory: Item Tables

Item Master
MTL_SYSTEM_ITEMS
MTL_ITEM_CATALOG_GROUPS
MTL_DESCR_ELEMENT_VALUES
MTL_PARAMETERS
Inventory Item Tables

The following tables store inventory item related information:
MTL_SYSTEM_ITEMS
CST_COST_TYPES
CST_ITEM_COSTS
This table holds the definition of an inventory organization. For more information on
this table, please see the Oracle Inventory: Organizations and Default Accounts
section.
This 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. When
associated with an item catalog group, the item inherits the descriptive elements of that
group which then behaves like additional attributes.
Item catalog group is a key flexfield (flex code MICG).
.....................................................................................................................................................
9-10

.....................................................................................................................................................
MTL_ITEM_CATALOG_GROUPS (continued)
Major Columns
ITEM_CATALOG_GROUP_ID (PK)
ENABLED_FLAG
SEGMENT1 ... 20
MTL_SYSTEM_ITEMS
This is the definition table for items. This table holds the definitions for inventory
items and other noninventory purchasing items such as pencils, pens, and desks. An
item is uniquely identified by INVENTORY_ITEM_ID and ORGANIZATION_ID.
Inventory item identifiers are a key flexfield, like account numbers and asset category.
An inventory item can be assigned to more than one inventory organization.
Major Columns
DESCRIPTION
SEGMENT1...SEGMENT20
SUMMARY_FLAG
ENABLED_FLAG
PURCHASING_ITEM_FLAG
SHIPPABLE_ITEM_FLAG
CUSTOMER_ORDER_FLAG
INTERNAL_ORDER_FLAG
SERVICE_ITEM_FLAG
INVENTORY_ITEM_FLAG
INVENTORY_ASSET_FLAG
SO_TRANSACTION_FLAG
STOCK_ENABLED_FLAG
VENDOR_WARRANTY_FLAG
INVOICEABLE_ITEM_FLAG
PRIMARY_UOM_CODE
MUST_USE_APPROVED_VENDOR_FLAG
PRIMARY_UNIT_OF_MEASURE
MTL_TRANSACTIONS_ENABLED_FLAG
Instructor Note
Navigate to the Master Items window (responsibility: Inventory, Vision Operations):
(N) Items>Master Items>Find
.....................................................................................................................................................
9-11

.....................................................................................................................................................
This table stores the descriptive element values for a specific item. When an item is
associated with a particular item catalog group, one row per descriptive element (for
that catalog group) is inserted into this table. This table is then updated with the
descriptive element values that the user specifies for the item. An item can only be
assigned to one item catalog group and will therefore only have descriptive elements
for a single catalog group.
Major Columns
ELEMENT_NAME (PK)
CST_COST_TYPES
This table stores the cost type definition. Cost types represent sets of costs such as last
years cost, frozen cost and next years cost. A cost type can be shared among
organizations (public) or non-shared (private). This table is seeded with three cost
types: frozen, average and pending. All costs reference a cost type. The frozen cost
type is utilized for recording the financial impact of inventory transactions.
Major Columns
COST_TYPE_ID (PK)
COST_TYPE
Instructor Note
Navigate to the Cost Types window (responsibility: Inventory, Vision Operations):
(N) Setup>Costs>Cost Types
.....................................................................................................................................................
9-12

.....................................................................................................................................................
CST_ITEM_COSTS
This table stores item cost control information by cost type.
For standard cost organizations, the item cost control information for frozen cost type
is created when you enter a new item. For average cost organizations, the item cost
control information is created when you transact the item for the first time.
Major Columns
COST_TYPE_ID (PK)
ITEM_COST
Instructor Note
Navigate to Item Costs Summary window (responsibility: Inventory, Vision
Operations):
(N) Costs>Item Costs
.....................................................................................................................................................
9-13

.....................................................................................................................................................
Oracle Inventory: Transaction Tables

Inventory Transactions
MTL_ONHAND_
QUANTITIES
MTL_TRANSACTION
_ACCOUNTS
GL_CODE_
COMBINATIONS
LOCATOR
MTL_SYSTEM_ITEMS
SUB_INVENTORY
MTL_MATERIAL_TRANSACTIONS_TEMP
Transaction Tables
The following tables store transaction related information:
MTL_TRANSACTION_TYPES
.....................................................................................................................................................
9-14

.....................................................................................................................................................
MTL_TRANSACTION_TYPES
This table stores seeded as well as user defined transaction types.
Major Columns
TRANSACTION_TYPE_ID (PK)
TRANSACTION_TYPE_NAME
TRANSACTION_ACTION_ID
TRANSACTION_SOURCE_TYPE_ID
USER_DEFINED_FLAG
ATTRIBUTE1 ... 15
Instructor Note
Navigate to the Transaction Types window (responsibility: Inventory, Vision
Operations):
(N) Setup>Transactions>Types
.....................................................................................................................................................
9-15

.....................................................................................................................................................
This table stores a record of every material transaction and cost update performed in
Oracle Inventory. Records are inserted through either the transaction processor or the
standard cost update program.
Major Columns
TRANSACTION_ID (PK)
INVENTORY_ITEM_ID
ORGANIZATION_ID
TRANSACTION_TYPE_ID
TRANSACTION_ACTION_ID
TRANSACTION_SOURCE_ID
TRANSACTION_SOURCE_NAME
TRANSACTION_UOM
PRIMARY_QUANTITY
TRANSACTION_DATE
PROJECT_ID
TASK_ID
TO_TASK_ID
SOURCE_PROJECT_ID
SOURCE_TASK_ID
TO_PROJECT_ID
Instructor Note
Navigate to the Material Transactions window (responsibility: Inventory, Vision
Operations):
(N) Transactions>Material Transactions
.....................................................................................................................................................
9-16

.....................................................................................................................................................
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. This table is updated by the Cost
Manager by using cost information from CST_ITEM_COSTS.
Major Columns
INVENTORY_ITEM_ID
ORGANIZATION_ID
TRANSACTION_DATE
TRANSACTION_SOURCE_ID
GL_BATCH_ID
ACCOUNTING_LINE_TYPE
BASE_TRANSACTION_VALUE
REFERENCE _ACCOUNTS
TRANSACTION_ID
REFERENCE_ACCOUNT
RATE_OR_AMOUNT
Instructor Note
Navigate to the Distributions window (responsibility: Inventory, Vision Operations):
(N) Transactions>Material Transactions (B) Distributions
.....................................................................................................................................................
9-17

.....................................................................................................................................................
This table stores quantity-on-hand information.
Major Columns
DATE_RECEIVED (PK)
SUBINVENTORY_CODE
REVISION
Instructor Note
Navigate to the Item On-hand Quantities window (responsibility: Inventory, Vision
Operations):
(N) Onhand, Availability>Onhand Quantities
.....................................................................................................................................................
9-18
Oracle Inventory: Physical Inventory Tables

.....................................................................................................................................................
Oracle Inventory: Physical Inventory Tables

Physical Inventory
MTL_
PHYSICAL_
INVENTORY_
TAGS
MTL_
SECONDARY_
INVENTORIES
MTL_
PHYSICAL_
ADJUSTMENTS
MTL_PHYSICAL_
SUBINVENTORIES
MTL_PHYSICAL_
INVENTORIES
MTL_SYSTEM_ITEMS
MTL_
MATERIAL_
TRANSACTIONS
Physical Inventory Table

The following table stores information about the financial impact of a physical
inventory adjustment:
MTL_PHYSICAL_ADJUSTMENTS
.....................................................................................................................................................
9-19

.....................................................................................................................................................
MTL_PHYSICAL_ADJUSTMENTS
This table 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.
Major Columns
ADJUSTMENT_ID
PHYSICAL_INVENTORY_ID
ORGANIZATION_ID
INVENTORY_ITEM_ID
SUBINVENTORY_NAME
LOCATOR_ID
LOT_NUMBER
SERIAL_NUMBER
GL_ADJUST_ACCOUNT
Instructor Note
All other tables shown in the slide contain information used to produce count sheets,
or to download count information to a hand-held counter.
.....................................................................................................................................................
9-20
Oracle Inventory: Cycle Count Tables

.....................................................................................................................................................
Oracle Inventory: Cycle Count Tables

Cycle Count
MTL_CC
SCHED_COUNT
XREFS
MTL_CYCLE_
COUNT_
ENTRIES
MTL_
MATERIAL_
TRANSACTIONS
MTL_
SYSTEM_ITEMS
MTL_CC_
SCHEDULE_
REQUESTS
MTL_CYCLE_
COUNT_ITEMS
MTL_CYCLE_
COUNT_HEADERS
MTL_CYCLE_
COUNT_
CLASSES
Cycle Count Tables

The following table stores information about the results of a cycle count:
MTL_CYCLE_COUNT_ENTRIES
MTL_CYCLE_COUNT_ENTRIES
This table stores the actual results 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.
Major Columns
CYCLE_COUNT_ENTRY_ID (PK)
ITEM_INVENTORY_ID
SUBINVENTORY
CYCLE_COUNT_HEADER_ID
INVENTORY_ADJUST_ACCOUNT
Instructor Note
All other tables shown in the slide contain information used to produce count sheets,
or to download count information to a hand-held counter.
.....................................................................................................................................................
9-21

.....................................................................................................................................................
Inventory to General Ledger: Data Transfer

Passing Inventory Information to
General Ledger
Inventory
Inventory transfer to GL by Inventory Organization
GL_INTERFACE
Journal Import
General Ledger
Inventory Transfer to General Ledger

Data is transferred to Oracle General Ledger for each inventory organization using the
Transfer to GL process. The Journal Import process must then be run to create journal
entries in GL_JE_BATCHES, GL_JE_HEADERS and GL_JE_LINES.
The ORG_GL_BATCHES table is used while transferring data from Inventory to
General Ledger:
ORG_GL_BATCHES
This table holds history rows for every batch of transactions that have been interfaced
to the GL_INTERFACE table. When you run the GL Transfer function, a new row is
inserted into this table using the next GL_BATCH_ID number. This GL_BATCH_ID
is used in the MTL_TRANSACTION_ACCOUNTS table to mark records which have
been transferred to the GL_INTERFACE table.
Major Columns
ACCT_PERIOD_ID
GL_BATCH_DATE
LAST_UPDATE_LOGIN
GL_BATCH_ID (PK)
.....................................................................................................................................................
9-22
Summary
.....................................................................................................................................................
Summary
Summary
In this lesson, you should have learned about the

financial functions that occur in Oracle Inventory.
Oracle Inventory contains the following business
functions:
Organizations
Item master
Inventory movement
Cycle counts
Physical inventory
.....................................................................................................................................................
9-23

.....................................................................................................................................................


.....................................................................................................................................................
9-24

Oracle Financials Functional Foundation Release 11 Volume 1 Instructor Guide

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Oracle Financials Functional Foundation Release 11 Volume 1 Instructor Guide

Caricato da

Copyright:

Formati disponibili

Oracle Financials Functional

Copyright Oracle Corporation, 1999. All rights reserved.

Restricted Rights Legend

Security Tables: Data Groups 3-11

Oracle Order Entry 4-8

Oracle Purchasing: Receiving Default Information 6-26

Lesson 9: Oracle Inventory

Lesson 11: Oracle Receivables

Lesson 13: Oracle Self-Service Web Applications

Appendix B: Database Tables and Their Primary and Foreign Key

Do not save changes to the database.

Use the SELECT command to view

Typographic Conventions in Code

Typographic Conventions in Navigation Paths

Lesson 1: Course Introduction

After completing this course, you should be able to

Describe the directory structure for Oracle

Read and evaluate entity relationship diagrams

Use an open interface

Copyright Oracle Corporation, 1999. All rights reserved.

Lesson 1: Course Introduction

Oracle Applications Products Overview

Copyright Oracle Corporation, 1999. All rights reserved.

Oracle Applications Overview

Copyright Oracle Corporation, 1999. All rights reserved.

Oracle Financial Applications

Lesson 1: Course Introduction