SAP SD Blueprinting Document

1. Process code :
GFCL-SD-012 Business Blueprint
Sales & Distribution
Project - Pragathi
Process Owner : D. DAVID GEORGE
Consultant (EID) RAJASEKHAR
Consultant (CFL) ANANDAN
Coreteam Member : KVS CHITTI
A. SRINIVASA RAO
Title :Collection Processing Version : 1.0 Date : 29.06.2006
1. BUSINESS PROCESS SCOPE ...........................................................................................................................................................1
3. CLIENT REQUIREMENTS...............................................................................................................................................................2
3.1 PROCESS REQUIREMENTS.................................................................................................................................................... 2
3.2 PRINTING REQUIREMENTS .................................................................................................................................................. 2
4. SPECIFICATION FOR IMPLEMENTATION IN SAP...................................................................................................................2
4.1 DEFINITION OF SAP CONCEPTS................................................................................................................................................ 2
4.2 MODELING OF CLIENT REQUIREMENTS IN SAP......................................................................................................................2
4.2.1 Organizational elements used .................................................................................................................................................2
4.2.2 To-Be process flow description ...............................................................................................................................................2
4.2.3 To-Be process flow chart..........................................................................................................................................................3
4.2.4 Change management issues......................................................................................................................................................3
4.2.5 Requirements mapping .............................................................................................................................................................3
4.2.5.1 Process ..................................................................................................................................................................................3
4.2.5.2 Printing...................................................................................................................................................................................3
4.2.5.3 Authorization..........................................................................................................................................................................3
4.2.5.4 Legal.......................................................................................................................................................................................3
4.2.5.5 Development...........................................................................................................................................................................3
4.2.5.6 Reporting................................................................................................................................................................................3
4.2.5.7 Interface.................................................................................................................................................................................3
1. REFERENCE.........................................................................................................................................................................................3
5. GAP ANALYSIS .................................................................................................................................................................................3
6. BUSINESS PROCESS APPROVAL...................................................................................................................................................4
1. Business Process Scope
Collection Processing
2. Description of Business Process Flow
Collection processing comes under Treasury and dealt by Financial Functionality.
Page 1 of 4

2. Process code :
GFCL-SD-012 Business Blueprint
Sales & Distribution
Project - Pragathi
Process Owner : D. DAVID GEORGE
Consultant (EID) RAJASEKHAR
Consultant (CFL) ANANDAN
Coreteam Member : KVS CHITTI
A. SRINIVASA RAO
Title :Collection Processing Version : 1.0 Date : 29.06.2006
3. CLIENT Requirements
3.1 Process requirements
3.2 Printing requirements
3.3 Authorization requirements
3.4 Legal requirements
3.5 Development
3.6 Reporting requirements
3.7 Interface requirements
4. Specification for Implementation in SAP
SAP Definitions if applicable
4.1 Definition of SAP concepts
A top level Conceptual Understanding of the relevant SAP Model that would influence the above mentioned Business Process
4.2 Modeling of CLIENT requirements in SAP
How will the CLIENT Requirements gets addressed in the above described SAP model
To be process mapping
 With reference to AS-IS process, how it will be mapped in SAP
 Whether all requirements are met in SAP
 If certain requirements are not met with standard SAP, identify this as GAP
 To-be Process chart if applicable
4.2.1 Organizational elements used
(List the organizational elements proposed to be used during the process. E.g., whether separate
company code will be needed for an EOU?)
4.2.2 To-Be process flow description
(Describe process flow in To-Be scenario)
Page 2 of 4

3. Process code :
GFCL-SD-012 Business Blueprint
Sales & Distribution
Project - Pragathi
Process Owner : D. DAVID GEORGE
Consultant (EID) RAJASEKHAR
Consultant (CFL) ANANDAN
Coreteam Member : KVS CHITTI
A. SRINIVASA RAO
Title :Collection Processing Version : 1.0 Date : 29.06.2006
4.2.3 To-Be process flow chart
4.2.4 Change management issues
(This is for ‘Organization Change Management’ – List the changes identified in the process
mapping. E.g. with purchase order release strategy, the document will have to be released in
R/3 by the Materials Manager. In AS-IS scenario, the manager used to sign the PO. Releasing
the document in the system would be an additional activity)
4.2.5 Requirements mapping
(Check whether the requirements listed by client can be mapped in standard SAP. If those are
not available in standard SAP, then those are to be listed as ‘Gaps’)
4.2.5.1 Process
4.2.5.2 Printing
4.2.5.3 Authorization
4.2.5.4 Legal
4.2.5.5 Development
4.2.5.6 Reporting
4.2.5.7 Interface
Process No Process Description
Links to CLIENT process If applicable (any external
reference process
number, e.g. from ISO/
FDA etc.)
5. Gap Analysis
Gaps Approach**
List the requirements which cannot be
mapped with standard SAP
**Identify that there is a needed business function that cannot be accommodated by SAP. Mention System
modification that needs to be done- at a higher level, any future enhancements which might address the requirement
Page 3 of 4
1. Reference

4. Process code :
GFCL-SD-012 Business Blueprint
Sales & Distribution
Project - Pragathi
Process Owner : D. DAVID GEORGE
Consultant (EID) RAJASEKHAR
Consultant (CFL) ANANDAN
Coreteam Member : KVS CHITTI
A. SRINIVASA RAO
Title :Collection Processing Version : 1.0 Date : 29.06.2006
6. Business Process Approval
By Date Comments
Page 4 of 4