Posts

Showing posts with the label Oracle Inventory

Oracle Item catalog

Image
Item  Catalog ITEM CATALOG Item Catalog is a flex field , which is used to define descriptive elements for Items . Use of Item catalog in Oracle Inventory is to Group items that share commoncharacteristics. In order to define catalog, we can setup distinct catalog groups to partition the Item master. Each catalog group in turn has a set of unique characteristics called as Descriptive element that describe item belonging to the Group. Oracle Inventory provides item catalogs to help you quickly locate items based on key characteristics. For Example: We can define a new catalog group called Two-Wheeler. We can assign descriptive elements of Engine capacity, power and color to the catalog group. In Master Item Screen create an item ‘ABC’ to the group Two-Wheeler. We can choose values for each of descriptive elements such as 150CC, 11 BHP and Black or 100CC, 85BHP and Yellow. Now we can refer to the item by both unique item number ‘ABC’ or by the Two-Wheeler catalog (150CC, 11 BHP, B...

Phantom Assembly

What exactly is a Phantom item or Assembly means? Can anyone plese tell me what exactly is a phantom item or assembly means?  How does it affect the MRP process?  Phantom Supply Type (what Oracle says) • Phantom components can be assigned to bill of material component subassemblies and subassembly items in Oracle Bills of Material and Oracle Engineering. Components of phantom subassemblies are used as if they were tied directly to the parent assembly. Phantom supply types cannot be assigned to jobs and repetitive lines/assembly associations in Work in Process. See: Phantoms. • Phantoms behave normally when they are top level assemblies, such as when master scheduled or manufactured on a discrete job. As subassemblies, they lose their distinct identity and become a collection of their components. Phantom components (not the phantom itself) are included on discrete jobs and repetitive schedules and are listed on the Discrete Job and Repetitive Schedule Pick List Rep...

FAQ: Sales Order Processing within Inventory / Drop Ship Transactions Hungup In Transaction Open Interface

How do SO Lines flow into inventory? Two separate flows are used depending if you perform a Pick release or Sales Order Issue.  For pick release, the pick list generation program creates a move order for the order line.  When the move order is "allocated", it inserts a record into the pending transaction table (MTL_MATERIAL_TRANSACTIONS_TEMP).  When the move order is transacted, the record is moved to the transaction history table (MTL_MATERIAL_TRANSACTIONS).  For sales order issues, the ship confirm / trip stop process sends information to inventory through the transaction open interface table (MTL_TRANSACTIONS_INTERFACE). The ship confirm process then runs the inventory transaction worker -- depending on the profile "WSH: Defer Inventory Process Online" -- see later questions.  The inventory transaction worker validates the data inserting it into the pending transaction table (MTL_MATERIAL_TRANSACTIONS_TEMP), then into the transaction history table (MT...

FAQ: Unprocessed Transactions / Closing Inventory Accounting Period

What is the MTL_TRANSACTIONS_INTERFACE table used for? This is the Interface between non-Inventory applications and the Inventory Transactions module. In other words any other module other than Inventory that wants to update Inventory has to come through this table. Modules such as WIP (Work In Progress) and OE (Order Entry) first pass their records to the MTL_TRANSACTIONS_INTERFACE (MTI) for validation. The Transactions Manager (INCTCM) reads records from the MTI table, validates them and moves the successful transactions into the MTL_MATERIAL_TRANSACTIONS_TEMP table, and submits Transaction workers (sub-processes - INCTCW) which then process these records through inventory. This process consists of data derivation, validation, and the transfer of records from MTL_TRANSCTIONS_INTERFACE, MTL_TRANSACTIONS_LOTS_INTERFACE and MTL_SERIAL_NUMBERS_INTERFACE into their associated TEMP (temporary) tables from where the transactions processor processes them. Both the Lots and Serial number t...

Min Max Planning

PURPOSE This document is meant to assist in the successful completion of the Min-Max Planning Report  SCOPE & APPLICATION The intended use of this document is for the casual user beginning to use the Min-Max Planning feature of Oracle Inventory. MIN MAX PLANNING & REPORT Min-Max planning is a type of order point replenishment system where the minimum is the order point, and the maximum is the "order up to" inventory level. The order quantity is variable and is the result of maximum minus available and on-order inventory. An order is recommended when the sum of the available and the on-order inventory is at or below the minimum. Oracle Inventory enables you to perform min-max planning at two levels: A. Organization B. Subinventory To perform organization-level min-max planning for an item, you must specify organization-level minimum and maximum quantities. To perform subinventory-level min-max planning for an item, you ...

Material Status, Onhand Status and Item Status in Oracle Inventory

What is Material Status? Material Status control restricts the movement and usage of portions of on-hand inventory. Using material status control enables you to control whether you can pick or ship an internal order or sales order, or issue material for a work order. You can also specify whether material needs to be quarantined until you inspect it. In addition, you can determine whether products with a particular status can be reserved, included in available to promise calculations, or netted in production planning. You assign material statuses at four levels: subinventory, locator, lot, and serial. You assign subinventory and locator statuses in the subinventory and locator windows. The location status applies to the material in the location and not the location itself. To assign a material status to a lot or serial, you must first enable the item attributes Lot Status Enabled, and Serial Status enabled on the item in the Item Master. You can also optionally assign a defa...

Period End Closing Checklist in Oracle in R12

Product family Product Code Step number Step name 1 Order Management (OM): Order Management ONT 1.1 Complete the sales orders Order Management ONT 1.2 Import Sales Order Order Management ONT 1.3 Pre-Billing Acceptance Shipping WSH 1.4 Complete the shipping transactions Order Management ONT 1.5 Prepare the link with AR Order Management ONT 1.5.1 Check run of Workflow background engine Receivables AR 1.5.2 Run the Invoice Interface/Autoinvoice Receivables AR 1.5.3 Verify the Autoinvoice Exceptions 2 Receivables (AR): Receivables AR 2.1 Complete all Receivables transactions for the period being clos...