Inventory And Order Management

1

Oracle Inventory Oracle Inventory interacts with the other applications by sharing information:  Oracle Cost Management: From cost Information to transaction rates  Oracle Work in Progress: From WIP activity and ATP supply information to UOM, items, and on-hand quantity.  Oracle Master Scheduling/MRP: From ATP supply information to on-hand quantity and forecasts  Oracle Bill of Materials to UOM and items Integration of Inventory to Manufacturing modules  Oracle Engineering: From engineering item information to UOM and items  Oracle Order Management: From Shipping, reservations, and demand to UOM, items, and ATP/on-hand quantity  Oracle Purchasing: From receipts/deliveries, ATP supply, and planning supply to UOM, items, requisition, and inter-org shipments Integration of Inventory to Financial modules  Oracle General Ledger From: Set of Books and Currency Exchange Rates To: Transaction Accounting Summary/Detail  Oracle Payables To: UOM and Items  Oracle Receivables To: UOM and items From: Intercompany Invoice  Oracle Assets To: UOM and Items Multi-Org tables: Flow Table Business HRFV_BUSINESS_GROUPS group Columns BUSINESS_GROUP_NAME DATE_TO BUSINESS_GROUP_SHORT_NAME LEGISLATION_CODE DEFAULT_CURRENCY_CODE EMP_NUMBER_GENERATION_METHOD GRADE_STRUCTURE PEOPLE_GROUP_STRUCTURE JOB_STRUCTURE COST_ALLOCATION_STRUCTURE POSITION_STRUCTURE COMPETENCE_STRUCTURE WORKING_HOURS_FREQUENCY WORKING_HOURS_AMOUNT SET_OF_BOOKS_ID

Set of Books

GL_SETS_OF_BOOKS

2

Legal entity

HR_LEGAL_ENTITIES

NAME SHORT_NAME CURRENCY_CODE PERIOD_SET_NAME CHART_OF_ACCOUNTS_ID BUSINESS_GROUP_ID SET_OF_BOOKS_ID ORGANIZATION_ID NAME DATE_FROM DATE_TO BUSINESS_GROUP_ID SET_OF_BOOKS_ID LEGAL_ENTITY_ID ORGANIZATION_ID NAME DATE_FROM DATE_TO

Operating Unit

HR_OPERATING_UNITS

Inventory Organization Sub Inventory Stock Locators

MTL_PARAMETERS ORG_ORGANIZATION_DEFINITIONS HR_ALL_ORGANIZATION_UNITS MTL_SECONDARY_INVENTORIES MTL_ITEM_LOCATIONS

ORGANIZATION_ID SECONDARY_INVENTORY_NAME ORGANIZATION_ID SUBINVENTORY_CODE INVENTORY_LOCATION_ID SEGMENT1

How to find whether MULTI_ORG is enabled for the application or not? SQL> Select * FROM FND_PRODUCT_GROUPS Columns in the table FND_PRODUCT_GROUPS: RELEASE_NAME PRODUCT_GROUP_TYPE MULTI_ORG_FLAG MULTI_LINGUAL_FLAG MULTI_CURRENCY_FLAG From the backend, How to set Client Info in Backend?  DBMS_APPLICATION_INFO.SET_CLIENT_INFO ('org_id'); Ex: DBMS_APPLICATION_INFO.SET_CLIENT_INFO (103);

 FND_CLIENT_INFO.SETUP_CLIENT_INFO (application_id => <application_id>
,responsibility_id =><Resp Id> ,user_id =><User id> ,security_group_id =><Security Group Id>); Ex: FND_CLIENT_INFO.SETUP_CLIENT_INFO(application_id => 660, responsibility_id =>21623,

3

security_group_id =>0).start_date AND gls.end_date FROM gl_period_statuses gls WHERE gls.end_date.SET_CLIENT_INFO (103).set_of_books_id = <set_of_books_id> AND gls.user_id =>0.application_id = 222 AND sysdate BETWEEN gls. Ex: DBMS_APPLICATION_INFO.SET_CLIENT_INFO ('org_id'). gls. Inventory Flexfield: Only One Structure Supported Inventory Flexfields 4 . How to set Client Info in Reports? Before Report: DBMS_APPLICATION_INFO. How to pass Sets of Books ID and Org ID to the Concurrent Program Report? Name Value Set Default SQL Statement Set of Books ID AR_CHART_OF_ACCOUNTS_NO_VALIDATION select sb. ar_system_parameters sp where sb.start_date .set_of_books_id from gl_sets_of_books sb.set_of_books_id = sp.set_of_books_id Org ID MULTI_ORG_ID select org_id from ar_system_parameters How do you validate GL Periods? SELECT gls.

Order Type. It is also a transaction source type of its own.) System Items (Items Flexfield) You must set up your OE: Item Flexfield profile option to specify the Item Flexfield structure that you will use for your Oracle applications. You must define this flexfield before placing demand or making reservations in Oracle Order Management. This combination guarantees each transaction to Inventory is unique.Account Alias Item Catalogs Sales Order Stock Locators Sales Order Your Sales Order Flexfield should be defined as Order Number. thereby allowing you to query and report transactions using your user–friendly references to particular account numbers. Account Aliases An account alias is a logical reference to a frequently used account number combination. Users can also set up the OE: Item Flexfield Entry Method profile option to specify your preferred method of entry for this Flexfield Item Categories Item Categories Flexfield is associated to Category Sets. Logical reference to accounting code combinations: 5 . and Order Source. You must set up the OM: Source Code profile option to determine the source code you will use in for the third segment of this flexfield to guarantee that each transaction is unique. (Oracle Inventory defaults the value of the OM: Source Code profile option to ’ORDER MANAGEMENT’.

Where do we set Inventory Organization for a particular responsibility?? Through Organizational Access Form Transaction Source Type: Item: Items is a part or service you: o Purchase o Sell o Plan o Manufacture o Stock o Distribute o Prototype The following Modules use items: 6 .

Both status attributes and item status can be controlled at the item level or organization levels.Item Statuses and Item Attributes Status attributes are item attributes that enable key functionality for each item. An item status is defined by selecting the value check boxes for the status attributes. Item Statuses are:  BOM Allowed  Build in WIP  Customer Orders Enabled  Internal Orders Enabled  Invoice Enabled  Transactable  Purchasable  Stackable Item Attributes 7 .

or out of inventory. List Price. a workday calendar. Transact able. Shippable. Stackable. as many distinct item catalog groups as needed can be defined. Purchased.  All transactions validate the various controls (revision. 8 . Transaction  A transaction is an item movement into. Build in WIP. lot number. BOM Allowed. Planning and Inventory  Assign items to categories. Internal Orders Enabled. values for the descriptive elements that apply to the item are defined. Returnable. Possible values for Processing Speed might be 100MHZ.  Define category sets and assign the categories to the sets. Invoice Enabled. A transaction changes the quantity.Item attributes are the collection of information about an item. locator. Locator Control Receipt Required. and a list of items. Categories and Category Sets Categories are logical groupings of items that have similar characteristics. The characteristic required to uniquely define an item in each group is configured in advance. Purchasable. Inventory.  An inventory organization can be a logical entity like an item master organization which only holds items with no transactions An inventory organization can have its own location with a set of books. The user specifies a default category for this purpose in each of these modules. Each set can use a different Flexfield definition if required. Financing Allowed. item cataloging is optional. Revision Control. Some application modules. Lot Control. Each group has unique characteristics (called descriptive elements) that completely describe items belonging to the group. Item Cataloging  Item cataloging is used to add descriptive information to items and to partition the Item Master into groups of items that share common characteristics. A category set is a distinct category grouping scheme and consists of categories.  To define a catalog. Inventory supports a number of predefined and user-defined transaction types. Inventory Item. an item catalog group called Computer could have a descriptive element called Processing Speed. and serial number) enabled for items. a costing method. Inventory Organization  An inventory organization can be a physical entity like a warehouse where inventory is stored and transacted. and so on. for example require that all items are assigned to a category.  While the catalog group Flexfield is a required setup. Customer Orders Enabled.  When assigning an item to an item catalog group. like Purchasing. within. Categories and category sets are used to group items for various reports and programs. 133MHZ. Item Categories . Costing Enabled.  Every material movement has a corresponding set of accounting transactions that Oracle Inventory automatically generates.  Assign default category sets to each functional area. For example. or cost of an item.  Define categories.Setup  Define the Flexfield structures for the item categories Flexfield. Receivable. While defining items. these characteristics are assigned to an item catalog group. An item can be assigned to only one category within a set. location.

Its single purpose is for entering items.  Accuracy Analysis: You can perform a cycle count. It is not used to enter items. Items are entered in an item master organization and then assigned to use in child organizations. subsidiary.  Costing Methods: You set your costing method (Standard or Average) at the organizational level.  A maximum of one item validation organization per operating unit is allowed to determine the items that may be sold in each operating unit. An inventory organization can share one or more of these characteristics with other organizations. The item attribute control level determines the costing organization. Items are entered in an item master organization and then assigned to be used in child organizations. It gets a list of items from the master. Item Master Organization Item Master Organization is usually the first Inventory organization that is set up. costing method. Multiple item validation organizations can be listed that share the same item master organization. What is Item Master organization and Child Organization?  Item Master Organization is usually the first Inventory organization that is set up. or a physical inventory Item validation organization  Item validation organization is a logical entity listing all the items that an enterprise sells to customers. It has no sub inventories and is not used for inventory transactions. It is not used to enter items. workday calendar and list of items.  Child Organization is an inventory organization with at least one sub inventory that is set up for processing inventory transactions. Consider the following when you plan your enterprise structure:  Sets of Books: You can tie one Oracle General Ledger set of books to each inventory organization. Child Organization Child Organization is an inventory organization with at least one subinventory that is set up for processing inventory transactions. Its single purpose is for entering items. What is the purpose of Organization Assignment? After defining an Item in the Item master.  Item Costs: Oracle Inventory keeps one cost per item per inventory organization. 9 . The purpose of the Organization Assignment is to make the item available for Transactions in particular Organizations.  A minimum of one item validation organizations is required per set of books.  Forecasting: You can forecast your items. it has to be assignment to the Organization and is known as Organization Assignment. It gets a list of items from the master. An organization can be a company. or warehouse.  Movement between Inventory Sites: You can use in-transit inventory for interorganization transfers. It has no sub inventories and is not used for inventory transactions.  Planning Method: You can choose how to plan your items.  An inventory organization is an inventory location with its own set of books.

representing either a physical area or a logical grouping of items. Items can be received directly into and shipped items directly from locators. Subinventory  A sub inventory is a Subdivision of an organization. Inventory propagates item to all organizations in which the item is to be defined. If locator control is turned on at the item 10 .  Locators may represent rows. and then go to another organization and choose Min-Max planning for the same item. use the Deletion Groups window to delete the item. Organizational attributes for item attributes which are enabled in that organization. such as raw material. aisles. Inventory controls are optional for all items  Locator  Revision  Lot  Serial Number Stock Locator / Locator Control  Locators are optional structures within sub inventories. For example. or a freezer compartment. go to an organization to choose reorder point planning for an item. Each subinventory must contain the following information:  Unique alphanumeric name  Status  Cost Group (feature enabled if you have WMS installed)  Parameters  Lead times  Sourcing information  Account information Inventory Controls Any combination of the four controls can be implemented for each item. such as a storeroom or receiving dock    A subinventory is a physical or logical grouping of inventory.  If you decide to purge the item immediately after incorrectly defining it and before using it anywhere in the system. can be entered or changed which are enabled in that organization. finished goods. Deletion Constraints and Deletion Groups  If you want to enforce specific business rules and add custom checks before you can delete an item.What are Organization Assignment and Organization Item? Item can be enabled in all child organizations under master organization or child organizations where the item to be used is chosen. you must define item deletion constraints to supplement the standard predefined item deletion conditions. or bins in warehouses. The subinventory is the primary place where items are physically stocked. you will be able to delete it. A subinventory must be specified for every inventory transaction Sub inventories can be further divided into areas designated as locators. For example. if you make a mistake in entering an item number.  Locators are the third level in the enterprise structuring scheme of Oracle Inventory.  You can structure your Oracle Inventory installation so some of the subinventories and items have locator control while others do not. defective material.  You can delete items that have incorrect attribute information.

and each subinventory can have multiple stock locators.level.  Letters are always in upper case and numbers may include decimals. or routing. To do so a revision is a must for each material transaction. bill of material.  Revision control is enabled for items for which version changes or changes that are significant enough to track but are not affecting the function and feature of the item are tracked. Revision Control  A revision is a particular version of an item. Locator Listing Report You use the Locator Listing Report to list stock locators you defined. you must specify a locator when transacting any item into or out of that subinventory. you must specify a locator when transacting the item into or out of a subinventory. You also use this report to review volume and weight allowed in a location before transacting items. 10 precede 9.  By using the ‘Revision control’ option while defining items item quantities can be tracked by item revision. A1. etc can be used. decimals should always be followed by a number. numbers and characters such as A. For example. then the locator is not included in the report.  The value entered in the Starting Revision field in the Organization Parameters window displays as the starting revision for the item when assigning revisions to an item. Lot Control  Inventory provides complete lot number support for inventory transactions.  When defining Revision numbers letters.  A lot identifies a specific batch of an item that is received and stored in an organization. 2B. The possible locator control types are: o None o Pre-specified o Dynamic entry o Item Level Explaining Locator Control Reports Locator Quantities Report You use the Locator Quantities Report to identify items and their quantities stored in the specified stock locators. If locator control is turned on at the subinventory level.  To ensure that revisions sort properly. Each stock locator you define must belong to a subinventory. 11 . If the stock locator has a zero on-hand quantity.  Revision Control item attributes cannot be changed when an item has quantity on hand. according to ASCII sorting.  Revisions are sorted according to ASCII rules. revision 10 cannot be used after revision 9 because.  Each revision must be greater than the previous revision.

Lot numbers must be assigned whenever items under lot control are received into inventory. You can run the report for a range of lot numbers and items and a specific supplier lot number. The report shows you the lot material transactions related to the selected items as. An inventory receipt can be split in to several lots. items. You can run the report for a range of lots. Supplier Lot Trace Report You can use the Supplier Lot Trace Report to trace a specific lot to its supplier lots. Lot Control must be turned on at the item level. You can also specify a specific category set and display transaction quantities in their primary or transacted unit of measure.       Lot control is a technique for enforcing the use of lot numbers during material transactions. the lot number must be indicated to perform a transaction. thus enabling the tracking of batches of items throughout their movement in and out of inventory. lot numbers. If Lot Control is turned on for an item. transactions types. and subinventories. as necessary. transaction reasons. Quantities can be added to existing lot numbers. and transaction quantities. 12 . Expired Lots Report You can use the Expired Lots Report to show lots in your organization that expire on or before the date you specify. transaction dates. You can run the report for a range of items or for a specific item only. Explaining Lot Control Reports Lot Transactions Register You can use the Lot Transactions Register to report comprehensive lot number material transaction detail within a specific date range. Inventory will generate default lot numbers by using the default lot number generation method which is configured in the Organization Parameters window during setup.

 Individual units of items can be tracked by using serial numbers. it simply reserves serial numbers for an item. optionally serial numbers for the item can be predefined. Serial numbers can be used to track items over which a very tight control is to be maintained.  If Predefined is specified as the serial number control type.Serial Control  A serial number is an alphanumeric piece of information assigned to an individual unit of an item. Serial number control is a system technique for enforcing the use of serial numbers during a material transaction. A serialized unit is a combination of an item number and a serial number.  One serial number per unit of an item can be assigned  Depending on how Serial Number Control is set at the Master Item level will determine how serial numbers are generated.  If control ‘At inventory receipt’ or ‘At sales order issue’. This does not assign numbers to units in inventory. Generating Serial Numbers  Inventory uses the starting serial number prefix and the starting serial number specified in the Item screen. serial numbers for that item must be predefined. no serial number control will be enforced.  If No Control is specified as the serial number control type. Serial Genealogy 13 . for later use.  The process of generating serial numbers is done through a concurrent report.

Item Templates  Templates are defined sets of attributes that can be used over and over to create many similar items. Explaining Serial Number Control Reports Serial Number Transactions Register You can use the Serial Number Transactions Register to report comprehensive serial number material transaction detail within a specific date range. and supplier serial numbers.    Enables to view the composition and transaction history of a serial-controlled item through a graphical user interface.  Templates can be applied at any time after the item is created. transaction reasons. items. Includes all material transactions within an organization. Enables to trace serial numbers from a component to a final assembly. Templates make initial item definition easier and more consistent.  Templates can hold a complete set of attributes or a partial set. transaction types. and subinventories. You can also specify a specific category set and display transaction quantities in their primary or transacted unit of measure. If a partial set. Oracle Inventory enables you to run the report for a range of serial numbers. items. Serial Number Detail Report You can use the Serial Number Detail Report to report on information about current serialized units in your organization for a specific source type or serialized unit status. then only values stored in the template overwrite those on the item  Users can define their own templates or predefined templates include: ATO Model ATO Item ATO Option Class Kit PTO Model PTO Option Class Planning Item Phantom Item Subassembly Purchased Freight Finished Good Outside Processing Item Reference Item Supply Item Product Family Item Relationships The following types of relationships can be defined for items:  Item cross-references  Substitute items  Related items  Manufacturer part numbers  Customer item numbers Relationships between items can be defined to improve purchasing management and item searching capabilities. Multiple templates can be applied to a single item. Enables to trace serial numbers from an assembly to all components. Substitute items can be received in Oracle Purchasing. suppliers. You can run the report for a range of serial numbers. 14 .

gram. Receipt to Issue Life Cycle: Oracle Inventory uses the receipt to issue process to manage your inventory. Mfg and BOM. First 10 Bytes are used to store Operating Unit ID(or ORG_ID) for the multiple organization support feature. • Oracle Order Management • Oracle Purchasing • Oracle Work in Process • Oracle Inventory 15 . Multi-Org views are partitioned by ORG_ID. AR and OM Levels). A Global Variable exists in the Oracle Database called CLIENT_INFO.  Multiple cross-reference types can be assigned to a single item. to specify the quantity of an item. “each” is a unit of measure that used to specify the number of units of an item. PO. pound. and ounce. A unit of measure class is a group of units of measure with similar characteristics. a cross–reference type Old can be created to track the old item numbers . For example. You use the following applications to issue inventory. and a cross-reference type Supplier to track supplier part numbers. (It comes in AP. What is the Importance of UOM? A unit of measure (UOM) is a term used along with a numeric value. Org_Id represents Operating Unit Id. and from one organization to another organization using the following applications • Oracle Shipping • Oracle Order Management • Oracle Work in Process • Oracle Inventory Issuing When you send materials out of inventory you issue it. which is 64 byte long. The ORG_ID value is stored in CLIENT_INFO variable.Item cross-references  Cross–reference types define relationships between items and entities such as old item numbers or supplier item numbers. ORGANIZATION_ID For inventory. You can receive inventory using the following applications • Oracle Purchasing • Oracle Work in Process • Oracle Inventory Transferring You can transfer inventory within an organization. For example. A unit of measure conversion is a mathematical relationship between two different units of measure. For example. “weight” can be a unit of measure class with units of measure such as kilogram. What is the difference between Organization_Id and Org_Id? Organization_Id represents Inventory Organization Id. The three main pieces of the process are as follows: Receiving When you take delivery of inventory in to your warehouse you receive it.

Order Management Order management can generate a transfer to move stock from a finished goods area to a staging area for shipping. Inventory Inventory transfers materials using the following methods: • Transfer between Organizations • Replenish materials • Request transfers 16 . Shipping Shipping can generate a transfer to move stock from a finished goods area to a staging to for shipping. Purchasing You can receive inventory from outside of your organization using purchasing.Receiving Inventory There are different ways you can receive inventory in to stock. Work in Process Work in Process can generate a transfer to acquire components for a project. The ways you use purchasing in relation to receiving are:  Purchase Order Receipt  Internal Requisition  In transit Receipt  Return Material Authorization  Unexpected Receipt Work in Process You can receive inventory from the manufacturing floor using Oracle Work in Process  Component Return  Negative Component Issue  Assembly Return Inventory You may receive inventory in to stock using the inventory application in the following ways:  Miscellaneous Account  Receipt from Project  User Defined  Inter-organization receipt Types of Inventory Receipts  Receipt and Deliver  Receipt and then Deliver  Inspection • Receipt • Deliver • Inspection Transferring Inventory Different applications can generate requests to transfer inventory.

Issuing Inventory You can issue stock out of inventory using the following applications: Order Management Order Management can generate an inventory issue through: • Sales Orders • Internal Orders Purchasing Purchasing can generate an inventory issue for: • Return to Vendor materials Work in Process Work in process can generate an inventory issue through: • Component Issue • Assembly Return Inventory You can issue stock using the inventory application in the following ways: • User Defined • Inter Organization Transfer • Cycle Count Negative • Request Issue Item Profile Options Transaction Types:  Receive items into your organization using a general ledger account number  Issue items from your organization using general ledger account number  Transfer items from a subinventory in your organization to another subinventory in the same organization  Transfer items directly between organizations  Transfer items between organizations by way of intransit 17 .

Predefined transaction types are as follows: • Purchase Order • Account Alias • Move Order • Internal Order • Standard Cost • Update • Internal Requisition • Sales Order • Cycle Count • Periodic Cost Update • Physical Inventory • RMA (Return Material Authorization) • Inventory • Job or Schedule Transaction Action You use transaction actions with a source type. A number of transaction types are predefined in Oracle Inventory. it uniquely identifies the type of transaction performed. It is used to classify a particular transaction for reporting and querying purposes.     A transaction type is the combination of a transaction source type and a transaction action. It is used to classify a particular transaction for reporting and querying purposes. Reserve items for a specific account or temporarily prevent the release of items onto the shop floor A transaction type is the combination of a transaction source type and a transaction action. Oracle Inventory provides the following predefined transaction source types. Oracle Inventory provides the following transaction actions: • Assembly completion • Issue from stores • Subinventory transfer • Direct organization transfer • Cycle count adjustment • Physical inventory adjustment • Intransit receipt • Intransit shipment • WIP assembly scrap 18 . A transaction action identifies a transaction type. Oracle Inventory also uses transaction types to identify certain transactions to include in historical usage calculations for ABC analysis or forecasting. The user can also define additional types by setting up new combinations of source types and actions. You can define additional source types. Transaction Source Type You use a transaction source type with a transaction action.

These run at the periodic intervals you specify until you disable them with the concurrent manager. Cost Transaction Manager The material cost transaction manager must run to cost material transactions. such as completions or component issue. Remote Procedure Manager Remote procedure manager processes online inventory transactions WIP initiates. Material Transaction Manager Immediately executes a material transaction after you save your changes in a transaction window. Move Transaction Manager The move transaction manager moves assemblies received from an outside processing supplier to the next operation. processing intervals and the number of transactions processed by each worker during each interval. You do not have to launch the other transaction managers if you decide to process your transactions on-line. What are the Types of Inventory Transactions? 19 .• • • • • • • Cost update Receipt into stores Negative component issue Delivery adjustments Negative component return Assembly return Vendor Managed Inventory Planning Transfers Transaction Managers Transaction mangers control the number of transaction workers. and do not use the transaction interface.

issuing items for R & D or issuing track able expense items. Inter ORG Transfers This transaction is used to transfer goods from one inventory organization to another. 20 . or between two locators within the same subinventory We can transfer from asset to expense subinventories. If an item has a restricted list of subinventories. as well as from tracked to non–tracked subinventories.Miscellaneous Transactions This transaction is used to do adjustments in stock due to damage. obsolescence. Interorganization Direct Shipment You use the Interorganization Transfer window to move inventory directly from a shipping organization to a destination organization. we can only transfer material from and to subinventories in that list. Subinventory Transfer This transaction is used to transfer goods from one stockroom to another with in the same inventory organization. Use the Subinventory transfer window to: Transfer material within your current organization between sub inventories.

you do not need to specify the delivery location. 21 . and. a percentage of the transaction value or a discrete amount that Oracle Inventory uses to compute transfer charges. a shipment number. • You only need to enter the subinventory you are shipping from.Interorganization Intransit Shipment • When you perform the transfer transaction. the freight information.

These two inventory transactions will be covered in Oracle Shipping and WIP training You Can Perform the Following Oracle Inventory Transactions  Receive items into your organization from a general ledger account number  Issue items from your organization to a general ledger account number  Transfer items from a subinventory in your organization to another subinventory in the same organization  Transfer items directly between organizations  Transfer items between organizations by way of in-transit  Reserve items for a specific account or temporarily prevent the release of items onto the shop floor What is Move Order? 22 .Transfer type: Direct: Inter-organization transfers move inventory directly from the shipping organization to the destination organization. WIP Issue This transaction is used to issue materials against production orders. Note: WIP issue and Sales issue will not be covered as part of Oracle inventory training. Receiving Transactions This transaction is used to move goods from receiving dock to specified subinventory and locator. Sales Issue This transaction is used to move goods from pick subinventory to staged subinventory. Intransit: Inter-organization transfers move inventory to intransit inventory first. You can track this inventory until it arrives at the destination organization.

the material is only transacted to the staging subinventory and reserved. The line details are the Inventory transactions that occur to fulfill a particular request line (move order line). and any project and task references if the organization is Project Manufacturing enabled.” Users can set up a default Pick Confirm policy in the Inventory organization parameters. If mobile devices such as bar code scanners are used to perform inventory transactions. This refers to the entity that created the move order. This default can be overridden at each Pick Release. Reservations created for sales orders are automatically updated and transferred you as the move order is released and transacted. Note that even if an automatic pick confirm is employed. Pick Confirmation automatically transfers the high level reservation to a detailed reservation (including lots. For all move orders. on the move order line. you should use manual pick confirmation for greatest inventory accuracy and control. lot.Transaction defaults (for destination locators). or subinventory. the final result is one of the two supported transactions: subinventory or move order issue. completed quantity (if the move order has been partially fulfilled). The Move Order Line Details (transaction lines) created by the detailing process must be transacted to confirm the material drop-off in staging. or serial controlled. These details can be edited prior to transaction by a user. Anatomy of a Move order: Oracle Order Picking and Shipping stores the move order source type in the header. and the requested date. a source and destination if known. They store the item. Shipping Execution uses it to move the items during the shipping process into a stage area before the items are really shipped to the customer. This process is called Pick Confirmation. If the material is locator.A move order is a request for a sub inventory transfer or account issue. At pick confirmation.  Move Order Requisitions  Replenishment Move Orders  Pick Wave Move Orders The move order type refers to the entity that created the move order. The lines are the requests on that move order. locator. the order number. A user can still manage any discrepancies found by deleting the reservation and transacting the material back to its original subinventory. serial. It is used to make sub inventory transfers. Move Order Source Types Oracle Inventory Release 11i provides three types of move orders. the Pick Confirm transactions can occur immediately after the lines are detailed. This option is called “auto pick confirm. Pick confirmation executes the subinventory transfer that moves the material from its source location in the warehouse into the staging location. An order could be a pick wave (for sales order picks) a replenishment type. subinventory. revisions. Move Order Requisition 23 . and locators) in the staging location. It is a transaction type in inventory. a user can report a missing quantity or change the transaction line if the picker chose to use material from a different lot. The pick release process creates move orders which are pre-approved requests for sub inventory transfers to bring material from its source locations in the warehouse to a staging sub inventory. These details are automatically filled in by Oracle Inventory using the Inventory Picking Rules and the Item . or the user can manually fill in the details. If an organization’s picks rarely deviate from the suggested picking lines and the overhead of requiring a Pick Confirmation is unmanageable. The user can also request specific serial or lot numbers if know. Order Picking and Shipping also stores the default source and destination if available. this information is filled in at the line detail level. requested quantity. a requisition for sub inventory transfer and so on.

This is not the same default type that you would use for receiving or shipping. The requisition can optionally go through an Oracle Workflow approval process before it becomes a move order. Replenishment move orders are pre-approved and ready to be transacted. The line details are the inventory transactions that must be fulfilled to complete the move order line. In this case. You can now set up a default locator for each item that you want to move around the warehouse on a move order. Pick Wave Move Order The pick release process generates move orders to bring the material from its source location in stores to a staging location. the min-max or replenishment count report automatically generates a move order.The requisition is a manually generated request for a move order. You can generate requests for subinventory transfers or move order issues. and lots to source the material in order to fulfill a move order line. You must create a move order requisition. In these cases orders can be released to 24 . This transaction is a subinventory transfer. Allocating occurs when you click the Allocate button in the move order transaction window. Suggesting a Destination The picking rules only suggest source locations. revisions. to suggest source locators.  Pick release only creates move orders but does not fill in the line details. Replenishment Move Order These move orders are generated by kanban cards where the pull sequence calls for a subinventory transfer (intra-organization kanbans). Suggesting Sources Oracle Inventory uses the picking rules you set up at the organization or organization-item level. If no approval process is used. the requisition becomes a move order immediately. Pick slips and other shipping and inventory reports will also be available with Oracle Order Management. A user must navigate to the move order form after pick release and press the Allocate button. or by min-max planned items where the item’s replenishment source (set at the item-sub inventory level) is another sub inventory. These choices are made by setting up an organization parameter but can be overridden at pick release. Oracle Inventory generates a suggestion based on the item subinventory locator default you set up for move orders. the item subinventory defaults were used only for put away locations in the receiving process. Oracle Shipping Oracle Shipping provides two choices for when and how the user will fill in the line details. These orders are pre-approved and ready to transact. This option allows warehouse managers to determine when to release the pick to the floor and might be a better solution for implementations running a global order entry with distributed warehouse management and/or shipping.  Auto allocate --the allocating process is done at pick release instantly after the move order is created. Allocating Move Orders Allocating is the process in Oracle Inventory that uses picking rules and item transaction defaults to suggest move order line details to fulfill a move order line. Before release 11i. You can consider the allocating process as a sourcing process. These move orders are generated automatically by the Oracle Shipping Execution pick release process. No more human intervention is needed and the pick slip can be printed automatically. If the destination subinventory is locator-controlled and no locator was specified on the move order line. which you define as a subinventory in Oracle Inventory.

When you check this option in the Pick Release parameters. and these include  Oracle Advanced Pricing  Oracle Configurator  Oracle Accounts Receivable  Oracle Advanced Planning and Scheduling How to debug the OM Applications Data? Run $ONT_TOP/sql/omse11i. Additional products are available which are also integrated with Oracle Order Management. calculate the price of items on order lines.regional warehouses from the central order management location in advance and individual warehouses can schedule picks closer to actual ship time. If the user transacts less than the requested quantity. How do you create Category from backend? Using the procedure INV_ITEM_CATEGORY_PUB.CREATE_CATEGORY 25 . What does the Auto pick Confirm option do? This option should be active if you want the Pick Engine to accept the suggested values during Detailing. What is Transact Order? Once the lines have been allocated.sql by providing the Order Number. The Detailing can be made manually. Order Management: Introduction Using the Oracle Order Management (OM) Suite. This is a suggestion of sourcing material and it is called "Detailing". you can commit all of the transactions for a single move order line by selecting the lines you want to transact and clicking the Transact button. What does the Auto Detail option do? Pick Release always creates a Move Order transaction. the order remains open until the full quantity is transacted or the order is closed or canceled. the Pick Engine creates transaction lines suggestions. for example by shipping the items. This enables you to transact each detail line before or after picking the material. Header Id and Line Id. You can save and exit the move order line details without transacting if you need to print a pick slip report. The Detailing also creates a high level reservation on the material if no reservations previously existed. and send information to accounts receivable system so that invoices are created. It can be activated only if you select the Autodetail option. you can enter sales orders. The core OM products are  Oracle Order Management  Oracle Shipping Execution (SE)  Oracle Pricing These products are included when Oracle Order Management is purchased. fulfill the orders.

Reservable. an availability window is displayed which shows the following fields: Warehouse. Available Date. Request Date. and Error Message. Available. On Hand. 26 .How are the quantities calculated in the autoschedule availability window? When you turn on Autoscheduling in the Sales Order form. Returns => Order Organizer => New Order Hit Tools => Auto Schedule INV Responsibility: Item Supply/Demand => On Hand Availability How the Order Information gets stored in RA_INTERFACE_LINES Table? Descriptive Flexfield: Line Transaction Flexfield Column INTERFACE_LINE_ATTRIBUTE1 INTERFACE_LINE_ATTRIBUTE2 INTERFACE_LINE_ATTRIBUTE3 INTERFACE_LINE_ATTRIBUTE4 INTERFACE_LINE_ATTRIBUTE5 INTERFACE_LINE_ATTRIBUTE6 INTERFACE_LINE_ATTRIBUTE7 INTERFACE_LINE_ATTRIBUTE8 INTERFACE_LINE_ATTRIBUTE9 INTERFACE_LINE_ATTRIBUTE10 INTERFACE_LINE_ATTRIBUTE11 Vales Stored in Order Number Order Type Delivery Name Way Bill Count Line ID Picking Line Id Bill Of Lading Customer Item Part Warehouse Id Price Adjustment Id What setup is required In order to appear Invoice Details on Order -> Action-> Additional Information Tab? User Profile Option OM: Source Code value should match with DFF: Line Transaction Flexfield context. The fields pertaining to quantities are calculated as follows: Available: -For 'ATP' items = INV On-Hand Quantity minus outstanding demand -For 'non-ATP' items = Quantity Requested on the order line On Hand = INV On-Hand Quantity Reservable = INV On-Hand quantity minus outstanding reservations Navigation: OM Responsibility: Orders.

Is there any way to copy Item Attributes from Master Org to all Child Orgs, here the attributes are controlled at Org Level. Example: Would like to change Transactable Attribute on item TC17AGN1R for all Laddaw orgs to correspond with org L00, using Laddaw Master Hierarchy Using Copy Item Attributes Function can achieve this functionality. (N) Inventory -> Items -> Copy Item Attributes This form function launches concurrent request “Inventory Item Update Processor” which intern selects the data from the tables MTL_ITEM_VALUES_TEMP, MTL_UPDATE_RECORDS_TEMP and insert into MTL_SYSTEM_ITEMS_INTERFACE table then submit the request ‘Import Items’. Copy Item Attributes- Functionlity: 1. select Hierarchy Name 2. Select Item or Item Range or All Items. 3. Select Attribute(s).

27

4. Copy From Org : Choose Organization by Choose Button, from which you want to copy 5. 6.
attributes (Choosed Org appears in Blue Band color). Copy To Org: Select Organizations (by selecting Check box’s) to get copy from the blue band choosed org. Apply which launches concurrent request “Inventory Item Update Processor.

To extract COGS CCID based on the Segments DECLARE

28

l_cogs_segments l_combination l_seg_separator l_combination_flag l_cogs_ccid_id l_structure_id BEGIN

FND_FLEX_EXT.SEGMENTARRAY; Varchar2(250); Varchar2(2); Boolean; Number; Number;

l_combination := ‘101-345-400-7890-90’; l_seg_separator := ‘-‘; l_no_of_cogs_segments := FND_FLEX_EXT.BREAKUP_SEGMENTS(l_combination, l_seg_separator, l_cogs_segments); l_combination_flag := FND_FLEX_EXT.GET_COMBINATION_ID( 'SQLGL', -- Application Short Name 'GL#', -- Flex Field Code l_structure_id, -- Flex Field Structure ID to_char(sysdate,'DD-MON-YYYY'), 6, -- No. of Segments l_cogs_segments, l_cogs_ccid_id); End;

Min–Max Planning
You can use min–max planning to maintain inventory levels for all of your items or selected items. With min–max planning, you specify minimum and maximum inventory levels for your items. When the inventory level for an item (on–hand quantities plus quantities on order) drops below the minimum, Oracle Inventory suggests a new purchase requisition, internal requisition, move order, or job to bring the balance back up to the maximum. Oracle Inventory performs min–max planning for your items at either • Organization level • Sub inventory level. When you min–max plan at the organization level, you can optionally include the following transactions as demand in the min–max planning calculation: Unreserved sales orders, reserved sales orders, account issue move orders, and work in process component requirements. Purchase requisitions and internal requisitions for buy items and WIP unreleased jobs for make items for the suggested replenishment quantities can be optionally created. You can then turn these requisitions into purchase orders or internal orders and the unreleased jobs into jobs for the required items.

Organization Level Min–Max Planning
When you min–max plan at the organization level, Oracle Inventory looks at inventory balances, purchase requisitions, internal requisitions, internal sales orders, and WIP jobs as supply. It looks at sales orders, WIP job component requirements, and account issue move orders as demand. To use min–max planning at the organization level, you must set the item attributes used by min– max planning. You can start by setting the Inventory Planning Method item attribute to Min–max planning. You establish your minimum and maximum levels used in the calculation using the Min– Max Minimum Quantity and the Min–Max Maximum Quantity item attributes. You can optionally set

29

adjusted for order quantity modifiers: 30 . If you choose No to all the net demand options. In addition to the planning level option. Maximum Order Quantity. For buy items. Non– nettable quantities may optionally be included. • If Total Available < Minimum Quantity. Oracle Inventory offers the options to Net Reserved Orders. and Fixed Lot Size Multiplier) to further control the suggested order quantities generated by min–max planning. since you cannot generate repetitive plans. purchase requisitions. • Order Quantity = Maximum Quantity – Total Available. internal orders.the order quantity modifier item attributes (Minimum Order Quantity. Set the Make or Buy flag to Make to optionally generate unreleased jobs and to Buy to optionally generate requisitions. You also specify a Demand Cutoff Date and a Supply Cutoff Date. in which: o Minimum Quantity is the value for the Min–Max Minimum Quantity item attribute. and work in process jobs scheduled for receipt on or before the supply cutoff date. set the List Price for the item to automatically generate requisitions. Net Unreserved Orders. Net WIP Demand. you have the option of generating requisitions. you run min–max planning for your organization. suggest a new order. Oracle Inventory performs the following calculation: • Nettable Quantity on Hand + On Order = Total Available. or a report only. unplanned jobs. By selecting organization level planning. internal requisitions. o On Order is the sum of open purchase orders. and Include Non–nettable Inventory Quantities when calculating availability. Min–max planning is performed by running the Min–Max Planning report. For repetitive items. in which: o Nettable Quantity on Hand is the sum of the quantities on hand for the item across all the nettable subinventories within your organization.

Non–nettable quantities may optionally be included. The following example shows you how Oracle Inventory performs min–max planning. Oracle Inventory performs the following calculation: • Nettable Quantity on Hand + On Order – Open Demand = Total Available. Oracle Inventory creates internal requisitions for internal sales orders for Buy items when the item attribute Replenishment Source Type is set to Inventory. • • When you run the Min–Max Planning report. Oracle Inventory creates purchase requisitions for Buy items when the item attribute Replenish ment Source Type is set to Supplier. and specify No to Net Reserved Orders. o The order quantity must be greater than or equal to the minimum quantity. Oracle Inventory uses the item attribute Source Organization to determine the organization from which the internal requisition sources the item. inventory reservations. For Repetitive Items you optionally create requisitions or unreleased jobs. and WIP component demand scheduled for issue on or before the demand cutoff date. or Oracle Inventory revises the quantity upward to the minimum. adjusted for order quantity modifiers: o Oracle Inventory revises the order quantity if necessary for the quantity to be a multiple of the fixed lot size multiplier. You must also specify a ocation to serve as the default deliver to location on the requisitions. including reserved sales orders.o Oracle Inventory revises the order quantity if necessary for the quantity to be a multiple of the fixed lot size multiplier. or Oracle Inventory revises the quantity upward to the minimum. If you choose Yes to any of the net demand options. you can have Oracle Inventory create requisitions for buy items and unreleased jobs for make items by answering Yes to Restock. account issue move orders. requisitions. or Oracle Inventory revises the quantity down to the maximum. o On Order is the sum of open purchase orders. Order Quantity = Maximum Quantity – Total Available. suggest a new order. in which o Nettable Quantity on Hand is the sum of the quantities on hand for the item across all the nettable subinventories within your organization. Assume an item has the following quantity values and item attribute settings: • • • • • • Nettable quantity on hand = 25 Open supply quantity = 50 Open reserved sales order quantity = 90 Inventory planning method = Min–max planning Min–max minimum quantity = 100 Min–max maximum quantity = 500 If you run the Min–Max Planning report. For internal requisitions. in which o Minimum Quantity is the value for the Min–Max Minimum Quantity item attribute. o The order quantity must be less than or equal to the maximum quantity. o The order quantity must be greater than or equal to the minimum quantity. If Total Available < Minimum Quantity. internal orders. and work in process jobs scheduled for receipt on or before the supply cutoff date. o Open Demand is the sum of unreserved sales orders. Oracle Inventory performs the following calculations: 31 .

Below min check: 75 < 100 o The total available quantity is less than the min–max minimum quantity. B. so Oracle Inventory plans a new order. Cycle counting can also be a valuable tool to help identify patterns in the errors found. so open reserved orders total to 90. o Total available quantity is 75. If you run the Min–Max Planning report. Cycle Counting With cycle counting. Benefits of Cycle Counting Keeping inventory records accurate by correcting errors between the system on-hand (perpetual) and actual on-hand (physical quantities). With ABC analysis you can use cycle counting to count items of greater importance more frequently than those of less importance. Inventory is counted on a cyclic schedule rather than once a year. Oracle Inventory will plan an order for 425. Oracle Inventory performs the following calculations: • Total Available: (25 + 50) – 90 = (–15) o We assume that all the supply is within the supply cutoff date. • • Explaining ABC Analysis ABC Analysis is the classification of a group of items in decreasing order of annual dollar volume or other criteria. Cycle counting supports scheduled counting based on value or counting by location. for a supply total of 50. • A Group.• • • Total Available: 25 + 50 = 75 o We assume that all the supply is within the supply cutoff date. so Oracle Inventory plans a new order. and specify Yes to Net Reserved Orders. and 50%-70% by projected dollar volume. Below min check: (–15) < 100 o The total available quantity is less than the min–max minimum quantity. • B Group. and C.The B group usually represents about 20% of the times and about 20% of the dollar volume. • C Group.The C group contains 60%-70% of the items and represents about 10%30% of the dollar volume. A cycle inventory count is usually taken on regular defined basis. o We assume that all the demand is within the demand cutoff date. This array is then normally split in to three classes A. Max quantity less total available: 500 – (–15) = 515 o To bring the quantity available back to the min–max maximum. Max quantity less total available: 500 – 75 = 425 o To bring the quantity available back to the min–max maximum. Analysis of these patterns can suggest and help to prioritize 32 . o Total available quantity is (–15). and can be set up at the organization level or the subinventory level. Oracle Inventory will plan an order for 515.The A group usually represents 10% to 20% by number of items. for a supply total of 50. Most effective cycle counting systems require the counting of a certain number of items every workday with each item counted at a prescribed frequency.

Physical Inventory A physical inventory is a periodic reconciliation of system on-hand balances with physical counts in inventory. You can perform physical inventories whenever you choose to verify the accuracy of your system on-hand quantities. or once a year depending on organization requirements. and processes.improvements in training. Physical inventories are usually performed once every six months. FAQs 33 . Over a period of time these improvements may increase the average level of inventory record accuracy. You can perform a physical inventory for an entire organization or for particular subinventories within an organization. tools.

Delivery: A delivery consists of a set of delivery lines that are scheduled to be shipped to a customer’s shipto location on a specific date and time. In a delivery, you can include items from different sales orders as well as back orders. You can group multiple deliveries together to create a trip. More than one trip may be required to complete a delivery. For example, a delivery can consist of two trips, the first trip by truck and the second trip by rail. Picking Rules Move orders will use the picking rules set up in Oracle Inventory to locate the material required to fulfill the move order line. Together with item-sub inventory defaults (required if the staging sub

34

inventory is locator controlled), the picking rules suggest the staging transfer transaction lines with appropriate source information that will be required to obtain enough material in the staging location for the delivery. The process where the Picking Engine generates these transaction line suggestions is called allocating. How system determines Pick from Sub inventory/Locator to do pick release from shipping Transaction form? Thru Pick Rule Based on Picking rule, assigned to the Item (1st in mtl_system_items) if Null then from mtl_parameters then where it looks for that inv. org Configuring Your Picking Process: You can determine the number of pick release steps the system will prompt to move material from pick release to ship confirmation. These steps are: 1. Pick Release 2. Move Order Line Allocation (detailing) 3. Move Order Line Pick Confirmation 4. Ship Confirmation Pick Release Pick Release finds and releases eligible delivery lines that meet the release criteria, and creates move orders. You can pick release by order, trip, stop, container, delivery, warehouse, and customer, scheduled, or requested dates, shipment priority or combinations of the above criteria. The default release criteria are set up in Shipping Parameters, but you can override the default criteria in the Release Sales Order window at pick release. The move orders create a reservation, determine the source, and transfer the inventory to staging areas. Pick Slips can be created after the detailing process completes, and the quantity and source can be manually verified at pick confirm. Detailing and pick confirmation can be manually transacted through inventory or set up in Shipping Parameters to occur automatically at pick release. You can run one or more releases and customize release criteria to meet your requirements. You can define:   Release Rules to specify you’re picking criteria through pick release parameters. Release Sequence Rules specify the order in which eligible delivery lines are released. The order in which delivery lines are released using a Release Sequence Rule is based on the following attributes:  Order number  Outstanding invoice value  Scheduled date  Departure date  Shipment priority Pick Slip Grouping Rules to determine how released move order lines are grouped onto pick slips.

Oracle Shipping Execution’s Pick Release process creates move orders. One order is created per pick release batch per organization, so if you pick release across multiple organizations, one move order is generated in each facility. One move order line is generated for each order line included in

35

the picking batch. That move order line includes the item, quantity, the staging location (the destination sub inventory and locator) and a source sub inventory and locator if one was specified on the sales order line or on the Release Sales Orders window. For non-transactable items, pick release does not use the value of Enforce Ship Sets and Ship Models in the shipping parameters. However, ship confirm does validate non-transactable items for broken ship sets and ship models. For non-reservable items, allocation and pick release run, but suggestions are not created during pick release, and pick confirm will not run for the item. You can print pick slips, but they will not be detailed with sub inventory and stock locator to pick from, however they will list the item and quantity to be picked. Auto-allocate should be Yes and Auto-pick-confirm can be set to any. Detail Line Allocation (Detailing) To release the move order lines created at Pick Release to the warehouse and to print pick slips, the lines must be allocated. The allocation process for a pick wave move order line also creates a high level (organization level) reservation for the item(s) if no previous reservations exist for them. You can choose to do this immediately after the move order lines are created or to postpone this step until a later point in time. Once the lines are allocated, they have a status of Released to Warehouse. Postponing the detailing process might be employed by organizations that pick release across multiple warehouses but prefer to enable each warehouse to determine when to release their order lines to the floor. Detailing the order lines immediately after they are created is called auto-detailing. Postponing the detailing process is referred to as manual-detail. You can set up a default detailing mode in the Shipping Parameters window. This default can be overridden at each Pick Release through the Release Sales Orders window. Pick Confirmation The move order line details must be transacted (in Inventory) to confirm the material drop-off in staging. Pick confirmation executes the sub inventory transfer that systematically moves the material from its source location in the warehouse to the staging location. Pick Confirmation automatically transfers the high level reservation to a allocated reservation (including lots, sub inventory and locators) in the staging location. Inventory updates Shipping Execution with the results of the pick confirm:  Pick Confirmed quantity is assigned a status of Staged/Pick Confirmed.  Unconfirmed quantity is assigned a status of Backordered. At pick confirmation, you can report a missing quantity or change information if material is picked from a different lot, serial, locator, or sub inventory. Auto pick confirm can be set up as the default to occur immediately after the lines are detailed if an organization’s picks rarely deviate from the suggested picking lines or the overhead of requiring a Pick Confirmation is unmanageable. You can set up a default Pick Confirm policy in the Inventory organization parameters. This default can be overridden at each Pick Release. Pick confirmation follows the allocation and reservation process automatically if both the Auto Allocate and Auto Pick Confirm options are selected in the Release Rules window. Pick Confirm always follows the detailing and reservation process. If Auto Allocate is not chosen, it is not possible to Auto Pick Confirm. After you perform a partial move transaction on a move order, the delivery detail shipped quantity is usually blank. However, if the move order is for a serial controlled item, the shipped quantity appears. Generally, the requested quantity of a staged delivery detail is the shipped quantity because the non-shipped quantity is split into separate backorder delivery lines. However, for delivery details with serial controlled items, the shipped quantity has a value so that you can enter the serial numbers when transacting.

36

If adequate quantity is not available to detail the mover order. This is done in the Release Sales Orders for picking window. Once you have made your changes you can transact the move order to pick confirm the inventory. The detailing process fills in the move order line details with the actual transactions to be performed. which creates a move order that is automatically detailed but enables you to view the pick recommendation and provides the opportunity to change quantity. Shipping Transactions window: You can run pick release in the Shipping Transactions window by selecting Launch Pick Release from the Actions menu. This window can also be accessed from the Tools menu in the Shipping Transactions window. location.  Standard Report Submission (SRS): You can run a specific release at the same time every day. SRS runs pick release in the background multiple times. you can transact the mover order to pick confirm the transaction. If no reservations exist before the detailing process. it also creates reservation for the material. One Step process consists of select both auto-detail and auto pick confirm checkboxes on the inventory tab when you pick release. sub inventory and to report a missing quantity at the pick confirmation step in the transact move orders window. With the new pick release engine. enabling you to run other processes simultaneously. Once detailed. Two Step process consists of selecting auto-detail.Pick Release can be run using the following methods:  On-line: You can pick release one order immediately. Using the new engine can be performed a one-two or three-step process.  Material Picking or Pick Release: Oracle shipping execution enables you to use move orders Transactions for generating pick requests and reservation in Oracle Inventory. which means that the pick recommendation is automatically created and pick confirmed without any manual interaction. What does Detailing mean? Detailing is the process which Oracle Order Picking and Shipping uses the picking rules to determine where to source the material to fulfill the request line (move order line). thereby eliminating time spent waiting for the order to process through the Concurrent Manager queue.  Concurrent: You can run pick release in the background. This is done in the Release Sales Orders for picking window. which creates a move order that you can manually or automatically detail in the transact move order window. Three Step process consists of selecting neither the auto-detail or auto pick confirm check boxes. This is done in the Release Sales Orders for Picking SRS window. this process can be repeated later. You can also pick release items on a delivery. you can pick release all items together on a trip or stop. This window can also be accessed from the Tools menu in the Shipping Transactions window. but not auto pick confirm. What is the difference between Available Qty and On-Hand Qty? Available Qty + Reserved Qty = On-Hand Qty What is the difference between concurrent or on-line pick releases? 37 .

the balance of the sales order may be backordered. Ship Confirmation The material picking process ends when the items are ship confirmed out of inventory. For example. related deliveries. you may prefer to automatically create trips:   Auto-creating a trip for a delivery: You can find the delivery you want to ship. Ship confirming the items removes the existing reservations and performs the sales order issue transaction. What is meant by Trips? How to create Trips? Overview: A trip is an instance of a specific freight carrier departing from a particular location containing deliveries. When you manually create a trip. The user can continue working with the application even though the pick release has not completed yet. What is Item Cross References used for? Cross Reference types define relationship between Items and entities such as Customer Items or Supplier Items. and may include intermediate stops. On-line pick release releases the orders while the user waits for the application to returns the control to the user. You may choose to ship confirm only part of the sales order quantity. you can manually assign stops. Creating a Trip There are several ways to create a trip:  Automatic  Manual Automatic If your shipping process does not require advanced planning. In this case. The first line represents the shipped quantity. Manual During transportation planning. The backordered line is automatically Pick Released by Oracle Shipping Execution. and autocreate a trip and related trip stops. Back ordering at Ship Confirm automatically splits the sales order into two lines. you can manually set up a trip ahead of time and then assign delivery lines. and delivery lines to that trip. What is the effect of the following transactions on On-Hand Qty? Sub Inventory Transfer Miscellaneous Issue On-Hand Qty remains same on a Sub-Inventory transfer. deliveries. The user may feel a lower performance in the applications depending of how many lines are being processed. A move order line is automatically generated for the backordered quantity.Concurrent pick release releases one or more orders in the background improving the performance for the user. and the second line represents the backordered quantity. On-Hand Qty reduces on Miscellaneous Issue 38 . A trip is carrier specific and contains at least two stops such as a stop to pick up goods and another stop to drop off goods. you can manually create a trip and later assign delivery lines or find the delivery lines and create a trip. Trips can be created automatically or manually. and trip stops. Auto-creating a trip for containers and lines: You can find the lines and containers you want to ship and auto-create a trip which creates a trip. for a regular trip scheduled to depart every Friday.

What is meant by RMA? Return Material Authorization. It also allows the user to prevent breaking LPNs or lots by small amounts when the quantity requested does not match the quantity in inventory. free goods. than what was released. What are the different types of Modifiers? Discount List. What does Pick Release mean? An order cycle action to notify warehouse personnel that orders is ready for picking. This means that there will not be an option for backporting of this code.Return Material Order. at Ship confirm. What does ATP mean? What is the significance of ATP? Available to Promise. What is Over Picking? Over picking is a new enhancement included in the Order Management family pack G(2118482) that allows the Pick Confirm transaction to pick in excess of the requested quantity as long as it is within the over shipment tolerance. only header data is available. How are Backorders handled /processed? 39 . (For example. Freight and Special Charges. And backorders caused by shipping less. instead of picking exactly 5 cans. What are defaulting Rules? Information that Oracle Order Management automatically enters depending on other information you enter.What is a Modifier? Modifiers enable you to setup price adjustments. What is Back order? When it occurs? In the Back Order the material gets unreserved. and the warehouse either is out of individual cans or has a policy against loose cans. benefits (for example. Is the Customer Site data available across the operating units? No. Backorders caused by Pick Releasing (PR) order lines when there is no or not enough stock available. In order to receive this code. Explain Credit Check and Credit Hold for a Customer Site? Credit Check is a check carried by the System the customer is exceeded his credit limit. Credit hold is a hold applied on orders when he exceeds his credit limit. Pick release rule A user-defined set of criteria to define what order lines should be selected during picks release. Promotion surcharge. OM Family Pack G or higher family pack needs to be applied. This functionality will not be offered prior to OM Family Pack G code release. coupons) and freight and special charges that the price Engine applies immediately to pricing requests or accrues for later disbursement. For example. if the customer ordered 5 cans and the warehouse have only 6-packs. . discounts and surcharges). The over picking functionality allows the picker to pick a 6-pack (6 cans wrapped) to fulfill the order.

the system will not print pick slips for lines that are not detailed. there is a check box labeled Close Trip. If the check box is not checked. the second 'Submitted for Release' (Move Order created. the original order line will be split into a 'Shipped' and a 'Submitted for Release' line (unless the shipped quantity falls within the under shipment tolerance). Only when the original delivery line is interfaced through Inventory Interface/Order Management Interface. Pick Release is able to distinguish between the two. then you have to manually go to the stop tab and close a stop. The delivery line. In R11i.As in previous releases. After Ship Confirming the Released delivery line. If that check box is checked. The order line will not split at this point. you have can either designate the remaining quantity as 'Backordered' (meaning the quantity was lost somewhere along the picking/staging process) or leave it in staging in to assign it to a different delivery (i. there is no order or workflow status called 'Backorder'. Once a stop is closed. Order Management and Shipping Execution has two types of Backorders. It will create move order lines for each line. Backorders Caused by shipping less than what was Released Before Ship Confirming a Released (Pick Confirmed) delivery line. because it allows you to release them separately. Set the profile INV: Detail Serial Numbers to ‘Yes’. The first delivery line will become status ‘Released’ (Pick Confirmed). A. the Trip and associated stops are closed when the delivery is closed. A backordered quantity will remain noted on the same delivery line. You (or the system) will however. Also. you have the option to update the shipped quantity. any staged quantities will be split off in a separate delivery line that is immediately ready to be shipped in a subsequent delivery.e. And backorders caused by shipping less. In the latter case. but not confirmed). At Ship Confirm. be released after the hold has been removed? Create a new delivery. Inventory will then suggest serial 40 . you cannot switch off reservations for PR. but receives a 'Picked partial' status. truck was full and wait for next pick up). This split will only happen if the backordered quantity is greater than the Under Shipment Tolerance. which was 'Ready to Release' before running PR will be split into a quantity that was available for picking and a unavailable quantity. the Inventory and OM Interface are submitted. The latter will be available for Pick Release as a 'Backorder' as soon as there is stock available. You will not really see any difference between a scheduled order line that was never released and a backordered line. How come when I ship confirm a delivery the Inventory and OM Interface are not run? When ship confirming a delivery. Backorders after Pick Releasing with Insufficient Stock Pick Release will process all order (more correctly shipping) lines that you selected when submitting PR. will the order line be split into a line for the shipped quantity and a new line for the backordered quantity (Awaiting shipping). at Ship confirm. This enables you to pick the remaining quantity again in order to fulfill the complete order quantity. On the sales order. assign the lines to the new delivery and perform the ship confirm process. not be able to (auto) detail and (auto) Pick Confirm the lines where there is not enough stock available. How can lines that were unassigned from a delivery a time of ship confirm due to a credit hold. the ‘Details Required' status is checked. Backorders caused by Pick Releasing (PR) order lines when there is no or not enough stock available. How can I ship the fastest way? Check the Autodetail option in Pick Release. If the shipped quantity is less than the picked quantity. whether there is stock available or not. B. than what was released. It can be defaulted from the Shipping Parameters form.

numbers during the Detailing process. Purchase release. orders. there is no shipping involved. It uses the following attributes: order number. and items. schedule date. ORG_ID can be set at Master Level or Transaction Level? ORG_ID can be set at Transaction Level. The invoice can be done only after the receipt is made for the purchase order created by the purchase requisition created from the Purchase release. What are the Different Types of Sales Orders Flows?  Standard Sales Order Flow  Drop Ship Order Flow Internal Sales Order Flow CTO Configure To Order Assemble To Order Back To Back Order (Procure To Order) Flow Return Material Authorization (RMA) What is meant by drop shipment order type? What are the different steps involved in executing sales order? In the Drop shipment order. The steps involved are Book the Order. Invoicing. customer sites. While shipping we can over/under shipping the quantity in the sales order. How do restrict data for a responsibility as per the ORG_ID? Through Multi-Org you can restrict data for a responsibility as per the ORG_ID. Set of book id should have the value to restrict the data for a responsibility. Hold source An instruction for Order Management to place a hold on all orders or lines that meet criteria you specify. A pick release process may print more that one report for the same picking batch. What is Hold management? Hold A feature that prevents an order or order line from progressing through the order cycle. You can place a hold on any order or order line. A hold criteria can include customers. Warehouses are what organizations in Oracle Manufacturing? Inventory What is meant by shipment tolerance? Over/Under shipment tolerance. Do not check the Pick Confirmation Required flag in the Organization Parameters form. How does the pack slip report groups the released lines? It uses the pick slip grouping rule assigned during the pick release. Create a hold source when you want to put all current and future orders for a particular 41 . outstanding invoice value. Only in GL. Hold criteria A criterion used to place a hold on an order or order line. What is the difference between Standard Sales Order Cycle and Drop Shipment Order Cycle? Shipment is the difference. departure date and shipment priority. What criteria use the process to release the eligible order lines? This is indicated by the Release Sequence Rule.

What are the prerequisites of the Sales Order? Customer. Returnable *Customer should be “Internal” Can you update the Sales Order once it is Booked? Depends on the Processing Constrains setup. *Internal Order. Check Material Storage Bill of Material Tab BOM Allowed Purchasing Tab Purchased Purchasable Use Approved Supplier General Planning Tab Make or Buy Source Type: Supplier Lead Times Tab Preprocessing –give some values Work-in-process Tab Build in WIP Order Management Tab Customer Ordered. Revision Control Receivable. Transact able. Customer Enabled.*Stock able. Shippable. *Internal Order Enabled. Order Management gives you the power to release holds for specific orders or order lines. What are different order types?  Order  Return  Mixed 42 . Assemble To Order. Price List and Order Type. *OE Transact able. Oracle Order Management holds all new and existing orders for the customer or item in your hold source until you remove the hold source. while still maintaining the hold source. Hold type Indicates the kind of hold you place on an order or order line.customer or for a particular item on automatic hold. What is the Item attributes for an Item to create Drop Ship Order? Purchased (PO) Enabled Purchasable (PO) Enabled Translatable (INV) Enabled Stock able (INV) Optional Reserveable (INV) Enabled Customer Ordered (OM) Enabled Customer Orders Enabled (OM) Enabled Default SO Source Type Optional Shippable (OM) Enabled Transact able (OM) Enabled Costing Enabled (enabled for items that are to be costed) Inventory Asset Value Enabled (for asset items) (non-expense items) What is the Item attributes for an Item to create Internal Sales Order? Main Tab Standard Inventory Tab *Inventory Item.

Open Interfaces 43 .

or assign existing items to additional organizations. You can specify values for all the item attributes. update existing items. or you can specify just a few attributes and let the remainder default or remain null. they are not processed into Oracle Inventory.Open Interface: Import Items The Item Interface lets you import items into Oracle Inventory and. you create new items in your item master organization. When you import items through the Item Interface. the interface runs only for the current organization and interface table rows for other organizations are ignored. The Item Interface also lets you import revision details. and now want to 44 . Indicate whether to validate all items and their data residing in the interface table that has not yet been validated. if installed at your site. Oracle Engineering. Import Items Parameter All Organizations Validate Items Meaning Indicate whether to run the interface for all organizations in the item interface table. so you are insured of valid items. You would choose No if you had previously run the item interface and responded Yes for Validate Items and No for Process Items. If items are not validated. Validation of imported items is done using the same rules as the item definition windows. If you choose No. including past and future revisions and affectivity dates.

you run the Item Interface to import the data. validates data you include.CREATE_ITEM 45 . This table is used only for revision information. Indicate whether to delete successfully processed items from the item interface tables. Steps: Before you use the Item Interface. and is not required. Indicate whether to process items. select Import Items from the Import submenu. Concurrent program: Import Items To run the Item Interface. A fourth table. The Item Interface assigns defaults. If you choose Yes. You can also use the Item Interface to import item material cost. and item category assignment records into these interface tables. accessed from the Inventory menu. revision. You would choose No. or select Import Items in the Request Name field in the All Reports window Interface Item Interface Interface Tables MTL_SYSTEMS_ITEM_INTERFACE MTL_ITEM_REVISIONS_INTERFACE MTL_ITEM_CATEGORIES_INTERFACE MTL_ INTERFACE_ERRORS Concurrent Program Import Items (INCOIN) Concurrent Program Import Items Main Tables MTL_SYSTEMS_ITEM_B MTL_ITEM_REVISIONS MTL_ITEM_CATEGORIES Interface Table MTL_SYSTEM_ITEMS_I NTERFACE Error Table MTL_INTERFACE_ ERRORS Actual Table MTL_SUYSTEM_I TEMS_B API To Create Item: INV_ITEM_GRP. This is the main item interface table. If you are importing revision details for your new items. and (if revision detail is included) the MTL_ITEMS_REVISIONS_INTERFACE table. Interface Tables: The Item Interface reads data from three tables for importing items and item details. the MTL_ITEM_CATEGORIES_INTERFACE table is used to store data about item assignments to category sets. MTL_ INTERFACE_ERRORS. is used for error tracking of all items that the Item Interface fails. and revision details. as well as the MTL_ITEM_ CATEGORIES_INTERFACE table. To import item category assignments. material overhead. and categories to be imported into the Oracle Inventory MTL_ITEM_CATEGORIES table. After you load item. You can use the MTL_ITEM_REVISIONS_INTERFACE table. and then imports the new items. and may be the only table you choose to use. to remove successfully processed rows from the interface table without performing any other processing. all qualifying items in the interface table are inserted into Inventory. Choose No to leave all rows in the item interface tables for successfully processed items.Process Items Delete Processed Rows process your items. along with Yes for Delete Processed Rows. you must write and run a custom program that extracts item information from your source system and inserts the records into the MTL_SYSTEM_ITEM_INTERFACE table. You use the MTL_SYSTEMS_ITEM_INTERFACE table for your new item numbers and all item attributes.

After you load item. 3). validates included data. revision. as well as the MTL_ITEM_CATEGORIES_INTERFACE table. import failed 5 = Import in process 7 = Import succeeded Open Interface: Item Category Assignment Open Interface MTL_ITEM_CATEGORIES_INTERFACE table to store data about item assignments to category sets. TRANSACTION_ID Enter Transaction ID TRANSACTION_TYPE CREATE = to create an item record (true when both importing a new item and assigning an already existing item to another organization). 1 = Pending 2 = Assign complete 3 = Assign/validation failed 4 = Validation succeeded. 1. a corresponding value of 1.UPDATE_ITEM How can I run Item Open Interface in parallel mode. The set_process_id identifies the process request via a numeric parameterand cannot be set to null. A table. When the interface is scheduled on the interface scheduler. 46 . and categories to be imported into the Oracle Inventory MTL_ITEM_CATEGORIES table. each batch can be set with a different set_process_id (i. The Item Open Interface assigns defaults.. SET_PROCESS_ID Enter an arbitrary number. and then imports the new items.To Update Item: INV_ITEM_GRP. MTL_SYSTEM_ITEM_INTERFACE Table: Column Name Instruction ITEM_NUMBER Enter Item Number DESCRIPTION Enter Item description ORGANIZATION_CODE Enter the organization that the new item will import into. MTL_INTERFACE_ERRORS. This is the only value currently supported by the Item Interface. CATEGORY_SET_ID Enter Category Set ID CATEGORY_ID Enter Category ID PROCESS_FLAG Enter 1 for pending data to be imported. you run the Item Open Interface to import the data. Rows designated with the same Value for SET_PROCESS_ID will process together. you must write and run a custom program that extracts item information from your source system and inserts the records into the MTL_SYSTEM_ITEMS_INTERFACE table. This defines which records are processed by that request and allows the 3 processes to run in parallel. For example. to enhance performance? There is a new field in the mtl_system_items_interface table called set_process_id. 2. and item category assignment records into these interface tables. if you wish to run 3 parallel processes. it is possible to process more than one batch at a time through the interface. 2 or 3 can be entered as the last parameter in the schedule request. By populating this field. Before using the Item Open Interface.e. and (if revision detail is included) the MTL_ITEMS_REVISIONS_INTERFACE table. is used for error tracking of all items that the Item Interface fails.

Rows designated with the same Value for SET_PROCESS_ID will process together. Item Category Assignment gets created for both Master and Child Organizations.CREATE_CATEGORY INV_ITEM_CATEGORY_PUB.CREATE_CATEGORY_ASSIGNMENT FND_FLEX_EXT. import failed. indicating the results of the import 1 = Pending 2 = Assign complete 3 = Assign/validation failed 4 = Validation succeeded. DELETE to delete already existing assignment. This is application for both ways i. To get the Code Combination ID API INV_ITEM_GRP. thru Interface or through API. After running the import process.Interface Table MTL_ITEM_CATEGORIES _INTERFACE Concurrent Program Item Category Assignment Open Interface (INV_ITEM_CAT_ASSIGN_OI) Error Table MTL_INTERFACE_ ERRORS Actual Table MTL_ITEM_CATEGORIES API INV_ITEM_CATEGORY_PUB. the PROCESS_FLAG of the corresponding rows will be set to different values.UPDATE_ITEM INV_ITEM_CATEGORY_PUB. Ex: ‘101’-2001-30014001’ into an array of segments. 5 = Import in process 6 = Import succeeded TRANSACTION_TYPE SET_PROCESS_ID ORGANIZATION_CODE CATEGORY_SET_ID CATEGORY_ID ITEM_NUMBER CREATE to create a new item UPDATE to update existing items.BREAKUP_SEGMENTS FND_FLEX_EXT. Enter Category Set ID Enter Category ID Enter Item Number Note: In case you pass Master Organization ID to the Table MTL_ITEM_CATEGORIES_INTERFACE.GET_COMBINATION_ID Customer Item and Customer Item Cross-Reference Open Interfaces 47 . Enter the organization that the new item will import into.e. Enter an arbitrary number. APIs: Purpose To Update Inventory Item To Create Item Category To Assign Item to Category To Break up the Code into an array of segments. CREATE_CATEGORY _ASSIGNMENT MTL_ITEM_CATEGORIES_INTERFACE Table: Column Name Instruction PROCESS_FLAG Enter 1 for pending data to be imported.

Functional Overview . The information provided in these fields is validated against the Oracle table RA_CUSTOMERS. it is applicable to all organizations assigned the cross-referenced Inventory Item. For each customer item you must define related information such as the Customer and Item Definition Level. you run the Customer Item Interface. Customer Item Definition Level. You create a cross-reference to the associated Oracle Inventory item by specifying the item and its Master Organization. Interfaces will error out with the appropriate error code if the customer information cannot be validated. You first add the customer item cross-reference records to the MTL_CI_XREFS_INTERFACE table.Customer Item Cross-Reference Interface The Customer Item Cross-Reference Interface lets you import cross-references between customer items and existing Oracle Inventory items into your Master organization. Interface Table MTL_CI_INTERFACE MTL_CI_XREFS_INT ERFACE Concurrent Program Import Customer Items Import Customer Item Cross References Error Table Actual Table MTL_CUSTOMER_IT EMS MTL_CUSTOMER_IT EM_XREFS API Table MTL_CI_INTERFACE: CUSTOMER_ITEM_NUMBER CUSTOMER_ITEM_DESC CUSTOMER_ID CUSTOMER_NUMBER CUSTOMER_NAME Customer Item Number Customer Item Description You define a customer by populating either of the CUSTOMER_NAME. 48 . and Rank. For each customer item cross-reference. Validation of the customer items uses the same rules as the Customer Items window to ensure that only valid items are imported. Note that at least one of these fields must be entered for validation.Functional Overview . you must define the Customer. CUSTOMER_NUMBER. You can also create multiple cross-references between Oracle Inventory items and one customer item. Validation of the customer items cross-references uses the same rules as the Customer Item Cross-References window to ensure that only valid cross-references are imported. In addition. Customer Item. or CUSTOMER_ID fields. The Customer Item Interface reads each record from the interface table and adds items that are successfully validated to the MTL_CUSTOMER_ITEMS table. If more than one field is populated to identify a customer. then only the data in the highest priority field is used for validation according to the following rules of precedence: ■ CUSTOMER_ID has priority over CUSTOMER_NUMBER. Then the Customer Item Cross-Reference Interface validates each record and moves the successfully validated items to the MTL_CUSTOMER_ITEM_XREFS table. Cross references are defined at the Master Organization level of the cross-referenced inventory item. Customer Address is required if you set Item Definition Level 3 while Customer Category is required for Item Definition Level 2. Model Items and other attributes such as Demand Tolerances and Departure Planning Flags for each customer item After you add new customer items to the MTL_CI_INTERFACE table. Commodity Codes. Once a customer item cross-reference to an Inventory item has been defined. you can provide Master and Detail Container information. You can create multiple cross-references between customer items and one Oracle Inventory item.Customer Item Interface The Customer Item Interface lets you import customer items into Oracle Inventory.

TRANSACTION_TYPE ERROR_CODE ERROR_EXPLANATION PROCESS_FLAG PROCESS_MODE ■ CUSTOMER_NUMBER has priority over CUSTOMER_NAME. and derives or defaults any additional columns. you insert the rows in the interface table and call a Transaction Worker directly. These transactions could include sales order shipment transactions from an order entry system other than Oracle Order Entry. passing the group identifier of the interfaced transactions as a parameter so that the worker can recognize which subset of transactions to process. Note that these are required columns and should be populated with 1. or they could be simple material issues. picking up all transactions from the history table that have not yet been marked as costed. Next. TRANSACTION_TYPE is a required field. This is the only value supported currently by this interface. and launches a Transaction Worker to process each group. Once the transaction has been successfully processed. Open Transaction Interface Oracle Inventory provides an open interface for you to load transactions from external applications and feeder systems. updates the error code and explanation if a validation or processing error occurs. Always set the TRANSACTION_TYPE to CREATE to create a new item in the MTL_CUSTOMER_ITEMS table. All material movement transactions update inventory perpetual balances for the issue. The Transaction Worker calls the Transaction Validator which validates the row. you must also insert rows into MTL_TRANSACTION_LOTS_INTERFACE and MTL_SERIAL_NUMBERS_INTERFACE respectively. Error Code Error Description The PROCESS_FLAG and PROCESS_MODE columns report the status of the record after the import and validation process is complete. There are two modes you can use to process your transactions through the interface. Data already in these columns is ignored and overwritten if necessary. groups the transaction rows. or transfers loaded from data collection devices. In the second processing mode. 49 . receipts. For material movement of items that are under lot or serial control. the Transaction Processor records the transaction details in the transaction history table along with relevant current cost information. the corresponding row is deleted from the interface table. The interfaces will error out if a required field is missing or contains invalid data. the transaction is costed by the transaction cost processor which runs periodically. or transfer locations. you populate the interface table only. In the first processing mode. Then the Transaction Manager polls the interface table asynchronously looking for transactions to process. receipt. Finally. The following transaction types are supported by this interface:  Inventory issues and receipts (including user-defined transaction types)  Subinventory transfers  Direct inter-organization transfers  Intransit shipments  WIP component issues and returns  WIP assembly completions and returns  Sales order shipments  Inventory average cost updates You must write the load program that inserts a single row for each transaction into the MTL_TRANSACTIONS_INTERFACE table.

WIP Issue Transactions WIP issue transactions also update quantity issued for all material requirements on the job or repetitive schedule and charge the costs of issued components to the job/schedule. QUANTITY_UPDATE MTL_INTERFACE_ERRORS Actual Table: MTL_MATERIAL_TRANSACTIONS Transaction Interface Bill and Routing Interface Functional Overview: Interface Bill and Routing Interface Interface Tables BOM_BILL_OF_MTLS_INTERFACE BOM_INVENTORY_COMPS_ INTERFACE BOM_REF_DESGS_INTERFACE Concurrent Program Bill and Routing Interface Main Tables 50 . Line. Average Cost Transactions In average cost organizations. launch appropriate backflush transactions. you must specify the sales order demand details so that Oracle Inventory can reserve the completed units to the appropriate sales order line/shipment. Inventory Issue Transactions Inventory Issue transactions consume any existing reservations where the Transaction Source Type and Source match.Additional Transaction Processing Flow Steps The following transactions require additional processing by the transaction processor or other modules. Sales Order Shipment Transactions For sales order shipment transactions. Delivery. WIP Completion Transactions WIP completion transactions update the job or repetitive schedule completed quantities. on-hand quantity. and relieve costs of completed assembly from the job/schedule. and then you issue 4 boxes to that department. the Transaction Processor attempts to consume any reservations that may have been created for an order by matching the Order. with a remaining balance of 6 reserved boxes. For example. and the transaction value and quantity (if appropriate) to calculate the new average. the reservation will automatically be partially consumed. If the WIP completion/return transaction completes or return job assemblies in an average costing organization. the processor also creates an interface row in MRP_RELIEF_INTERFACE that the MRP Planning Manager uses to relieve the Master Demand Schedule. If MRP is installed. Interface Interface Tables MTL_TRANSACTIONS_INTERFACE MTL_TRANSACTION_LOTS_INTERFACE MTL_SERIAL_NUMBERS_INTERFACE Concurrent Program Process transaction interface Error Tables API INV_QUANTITY_TREE_PUB. If you are completing an ATO assembly. and Picking Line identifiers. if you reserved 10 boxes of paper for the Finance department. receipts and average cost update transactions modify the item’s average cost using the current average cost. the rows in the CST_COMP_SNAP_INTERFACE table are transferred to the CST_COMP_SNAPSHOT table so that completion costs can be calculated.

Process. or Procedure Name Oracle Inventory Transactio ns Inbound MTL_TRANSACTIONS_INTERFACE MTL_SERIAL_NUMBERS_INTERFACE MTL_TRANSACTION_LOTS_INTERFAC E MTL_ITEM_QUANTITIES_VIEW MTL_SYSTEM_ITEMS_INTERFACE MTL_ITEMS_REVISIONS_INTERFACE MTL_CI_INTERFACE MTL_CI_XREFS_INTERFACE Oracle Inventory Oracle Inventory Oracle Inventory Oracle Inventory On-Hand Balances Item Customer Item Customer Item CrossReferences Material Outboun d Inbound Inbound Inbound View Table Table Table Oracle Inventory Inbound Table MTL_TRANSACTIONS_INTERFACE MTL_SERIAL_NUMBERS_INTERFACE MTL_TRANSACTION_LOTS_INTERFAC E BOM_BILL_OF_MTLS_INTERFACE BOM_INVENTORY_COMPS_ INTERFACE BOM_REF_DESGS_INTERFACE BOM_SUB_COMPS_INTERFACE MTL_ITEMS_REVISIONS_INTERFACE Oracle Bills of Material Bill of Material Inbound Table 51 . or Procedur e Table Table. View.BOM_SUB_COMPS_INTERFACE MTL_ITEMS_REVISIONS_INTERFACE BOM_EXPORT_TAB BOM_SMALL_EXPL_TEMP Open Interfaces: Product Interface/A PI Name Data Flow Direction Table. View. Module Name.

or internal orders created for internal requisitions developed in Oracle Purchasing or returns. reservations. Order Import can import changes for existing Sales Orders. for example. and sales credits in the base Order Management tables. updating or deleting the orders in the base Order Management tables. legacy systems. Each time you run Order Import.BOM_EXPORT_TAB BOM_SMALL_EXPL_TEMP Oracle Work in Process Order managem ent Move Transactio n Order Header Order Lines Inbound Table WIP_MOVE_TXN_INTERFACE CST_COMP_SNAP_INTERFACE (if OE_HEADERS_IFACE_ALL OE_LINES_IFACE_ALL Open Interface: Order Import Order Import is an Order Management Open Interface that consists of open interface tables and a set of APIs. Order Management checks all the data during the import process to ensure its validity within the module. scheduling of shipments. If the order is imported as BOOKED then during the post booking process (when the Line status becomes AWAITING SHIPPING from BOOKED) will cause data to be written in the WSH_DELIVERY_DETAILS and WSH_DELIVERY_ASSIGNMENTS tables. processing constraint checks. and finally inserting. Order Import features include validation and defaulting. price adjustments. and if succeeded or failed. It is to be noted here that Order Import does not populate any Shipping tables. Order Management produces a summary of information letting you know of the total number of orders that Order Import has evaluated. EDI transactions that are processed by the Oracle e-Commerce Gateway. Valid transactions are then converted into orders with lines. new and completed sales orders or returns from various sources. 52 . both Oracle and Non Oracle. applying and releasing of order holds.

Form Field Order Type Price List Salesperson Customer Number Org ID Warehouse OE_ORDER_HEADERS_ALL ORDER_TYPE_ID PRICE_LIST_ID SALESREP_ID SOLD_TO_ORG_ID SOLD_FROM_ORG_ID SHIP_FROM_ORG_ID Table Name OE_TRANSACTION_TYPES_ALL QP_PRICE_LISTS_V RA_SALESREPS_ALL HZ_CUST_ACCOUNTS or OE_SOLD_TO_ORGS_V HR_OPERATING_UNITS ORG_ORGANIZATION_DEFINITIONS Column Name TRANSACTION_TYPE_ID PRICE_LIST_ID SALESREP_ID Other Columns NAME NAME SALESREP_NUMBER PARTY_ID CUST_ACCOUNT_ID ORGANIZATION_ID ORGANIZATION_ID ORGANIZATION_ID NAME SITE_USE_CODE= SHIP_TO LOCATION View Columns: LOCATION_ID NAME SITE_USE_ID CUSTOMER_ID ADDRESS_LINE_1 ADDRESS_LINE_2 ADDRESS_LINE_3 ADDRESS_LINE_4 TOWN_OR_CITY POSTAL_CODE COUNTRY SITE_USE_CODE= BILL_TO LOCATION View Columns: LOCATION_ID Ship To Location SHIP_TO_ORG_ID HZ_CUST_ACCT_SITES_ALL HZ_CUST_SITE_USES_ALL Or OE_SHIP_TO_ORGS_V SITE_USE_ID Bill To Location INVOICE_TO_ORG_ID HZ_CUST_ACCT_SITES_ALL HZ_CUST_SITE_USES_ALL Or OE_INVOICE_TO_ORGS_V SITE_USE_ID 53 .

CREDIT'. PRICE_LIST_ID. Custmer Id : ============= select PARTY_ID from hz_cust_accounts where CUST_ACCOUNT_ID = 57654 -. --PRICE_LIST_ID=218220 Saesrep ID: =========== select * from ra_salesreps_all where name='ICO_POLAND' and org_id = 684. org_id. ordered_date.NAME SITE_USE_ID CUSTOMER_ID ADDRESS_LINE_1 ADDRESS_LINE_2 ADDRESS_LINE_3 ADDRESS_LINE_4 TOWN_OR_CITY POSTAL_CODE COUNTRY Interface Tables: order_type_id: ============== Select * from oe_transaction_types_tl where NAME='EDC RMA ICO w/RECEIPT. --order_type. orig_sys_document_ref. sold_to_org_id. --TRANSACTION_TYPE_ID=1593 Order Source Id : ============= select * from oe_order_sources where NAME='Online' --ORDER_SOURCE_ID=0 Price List Id: =============== select * from QP_PRICE_LISTS_V where name='PL STD LIST A'. ship_to_org_id. invoice_to_org_id. 54 . created_by. SALESREP_ID.sold_to_org-id Standard Sales Order: insert into oe_headers_iface_all (order_type_id. order_source_id. customer_id. last_updated_by. customer_po_number. TRANSACTIONAL_CURR_CODE. creation_Date.

orig_sys_line_ref.'CG BILL ONLY TRADE ORDER' -. .orig_sys_document_ref . order_quantity_uom.. . creation_date ) Values ( 0--order_source_id. calculate_price_flag. orig_sys_document_ref. . request_date. . 1234 --customer_po_number.'EA' --order_quantity_uom.'INSERT' --operation_code. . inventory_item_id. schedule_ship_date. --Need to Check if ist always Item Level Default Value? ship_from_org_id. 1264 --org_id. .ordered_date.invoice_to_org_id.5--ordered_quantity. promise_date.last_updated_by. 4582158 -. .sysdate -.order_source_id. created_by.'USD' -. . --Need to Check if ist always Item Level Default Value? . 4582156 -. .381645--inventory_item_id. UNIT_LIST_PRICE.TRANSACTIONAL_CURR_CODE. . last_update_date. . ordered_quantity. .sysdate --last_update_Date. . .1 --created_by. insert into oe_lines_iface_all (order_source_id.order_type .customer_id .creation_Date. 100006574 --SALESREP_ID . ).null--orig_sys_line_ref.1 -. . 2920367 -.NULL --ship_from_org_id.PRICE_LIST_ID .last_update_Date.order_type_id -.0 -.9999 --orig_sys_document_ref. 55 . 1309328 -. operation_code ) values ( 3262 -. operation_code.sysdate -.ship_to_org_id. . 225964 -. .sold_to_org_id.9999 -. unit_selling_price. last_updated_by.

ordered_date. order_source_id. orig_sys_document_ref. operation_code. Return_reason_code: Populate a reason code from lookup_type CREDIT_MEMO_REASON The following are Optional: 4. (If return_context: ORDER.10 --unit_selling_price.'N' --calculate_price_flag. calculate_price_flag: Set it to “P” if you want to retain the original price. created_by. sold_to_org_id.1 --last_updated_by. line_category_code: RETURN 2. ship_to_org_id. line_type_id: Assign a line_type_id from RMA line. . insert into oe_headers_iface_all (order_type_id. . --order_type. customer_id. . creation_Date.10 --UNIT_LIST_PRICE. . TRANSACTIONAL_CURR_CODE. last_update_Date. . PRICE_LIST_ID. populate into this filed) 6.sysdate --last_update_date. populate into this filed) 7. the flag to “Y” if you want to reprice the RMA line.'INSERT' --operation_code. . Line_type_id is optional. . org_id. SALESREP_ID. return_attribute1: header_id from the referenced order. RMA Order: For the Order Line record. populate the header_level/line level sales credits details from the referenced order. customer_po_number. ) 3.1 --created_by. provided a default line_type has been defined for the specified Order Line Type. 8.NULL --schedule_ship_date. For sales credit info..SYSDATE --request_date. return_attribute2: line_id from the referenced order line.sysdate --creation_date ). (If return_context: ORDER.NULL--promise_date. invoice_to_org_id. return_context: ORDER 5. . last_updated_by. populate the following attributes only: 1. 56 . . Putting the flag to “N” will still import the freight charges from the referenced line. .

org_id. 137951 . -. operation_code. RETURN_REASON_CODE. last_update_date.customer_po_number. 57654 -.ordered_date.created_by. -.TRANSACTIONAL_CURR_CODE.last_updated_by. -. created_by. org_id ) Values 57 . 318612 -.order_type_id -.. --Need to Check if ist always Item Level Default Value? ship_from_org_id.PRICE_LIST_ID . last_updated_by. order_quantity_uom. ordered_quantity. request_date.SALESREP_ID . LINE_CATEGORY_CODE.SHIP_FROM_ORG_ID ) values ( 1593 -.last_update_Date. . creation_date. -.operation_code -.CREDIT' -.'PLN' -.invoice_to_org_id. promise_date.sysdate .ship_to_org_id. calculate_price_flag. orig_sys_document_ref.creation_Date. UNIT_LIST_PRICE. 218220 -. -. schedule_ship_date. -. orig_sys_line_ref.sysdate .customer_id . RETURN_CONTEXT. -.'7777' -. -. 684 .0 -. . LINE_TYPE_ID. unit_selling_price. 45678 .ship_from_og_id insert into oe_lines_iface_all (order_source_id. -.sysdate .'INSERT' .order_type . 100001022 -.order_source_id. 861109 .sold_to_org_id. -.orig_sys_document_ref .'EDC RMA ICO w/RECEIPT.687 ).1 . inventory_item_id.1 . .

LINE_CATEGORY_CODE.sysdate --creation_date . --Need to Check if ist always Item Level Default Value? . . .'7777' --orig_sys_document_ref. .sysdate --last_update_date.687 --ship_from_org_id. . . .1 --last_updated_by. .'INSERT' --operation_code.1 --created_by.150 --UNIT_LIST_PRICE. .NULL --schedule_ship_date.LINE_TYPE_ID .NULL --promise_date. .239777 --inventory_item_id. .6 --ordered_quantity.150 --unit_selling_price. . .SYSDATE --request_date. .1584 -.RETURN_CONTEXT .'1111' --orig_sys_line_ref. .'EA' --order_quantity_uom. 58 . . .'DEFECTIVE PRODUCT' --RETURN_REASON_CODE .'RETURN' -.684 ).( 0 --order_source_id.'N' --calculate_price_flag. .NULL -.

The entire book required columns need to be passed for importing a Closed Order. the order will still be imported.  The header interface table should have o CANCELLED_FLAG set to 'Y' o CHANGE_REASON as a valid lookup code from CANCEL_CODE lookup type. which means no defaulting. as it goes through the booking cycle where validation for all the booking required columns are done. Cancellation of Order using Order Import  If the entire order is to be cancelled. 3. BOOKED. 59 . As orders were already closed in the old system. There is a difference between closing an existing order and importing orders in "CLOSED" status the first time itself. Scheduling Order Import allows you to reserve orders as they are imported. i. By passing the action request to the OE_ACTIONS_IFACE_ALL table.e. Status of Orders Orders can be imported as ENTERED. Order Management still imports the order in the Entered state and reports a booking error. using the same rules as online order entry. If the scheduling request is unsuccessful on an imported order. Orders can be imported as ENTERED. CLOSED. then  The lines information should not be loaded into the interface table. Closed_Flag should be passed as "Y" to the OE_HEADERS_IFACE_ALL table and OPERATION_CODE should be "INSERT. there will not be any changes performed to the records.Note: If any of the required fields for a booked order are not supplied. To unschedule a line by order import the operation_code should be ‘UPDATE’ and the REQUEST_DATE and SCHEDULED_SHIP_DATE on OE_LINES_IFACE_ALL should be NULL. in the OE_HEADERS_IFACE_ALL do not pass the BOOK_FLAG and in the OE_ACTIONS_IFACE_ALL table put operation code as BOOK_ORDER. Order can be imported in Booked condition using one of the following methods: By populating the column BOOK_FLAG of the table OE_HEADERS_IFACE_ALL as ‘Y’. 4. If an order is imported with an entry status of CLOSED. BOOKED or CLOSED.BOOKED_FLAG=N or NULL) then the result after import is that the line is BOOK_ORDER eligible. Importing Closed Orders using Order Import Closed Orders are treated differently from open orders 1. To Import Closed Orders oe_headers_iface_all table should have the CLOSED_FLAG as "Y" and the operation_code as ‘INSERT’ 2. and the scheduling exceptions can be viewed in the Error Messages of the Order Import Corrections window.  If only the line is to be cancelled then  Both the lines and the header tables should be populated in the interface table. If an order is imported with an entry status of ENTERED (OE_HEADERS_IFACE_ALL.

or 'CONTACT') to denote the type of information in the record. the header_id and other Order related details are queried based on the Order Source Id and the Orig Sys Document Ref number.Orig_sys_document_ref. When the order import is used to create a new customer (new account/address/contact etc). it will be processed in OM until closure. And the operation code to be used for cancellation should be ‘UPDATE’ . So depending on whether the order or the line is to be cancelled. 'ADDRESS'. Sales Order created using the Sales Order form can be updated using Order Import and the Order Import source is Online ( Order_source_id = 0). Then since the line CANCELLED_FLAG is also 'Y' it tries to cancel the already cancelled line and errors out. When an existing order is updated. Updating Existing Orders using Order Import While updating existing Sales Orders. Based on the data available in the OE_HEADERS_IFACE_ALL the data from the table OE_CUSTOMER_INFO_IFACE_ALL is processed to add a new customer. The following table explains the linkage between the various header interface table columns and the column CUSTOMER_INFO_TYPE_CODE and the usage of the combination. If the both the order and the line CANCELLED_FLAG is set to 'Y' then in such cases the program cancels the header along with the lines because the header CANCELLED_FLAG is 'Y'. the Operation_code should be UPDATE. The table OE_CUSTOMER_INFO_IFACE_ALL needs to be populated for this. For the Order Line. Set the CANCELLED_FLAG to 'Y' only for the lines with the qty updated to zero. and Orig_sys_line_ref are used to get the specific line for updation. the CUSTOMER_INFO_TYPE_CODE should be either ('ACCOUNT'. the cancelled flag and the header information or the line information should to be loaded. This table can also be used to import a new address only or contact information of an existing Customer. The link between the header interface record and the customer interface record is made through the column CUSTOMER_INFO_REF of the table OE_CUSTOMER_INFO_IFACE_ALL and any one of the columns mentioned below. the Order_source_id . 60 . the address and contacts using Order Import. Add Customer Order Management provides the capability to add a new customer. An Order cannot be updated to status closed as it is assumed that after importing the order. The link depends on the CUSTOMER_INFO_TYPE_CODE.

and the manual adjustment is applied on the line when the order is processed for import. The following columns can be passed as ‘Y’ if price adjustment is not to be applied on the Order/ Line again by the pricing engine overriding all the changes done based on value populated in the OE_PRICE_ADJS_IFACE_ALL and OE_PRICE_ADJS_IFACE_ALL tables. In the OE_LINES_IFACE_ALL --. (provided a default line_type has been defined for the specified Order Type. 61 . you cannot specify a value for the line category_code column.Importing Sales Credit Both Quota and Non Quota Sales Credit can be imported. Use an order category of RETURN or MIXED for the Order Header record. Populate all required attributes for creating a return order line. Creation of a non-referenced RMA If you want to import a return order for a non-referenced return.CALCULATE_PRICE_FLAG should be ‘Y’. you must populate all required attributes for creating a return order. Order Management utilizes workflow activities to import returns. This information is passed to the process order API. Importing Returns Returns can be imported like a regular sales order.UPDATED_FLAG should be ‘Y’.APPLIED_FLAG should be ‘Y’-. The table OE_PRICE_ADJS_IFACE_ALL is populated with the adjustment to be imported along with the line. Line_type_id is optional. The table OE_CREDITS_IFACE_ALL has to be populated for this. You will need to populate the column reason_code for all return lines. Importing Price Adjustments Manual Price Adjustments can be imported using the tables OE_PRICE_ADJS_IFACE_ALL and OE_PRICE_ATTRS_IFACE_ALL. When this flag is passed as ‘Y’ the pricing engine calculates the selling price after applying the eligible automatic modifiers. In the OE_PRICE_ADJS_IFACE_ALL --. Valid values are those values defined for the Order Management QuickCode CREDIT_MEMO_REASON.). For Order Line Record. You need to populate the column ordered_quantity with a negative value.

populate the header_level/line level sales credits details from the referenced order. Holds can be applied or released using OE_ACTIONS_IFACE_ALL. you should copy the Header Record for the return from the referenced Order header record. You can send EDI acknowledgments for original orders and change requests (Whether received through EDI or other means). populate the following attributes only: line_category_code: RETURN return_context: ORDER return_attribute1: header_id from the referenced order. ) Return_reason_code: Populate a reason code from lookup_type CREDIT_MEMO_REASON For sales credit info. the flag to “Y” if you want to reprice the RMA line. provided a default line_type has been defined for the specified Order Line Type. Putting the flag to “N” will still import the freight charges from the referenced line. the operation_code for the header and the lines Interface table should have operation code as UPDATE and in the actions table the Operation_Code should be RELEASE_HOLD. EDI 855 and EDI 865 Holds and Releases Order Management automatically applies all holds to imported orders and order lines that meet hold criteria. just as you would for orders entered through the Sales Orders window. For applying HOLD using the actions table the operation_code for the header and the lines Interface table should have operation code as UPDATE and in OE_ACTIONS_IFACE_ALL. calculate_price_flag: Set it to “P” if you want to retain the original price. Creation of a Referenced RMA (If users want to return an existing outbound line) If you create a referenced RMA. 62 . you should copy the Header Record for the return from the referenced Order header record. Order Import applies holds on imported orders for review. modifying the Order Type to category RETURN or MIXED (order_type_id from oe_transaction_types_all). EDIs: EDI Name EDI 850 EDI 860 Purpose Inbound Order Import inbound Order Change (860/ ORDCHG) transactions for automated changing of order shipment quantities. For the Order Line record. dates and location information. and the outbound Purchase Order Change Acknowledgment (865/ORDRSP) transaction are supported. Both the outbound Purchase Order Acknowledgment (855/ORDRSP) transaction. The HOLD_ID and the RELEASE_REASON_CODE should also be populated. Line_type_id is optional. modifying the Order Type to category RETURN or MIXED (order_type_id from oe_transaction_types_all).Creation of a Referenced RMA (If users want to return an existing outbound line) If you create a referenced RMA. line_type_id: Assign a line_type_id from RMA line. For releasing the hold using OE_ACTIONS_IFACE_ALL. the Operation_Code should be APPLY_HOLD and the Hold_ID needs to be populated. return_attribute2: line_id from the referenced order line.

a new line can be added to an existing order or an existing line can be split into two or more lines. you will not be able to book orders with invalid configurations. however. it reserves it. -.DELINK_CONFIG deletes the configuration item.MATCH_AND_RESERVE checks if an existing configuration item matches the configuration created by the user and if the configuration item is available.Configuration (ATO/PTO) Order Management provides you with the ability to import ATO and PTO configurations. If you choose the Errors 63 . -. If the SPLIT_FROM_LINE_REF. the error can also be viewed from the Application. For this. The validation-only mode may also facilitate testing of transactions through Order Import even in a production environment to take advantage of all the setup in the production environment. user has to send the optional components along with model. Viewing Orders that have failed In Order Management Rel 11i. In case of (Configurations) ATO models (also in case of PTO models). Viewing Errors In Order Management. The order that have failed in Order Import can be selected from the Corrections Form (OEXOIMPT) and the error can be seen using the Error Button. The error messages stored are context sensitive. it will not know what options user wants to select. This is because although OM knows the BOM of the ATO model. The following operation Code can be used in the actions table for the configurations. Table: Operation Code for Configuration Adding Lines to existing Orders In Order Management. Make necessary corrections to the transactions in the Order Import window. you can import valid and invalid configurations. the Operation Code at the header should be UPDATE and the operation code at the line level should be INSERT or CREATE. Users can run production transactions in validation-only mode for a preview of exceptions. the Entity Id used is the Line_ID of the Top Model Line of the ATO configuration. in 11i the Order Import process can be run in the validation-only mode. is populated then the LINE_ID in the line table is taken as the SPLIT_FROM_LINE_ID and that line is SPLIT. These orders are highlighted in red in the window. For EDI orders. Validation of data Before Importing Unlike in Order Import in Rel 11. and then choose the Validate button to perform a validation check. For both the operation codes. This mode allows the transaction to be validated against all the Order Management rules but does not allow it to pass valid transactions to the base Order Management tables. User should not send the standard mandatory components. In case it is not populated then a new line is added to the existing order. the orders that have failed in Order Import can be viewed in the Corrections summary window.

all the errors are displayed for that line. Once the validation is successful. run and correct the data if required. The value in the fields of oe_headers_iface_all and oe_lines_iface_all tables can be inserted. you can also fix these errors in the window and try importing the order again. This conversion of data. a debug log file is generated (information depends on the OM Debug Level). The requirement is to convert the existing data in the legacy system or that coming from the customer (Web Enabled) to data that can be understood by the Oracle Application. the failed orders can be modified from the Corrections form. more records can be populated on to the interface tables and the Order Import batch processes can be run to import (either by running the Order import concurrent request or by importing directly from the Corrections form) to process the entered data and convert it to legitimate orders. a change in the functionality from the earlier versions of order imports. the ERROR flag is unchecked and the REQUEST_ID field cleared. For testing the data a single sample record can be populated onto the interface tables and the record can be validated by running the order import request with Parameter Validated as YES. it. If you encounter errors while importing orders. There is no Process Exception Report in Order Management. If you choose the Errors button from the Lines region. 64 . Hence. Once the error is corrected. One or multiple orders or lines can be updated at the same time through the Summary window. the order can be resubmitted for Import from the Summary window. updated. and can be seen in the Corrections form (these lines will be highlighted in red). loading can be done by first converting it to flat files and then using an Oracle utility called SQL*LOADER. These failed records can be corrected in this window and re-imported from the Corrections window. Order Import Process This section explains the Order Import process. which enables the Application to understand and further process. Data in the interface tables is picked up by the concurrent managers.button from the Order Header region. This reads each position in the two dimensional flat file and converts it to a field value for the interface tables. The error can also be seen in the Order Import Log file when importing using the Order Import concurrent request. and deleted from the Summary form. Correcting Errors from the Form In Order Management. is done by the Open Interface APIs. Records that fail validation have the Error Flag set to Y and remain in the Interface tables. all the errors for that order are displayed. You can navigate from the Errors window to the Order Headers or Lines region where the error has occurred. If data is from a non-Oracle based system. But multi selection of lines is not allowed. the tables involved and the means available to validate. which validates it based on the arguments specified in the interface tables and converts it to orders by updating the concerned base tables. Methods for loading data onto the interface tables A stored procedure can be written to extract data from an existing system and put it directly into these interface tables. The difference between importing from the Corrections form and using the request is that in case of the concurrent request. You can also mark an order or a line to be rejected by setting the REJECTED flag.

1. 15. It also allows the transfer of requisitions for internally sourced products from Purchasing. the first thing that is done is to insert the request_id into the interface tables.Orders can be imported in any valid entry status. Process Header Pricing Attributes Process Header Adjustment Attributes Process Header Adjustment Associations Process Header Sales Credits Check Entity context to make sure all lines belong to one header Process Lines Process Line Adjustments Process Line Pricing Attributes Process Line Adjustment Attributes Process Line Adjustment Associations Process Line Sales Credits Process Line Lot Serial Numbers Perform Cross Entity Logic for Sales Order business object VALIDATION When the order is found in the interface tables. For example. What is the MTL_TRANSACTIONS_INTERFACE table used for? A1. If CLOSED_FLAG = ‘N’. 7. It is done in three steps: Check for Required Attributes. Once the interface managers pick up the records in the interface tables. 8. 4. If the OPERATION_CODE is ‘INSERT’ then it is changed to ‘CREATE’ for all the interface tables. Inventory Item is a required field on the order line entity. This is the Interface between non-Inventory applications and the Inventory Transactions module. 10. updated or deleted. including Booked. This will first give the validation of the case where CLOSED_FLAG = ‘N’. 16. Cross-Attribute Validation. 6. The value of the CLOSED_FLAG is checked. 3. then raise an error and quit. for a booked line. raise an error and quit. respective processes are triggered. the Order Import Procedure for open Orders OE_ORDER_IMPORT_PVT. The entities are processed in the following sequence: Process Header Record Process Header Adjustments. Check for Conditionally Required Attributes. 11. the Order import procedure for closed orders (OE_CNCL_ORDER_IMPORT_PVT. 14. 5. 2. 9.Import_Order is called. Validate that all the required attributes have been specified on the entity and even if one required attribute is missing.Import_Order) is called. ship to location is required. For example verify that the ship to is valid for the customer. it validates them to see if orders need to be created. if at least one attribute is not valid. For example. It also allows completed orders to be imported. 65 . 12. raise an error and quit. At the end of the validation. 13. Modules such as WIP (Work In Progress) and OE (Order Entry) first pass their records to the MTL_TRANSACTIONS_INTERFACE (MTI) for validation. The Order Import Pre Processor is called. In other words any other module other than Inventory that wants to update Inventory has to come through this table. Validate that all attributes that are required based on the status of the entity have been specified and if at least one is not specified. Depending on the arguments specified. The validation starts. Validate all those attributes that are dependent on the value of another attribute. If CLOSED_FLAG = ‘Y’.

The Cost Manager is a concurrent job that runs in the background. Example :. If it is set to 'E' then it has erred for some reason.In the case of an Sales Order. It is from here that the inventory quantities finally get updated. However. 66 . (CMCTCM) COSTED_FLAG = 'N'(Not Processed) This means record is pending. The transactions which are done through this form are on-line processing. this needs to be updated to show that it is no longer available in Inventory stock. This is a transactional historical table. MTL_TRANSACTIONS_LOTS_INTERFACE and MTL_SERIAL_NUMBERS_INTERFACE into their respective TEMP (temporary) tables from where the transactions processor processes them. validation. it is the holding point for transactions to be cost. the item is being shipped to a client so the lot and serial number if being used. LOCK_FLAG = 2 PROCESS_FLAG = 1 transaction_mode = 3 What is the MTL_MATERIAL_TRANSACTIONS_TEMP table used for? Once the transactions have been passed to this table after initial validation by the Transactions Manager (INCTCM) from the MTL_TRANSACTIONS_INTERFACE a job id is attached and a Transactions Worker (INCTCW) is submitted by the INCTCM process in order to the get the records processed and moved to the MTL_MATERIAL_TRANSACTONS table. Both the Lots and Serial number tables above are used when items being updated are under 'Lot' or 'Serial' number control. and submits Transaction workers (sub-processes INCTCW) which then processes these records through inventory. validates them and moves the successful transactions onto MTL_MATERIAL_TRANSACTIONS_TEMP. If it is NULL then the transaction has already been processed. and transfer of records from MTL_TRANSCTIONS_INTERFACE. Inventory Module Forms like Miscellaneous transactions writes directly into this table. This table is also used by Inventory Module and Purchasing module which writes directly onto this table for any transactions entered within itself and each transaction in turn through a process of strict validation.There is an Interface Manager called the Transactions Manager (INCTCM) which reads records from this table. What type of issues will you see with the MTL_MATERIAL_TRANSACTIONS table? Transaction is valued (unit cost*quantity = $ amount) Once data gets here the transaction is almost complete except for the fact that it needs to have the costing details finally updated and written to the Transaction Accounts table for transfer to General Ledger. serial/lot numbers get marked as being used. It is important to note that in general the processors will not move the transactions from this table if the following fields are not set as follows. This process consists of data derivation.

Move. What is the setup required for Drop ship PO? ITEM ATTRIBUTES: Navigate: Inventory -> Items .What are the major tables involved in Material Movement for Inventory and WIP Material. When attempting to load legacy data into the MTL_TRANSACTIONS_INTERFACE table.> Organization items Purchased (PO) Enabled 67 . Why is the distribution account ID required in MTL_TRANSACTIONS_INTERFACE? All issues and receipts of asset items to an asset subinventory and sales order shipments require the distribution account id that originates from GL code combinations. -.Resource Cost Worker processes records in this table. How is a Drop Ship PO created? Drop shipments are created as sales orders in Order Management. What is a Drop ship PO? Oracle Order Management and Oracle Purchasing integrate to provide drop shipments. The column is optional and shows up on reports and transaction displays. This account id is required to create a complete audit trail of the transaction. In the Oracle Manufacturing Implementation Manual.WIP Move Transaction Worker processes records in this table (WICTCM) WIP_MOVE_TRANSACTIONS -. This section describes the transaction type id's and there is not a PO number.Must be viewed and resubmitted via SQL with the scripts below WIP_COST_TXN_INTERFACE -. Refer to the column of transaction_reference and this column will allow the PO number. Then Purchasing’s Requisition Import process creates the requisitions. WIP_MOVE_TXN_INTERFACE -.INCTCM is the Transaction Manager for this Table MTL_MATERIAL_TRANSACTIONS -. Since a column for the PO number does not directly exist. or because it’s more cost effective for the supplier to ship the item to the customer directly.CMCTCM is the Cost Manager for the records to be coasted in this table.CMCCCM is the Cost Collection Manager for the records to be imported to Project Mfg. The Purchase Release concurrent program or workflow in Order Management creates rows in the Requisition Import tables in Purchasing.INCTCM is the Transaction Manager for this Table. MTL_MATERIAL_TRANSACTIONS_TEMP -. a transaction_reference field can be used to input this information. Drop shipments are marked with the Source Type of External in Order Management and Supplier in Purchasing. Drop shipment was introduced in R11. and Resource Transactions? MTL_TRANSACTIONS_INTERFACE -. Drop shipments are orders for items that your supplier ships directly to the customer either because you don’t stock or currently don’t have the items in inventory. into what column is the PO number input? There is not a direct column for PO number. locate the section on Open Transactions Interfaces.

Purchasable (PO) Enabled Transactable (INV) Enabled Stockable (INV) Optional Reservable (INV) Optional Inventory Item (INV) Optional Customer Ordered (OM) Enabled Customer Orders Enabled (OM) Enabled Internal Ordered (OM) Disabled Internal Orders Enabled (OM) Disabled Shippable (OM) Optional OE Transactable (OM) Enabled All Drop Ship items must be defined in the organization entered in the profile option OE: Item Validation Organization and in the Receiving Organization. If items on a Drop Ship order are cancelled. Can Configurable Items be drop shipped? Currently only Standard Items can be drop shipped. If the sub-inventory is not Reservable the sales order issue transaction will not be created in MTL_TRANSACTIONS_INTERFACE. If you use Oracle master Scheduling/MRP and Oracle Supply Chain Planning. will the order changes automatically be updated on the PO? Order changes will not be automatically updated on the PO. Functionality for Configurable Items will be 68 . Does Order Management 11i have functionality to do serial number management with Drop Shipments? You are able to receive serial numbered Drop Ship stock. you will have to manually update the POs in the Purchasing application. go to an inventory responsibility and navigate to Setup -> Organizations -> Subinventories. to avoid miscounting supply you may not want to include logical organizations in your planning. To create the subinventory. Subinventory Attributes for Asset Subinventory Reservable/Allow Reservations Asset Subinventory Subinventory Attributes for Expense Subinventory Reservable Asset-must NOT be enabled. Expense subinventories must have the Reservable box checked and the Asset box unchecked. ensure that doing so does not cause planning and forecasting complications. If you choose to include logical organizations. subinventories should be defined. Pulling up the Discrepancy report will allow you to view the differences between the Sales Order and PO. Order Management will receive the serial number noted on the PO. There is a discrepancy report available that will report differences between the PO and the Sales Order. How can we avoid the miscounting of supply as logical organization is involved? You must receive drop-ship items in a logical organization. After drop ship inventory organization is created. However. does the system automatically generate a PO Change to the PO originally sent to the supplier? No. Drop Ship functionality in this regard remains the same as in R11. Asset subinventories must have the reservable and Asset boxes checked. All drop ship sub-inventory must have Reservable box checked. If you make changes to a sales order after the Purchase Order (PO) has been generated.

A user who wants to cancel a drop ship sales order line must ensure no receipts have been created against the line and that the requisition and/or purchase order associated with the line is cancelled. and you do not wish to fulfill the remaining quantity.1 contains a diagnostic script that can be used for troubleshooting problems with sales orders.added in future releases. Note 133464. the trace for the errors. Debugging receipt transaction or the sales order issue transaction. -Save the receipt for the deliver transaction (destination type will say Inventory for the deliver transaction). Set the following profile options: RCV: Processing Mode to Immediate or Batch RCV: Debug Mode to Yes OM: Debug Level to 5 INV: Debug Trace to Yes INV: Debug level to 10 TP: INV Transaction processing mode to Background -Then go to Sys Admin: Concurrent: Program: Define. the Inventory Transaction Worker log file. The first line contains the quantity shipped and the second line contains the non-shipped quantity in backorder. Status of PO will always be approved. But only the portion that has not been received can be cancelled. Can we cancel drop shipment after it is received? Drop shipments cannot be cancelled once Oracle Purchasing obtains the receipt. cancel the line. as well as.OM is updated to receiving interface eligible. Drop ship lines do not use the pick release. query up the Receiving Transaction Processor and check the Enable Trace box. How are over/under shipments handled in drop shipment? If part of a drop-ship line ships. How do I drop ship across operating units? Release 11i does not currently support this functionality. The PO line quantity should be changed to reflect the new quantity. You can cancel the second line the backorder on the sales order. What debugging tools are available for Drop shipments? 1. If the supplier ships more than the ordered quantity. This PO is linked to the drop ship order so that when the receipt is done (partial or complete) . you can bill your customer for the additional quantity or request that they return the item. Will Blanket PO's work with Drop Shipment? Blanket PO's will not work with Drop shipment because the PO must be created when OM notifies PO that a drop ship order has been created. If you cancel a drop shipment line for which you have not shipped the entire quantity. -View the Receiving Transaction Processor log file. Cancellation of a Partial Drop Ship receipt is allowable. 69 . Over shipments must also be handled manually. Use the Drop Ship Order Discrepancy Report to view differences between your drop-ship sales orders and their associated purchase requisitions and orders. What is the Import source and status of PO generated from Drop Shipment? Import source is Order Entry. the order processing splits the line. 2. ship confirm or inv interface order cycles.

FROM_LOCATOR_ID.On Hand Qty select INVENTORY_ITEM_ID .8857. 7170 -.Release Order -.No Move Order.TRANSACTION_QUANTITY .7169.header_id : 5080 -.Move Order : Line_status = 7 QUANTITY_DETAILED is not null -. '0121884') -. TO_SUBINVENTORY_CODE.Sales Order Lines select * from oe_order_lines_all where header_id = 5080 -.Batch_Id : 3355 -. FROM_SUBINVENTORY_CODE.Order to Invoice Tables: select INVENTORY_ITEM_ID. HEADER_ID . REQUEST_NUMBER.Transact Order : Line_status = 5 QUANTITY_DELIVERED is not null Select LINE_ID.Sales Order Header select * from oe_order_headers_all where order_number = '1001126' -. segment1 from mtl_system_items_b where segment1 in ('0071884'. GROUPING_RULE_ID from mtl_txn_request_headers where ORGANIZATION_ID = 221 and REQUEST_NUMBER = 3355 -. TO_LOCATOR_ID 70 .LOCATOR_ID .SUBINVENTORY_CODE . HEADER_STATUS.CREATE_TRANSACTION_ID . LINE_NUMBER.LOT_NUMBER from mtl_onhand_quantities where ORGANIZATION_ID = 221 and INVENTORY_ITEM_ID in (8857. 8707 -. 8707) -.Header Info select HEADER_ID. No Transact Order Line_status = 7 QUANTITY_DETAILED is NULL QUANTITY_DELIVERED is null -.Release Sales Order -. TO_SUBINVENTORY_CODE. INVENTORY_ITEM_ID. FROM_SUBINVENTORY_CODE.

8707) and ORGANIZATION_ID = 221 and TXN_SOURCE_LINE_ID in (7169.QUANTITY_DETAILED .PRIMARY_QUANTITY ..LOT_NUMBER .TRANSACTION_TYPE_NAME . 7170) -.QUANTITY .line_id -.TRANSACTION_SOURCE_TYPE_ID .SOURCE_LINE_ID .SUBINVENTORY_CODE .All Material Transaction Types gets stored in mtl_transaction_types select TRANSACTION_TYPE_ID .oe_order_lines_all.Once you Transact Order only .LINE_STATUS .TRANSFER_SUBINVENTORY .BACKORDER_DELIVERY_DETAIL_ID from mtl_txn_request_lines where INVENTORY_ITEM_ID in (8857.Can view same Information in -Inventory -> Transaction -> Material Transaction/Transaction Summary select TRANSACTION_ID .PICK_SLIP_NUMBER .TRANSACTION_SOURCE_TYPE_ID .INVENTORY_ITEM_ID .TXN_SOURCE_ID . INVENTORY_ITEM_ID.line_id -.LOCATOR_ID .TRANSACTION_TYPE_ID . 71 .Reservation select RESERVATION_ID.PRIMARY_QUANTITY . DEMAND_SOURCE_LINE_ID. RESERVATION_QUANTITY.TRX_SOURCE_LINE_ID .QUANTITY_DELIVERED .TRANSACTION_SOURCE_TYPE_ID from mtl_transaction_types where TRANSACTION_TYPE_ID = 52 -.oe_order_lines_all.PICK_SLIP_DATE .MOVEMENT_ID from mtl_material_transactions where INVENTORY_ITEM_ID in (8857. DEMAND_SOURCE_HEADER_ID.TRANSACTION_ACTION_ID . data gets populated into mtl_material_transactions -.TRANSACTION_QUANTITY .TRANSFER_LOCATOR_ID .TRANSACTION_TYPE_ID . 8707) and ORGANIZATION_ID = 221 and TRX_SOURCE_LINE_ID in (7169.TXN_SOURCE_LINE_ID .DESCRIPTION . 7170) -.

DETAILED_QUANTITY from mtl_reservations where ORGANIZATION_ID = 221 and DEMAND_SOURCE_LINE_ID in (7169.Released to Warehouse Y .DELIVERY_LEG_ID=2630956. PICK_UP_STOP_ID=5217623 select * from wsh_trip_stops where stop_id =5217623 -.line_id order by RESERVATION_ID desc -.Backorder C .Ready to Release S . LOT_NUMBER. 7170) -. REQUESTED_QUANTITY.Staged/Pick Confirmed B .Shipping -. LOCATOR_ID. RELEASED_STATUS from wsh_delivery_details where SOURCE_HEADER_NUMBER = '1001126' --oe_order_headers_all.trip_id = 2618561 select * from wsh_trips where trip_id = 2618561 72 . DELIVERY_ID. RELEASED_STATUS Meaning: ========================================== R .oe_order_lines_all.order_number wsh_delivery_details. PARENT_DELIVERY_ID.PRIMARY_RESERVATION_QUANTITY.Auto Create Delivery Information select DELIVERY_DETAIL_ID.Auto Create Delivery Information select DELIVERY_ASSIGNMENT_ID. CUSTOMER_ID. MOVE_ORDER_LINE_ID.wsh_delivery_details. DELIVERY_DETAIL_ID from wsh_delivery_assignments where DELIVERY_DETAIL_ID in (15136. LOT_NUMBER.Pallet Information SELECT * FROM WSH_NEW_DELIVERIES WHERE DELIVERY_ID = 9413115 -INITIAL_PICKUP_LOCATION_ID=85086 --ULTIMATE_DROPOFF_LOCATION_ID=455356 select * from wsh_delivery_legs where DELIVERY_ID =9413115-. INVENTORY_ITEM_ID. SUBINVENTORY_CODE. SOURCE_LINE_ID. LOT_NUMBER_ID. ITEM_DESCRIPTION. SOURCE_HEADER_ID.DELIVERY_DETAIL_ID -.Cancelled -. SUBINVENTORY. SUBINVENTORY_ID.Interfaced D .15137) -.

-.Trips select * from wsh_trips where TRIP_ID = 2788 -. -Select * from ra_customer_trx_lines_all 73 .AR Interface Lines select * from ra_interface_lines_all where sales_order in ('1001081'.Invoice Header Select * from ra_customer_trx_all.'1001096') -.

Line Statuses in OM and SE 74 .

This status is no longer valid starting with Release 11i. the delivery line status flow is: Ready to Release (SE): Order line is booked and passed to Shipping Execution. When the ship line logic starts. Booked (OM): Order is booked. Navigating to Shipping Execution. The move order lines have been allocated and pick confirmed. Once a delivery has been created. Released was replaced by the following three additional statuses: Backordered (SE): The delivery line is pick released but no allocations were created or partial allocations occurred. 75 . Open (OM): This status of a delivery on the Additional Line Information form indicates that none of the delivery lines associated with that delivery have been ship confirmed. if a delivery line has a quantity of 100. It is now a delivery line that is eligible for Pick Release. The quantity on the original delivery line changes to 25 to reflect the allocated portion with a status of Staged/Pick Confirmed. It occurs after pick confirm to indicate sub inventory transfer from source location to staging location is complete. Released to Warehouse (SE): Pick Release has started but not completed. The action has translated the delivery lines into move order lines in Inventory.Entered (OM): Order is saved but not booked. Staged/Pick Confirmed (SE): The delivery line is successfully pick released. Released (SE): Pick Release has run successfully. Not Ready to Release (SE): A delivery line may be in this status when it is interfaced manually into Shipping. the delivery and its associated delivery lines are eligible for Ship Confirm. the original delivery line splits to create a new line (quantity of 75) for the unallocated portion with a status of Backordered. is not scheduled and has no reservations.4. the order line status changes to Awaiting Shipping. Awaiting Shipping (OM): Order is booked but lines are not yet picked. Submitted for Release status changes name to Released to warehouse. Submitted for Release (SE): In Release 11i. Scheduled (OM): A user can customize the Workflow to show the Scheduled status which indicates that the order line has been successfully scheduled. and at pick release only 25 are available for allocation. When lines are imported automatically from Order Management this status is not used. As an example.4. Either no allocations were created or allocations have not been Pick Confirmed. Both Backordered and Staged/Pick Confirmed status provide the ability to perform opportunistic cross-docking for warehouse organizations with Oracle Warehouse Management System (WMS) installed. Lines staged until they are ship confirmed. Shipped (SE): This line status indicates that the delivery associated with the delivery line(s) is ship confirmed.

Order Management writes information to Receivables tables. It does not necessarily indicate that the line is interfaced to Accounts Receivable (AR) since you must “close line” activity in a no-bill flow. The order line then splits to reflect the changes that occurred during the Shipping process. The delivery line splits during Ship Confirm and the information passes to Order Management through the Process Order API. Confirmed (SE): This delivery status indicates that the delivery line is either shipped or backordered and the trip stops are open. Interfaced (SE): If delivery was sourced from Oracle OM: The delivery line is shipped and the OM Interface and Inventory Interface concurrent processes have completed. This is a synchronization step within the Workflow process. Awaiting Fulfillment (OM): Not all shippable lines in a fulfillment set or a configuration are fulfilled. Closed (OM): Closed indicates that the line is closed. Interfaced to Receivables (OM): Invoice Interface has been launched. This status appears in the Additional Line Information at the Pick Status field. The Delivery status is set to in transit. There are 20 on hand in inventory. Note: Fulfillment Sets are defined as a group of order lines that get fulfilled together. The order line with quantity 20 has the status of Picked or Shipped depending on whether or not the delivery line is Ship Confirmed.4. 76 . a customer orders quantity 50. Items that are not shippable can be in fulfillment sets with shippable items. Navigate back to Order Management and query the order which results in OM pulling updated Pick Release information from Shipping Execution (in R11i. No further processing will occur for this line. A line can belong to either a ship set or an arrival set. As an example. Shipping Execution pushes status information to Order Management once Ship Confirm is completed: Shipped (OM): The delivery associated with the line is Ship Confirmed. 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. Partially Interfaced to Receivables (OM): This status is used in a PTO flow and indicates that the particular PTO item is required for revenue.In Transit (SE): This delivery status indicates that the delivery associated with the line is ship confirmed and the pick up stop is closed. Fulfilled (OM): All lines in a fulfillment set are fulfilled. the Delivery set in transit and the Trip closed. these statuses will occur after Staged/Pick Confirmed and Backordered respectively): Picked (OM): Pick release has completed normally (both allocation and pick confirm). and then will not be fulfilled (and therefore invoiced) until the shippable items are fulfilled. Picked Partial (OM): This status occurs when a delivery line is not allocated the full quantity during Pick Release and Ship Confirm has not occurred. but can belong to multiple fulfillment sets. If delivery was sourced from an Oracle Application other than OM: The delivery line is shipped and the Inventory Interface concurrent process has completed. Canceled (OM): Indicates that the line has been completely canceled. The delivery line splits into two delivery lines and therefore represents two order lines in Order Management. The second order line with a quantity of 30 has a status of Awaiting Shipping.

Order Statuses: Action Entered Booked Order Management Header Line Status Status Entered Entered Booked Awaiting Shipping Booked Awaiting Shipping Booked Booked Picked Shipped Shipping Execution Action Status Ready to Release Released to Warehouse Staged/Pick Confirmed Shipped/InTransit/Confirmed Interfaced

Allocate/Move Order Transact/Pick Confirm Ship Confirm Run ‘Interface Trip Stop’

AutoInvoice Import Program

Fulfilled Interface to Receivables Closed

Bill Only Line Status Flow A customer calls up to place an order for Service that is a non-shippable item. The line status flow of this order will be: • Entered • Booked • Invoiced • Closed Returns Line Status Flow • Entered • Booked • Awaiting Return Disposition: Item requires inspection before Purchasing can create a receipt • Awaiting Return: Purchasing creates a receipt of the item • Returned: Item has been received and accepted Drop Ship Line Status Flow • Entered • Booked • Purchase Release: Item requires inspection before Purchasing can create a receipt • Awaiting Receipt: Purchasing creates a receipt of the item • Interfaced to Receivables • Closed Order and Delivery Line Statuses

77

These tables show the status of order lines and delivery lines after you perform certain actions. They show information for the Order Organizer, Sales Orders window, Shipping Transactions form for deliveries and delivery lines, and Shipping Transactions form for stops and trips. How to read the lines in the table: Immediately after you autocreate a delivery, the status of all the entities will be as listed in the Create Trip column of the table. o o o o The Order Organizer Summary form will show the status of Booked The Order Organizer Lines form will show the status of Awaiting Shipping The Order Information Main tab of the sales order pad will show the status of Booked The Line Items tab of the sales order pad will show the status of Awaiting Shipping The delivery Status on the Shipping Transactions form, Deliveries tab, will show the status of Open The Line Status on the Shipping Transactions form, Lines/LPNs tab, will show the status of Ready to Release The trip Status on the Shipping Transactions form, Path by Trip tab, will show the status of Open The stop Status on the Shipping Transactions form, Path by Stop tab, will show the status of Open The Stop Activity Status at Origin and Destination on the Shipping Transactions form will show the status of N/A The Trip Activity of the Shipping Transactions form will show the status of N/A

o o o o o
o

78

79

80 .

81 .

Definitions 82 .

Set of books A financial reporting entity that partitions General Ledger information and uses a particular chart of accounts. due to line level overrides. The term buyer and customer are used synonymously in discussion about EDI transactions. Electronic Data Interchange (EDI) Exchanging business documents electronically between trading partners. The salesperson parameter in both reports is based upon a query of the default salesperson stored on the header for each order.Buyer/customer and supplier/vendor The term supplier and Vendor are used synonymously in discussions about EDI transactions. You define it by setting the OM: Item Validation Organization parameter. and planning. purchase. costing. and accounting calendar. including components. and option classes you can use to group options in model and option class bills. subassemblies. Oracle Manufacturing also uses items to represent planning items that you can forecast. You determine the functional currency for the set of books you use in your organization. Although the header level salesperson may not have actually received credit for any of the lines in the order. and/or that manufactures or distributes products. Item Anything you make. such as plastics. Inventory organization An organization that tracks inventory transactions and balances. or supplies. You must define all items and bills in your Item Validation Organization. Salesperson A person responsible for the sale of products or services. or sell. materials. standard lines that you can include on invoices. EDI subscribes to standard formats for conducting these electronic transactions as stated by various standards. The functional currency is generally the currency used to perform most of your company’s business transactions. This concept is the same whether or not the Multi-organization support feature is implemented. Category Code used to group items with similar characteristics. but you also need to maintain your items and bills in separate organizations if you want to ship them from other warehouses. Salespeople are associated with orders. The business entities are the trading partners for the PO Change transaction. Also called base currency. or glass items. invoices. 83 . Item Validation Organization The organization that contains your master list of items. metals. our parameter is based upon the header information. Typical category sets include purchasing. returns. and customers. commitments. You can also assign sales credits to your salespeople. Category set A feature in Inventory where users may define their own group of categories. functional currency. finished products. Functional Currency Currency you use to record transactions and maintain your accounting information.

In Oracle Order Management the term customer item’ is exactly that. Customer item vs. Shippable item An item with the Shippable inventory item attribute set to Yes. Customer item/order item In Oracle Order Management the term item refers to the supplier’s item. You control inventory for inventory items by quantity and value. You recognize the cost of an inventory item as an expense when you consume it or sell it. indicating that this item will appear on pick slips and pack slips. The use of this concept allows the user to perform functions such as: Up-selling Cross-selling Substitution Supercession Up-sell is the capability to suggest a better item to a customer who is placing an order. Intangible item A non-physical item sold to your customers such as consulting services or a warranty. you may also be able to stock it. Supercession refers to one product that has replaced (superceded) another product.Inventory item Items you stock in inventory. the term customer item refers to the item as in the customer’s application. Invoice item Oracle Order Management prints the name or/and description of the item on the invoice. Intangible items are non-shippable and do not appear on pick slips and pack slips. You generally value the inventory for an item by multiplying the item standard cost by the quantity on hand. Service item An inventory item used to define a service program or warranty. If an item is also an inventory item. Typically. thus defining a particular configuration for the model. Purchased item An item that you buy and receive. A synonym for serviceable item is a serviceable product. supplier item In Oracle Order Management. Service items can be recorded against serviceable products. Related Item The term Related Items covers a number of different relationships types which can be defined between items. the term item refers to the supplier’s item. Cross-sell is the capability to suggest additional items to a customer who is placing an order. Configuration A window that allows you to choose options available for a particular model. the inventory item remains an asset until you consume it. depending on your selection for the Item Display parameter. Bills of Material creates a configuration item for assemble-to-order models. In Oracle Order Management. Substitution is the capability to suggest equivalent items. 84 . Configuration item The item that corresponds to a base model and a specific list of options.

or adjustment to an inventory organization. Area. Subinventory Subdivision of an organization. Dunning letters A letter you send to your customers to inform them of past due debit items. Unit of measure class A group of units of measure and their corresponding base unit of measure. ubinventory. Locator Physical area within a sub inventory where you store material. bill of material. and Pack. stocking. Time. or routing. but allows it to be consumed in manageable pieces. Material transaction Transfer between. This maintains the integrity of the overall lot. such as a row. Current on-hand quantity Total quantity of the item on-hand before a transaction is processed. Volume. 85 . Drop shipment A method of fulfilling sales orders by selling products without handling. bin. The standard unit classes are Length. Weight. Issue of component items from inventory to work in process. On-hand quantity The physical quantity of an item existing in inventory. or locator. receipt to. aisle. or delivering them. or shelf. Revision control An inventory control option that tracks inventory by item revision and forces you to specify a revision for each material transaction. Unit of measure The unit that the quantity of an item is expressed. You can choose to include unapplied and on-account payments. The selling company buys a product from a supplier and has the supplier ship the product directly to customers. Inventory allocation The act of assigning on hand inventory to specific orders. Unit of measure conversions Numerical factors that enable you to perform transactions in units other than the primary unit of the item being transacted. Sublot A subdivision of a lot which may be used when an entire lot is more than would be used or produced at any one time. such as a storeroom or receiving dock. representing either a physical area or a logical grouping of items. Revision A particular version of an item. Receipt of completed assemblies into inventory from a job or repetitive schedule. Oracle Receivables lets you specify the text and format of each letter. but grouping of the material into a single lot is still desired. issue from.Dropship item An item that is going to be sourced externally from the supplier directly to our customer.

Order Management Transaction types:  Determine the workflow processes executed for both the order and line. 86 . Accordingly. Price list A list containing the base selling price per unit for a group of items. Transaction interface An open interface table through which you can import transactions. Ship To.  Can specific processing controls for an order or line based upon the transaction type entered. Oracle Order Management automatically creates list prices based on formulas you define. Price adjustments can be for an order line or the entire order. Pricing rule A mathematical formula used to define item pricing. Bill To. the Scheduling level controls the way scheduling works at the time of order entry for lines. item category or service offered. the ship-to location.  For example.List price In Oracle pricing. item categories or service offered.00 each. Price adjustments can have a positive or negative impact on the list price. Price adjustment The difference between the list price of an item and its actual selling price. All prices in a price list are for the same currency.  Enable you to group orders and lines. The batch source also controls invoice defaults and invoice numbering. Transaction Type Order and Lines can be grouped together loosely as certain Transaction Types. if two of item A cost $10. You define the list price on a price list. and internal or external orders. the base selling price per unit of the item.  Can act as sources for order and line level attribute defaulting. The selling price is the unit cost for a particular item. Price adjustments that lower the list price are also commonly known as discounts. Transaction batch source A source you define in Oracle Receivables to identify where your invoicing activity originates. the selling price is $10.  Can default from the Customer. Transaction type A feature that allows you to specify default values for orders and order lines including the customer.  Can establish order or line level processing constraints. and line transaction types can default from the order transaction type. All price adjustments are applied against the list price.00 for each unit. Transaction Type Code determines whether the transaction type is an Order Transaction Type or a Line Transaction Type. a transaction type can be used to default attributes/controls for an order or a line. Thus. Selling price Selling Price is defined as the price derived after applying price adjustments to the list price. You create a pricing rule by combining pricing components and assigning a value to the components. or Deliver-To site at the order header.

Generic hold A hold that will prevent the order/order line processing. In a process diagram. E. You can place a hold on any order or order line. Purchase Order (PO) / Sales Order (SO) The term ‘purchase order’ represents the order as defined in the Purchasing application. Transition In Oracle Workflow. Release criteria The criteria specified in the Pick Release window which defines which eligible order lines to pick release. Hold type Indicates the kind of hold you place on an order or order line. An order cycle lets you define the activity an order follows from initial entry through closing. Order Management gives you the power to release holds for specific orders or order lines. You can define as many order cycles as your business requires. The term ‘sales order’ represents the order data as defined in the Order Management application. the relationship that defines the completion of one activity and the activation of another activity within a process. a hold should be placed such that it prevents the customer’s orders from progressing to the next activity.Transaction type code Transaction type code determines whether the transaction type is an Order Transaction Type or a Line Transaction Type.g. if a customer has bad credit history. the arrow drawn between two activities represents a transition. Oracle Order Management holds all new and existing orders for the customer or item in your hold source until you remove the hold source. Order cycles are assigned to order types. Order cycle A sequence of actions you or Order Management perform on an order to complete the order. Release of Hold The action of removing the hold on an order. Create a hold source when you want to put all current and future orders for a particular customer or for a particular item on automatic hold. such as customer and item. Hold criteria can include  Customers  Customer sites  Orders  Items Hold source An instruction for Order Management to place a hold on all orders or lines that meet criteria you specify. You can create holds based on a combination of two criteria. Hold A feature that prevents an order or order line from progressing through the order cycle. 87 . while still maintaining the hold source. or item and warehouse. Hold criteria A criterion used to place a hold on an order or order line.

this controls an order’s workflow activity. Oracle or Non-Oracle system. shippable. the order line is automatically updated to indicate that it was fulfilled. the company running Order Management is modeled as the company to whom the end customer places the original order. Order Import Order Import is Oracle Order Management’s Open Interface that import orders from an internal or external source. credit checkpoint. to indicate that we are defining the process from this point of view. etc. Order Management sends information to the Purchasing Application to create that PO. Drop shipment A Drop Shipment occurs when a customer order is sourced from and delivered by a supplier. that a normal order entered through the Sales Order window would have gone through. line type (standard. The selling company buys a product from a supplier and has the supplier ship the product directly to customers. We call this process Vendor Drop Shipment. Only standard items may be drop shipped. Blanket Sales Agreement A sales order for a customer that has specific characteristics related to an order between a customer and a vendor. as long as the items are part of your item master and price list. An order cycle lets you define the activity an order follows from initial entry through closing. Each order line goes through a cycle appropriate to the order type. order number sequence.Order Processing Cycle A sequence of actions you or Order Management performs on an order to complete the order. kits and models cannot be drop shipped at this time. and then when that PO is received (to indicate shipment from the supplier to your customer). Receivables allows you to authorize the return of your sales orders as well as sales made by other dealers or suppliers. Replacement order A sales order created to replace goods being returned by a customer. which performs all the validations before importing the order. 88 . return or internal) and item type (standard. In this process. stocking. A source type of External indicates Drop Ship. and transaction type. In Order Management. A method of fulfilling sales orders by selling products without handling. translatable. Order type Classification of an order. Blanket Order A sales order for a customer that has specific characteristics related to an order between a customer and a vendor.) of that line. or delivering them. Internal requisition A requisition in the Purchasing system that will directly result in the generation of a sales order in the Order Management system through the Order Import process in OM. model. The Source Type attribute on the order line controls whether a line will be fulfilled internally or drop shipped. Return material authorization (RMA) Permission for a customer to return items.

Internal Order A sales order in the Order Management system that is generated from an internal requisition in the Purchasing system and loaded into OM through Order Import. either system. and becomes an internal sales order when the information is transferred from Purchasing to Order Management. You can define business rules for defaulting values. If a defaulting rule definition fails to default desired values for orders or returns.or user-defined. Source Type) ■ Defaulting Condition ■ Precedence of Defaulting Condition (if multiple defaulting conditions exist. A defaulting rule includes the following components: ■ Defaulting Source/Value (Entity and Attribute. Closed order An order and its order lines that have completed all activities in its process flow and for which the close activity has been completed. precedence determines the condition to use) ■ Sequence (in what order is the rule applied if multiple rules exist) ■ Source Type and Defaulting Source/Value: (how the attribute value is derived Defaulting Sources A defaulting rule source is the location from which you obtain a defaulting value. Sales credit Credits that you assign to your salespeople when you enter orders. Also known as internal requisition or purchase requisition. you can choose to define additional defaulting rules for most attributes (fields) within Entities such as Order or Line. Defaulting Sources include:  Same Record  Related Record  System Variable  Constant Value  Profile Option  PL/SQL API Profile Option The profile option source enables you to use a profile option. usually the location is another entity and attribute. as a default value source. For most attributes. Internal Sales Order A request within your company for goods or services. such as inventory or manufacturing. You must indicate the name of the profile option to be used as the default 89 . you can assign at least one entity/attribute defaulting source. Credits can be either quota or non-quota and can be used in determining commissions. Defaulting rules Information that Oracle Order Management automatically enters depending on other information you enter. in addition to using other defaulting sources. invoices and commitments. and prioritize how conditions and validation rules are implemented. Order management – Defaulting Rule: Order Management Defaulting Rules reduce the amount of data input required when entering orders or returns. An internal sales order originates from an employee or from another process as a requisition.

Set up a defaulting rule for tax date with Same Record source and Source Attribute as Schedule Ship Date. For example a common requirement is to compute tax for an order line based on the scheduled ship date for that line.LINE_CATEGORY_CODE G_HDR. Constant Value The constant value source option enables you to specify a constant value instead of a field that contains a value. PL/SQL API If you have a complex defaulting rule that cannot be defined using any other defaulting source. you can use the API source. Your logic to derive default values can be coded into your custom PL/SQL API. For example Order Type can be defaulted from its value on the related objects: Customer. The source attribute in each case would be Order Type. if all items in your organization are sold with the unit of measure Each. Invoice To.LINE_TYPE_ID G_HDR. Bill To and Item.value in your rule.ORDER_CATEGORY_CODE G_LINE.INVOICE_TO_ORG_ID G_HDR. Same Record Using same record as a source. This is especially useful if you want your default to be the same value or to be used if no other sources you have defined for your rule can provide a value. you can setup the Request Date defaulting rule with System Variable as sysdate + 1. Defaults for certain attributes can be setup when defining related object records such as Customer. or Ship To. you can default an attribute from another attribute on the same entity record. For example. enabling you to reference you API within a defaulting rule. Related Record The Relates Record is one of the most frequently used defaulting sources. For example if the policy of your organization is to ship all items on the next day.ORDER_TYPE_ID G_LINE. For each attribute that you can use as a default.SHIP_TO_ORG_ID G_HDR. Ship To. Profile options sources enable for flexible default value tailoring without complex customizations. System Variable This system variable source option enables you to default system variables or functions of system variables for a field. Some of the Standard PL/SQL APIs: Package OE_ORDER_PUB Function G_HDR.SOLD_TO_ORG_ID 90 . you could define a defaulting rule to default the value of Each for the Unit of Measure attribute within the Order Line entity. This is commonly used to default date fields where SYSDATE expression or functions on SYSDATE can be used to default the current date or a function of the current date.SHIP_FROM_ORG_ID G_HDR. related record source objects/ source attributes are pre-defined in the system.

INVENTORY_ITEM_ID GET_PRIMARY_DELIVER_TO OE_DEFAULT_PVT GET_TAX_CODE GET_ACCOUNTING_RULE_DURATION GET_CC_EXPIRATION_DATE GET_CC_HOLDER_NAME GET_CREDIT_CARD_NUMBER GET_SOB_CURRENCY_CODE GET_COST_TYPES GET_SHIPPED_STATUS GET_COST_AMOUNT('INSURANCE') DATE_TO_CANONICAL NUMBER_TO_CANONICAL NUMBER_TO_CANONICAL G_LINE.FREIGHT_TERMS_CODE G_LINE.ORDERED_QUANTITY G_LINE. Deferred Accounting Rules 91 . You can use accounting rules with transactions that you import into Receivables using AutoInvoice and with invoices that you create manually in the Transaction windows.ORDERED_DATE OE_CHARGE_PVT FND_DATE FND_NUMBER INV_IC_ORDER_PUB Accounting Rules Rules that Oracle Receivables AutoInvoice uses to specify revenue recognition schedules for transactions. For example.G_LINE.IC_CUSTOMER_ID G_LINE. When you run the Revenue Recognition program for an invoice that is associated with one or more accounting rules.PAYMENT_TERM_ID G_LINE.SHIP_FROM_ORG_ID G_LINE.CUST_PO_NUMBER G_HDR.INVENTORY_ITEM_ID G_LINE.IC_CUSTOMER_SITE_ID G_LINE.PAYMENT_TERM_ID G_HDR. you can define a fixed duration accounting rule with monthly revenue recognition for a period of 12 months. Receivables creates the invoice’s revenue distributions for the period or periods in which the rules fall.IC_SELLING_ORG_ID G_LINE.FREIGHT_TERMS_CODE G_LINE.SOLD_TO_ORG_ID G_HDR.SHIP_TO_ORG_ID G_LINE. Accounting rules determine the number of periods and percentage of total revenue to record in each accounting period. Define accounting rules to create revenue recognition schedules for your invoices.PRICE_LIST_ID G_HDR.IC_SHIPPING_ORG_ID G_LINE. You can define an unlimited number of accounting rules. You can define an accounting rule where revenue is recognized over a fixed or variable period of time.

Revenue Accounting posts that portion of revenue into the subsequent open accounting period. that you entered. This causes Receivables to shift the schedule by one month. When you use deferred accounting rules. the rule is deferred in this example. March 2. If an accounting period is closed. Receivables recognizes the revenue in the period that you specify with the Actions wizard. all periods are open. but is later closed before you can finish adjusting this invoice’s revenue. You later earn the revenue using the Actions wizard. In this example. If you use a non-deferred accounting rule with multiple accounting periods. Revenue Accounting uses the schedule created by the Revenue Recognition program. However. and the start date is determined by the GL start date that you entered using the Actions wizard. illustrated by the February 2 row. but perhaps you entered March 2 as the GL start date. illustrated by the March 2 row. If you use a deferred accounting rule with a single accounting period. In this example. Revenue Accounting creates the revenue recognition schedule based on the rule. which means that Receivables creates a single distribution line that posts to an unearned revenue GL account when you run Revenue Recognition. The February 2 row shows what the original revenue recognition schedule would have been if the accounting rule were not deferred. If the GL start date occurs in a closed accounting period. This table illustrates what happens when you have a $300 invoice with a 3 month non-deferred rule. February is open at first. If you use a deferred accounting rule with multiple accounting periods. The tables below illustrate the difference between deferred and non-deferred rules. • This table illustrates what happens when you have a $300 invoice with a 3 month deferred rule and an original start date of February 2. the Revenue Recognition program creates a single distribution per line that posts to an unearned revenue GL account. Later. • 92 . Revenue Accounting posts that portion of revenue into the subsequent open accounting period.You create deferred accounting rules by selecting the Deferred Revenue check box in the Invoicing and Accounting Rules window during rule definition. If the invoicing rule on a transaction is Bill in Arrears. Revenue Accounting honors the original schedule. the Revenue Recognition program ignores the deferred flag. Revenue Accounting ignores the original start date from the transaction and uses the GL date. However. You can use deferred accounting rules only for invoices that are assigned the Bill in Advance invoicing rule. you use the Actions wizard to earn revenue on this invoice.

the invoice’s revenue. illustrated by the March 2 row. or Not Open period. then Revenue Recognition will create the distribution records for an unearned revenue account. Future. then the program generates the accounting for all other transactions in the submission. Revenue Accounting uses the original schedule.The February 2 row shows the original revenue recognition schedule that Receivables creates when you first run Revenue Recognition. Receivables consider this revenue unscheduled. Receivables will automatically create the reverse accounting entries. If you later decide that the GL distributions need to be reclassified. The Revenue Recognition program will create distribution records for the invoices and credit memos that you create in Receivables and import using AutoInvoice. Future. When you submit the program. tax. If a deferred accounting rule exists. at this stage. February is open. freight. February is now closed. or Not Open. but completes with a status of Warning. you can change the individual distribution on the transaction. or delete. If the Revenue Recognition program cannot create accounting distributions for a transaction. Therefore. Note: Revenue Recognition creates accounting distributions for all periods of status Open. When you re-earn revenue on invoices with non-deferred accounting rules. 93 . Revenue Recognition also creates the receivable. however. The Revenue Recognition program uses the accounting distribution sets that you specify in the Transactions window or import into Receivables using AutoInvoice to determine the accounts of your newly created revenue distribution records. then Revenue Recognition creates the distributions in the next Open. In this example. At this stage. Later. The program creates the revenue distribution records for all accounting periods specified by the accounting rule on each transaction line. incomplete. Receivables include the transaction at the bottom of the Revenue Recognition Execution report so that you know which transaction to correct. perhaps you discovered that the schedule was wrong. so you used the Actions wizard to unearn. Receivables posts February’s allocation to March. illustrated by the February 2 row. Recognizing Revenue Run the Revenue Recognition program to generate the revenue distribution records for your invoices and credit memos that use Invoicing and Accounting Rules. and AutoInvoice clearing account assignments which correspond to the GL date of each invoice included in your submission. Revenue Recognition selects all transactions that have invoicing and accounting rules and that have not yet been processed since you last submitted the program. Receivables consider this revenue scheduled. and then correctly re-earn. If any period has a status of Closed or Close Pending. You assign accounting rules to recognize revenue over several accounting periods.

You can include or exclude components in the equation to derive credit balances consistent with your company’s credit policies. Uninvoiced Orders.Credit check rule A rule that defines the components used to calculate a customer’s outstanding credit balance. Invoicing rules Rules that Oracle Receivables uses to determine when you bill your invoices. Tax. Include returns. and orders currently on hold. You can bill In Advance or In Arrears. Pick release rule A user-defined set of criteria to define what order lines should be selected during pick release. Invoicing Rule is selected in the Transaction form. Pick release An order cycle action to notify warehouse personnel that orders are ready for picking. Components include open receivable Balances. Freight and Special Charges. 94 .

Pick Release sequence rule The rule for pick release that decides the order in which eligible order line details request item reservations from Oracle Inventory. 95 .

Note: Release Sequence rule and Pick slip Grouping Rule are attached in Shipping Parameters form or in Pick Release Rule. the pick slip contains all orders released in that picking batch. and option class items. Bill of lading A carrier’s contract and receipt of goods transported from one location to another. 96 . Pick slip grouping rule Criterions for grouping together various types of pick slips. If you use the consolidated pick slip. Pick-to-order A configure-to-order environment where the options and included items in a model appear on pick slips and order pickers gather the options when they ship the order. The rule dictates how the Pick Slip Report program groups released lines into different pick slips.Pick Slip Internal shipping document pickers use to locate items to ship for an order. Pick-to-order is also an item attribute that you can apply to standard. model. If you use standard pick slips. Alternative to manufacturing the parent item on a work order and then shipping it. Pack slip An external shipping document that accompanies a shipment itemizing in detail the contents of that shipment. each order will have it’s own pick slip within each picking batch.

purchase order or sales order (only a suggested carrier) or at the time of transportation planning (planned carrier) or at the time of route scheduling (actual carrier). Delivery detail Contains items to be shipped out of a warehouse. They can charge to the customer in the order/delivery/invoice or not.Scheduling Order scheduling includes assigning demand or reservations. This date is either specified by the customer on a delivery-based demand transaction. or calculated by applying in-transit lead time to a customer-specified Shipment Date. This will cause the demand to be planned in Material Planning Systems. Freight Charges A shipment-related charge added during ship confirmation and billed to your customer. Freight terms An agreement indicating who pays the freight costs of an order and when they are to be paid. Carrier A Supplier that provides transportation services. Delivery Leg Consists of latest two stops where the delivery is picked up and dropped off respectively on the same trip. Freight Carrier A commercial company used to send item shipments from one address to another. Delivery A set of order lines to be shipped to a customer’s ship-to location on a given date in a given vehicle. and lots or subinventories to an order line. Freight terms do not affect accounting freight charges. Delivery date The date on which the product is to arrive at the Ship-To Location. After the delivery is closed. In the former case. A single delivery may include items from different sales orders and may include backorders as well as regular orders. the line is no longer available in the planning pool. warehouses. shipment dates. 97 . Delivery line A shippable and booked line from the planning pool. Multiple deliveries can be grouped into a single departure. Document Sets A grouping of shipping documents you can run from the Confirm Shipments window. which has been allocated to a delivery. the delivery line will also be considered closed. This may be a sales order line. a WIP line or a PO line. The delivery may travel through several legs to get to its final destination. Freight on board (FOB) The point or location where the ownership title of goods is transferred from the seller to the buyer. They can be referred to as deliverables. the selling company pays the charges. an RMA line. Delivery leg is synonym with the Bill of Lading. It can be assigned at the time of order entry. After allocation.

Shipment set A group of items that must ship-together. Shipment schedule An itemized list of when. and Waybill. Mailing Label. marking.Shipping The function that performs tasks for the outgoing shipment of parts. It may make other stops on its way from the starting point to its final destination. A shipment might contain just part of an order that is pick released and packed. Shipping documents Shipping related reports. These instructions are intended for internal use. where some of the items on the picking slip are not in stock. These stops can be for picking up or dropping off deliveries.  Must contain at least two stops 98 . if all items in that order are pick released and packed together. A shipment might also contain only part of a released order line. These stops may be for picking up or dropping off deliveries. DHL)  A Trip is an instance of a specific freight carrier departing from a particular location containing deliveries. Shipping instructions Notes that print on the pick slip. Trip An instance of a specific Freight Carrier departing from a particular location containing deliveries. Thus. and in what quantities to ship an order line. Vehicle Load Sheet Summary. components. The carrier may make other stops on its way from the starting point to its final destination. Pack Slip. It includes packaging. a shipment might contain an entire order. how. where.  Is carrier-specific (such as UPS. Commercial Invoice. such as the Bill of Lading. Shipment An individual package sent to a customer. and products. weighing and loading for shipment.

dropping off a delivery or both. and Miami to Dallas (stop 4). and Miami to Dallas Trip stop  A point along the route a trip makes to its final destination. The activity might include picking up a new delivery. stop is a release criteria for releasing items that have initial pick-up locations corresponding to the specified stop. or both.  A location at which the trip is due for a pick-up or drop-off. A Stop represents a point along the route that a trip makes to its final destination. This point may also have some activity associated with it.In the above Example.  In the above example.  This point may also have some activity associated with it. The activity might include picking up a new delivery. New York to Miami. Trip 1: San Francisco (stop 1) to New York (stop 2). or location. dropping off a delivery. In Pick Release. New York to Maim (stop 3). 99 . Trip 1 :San Francisco to New York.

in certain cases. Invoice value The total outstanding order value that needs to be invoiced. container capacities and. and on account credits from other systems to Oracle Receivables. A Payables feature that allows you to enter multiple invoices together in a group. Waybill number The number associated with a waybill that you record for the shipping batch at ship confirmation. An invoice batch can contain invoices in different currencies. Receivables display any differences between the control and actual counts and amounts. Batch sources A source you define in Oracle Receivables to identify where your invoicing activity originates. AutoInvoice A program that imports invoices. Fulfillment Sets One of the key features of fulfillment is to ensure order lines are invoiced together. When you enable you batch control system option. and other information that is sent to a customer for payment. Multiple Organization in Oracle Applications automatically creates invoice batches for Payables expense reports. including payment terms. which is the sum of the invoice amounts in the batch. A summarized list of charges. There are two activities which are considered fulfillment method activities (workflow item attribute) in the seeded Order Management workflow process. invoice item information. This document may list any tax and freight charges. Within Order Management fulfillment functionality is controlled by the workflow activity Fulfill. and all standard invoices. the loading order for the customer’s specified unload order. Also known as invoice batch sources. You can also optionally enter batch defaults for each invoice in a batch. Waybill A document containing a list of goods and shipping instructions relative to a shipment. Invoice batch A group of invoices you enter together to ensure accurate invoice entry. The batch source also controls invoice defaults and invoice numbering. For a standard shippable line. credit memos. Invoice A document you create in Oracle Receivables that lists amounts owed for the purchases of goods or services. Planning the trip requires consideration of vehicle load capacities. and not separately. An order is considered fulfilled when the Fulfill workflow activity has successfully completed. prepayments. and recurring invoices. and the total batch amount.Trip planning stop The process of planning the necessary vehicles and grouping the scheduled shipments that will be included in a given trip. Credit memo A document that partially or fully reverses an original invoice amount. the fulfillment 100 . Invoices within the same batch share the same batch source and batch name. for each batch of invoices you create. or number of invoices in the batch. You enter the batch count.

Ship sets are limited to order lines that contain the same following identifying order/line attribute values:  Ship From and Ship To Organization (a null value within either of these fields is not valid)  Scheduled Ship Date Arrival Sets Arrival sets ensure all order lines within the set definition are scheduled to arrive at a customer site on the same date regardless of shipping method and ship to location. but are limited to the order for which they were created  Ship from different warehouses and ship on different days All order lines within a Arrival Set must have the following identical identifying order/line attribute values:  Order Line Scheduled Arrival Date  Order Line Ship To Organization 101 . to ensure that the order line is not released until the full quantity is available.  For orders that contain multiple lines with the same item. For a return line the fulfillment method activity is the Receiving activity. Ship sets ensure that all order lines within a Ship set do not progress past the Ship workflow sub process within respective line flows until all lines within the set have available quantity to ship.method activity is the Shipping activity. You can use ship sets to do the following:  Assign a single ship set to all the lines in an order to support your customers that do not allow partial shipments. Arrival sets can:  Span multiple organizations. assign the order line to a ship set. Ship Sets Ship Sets enable you to group order lines within a set for shipment.

Different Types of Sales Order Flows Different types of Sales Order flows:  Standard Sales Order Flow 102 .

and Purchasing etc.) and status of orders.Return Material Authorization (RMA) Internal Sales Order Flow: Drop Shipment Order Flow CTO Configure To Order (Assemble To Order) Back To Back Order (Procure To Order) Flow Standard Sales Order Flow: Standard Sales Order Flow: In Oracle Order Management.Process Steps: This section will guide you through a basic sales order flow from entry to invoicing. Order Management offers Line level independence where you can capture regular orders as well as returns using the same form. view. including:  Enter a Standard Sales Order  Schedule the Order  Book the Order  Pick Release  Ship Confirm  Fulfillment 103 . Standard Sales Order . The sales order form offers users a convenient and quick entry point for creating and editing order information as well as viewing summary information from other subsystems (i. and update order information. Shipping. enter. Receivables.e. the sales order form enables you to organize.

shipment scheduling. processing constraint checks. All data is checked for validity during the import process. Customer & configuration Information against Inventory Item & Customer already defined 104 . Manual entry  You can enter order manually  Tax.  The Order Import include validation and defaulting.  Demand can also come from Internal Sources like other Inventory Organizations as Internal orders. updating or deleting the orders in the data base tables. then ultimately inserting. shipping constraints. applying and releasing of order holds. invoicing constraints and sales credits have to be specified  The system Validates the Item. Invoicing Interface Entering a Sales Order: Order Import  A Sales order can be imported from other sources.

manual Order Booking and Scheduling: Check Credit holds  Automatically checks for sufficient credit limit for the customer in the entire order booking and fulfillment cycle  Puts order on hold in case of credit check failure  Authorized personnel can release holds  Customers can be given higher credit limits after analysis  Automatic release of order holds after increase of the  credit limit Book Order  Orders are booked after all check points have been qualified for the organization  All terms and conditions are frozen  Order becomes the legal contract after being booked Schedule Order  Automatic selection of the warehouse based on geographical proximity to the customer and other user defined rules  Automatically/manually schedules the shipment or the arrival date at the customer’s premises based on stock availability and planned supplies  Considers resource. material and suppliers’ constraints while scheduling the orders when Constraint based planning is in place  Automatic/manual reservation of stock after scheduling 105 .Scheduling:    Communications tool for balancing customer demands with ability to fulfill the demand Provides a schedule date and warehouse that would fulfill the demand Options – autoschedule.

    Request date – date which customer requests the product to be shipped / received Promise Date – date on which we agree to ship / customer would receive Schedule Ship date – date on which quantity should be available for shipment Schedule Arrival date – date on which customer would receive the product. Satisfy Demand: Manufacturing Strategy  MTS – Make to stock environment entails building end products to a forecast and maintaining a safety stock depending on desired service levels  BTO – Build to order environment has the following variants o Assemble to order (Postponement) entails building generic/key ubassemblies to a forecast and using final assembly schedules to assemble end products based on customer orders in order to reduce delivery lead times to the customer o Make to order environment entails procuring raw materials. procuring and building end products upon receipt of a customer order  Procure to Order has the following variants o Drop shipment (Supplier ships directly to the customer upon receipt of a customer order) o Procuring customer specific configurations based on customer orders 106 . building subassemblies / end products after receiving a customer order leading to increased delivery lead times  ETO – Engineer to Order entails designing.

Picking Engine creates Move Order:  Must Detail to Print Pick Slips  Creates reservation from Org.Available To Promise:  Quantity of current on hand stock. outstanding receipts and planned production not committed  Can be viewed by clicking on the availability button Pick Release: An order cycle action to notify warehouse personnel that orders are ready for picking. creates Move Orders that move the inventory to staging areas. calls Inventory Pick Release to reserve items and print the pick slips. Item. Ship Confirmation * May be automated   Pick Release finds and releases eligible order lines that meet the release criteria. and optionally. Pick Release 2. and Qty Auto Detailing Suggest souring for material immediately based on established picking rules Set as default in the Organization Shipping Parameters form Allocating Inventory: 107 . Move Order Line Pick Confirmation* 4. Move Order Line Detailing* 3. Finds and releases eligible order lines that meet the release criteria and creates move order Configurable Process (four steps) 1.

Allocate Move Order: • Allocating is the process that uses Inventory picking rules (FIFO. If adequate quantity is not available to detail the move order. this process can 108 . The detailing process fills in the move order line details with the actual transactions to be performed.  Reservations created for sales orders are automatically updated and transferred for the user as the move order is released and transacted. • The allocating process fills in the move order line details with the actual transactions to be performed and allocates the material to the move order. The move order is created by the Pick Release engine.” Detailing is the process by which Oracle Order Picking and Shipping uses the picking rules to determine where to source the material to fulfill a request line (move order line). the move order must be “detailed. • Warehouse management uses the Rules Engine to determine the appropriate material allocations in order to improve picking efficiency Procedural Flow for Material Picking Move Orders: 1. 2.  Pick release process creates move orders which are pre-approved requests for subinventory transfers to bring material from its source locations in the warehouse to a staging subinventory. Next.Move Order  A move order is a request for a subinventory transfer or account issue. LIFO etc) to determine where to source the material to fulfill a request line.

the order number. or the user can manually fill in the details. the order remains open until the full quantity is transacted or the order is closed or canceled. a source and destination if known. it also creates the reservation for the material. or users can transact one detail line at a time as the items are moved.be repeated later. users may print a pick slip or push the move order line details to mobile devices for transaction through the move order APIs. a requisition for subinventory transfer and so on. They store the item. this information is filled in at the line detail level. The line details are the Inventory transactions that occur to fulfill a particular request line (move order line). or serial controlled. and any project and task references if the organization is Project Manufacturing enabled. The Move Order Line Details (transaction lines) created by the detailing process must be transacted to confirm the material drop-off in staging. lot. The user now transacts the move order to confirm the pick. The lines are the requests on that move order. If the user transacts less than the requested quantity. Pick confirmation executes the subinventory transfer that moves the material from its source location in the warehouse into the staging location. If the material is locator. These details are automatically filled in by Oracle Inventory using the Inventory Picking Rules and the Item . This refers to the entity that created the move order. and the requested date. completed quantity (if the move order has been partially fulfilled). The user can also request specific serial or lot numbers if know. Pick Confirmation automatically transfers the 109 . on the move order line. 3. An order could be a pick wave (for sales order picks) a replenishment type. These details can be edited prior to transaction by a user. This process is called Pick Confirmation. If no reservation exists before the detailing process. The order line can be transacted all at once. requested quantity. Before transaction. Move Order Components: Anatomy of a Move order: Oracle Order Picking and Shipping stores the move order source type in the header. Order Picking and Shipping also stores the default source and destination if available.Transaction defaults (for destination locators).

a pick slip can be printed or the move order line allocations can be pushed to mobile devices for transaction through the move order APIs.” Users can set up a default Pick Confirm policy in the Inventory organization parameters. At pick confirmation. If mobile devices such as bar code scanners are used to perform inventory transactions.  Pick Confirmation automatically transfers the high level reservation to a allocated reservation (including lots. A user can still manage any discrepancies found by deleting the reservation and transacting the material back to its original subinventory. a user can report a missing quantity or change the transaction line if the picker chose to use material from a different lot. Pick confirmation  The move order line details must be transacted (in Inventory) to confirm the material dropoff in staging (Destination Inventory). a user can report a missing quantity or change information if material is picked from a different lot. serial. subinventory and locators) in the staging location.high level reservation to a detailed reservation (including lots. Ship Confirmation Business Flow: 110 . locator. the Pick Confirm transactions can occur immediately after the lines are detailed. or subinventory.  At pick confirmation. revisions. This option is called “auto pick confirm. Note that even if an automatic pick confirm is employed. Pick Confirmation:  The Move Order Line Details created by the detailing process must be transacted to move the material to staging  Auto Pick Confirm – Set as default in the Shipping Parameters form – Can be overridden at Pick Release Print Pick Slips  Before a move order is transacted. If an organization’s picks rarely deviate from the suggested picking lines and the overhead of requiring a Pick Confirmation is unmanageable. This default can be overridden at each Pick Release. subinventory. serial. locator. and locators) in the staging location. or subinventory. you should use manual pick confirmation for greatest inventory accuracy and control. the material is only transacted to the staging subinventory and reserved.

Ship Confirmation: Pack Material  Automatic volume & weight calculations  Automatic selection of containers  Control on fill percentage Transportation 111 .

cost of sales accounting Note:   If defer interface check box is unchecked. interface to Inventory and OM takes place (=> inventory gets decremented and order line gets updated with shipped quantity) If defer interface is checked.  Selection of mode of transportation Selection of carrier & service level Freight Cost  Provide integration with UPS for automatic calculation of freight based on service levels & zip codes  Charge freight to the customer at actual or with markup Shipping Document  Shipping labels  Generate packing list  Generate Bill of Lading  Can be integrated with 3rd party software for exports compliance/ documentation Confirm Shipment  Allows over/under shipment based on customer’s tolerance level  Automatic reduction in inventory. “Interface Trip Stop – SRS” request needs to be run to effect interfaces to Inventory and OM. 112 .

backorder quantity = requested quantity). the full quantity (10) is shipped and displays in the Shipped Quantity field. For example. For example. Cycle Count action. For example. Unspecified Quantities Cycle Count: Ship confirms the quantity of items specified in the Shipped Quantity field. if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values entered). backorder quantity = requested quantity) and transfers the backorder reservation to cycle counting. the full quantity (10) remains in the Stage Quantity field and the line is no longer associated with a delivery. if you want all staged delivery lines grouped together in a new delivery. Note: If a non-zero Stage Quantity exists on a line. You can also transfer delivery quantities to cycle count prior to ship confirm by using the Shipping Transactions form. 113 .  Backorder All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0.  Ship Entered Quantities. the full requested quantity is shipped (10) and displays in the Shipped Quantity field. if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values).  Ship All: Ship confirms the entire quantity regardless of what was entered in the Shipped Quantity field (shipped quantity = requested quantity). Unspecified Quantities Backorder: Ship confirms the quantity of items specified in the Shipped Quantity field and treats blank quantities as full backorders (backorder quantity = requested quantity).Ship Options region:  Ship Entered Quantities. Cycle Count action. click Go to ship confirm and save your work. For example. For example.  Enable the Create Delivery for Staged Quantities box (default setting). Note: If the delivery status is Closed. Unspecified Quantities Ship: Ship confirms the quantity of items specified in the Shipped Quantity field and treats blank values as full quantity (shipped quantity = requested quantity). the full quantity (10) is backordered and displays in the backordered Quantity field. You can also transfer delivery quantities to cycle count prior to ship confirm by using the Shipping Transactions form. the full quantity (10) is backordered and transferred to cycle counting.  Ship Entered Quantities. the delivery is unassigned from all trips and all lines will be unassigned from the delivery. If you do not want to create a trip for the delivery. treats blank quantities as full backorders (backorder quantity = requested quantity). Unspecified Quantities Stage: Leaves the unspecified delivery line quantity as staged and removes it from the delivery. if the Requested Quantity is 10 and the Shipped Quantity field is 5.  Cycle Count All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0. and transfers the backorder reservation to cycle counting.  Ship Entered Quantities. it is split from the line and unassigned from the delivery. if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values). If the Create Delivery for Staged Quantities is enabled. if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values). all staged delivery lines are grouped together in a new delivery.

This enables you to specify the stop departure date which is the date Order Management Inventory interface will occur. One way to ship confirm one or more deliveries is to enable the Set Delivery in-Transit and Close Trip fields in the Confirm Delivery window: o Set Delivery In-transit: Creates a trip and stops for the delivery. o If you enable the Defer Interface box and run Ship Confirm. You can enter a future Actual Departure Date. Information to Customers  Invoices (Can be single or Consolidated) are sent to Customers through Post. Sets status of delivery to Intransit and initiates Order Management (OM) and Inventory interfaces.  Enable the Create Bill of Lading box if you want to create a Bill of Lading. is cleared. If Allow Future Ship Date is selected.  Defer Interface box o If you disable the Defer Interface box and run Ship Confirm. inventory gets decremented and the order line is updated with the shipped quantity. This generates a Bill of Lading number and prints it if it is part of a document set. do not do so as you receive an error. In the Auto-create Trip Options region. you receive a warning and the Inventory Interface concurrent process does not process the transaction until the actual departure date. you need to run the “Interface Trip Stop“SRS concurrent request to update the Inventory and the Order Line status. select or update the Ship Method and the Actual Departure Date. but leaves second stop open. all stops.  Entered Manually in Receivables module. and the delivery. When the Defer Interface box is enabled. If Allow Future Ship Date in the Shipping Parameters form. Shipping Transactions tabbed region. o Close Trip: Creates a trip and stops for the delivery. E-mail & EDI Transmission 114 . Creating Invoices: Invoice Generation Sources  Imported through other legacy systems & other Oracle applications automatically by AutoInvoice Interface program. a request is not automatically submitted to interface the trip stops. Closes the first stop of the delivery. Closes trip.

OM Standard Header Workflow: OM Standard Line Workflow: OM Standard Line Workflow: 115 .

quality data.   To Picking subinventory Cr.COGS Dr. After import into AR. This lets you collect material movement transactions such as receipts.Staging subinventory Dr. issues. and shipments. completions. At Ship confirm . To Material Cr. movements. To Tax a/c Cr. 116 . OE_ORDER_HEADERS_ALL: Stores header info of a so OE_ORDER_LINES_ALL: Stores Line Info Of A So WSH_DELIVERY_DETAILS: Stores Delivery Details(For Various Lines) Of A So In Shipping WSH_NEW_DELIVERIES: Stores delivery information WSH_DELIVERY_ASSIGNMENTS WSH_TRIPS WSH_TRIP_STOPS WSH_DELIVERY_LEGS RA_INTERFACE_LINES: Receivables interface table for storing OM info RA_CUSTOMER_TRX_LINES_ALL: Stores Invoice Info In AR RA_CUSTOMER_TRX_ALL: Stores Invoice Info In AR Tables that get updated: • • • • • • • • • • • Overview of Oracle Manufacturing APIs and Open Interfaces Oracle Manufacturing products provide a number of open interfaces so you can link them with nonOracle applications. Basic Business Needs Oracle Manufacturing product APIs and open interfaces provide you with the features you need to support the following basic business needs:  Connect to data collection devices.Accounting entries in the cycle:  At pick release . To Revenue a/c Cr. This speeds data entry and improves transaction accuracy.Receivables a/c Dr. and even the applications of your suppliers and customers. applications on other computers. applications you build.

Credit order types have an order type category Return and an order with mixed order type category can contain both regular and return lines. Control processing of inbound data imported from outside Oracle applications. custom and legacy manufacturing systems — to create integrated enterprise wide systems. Process Flow This section will guide you through a basic flow for a Return for Credit with Receipt. and resubmit imported data that failed validation. reference a sales order. After you have selected the sales order or order lines. use the Copy function in the Actions list to generate the return order or line by specifying an RMA line type. from entry to generating a credit memo. invoice. Line types can be variations of Return. Checked the Order Status as Order Status – Booked Order Line Status – Returned 5. Review. An order can have a mix of outbound (regular) and inbound (return) lines. Lastly. View the Credit Memo in Order Management 8. such as Return with Approval. identify a sales order to be returned and query the order lines. Return for Credit only. PO number or serial number of an item directly in the Return Reference field within the Line Items tab of the Sales Order form. etc. Check the on-hand quantity of the item in Inventory to verify that correct quantity was received. manually enter return line information and choose the appropriate return line type in the Sales Order form. for return without originating sales order line. Second. Connect to external systems — such as the customer’s purchasing system and the supplier’s order entry system — to better integrate the supply chain via electronic commerce. and have a line type category of RETURN. including: 1. Export data from Oracle Manufacturing products RMA Flow Overview RMA is often used synonymously with Return or Credit Orders and Returned Material. Create an RMA having a single line whose originating transaction is unknown 2. Run Workflow Background Process 6. There are three ways to create RMA’s within Order Management.Awaiting Return 3. Each order type and each line type is associated with a workflow process. Book the RMA After booking the order: Order Status – Booked Order Line Status .. Receive the RMA using the Receipts form of Oracle Purchasing 4. if not restricted by the order type definition.      Connect to other systems — such as finite scheduling packages. update. Check the Shipped and Fulfilled quantity on the RMA line 117 . Run ‘Auto Invoice Master Program’ to generate a credit memo 7. A return line is indicated by Line Type and by its negative and highlighted item quantity and line total price. computer-aided design systems. First. Validate imported data to ensure integrity of Oracle Manufacturing products.

in the Order Information tab of the Sales Order form. the user will enter the same information (i. is exactly the same as entering an order. Figure 6–1 is the Sales Order form for entering the Header information for the RMA: Once the Order Header information is entered. Customer Name.Enter the RMA on the Sales Order form. Order Type. you will enter the line information within the Line Items screen. except at the line level where the user specifies the Line Type as a Return and a negative line quantity and total quantity appear on the form. Refer to the Workflow section for details on the Generic Order and Line workflow for returns. Thus. Entering a return on the Sales Order form.) as a standard order. The Standard order type is assigned to a Generic Order and Line workflow. which allows either an order or return to be entered. as seen in Figure 6–2 : 118 . etc.e.

Check the box next to the line you wish to receive. Product Discontinued). A Return Reason is required to be entered (i. we are entering a single line RMA where the originating transaction is unknown. Tab through the Header window to the Receipts Line window.In the Main Tab. Once you are in the Receipts Line window. Change responsibilities to Purchasing and navigate to the Receiving > Receipts form. The user can enter a positive or negative number. You will also see that the negative quantity will be highlighted in another color. the user is creating a transfer to inventory transaction in Purchasing. Save this transaction and record the receipt number in the Header window. Book the RMA. Receive the RMA using the Receipts form of Oracle Purchasing. These items are now considered as supply. in the Returns tab. In the Receipt Header window. In the Receipts form. The organization you choose should be the same warehouse where your RMA is created. the RMA number and quantity will populate the form. Purchasing will communicate the quantity received to Order Management to update the RMA. enter the Ordered Item and the Quantity to be returned. the user will need to enter the Line Type as a return (i. Return for Credit with Receipt of Goods) and enter a Return Reason. By choosing the Destination Type as Inventory. select the Customer Tab and find your RMA #.e. Since we did not reference a sales order. enter a Destination Type as Inventory and subinventory. Next. Users are able to book an order or return at either the Order Information Tab or Line Items Tab via the Book button. an Organization window will be displayed if this is the first time you have navigated to the Purchasing > Receipts form since your login. 119 .e.

120 .

Select the Autoinvoice Master program and run the program for your RMA # and specify the invoice source as the one associated with the line type of the RMA line. The eligible lines will automatically be put into a fulfillment set. The Workflow process of the return line(s) will be on the Invoice Interface activity. 7. 8. In the Material Transactions form. 121 . an Organization window will be displayed if this is the first time you have navigated to the Inventory > Material Transactions form since your login. However. Once the information is written to the tables. note that the credit memo is not actually generated until the Autoinvoice program in Receivables has been run. Fulfill RMA line. the subinventory chosen and the quantity specified to be returned from the Receipts form.6. Lines that are not in a fulfillment set simply pass through the activity automatically. The fulfillment activity acts as a synchronization point for all lines on the order that are in a fulfillment set. The invoice interface activity places the information from the return line into the Receivables Interface tables. To run the Autoinvoice program. The credit memo will then be viewable in the Sales Order form. Check the on-hand quantity of the item in Inventory to verify that correct quantity was received. the user needs to change responsibilities to Receivables and navigate to the Interfaces form. This form will show you your item #. Generate a credit memo for the return. The lines in the fulfillment set will wait at the fulfillment activity until all the lines in the set have reached the activity. the invoice interface activity is complete. Find the item name being returned and navigate to the Transaction Type tab. The user will not have to perform anything during this step. Change responsibilities to Inventory and navigate to the Transactions > Material Transactions form. Verify that the source type is RMA and the source is your RMA # for the quantity being returned. The Autoinvoice Master program will generate the Autoinvoice Import program which generates the credit memo. once the Fulfillment activity completes. The organization you choose should be the same warehouse where your RMA is created. and the line proceeds to the close line activity.

select the Actions button and choose Additional Order Information. This form will show your the credit memo number and amount. 122 . View the credit memo in Order Management. To add the field. the user needs to use the folder technology to add the field to the sales order form. click on the Warehouse field in the Shipping Tab of the Line Items form. Check the Shipped and Fulfilled quantity on the RMA line. select the Folder menu at the top of the form.9.  And Book the Order and save it  Note down the RMA number Go To Purchasing Order Responsibility #        #   N – Receiving – Receipts Change the Org to ship_to Org In find expected receipts window customer tab enter the RMA number and Click on find button Receipts window. the user need to change responsibilities to Order Management > Orders. From the above step. Once the Additional Order Information form has opened. Line Tab check the check box set to Yes on the Line Order In the Line Order enter the sub inventory of the Org Save the form It automatically saves the return order Item (RMA) in the sub inventory. Next. Query your RMA # in the Order Organizer. Returns > Order Organizer form. Go and check whether it is updated the item or not in Inventory Come Back to Order Management In SO window check the Status its “Closed” Order Management automatically closes returns that have successfully Completed their order flow. if you have the close order activity within your order flow. To access the Fulfilled Quantity field. To view the credit memo in Order Management. Returns – Sales Order  Create Standard Sales Order Book the Order  Release the Sales Order (Pick Release)  Ship the Sales Order by Shipping – Transaction (Query with the SO and note the SO number)  Now Again Create the New Sales Order  In the Line Items tab enter the same quantity as entered on the above raised Sales Order or Give the SO number in the Returns tab  Line Items tab in Returns tab Line Type field enter the Return(Receipts)  Give the Sales Order number in the Reference Field  Give the Reason in the Return Reason. Scroll to view the Shipped Quantity field. navigate in the Sales Order form to the Line Items tab for the RMA. 10. select Show Field and choose the Quantity Fulfilled field from the list. Implementation Steps: # Order. The Shipped Quantity means the received quantity for return lines and the Fulfilled Quantity means the delivered quantity for the return lines. Once the RMA is queried. click on the Receivables tab to view the credit memo. The field will populate in the form.

Price List. Subtotal.  Enter the Schedule Ship Date  Click on the Actions button select the split lines  Splits the line item quantity into different lines with different dates  And click on the Split line button as shown in the above picture  Automatically splits the lines  Save it and Book the order by clicking on the Book Order button. FOB. Tax. Shipping Method.Release Sales Order Order Tab:  Enter the Sales Order number and press tab it automatically takes everything Inventory Tab:  Enter the Warehouse number automatically takes Pick slip grouping rule. Tax handling Line Items . automatically the UOM will come. Auto allocate.# N – Orders. Currency. Bill to Locations. Warehouse. Sales Person. Charges and Total  Choose the Order Type Others Tab:  Automatically comes with the Customer name or Customer number you have Chosen Payment Terms.Main Tab:  Enter the Item number. Status. Freight Terms. Auto pick confirm. Sub Inventory 123 .Main Tab:  Choose the Customer Name and Choose the Customer Number  Relating to Customer fields information is displayed automatically Ship-to. Returns – Sales Order Order Information .  Enter the quantity in qty column automatically the Unit Selling Price will come.  The status is “Awaiting Shipping” # N – Shipping – Release Sales Order . Date Ordered.

#    N-Shipping-Transaction Find with the Sales order number and you will find the screen as shown above The status will be “Staged” for the release order and “Ready To Release” for future dates Select the Line order to shipping and click on Delivery Tab and select the ship confirm from the Actions and click on go button.    And give the Concurrent Request by clicking on Concurrent button Run the Pick Slip Report See the output of Pick Slip Report the data is come or not by clicking on the View output button In sales order window query with the sales order number and in line items tab See the status is “Picked” for the date which is release the order and “Awaiting Shipping” for the future dates. (2) For selecting the multiple line shipping hold Ctrl key and click on the lines To ship and select the ship confirm for Actions and click on go button The status will be “Closed” Check the Sales order window in Line Items Status is “Shipped” and future release order status will be “Awaiting shipping” Check the On Hand Quantity is reduced in the Inventory stores. Automatically its is shipped (1) For only one line as to ship select the Delivery Actions select the unassigned to delivery and then give the ship confirm in Delivery Actions and click on go button.    124 .

The Source Type attribute on the requisition line controls whether a line will be fulfilled internally or purchased from a supplier.Internal Sales Order Flow Internal Sales Order Flow: Overview: The Internal Requisition/Internal Orders process is used for requesting and transferring material from one inventory or expense location to another. So. the requisition can be received to record receipt of goods. Sourcing rules can automatically determine if the source type is to be Inventory or an external supplier. Order Management is seeded with an Order Source of Internal. to identify lines created from internal requisitions. It is not possible to manually enter Internal Orders using the Order Management user interface – these orders must come in via Order Import. Order Management receives information from the Purchasing Application to create an Internal Sales Order. When the sales order is shipped (to indicate either intra or interorganization movement of goods). A source type of Inventory indicates an internal order. Requesting Org (M1) will place the order request on Source Org (M2). An Internal Requisition is initiated in Oracle Purchasing. The internal requisition id is stored in the Original System Reference column on the order header of the Internal Order. for the Source Org (M2). the Requesting Org (M1) becomes a customer and hence an internal customer needs to be created for it and this internal customer is then associated with the Requesting Org (M1) 125 .

c) Updates the Inventory Organization in Destination Organization Implementation Steps: Item Master Attributes: Main Tab Inventory Tab Bill of Material Tab Purchasing Tab General Planning Tab Lead Times Tab Work-in-process Tab Order Management Tab : : : : : : : : Standard *Inventory Item. This can also be scheduled as part of your set up to run periodically to meet business needs. Returnable *Customer should be “Internal” Purchasing Responsibility # • • Purchasing – Requisition – Internal Requisition Normally create the requisition with type “Internal Requisition” Give the Destination Organization number and site name 126 . Be sure to run Order Import using a responsibility that corresponds to the operating unit in which the internal order needs to be created. 5) After Order Import completes successfully. 8) Receive against the Internal Requisition. OE_LINES_IFACE_ALL). Check Material Storage BOM Allowed Purchased Purchasable Use Approved Supplier Make or Buy Source Type: Supplier Preprocessing –give some values Build in WIP Customer Ordered. This can also be scheduled as part of your set up to run periodically to meet business needs. Revision Control Receivable. a) Go to the Destination Organization in purchasing application b) Receive the Goods from Purchasing Application. 4) Run Order Import with Order Source = Internal in OM to create the Internal Order. Sourcing Rules may set source type attribute to Inventory. Observe that Order Status = BOOKED Line Status = Awaiting Shipping 6) Pick Release 7) Ship the Internal Order. 3) Run the Create Internal Sales Order concurrent program in Purchasing to load the Order Import tables (OE_IFACE_HEADERS_ALL.Process Steps: 1) Enter Requisition in Oracle Purchasing.*Stock able. or manually choose Inventory source type. Transact able. Assemble To Order. 2) Approve the Internal Requisition. Customer Enabled. *Internal Order Enabled. query the sales order. *OE Transact able. It is possible to create an internal order in an operating unit different from that of the internal requisition. Shippable. *Internal Order.

• • • # # Give the Source Inventory Organization and site name Approve the requisition by clicking the Approve Button Note down the requisition number Run the Request “Create Internal Order” Here records in Interface Tables Orders.REQUISITION_HEADER_ID gets stored in OE_HEADERS_IFACE_ALL.REQUISITION_LINE_ID) RCV_SHIPMENT_HEADERS 127 .SEGMENT1) PO_REQUISITION_LINES_ALL -. Returns – Import Orders – Order Import Request Order Source : Internal Order Reference : Give the Requisition Number Validate only : take default Instance : take default # • • • # Orders.PO Requisition Line After running 'Create Internal Order' data loads into OE Interface Tables OE_HEADERS_IFACE_ALL -PO_REQUISITION_HEADERS_ALL.ORIG_SYS_DOCUMENT_REF OE_LINES_IFACE_ALL After running 'Import Orders' data loads into OE Main Tables from the Interface Table OE_ORDER_HEADERS_ALL OE_ORDER_LINES_ALL Receiving Tables RCV_SHIPMENT_LINES (RCV_SHIPMENT_LINES.REQUISITION_LINE_ID = PO_REQUISITION_LINES_ALL. Returns – Order Organizer Query with the requisition number Here it opens the Sales Order form Note down the Sales Order number here shows the status “Awaiting Shipping” Shipping – Release Sales Order – Release Sales Order • Give the Sales Order Number and click on the concurrent button • It will run the Pick Release document check there should be data • Query the SO and Check the Sales Order Status will show “Picked” Shipping – Transaction • Query with the SO number and Ship the Transaction • Query the SO and Check the Sales Order status will show “Shipped # Go to the Destination Organization and Receive the Goods Updates the Inventory Organization Tables Affected with Internal Sales Order: PO_REQUISITION_HEADERS_ALL -.PO Requisition Header (Requisition Number stores in PO_REQUISITION_HEADERS_ALL.

and automatically default the source type of External for order lines which need to be drop shipped Process Steps 128 . In this process. kits and models cannot be drop shipped at this time. the order line is automatically updated to indicate that it was fulfilled. to indicate that we are defining the process from this point of view. the company running Order Management is modeled as the company to whom the end customer places the original order. We call this process Vendor Drop Shipment. you can:  Optionally receive and electronically process Advanced Shipping Notices (ASN)  Automatically perform logical receipts upon notification of shipment  Perform Drop Ship for both make and buy items. The benefits of drop shipping include:         No inventory is required Reduced order fulfillment processing costs Reduced flow times Elimination of losses on non-sellable goods Elimination of packing and shipping costs Reduced inventory space requirements Reduced shipping time to your customer Enables you to offer a variety of products to your customers When processing drop shipments for orders.Drop Shipment Order Flow Drop Shipment Order Flow Overview: A Drop Shipment occurs when a customer order is sourced from and delivered by a supplier. and then when that PO is received (to indicate shipment from the supplier to your customer). The Source Type attribute on the order line controls whether a line will be fulfilled internally or drop shipped. A source type of External indicates Drop Ship. Only standard items may be drop shipped. Order Management sends information to the Purchasing Application to create that PO.

These changes need to be manually updated in Purchasing and then communicated to the vendor. Drop ship order lines can be processed for standard items. Run Requisition Import in Purchasing to create the requisition. 2. Create a PO or autocreate a Blanket PO release from the approved requisition. 5. If the vendor does not send ASN. Create a PO or autocreate a Blanket PO Release from the approved requisition. receipt can be entered manually (passive receiving). Sales Order/Purchase Order Discrepancy Report. or the user may manually choose External source type. 3. the changes are not automatically communicated to Purchasing. Defaulting Rules may set source type attribute to External. When the vendor ships product to your customer. a Purchase Release concurrent program can be run to do the same. A drop ship order can be changed or canceled in Order Management after it has been sent to Purchasing but before receipt. OM workflow proceeds to next step. However. When the vendor ships product to your customer. typically invoicing of the end customer. approve the requisition to generate the Purchase Order. Create Supply workflow step loads OM information into Purchasing’s Requisition Import tables. or choose to have manual intervention to receive the ASN. This is sent to the vendor. shows what orders have changed. Inbound and outbound material transactions are automatically created for accounting purposes. Run Requisition Import in Purchasing to create the requisition. Order Management workflow proceeds to next step. to indicate shipment to the customer. 4. Alternatively. or even an invoice. Inbound and outbound material transactions are automatically created for accounting purposes. A report. or even an invoice. you may receive an ASN. You can set the profile PO: Automatically Deliver Drop Ship ASNs to trigger automatic receipt of the ASNs in Purchasing. a Purchase Release concurrent program can be run to do the same. The receipt triggers automatic receipt of the line in Purchasing. Non SMC PTO models. Enter and book an order Defaulting Rules may set source type attribute to External through the organization level item attribute setting—Default SO source type for the item or you can manually choose External as the source type on the sales order line. 1. SMC PTO models cannot be used on drop ship order lines. Implementation Steps: Item Attribute used within Drop Ship order processing Setting Purchased (PO) : Enabled Purchasable (PO) : Enabled Translatable (INV) : Enabled Stock able (INV) : Optional Reserveable (INV) : Enabled 129 . Note that only standard items can be drop shipped. ATO models.Enter and book order. The Create Supply workflow step loads OM information into Oracle Purchasing’s Requisition Import tables. and kits. to indicate shipment to the customer. you may receive an ASN. 6. After Requisition Import completes successfully. Alternatively. a receipt can be entered manually (passive receiving) to record a logical receipt. typically invoicing of the end customer. If the vendor does not send an ASN. kits and models cannot be drop shipped.

Book the sales Order. The Create Supply . 2. Observer that Order Status = Booked Line Status = Booked 3. Run Workflow Background process. Observer that Order Status = Booked Line Status = Awaiting Receipt When an order line with a source type of external is booked.Customer Ordered (OM) : Enabled Customer Orders Enabled (OM) : Enabled Default SO Source type : Optional Shippable (OM) : Enabled Transact able (OM) : Enabled Costing : Enabled (enabled for items that are to be costed) Inventory Asset Value : Enabled (for asset items) (non-expense items) Steps: 1. 130 .Deferred. the seeded workflow “Line Flow – Generic” will process drop shipment lines. Enter Sales Order with Order Line Source Type is set to External.Line subprocess utilizes the function Branch on Source Type which detects an item with a Source Type of External and moves the line to Purchase Release .

Send PO to the Supplier 9. Run AutoInvoice Program. Run Workflow background process 14. Process the Logical Receipts for the PO Oracle Purchasing -> Receipts • Select the Source Type = “Supplier” • Query with the Purchase Order • Select the line and give the stores name and Save the form. The Purchase Release concurrent program processes eligible lines with a source type of External and passes information to Oracle Purchasing. Approve PO 8. Create PO from the approved requisition by submitting the request ‘Autocreate’ 7. The Purchase Release process is initiated to write records to the PO_REQUISITIONS_INTERFACE_ALL table. Marks the line as Shipped and progress the line. Inventory is incremented. Call OM to notify that the Line is fulfilled. Observer that Order Status = Booked Line Status = Shipped 12. OM Decrements Inventory. Order Management Responsibility # Orders. Returns – Sales Order 131 . 13. 5. 6.4. Supplier Ships the goods and sends the Advanced Shipping Notices (ASN) to the Purchasing System 10. Deliver the Goods to Inventory. Logically inventory will updated 11. Submit the Oracle Purchasing Requisition Import concurrent program to create purchase requisitions based on this information in the Interface table PO_REQUISITIONS_INTERFACE_ALL and the requisition is approved.

Drop ship Requisition Number is generated note down the Requisition Number # • • • • • Purchasing – Auto Create Create the Purchase Order through the Auto Create with Requisition Number Query with the Requisition Number Purchase Order click on the Shipment Button (Here we are going to see Ship-To customer and Bill-To ) Approve the Purchase Order by clicking the Approve Button Note down the PO number 132 .• • • • Shipping Tab of Sales Order select the Source Type as “External” Normal Book the SO Order Status: Booked Line Status: Booked Run the Request “Work Flow Back Ground Process ” Order Status: Booked Line Status: Awaiting Receipt From Actions Button select the Additional Line.

This table stores information about the order and line OE_TRANSACTION_TYPES_ALL 133 . which means it will Pick Release and Ship Confirm automatically • Here this generates the Invoice for the sales order • Will then take it past the Inventory update process and close the line out. Logically inventory will updated • # Orders. this table stores the information of Validation Organization for different operating units.Receiving – Receipts • • • # Select the Source Type = “Supplier” Query with the Purchase Order Select the line and give the stores name and Save the form. Returns – Sales Order Query with the SO number and check the status is “Shipped” Run the Request “Work Flow Background Process” • Query the SO and Check the Sales Order status will show “Closed” • Once the SO is Close. < End of Drop Shipment Order Flow  > ONT Tables: Table Name OE_SYSTEM_PARAMETERS_ALL Purpose This table is used for storing all system parameter information. Currently the only system parameter in Order Management being Item Validation Organization.# Inventory – Transactions .

Stores information for all order lines in Oracle Order Management. This table stores customer reported lot serial numbers for lot and / or serial number controlled return lines. sales credits) into Order Management. This table stores the information about. Stores history of attribute changes of Entity Sales Credits. This tables stores information about all the holds that has been released.OE_ORDER_SOURCES OE_ORDER_HEADERS_ALL OE_ORDER_LINES_ALL OE_HOLD_DEFINITIONS OE_HOLD_SOURCES_ALL OE_HOLD_RELEASES OE_ORDER_HOLDS_ALL OE_ORDER_LINES_ALL OE_LOT_SERIAL_NUMBERS OE_DEFAULT_ACTIONS OE_CUSTOM_ACTIONS OE_INVOICE_NUMBERS OE_ORDER_PRICE_ATTRIBS OE_PRICE_ADJ_ATTRIBS OE_PURGE_ORDERS OE_SALES_CREDITS OE_SALES_CREDIT_HISTORY OE_SALES_CREDIT_TYPES transaction types. This is a multi-org table. This table stores pricing attributes and asked for promotions. flag to indicate if the action is displayed as button. order lines. An ABC Class is a category under which items with similar metrics are put together. This table is used for generating invoice numbers based on the delivery name. This table stores information of the hold source criteria. flag to indicate if the action is displayed as default button and the folder object name. This table stores information of all the orders and lines that are on hold and the link to hold sources and hold releases. access key. folder object name. Each row in this table defines an ABC Class. Each row includes the name of the action. This table stores information on qualifiers and pricing attributes. all the actions that are assigned to a folder. which to that corresponding price adjustment line qualified for. The Compile ABC Analysis form allows the user to specify the criterion to be 134 . Stores header information for orders in Order Management Stores information for all order lines in Oracle Order Management This table stores information about hold name and its validity period. deals and coupon number entered by the user. This table stores the information about all the actions that are applicable to the sales order. Each row includes the name of the action. Shipping (WSH) Tables: Inventory Tables (INV): Table Name MTL_ABC_CLASSES Purpose MTL_ABC_CLASSES contains information about ABC Classes. This table stores information about sales credits. prompt name. This tables stores the names of feeder systems from which you import sales order data(order headers. This table stores information about sales credit types. Stores the order details for orders included in a purge set.

Item categories now support multilingual category description. The table is not used if the cycle count is at organization level. compile value. MTL_CROSS_REFERENCES is used to assign crossreferences to items. Oracle Inventory uses this information to provide an ordered sequence of items. Oracle Inventory uses this information in the automatic scheduling feature of cycle counting and for validation purpose when schedule requests are manually entered. MTL_CATEGORY_SETS_B MTL_CC_SERIAL_NUMBERS MTL_CC_SUBINVENTORIES MTL_CATEGORY_SETS_B contains the entity definition for category sets. This table is used to store serial numbers associated to a cycle count entry involving a serialized item. but not more than once in a given group. A category set is a categorization scheme for a group of items. Items are grouped into categories within the context of a category set to provide flexible grouping schemes. based on the compile criteria defined in MTL_ABC_COMPILE_HEADERS. Items may be assigned to different categories in different category sets to represent the different groupings of items used for different purposes. cumulative quantity. MTL_CC_SUBINVENTORIES stores all the subinventories that are to be considered for cycle counting when the scope of the cycle count is at subinventory level. The cross reference type code identifies the cross-referencing identification system being used.MTL_ABC_COMPILES MTL_CATEGORIES_B used for defining such metrics. The item category is a key flexfield with a flex code of MCAT. MTL_CATEGORIES_B is the code combinations table for item categories. This can include references to an old item MTL_CROSS_REFERENCES 135 . Each row also contains an item's compile quantity. MTL_CATEGORIES_TL table holds translated Description for Categories. MTL_ABC_COMPILES stores information about each item within an ABC compile. The flexfield structure identifier is also stored in this table to support the ability to define more than one flexfield structure (multi-flex). Each row includes an item's sequence number relative to other items within the given compile. The cross-reference identifies the specific relationship between the item and the other identification system. MLS is implemented with a pair of tables: MTL_CATEGORIES_B and MTL_CATEGORIES_TL. and cumulative value. A given ABC Class can be used in more than one ABC Group. to which the user can then assign an ABC Class. This table is used only when the user has selected the serial control option "Count: Multiple Per Request" in the corresponding cycle count header.

to supplier item identifications. This ensures that for a given functional area. The category set for a given functional area is uaranteed to have a category assignment for each item defined for use by the functional area. the item inherits the descriptive elements for that group which then behave like additional item attributes. and Address. MTL_DESCRIPTIVE_ELEMENTS stores the descriptive element definitions for an item catalog group. the category set for the Inventory functional area is mandatory (and defaults) for all items defined as Inventory items. . MTL_DEFAULT_CATEGORY_SETS stores the identifier of the category set that acts as the default for a particular functional area. The customer item definition is organization independent. and Reservation Rows.MTL_CROSS_REFERENCE_TYPES MTL_CUSTOMER_ITEMS MTL_DEFAULT_CATEGORY_SETS MTL_DEMAND identification scheme. The table stores the attribute name. Planning and other Manufacturing functions. MTL_ITEM_ATTRIBUTES table stores information on item attributes. An item catalog group consists of items that can be described by the same set of descriptive elements or item properties. there will be a category set that contains all of the items for that functional area. The user can specify values for the descriptive elements and can use that information to search for items MTL_DESCRIPTIVE_ELEMENTS MTL_ITEM_ATTRIBUTES MTL_ITEM_CATALOG_GROUPS_B 136 . etc. When an item is associated with an item catalog group. Each inventory item can be assigned cross-references using any number of cross-reference types. Each record can be defined at one of the following levels: Customer. This can include references to an old item identification scheme. the corresponding user-friendly name seen by the users. Each row in the table corresponds to an attribute. Open Demand Rows. MTL_ITEM_CATALOG_GROUPS_B is the code combinations table for item catalog groups. etc. MTL_CROSS_REFERENCE_TYPES is used to define cross-reference types. The cross reference type provides context information for cross-referencing from an item to some other identification system that is relevant. MTL_CUSTOMER_ITEMS stores customer item information for a specific customer. There are three major row types stored in the table: Summary Demand rows. This information is used to determine the mandatory category sets for an item. It is also used to provide a default category set for forms and reports that require a category set field value or parameter. Each inventory item can be assigned any number of cross-references for any number of crossreference types. Descriptive elements are defining properties used to describe in the catalog group. to supplier item identification. and the kind of validation enforced on the attribute. Address Category. For example. This table stores demand and reservation information used in Available To Promise.

depending on the Multiple Assignments Allowed attribute value in a given category set definition. The presence of an engineering change notice code in this table indicates that the engineering system issued the revision through the implementation process. i. so every item will at least have one starting revision. Along with the engineering change order. MTL_ITEM_STATUS is the definition table for material status codes.. etc. this table stores the item. The associated attributes describe which subinventory this locator belongs to. Oracle Shipping Execution.MTL_ITEM_CATEGORIES MTL_ITEM_LOCATIONS MTL_ITEM_LOC_DEFAULTS MTL_ITEM_REVISIONS_B using the Item Search window. The values of the individual status attributes associated with an item status are stored in MTL_STATUS_ATTRIBUTE_VALUES. Obsolete. and Oracle Purchasing respectively. what the locator physical capacity is. MTL_ITEM_LOC_DEFAULTS contains the optional default locators for shipping and receiving purposes. an implementation date and initiation date will be stored.e. It indicates the status of an item. the category set. and the category. The status optionally controls several 'function controlling' item attributes (status attributes) and can be used to disable the item from being used by the various application products. The locator is a key flexfield. MTL_ITEM_LOCATIONS is the definition table for stock locators. Pending. For each category assignment. Items always may be assigned to multiple category sets. MTL_ITEM_REVISIONS stores revision levels for an inventory item. DEFAULT_TYPE indicates whether the subinventory is meant for default shipping or receiving. The Flexfield Code is MTLL. Status code is a required item attribute. MTL_ITEM_CATEGORIES stores inventory item assignments to categories within a category set. Also see MTL_ITEM_SUB_DEFAULTS. Active. MTL_ITEM_STATUS MTL_ITEM_SUB_DEFAULTS MTL_ITEM_SUB_INVENTORIES 137 . However. The LOCATOR_ID and SUBINVENTORY_CODE identify the exact locator/subinventory which one wishes to have as default. When an item is defined a starting revision record is written out to this table. MTL_ITEM_SUB_INVENTORIES maintains a listing of subinventories assigned to an inventory or engineering item. MTL_ITEM_SUB_DEFAULTS contains the list of optional default shipping and receiving subinventories for items in an organization. This information is used by Oracle Order Management.. an item can be assigned to either many or only one category in that category set. The DEFAULT_TYPE indicates whether it is the default shipping or receiving subinventory/locator.

When the transaction lines are transacted. and the request number of the move order. This table stores all of the move order headers. The defined status can be assigned to Subinventory. When you apply a template to an item. MTL_ITEM_TEMPLATES MTL_ITEM_TEMPLATES is the definition table for item templates. the enabled item attributes are propagated to the item. and INVENTORY_ITEM_ID. the move order type. MTL_PARAMETERS maintains a set of default options MTL_ITEM_TEMPL_ATTRIBUTES MTL_LOT_NUMBERS MTL_MATERIAL_STATUSES_B MTL_MATERIAL_TRANSACTIONS MTL_TXN_REQUEST_HEADERS MTL_TXN_REQUEST_LINES MTL_ONHAND_QUANTITIES MTL_PARAMETERS 138 . Each move order line must be tied to a specific move order header. a lot number could exist in more than one organization or for different items. the enabled attribute values are propagated to the item. The lines are requests to move some quantity of an item from a source location to a destination location or account. the move order status. You can use a template to set certain item attributes. the quantity delivered is updated. When a line is detailed or pick released. Since the primary key consists of LOT_NUMBER. It contains all the attributes which are not translated and don't vary by language. locator.These subinventories make up the list of valid subinventories when transacting this specific item and the user has specified (in the master window) that the item must use subinventories restricted to a pre-defined list. The table MTL_TXN_REQUEST_LINES stores all of the move order lines. When a template is created. a row is inserted for each available item attribute. MTL_LOT_NUMBERS stores the definition and expiration date of all lot numbers in inventory. The user can then specify values for and enable each template attribute for later use. You may apply several different templates to an item to achieve a layering of attributes. lot and serial to restrict certain transaction types. MTL_MATERIAL_STATUSES_B is the base table for the inventory statuses. MTL_MATERIAL_TRANSACTIONS stores a record of every material transaction or cost update performed in Inventory. It contains the user-defined name (TEMPLATE_NAME) and description (DESCRIPTION). MTL_ITEM_TEMPL_ATTRIBUTES stores the attributes and attribute values for item templates. The headers contain all information which pertains to entire move orders. including the transaction type of the move order. ORGANIZATION_ID. When the template is applied to an item. the quantity detailed is updated appropriately and transaction lines are created in MTL_MATERIAL_TRANSACTIONS_TEMP.

One row per subinventory per physical inventory. inter-organization options. availability type. raw material. demand picking order..e. indicating a list of valid places where this item will physically exist in inventory. finished goods. locator type.MTL_PHYSICAL_INVENTORIES MTL_PHYSICAL_SUBINVENTORIES MTL_RESERVATIONS MTL_SALES_ORDERS MTL_SECONDARY_INVENTORIES like general ledger accounts. including the approvals required. etc. supply source header. This table stores reservation information. indicating a list of valid places where this item will physically exist in inventory. You can also specify whether this subinventory is an expense or asset subinventory (ASSET_INVENTORY). locator. locator). for each organization defined in Oracle Inventory. MTL_SECONDARY_LOCATORS MTL_SERIAL_NUMBERS 139 . Supply source information comprises supply source type (Inventory. A subinventory is a section of inventory. Account. locator type. MTL_PHYSICAL_INVENTORIES contains certain userdefined options for a physical inventory. subinventory scope (all or a subset specified in MTL_PHYSICAL_SUBINVENTORIES). MTL_SECONDARY_INVENTORIES is the definition table for the subinventory. subinventory.. Other attributes include general ledger accounts. demand source line and demand source name. Each record is a reservation that ties an item/organization combination with a demand source and a supply source. tolerances. availability type. Inventory). These serial numbers are also used in other areas of Oracle Manufacturing. MTL_SERIAL_NUMBERS stores the definition and current status of all serial numbers in Oracle Inventory. etc. demand source header. etc. raw material. MTL_SALES_ORDERS stores Inventory's local definition of sales orders. or whether quantities are tracked (QUANTITY_TRACKED). demand picking order. and reservable type. Account Alias. finished goods. Other attributes include general ledger accounts. supply source line. supply source name and inventory controls (revision. and whether tags may be created in the Physical Inventory Counts window or whether they must be pre-generated. Subinventories are assigned to items (in a many to one relationship). costing method. lot. lot. A subinventory is a section of inventory. MTL_SECONDARY_INVENTORIES is the definition table for the subinventory. and serial controls. Subinventories are assigned to items (in a many to one relationship). WIP jobs). MTL_PHYSICAL_SUBINVENTORIES specifies which subinventories are involved in a physical inventory when the physical inventory does not include all subinventories. i. and reservable type. i. Demand source information comprises demand source type (Sales Order.e.

You can specify item-related information in fields such as: Bill of Material.Resides in stores . WSH_PICKING_RULES has picking rules for defaulting Pick Release options. Work in Process. This table stores the list of all the partner ITM Applications. WSH_FREIGHT_COSTS records freight costs. The flexfield code is MSTK. Order Management. WSH_DELIVERY_LEG_DETAILS stores pick-up/drop-off information for each delivery line of a delivery leg. Shipping Tables: Table Name WSH_CARRIERS Purpose ***** Warning: Oracle Internal Use Only ***** Oracle Corporation does not support access to Oracle applications data using this object. This table holds the definitions for inventory items. WSH_TRIPS has trip records.Issued out of stores . Use the standard 'System Items' flexfield that is shipped with the product to configure your item flexfield. engineering items. WSH_NEW_DELIVERIES has the delivery records. Inventory. except from standard Oracle Applications programs. The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. since it is implemented as a flexfield. MPS/MRP Planning. WSH_TRIP_STOPS has trip stop records. WSH_DELIVERY_LEGS maps deliveries to their pick up and drop off stops. WSH_DELIVERY_LEG_ACTIVITIES stores activity history for a given shipment (delivery). the same item can be defined in more than one organization. Therefore. Purchasing. WSH_PICK_GROUPING_RULES has grouping rules for Pick Release. ***** Warning: Oracle Internal Use Only ***** Oracle Corporation does not support access to Oracle applications data using this object. You can set up the item with multiple segments. Lead times.MTL_SYSTEM_ITEMS_B A serial number can have one of four statuses: . General Planning. WSH_NEW_DELIVERIES WSH_DELIVERY_ASSIGNMENTS WSH_DELIVERY_DETAILS WSH_DELIVERY_LEGS WSH_DELIVERY_LEG_ACTIVITIES WSH_DELIVERY_LEG_DETAILS WSH_TRIPS WSH_TRIP_STOPS WSH_FREIGHT_COSTS WSH_LOCATIONS WSH_ITM_VENDORS WSH_PICKING_RULES WSH_PICK_GROUPING_RULES 140 . and purchasing items. except from standard Oracle Applications programs. Receiving. WSH_DELIVERY_ASSIGNMENTS assigns delivery details to a delivery and/or a parent delivery detail (LPN). Costing.Resides in intransit MTL_SYSTEM_ITEMS_B is the definition table for items. Physical attributes.Defined but not used . WSH_DELIVERY_DETAILS has delivery lines and LPNs. and Invoicing.

and "Take the Ralston Avenue exit from highway 101. POST_OFFICE. postal code. The HZ_LOCATIONS table stores information about a delivery or postal address such as building number. Jane Doe {{"bul:1"}}Group-for example. The primary key for this table is CUST_ACCT_SITE_ID. Oracle Corporation {{"bul:1"}}Person-for example. A profile class defined in the HZ_CUSTOMER_PROFILE_CLASSES table can be used to provide default values for the attributes in this table. The parties can be one of four types: {{"bul:1"}}Organization-for example. The primary key for this table is CUST_ACCOUNT_PROFILE_ID The HZ_CUST_ACCT_SITES_ALL_M table stores information.Oracle Receivables Tables: Table Name HZ_CUST_ACCOUNTS HZ_CUSTOMER_PROFILES Purpose The HZ_CUSTOMER_PROFILES table stores information about the credit characteristics of a single customer account or a customer account site or a party. Data in the HZ_LOCATIONS table is also used to determine the appropriate tax authority and tax rates for sales tax and VAT calculations. from the HZ_CUST_ACCT_SITES_ALL table. For example. The HZ_CUST_SITE_USES_ALL_M table stores information. street address. and directions to a location. HZ_CUST_ACCT_SITES_ALL HZ_CUST_SITE_USES_ALL HZ_LOCATIONS HZ_PARTIES 141 . The HZ_PARTIES table stores basic information about parties that can be shared with any relationship that the party might establish with another party. turn left on Oracle Parkway. This table provides physical location information about parties (organizations and people) and customer accounts. about the uses of customer sites before an account merge occurs. you can store information such as Building 300. The default values copied into this table can be modified to more closely match the customer account defined in this table. 500 Oracle Parkway. about customer account sites before an account merge occurs." . multiple parties can have the same name. 94065. Although a record in the HZ_PARTIES table represents a unique party. The primary key for this table is CUST_SITE_USE_ID. and TIME_ZONE columns. go east on Twin Dolphins Drive. Jane Doe at Oracle Corporation. World Wide Web Consortium {{"bul:1"}}Relationship-for example. watch for the Building 300 sign on your right. Records in the HZ_LOCATIONS table can store delivery and postal information about a location through columns such as the LOCATION_DIRECTIONS. from the HZ_CUST_SITE_USES_ALL table. You can also use the HZ_LOCATIONS table to store latitude and longitude information.

people. and groups Customer account information Links party to physical locations HZ_CUST_SITE_USES HZ_LOCATIONS Physical addresses Columns PARTY_ID PARTY_NUMBER PARTY_NAME CUST_ACCOUNT_ID PARTY_ID ACCOUNT_NUMBER CUST_ACCT_SITE_ID CUST_ACCOUNT_ID PARTY_SITE_ID PARTY_SITE_ID PARTY_ID LOCATION_ID PARTY_SITE_NUMBER SITE_USE_ID CUST_ACCT_SITE_ID SITE_USE_CODE LOCATION LOCATION_ID 142 . HZ_ORGANIZATION_PROFILES. The HZ_PARTY_SITES table links a party (see HZ_PARTIES) and a location (see HZ_LOCATIONS) and stores location-specific party information such as MAILSTOP and ADDRESSEE. One party can optionally have one or more party sites. 500 Oracle Parkway can be specified as a party site for Oracle Corporation. The identifying address contained in the HZ_PARTIES table is demoralized from the HZ_LOCATIONS table. and HZ_PERSON_LANGUAGE tables. HZ_PERSON_PROFILES. Description Information about parties such as organizations. Party sites can have multiple uses.HZ_PARTY_SITES HZ_PARTY_SITE_USES RA_CUSTOMERS RA_BATCHES_ALL RA_CUSTOMER_TRX_ALL RA_CUSTOMER_TRX_LINES_ALL RA_LINE_ORDERING_RULES RA_SITE_USES_ALL RA_TERMS_B RA_TERMS_LINES RA_TERMS_LINES_DISCOUNTS RA_TERRITORIES RA_ADDRESSES RA_BATCHES RA_GROUPING_RULES Table Name HZ_PARTIES HZ_CUST_ACCOUNTS HZ_CUST_ACCT_SITES HZ_PARTY_SITES {{"bodytext"}}Party records can be created and updated using third party data sources such as Dun & Bradstreet's Global Data Products. The HZ_PARTY_SITE_USES table stores information about how a party site is used. HZ_CONTACT_POINTS. This party site can then be used for multiple customer accounts within the same party. for example Ship-To and Bill-To. The HZ_PARTIES table contains demoralized information from the HZ_LOCATIONS. One location can optionally be used by one or more parties. For example.

and on-account credits in Oracle Public Sector Receivables. Receivables rejects transactions with invalid information to ensure the integrity of your data. credit memos. flexible tool you can use to import and validate transaction data from other financial systems and create invoices. You use a custom feeder program to transfers transaction data from an external system into the AutoInvoice interface tables. you can:  Import large numbers of transactions for seamless integration from Oracle or non-Oracle systems o Invoices o Debit memos o Credit memos o On-account credits  Calculate taxes for the imported transactions.COUNTRY ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 CITY POSTAL_CODE STATE PROVINCE COUNTY POST_OFFICE Inventory Key Flex Fields: Key Flex Field Item Categories Item Catalogs Sales Orders Stock Locators System Items Short code MCAT MICG MKTS MTLL MSTK CC Table MTL_CATEGORIES_B MTL_ITEM_CATALOG_GROUPS_B MTL_SALES_ORDERS MTL_ITEM_LOCATIONS MTL_SYSTEM_ITEMS_B CC Table AR_LOCATION_COMBINATIONS RA_TERRITORIES CC Table GL_CODE_COMBINATIONS GL_CODE_COMBINATIONS Oracle Receivables . or pass the tax through the tables  Correct errors easily online Create invoices from the following Oracle applications: – Oracle Order Management 143 .Key Flex Fields: Key Flex Field Short code Accounting Flexfield GL# Reporting GLAT Attributes:Accountin AutoInvoice Overview AutoInvoice is a powerful. AutoInvoice then selects data from the interface tables and creates transaction in Receivables.Key Flex Fields: Key Flex Field Short code Sales Tax Location RLOC Flexfield Territory Flexfield CT# Oracle General Ledger. With AutoInvoice. debit memos.

 Receivables automatically applies these required grouping rules to any additional transaction attributes assigned to the grouping rules.– – – Oracle Projects Oracle Service Oracle Property Manager Create invoices from the following non-Oracle applications: – Legacy system (for transaction history) – Non-Oracle billing applications – Non-Oracle order entry applications Grouping Rules  Grouping rules are mandatory and determine how transaction lines are grouped into transactions  Grouping rules specify attributes that must be identical for lines to appear on the same transaction. Grouping Rule Hierarchy AutoInvoice uses the following hierarchy to determine which grouping rule to use for a transaction line:  The grouping rule specified in the Transaction Sources window for the batch source of the transaction line  The grouping rule specified in the Customer Profile Classes window for the bill-to site use of the transaction line 144 .  AutoInvoice requires mandatory grouping on the transaction attributes Currency Code and Bill-To Customer (only one of each attribute is allowed per invoice).  All attributes of the Transaction Flexfield are optional within a grouping rule and can be assigned as optional grouping characteristics in the Grouping Rules window.

BOOKED or CLOSED.BOOKED_FLAG=N or NULL) then the result after import is that the line is BOOK_ORDER eligible. tax.  The Line_Type field identifies the type of information contained in the record.  A child record is linked to the parent record using the Link-To Transaction flexfield. Oracle Receivables uses three interface tables for AutoInvoice:  RA_INTERFACE_LINES  RA_INTERFACE_DISTRIBUTIONS  RA_INTERFACE_SALESCREDITS RA_INTERFACE_LINES Table  This table contains information relating to all transactions to be processed by AutoInvoice. Order Import in Oracle Order Management: Status of Orders Orders can be imported as ENTERED. debit memos.  Records in this table are linked to records in the RA_INTERFACE_LINES table using the Transaction flexfield. 145 . debit memos.  The two tables are linked using the Transaction flexfield. Any accounts that are not passed will be derived using AutoAccounting. Header Freight.  Accounts defined in this table override any accounts created using AutoAccounting.  Not required if AutoAccounting determines GL distributions. and on-account credits.  A record can be a parent record: Line. freight. AutoInvoice uses the default grouping rule specified in the System Options window AutoInvoice Line Ordering Rules  AutoInvoice uses these rules to order transaction lines when grouping the transactions it creates into invoices. Transactions include invoices.  AutoInvoice uses transaction attributes in the line ordering rules to order invoice lines based on the priority defined. RA_INTERFACE_DISTRIBUTIONS Table  This table contains accounting distributions to be used by the transactions defined in RA_INTERFACE_LINES. and credit memos. or Charges. or finance charges information. ENTERED: If an order is imported with an entry status of ENTERED (OE_HEADERS_IFACE_ALL. credit memos.  An ascending or descending order for each transaction attribute assigned to a rule can also be specified.  Line ordering rules can be assigned to each grouping rule.  The grouping rule specified in the Customer Profile Classes window for the bill-to customer of the transaction line If no rule is specified in either the Transaction Sources or Customer Profile Classes window.  Choose to pass some or all account information to AutoInvoice.  Not required if not tracking sales credit. RA_INTERFACE_SALESCREDITS Table  This table contains all sales credit information for the transactions in the RA_INTERFACE_LINES table. or a child record: Tax or line-level Freight.  Each record contains line.

a warning will be given. When the unavailable quantity is in cycle count. If the both the order and the line cancelled_flag is set to 'Y' then in such cases the program cancels the header along with the lines because the header cancelled_flag is 'Y'. So depending on whether the order or the line is to be cancelled. If it is greater than the over shipment tolerance. but you won’t be able to pass the information to OM. in the OE_HEADERS_IFACE_ALL do not pass the BOOK_FLAG and in the OE_ACTIONS_IFACE_ALL table put operation code as BOOK_ORDER. The Under-Shipment tolerance behaves differently. The remaining quantity will automatically cancel. there will not be any changes performed to the records. any quantity less than the requested amount is allowable. then the lines information should not be loaded into the interface table and the header interface table should have the cancelled_flag set to 'Y' and the CHANGE_REASON as a valid lookup code from CANCEL_CODE lookup type.BOOKED: Order can be imported in booked condition using one of the following methods:  By populating the column BOOK_FLAG of the table OE_HEADERS_IFACE_ALL as ‘Y’. This functionality requires adding the security privilege Cycle Count Delivery Line. All the book required columns need to be passed for importing a Closed Order. if the user notices a discrepancy between physical inventory and system inventory. Cancellation of Order using Order Import If the entire order is to be cancelled. Importing Closed Orders using Order Import Closed Orders are treated differently from open orders 1. then the missing quantity may be transferred to cycle count within the Shipping Transactions form using the Actions button. Then since the line cancelled_flag is also 'Y' it tries to cancel the already cancelled line and errors out. Over/Under Shipments A quantity greater than the quantity on the line is allowed if it is within the over-shipment tolerance. The actual quantity shipped is recorded on the line. If only the line is to be cancelled. the cancelled flag and the header information or the line information should to be loaded. There is a difference between closing an existing order and importing orders in "CLOSED" status the first time itself. Also the operation code to be used for cancellation should be ‘UPDATE’ . which means no defaulting. Once you have run the OM interface.e. Transfer of Reservations to Cycle Count: During pick release. i.  By passing the action request to the OE_ACTIONS_IFACE_ALL table. as it goes through the booking cycle where validation for all the booking required columns are done. but the user will not be stopped from shipping the additional quantity. then both the lines and the header tables should be populated in the interface table but should set the cancelled_flag to 'Y' only for the lines with the qty updated to zero. 4. Notes: Freight costs can be modified after Ship Confirm. you can no longer pass modified freight cost information back to OM. it is not available for pick release and the inventory control staff can correct the discrepancy during the next cycle count of the discrepant item. You can still modify freight costs. the modified costs will only be included on the customer invoice if OM Interface has not yet run (previously called Update Shipping). 3. 146 . To Import Closed Orders oe_headers_iface_all table should have the closed_flag as "Y" and the operation_code as ‘INSERT’ 2. the line will close once the shipment is processed. If the quantity shipped is within the under-shipment tolerance. At ship confirm. However. As orders were already closed in the old system.

instead of picking exactly 5 cans. For example. the other line becomes a backordered line with the difference. and the warehouse either is out of individual cans or has a policy against loose cans. o It allows the user to prevent breaking LPNs or lots by small amounts when the quantity requested does not match the quantity in inventory. the warehouse has only six-packs. if the customer orders five cans. The over picking functionality allows the picker to pick a 6-pack (6 cans wrapped) to fulfill the order. which is a natural extension to the over shipping feature. the line will split into 2 lines. one line represents the quantity shipped.However. Inventory Flexfield: 147 . if the quantity shipped is outside the tolerance. Over Picking The over picking enhancement supports the following: o It allows the Pick Confirm transaction to pick in excess of the requested quantity as long as it is within the over shipment tolerance.

Sign up to vote on this title
UsefulNot useful