Oracle Inventory Training.

Discussing Inventory Structure Describing Inventory Major Features and Functions Identifying Major Tables Used in Oracle Inventory Reading Oracle Inventory ERDs Discussing Open Interfaces and !Is for Oracle Inventory Discussing Inventory Structure

What is inventory? In simple terms it is a stock of items that your business is selling in order to make a living. Almost every non-IT related business has some physical items to sell and hence Inventory is at the heart of almost any business and is central to the planning process. The considerations in setting it up are at least as complex as those for any other single application. Commonly Inventory !ill be installed during the implementation of "rder #ntry $urchasing %anufacturing or &upply Chain %anagement but it is an extremely complex module in its o!n right !ith several important setup considerations. Inventory System: The simplest function of an Inventory system is to keep track of your items i.e. !hich item came in and !hich item !ent out of inventory and !hen the item count reaches belo! a certain threshold value then alert the responsible person to replenish it soon. &o ho! does items go in and out of the !arehouse? 'et say your company manufactures office chairs. When a customer orders ( chairs and !hen you ship them to the customer the count of the item goes do!n and !hen you manufacture them internally and !hen the finished chair is ready and moved to the !arehouse the item count increases. An item can be internally consumed too. An inventory system provides physical management of a company)s stock until it is either used up or sold. It also performs a logical cataloging function. This stock is referred to by its item number* +usually item number is the segment, column of mtl_system_items- and has many attributes that affect the transactions that the modules can process against the item. #very other module !ithin "racle Applications that needs to name types of ob.ects looks to the Inventory Item %aster for details regarding an item. These ob.ects

include products ordered through "racle "rder #ntry items invoiced through "racle /eceivables items purchased through "racle $urchasing items paid for through "racle $ayables items maintained through "racle &ervice and items charged against pro.ects in "racle $ro.ects. #very module in the %anufacturing suite +#ngineering 0ills of %aterial Work in $rocess * %aster $roduction &chedule1%aterial /e2uirements $lanning and Cost %anagement- deals !ith items named in Inventory. Inventory)s can also track intangibles like maga3ine subscriptions. The company can sell these items along !ith physical ob.ects. Assemblies that are never stocked can also be defined in Inventory. A phantom item for example represents an intermediate step in manufacture an assembly that is never stocked in inventory because it is used immediately in a higher-level assembly. "racle Inventory)s on-hand balance is increased !hen an item is bought or made. Inventory relin2uishes control and decreases its balance !hen items are sold or put to their final use !ithin the company. $ads of paper in the stock room are inventory4 the same pad of paper on somebody)s desk is not-as far as the company is concerned it is already used. A ne! desk in the !arehouse belongs to inventory4 a desk in somebody)s office is no longer in inventory. %any ma.or purchases such as plant and e2uipment never have an on-hand balance because they are put to their final use as soon as they are bought.

Oracle Inventory system

Inventory Organizations
n Inventory organi"ation may be one of the following# $ p%ysical entity li&e a 'are%ouse '%ere inventory is stored and transacted. $ logical entity li&e an ite( (aster organi"ation '%ic% only %olds ite(s 'it% no Transactions n inventory organi"ation (ay %ave t%e following attributes $ n inventory organi"ation can %ave its o'n location 'it% a set of boo&s) a costing (et%od)a 'or&day calendar) and a list of ite(s. $ n inventory organi"ation can s%are one or (ore of t%ese c%aracteristics 'it% ot%er organi"ations.

Sets of Books *ou can tie one Oracle +eneral ,edger set of boo&s to eac% inventory organi"ation. Costing Methods *ou c%oose your costing (et%od at t%e organi"ational level. T%e ite( attribute control level deter(ines t%e costing organi"ation. Item Costs Oracle Inventory &eeps one standard cost per ite( per inventory organi"ation. Movement Between Inventory Organizations *ou can use intransit inventory for interorgani"ation transfers. Planning Method *ou can perfor( reorder point planning at t%e organi"ational level) and you can perfor( (in(a- planning at bot% t%e organi"ation and subinventory level. In Multi-Org *ou can tie one govern(ent reporting entity.legal entity to eac% inventory organi"ation. *ou can also tie one operating unit to eac% inventory organi"ation.

orecasting Oracle Inventory forecasts ite( usage at t%e organi"ation level only. !ccuracy !nalysis *ou can perfor( a p%ysical inventory) /0 classifications) and cycle counting at bot% t%e organi"ation and subinventory levels.

Flow of any manufacturing company: 1) Raw material flow into manufacturing company. 2) Raw material gets processed according to requirement. 3) Finally finished goods are distributed to end consumers through physical distribution system. For this different companies use different manufacturing strategies, according to their business need and their requirement and they are,

Manufacturing Strategies Ma e! to!stoc "n this deli#ery time is equal to shipment time, generally you will maintain stoc . Ma e! to!order "n ma e!to!order deli#ery time is manufacturing $ assembly time $ shipment time. %ssemble! to! order "n this strategy assembly time and shipment time contributes to deli#ery time. &ngineer! to! order! "n this special category order processing starts from design, manufacturing, assembly and shipment. Materials Management %ny strategy company implements, there comes material management, for following benefits 1) For planning and controlling materials flow 2) Ma'imi(e use of firm)s resources 3) *ro#ide required le#el of customer ser#ice For this material management we will control these acti#ities Activities *roduction *lanning+ ,he company will plan production according requirement and according to that the status of in#entory is chec ed. "mplementation of planning - control+ *roduction planning should be implemented and control through proper resources, mainly in#ol#ed purchasing. "n#entory management+ %s per planning in#entory should be managed, that #ary from raw material to finished goods. Modules .ifferent modules which are interrelated with "n#entory - *urchasing. / M*0 1 Manufacturing *lanning - 0ontrol / M*2 1 Master *roduction 2chedule / MR* 1 Materials Required *lanning / 34M 1 3ill 4f Material Relation with ma5or modules *roduction *lanning Master production schedule &ngg. 34M MR* *urchasing "n#entory *roduction control *roduction planning is done by eeping long term #iew, while on that basis master production schedule is created. MR* will ta e feedbac 34M, &ngg. other modules. *urchasing will wor according to MR* for which status will

pro#ide by "n#entory. 2o now we can #isuali(e the position of purchasing in#entory in whole manufacturing organi(ation. 4ther Manufacturing modules which are inter!related are, / 4racle 34M 6 bill of material) / 4racle &ngineering / 4racle *roduct 0onfigurator / 4racle MR* / 7"*6 7or "n *rocess) / 0ost management / 4racle quality "n#entory "n "n#entory all ma5or functions are related with items, all functionality is pro#ided by eeping item as center. 8ow we will discuss #arious aspects of in#entory and flow of "n#entory. "n#entory consists of, mainly 1. Raw material 2. 7or "n *rocess "n#entory 3. Finished 9oods Functions of in#entory 1. Maintaining stoc 2. *lanning 3. Forecasting :. *hysical control of in#entory ;. Receipt <. "ssues 7e will discuss these functions as regards with oracle applications. Inventory Flexfields ,he fle'fields which are used in in#entory are+

/ %ccount aliases / "tem catalogs / "tem categories / 2ales orders / 2toc locators / 2ystem items .epending on your setup in#entory can use other modules fle'fields li e %ccounting 69eneral =edger) - 2ales ta' location - territory from %ccounts Recei#ables Account Aliases ,able name + M,=>9&8&R"0>."2*42","482 %n account alias is an easily recogni(ed name or label representing a general ledger account number. ?ou can #iew, report, and reser#e against an account alias. .uring a transaction, you can use the account alias instead of an account number to refer to the account. Item catalogs ,able name+ M,=>",&M>0%,%=49>9R4@*2 @nique ". column+ ",&M>0%,%=49>9R4@*>". "f you ma e entries for your items in a standard industry catalog or want to group your items according to certain descripti#e elements, you need to configure your "tem 0atalog 9roup Fle'field. &#en if you do not use item cataloging, you must enable at least one segment and compile this fle'fields before you can define items. ,hese fle'fields supports only one structure and dynamic inserts is not allowed.
Item categories

,able name+ M,=>0%,&94R"&2 @nique ". 0olumn+ 0%,&94R?>". ?ou must define - configure your item categories fle'fields before you can start defining items since all items must be assigned to categories. ?ou can

define multiple structures from different category groups. 2o that you can associate these structures with categories - category sets. Sales order ,able name+ M,=>2%=&2>4R.&R2 @nique ". 0olumn+ 2%=&2>4R.&R>". ,hrough this fle'field in#entory will identify sales order transactions of 4M with in#entory. ,his sales order fle'field should be defined as order number, order type and order source so that each transaction will be unique in in#entory.
Stock locators

,able name+ M,=>",&M>=40%,"482 @nique ". 0olumn+ "8A&8,4R?>=40%,"48>". "f you eep trac of specific locators such as aisle, row, bin indicators for your items, you need to configure your 2toc =ocators Fle'field and implement locator control in your organi(ation. ?ou can use stoc locators field to capture more information about stoc locators in in#entory. "f you do not ha#e oracle in#entory installed any none of items ha#e locator control then it is not necessary to define this fle'field. %nd this fle'field supports only one structure.
System items (item flexfield)

,able name+ M,=>2?2,&M>",&M2 %nd unique id column is "8A&8,4R?>",&M>". ?ou can use item fle'field for recording and reporting your item information, and you must define and configure your item fle'field before you can start defining items. ?ou must plan how 4racle "n#entory represents your company)s in#entory sites and business units. ,his includes defining organi(ations, locations, subin#entories, and locators depending on your company structure. "n#entory is consisting of in#entory 1 subin#entory !locators as per your organi(ation setup. ",&M is defined in in#entory that is generally first in master organi(ation, so that later it can be assign to multiple organi(ations. %lso item definition can be uploaded by item upload open interface.

",&M definition

?ou define items in one organi(ation. ,o distinguish it from others, we call it the "tem Master organi(ation. 4ther organi(ations 6child organi(ations) refer to the "tem Master for item definition. %fter you define an item in the "tem Master, you can assign it to any number of other organi(ations. "tem attributes

/ / / / / / /

"n#entory attributes li e lot controlB serial control *urchasing and costing information. bill of materialB item category attributes *hysical attributes li e weight, #olume Recei#ing attributes 9eneral planning attributes li e min!ma' qty, order qty. 2tatus of item

9enerally we will group the item attributes in these groups Main "n#entory 3ill of material %sset management 0osting *urchasing Recei#ing *hysical attributes 9eneral planning M*2BMR* planning =ead times 7or "n *rocess 4rder Management "n#oicing 2er#ice 8ow we will discuss main attributes from ma5or group. Main attribute group
Primary nit of Measure!

,his is the stoc ing and selling unit of measure. %ny necessary con#ersions are based on this unit of measure. ,his attribute is not updatable. ,he default primary unit of measure for new items is defined using the "8A+ .efault *rimary @nit of Measure profile option.
ser Item "ype!

4racle pro#ides se#eral types by default at installation. ,hese types correspond to the item templates also pro#ided. 2elect one of these #alues, or one you defined with the "tem ,ype window. .ifferent item types are %,4 modelB Finished goodB FreightB "n#entory ,ype etc.
Item Status!

"tem status codes set or default the #alues for attributes under status control. @ser1defined status codes control certain item attributes designated as status attributes. "tem status can be acti#eBengineerBinacti#e. ,he default item status for new items is defined using the "8A+.efault "tem 2tatus profile option. Inventory Attri#ute $roup "n#entory "tem!"ndicate whether to stoc and transact this item in 4racle "n#entory. 2toc able!"ndicate whether to stoc this item in "n#entory. ?ou can set this attribute only when you turn on the "n#entory "tem option. ,ransactable 1 "ndicate whether to allow "n#entory transactions. ?ou can set this attribute only when you turn on the 2toc able option.

Reser#able!"ndicate whether you can create material reser#ations. ?ou can reser#e an item only when you ha#e sufficient in#entory. 4ther attribute in this group are =ot control, serial control, locator control. %ill of Material attri#ute group 34M allowed!%llows you to define a bill of material for an item, or to assign the item as a component on a bill. 34M item type!,his attribute is controlled at the Master le#el only. 2elect a type to control bill functionality. ?ou must enter a #alue here if 34M %llowed is turned on.
Asset management attri#ute group

,hese are the attributes you ha#e to gi#e for asset management. %sset item type!,his attribute identifies the asset item as an %sset 9roup, %sset %cti#ity, or Rebuildable item. %cti#ity type!,his is rele#ant when the %sset "tem ,ype is set to %sset %cti#ity. ,his indicates the type of maintenance for this asset acti#ity.
&osting attri#ute group

?ou ha#e to set these attributes while defining or updating items. 0osting enabled! "ndicate whether to report, #alue, and account for any item costs. "n#entory asset #alue!"ndicate whether to #alue an item as an asset in in#entory. ,urning this option off indicates an e'pense item. 0ost of goods sold account! ,his attribute is controlled at the 4rgani(ation le#el only. &nter a general ledger account to use as a source for the 0ost of 9oods 2old %ccount. ,he default cost of goods sold account is set when you define organi(ation parameters. Purc'asing attri#ute group *urchased! "ndicate whether to purchase and recei#e an item. ,urning this option on allows you to set the *urchasable attribute. *urchasable!"ndicate whether to order an item on a purchase order. ?ou can set this only when *urchased is turned on. Receipt required! "ndicate whether you must recei#e an item before you can pay the in#oice. =ea#e this field blan if you want "n#entory to use the #alue defined in the *urchasing 4ptions window for transactions in#ol#ing this item. i.e. three way in#oice matching "nspection required! "ndicate whether to inspect an item upon receipt from the supplier, before paying the corresponding in#oice. =ea#e this field blan if you want "n#entory to use the #alue defined in the *urchasing 4ptions window for transactions in#ol#ing this

item. &ncumbrance account! ,his attribute is controlled at the 4rgani(ation le#el only. &nter the default encumbrance account 4racle *urchasing uses when an item is recei#ed. "f the item encumbrance account does not e'ist, 4racle *urchasing uses the sub in#entory account. &'pense account! ,his attribute is controlled at the 4rgani(ation le#el only. &nter the default in#entory account for e'pense items. ,his attribute is used only when "n#entory %sset Aalue is turned off. 4racle *urchasing debits this account when you recei#e an item into in#entory only if the item is being e'pensed. "f you recei#e into an e'pense subin#entory, 4racle *urchasing uses the e'pense account you assigned to the subin#entory firstC if you do not define the account here, 4racle *urchasing uses the e'pense account assigned to the item. Recei#ing attribute group "n this group ma5or attributes are receipt date controls, #alid transactions and o#er!receipt quantity control. P'ysical attri#ute group ,he main attributes li e weight, #olume, and dimension are shown below, $eneral planning attri#utes "n#entory planning method!Dere you can select option for organi(ational le#el planning. =i e not planned, min!ma' or recorder point. For min!ma' quantity, order quantity and source. For source you can gi#e in#entory, subin#entory or supplier. (rder Management attri#ute group 0ustomer ordered!"ndicate whether to allow an item to be ordered by e'ternal customers. ?ou can add any customer orderable items to price lists in 4racle 4rder Management. 2hippable!"ndicate whether to ship an item to a customer. 2hippable items are released by 4racle 2hipping &'ecution)s *ic Release program, creating confirmable shipping lines, and are printed on the pic slip. .efault shipping organi(ation!&nter the 4racle 2hipping &'ecution primary shipping organi(ation. *ic ing rule!&nter the pic ing rule that defines the order in which subin#entories, locators, lots, and re#isions are pic ed. Invoicing attri#ute group "n#oicable item!"ndicate whether to include an item on an 4racle Recei#ables in#oice. %ccounting rule!&nter an accounting rule to identify special re#enue

recognition rules for an item, such as recogni(ing re#enue o#er time. "n#oicing rule!&nter an in#oicing rule to determine the period in which you send an in#oice when you recogni(e re#enue o#er time 6using accounting rules). 2ales account!,his attribute is controlled at the 4rgani(ation le#el only. &nter the general ledger account 4racle Recei#ables uses to record re#enue when you bill the customer. "f %uto!%ccounting is based on items, accounting entries are created at that time.
Item templates

,here are two types of templates. *redefined or custom template. *redefined templates are planning item, purchased, outside processing item, lease item. 2o that once you assign any template, to new item then all default characters are assign to new item. &ategory set ) category 0ategories are logical grouping of items that ha#e similar characteri(es, and a category set is a distinct category grouping scheme and consist of categories. .ifferent category set accordingly to company need and reporting structure. @se+ For forecasting - summari(ing history of that category. ,o eep easy trac on that category. .efine category sets .efine categories 2pecify default category sets %ssign categories to an item ,ables are related as, for item categories M,=>",&M>0%,&94R"&2 M,=>2?2,&M>",&M2>3 M,=>0%,&94R?>2&,>A%=".>0%,2 M,=>0%,&94R?>2&,2>3 M,=>0%,&94R"&2>3
nit of Measure

4racle %pplications products pro#ide powerful methods for defining and manipulating units of measure. ?ou can easily con#ert between the units you define. ,his allows you to manufacture, order, or recei#e items in any unit of measure. ,able is related as+ M,=>@8",2>4F>M&%2@R&>,= M,=>@4M>048A&R2"482 M,=>2?2,&M>",&M2>3 "tem setup

,he main tables that are in#ol#ed in item master set up are with their relation, M,=>2?2,&M>",&M2>3 M,=>",&M>2,%,@2 M,=>",&M>,&M*=%,&2 M,=>*%R%M&,&R2 M,=>",&M>%,,R"3@,&2 "tem relationship ?ou can define item relationship between items. ,his allows you to search items through these relationships and for maintaining also. / "tem cross reference @se the 0ustomer "tem 0ross References window to define and update cross references between your in#entory items and the customer item numbers defined in the 0ustomer "tems 2ummaryB.etail windows. M,=>",&M>,&M*=>%,,R"3@,&2 / 2ubstitute items "n this relationship you can replace the outdated item, still eeping trac on it. / Related items ?ou can relate different items according to your need. / Manufacturer part no. ?ou can define manufacturer part numbers for items. ?ou can use this information for reporting purposesC and in catalog searches for particular items. Inventory control / =ocator control ?ou will trac item as locator wise, it is a common method of in#entory control. / Re#ision 0ontrol 7ith different re#ision of items according to your need, re#ision control can be "mplemented. / =ot 0ontrol ?ou will define lot of your items so that you can trac that item according to their lot numbers. / 2erial no. 0ontrol For e'pensi#e or for which you want tight control you will gi#e serial numbers to those items. "tem catalog @sed to partition items that share some common characteristics.
Item "ransaction

7"* 2uppliers "8A "n# customers "n#entory can interact or can ha#e transactions with suppliers, customers, wor in process and with other sub in#entories. % transaction type is the combination of a transaction source type and a transaction action. "t is used to classify a particular transaction for reporting and querying purposes. 4racle "n#entory also uses transaction types to identify certain transactions For e'ample, transaction type is purchase order receipt which is a combination of transaction action i.e. receipt into stores and transaction source type is

purchase type. Ma5or transactions are, Su#!Inventory transfer &ach subin#entory transfer is carried out as two separate transactions, creating two records in M,=>M%,&R"%=>,R%82%0,"482. ,he first record represents an issue from the source subin#entory and the second record is a receipt from the destination subin#entory. Inter! organi*ation transfer @se the "nter14rgani(ation 2hipping 8etwor window to define accounting information and the relationships that e'ist between shipping and destination organi(ations. ?ou can specify whether an organi(ation is a shipping organi(ation, a destination organi(ation, or both. "n these transactions you will need bills, shipping bills and other accounting details. A%& Analysis ) cycle counting %30 analysis is a method of determining relati#e #alue of items in your "n#entory sites. %utomatically scheduled or manually scheduled cycle counts ?ou can define your own %30 group li e % class, 3 class, 0 class. 8ow we will go through some of the set up steps, which you will need before setting up in#entory. Setup / .efine item fle'fields / .efine item categories fle'fields / .efine catalog group fle'fields / .efine @4M / .efine subin#entories. / .efine locators / .efine organi(ation parameters. / .efine intercompany relationship. / .efine pic ing rules. 2ome of the parameters we ha#e to set defaults li e item status as acti#e, default primary unit of measure as &ach or requisition appro#al status as appro#ed or unappro#ed. (rgani*ation parameters ?ou can define and update default in#entory and costing parameters for your current organi(ation in the following areas+ .efault in#entory parameters 0osting information Re#ision, lot, serial parameters %,*, *ic , "tem!sourcing parameters "nter!4rgani(ation "nformation 4ther account *arameters .efine warehouse parameters

+efault inventory parameters *ro#ide organi(ation code and item master organi(ation "n the Mo#e 4rder ,imeout *eriod field, enter the number of days a mo#e order requisition can wait for appro#al. For locator control option+ "n#entory transactions within this organi(ation do not require locator information. *re! specified only+ "n#entory transactions within this organi(ation require a #alid, predefined locator for each item. .ynamic entry allowed+ "n#entory transactions within this organi(ation require a locator for each item. ?ou can choose a #alid, predefined locator, or define a locator dynamically at the time of transaction. .etermined at subin#entory le#el+ "n#entory transactions use locator control information that you define at the subin#entory le#el. 0osting "nformation ?ou ha#e to define costing organi(ation and costing method. ,aluation Accounts: ?ou choose a default #aluation account when you define organi(ation parameters. @nder standard costing, these accounts are defaulted when you define subin#entories and can be o#erridden. / Material %n asset account that trac s material cost. For a#erage costing, this account holds your in#entory and in transit #alues. 4nce you perform transactions, you cannot change this account. / Material 4#erhead %n asset account that trac s material o#erhead cost. / Resource %n asset account that trac s resource cost. / 4#erhead %n asset account that trac s resource and outside processing o#erheads. / 4utside processing %n asset account that trac s outside processing cost. / &'pense ,he e'pense account used when trac ing a non!asset item. 4ther accounts / 2ales ,he profit and loss 6income statement) account that trac s the default re#enue account. / 0ost of 9oods 2old ,he profit and loss 6income statement) account that trac s the default cost of goods sold account. / *urchase *rice Aariance ,he #ariance account used to record differences between purchase order price and standard cost. ,his account is not used with the a#erage cost method. / "n#entory %B* %ccrual ,he liability account that represents all in#entory purchase order receipts not matched in %ccounts *ayable, such as the unin#oiced receipts account. / "n#oice *rice Aariance ,he #ariance account used to record differences

between purchase order price and in#oice price. ,his account is used by %ccounts *ayable to record in#oice price #ariance. / &ncumbrance %n e'pense account used to recogni(e the reser#ation of funds when a purchase order is appro#ed. / *ro5ect 0learance %ccount 7hen performing miscellaneous issues to capital pro5ects, the pro5ect clearance account is used to post the distributions. / %#erage 0ost Aariance @nder a#erage costing with negati#e quantity balances, this account represents the in#entory #aluation error caused by issuing your in#entory before your receipts. "nter!4rgani(ation ,ransfer %ccounts ?ou define default inter1organi(ation transfer accounts in the 4rgani(ation *arameters window. ,hese accounts are defaulted when you set up shipping information in the "nter14rgani(ation 2hipping 8etwor s window. / ,ransfer 0redit ,he default general ledger account used to collect transfer charges when this organi(ation is the shipping organi(ation. ,his is usually an e'pense account. / *urchase *rice Aariance ,he default general ledger account used to collect the purchase price #ariance for inter1organi(ation receipts into standard cost organi(ations. ,his is usually an e'pense account. / *ayable ,he default general ledger account used as an inter1organi(ation clearing account when this organi(ation is the recei#ing organi(ation. ,his is usually a liability account. / Recei#able ,he default general ledger account used as an inter1organi(ation clearing account when this organi(ation is the shipping organi(ation. ,his is usually an asset account. / "n!transit "n#entory ,he default general ledger account used to hold in!transit in#entory #alue. ,his is usually an asset account. For a#erage cost organi(ations, this account is the default material account. 4ther information you ha#e to gi#e is, Re#ision, 2erial and lot control information. %,*, *ic , "tem sourcing rules. Inventory Planning and replenis'ment: 4racle "n#entory lets you manage your in#entory le#els using any combination of the system)s planning and replenishment features, including min1ma' planning, reorder point planning, anban replenishment, and a replenishment system for generating orders.

*erforming Recorder!*oint planning "n this planning method you will ta e minimum order quantity and time to fulfill the order to decide the le#el of order. 2o record point is safety stoc $ forecast demand during lead time *erforming min!ma' planning "n this simple method you will decide ma'imum and minimum le#el of stoc for that item, so that at min le#el order can be placed and the qty of that item can be full at ma' le#el. 2ubin#entory replishment planning For some items you will ha#e transactions with other subin#entory so that optimum stoc can be maintained. 0reating - e'ecuting Eanban cards "n this you will use anban method by deciding some items as anban cards. %nd through requisition interface i.e. after running requisition import, *urchase requisition gets created that turns out to purchase orders. ,hen through purchase order u can receipt material in in#entory. %nd that is how purchasing comes into picture. 3efore that we will ta e loo at main tables in in#entory modules li e Ma5or ,ables / M,=>2?2,&M>",&M2>3+ 3ase table for item definition. / M,=>*%R%M&,&R2 + ,his table is consist of 4R9%8"F%,"48>"., *"0E"89>R@=&>"., R@=&>". for %,* / M,=>",&M>0%,&94R?> 2&,2 / M,=>",&M>0%,&94R"&2 + ,hese tables will store information about different category sets and categories defined. / M,=>",&M >2@3>"8A&8,4R"&2 / M,=>",&M>=40%,"482 / M,=>2?2,&M>",&M2>"8,&RF%0& / M,=>2@**=? / M,=>48D%8.>G@%8,","&2 / M,=>R&2&RA%,"482 + ,hese table stores information about reser#ed quantity and on hand quantity with a#ailable quantity for pic ing rules. / M,=>2%=&2>4R.&R2 + 4rder Management will interact with in#entory for order details through this table. / M,=>",&M>F=&HF"&=.2 / M,=>",&M>,&M*=%,&2 / M,=>",&M>%,,R"3@,&2 / M,=>",&M>R&A"2"482 / M,=>M%,&R"%= ,R%82%0,"48 / M,=>,R%82%0,"482>R&%2482 %dditional terms in in#entory

/ %ccounting close cycle+ 9eneral ledger transfer "n#entory accounting periods - Move orders: Mo#e orders are requests for the mo#ement of material within a single organi(ation. ,hey allow planners and facility managers to request the mo#ement of material within a warehouse or facility for purposes li e replenishment, material storage relocations and quality handling. Mo#e orders are restricted to transaction within tan organi(ation - if you are transferring material between organi(ation, you must internal requisitions. ,hree types of mo#e orders+ Mo#e order requisition Replenishment mo#e orders *ic wa#e mo#e orders Interfaces (pen Item Interface ?ou can import items from any source into 4racle "n#entory and 4racle &ngineering using the "tem "nterface. 7ith this interface, you can con#ert in#entory items from another in#entory system, migrate assembly and component items from a legacy manufacturing system, con#ert purchased items from a custom purchasing system, and import new items from a *roduct .ata Management pac age. ,he "tem "nterface #alidates your data, insuring that your imported items contain the same item detail as items you enter manually in the Master "tem window. ,he "tem "nterface reads data from three tables for importing items and item details. M,=>2?2,&M2>",&M>"8,&RF%0& ,his table is used for your new item numbers and all item attributes. ,his is the main item interface table, and may be the only table you choose to use. M,=>",&M>R&A"2"482>"8,&RF%0& "f you are importing re#ision details for your new items, you can use this table. 7hich is used only for re#ision information, and is not required. M,=>",&M>0%,&94R"&2>"8,&RF%0& ,o import item category assignments, the table is used to store data about item assignments to category sets, and categories to be imported into the 4racle "n#entory M,=>",&M>0%,&94R"&2 table. M,=>"8,&RF%0&>&RR4R2 is used for error trac ing of all items that the "tem "nterface fails. 3efore you use the "tem "nterface, you must write and run a custom program that e'tracts item information from your source system and inserts the records into the M,=>2?2,&M>",&M>"8,&RF%0& table. %nd if re#ision - category details are there upload into respecti#e tables. %fter you load item, re#ision, and item category assignment records into these interface tables, you run the "tem "nterface to import the data. ,he "tem "nterface assigns defaults, #alidates data you include, and then imports the new items.

0ustomer "tem and 0ustomer "tem 0ross!Reference 4pen "nterface % number of manufacturing industries are characteri(ed by a multi!tiered, 5ust! intime supply chain structure. ,oday)s manufacturing en#ironment requires a close wor ing relationship between customers and suppliers along the entire supply chain. 2uppliers must be able to react quic ly to their customers) often changing requirements. 3y cross!referencing customer items with their own in#entory items, suppliers can achie#e faster order processing and shipments by allowing customers to place orders using customer item numbers. ?ou can import customer items and customer item cross!references from any legacy system into oracle in#entory. "n customer item interface you import customer items into in#entory. For each customer item you must define related information such as customer and item definition le#el. M,=>0">"8,&RF%0& @sing this table data is transferred M,=>0@2,4M&R>",&M2 table. "n customer item cross reference, you can import cross!references between customer items and e'iting in#entory items into your master organi(ation. ?ou can create multiple cross!references between customer items and one 4racle "n#entory item. ?ou can also create multiple cross!references between 4racle "n#entory items and one customer item. M,=>0">HR&F2>"8,&RF%0& @sing this interface table data is uploaded into base table, M,=>0@2,4M&R>",&M>HR&F2. .eports In inventory 4racle "n#entory pro#ides you with a wide #ariety of reports, intended for different users of the product. 7e will ha#e o#erloo on ma5or reports that you will come across. Inactive items report ?ou can use this report to print items that ha#e not had an in#entory transaction since the date you specify. ?ou can use this report to isolate items that ha#e become inacti#e and #erify their status. ,he parameters are display and brea on sub in#entory, category set, inacti#e since i.e. date from which no transactions were occurred for items. Item categories report ?ou will use this report to list items and their associated categories. Report can de#elop output as per category set and for gi#en item range. Item definition detail @se the "tem .efinition .etail report to #iew comprehensi#e information for items. @se this report to #erify items ha#e been classified in conformance with decisions you ha#e made regarding how the parts are to be planned, coasted, and located. ,he report prints the item definition for the organi(ation in which you submit the report.

?ou can #iew item attributes as per the category and also depending on your choice which attributes you want to print. =i e general item attributes, bill of material item attributes, costing item attributes, in#entory item attributes or physical item attributes. Item definition summary report @se the "tem .efinition 2ummary report to print a limited amount of information about items, such as description, status, and cost. Item template listing @se the "tem ,emplate =isting to re#iew the template definitions. % template is a way to define a set of attribute #alues. Reports parameters are all template flag or item template. Item statuses report @se the "tem 2tatuses Report to #iew the item statuses. For e'ample, ?ou can use the report to re#iew all pending statuses by ma ing the effecti#e date and the report date the same. ?ou can ha#e options li e categories from!to, items from 1to, and status effecti#e date. %nd only for particular status. A%& descending value report @se the %30 .escending Aalue Report to #iew the results of an %30 compile. ,he report is sorted by descending #alue or quantity, depending on the compile criterion. @se this report to e#aluate the brea points for assigning your %30 classes to items. ?ou can gi#e cumulati#e display criteria i.e. cumulati#e by #alue of cumulati#e by quantity.

(rgani*ation Setup / @se the 4rgani(ation *arameters window to complete your organi(ation definition for in#entory purposes.
/ .efine recei#ing parameters if you recei#e items on purchase orders, internal orders, and in transit interorgani(ation shipments. / ,he item master organi(ation should be the first in#entory organi(ation for which parameters are defined. / ?ou must also specify the item master organi(ation. ,he system defaults this field to the organi(ation for which parameters are being entered. "t must be changed, for any organi(ation that is not a master organi(ation. / ?ou must define the control options and account defaults for your organi(ation before you can define items or perform any transactions. / ?ou must assign a unique short code to your organi(ation and use this code to identify the organi(ation with which you want to wor .

4racle "n#entory represents your companyIs in#entory sites and business units. ,his includes defining organi(ations, locations, subin#entories, and locators. .efine organi(ation parameters. ,hese parameters are the source for default in#entory, costing, control, and mo#ement parameters for an organi(ation .efine subin#entories that represent physical or logical locations for items within an organi(ation .efinelocators that represent storage structures 6for e'ample, aisles or bins) within 2ubin#entories .efine planners or planning entities for each organi(ation. ?ou assign planners to in#entory items at the organi(ation le#el

.efining .efault "n#entory *arameters ,o define in#entory parameters+ 1. 8a#igate to the 4rgani(ation *arameters window.

2elect an "tem Master organi(ation. ?ou create items in the item master organi(ation and assign them to other organi(ation within your operating unit. Mo#e 4rder ,ime!out *eriod field, ,he wor flow appro#al process sends a notification to the item planner when a mo#e order requisition requires appro#al. %fter the first time!out period, if the recipient has not appro#ed or re5ected the order, the system sends a reminder notice. %fter the second time!out period, the system automatically re5ects or appro#es the order depending on whether you select %ppro#e automatically or Re5ect automatically in the Mo#e 4rder ,ime!out %ction field. 2elect a locator control option+

8one+ "n#entory transactions within this organi(ation do not require locator information. *respecified only+ "n#entory transactions within this organi(ation require a #alid, predefined locator for each item. .ynamic entry allowed+ "n#entory transactions within this organi(ation require a locator for each item. ?ou can choose a #alid, predefined locator, or define a locator dynamically at the time of transaction. .etermined at subin#entory le#el+ "n#entory transactions use locator control information you define at the subin#entory le#el. .efault 4n!hand Material 2tatus trac ing option "mportant+ ?ou cannot update this field for e'isting organi(ations.,o enable this field, you must submit the %cti#ate 4nhand =e#el Material 2tatus ,rac ing concurrent program.

nit of Measure
% unit of measure 6@4M) is a #alue that specifies the quantity of an item. For e'ample, JeachKis a unit of measure that you would use to specify the number of units of an item.

@nit of Measure 0lass% unit of measure class is a group of units of measure with similar characteristics. For e'ample, JweightK can be a unit of measure class with @4Ms such as ilogram, gram, pound,and ounce. @ses of @nits of Measure *lanning *roducts / Forecasting and consumption / Master scheduling / Material requirements planning 7or in *rocess / 2hop floor mo#es / Resource transaction / 0ompletion and return transactions / "nquiries and reports 3ills of Material and &ngineering / .efining bills of material / .efining engineering items

@nits of Measure 0lasses 68) L 2etup L @nits of Measure L 0lasses. @nit of Measure 0on#ersions 68) 2etup L @nits of Measure L 0on#ersions

Item Master %usiness /xample

2uppose you ha#e a distribution warehouse and a manufacturing factory. "n the warehouse, the item has independent demand and is min!ma' planned. "n the factory, the item is MR* planned and built. @sing an "tem Master with a warehouse and a factory as the other organi(ations, you define the item 5ust once!in the "tem Master. 8e't, you assign the item to both the warehouse and the factory. Finally, you change the planning and build attributes in each organi(ation to describe the different beha#ior of the items in those organi(ations. ?ou do not ha#e to change any other information about the itemC in fact, because information such as unit of measure, description, and so on is maintained at the Master le#el, you now it is consistent in each organi(ation. "tem attributes are information about an item, such as order cost, lead time, and re#ision control. 4ne of the prerequisites for defining items 6and assigning #alues to item attributes) is setting attribute controls. &ontrol 0evel ,his attribute control type determines whether you ha#e centrali(ed 6Master le#el) or decentrali(ed 64rgani(ation le#el) control of item attributes.

%ttributes maintained at the Master le#el ha#e the same attribute #alues in each organi(ation in which an item is assigned. For e'ample, you maintain an itemIs primary unit of measure at the Master le#el. %ttributes maintained at the 4rgani(ation le#el may ha#e different attribute #alues in different organi(ations. For e'ample, an item may be min!ma' planned in a distribution organi(ation but material requirement planning 6MR*) planned in a production organi(ation.

Item Status &ontrol 2tatus control describes whether certain status attributes ha#e default #alues that appear when you assign a status code to an item, and whether status codes control those attribute #alues after the defaults are assigned to an item.
8ote+ "tem 2tatus 0ontrol differs from material status control. "tem status control controls the action you can perform on an item, such as purchasing or stoc ing an item. Material 2tatus controls the transactions you can perform on an item. ,he status attributes are+ / 34M %llowed / 3uild in 7"* / 0ustomer 4rders &nabled / "nternal 4rders &nabled / "n#oice &nabled / ,ransactable / *urchasable / 2toc able / Recipe &nabled

,he "tem 2tatus attribute has a defined set of yesBno #alues for the status attributes. ?ou apply the #alues to the status attributes when you choose an item status code when you define an item. For e'ample, in the beginning of a product de#elopment cycle you set the "tem 2tatus attribute to *rototype with all of the status attributes defaulted to yes e'cept for 0ustomer 4rders &nabled. 7hen the item is ready you change the "tem 2tatus attribute to %cti#e to enable all item functions.?ou can assign one or more pending statuses for an item, to be implemented on future dates.,hese statuses become effecti#e on their assigned effecti#e dates. ?ou can #iew the status history of an item if needed.

Defining Items

Defining Item Types

The User Item Type item attribute is a QuickCode you use when you define an item. You can use the types provided by Oracle Inventory or create your own.

To define your own item types:

1. Navi ate to the Item Type QuickCodes window. The User access level is selected

indicatin you can add or modify QuickCodes without restriction.

To define an item using the Attribute Groups Tab:

1. Navi ate to the !ttribute "roups tab on the #aster Item window.

$nter a uni%ue desi nator for the item.

3. Optionally& select a Control 'evel to enable only #aster level or Or ani(ation level

attributes. The default is to enable all attributes. 4. )elect an tabbed re ion to display an item attribute roup where you can specify values for attributes in that roup. Note: To locate a particular attribute without manually lookin throu h the tabbed re ions choose *ind !ttribute from the Tools menu. 5. )ave your work.

Master-Level Control n attribute you (aintain at t%e (aster level %as identical values across all organi"ations t%at use t%e ite(. Organization-Level Control n attribute you (aintain at t%e organi"ation level (ay %ave different values for eac% organi"ation t%at uses it. Attribute Control So(e attributes can be (aintained at only t%e Master level or t%e Organi"ational ,evel.Unit of Measure s%ould be (aintained at t%e Master level.If using (ultiple organi"ations) t%e Min1Ma- attribute s%ould be (aintained at t%e organi"ation level. 234 5 Ite(s 5 Master Ite(s

To define a ess mappings between organi!ations and responsibi"ities:

1. Navi ate to the Or ani(ation !ccess window.

(pen Item Interface

?ou can import and update items, and their category assignments from any source into 4racle "n#entory and 4racle &ngineering using the "tem "nterface. 7ith this interface, you can con#ert in#entory items from another in#entory system, migrate assembly and component items from a legacy manufacturing system, con#ert purchased items from a custom purchasing system, and import new items from a *roduct .ata Management pac age. ,he "tem "nterface reads data from two tables for importing items and item details. ?ou use the M,=>2?2,&M>",&M2>"8,&RF%0& table for new item numbers and all item attributes. ,his is the main item interface table, and can be the only table you choose to use. "f you are importing re#ision details for new items, you can use the M,=>",&M>R&A"2"482>"8,&RF%0& table. ,his table is used only for re#ision information, and is not required. % third table, M,=>"8,&RF%0&>&RR4R2, is used for error trac ing of all items that the "tem "nterface fails.

/efore you use t%e Ite( Interface) you (ust 'rite and run a custo( progra( t%at e-tracts ite( infor(ation fro( your source syste( and inserts it into t%e MT,6S*STEM6ITEMS6I3TERF 0E table) and 2if revision detail is included4 t%e MT,6ITEMS6RE7ISIO3S6I3TERF 0E table. fter you load t%e ite(s into t%ese interface tables) you run t%e Ite( Interface to i(port t%e data. T%e Ite( Interface assigns defaults) validates data you include) and t%en i(ports t%e ne' ite(s.

Importing Items
To import items using the Item Interfa e:
1. Navi ate to the Import Items or !ll +eports window. #. $nter Import Items in the Name field. The ,arameters window appears

12 "ndicate whether to run the interface for all organi(ations in the item interface table.

"f you choose No, the interface runs only for the current organi(ation and interface table rows for other organi(ations are ignored.

32 "ndicate whether to #alidate all items and their data residing in the interface table

that ha#e not yet been #alidated. "f items are not #alidated, they are not processed into 4racle "n#entory. ?ou would choose No if you had pre#iously run the item interface and responded Yes for Validate Itemsand8oforProcess Items4 and now want to process your items.
52 "ndicate whether to process items. "f you choose Yes, all qualifying items in the

interface table are inserted into "n#entory. ?ou would choose No, along with Yes for Delete Processed Rows, to remo#e successfully processed rows from the interface table without performing any other processing.
62 "ndicate whether to delete successfully processed items from the item interface

tables. 0hoose No to lea#e all rows in the item interface tables for successfully processed items.
72 0hoose 4E to close the *arameters window, then choose 2ubmit.