MDS RF Transactions:

1. RF Picking operation.
a)Flow process
b) Business requirements handled
c) Screen layout
2. RF Packing operation.
a)Flow process
b) Business requirements handled
c) Screen layout
3. Inventory counting
a) Flow process
b) Screen layout

MEDSITE SAP R/3 Project

DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 1
MEDSITE RF PICKING OPERATION

(Validates and Confirms Delivery Picking based upon

the Delivery Document)

FLOW PROCESS
The Picking functionality SAP Change Delivery transaction VL02N needs
to be Radio Frequency (RF) and Bar-Code enabled, so that it can be
executed from hand-held devices, containing both mini-terminals and bar-
code scanners, which are not physically connected to SAP terminals.

Since the standard MDE Picking By Delivery ID transaction presupposes the

complete implementation of the Warehouse Management module MDS
developed own custom MDE transaction ZLMPICK, which will use
16x19 input screens.

This transaction is equally capable of the background processing and

updating of SD Delivery screens on the SAP GUI and on the RF-enabled
hand held devices.

The input screen default fields for material numbers and storage bin numbers
(on both of the above platforms) should has an additional line to enable the
entry of both the keyed-in and the bar-code scanned picking
validation/confirmation of both of these fields for each Delivery line.

The defaulted quantity field ( ) for each returned line item is capable of
being changed by keystroke (either on the hand-held device or on the SAP
GUI transaction) before the picking of each line item is confirmed.

Picking confirmation of the line item will take place only after each bin# and
material# have been validates through bar-code scanning (or data entry if RF
is down). This means that each entry field to be validated will have an extra
validation line to receive the scanned information.

MEDSITE SAP R/3 Project

DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 2
BUSINESS REQUIREMENTS HANDLED

The regular picking functionality is designed to allow a partial pick,

where the user enters a pick quantity that is less than the delivery
quantity for a delivery line item. However, even though our custom RF
transaction ZLMPICK will allow partial picking, that would defeat the
purpose of RF-automating the entire delivery process.

The follow-up transaction ZLMPACK will not allow the user to pack if
any line item is not completely picked. In such a case, the user will
manually need to finish the picking (through transaction VL02N on the
SAP GUI) before they can do the RF Packing. The reason for this
restriction is that you can only do background posting of goods issue,
after picking and packing are finished, for a complete delivery. So our
entire automated delivery process must presuppose complete picking
and packing.

SCREEN LAYOUT
MEDSITE SAP R/3 Project
DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 3
 MEDSITE SAP R/3 Project
DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 4
MEDSITE RF PACKING FROM DELIVERY DOCUMENT

(Creates Handling Units for Delivery Packing based upon a

Delivery Document)

FLOW PROCESS
The Packing functionality in SAP Change Delivery transaction VL02N is
Radio Frequency (RF) and Bar-Code enabled, so that it can be executed
from hand-held devices, containing both mini-terminals and bar-code
scanners, which are not physically connected to SAP terminals.

Standard MDE Packing transactions works using the standard developed

custom MDE transaction ZLMPACK, which will use 16x19 input screens.

This program is equally capable of the background processing and updating

of SD Delivery screens from the SAP GUI and from the RF-enabled hand
held devices.

The defaulted quantity field for each returned line item is capable of being
changed by keystroke (either on the hand-held device or on the SAP GUI
transaction) before the packing of each line item into a handling unit
(together with its packaging material) is generated.

BUSINESS REQUIREMENTS HANDLED

Although VL02N will allow you to manually create packing proposals for
items that have not yet been picked, this transaction will never be executed
by Medsite before Delivery Picking (RF transaction ZLMPICK) has been
completed.

Partial picking for each line item in a delivery will be allowed, as the user
can change the picked quantity to a number less than the system-proposed
delivery quantity.

MEDSITE SAP R/3 Project

DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 5
Over all picking status A (not yet picked) or B (incompletely pick) will not
be tolerated for any line item in a delivery that is going to be packed.

RF transaction ZLMPACK will thus only be able to pack for Deliveries

where each line item has been fully picked. It will default the delivery
quantity. That defaulted quantity and unit of measure should not be over-
written.

This transaction is successful only when all materials picked for a delivery
are accounted( each line item wise and per each quantity in line item) and
attached to allowable packaging material to form as many handling units as
needed.
This will allow clipper/ shipper interfaces to return a tracking number that
will later be added to each handling unit number.

The transaction must be capable of handling all combinations henceforth

mentioned in the example.
SCREEN LAYOUT:

MEDSITE SAP R/3 Project

DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 6
 INVENTORY COUNTING

The SAP transactions for Enter Count without Reference to Document

(MI09) is Radio Frequency (RF) and Bar-Code enabled, it can be
executed from hand-held devices, containing both mini-terminals and bar-
code scanners, which are not physically connected to SAP terminals.

Since the standard MDE Physical Inventory transactions presupposes the

complete implementation of the Warehouse Management module,
We have developed our own custom MDE transaction, using the standard
16x19 input screen format.

We have created a custom MDE transaction ZLMINV with a single input

screen, accessible from the custom Medsite RF Menu ZRFMENU.

This program is capable of

1) creating Physical Inventory documents with a single material line item

2) with counts entered on those documents

in a single background process from a single input screen, returning the

count-updated Physical Inventory Document number at the bottom of the
entry screen.

Moreover it is capable of being executed from both the hand-held RF

devices (through the Telnet/Sap console interface) and from a custom
MDE transaction ZLMINV on the SAP GUI, in case the RF Interface is not
available. Also, the entire input screen required entry fields for both the
hand-held and SAPGUI formats.
After the quantity is keyed in and the Enter key is hit, the transaction will be
saved and posted in the background, creating a new Physical Inventory
Document with a singe line item in “already counted” status..

MEDSITE SAP R/3 Project

DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 7
SCREEN LAYOUT:

MEDSITE SAP R/3 Project

DOCUMENT NAME AUTHOR / REVISION ISSUE DATE PAGE
RF transactions Praveen 08.12.2003 8