Sie sind auf Seite 1von 23

SVC.EXT.

339 Enterprise Service Contracts


Motorola Business Transformation Program Phase II
Version 1.1
Date: 23-MAR-2012

Document Change Control


Change History
Version

Date

Changes

Author

0.1

19-Mar-2012

Initial Version

Venu Andra

0.2

20-Mar-2012

Initial Version

Tauseef / Mitul

0.3

20-Mar-2012

Initial Version

Tauseef

0.4

23-Mar-2012

Changes as per Rachels comments

Tauseef

1.0

23-Mar-2012

Prepared for approvals

Terry McLaughlin

1.1

23-Mar-2012

Change in File format & File Name

Tauseef

Review Detail
Review #

Date

Name & Role of Reviewer

Rachel Vajgrt

Umesh Jetty

Emilio Bahena

TerryMcLaughlin

Anne-Michele Destefano

Approval Detail
Name & Role of Approver

Signature

Rachel Vajgrt
Anne-Michele Destefano
Ataullah Mohammed IT Architect

Approval Link
https://docs.google.com/a/motorola.com/spreadsheet/ccc?
key=0Al5jdkjvd4dndDlNX0l5aWdjTV9xMnF2M3ZNNU5vQWc#gid=1

SVC.EXT.339.FD_TD.v 0.1

CONTENTS
1. BACKGROUND ........................................................................................................................................................................................5
2. GLOSSARY OF DEFINITIONS.......................................................................................................................................................................6
3. REFERENCES...........................................................................................................................................................................................7
4. SOX PROJECT TYPE (SOX COMPLIANCE)..................................................................................................................................................8
5. REQUIREMENT DEFINITION........................................................................................................................................................................9
6. FUNCTIONAL SPECIFICATION...................................................................................................................................................................10
6.1. DESIGN CONSIDERATIONS:...................................................................................................................................................................10
6.2. DESIGN ASSUMPTIONS:.......................................................................................................................................................................11
6.3. MAJOR FEATURES:.............................................................................................................................................................................11
6.4. DATA MAPPING.................................................................................................................................................................................11
6.5. FILE LAYOUT: ..................................................................................................................................................................................11
6.5.1. FILE FORMAT FOR UPLOAD SNS IN SERVICE CONTRACT.......................................................................................................................11
6.6. DETAILED REQUIREMENT:...................................................................................................................................................................11
6.7. LOADING REQUIREMENTS:...................................................................................................................................................................11
6.8. PRE REQUISITES:...............................................................................................................................................................................11
6.9. FLOW DIAGRAM................................................................................................................................................................................12
.............................................................................................................................................................................................................13
6.10. DATA VALIDATION REQUIREMENT: ....................................................................................................................................................14
6.11. DATA CLEANUP...............................................................................................................................................................................14
6.12. NON-FUNCTIONAL REQUIREMENTS.....................................................................................................................................................14
6.12.1. SECURITY REQUIREMENTS.............................................................................................................................................................14
6.12.2. PERFORMANCE REQUIREMENTS........................................................................................................................................................14
6.12.3. HARDWARE/SOFTWARE/INSTANCE ..................................................................................................................................................14
6.12.4. APPLICATION LANGUAGE REQUIREMENTS.........................................................................................................................................14
6.12.5. USER INTERFACE...........................................................................................................................................................................14
6.12.6. USER DOCUMENTATION AND HELP SYSTEM REQUIREMENTS................................................................................................................14
6.12.7. INFORMATION PROTECTION REQUIREMENTS.......................................................................................................................................14
6.12.8. AVAILABILITY REQUIREMENTS........................................................................................................................................................14
6.12.9. SUPPORTABILITY/MAINTAINABILITY REQUIREMENTS...........................................................................................................................14
6.12.10. ARCHIVING/STORAGE REQUIREMENTS............................................................................................................................................14
6.12.11. INTERNAL CONTROL REQUIREMENTS :.............................................................................................................................................14
6.13. ERROR HANDLING:...........................................................................................................................................................................15
6.14. DATA VERIFICATION.........................................................................................................................................................................15
7. TECHNICAL DESIGN...............................................................................................................................................................................16
7.1. APPROACH:.......................................................................................................................................................................................16
7.2. IMPACT OF ORACLE PATCHES..............................................................................................................................................................16
7.3. PROGRAM AND COMPONENT DETAILS:..................................................................................................................................................16
7.4. < PROGRAM NAME> - CONVERSION/INTERFACE/CONCURRENT PROGRAM DESCRIPTION:..............................................................................16
7.4.1. CALLING ARGUMENTS.....................................................................................................................................................................16
7.4.2. INPUT/OUTPUT FILES AND TABLES ...................................................................................................................................................16
7.4.3. LOG OUTPUT..................................................................................................................................................................................16
7.4.4. PROGRAM LOGIC:...........................................................................................................................................................................17
7.4.5. PSEUDO CODE.................................................................................................................................................................................17
7.4.6. VALIDATION LOGIC.........................................................................................................................................................................17
7.4.6.1. ERROR CONDITIONS:....................................................................................................................................................................17
7.4.6.2. WARNING CONDITIONS:................................................................................................................................................................17
7.4.6.3. INCOMPATIBILITY..........................................................................................................................................................................17
7.4.7. OTHER CONSIDERATIONS..................................................................................................................................................................17
7.4.7.1. RESTART STRATEGY.....................................................................................................................................................................17
7.4.7.2. CRASH RECOVERY.......................................................................................................................................................................17
7.5. <FORM NAME> - FORM DESCRIPTION:.................................................................................................................................................17
7.5.1. NAVIGATION LOGIC.........................................................................................................................................................................17
7.5.1.1. ENTRY MODE..............................................................................................................................................................................17
7.5.2. BLOCK RELATIONSHIP DIAGRAM.......................................................................................................................................................17
7.5.3. BLOCK AND FIELD SUMMARY...........................................................................................................................................................17
7.5.3.1. BLOCK 1....................................................................................................................................................................................17
7.5.3.2. BLOCK 2....................................................................................................................................................................................18
7.5.3.3. SPECIAL LOGIC............................................................................................................................................................................18
SVC.EXT.339.FD_TD.v 0.1

7.5.3.3.1. BLOCK 1.................................................................................................................................................................................18


7.5.3.3.2. BLOCK 2.................................................................................................................................................................................18
7.6. <REPORT NAME> - REPORT DESCRIPTION:...........................................................................................................................................18
7.7. <WORKFLOW NAME> - WORKFLOW DESCRIPTION.................................................................................................................................18
7.7.1. WORKFLOW PROCESSES...................................................................................................................................................................18
7.7.1.1. <PROCESS NAME>.......................................................................................................................................................................18
7.7.2. PROCESS DESIGN............................................................................................................................................................................18
7.7.3. PROGRAM LOGIC ...........................................................................................................................................................................18
7.7.4. PSEUDO CODE.................................................................................................................................................................................18
7.8. TABLE AND VIEW USAGE....................................................................................................................................................................18
7.9. APPLICATION DESIGN.........................................................................................................................................................................18
7.9.1. VALUE SETS..................................................................................................................................................................................18
7.9.2. DESCRIPTIVE FLEX FIELDS................................................................................................................................................................18
7.9.3. KEY FLEX FIELDS: .........................................................................................................................................................................19
7.9.4. LOOKUPS: .....................................................................................................................................................................................19
7.10. DATABASE DESIGN...........................................................................................................................................................................19
7.10.1. GRANTS/SYNONYMS......................................................................................................................................................................19
7.10.2. ARCHIVING...................................................................................................................................................................................19
7.10.3. DATABASE DIAGRAM.....................................................................................................................................................................19
7.10.4. NEW TABLES, VIEWS, INDEXES, SEQUENCES....................................................................................................................................19
7.10.5. NEW DATABASE TRIGGERS.............................................................................................................................................................19
8. TEST CASES.........................................................................................................................................................................................20
8.1. UNIT TEST PLAN:..............................................................................................................................................................................20
9. APPLICATION SET UPS...........................................................................................................................................................................21
10. LOCALIZATION IMPLICATIONS (IF APPLICABLE)........................................................................................................................................22
11. ISSUES...............................................................................................................................................................................................22
11.1. OPEN ISSUES...................................................................................................................................................................................22
11.2. CLOSED ISSUES................................................................................................................................................................................22
12. ACCEPTANCE CRITERIA........................................................................................................................................................................23

SVC.EXT.339.FD_TD.v 0.1

1. Background
Enterprise Customers requesting extended services for a group of devices are presented with Service Contracts for
the particular type of devices in bulk. This extension will be used to validate the eligibility and mass upload of
serial numbers in service contract. This extension will also support bulk update of install base item instances.

2. Glossary of Definitions
A Glossary of Definitions is available on Google Docs at the below link.
https://docs.google.com/a/motorola.com/document/d/1Ou4noP_bdX8UICg67B0RGB_3S6StxJC99KSeYdYs5s/edit?hl=en_US

3. References
Document Name
PL 201 Requirements Traceability
iProtect Basic Risk Self-Assessment Form
AP250_RICEFW
BP 310 Process Flows

URL
https://compass.motorola.com/go/375203815
http://compass.mot-mobility.com/go/321805679
https://compass.motorola.com/go/375203815
https://compass.motorola.com/go/377577537

4. SOx Project Type (SOx Compliance)


The SOX Project Type for this project or change is:

SOx PROJECT TYPE


Type 1: SOX Significant
Type 2: SOX Impacting
Type 3: SOX Level 1 System, but not SOX significant or impacting
Type 4: Not SOX Level 1 system

EVIDENCE
SOX Request #
72093

5. Requirement Definition
This is detail design document for the requirement defined in the fit gap analysis.

5.1

Extension Short Description: (Required)

Warranty Exceptions

5.2

Process Area: (Required)

Service Contract (OKS)

5.3

Application: (Required)

Service Contract (OKS)

5.4

Development Complexity: (Required)

Medium

5.5

Transaction Volume: (Required)

Medium

5.6

Automatic or Manual Conversion:


(Required)

N/A

5.7

Source System: (Required)

Service Contract (OKS)

5.8

Source System Contact: (Required)

Umesh Jetty

5.9

Destination System: (Required)

Service Contract (OKS)

5.10

Destination System Contact: (Required)

Umesh Jetty

6. Functional Specification
6.1. Design Considerations:
Business Scenarios
1. Motorola can sell/offer service contracts to enterprise customers where charges shall be applied to
the Enterprise customer but services shall be provided to other party/customer (Employees) related to
Enterprise customer
2. Service contract will be create for enterprise customer having multiple serial numbers associated
under single contract.
Business Requirement
1.

Business team shall create a contract in entered status with below mentioned details
Header
Parties

Pricing

Administration
Line Details

Contract Number
Start Date End Date
Currency
Vendor (Motorola)
Customer (Ship To)
Third Party (Bill To)
Price List
Accounting Rule
Invoicing Rule
Payment Terms
Contract Group
Approval Workflow
Service Item

2. Business team shall create the file to upload bulk Serial Numbers to the contract created in Entered
Status.
3. If there is no contract found in Entered state, extension will not update the contract, business need to
create a new contract in Entered Status and update file accordingly.
4. Business team shall pass Service Item, Serial Number, Start Date, Duration and Period in the file to
the extension.
5. Contract Number and Party Number will be provided as file name. The program will read the
contract number and party number from file name.
6. File name must follow the same structure - ESC_XXXXXX_ZZZZZ.csv, where XXXXX represent
Contract Number and ZZZZ represents Party Number.
eg. ESC_US-100000017-SC_654788.csv
7. All the fields are mandatory in the file.
8. The extension shall call Serial Number search program and create IB record from UPD if IB record is
not already in Install Base.
9. The extension will validate the IB ownership with contract party, if there is mismatch it will transfer
ownership of the item instance to Ship-To contract party.
10. While ownership will be transferred, Party details will be fetched from contract.
11. QA check validation and Contract approval will be done manually.
12. If there is any existing contract (Warranty / Repair / POP), it needs to be transferred to new owner
during ownership transfer.
13. Billing schedule has to be created by the program.
14. Unprocessed records will be notified to business with valid error details.

Screen Shot will show where to get Contract and Party Number

Contract_Party_Details.jpg

6.2. Design Assumptions:

If the Serial Numbers are not preset in IB then it should be created from UPD by calling Serial
Number Search.
All the Serial Number uploaded for Contract Creation for specific contract will belong to same Ship
To Service customer
Serial Number will be added for the contract in entered status, once contract is approved and active,
new contract will be created for same Bill to and Ship to Party.
Coverage duration for new serial must be Less Than or Equal To contract duration passed in the file.
A contract can have multiple service item in contract, Same service item can not be repeated in a
contract.
The required responsibilities are active with associates who are responsible for create & approve
service contracts.
While a contract is renewed it must have new contract number, contract number with modifier is not
supported.

6.3. Major Features:

Mass upload serial numbers in Service Contract.

6.4. Data Mapping


Not Applicable (NA)

6.5. File Layout:


6.5.1.

File Format for upload SNs in Service Contract


a.

Mass Upload Contract

ESC_XXXXXXXX_ZZZ
ZZZZ.csv

6.6. Detailed Requirement:


Req. No.

Requirements Description

6..6.
1
6..6.
2
6..6.
3
6..6.
4

Ability to a create service contract with different billing party and service party
Automated process to add bulk SR# to the contract
Validate the contract status to add serial number in sublines
Transfer ownership of item instance if required.

6.7. Loading Requirements:


6.8. Pre Requisites:

All items need to have been defined in the Item Master

6.9. Flow Diagram


Below flowchart give the process flow of Mass upload serial numbers in service contract through flat file.

Date File

Enterprise
Contract
Program

Validate
Contract

Valid Contract Found

Add Lines to the


Contract

Valid Contract Not Found

No

Log an error and


send details

Log an error and


send details

Sign
Contract

Contract Active

Yes

Approval
Successfull

Continue QA
check and
approval

Lines Added
Succesfully

Continue
Approval

Yes

QA Check
Successful

No

No

Rectify Error
and Approve

Rectify Error
and QA
check again

6.10.

Data Validation Requirement:


NA

6.11.

Data Cleanup
NA

6.12.

Non-Functional Requirements

6.12.1. Security Requirements


NA

6.12.2. Performance Requirements


Req. No.

Requirements Description

6.13.2.1

Forms and Extensions should be verified with parallel sessions to check for locks

6.12.3. Hardware/Software/Instance
Hardware

CPU
RAM
Others
Oracle
Internet
Explorer/Chrome/Mo
zilla
Others

Software

Instance

Speed: 1GHz
Memory: 2GB
None
Software: Oracle Client 10g
Version: Latest Version available
None

NA

6.12.4. Application Language Requirements


NA

6.12.5. User Interface


NA

6.12.6. User Documentation and Help System Requirements


NA

6.12.7. Information Protection Requirements


NA

6.12.8. Availability Requirements


NA

6.12.9. Supportability/Maintainability Requirements


NA

6.12.10.Archiving/Storage Requirements
The files of enterprise service contracts archived after 1yr of contract expire.

6.12.11.Internal Control Requirements:


NA

6.13.

Error Handling:
Sl. #

6.14.

Potential Errors

Data Verification
NA

Possible Reasons

Notification
Procedures

Solution
Strategy

Responsible
organization

7. Technical Design
7.1. Approach:
7.2. Impact Of Oracle Patches
7.3. Program and Component Details:

Object Name / Concurrent


Program

File Name

Object Type

Description

7.4. < Program Name> - Conversion/Interface/Concurrent Program Description:


7.4.1.

Calling Arguments

Number of Days

7.4.2.

Input/Output Files and Tables

Tables

7.4.3.
NA

Log Output

7.4.4.

Program Logic:

7.4.5.

Pseudo code

7.4.6.

Validation Logic

7.4.6.1. Error Conditions:


NA

7.4.6.2. Warning Conditions:


NA

7.4.6.3. Incompatibility
NA

7.4.7.

Other Considerations

7.4.7.1. Restart Strategy


NA

7.4.7.2. Crash Recovery


NA

7.5. <Form Name> - Form Description:


7.5.1.

Navigation Logic

7.5.1.1. Entry Mode


START
1.
2.
END

7.5.2.

Block Relationship Diagram

<The diagram below represents the base tables of each block of the form (vertical) and tables referenced for
validation or lookups (horizontal)>

7.5.3.

Block and Field Summary

7.5.3.1. Block 1
Base Table:
Where/Order By:
Field/Column

Type

Reqd?

Default

Validation

Quick Pick

7.5.3.2. Block 2
Base Table:
Where/Order By:
Field/Column

Type

Reqd?

Default

Validation

Quick Pick

7.5.3.3. Special Logic


7.5.3.3.1.

Block 1

7.5.3.3.2.

Block 2

7.6. <Report Name> - Report Description:


7.7. <Workflow Name> - Workflow Description
7.7.1.

Workflow Processes
7.7.1.1.

<Process Name>
NA

7.7.2.

Process Design
NA

7.7.3.

Program Logic
NA

7.7.4.

Pseudo code
NA

7.8. Table and View Usage


Table Name

Select

7.9. Application Design


7.9.1.

Value Sets
NA

7.9.2.

Descriptive Flex fields


NA

Insert

Update

Delete

Base
Table

7.9.3.

Key Flex fields:


NA

7.9.4.

Lookups:
NA

7.10.

Database Design
NA

7.10.1. Grants/Synonyms
NA

7.10.2. Archiving
NA

7.10.3. Database Diagram


NA

7.10.4. New Tables, Views, Indexes, Sequences


NA

7.10.5. New Database Triggers


NA

8. Test Cases
8.1. Unit Test Plan:
Test Scenario

Step No

Description

Expected Result

Actual Results

9. Application Set Ups

10. Localization Implications (if Applicable)

11. Issues
11.1.

Open Issues

Serial No.
1.

11.2.

Issue
Number of maximum sublines in a
contract?

Resolution
No.

Closed Issues

Serial No.
1.

Issue

Resolution

12. Acceptance Criteria