Part 4-->http://ebiztechnics.blogspot.com/2016/05/oracle-ebusiness-suite-inventory-basics-part4.html
Revision Control
Revision Control
Indicate whether to
track inventory balances by revision. If you turn this option on you must
specify an existing revision number for issues and receipts]
Attention: You cannot change revision control when an item has
quantity on hand. If Revision Control is controlled at the
Master Item level, the check for on–hand quantity is against the sum of on–hand
quantities in all child organizations.
Note: Reservation control for a subinventory overrides reservation control for
an item. In other words, if an item is reservable but a subinventory is not,
the item quantity in that subinventory is not
reservable.
Can you turn the reservation control off when reservation
exists?
You cannot turn
reservation control off if reservations exist.
Attention: Oracle Work in Process recognizes either lot control or serial number
control for an item—but not both. You cannot
transact an item into
Work in Process if it has both lot and serial control defined.
Organization Setup Steps
The
Following steps should be taken in the order listed. These are the
MINIMUM
steps necessary to successfully define an Organization for the
Oracle
Inventory module. Further information on these steps and other
Optional
steps can be found in the Oracle Manufacturing Implementation
Manual
under Inventory Setup.
1.
Define your Ledger (GL function)
2.
Define your Key Flex Fields in the following order. Navigation Path:
Setup/Flexfields/Key.
Flexfields to setup: System Items, Item Categories,
Item
Catalog Group, Stock Locators, Account Alias, Sales Order.
3.
Define locations (used for a variety of functions including receiving
and default delivery locations).
Note: If you populate the organization field
of this form it will only
show
on the LOV for that organization.
4.
Define a workday calendar, also called the manufacturing calendar. Each
organization references this calendar for
planning and scheduling
activities. Optionally; define the calendar
exceptions sets. Once this
is completed, click on 'Special' and Build
the calendar. It is suggested
that the calendar start on the first day of
the work week. For
example, if the primary work schedule
consists of working Monday through
Friday with Saturday and Sunday off, then
make the start date on the
calendar coincide with a Monday date and end
with a Sunday date.
Note: A calendar must have at least 1 shift
and 1 workday pattern defined.
Use the Dates button to review the
calendar for accuracy before
building it.
5.
Define organizations. Assign and enable the appropriate Organization
classifications to each organization defined
(based on the desired
structure).
Note: Must have at least 1 INV and 1
GRE/Legal entity Organization.
The Business Group classification
should not be used unless
multi-org functionality will be used.
6.
Complete the minimum required 'other' information for each classification
selected;
a) GRE/Legal entity; must define an employer
identification number
and Set of Books.
b) Operating Unit; must define a legal
entity. Operating Units are optional.
c) Inventory Org;
i) Accounting information; Set of Books
(SOB), Legal Entity,
Operating unit (dependant).
ii) Inventory information; Org code, Item
Master Org, and calendar,
costing Org and method, and Account information
(this is located in
the costing, inter-org, and other
accounts zones), other settings
are optional based on the features the
customer intends to use.
iii) The Receiving and Customer/Supplier
information are optional.
7.
Define the Unit of Measure classes. Then define the Units of Measure. Then
define the Unit of Measure conversions for
the application.
Note: Remember; each class can only have 1
base unit of measure. Base units
of measure should generally be the
smallest unit of measure in the
class. Units of measure should have a
logical connection to the class
they are assigned. When disabling
Units of Measure; disable the
conversions first, then the Unit of
Measure, and if it is a base unit,
the class should be disabled also.
Caution, once an item has been
defined in the Item Master the primary
unit of measure for that item
may not be modified.
8.
Define subinventories that represent the physical or logical locations for
items within an organization. Must complete
name and description. All other
information is optional base on what
features of the application the customer
is going to use. You must define at least 1
subinventory per Organization.
9.
The remaining Organization setup sections are optional, based on what features
and modules the customer intends to utilize.
a) Define locators that represent storage
structures (for example, aisles
or
bins) within subinventories.
b) Define Shipping Networks and Methods to
facilitate Inter-Org Transfers.
c) Define Freight Carriers.
d) Define Organization Access. Remember that
if a customer defines any access
information in this screen for an
organization, they MUST define
access
for ALL responsibilities that they want
to have access to that
organization. Failure to do this will
cause the unlisted responsibilities
to no longer function in that organization!
e) Define Inter-Company Relations for
inter-company functionality.
Once
these steps are completed the Organization is setup and usable. The user
should
then proceed with setting up the rest of the inventory system. See the
Oracle
Manufacturing Implementation guide, or the Oracle Inventory Users guide
for
instructions on setting up Items, Categories, Costs, Transaction Defaults,
and
other features of the Oracle Inventory system. It is always advisable to
consult
Oracle Worldwide Support Services or Oracle Metalink for the current
Critical
patch list for the Inventory Module prior to implementing a new
Inventory
system.
