SAP SD Blueprinting Document

1. Process code :
GFCL-SD-007 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 : Billing Version : 1.0 Date : 29.06.2006
1. BUSINESS PROCESS SCOPE ..........................................................................................................................................................2
BILLING ........................................................................................................................................................................................2
2. DESCRIPTION OF BUSINESS PROCESS FLOW .....................................................................................................................3
3. CLIENT REQUIREMENTS................................................................................................................................................................4
3.1 PROCESS REQUIREMENTS.......................................................................................................................................................... 4
3.2 PRINTING REQUIREMENTS ........................................................................................................................................................ 4
3.3 AUTHORIZATION REQUIREMENTS .............................................................................................................................................4
3.4 LEGAL REQUIREMENTS ........................................................................................................................................................... 4
3.5 DEVELOPMENT ........................................................................................................................................................................ 4
3.6 REPORTING REQUIREMENTS ..................................................................................................................................................... 4
3.7 INTERFACE REQUIREMENTS ...................................................................................................................................................... 4
4. SPECIFICATION FOR IMPLEMENTATION IN SAP...................................................................................................................4
4.1 DEFINITION OF SAP CONCEPTS................................................................................................................................................ 4
4.2 MODELING OF CLIENT REQUIREMENTS IN SAP......................................................................................................................4
4.2.1 To-Be process flow description ................................................................................................................................................5
4.2.2 To-Be process flow chart..........................................................................................................................................................5
4.2.3 Change management issues......................................................................................................................................................5
4.2.4 Requirements mapping .............................................................................................................................................................5
4.2.4.1 Process ..................................................................................................................................................................................5
4.2.4.2 Printing...................................................................................................................................................................................5
4.2.4.3 Authorization..........................................................................................................................................................................5
4.2.4.4 Legal.......................................................................................................................................................................................5
4.2.4.5 Development...........................................................................................................................................................................5
4.2.4.6 Reporting................................................................................................................................................................................5
4.2.4.7 Interface.................................................................................................................................................................................5
5. REFERENCE.........................................................................................................................................................................................6
6. GAP ANALYSIS ...................................................................................................................................................................................6
6. BUSINESS PROCESS APPROVAL...................................................................................................................................................6
Page 1 of 6

2. Process code :
GFCL-SD-007 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 : Billing Version : 1.0 Date : 29.06.2006
1. Business Process Scope
Billing
Create > Change > Display
Page 2 of 6

3. Process code :
GFCL-SD-007 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 : Billing Version : 1.0 Date : 29.06.2006
2. Description of Business Process Flow
Direct Sales to Customers from Plant.
After completion of Goods Issue for the Delivery Documents at Shift Office, Billing is done through T
Code VF01 Delivery to be billed is entered in screen and saved for creation of Billing & Accounting
Document.
After completion of Billing, the Delivery Challan cum Tax Invoice is generated and printed through
VF31. (Screen shot given below)
For printing Delivery Challan cum Tax Invoice
Select the output type “RFER” (Invoice – Fertilizers)
Billing Document No. in the respective field is to be entered.
Enter processing Mode (“1” -first processing & 2 for reprocessing)
Press Execute.
Billing Document is printed.
Page 3 of 6

4. Process code :
GFCL-SD-007 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 : Billing Version : 1.0 Date : 29.06.2006
3. CLIENT Requirements
3.1 Process Requirements
3.2 Printing requirements
Delivery Challan Cum Tax Invoice for Plant dispatches on FOL
Invoices for dispatches from RMOs (1+2)
Sales Journal (1+1)
3.3 Authorization requirements
User specific. Available in SAP.
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
Page 4 of 6

5. Process code :
GFCL-SD-007 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 : Billing Version : 1.0 Date : 29.06.2006
(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.1 To-Be process flow description
(Describe process flow in To-Be scenario)
4.2.2 To-Be process flow chart
4.2.3 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.4 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.4.1 Process
4.2.4.2 Printing
4.2.4.3 Authorization
4.2.4.4 Legal
4.2.4.5 Development
4.2.4.6 Reporting
4.2.4.7 Interface
Page 5 of 6

6. Process code :
GFCL-SD-007 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 : Billing Version : 1.0 Date : 29.06.2006
5. Reference
Process No Process Description
Links to CLIENT process If applicable (any external
reference process
number, e.g. from ISO/
FDA etc.)
6. 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
6. Business Process Approval
By Date Comments
Page 6 of 6

7. Process code :
GFCL-SD-007 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 : Billing Version : 1.0 Date : 29.06.2006
5. Reference
Process No Process Description
Links to CLIENT process If applicable (any external
reference process
number, e.g. from ISO/
FDA etc.)
6. 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
6. Business Process Approval
By Date Comments
Page 6 of 6