SAP SD Blueprinting Document

1. Process code :
GFCL-SD-005
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 : Delivery & Goods Issue Version : 1.0 Date : 29.06.2006
1. BUSINESS PROCESS SCOPE ...........................................................................................................................................................2
2. DESCRIPTION OF BUSINESS PROCESS FLOW..........................................................................................................................3
3. CLIENT REQUIREMENTS ..............................................................................................................................................................4
3.1 PROCESS REQUIREMENTS....................................................................................................................................................... 4
3.2 PRINTING REQUIREMENTS ........................................................................................................................................................ 4
3.6 REPORTING 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 Organizational elements used .................................................................................................................................................5
4.2.5 Requirements mapping .............................................................................................................................................................5
4.2.5.1 Process ..................................................................................................................................................................................5
4.2.5.2 Printing ..................................................................................................................................................................................5
4.2.5.3 Authorization..........................................................................................................................................................................5
4.2.5.4 Legal.......................................................................................................................................................................................5
4.2.5.5 Development...........................................................................................................................................................................5
4.2.5.6 Reporting................................................................................................................................................................................5
4.2.5.7 Interface.................................................................................................................................................................................5
5. REFERENCE.......................................................................................................................................................................................5
6. GAP ANALYSIS ...................................................................................................................................................................................5
3. BUSINESS PROCESS APPROVAL...................................................................................................................................................6
1. Business Process Scope
DELIVERY & GOODS ISSUE
Create > Change >Display
Page 1 of 6

2. Process code :
GFCL-SD-005
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 : Delivery & Goods Issue Version : 1.0 Date : 29.06.2006
2. Description of Business Process Flow
Delivery against Sale Order at Plant (Road)
Sales Order created by RMO is processed through VL04 at Plant and Delivery Number generated by
the system automatically. Here we have two Selection options (1) Sales (2) Stock Transfers
• TALA is entered through ZTALA where initially we enter Time in
• Truck proceeds to Weigh Bridge for recording tare weight
• Truck proceeds to Bagging Plant for getting loaded with the stipulated Product & Quantity
• After completion of loading, truck returns to weigh bridge for recording gross weight to arrive
the net weight. If the weighment is found within tolerance limits, the truck will be released to
Distribution Shift Office for further processing like completion of TALA by entering Out Time by
Security on manual TALA.
• Delivery then attached to Truck Authorization & Loading Advice (TALA). Now, Time out
details, Tare & Gross weights & loading particulars are entered .
• Shift Incharge (Distribution) checks the details like product and quantity authorized by
him are loaded correctly. Delivery is then changed (VL02) enters the date of Goods Issue,
Picking Quantity, Way Bill No and Transporter in the system in line with manual TALA. Finally,
Goods issue is posted.
• Soon after goods issue, invoicing (Delivery Challan Cum Tax Invoice) is done through (VF01)
for the delivery posted. The invocing is done by entering the Delivery No; in VF01 screen and
by execution Invoice No. is generated.
• This Invoice is printed through VF31. and handed over to the Contractors’ Rep. and released
to Security Dept., for their checking and sending the truck out.
For direct dispatches from Plant, the Delivery No generated by the system will replace the manual
WRO entered in PO field in the Sale Order through back ground processing.
For RMOs, this procedure is not applicable.
The Number ranges for Plant dispatches starts with
Page 2 of 6
Despatch process

3. Process code :
GFCL-SD-005
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 : Delivery & Goods Issue Version : 1.0 Date : 29.06.2006
2. Description of Business Process Flow
Delivery against Sale Order at Plant (Road)
Sales Order created by RMO is processed through VL04 at Plant and Delivery Number generated by
the system automatically. Here we have two Selection options (1) Sales (2) Stock Transfers
• TALA is entered through ZTALA where initially we enter Time in
• Truck proceeds to Weigh Bridge for recording tare weight
• Truck proceeds to Bagging Plant for getting loaded with the stipulated Product & Quantity
• After completion of loading, truck returns to weigh bridge for recording gross weight to arrive
the net weight. If the weighment is found within tolerance limits, the truck will be released to
Distribution Shift Office for further processing like completion of TALA by entering Out Time by
Security on manual TALA.
• Delivery then attached to Truck Authorization & Loading Advice (TALA). Now, Time out
details, Tare & Gross weights & loading particulars are entered .
• Shift Incharge (Distribution) checks the details like product and quantity authorized by
him are loaded correctly. Delivery is then changed (VL02) enters the date of Goods Issue,
Picking Quantity, Way Bill No and Transporter in the system in line with manual TALA. Finally,
Goods issue is posted.
• Soon after goods issue, invoicing (Delivery Challan Cum Tax Invoice) is done through (VF01)
for the delivery posted. The invocing is done by entering the Delivery No; in VF01 screen and
by execution Invoice No. is generated.
• This Invoice is printed through VF31. and handed over to the Contractors’ Rep. and released
to Security Dept., for their checking and sending the truck out.
For direct dispatches from Plant, the Delivery No generated by the system will replace the manual
WRO entered in PO field in the Sale Order through back ground processing.
For RMOs, this procedure is not applicable.
The Number ranges for Plant dispatches starts with
Page 3 of 6
Despatch process

4. Process code :
GFCL-SD-005
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 : Delivery & Goods Issue Version : 1.0 Date : 29.06.2006
3. CLIENT Requirements
3.1 Process Requirements
3.2 Printing requirements
For Plant dispatch only
Delivery Challan Cum Tax Invoice – 1+4
Warehouse Transfer Order – 1+4
TALA – Manual pre printed 1+2
WALA – Manual pre printed 1+ 5
3.3 Authorization requirements
User specific.
3.4 Legal requirements
3.5 Development
3.6 Reporting requirements
ABAP reports list attached separately
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
Page 4 of 6

5. Process code :
GFCL-SD-005
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 : Delivery & Goods Issue Version : 1.0 Date : 29.06.2006
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)
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
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
Page 5 of 6

6. Process code :
GFCL-SD-005
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 : Delivery & Goods Issue Version : 1.0 Date : 29.06.2006
3. Business Process Approval
By Date Comments
Page 6 of 6

7. Process code :
GFCL-SD-005
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 : Delivery & Goods Issue Version : 1.0 Date : 29.06.2006
3. Business Process Approval
By Date Comments
Page 6 of 6