Transfer of Delivery Line

Reservations to Cycle Count

An Oracle White Paper
November 2001

Transfer of Delivery Lines to Cycle Count

EXECUTIVE OVERVIEW
This document describes the new action of transferring delivery line quantities to Cycle
Count in Oracle Shipping Execution. Until now, the Shipping Execution application
removed the reservations for backordered lines and returned the reserved quantity to
available inventory. The benefit of this new action is that a user has the option to
transfer the reservations on a Pick Released item to Cycle Count and simultaneously
backorder the delivery line quantity which helps keep available system inventory
accurate.
INTRODUCTION

Maintaining an accurate accounting of shippable inventory is important for all

businesses. In Release 11i, Family Pack G, transfer of delivery lines to cycle count
is introduced so that the shipping staff can better manage discrepancies in
inventory balances. As unexpected situations occur while staging orders in the
warehouse, such as, an item is damaged or physical inventory is out of balance with
system inventory, then shipping staff can transfer a quantity to Cycle Count so
that future reservations cannot be placed against that quantity.
BUSINESS NEED

Prior to the availability of the cycle count feature, if you backordered any quantity
from a delivery line, then that quantity became available within inventory for future
reservations and there was no means of blocking out that quantity to prevent
future reservations. The result was that the shipping staff might try to fulfill an
order with the same missing quantity infinite times until accounting made a special
effort to adjust the system inventory for this item. For example, assume the
available system inventory equals 20 and you have a delivery line with a requested
quantity of 20 but physical inventory is depleted after picking a quantity of 17. In
this situation, the shipping staff would use the new cycle count functionality to
transfer the reservation for three missing items into cycle count so that available
inventory balance in the system remains at zero. Cycle count functionality allows
this type of adjustment for inventory reservations.
Enabling Cycle Count in Roles and Users Security

To use this functionality, you must have the Roles and Users security privilege for
Cycle Count Delivery Line. This security privilege appears on the Shipping
Execution Role Definition form, Lines/LPNs tabbed region and may require the
assistance of your system administrator.

White Paper Title

Page 1

Navigate to: Shipping > Setup > Grants and Role Definitions > Grants
Within the Shipping Execution Grants form (as shown above), query your user
name to verify which role(s) you have been assigned. By placing the cursor on the
line with the role you wish to view and clicking on the View Role button, you can
see the Role Definition form shown below.

White Paper Title

Page 2

At the Lines/LPNs tab, the Cycle Count Delivery Line must be checked and the
Data Access field set to edit before the cycle count feature will appear in the
Shipping Transactions form for your use. NOTE: if your current Role, as defined
by this form does not have the Cycle Count feature enabled, then a new role must
be created and assigned to you. The system will not allow you to enable this
feature within the current role. For additional information, see Roles and Users
Security white paper on Metalink.
Transferring Lines to Cycle Count

The cycle count feature is available through the Shipping Transactions form. By
specifying a quantity in the Shipping Transactions form, you create a backorder for
the entire quantity, or a partial quantity of the delivery line. The Shipping
Transactions form transfers the reservation for the backordered quantity to a new
category in inventory called cycle count.
Cycle counting can only be performed on a pick released delivery line. In other
words, the line status must show as staged. If any other line status appears on the
delivery line, then you must progress the delivery line before attempting to use the
cycle count feature.
There are two forms that can be used for transferring delivery lines to Cycle
Count:
1.

Transfer to Cycle Count form

2.

Confirm Delivery form

Using the Transfer to Cycle Count Form to Transfer Delivery Lines

The Transfer to Cycle Count form is new in Family Pack G. If the security
privilege was correctly setup as described earlier, then you can access this new
form by placing the cursor on the target delivery line and, in the Action menu,
select Cycle Count and click the GO button.
As an example, if you are processing a staged delivery line with quantity 10, and 2
of the items are damaged while being moved, then you may want to transfer 2
delivery line items to cycle count. In the Transfer to Cycle Count form enter the
quantity to cycle count and click OK.

White Paper Title

Page 3

After you click OK to submit this information, the cycle count functionality:

Splits the delivery line into two delivery lines, one with quantity eight and
one with quantity two.

Leaves the delivery line with quantity eight as a staged delivery.

Backorders the delivery line with quantity two and transfers its reservation
to cycle count (in the background).

NOTE: The Secondary area in the Transfer to Cycle Count form is inactive and
intended for future use.

You can transfer the entire quantity in the delivery line to cycle count, or any part
of the quantity. However, you cannot transfer more than the delivery line quantity
to cycle count.
Using the Confirm Delivery Form to Transfer Delivery Lines into Cycle Count

You can also transfer delivery quantities to cycle count during ship confirmation by
specifying either:

Cycle count all (the entire quantity), or

Cycle count unspecified quantities

To cycle count all the quantity on the delivery line select the delivery tab and at
Actions menu select ship confirm to display the confirm delivery window. In the
Ship Options area, select the radio button for Cycle Count All then click OK, as
shown below. The result is that the entire reserved quantity for the delivery is
transferred to cycle count and the delivery line status is changed to backordered.

White Paper Title

Page 4

To cycle count unspecified quantities you use a two-step process. This

functionality assumes that you want to group any quantity not shipped and
transferred the line quantities into another status (staged, backordered, cycle
counted). First, in the Lines/LPNs tab, you enter a Shipped Quantity equal to or
less than the Requested Quantity. In the example shown below, two delivery
lines each containing a requested quantity of 20 are being transacted. A Shipped
Quantity of 16 is manually entered in the first delivery line, and a shipped quantity
of 20 is entered in the second delivery line.

White Paper Title

Page 5

Secondly, in the Delivery tab, Actions menu, you select ship confirm and GO. In
the Confirm Delivery form, if you select Ship Entered Quantities and in the
Unspecified Quantities LOV select Cycle Count (as shown below) then when you
ship confirm only the Shipped Quantity is confirmed. The balance of delivery
lines, where the Shipped Quantity was less than the Requested Quantity will get
backordered and the reservation for that quantity will transfer to cycle count.

Results of this action are shown on the following screen shot of the Shipping
Transactions form.

White Paper Title

Page 6

When the ship confirm occurs, then five events are kicked off for this example.
1.

The partially filled delivery line splits into two lines (77544 & 77546).

2.

The fulfilled portion of the delivery line (77544) is ship confirmed.

3.

The unfulfilled delivery line (77546) quantity of four is backordered.

4.

Simultaneously, a quantity of four is transferred to cycle count

reservations (occurs in the background).

5.

The delivery line receiving its requested quantity (77545) is ship

confirmed.

Viewing Line Quantities Transferred to Cycle Count

You can view the reservations transferred to Cycle Count for each item by
navigating to: Inventory > On-hand Availability > Reservations. Within this form,
accounting staff can periodically review the cycle count inventory, adjust inventory,
and clear these reservations, as necessary. Note: As of this writing, the table for
cycle count was not seeded in the application (cycle count is missing from Demand
Type LOV). See bug 1801422.

Using Other Features with Cycle Count

When transferring delivery line reservations to cycle count, the user needs to
understand what impact, if any, other active features will have in response to the
transfer. The other features mentioned in this section include: serial numbered
items, ship sets and ship models.
Transferring Serial Numbered Items to Cycle Count

When you transfer delivery line reservations to cycle count and the line items are
serial numbered, then the cycle counting function does not consume the serial
number. The serial number is returned to the pool so that the number can be
reused.
In other words, when the delivery line is backordered during the cycle counting
process, the serial number is not transferred with the reservation to cycle count

White Paper Title

Page 7

and the serial number is not attached to backordered line item(s).

The serial number is returned to the serial number pool regardless of how the
serial number generation feature is set up (e.g. At Receipt, At Sales Order Issue, or
Predefined) within the master item inventory.
Transferring Ship Sets and Ship Models to Cycle Count

Transferring reservations to cycle count that include part of a ship set or a ship
model should cause a warning message to appear that acknowledges that this
action will break the ship set if you proceed. However, as of this writing, the
warning message is not popping up. Reference bug 2026895.

White Paper Title

Page 8

White Paper Title

November 2001
Author: Timothy Conroy
Contributing Authors:
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
Web: www.oracle.com
This document is provided for informational purposes
only and the information herein is subject to change
without notice. Please report any errors herein to
Oracle Corporation. Oracle Corporation does not
provide any warranties covering and specifically
disclaims any liability in connection with this document.
Oracle is a registered trademark of Oracle corporation.
All other names may be trademarks of their respective owners.
Copyright Oracle Corporation 2000
All Rights Reserved