Technical Design Document

MMWF001 Notification to user for approved_rejected purchase

requisition

Version: 1.0

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 1 Last modified by: Mayank Choudhary
MMWF001 Notification to user for approved_rejected
purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 2 Last modified by: Mayank Choudhary
Usage guidelines and Specific Instructions:

• Document Flow - The flow of the document is generic. Specific changes to the flow will be
required to be done by the client team to suit the client context.

• Document Content -The content explains the technical specification in a generic manner.
Specific changes are required to be made to meet client requirement.

• Section 1 - The overall requirement summary, assumptions, dependencies can be

documented as a part of this section.

• Section 2 – This section caters to the detailed functional requirement. The technical flow
diagram and description can be designed and documented here. This should also include
conversion type, processing and operational considerations.

• Section 3 – Finer details like the database tables, external programs, SAP screens, data
mapping, source/target structure, are to be furnished in this section.

• Section 4 - The section needs to cover all the key business test conditions and assembly
test conditions that the conversion has to satisfy.

• Section 5 – All issues that have cropped up so far and their present status are to be
highlighted in this section.

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 3 Last modified by: Mayank Choudhary
Document Information

Deliverable Name Notification to user for approved rejected purchase requisitions

Author Debashis Roy
Owner Basab Bose
Team FastForward ABAP Factory
Status Initial Draft
Version 1.0

Document Review & Sign-off

Signatories
Role Name Signature Date
28-06-2012
Developer Debashis Roy

Reviewers
Role Name Comments Received Date

Revision History

Version
Date Author Revision Description
No.

Other Related Documents

<Please insert links to related Documents (issues, data entities, etc.).>

Related Document Comment

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 4 Last modified by: Mayank Choudhary
Related Document Comment

Table of Contents
Technical Attributes......................................................................................................................................7
1 Development Overview ...................................................................................................................................8
1.1 Requirements Summary .......................................................................................................................8
1.2 Assumptions ........................................................................................................................................8
1.3 Dependencies / Constraints ................................................................................................................8
1.4 Objects or Transactions Affected .......................................................................................................8
1.5 Transaction Volume ..............................................................................................................................8
1.6 Standards .............................................................................................................................................8
1.7 Security, Integrity and Controls ............................................................................................................8
1.8 Error Handling / Messages ...................................................................................................................9
1.9 Estimation of Effort ..............................................................................................................................9
2 Detailed Technical Specifications .......................................................................................................... 10
2.1 Technical Flow Diagram .................................................................................................................... 10
2.2 Technical Flow Description .................................................................. Error! Bookmark not defined.
2.3 Selection Screen Details...................................................................... Error! Bookmark not defined.
2.4 Data Source and Mapping ................................................................................................................. 13
2.5 Logo ................................................................................................................................................... 13
2.6 Barcodes ............................................................................................................................................ 13
N/A................................................................................................................... Error! Bookmark not defined.
2.7 Standard Text .................................................................................................................................... 13
2.8 Output Format .................................................................................................................................... 13
2.9 Form Details ...................................................................................................................................... 13
1.1.1 Main Heading ............................................................................ Error! Bookmark not defined.
1.1.2 Sub-heading .............................................................................. Error! Bookmark not defined.
1.1.3 Totalling ..................................................................................... Error! Bookmark not defined.
1.1.4 Sort Criteria ............................................................................... Error! Bookmark not defined.
1.1.5 Page Breaks ............................................................................... Error! Bookmark not defined.
1.1.6 Form Paper Size ....................................................................... Error! Bookmark not defined.
1.1.7 Form Layout .............................................................................. Error! Bookmark not defined.
Layout Set .................................................................................................. Error! Bookmark not defined.
1.1.8 Execution Mode Details ........................................................... Error! Bookmark not defined.
1.1.9 Miscellaneous Requirements .................................................. Error! Bookmark not defined.
2.10 Security and Authorization ................................................................................................................. 13
2.11 Processing and Operational Considerations ..................................................................................... 13
1.1.10 Dependencies ............................................................................ Error! Bookmark not defined.
1.1.11 Batch Requirements ................................................................ Error! Bookmark not defined.
1.1.12 Restart/Recovery Procedures ................................................ Error! Bookmark not defined.
1.1.13 Data Maintenance Requirements .......................................... Error! Bookmark not defined.
1.1.14 Re-use Details ........................................................................... Error! Bookmark not defined.
1.1.15 Multi-company, Multi-jurisdiction Considerations ............. Error! Bookmark not defined.
1.1.16 Other ........................................................................................... Error! Bookmark not defined.
3 Technical Requirements .......................................................................................................................... 14
3.1 Database Tables ................................................................................................................................ 14
3.2 External Programs ............................................................................................................................. 14
3.3 Development Class ............................................................................................................................ 14
3.4 Message Class .................................................................................................................................. 14
3.5 Program ID ........................................................................................................................................ 14
3.6 Program Type .................................................................................................................................... 14
MMWF001 Notification to user for approved_rejected
purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 5 Last modified by: Mayank Choudhary
 3.7 Module ............................................................................................................................................... 14
3.8 Transport Number(s) ......................................................................................................................... 14
4 Testing Requirements .............................................................................................................................. 15
4.1 Key Unit/Assembly Test Conditions .................................................................................................. 15
5 Outstanding Issues .................................................................................................................................. 16
6 Appendix ................................................................................................................................................... 17
6.1 Glossary of Terms ............................................................................................................................. 17
6.2 Additional Supporting/Reference Documentation ............................................................................. 17

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 6 Last modified by: Mayank Choudhary
Technical Attributes

Specification MMWF001
Program Name RBUS2105
Description PR Approval
SAP Type Work Flow
Attribut
es
Status Initial Development
Application MM
Developme ZMM01
nt Class
Authorizati
on Group
Logical
Database
Creation Date 28-June-2012
Version 01
Modification Ident.
Application Area Material Management

Author Debashis Roy

Approver Basab Bose

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 7 Last modified by: Mayank Choudhary
1 Development Overview
1.1 Requirements Summary

PR Approval Process (Release Strategy)

PR approval proccess will be configured as per DOP in the system for plant wise.

1.2 Assumptions

 HOD Derivation is dependent on the Release strategy configuration. It will be either on Z table , or on
individual department wise release code configuration.

1.3 Dependencies / Constraints

NA

1.4 Objects or Transactions Affected

Object Impacted Level of Impact Preventive Measure
ME51N / ME52N

1.5 Transaction Volume

Approximate 1000 emails will be triggered per day across all plants.

1.6 Standards
NA.

1.7 Security, Integrity and Controls

NA.
MMWF001 Notification to user for approved_rejected
purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 8 Last modified by: Mayank Choudhary
1.8 Error Handling / Messages
NA.

1.9 Estimation of Effort

Estimated Hours Actual Hours Sign-off
268.97 300.00

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 9 Last modified by: Mayank Choudhary
2 Detailed Technical Specifications
2.1 Technical Flow Diagram

Workflow will trigger whenever there will be any changes in the below mentioned events for purchase
requisition business object BUS2105.

RELEASESTEPCREATED Requisition Release Step Generated

REJECTED Release of Purchase Requisition Refused
RELEASED Release Purchase Requisition
CREATED Purchase requisition created

Email Details:

All emails will be trigged to user’s SAP inbox only.

Different emails will be triggered on different scenarios as mentioned above:

All the steps will be in Workflow history.

Step Description:
 Step 1: Get PR document type: EBAN-BSART
 Step 2: Get PR processing status: EBAN-BANPR
 Step 3:

Case 1: EBAN-BANPR=5 If PR is finally released for PO

 Step 4: Get email address of PR creator: EBAN- ERNAM
 Step 7: Send email to PR creator with Subject “PO &EBAN- EBELN created from PR &EBAN-
BANFN “

Email will be triggered to Indenter.

Email Subject “PO &EBAN- EBELN created from PR &EBAN- BANFN “

Email Subject : PR ....................(No) dated ................ is finally released for procurement.

Email Body:

Dear Sir/Madam,
PR.......................(No) dated.........................is finally released for procurement.

Please keep in touch with Purchasing group/Buyer for further correspondence.

Case 2: EBAN-BANPR =8 If PR is rejected

 Step 5: Get email address of PR creator: EBAN- ERNAM
 Step 8: Send email to PR creator with Subject “PR &EBAN- BANFN is Rejected“

Email will be triggered to Indenter.

Email Subject “PR &EBAN- BANFN is Rejected“ & (Created date should also appear)

Email Body:
MMWF001 Notification to user for approved_rejected
purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 10 Last modified by: Mayank Choudhary
Dear Sir / Madam,
PR &EBAN- BANFN has been rejected by &EKKO- ERNAM on &EKKO- AEDAT.
Please keep in touch with the approver for further details.

Thanks,
JSW Automated mailing system

Case 3: EBAN-BANPR =3, If PR is under Release

 Step 6: Next approval levels is determined as per with PR release strategy:

Find out the EBAN- FRGZU (Say XX), Count the no of characters (2), It means the PR is released by 2 nd
level. Find out the email ID of next level from the Z table for notification sending.
 Step 9: Send email to next level approver with Subject “PR &EBAN- BANFN is pending for your
approval“

Email will be triggered to next level of approvers

Subject “PR &EBAN- BANFN is pending for your approval“

Email Body:

Dear Sir / Madam,

PR &EBAN- BANFN is now pending for your approval. Please login to SAP and approve with your
SAP ID.

Thanks,
JSW Automated mailing system

Case 4: PR Blocked and unreleased by buyer

Email will be triggered to the Indenter

Subject “PR &EBAN- BANFN & Date is blocked by Purchasing group/Buyer”

Email Body:

Dear Sir / Madam,

PR &EBAN- BANFN is blocked by purchaser..

Blocked line Item numbers only in case the PR is blocked partially.

The reason for blocking is BLOCKING CODE Description.

Please do the needful and re-approve the PR again.

Thanks,
JSW Automated mailing system

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 11 Last modified by: Mayank Choudhary
A custom work flow in SAP Work flow Builder is developed as per the steps mentioned above.

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 12 Last modified by: Mayank Choudhary
2.2 Data Source and Mapping

NA

2.3 Logo

NA

2.4 Barcodes

NA

2.5 Standard Text

NA

2.6 Output Format

NA

2.7 Form Details

NA

2.8 Security and Authorization

NA

2.9 Processing and Operational Considerations

NA

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 13 Last modified by: Mayank Choudhary
3 Technical Requirements
3.1 Database Tables

NA

3.2 External Programs

NA

3.3 Development Class

ZMM01

3.4 Message Class

(Use message class created for the the module)

3.5 Program ID

NA

3.6 Program Type

Workflow

3.7 Module
MM

3.8 Transport Number(s)

CTS Request CTS Task Number CTS Description

Number
JEDK906171 EHP6:MM_DEVL_120525_
MMWF001_Notifin to user
for PR apprv/rej

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 14 Last modified by: Mayank Choudhary
4 Testing Requirements
4.1 Key Unit/Assembly Test Conditions
Indicate the business-level test conditions used to verify successful operations of the form.

Unit Test Log

Test
Objective
Step Date Description Expected Actual Requirement Sign
No. Output/Results Output/Results ID -off

Note
s

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 15 Last modified by: Mayank Choudhary
5 Outstanding Issues
Issu Description Assigned To Status Impact Resolution
e No

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 16 Last modified by: Mayank Choudhary
6 Appendix
6.1 Glossary of Terms

Term Definition

6.2 Additional Supporting/Reference Documentation

NA

MMWF001 Notification to user for approved_rejected

purchase requisition
Modified: 22-May-2012
©2012 Accenture. All Rights Reserved. 17 Last modified by: Mayank Choudhary