Oracle ERP ER Diagrams

Shop Floor Management ER Diagram

Triniti CEO Srinath Alamela architected Oracle Shop Floor Management (OSFM) in the late 90's as
an extension to Oracle Discrete Work in Process(WIP) module. It was to facilitate Manufacturing
Execution Systems (MES) such as Workstream, PROMIS etc to be integrated into Oracle at a Lot
transaction level. Oracle WIP tracking could not handle complex transactions such as splits,
merges prior to OSFM.

Attached is the ER Diagram for this module. It can also be used for Oracle Discrete WIP. Tables
with prefix WSM are OSFM specific.
BOM and Routing ER Diagrams
The Oracle R12 Bill Of Materials and Routing ER diagram shows all BOM and Routing tables that
are used in Oracle R12 Shop Floor Management.

The Entity Relationship Diagram (ERD) reflects Oracle R12 BOM and Routing Table wise Data
Model which illustrates the relation between each table primary key and Reference Table foreign key.

Routing ER Diagram

Purchasing ER Diagram
The Oracle R12 Purchasing Module ER Diagram shows all Purchasing and Receiving tables that are
used in Oracel R12 PO Module. The Entity Relationship Diagram (ERD) reflects Oracel R12 PO
Table wise Data Model which illustrates the relation between each table primary and reference table
freign key.
Oracle R12 eBTax ER Diagram
Oracle R12 eBTax ER diagram shows all eBTax tables that are used in Oracle R12 eBTax Module
Oracle Advanced Pricing ER Diagram
Oracle TCA - Customer Account key primary and
foreign key definitions
Oracle EBusiness Suite Trading Community Architecture ER Diagram - a useful guide to writing
queries. Limited to only the primary and foreign keys to optimize content on page. We will add the
Supplier side as well shortly.

ORACLE APPS SUPPLY CHAIN

MANAGEMENT TABLES ERD DIAGRAM

Oracle inventory main reporting tables.

MTL_MATERIAL_TRANSACTIONS

Base table for all transactions (etc RCV,Issuance,Sub Inv Transfer,Inter Org Transfer,Misl
Transactions).

MTL_SYSTEM_ITEMS

Table contains all System items organization wise. It is Base table for items.
This table holds the definitions for inventory items, engineering items, and
purchasing items. The flexfield code is MSTK. The primary key for an item is the
INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in
more than one organization. Each row represents an item in an organization.

MTL_SYSTEM_ITEMS_TL

Table contains translated description of each master item.

The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID and LANGUAGE.

MTL_TRANSACTION_TYPES

Transaction types and names.

ORG_ACCT_PERIODS

Organization wise accounting periods.

GL_CODE_COMBINATIONS

Stores valid Accounting Flexfield segment value combinations for each accounting
flexfield structure within your General Ledger. Primary key: CODE_COMBINATION_ID.

MTL_SECONDARY_INVENTORIES

This table is the definition table for the subinventory. Subinventories are assigned to
items, indicating a list of valid places in which this item may be located. The
primary key is SECONDARY_INVENTORY_NAME, ORGANIZATION_ID.

MTL_ITEM_CATEGORIES
This table stores the item assignments to categories within a category set. For each
assignment, this table stores the item, category set, and the category. Items can be
assigned to multiple categories and category sets, but can be assigned to only one
category in a given category set. This table is populated through either the Define
Item or the Update Item/Org Attributes forms. It can also be populated by
performing item assignments when a category set is defined. The primary key is
INVENTORY_ITEM_ID, ORGANIZATION_ID, CATEGORY_SET_ID.

Oracle Purchasing main reporting tables.

RCV_TRANSACTIONS

You can get data of all receiving transactions in this table.

Important columns

TRANSACTION_TYPE like DELIVER,REJECT,ACCEPT,CORRECT,RETURN TO RECEIVING

TRANSFER, RETURN TO VENDOR, RECEIVE.

Also you can directly connect to shipment and purchase order tables for rcv_transactions

By SHIPMENT_HEADER_ID and PO_HEADER_ID.

PO_HEADERS_ALL

Get purchase order header level information from this table.

Important Columns

TYPE_LOOKUP_CODE indicates purchase order type like RFQ, STANDARD.

PO_LINES_ALL

Get purchase order live level information from this table.

Important columns

ITEM_ID join with table MTL_SYSTEM_ITEMS column ITEM_ID to get item all information.

PO_VENDORS
Get vendor level information from this table.

Important columns

PO_VENDOR_SITES_ALL

Get vendor sites information from this table in detail.

Understanding the Core Oracle E-Business

Suite HRMS Tables

There are hundreds of tables in Oracle E-Business Suite HRMS, but some are
used more frequently than others. When querying, it is important to not only
know the common tables that are used, but also to understand how the tables
link together. Some of the common tables are listed below.
Common HRMS Tables

The chart above shows some of the most common tables that are used in
Oracle HRMS. Often, a column in one table will link to a column in a different
table. For example, the primary key PERSON_ID in the
PER_ALL_PEOPLE_F table will link to the foreign key PERSON_ID in the
PER_ALL_ASSIGNMENTS_F table to connect people to their appropriate
assignments. The Entity Relationship Diagram (ERD) below reflects Oracles
Logical Data Model which illustrates the connections between each table
(Click to enlarge).
Here are a few examples of interpretations:

A person may have one or many assignments, but an assignment must

be assigned to a person
 A position must have only one organization, but an organization has
one or many positions

A position may be in many assignments, but an assignment be only be

linked to one position

ERD Key