Oracle Inventory - Interview questions & answers

1) Which are required steps in Inventory module set up? Answer: a) All the 6 key flexfields i.e Items, Item Catalog, Account Alias, Sales Order, Locator and Item Category b) Organizations c) Change Organizations d) Intercompany Relations e) Unit of Measure Classes f)Subunventories g)Item Attribute Controls, Categories h)Default Category set i)Item Statuses j) Cost types k)Profile Options l)Inventory Accounting Periods 2) What do you mean by Required with Defaults Steps? Answer: Required Step With Defaults means that the setup functionality comes with pre-seeded, default values in the database; however, you should review those defaults /default values and decide whether to change them to suit your business needs 3)Which are Required with Defaults Steps in Inventory module? Answer: There are no such steps in Inventory module 4)There is no stock locator control in your Inventory organization.Do you still need to configure it? Answer: You need not to configure the flexfield in a specific way but you must still compile the Stock Locators key Flexfield because all Oracle Inventory transaction and on-hand inquiries and reports require a frozen flexfield definition 5) What is the use of a picking rule? Answer: When you pick release a sales order in Order Management module , Order Shipping Execution module ( which is a part of Order Management) submits requests to Oracle Inventory module which uses the information given in picking rule to give priority to pick units of an items and then it generates pick lists for sales orders 6) Can you apply material overheads to Average Costing Organization? Answer: No, you can not apply it to Average Costing Organization. However you can apply it to Standard Costing Organization

7) What is a Transaction Action? Answer: A transaction action is a predefined method of changing the quantity and/or location and/or cost of an item. It is used in Transaction Type form 8) How many Predefined Transaction Actions are available in Inventory module? Answer: You may use one of six predefined transaction actions: --issue from stores, subinventory transfer, direct organization transfer, intransit shipment, cost update and receipt into stores. 9)Can you do Inventory transactions in prior periods? Answer: Yes, you can do by setting the profile option INV: Transaction Date validation to Provide warning when date in past period or Allow date in any open period. It allows entry of a past date 10) Can you change customer item name or Item after you save it? Answer: Yes, you can change it if you have set the profile option INV: Updatable Customer Item to Yes and INV: Updatable item to Yes respectively

r 27, 2008

Line Status in Order Management

Oracle Order Management and Shipping Execution provides line status to best reflect the stage of the process for the order line and delivery line.

Line statuses can be seen in the 'status' field of the 'Line Items' Main tab in the Sales Order form. It can also be noted from the Shipping transaction form. Below are the most commonly observed line statuses and what they mean: Awaiting Shipping: Order is booked but lines are not yet picked Ready to Release: Order line is booked and passed to Shipping Execution. It is now a delivery line that is eligible for Pick Release Released to Warehouse: Pick Release has started but not completed. Either no allocations were created or allocations have not been Pick Confirmed Backordered: The delivery line is pick released but no allocations were created. As an example, if a delivery line has a quantity of 100, and at pick release only 25 are available for allocation, the original delivery line splits to create a new line (quantity of 75) for the unallocated portion with a status of Backordered Staged/Pick Confirmed: The delivery line is successfully pick released. It occurs after pick confirm to indicate subinventory transfer from source location to staging location is complete Shipped: This line status indicates that the delivery associated with the delivery line(s) is ship confirmed Picked: Pick release has completed normally (both allocation and pick confirm). The delivery associated with the delivery line(s) may have also been Ship Confirmed but the Delivery may not be set in transit and the Trip may not be closed Interfaced: If delivery was sourced from Oracle OM, the delivery line is shipped and the OM Interface and Inventory Interface concurrent processes have completed. If delivery was sourced from an Oracle Application other than OM, the delivery line is shipped and the Inventory Interface concurrent process has completed. Awaiting Fulfillment: Not all shippable lines in a fulfillment set are fulfilled Fulfilled: All lines in a fulfillment set are fulfilled Closed: Closed indicates that the line is closed. It does not necessarily indicate that the line is interfaced to Accounts Receivable (AR). Canceled: Indicates that the line has been completely canceled. No further processing will occur for this line Posted by OracleOnDemand at 12:32 PM 0 comments

esday, March 1, 2011

Handling standard wastage (Shrinkage rate) in Oracle

Lets say we have a requirement where in every manufacturing job of 100 quantity ends up producing 80 quantity. You can define a shrinkage rate to describe expected scrap or other loss. Using this factor, the planning process creates additional demand for shrinkage requirements for the item to compensate for the loss and maintain supply.

For example, if you have a demand for 100 quantity and a discrete job of 40 quantity, the planning engine would suggest a planned order of 60 quantity. This would happen when there is no value populated in the "Shrinkage rate" field on Item Master (MPS/MRP planning tab)

Now going back to the business requirement mentioned above where every manufacturing job of 100 quantity ends up producing 80 quantity. If a shrinkage rate of 0.2 is entered in Item master, planning engine assumes that you lose 20% of any current discrete jobs and 20% of any suggested planned orders.

Demand quantity = 100 a. Discrete Job = 40 Shrinkage = 20% of 40 = 8 quantity Net supply from Discrete Job = 40 minus 8 = 32 quantity

b. Net requirement balance: Demand qty - Net Supply = 100 minus 32 = 68 Planning engine suggests a planned order = 68 divided by 0.2 = 85

Total Demand = 100 (original demand) + 8 (discrete job shrinkage) + 17 (planned order shrinkage) = 125 Total Supply = 40 (discrete job) + 85 (planned order suggested by planning engine) = 125 Shrinkage is the wastage that happens while manufacturing finished goods.
---------------------------------------------------------------------Please write to us on applearn@gmail.com for your inputs

----------------------------------------------------------------------------------------

Posted by OracleOnDemand at 3:08 AM 0 comments Labels: Advanced Supply Chain Planning (ASCP), Inventory, SAM

Thursday, November 11, 2010

Move Order Transaction

Move Orders allow transaction of material transfer from one subinventory to another in the same inventory organization. At a high level, Move Order process have two basic steps: a) Creation of the Move Order b) Move Order transfer transaction

Move Order can be manually created or it can be automatically created from various replenishment and material demand processes.

Move Order can be created through multiple sources: a) Manual creation b) Min-Max replenishment c) Kanban replenishment d) Sale Order Pick Release e) WIP Job Component Pick Release f) Move Order API

Steps in the Move Order Process: 1. Move Order creation through various sources (mentioned above) 2. Move Order approval 3. Move Order allocation 4. Move Order transfer

Move Order Time Out Use if you want to require approvals for the move orders in your organization. If this is left blank, the Move Order will be approved automatically

Profile option "INV: Fill & Kill Move Order" can be used to gives capability to cancel replenishment move order lines that have partially allocated and transacted

----------------------------------------------------------------For questions and contributions, please write to applearn@gmail.com -----------------------------------------------------------------

Posted by OracleOnDemand at 2:30 AM 0 comments Labels: Inventory, SAM

Monday, April 13, 2009

Serial Number Uniqueness

Using the Organization Parameters window, user can choose the type of serial number uniqueness for the organization. You can choose to enforce uniqueness within inventory items, within an organization or across organizations. However, system stops you from creating the same serial number for the same item in a different operating unit. Obvious reason for this being that the base table MTL_SERIAL_NUMBERS does not have any column to hold the OU value. Let us know your comments, if you disagree Posted by OracleOnDemand at 5:37 PM 0 comments Labels: Inventory, SAM

Monday, March 30, 2009

Kanban in Oracle Applications

Here are few slides on implementing Kanban using Oracle Applications. Please note that slides can be viewed on http://applearn.blogspot.com Posted by OracleOnDemand at 11:52 PM 0 comments Labels: Inventory, SAM

Wednesday, March 4, 2009

Inventory Management - An Introduction

Inventory Management - An Introduction

Posted by OracleOnDemand at 12:10 PM 0 comments Labels: Inventory, SAM, Videos

Saturday, February 28, 2009

Internal Requisition to Internal Order

Hope the above helps to understand the process of Internal Requisition to Internal Order cycle in Oracle Applications Posted by OracleOnDemand at 1:43 AM 1 comments Labels: Inventory, Order Management, Purchasing, SAM, Slides

Thursday, February 5, 2009

Min-Max Planning
Min-Max Planning determines the size and timing of item replenishment orders and creates a purchase order/move order to replenish items stock. This purchase order/move order to restock items is created based upon the Min-Max Planning report. The planning report provides the item and quantity to be ordered or manufactured. Items are required to be restocked when the quantity of an item in stock is fewer than the quantity required by the inventory organization. It maintains inventory stock levels for all of your items or selected items. With min-max planning, you specify minimum and maximum inventory levels for your items and minimum and maximum order quantity. You can also specify fixed lot multiplier. When the inventory level for an item (on-hand quantities plus quantities on order) goes down below the minimum quantity prescribed by you, Oracle Inventory module suggests a new purchase requisition, internal requisition, move order, or a manufacturing job to bring the balance back up to the maximum quantity mentioned by you. Inventory module performs min-max planning for your items at either the organization level or the subinventory level. You can choose this level when you run min- max planning report. When you min-max plan at the organization level, you can optionally include the following transactions as demand quantity in the min-max planning calculation a) unreserved sales orders b) reserved sales orders c) account issue move orders d) work in process component requirements This creates Purchase requisitions or internal requisitions for buy items and WIP unreleased jobs for make items for the suggested replenishment quantities. You can then turn these requisitions into purchase orders or internal orders and the unreleased jobs into released jobs for the required items. If a revision is specified when a purchase order requisition is created for revision controlled items, it is controlled by setting of the profile option INV: Purchasing by Revision When you min-max plan at the subinventory level, you can optionally include only unreserved sales orders, reserved sales orders, account issue move orders, and subinventory transfer move orders as demand quantity in the min-max planning calculation. Subinventory level planning cannot generate jobs for WIP and does not consider WIP jobs as supply or WIP components as demand. Purchase requisitions, internal requisitions, or pre-approved move orders for the suggested replenishment quantities can be optionally created. You can then turn requisitions into purchase orders or internal orders for the required items. Sourcing Rule does not work with Min-Max Planning. Posted by OracleOnDemand at 10:43 PM 5 comments Labels: Inventory, Planning, SAM, VKD

Sunday, January 11, 2009

Which are different Inventory Planning methods?

Which are different Inventory Planning methods? There are 5 inventory Planning methods as mentioned below: 1) Subinventory Replenishment planning 2) Min-max planning 3) Re-order point planning 4) Kanban planning 5) Periodic Automatic Replenishment(PAR) Subinventory Replenishment planning Oracle Inventory provides additional methods for planning and replenishing inventories. Even if you are not maintaining perpetual on-hand balances in non-tracked subinventories, for example-you can use the replenishment counting system to plan your inventories. This may be ideal for replenishing free stock items that you store on the production floor, or office supplies kept in departmental cabinets. Oracle Inventory even provides an open interface for loading replenishment count data collected electronically, such as with a hand held bar code reader. Replenishment Counting Tracked Subinventories In some situations, you may want to do your own planning and use Oracle Inventory to create your internal requisitions. When using the replenishment system in this manner, you provide the system with one of the following pieces of information (in addition to the item and subinventory): Order quantity. You specify the quantity that is to be ordered. Order maximum quantity. Oracle Inventory orders the min-max maximum quantity. You can manually enter this information in the Replenishment Counts window or through an external interface, using the replenishment interface tables Replenishment Counting Non-Tracked Subinventories Planning and replenishment of non-quantity-tracked subinventories is different because Oracle Inventory cannot use perpetual system quantities. As you issue items from a subinventory without formal issuing procedures, it is necessary to take inventory of non-tracked subinventories to record item usage and determine reorder necessity. In order to determine when and how much to replenish, you periodically physically count the items in non-tracked sub inventory. Here also you can enter the count details through batch load transaction such as bar code reader or manually by navigation. Inventory module permits on hand quantity as an additional replenishment information type for non-tracked subinventories.

Planning Levels You can only use the replenishment counting system at the subinventory level. To use replenishment counting, you must set up item-subinventory relationships using the Item Subinventories or Subinventory Items windows. Posted by OracleOnDemand at 4:43 PM 0 comments Labels: Inventory, Planning, SAM, VKD

Monday, January 5, 2009

'Push' and 'Pull' systems of controlling resources in Inventory planning

'Push' and 'Pull' systems of controlling resources in Inventory planning The push system pushes the resources in to manufacturing based on resource planning. It is also more commonly known as the Materials Requirements Planning (MRP) system. This system is based on the Planning Department setting up a long-term production schedule which is then analysed to give a detailed production schedule for making or buying parts. This detailed schedule then pushes the operations team to make or purchase a part and push it forward to the next work station. The biggest weakness of this system is that it is based on guessing/forecasting the future customer product demand to develop the production schedule that production is based on and estimating the time it takes to produce each part. Over-estimation and under-estimation may lead to excess inventory quantity or part shortages, respectively. A Pull system is a method of controlling the flow of resources in which replacement of products is based on consumption of the item quantity. A pull system is completely based on customer product demand. Whatever is consumed is only ordered on sources of supply. Since here the resources are pulled from the supply sources, it is called 'Pull' system. A Kanban system of Inventory planning is a Pull system that uses color-coded cards attached to parts or part containers to regulate the upstream production and delivery flow. Posted by OracleOnDemand at 12:23 AM 0 comments Labels: Advanced Supply Chain Planning (ASCP), Inventory, Oracle Fundamentals, Planning, SAM, VKD

Monday, December 29, 2008

What is a kit ? How does it differ from PTO ?

What is a kit ? How does it differ from PTO ? A kit is a PTO item which consists of a standard list of mandatory components (or included items) i.e

standard bills of material which you pick, pack and ship when you process a customer sales order for that item. A kit is similar to a picktoorder model because it has shippable components, but it has no available options to choose like PTO model and customer places a sales order directly by its item code number and not by using the configuration window (selecting from various options). In Oracle Inventory module, kit item type and kit item template are pre-defined by Oracle and are supplied along with software. An example of a product kit is a motor car maintenance kit which consists spanners, jack etc.It is quite possible that each kit component is in different stock keeping unit( SKU). The word Kitting is used when you make a kit after picking it's components from subinventory/ies and pack it. For example making a bundle of a kit components is called kitting. In short, kit is a bundle of various mandatory components which a merchant /manufacturer sells as a master product. Posted by OracleOnDemand at 9:49 PM 0 comments Labels: Inventory, Oracle Fundamentals, Order Management, SAM, VKD

Saturday, December 6, 2008

Oracle Inventory - Interview questions & answers

1) Which are required steps in Inventory module set up? Answer: a) All the 6 key flexfields i.e Items, Item Catalog, Account Alias, Sales Order, Locator and Item Category b) Organizations c) Change Organizations d) Intercompany Relations e) Unit of Measure Classes f)Subunventories g)Item Attribute Controls, Categories h)Default Category set i)Item Statuses j) Cost types k)Profile Options l)Inventory Accounting Periods 2) What do you mean by Required with Defaults Steps? Answer: Required Step With Defaults means that the setup functionality comes with pre-seeded, default values in the database; however, you should review those defaults /default values and decide whether to change them to suit your business needs 3)Which are Required with Defaults Steps in Inventory module?

Answer: There are no such steps in Inventory module 4)There is no stock locator control in your Inventory organization.Do you still need to configure it? Answer: You need not to configure the flexfield in a specific way but you must still compile the Stock Locators key Flexfield because all Oracle Inventory transaction and on-hand inquiries and reports require a frozen flexfield definition 5) What is the use of a picking rule? Answer: When you pick release a sales order in Order Management module , Order Shipping Execution module ( which is a part of Order Management) submits requests to Oracle Inventory module which uses the information given in picking rule to give priority to pick units of an items and then it generates pick lists for sales orders 6) Can you apply material overheads to Average Costing Organization? Answer: No, you can not apply it to Average Costing Organization. However you can apply it to Standard Costing Organization 7) What is a Transaction Action? Answer: A transaction action is a predefined method of changing the quantity and/or location and/or cost of an item. It is used in Transaction Type form 8) How many Predefined Transaction Actions are available in Inventory module? Answer: You may use one of six predefined transaction actions: --issue from stores, subinventory transfer, direct organization transfer, intransit shipment, cost update and receipt into stores. 9)Can you do Inventory transactions in prior periods? Answer: Yes, you can do by setting the profile option INV: Transaction Date validation to Provide warning when date in past period or Allow date in any open period. It allows entry of a past date 10) Can you change customer item name or Item after you save it? Answer: Yes, you can change it if you have set the profile option INV: Updatable Customer Item to Yes and INV: Updatable item to Yes respectively Posted by OracleOnDemand at 11:17 PM 0 comments

Labels: Interview Questions, Inventory, SAM, VKD

Saturday, November 22, 2008

Serial Controlled Items

Serial Controlled Items A Serial Number is a unique number assigned to each discrete unit of an item that is stored in inventory. A serial number can also be defined as a set of characters that uniquely identifies a single unit and can be used for traceability and warranty purposes. Serial numbers are valuable in quality control, as once a defect is found in the production of a particular batch of product, the serial number will quickly identify which units are affected. Serial numbers are also used as a deterrent against theft and counterfeit products in that serial numbers can be recorded, and stolen or otherwise irregular goods can be identified. Oracle Inventory provides complete serial number support for inventory transactions. Serial number control can be enabled for specific items in inventory. For items under serial number control, a unique serial numbers is assigned to each individual unit and thereafter the same serial numbers is referenced each time a material transaction is performed. Serial Number Uniqueness A Serial Number must be unique so that it can be tracked. Uniqueness of Serial Numbers can be enforced at various levels. This is defined at the inventory organization level. Within Inventory Items Once a serial number is assigned to a particular item, it cannot be assigned to the same item regardless of the inventory organization. For example if serial number SN100 is assigned to item A, serial number SN100 cannot be assigned to any other instance of item A in any other inventory organization. Within Organizations In addition to the restrictions Within Inventory Items control, the same serial number cannot exist twice within the same organization. For example if serial number SN100 is assigned to item A, it cannot be assigned to Item B in the same inventory organization. However, SN100 can be assigned to item B in any other organization. Across Organizations In addition to the restrictions Within Organizations, once a serial number is assigned to an item, it cannot be assigned to any other item regardless of organization. For example if serial number SN100 is assigned to item A, it cannot be assigned to item B in any organization. If uniqueness Across

Organization is assigned to to any organization it restricts the serial numbers in all other organizations. If one organization dictates Across Organizations, all other organizations must do so too Posted by OracleOnDemand at 1:20 PM 0 comments Labels: Inventory, SAM

Thursday, November 6, 2008

Physical Inventory Adjustments for Reserved Items

Physical Inventory Adjustments for Reserved Items While performing Physical Inventory activities using Oracle Inventory, user performs the following steps: 1. Physical Inventory setup to define tolerances, subinventories etc. 2. Physical Inventory snapshot 3. Tag generation 4. Tag count entry 5. Approve Physical Inventory 6. Post Physical Inventory adjustments While approving the physical inventory, user might face a message "You are trying to perform Physical Inventory Adjustment for material that has reservations" This is an intended functionality. Inventory cannot be adjusted so that these adjustments take quantity from reservations. Users need to unreserve the demand and perform adjustment. The System does not know which Reservations are genuine now

For any questions, please use the comments on this post on http://applearn.blogspot.com Posted by OracleOnDemand at 12:06 PM 3 comments Labels: Inventory, SAM

Tuesday, August 19, 2008

Oracle Inventory Tables

mtl_system_items mtl_item_revisions mtl_item_categories mtl_material_transactions mtl_transaction_lots_numbers mtl_serial_numbers rcv_shipment_headers rcv_shipment_lines mtl_system_item_interface mtl_item_revisions_interface mtl_item_categories_interface mtl_transaction_interface mtl_transaction_lots_interface mtl_serial_numbers_interface rcv_headers_interface rcv_transactions_interface Posted by OracleOnDemand at 11:18 PM 0 comments Labels: Inventory, SAM

Monday, February 4, 2008

Creating an Item

Use this procedure to create a new item 1. With an Inventory responsibility, navigate as Inventory -->Items --> Master Items 2. Enter Item name and Item description. Click Save 3. To copy from an existing item template, on the same form go to Tools --> Copy from. Select the item template (for example Purchased); applying item template would enable the pre-set item attributes for this item template. Users can create couple of item templates which suits their requirements and use each of them for faster item creation 4. Observe and enable the fields on each of the tabs on the item creation form such as Inventory, Order Management, Invoicing, Purchasing, Bills of Material, Costing etc. Details on each of the attributes would be discussed while discussing the relevant modules. 5. After creation the item is Master Organization as above, to enable it in other inventory organizations navigate as Tools --> Organization Assignment. Check the required organizations and save. Posted by OracleOnDemand at 9:58 AM 0 comments Labels: Inventory, Purchasing, SAM

Thursday, January 31, 2008

Organization setup in Oracle Inventory

Below are are the minimum steps necessary to successfully define an Organization in Oracle Inventory: 1. Define your set of books (GL function) 2. Define the Key Flex Fields: System Items, Item Categories, Item Catalog Group, Stock Locators, Account Alias and Sales Order 3. Define locations 4. Define a workday calendar 5. Assign and enable the appropriate Organization classifications to each organization defined 6. Complete the minimum required 'other' information for each classification selected. For example, for the inventory Org; a) Accounting information- Set of Books (SOB), Legal Entity, Operating unit b) Inventory information- Org code, Item Master Org, calendar, costing Org and method, and Account information c) The Receiving and Customer/Supplier information are optional 7. Define the Unit of Measure classes, Units of Measure and then Unit of Measure conversions

8. Define subinventories that represent the physical or logical locations for items within an organization 9. The remaining Organization setup sections are optional, based on what features and modules the customer intends to utilize a) Define locators b) Define Shipping Networks c) Define Freight Carriers d) Define Organization Access e) Define Inter-Company Relations for inter-company functionality Posted by OracleOnDemand at 1:44 AM 0 comments Labels: Inventory, SAM

Friday, January 25, 2008

Commonly used terms in Oracle Inventory

What is an Inventory Item? A part number or product code used to track goods or services. Inventory item numbers represent physical goods that are purchased, built or assembled. Inventory item numbers may also be created to represent services sold to customers. These numbers have attributes that describe or control how the item is used. Inventory items are created in an Item Master Organization and then assigned to execution inventory organizations. Attributes for items may be set at the master level, so the value is consistent across all organizations, or at the organization level, so that the value may vary by organization. The attribute control level determines if an attribute is set at the master or organization level. An example of a typical

master level controlled attribute is Item Description, which you may want to be the same across all organizations. Planner code, however, is set at the organization level, as each organization has a planner responsible for managing the item. What is an Inventory Organization? An entity used to represent a manufacturing or distribution site. Inventory organizations are where a user tracks on-hand balances, manufactures goods, and transacts the daily ins and outs of material movement. An inventory organization is the lowest level entity for costing goods, planning material requirements, and securing system access. Only a single address may be assigned to an Inventory Organization. An inventory organization is assigned a Set of Books which determines the chart of accounts, fiscal calendar, and base currency for all financial and value added activities that occur within the organization. Inventory Organizations are also assigned to a Legal Entity Organization and an Operating Unit Organization. A variation on the inventory organization is the master item organization. Generally, with Oracle Applications a single inventory organization is created and designated at the master organization. Items are defined first in the master organization, then enabled in other inventory organizations as necessary. Some of the item attributes are set as controlled at the master organization and therefore the attribute values cannot be updated within individual inventory organizations. Category sets may also be designated as master organization level. Cross-references are also master level only or master level optional as well What is a Category Set? A grouping of item categories. A category set is a user-defined entity for grouping items by category within the category set entity. Oracle inventory requires at least one category set be used. Product family, commodity, usage, or any other grouping and reporting requirements a user may have generally define category sets for grouping items. Category sets may be defined at the master organization level or the inventory item organization level. What is an Item Category? A code used for classifying or grouping items. Items are assigned to a category within a category set for reporting and grouping. To see the grouping, a user would specify a category set and one or more categories from that set What is a Subinventory? Physical or logical locations for storing inventory. Subinventories are generally defined to represent the main stores area as well as stocking points on the production floor. Additional subinventories may be used to specify supply closets or cabinets and the cage area for discrepant material. Subinventories are

flagged as to availability for planning (nettable), reservations, and available to promise checks, thereby determining the availability of the material stored in the subinventory. Subinventories are assigned material asset account numbers. As goods move in and out of a subinventory a transaction posts to the asset account. What is a Workday Calendar? The workday calendar indicates the manufacturing workdays for an inventory organization. The calendar indicates holidays as well as work shifts. Multiple calendars may be defined for an organization to represent differences in workdays by department or group. What is a Stock Locator? A physical area within a stockroom. The stock locator is a key flexfield that is often defined as a multiple segment flexfield with the segments representing the physical layout of a stockroom. For example, a stockroom may be laid out in rows of shelves with bins on the shelves, each numbered so that a row/shelf/bin combination would direct someone to a particular material storage compartment. Such an implementation would define a locator flexfield as a 3 segment flexfield with segments for row, shelf, and bin Posted by OracleOnDemand at 11:35 AM 4 comments Labels: Inventory, Most Asked Questions (MAQs), SAM

Tuesday, January 8, 2008

Entering Receipts from a Supplier

Navigation: Inventory --> Receiving --> Receipts 1) Choose the Source Type as Supplier 2) Enter Purchase Order Number 3) Click Find button On the next screen that pops up, 1) Check the Line which is to be received 2) Enter Subinventory name in the Subinventory Field & Save the record 3) Click on Header button to see Receipt Number Note: The Lines will be behind the Header window. If the header window is closed, the lines can be viewed On saving this transaction, the receipt for the item selected from the Purchase Order is completed Posted by OracleOnDemand at 11:57 PM 1 comments Labels: Inventory, Purchasing, SAM

Thursday, January 3, 2008

Oracle Inventory - Training

Course reflects the logical flow of the processes in Inventory Management. Understand where Oracle Inventory fits in the overall enterprise structure. Learn how to setup items, how to use various inventory controls available, how to perform trnsactions & transfers, how to setup cycle counting and physical inventory. Use of powerpoint slides for a clear understanding of the concepts and flow. Lab guides on each session topic provides a step-by-step approach to help you to understand the minute details as well. Understand the new features that Oracle Ebusiness Suite Release 12 is offering in Oracle Inventory.

Course Topics Receipt to Issue Lifecycle Receiving Inventory Transferring Inventory Issuing Inventory Multi-Org Feature in Oracle Applications Structure of an Inventory Organization Model an Enterprise in Oracle Applications Organization Structure, Overview Defining Items Item Attributes and Statuses

Assigning Items to Organizations Defining Units of Measure Item Attributes and Statuses Item Master Organization Defining Item Deletion Constraints Setting up Item Profile Options Subinventories Locator Control Revision Control Lot Control Serial Control Transaction Flows Transaction Types Move Orders Transaction Reasons Shipping Networks Movement Statistics Cycle Counting Physical Inventory ABC analysis *Please note that the training mode would be class-room training and includes fees based on modules selected *We arrange training on need basis for a batch of interested aspirants. Posted by OracleOnDemand at 12:01 AM 0 comments Labels: Inventory, Training

Tuesday, November 6, 2007

Oracle Inventory - Organizations - Basics

Oracle Applications uses multiple types of organizations to build the business execution structure. At the top of the structure is the accounting set of books SOB), defined in the General Ledger. Next, different types of organizations are used to further define the organization structure and relationships. All organizations are defined and updated with the Define Organization form. Set of Books: A General Ledger SOB, linked to the inventory organization, controls the financial accounting of inventory transactions. A SOB is made up of a chart of accounts, a financial calendar, and a currency. The general ledger secures transactions (journal entries, balances) by SOB.

Legal Entity. A legal entity organization defines the tax and fiscal reporting level. The legal entity represents the legal company. Operating Unit: An operating unit organization defines the Purchasing, Order Entry, Accounts Payable and Accounts Receivable level of operation. An operating unit may span multiple manufacturing facilities, distribution points and sales offices, or it may be limited to a single site. Inventory Organization: Two flavors of inventory organizations are found in Oracle Applications. They are defined the same, and both are assigned a set of books, a legal entity organization, an operating unit organization, and a location. An item master organization is used for item number maintenance and validation. This master organization serves as a data repository storing items and item attributes, master level categories and category sets, master level cross references, and numerous data defaults. On-hand balances, inventory movements, and other on-going inventory activities are not performed in an item master organization. Generally, the master organization is used as the validation organization for Purchasing and Order Entry. It is recommended that a single item master organization be defined, even in multiple organization, multiple sets of books environments. In addition to the item master organization there are one or more non-master inventory organizations. Like the item master inventory organization, the non-master organizations are assigned a set of books, a legal entity organization and an operating unit organization. The non-master inventory organization points to a master organization and looks to the master organization for master level item attributes, master level categories, and other master level controlled data. Note that each organization has its own set of books/legal entity/operating unit relationship, so inventory organizations with differing SOBs or operating units may share the same master organization. These non-master inventory organizations are the execution level organizations. They hold on-hand balances and transaction history. Here is where inventory users execute their daily activities, such as receiving and issuing material, performing cycle counts, and viewing material availability and transaction history. A single organization therefore generally represents a single manufacturing site or distribution center. Locations: A location code is an address. Each inventory organization must be assigned at least one location code.

Subinventories: A subinventory is used as a holding point for on-hand inventory and generally represents a stockroom, stocking area or cage used for storing material. Subinventories are defined within inventory organizations. An inventory organization may have any number of subinventories, and an asset account is assigned to each subinventory. Since the subinventory entity is logical, as there is not an address or physical location description associated with it, clients may define subinventories for any physical or logical grouping of inventory Stock Locators: Stock locators are an optional entity that may be used to represent physical locations within a subinventory. You may choose to use stock locators for selected subinventories or selected items within selected subinventories. If locators are used, subinventory and locator track on-hand balances. Therefore, if locators are defined to represent a shelf within a stockroom, on-hand balances on the system would show the item and quantity down to the physical location within the facility. Oracle Inventory uses a key flexfield for stock locators. This presents a few limitations for its use. Only one locator flexfield definition is allowed per install. Therefore, if the stockroom (subinventory) wants to track material by row, bin and shelf, it will likely define a three-segment flexfield with segments for row, bin, and shelf. If locators are desired for another subinventory, even in another organization, the structure will again be 3 segments for row, bin and shelf. In addition to this limitation, locators must be unique within an organization; you cannot use the same locator in different subinventories within an organization, but you can use the same locator in subinventories in a different organization. Posted by OracleOnDemand at 8:36 PM 3 comments Labels: Inventory, SAM Newer Posts Older Posts

Knowledge increases with sharing! If you would like to contribute, please drop an email on applearn@gmail.com
Showing newest posts with label Oracle Fundamentals. Show older posts

Wednesday, January 14, 2009

Shortnames for Oracle Applications products

Shortnames for Oracle Applications products 1)ABM - Activity Based Management 2)AD - Applications DBA 3)AHL - Oracle Advanced Service Online 4)AK - Oracle Common Modules-AK 5)ALR - Oracle Alert 6)AMF - Oracle Fulfillment Services 7)AMS - Oracle Marketing 8)AP - Oracle Payables 9)AR - Oracle Receivables 10)AS - Oracle Sales 11)ASG - Oracle CRM Gateway for Mobile Services 12)ASL - Oracle Mobile Field Sales Laptop 13)ASO - Oracle Order Capture 14)AST - TeleSales 15)AX - Global Accounting Engine 16)AZ - Application Implementation 17)BEN - Oracle Advanced Benefits 18)BIC - Customer Intelligence 19)BIL - Sales Intelligence 20)BIM - Marketing Intelligence 21)BIS - Oracle Applications BIS 22)BIX - Call Center Intelligence 23)BNE - Oracle Web ADI 24)BOM - Oracle Bills of Material 25)BSC - Balanced Scorecard 26)CCT - Oracle Call Center and Telephony 27)CE - Oracle Cash Management 28)CHV - Oracle Supplier Scheduling 29)CLN - Supply Chain Trading Connector for RosettaNet 30)CN - Oracle Sales Compensation 31)CS - Oracle Service 32)CSC - Customer Care 33)CSD - Depot Repair 34)CSE - Oracle Enterprise Install Base 35)CSF - Field Service 36)CSI - Install Base 37)CSM - Oracle Field Service Palm 38)CSP - Oracle Spares Management 39)CSR - Oracle Scheduler 40)CSS - Support

41)CUG-Oracle Citizen Interaction Center 42)CUN - Oracle Network Logistics NATS 43)CZ - Oracle Configurator 44)EAM - Oracle Enterprise Asset Management 45)EC - Oracle e-Commerce Gateway 46)ECX - Oracle XML Gateway 47)EDR - Oracle E Records 48)ENG - Oracle Engineering 49)FII - Financials Intelligence 50)FLM - Oracle Flow Manufacturing 51)FND - Application Object Library 52)FTE - Oracle Transportation Hub 53)FV - Oracle Federal Financials 54)GHR - Oracle Federal HR 55)GL - Oracle General Ledger 56)GMA - Oracle Process Manufacturing Systems 57)GMD - Oracle Process Manufacturing Product Development 58)GME - Oracle Process Manufacturing Process Execution 59)GMF - Oracle Process Manufacturing Financials 60)GMI - Oracle Process Manufacturing Inventory 61)GML - Oracle Process Manufacturing Logistics 62)GMP - Oracle Process Manufacturing Process Planning 63)GMS - Oracle Grants Accounting 64)GR - Oracle Process Regulatory Mgmt 65)HRI - Human Resources Intelligence 66)HXC - Oracle Time and Labor 67)HXT - Oracle Time and Labor Rules 68)IBA - iMarketing 69)IBC - Oracle iContent 70)IBE - iStore 71)IBU - iSupport 72)IBY - iPayment 73)ICX - Oracle Self-Service Web Applications 74)IEB - Oracle Interaction Blending 75)IEC - Oracle Campaign Plus 76)IEM - Oracle eMail Center 77)IEO - Call Center Technology 78)IES - Scripting 79)IEU - Oracle Universal Work Queue 80)IEX - Oracle Collections 81)IGC - Commitment Administration 82)IGF - Student Systems Fin Aid

83)IGI - Oracle International Public Sector Financials 84)IGS - Oracle Student Sytems 85)IGW - Oracle Grants Proposal 86)INV - Oracle Inventory 87)IPD - Oracle Product Development Exchange 88)ISC - Supply Chain Intelligence 89)JTF - CRM Foundation 90)JTM - Oracle CRM Mobile Foundation 91)JTS - Oracle CRM Self Service Administration 92)MRP - Oracle Master Scheduling/MRP 93)MSC - Oracle Advanced Supply Chain Planning 94)MSD - Oracle Demand Planning 95)OFA - Oracle Assets 96)OKC - Oracle Contracts Core 97)OKI - Oracle Contracts Intelligence 98)OKL - Oracle Lease Management 99)OKR - Oracle Contracts for Rights 100)OKS - Oracle Contracts Service Module 101)ONT - Oracle Order Management 102)OPI - Operations Intelligence 103)OTA - Oracle Training Administration 104)OZF - Funds & Budgets 105)PA - Oracle Projects 106)PAY - Oracle Payroll 107)PER - Oracle Human Resources 108)PJM - Oracle Project Manufacturing 109)PN - Oracle Property Manager 110)PO - Oracle Purchasing 111)POA - Purchasing Intelligence 112)POM - Oracle Exchange 113)PON - Oracle Sourcing 114)POS - Internet Supplier Portal 115)PQH - Oracle Public Sector HR 116)PSA - Public Sector Applications 117)PSB - Oracle Public Sector Budgeting 118)PSP - Oracle Labor Distribution 119)PV - Partner Relationship Management 120)QA - Oracle Quality 121)QP - Oracle Pricing 122)QRM - Oracle Risk Management 123)RG - Application Report Generator 124)RLM - Oracle Release Management

125)VEA - Oracle Automotive 126)WIP - Oracle Work in Process 127)WMS - Oracle Warehouse Management System 128)WSH - Oracle Shipping 129)WSM - Shop Floor Management 130)XDP - Oracle Provisioning 131)XNC - Oracle Sales for Communications 132)XNI - Oracle Install Base Intelligence 133)XNP - Oracle Number Portability 134)XNS - Oracle Service for Communications 135)XTR - Oracle Treasury Posted by OracleOnDemand at 10:35 PM 1 comments Labels: Most Asked Questions (MAQs), Oracle Fundamentals, SAM, VKD

Monday, January 5, 2009

'Push' and 'Pull' systems of controlling resources in Inventory planning

'Push' and 'Pull' systems of controlling resources in Inventory planning The push system pushes the resources in to manufacturing based on resource planning. It is also more commonly known as the Materials Requirements Planning (MRP) system. This system is based on the Planning Department setting up a long-term production schedule which is then analysed to give a detailed production schedule for making or buying parts. This detailed schedule then pushes the operations team to make or purchase a part and push it forward to the next work station. The biggest weakness of this system is that it is based on guessing/forecasting the future customer product demand to develop the production schedule that production is based on and estimating the time it takes to produce each part. Over-estimation and under-estimation may lead to excess inventory quantity or part shortages, respectively. A Pull system is a method of controlling the flow of resources in which replacement of products is based on consumption of the item quantity. A pull system is completely based on customer product demand. Whatever is consumed is only ordered on sources of supply. Since here the resources are pulled from the supply sources, it is called 'Pull' system. A Kanban system of Inventory planning is a Pull system that uses color-coded cards attached to parts or part containers to regulate the upstream production and delivery flow. Posted by OracleOnDemand at 12:23 AM 0 comments Labels: Advanced Supply Chain Planning (ASCP), Inventory, Oracle Fundamentals, Planning, SAM, VKD

Monday, December 29, 2008

What is a kit ? How does it differ from PTO ?

What is a kit ? How does it differ from PTO ? A kit is a PTO item which consists of a standard list of mandatory components (or included items) i.e standard bills of material which you pick, pack and ship when you process a customer sales order for that item. A kit is similar to a picktoorder model because it has shippable components, but it has no available options to choose like PTO model and customer places a sales order directly by its item code number and not by using the configuration window (selecting from various options). In Oracle Inventory module, kit item type and kit item template are pre-defined by Oracle and are supplied along with software. An example of a product kit is a motor car maintenance kit which consists spanners, jack etc.It is quite possible that each kit component is in different stock keeping unit( SKU). The word Kitting is used when you make a kit after picking it's components from subinventory/ies and pack it. For example making a bundle of a kit components is called kitting. In short, kit is a bundle of various mandatory components which a merchant /manufacturer sells as a master product. Posted by OracleOnDemand at 9:49 PM 0 comments Labels: Inventory, Oracle Fundamentals, Order Management, SAM, VKD

What is Configure to order (CTO) ?

What is Configure to order (CTO) ? It is a method of manufacturing which allows you, or your customer, to choose a base product at the very moment of ordering and then configure all the variable parameters (features) associated with that product from defined/available options. Based on these selections, configurable items on each quote or order typically generates the unique product configuration and manufacturing routing and/or bill of materials based on various features and options. Vendor/order receiving company subsequently builds that configuration dynamically upon receipt of the order. The ability of the vendor to make and deliver products customized to specific customer needs offers a powerful competitive edge over competitors. CTO is an environment in which the product or service is assembled or kitted on receipt of the sales order. Oracle EBS supports the Configure to Order environment with a range of features in order entry, demand forecasting, master scheduling, production, shipping, and financial accounting. Configure to Order includes Pick-to-Order (PTO) and Assemble-to-Order (ATO) items, models, and hybrids. It supports building configurations using other configurations as sub-assemblies (multi-level

configure-to-order), internal and external sourcing of ATO models at any level in the BOM and supports multi-level PTO/ATO hybrids. Posted by OracleOnDemand at 9:42 PM 2 comments Labels: Manufacturing Foundations, Oracle Fundamentals, Order Management, SAM, VKD

What is Pick to Order (PTO) ?

What is Pick to Order (PTO) ? It is a configure-to-order environment where the options and included items in a PTO model (finished good) appear on pick slips after you receive the sales order from customer. Pickers gather the options (based on selection rules), the predefined shippable products parts/components or service from their predefined locations using pick slip and then ship the order. It is assumed that options and components quantity are readily available. It is an alternative to manufacturing the parent item on a work order and then shipping it. There is no additional value added after getting the customer order. For Example: Computer System (CPU, Monitor and Printer) A pick to order model can have PTO option class, PTO items, ATO model, ATO Option class and ATO option items. There can not be any PTO model, PTO option class or PTO item under an ATO model. You want to manufacture a promotional laptop computer, you need laptop computer, dikettes, accessories and battery pack. Here, you define PL computer as PTO model, laptop computer as ATO model, battery pack, diskette and accessories as purchase items. Standard, model and option class Bills of material, can include bills for pick-to-order bills, Pick-to-order is also an item attribute that you can apply to standard, model, and option class items. Oracle Master Scheduling/MRP and Supply Chain Planning does not support planning for pick-to-order models and option classes. Pick to Order (PTO) items have the Pick Component attribute set to Yes. Pick-to-order bills cannot have fractional component quantities if Oracle Order Management is installed. You cannot create routings for planning or pick-to-order items. Posted by OracleOnDemand at 9:29 PM 2 comments Labels: Manufacturing Foundations, Oracle Fundamentals, SAM, VKD

What is Assemble-to-Order (ATO) Manufacturing ?

What is Assemble-to-Order (ATO) Manufacturing ? ATO simplifies the process of manufacturing finished goods. These goods are standard products and are often configured by customers from Bills of material, where you can define available options for unique product configurations. Based on forecasting, subassemblies are manufactured prior to receiving the customer order and when the order is received, the stocked subassemblies and components are

assembled to make the finished products. It is an environment where you open a final assembly order to assemble items that customers orders. It is manufacturing method/strategy which allows a product to be made or service to be available to meet the needs of a specific customer order. While producing finished goods on a large scale, this requires sophisticated planning processes which master schedules ATO models and options and then create work orders to build the unique configuration in WIP module while maintaining control of inventory, planning, cost accounting and Bills of Material. Planning process also anticipates changing demand for external or internal components or accessories and at the same time focuses on product customizations for individual customers. WIP, Order Management and Shipping modules support building and shipping of ATO configurations. A discrete job is created from a configuration. An assemble to order item/assembly then can be linked to a sales order. Assemble-to-order is also an item attribute in Inventory module that you can apply to standard, model, and option class items. In Bills of Material module, a model bill can be either assembleto-order or pick-to-order and an option class bill can be either assemble-to-order or pick-to-order. AssembletoOrder Model (ATO Configuration) is a Model bill of material with optional items and option selection rules or Configuration manufactured from mandatory components and selected options, or purchased from a supplier. An ATO model can have ATO option class, ATO Option item, PTO Option Class and PTO Option item under it. ATO Model can be a finished good or it be a part of another bills i.e it is component on another bill. Assemble-to-Order Item is a Standard bill of material with mandatory standard components or Item manufactured from mandatory standard components, or purchased from a supplier. For Example: Automobiles, computer manufacturing. Suppose you want to produce a laptop computer. Then, it requires carrying case, key board, CPU, Monitor and Operating system. While defining a bills of material for laptop computer, you can define computer as ATO Model. A Model comes at the top of the configuration hierarchy, second comes the Option Class and then the Option item. Carrying case and keyboard are purchased items under the bill of laptop. CPU, monitor and Operating system are option classes and 386 processor and 486 processor are optional items under the option class CPU. Similarly ,you can have optional item under other option classes. It is quite possible that ATO Model itself is component on another bills of material. Posted by OracleOnDemand at 9:06 PM 2 comments Labels: Manufacturing Foundations, Oracle Fundamentals, Order Management, SAM, VKD, Work in Process (WIP)

Friday, December 26, 2008

What is Assemble-to-Order(ATO) Manufacturing ?

What is Assemble-to-Order(ATO) Manufacturing ? You can define available options in Bills of Material for unique product configurations. You can master

schedule models and options and then create work orders to build these unique product configuration in WIP while maintaining control of inventory, planning and cost accounting. Bills of Material, WIP and Order Management/Shipping modules support building and shipping of ATO configurations. A discrete job is created from a configuration or an assemble to order item and then can be linked to a sales order. Posted by OracleOnDemand at 11:32 PM 0 comments Labels: Manufacturing Foundations, Oracle Fundamentals, SAM, VKD, Work in Process (WIP)

What is Flow Manufacturing ?

What is Flow Manufacturing ? Flow Manufacturing is an innovative manufacturing method which synchronizes production with customer demand. The characteristics of flow processes are: a) Straight and short product flow patterns b) Make to order strategy c) Single-piece production d) Just-In-Time materials/pull/dependent demand scheduling e) Short production cycle times f) Highly flexible and responsive processes g) Highly flexible machines and equipment h) Quick changeover i) Continuous flow work cells j) Compressed space k) Multi-skilled employees l) Empowered employees m) High first inspection - pass yields with major reductions in defects Oracle Flow Manufacturing module supports the entire build-to-order manufacturing process which includes make-to-stock, configure-to-order, discrete-repetitive, assemble-to-order, and engineer-toorder manufacturing strategies and methods. It initiates schedules as soon as customer orders are received, and ensures shipment as soon as build is complete. Flow manufacturing employs pulls material using kanbans planning and backflushes material and costs upon completion. This in turn helps decrease inventories, optimize machine utilization, reduce response time to customer orders, and simplify shop floor activities. Flow manufacturing production lines are designed to support the inter-mixed production of multiple products within a family on the same line at a constant rate. It can be used in Inventory module to

replenish kanbans and in Work in Process to complete assemblies without having to create a job or a schedule (work order less job) Posted by OracleOnDemand at 11:10 PM 1 comments Labels: Manufacturing Foundations, Oracle Fundamentals, SAM, VKD, Work in Process (WIP)

What is Project Manufacturing ?

What is Project Manufacturing ? Large contracts or projects received by the companies can not be completely fulfilled by process manufacturing or disrete or repetitive manufacturing methods. It requires a separate manufacturing method known as project manufacturing. Project manufacturing meets demand driven production requirements for large contracts or projects. It allows you to plan, schedule, process and cost against a specific contract or a group of contracts or project for a specific customer. Oracle Project Manufacturing supports companies in the Engineer-To-Order, Make-To-Order manufacturing strategies and Aerospace and Defense industries. These industries plan, track, procure, and cost based on project, contract, or Seiban numbers. If Oracle Projects is installed and the Project References Enabled and Project Control Level parameters are set in the Organization Parameters window in Inventory module, you can assign project and, if required, task references to planned orders, jobs, purchase orders, sales orders, miscellaneous transaction and other entities within Oracle Manufacturing. If the Project Cost Collection Enabled parameter is also set in inventory organization parameters, you can optionally collect and transfer manufacturing cost to Oracle Projects module. Project costs are tracked by project/task and expenditure type. Posted by OracleOnDemand at 11:00 PM 0 comments Labels: Manufacturing Foundations, Oracle Fundamentals, Projects, SAM, VKD, Work in Process (WIP)

Thursday, December 18, 2008

What is Process Manufacturing?

What is Process Manufacturing? Process manufacturing is different from Discrete manufacturing. Manufacturing is not in discrete batches but is a process of pressing/mixing/chemical processing/heating/boiling liquid/semi liquid/solid and powder or raw materials. Once you manufacture a product by using process manufacturing, the output can not be brought to it's original basic form. For example orange juice with sugar added cannot be put back in to the Orange and Sugar seperately. On the other hand a computer manufactured by a discrete manufacturing process can be disassembled and the parts can be returned to stock to a large extent. Examples of process manufacturing are food products, beverages, paints & coatings, chemicals, specialty chemicals , pharmaceuticals, consumer packaged goods, Bulk drug pharmaceuticals, Nutraceutical, cosmeceutical and biotechnology industries. In Process Manufacturing, there are ingredients and not parts; there are formulas and not bill of materials; and bulk, not Unit of measure Each For original post, please visit http://applearn.blogspot.com Posted by OracleOnDemand at 12:51 AM 0 comments Labels: Interview Questions, Manufacturing Foundations, Most Asked Questions (MAQs), Oracle Fundamentals, SAM, VKD, Work in Process (WIP)

Sunday, December 14, 2008

Different manufacturing strategies

Which are different manufacturing strategies? There are 4 manufacturing strategies a) Make to stock(MTS)

b) Make to Order(MTO) c) Assemble to Order(ATO) d) Engineer to order(ETO) In MTS, stock is created by companies for items without receiving an order from customer. Examples are manufacturing of refrigerators, washing nachines and Television sets. They are manufactured in a flow shop based on master schedule and stocked in finished goods subinventory until they are shipped to a cutomer. MTO are manufactured after receiving customer order, which means customer is willing to accept longer delivery period. The examples are commercial dish washers and refrigerators for hotels. These items are produced in a flow shop or in job shop depending up on the range of product families produced by the factory. In order to reduce lead time the factory often uses ready components to manufacture a product. In ATO, stock of existing items is kept on hand but they are sub assemblies, not the finished product. The company uses final assembly orders to put the finished product together according to specifications of the customer order. This involves some extra lead time but not as much as MTO. Private aircrafts, commercial trucks and computers are the examples of ATO. ATO items may be produced either in flow shop or job shop. ATO offers many variations in standard product because of the choices the customers have in deciding final product from options provided . ETO item is built on the customer product specifications such as large commercial aircrafts. Such product can not be produces according to existing specifications of the company because some engineering skill is required to incorporate customer specifications in to the design of the final product. Companies using this manufacturing strategy, always quote longer lead time .The engineering and manufacturing costs involved are also high and are tracked for each order separately. Posted by OracleOnDemand at 11:59 AM 1 comments Labels: Interview Questions, Manufacturing Foundations, Most Asked Questions (MAQs), Oracle Fundamentals, SAM, VKD, Work in Process (WIP)

Saturday, December 13, 2008

What is Discrete Manufacturing?

What is Discrete Manufacturing? 1) Discrete manufacturing is a manufacturing process in which distinct items/products(which you can easily count, see and touch) are built or manufactured in discrete batches on manufacturing floor. It creates physical products which go directly to business and consumers, and assemblies that are used by other manufacturers. The resulting product is easily identifiable. It is different from process

manufacturing where products are undifferentiated (can not tell the difference between one product and another) such as oil, natural gas and salt. 2) A typical characteristic of discrete manufacturing is the frequent switching from one manufactured product to another. The products are typically manufactured in individually defined lots, the sequence of work centers through production varying for each one of these. Costs are calculated on the basis of orders and individual lots. 3) Discrete manufacturing is also characterized by individual or separate unit production. Units can be produced in low volume with very high complexity or high volumes of low complexity. Low volume/high complexity production results in the need for an extremely flexible manufacturing system that can improve quality and time-to-market speed while cutting costs. High volume/low complexity production puts high premiums on inventory controls, lead times and reducing or limiting materials costs and waste 4) Discrete manufacturing typically involves the sequence of work centers through which the products can pass during production. This sequence can be varied as per requirement. The order of work centers is determined in routings, which can often be very complex. There can be waiting times between the individual work centers. Also, semi-finished products are frequently placed in interim storage prior to further processing 5) In discrete manufacturing, component materials are staged with specific reference to the individual production lots. Completion confirmations for the various steps and processes document the work progress and enable fine-tune controlling. Examples are Transportation equipment, Automobiles, toys, Computer and accessories and electronic products, consumer electronics, furniture, Lego Blocks, Appliances and other house hold items, Industrial and electrical equipment, Medical equipment and supplies, Fabricated metal, furniture, recycling, pencil ,light bulb, telephone, bicycle, fuel pump, miscellaneous manufacturing as well as "big ticket consumer and commercial goods like cars and airplanes, semi conductors, outfitting with industrial products, machine and plant engineering, right through to shipbuilding and aircraft construction. Fabricating products by assembling components and subsystems into larger systems. The automated assembly line is the prime example of discrete manufacturing such as in the making of automobiles, household appliances and computer systems. Discrete manufacturing systems typically deal with digital inputs to programmable logic controllers (PLCs) and programmable automation controllers (PACs) that cause motors and robotic devices to be activated. Fabricated Metal Products, Industrial and Commercial Machinery. Posted by OracleOnDemand at 10:44 AM 0 comments Labels: Interview Questions, Manufacturing Foundations, Most Asked Questions (MAQs), Oracle Fundamentals, SAM, VKD, Work in Process (WIP)

Monday, April 14, 2008

Form Personalization
Most of the customers wish to modify the way the forms look and behave. They want to change the labels on the form fields, hide fields, hide buttons, amend custom logic. With the Oracle E-Business Suite release 11.5.10, Oracle has introduced a mechanism which revolutionizes the way the forms can be customized to fulfill the customer needs. For many years, Oracle Applications has provided a custom library using which the look and behavior of the standard forms can be altered, but the custom library modifications require extensive work on SQL and PL/SQL. In the release 11.5.10, Oracle has provided a simple and easy feature to implement the customer specific requirements without modifying the underlying forms code or CUSTOM library. Although CUSTOM library still can be used for forms customization to implement the complex business logic, the personalization feature provided in the latest release is easy, faster and requires minimum development effort The personalization form is invoked by Menu Navigation as below Help --> Diagnostics --> Custom Code --> Personalize By default, this menu option is enabled when any of the standard forms are opened, but at other times this menu option is disabled. The personalization form cannot be opened when the user is on the responsibility navigator. This means the specific form should be opened first, then invoke the Personalization form using the above navigation. Then define the personalization rules and actions on the personalization form, validate and apply them which automatically add the custom rules to the underlying specific form. For example, if the specific form is Sales Order; Open the Sales Order form first, and then invoke the Personalization Form using the menu option By default the Personalize menu is visible to all the users; this can be controlled with help of profile options. By setting up the below profile options, the access to the Personalize menu can be limited for the authorized users. This will prevent unauthorized users from changing the look and behavior of the forms. The profile options are 1) Utilities: Diagnostics = Yes/No 2) Hide Diagnostics = Yes/No Posted by OracleOnDemand at 11:38 PM 0 comments Labels: Oracle Fundamentals, SAM, Technical

Saturday, December 22, 2007

DESCRIPTIVE FLEXFIELDS (DFF)

DESCRIPTIVE FLEXFIELDS (DFF) DFF provide customiszable expansion space to capture information which otherwise is not captured by the standard application. Gives you the flexibility to satify different group of users without having to reprogram the application. DFF can be context sensitive where the information your application stores depends on other values your users enter in other parts of the form. Each DFF has a name you assign. You can specify valid segment values or setup criteria to validate the entry of any value. DFF is made up of subfields and appears in a pop-up window on the form. DFF are implemented as a set of database columns with one column for each segment. The brackets [ ] indicate the presence of a DFF. When the cursor reaches the brackets the DFF pops open. DFF can be enabled and disabled - hence it only pops open when it is in enabled mode. Posted by OracleOnDemand at 10:28 PM 1 comments Labels: Oracle Fundamentals, SAM

Friday, December 21, 2007

Flexfields
As the name suggests, flexfield is a "flexible field". Flexfield is a field made up of multiple segments which are actually table columns. Each segment has a name that can be assigned and a set of valid values. There are 2 types of flexfields in Oracle Applications namely "Key flexfield" (KFF) and descriptive flexfield (DFF) Using KFF and DFF, Oracle gives enormous amount of flexibility to customers to customize (or rather I may call it configuring) to match the different business needs without the need for programming. Flexfields provide the flexibility to implement code structure and capture additional information. KEY FLEXFIELDS (KFF) KFF represents an 'intelligent key' that uniquely identifies an application entity. Each KFF segment has a name you assign and a set of valid values you can specify. Each value has a meaning which can be again specified. KFF provides with a flexible 'code' data structure that users can setup in whichever way they like to use the KFF segments. As mentioned, for each segment one can also define valid values for each segment as well as cross-validation rules to describe valid segment combinations.

Oracle General Ledger Accounting flexfield is an example of a KFF used to uniquely identify a General Ledger account. Another example of KFF would be Item flexfield in Oracle Inventory - its used to uniquely identify inventory items. It could contain segments such as product class, product code, size, color and packaging code. You could valid values for the color segment - for example a user can enter only from a range of "01" to "10" (where "01" meand red and "02" means blue and so on). Cross validation rules can also be applied to validate combination of segment values entered by the user. For example, take an example of shirt - if a user select "01" in color code (which means red color), size can be only "40" and "42" and not "44". This is because business has red color shirts available in size "40" and "42" only. Flexfield segments are usually validated against a set of valid values - called as value set. Oracle Applications provide a couple of seeded Key flexfields. Watch out for the next post on Descriptive Flexfields (DFF). If you wish to receive an email whenever that is posted, drop a email on oracleondemand@gmail.com. Posted by OracleOnDemand at 2:42 PM 0 comments Labels: Oracle Fundamentals, SAM

Wednesday, December 19, 2007

Multi-Organization (Multiorg) feature in Oracle Applications

Oracle Applications 11i has a feature called Multi-Organization (popularly called Multiorg), what brought a lot of benefits for customers which has multiple business units. Using the Multi-Organization feature, this kind of company will need only one single instance to support its business, keeping transactions data separate and secure. This model allows you to support any number of business units on a single instance of any Oracle Applications product, even if those business units use different Set of Books. We can define different

structures using Multiorg feature to suit the business needs Couple of basics business needs that need the multiorg functionality are... 1) Use a single installation of Oracle Applications product to support any number of organization 2) Sell products from a legal entity which uses one set of books and, ship them from another legal entity using a different set of books 2) Purchase products through one legal entity and receive them in another legal entity 3) Support any number of legal entities within a single installation of Oracle Applications. 4) Secure access to data, so users can access only the information that is relevant to This structure is the first definition that has to be done when implementing Oracle E-Business suite. It has to be done carefully, since it is not possible to change after it is defined in the system ! Posted by OracleOnDemand at 12:07 AM 0 comments Labels: Oracle Fundamentals, SAM Newer Posts Older Posts