Archive | inventory RSS feed for this section

Types of Move Order

10 Sep

Types Of Move Order

Move orders are created from different sources.
This can be identified from the Move Order header move order type field.
Different types of Move Orders are 

Move Order Requisitions: 

These are created from the move order form. Based on the setup at the organization and item level, move orders require approval before they can be allocated and transacted. These requisitions can be created to charge an account or move the material from one subinventory to another.

Replenishment Move Orders: 

These are auto-created with pre approved status. Depending on the planning type you can replenish the quantity in a subinventory for an item. Three types of replenishment plans (in relation to move orders) are available:

  • Min-max Replenishment Planning
  • Kanban Replenishment Planning
  • Replenishing Count planning

Based on these sources, when appropriate programs are run, move orders are automatically created.

Pick Wave Move Order Requisitions: 

These move orders are specifically for the sales order picking process. When Pick Releasing program is run move orders are created as preapproved and allocated(depending on the Pick Release setup). Pick Confirm process transacts these pick wave move orders.

Oracle SCM Functional Interview Questions: Inventory

18 May
Inventory

  1. What are different planning methods in Inventory
  2. What are the setups for different planning method (Min-Max)
  3. What is the concurrent program for the planning
  4. What are the setups for expense item?
  5. How many key flexfields are there in Inventory?
  6. What is the use of sales order KFF?
  7. How we can have the item key flexfield with 2 segments, is it possible, if yes then how, if no then why?
  8. How will you inactivate the Inventory locations
  9. What all setups you have done in inventory organization implementation

Difference between Oracle Inventory and WMS

21 Sep

Difference between Oracle Inventory and WMS

Both Inventory and WMS modules are used to hold the inventory and do transactions like receiving and picking goods but WMS is more expensive then inventory coz WMS has got some important premium features which is not there in Inventory module.

So to explain the differences are

Inventory without WMS is basically small in size and where the granular level management and information are not required like labor cost, resource cost, etc. For example small shops or small manufacturing units who basically holds the stocks and ship it to their customer where not much of resources involved from warehouse point of view, they can simply fulfil their business requirement by using the Inventory module but if you will consider big transportation companies like UPS, DHL or big retail or FMCG manufacturing companies who manufacture thousands of products and they have their warehouse worked by number of resources, machines maintained by various departments and spread across large locations, they cannot fulfil their business requirement by simply with Inventory module, they need bit more detailed analysis of warehouse resources, cost, efficiency, effectiveness and want to track the time and labour to fulfil the customer demand in a more efficient and cost effective ways then need to go with Warehouse Management System which comes with all these features.

These are the basic features which WMS provides but not in Inventory
  • WMS comes with rule workbench which makes warehouse management lot easier and efficient by defining different rules, pick rules, putaway rules, label printing rules.
  • WMS provides cost involved in granular level in different tasks like shipping, picking, fuel costs by machine, labour costs, etc.
  • From finance or accounting point of view, suppose business maintains a line of products (more than one number of products but in one line, suppose a health care company in its hair care product line makes different products like 100 ml, 200 ml bottles, 10 ml sachets) stores in one subinventory but want to get valuation accounting details for each product. It is not possible by Inventory as in inventory all products are comes under one accounting which is defined in subinventory but the same can be derived in WMS by using cost group rule.
  • So in Inventory module, accounting details canot be given down the subinventory level but in WMS it can be derived in many different levels, in locator level, lot level, supplier level, etc.
  • Lot more features are there like operation management, task dashboard where warehouse manager can check each and individual resources and how much they are occupied, according he can assign the task to complete in timely and cost effective way which is lacking in Inventory.
  • From technology point of view, Mobile devices enabled with RF can be used with WMS, so that means you can do transaction in real time on the go when you do physical movement, you can do the same in system and also get the required label printed on the go. But in Inventory these are two different tasks, you have to physically do the transaction then need to come to the machine and do the transaction in system. In big warehouses where everyday thousands of transactions are happening, this is not a cost effective or efficient solution. But with WMS, all these things will be ease.

What and Why Oracle Warehouse Management System (WMS)

13 Mar

Oracle Warehouse Management System

Oracle Warehouse Management System (WMS) is an advanced inventory module with lot of efficient, unique and enhanced features that improves productivity of distribution centers, manufacturing and inventory handing processes. It supports manual data entry, data entry through barcode scanning and through RFID too.
It enables organizations to maximize their utilization of labor, space and equipment investments by coordinating and optimizing resource usage and material flows across a global supply chain on a single platform.
Key Business Processes supported by Oracle WMS are:
  • Inbound Logistics (Receiving from Supplier, Returns, Corrections)
  • Outbound Logistics (Picking, Packing, Shipping)
  • Reverse Logistics (Customer Returns)
  • Stocking and Internal Inventory Movements
  • WIP JOB Assembly completion, Component issues

Broad Based Support for Warehouse Processes

Oracle WMS provides a robust warehouse solutions platform to efficiently manage the flow of goods and warehouse resources across a wide variety of business processes including order fulfilment, manufacturing, field service, inbound logistics-from receipt, inspection to storage, counting and replenishment.

Optimize Warehouse Resources

Oracle WMS enables users to optimize resources such as storage space, labor and equipment using rules based execution. Putaway rules based on configurable parameters like velocity, volume and material classifications. Rules can be used to minimize fragmentation, enforce storage policies, reduce obsolescence or implement other storage restrictions. Similarly pick tasks for outbound orders can be generated considering one or more goals such as reduction in material handling (tasks for full or split cases), reduce travel time (nearest location), minimize obsolescence (FIFO) or other customer specific preferences (grade, color, size, etc).

Advanced Wave and Task Planning

Using wave planning, Oracle WMS can fulfil a large number of orders quickly by streamlining the full execution process. Oracle WMS provides a flexible and powerful planning tool with a dashboard to create, plan and track wave progress, drilldown to task or line level and the ability to configure exceptions to facilitate proactive resolution of issues. Advanced Wave Planning also includes task planning features that can be used to group and dispatch tasks based on an execution criteria.

Planned and Opportunistic Crossdocking

Oracle WMS can identify crossdocking opportunities in the warehouse by matching expected receipts with outbound shipments and manufacturing component requirements using flexible crossdock rules. These rules allow the users to have greater of control over supply and demand eligibility for crossdocking and minimize the product wait time in outbound staging areas before getting crossdocked.

Demand Driven Replenishment to Forward Pick Locations

Oracle WMS offers Push and Pull based replenishments to forward pick area for warehouses to efficiently pick high volume of orders lines. The Pull replenishment feature automatically creates a replenishment task when a potential shortage is detected in the forward pick area. The dynamic replenishment execution capability ensures that pick areas are replenished with minimal oversight and pick tasks are dispatched only when material is available to pick. Push based replenishment allows a warehouse to effectively manage a surge in demand e.g., promotions by replenishing a forward pick area based on future demand visibility of an item.

Improve Loading Efficiency and Dock Door Utilization

Oracle WMS facilitates integrated transportation planning and execution by leveraging the dock door appointments created in Oracle Transportation Management (OTM). Oracle WMS ensures that orders are released based on the dock appointments and material is staged to the correct dock door. Oracle WMS improves trailer loading by recommending loading of containers in the reverse stop sequence of a multi-stop shipping itinerary.

Support for Advanced and Non-traditional Warehousing Processes

Competitive pressures and globalization is forcing traditional warehouses to take on value added services previously reserved for manufacturing and service centers. It is forcing manufacturing centers to take on warehousing and order fulfillment activities. Oracle WMS offers advanced material and resource handling capabilities for these additional business flows.

Repair Services, Returns, Disposition, Teardown and Refurbishment

Oracle WMS also offers the materials management feature set required in reverse logistics operations. Users can define required return product flow to guide subsequent inspection and rework processing (repair, teardown, etc.). This enables users to seamlessly manage reverse logistics operations in the same distribution centers that handle vendor receipts and customer order fulfilment.

Manufacturing, Assembly and Distribution

Oracle WMS provides a seamlessly integrated system for all manufacturing execution processes including repair and maintenance business processes. Oracle WMS supports component picks for discrete jobs and schedules, ingredient picks for process manufacturing batches, parts picks for maintenance work orders and repair orders generated in Enterprise Asset Management or Depot Repair.

Adapt to Changing Needs

To adapt rapidly changing business requirements driven by customers, regulatory bodies, new product introductions, fluctuating demand and global outsourcing, Oracle WMS provides a configurable, rules-based infrastructure that easily adapts to changing business needs and compliance mandates without customization.

Distributed Deployment of Oracle Warehouse Management

Customers can deploy WMS in a decentralized environment that is physically decoupled from rest of the E-Business Suite (EBS), making it possible to leverage the latest features in WMS but with older EBS installation or potentially non-EBS host systems. Distributed WMS also ensures greater availability of WMS instance, it is an “always on” solution that is unaffected by the network connection or the general availability of the host system.

Pick Method Suited for Warehouse Business Needs

Oracle WMS provides flexibility to warehouses to choose a pick methodology that is aligned with the ordering profile of the item. It supports pick and pass, zone picking and cluster picking to reduce warehouse travel. It enables one-step pick and pack directly into shipping cartons thus eliminating downstream packing operations.

Personalized Mobile User Interfaces and Workflow Processing

Oracle WMS facilitates efficient transaction processing by enabling users to configure mobile transaction pages for their specific needs. This allows the user to view or enter only the required information that is needed to complete the transaction for a specific business context.

Rules-Driven Processes

Oracle WMS has, at its core a flexible and powerful business rules engine, which permits extensive tailoring of key WMS processes such as directed picking and putaway, labeling, material routing selection and task dispatching without the need to customize code as shown in Figure 2. This extensible rules based architecture enables key processes to evolve and adapt dynamically.

RFID Enabled

Oracle WMS provides out of the box support for RFID and EPC technology for addressing RFID labeling compliance. EPC’s can be extracted from an inbound ASN and provided on outbound ASN’s to customers. Oracle WMS also provides a flexible framework to automate any warehouse transaction via RFID or any other sensor based on an event detection infrastructure.

Device Agnostic Material Handling Equipment Integration

Warehouse Control System (WCS) feature in Oracle WMS provides out of the box integration with material handling equipment such as conveyors, carousels, ASRSs, pick to light and even voice directed picking systems. Customers can deploy diverse equipments using an open API device integration to request tasks, and receive responses from diverse equipment types. Managerial workbenches enable real-time monitoring of the equipment and provide real-time visibility to the entire automation environment.
Oracle WMS enables organizations to transform their materials management operations to agile fulfilment centers through optimal use of inventory supply and warehouse resources. It leverages a flexible framework that provides supply and demand matching, advanced task management, automation hardware support and support for the breadth of materials management processes frequently required in warehouses, manufacturing facilities and service depots

What and Why Oracle Warehouse Management System (WMS)

13 Mar

Oracle Warehouse Management System

Oracle Warehouse Management System (WMS) is an advanced inventory module with lot of efficient, unique and enhanced features that improves productivity of distribution centers, manufacturing and inventory handing processes. It supports manual data entry, data entry through barcode scanning and through RFID too.
It enables organizations to maximize their utilization of labor, space and equipment investments by coordinating and optimizing resource usage and material flows across a global supply chain on a single platform.
Key Business Processes supported by Oracle WMS are:
  • Inbound Logistics (Receiving from Supplier, Returns, Corrections)
  • Outbound Logistics (Picking, Packing, Shipping)
  • Reverse Logistics (Customer Returns)
  • Stocking and Internal Inventory Movements
  • WIP JOB Assembly completion, Component issues

<!–[if !supportLists]–>

Broad Based Support for Warehouse Processes

Oracle WMS provides a robust warehouse solutions platform to efficiently manage the flow of goods and warehouse resources across a wide variety of business processes including order fulfilment, manufacturing, field service, inbound logistics-from receipt, inspection to storage, counting and replenishment.

Optimize Warehouse Resources

Oracle WMS enables users to optimize resources such as storage space, labor and equipment using rules based execution. Putaway rules based on configurable parameters like velocity, volume and material classifications. Rules can be used to minimize fragmentation, enforce storage policies, reduce obsolescence or implement other storage restrictions. Similarly pick tasks for outbound orders can be generated considering one or more goals such as reduction in material handling (tasks for full or split cases), reduce travel time (nearest location), minimize obsolescence (FIFO) or other customer specific preferences (grade, color, size, etc).

Advanced Wave and Task Planning

Using wave planning, Oracle WMS can fulfil a large number of orders quickly by streamlining the full execution process. Oracle WMS provides a flexible and powerful planning tool with a dashboard to create, plan and track wave progress, drilldown to task or line level and the ability to configure exceptions to facilitate proactive resolution of issues. Advanced Wave Planning also includes task planning features that can be used to group and dispatch tasks based on an execution criteria.

Planned and Opportunistic Crossdocking

Oracle WMS can identify crossdocking opportunities in the warehouse by matching expected receipts with outbound shipments and manufacturing component requirements using flexible crossdock rules. These rules allow the users to have greater of control over supply and demand eligibility for crossdocking and minimize the product wait time in outbound staging areas before getting crossdocked.

Demand Driven Replenishment to Forward Pick Locations

Oracle WMS offers Push and Pull based replenishments to forward pick area for warehouses to efficiently pick high volume of orders lines. The Pull replenishment feature automatically creates a replenishment task when a potential shortage is detected in the forward pick area. The dynamic replenishment execution capability ensures that pick areas are replenished with minimal oversight and pick tasks are dispatched only when material is available to pick. Push based replenishment allows a warehouse to effectively manage a surge in demand e.g., promotions by replenishing a forward pick area based on future demand visibility of an item.

Improve Loading Efficiency and Dock Door Utilization

Oracle WMS facilitates integrated transportation planning and execution by leveraging the dock door appointments created in Oracle Transportation Management (OTM). Oracle WMS ensures that orders are released based on the dock appointments and material is staged to the correct dock door. Oracle WMS improves trailer loading by recommending loading of containers in the reverse stop sequence of a multi-stop shipping itinerary.

Support for Advanced and Non-traditional Warehousing Processes

Competitive pressures and globalization is forcing traditional warehouses to take on value added services previously reserved for manufacturing and service centers. It is forcing manufacturing centers to take on warehousing and order fulfillment activities. Oracle WMS offers advanced material and resource handling capabilities for these additional business flows.

Repair Services, Returns, Disposition, Teardown and Refurbishment

Oracle WMS also offers the materials management feature set required in reverse logistics operations. Users can define required return product flow to guide subsequent inspection and rework processing (repair, teardown, etc.). This enables users to seamlessly manage reverse logistics operations in the same distribution centers that handle vendor receipts and customer order fulfilment.

Manufacturing, Assembly and Distribution

Oracle WMS provides a seamlessly integrated system for all manufacturing execution processes including repair and maintenance business processes. Oracle WMS supports component picks for discrete jobs and schedules, ingredient picks for process manufacturing batches, parts picks for maintenance work orders and repair orders generated in Enterprise Asset Management or Depot Repair.

Adapt to Changing Needs

To adapt rapidly changing business requirements driven by customers, regulatory bodies, new product introductions, fluctuating demand and global outsourcing, Oracle WMS provides a configurable, rules-based infrastructure that easily adapts to changing business needs and compliance mandates without customization.

Distributed Deployment of Oracle Warehouse Management

Customers can deploy WMS in a decentralized environment that is physically decoupled from rest of the E-Business Suite (EBS), making it possible to leverage the latest features in WMS but with older EBS installation or potentially non-EBS host systems. Distributed WMS also ensures greater availability of WMS instance, it is an “always on” solution that is unaffected by the network connection or the general availability of the host system.

Pick Method Suited for Warehouse Business Needs

Oracle WMS provides flexibility to warehouses to choose a pick methodology that is aligned with the ordering profile of the item. It supports pick and pass, zone picking and cluster picking to reduce warehouse travel. It enables one-step pick and pack directly into shipping cartons thus eliminating downstream packing operations.

Personalized Mobile User Interfaces and Workflow Processing

Oracle WMS facilitates efficient transaction processing by enabling users to configure mobile transaction pages for their specific needs. This allows the user to view or enter only the required information that is needed to complete the transaction for a specific business context.

Rules-Driven Processes

Oracle WMS has, at its core a flexible and powerful business rules engine, which permits extensive tailoring of key WMS processes such as directed picking and putaway, labeling, material routing selection and task dispatching without the need to customize code as shown in Figure 2. This extensible rules based architecture enables key processes to evolve and adapt dynamically.

RFID Enabled

Oracle WMS provides out of the box support for RFID and EPC technology for addressing RFID labeling compliance. EPC’s can be extracted from an inbound ASN and provided on outbound ASN’s to customers. Oracle WMS also provides a flexible framework to automate any warehouse transaction via RFID or any other sensor based on an event detection infrastructure.

Device Agnostic Material Handling Equipment Integration

Warehouse Control System (WCS) feature in Oracle WMS provides out of the box integration with material handling equipment such as conveyors, carousels, ASRSs, pick to light and even voice directed picking systems. Customers can deploy diverse equipments using an open API device integration to request tasks, and receive responses from diverse equipment types. Managerial workbenches enable real-time monitoring of the equipment and provide real-time visibility to the entire automation environment.
Oracle WMS enables organizations to transform their materials management operations to agile fulfilment centers through optimal use of inventory supply and warehouse resources. It leverages a flexible framework that provides supply and demand matching, advanced task management, automation hardware support and support for the breadth of materials management processes frequently required in warehouses, manufacturing facilities and service depots

Oracle Inventory: Defining Subinventories

27 Nov

Defining Subinventory

Go to Inventory Super User responsibility
Setup à Organization à Subinventories
Click on New
Name: Should be a unique alphanumeric name
Description: Short description of the subineventory
Status: By default it takes as Active
Default Cost Group: Attach the Cost group here.
Type: Storage or Receiving, as per the requirement

Main Alternative Region:

Include in ATP: Indicate whether to include items in this subinventory in ATP calculations
Allow Reservation: Indicate whether to include this subinventory when you perform available-to-reserve calculations.
Nettable: Indicate whether the planning process uses the on-hand balance of these subinventory items as available inventory.
Quantity Tracked: Indicate whether each transaction for this subinventory updates the quantity on hand for the subinventory.
Note: If you leave this option unchecked, on-hand balances are not maintained and you cannot check or update the Asset Inventory, Include in ATP, Reservable, or Nettable options.
You can update this value only if there is no on-hand quantity for the subinventory.
Asset Subinventory: Indicate whether to maintain the value of this subinventory on the balance sheet.
Locator Control:
You can select an option only if you selected locator control as Determined at subinventory level in the Locator Control field in the Organization Parameters window. You can only update this option if there is no on-hand quantity for the subinventory.
None: Inventory transactions within this subinventory do not require locator information.
Prespecified: Inventory transactions within this subinventory require you to enter a valid predefined locator for each item.
Dynamic entry: Inventory transactions within this subinventory require you to enter a locator for each item. You may choose a valid predefined locator, or define a locator dynamically at the time of transaction.
Item level: Inventory transactions use locator control information that you define at the item level.
Picking Order: This value indicates the priority with which items can be picked from this subinventory, relative to another subinventory, where a given item resides.
Dropping Order: This value indicates the priority with which items can be dropped to this subinventory, relative to another subinventory at the time of receipt.
Inactive On: Enter the date, if you want this subinventory to inactivate.

Lead Times:

Optionally, enter pre-processing, processing, and post-processing lead times for items in this subinventory.
These lead times are used when you use min-max planning at the subinventory level.

Sourcing:

Select a source type for item replenishment
Inventory: Replenish items internally, from another subinventory in the same organization or another organization.
Supplier: Replenish items externally, from a supplier you specify in Oracle Purchasing.
Subinventory: Replenish items internally from this subinventory.

Account:

Enter all General Ledger accounts as defined in the system as per the business requirement.
Save your job. This will create a subinventory.

GL Accounts Used in Subinventories

Material
Enter a general ledger account to accumulate material costs for items received into this subinventory. This is usually an asset account used for the value of goods stored in this subinventory.
For asset items, you use this account as a default when you generate purchase requisitions from MRP, min-max organization level planning, or reorder point planning. However, when you receive the purchase order, you use the appropriate valuation or expense account.
Outside Processing
Enter a general ledger account to accumulate outside processing costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you receive items for a job or schedule in Oracle Purchasing. Oracle Work in Process relieves this account at standard cost when you issue components to a job or schedule.
Material Overhead
Enter a general ledger account to accumulate material overhead or burden costs for this subinventory. This is usually an asset account.
Overhead
Enter a general ledger account to accumulate resource or department overhead costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you complete assemblies from a job or schedule. Oracle Work in Process relieves this account at standard when you issue components to a job or schedule.
Resource
Enter a general ledger account to accumulate resource costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you complete assemblies from a job or schedule. Oracle Work in Process relieves this account at standard cost when you issue components to a job or schedule.
Expense
Enter a general ledger account to accumulate expenses for this subinventory. For expense subinventories, this account is charged when you receive any item. For asset subinventories, this account is charged when you receive an expense item.
Encumbrance
ORACLE PURCHASING ONLY

Enter a general ledger account to hold the value of encumbrances against items in this subinventory. This account is used for purchase order receipts and returns.

Oracle Inventory: Defining Subinventories

27 Nov

Defining Subinventory

Go to Inventory Super User responsibility
Setup à Organization à Subinventories
Click on New
Name: Should be a unique alphanumeric name
Description: Short description of the subineventory
Status: By default it takes as Active
Default Cost Group: Attach the Cost group here.
Type: Storage or Receiving, as per the requirement

Main Alternative Region:

Include in ATP: Indicate whether to include items in this subinventory in ATP calculations
Allow Reservation: Indicate whether to include this subinventory when you perform available-to-reserve calculations.
Nettable: Indicate whether the planning process uses the on-hand balance of these subinventory items as available inventory.
Quantity Tracked: Indicate whether each transaction for this subinventory updates the quantity on hand for the subinventory.
Note: If you leave this option unchecked, on-hand balances are not maintained and you cannot check or update the Asset Inventory, Include in ATP, Reservable, or Nettable options.
You can update this value only if there is no on-hand quantity for the subinventory.
Asset Subinventory: Indicate whether to maintain the value of this subinventory on the balance sheet.
Locator Control:
You can select an option only if you selected locator control as Determined at subinventory level in the Locator Control field in the Organization Parameters window. You can only update this option if there is no on-hand quantity for the subinventory.
None: Inventory transactions within this subinventory do not require locator information.
Prespecified: Inventory transactions within this subinventory require you to enter a valid predefined locator for each item.
Dynamic entry: Inventory transactions within this subinventory require you to enter a locator for each item. You may choose a valid predefined locator, or define a locator dynamically at the time of transaction.
Item level: Inventory transactions use locator control information that you define at the item level.
Picking Order: This value indicates the priority with which items can be picked from this subinventory, relative to another subinventory, where a given item resides.
Dropping Order: This value indicates the priority with which items can be dropped to this subinventory, relative to another subinventory at the time of receipt.
Inactive On: Enter the date, if you want this subinventory to inactivate.

Lead Times:

Optionally, enter pre-processing, processing, and post-processing lead times for items in this subinventory.
These lead times are used when you use min-max planning at the subinventory level.

Sourcing:

Select a source type for item replenishment
Inventory: Replenish items internally, from another subinventory in the same organization or another organization.
Supplier: Replenish items externally, from a supplier you specify in Oracle Purchasing.
Subinventory: Replenish items internally from this subinventory.

Account:

Enter all General Ledger accounts as defined in the system as per the business requirement.
Save your job. This will create a subinventory.

GL Accounts Used in Subinventories

Material
Enter a general ledger account to accumulate material costs for items received into this subinventory. This is usually an asset account used for the value of goods stored in this subinventory.
For asset items, you use this account as a default when you generate purchase requisitions from MRP, min-max organization level planning, or reorder point planning. However, when you receive the purchase order, you use the appropriate valuation or expense account.
Outside Processing
Enter a general ledger account to accumulate outside processing costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you receive items for a job or schedule in Oracle Purchasing. Oracle Work in Process relieves this account at standard cost when you issue components to a job or schedule.
Material Overhead
Enter a general ledger account to accumulate material overhead or burden costs for this subinventory. This is usually an asset account.
Overhead
Enter a general ledger account to accumulate resource or department overhead costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you complete assemblies from a job or schedule. Oracle Work in Process relieves this account at standard when you issue components to a job or schedule.
Resource
Enter a general ledger account to accumulate resource costs for this subinventory. This is usually an asset account. Oracle Work in Process charges this account at standard cost when you complete assemblies from a job or schedule. Oracle Work in Process relieves this account at standard cost when you issue components to a job or schedule.
Expense
Enter a general ledger account to accumulate expenses for this subinventory. For expense subinventories, this account is charged when you receive any item. For asset subinventories, this account is charged when you receive an expense item.
Encumbrance
ORACLE PURCHASING ONLY

Enter a general ledger account to hold the value of encumbrances against items in this subinventory. This account is used for purchase order receipts and returns.

Oracle Inventory Defining Organization

2 Nov

Defining Inventory Organization

Navigate to the Inventory Super User responsibility.
Setup à Organizations à Organizations
Define the following organizations as per the requirement of business
·         Business Group
·         Legal entity
·         Operating Unit
·         Organization

External organizations (for example, tax offices, insurance carriers, disability organizations, benefit carriers, or recruitment agencies)
Internal organizations (for example, departments, sections or cost centers)

Select New

Creating an Organization


1.       Enter a name for your organization in the Name field. A check is performed to see if organizations with the same name already exist.
All Oracle applications you install share the information entered in the Organization window. Therefore organization names must be unique within a business group, and business group names must be unique across your applications network.
2.       Optionally, select an organization type in the Type field.
Organization types do not classify your organization; you use them for reporting purposes only. The type may identify the function an organization performs, such as Administration or Service, or the level of each organization in your enterprise, such as Division, Department or Cost Center.
3.       Enter a start date in the From field. This should be early enough to include any historical information you need to enter.
4.       Enter a location, if one exists. You can also enter an internal address to add more details such as floor or office number.
5.       Enter internal or external in the Internal or External field. You cannot assign people to an external organization.
Examples of external organizations that may require entry are disability organizations, benefits carriers, insurance carriers, organizations that employees name as beneficiaries of certain employee benefits, and organizations that are recipients of third party payments from employees’ pay.
6.       Then save your work.

Organization Classification

As we are defining an Inventory Organization, we will choose the classification name as Inventory Organization.
Then mark the enabled checkbox and then save your work.  
Then go to Others

Select Accounting Information
Here, we need to attach the Ledger, Legal Entity and Operating Unit.

Enter the details and select Ok, again in next window Ok.
This will ask for a confirmation, select Yes.
Then again from the Others button, select Inventory Information.
This will pop up the Organization Parameters window.

Organization Parameters

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

Inventory Parameters


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.  
8. Select a Default On-hand Material Status tracking option. This step is optional.
9. Indicate whether locator aliases must be unique across the organization

Costing Information


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 element
Optionally, 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 Group
Indicate 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.

Other Accounts


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.
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.
Encumbrance: An expense account used to recognize the reservation of funds when a purchase order is approved.
Sales: The profit and loss (income statement) account that tracks the default revenue account.
Cost of Goods Sold: The profit and loss (income statement) account that tracks the default cost of goods sold account.
Project Clearance Account: When performing miscellaneous issues to capital projects, the project clearance account is used to post the distributions.
Deferred COGS Account: This account is used by the Sales Order Issue transaction type to deferred COGS until AR recognizes revenue.
Cost Variance Account:  Under average costing with negative quantity balances, this account represents the inventory valuation error caused by issuing your inventory before your receipts.
Landed Cost Management (LCM) variance account: This account is used by the new Landed Cost Management module.
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.

Revision, Lot, Serial, LPN Parameters


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.

ATP, Pick, Item–Sourcing Parameters


Select a default ATP rule.
ATP rules define the options used to calculate the available to promise quantity of an item. If you are using Oracle Order
Management, the default is the ATP rule for the Master organization.
Picking Defaults
Select a default picking rule.
Picking rules define the priority that order management functions use to pick items.
Notes: This rule will not be employed in a WMS enabled organization. The WMS picking rules will be used.
Enter a default subinventory picking order.
This value indicates the priority with which you pick items from a subinventory, relative to another subinventory, in which a given item resides. The value you enter here displays as the default when you define a subinventory.
Enter a default locator picking order.
This value indicates the priority with which you pick items from a locator, relative to another locator, where a given item resides. The value you enter here displays as the default when you define a locator.
Check the Pick Confirmation Required box if you want your pickers to manually pick confirm. If you do not check the box, pick confirmation will occur automatically.
Item-Sourcing Default
Select a source type for item replenishment.
Inventory: Replenish items internally from another subinventory in the same organization or another organization.
Supplier: Replenish items externally, from a supplier you specify in Oracle Purchasing.
None: No default source for item replenishment.
Select the organization used to replenish items.
You must enter a value in this field if you selected Inventory in the Type field.
Select the subinventory used to replenish items.
You must enter a value in this field if you selected your current organization in the Organization field. You cannot enter a value in this field if you selected Supplier in the Type field.

Inter–Organization Information


Select an Inter–Organization Transfer Charge option.
None: Do not add transfer charges to a material transfer between organizations.
Predefined percent: Automatically add a predefined percent of the transaction value when you perform the inter–organization transfer.
Requested value: Enter the discrete value to add when you perform the inter–organization transfer.
Requested percent: Enter the discrete percentage of the transfer value to add when you perform the inter–organization transfer.
Inter–organization cost accounts
Enter default inter–organization cost accounts. These accounts are defaulted when you set up shipping information in the
Inter–Organization Shipping Networks window

Oracle Inventory Defining Organization

2 Nov

Defining Inventory Organization

Navigate to the Inventory Super User responsibility.
Setup à Organizations à Organizations
Define the following organizations as per the requirement of business
·         Business Group
·         Legal entity
·         Operating Unit
·         Organization

External organizations (for example, tax offices, insurance carriers, disability organizations, benefit carriers, or recruitment agencies)
Internal organizations (for example, departments, sections or cost centers)

Select New

Creating an Organization


1.       Enter a name for your organization in the Name field. A check is performed to see if organizations with the same name already exist.
All Oracle applications you install share the information entered in the Organization window. Therefore organization names must be unique within a business group, and business group names must be unique across your applications network.
2.       Optionally, select an organization type in the Type field.
Organization types do not classify your organization; you use them for reporting purposes only. The type may identify the function an organization performs, such as Administration or Service, or the level of each organization in your enterprise, such as Division, Department or Cost Center.
3.       Enter a start date in the From field. This should be early enough to include any historical information you need to enter.
4.       Enter a location, if one exists. You can also enter an internal address to add more details such as floor or office number.
5.       Enter internal or external in the Internal or External field. You cannot assign people to an external organization.
Examples of external organizations that may require entry are disability organizations, benefits carriers, insurance carriers, organizations that employees name as beneficiaries of certain employee benefits, and organizations that are recipients of third party payments from employees’ pay.
6.       Then save your work.

Organization Classification

As we are defining an Inventory Organization, we will choose the classification name as Inventory Organization.
Then mark the enabled checkbox and then save your work.  
Then go to Others

Select Accounting Information
Here, we need to attach the Ledger, Legal Entity and Operating Unit.

Enter the details and select Ok, again in next window Ok.
This will ask for a confirmation, select Yes.
Then again from the Others button, select Inventory Information.
This will pop up the Organization Parameters window.

Organization Parameters

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

Inventory Parameters


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.  
8. Select a Default On-hand Material Status tracking option. This step is optional.
9. Indicate whether locator aliases must be unique across the organization

Costing Information


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 element
Optionally, 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 Group
Indicate 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.

Other Accounts


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.
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.
Encumbrance: An expense account used to recognize the reservation of funds when a purchase order is approved.
Sales: The profit and loss (income statement) account that tracks the default revenue account.
Cost of Goods Sold: The profit and loss (income statement) account that tracks the default cost of goods sold account.
Project Clearance Account: When performing miscellaneous issues to capital projects, the project clearance account is used to post the distributions.
Deferred COGS Account: This account is used by the Sales Order Issue transaction type to deferred COGS until AR recognizes revenue.
Cost Variance Account:  Under average costing with negative quantity balances, this account represents the inventory valuation error caused by issuing your inventory before your receipts.
Landed Cost Management (LCM) variance account: This account is used by the new Landed Cost Management module.
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.

Revision, Lot, Serial, LPN Parameters


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.

ATP, Pick, Item–Sourcing Parameters


Select a default ATP rule.
ATP rules define the options used to calculate the available to promise quantity of an item. If you are using Oracle Order
Management, the default is the ATP rule for the Master organization.
Picking Defaults
Select a default picking rule.
Picking rules define the priority that order management functions use to pick items.
Notes: This rule will not be employed in a WMS enabled organization. The WMS picking rules will be used.
Enter a default subinventory picking order.
This value indicates the priority with which you pick items from a subinventory, relative to another subinventory, in which a given item resides. The value you enter here displays as the default when you define a subinventory.
Enter a default locator picking order.
This value indicates the priority with which you pick items from a locator, relative to another locator, where a given item resides. The value you enter here displays as the default when you define a locator.
Check the Pick Confirmation Required box if you want your pickers to manually pick confirm. If you do not check the box, pick confirmation will occur automatically.
Item-Sourcing Default
Select a source type for item replenishment.
Inventory: Replenish items internally from another subinventory in the same organization or another organization.
Supplier: Replenish items externally, from a supplier you specify in Oracle Purchasing.
None: No default source for item replenishment.
Select the organization used to replenish items.
You must enter a value in this field if you selected Inventory in the Type field.
Select the subinventory used to replenish items.
You must enter a value in this field if you selected your current organization in the Organization field. You cannot enter a value in this field if you selected Supplier in the Type field.

Inter–Organization Information


Select an Inter–Organization Transfer Charge option.
None: Do not add transfer charges to a material transfer between organizations.
Predefined percent: Automatically add a predefined percent of the transaction value when you perform the inter–organization transfer.
Requested value: Enter the discrete value to add when you perform the inter–organization transfer.
Requested percent: Enter the discrete percentage of the transfer value to add when you perform the inter–organization transfer.
Inter–organization cost accounts
Enter default inter–organization cost accounts. These accounts are defaulted when you set up shipping information in the
Inter–Organization Shipping Networks window

Creating an Item in Oracle Apps

20 Oct

Creating an Item in Oracle Apps

Please follow the process to create a new Item.
Navigate to the Inventory Super User responsibility.
Go to Items à Master Items
1. Enter the Item name in Item field
2. Enter the Item Description in Description field
3. Save the form

1.png

4. Now you can copy attributes from any existing templates or manually set all the attributes for all the tabs.
5. For copying attributes from existing template, go to Tools à Copy From

2.png

6. Select any existing template which suits your requirements and then click Apply, once Template is Implemented then click done.
7. Now all attributes are set as per the template.
8. You can check the tabs individually and whenever any attribute needs to change for your business requirement, you can do the change.
9. After done with all the changes, Click Save.
3.png