52583714 Mfg Fundamentals ERDs1

Oracle Order EntryApplication Object Library
Oracle Application Object Library:
Inventory Database
MTL_PARAMETERS
MTL_MATERIAL
TRANSACTIONS
MTL_SYSTEM_ITEMS_B
HR_ORGANIZATION_UNITS
MTL_ONHAND_QUANTITIES
MTL_SYSTEM_ITEMS_TL
MTL_TRANSACTION
ACCOUNTS
Org
Item
Trans
O/H
Oracle Inventory: Organizations
GL_CODE_
COMBINATIONS
GL_SETS_OF_BOOKS
MTL_INTERORG_
PARAMETERS
HR_ALL_ORGANIZATION_UNITS
HR_ORGANIZATION_
INFORMATION
MTL_PARAMETERS
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 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.
Copyright Ó Oracle Corporation, 2001. All rights reserved.
Oracle Inventory: Organizations
From
To
MTL_PARAMETERS
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.
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.
Oracle Inventory:
MTL_SECONDARY_LOCATORS
MTL_ITEM_LOCATIONS
MTL_ITEM_SUB_INVENTORIES
MTL_SECONDARY_INVENTORIES
MTL_SYSTEM_ITEMS_B
MTL_PARAMETERS
MTL_SYSTEM_ITEMS_TL
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.
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
Oracle Inventory:
Oracle Inventory: Item Master
MTL_ITEM_ATTRIBUTES
MTL_SYSTEM_ITEMS_B
MTL_ITEM_STATUS
MTL_ITEM_TEMPLATES
MTL_ITEM_TEMPL_ATTRIBUTES
MTL_PARAMETERS
MTL_STATUS_ATTRIBUTE_VALUES
MTL_SYSTEM_ITEMS_B
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 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
Oracle Inventory Item Status
MTL_ITEM_ATTRIBUTES
MTL_ITEM_STATUS
MTL_SYSTEM_ITEMS_B
MTL_PENDING_ITEM_STATUS
MTL_SYSTEM_ITEMS_B
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
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.
Oracle Inventory:
Oracle Inventory Item Controls
MTL_SYSTEM_ITEMS_B
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
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.
Oracle Inventory: Item Categories
MTL_SYSTEM_ITEMS_B
FND_ID_FLEX_STRUCTURES
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.
Oracle Inventory: ABC Analysis
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.
Oracle Inventory: Item Catalogs
MTL_DESCRIPTIVE_ELEMENTS
MTL_DESCR_ELEMENT_VALUES
MTL_ITEM_CATALOG_GROUPS
MTL_SYSTEM_ITEMS_B
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 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 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
Oracle Inventory: Item Catalogs
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 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 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
BOM and Engineering
Oracle Bills of Material/Engineering
Bills of Material Structures
BOM_BILL_OF_
MATERIALS
MTL_
SYSTEM_
ITEMS_B
MTL_
ITEM_
LOCATIONS
BOM_
OPERATION_
SEQUENCES
BOM_ALTERNATE_
DESIGNATORS
MTL_
SECONDARY_
INVENTORIES
PRIMARY
BILL
ALTERNATE
BILL
MTL_
ITEM_
REVISIONS
BOM_
INVENTORY_
COMPONENTS
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_ALTERNATE_DESIGNATORS
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 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 BOM: Bills of Material
BOM
OPERATION
SEQUENCES
BOM_BILL_OF_
MATERIALS
MTL_ITEM
REVISIONS
Oracle Inventory Entity Relationship Diagram
The major tables in Oracle Inventory are grouped by business function.
Organizations
MTL_PARAMETERS
GL_SETS_OF_BOOKS
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.
Routings
BOM_
OPERATIONAL_
ROUTINGS
MTL_
SYSTEM_
ITEMS_B
BOM_
OPERATION_
SEQUENCES
PRIMARY
ROUTING
ALTERNATE
ROUTING
BOM_ALTERNATE_
DESIGNATIONS
BOM_
RESOURCES
BOM_
OPERATION_
RESOURCES
MTL_RTG_
ITEM_
REVISIONS
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_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
Oracle BOM: Routings
Oracle Inventory Entity Relationship Diagram
The major tables in Oracle Inventory are grouped by business function.
Organizations
MTL_PARAMETERS
GL_SETS_OF_BOOKS
Oracle BOM/Engineering Change Control
ENG_CURRENT_
SCHEDULED_DATES
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
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
Cost Management
Cost Types: Std Avg, FIFO, LIFO
CST_LAYER_
COST_DETAILS
CST_ACTIVITIES
BOM_
RESOURCES
CST_COST_
ELEMENTS
CST_QUANTITY_LAYERS
CST_ITEM_COSTS
MTL_SYSTEM_ITEMS_B
CST_COST_TYPES
MTL_SYSTEM_ITEMS_B
CST_COST_TYPES
CST_COST_TYPES stores the cost type definition. Cost types represent sets of costs, frozen cost, or next year’s cost. The table is seeded with the following costs types:
Frozen: The organization uses the standard costing method.
Pending: For standard cost organizations, Pending charges to the frozen cost.
Average: The organization uses the average costing method.
FIFO: The organization uses the FIFO costing method.
LIFO: The organization uses the LIFO costing method.
You can define as many additional cost types as you want. The primary key is COST_TYPE_ID.
CST_ITEM_COSTS
CST_ITEM_COSTS stores the cost control information. The Define Item Cost 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
BOM_RESOURCES
Cost Type: Standard
MTL_SYSTEM_ITEMS_B
CST_COST_TYPES
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_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
BOM_RESOURCES
Cost Type: Avg, LIFO, FIFO
BOM_
RESOURCES
CST_COST_
ELEMENTS
CST_ITEM_COSTS
MTL_SYSTEM
ITEMS_B
CST_COST
TYPES
BOM_OPER
SEQUENCES
BOM
DEPARTMENTS
CST_LAYER_COST_DETAILS
MTL_SYSTEM_ITEMS_B
CST_COST_TYPES
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_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
BOM_RESOURCES
Oracle Cost Management
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:
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
Supply Chain Planning
Oracle Master Scheduling/MRP
MPS / MRP / SCP
MPS / MRP / SCP
MPS / MRP / SCP
Oracle Capacity
Oracle Capacity
Inventory Transactions
Oracle Inventory Transaction Flow
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.
Oracle Inventory:
MTL_UNIT_
TRANSACTIONS
MTL_SYSTEM_ITEMS_B
MTL_TRANSACTION_
LOT_NUMBERS
MTL_ITEM_
REVISIONS
MTL_SERIAL_
NUMBERS
MTL_LOT_NUMBERS
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_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
Oracle Inventory: Physical Inventory
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 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
Oracle Inventory: Cycle Count
MTL_SYSTEM_ITEMS_B
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 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.
Purchasing
Oracle Purchasing: Entity Relationships
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.
Suppliers
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
HR_EMPLOYEES
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.
Oracle Purchasing: Requisitions
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.
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.
Oracle Purchasing: Purchasing Documents
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.
Receiving
MTL_MATERIAL_
TRANSACTIONS
RCV_SHIPMENT_
HEADERS
MTL_SYSTEM_
ITEMS_B
RCV_SHIPMENT_
LINES
RCV_
TRANSACTIONS
RCV_SUPPLY
PO_
DISTRIBUTIONS_ALL
PO_LINE_
LOCATIONS_ALL
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 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
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.
iProcurement
Catalog Database Structure
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.
Category Database Structure
This slide shows the simplistic relationship between items and categories.
Descriptors Database Structure
ICX_POR_CATEGORIES
ICX_POR_CATEGORIES_TL
ICX_POR_CATEGORIES_VL
ICX_POR_DESCRIPTORS
ICX_POR_DESCRIPTORS_TL
ICX_POR_DESCRIPTORS_VL
New
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 Database Structure
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 Database Structure
Annnnnnn where nnnnnn=RT_DESCRIPTOR_ID
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 Database Structure
New
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’.
Work in Process
Oracle Work in Process Overview
MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
WIP_DISCRETE_
JOBS
WIP_FLOW_
SCHEDULES
WIP_REPETITIVE_
SCHEDULES
WIP_REPETITIVE_
ITEMS
MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
WIP_ENTITIES stores information about each discrete job or repetitive assembly. Each row includes a unique discrete job or repetitive assembly name, entity type, and the assembly built by the job or by the repetitive assembly. The primary key is WIP_ENTITY_ID.
WIP_REPETITIVE_ITEMS
WIP_REPETITIVE_ITEMS stores your repetitive assemblies and the production lines on which you build each assembly. Each row represents a particular assembly/line combination. The primary key is WIP_ENTITY_ID, LINE_ID.
WIP_REPETITIVE_SCHEDULES
WIP_REPETITIVE_SCHEDULES stores repetitive schedule information. Oracle Work in Process uses this information to control repetitive production. The primary key is REPETITIVE_SCHEDULE_ID.
WIP_DISCRETE_JOBS
WIP_DISCRETE_JOBS stores information about discrete jobs. Each row represents a discrete job. Oracle Work in Process uses this information to control discrete production. The primary key is WIP_ENTITY_ID.
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: DISCRETE JOB
WIP: REPETITIVE SCHEDULES
Oracle Work in Process Operations
MTL_
SYSTEM_
ITEMS_B
WIP_REQUIREMENT_OPERATIONS
WIP_
DISCRETE_JOBS
MTL_
ITEM_
LOCATIONS
WIP_
REPETITIVE_
SCHEDULES
WIP_
SHOP_FLOOR_
STATUSES
WIP_OPERATIONS
WIP_OPERATION_
RESOURCES
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_OPERATIONS
MTL_SYSTEM_ITEMS_B
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_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.
Oracle Work in Process: Discrete Jobs
WIP_
OPERATION_
RESOURCES
WIP_
DISCRETE_
JOBS
MTL_MATERIAL_
TRANSACTIONS
WIP_
ACCOUNTING_
CLASSES
WIP_WORK_
ORDER_
INTERFACE
WIP_OPERATIONS
MTL_SYSTEM_ITEMS_B
WIP_ENTITIES
WIP_
REQUIREMENT_
OPERATIONS
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_WORK_ORDER_INTERFACE
WIP_WORK_ORDER_INTERFACE enables you to import Discrete job and Repetitive schedule header information, and Discrete job operations, material, resource, and scheduling information from any source, using a single process. There is no primary key associated with this interface.
WIP_ACCOUNTING_CLASSES
This table stores accounting flexfield information for standard discrete jobs, nonstandard asset jobs, nonstandard expense jobs, and repetitive assemblies. Oracle Work in Process stores a general ledger account for each cost element associated with a class. The CLASS_CODE column uniquely identifies each class. Oracle Work in Process uses this information to create the journal entries that post cost transactions. The primary key is CLASS_CODE, ORGANIZATION_ID.
MTL_SYSTEM_ITEMS_B
This is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. Each item is initially defined in an item master organization. Then you assign the item to other organizations that need to recognize this item. A row is inserted for each new organization to which the item is assigned. The primary key is INVENTORY_ITEM_ID, ORGANIZATION_ID.
Oracle Work in Process: Repetitive Schedules
WIP_
REQUIREMENT_
OPERATIONS
WIP_
OPERATION_
RESOURCES
WIP_
ACCOUNTING_
CLASSES
WIP_
REPETITIVE_
SCHEDULES
WIP_OPERATIONS
MTL_SYSTEM_ITEMS_B
MTL_MATERIAL_
TRANSACTIONS
WIP_ENTITIES
WIP_
WORK_ORDER_
INTERFACE
WIP_REPETITIVE_ITEMS stores your repetitive assemblies and the production lines on which you build each assembly. Each row represents a particular assembly/line combination and includes information such as the line priority, the accounting class associated with the line, the line speed, the line’s supply type, if the line is used in calculating the assembly’s lead time, the completion subinventory and locator for a line, and the alternate bill and routing you use for a particular line. Oracle Work in Process uses this information when you define repetitive schedules. Oracle Master Schedule/MRP and Oracle Capacity use this information when mass loading repetitive schedules and running capacity loads on repetitive schedules. The primary key is WIP_ENTITY_ID, LINE_ID.
WIP_OPERATIONS
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_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.
Oracle WIP Material Transactions
MTL_MATERIAL_TXN_ALLOCATIONS
This table stores the repetitive schedules charged by a material transaction. Each row contains the quantity transacted to each schedule for a given transaction. Oracle Work in Process uses this information to report changes to individual schedules for multischedule material transactions. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID.
This table holds the accounting information for each material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information to track the financial impact of quantity moves. (There is no primary key for this table.)
This table stores a record of every material transaction, including issues and returns of component items in Work in Process. Records are inserted into this table through the transaction processor. The primary key is TRANSACTION_ID.
This table stores information about the material requirements for jobs or schedules. Oracle Work in Process uses this information to track the material used in a job or schedule. The primary key is INVENTORY_ITEM_ID, WIP_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).
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.
Oracle WIP: Move Transactions
WIP_DISCRETE_JOBS
This table stores a record of every material transaction, including issues and returns of component items in Work in Process. Records are inserted into this table through the transaction processor. The primary key is TRANSACTION_ID.
WIP_OPERATIONS
WIP_MOVE_TXN_ALLOCATIONS
This table stores Move quantity information for single shop floor Move transactions that transcend multiple repetitive schedules. The primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID.
WIP_TXN_ALLOCATIONS
WIP_TXN_ALLOCATIONS stores resource information for single resource cost transactions that transcend multiple repetitive schedules. Oracle Work in Process allocates resource charges to repetitive schedules based on a FIFO algorithm. The primary key is TRANSACTION_ID, 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.
Oracle WIP: Resource Transactions
WIP_DISCRETE_JOBS
WIP_OPERATIONS
WIP_TRANSACTIONS
WIP_TRANSACTIONS stores information about each resource transaction in Oracle Work in Process. Oracle Work in Process uses this information to track resources and to calculate values stored in WIP_TRANSACTION_ACCOUNTS. The primary key is TRANSACTION_ID.
WIP_COST_TXN_INTERFACE
WIP_COST_TXN_INTERFACE contains information about cost transactions that Oracle Work in Process needs to process. Oracle Work in Process uses this table to support all resource cost transactions, including transactions you process from other systems. The primary key is TRANSACTION_ID (o).
WIP_TRANSACTION_ACCOUNTS
WIP_TRANSACTION_ACCOUNTS holds the accounting information for each resource transaction in WIP_TRANSACTIONS. These tables are joined by the TRANSACTION_ID column, and there are at least two rows (debit and credit) for each transaction of a costed resource. Oracle Work in Process uses this information to track the financial impact of resource transactions. There is no primary key.
WIP_TXN_ALLOCATIONS
WIP_TXN_ALLOCATIONS stores resource information for single resource cost transactions that transcend multiple repetitive schedules. Oracle Work in Process allocates resource charges to repetitive schedules based on a FIFO algorithm. The primary key is TRANSACTION_ID, 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.
Oracle WIP: Completion Transactions
WIP_DISCRETE_JOBS
MTL_MATERIAL_TRANSACTIONS_TEMP is the gateway for all material transactions. Transfer records are stored in this table as a single record. The primary key is TRANSACTION_HEADER_ID (o).
MTL_TRANSACTION_ACCOUNTS holds the accounting information for each material transaction in MTL_MATERIAL_TRANSACTIONS. Oracle Inventory uses this information to track the financial impact of quantity moves. There is no primary key for this table.
MTL_MATERIAL_TXN_ALLOCATIONS
MTL_MATERIAL_TXN_ALLOCATIONS stores the repetitive schedules charged by a material transaction. Each row contains the quantity transacted to each schedule for a given transaction. Oracle Work in Process uses this information to report changes to individual schedules for multischedule material transactions. the Primary key is TRANSACTION_ID, REPETITIVE_SCHEDULE_ID, ORGANIZATION_ID.
WIP_FLOW_SCHEDULES
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.
Oracle WIP: Work Order-less Completions
WIP_PERIOD_
BALANCES
WIP_
TRANSACTIONS
WIP_
FLOW_
SCHEDULES
MTL_MATERIAL_
TRANSACTIONS
MTL_MATERIAL_
TRANSACTIONS_
TEMP
MTL_
TRANSACTIONS_
INTERFACE
WIP_ENTITIES
BOM_
BILL_OF_
MATERIALS
BOM_
OPERATIONAL_
ROUTINGS
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_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
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.
R11i Order Management
HZ / Customer Diagram
Oracle OM: Order Types
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)
Oracle OM: Orders & RMAs
Oracle OM: Items & Models
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
Oracle Inventory: Pricing
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: ???
Symbols
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.