2. Oracle Application Object Library:
Security
FND_RESPONSIBILITY_TL
FND_DATA_
FND_USER
GROUP_UNITS
FND_USER_ FND_DATA_
RESP_GROUPS GROUPS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
3. Oracle Application Object Library:
Key Flexfields
FND_ID_ FND_ID_
FND_ID_FLEXS FLEX_SEGMENTS
FLEX_
STRUCTURES
APPLICATION
FND_FLEX_VALUE_SETS
TABLE
FND_FLEX_ FND_FLEX_
VALUES VALIDATION_
TABLES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
4. Oracle Application Object Library:
Descriptive Flexfields
FND_DESCR_FLEX_COLUMN_USAGES
FND_DESCR_ FND_FLEX_VALUE_SETS
FLEX_CONTEXT
FND_FLEX_
VALIDATION_ FND_FLEX_
TABLES VALUES
TABLE
APPLICATION
FND_DESCRIPTIVE_FLEXS TABLE
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
5. Inventory Database
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
6. Oracle Inventory Database Summary Diagram
Org MTL_PARAMETERS HR_ORGANIZATION_UNITS
Item MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_TL
MTL_MATERIAL MTL_TRANSACTION
Trans TRANSACTIONS ACCOUNTS
O/H MTL_ONHAND_QUANTITIES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
7. Oracle Inventory: Organizations
From MTL_INTERORG_
MTL_PARAMETERS
To PARAMETERS
HR_ALL GL_CODE_
ORGANIZATION_ COMBINATIONS
UNITS
HR_ORGANIZATION_
INFORMATION GL_SETS_OF_BOOKS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
8. Oracle Inventory:
Subinventories and Locators
MTL_PARAMETERS MTL_SYSTEM_ITEMS_B
GL_CODE_
COMBINATIONS
MTL_SECONDARY_ MTL_ITEM_
INVENTORIES SUB_INVENTORIES
MTL_ITEM_ MTL_SECONDARY_
LOCATIONS LOCATORS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
9. Oracle Inventory:
Item Master / Template / Status
MTL_PARAMETERS MTL_ITEM_ MTL_ITEM_
TEMPLATES ATTRIBUTES
MTL_ITEM_STATUS
MTL_ITEM_
TEMPL_ATTRIBUTE
MTL_PENDING_
ITEM_STATUS
MTL_STATUS_ATTRIBUTE_VALUES
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_TL
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
10. Oracle Inventory Item Controls
MTL_SYSTEM_ITEMS_B
MTL_LOT_NUMBERS MTL_SERIAL_NUMBERS MTL_ITEM_REVISIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
11. Oracle Inventory: Item Categories
MTL_ITEM_CATEGORIES MTL_SYSTEM_ITEMS_B
MTL_CATEGORY_
SET_VALID_CATS
MTL_CATEGORIES_B MTL_CATEGORY_
SETS_B
FND_ID_FLEX_
STRUCTURES
MTL_CATEGORIES_TL MTL_CATEGORY_SETS_TL
MTL_DEFAULT_
CATEGORY_SETS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
12. Oracle Inventory: ABC Analysis
MTL_SYSTEM_ITEMS_B MTL_SECONDARY INVENTORIES
MTL_ABC_COMPILES
MTL_ABC_ MTL_ABC_COMPILE_
ASSIGNMENTS HEADERS
MTL_ABC_
MTL_ABC_ MTL_ABC_ASSIGN_ ASSIGNMENT_
CLASSES GROUP_CLASSES GROUPS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
13. Oracle Inventory: Item Catalogs
MTL_ITEM_CATALOG_GROUPS
MTL_DESCRIPTIVE_ELEMENTS
MTL_SYSTEM_ITEMS_B
MTL_DESCR_ELEMENT_VALUES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
14. BOM and Engineering
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
15. Oracle BOM: Bills of Material
MTL_SYSTEM_ITEMS
MTL_ITEM ASSEMBLY COMPONENT
REVISIONS
BOM_BILL_OF_
MATERIALS
BOM
BOM_INVENTORY_COMPONENTS OPERATION
SEQUENCES
MTL_SECONDARY MTL_ITEM
INVENTORIES LOCATIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
16. Oracle Bills of Material/Engineering
Resources and Departments
BOM_RESOURCES
BOM_
DEPARTMENT_
RESOURCES
BOM_DEPARTMENTS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
17. Oracle BOM: Routings
MTL_SYSTEM_ITEMS
ASSEMBLY O/P ITEM
MTL BOM_OPERATIONAL
ITEM_RTG ROUTINGS
REVISIONS
BOM_OPERATION
SEQUENCES
BOM_OPERATION
BOM_RESOURCES
RESOURCES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
18. Oracle BOM/Engineering Change Control
BOM_
ENG_CURRENT_
INVENTORY_
SCHEDULED_DATES
COMPONENTS
BOM_BILL_OF_ MTL_
MATERIALS SYSTEM_
PRIMARY ITEMS_B
ENG_ BILL
REVISED_
COMPONENTS ENG_
ALTERNATE
REVISED_ BILL
ITEMS
ENG_
CHANGE_
ORDER_
REVISIONS ENG_ENGINEERING_CHANGES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
19. Cost Management
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
20. Cost Type: Standard
CST_COST MTL_SYSTEM
TYPES ITEMS_B
CST_COST_ BOM
ELEMENTS DEPARTMENTS
CST_ITEM_COSTS
BOM_ BOM_OPER
RESOURCES SEQUENCES
CST_ITEM_COST_DETAILS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
21. Cost Type: Avg, LIFO, FIFO
CST_COST MTL_SYSTEM
TYPES ITEMS_B
CST_COST_ BOM
ELEMENTS DEPARTMENTS
CST_ITEM_COSTS
BOM_ BOM_OPER
RESOURCES SEQUENCES
CST_ITEM_COST_DETAILS
CST_LAYER_COST_DETAILS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
30. Oracle Inventory Transaction Flow
External Inventory,
Receiving
Systems WIP, OM
RCV_
RCV
TRANSACTIONS_
processor
INTERFACE
MTL_ MTL_MATERIAL_ MTL_ MTL_
TRANSACTIONS_ TRANSACTIONS_ MATERIAL_ TRANSACTION_
INTERFACE TEMP TRANSACTIONS ACCOUNTS
TXN TXN Cost
processor worker processor
MTL_ONHAND_QUANTITIES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
31. Oracle Inventory:
Inventory Transactions and Item Controls
MTL_SYSTEM_ITEMS_B
MTL_SERIAL_
MTL_LOT_NUMBERS
NUMBERS
MTL_ITEM_
REVISIONS
MTL_UNIT_ MTL_TRANSACTION_
TRANSACTIONS LOT_NUMBERS
MTL_MATERIAL_TRANSACTIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
32. Oracle Inventory: Physical Inventory
MTL_SYSTEM_ITEMS_B MTL_MATERIAL_TRANSACTIONS
MTL_PHYSICAL
INVENTORIES
MTL_ MTL_PHYSICAL
MTL_
PHYSICAL_ SUBINVENTORIES
PHYSICAL_
INVENTORY_
ADJUSTMENTS
TAGS
MTL_SECONDARY
INVENTORIES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
33. Oracle Inventory: Cycle Count
MTL_CC MTL_
SCHED_COUNT SYSTEM_ITEMS_B
XREFS
MTL_CC
SCHEDULE_
REQUESTS
MTL_CYCLE
COUNT_ MTL_CYCLE
ENTRIES COUNT_ITEMS
MTL_
MTL_CYCLE MTL_CYCLE
MATERIAL_
COUNT_HEADERS COUNT_
TRANSACTIONS
CLASSES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
34. Purchasing
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
35. Oracle Purchasing: Entity Relationships
PO-VENDORS RCV_SHIPMENT_HEADERS
PO_VENDOR_SITES_ALL
RCV_SHIPMENT_LINES
PO_HEADERS_ALL
RCV_TRANSACTIONS
PO_LINES_ALL
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
36. Suppliers
PO_VENDORS HR_EMPLOYEES
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
37. Oracle Purchasing: Requisitions
PO_REQUISITION_HEADERS_ALL HR_EMPLOYEES
PO_REQUISITION_LINES_ALL MTL_SYSTEM_ITEMS_B
PO_REQ_DISTRIBUTIONS_ALL GL_CODE_COMBINATIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
38. Oracle Purchasing: Purchasing Documents
PO_HEADERS_ALL PO_RELEASES_ALL
PO_LINES_ALL MTL_SYSTEM_ITEMS_B
PO_LINE_LOCATIONS_ALL
PO_DISTRIBUTIONS_ALL GL_CODE_COMBINATIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
39. Receiving
RCV_SHIPMENT_
HEADERS
PO_LINE_ RCV_SHIPMENT_ MTL_SYSTEM_
LOCATIONS_ALL LINES ITEMS_B
PO_ RCV_ MTL_MATERIAL_
DISTRIBUTIONS_ALL TRANSACTIONS TRANSACTIONS
RCV_SUPPLY
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
40. iProcurement
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
41. Catalog Database Structure
ICX_POR_PRICE_LISTS ICX_POR_ITEMS
ICX_POR_PRICE_LIST_LINES
ICX_POR_ORACLE_ITEM_SUBTABLE
ICX_POR_ITEMS_TL
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
42. Category Database Structure
ICX_POR_ITEMS ICX_POR_CATEGORIES
ICX_POR_CATEGORY_ITEMS
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
43. Descriptors Database Structure
ICX_POR_DESCRIPTORS ICX_POR_CATEGORIES
ICX_POR_DESCRIPTORS_TL
ICX_POR_CATEGORIES_TL
ICX_POR_DESCRIPTORS_VL
ICX_POR_CATEGORIES_VL
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
44. Category Mapping Database Structure
ICX_POR_CATEGORIES
ICX_POR_CATEGORY_ORDE ICX_POR_CATEGORY_DATA_SOURC
R_MAP ES
Map Unified Catalog Map Core to Unified
To Core (Manual) Catalog (Automatic)
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
45. Local Descriptors Database Structure
ICX_POR_CATEGORIES_TL
ICX_POR_Cnnnnnn_TL
ICX_POR_Cnnnnnn_VL
Local Descriptors are columns of form
Annnnnnn where nnnnnn=RT_DESCRIPTOR_ID
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
46. Error Tracking Database Structure
ICX_POR_BATCH_JOBS
ICX_POR_FAILED_LINES
ICX_POR_FAILED_LINE_MESSAGES
More than one line per ‘Item’ failure
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
47. Work in Process
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
48. Oracle Work in Process Overview
MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
WIP_REPETITIVE_
ITEMS
WIP_REPETITIVE_ WIP_DISCRETE_ WIP_FLOW_
SCHEDULES JOBS SCHEDULES
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
49. WIP: DISCRETE JOB
WIP_
ENTITIES
WIP_
ACCOUNTING
WIP_ CLASSES
DISCRETE_JOBS
WIP_SO_
ALLOCATIONS
GL_CODE_
COMBINATIONS
WIP_
OPERATIONS
ASSEMBLY
MTL_SYSTEM_ITEMS
COMPONENT
WIP_
OPERATION_
RESOURCES
WIP_JOB_
SCHEDULE_
INTERFACE
WIP_
REQUIREMENT_OPERATIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
50. WIP: REPETITIVE SCHEDULES
WIP_
ENTITIES WIP_
WIP_ ACCOUNTING
REPETITIVE_ITEMS CLASSES
WIP_ GL_CODE_
REPETITIVE_SCHEDULES WIP_LINES
COMBINATIONS
WIP_
OPERATIONS
ASSEMBLY
MTL_SYSTEM_ITEMS
COMPONENT
WIP_
OPERATION_
RESOURCES
WIP_JOB_
SCHEDULE_
INTERFACE
WIP_
REQUIREMENT_OPERATIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
51. Oracle Work in Process Operations
WIP_REQUIREMENT_OPERATIONS
MTL_
SYSTEM_
ITEMS_B
WIP_
WIP_ DISCRETE_JOBS
REPETITIVE_
SCHEDULES MTL_
ITEM_
LOCATIONS
WIP_OPERATION_ WIP_
RESOURCES SHOP_FLOOR_
STATUSES
WIP_OPERATIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
52. Oracle Work in Process: Discrete Jobs
MTL_SYSTEM_ITEMS_B
MTL_MATERIAL_
TRANSACTIONS WIP_ENTITIES
WIP_
WIP_ ACCOUNTING_
WIP_
REQUIREMENT_ CLASSES
OPERATION_
RESOURCES OPERATIONS
WIP_
DISCRETE_
JOBS WIP_WORK_
ORDER_
INTERFACE
WIP_OPERATIONS
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
53. Oracle Work in Process: Repetitive Schedules
MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
MTL_MATERIAL_ WIP_
WIP_REPETITIVE_ITEMS ACCOUNTING_
TRANSACTIONS
CLASSES
WIP_OPERATIONS
WIP_
WIP_ WORK_ORDER_
REPETITIVE_ INTERFACE
WIP_ WIP_ SCHEDULES
REQUIREMENT_ OPERATION_
OPERATIONS RESOURCES
®
Copyright Ó Oracle Corporation, 2001. All rights reserved.
54. Oracle WIP Material Transactions
WIP_REPETITIVE_SCHEDULES
MTL_
TRANSACTION_
ACCOUNTS
MTL_ WIP_
WIP_
MATERIAL_TXN REQUIREMENT_
OPERATIONS
ALLOCATIONS OPERATIONS
MTL_
MATERIAL_ WIP_DISCRETE_JOBS
TRANSACTIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
55. Oracle WIP: Move Transactions
WIP_TXN_
ALLOCATIONS
WIP_MOVE_TXN_ WIP_REPETITIVE_
ALLOCATIONS SCHEDULES
WIP_
OPERATIONS
WIP_
DISCRETE_JOBS
WIP_
TRANSACTIONS WIP_
OPERATION_
RESOURCES
WIP_MOVE_ MTL_MATERIAL_
TRANSACTIONS TRANSACTIONS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
56. Oracle WIP: Resource Transactions
WIP_TXN_ WIP_
ALLOCATIONS WIP_ REPETITIVE_
COST_TXN_ SCHEDULES
INTERFACE
WIP_OPERATION_
RESOURCE_
USAGE
WIP_
OPERATION_
RESOURCES
WIP_TRANSACTIONS
WIP_OPERATION_ WIP_
OVERHEADS OPERATIONS WIP_
DISCRETE_
WIP_ JOBS
TRANSACTION_
ACCOUNTS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
57. Oracle WIP: Completion Transactions
MTL_ WIP_
MATERIAL_TXN_ REPETITIVE_
ALLOCATIONS SCHEDULES
MTL_
TRANSACTION
ACCOUNTS
MTL_MATERIAL_
WIP_FLOW_
TRANSACTIONS_
SCHEDULES
TEMP
MTL_MATERIAL_
TRANSACTIONS
WIP_DISCRETE_
JOBS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
58. Oracle WIP: Work Order-less Completions
MTL_
TRANSACTIONS_ WIP_PERIOD_
INTERFACE BALANCES
MTL_MATERIAL_
TRANSACTIONS
MTL_MATERIAL_ WIP_
TRANSACTIONS_ WIP_
FLOW_
TEMP TRANSACTIONS
SCHEDULES
BOM_
BILL_OF_
WIP_ENTITIES
MATERIALS
BOM_
OPERATIONAL_
ROUTINGS
®
0-00 A Copyright Ó Oracle Corporation, 2001. All rights reserved.
60. HZ / Customer Diagram
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
61. Oracle OM: Order Types
RA_CUST_TRX_ RA_BATCH_
TYPES_ALL SOURCES_ALL
OE_CREDIT_
CHECK_RULES
Pick
OE_WORKFLOW_ OE_TRANSACTION_ Ship
ASSIGNMENTS TYPES_ALL
OE_ORDER_
HEADERS_ALL
OE_ORDER_
LINES_ALL
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
62. Oracle OM: Orders & RMAs
OE_ORDER_ OE_PURGE_
OE_TRANSACTION SOURCES_ALL SETS
TYPES_ALL
OE_AGREEMENTS_B OE_PURGE_
OE_ORDER_
ORDERS
HEADERS_ALL
OE_SALES_ OE_SETS
OE_ORDER_
CREDITS LINES_ALL
OE_PRICE_ OE_LINE_
ADJUSTMENTS SETS
OE_ORDER_
LINES_HISTORY
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
63. Oracle OM: Items & Models
MTL_CROSS_ OE_ORDER_ MTL_CUSTOMER_
REFERENCE_TYPES LINES_ALL ITEMS
MTL_CROSS_ MTL_CUSTOMER_
REFERENCES ITEMS_XREF
MTL_SYSTEM_
ITEMS
BOM_INVENTORY_
COMPONENTS
OE_ITEMS_V
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
64. Oracle Inventory: Pricing
FND_CURRENCIES OE_AGREEMENTS_B
QP_PRICE_
LIST_HEADERS
QP_QUALIFIER_
RULES
QP_QUALIFIERS QP_PRICE_
FORMULA_LINES
QP_PRICE_
FORMULAS_B
QP_LIST_ MTL_RELATED_
LINES ITEMS
QP_PRICING_
PHASES
QP_EVENT_ QP_COUPONS
PHASES
QP_PRICING_
ATTRIBUTES
®
New Copyright Ó Oracle Corporation, 2001. All rights reserved.
Editor's Notes
MTL_PARAMETERS MTL_PARAMETERS is an inventory organization with which an item is associated. The primary key is the ORGANIZATION_ID. MTL_INTERORG_PARAMETERS This table identifies the receiving organizations linked to a particular organization. You must define the interorganizational relationship before you perform any interorganization transfers. Units of measure, distance, transfer charge, and accounting information are also specified in this table. The primary key is FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID. GL_SETS_OF_BOOKS GL_SETS_OF_BOOKS stores information about the sets of books you define in your general ledger application. Each row includes the set of books name, description, functional currency, and other information. This table corresponds to the Define Set of Books form. The primary key is SET_OF_BOOKS_ID. GL_CODE_COMBINATIONS This table stores valid Accounting Flexfield segment value combinations for each accounting flexfield structure within your general ledger application. The primary key is CODE_COMBINATION_ID. HR_ALL_ORGANIZATION_UNITS HR_ALL_ORGANIZATION_UNITS stores generic information about organizations. An organization can be used for various purposes in Oracle Manufacturing applications. For example, one organization can represent a business group, an ECO department, a planning organization, and an inventory organization. The primary key is ORGANIZATION_ID.
MTL_PARAMETERS MTL_PARAMETERS is an inventory organization with which an item is associated. The primary key is the ORGANIZATION_ID. MTL_INTERORG_PARAMETERS This table identifies the receiving organizations linked to a particular organization. You must define the interorganizational relationship before you perform any interorganization transfers. Units of measure, distance, transfer charge, and accounting information are also specified in this table. The primary key is FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID. GL_SETS_OF_BOOKS GL_SETS_OF_BOOKS stores information about the sets of books you define in your general ledger application. Each row includes the set of books name, description, functional currency, and other information. This table corresponds to the Define Set of Books form. The primary key is SET_OF_BOOKS_ID. GL_CODE_COMBINATIONS This table stores valid Accounting Flexfield segment value combinations for each accounting flexfield structure within your general ledger application. The primary key is CODE_COMBINATION_ID. HR_ALL_ORGANIZATION_UNITS HR_ALL_ORGANIZATION_UNITS stores generic information about organizations. An organization can be used for various purposes in Oracle Manufacturing applications. For example, one organization can represent a business group, an ECO department, a planning organization, and an inventory organization. The primary key is ORGANIZATION_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in more than one organization. Each row represents an item in an organization. MTL_SYSTEM_ITEMS_TL MTL_SYSTEM_ITEMS_TL is a table holding translated Description column for Items. GL_CODE_COMBINATIONS This table stores valid Accounting Flexfield segment value combinations for each accounting flexfield structure within your general ledger application. The primary key is CODE_COMBINATION_ID. MTL_SECONDARY_INVENTORIES MTL_SECONDARY_INVENTORIES is the definition table for the subinventory. Subinventories are assigned to items, indicating a list of valid places in which this item may be located. The primary key is SECONDARY_INVENTORY_NAME, ORGANIZATION_ID. MTL_ITEM_SUB_INVENTORIES MTL_ITEM_SUB_INVENTORIES maintains a listing of subinventories assigned to an inventory or engineering item. The subinventories make up the valid list of subinventories when transacting a specific item if the user has specified that the item must use subinventories from a predefined list. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, SECONDARY_INVENTORY MTL_ITEM_LOCATIONS MTL_ITEM_LOCATIONS is the definition table for stock locators. The associated attributes describe the subinventory to which this locator belongs, and the locator physical capacity. The primary key is INVENTORY_LOCATION_ID, ORGANIZATION_ID. MTL_SECONDARY_LOCATORS MTL_SECONDARY_LOCATORS stores all locators within a subinventory for a specific item. The locators make up the valid list of locators when transacting that specific item to/from the subinventory when the user has specified that the item must use locators from a predefined list. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, SECONDARY_LOCATORS. MTL_PARAMETERS MTL_PARAMETERS is an inventory organization with which an item is associated. The primary key is the ORGANIZATION_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in more than one organization. Each row represents an item in an organization. MTL_ITEM_ATTRIBUTES MTL_ITEM_ATTRIBUTES stores the item attributes, their user-friendly names if the item is maintained at the item or item/organization level, and the kind of validation required for each attribute. This table is seeded on install or upgrade. The primary key is ATTRIBUTE_NAME. MTL_ITEM_TEMPL_ATTRIBUTES MTL_ITEM_TEMPL_ATTRIBUTES stores the attributes and attribute values for a template. When a template is created, a row is inserted for each available item attribute. When the template is applied to an item, the enabled attribute values are propagated to the item. The primary key is TEMPLATE_ID, ATTRIBUTE_NAME. MTL_ITEM_STATUS MTL_ITEM_STATUS is the definition table for a material status code. The status code is a required item attribute and indicates the item status (for example, active, pending, or obsolete). You may define as many additional status codes as you want. The values of the individual status attributes associated with an item status are stored in MTL_STATUS_ATTRIBUTE_VALUES. The primary key is INVENTORY_ITEM_STATUS_CODE. MTL_ITEM_TEMPLATES MTL_ITEM_TEMPLATES is the definition table for item templates. It contains the user-defined name and description. When the template is applied to an item, the enabled item attributes are propagated to the item. The primary key is TEMPLATE_ID. MTL_STATUS_ATTRIBUTE_VALUES MTL_STATUS_ATTRIBUTE_VALUES stores the attribute values associated with an item status code. One record is created for each of the function-enabling attributes for each defined item status code. The primary key is INVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME. MTL_PARAMETERS MTL_PARAMETERS is an inventory organization with which an item is associated. The primary key is the ORGANIZATION_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in more than one organization. Each row represents an item in an organization. MTL_ITEM_ATTRIBUTES MTL_ITEM_ATTRIBUTES stores the item attributes, their user-friendly names if the attribute is maintained at the item or item/organization level, if the attribute is controlled by an item’s status, and the kind of validation required for each attribute. This table is seeded on install or upgrade. The top eight item attributes are as follows: Stockable Transactable BOM allowed WIP allowed Purchasable OE Orderable Internal Orderable Billable The primary key is ATTRIBUTE_NAME. MTL_STATUS_ATTRIBUTE_VALUES MTL_STATUS_ATTRIBUTE_VALUES stores the attribute values associated with an item status code. One record is created for each of the function-enabling attributes for each defined item status code. The primary key is INVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME. MTL_ITEM_STATUS MTL_ITEM_STATUS is the definition table for a material status code. The status code is a required item attribute and indicates the item status (for example, active, pending, or obsolete). You may define as many additional status codes as you want. The values of the individual status attributes associated with an item’s status are stored in MTL_STATUS_ATTRIBUTE_VALUES. The primary key is INVENTORY_ITEM_STATUS_CODE. MTL_PENDING_ITEM_STATUS MTL_PENDING_ITEM_STATUS is used to define and store the history of the item statuses that have been or will be assigned to an item. This table maintains the status history for each item. This table also stores pending status information. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, STATUS_CODE, EFFECTIVE_DATE.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in more than one organization. Each row represents an item in an organization. MTL_ITEM_REVISIONS MTL_ITEM_REVISIONS stores revision levels for an inventory item. When an item is defined, a starting revision record is written out to the table; every item will have at least one revision. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION. MTL_SERIAL_NUMBERS MTL_SERIAL_NUMBERS stores the definition and current status of all serial numbers in Oracle Inventory. These serial numbers are also used in other areas of Oracle Manufacturing applications. A serial number can have one of four statuses: Defined, but not used Resides in stores Issued out of stores Resides in transit The primary key is INVENTORY_ID, SERIAL_NUMBER, CURRENT_ORGANIZATION_ID. MTL_LOT_NUMBERS MTL_LOT_NUMBERS stores the definition and expiration date of all lot numbers in inventory. A lot number can exist in more than one organization or for different items. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, LOT_NUMBER.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in more than one organization. Each row represents an item in an organization. FND_ID_FLEX_STRUCTURES FND_ID_FLEX_STRUCTURES stores structure information about key flexfields. The primary key is APPLICATION_ID, ID_FLEX_CODE, ID_FLEX_NUM. MTL_CATEGORIES_B MTL_CATEGORIES_B is the code combinations table for item categories. Items are grouped into categories within the context of a category set to provide flexible grouping schemes. The primary key is CATEGORY_ID. The item category is a key flexfield with a flexfield code of MCAT. MTL_CATEGORIES_TL MTL_CATEGORIES_TL is a table holding translated Description column for Item Categories. MTL_CATEGORY_SETS_B MTL_CATEGORY_SETS_B contains the entity definition for category sets. A category set is a categorization scheme for a group of items. Items can be assigned to different categories in different category sets, but can be assigned to only one category within a category set. The primary key is CATEGORY_SET_ID. MTL_CATEGORY_SETS_TL MTL_CATEGORY_SETS_TL is a table holding translated Name and Description columns for Category Sets. MTL_CATEGORY_SET_VALID_CATS MTL_CATEGORY_SET_VALID_CATS defines the valid category list for a particular category set. If category validation is required, the list of valid categories is stored in this table and is used to restrict category selection for the category set. The primary key is CATEGORY_SET_ID, CATEGORY_ID. MTL_DEFAULT_CATEGORY_SETS MTL_DEFAULT_CATEGORY_SETS stores the identifier of the category set that acts as the default for a particular functional area. This information is used to determine the mandatory category sets for an item. It is also used to provide a default category set for forms and reports that require a category set field value or parameter. The primary key is FUNCTIONAL_AREA_ID, CATEGORY_SET_ID. MTL_ITEM_CATEGORIES MTL_ITEM_CATEGORIES stores the item assignments to categories within a category set. For each assignment, this table stores the item, category set, and the category. Items can be assigned to multiple categories and category sets, but can be assigned to only one category in a given category set. This table is populated through either the Define Item or the Update Item/Org Attributes forms. It can also be populated by performing item assignments when a category set is defined. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, CATEGORY_SET_ID.
MTL_ABC_CLASSES MTL_ABC_CLASSES contains information about ABC classes. Each row in this table defines an ABC class. An ABC class is a category under which items with similar metrics are put together. An ABC class can be used in more than one ABC group, but only once within a given group. The primary key is ABC_CLASS_ID. MTL_ABC_ASSIGNMENT_GROUPS MTL_ABC_ASSIGNMENT_GROUPS contains information for ABC groups. Each row in this table defines an ABC group and is populated by the Define ABC Group table. Oracle Inventory uses this information as the basis for ABC class assignment and item assignment. The primary key is ASSIGNMENT_GROUP_ID. MTL_ABC_ASSGN_GROUP_CLASSES MTL_ABC_ASSIGN_GROUP_CLASSES stores information about the ABC classes assigned to an ABC group. An ABC class can be assigned to one or more ABC groups, but can be used only once in each ABC group. The primary key is ASSIGNMENT_GROUP_ID, ABC_CLASS_ID. MTL_ABC_ASSIGNMENTS MTL_ABC_ASSIGNMENTS holds assignments of inventory items to ABC classes and ABC groups. Oracle Inventory uses this information to load the cycle count process. The primary key is INVENTORY_ITEM_ID, ASSIGNMENT_GROUP_ID, ABC_CLASS_ID. MTL_ABC_COMPILE_HEADERS MTL_ABC_COMPILE_HEADERS contains information used for, and that results from, an ABC compile or an ABC analysis. It holds user-specified information, such as the current compile option and cost code chosen, the results of an ABC analysis, the cumulative quantity, and the cumulative value. Oracle Inventory uses this information during the ABC compile process to determine the compile criterion and attributes used for the compile. The primary key is COMPILE_ID. MTL_ABC_COMPILES MTL_ABC_COMPILES stores information about each item within an ABC compiler. Each row includes an item's sequence number relative to other items in the given compiler, based on the criteria defined in MTL_ABC_COMPILE_HEADERS. The primary key is INVENTORY_ITEM_ID, COMPILE_ID. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID.
MTL_ITEM_CATALOG_GROUPS MTL_ITEM_CATALOG_GROUPS is the entity table for item catalog groups. An item catalog group consists of items that can be described by the same set of descriptive elements or item properties. The item catalog group assignment for an item is done at the item master organization level. The item catalog group is a key flexfield. The flexfield code is MICG. The primary key is ITEM_CATALOG_GROUP_ID. MTL_DESCRIPTIVE_ELEMENTS MTL_DESCRIPTIVE_ELEMENTS stores the descriptive element definitions for an item catalog group. Descriptive elements are defining properties used to describe the catalog group. The primary key is ITEM_CATALOG_GROUP_ID, ELEMENT_NAME. MTL_DESCR_ELEMENT_VALUES MTL_DESCR_ELEMENT_VALUES stores the descriptive element values for a specific item. An item can only be assigned to one item catalog group and will only have descriptive elements for a single catalog group. The primary key is INVENTORY_ITEM_ID, ELEMENT_NAME. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in more than one organization. Each row represents an item in an organization.
MTL_ITEM_CATALOG_GROUPS MTL_ITEM_CATALOG_GROUPS is the entity table for item catalog groups. An item catalog group consists of items that can be described by the same set of descriptive elements or item properties. The item catalog group assignment for an item is done at the item master organization level. The item catalog group is a key flexfield. The flexfield code is MICG. The primary key is ITEM_CATALOG_GROUP_ID. MTL_DESCRIPTIVE_ELEMENTS MTL_DESCRIPTIVE_ELEMENTS stores the descriptive element definitions for an item catalog group. Descriptive elements are defining properties used to describe the catalog group. The primary key is ITEM_CATALOG_GROUP_ID, ELEMENT_NAME. MTL_DESCR_ELEMENT_VALUES MTL_DESCR_ELEMENT_VALUES stores the descriptive element values for a specific item. An item can only be assigned to one item catalog group and will only have descriptive elements for a single catalog group. The primary key is INVENTORY_ITEM_ID, ELEMENT_NAME. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. The same item could be defined in more than one organization. Each row represents an item in an organization.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The item attribute BOM_ENABLED allows an item to be used in bills of material. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID. BOM_BILL_OF_MATERIALS BOM_BILL_OF_MATERIALS stores information about manufacturing and engineering bills of material. Each row represents a unique manufacturing or engineering bill and is defined by its primary key, BILL_SEQUENCE_ID. BOM_ALTERNATE_DESIGNATORS BOM_ALTERNATE_DESIGNATORS stores the alternate designators used to define alternate bills of material and routings. The primary key is ALTERNATE_DESIGNATOR_CODE (o), ORGANIZATION_ID BOM_INVENTORY_COMPONENTS BOM_INVENTORY_COMPONENTS stores information about bill of material components. COMPONENT_SEQUENCE_ID uniquely identifies each row. There is one row per component on an operation within a given date range. The primary key is COMPONENT_SEQUENCE_ID. BOM_OPERATION_SEQUENCES BOM_OPERATION_SEQUENCES stores information about routing operations. You can define multiple operations for a routing. You must specify the department in which every operation must occur. The Routing Define form prevents overlapping effective dates for the same operation. The primary key is OPERATION_SEQUENCE_ID. MTL_ITEM_LOCATIONS MTL_ITEM_LOCATIONS is the definition table for stock locators. The associated attributes describe which subinventory this locator belongs to, what the locator physical capacity is, and so on. The locator is a key flexfield; the flexfield code is MTLL. The primary key is INVENTORY_LOCATION_ID, ORGANIZATION_ID. MTL_SECONDARY_INVENTORIES MTL_SECONDARY_INVENTORIES is the definition table for the subinventory. A subinventory is a section of inventory such as raw material or finished goods. Subinventories are assigned to items, indicating a list of valid places where this item will physically exist in inventory. The primary key is SECONDARY_LOCATION_NAME, ORGANIZATION_ID. MTL_ITEM_REVISIONS MTL_ITEM_REVISIONS stores revision levels for an inventory item. When an item is defined, a starting revision record is written out to this table, so every item will at least have one starting revision. The presence of an engineering change notice code in this table indicates that the engineering system issued the revision through the implementation process. Along with the engineering change order, an implementation date and initiation date will be stored. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION.
Oracle Inventory Entity Relationship Diagram The major tables in Oracle Inventory are grouped by business function. Organizations HR_ORGANIZATION_UNITS MTL_PARAMETERS GL_CODE_COMBINATIONS GL_SETS_OF_BOOKS Item Master MTL_SYSTEM_ITEMS MTL_UNITS_OF_MEASURE MTL_ITEM_ATTRIBUTES MTL_ITEM_TEMPLATES MTL_ITEM_TEMPL_ATTRIBUTES MTL_PARAMETERS Item Controls MTL_ITEM_REVISIONS MTL_SERIAL_NUMBERS MTL_LOT_NUMBERS MTL_SYSTEM_ITEMS
BOM_RESOURCES BOM_RESOURCES stores information about material and outside processing resources. It also stores overhead, material overheads, and material subelements. COST_ELEMENT_ID determines the resource type. The primary key is RESOURCE_ID. BOM_DEPARTMENTS BOM_DEPARTMENTS stores department information. DEPARTMENT_ID is the primary key that uniquely identifies each row. You can assign a delivery location for each department used, which is used with outside processing resources. The primary key is DEPARTMENT_ID. BOM_DEPARTMENT_RESOURCES BOM_DEPARTMENT_RESOURCES stores information about resources that you assign to a department. You can use these resources on routing operations. The primary key is DEPARTMENT_ID, RESOURCE_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ID, ORGANIZATION_ID. BOM_OPERATIONAL_ROUTINGS BOM_OPERATIONAL_ROUTINGS stores information about manufacturing and engineering routings. The primary key is ROUTING_SEQUENCE_ID. BOM_ALTERNATE_DESIGNATORS BOM_ALTERNATE_DESIGNATORS stores the alternate designators you use to define alternate bills of material and routings. The primary code is ALTERNATE_DESIGNATOR_CODE (o), ORGANIZATION_ID. MTL_RTG_ITEM_REVISIONS MTL_RTG_ITEM_REVISIONS stores revision levels for routings. A revision must be inserted into this table when a routing is defined; every routing has at least one valid revision. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, PROCESS_REVISION. BOM_OPERATION_SEQUENCES BOM_OPERATION_SEQUENCES stores information about routing operations. You can define multiple operations for a routing. You must specify the department in which every operation must occur. The primary key is OPERATION_SEQUENCE_ID. BOM_OPERATION_RESOURCES BOM_OPERATION_RESOURCES stores information about resources you require to complete operations on routings. You can assign multiple resources or assign the same resource multiple times at any operation. The primary key is OPERATION_SEQUENCE_ID, RESOURCE_SEQ_NUM. BOM_RESOURCES BOM_RESOURCES stores information about material and outside processing resources. It also stores overhead, material overheads, and material subelements. COST_ELEMENT_ID determines the resource type. The primary key is RESOURCE_ID.
Oracle Inventory Entity Relationship Diagram The major tables in Oracle Inventory are grouped by business function. Organizations HR_ORGANIZATION_UNITS MTL_PARAMETERS GL_CODE_COMBINATIONS GL_SETS_OF_BOOKS Item Master MTL_SYSTEM_ITEMS MTL_UNITS_OF_MEASURE MTL_ITEM_ATTRIBUTES MTL_ITEM_TEMPLATES MTL_ITEM_TEMPL_ATTRIBUTES MTL_PARAMETERS Item Controls MTL_ITEM_REVISIONS MTL_SERIAL_NUMBERS MTL_LOT_NUMBERS MTL_SYSTEM_ITEMS
ENG_ENGINEERING_CHANGES ENG_ENGINEERING_CHANGES stores information about engineering change order headers. Each row includes the unique identifier of the ECO, a description, change order type, the reason and priority codes, the status and the requestor, approval list and approval status, implementation costs, and cancellation information. The primary key is CHANGE_NOTICE, ORGANIZATION_ID. ENG_CHANGE_ORDER_REVISIONS ENG_CHANGE_ORDER_REVISIONS stores information about the user-defined revisions of an engineering change order. It is a child table of ENG_ENGINEERING_CHANGES. The primary key is REVISION_ID. ENG_REVISED_ITEMS ENG_REVISED_ITEMS stores information about the revised items (usually assemblies) on an engineering change order. It is a child table of ENG_ENGINEERING_CHANGES. The primary key is REVISED_ITEM_SEQUENCE_ID. ENG_CURRENT_SCHEDULED_DATES ENG_CURRENT_SCHEDULED_DATES stores information about the effective date for each revised item on an engineering change order. Each time the effective date for a revised item on an ECO is changed, a new row is inserted into this table. The primary key is SCHEDULE_ID, REVISED_ITEM_SEQUENCE_ID (o). BOM_BILL_OF_MATERIALS BOM_BILL_OF_MATERIALS stores information about manufacturing and engineering bills of material. Each row represents a unique manufacturing or engineering bill and is defined by the BILL_SEQUENCE_ID primary key. BOM_INVENTORY_COMPONENTS BOM_INVENTORY_COMPONENTS stores information about bill of material components. The primary key, COMPONENT_SEQUENCE_ID, uniquely identifies each row. There is one row per component on an operation within a given date range. ENG_REVISED_COMPONENTS ENG_REVISED_COMPONENTS stores information about the implemented and canceled revised components on an engineering change order. The primary key is COMPONENT_SEQUENCE_ID. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ID, ORGANIZATION_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ID, ORGANIZATION_ID. CST_COST_TYPES CST_COST_TYPES stores the cost type definition. Cost types represent sets of costs, frozen cost, or next year’s cost. The table is seeded with the following costs types: Frozen: The organization uses the standard costing method. Pending: For standard cost organizations, Pending charges to the frozen cost. Average: The organization uses the average costing method. FIFO: The organization uses the FIFO costing method. LIFO: The organization uses the LIFO costing method. You can define as many additional cost types as you want. The primary key is COST_TYPE_ID. CST_ITEM_COSTS CST_ITEM_COSTS stores the cost control information. The Define Item Cost form inserts information into this table. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID. CST_COST_ELEMENTS CST_COST_ELEMENTS stores the cost element information. It is seeded with five cost elements: Material, Material Overhead, Resource, Outside Processing, and Overhead. The primary key is COST_ELEMENT_ID. CST_QUANTITY_LAYERS CST_QUANTITY_LAYERS stores item average cost, FIFO, and LIFO information by cost layer. This table is only used for average costing, FIFO, and LIFO organizations. The primary key is LAYER_ID. CST_LAYER_COST_DETAILS CST_LAYER_COST_DETAILS stores detailed cost information by element and level. It is a child table of CST_QUANTITY_LAYERS. The primary key is LAYER_ID, COST_ELEMENT_ID, LEVEL_TYPE. CST_ACTIVITIES CST_ACTIVITIES stores activity definitions. An activity can be organization-specific or shared among all organizations. The primary key is ACTIVITY_ID. BOM_RESOURCES BOM_RESOURCES stores information about all cost subelements, resources, overhead, material overheads, and material subelements. COST_ELEMENT_ID determines the resource type. The primary key is RESOURCE_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ID, ORGANIZATION_ID. CST_COST_TYPES CST_COST_TYPES stores the cost type definition. Cost types represent sets of costs, frozen cost, or next year’s cost. The table is seeded with the following costs types: Frozen: The organization uses the standard costing method. Pending: For standard cost organizations, Pending charges to the frozen cost. Average: The organization uses the average costing method. FIFO: The organization uses the FIFO costing method. LIFO: The organization uses the LIFO costing method. You can define as many additional cost types as you want. The primary key is COST_TYPE_ID. CST_ITEM_COSTS CST_ITEM_COSTS stores the cost control information. The Define Item Cost window inserts information into this table. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID. CST_COST_ELEMENTS CST_COST_ELEMENTS stores the cost element information. It is seeded with five cost elements: Material, Material Overhead, Resource, Outside Processing, and Overhead. The primary key is COST_ELEMENT_ID. CST_ITEM_COST_DETAILS CST_ITEM_COST_DETAILS stores detailed cost information for an item for a cost type. It is the child table of CST_ITEM_COSTS. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID. CST_ACTIVITIES CST_ACTIVITIES stores activity definitions. An activity can be organization-specific or shared among all organizations. The primary key is ACTIVITY_ID. BOM_RESOURCES BOM_RESOURCES stores information about all cost subelements, resources, overhead, material overheads, and material subelements. COST_ELEMENT_ID determines the resource type. The primary key is RESOURCE_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ID, ORGANIZATION_ID. CST_COST_TYPES CST_COST_TYPES stores the cost type definition. Cost types represent sets of costs, frozen cost, or next year’s cost. The table is seeded with the following costs types: Frozen: The organization uses the standard costing method. Pending: For standard cost organizations, Pending charges to the frozen cost. Average: The organization uses the average costing method. FIFO: The organization uses the FIFO costing method. LIFO: The organization uses the LIFO costing method. You can define as many additional cost types as you want. The primary key is COST_TYPE_ID. CST_ITEM_COSTS CST_ITEM_COSTS stores the cost control information. The Define Item Cost window inserts information into this table. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID. CST_COST_ELEMENTS CST_COST_ELEMENTS stores the cost element information. It is seeded with five cost elements: Material, Material Overhead, Resource, Outside Processing, and Overhead. The primary key is COST_ELEMENT_ID. CST_ITEM_COST_DETAILS CST_ITEM_COST_DETAILS stores detailed cost information for an item for a cost type. It is the child table of CST_ITEM_COSTS. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID. CST_ACTIVITIES CST_ACTIVITIES stores activity definitions. An activity can be organization-specific or shared among all organizations. The primary key is ACTIVITY_ID. BOM_RESOURCES BOM_RESOURCES stores information about all cost subelements, resources, overhead, material overheads, and material subelements. COST_ELEMENT_ID determines the resource type. The primary key is RESOURCE_ID.
BOM_DEPARTMENTS BOM_DEPARTMENTS stores department information. DEPARTMENT_ID is the primary key and uniquely identifies each row. CST_RESOURCE_COSTS CST_RESOURCE_COSTS stores resource and outside processing resource unit costs by a cost type. The primary key is RESOURCE_ID, COST_TYPE_ID. CST_COST_TYPES CST_COST_TYPES stores the cost type definition. Cost types represent sets of costs, frozen cost, and next year’s cost. The table is seeded with the following costs types: Frozen: The organization uses the standard costing method. Pending: For standard cost organizations, Pending charges to the frozen cost. Average: The organization uses the average costing method. FIFO: The organization uses the FIFO costing method. LIFO: The organization uses the LIFO costing method. You can define as many additional cost types as you want. The primary key is COST_TYPE_ID. CST_RESOURCE_OVERHEADS CST_RESOURCE_OVERHEADS stores the list of resources to which an overhead applies. The cost processor looks at this table to find the overheads that need to be absorbed. The primary key is COST_TYPE_ID, RESOURCE_ID, OVERHEAD_ID. CST_DEPARTMENT_OVERHEADS CST_DEPARTMENT_OVERHEADS stores overhead rates for a cost type. You can define overhead rates in the Define Overhead window. The primary key is DEPARTMENT_ID, COST_TYPE_ID, OVERHEAD_ID. BOM_RESOURCES BOM_RESOURCES stores information about resources, overhead, material overheads, and material subelements. COST_ELEMENT_ID determines the resource type. The primary key is RESOURCE_ID.
MTL_TRANSACTIONS_INTERFACE This is the interface point between non-Inventory applications and the Inventory transaction module. The Transaction Manager concurrent program polls this table at a user-specified process interval and submits the transaction workers to process them. Processing consists of data derivation, validation, and transfer of records from MTL_TRANSACTIONS_INTERFACE, MTL_TRANSACTION_LOTS_INTERFACE, and MTL_SERIAL_NUMBERS_INTERFACE into their respective TEMP tables, from where they are processed by the transaction processor. MTL_MATERIAL_TRANSACTIONS_TEMP This table is the gateway for all material transactions. Records are processed from this table into Inventory through the transaction processor. All Inventory transaction forms write directly to this table. Outside applications must write transaction records to MTL_TRANSACTSIONS_INTERFACE to be processed through MTL_MATERIAL_TRANSACTIONS_TEMP and the transaction processor by the Transaction Worker concurrent program. MTL_MATERIAL_TRANSACTIONS This table stores a record of every material transaction or cost update performed in Inventory. Records are inserted into this table either through the transaction processor or by the standard cost program. The primary key is TRANSACTION_ID. MTL_TRANSACTION_ACCOUNTS This table holds the accounting information for each material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information to track the financial impact of your quantity moves. Instructor Note There is no primary key for this table in the TRM.
MTL_UNIT_TRANSACTIONS MTL_UNIT_TRANSACTIONS stores a record of every material transaction of a serialized unit in Oracle Inventory. Records are inserted into this table through the transaction processor. The primary key is TRANSACTION_ID, SERIAL_NUMBER. MTL_SERIAL_NUMBERS MTL_SERIAL_NUMBERS stores the definition and current status of all serial numbers in Oracle Inventory. These serial numbers are also used in other areas of Oracle Manufacturing applications. The primary key is INVENTORY_ITEM_ID, SERIAL_NUMBER, CURRENT_ORGANIZATION_ID. MTL_TRANSACTION_LOT_NUMBERS MTL_TRANSACTION_LOT_NUMBERS stores lot number information for transactions in the MTL_MATERIAL_TRANSACTIONS table. The primary key is TRANSACTION_ID, LOT_NUMBER. MTL_LOT_NUMBERS MTL_LOT_NUMBERS stores the definition and expiration date of all lot numbers in Oracle Inventory. The primary key is INVNETORY_ITEM_ID, ORGANIZATION_ID, LOT_NUMBER. MTL_ITEM_REVISIONS MTL_ITEM_REVISIONS stores the revision levels for an inventory item. When an item is defined, a starting revision record is written to this table so that every item has at least one revision. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID.
MTL_PHYSICAL_SUBINVENTORIES MTL_PHYSICAL_SUBINVENTORIES specifies which subinventories are involved in a physical inventory when the physical inventory does not include all subinventories. The primary key is ORGANIZATION_ID, PHYSICAL_INVENTORY_ID, SUBINVENTORY. MTL_SECONDARY_INVENTORIES MTL_SECONDARY_INVENTORIES is the definition table for the subinventory. Subinventories are assigned to items, indicating a list of valid places in which this item is located. The primary key is SECONDARY_INVENTORY_NAME, ORGANIZATION_ID. MTL_PHYSICAL_INVENTORY_TAGS MTL_PHYSICAL_INVENTORY_TAGS stores information regarding physical inventory tags, including tag number, SKU information, tag quantity, and a pointer to the corresponding adjustment in MTL_PHYSICAL_ADJUSTMENTS. A change to this table can require a change to MTL_PHYSICAL_ADJUSTMENTS to ensure that the information therein remains consistent with its tags. The primary key is TAG_ID. MTL_PHYSICAL_ADJUSTMENTS MTL_PHYSICAL_ADJUSTMENTS contains all information about the adjustment transactions, including the size of the necessary adjustment, the accounts to which the adjustment transaction was posted, and the approval status of each transaction. The primary key is ADJUSTMENT_ID. MTL_MATERIAL_TRANSACTIONS MTL_MATERIAL_TRANSACTIONS stores a record of every material transaction or cost update performed in Inventory. Records are inserted into this table either through the transaction processor or by the standard cost update program. The primary key is TRANSACTION_ID. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID. MTL_CYCLE_COUNT_ITEMS MTL_CYCLE_COUNT_ITEMS stores information about all items eligible for cycle counting within the scope of a cycle count name. Oracle Inventory uses this information to direct the cycle count scheduling process, and as a validation table when entering manual schedule requests. The primary key is CYCLE_COUNT_HEADER_ID, INVENTORY_ITEM_ID. MTL_CYCLE_COUNT_CLASSES MTL_CYCLE_COUNT_CLASSES stores information about cycle count classes, such as associated cycle count name, approval tolerance limits, and minimum counting frequency. Oracle Inventory uses Cycle Count Classes as a unit for specifying and defaulting cycle count attributes. The primary key is ABC_CLASS_ID, CYCLE_COUNT_HEADER_ID. MTL_CYCLE_COUNT_HEADERS MTL_CYCLE_COUNT_HEADERS stores information about cycle count names. Oracle Inventory uses this information to track defined cycle count names, to indicate tolerance/approval limits, cycle count calendar and exception set, ABC initialization information, scheduling options, and recount options. The primary key is CYCLE_COUNT_HEADER_ID. MTL_CC_SCHEDULE_REQUESTS MTL_CC_SCHEDULE_REQUESTS stores cycle count schedule requests. Oracle Inventory uses this information to feed the count generation process and generate Cycle Count Requests that show up in the Count List Reports. The primary key is CYCLE_COUNT_SCHEDULE_ID. MTL_CC_SCHED_COUNT_XREFS MTL_CC_SCHED_COUNT_XREFS links cycle counts entered to the schedule request that generated it. Oracle Inventory uses this information to determine when a schedule request has been completed and to update its status. The primary key is CYCLE_COUNT_SCHEDULE_ID, CYCLE_COUNT_ENTRY_ID. MTL_CYCLE_COUNT_ENTRIES MTL_CYCLE_COUNT_ENTRIES stores the actual counts of a cycle count. A row in this table without a count is considered to be a count request. Oracle Inventory uses this information to determine and store cycle count adjustments, recounts, and approval requirements. The primary key is CYCLE_COUNT_ENTRY_ID. MTL_MATERIAL_TRANSACTIONS MTL_MATERIAL_TRANSACTIONS stores a record of every material transaction or cost update performed in Inventory. Records are inserted into this table either through the transaction processor or by the standard cost update program. The primary key is TRANSACTION_ID.
PO_VENDORS This table stores information about your suppliers. Oracle Purchasing uses this information to determine active suppliers. The primary key is VENDOR_ID. RCV_SHIPMENT_HEADERS This table stores common information about the source of your receipts or expected receipts. You group your receipts by the source type and the source of the receipt. Oracle Purchasing does not allow you to group receipts from different sources under one receipt header. The primary key is SHIPMENT_HEADER_ID. PO_VENDOR_SITES_ALL This table stores information about supplier sites. Oracle Purchasing uses this information to store supplier address information. The primary key is VENDOR_SITE_ID. RCV_SHIPMENT_LINES This table stores information about items that have been shipped or received from a specific receipt source. This table also stores information about the default destination for in-transit shipments. The primary key is SHIPMENT_LINE_ID. PO_HEADERS_ALL PO_HEADERS_ALL contains information for your purchasing documents. Each row contains buyer information, supplier information, notes, foreign currency information, terms and conditions information, and the document status. Oracle Purchasing uses this information to record information related to a complete document. The primary key is PO-HEADER_ID. RCV_TRANSACTIONS This table stores historical information about receiving transactions that you have performed. When you enter a receiving transaction and the receiving transaction processor processes your transaction, the transaction is recorded in this table. Once a row has been inserted into this table, it will never be updated. When you correct a transaction, the net transaction quantity is maintained in RCV_SUPPLY. The original transaction does not get updated. You can only delete rows from this table using the Purge feature of Oracle Purchasing. The primary key is TRANSACTION_ID. PO_LINES_ALL PO_LINES_ALL stores current information about each purchase order line. You need one row for each line you attach to a document. Each row includes the line number, item number and category unit, price, tax information, and quantity ordered for the line. Oracle Purchasing uses this information to record and update item and price information for purchase orders, quotations, and RFQs. The primary key is PO_LINE_ID.
PO_VENDORS This table stores information about your suppliers. Oracle Purchasing uses this information to determine active suppliers. The primary key is VENDOR_ID. HR_EMPLOYEES HR_EMPLOYEES is a view that contains information about employees. You must have a row for each requestor, requisition preparer, approver, buyer, or receiver who uses Oracle Purchasing. The primary key is EMPLOYEE_ID (o). PO_VENDOR_SITES_ALL This table stores information about supplier sites. Oracle Purchasing uses this information to store supplier address information. The primary key is VENDOR_SITE_ID. PO_VENDOR_CONTACTS This table stores information about supplier site contacts. The primary key is VENDOR_CONTACT_ID.
PO_REQUISITION_HEADERS_ALL PO_REQUISITION_HEADERS_ALL stores information about requisition headers. Each row contains the requisition number, preparer status, and description. It is one of three tables that stores requisition information. The primary key is REQUISITION_HEADER_ID. HR_EMPLOYEES HR_EMPLOYEES is a view that contains information about employees. You must have a row for each requestor, requisition preparer, approver, buyer, or receiver who uses Oracle Purchasing. The primary key is EMPLOYEE_ID (o). PO_REQUISITION_LINES_ALL This table stores information about requisition lines. Each row contains the line number, item number, item category, item description, need-by date, deliver-to location, item quantities, units, prices, requestor, notes, and suggested supplier information for the requisition line. This table is one of three tables that stores requisition information. The primary key is REQUISITION_LINE_ID. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID. PO_REQ_DISTRIBUTIONS_ALL PO_REQ_DISTRIBUTIONS_ALL stores information about the accounting distributions associated with each requisition line. Each requisition line must have at least one accounting distribution. Each row includes the Accounting Flexfield ID and requisition line quantity. This table is one of three tables that stores requisition information. The primary key is DISTRIBUTION_ID. GL_CODE_COMBINATIONS This table stores valid Accounting Flexfield segment value combinations for each accounting flexfield structure within your general ledger application. GL_CODE_COMBINATIONS is populated by the system when a new accounting flexfield combination is used, either through dynamic insertion or manually. This table references the CODE_COMBINATION_ID, which is the foreign key used throughout Oracle Applications when tracking an accounting flexfield combination. The primary key is CODE_COMBINATION_ID.
PO_HEADERS_ALL PO_HEADERS_ALL contains information for your purchasing documents. Each row contains buyer information, supplier information, notes, foreign currency information, terms and conditions information, and the document status. Oracle Purchasing uses this information to record information related to a complete document. The primary key is PO-HEADER_ID. PO_LINES_ALL PO_LINES_ALL stores current information about each purchase order line. You need one row for each line you attach to a document. Each row includes the line number, item number and category unit, price, tax information, and quantity ordered for the line. Oracle Purchasing uses this information to record and update item and price information for purchase orders, quotations, and RFQs. The primary key is PO_LINE_ID. PO_LINE_LOCATIONS_ALL This table contains information about purchase order shipment schedules and blanket agreement price breaks. You must have one row for each schedule or price break you attach to a document line. Each row contains the location, quantity, and dates for each shipment schedule. Oracle Purchasing uses this information to record delivery schedule information for purchase orders and price break information for blanket purchase orders, quotations, and RFQs. The primary key is LINE_LOCATION_ID. PO_DISTRIBUTIONS_ALL PO_DISTRIBUTIONS_ALL contains accounting information for a purchase order shipment line. Oracle Purchasing uses this information to record accounting and requisition information for purchase orders and releases. It is one of five tables that stores purchase orders and releases. The primary key is PO_DISTRIBUTION_ID. PO_RELEASES_ALL This table contains information about blanket and planned purchase order releases. You need one row for each release you issue for a blanket or planned purchase order. Each row includes the buyer, date, release status, and release number. Each release must have at least one purchase order shipment (PO_LINE_LOCATIONS_ALL). The primary key is PO_RELEASE_ID.
RCV_SHIPMENT_HEADERS This table stores common information about the source of your receipts or expected receipts. You group your receipts by the source type and the source of the receipt. Oracle Purchasing does not allow you to group receipts from different sources under one receipt header. The primary key is SHIPMENT_HEADER_ID. RCV_SHIPMENT_LINES This table stores information about items that have been shipped or received from a specific receipt source. It also stores information about the default destination for in-transit shipments. The primary key is SHIPMENT_LINE_ID. PO_LINE_LOCATIONS_ALL This table contains information about purchase order shipment schedules and blanket agreement price breaks. You must have one row for each schedule or price break you attach to a document line. Each row contains the location, quantity, and dates for each shipment schedule. Oracle Purchasing uses this information to record delivery schedule information for purchase orders, and price break information for blanket purchase orders, quotations, and RFQs. The primary key is LINE_LOCATION_ID. RCV_TRANSACTIONS This table stores historical information about receiving transactions you have performed. Once a row is inserted into this table, it will never be updated. When you correct a transaction, the net transaction quantity is maintained in RCV_SUPPLY. The original transaction quantity is not updated. You can delete rows from this table using the purge feature of Oracle Purchasing. The primary code is TRANSACTION_ID. MTL_MATERIAL_TRANSACTIONS MTL_MATERIAL_TRANSACTIONS stores a record of every material transaction or cost update performed in Oracle Inventory. Records are inserted into this table either through the transaction processor or by the standard cost update program. The primary key is TRANSACTION_ID. MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID. PO_DISTRIBUTIONS_ALL PO_DISTRIBUTIONS_ALL contains accounting information for a purchase order shipment line. Oracle Purchasing uses this information to record accounting and requisition information for purchase orders and releases. It is one of five tables that stores purchase orders and releases. The primary key is PO_DISTRIBUTION_ID. RCV_SUPPLY This table stores information about on-hand quantities in receiving and inspection. Oracle Purchasing uses the table to track item, quantity, location and source information for each receiving transaction. The primary key is SUPPLY_TYPE_CODE, SUPPLY_SOURCE_ID.
ICX Database Diagrams This slide shows the relationship between an item and price lists. Each supplier with items in the Unified Catalog will have a global price list (buyer id -2) for prices that are visible to everyone. If a price list is set up that is specific to an operating unit, this will be set up as another list against the same supplier. The Oracle Item Subtable holds information that links the item back to core applications - template Ids, contract Ids and so on. It’s done as a subtable to minimize impact on the main item table. The item itself is split into ‘universal’ attributes and those that need language translation. Oracle development has maintained consistency with core applicationss in using _TL translation tables and _VL translation views. More detailed information is available from the Oracle Self-Service Purchasing Technical Reference Manual.
Item - Category Structure This slide shows the simplistic relationship between items and categories.
Descriptors Note: Category key ‘0’ is the root category for base descriptors . Each category has descriptors associated with it. If the descriptors are base descriptors, they are associated with the root category. It is absolutely CRITICAL to not delete this entry! Although it is not visible/removable through the front-end user interface, using sql*plus it is all too easy to forget.
Category Mapping Categories must map to core Oracle applications to be usable within iProcurement. Although you can create items and categories within the unified Catalog, you cannot add an item to a shopping cart until the category of that item has been mapped. Core applications categories are automatically mapped, as the extractor knows which entry in mtl_categories to map to. Categories created directly into the Unified Catalog, bypassing core apps, must be mapped back manually using the Special Order Mapping screen in eContent manager
Local Descriptors Local descriptors (ie.specific to a category) are not held on the item tables. instead, a table is created using the category ID, with columns which represent the descriptor Ids. For example, Category ‘Pens’, with an ID of 100, has two local descriptors ‘Style’ (ID 998) and colour (ID 999). This creates a table ICX_POR_C100_TL, with columns A998 and A999.
Error Tracking Because the Catalog load process was lifted from exchange, it does not integrate with the concurrent managers. Instead, job requests are written to the batch jobs table above, and error messages are written to the two tables shown. Each descriptor for a failed item gets a row in the failed lines table, so deciding exactly what the failing value(s) were is not straightforward. You can also view rejected lines in eContent Manager, but if there is more than one failure reason for a given item, you get the message ‘Multiple errors’.
MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID. WIP_ENTITIES WIP_ENTITIES stores information about each discrete job or repetitive assembly. Each row includes a unique discrete job or repetitive assembly name, entity type, and the assembly built by the job or by the repetitive assembly. The primary key is WIP_ENTITY_ID. WIP_REPETITIVE_ITEMS WIP_REPETITIVE_ITEMS stores your repetitive assemblies and the production lines on which you build each assembly. Each row represents a particular assembly/line combination. The primary key is WIP_ENTITY_ID, LINE_ID. WIP_REPETITIVE_SCHEDULES WIP_REPETITIVE_SCHEDULES stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID. WIP_DISCRETE_JOBS WIP_DISCRETE_JOBS stores information about discrete jobs. Each row represents a discrete job. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID. WIP_OPERATIONS WIP_OPERATIONS stores information about the operations for your discrete jobs and repetitive schedules. Oracle Work in Process uses this information to control and monitor your assembly production on the shop floor. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_FLOW_SCHEDULES WIP_FLOW_SCHEDULES stores Work Order-less Flow schedule information. Each row represents a Flow schedule and contains information about the assembly being built. The primary key is WIP_ENTITY_ID. Instructor Note The full definition and explanation of Flow Schedules will be available when that product has been added to this course.
WIP_REQUIREMENT_OPERATIONS WIP_REQUIREMENT_OPERATIONS stores information about the material requirements for jobs or schedules. Oracle Work in Process uses this information to track the material used in a job or schedule. The primary key is INVENTORY_ITEM_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_REPETITIVE_SCHEDULES WIP_REPETITIVE_SCHEDULES stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID. WIP_OPERATIONS WIP_OPERATIONS stores information about the operations for your discrete jobs and repetitive schedules. Oracle Work in Process uses this information to control and monitor your assembly production on the shop floor. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID. MTL_ITEM_LOCATIONS MTL_ITEM_LOCATIONS is the definition table for stock locators. The associated attributes describe which subinventory this locator belongs to, what the locator physical capacity is, etc. The primary key is INVENTORY_LOCATION_ID, ORGANIZATION_ID. WIP_OPERATION_RESOURCES WIP_OPERATION_RESOURCES stores information about the resources associated with an operation for a job or a repetitive schedule. Oracle Work in Process uses this information to schedule jobs and repetitive schedules, and to charge resources to jobs and schedules. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_DISCRETE_JOBS WIP_DISCRETE_JOBS stores information about discrete jobs. Each row represents a discrete job. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID. WIP_SHOP_FLOOR_STATUSES This table stores the status codes that you assign to a discrete job or repetitive schedule. Each row contains the operation sequence number and intraoperation step to which you assign the status. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, SHOP_FLOOR_STATUS_CODE, LINE_ID, INTRAOPERATION_STEP_TYPE.
WIP_DISCRETE_JOBS WIP_DISCRETE_JOBS stores information about discrete jobs. Each row represents a discrete job. It also contains the information about the assembly being built, the revision of the assembly, the job quantity, the job status, accounting information, and job schedule dates. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID. WIP_OPERATIONS WIP_OPERATIONS stores information about the operations for your discrete jobs and repetitive schedules. Oracle Work in Process uses this information to control and monitor your assembly production on the shop floor. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_REQUIREMENT_OPERATIONS WIP_REQUIREMENT_OPERATIONS stores information about the material requirements for jobs or schedules. Oracle Work in Process uses this information to track the material used in a job or schedule. The primary key is INVENTORY_ITEM_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_OPERATION_RESOURCES WIP_OPERATION_RESOURCES stores information about the resources associated with an operation for a job or a repetitive schedule. Oracle Work in Process uses this information to schedule jobs and repetitive schedules, and to charge resources to jobs and schedules. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_WORK_ORDER_INTERFACE WIP_WORK_ORDER_INTERFACE enables you to import Discrete job and Repetitive schedule header information, and Discrete job operations, material, resource, and scheduling information from any source, using a single process. There is no primary key associated with this interface. WIP_ACCOUNTING_CLASSES This table stores accounting flexfield information for standard discrete jobs, nonstandard asset jobs, nonstandard expense jobs, and repetitive assemblies. Oracle Work in Process stores a general ledger account for each cost element associated with a class. The CLASS_CODE column uniquely identifies each class. Oracle Work in Process uses this information to create the journal entries that post cost transactions. The primary key is CLASS_CODE, ORGANIZATION_ID. MTL_SYSTEM_ITEMS_B This is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. Each item is initially defined in an item master organization. Then you assign the item to other organizations that need to recognize this item. A row is inserted for each new organization to which the item is assigned. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID.
WIP_REPETITIVE_ITEMS WIP_REPETITIVE_ITEMS stores your repetitive assemblies and the production lines on which you build each assembly. Each row represents a particular assembly/line combination and includes information such as the line priority, the accounting class associated with the line, the line speed, the line’s supply type, if the line is used in calculating the assembly’s lead time, the completion subinventory and locator for a line, and the alternate bill and routing you use for a particular line. Oracle Work in Process uses this information when you define repetitive schedules. Oracle Master Schedule/MRP and Oracle Capacity use this information when mass loading repetitive schedules and running capacity loads on repetitive schedules. The primary key is WIP_ENTITY_ID, LINE_ID. WIP_REPETITIVE_SCHEDULES WIP_REPETITIVE_SCHEDULES stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID. WIP_OPERATIONS WIP_OPERATIONS stores information about the operations for your discrete jobs and repetitive schedules. Each row represents a specific operation and includes an operation sequence number to order the operations for a job or repetitive schedule. Oracle Work in Process uses this information to control and monitor your assembly production on the shop floor. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_REQUIREMENT_OPERATIONS WIP_REQUIREMENT_OPERATIONS stores information about the material requirements for jobs or schedules. Oracle Work in Process uses this information to track the material used in a job or schedule. The primary key is INVENTORY_ITEM_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_OPERATION_RESOURCES WIP_OPERATION_RESOURCES stores information about the resources associated with an operation for a job or a repetitive schedule. Oracle Work in Process uses this information to schedule jobs and repetitive schedules, and to charge resources to jobs and schedules. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_ACCOUNTING_CLASSES This table stores accounting flexfield information for standard discrete jobs, nonstandard asset jobs, nonstandard expense jobs, and repetitive assemblies. Oracle Work in Process stores a general ledger account for each cost element associated with a class. The CLASS_CODE column uniquely identifies each class. Oracle Work in Process uses this information to create the journal entries that post cost transactions. The primary key is CLASS_CODE, ORAGANIZATION_ID. MTL_SYSTEM_ITEMS_B This is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. Each item is initially defined in an item master organization. Then you assign the item to other organizations that need to recognize this item. A row is inserted for each new organization to which the item is assigned. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID.
MTL_MATERIAL_TXN_ALLOCATIONS This table stores the repetitive schedules charged by a material transaction. Each row contains the quantity transacted to each schedule for a given transaction. Oracle Work in Process uses this information to report changes to individual schedules for multischedule material transactions. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID. MTL_TRANSACTION_ACCOUNTS This table holds the accounting information for each material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information to track the financial impact of quantity moves. (There is no primary key for this table.) MTL_MATERIAL_TRANSACTIONS This table stores a record of every material transaction, including issues and returns of component items in Work in Process. Records are inserted into this table through the transaction processor. The primary key is TRANSACTION_ID. WIP_REQUIREMENT_OPERATIONS This table stores information about the material requirements for jobs or schedules. Oracle Work in Process uses this information to track the material used in a job or schedule. The primary key is INVENTORY_ITEM_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_OPERATIONS WIP_OPERATIONS stores information about the operations of your discrete jobs and repetitive schedules. Each row represents a specific operation and includes an operation sequence number to order the operations for a job or repetitive schedule. Oracle Work in Process uses this information to control and monitor your assembly production on the shop floor. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_REPETITIVE_SCHEDULES This table stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID. WIP_DISCRETE_JOBS This table stores information about discrete jobs. Each row represents a discrete job. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID.
WIP_DISCRETE_JOBS WIP_DISCRETE_JOBS stores information about discrete jobs. Each row represents a discrete job. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID. WIP_REPETITIVE_SCHEDULES WIP_REPETITIVE_SCHEDULES stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID. MTL_MATERIAL_TRANSACTIONS This table stores a record of every material transaction, including issues and returns of component items in Work in Process. Records are inserted into this table through the transaction processor. The primary key is TRANSACTION_ID. WIP_OPERATIONS WIP_OPERATIONS stores information about the operations for your discrete jobs and repetitive schedules. Each row represents a specific operation and includes an operation sequence number to order the operations for a job or repetitive schedule. Oracle Work in Process uses this information to control and monitor your assembly production on the shop floor. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_OPERATION_RESOURCES WIP_OPERATION_RESOURCES stores information about the resources associated with an operation for a job or a repetitive schedule. Oracle Work in Process uses this information to schedule jobs and repetitive schedules, and to charge resources to jobs and schedules. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_MOVE_TXN_ALLOCATIONS This table stores Move quantity information for single shop floor Move transactions that transcend multiple repetitive schedules. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID. WIP_TXN_ALLOCATIONS WIP_TXN_ALLOCATIONS stores resource information for single resource cost transactions that transcend multiple repetitive schedules. Oracle Work in Process allocates resource charges to repetitive schedules based on a FIFO algorithm. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID. WIP_TRANSACTIONS This table stores information about each resource transaction in Oracle Work in Process. Oracle Work in Process uses this information to track resources and to calculate values stored in WIP_TRANSACTION_ACCOUNTS. The primary key is TRANSACTION_ID. WIP_MOVE_TRANSACTIONS WIP_MOVE_TRANSACTIONS stores information about shop floor move transactions. Each row represents a single move transaction and includes a unique transaction ID, a transaction date, the job or repetitive schedule in which the move occurs, the quantity moved, the from and to operation sequence numbers, operation codes, and intraoperation steps. Oracle Work in Process uses this information to track move transactions. The primary key is TRANSACTION_ID.
WIP_DISCRETE_JOBS WIP_DISCRETE_JOBS stores information about discrete jobs. Each row represents a discrete job. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID. WIP_REPETITIVE_SCHEDULES WIP_REPETITIVE_SCHEDULES stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID. WIP_OPERATIONS WIP_OPERATIONS stores information about the operations for your discrete jobs and repetitive schedules. Each row represents a specific operation and includes an operation sequence number to order the operations for a job or repetitive schedule. Oracle Work in Process uses this information to control and monitor your assembly production on the shop floor. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_OPERATION_RESOURCES WIP_OPERATION_RESOURCES stores information about the resources associated with an operation for a job or a repetitive schedule. Oracle Work in Process uses this information to schedule jobs and repetitive schedules, and to charge resources to jobs and schedules. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, REPETITIVE_SCHEDULE_ID (o). WIP_TRANSACTIONS WIP_TRANSACTIONS stores information about each resource transaction in Oracle Work in Process. Oracle Work in Process uses this information to track resources and to calculate values stored in WIP_TRANSACTION_ACCOUNTS. The primary key is TRANSACTION_ID. WIP_COST_TXN_INTERFACE WIP_COST_TXN_INTERFACE contains information about cost transactions that Oracle Work in Process needs to process. Oracle Work in Process uses this table to support all resource cost transactions, including transactions you process from other systems. The primary key is TRANSACTION_ID (o). WIP_TRANSACTION_ACCOUNTS WIP_TRANSACTION_ACCOUNTS holds the accounting information for each resource transaction in WIP_TRANSACTIONS. These tables are joined by the TRANSACTION_ID column, and there are at least two rows (debit and credit) for each transaction of a costed resource. Oracle Work in Process uses this information to track the financial impact of resource transactions. There is no primary key. WIP_TXN_ALLOCATIONS WIP_TXN_ALLOCATIONS stores resource information for single resource cost transactions that transcend multiple repetitive schedules. Oracle Work in Process allocates resource charges to repetitive schedules based on a FIFO algorithm. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID. WIP_OPERATION_RESOURCE_USAGE WIP_OPERATION_RESOURCE_USAGE stores information about the use of resources associated with job and schedule operations. Each row represents a resource usage in a valid shift for that particular resource. There is no primary key. WIP_OPERATION_OVERHEADS WIP_OPERATION_OVERHEADS stores information about resource-based and departmental overhead costs for jobs in an average costing organization. The primary key is WIP_ENTITY_ID, OPERATION_SEQ_NUM, OVERHEAD_ID, RESOURCE_SEQ_NUM, BASIS_TYPE.
WIP_DISCRETE_JOBS WIP_DISCRETE_JOBS stores information about discrete jobs. Each row represents a discrete job. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID. WIP_REPETITIVE_SCHEDULES WIP_REPETITIVE_SCHEDULES stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID. MTL_MATERIAL_TRANSACTIONS_TEMP MTL_MATERIAL_TRANSACTIONS_TEMP is the gateway for all material transactions. Transfer records are stored in this table as a single record. The primary key is TRANSACTION_HEADER_ID (o). MTL_MATERIAL_TRANSACTIONS MTL_MATERIAL_TRANSACTIONS stores a record of every material transaction or cost update performed in Oracle Inventory. Records are inserted into this table either through the transaction processor or by the standard cost update program. The primary key is TRANSACTION_ID. MTL_TRANSACTION_ACCOUNTS MTL_TRANSACTION_ACCOUNTS holds the accounting information for each material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information to track the financial impact of quantity moves. There is no primary key for this table. MTL_MATERIAL_TXN_ALLOCATIONS MTL_MATERIAL_TXN_ALLOCATIONS stores the repetitive schedules charged by a material transaction. Each row contains the quantity transacted to each schedule for a given transaction. Oracle Work in Process uses this information to report changes to individual schedules for multischedule material transactions. the Primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID. WIP_FLOW_SCHEDULES WIP_FLOW_SCHEDULES stores Work Order-less Flow schedule information. Each row represents a Flow schedule and contains information about the assembly being built. The primary key is WIP_ENTITY_ID Instructor Note The full definition and explanation of Flow Schedules will be available when that product has been added to this course.
WIP_FLOW_SCHEDULES WIP_FLOW_SCHEDULES stores Work Order-less Flow schedule information. Each row represents a Flow schedule. Oracle Work in Process uses this information to control Flow schedule production. The primary key is WIP_ENTITY_ID. MTL_TRANSACTIONS_INTERFACE MTL_TRANSACTION_INTERFACE is the interface point between non Oracle Inventory applications and the Oracle Inventory transaction module. Transaction Manager concurrent program polls this table at a user specified process interval, and submits the Transaction Workers to process them. There is no primary key for this table. MTL_MATERIAL_TRANSACTIONS MTL_MATERIAL_TRANSACTIONS stores a record of every material transaction or cost update performed in Oracle Inventory. Records are inserted into this table either through the transaction processor or by the standard cost update program. The primary key is TRANSACTION_ID. MTL_MATERIAL_TRANSACTIONS_TEMP MTL_MATERIAL_TRANSACTIONS_TEMP is the gateway for all material transactions. Transfer records are stored in this table as a single record. The primary key is TRANSACTION_HEADER_ID. BOM_BILL_OF_MATERIAS BOM_BILL_OF_MATERIALS stores information about manufacturing and engineering bills of material. Each row in this table represents a unique manufacturing or engineering bill. The primary key is BILL_SEQUENCE_ID. BOM_OPERATIONAL_ROUTINGS BOM_OPERATIONAL_ROUTINGS stores information about manufacturing and engineering routings. The primary key is ROUTING_SEQUENCE_ID. WIP_PERIOD_BALANCES WIP_PERIOD_BALANCES stores summary accounting information for jobs and schedules. Each row represents job or schedule charges within a given accounting period, and contains the summary values for each cost element. The primary key is ACCT_PERIOD_ID, WIP_ENTITY_ID. WIP_TRANSACTIONS WIP_TRANSACTIONS stores information about each resource transaction in Oracle Work in Process. Oracle Work in Process uses this information to track resources and to calculate values stored in WIP_TRANSACTION_ACCOUNTS. The primary key is TRANSACTION_ID. WIP_ENTITIES WIP_ENTITIES stores information about jobs, repetitive assemblies, and flow schedules. Each row includes a unique entity name, the entity type, and the assembly being built. The primary key is WIP_ENTITY_ID.
RA_CUST_TRX_TYPES_ALL A/R Transactions (Invoice/Credit Memo) RA_BATCH_SOURCES_ALL OE_TRANSACTION_TYPES_ALL R11i: New table for Order Type: Set at Hdr and Line. Line Points to Hdr OE_CREDIT_CHECK_RULES (Same as R11) OE_WORKFLOW_ASSIGNMENTS R11i: Replaces Order Cycles OE_HEADERS_ALL / OE_LINES_ALL New in R11i: Order Type at Header and Line.
NOTES: BOM_INVENTORY_COMPONENTS (For Models & Options) MTL_CROSS REFRENCE_TYPES / MTL_CROSS_REFERENCES New R11i OM Feature: Can use Inventory Cross Reference feature in Order Entry. OE Lines keep bothCross Refernce values and Item ID. See columns “ Item_Idnetifier_Type ” and “ Ordered_Item ” MTL_CUSTOMER_ITEMS / MTL_CUSTOMER_ITEMS_XREF “ Ordered_Item_ID ” points ot Mtl_Customer_Items “ Customer_Item_ID ”
Price List Header & Lines have extensive new options in R11i Agreement works as before, is assigned to a price list. Can now create qualifier (ex: cust= “ acme ” ) and assign to price list or line. Lines are assigned ‘ phase ’ for pricing to trigger: “ Book ” , “ Ship ” , etc Pricing Attributes: ??? New Price Feature: Coupon. Earn benefit with first order, apply to next order. New price Feature: Upgrade Item (pay for 10oz bottle, get 16oz instead) Price Formulas is a new feature in R11i, advanced pricing only. Dtls: ???
Courseware ERD Formatting Objective Follow the visual standards used in the TRM as close as possible, given the reproduction medium to be used. Courseware ERD Formatting Standards 1. Use the symbols, typefaces, line weights, and font sizes in this document. 2. Allow fills for table symbols where that makes the ERD easier to understand; do not use graduated fills at all. 3. Allow colors for fills or background when displaying onscreen, if that makes the ERD easier to understand. 4. Following the TRM standard, all “ pig ’ s-ears ” are shown with either dotted lines or solid lines, but not shown with half dotted and half solid. This is a compromise necessitated by Powerpoint. 5. Omit the descriptive text alongside the relationship lines.
