May 15, 2012

Interorganization Shipping Networks


An inter-organization shipping network describes the relationships and accounting information between a shipping organization and a destination organization. You must define a shipping network between two organizations before you can transfer material between organizations. When you set up a shipping network you must select a transfer type: intransit or direct.
        Intransit: Oracle Inventory moves material to an intermediary state before it reaches the destination organization. After the material arrives at the destination organization, you will need a receipt transaction to retrieve it. If intransit is selected, you can define:
o   Shipping Methods
o   GL Accounts to use in transit
o   Material ownership during transfer
o   Planning lead times
o   Transfer Charges
        Direct: Oracle Inventory moves the material directly to the destination organization. However, for both transfer types, you can determine default receipt routing and whether internal orders are required to transfer material.

Shipping Method

Shipping methods are the way you ship material. When you create a shipping method, you must enable it before you can use it in a shipping network. If you disable a shipping method, it cannot be used in a shipping network.

Additional Setup Steps
Entering Employees
Employees who perform cycle and physical inventory counts.
Defining Planners
Identify persons responsible for planning items or groups of items.
Defining Freight Carriers
Enables assignment of a general ledger account to one or more carriers to collect costs associated with their use. You can assign a carrier to each interorganization transfer.

Additional Organizational Setups

Material Shortage Parameters
Define the parameters for the system to determine when unsatisfied demand exceeds available quantity of incoming supply. This condition can be used by the system to trigger shortage alerts and notifications.
Organization Access
This controls access to organizations based on the user responsibility assigned to a user by the system administrator.
When implemented for one user responsibility, it is then required for all other user responsibilities accessing the same organization.

Copying Inventory Organizations

You can create new inventory organizations or copy an existing organization. You must establish a model organization to use as a baseline for new organizations. This model organization must be a transactional organization and not an item master organization. You can copy only organizations within the same operating unit. The system creates the new organizations under the same business group to which the model organization belongs, and assigns the new organizations to the same operating unit, legal entity, and ledger as the model organization.
When you copy organizations you specify which information to copy from the model organization. You can choose to copy the following information from the model organization:
        Organization definition
        Shipping networks
        Hierarchy assignments
        Bills of material and bills of material parameters
        Departments, resources, and routings
        Item information
When you copy a model organization the system automatically copies the following information:
        Subinventories
        Locators
        Work in Process parameters
        Work in Process accounting classes
        Planning parameters
        Shipping parameters
Note: The system does not copy organization-specific data including: cost type, cost subelement, Process Manufacturing Enabled, Oracle Warehouse Management enabled, and cost-sharing entities.
Read More

May 10, 2012

Subinventory
A subinventory is a physical or logical grouping of inventory such as raw material, finished goods, defective material, or a freezer compartment. A subinventory can be the primary place where items are physically stocked. You must specify a subinventory for every inventory transaction.
Storage Subinventory:
·         Mandatory
·         Tracking of good possible
·         Material reflects in onhand quantity
Receiving Subinventory:
·         Optional
·         Tracking fo goods possible
·         Does not reflect in onhand quantity
·         Available if receipt is made through use of Oracle Warehouse Management System and Oracle Mobile Supply Chain Application.
Note: Types of subinventories other than Storage matter only in WMS. You cannot have a receiving subinventory unless you are using MSCA or WMS. For example, you can receive material on the dock and can place it in a receiving subinventory (quantity is not reflected in on-hand) before you transfer it to a putaway location. There can be many receiving subinventories in the receiving area of a warehouse.

Defining Subinventories

You define subinventories by organization. Each subinventory must contain the following information:
        Unique alphanumeric name
        Status
        Cost Group (if you have Oracle Warehouse Management installed)
        Parameters
        Lead times
        Sourcing information
        Account information

Locator Control

Locators are structures within subinventories. Locators are the third level in the enterprise structuring scheme of Oracle Inventory. Locators may represent rows, aisles, or bins in warehouses. You can transact items into and out of locators. You can restrict the life of locators, establish capacity of a specific locator in weight or units, as well as specify dimensions which define a locator’s capacity by volume.
In coordination with locator settings at the subinventory and item level, you must first specify locator controls at the Organization level:
        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 you define at the subinventory level.

Dynamic and Static Locators

Dynamic Locator: Generated during a transaction as needed
Static Locator: Predetermined

Subinventory-Locator Relationship

You can structure Oracle Inventory in such a way that 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:
        None
        Prespecified
        Dynamic entry
        Item Level
You cannot use the same locator names within any two subinventories within the same organization.

Locator Flexfield Structure

Locator flexfield structure is common across all organizations. For example if you set up Row1A Rack 1A and Bin 1A in M1 Seattle, you cannot use Aisle 1A Rack 1A and Bin1A structure in M2 Boston.
Read More
Copyright © . Oracle Apps (SCM) . All Rights Reserved
Oracle Apps (SCM) is an online knowledge sharing blog which index online free tutorials, blogs and other sources, to get easier and accessible manner. The blog has been created keeping only one intention of sharing knowledge and for learning purpose. All trademarks, trade names, service marks, copyrighted work, logos referenced herein belong to their respective owners/companies. If any of the posting is violating copyright and you want us to remove that content. Please contact Here