Professional Documents
Culture Documents
Sap SD Sun Surya Material 140302053227 Phpapp01 PDF
Sap SD Sun Surya Material 140302053227 Phpapp01 PDF
SAP
SALES & DISTRIBUTION
By
SUN SURYA
Technologies
SAP-SD
SAP-SD
Index
SL.NO TOPIC
1
2
6
7
8
9
10
11
12
13
14
15
16
PAGE NO
INTRODUCTION
SALES & DISTRIBUTION
MODEL OF ENTERPRISE STRUCTURE
BUSINESS PROCESS
DEFINITIONS
ASSIGNMENTS
MASTER DATA
CUSTOMER MASTER
MATERIAL MASTER
DOCUMENTS
SALES DOCUMENT HEADER
ITEM CATEGORY
ASSIGN ITEM CATEGORIES
DEFINE SCHEDULE LINE CATEGORIES
PRICING
DEFINE PRICING PROCEDURE (OVKK)
SYSTEM MODIFICATIONS
PRICING EXERCIES
FREE GOODS
SD CONFIGURATION SETTINGS
ROUTE DETERMINATION
OUTPUT DETERMINATION PROCEDURE
ASSIGN OUTPUT DETERMINATION PROCEDURE
TEXT DETERMINATION PROCEDURE
TEXT DETERMINATION PROCEDURE FOR SALES DOCUMENT
HEADER
PARTNER DETERMINATION PROCEDURE
ASSIGN RELEVANT PARTNER FUNCTIONS FOR PARTNER
DETERMINATION PROCEDURE
DEFINE PARTNER DETERMINATION PROCEDURE FOR SALES
DOCUMENT HEADER
INCOMPLETNESS PROCEDURE
MATERIAL DETERMINATION
CROSS SELLING
ITEM PROPOSAL AND PRODUCT PROPOSAL
CREDIT MANAGEMENT / RISK MANAGEMENT
SIMPLE CREDIT CHECK
AUTOMATIC CREDIT CHECK
TRANSFER OF REQUIREMENT AND AVAILABILITY CHECK
1
4
4
5
6
11
14
28
32
36
49
53
53
60
72
74
84
94
96
99
102
103
104
106
108
109
110
112
114
117
119
126
128
132
SAP-SD
SL.NO TOPIC
PAGE NO
17
18
COPY CONTROL
CONTRACTS
A) VALUE CONTRACT (WK1)
B) SERVICE CONTRACT (WV)
C) MASTER CONTRACT
137
141
143
145
148
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
CUSTOMER COMPLAINTS
CONSIGNMENT
INTER COMPANY / CROSS COMPANY SALES
THIRD PARTY SALES ORDER
INDIVIDUAL PURCHASE ORDER
DEFINE DELIVERY DOCUMENT
PACKING
RETURNABLE PACKAGING
BILLING DOCUMENT TYPE
MAKE TO - ORDER
VARIANT CONFIGURATION
REBATES
LOGISTICS INFORMATION SYSTEM (L I S)
STOCK TRANSFER ORDER (STO)
BATCH MANAGEMENT
BILL OF MATERIAL (BOM)
FAQ
150
154
156
157
159
160
165
167
169
173
174
185
189
193
200
203
204
SAP-SD
SAP
SAP
SAP : SAP is SYSTEMS APPLICATIONS AND PRODUCTS in Data Process
Different Modules in SAP are
1.
2.
3.
4.
5.
6.
----------------
HR
Stores / Purchases
Finance
Mechanism
Planning
SAP-SD
ERP Package
Finance
ORD MGMT
ORACLE
PEOPLESOFT
JDEDWARDS
BaaN
SAP R/3
U
X
X
X
U
X
X
U
X
U
INV
X
X
X
X
U
MFG
HR
X
X
X
U
U
X
U
X
X
U
ROOTS OF SAP
4 IBM people developed the SAP in 1972.
SAP R/3 : Its a German based product.
SAP AG : AG stands for Incorporation in USA
AG stands for Company in INDIA
IDES: Internet Demonstration and Evaluation System.
R/3 stands for Real time 3 tier architecture. Tier is nothing but a scope of
computer.
Single Tier: Single Tier means Standalone System. Ex: PC
Database Layer
Application Layer
Presentation Layer
Database Layer is Back end
Presentation Layer is Front end.
Two Tier Architecture:
Database Layer
Application Layer
|
|
|
|
CL1 CL2 CL3 CL4
|
CL5
(CL client)
WP
WP
WP
Despatcher
CL1
CL2
CL3
CL4
CL5
Ph: 040-69996677, 9246188809
SAP-SD
Implementation Partner
|
SAP Team
(Steering Committee)
Technical Consultants
Functional Consultants
Basis
Client
|
Ex: Dr Reddy Labs
(Core Team)
CEO
GM
HODS
End users
Feasibility study between Steering committee and Core Team.
BBP Business Blue Print.
Core Team gives their requirements to Steering Team,
Steering Committee prepares the Business Blue Print i.e called BBP.
Dev. Server
QIA
PROD
----> Issues
Config
+
Customize
BBP
Unit Testing
Product Support
Functional
Tools
Smoke Volume PerExrine
Lotus Notes
Remedy
SAP-SD
SAP-SD
BUSINESS PROCESS
Inquiry
|
Quotation
|
Purchase
Order
|
Sales
Order
|
Outbound
Delivery
|
Sales
Invoice
I.
II.
Master Data
(a) Customer Master
(b) Material Master
(c) Customer Material Info Records
(d) Pricing Condition Records
III
Configure Documents
(a) Sales Documents
(b) Deliver Documents
(c) Billing Documents
To Configure and Customize SAP : SAP design certain tools. That are
(a) ABAP (Work bench) - for Technical Consultants
(b) I M G (Implementation Guide) for Functional Consultants
(c) Administration (BASIS)
To navigate from screen to screen or transaction to transaction we use transaction
code or specified Path.
SPRO is a Transaction Code to go to IMG Tool.
PATH:
Logistics
Tools
Customizing IMG
SPRO Edit Project
SAP reference IMG
SAP-SD
SAP-SD
DEFINITION
1.DEFINE COMPANY (RCOMP) : Company is an highest Organizational Unit in the
enterprise structure. It represents Corporate Group.
PATH:
IMG
Enterprise Structure
Definition
Financial Accounting
Define Company
Select standard company (1000) click on copy as icon and define company by
changing data.
2.DEFINE COMPANY CODE (BUKRS):
Company code is an independent
Organizational Unit. Which is responsible look after Business Transaction in specified
geographical Area.
Which represents subsidiary of company which is having its own set of Database tables
from where we can generate reports like Balance Sheets and Profit & Loss A/cs and we
can consolidate those reports at this level.
Company can have no of company codes. That means company
codes should be assign to company. Company and Company codes define and
maintain by FICO.
PATH:
IMG
Enterprise Structure
Definition
Financial Accounting
Edit, Copy, Delete, Check Company Code
Edit Company Code Data.
Choose existing company code ex:1000 click on Copy as icon and define company
code by changing data.
3.DEFINE SALES AREA (TVTA) : TVTA is the Table for sales area. Sales Area is a
Logical Collection of 3 physical organizational units. That are :
(a) Sales Organization
(b) Distribution Channel
(c) Division.
We use Sales Area to maintain Master Data,to configure documents to process
documents (by Customer) and to generate reports. Sales Area defines which division
(Material) passes through which distribution channel under which sales organization to
the customer.
(A).DEFINE SALES ORGANISATION (VKORG): Sales Organization is the
independent Organizational Unit in SD module. Which is responsible to process
business transactions with in specified geographical area and also it is responsible to
look after lExal obligations with in the specified area.
SAP-SD
SAP-SD
PATH:
o
o
o
o
IMG
Sales & Distribution
Billing
Inter Company Billing
Define internal customer no by Sales Organization.
SAP-SD
10
IMG
Enterprise Structure
Definition
Sales & Distribution
Maintain Sales Office.
Choose existing Sales Office Ex: 1000,Click on copy as icon and define Sales Office
(Ex:MSO) Save it and go back.
5.MAINTAIN SALES GROUP (VKGRP): Group of Sales Employees or an Physical
Organizational Unit (Branch Office) can be define as a Sales Group. Sales Office
can have no of Sales Groups. That means Sales Group should be assign to Sales
Office.
PATH:
IMG
Enterprise Structure
Definition
Sales & Distribution
Maintain Sales Group.
Go to new entries and define Sales Group (SD1). Save it and go back.
Note: Sales Area, Sales Office, Sales Group and Shipping Point define and maintain
by
SD Consultants.
6.DEFINE PLANT (WERKS): Plant is an highest organizational unit in MM Module.
Which is responsible to make a plan and to manufacture materials. One Sales
Organization can sell materials from no of plants, that are define under different
company codes.Company code can have no of plants, that means Plant can be
assign to company code.
FAQ: Can we sub-divide Plant?
Ans: Yes, it can divide into different no of storage locations.
PATH:
IMG
Enterprise Structure
Definition
Logistics General
Define, Copy, Delete, Check Plant
Define Plant
SAP-SD
11
Choose existing Plant ex:1000,Click on copy as icon, define our plant by changing
data.
7.MAINTAIN STORAGE LOCATION (LGORT):
Storage location nothing but a sub-division of plant. Where we can
maintain Raw-Material, Finished Products and Scrap. Plant can have no of storage
locations that means Sales Location should be assign to Plant.Plant/Storage
Location combination assign to Warehouse Complex.
FAQ: Can we assign 1 storage location that has been define under 1 plant to another
plant?
ANS: No.
PATH:
IMG
Enterprise Structure
Definition
Materials Management.
Maintain Storage Location.
Specify the Plant under which the storage location is going to be defined in work area
go to new entries and define storage location (SL1) save it and go back.
Note: Plant and Storage Location defined and maintained by MM Consultants.
8.DEFINE SHIPPING POINT (VSTEL):
Shipping Point is an independent organizational unit in SD module. Which is
responsible to process inbound and outbound deliveries.
A delivery can/should take place from one shipping point. Every shipping point has
its own organizational data. Ex: Factory calendar, ship timings, picking, packing and
loading times etc.
Plant can have no of shipping points. That means shipping point should be assign to
plant.
PATH:
IMG
Enterprise Structure
Definition
Logistics Execution
Define, Copy, Delete, check shipping point.
Define shipping point.
Choose existing shipping point. Ex:1000Click on copy as icon and define shipping
point by changing the data. (MSP)
Note: Shipping Point can be group of employees or physical organizational unit
Which is responsible to process deliveries
SAP-SD
12
ASSIGNMENT
1.Assign Company Code to Company:
PATH:
IMG
Enterprise Structure
Assignment
Financial Accounting
Assign company code to company.
Choose our company code from position (MUL1) and assign company.
2.Assign Sales Organization to Company Code:
PATH:
IMG
Enterprise Structure
Assignment
Sales & Distribution
Assign Sales Organization to Company Code
Choose our company code from find button (MUL1) select it and click on assign icon
and choose our Sales Organization from the list. Save it and Exit.
3.Assign Distribution Channel to Sales Organization:
PATH:
IMG
Enterprise Structure
Assignment
Sales & Distribution
Assign Distribution Channel to Sales Organization.
Choose our Sales Organization (MUHO) from find button, select it, click on assign
icon and select distribution channels (PS and SS) from the list. Save it and Exit.
4.Assign Division to Sales Organization:
PATH:
IMG
Enterprise Structure
Assignment
Sales & Distribution
Assign Division to Sales Organization.
Choose our Sales Organization (MUHO) from the find button, select it, click on
assign icon and choose our divisions from the list. Save it and go back.
5.Set Up Sales Area (TVTA):
PATH:
IMG
Enterprise Structure
Assignment
Sales & Distribution
Set Up Sales Area.
SAP-SD
13
Choose our Sales Organization (MUHO) from find button, select it , click on assign
icon and choose 2 Distribution channels from the list, select one distribution channel,
click on assign icon and choose 2 Divisions from the list.
Repeat the same process for another distribution channel also. Save it and Exit.
6.ASSIGN SALES OFFICE TO SALES AREA:
PATH:
IMG
Enterprise Structure
Assignment
Sales & Distribution
Assign Sales Office to Sales Area
Choose our Sales Organization (Sales Area) from find button and select 1 Sales
Area, click on assign icon and choose our Sales Office from the list.
Repeat the same process for another 3 Sales Areas also. Save it and Exit.
7.ASSIGN SALES GROUP TO SALES OFFICE:
PATH:
IMG
Enterprise Structure
Assignment
Sales & Distribution
Assign Sales Group to Sales Office
Choose our Sales Office from find button, select it and click on assign icon, select our
Sales Group from the list. Save it and Exit.
8.ASSIGN PLANT TO COMPANY CODE (M M Assignment):
PATH:
IMG
Enterprise Structure
Assignment
Logistics - General
Assign Plant to Company Code.
Choose our Company Code from find button, select it, click on assign icon, select our
plant from the list. Save it and Exit.
9.SETUP SALES LINE: Sales line is the combination of single Sales Organization,
single Distribution Channel and single Plant. Sales line allows the system to sell
materials from different plants.
It is a pre-requisite for Cross Company Sales.
SAP-SD
14
PATH:
IMG
Enterprise Structure
Assignment
Sales & Distribution
Assign Sales Organization Distribution Channel Plant
Choose Sales Organization from the find button, select the combination, click on
assign icon and choose our plant from the list. Repeat the same process for another
combination also. Save it and Exit.
10.ASSIGN SHIPPING POINT TO PLANT:
PATH:
IMG
Enterprise Structure
Assignment
Logistics Execution
Assign Shipping Point to Plant
Choose our Plant from find button, select it, click on assign icon and select our
Shipping Point from the list. Save it and Exit.
ECO1 Transaction code for display the company structure.
PATH:
IMG
Enterprise Structure
Definition
Edit, Copy, Delete, Check Company Code
Copy, Delete, Check Company Code
Click on Organizational Structure
Click on Navigation
Choose our Company Code (Double Click or Choose)
SAP-SD
15
MASTER DATA
Master Data is pool up data. That is going to be created centrally in the System and
made available for documents.
Master data doesnt change frequently.
CUSTOMER MASTER: We maintain customer details in the form of master data.
Every customer master has a structure, that means it is made up with 3 sections i.e
(a) General Data Section (KNA1): In general data section customer personal
details like Name, Address, Postal Code etc is going to be captured.
KUNNR is the field in KNA1 table where the customer number is going to be stored.
(b) Company Code Data Section (KNB1): In company code data section customers
financial details like reconciliation A/C no, Bank A/C no, Insurance No etc., is going to
be stored.
Sales Area Data Section (KNVV): In Sales Area data section customers Sales,
Shipping, Billing details are going to be captured.
KNBP is a table for customers partner functions.
KNVS is a table for customers shipping details is going to be stored.
ACCOUNT GROUP: According to Partner Functions to each and every partner
one account group is going to be defined and maintained by FICO Consultants.
By using account group we can control customer master. By changing or assigning
Field Status to each and every field in the customer master.
FIELD STATUS:
SUPRESS: It hides the field from the Customer Master.
REQUIRED: Value should be maintained.
OPTIONAL: Value may be or may not be maintained.
DISPLAY: Field can be view.
PARTNER FUNCTIONS: In addition to natural partners business treats customers.
a)
b)
c)
d)
Customers (KU)
Vendors (LI)
Contact Persons (AP)
Sales Employee (PE)
Also as a business.
SAP-SD
16
Depending upon the partner type every partner has to fulfill /perform certain
mandatory partner functions. While making transactions with business.
Ex :
(A)
CUSTOMERS (KU)
--------------------------------------------SP
SH
BP
PY
|
|
|
|
Sold to Ship to Bill to Payer
Party
Party
Party
Partner Function
Number
Sold To Party
Ship To Party
Bill To Party
Payer
10
20
30
40
Number
Range
101-200
201-300
301-400
401-500
Current
Number
0
0
0
0
Extension
SAP-SD
17
Partner Determination:
Path: IMG
Sales & Distribution
Basic Functions
Partner Determination
Setup Partner Determination
Set up Partner Determination for Customer Master
Go to New Entries
Define Partner Determination Procedure
Ex:
Sold to Party
Select Partner Determination
Double Click on Partner Functions in Procedure
Go to New Entries
Partners
SAP-SD
18
SP
SH
BP
PY
XD02
VD02
Change
XD03
VD03
Display
If you use XD01 then Customer Master is going to be created centrally, that means
Company Code data should be maintained.
If you use VD01, then Customer Master is going to be created with specific to Sales
Area, that means Company Code can not be maintained.
PATH: Logistics
Sales & Distribution
Master Data
Business Partners
Customer
Create VD01 or XD01
ACCOUNT GROUP: Choose Account Group ex:0001 from Account Group overview
icon, double click.
CUSTOMER: (Internal or External) Specify Company Code and Sales Area.
Maintain data in General data session like Name, Address etc., maintain data in
Company Code data session.
Tab1 --- Accounting Management:
Reconciliation Account No: 14000 (nothing but a GL No.)
The value of this field used by the system to post Sales Revenues of this customer in
respective GL A/c.
Sort Key 003 : Sort Key can be used to list out line items of the Customer.
Tab2 --- Payment Transactions: Check Payment history records. This control
allows the system to record payment details of this customer in FD32 (Transaction
Code / Customer Master).
SAP-SD
19
SAP-SD
20
ITEM PROPOSAL / PRODUCT PROPOSAL: This is the concept by which user can
place the order on behalf of the customer have been rExularly purchases same
materials with or without default quantity. It works as a order entry tool. We create
item proposal discounts in VA51, where by using document type PV where we
create. When we list out all the materials that customer rExularly purchases and we
assign the document number in Customer Master Sales Area Data Section sales tab
item proposal field. During Sales Order processing user uses option PROPOSAL
ITEMS.
ACCOUNTS AT CUSTOMER: Assign account number if Business maintains with
Customer (As a Vendor).
UNITS GROUP: Ex: PAL
purchases.
EXCHANGE RATE TYPE: Assign exchange rate type for customer. System uses
exchange rate type, if Invoice is going to be settled in currency other than document
currency.
CUSTOMR PROCEDURE FOR PRODUCT PROPOSAL (PP CUST PROC): Ex :
A) PRODUCT PROPOSAL
B) CROSS SELLING
together with document procedure for product proposal. System determines product
proposal or cross billing.
Cross selling is the concept by which business can offer combination material for
ordered material. Ex: for Computer, Computer stand can be suggested.
PRICE GROUP: Ex: 01 Bulk Buyer
Grouping of the Customer to carryout Pricing.
Ex: Condition Type (KO20) used in pricing procedure.
PATH: IMG
Sales & Distribution
Basic Functions
Pricing
Maintain Price Relevant Master Data Fields
Define pricing groups for customers
Go to new entries and define price groups, Save it and Exit.
CUSTOMER PRICING PROCEDURE: Ex: 1 standard Assign pricing procedure to
customer, the value of this field used by the system as a one of the factor to
determine pricing procedure.
FAQ: How System determines pricing procedure?
ANS: System determines pricing procedure by taking 3 factors into consideration
(a) Sales Area
(b) Document Pricing Procedure (VOV8 of OR)
(c) Customer Pricing Procedure (= default pricing procedure)
SAP-SD
21
PATH: IMG
Sales & Distribution
Basic Functions
Pricing
Pricing Control
Define and Assign Pricing Procedure
Define Customer Pricing Procedures.
Go to new entries and Define customer Pricing Procedure, save it and Exit.
PRICE LIST: Ex: 01 Wholesale
Price List can be defined for group of customers to carry out pricing.
PATH: IMG
Sales & Distribution
Business Function
Pricing
Maintain Price
Relevant Master Data Fields
Define Price List catExories for Customers
Go to new entries and define Price List catExories by customers, save and Exit.
CUSTOMER STATISTICAL GROUP: Ex: 1 Relevant for statistics.
Grouping of the Customer to Generate statistical reports from LIS Logistics
Information System (Open Data Warehouse).
PATH:
IMG
Logistics General
Logistics Info System
Logistics Warehouse
Updating
Updating Control
Setting : Sales & Distribution
Statistics Groups
Maintain Statistics Groups for Customers.
Go to new entries and define Statistics Groups, save it and Exit.
SAP-SD
22
SAP-SD
23
a) System first checks customer material info records. If Plant has been
maintained, then it will take from Customer Material Info records or else it will
go to b
b) Customer Master Ship to Party or else it will go to c
c) Materials Master or else Plant should be determined manually during Sales
Order Processing.
CHECK RELEVANT FOR POD: Proof of Delivery is the concept by which business
can map ACKNOWLEDGEMENT business.
In normal business process business delivery goods to the customer and customer in
term sends acknowledgement for the goods that he received, then only business
raises Invoice. To map this business scenario, proof of delivery can be used in SAP,
that prevents the user from raising Invoice unless and until user confirm
acknowledgment from the customer.
POD TIME FRAME: Specify the time in days up to which system has to wait to
receive POD confirmation, after that period system automatically allows the user to
raise Invoice by assuming that goods reached to the customer place, then user
releases the document by using transaction code VLPODQ (Automatic POD
confirmation).
CHECK ORDER COMBINATION: It is a pre-requisite to combine number of Sales
Orders that belongs to same ship to party for collective processing.
CHECK COMPLETE DELIVERY REQUIRED BY LAW: This control determines
whether Sales Order should be splitted into different deliveries.
PARTIAL DELIVERY PER ITEM:
Blank
A
B
C
D
The value of the field determines whether line item can be splitted or not.
MAXIMUM PARTIAL DELIVERIES: 9
The value of this field restricts Max partial deliveries for line item in the Sales Order,
that means Sales Order line item can be splitted by X / 9.
CHECK UNLIMITED TOLERANCE: This indication allows un-limited tolerances for
Sales Order line item QTY.
UNDER DELIVERY TOLERANCE AND OVER DELIVERY TOLERANCE: Specify
the limit in % for Under Delivery Tolerance and Over Delivery Tolerance. Ex: 10%
and 10%
Note: If unlimited Tolerance check, then limit need not be specify.
TRANSPORTATION ZONE: The value of this field used by the System to determine
ROUTE for a line item in the Sales Order as a one of the factor.
SAP-SD
24
BILLING TAB:
Check subsequent Invoice processing: This control determines that manual
posted invoices should be printed out.
Check Rebates: Active this control as a pre-requisite, if the business want to map
rebates.
Check Price Determination: This indicator allows / is a pre-requisite to determine
price for customer hierarchy.
Invoicing Dates and Invoicing List Dates: Assign factory calendar to generate
invoices and invoice list.
Invoice List: Invoice list is the list of invoices, that particular customer payer should
pay. The list given to collection agent who us the responsible to collect money from
customer for which he will be paid factoring discount.
FAQ: If Customer Payer accepts invoices and invoice list how do you configure it?
ANS:
CALENDERS
PATH: To define Factory Calendar
IMG
Sales & Distribution
Master Data
Business Partners
Customers
Billing Document
Define Billing Schedule.
(a)
go
Back.
Define Holiday Calendar: Click on change icon
Click on create icon
Specify public holiday calendar ID with
Description
Validity Periods, click on assign public holiday
And choose our public holiday from the list and click on assign public
holiday.
Save it and go back.
(b)
SAP-SD
25
INCOTERMS: CIF (Costa, Insurance and freight) Assign Incoterms to change freight
Condition Type (KF00) used by the system in pricing procedure.
International Chamber of Commerce of terms of liability for freight in transit.
The terms and conditions defined by ICC that should be avoid by shipper and ship to
party.
Terms of Payment: Ex: 0001 Payable Immediately Due net
0002 With in 14 days 3% Cash Discount
With in 30 days 2% Cash Discount
With in 45 days due net.
Assign Payment terms for customer / payer according to which customer should pay
the money and Cash Discount will be granted. Condition type SKTO used in pricing
procedure.
PATH: IMG
Sales & Distribution
Master Data
Business Partners
Customers
Billing Documents
Define terms of payment
Go to new entries and define payment terms.
Path is same for incoterms also.
SAP-SD
26
SAP-SD
27
FAQ: If ship to party wants to receive shipment on particular day. Ex: Saturday.
How do you configure it?
ANS: By defining Factory Calendar.
PATH:
IMG
Sales & Distribution
Master Data
Business Partners
Customers
Shipping
Define Customers Calendar
In the same path define goods receiving hours. Ex: 001 week days.
Assign these goods receiving hours in General Data Section unloading points tab
and goods receiving hours option.
FAQ: Can you create Customer Material info records from customer master?
Ans: Yes
PATH: XD02 or VD02 Sales Area Data Session
Environment
Then, Customer Material information
FAQ: Can you block customer from customer master?
ANS: Yes
PATH: DX02 or VD02 Sales Area section, Extras, Blocking Data, specify the
particular area.
SAP-SD
28
MATERIAL MASTER
FICO Settings: Define and Assign Fiscal Year variant to company code. Fiscal
Year is nothing but a Financial Year.
a. K4 Calendar Year / Dependent. Ex: Jan Dec
b. V3 Year Dependent. (Apr Mar)
Path:
IMG
Financial Accounting
Financial Accounting Global setting
Fiscal Year (a) Maintain Fiscal Year variant
Assign Company Code to a Fiscal Year variant.
Choose our company code and assign Fiscal Year variant. Save it and Exit.
Define and Assign Chart of Accounts to Company Code: Company Accounts is
nothing but a list of General Ledger Accounts.
Path:
IMG
Financial Accounts
General Ledger
Accounting
G/L Accounts
Master Records Preparations
Assign Company Code to Chart of Accounts.
Choose our company code from position button and assign chart of accounts as a
INT (International). Save it and Exit.
M M Settings
Assign Materials type at company code level (OMSY).
Choose our company code and assign Fiscal Year (Current Year) then specify
posting period accordingly to Fiscal Year variant. If it is K4 then every 3 months as a
period.
Check ABP (Allowed Back posting Periods). Save it and go back.
QTY / Value updating (OMS2): In SAP materials catExorized as a finished
products, semi finished products, Raw Materials etc.,
Ex: FERT Finished Products
HALB Semi-finished Products
ROH Raw Material
HAWA Trading Goods
VERP Packaging Material
LEIH Returnable Packing Materials
NLAG Non Stock Material
PIPE Pipe Line Materials
Materials are valuated usually at company code level or plant level.
SAP-SD
29
Choose FERT from position button and click on QTY / Value updating control
button. Choose valuation area (Plant) material type (FERT) and check QTY
updating.
Save it and Exit.
Maintain material master is the involvement of MM, PP, QM, SD, WM, FICO
consultants. Material Masters are maintained with specific to SD division.
Material Master can be maintain in MM module as well as SD module depending
upon material type.
If it is finished Product, then Material Master can be maintained in both areas. If it is
HAWA, usually that is going to be maintained in SD.
MM01 Create
MM02 Change
MM03 Display
PATH:
Logistics
Material Management
Material Master
Material
Create (General)
MM01 Immediately OR
Logistics
Sales & Distribution
Master Data
Products
Material
Other Material
MM01 Create Material
Internal assignment depending upon the material type,
Industry Sector Mechanical Engineering
The material that we are going to create belongs to certain industry sectors.
Ex: Chemical Industry, Pharmaceutical Industry etc.,
Material Type: Ex: Finished Product
The material that we are going to created belongs to certain material type.
Ex: Finished Product, Raw-Material, Semi-finished Product etc.,
Depending upon the material type system can understand whether material can be
procured internally or externally. If it is FERT, then both procurements are possible.
If it is a HAWA only external procurement possible so that depending upon the
material type system proposes relevant views.
Click on select views and select
SAP-SD
30
Basic Data
Sales : Sales Organization Data 1 and 2
Sales : General / Plant Data
General Plant Data / Storage 1
General Plant Data / Storage 2
Accounting Data 1
Click on Organizational levels. Specify our Plant, Storage Location, Sales
Organization, Distribution Channel
Click on continue
Maintain Data in Basic Data 1
Specify description
:
Specify Base Unit of measure: (EA)
Specify Material Group
: 00104
Grouping of the Materials to generate statistical reports and to carryout pricing.
Assign Division: 4W (SD Division)
General item catExory Group: By default it is NORM depending upon the material
type system proposes general item catExory group. The values of this field used by
system as a one of the factor to be determine sales order line item as a Standard
item, Free of Charge item, Service item, Value item and Text item.
Ex:
SAP-SD
31
Minimum Delivery Qty: Ex: 20 each. The order should be delivered for this
stipulated Qty, otherwise system issues warning message.
Delivery Unit: 2 Boxes.
Conditions: Maintain Sales Price (PROO). Ex: 1 Box = 1000/Sales : Sales Organization 2: Ex: 1 Relevant for statistics.
Grouping of the materials to update LIS with the transactions of the material.
Volume Rebate Group: Ex: 01 Max Rebate
The value of this field used by system for rebate settlement.
Material Pricing Group: Ex: 01 Standard Parts.
Grouping of this materials to carryout pricing. Condition type K020 used by the
system in pricing procedure.
Account Assignment Group: Ex: 03 Finished Goods
Grouping of the materials to post Sales Revenues, Sales Deductions, Freight
Revenues and Tax Revenues in respective GL A/cs.
It is a pre-requisite for FICO and SD intExration along with ACCOUNT GROUP OF
CUSTOMERS.
General Item CatExory Group and Item CatExory Group: NORM, the value of this
field used by the system as a one of the factor to determine item catExory for a line
item in the Sales Order,
FAQ: How system determines Item CatExory for a line item in the Sales Order?
ANS: System determines item catExory for a line item in the Sales Order by taking 4
factors into consideration.
a) Sales document type (that end users enter). Ex: TA/OR +
b) Item CatExory Group (from its Material Master). Ex: NORM +
c) Usage of the Material (of the Material). Ex: NIL +
d) Higher level item catExory (of the line item) Ex: NIL
= default item catExory (of line item). Ex: TAN Standard item.
Sales : General / Plant:
Availability check. Ex: 02 Individual requirements.
It is a checking group of availability check. The value of this field defines whether
and how system has to carry out TOR and availability function for this material if it is
placed in the Sales Order and Delivery document. If it is to be carried out, then what
kind of requirement it has to generate whether individual requirements or collective
requirements.
If it is individual requirements, then system creates demand with MRP for each Sales
Order.
SAP-SD
32
With individual requirements we can have a clear view of the requirements for this
material in CO09.
If it is summarized requirements, then system create demands with MRP for this
material at a time. Ex: Weekly once i.e. Monday, when the business raises number
of Sales Orders this kind of requirement to be advisable.
It also defines how long system has to wait i.e. as long as MPR elements (Purchase
Requisitions, Purchase Orders etc) existed or up to RLT time (Replenishment lead
time).
RLT is the time that required by business to procure materials internally or externally.
Together with Checking Rule it controls availability check.
Check Batch Management: This indicator is a pre-requisite if the material is to be
processed batch wise.
Transportation Group: Ex: 0014 On Palettes
Grouping of the materials that required similar requirements for transaction. The
value of this field used by the system as a one of the factor to determine ROUTE.
Loading Group: Ex: 001 Crane
Grouping of the materials that required similar requirements for loading. The value of
this field used by the system as a one of the factor to determine Shipping Point.
Sales Text: Plant Data / Storage 1 and Storage 2
Maintain data in this 2 views, if the material is to be managed in warehouse.
Extend the material into these 2 views to initiate the stock in storage location or plant.
ACCOUNT1: S Standard Price
V Moving average Price
Depending upon the material type system proposes standard price or moving
average price. The value of this field used by system to valuate the stock.
If it is standard price, then system valuates the stock with out taking inventory
movements into consideration.
If it is moving average price system valuates the stock by taking inventory
movements into consideration.
It represents cost price. Condition type VPRS used by system in pricing procedure to
calculate profit margin.
Maintain standard price. Ex: 1000
SAP-SD
33
DOCUMENTS
Document is nothing but a data container. Document can be used as a proof of
transaction and they can be used to capture transactional details.
To simplify business/ processes documents has been catExorized into 3 sections
with respect to Sales and Distribution.
a.
b.
c.
SALES DOCUMENTS
DELIVERY DOCUMENTS
BILLING DOCUMENTS
SALES DOCUMENTS:
Sales related Business data is going to captured into sales documents.
Sales document types: To map different different processes/transaction, sales
documents has been catExorized into 4 sections.
1.PRE SALES ACTIVITIES: Ex: Inquiry (AF/IN)
Quotation (AG/QT)
2.SALES ORDER:
1.Contracts
2.Schedule Agreement.
The difference between contracts and scheduling agreement is
Contracts: These doesnt have Schedule Agreement.
Schedule Agreement: Schedule Agreements do have schedule times.
a. CONTRACTS (K): Qty contract (KM/NMS)
Value Contracts (WK1, WK2)
Service Contracts (WVSC)
Rental Contract (MV/QP)
Master Contract (GK)
c. SCHEDULING AGREEMENT: Scheduling Agreement with delivering
Schedule called as BL and
Schedule Agreement with delivery order called as LZM
4.CUSTOMER COMPLAINTS:
Ex: Credit Memo requests (G2)
Debit Memo requests (L2)
SUN SURYA TECHNOLOGIES
SAP-SD
34
Returns (RE)
Subsequent Free of charge Deliveries (SDF)
Free of Charge Delivery (CD) Samples
Invoice correction request (RK)
Del
Bill
IN/AF
Imm
Del
QT/AG
OR/TA
LF
LF
LF
F2
F2
F2
BV/CS
Imm
Del
LF
SO/RO
Imm
Del
F2
To define different types of Sales documents, SAP has given one standard format.
That standard format has an architecture i.e every Sales Document is made up with
3 types
a. Header Level CatExory( VBAK):
At a header level CatExory Data like.. Master Data, Organizational Data etc. is going
to captured. The Data that is going to be captured at header level applies to whole
document. Header Level CatExory is controlled by document type.
Ex: AF, KG, TA, BV, SO etc.
b. Item Level CatExory (VBAP):
Every Sales Documents should have Line Items. Those Line Items contains Data
Ex: Plant, Storage Location, Shipping Point, Route, Net Price etc and the Data
applies to the particular Line Item only. Sales Order Line Items controlled Item
CatExory.
Ex:
TAN
TANN
TAD
TATX
TAW
TAB
TAS
(Standard Item),
( Free of Charge)
(Service Item)
(Text Item)
(Value Item)
(Individual Purchase Order)
(Third party Item)
SAP-SD
35
Depending upon the Item CatExory Sales Order Line Item can be controlled with
respective pricing, Inventory management, TOR. (Transfer of Requirement).
c. Schedule Line CatExory (VBEP):
Require Delivery Date and Qty to be confirmed is called Schedule lines.
Every Line Item in the Sales Order may have one or more than one Schedule lines.
Schedule Lines of Line Item causes to create delivery document for Line Item, that
means it acts as basis to create delivery document. Depending upon the transaction
type document may have activated or de-activated schedule lines. Schedule Lines
are controlled by Schedule Lines CatExory.
Ex: CP - deterministic the MRP.
CN - No MRP
VBAK
Sold to Party :
Ship to Party :
HLC
Net Ord
Val
P O No:
LIST
Item
Material
No
10 Rice
20 Wheat
30 Tooth Paste
40 Soaps
50 Good Day
60 Service (for Mixer)
70 Papad
735
P O Dt:
Quantity
Item
No
100 Kg
200 Kg
100 Gm
10
1
X
1 Pack
Material
10 Rice
20 Wheat
30 Tooth Paste
35 Tooth Paste
40 Soaps
50 Good Day
60 Service
70 Papad
TOTAL
Req Del
Date
Order
QTY
100 Kg
200 Kg
Today
Today
Tomorrow
Today
1 Pack
Tomorrow
PR
PO
Order
QTY
100 Kg
200 Kg
100 Gm
25 Gm
10
1
X
1 Pack
100
200
100
25
100 I L C
10
100
100
735
Confirmed
Qty
100 Kg
100 Kg
100 Kg
1/2 Pack
1/2 Pack
GR
Pruchase
Goods
Requisition Purchase Order Received
Price
INV
SLC
VP
Vendor
Invoice Pmt
SAP-SD
36
INVOICE (F2)
Item
No
Picked
Qty
100 Kg
100 Kg
100 Gm
25 Gm
10
1
X
1/2 Pkt
Material
Picked Price
Qty
10 Rice
100 Kg
20 Wheat
100 Kg
30 Tooth Paste 100 Gm
35 Tooth Paste 25 Gm
40 Soaps
10
50 Good Day
1
60 Service
X
70 Papad
1/2 Pkt
Total
Less : Discount
Total Price
100 Standard
100 Standard
100 Standard
25 Standard + Free of Charge
100 Standard
10 Standard
100 Service
50 Third Party Item
585
25
560
SAP-SD
37
SAP-SD
38
General Control:
Reference Mandatory: The value of this field makes preceding document as a
mandatory to this document type.
Ex: For QT IN is mandatory
For TA QT is mandatory.
Check Division: Blank No dialog
1
- Dialog
2
Error
The value of this field determines system response when item division defines with
header division.
Ex: Warning or Error
ORDER PROBABILITY: 100%
Together with customer Probability VD01, System calculates the chances of
completion of line Item with the Sales Order
Ex : If it is
Inquiry
AF
30%
Quotation
AG
70%
TA
100%
CREDIT CHECK
Blank
No Credit limit check
A
Run simple credit limit check and warning message.
B
Run simple credit limit check and error message.
C
Run simple credit limit check and delivery block.
D
Credit management Automatic credit control.
Assign whether and how system has to carry out Credit Check for the Sale
Document:
Ex: No Check or simple Credit Limit Check. And Automatic Credit Check
In business granting Materials on credit is quite common. While granting Credit to
the customer the business should be very cautious otherwise Business may be
Bankrupted, so as to avoid this kind of situation SAP delivered a Feature called
Credit Management/ Risk Management by using this tool whereas Credit checks can
be carried out while processing the document. Once the Credit Limit has been
exceeded the system response according to the value that will specify in this field i.e.
A to C
(for simple credit check) OR
D- Credit Management: Automatic change according to OVA8 to define Automatic
credit check)
SAP-SD
39
SAP-SD
40
SAP-SD
41
Pre-requisites:
1. Number ranges should be same.
2. Document catExories A,B,C,D,I,K and L only can be reference as a
alternative sales document types with each other. Indicator should not be set.
3. Sales Documents should be blocked.
4. Un-check item division.
5. Commitment date should be same.
6. Billing plant type should be same.
7. Payment guarantee procedure should be same.
8. Payment Card plan type should be same.
9. Checking group should be same.
Variant: In IMG we define variants with held of ABAPers. Ex: Screen Variants by
which default values, default Tabs can be proposed for a sales document type.
Display Range: UALL All Items
UHAU Main Item
UMAR Selected Item
The value of this field determines which line status can be displayed during Sales
Order processing.
Function Code for Overview Screen: Ex: UER1 Press Enter to go to General
Over View. The value of this field determines which Tab system has to propose by
default.
Once the user press enter after specifying document type and sales area.
facilitates order entry.
It
Quotation Messages: The value of this field reminds the user about the open
quotations if they are existed at header level or item level in a popup box, then the
user will have a choice to complete those open quotations first or the user can ignore
the open quotations and he can proceed.
Outline Agreement Messages: The functionality is the same like above field, but
system shows message about outline agreements. Additional reference to all
contracts for partner is authorized to release. In business Sold to Party or Ship to
Party may be authorize to release the contracts. If the partner is existed in other
contracts and if they are open, then system takes those documents also into
consideration and shows the message.
Message Master Contract: The value of this field reminds the user about the open
master contracts for contract documents. It is relevant for master contracts.
Product Attribute Messages: The value of this field determines system responses if
product attributes are going to be change during Sales Order processing whether
warning or Error messages.
SAP-SD
42
SAP-SD
43
Shipping Section
This section deals with shipping activities.
Delivery Type: Ex: LF. Assign Delivery Document Type LF for this Sales
Document types. So that system automatically proposes this delivery document type
LF when outbound delivery is going to be initiated with reference to this Sales
Document Type.
Delivery Block: Assign delivery block for sales document header so that system
automatically proposes delivery block for all line items in the sales document as
some one in the business has to check sales document before initiating outbound
delivery.
It is relevant for Free of Charge deliveries.
Shipping Conditions: Assign shipping conditions to sales document header. The
system automatically proposes for all the line items in the Sales Order.
The value of this field used by the system as a one of the pre-requisite to determine
shipping point.
This value will be given priority while determining shipping point. It is relevant for BV
and RO.
Shipping Cost Info Profile: Ex: Standard. In IMG we define shipping cost info
profile in which we can specify transactions planning point, shipping type, shipment
cost calculation procedure etc., That is used by system for shipment and
transportation.
Immediate Delivery: Ex: Blank Create Delivery Separately.
A Create Delivery Immediately.
X Create Delivery Immediately if Qty confirmed today.
The value of this field causes to create immediate delivery document for sales
document.
SAP-SD
44
BILLING
This section deals with billing activities for this document type.
Delivery Related Billing Type: Ex: F2
Order Related Billing Type : Ex: - F2
Assign document type for Delivery Related Billing Type and Order Related items in
the Sales Order. System automatically proposes billing document type F2 for this
sales document type when the billing process is going to be initiated.
Inter Company Billing Type: Ex: IV. Assign billing document type IV the system
automatically proposes for inter company billing transactions.
Billing Block: Assign billing block at sales document header level the system
automatically proposes for all the line items in the sales document before initiating
invoice process has some in the business has to check sales document before
initiating invoice process with reference to this sales document type. It is relevant for
Credit Memo request and Debit Memo request sales document types.
Condition Type line Items: Ex: 02. Assign condition type that is used by system as
a base to carryout pricing based on the Sales Order line item cost.
It has a intExration with FICO.
Billing Plan Type: Ex: 01 Milestone Billing
02 Periodic Billing
Assign billing plan type for Sales Document header level that applies to all line items
in the Sales Order.
Ex: Periodic Billing. The entire value to be billed in full
amount on each billing plan date. Ex: It can be user rental contracts or maintenance
contracts.
Milestone Billing: The total value to be billed is distributed between the individual
planning dates. It can be a percentage amount or absolute amount. Ex: It can be
used Projects.
Payment Guarantee Procedure: Together with Customer Payment guarantee
procedure system determines payment guarantee procedure for a line item in the
payment guarantee procedure in the Sales Order.
System activates receivable risk management component in FI Module.
Payment Card Plan Type: Ex: 03 Payment Card. Assign Payment Card plan for
Sales document line item in the Sales Order.
Checking Group: Ex: 01 Standard. Assign checking group to carry out checks on
payment cards.
Requested Delivery Date / Pricing Date / Purchase Order Date: This section
deals with default dates in sales documents for deliveries, Pricing etc.,
SAP-SD
45
Lead Time in Days: Ex: 7. System adds current date to the 7 days and proposes
required delivery date in the sales document.
Date Type: Ex: 1 Day
2 Week
3 Month
Date format for schedule lines can be assigned.
Proposed Pricing date based on the requested delivery date. The value of this field
specifies which date system has to propose by default for pricing.
Proposed Valid from Date: The value of this fields specifies when the document
should come into force.
Check Propose Delivery Date: This indicator takes current date and proposes as a
delivery date. It is relevant for Cash Sales and Rush Sales.
Check Propose Purchase Order Date: This indicator proposes current date as a
Purchase Order date.
CONTRACT
This section deals with contract documents. Ex: SC Service Contract.
Pricing Procedure Condition Header: Ex: PABROI. Assign pricing procedure for
contract sales document header level i.e. proposed by system automatically for
contract.
Pricing Procedure Condition Item (PABR02): Assign pricing procedure for contract
document item level that applied to line item.
Contract Profile: Ex: 0001 One Year Contract. In IMG we define contract profiles
in which we define contract starting date, ending date, cancellation rules etc., that is
going to be used by this contract document type.
Billing Request (IRC Debit Request Memo): Assigning Debit Memo Request to
compensate business in service contracts.
Grand Referencing Procedure: In IMG we define referencing procedure. Ex:
SDGK Standard. That can be used by the system to assign lower level contracts
to master contracts. Through this referencing procedure system can understand
which fields can be copies which fields can be changes.
It is relevant for master contract document type GK.
Contract Data Allowed: The value of this field specifies whether contract data is
allowed for this document type or not.
If you assign X then the changes that we are going to carried out at header level is
not going to be effected at item level.
SAP-SD
46
If you assign Y that the changes that we are going to carried out at header level
applies to item level.
Follow Activity Type: Ex: 0003 Sales Letter. We specifying follow up activity type
for contract sales document type that is to be created when sales activity is defines
as follow up action which is going to be proposed when the user initiate the creating
of follow up action from follow up action work list. Ex: 0003 Assign to Rent of
Contract (MV).
Path to Create Follow Up Actions outline agreements.
Contract
Subsequent Functions
Follow up actions and maintain selection screen
Click on Execute and Choose all contracts with the follow up action.
Create Sales Activity and go to edit follow up actions then the dialog box will display
in which system proposes sales activity 0003 save it then system automatically
created follow up activity type for selected contracts.
Subsequent Order Type: Ex: AG. Assign follow up order type automatically
created as a subsequent processing. Ex: A maintenance contract is a validity period
of 1 year for that contract follow up order type AG is assign which is to be created 2
weeks before the contract end date. Then go to outline agreements Contracts
Subsequent Functions Follow up Actions, then system automatically
proposes follow up order type AG that has to be assign to this document type.
Check Partner Authorization: In contracts some partners are authorized to enter to
release the contracts. The value of this field checks whether the partner is
authorized to release the contracts or not.
AA Sold-to-Party authorized to release the contract.
AW Ship-to-Party authorized to release the contract.
Check Update Lower Level Contracts: This indicator causes to update lower level
contracts that are assign to Master Contracts.
Availability Check: Business transaction type OR, SO has to confirm the quantities
system has to carry out availability check. In SAP availability check can be
configured by following 3 methods.
a. Availability Check using ATP (Availability to Promise) Logic / Planning.
b. Availability Check against Product Allocation.
c. Rule based availability check.
In Rule based availability check system carries out GATP (Global Availability to
Promise) in APO system (Advanced Planner and Optimizer).
SAP-SD
47
CLIENT LANDSCAPE
SCM
SEM
APO
R/3
CRM
BIW
SRM
R/3 transfer the requirements of the Sales Order or the delivery through APO system
thru CIF (Central Interface) and APO carries out GATP and returns the results of the
GATP to R/3.
If system has to carried out GATP in APO system then in R/3 sales document
header level at availability check session in business transaction field document type
should be assigned.
It is not relevant for CS and RO.
Define number ranges for Sales Documents:
Path:
IMG
Sales & Distribution
Sales
Sales Documents
Sales Document Header
Define Number Ranges for Sales Documents (VN01)
Click on change intervals icon.
Click on Insert intervals icon and define 2 number ranges 1 is with external option
and another one is with out external option.
Go to define sales document types (VOV8) choose sales document type and assign
those 2 number keys in number system section.
Define Purchase Order types: Here purchase order types
DFUE Data Transfer
MUEN Orally
SCHR Written
TELE By Telephone.
Define Order Reasons (OVAU): Go to new entries and define Order Reasons.
SAP-SD
48
SAP-SD
49
Define Usage Indicators: Here scheduling Agreements line item usages defined.
Ex: Spare Parts, Sample, Serialized Parts.
Assign Sales Area to Sales Document Types: There are 3 Sales Areas in the
Business. Ex: 0001, 01 and 01. If Sales Document Type OR is authorized under
this particular Sales Area then configuration setting:
1. Grouping together Sales Organization
Sales Organization
0001
Distribution Channel
01
Distribution Channel
01
Distn Channel
01
Division
01
SALES AREA 2: Ex: 0002, 01, 01. If Sales Document type OR to be assigned to
this Sales Area.
1.Grouping together Sales Organization
Sales Organization
0002
Distribution Channel
01
Distribution Channel
01
Division
01
Division
01
Division
02
Division
01
SAP-SD
50
SAP-SD
51
Completion Rule: It is for Quotation and Contract Items. The value of this field used
by the system to establishment completion rule for a line item in the sales document.
Completion rule defines status of the item as a Completed or being processed
together with a control that is Update Document Flow at copy control of Sales
Document to Sales Document at item level catExory level. This field establishes
completion rule.
Special Stock: In Business certain stock to be created as a special stock for special
business concerns. Ex: Make-to-Order, Configurable Materials, Consignment Stock
and Returnable Packaging.
Consignment Issue: Ex: W
Billing Relevance:
A Delivery Related Billing document
B Relevant for Order Related Billing Status according to Order Quantity.
The value of this field specifies whether the item catExory is relevant for billing or not.
If it is relevant then how the billing document should be updated.
Billing Plan Type: The value of this field specifies billing plan type for this item
catExory. Ex: For Project Related Items. 01 Milestone Billing
SAP-SD
52
SAP-SD
53
Transaction Flow:
Incompletion Procedure: Ex: 20. In IMG we define incompletion procedure for
sales document item level by which system reminds the user about the fields in
which values has not been maintained while saving the document.
Partner Determination Procedure: Ex: N. In IMG we define partner determination
procedure by which system determines relevant partner functions at item catExory
level. Ex: Ship to Party.
Text Determination Procedure: Ex: 01. In IMG we define text determination
procedure for sales document item level by which system proposes text for a line
item in the Sales Order.
Item CatExory Statistics Group: Ex: 1. Assign update rule to update LIS at item
catExory level.
Screen Sequence Group: Ex: N. The value of this field specifies which screen in
which sequence that are to be displayed at item level during document processing.
Status Profile: In IMG we define status profile by which we can specify system
statuses and user statuses.
Check Create P O Automatically: In third party and individual purchase items
system has to create P O automatically. This indicator triggers automatic creation of
P O. It is relevant for ALE (Application Link Enabling).
Bill of Material / Configuration: This section deals with BOM and Configurable
Materials.
Ex: TAQ, TAE, TAP (BOM items).
TAC (Configurable Item).
BOM items are nothing but structured materials or recipes structured materials made
up with number of components as a header item as well as sub-items.
The value of this field specifies or determines configuration stratExy for the line item.
That means it can under stand whether correct dependences selected or not.
Material Variant Action: Ex: 2 Replace Configurable Material (Only in Append).
The value of this field determines system response when system finds material
variant for selected characteristics.
ATP Material Variant: The value of this field determines whether system has to
carryout ATP check on material variants.
Structure Scope: Ex: D Configuration Possible with BOM exposure. The value of
this field causes to expose BOM during Sales Order processing as a single level
BOM, Multi level BOM, Configuration BOM exposure.
Application: Ex: SD01 Sales and Distribution. Specify the application area where
the BOM is to be exploded.
Check Variant Matching: This indicator determines variant configuration.
SAP-SD
54
SAP-SD
55
Define default values for material type depending upon the material type that the user
uses while creating material master system automatically proposes general item cat
Exory group in the material master. So that general item v\catExory groups should
be assigned to material types. Ex: FERT = NORM.
Define Item Category Usage: Item catExory usage controls system response during
document processing. If the system does not refer to a material but to a text item.
Ex: Batch Split, Text Item, Service Item with / without billing and Free.
While determining item catExories for a line item in the Sales Order system requires
the usage of the material. That means the line item has specific usage according to
that usage it has to respond.
Ex: CHSP Batch Split
CSEL Cross Selling
FREE Free Goods
PACK Shipping Unit
TEXT Text Item
VCTR Value Contract.
Assign Item Categories (VOV4): Every Sales Document line item is going to be
determine automatically by taking 4 factors in to consideration
Sales
Document
Type
Item
CatExory
Group
Higher
Level
CatExory
Usage
Default
Item
CatExory
AF
NORM
NIL
NIL
AFN
AG
NORM
NIL
NIL
AGN
TA
NORM
NIL
NIL
TAN
TA
NORM
FREE
TAN
TANN
Define Reasons for Rejection: In business customers may reject certain items or
business can also reject certain items so that the reasons for the rejection should be
specified in the document for statistical information purpose. Go to new entries and
define reasons for rejection.
Date:14.07.2006
Define Schedule Line CatExories (VOV6):
Path: IMG
Sales & Distribution
Sales
Sales Document
Schedule Lines
Define Schedule Line CatExories
CP Deterministic MRP
SUN SURYA TECHNOLOGIES
SAP-SD
56
Business Data :
Delivery Block: Assign Delivery Block for Sales Document line items at schedule
line catExory level so that system automatically proposes delivery block while
initiating outbound delivery for a line item in the Sales Order.
Movement Type: Ex: 601 Goods Issue : Delivery. In Inventory Management
Material movements are controlled / signified by movement types depending upon
the movement only system can understand what type of delivery is going take place
Movement Type 1 Step: In inventory movement the stock updating should take
place at a time at receiving storage location and delivering location in Replenishment
Deliveries (STOs) or manually they should be updated. If automatically, system has
to update the stock in receiving and delivering plant level then that is called as a
Movement Type 1 Step.
Ex: NC Inter Company Replenishment. Movement Type 643 and Movement Type
1 Step 645.
SALES
DOCUMENTS
TYPE
[ TA ]
+
MATERIAL TYPE
[ FERT ]
GENERAL ITEM
CATEXORY
GROUP
[NORM]
+
USAGE
[NIL]
+
HIGHER LEVEL
GATEXORY
[NIL]
DEFAULT
DEFAULT
MRP
ITEM CATEXORY +
TYPE
= [TAN]
[ PD / NIL ]
SCHEDULE
=
LINE
CATEXORY
[ CP ]
SCHEDULE CATEXORY
ORD TYPE [NB]
TOR
AVT CHECK
PROD ALL
SAP-SD
HAWA
HAWA
57
TA
+
BANC
+
NIL
+
NIL
TA
+
BANS
+
NIL
+
NIL
ND
NB
Order Type: If the material is Third Party item then system automatically has to
create purchase requisition for that particular line item in the Sales Order. To create
Purchase Requisition automatically one standard purchase requisition document type
(NB) should be assigned at schedule line catExory level. That assignment triggers
automatic creation of Purchase Requisition.
Ex: For Schedule Line catExory Type CB Individual Purchase Order
CS LEx
Item CatExory: Ex: O Standard. Specify the item catExory of purchase requisition
type by which system can understand whether it is individual purchase order or third
party.
Ex: 0 Standard
5 Third Party
Account Assignment CatExory: Assigning Account CatExory (E or 1) by which
account determination take place for third party item.
Check Item Relevant for Delivery: This indicator creates schedule line for a line
item in the Sales Order.
Purchase Requisition Delivery Schedule: It is relevant for individual purchase
order items as system has to create delivery schedule (Goods Issue Date, Loading
Date, Material Availability Date, Transportation Planning Date for Delivery Date).
SAP-SD
58
Transaction Flow:
Incompletion Procedure: 30 Delivery Related Schedule Line. In IMG we define
incompletion procedure and assign to schedule line catExory level by which system
reminds the user about the fields in which values has not been maintain while saving
the document.
Check Requirement / Assembly: This control defines that system has to transfer
the requirements for this transaction as well as system starts to create assembly
order. It is a pre-requisite for TOR.
Check Availability: This indicator specifies that system has to carry out availability
check for this transaction.
Check Product Allocation: This indicator specifies that product allocation is active
for this transaction.
Assign Schedule Line CatExories: SAP automatically determines schedule lines
for a line item in the Sales Order by taking 2 factors into consideration.
Item CatExory + MRP Type = Default Schedule Line CatExory.
TAN + PD = CP
TAN + NIL = CP
TAN + ND = CN (Individual P O)
TAN + NB = CS (Third Party)
FAQ: What are the control parameters of Sales Document ?
ANS: Header Level CatExory, Item Level CatExory and Schedule Line CatExory.
SAP-SD
59
VA11
VA21
AF -> AG
->
TA :
LF
F2
:
:
:- - - - - - - - - - - > MBIC - [Stock Initialization]
Inquiry AF (VA11):
Path: Logistics
Sales & Distribution
Sales
Inquiry
VA11 Create
Specify Sold to Party, Validity Period and Quantity.
Item CatExory AFN
Schedule Line CatExory AT
VOV8 of AF or IN (Header Level CatExory of Inquiry)
SD Doc CatExory
:A
Probability
: 30%
Screen Sequence Group : AG
Transaction Group
:1
Doc Pricing Procedure
:A
Function Code for Overview Screen : UER2
VOV8 of AFN (Item Level CatExory of Inquiry)
Completion Rule : A
Pricing
:X
Check Business Item
Check Schedule lines allowed.
Item CatExory Assignment:
AF + NORM + NIL + NIL = AFN
VOV6 of AT (Schedule Line CatExory of Inquiry)
No Schedule Lines for Inquiry
Quotation AG (VA21):
Path: Logistics
Sales & Distribution
Sales
Quotation
VA21 Create
SAP-SD
60
Specify document type AG or QT and click on create with reference, specify Inquiry
Number, Click on selection list, click on copy icon process document.
Alternative Item: By using this concept business can offer alternative item for line
item in the Inquiry or Quotation. The user has to specify line item number in item
catExory AGN.
VOV8 of AG or QT (Header Level CatExory of Quotation)
SD Doc CatExory
:B
Probability
: 70%
Screen Sequence Group : AG
Transaction Group
:2
Doc Pricing Procedure
:A
Function Code for Overview Screen : UER2
VOV8 of AGN (Item Level CatExory of Quotation)
Completion Rule : AB
Pricing
:X
Check Business Item
Check Schedule lines allowed.
VOV6 of BN (Schedule Line CatExory of Quotation)
No Schedule Lines for Quotation.
Sales Order:
Path: Logistics
Sales & Distribution
Sales
Order
VA01 Create
Click on create with reference. Specify offer number (QT)
Click on Selection List.
Click on copy
Item CatExory TAN
Schedule Line CatExory CP
MMBE Stock Overview.
Specify Material Number, Plant, Storage Location and click on execute icon.
Go to MBIC for initializing the Stock.
Specify movement type 561
561 Receipt Per initial entry of stock balances into un-restricted use.
561E Receipt Per initial entry of stock balances into un-restricted Sales Order.
561K Receipt Per initial entry of stock balances into un-restricted consignment.
561M Receipt Per initial entry of stock balances into un-restricted RTP.
561O Receipt Per initial entry of stock balances into un-restricted with sub
contracting.
SUN SURYA TECHNOLOGIES
SAP-SD
61
561Q Receipt Per initial entry of stock balances into un-restricted Project.
561V Receipt Per initial entry of stock returnable pack at customer.
561W Receipt Per initial entry of stock consignment at customer
Specify Plant and Storage Location and Click on enter.
Outbound Delivery (VL0IN)
Path: Logistics
Logistics Execution
Outbound Process
Goods Issue for Outbound Delivery
Outbound Delivery
Create
Single Document
VL0IN with reference to Sales Order.
Specify Shipping Point, Selection Date (on or after confirmed Qtys Date in the S O).
Specify the Order Number
Specify the Picking Qty
Click on PGI
Invoice (VF01)
Path: Logistics
Sales & Distribution
Billing Document
VF01 Create
Generate Reports:
Path: Logistics
Sales & Distribution
Sales Information System
Standard Analysis
MCTA Customer
And maintain selection screen.
SAP-SD
62
PRICING
Sales Order Configuration:
Revenue Account
Determination
T O R / A V T Check
SALES DOCUMENT
Text Determination
Procedure
Header
Item
Partner Determination
Functions
Credit Management /
Risk Management
TAX
TA
TAN
Schedule CP
Line
Output Determination
Shipping Point
Determination
Pricing
Customer
Material
Pricing Procedure:
V/08
BASE PRICE
( - ) DISCOUNTS
ACCESS SEQUENCE
CONDITION TABLES
V/07
V/03
LINK
Data Combination
Values
----> WH+FM+PL1+SA1
1000
990
( + ) FREIGHT CHARGES
----> WH+FM+PL2+SA1
1100
( + )TAXES
----> WH+RT+PL1+SA1
=
|
|
|
Condition Records (VK11)
1050
|
|
|
Condition Types (V/06)
SAP-SD
63
In the above condition types some are mandatory and some are optional,
Mandatory : Base Price and Taxes
Optional : Discounts and Freight Charges
Customer : WH Whole Sales, RT Retailer
Material : FM Fast Moving. SM Slow Moving
Plant
: PL1 Plant 1, PL2 Plant 2
Sales Area: SA1 Sales Area 1, SA2 Sales Area 2
Pricing: Price is the calculation of costs. (for Internal purpose), calculation
revenues (for External purpose).
of
To calculate price for particular item certain pricing elements are going to be
participated. Among those pricing elements some are mandatory (Base Price and
Taxes), some are optional (Discounts and Freight). To determine value for particular
pricing element business has to take certain COMBINATIONS into consideration
that are LINKED to pricing elements. To map this pricing procedure in our SAP
system we use a tool called CONDITION TECHNIQUE which is having certain
components that are
Procedure
+
Condition Type
Access Sequence
Condition Table
Condition Records
SAP-SD
64
Step Counter Condition Description From To Manual Manda Statistical Print Sub Requi Alternative Alternative Accoun Accu
Type
tory
formula
10
15
20
25
30
0 PR00
0
1 K004
2 K005
3 K007
Gross Value
Base Val
10
15
15
15
Counter=0
Counter=0
Counter=1
Counter=2
Counter=3
From 10
From 15
From 15
From 15
Condition Type
Description
PR00
Price
K004
Material
K005
Customer / Material
K007
Customer / Discount
Description: System copies description of condition type from its description (V/06)
Ex: PR00 = Price
K004 = Material
K005 = Customer / Material
K007 = Customer / Discount and so on..
From and TO: These two columns are for 2 purposes
a. As a base to the condition type: From column can be used as a base to the
condition type for calculating further value.
ting
Key
rals
SAP-SD
Ex:
Step
10
15
20
65
Counter Condition Type
0
PR00
0
0
K004
Description
Price
Gross Value
Material
From
10
15
b. TO: As a range between the steps From and To columns can be used to
specify the range between same condition types. So that depending upon the
condition types system deducts or adds the total value of those condition
types from specifies common source.
Ex:
Step Counter
Cond Type Description From To
15
0
Gross Value
10
20
0
K004
Material
15
25
0
K005
Customer/Mat 15
30
0
K007
Customer Disc 15
35
0
Total Disc Val 16
34
Check Manual: This indicator specifies that specific condition type can be
determined manually during Sales Order processing.
Ex: Discount, Freight Charges.
K004
Manual
K005
K007
Gross Value
PR00 Price
Statistical: If the particular condition type specifies as a statistical then the value of
that condition type will not be taken into net value calculates. That condition type
used only for information purpose.
Ex: VPRS Cost should be specified
SKTO Cash Discount also should be statistical
Print: The value of this field specifies whether line item can be printed or not.
If it is
Blank It was not printed
X System Prints at item level
S System prints totals level.
Sub-Total: The value of this field determines where the sub-totals are to be stored.
Ex: KOMP KZWI1
KOMP KZWI 2
Gross Value 1
Total Discount 2
1
2
SAP-SD
66
(or)
Counter
Condition Type
VO02
Rebate Discount
23 or 24.
SAP-SD
67
SAP-SD
68
SAP-SD
69
SAP-SD
70
SAP-SD
71
Check Value: This indicator allows the user to change condition value during Sales
Order Processing.
Check Qty Relation: It specifies whether conversion factor for the units of measure
in condition of this type can be changes during document processing.
Ex: 1 Box = 10 each items maintained in condition records. During Sales Order
processing it can be change as a 20 each items.
Calculation Type: This indicator controls to change calculation type during Sales
Order processing.
Master Data Section
Valid From: The value of this field specifies when this condition type is valid in
pricing procedure.
Valid To: The value of this field specifies how long this condition type remains valid.
Reference Condition Type: Another condition type can be referenced to this
condition type. So that condition records can be maintain only for referencing
condition types.
Ex: MW15 MWST can be reference
AMIZ AMIW can be reference
Reference Application: Ex: V Sales & Distribution. Specify application area of
referencing condition type.
Pricing Procedure: So as to use Condition Supplement Feature one pricing
procedure should be defines in V/08 and assigned to condition type in this field. The
system automatically applies condition supplement feature during Sales Order
processing.
Deletion from Data Base: The value of this field determines system response if the
condition record is going to be deleted from the database. If it is blank, so that
condition record can not be used in pricing. If it is A, condition record deleted from
database then system gives a popup box in which it will ask whether the condition
records can be deleted or deletion indicator is set. If you set B, condition records will
be deleted but system shows popup box only if the condition records contain
condition supplements.
Check Condition Index: Condition index can be created for particular condition type
to maintain condition records.
Check Condition Update: Together with condition index Condition Update allows
to restrict the usage of the condition type for limited Sales Orders or for particular
condition base value or condition value.
Scales Section: Scale is nothing but a range of Qty or Value. In the business when
Qty is going to be increased discount should be increased.
Scale Basis: Assign Scale basis for condition type based on the pricing element.
Ex: C Qty
Check Value: Ex: A Descending. Assign checking rule for scale rates.
SUN SURYA TECHNOLOGIES
SAP-SD
72
Scale Type: Assign Scale type depending upon the pricing element.
A Base Scale
B To Scale
C Graduated to interval scale.
Scale Formula: To map different cinereous in scales with the help of ABAPers
routines can be written in VOFM transaction code.
Unit of Measure: Assign unit of measure the system automatically proposes for
scales while maintaining condition records. Ex: PAL Pallet Discount.
Control Data 2 Section: It controls the currency conversion where the currency in
the condition records valid with document currency. Ex: In VK11 condition amount
maintain as a INR and Sales Order raised to US Dollars. To calculate condition
value in the document, system multiplies the amount that results from condition
records by the item Qty. Ex: 1 item cost = 1 Dollar. Order Qty = 10 items then
condition value is 10 dollars. This indicator controls whether system carries out
currency conversion before or after the multiplication. If you check this field then
system converts condition value into document currency after multiplication. If it is
uncheck the system converts the condition value into the document currency before
multiplies.
Check Accruals: This indicator specifies that system post the amounts resulting
from this condition type to Financial Account as a accruals. If it is check then system
shows this condition type in Sales Document as a statistical condition. Ex: Freight
Conditions.
Check Invoice List Condition: This indicator specifies that this condition type is for
internal costing purpose.
Check Inter Company Billing: This indicator specifies that this condition type is for
inter company billing. Ex: PI01 Absolute Amount and PI02 Percentage Amount.
Check Service Charge Settlement: This indicator specifies that trading contract
conditions should be calculated using the Vendor billing document.
Check Variant Condition: This indicator specifies that this condition type is variant
pricing for configurable materials. Ex: VA00 Absolute Amount and VA01
Percentage Amount.
Qty Conversion: This field controls the Qty conversion during determination of
condition basis. It is only relevant for calculation rule C and it is relevant if the
sales Qty unit and condition Qty unit as identical/ If it is de-activated the condition
basis Qty is converted via Qty to the stock keeping unit, this means that the condition
Qty is determined for planned factors. So that changes to the conversion in the
delivery or the orders are not taken into account. If it is activated then system takes
document Qty that means actual Qty.
Exclusion: Specify Exclusion indicator so that system automatically excludes the
condition types that falls below this condition type during Sales Order processing.
Ex: It is relevant for Base Price. So that system automatically excludes all discount
condition types that falls under this base price.
SUN SURYA TECHNOLOGIES
SAP-SD
73
SAP-SD
74
SYSTEM MODIFICATIONS
Define Pricing Procedure based on Customer classification. Customers are
classified as a A,B,C in KNVV Table/ KLABC field.
Create Condition Table V/03 with KLABC.
Path:
IMG
Sales & Distribution
Business Functions
Pricing
Pricing Control
Define Condition Tables
Condition: Allowed Fields
Create Condition Tables
And specify condition table number and choose field Standard Price (STPRS).
STPRS not existed in the field catalog. When the field is not available in the field
catalog then the field can be included in the field catalog by going to condition :
allowed fields option.
Go to New Entries and include field STPRS.
Data Flow
Enterprise
Structure
Master Data
RCOMP
KNA1
KNB1
BUKRS
KNVV
KNVP
VKORG
KNVS
VTWEX
MARA
Pricing Communication
Structure
Sales
Document
Delivery
Document
Billing
Document
VBAK
LIKP
VBRK
VBAP
VBEP
LIPS
VBRP
KOMK
+
KOMP
SPART
=
KOMG
WERKS
LGORT
VSTEL
SAP-SD
75
Path:
IMG
Sales and Distribution
System Modifications
Create new fields (Using condition technique)
New fields for Pricing
Select use include for new fields in dictionary (Batch Determination)
Specify KOMP in Database field table field
Click on display
Click on Append structure
Click on New Append structure, extend the description and continue
Specify description and specify component ZZSTPRS and specify the component
type STPRS save it.
Click on Local Object and click on check (F2)
Click on Currency / Quantity fields and specify reference table VBAP and Ref field
WAERK, save it, check it and activate it.
Include STPRS in KOMG
Click on display
Click on Append structure
Click on New Append structure, extend the description and continue
Specify description and specify component ZZSTPRS and specify the component
type STPRS save it.
Click on Local Object and click on check (F2)
Click on Currency / Quantity fields and specify reference table VBAP and Ref field
WEARK (Currency Key), save it, check it and activate it.
Go to Conditions : allowed fields
Go to New Entries and include ZZSTPRS save it and go to create condition tables,
specify Condition Table Number and Create condition table with Standard Price click
on create, local object.
SAP-SD
76
Pricing Exercises
1) Condition Exclusion Group: In the Business it is quite common to have number
of discounts that can be granted to the customers due to certain privilExes. If
Business grants number of discounts then Business incurs loss in the profit margin.
So as to avoid this kind of situation SAP delivered a feature called Condition
Exclusion Group by which can offer best or least favorable condition value or type to
the customer.
Configuration Settings: Define Exclusion condition.
Path:
IMG
Sales and Distribution
Business Functions
Pricing
Condition Exclusion
Condition Exclusion for Group of conditions
a. Define Condition Exclusion Groups: Go to New Entries and Define
Exclusion group with description. Ex: Y001 save it and go back.
b. Assign Condition types to the Exclusion Groups: Go to New Entries and
assign K004, K005 and K007 for Exclusion Group Y001 save it and exit.
c. Maintain Condition Exclusion for Pricing Procedure: Choose our Pricing
Procedure, click on Exclusion, go to new entries and specify sequence
number and assign condition exclusion procedure.
A Best Condition between condition types.
B Condition with in the condition type.
C Best Condition between the Two exclusion groups.
D Exclusive
E Least favorable with in the condition type.
F Least favorable between the Two exclusion groups.
Select A and assign condition exclusion group Y001 and save it.
Go to VA01 and raise the Sales Order and go to conditions and check the values.
Condition Supplement: When the Business wants to give certain discounts
irrespective of any combination till certain period, condition supplement can be use.
For every pricing procedure Base Price is mandatory. So that system automatically
proposes discounts by default along with Base Price in the Sales Order.
Configuration Settings:
1. Define Pricing Process for condition supplement in V/08.
Go to New Entries and assign Condition Type with out any controls.
10 0
PR00
15 0
K004
20 0
K005
SUN SURYA TECHNOLOGIES
SAP-SD
77
1
11
21
31
41
50
1000
900
800
700
600
500 and so on..
and go to VA01 and raise the Sales Order for 50 items and go to conditions screen
and check scale effect.
2.b) Graduated Scales: In graduated scales system averages the Base Price
depending upon the order Qty. It is a pro-business condition type. Hidden costs can
be mapped.
Ex: If Order Qty = 25
Scale Rate is up to
10 = 300
20 = 290
30 = 280
SAP-SD
78
1 10 Items
nd
2 10 Items
rd
3 5 Items
Total
10*300 = 3000
10*290 = 2900
5*280 = 1400
----------25
7300
-----------
There fore for each item 7300/25=292/Configuration Settings: Go to V/06 and define condition type PR02
Access Sequence K005
Condition Class B
Calculate Type C
Manual Entries D
Check Item condition
Scale Basis
C
Check Value
Blank
Scale Type
D (VV IMP) and save it.
Go to V/08 and include PR02 instead of PR00. Change PR00 to manual and PR02
is mandatory. Save it and go to OVKK and assign condition type PR02.
Go to VK11 and maintain condition record for PR02. Select condition line item go to
goto button Scales
To
10
300
20
290
30
280 and save it.
Go to VA01 and raise the Sales Order for 25 Items and go to condition screen and
check condition amount for each item.
SAP-SD
79
Header Conditions
When the Business wants to give certain discounts or when it wants to
charge freight charges for all the line items in the Sales Order (for particular
transaction) Header conditions can be defined.
Header Condition doesnt have access sequence and access sequence can not be
maintained. So that values for header condition should be determined manually
during Sales Order Processing.
Values of Header conditions applies to whole items in the Sales Order.
Ex: HA00, HB00, HD00 etc.,
Configuration Settings:
Go to V/06 and define HA00 Percentage Discounts
Access Sequence NIL
Condition Class A
Calculation Type A
Plus or Minus X
Check group condition
Check Header Condition
V/06 of HB00 Discount Value
Access Sequence NIL
Condition Class A
Calculation Type B
Plus or Minus X
Check group condition
Manual Entries - Blank
Check Header Condition
Go to V/08 and include HA00 and HB00 between the discount condition steps with
manual option. Save it.
Go to VA01 and raise the Sales Order.
Go to item condition screen and check HA00 and HB00 values. System doesnt
propose HA00 and HB00 condition types as those are manual with Header condition
types. So that values should be determined manually.
Go to Sales Order over view screen and click on display doc. Header details icon or
go to goto button, Header, Conditions and specify HA00 and HB00, click on Activate
: New Document Pricing button.
Go to item condition screen and check HA00 and HB00 values.
3.b) HM00 Net Order Value: If the Business wants to charge Net Order Value
manually during Sales Order processing. HM00 condition type can be determined
V/06 of HM00.
Access Sequence NIL
Condition Class B
Calculation Type B
Check Group Condition
Manual Entries Blank
Check Header Condition
And go to VA01 and raise the Sales Order.
SUN SURYA TECHNOLOGIES
SAP-SD
80
SAP-SD
81
7) EDI1 and EDI2 Customer Expected Price and Value: In the Business,
customers express Price for the material. Business may accept it and reject it.
Customers expected price can be received thru EDI system or manually can be
entered. If there is any difference the customer expected price then billing document
can be blocked for that Sales Order. Then concern person in the business can
release the Sales Document by accepting or rejecting customer expected price.
V/06 of EDI1
Access Sequence NIL
Condition Class B
Calculation Type C
Condition CatExory - J
Check Header Condition
Check Item Condition
V/06 of EDI2
Here calculation Type is B remain same as EDI1
Go to V/08 and include EDI1 with manual option and Alt formula for Condition Type =
8 and include EDI2 also in the same procedure.
Go to VA01 and raise the Sales Order and include EDI1 value manually.
Go to VL01 and VF01 and raise Invoice, system blocks the Document.
Go to V.25
Path: Logistics
Sales and Distribution
Sales
Information System
Work lists
V.25
Release Customer Expected Price
Specify User Name and Sales Area
Click on Execute.
Select Sales Orders and click on release.
Save it and go back.
Go to VF01 and raise the Invoice and save it.
8) VPRS Cost: VPRS condition type can be used to calculate profit margin. This
condition copies cost price from the material master (Accounting 1 View). Check
determine cost should be activated at V0V7 of TAN.
V/06 of VPRS
Access Sequence NIL
Condition Class B
Calculation Type C
Condition CatExory G
Manual Entries - D
Check Item Condition
Go to V/08 and include condition type VPRS with statistical check
Sub-total = B
Requirement = 4
The next step include profit margin with Alt formula for Condition Type = 11 and save
it.
Go to VA01 and raise the Sales Order.
SUN SURYA TECHNOLOGIES
SAP-SD
82
AMIW
PRICE GROUP
CONDITION TYPE
02
200/-
SALES ORDER
CUSTOMER PRICE GROUP
02
NET VALUE
AMIW
AMIZ
NET VALUE
160
200
40
200
ITEM 10 ITEM 20
100
60
125
75
25
15
125
75
Configuration Settings:
In VD01 Customer Price Group should be maintained in the Sales Area Data
Section.
V/06 of AMIW
Access Sequence K020
Condition Class A
Calculation Type B
Puls / Minus Blank
Check Group Condition
Manual Entries - D
Check Item Condition
V/06 of AMIZ
Access Sequence K020
Condition Class A
Calculation Type B
Manual Entries C
Reference Condition Type AMIW
Check Reference Application
Go to V/08 and include AMIW with statistical
Requirement = 2
Sub-total = D
And include AMIZ, requirement = 2, Alt formula for Condition Type = 13 save it
SAP-SD
83
Go to VK11 and maintain condition records for 2 materials as a 100 and 60, and maintain
condition records for AMIW for customer price group = 02 as a 200 save it and exit.
Go to VA01 and raise the Sales Order and go to Header Condition Screen.
10.00
20.00
30.00
40.00
Go to V/08 and include K029 condition type between discount condition steps.
Go to VA01 and raise the Sales Order for 2 Items.
11.a) Pallet Discounts: Discounts can be given to Full Pallet and on Mixed Pallet.
Surcharge can be charged on insufficient Pallets as well as Mixed Pallet.
Create 2 Materials
Base Unit = PAL
Sales Unit of Measure = EA
Conversion factor 1 Pallet = 50 Each Items.
Condition Type = KP00 Pallet Discount
Discount can be granted on Full Pallet.
V/06 of KP00
Access Sequence K007
Condition Class A
Calculation Type C
Plus / Minus
X
Manual Entries C
Check Item Condition
Unit of Measure PAL
Go to V/08 and include condition type KP00 with requirement = 2
Alt formula for condition Base Value = 22
Go to VK11 and maintain condition records for KP00 for Customer.
Go to VA01 and raise the Sales Order and check the values.
SUN SURYA TECHNOLOGIES
SAP-SD
84
SAP-SD
85
11.c) KP02 Mixed Pallet Discount: Discounts can be granted on mixed pallet.
V/06 of KP02
Access Sequence K007
Condition Class A
Calculation Type B
Plus / Minus - X
Check Group Condition
Check Item Condition
Scale Basis C
Check Value - A
Unit of Measure PAL
Go to V/08 and include condition type KP02 between Discount Condition steps.
Go to VK11 and maintain condition records for KP02 as a Rs.5/- surcharge.
Go to VA01 and raise the Sales Order and check the values.
11.d) KP03 Mixed Pallet Surcharge:
Surcharge can be levy on mixed pallet.
V/06 of KP03
Access Sequence
K007
Condition Class
A
Calculation Type
B
Check Group Condition
Check Item Condition
Scale Basis
C
Check Value
-B
Scale Formula
- 23
Unit of Measure
PAL
Go to V/08 and include condition type KP03 between Freight Condition steps.
Go to VK11 and maintain condition records for KP03.
Go to VA01 and raise the Sales Order and check the values.
SAP-SD
86
FREE GOODS
Free Goods: In every Business granting Free Goods is quite common to encourage
sales and to grant privilExes. In SAP Free Goods can be configured by following 2
methods.
a. Manual
b. Automatic.
A. Manual: By specifying higher level item catExory for a line item user can
determine Free Goods manually.
Go to Va01 and raise the Sales Order for two line items.
VOV4 of TANN
Sales Document Type = OR
Item CatExory = NORM
Usage = FREE
Higher Level CatExory = TAN
=TANN
SAP-SD
87
SAP-SD
88
SAP-SD
89
Exclusive: In Exclusive, system configures Free Goods excluding Free Goods Qty
from Order Qty. That means for 10 items 1 item is free, then system configures Free
Goods as a 10+1.
In Exclusive other items can be given as a Free Goods Item than Order Item.
Maintain Condition Records (VBN1):
Path: Logistics
Sales and Distribution
Master Data
Conditions
Free Goods
VBN1 Create.
Specify Discount type NA00
Click on Key Combinations and maintain condition records for Exclusive by choosing
Exclusive option.
Click on Exclusive Button without maintain any values.
Maintain Entries
Specify Order Material
Specify Minimum Qty = 10
Specify From Qty = 10
Specify Unit of Measure EA
Specify Free Goods Qty 1
Specify Unit of Measure of Free Goods EA
Specify Calculation Formula 1
And Assign Free Goods CatExory 2 Exclusive
Specify Additional Material for Free Goods (Other Material)
Deliver Free Goods Delivery control and Save it.
Go to VA01 and raise the Sales Order and check the EXCLISIVE effect.
Condition Type NRAB: When the Customer wants to deduct the Free Goods Qty
cost from main item cost and he doesnt receive Free Goods Qty, condition type
NRAB can be used. NRAB condition type doesnt display the Free Goods item in
the Sales Order and it deduct the Free Goods Qty cost from the main item cost. That
means for 1 item cost Rs.100/- then for 10 items system charge only Rs.900/- but 10
items can be given.
Note: It applies only for Inclusive option.
Configuration Settings: Define Condition Type NRAB
V/06 of NRAB Free Goods
Access Sequence NIL
Condition Class A
Calculation Type C
Condition CatExory F Free Goods Inclusive
Manual Entries D
Check Item Condition
Pricing for Inclusive Free Goods without Item Generation: Choose our Pricing
Procedure and include condition type NRAB between Discount condition steps with
Requirement = 59
SAP-SD
90
SAP-SD
91
Go to goto button
Click on Details
Specify Lower Limit and Upper Limit for condition rates.
Save it.
Go to VA01 and raise the Sales Order and go to item condition screen and
manipulate the amount according the limits. It applies only for specific condition
records.
Change Condition Records: SAP records changes that we are going to carried out
for particular condition records.
Go to VK12 and specify Condition Type
Click on Key Combination
Maintain Selection Screen
Click on Execute
Select Condition Line Item
Environment
Changes
Condition Record and check the report.
MASS MAINTENANCE: To carry out Mass Changes for condition records go to
VK12 and specify condition type
Select all line items
Click on change amount icon and specify Percentage amount and click on copy icon.
If prices should be enhanced with absolute amount, specify absolute amount in
absolute field.
If you want to deduct certain Percentage or certain value, specify (minus) symbol to
the absolute amount or percentage.
Condition Index: For every condition type we can create condition index by which
we can maintain condition records (V_17 Create Condition, V/15 Change
Condition, V/16 Display Condition).
For Condition Index Condition Table should be created. According to Business
scenario, if business wants to restrict the usage of the condition type and condition
index should be created.
Path:
IMG
Sales and Distribution
Basic Functions
Pricing
Maintain Condition Index
a. Maintain Condition Tables for Index
Specify Condition Table Number
Choose KUNNR/MATNR
b. Activation of Condition Index
By defaults system activates our condition index tables.
c. Change Condition types
Choose K005 and click on copy as icon and define Condition Type as Y005.
Check Condition Update
SUN SURYA TECHNOLOGIES
SAP-SD
92
Go to V/08 and include condition type (Ex: Y005) between Discount Condition Types.
Go to VK11, specify condition Y005 and maintain records and save it.
Go to VK12, click on select using Index
Select our condition table that we created for condition index.
Maintain selection screen
Click on execute
Change the Condition Value and Save it.
Condition Update: By using Condition Update specific condition type can be
restricted for limited Sales Orders or for a certain condition base value or for specific
condition amount.
Go to V/06 and make sure that Condition Index and Condition updates are activate in
condition type.
Go to VK12, Click on select using Index
Select Condition Index table
Click on Execute Icon
Go to goto button and select Additional Data
Specify a. Max. Condition Value or
b. Max. Number of Orders or
c. Max. Condition Base Value
in limits for Pricing Section and save it.
Go to VA01 and raise the Sales Order 2 times and check the effect.
Copying Rules for Conditions: Conditions and Condition Tables can be copies with
each other.
Same condition types with same condition tables can be copied.
Same condition types with different condition tables can be copies.
Due to this copy control function number of condition records can be copied from
single condition record.
Path to Maintain Copy Control:
IMG
Sales and Distribution
Basic Functions
Pricing
Pricing Control
Copy Control for Pricing Condition
a. Copying Rules for Condition Types: Here source condition K004 can be copied
into target condition table K004.
K007 can be copied into K020 condition type.
K029 can be copied into K029 condition type.
b. Copying Rules for Condition: Here source table ex:4 can be copied into target
table 29. Ex: Customer Group 01 and Customer Pricing Group 01 copied into
Customer Group 02 and Customer Pricing Group 02 by using condition type K020.
SAP-SD
93
SAP-SD
94
Field Name
Customer Number
Position
Page Header of Pricing Report
Material Number
Release Status
Condition Type
Text
The Key Field and the
Corresponding text are display
The Key Field and the
Corresponding text are display
The Key Field and the
Corresponding text are display
The Key Field and the
Corresponding text are display
SAP-SD
95
c. Assign Variants to Company Code: Choose our Company Code and assign
posting period variant as a 1000 and save it.
Assign Financial Document Type RV.
SA
WA Goods Issue
WE Goods Receipt
WL Goods Issue / Delivery
Path: IMG
Financial Accounting
Financial Accounting Global Settings
Document
Document Header
Define Document Types
Choose Document Type RV Billing Document Transfer
Select it, Copy it and Rename it.
Click on Number Range Information
SAP-SD
96
SD Configuration Settings
1. Create Customer Master by using Transaction Code XD01 and make sure that
reconciliation account, Sort Key, Account Assignment Group (ex:01 Domestic
Revenues) in Billing Document Tab.
2. Make sure that Account Assignment Group for Material in Sales:Sales Orgn Data
2 maintain in Material Master.
3. Check Master Data relevant for Account Assignment.
Path:
IMG
Sales and Distribution
Basic Functions
Account Assignment/Costing
Revenue Account Determination
Check Master Data Relevant for Account Assignment
a. Materials: Account Assignment Groups: Here Account Assignment Groups for
Materials. Ex: 01 Trading Goods
02 Services
03 Finished Goods etc define. These values are proposed into
Material Master.
b. Customers : Account Assignment Groups: Here Customer Account
Assignment Groups.
Ex:
01 Domestic Revenues
02 Foreign Revenues
03 Affiliated Company Revenues are defined. These values are proposed
into Customer Master.
4. Define Dependencies of Revenue Account Determination:
Path: Path is same as point no 3.
Account Determination: Create condition Tables
Ex:
SAP-SD
97
SAP-SD
98
ROUTE DETERMINATION
For each and every line item in the Sales Order Route can be determined
automatically. Route may consists different stages with different transportation
connection points or lExs. The material can be transported from source to
destination by using different mode of transports with different shipment types.
Route can be determined for a line item in the Sales Order. Route can be redetermined at delivery document header level by taking Weight Group into
consideration.
Configuration Settings:
a. Define Modes of Transport: Ex: Road, Train or Post.
Path:
IMG
Sales and Distribution
Basic Functions
Routes
Define Routes
Define Modes of Transports and define 01 Street, 02 Train, 03 Ship as a
mode of transport.
b. Define Shipping Types: Ex: Truck, Mail, Train and Ship. Define Shipping types
and assign mode of transport.
Ex:
01 Truck
02 Mail
03 Train
04 Ship
01 Street
06 Postal Service
02 Train
03 Ship
SAP-SD
99
SAP-SD
100
Route Determination
Define Transportation Zone: Transportation Zone represents Ship to Party RExion
or vendor RExion. System uses Transportation Zone as a one of the factor to
determine the route for a line item in the Sales Order.
Go to New Entries and define Transportation Zone for Country.
NOTE: This value proposed into Customer Master General Data Session.
Maintain Country and Transportation Zone for Shipping Point.
Choose shipping point and country and assign our Transportation Zone. Save it and
Exit.
Define Transportation Groups: Ex: 0001 The value of this field proposed into Material Master and used by the system as a
one of the factor to determine Route.
Maintain Route Determination: System automatically determine route for a line
item in the Sales Order by taking 4 factors into consideration.
a. Country of Departure Zone
b. Country of Destination Zone
c. Shipping Conditions (From Sales Document Header)
d. Transportation Group (From Material Master)
Go to New Entries
Specify Country of Departure Zone (IN)
Specify Departure Zone (Ex: Coastal Zone)
Specify Destination Country (IN)
Specify Receiving Transportation Zone
Select the combination and click on Route Determination without Weight Group
(Order)
Go to New Entries
Specify Shipping Conditions, Transportation Group and Assign our Route. Save it.
Go to VA01 and raise the Sales Order.
Go to Item Shipping Tab and check Route Determination.
SAP-SD
101
SAP-SD
102
Change Output:
Program: With the help of Technical Consultants Business can inform the customer
about the changes to the output that was already sent to customer. This routine
checks what kind of changes should be effected in the new output.
In the General Data section check multiple issuing should be activated.
Form Routine: Assign the routine that calls up the program.
Replacement of Text Symbals:
Programme: By Technical Assistance we can have different Text and Text Symbols
on output. Ex: Output Title, P O Number and Date.(Default Values)
SAP-SD
103
Dispatch Time: Ex: Send immediately when saving the application. The value of
this field determines how the output should be dispatched. That means periodic job
allowed or not. Ex: Output type RD03 Cash Sales Invoice should be assigned with
send immediately (when saving the Application).
Transmission Medium: Assign Transmission Medium thru which output should be
send to the Customer or Partner. Ex: Printout, Fax, Telex, EDI, Simple Mail etc.,
EDI: Electronic Data Interchange is a Sub-System which can be used by SAP to
speak with Non-SAP system by using a concept I Doc (Intermediatory Document).
Partner Function: Assign relevant Partner Function to Output Type.
Communication StratExy: Ex: CS01 Internet/Letter. Assign Communication
StratExy to the output to be transmitted externally.
Time: Check Timing 1 (Periodic Job not allowed). This control determines periodic
job for output processing.
Storage System: The value of this field specifies archiving mode of output of Sales
Documents.
Print: Print Parameter : Sales Organization. Pass the Print parameters to get the
Print.
Mail: This section deals with output type mail.
Document Name: WF MC Specify the folder name thru which output is going to be
transmitted the mails.
Priority: Assign the priority of the folder.
Check Not Changeable: If it is activated only the mail recipient and sender can
change the output.
Click on Mail Title and Texts
Choose Language English and specify text for Internal Mails. Maintain the Text.
Save it and Exit.
Click on Processing Routines: Assign Transmission Medium 1
Program RVADOR01
Form Routine Entry
Form RVORDER01
Partner Function Step: Assign Partner Functions to relevant transmission mediums.
Ex: Printout SP.
Save it and Exit.
SAP-SD
104
OR
Partner Function
Trans. Medium
SP
Dispatch Type
Language
EN
SAP-SD
105
SAP-SD
106
SAP-SD
107
SAP-SD
108
Partner Type
KU
LI
AP
PE
Partner Functions
SP, SH, BP, PY
FA
CP
SE, KB, KM
SAP uses Condition Technique to determine relevant Partner Functions for the
objects like Customer Master, Document Header and Item CatExories.
Partner Determination Procedure to Customer Master:
SAP determines relevant Partner Functions to the Customer Master by following One
Partner Determination Procedure that is going to be defined in IMG and assigned
with relevant partner functions depending upon the Account Group.
A. Define Account Group: Ex: Y001 for Sold to Party. Sold to Party performs Ship
to Party, Bill to Party and Payer partner functions also. So that the user should
maintain data in Sales, Shipping, Billing Tabs. So field status should be maintain
Required or Optional to each and every field depending upon the field priority.
Path: IMG
Financial Accounting
Accounts Receivable and Account Payable
Customer Accounts
Master Data
Preparations for Creating Customer Master Data
Define Account Group with Screen Layout (Customers)
CPD One time Customers
CPDA One time Customer
Go to New Entries
Specify the Account Group Name with Description Ex: Y001 Sold to Party
One Time Account
Output Determination Procedure.
Maintain field status in General Data, Company Code Data, Sales Data.
Define Number Ranges:
Create Number Ranges for Customer Accounts
Click on Change Intervals Icon
Click on Insert Intervals Icon
Define Lower Limit and Upper Limit Number Range
SAP-SD
109
Specify the Current Number and External if Customer Number assigned externally.
Save it and exit
Assign Number Ranges to Customer Accounts Group:
Choose our Account Group Y001
Assign Number Range Key
Save it and Exit.
SD Configuration Settings
Define Partner Functions:
Path: IMG
Sales and Distribution
Basic Functions
Partner Determination
Set up Partner Determination
Set up Partner Determination for Customer Master
Click on Partner Functions control button under dialog structure
Unique
Partner
Name
Partner
Error
Higher level
Function
Type
Group Part Function
SP
Sold to Party KU
07
SH
Ship to Party KU
07
BP
Bill to Party
KU
07
PY
Payer
KU
07
Customer
Hierarchy Type
Error Group: Incompleteness Procedure for Partner Functions. That reminds the
user about the fields in which values has not been maintained while saving the
Document.
Higher level Partner Functions: Some Partners may have superior partner
functions. Then they should be assigned. Ex: Credit Representative (KB) has higher
level partner Credit Manager (KM), that are belongs to Partner Type PE (Personnel).
So that KM should be assigned to Kb as a higher level partner functions.
Unique: This indicator specifies that specific partner function is unique in the Partner
Determination Procedure. That means a single person only performs that partner
functions. Ex: SP
Customer Hierarchy Type: Specify the Customer Hierarchy Type it relevant Partner
is participating in Customer Hierarchy.
Define Partner Determination Procedure: Choose Standard Partner Determination
Procedure AG copy and rename it or go to new entries and define Partner
Determination Procedure. Ex: Y1 and save it.
SAP-SD
110
Name
Not
Changeable
Mandatory
Sold to Party
Ship to Part
Bill to Party
Payer
Configuration Settings
Define Partner Functions (SP, SH, BP and PY)
Path: IMG
Sales and Distribution
Basic Functions
Partner Determination
Set up Partner Determination
Setup Partner Determination for Sales Document Header
Click on Partner Function Combination button
Check SP, SH, BP, PY defined or not.
SAP-SD
111
Partner
Y5
Y5
Y5
Y5
SP
SH
BP
PY
Name
Manual
Sequence
Function
Sold to Party
Ship to Party
Bill to Party
Payer
Save it.
Assign Partner Determination Procedure to Document Type:
Select our Partner Determination Procedure
Click on Partner Determination Procedure assignment control button.
Choose Sales Document Type OR
Assign our Partner Determination Procedure
Save it and Exit.
Go to VA01 and raise the Sales Order and specify the Customer Number
Go to goto button, Header, Partners.
SAP-SD
112
INCOMPLETNESS PROCEDURE
Sales Documents, Delivery Documents according to their architecture contains
certain important fields at each level of Document i.e. Header Level, Item Level,
Schedule Lines. The values of those fields will have a greater influence on
processing of subsequent documents. So that value should be maintain in those
fields before saving the document otherwise user may face certain problems while
processing subsequent Documents. So as to avoid this kind of situation SAP
delivered a feature called Incompleteness Procedure which can be defined for at
each level of document. To this Incompleteness Procedure that important fields are
assigned and by using Status Group documents can be block at each level of
processing. If values has not been maintained in those fields.
Incompleteness Procedure doesnt concern whether correct value has been
maintained or not. It concern only whether value has been maintained or not.
Note: Incompleteness Procedure can not be configured for Billing Documents as
billing document doesnt have any subsequent document.
Configuration Setting for Incompleteness Procedure for a Field Order Reason (AUGRU)
Define Setting Groups: Status Groups Records relevant message about the
missing information and blocks the documents.
Path:
IMG
Sales and Distribution
Basic Functions
Log of Incomplete Items
Define Status Groups
Choose existing status group
Copy and Rename it and check the following
General: This control records certain information about the fields at Header Level.
Ex:PO Number if not maintained.
Check Delivery: This control records certain information about fields. Ex: Shipping
Point at Item level and issued appropriate message on the status bar.
Check Billing Document: This control records appropriate status message if certain
billing information missed. Ex: Payment Terms.
Check Price: This control records appropriate information if data at item level. Ex:
Price has been missed.
Goods Movement: This control records appropriate message if certain information
missed at schedule line level. Ex: Movement Types and Issued appropriate status
message.
It is relevant for Shipping Document.
Picking/Put away: This control records appropriate status message if certain
information missed. Ex: Picking and Put away.
SUN SURYA TECHNOLOGIES
SAP-SD
113
SAP-SD
114
MATERIAL DETERMINATION
Order Material can be swap with other material. Ex: With the user specified material
A in the Sales Order B can be given to Customer.
When the Business stopped the Production of existing material, that can be swapped
with new material or existing material can be offered with special packing or it can be
used with EAN (European Article Number) number.
SAP uses Condition Technique to Determine
Configuration Settings:
A. Maintain pre-requisites for Material Determination.
a. Create Condition Tables: Ex: 001 Material Enters (MATWA)
b, Maintain Access Sequence: Access Sequence Ex: A001 Define and Condition
Table 001 (MATNR) Assigned.
c. Define Condition Types: Condition Type A001 Define and Assign to Access
Sequence A001.
d. Maintain Procedure: Procedure A00001 defined and Condition Type A001
Assigned.
B. Assign Procedure to Sales Document Types: Choose Sales Document Type
OR and Assign Material Determination Procedure A00001.
C. Define Substitution Reasons: Here substitution reasons Ex: 0005 Promotion
Defined.
Check Entry: This Indicator allows to print original material on the document.
Check Warning: This indicator issues warning message.
StratExy: A
Automatic Check A
A - Substitute Products are displayed for selection
B General Material Determination with selection, without ATP
Outcome Check:
Blank Item will be replaced
A Substitution Products are displayed as sub items.
B As in A but only when creating the item in sales.
Save it.
SAP-SD
115
SAP-SD
116
CROSS SELLING
Cross Selling is the concept by which business can suggest combination material(s)
for ordered material.
Ex: If the Customer placed the Order for Material Computer, Computer Stand can be
suggested.
During Sales Order Processing system displays list of combination materials in a
popup box. So that the user can explained the features of product and if the
customer agreed to purchase those combination materials user can select otherwise
user can leave it.
SAP uses Condition Technique for Cross Selling
Document Procedure for Cross Selling
+
Customer Procedure for Cross Selling
Along with Sales Area used by the system to determine cross selling.
Configuration Settings
A. Define Determination Procedure for Cross Selling:
Path:
IMG
Sales and Distribution
Basic Functions
Cross Selling
Define Determination Procedure for Cross Selling
1. Create Condition Tables:
Ex: 011 Material (MATNR) Defined
2. Maintain Access Sequence:
Access Sequence C001 Material number Cross Selling Defined and Condition
Table (011) Assigned
3. Define Condition Types:
Condition Type C001 Defines and Assigned with Access Sequence C001.
4. Maintain Procedure:
Ex: C00001 Cross Selling Procedure Defined and Condition type C001 Assigned.
SAP-SD
117
SAP-SD
118
SAP-SD
119
SAP-SD
120
SAP-SD
121
SAP-SD
122
SAP-SD
123
COMPANY
CREDIT CONTROL AREA
Company Code 1
Company Code 2
Path:
IMG
Enterprise Structure
Definition
Financial Accounting
Define Credit Control Area
Choose existing Credit Control Area. Ex: 1000
Click on Copy as Icon and Define Credit Control Area by changing data.
Currency: Assign the Currency INR for the Credit Control Area.
Update Group: This group updates open orders value, open delivery value, open
billing values for the credit. If you Assign Update Group 000012 then:
a. Sales Order: It increases open order value for delivery relevant schedule lines.
b. Delivery: It reduces Open Order Value from Delivery relevant schedule lines and
increases open delivery value.
c. Billing Document: It reduces Open Delivery Value and Increases Open Billing
Value.
d. Financial Accounting Document: It reduces Open billing Document Value and
Increases Open Items.
If you Assign Update Group 000015 then:
a. Delivery Document: It increases Open Delivery Value and Increases open Billing
value.
b. Financial Accounting Document: It reduces Open billing Document Value and
Increases Open Items.
If you Assign Update Group 000018 then:
a. Sales Order: It increases open delivery value.
b. Billing Document: It reduces Open Delivery Value and Increases Open Billing
Document Value.
c. Financial Accounting Document: It reduces Open billing Document Value and
Increases Open Items.
Fiscal Year Variant: Assign Fiscal Year Variant K4.
Default Data for Automatically Creating New Customers: It any value maintained
in the below specifies 3 fields then system automatically applies that data Risk
CatExory, Credit Limit, Representative Group to New Customers.
In IMG we are going to define Risk CatExory and Credit Representative group for
Customers. The Credit Limit that we specified here applies to all the New Customers
that are defined under risk credit control area. Ex: 100000/-
SAP-SD
124
Check All Company Codes: This indicator signifies that the posting of this credit
control area applies to all the company codes that means the credit limit that we
defined for new customers is a overall limits across all the company codes. Save it
and exit.
Assign Company Code to Credit Control area.
Path:
IMG
Enterprise Structure
Assignment
Financial Accounting
Assign Company Code to Credit Control Area.
Choose our company code and assign our credit control area. Save it and exit.
Define Groups: Here Customers are group for Credit Management. It is only for
information purpose.
Path:
IMG
Financial Accounting
Accounts Receivable and Accounts Payables
Credit Management
Credit Control Account
Define Groups
Go to New Entries and Define Customer Credit Groups.
Ex: Z001 Major Customers
Z002 Medium Customers
Z003 Small Customers and Assign to Credit Control Area. Save it and exit.
Define Risk CatExories: Here Customers are catExorized for Credit Management
and Assign to Credit Control Area.
Go to New Entries
Y1 High Risk CatExory
Y2 Medium Risk CatExory
Y3 Low Risk CatExory
Save it and exit.
Define Credit Representative Groups: Here company personnel can be defined as
a Credit Representative Group and Assign to Credit Control Area. It can be used as
a selection criteria to generate Credit List.
Go to New Entries. Ex: CG1
399
Cr. Group
SAP-SD
125
Ex: Choose existing Credit Representative group and copying and renaming with
our credit representative group and credit control area and save it.
Credit
Representative
Credit
Control
Partner
Function
CG1
399
KB
Check Credit
Control
Personnel
Number
Name
ID
1051
Mr. XXX
Emp 2
Go to change mode of Credit Control Area and Assign Risk CatExory (399) and
Credit Rep. Group (CG1) save it and exit.
SD Configuration Settings
1. Specify Subtotal as a A for Credit Price:
Path:
IMG
Sales and Distribution
Basic Functions
Credit Management / Risk Management
Credit Management / Risk Management Settings
Enter Settings
Conditions : Procedure
Choose our Pricing Procedure and Assign Sub-total as a A to Credit Price
(A KOMP / CMPRE)
2. Configuration Setting: Assign Partner Functions KB and KM to Sales Document
Header to exchange information as well as to take certain decisions. Partner
Functions KB Credit Representative, KM Credit Manager should be defined and
assigned. Credit Manager is a superior to Credit Representative.
Path:
IMG
Sales and Distribution
Basic Functions
Credit Management / Risk Management
Credit Management / Risk Management Settings
Enter Settings
Configuration : Partner
Choose Sales Document Header
Click on change Icon
Choose Standard Partner Determination Procedure TA
Click on Partner Functions in Procedure control button under dialog structure
Check Mandatory option fir KB and KM.
3. Output Types (KRML): To exchange the information between Credit Manager
and Credit Group output type KRML should be configured with transmission medium
7 Simple Mail.
SAP-SD
126
Path:
IMG
Sales and Distribution
Basic Functions
Credit Management / Risk Management
Credit Management / Risk Management Settings
Enter Settings
Output Types
Choose output type KRML Credit Processing
Click on Details Icon
Click on Display to Change Icon
And again choose output type KRML and Click on Details Icon.
General Data
Access Sequence : 0005 Credit Control Area
Check Access to Conditions
Check Multiple Issuing
Default Values Tab
Dispatch Time: Send Immediately when saving the application.
Transaction Medium : Simple Mail (7)
Partner Function : KB Credit Representative
Communication StratExy : Blank
Time Tab
Check Timing 2
Check Timing 3
Periodic Jobs not allowed.
Mail
Specify the Document Name : KREDITCHECK
Priority : 9
Click on Mail title and Texts control button
Choose Language English
Double Click on Text and Type the Text and specify the Message. Save it.
Click on Processing Routines
Assign Program FORM Routine written by ABAPer by which output going to be
trigger.
Click on Partner Functions Control Button
Assign KB and KM to Transmission Medium Simple Mail.
Save it and exit.
SAP-SD
127
SAP-SD
128
Define Credit Groups: As automatic Credit Checks determine Credit Control Area +
Risk CatExory + Document Credit Group, Sales Documents, Delivery Documents
and PGI Documents should be group. That means Automatic Credit Check can be
carried out on Sales Order Level or Delivery Level or PGI (Post Goods Issue) Level.
Ex: 01 Credit Group for Sales Order
02 Credit Group for Delivery
03 Credit Group for Goods Issue.
Save it and exit.
Assign Sales Documents and Delivery Documents:
a. Credit Limit Check for Order Types: Choose Sales Document Type OR and
Assign check Credit Limit as a D and Credit Group for Sales Order (01) and save
it.
b. Credit Limit Check for Delivery Types: Choose Delivery Document Type LF
and Assign Delivery Credit Group (02) and Goods Issue Credit Group (03) save it
and exit.
SAP-SD
129
SAP-SD
130
Go to XD01 or XD02
Go to Sales Area Data Section Billing Tab and Assign Credit Control Area and save
it.
Go to VA01 and raise the Sales Order and check system response for Simple Credit
Check.
Go to VN01N and initiate Outbound Delivery, then system blocks the document due
to Credit Check. Then concern person in the Business removes the block by going
to VKM3 or VKM4 or VKM5.
SAP-SD
131
SAP-SD
132
To
To: Specify the time periods for bExinning of the seasonal factors.
2
3
4
5
Static
Dynamic
Doc Value
Critical fields
Next Review
Date
Reaction
Reaction
Reaction
Reaction
Reaction
Status/Block
Status/Block
Status/Block
Status/Block
Status/Block
Open Order
Horizon Period
Max Doc Value
No of Days
Open Items
Reaction
Oldest
Open Items
Highest
Dunning
Level
User 1
User 2
User 3
Reaction
Status/Block Days
Reaction
Open Delivery
Month
No of Days
Open
Oldest Open
Item
SAP-SD
133
If system has to take all Open Orders, all Deliveries into consideration then Check
Open Orders and Open Deliveries option.
If Credit Limit exceeded, you want to block it then Check Status / Block Indicator.
Dynamic: It indicates system carries out Dynamic Credit Limit check with in specify
Credit Horizon. System gets the Credit Exposure by splitting static part (Open Items,
Open Billing and Open Delivery Values) and dynamic part i.e. Open Order Value.
The Open Order includes all or not yet partially delivered orders. The value is
calculated based on shipping date and the Credit Horizon (Ex: 2 Months) that we
specified in the Horizon field so that when evaluating the Credit, system ignores all
open orders that are due for delivery after that horizon date.
The sum of the Static and Dynamic parts may not exceed the Credit Limit.
Document Value: It indicated that system carries out Credit Check based on
Maximum Document Value that we specified in Max Doc Value field. This kind of
Credit Check is relevant for New Customers whose Credit Limit not defined.
Critical Fields: Critical Fields like Payment Terms changed then system carries out
Credit Check along with Additional value days and fixed value days.
Note: This Check is only valid for Sales Documents only.
Next Review Date: It indicates whether system has to carry out Credit Check based
on the date of next review date for Credit.
While processing the Document the next Credit Review date should not be on the
current date which we maintain (FD32 Customer Credit Master Status
Section Internal Data Next Review Date)
We define time buffer for this kind of Credit Check in the adjacent field and also we
can maintain no of days that are added to next credit review date.
Check Open Items: Specifies whether the system carries out Credit Check based on
Open Items.
Based on the below specifies factors, system carries out Credit Check on Open
Items.
a. Maximum % of overdue items in open items.
b. No of days which the open items are overdue.
The proportion of overdue open items (That exceeds the specified no of days in the
total of open items should not exceeds the % specified)
Oldest Open Item: It indicates whether the system carries out Credit Check based
on the age of the oldest open item.
The oldest open item must not be older than the no of days specified.
Highest Dunning Level: It indicates whether system has to carryout Credit Check
based on the highest dunning level which we maintain in Customer Master Company
SUN SURYA TECHNOLOGIES
SAP-SD
134
Code data section in Correspondence Tab Dunning Procedure and Dunning Level
which will be copied to (FD32 Customer Credit Master Overview Section Dunning
Data)
When Dunning Procedure reached to the highest level than system carries out
Automatic Credit Check.
Check Static, save it and exit.
Go to VOV8 of OR and Assign Value D in Check Credit Limit field and Assign
Credit Group as a 01, save it and exit.
Go to VA01 and raise the Sales Order and check Automatic Credit Check effect.
Go to VL01N then system blocks the Document.
Go to VKM3 and release the Document.
FAQ: If Credit Management to be configured for Division Specific? How do you
configure it?
ANS: Assign Credit Control Area to Sales Area. Sales Area is a combination of Sales
Organization, Distribution Channel and Division.
Path:
IMG
Enterprise Structure
Assignment
Sales and Distribution
Assign Sales Area to Credit Control Area
Choose our Sales Area and Assign our Credit Control Area.
SAP-SD
135
SAP-SD
136
SAP-SD
137
Item CatExory
TAN
TAN
TAN
+
+
+
MRP Type
PD
NIL
ND
Requirement Type.
= 041
= 041
= 011 Delivery Requirement
SAP-SD
138
SAP-SD
139
f. Define Procedure for Each Schedule Line CatExory: Here find tuning settings
for Availability Check at Schedule Line CatExory level can be configured.
Ex: CP Check Availability Check and Transfer of Requirements.
Note: This configuration settings are copies from TOR configuration settings.
g. Define Procedure for Each Delivery Item CatExory: Here Availability Check
control define delivery Item CatExory whether system has to carry out Availability
Check or not for Delivery Item.
Choose Item CatExory TAN and Assign Blank, X or Y.
h. Checking Rule for Updating Back Orders: When the Document saved with
order Qty ZERO then system treats the Order as a back order. Then the back order
can be completed by using concept called Re-scheduling. To update the back orders
we define Checking Rule at Plant Level. Ex: Choose our Plant and Assign Checking
Rule (01) save it and exit.
i. Define Default Settings: While Carry out Availability Check system determines
ATP Qty by following a formula:
ATP Qty = Warehouse Stock + Planned Receipts Planned Issues
If ATP Qty is positive then system confirms the Qty according to required delivery
date.
If ATP Qty is NExative the SAP gives 3 options (in a dialog box) to the user to take
decision. That are:
1. One Time Delivery: In One Time Delivery of Order Qty is 100 Units, Required
Delivery Date is Current Date then system confirms Qty after 1 week. If the user
uses one time delivery then system confirms Qty as a ZERO then it can be
completed by using Back Order Processing.
2. Complete Delivery: If the user chooses this option that is 50 items today,
remaining 50 items after 1 week then system confirms full Qty after 1 week. So that
Order can be delivered after 1 week.
3. Delivery Proposal: The user chooses this option then 50 confirmed and delivered
today and remaining 50 can be delivered after 1 week
SAP-SD
140
COPY CONTROL
Ex:
"QT"
COPY CONTROL
|
|
"OR"
HEADER
HEADER
HEADER
ITEM
ITEM
ITEM
SCHEDULE LINE
SCHEDULE LINE
SCHEDULE LINE
Copy control is a concept by which SAP copies data from Source Document to
Target Document by using Data Transfer routines at each level of Document. While
copying Requirements can be Specified so that system takes those
requirements into consideration while copying data.
Transaction code VOFM to get the data transfer routines.
Documents can be copied:
a. Sales Document To Sales Document
b. Sales Document To Delivery Document
c. Sales Document To Billing Document
d. Delivery Document To Billing Document
e. Billing Document To Billing Document
f. Billing Document To Sales Document
Sales Document To Sales Document:
Path:
IMG
Sales and Distribution
Sales
Maintain Copy Control for Sales Documents
Copying Control Sales Document to Sales Document
Header: Choose OR to QT
Click on Display to Change
Again Choose OR to QT
Go to Details Icon
Data Transfer Routines: 051 General Header Data. This routine transfers
General Header Information from Header to Header copies. It is Assigned to VBAK
SUN SURYA TECHNOLOGIES
SAP-SD
141
Table. This routine also ensure certain data should not be copies. Ex: Purchase
Order.
Data Transfer Routines: 101 Business Data Header. This routine transfers
Business Data from Header to Header. Ex: Payment Terms, INCO Terms etc.,
Data Transfer Routines: 001 Partner Header. This routine transfers relevant
Partner Functions from Header to Header, Irrelevant Partners removed and required
Partners fulfilled.
Copying Requirements: 001 Header Same Customer. This requirement
ensures whether same sold to party is going to be copies or not into target document.
Otherwise system throws error. Ex: One Quotation raised for Customer A, if Sales
Order is going to be raised with reference to same Quotation for Customer B then
system throws error.
Check Copy Item Number: This Indicator copies Sales Order Line Item number
from preceding document to target document.
Check Complete Reference: This Indicator issues a message if source document
Qty has not been fully referenced.
Item: Choose Item catExory AGN go to details icon
a. Proposed Item CatExory: Specify Item CatExory the system automatically
proposes and it overwrites VOV4. Ex: In Billing Cost determination should not take
place for Credit Memos for Third Party Orders (G2S). So that system should use
item catExory TASG as a default since it doesnt determine cost instead of proposing
item catExory TAS.
Data Transfer Routine: 151 General Data Item. This routine transfers General
Data from Item Level.
Data Transfer Routine: 102 Business Data / Item Completion. This routine
transfers Business Data at Item Level. Ex: Payment Terms and INCO Terms etc.,
Data Transfer Routine: 002 Partner Item. This routine transfers relevant Partner
Functions from source document to target document at item level. It copies relevant
Partner Functions and its removes irrelevant partner functions and fulfill required
partner functions.
Copying Requirements: 301 Item rejection reasons. This requirement doesnt
copy the rejected items from source to target documents.
Check Copy Schedule Lines: This indicator copies or created schedule lines in
target document. Ex: When contract document released by the releasing order
OR then system has to create schedule lines in OR even though contract
document doesnt contain schedule lines.
Update Document Flow: Ex: X Create Document Flow Records.
Blank Do not Create Document Flow Records
2 Create Document Flow Records except for delay / Goods Issue / Billing
Document
SUN SURYA TECHNOLOGIES
SAP-SD
142
SAP-SD
143
SAP-SD
144
CONTRACTS
In Business Customers enter for worth of Material, for Qty of
or for Rental Contracts. Contract is a LExal binding of both parties to perform certain
activities for a sake of Monitory Considerations. Contracts can be mapped in SAP
system by defining Documents.
Ex:
Qty Contract
(KM)
Value Contract (WK1 and WK2)
Service Contract (WV)
Rental Contract (MV)
Master Contract (GK)
Master Contract is nothing but a Header Contract to which all Contracts can be
Assigned as a Lower Level Contracts, if the Customer enters for all Contracts with
the Business. Due to this Master Contracts data consistency can be maintained.
Master Contracts are executed thru Work Flow.
Contracts doesnt have any Schedule Lines.
In Business one person should be authorized to enter and To Release the
Contracts. Usually Sold to Party or Ship to Party may be authorized to release
Contract. Partner Function AA Sold to Party authorized to release the contract
should be define and assign to Partner Determination Procedure for Customer
Master object or Sales Document object.
Release Order: Contracts are released by using Release Order i.e. Sales Order.
Ex: TA. For Contracts Business may follow different Pricing Procedures.
Qty Contract (KM): When the Customer wants certain Qty of the Material during
certain period or when the Business lacks sufficient production to meet the demand
Qty contracts can be entered. To distribute available Qty evenly among Customers.
VOV8 of KM
Sales Document Type NMS
SD Document CatExory G
Screen Sequence Group LP Out Line Agreement
Transaction Group 4 Contract
Doc Pricing Procedure A
Message : Master Contract A Check
No Delivery and No Billing
VOV7 of KMN
Completion Rule C
Pricing - X
Uncheck Schedule Lines Allowed
SAP-SD
145
VA01
VL01N
TA
LF
VF01
F2
Qty Contract
Standard Order
Delivery
Invoice
Path: Logistics
Sales and Distribution
Sales
Contract
VA41 Create
Specify the Contract Type KM and Sales Area
Specify Validity Period
Save the Document and go to VA01 to release the Contract
Go to VL01N and VF01.
SAP-SD
146
VA41
VA01
VL01N
VF01
WK1
OR
LF
F2
SAP-SD
147
Path: Logistics
Sales and Distribution
Master Data
Products
Value Contract
Assortment Module
WSV2 Create
Click on Items
Specify Description
List out all the Materials that are going to be participated in the Value Contract with
validity periods. Save it and note down the Assortment Module Number.
Go to VA41
Specify Doc Type WK1
Specify the Description
Specify the Validity Periods and Specify the Assortment Module Number with Target
Value in the Line Item and save the Document.
Go to VA01 and release the Value Contract.
Specify the Open Qty
Select Line Item
Click on Expand Assortment Module Option.
Specify the Order Qty, Press Enter and go back, again select line item and click on
copy system copy 2 line items and process the Sales Document then VL01N and
VF01.
SAP-SD
148
SAP-SD
149
Define Rules for Determining Dates: Here Date Determination Rules are defines.
Ex: 04 Acceptance Date
Base Line Date - 04 Acceptance Date
Save it and Exit.)
SAP-SD
150
Billing Request: IRC (Debit Memo Request for Contract). Assign Billing Document
Type for Service Contracts that system automatically proposes for Business
Compensation for Service Contract.
Contract Data Allowed: Ex: X. The Value of this field determines whether Contract
data allowed for this Sales Document. If you Assign X the changes that we are
going to carried out at Header Level, doesnt effect at Item Level. If you Assign Y
changes effect at Item Level.
Follow up Activity Type: 000 Telephone Call. Assign follow up activity type that
is to be created as a follow up action for Service Contract.
VOV7 of WVN
Completion Rule C
Billing Relevance : I Order Related Billing Billing Plan.
Billing Plan Type : 02 Periodic Billing.
Pricing : X
Uncheck Schedule Lines Allowed.
Save it and Exit.
Go to VA41 and Process Service Contract and go to VF01 and raise Invoice.
SAP-SD
151
MASTER CONTRACT
When the Customer enters with different types of contracts those contracts can be
assigned to Master Contracts as a Lower Level Contracts. So that date consistency
can be maintained.
Group Referencing Procedure (SDGK): To Assign Lower Level Contracts to
Master Contracts are referencing Procedure required by which what kind of fields can
be copied and what kind of fields proposed from Master Contracts to Lower Level
Contracts.
Path:
IMG
Sales and Distribution
Sales
Sales Documents
Contracts
Master Contracts
Define Referencing Requirement
a. Define Reference Sales Document Types: Here Lower Level Contracts are
assigned to Master Contracts.
b. Define Referencing Procedures: Has fields are catExorized into 3 parts
1. Identical Fields: A Master Contract can only be referenced by a contract if the
fields in the Master Contract and Lower Level Contracts Matches.
2. Copy Fields: The Values of these fields are copied from Master Contract into
Lower Level Contract. Deviating values in the Lower Level Contracts are not
allowed.
3. Proposal Fields: Like copying fields are
but values
can be over written.
Choose Standard Referencing Procedure SDGK and copy it and rename it (ZSDK).
Select our Procedure
Click on Fields Control Button under dialog structure
Go to new entries and maintain entries in the table like below
Table
VBAK
VBKD
VBAP
VEDA
Field
Name
AUGRU
INC01
KUNNR
VLAUFZ
Copying Rule:
Partner
Function
SP
Copy
Rule
Message
C
B
A
A
SAP-SD
152
VOV8 of GK
SD Document CatExory 0
Screen Sequence Group GK (Master Contract)
Transaction Group 4
Document Pricing Procedure V
Contract Profile 001
Group Referencing Procedure ZSDK
Contract Data Allowed X
Check Update Lowe Level Contract
Save it.
Go to VA41
Specify Document Type GK
Specify Sold to Party No
Specify the Description
Specify Contract Start Date 01 (Todays Date)
Specify Contract End Date 10 (Todays Date + 1 Year)
Save it and note down the Master Contract Number.
Again go to VA41 and raise Quantity Contract
Specify the Description
Specify the Contract Start Date and End Date (Like Master Contract Validity Periods)
and Assign Master Contract Number that was created in the previous step)
Sate it and Exit.
Go to VA41 of Master Contract and check Qty Contract has been assigned or not.
SAP-SD
153
CUSTOMER COMPLAINTS
In Normal Business Process, Business or some times Customers may incur losses,
so that compensations should be takes place according to the Partner.
If Customer incurred loss Ex: Due to Damage in Transit Customer compensation to
be carried out by following 2 methods.
a. By sending Physical Materials proportionate to Damaged Goods OR
b. Raising Credit Memo with reference to Credit Memo Request.
If rehabilitation cost more than the Production cist then the Business may ask the
Customer to destroy the goods the according to Customer request business may
sent physical goods as a customer compensation or business may raise Credit
Memo.
If rehabilitation cost less than the actual cost then Business may ask the Customer to
return the Damaged goods and it has to receive those damaged goods into separate
storage location, then the Business has to test those damaged goods to find out the
reason for the damage and also if there is any choice to rectify those damaged goods
by the Quality Inspector. If there is any rectifiable goods existed then those goods
will be rectified and transferred to Un-restricted Usage of main storage location.
If un-restricted goods are existed then those goods are transferred to Scrap
storage location, from there scrap materials are removed from scrap storage location
by following Normal Standard Business Process.
Configuration Settings:
If Customer doesnt Return the Goods Credit Memo Request
Process Flow:
IN
QT
VA11
VA21
OR LF
VA01
VL01N
F2
VF01
G2 G2
VA01
VF01
SAP-SD
154
Debit Memo Request: When the Business incurs Loss in Business Transaction due
to Price Discrepancy or Excess Delivery Debit Memo Request can be raised.
Process Flow:
IN
VA11
QT
VA21
OR LF
VA01
VL01N
F2
VF01
L2 L2
VA01
VF01
SAP-SD
155
Process Flow:
VA11
VA21
IN
QT
Scrap
VA01
VL01N
VF01
OR
LF
F2
|
RE
LR (SL2)
|
MB1B
453
SL1
|
MB1B
453
-----> VA11 -----> VA21 ----> VL01N ----> VF01
SL3
|
VF01 (RE) Credit for Request
VOV8 of RE Returns
SD Doc CatExory : H
Screen Sequence Group : RE - Returns
Transaction Group : 0 Sales Order
Doc Pricing Procedure : A
Delivery Type LR Return delivery
Delivery Related Billing Type : RE Credit for Request
Order Related Billing Type : RE Credit for Request
Billing Block : 08 Check Credit Memo
VOV7 of REN Request
Billing Relevance : B
Pricing : X
Check Schedule Lines Allowed.
Check Returns
Check Weight / Vol Relevant
Check Determine Cost.
VOV6 of DN Returns
Movement Type : 651 Return Delivery
Check Item Relevant for Delivery
SAP-SD
156
VA21
VA01
VL01N
VF01
IN
QT
OR
|
LF
F2
SDF
----------------->
LF
SAP-SD
157
CONSIGNMENT
Consignment Business Process when the Business launches New Product then the
dealer may not take the Materials from the Business so that Business sent that new
stock to dealer CONSIGNMENT AGENT without carrying out Billing Process.
If consignment Agent sells the stock to the consumer, then only business bills the
customer Consignment Agent.
Consumer returns the goods to the Consignment Agent if they are damaged. So that
Business should compensate it by raising Credit Memo.
If Consignment Agent doesnt want to sell consignment stock then the business has
to pick up unsold stock from customer side.
V V Imp: Consignment Agent can be defined in SAP system as a special stock
partner, with a partner function SB. Consignment Business Process consists of 4
phases
a. Consignment Fill up:
VA01 VL01N
KB
LF
b. Consignment Issue:
VA01 VL01N VF01
KE
LF
F2
c. Consignment Returns:
VA01 VL01N VF01
KR
LR
RE
d. Consignment Pick Up:
VA01 VL01N
KA
LR
Consignment Business Process:
Item
CatExory
KB / CF
KE / CI
KR / CR
KA / CP
KBN
KEN
KRN
KAN
Schedule
Line
CatExory
E1
C1
D0
F1
Movement
Type
631
633
634
632
VOV8 of KB
SD Doc CatExory : C Consignment Fill Up
Doc Pricing Procedure : A
Delivery Type : LF
VOV7 of KBN
---- NIL ---VOV6 of E1
Movement Type : 631
Check Item Relevant for Delivery
Check TOR and Availability Check
SUN SURYA TECHNOLOGIES
SAP-SD
158
VOV8 of KE
SD Doc CatExory : C Consignment Fill Up
Doc Pricing Procedure : A
Delivery Type : LF
Delivery Relevant Billing Type : F2
Order Relevant Billing Type : F2
VOV7 of KEN
Special Stock : W Consignment Customer
Billing Relevance : A
Pricing : X
VOV6 of C1
Movement Type : 633
Check Item Relevant for Delivery
Check TOR and Availability Check
VOV8 of KR Consignment Returns
SD Doc CatExory : H
Screen Sequence Group : RE
Doc Pricing Procedure : A
Delivery Type : LR
Order Relevant Billing Type : RE
Billing Block : 08
Check Propose Delivery Date
VOV7 of KRN Consignment Returns
Special Stock : W Consignment Customer
Billing Relevance : B
Pricing : X
VOV6 of D0
Movement Type : 634
Check Item Relevant for Delivery
VOV8 of KA Consignment Pick Up
SD Doc CatExory : C
Doc Pricing Procedure : A
Delivery Type : LR
VOV7 of KAN
--- NIL--VOV6 of F1
Movement Type : 632
Check Item Relevant for Delivery
Check TOR and Availability Check.
SAP-SD
159
SAP-SD
160
SAP-SD
161
SAP-SD
162
Process Flow:
IN QT OR MIGO LF F2
Go to VA01 and raise the Sales Order.
Go to ME21N and raise the Purchase Order with reference to Purchase Requisition
Number.
Go to MIGO
Check Line Item
Click on Post Icon
Go to MMBE
Check the Balance Stock
Go to MIRO
Specify the Purchase Order Number with reference to the Purchase Order. With this
Invoice is going to be verifies by MM and save it.
Go to VL01 and initiate outbound delivery.
Save the Delivery Document.
Go to LT03 to Sales the Transfer Order.
Specify the Warehouse number, Plant, Delivery Document Number and press enter.
Go to VL02N and do the PGI.
Go to VF01 and raise the Invoice.
Go to VA02 and check the document flow.
Go to MMBE and check the stock, then it is ZERO stock after PGI.
To carryout Inbound and Out bound Deliveries.
SUN SURYA TECHNOLOGIES
SAP-SD
163
SAP-SD
164
SAP-SD
165
Check General Packing Material Item: This indicator determines whether we want
to permit generation of delivery items for packaging materials in deliveries of this
delivery type. It can be used to generate bill for packaging materials to customers
and also packaging materials can be managed in inventory management.
Partner Determination Procedure: LF. In IMG we define Partner Determination
Procedure to propose relevant partner functions. Ex: Ship to Party.
Path:
IMG
Sales and Distribution
Basic Functions
Partner Determination set up Partner Determination for Delivery
Save it.
Define Delivery Document Item CatExory (LIPS): Transaction Code OVLP.
The system which is not going to be copies from Sales Document system determines
New Item CatExory. Ex: DLN
Choose Item CatExory DLN Standard Order Without Order.
Document CatExory : J Delivery
Classifying the Delivery Document Item CatExory.
Material / Statistics:
Check Material Number: 0 Allowed. This indicator allows to initiate outbound
delivery for a line item in the delivery document item whose order Qty = 0.
It is relevant for Text Items.
Item CatExory Statistics Group:
1 - Order. Debit Memo
The value of this field determined whether the statistical data gets updated in LIF
(Logistic Info System)
Stock Determination Rule
Blank
Check Qty Zero : A Note about the situation
It specifies whether delivery document item can be maintained with Qty zero when in
delivery a new Item enter with Qty Zero, then this value determines the system
response.
SAP-SD
166
SAP-SD
167
SAP-SD
168
PACKING
In Business Materials are determined with packing material. Packing Materials
maintained in the Business as a Normal Inventory. Packing can be carried out during
Sales Order Processing or Delivery document processing usually at delivery
document as a DLN.
Configuration Settings:
a. Define Number Ranges for Handling Units: |Handling Unit is nothing but a
Packing Material to be packed.
Path:
IMG
Logistics Execution
Shipping
Packing
Define Number Ranges for Handling Units.
Click on Change Intervals Icon
Click on Interval Icon
Define Number Ranges.
b. Packing Control by Item CatExory: Here for Delivery Document Line item is
going to be controlled for packing item.
Define Packing Material Types: Ex: Cranes, Trucks and Pallets. This packing
materials are assigned to Material Master.
Ex: V075 Skeleton Box.
Save it and Exit.
Define Material Group for Packing Material: Here Packing Materials are grouped
that can be used to pack similar materials. Ex: G010.
Define Allowed Packing Materials:
Go to New Entries
Assign Packing Material Type
Ex: V075 to Material Group for Packaging Material. Ex:G010
Go to MM01 and Create Material Master with a Material Type Packaging and make
sure that data maintained in
Basic Data 1: Material Group Packaging Material G010.
Sales : General / Plant: Assign Packing Material Type V075
Assign Allowed Packaging Weight : 1000
Remaining Data is same as other Material.
SAP-SD
169
SAP-SD
170
RETURNABLE PACKAGING
Process Flow:
A. Scenario 1:
B. Scenario 2:
OR LF F2 LA LR
OR LF F2 LF F2
SAP-SD
171
Save it.
Go to VL01N and carry out inbound delivery
Select PGR
Save it.
Go to MMBE and check the balance.
Scenario 2:
If the Customer doesnt returns returnable packaging material
Go to VA01
Specify Document Type : LN
Item CatExory : LAN
Schedule Lines : C3
Movement Type : 623
Save it.
Go to VL01N
Go to VF01 and raise the Invoice.
Save it.
VOV8 of LA
SD Doc CatExory : C
Doc Pricing Procedure : A
Delivery Type : LR
VOV7 of LAN
NIL
VOV6 of F3
Movement Type : 622
Check Item Relevant of Delivery
Check TOR and Availability Check
VOV8 of LN
SD Doc CatExory : C
Doc Pricing Procedure : A
Delivery Type : LF
Delivery Related Billing Type : F2
VOV7 of LNN
Special Stock : V Returnable Packaging with Customer
Billing Relevance : A Delivery Related Billing Document
Pricing : X
Save it.
VOV6 of C3
Movement Type : 623
Check Item Relevant of Delivery
Check TOR and Availability Check.
SUN SURYA TECHNOLOGIES
SAP-SD
172
Save it.
SAP-SD
173
SAP-SD
174
FAQ: What are the Two fields that are transferred to FI/CO module after saving
Invoice?
A. Reference Number
B. Allocation Number
Account Assignment / Pricing:
Account Determination Procedure : Ex: KOFI00
Assign Account Determination Procedure to billing document type (F2) by which
system transfers billing information SD to FI.
FAQ: What is the difference between Proforma Invoice and Standard Invoice?
OR
How you will differentiate there two?
Ans: Proforma Invoice doesnt have Account Determination Procedure as it need not
to transfer Billing information from SD to FI.
Output / Partners / Texts:
Output Determination Procedure : V10000
Define output determine procedure in
IMG S&D Basic Functions Output Control Output Determination
Output Determination using Condition Technique Maintain Output
Determination for Billing Document Maintain Outputs Types.
Ex: RD00 Invoice.
Output Type : RD00
Header Partners : FK
Item Partners : FP
In IMG Partner Determination Procedure defined and assigned to Billing Document
Header and Item.
Path: IMG
Sales and Distribution
Basic Functions
Partner Determination
Setup Partner Determination
Setup Partner Determination for Billing Document Header, Item
Text Determination Procedure for Billing Document Header and Item
Ex: 05
In IMG Text Determination Procedure defined and assigned to Billing Document
Header and Item.
Check Delivery Text
This indicator copies text from the Delivery Document Header.
SAP-SD
175
SAP-SD
176
MAKE TO - ORDER
Business produces material based on MRP irrespective of the Sales Order. I.e.
Make To Stock.
If the standard product is going to be changes slightly according to the customer
requirement then business manufacture that particular material for particular
customer is called as Make To Order.
Inventory is going to be maintained with special stock indicator E (E Orders on
Hand)
Configuration Settings:
Create Material Master by maintaining General Item CatExory Group 0001 (Make
To Order).
Availability Check 02
Transportation Group 0001.
Go to VA01 and raise the Sales Order.
Item CatExory : TAK
Schedule Line CatExory : CP
Requirement Type (Procurement Tab) : KE (Individual Customer Order without
Consumption)
Requirement Class : 040 (Transaction Code OVZG)
Check TOR and Availability Check
Special Stock : E
VOV7 of TAK
Billing Relevance : A
Pricing : X
Go to MB1C
Maintain stock with a special stock indicator E
Movement Type 561
Special Stock E
Specify the Sales Order Number, Line Item Number and save it
Go to VL01N
Maintain Data
Go to VF01
Save it.
SAP-SD
177
VARIANT CONFIGURATION
In Business some Materials are going to be manufactured according to the
requirements of the Customers. Those Materials are called Configurable Materials.
That can be configured according to Customer requirements during Sales Order
Processing.
Every configurable material is a Object. Every Object has Characteristics. Every
Characteristics has a Single or Multiple Values.
Ex: Configurable Material = CAR (Object)
Car has Engine, Steering, Color, Body (Characteristics)
Radial Tyres or Normal Tyres is single or multiple values.
Business some times manufacturers these characteristics in advance without taking
Sales Order into consideration as a normal finished goods and maintain inventory as
a variant.
Business can calculate variant pricing also.
Configurable Material can be exploded as a BOM.
Requirements are transferred to MRP by requirement type KEK
Material should be maintained in inventory with a special stock indicator E
To control configuration dependencies can be used.
Dependencies controls the combination of characteristics and their values.
Variant configuration in SAP doesnt / can not control complete configuration.
Configuration Settings:
Variant configuration in SAP has a intExration with CA Classification
LO Material Master
PP Bill of Material, Routings, MRP, Production Orders, Master Receipts.
SD Sales, Conditions
MM Purchasing
CO Costing and Technical Module.
SAP-SD
178
PROCESS FLOW
Step1:
Define MRP Groups:
Path:
IMG
Material Management
Consumption Based Planning
MRP Groups
Carryout Overall Maintenance of MRP Group
Specify Plant and create
Specify MRP Group with description
Create
Create
Save it
Maintain
Specify MRP Group and
SUN SURYA TECHNOLOGIES
SAP-SD
179
Click on Maintain
Click on Scheduling / Document Type
Select Scheduling Info Record and
Assign NB to standard purchasing order
Document type for subcontracting and stock transfer order document.
Save it and go back.
Click on rescheduling Horizon
Specify 7 Days
Save it and go back
Planning Horizon (Click on)
Specify 7 as planning Horizon
Save it and go back
Check maximum MRP Interval (Click on)
Specify 7 as value
Save it and go back
Click on safety stock
Specify 100 as Available safety stock
Creation Indicator (Click on)
Create Purchase Requisition : 1
Create MRP List : 1
Schedule Lines : 3
Save it and go back.
Click on Project Planning Requirements Grouping
Check Grouping Requirement
Save it and go back and exit.
Define MRP Group for Each Material Type
Go to New Entries
Specify Material Type : KMAT
Plant and MRP Group (Created in Previous Step)
Save it and Exit.
Define MRP Controllers
Path:
IMG
Materials Management
Consumption Based Planning
Master Data
Define MRP Controllers
Choose standard MRP controller Ex: 1000
Click on Copy as Icon and
Define MRP Controller
Save it and Exit.
SAP-SD
180
SD Configuration Settings
Create Configurable Material
Path: Logistics
Materials Management
Material Master
Material
Create (Special) MMK1 Configurable Materials
Specify Industry Sector (mechanical Engineering)
Click on Select Views and Select Views Basic Data, Classification, Sales : Sales
Organization Data 1 and 2, Sales : General/Plant Data, MRP 1,2 and 3
Maintain Data in Basic Data 1
General Item CatExory Group : 0002 Configurable Configuration Management
CM Relevance : Relevant for Configuration Management
Classification:
Enter into the View
Sales : Sales Orgn Data 1:
Delivering Plant :
Tax Classification No :
Conditions :
Sales : Sales Orgn Data 2:
Material Statistic Group : 01
Volume Rebate Group : 001
Material Pricing Group : 01
Account Assignment Group : 03
General Item CatExory Group : 0002
Item CatExory Group : 0002
SAP-SD
181
M R P 3:
StratExy Group : 25 Make To Order for Configurable Material.
Save it.
Step 2:
Create Characteristics:
Characteristics are nothing but features of object (Object = Material)
(Transaction Code : CT04)
Path: Logistics
Cross Application Components
Classification System
Master Data
CT04 Characteristics
SAP-SD
182
Step 3:
Create Class (CL01)
Class holds characteristics that can be assigned to Materials (Master). Through
configuration profile class can be assigned to Material.
Path: Logistics
Cross Application Components
Classification System
Master Data
CL02 Create
Specify the Class Name : Ex: ZCAR
Class Type : Ex: 300 Variants
Maintain Data in Basic Data 1
Description
Check Warning Message
Characteristics Tab: Assign all Characteristics that we created under 2nd Step.
SAP-SD
183
ENGINE_CAP
TRANSMISSION
FUEL
TYRE
ACCESSORIES
COMFORTS
STEERING
ZSDCOM
Save it.
Step 4:
Create Configuration Profile (CU41):
Path: Logistics
Central Functions
Variant Configuration
Configuration Profile
CU41 Create
Choose Material
Specify the Material Number
Press Enter
Specify the Profile Name : Ex: ZCONFIG_Profile
Assign Class Type : Ex: 300 Variants
Organizational Areas : V Sales and Distribution
Status : 1
Click on Class Assignment
Specify our Class : Ex: ZCAR
Press Enter
Save it.
Step 5:
Create Object Dependencies (CU01): Dependencies allows us to create
relationships and restrictions between different characteristic and characteristic
values.
1. Ex: Preconditions
Preconditions are used to hide the characteristics and characteristic values that are
not allowed and there by ensures that configuration of an object is consistent.
Ex: If Engine_Cap = 800CC then system should not display comforts.
Engine_Cap IN (1000CC, 1400CC, 2000CC)
Go to CU01
Path: Logistics
Central Function
Variant Configuration
Dependency
Single Dependency
CU01 Create
Specify Dependency Name
SUN SURYA TECHNOLOGIES
SAP-SD
184
Ex: ENGINE_CAP_COMF_RECORD
Press Enter
Specify the Description
Status : 2 (IN Preparation)
Select Dependency Type and select
Precondition
Click on Dependency Editor and write the code.
CODE:
000010 ENGINE_CAPIN (100cc, 1400cc, 2000cc)
Select Check Button and Execute
Save it
Change the Status as 1 (Release)
2. Selection Conditions:
Selection conditions are used to ensure that all the objects relevant to a variant are
selected.
Selection conditions determine which variants required a specific component or a
operation.
Selection conditions determine when it is a mandatory to assign a value to a
characteristic.
Ex: 800cc, 1000cc, 1400cc cars can have only Petrol as a Fuel. Where as
2000cc cars can have Petrol / Diesel / CNG
Go to CU01
Specify Dependency Name : ENGINE_CAP_FUEL_SELECCOND
Specify Description : ENGINE_CAP_FUEL_SELECCOND and
Select select condition
Click on Dependency Editor and write the Code.
CODE:
000010 ENGINE_CAP = 2000cc.
Check it (CTRL + F2)
Save it
Change the status as a 1 released
Save it.
3. Action Conditions
Action Conditions are used to infer values for Characteristics. Values that are set by
an action can not be over written.
Ex: 1000cc Car can be supplied only with 1+4 transmission system. That means if
user selects ENGINE_CAP=1000cc then system automatically proposes 1+4 as a
transmission.
SAP-SD
185
Go to CU01
Specify Dependency Name : ENGINE_CAP_TRANS_ACTION
Specify Description : ENGINE_CAP_TRAN_ACTION
Select Action
Click on Dependency Editor and write the Code 000010 SELE.TRANSMISSION =
1+4 if ENGINE_CAP = 1000cc
Check it and Save it.
Change the status as 1 Release
Save it and go back.
4. Procedures:
Procedures are used to information values for characteristics like Actions but
unlike Actions the values that are proposed by procedures can be overwritten.
Ex: Radial Tyres can be given for 1400cc and 2000cc with Power Steering and
Cross Play Tyres can be given for 800cc and 1000cc cars with Normal Steering.
Go to CU01
Specify Dependency Name : ENGINE_CAP_ST_PROCEDURE
Specify Description : ENGINE_CAP_TY_ST_PROCEDURE
Select Procedure
Click on Dependency Editor and write the Code 000010 $ SELF.TYRE = RADIAL if
ENGINE_CAP.IN (1400cc, 2000cc) and
000020 $ STEERING = POWER
000030 $ SELF.TYRE = CROSSPLAY if ENGINE_CAP IN (800cc, 1000cc) and
000040 $ STEERING = NORMAL.
Click it and Save it.
Change the status 1
Save it and go back.
SAP-SD
186
SAP-SD
187
SAP-SD
188
REBATES
Rebates are special kinds of discounts, that are going to be paid to the Customer
Payer based on certain sales volume with in certain specified time period.
Configuration Settings
a. Check Rebate Processing Active should be activated while defining the Sales
Order.
b. Check Rebates should be activated at Customer Payer.
c. Check Relevant for Rebates should be activated while defining Billing Document
Type.
Define Agreement Types:
Path:
IMG
Sales and Distribution
Billing
Rebate Processing
Rebate Agreements
Define Agreement Types
Here Agreement Types Ex: 0001 Group Rebate
0002 Material Rebate
0003 Customer Rebate
0004 Hierarchy Rebate
0005 Independent of Sales volume define.
Select 0002
Go to details Icon
Proposed Valid From
Proposed Valid To
Assign valid periods of Rebate Agreement.
Payment Method: Assign Payment Method that is going to be used for rebate
settlement. Ex: Cash, Cheque etc.,
Default Status:
Ex: A Settlement is being checked for release
B Agreement released for settlement
C Settlement has been created
D Final settlement of agreement already carried out.
Blank Open.
Verification Levels: F Display Totals by Payer / Material.
The value of this field specifies how the rebate agreement totals should be displayed.
Check Different Validity Period: The value of this field specifies that whether rebate
agreement condition records validity period should be same or not.
SAP-SD
189
SAP-SD
190
SAP-SD
191
SAP-SD
192
SAP-SD
193
Choose Sales Document : Header Data Option from Source Table Screen (Right
side Screen) and select the fields Sold To Party (KUNNR), Sales Organization
(VKORG), Distribution Channel (VTWEX), Division (SPART) and Material (MATNR)
from Sales Doc : Item Data option.
Click on Copy + Close option
Click on copy
Save it go back and Create Field Catalog for Key Figures.
Specify the Field Catalog Name with Description
Specify Application : 01 Sales and Distribution
Select Key Figures field catalog option
Press Enter
Click on Key Figures
Select Sales Doc : Header Data Option from Source Table
Select Net Value (NETWR)
Click on Copy + Close
Click on Copy
Save it and go back.
Create Info Structure:
Path:
IMG
Logistics General
Logistics Information System
Data Basis
Information Structure
Logistics Data Warehouse
Maintain Self-Defined Information Structures
Create
Specify Info Structure Name (Between S501 To S999).
Specify the Application : 01 S & D
Specify type of IS (Info Structure) : Blank Standard
C Without Period Unit
T Transfer to SAP-BW
Specify Blank
Check Ping Possible
Click on Choose Characteristics Option
Select Characteristics field catalog
(Which was created in the previous step)
Select the fields from Field Catalog Fields
Click on Copy + Close Icon
Click on Copy
Click on Choose Key figures option
Select Key Figures field catalog and select the fields from the field catalog fields
Click on Copy + Close
Click on Copy
Assign Unit as a 31 (WAERK) Doc Currency
Check Sum. If it is activated, system accumulates the key figure values.
Check Fix. Set this indicator if you want to Fix the values of this Key Figure in the
planning table of Flexible Planning.
Save it, check it and click on generate, Go back Save it and Exit.
SAP-SD
194
SAP-SD
195
SAP-SD
196
SAP-SD
197
Go to MMBE and check the stock overview in both supplying and receiving storage
location.
Two Step:
Date:
Plant 1000
Supplying Storage Location 0001
Receiving Storage Location 0002
Removal from Supplying Storage Location
Movement Type 313 Transfer Posting Storage Location to Storage Location
remove from Storage.
Go to MB1B
Specify supplying Plant and Storage Locations
Specify Receiving Storage Location
Specify Material and Qty
Press Enter and Save it.
Go to MMBE and check the stock balance in supplying storage location.
Go to MMBE of Receiving Storage Location Stock In Transfer.
Go to MB1B and receive the stock in transfer into receiving storage location (0002)
By specifying Movement Type 315 Transfer Posting Storage Location to Storage
Location Place in Storage.
Specify Plant and Receiving Storage Location
Specify Material and Qty
Press Enter and Save it.
Go to MMBE of Receiving Storage Location and Stock in Unrestricted usage.
SAP-SD
198
SAP-SD
199
Go to MB1B
Specify Movement Type 351 Transfer Posting to Stock in Transit from Unrestricted
Usage.
Specify supplying Plant (1000)
Storage Location (0001)
Press Enter
Specify the Purchase Order Number
Press Enter
Go to MIGO to receive the Goods with reference to Purchase Order.
Check Item OK
Click on Post and Check the Stock Overview.
Stock Transport Order with SD Delivery (One Step Intra) with in Company Code.
Data:
Plant 1000 Issuing Plant
Plant 1100 Receiving Plant
Configuration Settings
Create Customer Master by using XD01 Transaction Code under 1000 / 10 / 00
(Plant 1000). Ex: 700031
Create Vendor Master by using XK01 Transaction Code under 1000 / 10 / 00 and
make sure that in purchasing data section, Extras, Add Purchasing Data and
Specify Plant (Supplying)
Go to IMG MM Purchasing Purchase Order Set Up STO
Define Shipping Data for Plants
Choose Supplying Plant (1000)
Maintain Sales Area
Save it and Exit.
Choose Receiving Plant (1100) and Assign Customer Number.
Save it and go back.
Maintain Delivery Type (NK) and Checking Rule (RP)
For only supplying Plant 1000 with Document Type UB.
Path is same up to set up STO
Assigning Delivery Type and Checking Rule
Choose Document Type UB
Assign Supplying Plant (1000)
Assign Delivery Type (NL)
Assign Checking Rule (RP) and Save it.
Decide One Step Procedure or Two Steps Procedure.
a. One Step:
Assign Supplying Plant Receiving Plant
Check Document Type and Checking Rule (If it is activated then it is a One Step
Procedure).
SAP-SD
200
1100
1100
1100
SAP-SD
201
SAP-SD
202
Go to OVKK and Assign Pricing Procedure ZIV002 to supplying Plant Sales Area
with Document Pricing Procedure N IB Stock Transfer condition Type ZIVU.
Go to VK11 and maintain condition records for ZIVU.
Specifying Supplying Plant, Customer Number and Price.
Go to ME21N and raise standard Purchase Order
Specify Vendor Number
Specify Purchasing Organization (2200)
Specify Company Code (2200)
Specify the Material Number and Qty
Specify Receiving Plant and Storage Location
Save it and note down the P O Number.
Go to V4OB RPL Delivery
Specify Shipping Point (1000)
Go to Purchase Order Tab and specify Purchasing Document and Supplying Plant.
Click on Execute
Select Line Item and Click on background
Click on Next and note down Delivery Document Number
Go to VL02N
Go to Subsequent Functions
Crate Transfer Order (LT03) and note down the Transfer Order.
Go to VL02N and Carryout PGI
Go to VL02N and note down Movement Type 645 Transfer to Cross Company.
For Two Steps (643 Transfer to Cross Company)
Go to MMBE and check the Stock Balance.
Go to VF01 Document Type ZIVU IB Stock Transfer.
Save it.
Process Flow for Two Step :
ME21N VL10B VL02N MIGO MIRO
Go to VF01 (NLCC)
SAP-SD
203
Batch Management
In Business especially Pharmaceutical and FMCG Materials are processed in
Batches. In some Industries Materials should be processed only in Batches as a
statutory requirement. By using Batch Management Concept defectives can be
identified and LIFO and FIFO methods can be implemented. Materials usually
processed from Production to Sales by Batches only. SAP uses condition technique
to determine Batch Management concept as a intExration with Production, Inventory
Management and Sales and Distribution.
Configuration Settings: Create Material Master and make sure that checking group
of Availability Check should be CH Batches and check Batch Management in
Sales:General / Plant Data.
Activating Batch: Batch can be activated at 3 levels.
a. Client Level
b. Plant Level
c. Material Level
If it is client level then Batch Data is specific to client.
If it is Plant Level then Batch Data is specific to Plant.
If it is Material Level then Batch Data is specific to Material Level only. That means
when the Material moving to other plant then Batch Data should be maintain
separately at Plant Level. Usually it is at Material Level.
Path:
IMG
Logistics - General
Batch Management
Specify Batch Level and Activates Status Management
Batch Level
Check Batch Unique at Material Level
Save it and go back.
Maintain Internal Batch Number Assignment:
Path: IMG
Logistics General
Batch Management
Batch Number Assignment
Activate Internal Batch Number Assignment
Activate Batch Number Assignment
Check Automatic Batch Number Assignment Active
Maintain Internal Batch Number Assignment Range:
Click on Change Icon
Click on Number Ranges
Click on Change Intervals
SUN SURYA TECHNOLOGIES
SAP-SD
204
SAP-SD
205
SAP-SD
206
Header
Sub-Item
TAQ
TAP
TAE
TAN
ERLA
LUMF
Go to MM01 and Create Material Master by specifying General Item CatExory Group
for Header Item ERLA / LUMF and for sub-item as a NORM.
Go to MB1C and initialize the stock for both items.
Create BOM (CS01)
Path: Logistics
Sales and Distribution
Master Data
Products
BOM
BOM
Material BOM
CS01 Create
Specifying Header Material, Plant and BOM usage 5 (Sales and Distribution)
Press Enter and Specify Sub-Components with Qty
Save it.
Go to VA01 and raise the Sales Order by specifying Header Material and Check
BOM Explosion.
SAP-SD
207
FAQS
1.
If Customer Payer accepts invoices and invoice list how do you configure it?
ANS:
2.
If ship to party wants to receive shipment on particular day. Ex: Saturday. How
do you configure it?
Can you create Customer Material info records from customer master?
Ans: Yes
PATH: XD02 or VD02 Sales Area Data Session
Environment
Then, Customer Material information
4.
ANS: Yes
PATH: DX02 or VD02 Sales Area section, Extras, Blocking Data, specify the
particular area.
5.
How system determines Item Category for a line item in the Sales Order?
ANS: System determines item category for a line item in the Sales Order by taking 4
factors into consideration.
e) Sales document type (that end users enter). Ex: TA/OR +
f) Item Category Group (from its Material Master). Ex: NORM +
g) Usage of the Material (of the Material). Ex: NIL +
h) Higher level item category (of the line item) Ex: NIL
= default item category (of line item). Ex: TAN Standard item.
6.
ANS: Yes
7.
ANS: Header Level Category, Item Level Category and Schedule Line Category.
SAP-SD
8.
208
ANS: Exclusive indicator restricts the system to read condition record for particular
condition table if it finds condition records for one condition table. That means it
stops search procedure with one condition table it finds condition records.
Select Access Sequence and click on Fields Control button and press enter.
9.
10.
ANS: Assign Credit Control Area to Sales Area. Sales Area is a combination of
Sales Organization, Distribution Channel and Division.
11.
Can we Create Document Flow Records only for Inquiry, Quotation and Sales
Order?
ANS: Yes. It is relevant for Contract Business Cinereous. We have to Assign Value
as a 2.
12. Can we carry out New Pricing during Sales Document Processing?
ANS: YES. By using option update in Item Condition Screen.
13. What are the Two fields that are transferred to FI/CO module after saving
Invoice?
A. Reference Number
B. Allocation Number
14.
How System Determines Plant for a line item in the Sales Order?
ANS: System follows search criteria for determine plant for a line item in the Sales
Order.
d) System first checks customer material info records. If Plant has been
maintained, then it will take from Customer Material Info records or else it will
go to b
e) Customer Master Ship to Party or else it will go to c
f) Materials Master or else Plant should be determined manually during Sales
Order Processing.
15. Can we carry out New Pricing during Sales Document Processing?
ANS: YES. By using option update in Item Condition Screen.
SAP-SD
209
FAQ: What is the difference between Proforma Invoice and Standard Invoice?
OR
How you will differentiate there two?
Ans: Proforma Invoice doesnt have Account Determination Procedure as it need not
to transfer Billing information from SD to FI.