Inventory And Order Management 244f2a

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

3

_id =>0, security_group_id =>0); How to set Client Info in Reports? Before Report: DBMS_APPLICATION_INFO.SET_CLIENT_INFO ('org_id'); Ex: DBMS_APPLICATION_INFO.SET_CLIENT_INFO (103);

How to 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_S_NO_VALIDATION select sb.set_of_books_id from gl_sets_of_books sb, ar_system_parameters sp where 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.start_date , gls.end_date FROM gl_period_statuses gls WHERE gls.set_of_books_id = <set_of_books_id> AND gls.application_id = 222 AND sysdate BETWEEN gls.start_date AND gls.end_date; Inventory Flexfield:

Only One Structure ed Inventory Flexfields

4

Alias Item Catalogs Sales Order Stock Locators Sales Order Your Sales Order Flexfield should be defined as Order Number, Order Type, and Order Source. This combination guarantees each transaction to Inventory is unique. You must define this flexfield before placing demand or making reservations in Oracle Order Management. 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’.) 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. s 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. Aliases An alias is a logical reference to a frequently used number combination. It is also a transaction source type of its own, thereby allowing you to query and report transactions using your –friendly references to particular numbers. Logical reference to ing code combinations:

5

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

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. Both status attributes and item status can be controlled at the item level or organization levels. Item Statuses are:  BOM Allowed  Build in WIP  Customer Orders Enabled  Internal Orders Enabled  Invoice Enabled  Transactable  Purchasable  Stackable

Item Attributes

7

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

8

 An inventory organization can share one or more of these characteristics with other organizations.

 An inventory organization is an inventory location with its own set of books, costing method, workday calendar and list of items. An organization can be a company, subsidiary, or warehouse. 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.  Costing Methods: You set your costing method (Standard or Average) at the organizational level. The item attribute control level determines the costing organization.  Item Costs: Oracle Inventory keeps one cost per item per inventory organization.  Movement between Inventory Sites: You can use in-transit inventory for interorganization transfers.  Planning Method: You can choose how to plan your items.  Forecasting: You can forecast your items.  Accuracy Analysis: You can perform a cycle count, or a physical inventory Item validation organization  Item validation organization is a logical entity listing all the items that an enterprise sells to customers. Multiple item validation organizations can be listed that share the same item master organization.  A minimum of one item validation organizations is required per set of books.  A maximum of one item validation organization per operating unit is allowed to determine the items that may be sold in each operating unit. Item Master Organization Item Master Organization is usually the first Inventory organization that is set up. Its single purpose is for entering items. It has no sub inventories and is not used for inventory transactions. Items are entered in an item master organization and then assigned to be used in child organizations. Child Organization Child Organization is an inventory organization with at least one subinventory that is set up for processing inventory transactions. It is not used to enter items. It gets a list of items from the master. What is Item Master organization and Child Organization?  Item Master Organization is usually the first Inventory organization that is set up. Its single purpose is for entering items. It has no sub inventories and is not used for inventory transactions. Items are entered in an item master organization and then assigned to use in child organizations.

 Child Organization is an inventory organization with at least one sub inventory that is set up for processing inventory transactions. It is not used to enter items. It gets a list of items from the master. What is the purpose of Organization Assignment? After defining an Item in the Item master, it has to be assignment to the Organization and is known as Organization Assignment. The purpose of the Organization Assignment is to make the item available for Transactions in particular Organizations.

9

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. Inventory propagates item to all organizations in which the item is to be defined. Organizational attributes for item attributes which are enabled in that organization, can be entered or changed which are enabled in that organization. For example, go to an organization to choose reorder point planning for an item, and then go to another organization and choose Min-Max planning for the same item. Deletion Constraints and Deletion Groups  If you want to enforce specific business rules and add custom checks before you can delete an item, you must define item deletion constraints to supplement the standard predefined item deletion conditions.  You can delete items that have incorrect attribute information. For example, if you make a mistake in entering an item number, use the Deletion Groups window to delete the item.  If you decide to purge the item immediately after incorrectly defining it and before using it anywhere in the system, you will be able to delete it. Subinventory  A sub inventory is a Subdivision of an organization, representing either a physical area or a logical grouping of items, such as a storeroom or receiving dock   

A subinventory is a physical or logical grouping of inventory, such as raw material, finished goods, defective material, or a freezer compartment. The subinventory is the primary place where items are physically stocked. A subinventory must be specified for every inventory transaction Sub inventories can be further divided into areas designated as locators.

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  information Inventory Controls Any combination of the four controls can be implemented for each item. Inventory controls are optional for all items  Locator  Revision  Lot  Serial Number Stock Locator / Locator Control  Locators are optional structures within sub inventories.  Locators are the third level in the enterprise structuring scheme of Oracle Inventory.  Locators may represent rows, aisles, or bins in warehouses. Items can be received directly into and shipped items directly from locators.  You can structure your Oracle Inventory installation so some of the subinventories and items have locator control while others do not. If locator control is turned on at the item

10

level, you must specify a locator when transacting the item into or out of a subinventory. If locator control is turned on at the subinventory level, you must specify a locator when transacting any item into or out of that subinventory. Each stock locator you define must belong to a subinventory, and each subinventory can have multiple stock locators. 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 the stock locator has a zero on-hand quantity, then the locator is not included in the report. Locator Listing Report You use the Locator Listing Report to list stock locators you defined. You also use this report to review volume and weight allowed in a location before transacting items. Revision Control  A revision is a particular version of an item, bill of material, or routing.  By using the ‘Revision control’ option while defining items item quantities can be tracked by item revision. To do so a revision is a must for each material transaction.  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 item attributes cannot be changed when an item has quantity on hand.  When defining Revision numbers letters, numbers and characters such as A, A1, 2B, etc can be used.  Letters are always in upper case and numbers may include decimals.  To ensure that revisions sort properly, decimals should always be followed by a number.  Revisions are sorted according to ASCII rules.  Each revision must be greater than the previous revision. For example, revision 10 cannot be used after revision 9 because, according to ASCII sorting, 10 precede 9.  The value entered in the Starting Revision field in the Organization Parameters window displays as the starting revision for the item when asg revisions to an item.

Lot Control  Inventory provides complete lot number for inventory transactions.  A lot identifies a specific batch of an item that is received and stored in an organization.

11



     

Lot control is a technique for enforcing the use of lot numbers during material transactions, thus enabling the tracking of batches of items throughout their movement in and out of inventory. If Lot Control is turned on for an item, the lot number must be indicated to perform a transaction. Lot Control must be turned on at the item level. Lot numbers must be assigned whenever items under lot control are received into inventory. An inventory receipt can be split in to several lots, as necessary. Quantities can be added to existing lot numbers. Inventory will generate default lot numbers by using the default lot number generation method which is configured in the Organization Parameters window during setup.

Explaining Lot Control Reports Lot Transactions You can use the Lot Transactions to report comprehensive lot number material transaction detail within a specific date range. You can run the report for a range of lots, items, transactions types, transaction reasons, and subinventories. You can also specify a specific category set and display transaction quantities in their primary or transacted unit of measure. Supplier Lot Trace Report You can use the Supplier Lot Trace Report to trace a specific lot to its supplier lots. 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, lot numbers, transaction dates, and transaction quantities. 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. You can run the report for a range of items or for a specific item only.

12

Serial Control  A serial number is an alphanumeric piece of information assigned to an individual unit of an item. A serialized unit is a combination of an item number and a serial number.  Individual units of items can be tracked by using serial numbers. Serial number control is a system technique for enforcing the use of serial numbers during a material transaction. Serial numbers can be used to track items over which a very tight control is to be maintained.  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 No Control is specified as the serial number control type, no serial number control will be enforced.  If Predefined is specified as the serial number control type, serial numbers for that item must be predefined.  If control ‘At inventory receipt’ or ‘At sales order issue’, optionally serial numbers for the item can be predefined. Generating Serial Numbers  Inventory uses the starting serial number prefix and the starting serial number specified in the Item screen.  The process of generating serial numbers is done through a concurrent report. This does not assign numbers to units in inventory; it simply reserves serial numbers for an item, for later use. Serial Genealogy

13

   

Enables to view the composition and transaction history of a serial-controlled item through a graphical interface. Includes all material transactions within an organization. Enables to trace serial numbers from an assembly to all components. Enables to trace serial numbers from a component to a final assembly.

Explaining Serial Number Control Reports Serial Number Transactions You can use the Serial Number Transactions to report comprehensive serial number material transaction detail within a specific date range. You can run the report for a range of serial numbers, items, transaction types, transaction reasons, and subinventories. You can also specify a specific category set and display transaction quantities in their primary or transacted unit of measure. 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. Oracle Inventory enables you to run the report for a range of serial numbers, items, suppliers, and supplier serial numbers. Item Templates  Templates are defined sets of attributes that can be used over and over to create many similar items. Templates make initial item definition easier and more consistent.  Templates can be applied at any time after the item is created. Multiple templates can be applied to a single item.  Templates can hold a complete set of attributes or a partial set. If a partial set, then only values stored in the template overwrite those on the item  s 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. Substitute items can be received in Oracle Purchasing.

14

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

15

Receiving Inventory There are different ways you can receive inventory in to stock. Purchasing You can receive inventory from outside of your organization using purchasing. 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  Receipt from Project  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. Shipping Shipping can generate a transfer to move stock from a finished goods area to a staging to for shipping. Order Management Order management can generate a transfer to move stock from a finished goods area to a staging area for shipping. Work in Process Work in Process can generate a transfer to acquire components for a project. Inventory Inventory transfers materials using the following methods: • Transfer between Organizations • Replenish materials • Request transfers

16

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: • Defined • Inter Organization Transfer • Cycle Count Negative • Request Issue Item Profile Options

Transaction Types:  Receive items into your organization using a general ledger number  Issue items from your organization using general ledger 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



Reserve items for a specific 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. 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. Oracle Inventory also uses transaction types to identify certain transactions to include in historical usage calculations for ABC analysis or forecasting. A number of transaction types are predefined in Oracle Inventory. The can also define additional types by setting up new combinations of source types and actions.

Transaction Source Type You use a transaction source type with a transaction action; it uniquely identifies the type of transaction performed. Oracle Inventory provides the following predefined transaction source types. You can define additional source types. Predefined transaction types are as follows: • Purchase Order • 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 transaction action identifies a transaction type. 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

• • • • • • •

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, processing intervals and the number of transactions processed by each worker during each interval. 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. Remote Procedure Manager Remote procedure manager processes online inventory transactions WIP initiates, such as completions or component issue. 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. You do not have to launch the other transaction managers if you decide to process your transactions on-line, and do not use the transaction interface. What are the Types of Inventory Transactions?

19

Miscellaneous Transactions This transaction is used to do adjustments in stock due to damage, obsolescence, issuing items for R & D or issuing track able expense items. 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, or between two locators within the same subinventory We can transfer from asset to expense subinventories, as well as from tracked to non–tracked subinventories. If an item has a restricted list of subinventories, we can only transfer material from and to subinventories in that list. Inter ORG Transfers This transaction is used to transfer goods from one inventory organization to another. Interorganization Direct Shipment You use the Interorganization Transfer window to move inventory directly from a shipping organization to a destination organization.

20

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

21

Transfer type: Direct: Inter-organization transfers move inventory directly from the shipping organization to the destination organization. Intransit: Inter-organization transfers move inventory to intransit inventory first. You can track this inventory until it arrives at the destination organization. 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. 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. 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 number  Issue items from your organization to a general ledger 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 or temporarily prevent the release of items onto the shop floor What is Move Order?

22

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

23

The requisition is a manually generated request for a move order. You must create a move order requisition. You can generate requests for subinventory transfers or move order issues. The requisition can optionally go through an Oracle Workflow approval process before it becomes a move order. If no approval process is used, the requisition becomes a move order immediately. Replenishment Move Order These move orders are generated by kanban cards where the pull sequence calls for a subinventory transfer (intra-organization kanbans), or by min-max planned items where the item’s replenishment source (set at the item-sub inventory level) is another sub inventory. In this case, the min-max or replenishment count report automatically generates a move order. Replenishment move orders are pre-approved and ready to be transacted. 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, which you define as a subinventory in Oracle Inventory. This transaction is a subinventory transfer. These move orders are generated automatically by the Oracle Shipping Execution pick release process. These orders are pre-approved and ready to transact. Pick slips and other shipping and inventory reports will also be available with Oracle Order Management. 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. The line details are the inventory transactions that must be fulfilled to complete the move order line. You can consider the allocating process as a sourcing process. Allocating occurs when you click the Allocate button in the move order transaction window. Suggesting Sources Oracle Inventory uses the picking rules you set up at the organization or organization-item level, to suggest source locators, revisions, and lots to source the material in order to fulfill a move order line. Suggesting a Destination The picking rules only suggest source locations. If the destination subinventory is locator-controlled and no locator was specified on the move order line, Oracle Inventory generates a suggestion based on the item subinventory locator default you set up for move orders. Before release 11i, the item subinventory defaults were used only for put away locations in the receiving process. You can now set up a default locator for each item that you want to move around the warehouse on a move order. This is not the same default type that you would use for receiving or shipping. Oracle Shipping Oracle Shipping provides two choices for when and how the will fill in the line details. These choices are made by setting up an organization parameter but can be overridden at pick release.

 Auto allocate --the allocating process is done at pick release instantly after the move order is created. No more human intervention is needed and the pick slip can be printed automatically. 

Pick release only creates move orders but does not fill in the line details. A must navigate to the move order form after pick release and press the Allocate button. 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. In these cases orders can be released to

24

regional warehouses from the central order management location in advance and individual warehouses can schedule picks closer to actual ship time.

What is Transact Order? Once the lines have been allocated, 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. You can save and exit the move order line details without transacting if you need to print a pick slip report. This enables you to transact each detail line before or after picking the material. If the transacts less than the requested quantity, the order remains open until the full quantity is transacted or the order is closed or canceled. What does the Auto Detail option do? Pick Release always creates a Move Order transaction. When you check this option in the Pick Release parameters, the Pick Engine creates transaction lines suggestions. This is a suggestion of sourcing material and it is called "Detailing". The Detailing also creates a high level reservation on the material if no reservations previously existed. The Detailing can be made manually. 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. It can be activated only if you select the Autodetail option.

Order Management: Introduction Using the Oracle Order Management (OM) Suite, you can enter sales orders, calculate the price of items on order lines, fulfill the orders, for example by shipping the items, and send information to s receivable system so that invoices are created. The core OM products are  Oracle Order Management  Oracle Shipping Execution (SE)  Oracle Pricing These products are included when Oracle Order Management is purchased. Additional products are available which are also integrated with Oracle Order Management, and these include  Oracle Advanced Pricing  Oracle Configurator  Oracle s Receivable  Oracle Advanced Planning and Scheduling How to debug the OM Applications Data? Run $ONT_TOP/sql/omse11i.sql by providing the Order Number, Header Id and Line Id. How do you create Category from backend? Using the procedure INV_ITEM_CATEGORY_PUB.CREATE_CATEGORY

25

How are the quantities calculated in the autoschedule availability window? When you turn on Autoscheduling in the Sales Order form, an availability window is displayed which shows the following fields: Warehouse, Available, On Hand, Reservable, Request Date, Available Date, and Error Message. 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, 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? Profile Option OM: Source Code value should match with DFF: Line Transaction Flexfield context.

26

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

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

BEGIN 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, 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 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

the order quantity modifier item attributes (Minimum Order Quantity, Maximum Order Quantity, and Fixed Lot Size Multiplier) to further control the suggested order quantities generated by min–max planning. Set the Make or Buy flag to Make to optionally generate unreleased jobs and to Buy to optionally generate requisitions. For buy items, set the List Price for the item to automatically generate requisitions.

For repetitive items, since you cannot generate repetitive plans, you have the option of generating requisitions, unplanned jobs, or a report only. Min–max planning is performed by running the Min–Max Planning report. By selecting organization level planning, you run min–max planning for your organization. In addition to the planning level option, Oracle Inventory offers the options to Net Reserved Orders, Net Unreserved Orders, Net WIP Demand, and Include Non–nettable Inventory Quantities when calculating availability. You also specify a Demand Cutoff Date and a Supply Cutoff Date. If you choose No to all the net demand options, Oracle Inventory performs the following calculation: • Nettable Quantity on Hand + On Order = Total Available, 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. o On Order is the sum of open purchase orders, purchase requisitions, internal requisitions, internal orders, and work in process jobs scheduled for receipt on or before the supply cutoff date. • If Total Available < Minimum Quantity, suggest a new order, in which: o Minimum Quantity is the value for the Min–Max Minimum Quantity item attribute. • Order Quantity = Maximum Quantity – Total Available, adjusted for order quantity modifiers:

30

o Oracle Inventory revises the order quantity if necessary for the quantity to be a multiple of the fixed lot size multiplier.

o The order quantity must be greater than or equal to the minimum quantity, or Oracle Inventory revises the quantity upward to the minimum. If you choose Yes to any of the net demand options, Oracle Inventory performs the following calculation:

•

Nettable Quantity on Hand + On Order – Open Demand = Total Available, 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. o On Order is the sum of open purchase orders, requisitions, 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, inventory reservations, including reserved sales orders, issue move orders, and WIP component demand scheduled for issue on or before the demand cutoff date.

•

If Total Available < Minimum Quantity, suggest a new order, in which o Minimum Quantity is the value for the Min–Max Minimum Quantity item attribute.

•

Order Quantity = Maximum Quantity – Total Available, 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. o The order quantity must be greater than or equal to the minimum quantity, or Oracle Inventory revises the quantity upward to the minimum. o The order quantity must be less than or equal to the maximum quantity, or Oracle Inventory revises the quantity down to the maximum.

When you run the Min–Max Planning report, you can have Oracle Inventory create requisitions for buy items and unreleased jobs for make items by answering Yes to Restock. You must also specify a ocation to serve as the default deliver to location on the requisitions. Oracle Inventory creates purchase requisitions for Buy items when the item attribute Replenish ment Source Type is set to Supplier. Oracle Inventory creates internal requisitions for internal sales orders for Buy items when the item attribute Replenishment Source Type is set to Inventory. For internal requisitions, Oracle Inventory uses the item attribute Source Organization to determine the organization from which the internal requisition sources the item. For Repetitive Items you optionally create requisitions or unreleased jobs. The following example shows you how Oracle Inventory performs min–max planning. 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, and specify No to Net Reserved Orders, Oracle Inventory performs the following calculations:

31

•

• •

Total Available: 25 + 50 = 75 o We assume that all the supply is within the supply cutoff date, for a supply total of 50. o Total available quantity is 75. Below min check: 75 < 100 o The total available quantity is less than the min–max minimum quantity, so Oracle Inventory plans a new order. Max quantity less total available: 500 – 75 = 425 o To bring the quantity available back to the min–max maximum, Oracle Inventory will plan an order for 425.

If you run the Min–Max Planning report, and specify Yes to Net Reserved Orders, 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, for a supply total of 50. o We assume that all the demand is within the demand cutoff date, so open reserved orders total to 90. o Total available quantity is (–15). Below min check: (–15) < 100 o The total available quantity is less than the min–max minimum quantity, so Oracle Inventory plans a new order. Max quantity less total available: 500 – (–15) = 515 o To bring the quantity available back to the min–max maximum, Oracle Inventory will plan an order for 515.

Explaining ABC Analysis ABC Analysis is the classification of a group of items in decreasing order of annual dollar volume or other criteria. This array is then normally split in to three classes A, B, and C. • A Group- The A group usually represents 10% to 20% by number of items, and 50%-70% by projected dollar volume. • B Group- 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. Cycle Counting With cycle counting, Inventory is counted on a cyclic schedule rather than once a year. A cycle inventory count is usually taken on regular defined basis. Most effective cycle counting systems require the counting of a certain number of items every workday with each item counted at a prescribed frequency. With ABC analysis you can use cycle counting to count items of greater importance more frequently than those of less importance. Cycle counting s scheduled counting based on value or counting by location, and can be set up at the organization level or the subinventory level. Benefits of Cycle Counting Keeping inventory records accurate by correcting errors between the system on-hand (perpetual) and actual on-hand (physical quantities). Cycle counting can also be a valuable tool to help identify patterns in the errors found. Analysis of these patterns can suggest and help to prioritize

32

improvements in training, tools, and processes. Over a period of time these improvements may increase the average level of inventory record accuracy. 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 the accuracy of your system on-hand quantities. You can perform a physical inventory for an entire organization or for particular subinventories within an organization. Physical inventories are usually performed once every six months, or once a year depending on organization requirements.

FAQs 33

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

Pick Release can be run using the following methods:  On-line: You can pick release one order immediately, thereby eliminating time spent waiting for the order to process through the Concurrent Manager queue. This is done in the Release Sales Orders for picking window. This window can also be accessed from the Tools menu in the Shipping Transactions window.

 Concurrent: You can run pick release in the background, enabling you to run other processes simultaneously. This is done in the Release Sales Orders for picking window. This window can also be accessed from the Tools menu in the Shipping Transactions window. 

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. This is done in the Release Sales Orders for Picking SRS window.



Shipping Transactions window: You can run pick release in the Shipping Transactions window by selecting Launch Pick Release from the Actions menu.

Material Picking or Pick Release: Oracle shipping execution enables you to use move orders Transactions for generating pick requests and reservation in Oracle Inventory. With the new pick release engine, you can pick release all items together on a trip or stop. You can also pick release items on a delivery. Using the new engine can be performed a one-two or three-step process. One Step process consists of select both auto-detail and auto pick confirm checkboxes on the inventory tab when you pick release, which means that the pick recommendation is automatically created and pick confirmed without any manual interaction. Two Step process consists of selecting auto-detail, but not auto pick confirm, which creates a move order that is automatically detailed but enables you to view the pick recommendation and provides the opportunity to change quantity, location, sub inventory and to report a missing quantity at the pick confirmation step in the transact move orders window. Once you have made your changes you can transact the move order to pick confirm the inventory. Three Step process consists of selecting neither the auto-detail or auto pick confirm check boxes, which creates a move order that you can manually or automatically detail in the transact move order window. Once detailed, you can transact the mover order to pick confirm the transaction. 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). The detailing process fills in the move order line details with the actual transactions to be performed. If adequate quantity is not available to detail the mover order, this process can be repeated later. If no reservations exist before the detailing process, it also creates reservation for the material. 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

Concurrent pick release releases one or more orders in the background improving the performance for the . The can continue working with the application even though the pick release has not completed yet. On-line pick release releases the orders while the waits for the application to returns the control to the . The may feel a lower performance in the applications depending of how many lines are being processed. 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. 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, and may include intermediate stops. Trips can be created automatically or manually. Creating a Trip There are several ways to create a trip:  Automatic  Manual Automatic If your shipping process does not require advanced planning, you may prefer to automatically create trips:  

Auto-creating a trip for a delivery: You can find the delivery you want to ship, and autocreate a trip and related 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, related deliveries, and trip stops.

Manual During transportation planning, you can manually create a trip and later assign delivery lines or find the delivery lines and create a trip. For example, for a regular trip scheduled to depart every Friday, you can manually set up a trip ahead of time and then assign delivery lines. When you manually create a trip, you can manually assign stops, deliveries, and delivery lines to that trip. Ship Confirmation The material picking process ends when the items are ship confirmed out of inventory. Ship confirming the items removes the existing reservations and performs the sales order issue transaction. You may choose to ship confirm only part of the sales order quantity. In this case, the balance of the sales order may be backordered. Back ordering at Ship Confirm automatically splits the sales order into two lines. The first line represents the shipped quantity, and the second line represents the backordered quantity. The backordered line is automatically Pick Released by Oracle Shipping Execution. A move order line is automatically generated for the backordered quantity. What is Item Cross References used for? Cross Reference types define relationship between Items and entities such as Customer Items or Supplier Items. 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. On-Hand Qty reduces on Miscellaneous Issue

38

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

How are Backorders handled /processed?

39

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

How can I ship the fastest way? Check the Autodetail option in Pick Release. It can be defaulted from the Shipping Parameters form. Set the profile INV: Detail Serial Numbers to ‘Yes’. Inventory will then suggest serial

40

numbers during the Detailing process. Do not check the Pick Confirmation Required flag in the Organization Parameters form. What criteria use the process to release the eligible order lines? This is indicated by the Release Sequence Rule. It uses the following attributes: order number, outstanding invoice value, schedule date, departure date and shipment priority. How does the pack slip report groups the released lines? It uses the pick slip grouping rule assigned during the pick release. A pick release process may print more that one report for the same picking batch. ORG_ID can be set at Master Level or Transaction Level? ORG_ID can be set at Transaction Level. 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. Only in GL, Set of book id should have the value to restrict the data for a responsibility. 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, there is no shipping involved. The steps involved are Book the Order, Purchase release, Invoicing. 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. Warehouses are what organizations in Oracle Manufacturing? Inventory What is meant by shipment tolerance? Over/Under shipment tolerance, While shipping we can over/under shipping the quantity in the sales order. What is the difference between Standard Sales Order Cycle and Drop Shipment Order Cycle? Shipment is the difference. 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. Hold criteria A criterion used to place a hold on an order or order line. A hold criteria can include customers, customer sites, orders, and items. Hold source An instruction for Order Management to place a hold on all orders or lines that meet criteria you specify. Create a hold source when you want to put all current and future orders for a particular

41

customer or for a particular item on automatic hold. Order Management gives you the power to release holds for specific orders or order lines, while still maintaining the hold source. Oracle Order Management holds all new and existing orders for the customer or item in your hold source until you remove the hold source. Hold type Indicates the kind of hold you place on an order or order line. 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,*Stock able, Transact able, Revision Control Receivable, 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, Customer Enabled, Shippable, *Internal Order, *Internal Order Enabled, *OE Transact able, Assemble To Order, Returnable *Customer should be “Internal” Can you update the Sales Order once it is Booked? Depends on the Processing Constrains setup. What are the prerequisites of the Sales Order? Customer, Price List and Order Type. What are different order types?  Order  Return  Mixed

42

Open Interfaces

43

Open Interface: Import Items The Item Interface lets you import items into Oracle Inventory and, if installed at your site, Oracle Engineering. When you import items through the Item Interface, you create new items in your item master organization, update existing items, or assign existing items to additional organizations. You can specify values for all the item attributes, or you can specify just a few attributes and let the remainder default or remain null. The Item Interface also lets you import revision details, including past and future revisions and affectivity dates. Validation of imported items is done using the same rules as the item definition windows, so you are insured of valid items. Import Items

Parameter All Organizations Validate Items

Meaning Indicate whether to run the interface for all organizations in the item interface table. If you choose No, the interface runs only for the current organization and interface table rows for other organizations are ignored. Indicate whether to validate all items and their data residing in the interface table that has not yet been validated. If items are not validated, they are not processed into Oracle Inventory. You would choose No if you had previously run the item interface and responded Yes for Validate Items and No for Process Items, and now want to

44

Process Items

Delete Processed Rows

process your items. Indicate whether to process items. If you choose Yes, all qualifying items in the interface table are inserted into Inventory. You would choose No, along with Yes for Delete Processed Rows, to remove successfully processed rows from the interface table without performing any other processing. Indicate whether to delete successfully processed items from the item interface tables. Choose No to leave all rows in the item interface tables for successfully processed items.

Interface Tables: The Item Interface reads data from three tables for importing items and item details. You use the MTL_SYSTEMS_ITEM_INTERFACE table for your new item numbers and all item attributes. This is the main item interface table, and may be the only table you choose to use. If you are importing revision details for your new items, You can use the MTL_ITEM_REVISIONS_INTERFACE table. This table is used only for revision information, and is not required. To import item category assignments, the MTL_ITEM_CATEGORIES_INTERFACE table is used to store data about item assignments to category sets, and categories to be imported into the Oracle Inventory MTL_ITEM_CATEGORIES table. A fourth table, MTL_ INTERFACE_ERRORS, is used for error tracking of all items that the Item Interface fails. Steps: Before you use the Item Interface, 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, and (if revision detail is included) the MTL_ITEMS_REVISIONS_INTERFACE table, as well as the MTL_ITEM_ CATEGORIES_INTERFACE table. After you load item, revision, and item category assignment records into these interface tables, you run the Item Interface to import the data. The Item Interface assigns defaults, validates data you include, and then imports the new items. You can also use the Item Interface to import item material cost, material overhead, and revision details. Concurrent program: Import Items To run the Item Interface, select Import Items from the Import submenu, accessed from the Inventory menu, or select Import Items in the Request Name field in the All Reports window Interface

Interface Tables

Item Interface

MTL_SYSTEMS_ITEM_INTERFACE MTL_ITEM_REVISIONS_INTERFACE MTL_ITEM_CATEGORIES_INTERFACE MTL_ INTERFACE_ERRORS

Interface Table MTL_SYSTEM_ITEMS_I NTERFACE

Concurrent Program Import Items (INCOIN)

Concurrent Program Import Items

Main Tables MTL_SYSTEMS_ITEM_B MTL_ITEM_REVISIONS MTL_ITEM_CATEGORIES

Error Table

Actual Table

API

MTL_INTERFACE_ ERRORS

MTL_SUYSTEM_I TEMS_B

To Create Item: INV_ITEM_GRP.CREATE_ITEM

45

To Update Item: INV_ITEM_GRP.UPDATE_ITEM

How can I run Item Open Interface in parallel mode, to enhance performance? There is a new field in the mtl_system_items_interface table called set_process_id. By populating this field, it is possible to process more than one batch at a time through the interface. The set_process_id identifies the process request via a numeric parameterand cannot be set to null. For example, if you wish to run 3 parallel processes, each batch can be set with a different set_process_id (i.e., 1, 2, 3). When the interface is scheduled on the interface scheduler, a corresponding value of 1, 2 or 3 can be entered as the last parameter in the schedule request. This defines which records are processed by that request and allows the 3 processes to run in parallel. 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. TRANSACTION_ID Enter Transaction ID TRANSACTION_TYPE CREATE = to create an item record (true when both importing a new item and asg an already existing item to another organization). This is the only value currently ed by the Item Interface. SET_PROCESS_ID Enter an arbitrary number. Rows designated with the same Value for SET_PROCESS_ID will process together. CATEGORY_SET_ID Enter Category Set ID CATEGORY_ID Enter Category ID PROCESS_FLAG Enter 1 for pending data to be imported. 1 = Pending 2 = Assign complete 3 = Assign/validation failed 4 = Validation succeeded; 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, and categories to be imported into the Oracle Inventory MTL_ITEM_CATEGORIES table. A table, MTL_INTERFACE_ERRORS, is used for error tracking of all items that the Item Interface fails. Before using the Item Open Interface, 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, and (if revision detail is included) the MTL_ITEMS_REVISIONS_INTERFACE table, as well as the MTL_ITEM_CATEGORIES_INTERFACE table. After you load item, revision, and item category assignment records into these interface tables, you run the Item Open Interface to import the data. The Item Open Interface assigns defaults, validates included data, and then imports the new items.

46

Interface Table

Concurrent Program

Error Table

Actual Table

API

MTL_ITEM_CATEGORIES _INTERFACE

Item Category Assignment Open Interface (INV_ITEM_CAT_ASSIGN_OI)

MTL_INTERFACE_ ERRORS

MTL_ITEM_CATEGORIES

INV_ITEM_CATEGORY_PUB. CREATE_CATEGORY _ASSIGNMENT

MTL_ITEM_CATEGORIES_INTERFACE Table: Column Name Instruction PROCESS_FLAG Enter 1 for pending data to be imported. After running the import process, the PROCESS_FLAG of the corresponding rows will be set to different values, indicating the results of the import 1 = Pending 2 = Assign complete 3 = Assign/validation failed 4 = Validation succeeded, import failed, 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. DELETE to delete already existing assignment. Enter an arbitrary number. Rows designated with the same Value for SET_PROCESS_ID will process together. Enter the organization that the new item will import into. Enter Category Set ID Enter Category ID Enter Item Number

Note: In case you Master Organization ID to the Table MTL_ITEM_CATEGORIES_INTERFACE, Item Category Assignment gets created for both Master and Child Organizations. This is application for both ways i.e. thru Interface or through API. 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. Ex: ‘101’-2001-30014001’ into an array of segments. To get the Code Combination ID

API INV_ITEM_GRP.UPDATE_ITEM INV_ITEM_CATEGORY_PUB.CREATE_CATEGORY INV_ITEM_CATEGORY_PUB.CREATE_CATEGORY_ASSIGNMENT FND_FLEX_EXT.BREAKUP_SEGMENTS

FND_FLEX_EXT.GET_COMBINATION_ID

Customer Item and Customer Item Cross-Reference Open Interfaces

47

Functional Overview - Customer Item Interface The Customer Item Interface lets you import customer items into Oracle Inventory. For each customer item you must define related information such as the Customer and Item Definition Level. Customer Address is required if you set Item Definition Level 3 while Customer Category is required for Item Definition Level 2. In addition, you can provide Master and Detail Container information, Commodity Codes, 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, you run the Customer Item Interface. The Customer Item Interface reads each record from the interface table and adds items that are successfully validated to the MTL_CUSTOMER_ITEMS table. Validation of the customer items uses the same rules as the Customer Items window to ensure that only valid items are imported. Functional Overview - 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. For each customer item cross-reference, you must define the Customer, Customer Item, Customer Item Definition Level, and Rank. You create a cross-reference to the associated Oracle Inventory item by specifying the item and its Master Organization. You can create multiple cross-references between customer items and one Oracle Inventory item. You can also create multiple cross-references between Oracle Inventory items and one customer item. Cross references are defined at the Master Organization level of the cross-referenced inventory item. Once a customer item cross-reference to an Inventory item has been defined, it is applicable to all organizations assigned the cross-referenced Inventory Item. You first add the customer item cross-reference records to the MTL_CI_XREFS_INTERFACE table. Then the Customer Item Cross-Reference Interface validates each record and moves the successfully validated items to the MTL_CUSTOMER_ITEM_XREFS table. 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. Interface Table MTL_CI_INTERFACE

Concurrent Program Import Customer Items

MTL_CI_XREFS_INT ERFACE

Import Customer Item Cross References

Table MTL_CI_INTERFACE: CUSTOMER_ITEM_NUMBER CUSTOMER_ITEM_DESC CUSTOMER_ID CUSTOMER_NUMBER CUSTOMER_NAME

Error Table

Actual Table MTL_CUSTOMER_IT EMS MTL_CUSTOMER_IT EM_XREFS

API

Customer Item Number Customer Item Description You define a customer by populating either of the CUSTOMER_NAME, CUSTOMER_NUMBER, or CUSTOMER_ID fields. Note that at least one of these fields must be entered for validation. The information provided in these fields is validated against the Oracle table RA_CUSTOMERS. Interfaces will error out with the appropriate error code if the customer information cannot be validated. 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.

48

TRANSACTION_TYPE

ERROR_CODE ERROR_EXPLANATION PROCESS_FLAG PROCESS_MODE

■ CUSTOMER_NUMBER has priority over CUSTOMER_NAME. TRANSACTION_TYPE is a required field. The interfaces will error out if a required field is missing or contains invalid data. Always set the TRANSACTION_TYPE to CREATE to create a new item in the MTL_CUSTOMER_ITEMS table. This is the only value ed currently by this interface. 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. Data already in these columns is ignored and overwritten if necessary. Note that these are required columns and should be populated with 1.

Open Transaction Interface Oracle Inventory provides an open interface for you to load transactions from external applications and feeder systems. These transactions could include sales order shipment transactions from an order entry system other than Oracle Order Entry, or they could be simple material issues, receipts, or transfers loaded from data collection devices. The following transaction types are ed by this interface:  Inventory issues and receipts (including -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. For material movement of items that are under lot or serial control, you must also insert rows into MTL_TRANSACTION_LOTS_INTERFACE and MTL_SERIAL_NUMBERS_INTERFACE respectively. There are two modes you can use to process your transactions through the interface. In the first processing mode, you populate the interface table only. Then the Transaction Manager polls the interface table asynchronously looking for transactions to process, groups the transaction rows, and launches a Transaction Worker to process each group. In the second processing mode, you insert the rows in the interface table and call a Transaction Worker directly, ing the group identifier of the interfaced transactions as a parameter so that the worker can recognize which subset of transactions to process. The Transaction Worker calls the Transaction Validator which validates the row, updates the error code and explanation if a validation or processing error occurs, and derives or defaults any additional columns. Next, the Transaction Processor records the transaction details in the transaction history table along with relevant current cost information. All material movement transactions update inventory perpetual balances for the issue, receipt, or transfer locations. Once the transaction has been successfully processed, the corresponding row is deleted from the interface table. Finally, the transaction is costed by the transaction cost processor which runs periodically, picking up all transactions from the history table that have not yet been marked as costed.

49

Additional Transaction Processing Flow Steps The following transactions require additional processing by the transaction processor or other modules. Inventory Issue Transactions Inventory Issue transactions consume any existing reservations where the Transaction Source Type and Source match. For example, if you reserved 10 boxes of paper for the Finance department, and then you issue 4 boxes to that department, the reservation will automatically be partially consumed, with a remaining balance of 6 reserved boxes. Average Cost Transactions In average cost organizations, receipts and average cost update transactions modify the item’s average cost using the current average cost, on-hand quantity, and the transaction value and quantity (if appropriate) to calculate the new average. 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. WIP Completion Transactions WIP completion transactions update the job or repetitive schedule completed quantities, launch appropriate backflush transactions, and relieve costs of completed assembly from the job/schedule. If you are completing an ATO assembly, you must specify the sales order demand details so that Oracle Inventory can reserve the completed units to the appropriate sales order line/shipment. If the WIP completion/return transaction completes or return job assemblies in an average costing organization, the rows in the CST_COMP_SNAP_INTERFACE table are transferred to the CST_COMP_SNAPSHOT table so that completion costs can be calculated. Sales Order Shipment Transactions For sales order shipment transactions, the Transaction Processor attempts to consume any reservations that may have been created for an order by matching the Order, Line, Delivery, and Picking Line identifiers. If MRP is installed, the processor also creates an interface row in MRP_RELIEF_INTERFACE that the MRP Planning Manager uses to relieve the Master Demand Schedule. Interface

Interface Tables

Transaction Interface

MTL_TRANSACTIONS_INTERFACE MTL_TRANSACTION_LOTS_INTERFACE MTL_SERIAL_NUMBERS_INTERFACE

Concurrent Program Process transaction interface

Error Tables

API INV_QUANTITY_TREE_PUB. QUANTITY_UPDATE

MTL_INTERFACE_ERRORS

Actual Table: MTL_MATERIAL_TRANSACTIONS

Bill and Routing Interface Functional Overview: Interface

Interface Tables

Bill and Routing Interface

BOM_BILL_OF_MTLS_INTERFACE BOM_INVENTORY_COMPS_ INTERFACE BOM_REF_DESGS_INTERFACE

Concurrent Program Bill and Routing Interface

Main Tables

50

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, Process, or Procedur e

Table, View, Module Name, or Procedure Name

Oracle Inventory

Transactio ns

Inbound

Table

MTL_TRANSACTIONS_INTERFACE MTL_SERIAL_NUMBERS_INTERFACE MTL_TRANSACTION_LOTS_INTERFAC E

Oracle Inventory

On-Hand Balances

Outboun d

View

MTL_ITEM_QUANTITIES_VIEW

Oracle Inventory

Item

Inbound

Table

MTL_SYSTEM_ITEMS_INTERFACE MTL_ITEMS_REVISIONS_INTERFACE

Oracle Inventory

Customer Item

Inbound

Table

MTL_CI_INTERFACE

Oracle Inventory

Customer Item CrossReferences

Inbound

Table

MTL_CI_XREFS_INTERFACE

Oracle Inventory

Material

Inbound

Table

MTL_TRANSACTIONS_INTERFACE MTL_SERIAL_NUMBERS_INTERFACE MTL_TRANSACTION_LOTS_INTERFAC E

Oracle Bills of Material

Bill of Material

Inbound

Table

BOM_BILL_OF_MTLS_INTERFACE BOM_INVENTORY_COMPS_ INTERFACE BOM_REF_DESGS_INTERFACE BOM_SUB_COMPS_INTERFACE MTL_ITEMS_REVISIONS_INTERFACE

51

BOM_EXPORT_TAB BOM_SMALL_EXPL_TEMP Oracle Work in Process

Move Transactio n

Order managem ent

Order Header

Inbound

Table

WIP_MOVE_TXN_INTERFACE CST_COMP_SNAP_INTERFACE (if OE_HEADERS_IFACE_ALL OE_LINES_IFACE_ALL

Order Lines

Open Interface: Order Import Order Import is an Order Management Open Interface that consists of open interface tables and a set of APIs. Order Import can import changes for existing Sales Orders, new and completed sales orders or returns from various sources, both Oracle and Non Oracle, for example, legacy systems, EDI transactions that are processed by the Oracle e-Commerce Gateway, or internal orders created for internal requisitions developed in Oracle Purchasing or returns. Order Import features include validation and defaulting, processing constraint checks, applying and releasing of order holds, scheduling of shipments, and finally inserting, updating or deleting the orders in the base Order Management tables. Order Management checks all the data during the import process to ensure its validity within the module. Valid transactions are then converted into orders with lines, reservations, price adjustments, and sales credits in the base Order Management tables. It is to be noted here that Order Import does not populate any Shipping tables. 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. Each time you run Order Import, Order Management produces a summary of information letting you know of the total number of orders that Order Import has evaluated, and if succeeded or failed.

52

Form Field Order Type Price List

OE_ORDER_HEADERS_ALL ORDER_TYPE_ID PRICE_LIST_ID

Table Name OE_TRANSACTION_TYPES_ALL QP_PRICE_LISTS_V

Column Name TRANSACTION_TYPE_ID PRICE_LIST_ID

Salesperson

SALESREP_ID

RA_SALESREPS_ALL

SALESREP_ID

HZ_CUST_S or Customer Number

CUST__ID

SOLD_TO_ORG_ID

Org ID Warehouse

SOLD_FROM_ORG_ID SHIP_FROM_ORG_ID

OE_SOLD_TO_ORGS_V HR_OPERATING_UNITS ORG_ORGANIZATION_DEFINITIONS

Other Columns NAME NAME SALESREP_NUMBER PARTY_ID

ORGANIZATION_ID ORGANIZATION_ID ORGANIZATION_ID

NAME SITE_USE_CODE= SHIP_TO LOCATION

Ship To Location

SHIP_TO_ORG_ID

Bill To Location

INVOICE_TO_ORG_ID

HZ_CUST_ACCT_SITES_ALL HZ_CUST_SITE_USES_ALL Or OE_SHIP_TO_ORGS_V

HZ_CUST_ACCT_SITES_ALL HZ_CUST_SITE_USES_ALL Or OE_INVOICE_TO_ORGS_V

SITE_USE_ID

SITE_USE_ID

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

53

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,CREDIT'; --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'; --PRICE_LIST_ID=218220 Saesrep ID: =========== select * from ra_salesreps_all where name='ICO_POLAND' and org_id = 684; Custmer Id : ============= select PARTY_ID from hz_cust_s where CUST__ID = 57654 -- sold_to_org-id Standard Sales Order: insert into oe_headers_iface_all (order_type_id, --order_type, order_source_id, orig_sys_document_ref, PRICE_LIST_ID, TRANSACTIONAL_CURR_CODE, SALESREP_ID, customer_id, sold_to_org_id, ship_to_org_id, invoice_to_org_id, customer_po_number, ordered_date, org_id, created_by, creation_Date, last_updated_by,

54

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

55

,'N' --calculate_price_flag, ,SYSDATE --request_date, ,NULL --schedule_ship_date, ,NULL--promise_date, ,10 --UNIT_LIST_PRICE, ,10 --unit_selling_price, ,'INSERT' --operation_code, ,1 --last_updated_by, ,sysdate --last_update_date, ,1 --created_by, ,sysdate --creation_date );

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

56

SHIP_FROM_ORG_ID ) values ( 1593 -- order_type_id -- ,'EDC RMA ICO w/RECEIPT,CREDIT' -- order_type ,0 -- order_source_id, ,'7777' -- orig_sys_document_ref , 218220 -- PRICE_LIST_ID ,'PLN' -- TRANSACTIONAL_CURR_CODE, , 100001022 -- SALESREP_ID , 318612 -- customer_id , 57654 -- sold_to_org_id, , 861109 , 137951 , 45678 ,sysdate , 684 ,1 ,sysdate ,1 ,sysdate ,'INSERT' ,687 );

-- ship_to_org_id, -- invoice_to_org_id, -- customer_po_number, -- ordered_date, -- org_id, -- created_by, -- creation_Date, -- last_updated_by, -- last_update_Date, -- operation_code -- ship_from_og_id

insert into oe_lines_iface_all (order_source_id, orig_sys_document_ref, orig_sys_line_ref, inventory_item_id, order_quantity_uom, --Need to Check if ist always Item Level Default Value? ship_from_org_id, ordered_quantity, calculate_price_flag, request_date, schedule_ship_date, promise_date, UNIT_LIST_PRICE, unit_selling_price, operation_code, last_updated_by, last_update_date, created_by, creation_date, LINE_CATEGORY_CODE, RETURN_REASON_CODE, LINE_TYPE_ID, RETURN_CONTEXT, org_id ) Values

57

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

58

Note: If any of the required fields for a booked order are not supplied, Order Management still imports the order in the Entered state and reports a booking error. Orders can be imported as ENTERED, BOOKED or CLOSED. Status of Orders Orders can be imported as ENTERED, BOOKED, CLOSED. If an order is imported with an entry status of ENTERED (OE_HEADERS_IFACE_ALL.BOOKED_FLAG=N or NULL) then the result after import is that the line is BOOK_ORDER eligible. 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’. By ing the action request to the OE_ACTIONS_IFACE_ALL table, i.e. in the OE_HEADERS_IFACE_ALL do not the BOOK_FLAG and in the OE_ACTIONS_IFACE_ALL table put operation code as BOOK_ORDER. If an order is imported with an entry status of CLOSED, Closed_Flag should be ed as "Y" to the OE_HEADERS_IFACE_ALL table and OPERATION_CODE should be "INSERT. 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. There is a difference between closing an existing order and importing orders in "CLOSED" status the first time itself. 3. As orders were already closed in the old system, there will not be any changes performed to the records, which means no defaulting. 4. The entire book required columns need to be ed for importing a Closed Order, as it goes through the booking cycle where validation for all the booking required columns are done. Scheduling Order Import allows you to reserve orders as they are imported, using the same rules as online order entry. If the scheduling request is unsuccessful on an imported order, the order will still be imported, and the scheduling exceptions can be viewed in the Error Messages of the Order Import Corrections window. 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. Cancellation of Order using Order Import  If the entire order is to be cancelled, then  The lines information should not be loaded into the interface table.  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. 

If only the line is to be cancelled then  Both the lines and the header tables should be populated in the interface table.

59



Set the CANCELLED_FLAG to 'Y' only for the lines with the qty updated to zero. And the operation code to be used for cancellation should be ‘UPDATE’ .

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'. Then since the line CANCELLED_FLAG is also 'Y' it tries to cancel the already cancelled line and errors out. So depending on whether the order or the line is to be cancelled, the cancelled flag and the header information or the line information should to be loaded. Updating Existing Orders using Order Import While updating existing Sales Orders, the Operation_code should be UPDATE. When an existing order is updated, the header_id and other Order related details are queried based on the Order Source Id and the Orig Sys Document Ref number. For the Order Line, the Order_source_id ,Orig_sys_document_ref, and Orig_sys_line_ref are used to get the specific line for updation. 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). An Order cannot be updated to status closed as it is assumed that after importing the order, it will be processed in OM until closure. Add Customer Order Management provides the capability to add a new customer, the address and s using Order Import. The table OE_CUSTOMER_INFO_IFACE_ALL needs to be populated for this. 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. This table can also be used to import a new address only or 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 link depends on the CUSTOMER_INFO_TYPE_CODE. When the order import is used to create a new customer (new /address/ etc), the CUSTOMER_INFO_TYPE_CODE should be either ('', 'ADDRESS', or '') to denote the type of information in the record. 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.

60

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

61

Creation of a Referenced RMA (If s want to return an existing outbound line) If you create a referenced RMA, you should copy the Header Record for the return from the referenced Order header record, modifying the Order Type to category RETURN or MIXED (order_type_id from oe_transaction_types_all). Creation of a Referenced RMA (If s want to return an existing outbound line) If you create a referenced RMA, you should copy the Header Record for the return from the referenced Order header record, modifying the Order Type to category RETURN or MIXED (order_type_id from oe_transaction_types_all). For the Order Line record, populate the following attributes only: line_category_code: RETURN return_context: ORDER return_attribute1: header_id from the referenced order. return_attribute2: line_id from the referenced order line. calculate_price_flag: Set it to “P” if you want to retain the original price, the flag to “Y” if you want to reprice the RMA line. Putting the flag to “N” will still import the freight charges from the referenced line. line_type_id: Assign a line_type_id from RMA line. Line_type_id is optional, provided a default line_type has been defined for the specified Order Line Type. ) Return_reason_code: Populate a reason code from lookup_type CREDIT_MEMO_REASON For sales credit info, populate the header_level/line level sales credits details from the referenced order. EDIs: EDI Name EDI 850 EDI 860

EDI 855 and EDI 865

Purpose Inbound Order Import inbound Order Change (860/ ORDCHG) transactions for automated changing of order shipment quantities, dates and location information. You can send EDI acknowledgments for original orders and change requests (Whether received through EDI or other means). Both the outbound Purchase Order Acknowledgment (855/ORDRSP) transaction, and the outbound Purchase Order Change Acknowledgment (865/ORDRSP) transaction are ed.

Holds and Releases Order Management automatically applies all holds to imported orders and order lines that meet hold criteria. Order Import applies holds on imported orders for review, just as you would for orders entered through the Sales Orders window. Holds can be applied or released using OE_ACTIONS_IFACE_ALL. 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, the Operation_Code should be APPLY_HOLD and the Hold_ID needs to be populated. For releasing the hold using OE_ACTIONS_IFACE_ALL, 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. The HOLD_ID and the RELEASE_REASON_CODE should also be populated.

62

Configuration (ATO/PTO) Order Management provides you with the ability to import ATO and PTO configurations. For EDI orders, you can import valid and invalid configurations, however, you will not be able to book orders with invalid configurations. In case of (Configurations) ATO models (also in case of PTO models), has to send the optional components along with model. This is because although OM knows the BOM of the ATO model, it will not know what options wants to select. should not send the standard mandatory components. The following operation Code can be used in the actions table for the configurations. For both the operation codes, the Entity Id used is the Line_ID of the Top Model Line of the ATO configuration. -- DELINK_CONFIG deletes the configuration item. -- MATCH_AND_RESERVE checks if an existing configuration item matches the configuration created by the and if the configuration item is available, it reserves it. Table: Operation Code for Configuration

Adding Lines to existing Orders In Order Management, a new line can be added to an existing order or an existing line can be split into two or more lines. For this, the Operation Code at the header should be UPDATE and the operation code at the line level should be INSERT or CREATE. If the SPLIT_FROM_LINE_REF, is populated then the LINE_ID in the line table is taken as the SPLIT_FROM_LINE_ID and that line is SPLIT. In case it is not populated then a new line is added to the existing order. Validation of data Before Importing Unlike in Order Import in Rel 11, in 11i the Order Import process can be run in the validation-only mode. This mode allows the transaction to be validated against all the Order Management rules but does not allow it to valid transactions to the base Order Management tables. s can run production transactions in validation-only mode for a preview of exceptions. Make necessary corrections to the transactions in the Order Import window, and then choose the Validate button to perform a validation check. 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. Viewing Orders that have failed In Order Management Rel 11i, the orders that have failed in Order Import can be viewed in the Corrections summary window. These orders are highlighted in red in the window. Viewing Errors In Order Management, the error can also be viewed from the Application. 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. If you choose the Errors

63

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

64

Orders can be imported in any valid entry status, including Booked. It also allows completed orders to be imported. It also allows the transfer of requisitions for internally sourced products from Purchasing. Once the interface managers pick up the records in the interface tables, it validates them to see if orders need to be created, updated or deleted. Depending on the arguments specified, respective processes are triggered. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16.

The entities are processed in the following sequence: Process Header Record Process Header Adjustments. 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, the first thing that is done is to insert the request_id into the interface tables. The value of the CLOSED_FLAG is checked. If CLOSED_FLAG = ‘Y’, the Order import procedure for closed orders (OE_CNCL_ORDER_IMPORT_PVT.Import_Order) is called. If CLOSED_FLAG = ‘N’, the Order Import Procedure for open Orders OE_ORDER_IMPORT_PVT.Import_Order is called. This will first give the validation of the case where CLOSED_FLAG = ‘N’. If the OPERATION_CODE is ‘INSERT’ then it is changed to ‘CREATE’ for all the interface tables. The Order Import Pre Processor is called. The validation starts. It is done in three steps: Check for Required Attributes. Validate that all the required attributes have been specified on the entity and even if one required attribute is missing, raise an error and quit. For example, Inventory Item is a required field on the order line entity. Check for Conditionally Required Attributes. 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, raise an error and quit. For example, for a booked line, ship to location is required. Cross-Attribute Validation. Validate all those attributes that are dependent on the value of another attribute. At the end of the validation, if at least one attribute is not valid, then raise an error and quit. For example that the ship to is valid for the customer. What is the MTL_TRANSACTIONS_INTERFACE table used for? A1. This is the Interface between non-Inventory applications and the Inventory Transactions module. In other words any other module other than Inventory that wants to update Inventory has to come through this table. Modules such as WIP (Work In Progress) and OE (Order Entry) first their records to the MTL_TRANSACTIONS_INTERFACE (MTI) for validation.

65

There is an Interface Manager called the Transactions Manager (INCTCM) which reads records from this table, validates them and moves the successful transactions onto MTL_MATERIAL_TRANSACTIONS_TEMP, and submits Transaction workers (sub-processes INCTCW) which then processes these records through inventory. This process consists of data derivation, validation, and transfer of records from MTL_TRANSCTIONS_INTERFACE, MTL_TRANSACTIONS_LOTS_INTERFACE and MTL_SERIAL_NUMBERS_INTERFACE into their respective TEMP (temporary) tables from where the transactions processor processes them. Both the Lots and Serial number tables above are used when items being updated are under 'Lot' or 'Serial' number control. Example :- In the case of an Sales Order, the item is being shipped to a client so the lot and serial number if being used, this needs to be updated to show that it is no longer available in Inventory stock. 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. LOCK_FLAG = 2 PROCESS_FLAG = 1 transaction_mode = 3 What is the MTL_MATERIAL_TRANSACTIONS_TEMP table used for? Once the transactions have been ed 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. 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. Inventory Module Forms like Miscellaneous transactions writes directly into this table. The transactions which are done through this form are on-line processing. It is from here that the inventory quantities finally get updated; serial/lot numbers get marked as being used. 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 s table for transfer to General Ledger. This is a transactional historical table. However, it is the holding point for transactions to be cost. The Cost Manager is a concurrent job that runs in the background. (CMCTCM) COSTED_FLAG = 'N'(Not Processed) This means record is pending. If it is NULL then the transaction has already been processed. If it is set to 'E' then it has erred for some reason.

66

What are the major tables involved in Material Movement for Inventory and WIP Material, Move, and Resource Transactions? MTL_TRANSACTIONS_INTERFACE -- INCTCM is the Transaction Manager for this Table. MTL_MATERIAL_TRANSACTIONS_TEMP -- INCTCM is the Transaction Manager for this Table MTL_MATERIAL_TRANSACTIONS -- 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. WIP_MOVE_TXN_INTERFACE -- WIP Move Transaction Worker processes records in this table (WICTCM) WIP_MOVE_TRANSACTIONS -- Must be viewed and resubmitted via SQL with the scripts below WIP_COST_TXN_INTERFACE -- Resource Cost Worker processes records in this table.

When attempting to load legacy data into the MTL_TRANSACTIONS_INTERFACE table, into what column is the PO number input? There is not a direct column for PO number. In the Oracle Manufacturing Implementation Manual, locate the section on Open Transactions Interfaces. This section describes the transaction type id's and there is not a PO number. Refer to the column of transaction_reference and this column will allow the PO number. The column is optional and shows up on reports and transaction displays. Since a column for the PO number does not directly exist, a transaction_reference field can be used to input this information. Why is the distribution ID required in MTL_TRANSACTIONS_INTERFACE? All issues and receipts of asset items to an asset subinventory and sales order shipments require the distribution id that originates from GL code combinations. This id is required to create a complete audit trail of the transaction. What is a Drop ship PO? Oracle Order Management and Oracle Purchasing integrate to provide drop shipments. 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, or because it’s more cost effective for the supplier to ship the item to the customer directly. Drop shipment was introduced in R11. How is a Drop Ship PO created? Drop shipments are created as sales orders in Order Management. The Purchase Release concurrent program or workflow in Order Management creates rows in the Requisition Import tables in Purchasing. Then Purchasing’s Requisition Import process creates the requisitions. Drop shipments are marked with the Source Type of External in Order Management and Supplier in Purchasing.

What is the setup required for Drop ship PO? ITEM ATTRIBUTES: Navigate: Inventory -> Items - > Organization items Purchased (PO) Enabled

67

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. All drop ship sub-inventory must have Reservable box checked. If the sub-inventory is not Reservable the sales order issue transaction will not be created in MTL_TRANSACTIONS_INTERFACE. After drop ship inventory organization is created, subinventories should be defined. To create the subinventory, go to an inventory responsibility and navigate to Setup -> Organizations -> Subinventories. Asset subinventories must have the reservable and Asset boxes checked. Expense subinventories must have the Reservable box checked and the Asset box unchecked. Subinventory Attributes for Asset Subinventory Reservable/Allow Reservations Asset Subinventory Subinventory Attributes for Expense Subinventory Reservable Asset-must NOT be enabled. How can we avoid the miscounting of supply as logical organization is involved? You must receive drop-ship items in a logical organization. If you use Oracle master Scheduling/MRP and Oracle Supply Chain Planning, to avoid miscounting supply you may not want to include logical organizations in your planning. If you choose to include logical organizations, ensure that doing so does not cause planning and forecasting complications.

If you make changes to a sales order after the Purchase Order (PO) has been generated, will the order changes automatically be updated on the PO? Order changes will not be automatically updated on the PO. Pulling up the Discrepancy report will allow you to view the differences between the Sales Order and PO. However, you will have to manually update the POs in the Purchasing application.

If items on a Drop Ship order are cancelled, 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. There is a discrepancy report available that will report differences between the PO and the Sales Order.

Does Order Management 11i have functionality to do serial number management with Drop Shipments? You are able to receive serial numbered Drop Ship stock. Order Management will receive the serial number noted on the PO.

Can Configurable Items be drop shipped? Currently only Standard Items can be drop shipped. Functionality for Configurable Items will be

68

added in future releases.

How do I drop ship across operating units? Release 11i does not currently this functionality. How are over/under shipments handled in drop shipment? If part of a drop-ship line ships, and you do not wish to fulfill the remaining quantity, cancel the line. Over shipments must also be handled manually. If the supplier ships more than the ordered quantity, you can bill your customer for the additional quantity or request that they return the item. Use the Drop Ship Order Discrepancy Report to view differences between your drop-ship sales orders and their associated purchase requisitions and orders.

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. This PO is linked to the drop ship order so that when the receipt is done (partial or complete) .OM is updated to receiving interface eligible. Drop ship lines do not use the pick release, ship confirm or inv interface order cycles.

Can we cancel drop shipment after it is received? Drop shipments cannot be cancelled once Oracle Purchasing obtains the receipt. A 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. Cancellation of a Partial Drop Ship receipt is allowable. But only the portion that has not been received can be cancelled. If you cancel a drop shipment line for which you have not shipped the entire quantity, the order processing splits the line. The first line contains the quantity shipped and the second line contains the non-shipped quantity in backorder. You can cancel the second line the backorder on the sales order. The PO line quantity should be changed to reflect the new quantity.

What debugging tools are available for Drop shipments? 1. Note 133464.1 contains a diagnostic script that can be used for troubleshooting problems with sales orders. 2. Debugging receipt transaction or the sales order issue 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 : Concurrent: Program: Define; query up the Receiving Transaction Processor and check the Enable Trace box. -Save the receipt for the deliver transaction (destination type will say Inventory for the deliver transaction). -View the Receiving Transaction Processor log file, the Inventory Transaction Worker log file, as well as, the trace for the errors.

What is the Import source and status of PO generated from Drop Shipment? Import source is Order Entry. Status of PO will always be approved.

69

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

70

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

71

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

72

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

73

Line Statuses in OM and SE

74

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

75

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

76

Order Statuses: Action Entered Booked

Order Management Header Line Status Status Entered Entered Booked Awaiting Shipping Booked Awaiting Shipping Booked

Picked

Booked

Shipped

Shipping Execution Action Status

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

AutoInvoice Import Program

Ready to Release Released to Warehouse Staged/Pick Confirmed Shipped/InTransit/Confirmed Interfaced

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

o o 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

78

79

80

81

Definitions

82

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

83

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

84

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

85

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

86

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

87

Order Processing Cycle A sequence of actions you or Order Management performs on an order to complete the order. 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, line type (standard, return or internal) and item type (standard, model, shippable, translatable, etc.) of that line. Order Import Order Import is Oracle Order Management’s Open Interface that import orders from an internal or external source, Oracle or Non-Oracle system, which performs all the validations before importing the order, that a normal order entered through the Sales Order window would have gone through. Order type Classification of an order. In Order Management, this controls an order’s workflow activity, order number sequence, credit checkpoint, and transaction type. Blanket Sales Agreement A sales order for a customer that has specific characteristics related to an order between a customer and a vendor. Replacement order A sales order created to replace goods being returned by a customer. Blanket Order A sales order for a customer that has specific characteristics related to an order between a customer and a vendor. Return material authorization (RMA) Permission for a customer to return items. Receivables allows you to authorize the return of your sales orders as well as sales made by other dealers or suppliers, as long as the items are part of your item master and price list. Drop shipment A Drop Shipment occurs when a customer order is sourced from and delivered by a supplier. Order Management sends information to the Purchasing Application to create that PO, and then when that PO is received (to indicate shipment from the supplier to your customer), the order line is automatically updated to indicate that it was fulfilled. In this process, 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, to indicate that we are defining the process from this point of view. 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; kits and models cannot be drop shipped at this time. A method of fulfilling sales orders by selling products without handling, stocking, or delivering them. The selling company buys a product from a supplier and has the supplier ship the product directly to customers. 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.

88

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. Internal Sales Order A request within your company for goods or services. An internal sales order originates from an employee or from another process as a requisition, such as inventory or manufacturing, and becomes an internal sales order when the information is transferred from Purchasing to Order Management. Also known as internal requisition or purchase requisition. 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. Sales credit Credits that you assign to your salespeople when you enter orders, invoices and commitments. 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. Order management – Defaulting Rule: Order Management Defaulting Rules reduce the amount of data input required when entering orders or returns. You can define business rules for defaulting values, and prioritize how conditions and validation rules are implemented. If a defaulting rule definition fails to default desired values for orders or returns, you can choose to define additional defaulting rules for most attributes (fields) within Entities such as Order or Line. A defaulting rule includes the following components: ■ Defaulting Source/Value (Entity and Attribute, Source Type) ■ Defaulting Condition ■ Precedence of Defaulting Condition (if multiple defaulting conditions exist, 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; usually the location is another entity and attribute. For most attributes, you can assign at least one entity/attribute defaulting source, in addition to using other defaulting sources. 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, either system- or -defined, as a default value source. You must indicate the name of the profile option to be used as the default

89

value in your rule. Profile options sources enable for flexible default value tailoring without complex customizations. Constant Value The constant value source option enables you to specify a constant value instead of a field that contains a value. 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. For example, if all items in your organization are sold with the unit of measure Each, you could define a defaulting rule to default the value of Each for the Unit of Measure attribute within the Order Line entity. System Variable This system variable source option enables you to default system variables or functions of system variables for a field. 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. For example if the policy of your organization is to ship all items on the next day, you can setup the Request Date defaulting rule with System Variable as sysdate + 1. Same Record Using same record as a source, you can default an attribute from another attribute on the same entity record. For example a common requirement is to compute tax for an order line based on the scheduled ship date for that line. Set up a defaulting rule for tax date with Same Record source and Source Attribute as Schedule Ship Date. Related Record The Relates Record is one of the most frequently used defaulting sources. Defaults for certain attributes can be setup when defining related object records such as Customer, Ship To, Bill To and Item. For each attribute that you can use as a default, related record source objects/ source attributes are pre-defined in the system. For example Order Type can be defaulted from its value on the related objects: Customer, Invoice To, or Ship To. The source attribute in each case would be Order Type. 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, enabling you to reference you API within a defaulting rule. Some of the Standard PL/SQL APIs: Package OE_ORDER_PUB

Function G_HDR.ORDER_CATEGORY_CODE G_LINE.LINE_CATEGORY_CODE G_HDR.ORDER_TYPE_ID G_LINE.LINE_TYPE_ID G_HDR.SHIP_FROM_ORG_ID G_HDR.SHIP_TO_ORG_ID G_HDR.INVOICE_TO_ORG_ID G_HDR.SOLD_TO_ORG_ID

90

G_LINE.SHIP_FROM_ORG_ID G_LINE.SHIP_TO_ORG_ID G_LINE.SOLD_TO_ORG_ID G_HDR.PAYMENT_TERM_ID G_LINE.PAYMENT_TERM_ID G_HDR.PRICE_LIST_ID G_HDR.CUST_PO_NUMBER G_HDR.FREIGHT__CODE G_LINE.FREIGHT__CODE G_LINE.INVENTORY_ITEM_ID GET_PRIMARY_DELIVER_TO OE_DEFAULT_PVT

OE_CHARGE_PVT FND_DATE FND_NUMBER INV_IC_ORDER_PUB

GET_TAX_CODE GET_ING_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.IC_CUSTOMER_ID G_LINE.IC_CUSTOMER_SITE_ID G_LINE.IC_SELLING_ORG_ID G_LINE.IC_SHIPPING_ORG_ID G_LINE.ORDERED_QUANTITY G_LINE.INVENTORY_ITEM_ID G_LINE.ORDERED_DATE

ing Rules Rules that Oracle Receivables AutoInvoice uses to specify revenue recognition schedules for transactions. You can define an ing rule where revenue is recognized over a fixed or variable period of time. For example, you can define a fixed duration ing rule with monthly revenue recognition for a period of 12 months. Define ing rules to create revenue recognition schedules for your invoices. ing rules determine the number of periods and percentage of total revenue to record in each ing period. You can use ing rules with transactions that you import into Receivables using AutoInvoice and with invoices that you create manually in the Transaction windows. You can define an unlimited number of ing rules. When you run the Revenue Recognition program for an invoice that is associated with one or more ing rules, Receivables creates the invoice’s revenue distributions for the period or periods in which the rules fall. Deferred ing Rules

91

You create deferred ing rules by selecting the Deferred Revenue check box in the Invoicing and ing Rules window during rule definition. When you use deferred ing rules, the Revenue Recognition program creates a single distribution per line that posts to an unearned revenue GL . You later earn the revenue using the Actions wizard. You can use deferred ing rules only for invoices that are assigned the Bill in Advance invoicing rule. If the invoicing rule on a transaction is Bill in Arrears, the Revenue Recognition program ignores the deferred flag. If you use a deferred ing rule with a single ing period, Receivables recognizes the revenue in the period that you specify with the Actions wizard. If you use a deferred ing rule with multiple ing periods, Revenue ing creates the revenue recognition schedule based on the rule, and the start date is determined by the GL start date that you entered using the Actions wizard. If the GL start date occurs in a closed ing period, Revenue ing posts that portion of revenue into the subsequent open ing period. If you use a non-deferred ing rule with multiple ing periods, Revenue ing uses the schedule created by the Revenue Recognition program. If an ing period is closed, Revenue ing posts that portion of revenue into the subsequent open ing period. 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. In this example, all periods are open.

The February 2 row shows what the original revenue recognition schedule would have been if the ing rule were not deferred. However, the rule is deferred in this example, which means that Receivables creates a single distribution line that posts to an unearned revenue GL when you run Revenue Recognition. Later, you use the Actions wizard to earn revenue on this invoice, but perhaps you entered March 2 as the GL start date. Revenue ing honors the original schedule, illustrated by the February 2 row. However, Revenue ing ignores the original start date from the transaction and uses the GL date, March 2, that you entered. This causes Receivables to shift the schedule by one month, illustrated by the March 2 row. •

This table illustrates what happens when you have a $300 invoice with a 3 month non-deferred rule. In this example, February is open at first, but is later closed before you can finish adjusting this invoice’s revenue.

92

The February 2 row shows the original revenue recognition schedule that Receivables creates when you first run Revenue Recognition. At this stage, February is open. Later, perhaps you discovered that the schedule was wrong, so you used the Actions wizard to unearn, and then correctly re-earn, the invoice’s revenue. When you re-earn revenue on invoices with non-deferred ing rules, Revenue ing uses the original schedule, illustrated by the February 2 row. In this example, however, at this stage, February is now closed. Therefore, Receivables posts February’s allocation to March, illustrated by the March 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 ing Rules. You assign ing rules to recognize revenue over several ing periods. The Revenue Recognition program will create distribution records for the invoices and credit memos that you create in Receivables and import using AutoInvoice. The Revenue Recognition program uses the ing distribution sets that you specify in the Transactions window or import into Receivables using AutoInvoice to determine the s of your newly created revenue distribution records. Revenue Recognition also creates the receivable, tax, freight, and AutoInvoice clearing assignments which correspond to the GL date of each invoice included in your submission. If you later decide that the GL distributions need to be reclassified, you can change the individual distribution on the transaction. Receivables will automatically create the reverse ing entries. When you submit the program, Revenue Recognition selects all transactions that have invoicing and ing rules and that have not yet been processed since you last submitted the program. The program creates the revenue distribution records for all ing periods specified by the ing rule on each transaction line. Receivables consider this revenue scheduled. If a deferred ing rule exists, then Revenue Recognition will create the distribution records for an unearned revenue . Receivables consider this revenue unscheduled. Note: Revenue Recognition creates ing distributions for all periods of status

Open, Future, or Not Open. If any period has a status of Closed or Close Pending, then Revenue Recognition creates the distributions in the next Open, Future, or Not Open period. If the Revenue Recognition program cannot create ing distributions for a transaction, then the program generates the ing for all other transactions in the submission, but completes with a status of Warning. Receivables include the transaction at the bottom of the Revenue Recognition Execution report so that you know which transaction to correct, incomplete, or delete.

93

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

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

Pick Slip Internal shipping document pickers use to locate items to ship for an order. If you use standard pick slips, each order will have it’s own pick slip within each picking batch. If you use the consolidated pick slip, the pick slip contains all orders released in that picking batch. Pack slip An external shipping document that accompanies a shipment itemizing in detail the contents of that shipment. Pick slip grouping rule Criterions for grouping together various types of pick slips. The rule dictates how the Pick Slip Report program groups released lines into different pick slips.

Note: Release Sequence rule and Pick slip Grouping Rule are attached in Shipping Parameters form or in Pick Release Rule. Bill of lading A carrier’s contract and receipt of goods transported from one location to another. 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. Alternative to manufacturing the parent item on a work order and then shipping it. Pick-to-order is also an item attribute that you can apply to standard, model, and option class items.

96

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

97

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

98

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



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. The activity might include picking up a new delivery, dropping off a delivery, or both.

In the above example, Trip 1: San Francisco (stop 1) to New York (stop 2), New York to Maim (stop 3), and Miami to Dallas (stop 4).

99

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

100

method activity is the Shipping activity. For a return line the fulfillment method activity is the Receiving activity. Ship Sets Ship Sets enable you to group order lines within a set for shipment. You can use ship sets to do the following:  Assign a single ship set to all the lines in an order to your customers that do not allow partial shipments.  For orders that contain multiple lines with the same item, to ensure that the order line is not released until the full quantity is available, assign the order line to a ship set. 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. 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. Arrival sets can:  Span multiple organizations, 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

Different Types of Sales Order Flows Different types of Sales Order flows: 

Standard Sales Order Flow

102

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, the sales order form enables you to organize, enter, view, and update order information. Order Management offers Line level independence where you can capture regular orders as well as returns using the same form. The sales order form offers s a convenient and quick entry point for creating and editing order information as well as viewing summary information from other subsystems (i.e. Shipping, Receivables, and Purchasing etc.) and status of orders.

Standard Sales Order - Process Steps: This section will guide you through a basic sales order flow from entry to invoicing, including:  Enter a Standard Sales Order  Schedule the Order  Book the Order  Pick Release  Ship Confirm  Fulfillment

103



Invoicing Interface

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

104

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, 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 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 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

   

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, building subassemblies / end products after receiving a customer order leading to increased delivery lead times  ETO – Engineer to Order entails deg, 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

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. Finds and releases eligible order lines that meet the release criteria and creates move order Configurable Process (four steps) 1. Pick Release 2. Move Order Line Detailing* 3. Move Order Line Pick Confirmation* 4. Ship Confirmation * May be automated  

Pick Release finds and releases eligible order lines that meet the release criteria; creates Move Orders that move the inventory to staging areas; and optionally, calls Inventory Pick Release to reserve items and print the pick slips. Picking Engine creates Move Order:  Must Detail to Print Pick Slips  Creates reservation from Org, Item, 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  A move order is a request for a subinventory transfer or issue.  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.  Reservations created for sales orders are automatically updated and transferred for the as the move order is released and transacted. Allocate Move Order: • Allocating is the process that uses Inventory picking rules (FIFO, LIFO etc) to determine where to source the material to fulfill a request line. • 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. • 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.

The move order is created by the Pick Release engine. Next, the move order must be “detailed.” 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 detailing process fills in the move order line details with the actual transactions to be performed. If adequate quantity is not available to detail the move order, this process can

108

be repeated later. If no reservation exists before the detailing process, it also creates the reservation for the material. Before transaction, s may print a pick slip or push the move order line details to mobile devices for transaction through the move order APIs. 3.

The now transacts the move order to confirm the pick. The order line can be transacted all at once, or s can transact one detail line at a time as the items are moved. If the transacts less than the requested quantity, the order remains open until the full quantity is transacted or the order is closed or canceled.

Move Order Components:

Anatomy of a Move order: Oracle Order Picking and Shipping stores the move order source type in the header. This refers to the entity that created the move order. An order could be a pick wave (for sales order picks) a replenishment type, a requisition for subinventory transfer and so on. Order Picking and Shipping also stores the default source and destination if available, the order number, and the requested date. The lines are the requests on that move order. They store the item, requested quantity, completed quantity (if the move order has been partially fulfilled), a source and destination if known, and any project and task references if the organization is Project Manufacturing enabled. The can also request specific serial or lot numbers if know, on the move order line. The line details are the Inventory transactions that occur to fulfill a particular request line (move order line). If the material is locator, lot, or serial controlled, this information is filled in at the line detail level. These details are automatically filled in by Oracle Inventory using the Inventory Picking Rules and the Item - Transaction defaults (for destination locators), or the can manually fill in the details. These details can be edited prior to transaction by a . The Move Order Line Details (transaction lines) created by the detailing process must be transacted to confirm the material drop-off in staging. This process is called Pick Confirmation. Pick confirmation executes the subinventory transfer that moves the material from its source location in the warehouse into the staging location. Pick Confirmation automatically transfers the

109

high level reservation to a detailed reservation (including lots, subinventory, revisions, and locators) in the staging location. At pick confirmation, a can report a missing quantity or change the transaction line if the picker chose to use material from a different lot, serial, locator, or subinventory. If an organization’s picks rarely deviate from the suggested picking lines and the overhead of requiring a Pick Confirmation is unmanageable, the Pick Confirm transactions can occur immediately after the lines are detailed. This option is called “auto pick confirm.” s can set up a default Pick Confirm policy in the Inventory organization parameters. This default can be overridden at each Pick Release. Note that even if an automatic pick confirm is employed, the material is only transacted to the staging subinventory and reserved. A can still manage any discrepancies found by deleting the reservation and transacting the material back to its original subinventory. If mobile devices such as bar code scanners are used to perform inventory transactions, you should use manual pick confirmation for greatest inventory accuracy and control. 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, 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. Pick confirmation  The move order line details must be transacted (in Inventory) to confirm the material dropoff in staging (Destination Inventory).  Pick Confirmation automatically transfers the high level reservation to a allocated reservation (including lots, subinventory and locators) in the staging location.  At pick confirmation, a can report a missing quantity or change information if material is picked from a different lot, serial, locator, or subinventory.

Ship Confirmation Business Flow:

110

Ship Confirmation:

Pack Material  Automatic volume & weight calculations  Automatic selection of containers  Control on fill percentage Transportation

111

 

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, cost of sales ing 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, “Interface Trip Stop – SRS” request needs to be run to effect interfaces to Inventory and OM.

112

Ship Options region:  Ship Entered Quantities, 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). For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values entered), the full quantity (10) is shipped and displays in the Shipped Quantity field.

 Ship Entered Quantities, 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). For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values), the full quantity (10) is backordered and displays in the backordered Quantity field.

 Ship Entered Quantities, Unspecified Quantities Stage: Leaves the unspecified delivery line quantity as staged and removes it from the delivery. For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values), the full quantity (10) remains in the Stage Quantity field and the line is no longer associated with a delivery. Note: If a non-zero Stage Quantity exists on a line, it is split from the line and unassigned from the delivery. If the Create Delivery for Staged Quantities is enabled, all staged delivery lines are grouped together in a new delivery.

 Ship Entered Quantities, Unspecified Quantities Cycle Count: Ship confirms the quantity of items specified in the Shipped Quantity field, treats blank quantities as full backorders (backorder quantity = requested quantity), and transfers the backorder reservation to cycle counting. For example, if the Requested Quantity is 10 and the Shipped Quantity field is blank (no values), the full quantity (10) is backordered and transferred to cycle counting. You can also transfer delivery quantities to cycle count prior to ship confirm by using the Shipping Transactions form, Cycle Count action.

 Ship All: Ship confirms the entire quantity regardless of what was entered in the Shipped Quantity field (shipped quantity = requested quantity). For example, if the Requested Quantity is 10 and the Shipped Quantity field is 5, the full requested quantity is shipped (10) and displays in the Shipped Quantity field.

 Backorder All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0, backorder quantity = requested quantity). Note: If the delivery status is Closed, the delivery is unassigned from all trips and all lines will be unassigned from the delivery.

 Cycle Count All: Backorders the entire quantity irrespective of what was entered (shipped quantity = 0, backorder quantity = requested quantity) and transfers the backorder reservation to cycle counting. You can also transfer delivery quantities to cycle count prior to ship confirm by using the Shipping Transactions form, Cycle Count action. 

Enable the Create Delivery for Staged Quantities box (default setting), if you want all staged delivery lines grouped together in a new delivery. If you do not want to create a trip for the delivery, click Go to ship confirm and save your work.

113

 In the Auto-create Trip Options region, select or update the Ship Method and the Actual Departure Date. 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. Closes the first stop of the delivery, but leaves second stop open. Sets status of delivery to Intransit and initiates Order Management (OM) and Inventory interfaces. o Close Trip: Creates a trip and stops for the delivery. Closes trip, all stops, and the delivery. You can enter a future Actual Departure Date. If Allow Future Ship Date in the Shipping Parameters form, Shipping Transactions tabbed region, is cleared, do not do so as you receive an error. If Allow Future Ship Date is selected, you receive a warning and the Inventory Interface concurrent process does not process the transaction until the actual departure date.

 Enable the Create Bill of Lading box if you want to create a Bill of Lading. This generates a Bill of Lading number and prints it if it is part of a document set. 

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. o If you enable the Defer Interface box and run Ship Confirm, you need to run the “Interface Trip Stop“SRS concurrent request to update the Inventory and the Order Line status. When the Defer Interface box is enabled, a request is not automatically submitted to interface the trip stops.

Creating Invoices: Invoice Generation Sources  Imported through other legacy systems & other Oracle applications automatically by AutoInvoice Interface program.  Entered Manually in Receivables module. Information to Customers  Invoices (Can be single or Consolidated) are sent to Customers through Post, E-mail & EDI Transmission

114

OM Standard Header Workflow:

OM Standard Line Workflow:

OM Standard Line Workflow:

115

ing entries in the cycle:

 At pick release - Staging subinventory Dr.  

To Picking subinventory Cr. At Ship confirm - COGS Dr. To Material Cr. After import into AR- Receivables a/c Dr. To Revenue a/c Cr. To Tax a/c Cr.

Tables that get updated:

• • •

• • • • •

• • •

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

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, applications you build, applications on other computers, and even the applications of your suppliers and customers. Basic Business Needs Oracle Manufacturing product APIs and open interfaces provide you with the features you need to the following basic business needs:  Connect to data collection devices. This lets you collect material movement transactions such as receipts, issues, quality data, movements, completions, and shipments. This speeds data entry and improves transaction accuracy.

116





   

Connect to other systems — such as finite scheduling packages, computer-aided design systems, custom and legacy manufacturing systems — to create integrated enterprise wide systems. 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. Control processing of inbound data imported from outside Oracle applications. Validate imported data to ensure integrity of Oracle Manufacturing products. Review, update, and resubmit imported data that failed validation. Export data from Oracle Manufacturing products

RMA Flow Overview RMA is often used synonymously with Return or Credit Orders and Returned Material. An order can have a mix of outbound (regular) and inbound (return) lines, if not restricted by the order type definition. Credit order types have an order type category Return and an order with mixed order type category can contain both regular and return lines. Each order type and each line type is associated with a workflow process. A return line is indicated by Line Type and by its negative and highlighted item quantity and line total price. Line types can be variations of Return, such as Return with Approval, Return for Credit only, etc., and have a line type category of RETURN. There are three ways to create RMA’s within Order Management. First, identify a sales order to be returned and query the order lines. 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. Second, reference a sales order, invoice, PO number or serial number of an item directly in the Return Reference field within the Line Items tab of the Sales Order form. Lastly, for return without originating sales order line, manually enter return line information and choose the appropriate return line type in the Sales Order form. Process Flow This section will guide you through a basic flow for a Return for Credit with Receipt, from entry to generating a credit memo, including: 1. Create an RMA having a single line whose originating transaction is unknown 2. Book the RMA After booking the order: Order Status – Booked Order Line Status - Awaiting Return 3. Receive the RMA using the Receipts form of Oracle Purchasing 4. Check the on-hand quantity of the item in Inventory to that correct quantity was received. Checked the Order Status as Order Status – Booked Order Line Status – Returned 5. Run Workflow Background Process 6. Run ‘Auto Invoice Master Program’ to generate a credit memo 7. View the Credit Memo in Order Management 8. Check the Shipped and Fulfilled quantity on the RMA line

117

Enter the RMA on the Sales Order form. Entering a return on the Sales Order form, is exactly the same as entering an order, except at the line level where the specifies the Line Type as a Return and a negative line quantity and total quantity appear on the form. Thus, in the Order Information tab of the Sales Order form, the will enter the same information (i.e. Customer Name, Order Type, etc.) 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. Refer to the Workflow section for details on the Generic Order and Line workflow for returns. Figure 6–1 is the Sales Order form for entering the Header information for the RMA:

Once the Order Header information is entered, you will enter the line information within the Line Items screen, as seen in Figure 6–2 :

118

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

119

120

6. Check the on-hand quantity of the item in Inventory to that correct quantity was received. Change responsibilities to Inventory and navigate to the Transactions > Material Transactions form. In the Material Transactions form, an Organization window will be displayed if this is the first time you have navigated to the Inventory > Material Transactions form since your . The organization you choose should be the same warehouse where your RMA is created. Find the item name being returned and navigate to the Transaction Type tab. that the source type is RMA and the source is your RMA # for the quantity being returned. This form will show you your item #, the subinventory chosen and the quantity specified to be returned from the Receipts form.

7. Fulfill RMA line. The fulfillment activity acts as a synchronization point for all lines on the order that are in a fulfillment set. The lines in the fulfillment set will wait at the fulfillment activity until all the lines in the set have reached the activity. Lines that are not in a fulfillment set simply through the activity automatically. The will not have to perform anything during this step. The eligible lines will automatically be put into a fulfillment set. 8. Generate a credit memo for the return. The Workflow process of the return line(s) will be on the Invoice Interface activity, once the Fulfillment activity completes. The invoice interface activity places the information from the return line into the Receivables Interface tables. Once the information is written to the tables, the invoice interface activity is complete, and the line proceeds to the close line activity. However, note that the credit memo is not actually generated until the Autoinvoice program in Receivables has been run. The credit memo will then be viewable in the Sales Order form. To run the Autoinvoice program, the needs to change responsibilities to Receivables and navigate to the Interfaces form. 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 Autoinvoice Master program will generate the Autoinvoice Import program which generates the credit memo.

121

9. View the credit memo in Order Management. To view the credit memo in Order Management, the need to change responsibilities to Order Management > Orders, Returns > Order Organizer form. Query your RMA # in the Order Organizer. Once the RMA is queried, select the Actions button and choose Additional Order Information. Once the Additional Order Information form has opened, click on the Receivables tab to view the credit memo. This form will show your the credit memo number and amount. 10. Check the Shipped and Fulfilled quantity on the RMA line. From the above step, navigate in the Sales Order form to the Line Items tab for the RMA. Scroll to view the Shipped Quantity field. To access the Fulfilled Quantity field, the needs to use the folder technology to add the field to the sales order form. To add the field, click on the Warehouse field in the Shipping Tab of the Line Items form. Next, select the Folder menu at the top of the form, select Show Field and choose the Quantity Fulfilled field from the list. The field will populate in the form. The Shipped Quantity means the received quantity for return lines and the Fulfilled Quantity means the delivered quantity for the return lines. Implementation Steps: # Order. 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.  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, 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. 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.

122

#

N – Orders. Returns – Sales Order

Order Information - Main Tab:  Choose the Customer Name and Choose the Customer Number  Relating to Customer fields information is displayed automatically Ship-to, Bill to Locations, Date Ordered, Price List, Sales Person, Status, Currency, Subtotal, Tax, Charges and Total  Choose the Order Type Others Tab:  Automatically comes with the Customer name or Customer number you have Chosen Payment , Warehouse, Freight , Shipping Method, FOB, Tax handling Line Items - Main Tab:  Enter the Item number, automatically the UOM will come.  Enter the quantity in qty column automatically the Unit Selling Price will come.  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.  The status is “Awaiting Shipping” #

N – Shipping – Release Sales Order - 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, Auto allocate, Auto pick confirm, Sub Inventory

123

   

#

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.

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. 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. (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.

124

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. An Internal Requisition is initiated in Oracle Purchasing. Sourcing rules can automatically determine if the source type is to be Inventory or an external supplier. 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), the requisition can be received to record receipt of goods. The Source Type attribute on the requisition line controls whether a line will be fulfilled internally or purchased from a supplier. A source type of Inventory indicates an internal order. Order Management is seeded with an Order Source of Internal, to identify lines created from internal requisitions. The internal requisition id is stored in the Original System Reference column on the order header of the Internal Order. It is not possible to manually enter Internal Orders using the Order Management interface – these orders must come in via Order Import.

Requesting Org (M1) will place the order request on Source Org (M2). So, 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

Process Steps: 1) Enter Requisition in Oracle Purchasing. Sourcing Rules may set source type attribute to Inventory, or manually choose Inventory source type. 2) Approve the Internal Requisition.

3) Run the Create Internal Sales Order concurrent program in Purchasing to load the Order Import tables (OE_IFACE_HEADERS_ALL, OE_LINES_IFACE_ALL). This can also be scheduled as part of your set up to run periodically to meet business needs.

4) Run Order Import with Order Source = Internal in OM to create the Internal Order. Be sure to run Order Import using a responsibility that corresponds to the operating unit in which the internal order needs to be created. It is possible to create an internal order in an operating unit different from that of the internal requisition. This can also be scheduled as part of your set up to run periodically to meet business needs.

5) After Order Import completes successfully, query the sales order. Observe that Order Status = BOOKED Line Status = Awaiting Shipping 6) Pick Release

7) Ship the Internal Order. 8) Receive against the Internal Requisition.

a) Go to the Destination Organization in purchasing application b) Receive the Goods from Purchasing Application. 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,*Stock able, Transact able, Revision Control Receivable, 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, Customer Enabled, Shippable, *Internal Order, *Internal Order Enabled, *OE Transact able, Assemble To Order, 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

• • •

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. Returns – Import Orders – Order Import Request Order Source : Internal Order Reference : Give the Requisition Number Validate only : take default Instance : take default

# • •

•

Orders. 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.SEGMENT1) PO_REQUISITION_LINES_ALL -- PO Requisition Line After running 'Create Internal Order' data loads into OE Interface Tables OE_HEADERS_IFACE_ALL -PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID gets stored in OE_HEADERS_IFACE_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.REQUISITION_LINE_ID) RCV_SHIPMENT_HEADERS

127

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. Order Management sends information to the Purchasing Application to create that PO, and then when that PO is received (to indicate shipment from the supplier to your customer), the order line is automatically updated to indicate that it was fulfilled. In this process, 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, to indicate that we are defining the process from this point of view. 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; kits and models cannot be drop shipped at this time. 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, 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, and automatically default the source type of External for order lines which need to be drop shipped

Process Steps

128

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

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. Enter Sales Order with Order Line Source Type is set to External. 2. Book the sales Order. 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, the seeded workflow “Line Flow – Generic” will process drop shipment lines. The Create Supply - 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 - Deferred.

130

4. The Purchase Release concurrent program processes eligible lines with a source type of External and es information to Oracle Purchasing. The Purchase Release process is initiated to write records to the PO_REQUISITIONS_INTERFACE_ALL table.

5. 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. 6. Create PO from the approved requisition by submitting the request ‘Autocreate’ 7. Approve PO 8. Send PO to the Supplier 9. Supplier Ships the goods and sends the Advanced Shipping Notices (ASN) to the Purchasing System 10. 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, Logically inventory will updated 11. Deliver the Goods to Inventory. Inventory is incremented. Observer that Order Status = Booked Line Status = Shipped 12. Call OM to notify that the Line is fulfilled. OM Decrements Inventory. Marks the line as Shipped and progress the line. 13. Run Workflow background process 14. Run AutoInvoice Program.

Order Management Responsibility #

Orders. Returns – Sales Order

131

• • • •

#

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, 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

#

Inventory – Transactions - Receiving – Receipts

• • • #

• #

Select the Source Type = “Supplier” Query with the Purchase Order Select the line and give the stores name and Save the form, Logically inventory will updated

Orders. 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, 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.

< End of Drop Shipment Order Flow  > ONT Tables: Table Name OE_SYSTEM_PARAMETERS_ALL

OE_TRANSACTION_TYPES_ALL

Purpose This table is used for storing all system parameter information. Currently the only system parameter in Order Management being Item Validation Organization, this table stores the information of Validation Organization for different operating units. This table stores information about the order and line

133

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 tables stores the names of feeder systems from which you import sales order data(order headers, order lines, sales credits) into Order Management. 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. This table stores information of the hold source criteria. This tables stores information about all the holds that has been released. This table stores information of all the orders and lines that are on hold and the link to hold sources and hold releases. 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. This table stores the information about all the actions that are applicable to the sales order. Each row includes the name of the action, flag to indicate if the action is displayed as default button and the folder object name. This table stores the information about, all the actions that are assigned to a folder. Each row includes the name of the action, flag to indicate if the action is displayed as button, folder object name, access key, prompt name. This table is used for generating invoice numbers based on the delivery name. This table stores pricing attributes and asked for promotions, deals and coupon number entered by the . This table stores information on qualifiers and pricing attributes, which to that corresponding price adjustment line qualified for. Stores the order details for orders included in a purge set. This table stores information about sales credits. Stores history of attribute changes of Entity Sales Credits. This table stores information about sales credit types.

Shipping (WSH) Tables: Inventory Tables (INV): Table Name

Purpose

MTL_ABC_CLASSES

MTL_ABC_CLASSES contains information about ABC Classes. Each row in this table defines an ABC Class. An ABC Class is a category under which items with similar metrics are put together. The Compile ABC Analysis form allows the to specify the criterion to be

134

MTL_ABC_COMPILES

MTL_CATEGORIES_B

used for defining such metrics. A given ABC Class can be used in more than one ABC Group, but not more than once in a given group. MTL_ABC_COMPILES stores information about each item within an ABC compile. Each row includes an item's sequence number relative to other items within the given compile, based on the compile criteria defined in MTL_ABC_COMPILE_HEADERS. Each row also contains an item's compile quantity, compile value, cumulative quantity, and cumulative value. Oracle Inventory uses this information to provide an ordered sequence of items, to which the can then assign an ABC Class. MTL_CATEGORIES_B is the code combinations table for item categories. Items are grouped into categories within the context of a category set to provide flexible grouping schemes. The item category is a key flexfield with a flex code of MCAT. The flexfield structure identifier is also stored in this table to the ability to define more than one flexfield structure (multi-flex). Item categories now multilingual category description. MLS is implemented with a pair of tables: MTL_CATEGORIES_B and MTL_CATEGORIES_TL. MTL_CATEGORIES_TL table holds translated Description for Categories.

MTL_CATEGORY_SETS_B

MTL_CC_SERIAL_NUMBERS

MTL_CC_SUBINVENTORIES

MTL_CROSS_REFERENCES

MTL_CATEGORY_SETS_B contains the entity definition for category sets. A category set is a categorization scheme for a group of items. Items may be assigned to different categories in different category sets to represent the different groupings of items used for different purposes. This table is used to store serial numbers associated to a cycle count entry involving a serialized item. This table is used only when the has selected the serial control option "Count: Multiple Per Request" in the corresponding cycle count header. 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 table is not used if the cycle count is at organization level. Oracle Inventory uses this information in the automatic scheduling feature of cycle counting and for validation purpose when schedule requests are manually entered. MTL_CROSS_REFERENCES is used to assign crossreferences to items. The cross reference type code identifies the cross-referencing identification system being used. The cross-reference identifies the specific relationship between the item and the other identification system. This can include references to an old item

135

MTL_CROSS_REFERENCE_TYPES

MTL_CUSTOMER_ITEMS

MTL_DEFAULT_CATEGORY_SETS

MTL_DEMAND

MTL_DESCRIPTIVE_ELEMENTS

MTL_ITEM_ATTRIBUTES

MTL_ITEM_CATALOG_GROUPS_B

identification scheme, to supplier item identification, etc. Each inventory item can be assigned any number of cross-references for any number of crossreference types. 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. This can include references to an old item identification scheme, to supplier item identifications, etc. Each inventory item can be assigned cross-references using any number of cross-reference types. MTL_CUSTOMER_ITEMS stores customer item information for a specific customer. Each record can be defined at one of the following levels: Customer, Address Category, and Address. The customer item definition is organization independent. MTL_DEFAULT_CATEGORY_SETS stores the identifier of the category set that acts as the default for a particular functional area. 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. . 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. For example, the category set for the Inventory functional area is mandatory (and defaults) for all items defined as Inventory items. This ensures that for a given functional area, there will be a category set that contains all of the items for that functional area. This table stores demand and reservation information used in Available To Promise, Planning and other Manufacturing functions. There are three major row types stored in the table: Summary Demand rows, Open Demand Rows, and Reservation Rows. MTL_DESCRIPTIVE_ELEMENTS stores the descriptive element definitions for an item catalog group. Descriptive elements are defining properties used to describe in the catalog group. MTL_ITEM_ATTRIBUTES table stores information on item attributes. Each row in the table corresponds to an attribute. The table stores the attribute name, the corresponding -friendly name seen by the s, and the kind of validation enforced on the attribute. MTL_ITEM_CATALOG_GROUPS_B is the code combinations table for item catalog groups. An item catalog group consists of items that can be described by the same set of descriptive elements or item properties. When an item is associated with an item catalog group, the item inherits the descriptive elements for that group which then behave like additional item attributes. The can specify values for the descriptive elements and can use that information to search for items

136

MTL_ITEM_CATEGORIES

MTL_ITEM_LOCATIONS

MTL_ITEM_LOC_DEFAULTS

MTL_ITEM_REVISIONS_B

MTL_ITEM_STATUS

using the Item Search window. MTL_ITEM_CATEGORIES stores inventory item assignments to categories within a category set. For each category assignment, this table stores the item, the category set, and the category. Items always may be assigned to multiple category sets. However, depending on the Multiple Assignments Allowed attribute value in a given category set definition, an item can be assigned to either many or only one category in that category set. MTL_ITEM_LOCATIONS is the definition table for stock locators. The associated attributes describe which subinventory this locator belongs to, what the locator physical capacity is, etc.. The locator is a key flexfield. The Flexfield Code is MTLL. MTL_ITEM_LOC_DEFAULTS contains the optional default locators for shipping and receiving purposes. The LOCATOR_ID and SUBINVENTORY_CODE identify the exact locator/subinventory which one wishes to have as default. The DEFAULT_TYPE indicates whether it is the default shipping or receiving subinventory/locator. Also see MTL_ITEM_SUB_DEFAULTS. MTL_ITEM_REVISIONS stores revision levels for an inventory item. When an item is defined a starting revision record is written out to this table, so every item will at least have one starting revision. The presence of an engineering change notice code in this table indicates that the engineering system issued the revision through the implementation process. Along with the engineering change order, an implementation date and initiation date will be stored. MTL_ITEM_STATUS is the definition table for material status codes. Status code is a required item attribute. It indicates the status of an item, i.e., Active, Pending, Obsolete. 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.

MTL_ITEM_SUB_DEFAULTS

MTL_ITEM_SUB_INVENTORIES

The values of the individual status attributes associated with an item status are stored in MTL_STATUS_ATTRIBUTE_VALUES. 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, Oracle Shipping Execution, and Oracle Purchasing respectively. DEFAULT_TYPE indicates whether the subinventory is meant for default shipping or receiving. MTL_ITEM_SUB_INVENTORIES maintains a listing of subinventories assigned to an inventory or engineering item.

137

These subinventories make up the list of valid subinventories when transacting this specific item and the has specified (in the master window) that the item must use subinventories restricted to a pre-defined list.

MTL_ITEM_TEMPLATES

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

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

138

MTL_PHYSICAL_INVENTORIES

MTL_PHYSICAL_SUBINVENTORIES

MTL_RESERVATIONS

MTL_SALES_ORDERS MTL_SECONDARY_INVENTORIES

MTL_SECONDARY_LOCATORS

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

MTL_SERIAL_NUMBERS

You can also specify whether this subinventory is an expense or asset subinventory (ASSET_INVENTORY), or whether quantities are tracked (QUANTITY_TRACKED). MTL_SERIAL_NUMBERS stores the definition and current status of all serial numbers in Oracle Inventory. These serial numbers are also used in other areas of Oracle Manufacturing.

139

MTL_SYSTEM_ITEMS_B

A serial number can have one of four statuses: - Defined but not used - Resides in stores - Issued out of stores - Resides in intransit MTL_SYSTEM_ITEMS_B is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. You can specify item-related information in fields such as: Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning, MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing. You can set up the item with multiple segments, since it is implemented as a flexfield. Use the standard 'System Items' flexfield that is shipped with the product to configure your item flexfield. The flexfield code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. Therefore, the same item can be defined in more than one organization.

Shipping Tables: Table Name WSH_CARRIERS

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

Purpose ***** Warning: Oracle Internal Use Only ***** Oracle Corporation does not access to Oracle applications data using this object, except from standard Oracle Applications programs. WSH_NEW_DELIVERIES has the delivery records. WSH_DELIVERY_ASSIGNMENTS assigns delivery details to a delivery and/or a parent delivery detail (LPN). WSH_DELIVERY_DETAILS has delivery lines and LPNs. 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). WSH_DELIVERY_LEG_DETAILS stores pick-up/drop-off information for each delivery line of a delivery leg. WSH_TRIPS has trip records. WSH_TRIP_STOPS has trip stop records. WSH_FREIGHT_COSTS records freight costs. ***** Warning: Oracle Internal Use Only ***** Oracle Corporation does not access to Oracle applications data using this object, except from standard Oracle Applications programs. This table stores the list of all the partner ITM Applications. WSH_PICKING_RULES has picking rules for defaulting Pick Release options. WSH_PICK_GROUPING_RULES has grouping rules for Pick Release.

140

Oracle Receivables Tables: Table Name HZ_CUST_S HZ_CUSTOMER_PROFILES

HZ_CUST_ACCT_SITES_ALL

HZ_CUST_SITE_USES_ALL

HZ_LOCATIONS

HZ_PARTIES

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

141

{{"bodytext"}}Party records can be created and updated using third party data sources such as Dun & Bradstreet's Global Data Products. The HZ_PARTIES table contains demoralized information from the HZ_LOCATIONS, HZ_PERSON_PROFILES, HZ__POINTS, HZ_ORGANIZATION_PROFILES, and HZ_PERSON_LANGUAGE tables. The identifying address contained in the HZ_PARTIES table is demoralized from the HZ_LOCATIONS table. 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. One location can optionally be used by one or more parties. For example, 500 Oracle Parkway can be specified as a party site for Oracle Corporation. This party site can then be used for multiple customer s within the same party. The HZ_PARTY_SITE_USES table stores information about how a party site is used. Party sites can have multiple uses, for example Ship-To and Bill-To.

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__B RA__LINES RA__LINES_DISCOUNTS RA_TERRITORIES RA_ADDRESSES RA_BATCHES RA_GROUPING_RULES Table Name HZ_PARTIES HZ_CUST_S

Description Information about parties such as organizations, people, and groups Customer information

HZ_CUST_ACCT_SITES HZ_PARTY_SITES

Links party to physical locations

HZ_CUST_SITE_USES

HZ_LOCATIONS

Physical addresses

Columns PARTY_ID PARTY_NUMBER PARTY_NAME CUST__ID PARTY_ID _NUMBER CUST_ACCT_SITE_ID CUST__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

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

Oracle Receivables - Key Flex Fields: Key Flex Field Short code Sales Tax Location RLOC Flexfield Territory Flexfield CT# Oracle General Ledger- Key Flex Fields: Key Flex Field Short code ing Flexfield GL# Reporting GLAT Attributes:in

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

AutoInvoice Overview AutoInvoice is a powerful, flexible tool you can use to import and validate transaction data from other financial systems and create invoices, debit memos, credit memos, and on- credits in Oracle Public Sector Receivables. You use a custom feeder program to transfers transaction data from an external system into the AutoInvoice interface tables. AutoInvoice then selects data from the interface tables and creates transaction in Receivables. Receivables rejects transactions with invalid information to ensure the integrity of your data. With AutoInvoice, 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- credits  Calculate taxes for the imported transactions, or the tax through the tables  Correct errors easily online Create invoices from the following Oracle applications: – Oracle Order Management

143

– – –

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.  AutoInvoice requires mandatory grouping on the transaction attributes Currency Code and Bill-To Customer (only one of each attribute is allowed per invoice).  Receivables automatically applies these required grouping rules to any additional transaction attributes assigned to the grouping rules.  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. 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

 

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, 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, debit memos, and credit memos.  Line ordering rules can be assigned to each grouping rule.  AutoInvoice uses transaction attributes in the line ordering rules to order invoice lines based on the priority defined.  An ascending or descending order for each transaction attribute assigned to a rule can also be specified. 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. Transactions include invoices, debit memos, credit memos, and on- credits.  Each record contains line, tax, freight, or finance charges information.  The Line_Type field identifies the type of information contained in the record.  A record can be a parent record: Line, Header Freight, or Charges; or a child record: Tax or line-level Freight.  A child record is linked to the parent record using the Link-To Transaction flexfield. RA_INTERFACE_DISTRIBUTIONS Table  This table contains ing distributions to be used by the transactions defined in RA_INTERFACE_LINES.  s defined in this table override any s created using Autoing.  Choose to some or all information to AutoInvoice. Any s that are not ed will be derived using Autoing.  Records in this table are linked to records in the RA_INTERFACE_LINES table using the Transaction flexfield.  Not required if Autoing determines GL distributions. RA_INTERFACE_SALESCREDITS Table  This table contains all sales credit information for the transactions in the RA_INTERFACE_LINES table.  The two tables are linked using the Transaction flexfield.  Not required if not tracking sales credit. Order Import in Oracle Order Management: Status of Orders Orders can be imported as ENTERED, BOOKED or CLOSED. ENTERED: If an order is imported with an entry status of ENTERED (OE_HEADERS_IFACE_ALL.BOOKED_FLAG=N or NULL) then the result after import is that the line is BOOK_ORDER eligible.

145

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’.  By ing the action request to the OE_ACTIONS_IFACE_ALL table, i.e. in the OE_HEADERS_IFACE_ALL do not the BOOK_FLAG and in the OE_ACTIONS_IFACE_ALL table put operation code as BOOK_ORDER. 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. There is a difference between closing an existing order and importing orders in "CLOSED" status the first time itself. 3. As orders were already closed in the old system, there will not be any changes performed to the records, which means no defaulting. 4. All the book required columns need to be ed for importing a Closed Order, 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, 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. If only the line is to be cancelled, 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. Also the operation code to be used for cancellation should be ‘UPDATE’ . 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'. Then since the line cancelled_flag is also 'Y' it tries to cancel the already cancelled line and errors out. So depending on whether the order or the line is to be cancelled, the cancelled flag and the header information or the line information should to be loaded. Notes: Freight costs can be modified after Ship Confirm. However, the modified costs will only be included on the customer invoice if OM Interface has not yet run (previously called Update Shipping). Once you have run the OM interface, you can no longer modified freight cost information back to OM. You can still modify freight costs, but you won’t be able to the information to OM. Transfer of Reservations to Cycle Count: During pick release, if the notices a discrepancy between physical inventory and system inventory, then the missing quantity may be transferred to cycle count within the Shipping Transactions form using the Actions button. When the unavailable quantity is in cycle count, 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. This functionality requires adding the security privilege Cycle Count Delivery Line. Over/Under Shipments A quantity greater than the quantity on the line is allowed if it is within the over-shipment tolerance. If it is greater than the over shipment tolerance, a warning will be given, but the will not be stopped from shipping the additional quantity. The actual quantity shipped is recorded on the line. The Under-Shipment tolerance behaves differently. At ship confirm, any quantity less than the requested amount is allowable. If the quantity shipped is within the under-shipment tolerance, the line will close once the shipment is processed. The remaining quantity will automatically cancel.

146

However, if the quantity shipped is outside the tolerance, the line will split into 2 lines, one line represents the quantity shipped, the other line becomes a backordered line with the difference. Over Picking The over picking enhancement s 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, which is a natural extension to the over shipping feature.

o It allows the to prevent breaking LPNs or lots by small amounts when the quantity requested does not match the quantity in inventory. For example, if the customer orders five cans, the warehouse has only six-packs, and the warehouse either is out of individual cans or has a policy against loose cans. The over picking functionality allows the picker to pick a 6-pack (6 cans wrapped) to fulfill the order, instead of picking exactly 5 cans. Inventory Flexfield:

147

Inventory And Order Management 244f2a

Overview 5o1f4z

More details 6z3438

Related Documents c2h70

Inventory And Order Management 244f2a

Capacity Management And Inventory Management 1s555o

Stores And Inventory Management z1w4b

Inventory Management 2s1m5c

Inventory Management 2s1m5c

Inventory Management 2s1m5c

More Documents from "Ajay Dogra" 634a42

Inventory And Order Management 244f2a

Ferrous Metal 5k19h

Hematoxylin Stain Its Importance In Histology 5m1k2f

C6-01 Service Manual 1.0 511p17

Mx Road 1b6p4j

Elementary Structural Analysis - By Wilbar Norris(1) 1jf44