FIFS_DPR

Development Summary:

Name of ProjectWWG UDAAN

AuthorMahesh Rai

Name of DevelopmentZRQM_NOTIF_MAIL

Short DescriptionTrigger mail automatically just after saving at notification status ATCO to Parveen Prabhu ji. If Notification not APOK then mail to Naveen Ji after 30 Days from date of Notification.

When status is APOK then mail should triggered to Sales coordinator & Account Deptt.

Development TypeMail

Module/Business Process

Current Version

Required T Code

Complexity (L/M/H)M

Priority (L/M/H)L

Frequency Daily

Functional Consultant Mahesh Rai

Process Owner

Approval Date

Reference PDDQuality Notification

Specification is approved for coding(Signature & Name Mahesh Rai)Version History:

Version NoDate UpdatedChange Request NoRevision AuthorReason for Revision

Technical Summary:

Name of Technical ConsultantRam Shankar

Request No

Start Date

Completion Date

Approval Date

Tested and Approved(Signature & Name Process Owner)

Functional Specification:

Objective of DevelopmentSAP system should send mail at THREE levels for the notification type Q1 only.

Point1: When the notification is just saved but Notification status should be ATCO ( I0159- system status in TJ02 table)

Point2:After 30 days on regular basis till the status of the notification becomes APRQ ( I0525 system status in TJ02 table) then Mail to Naveen Ji. If Notification status APOK ( I0526 system status in TJ02 table) then mail not triggered to Naveen Ji

Point3:When the Notification status APOK ( I0526 system status in TJ02 table)

then mail to triggered sales coordinator & account deptt.Relevant Transaction Codes

Transaction CodeDescription

QM01Create customer claim Notification

QM11Notification customer claim report

Reference SAP Programs

Program NameDescription

Selection Parameters

Field NameTable NameDescription(M)andatory

(O)ptional(P)arameter

(S)elect Option

Error Handling

Message ClassError NoError MessageCause of Error

User Exit/Enhancement

Exit NameComponent NameDescription

Source File Location

File Path

Pr-requisite

Program Logic/Pseudo Code

Pick notification type, no, short text, Reference no & notification date from QMEL table.

To check the status of the notification, pick the Object no from QMEL table against the notification and pass the same into JEST table.

To get the description of status, pass the Object status from JEST table into TJ02 table.

Conditions for auto mail generation:

4.1 Mail should be triggered to Mr. Parveen Ji (parveen Kumar ), only for Q1 type Notification (QMART field of QMEL table). For testing purpose, you can use my email Id mahesh.rai@worldswindow.cc.

4.2 Mail should be triggered when the notification status ATCO ( I0159 system status in TJ02 table) is saved.

Mail should also be triggered on regular basis after 30 days when calculated from the date of notification till the status of the notification changes to APOK ( I0526 system status in TJ02 table)

The contents of the mail will be

5.1 For the mail which will be created just after saving the notification.Subject: Customer Claim (PFR)Dear Sir following customer claim have been received.

5.2 For the mail which is generated for the pending notifications.

Subject: Pending Claims

Dear Sir following claims notifications are pending:

Notification no (QMNUM field of QMEL table)

Notification date (QMDAT QMEL table)

Short Description (QMTXT QMEL table)

Sales Order No (VBELN field of QMEL table)

Customer Name: from table KNA1Report Layout (For Reports)

Special Requirement

Assumption/Note

Technical Specification

Objects Used

Logical Database

TablesQMEL, TJ02T & KNA1

Includes

Function Modules

Message Class

Called Screens / T Codes / Programs

BDC Type

Package

Logic Applied

Assumption/NotesPage 5 of 5