Sie sind auf Seite 1von 7

PICK RELEASE SHIPPINGRELEASE SALES ORDER RELEASE SALES ORDER

Select a release rule from the Based On Rule list to automatically define the remaining parameters on this window. You can group shipping documents and other reports in a set. You can print document sets when you select a document set in either the Release Sales Orders For Picking or Confirm Shipment windows

Enter a unique name for the batch of orders you want to release. This batch name is printed on all shipping documents. If you leave this field blank when saving the batch, Oracle Order Entry/Shipping automatically assigns a sequential number (batch ID) for you. Attention: You can refer to this batch name when you print the Process Exception Report.

Orders
1. Unreleased Releases all unreleased order lines that meet your criteria. 2. All Releases backordered picking lines and unreleased order lines that meet your criteria. 3. Backordered Releases only backordered picking lines that meet your criteria.

Destination Type

Region- If you select Region as the Destination Type, then click the Destination field and the Select Regions window displays to enable you to find a defined region. Zone Ship-To Location- It can be External Or Internal. If u select Internal Location, then the Destination list of values will contain only internal organizations

If the Enforce Ship Method is checked in the Global Parameters window , a ship method (carrier) need to be entered and recorded for each shipment. If you want to change the Ship Method in the delivery and do not need to enforce it as a grouping attribute, you can deselect Ship Method. Set Autocreate delivery to Yes, such that a shipper/Delivery is automatically created.Check Auto Pick Confirm box for accepting the suggestions given by system and staging the goods at staging subinventory. If you don't want to

use the suggestions made by the system then say Auto pick confirm as "No". Then you need to go to Transact move order screen in Inventory and modify the suggestions made by the system and thus manually pick confirm.

There are two methods for running Pick Release from this window, including the following:

Execute Now: Releases an order, Trip, Trip Stop, or delivery immediately, thus eliminating time spent waiting to process through the Concurrent Manager queue. If this method is selected, however, you must wait until pick release completes prior to running other processes. Concurrent: Releases in the background for multiple orders, Trips, or deliveries, enabling you to run other processes simultaneously.

Make sure to include a Warehouse, based on this the order lines available on the order will be filtered. Choose Auto Allocate as "Yes" such that the system will suggest from which subinventory or locator the goods can be shipped. Global Parameters Window

Select the range of Scheduled Ship Dates and/or Requested Dates. You can indicate whether you want the system to look at the scheduled ship date or the requested date. You can then enter the number of days in the past or future, as well as the time, relative to current system date that you want included in the release criteria. This means that it is possible to set up a desired release window in terms of number of days rather than only static dates. If your organization has a calendar assigned, then the release rule will honor non-working days (for example, Saturday, Sunday) to select delivery lines for pick release. If the rule shown were applied to Organization V1 and that Organization has Saturday and Sunday as non-working days on their organization calendar, then the following would occur: If pick release is run on Thursday, the delivery lines for Thursday, Friday, Monday, and Tuesday (system date + 3 working days) are selected for pick release. A negative value may be used in the Days field to include past dates which enables backordered lines to be considered for pick release. Alternatively, you can create a pick release rule using static dates by selecting the options Start On and End On in the Scheduled Ship Dates region and the Requested Dates region.

Technical Perspective
Pick Release Transactions
WSH_PICKING_BATCHES BATCH_ID NAME TRIP_ID TRIP_STOP_ID DELIVERY_ID DELIVERY_DETAIL_ID BACKORDERS_ONLY_FLAG DOCUMENT_SET_ID EXISTING_RSVS_ONLY_FLAG SHIPMENT_PRIORITY_CODE SHIP_METHOD_CODE CARRIER_ID CUSTOMER_ID SHIP_TO_LOCATION_ID ORDER_HEADER_ID ORDER_LINE_ID WSH_NEW_DELIVERIES DELIVERY_ID NAME PLANNED_FLAG STATUS_CODE INITIAL_PICKUP_DATE INITIAL_PICKUP_LOCATION_ID ULTIMATE_DROPOFF_LOCATION_ID ULTIMATE_DROPOFF_DATE CUSTOMER_ID INTMED_SHIP_TO_LOCATION_ID POOLED_SHIP_TO_LOCATION_ID FREIGHT_TERMS_CODE FOB_CODE FOB_LOCATION_ID WAYBILL WSH_DELIVERY_ASSIGNMENTS DELIVERY_ASSIGNMENT_ID DELIVERY_ID DELIVERY_DETAIL_ID PARENT_DELIVERY_ID PARENT_DELIVERY_DETAIL_ID ACTIVE_FLAG

Query to find out the shipper info :


select wnd.delivery_id delivery_id, substrb(party.party_name,1,50) customer, wpb.name batch_name, wsh_util_core.get_location_description( wnd.INITIAL_PICKUP_LOCATION_ ID, 'NEW UI CODE') ship_from, wsh_util_core.get_location_description( wnd.ULTIMATE_DROPOFF_LOCA TION_ID, 'NEW UI CODE') ship_to, wnd.INITIAL_PICKUP_DATE pickup_date, wnd.ULTIMATE_DROPOFF_DATE dropoff_date, lv.meaning ship_method, wnd.WAYBILL waybill, wnd.GROSS_WEIGHT gross_weight, wnd.WEIGHT_UOM_CODE uom, wnd.status_code, we.message from wsh_new_deliveries wnd, wsh_picking_batches wpb, wsh_exceptions we, fnd_lookup_values_vl lv, hz_cust_accounts cust_acct, hz_parties party where wnd.delivery_id = 12814 and wpb.batch_id = wnd.batch_id and we.delivery_id(+) = wnd.delivery_id and we.exception_name(+) = 'WSH_BATCH_MESSAGE' and lv.lookup_code(+) = wpb.ship_method_code and lv.lookup_type(+) = 'SHIP_METHOD' and lv.view_application_id(+) = 3

Query to find out shipper detail info :


SELECT wnd.delivery_id, wnd.name delivery_name, wdd.source_header_number so_order_number, oola.line_number so_line_number, wdd.source_header_id so_header_id, wdd.source_line_id so_line_id, wdd.shipping_instructions, wdd.inventory_item_id, wdd.requested_quantity_uom, msi.description item_description, msi.revision_qty_control_code , wdd.ship_method_code carrier, wdd.shipment_priority_code priority, wdd.organization_id, wnd.initial_pickup_location_id, wdd.released_status, wdd.source_code FROM mtl_system_items_vl msi, oe_order_lines_all oola, wsh_delivery_details wdd, wsh_delivery_assignments wda, wsh_new_deliveries wnd WHERE wnd.delivery_id =18910 AND wda.delivery_id = wnd.delivery_id(+) AND wdd.delivery_detail_id =

and cust_acct.cust_account_id (+)=wnd.customer_id and party.party_id(+) = cust_acct.party_id /

wda.delivery_detail_id AND wdd.inventory_item_id = msi.inventory_item_id(+) AND wdd.organization_id = msi.organization_id(+) AND wdd.source_line_id = oola.line_id AND wdd.source_header_id = oola.header_id