Oracle Apps Inventory FAQs

Oracle Apps Inventory FAQs

Where do we set Inventory Organization for a particular responsibility??

Through Organizational Access Form

Transaction Source Type:

Item:

Items is a part or service you:

<!--[if !supportLists]-->o        <!--[endif]-->Purchase

<!--[if !supportLists]-->o        <!--[endif]-->Sell

<!--[if !supportLists]-->o        <!--[endif]-->Plan

<!--[if !supportLists]-->o        <!--[endif]-->Manufacture

<!--[if !supportLists]-->o        <!--[endif]-->Stock

<!--[if !supportLists]-->o        <!--[endif]-->Distribute

<!--[if !supportLists]-->o        <!--[endif]-->Prototype

The following Modules use items:

Item Statuses and Item Attributes:

Status attributes are item attributes that enable key functionality for each item. An item status is defined by selecting the value check boxes for the status attributes.  Both status attributes and item status can be controlled at the item level or organization levels.

Item Statuses are:

<!--[if !supportLists]-->Ø       <!--[endif]-->BOM Allowed

<!--[if !supportLists]-->Ø       <!--[endif]-->Build in WIP

<!--[if !supportLists]-->Ø       <!--[endif]-->Customer Orders Enabled

<!--[if !supportLists]-->Ø       <!--[endif]-->Internal Orders Enabled

<!--[if !supportLists]-->Ø       <!--[endif]-->Invoice Enabled

<!--[if !supportLists]-->Ø       <!--[endif]-->Transactable

<!--[if !supportLists]-->Ø       <!--[endif]-->Purchasable

<!--[if !supportLists]-->Ø       <!--[endif]-->Stackable

<!--[if !vml]--><!--[endif]-->

Item Attributes

Item attributes are the collection of information about an item.

Stackable, Receivable, Financing Allowed, Purchased, Shippable, Returnable, Costing Enabled,

Transact able, BOM Allowed, Build in WIP, Purchasable, Customer Orders Enabled, Internal Orders Enabled, Invoice Enabled, Inventory Item, Revision Control, Lot Control, Locator Control

Receipt Required, List Price.

Categories and Category Sets

Categories are logical groupings of items that have similar characteristics. 

A category set is a distinct category grouping scheme and consists of categories.

Some application modules, Inventory, for example require that all items are assigned to a category.  The user specifies a default category for this purpose in each of these modules. Categories and category sets are used to group items for various reports and programs.

Item Categories - Setup

<!--[if !supportLists]-->Ø       <!--[endif]-->Define the Flexfield structures for the item categories Flexfield.

<!--[if !supportLists]-->Ø       <!--[endif]-->Define categories.

<!--[if !supportLists]-->Ø       <!--[endif]-->Define category sets and assign the categories to the sets.  Each set can use a different Flexfield definition if required.

<!--[if !supportLists]-->Ø       <!--[endif]-->Assign default category sets to each functional area, like Purchasing, Planning and Inventory

<!--[if !supportLists]-->Ø       <!--[endif]-->Assign items to categories.  An item can be assigned to only one category within a set.

Item Cataloging

<!--[if !supportLists]-->Ø       <!--[endif]-->Item cataloging is used to add descriptive information to items and to partition the Item Master into groups of items that share common characteristics. The characteristic required to uniquely define an item in each group is configured in advance. While defining items, these characteristics are assigned to an item catalog group.

<!--[if !supportLists]-->Ø       <!--[endif]--> While the catalog group Flexfield is a required setup, item cataloging is optional.

<!--[if !supportLists]-->Ø       <!--[endif]-->To define a catalog, as many distinct item catalog groups as needed can be defined. Each group has unique characteristics (called descriptive elements) that completely describe items belonging to the group.

<!--[if !supportLists]-->Ø       <!--[endif]-->When assigning an item to an item catalog group, values for the descriptive elements that apply to the item are defined. For example, an item catalog group called Computer could have a descriptive element called Processing Speed. Possible values for Processing Speed might be 100MHZ, 133MHZ, and so on.

Transaction

<!--[if !supportLists]-->Ø       <!--[endif]-->A transaction is an item movement into, within, or out of inventory. A transaction changes the quantity, location, or cost of an item. Inventory supports a number of predefined and user-defined transaction types.

<!--[if !supportLists]-->Ø       <!--[endif]-->Every material movement has a corresponding set of accounting transactions that Oracle Inventory automatically generates.

<!--[if !supportLists]-->Ø       <!--[endif]-->All transactions validate the various controls (revision, locator, lot number, and serial number) enabled for items.

Inventory Organization

<!--[if !supportLists]-->Ø       <!--[endif]-->An inventory organization can be a physical entity like a warehouse where inventory is stored and transacted.

<!--[if !supportLists]-->Ø       <!--[endif]-->An inventory organization can be a logical entity like an item master organization which only holds items with no transactions An inventory organization can have its own location with a set of books, a costing method, a workday calendar, and a list of  items.

<!--[if !supportLists]-->Ø       <!--[endif]-->An inventory organization can share one or more of these characteristics with other organizations.

<!--[if !supportLists]-->Ø       <!--[endif]-->An inventory organization is an inventory location with its own set of books, costing method, workday calendar and list of items.  An organization can be a company, subsidiary, or warehouse.

Consider the following when you plan your enterprise structure:

<!--[if !supportLists]-->Ø       <!--[endif]-->Sets of Books: You can tie one Oracle General Ledger set of books to each inventory organization.

<!--[if !supportLists]-->Ø       <!--[endif]-->Costing Methods: You set your costing method (Standard or Average) at the organizational level.   The item attribute control level determines the costing organization.

<!--[if !supportLists]-->Ø       <!--[endif]-->Item Costs: Oracle Inventory keeps one cost per item per inventory organization.

<!--[if !supportLists]-->Ø       <!--[endif]-->Movement between Inventory Sites: You can use in-transit inventory for inter-organization transfers.

<!--[if !supportLists]-->Ø       <!--[endif]-->Planning Method: You can choose how to plan your items.

<!--[if !supportLists]-->Ø       <!--[endif]-->Forecasting:  You can forecast your items.

<!--[if !supportLists]-->Ø       <!--[endif]-->Accuracy Analysis:  You can perform a cycle count, or a physical inventory

Item validation organization

<!--[if !supportLists]-->Ø       <!--[endif]-->Item validation organization is a logical entity listing all the items that an enterprise sells to customers. Multiple item validation organizations can be listed that share the same item master organization.

<!--[if !supportLists]-->Ø       <!--[endif]-->A minimum of one item validation organizations is required per set of books.

<!--[if !supportLists]-->Ø       <!--[endif]-->A maximum of one item validation organization per operating unit is allowed to determine the items that may be sold in each operating unit.

Item Master Organization

Item Master Organization is usually the first Inventory organization that is set up.  Its single purpose is for entering items.  It has no sub inventories and is not used for inventory transactions. Items are entered in an item master organization and then assigned to be used in child organizations.

Child Organization

Child Organization is an inventory organization with at least one subinventory that is set up for processing inventory transactions.  It is not used to enter items.  It gets a list of items from the master.

What is Item Master organization and Child Organization?

<!--[if !supportLists]-->Ø       <!--[endif]-->Item Master Organization is usually the first Inventory organization that is set up.  Its single purpose is for entering items.  It has no sub inventories and is not used for inventory transactions. Items are entered in an item master organization and then assigned to use in child organizations.

<!--[if !supportLists]-->Ø       <!--[endif]-->Child Organization is an inventory organization with at least one sub inventory that is set up for processing inventory transactions.  It is not used to enter items.  It gets a list of items from the master.

What is the purpose of Organization Assignment?

After defining an Item in the Item master, it has to be assignment to the Organization and is known as Organization Assignment. The purpose of the Organization Assignment is to make the item available for Transactions in particular Organizations.

What are Organization Assignment and Organization Item?

Item can be enabled in all child organizations under master organization or child organizations where the item to be used is chosen. Inventory propagates item to all organizations in which the item is to be defined.

Organizational attributes for item attributes which are enabled in that organization, can be entered or changed which are enabled in that organization.  For example, go to an organization to choose reorder point planning for an item, and then go to another organization and choose Min-Max planning for the same item.

Deletion Constraints and Deletion Groups

<!--[if !supportLists]-->Ø       <!--[endif]-->If you want to enforce specific business rules and add custom checks before you can delete an item, you must define item deletion constraints to supplement the standard predefined item deletion conditions.

<!--[if !supportLists]-->Ø       <!--[endif]-->You can delete items that have incorrect attribute information. For example, if you make a mistake in entering an item number, use the Deletion Groups window to delete the item.

<!--[if !supportLists]-->Ø       <!--[endif]-->If you decide to purge the item immediately after incorrectly defining it and before using it anywhere in the system, you will be able to delete it.

Subinventory

<!--[if !supportLists]-->Ø       <!--[endif]-->A sub inventory is a Subdivision of an organization, representing either a physical area or a logical grouping of items, such as a storeroom or receiving dock

<!--[if !supportLists]-->Ø       <!--[endif]-->A subinventory is a physical or logical grouping of inventory, such as raw material, finished goods, defective material, or a freezer compartment.

<!--[if !supportLists]-->Ø       <!--[endif]-->The subinventory is the primary place where items are physically stocked. A subinventory must be specified for every inventory transaction

<!--[if !supportLists]-->Ø       <!--[endif]-->Sub inventories can be further divided into areas designated as locators.

Each subinventory must contain the following information:

<!--[if !supportLists]-->Ø       <!--[endif]-->Unique alphanumeric name

<!--[if !supportLists]-->Ø       <!--[endif]-->Status

<!--[if !supportLists]-->Ø       <!--[endif]-->Cost Group (feature enabled if you have WMS installed)

<!--[if !supportLists]-->Ø       <!--[endif]-->Parameters

<!--[if !supportLists]-->Ø       <!--[endif]-->Lead times

<!--[if !supportLists]-->Ø       <!--[endif]-->Sourcing information

<!--[if !supportLists]-->Ø       <!--[endif]-->Account information

Inventory Controls

Any combination of the four controls can be implemented for each item. Inventory controls are optional for all items

<!--[if !supportLists]-->Ø       <!--[endif]-->Locator

<!--[if !supportLists]-->Ø       <!--[endif]-->Revision

<!--[if !supportLists]-->Ø       <!--[endif]-->Lot

<!--[if !supportLists]-->Ø       <!--[endif]-->Serial Number

Stock Locator / Locator Control

<!--[if !supportLists]-->Ø       <!--[endif]-->Locators are optional structures within sub inventories.

<!--[if !supportLists]-->Ø       <!--[endif]-->Locators are the third level in the enterprise structuring scheme of Oracle Inventory.

<!--[if !supportLists]-->Ø       <!--[endif]-->Locators may represent rows, aisles, or bins in warehouses. Items can be received directly into and shipped items directly from locators.

<!--[if !supportLists]-->Ø       <!--[endif]-->You can structure your Oracle Inventory installation so some of the subinventories and items have locator control while others do not.  If locator control is turned on at the item level, you must specify a locator when transacting the item into or out of a subinventory.  If locator control is turned on at the subinventory level, you must specify a locator when transacting any item into or out of that subinventory.  Each stock locator you define must belong to a subinventory, and each subinventory can have multiple stock locators.  The possible locator control types are:

<!--[if !supportLists]-->o        <!--[endif]-->None

<!--[if !supportLists]-->o        <!--[endif]-->Pre-specified

<!--[if !supportLists]-->o        <!--[endif]-->Dynamic entry

<!--[if !supportLists]-->o        <!--[endif]-->Item Level

Explaining Locator Control Reports

Locator Quantities Report

You use the Locator Quantities Report to identify items and their quantities stored in the specified stock locators.  If the stock locator has a zero on-hand quantity, then the locator is not included in the report.

Locator Listing Report

You use the Locator Listing Report to list stock locators you defined.  You also use this report to review volume and weight allowed in a location before transacting items.

Revision Control

<!--[if !supportLists]-->Ø       <!--[endif]-->A revision is a particular version of an item, bill of material, or routing. 

<!--[if !supportLists]-->Ø       <!--[endif]-->By using the ‘Revision control’ option while defining items item quantities can be tracked by item revision.  To do so a revision is a must for each material transaction.

<!--[if !supportLists]-->Ø       <!--[endif]-->Revision control is enabled for items for which version changes or changes that are significant enough to track but are not affecting the function and feature of the item are tracked.

<!--[if !supportLists]-->Ø       <!--[endif]-->Revision Control item attributes cannot be changed when an item has quantity on hand. 

<!--[if !supportLists]-->Ø       <!--[endif]-->When defining Revision numbers letters, numbers and characters such as A, A1, 2B, etc can be used.

<!--[if !supportLists]-->Ø       <!--[endif]-->Letters are always in upper case and numbers may include decimals.

<!--[if !supportLists]-->Ø       <!--[endif]-->To ensure that revisions sort properly, decimals should always be followed by a number.

<!--[if !supportLists]-->Ø       <!--[endif]-->Revisions are sorted according to ASCII rules.

<!--[if !supportLists]-->Ø       <!--[endif]-->Each revision must be greater than the previous revision.  For example, revision 10 cannot be used after revision 9 because, according to ASCII sorting, 10 precede 9.

<!--[if !supportLists]-->Ø       <!--[endif]-->The value entered in the Starting Revision field in the Organization Parameters window displays as the starting revision for the item when assigning revisions to an item.

<!--[if !vml]--><!--[endif]--> <!--[if !vml]--><!--[endif]-->

Lot Control

<!--[if !supportLists]-->Ø       <!--[endif]-->Inventory provides complete lot number support for inventory transactions.

<!--[if !supportLists]-->Ø       <!--[endif]-->A lot identifies a specific batch of an item that is received and stored in an organization.

<!--[if !supportLists]-->Ø       <!--[endif]-->Lot control is a technique for enforcing the use of lot numbers during material transactions, thus enabling the tracking of batches of items throughout their movement in and out of inventory.  

<!--[if !supportLists]-->Ø       <!--[endif]-->If Lot Control is turned on for an item, the lot number must be indicated to perform a transaction.

<!--[if !supportLists]-->Ø       <!--[endif]-->Lot Control must be turned on at the item level.

<!--[if !supportLists]-->Ø       <!--[endif]-->Lot numbers must be assigned whenever items under lot control are received into inventory.

<!--[if !supportLists]-->Ø       <!--[endif]-->An inventory receipt can be split in to several lots, as necessary.

<!--[if !supportLists]-->Ø       <!--[endif]-->Quantities can be added to existing lot numbers.

<!--[if !supportLists]-->Ø       <!--[endif]-->Inventory will generate default lot numbers by using the default lot number generation method which is configured in the Organization Parameters window during setup.

Explaining Lot Control Reports

Lot Transactions Register

You can use the Lot Transactions Register to report comprehensive lot number material transaction detail within a specific date range.  You can run the report for a range of lots, items, transactions types, transaction reasons, and subinventories.  You can also specify a specific category set and display transaction quantities in their primary or transacted unit of measure.

Supplier Lot Trace Report

You can use the Supplier Lot Trace Report to trace a specific lot to its supplier lots.  You can run the report for a range of lot numbers and items and a specific supplier lot number.  The report shows you the lot material transactions related to the selected items as, lot numbers, transaction dates, and transaction quantities.

Expired Lots Report

You can use the Expired Lots Report to show lots in your organization that expire on or before the date you specify.  You can run the report for a range of items or for a specific item only.

  

Serial Control

<!--[if !supportLists]-->Ø       <!--[endif]-->A serial number is an alphanumeric piece of information assigned to an individual unit of an item.  A serialized unit is a combination of an item number and a serial number.

<!--[if !supportLists]-->Ø       <!--[endif]-->Individual units of items can be tracked by using serial numbers. Serial number control is a system technique for enforcing the use of serial numbers during a material transaction. Serial numbers can be used to track items over which a very tight control is to be maintained.

<!--[if !supportLists]-->Ø       <!--[endif]-->One serial number per unit of an item can be assigned

<!--[if !supportLists]-->Ø       <!--[endif]-->Depending on how Serial Number Control is set at the Master Item level will determine how serial numbers are generated.

<!--[if !supportLists]-->Ø       <!--[endif]-->If No Control is specified as the serial number control type, no serial number control will be enforced.

<!--[if !supportLists]-->Ø       <!--[endif]-->If Predefined is specified as the serial number control type, serial numbers for that item must be predefined.

<!--[if !supportLists]-->Ø       <!--[endif]-->If control ‘At inventory receipt’ or ‘At sales order issue’, optionally serial numbers for the item can be predefined.

Generating Serial Numbers

<!--[if !supportLists]-->Ø       <!--[endif]-->Inventory uses the starting serial number prefix and the starting serial number specified in the Item screen.

<!--[if !supportLists]-->Ø       <!--[endif]-->The process of generating serial numbers is done through a concurrent report.  This does not assign numbers to units in inventory; it simply reserves serial numbers for an item, for later use.

Serial Genealogy

<!--[if !supportLists]-->Ø       <!--[endif]-->Enables to view the composition and transaction history of a serial-controlled item through a graphical user interface.

<!--[if !supportLists]-->Ø       <!--[endif]-->Includes all material transactions within an organization.

<!--[if !supportLists]-->Ø       <!--[endif]-->Enables to trace serial numbers from an assembly to all components.

<!--[if !supportLists]-->Ø       <!--[endif]-->Enables to trace serial numbers from a component to a final assembly.

Explaining Serial Number Control Reports

Serial Number Transactions Register

You can use the Serial Number Transactions Register to report comprehensive serial number material transaction detail within a specific date range.  You can run the report for a range of serial numbers, items, transaction types, transaction reasons, and subinventories.  You can also specify a specific category set and display transaction quantities in their primary or transacted unit of measure.

Serial Number Detail Report

You can use the Serial Number Detail Report to report on information about current serialized units in your organization for a specific source type or serialized unit status.  Oracle Inventory enables you to run the report for a range of serial numbers, items, suppliers, and supplier serial numbers.

Item Templates

<!--[if !supportLists]-->Ø       <!--[endif]-->Templates are defined sets of attributes that can be used over and over to create many similar items. Templates make initial item definition easier and more consistent.

<!--[if !supportLists]-->Ø       <!--[endif]-->Templates can be applied at any time after the item is created. Multiple templates can be applied to a single item.

<!--[if !supportLists]-->Ø       <!--[endif]-->Templates can hold a complete set of attributes or a partial set.  If a partial set, then only values stored in the template overwrite those on the item

<!--[if !supportLists]-->Ø       <!--[endif]-->Users can define their own templates or predefined templates include:

ATO Model              

ATO Item

ATO Option Class              

Kit

PTO Model

PTO Option Class

Planning Item

              Phantom Item         

Subassembly

Purchased

Freight                            

Finished Good          

Outside Processing Item

Reference Item                 

Supply Item

Product Family

Item Relationships

The following types of relationships can be defined for items:

<!--[if !supportLists]-->Ø       <!--[endif]-->Item cross-references

<!--[if !supportLists]-->Ø       <!--[endif]-->Substitute items

<!--[if !supportLists]-->Ø       <!--[endif]-->Related items

<!--[if !supportLists]-->Ø       <!--[endif]-->Manufacturer part numbers

<!--[if !supportLists]-->Ø       <!--[endif]-->Customer item numbers

Relationships between items can be defined to improve purchasing management and item searching capabilities. Substitute items can be received in Oracle Purchasing.

Item cross-references

<!--[if !supportLists]-->§         <!--[endif]-->Cross–reference types define relationships between items and entities such as old item numbers or supplier item numbers.  For example, a cross–reference type  Old can be created to track the old item numbers , and a cross-reference type Supplier to track supplier part numbers.

<!--[if !supportLists]-->§         <!--[endif]-->Multiple cross-reference types can be assigned to a single item.

What is the Importance of UOM?

A unit of measure (UOM) is a term used along with a numeric value, to specify the quantity of an item. For example, “each” is a unit of measure that used to specify the number of units of an item.

A unit of measure class is a group of units of measure with similar characteristics. For example, “weight” can be a unit of measure class with units of measure such as kilogram, gram, pound, and ounce.

A unit of measure conversion is a mathematical relationship between two different units of measure.

What is the difference between Organization_Id and Org_Id?

Organization_Id represents Inventory Organization Id.

Org_Id represents Operating Unit Id.

A Global Variable exists in the Oracle Database called CLIENT_INFO, which is 64 byte long. First 10 Bytes are used to store Operating Unit ID(or ORG_ID) for the multiple organization support feature. Multi-Org views are partitioned by ORG_ID. The ORG_ID value is stored in CLIENT_INFO variable. (It comes in AP, PO, AR and OM Levels).

ORGANIZATION_ID For inventory, Mfg and BOM.

Receipt to Issue Life Cycle:

Oracle Inventory uses the receipt to issue process to manage your inventory.  The three main pieces of the process are as follows:

Receiving

When you take delivery of inventory in to your warehouse you receive it.  You can receive inventory using the following applications

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Purchasing

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Work in Process

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Inventory

Transferring

You can transfer inventory within an organization, and from one organization to another organization using the following applications

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Shipping

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Order Management

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Work in Process

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Inventory

Issuing

When you send materials out of inventory you issue it.  You use the following applications to issue inventory.

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Order Management

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Purchasing

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Work in Process

<!--[if !supportLists]-->•          <!--[endif]-->Oracle Inventory

Receiving Inventory

There are different ways you can receive inventory in to stock.

Purchasing

You can receive inventory from outside of your organization using purchasing.  The ways you use purchasing in relation to receiving are:

<!--[if !supportLists]-->Ø       <!--[endif]-->Purchase Order Receipt

<!--[if !supportLists]-->Ø       <!--[endif]-->Internal Requisition

<!--[if !supportLists]-->Ø       <!--[endif]-->In transit Receipt

<!--[if !supportLists]-->Ø       <!--[endif]-->Return Material Authorization

<!--[if !supportLists]-->Ø       <!--[endif]-->Unexpected Receipt

Work in Process

You can receive inventory from the manufacturing floor using Oracle Work in Process

<!--[if !supportLists]-->Ø       <!--[endif]-->Component Return

<!--[if !supportLists]-->Ø       <!--[endif]-->Negative Component Issue

<!--[if !supportLists]-->Ø       <!--[endif]-->Assembly Return

Inventory

You may receive inventory in to stock using the inventory application in the following ways:

<!--[if !supportLists]-->Ø       <!--[endif]-->Miscellaneous Account

<!--[if !supportLists]-->Ø       <!--[endif]-->Receipt from Project

<!--[if !supportLists]-->Ø       <!--[endif]-->User Defined

<!--[if !supportLists]-->Ø       <!--[endif]-->Inter-organization receipt

Types of Inventory Receipts

<!--[if !supportLists]-->Ø       <!--[endif]-->Receipt and Deliver

<!--[if !supportLists]-->Ø       <!--[endif]-->Receipt and then Deliver

<!--[if !supportLists]-->Ø       <!--[endif]-->Inspection

<!--[if !supportLists]-->•          <!--[endif]-->Receipt

<!--[if !supportLists]-->•          <!--[endif]-->Deliver

<!--[if !supportLists]-->•          <!--[endif]-->Inspection

Transferring Inventory

Different applications can generate requests to transfer inventory. 

Shipping

Shipping can generate a transfer to move stock from a finished goods area to a staging to for shipping.

Order Management

Order management can generate a transfer to move stock from a finished goods area to a staging area for shipping.

Work in Process

Work in Process can generate a transfer to acquire components for a project.

Inventory

Inventory transfers materials using the following methods:

<!--[if !supportLists]-->•          <!--[endif]-->Transfer between Organizations

<!--[if !supportLists]-->•          <!--[endif]-->Replenish materials

<!--[if !supportLists]-->•          <!--[endif]-->Request transfers

Issuing Inventory

You can issue stock out of inventory using the following applications:

Order Management

Order Management can generate an inventory issue through:

<!--[if !supportLists]-->•          <!--[endif]-->Sales Orders

<!--[if !supportLists]-->•          <!--[endif]-->Internal Orders

Purchasing

Purchasing can generate an inventory issue for:

<!--[if !supportLists]-->•          <!--[endif]-->Return to Vendor materials

Work in Process

Work in process can generate an inventory issue through:

<!--[if !supportLists]-->•          <!--[endif]-->Component Issue

<!--[if !supportLists]-->•          <!--[endif]-->Assembly Return

Inventory

You can issue stock using the inventory application in the following ways:

<!--[if !supportLists]-->•          <!--[endif]-->User Defined

<!--[if !supportLists]-->•          <!--[endif]-->Inter Organization Transfer

<!--[if !supportLists]-->•          <!--[endif]-->Cycle Count Negative

<!--[if !supportLists]-->•          <!--[endif]-->Request Issue

Transaction Types:

<!--[if !supportLists]-->Ø       <!--[endif]-->Receive items into your organization using a general ledger account number

<!--[if !supportLists]-->Ø       <!--[endif]-->Issue items from your organization using general ledger account number

<!--[if !supportLists]-->Ø       <!--[endif]-->Transfer items from a subinventory in your organization to another subinventory in the same organization

<!--[if !supportLists]-->Ø       <!--[endif]-->Transfer items directly between organizations

<!--[if !supportLists]-->Ø       <!--[endif]-->Transfer items between organizations by way of intransit

<!--[if !supportLists]-->Ø       <!--[endif]-->Reserve items for a specific account or temporarily prevent the release of items onto the shop floor

A transaction type is the combination of a transaction source type and a transaction action. It is used to classify a particular transaction for reporting and querying purposes.

<!--[if !vml]--><!--[endif]-->

<!--[if !supportLists]-->Ø       <!--[endif]-->A transaction type is the combination of a transaction source type and a transaction action.

<!--[if !supportLists]-->Ø       <!--[endif]-->It is used to classify a particular transaction for reporting and querying purposes.

<!--[if !supportLists]-->Ø       <!--[endif]-->Oracle Inventory also uses transaction types to identify certain transactions to include in historical usage calculations for ABC analysis or forecasting.

<!--[if !supportLists]-->Ø       <!--[endif]-->A number of transaction types are predefined in Oracle Inventory.  The user can also define additional types by setting up new combinations of source types and actions.

Transaction Source Type

You use a transaction source type with a transaction action; it uniquely identifies the type of transaction performed. Oracle Inventory provides the following predefined transaction source types.  You can define additional source types.  Predefined transaction types are as follows:

<!--[if !supportLists]-->•          <!--[endif]-->Purchase Order

<!--[if !supportLists]-->•          <!--[endif]-->Account Alias

<!--[if !supportLists]-->•          <!--[endif]-->Move Order

<!--[if !supportLists]-->•          <!--[endif]-->Internal Order

<!--[if !supportLists]-->•          <!--[endif]-->Standard Cost

<!--[if !supportLists]-->•          <!--[endif]-->Update

<!--[if !supportLists]-->•          <!--[endif]-->Internal Requisition

<!--[if !supportLists]-->•          <!--[endif]-->Sales Order

<!--[if !supportLists]-->•          <!--[endif]-->Cycle Count

<!--[if !supportLists]-->•          <!--[endif]-->Periodic Cost Update

<!--[if !supportLists]-->•          <!--[endif]-->Physical Inventory

<!--[if !supportLists]-->•          <!--[endif]-->RMA (Return Material Authorization)

<!--[if !supportLists]-->•          <!--[endif]-->Inventory

<!--[if !supportLists]-->•          <!--[endif]-->Job or Schedule

Transaction Action

You use transaction actions with a source type.  A transaction action identifies a transaction type.  Oracle Inventory provides the following transaction actions:

<!--[if !supportLists]-->•          <!--[endif]-->Assembly completion

<!--[if !supportLists]-->•          <!--[endif]-->Issue from stores

<!--[if !supportLists]-->•          <!--[endif]-->Subinventory transfer

<!--[if !supportLists]-->•          <!--[endif]-->Direct organization transfer

<!--[if !supportLists]-->•          <!--[endif]-->Cycle count adjustment

<!--[if !supportLists]-->•          <!--[endif]-->Physical inventory adjustment

<!--[if !supportLists]-->•          <!--[endif]-->Intransit receipt

<!--[if !supportLists]-->•          <!--[endif]-->Intransit shipment

<!--[if !supportLists]-->•          <!--[endif]-->WIP assembly scrap

<!--[if !supportLists]-->•          <!--[endif]-->Cost update

<!--[if !supportLists]-->•          <!--[endif]-->Receipt into stores

<!--[if !supportLists]-->•          <!--[endif]-->Negative component issue

<!--[if !supportLists]-->•          <!--[endif]-->Delivery adjustments

<!--[if !supportLists]-->•          <!--[endif]-->Negative component return

<!--[if !supportLists]-->•          <!--[endif]-->Assembly return

<!--[if !supportLists]-->•          <!--[endif]-->Vendor Managed Inventory Planning Transfers

Transaction Managers

Transaction mangers control the number of transaction workers, processing intervals and the number of transactions processed by each worker during each interval.

These run at the periodic intervals you specify until you disable them with the concurrent manager.

Cost Transaction Manager

The material cost transaction manager must run to cost material transactions.

Remote Procedure Manager

Remote procedure manager processes online inventory transactions WIP initiates, such as completions or component issue.

Material Transaction Manager

Immediately executes a material transaction after you save your changes in a transaction window.

Move Transaction Manager

The move transaction manager moves assemblies received from an outside processing supplier to the next operation.

You do not have to launch the other transaction managers if you decide to process your transactions on-line, and do not use the transaction interface.

What are the Types of Inventory Transactions?

Miscellaneous Transactions

This transaction is used to do adjustments in stock due to damage, obsolescence, issuing items for R & D or issuing track able expense items.

Subinventory Transfer

This transaction is used to transfer goods from one stockroom to another with in the same inventory organization.

Use the Subinventory transfer window to:

Transfer material within your current organization between sub inventories, or between two locators within the same subinventory

 We can transfer from asset to expense subinventories, as well as from tracked to non–tracked subinventories. If an item has a restricted list of subinventories, we can only transfer material from and to subinventories in that list.

Inter ORG Transfers

This transaction is used to transfer goods from one inventory organization to another.

Interorganization Direct Shipment

You use the Interorganization Transfer window to move inventory directly from a shipping organization to a destination organization.

<!--[if !vml]--><!--[endif]-->

Interorganization Intransit Shipment

<!--[if !supportLists]-->•          <!--[endif]-->When you perform the transfer transaction, you do not need to specify the delivery location.

<!--[if !supportLists]-->•          <!--[endif]-->You only need to enter the subinventory you are shipping from, a shipment number, the freight information, and, a percentage of the transaction value or a discrete amount that Oracle Inventory uses to compute transfer charges.

<!--[if !vml]--><!--[endif]-->

<!--[if !vml]--><!--[endif]-->

Transfer type:

Direct: Inter-organization transfers move inventory directly from the shipping organization to the destination organization.

Intransit: Inter-organization transfers move inventory to intransit inventory first. You can track this inventory until it arrives at the destination organization.

Receiving Transactions

This transaction is used to move goods from receiving dock to specified subinventory and locator.

Sales Issue

This transaction is used to move goods from pick subinventory to staged subinventory.

WIP Issue

This transaction is used to issue materials against production orders.

Note: WIP issue and Sales issue will not be covered as part of Oracle inventory training. These two inventory transactions will be covered in Oracle Shipping and WIP training

You Can Perform the Following Oracle Inventory Transactions

<!--[if !supportLists]-->Ø       <!--[endif]-->Receive items into your organization from a general ledger account number

<!--[if !supportLists]-->Ø       <!--[endif]-->Issue items from your organization to a general ledger account number

<!--[if !supportLists]-->Ø       <!--[endif]-->Transfer items from a subinventory in your organization to another subinventory in the same organization

<!--[if !supportLists]-->Ø       <!--[endif]-->Transfer items directly between organizations

<!--[if !supportLists]-->Ø       <!--[endif]-->Transfer items between organizations by way of in-transit

<!--[if !supportLists]-->Ø       <!--[endif]-->Reserve items for a specific account or temporarily prevent the release of items onto the shop floor

What is Move Order?

A move order is a request for a sub inventory transfer or account issue. The pick release process creates move orders which are pre-approved requests for sub inventory transfers to bring material from its source locations in the warehouse to a staging sub inventory. Reservations created for sales orders are automatically updated and transferred you as the move order is released and transacted.

It is a transaction type in inventory.  It is used to make sub inventory transfers.  Shipping Execution uses it to move the items during the shipping process into a stage area before the items are really shipped to the customer.

Anatomy of a Move order:

Oracle Order Picking and Shipping stores the move order source type in the header.  This refers to the entity that created the move order.  An order could be a pick wave (for sales order picks) a replenishment type, a requisition for sub inventory transfer and so on.  Order Picking and Shipping also stores the default source and destination if available, the order number, and the requested date.

The lines are the requests on that move order.  They store the item, requested quantity, completed quantity (if the move order has been partially fulfilled), a source and destination if known, and any project and task references if the organization is Project Manufacturing enabled.  The user can also request specific serial or lot numbers if know, on the move order line.

The line details are the Inventory transactions that occur to fulfill a particular request line (move order line).  If the material is locator, lot, or serial controlled, this information is filled in at the line detail level.  These details are automatically filled in by Oracle Inventory using the Inventory Picking Rules and the Item - Transaction defaults (for destination locators), or the user can manually fill in the details.  These details can be edited prior to transaction by a user.

The Move Order Line Details (transaction lines) created by the detailing process must be transacted to confirm the material drop-off in staging. This process is called Pick Confirmation. 

Pick confirmation executes the subinventory transfer that moves the material from its source location in the warehouse into the staging location.  Pick Confirmation automatically transfers the high level reservation to a detailed reservation (including lots, subinventory, revisions, and locators) in the staging location.  At pick confirmation, a user can report a missing quantity or change the transaction line if the picker chose to use material from a different lot, serial, locator, or subinventory.  If an organization’s picks rarely deviate from the suggested picking lines and the overhead of requiring a Pick Confirmation is unmanageable, the Pick Confirm transactions can occur immediately after the lines are detailed.  This option is called “auto pick confirm.”  Users can set up a default Pick Confirm policy in the Inventory organization parameters.  This default can be overridden at each Pick Release. 

Note that even if an automatic pick confirm is employed, the material is only transacted to the staging subinventory and reserved.  A user can still manage any discrepancies found by deleting the reservation and transacting the material back to its original subinventory.  If mobile devices such as bar code scanners are used to perform inventory transactions, you should use manual pick confirmation for greatest inventory accuracy and control.

Move Order Source Types

Oracle Inventory Release 11i provides three types of move orders.

<!--[if !supportLists]-->Ø       <!--[endif]-->Move Order Requisitions

<!--[if !supportLists]-->Ø       <!--[endif]-->Replenishment Move Orders

<!--[if !supportLists]-->Ø       <!--[endif]-->Pick Wave Move Orders

The move order type refers to the entity that created the move order. For all move orders, the final result is one of the two supported transactions: subinventory or move order issue.

Move Order Requisition

The requisition is a manually generated request for a move order. You must create a move order requisition. You can generate requests for subinventory transfers or move order issues. The requisition can optionally go through an Oracle Workflow approval process before it becomes a move order. If no approval process is used, the requisition becomes a move order immediately.

Replenishment Move Order

These move orders are generated by kanban cards where the pull sequence calls for a subinventory transfer (intra-organization kanbans), or by min-max planned items where the item’s replenishment source (set at the item-sub inventory level) is another sub inventory. In this case, the min-max or replenishment count report automatically generates a move order. Replenishment move orders are pre-approved and ready to be transacted.

Pick Wave Move Order

The pick release process generates move orders to bring the material from its source location in stores to a staging location, which you define as a subinventory in Oracle Inventory. This transaction is a subinventory transfer. These move orders are generated automatically by the Oracle Shipping Execution pick release process. These orders are pre-approved and ready to transact. Pick slips and other shipping and inventory reports will also be available with Oracle Order Management.

Allocating Move Orders

Allocating is the process in Oracle Inventory that uses picking rules and item transaction defaults to suggest move order line details to fulfill a move order line. The line details are the inventory transactions that must be fulfilled to complete the move order line. You can consider the allocating process as a sourcing process. Allocating occurs when you click the Allocate button in the move order transaction window.

Suggesting Sources

Oracle Inventory uses the picking rules you set up at the organization or organization-item level, to suggest source locators, revisions, and lots to source the material in order to fulfill a move order line.

Suggesting a Destination

The picking rules only suggest source locations. If the destination subinventory is locator-controlled and no locator was specified on the move order line, Oracle Inventory generates a suggestion based on the item subinventory locator default you set up for move orders. Before release 11i, the item subinventory defaults were used only for put away locations in the receiving process. You can now set up a default locator for each item that you want to move around the warehouse on a move order. This is not the same default type that you would use for receiving or shipping.

Oracle Shipping

Oracle Shipping provides two choices for when and how the user will fill in the line details.  These choices are made by setting up an organization parameter but can be overridden at pick release.

<!--[if !supportLists]-->Ø       <!--[endif]-->Auto allocate --the allocating process is done at pick release instantly after the move order is created.  No more human intervention is needed and the pick slip can be printed automatically.

<!--[if !supportLists]-->Ø       <!--[endif]-->Pick release only creates move orders but does not fill in the line details.  A user must navigate to the move order form after pick release and press the Allocate button.  This option allows warehouse managers to determine when to release the pick to the floor and might be a better solution for implementations running a global order entry with distributed warehouse management and/or shipping.  In these cases orders can be released to regional warehouses from the central order management location in advance and individual warehouses can schedule picks closer to actual ship time.

What is Transact Order?

Once the lines have been allocated, you can commit all of the transactions for a single move order line by selecting the lines you want to transact and clicking the Transact button. You can save and exit the move order line details without transacting if you need to print a pick slip report. This enables you to transact each detail line before or after picking the material.

If the user transacts less than the requested quantity, the order remains open until the full quantity is transacted or the order is closed or canceled.

What does the Auto Detail option do?     

Pick Release always creates a Move Order transaction.  When you check this     option in the Pick Release parameters, the Pick Engine creates transaction     lines suggestions.  This is a suggestion of sourcing material and it is     called "Detailing".  The Detailing also creates a high level reservation on the material if no reservations previously existed.  The Detailing can be made manually.

What does the Auto pick Confirm option do?  
This option should be active if you want the Pick Engine to accept the suggested values during Detailing.  It can be activated only if you select   the Autodetail option.