Enter a starting revision to be the default for each new item.
Lot Number
1. Select an option for lot number uniqueness.
Across items: Enforce unique lot numbers for items across all organizations.
None: Unique lot numbers are not required.
2. Select an option for lot number generation.
User–defined: Enter user–defined lot numbers when you receive items.
At organization level: Define the starting prefix and lot number information for items using the values you enter in the Prefix, Zero Pad Suffix, and Total Length fields. When you receive items, this information is used to automatically generate lot numbers for your items.
At item level: Define the starting lot number prefix and the starting lot number when you define the item. This information is used to generate a lot number for the item when it is received.
3. Indicate whether to add zeroes to right–justify the numeric portion of lot numbers (Zero Pad Suffix).
4. Optionally, select an alphanumeric lot number prefix to use for system–generated lot numbers when generation is at the organization level.
5. Optionally, define the maximum length for lot numbers. If you use Oracle Work in Process and you set the WIP parameter to default the lot number based on inventory rules, then WIP validates the length of the lot number against the length you define in this field.
Serial Number
1. Select an option for serial number uniqueness.
Within inventory items: Enforce unique serial numbers for inventory items.
Within organization: Enforce unique serial numbers within the current organization.
Across organizations: Enforce unique serial numbers throughout all organizations.
2. Select an option for serial number generation.
At organization level: Define the starting prefix and serial number information for items using the information you enter in the following fields of this window.
At item level: Define the starting serial number prefix and the starting serial number when you define the item.
3. Optionally, select an alphanumeric serial number prefix to use for system–generated serial numbers when generation is at the organization level.
4. Optionally, enter a starting serial number to use for system–generated serial numbers.
If serial number generation is at the organization level you must enter a starting serial number.
5. Indicate whether the system will suggest serial numbers as part of the move order line allocating process. If you do not select this option, you must manually enter the serial numbers in order to transact the move order.

Encumbrance: An expense account used to recognize the reservation of funds when a purchase order is approved.

Inventory A/P Accrual :
The liability account that represents all inventory purchase order receipts not matched in Accounts Payable, such as the uninvoiced receipts account.
Purchase Price Variance : The variance account used to record differences between purchase order price and standard cost. This account is not used with the average cost method.
Invoice Price Variance : The variance account used to record differences between purchase order price and invoice price. This account is used by Accounts Payable to record invoice price variance.
Cost of Goods Sold: The profit and loss (income statement) account that tracks the default cost of goods sold account.
Sales: The profit and loss (income statement) account that tracks the default revenue account.
Project Clearance Account: When performing miscellaneous issues to capital projects, the project clearance account is used to post the distributions.
Average Cost Variance:  Under average costing with negative quantity balances, this account represents the inventory valuation error caused by issuing your inventory before your receipts.
Note: For standard costing, only the Purchase Price Variance, Inventory A/P Accrual, Invoice Price Variance, Expense, Sales and Cost of Goods Sold accounts are required. The other accounts are used as defaults to speed your set up.
Note: For average costing, only the Material, Average Cost Variance, Inventory A/P Accrual, Invoice Price Variance, Expense, Sales and Cost of Goods Sold accounts are required. The other accounts are used as defaults or are not required.

The costing organization that controls the costs in your current organization and the costing method are displayed. You cannot make changes to these fields.

1. Costing Organization

2. Costing Method


3. Transfer to GL
Indicate whether all transactions are posted in detail to the general ledger.
Caution: Transferring detail transaction distributions to the general ledger increases general ledger posting times due to the number of records created.
4. Reverse Encumbrance Indicate whether to reverse encumbrance entry upon receipt in inventory.
You normally select this option if you use encumbrances with Oracle Purchasing.
5. Optionally, enter a Cost Cutoff Date
If you leave this field blank, all available transactions will be costed,as usual. If you enter a date, all transactions prior to this date will be costed. All transactions on or later than this date will not be costed.
For inter–organization transfers, a standard costing, receiving organization will not cost a receipt if the sending organization did not already cost the transaction.
The default time is the first instant of the date. You can optionally choose another time.
The standard cost update process can be performed on the cost cutoff date. You can restart cost processing by changing the cutoff date to blank, or a future date.

6. Default Material Sub element
For standard costing, select a material sub–element that this organization uses as a default when you define item costs. For average costing, the default material sub–element you select can be used for cost collection when Project Cost Collection Enabled is set.
7. Material Over head Sub elementOptionally, select a Default Material Overhead Sub–Element from the list of values. During the Supply Chain Rollup process, when costs are merged from another organization, markup and shipping costs will use this value.
The supply chain cost rollup will complete successfully, regardless of whether this field is populated. If the Cost Rollup identifies an organization with a default material overhead sub–element not set up, a corresponding warning message will be printed in the log file.

8. Default Cost GroupIndicate the default cost group for the organization. This will default into the Default Cost Group field for each subinventory. If the WMS cost group rules engine fails to find a cost group, this cost group will be used.
9. Valuation Accounts
You choose a default valuation account when you define organization parameters. Under standard costing, these accounts are defaulted when you define subinventories and can be overridden. Under average costing, these accounts (except for Expense) are used for subinventory transactions and cannot be updated. For a detailed discussion of cost
elements.
Material An asset account that tracks material cost. For average costing, this account holds your inventory
and intransit values. Once you perform transactions, you cannot change this account.
Material Overhead An asset account that tracks material overhead cost.
Resource An asset account that tracks resource cost.
Overhead An asset account that tracks resource and outside processing overheads.
Outside processing An asset account that tracks outside processing cost.
Expense The expense account used when tracking a non–asset item.

You can define and update default inventory and costing parameters for your current organization in the following areas:

  1. Inventory Parameters
  2. Costing Information
  3. Other Account Parameters
  4. Revision, Lot, Serial, LPN Parameters
  5. ATP, Pick, Item–Sourcing Parameters
  6. Defining Inter–Organization Information
  7. Defining Warehouse Parameters
  8. 1. Enter an organization code for which you want to set up the organization parameter. 2. Select an Item Master organization. Oracle Inventory only defines items in the Item Master organization of the organization from which you enter the Items window. 3. Select a workday calendar. This is required when Oracle Master Scheduling/MRP and Oracle Supply Chain Planning is installed. 4. Optionally, select a demand class. Demand classes segregate scheduled demand and production into groups, allowing you to track and consume those groups independently. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses this demand class during forecast consumption, and shipment and production relief. 5. In the Move Order Timeout Period field, enter the number of days a move order requisition can wait for approval. The workflow approval process sends a notification to the item planner when a move order requisition requires approval. After the first timeout period, if the recipient has not approved or rejected the order, a reminder notice is sent. After the second timeout period, the order is automatically approved or rejected, depending on whether you select Approve automatically or Reject automatically in the Move Order Timeout Action field. If you want to bypass the move order approval process and automatically approve move order requisitions, enter 0 days in the Move Order Timeout Period field and select Approve automatically in the Move Order Timeout Action field. 6. Select a move order timeout action Approve automatically: After the second timeout period, move order requisitions are automatically approved. Select this option and set the Move Order Timeout Period to 0 if you want to bypass the move order approval process and automatically approve move order requisitions. Reject automatically: After the second timeout period, move order requisitions are automatically rejected. 7. Select a locator control option: None: Inventory transactions within this organization do not require locator information. Prespecified only: Inventory transactions within this organization require a valid, predefined locator for each item. Dynamic entry allowed: Inventory transactions within this organization require a locator for each item. You can choose a valid, predefined locator, or define a locator dynamically at the time of transaction. Determined at subinventory level: Inventory transactions use locator control information that you define at the subinventory level.

  • Indicate whether to allow negative balances. Determines whether inventory transactions can drive the inventory balance of an item negative.
    Attention: If insufficient quantity on hand exists in a supply subinventory to satisfy backflush demand, Oracle Work in Process forces the supply subinventory balance negative, ignoring this option setting.
  • Auto delete allocation at Move Order cancellation
  • Indicate whether this organization is an Oracle Warehouse Management enabled organization. You can use WMS features such as LPNs, task management, warehouse execution rules and cost
    groups in this organization. Locator control must be enabled in order to enable WMS. Once this has been enabled and transactions have been entered in this organization, this box cannot be unchecked.
  • Indicate whether this organization is enabled for Quality inspection.
  • Indicate whether this organization is an Oracle Enterprise Asset Management enabled Organization.
  • Enter a total load weight and unit of measure for this organization.
  • Enter a total volume and unit of measure for this organization.  

New Features in R12
1. Select a Default On-hand Material Status tracking option. This step is optional.
Attention: You cannot update this field for existing organizations. To enable this field, you must submit the Activate Onhand Level Material Status Tracking concurrent program.
2. Indicate whether locator aliases must be unique across the organization.

You can specify which organizations a responsibility can access by mapping responsibilities to organizations. Once this mapping is set up, a user logging into an Oracle Manufacturing product is restricted to the organizations mapped to the responsibility chosen. The Change Organization window is restricted as well.
Attention: Until you assign an organization to a responsibility in this window, all responsibilities have access to all organizations. Once you have restricted any responsibility to an organization, you must then explicitly define the organizations which all responsibilities can access.
Attention: This feature does not restrict access once the user is in the product. Users with access to functions that cross multiple organizations (such as ATP, Inter–organization Transfers, Item Search, Multi–organization Quantity Report, and so on) can still specify any valid organization when running these functions.