Vous êtes sur la page 1sur 101

Project: ARCHIT

ARCH Pharmalabs Limited

Business Blueprint
Sales & Distribution
BBP_SD_V1.0

SIGNATORY

NAME

Prepared /
Signed by

Srinivas Poduru

TITLE

DATE
/

Reviewed/
Approved by

Approved by

Approved by

Authorized
by

SIGNATURE

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

2 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Document Control
Document ID

ZTL/2010/PRJ-252/SD

Compliance Status

Mandatory

Security Classification

Company Restricted

Issue Date

Document Status

Prepared by

Quality Review

Authorized by

Distribution

Document History

2010 Zensar Technologies

Draft,

Revised,

Final

Srinivas Poduru

Sreenivasan A

V1.0

Page 2 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

3 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

DOCUMENT CONTROL:
S NO

Revision

Creation Date

Last Modified

Remarks

1
2
3
4
5

2010 Zensar Technologies

Page 3 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

4 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Table of Contents
1.

INTRODUCTION.............................................................................................................. 7

2.

S.D MODULE KEY COMPONENTS................................................................................7

2.1

Sales Order Processing.................................................................................................8

2.2

Delivery Processing.......................................................................................................8

2.3

Billing.............................................................................................................................. 8

2.4

Excise Invoice................................................................................................................9

2.5

Pricing and Conditions..................................................................................................9

2.6

Automatic Credit Check...............................................................................................10

2.7
3.

Availability Check.........................................................................................................10
ENTERPRISE STRUCTURE.........................................................................................11

3.1

Controlling Area...........................................................................................................11

3.2

Company code............................................................................................................. 12

3.3

Sales Organization.......................................................................................................12

3.4

Distribution Channel....................................................................................................13

3.5

Division......................................................................................................................... 13

3.6

Sales Office.................................................................................................................. 14

3.7

Sales Group.................................................................................................................. 14

3.8

Sales Area..................................................................................................................... 15

3.9

Plant.............................................................................................................................. 18

3.10

Logical Plants (Bonded Warehouse).......................................................................19

2010 Zensar Technologies

Page 4 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

5 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

3.11
4

Storage Location.......................................................................................................... 19
MASTER DATA:............................................................................................................. 22

4.1

BBP_SD_BP01: Customer Master..............................................................................22

4.2

BBP_SD_BP02: Material Master (Sales views)..........................................................28

4.3
BBP_SD_BP03: Pricing condition records...............................................................31
5 BUSINESS PROCESSES....................................................................................................34
5.1 BBP_SD_BP01: STANDARD ORDER................................................................................34
5.2 BBP_SD_BP02: SAMPLE ORDER....................................................................................36
5.3 BBP_SD_BP03: STOCK TRANSFER ORDER...................................................................37
5.4 BBP_SD_BP04: SUPPLEMENTARY INVOICE..................................................................39
5.5 BBP_SD_BP05: JOB WORK ORDER - WITH ONLY SERVICE CHARGES......................40
5.6 BBP_SD_BP06: JOB WORK ORDER WITH MATERIAL COST AND SERVICE CHARGES
41
5.7 BBP_SD_BP07: THIRD PARTY SALES (TRADING PRODUCTS/ SALE IN TRANSIT)....41
5.8 BBP_SD_BP08: PROJECT BASED ORDER.....................................................................42
5.9 BBP_SD_BP09: CUSTOMER RETURN ORDER...............................................................43
5.10 BBP_SD_BP10: CREDIT AND DEBIT MEMO REQUEST PROCESSING.......................45
5.11 BBP_SD_BP11: OUTBOUND DELIVERY PROCESSING................................................48
5.12 BBP_SD_BP012: RETURNS DELIVERY PROCESSING...............................................51
5.13

BBP_SD_BP13: INVOICE PROCESSING.....................................................................51

5.14 BBP_SD_BP14: AVAILABLE TO PROMISE..................................................................54


5.15 BBP_SD_BP15: CREDIT MANAGEMENT.....................................................................56
5.16

BBP_SD_BP16: BATCH DETERMINATION..................................................................59

5.17

BBP_SD_BP17: EXCISE INVOICE /ARE DOCUMENTS PROCESSING......................60

2010 Zensar Technologies

Page 5 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

6 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

5.18

BBP_SD_BP18: EXPORT ORDER................................................................................63

REPORTS & SCRIPTS REQUIREMENTS....................................................................82

6.1

REPORT REQUIREMENTS..........................................................................................82

6.2
7.

SCRIPS REQUIREMENTS: SC_SD_01........................................................................90


FUNCTIONAL REQUIREMENTS..................................................................................91

8.

INTEGRATION POINTS................................................................................................95

9.

AUTHORIZATION CONSIDERATION...........................................................................97

10.

MASTER DATA CONSIDERATIONS.............................................................................98

11.

VALIDATION/ENHANCEMENTS CONSIDERATIONS.................................................98

2010 Zensar Technologies

Page 6 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

7 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

1.

SUPERSEDES:

Introduction
The purpose of this document is to compile the requirements gathered during business
process design workshops and it documents the business process requirements of the
company. With this, you can better understand how the company intends to run its business
within the SAP System.
This document describes the design of the proposed solution and implications for the
business process. This document is to communicate the new business solution and
expected changes to the business process. The information needs to include:

Enterprise organizational structures


The proposed integrated business processes
Associated function definitions
Business requirements in term of reports/script and functionality
Authorizations

With the information conveyed by this document, the business should be able to approve
the proposed solution. The Business Blue print becomes the master deliverable/document,
which serves as a basis for the entire project.
Brief Introduction of SD Process in ARCH
As per market demand, Sales target is prepared which is usually called as Sales forecast.
Sales forecast is also based upon last years sales performance. Sales target is prepared
based on Customer and Material. Entire market area is divided into 4 major Sales Offices
(zones). Each zone is further divided into Sales groups.
Arch sales of their own manufactured goods along with Raw Material and Trading material.
Excise duty is applicable at factory gate for manufactured and traded goods and sales tax as
applicable.

2.

S.D Module key components

2010 Zensar Technologies

Page 7 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

8 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

SD module provides flexible, automated support in processing all sales activities in the
company. The Sales system allows executing the various sales business transactions based
on sales documents defined in the system. The most important basic functions in SD are as
follows.

2.1

Sales Order Processing

A Standard Order is used to process customer request for material .The process of creating a
standard sales order begins with the customers request for materials to be sent to them. This
request could be via phone, mail or fax.
Once a customers purchase order is received, the order is processed through Sale Order form
(SO). The SO is raised for the required quantity after considering the factory stocks .The
dispatches shall be planned and invoices are generated based on the customer tax liability. The
deliveries shall be made directly.
During sales order processing, the system carries out various functions, such as monitoring of
sales transactions, checking for material availability, Delivery scheduling, calculating pricing and
taxes, checking credit limits and creating output documents for a sale order confirmation.

2.2

Delivery Processing

As per Dispatch Advice issued from marketing, finished goods are dispatched to the respective
customer.
In its role as central object of the goods issue process, the delivery supports all shipping
activities such as picking, packing, transportation and goods issue. During the delivery process,
shipping-planning information is recorded, status of shipping activities is monitored and the data
accumulated during shipping is documented.

2.3

Billing

On receipt of the Dispatch Advice, the marketing & logistics department generates Delivery
Challan cum invoice.
Billing represents the final processing stage for a business transaction in Sales and Distribution.
This component includes the following functions: Creation of: Invoices based on deliveries,
Issue of credit and debit memos, Cancel billing transactions, Manual Transfer billing data to
Financial Accounting.
2010 Zensar Technologies

Page 8 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

9 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2.4

SUPERSEDES:

Excise Invoice

An entry is made in the excise as per the Delivery cum Invoice Challan and registers shall be
updated accordingly. Respective excise entries shall be passed on.
Excise Invoice, a statutory requirement created subsequently with reference to the Proforma
Invoice/Billing Document which has to be sent along with physical delivery. This component
includes Creation of Excise Invoice, Change and Cancel Excise Invoice.

2.5

Pricing and Conditions

Pricing policyBasic Sale Price

Prices are flexible based on the product moment and seasonal demand forecast.
SO s are raised for required prices
The depot transfer prices are without any discount element.
The sales could be Cash sale / credit sale.
Various elements are considered during the price fixation.

Pricing policyCommission process.


All the above elements are included in the sale price and provisions are created.

Commissions are settled at later stage through credit note or as per the announced
schemes
Pricing policy-- Taxes.

Some products are excisable and some are non excisable

Even though area wise prices are not maintained, depots can access any price based on
the mother excise.

2010 Zensar Technologies

Page 9 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

10 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Pricing is used for the calculation of prices. Various conditions are used to represent a set of
business scenarios that apply when a price is calculated. For e.g. a particular customer
orders a certain quantity of a certain product on a certain day. The variable factors like the
customer, the product, the order quantity, the date determine the final price the customer
gets. The Excise Conditions to trigger the Excise Duties Applicable is also maintained in as
master data. In exports the conditions are to be entered manually at the time of Sales Order
or Quotation as desired, taking the business model into consideration. In domestic
operations the condition records for Excise and Taxes are maintained so that these are
triggered automatically during sales order creation.

2.6

Automatic Credit Check


At present there is no specific credit check available in the system. The manual controls are
applied based on the customer outstanding amounts and ageing analysis.
Automatic Credit Checks can be specified to meet the credit management needs.
The checks can be carried out at various times during the sales order cycle, from order
receipt to delivery. After credit check the system blocks the sales order and does not allow
delivery processing unless the document is released by the appropriate manger. In
Domestic Sales Organization the credit check is division specific for example if the customer
exists in more than two divisions, division specific credit limits can be set.

2.7

Availability Check
The stock position is verified physically on receipt of sales orders.
When a sales order is entered, the delivery of goods for the required delivery can be
confirmed if the goods are available for all the necessary processing activities which take
place before delivery. The shipping department can ensure that freight forwarding or another
shipping company is advised early enough so that sufficient time remains for packing and
loading to be carried out. In exports the moment the sales order is entered in the system the
system proposes a date of delivery depending on the in house production and the total
replenishment lead time of the materials.

2010 Zensar Technologies

Page 10 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

11 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

3.

SUPERSEDES:

Enterprise Structure
The Organization elements for ARCH Pharmalabs Ltd are given below.

S.No.

Description

1.

Controlling Area

2.

Company code

3.

Sales Organization

4.

Distribution Channels

5.

Divisions

6.

Sales Area

7.

Sales Office

8.

Sales Group

9.

Plants

10.

Purchasing Organization

11.

Purchasing Group

12.

Storage location

3.1

Controlling Area

Controlling Areas is an organizational unit in Accounting which views the business organization
from a cost accounting standpoint. Controlling Areas is being used to represent a closed
system for cost accounting purposes. Controlling Areas is used for internal reporting purposes.
Multiple Company Codes can be used for same Controlling Area, to have a uniform Costing
Systems in place.
All the company codes in the controlling area must use the same Chart of Accounts and Fiscal
Year Variant.
Controlling Area 1000- Arch - Standard Hierarchy is used for all company codes.
2010 Zensar Technologies

Page 11 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

12 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

SL No

Controlling
Area

Company code

1000

1000

Arch Pharmalabs Limited

1000

3000

Avon Organics Limited

3.2

Company Code name

Company code

Company Code is the Organizational Unit of Financial Accounting for which a complete selfcontained set of accounts can be drawn up for purposes of external reporting.
This includes recording of all relevant transactions and generating all supporting documents
required for financial statements.
At each Company Code level, Balance Sheet, Profit and Loss Account and all financial
statements can be generated. Also Statements required for Legal Reporting can be generated /
balanced at Company Code level.
SL No

Company Code ID

1000

Arch Pharmalabs Limited

3000

Avon Organics Limited

3.3

Company Code Description

Sales Organization
A sales organization is an organizational unit that sells and distributes products, negotiates
terms of sale, and is responsible for these transactions. It represents the selling unit as a
legal entity. It is an organizational unit within logistics that structures the company according
to its sales requirements. Each business transaction is processed within a sales
organization. The sales organization must be specified in all sales documents.
The Sales Organizations for Arch Group are

2010 Zensar Technologies

Page 12 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

13 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Company Code

Sales Org Code

Sales Organization Description

1000
1000
3000
3000

1000
1500
3000
3500

Domestic Sales Organization--- Arch


Export Sales Organization----- Arch
Domestic Sales Organization --Avon
Export Sales Organization Avon

3.4

Distribution Channel
The distribution channel represents the channel through which salable materials or services
reach customers. Typical distribution channels include Direct, Depot sales, Inter Company
etc for Domestic & Export Sales Organization. You can assign a distribution channel to one
or more sales organizations. Within a sales organization a customer can be supplied
through several distribution channels.

Distribution Channel

Description

10
20
30
99

Direct
Depot / Warehouse
Inter-company Sale
Stock Transfer

3.5

Division
A division can be defined as a Product group that could be made up of a wide-ranging
spectrum of products. This entity normally groups together saleable materials and services
for the purpose of responsibility and analysis. For every division you can make customerspecific agreements on, for example, partial deliveries, pricing and terms of payment. Within
a division you can carry out statistical analyses or set up separate marketing.

Division
10
20
31
32

Description
Intermediates
API
CRAMS - Intermediates
CRAMS - API

2010 Zensar Technologies

Page 13 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

14 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
40
51
90
91
92

3.6

SUPERSEDES:

Agro Chemicals
Services
Others
Job work
Scrap sale

Sales Office

As per the present set up Sales Offices are defined as per the Zones of the country
Geographical aspects of the organization in business development and sales are defined using
the term sales office. A sales office can be considered as a subsidiary. Sales offices are
assigned to sales areas. If you enter a sales order for a sales office within a certain sales area,
the sales office must be assigned to that area.
Sales Offices are mapped to Areas in the present setup and made as a mandatory field in
Customer Master.

Sales office
NOR
SOU
EAS
WES
USA
EUR
ASP
MIE
LAT

3.7

Description
North Office
South Office
East Office
West Office
USA Office
Europe Office
Asia Pacific Office
Middle East Office
Latin America Office

Sales Group

At present the price and discount structures are fixed at division level. The division is nothing
but the sub area of a district in a state.
The sales office may be subdivided into sales groups. For example, sales groups can be
defined for individual divisions. For All the Sales Organizations, sales personal are mapped as
sales groups..
Sales Grp

Andhra Pradesh

2010 Zensar Technologies

Page 14 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

15 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

001
002

Mr Sudhir Nagar
Mr Vijay Garg

003
004
005
006
007
MGT
501
502
503
504
505
506
507

Mr Hemant Yadav
Mr Jatin Bhatia
Mr Rabi Panda
Domestic Sales Group # 6
Domestic CRAMS SP
Domestic/Export customers handled by Management
Mr Sudhir Nagar
Mr Prabhakar Duwuri
Mr Shrinivas V Mansabdar
Mr Samrat Choudhary
Mr Phanindra Inturi
Export Sales Group # 6
Export CRAMS SP

3.8

Sales Area
A Sales Area can be defined as a combination of Sales Organization, Distribution Channel
and Division for which each business transaction is carried out.

SO
1100
1100
1100
1100
1100
1100
1100
1100
1100
1100
1100

Distribution
Channel
10
10
10
10
10
10
10
10
20
20
20

2010 Zensar Technologies

Description
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Depot / Warehouse
Depot / Warehouse
Depot / Warehouse

Division
10
20
31
32
51
90
91
92
10
20
51

Description
Intermediates
API
CRAMS - Intermediates
CRAMS - API
Services
Others
Job work
Scrap sale
Intermediates
API
Services
Page 15 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

16 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SO
1100
1100
1100
1100
1100
1100
1100
1100
1100
1100
1500
1500
1500
1500
1500
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3100
3500
3500

Distribution
Channel
20
20
20
30
30
30
99
99
99
99
10
10
10
10
10
10
10
10
10
10
10
10
10
10
20
20
10
20
20
20
20
30
30
30
99
99
99
99
99
10
10

2010 Zensar Technologies

Description
Depot / Warehouse
Depot / Warehouse
Depot / Warehouse
Inter-company Sale
Inter-company Sale
Inter-company Sale
Stock Transfer
Stock Transfer
Stock Transfer
Stock Transfer
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Direct
Depot / Warehouse
Depot / Warehouse
Depot / Warehouse
Depot / Warehouse
Depot / Warehouse
Depot / Warehouse
Depot / Warehouse
Inter-company Sale
Inter-company Sale
Inter-company Sale
Stock Transfer
Stock Transfer
Stock Transfer
Stock Transfer
Stock Transfer
Direct
Direct

SUPERSEDES:

Division
90
91
92
10
20
90
10
20
51
90
11
12
13
14
51
10
20
31
32
40
51
90
91
92
10
20
40
51
90
91
92
10
20
90
10
20
40
51
90
10
20

Description
Others
Job work
Scrap sale
Intermediates
API
Others
Intermediates
API
Services
Others
Intermediates
API
CRAMS - Intermediates
CRAMS - API
Services
Intermediates
API
CRAMS - Intermediates
CRAMS - API
Agro Chemicals
Services
Others
Job work
Scrap sale
Intermediates
API
Agro Chemicals
Services
Others
Job work
Scrap sale
Intermediates
API
Others
Intermediates
API
Agro Chemicals
Services
Others
Intermediates
API
Page 16 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

17 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SO
3500
3500
3500

Distribution
Channel
10
10
10

Description
Direct
Direct
Direct

SUPERSEDES:

Division
31
32
51

Description
CRAMS - Intermediates
CRAMS - API
Services

ARCH/AVON
ORGANISATIONAL STRUCTURE
SALES AND DISTRIBUTION

Company Code ARCH-1000 & AVON - 3000

Sales Area
D
I
S
T
R
I
B
U
T
I
O
D
N
I
V
I
S
I
O
N

Dom Sales Organization


C
H
A
N
DCN 10Dire
E ct
L

Export Sales Organization


1500/3500

1100/3100

DC-20
Depot

DIV-10
Intermediates

DC-30

I.Com

DIV-20
API

DC-99
STO

DIV-31
CRAMSINT

DC-10
Direct

DIV-32
CRAMS-API

DIV-40
Agro
Chemicals

DIV-51
Service

DIV- 90
Others

Sales OfficeNorth, South, East, WestSales Group16


different sales personal

2010 Zensar Technologies

Page 17 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

18 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
3.9

SUPERSEDES:

Plant
Plant is an operational unit within a company code. A Plant is an organizational unit that
structures the enterprise from the production, procurement, distribution and Stock Storage
Area. The following are the plants in Arch/Avon.

Manufacturing Plant
Company
Code
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000
1000

Plant
1100
1101
1102
1103
1104
1105
1106
1107
1161
1171
1173
1200
1201
1202
1203
1301

1000

1302

1000
3000
3000
3000
3000
3000

1571
3101
3200
3201
3401
3171

Plant Description
Head Office
Arch Pharmalabs ltd - Tarapur factory
Arch Pharmalabs ltd - Badlapur Unit
Arch Pharmalabs ltd - Taloja G - 6 Unit
Arch Pharmalabs ltd - Taloja R & D Unit
Arch Pharmalabs Ltd- Tarapur, Plot- E-64 & E-82
Arch Pharmalabs ltd - Dombivali unit
Arch Pharmalabs ltd - Turbhe R & D Unit
Arch Pharmalabs Ltd- Tarapur, Plot- E-80 & E-81
Arch Pharmalabs ltd - Tarapur WH
Arch Pharmalabs ltd - Bhiwandi Godown
Arch Pharmalabs ltd - RO- Hyderabad
Arch Pharmalabs ltd - Merven Unit
Arch Pharmalabs ltd - Siddipet Unit
Arch Pharmalabs ltd - Sibra Unit
Vitalife Laboratories (A divison of Arch Pharmalabs
Ltd)
Vitalife Laboratories R&D (A divison of Arch
Pharmalabs Ltd)
Arch Pharmalabs ltd - Vitalife Bhiwadi Godown
Avon Organics Limited - Solapur unit
Head Office
Avon Organics Limited - Sadasivpet unit
Avon Organics Limited - Vadodara unit
Avon Organics Limited - Bhiwandi Ware House

Plant Location
Mumbai
Tarapur
Badlapur
Taloja
Taloja
Tarapur
Dombivali
Turbhe
Tarapur
Tarapur
Bhiwandi
Hyderabad
Hyderabad
Hyderabad
Hyderabad
Gurgaon
Gurgaon
Bhiwadi
Solapur
Hyderabad
Hyderabad
Vadodara
Bhiwandi

Depots (Plant)
S no
01

Company
1000

Plant
1172

Description
APL BHIWANDI (DEPOT)

2010 Zensar Technologies

Plant Location
BHIWANDI
Page 18 of 101

Sales Org.
4011 ALG - Exports

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

19 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
02
03

1000
1000

1271
1272

04

1000

1371

05

1000

1372

06

1000

1471

APL HYDERABAD WH (DEPOT)


APL SIBRA WH (DEPOT)
APL
VITALIFE
GODOWN1
(DEPOT)
APL
VITALIFE
GODOWN2
(DEPOT)
APL
VADODARA
GODOWN
(DEPOT)

3.10

Logical Plants (Bonded Warehouse)

S no
01
02
03
04
05
06

Company
1000
1000
1000
3000
3000
3000

Plant
1151
1152
1153
3251
3252
3253

Description
Logical Port- Maharashtra
Logical Port- Andhra Pradesh
Logical Port- Haryana
Logical Port- Maharashtra
Logical Port- Andhra Pradesh
Logical Port- Haryana

SUPERSEDES:
HYDERABAD WH
SIBRA WH
VITALIFE GODOWN1
VITALIFE GODOWN2
VADODARA GODOWN

Plant Location
Maharashtra
AndhraPradesh
Haryana
Maharashtra
AndhraPradesh
Haryana

Note -Different stocks at Different logical plants can be tracked at different


Storage locations If required additional logical bonded Locations can be created

3.11

Storage Location
To monitor the stock of the material, it is necessary to have a storage location wherein the
materials are stored. As per material storage requirements of Arch Pharmalabs, the
following storage locations (plant wise) are maintained

Plant
1100
1101
1102
1103
1104
1105
1106
1107
1161
1171
1173

Storage location ID
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01

2010 Zensar Technologies

Description
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Page 19 of 101

Sales Org.
4011 ALG - Exports

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

20 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
Plant
1200
1201
1202
1203
1301
1302
1571
3101
3200
3201
3401
3171
1100
1101
1102
1103
1104
1105
1106
1107
1161
1171
1173
1200
1201
1202
1203
1301
1302
1571
3101
3200
3201
3401
3171
1100
1101
1102
1103
1104
1105
1106

Storage location ID
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
FG01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
SY01
RT01
RT01
RT01
RT01
RT01
RT01
RT01

2010 Zensar Technologies

SUPERSEDES:

Description
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
Scrap Yard
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
Page 20 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

21 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
Plant
1107
1161
1171
1173
1200
1201
1202
1203
1301
1302
1571
3101
3200
3201
3401
3171
1100
1101
1102
1103
1104
1105
1106
1107
1161
1171
1173
1200
1201
1202
1203
1301
1302
1571
3101
3200
3201
3401
3171

Storage location ID
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
RT01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01
SF01

SUPERSEDES:

Description
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
FG Return Store
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate
Intermediate

Depot Storage Locations


2010 Zensar Technologies

Page 21 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

22 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

Plant
1172
1271
1272
1371
1372
1471

Storage location ID
FG01
FG01
FG01
FG01
FG01
FG01

SUPERSEDES:

Description
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods

Storage Locations (Logical Plants)


Plant
1151
1152
1153
3251
3252
3253

4
4.1

Storage location ID
FG01
FG01
FG01
FG01
FG01
FG01

Description
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods
Finished goods

Master data:
BBP_SD_BP01: Customer Master

The data relevant to all the customers of the company are maintained in the form of Customer
Master Records. The following types will be used to differentiate between the customers.
Customer master Exports: Customer Master Data contains all the details pertaining to a
customer like his Name, Address, Contact Information, Payment terms, Shipping Terms,
Delivery Priority & Partner Functions.

Account Groups:
The account group is a classifying feature within customer master records.
All the Domestic Customers, Consignees, Inter Company Customers and Export
customers of the company would be grouped into separate groups.
2010 Zensar Technologies

Page 22 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

23 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Domestic:

The account group is a classifying feature within customer master records.


All the Domestic customers of the company would be grouped into separate group.

Account
Code
ZDOM
ZDSH
ZDIP
ZDIC
ZINT

Group Description
Domestic Customer
Domestic Consignee
Intra Plant Customer
Inter Company Customer
STO Customer for Plant

Number range assignment to customer account groups


No
Range
series
8
6
7
2
3
5
4

Account
Group
ZDBP
ZDIC
ZDIP
ZDOM
ZDSH
ZESH
ZEXP

Description
Domestic Bill-to party
Inter Company Customer
Intra Plant Customer
Domestic Customer
Domestic Consignee
Export Consignee
Export Customer
STO Customer - plant
Specific
IP

ZINT

From
350001
800001
900001
100001
300001
600001
500001

To
359999
899999
999999
199999
349999
699999
599999

1100

4999

Sold-To Party
The Customers Organization Sold-To party is the legal entity that represents
Arch/Avon customer. This is the entity that takes ownership of the goods they
purchase and often has many users, or contacts working within their Organization.

2010 Zensar Technologies

Page 23 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

24 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Ship-To Party
To whom and where the goods are shipped. Ship-To party is the entity that
physically receives products. One Sold-To party could have multiple Ship-To
accounts associated with it. Many of these Ship-To accounts may be user specific
accounts. For Arch/Avon (Dom) Ship to party account can be different than the sold
to party account.

Bill-To Party
To whom the invoice will be sent. The Bill-To Party is the entity or person that will
receive the invoice. For Arch/Avon (Dom) Bill to party account can be different than
the sold to party account.
Payer
Payer is the entity or person who is responsible for payment. The Payer is the
entity or person that is responsible for account settlement. The Payer will have a
credit limit and an accounts receivable account. It is important to note that the Payer
is aligned with credit control. In this manner, Company can manage the risk of an
entire organization or group of individuals within an organization. For Arch/Avon
(Dom) the Payer account can be different than the sold to party account.

Exports:
Account
Code
ZEXP
ZESH

Group Description
Export Customer
Export Consignee

Sold-To Party
The Customers Organization Sold-To party is the legal entity that represents
Arch/Avon customer. This is the entity that takes ownership of the goods they
purchase and often has many users, or contacts working within their Organization.

Ship-To Party
To whom and where the goods are shipped. Ship-To party is the entity that
physically receives products. One Sold-To party could have multiple Ship-To
accounts associated with it. Many of these Ship-To accounts may be user specific
accounts. For Arch/Avon Ship to party account can be different than the sold to party
account.
2010 Zensar Technologies

Page 24 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

25 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Bill-To Party
To whom the invoice will be sent. The Bill-To Party is the entity or person that will
receive the invoice. For Arch/Avon Bill to party account can be different than the sold
to party account.
Payer
Payer is the entity or person who is responsible for payment. The Payer is the
entity or person that is responsible for account settlement. The Payer will have a
credit limit and an accounts receivable account. It is important to note that the Payer
is aligned with credit control. In this manner, Company can manage the risk of an
entire organization or group of individuals within an organization. For Arch/Avon the
Payer account can be different than the sold to party account.

Commission Vendor
The sales vendors are responsible for selling products or services.

Master data also enables partners to be automatically linked with a business


transaction.

Customer Master Structure

You can create and change master records using groups of data that differ in the
level of detail. Master records for business partners who are customers have the
following structures.

General Data

General data does not depend on the company code or the sales and distribution
organization. General data applies to one business partner for all company codes, and in
all sales areas. It is shared information across Arch/Avon Organization. General data is
used in many functions including promotions, order entry & acknowledgement, financial
2010 Zensar Technologies

Page 25 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

26 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

and sales reporting.


It includes:
o
o
o
o
o

Customer Number
Account Group
Company address or
Persons name & address
Contact persons

Company Code Data

Company code data only applies to company code, (i.e. for Arch/Avon). This data is
only relevant to Financial Accounting.
Reconciliation Account
The reconciliation account in G/L accounting is the account which is updated parallel to
the sub ledger account for normal postings (for example, invoice or payment).

Sales Area Data

The data for one customer can differ for each sales area. A sales area is a combination
of sales organization, distribution channel and division.
o

Sales office

A Sales office would be defined for a territory or region. They would be assigned
to the sales areas. An area manger with specified (one or more districts) area
shall be monitoring the sales
o

Sales group

Employees of a sales office can be assigned to sales groups. A sales group


consists of a certain number of sales representatives.

Customer Pricing Procedure.

2010 Zensar Technologies

Page 26 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

27 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

A group of customers who share the same pricing procedure

o
Customer statistics Group.
This field is used for updating the Sales Information System Reports
Shipping Condition
Shipping point determination would be carried out by the SAP system if a
shipping condition is contained in the sales document. The shipping conditions
defined in the customer master record would be copied into the sales document
header which would then be used to determine the shipping point.
o

Shipping
condition
01
02

Description
Standard
Pickup

Need based shipping conditions shall be created accordingly.


o

Account Assignment Group

The account assignment group to which the system automatically posts the
sales document

01
02
21
31

Domestic Revenues
Domestic - SEZ
Export
Affiliated Companies

Tax Classification

The tax classification for Export & Domestic Customers is as follows


o

Exports

Tax
2010 Zensar Technologies

Description
Page 27 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

28 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Classification
0
Tax exempt
1
Full tax

Domestic
Tax
Classification
0
1
2
3
4
5
6

Description
Fully Exempt
Full tax
50% tax
Without from C
against from 'F'
against from 'H'
against from 'I'

Maintenance of Master Data shall be handled by central ERP team at Head Office. All the
controls including setting of block or deletion flag shall be handled by the team. The application
for the Master Data creation as well as modification needs to be approved by concerned.

4.2

BBP_SD_BP02: Material Master (Sales views)


Descriptions of the individual materials used in an enterprise would be stored in material
master records. The following section explains some of the important views and
information a material master record contains and that are relevant for sales and
distribution:

i. Sales Org 1
In this view, we would define basic data and units of measure and tax
classification (e.g. sales units)
Important fields:
2010 Zensar Technologies

Page 28 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

29 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Base Unit of Measure - Unit of measure in which stocks of the material are
managed. The system converts all the quantities you enter in other units of
measure (alternative units of measure) to the base unit of measure.

Sales Unit Unit of measure in which the material is sold. This field would be
used if a unit of measure differing from the base unit of measure is used. This
would be proposed in other transactions/events, where it can be changed. The
sales unit KG would be used for Domestic & Exports.

Old Material Number-- You can use the old material number to systematically
search for material master records via match codes

Delivering Plant - Plant from which the goods should be delivered to the
customer.

Division The division would be used to determine the sales areas and the
business areas for a product.

Alternate unit of measurement-The material is having three alternate unit of


measurements which are maintained in additional data tab in material master.
The BOM and sale unit is available in transaction, whereas the other UOM shall
be considered in output.

ii. Sales Org 2


This view contains Material groupings (e.g. material pricing group)
Important fields:

Material Pricing Group--- A combination of customer and material pricing group & a
combination of price group and material group. This has been activated for maintaining
price on basic unit of measure for different pack codes.

01

Normal

02

Spare Parts

A few examples are given above


2010 Zensar Technologies

Page 29 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

30 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Account Assignment group - A grouping of materials that the system uses to


determine the revenue or sale deduction account when creating an accounting
document from a billing document. This is used for determining the accounts to
which goods values or distributions are posted.
10

API

20

Intermediates

31

CRAMS-Intermediates

32

CRAMS-API

40
51

Agro Chemicals
Services

90

Others

91

Job work

92

Scrap Sale

Item Category group - A grouping of materials that the system uses to


determine item categories during the processing of sales documents. All the
items would be grouped as Standard items for sales.

iii. Sales/Plant Data


In this view Sales and shipping data (e.g. gross weight, loading group) are defined.
Availability Check - Specifies whether and how the system checks availability and
generates requirements for materials planning. The system generates the requirements
for Materials planning for each sale order. For exports the 02 is the availability check
which is used to generate individual requirements for scheduling and planning for the
material availability.
01
02

2010 Zensar Technologies

Daily requirements
Individual requirements

Page 30 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

31 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

4.3 BBP_SD_BP03: Pricing condition records


The Pricing Condition records would allow you to store and retrieve pricing data in the
system. All the pricing elements for the business - freight and taxes - that would be used
for automatic pricing must be stored in the system as condition records.
The following condition records are required to be defined for the different pricing
elements for any validity period.
These pricing condition records would be maintained by the Sales and distribution team
in coordination with the Finance and Operations department.
Domestic Pricing
Pricing Procedures

Description

ZCRAM1

Exp.Pricing Procedure-CRAMS

ZCRAM5

Service Pricing ProcedureCRAMS

ZDEPOT

Depot Pricing Prcd-Arch/Avo

ZDOM11

Dom.Jobwork Returns

ZDOMTP

Dom. Returns Pricing Procedure

ZDOM15

Deemed Exp Pricing Arch/Avon

ZDOMLL

Dom Jobwork Pricing

ZDOMRT

Dom. Returns Pricing Procedure

ZDOMTP

Dom.Third Party.Pricing Procd

ZDSTO1

STO Pricing Procedure-Arch/Avo

ZEXP01

Exp.Pricing Procedure

ZEXPRT

Exp.Returns Pricing Procedure

ZPSQTN

PS Quotation Pricing

As some of the elements may be settled through credit note or debit note a separate document
type along with pricing has been proposed. For ex expenses like freight, other discounts
The following Condition types are used in preparing the above pricing procedures to cater the
requirements of the organization.

2010 Zensar Technologies

Page 31 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

32 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
Condition types

Description

JEXP

IN: A/R BED %

JECS

IN A/R E-Cess

JA1X

A/R Sec & Hr ECS

JIVC

A/R CST Payable

JIVP

A/R VAT Payable

JLSR

IN A/R LST Surcharge

JLST

IN A/R LST

ZC02

Inland Comm Amt Item

ZC06

Oversea Com Amt Item

ZCON

Conversion Charges

ZD02

Discount Amount Item

ZECD

Imp Duty- Unload Pt

ZF02

Freight Amount Item

ZF04

Palletization

ZF05

Stuffing

ZF06

Chocking Chrg

ZF07

THC Shipping

ZF08

Carting Charges

ZF09

Transport Crg(Inland

ZF10

Loading & Unloading

ZF13

B/L & AWB Doc Chrg

ZF14

Transport CFS

ZF15

Custom Doc Chrgs

ZF16

Ground Rent

ZF17

Repacking gharges

2010 Zensar Technologies

SUPERSEDES:

Page 32 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

33 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
Condition types

Description

ZF18

Handling & Trnps CFS

ZFRT

Freight Amount Item

ZI02

Insurance Amt Item

ZOIC

Other Incidental Chg

ZP01

Basic Price-Dom

ZP02

Basic Price-STO

ZP03

Job Work Rate

ZP04

FOB Price

ZP05

Depot Base Price

ZP06

CIF Price

ZPPS

Project Service Cost

ZTCS

Tax Colctd @ source

ZTPP

Third Party Price

SUPERSEDES:

The following access sequences are maintained to differentiate tax calculation from region to
region and to cater the other requirements of the organization.

Country/Plant Region/Customer Region/ Tax Classification Customer/ Tax


Classification Material

Exports Pricing

Pricing
Procedures

Description

ZEXP01

Exp. Pricing Procedure

Condition Type

Description

2010 Zensar Technologies

Page 33 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

34 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document
ZF04

FOB Price

ZF06

CIF Price

ZC02

Inland Commission (Item)

ZC06

Inland Commission( Item)

SUPERSEDES:

The following key combination would be used in Access Sequence to determine prices
for materials during Sales order processing in case of Controlled Products, Manual
pricing is used for regular products.
o
o

Customer/ Material with Release Status


Material with Release Status

5 Business Processes
5.1 BBP_SD_BP01: Standard Order
Process Description: As Is
The customers are indenting the orders directly on the Company for supplying the material. A
Standard Order is used to process customer purchase orders for material the process of
creating a standard sales order begins with the customers request for materials to be sent to
2010 Zensar Technologies

Page 34 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

35 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

them. This purchase order could be via phone, mail or fax. Once a customers purchase order
is received, the order is processed through Sale order form (SO). The SO is raised for the
required quantity after considering the factory stocks the dispatches shall be planned and
invoices are generated based on the customer tax liability. The deliveries shall be made directly.
Process Description:
A Standard Order is used to process customer purchase orders for material that is owned by the
sales organization. The standard order will result in normal scheduling of deliveries and, in
many scenarios, is relevant for pricing since customer billing will occur from the delivery of
materials ordered on the standard order.
The process of creating a standard sales order begins with the customers request for materials
to be sent to them. This purchase order could be via hard copy, phone, e-mail or fax. Once a
customers purchase order is received, the order is manually entered into the SAP R/3 system
via the VA01 Sales Order Entry transaction. The sales area responsible for processing the
order is entered along with the sold to business partner, customers purchase order number,
material number, delivering plant and ordered quantity. The remaining information on the sales
order is derived from master data (e.g., customer, material and pricing conditions) and system
configuration for automatic determination (e.g., shipping point). The process of creating a
standard order ends when the order is saved and all required fields are entered (based on
incompletion procedure rules).
During the creation of a standard order, several processes are performed to ensure the order
can be filled to the customers satisfaction and within the constraints of Arch Pharmalabs
policies. These processes are described below.
1) Customer PO information - PO number field would be a required field for Standard sales

order.
Arch Pharmalabs will use INCO terms which would default into Sales order from Sold to
customer master data. The value can be changed during order entry by customer service as
per the requirement.
2) Business Partner Determination - Based on the sold-to business partner, the default ship-

to, bill-to, Vendor and payer partners are proposed into the order. If multiple Ship tos exist
for Sold to, the default Ship to number (same as sold to) can be changed during order entry
through a pop up screen selection.
3) Batch Determination - Batch numbers (if required) can be manually entered at the time of

sample sales order and they would be copied to delivery document if not then system does
automatic batch determination during creation of outbound delivery for Domestic
Operations.
4) Scheduling - The system calculates the schedules required to deliver the order based on

the delivering plant. Order will capture the Requested delivery date even after the system
2010 Zensar Technologies

Page 35 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

36 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

proposes different availability dates based on availability of Inventory. Requested delivery


date can be entered at line item level.
5) Availability Check Availability check is carried out automatically and the system proposes

the delivery date when there are no ready quantities available in the respective plant
locations by taking the replenishment lead time into consideration.
6) Pricing - Customer pricing is need to be updated manually during Order creation

7) Credit Control - The system performs credit checks against the designated payer business

partner. The order is blocked for delivery if credit checks are not passed. In domestic sales
the credit control is division specific and the customer is blocked for delivery only for the
division for which he has exceeded the credit limit set.
8) Free Samples: The sample sales order would have the facility to determine free samples

and these would not be relevant for billing. Customer Service has to enter this during the
sales order entry.
9) Output: The order confirmation/Proforma Invoice output can be obtained from the Sales

order for exports. This requirement is not there for Domestic at the stage for sales order.
Open Orders: In case of a change in the existing price, the current price will get updated in the
open orders. This function has to be carried through modifying the sales order manually.
SAP Configuration Considerations / Decisions:

Document type ZO10, ZO11, ZO12, ZO13, ZO14, ZO18 will be used with internal
number range for Manual Orders being entered by Logistics Department.
Material, order quantity, plant, shipping point, material price, gross weight, and net
weight will be required fields at item level.
Document types ZO10, ZO11, ZO13, would be relevant for automatic credit control.
Sold to party, Payer, Bill to, Ship to, for Client will be required partners on sales order.
Standard order can be raised at depot level and factory level.
Material Information, Customer Information, Payment terms etc will be not be allowed to
any modification at transaction level through customization.
Sales orders that are pending for what so ever reason ,needs to be reviewed periodically
by the marketing team and to be short closed with a suitable reason.

5.2 BBP_SD_BP02: Sample Order

Process Description: As Is
2010 Zensar Technologies

Page 36 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

37 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Samples will be dispatched from the depots and Mfg Plants to the customers. These
samples will be consumed by the customers for before confirming the order.
Process Description:
A sample order is used to send free samples to customer. As the system cannot create a
delivery without a sales document, so the user has to create sales document type for sample
order. The delivery is actually a sales document type that is only relevant for deliveries and not
invoicing. A proforma invoice can be generated to generate excise liability if material is
excisable.

SAP Configuration Considerations / Decisions:


A separate document type ZO16 is created for sample order with Proforma billing type as
ZF8D/ZF15

5.3 BBP_SD_BP03: Stock Transfer Order


Process Description: As Is
Stock transfer process--As per the market requirement depot in charge is placing the orders to
head office for material and subsequently the SO is raised based on the availability of material
at factory. Based on the market demand and order position, the production schedules are
planned on daily basis. On urgency, material can be transferred to other depots through depot
transfers.

Process Description:
In the normal course of business, there may be the requirement of transferring the materials
from one plant to another. To meet this requirement and to have records of all the movements of
goods, normally the Stock Transport Order is being used in the business. Since the Stock
Transport Order has all the characteristics of a purchasing document, hence movements of
goods can be traced and all subsequent transaction can be monitored at any point of time. In
the standard SAP, the following procedures are available for stock transfer by using the stock
transport order:
2010 Zensar Technologies

Page 37 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

38 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

-Stock Transport Order without Delivery


-Stock Transport Order with SD Delivery via Shipping
-Stock Transport Order through MM (addressed in MM BBP)
Process Flow & Stock Updates
The following is process flow for stock transfer by using the stock transport order:

Indenting/receiving plant creates a stock transport order for the quantity


required/needed.
Unrestricted-use stock of supplying plant is decreased to the tune of
quantity supplied against the stock transport order. Stock in transit of the receiving plant
is increased
Indenting plant receives the goods and post the goods receipt with reference to the stock
transport order.
The stock in transit is reduced and the unrestricted-use stock increased in the receiving
plant

Effects of Stock Transport Order


The following are effects of using a stock transport order for transfer of stock.

A goods receipt can be planned in the receiving plant. If needed, delivery


costs can be captured in the stock transport order

The stock transfer order can also be used in MRP .A delivery via Shipping can be used
for goods issue.

The goods can be posted directly to consumption. Stock transport Order history is
updated

SAP Configuration Considerations / Decisions:


Depot Transfer Process:
Order type ZUB1 is used for Stock transport Order with reference to purchase requisition.
2010 Zensar Technologies

Page 38 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

39 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Movement types 641 for Goods Issue


Delivery type is ZNL.

A customer number of the receiving plant is maintained in the plant. This customer number is
used in SD shipping processing to identify the goods recipient (ship-to party) if provision has
been made in Customizing for a stock transfer to be carried out with an SD delivery
The STO process is configured by defining receiving plant as a customer and distribution
channel (99).
Sales organization 1100 /3100
Distribution channel 99
Division

00

With this data, the system determines the shipping data for the material to be transferred (e.g.
the shipping point).
Excise invoice is created with Proforma invoice (ZJEX). As soon as the marketing team receives
the branch indent, they can analyze the requirement and process Stock transport Orders for
available stocks at plant as well as other depots.

5.4 BBP_SD_BP04: Supplementary Invoice


Process Description: As Is
In certain circumstances additional duties have to be paid to the excise department on the
stocks available at different depots due to the fluctuation in the price.

Process Description:
The Organization may have to pay differential duty as the assessment was provisional or
price was escalated later or duty was short paid through mistake or for any other reason. In
such cases, the organization has to pay differential duty by preparing supplementary
invoice. Buyer can avail Cenvat credit on basis of such supplementary invoice. Though
rules do not specify, such supplementary invoice should be from same series of invoice. It
should give cross reference to the original invoice under which the goods were cleared.
2010 Zensar Technologies

Page 39 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

40 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

SAP Configuration Considerations / Decisions:


The normal SD process like creation of sale order from depot and proforma invoice shall be
created. Through standard transactions, Excise Journal Voucher can be generated under other
adjustments head.
This process shall be mapped as per AVON/ARCH requirement after considering various factors

5.5 BBP_SD_BP05: Job work Order - with only service charges


Process Description: As Is
Job work order - Customers release the job work orders to company for processing material
and subsequently the Job Work Order / invoice is raised with service charges
Material is received under customer material challan. After processing; delivery shall be done
along with subsidiary Challan and billing.
Process Description:
Process Flow & Stock Updates
The following is process flow for Job Work by using the Job Work order:

Customer Material is created as non valuated material


Create a Job work order against that customer
Then receive the material quantity
After process completion, delivered the material with subsidiary challan (with excise
entries).
Service charges are invoiced against delivery

SAP Configuration Considerations / Decisions:


The process is mapped by creating the Job Work order -Order type (ZO18).
Delivery type is ZLFD
Service invoice is created with ZF18
Excise invoice is created with invoice (ZO18)
2010 Zensar Technologies

Page 40 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

41 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

5.6 BBP_SD_BP06: Job work Order with material cost and service charges
Process Description: As Is
Job work order - The customers release the job work orders to company for processing
material. The finished product is produced by adding the in house material to the customer
material subsequently the Job Work order/ invoice is raised with service charges plus actual
material cost through regular sales order charging the cost of raw material and excise duties
Process Description:
Process Flow & Stock Updates
The following is process flow for Job Work by using the Job Work order:

Customer Material is created as non valuated material


create a Job work order against that customer
Bill the excess materials and receive against Job work order.
Then receive the material quantity
After process completion, delivered the material with subsidiary challan (with excise
entries).
Service charges plus material cost are invoiced against delivery

SAP Configuration Considerations / Decisions:


The process is mapped by creating the order - Job Work Order type (ZO18).
Delivery type is ZDLF
Job Work invoice is created with ZF18
Regular Sales Order created for billing Raw Material ZO11
Excise invoice is created with Raw Material invoice ZF10

5.7 BBP_SD_BP07: Third Party Sales (Trading Products/ sale in transit)


Process Description: As Is
2010 Zensar Technologies

Page 41 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

42 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Apart from the sale of manufactured products, ARCH / AVON have the sales of trading products.
They are procuring finished products and selling directly to customers from their vendors.

Process Description:
The Trading Order is the main document in Trading Order Management. The organization can
process both purchase and sales data either simultaneously or separately, using one document.
This forms the basis of all purchasing, sales and expense processes and provides the
organization with a clear overview and process control of all related business transactions. As it
takes account of purchasing prices, sales prices and expenses the trading order allows
organization to perform a profitability simulation immediately. The trading contract can support
Back-to-back transactions as well as one-sided purchasing and sales transactions
SAP Configuration Considerations / Decisions:
Order Type ZO12 is created for Domestic Third Party Order. Domestic Third Party Order can
be raised with specific requirements of the customer. System will generate the purchase
requisition on saving the sales order.
A system generated purchase requisition shall be processed by purchase department which
shall be addressed in MM Module.
In Sales and Distribution, the Trading products as well as manufactured goods have different
pricing structure. A normal sales order, in case of customers purchase order, suffices the
requirement.

5.8 BBP_SD_BP08: Project based Order


Process Description: As Is
Project based order - The customers release the orders to company for developing the new
molecule. The product is produced by adding the in house material to the customer material
subsequently the Project based order/ invoice is raised with service charges plus actual
material cost through regular sales order charging the cost of raw material and other charges if
any.
2010 Zensar Technologies

Page 42 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

43 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Process Description:
Process Flow
The following is process flow for Project based order:

Project based Order will be created based on the Customer PO and WBS assigned to
that Order item.
Whenever Customer places Order for Services then Service order needs to be created.
After process completion, deliver the material with Development Charges.
Service charges are invoiced against Order.
Service order is created with service material and pricing will be updated manually
based on the utilization hours.
Billing will be generated periodically as per the requirement.

SAP Configuration Considerations / Decisions:


The process is mapped by creating the order Project based Order type and Service Order
(ZPRO/ ZFTE).
Delivery type is ZLFE
Job Work invoice is created with ZF65
Service Order created for billing services ZFTE
Excise invoice is created with Raw Material invoice ZF66
Creation of Billing plan type 02 (Periodic Billing)

5.9 BBP_SD_BP09: Customer Return Order


Process Description: As Is
AVON/ARCH
The stock returned by the customer because of / damages/ leakages or quality is taken into
account. No replacement order process. The stock returned/rejected by the customer is
accounted and a credit note is prepared for that customer. The customer should mention the
invoice number on which he originally received the goods from the branch office. If the stock is
2010 Zensar Technologies

Page 43 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

44 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

returned within six months then the sales tax amount paid is returned to the customer. If the
customer returns the stock after six months the sales tax is not paid to the customer.
Process Description:
Return order processing is one of the components of Returns to Credit end to end business
process .The other components of end to end process such as Returns delivery processing,
goods receipt, credit memo processing are covered under separate process documents.
Returns are used to process goods delivered to a customer which were damaged, are no longer
needed, short shipped, have expired, or are about to expire. The return process starts with a
customer request to return product or product being returned with or without prior notification. A
return order is entered indicating the material being processed in the return with reference to
customer invoice. The return order will have a billing block, which will need to be removed
before customer can receive reimbursement. A return delivery is created with reference to the
Billing Document to allow the receiving of the returned material. Posting of the goods receipt is
used to document the incoming movement of material to a specific returns location. The return
process ends with a credit memo or a rejection of the return.

Return order could be created in the system in following circumstances:

Wrong product shipped to customer


Customer ordered wrong product and wants to return
Material damaged in transit
Product recalls
Material quality complaint
Batch problem

Return order for customer returns due to wrong products shipped, wrong products
ordered, expired products and Product recalls:
After verification of the complaint and approval of complaint (Verification and approval would be
handled outside SAP), Return order type ZRED, will be created with reference to original Billing
Document. If the complaint from customer is against multiple SO or the SO generated in legacy
system, Return order will be created w/o reference. All prices will be manually adjusted in
Return order if necessary.
Return Order processing:
2010 Zensar Technologies

Page 44 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

45 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Returns can be tied directly to a Billing Document. By examining the document flow of
an SO, one can be able to see associated returns.
Flexibility exists to process returns for multiple invoices.
All Return orders in general would be created in SAP with reference to Original Billing
Document. If original Billing Document doesnt exist in system or original Billing
Document is unknown or Return required for multiple original invoices, then the Return
order will be created without reference. When Return Sales order is created without
reference to original Billing Document, the system determines price for materials from
current list price. If this price is different from original Billing Document price then
customer service can change price for each material during order entry.
All Return orders would have a default billing block 08-Check Credit memo at the
header. Distribution Manager will remove the block after verifying goods received at
matches with Billing Document.
INCO terms would default from customer master or original invoice during Return order
creation and they can be changed during order entry if required. Customer service would
not enter batch number as this would be copied from the Billing Document directly for
each material during order entry.
Order reason will be a required field and customer service has to pick appropriate
reason from drop down box. They can be used for reporting purpose
1. Wrong product shipped
2. Customer return
3. Damaged in transit
4. Product expired
5. Product recall
6. Miscellaneous
7. Short shipment
8. Sales Call
Return Goods authorization document can be printed immediately after saving Return
Sales order type ZRED.
Shipping department will inform Customer service if material is returned from customer
without prior notification to take appropriate action with respect to talking to customer,
creating Return order in the system etc.
The returned stocks are immediately posted to blocked/quality stocks.

SAP Configuration Considerations / Decisions:

Sales document type ZRED, will be used with Internal number range
Return order types are not relevant for credit check
PO number field will be a required field.

2010 Zensar Technologies

Page 45 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

46 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

5.10 BBP_SD_BP10: Credit and Debit memo request processing


Process Description: As Is
Credit notes are issued in the following scenarios
Sales Return -- The stock returned by the customer because of / damages/ leakages/
expiry/near expiry is taken into account. The stock returned/rejected by the customer is
accounted and a credit note is issued to that customer.
Debit notes are issued in the following scenarios.
If excess goods are sent or Taxes are wrongly charged while moving the materials or price
charged is less than the approved price. Debit note is issued to customers under these
scenarios.
Process Description:
This covers following business processes:
Credit memo requests
Debit memo requests
The debit and credit memo process in SAP is used to process customer complaints specific to
sales and distribution activities. This process starts with a sales document (debit or credit memo
request) to capture the request. These documents can reference an invoice, in which selected
information can be copied. HO enters the information regarding the complaint in the document.
The document for processing depends on the nature of the complaint as explained in the
scenarios below. The document is blocked for billing (default billing block). In general a credit
memo request should go through an approval process.
Credit memo request - This is a sales document used in complaints processing to request a
credit memo for a customer. If the price calculated for the customer was too high (for example,
with the wrong scaled prices or because a discount was forgotten), you can create a credit
memo request.
Debit memo request - This is a sales document used in complaints processing to request a
debit memo for a customer. If the price calculated for the customer was too low (for example,
with the wrong scaled prices or freight charges), you can create a debit memo request.
2010 Zensar Technologies

Page 46 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

47 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Reasons for Credit Memo Request processing:


Goods damaged in transit due to Carrier error:
After verification of the complaint and approval of complaint (Verification and approval would be
handled outside SAP), Credit memo request will be created with reference to original SO. All
prices will be manually adjusted in Credit memo request if necessary. If the complaint is against
multiple SO, Credit memo request will be created w/o reference.
Customer registers a complaint because they were charged too much for the item or
order:
After verification of the complaint and approval of complaint (Verification and approval would be
handled outside SAP), Credit memo request will be created with reference to original Billing
Document. If the complaint from customer is against multiple Billing Documents, Credit memo
request will be created w/o reference. The price difference will be manually entered Credit
memo request.
Reasons for creating Debit memo Request processing:
Customer was charged too less for the item or order:
After verification of the complaint, Debit memo request will be created with reference to original
Billing Document. If the complaint is across multiple Billing Documents, Debit memo request will
be created w/o reference. The price difference will be manually entered Debit memo request.
Customer wasnt charged freight charges on original invoice:
After verification of the complaint, Debit memo request will be created entering Freight
adjustment material and freight will be manually in header conditions in Debit memo request.

SAP Configuration Considerations / Decisions:


1. All Credit memo requests would be created in SAP with reference to Original Billing
Document. If original Billing Document doesnt exist in system or original Billing
Document is unknown or Credit required for multiple original Billing Document then
Credit memo request would be created without reference.
2. Customers Invoice number would be entered in PO number field on Credit memo
request and this will not be a required field.
2010 Zensar Technologies

Page 47 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

48 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

3. Sales order document type (ZCRD ) would be used for Credit memo requests with
internal number range for other credit notes ex- commission settlement etc.
4. All Credit memo requests would have a default billing block 08-Check Credit memo at
the header. Customer service Supervisor will remove the block after Sales order is
saved by customer service.
5. Order reason is a required field and customer service has to pick appropriate reason
from drop down box. This field is used for reporting purpose.
6. Invoice header text would be used if required and this text will be printed on Credit
memo. If Credit memo request is created without reference to original Billing Document,
the system determines price for materials from current list price. This price is needs to
be adjusted by customer service based on each material and price to be adjusted.
7. All credit memo requests would be created in SAP with reference to Original Invoice. If
original Invoice doesnt exist in system or original Billing Document is unknown or credit
is required for multiple original Billing Documents then Credit memo request would be
created without reference.
8. Sales order document type (ZDRD,) would be used for Debit memo requests with
internal number range.
9. Order reason is a required field and customer service has to pick appropriate reason
from drop down box. This field is used for reporting purpose.
10. Invoice header text would be used if required and this text will be printed on Debit
memo.
11. If Debit memo request is created without reference to original invoice, the system
determines price for materials from current list price. This price is needs to be adjusted
by customer service based on each material and price to be adjusted.

5.11 BBP_SD_BP11: Outbound Delivery Processing


Process Description: As Is
Based on SO, goods are dispatched to the customer through DC cum Invoice. A delivery
Challan is made with the product details and the customer details as well as batch details. Once
a DC is made the stock is reduced from the stock ledger. Excise invoice shall be made for
excisable goods.
2010 Zensar Technologies

Page 48 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

49 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Process Description:
Delivery processing is one of the key components of Order to Cash end to end business
process. Delivery Processing, sometimes referred to as Shipping, covers the functions which
take place between Sales Order Completion and Physically Shipping the Product:
Outbound Delivery Documents include:
1. Standard Delivery process supporting all Sales Orders inclusive of Free of charge sample
orders.
2. Delivery Reversals.
3. Output Documents required during Standard Delivery processing.
4. List of reports needed to support Standard Delivery processing.
A Delivery document is created when an order line is completed, that is the inventory is
available and no holds apply. The Delivery Document contains a header and items section.
The Document Header
The general data relevant for shipping is stored in the document header. This data is valid for
the entire document. It includes the following:
Shipping point, which is explained in detail later in the document
Data on delivery scheduling and transportation scheduling (for example,
the goods issue date or the delivery date at the ship-to party)
Number of the sold-to party and the ship-to party
This is the data that applies to one particular item. For example,

Material number
Delivery quantity
Plant and storage location specifications
Batch (Lot) Allocation
Picking date

The Delivery Document obtains most of its information automatically from the sales order
header and line detail. Some information is also passed from the Customer and Material
Masters. A delivery is processed through one shipping point. Shipping Points can be
determined in the sales order for each item and depend on 3 factors:

Shipping Condition set up in the customer master. e.g. (Ship) As soon as possible.

2010 Zensar Technologies

Page 49 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

50 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Loading Group from the material master record.


Delivering Plant, which is determined from the customer master if present or the
material master if not.

Certain prerequisites must be met before an order can be delivered. When a delivery is created,
the system carries out various functions which add to the data in the delivery and check its
validity:
The delivery quantity of an item is determined and the availability of the
material is checked.
The delivery situation of the order and any partial delivery agreements are
checked.
1. The Client can have partial delivery agreements with all customers. Delivery qty can be
changed during picking if material is physically unavailable as per scheduled quantity in
sales order.
2. No Delivery will be created with 0 quantity
3. Availability check (ATP) would be performed during delivery creation for all the line items
due for delivery on scheduled delivery date.
4. Shipping Instructions will be copied from Sales order into Delivery document if same is
entered on Sales order.
5. Batch Determination would happen in the Delivery creation mode based on the Pre
Determined criteria of FEFO ( First Expiry First Out )
6. The Delivery department can combine different sales orders for the same customer whose
shipping address, delivery dates, INCO terms Shipping Conditions are the same and create
a single delivery document.
Reversal of Post Goods Issue:
To accommodate rare occurrences where a product is shipped out but then retrieved in
order to ship it elsewhere.

SAP Configuration Considerations / Decisions:

Delivery Document types ZLRD and ZLFD for Domestic will be used.
Delivery Document types ZLRE, ZNL, ZLFE and ZLFD will be used for Job Work,
Replenishment and Exports Deliveries respectively.
Shipping Conditions (01 Standard and 02 Pickup)
Shipping Points
Define Delivery Types with Internal number range
Define item categories and item category determination in deliveries

2010 Zensar Technologies

Page 50 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

51 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

No specific delivery tolerances required. Copy controls are being maintained with reference
to sales order quantity.
Set up incompletion procedures and copy control requirements for deliveries
Set up ATP during delivery processing
Set up automatic batch determination during delivery processing for Domestic & Exports.
Set up output determination during delivery processing.
The system date / document created date shall be the actual goods issue date.

5.12 BBP_SD_BP012: Returns Delivery Processing


Process Description:
Returns Delivery processing is one of the key components of the Returns to Credit end to end
business process. Returns Delivery Processing covers the functions which take place between
Returns Sales Order Completion and Credit memo:
Return Delivery Documents include:
1. Returns Delivery creation
2. Goods receipt for Returns Delivery
3. List of reports needed to support Returns Delivery processing.
A Returns Delivery document is created with reference to Returns Sales order. Returns delivery
will be created manually when the goods are physically received by the Shipping point from
customer.
1. Returns Delivery document will not be relevant for picking.
2. If the physical goods receipt quantity doesnt match with quantity, the user will have the
ability to change the delivery document and perform goods receipt.
3. If batch number of goods received physically at the Shipping point doesnt match the batch
number on the Returns sales order, the user will have to request Customer Service to
Modify the original return Order and process the delivery.
4. If the batch number of goods received physically at the Shipping point doesnt contain a
batch number in SAP, the user will have the ability to mention a relevant batch number.
SAP Configuration Considerations / Decisions:
Delivery type (ZLRD) would be used for Return Delivery with Internal number range.
When goods receipt is done for Return Deliveries for Return order type ZLRD, the stock would
be put into Goods returns (Movement type 651)
2010 Zensar Technologies

Page 51 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

52 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

5.13

SUPERSEDES:

BBP_SD_BP13: Invoice Processing

Process Description: As Is
As per Dispatch Advice issued from marketing, Finished Goods are dispatched to the respective
customer. On receipt of the Dispatch Advice, the logistics department generates Delivery
Challan cum invoice. An entry is made in the excise as per the Delivery cum Invoice Challan
accordingly (PLA or under bond) account receivable by debiting customer and crediting sale of
goods.
Process Description:
This will cover the following scenarios within the billing process. Billing is one of the components
of Order to Cash end to end business process. This process involves
Standard customer invoices
Invoice cancellations
Debit and Credit memos
The standard billing process is the automatic creation of customer invoices using data from
sales orders and delivery processing. Sales activities conclude with billing and the data is
transferred to financial accounting and controlling / profitability analysis.
Standard Customer Invoices
Standard customer invoices are used to bill external customers for the goods they have
received from company. The billing process starts when the deliveries are due for billing, this is,
deliveries with goods issue posted, no billing block and with the billing date due for billing. The
process ends when the invoice is created and the data posted to financial accounting and
profitability analysis.
The standard customer invoices will be created based on the outbound delivery. The reason for
this decision is that a customer can only be invoiced after the goods are issued and only after
the delivery it can be ensured that the correct quantity is billed.
Credit and Debit Memo Invoices
The debit and credit memos are created based on a reference document. The different source
documents are:
2010 Zensar Technologies

Page 52 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

53 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Debit or credit memo request


Return order

Generating Invoices
The different processes to create customer standard invoices, debit and credit memos are:
Processing the billing due list. The billing due list is a work list which lists all the documents
relevant for billing. These are deliveries with goods issue posted, Credit memo request and
debit memo request with no billing block and with the billing date due for billing. The billing
due list can be triggered manually.
Manually selecting a single delivery or sales order (Credit memo request and debit memo
request)
The customer invoices can be processed using the billing due list or process a single delivery to
create the invoice.
Specific requirements during invoice creation
The general practice is to create one invoice per one customer delivery.
We can also combine deliveries into one invoice for deliveries of the same date for a customer
and PO number.
Integration with financial accounting and controlling
Once the billing document is created in the system, the invoices are going to be posted
manually to financial accounting. This is done using automatic account determination. The
following accounts are relevant for standard sales transactions:
External Sales to Customers
In the case of sample orders they are going to be assigned to a cost element, which will require
a cost center. This will happen at the time of good issue.
The account determination is going to have the following access sequence:
Chart of account (one global chart of account)
Sales Organization
Account assignment for customer
Account assignment for material
Account key
In some cases, the system cannot post entries in the billing documents automatically to the
relevant account. If any of the following posting blocks apply, the billing documents are blocked
for release to accounting:
errors in account assignment
2010 Zensar Technologies

Page 53 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

54 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

billing document is incomplete


errors in pricing
Invoice Cancellation
A different billing scenario is the cancellation of invoices. This process starts when a reason for
the cancellation of an invoice occurs and no credit / debit memo can be used to solve the
problem. The process ends when a new, corrected invoice is created and posted to accounting.
A billing document may need to be canceled for several reasons, typical examples to use this
feature are corrections in the account assignment or pricing or the billing date has to be
changed.
After creating a cancellation document, the reference document automatically can be billed
again.
No inventory movements of goods occur when invoices are canceled. If there is a need to
reverse the goods issue, it has to be canceled in the delivery.

SAP Configuration Considerations / Decisions:


Note: No. Ranges for Standard Invoices and Returns invoices and Sample invoices are same
1. The Document types ZF10, ZF11, ZF13 for Domestic invoice will be used.
2. The Document types ZG2D, ZL2D for Domestic Credit Memo, Domestic Debit Memo are
used.
3. The Document type ZS1D for Domestic cancellation of Invoice is used.
4. The Document type ZS2D for Domestic cancellation of Credit Memo is used is used.
5. The Document type ZF5D will be used for Proforma Invoice.
6. The Document type ZF14 will be used for Job work Invoice.
7. The Document type ZF50 will be used for Export Invoice.
8. The manual conditions in Pricing, Freight, Commissions are allowed.
9. Revenue account determination is based on sales organization & account key
combination
10. Logistic Department can look at billing log for any errors or blocked documents.

2010 Zensar Technologies

Page 54 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

55 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

5.14 BBP_SD_BP14: Available to Promise


Process Description: As Is
Stock is verified physically and dispatched. If there is a shortage, a request is moved to
production department and the stock is produced as per the requirement.
Process Description:
Available to Promise
ATP (Available to Promise) is key component of Order to Cash end to end business process.
Availability checking within sales and distribution is the process of confirming the capability of
delivery of goods for the specified delivery date. Availability checking will be performed when
the sales document is created and when quantities or dates are changed. The quantity
requested is checked against the ATP quantity to determine if stock can be delivered by the
requested delivery date. If the product is available, it is allocated to the document and shipping
deadlines are determined. If the goods ordered by the customer are not available on the
requested date, other delivery proposals are offered for selection. This process ends with either
the allocation of stock and MRP request for the item.
As a base design, availability checking will be done against ATP quantities during sales order
entry and delivery creation. At sales order entry the ATP quantity is calculated from the Storage
Location, the planned incoming stock (purchase orders, process orders) and the planned
outgoing stock (sales orders, deliveries, purchase orders and reservations).
At Delivery creation the ATP quantity is calculated from the stock on hand and the planned
outgoing stock (sales orders and deliveries)
Determining which stock types, in Client and out Client movements, to consider in availability
checking is referred to as the scope of check. ATP is time-specific. This type of check is
performed dynamically by each, taking the relevant stock and planned goods movements into
account with replenishment lead time.
Replenishment lead time is the time that is needed to procure or produce the requested
material. Availability is checked up to the end of replenishment lead time. If the material
availability date > current date + replenishment lead time for the item, the item itself can be
confirmed despite insufficient stock being available. The replenishment lead time is maintained
in the material master and will be used in availability checking.
Delivery Scheduling and availability checking are mutually dependent. SAP uses the requested
2010 Zensar Technologies

Page 55 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

56 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

delivery date along with customer location information to determine when goods must be
available (material availability date). Delivery scheduling determines delivery dates based on
several different lead times defined in the system including:

Material availability - This date is calculated by SAP, working backwards from the
customers requested delivery date. It is the date by which sufficient quantities of an item
must be available for picking to begin the delivery process. It accounts for time required to
pick, pack, load and transport the goods.
Loading - The date by which picking and packing must be completed so that goods are
ready for loading and for the delivery to reach the customer on time. Any special packaging
material must also be ready on this date. The date is calculated by SAP using predefined
time estimates influenced by the shipping point, route and loading group.
Goods issue - The date the goods must physically leave the shipping point to reach the
customer in time. On time refers to the date on which the customer requests delivery of the
goods. The date is calculated automatically by SAP based on the requested delivery date,
picking and packing time, loading time and transit time.

Backward scheduling is used to determine the date on which the material must be available
for the customer to receive the goods on time. SAP starts with the requested delivery date and
counts backwards, taking into account the pick, pack, load, and transport of goods. If the
material is available, Client can meet the requested date. SAP uses the longer of the two times
(lead time vs. pick / pack time) in calculating delivery scheduling.
If the material is not available on the availability date, forward scheduling is performed. SAP
attempts to determine a date when the material is available. This date is the new material
availability date. SAP uses the new material availability date as a starting point for carrying out
delivery scheduling again to determine a new delivery date.
1. The material has stock available for the customers requested delivery date. The item will be
confirmed and the ATP quantity will be reduced by the requested quantity. Though there is
currently no available stock, for example, the requested quantity is 10, with a requested delivery
date of 2 weeks from current date. The item could still be confirmed if there is a planned
incoming movement of inventory within the necessary lead time.
2. Partial deliveries are established. A portion of the delivery would be confirmed by the
requested delivery date. The remaining quantity could be assigned a later delivery date (based
on a planned incoming movement of stock), or backorder processing will be carried out. This
would result in two or more schedule lines being created. Customers and/or materials could be
configured to not allow partial deliveries if required.
3. The ATP quantity for the requested material is 0. With replenishment lead time SAP will
perform forward scheduling to determine and confirm a delivery date. Requirements would be
2010 Zensar Technologies

Page 56 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

57 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

passed on to MRP. This would lead to either a production request or a purchase order.
SAP Configuration Considerations / Decisions:
ATP check will be carried out for the following order types: ZO11, ZO13, ZO10,ZO51 and ZO12
ATP check will not be carried out for Returns orders.

5.15 BBP_SD_BP15: Credit Management


Process Description: As Is
At present there is no specific credit control mechanism. They are applying the controls based
on the customer outstanding/ ageing analysis. They would like to monitor on the following basis.
1 By giving the credit limit around 30 % of the last year sale as the limit for current
year
2 They shall increase the same with authorization
3 The control needs to be at goods movement level
4 All the Customers shall be treated as one group
5 Payment terms shall be reviewed at the discretion of the management
Process Description:
Credit management is one of the key components of the Order to Cash end to end business
process. A decentralized credit management structure can be implemented. A credit control area
will be attached to one company code.
The Credit Management process is used to implement a credit policy that effectively minimizes
credit risk & resolves credit holds (documents blocked for credit-related reasons) as quickly as
possible, and expedites sales order processing. Credit management includes the following
features:
1.
2.
3.
4.

Credit Evaluation
Credit Set-up/Approval
Perform Credit Check
Release of Sales Documents

Credit Evaluation:

The credit management process starts when a credit check is performed and a new
purchase order is received either through, fax, phone call or mail. This purchase order could
be from an existing customer or a new customer.

2010 Zensar Technologies

Page 57 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

58 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

For customers, a credit evaluation is performed outside of the SAP system, possibly through
financial agencies like banks and insurance companies.

Credit Set-up/Approval:
Once the customer is verified and accepted, a customer record is entered into the SAP system
and is assigned appropriate risk category.

001--Risk category 001

Perform Credit Check:


The credit check is performed in the Sales Order Processing at the time of Order Entry. The risk
category, credit control area, and the sales document type determine the behavior of the
customer through the order to cash business process.
For the combinations of credit control area, risk category, and document credit group, any
of the following credit checks can be defined:
1. Dynamic Credit Limit Check with Credit Horizon

Dynamic Check includes the open order value, open items, open billing and delivery
values
The open order value includes undelivered or partially delivered orders. The value is
calculated on the shipping date and stored according to a time period that is
specified in days, weeks, or months.
A credit horizon should be specified. The system will ignore all open orders that are
due for delivery after the horizon date.
The dynamic parts of the check may not exceed the credit limit.
The periodicity of the credit horizon will be measured in months.

2. Changes Made to Critical Fields


The credit check is triggered by changes made in the document to values of any of the creditsensitive fields.
The checks can be carried out at various times during the sales order cycle, from order receipt
to delivery. At Client, credit check will be performed at sales order rather than the time of
delivery. For each checking rule, the system can react with an error or a warning. In the case of
a warning, the system automatically enters a credit status in the document and then saves it.
The status text describes the result of the credit check. A message tells the user if the document
was blocked because the customer's credit limit was exceeded.
These could be Sales order blocking requirements
Sales orders will be blocked for delivery for customers. Warning message will be
2010 Zensar Technologies

Page 58 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

59 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

displayed at the time of saving sales order. Schedule lines will not be confirmed in sales
order and material requirements will not be passed.
Release of Sales Documents:
As these parameters are applied, some of the sales order documents can be blocked for
subsequent actions due to a failure of credit-check. Credit Representative will have to run
blocked orders report twice or three times a day .These documents are then reviewed by the
Credit Representative and either approved or rejected. If the documents are approved, the
credit block is removed by the Credit Manager, and the documents continue through the Order
to Cash Business process. All the unapproved documents are subjected to further review of the
credit department.
SAP Configuration Considerations / Decisions:

Credit control Areas 1000,3000 are created for Arch & Avon respectively

Credit Groups: 01 - Credit Group for Sales Order 02 - Credit Group for Delivery 03Credit Group for Goods Issue are maintained.

Automatic credit check functionality will be used

Only one risk category (001) is maintained for the customers for the purpose of setting
Credit Limits and Credit Control.

An authority is assigned to release all blocked sales orders.

Required payment terms with interest calculation shall be mapped

5.16

BBP_SD_BP16: Batch determination

Process Description: As Is
At present manual batch determination has been done as per physical stock availability. The
batches shall be changed at the time of GRN at delivery point (Depots) as per the receipt of
goods.
Process Description:
The Batch determination process is one of the key components of the Order to Cash end to end
business process.
Batch determination during Delivery processing:
Manual batch determination for exports & automatic batch determination for domestic will be
performed during Delivery processing. Batches will be selected based on FEFO (first expire first
out) criteria. A sort rule will be set up based on FEFO. Material specific batch requirements for
2010 Zensar Technologies

Page 59 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

60 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

expiration days and number of batch splits allowed will be maintained in batch search condition
records.
Batch determination in Sales orders:
Manual batch determination can be allowed during Sales order entry with same requirements as
above. Selecting batches during order entry will be more of an exception than rule.
SAP Configuration Considerations / Decisions:
FOLLOWING KEY COMBINATIONS WILL BE USED TO SET-UP BATCH SEARCH
CONDITIONS IN SAP:
5.17

Sort rule FEFO First Expiry First Out will be used for the Process.
Customer /Material
Material

BBP_SD_BP17: Excise Invoice /ARE Documents Processing

Process Description: As Is
The standard excise norms are followed, ARE1 creation during Deemed Export process
Process Description:
This will cover the following scenarios related to Excise statutory requirements process. This
process involves:
Creating Excise Invoice with Proforma invoice/Billing reference
Excise Invoice cancellations
Creation of ARE Documents according to the kind of sales done against BOND or claim
against CENVAT. The standard Excise Invoice process is the creation of Excise invoices
using data from with Proforma invoice/Billing reference. Excise activities conclude with the
preparation of ARE documents.
Standard Excise Invoices:
Business document that is prepared when we issue excisable goods from a manufacturing
plant. The excise invoice lists the goods that you have issued and states how much excise duty
applies. Client uses the excise invoice to claim back the excise that has been paid from the
excise authorities against BOND. Excise invoice is due to creation when the goods are moving
2010 Zensar Technologies

Page 60 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

61 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

out of the Manufacturing Plant.The process ends when the invoice is created, posted to financial
accounting subsequently ARE Document is created and the relevant entries are made in the
BOND register. The Excise Invoice is created with the billing document as the reference
document. The different source documents are:

Proforma invoice
Billing reference

Generating Excise Invoices:


When Client sends the goods to the customer, they enclose the commercial invoice; they create
the excise invoice with reference to the commercial invoice. If Client wants to send the
commercial invoice after they have dispatched the goods, however, they can create the excise
invoice with reference to a pro forma or commercial invoice.
Excise invoice will be generated with reference to Proforma or Commercial Invoice.
Selection of Excise invoice type as LOT, BOND or No BOND in case of Exports. Customer
submitted form need to be created as BOND in case of Deemed exports with ARE1. ARE1
cannot be saved without attaching license type. If selected as Deemed then system will allow to
create ARE3 instead of ARE1 where attachment of CT1/CT3 form is mandatory while creation of
ARE3 document with reference to Excise invoice.
Integration with financial accounting and controlling
Once the Excise Invoice is created in the system, the invoices are going to be posted
automatically to financial accounting. The following accounts are relevant for standard sales
transactions:
Excise payable accounts will be updated
In the case of Export sales the Excise duties are not levied on to the Export Customers but the
Client has to submit ARE documents for the same to the Excise Authorities to avoid the excise
duty payment.
Sample orders will also attract Excise duties but Sales taxes will not be Applicable.
Excise Invoice Cancellation
The Excise Invoice can be cancelled by giving the reference document number by which it is
created. It reverses any excise duty accounted for.
SAP Configuration Considerations / Decisions:
Excise Invoice is a legal document will be created online and to be submitted to the Excise
Authorities periodically. The excise invoice should be printed
2010 Zensar Technologies

Page 61 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

62 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Prerequisites for creating excise invoice are


Post Goods Issue must be completed for the delivery
Proforma invoice needs to be created for creating Excise invoice for stock transfer.
In case of customer order, the excise invoice shall be created with reference to commercial
invoice.
In case of Depot transfer to excise Depot, the standard Excise procedure is followed

In Arch Pharmalabs Organization the following are excisable plants.


The excise group and series group details are given below.
Excise
Group
10
11
12
13

Plant
1100
1101
1102
1103

15
16
17
23
25
26
27
29
30
31
32
33
34
36
38
42

1105
1106
1107
1172
1201
1202
1203
1271
1272
1301
1371
1372
1471
3101
3201
3401

Description
1100 MFG PLANT EXCISE GROUP
1101 - APL TARAPUR T86
1102 - APL BADLAPUR
1103 - APL TALOJA G-6 UNIT
1105 - APL TARAPUR, PLOT E64 E80, E81 &
E82
1106 - APL DOMBIVALI UNIT
1107 - APL TURBHE R&D UNIT
1172 - APL BHIWANDI (DEPOT)
1201 - APL MERVEN UNIT
1202 - APL SIDDIPET UNIT
1203 - APL SIBRA UNIT
1271 - APL HYDERABAD WH (DEPOT)
1272 - APL SIBRA WH (DEPOT)
1301 - APL VITALIFE LABORATORIES
1371 - APL VITALIFE GODOWN1 (DEPOT)
1372 - APL VITALIFE GODOWN2 (DEPOT)
1471 - APL VADODARA GODOWN (DEPOT)
3101 - AOL SOLAPUR UNIT
3201 - AOL SADASIVPET UNIT
3401 - AOL VADODARA UNIT

Series Group
100
105
110
2010 Zensar Technologies

Mfg/Depot
Mfg
Mfg
Mfg
Mfg
Mfg
Mfg
Mfg
Depot
Mfg
Mfg
Mfg
Depot
Depot
Mfg
Depot
Depot
Depot
Mfg
Mfg
Mfg

Plant & Description


1100 MFG PLANT DOMESTIC SERIES GROUP
1100 MFG PLANT EXPORT SERIES GROUP
1101 TARAPUR FACTORY - LOCAL
Page 62 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

63 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Series Group
115
120
125
130
135
150
155
160
165
170
175
230
250
255
260
265
270
275
290
300
310
315
320
330
340
360

Plant & Description


1101 TARAPUR FACTORY - EXPORT
1102 BADLAPUR UNIT - LOCAL
1102 BADLAPUR UNIT - EXPORT
1103 TALOJA G 6 UNIT - LOCAL
1103 TALOJA G 6 UNIT - EXPORT
1105 TARAPUR, PLOT E64 & E82 - LOCAL
1105 TARAPUR, PLOT E64 & E82 - EXPORT
1106 DOMBIVALI UNIT - LOCAL
1106 DOMBIVALI UNIT - EXPORT
1107 TURBHE R & D UNIT - LOCAL
1107 TURBHE R & D UNIT - EXPORT
1172 APL BHIWANDI (DEPOT)
1201 MERVEN UNIT - LOCAL
1201 MERVEN UNIT - EXPORT
1202 SIDDIPET UNIT - LOCAL
1202 SIDDIPET UNIT - EXPORT
1203 SIBRA UNIT - LOCAL
1203 SIBRA UNIT - EXPORT
1271 APL HYDERABAD WH (DEPOT)
1272 APL SIBRA WH (DEPOT)
1301 VITALIFE LABORATORIES - LOCAL
1301 VITALIFE LABORATORIES - EXPORT
1371 APL VITALIFE GODOWN1 (DEPOT)
1372 APL VITALIFE GODOWN2 (DEPOT)
1471 APL VADODARA GODOWN (DEPOT)
3101 SOLAPUR UNIT - LOCAL

365
380
385
420
425

3101 SOLAPUR UNIT - EXPORT


3201 SADASIVPET UNIT - LOCAL
3201 SADASIVPET UNIT - EXPORT
3401 VADODARA UNIT - LOCAL
3401 VADODARA UNIT - EXPORT

5.18

BBP_SD_BP18: Export Order

2010 Zensar Technologies

Page 63 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

64 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

Process Description: As Is
There are two types of exports viz Direct export and Deemed Export.

Direct Export
The customers are indenting the orders directly on the Company for supplying the material. An
Export Order is used to process customer purchase orders for material .The process of creating
an export order begins with the customers request for materials to be sent to them and the
factory manufactures the special stocks as per the customer specifications. The dispatches
shall be planned through Air or sea ports
The invoices are generated based on the customer LC terms and the realization would be
In foreign currency

Deemed Export
The merchant/manufacturer exporters are placing the orders on ARCH/AVON for supplying the
material for export purpose. The goods are dispatched on CT1 bond and Form H for excise duty
as well as Sales tax exempted. The proceeds received shall be in INR.

Process Description:
An export order is used to process customer purchase orders for material that is owned by the
sales organization. The export order will result in normal scheduling of deliveries and, in many
scenarios, is relevant for pricing since customer billing will occur from the delivery of materials
ordered on the export order.
The process of creating a standard export order begins with the customers request for
materials to be sent to them. This purchase order could be via hard copy, phone, e-mail or fax.
Once a customers purchase order is received, the order is manually entered into the SAP R/3
system via the VA01 export order entry transaction. The sales area responsible for processing
the order is entered along with the sold to business partner, customers purchase order number,
material number and ordered quantity. The remaining information on the export order is derived
from master data (e.g., customer, material, customer/material information records, and pricing
conditions) and system configuration for automatic determination (e.g., shipping point). The
process of creating a export order ends when the order is saved and all required fields are
entered (based on incompletion procedure rules). All the required sales Texts need to be
maintained to meet pre shipment and post shipment Export requirements.
2010 Zensar Technologies

Page 64 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

65 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

During the creation of an export order, several processes are performed to ensure the order can
be filled to the customers satisfaction and within the constraints of Arch Pharmalabs policies.
These processes are described below.
1) Customer PO information - PO number field would be a required field for Standard export
order.
Arch Pharmalabs will use INCO terms which would default into Export order from Sold to
customer master data. The value can be changed during order entry by customer service as per
the requirement.

2) Business Partner Determination - Based on the sold-to business partner, the default shipto, bill-to and payer partners are proposed into the order. If multiple ship-tos exist for Sold to,
the default Ship to number ( same as sold to ) can be changed during order entry thru a pop up
screen selection.

3) Batch Determination - In exports the batches are to be determined manually during the
delivery as the business model is Make to stock

4) Scheduling - The system determines the shipping point based on the delivering plant and
calculates the schedules required deliver the order. Order will capture the Requested delivery
date even after the system proposes different availability dates based on availability of
Inventory. Requested delivery date can be entered at line item level.
5) Availability Check As the scenario in exports is Make to stock the system checks the
relevant in house production time and the replenishment lead time and proposes the delivery
date.

6) Pricing - Customer pricing is carried out manually for exports sales order.

7) Samples - The sales order would have the facility to determine samples and these would not
be relevant for billing. Customer Service has to enter this during the sales order entry.

8) Output- The order confirmation/Proforma Invoice output can be obtained from the Sales
order for exports.

2010 Zensar Technologies

Page 65 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

66 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

SUPERSEDES:

SAP Configuration Considerations / Decisions:


A separate document type for export inquiry has been given.
A separate quotation for export is created and made reference to export order
An export order shall be based on the final agreed price with customer purchase order.

Document type ZINE, ZQTE, and ZO51 will be used with internal number range for
Manual Orders being entered by Logistics Department.
Material, order quantity, plant, shipping point, material price, gross weight, and net
weight will be required fields at item level.

Sold to party, Payer, Bill to, Ship to, for Client will be required partners on export order.

The standard excise process for removal of goods with ARE procedure has been
mapped.

The required license type as well as Bond shall be used for excise transaction
The separate series groups are maintained for ARCH and AVON for exports.

The export obligations and other export benefits are met with ABAP development.

2010 Zensar Technologies

Page 66 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

67 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 67 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

68 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 68 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

69 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 69 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

70 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 70 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

71 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 71 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

72 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 72 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

73 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 73 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

74 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 74 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

75 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 75 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

76 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 76 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

77 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 77 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

78 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 78 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

79 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 79 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

80 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 80 of 101

Business Blue Print


DOCUMENT NUMBER:BBP_SD_V 1.0

PAGE:

81 of 101

TITLE: Sales & Distribution (SD)


ADDENDUM/AMENDMENT #: New Document

2010 Zensar Technologies

SUPERSEDES:

Page 81 of 101

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 82 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

Reports & Scripts Requirements

6.1

REPORT REQUIREMENTS
URS/SD/001 (Domestic Sales Process)
Report Number
Report Name
URS/SD/001/REP-001
URS/SD/001/REP-002
URS/SD/001/REP-003
URS/SD/001/REP-004
URS/SD/001/REP-005
URS/SD/001/REP-006

URS/SD/001/REP-007

URS/SD/001/REP-008
URS/SD/001/REP-009
URS/SD/001/REP-010

Pending Orders (SP wise,


Customer wise, Total)
Consolidated pending orders
(Product-wise, Plant-wise
Shipment details Report with
transporter and LR #
OTIF Report (Orders v/s
shipment info, on-time delivery
%)
Pending Orders v/s stocks
available
Sales transaction summery
report; from PO to AWB
(Includes PO # & date, SO # &
date, Inv # and date,
Documents couriered date &
courier details)
Statutory forms Reports for
following:
C-Form, H-form, F-form, E1E2 sales, I Form, All forms
pertaining to deemed exports
It should give info on Total
Forms Ledger, To be recover
date, Forms received, Forms
pending.
Forms courier to plant reports
(to avoid docs misplacement)
SP wise Report of pending
Forms
Sales Report with period
range and following filter

Reporting
Process Area
S.Org/D.Ch/Div

Reporting
Categories/Data
I/O
Standard

S.Org/D.Ch/Div

Standard

S.Org/D.Ch/Div

Development

S.Org/D.Ch/Div

Development
Development
Development

Development

Development
Development
Development

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 83 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

URS/SD/001/REP-011
URS/SD/001/REP-012

URS/SD/001/REP-013

URS/SD/001/REP-014

SUPERSEDES:
options
Product-wise, Customerwise, country-wise, agent wise
Sales Report
Division wise report (API/
Intermediate/ CRAMS)
- Therapeutic category wise
sale report
- Sales concern wise
Sales report below some
price range (criteria / filter
option)
- Sales report for shipments
under Adv License and Third
party export
(POE)
- Report Based upon sales
type (e.g. Deemed, 3rd party
etc)
- Total Sales v/s Pay terms
wise value break up
Freight Report (SO No.,
Invoice No., Cost Incurred and
Payment done)
Report consisting to recover,
status, reminder, returnable
material due date, time-line
before which we send material
for
repairing
/modification/servicing
For require excise statutory
report will be generated
separately on Local Sales,
Cleared Inputs as such Export
Sales i.e dispatch Quantity,
Assessable Value, Excise Duty
(Basic + AED + ED Cess + S&
H Ed. Cess & Vat) as well as
purchase return report. It
should be matching with ER-1,
return/ER-4
Local
Sales
/
Export
Sales/Cleared Inputs as such

Development
To verify

Development
ER-4 Not possible

To verify

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 84 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

Purchase
Return
(Monthly/Yearly)
Reports (URS/SD/002/REP-001 (Export Order Execution Process)
Report Number
Report Name
Reporting
Process Area
URS/SD/002/REP-001

URS/SD/002/REP-002
URS/SD/002/REP-003

URS/SD/002/REP-004

URS/SD/002/REP-005
URS/SD/002/REP-006

URS/SD/002/REP-007

Enquiry - Quotation Order


Invoice Report
(Customer wise, Sales office
/ Location wise, country
wise, sales group, Agent
wise)
Product Group Enquiry v/s
business materialized report
Business Lost report with
reasoning
(Competitor info to feed in if
available with sales person
against whom we gain / lost
biz. For price, lead time,
quality etc. This is to further
create competitors report
for future ref if possible)
Visit reports (Sales Person)
(Alongwith agenda inputs,
list of products & volumes
which customer is currently
using to be filled in to
masters)
Report on Trade fair visitors
to our stand, business
meets, seminars, events
Customer
complaint
monitoring
and
status
tracking
(Quality, Other issues viz.
packing, leakage etc)
Price Trend analysis /
comparison report
(period wise, customer wise,
product wise)

Reporting
Categories/Data
I/O
Development

Development
Not Possible

Not Possible

Not Possible
Development

Development
(Customer sales
price report)

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 85 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:
URS/SD/002/REP-008

URS/SD/002/REP-009

URS/SD/002/REP-010

URS/SD/002/REP-011
URS/SD/002/REP-012
URS/SD/002/REP-013

URS/SD/002/REP-014

URS/SD/002/REP-015

SUPERSEDES:
Sales Report :
Party-Wise, Product-Wise,
Location Wise, Region
wise, state wise
Selling price report (Latest
Price Statement with respect
to Customer and Products
along with Mode of transport.
Pending
Order
Report
including following data:
Sales Order No & date, PO
No. & date, Party Name,
Product, Quantity, Despatch
Date, Quantity Dispatched,
Balance
Quantity
and
schedule
Stock available with batch
wise summery, Mfg & Expiry
date
Planned
production
v/s
achieved output
Sales
Budget
v/s
achievement
for
FY
(product-wise,
customer
wise)
Top 10 customers, products
report
(choice of choosing multiple
products as well as option to
select max range e.g. 10- 25
etc)
Sales Report with period
range and following filter
options
- Product-wise, Customerwise, country-wise, agent
wise Sales Report
- Division wise report (API/
Intermediate/ CRAMS)
- Therapeutic category wise
sale report
- Sales concern wise

Development

Development
(Customer sales
price report)
Development

Standard
meet
PP related
Development

Development

Development

can

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 86 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

URS/SD/002/REP-016

URS/SD/002/REP-017
URS/SD/002/REP-018
URS/SD/002/REP-019

URS/SD/002/REP-020
URS/SD/002/REP-021

URS/SD/002/REP-022
URS/SD/002/REP-023

SUPERSEDES:
- Sales report below some
price range (criteria / filter
option)
- Sales report for shipments
under Adv License and Third
party export
(POE)
- Report Based upon sales
type (e.g. Deemed, 3rd party
etc)
- Total Sales v/s Pay terms
wise value break up
Market Potential v/s Market
Share Report ( Product wise,
Segment wise & Therapeutic
Category
Freight Report (SO No.,
Invoice No., Cost Incurred
and Payment status)
Payment Collection Reports
for domestic and exports
Receivables reports with
following filters
Country wise, customer
wise, territory wise
- Overdue
Total o/s v/s specific
customer o/s, %
O/s only against sale
incurred by agents
Credit Control Report on pay
terms & value limits (in FC /
INR)
Sales Agent commission
payable report (Due, Paid,
O/s) with customer payment
status
(if
received
or
outstanding)
Commission payable for
customer
payments
not
received
Blocked agent report with
reasons

Not Possible

Development
Standard
Development

Standard
meet

can

Development

Development
Development-MM

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 87 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:
URS/SD/002/REP-024
URS/SD/002/REP-025
URS/SD/002/REP-026
URS/SD/002/REP-027

URS/SD/002/REP-028
URS/SD/002/REP-029

URS/SD/002/REP-030
URS/SD/002/REP-031

URS/SD/002/REP-032
URS/SD/002/REP-033
URS/SD/002/REP-034
URS/SD/002/REP-035

SUPERSEDES:
Sales Agent Agreement
report (start & end period,
products, territory, %)
Pop-up / reminder feature for
contract renewal in advance
(1 / 2 / 3 Mths)
Debit notes and credit notes
report
Pending proof of Exports for
all Merchant Export Orders/
Trading
Export
Orders
(BRC, Disclaimer certificate,
H form, I Form,
Open part DMF given to
customer Report
Report on CDA, sales
agreement (Includes start
end date, allowing to select
pop-up
reminders 1-3
months in advance from the
date of agreement expiry)

Not Possible
MM to check

Trading PO issued and


shipment status report
Customer PO v/s Trading
PO sales price report (To
know trading profit incl.
license benefit )
Customer payment received
v/s vendor payment status
report
vendor business summery
report
Product-wise various vendor
comparison report
Customer & Agent Master to
update with following.
(Name, locations, customer
contact person & details,
various locations, DL #,
payment terms, credit limits,
business direct / thru agent
(agent details if applicable)

Development

MM to check
Standard
Development

Development
To check

Development

Development
Development-MM
Development-MM
Standard
meet

can

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 88 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

URS/SD/002/REP-036

Pending
ARE-1
status
against Rebate / LUT - 1
URS/SD/003/REP-001 (CRAMS)
Report Number
Report Name
Reporting
Process Area

Standard

URS/SD/003/REP-001

Reporting
Categories/Data
I/O
Development

URS/SD/003/REP-002

Business status report


(Inception to Execution with
remarks if business not
materialized)
Sales Report

URS/ SD/004/REP-001 (Job-work In)


Report Number
Report Name
URS/ SD/004/REP-001

Development
Reporting
Process Area

List of POs placed Material


wise / Site wise.
URS/ SD/004/REP-002
Status of FG to be sent to
resp. customer.
URS/ SD/004/REP-003
Stock of inventory customer
wise / job order wise.
URS/SD/004/REP-004
Register of Annexure IV & V
(as per challan wise report)
URS/SD/004/REP-005
Require following Job Work
Challan format in SAP
-Challan of movement of
Inputs/Partially/processed
Inputs/Capital Goods under
cenvat rules 4 (5) a
-Subsidiary challan format
(Job Work Out)
URS/SD/005 (Sample Execution Customer sample Request)
Report Number
Report Name
Reporting
Process Area
URS/SD/000/REP-001

URS/SD/000/REP-002

Sample Summery report


including following:
SO # & date, EI # & date,
product,
qty, customer,
country, value, approval
status, 1st order reference
Rejected sample report with

Reporting
Categories/Data
I/O
Standard
Standard (stock
Availability)
Standard (stock
Availability)
Development-MM
Development
MM &SD

Reporting
Categories/Data
I/O
Development

Development

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 89 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

reasoning and action taken


Sample issued v/s business
materialized (%)
URS/SD/006 Filing of Export and Import License with DGFT (EXIM)
Report Number
Report Name
Reporting
Process Area
URS/SD/000/REP-003

Development

URS/SD/006/REP-001

Duty saved

Reporting
Categories/Data
I/O
Development-MM

URS/SD/006/REP-002

Export Made

Development

URS/SD/007 Clearing and forwarding procedure for Export (EXIM)


Report Number
Report Name
Reporting
Process Area
URS/SD/007/REP-001

Export Register

Reporting
Categories/Data
I/O
Development

URS/SD/007/REP-002

DEPB Register

Development

Advance License Register


Freight Register
Clearing cost report
(Includes C&F expense,
Transport
cost,
CFS
movement
charges,
Loading
&
unloading
charges,
URS/SD/000/REP-006
ADVANCE
LICENCE
STATUS
URS/SD/008 Sales Return (Rejection) process
Report Number
Report Name
Reporting
Process Area

Development
Development
Development

URS/SD/007/REP-003
URS/SD/007/REP-004
URS/SD/007/REP-005

URS/SD/008/REP-001
URS/SD/008/REP-002

Sales v/s Sales Return


report with reasoning
Sales return report with
following options:
Customer wise, Agent
wise, Product-wise, Plantwise,

Development
Reporting
Categories/Data
I/O
Development
Development

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 90 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

URS/SD/010 Logistics for Re-Export of Rejected Import Material (EXIM)

Report Number

Report Name

URS/SD/010/REP-001
URS/SD/010/REP-002

Import and re-export report


License utilization at the
time of Import
Total Import cost

URS/SD/010/REP-003

6.2

SCRIPS REQUIREMENTS: SC_SD_01

4.Outputs:
Sr. No.

Output Name

URS/SD/01/OUT-001

Quotation / Offer

URS/SD/01/OUT-002

Proforma Invoice

URS/SD/01/OUT-003

Sales Order

URS/SD/01/OUT-004

Tax Invoice

Sr. No.

Output Name

URS/SD/002/OUT-001

Quotation / Offer

URS/SD/002/OUT-002

Proforma Invoice

URS/SD/002/OUT-003

Sales Order

Reporting
Process Area

Reporting
Categories/Data
I/O
Development
Development
Development
MM

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 91 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

URS/SD/002/OUT-004

Pre-Shipment Documents

URS/SD/002/OUT-005

Post-Shipment Documents

URS/SD/002/OUT-006

BRC

Sr. No.

Output Name

URS/SD/008/OUT-001
URS/SD/008/OUT-002

Purchase Order Sales Return


Blank

URS/SD/008/OUT-003

Blank

Sr. No.

Outputs.

URS/SD/000/OUT-001
URS/SD/000/OUT-002
Sr. No.

Sales Order
Sample Documentation
Output Name

URS/SD/003/OUT-001

Advance Invoice

URS/SD/003/OUT-002

Sales Order

URS/SD/003/OUT-003

Pre-Shipment Documents

Sr. No.

Output Name

URS/SD/007/OUT-001
Sr. No.

Shipping Bill
Output Name

URS/SD/004/OUT-001

Purchase Order SCPO & JOPO

7.

Functional Requirements

Functional Design requirements:


URS/SD/001 (Domestic Sales Process)
Functional
Requirement No.
URS/SD/001/REQ-001
URS/SD/001/REQ-002
URS/SD/001/REQ-003

Requirement
For all statutory Forms, Report will be
generated on Customer Address and
not on the Consignee Address.
If form reminder mailer to HODs and
sales concern possible
Provision for entering ARE-1 receipt in

Config
Custom
Manual

/
/ Req. Priority
M
N
M

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 92 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

URS/SD/001/REQ-004

URS/SD/001/REQ-005
URS/SD/001/REQ-006

URS/SD/001/REQ-007

SUPERSEDES:
system
(which is obtained from excise dept respective plant. Based on this ARE-1
which we send to customer , POE will
be received)
Payment Receipt / Cheque collection
receipt to be generated thru system
(which is in excel format currently,
creates huge papers). It should have 2
or 3-stages entry such as:
Payment entered by, Checked by,
Authorized by.
VAT Tin No. & CST Tin No. should
appear on the Tax Invoice with
respective various Sites.
The
Declaration
under
the
Maharashtra Sales Tax should appear
on the Tax Invoices issued from
Locations in Maharashtra.
Returnable Gate Pass required in
SAP

M
M

To
verif
requirement

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 93 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

URS/SD/002 (Export Order Execution Process)


Sr.No.
Requirements
URS/SD/002/REQ-001
Sales Order modification rights are
required. Also SO print should be on
one page in vertical form.

URS/SD/002/REQ-002

Agent name and commission to be


captured in the Sales Order

URS/SD/002/REQ-003

FOB Calculation is required

URS/SD/002/REQ-004

Drug Mfg. Lic. No. should appear in


Pre-Shipment Invoices with respect to
various sites and should appear only
on selection of the same.

URS/SD/002/REQ-005

Drug Storage and Sales License No.


should
appear
in
Pre-Shipment
Invoices raised from Maharashtra.

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 94 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

URS/SD/002/REQ-006

List of exempted Raw-Materials should


appear one below the other. (Max. limit
of the list should be 10 Raw Materials)

To verify the
requirement

URS/SD/002/REQ-007

Print Out of Post-Shipment Invoice


must be in One Page

URS/SD/002/REQ-008

Print Out of Post-Shipment Packing


List :- Summary + Detailed

URS/SD/002/REQ-009

BRC should capture max details from


Post-Shipment Invoice

URS/SD/002/REQ-010

System to have FOB Calculation and


should be flexible.

URS/SD/002/REQ-011

When Pre-Shipment Invoice is created


under Advance License, then the said
Invoice number & quantity should be
updated in Advance License Register

URS/SD/002/REQ-012

Following to appear in post-shipment


document but not on print out:

Shipping Bill No. & Date, Airway Bill


No. & Date, Bank Name, Insurance in
Rs. Freight in Rs. & USD, FOB in USD
and FOB in Rs.
However the same should be captured
in the MIS & BRC
URS/SD/002/REQ-013

Inward Freight (approx.) has to be


taken into consideration while creating
the Local and Exports Sales Order

URS/SD/002/REQ-014

Overseas Freight charges & Other


Expenses must be captured MIS.
However we receive freight forwarders
invoice bet 15 30 days from the date
of shipment (delays due to late receipt
of BL)

URS/SD/002/REQ-015

Payment

M-FI

Due

reminders

through

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 95 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:
system

URS/SD/002/REQ-016

Print Out of ARE-1 must be in legal


paper.

URS/ SD/ 004 (Job-work In)


Sr. No.
Requirements
URS/SD/004/REQ-001
Reference of SCPO in JOPO.
URS/SD/004/REQ-002
In case of FG, the yield of material is
more than the qty. mentioned in PO. It
is very difficult in ERP to receive this
Extra yield. Provision to receive extra
yield in SAP required.
URS/SD/004/REQ-003
Material is received for Job Work from
A party and the same material is sent
to the parent factory for job work.
(Provision Required)
URS/SD/006 Filing of Export and Import License with DGFT (EXIM)

M
M-PP
verify

Sr.No.
URS/SD/006/REQ-001
URS/SD/006/REQ-002
URS/SD/006/REQ-003

Requirements
Export Register
Import register
License Status expiry

M
M-MM
M

URS/SD/006/REQ-004

Duty saved Register

M-MM

URS/SD/007 Clearing and forwarding procedure for Export (EXIM)


Sr.No.
Requirements
URS/SD/007/REQ-001
POP UP FOR EXCESS QTY
UTILISED AGAINST EXPORT &
IMPORT LICENCE
URS/SD/007/REQ-002
C&F Expenses, Transport Cost ,Freight
Charges,
Container
Movement
Charges
,Loading
&
Unloading
Charges
URS/SD/008 Sales Return (Rejection) process
Sr.No.
URS/SD/008/REQ-001

Requirements
System should have linkage between
sales invoice and the sales return
(S/R) (goods rejected). This ref should

N
W

to

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 96 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

be also linked with customer


complaint management. The S/R
should reflect in sales report as well.
URS/SD/010 Logistics for Re-Export of Rejected Import Material (EXIM)
URS/SD/010/REQ-001

While preparing the Excise invoice


from plant for re-export of rejected
goods, system should show the details
of the import consignment clearance
documents.
Generation of re-export commercial
invoice which should be linked to
Import document

URS/SD/010/REQ-002

M = this is a critical requirement and the system MUST perform it


W = this is a critical requirement and we can use a WORK-AROUND
N = this requirement is NICE to have
F = this requirement is planned for a future Implementation Wave

8.

Integration Points

Process

FI

CO

Company
Organisation

Chart

Structure

Profit

of

Codes,
Accounts,
Centres,

MM

Plant,
Controlling Area, Cost Elements

Locations,

SD

Storage
Purchase

Organization

Currencies
Sales & Distribution
Dr. Cost of Goods
Post Goods Issue

Sold A/c
Cr. Finished Goods

Controlling Document generates

Inventory A/c
Billing
Creation

Invoice

Dr. Customer A/c


Cr. Sales Revenue

Controlling Document generated

Material Document is
posted

Sales
Distribution
Division

PPQM
Organization,
Channel,

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 97 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

A/c
Cr.

Excise

Duty

collected
Cr. VAT/CST Payable
Return

Delivery

Processing
Dr. Finished Goods
Inventory A/c

Post Goods Receipt

Cr. Cost of Goods

Controlling Document generated

Sold A/c
Return

Invoice

Credit Memo

Dr. Sales Returns A/c


Cr. Customer A/c

Controlling Document generated

Materials Management
Purchase
Documents
Purchase

Purchase

Requisition

Commitments will be updated on

Requisitions

the Account Assignment object


Purchase Order Commitments

Purchase Orders

will be updated on the Account


Assignment object

Inventory Management
Dr.

Raw

Material

Controlling Document generated

Stock A/c

Goods Receipts

Cr. GR / IR Clearing
A/c
Dr. Consumption of

Controlling Document generated

Material A/c

Goods Issue

Cr.

Raw

Material

Stock A/c
Subsequent

Accounting

Adjustments

Document generated
Accounting

Transfer Postings
Cancellation
documents
Physical Inventory

Service Entry

Controlling Document generated

Controlling Document generated

Document generated
of

Accounting

Controlling Document generated

Document generated
Accounting
Document generated

Controlling Document generated

Material Document is
posted

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 98 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

Service Entry Sheets

SUPERSEDES:

Accounting
Document generated

Controlling Document generated

Invoice Verification
Accounting

Invoice

Document generated
Accounting

Subsequent Credit

Document generated
Accounting

Subsequent Debit

Document generated
Accounting

Credit Memo
Cancel

of

Document generated
invoice

documents

Accounting
Document generated

Controlling Document generated

Controlling Document generated

Controlling Document generated

Controlling Document generated

Controlling Document generated

Production Planning
Goods issue against

Accounting

Process Order

Document generated

Confirmation

of

Receipt

against

Process

Order
Process
Settlement

9.

Order

Material Document is
posted

Controlling Document generated

Process Order
Goods

Controlling Document generated

Accounting
Document generated
Accounting
Document generated

Controlling Document generated

Controlling Document generated

Material Document is
posted
Material Document is
posted

Authorization Consideration

Authorizations as per the Archit SD authorization Role matrix

10. Master data Considerations


No

Master
data

Considerations

Remarks

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 99 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

8.01

Material
Master

Sales Views will used to generate the data


relevant to Sales & the Sales Text will be
used to generate required outputs during
sales order,COA and Invoice printing .

8.02

Customer
master

8.03

Tax
Master

The address fields in the general area data


would be used to capture the address of the
Customer in case of Domestic Customers
and the CIN tab would be used to capture
the CST & LST/ TIN numbers. The country &
region of the customer for both Exports &
Domestic would be captured so the details
can be used in generating reports.
The tax master would be maintained for the
following combination
Country/Plant
region/customer
region/
customer tax classification/material tax
classification.

8.04

Batch
Master

11.

Validation/Enhancements Considerations

The batch search strategy would be


maintained for the combination of plant/
material only so that repeated maintenance
of the same data can be avoided.

Alternate units of
Old material numbers
field has been used for
easy search option at
transaction level.
The
Sales
statistics
group, Sales Office &
Sales Group would be
captured in the Sales
Area data to capture the
sales details. These
fields made mandatory
for MIS information.
System considers taxes
based on the consignee
if different then the sold
to party for the tax
calculation.
The FEFO logic has
been used for batch
strategy. As per the
requirement batches can
be changed manually.

Exploding Job work order material RM BOM in Additional data B tab


with quantities required to manufacture Job work Material.

System should not allow goods reversal if proceeding documents


(Commercial Invoice/ Pre shipment) are created for that delivery.

System should not allow creating multiple Pro Forma invoices against a
single delivery.

Transport details requirement in Delivery document to update


transporter details.

While creating Depot commercial invoice selling price to be compared


with assessable value of RG23D, in case of excess system should give

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 100 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

error message.

Billing document cancellation should not allow if Excise invoice exist


against billing document.

Excise Invoice cancellation not to be allowed if ARE exist against the


Excise Invoice.

Cancelled Excise invoice print should not trigger.

Excise invoice number should be updated in the reference field of


Accounting Document.

Posting date, billing date and the delivery should of same month if
changes then system should give message.

Tax amount should not be copied to returns order if reference


document date is exceeding 6 months.

Business Blue Print


DOCUMENT NUMBER: BBP_PP-PI_V.0

PAGE:
101

Page 101 of

TITLE: Production Planning for Process Industries (PP-PI)


ADDENDUM/AMENDMENT #:

SUPERSEDES:

History of Change

16.09.2010

Version
Number
V 1.0

Section

Reason for Revision

All

Initial Document

Vous aimerez peut-être aussi