You are on page 1of 16

n this Document Goal Solution References

Applies to:
Oracle Purchasing - Version: 11.5.5 to 12.0.6 - Release: 11.5 to 12 Information in this document applies to any platform.

To demonstrate the dropshipment process starting Steps : 1 - Identify internally ordered item and create the Sales Order Using the Seeded Item and Customer 2 - Progress the Sales Order Workflow - and execute the Requisition Import 3 - Autocreate the Requisition into a Purchase Order and Approve 4 - Create the Receipt and confirm the Sales Order Line is now Shipped 5 - Review the Sales Order Line - confirm it is Closed - view Invoice

Utilizing the Oracle E-Business Suite - Vision Demonstration Database - it is possible to create a Drop Ship Sales Order using the following steps below, upon logging in as CHORTON/welcome. Two responsibilities will be used during the demonstration: - Purchasing, Vision Operations USA - Order Management Super User, Vision Operatoins 1. Login using the CHORTON username, and proceed to the Order Management Super User, Vision Operations. Navigate - Orders,Returns -> Sales Orders

Choose the Customer as 'Business World'. All information will default - next choose the Line Items tab.

Enter the Item CM51563, enter a quantity and the price will default.

Chose the Shipping Tab - confirm the Source Type is External. Book the Order in question. Exit the form. NOTE: External - means that the sales order will utilize the Purchasing Application to pursue ordering this Item, as the actual inventory is not maintained on-hand.

2 - Within the Order Management Super User, Vision Operations Navigate - Reports,Requests-> Run Requests - Submit the Workflow Background Process - The parameters above can be utilized. By Default the Order Line workflow gets deferred, so this step is necessary.

The next step is to engage the Purchase Release process. - Pass in the Operating Unit and the Drop Ship Sales Order number - Hit OK and ensure it completes This process is responsible for inserting data into the po_requisitions_interface_all table.

SQL Developer can be used to confirm that the data was in fact properly inserted. Example SQL: select * from po_requisitions_interface_all where trunc(creation_date) = trunc(sysdate);

The data which was inserted, must now be imported into Purchasing - using the Requisition Import Program. It is possible to run the Requisition Import Program either from Purchasing or Order Management. The parameters above should be used when importing the requisition, most important of the parameters being Input Source. _______________________________________________________________________________ __

Moving to Purchasing, Vision Operations USA Navigate - Requisitions-> Requisitions Summary - Enter the import source of ORDER ENTRY in the find form. - Give the creation date as todays date - as seen above - Choose Find

The requisition is located and has been imported as Approved. Order Management inserts the status as Approved, so all drop ship requisitions are created as Approved.

3 - Using the Purchasing Responsibility, Navigate to the Autocreate form. Navigate: Autocreate (it is directly off the main menu path) - Search for the requisition (possibly choose clear in the find form and then search) - Locate the requisition line and select it for Autocreate - Choose the Automatic Button - A default supplier will appear - proceed to choose 'Create'

The Purchase Order is created and the reference to the Sales Order is visible. Action should be taken to Approve the purchase order.

It should also be noted that the Ship To is the Customer Ship To - on the Purchase Order. __________________________________________________________________________

4 - Using Purchasing, Vision Operations, USA

Navigate: Receiving/Receipts Upon entering the form choose M1 as the Inventory Organization - This was the inventory organization used on the Purchase Order Shipment Enter the Purchase Order number and then choose Find A line is returned, ensure destination type is Inventory (it will default) - Enter a Subinventory of Stores and then Save The receiving process is essentially used to confirm that the goods have in fact reached the Ship To address, which is in-turn the Customer. ______________________________________________________________________________ Back to Order Management Super User, Vision Operations - Orders,Returns/Orders - Query on the Sales Order that was used and view the status of the line

Notice that the status is Shipped. The Receiving process has communicated to the Sales Order workflow that the product has been received - which essentially means that the product has been shipped to the customer by the Supplier.

Again, choose Reports,Requests-Run Requests from the Order Management Responsibility. - Execute the Workflow Background Process - The parameters above can be used At this point, the Sales Order Line workflow is again deferred awaiting the Background Process.

5 - With a run of the Workflow Background process, the Sales Order workflow is engaged and the result is the Sales Order line is now Closed.

Choosing Actions/Additional Information - it is possible to see the invoice.

Choosing the Invoices/Credit Memos - the invoice can be viewed. ____________________________________________________________

The above image is an overview of what has taken place in this drop ship example. _____________________________________________________________________ The following sql can be used to find drop ship purchase orders - within the Vision Operations operating unit. SELECT prh.segment1 req_num, prh.INTERFACE_SOURCE_CODE, prl.line_num req_line_num, poll.line_location_id po_line_loc_id, poh.segment1 po_blanket_num, poh.org_id org,, oed.line_location_id oe_line_loc FROM po_requisition_headers_all prh, po_requisition_lines_all prl, po_line_locations_all poll, po_headers_all poh, oe_drop_ship_sources oed, hr_all_organization_units hr WHERE prh.requisition_header_id = prl.REQUISITION_HEADER_ID AND hr.organization_id = poh.org_id AND prl.line_location_id = poll.line_location_id AND poh.po_header_id = poll.po_header_id

AND oed.line_location_id = poll.line_location_id AND poh.org_id = 204 ORDER BY poh.creation_date DESC;