Below post will give you the details about the pick release status

Instance: 11i or R12

Table: WSH_DELIVERY_DETAILS

Column: RELEASED_STATUS

Possible Values:

B: Backordered- Line failed to be allocated in Inventory

C: Shipped -Line has been shipped

D: Cancelled -Line is Cancelled

N: Not Ready for Release -Line is not ready to be released

R: Ready to Release: Line is ready to be released

S: Released to Warehouse: Line has been released to Inventory for processing

X: Not Applicable- Line is not applicable for Pick Release

Y: Staged- Line has been picked and staged by Inventory

Delivery line statuses in detail

Not Applicable (Code X)

The delivery line can be invoiced but non-shippable, for example, a service line or a

warranty line.

Not Ready for Release (Code N)

The delivery line is not eligible for pick release. This happens when the order line is

manually imported into Oracle Shipping Execution using the Import Delivery Line

concurrent process or the corresponding order line has not reached the Awaiting Shipping

workflow activity.

Ready for Release (Code R)

The delivery line is eligible for pick release. Occurs when the order line has reached the

Awaiting Shipping workflow activity (it is booked, scheduled, and in Oracle Shipping

Execution).

Submitted to Warehouse (Code S)

Pick release has processed the delivery line and has:

1.       Created move order headers and lines.

2.       Found available quantity and created inventory allocations.

3.       Not pick confirmed. If you are using auto-pick confirm, it changes release status to Staged.

If you are not using auto-pick confirm and want to progress the delivery lines, navigate to

Oracle Inventory Move Order Transaction window and perform manual pick confirm.

Staged (Code Y)

The delivery line is pick confirmed; inventory is transferred from storage sub-inventory to

staging sub-inventory. It remains staged until ship confirm.

Backordered (Code B)

Some of the circumstances that can causes this status are listed below

  Pick release has processed the delivery line and cannot find the entire quantity. This

typically occurs when the Oracle Inventory indicates that there is not enough material

(either because there is not enough material or because the inventory balance is incorrect).

  At ship confirm, you: Enter Shipped Quantity that is less than Original Requested Quantity

Backorder the entire delivery quantity transfer a reservation to cycle count.

  This typically occurs when the material that you want to ship:

1.       Has become unavailable, for example, damaged, between picking and shipping.

2.       Is available and you backorder material for specific business reasons. For example, all

available material has been allocated to a specific customer when you find out additional

supply for other orders will be delayed.

Shipped (Code C)

The delivery line’s delivery is ship confirmed and posted as in-transit, OM Interface and

Inventory Interface have processed, and the trip is closed.

Cancelled (Code D)

The order line that the delivery line supports is cancelled.

What is Release Rules in Oracle apps?

Release Rules define the criteria to be used during Pick Release. Only orders which meet the criteria and are eligible will be Released. An Order line is eligible if it has completed the prerequisite workflow activities, such as Schedule - Line or Create Supply.

What is meant by Release Sequence Rules in Oracle apps?

Release Sequence Rules determines the order in which inventory is allocated to sales orders. Users can choose to allocate by order, outstanding Invoice value, Scheduled Date, Departure Date & Shipment Priority.The order in which sales orders are filled could be very important. If a company has a problem of running out of material before all of their orders have been filled it is very important that they have filled their most important orders first.

What is meant by Picking Rules?

Picking Rules, which are created and maintained in Inventory, suggests which material to use, based on inventory controls such as Revision control, Lot control, FIFO (first in first out) or subinventory/locator picking numbers.

Picking Rule is an Item Attribute. Create a variety of picking rules and associate them with the appropriate items. If there isn’t a Picking Rule associated with the item, the system will use the Organization’s default Picking Rule which is found on the Shipping Organization’s Parameters.

Note: Picking Rules are covered in Inventory. To learn more see Inventory’s users guide.

What is meant by Pick Slip Grouping Rules?

Pick Slip Grouping Rules organize how released order lines are grouped on Pick Slips for ease of picking. For Example: By using the Pick Slip Grouping Rule "Sub-Inventory" the user can reduce the number of trips to a particular subinventory by grouping all lines for that sub-inventory on to one Pick Slip.

What Happens during Pick Release ?

A pre-approved Move Order is automatically created in Inventory. A Move order is a request for a subinventory transfer from the source (stocking)

subinventory to the destination (staging) subinventory.

A Move order is created for every Sales Order Line that has the status of “Awaiting Shipping” and passes the picking criteria (Use your Release Rules to guide this process).

The Destination subinventory is the Staging subinventory entered on the Release Sales Orders form or defaulted from the Shipping Parameters. Only one staging subinventory is allowed per Picking Batch.

Note: A Picking Batch is the total number of Order Lines that were released at one time.

Inventory uses the move order to manage material requisitions within an Organization.

Other options During Pick Release

Allocate Inventory to the move order Allocating can be done automatically after the move order is created by setting “Auto

Allocate” to yes on the Release Sales Order form or postponed until later, then manually allocated from the Transaction Move Orders form.

The Release Sequence Rule, that was entered on the Release Sales Orders form, or defaulted from the Shipping Parameters, will be used to determine in what sequence to fill the move orders.

Move orders use inventory’s picking rules to suggest the material that should be allocated. The sourcing values for subinventory, locators, revisions, and lots are defaulted on to the move order.

Serial Numbers can be allocated if the profile option: INV: Detail Serials = “Yes”. If it is set to “No” serial numbers can be entered before Pick Confirm from the Move Orders form or after Pick Confirm from the Shipping Transaction form.

The source defaults can be manually updated from the Transaction Move Orders form.

A high level reservation is placed for the Move Order’s material requirements.

Allocating inventory is a prerequisite for printing Pick Slips. The Pick Slip Grouping Rule entered on the Release Sales Orders form or defaulted from the Shipping Parameters is used while printing pick slips.

Pick Confirm the move order

Pick Confirm can be done automatically during the picking process by setting “Pick Confirm” to yes on the Release Sales Orders form or by unchecking the Pick Confirm Required checkbox in the Organization Parameters form. If it is not done automatically during pick release it can be done manually from the Transaction Move Orders form by selecting the Transact button.

The Pick Confirm transaction executes the subinventory transfer, moving the material from it’s source location to it’s destination staging location. Only 1 staging subinventory is supported per picking batch.

The high level reservations are replaced with detail reservations.

Note: A high level reservation puts a reservation on a given quantity. For example if the sales order line needs ten 12” Monitors and you have 15 on hand, the reservation will guarantee that 10 of them will be available for this order but it doesn’t specify which 10. Detail reservations puts a reservation on specific subinventory, locator, revision, and lot number.

If you transact less than the requested quantity, the Move Order will stay open until the total quantity is transacted, or the order is closed or cancelled.

The status of the Sales Order Line, which is linked to the Move Order, is changed to “Picked” making it eligible for Ship Confirm.

If not all of the Move order quantity was transacted the status of the Sales Order Line, is changed to “Picked Partial”. During Ship Confirm the order line will split into 2 shipment schedules (e.g. 1.1 and 1.2). The status of the unfilled line will be changed to “Awaiting Shipping”.

If there is a shortage of material a shortage messages alerts the appropriate individual.

If an organization’s actual picks rarely deviate from the suggested material, it is suggested that you run your picking process with Auto Allocate and Pick Confirmed set to Yes to cut down on the overhead which is required to transact manually.

Auto Create Deliveries - Optional A delivery is required in order to Ship Confirm. You can select to have the Picking process

automatically group your delivery lines into deliveries to expedite this process.

http://knoworacle.wordpress.com/2008/12/08/data-flow-for-11i-order-to-cash-cycle/

http://www.shareoracleapps.com/2010/07/interview-questions-pick-release.html

Scheduling and Booking Submitted by Anonymous on Fri, 01/16/2009 - 21:53

Tag:

Order Management

/

Scheduling is a means of communicating the balance between customer demand and a company’s ability to fulfill an order from current inventory and supply sources.  Order scheduling is managed differently from company to company – and Oracle Order Scheduling supports a variety of scheduling environments.

The scheduling feature of Oracle Order Management (OM) enables you to determine when items will be available to promise to a customer(ATP), schedule the shipment or arrival of order lines based on this availability(Schedule), and reserve on-hand inventory to sales order lines(reservation) SO, the features that are provided under the umbrella term of scheduling are:■ Calculating Available-to-Promise (ATP)■ Scheduling ( Populate dates - ship and arrival schedule dates)■ Create demand (Makes demand visible to planning)■ Reserving (Reserves the line items if the due date is within the reservation time fence)■ Sets the ship from■ Calculates the delivery  lead  time based  on as  ship  method (if you have set up a shipping network)

Scheduling is an action performed on an order line or a group of lines. The action performs the following:

Determines the source (warehouse) for the order line. If the warehouse is entered on the line, either manually or using defaulting rules, the scheduling action uses the requested warehouse and the other scheduling results are based on it. If the warehouse is blank, the scheduling action determines the best warehouse based on the sourcing rules. This functionality includes ATO models.

Determines the schedule ship date, the schedule arrival date, the delivery lead time and the shipping method.

Makes the line visible to the planning applications and consumes supply for the item. When a line is successfully scheduled the VISIBLE_DEMAND_FLAG is set to Yes.

If the reservation time fence is set and the schedule ship date is within the  reservation time fence, automatically reserves the line.

Scheduling ProcessSales order line would be scheduled for both the ATP as well non-ATP items based on the availability of the item. When scheduling is not performed during sales order entry (either manually or automatically), then as part of standard functionality, scheduling will be done by the workflow process.

Scheduling is done by the workflow process associated with the order line (OEOL). For example: Considering the Line Flow – Generic work flow Once the order is Booked, the work flow completes the Booking activity and proceed to the next stage i.e. Scheduling. This is when Scheduling is performed.Open the process ‘Line Flow - Generic’ in the Workflow Builder. The ‘Line Flow - Generic’ process looks as below

   Order will wait at “Wait for Booking” till booking action is performed. The work flow will progress to next stage.- Double click on the 'Schedule - Line' sub process in 'Line Flow - Generic' process. Double clicking opens 'Schedule - Line' sub process which looks as below

Once the line is scheduled, SCHEDULE_SHIP_DATE is populated into the OE_ORDER_LINES_ALL.The SCHEDULE_SHIP_DATE should be a value between the REQUEST_DATE and the LATEST_ACCEPTABLE_DATE.

Scheduling sets the VISIBLE_DEMAND_FLAG, SCHEDULE_STATUS_CODE as soon as the lines are scheduled. The two columns are independent and are not based on the setups

 

Scheduling by Ship or Arrival DateThe request date may be either the requested ship date or the requested arrival date depending on the request date type of the customer. If the customer's request dates are requested arrival dates, the scheduling action calls MRP's scheduling API with the requested arrival date. The API returns the first date on or after the requested arrival date that the items could arrive at the customer location, and enters that date into the scheduled arrival date field for the line(s). The schedule ship date is calculated by subtracting the delivery lead time (number of days for items to reach the customer once they ship) from the schedule arrival date. If the shipping network has not been defined for this combination of locations, the delivery lead time will be considered zero days and the schedule ship date and schedule arrival date will be the same.

If you enter a schedule ship date on the order line before performing the schedule action, the system will attempt to schedule on that date when the schedule action occurs. If it cannot, the schedule action fails.

You can define for each customer the delivery window in days that they will accept by entering the latest schedule limit on the customer window. When you enter an order line, the latest

acceptable date is calculated by adding the latest schedule limit to the request date. When the scheduling action occurs, the schedule date will only be returned if it is between the requested date and the latest acceptable date. If it is not within this range, the scheduling action fails. For example, suppose that you have a customer who only accepts orders that ship within 5 days of the request date. You would enter 5 in the latest schedule limit fields on the Order Management tab of the customer window. When you enter an order line, if the request date is September 10, the latest acceptable date would be September 15. When the scheduling action occurs, if the schedule date returned is not in the date range of September 10 through September 15, the schedule request fails.

You can control whether OM schedules lines on hold by using the profile option OM: Schedule lines on Hold. If an order or line is on hold and this profile option is No, then the scheduling action fails.

Alternative Ways to ScheduleThe scheduling action can be invoked in multiple ways.

1. You can schedule from the sales order window by having autoschedule turned on,2. You can schedule a line by manually choosing to schedule using the context menu or the

tools menu.

3. You can schedule using a workflow activity either immediately or in deferred mode.

If the scheduling action fails in the workflow then the line is moved to scheduling eligible activity. You can then use the Schedule Orders concurrent program to schedule the lines with exceptions.

AutoscheduleThe sales order line is scheduled when it is saved. If either the Autoschedule check box on the order transaction type is checked or the OM: Autoschedule profile option is Yes, the sales order will be opened in Autoschedule mode.

You can turn Autoschedule on or off from the sales order window by going to the Tools menu. Note that if autoscheduleis turned on the availability window is automatically displayed when the sales order window is opened. You can close the availability window, but the lines will still be autoscheduled unless the autoschedule check box on the tools menu is unchecked.

ManualYou can access the scheduling sub menu either by selecting schedule from the list of activities on the tools menu or by placing your cursor on a line and pressing the right mouse button. Selecting schedule from these menus will trigger the scheduling action. If the action is selected from the

order header tab, all the lines on the order will be scheduled. If the action is selected from the lines tab, it applies only to the line or group of lines selected.

If the profile option MSC_OM_IMPORT_PRESCHEDULED is set to Yes, then you will be able to schedule ATO items on weekends as well. However if you require the scheduling to be done only on valid working days, set this profile option to No.

WorkflowThe seeded scheduling workflow activity should be used in the workflow process for your order lines. In the Line Flow - Generic seeded flow, the schedule activity is a synchronous activity immediately after booking. With this type of process, scheduling will occur immediately after booking. Scheduling errors will be seen by the person who is booking the order.If the scheduling activity is deferred it will occur after the workflow background process runs and any error messages will be available in the process messages window. Only lines waiting at the Schedule-Eligible workflow activity are selected. The default is no value entered. Note that the lines may or may not be scheduled and still could be waiting at the activity.

Manual Scheduling Sub-ProcessIn Release 12, a new scheduling sub-process named Schedule-Line, Manual is provided to handle cases where you may want to control scheduling manually after the order is booked. If the new sub-process is used in the line workflow, then after booking the order, lines are blocked at the Schedule-Eligible activity. You can progress the Schedule-Eligible activity from Sales Orders window or use the Schedule Orders concurrent program to schedule the lines.

A new generic line workflow is not provided with this new sub-process. If you require to use this sub-process you can copy and customize the generic line workflow and replace the new sub-process in place of the existing Schedule – Line sub-process.

Schedule Orders Concurrent ProgramThe Schedule Orders Concurrent Program functionality has been enhanced in the current release. This program selects all lines that have failed workflow scheduling, and attempts to schedule them. These lines are waiting at the schedule-eligible activity. The user can select orders based on the order number and other parameters.

In addition, lines that have never been scheduled can now be scheduled using the Schedule Orders concurrent program. This is useful for high-volume orders, where a batch of imported orders in Booked status can be mass scheduled. Please note that lines that have not been booked are not scheduled.

Also the enhancements to the Schedule Orders concurrent program enable you to reschedule lines in case there is a change in supply dates or even unschedule lines if they have been scheduled previously. You have two re-scheduling options: Re-Schedule and Re-scheduling with Request Date. You can query scheduled lines and perform a reschedule. You can move schedules in and out based on the item's availability, and if orders or delivery schedules from suppliers are changed or cancelled, then the allocated product can be rescheduled to meet other demands

earlier or later. You can query and sort scheduled lines, and assign either a new Schedule Ship Date (this can be Schedule Ship Date or Schedule Arrival date; depending on the Order Date Type value) or Warehouse (location) when re-scheduling a line.

For each line of the order that fails workflow scheduling, messages will be stored in the Process Messages table and also printed in the logfile.

If scheduling was successful, the scheduling workflow activity will complete with a result of COMPLETE so that the line can progress to the next activity.

If scheduling was not successful, the workflow activity will complete with the result of INCOMPLETE. The line can then be scheduled manually by progressing the order from the sales order window (press the Action button and select Progress Order) or automatically in the next run of the scheduling concurrent program. Submit the scheduling concurrent program by navigating to (N) Orders, Returns > Schedule Order

Scheduling Across OrdersScheduling Across Orders provides the ability to view scheduling attributes of multiple lines across orders, and to perform any scheduling action from a single window. From the Scheduling tab on the Find window of the Order Organizer, you can query lines based on a variety of parameters, such as:

Item Warehouse

Request Date

Reservation Status (Reserved or Unreserved)

Scheduling Status (Scheduled or Unscheduled)

Shipping Status (Picked, Unpicked, or Backordered)

Order Status

Customer

Shipment Priority

Schedule Date Ranges

Request Date Ranges

After performing an intelligent query to display a group of lines, you will see a new window, Scheduling Organizer. From the Scheduling Organizer, you can perform scheduling actions on lines across orders, that is, you can Schedule, Unschedule, Reserve, Unreserve and perform ATP inquiry.

Access to the scheduling tab is controlled by the Profile Option OM: Scheduling Role. Those with the role of CSR Only do not have access to the Scheduling tab, but they have the same

functionality available in previous releases. Those with the role of Scheduler Only are allowed access to the Scheduling tab, but not to other tabs (Order Information, Line Information, Advanced, and Holds Information). Those with the role of both CSR and Scheduler have access to all tabs in the Find window of the Order Organizer.

Additionally, the role determines whether some actions are available. For instance, those with the role of Scheduler only will not be allowed to open the Sales Order window from the Scheduling Organizer.

Scheduling Across Orders is useful in a variety of business scenarios:• Availability and/or scarce inventory: Who has the reserved items? Which customers have scheduled lines? Which customers have unscheduled lines? If desired, you can take supply away from lower priority customers, and give it to higher priority customers within Scheduling Across Orders.• Customer service: View all the lines for a customer. Which lines need to be scheduled or reserved?• Scheduling: Query all lines that are scheduled to ship on a specific date, and push out the schedule date for those lines as required. Or query any lines where Override ATP is flagged, and decide how to provide supply.• Revenue impact: Query up all lines for an item, and display gross margin. Using Folders, move gross margin to be one of the first three columns on the Scheduling Organizer. Then sort based on gross margin. Reserve the lines with the higher gross margins, and pick by prior reservation. By doing so, you can impact bottom line for a month, quarter, and so on.

Scheduling SetsFor scheduling functions other than Override ATP, Order Management may perform the function on only one line or on that line and a group of related lines. Scheduling treats the following groups as scheduling sets. For these line groups, the scheduling activity occurs on all the lines of a set.

• Assemble to Order (ATO) Models• Ship Model Complete (SMC) Pick to Order (PTO) Models• Line Sets• Ship Sets• Arrival SetsScheduling processes the lines of the set together and applies the rules required to honor the set. If lines are in a ship set they will be scheduled from the same warehouse and will have the same requested ship date and ship to. They may not have the same Shipping Method. For instance, in a PTO model or a ship set you might ship a fragile part using one Shipping Method, and a heavy part using another Shipping Method. User created ship sets, ATO models and SMC PTO models are all ship sets.

All lines in a user created arrival set will have the same arrival date and ship to organization. Lines assigned to an Arrival Set within an order will be scheduled with the same requested arrival date and ship to.

Calculating Available to Promise (ATP)Oracle Order Management enables you to advise your customers when items will be available based on current on-hand inventory plus the expected incoming supply and outgoing demand.

Calculating ATP requires as input the item, the order quantity, the order quantity unit of measure and the request date. In general the user will enter the item and order quantity on every order line. The request date and order quantity unit of measure may be defaulted or manually entered. ATP may be calculated for a single line, a group of lines, or a complete order. The results for a single line are displayed in a single column in a small window. The results for multi-line ATP are displayed in a table

  Warehouse: Either the warehouse on the order line or, if the warehouse on the order line

was blank, the best warehouse as selected by the sourcing rules. Request Date Qty: The quantity that is available on the requested date

Available: The order quantity, if ATP was successful. The available quantity, whichwill be less than the order quantity, if ATP was not successful.

On-hand Qty: The quantity that is currently in the warehouse.

Qty Reservable: The on-hand quantity minus the quantity that is already reserved to other sources of demand.

Request Date: The date on the order line.

Available date: The date that the ordered quantity will be available. It could be the request date if the order quantity is available on the request date, or it might be a future date when the order quantity will be available

Error Message: Any error that occurred in calculating ATP. For example, if the Check ATP flag for the item is not selected then this field will display ATP not applicable.

Substitute Item: If the requested item is not available and the requested quantity for a defined substitute is available, the substitute item will be displayed. An additional tab, showing the availability of the substitute item, is also displayed.displayed for single items. A multi-line window displays availability information for sets and models.

Clicking the Global Availability button located at the bottom of the Availability window opens the ATP window that has the list of warehouses where the item is enabled. You can select the warehouses for which you want to see the availability, andthe system will return the availability in all the selected warehouses.ATP is calculated automatically during scheduling, and may be calculated manually by clicking Availability on the Line Items tab of the Sales Order window. There are several steps required for ATP calculations.

1. Ensure items and options you wish to perform ATP inquires against have the following items attributes properly set:Check ATPATP ComponentsThis includes ATP flag within a Bills of Materials.

2. Ensure that ATP rules have been defined and set. You can define ATP Rules and assign them as defaults at the organization, subinventory, or item level.

3. Define your item Sourcing Rules and any Assignment sets you wish to use. You can define Sourcing Rules within Oracle Supply Chain Planning, Sourcing Rules window. If you do not have Oracle Supply Chain Planning fully installed, you cannot define Sourcing Rules. You may, however, define simple sourcing information at either the item level and the organization levels.

4. Define the Organizations and Application Instance Ids you will wish to collect source ATP data entities from. ATP Inquiries are performed against a common data store within an application instance.

5. Optionally, determine if you wish to enable item substitutions.If you are using ASCP, supply/demand is set up at the plan level.Global Order Promising will only use the infinite time fencespecified on the ATP rule.

If you are using ASCP, supply/demand is set up at the plan level. Global Order Promising will only use the infinite time fence specified on the ATP rule.

If you are not using ASCP, ATP rules must be defined to determine the sources of supply and demand which are included in the calculation. The ATP rules must be associated with items and/or inventory organizations. Also, the data collection program must be run. There is a requirement for ATP calculations to be very fast; some customer service representatives will need to give this information to customers on the phone. However, considering all the possible sources of supply and demand for an ATP calculation can be very complex. Therefore, a concurrent process known as data collection must be run to summarize the supply and demand picture. This program is part of the Oracle Advanced Planning and Scheduling application. The ATP calculation is then performed on the summary tables. For details about setting up ATP rules and running the data collection program, see the setup section of this document.

http://www.oracleug.com/user-guide/order-management/shipping-execution