Efewler

S.No.
Issue
Severity (Client specific)
SKU Coding and sub codes system should allow receiving

by scanning different barcodes available and linking them to
1 the master item code.
Non-Critical
RF screens or Mobile UI should be flexible allow removing

validations that are not necessary with the objective of being
2 as light for the operator as possible.
Critical (Must to Have)
Putaway Pallets & Locators definintion if Pallet dimensions

are not equal to locator dimensions and capacity, system
should suggest another nearest locator in same sub-inventory
and if not applicable move to the next sub-inventory.
Putaway algorithms should be advanced and user friendly to
allow quick on the spot changes, use of logical picking
sequencing and definition of Locators segments (aisle, Bay,
3 Level, Position etc)
LPN Generation will be done per Pallet, where Each Pallet

contains 1 Item & each container can contain multiple of
4 Pallets.
Non-Critical
System or Implementation should include a solution to

handle Drive In type of Storage systems, multi LPNs mixed
5 with different Lots and FEFO information.
Non-Critical
Picking of items against sales order, should be done in

secondary UOM (CRT), where as the pricing will be done
6 with Primary UOM (KG).
Catch Weight concept needs to be used on Receiving and

Picking activities. Catch Weight should work on Primary
UOM (KG) whereas physical UOM handled is secondary
UOM (CRT). Catch weight functionality should allow a
smooth user data entry and updates, on Piece or Pallet level
7 without slowing down the process.
Picking will be done using FEFO rotation, including Shelflife

and specific FEFO overrides. Key account setup should be
available to define Shelflife constraints to apply during Order
8 picking.
Wave or Summary Orders planning should be used to group

orders of different types or criteria (such as expected delivery
dates, priority, key accounts, region or zon etc). As a
control screen, Wave planning should have various KPI or
measures (numeric and graphical) information with export
9 capability to Excel/Pdf.
Work Tasks should be created automatically, and automatic

operator assignment should be tested as it may create
10 difficulties in the Put-away and picking procedures.
Non-Critical
Definition of picking rules should take in consideration the

customer routes, for which different picking attributes needs
to be checked, which includes segregation of items by
11 customer routes.
Non-Critical
Batch or Consolidated picking method will be used mainly to

drive the picking operations. System should drive the
Picking and loading tasks to direct operators to picking and
sort/segregate orders on staging. Process should be smooth
and least scanning/data entry possible to allow fast
12 processing and orders shipping.
Picking Slots and Assignments module should be included,

allows to assign pick slots for SKUs based on variation
sorting/rules. System should also suggest or dynamically
assign/use a pick slot during picking for SKUs to minimize
13 disruption of pickng.
Non-Critical
Cross Docking module should be included for items forward

to pre-defined Orders, in full or partial, flow thru or
14 opportunistic.
Non-Critical
Creation & Printing of Labels with different business flows

should be used intensively to minimize the data entry in
15 hand-held devices
Non-Critical
Automatic holding of items by LOCATORS for any Hold

purpose is a regular transaction for Quality Assurance
16 requirements
Cycle counting and Physical counting processes should be

included with all options and task releasing options
17 requested in warehouses.
Different Coding for LPN to differentiate between LPN for

18 Container and LPNs for Pallets.
Non-Critical
System should automatically segregate the Container LPN

into Default Pallet LPNs according to default number of
Cartons per Pallet at the time of receiving the interorganization transaction to Port Organization to the branch
organization, and we can provide the system with this
19 default number to be used per SKU.
Non-Critical
For Non Oracle WMS, Systems Integration WMS Oracle

ERP: it should include all Interfaces required to pull/push
data onto ERP system. The integration design and
technicality should used straight forward connections means
and allow least supervision and IT maintenance possible
20 (Web Services, APIs, adapters etc)
Building Powerusers skills or Train the Trainer tasks should

be planned in depth to assure most if not all technical skills
transfers to Munajem selected Power users (around 10
21 Powerusers).
Possible Solution
Use GTIN Solution for all the items where multiple codes needs
to be linked to single item, and by scanning the labels for any of
such codes, system will understand which Item is being
referred.
Personalization of the Mobile UI to allow users to view only

those fields which need to be entered. Also since there could be
many UI where users many need this solution, each UI needs to
be reviewed with business to understand what validations they
want to add or remove. Accordingly estimates could be
provided
Putaway rules should be written according to the user

requirement to take care of the requirement, considering the
pallet dimensions and locator dimensions across subinventories
in a ascending order of the pallet dimensions
Customizations and optimal usage of Packing workbench

functionality in eBS.
From the issue, we understand there is a requirement of Drive

in Self storage business process, a custom solution can be
designed to handle this process
This is a concept of Advanced Catch weight. Using Advanced

catch weight solution this can be achieved through proper
pricing.
Advanced Catch weight solution is introduced in R12.2, the

customer should either upgrade to R12.2 or design a custom
solution to handle this requirement
Picking rules need to be written according to the shelf life. If

necessary additional item/serial/lot/ onhand attributes can be
designed to maintain suitable information which can be used in
design of picking rules for suitable picking of items as per FEFO
rotation/shelf life/FEFO over ride for exceptional cases / shelf
life constraints
1. use of oracle WMS Wave planning with suitable

workarounds/tweaking to incorporate all the necessary
conditions
2. Customization to upload the KPIs and parameters through
excel.
Suitable task assignments user defined rules need to be written

to ensure correct task is generated and assigned to the suitable
user with minimum administrator intervention
This can be achieved be writing custom user defined picking

rules. Additionally a suitable solution can be designed to take
define routes and picking attributes which can be used to define
Picking rules
User defined picking/task assignment rules should be written

according to user requirements to handle this business process.
Suitable label generation/automation can be achieved to
achieve proper scanning and avoide much data entry in hand
held device
User defined picking/task assignment rules should be written

according to user requirements to handle this business process
Planned cross docking and opportunistic cross docking features

can be used in Oracle ERP to incorporate this requirement
Label printing is a part of WMS module. The same feature can

be used, however if there are any specific user requirements
which need customizations, same can be looked into,
depending upon the feasibility oracle erg provides
Customization can be designed using the standard oracle

feature of material onhand status.
Item counting process can be incorporated in WMS and can be

performed using mobile device. The solution can be demoed to
the customer if requested.
Can be achieved using customizations of LPN numbering
Customization can be designed to achieve the same through

packing workbench solution, however more discussion needs to
be done to get proper business requirements first before the
solution is designed and finalized.
Discussion with technical consultants and DBAs along with the

project management to ensure the correct process and technical
guidelines are followed to incorporate the given requirements
Train the trainer' program will be used to develop all the

necessary functional skills in the Power users.
Functional tasks
Functional efforts (Man-days)
1. Discussion of the issue with the SME / Key Business Users

2. Understanding the current and future business process
requirements w.r.t. the issue
3. Documentation of the requirements
4. Design of a suitable solution (standard ERP feature, customization,
upgrade or workaround)
5. Review of the solution with SME / Key business users
6. Agreement with key business users on the solution
7. Documentation of the solution, the features of the solution, and the
highlights on necessary steps which are required for the solution
(setups, DFFs, Value sets, custom objects, workflows etc)
8. Demo of the solution to be given to client if possible and with
technical/functional feasibility (additional efforts might be required
here)

here)

here)

here)

here)
12

here)
As per issue 7.
here)
* 2 Days for the demo

of the solution in
R12.2 (non instance
specific)
* 16 Days to design a
solution in R12.0

here)
10

here)
10

here)

here)

here)
10

here)
10

here)
12

here)

here)

here)

here)

here)
10

here)

here)

Efewler

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Efewler

Uploaded by

Copyright:

Available Formats

S.No.

Severity (Client specific)

SKU Coding and sub codes system should allow receiving

RF screens or Mobile UI should be flexible allow removing

Putaway Pallets & Locators definintion if Pallet dimensions

LPN Generation will be done per Pallet, where Each Pallet

System or Implementation should include a solution to

Picking of items against sales order, should be done in

Critical (Must to Have)

Catch Weight concept needs to be used on Receiving and

Critical (Must to Have)

Picking will be done using FEFO rotation, including Shelflife

Wave or Summary Orders planning should be used to group

Work Tasks should be created automatically, and automatic

Definition of picking rules should take in consideration the

Batch or Consolidated picking method will be used mainly to

Picking Slots and Assignments module should be included,

Cross Docking module should be included for items forward

Creation & Printing of Labels with different business flows

Automatic holding of items by LOCATORS for any Hold

Critical (Must to Have)

Cycle counting and Physical counting processes should be

Critical (Must to Have)

Different Coding for LPN to differentiate between LPN for

System should automatically segregate the Container LPN

For Non Oracle WMS, Systems Integration WMS Oracle

Building Powerusers skills or Train the Trainer tasks should

Critical (Must to Have)

Personalization of the Mobile UI to allow users to view only

Putaway rules should be written according to the user

Customizations and optimal usage of Packing workbench

From the issue, we understand there is a requirement of Drive

This is a concept of Advanced Catch weight. Using Advanced

Advanced Catch weight solution is introduced in R12.2, the

Picking rules need to be written according to the shelf life. If

1. use of oracle WMS Wave planning with suitable

Suitable task assignments user defined rules need to be written

This can be achieved be writing custom user defined picking

User defined picking/task assignment rules should be written

User defined picking/task assignment rules should be written

Planned cross docking and opportunistic cross docking features

Label printing is a part of WMS module. The same feature can

Customization can be designed using the standard oracle

Item counting process can be incorporated in WMS and can be

Can be achieved using customizations of LPN numbering

Customization can be designed to achieve the same through

Discussion with technical consultants and DBAs along with the

Train the trainer' program will be used to develop all the

Functional efforts (Man-days)

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

* 2 Days for the demo

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users

1. Discussion of the issue with the SME / Key Business Users