You are on page 1of 20

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

n

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

...............................................................7 VOLUMETRIC.......... 5 3 SYSTEM REQUIREMENTS..................................................6 DEPENDENCIES (IF ANY):.............................................................................................4 1 OBJECTIVES.......................... 5 2 SCOPE...................1 SOLUTION DETAIL................................................6 3.................................................................................................................................................6 3...............8 NON FUNCTIONAL REQUIREMENT..........................................................................................................................................5 3.................................................................................5 3...............................5 3.........................................................................................................................6 3..............................................................................................................................................................................Table of Contents YTERMS AND ABBREVIATIONS..........................................................................4 USER INTERFACE REQUIREMENT..............................6 3................................................................................................5 ASSUMPTIONS....6 CONFIDENTIAL/INTERNALLY RESTRICTED Page 3 of 20 .......................................................................................6 3.................................................................................................................................................3 DATA ARCHITECTURE/FLOW.........................4 STAKE HOLDER MAP..4 REFERENCES.........2 SOLUTION ARCHITECTURE...................

.......................7 6 5...........3....................................................................... 8 1....7 5......7 4 INTERFACES..............1..................................................9 UAT ACCEPTANCE CRITERIA.....1 Development Environment: / Testing/Staging Environment.........................1 TERMS AND ABBREVIATIONS Acronym Description 1.............................7 5..............................1................................. 7 5 HARDWARE AND SOFTWARE REQUIREMENTS.......3 Software and Utilities:......................................................................2 Stake Holder Map Stakeholders Email CONFIDENTIAL/INTERNALLY RESTRICTED Role Page 4 of 20 ..............................................................................................1.......................................................2 Production Environment:.................................................8 APPENDIX A:...................................................

shivaji@uninor.sharma@uninor.com Wipro Business Analyst Anil Khanna anil.in Uninor ERP head (Fin) Udit Garg Udit.com Wipro Architect Rajeev Gupta rajeev.gupta@wipro.in Uninor IT .Vivek Sharma Vivek. CONFIDENTIAL/INTERNALLY RESTRICTED Page 5 of 20 .com Wipro Delivery Manager Uninor Business (Finance) 2.kanta@uninor.in Dipti Kanta Dipti.kandwal@uninor.PM Ajay Sikarwar Ajay. Head Dhiraj Shivaji Dhiraj. 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.in Uninor Business (SCM) Tarun Kandwal Tarun.Sikarwar@uninor.in Uninor IT SPOC .Arch.garg1@wipro.khanna@wipro.

there is an immediate requirement for adding 2 cores to each DB Server to improve CPU utilization and performance.3. . 3.e RCV AND SUK are serial wise and the transaction occurs in huge amount (crores in case of RCV). Scope In ERP System transaction of some items i. Requirement Kitting removing process Remark 1. 2.CPU Utilization for DB Servers is already reaching 70%-90% levels. SL # 1. Unless we switch to Non-Serialized Inventory in ERP.1 Out-of-Scope Below Requirements are out of scope. Its change the item to be shippable. So there is major impact on ERP which takes a lot of time in GRN and Shipping.The ERP system’s performance is not meeting the business user’s expectation and the system is being often reported slow. Kitting is just a way to differentiate between RAW SIM and FIN GOOD SIM. CONFIDENTIAL/INTERNALLY RESTRICTED Page 6 of 20 .

On hand quantity will be transferreds all the transactions will be performedto on new item codes through 4 GRN process of RCVs and SUKs based on serial range basis.4 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’. quantity transfer. new item code as serial control needs to be removed. Miscellaneous OUT and IN. Start number will be entered by user and end number will be automatically populated based on lot quantity. As the DFF is enabled at lot number line level it should be ensure that DFF doesn’t impact on other items which CONFIDENTIAL/INTERNALLY RESTRICTED Page 7 of 20 . Serial Number range will be entered with Lot Number transaction as Additional information during doing the GRN. Item attribute (Lot control generation) will remain as it is. 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. New item code needs to be defined in price list. Individual serial numbers will not be maintained in system. New item code needs to be defined the item in the price list 2 which is attached to the customer. In the system only serial number range will be Maintained.

are not part of scope. serial number range will be given at lot number line level captured in DFF. JOB creation and move transaction process will remain same. Lot number needs to be entered as currently. 5 During SUK kitting. WIP material transaction of child item will be based on serial number range captured in DFF. rather than entering lot and serial Parent and child relationship of new item code will be number as currently. Lot number needs to be entered as currently. only lot number and serial number defined in BOM range (in DFF) is to be entered. During complete transaction (of finished goods item). CONFIDENTIAL/INTERNALLY RESTRICTED Page 8 of 20 .

Same serial number cannot be shipped again.between already Shipping file send to DMS will consist only of serial shipped serial numbers for same item. be same. number range.6 Shipping of item based on serial number range basis. allowed if serial number range falls in. 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. DMS will split the range into separate Assumption: For two different RCVs serial number can’t serial numbers. Validation for serial number range that has been already shipped. CONFIDENTIAL/INTERNALLY RESTRICTED Page 9 of 20 .

Inter org transfer of item from source to destination org (Warehouse to warehouse transfer). Daily sales from COCO will go changes as now associated Oracle GRN will have serial number in DFF. lot and serial number range (in DFF) will be captured. CONFIDENTIAL/INTERNALLY RESTRICTED Page 10 of 20 . 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. 8 Inter org transfer based on shipment number. will perform on lot and serial number range basis. During the move order transact process. GRN in destination org will also perform on lot and serial number range basis.7 Internal sales order process.

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. RMA’ and ‘order import’ creates sales order having negative quantity. Two scheduled programs ‘Uninor OM interface new for Validation of serial number. For old item codes. For each individual item RMA serial number ‘from and to’ value remain same. requirement 3 has details) CONFIDENTIAL/INTERNALLY RESTRICTED Page 11 of 20 .9 RMA comes from DMS.

For each individual item serial number range will be same. requirement 3 has details) CONFIDENTIAL/INTERNALLY RESTRICTED Page 12 of 20 . Validation for duplicity of serial number in RMA needs to be performed here as now serial numbers are not available in the system. COCO return files interface to ERP through loader program This RMA will now be performed on serial number range basis. For old item codes.10 RMA transaction from COCO. (Please note this process is for RMA in new item codes.

12 Old item codes need to be removed from its price list. “Uninor RA On hand Data” and RMA query. these process sends the data to RA team. old item code needs to be removed from price list to make sure that it is not available for further use. Format of reports will remain same as only serial number range is sent to RA team.11 Reconciliation from RA team. That has serial number range. CONFIDENTIAL/INTERNALLY RESTRICTED Page 13 of 20 . “Uninor RA Sales Data”. After new item code has been defined. But these reports will need changes as range will be picked up from DFF now.

CUSTOMER ORDERED /CUSTOMER ENABLED. 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 old item will be based on serial number as of current process but for ensuring this that it is not purchasable and customer ordered . For SUK item new BOM will be created with respect to the new item codes. attribute (PURCHASED/PURCHASBLE. CONFIDENTIAL/INTERNALLY RESTRICTED Page 14 of 20 ORDERS . On hand quantity will be migrated from old item to new item code having serial numbers in DFF field.1 Solution Details of Requirement 4.INTERNAL ORDERED) of old item need to be change as it is not purchasable and customer ordered.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. 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. GRN and Shipping process will be based on serial number range given in the DFF at time of move order transact.4.

4.3 Data Architecture/Flow CONFIDENTIAL/INTERNALLY RESTRICTED Page 15 of 20 .

3.5 Assumptions 1. 7. 4. 4. 6. DFF will be mandatory and non-mandatory for which item. RMA of old item code will be based on serial number basis. Pending kitting need to be closed. CONFIDENTIAL/INTERNALLY RESTRICTED Page 16 of 20 . New item code And its mapping with old item code to new item will be provided by SCM team 8.4. All POs need to be closed of old items. No pending GRN. Before transferring the on hand quantity in new item code there should not any pending transaction of that item.  Customization of transaction form need to be checked properly. 5. 9. Unhand quantity to be transferred will be based on on hand report provided by SCM team.  Each and every scenarios need to be checked by user. 2.4 User Interface Requirement  Data flow from DMS system need to be perform by user. Old item code will not be disabled until and unless there is no further transaction on it.

6 Dependencies (If any): 1. as per IA confirmation.  Availability Requirements :No  System Capacity and Scalability Requirements: Yes  Efficiency Requirements: Yes  Maintainability Requirements: No CONFIDENTIAL/INTERNALLY RESTRICTED Page 17 of 20 . Business has to provide new code list mapped with the old items. 4.  Performance Requirements: Yes. PR submission time should not be increased by more than 30 seconds from the present one.4.7 Volumetric N/A 4. Business has to provide list of items that are serial control and will now be non-serialized 2.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.

9 UAT Acceptance Criteria Provided by business 1.1 Development Environment: / Testing/Staging Environment CONFIDENTIAL/INTERNALLY RESTRICTED Page 18 of 20 .4. Interfaces S Name No 1 DMS Direction Mode/ Purpose and other details Protocol In Po flow in ERP 2 2. HARDWARE AND SOFTWARE REQUIREMENTS 6.

11.7 ERP 6.1) & 11G(Database) 11.7 ERP 6.1.2 Production Environment: Server Name Location of the Server Operating System License Hardware Configuration Software and Version Owners of the System GNNERP01.0.3 Software and Utilities: Application Server Database License Web Server Protocols Used for transactions Oracle Application Server 10G 11G .7 10G CONFIDENTIAL/INTERNALLY RESTRICTED Page 19 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.02 GNDC Solaris 10 Sun Server R12(12.0.1) & 11G(Database) 11.1.0.1.1.

Appendix A: CONFIDENTIAL/INTERNALLY RESTRICTED Page 20 of 20 .External Interfaces 3.