BRPF Number:

BRPF Name:

NON Serialization

Domain:

ERP

Application:

ERP
Udit Garg

List of Contributors
Project Manager / Email ID:

Dhiraj Shivaji
Business SPOC:

Dipti Kanta
Tarun Kandwal
Vivek Sharma
Vimal Singh

Udit Garg/20-aug-15
Prepared by/Date

Reviewed by/Date

Approved by/Date

Revision History
Versio

Date of

Description of

Reason for

Affected

Revision

Change

Change

Sections

(x.y.y)

Affected Groups

List of Reference Documents

Name

Version No.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 2 of 20

Approved By

Table of Contents
YTERMS AND ABBREVIATIONS...............................................................................................4

STAKE HOLDER MAP...............................................................................................................4

REFERENCES...............................................................................................................................4
1

OBJECTIVES....................................................................................................................... 5

SCOPE................................................................................................................................. 5

SYSTEM REQUIREMENTS..................................................................................................5
3.1

SOLUTION DETAIL...............................................................................................................5

3.2

SOLUTION ARCHITECTURE...................................................................................................5

3.3

DATA ARCHITECTURE/FLOW................................................................................................6

3.4

USER INTERFACE REQUIREMENT.........................................................................................6

3.5

ASSUMPTIONS....................................................................................................................6

3.6

DEPENDENCIES (IF ANY):....................................................................................................6

3.7

VOLUMETRIC......................................................................................................................6

3.8

NON FUNCTIONAL REQUIREMENT........................................................................................6

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 3 of 20

3.9

UAT ACCEPTANCE CRITERIA...............................................................................................7

INTERFACES....................................................................................................................... 7

HARDWARE AND SOFTWARE REQUIREMENTS..............................................................7

5.1.1

Development Environment: / Testing/Staging Environment......................................7

5.1.2

Production Environment:..........................................................................................7

5.1.3

Software and Utilities:..............................................................................................8

APPENDIX A:....................................................................................................................... 8

1.1 TERMS AND ABBREVIATIONS

Acronym

Description

1.2 Stake Holder Map

Stakeholders

Email

CONFIDENTIAL/INTERNALLY RESTRICTED

Role

Page 4 of 20

Vivek Sharma

Vivek.sharma@uninor.in

Uninor IT SPOC - PM

Ajay Sikarwar

Ajay.Sikarwar@uninor.in

Uninor IT - Arch. Head

Dhiraj Shivaji

Dhiraj.shivaji@uninor.in

Dipti Kanta

Dipti.kanta@uninor.in

Uninor Business (SCM)

Tarun Kandwal

Tarun.kandwal@uninor.in

Uninor ERP head (Fin)

Udit Garg

Udit.garg1@wipro.com

Wipro Business Analyst

Anil Khanna

anil.khanna@wipro.com

Wipro Architect

Rajeev Gupta

rajeev.gupta@wipro.com

Wipro Delivery Manager

Uninor Business
(Finance)

2. Objectives
The objective of the document is to derive high-level solution that will be implemented for NON SERIALIZED INVENTORY as a
part of business requirement.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 5 of 20

3. Scope

In ERP System transaction of some items i.e RCV AND SUK are serial wise and the transaction occurs in huge amount (crores
in case of RCV).The ERP systems performance is not meeting the business users expectation and the system is being often
reported slow.CPU Utilization for DB Servers is already reaching 70%-90% levels. Unless we switch to Non-Serialized Inventory
in ERP, there is an immediate requirement for adding 2 cores to each DB Server to improve CPU utilization and performance. So
there is major impact on ERP which takes a lot of time in GRN and Shipping.
3.1

Out-of-Scope

Below Requirements are out of scope.

SL
#
1.

Requirement
Kitting removing process

Remark
1. Kitting is just a way to differentiate
between RAW SIM and FIN GOOD
SIM.
2. Its change the item to be shippable.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 6 of 20

System Requirements

Requireme

Requirement Description

Solution Description

nt Id
1

Certain finished goods item codes need to be replaced by

Item attribute (Serial control generation): NO CONTROL.

new item code as serial control needs to be removed.

Item attribute (Lot control generation) will remain as it is.

New item code needs to be defined in price list.

New item code needs to be defined the item in the price list

which is attached to the customer.

3

On-hand quantity of old items (in scope items) to new items

Custom program needs to be developed for On hand

need to be transferred based on serial number range basis.

quantity transfer. On hand quantity will be transferreds all the

transactions will be performedto on new item codes through

GRN process of RCVs and SUKs based on serial range

basis.

Miscellaneous OUT and IN.

Serial Number range will be entered with Lot Number
transaction as Additional information during doing the
GRN.
Start number will be entered by user and end number
will be automatically populated based on lot quantity.
In the system only serial number range will be
Maintained. Individual serial numbers will not be
maintained in system.
As the DFF is enabled at lot number line level it should
be ensure that DFF doesnt impact on other items which

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 7 of 20

are not part of scope.

During SUK kitting, rather than entering lot and serial

Parent and child relationship of new item code will be

number as currently, only lot number and serial number

defined in BOM

range (in DFF) is to be entered.

JOB creation and move transaction process will remain

same.
During complete transaction (of finished goods item),
serial number range will be given at lot number line level
captured in DFF. Lot number needs to be entered as
currently.
WIP material transaction of child item will be based on
serial number range captured in DFF. Lot number needs
to be entered as currently.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 8 of 20

Shipping of item based on serial number range basis.

Move order transacts will based on lot number and DFF

Validation during shipping to ensure that no shipment is

will be enabled for serial number start/end range.

allowed if serial number range falls in- between already

Shipping file send to DMS will consist only of serial

shipped serial numbers for same item.

number range. DMS will split the range into separate

Assumption: For two different RCVs serial number cant

serial numbers.

be same.

Validation for serial number range that has been already

shipped. Same serial number cannot be shipped again.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 9 of 20

Internal sales order process.

During the move order transact process, lot and serial

number range (in DFF) will be captured.
GRN file based receiving in ERP of internal organization
now will consist of lot and serial number range captured
in ERP.
Shipment file to ARMS will go changes as now only
serial number range will be sent.
Daily sales from COCO will go changes as now
associated Oracle GRN will have serial number in DFF.

Inter org transfer based on shipment number.

Inter org transfer of item from source to destination org

(Warehouse to warehouse transfer).

will perform on lot and serial number range basis.

GRN in destination org will also perform on lot and serial
number range basis.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 10 of 20

RMA comes from DMS.

Two scheduled programs Uninor OM interface new for

Validation of serial number.

RMA and order import creates sales order having

negative quantity.
For each individual item RMA serial number from and to
value remain same.
Validation for duplicity of serial number in RMA needs to
be performed here as now serial numbers are not
available in the system. (Please note this process is for
RMA in new item codes. For old item codes, requirement
3 has details)

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 11 of 20

10

RMA transaction from COCO.

COCO return files interface to ERP through loader

program
This RMA will now be performed on serial number range
basis.
For each individual item serial number range will be
same.
Validation for duplicity of serial number in RMA needs to
be performed here as now serial numbers are not
available in the system. (Please note this process is for
RMA in new item codes. For old item codes, requirement
3 has details)

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 12 of 20

11

Reconciliation from RA team.

Uninor RA Sales Data, Uninor RA On hand Data

and RMA query, these process sends the data to RA
team. That has serial number range.
Format of reports will remain same as only serial number
range is sent to RA team. But these reports will need
changes as range will be picked up from DFF now.

12

Old item codes need to be removed from its price list.

After new item code has been defined, old item code
needs to be removed from price list to make sure that it
is not available for further use.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 13 of 20

4.1

Solution Details of Requirement

4.2 Solution Architecture

Solution will be responsible for following functionalities
New item code will be created for every old item code respectively.
New item code need to define in the price list.
On hand quantity will be migrated from old item to new item code having serial numbers in DFF field.
GRN and Shipping process will be based on serial number range given in the DFF at time of move order transact.
For SUK item new BOM will be created with respect to the new item codes.
WIP Material transaction of parent and child items will be based on serial number range maintain at DFF level.
Internal sales order and inter org transfer will process will be remain same except serial number range will be maintained at
DFF at lot number line level.
RMA of new item code will be based on serial number range and required a custom validation as of now serial number is not
maintained for items.
RMA of old item will be based on serial number as of current process but for ensuring this that it is not purchasable and
customer

ordered

attribute

(PURCHASED/PURCHASBLE,

CUSTOMER

ORDERED

/CUSTOMER

ENABLED,INTERNAL ORDERED) of old item need to be change as it is not purchasable and customer ordered.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 14 of 20

ORDERS

4.3 Data Architecture/Flow

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 15 of 20

4.4 User Interface Requirement

Data flow from DMS system need to be perform by user.

Each and every scenarios need to be checked by user.

Customization of transaction form need to be checked properly.

4.5 Assumptions
1. DFF will be mandatory and non-mandatory for which item.
2. Before transferring the on hand quantity in new item code there should not any pending transaction of
that item.
3. Unhand quantity to be transferred will be based on on hand report provided by SCM team.
4. All POs need to be closed of old items.
5. No pending GRN.
6. Pending kitting need to be closed.
7. New item code And its mapping with old item code to new item will be provided by SCM team
8. RMA of old item code will be based on serial number basis.
9. Old item code will not be disabled until and unless there is no further transaction on it.

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 16 of 20

4.6 Dependencies (If any):

1. Business has to provide list of items that are serial control and will now be non-serialized
2. Business has to provide new code list mapped with the old items.

4.7 Volumetric
N/A
4.8 Non Functional Requirement
Operational Requirement : N/A
Usability Requirements: Yes
User & Application Documentation Requirements : Yes
Security Requirements to comply with UNINOR IS policy been captured? Yes, as per IA confirmation.
Performance Requirements: Yes, PR submission time should not be increased by more than 30 seconds from the
present one.
Availability Requirements :No
System Capacity and Scalability Requirements: Yes
Efficiency Requirements: Yes
Maintainability Requirements: No
CONFIDENTIAL/INTERNALLY RESTRICTED

Page 17 of 20

4.9 UAT Acceptance Criteria

Provided by business

1. Interfaces

Name

No
1

DMS

Direction

Mode/

Purpose and other details

Protocol

In

Po flow in ERP

2. HARDWARE AND SOFTWARE REQUIREMENTS

6.1 Development Environment: / Testing/Staging Environment

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 18 of 20

Server Name
Server Location
Operating System
License
Hardware Configuration
Software & Version
Owners of the System

GNNMIH81
GNDC
Solaris 10
Sun Server
R12(12.1.1) & 11G(Database) 11.1.0.7
ERP

6.2 Production Environment:

Server Name
Location of the Server
Operating System
License
Hardware Configuration
Software and Version
Owners of the System

GNNERP01,02
GNDC
Solaris 10
Sun Server
R12(12.1.1) & 11G(Database) 11.1.0.7
ERP

6.3 Software and Utilities:

Application Server
Database
License
Web Server
Protocols Used for transactions

Oracle Application Server 10G

11G , 11.1.0.7
10G

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 19 of 20

External Interfaces

3. Appendix A:

CONFIDENTIAL/INTERNALLY RESTRICTED

Page 20 of 20