Scil SD BBP Final

Sitara Chemical Industries
Limited (SCIL)
Business Blue Print
SAP ECC 6.0 IMPLEMENTATION
Sales & Distribution Module
Prepared By:
Date: Rabi-us-Sani 07, 1429

14th April 2008
Contents
1 REVISION HISTORY ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 8
2 DISTRIBUTION LIST ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 8
3 BUSINESS BLUEPRINT AGREEMENT ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 9
4 INTRODUCTION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 10
4.1 OVERVIEW OF SALES AND DISTRIBUTION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 10
4.2 SCOPE OF IMPLEMENTATION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 11
4.3 LEGEND ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 12
5 SALES AND DISTRIBUTION ORGANISATIONAL STRUCTURE ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 13
5.1 SALES ORGANIZATION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 13
5.2 DISTRIBUTION CHANNEL ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 14
5.3 PRODUCT DIVISION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 14
5.4 SALES AREA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 14
5.5 INTERNAL ORGANIZATION IN SALES AND DISTRIBUTION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 15
5.6 SALES DISTRICT ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 18
5.7 SALES OFFICE ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 19
6 MASTER DATA MAINTENANCE ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 20
6.1 CUSTOMER MASTER DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 20
6.1.1 BUSINESS SPECIFICATIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 20
6.1.1.1 Chemical Division ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 20
6.1.1.2 Agri Division ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 20
6.1.1.3 Textile Division ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 21
6.1.2 SAP ENABLED BUSINESS PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 22
6.1.2.1 Salient Features of Customer Master Data ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 25
6.1.3 CONTROLS FOR MASTER DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 26
6.1.4 CUSTOMER MASTER CONFIGURATION DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 29
6.1.5 MATERIAL MASTER‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 29
6.2 CUSTOMER CREDIT MASTER DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 31
6.2.1.1 Chemical division ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 31
6.2.1.2 Agri Division ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 31
6.2.2 SAP ENABLED PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 31
6.2.2.1 Purpose of Credit Management ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 31
6.2.3 CREDIT EXPOSURE LIMITS DEFINITION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 34
6.3 CONDITIONS MASTER DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 35
Business Blue Print Document Page 2 of 248

6.3.1 BUSINESS SPECIFICATION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 35
6.3.1.1 Chemical Division ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 35
6.3.1.2 Agri Division ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 35
6.3.2 SAP ENABLED PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 37
6.3.2.1 Pricing Master Configuration Data ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 39
6.3.2.2 Condition Master‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 39
7 BUSINESS REQUIREMENTS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 41
8 END TO END BUSINESS SCENARIOS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 43
8.1 ORDER TO CASH ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 43
8.2 COMPLAINTS PROCESSING WITH CREDIT MEMO ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 45
8.3 RETURNS PROCESSING WITH CREDIT MEMO ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 47
8.4 RETURNABLE PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 49
A. CHEMICALS DIVISION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 51
1 BUSINESS PROCESS OF SALES AND DISTRIBUTION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 52
1.1 PRE‐SALES PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 54
1.1.2 INQUIRY PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 54
1.1.2.1 Process Flow ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 54
1.1.2.2 Process Description ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 54
1.1.3 QUOTATION PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 55
1.1.3.1 Process Flow ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 55
1.1.3.2 Process Description ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 55
1.2 SAP ENABLED BUSINESS PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 56
1.2.1 SAP QUOTATION PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 56
1.2.2 INQUIRY/QUOTATION PROCESSING CONFIGURATION DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 56
1.2.3 PRE SALES‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 56
1.3 SALES ORDER PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 59
1.3.1.1 Dealer Sales: Direct & through zone office ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 59
1.3.1.2 Institution Sales: Direct and through zones office ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 61
1.3.1.3 Exports Order Processing ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 63
1.3.1.4 Sales Through Pipeline: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 64
1.3.2.1 In‐direct Sales Order Processing (Sales & Distribution): ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 66
1.3.2.2 Direct Sale Process (Sales & Distribution) ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 68
1.3.2.3 Export Sale Process (Sales & Distribution) ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 70
1.3.2.4 Sales through Pipeline Sale Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 72
1.3.2.5 Tender Sales Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 73
1.3.2.6 Return Sales Order Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 74
1.3.2.7 Salient Features of Standard Order ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 75
1.3.2.8 Controls of Sales Order ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 77
1.3.2.9 Sales Order Processing Configuration Data: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 82

1.3.2.10 Sales Order‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 83
1.4 CREDIT NOTE & DEBIT NOTES ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 85
1.4.2.1 Salient Features of Credit Notes Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 87
1.4.2.2 Salient features of Debit Note Process. ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 88
1.4.2.3 Credit/Debit Memo Configuration Data: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 88
1.5 DELIVERY PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 91
1.5.1.1 Head Office Shipping Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 91
1.5.1.2 Karachi Office Shipping Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 94
1.5.2.1 Head office Shipping Process Description: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 97
1.5.2.2 SCIL Sales & Distribution Karachi Shipping Process Description: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 99
1.5.2.3 SCIL Sales & Distribution Through Shipping Process Description: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 101
1.5.2.4 Salient Features of Dispatch Note ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 103
1.5.2.5 Controls of Dispatch Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 104
1.5.3 DELIVERY PROCESSING CONFIGURATION DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 109
1.5.3.1 Shipping‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 109
1.6 BILLING PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 112
1.6.1 BUSINESS SPECIFICATIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 112
1.6.1.1 Invoice Process: Local Sales ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 112
1.6.2 SAP ENABLED PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 113
1.6.2.1 Billing Process Sales and Distribution Department: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 114
1.6.2.2 Salient Feature of Standard Billing ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 115
1.6.2.3 Controls of Billing ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 116
1.6.3 BILLING PROCESS CONFIGURATION DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 118
1.6.3.1 Billing‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 118
2 REPORTING REQUIREMENTS‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 121
2.1 STANDARD AND NON‐STANDARD SEGREGATION OF REPORTS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 121
3 SCRIPTS REQUIREMENTS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 122
B. AGRI DIVISION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 123
1 BUSINESS PROCESS OF SALES AND DISTRIBUTION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 124
1.1 PRE‐SALES PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 126
1.1.1 BUSINESS SPECIFICATION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 126
1.1.2 INQUIRY PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 126
1.1.2.1 Process Flow ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 126
1.1.2.2 Process Description ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 126
1.1.3 QUOTATION PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 127
1.1.3.1 Process Flow ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 127
1.2 SAP ENABLED BUSINESS PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 128
1.2.1 SAP QUOTATION PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 128

1.2.2 INQUIRY/QUOTATION PROCESSING CONFIGURATION DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 128
1.2.3 PRE SALES‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 128
1.3 SALES ORDER PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 131
1.3.1.1 Dealer Sales ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 131
1.3.1.2 Direct Sales ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 132
1.3.1.3 Retail Sales ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 134
1.3.1.4 SAP Enabled Business Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 135
1.3.1.5 In‐direct Sales Order Processing (Sales & Distribution): ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 136
1.3.1.6 Direct Sale Process (Sales & Distribution) ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 138
1.3.1.7 Retail Sale Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 140
1.3.1.8 Return Sales Order Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 142
1.3.1.9 Salient Features of Standard Order ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 143
1.3.1.10 Controls of Sales Order ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 145
1.3.1.11 Sales Order Processing Configuration Data: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 150
1.3.1.12 Sales Order‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 151
1.4 CREDIT NOTE & DEBIT NOTES ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 153
1.4.2 SAP ENABLED BUSINESS PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 154
1.4.2.1 Salient Features of Credit Notes Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 155
1.4.2.2 Salient features of Debit Note process. ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 156
1.4.2.3 Credit/Debit Memo Configuration Data: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 156
1.5 DELIVERY PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 158
1.5.2.1 Shipping Process:‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 162
1.6 BILLING PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 172
C. TEXTILE DIVISION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 184
1 BUSINESS PROCESS OF SALES AND DISTRIBUTION ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 185

1.1 PRE‐SALES PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 187
1.1.2 INQUIRY PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 187
1.1.2.1 Process Flow ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 187
1.1.3 QUOTATION PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 188
1.1.3.1 Process Flow ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 188
1.2 SAP ENABLED BUSINESS PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 189
1.2.1 SAP QUOTATION PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 189
1.2.2 INQUIRY/QUOTATION PROCESSING CONFIGURATION DATA ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 189
1.2.3 PRE SALES‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 189
1.3 SALES ORDER PROCESSING ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 192
1.3.1.1 Agent/Direct Sales ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 192
1.3.1.2 Indirect Sales from Karachi Office: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 193
1.3.1.3 Institution Sales ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 194
1.3.1.4 Retail Sales ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 196
1.3.1.5 SAP Enabled Business Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 197
1.3.1.6 In‐direct Sales Order Processing (Sales & Distribution): ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 198
1.3.1.7 Direct Sale Process (Sales & Distribution) ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 200
1.3.1.8 Retail Sale Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 202
1.3.1.9 Return Sales Order Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 204
1.3.1.10 Salient Features of Standard Order ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 205
1.3.1.11 Controls of Sales Order ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 207
1.3.1.12 Sales Order Processing Configuration Data: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 212
1.3.1.13 Sales Order‐VALUE ADDITIONS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 213
1.4 CREDIT NOTE & DEBIT NOTES ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 215
1.4.2.1 Salient Features of Credit Notes Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 217
1.4.2.2 Salient features of Debit Note process. ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 218
1.4.2.3 Credit/Debit Memo Configuration Data: ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 218
1.5 DELIVERY PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 221
1.5.1.1 Shipping Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 221
1.5.1.2 Karachi Office Shipping Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 223
1.5.2.1 Shipping Process ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 226
1.5.2.2 Shipping Process Karachi ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 228
1.6 BILLING PROCESS ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 237


1 Revision History
Revision History
Date Prepared By Reviewed By Ver No. Comments
Saturday,April 12, 2008 Zia & Shoaib Tahir Lodhi 1.0 1st Review
Monday, April 14, 2008 Tahir Lodhi Shahzaib Siddiqi 2.0 2nd Review
Tuesday, April 28, 2008 Shahzaib Siddiqi Muhammad Moin 3.0 3rd Review
Wed ,April 30, 2008 Tahir Lodhi Shahzaib Siddiqi Final Final Review
2 Distribution List
Distribution List
Mr. Muhammad Azam Butt

Deputy General Manager Marketing
Chemical Division
Mr. Asad Rathore

Sales & Marketing Manager
Chemical Division
Mr. Chaudhry Naeem Raza

Deputy General Manager Marketing
Agri Division
Mr. Iqbal
Sales and Marketing Manager
Textile Division
Mr.Ather Mujhaid
Project Manager
Sitara Chemicals Industries Limited
Mr. Inayat. U. Koreshi

Partner (BTS-SAP) & Project Director
Abacus Consulting
Shahzaib Siddiqi
Project Manager
AbacusConsulting
Mr. Muhammad Moin

Assistant Vice President
Abacus Consulting

3 BUSINESS BLUEPRINT AGREEMENT
Signing this document records SCIL agreement to the contents of this Business Blueprint,
and confirms that the remainder of the project can proceed.
SCIL Acceptance & Approvals

Name Position Date Signature
Shahzaib Siddiqi Ather Mujhaid

Project Manager Project Manager
AbacusConsulting SCIL

4 INTRODUCTION
The objective of the Business Blue Print document is to present To Be SAP enabled
business processes for SCIL Sales and Distribution function that will be carried out in
Chemicals, Agri and Textile divisions.
The document contains proposed organizational structure that will be defined in the SAP
system, this include definition of sales organization , distribution channel, production division,
sales area, internal organization in sales and distribution, sales district and sales office.
This documents is the hybrid of SAP business process and technical specification that would
be defined and configured into the Development, Q/A and Production systems. Input and
consensus of the nominated power users were taken for the finalisation of Organizational
structure and Business Processes.
The scope of this document is restricted to the following standard SAP Business processes:
Pre sales processes, Sales order processes, Shipping process, Billing process.
The submission and approval of this document marks the completion of the Blue print Phase
of our SAP implementation at SCIL
4.1 Overview of Sales and Distribution
The design of the Sales and Distribution module emphasis on using sales strategy that is
sensitive to the market. As a priority of the Parameterization in Sales and Distribution
module is to set up a data structure that can record, analyze and control the activities that
will satisfy customers and produce adequate profit over the next accounting period and into
future.
The Sales and Distribution module provides a set of master data records and a system of
documented business transactions. The standard business programs of Sales and
Distribution module are organized around, master data, sales support, Sales, shipping and
billing. These activities represent value-adding processes because SCIL can lose value in
terms of reputation and in financial terms if any of them is allowed to perform badly.
The Sales and Distribution’s Sales Information System will allow SCIL to gain insight on all
matters concerning prospecting, sales and deliveries. The feature of display and flexible
access to the master records and transaction data allows statistical analyses and evaluation
of decision-making and strategic planning.

4.2 Scope of Implementation
This document describes the business process flows and activities for the following:
1. Sales
o Maintenance of Master Data

o Inquiry, Quotation & Contract Processing
o Sales Order Processing
o Availability Check
o Discount & Credit Control
2. Shipping
o Delivery Processing
o Goods Issue
3. Billing
o Billing Request processing

o Credit Memo Procedures
o Debit Memo Procedures

4.3 Legend
The following describes the symbols used in the process map:
Start Process Decision
Activity step Document
Display Transfer out of

module scope
Preparation Data
Out of system Start

Terminate Process Process
Out of system Out of system

document Activity step
Out of system
decision

5 Sales and Distribution Organisational Structure
Sales and Distribution Organisational Structure – SAP Perspective
Following portrays the structural organization and special features of Sales and Distribution
for SCIL. In the SAP, several structures can be used to represent the legal and
organizational structure of the company. Organization elements can be structured from the
point of view of accounting, materials management, and sales and distribution. It is possible
to combine these structures. The organizational structures form a framework in which all
business transactions can be processed.
Figure 1: Overview of Sales and Distribution External Structure
5.1 Sales Organization
An organizational unit subdivides an enterprise according to the requirements of sales. A

sales organization is responsible for the sale and distribution of goods and services. Each
business transaction is processed within a sales organization that must be specified in all
sales documents. It is available for all basic functions of SD (such as pricing, availability,
etc.)
Sales Organization Description

1000 SCIL

5.2 Distribution Channel
The distribution channel defines how different Materials reach to the customer. For example
local, export or wholesaler In SCIL we have four distribution channels which are given below.
Distribution Channel Description

10 Exports
20 Direct Sales
30 In-Direct Sales
40 Retail Sales
5.3 Product Division

A broad product range that could be sub divided into further grouping of products.
Division Description
10 Basic Chemicals
20 Speciality Chemicals
30 Agri
40 Yarn
50 PVC
99 Miscellaneous
5.4 Sales Area

SD is organized according to sales organization, distribution channel and division. A
combination of these three organizational units forms the sales area in SCIL, we have 18
sales areas which are given below.:
Sales Organization Distribution Channel Division

1000 10 10
1000 10 20
1000 10 50
1000 10 99
1000 20 10
1000 20 20
1000 20 30
1000 20 40
1000 20 50
1000 20 99
1000 30 10
1000 30 20
1000 30 30
1000 30 40
1000 30 99
1000 40 30
1000 40 40
1000 40 99

5.5 Internal Organization in Sales and Distribution
The internal organizations in Sales are represented by the elements like sale district, sales
office and sales group and sales town.
Figure 2: Overview of SCIL Sales and Distribution External Structure

5.6 Sales District
A geographical sales district in (SCIL deemed as sales regions) where it will plan, execute
and analyze each step of sales activities and ground level marketing and make different
discussion on the basis of data received. SCIL will assign customers to a sales district and
later use the sales district to generate sales statistics.
These Sales District are maintained for SCIL considering the growth of sales and in case of
increase in sales offices internal organization could be developed flexible so that additional
sales office could be maintained under Sales District.
S.NO Sales Districts Description

Chemicals Sales Districts
01 100000 Punjab
02 200000 Sindh
Agri Sales Districts
01 100000 Punjab
02 200000 Sindh
Textile Sales Districts
01 100000 Punjab
02 200000 Sindh

5.7 Sales Office
A sales office establishes contact between the Institutions, Dealers and SCIL Staff under the
instruction of sales districts. It monitors SCIL sales in the market, which is done by SCIL
sales force. It also resolves all issues between Customer and SCIL.
S.NO Sales Offices Description

Chemicals Sales Offices
01 1000 Lahore
02 2000 Faislabad
03 3000 Gujrawala
04 4000 Multan
05 5000 Islamabad
06 6000 Hyderabad
07 7000 Karachi
Agri Sales Offices
01 2000 Faislabad
02 4000 Multan
03 8000 Rahim Yar Khan
04 9000 Sahiwal
05 9100 Toba Tek Singh
06 9200 D.G.Khan
07 6000 Hyderabad
Textile Sales Office
01 2100 Faislabad Office
02 2200 Mill Office
03 2300 Yarn Market
04 7000 Karachi

6 Master Data Maintenance
6.1 Customer Master Data
6.1.1 Business Specifications
6.1.1.1 Chemical Division
There are 4 customer types in the current system for chemical division.
• Institutions
• Agents
• Direct Customers
• Export
¾ Institutions
Customers off SCIL chemical division include industrial customers who place orders directly
and indirectly. These customers are given discounts and rebates due to their regular
purchases and huge volumes over certain period of time. Some of these customers are
given better prices, due to their ongoing relationship with SCIL. Institutions can place their
orders at head office or regional offices.
¾ A ge n ts
SCIL chemical division, in order to reach different regions and cater to customers with
smaller orders has appointed some dealers as their agents who order the SCIL products on
behalf of these customers. These agents are responsible for the payments delay if any and
there fore receive performance based discounts and rebates.
¾ D i r e c t Cu s to m e r s
Direct customers place their orders directly at SCIL head office sales and marketing
department and the sales process is complete within the SCIL head office.
¾ Ex p or t C u st om e rs
Export Sales are done through Agents specified as export Agents.
Export products are packaged in cardboard boxes with specification printed stickers. Agents
play a major role in the sale of Textile division sales.
Export Sales process in Textile:
• Inquiries by mail
• Agent contacts Export Sales office with foreign customers query.
• Cost sheet for export is prepared by finance department
• Cost sheet is approved by CEO
• L/C based sales 120 days terms are made.
• Standard export sales process follows.
6.1.1.2 Agri Division
There are three customer types in the current system for Agri Division
Direct customers place their orders directly at SCIL Faisalabad sales and marketing
department.

¾ Dealers
Agri Division has authorized dealers in different parts of Punjab region and one in
Hyderabad.
¾ R e ta il
Retailing facility is available to Agri division customers.
6.1.1.3 Textile Division
Three types of customers for Textile division
• Corporate
• Retail
• Export
Cash Sales are made from Faisalabad Godown. Sales basis on customer to customer basis:
• Advance payments
• Credit Sales
¾ Ex p or t C u st om e rs
Export Sales are done through Agents specified as export Agents.
Export products are packaged in cardboard boxes with specification printed stickers. Agents
play a major role in the sale of Textile division sales.
Export Sales process in Textile:
• Inquiries by mail
• Agent contacts Export Sales office with foreign customers query.
• Cost sheet for export is prepared by finance department
• Cost sheet is approved by CEO
• L/C based sales 120 days terms are made.
• Standard export sales process follows.
Direct customers place their orders directly at SCIL head office sales and marketing
department.
¾ R e ta il Cu st o m e rs
Retailing facility is available to both Textile and Agri division customers but not chemical
division. Retail customers are served from Faisalabad office.

6.1.2 SAP Enabled Business Process
¾ S AP C u s t o m e r Ma s te r Pr oce s s D ef in i t io n
Each person or company bought from SCIL in the past or is accorded the status of a
prospective customer, because SCIL have a responsible expectation that the person or
company will purchase from SCIL in future is represented by a master record. The customer
master record stores the following data types:
• General data
• Company code data
• Sales Area Data
¾ Ge ne ral Dat a
is maintained for every customer. Examples of General data would include Name, Address,
Telephone Numbers, Fax Numbers, Email Address, Contact Persons, Sales tax registration
number, Customer group etc.
¾ Company C ode Data

Company code data is related to the Company Code Organization of the company. It is
defined individually for each CC. Examples of CC Data would include Payment terms,
Reconciliation accounts, Information on Insurance, Account Management, Withholding Tax
Data etc. The accounting department primarily inputs this data.
¾ Sales Area Data

Sales & Distribution Data is related to the Sales Area. This data only applies to one sales
area and therefore is dependent on the sales structure.
Sold-to-Party
The person (Legal / Actual) who actually orders the goods.
Ship-to-Party
The person (Legal / Actual) who actually receives the goods.
Bill-to-Party
The person (Legal / Actual) who actually receives the invoice.
Payer
The person (Legal / Actual) who actually settles the invoice.
Sales Manager
The person (Legal / Actual) who is actually responsible for sales.
The system standard customer master record represented by sold-to-party, ship-to-party,

bill-to party and payer. SCIL can limit the screens and fields accessed in the customer
master record so that only the necessary data is entered and that can be done through
account groups. The function of a customer is defined by assigning an account group.

¾ Custome r ma ster d a ta ma intena nce
Activities for customer master data maintenance will be done by Sales and Marketing
where-as SCIL Sales & Distribution, Group marketing department will give all customer
related information to account department .
Process Flow:
Process Description
1. Sales and marketing department collect customer related information
2. Sales and Marketing assistant check if the customer already exists in the system.

3. If customer already exist then sales assistant change master data information if
required.
4. If customer don’t exist in the system then sales assistant create customer master
date in the system
¾ C r e a te N e w C u s t om e r
New customers master data will be created using SAP transaction code XD01 or SAP
standard menu path:
Logistics > Sales and Distribution > Master Data > Business Partner > Customer > Create >
Complete.
During creation of Customer data following views have to be maintained:
General Data: It will be used to record general data of customer such as address, phone
number, contacts number etc.
Company Code Data: It will be used to record data of customer related to financial
accounting such as reconciliation account, sales tax etc.
Sales Area Data: It will be used to record data of customer related to Sales and Distribution
transaction such as data for sales process, shipping process, billing process and partner
function. All critical fields maintained in the system are set as mandatory fields, so that users
could easily be able to identify necessary data key fields.
¾ U pda t e /C ha n ging e x is tin g C u sto m ers

Any changes on existing customer master data will be maintained in the SAP system. All
changes in customer master data will not effect historical transactions. SCIL can change
customer master data in two ways for sales and distribution and centrally.
Customer Master Data will be updated using SAP transaction code XD02 or SAP standard
menu path:
Logistics > Sales and Distribution > Master Data > Business Partner > Customer > Change
> Complete
Mass processing can also be done if many customers need to be updated in one process via
SAP transaction code: XD99 or SAP standard menu path:
Logistics > Sales and Distribution > Master Data > Business Partner > Customer Master
Mass Maintenance.
¾ R ef er e nc e f o r C us to m er M a s t e r R e c o r d C r e a t i o n
If a new customer master record require to be created, for which similar data already exists
in any other customer master data, SCIL will create with functionality of creation customer
master data with reference, this will reduce the effort required to create the new master
record.
During creation of master data with reference, if SCIL enter only the customer number in the
reference section, the system will copy only the general data into the new customer master
record. If SCIL also enter data on the sales area, the sales and distribution data will also be
copied. Only data, which can be identical for both master records, is copied. For example,

address is not copied, while country, language and account group are. SCIL can change all
copied data.
¾ D e l e t i o n / B l o c k e x is t i n g C us to m er s
SCIL can mark a customer master record for deletion if, for example, SCIL no longer
maintains business relationships with the customer, by using the deletion indicator SCIL can
mark the customer master record. The master record is only deleted after all dependent data
has been deleted.
To mark a customer master record for deletion, use the following steps:
In the Sales and Distribution master data screen select, Business partners > Sold-to Party >
Mark for deletion.
The deletion indicator can be recognized by warning and error messages (for example,
when entering a sales order). SCIL can cancel a deletion indicator in a customer master
record by removing the indicators. To do this, proceed exactly as if SCIL wanted to set a
deletion indicator.
Similarly a customer master record can be blocked, for example, when SCIL want to
temporarily stop business relations with a customer. To block the customer master record of
a sold-to party, for example, use the following steps. In the Sales and Distribution select,
¾ B us in es s pa r tn er s > Cu s to m er h iera r chy > Bl o ck

SCIL can cancel a block in a customer master record by removing the block indicators. To
do this, proceed exactly as if SCIL wanted to set a block.
6.1.2.1 Salient Features of Customer Master Data

The salient features of the Customer Master Data are discussed as below:
• Four Functions are available which are:

Sold to Party - The person (Legal / Actual) who actually orders the goods.
Ship to Party - The person (Legal / Actual) who actually receives the goods.
Bill to Party - The person (Legal / Actual) who actually receives the invoice.
Payer - The person (Legal / Actual) who actually settles the invoice.
In most cases all the four functions are the same. So when sold to party is created, all other
functions would be automatically created. We can create more than one ship to party /
Consignee for one sold to party / Customer.
• Sales & Marketing Manager responsible for that customer will be stored in customer
master partner data.
• Industry will also be maintained in the customer profile.
• System will always assign a unique internally generated 5-digit number to each customer
created.
• All customers would be created for a sales area, which comprises the sales organization,
distribution channels and the divisions.
• Regions will be maintained for every customer. The following two regions have been
identified and will be available in the new system,
1. Punjab

2. Sindh
• Sales tax status and registration numbers will be maintained in a optional field. Business
will maintain Customers sales tax registration no. in the provided field for every
registered customer, NA for the registered whose ST registration no is not known and
NIL for unregistered customer.
• Incoterms and Payment terms will be maintained wherever applicable. This information
will be copied to subsequent documents (Quotation/Sales order etc )
6.1.3 Controls for Master Data
¾ A d din g C us to m er s
Control Objective
Controls should be in place to ensure that the ability to add customers to the customer
master file is limited to appropriately authorized personnel. Control over who can create
customers should exist through security access.
Suggested Procedures
Appropriate security restrictions should be implemented by configuring appropriate
authorization objects, that would control access to add customers Centrally and in the
Accounting and Sales views.
This control should be implemented at the time of roles and user profiles design.
¾ C om p le t io n
Control Objective
Controls should be in place to ensure that new customer data is complete.
Report RFDKAG00, the ‘customer comparison’ report can list all customers set up in a sales
area that have not been set up in accounting (alternatively it can list all customers set up in
accounting which are not in a sales area).
The SAP process owner should do monthly review of this report in order to ensure that
customer records are complete and all views have been created.
¾ Duplication
Control Objective
Controls should be in place to prevent duplicate customers from being added to the
customer master file. SAP does not allow duplicate customer numbers. However, it is still
possible to enter the same customer record twice. Customer records will be created first by
the sales & marketing departments and then the accounting data will be added by the
finance department.
Report RFDKVZ00, the “New Customer Audit Trails” which provides a list of customers, can
be used to prevent duplication of customers.
This report should be reviewed by the SAP process owner on monthly basis.

¾ Multi ple Delive r y Addre s s
Control Objective
Controls should be in place to ensure that the assignment of multiple delivery addresses to
customers is reviewed and approved.
Multiple delivery addresses can be set up by creating new customers and completing the
alternative payer field. The invoice is sent to the alternative payer. An alternative is to use
‘ship to’ addresses. The control applied should be a review of audit trails in the same way as
the creation of new customer records.
All customers set up as ‘ship to’ can be listed using report RFDKAG00 ‘Customer
Comparison’ and selecting the account groups set up for ‘ship to’ customers.
The SAP process owner should review the report on a monthly basis.
¾ N u m b e r R a n g es
Control Objective
Control should be in place to ensure that customers may only be assigned customer
numbers within approved number ranges. SAP allows number ranges to be internally or
externally assigned. More controls can be applied to numbers that are internally assigned.
It is recommended that internal assignment of customer account numbers is used as it offers
the additional control of accounting for the completeness of vendor accounts in reporting and
analysis since account numbers are sequential. If external vendor account number
assignment is allowed, there is a chance that standard naming conventions may not be
followed, and all numbers in the range not being assigned.
¾ C on v e r s i o n of P r o s p ec ts t o Cu s t o m e r s
Control Objective
Controls should be in place to ensure that the ability to convert prospects to customers is
limited to authorized personnel. Although the company is currently not using the option of
prospective customers, however, following procedures are recommended for conversion of
prospects to customers, if used in future.
Controls over creating customers should not be bypassed when converting prospects to
customers. A sales prospect and a sales customer both require authorizations over objects.
These objects should be appropriately configured in order to control access.
These controls should be implemented at the time of the roles design and creating user
profiles.
¾ Au th o r iza t io n a n d Rev i e w of C ha n g es
Control Objective
Controls should be in place to ensure that only authorized personnel have the ability to make
changes to the customer master. Control over who can make changes to the customer
master should exist, in particular the accounting views where payment date is input.

Access control over the appropriate authorization check object should be set in at the time
of role design and creation of user profiles.
Audit trails of changes are available - via transaction FD04 for individual changes or by
report RFDABL00 for all changes in a particular company, sales organization, over a
particular period.
Monthly review of this report by SAP process owners is recommended.
¾ A l t er a ti o n of C r e d i t L i m i t
Control Objective
Controls should be in place to ensure that the ability to create/change customer credit limits
is restricted to authorized personnel. It is important that ‘credit control area’ has been
properly defined in sales area by the SAP Process Owner.
• The objects required for authorization to create/change limits should be appropriately
configured in order to control access.
• These control objects should be implemented at the time of roles designs and user
profiles.
• Credit limits for all customers can be reported using report RFDKLI40 - Credit Overview.
• Monthly review of the report by the SAP process owner is recommended.
• Changes to the credit limit for a specified customer can be displayed, including the user
id of the person making the changes.
• Monthly review of the report by the SAP process owner is recommended.
¾ Deletion
Control Objective
Control should exist to prevent deletion of customer accounts while there are still
outstanding transactions. Customers cannot be deleted if there are any open items and if
there is any balance on the account in the previous month.
Only authorized staff should flag customers for deletion. The appropriate objects should be
configured to control access to this function.
¾ T e r ms a n d C on d i ti o ns
Control Objective
Controls should be in place to ensure terms and conditions offered are consistent with
management guidelines.
Suggested Procedure
The terms and conditions should be reviewed on a quarterly basis by an appropriate level of
management in order to ensure that they are in line with the management guidelines.
¾ Ba nk in g D a ta
Control Objective
Banking data is created/changed and deleted only by authorised staff.

The appropriate objects allowing create/change access to banking data should be
configured to control access. This control should be set in at the time of roles design and
creating of user profiles.
6.1.4 Customer Master Configuration Data

Taking into consideration the SCIL requirement following account groups are maintained
along-with the system internal number ranges allocated to them for maintenance of
Customer Master Data:
Account Group Description Number Ranges

Sales & Distribution
Agents are assigned by SCIL for
different regions. These agents can 100000- 199999
Agents
place orders directly at Faisalabad
or any of the regional offices.
These act like agents but are 200000-299999
Brokers
temporary mostly for single order.
Local customers are from 300000-399999
Local Customers Faisalabad who directly place orders
at Faisalabad sales office.
Export customers who place orders 400000-499999
Foreign
directly but are routed using an
Customers
export agent.
Permanent customers of SCIL who
Institutional place make-to-order most of the 500000-599999
Customers times and contracts are used for
these customers.
Retail Customer for Agri and Textile 600000-699999
Retail Customers who buy small quantity directly from
shop or factory outlet
700000-799999
Others All Other Customers
6.1.5 Material Master-VALUE ADDITIONS

• SAP system has one of the most enhanced master data management systems and
organizes data on a single platform. Master data may be created discretely at remote
locations however system accumulates all data in the central master data repository.
For SCIL Account Groups have been maintained to provide a consistent number range
for the customers created in the system, enabling unique identification of the customer
and homogenize master data maintenance.
• Standard SAP provides enhanced master data management capability that allows
maintaining customer specific data at three levels. The customer master data
components are copied into sales documents whenever a customer is called in the
document. All or any customer related values maintained in the master could be copied
into the sales document.

• All customer codes will be created as subsidiary ledger account to a natural account
code of trade receivables, which will considerably reduce trial balance maintenance.

6.2 Customer Credit Master Data
6.2.1.1 Chemical division
In SCIL credit management exist but not practiced firmly. Sales and Marketing department
checks the Credit history of customer before taking the order. Sales and marketing
department have the authority to bypass the credit limit block set by finance if needed.
In Agri Division credit management exist but not practiced firmly. Sales and Marketing
department checks the Credit history of customer before taking the order.

In SCIL credit management exist but not practiced firmly. Sales and Marketing department
checks the Credit history of customer before taking the order. Sales and marketing
department have the authority to bypass the credit limit block set by finance if needed.
6.2.2 SAP Enabled Process
This section aims to provide the users with a complete overview Of Credit Management in
SAP
6.2.2.1 Purpose of Credit Management
Outstanding receivables or bad debts can have a substantial effect on the success of a
company, but with the aid of Credit Management, the risk can be minimized by defining
specific credit limits. Thus the authorities can take the financial pulse of a Customer or group
of customers, and enhance their credit-related decision-making. There will be Four Credit
control Areas in SCIL.
Salient Features of Customer Credit Management
Information Required Triggers

Customer Number SAP generated customer number
Customer address Replicated automatically from master data
Credit Limit Approved credit limit of the customer
Credit Days Approved credit days of the customer
Credit Exposure Will be calculated automatically. Formula discussed below
Credit Exposure % Will be calculated automatically
It is imperative to understand the methodology of credit exposure calculation in SAP. The

formula used in SAP for exposure calculation is as follows

Credit Exposure = Accounts Receivable + Open Sales Orders.
This can further be explained by the following example:
Customer Name: ABC

Credit Limit: Rs. 100,000
Accounts Receivable: Rs. 90,000
Open Sales Orders: Rs. 6,000
This means that sales orders worth Rs This means that dispatches worth
6,000 have been made for this Rs 90,000 have been made for
customer, but the dispatch and the Bata Industries and the customer
invoicing has not taken place. has been invoiced for this amount
Credit Exposure = Rs. 96,000

Credit Management Process Flow
The following subsection will provide with an overview of the credit management process to
be followed in SAP:
Credit Management Sales & Distribution, Financial

Accounting
Definition of Credit Master Data
Create Sales Order
Customer Bata Industries
Credit Limit Rs 100, 000

Credit Limit Used Rs 90,000
Sales Order Number 100

SAP Mail Box Gross Value Rs 15,000
Order Blocked
Clearing & Release
Credit Information System Dispatch, Invoicing

Credit Manager Contacted Customer Invoiced
Sales Order Released

Process Flow
1. Sales Order is entered in the system.
2. Assuming that this sales order leads to the credit limit being exceeded for this
customer, the system outputs a warning message, but does not prevent SCIL from
saving the order. It blocks the order.
3. If the order is blocked, the credit representative processes the blocked order from
a list of blocked sales and distribution documents.
4. The credit representative now decides if the additional credit should be granted, as
per the authorized limits.
5. The credit representative can release the Blocked Sales Order if he has the
necessary authorization. (Credit Control Area / Risk Category (Customer Rating) /
Credit limit % used)
6. Credit approval levels can be maintained by assigning different percentage credit

limit used factor to different Credit Roles. And only the person with necessary
Role/Authorization can release Sales Orders in different Credit exposure ranges.
7. Alternative Credit representative personnel/authorities will be maintained to

address the cases when front line credit representative is not available or out of
reach.
8. Once the credit representative releases the Sales order, a delivery can be created
and a billing document generated. Once SCIL have saved this document, the
accounting department will post this document and hence a financial accounting
document will be generated.
9. The customer pays the invoice that SCIL created in the previous step. SCIL then
post the incoming payment in Accounts Receivable (FICO).
Prerequisites
• Credit control areas (CCA) will be defined and assigned to each Sales Area.
• The credit data (credit limit and risk category) for the customers will be maintained in
Customer credit control data by the authorize personnel. In SCIL Accounting department
will be responsible of doing and maintaining this activity in the system.
6.2.3 Credit Exposure Limits Definition
The business has to decide the exposure limits definition in SAP. This means, that the
percentages up to which the credit managers would be allowed to release the sales orders.
Credit Manager Exposure in % (Over and Above the Credit Limit)

Manager Up till 20%
General Manager Up till 50%

6.3 Conditions Master Data
6.3.1 Business Specification
6.3.1.1 Chemical Division
Pricing for chemicals is controlled by finance department. Discounts are value and quantity
based depending on customer and material.
Following is the Structure of Chemical Pricing
Unit Price xxx

Trade Discount xxx
Delivery Charges xxx
Sales tax xxx
Excise Duty xxx
Rebate xxx
Net Price xxx
¾ Incentives
Rebates
Different rebates are given to customers on product quantity, monthly volume of sales orders
as per the value of sales orders in a specific period of time. In time payments of due amount
also make a customer eligible for rebate.
Discount
Discounts are only for sales order based on minimum order quantity for discount allowance.
Commission
Dealers are paid commission on the value of the order. Commission is not mentioned on the
invoice. Calculated on monthly basis and adjusted in bills.
They follow backward pricing procedure to calculate basic price. Offered Price may vary by
customer to customer and incorporates different discounts on product basis. Different
discounts and rebates are offered to customer. Transportation of goods is not SCIL’s
responsibility but freight is included in basic price of the product, according to the
transportation zone.
Even though products are sold in small packaging of 1,2,3 liters still sales are recorded on
net weight basis, i.e. Gross weight less net weight less packaging weight.
Following is the Structure of Agri Division Pricing
Unit Price Xxx

Freight Xxx
Discount (xxx)
Gross Price Xxx
Sales Tax 15%
S.E.Duty 1%
Agent Commission Xxx
Net Price Xxx

¾ F r e ig h t tr ea t m e n t i n A g r i D iv is i on .
1. Commercial Vehicles
2. SCIL vehicles
Both the freights are treated same in Invoice processing.

Discounts Base is same for both Agri and Chemical Division products, i.e,
1. Customer
2. Product
3. Value
4. Quantity
¾ Incentives
Rebates
Different rebates are given to customers on product quantity, monthly volume of sales orders
as per the value of sales orders in a specific period of time. In time payments of due amount
also make a customer eligible for rebate.
Discount
Discounts are only for sales order based on minimum order quantity for discount allowance.
Commission
Dealers are paid commission on the value of the order. Commission is not mentioned on the
invoice. Calculated on monthly basis and adjusted in bills.
For Textile prices totally depends on yarn market movement. Offered Price may vary by
customer, Depends on negotiation with the customer. No discount or rebates are offered to
customer. Transportation of the goods is customer’s responsibility (in case of retail) so no
freight is charged to customer. For yarn sales, sales Tax is 0% based.
Following is the Structure of Textile Pricing
Unit Price xxx

Sales tax 000
Agent Commission xxx
Net Price xxx
Freight for the consignment is decided at the time of contract.

Pricing is done almost daily on demand and supply basis.
After the sale of yarn if the product is still not moved by the customer then a charge of 2Rs.
per bag is charged in the system, but in practice this is not followed due to very competitive
market.
¾ Incentives
Textile division do business with different agents for different orders. There is no process of
registration of agents, and these change with order to order. Different agents are on different
scales of commissions and discounts on performance basis as per quantity and month wise
sales orders. Discounts are for agents and only on sales order. Dealers and agents are paid
commission on per unit value of the order. Commission is not mentioned on the invoice.

¾ S AP C o n d i ti o n Ma s t e r P r oce s s D e f in i ti o n
The term condition master data/records allow SCIL to store and retrieve pricing information
in the system. All the pricing elements of SCIL daily business - the prices, discounts,
surcharges for freight and taxes - that SCIL want to use for automatic pricing will be stored in
the system as condition records. SCIL can define as many condition records, as it wants for
the different pricing elements for any validity period.
Conditions represent a set of circumstances that apply when a price is calculated. For
example, a particular customer orders a certain quantity of a particular Material on a certain
day. The variable factors here could be - the customer, the Material, the order quantity, and
the date (Key combination at the time of generating sales orders). The information about
each of these factors can be stored in the system as master data. This master data is stored
in the form of condition records.

Process flow
Activities for Condition master data maintenance will be done by SCIL Accounting
department responsible users.
SCIL needs to create condition records for all the pricing elements that the system takes into
account during the automatic pricing. These conditions could be of prices, commission and
certain valid period. During document processing, the system transfers data from the
condition records and determines the amounts for individual pricing elements and the final
amount for the sales document.
SCIL could maintain fix prices for chemicals and Agri whereas manual pricing will be used
for Textile. SCIL can maintain discounts for variable net prices, so that analysis could be
made available about organization and group of customer availing discounts etc.

Master data for pricing can be maintained under the Key combinations of the following fields:
• Sales Organization
• Distribution Channel
• Division
• Sales District
• Sales Office
• Customer Group
• Sold-to Party
• Material Number
6.3.2.1 Pricing Master Configuration Data
The following pricing types will be maintained for SCIL in pricing master data:
Condition Types Description
PR00 Pricing Condition Type
K004 Material Discount
K005 Customer / Material Discount
K007 Customer Discount
R100 100% discount (for Free of Charge Delivery)
KF00 Freight
MWST Output Tax
MWAS Special Duty
VPRS Internal Price (Statistical Condition)
6.3.2.2 Condition Master-VALUE ADDITIONS
• SAP comprehensive pricing module will provide you with an advanced, more flexible,
matrix based and centrally maintained price and conditions maintenance system.
Fully automatic price and conditions determination at each and every transaction.
• SAP system enables the user to maintain the validity period for each condition to
signify their effectiveness for a set period.
• System will not only copy the centrally maintained conditions, after determination, on
transaction but will also allow them to be changed at time of order and quotation, if
user is authorized.
• SAP system will allow ease of maintaining conditions as master data. Here
conditions represent a set of circumstances that apply when the price will be
calculated. These conditions will be based on variable factors which are used to

determine the final price a customer shall get. The factors may be the product, the
order quantity and the date.
• Cost and profit margin will be recorded and displayed for each transaction and thus
allow the user to assess the real time profit earned from a sales order at the time of
booking the order.
• Three tier condition records will be maintained for SCIL to distribute discount
percentages on the basis of designation. Each condition type will be assigned to a
user (for such control appropriate authorities should have their personal user account
on the SAP system), however to update the discounts each user will have to access
the system from their own username in order to provide the customer desired level of
discount.
• If the need be special prices in the SAP system can be maintained for a particular
transaction. The price will be valid for that transaction only and customer will not be
extended sales discount on any other transaction.
• The condition technique in SAP refers to the method by which the system determines
prices from information stored in condition records. In Sales and Distribution, the
various elements used in the condition technique are set up and controlled in
Customizing. During sales order processing, the system uses the condition technique
to determine a variety of important pricing information. For example, the system
automatically determines which gross price the customer should be charged and
which discounts and surcharges are relevant given the conditions that apply.
• There are several ways to get information about pricing and condition records. For
example, during sales order processing, user can carry out a pricing analysis from
the pricing screen. The analysis provides detailed information about which condition
types were used, and which condition types were or were not found. In addition, user
can display information about pricing master data (condition records). For example,
user can search for all condition records regardless of condition type where a
particular material is used as part of the condition record key (searching for condition
records via an index).

7 Business Requirements
User requirement analysis directed in including the following solutions:
• SAP system has one of the most enhanced master data management systems and
organizes data on a single platform
• For SCIL Account Groups have been maintained to provide a consistent number range
for the customers created in the system, enabling unique identification of the customer.
• The company code will be assigned to a credit control area, which will enable automatic
credit control. Therefore credit limits can be maintained centrally for each customer code.
• Material Master Data will be maintained centrally in the database and will work as central
information source for all SAP components. This way not only data redundancy will be
avoided but also this data will be used in most transactions.
• Centrally maintained price and conditions maintenance system
• If the need be special prices in the SAP system can be maintained for a particular
transaction. The price will be valid for that transaction only and customer will not be
extended sales discount on any other transaction.
• The system automatically determines which gross price the customer should be charged
and which discounts and surcharges are relevant given the conditions that apply.
• User can search for all condition records regardless of condition type where a particular
material is used as part of the condition record key (searching for condition records via
an index)
• SAP provides seamless flow of data from one functional silo to another. Currently all
functional silos at SCIL work discretely. No formal channels exist for the exchange of
business information. Business data is exchanged informally through ad hoc and
manually generated documents. This raises serious concerns for data security and
sensitivity. However SAP solution automatically ensures smooth flow of the data through
its seamless integration and ensures that data is created updated and accessed only by
the authorized users.
• The system provides a transaction to list all of the sales documents that have been
blocked for delivery, with information about what has caused the block. Credit
department manually reviews the Customer’s current credit situation, and when the sales
order is approved, the delivery block is removed from the sales order
• System will automatically block the orders exceeding credit limits and will forward the
blocked orders to authorized person for necessary action. Other orders will not need
confirmation and authorization of credit limits as a result sale order processing time will
dynamically decrease.
• Each sale will be recorded with relevant sale employee in the system and extensive
reporting will help find out individual employee sales at any level.
• Now all the functions required for Sales order processing (e.g. stock availability check,
pricing and credit limit check) will be performed automatically by system and no more
multiple department involvement will be required resulting in fast processing
• The dates confirmed by system, using online Available to promise check and smart
delivery scheduling, will be 100% accurate and will help SCIL achieve on time delivery,

accurate production and procurement requirements, quick and reliable decision making
and above all customer satisfaction.
• There is a status field for the sales order header and items that specifies whether the
availability check has covered the commitment for undelivered order quantities. User can
display all sales documents that have the "delayed" status. A delayed sales order is one
where the committed quantities could not be either completely or partially committed, or
where the quantity will be not be confirmed as committed until a later date.
• Sales order report are available in drill-down format allowing the user to access and
analyze the sales information against multiple variables.
• SAP Delivery processing system provides Collective Delivery processing using delivery
due list. The user can process all the deliveries at one button click. The deliveries which
can be combined e.g. deliveries of a single ship to party will be combined by the system
automatically.
• System provides enhanced reporting features for freight and transportation expenses.
• Authorization in SAP defines an area of responsibility of the authorized user, which
automatically instills internal controls for creating, updating and accessing sensitive
business data. This also enhances data security, as only authorized individuals would
have access to the company’s important data.
• System will allow you to create invoice splits, for single order or either collective bills for
several orders, for the same customer.
• System automatically posts revenue to the profit center which is defaulted into the sales
documents from the material master data. System automatically generates a profit center
documents and directly posts the revenue to the profit center.

8 End to End Business Scenarios
8.1 Order to Cash

8.2 Complaints Processing with Credit Memo

8.3 Returns Processing with Credit Memo

8.4 Returnable Processing

A. CHEMICALS DIVISION
1 Business Process of Sales and Distribution
Following is the Mega Business process in Sales and Distribution module of SAP. This
process shows the document and work flow along with the integration of Sales and
distribution with the Financials and Materials Management
Processes in Sales and Distribution
Sales Sales
support Sales activity
Information M
System A
Sales T
Inquiry
E
Quotation R
I
A
USD Contract
L
Free-of-charge
Free-of-charge S
delivery
subsequent Order Returns Sched. agt
delivery
M
Shipping Outbound
A
delivery N
Shipment A
G
E
Billing M
Debit memo Invoice Credit memo E
N
T
Financial accounting
© SAP AG 1999
1.1 Pre-Sales Process
1.1.2 Inquiry Processing

Inquiry and quotation record is maintained in printed forms. There is no record in the system
and these do not become part of sales system at any stage. Sales process starts from Sales
order processing.
1.1.2.1 Process Flow
1.1.2.2 Process Description

• Customer can place an inquiry via different channels:
• Zonal Office receives inquiry
• Dealer receives inquiry and forwards it on behalf of customer
• Head Office directly receives inquiry from customer
• Inquiry can initiate through either email, fax or telephone.

1.1.3 Quotation Processing
order processing.

• Upon receipt of inquiry from customer through any channel, sales and marketing
department at head office record the inquiry details.
• Sales and marketing department does relevant checks with inventory availability,
production planning, and possibility of earliest possible shipping times.
• After adding the price and availability date the quotation is sent through the same
channel back to the customer.

1.2 SAP Enabled Business Process
Customer Inquiry is a primary document in the pre-sales process. An Inquiry presents the
customer requests for a quotation from the supplier (SCIL). The SCIL sales department will
record a particular requisition from the customer, mostly in the cases of inquiries from
Institutions customer. This information is then available to sales department in future period
for preparation of quotation and subsequently sale orders. With the help of maintaining
inquires in system SCIL could be able to analyze which inquires and quotation and prospect
orders are won or lost and not matured, for future sales strategies.
1.2.1 SAP Quotation Processing
A quotation presents the customer with a legally binding offer for delivering a Material or
providing a service within certain fixed conditions from the supplier (SCIL). This information
is then available to sales department so that it can make the subsequent Sales Order with
reference to Quotation. An important aspect of the Quotation will be its usefulness in the
information flow being maintained in the system, e.g. if the quotation submitted to a certain
customer results in a sales order (booking), then in that case the information in the quotation
can be directly copied into the next documents.
1.2.2 Inquiry/Quotation Processing Configuration Data
Following documents types will be used:
Order Type Usage Number Ranges

Inquiry (IN) This document type is used to handle all local, Out 0010000000-
and subscription inquiries; an internal number 0014999999
assignment will be used for its identification.
Quotation This document type is used to process the local, 0020000000 -
(QT) Out and subscription quotation process; an internal 0024999999
number assignment will be used for its
identification.
Pre sales activities will be done by SCIL Sales and Marketing department responsible users.
1.2.3 Pre Sales-VALUE ADDITIONS
• SAP strong pre-sales system comes with a comprehensive inquiry processing

system, which will store, process and report assessments and their status. Not only
these assessments will be source of information for decision-making but also will
help in speeding up the subsequent processes such as fast quotation or order
creation by just copying information from inquiries.
• With SAP pre-sales, quotations can be created and processed in the system. Similar
to Inquiries there is very strong processing and reporting system for quotations.
• Pre-sales processing in SAP enables to capture complete life cycle of the customer
from the time of initial contact to maturing the prospect into a customer.
• Sales quotations are created with specific validity dates and can be utilized in all
Sales processes.
• Pricing is automatically determined on quotations based on pricing condition tables
maintained for materials.

• Text determination tables allow free formats of verbiage to be displayed online and
printed on output documents.
• A customer inquiry and quotation document comprises one or more items that
contain the quantity of a material or service that the customer asked for. The total
quantity of an inquiry item can be subdivided between the schedule lines in different
amounts and relevant delivery dates.
• Line items can be structured in a hierarchy so that you can differentiate between
batches or explode any combinations of materials (bills of material). The valid
conditions for an item are listed in the item conditions and can be derived individually
from the conditions for the whole document.
• Sales queries the user enter and store all the important, sales-related information
used during sales order processing. Queries that are not complex can be entered
quickly in the initial entry screen. The query can be entered from scratch or can be
copied. For example, when the customer decides he wants a firm quote, user can
copy a previously entered inquiry directly into a quotation.
• The inquiries and quotations entered in the system can be displayed and evaluated
in a list. Users can use selection criteria to limit the list which gives them a more
selective display and processing. For analysis purposes, user can list all the
quotations processed during the last six months and examine those that were
rejected and for what reasons.
• Users can maintain a validity date in sales queries by which time the query should
have been answered. The documents can then be monitored and evaluated
according to this validity date, which then allows the user to evaluate the queries on
time. In this way users are able to plan and implement the necessary subsequent
activities according to the deadline.
• Inquiries and quotations can also be referenced from an existing sales document
(inquiry, quotation, sales orders and billing documents), largely reducing user input
time.
• The first information is the most important up-to-date status at header and item level.
From here the user can branch into more detailed status information for the header
and item as well as additional information about the document. User can obtain more
detailed information by expanding the nodes in the hierarchy.
• The system takes all the relevant statuses for a business process and determines the
most important status information at the time for the initial screen dynamically.
Examples of an important status could be the last status change to a document or
the most important status according to document type or an item category that has
not yet been changed.
• The type of status information that is important depends on the document type, item
category and schedule line category.

1.3 Sales Order Processing
1.3.1.1 Dealer Sales: Direct & through zone office
Process Flow

Process Description
• Customer places the order with the appointed dealers.
• Dealer may send the order directly to head office or to the zonal office.
• Head office receives the order from the dealer or zonal office.
• Sales order becomes part of queue of different orders received from other zonal offices.
• If possible, and possibility is defined as the necessary checks with inventory and
production, the sales department validates the order.
• If not validated, the order is deleted from the queue and the zonal office has to again
place the order next day.
• On validation the order moves to the pre dispatch program. These are the orders which
will be processed at the available dates.
• From pre-dispatch program the sales and marketing department confirms some orders.
And sends all the details to finance department.
• Finance department checks for the credit limits of the customer and other payment
issues if any. Here the order can be approved or not by the finance department.
• Sometimes on disapproval of the finance department there is a by pass authority of sales
and marketing department and they can still go ahead with the sales order and process
it. This practice is part of the system but done for certain customers and situations only.
• If not approved the process ends here. Else the finance department sends its approval to
the sales and marketing department.
• Upon receipt of approval sales and marketing department issues the loading slip.

1.3.1.2 Institution Sales: Direct and through zones office
Process Flow

Process Description
• Customer places the order through phone, fax or email at one of the zonal offices or
directly at head office.
• Head office receives the order from the zonal office.
• From pre-dispatch program the sales and marketing department confirms some orders,
and sends all the details to finance department.

1.3.1.3 Exports Order Processing
Process Flow

Process Description
• In exports related orders, customer places the orders with head office sales and
marketing department.
• Upon validation of the order, sales and marketing department gathers info for
transportation and shipping through the export agents.
• The export agent provides cost of shipping and handling, availability of vessel and other
export related documentation.
• On the basis of these costs sales and marketing department prepares a cost sheet.
• This cost sheet is then sent to the finance department for approval. Here there is no
bypass authority.
• On approval from finance department the order is confirmed and sent for processing as
in other case.
1.3.1.4 Sales Through Pipeline:

• SCIL also sell some product through direct pipeline to only one customer ”Aslam
Chemicals” adjacent to the Sitara chemicals.
• SCIL has maintained the pipeline with that customers and flow meter is placed in
Materials Management department under lock and key.
• Representative of customer comes to SCIL with order details.
• Sales and Marketing Department issues him the loading slip.
• Along with loading slip Customer, Security person, and Material dept. representative
goes to valve and record the last reading on flow meter.
• After that open valve and issue the requested material.
• Now they record the reading on flow meter.
• After that security person goes to weigh bridge and record the opening and closing
reading of flow meter.
• Now information reached to the excise department through system where they issue the
dispatch advice and follows the standard procedure.
¾ S AP Sal es Ord e r Proc ess in g Defin ition
A sales order is an electronic document that records customer's request for goods or
services. The sales order contains all information to process the customer's request during
the order processing. The sales component thus automatically proposes data from master
records and control tables that were previously stored. As a result, possible input errors
occurring during sales order processing and entering of redundant data is avoided. Multiple
items can be entered on a single screen. The way in which a material is obtained for a sales
order can depend on the type of material and on the sales transaction.
In SCIL, Customer order entries in SAP System will be more than just capturing customer
demand. Through the integration built into the system, the act of entering the order into the
system will have implications in the areas of production planning, materials management,
Credit management, financial controlling and forecasting. Once the required information is
entered in the Sales order, such as the customer no., material, quantity, required delivery

date and other relevant information, the in- built integration in SAP system will enable the
personnel of the sales & distribution department to commit a delivery date to the customer
which is accurate and can be honoured. At the same time the relevant information is passed
on the concerned departments to make preparations to deliver the goods or services on the
date promised to the customer.
¾ Docu men t Flow

The Document flow option enables the SAP user to track the sales documents into the
system. For example from the Sales Orders screen the user can track the preceding
documents like inquiry and quotation which might have resulted in the creation of the
concerned sales orders. Similarly the user can track the subsequent documents like
Dispatch notes, Sales invoices, Credit / Debit Notes, Invoice Cancellation etc. This provides
the SAP user with the complete picture of that Sales order and its status.

1.3.2.1 In-direct Sales Order Processing (Sales & Distribution):
Process Flow:

Process Description
1. SCIL Sales & Distribution department receives sales order.
2. Sales & Marketing department will create or change sales order in the system. If
sales order does not exist in the system then S&M assistant will create the sales
order, if sales order already exist then S&M assistant or authorized person will
change the sales order if required.
3. Crate Sales order : SAP credit limit check and Credit Block comes under finance
department, Therefore SCIL Agents Credit limit check will be checked through
Finance department.
4. If credit limit exceed then sales order can be saved but delivery cannot be
prepared.
5. If does not exceed the limit then sales order is created in the system.
6. Head office validates the order.
7. Create delivery in the system with reference to the sales order.
8. If sales order already in the system then user can change or amend sales order
subsequently create delivery note.

1.3.2.2 Direct Sale Process (Sales & Distribution)
Process Flow:

Process Description
Finance department.
prepared.

1.3.2.3 Export Sale Process (Sales & Distribution)
Process Flow:

Process Description
1. Customer Inquiry received thorough internet.
2. S&M department get shipment information from the forwarding agent.
3. S&M department prepare cost sheet and send to finance department.
4. Finance department check the cost sheet and if not approved the inform S&M
department.
5. On the approval, approved cost sheet send to S&M department, which is then
send to customer.
6. If Customer agrees to rates: Sales & Marketing department will create or change
sales order in the system. If sales order does not exist in the system then S&M
assistant will create the sales order, if sales order already exist then S&M
assistant or authorized person will change the sales order if required.
Finance department.
prepared.

1.3.2.4 Sales through Pipeline Sale Process
Process Flow:

Process Description
1. SCIL also sell some product through direct pipeline to only one customer ”Aslam
Chemicals” adjacent to the Sitara chemicals.
2. SCIL has maintained the pipeline with that customers and flow meter is placed in
Materials Management department under lock and key.
3. Representative of customer comes to SCIL with order details.
5. Create Sales order : SAP credit limit check and Credit Block comes under finance
Finance department.
prepared.
1.3.2.5 Tender Sales Process
Tendering Business:
SCIL-Chemical also performs tendering business but only with Government Institutions.
It can be both on Quantity basis or time based. Price of product in tender is different from the
regular price of product.
Predefined format is used to carry out tendering business, main items in this format are:
• Extra Margin (future Cost)

• Earnest Money (%age)
• PBG (Performance Bank Guarantee)
In SAP, separate Sales Order Type will be used for tendering business, to have manual
pricing function in the sales order. Through this order type automatically determined price
can be changed in the sales order.

1.3.2.6 Return Sales Order Process
Process Flow
Process Description
Return process with complete or partial quantity is returned is also in practice of SCIL. In
return sales order process users create return order with reference to subsidiary document
which is a sales order number. In this process user will mentioned the return reason that can
be any (SCIL SAP user will provide the return reason list). Return order will release. Then
SCIL user will create return delivery process in this user will receive Goods receipt. Finance
will issue the Debit or Credit note to the Customer.

1.3.2.7 Salient Features of Standard Order
• Sales Order will be booked in SAP, upon the receipt of customer request.
• System will assign an internally generated number to each Sales Order
• A Sales Order however can have more than one items
• A unique code will be generated by SAP to identify every new customer (Customer
Code)
• Customer code could be searched by name, by city or by search term. The search term
would cater to the existing (current) customer codes to make searching easier
• A unique material number will be generated by SAP for every product. This material
number will be used to identify that material in all business processes and transactions. It
can be over written as long as the material is included in the Material Listing of that
customer
• The Material Description will be copied from the Material Master. The same description
copies into the dispatch Note at the time of dispatch
• Material Quantity is the required quantity of material
• Requested delivery date will be in day format. It will be Sales Order Date + 1 Day. Will be
editable
• In case of complete deliveries, the status of the sales order would change from open to
completely delivered, while in case of partial deliveries, the status of the sales order
would change form open to partially delivered
• If there is only one consignee for the customer the system will automatically determine
this code but if there is more than one consignee for a specific customer, the system will
pop up a window for selection
• Delivery terms/Inco terms (e.g. CNF, FOB, EXW) will be proposed as Ex-works from
Customer Master.
• Payment terms will be proposed from customer master but can be over written
• Pricing will be determined automatically
• Division will be the concerned product group.
• Material Sales Tax information will be proposed from the Material Master.
• Default currency will be from the material master as Pak rupees.
• The pricing date will be the current date as default
• Delivering plant information will be determined automatically from the customer/material
master.
• Shipping Plant will be determined automatically through system table.
• Check whether the shipping point has been determined automatically.
• Check credit limits.
• Any changes made in the sales order can be tracked vis-à-vis the original value, the new
value, the editor, time etc
• Priority levels can be set in sales orders to prioritize deliveries as per requirements

• From the sales order screen the SAP user can branch directly to the customer’s account
receivable ledger to view the various details of all postings in his account

Sales Order Number Internally Generated Number of SAP
Sales Order Date Current date will be default.
Requested Delivery Date This will be Sales Order Date . Will be editable
Sold to Party Code Customer code (can also be copied from preceding
docs)
Sold to Party Name Customer Name
Ship to Party Code If there is only one consignee for the customer the
system will automatically determine this code but if
there are more than one consignee for a specific
customer, the system will pop up a window for
selection.
Ship to Party Name Consignee Name
Material Number Proposed automatically through item proposal but can
be over written as long as the material is included in
the Material Listing of that customer
Material Description This will be copied from Material Master but can be
over-written. The same description copies into the
Dispatch Note at the time of Dispatch.
Material Quantity Required quantity of the material
Inco terms Delivery terms will be proposed as Ex-Works from
Customer Master.
Payment Terms Payment terms will be proposed from Customer
Master but can be over-written
Pricing Pricing will be determined automatically, if maintained
Division The concerned product group
Customer Sales Tax Information Proposed from Customer Master
Material Sales Tax Information Proposed from Material Master
Currency Default will be Pak. Rupees from Customer Master
Pricing Date Current date will be default
Delivering Plant Will be determined automatically from Customer /
Material Master
Shipping Plant Will be determined automatically through system table

1.3.2.8 Controls of Sales Order
¾ O r der Ty pes Ava i la bl e
Control Objective
Controls should be in place to ensure that only valid order types are created when sales
orders are entered.
The system should be configured to display only valid order types at the creation of a sales
order. This will limit the display of Order Types to only those that are relevant making it
easier for the user.
¾ C om p l e t io n of M a n d a t o ry F i e l ds
Control Objective
Controls should be in place to ensure that all relevant and required sales order information is
captured before an order is acted on.
Order types should be configured to ensure that all mandatory information is captured before
the order can be released.
Report V.02 (menu path: Logistics - Sales & Distribution - Sales – Information Systems-
Order - Incomplete Orders) can be used to review and complete previously created
incomplete orders. The SAP process owner should review this report on a monthly basis.
¾ Ma n da to r y R ef er en ce
Control Objective
Controls should be in place to ensure that mandatory reference order types are configured.
Order types, such as debit/credit memos and return orders can have a reference mandatory
indicator set so that these order types can only be created with reference to another order
type, i.e. standard order. Reference mandatory indicator should be set accordingly.
¾ C r e a ti o n of S a l e s O r de rs
Control Objective
Controls should be in place to ensure that customer requests result in sales orders.
All orders can be saved, even if the order is missing pertinent information. A message
appears when saving an incomplete order to either save the incomplete document, process
the incomplete document or cancel the order.
Report V.02 (menu path: Logistics - Sales & Distribution - Sales –Information Systems-
¾ M i n im u m S a l es O r der Q u a n t i ty
Control Objective
Controls should be in place to ensure that minimum order quantities are applied, where
applicable.

A minimum order quantity can be set in the material master record. Orders for less than this
quantity will result in warning message being displayed. The warning message can be
configured to an error if this is required. A warning message will allow further processing,
whereas in error will suspend further processing until the error is fixed.
Review company policy on minimum order quantity and make appropriate changes to the
material master records, if required.
¾ S a les O r der S e q ue n t ial N u m berin g
Control Objective
Controls should be in place to ensure that orders are numbered consecutively.
This is an automatic feature of SAP for internally assigned numbers. The configuration must
be reviewed to ensure no external numbers can be assigned.
¾ S a les O r der A p pr o p r ia ten es s a nd A u t ho r iza t io n
Control Objective
Controls should be in place to ensure that orders received are appropriate and authorized.
Orders should only be received for valid products, which the customer is authorized to
receive and the sales representative is authorized to allow.
Both customers and products are allocated to Sales Areas (Sales Organization, Distribution
Channel, Division), so a customer is restricted to receive only products within a Sales Area.
Access control over authorization objects should be implemented at the time of the roles
design and creating user profiles.
¾ Free of Cha r ge Ord er s
Control Objective
Controls should be in place to ensure that “free of charge” orders are reviewed and
approved.
Free of charge items can be controlled by order type within a Sales Order. There is no
standard SAP report available to review free of charge items. However, a selection of all
free of charge items can be made in the Information Systems Reporting Section.
An added precaution on all free of charge orders would include a delivery block. This would
enable an individual to be responsible for checking the details before shipping occurs, thus
allowing a release procedure to be established.
Free of Charge Policy

The company’s policy for free of charge items should be established so that the
representatives are working with guidelines for free of charge items.
Review Free of Charge Orders

Review report using VA05 of all free of charge items to ensure the appropriate control of
these items and that the company policy for free of charge items is being followed. This can
also be accessed through: Logistics - Sales and Distribution - Sales - Information Systems -
Orders – List of Sales Orders. The SAP process owner should review this report every
month.

¾ O r der S c hed u les
Control Objective
Controls should be in place to ensure that order schedules are reviewed.
SAP provides a report for all incoming orders. This can be accessed through the following
menu path: Information Systems - Logistics - Sales and Distribution - Sales Organization –
Sales Organization - Incoming Orders. or through transaction code MC(I).
To ensure timely processing of orders received, the SAP process owner should review this
report on a regular basis.
¾ T imely Av aila bil i ty Of Order Requ es ted
Control Objective
Controls should be in place to ensure that Inventory is checked as orders are entered.
This is a standard feature of SAP. Configuration will determine what is included in the
availability check by appropriately setting “scope of availability check”.
¾ Ba ck O r d er s
Control Objective
Controls should be in place to ensure that orders, which cannot be complete, are placed on
backorders.
Backorders should be monitored together with all other orders not delivered. Backorders
can be checked at the time of the order.
To list backorders by sales area, the menu path is : Logistics - Sales & Distribution - Sales –
Information Systems - Orders - Display Backorders. Report V.15.
Another option is to look at incomplete documents and choose all orders that have not been
delivered. Menu path : Logistics - Sales & Distribution - Sales - Information Systems -
Orders - Incomplete Orders. Report V.02.
These reports should be reviewed by the SAP process owner on a monthly basis.
¾ P r ioritiza tion of Ba ck O r ders
Control Objective
Controls should be in place to ensure that backorders are prioritized.
A report can be run at any time to select back-orders, which can now be met after revised
stock availability, i.e. additional receipts or production.
To process backorders, the menu path is : Logistics - Sales & Distribution - Sales -
Backorders - Backorder Processing - SD Document (V_RA).
SAP does not block orders for products where goods are already on backorder, i.e. when
stock becomes available customers can jump the queue if this report is not run regularly.
There should be user procedures set up to control this aspect of backorders.

¾ A u t h o r i z a t i o n t o O ver r i d e B a c k O r d e r s
Control Objective
Controls should be in place to ensure that that the ability to override backorders is limited to
authorized personnel.
Overrides to the back-order system are controlled by authorizations for the following
processes:
• Control over stock reservations
• Releasing back-orders
Controls should be implemented at the time of the roles design and creating user profiles.
¾ Ac cu ra t e Rec o r d in g of Or d er ed Ma ter i a l s
Control Objective
Controls should be in place to ensure that ordered materials are recorded accurately
A review of the material master should be made to ensure only accurate orders can be
placed in the system. The data should be reviewed periodically, by the SAP process owner,
to ensure only relevant data is maintained.
¾ O r ders f o r Val i d Pr odu c ts
Control Objective
Controls should be in place to ensure that orders can only be received for valid products,
which the customer is authorized to receive and the clerk/officer is authorized to allow.
Customers and products are allocated to sales areas – so that a customer can only receive
certain products.
Access control over authorization objects restricts access to creating sales orders in sales
organizations and order types in a sales order.
profiles.
¾ El ec tr on i c Da ta In terc ha n ge (ED I)
Control Objective
Controls should be in place to ensure that EDI data transmissions are verified
If SCIL uses EDI, data should be verified for validity at each sending/receiving point. Well
defined procedures are required so that there is no miscommunication of information.
¾ A p pr ov ed Pr ic es a n d D i sc o u n t
Control Objective
Controls should be in place to ensure that prices and discounts applied are those stated in
the approved price list and/or the customer master file.

Price lists can be linked to a customer or a fixed price set for each product. Complex rules
for discounts can apply through terms and conditions. Controls in this area will be specific to
each location/business unit.
Access control over authorization object restricts access to different methods of pricing
(condition types) and controls access to pricing in different sales organizations.
profiles
¾ Ma i n te na nce of Pr ic in g Da ta
Control Objective
Controls should be in place to ensure that only authorised personnel maintain pricing data.
Control should be in place to ensure that access control over authorization objects are
limited to authorised personnel. Access needs to be restricted to objects for configuring
different methods of pricing (condition types) and for pricing in different sales organization.
profiles.
¾ Va lid ity of Pric es
Control Objective
Controls should be in place to ensure that valid prices are set.
Pricing procedures and access sequences determine which prices/discounts/etc. are used
and the order in which they are applied.
As part of the order entry procedure, the account representatives should review the pricing
prior to saving the order. Pricing can be reviewed at an individual item level or at the overall
pricing of the entire order. Any problems in pricing should be immediately reported.
The pricing strategy should be reviewed periodically to ensure that it is still in line with ICI’s
policies for pricing.
¾ C on tr ol O ver N on -S ta n da r d Pr ic es a n d Ov errides
Control Objective
Controls should be in place to ensure that non-standard prices and overrides are controlled.
SAP allows each pricing element to be configured to block overrides at the time of the order.
Minimum prices for products can also be set by specifying conditions under SAP. This
overrides any discounts which reduce the price below the set minimum (except cash
discounts).
Prices must be current. This can be controlled by ensuring an error message is displayed if
the price is set to the past (in backdate).
¾ R ea s on a b le n e s s o f Pr ic e s
Control Objective
Controls should be in place to ensure that set prices are reasonable.

SAP has the functionality to set very complex combinations of deals, discounts, and other
conditions.
Margins can be reviewed for each order input, as part of the standard configuration by
configuring the system to display profit margin.
¾ P r ice Ex i s t en c e
Control Objective
Controls should be in place to ensure that all orders have a price.
An order cannot be released without a price. In order to enter a price, a PR00 condition
record must be created to create a price for a sales order, if the price for that product
(material) has not yet been set up.
¾ P r ice C he ck o n G oo ds R e tu r n ed
Control Objective
Controls should be in place to ensure that prices for returned items are verified.
The customer specific price should be reviewed when goods are returned, to determine the
credit that will be given to the customer.
This review should be done by the sales representative when the return order is being
created.
1.3.2.9 Sales Order Processing Configuration Data:

Sales Order processing documents Types:
Order Type Usage Number Range

Indirect Orders - ZIDO Sales Order through 1000000000-1999999999
agent
Direct – ZDIR Sales Order directly to 2000000000-2999999999

SCIL
Export Order - ZEXP All Export Orders 3000000000-3499999999

Pipeline Order - ZPLO For Aslam |Chemicals 4500000000-4999999999
Order
Samples -ZSMP For Samples 5000000000-5299999999

Free of Charge Order - All sales free of charged 5300000000-5599999999
ZFCO
Cash Sales -ZCSH All Cash Orders 5600000000-5999999999

Return Order - ZRTN Sales returns 6000000000-6499999999
Returnable Packing - For Returnable Packing 6500000000-6999999999
ZRPK Return

1.3.2.10 Sales Order-VALUE ADDITIONS
order is approved, the delivery block is removed from the sales order. You go directly
from the list to an individual sales document by placing the cursor on the relevant
document and choosing Edit sales doc.
• SAP Sales processing system supports creation of orders with or without reference to
quotations. An extensive status view is provided to find out references quickly and to
view status of documents at both header and item level.
• As discussed in Credit Master Maintenance, that credit for customers will be defined and
controlled centrally. System will automatically block the orders exceeding credit limits
and will forward the blocked orders to authorized person for necessary action. Other
orders will not need confirmation and authorization of credit limits as a result sale order
processing time will dynamically decrease.
multiple department involvement will be required resulting in fast processing.
• In the sales order, a committed quantity and date are issued alongside the confirmed
quantity calculated by the availability check, which enables see whether committed
quantities and delivery dates have been complied with. These new functions are
particularly useful if the users are expecting production bottlenecks and where obligatory
agreements on dates have to be met. Users can specify the delivery time at header level
and this influence the delivery times for all items in a sales order but you can also enter
different delivery times for single items at item level. When you create a sales order with
reference to a contract or quotation the system copies the delivery time into the sales
order item. If you do not enter a delivery, nothing changes in sales processing.
• In the schedule line screen for the sales order items there are fields for the committed
quantities and dates. In a normal sales order, the commitment date results from the first
availability check. If a second availability check results in different data, users can
compare the two to see if the availability situation for a sales order item has improved or
deteriorated. The commitment date is calculated using the delivery time in sales orders
that may refer to a quotation with a delivery time. The committed quantity is calculated
from the agreed delivery time or from the confirmed quantity. If there is any change the

material, quantity and delivery date or delivery time in the sales order, the system
recalculates the committed quantity.
• Standard complaint handling process in system will allow creating either credit memo or
free of charge deliveries with reference to relevant orders or invoices. All relevant
information will be copied from reference document and the reference will be maintained
by system for reporting purposes.
• System will print the invoices with payment status of customer making it visible that
which invoices have to be paid by customer and which is only for documentation
purpose.
• System treats transportation breakages as sales to transporters. It maintains the
relationship between order, credit memo or free of charge delivery to customer,
transporter order for breakage charges thus providing one view status of any order at
any point of time
Duplicate sales orders are a problem, particularly in business-to-business mail orders. Users
may, for example, receive an order over the phone followed by a confirmation fax. These
may be inadvertently treated as two separate orders. If this is not corrected, it can lead to
unnecessary handling, shipping costs, and returns. SAP can search for all sales documents
that have the same customer, currency, and total value of the order. From this list user can
select pairs of documents and have R/3 drill down into the individual line items. If at least
one of the line items differs between the two orders, the system will automatically let both
orders proceed. If, on the other hand, the line items are all identical, user can then examine
the individual sales and choose which one to proceed with. In this way user can catch
unintentional duplication at an early stage and thereby reduce the frequency of merchandise
returns. User can run the duplicate order report, from the system (SDD1), the system will list
all the sales documents matching the criteria selected. Next to each customer, there will be
either a green or yellow button. A green button indicates that there are no duplicate sales
documents. A yellow button indicates that one or more sales documents for this customer
have the same currency and total order value.

1.4 Credit Note & Debit Notes
Process Flow
Process Description
• Customer Lodges Complaint by Filling Complaint Form.
• Sales And Marketing Department Forwards The Complaint After Acceptance To Finance
For Approval.
• Credit Memo/Debit Memo Created and Sent To Customer.

This document aims to provide the audience with a complete, concise and a comprehensive
overview of the credit notes and debit notes in SAP. The process of Credit / Debit memo
notes is discussed under the following heads:
Process Flow

¾ C r e di t M e mo R e qu es t & Cr e d it No t es
Credit Note can be issued for many reasons. For e.g. Discounts offered to a customer
(besides Sales Tax Invoice) are issued through credit notes. Credit note can be issued with
reference to sales invoice, return delivery or even without reference as the case may be.
¾ D e b it M e m o R e q ue st & D e bi t N o tes
Debit note request will be created with reference to invoice or independently. In the first
case, all information maintained in invoice would be replicated into debit note request. When
this requested would be verified by authorize concerns, debit note will be created against
Debit Note Request
1.4.2.1 Salient Features of Credit Notes Process

• System will assign an internally generated number to each Credit Note Request and
Credit Note
• When credit note request or Credit note will be issued the status of sales order will also
list that for this sales order credit note request and credit note exist
• For every customer a unique code will be used to identify the customer.
• In case of Credit memo request created with reference to pricing will be copied from
invoice.
• Credit memo request and subsequent credit notes can also be created without reference
to any invoice. In this case the Credit Note will be created without sales tax
• In case of return delivery the credit note request will be created with reference to the
return delivery. The pricing will be copied from the returns document (which in turn was
copied from Invoice) and the quantity will be copied from the returns delivery document.
• In case where Credit note has to be created against sale for which ninety days has been
passed, the credit note will be created net of Sales Tax
Following data will be maintained in system to create credit memo request and credit note.
Information Required Source

Credit Note Number / Request Number Internally Generated Number of SAP
Credit Note Date / Request Date Current date will be default. Can be
changed.
Sold to Party Code Will be copied from the reference
document. Can not be changed
Sold to Party Name Will be copied from the Master data.
Cannot be changed.
Material Number Will be copied from the reference
document
Material Description Will be copied from the Master data
Material Quantity Will be copied from the reference
document
Pricing Will be copied from the reference
document

Division Will be copied from the reference
document
Customer Sales Tax Information Will be copied from the reference
document
Material Sales Tax Information Will be copied from the reference
document
Currency Will be copied from the reference
document
Reason of Credit Note Reason for which the credit note is issued
1.4.2.2 Salient features of Debit Note Process.

• System will assign an internally generated number to each Debit Note Request and
Debit Note regardless of division or geographical location
• A reason will be assigned in system for issuance of debit note
• The information can be replicated in Debit note request from invoice and from Debit note
request to Debit not
• When debit note request and debit note will be issued, the status of sales order will also
list that for this sales order debit note request and debit note exists
1.4.2.3 Credit/Debit Memo Configuration Data:
Credit/Debit Memo types
Document Type Usage Number Ranges

Credit Memo Reg This order type is to send credit 30000000-34999999
memo req for credit note
Debit Memo Reg This order type is to send debit 40000000-45999999

memo req for credit note
Credit Note (G2) This invoice type is used to

maintain claim from customer 35000000-39999999
for damage and shortage
cases.
Debit Note (L2) This invoice type is used to 45000000-49999999

charged the customer for
specific reason such as pricing
mistakes etc.

Credit or Debit Memo documents can be created using one of the following:
• Create a Debit Memo and Credit Memo request.
• Individual invoice document creation using SAP standard transaction code VF01, or
using SAP standard menu path: Logistics > Sales and Distribution > Billing > Billing
Document > Create
• Collective processing using SAP standard transaction VF04, or using SAP standard
menu path: Logistics > Sales and Distribution > Billing > Billing Document > Maintain
Billing Due List (Select Document Related Billing on selection screen).

1.5 Delivery Process
1.5.1.1 Head Office Shipping Process
Process Flow

Process Description
• All deliveries except caustic soda for Karachi are made from Head office sales and
Marketing.
• On issuance of loading slip starts the delivery process starts.
• Sales and marketing department provide the loading slip to security department, which in
turn contacts to transporter to bring in the vehicle.
• At in-gate the vehicle is checked by security department for necessary compliance
regarding, cleanliness, sealing of lower valves, drivers and vehicle documents etc.
• On clearance the vehicle is moved to weigh bridge one for tare weight of the vehicle.
• Tare weight is also recorded on the loading slip by hand along with the weight card
issued at this time.
• When all the necessary information is recorded at the Weigh Bridge-I, now the vehicle
moves to the specific storage location (silos for filling or warehouse for loading). Loading
group which SCIL is currently using:
Crane
Fork Lift
Manual
Flow meters
Liquid:
Filling of the tanker is recorded by the flow meters attached, which is afterward converted
into the tons. ISO standardized tanks are also used for the delivery of HCL.
Solids:
SCIL uses two types of packing material for the delivery of solid material:
Bags
Drums
Gas:
Cylinders are used for the delivery of gases. Following are the necessary information which
has to be maintained for the delivery of gases in cylinders:
Expiry Date of the cylinder

N.O.C from the explosive department
Cylinder Number
All the above mentioned information is printed on the cylinders. Delivery of theses cylinders
are not possible unless and until all the information is recorded in system.
LAB Test
After getting all the required material, sample is taken from the truck and sent to the lab for
quality assurance. Now with the Loading Slip truck drivers also have the lab test report
document. Vehicle is now ready for the dispatch and reaches the Weigh Bridge-II.
Weigh Bridge
Weigh Bridge-II records the gross weight of the truck.
Net weight = Gross weight – Tare Weight (Liquid Only)
Net weight = Gross weight – (Tare weight + Packaging)
This net weight is used for billing of the product, this is also known as charge weight.

Upper lid Sealed
On confirmation by the weigh bridge-II for the recorded weight in comparison with the weight
history of truck and material quantity marketing department sealed the upper lid and truck
drivers take the document to the excise department.
Excise Department
Driver reaches the excise department, where all the necessary information is recorded,
which includes:
Concentration of the product

Quantity
Bilty No
Transporters information,
Vehicle No.
Weight details
Now the Excise Department issues the dispatch advice:
Excise Copy
Marketing Dept. copy
Finance Dept. copy
Customer/Transporter copy (Used for good receipt acknowledgement, and recorded in
marketing department when truck comes for the next load)
Detailed Specifications for Cylinders used in sales of Gases. These specifications are
available within the system and are part of the sales document.

1.5.1.2 Karachi Office Shipping Process
Process Flow
Process Description
• Head Office Delivery Process is maintained even though no goods delivery from SCIL
FSD.
• Karachi office maintains a minimum stock at a third party ware house.
• The Sales order is placed and process similar to direct orders via zonal office but the
delivery is made through the warehouse.
• In this case the customer will pay for the storage charges.

Dispatch/Delivery note will be generated with reference to the sales order. The system
provides the functionality of generating a delivery due list, this list is date specific. The
highest level of integration allows the person creating delivery to collect/pick all the data from
sales order according to the delivery schedule maintained in the sales order created by the
sales admin officer.
¾ S hi pp i n g P r oc ess S A P D ef in i t io n :
Shipping is defined as “the act or business of transporting Material”. It is a significant

element of the logistics chain in which certain customer’s Material distribution planning play
major roles. In shipping processing, all delivery procedure decisions can be made at the
start of the shipping process by, taking into account general business agreements with SCIL
customer, recording special material requests, defining shipping conditions in the master
data or in sales document.
The result is an efficient and largely automatic shipping process in which manual changes
are only necessary under certain circumstances. The result is an effective and mainly
practised shipping process. Shipping is a subsequent activity of the Sales Document
component.
¾ D e l iv ery D o c u m e n t C r ea t i o n
Delivery document can be created by following:
Individual delivery document creation using SAP standard transaction code VL01N, or using
SAP standard menu path:
Logistics > Sales and Distribution > Shipping and Transportation > Outbound Delivery >
Create > Single Document > With Reference to Sales Document
Collective processing using SAP standard transaction VL10C or using SAP standard menu
path:
Create > Collective Processing > Sales Document and Schedule Lines
¾ P os ti n g Go o d s Is su e
After finalizing the delivery note, the warehouse in charge posts this delivery note in the
system; this process is called Outbound Post Goods Issue. As soon as it is posted in the
system, the inventory is reduced automatically and it is reflected on financial ledger.
When the goods leave the plant, the shipping business activity is finished. The outbound
delivery forms the basis of goods issue posting. The data required for goods issue posting is
copied from the outbound delivery into the goods issue document, which cannot be changed
manually. In this way, the users can be sure that the goods issue document is an accurate
reflection of the outbound delivery.
When post goods issue is carried out for an outbound delivery, the following functions are
carried out on the basis of the goods issue document:

• Plant’s stock of the Material is reduced by the delivery quantity
• Value changes are posted to the balance sheet account in inventory accounting
• Requirements are reduced by the delivery quantity
• Goods issue posting is automatically recorded in the document flow
Post Goods Issue can be done via SAP standard Outbound Delivery Monitor or transaction
code VL02N or VL06G.
After goods issue is posted for an outbound delivery, the scope for changing the delivery
document becomes very limited. This prevents there being any discrepancies between the
goods issue document and the outbound delivery.

1.5.2.1 Head office Shipping Process Description:
Process Flow
Process Description:
1. Open Sales Orders in system received after creation of delivery in sales order
process.

2. Delivery Due List is composed of multiple deliveries, with reference to open
orders.
3. Sales & Marketing Assistant Create Delivery for picking and packing process at
warehouse.
4. Vehicle i.e the truck or tank lorry is assigned to certain delivery in the system.
5. Security/Admin contacts the transporter for the truck to be moved inside the SCIL
premises.
6. Necessary Checks by Security department person as to the fitness of the vehicle

for loading of chemicals and other products.
7. After clearance from the vehicle checks , it is then forwarded to move to WB-1 for
tare Weight process.
8. Tare weight is recorded in the system
9. If stock available according to Delivery
Truck is loaded/ tanker is filled

Transfer of requirement
10. QC Lab takes the sample from the vehicle and issues the lab report.
11. QC Lab Clear the test and a copy of the lab test is attached with other delivery
documents.
12. After fill up the vehicle goes to WB-2 for the Gross Weight, Gross weight – Tare
weight = Net Weight.
13. Weight card is Printed from system and issued to the driver.
14. Gross weight is recorded in the system & also on the Weight card.
15. Driver takes all the documents to Excise Department.
16. Excise officer updates delivery order by changing net weight, entering Lab report
details and Builty No. (For fare purpose) in the system.
17. Excise Dept. prints & issues 4-copies of Dispatch Advice.
18. Post Goods Issue
19. Truck is loaded vehicle reaches the security section again for the final inspection
and Seal the upper led.
20. Vehicle departs from Out Gate

1.5.2.2 SCIL Sales & Distribution Karachi Shipping Process Description:
Process Flow
process.

orders.
warehouse.
4. If stock available according to Delivery
Truck is loaded/ tanker is filled

5. Transfer of requirements to production department.
6. Post Goods Issue.
7. Replenishment level of goods stored fulfilled at Karachi Warehouse.
8. Dispatch Note sent to the Customer.

1.5.2.3 SCIL Sales & Distribution Through Shipping Process Description:
Process Flow

Process Description
1. S&M assistant create delivery in the system, print out of delivery will be used as
loading slip.

2. Along with loading slip Customer, Security person, and Material dept.
representative goes to valve and record the last reading on flow meter.
3. After that open valve and issue the requested material.
4. Now they record the reading on flow meter.
5. After that security person goes to weigh bridge and record the opening and closing
reading of flow meter.
6. Delivery Order quantity changed according to the reading.
7. Post goods issue
8. Now information reached to the excise department through system where they
issue the dispatch advice and follows the standard procedure.
1.5.2.4 Salient Features of Dispatch Note
The salient features of the Dispatch Processing are discussed as below:
• System will assign an internally generated number to each Dispatch note

regardless of division.
• Separate deliveries will be generated for each Sales Order. A sales order may
result in more than one dispatch note.
• Ship to Party (Consignee) will be copied from Sales order and can’t be changed
on dispatch note.
• Material no., description, quantity and sales unit will be copied from Sales Order
whereas various other details about the material will be copied from master data
of material.
• System allows you to have a single Sold-to-party while the goods can be
dispatched to multiple locations by changing Ship-to-party.
¾ Data on D is pa t c h N o te
The following information is maintained in the Dispatch Note

Dispatch Note Number Internally Generated Number of SAP
Dispatch Note Date Current date will be default
Sold to Party Code Customer code
Sold to Party Name Customer Name from Customer master
data
Ship to Party Code Ship to party will be copied from Sales
Order
Ship to Party Name Consignee Name from Ship tom master

data
Material Number Will be copied from Sales Order
Material Description Will be copied from Sales Order
Material Quantity Confirmed quantity will be copied from
Sales Order.
Division Will be copied from Sales Order
Incoterms (Delivery Terms) Will be copied from Sales Order
1.5.2.5 Controls of Dispatch Process
¾ C r e a ti o n of D is pa tc h N ot e s
Control Objective
Dispatch notes should only be created with reference to the sales orders.
Controls should be in place to ensure that dispatch notes can only be created with reference
to the sales orders. The dispatch staff should not be allowed to create deliveries on their
own initiatives. All relevant information should be copied from the sales order.
¾ O nl y C o m p l e t e S a l e s O r d e r s P r o c e s s e d f o r D el i v e r y
Control Objective
Controls should be in place to ensure that only complete sales orders are processed for
delivery.
incomplete orders. Controls should be in place to ensure that only complete orders are
processed for delivery.
¾ D e l iv ery R ec or ds
Control Objective
Controls should be in place to ensure that accurate records of deliveries are maintained.
The picked quantity cannot be higher than the ordered quantity within SAP. Through
discussions we understand that SCIL will not be using the picking facility in SAP and post
goods issue will be based on the dispatch note. Controls should be in place to ensure that
appropriate and accurate records of deliveries are maintained.
¾ S toc k Al l oc a ti o n
Control Objective
Controls should be in place to ensure that stock assignments/allocations are recorded as
soon as possible upon acceptance of an order.

This is an automatic feature of SAP performed at goods issue. Before goods issue the stock
will be allocated to the confirmed customer order.
¾ P r o mp t D el iv er ies
Control Objective
Controls should be in place to ensure that timely deliveries are made.
All confirmed orders should be delivered in time. The delivery due list (VL10A) processes all
orders ready for delivery and lists all orders due for delivery (for each shipping point). The
SAP process owner should review this report regularly to ensure old orders are followed up.
¾ P a r t i a l D el i v er i e s
Control Objective
Controls should be in place to ensure that customers who do not want partial deliveries do
not receive them.
SAP allows partial deliveries. The delivery note will contain the stock recorded as picked
(which will be less than the order). The shortage will be recorded on the delivery due list
(VL10A). A flag setting in the customer master determines if the customer allows partial
deliveries. If all customers require full deliveries, this should be set as a mandatory field in
the customer master.
¾ C on s e c u ti v e N u m b e r i n g
Control Objective
Controls should be in place to ensure that all dispatch documents have a consecutive
number.
This is an automatic feature in SAP for internally assigned numbers. The configuration must
be appropriate to ensure no external numbers can be assigned.
¾ O ve r r i d e s t o D i s pa tc h N o t e
Control Objective
Controls should be in place to ensure that overrides to the dispatch note are restricted.
Information on the dispatch note is copied from the sales order and material master. It is
recommended that the overrides to the information on the dispatch note be restricted to
authorized users. We understand that manual overrides will be allowed, which may result in
reduction in quantities and/or changes to text information. Manual controls should be in
place to authorize these overrides.
Consultant’s Comments: The system allows certain changes to the dispatch note to facilitate
the operation/user. This includes information from any preceding document or data and can
only be added at the dispatch stage, and only the dispatch department is knowledgeable
about such information. Reducing the dispatch quantity is a logical activity for example,
incase of system/physical availability of stock but the condition/stacking of goods is such that

it cannot be dispatched, so the quantity on dispatch note can be reduced. However, quantity
cannot be increased if over tolerance is not allowed. Hence, the system does not allow any
editing which involves any inherent risk in the underlined process.
¾ D e l iv ery M e t h o ds
Control Objective
Controls should be in place to ensure that appropriate delivery methods are used to deliver
orders.
The material master record contains details of the material, and any special handling
requirements. When a pack is opened the system automatically selects appropriate items.
The shipping point determination selects the cheapest/most appropriate shipping point (and
hence delivery method) based on this information.
The accuracy of the descriptive information (weight, dimension, hazard codes) held on the
material master must be maintained. If this information is inaccurate, then the control will not
work and there will be a higher risk that inappropriate delivery methods will be used.
¾ Ba ck O r d er s
Control Objective
Controls should be in place to ensure that back-orders are monitored and controlled.
Customer requirements that cannot be immediately satisfied are placed on back order.
Back-orders should be regularly monitored together with all other orders not delivered -
using List of incomplete orders (V.02) menu path: Logistics - Sales and Distribution - Sales
Information Systems - Orders - Incomplete Orders (V.02).
The SAP process owner should review this report regularly to ensure timely delivery of all
outstanding orders.
¾ P r oc ess i n g S ta tu s
Control Objective
Controls should be in place to ensure that the system updates the processing status of all
orders regularly.
SAP provides the functionality of monitoring the overall processing status of any order at any
point of time. The status of the order should remain ‘open’ as long as delivery document is
not posted. Its status should change from ‘open’ to ‘being processed’ at the time the delivery
is posted. When the sales tax invoice is created the status should than be changed to
‘completed’. Controls should be in place to ensure that the status of all orders is updated in a
timely fashion.
¾ R ev e r s a l of D is pa t ch N o te
Control Objective
Reversal of a dispatch note should not be allowed if a subsequent document is created
against that dispatch note.

This is an automatic feature of SAP. Where a dispatch note is to be deleted/cancelled, all
references to any subsequent documents, should first be deleted to allow cancellation of a
particular dispatch note.
¾ Q ua l i ty C o n tr o l Re v ie w of R etu r ne d G o o ds
Control Objective
Controls should be in place to ensure that returned goods are subject to inspection by quality
control department.
Controls should be in place to ensure the returned goods are subject to quality controls
review before the dispatch department will book the goods return. Based on the review result
of the quality control department, the goods will be appropriately classified in the accounting
records.
¾ C r e d i t N o tes C re a t ed O n ly Wi t h R e f e r e n c e t o R e t u r ns
Control Objective
Where goods are returned the credit note should only be created with reference to the
returned delivery.
Controls should be in place to ensure credit notes are created only with reference to the
returned deliveries. The system should be configured to allow users to raise/process credit
notes only with appropriate reference to the returned deliveries.
¾ I d e n t if ic a t i on of R e tu r n s
Control Objective
Controls should be in place to ensure that all returns are clearly identified.
The returned goods should be held separate in the warehouse pending inspection. In SAP,
the return delivery should be appropriately referenced to the corresponding dispatch note to
allow for appropriate identification of the return.
Additional controls include the following:
If the Bill of Lading (BOL) does not match the receiving report, the receiving report should
take precedence. The returns should be placed in the inspection area with a different
movement type.
Control Objective
credit that will be given to the customer. This review should be done by the sales
representative when the return order is being created.
¾ M o n i t or in g of R etu rn L e v el s

Control Objective
Controls should be in place to ensure that return levels are monitored.
The inventory and sales information systems can be configured to produce statistics (and
graphs) on returns. Following standard reports for returns are available within the SAP.
Returns Report for Given Sales Organization

Sales Org. Returns, Selection (MC+Y), menu path: Information Systems - Logistics - Sales
and Distribution - Sales Organization - Sales Organization - Returns (MC+Y), allows reports
of returns to be created for a given sales organization.
Returns Report for Given Customer

Customer Returns, Selection (MC+A), menu path: Information Systems - Logistics - Sales
and Distribution - Customer - Returns (MC+A), allows reports of returns to be created for a
given customer.
Returns Report for Material

Material Returns, Selection (MC+M), menu path: Information Systems - Logistics - Sales and
Distribution - Material - Returns (MC+M), allows reports of returns to be created for a given
material.
The SAP process owner should review these report on a quarterly basis.
¾ A p propria t eness of Cred itin g Re turns
Control Objective
Controls should be in place to ensure that returns are credited appropriately.
The SAP process owner should review the following reports on a regular basis to ensure
returns are credited appropriately.
• Credit Memo Report by Sales Organization
• Sales Org. Credit Memos, Selection (MC+6), menu path: Information Systems - Logistics
- Sales and Distribution - Sales Information System - Sales Organization – Sales Org.
Credit Memos Selection (MC+6).
The credit memo report (MC+6) should be compared to the returns (MC+Y). Manual
procedures are required and follow-up is essential to control quality customer service in this
area. Other reports available within SAP include:
• Credit Memo Report by Customer
• Customer Credit Memos-Selection (MC+I), menu path: Information Systems - Logistics -
Sales and Distribution - Customer - Credit Memos (MC+I).
• Credit Memo Report by Material
• Material Credit Memos, Selection (MC+U), menu path: Information Systems - Logistics -
Sales & Distribution - Material - Credit Memos (MC+U).
¾ B l oc k in g of C r edi t N ote s
Control Objective

Controls should be in place to ensure that the ability to create and/or unblock credit notes is
limited to authorized personnel.
In configuration it is possible to set up credit notes so that they are automatically blocked for
billing. A different person must then remove the block.
Definition of appropriate activity types and access control over authorization objects should
be implemented at the time of the roles design and creating user profiles.
¾ R el e a s e o f C r e d it N o t es
Control Objective
Controls should be in place to ensure that only approved credit notes are released.
Credit notes should only be released with proper approval. It is possible for many users with
access to accounting documents to be able to post credit notes. Controls can be improved
by allocating the credit note document types to a special authorization group and only
allowing authorized staff to be able to post to this authorization group.
1.5.3 Delivery processing Configuration Data
Delivery Processing related document types:
Delivery Type Usage Number Ranges

Outbound Delivery This delivery type is used to 8000000000- 8499999999
(LF) classify all standard delivery.
Inbound Delivery Delivery Type to cater return 7000000000-7499999999

(LR) Document.
Inbound Delivery Delivery Type to cater 7599999999-7999999999
Returnable (LR) returnable Packing
1.5.3.1 Shipping-VALUE ADDITIONS
due list. When the items become ready to be delivered to customer according to the
system suggested ATP date, a work list is displayed to logistics user with various signal
lights showing the time wise priority to process the deliveries. The user can process all
the deliveries at one button click. The deliveries which can be combined e.g. deliveries of
a single ship to party will be combined by the system automatically.
• SAP system provides strong document and audit trails. System keeps a track record of
the creator of the document, date of creation of the document, date of update of the
document, user responsible for update and details of preceding and subsequent
documents. It also keeps a log of any warning messages ignored by the user. This
enables the management to exercise control on the users and hold them accountable for
their mistakes.

• System provides standard reports, which are updated online, and real time basis. SAP
will display report of all pending orders. System provides ease of changing orders if one is
authorized to do so. System also provides deadline monitoring for reference documents
due for shipment (sales orders and purchase orders, for instance).

1.6 Billing Process
1.6.1.1 Invoice Process: Local Sales
Process Flow

Process Description
• Billing process starts at the time when Excise Department issues dispatch advice “D.A”.
• On receiving finance copy of D.A, finance department executes the billing process.
• Billing department gets necessary information from Dispatch Advice and details entered
in system by sales and marketing department, weigh bridge, etc and prepares invoice for
customer.
• Terms of payments SCIL-Chemical uses are:
Advance
Cash
Credit / Debit Memo
• The factors involved in billing are:
Rate (Basic Price) of Product
Discounts are valid for any customer
Tax classification for type of sales
Excise duty on product
Sales Tax
Dealer commission for product. Payment on monthly basis.
Freight
¾ B ill i n g Pr oc ess D ef in it i on SA P
Invoice is a legal document used to bill a customer for goods delivery. Deliveries and
services, which are carried out on the basis of sales documents and are, invoiced to the
customer billing represents the final processing stage for a business transaction in Sales and
Distribution. Information on billing is available at every stage of document processing and
delivery processing.
Invoice documents can be created using one of the following:
Individual invoice document creation using SAP standard transaction code VF01, or using
Logistics > Sales and Distribution > Billing > Billing Document > Create
Collective processing using SAP standard transaction VF04, or using SAP standard menu
path:
Logistics > Sales and Distribution > Billing > Billing Document > Maintain Billing Due List

1.6.2.1 Billing Process Sales and Distribution Department:
Process Flow:
1. Billing Document will be created with reference to delivery document in S&M

department.
2. Sales & Marketing department will have option to create billing document either
individually or collectively.
3. Excise Office will create billing document in the system.
4. Once the invoice is created in the system, sales tax invoice can be printed
5. Finance department will do necessary check in the invoice.

6. Finance department will print commercial invoice.
7. Invoice send to customer next day through courier.
8. This invoice is in favor of the customer, it will reflect the gross price, it will not
show the agent commission amount, whereas commercial invoice is for agent and
will show all rebates and commission details.
1.6.2.2 Salient Feature of Standard Billing
The salient features of the Sales Tax Invoice Processing are discussed as below:
• The dispatch note and the Sales Tax Invoice will be generated before the
physical delivery of the goods, and will be sent with the goods.
• The warehouse staff will have to physically check the stocks before posting the
dispatch note.
• The sales tax invoice will always generate an invoice for the quantity on the
dispatch note.
• System will assign an internally generated number to each Sales Tax Invoice
• Various deliveries can be generated for each Sales Order. One Sales Tax Invoice
will be created for each Dispatch note.
• Bill-to-Party will be copied from Sales order and can’t be changed on SALES TAX
INVOICE.
• Sales tax will appear on Sales Tax Invoice as per the applicable Government
regulations. This can be updated in the master data when required.
• The business has decided to implement de-centralized invoicing, with invoicing at
Lahore, Karachi and Faisalabad offices.
• It is imperative that signatory authorities be defined at the regional offices for the
signing of the sales tax invoices.
• As per the controls proposed, the system will be configured that the sales tax will
be either deducted at the time of delivery or the receipt of advance payment
whichever is earlier.

1.6.2.3 Controls of Billing
Control Objective
Partial deliveries are correctly invoiced and the balance of the delivery is completed and
invoiced.
For partial deliveries - a report can be run showing all partial orders (menu path: Logistics -
Sales & Distribution - Billing - Environment - List Deliveries using transaction VL05).
This can be run for open deliveries by ship-to-party or material. This report should be
reviewed monthly by the SAP process owner to ensure deliveries are completed and
invoicing is up to date.
¾ P os ti n g o f G o ods I s su e
Control Objective
Controls should be in place to ensure that the ability to post goods issue is limited to
authorised personnel.
Suggested procedures
The authorisation object, authorising posting for goods issue should be restricted to those
individuals having authority to post goods issue. The object activities should also be
reviewed to ensure access for deleting deliveries is controlled.
¾ Inv o ic in g all D e l iveries
Control Objective
Controls should be in place to ensure that all deliveries to customers are invoiced.
The billing due list (menu path: Logistics - Sales & Distribution - Billing - Billing Document -
Billing Due List , transaction VF04) details all deliveries which have not been billed.
This report should be run regularly and outstanding documents followed up, to ensure
invoicing is complete for all orders delivered
¾ Ac cu racy of I n v o ic es
Control Objective
Controls should be in place to ensure that invoices sent to customers are accurate.
We understand that invoices have been configured to restrict any changes in line items.
However, certain condition records in the pricing procedure are allowed for manual overwrite
during sales order creation. To control any errors in input/changes to the pricing data, it is
recommended that minimum and maximum limits are set for the condition records. This
control is for sales order creation.
In order to review the accuracy of invoices, invoice details are automatically obtained from
the sales order and dispatch details. To review the billing documents: Logistics - Sales &
Distribution - Billing - Billing Document - List Billing Document (VF05).

¾ S eque n tia l Nu mberin g of Bill ing D ocu men ts
Control Objective
Controls should be in place to ensure that billing documents are assigned consecutive
numbers.
¾ P os ti n g Bl oc ks
Control Objective
Controls should be in place for posting of unusual or particularly sensitive documents.
SAP allows posting blocks to be configured by document type, for documents requiring
additional control, i.e. returns, credit notes, debit notes, etc. It is recommended that SCIL
consider the use of this facility.
Where the posting block indicator is on, this will block the automatic transfer of billing
documents to the accounting records. The corresponding accounting document is only
created after the block is cancelled.
Where billing documents have not been updated in the FI module, it should be manually
updated to the accounting records (menu path : Logistics - Sales/Distribution - Billing -
Change - Release to Accounting).
Consultant’s comments: Blocks are not cancelled but released. Billing documents are not
manually updated but are released for posting in FI.
¾ Au th o r iza t io n f o r Bil lin g Tra n sac ti o ns
Control Objective
Controls should be in place to ensure that SAP billing transactions are executed only by
Authorisations objects, allowing access for maintaining billing documents by billing type and
sales organisation should be restricted to those individuals having authority for billing. This
should be done at the time of roles design.
¾ C u t - of f
Control Objective
Controls should be in place to ensure that sales and cost of sales are recorded in the correct
accounting period.
Sales and cost of sales should be included in the correct accounting period. At period end,
the sale and the cost of sale should be matched.
The cost of sales accounting is updated at the goods issue (delivery) and sales accounting is
updated at billing. Therefore, there will only be a difference if billing has not been run after
goods issue. This can be discovered by running the billing due list - transaction VF04 (menu
path: Logistics - sales/distribution - billing - billing document - billing due list). The total value
on this report will give the necessary adjustment for cut-off.

The SAP process owner should review this report at each cut-off date to ensure recording of
accounting entries in the correct accounting period.
Consultant’s Comments: Cost of goods sold is recorded through Goods Issue/Despatch.
1.6.3 Billing Process Configuration Data
Sales and distribution documents used to bill a customer for a delivery of goods or for
services rendered. Billing/invoice type controls the processing of invoices, credit memos,
debit memos and cancellation documents. Following Billing/Invoice document types will be
used:
Billing/Invoice Types Usage Number Ranges

Standard Invoice (F2) For Standard Invoice 9000000000-9499999999
Return invoice ( RE) For return Invoice 50000000-54999999
Return invoice For return of returnable 55000000 - 59999999
Returnable ( ZR) packing deposit
1.6.3.1 Billing-VALUE ADDITIONS

business data. This also enhances data security, as only authorized individuals
would have access to the company’s important data.
• Along with this extensive secure authorization, system provides facility of printing
invoices with payment history and status.
• Process of billing due list can be done either as a background task or foreground.
• System will allow you to create invoice splits, for single order or either collective bills
for several orders, for the same customer.
• Periodic billing plans for space rental orders are also available in the SAP system.
• The seamless integration of the SAP system minimizes redundant activities. Data
posted in the SD or MM becomes source of data for financial document, hence need
for ad hoc reports, forms and documents are eliminated.
• System will maintain aging of open accounts receivable items which helps finding out
invoice dates
• As complaints are processed in system, system will allow generating credit memos
and handle returns with reference to these complaints. System will provide ease of
creation credit / debit memos with reference to already created invoices. System also
supports creation of Pro-forma invoices.
• The system combines documents with the same customer number, proposal billing
type and sales organization, and attempts to include them all in the same billing
document. If the preconditions are met, then a single invoice is created for the
deliveries and/or orders. The invoice list lets you create, at specified time intervals or

on specific dates, a list of billing documents (invoices, credit and debit memos) to
send to a particular payer. The billing documents in the invoice list can be single or
collective documents (collective invoices combine items from more than one
delivery). The standard version of the SAP R/3 System includes two types of invoice
lists, for credit memos and for billing documents and debit memos.
• System automatically posts revenue to the profit center which is defaulted into the
sales documents from the material master data. System automatically generates a
profit center documents and directly posts the revenue to the profit center.

2 Reporting Requirements
Sales Reports are flexible tool for collecting, and evaluating data (available in system) from
the operative application. In addition SCIL can use this data as the basis for forecasting and
planning sales activities. SCIL can therefore use the information for controlling, monitoring
and planning purposes.
Apart from available data from the Sales and Distribution application few certain external
generation.
2.1 Standard and Non-Standard Segregation of Reports
Standard Reports that are the closest matches to reports submitted by Business Key Users.
SAP Standard Report Transaction Code of

Title of Report
Title Standard Report
Date wise Due Overdue Status Customer Payment RFDOPR20/RFDSLDOO/
History FDOPO00
Chlorine Cylinder Status ABAP/QUERY
Daily dispatch validation ABAP / QUERY
Consignee Loading List Customer List RFDKVZ00
Expired Cylinder List MM-REPORT
Customer List number wise Customer List RFDKVZ00/S_ALR_87012
179
Transporter List Customer List RFDKVZ00
Dispatch Advice Validation Report ABAP/QUERY
City Wise consignee list Customer List RFDKVZ00
HCL/Exports List SIS: SalesOrg. LIS REPORT/ MC(1
Inc.Orders Selection
Customer wise sale report for year SIS: MC(A
Customer,Inc.Orders
Selection
Customer ledger movement FICO
Product wise sales statement ABAP / QUERY
Dispatch Advice Not return by ABAP /QUERY
Transporters
Un-Acknowledged Dispatch Advice ABAP /QUERY
Liquid Chlorine Cylinders’ Daily Monthly sales report MC(A
Dispatch Report Party Wise
Chlorine cylinder status MM-REPORT

3 Scripts Requirements
SAP script is the standard SAP form design tool to develop customized form printing format,
which could be specified in system for business activities such as invoices, purchase
Documents, delivery notes etc. These scripts could be used for internal process or required
for external submissions.
Following scripts / printing forms were identified by SCIL for their Chemicals division:
S.No. Description
1 Finish Product Loading Slip
2 Receipt WB2
3 Dispatch Advise
4 Invoice

B. Agri Division
Sales Sales
Information M
System A
Sales
Inquiry T
E
Quotation R
I
A
USD Contract
L
Free-of-charge
Free-of-charge S
delivery
delivery
M
Shipping Outbound
A
delivery N
Shipment A
G
E
Billing M
N
T
© SAP AG 1999


order processing.


order processing.



identification.

Sales processes.

time.

1.3.1.1 Dealer Sales
Process Flow
Process Description
• Customer places the order with the appointed dealers.
• Dealer may send the order directly to head office or to the zonal office.
• Head office receives the order from the dealer or zonal office.

• From pre-dispatch program the sales and marketing department confirms some orders.
And sends all the details to finance department.
1.3.1.2 Direct Sales
Process Flow

Process Description
• Customer places the order through phone, fax or email at one of the zonal offices or
directly at Faisalabad Office Agri Division.
• Faisalabad Office Agri Division receives the order from the zonal office.
• From pre-dispatch program the sales and marketing department confirms some orders,
and sends all the details to finance department.

1.3.1.3 Retail Sales
Process Flow

Process Description
• Customer places the order in person directly at Faisalabad Office Agri Division.
• If possible, and possibility is defined as the necessary checks with inventory, the sales
department validates the order.
• From pre-dispatch program the sales and marketing department confirms order, and
sends all the details to finance department.
1.3.1.4 SAP Enabled Business Process
¾ Docu men t Flow


Process Flow:

Process Description
Finance department.
4. If credit limit exceeds then sales order can be saved but delivery cannot be
prepared.
5. If credit limit does not exceed the allowed limit then sales order is created in the
system.
6. Head office validates the order to be processed further.

Process Flow:

Process Description
Finance department.
prepared.
5. If credit limit does not exceed the allowed limit then sales order is created in the
system.

1.3.1.7 Retail Sale Process
Process Flow:

Process Description
1. Customer Inquiry received thorough internet.
2. S&M department get shipment information from the forwarding agent.
3. S&M department prepare cost sheet and send to finance department.
4. Finance department check the cost sheet and if not approved they inform S&M
department.
5. On the approval, approved cost sheet send to S&M department, which is then
send to customer.
6. If Customer agrees to rates: Sales & Marketing department will create or change
sales order in the system. If sales order does not exist in the system then S&M
assistant will create the sales order, if sales order already exist then S&M
assistant or authorized person will change the sales order if required.
Finance department.
prepared.

Process Flow
Process Description
Return process with complete or partial quantity is also in practice of SCIL. In return sales
order process users create return order with reference to subsidiary document which is a
sales order number. In this process user will mentioned the return reason that can be any
(SCIL SAP user will provide the return reason list). Return order will release. Then SCIL user
will create return delivery process in this user will receive Goods receipt. Finance will issue
the Debit or Credit note to the Customer.

Code)
customer
editable
Customer Master.
master.


docs)
selection.
Customer Master.
Material Master

Control Objective
orders are entered.
Control Objective
Control Objective
Control Objective
Control Objective
applicable.

Control Objective
Control Objective
Control Objective
approved.


month.

Control Objective
Control Objective
¾ Ba ck O r d er s
Control Objective
backorders.
Control Objective

Control Objective
processes:
Control Objective
Control Objective
certain products.
profiles.
Control Objective
Control Objective

profiles
Control Objective
profiles.
Control Objective
Control Objective
discounts).
Control Objective

conditions.
Control Objective
Control Objective
created.

Indirect Orders - ZIDO Sales Order through 1000000000-1999999999
agent
Direct – ZDIR Sales Order directly to 2000000000-2999999999

SCIL
Retail Order -ZRTL For Agri retail sales 3500000000-3999999999

from the shop or
factory outlet
Samples -ZSMP For Samples 5000000000-5299999999
Free of Charge Order - All sales free of 5300000000-5599999999

ZFCO charged
Cash Sales -ZCSH All Cash Orders 5600000000-5999999999
Return Order - ZRTN Sales returns 6000000000-6499999999

Returnable Packing - For Returnable 6500000000-6999999999
ZRPK Packing Return


purpose.
any point of time

Process Flow
Process Description
For Approval.

Process Flow

Debit Note Request

Credit Note
invoice.

changed.
Cannot be changed.
document
document
document

document
document
document
document
1.4.2.2 Salient features of Debit Note process.

Billing Type Usage Number Ranges

Credit Memo This order type is to send credit memo 30000000-34999999
Reg req for credit note
Debit Memo This order type is to send debit memo 40000000-45999999

Reg req for credit note
Credit Note This invoice type is used to maintain 35000000-39999999

(G2) claim from customer for damage and
shortage cases.
Debit Note This invoice type is used to charged 45000000-49999999

(L2) the customer for specific reason such
as pricing mistakes etc.
Document > Create

Transportation types used in shipping process

• SCIL
• Customer Own
• Contractor customer
• Contractor SCIL
• Dealer
Drums are returnable and at the time of sale the customer pays for the security deposit of
the drums.
Process Flow

Process Description
• In case of stock unavailability at Faisalabad Godown for Agri Products the delivery is
made from SCIL Head Office.
• Agri division have its vehicles for up to five tonnes for pre determined locations and
customers.
• Any customer who orders for products more than 5 tonnes will receive it from an out side
contractor vehicle.
• SCIL own vehicle info is maintained with plant maintenance department.
• On issuance of loading slip starts the delivery process.
• Agri Sales and marketing department provide the loading slip to security department,
which in turn contacts to transporter to bring in the vehicle.
• At in-gate the vehicle is checked by security department for necessary compliance.
Regarding, cleanliness, drivers and vehicle documents etc.
• On clearance the vehicle is moved to weigh bridge one for tare weight of the vehicle.
• Tare weight is also recorded on the loading slip by hand along with the weight card
issued at this time.
• When all the necessary information is recorded at the Weigh Bridge-I, now the vehicle
moves to the specific storage location. Loading group which SCIL Agri is currently using:
Crane
Fork Lift
Manual
• Liquid:
Products are stored in Cans of 1,2,3 litres and 25, 35 litres.
• Solids:
SCIL uses bags for the delivery of solid material:

LAB Test:
Sample is taken from the batch at the time of production and sent to the lab for quality
assurance.
Batch wise lab tests are documented and accompany to the customer along with all sales
documents. Since Agri products are sold in pre packaged cans and sacks, therefore lab
tests are done before packaging is done.
This lab certificate becomes part of delivery documents. Now with the Loading Slip truck
drivers also have the lab test report document. Vehicle is now ready for the dispatch and
reached the Weigh Bridge-II.
Weigh Bridge No 2.
Weigh Bridge-II records the gross weight of the truck.
Net weight = Gross weight - Tare weight - Packaging
This net weight is used for billing of the product, this is also known as charge weight.
Excise Department:
Driver reaches the excise department, where all the necessary information is recorded,
which includes:
• Lab Report
• Quantity
• Bilty No
• Transporter information,
• Vehicle No.
• Weight details
• Now the Excise Department issues the dispatch advice:
• Excise Copy
• Marketing Dept. copy
• Finance Dept. copy
• Customer/Transporter copy (Used for good receipt acknowledgement, and recorded in
marketing department when truck comes for the next load)


component.
path:


1.5.2.1 Shipping Process:
Process Flow

process.

orders.
warehouse.
4. Vehicle i.e. the truck or tank lorry is assigned to certain delivery in the system.
5. Security/Admin contacts the transporter for the truck to be moved inside the SCIL
premises.
6. Necessary Checks by Security department person as to the fitness of the vehicle

for loading of chemicals and other products.
7. After clearance from the vehicle checks, it is then forwarded to move to WB-1 for
tare Weight process.
8. Tare weight recorded in the system.
9. If stock available according to Delivery.
Truck is loaded
10. After fill up the vehicle goes to WB-2 for the Gross Weight, Gross weight – Tare
weight = Net Weight.
11. Weight card is Printed from system and issued to the driver.
12. Gross weight recorded in the system & Weight card.
13. Driver takes all the documents to Excise Department.
14. Excise officer updates delivery order by changing net weight, entering Lab report
details and Builty No. (For fare purpose) in the system.
15. Excise Dept. prints & issues 4-copies of Dispatch Advice.
16. Post Goods Issue.
17. Truck is loaded vehicle reaches the security section again for the final inspection
and Seals the upper lid.
18. Vehicle departs from Out Gate.


on dispatch note.
of material.

data
Order
data
Sales Order.

Control Objective
Control Objective
delivery.
Control Objective
Control Objective
Control Objective

Control Objective
not receive them.
Control Objective
number.
Control Objective
Control Objective
orders.

¾ Ba ck O r d er s
Control Objective
outstanding orders.
Control Objective
orders regularly.
timely fashion.
Control Objective
Control Objective
control department.

records.
Control Objective
returned delivery.
Control Objective
movement type.
Control Objective
Control Objective


given customer.

material.
Control Objective

Control Objective

Control Objective

(LF) classify all standard
delivery.
Inbound Delivery Delivery Type to cater 7000000000-7499999999
(LR) return Document.
Inbound Delivery Delivery Type to cater
Returnable (ZR) returnable Packing 7599999999-7999999999
their mistakes.

1.6 Billing Process
Process Flow

Process Description
• Billing process starts at the time when Excise Department issues dispatch advice “D.A”.
• On receiving finance copy of D.A, finance department executes the billing process.
• Billing department gets necessary information from Dispatch Advice and details entered
in system by sales and marketing department, weigh bridge, etc and prepares invoice for
customer.
• Terms of payments SCIL-Agri uses are:
Advance
Cash
Credit / Debit Memo
• The factors involved in billing are:
Rate (Basic Price) of Product
Discounts are valid for any customer
Tax classification for type of sales
Excise duty on product
Sales Tax
Dealer commission for product. Payment on monthly basis.
Freight
• Billing is done in batch processing and the dispatch advices generated on same day are
processed together.
• Credit sales are made only for a very few select customers approved by the
management.

• Individual invoice document creation using SAP standard transaction code VF01,
or using SAP standard menu path:
• Logistics > Sales and Distribution > Billing > Billing Document > Create
• Collective processing using SAP standard transaction VF04, or using SAP
standard menu path:
• Logistics > Sales and Distribution > Billing > Billing Document > Maintain Billing
Due List

Process Flow:

department.

dispatch note.
dispatch note.
INVOICE.

Control Objective
invoiced.
Control Objective
Control Objective
Control Objective

Control Objective
numbers.
Control Objective
Control Objective
¾ C u t - of f
Control Objective
accounting period

used:

Standard Invoice (F2) For Standard Invoice 9000000000-499999999
Return invoice ( RE) For return Invoice 50000000-54999999
Return invoice For return of returnable 55000000 - 59999999
Returnable ( ZR) packing deposit

invoice dates


generation.

Title of Report
Vehicle wise Dispatch report ABAP / Query
Invoice validation report ABAP / Query
Customer sales discount comparison Customer Analysis LIS / FD10 /MCTA
with previous two periods
Product wise sales return summary MC+M
Product Sales for the Year
District wise selected product MC+Q
summary
Outstanding Orders re[port Delivery Due List VL04
Sales Tax Report Product wise ABAP/Query
District Wise monthly Sales Analysis MC+E
Customer wise monthly Sales MC+E
Analysis
Customer & Product wise Sales & ABAP /Query
receipt Summary
District wise sales of CAB ABAP
Products Rate Change History VK12
Product Wise Sales Summary
Summary of Sales Invoices Under Invoice List ABAP
Section 26(5) of Sales Tax Act, 1990
Product Wise Sale Summary Without MCTC
Sale Return Effect
Vehicle wise Dispatch report ABAP / Query

Following scripts / printing forms were identified by SCIL for their Agri divisions:
S.No. Description
2 Receipt WB2
3 Dispatch Advise
4 Invoice

C. Textile Division
Sales Sales
Information M
System A
Sales
Inquiry T
E
Quotation R
I
A
USD Contract
L
Free-of-charge
Free-of-charge S
delivery
delivery
M
Shipping Outbound
A
delivery N
Shipment A
G
E
Billing M
N
T
© SAP AG 1999


order processing.


order processing.



identification.

Sales processes.

time.

1.3.1.1 Agent/Direct Sales
Process Flow

Process Description
• Customer Order through agent.
• Sales and Marketing department checks customer previous record, if the customer has a
negative history (credit history, breaching the contract, etc.) then the order is not
processes and process ends here.
• If history is positive negotiation on rates is done between customer and marketing
department with the customer.
• After Negotiations Sales and Marketing Department prepare Sales Contact on the
system. Sales Contact contains, Total Quantity to buy, Rates, Delivery Priority, Credit
Limit, Brokers Commission or Brokery rates and freight conditions.
• Contract is then transferred to Finance department through system, Finance
Department check the details of the contract, if any change needed finance department
sends it back to marketing department for necessary changes. or get approval from CEO
and confirms the order.
• If no changes required then Marketing Department prepare Delivery order and sends
one copy to Customer for good issue and one copy to Finance department for billing
purpose
• “Broker” places the order.
• Orders receive at sales office from broker on phone/fax/email or purchase order.
Necessary validation of order and broker is done.
• Negotiations regarding rate, quantity and commission percentage or brokery (per bag
fixed amount) is finalized before preparation of contract.
• Sometimes broker or customer prepares the contract and forward it to the SCIL-Yarn
sales office.
• After preparation of contract sales department forward it to finance department for
necessary checks.
• On approval of contract, sales department issues the delivery order document and
delivery process starts.
• In case of rejection from the finance department, sales department made the necessary
amendments in contract or get the approval from CEO and confirms the order.
1.3.1.2 Indirect Sales from Karachi Office:

• SCIL also maintains its Yarn Office in Karachi.
• Sales takes place through appointed brokers only.
• Karachi office receives orders and after following the same process sends data to
Faisalabad office to prepare contract.
• Faisalabad office prepares contract and informs Khi. Office, who then issues Delivery
Order to the customer, broker.
• Contract with the customer is sent to Finance department for approval. Credit limit Check
is the responsibility of Marketing Department

1.3.1.3 Institution Sales
Process Flow

Process Description
• Customer Orders Direct at Textile division Sales and Marketing Office Faisalabad.
• Sales and Marketing department checks customer previous record, if the customer has a
negative history (credit history, breaching the contract, etc.)then the order is not
processes and process ends here.
• If history is positive negotiation on rates is done between customer and marketing
department with the customer.
• After Negotiations Sales and Marketing Department prepare Sales Contact on the
system. Sales Contact contains, Total Quantity to buy, Rates, Delivery Priority, Credit
Limit, Brokers Commission or Brokery rates and freight conditions.
• Contract is then transferred to Finance department through system, Finance
Department check the details of the contract, if any change needed finance department
sends it back to marketing department for necessary changes. or get approval from CEO
and confirms the order.
• If no changes required then Marketing Department prepare Delivery order and sends
one copy to Customer for good issue and one copy to Finance department for billing
purpose

1.3.1.4 Retail Sales
Process Flow
Process Description
• Customer Order Directly, these orders are of small quantity like 6 or 7 bags.
• Sales and Marketing assistant receive cash.
• Sales and Marketing assistant issue delivery order.

1.3.1.5 SAP Enabled Business Process
¾ Docu men t Flow


Process Flow:

Process Description
1. Sales & Marketing department receives sales order.
2. S&M department check the credibility of customer.
3. If not cleared the inform to customer.
4. Negotiation with the customer on rates.
Finance department.
prepared.

Process Flow:

Process Description
1. Sales & Marketing department receives sales order.
2. S&M department check the credibility of customer.
3. If not cleared the inform to customer.
4. Negotiation with the customer on rates.
Finance department.
prepared.

1.3.1.8 Retail Sale Process
Process Flow:

Process Description
1. Customer Order directly, these order are of small quantity like 6 or 7 bags .
2. Sales and Marketing department receive Cash
3. S&M assistant. Create/change Sales Order in System
4. Sales Order Existence check in system
5. Create Sales Order in system
6. Change / Amend Sales Order in system

Process Flow
Process Description
Return process with complete or partial quantity is returned is also in practice of SCIL. In
return sales order process users create return order with reference to subsidiary document
which is a sales order number. In this process user will mentioned the return reason that can
be any (SCIL SAP user will provide the return reason list). Return order will release. Then
SCIL user will create return delivery process in this user will receive Goods receipt. Finance
will issue the Debit or Credit note to the Customer.

Code)
customer
editable
Customer Master.
master.


docs)
selection.
Customer Master.
Material Master

Control Objective
orders are entered.
Control Objective
Control Objective
Control Objective
Control Objective
applicable.

Control Objective
Control Objective
Control Objective
approved.


month.

Control Objective
Control Objective
¾ Ba ck O r d er s
Control Objective
backorders.
Control Objective

Control Objective
processes:
Control Objective
Control Objective
certain products.
profiles.
Control Objective
Control Objective

profiles
Control Objective
profiles.
Control Objective
Control Objective
discounts).
Control Objective

conditions.
Control Objective
Control Objective
created.

Indirect Orders – ZINS Sales Order through 1000000000-1999999999
agent
Direct ZDRS Sales Order directly to 2000000000-2999999999

SCIL
Export Order –ZEXS All Export Orders 3000000000-3499999999
Retail Order- ZRTS For Agri retail sales

from the shop or 3500000000-3999999999
factory outlet
Samples –ZSPS For Samples 5000000000-5499999999
Free of Charge Order – All sales free of
ZFCS charged 5500000000-5999999999
Cash Sales –ZCSS All Cash Orders 6000000000-6499999999
Return Order –ZRES Sales returns 6500000000-6999999999


purpose.
any point of time

Process Flow
Process Description
For Approval.

Process Flow

Debit Note Request

Credit Note
invoice.

changed.


Cannot be changed.

document

document
document
document
document
document
document
1.4.2.2 Salient features of Debit Note process.

Billing Type Usage Number Ranges

Credit Memo This order type is to send 60000000-64999999
Reg credit memo req for
credit note
Debit Memo This order type is to send 70000000-75999999
Reg debit memo req for credit
note
Credit Note This invoice type is used 65000000-69999999
(G2) to maintain claim from
customer for damage
and shortage cases.
Debit Note This invoice type is used 75000000-79999999
(L2) to charged the customer
for specific reason such
as pricing mistakes etc.

Document > Create

Material Stocks are transferred from mills warehouse to Faisalabad Godown by creating a
stock transfer order. Three godowns are used for the storage of Textile division products
namely;
• Karachi
• Faisalabad
• Mill
Per bag half kg is additional weight in order to compensate for loss of moisture in storage.
Partial delivery is allowed in most cases.
1.5.1.1 Shipping Process
Process Flow

Process Description
• Customer receives the delivery order from sales and marketing department.
• Customer goes to designated warehouse with the DO.
• Warehouse department issue good as per DO details. Delivery can be from Yarn market
warehouse or mill warehouse.
• Warehouse department issues gate pass to customer.
• Customer gives the gate pass to security and clears the goods from warehouse.

1.5.1.2 Karachi Office Shipping Process
Process Flow
Process Description
• Head Office Delivery Process is maintained even though no goods delivery from SCIL
FSD.
• Karachi office maintains a minimum stock at a third party ware house.
• The Sales order is placed and process similar to direct orders via zonal office but the
delivery is made through the warehouse.


component.
path:


1.5.2.1 Shipping Process
Process Flow

process.

orders.
warehouse.
4. Customer takes the DO from Marketing Department and goes to designated

warehouse for delivery.
5. If stock available according to Delivery.
Truck is loaded
Otherwise Transfer of requirement to production is sent.
6. If stock is available, Post Goods Issue.
7. Warehouse dept issues gate pass to customer.
8. Customer gives the gate pass to the security to clear the goods from warehouse

1.5.2.2 Shipping Process Karachi
Process Flow:
1. Open sales orders in system.
2. Delivery due list with ref to open order.
3. Sales & Marketing assistant create delivery.
4. If stock not available according to delivery transfer of requirements.
5. If stock available, Post Goods Issue.
6. Replenishment level of goods stored fulfilled at Karachi Warehouse.
7. Dispatch note customer.


on dispatch note.
of material.

data
Order
data
Sales Order.

Control Objective
Control Objective
delivery.
Control Objective
Control Objective
Control Objective

Control Objective
not receive them.
Control Objective
number.
Control Objective
Control Objective

orders.
¾ Ba ck O r d er s
Control Objective
outstanding orders.
Control Objective
orders regularly.
timely fashion.
Control Objective
Control Objective

control department.
records.
Control Objective
returned delivery.
Control Objective
movement type.
Control Objective
Control Objective


given customer.

material.
Control Objective
Control Objective

Control Objective

(ZD) classify all standard delivery.
Inbound Delivery Delivery Type to cater return 7500000000-7999999999

(ZR) Document.
their mistakes.

1.6 Billing Process
Process Flow

Process Description
• Sales and Marketing department sends one copy of DO to finance department through
system.
• Finance Department performs necessary check.
• Invoice data is copied from DO. Invoice created and printed from system.
• Invoice sends to customer next day through postal service.

Individual invoice document creation using SAP standard transaction code VF01, or using
Logistics > Sales and Distribution > Billing > Billing Document > Create
Collective processing using SAP standard transaction VF04, or using SAP standard menu
path:
Logistics > Sales and Distribution > Billing > Billing Document > Maintain Billing Due List

Process Flow:

department.

dispatch note.
dispatch note.
INVOICE.
• The business has decided to implement de-centralized invoicing, with invoicing at
Lahore, Karachi and Faisalabad offices.

Control Objective
invoiced.
Control Objective
Control Objective
Control Objective

Control Objective
numbers.
Control Objective
Control Objective
¾ C u t - of f
Control Objective
accounting period

used:

Standard Invoice (ZB) For Standard Invoice 9000000000- 9499999999
Return invoice ( RE) For return Invoice 50000000- 54999999

invoice dates


generation.


Title of Report
Daily Yarn Production, Yarn Rate, ABAP
Stocks and Booking status
Count wise Contract Outstanding ABAP

Count / Month wise Yarn sales Rate ABAP
Analysis
Party Wise Yarn Sales Trend SIS: MC(A
Customer,Inc.Orders -
Selection
Count / Party Wise Yarn Sale MC(E LIS Report
Yarn Count Wise Sales Report ABAP
Summary of Sales Invoices ABAP
Date Wise Delivery Report Delivery Monitor VL060
Date Wise Delivery Order Report Delivery Monitor VL060
Count Wise Party List RFDKVZ00
Stock of Yarn at Mill/Godown/Karachi MB52 & MB55
Yarn sales Yearly Comparison SIS: Customer, MC(E LIS
Inv.Sales - Selection
Party Count Wise SIS: Customer, MC(E LIS
Inv.Sales - Selection
Daily Yarn Production, Yarn Rate, ABAP
Stocks and Booking status
Count wise Contract Outstanding ABAP

Count / Month wise Yarn sales Rate ABAP
Analysis
Party Wise Yarn Sales Trend SIS: MC(A
Customer,Inc.Orders -
Selection

Following scripts / printing forms were identified by SCIL for their Textile division:
S.No. Description
2 Agency Invoice
3 Invoice

Scil SD BBP Final

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Scil SD BBP Final

Caricato da

Copyright:

Formati disponibili

Sitara Chemical Industries

Business Blue Print

SAP ECC 6.0 IMPLEMENTATION

Sales & Distribution Module

Date: Rabi-us-Sani 07, 1429

Business Blue Print Document Page 2 of 248

Business Blue Print Document Page 3 of 248

Business Blue Print Document Page 4 of 248

Business Blue Print Document Page 5 of 248

Business Blue Print Document Page 6 of 248

Business Blue Print Document Page 7 of 248

Mr. Muhammad Azam Butt

Mr. Asad Rathore

Mr. Chaudhry Naeem Raza

Mr. Inayat. U. Koreshi

Mr. Muhammad Moin

Business Blue Print Document Page 8 of 248

SCIL Acceptance & Approvals

Shahzaib Siddiqi Ather Mujhaid

Business Blue Print Document Page 9 of 248

4.1 Overview of Sales and Distribution

Business Blue Print Document Page 10 of 248

o Maintenance of Master Data

o Billing Request processing

Business Blue Print Document Page 11 of 248

The following describes the symbols used in the process map:

Start Process Decision

Activity step Document

Display Transfer out of

Out of system Start

Out of system Out of system

Business Blue Print Document Page 12 of 248

Sales and Distribution Organisational Structure – SAP Perspective

Figure 1: Overview of Sales and Distribution External Structure

5.1 Sales Organization

An organizational unit subdivides an enterprise according to the requirements of sales. A

Sales Organization Description

Business Blue Print Document Page 13 of 248

Distribution Channel Description

5.3 Product Division

5.4 Sales Area

Sales Organization Distribution Channel Division

Business Blue Print Document Page 14 of 248

Figure 2: Overview of SCIL Sales and Distribution External Structure

Business Blue Print Document Page 15 of 248

S.NO Sales Districts Description

Business Blue Print Document Page 18 of 248

S.NO Sales Offices Description

Business Blue Print Document Page 19 of 248

6.1.1 Business Specifications

6.1.1.1 Chemical Division

Export Sales process in Textile:

6.1.1.2 Agri Division

Business Blue Print Document Page 20 of 248

6.1.1.3 Textile Division

Three types of customers for Textile division

Export Sales process in Textile:

Business Blue Print Document Page 21 of 248

¾ Company C ode Data

¾ Sales Area Data

The system standard customer master record represented by sold-to-party, ship-to-party,

Business Blue Print Document Page 22 of 248

1. Sales and marketing department collect customer related information