- It identifies the products/services under warranty
- Validate the authenticity of warranty claims
- Validates whether the product/service issue highlighted by customer falls under warranty
- Define the effects of warranties on pricing & invoicing
- Monitor expenses incurred under due to warranty issues
- Vehicle Consumer come into dealership
- Dealer determines if product/service defect is under valid warranty
- If yes, dealer files warranty claim
- Warranty assessors may review claim for accuracy
- Claim is either approved or rejected
- If approved, claim is processed through to Finance and dealer is reimbursed
SAP:
- Define Warranty Claim Type
- Assign Number Range for Claim Type
- Define Decision Codes
- Define Pricing for warranty claim
- Maintain Pricing Condition Records
- Define Action Matrix for Claim Processing
- Define GL Account Determination Procedure for Claim Processing
- Assign Pricing, action matrix and GL Account Determination Procedure to Claim Type
- Implement Validation/Substitution for claims (Optional)
- Define Output Determination for claim credit note
- Maintain Output Condition Records
path for configuring the same.
follows the same process.
5. Maintain Pricing Condition Records
Similar to SD pricing condition records, warranty pricing condition records can be maintained via Transaction WYP1/WYP2/WYP3. To maintain conditions records
Please refer following SAP menu path.
SAP Menu ==> Logistics ==> Customer Service ==> Service Agreements ==> Warranty Claim Processing à Master Data ==>Condition Records for Pricing.
6. Define Action Matrix for Claim Processing
Action Matrix is a consolidated matrix of different actions/activities which can be carried out to a claim document at any given moment of time and also the consequences once any action is executed. Action matrix primarily consists of different actions and related status to it. Refer details about Action and Processing Status as mentioned below.
Action:
Every action does some processing and the processing logic is written is related Function Module attached to it. For example, standard action T041 has been defined as Elementary Action and Function Module WTY04_OC_POST_AC has been attached which would help to post credit memo for the claim amount.
To define action, follow below configuration path.
OWTY ==> Warranty Claim Processing ==> Control Data ==> Processing Control ==> Define Actions.
Refer Attached Function Module:
Processing Status:
After every action, claim gets a new status to identify every stage of the warranty claim. During definition of Action Matrix, these statuses would be used.
To define status, follow below configuration path.
OWTY ==> Warranty Claim Processing ==> Control Data ==> Processing Control ==> Define Processing Statuses.
Action Matrix:
Once Action and Processing Statuses are defined, action matrix can defined based on business requirement. This matrix would suggest what all activities (Claim Check, Claim Approval, Claim Reject etc.) can be done on a particular warranty claim and after completion of those action what would happen to the same claim document.
To define action matrix, please following below configuration path.
OWTY ==> Warranty Claim Processing ==> Control Data Processing Control ==> Define Action Controls.
Example of Standard Action Matrix is AP02.
Above given example (highlighted row), matrix suggests that for a claim document we can perform action T060 (via attached Function Module to it) only if the claim status is B002 and once we complete action T060, claim would have status B060.
7. Define GL Account Determination Procedure for Claim Processing
Every warranty claim should have account determination procedure attached to it to determine right GL account for posting claim expenses. Similar to configuration of Revenue Account Determination Procedure (e.g. definition of access sequence, condition type,
pricing procedure etc.) in the area of Finance, warranty GL Configuration procedure follows the same process.
To define GL determination procedure, refer following configuration path.
OWTY ==> Warranty Claim Processing ==> Revenue Account ==>Determination.
Example of Standard GL Determination procedure is KOFI00.
8. Assign Pricing, Action matrix and GL Account Determination Procedure to Claim Type
Pricing Procedure, Action Matrix and GL Account Determination procedure can be assigned to a claim type. To assign pricing procedure, action matrix and GL determination procedure, refer following configuration path.
OWTY ==> Warranty Claim Processing ==> Define Warranty Claim Types.
9. Implement Validation/Substitution for claims (Optional)
Validation and Substitution rules are similar functionality as available in the area of Finance. During warranty claim processing, if there is any business requirement to perform certain validation OR to substitute certain values as requested by business, these rules can be
implemented.
Implementation of Validation & Substitution is exactly similar to the functionality available in Finance Area. To implement validation and substitution please refer following configuration path.
OWTY ==> Warranty Claim Processing ==> Control Data ==> VSR Checks.
10. Define Output Determination for claim credit note
In case business has requirement to have an output (Print/Mail) for warranty credit notes, output determination procedure needs to be configure similar to output determination in SD area. Only difference here is, output type is assigned to FI documents generated for the claim. To implement output/message determination for warranty please refer following configuration path.
OWTY ==> Warranty Claim Processing ==> Message Determination.
11. Maintain Output Condition Records
Similar to SD output condition records, warranty message condition records can be maintained via Transaction WYN1/WYN2/WYN3. To
maintain conditions records please refer following SAP menu path.
SAP Menu ==> Logistics ==> Customer Service ==> Service Agreements ==> Warranty Claim ==> Processing ==> Master Data ==>
Condition Records for Message Determination.
