You are on page 1of 8

Warranty Claim Processing Functional

Specification

Warranty Claim Process

Functional Specification
(Data Upload Program)
Author:
Reviewed By:
Status :
Issue Date:
Version:

Sanjay
Avinash
Draft

Document Control
Ver

Details of Changes

By

Date

Reviewed by

Document Approval
Name

Role

Warranty Claim Processing Funct Specification

Signature

Page 1 of 8

Date

01 Sept 2008

Warranty Claim Processing Functional


Specification

Table of Contents
1. OVERVIEW..........................................................................................................................................3
1.1 PURPOSE...............................................................................................................................................3
1.2 BUSINESS RATIONALE..........................................................................................................................3
1.3 GENERAL REQUIREMENTS...................................................................................................................3
1.4 ASSUMPTIONS......................................................................................................................................3
1.5 RELATED DOCUMENTS.........................................................................................................................3
2. DETAILED DESIGN............................................................................................................................4
2.1 EXISTING / SAMPLE REPORTS OR RELATED TRANSACTIONS...............................................................4
2.2 WARRANTY CLAIM PROCESS DESIGN..................................................................................................4
2.2.1 Detailed Description of New Report / Changes to Existing Report..............................4
2.2.2 Interactive Capabilities ...............................................................................................4
2.2.3 Input: Selection Screen Layout...................................................................................5
2.2.4 Input: Fields and Validations.......................................................................................5
2.2.5 Output: Report Layout.................................................................................................5
2.2.6 Output: Field Descriptions...........................................................................................6
2.2.7 Additional Output Information:.....................................................................................6
2.2.8 Main Heading:............................................................................................................. 6
2.2.9 Sub-Heading:.............................................................................................................. 6
2.2.10 Breaking:................................................................................................................... 6
2.2.11 Totals:....................................................................................................................... 6
2.2.12 Sorting:...................................................................................................................... 6
2.2.13 Design Constraints:...................................................................................................6
2.2.14 Security and Authorisations:......................................................................................6
2.3 PERFORMANCE CONSIDERATIONS........................................................................................................6
2.4 ERROR HANDLING................................................................................................................................6
2.4.1 Potential Errors:.......................................................................................................... 6
2.4.2 Notification Procedures:..............................................................................................6
3. TESTING REQUIREMENTS..............................................................................................................7
3.1 CONFIGURATION FOR TESTING............................................................................................................7
3.2 BUSINESS TEST CONDITIONS...............................................................................................................7
3.3 TEST DATA...........................................................................................................................................7

Warranty Claim Processing Funct Specification

Page 2 of 8

01 Sept 2008

Warranty Claim Processing Functional


Specification

1.

OVERVIEW

1.1
Purpose
The purpose of this document is mass upload warranty claim data into sap r/3 system through
upload programme.
Upload program will be developed to load customer claim invoices to create a claim into the
SAP R/3 system. This program will pick up the data file from common server, validate the data
into std Excel format, validate important input fields with SAP R/3 like Claim type, Customer no,
Item no ,Material group, Customer group, Claim value etc. and upload the data.
1.2
Business Rationale
The business rational is to find the status of the warranty claim data upload programme is
getting upload correctly in SAP R/3 as per requirement or not. Also system has to validate data
before upload in the system, if there is any data mismatch system should give the error with
particular wrong data information. Once data get uploaded in the system, warranty claim
number should generate.
1.3
General Requirements
Distribution target audience / executors:
Distribution number of copies:
Summary level:
Output:
Mode of Operation:
Initiating process (transaction, interface,
etc.):
Volume (expected no. of records):
Execution frequency:
Execution authorisation (role or profile):
1.4
No.
1.
2.

Error Summary

Daily

Assumptions
Assumption detail

1.5
Related Documents
Document Name

Warranty Claim Processing Funct Specification

Link

Page 3 of 8

01 Sept 2008

Warranty Claim Processing Functional


Specification

2.

DETAILED DESIGN

2.1
Existing / Sample Reports or Related Transactions
SAP Program Name:
SAP Menu / Transaction:
Legacy Report Name:
Legacy Report Number:
2.2

Warranty Claim process Design

2.2.1

Detailed Description of New Report / Changes to Existing Report

2.2.2

Interactive Capabilities

Warranty Claim Processing Funct Specification

Page 4 of 8

01 Sept 2008

Warranty Claim Processing Functional


Specification

2.2.3

Input: Selection Screen Layout

2.2.4 Input: Fields and Validations


Table
Field
Description
PNWTYH
REFDT
Reference Date
KNA1
KUNNR
Partner
PNWTYH
RELTY
Obj.Type
PNWTYH
RELOB EXT
Obj.No
WTY_PNV_D V_PARNR
Partner
YNPRO
(Version)
PVWTY
POSKT CUST Item Type
MARA
MATNR
Material code
PVWTY
QUANT
Quantity
PVWTY
I_SERNO
Serial No
PVWTY
MEINH
Unit of
measure
PVWTY
HERST
Vendor
MARA
MATKL
Material group
KNVV
KDGRP
Customer
group
PVWTY
CONTR
Contribution
PNWTYV
HANDLE
Warranty
Handle

Mandatory
yes
yes
yes
yes
yes

Default Value

EQUI

yes
yes
yes
no
yes
yes

yes
yes

2.2.4.1 Validations:

1) While converting data into standard excel format file, system has to provide
basic data validation.
2) While upload data file into SAP R/3 for create claim with tranction code WTY,
program has to validate claim data properly as per business rule like
Customer/Material/Equipment and Vendor Number.
3) If file comes with more than one line item for cerate the claim in the system and
if there is error with some line item system has to throw error message for
invalid data.
4) If data file comes with two different customers and/or Reference no (invoice
no), system should create two different claims.
5) If material group is PRE, system should create claim type as Pre-Credit.
6) If material group is POST system should create claim type as Post-Credit.
7) If customer group is XX and product is not under warranty then system should
create claim type as a YP02- Authorization.
8) If claim comes with same customer and different Equipment number for
different line item then system should create different claim number.

2.2.5

Output: Report Layout

Warranty Claim Processing Funct Specification

Page 5 of 8

01 Sept 2008

Warranty Claim Processing Functional


Specification

2.2.6

Output: Field Descriptions

2.2.7

Additional Output Information:

2.2.8

Main Heading:

2.2.9

Sub-Heading:

2.2.10 Breaking:

2.2.11 Totals:

2.2.12 Sorting:

2.2.13 Design Constraints:

2.2.14 Security and Authorisations:

2.3

Performance Considerations

2.4

Error Handling

2.4.1

Potential Errors:

2.4.2

Notification Procedures:

Warranty Claim Processing Funct Specification

Page 6 of 8

01 Sept 2008

Warranty Claim Processing Functional


Specification

3.

TESTING REQUIREMENTS

3.1

Configuration for Testing

3.2
Business Test Conditions
No. Description
1
Check material/customer/equipment
and vendor Number
2
Check Object Warranty
3
4
5

Check combination of same customer


and same Equipment for all line item
Check combination of same customer
but different Equipment number for
different line items
Check different customer but same
equipment number

3.3

Expected Result
System should give error message for incorrect
data.
If product is not under warranty but customer
group is XX (Authorization) then should claim
type as YP02 or reject the claim..
Create single claim number
Create different claim number
Create different claim number

Test Data
Header Data

Ref Date

Partner

1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9
1709200
9

GM
MOTORS
GM
MOTORS
GM
MOTORS
Delphi
GM
MOTORS
GM
MOTORS
GM
MOTORS
Delphi
Delphi
GM
MOTORS
GM
MOTORS
GM
MOTORS
GM
MOTORS
Delphi
GM
MOTORS
GM
MOTORS
GM
GM
MOTORS

Version Data
Ext. Obj.
no
CHASIS
E1
CHASIS
E1
CHASIS
E1
CHASIS
E1
ENGINE
1
ENGINE
1
ENGINE
1
ENGINE
1
ENGINE
1
CAR1

Material
no
Battery

Serial
no

Qt
y
1

Unit of
Measure
EA

Vendo
r
Delphi

Contributio
n
500

Authorisation / Claim1

Tyres

EA

Delphi

500

Authorisation / Claim1

Battery

EA

500

Authorisation / Claim1

Battery

EA

Nissa
n
Delphi

500

Fail case

Battery

EA

Delphi

500

Precredit / Claim 1

Tyres

EA

Delphi

500

Precredit / Claim 1

Battery

EA

500

Precredit / Claim 1

Battery

EA

Nissa
n
Delphi

500

Precredit / Claim 2

Tyres

EA

500

Precredit / Claim 2

Battery

EA

Nissa
n
Delphi

500

Precredit / Claim 3

ENGINE
1
ENGINE
1
ENGINE
1
ENGINE
1
CAR1

Stearing

EA

Delphi

500

Postcredit / Claim1

Gear Box

EA

Delphi

500

Postcredit / Claim1

Stearing

EA

500

Postcredit / Claim1

Stearing

EA

Nissa
n
Delphi

500

Postcredit / Claim2

Stearing

EA

Delphi

500

Postcredit / Claim3

CAR1

Gear Box

EA

500

Postcredit / Claim3

ENGINE
1
ENG

Gear Box

EA

Nissa
n
Delphi

500

Fail case

Gear Box

EA

Delphi

500

Fail case

Warranty Claim Processing Funct Specification

Page 7 of 8

01 Sept 2008

Warranty Claim Processing Functional


Specification
1709200
9
1709200
9

GM
MOTORS
GM
MOTORS

ENGINE
1
ENGINE
1

BATT

EA

Delphi

500

Fail case

Battery

EA

DEL

500

Fail case

Transaction:
Menu Path:
Step 1:
Step 2:

Warranty Claim Processing Funct Specification

Page 8 of 8

01 Sept 2008

You might also like