Sap SD Notes

SAP
SYSTEM APPLICATION IN DATA PROCESSING
Mr. venkat
S.D
SALES AND DISTRIBUTION
1
S AP
SYSTEM APPLICATION IN DATA PROCESSING
SD – SALES AND DISTRIBUTION
ABAP BASIS FUNCTIONAL
SD – HCM – FI – MM – PP – QM – ABAP
‘BASIS’ – (S D) - SALES AND DISTRIBUTION

SAP - R/3 it’s mean Real 3-tier Architecture.
1) PRESENTATION LAYER
2) APPLICATION LAYER
3) DATABASE LAYER
GUI : - GRAPHICAL USER INTERFASE
NDPs : - NEW DIMENTION PRODUCTS
CRM : - CUSTOMER RELATIONSHIP MANAGEMENT
SRM : - SUPLIER RELATIONSHIP MANAGEMENT
SCM : - SUPLIER CHAIN MANAGEMENT
SEM : - STSTEGIC ENTERPRISE MANAGEMENT
APO : - ADVANCED PLANING OPTIMINING
BW/BI : - BUSSINES WAREHOUSE / BUSSINESS INTELEGENCE
BO : - BUSSINESS OBJECT
MDM : - MASTER DATA BASE MANAGEMENT
XI : - EXCHANGE INFRASTRUCTURE (INTER FASE TOOL)
EP : - ENTERPRISE PORTAL
WAS : - WEB APPLICATION SERVER (WEB ENABLED)
2
NET VEIWER COMPINENTS
ESS : - EMPLOYEE SERVICE SYSTEM
MSS : - MANAGER SERVICE SYSTEM
INDUSTRY SOLUTION (I S)
IS-PRODUCTS, IS-RETAIL, IS-OIL, IS-UTILITY, IS-MEDIA,
ECC : - ENTERPRISE CONTROL COMPONENT
(ECC6.0, ECC5.0, ECC4.7)
AS – IS STUDY
ENTERPRISE STRUCTURE: - Under the enterprise structure we have to maintain

the following organization elements.
1. COMPANY CODE: - It is the legal entity which is responsible for all the
business tractions taking place in the company.
2. SALES ORGANIZATION: - It is the responsible organizational element
which takes care of all the sales transactions in the company code. It is
always recommended practice to have minimum number of sale
organization.
3. DISTRIBUTION CHANNEL; - Specific the channel through which goods
are sold to the consumers for example whole sale, Retail, Direct sales, ETC.
4. DIVISION: - The range of products for which the company is carrying out
sales is divided in to deferent divisions the division is nothing but the
product line of the company which is the categorizations of materials is
depending on their purpose and users.
5. SALES AREA: - It is the combination of sales organization distribution
channels division. The sales area always represents the basic sale process off
the company and all the sales transactions will be executed with in a sales
area.
6. SALES LINE: - Its combination of sales organization and distribution
channel.
7. SALES OFFICE: - It is the geographical aspect of the structure of the
company.
8. SALES GROUP : - The employees working for a sales office will be divided
in to sales group
3
RELATION BETWEEN THE ORGANIZATIONAL ELEMENTS
1).Relation between company codes can have much sales organization for carrying
out sales. But one sales organization can work for one company code. So the
relation between company code and sales organization is (ONE TO MANY)
RANBAXY
DIVISION SALES ORGANIZATION – ONE TO ONE
ONE
TO EXPORT SALES ORGANIZATION_
MANY
(One too many)
(One too one)
(One too many)
2). Relation between sales organization and distribution channel one

Sales organization can have many distribution channel can be used
For many sales organization and distribution channel is (MANY TO MANY)
RANBAXY
D.S.O E.S.O
(ONE TOO MANY) __ WHOLE SALES __ WHOLE SALES
(MANY TOO ONE) __ RETAIL SALES (MANY TO ONE)
(MANY TOO MANY) __ DIRECT SALES
3). Relation between sales organization and division from one sales organization
we can sell many division one division can be sold from many sales organization
so the relation between sales organization and division is (MANY TO MANY).
RANBAXY
D.S.O E.S.O
__ CARD __ CARD
ONE
TO __ NEURO __ NEURO
MANY
4
4). Relation between distribution channel and division from one distribution
channel we can sell many division can be sold from many distribution channels so
the relation between distribution channel and division is (MANY TO MANY)
WHOLE SALE RETAIL
ONE __ CARD ___ CARD

TO
MANY __ NEURO MANY TOO ONE
5). Division is always sales organization specific that is it’s the sales Organization
that decides the number of divisions to be sold.
D.S.O (CARDS & NEURO) E.S.O – (CARD)
D.S.O E.S.O
W.H W.H
CARD NEURO
5
S A P built on client server technology
1. EASY ACCESS MENU
2. USER MENU
3. DYNAMIC MENU
4. COSTUMIZING MENU
(I M G)- MEAN’S - IMPLIMENTATION GUIDE
SERVER: s d 1, CLIENT: 811, USER NAME: SAP USER, PASSWORD: India

12345.
DEFINING SALES ORGANIZATION
From easy access menu Select,(/NSMRO)

TOOLS

CUSTOMIGING

I M G (implementation guide)

S P R O executes project

SAP reference IMG

ENTERPRISES STRUCTURE

DEFINATION


DEFINE, COPY, DELETE CHECKS, AND SALES ORGANIZATION.
COPY, DELETE, CHECKS, SALES ORGANIZATION (fi&f4)
(Is our help)
6
Select the icon copy organizational object.
Make a copy from an existing sales organization to required new sales
organization.
CUSTOMIZING REQUEST
1). We need to save the data in customizing request.
2). For creating the new request select the icon create request and Specify short
description
3). To select a request from the list of available select the button own request.
4). After saving the data in the customizing request come back to the
previous screen and go to define sales organization
5). Select the defined sales organization and select the icon details
6). Specify the name of sales organization.
7). Specify the currency.
8). Specify the calendar. (01)
9). If the sales organization is offering rebates for customers, we have

To check the field rebate process active.
10). Select the address icon and specify the require data
11). Save the sales organization.
If we get the error. Data is locked by user, use the transaction code
SM 12 unlocks it.
Go to main menu, Select Delete all
/N – With a session a new screen comes.
/O – Its open a new.
The maximum session that can be similarly be opened is (“6"- sessions).
7
DEFINING DISTRIBUTION CHANNEL
SPRO-DEFINE DELETE DISTRIBUTION CHANNEL COPY, DELETE,

CHECKDISTRIBUTION CHANNEL.

SELECT THE ICON COPY ORGANIZATIONAL OBJECT.

MAKE A COPY FROM AN EXISTING DISTRIBUTION CHANNEL TO
THE REQUIRED

NEW DISTRIBUTION CHANNEL.

COME BACK TO THE PREVIOUS SCREEN AND GO TO DEFINE
DISTRIBUTION CHANNEL.

SELECT THE DEFINED DISTRIBUTION CHANNEL AND SPECIFY
THE REQUIRED NAME AND SAVE IT.
DEFINING DIVISION
SPRO


DEFINATION

LOGISTICS GENERAL

DEFINE COPY DELETE CHECK DIVISION

COPY, DELETE, CHECK DIVISION
Make a copy from existing division to the required new division.
Come back to the previous screen and go to define division.
Select the define division and specified the required name of
8
DEFINING SALES OFFICE
SPRO


DEFINATION


MAINTAIN SALES OFFICE
Go to “NEW ENTRY’S” and create the sales office.

“SELECT THE ADDRESS” icon and specified the required data.
DEFINING COMPANY CODE

SPRO

MAINTAIN SALES OFFICE


DEFINATION, SALES AND DISTRIBUTION

Edit, Copy, Delete, Check, Company code.

Copy, Delete, Check, Company code.

Make copy from an existing company code to the required new Company code.
Come back to the previous screen and go to edit company code data.
Select the define company code and go to details.
Specify the company name and country and currency.
Select the address icon and specify the required data.
9
ASSIGNING SALES ORGANIZATION TO COMPANY CODE
SPRO


ASSIGNMENT


ASSIGN SALES ORGANIZATION TO COMPANY CODE.
IDESAG: International demonstration education system.

Select the sales organization and resigned company code.
ASSIGNING DISTRIBUTION CHANNELS TO SALES ORGANIZATION

SPRO


ASSIGNMENT


ASSIGN DISTRIBUTION CHANNEL TO SALES ORGANIZATION.
Go to “new entries” and specify the required combinations of sales

Organization and distribution channel.
ASSIGNING DIVISIONS TO SALES ORGANIZATIONS

SPRO


ASSIGNMENT


10
ASSIGN DIVISION TO SALES ORGANIZATION.
Go to “new entries” and specify the required combination Sales organization and
Division.
MAINTAINING SALES AREA
SPRO


ASSIGNMENT


SET UP SALES AREA.
Go to “new entries” and specify the required combination of Sales Organization,

Distribution Channel and Division.
ASSIGN SALES OFFICE TO SALES AREA

SPRO


ASSIGNMENT


ASSIGN SALES OFFICE TO SALES AREA
Go to “new entries” and specify the required combinations of sales Organization,
Distribution channel, Division, and sales office.
DEFINING SALES GROUP

SPRO

ENTERPRISE STRUCTURE

DEFINATION


11
MAINTAIN SALES GROUP
Go to “new entries” and create the required sales group.
ASSINING SALES GROUP TO SALES OFFICE

SPRO


ASSIGNMENT


ASSINING SALES GROUP TO SALES OFFICE
Go to “new entries” and specify the required combinations of sales office or sales
group.
DEFINING PLANT
SPRO


DEFINATION

LOGISTICS GENERAL
a).Define  Copy  Delete  Check  Plant.
b).Copy  Delete  Check  Plant.
c).Make a copy from an existing plant to the required new plant
d).Come back to the previous screen and go to define plant.
e).Select the define plant and go to detail’s.
f).Specify the required name and factory calendar.
g).Select the address icon and specify the required data.
12
ASSIGN PLANT TO COMPANY CODE
SPRO


ASSIGNMENT

LOGISTICS GENERAL

ASSIGN PLANT TO COMPANY CODE
Go to “new entries” and specify the required combinations are

Company code and plant
In a standard Business practice one company code can have many plants. Where as
one plant can only work for one company code.
ASSIGNING PLANT TO SALES ORGANIZATION

SPRO


ASSIGN SALES ORGANIZATION AND DISTRIBUTION PLANT.
Go to “new entries” and specify the required combination of sales organization,

Distribution channel and plant.
a).In a standard business practice, to assign a plant to sales

Organization both of them shall belong to some company code.
b).The relation between sales organization and plant is {MANY – MANY}.
c).To sees the entire structure and selects the button structure in that
Screen where we have copied the sales organization and then
13
Select the button navigation.
DESIGN REGION
SPRO

SAP NET VEIWER

GENERAL SETTINGS

SET COUNTRIES

INSERT REGIONS
Go to “new entries” have and create region fir the required for the Country.
MAINTAINING COUNTRY SPECIFIC CHECK
SPRO

SAP NET VEIWER

GENERAL SETTINGS

SET COUNTRIES

SPECIFIC CHECK
MAINTAINED CALENDER
SPRO

SAP NET VIEWER

GENERAL SETTINGS MAINTAIN CALENDER
PUBLIC HOLIDAY’S
Specify the list of public holiday’s are depends on the country.
HOLIDAY CALENDER
14
Specify the number of working days in a week. The calendar is across client
component or client in depend component. That is if we maintain the calendar by
default it will be seen across.
But the other components only are seen in that client in which they are maintain or
called client specific or client dependent components.
MASTER DATA
1) CUSTOMER MASTER DATA
2) MATERIAL MASTER DATA
3) CUSTOMER MARERIAL INFO RECORD
4) CONDITIONS MASTER DATA
CUSTOMER MASTER DATA

We have to maintain the data base of all the customers in the SAP system,
With whom the company is carrying out business transactions for each customer
we have to specify a number and maintain the corresponding details of the
customer for that particular number.
During the sales transactions
If we specify the customer number, the system automatically determines the

corresponding details of the customer from the customer master record.
CREATING THE CUSTOMER

From easy access menu sell at
LOGISTICS


MASTER DATA

BUSINESS PARTNER

15
CUSTOMER CREATE

XDOI – complete.
The customer master record contains three views for which we need to maintain
the data; they are general data, company code data and sales area data. Each view
contains different TAB pages and each TAB page contains for which we need to
maintain the data. We can migrate all the details of the customers from the legacy
system (non SAP system) to SAP system by using (L.S.M.W) & (B.D.C)
L.S.M.W - LEGASY SYSTEM MYGRATION WORK BENCH

B.D.C - BATCH DATA COMMUNICATION
Specify the data for the following views to create the customer.
GENERAL DATA
I). ADDRESS: Specify the required data of the customer on the address
TAB page
II). MARKETING:
CUSTOMER CLASSIFICATION
Specifies a classification of customer which can be based on their sales
Turnovers
Defining customer classification
Go to new ‘entrees’ and create.
III). GOODS RECEIVING HOURS

Specifies the timing in which the good's can be unloaded at the Customer’s
locution.
Define good’s receiving hours
Go to new ’entry’s and create.
IV). TAB PAGE
CONTACT PERSON’S:-
Specify the contact person at the customer’s location creating.
CONTACT PERSONS
LOGISTICS

SALES DISTRIBUTION

MASTER DATA
16

BUSINESS PARTNER

CONTACT PERSON (VAP1) create
COMPANY CODE DATA: -

Under the view account management. Under the TAB
- RECONCILIATION –
This account in the G/L accounting is the accounting which is updated
Parallel to the sub ledger accounting for normal postings
(Re Account-140000)
PAYMENT TRANSACTION’S: -
UNDER TAB PAGE – (TERM’S OF PAYMENT)
Specifies the key for payment term’s composed of payment periods
And cash discount percentages.
DEFINING TERM’S OF PAYMENT
SPRO


MASTERDATA

BUSINESS PARTNER’S

CUSTOMER’S BILLING DOCUMENT (Under entries)
PAYMENT HISTORY RECORD: -

If we check this field, the payment history of the customer we will be recorded and
display by the system in the corresponding credit master data of the customer.
SALES AREA: -
A) SALES: - Sales District
Specify the sales district in which the customer exist defining sales district.
SPRO

SALES DISTRIBUTION

MASTER Data

17

CUSTOMER’S

SALES

DEFINE SALES DISTRICT (New entries)
B) SALES OFFICE: -
Specifies the sales office in which the customer exist.
C) SALES GROUP: -
Specifies the sales group of customer’s which can be based on the kind of
transaction’s they execute with the company.
DEFINING CUSTOMER GROUP
SPRO

SALES DISTRIBUTION

MASTER DATA


CUSTOMER’S

SALES

DEFINE CUSTOMER GROUP’S
CURRENCY: -Specifies the currency of the customer.
NOTE: - If the currency of the customer deer’s from the currency of the company
code, we have to maintain the exchange for the required exchange type by using
the transaction code (OC41) from the currency of the customer to currency of
company code and specify that type in the customer master first field
“EXCHANGE RATE TYPE”
SWITCH OFF ROUNDING: -
If we check we field, the rounding off the order quantities will not be done for the
customer.
CUSTOMER PRICIENG PROCESSER: - Enter in (1)
This field enables the system to automatically determine a corresponding “pricing
processor” for customer’s during the sales document processing.
TAB –II
18
SHIPPING: -
DELIVERY PRIORITY : - (no notes) –HIGH/LOW/MEDIUM etc
SHIPPING CONDITIONS: -
It enables the systems to automatically determine a corresponding
“SHIPPING POINT” for the customer during the sales document processing.
DEFINE SHIPPING CONDITIONS: -

SPRO

LOGISTICS EXECUTION

SHIPPING

BASIC SHIPPING FUNCTIONS
Shipping point and goods receiving point determination define shipping conditions
(new entries)
DELIVERY PLANT: - (C & F) CARRYING AND FORWARD

Specifies the plant from which goods are delivered to the customer
RELAVANT for – (P O D) PROOF OF DELIVERY
If we check the customer becomes relevant from proof of delivery. That is he will
said the acknowledgement the company offer receiving the goods if the customer
relevant for (P O D) we can also specify the “POD TIME FRAME”
ORDER COMBINATION
If we check the field, we can combine multiple orders for a customer to create a
single delivery.
PARTIAL DELIVERY FROM ITEM
Specifies weather the customer request full or partial delivery of the item
MAXIMUM PARTIAL DELIVERY : - (EMPTY)
BILLING DOCUMENTS: -
If we check this field, the customer becomes eligible for receiving the rebates.
INCOTERM”S: - (INTERNATIONAL COMMON TERMS)
CIF: - (COST INSURANCE AND FRIEGHT)
CFR :-( COSTS AND FRIEGHTS)
INCOTERMS: -
19
The incoterm’s specifies curtain internationally recognized terms and conditions
that the shipper and the receiving the party must follow for the shipping transaction
to be successfully completed. The part two of incoterm’s specifies the place from
which goods are delivered to the customer.
DEFINING INCOTERMS: -
SPRO


MASTER DATA

BUSINESS PARTNERS

CUSTOMERS

BILLING DOCUMENT

DEFINE INCOTERM’S.
CPT :- (Freight free)
In the definition of incoterm’s If we check the field location mandatory; it becomes
mandatory to have part (2) of that incoterm’s in the customer master.
ACCOUNT ASSIGNMENT GROUP:-
The field enables the system to post the sales values of customers to the
corresponding G/L accounts during revenue account determination processor.
TAX CLASSIFICATION: -
Specifies weather the customer is liable for tax or not.
PARTNERS FUNCTIONS:-
1. S.P:- SOLD TO PARTY
Specifies the customer placing order with the company.
2. S.H:- SHIP TO PARTY
Specifies the customer receiving the material.
3. B.P:- BILL TO PARTY
Specifies the customer on whom the bill is raised.
20
4. P.Y:- PAYER
Specifies the customer making the payment.
1. The information regarding the partners is always provided by sold to party
record.
2. Depending on the requirement all the partners can be same or they can defer.
3. If all the partners are same, we need to create the customer as sold to party and
specify that customer number for the remaining partner functions.
4. If the partners define, we need to create customer master records for those
partners and specify those customer numbers in the sold to party record for the
respective partner functions
5. If required one sold to party. Can have multiple SH & BP & PY.
CREATING THE CUSTOMER: - (XDO1COMPLETE)
ACCOUNT GROUP: - Specify the weather we are creating is a sold to party or
ship to party or payers.
NOTE: - Account group controls views and fields.
A. CUSTOMER: - specify the customer number.
B. Specify the company code with which customer executive business
transactions.
C. SALES ORGANIZATION: - Specify the sales organization with which the
customer executes the sales transactions.
D. DISTRIBUTION CHANNEL: - Specify the channel through which the
customer executes the sales transactions.
1. DIVISION: - Specify the division for which the customer executes sales
transactions enter the required data for the three views in the customer master and
save the customer.
NOTE: - While creating the customer if we get the error, sales area is not defined
for customers.
SOLUTION
SPRO


DEFINE

COMMON DISTRIBUTION CHANNELS
Select the required combination of sales organization and distribution channel and
specify the sales distribution channel for the fields –DCh-COnds and DCh-
CUst/mt (consistency structure).
21
2. DEFINE COMMON DIVISION: - Select the required combination of the
sales organization and division and specify the same division for the fields “Div
Con” and “Div cus.
3. DEFINING ACCOUNT GROUP:-
SPRO

FINANCIAL ACCOUNTING

RECEIVABLE AND ACCOUNTS PAYABLE CUSTOMERS

MASTER DATA PREPARATION FOR CUSTOMER MASTER DATA

DEFINE ACCOUNT GROUPS WITH SCREEN LAYOUT.
OOO1 - SOLD TO PARTY.

OOO2 - GOODS RECEIPENTS.
OOO3 - PAYER.
OOO4 - BILL TO PARTY.
In the definition of the account group we can control the field’s status. That is
depending on the requirement we can make a field as optional entry or required
entry or in display mode or we can SUPPRESS it also.
SP  ALL THE VIEWS
SH  SALES/SHIPPING/BILLING. (ONLY TAX-CLASS)
PX  SALES/BILLING
BP  SALES
EXISTING IN THE CUSTOMER

XDO1-enter

COMPLETE

ACCOUNT GROUP

CUSTOMER CREATING

SOLD TO PARTY ((or) BILL TO PARTY (or) PAYER
NOTE: - Below To Account Group Views and Fields.
22
CUSTOMER: - Specify the customer number.
COMPANY CODE: - Specify the company code with which the customer
executes business transaction.
SALES ORGANIZATION: - Specify the sales organization with which the
customer executes the sales organization.
DISTRIBUTION CHANNEL: - Specify the channel through which the executive
to sales transaction.
DIVISON: - Specify the division from which the customer executes sale
transaction. Enter (find a/c)
PARTNER FUNCTION: - Enter the required data for the area customer master
and save the customer.
NOTE: - By creating customer if we get the bearer “sales area not defines for
customer.
SOLUTION
SPRO


MASTER DATA
1- DEFINE COMMON DISTRIBUTION CHANNEL:-

Select the reserved combination of sales organization and distribution channel and
specify same distribution channel for the fields (Dch-Cust/m+)
2- DEFINE COMMON DIVISION:-
Select the required combination of sales organization and division and specify
same division for the fields “DIVISION and DIVCUS”.
3- DEFINING ACCOUNT GROUP: -
SPRO


ACCOUNT RECIEVABLE

ACCOUNT PAYABLE

CUSTOMER ACCOUNTS
23

MASTER DATA

PREPARATAIN CREATING CUSTOMER MASTERDATA

DEFINE ACCOUNT GROUP SCREEN LAY OUT.
SOLD TO PARTY – 0001
GOODS RECEIVE – 0002
PAYER – 0003
BILL TO PARTY - 0004
In the definition account group we can control the field specify that is depending
on the requirement we can make a field by optional entry or required entry display
mode or we can suppress also.
SP  All the views, SH  Sale / Shipping / billing, Pay  Sales / Billing – BP –
Bill – Sales
CREATING NUMBER RANGE FOR CUSTOMER
SPRO


ACCOUNTS RECORD & PAYABLE

CUSTOMER ACCOUNTS

MASTER DATA

PREPARATION FOR CREATING CUSTOMER DATA

CREATE NUMBER RANGES FOR CUSTOMER ACCOUNTS.
Select the Button “CHANGE INTERVALS”
To create a new number range. Select the button “INSERT INTERVAL”
For a number range. If we check the “EXETERNAL” it becomes an external
number range. i.e., while creating the customers we have to specify a number for
the customer. If we don’t check this field it becomes an internal number range
where the system automatically process number for customers
NOTE: -To delete a number range the status must be initial after creating the
number range it has to be assigned to the required account group for this go to.
(enter) assign number ranges to customer account group.
24
Select the required account group and assign the number range.
PATNER DETERMINATION PROCEDURE: -
In the order to get the required partner functions in to customer master we have to
define partner determination procedure for this.
SPRO


BASIC FUNCTIONS

PARTNER DETERMINATION

SET UP PARTNER DETERMINATION

SET UP PARTNER DETERMINATION FOR CUSTOMER MASTER
DEFINE PARTNER FUNCTIONS: -
Select Partner function we have to specify a corresponding “PARTNER TYPE”
which control the functionality of that partner for example for a partner function if
the partner type is “KU” it becomes customers and if the partner type is “L I 1” it
becomes under for a partner function. If we check the field “UNIQUE” we can
have only one partner of that function with in a customer master.
NOTE: - SP is always “UNIQUE”.
1. ASSIGNING PARTNER FUNCTIONS TO ACCOUNT GROUP
Select Account Groups, Function Assignment
Go to ‘new entries’ and assigned the required the partner functions to the required
account group.
2. DEFINING PARTNER DETERMINATION PROCESSOR
Select partner determination processor
Go to “new entries” and create processor.
3. PLACING THE PARTNER FUNCTION IN THE PROCESSOR
Select the created processor and go to partner functions in processor.
Go to “new entries” and enter required partner function if we check the field “not
modifiable”. It becomes mandatory to have at least one partner of that function in
the customer master record.
4. ASSIGNING THE PROCESSOR TO ACCOUNT GROUP

Select partner determination processor assignments select the required account
group and assign the processor
25
FIRST DEFINED ACCOUNT GROUP (4 GROUPS OF CUSTOMER)
S-P, B-P, P-Y, S-H
1. DEFINE OUR ACCOUNT GROUP
2. CREATE NUMBER RANGE
3. ASSIGNED NUMBER RANGE TO ACCOUNT GROUP
4. COMPLETE PARTNER DETERMINATION PROCESSOR
5. CREATE CUSTOMER
EXTENDING THE CUSTOMER TO NEW SALES AREAS

Go to “XDO1” create below to the specify the account group specify the customer
for whom the data has to be extended. Specify the new sales area to which the
customer has to be extended.
In the reference section specify the same customer company code and specify that
sales area in which he is already created (say) enter
The entire data will be extended to the new sales area and save the customer even
though. The same data is copied to the new sales area.
If required it can be changed that have been made, “on the sales data view”
are specific to that particular sales area only.
If a customer is created by using the transaction code ‘XDO1’, He can be used in

sales as well as finance where as if the customer is created by using the transaction
code “VDO1” He can only be used in SD.
MATERIAL MASTER DATA: -
LOGISTICS


MASTER DATA

PRODUCTS

26
MATERIAL

OTHER MATERIALS (MMO1- CREATE)
Specify the data for the following fields

1. MATERIAL: - “USE ANY CODE”
2. INDUSTRY SECTOR: - KEEP THIS ONLY (RETAIL)
3. MATERIAL TYPE: - enter only (HAWA Trading good)
Select the button “select views”
Select the following views to maintain the data
1. BASIC DATA – 1
2. SALES SALES ORGANIZATION DATA – 1
3. SALES SALES ORGANIZATION DATA - 2
4. SALES GENERAL AND PLANT DATA
5. SALES TEXTS
6. MRP – 1 (MATERIAL REQUIREMENT PLANNING)
7. ACCOUNTING - 1
Select the button organizational levels
Specify the plant and the storage location in which the material exist and also
specify the sales organization and the distribution channel from which the material
has to be sold.
CREATING STORAGE LOCATION: -

SPRO


MATERIALS MANAGEMENT
27

MAINTAINS STORAGE LOCATION
Specify the data for the following views.
1. BASIC DATA – 1 (1)

Specify the description of the material.
2. BASE UNIT OF MEASURE – Specify the unit of measure in which the stocks
of the material or maintained.
3. DIVISION – Specify the division in which the material exists
4. Specify the required dimensions of the materials
E A N: - INTERNATIONAL ORTICLE NUMBER
U P C: - UNIVERSAL PRODUCT CODE
SALES SALES ORGANIZATION: -

Sales unit: - Specifies the unit of material in which the material is sold
NOTE: - 1. We need to specified a sales unit only if it definers from base unit
2. If the sales unit defers from base unit, we can maintain conversion factors that is
the quantity relation between sales unit and base unit.
DELIVERY PLANT: - Specifies the plant from which the material is delivered to
the customers.
MATERIAL GROUP: - Specifies a grouping of materials that have the same
characteristics or tributes.
DEFINING MATERIAL GROUP: -
CASH DISCOUNT: - If we check this field, the material qualifies for the cash
discount specified in the terms of payment.
MINIMUM ORDER QUANTITY: - Specifies the minimum quantity of the
material that may be order for each cash sales transactions.
NOTE: - The minimum order quantity can only be maintained in base unit of
measure
MINIMUM DELIVERY QUANTITY: - Specifies the minimum quantity of the
material that is to be delivered for each shipping transaction.
ROUNDING PROFILE: - Specifies the rule that the system uses to adjust the
order proposal quantity to the nearest deliverable units
NORM – STANDARD ITEM
BANS – THIRD PARTY ITEM
ERLA (or) LUMF – BILLS OF MATERIALS (BOM).
SALES GENERAL&PLANT: - AVAILABILITY CHECK.
Specifies weather and how the system checks the availability of material in the
sales document.
BATCH MANAGEMENT: - (DE CHECKS IT).
28
Specifies weather the material is maintained in batches.
TRANSPORTATION GROUP: - Specifies a grouping of materials that have the
same transaction requirements.
DEFINING TRANSPORTATION GROUP: - (GO TO SPRO)
LOADING GROUP: - Specifies a grouping of materials that have the same
loading requirements.
DEFINES LOADING GROUP: - (GO TO SPRO)
SALES TEXT: - Here we can specify any information regarding the material that
explain the material in more detail and use full in further processing of the
material.
MRP-1(ND) : - (MATERIAL REQUIREMENT PLANING)
Specifies weather and how the requirement of material is planned.
ACCOUNTING – 1: -
a) VALUATION CLASS: - It enables the system to cost of different material
types to the corresponding GL accounts
b) Depending on the “price control”, we have to specify either moving price or
standard price. (Save the material master)
While creating the material if we get the ‘error’, the company code does not
exist or has not been fully maintained resolve it in the following way.
SOLUTION: - SPRO

LOGISTICS

GENERAL MATERIAL MASTER

BASIC SETTINGS

MAINTAIN COMPANY CODE FOR MATERIALS MANAGEMENT.
Select the required company code and specify the current year and period.
EXETENDING THE ORGANIZATIONAL DATA FOR MATERIAL: -
‘MM01’ Create transaction code
For the field “material” for which the data has to be extended
For the field “copy from material” specify the same material
Select the required views
Select the button “organizational levels”
In the “copy from” fields specify those values in which the material is
Already maintained
29
In the “organizational levels” specify those values to which the material has to be
extended enter.
The material will be extended to the new organizational levels and save it.
To get the “TAX CLASIFICATION” in customer and material master records, go
to “OVK1” go to new entries and assign the tax category “MUST” to the required
country.
QUESTIONS IN CUSTOMER MASTER

1. Assigned four partner functions to account group but place only 3 in the
procedure and create the customer?
Ans: - While creating the customer the system determines only those 3 partner
function that are placed in the procedure that is the partner determination
procedure enables the system to determine the partner functions in to customer
master record.
2. Assigned three partner functions to account group but place all four in the
procedure and create the customer?
Ans: - In the customer master record the system determines all four partner
functions but it picks the customer numbers only for those three partner functions
to account group enables the system to determine the corresponding customer
numbers for the partner function.
3. In the customer master record where the system displays the account group by
which that customer created?
Ans: - In the customer master data from the main menu select EXTRAS 
administrative data.
4. In the customer master where we can see all the changes that have been made?
Ans: - In the customer master from the main menu select environment  Account
charges  All fields (or)
LOGISTICS


MASTER DATA
30

BUSINESS PARTNER

CUSTOMER

DISPLAY CHANGES VD04 (or) XD04.
5. How to change the account group of a customer?
Ans: - LOGISTICS


MASTER DATA

BUSINESS PARTNER

CUSTOMER

XD07 CHANGE ACCOUNT GROUP.
NOTE: -
To change the account group for a customer, the current and new account groups
must have same number range.
CREATING SALES ORDER
LOGISTICS


ORDER

VA01 CREATE (is a transaction code).
Specify the order type “OR”
Specify the sales area in which the order is created – enter

In the over view screen specify the sold to party, ship to party Po no, (purchase
order) material and order quantity.
ERROR NO – 1
The order type OR is not defined for sales area
SOLUTION
31
SPRO


SALES

SALES DOCUMENTS

SALES DOCUMENT HEADER

ASSIGN TO SALES AREA TO SALES DOCUMENT TYPES.
1 COMBINES SALES ORGANIZATIONS: -

Select the required sales organization and assign the same as reference.
2 COMBINE DISTRIBUTION CHANNELS: -
Select the required combination of sales organization and distribution channel and
assign the same distribution channel as reference.
3 COMBINE DIVISIONS: -
Select the required combination of sales organization and division and assign the
same division as reference.
4 ASSIGN SALES ORDER TYPES PERMITTED FOR SALES AREA:
Go to “new entries” and specify the required combinations of sales organization,
distribution channel, division and the document type (OR).
ERROR – 2
No pricing procedure could be determined.
1. SOLUTION: - In the corresponding customer master specify the customer

pricing procedure as 1.
2. SOLUTION: - Go to /n OVKK. Go to new entries and assign the pricing
procedure (RVAA01) to the required combination of sales organization,
distribution channel, division, document pricing procedure (A) and customer
pricing procedure (1) then that error will be solved.
ERROR – 3
For the item number business area can be determined.
SOLUTION
32
SPRO


BASIC FUNCTIONS

ACCOUNT ASSIGNMENT AND COASTING
BUSINESS AREA ACCOUNT ASSIGNMENT
DEFINE NEW RULES BY SALES AREA: -

Select the required sales area and assigned the “rule” for business area
determination,
If the rules “1” we need to assign the business area to the plant and division. For
this go to – entry.
Assign business area to plant and division go to new entries and assign the required
business area to the required plant and division.
If the rule is “2 or 3” we need to assign the business area. For this go to assign
business area by sales area.
ERROR – 4
If we get an error regarding “chart of account” solution, go to “ob62” select the
required company code and assign the chart of accounts “I N T”
(PRE DEFINED ENTRIES)
ERROR -5
Assign physical year variant go to “0B37” select the required company code and
assigned “K4”.
CUSTOMER MATERIAL INFORMATION RECORD

If the customer is placing order for a material by his own code. (Customer material
number) rather the original material code, we need to maintain this record. Where
we have to assign that customer material number to the original material code.
During the sales order processing if we specify the customer material number; the
system automatically determines original material number.
MAINTAINING CUSTOMER MATERIAL INFORMATION RECORD
LOGISTICS

33

MASTER DATA

AGREEMENT

CUSTOMER MATERIAL INFORMATION “VD51” Create.
Specify the customer for whom the record has to be maintained and also specify
the corresponding sales line of the customer (  )
In the over view screen specify the original material code for the field material
number.
Select the record and go to details where we can specify customer description 
plant  minimum delivery quantity etc, (save the record)
NOTE: - In the sales order the customer material number is entered on the view
ordering party.
CONDITIONS MASTER DATA: -

In a business practice the enter pricing is categories in to four elements.
They are
1). BASIC PRICE
2). DISCOUNT CHARGE OR SURCHARGE
3). TAX
4). FRIEGHT
For each pricing element we have corresponding “condition types” in the SAP
system for example.
PR00: - PRICE
K004: - MATERIAL DISCOUNT
K005: - CUSTOMER MATERIAL DISCOUNT
K007: - CUSTOMER DISCOUNT
MWST: - OUT PUT TAX
KF00: - FRIEGHT
Defining on the requirement. We need to maintain the condition amounts for the
condition type, maintaining the condition amount for a condition type is called
34
condition record and maintaining condition records for the condition type is called
conditions master data.
MAINTAINING CONDITION RECORDS: -

LOGISTICS


MASTER DATA

CONDITIONS

SELECT USING CONDITION TYPE “VK11” creates.
Specify the condition type for which the condition record has to be maintained
select the required key combination.
Then enter on “fast entry’s” screen maintain the condition record by specifying the
required the material and the corresponding amount.
The condition record is always valley with in the two dates specified for the fields
valid from and valid to.
SALES: -
To change the condition amount as the quantity “OR WEIGHT OR VOLUME etc”
changes, we need to maintain sales. For this select the record and select the icon
scales.
MAINTAINING LIMIT VALUES: -

Select the record and select the icon details and specify the required values for the
fields, “LOWER LIMIT AND UPPER LIMIT”. So that during pricing in the sales
document the condition type cannot be change to a value that false is and these
limits. (Save the condition record).
In the sales document the pricing information of the material is displayed on the
“conditions” tab page in the corresponding item data.
SALES DOCUMENT PROCESSING
STRUCTURE OF A SALES DOCUMENT: -
35
The entire data in the sales document lies at 3”levels” they are
HEADER DATA, ITEM DATA & SCHEDULE LINE DATA.
HEADER DATA: -
Any information which is applicable for the entire sales document it self. Is called
header data for example SOLD TO PARTY, SHIP TO PARTY, PO.NO,
DOCUMENT DATA, DOCUMENT CURRENCY ETC,
To see the header data select the icon display document header details from the
over view screen (or) in the over view screen from the main menu select Go to 
HEADER  select the required view.
ITEM DATA: -
Even though general data entered at header level up lies by default for all the items
in the sales document, each and every item in the document will have it own
related information called item data. For example material code, description, order
quantity, unit of measure, plant, pricing, ship to party etc.
Even though the data had header level is copy to the items if required it can be
changed at item level. But those changes are specifies to that particular line it an
only for which they have be made.
To select item data select the line item and select the icon display item details (or)
from the main menu select go to  item  select the required view.
SCHEDULE LINE DATA: -

It always gives the information about the delivery dates and corresponding
quantities depending on the availability of the material, Each and every item in the
document will have one or more number of schedule lines to see this schedule line
data of an item, go to the corresponding item data and select the views schedule
lines.
ORIZAN OF DATA IN THIS SALES DOCUMENT
INTRODUCTION: - During the sales document processing the system

automatically retries the data at all levels in the following way.
HEADER LEVEL: - At this level the system determines the data from the
customer record. The movement we entered sold to party in the sales document,
the system by default goes to the corresponding master record and checks weather
all the partners are same or they defer. If all the partners are same, the system
retries the entire data from the sold to party record it self. If the partners differ, the
36
system determines the data from different master records. Curtain details like sales
area , sales office, sales group etc will be determine from sold to party record,
curtain other details like unloading point, receiving point, shipping conditions etc,
will be incoterms, payment terms etc, will be determine from payer record.
ITEM LEVEL: - At this level the system retries the data in different ways for
example curtain details like. Unit of measure, conversion factors, gross weight, net
weight, division etc. will determined from the corresponding material master
record. Where as curtain other details like incoterms, payment terms, unloading
point etc, will be copied from header data the system determines the plant for the
item from one of the following master records by searching in the sequence in
which they are specified.
CUSTOMER MATERIAL INFOCORD
CUSTOMER MASTER RECORD
MATERIAL MASTER RECORD
SCHEDULE LINE LEVELS: - At this level the system proposes delivery dates
and the corresponding confirm quantities by checking availability of material and
also by considering the corresponding lead times.
CREATING THE SALES DOCUMENTS WITH REFERENCE

Example creating order with reference to quotation
CREATING QUATATION: -
LOGISTICS


SALES

QUOTATION

VA21CREATE.
Specify the quotation type “QT” enter the required data and save the quotation.
2. CREATE ORDER AGAIN’ST QUATATION: -
37
VA01, create specify the order type (OR)
Select the button “create with reference”
Specify the quotation number and select button copy
The entire data will be copied from quotation to sales order and save it.
3. DOCUMENT FLOW: - If the documents are create at reference, the system

forms a flow documents in which if we know one document number, with the help
the icon “DISPLAY DOCUMENT FLOW” we can see the other document
numbers.
STATUS OF A SALES DOCUMENT

We have “3” different status for a sales document. They are “open being process
and completed”
The status of a sales document always depends on status of the items in the
document. If the status of all the items in the document is “open”, the status of the
document is open. If the status of the document is completed, if the status of any
one of the items in the document is either open (With other items having the status
completed) Or being process. The status of the document is being process. The
status of the item in the document depends on the quantity that has been reference.
If it is fully referenced, the status of the item will be opened. If it is not at all
referenced, the status of the item will be opened. If it is partially referenced, the
status of the item is being process. We can see the entire status of a sales document
by selecting the button “status over view” in the document flow or select the TAB
page “status” in the header data. To see the status of individual items, select the
TAB page “status” in the corresponding item data.
CONTROLING THE DATA IN THE SALES DOCUMENT
As for the sales requirement for the client, the data at all the “3” levels in the sales
documents has to be process accordingly, for this we have the following
controlling partners in the sales document.
1. The data at header level is controlled by “sales document type”
2. The data at item level is controlled by “item category”
3. The data schedule line level is controlled by schedule line category.
SALES DOCUMENT TYPES

In a business process we have different sales transactions like Enquiry, Quotation,
Sales order, Return order etc; each sales transaction is having its own purposed
38
behavior. For example the transaction quotation is not relevant for shipping and
billing where as the other transactions. Sales order is relevant from both of them.
For each sales transaction we need to create a corresponding sales document in the
SAP system. While creating the sales document we have to specify the sales
transaction for which that sales document is created and it is always controlled by
sales document type each sales document is created by using a sales document type
which is the representation of the sales transaction in the SAP system and help the
system in further processing of the document.
The number of sales document types that we need to define depends on the sales
requirement of the client.
1). DEFINING SALES DOCUMENT TYPES

SPRO


SALES

SALES DOCUMENT


DEFINE SALES DOCUMENT TYPE.
EXAMPLE: - “IN” – ENQUIRY, “QT” – QUOTATION, “OR” – ORDER,

“RE” – RETUNS ORDER, “CS – CASH SALE, “RO” – RUSH ORDER (special
sales order) “DS” – SCHEDULING AGREEMENT,
“CR” – CREDIT IT MEMO REQUEST, “DR” DEBIT MEMO REQUEST.
FUNCTIONALITY OF SALES DOCUMENT TYPE
2. DOCUMENT CATEGERY
Specifies a classification of different types of documents that we can process in the
sales and distribution system. The document category determines how the system
stores and keeps track of the document data.
FOR EXAMPLE: - A) INQUIRY, B) QUOTATION, C) ORDER etc
3. SALES DOCUMENT BLOCK
39
Specifies weather the sales document type is blocked for processing.
If we block a sales document type, the users cannot create new sales documents of
that type. But those sales documents that are already created before setting the
block can be changed or displayed.
4. NUMBER RANGE INTERNAL ASSIGNMENT: -
5. NUMBER RENGE EXTERNAL ASSIGNMENT: -

Specifies the number ranges that either the system (If it is internal) or the user (If it
is external) uses for giving numbers for sales documents while saving them.
NOTE: - Creating number ranges for sales documents

SPRO


SALES

SALES DOCUMENT


DEFINIG NUMBER RANGES FOR SALES DOCUMENT
6). ITEM NUMBER INCREAMENT

Specifies the value by which the item number in the sales document increases.
“WHEN THE SYSTEM AUTOMATICALLY GENERATES ITEM NUMBERS”
in the sales documents.
7). SUB ITEM INCREAMENT; - Specifies the value by which the sub item
number is incremented in the sales document.
NOTE: - If we leave the field blank, the sub item number will be incremented by a
value by which the main item number is incremented.
8). REFERENCE MANDATORY: -
40
Specifies weather reference document is mandatory for creating the sales
document. If so it also specifies the document type that should be used as
reference.
9). ITEM DIVISION: -

If we check this field, the division at item level in the sales document will be
determined from corresponding material master record. Other wise the division
entered at header level will be copied to all the items in the document.
10). CHECK DIVISION: -

Specifies weather and how the system reacts if the division at item level in the
sales document defers from the division at he header level.
11). CHECK CREDIT LIMIT: -

Specifies weather the system carry’s out a credit limit check during the sales
document processing.
NOTE: - Its not required to carry out the credit limit check for curtain sales
document types  IN, QT, RE, CS, they are ways recommended to check the
credit limit for “OR”
12). READ INFORMATION RECORD: -

In the sales document if we specify the customer material number, the system
automatically determines original material number. For this we have to check this
field in the definition of corresponding sales document type.
13). CHECK PURCHASE ORDER NUMBER: -

Specifies weather and how the system reacts if multiple sales documents have the
same “P.O” number
NOTE: - If multiple sales documents have the same “P.O” number by using this
field we can get either warning message or no messages. If the requirement is to
get error message we have to user exists in ABAP. To see all the available user
exists go to.
SPRO


SYSTEM MODIFICATIONS

USER EXISTS
41
14). SCREEN SEACKVENCE GROUP: -
Specifies which screens we see during the sales document processing.
15). TRANSACTION GROUP: -

Specifies a group in that allows you to control a curtain characteristics of a
transaction according to sales document type. The transaction group controls the
types of documents that we can process with curtain system transaction.
0. FOR ORDER 1. FOR INQUIRY 2. FOR QUOTATION
16). DOCUMENT PRIECING PROCEDURE: -

This field enables the system to automatically determine a corresponding pricing
procedure during the sales document processing, depending on the sales document
type “A” default.
17). DISPLAY RANGE: -

Specify weather the system displays the entire item in the sales document (OR)
only main items.
18). F.CODE FOR OVER .V. SCREEN: -

Specify which other view screen we reach during the sales document processing
offer specifying the data on the initial screen.
19). QUOTATION MASSEGES: -

Set an indicator if we want to receive message information that open quotations
exist, while creating the sales document.
Depending on the indicator we select the system searches for open quotation in the
sales document either at header level for customer (OR) at item level for the
material.
NOTE: - It is always a recommended practice to use this feature for “OR”, never
use it for “IN” and depending on the requirement it can used for “Q1”,
20). OUT LINE AGREEMENT MESSAGES: -

Same as above but used for “OPEN AGREEMENTS”
21). MESSAGE MASTER CONTRACTS: -

Same as above but used for “OPEN CONTRACTS”
22). INCOMPLETION MESSAGES: -

If we check this field we can’t save the sales document. If it is in complete.
42
SHIPPING
23). DELIVERY TYPE : -
Specifies the corresponding delivery type of the sales document
Example: - LF – Delivery with reference to sales order.
NOTE: - No shipping date has to be specified for curtain sales document types.
Like “IN and QT”,
24). SHIPPING CONDITIONS: -

If we specify “shipping conditions” for this field in the definition of sales
document type, during the sales document processing the value for shipping
conditions will be determined from this field only but not from customer master
record.
25). DELIVERY RELATED BILLING TYPE: -
26). ORDER RELATED BILLING TYPE: -

Specifies the corresponding billing type of the sales document type
EX: - (F1) Order related invoice
(F2) Delivery related invoice.
NOTE: - No billing data as to be specified for curtain sales document types like
(“IN and QT”).
27). BILLING BLOCK: -

Specifies weather the sales document type is blocked for billing.
28). PROPOSE DELIVERY DATE: -

If we check this field, the system automatically proposes the current date as
requested delivery date in the sales document.
29). LEAD TIME IN DAYS: -
Specifies the number of days in to future that the system uses to propose the
requested delivery date in the sales document
30). PROPOSE (P.O) DATE: -

If we check this field, the system automatically proposes the current date as P.O
date in the sales document.
31). PROPOSAL FOR PRIECING DATE: -

Specifies the date that the system automatically proposes as “PRIECING DATE”
in the sales document
43
32). PROPOSED VALID FROM DATE: -
Specifies the default “VALID FROM DATE” while creating the documents such as
quotations.
ITEM CATEGORY
The data at item level in a sales document is controlled by item category.
Defining on the document in which an item is entered and depending on the item
that is entered in the document, the data has to be controlled accordingly.
1. EXAMPLE
The same item has to be processed in different ways in different sales documents.
FOR EXAMPLE: - If an item exist in quotation. It is not relevant for “ship to
party & billing party” where as it is relevant for both of item. If it exist in the
document sales order
2. EXAMPLE
The same item has to be processed in different ways in the same document.
FOR EXAMPLE: - If we offered free goods for an item, the main quantity has to
be priced but not the free goods quantity even though the material is same.
3. EXAMPLE
Different items are to be processed in different ways in a sales document.
FOR EXAMPLE: - If we create sales order for a third party item, the system shall
automatically create a purchase requisition which is not required for a standard
item. To fulfill all such sales requirements,, we need to defined different item
category’s with the corresponding functionalities
and make sure that the system automatically determines and appropriate item
category for the item during the sales document processing.
DEFINE THE ITEM CATEGORY

SPRO


SALES

SALES DOCUMENT

SALES DOCUMENT ITEM

44
DEFINE ITEM CATEGORY
STANDARD ITEMS
EXAMPLE: - AFN  ITEM CATEGORY OF INQUIRY
AGN  ITEM CATEGORY OF QUOTATION
TAN  IS IN CATEGORY OF ORDER
AFNN  THIS IS THE ITEM CATEGORY OF FREE GOODS INQUIRY
AGNN  THIS IS THE ITEM CATEGORY OF FREE GOODS QUOTATION
TANN  THIS IS THE ITEM CATEGORY OF FREE GOODS ORDER
TAS  THIRD PARTY ITEM OF CATEGORY
FUNCTIONALITY OF ITEM CATEGORY
COMPLETION RULE: -
Specifies the rule that establishes when the status of a quotation or contract is
completed.
FOR EX: - We can specify that the status of a quotation is completed after the full
quantity has been referenced or with the first reference it self or we can also
specify that it’s not relevant for completion.
BILLING RELEVANCE: -
Specifies weather the item is relevant for billing. If so it also specifies the reference
document for creating the billing document.
NOTE: - Curtain items such have the items enquiry and quotation cannot be billed
so the corresponding item category “AFN &AGN” respective or not relevant for
billing. But the item category “TAN” which is used in sales order is relevant for
billing.
BILLING BLOCK: -
Specifies weather the item is blocked for billing.
PRICING: -
Specifies weather the item is relevant for pricing or not.
BUSINESS ITEM: -
If we check this field, the business data at item level is allowed to defer from the
business data at header level in the sales document.
NOTE: - 1. Any information related to sales, shipping and billing is called business
data
2. The business data of returns item should not be changed in the return order of
type “RE”. So we must not check this field in that corresponding item category of
returns.
SCHEDULE LINE ALLOWED: -
Specifies weather we can have schedule lines for items in the sales document.
45
NOTE: -Curtain items such as the items in the document “CREDIT MEMO
REQUEST” need not have schedule lines. So we must not check this field in that
corresponding category (G2N)
ITEM RELEVANT FOR DELIVERY: -
Specifies weather a “TEXT ITEM” is relevant for delivery.
NOTE: - To make a text item has relevant for delivery, we have to check this field
in that corresponding item category “TATX”. We need to make the item category
“TATX” has text item by specifying the value (B) – (TEXT ITEM) for the field
item type.
RETURNS: -
If we check this field, the item becomes a returns item.
NOTE: - The items processed in the sales document of type “RE” are the return
items. So we have to check this field in that corresponding item category “REN”.
WEIGHT AND VOLUME RELEVANT: -
If we check this field, the system determines weight and volume of the item
In to sales document from the corresponding material master record.
CREDIT ACTIVE: -
Specifies weather the item is relevant for credit management activities.
NOTE: - The items processes in the document “cash sale” cannot be sold on credit
basis. So we must not check this field in that corresponding item category (BVN).
DETERMINE COST: -
If we check this field, the system determines the cost of the item during pricing in
the sales document.
NOTE: - The cost condition type is “VPRS”.
AUTOMATIC BATCH DETERMINATION: -
If we check this field, the system automatically determines a corresponding batch
number for the items in the sales document.
ROUNDING PERMITTED: -
If we check this field, the order quantity of the item will be rounded to the nearest
deliverable units depending on the rounding profile specified in the material
master.
ORDER QUANTITY = 1: -
If we check this field, the order quantity for each line item will be limited to “1”.
SCREEN SEAQUANCE GROUP: -
(N) – SAVE THE ITEM CATEGORY.
ITEM CATEGORY DETERMINATION
46
During the sales document processing the system automatically determines a
corresponding item category for the items. For this the following setting must be
done.
SPRO


SALES

SALES DOCUMENT

SALES DOCUMENT ITEM

ASSIGN ITEM CATEGORY
INQUIRY STANDARD AFN
QUOTATION STANDARD AGN
ORDER STANDARD TAN
RETURN STANDARD REN
CASH SALES STANDA RD BVN
rd
ORDER 3 PARTY SALES TAS
SALES DOCUMENT TYPES

ZIN
DOCUMENT – CATEGORY – “B”
ZQT1
DOCUMENT – CATEGORY – “C”
ZOR
DOCUMENT – CATEGORY – “A”
ITEM CATEGORIES
ZAFN ZAGN ZTAN

N.R COMPLETION  N.R COMPLETION  N.R COMPLETION
RULE RULE RULE
 REL.BILLING  N.R BILLING N.R BILLING
ZAFNN ZAGNN ZTANN
47
S.DOC ITEM USAGE HI LV DEF IT
TYPE CATE ITEM CAT
GROUP CAT
INQUIRY ZOR NORM - - ZAGN
INQUIRY ZOR NORM - ZAGN ZAGNN
QUOTATION ZIN NORM - - ZTAN
QUOTATION ZIN NORM - ZTAN ZTANN
ORDER ZQT NORM - - ZAFN
ORDER ZQT NORM - ZAFN ZAFNN
STANDARD ITEM CATEGORY DETERMINATIN

SD.TYPE ITEM CATEGORY USAGE HI LV ITEM DFL IT CATEG
IN NORM - - AFN
IN NORM - AFN AFNN
QT NORM - - AGN
QT NORM - AGN AGNN
OR NORM - - TAN
OR NORM - TAN TANN
RE NORM - - REN
CS NORM - - BVN
RO NORM - - TAN
CR NORM - - G2N
DR NORM - - L2N
OR NORM - - TAS
IN AFN NORM TAN NORM TAN
QT AGN
NORM ORDER ORDER
NOTE:
OR - While assigning
TAN the item
NORM category, whatTANN
ever theBANS
item category thatTAS
is
assigned as manual item category, with that we can replace the default item
category in the sales document.
SCHEDULE LINE CATEGORY: -
The data at schedule line level in the sales document is controlled by schedule line
category. We need to define different schedule line categories with the
corresponding functionalities to be used in the respective sales documents.
1. DEFINING SCHEDULE CATEGORY: -
SPRO

48

SALES

SALES DOCUMENT

SCHEDULE LINES

DEFINE SCHEDULE LINE CATEGORIES
EXAMPLE: - AT – INQUIRY SCHEDULE LINE
BN – QUOTATION SCHEDULE LINE
CP – ORDERS SCHEDULE LINE
CV – ORDERS SCHEDULE LINE
CN – ORDERS SCHEDULE LINE
DN – RETURNS SCHEDULE LINE
FUNCTIONALITY OF SCHEDULE LINE CATEGORY
1. DELIVERY BLOCK: -
Specifies weather the item is blocked for delivery.
2. MOVEMENT TYPE: -
Specifies the physical or logical movement of materials leading to a change in the
stock levels or resulting in the consumption of the material
EXAMPLE: -
601 – GOODS ISSUE DELIVERY
651 – GOODS RETUNS (RESTRICTED USE)
653 – GOODS RETURNS (UN RESTRICTED USE)
655 – GOODS RETURN FOR QUALITY INSPECTION
661 – GOODS RETURN TO VENDOR
301 – PLANT TO PLANT STOCK TRANSFER
561 – ENTYR OF STOCK IN THE PLANT
49
3. ITEM RELEVANT FOR DELIVERY: -
If we check this field, the item becomes relevant for delivery
NOTE: -A curtain item such has the items in inquiry and quotations are not
relevant for delivery. So we must not check this field in those corresponding
schedule line categories “AT & BN” respectively.
4. ORDER TYPE: -
Specifies the document type “NB” for this field in the schedule line category of
third party which is “CS”. For “CS” we have to specify the value “5”
(THIRD PARTY) for the field item category
5. REQUIREMENT OR ASSEMBLY: -
If we check this field, the requirement (ORDER QUANTITIES) will be transferred
from sales and distribution to inventory management.
6. AVAILABILITY
If we check this field, the system carry’s out availability check for the items in the
sales document.
7. PRODUCT ALLOCATION: -
If we check this field, product allocation will be activated for the items in the sales
documents.
SAVE THE SCHEDULE LINE CATEGORY
SCHEDULE LINE CATEGORY DETERMINATION

corresponding schedule line category for the items.
For this the following setting must be done.
SPRO

50

SALES

SALES DOCUMENTS

SCHEDULE LINES

ASSIGNED SCHEDULE CATEGORIES
Go to ‘new entries’ and assigned the schedule line category to the combination of
item category and MRP type.
NORM

M-10 M-14
Mrp type –VV ND
TAN TAN
 Availability  Availability
Requirement &  Requirement &
Assembly Assembly
ITEM CATEGORY MRP TYPE SCHEDULE LINE CATEGORY

TAN VV CP
TAN ND CV
NOTE: -During the schedule line category determination what ever the manual
schedule line category we have assigned, with that we replace the default schedule
line category in the sales document.
Sales Item Higher

document category usage level
type group item
Default
IN NORM _ item
category
51
QT NORM _ AFN
Mrp type
OR NORM _ AGN ND Sch line cat

OR NORM _ TAN ND AT
RE NORM _ TANN ND BN
CS NORM _ REN ND CP
OR BANS _ BVS ND CP
TAS ND BN
ND CD
DS
PRICING
During the sales document processing the system automatically calculates the net
value of the document by considering the condition values of different pricing
elements. For this we need to configure the entire pricing has per the clients
requirements in the sap system by using “CONDITION TECHNIC” which
comprises of,
CONDITION TABLES
52
ACCESS SEQUANCE
CONDITION TYPES
PRICING PROCEDURE DEFINATION
PROCING PROCEDURE DETERMINATION
1. CONDITION TABLES: -
The condition table contains the key fields for maintaining condition records for
the condition types. Depending on the requirement we can have any key field
while creating the condition table. One condition type can have multiple condition
tables and one condition table can be used for multiple condition types. If a
condition table is used for more than one condition type, the usage of condition
records maintained in that condition table depends on the condition type to which it
is assigned.
CREATING CONDITION TABLE
SPRO


BASIC FUNCTIONS

PRICING

PRICING CONTROL

DEFINE CONDITION TABLES

CREATING CONDITION TABLES
Specify a number for the condition table which must be between “501 & 999”.
In the over view screen, from the field catalogue which contains the list of
available fields, select the required key fields.
To specify the required description for the condition table select the icon
“PROPOSE OR MAINTAIN TEXT”.
While maintaining the condition records we can always set the validity period by
specifying the required dates for the fields valid from and valid to.
To get this two fields, we have to check the field “WITH VALIDITY PERIOD” in
the definition of condition table select button “TECHNICAL VIEW”.
53
Here the fields that are marked has “KEY” appears at key level and the fields that
are marked as “ FOOTER FIELD” appears at footer level while maintaining
condition records.
Select the icon generate.
Select the button “LOCAL OBJECT” for saving the condition table.
2. ACCESS SEQUANCE: -
The access sequence is a search strategies with the help of which the system
determines valid condition records for the condition types during pricing in the
sales document. For this we need to create an access sequence and place the
required condition tables in a specified order and than use that access sequence for
the required condition type.
An access sequence can have multiple condition tables and if required one access
sequence can be used for multiple condition types.
If an access sequence is having multiple condition tables, the order in which they
are kept in the access sequence is very much important. Generally it is from most
specific combination to most generic combination.
CREATING ACCESS SEQUENCE

SPRO


BASIC FUNCTIONS

PRICING

PRICING CONTROL

DEFINE ACCESS SEQUENCE

MAINTAIN ACCESS SEQUENCE
Go to new entries and create the access sequence.
Select the create access sequence and go to access.
Go to new entries and enter the required condition tables in the required order.
The field number specifies the sequential number of the condition table in the
access sequence.
“For the field table” we have to specify the condition table number.
54
For the condition tables entered in the access sequence “check the field exclusive”.
So that the system moves to a condition table to determine a condition record only
if it cannot determine a valid condition record in the previous condition table.
Select the condition table entered in the access sequence and go to “Fields”.
The system gives a warning message saying that “The field assignment has not at
been made”.
Proceed for that till you get the fields.
Repeat the same processor for all the condition tables in the access sequence and
save it.
NOTE: - After defining ACCESS SEQUANCE it has to be assigned to the required
condition type.
CONDITION TYPES: -
Ina business process the entire pricings divided in to ‘4’elements they are,
1. BASIC PRICE
2. DISCOUNT (or) SURCHARGE
3. TAX
4. FRIEGHT.
Each pricing element is having its own purpose and usage to maintain this in the
SAP system we have to define corresponding condition types with the respective
functionalities.
DEFINING CONDITION TYPES: -
SPRO


BASIC FUNCTIONS

PRICING

PRICING CONTROL

DEFINE CONDITION TYPES

 MAINTAIN CONDITION TYPES 
FUNCTIONALITY OF A CONDITION TYPE
A). ACCESS SEQUANCE: - Specifies the corresponding A-SEQ of the condition

type.
55
B). CONDITION CLASS: -Specify the preliminary structuring at condition types
that allows you to control each condition type differently.
FOR EX: - The condition class “TAXES” specifies that the tax component has to
be predetermined if the location of the SHIP TO PARTY is changed in the sales
document.
C). PLUS (or) MINUS: - For a condition type if we specify the value
“NEGETIVE” for this field, it becomes discount and if we specify the value
“POSITIVE” becomes sir charge.
D). CALCULATION TYPE: - Specifies how the condition amount of a condition

type is calculated.
E). CONDITION CATEGORY: - Specifies the classification for different types

of conditions according to be predefined categories.
FOR EX: - All those conditions that related to freight costs.
F). ROUNDING RULE: - Specifies the rule that determines how the system
rounds off the condition values during pricing.
G). MANUAL ENTRIES: - Specifies weather the condition type can be manually
entered during pricing in the sales document (or) it has to be automatically
determined by the system.
H). AMOUNT (or) PERCENT: - If we check this field, the condition amount of a
condition type can be changed during pricing in the sales document.
I). VALUE: - If we check this field, the condition value of the condition type can
be changed during pricing in the sales document.
J). CALCULATION TYPE: - If we check this field, the calculation type of the
condition type can be changed during pricing in the document.
NOTE: - If we change the calculation type for a condition type in the sales
document, it is applicable to that particular line item only for which it is changed.
K). DELETE: - If we check this field for a condition type, it can be deleted during
pricing in the sales document.
L). ITEM CONDITION: - If we check this field for a condition type, it becomes
an item condition where it has to be entered at item level in the sales document.
56
The condition amount of the item condition is specific to that particular line item
only for which it is entered.
M). HEADER CONDITIONS: - If we check this field for a condition type, it

becomes header condition where it has to be entered at header level in the sales
document. The condition amount of the header condition will be copied has it is to
all the items in the sales document.
NOTE: - 1. Header condition type does not contain access sequence
2. After specifying the header condition type in the sales document,
We have to select the button activate.
3. The example for header condition is RB00.
N). GROUP CONDITION: - If we check this field for a header condition, it

becomes a group condition where the condition amount is not copied as it is to all
the items in the document, but is distributed proportionately among the items in the
document.
O). VALID FROM: -
P). VALID TO : - Specifies the beginning and ending of the validity dates that
the system automatically proposes while maintaining the condition records for the
condition type.
Q). REFERENCE CONDITION TYPE: - Specifies the condition type that can
be used as reference so that we only need to maintain condition records for the
reference condition type which will be automatically copied to other condition type
(In which reference condition type is entered) during pricing in the sales document.
NOTE: - Before specifying the reference condition type, first we have to Specify
the reference condition.
R). DELETE FROM DATA BASE: - Specifies weather the condition record has
to be deleted physically from the data base or decision indicator has to be while
deleting the condition record of the condition type.
S). SCALE BASIS: - Specifies how the scale amount of a condition type is
calculated.
FOR EX: -The system can calculate the pricing scale based on quotation (or)
weight (or) volume etc.
57
T). CHECK VALUE: - Specifies weather the scale rates must be entered in assign
ding or descending order.
U). SCALE FORMULA: - Specifies a routine which explains the formula for
calculating the scale amount of the condition type.
PRICING PROCEDURE
During the sales document processing the system automatically calculates the net
value of the document by considering the condition values of different condition
types. For this we need to define a pricing procedure in which we have to place all
the required condition types in a specified order and used that procedure for the
required document.
DEFINING PRICING PROCEDURE: -

SPRO


BASIC FUNCTIONS

PRICING

PRICING CONTROL

DEFINE ASSIGN PRICING PROCEDURES

MAINTAIN PRICING PROCEDURE
Go to “new entries” and create a pricing procedure.
Select the created pricing procedure and go to control data.
Go to “new entries” and specify the required condition types in the required order.
A). STEP: - Specifies the sequential number of a condition type in the pricing
procedure.
B). COUNTER: - Specifies the sequential number of a condition type with in a
step in the pricing procedure.
C). CONDITION TYPE: - Specify the required condition type.
D). DISCRIPTION: - Specifies the description of the condition type which will be
automatically determined from the definition of condition type.
58
E). FROM: -  If we specify the reference steps for the two fields, the condition
values of the steps specified and the condition values of the steps
in between will be totaled.
F)…... TO: - 
G). MANUAL: - Conditions that are given this indicator will be determined during
pricing in the sales document either if they are entered manually or determined
from other application such has costing.
(PR00 is no need to select)
H). REQUIRED: - (MANDATORY). If we check this field for a condition type, it
becomes mandatory during pricing in the sales document.
I). STATISTICS: - Conditions that are given this indicator will be set statistically
during pricing in the sales document that is the condition values of such condition
types will not be taken in to account while calculating the net value in the
document.
J). PRINT I.D: - Controls the issuing of condition lines while printing the
documents such has order confirmations or invoices.
K). SUB TOTAL: - Specifies weather and in which tables the condition values
must be stored.
L). REQUIREMENT: - The requirement specifies when a condition type has to
be determined during pricing in the sales document that is if a condition type has to
be determined in to sales document, the requirement specified here must be
specify.
FOR EXAMPLE: - The condition types like “PR00, K004” etc or to be

determined for those items which are relevant for pricing and even for free goods
also because we need to know the worth of free goods offered to the customers.
The relevancy of an item for pricing is controlled by item category with the field
“PRICING”. If the item is relevant for pricing, the value for this field will be “X”
where as for free goods it will be “B”. So these condition types or to be determined
for those items where the corresponding item category for the field pricing
contains either “X or B”. This is controlled by specifying the routine “2” for the
field requirement while placing these condition types in the pricing procedure.
But the condition type “R100” which offers 100% discount must be determined
only for free goods that are only for those items where the corresponding item
category for the field pricing contains “B”. This is controlled by specifying the
routine “55” for the field requirement while placing “R100” in the pricing
procedure.
DET MINES COND
REQUI CON.REC MANDATORY MESSAGE
TYPES INTO S.DOC
59
  /  
1. If the requirement is satisfied and condition records are maintained, the
condition type will be determined in to sales document. In this case the
system will not give any message in the sales document even though it’s
mandatory (or) not.
DET MINES COND

TYPE INTO S.DOC
    
2. If the requirement is satisfied and condition records are not maintained, the
condition type will not determined in to sales document. In this case the
system will give message to the sales document even though it’s mandatory.
DET MINES COND

TYPE INTO S.DOC
    
3. If the requirement is satisfied and condition records are not maintained, the
condition type will not determined in to sales document. In this case the system
will not give any message to the sales document even though it’s not mandatory.
DET MINES COND

TYPE INTO S.DOC
 / /  
4. If the requirement is not satisfied and condition records are maintained (or) not,
the condition type will not determined in to sales document. In the case the system
will not give any message in the sales document even though it’s not mandatory.
M). CAL TYPE (ALTERNATIVE CALCULATION TYPE): -

Specifies an alternative formula to the standard formula that determines how the
condition amount of a condition type is calculated.
FOR EX: - The profit margin of an item has to be calculated by deducting the cost
of the item from the net value of the item in the document. This is controlled by
specifying the routine “11” for this field while placing profit margin in the pricing
procedure.
N). BAS TYPE (ALTERNATIVE CONDITION BASE VALUE): -
60
Specifies a formula for determining the “condition basis” as on alternative to the
standard.
FOR EX: - The condition base value of the condition type “R100” is 100%
discount which will not change depending on any key combination. So rather
maintaining condition records for “R100”, we can maintain the condition base
value as “minus 100%” by specifying the routine “20” for this field while placing
“R100” in the procedure.
O). ACCOUNT KEY: - It enables the system to post the condition values of the
condition types to the corresponding G/L accounts during revenue account
determination procedure.
FOR EX: - ERL – (SALES REVENUE) ERS – (SALES DEDUCTIONS)
P). ACCRUALS KEY: - The accrual key enables the system to post the “rebate
accruals” to the corresponding G/L accounts.
FOR EX: - (ERU) rebate accruals (this code must be used only rebate).
 SAVE THE PRICING PROCEDURE 
PRICING PROCEDURE DETERMINATION

corresponding pricing procedure. For this the following setting must be done.
SPRO


BASIC FUNCTIONS

PRICING

PRICING CONTROL

DEFINE AND ASSIGN PRICING PROCEDURE

DEFINE PRICING PROCEDURE DETERMINATION
Go to new entries and assign the pricing procedure to the combination of sales
organization, distribution channel, division, document pricing procedure and
customer pricing procedure.
61
Sales organization sales area customer pricing procedure
Q1Q1 WH WH- 1 (0R*** “D.S – B”)
Distribution channel sales area customer pricing procedure

BQ WH
DQ RT RT- 2
Division sales area customer pricing procedure

CQ WH “WH- 3”
PRICING PROCEDURE (W/H)

WHOLE SALE RETAIL
 
RVAA01 RVAA02
PR00 = 1500.00 ZR00 = 1000.00
K004 - 100.00 Z004 - 110.00
K007 - 3% Z005 - 50.00
PRICING PROCEDURE DETERMINATION

I S.O D.CH DV D.PRC C.PRC ASS TO
Q1Q1 BQ CQ A 1 RVAA01
Q1Q1 DQ CQ A 2 RVAA02
If the requirement is to have a separate pricing procedures with in a group of

customers, for example whole sellers
II S.O D.CH DV D.PRC C.PRC ASS TO
Q1Q1 DQ CQ A 3 RVAA03
III S.O D.CH DV D.PRC C.PRC ASS TO

Q1Q1 DQ CQ B 1 RVAA04
If the requirement is to have different pricing procedures for a customer depending
on the sales document type.
62
NOTE: - Creating customer and document pricing procedures.
SPRO


BASIC FUNCTIONS

PRICING

PRICING CONTROL

DEFINE ASSIGN PRICING PROCEDURE

DEFINE CUSTOMER PRICING PROCEDURE
Go to new entries and create the required customer pricing procedures.
NOTE: - This value has to be specified in the required customer master
DEFINE DOCUMENT PRICING PROCEDURE

Go to new entries and create the required document pricing procedure.
NOTE: - This value has to be specified in the required sales document type.
CONDITION EXCLUSION: -
If we maintained exclusion indicator for a condition type, during pricing in the
sales document the system excludes (will not determined) the other below existing
condition types that have the same “requirement” has that condition type in which
exclusion is maintained.
We can maintain the exclusion in the definition of condition type or in the
condition records. If we maintained the exclusion in the definition of condition
type, by default it will be copied to all the condition records of that condition type
so that the condition exclusion will be working let it be any record that is copied in
to sales order. If we maintained the exclusion in the condition record rather the
condition type, the condition exclusion will be working only if that condition
record in which exclusion is maintained is copied in to sales order.
CONDITION SUPPLEMENTS: -Maintaining condition record for a condition

type in another condition type is called condition supplement.
63
FOR EX: -Maintaining “K007” has condition supplement in “PR00” select the
condition record of “PR00” and select the icon condition supplement and maintain
the record for “K007”.
NOTE: - To maintain a condition type has condition supplement in the other
condition type the following setting must be done.
The pricing procedure specified in the definition of that condition type in which the
condition supplement is entered must contain the condition type that is entered has
supplement.
NOTE: - Condition supplement will not be excluded.
NOTE: - during the sales document processing the system automatically calculates
the net value of the document by determining condition records for the condition
types in the following way.
PRICING PROCEDURE - (RVAA01)

CONDITION TYPE - (PR00)
ACCESS SEQUANCE - (PR02)
CONDITION TABLES
CUSTOMER MATERIAL
MATERIAL
VALID CONDITION RECORD  
VALID CONDITION RECORD  
PRICING DETERMINATION

PRICING PROCEDURE

CONDITION TYPES

ACCESS SEQUANCE

CONDITION TABLES
CONDITION RECORD
64
FREE GOODS DETERMINATION
(Inclusive & exclusive)
INCLUSIVE FREE GOODS: -

For a material giving the same material has free goods is called inclusive free
goods.
EXCLUSIVE FREE GOODS: -

For a material giving the different material has free good is called exclusive free
goods.
MAINTAINING CONDITION RECORDS FOR INCLUSIVE FREE

GOODS.
LOGISTICS


MASTER DATA

CONDITIONS

FREE GOODS

VBN1 CREATE
Specify the required condition type for free goods.
Select the required key combination. (Enter)
Maintain the condition record by specifying the data for the following fields.
1). MATERIAL: - Specify the material for which free goods are offered.
2). MINIMUM QUANTITY: - Specifies the minimum quantity of the
Material that must be ordered in order to get the free goods
3). FROM: - specifies the quantity from which free goods start.
4). UNIT OF MEASURE OF FREE GOODS: - #---------------#
5). ARE FREE GOODS: - Specifies the quantity of free goods offered for
That quantity specified in the field “FROM”.
65
6). CALCULATION RULE: - Specifies the rule for calculating the quantity of
free goods in the sales document.
7). FREE GOODS: - Specifies weather the records are maintained for
Inclusive or exclusive free goods
8). FREE GOOD DELIVERY CONTROL: -Specifies weather the free

Goods can be delivered regardless of the main item or in conjunction with the main
item (SAVE THE RECORD)
NOTE: - the inclusive free goods determines “10 pieces has 9+1” in the sales
document that is with in the order quantity it self the system proposes the free
goods.
MAINTAINING CONDITION RECORDS FOR EXCLUSIVE FREE

GOODS
LOGISTICS


MASTER DATA

CONDITIONS

FREE GOODS

VBN1 CREATE
Specify the required condition type for free goods.
Select the required key combination. (Enter)
1). MATERIAL: - Specify the material for which free goods are offered.
2). MINIMUM QUANTITY: - Specifies the minimum quantity of the
Material that must be ordered in order to get the free goods
3). FROM: - specifies the quantity from which free goods start.
4). UNIT OF MEASURE OF FREE GOODS: - #---------------#
5). ADDITIONAL FREE GOODS: - Specifies the quantity of free goods
Offered for that quantity specified in the field “FROM”
6). CALCULATION RULE: - Specifies the rule for calculating the
quantity Of free goods in the sales document.
7). FREE GOODS: - Specify the value  exclusive free goods
66
8). ADDITIONAL MATERIAL FREE GOOD: - Specify the material that
Is given has free good.
9). FREE GOOD DELIVERY CONTROL: -Specifies weather the free
Goods can be delivered regardless of the main item or in conjunction
With the main item (SAVE THE RECORD)
NOTE: - 1). The exclusive free goods determine 10 pieces as 10+1 that is rather
proposing the free goods with in the ordered quantity it self, the system offers
additional quantity of free goods.
2). In the exclusive free goods, if required the same material can be given has free
good.
NOTE: - Before maintaining the condition records, first we have to maintain
condition technique for free goods.
For this go to SPRO


BASIC FUNCTIONS

FREE GOODS

CONDITION TECHNIQUE FOR FREE GOODS
1). MAINTAIN CONDITION TABLES

Create the required condition tables with the corresponding key fields.
2). MAINTAIN ACCESS SEQUANCES
Create an access sequence and place the required condition tables in it.
3). MAINTAIN CONDITION TYPES
Go to new entries and create a condition type with the corresponding
Access sequence
4). MAINTAIN PRICING PROCEDURES
Define a procedure and place the required condition in it.
5). ACTIVATE FREE GOODS DETERMINATION
Go to new entries and assign the free goods procedure to the combination
of SALES ORGANIZATION, DISTRIBUTION CHANNEL,
DIVISION, PRICING PROCEDURE, CUSTOMER PRICING
PROCEDURE
67
MATERIAL LISTING AND EXCLUION
MATERIAL LISTING: -
What ever the materials that are placed in listing for a customer, he can access
those materials only.
MATERIAL CONDITION RECORD FOR MATERIAL LISTING

LOGISTICS


MASTER DATA

LISTING & EXCLUSION

VB01 CREATE
Specify the condition type for listing.
Select the required key combination (enter)
Specify the required materials in listing and save it.
MATERIAL EXCLUSION: - What ever the materials that are placed in exclusion
for a customer, he cannot access those materials.
MAINTAINING CONDITION RECORDS FOR MATERIAL EXCLUSION
LOGISTICS


MASTER DATA

LISTING & EXCLUSION

VB01 CREATE
Specify the condition type for exclusion.
68
Select the required key combination (enter)
Specify the required materials in exclusion and save it.
NOTE: - If a material exist both in listing and exclusion, by default exclusion is

given preference over listing.
NOTE: - Before maintaining condition records, first we have to maintain condition
technique for material listing and exclusion.
For this go to
SPRO


BASIC FUNCTIONS

LISTING & EXCLUSION
1). MAINTAIN CONDITION TABLES FOR LISTING&EXCLUSION

We need to create  or more condition tables to be used for listing & exclusion
2). MAINTAIN ACCESS SEQUANCE FOR LISTING&EXCLUSION

Depending on the requirement we need to create  or  access sequence to be
used for listing & exclusion.
3).MAINTAIN LISTING&EXCLUSION
We need to create  condition types  each for listing & exclusion and assign the
corresponding access sequences.
4). PROCEDURES FOR MAINTAINING LISTING&EXCLUSION

We need to define  procedures,  each for listing & exclusion and the
corresponding condition types in item.
5). ACTIVATE LISTING&EXCLUSION BY SALES DOCUMENT TYPE

Select the required sales document type & assign the procedures for listing &
exclusion.
69
MATERIALDETERMINATION(or)SUBSTITUTION
Substituting a material with another material or materials is called material
determination. In the sales document when we entered the main item ordered by
the customer, the system automatically proposes the list of substitute item from
which the customer can select the required materials or he can go with the main
item it self.
MAINTAINING CONDITION RECORDS FOR MATERIAL
DETERMINATION
LOGISTICS


MASTER DATA

PRODUCTS

MATERIAL DETERMINATION

VB11 (CREATE)
Specify the condition type for material determination
Select the required key combination (Enter)
1). MATERIAL ENTERED: - Specify that main item that has to be substituted
2). MATERIAL: - Specify that item with which the main item has to be
substituted.
70
3). REASON: - Specify the reason for substitution. To specify multiple materials
for substitutions, select the record and select icon alternative materials.
(SAVE THE RECORD)
NOTE: - Before maintaining condition records, first we have to maintain condition

technique for material determination.
For this go to
SPRO


BASIC FUNCTIONS


MAINTAIN PRE REQUISITIES FOR MATERIAL DETERMINATION
1). CREATE CONDITION TABLES: - We need to create the condition table by

having the key field “material entered” along with the other required field it any.
2). MAINTAIN ACCESS SEQUENCE: - Create an access sequence and place

the required condition tables in it.
3). DEFINE CONDITION TYPES: - Create a condition type and assign the
corresponding access sequence.
4). MAINTAIN PROCEDURE: - Define a procedure and place the condition type
in it.
5). ASSIGN PROCEDURES TO SALES DOCUMENT TYPES: -

Select the required sales document type and assign the procedure.
DEFINE THE REASON FOR SUBSTITUTION

SPRO

71

BASIC FUNCTIONS


DEFINE SUBSTITUTION REASONS
Go to new entries and create
1). SUBSTITUTION REASON: - Specify the required code
2). DISCRIPTION: - Specify the reason for substitution.
3). ENTRY: - If we check this field, the system prints the original material
Entered before substitution on the corresponding out put
4). WARNING: - If we check this field, the system gives a warning

Message is for substituting the main item in the sales document.
5). STRATEGY: - Specifies weather the product selection should occur

Automatically in the back ground offered for selection in a dialogue box.
6). OUT COME: - Specifies weather the out come of product selection should
replace the original entry or it should be recorded has a sub item of the original
entry
NOTE: - This feature out come can be used if the requirement is to sell the
substitute item at the price of main item. For this the following settings must be
done.
1). The system has to determined the price for the main item but not for the
substitute item for this the item category of the main item TAX must be relevant
for pricing where has the item category of the substitute item TAPS must not be
relevant for pricing
Sales doc type Item category Usage Hl lv item categ Dftitemcategory
72
OR NORM PSHP TAX
OR NORM PSA2 TAX TAPS
2). It is the substitute item that has to be delivered but not the main item so the
system has to reduce the stock for the substitute item only. For this we must not
specify any movement type in the schedule line category of main item which is CX
where has we must specify the movement type “601” in the schedule line category
of substitute item which is PP
ITEM CATEGORY MRP TYPE SCHEDULE LINE CATEGORY

TAX - CX
TAPS - PP
BOM: - BILLS OF MATERIAL
Any material which is manufactured by adding different company together is
called “BOM” item. We need to crate the material master records for the BOM
item as well as for the components and add all those components to the BOM item.
While creating the BOM item, we have to specify the item category group has
“ERLA or LUMF” and the components can be created has standard items.
CREATING BOM: -
LOGISTICS


MASTER DATA

PRODUCTS

BILLS OF MATERIAL

BILL OF MATERIAL

MATERIAL BOM

CS01 CREATE
1). MATERIAL: - Specify the BOM item for which components are to be added.
2). PLANT: - Specify the plant of the BOM item.
73
3). BOM USAGE: - Specifies the module in which BOM is used.
4). ALTERNATIVE BOM: - Specifies the number of the BOM if the material is
having multiple BOMS.
In the over view screen specify the required components with the corresponding
quantities and (SAVE THE BOM)
I). For the system to explore the BOM in the sales document, the following
settings must be done.
a). If the item category group of the BOM item is ERLA, the corresponding item
category of that item is “TAQ” in which we have to specify the value “A”
(EXPLODE SINGLE LEVEL BOM) for the field “structure scope”.
b). If the item category group of the BOM item is “LUMF” the corresponding item
category of that item is “TAP” in which we have to specify the value “A”
(EXPLODE SINGLE LEVEL BOM) for the field “structure scope”.
II). If the item category group of the BOM item is “LUMF”, the system determines
price for the components not for the BOM item. For this the following settings
must be done.
a). The item category of BOM item is “TAP” which must not be relevant for
pricing.
b). The item category of BOM item is “TAN” which must be relevant for pricing.
III). If the item category group of the BOM item is “ERLA”, the system
determines price for the BOM item but not for components. For this the following
settings must be done.
a). The item category of components is “TAQ” which must be relevant for pricing.
b). The item category of components is “TAE” which must be not relevant for
pricing.
NOTE: - If the material is having multiple BOM’S, we can get the list of all those
alternative BOM’S in the sales document. For this we have to check the field
“MANUAL ALTERNATIVE” in the item category of BOM’S item.
NOTE: - While creating the BOM we can specify the required description for the
field “ALTERNATIVE TEXT” to explain the BOM item in more detail. For this in
the BOM over view screen select the icon header.
ITEM CATEGORY ASSIGNMENT

SALES ITEM USAGE HIGHER LEVEL DEFAULT
DOCUMENT CATEGORY ITEM ITEM
TYPE CATEGORY CATEGORY
74
OR ERLA - - TAQ
OR NORM - TAQ TAE
OR LUMF - - TAP
OR NORM - TAP TAN
For detailing go to “BOM” material and delete.

NOTE: -
NET VALUE SHOULD NOT TO BE DOUBLED.
To get the price for the main item as well as for the components with out the net
value being doubled the following settings must be done.
ERLA
M-13 TAQ (PRICING)
M-10
TAE (NO PRICING)
M-11
Make “TAE” relevant for pricing
Statistical value (X (or) Y)
TAE is not used any where expect for component, of BOM.
LUMF: - TAP TAN

PRICING PRIECING RELEVANT
STATISTICUAL VALUE (X (or) Y)
MULTILEVEL BOM: - M – 13 ERLA: - - - - - - TAQ

Norm M - 10 TAE  OR ERLA --- TAQ
Norm M - 12 TAE   OR NORM --- TAQ, TAE
Norm M – 11 TAE    OR NORM --- TAE - TAE

SOLUTION: - 1).CS01 2). CS02  3). TAQ TAP
M – 13 M – 10
M - 10 M - 12
M – 11 structured scope – “B”
NOTE: - In the above case if we create sales order only for M -10, it becomes main
item for which the system determines the item category “TAN” which cannot pick
the components to over come this the following setting must be done.
75
M – 13 ---- (LUMF)TAP   OR LUMF -------- TAP
M – 10 (NORM) TAN     OR NORM -------- TAP - TAN
 M – 12 (NORM)
M – 11 (NORM)TAN   
NOTE: -
1). In the above case the system determines the item category “TANN” for M – 12
which makes it as free goods. To over come this we shall use a different item
category group for M – 12 for ex – ZORM and use the item category TAE with
following assignment (OR, ZORM – TAN, TAE).
NOTE: -
2). In the above case if you create sales order the system determines the item
category TAN which cannot pick the components. To over come this the following
setting must be done.
M – 13 (LUMF) TAP    OR ---- LUMF – TAP, TAN
M - 10 (LUMF) TAN
 M – 12 (ZORM) TAE OR – ZORM – TAN - TAE
M – 11 (NORM) TAN
CREDIT MANAGEMENT
SALES ORGANIZATION RISK CATEGORY CREDIT GROUPS
  
COMPANY CODE CUSTUMER TRANSACTION
TYPE

CREDIT CONTROL
CREDIT CONTROL AREA

It is the responsible organizational element which takes care of all credit
management activities in the company code.
CREDIT CONTROL AREA
76
COMPANY CODE -1 COMPANY CODE -2
SALES ORGANIZATION -1 SALES ORGANIZATION-2
CREDIT CONTROL AREA-1 CREDIT CONTROL AREA-2

 
COMPANY CODE-1 COMPANY CODE -2
SALES ORGANIZATION -1 SALES ORGANIZATION -2
DEFINING CREDIT CONTROL AREA

SPRO


DEFINATION


DEFINE CREDIT CONTROL AREA
Go to new entries
In the definition of credit control area we have to specify the currency, fiscal
Year variant and we also need to specify which documents are to be updated
From sales and distribution to finance for updating the credit limits.
The credit limit specified in the definition of credit control area by default applies
for all those new customers for whom the credit limits have not at be maintained.
ASSIGNING COMPANY CODE TO CREDIT CONTROL AREA

SPRO


ASSIGNMENT


77
ASSIGN COMPANY CODE TO CREDIT CONTROL AREA
Select the required company code and assign the required credit control area.
ASSIGNING SALES AREA TO CREDIT CONTROL AREA

SPRO


ASSIGNMENT


ASSIGN SALES AREA TO CREDIT CONTROL AREA
Select the required sales area and assign the required credit control area.
DEFINING RISK CATEGORY
SPRO

FINANCIAL ACCOUNTIGS

ACCOUNTS RECIEVABLE AND ACCOUNTS PAYABLE

CREDIT MANAGEMENT

CREDIT CONTROL CATEGORY

DEFINE RISK CATEGORIES
Go to new entries and create a risk category for the required credit control area.
NOTE: - After creating the risk category, it has to be assigned to the required
customers.
CREDIT GROUPS: -The credit groups specify which transaction can be locked
for processing if the credit limits are exceeded.
For defining the credit groups go to
SPRO


78
BASIC FUNCTIONS

CREDIT MANAGEMENT & RISK MANAGEMENT

CREDIT MANAGEMENT

DEFINE CREDIT GROUPS
For ex: -1). Credit group for sales order
2). Credit group for delivery
3). Credit group for goods & issue
NOTE: - For the system to block the corresponding transactions by using there
credit groups we have to assign these credit groups, to the respective transactions.
For this assignment go to

ASSIGN SALES DOCUMENTS AND DELIVERY DOCUMENTS.
A). Credit limit checks for order types select the required sales document type
assign the required credit group.
B). Credit limit check for delivery types select the read delivery type and assign the
corresponding credit groups. (02, 03) respectively to block the delivery and goods
issue
MAINTAINING CREDIT LIMIT FOR CUSTOMERS

LOGISTICS


CREDIT MANAGEMENT

MASTER DATA

FD32 CHANGE
Specify the customer for whom the credit limits are to be maintained and also
specify the credit control area of the customer.
Select all the views.
In the over view screen from the main select “go to”
CONTROL AREA DATA
79
STATUS
1). CREDIT LIMITS: - Specify the credit limits of the customer.
A). CREDIT HORIZAN DATE: - If we specify a data here only those out
standing order values. Which fall with in the horizon date is taken in to account
while calculating the credit limit used.
B). RISK CATEGORY: - Specify the risk category of the customers.
C). LAST INTERVAL REVIEW: - Specifies the data on which the customer
credit limits or last view.
D). NEXT INTERVAL REVIEW: - Specifies the date on which the customers
credit limits are going to review.
2). PAYMENT HISTORY: - On this view the system displays the pay must
history of the customer (provided we check the field payment history record)
In the corresponding customer data
3). FROM THE MAIN MENU GO TO: -General data & Central data.
A). TOTAL AMOUNT: - The amount for this field specifies the over all credit
limit the customer may receive in all the credit control areas.
B). INDIVIDUAL LIMITS: - The amount this field specifies the maximum credit
limit the customer may receive with in a credit control area. (Save it).
AUTOMATIC CREDIT CONTROL: - During the sales document processing if

the credits limits are exceed the system can automatically block the required
transaction for this we have to configure automatic credit control. For this go to
SPRO


BASIC FUNCTIONS

CREDIT MANAGEMENT & RISK MANAGEMENT

80
CREDIT MANAGEMENT

DEFINE AUTOMATIC CREDIT CONTROL.
We need to configure the automatic credit control in the combination of,

CREDIT CONTROL AREA RISK CATEGORY CREDIT GROUP
Ex: - credit control area – 1000 credit group – 01 – order
Risk category - 001 - 02 – delivery
- 002 - 03 – good issue
- 003
1).
1000 0002 01 This automatic credit control enables the system
to block the sales orders if the
credit limits are
Exceed for those customers with high
Risk category
2).
To block the goods issue if the credit limits are
Exceed for those customer. Low risk category.
3).
Block the delivery creates on. If the credit limits
Are exceeded for those customer with medium
Risk category
Go to new entries and enter the required combination of credit control area, risk
category and credit group. Specify the description.
81
ITEM CHECK: - If we check this field the system carries out the credit limit
check the movement we enter the item in the sales document other wise it checks
for credit limits while saving the document.
CREDIT LIMIT SEASONAL FACTOR: - Specifies the percentage by which the

credits limit her to be either increase or decrease during the specified period
CREDIT HORIZAN DATE
CHECKS: - (DYNAMIC): - If we go for this check for the purpose of valuating

credit, the system ignores all those open orders there for a due for delivery after the
horizon date.
STRATRIC: - If we go for this check for the purpose of a valuating credit the
system considers all those open orders that are due for delivery after the horizon
data.
DOCMENT VALUE: - If we check the system carries out the credit limit
check. For each sales document depending on the value, specified for the field
maximum document value.
NATIVE: - The document value check can be used for new customer for whom
the credit limits have not yet to be maintained.
REACTION: - Specifies weather and how the system reacts in the sales document
if the credit limits are exceeded.
STATUS (or) BLOCK: - If we check this field the system automatically blocks
the corresponding transaction controlled by credit group if the credit limits are
exceeded. (SAVE IT)
NOTE: - During sales document processing if the system has to carry out the credit
limit check, the following system also is done.
1). In the definition of sales document types we must not specify the value “no
credit limit check” for the field check credit limit.
2). In item category we have to check “credit active”.
82
REVENUE ACCOUNT DETERMINATION
PROCEDURE
When we save the billing document, the system automatically post all the values to
the corresponding G/L accounts. For this we have to configure the revenue account
determination procedure.
For the system to post the sales values to the corresponding G/L accounts, we have
to assign the G/L accounts to a given combination of fields.
For this assignment go to
SPRO


BASIC FUNCTIONS

ACCOUNT ASSIGNMENT AND COSTING


ASSIGN G/L ACCOUNTS (VK0A)
Go to the details of first table.
Go to new entries and assign the required G/L account to the combination of
following fields.
1). APPLICATION: -Specify “V” for sales distribution.
2). CONDITION TYPE: - Specify the combination type in the revenue account
determination procedure. For which the condition records are maintained that is
G/L accounts are assigned.
Ex: - (KOFI) This condition type is used for finance purpose
(KOFK) it is used for controlling.
3). CHART OF ACCOUNTS: - It’s a classification scheme used for the grouping
of G/L accounts. It provides a frame work for the recording of values to ensure and
orderly rendering of accounting data.
Here we need to specify the chart of accounts in which the G/L accounts we are
assigning exist.
4). SALES ORGANIZATION: - Specifies the sales organization from which the
values are to be posted to the corresponding G/L accounts.
83
5). ACCOUNT ASSIGNMENT GROUP OF CUSTOMER: - This is specified
in the customer master which enables the system to post the
Sales values of different customers to the corresponding G/L accounts
6). ACCOUNT ASSIGNMENT GROUP OF MATERIAL: - This is specified in

the material master which enables the system to post the sales values of materials
of different material types to the corresponding G/L accounts.
7). ACCOUNT KEY: - This is specified in the pricing procedure for the condition
type which enables the system to post the condition values to the corresponding
G/L accounts.
SALES ORGANIZATION
1000
ACCOUNT ASSIGNMENT GROUP OF CUSTOMER

01 – DOMESTIC
02 – EXPORT
ACCOUNT ASSIGNMENT GROUP OF MATERIAL

Z1 – TRADING GOODS
Z2 – FINISHED GOODS
ACCOUNT KEY
ERL – SALES REVENUE (PR00)
ERS – SALES DEDUCTIONS (K004, K00, K007)
APP COND CHART SALES A/C.AS A/C.AS A/C G/L.

LIC TYPE OF A/C ORGN CUST MATER KEY A/C
V KOFI INT 1000 01 Z1 ERL 11111
V KOFI INT 1000 01 Z1 ERS 22222
84
V KOFI INT 1000 01 Z2 ERL 33333
V KOFI INT 1000 01 Z2 ERS 44444
V KOFI INT 1000 02 Z1 ERL 55555
V KOFI INT 1000 02 Z1 ERS 66666
V KOFI INT 1000 02 Z2 ERL 77777
V KOFI INT 1000 02 Z2 ERS 88888

APP COND CHART SALES A/C.AS A/C.AS A/C G/L.
LIC TYPE OF A/C ORGN CUST MATER KEY A/C
V KOFK INT 1000 01 Z1 ERL 11111
V KOFK INT 1000 01 Z1 ERS 22222
V KOFK INT 1000 01 Z2 ERL 33333
V KOFK INT 1000 01 Z2 ERS 44444
V KOFK INT 1000 02 Z1 ERL 55555
V KOFK INT 1000 02 Z1 ERS 66666
V KOFK INT 1000 02 Z2 ERL 77777
V KOFK INT 1000 02 Z2 ERS 88888
NOTE: - Creating account assignment groups of customer and material

SPRO


BASIC FUNTIONS



CHECK MASTER DATA RELEVANT FOR ACCOUNT ASSIGNMENT
A). MATERIALS: ACCOUNT ASSIGNMENT GROUPS: -

Go to new entries and create the required account assignment group of material.
NOTE: - This value has to be specified in the required material master on the sales
organization to view
B). CUSTOMERS; ACCOUNT ASSIGNMENT GROUPS; -

Go to new entries and create the required account assignment group of customer.
NOTE: - This value has to be specified in the required customer master.
85
NOTE: - Before assigning the G/L accounts, first we have to maintain the
condition technique for revenue account determination procedure. For this go to
SPRO


BASIC FUNCTIONS


1). Define dependencies of revenue account determination  account
determination create tables.
2). Define access sequences and account determination types
a). Maintain access sequences for account determination.
Create an access sequences and place the required condition tables in it.
b). Define account determination types.
We need to define two condition types with the corresponding access sequence
where one of them must be used for finance purpose and the other is for
controlling.
3). Define and assign account determination procedures.
a). Define account determination procedures.
Define a procedure and place both the condition types in it.
While placing the condition types in the procedure we specify the same step
number with different counters.
For the condition types entered in the procedure we have to assign the requirement.
The condition type with requirement “3” will be used with out controlling and the
condition type with requirement “2” will be used with controlling.
b). Assign account determination procedure
Select the required billing types and assign the procedure.
NOTE: - If required we can create over own account keys. For this go to
SPRO


BASIC FUNCTIONS


86

DEFINE AND ASSIGN ACCOUNT KEYS
Define account key go to new entries and create
OUT LINE AGREEMENTS

SCHEDULING AGREEMENT: -
It’s an out line agreement with a customer containing the delivery dates and
quantities. Those are entered has schedule lines in the delivery schedule we can
create these schedule lines while creating the agreement or later also.
We full filled a scheduling agreement in exactly the same way has we prose’s a
normal delivery. After we have carried out the delivery, the system
Automatically up dates the field “delivered quantity” in the scheduling agreement
item with the delivery quantity.
CONTRACTS: -
These are the out line customer agreement that display when the sales materials or
services are sold with in a curtain time period.
1). QUANTITY CONTRACTS: -

It’s an agreement that the customer will order a curtain quantity of product during a
specified period. The contact contains basic quantity and price information but
dose not specify the delivery dates or quantities, because a contract dose not
contain schedule line.
2). VALUE CONTRACT: -

It’s a contractual agreement with the customer that contains the materials that they
may receive with in a curtain time period and up to a target value. The value
contract can contain curtain materials or a group of materials called assignment
module.
3). SERVICE CONTRACT: -

It’s an agreement that contains the conditions for a curtain service to the customer.
We can manage rentals and maintenance contracts in the standard SAP system.
4). MASTER CONTRACT: -
87
It’s a document in which we can group the contracts has a lower level contract so
that the general term specified in the master contract by default applies for all the
lower level contracts.
CREATING SCHEDULING AGREEMENT

SPRO


SALES

SCHEDULING AGREEMENT

VA31 Create
AGREEMENT TYPE IS – DS
While creating the agreement we have to specify the description, and validity
periods along with the other required data.
While creating the scheduling area, for each item we have to specify the delivery
dates and the corresponding quantities in the schedule line data of that item.
NOTE: - For ‘‘DS”

1). DOCUMENT CATEGORY IS – E
2). SCREEN SEQUANCE GROUP IS – LP
3). TRANSACTION GROUP IS – 3
4). DELIVERY TYPE IS – LF
5). BILLING TYPE IS – F2
NOTE: - The item category is “LPN”

LPN is same has TAN except the incompletion procedure.
NOTE: - The schedule line category is same has that of “OR”
CREATING CONTRACTS: -
SPRO

88

SALES

CONTRACT

VA41 Create
1). CONTRACT TYPE: – QC – QUANTITY CONTRACTS – NMS.

NOTE: - For QC
A). DOCUMENT CATEGORY IS – G,
B). SCREEN SEQUANCE GROUP IS – LP
C). TRANSACTION GROUP IS – 4
No shipping and billing data has to be specified.
NOTE: - The item category “KMN”

For “KMN” we must not check the field schedule line allowed the completion rule
is set to “C”. It’s not relevant for billing but relevant for pricing.
2). VALUE CONTRACT GENERAL: - “WK1”

NOTE: - FOR WK1,
A). DOCUMENT CATEGORY IS – G,
B). SCREEN SEQUANCE GROUP IS – WK
C). TRANSACTION GROUP IS – 4
No shipping and billing data has to be specified.
NOTE: - The item category is “WKN”
For WKN we must not check the field schedule line allowed.
Completion rule is set to – E
It’s not relevant for billing but relevant for pricing.
We have to check the field order quantity = 1
NOTE: - For creating this contract we must have assortment module.

For creating the assortment module go to
LOGISTICS


MASTER DATA

PRODUCTS
89

VALUE CONTRACT ASSORTMENT MODULE

WSV2 CREATE
Enter the required materials in the assortment module and save it.
3). MATERIAL RELEVANT CONTROL: - “WK2”

This contract is created by specifying the required materials rather the assortment
module.
NOTE: - “WK2” is same has “WK1” except the screen sequence group which is
“WK1”
NOTE: - The item category is “WKN”.
4). SERVICE AND MAINTANENCE CONTRACT: - “SC”

NOTE: - FOR “SC”
A). Document categories are – “G”.
B). Screen sequence group is - “VT”.
C). Transaction group is - “4”.
D). No shipping has to be specified.
E). the billing type is – F2
NOTE: - Item category is “WVN” is same has “KMN”. A part from that “WVN” is
relevant for billing.
5). MASTER CONTRACT: - “GK”

NOTE: - FOR “GK”
A). Document category is – “Q”
B). Screen sequence is - “GK”
C). Transaction group is - “4”
D). No shipping and billing data has to be specified.
ITEM CATEGORY DETERMINATION FOR

(agreements & contracts)
Sale doc type Item cat grp Usage Hl lv it cat Default it cat
DS NORM - - LPN
QC NORM - - KMN
WK1 NORM - - WKN
90
WK2 NORM - - WKN
SC DIEN - - WVN
SPECIAL SALES ORDER

CS – CASH SALE
RO – RUSH ORDER
CASH SALES: -
In a cash sale transaction the customer orders, picks and pays for the goods
immediately. The delivery is process as soon as the order is saved and the billing is
related to order.
CREATING CASH SALES: -

VA01 CREATE, ORDER TYPE IS – CS.
Enter the required data and save the cash sale order.
NOTE: -
1). When we save the cash sale order the system automatically creates the delivery.
for this we have to specify the value “X” (create delivery immediately, if quantity
conformed for today) for the field immediately “in the definition of document type
CS”.
2). While creating the cash sale order the requested delivery date must be the
current date. For this we must not specify any “lead time in days” in the definition
of “CS”.
3). The items in the cash sale transaction or not relevant for credit processing. For
this we must not check the field “credit active” in the corresponding item category
“BVN”
RUSH ORDER: -
In a rush order transaction the goods are delivered on the same days as the order is
processed and is relevant for credit processing the delivery is processed as soon as
the order is saved and the billing is related to delivery.
CREATING RUSHE ORDER: -

VA01 CREATE, ORDER TYPE IS “RO”
NOTE: -
1). For the system to automatically create the delivery while saving the rush order
we have to specify the value “X” for the field immediate delivery in the definition
of “RO” and must not specify any lead time in days
2). The items in this transaction or relevant for credit processing. So we can use the
item category “TAN” where credit active is check.
91
IMMEDIATE DELIVERY CREDITS
OR  
CS  
RO  
NOTE: - Has the contract does not have schedule line, we need to create an order
against the contract, called “RELEASE ORDER” and carry out the delivery and
billing against that release order.
INCOMPLETION PROCEDURE
Depending on the requirement we need to make the required fields has mandatory
in the transaction for this we need to define an incompletion procedure in which
we have to place all those fields that are to be made mandatory and then assign that
procedure to the required transaction.
For defining the incompletion procedure (GO TO)
SPRO


BASIC FUNCTIONS

92
LOG OF INCOMPLETION ITEM

DEFINE INCOMPLETENESS PROCEDURE
We can define the incompletion procedures for the following incompletion groups.
A). SALES – HEADER
B). SALES – ITEM
C). SALES – SCHEDULE LINE
D). PARTNER
F). SALES ACTIVITY
G). DELIVERY HEADER
H). DELIVERY ITEM.
Select the required incompletion group and go to “PROCEDURES”.
Get the screen in to change mode. Go to new entries and create a procedure select
the created procedure and go to fields. Go to new entries and entered the required
fields in the procedures that are to be mandatory.
1). TABLE: - Specify the data base table in which the field exists.
2). FIELD NAME: - Specify the technical name of the field.
3). DISCRIPTION: - Specifies the description of the field which will be

automatically determined by the system.
4). SCREEN: - Specifies the screen on which the user can enter the missing data.
5). STATUS GROUP: - Specifies the corresponding status group of the field.
6). WARNING: - If we check this field, the system gives a warning message if the
user does not make the entry for the mandatory field.
7). SEQUENCE: - Specifies the order in which the system checks the mandatory
field in the corresponding transaction.
(SAVE THE PROCEDURE)
NOTE: - Like this we need to define the incompletion procedures for all the
incompletion groups and assign them to the corresponding transactions. For this
assignment go to  Assign incompleteness procedures.
93
STATUS GROUP: - The status group specifies which sub sequent transactions can
be blocked for processing if the mandatory field is missing the data. For define in
this go to  Define status groups.
Go to new entries and define.

Status General Delivery Billing Price Goods Picking Put pack
group Document Movement Away

In the above example the system automatically blocks the billing document if the
mandatory field to which this status group is assigned is missing the data.
COPYING CONTROLS
When we create the documents with reference, the system copies the data from the
reference document to the sub sequent document. For this we have to configure the
copying controls between those documents.
Ex: - QT OR
`
HEADER (QT – OR) HEADER
`
`
ITEM CATEGORY (AGN – TAN) ITEM CATEGORY
SCHEDULE LINE (BN – CP) SCHEDULE LINE
I). COPYING CONTROL FOR SALES DOCUMENTS: -

SPRO


SALES

MAINTAIN COPY CONTROL FOR SALES DOCUMENT
1). COPYING CONTROL: S. DOCUMENT TO S. DOCUMENT
94
A). HEADER LEVEL: - At this level we need to specify the copying
requirements and data transfer routines.
The copying requirements specify which conditions must be satisfied for the
system to copy the data from the source document to target document.
The data transfer routines specify which data has to be copied from the source to
target document. For example the routines “51, 101, & 1” are used to copy the
general data, business data & partner data respectively at header level.
If we check the field “copy item number”, the system copies the item numbers for
materials from the source to target document.
If we check the field “complete reference”, the source document will be
completely copied in to target document.
B). ITEM CATEGORY: - Here also we need to specify copying requirements and
data transfer routines. For example the routines “151,
102, 2 & 251” are used to copy the general data, business data, partner data &
conditions respectively at item level.
COPY SCHEDULE LINE: - If we check this field, the schedule line data will be
copied from the source to target document.
UP DATE DOCUMENT FLOW: - When we create the documents with reference,
the system forms a flow of documents in which if we know one document number,
with the help of “DISPLAY DOCUMENT FLOW” we can see all other document
numbers that are created with reference. For this we have to specify the value “X”
(create document flow records) for this field while maintaining the copying
controls between those documents.
DO NOT COPY BATCH: - If we check this field, the batch number of the item
will not be copy from the source to target document.
PRICING TYPE: - Specifies weather and how the system treats the pricing data
while copying it from the source to target document.
C). SCHEDULE LINE: - Here also we need to specify the copying requirements
and data transfer routines, for example the routine 201 is used to copy the schedule
line data.
I). COPYING CONTROL: B. DOCUMENT TO S. DOCUMENT
BILLING DOCUMENT SALES DOCUMENT

F2 (INVOICE) CR
F2 (INVOICE) DR (debit memo request)
F2 (INVOICE) RK (in voice correction request)
NOTE: - Here we need to maintain the copying controls only at header item levels
because a billing document does not have schedule lines.
95
II). COPYING CONTROLS FOR DELIVERY DOCUMENTS: -
SPRO

LOGISTICS EXECUTION

SHIPPING

COPY CONTROL

SPECIFY COPY CONTROL FOR DELIVERIES
EX: - SALES DOCUMENT DELIVERY DOCUMENT

OR LF
RO LF
CS BV
RE LR
DS LS
NOTE: - Here we need to maintain the copying controls at header and item levels
only because a delivery document does not have schedule lines.
III). COPYING CONTROLS FOR BILLING DOCUMENTS

SPRO


BILLING

BILLING DOCUMENTS

MAINTAIN COPYING CONTROL FOR BILLING DOCUMENTS
96
1). COPYING S. DOCUMENT TO B. DOCUMENT
EX: - SALES DOCUMENT BILLING DOCUMENT

OR F1
CS BV
RE RE (credit for returns)
CR G2 (credit menu)
DR L2 (debit menu)
RK G2
2). COPYING CONTROL: D. DOCUMENT TO B. DOCUMENT

EX: - DELIVERY DOCUMENT BILLING DOCUMENT
LF F2
LD F2
3). COPYING CONTROL: B. DOCUMENT TO B. DOCUMENT

EX: - BILLING DOCUMENT BILLING DOCUMENT
F2 F2
F2 L2
F2 S1 (in voice cancellation)
L2 S1 (in voice cancellation)
G2 S2 (credit memo cancellation)
NOTE: - For all the billing documents we need to maintain the copying controls at
header and item levels only because the billing document does not have schedule
lines.
POSTING STOCK IN THE PLANT

Go to “MB1C”
Specify the movement type “561”
Specify the plant and the storage location in which the stock has to be posted &
enter.
Specify the required material and the corresponding quantity to be posted.
Select the icon post & save.
NOTE: - During the stock posting if we get the following errors resolve them by
using the solutions given.
97
ERROR – 1: - Posting is only possible in the period -----------------------------
SOLUTION: - Closing the posting periods go to  “MMPV”
ERROR – 2: - No plant parameters are maintained.

SOLUTION: - SPRO


INVENTORY MANAGEMENT AND PHYSICAL INVENTORY

PLANT PARAMETERS
ERROR – 3: - No stock posting is possible for the material.
SOLUTION: - Go to “OMS2”
Select the required material type and go to quantity and value updating.
Select the required valuation area and check the field’s quantity up dating and
value updating.
ERROR – 4: - Account determination entry -------- is not possible.
SOLUTION: - During the stock posting the cost of the material will be posted to
the corresponding G/L accounts. For this we need to assign the G/L account to the
combination of transaction key, chart of accounts, valuation modification,
valuation grouping code and valuation class. In this combination valuation
grouping code is one element that has to be assigned to the valuation area with out
which the system cannot post the cost of the material to the corresponding G/L
account with out which the system will not allow you to post the stock.
For this assignment of valuation grouping code to valuation area
Go to “OMWD” that is the transaction code.
Select the required valuation area and assign 0001.
ERROR – 5: - Opening the period.
Solution – A). Assigning posting period variant to company code

Go to “OBBP” Select the required company code and assign the variant ooo1 or
1000.
B). To open the period.
98
Go to “OB52” select the required variant and specify the current year for all the
account types in the second and fourth columns of year.
ERROR – 6: - Creating G/L accounts.

Go to “FS00” from the main menu select settings
 HIGHER or KEY DISPLAY
Select the option  Display accounts in navigation tree again go to “FS00”.
Select the icon “change company code” and specify the standard company code
“0001 or 1000”
Find the required G/L account and select the icon copy. Specify the required
company code to which it has to be copied (enter) and save the G/L account.
ERROR – 7: - While creating the G/L account if we get the error regarding “field’s
status variant”,
Go to  SPRO


ACCOUNT RECIEVABLE AND ACCOUNTS PAYABLE

BUSINESS TRANSACTIONS

OUT GOING IN VOICES AND CREDIT MEMO’S

CARRY OUT AND CHECK DOCUMENT SETTING

ASSIGN COMPANY CODE TO FIELD STATUS VARIANT
Select the required company code and assign the variant “0001 (or) 1000”.
ERROR – 8: - While creating the G/L account “if we get the error” the G/L
account is blocked for creation in chart of accounts.
SOLUTION: - Go to “FSP0” Select the icon change chart of accounts and entered
the required G/L account and select icon block.
De check the option blocked for creation and save it.
ERROR – 9: - No direct posting is possible to the G/L account.
99
SOLUTION: - Go to “FS00” find the required G/L account and select the icon
change.
Select the tab page create/bank/interest, and check the field post automatically
only.
ERROR – 10: - Creating number range for material documents
SOLUTION: - Go to “FBN1”
NOTE: - To see the list of material documents go to “MB51”
ERROR – 11: - No number range is maintained for the transaction / event.
SOLUTION: - Go to “OMBT”
Select the button change groups.
Select the required events (WA or WE) and the main menu
Select intervals  maintain.
Place the cursor in the column year and from the main menu
Select edit  insert year and create the required number range for the required
year.
NOTE: - To check these stocks in the plant go to “MMBE”.

(STOCK OVER VIEW)
SHIPPING
Shipping point it specifies the location from which goods are delivered to the
customer. Depending on the requirement we can have multiple shipping points for
a company.
Defining shipping point: -
SPRO

100

DEFINATION

LOGISTICS & EXCLUSION

DEFINE COPY DELETE CHECK SHIPPING POINT

COPY DELETE CHECK SHIPPING POINT
Make a copy from an existing shipping point to the required new shipping point.
Come back to the previous screen and go to define and shipping point.
Select the defined shipping point and go to details.
Specify the factory calendar.
Specify the required lead times.
Select the address icon and specify the required data.
(SAVE IT)
ASSIGN SHIPPING TO PLANT: -

SPRO


ASSIGNMENT


ASSIGN SHIPPING POINT TO PLANT
Select the required plant and select the button assign.

From the list of shipping points
Select the required one’s and plant.
NOTE: - The relation between plant and shipping point is “many to many”.
SHIPPING POINT DETERMINATION

corresponding shipping point for each item.
For this the following setting must be done
SPRO

101

SHIPPING


ASSIGN SHIPPING POINTS
Go to new entries and assign the shipping point to the combination of shipping
conditions, loading group and plant.
NOTE: - During the shipping point determination what ever the shipping point that
is assigned as manual shipping point, with that we can replace the default shipping
point in the sales document.
DELIVERY
(With reference) (With out reference)

Single delivery with reference to single order
Single delivery with reference to multiple orders (collective processing).
Multiple deliveries with reference to single order (partial deliveries).
CREATING A DELIVERY WITH REFERENCE TO ORDER

SPRO


SHIPPING AND TRANSPORTATION

102
OUT BOUND DELIVERY

CREATE

SINGLE DOCUMENT

VL01N – WITH REFERENCE TO SALES ORDER
1). SHIPPING POINT: - Specify the shipping point from which the order has to
be delivered.
2). SELECTION DATE: - Specify the delivery creation date.
3). ORDER: - Specify the order number for which the delivery document has to be
created.
4). FROM ITEM: -

TO ITEM: -
5). DELIVERY TYPE: - (keep blank)

NOTE: - While creating the delivery with reference, it’s not required to specify the
delivery type. Because it will be automatically determined by the system from the
definition of reference sales document type  (enter)
In the over view screen select the “picking” tab page where we find the pick
quantities as 0.
We need to pick the required quantity either from the plant or ware house
depending on the requirement.
Picking the quantity from the plant depends on the usage of batch numbers for the
material if the material is maintained in batches we need to pick the required
quantity by specifying the corresponding batch numbers.
If the material is not maintained in batches, we need to directly enter the required
pick quantity.
For picking the quantity from the ware house we need to create transfer order.
CREATING TRANSFER ORDER: -

Save the delivery document and from easy access menu select
103
LOGISTICS


SHIPPING TRANSPORTATION

PICKING

CREATE TRANSFER ORDER

LT03 SINGLE DOCUMENT (or)
In the delivery document over view screen from the main menu select sub sequent
functions  create transfer order.
(SAVE THE DELIVERY)
On the transfer order initial screen specify the ware house number from which we
need to pick the quantity and also specify the delivery document number for which
it has to be pick  (enter) . SAVE IT
The movement we reach the over view screen, the system picks the required
quantity and save the transfer order.
NOTE: - The delivery quantity in the out bone delivery will be copied has the
picking quantity in to transfer order.
Come back to the delivery document over view screen by using the transaction
code “VL02N” and select the picking tab page where we find the completely
picked quantity.
Select the button “post goods issue” which specifies that the goods are leaving the
company.
For example of post goods issue: -

1). The stock of the material will be reduced by the corresponding schedule
category.
For the system to reduce the stock we have to specify the movement type “601” in
the corresponding schedule line category.
104
2). The value changes will be posted to the balance sheet account in the inventory
accounting.
The post goods issue is automatically up dated in the document flow.
COLLECTIVE PROCESSING OF ORDER DUE TO DELIVERY
1). To combine multiple orders for a customer to create single delivery, we have to
check the field order combination in the required customer master.
2). To combine multiple orders for creating a single delivery, all those orders must
have same delivery date, shipping point and ship to party (ROUTE).
To combine multiple orders go to
LOGISTICS


SHIPPING AND TRANPORTATION

OUT BOUND DELIVERY

CREATE

COLLECTIVE PROCESSING OF DOCUMENTS DUE FOR DELIVERY

VL1OA SALES ORDERS (Delivery due list)
3). Specify the required shipping point, delivery creation date, ship to party and
select the icon execute.
4). The system gives the list of those sales orders that are to be delivered to the
specified ship to party on the specified date and from the specified shipping point.
5). Select the required orders to be combined and select the button create delivery
in back ground.
6). Select the icon log for delivery creation.
7). The system generates a group number which contains the delivery document
created.
8). To see the delivery document created by the system select the group number
and select the button documents.
9). For the delivery document created by the system we have to complete picking
and post goods issue.
CREATING PARTIAL DELIVERIES
105
To create partial deliveries for a customer, in the corresponding customer master
we have to specify the value “partial delivery allowed” for field partial delivery for
item.
We can create the partial deliveries in the following scenarios.
1). If the quantity ordered by the customer is conformed on different dates by the
system after checking the availability of material, we need to create partial
deliveries on those dates for the corresponding conformed quantities.
2). Even though the entire quantity is conformed on a single day, still we may
require to creating partial deliveries if the customer needs it. This can be done in
the following two ways.
A). While creating the delivery with reference to sales order, the system copies the
entire quantity in to delivery which we have to change as for the customers
requirement and complete the delivery with reference to same order the system
copies the remaining quantity in to delivery which again we have to change has for
the customers requirement and complete the delivery. Like this we need to create
the deliveries till the entire order quantity is delivered.
B). Rather changing the quantities in the delivery, we can directly entered the
required delivery dates with the corresponding quotation in the schedule line data
of the item in the sales order it self and then create the deliveries on those specified
dates with the corresponding quantities.
CREATING DELIVERY WITH OUT REFERENCE
LOGISTICS


SHIPPING AND TRANSPORTATION

OUT BOUND DELIVERY

CREATE

SINGLE DOCUMENT

VL01NO WITH OUT ORDER REFERENCE
Specify the shipping point.

Specify the delivery type “LO” (it’s mandatory)
Specify the sales area.
106
In the over view screen specify the ship to party, planed goods issue dates material
and delivery quantity.
Complete the picking and post goods issue.
DEFINING DELIVERY TYPES

SPRO

LOGISTICS EXECUTION

SHIPPING

DELIVERIES

DEFINE DELIVERY TYPES
EXAMPLE: -
LF - code is delivery with reference to order.
LO - code is delivery with out reference.
LR - code is returns delivery.
BV - code is cash sale delivery.
NL - code is replenishment delivery (intra company sale).
NLCC - code is replenishment delivery (inter company sale).
FUNCTIONALITY OF A DELIVERY TYPES

1). DOCUMENT CATEGORY: - ****************************
2). NUMBER RANGE INTERNAL ASSIGNMENT: - ***********
3). NUMBER RANGE EXTERNAL: - ************************
4). ITEM NUMBER INCREAMENT: -************************
5). ORDER REQUIRED: - Specifies weather a reference document is required

for creating the delivery document.
6). ITEM REQUIRENMENT: - Specifies a requirements routine for a delivery

item that does not refer to the sales document. That item must meet the
requirements of that routine before it can be further process.
7). OUT PUT DETERMINATION PROCEDURE: - Specifies the
corresponding out put determination procedure of the delivery type.
107
8). OUT PUT TYPE: - Specifies the corresponding out put type of the delivery
type.
9). APPLICATION: - Specify the application “V2” for shipping document.
10). PARTNER DETERMINATION PROCEDURE: -*****************
11). STORAGE LOCATION RULE: - Specifies the rule with the help of which
the system automatically determines a storage location for the delivery item.
12). DELIVERY SPLIT WARE HOUSE NUMBER: - If we check this field, the
delivery can be split depending on the ware house number for creating multiple
transfer orders.
13). SCREEN SEQUENCE GROUP: - Specify “LF”.
14). DISPLAY RANGE: - Specifies weather the system displays all the items or
only main items in the delivery document.
SAVE THE DELIVERY TYPE
ITEM CATEGORY IN DELIVERIES

SPRO

LOGISTICS EXECUTION

SHIPPING

DELIVERIES

DEFINE ITEM CATEGORIES FOR DELIVERIES
What ever the item categories that we have in the sale documents (That are
relevant for delivery), again the same we have in the delivery document but with a
different functionality.
FUNCTIONALITY OF DELIVERY ITEM CATEGORY
108
1). DOCUMENT CATEGORY: -**********************************
2). CHECK QUANTITY: - Specifies weather and how the system reacts if the
delivery quantity of the item is “0”.
3). CHECK MINIMUM DELIVERY QUANTITY: - Specifies weather the

system checks the minimum delivery quantity specified in the material master or
customer material info record. If so it also specifies how the system reacts if that
minimum is not melt in the delivery document.
4). CHECK OVER DELIVERY: - Specifies weather and how the system reacts
if the delivery quantity of the item exceeds order quantity.
5). AVAILABILITY CHECK OFF: - Specifies weather the system carries out
availability check for the delivery item.
6). ROUNDING: - Specifies weather and how the delivery quantity of the item
will be rounded (No need to use).
7). RELEVANT FOR PICKING: - Specifies weather the delivery item is relevant
for picking.
NOTE: - Curtain items such has the returns or not relevant for picking so we must
not check this field in that corresponding item category “REN”.
8). STORAGE LOCATION REQUIRED: - If we check this field, the storage

location becomes mandatory for the delivery item before it can be further
processed.
9). DEFINE STORAGE LOCATION: - If we check this field, the system

automatically determines a corresponding storage location for the delivery item.
10). DON’T HECK STORAGE LOCATION: - If we check this field, the system
will not run a check for the storage location entered for the delivery item.
11). NO BATCH CHECK: - If we check this field, the system will not run a
check for the batch number entered for the delivery item (de check).
109
12). AUTOMATICALLY BATCH NUMBER: - If we check this field, the
system automatically determines a corresponding batch number for the delivery
item. (SAVE THE ITEM CATEGORY)
NOTE: - If the delivery item is created with out reference, the system determines
the item category “DLN”.
13). ITEM CATEGORY DETERMINATION IN DELIVERY: - While creating

the delivery the system automatically determines an item category for the item. For
this the following setting must be done.
Go to
SPRO

LOGISTICS EXECUTION

SHIPPING

DELIVERIES

DEFINE ITEM CATEGORY DETERMINATION IN DELIVERY
For those delivery item created with reference, the item category determination is
not required, because the item category will be copied from the reference sales
document to delivery document.
But for those delivery item created without reference, the item category
determination has to be done where we have to assign the item category to the
combination delivery type, item category group. Usage and higher level item
category.
110
CROSS SELLING
It’s a sales practice where the customers are offered additional merchandise to what
they ordered in a effort to increase the sales volume.
CONFIBARING CROSS SELLING: -

SPRO


BASIC FUNCTIONS

CROSS SELLING

DEFINE DETERMINATION PROCEDURE FOR CROSS SELLING
1). CREATE CONDITION TABLES: - Create the required condition table with
the corresponding key field.
2).MAINTAIN ACCESS SEQUENCE: - Create an access sequence and place the
required condition tables in it.
3). DEFINE CONDITION TYPES: - Create a condition type and assign the
corresponding access sequence.
4). MAINTAIN PROCEDURE: - Define a procedure and place the required
condition type in it.
CROSS SELLING PROFILE: - The cross selling profile specifies how the cross
selling materials are to be displayed in the sales document.
For defining these go to.
SPRO


BASIC FUNCTIONS

CORRESPONDING

DEFINE AND ASSIGN CROSS SELLING PROFILE

DEFINE CROSS SELLING PROFILE
111
Go to new entries enter the cross selling materials will be automatically proposed
by the system or we have to manually retrieve them in the sales document.
CROSS SELLING “ATP” INDICATOR: - If we check this field, the system

carries out availability check for the cross selling materials in the sales document.
(SAVE THE PROFILE)
CREATING CUSTOMER AND DOCUMENT PROCEDURE FOR

CROSS SELLING
SPRO


BASIC FUNCTIONS

CROSS SELLING

MAINTAIN CUSTOMER AND DOCUMENT PROCEDURE FOR CROSS
SELLING
A).DEFINE PROCEDURE FOR CROSS SELLING: - Go to new entries and

create.
NOTE: - This value has to be specified in the required customer master for the
field “customer procedure for product proposal”.
(SALES AREA DATA VIEW AND SALES TAB PAGE)
B). DEFINE DOCUMENT PROCEDURE FOR CROSS SELLING: - Go to

new entries and create.
NOTE: - This value has to be assigned to the required sales document type. For
this assignment go to
112
C).ASSIGN DOCUMENT PROCEDURES FOR CROSS SELLING TO
DOCUMENT TYPES ASSIGN THE CROSS SELLING PROFILE: -
Go to
SPRO


BASIC FUNCTIONS

CROSS SELLING

DEFINE AND ASSIGN CROSS SELLING PROFILE

ASSIGN CROSS SELLING PROFILE
Go to new entries and assign the profile to the combination of sales organization,
distribution channel, division, customer procedure for cross selling and document
procedure for cross selling.
D). MAINTAINING CONDITION RECORDS FOR CROSS SELLING
LOGISTICS


MASTER DATA

PRODUCTS

CROSS SELLING

VB41 CREATE
Specify the condition type for cross selling.
Select the required key combination.  (Enter)
113
MAINTAIN THE CONDITION RECORD BY SPECIFY THE DATA FOR
THE FOLLOWING FIELDS
1). MATERIAL: - Specify the material for which the cross selling materials or
offered.
2). MATERIAL: - Specify the materials offered in cross selling materials are
offered.
3). CROSS SELLING DELIVERY CONTROL: - Specifies weather the cross

selling can be delivered regardless of main item or in conjunction with the main
item.
To specify multiple materials for cross selling, select the record and select the icon
alternative materials. (SAVE THE RECORD)
NOTE: - When we create sales order for the main item the system automatically
proposes the cross selling materials. If we need to manuals retrieve them, select the
line item and select the icon cross selling products.
BILLING
CREATING INVOICE: -
LOGISTICS


BILLING

BILLING DOCUMENT

VF01 CREATE
1). For this field “document” specify the reference document number for creating
the invoice and select the icon execute.
2). The entire data will be copied from the reference document to invoice and
“save the invoice”.
114
NOTE: -
1). The reference document for creating the billing document is controlled by item
category with the field billing relevance.
2). While creating the billing document it’s not required to specify the billing type
it will be automatically determined by the system from the definition of reference
sales document type.
NOTE: -
1). When we save the billing document the values from that document will be
automatically posted to the respective G/L accounts.
2). When we save the invoice the companies revenue account will be credited and
the customers account debited by with respective amounts.
For this the movement we save the invoice the system automatically generates a
document called accounting documents which is posted to finance.
3). To see the accounting document generated by the system, select the button
“accounting” from the initial or over view screen of the invoice created.
4). The system generates the following documents.

A. Accounting document.
B. Profit center document
C. profitability analysis POSTED TO “CO – PA”
D. special purpose ledger Controlling and Profitability analysis
E. Controlling document
Go to the details of accounting document.

The accounting document type is “RV”.
Data in the accounting documents
1). ITEM: - Specifies the number of records (accounts) in the accounting

document. The first record is always for payer.
2). PK (posting key): - The posting key specifies weather the account is credited
or debited.
In the case of invoice it is “01” for the payer account to debit that accounts is “50”
for the companies revenues account to credit that account where has it is forty for
the companies deductions account to debit that account.
3). ACCOUNT SHORT TEXT: - Specifies the description of the account.
115
4). TX (tax code): - Specifies the tax code of the country.
5). AMMOUNT: - Specifies the amount posted to the corresponding account.

NOTE: - For the system to generate the accounting document we have to configure
revenue account determination procedure and we also need to specify the
reconciliation account number in the master record of payer.
In the accounting document the system displays the reconciliation account number
in the details of payer record.
NOTE: - When we save the invoice if the system has not generated the accounting
document, we can check the reason for that in the following ways.
1). In the billing document over view screen from that main menu select
environment  account determination analysis  revenue accounts.
Here the system displays the condition types for which the G/L accounts are
determined.
2). Go to “VF02” specify the billing document numbers from the main menu select
bulling document  release to accounting (FBN1) is number range.
116
INVOICE CANCELLATION
LOGISTICS

SALES AND DIDTRIBUTION

BILLING

BILLING DOCUMENT

VF11 CANCEL
For this field document specify the invoice number to be cancelled and select the
icon execute.
Go to the details of invoice cancellation and (SAVE IT).
NOTE: -
When we save the invoice cancellation the system automatically generates and
accounting document which is posted to finance where those values that are
already posted to the corresponding G/L accounts during the invoice creation will
be reverted.
The accounting document type is “AB” and the posting key for the payer is “12”
where has it is “40” for the companies revenues account and “50” for the
deductions account.
SALES SOCUMENT DELIVERY DOCUMENT BILLING DOCUMENT
OR LF F2
`
RE LR RE Credit for returns
CR Credit meme request G2 Credit memo
Debit memo request Debit memo

DR L2
117
CREDIT MEMO: -
Because of any reasons if the company has to pay some amount back to the
customer, we have to create the billing document credit memo for this the
reference sales document is credit memo request.
CREATING CREDIT MEMO REQUEST: -

“VA01” create order type is “CR” (IF IT IS SD 4.7 VERSION “G2”) enter the
required data like “customer, material, target quantity” etc.
Specify the order reason.
Remove the billing block if any and (SAVE THE DOCUMENT).
NOTE: -
For “CR”
Document category is “K”.
Screen sequence group is “GA”.
Transaction group is “0”.
No shipping data has to be specified. (Leave it blank)
The corresponding billing type is “G2”.
ITEM CATEGORY: -
The item category is “G2N”. For “G2N” we must not check the field schedule line
allowed.
It is relevant for billing where billing relevant is set to see it relevant for pricing.
We have to check the field returns.
CREATING CREDIT MEMO: -

“VF01” create for the field documents specify the credit memo request number and
execute. The entire data will be copied from credit memo request to credit memo
and (SAVE IT).
NOTE: -
When we save the credit memo, the system automatically generates and accounting
document which is posted to finance where the Companies
revenue account is debited and the customers account is credited.
The accounting document type is “RV” and the posting key for the payer is “11”
where has it is “40” for the companies revenues account.
CREDIT MEMO CANCELLATION: -

Go to “VF11” for the field document specify the credit memo number and execute.
Go to the details of credit memo cancellation and SAVE IT.
118
NOTE: -
When we save the credit memo cancellation, the system automatically generates an
accounting document which is posted to finance where those values that are
already posted to the corresponding accounts during the credit memo creation will
be reverted.
The accounting document type is “AB” and the posting key for the payer is “02”
where has it is “50” for the company revenues account.
DEBIT MEMO
Because of any reasons if the customer has to pay some access amount to the
company, we have to create the billing document debit memo. For this the
reference document is debit memo request.
CREATING DEBIT MEMO REQUEST: -

“VA01” create order type is “DR” (in 4.7 – L2)
Creating debit memo request is absolutely same has credit memo request.
NOTE: - For “DR” document category is “L”.
Transportation group is “0”.
No shipping data has to be specified.
The billing type is “L2”.
NOTE: - The item category is “L2N”.
“L2N” is same has “G2N” accept the field returns which must not be check.
CREATING DEBIT MEMO: -

“VF01” create.
For the field document specify the debit memo request number and execute.
The entire data will be copied from debit memo request to debit memo.
“SAVE IT”
NOTE: - When we save the debit memo, the system automatically generates an
accounting document which is posted to finance where the companies account is
revenue in credit and the customers account is debited.
The accounting document is same has that of invoice.
NOTE: - Debit memo cancellation is same as invoice cancellation.
119
DEFINING BILLING TYPES: -
SPRO


BILLING

BILLING DOCUMENTS

DEFINE BILLING TYPES

DEFINE BILLING TYPES
EX: - F1.F2 – INVOICE.
BV – CASH SALE INVOICE
F5 – PRO FARMA INVOICE FOR ORDER
F8 – PRO FARMA INVOICE FOR DELIVERY
G2 – CREDIT MEMO
L2 – DEBIT MEMO
S1 – INVOICE CANCELLATION
S2 – CREDIT MEMO CANCELLATION
SV – CASH SALE INVOICE CANCELLATION
FUNCTIONALITY OF BILLING TYPE: -
1). Number range internal assignment.
2). Item number increment.
3). Document category.
4). Transaction group.
5). Negative posting: - Specifies the weather the negative posting is allowed for
the billing document type.
6). Posting block: - If we check the field, the automatic transfer of billing
document to the accounting will be block.
120
NOTE: - We can manually release the document to accounting in the following
way.
Go to “VF02” specify the billing document numbers and from the main menu
select the billing document  release to accounting.
RELEVANT FOR REBATE: - If we check this field the billing document type
become relevant for rebate processing.
CANCULLATION BILLING TYPE: - Specifies the corresponding cancellation

type of the billing document.
ACCOUNT DETERMINATION PROCEDURE: - Specifies the corresponding

revenue account determination procedure.
OUT PUT DETERMINATION PROCEDURE: - Specifies the corresponding

out put determination procedure of the billing type. (V10000)
APPLICATION: - “V3”.
OUT PUT TYPE: - Specifies the corresponding out put type of the billing
document. (RD00)
HEADER PARTNER: - Specifies the corresponding partner determination

procedure for the billing document header. (FK)
ITEM PARTNERS: - Specifies the corresponding partner determination

procedure for the billing document item.
TEXT DETERMINATION PROCEDURE: - Specify the corresponding text

determination procedure for the billing document header. (FP)
TEXT DETERMINATION PROCEDURE ITEM: - Specifies the corresponding

text determination procedure for the billing document item.
SAVE THE BILLING TYPE
121
THIRD PARTY SALES
In the 3rd party sales process the company does not delivery the items requested by
the customer. Instead we pass on the order to a 3rd party vendor who then ships the
goods directly to the customer and bills the company.
A sales order may consist partly or whole of 3rd party items.
AUTOMATIC 3RD PARTY ORDER PROCESSING: -
If a material is always delivered from the 3rd party vendors, we can specify that the
material is a 3rd party item by specifying the item category group “BANS” in the
material master record. During the sales order processing the system automatically
determines and appropriate item category for the 3rd party item which is “TAS”.
MANUAL 3RD PARTY ORDER PROCESSING: -
In the case of a material that we normally deliver or self but occasionally need to
order from the 3rd party vendors during the sales order processing we need to make
that item has a 3rd party item by changing the item category from “TANS to TAS”.
NOTE: - To create 3rd party sales process the following settings must also be done.
1).CREATING PURCHASING ORGANIZATION: -

SPRO


DEFINATION


MAINTAIN PURCHASING ORGANIZATION
Go to “new entries” create.
2). ASSIGNING PURCHASE ORGANIZATION TO COMPANY CODE: -
SPRO


DEFINATION


122
MAINTAIN PURCHASING ORGANIZATION TO COMPANY CODE
Select the required purchasing organization and assign the required company code.
3). ASSIGNING PURCHASING ORGANIZATION TO PLANT: -

SPRO


ASSIGNMENT


ASSIGN PURCHASING ORGANIZATION TO PLANT
Go to “new entries” and specify the required combination of purchasing

organization and plant.
4). CREATING THE VENDOR: -

LOGISTICS

MATERIALS MANAGEMANT

PURCHASING

MASTER DATA

VENDOR

CENTRAL

XKO1 CREATE
Specify the vendor number.
Specify the company code.
Specify the purchasing organization.
Specify the account group (0001).
For vendor – 160000 in reconciliation account. (FS00)
Specify the required data and SAVE THE VENDOR.
123
5). MAITAINING VENDOR INFO RECORD: -
LOGISTICS


PURCHASING

MASTER DATA

INFO RECORD

ME11 CREATE
Specify the vendor.
Specify the material. (3rd party item)
Specify the purchasing organization.
Specify the plant.
Specify the required data and SAVE THE RECORD.
6). MAINTAINING SOURCE LIST: -

LOGISTICS


PURCHASING

MASTER DATA

SOURCE LIST

ME01 MAINTAIN
rd
Specify the material. (3 party item)
Specify the plant  enter.
In over view screen specify the required vendor with the corresponding validity
period and SAVE THE RECORD.
124
7). While creating the material master record for the 3rd party item we must
maintain the data for the view purchasing along with the other required view with
item category “BANS”.
THE PROCESSING FLOW OF 3RD PARTY SALES
1). Create sales order for the 3rd party item. VA01” create enter the required data
and SAVE THE ORDER.
NOTE: -
1). When we save the sales order, the system automatically creates a purchase
requisition for the 3rd party item which is displayed in the corresponding schedule
line data of that item.
For the system to automatically create a purchase requisition for the 3rd party item,
we shall specify the document type “NB” for the field order type in the definition
of corresponding schedule line category of 3rd party item “CS”.
2). Assigning the “PR” to a vendor and creating “PO” go to “ME57”.

Specify the purchase requisition number, check the field “ASSIGNED
PURCHASE REQUISITIONS” and select the icon execute.
The system displays a record where it automatically retrieves a vendor. (FROM

SOURCE LIST)
Check the record and select button assignment over view.
Select the record and select the button process assignment where the system gives
a pop up box for creating “PO”  enter.
Drag and drop the “PR” number on the bosket.
The entire data will be copied from purchase requisition to purchase order.
(SAVE THE PURCHASE ORDER)
3). CREATING GOODS RECIEPT: -

Go to “MIGO”.
Specify the purchase order number and select the icon execute.
Check the field item “OK”.
Select the button post document.
125
4). CREATING INCOMING INVOICE: -
Go to “MIRO”.
Specify the purchase order number, invoice date  (enter).
Specify the required “AMOUNT” to make the “BALANCE” has “0”.
Select the button “SIMULATES”.
Select the required G/L account and select the button “POST”
5). CREATING CUSTOMER INVOICE: -

“VF01” create.
NOTE: - The invoice has to be created with reference to sales order.
NOTE: - When we create the invoice with reference to sales order, the quantity
must be determined from the incoming invoice. For this we must specify the value
“F” (order related billing document – status according to invoice quantity) for the
field billing relevance in the definition of corresponding item category of 3rd party
item “TAS”.
126
CONSIGNMENT SALES
CONSIGNMENT FILL UP PIECES
1). 1500
1000
COMPANY CUSTOMER
Pieces 500 1000
CONSIGNMENT ISSUE
200
2). 800 SALES
CUSTOMER
Pieces
3) CONSIGNMENT PICK UP
700
200 CUSTOMER
COMPANY
Pieces
4). CONSISIGNMENT RETURNS

100
CUSTOMER
100 SALES
Pieces
127
(3)CP
CP
CUSTOMER
200PC 1000PC (CF)
DISTRIBUTER
100PC
(CI) 2 2 2
(CR)
Sub dealer __ (1) 400 pc’s
Sub dealer __ (2) 250 pc’s
Sub dealer __
COMPANY (3) 150 pc’s
The consignment goods or the goods that are stored at the customer’s location but
are owned by the company the customer is not obliged to pay for these goods until
they are removed from the consignment stock.
Other wise he can usually return the goods which are not required.
THE PROCESS FLOW OF CONSIGNMENT SALES: -
There are four main transactions for carrying out the consignment stock processing
in the SAP system all of which support a separate management of stock. They are,
1). CONSIGNMENT FILLUP.
2). CONSIGNMENT ISSUE.
3). CONSIGNMENT PICKUP.
4). CONSIGNMENT RETURNS.
I). CONSIGNMENT FILLUP: - The consignment fill up is used to supplement

the customers consignment stock that is the stock is transferred to the customer’s
location but owned by the company.
CREATING CONSIGNMENT FILLUP: -
A). Create sales order “VA01” create.
128
The order type is (KB or CF).
Create the consignment fill up for the required quantity and save the order.
NOTE: - The document type “KB” is same has “OR” accept the billing data which
must not be specified.
NOTE: - The item category is “KBN” is not relevant for billing and pricing.
B). CREATE DELIVERY: -
Delivery type “VL01N” creates.
Complete the picking and post goods issue.
NOTE: - After completing the post goods issue the system creates a special stock
for the consigned customer. For this we have to specify the movement type “631”
in the corresponding schedule line category “E1”.
II).CONSIGNMENT ISSUE: -
The consignment issue enables the customer to take the goods from the
consignment stock for sales purpose.
It involves remove in the goods from the consignment stock and making them the
property of customer.
CREATING CONSIGNMENT IISUE: -
A). Create order – VA01create.
“OR” type is “KE or CI”.
Create the consignment issue for the required quantity to be sold and save the
order.
NOTE: - The document type “KE” is absolutely same has “OR” If we use the
document type “OR” it determines the item category “TAN” which in turn
determines the schedule line category “CP” where the movement type is “601”
which will reduce the main stock. But in consignment issue it is the special stock
that has to be reduced. For this we have to change the movement type for which we
have to change the schedule line category. For this we have to change the item
category because schedule line category is proposed by item category. To change
the item category we have to change the document type because item category is
proposed by document type.
NOTE: - The item category is “KEN” is same has “TAN”. A part from that the
“SPECIAL STOCK” indicator is set to “W” (consignment customer) for “KEN”.
B). CREATE DELIVERY: -

Delivery type “VL01N” Create.
This transaction is not relevant for picking so directly complete post goods issue.
NOTE: - To make a delivery item has not relevant for picking, we must not check
the field “RELEVANT FOR PPICKING” in the definition of corresponding
delivery item category.
129
NOTE: - After completing the post goods issue, the system reduces the special
stock by the corresponding delivery quantity.
For this we have to specify the movement type “633” in the definition of
corresponding schedule line category “CI”.
C). Create invoice: - “VF01” create.
III). CONSIGNMENT PICKUP: -

Any consignment goods that are left with the customer with out being sold can be
re posted to the company with a consignment pickup.
CREATING CONSIGNMENT PICKUP: -
A). CREATE ORDER: - “VA01” create.
Order type is “KA or CP”.
Create the consignment pickup for the required quantity to be taken back from the
customer and save the order.
NOTE: - The document type “KA” is same has the document type “KB” except the
delivery type which is “LR”.
NOTE: - The item category is “KAN” is same has “KBN”. A part from that we
have to check the field “returns for KAN”.
B). CREATE RETURNS DELIVERY: -

Delivery type “VL01N” Create.
This transaction is not relevant for picking so directly complete post goods receipt.
NOTE: - After completing the post goods receipt the special stock will be added to
the main stock in the plant. For this we have to specify the movement type “632”
in the definition of corresponding schedule line category “F1”.
IV). CONSIGNMENT RETURNS: -

The consignment returns are used if the customer wants to return the goods to the
consignment stock.
CREATING CONSIGNMENT RETURNS: -
A). Create order: - “VA01” create.
Order type is “CONR or CR”.
Create the consignment returns for the required quantity and save it.
NOTE: -The document type “CONR” is absolutely same has “RE”. If we use the
document type “RE”, it determines the item category “REN” which in turned
determines the schedule line category “DN” where the movement type is “651 or
653” where the stock is added to the main stock in the plant but in consignment
returns it must be added to the special stock.(so we cant use “RE”).
130
NOTE: - The item category is “KRN” is same has “REN”. A part from that the
special stock indicator is set to “W” for “KRN”.
B). CREATE RETURNS DELIVERY: -
Delivery type “VA01N” Create.
This transaction is also not relevant for picking so directly complete post goods
receipt.
NOTE: - After completing the post goods receipt the system create a special stock
for the concerned customer. For this we have to specify the movement type “634”
in the corresponding schedule line category “D0”.
C). CREATE THE CREDIT MEMO: - (credit for returns)

“VF01” Create.
NOTE: - After the consignment returns again we need to create consignment issue
if the customer wants to resale the special stock where has we need to create
consignment pick up if the customer wants to send it back to the company.
ITEM CATEGORY AND SCHEDULE LINE CATEGORY

DETERMINATION FOR CONSIGNMENT SALES: -
S.DOC ITEM USAG HL.LV

TYPE CATEGORY E IT.CAT
CONSIGNMET KB NORM - DEFAULT
FILL UP IT CATE
KE NORM - KBN MRP SC.LINE
CONSIGNMET
ISSUE TYPE CATEGOR
Y
CONSIGNMET KA NORM - KEN ND E1 (631)
PICKUP
CONSIGNMET KR NORM - KAN ND C1 (633)
RETURNS
KRN ND F1 (632)
ND D0 (634)
131
ITEM PROPOSAL
The frequently accruing material combinations and common delivery quantities
can be stored has item proposals. While creating the sales order we can copy the
required items from that item proposal. An item proposal can consist of materials
of different material types.
The order entry can be process more affectionately using item proposals.
CREATING ITEM PROPOSAL: -

LOGISTICS


MASTER DATA

PRODUCTS

ITEM PROPOSAL

“VA51” CREATE.
Specify the proposal type “PV”.
Specify the sales area  (enter)
In the over view screen specify the required materials with the corresponding
quantities and “save the item proposal”.
NOTE: - For “PV”
1). DOCUMENT CATEGORY IS “D”.
2). SCREEN SEQUENCE GROUP IS “MA”.
3). TRANSACTION GROUP IS “5”.
4). NO SHIPPING AND BILLING DATA HAS TO BE SPECIFIED.
132
NOTE: - After saving the item proposal we have to specify that number in the
customer master for the field “item proposal” on the sales tab page under the sales
area data view.
USING ITEM PROPOSAL IN SALES ORDER: -

After specifying the customer in the sales order view screen, select the icon
“possible items” where the system gives a pop up box in which it displays the item
proposal retrieved from the corresponding customer master.
Here we have options the following options

A). DEFAULT WITH OUT QUANTITY: -
If we select this button the system copies all the items from item proposal in to
sales order with out the quantities.
B). DEFAULT WITH QUANTITY: -

If we select this button the system copies all the items from item proposal with the
corresponding quantities.
C). SELECTION LIST: -

If we select this button, the system displays all the materials in the item proposal
from which we can copy the required materials with or with out quantities.
NOTE: -
If we want to create an item proposal for a “BOM” item, enter only the main item
with out the components,
At the time of copying the “BOM” item from “item proposal” in to sales order, the
system automatically retrieves the components.
133
DYNAMIC PRODUCT PROPOSAL
A product proposal is a list of products for a customer that is automatically
proposed during the sales document processing. We can determine our self which
materials should be displayed has product proposals in the sales document.
During the sales document processing the system displays a product proposal in
the item over view according to the customer and the business transaction.
The system does not run the standard checks like pricing availability check, free
goods determination etc. until we enter the order quantity.
The product acts both has an entry aid and also an aid to sales support and
promotions.
For example we can use the document history to analyses the customers
purchasing habits and recognize straight away if there behavior changes, for
instance when they suddenly stop ordering a product.
CONFIGURING DYNAMIC PRODUCT PROPOSAL: -

SPRO


BASIC FUNCTIONS

DYNAMIC PRODUCT PROPOSAL

MAINTAIN TABLE OF ORIGIN FOR PRODUCT PROPOSA
1).MAINTAIN TABLE OF ORIGIN FOR PRODUCT PROPOSAL

Here we need to specify different data sources for product proposal.
For ex: - A). ORDER HISTORY.
134
B). LISTING.
C). ITEM PROPOSAL.
D). CUSTOMER MATERIAL INFORMATION.
E). EXCLUSION.
2). DEFINE PRODUCT PROPOSAL PROCEDURE AND ACCESS

SEQUENCES.
A). Here we need to define two procedures for the product proposals. One is
“BACK GROUND PROCEDURE” which is used to determine the product
proposals from order history and the other is “ON LINE” procedure which is used
to determine the product proposals from the other data sources.
B). For each procedure we have to maintain access sequence where we have to
specify the corresponding function module for determining the product proposals.
C). For the back ground procedure we have to specify the function module
“SD__DPP__HISTORY” to determine the product proposal from order history.
D). In the online procedure we have to specify the function module

“SD__DPP__READ” for reading the product proposal from the data base. Below
to this we have to specify the following function modules for determining the
product proposal from the respective data sources.
SD__DPP__CUSTOMER__MATERIAL__INFO
SD__ DPP__EXCLUSION
SD__DPP__LISTING
SD__DPP__PRODUCT PROPOSAL
3). DEFINE CUSTOMER PRODUCT PROPOSAL.

Go to “new entries” and create.
NOTE: - This value has to be specified in the required customer master for the
field customer procedure for product proposal.
(SAVE THE AREA DATA VIEW AND SALES TEB PAGE)
4). DEFINE DOCUMENT PROCEDURE FOR PRODUCT PROPOSAL.

NOTE: - This value has to be assigned to the required sales document type for this
go to.
135
5). ASSIGN DOCUMENT PROCEDURE FOR PRODUCT PROPOSAL TO
SALES DOCUMENT TYPES.
6). MAINTAIN PROCEDURE DETERMINATION (IN BACK GROUND)

FOR PRODUCT PROPOSAL.
Go to “new entries” and assign the back ground procedure to the combination of
sales organization, distribution channel, division, and customer procedure for
product proposal.
7). MAINTAIN PROCEDURE DETERMINATION (ONLINE) FOR

PRODUCT PROPOSAL.
Go to “new entries” and assign the online procedure to the combination of sales
area, sales office (optional) sales group (optional) customer procedure
for product proposal and document procedure for product proposal.
NOTE: - For the system to determine the product proposal in to sales order we
have to schedule the report “generate product proposal” for back ground
processing.
For this go to
LOGISTICS


SALES

ENVIREMENT

“SDPV” GENERATE PRODUCT PROPOSAL
Specify the customer number, sales area and select the icon execute.
 USING PRODUCT PROPOSAL IN SALES ORDER: -

A). The movement we enter the customer in the sales order, the system calls up the
“function module” and determine the product proposals.
B). If we want to copy the quantities, we need to select the icon

“COPY PRODUCT PROPOSAL QUANTITY”
136
C). If we want to discard all the items in the product proposal, select the product
proposal active to inactive.
ROUTE DETERMINATION
1). TRANSPORTATION ZONE: -
It represents the reasons of delivery recipient and delivery shipper. We can define
the transportation zones according to the country and companies requirements.
For defining this go to: -

SPRO

LOGISTICS EXCLUSION

SHIPPING


ROUTES

ROUTE DETERMINATION

DEFINE TRANSPORTATION ZONES
Go to “new entries” and create a transportation zone for the required country.
2). MAINTAINING TRANSPORTATION ZONE FOR SHIP TO PARTY

In the customer master record we have to specify the transportation zone on the
address tab page under the general data view.
3). MAINTAINING TRANSPORTATION ZONE FOR SHIPPING POINT

In the shipping point definition we have to specify the transportation zone on the
“address” view.
4). TRANSPORTATION GROUP: - (material master)
137
5). DEFINING TRANSPORTATION CONNECTION POINTS
SPRO

LOGISTICS EXCLUSION

SHIPPING


ROUTES

DEFINE ROUTES

DEFINE MODES OF TRANSPORTATION
The mode of transport can be by air, by ship, byroad etc,
6). DEFINING TRANSPORTATION CONNECTION POINTS

SPRO

LOGISTICS EXCLUSION

SHIPPING


ROUTES

DEFINE ROUTES

DEFINE TRANSPORTATION CONNECTION POINTS
138
Go to “new entries”
The transportation connection point can be an air port or a train station or harbor or
inland port etc.
7). DEFINING ROUTE

SPRO

LOGISTICS EXCLUSION

SHIPPING


ROUTES

DEFINE ROUTES

DEFINE ROUTES AND STAGES
In the definition of the route we can specify the service agent, mode of transport,
distance, factory calendar, transist time, travel duration, transportation lead time in
days and hours, total allowed weight etc.
For each route we can maintain the corresponding stages and transportation
connection points
8). ROUTE DETERMINATION

A). IN SALES ORDER: -
In the sales order the system determines a route for each item. For this the
following settings must be done.
SPRO

LOGISTICS EXCLUSION

SHIPPING

139

ROUTES

ROUTE DETERMINATION

MAINTAIN ROUTE DETERMINATION
Go to “new entries” and specify the following data.

1). COUNTRY OF DEPARTURE (Country of shipping point)
2). DEPARTURE ZONE (Transportation of shipping point)
3). DESTINATION COUNTRY (Country of ship to party)
4). RECEIVING ZONE (Transportation zone of ship to party
Select the above entered combination and go to route determination with out
weight group (order)
Go to “new entries” and assign the route to the combination of shipping conditions
and transportation group.
B). IN DELIVERY: -
The shipping document type determines weather the route is redetermined in
delivery. Since we can only know the exact weight of group at the time of delivery,
it makes since to determine the route in delivery.
For ex: - An over deliver of goods could means that the delivery is now too heavy
to be delivered by flight and must be conversed by rail.
For this reason a “weight group” is used has an additional factor in determining
route in delivery. The weight group is determined on the basis of the total weight of
the delivery.
For creating the weight groups go to

SPRO

LOGISTICS EXCLUSION

SHIPPING
140


ROUTES

ROUTE DETERMINATION

DEFINE WEIGHT GROUPS
Go to “new entries” and create the weight groups.
After creating the weight groups, by using that we have to assign the route.
For this go to
SPRO

LOGISTICS EXCLUSION

SHIPPING


ROUTES

ROUTE DETERMINATION

MAINTAIN ROUTE DTERMINATION
Select the required combination of country of departure zone, destination country,

receiving zone and go to
“ROUTE DETERMINATION WITH WEIGHT GROUP” (Delivery)
Go to “new entries” and assign the route to the combination of shipping condition
transportation group and weight group.
NOTE: - Un like the sales order where each item can have its own route, all the
items in the delivery must have the some route.
141
TEXT DETERMINATION PROCEDURE
In a business relation ship it is essential that the business partner exchange the
information through out the logistics chain. In sales and distribution this exchange
of information is supported by text in the master records and documents.
The text can be used in many areas of sales and distribution.
For ex: - It can be a sales for customer, a sales text for material, explanations in
order confirmations, shipping instructions in delivery etc, we can define has many
text types has we require for master records and documents.
For this go to
SPRO


BASIC FUNCTIONS

TEXT CONTROL

DEFINE TEXT TYPES
Select the required text object and select the button text types.
Go to “new entries” and create a text type with the corresponding text ID.
1). TEXT INCUSTOMER MASTER: -

In the customer master record we can maintain the text on the general data view,
sales area data view and for contact persons.
To maintain the text on any view, from the material select extras  TEXT.
2). TEXT INMATERIAL MASTER: -
142
In the material master the text is maintained on the view sales text.
3). TEXT SALES DOCUMENTS; -

A). Document Header Text: - It refers to the entire document which is found in
the document header.
One important header text is “FORM HEADER” which is automatically copied
from the reference document or customer master record.
If required it can also be entered manually in the document.
Has the form header text appears at the top of the out put, we should reserve it for
the important information for the business partner.
The another important header text is “FORM SUPPLEMENT TEXT” which
appears at the bottom of the out put. The supplement text includes contract
agreements or liability exclusion clauses which are to be referred to at the end of
the form.
B). DOCUMENT ITEM TEXT: - It refers to the document item to which it is

assigned where we can maintain a separate text for each item.
The document item text is material sales text which is automatically copied from
the reference document or material master record. If required it can be manually
entered in the document.
4). TEXT DETERMINATION PROCEDURE: -

For the system to copy the text in to sales document from the reference document
are the master records, we have to configure text determination procedure.
For this go to
SPRO


BASIC FUNCTIONS

TEXT CONTROL

DEFINE AND ASSIGN TEXT DETERMINATION PROCEDURES
Select the required text object (ex: - sales document header) and select the button
change.
Go to “new entries” and create a procedure.
143
Select the created procedure and go to text IDs in text procedure.
Go to “new entries” and enter the required text types with the corresponding text
IDs.
Select the entered text ID and go to access sequences
Go to “new entries” and create an access sequences for the text ID.
Select the access sequences and go to access sequences for text IDs.
Go to “new entries” and specify the data base tables from which the system has to
determine the text for text ID.
NOTE: - For the system to determine the text for form header, we have to specify
the data in the access sequences in following way.
A). If a relevant header text exists in the reference document, it will be copied in to
the sub sequent document. If the text exists in several languages, it will be copied
in all those languages.
B). If there is no header text in the reference document are the document is created
with out reference, the system copies the “CUSTOMER SALES TEXT”
maintained on the sales area data view in the sold to party language.
C). If there no customer sales text in the sold to party language, the system copies
it in that language assigned to sales organization.
D). If there is no customer sales text on the sales area data view, the system copies
the “CENTRAL SALES TEXT” maintained on the general data view in the sold to
party language.
E). If there is no central sales text in the sold to party language, the system copies
it in that language assigned to sales organization.
REFRESHING AND DUPLICATING TEXT: -

It is often required for the text in sales and distribution documents that a particular
text appears uncharged through out the documents, for example that the terms of
payment shall remained same in the document header from the quotation to billing
phase. On the other hand it may be necessary to change a text in a document with
out changing that text in the follow up documents.
144
For this we have referencing and duplicating text.
1). REFERENCING TEXT: - In the referencing text if the text is changed at
source, it will be automatically change in all the follow up documents.
For this we have to uncheck the field “REFER or DUPLICATE” while placing that
text page type (TEXT ID) in the access sequences.
2). DUPLICATING TEXT: - In duplicating text, even though the text is changed
at source, it will not have any effect in the follow up document. For this we have to
check the field “REFER or DUPLICATE” while placing that text type in access
sequences.
STOCK TRANSPORT ORDER
(S.T.O)
1). The material for which S.T.O is created must be available in both the plants.
2). Create a vendor master record for the supplying plant in the company code of
receiving plant. (Vendor code – XK01)
NOTE: - While creating the vendor master record for the supplying the plant we
have to specify the account group “0007” plants.
3). Create a customer master record for the receiving plant in the company code of
supplying plant.
4). Assigning the customer number to the receiving plant.
SPRO


PURCHASING

PURCHASING ORDER

SET UP STOCK TRANSPORT ORDER

DEFINE SHIPPING DATA FOR PLANTS
Go to the details of receiving plant and specify customer number created for that
receiving plant.
5). SPRO
145


PURCHASING

PURCHASING ORDER

SET UP STOCK TRANSPORT ORDER

ASSIGN DELIVERY TYPE AND CHECKING RULE
Go to “new entries” and entered the following data.
A). PURCHASE ORDER TYPE: - Specify the “NB”
B). SUPPLYING PLANT: - Specify the plant supplying the goods.
C). DELIVERY TYPE: - Specify the replenishment delivery type
“NL or NLCC”
“NL” is the replenishment delivery type for intra company S.T.O
“NLCC” is the replenishment delivery type for inter company S.T.O
D). CHECKIN RULE: - Specify “B” for checking availability in delivery.
CREATING S.T.O
1). Create a purchase order (by receiving plant) go to “ME21N” and specify the
following data.
A). VENDOR: - Specify the vendor number created for the supplying plant.
B). MATERIAL: -
C). P.O QUANTITY: -
D). NET PRICE: -
E). CURRENCY: -
F). PLANT: - Specify the receiving plant number
G). STORAGE LOCATION: - Specify the storage location of receiving plant &
(enter)
Select the icon header and specify the purchasing organization, purchasing group
company code of receiving plant.
H). DELIVERY DATE: -
(SAVE THE PURCHASE ORDER)
2). CREATE THE REPLENISHMENT DELIVERY: -
(VL1OB P.ORDERS)
146
LOGISTICS


SHIPPING TRANSPORTATION

OUT BOUND DELIVERY

CREATE

COLLECTIVE PROCESS OF DOCUMENTS DUE FOR DELIVERY
Specify the shipping point of supplying plant, delivery creation date and select the
icon execute.
Select the required P.O number and select the button create delivery in back
ground.
Select the icon log for delivery creation.
Select the group number and select the button document.
Where the system displays the delivery document number created
For the delivery created complete picking and post goods issue.
3). CREATE GOODS RECIEPT IN THE RECEIVING PLANT: -

Go to “MIGO”
Specify the purchase order number and execute check the field “Item Ok” and
select the button post document.
147
AVAILABILITY CHECK
While creating the sales order the system can confirm the materials by the
requested delivery date. If they are available for all the necessary processing
activities that take place before the delivery for this we have to configure the
availability check in the SAP system.
TYPES OF AVAILABILITY CHECK

1). CHECK ON THE BASIS OF ATP QUANTITY (general)
2). CHECK AGAINST PLANNING.
3). CHECK AGAINST PRODUCT ALLOCATION.
CHECK ON THE BASIS OF ATP QUANTITY: - (Available to promise)

The system calculates the ATP quantity from the existing stock, planned inward
movements of material. This type of availability check is carried out for each
transaction with (or) without replenishment lead time.
REPLENISHMENT LEADS TIME: - (RLT)

Replenishment = refilling or refreshment stocks RLT is the time that is needed to
produce or procure the requested material. The system calculates the RLT
according to specific timings maintained in the material master and it always
depends on the material type. (FIELD)
For ex: - In the case of trading goods it is calculated according to purchasing
processing time, goods receipt processing time and the planned delivery time
(MRP2)
NOTE: - The RLT is specified in the material master on the view (MRP3)
148
NOTE: - The system carries out the availability check by following backward
scheduling and forward scheduling. In backward scheduling from the requested
delivery date. The system goes backwards for calculating the material availability
date by considering different lead times if the material availability date falls
between the requested delivery date and PO date. The system confirms the material
by the requested delivery date. In backward scheduling if the material availability
date falls below to PO date, the system goes for forward scheduling from the PO
date and proposes a new delivery date.
AVAILABILITY CHECK INCLUDING RLT: -

If the material availability date is calculated on the basis of the current date to lie
(exists) after the RLT, the item itself can be confirmed despite and insufficient
stock being available in this case the system assumes that any quantity requested
by the customer can be procured with in the requested delivery date and considers
the stock being available so that a binding confirmation can be sent to the
customer.
CONFIGURING THE AVAILABILITY CHECK IN THE SAP SYSTEM

THE FOLLOWING SETTINGS MUST BE MAINTAINED: -
1). The following controlling elements must be maintained in the material master
record.
A). STRATEGY GROUP: - The allowed planning strategies that is the main
strategy and the further possible strategies are combined in a strategy group. Here
we need to specify weather the material is against
MAKE – TO – ORDER PRODUCTION (OR) MAKE – TO – STOCK
PRODUCTION.
NOTE: - The “strategies group” is specified in the material master on the

View (MRP3)
B). MRP GROUP (PP): - The MRP group allows the materials to be combined
from the point of view of material requirements planning. The MRP group in the
combination of plant automatically determines a corresponding strategy group for
the material.
NOTE: - The MRP group is specified in the material master on the view “MRP1”
149
NOTE: - Grouping of MRP type is called MRP group.
2). The following SD specific control features are to be maintained for

configuration the availability check.
A). REQUIREMENTS CLASS: - (Which Type Of Check)

The requirement class specifies weather the availability check is carried out based
on ATP quantity and weather the requirements must be transferred to inventory
management.
For defining these go to

SPRO


BASIC FUNCTIONS

AVAILABILITY CHECK AND TRANSFORM OF REQUIREMENTS

AVAILABILITY CHECK

AVAILABILITY CHECK WITH ATP LOGIC OR AGAINST PLANNING

DEFINE PROCEDURE BY REUIREMENTS CLASS.
NOTE: - The requirement class has to be assigned to “requirement type” which

will be determined in to sales order.
B). CHECKING GROUP: - (Availability Check)

1). The checking group controls customer the system is to create individual or
collective requirements in sales and shipping process.
2). A material stock for availability check with transfer of requirements can be set
here.
3). The checking group is also used to deactivate the availability check.
For defining the check group goes to
SPRO

150

BASIC FUNCTIONS


AVAILABILITY CHECK


DEFINE CHECKING GROUPS
NOTE: - 1). The checking group is specified in the material master for the field
availability check.
NOTE: - 2). While creating the material master, the system automatically proposes
a checking group. For this the following setting must be done.
SPRO


BASIC FUNCTIONS


AVAILABILITY CHECK


DEFINE CHECKING GROUPS DEFAULT VALUE
Go to “new entries” and assign the required checking group to the combination of
material type and plant.
D). CHECKING RULE: -Which document system has to check (it is predefined)
The checking rule specifies the transaction in which the availability check has to be
carried out.
For these go to
SPRO

151

PURCHASING

PURCHASING ORDER

SET UP STOCK

TRANSPORT ORDER

CREATE CHECKING RULE
EX: - A – SD order, B – Delivery

AW – for consignment order.
BW – consignment deliveries
SCOPE AT CHECK: -
The checking group in the combination of checking rule determines the scope of
check where we have to specify which stocks, which inward movements of
material and which outward movements of material must be considered for
calculating ATP quantity. For maintaining these scopes of check go to.
SPRO


BASIC FUNCTIONS


AVAILABILITY CHECK

Carry out control for availability check. Go to “new entries” enter the checking
group, checking rule and maintain the scope of check.
We can consider the following stocks for calculating the ATP quantity.
A). Safety stock

B). Stock in transfer
152
C). Quantity inspection stock
D). Restricted use stock.
The following inward movements can be considered in the scope of check for
calculating the ATP quantity: -
A). PURCHASE ORDERS.
B). PURCHASE REQUISITIONS.
C). PLANNED ORDERS.
D). PRODUCTION ORDERS.
The following outward movements can be included in the scope of check for
calculating ATP quantity.
A). SALES REQUIREMENTS (orders)
B). DELIVERIES
C). RELEASE ORDER REQUIREMENTS (contracts)
NOTE: - If we de check the field “check with out RLT” system carries out the
availability check by considering RLT.
SAVE THE SCOPE OF CHECK
While checking the availability of material in a sales order the other users must not
create sales order the other users must not create sales order and purchase orders
for that material and must not change the corresponding material master record.
For these go to
SPRO


BASIC FUNCTIONS


153
AVAILABILITY CHECK


DEFINE MATERIAL BLOCK FOR OTHER USERS
Go to “new entries” and check the field “BLOCK” for the required combination of
checking group and initiator.
NOTE: - For the system to carry out the availability check for the item in the sales
document, we have to check the field “availability” in the definition of
corresponding schedule line category.
OUT PUT DETERMINATION PROCEDURE

I). ISSUING OUT PUT FOR BILLING DOCUMENTS
Go to VF02
Specify the billing document number and from the main menu.
SELECT BILLING DOCUMENT  ISSUE OUT PUT TO.
NOTE: - To set the required language for out put, in the billing document over
view screen from the main menu.
Select the out put type.
Select the button change out put and specify the required language.
SAVE THE BILLING DOCUMENT
NOTE: - The layout of the out put has to be customized has for the clients a
requirement. This is done by the developers by using “SMART FORMS” (or)
“ADOBE FORMS”.
II). ISSUING THE OUTPUT FOR DELLIVERY DOCUMENTS

Go to “VL02N” specify the delivery document number and from the main menu
SELECT OUT BOUND DELIVERY  ISSUE DELIVERY OUTPUT.
NOTE: - To specify the required language for output, in the delivery document
over view screen from the main menu
SELECT EXTRAS  DELIVERY OUTPUT  HEADER.
Specify the required language for output and SAVE THE DOCUMENT.
154
III). ISSUING OUTPUT FOR SALES DOCUMENTS
Go to “VA02”
Specify the order number and from the main menu
SELECT SALES DOCUMENT  ISSUE OUTPUT TO.
NOTE: - To specify the required language for output, in the sales document over
view screen from the main menu.
SELECT EXTRAS  OUTPUT  HEADER  EDIT.
Specify the required languages for output and SAVE THE DOCUMENT.
NOTE: - To issue the output for a document, we have to configure output

determination procedure in the following way.
I). OUTPUT DETERMINATION PROCEDURE FOR SALES DOCUMENTS

SPRO


BASIC FUNCTIONS

OUTPUT CONTROL

OUTPUT DETERMINATION

OUTPUT DETERMINATION USING THE CONDITION TECHNIQUE

MAINTAIN OUTPUT DETERMINATION FOR SALES DOCUMENTS
Complete the condition technique.
II). OUTPUT DETERMINATION PROCEDURE FOR DELIVERY

DOCUMENTS
SPRO

LOGISTICS EXCUSION

SHIPPING

155

OUTPUT CONTROL


MAINTAIN OUTPUT DETERMINATION FOR OUT BOUND DELIVERIES
III). OUTPUT DETERMINATION PROCEDURE FOR BILLING

DOCUMENTS
SPRO


BASIC FUNCTIONS

OUTPUT CONTROL


OUTPUT DETERMINATION USING THE CONDITION TECHNIQUE

MAINTAIN OUTPUT DETERMINATION FOR BILLING DOCUMENTS
NOTE: - We can configure the output determination procedure for all the
documents by using the transaction code “NACE”.
OUTPUT TYPES: -
EX: - AF00 FOR INQUIRY
AN00 FOR QUOTATION
BA00 FOR ORDER
LD00 FOR DELIVERY
156
RD00 FOR INVOICE
FUNCTIONALITY OF OUTPUT TYPE

A). GENERAL DATA: -
1). ACCESS SEQUENCE: - Specifies the corresponding access sequence of the
output type.
2). ACCESS TO CONDITIONS: - If we check this field, the system determines an

output by searching valid condition records.
3). CANNOT BE CHANGED: - If we check this field, we cannot make any

changes to the output in the corresponding document (Don’t check this field)
4). MULTIPLE ISSUING: - If we check this field, we can issue the same output to
the same partner for more than ones.
5). PARTNER INDEPENDENT OUTPUT: - If we check this field, we can issue
the output independent of the partner for whom the records are maintained.
B). DEFAULT VALUES

1). DISPATCH TIME: - Specifies weather the output has to be issued immediately
after saving the document or at a later stage with periodically scheduled jobs.
2). TRANSMISSION MEDIUM: - Specifies the default medium for output
For ex: - It can be a print out or fax etc.
3). PARTNER FUNCTION: - Specify the default partner for whom the output has
to be issued.
C). STORAGE SYSTEM

1). STORAGE MODE: - Specifies weather the system has to issue the print out
and archive it or only issue the print out.
D). PRINT
1). PRINT PARAMETERS: - Specifies the default parameters for print out.
For each output type we need to maintain “mail title and text” where we can
specify the required languages for output.
For each output we have to effectively the “processing routines” where media we
have to safely the following data are for each transmission.
FROM ROUTINE P.D.F SMART

MEDIUM PROGRAMME
ENTRY FORM
157
SD INVOICE -
S.D INVOICE
FORM01
BILLING PRINT 01 IN 6.0
PRINT OUT ENTRY
DOCUMENT
RV INVOICE01 IN
RVADIN01 IN 4.7
4.7
LE-SHP-
IN DELIVERY RE-DELNOTE ENTRY DELNOTE IN 6.0
PRINT OUT
DOCUMENT RVADDNO1 IN 4.7 ENTRY RV DELNOTE IN
4.7
SD-SDOC-PRINT
IN SALES ENTRY SD-DOC_FORM01
PRINT OUT 01 IN 6.0
DOCUMENT ENTRY RV ORDER 01
RVADOR01 IN 4.7
NOTE: - For this field smart form we have to specify the form customized by the
ABAPER.
PARTNER FUNCTION: - For each output types we need to maintain the “partner
function”. Where we have to specify the concerned partner for each transmission
medium
MAINTAIN CONDITION RECORDS FOR OUTPUT TYPE: -

LOGISTICS


MASTERDATA

OUTPUT

(OR – SP)  I) SALES DOCUMENTVV11 CREATE.

(LF – SP)II) SHIPPING DOCUMENT VV21 CREATE.

(F2 – BP)III) BILLING DOCUMENT VV31 CREATE

158
BATCH MANAGEMENT / DETERMINATION
STEP NO: 1 – For maintaining the batches for the material, we have to  check
the field “BATCH MANAGEMENT” in the corresponding material master record.
STEP NO: -2 – MAINTAINING NUMBER RANGE FOR BATCHES: -

SPRO

LOGISTICS GENERAL

BATCH MANAGEMENT

BATCH NUMBER ASSIGNMENT

ACTIVATE INTERNAL BATCH NUMBER ASSIGNMENT

ACTIVATE BATCH NUMBER ASSIGNMENT
Here we need to specify weather we want to use, internal or external number range
for batches.
AUTOMATIC BATCH NUMBER ASSIGNMENT IN ACTIVE
AUTOMATIC BATCH NUMBER ASSIGNMENT ACTIVE
159
If we are using “EXTERNAL NUMBER RANGE” for creating it go to
SPRO

LOGISTICS GENERAL

BATCH MANAGEMENT

BATCH NUMBER ASSIGNMENT

ACTIVATE INTERNAL BATCH NUMBER ASSIGNMENT

ACTIVATE BATCH NUMBER ASSIGNMENT

MAINTAIN NUMBER RANGE FOR INTERNAL BATCH NUMBER
ASSIGNMENT
STEP NO: - 3 – Post the stock for the material by using the batch numbers go to
“MB1C”
STEP NO: - 4 – CONFIGARATION BATCH DETERMINATION PRODUCT: -
SPRO

LOGISTICS GENERAL

BATCH MANAGEMENT

BATCH DETERMINATION AND BATCH CHECK
A). Condition tables – (Define sales and distribution strategy tables) create
condition table for batch determination.
B). Access sequence – define sales and distribution access sequence.
C). Strategy types – define sales and distribution strategy types.
FUNCTIONALITY OF STRATEGY TYPE: -

1). Access Sequence: -
2). Batch Split: - The number batch split allowed delivery the batch determination.
160
3). Changer Allowed: - If we  check this field, the number of batch split can be
changed during the batch determination.
4). Over Del Allowed: - If we check this field the system allows, the total of split
quantities to be greater than the actual required delivery quantity (i.e. picking)
5). Unit of Measure: - Specifies the unit of measure in which the system stocks
must be displayed during the batch determination.
6). Dialogue Batch Determination: - If we  check this field the system gives the
message during the batch determination in the corresponding document.
D). Batch Search Procedure Definition: - Define sales and distribution search
procedure. Define a procedure and place the required strategy type in it.
E). Batch search procedure allocation and check activation.

 Allocate SD search procedure and activate check.
Go to “new entries” and assign the procedure of steps to the combination of sales
area and sales document types.
While assigning the procedure, if we check this field “CHECK BATCH” the
system carries out a “CHECK” for the batch number entered manually in the
corresponding document. Against the selection criteria stored for the
“BATCH DETERMINATION”
F). Activate automatic batch determination in SD.
1). Automatic batch determination for sales order item
Select the required item categories (ex: - TAN) and check this field automatic batch
determination.
2). Activate automatic batch determination for delivery item category: -
Select the required item category (TAN) and  check the field automatic batch
determination.
NOTE: - It is always recommended to activate the batch determination at delivery
level rather then in sales order.
MAINTAINING CONDITION RECORDS FOR BATCHES:

LOGISTICS (OR) LOGISTICS
 
SALES AND DISTRIBUTION CENTRAL FUNCTIONS
 
MASTER DATA BATCH MANAGEMENT
161
 
PRODUCTS BATCH DETERMINATION
 
BATCH SEARCH STRATERY BATCH SEARCH STRATEGY
 
“VCH1” CREATE FOR SALES AND DISTRIBUTION

“VCH1” CREATE
Specify the strategy type.
Select the required key combination  (enter)
Maintain the condition record by specifying the required material.
The remaining details will be automatically determined from the definition of
strategy type.
Select the record and go to details where the field “selection type for batch
determination” specifies how the system has to determine the batch numbers for
the material in to the corresponding document because we are not using variant
configuration for batches. We shall not leave this field blank. We have to specify
the value “O” (selection with no selection criteria) for this field (save the record)
USING BATCHES IN DELIVERY: - While creating the delivery the system by

default definition of the batch number for the delivery item.
To see that select the icon in the field batch split indicator where the system
automatically generates one more line item with the corresponding batch number
Go to the details of that line item, change the delivery quantity has for the
available quantity in that batch number and come back to the over view screen and
enter the same quantity has picking quantity.
To enter one more batch select the delivery item, select the button batch split and
entered the required batch number with the corresponding delivery quantity and
come back to the over view screen and enter the pick quantity.
Like this we have to specify the required batch number till the entire delivery
quantity is picked and complete the post goods issue.

IN VOICE LIST
The invoice list allows you to create a list of billing documents to be sent to a
payer. We have two types of invoice lists one is for invoices and debit memos and
the other is for credit memos.
162
Ex: - A payer may be the head office of a buying group which pays all the invoices
for those goods shipped to the individual members.
The group payer takes the responsibility for paying the invoice list and then
collecting the payments from the individual members.
In return for these services the group payer may get factoring discount.
For creating the invoice list the following settings must be done.
1). In the customer master record of payer we have to specify the factory calendar
for the field “invoice list dates” on the billing document tab page under the sales
area data view.
2). We need to define the billing types “LR or LG” where LR is the invoice list for
invoices and debit memos where has LG is for credit memos.
For “LR” the document category is “3” and the corresponding cancellation type is
“L or S” where has for “LGs”.
We need to specify the billing type “LR” for the field invoice list type in the
definition of “F2 and L2” where has for the same field we have to specify “LG” in
the definition of “G2”.
For maintaining the factory discount we have to use the condition type “RL00”.
NOTE: - For “RL00” the condition class is discount or surcharge, the plus or
minus field contains negative, the calculation type is percentage and the condition
category is “R” invoice list condition.
We need to place “RL00” in the pricing procedure below to total value with
requirement “23”.
CREATING INVOICE LIST: - LOGISTICS


BILLING

INVOICE LIST

“VF21” Create
For the field document specify the required invoices and select the icon execute.
The system calculates the net value of the invoice list by combining the net values
of all the invoices entered.
163
The invoice list contains header and item data the header data contains an over
view of summary information such has the net values factoring discount, tax
amount etc.
Each item in the list represents the corresponding billing document entered in that
invoice list save the invoice list.
BACK ORDER PROCESSING (BOP)

Using back order processing we can list those documents relevant for requirements
for particular materials and confirm them manually.
We can assign the “ATP” stock to the out standing order quantities.
In addition we can with draw the already confirmed quantities and re assign them
to different items.
NOTE: - The back order processing is only available for those materials with
individual requirements that is in the corresponding material master record we
have to specify the checking group “02” for the field availability check.
EXAMPLE: -
1). The stock is at 50 pieces.
2). Create order for 30 pieces and complete the delivery.
3). Create one more sales order for the same material for 30 more pieces
Where the system confirms 20 pieces only
4). Post the stock for 50 more pieces.
5). Now the sales order created in the 3rd step can be confirmed for the entire
quantity by using back order processing for this go to
LOGISTICS

SALES AND DISTRBUTION

SALES

BACK ORDERS

BACK ORDER PROCESSING

V_RA SALES DOCUMENTS
6). On the selection list screen entire the required selection criteria like material,
plant, sales area etc, and select the icon execute.
164
7). The system displays all the materials that meet the selection criteria and for
each material it displays the corresponding information like the sales document
number, first delivery date, order quantity, confirmed quantity and open quantity.
8). In the over view screen the system displays the information like received (or)
required quantity, confirmed quantity and the cumulative “ATP” quantity for each
“MRP” element.
9). Select the required “MRP” elements (order) for which we have to change the
confirmed quantity and select the button change confirmation.
10). The field “OPEN” specifies the quantity at to be delivered the field “ATP”
quantity specifies a total available quantity the field “TOTAL COMMITED”
specifies the actual confirmed for the field “COMMITTED” we have to specify the
entire quantity that has to be confirmed. In is example it is “30”.
RE DISTRIBUTING THE CONFIRMED QUANTITIES: -

EXAMPLE: -
1). Stock is at 70 pieces.
2). Create the order for 30 pieces where the system confirms the entire 30 pieces.
3). Create one more order for 50 more pieces where the system confirms 40 pieces
only now we need to get 10 more pieces from the previous order to this order in the
following way.
Go to V_RA – sales document enter the required selection criteria and execute.
4). Select5 the document for which the confirmed quantity to be reduced and select
the button back orders.
5). Select the same order (MRP element) and select the button change
confirmation.
For the field committed reduced the quantity has for the requirement.
In is example it must has 20.
Select the icon copy “” and save it.
Select the second order for which the confirmed quantity has to be increased and
select the button “BACK ORDER”.
6). Select the same order (MRP element) and select the button change
confirmation.
Change the quantity for the field committed has for the requirement. In is example
it is 50.
Select the icon copy “” and save it.
VARIANT CONFIGARATION
165
PULSAR
ENGINE: - 150cc COLOUR: - RED

- 180cc - BLACK
- SILVER
PRICING
BASIC PRICE= 35000:00 10000:00 – 150cc
12000:00 – 180cc
10000:00 – RED
12000:00 – BLACK
15000:00 – SILVER
The variant configuration is a tool which helps to simply the complex
manufacturing of the final product with more varieties and the variation of the
input material. The manufacturer always has to offer new variants of its products.
Often by modifying the existing product designs we create new variants has we
process the order so that we can react quickly to the customers requirements.
1). CHARACTERISTICS: - When we create a sales order for the configurable
material, that sales order must describe precisely how the product being ordered is
to look.
This description always comes from the characteristics and the corresponding
characteristic values we always use the characteristics to define the features of a
configurable material so that the customer can choose from different options of the
characteristics.
CREATING CHARACTERISTICS: -
LOGISTICS

CENTRAL FUNCTIONS

VARIANT CONFIGURATION

ENVIRONMENT

CLASSIFICATION

MASTER DATA

CT04 CHARACTERISTICS
Enter the required characteristic and select the icon “create”.
166
On the “basic data” view specifies the description and the status must be
“released”.
Specify the data type. (Character format)
Specify number of characters.
In the sales document the movement we entered the configurable material the
system automatically displays the characteristics with the corresponding
characteristic values. Here if we need to choose only one characteristic value of a
characteristic at a given point of time. We have to select the option “single value”
under the “value assignment” section in the definition of characteristics. Where has
we need to select the option “multiple values” if the requirement is to select more
than one characteristic value of a characteristic at a given point of time in the sales
document.
Select the tab page “values” and enter the required characteristics values.
SAVE THE CHARACTERISTICS
CLASS: - In variant configuration a class is allowed use to hold the characteristics

that describing the configurable material. By linking the class to the material, we
allow that material to configure by using the characteristics of that class.
In variant configuration we can only use a class if that class has a class type that
supports the variant configuration and is “300” in the standard SAP system.
2). CREATING CLASS: -

LOGISTICS

CENTRAL FUNCTIONS


ENVIREMENT

CLASSIFICATION

MASTER DATA

CL02 CLASSES
167
Enter the required class.
Enter the class type “300” and select the icon “create”.
On the basic data view specifies the description and the status must be released.
Select the tab par “CHAR” and enter the required characteristics and save the
class.
3). CREATING MATERIAL MASTER FOR THE CONFIGURABLE

MATERIAL (PULSAR) AND ASSIGNING CLASS.
“MM01” create.
NOTE: -
A). While creating the material specifies the material type has “KMAT”.
(Configurable material)
B). On the basic one view, the value for the field “CM RELEVANTS” must be
“RELEVANT FOR CONFIGURATION MANAGEMENT”.
C). In the material master we have to enter class on the view “classification”.
D). We have to specify the item category group has “0002 configuration”.
E). Enter the required data and save the material master.
4). CONFIGURATION PROFILE: -

We maintain the configuration profiles to define the settings for the configurable
object that is hare we need to specify weather the material is configured with (or)
with out “BOM”.
If it is with “BOM” we can also specify weather it is single level (or) multi level.
To maintain the configuration profiles go to
LOGISTICS

CENTRAL FUNCTIONS


CONFIGURATION PROFILE
168

“CU41” CREATE
Select the object material then  enter.
Enter the required material (PULSAR) for which the configuration profile has to
be maintained.
In the overview screen create a profile with the class type “300”.
Select the created profile and go to profile detail.
Select the tab page “CONFIGURATION SCREEN” where we can maintain all the
setting “BOM”.
SAVE THE PROFILE
5). DEPENDENCIESE: -
The dependencies allow you to control the inter dependencies between the
characteristics and the characteristic values.
It also controls the components we can select from the bill of material.
DEPENDENCY TYPE
A). PRE-CONDITION: -
This dependency type specifies when an object
(A characteristic (or) A characteristic values (or) A BOM item etc.) can be copied
in to configuration.
For ex: - If a pre-condition is linked to an object, for example a characteristic

value, that object can only be copied to the configuration specified in the condition
is full filled.
B). SETTING CONDITION: - This dependency type specifies when it is
mandatory to assign a value to the characteristic.
C). PROCEDURE: - With the help of this dependency type we can infer
(automatically get it) values for the characteristic values.
NOTE: - In our example we will use the dependency type “PROCEDURE” to

automatically values. For this first we shall create a characteristic for price where
we have to specify the data base table in which the variant price is stored.
For creating this characteristic go to – “CT04”
 Enter the required characteristic for price (ex: - ZPR) and select the icon
“CREATE”.
 On the basic data view specifies the description and the status must be released.
 Select the tab page “ADDITIONAL DATA” and specify the table name
169
“SDCOM” and the field name “VKOND” where the variant price has to be stored
 enter.
SAVE THE CHARACTERISTIC
MAINTAINING DEPENDENCIES: -
LOGISTICS

CENTRAL FUNCTIONS


DEPENDENCY

SINGLE DEPENDENCY

“CU01” CREATE
Here we need to maintain the dependency and then assign it to the required
characteristic value.
Rather this we can directly go to the characteristic value and maintain the
dependency there it self.
For this go to “CT04”.
Enter the required characteristics (Engine) and select the icon “change”.
Select the required characteristic value and from the main menu.
Select extrasobject dependencieseditor.
Select the dependency type “PROCEDURE”.
Specify the following SINTAX.
$ SELF Price characteristic = “VARIANT”.
$ SELF ZPR = “150”.
NOTE: - What ever the variant we have used here, for the same we have to
maintain price while maintaining the condition records for the characteristic value.
(SAVE THE SINTAX)
NOTE: - Like this we have to maintain the dependencies for all the characteristic
values.
MAINTAINING PRICING
A). MAINTAINING BASIC PRICE: -
Go to “VK11” and maintain the condition records for “PR00” by specifying the
configurable material (PULSAR)
170
B). MAINTAINING VARIANT PRICE: -
Go to “VK11” and maintain the condition records for the condition type “VA00”
(standard) by specifying the configurable material and the corresponding variants.
NOTE: - For “VA00” the condition class is the discount (or) surcharge, calculation
type is quantity and the condition category is “O” variants.
C). We need to place “VA00” in the pricing procedure below to “PR00” with the
requirement to and account key “ERL”.
NOTE: - For the configurable material the item category is “TAC”.

“TAC” is same has “TAN” a part from that for “TAC” in the field structure scope
we have to specify the value “C”.(Configuration on BOM explosion) or
(Configuration possible with BOM explosion)
QUESTIONS FOR TRANSACTION CODES
1). T.CODE FOR LIST OF INQUIRES?

A). VA15.
2). T.CODE FOR INCOMPLETE INQUIRES?

A). V.03.
3). T.CODE FOR LIST OF QUOTATIONS?

A). VA25N.
4). T.CODE FOR INCOMPLETE QUOTATIONS?

A). V.04.
5). T.CODE FOR EXPIRING QUOTATIONS?

A). SDQ1.
6). T.CODE FOR EXPIRED QUOTATION?

A). SDQ2.
7). T.CODE FOR COMPLETED QUOTATIONS?

A). SDQ3.
8). T.CODE FOR LIST OF SALES ORDERS?

A). VA05.
171
9). T.CODE FOR INCOMPLETE SALES ORDERS?
A). VA02.
10). T.CODE FOR COMPLETE SCHEDULING AGREEMENTS?

A). VA35.
11). T.CODE FOR INCOMPLETE SCHEDULING AGREEMENTS?

A). V-05.
12). T.CODE FOR LIST OF CONTRACTS?

A). VA45.
13). T.CODE FOR INCOMPLETE CONTRACTS?

A). V.06.
14). T.CODE FOR EXPIRING CONTRACTS?

A). SDV1.
15). T.CODE FOR EXPIRED CONTRACTS?

A). SDV2.
16). T.CODE FOR COMPLETED CONTRACTS?

A). VA45 (or) SDV3.
17). T.CODE FOR LIST OF SALES DOCUMENT BLOCKED FOR

DELEVERY?
A). VA14L.
18). T.CODE FOR LIST OF SALES DOCUMENT BLOCKED FOR BILLING?

A). V.23.
19). T.CODE FOR LIST OF SALES ORDERS BLOCKED BECAUSE OF

CREDIT LIMIT?
A).
20). T.CODE FOR RELEASING THE SALES ORDERS BLOCKED BECAUSE

OF CREDIT LIMITS?
A). VA14L.
172
21). T.CODE FOR LIST OF DELIVERY DOCUMENTS?
A). VL06F.
22). T.CODE FOR INCOMPLETE DELIVERY DOCUMENTS?

A). VL04.
23). T.CODE FOR LIST OF DELIVERY DUE FOR PRICING / POST GOODS
ISSUE (DELIVERY MONITOR)?
A). VL01N.
24). T.CODE FOR CANCELLING POST GOODS ISSUE?

A). VL09.
25). T.CODE FOR LIST OF TRANSFER ORDERS?

A). VL10B.
26). T.CODE FOR BILLING DOCUMENTS?

A). VF05.
27). T.CODE FOR BILLING DUERIST?

A). VF04.
28). T.CODE FOR BLOCKED BILLING DOCUMENTS?

A). VFX3.
29). T.CODE FOR LIST OF INVOICE LIST?

A). VF21 (or) VF23 (or) VF25.
REBATE PROCESSING
We can configure the entire rebate process in “3” components.
1). CONFIGURING REBATES.
2). SETTING UP REBATE AGREEMENT.
3). MANAGING REBATE AGREEMENT AND PAYMENT.
I). CONFIGURING REBATES
173
1). PRE-REQUISITES: -
A). In the definition of sales organization we have to check the field rebate process
active.
B). In the corresponding customer master record (PAYER) we have to check the
field rebates.
C). In the definition of corresponding billing type we have to check the field
relevant for rebate.
2). MAITAINING CONDITION TECHNIQUE FOR REBATES: -

SPRO


BILLING

REBATE PROCESSING

CONDITION TECHNIQUE FOR REBATE PROCESSING
A). MAINTAIN CONDITION TABLES FOR REBATE: -

Create the required condition tables with the corresponding key fields.
B). MAINTAIN ACCESS SEQUENCES: -

Create an access sequences and place the required condition tables in it.
C). DEFINE CONDITION TYPES: -

Example: -
BO01 GROUP REBATE
BO02 MATERIAL REBATE
BO03 CUSTOMER REBATE
D). FUNCTIONALITY OF REBATE CONDITION TYPES: -
1). The condition class is “C” expense reimbursement.
2). The plus/minus field are negative.
174
3). The calculation type is percentage for “BO03 and BO01” where has it is
quantity for BO02.
4). For the rebate condition types several fields like header condition, group
condition, account/percentage etc.
Which we have in the regular pricing condition type or unavailable this is
controlled by the condition class “C”.
5). The field rebate process specifies weather the accruals are calculated depending
on the invoice value. If we leave this field blank the system calculates the rebate
accruals on each applicable invoice value and keeping the value “A” for this field
if we don’t base the rebate payment on the actual sales, but on the specific
performance of the customer such has the display schemes.
6). The field provision “CON” specifies weather we want to reverse the accruals at
the time of partial payment to the customer. Leaving this field blank will reverse
the accruals and the value “A” will prevent it.
E). MAINTAIN CONDITION PROCEDURES: -

We need to place the rebate condition types in the main pricing procedure only.
1). In the pricing procedure we have to specify a sub total for “REBATE BASIS”
just about to net value of the item by specifying the value “7”
(Carry over value to KOMP_BONBA rebate basis “1” for the field sub total.
2). Below to the net value of the item we have to place the rebates condition types
by specifying the step number of rebate basis in the field “FROM”.
3). For the rebate condition types we have to specify the requirement “24” which
enables the system to determine the rebate condition types in to the invoice only.
4). For the rebate condition types we have to assign the accrual key as well as
account key. The posting of rebate accruals to the corresponding G/L accounts is
done by the accrual key (ERU). The settlement document (CREDIT MEMO) uses
those accounts assign to the account key (ERB) which will reverse the accrued
amounts and credits the customer.
3). CONFIGURING THE REBATE AGREEMENT TYPES
A). DEFINING REBATE AGREEMENT TYPES: -
175
SPRO


BILLING

REBATE PROCESSING

REBATE AGREEMENT

DEFINE AGREEMENT TYPES

DEFINE AGREEMENT TYPES
FUNCTIONALITY OF AGREEMENT TYPE
1). PROPOSED VALID FROM: -

Specifies the default start data and end date of the rebate agreement. The default
start date is very much important in regards to weather or not we want to allow the
retro active rebates that is if the default started it is the beginning of the current
year, the system will calculate the rebates for all those invoices in the past from
that date onwards even though the rebate agreement is created on the current date
this is called retro active rebate.
2). PROPOSED VALID TO: - Specifies the default start data and end date of the
rebate agreement. The default start date is very much important in regards to
weather or not we want to allow the retro active rebates that is if the default started
it is the beginning of the current year, the system will calculate the rebates for all
those invoices in the past from that date onwards even though the rebate agreement
is created on the current date this is called retro active rebate.
3). PAYMENT METHOD: - Specifies the default payment method while repaying
the rebate amount to the customers.
4). DEFAULT STATUS: - Specifies the default status of the rebate agreement.
5). CONDITION TYPE GROUP: - Specifies the corresponding condition type

group of the rebate agreement.
176
6). VERIFICATION LEVELS: - Specifies the default level of detail we see while
reviewing the applied invoices in the rebate agreement.
7). DIFFERENT VALIDITY PERIOD: - If we check this field, the validity period
of the rebate condition record can defer from the validity period of the rebate
agreement.
8). PAYMENT PROCEDURE: - Specifies weather we want to allow the partial

rebate settlements up to the accrued value or no limit for the manual payment.
9). PARTIAL SETTLEMENT: - Specifies the document type “R3” for

automatically creating the document partial rebate settlement request while
entering the rebate payment in the rebate agreement.
10). REVERSE ACCRUALS: - If we check this field the system displays the
amount of accruals reverse in the rebate agreements.
11). FINAL SETTLEMENT: - Specifies the document type “B1” for creating
“REBATE CREDIT MEMO REQUEST” while making the final settlement to the
customer.
SAVE THE AGREEMENT TYPE
B). CONDITION TYPE GROUPS: -

The condition type group specifies which rebate condition types are allowed for
the rebate agreement type. For defining this condition type group go to
SPRO


BILLING

REBATE PROCESSING

REBATE AGREEMENTS

177
CONDITION TYPE GROUPS

DEFINE CONDITION TYPE GROUPS
To this condition type group we have to assign the required rebate condition types.
“ASSIGN CONDITION TYPES AND TABLES TO CONDITION TYPE
GROUPS” go to “new entries and enter the required combination of condition type
group, counter, condition type and condition table number.
After assigning the rebate condition types to the condition type group we have to
assign the condition type group to the rebate agreement type.
Assign condition types and tables to condition type groups.
Select the required rebate agreement type and assign the required condition type
group.
I). SETTING UP REBATE AGREEMENTS
A). CREATING REBATE AGREEMENT: -
LOGISTICS


MASTRDATA

AGREEMENTS

REBATE AGREEMENTS

“VBO1”
Specify the agreement type.

Specify the required sales area.
In the overview screen specify the rebate recipient (sold to party) the other details
are determined from the definition of rebate agreement type.
Select the button conditions.
Maintain the condition record for the required condition type.
NOTE: - If it is a customer rebate, we need to maintain the condition record on the
payer.
Select the record and go to details and specify the required “MATERIAL FOR
SETTLEMENT”.
178
NOTE: - What ever the material that is entered here, by using that the system
automatically creates the document “PARTIAL REBATE SETTLEMENT
REQUEST” while making the payment. SAVE THE AGREEMENT.
B). Create fue invoices based on which the system will calculate the accruals and
updates them in the rebate agreement.
III). MANAGING REBATE AGREEMENTS AND PAYMENTS
A). After creating the invoices the system automatically calculates the rebate
accruals and updates them in the rebate agreement. To see that select the condition
record maintained in the rebate agreement and select the icon payment data.
B). To see all the billing documents based on which the system has calculated
rebate accruals, select the icon “VERIFICATION LEVEL” in the overview screen
of rebate agreement.
C). CREATING PARTIAL SETTLEMENTS.
1). In the rebate agreement overview screen select the button “PAY” and enter the
required amount for the field amount to be paid and save the agreement”.
2). The movement we save the agreement the system automatically creates a
document “PARTIAL REBATE SETTLEMENT REQUEST”.
NOTE: - For the system to automatically create this document, we specify the
document type “R3” in the definition of agreement type for the
field “PARTIAL SETTLEMENT”.
3). Go to the overview screen of partial rebate settlement request by using the
transaction code “VA02” where the system displays that material entered has
material for settlement in the agreement.
Go to the item data of that item and select the “CONDITION” tab page where the
rebate condition type is displays twice. One is to reverse the accruals and the other
is to credit the customer with the specified amount. Remove the billing block if any
and save the document.
NOTE: - For “R3” document category is “K”.

No shipping data has to be specified.
The corresponding billing type is “B3” (Rebate partial settlement.)
NOTE: - The item category is “B1N” is relevant for billing where “BILLING
RELEVANTS” is set to see. It’s relevant for pricing.
Create the billing document rebate partial settlement (CREDIT MEMO)
“VF01”
179
Create this document with reference to (Partial rebate settlement request.) and
save it.
NOTE: - The billing document type “b3” is same has “G2” a part from that we
have to specify the value “C” (Partial settlement for a rebate agreement) for the
field rebate settlements till the entire rebate amount is paid to the customer.
INTER COMPANY SALES

STANDARD SALES
PLANT
S.ORG  COMPANY SHIPPING POINT
OR LF F2
CUST
INC.CON.SALES
PLANT PART-2
S.ORG COMPANY-1 SHIPPINGPOINT S.ORG COMPANY-2 S.P2
OR F2
CUST LP
I). C.M.R for “C1 in C2”

II). PLANT2  SALES ORGANIZATION IN-1
III). PI01/PR02.
IV). I V  O R.
The inter company sales describes the business process between to company codes
that belong to same client.
180
In this process the sales organization belongs to ordering company code and the
plant belongs to delivery company code.
The sales organization of ordering company code process the sales order and bills
the customer where has the plant of delivering company code delivers goods to the
customer and bills the ordering company code which is the inter company billing
document.
For configuring the inter company sales in the S A P system the following settings
must be determined.
1). A customer master record must be created for the ordering company code in the
sales organization of the delivery company code.
2). The permissible combinations of plants and sales organization must be

maintained that is the plant of delivering company code must be assigned to the
sales organization of ordering company code.
3). For maintaining the inter company price we have to use the condition type
“PI01 or PI02”.
NOTE: - For “PA01/PA02” the “CONDITION CLASS” is “PRICES” and the
condition category is “I” (Price for inter company billing). For PA01 the
calculation type is quantity where has it is percentage for PI02.
We need to place these condition types in the pricing procedure below to net value
with requirement “22”.
4). For creating inter company billing document, we need to define the billing type
“IV” and assign it to “OR”.
NOTE: - For “IV” the document category is “5” and the transaction is “7” and the
corresponding cancellation type is “IG”.
We need to specify “IV” in the definition of “OR” for the field inter company
billing type.
THE PROCESS FLOW OF INTER COMPANY SALES
I). Create sales order “VA01” create.

NOTE: -
1). The order has to be processed in the sales organization of ordering company
code.
NOTE: -
181
2). The system automatically determines the plant of ordering company code in to
sales order which we have to change to the plant of delivering company code. This
can be done on the view procurement.
II). Create delivery “Vl01N” create.

NOTE: -
The delivery document has to be processed from that shipping point assigned to the
pant of delivery company code.
III). Create billing document “VF01” create.

The delivery document has to be processed twice for creating the billing
documents. The delivering plant process the delivery document for creating the
inter company invoice where has the ordering company code process the
Same delivery document for creating customer invoices.
WORK SHOP
LAND SCAPE ASAP TESTING
182
 IMPLEMENTATION “E2E” (END TO END) FULL LIFE CYCLE
SUPPORT
UP GRADE
ROLL OUT
SAND BOX DEVELOPMENT QUALITY PRODUCTION

SERVER SERVER ASSURENCE SERVER SERVER
GOLDEN MASTER
SAND
CONFIGARATION CONFIGARATION
BOX PRODUCTION
CLIENT CLIENT
CLIENT CLIENT
ABAP INTEGRATION
DEVELOPMENT TESTING
CLIENT (client copy) CLIENT
UNIT TESTING TRAINING

CLIENT CLIENT
I). SAND BOX ENVIRONMENT: -

This environment is intended to be areas where the team can safely prove the
concepts are resolve the issue with out having to be concerned with the impact to
the main system.
This system can be refresh periodically are when ever it is required.
SAND BOX CLIENT: -

This is the only client in this environment that is to be used for those tasks that do
not fall under any tropical run.
For example the proofs of concepts that the development team does not have the
experience of performing in the post are not comfortable enough in performing can
be done in this client. The production data issues can also be pulled down to this
client to prove the solution.
II). DEVELOPMNT ENVIRONMENT: -

This environment is intended to be an area where the main activities accurse and or
tested before being mood through the quality environment on their way to
production.
A). GOLDEN CONFIGARATION: -
183
This is the client where all the configuration setting will be done and transported
the team members will have restricted access to this client. This client is the
reference client for production configuration where testing will not be allowed.
B). ABAP DEVELOPMENT CLIENT: -
This client is used by the programmer to develop new ABAP programs. Those
programs created here can be tested independent of the configuration development
changes that might be according in the other clients no configuration is allowed in
this client. The configuration changes for this client are done by refreshing them
using the golden configuration client.
C). UNIT TESTING CLIENT: -
This client is used specifically for the unit testing of the find configuration. This
client will be created from the golden configuration client and the sample text data
will be up loading here for carrying out unit testing.
III). QUALITY ASSURENCE ENVIRONMENT: -

This environment is to be has close to the same has the production environment as
possible this gives the developers a static version of how the production
environment will be all the completed unit tests from the development environment
strung together in to longer test that constitute the entire business process and
tested hers. There changes to the cross client objects are not allowed in this
environment where they must be done in the development environment. In rare
circumstances where a change has to be done directly in this environment, a prier
approval will be needed.
A). MASTER CONFIGURATION CLIENT: -

After unit testing is completed all those changes are transported to this client so
this is a client who contains all these transports.
There should not be any transactional data (testing) in this client so this client acts
has golden client.
B). INTEGRATION TESTING CLIENT: -
This client is used for integration and user acceptance testing consist of those unit
test strength together to compromise the complete business process the integration
testing is performed in this client after the functional configuration is completed.
This client is create a from the master configuration client.
C). TRAINING CLIENT: -
This is the client where the actual “SAP” training is done for users this client is
refreshed from master configuration client has for the requirements any
configuration changes which go to the production client would also go to this
client.
184
IV). PRODUCTION ENVIREMENT: -
This envirement is used for the production live operations of the client.
PRODUCTION CLIENT: -
This client issued for the live transactions. The custom rising and repository
changes are only allowed to the transported to this envirement after they have been
fully tested in the “QA” envirement and have a formed chase control approved. No
customizing or repository changes are allowed in this client under any
subcumstences this client is unique in the land scrape which cannot be refresh, can
only be restored from a back up.
ASAP – METHODOLOGY
(Is also called has road map)
SDLC
(SOFT WARE DEVELOPMENT LIFE CYCLE)
Accelerated “SAP” is a implementation solution provided by “SAP” for the rapid
and efficient implementation of the “SAP” system the “ASAP” methodology
integrates several components that work in conjunction.
PHASE IN “ASAP” METHODOLOGY: -
1). PROJECT PREPARATION.
2). BUSINESS BLUE PRINT. (B.B.P)
3). REALIZATION.
4). FINAL PREPARATION.
5). GO – LIVES SUPPORT.
1). PROJECT PREPARATION: -

This phase provides initial planning and preparation for the implementation of
“SAP” system.
 Deciding the scope of the project
 Deciding the system land scope
 Team formation
SAP

 
Consulting team client team
 
185
Project manager project manager
 
`      
Functional technical basis end power code business
User’s users team process
Owner
(BPO’s)
 PREPARING BUSINESS PROCESS DOCUMENT (or) BRS: -

It is the documentation of business requirement of the client
(AS IS ETUDY) “BRS” (BUSINESS REQUIREMENT SPECIFICATION)
 CICK OF MEETING: -
This mile stone activity is a critical point that officially launches the “R3”
implementation for the client. It also explains the implementation strategy. Time
(very important) (Deciding go-live date) and project goods and objectives
2). BUSINESS BLUE PRINT (B.B.P): -

In this phase we create business blue print which is a detailed documentation of the
results gathered during requirements work shops. For then more the business blue
print serves to document the business process requirements of the company. On
this basis we will achieve a common under standing of how the company intense to
run they business process in the SAP system.
A). Deciding the organization at structures
B). Preparing the data collection sheets for data migration (flat file)
C). Deciding the data conversion strategy for data migration.
D). Preparing (B.B.P) documentation. (AS – IS vs. TO BE)
AS –IS TO BE
1).R1 Y/N
2).R2 Y/N
3).R3 Y/N
4).R4 Y/N
E). Identifying the varies when customization has to be done.
F). GAP analysis.
G). Deciding user roles and authorization.
3). REALIZATION: - (This phase talk about configuration)
A). In this phase we implement all the business process requirements based on the
business blue print. We configure the entire system step by step in two work
186
packages called “BASE LINE” configuration and final configuration organization
change management.
B). BASIC LINE CONFIGARATION AND CONFIRMATION: -
During base line configuration we work on those processes which can be
configured with out any programming on enhancement.
C). UNIT TESTING OF BASE LINE CONFIGARATION: -
D). FINAL CONFIGURATION AND CONFERMATION: -
The final configuration is an iterative (repeated) process in which we set up all the
business requirements.
It is a transformation process that expands the base line solution defined during the
business blue print and base line configuration through multiple cycles until a
solution is found to deliver that satisfies the entire stated business requirement.
PREPARING FUNCTIONAL SPECIFICATION TO PASS ON THE

REQUIREMENTS TO ABAPER
TESTING THE CUSTOMIZATION

Preparing user manuals and configuration documents
4). FINAL PREPARATION: -

In this phase we complete the testing, system managements and the other related
activities to finalize our readiness to go live. For there more this phase also server
to resolve all the critical open issues.
A). UNLOADING THE SIMULATED DATA FROM THE LEGACY

SYSTEM.
B). CARRYING OUT INTEGRATION TESTING.
C). DECIDING CUT OVER ACTIVITIES AS CUT OVER STRATEGY:
In the cut over strategy we decide which activities can be stopped for time being so
that the other issues can be resolve which are essential for the project to go live.
PRE GO – LIVE END USER TRAINING.
5). GO – LIVE AND SUPPORT.

LIVE TRANSACTIONS WILL BE TACKING PLACE IN THE
PRODUCTION SERVER.
PRODUCTION SERVER
POST GO – LIVE TRAINING
S.L.A: - (SERVICE LEVEL AGREEMENT)
187
TOOLS: - (KINTANA) (AVINTIE) (EXPRESS.O.) (CLARIFY) issue tracking
tools.
SAME TIME  THIS IS THE “IBM” TOOL.

REMOTE ACCESS.
V.P.N: - (VERTUAL PRIVATE NETWORK FOR REMOTE ACCESS).
NOTE: - We need to transfer the data from the development to quality server by
transporting the custom rising request and work bench, request by using the
transaction code “SE09”.
Go to “SE09”.
Select the request type (CUSTOMIZING REQUEST)
Select the button display.
Select the required request and select the icon release directly.
NOTE: - To transport the request the basis guy has to set up transport management
system “TMS”.
 COUNTRY VERSION INDIA
188
 (CIN)
The tax component covers the most important loss and business practices specific
to India. There are basically ‘3’ types of taxes in India.
I). EXCISE DUTY

II). SALES TAX
III). WITH HOLDING TAX or “TDS” (Tax Deducted At Source)
I). EXCISE DUTY: -The system automatically calculates excise duties in

materials management, sales and distribution and post then in financial accounting.
We have the following types of excise duties in India.
a). BASIC EXCISE DUTIES : - (B.E.D)

This is the main type of excise duty in India which is levied on a wide range of
products.
b). SPECIAL EXCISE DUTY: - (X.E.D)

It’s a form excise duty in India levied on a limit number of goods, mostly luxury
goods including pan masala also.
c). ADDITIONAL EXCICE DUTY: - (A.E.D)

It’s a form of excise in India levied on a select range of products like sugar,
tobacco etc.
d). CESS: -
It’s a form of tax levied on the excise duty.
II). SALES TAX: -

This is a tax levied on the sale of a product which applies on the gross price of
goods inclusive of excise duty. There are ‘2’ different types of sales tax in India.
The interstate sales or subject to control sales tax (CST) where the rate is same
through out the country. On the other hand the intra state sales are subject to local
sales tax (LST) or (VAT) which defers from state to state.
189
S.D
Ex: - PURCHASING OUT GOING INVOICE
INCOMING INVOICE
PRICE = 100.00 ALLCOST- PRICE = 200.00
137.00
B.E.D = 14.00 (14% ON 100/-) OVER HEADS B.E.D = 28/-(14% ON
– 13.00 200-00)
S.E.D = 5.00 (5% ON 100/-) TOTAL – S.E.D = 10/-(5% ON
150.00 200.00)
A.E.D = 5.00 (5% 0N 100/-) PROFIT – A.E.D = 10/-(5% ON
50.00 200.00)
CESS = 1.00 (3% ON 24/-) PRICE – 200.00 CESS = 2/- (3% ON
48.00)
GROSS PRICE = 125.00 GROSS = 250.00
SALES TAX = 12.00 SALES TAX = 25.00
TOTAL = 137.00 TOTAL = 275.00
In the above case the input tax of “37.00 rupees” must be deducted from the out
put tax of “75.00 rupees” and the remaining “38.00 rupees” must be paid to the
government.
NOTE: -
In some industries the companies are only allowed to set off a portion of the input
duty against the out put duty. In this case the remainder of the duty is added to
material value. This is called “PARTIAL CENVAT CREDIT”.
FACTORY SALES
This process describes how the system handles from factories allowing the creation
of excise invoice which we have to send with each delivery that is subject to excise
190
duty. There are to scenarios, depending on weather we want to sent the commercial
invoice along with the delivery or data later date.
For the system to calculate the taxes we need to define the pricing procedures with
the corresponding condition types in the following way.
Go to V/08.
Define a pricing procedure.
Select the define procedure and go to control data.
Go to “new entries” and place the required condition types in the following way.
STEP NO-10: - Specify the condition type “PR00” for calculating the basic price.
STEP NO-20: - Specify the condition type “JASS” for calculating the assessable
value posted to finance and make it has statistical.
STEP NO-100: - Specify the condition type “JEXP” for calculating “BED” in
percentage.
This is to be calculated on the base price.
For this we have to specify the step no-10 for the field “from”.
STEP NO: - 101: - Specify the condition type “JEXQ” for calculating quantity
based “BED” and specify the “step no-10” for the field “from”.
STEP NO- 150: - Specify the sub total for calculating “BASE+BED” by
specifying the step no’s-10 & 101 for the fields “from and to”.
28-09-2011
STEP NO-200: - Specify the condition type “JEAP” for calculating A.E.D in
percentage on the basic price by specifying the step no-10 for the field “from”.
STEP NO- 201: - Specify the condition type “JEAQ” for calculating quantity
based A.E.D on basic price by specifying the step no-10 for the field “from”.
STEP NO- 250: - Specify the sub total for calculating “BASE+BED+AED” by
specifying the step no’s-150 & 201 for the fields “from and to”.
STEP NO- 300: - Specify the condition type “JESP” for calculating “SED” in
percentage on base price by specifying the step no-10 for the field “from”
STEP NO- 301: - Specify the condition type “JESQ” for calculating the quantity
based “SED” by specifying the step no-10 for the field “from”.
191
STEP NO- 350: - Specify the sub total for calculating “BASE+BED+AED+SED”
by specifying the step no’s-250 & 301 for the fields “from and to”.
STEP NO- 400: - Specify the condition type “JEXT” for calculating total “BED”
by specifying step no’s-100 & 101 for the fields “from and to”.
STEP NO- 401: - Specify the condition type “JEAT” for calculating total “AED”
STEP NO- 402: - Specify the condition type “JEST” for calculating total “AED”
STEP NO- 403: - Specify the sub total for calculating total excise duty by
specifying the step no’s 400 & 402 for the fields “from and to”.
STEP NO- 450: - Specify the condition type “JCEP” for calculating “CESS” in
percentage on the excise duty. For this specify the step no- 403 for the field
“from”.
STEP NO- 451: - Specify the condition type “JCEQ” for calculating quantity
based “CESS” by specifying the step no-403 for the field “from”.
STEP NO- 460: - Specify the sub total for the “COPY OF BASE VALUE” by
specifying the step no- 10 for the field “from”.
STEP NO- 500: - Specify the sub total for calculating gross price
(BASE+EXCISE DUTY+CESS) by specifying the step no’s 403 & 460.
STEP NO- 510: - Specify the condition type “JCST” for calculating “CST” on the
gross price. For this specify the step no- 500 for the field “from”.
STEP NO- 511: - Specify the condition type “JCSR” for calculating
“SURCHARGES ON CST”. For this specify the step no- 510 for the field “from”.
STEP NO- 520: - Specify the condition type “JLST” for calculating “LST” on the
gross price. For this we have to specify the step no- 500 for the field “from”.
STEP NO- 521: - Specify the condition type “JLSR” for calculating
“SURCHARGES ON LST”. For this specify the step no- 520 for the field “from”.
192
STEP NO- 600: -Specify the sub total for calculating total amount
(BASE+EXCISE DUTIES+SALES TAX) by specifying the step no’s 500 & 521
for the fields “from & to”.
SAVE THE PROCEDURE
NOTE: - When we save the billing document the excise duty shall be posted to one
G/L account and the sales tax shall be posted to separate G/L account for this we
have to assign separate account keys for the excise duty and sales tax condition
types. The standard account key for the excise duty condition types it is “EXD”
and for the sales tax condition types it is “MWS”.
NOTE: -
1). For all the excise duty condition types the condition class is “DISCOUNT OR
SURCHARGE” and the “PLUS OR MINUS” fields contains the value positive.
2). For the sales tax condition types the condition class is “TAXES” and the
condition category “TAXD”.
MAINTAINING CONDITION RECORDS: -

1). Go to “VK11” and maintain the condition records for “B.E.D, A.E.D, & S.E.D”
condition types.
2). The condition types “JEXT” “JEAT” & “JEST” are used to specify weather
the entire input excise duty has to be deducted.
If the requirement is to deduct the entire input excise duty, for these condition
types we have to specify the condition amount has 100% while maintaining the
condition records.
3). While maintaining the condition records for the sales tax condition types we
have to specify the tax code. For this first we have to create the tax code.
For creating the tax code go to “FTXP”.
THE PROCESS FLOW OF FACTORY SALES IF THE INVOICE IS SENT

ALONG WITH DELIVERY.
1). Create sales order “VA01” create.
2). Create delivery “VL01N” create complete picking and post goods issue.
3). Create invoice “VF01” creates (90000019)
4). EXCISE INVOICE: -
It’s a business document in India that we prepare when we issue the excise goods
from a manufacturing plant to be sold to a customer are to be transferred to another
plant. The excise invoice displays the goods we have issued to the customer and
states how much excise duty applies. The customer uses this excise invoice to
claim back the excise duty that he has already paid from the excise authority.
NUMBERING THE EXCISE INVOICES: -
193
The out going excise invoices have ‘2’ numbers.
‘1’ is an internal document number which is assigned immediately while creating
the excise invoice and the other number will not be assigned until we have verified
and posted it.
As for as the excise invoice is concerned, we have to number the out going excise
invoices in a sequential order starting each year from “1st APRIL” and must notify
the excise authority of the concerned location. The serial number must be printed
on each page of excise invoice. A series group governs each number range in the
“SAP” system for creating this go to
SPRO

LOGISTICS GENERAL

TAX ON GOODS MOVEMENTS

INDIA

BASIC SETTINGS

MAINTAIN SERIES GROUPS
While creating the series group we have to assign the corresponding excise
registration.
NUMBER OF LINE ITEMS FOR EXCISE INVOICE: -

Some states allow you to include only a limited number of items for each page of
excise invoice, especially if the excise invoices are to be printed on the pre
numbered forms.
To specify this in the “SAP” systems go to

SPRO

LOGISTICS GENERAL

194

INDIA

BASIC SETTINGS

MAIN EXCISE REGISTRATION
In the definition of excise invoice we have to specify the number of items to be
printed on each page of excise invoice.
CREATING EXCISE INVOICE: -

Go to the India localization menu by using the transaction code “J1IILN” and
select.
IN DIRECT TAXES

SALES AND OUT BOUND MOVEMENTS

EXCISE INVOICE

FOR SALES ORDER

J 1 I I N-OUT GOING EXCISE INVOICE CREATE/CHANGE/DISPLAY
Select the button create excise invoice from billing.
Specify the billing document number and posting data  (enter)
From the invoice the system copies the materials with the corresponding excise
duties in to excise invoice. For each material it displays
B.E.D, A.E.D, S.E.D & C.E.S.S and it also displays the total B.E.D, total A.E.D
total S.E.D, and total C.E.S.S.
(SAVE THE EXCISE INVOICE)
NOTE: - While creating the excise invoice we have to specify the series group and
excise group. While creating the excise invoice the system can automatically
propose a corresponding excise group and series group. For this the following
setting must be done.
SPRO

LOGISTICS GENERAL

195

INDIA

BASIC SETTINGS

OUT GOING EXCISE INVOICES

MAINTAIN DEFAULT EXCISE GROUP AND SERIES GROUPS
Go to “new entries” and enter the required combination of

SALES ORGANIZATION, DISTRIBUTION CHANNEL, SHIPPING POINT,
PLANT, EXCISE GROUP AND SERIES GROUP.
THE PROCESS FLOW OF FACTORY SALES IF THE INVOICE IS SENT

AT A LATER DATE
1). Create order.
2). Create delivery. (While creating the delivery specifies the delivery type has
“JF”) complete the picking and post goods issue.
3). Create Performa Invoice: - VF01 Create.
Specify the billing type “JEX” and create the Performa invoice with reference to
delivery and (SAVE IT),
4). CREATE EXCLUSIVE INVOICE: - Go to “J 1 I I N”.
Specify the button create excise invoice from billing for the field billing document
specify the Performa invoice number and create the excise invoice with reference
to that.
NOTE: - After creating the excise invoice, we have to create the commercial
invoice on the required date.
DEPOT SALES
We may sell the finished goods delivery from the place of manufacture to the
customer has we discussed in factory sales are first we may ship them to a separate
location for storage called depot from where we sell them to the customers this
second procedure is called depot sales.
196
The depot sales are handled differently from factory sales because of excise law.
The excise duty is payable when we sent the goods from the factory to depot, but it
is not levied again when we sell them to customers.
Some times when we make the final sales of the goods from the depot, the
price escalation (increase) could have happened with retrospective effect in such
senorious we need to pay the excise duty at the factory using on “A” certificate.
We need to register the “A” certificate details in “RG23D” register and recover the
excise duty from the customer.
THE PROCESS FLOW OF DEPOT SALES: -

1). Create “STO” from the factory to depot.
2). Create a sales order from the depot.
3). Create delivery.
4). Create invoice.
5). Create excise invoice for depot order.
For this from India localization menu select

IN DIRECT TAXES


EXCISE INVOICE

FOR SALES ORDER

“J 1 I J” CREATE/CHANGE/DISPLAY.
NOTE: - To take the print out of excise invoice.
IN DIRECT TAXES


EXCISE INVOICE

FOR SALES ORDER

“J 1 I P” PRINT.
NOTE: - To see the list of excise invoices select.
INDIRECT TAXES
197

REPORTS

J 1 I 7 – LIST EXCISE INVOICE.
NOTE: - For configure the “CIN” the following settings must also be done.
CALCULATION PROCEDURE: -
The “CIN” component is having “2” calculation procedures.
“1” is “TAXINJ” (4.7) and the other “TAXINN” (6.O) the procedure “TAXINJ” is
a routine based which will work on the logic what ever is there in that routine.
The other procedure “TAXINN” is a condition record based where we have to
maintain condition records for each tax condition type.
From the 4.7 version we are using the procedure “TAXINN”. We have to assign
this procedure to country “IN”.
For this go to
SPRO


FINANCIAL ACCOUNTING GLOBAL SETTINGS

TAX ON SALES AND PURCHAGES

BASIC SETTINGS

ASSIGN COUNTRY TO CALCULATION PROCEDURE
2). EXCISE REGISTRATION: - SPRO

LOGISTICS GENERAL

TAX ON GOODS MOVEMENT

INDIA

BASIC SETTINGS

MAINTAIN EXCISE REGISTRATIONS
198
A). EXCISE REGISTRATION: - Specify the required code for the excise
registration to be used in “SAP”.
B). REGISTRATION DISCRIPTION: -
C). ECC NUMBER: - Specifies the “EXCISE CONTROL CODE” number of the
organization.
D). EXCISE REGISTRATION NUMBER: - Specify a number assigned to each

premises are location that is registered has a manufacturing unit with the excise
authorities every plant with an excise registration number shall have its own excise
books.
E). We need to specify the concerned excise range, excise division and the
commisionarate in whose area the excise registration is located.
F). We need to specify weather the plant with this excise registration is liable to
pay A.E.D, S.E.D & C.E.S.S.
G). We need to specify weather the partial “CENVAT” credit is allowed for the
plant with this excise registration.
H). Here we also need to specify the number of items to be printed on each page of
excise invoice.
3). COMPANY CODE SETTINGS: -

SPRO

LOGISTICS EXCLUSION


INDIA

BASIC FUNCTIONS

MAINTAIN COMPANY CODE SETTINGS
199
A). Here we need to specify the date from which the excise invoice number range
come in to effect by using the field 1st month.
B). The field excise invoice selection days specifies the number of days to be
considered for the excise invoice selection.
For ex: - If the value for the field is “15”, at the time of generating the list of excise
invoices created for the last “15” days.
C). The field number of excise invoices to be selected specifies the number of
excise invoices that need to be selected in the excise invoice selection.
D). If we check the field rounding duty on procurement (purchase) the system
rounds the input excise duty.
E). If we check the field rounding duty on removal, the system round the out put
excise duty.
F). The field “CVD account” specifies the account to which the CVD amount shall
be posted.
NOTE: - The “COUNTER VEILING DUTY” is a form of excise duty levied on

the imports there by reducing any competitive advantages that they have over the
goods produced locally.
4). MAINTAINING PLANT SETTINGS: -

SPRO

LOGISTICS EXCLUSION


INDIA

BASIC SETTINGS

MAINTAIN PLANT SETTINGS
Here we need to specify weather the plant is a manufacturing unit or a depot.
200
If we de check the field “DEPOT”, it becomes a manufacturing unit where we have
to assign the corresponding excise registration.
5). EXCISE GROUPS: -

SPRO

LOGISTICS EXCLUSION


INDIA

BASIC SETTINGS

MATIAN EXCISE GROUPS
The excise group allows you to maintain a separate set excise registers and excise
accounts. The registers “RG23A, RG23C and PLA” serial number
(PLA: - profit &loss account) PLA serial numbers create an each excise group.
A). We have to create the excise group in the combination of required plant.
B). If the plant for which the excise group is created is a manufacturing unit, we
have to assign the corresponding excise registration.
C). If we check the field “EXCISE INVOICE DURING BILLING”, the system
automatically creates excise invoice the movement we save commercial invoice in
factory sales.
D). If the plant for which the excise group is created is a depot, we have to check
the field “DEPOT INDICATER”. In this case if we check the field “DEPOT
EXCISE INVOICE”, the system automatically creates excise invoice the
movement we save the commercial invoice in the depot sales.
6). MAINTAINING EXCISE REGISTERS: -
SPRO

LOGISTIS EXCLUSION


INDIA

201
BUSINESS TRANSACTIONS

EXCISE REGISTERS

SPECIFY “SAP” SCRIPT FORMS
Here we have to assign the “FORMS” to the corresponding excise registers.
8). MAINTAINING CHAPTER I.D: -

SPRO

LOGISTIS EXCLUSION


INDIA

MASTER DATE

MAINTAIN CHAPTER I.D’S
The chapter I.D specifies the corresponding schedules published by central board
of excise and customers and specifies the corresponding tax amount.
9). CUSTOMER MASTER SETTING: -
In the customer master we need to specify weather the customer is liable for tax or
not by using the field
“TAX CLASSIFICATION”
10). MATERIAL MASTER SETTINGS: -

In the material master we have to specify weather the material is liable for tax or
not by using the field “TAX CLASSIFICATION”.
NOTE: - To get the “TAX CLASSIFICATION” in customer and material master
records the following setting must be done.
SPRO


BASIC FUNCTIONS

TAXES
202

DEFINE TAX DETERMINATION RULES.
Go to “new entries” and enter the required tax country “IN” sequence ‘1’ and the
tax category “UTXZ”.
NOTE: - Depending on the requirement we can create out own values for the tax
classification of customer and material. For this go to
SPRO


BASIC FUNCTIONS

TAXES

DEFINE TAX RELEVANCY OF MASTER RECORDS.
A). CUSTOMER TAXES: -
Go to “new entries” and create the required tax classification of customer for the
required tax category.
B). MATERIAL TAXES: -

Go to “new entries” and create the required tax classification of material for the
required tax category.
203

Sap SD Notes

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Sap SD Notes

Enviado por

Direitos autorais:

Formatos disponíveis

SAP

SYSTEM APPLICATION IN DATA PROCESSING

ABAP BASIS FUNCTIONAL

‘BASIS’ – (S D) - SALES AND DISTRIBUTION

NDPs : - NEW DIMENTION PRODUCTS

CRM : - CUSTOMER RELATIONSHIP MANAGEMENT

SRM : - SUPLIER RELATIONSHIP MANAGEMENT

SCM : - SUPLIER CHAIN MANAGEMENT

SEM : - STSTEGIC ENTERPRISE MANAGEMENT

APO : - ADVANCED PLANING OPTIMINING

BW/BI : - BUSSINES WAREHOUSE / BUSSINESS INTELEGENCE

MDM : - MASTER DATA BASE MANAGEMENT

XI : - EXCHANGE INFRASTRUCTURE (INTER FASE TOOL)

WAS : - WEB APPLICATION SERVER (WEB ENABLED)

ENTERPRISE STRUCTURE: - Under the enterprise structure we have to maintain

2). Relation between sales organization and distribution channel one

ONE __ CARD ___ CARD

(I M G)- MEAN’S - IMPLIMENTATION GUIDE

SERVER: s d 1, CLIENT: 811, USER NAME: SAP USER, PASSWORD: India

DEFINING SALES ORGANIZATION

From easy access menu Select,(/NSMRO)

1). We need to save the data in customizing request.

6). Specify the name of sales organization.

7). Specify the currency.

8). Specify the calendar. (01)

9). If the sales organization is offering rebates for customers, we have

11). Save the sales organization.

Go to main menu, Select Delete all

/N – With a session a new screen comes.

/O – Its open a new.

The maximum session that can be similarly be opened is (“6"- sessions).

SPRO-DEFINE DELETE DISTRIBUTION CHANNEL COPY, DELETE,

Select the icon copy organizational object.

Make a copy from existing division to the required new division.

Come back to the previous screen and go to define division.

Select the define division and specified the required name of

Go to “NEW ENTRY’S” and create the sales office.

DEFINING COMPANY CODE

Select the icon copy organizational object.

IDESAG: International demonstration education system.

ASSIGNING DISTRIBUTION CHANNELS TO SALES ORGANIZATION

Go to “new entries” and specify the required combinations of sales

ASSIGNING DIVISIONS TO SALES ORGANIZATIONS

Go to “new entries” and specify the required combination of Sales Organization,

ASSIGN SALES OFFICE TO SALES AREA

DEFINING SALES GROUP

ASSINING SALES GROUP TO SALES OFFICE

b).Copy  Delete  Check  Plant.

c).Make a copy from an existing plant to the required new plant

d).Come back to the previous screen and go to define plant.

e).Select the define plant and go to detail’s.

f).Specify the required name and factory calendar.

g).Select the address icon and specify the required data.

Go to “new entries” and specify the required combinations are

ASSIGNING PLANT TO SALES ORGANIZATION

Go to “new entries” and specify the required combination of sales organization,

a).In a standard business practice, to assign a plant to sales

b).The relation between sales organization and plant is {MANY – MANY}.

2) MATERIAL MASTER DATA

3) CUSTOMER MARERIAL INFO RECORD

4) CONDITIONS MASTER DATA

CUSTOMER MASTER DATA

ONE CARD _ CARD