Professional Documents
Culture Documents
SAP SD Material: Systems Applications and Products in Data Processing For Business Applications', and It Deals
SAP SD Material: Systems Applications and Products in Data Processing For Business Applications', and It Deals
SAP: - ‘Systems Applications and Products in Data Processing for Business Applications’, and it deals
with more than 50 modules.
SAP
Ex: - ABAP, BASIS Ex: - PP, MM, FICO, SD, QM, SCM, HR…
ABAP :‘Advanced Business Application Programming’ – It’s a Language, used with open SQL Standard
GUI : Graphic Unit Interface
1. Integration
2. Security.
Company: It’s an Organizational Unit which can create according to the particular countries commercial law.
Company Code: It’s the legal Entity which takes care of the Entire Business activities of a company.
• Each company codes maintain separate P&L Accounts and Balance sheet.
Note: Company code is defined by Finance Mode.
Sales Organization: It’s the responsible organization unit which takes care of the Entire sales transactions of a
company.
• Sales Organization is Responsible for all the terms and conditions of sales deals and negotiations.
Distribution Channel:It specifies the channel through which goods are sold to the End Customer.
Ex: - Whole sellers, Retailers, Direct Customers…
Division:The Total no. of Materials or Services for which the company is doing sales are divide into different
Divisions.
• The Division is a group of similar Products which have some characteristics and fall into one
productRange/ Product line.
Sales Area:It’s the Combination of sales Organization, Distribution Channel and Division.
• The Sales Area always represents the basic sales process of a company.
Sales Line:It’s the Combination of Sales organization and Distribution Channel, Sales line is always port of a
Sales Area.
Sales Office:It represents the Geographical aspect of the structure of the client. Sales Office is also linked to
Sales Area.
Sales Group:The Employees working under a sales office are divided into different Sales Group. Sales Group is a group
of similar codes of sales people, and this Entry is not mandatory.
Relations: 1.Relation between company code and Sales Organization, are Company code can have multiple sales
Organization to handle the sales transaction, where as one sales organization can only work for the Company Code, so
relation between Company code and Sales Organization is one to many.
Reliance Communications
Company Code
Sales Organization
D ChannelDivision
Sales Area
Sales Office
Sales Group
The Relation between Sales Organization and Distribution Channel: One Sales Organization can be used
multiple distribution channel for sales purpose and one Distributor Channel can be used for multiple sales
Organization, so the relation between Sales Organization and Distribution channel is Many to many.
Relation between Sales Organization and Division: One Sales Organization can sell Division Products and
One Division Products can be sold to multiple sales organization, so the relation between sales Organization and
Division is many to many.
Ex:One to Many Sales Org to Division
Reliance Comm.Ranbaxy
Many to Many
Many to Many
Ranbaxy
Wh Rt Wh Rt
Relation: From the distribution channel we can sell products of different Division, similarly One Division
products can be sold from multiple Distribution channel, so the Relation between Distribution Channel and
Division is Many to many.
Note: Division is always Sales Organization, it specify i.e. Division is controlled by sales organization, but not by
the Distribution channel.
Organization structure
Unit
Company Code
One to many
Sales Organization
Many to Many
Sales Office
Sales Group
Defining sales Organization:
Path: From Easy Aceess menu select looks --- Customizing --- IMG --- Edit Project --- SAP Reference
IMG ---- Enterprises Structure.
(Or)
SPRO--- SAP Project Reference Objects--- Reference IMG--- Enterprises structure ------------ Definition
---- Sales & distribution ---
1. DefineSales Org
2. D. Channel
3. Sales Office
4. Sales Group’
5. Define Plant
6. Division from(Logistics- General)
Assignment:-
Assigning 1.Sales Org to Company Code
2. D.Channel to Sales Org
3. Division to Sales Org
4. Set up Sales Area / Maintain Sales Area
5. Sales office to Sales Area
6. Sales Group to Sales Office.
7. Plant to company Code
8. Plant to Sales Org
1. Public Holidays :- Define Public Holiday required and there are depends on country Government.
2. Holiday Calendar :- Assign the defined Holidays here which specifies list of holidays in a Company.
3. Factory Calendar :- Specify theno of working days in a weak and Assign the respective Holiday
Calendar.
1. General Data
2. Company Code
3. Sales Area Data
1. LSMW: ‘Legacy System Migration Workbench’ ( Legacy – Non SAP System ( Consultant) )
2. BDC: Bath Data Communication—ABAPer
Each screen contains different data sets/ Tab pages and each Tab page contains different Fields.
General Data:-This Tab page specifies ‘Address and other relevant details of the Customer’.
Customer Classifications: Specifies the classification of customers which can be based on their sales Turn over,
this field can also be used to determine a Specify Price for a particular customer.
Tabs:
Unloading Points:- Specify the place at which goods are to be Unloaded for the Customer.
Ex:Godown
Goods Receiving Hours: Specify the timings in which goods are to be Unloaded at the Customer Location.
Creating Contact Person: EA Menu—Logistics – S&D – Master Data – Business Partners – Contact
Person -- VAP1 – Create.
Company Code: ‘Account Management’
Reconciliation Account: The Reconciliation A/C in the GL A/C is the A/C which is updated parallel to
the sub ledger A/Cfor normal posting. Enter 140000asReconciliation A/C number for Practice.
Payment Transaction: (Term of Payment) : Specifies the key for Defining the payment Terms
composed of Cash discount Percentages and Payment Period.
Payment History Record: If we Check/ Select this field the payment history of the customer will be
recorded in his ‘Credit Master Data’
Sales Area Data:In the sales Tab specifies the Sales District.
Customer Group: Specifies the Grouping of customers, which can be based on the nature of their Business.
Ex: Industrial Customers, Trading Customers.
Customer Pricing Procedure: This field Enables the system to automatically propose the corresponding pricing
procedure for the customer during ‘Sales Document Pricing’
Shipping- Tab
Shipping conditions: This field Enables the system to automatically propose the corresponding shipping point
during the Sales Document Pocessing.
Delivery Point: Specifies the Plant from which goods are delivered to the customer.
POD- Proof Of Delivery→ If we Select / Check this field the customer will become relevant for
proof of Delivery, i.e. Customer is going to send POD after receiving the Material.
Order Combination: If we Check /Select this field we can combine multiple Orders for a customer in Order to
create single Delivery.
Partial Delivery per Item: Specifies whether the Customer requires full or Partial Delivery of the Item.
Billing Document: TabIt’s a Conditional Discount Rebates:If we check this field then the customer business
eligible for Receiving Rebates.
Delivery and Payment Terms:
Inco Terms: These are Internationally Accepted Shipping Terms and Conditions and it specifies certain
Internationally Accepted / Recognized Terms and Condition that the company and the receiving party must
follow for the Shipping Transaction to be successfully completed.
Inco Term – Part 2: Specifies the place from which goods are delivered.
Assignment:Terms of Payment is mentioned in ‘Company Code Data’ and ‘Sales Area Data’.
Accounting:
Account Assignment Group: This field Enable the system to post the Sales Values of the customers to the
corresponding. GL Account during Revenue.
Account Determination;
Tax Classifications (Output Tax): Specifies whether the customer is ‘Liable for Tax’ or not.
Partner Functions:
Sold To Party:Specifies the customer for Placing the Order with the company (SP).
Note:
1. Depending on the Requirement all the partners can be same or they differ.
2. If all the Partners are same we need to create the customer as Sold to Party and maintain the
Same number for all the Partner Functions.
3. If the partners differ we need to create Master Records for those parties and specifies those numbers in
Master data of Sold to Party for the corresponding Partner Function.
4. We will have all the Partner Functions, only for Sold to Party.
1. Account group 0001- Sold to Party : It specifies whether the Customer, what we are creating is SP,
SH, BP or Py.
Note: A/C Group controls fields and views of Customer Master Data.
In The Initial Screen View
2. Company Code: Specify the Company Code with which the customer is doing the Business.
3. Sales Organization:Specifies the Sales Org with which the Customer Executes the sales transaction.
4. Distribution Channel: Specifies the channel through which the Customer places the order.
5. Division:Specifies the Division for which the Customer places the order.
Enter -- Save
Defining Account Group:
Path: SPRO → FA → A/C Receivable & Payables → Customer A/C → MD → Preparation for
Creating Customer master data → Define A/C Group with screen Layout.
Ex: -0001 – SP 0003 -- BP
0002 -- SH 0004 – Py
Note:In the Definition of A/C group we can control the ‘Fields’ status, that is we can make as a required entry
(or) optional entry (or) in Display Mode (or) we can suppress it.
Path: From the same path select Create No. Ranges for Customer Account → select the Button
Change Intervals → click on Insert Interval.
Note: 1. For a No. Range, if we check/select the Field External, and it will become an External No.
Range, i.e.While creating the customer, user has to specify a no. for the Customer, otherwise it will become an
Internal No. Range, where the system automatically generates the No. for the customer.
Path:From the Same path select Assign No. Ranges to A/C Groups.
4.Partner Determination Procedure :To get the required Partner Functions into the Sales Transactions (
Sales Order – Delivery – Billing).
• First we need to add them into Customer Master to get the required Partner Functions in the
customer Master for the required A/C group Automatically, we need to maintain partner
Determination Procedure.
Note: 1. For any Partner Function, if we select / check field “Unique” , we cannot have
Multiple Partners of that function in a customer.
2. it’s a ‘partner Type ‘, which differ Partner Functions, whether the Partner Function
Belongs to Customer (or) Vendor (or) Any other Business Partner.
Note: 1. Assign partner Functions to A/C Group and – Enter and save.
2. For any Partner Function, if we check / Select field Not Modified, it cannot be Changed in the
Customer Master, and if we check the Field Mandatory, it becomes Mandatory in the Customer
Master.
Conclusion:
Ex:HAWATrading Goods
FERT Finished Goods
HALV Semi Finished Goods
ROH Raw Materials
VERP Packing Materials.
Select Views:
• Basic Data 1
• Basic Data 2
• Sales Organization 1 Select these depends on the Requirement.
• Sales Organization 2 Remove or Add
• Sales Text
• MRP 1
• Accounting 1
Sales Organization: Specify the Sales Organization from which the material is sold.
D.Channel: Specify the Channel through material is sold.
• Petrol -- Litres
• Rice -- Kgs
• Gold -- Grams
• Soap -- Each or (1 pack = 10 Eaches)
3. Sales Organization 1:
Note:1. we need to specify a Sales Unit only it differs from Base Unit.
2. If the Sales Unit differs from Base Unit we can maintain the conversion factor.
I.e. The Quantity relation Between Sales Unit and Base Unit.
Ex:
1. 3% discount with in 15 days
2. 2% discount within 30 days Payment Terms.
3. 1% discount within 45 days
4. 0% discount within 60 days
Note: DefineTax Classifications for ‘Master Data (Customer & Material), Go to OVK3and
OVK4, then Define them for output Tax MWSTclassification.
• Minimum Order Quantity: Specify the Minimum Quantity of the Material that
may be ordered by the customer for each sales Order.
Note: Minimum Order Quantity is always maintained in Base Unit of measure ( Ex: PC, Each, Pack)
• Rounding Profile: Specify the Key, that the system uses to Adjust the Order
Proposed Quantity to the nearest deliverable unit.
Note:If customer place an Order for 90 Bolts (100 bolts = 1 Pack), then we have to Adjust to
nearest Quantity, it means create the Order for 100 bolts (1 pack).
4. Sales Organization 2: -
• Account Assignment Group: This Field Enables the system to post the Sales
Values of different Material types to the corresponding G/L A/C, during
“Revenue Account determination”.
Availability Check: Specifies whether and how system check the Availability of the Material
during the sales document Processing.
Batch Management: If we check this field the material can be handled in Batches.
Transportation Group: Specifies a grouping of material that has the same Transportation
Required. (Ex:0001 for Pallets)
Loading Group: Specifies a grouping of the materials that have the same Requirements.
Ex: 0003 for Manual.
Note: This loading group Enables the system to determine respective shipping point during sales
document processing.
6. MRP 1:
MRP Type:(Material Resource Planning), specifies about whether and how the
requirement of the material Planned.
Note: This MRP type will Enable the system to determine schedule line category during sales
document process.
7. Accounting 1:
Valuation Class:This key enables the system to post the cost of different material types to the
corresponding G/L A/Cs. (With this COGS Price will be Realized)
Error: while creating the Material if you get an Error, just check “The Company Code does not exist”or
‘Fully Not Maintained the data’.
Select the Required Company Code & Specify the ‘Current Year’ and ‘Period’ (OMSY).
If customer is placing an Order for a Material by his own code rather the Original code of the Material. We need
to maintain CMIR, so that in the Sales Order Processing if we enter the customer material no., system
automatically determines Original Material Number.
Note: In the Overview screen specify the original Material code In the Field Material No. and In the Field
Customer Material specify the code by which customer places the Order for the Original Material.
Path:SPRO → S&D → Sales Documents → Sales Document Header → Assign Sales Area to
Sales Document Types (Consistency Check)
Solution: 1. In the Customer Master Record Specify the Pricing Procedure (1).
2. Go to OVKK → New Entries → Assign the Pricing ProcedureRVAA01
Solution:Go toOB62→Enter the Chart of Accounts INT (International) , if INT is not Accepted then
Enter CAUS.
Solution:Go to OB37→select the requirement Company Code and Assign the Fiscal Year Variant K4.
Solution:Go to MMR → Select the Button ‘Additional Data’ and maintain the description for the
material Language.
❖ Error: To get the Tax classification on the CMR and MMR for the required country.
Solution:Go to OVK1→ go to New Entries → Assign the Tax Category MWST to the required country.
When the customer Places an Order for goods or Services in an Organization, the Organization
creates a Sales Order. This sales order is called a Sales Document in the Sales and Distribution.
Structure of Sales Document:
1. Header Level Data:The data that is applicable for entire sales document is called Header
Data.
Ex: To see the Header Level data in sales Document select Icon ‘Display document Header
Details’ in the overview screen or from the main menu ‘Go To’ Header select the required view.
2. Item Level Data:The General Data Entered at Header Level by default applies for all the
items in the document but each and every Item will have it’s own Related Information which
applies for that particular item only is called Item Level data.
Note: Even though the Header Level data copies for all the Item, the data can be changed at the
item level. To see the item data of an Item select the ‘Line Item’ and from the main menu ‘ITEM’
Select the require view or you can double click on the ‘Item’.
3.Schedule Line Data: It gives the information regarding the delivery dates and the
corresponding confirmed Qty. depending on the Availability of the Material each and every Item
can have one or more no. of Schedule lines.
To see schedule line data of an Item 1st go to corresponding Item data and select the views
‘Schedule Lines’.
Va01Va02Va03
S Order
(Or)
Delivery Invoice
(Lf)
Vl01nVl02n Vofa
Creating the Sales Documents with Reference:
Note:CreatingQuotation (Va21):
• In the overview Screen – Maintain the Relevant Data, and complete the document and
SAVE the Quotation.
• In the overview Screen – Maintain the Relevant Data, and complete the document
Take care of ‘Incompletion Data’.
• Specify the Quotation No. in the Field Offer, and select the button Copy
• Now Data will be copied from Quotation to Order.
• If required, change the data and SAVEit.
Document Flow
If we create the Document with the Reference, the system form a Flows a document in
which, if we know one document No. with the help of ‘(Display Icon)Document flow
(Next to Order button),we can see the other Document numbers, and we can display
other documents also.
Controlling data in Sales Documents
Depending on the requirement, the data in the Sales Document has to be processed
accordingly for this we 3 control parameters in the sales document.
Path:SPRO → S&D → Sales → Sales Documents → Sales Document Header → Define Sales
Document Types.
1. IN – Inquiry
2. QT – Quotation
3. OR – Sales Order
4. RO -- Rush Order Sales Document type
5. CS – Cash Sales Va01
6. RE – Returns
7. DS – Scheduling Agreements
8. G2 – Credit Memo Request
9. L2 – Debit Memo Request
Ex:A – Inquiry
B – Quotation Sales document Category
C – Sales Order
2. Sales Document Blocks:Specifies whether sales document type is blocked for Processing.
Note: If we block a sales document type the user can’t create a new sales documents of that time,
but the sales document already created, before setting the block can be changed (Va02), or
displayed (Va03).
Ex:If any shoppers discount given for the festival season likes Diwali and that block will be opened again
for Diwali or the other seasonal time (depends).
3.No. Range Internal & External Assignment: Customer need, we will have to give Internal or
External No. Range. And this Define like CMR, but create for Sales Document.
• Specifies the No. ranges that either the system ( if it’s Internal) or the user ( if it’s External)
uses for giving nos. for the sales documents, while Saving them.
4. Item No. Increment:Specifies the value by which the Item No. Increases in the Sales document
onlywhen the system automatically generates Item no, and if the user Enters a manual no.
system will also accepts it.
5. Sub Item Increment: Specifies now the Sub Item nos. are incremented in the sales Document.
Note: If we don’t specify any value here, the Sub Item will be Incremented by a value by which
the main Item Increments.
General Control
7.Item Division: If we select / check this field the Division at Item Level in the sales
document, will be determined from the corresponding Material Master, otherwise the Division
entered it Header Level applies for the all line Items by default.
8. Check Division: Specifies how the system reacts, if the division, if Item Level refers from
the Header Level.
10. Check Purchase Order No.Specifies if we checkthis field, if the POno. is already existed
in the Sales Document, will not allow to take the same PO no. for the Other One.
11. Check Credit Limit: Specifies whether the system carries are Out of a credit Limit
Check during the sales document processing.
Ex:Credit Limit Check relevant for OR, RO and some time CS, not for In&Qt
Transaction Flow
12. Screen Sequence Group:Specifies which Screen we see during a Particular Transaction
and which Sequence they appear. i.e. In, Qt (or) Or.
Ex: Select from the Popup that which screen has to perform.
AU –forOrder
AG – for Qt
13. Transaction Group: Specifies a grouping that allows you to control certain characteristics
of a Transaction Group according to Sales Document Type. The Transaction Group controls
the types of sales documents, which we can process with certain system transactions in the
sales process.
14. Document Pricing Control: The field Enables the system to automatically proposed a
corresponding Pricing Procedure, depending on the sales Document type, during the sales
Document.
15. DisplayRange: Specifies whether the system displays all the Items (or)only main Item in
the sales Document.
16.Function Code for overview Screen: Specifies which Over view Screen (Tab), we reach
during the sales document processing after we Enterthe data on the Initial Screen.
17. Outline Agreement Messages (or) Contracts (or) Schedule Line Agreements: Set an
Indicator here if we want to receive a Message informing that Open out Line Agreements
exists, while creating the Sales Document, depending on the indicator we select here ( A or B
or C), the system checks Open out line Agreements, either at Header Level for the customer
or at Item Level for the Material.
Shipping:
20.Delivery Type:Specifies the corresponding Delivery type of the Sales Document type.
Ex:LF – Delivery Document Type – Delivery with Reference to Sales Order, and
‘No Shipping Data’ have to specified for In & Qt.
21. Delivery Block: Specifies whether the sales document is block for Delivery Processing.
Note: Delivery Block in the sales document type is applicable for the All Line Items,
and delivery block at Item Level (Item Category) is applicable only for that Particular Line
Item, delivery block at Schedule Line Level is more effective using which you can block the
delivery for different Schedule Lines of an Item.
22. Shipping Conditions: If we specify the Shipping Conditions here, during the sales
document processing, the value for Shipping Conditionswill be determined from this field,
but not from the Customer Master Data,shipping condition will enable the system to
determine corresponding shipping point in the sales order.
Ex: Plant
Loading Group
CMR
Shipping Conditions
Sales Document
Shipping point
Delivery
Billing
23. Delivery Related Billing type / Order Related Billing type: Specifies the corresponding
billing type of the sales document type.
• No billing data has to specified for In & Qt, because these are not relevant for billing.
24. Billing Block: Specifies whether the sales document is block for Billing process.
Note: Use Billing blocks for ‘Credit Memo Request (G2)’, ‘Debit Memo Request (L2)’
and ‘Return Order (RE)’.
Requesting Delivery Date/ Pricing Date/PO type:
25. Propose Delivery Date: If we Select/ Check this field the system process current date
as Requested Delivery date in the sales document.
26. Lead time in days: specifies the no. of days into future that the system used to propose
the requested delivery date in the sales document.
Note: If delivery is on 20th/ 09/ 11, but if customer again asks for future date like
25/09/11 then it’s possible.
(Or)
If can be given as Fixed date depends on customer need, 20th/ 09/11, then
it’s only on 20 /09/11, but everything is depends on Factory calendar Date.
th
27. Propose PO Date: If we checkthis field the system automatically proposes current
date as PO date in the sales Document.
28. Proposal for Pricing Date: Specifies the date that the system uses to propose the
Pricing date in the sales document.
ITEM CATEGORY
The data at Item Level in the sales document is controlled by Item category,
Depending on the requirement, how we process the data in the sales document varies for different material.
QT OR
In this the same Item has to process in different ways in different document types,
i.e. An Item in QT is not Relevant for Shipping & Billing, where has it’s Relevant for both these
Transactions (shipping /Billing) in Sales Order.
Ex: 2. M10
Item
10 -- M10 -------- 10 Rel Pricing & Billing M20 Not Rel. Pricing & Billing
In this ‘The same Item has to be Processed in different ways in the same
document, i.e. If we offers Free goods for an Item the main Qty has to be Priced, by not the Free Goods
Qty.
Ex: 3.OR
In the Above Item Different Materials have to be processed in different ways in the same
document, i.e. if we Enter a 3rd Party Item in the sales order, the system has to create a purchase order for
which a purchase Requisition should be created as it’s not required for Standard Item (NORM).
Similarly if it’s a BOM Item it should display the Components also.
To fulfill all such requirement we need to define different Item Categories with the corresponding
functionalities and make sure that the system by default determines those Item categories for the
corresponding materials/ Items in the corresponding sales documents.
Path:SPRO → S&D → Sales → Sales Docks → Sales Document Item → Define Item Cat.
Ex:AFN → Inquiry
AGN → QuotationStandard Item Category
TAN → Order
AFNN
Note:Item Cat. Group is (in Sales Org2) AGNN Free Good Standard Item cat.
Item Categories are Standard (Above& Next) TANN
TAS Third Party
Note:
➢ I.e. we can specify the Quotation is complete after the full Quantity has been
Referenced ‘B’. (Or)
➢ So we must use this for Inquiry and Quotation but we may not use this field
for Contractsand for other Order Types.
Billing Relevance:This field specifies whether the Item is Relevant for Billing, if so it also
specifies the Reference Document for creating the Billing Document.
Ex: The Item in the document IN & QT cannot be billed to control this corresponding Item
Categories AFN, AGN Respectively are made as ‘Not relevant for billing’.
➢ But the Item Category TANwhich is use in Sales Order and it’s ‘Relevant for Billing’.
Billing Block: Specifies whether the Item is blocked for Billing Process.
Ex: All the standard Items Categories like AFN, AGN and TAN are relevant for
Pricing.
➢ For Free of Goods (Free of charge)TANN is Relevant for Pricing, but it takes 100%
discount, so for TANN, the value for this field must be ‘B’ (Pricing for the Free
Goods 100%). And TANN is relevant for Billing Also.
Billing Item:If we check this field, the Business data (sales, shipping, Billing…etc)at Item
level is allowed to differ from the Business Data at the Header Levelin the sales
document.
➢ If we don’t check this field, the fields should be Grade outand will not allow changing
at Item Level.
➢ Any information determines to salesor shipping is called Billing Data.
Schedule Line Allowed:Specifies whether we can have the schedule line in the Sales document
or not.
➢ The terms such as the Items in Credit Memo Request doesn’t have the schedule
line, to control this we should not check in corresponding Item category ‘G2N’.
Item Relevant for Delivery: Specifies whether the Text Item (Brochures n etc) is Relevant for
delivery process or not.
Note: By default every item is Relevant for delivery Excepts like ‘Text Items’, if we
want to make Text Item Relevant for delivery this field has to be checked in the
corresponding Item Category TETX. We can make an Item Category as Text Itemby
specifying the value ‘B’in the Item Type.
Ex:The items we process in the sales document ‘RE’ are the Return Items, to specify
this we have to check this field in the corresponding Item category.
Weight and Volume Relevant: If we check this field the system determines Weight & Volume of
the material during the sales document processing.
Credit Active:If we check this field the Item will Relevant for Credit Management Activities.
Ex: We will not check this for Cash Sale (CS)→ BVN.And the Items in the cash sale
cannot be processed on credit basis to control this field should not be checked in the
corresponding Item CategoryBVN.
Determine Cost: If we check this field the system determines cost of the Item from (MModule)
during pricing in the sales document.
Rounding Permitted:If we check this field the Order Quantity of the Item will be rounded
depending on the ‘Rounding Profile’ specified in the Material Master.
Note: This is not required for AFN and AGN, but can be used for TAN.
Order Quantity = 1:If we check this field, the order quantity is each line Item will be limited to
‘01’.
During the sales document processing the system automatically determines the
corresponding Item Categories for the Items, for this the following setting is required.
Item Category
Usage
Sl. No. Sales Document Type Item CategoryGroup Usage Higher Level Default Item Cat
1. Inquiry NORM -- AFN
2. Inquiry ( Free Goods) NORM -- AFN AFNN
3. Quotation NORM -- AGN
4. Quotation ( Free NORM -- AGN AGNN
Goods)
5. Order NORM -- TAN
6. Order ( Free Goods) NORM -- TAN TANN
7. Cash Sale NORM -- BVN
8. Cash Sale ( Free NORM -- BVN BVNN
Goods)
9. Rush Order NORM -- TAN
10. Returns NORM -- REN
11. Credit Memo G2 NORM -- G2N
12. Debit Memo L2 NORM -- L2N
13. Order ( Third Party) BANS -- TAS
14. Order ( Text Item) NORM TETX TATX
Note: 1.Higher Level Item Category is the Item Category of the Higher Level Item (Main Item).
2. If we maintain any Item Category in Manual Item Category Field, while determining Item
categories (VoV4), system will allow to manually change the Item category in the sales order
other wise No.
Item Relevant for Delivery:If we check this field the item relevant for delivery Processing.
Note: The items in Inquiry and Quotation cannot be delivered to control this we don’t
check this field in those corresponding schedule line category AT & BN respectively. But
the schedule line categories CP, CV, CN and DN are relevant for delivery.
Order Type:Specifies the Purchase Requisition type‘NB’ → Third Party.
Note: we need to specify the document type ‘NB’ in this field for the Schedule line
category (CS)which is used for Third party.
Requirement / Assembly: If we check this field the requirement of a material will be transferred to
Inventory Management.
Availability Check:If we check this field the system carries out the Availabity Check for the items
in the document, It’s better Practice to check for all (IN, QT & OR).
During the sales document processing the system automatically process corresponding schedule line
category for the Items for the following setting is required.
Path:SPRO → S&D → Sales documents → Sales Document schedule line → Assign Schedule Line
Categories.
Item Category
MRP Type
Ex:1.M10 M11
Ex:2.
Note:If we don’t have MRP type in ‘Material Master’ in Assignment Leave it Blank.
Sales Dock Item category Usage HL Item Default Item MRP Type Schedule line
type Group category Category Category
Conclusion
Sales Document Type (OR) + Item Category (TAN) + Usage + H Level Item category
TAN = OR + NORM
CP = TAN + ND (and try these in Sales Order (Va01)
Pricing
Condition Master Data:In the business processing the entire pricing information of a material is
divided in to 4 elements.
For Each pricing elements we have corresponding condition typein the SAP System.
1. PR00 → Price
2. K004 → Material Discount
3. K005 → Customer / Material Discount
4. K007 → Customer Discount
5. MWST → Tax out Put
6. KF00 → Freights
Steps:
1-10 100
11-20 99
21-30 98
31-40 97
Select the condition Record and ‘Go ToDetails’ and specify the Limit
values for the condition record in the fields Lower and Upper Limit,so that during the sales Order
Processing the Condition Amount of that Condition Type cannot be changed to a Value which falls
beyond these limits.
Note: Pricing information in the Sales Order an be seen in condition tab of the Item data, and it can also
be Viewed at Condition tab of Header Data also.
Pricing: For the system to determine pricing elements during sales document processing, we have to
maintain ‘Condition Techniques’and Condition Technique is nothing but the Back End Setting,what
we do as a consultant to trigger correct price for the valid Key Combination during sales order
processing, Condition Techniques comprises of
1. Condition tables
2. Access Sequence
3. Condition Type
4. Pricing Procedure Definition
5. Pricing Procedure Determination.
Condition Table: Condition table contains the Key Fields for maintaining the Condition Records for a
Condition Type (PR00…etc), Depending on the requirement, we can use (Take) any field in the
Condition Table based on which the pricing is decided.
➢ One condition type can have multiple condition tables, and one condition table can use for
multiple condition pricing types.
Ex:Condition Table
➢ When we need to classify the customers in a class we do in CMR → General Data → Marketing
→ Customer Class → we can select to give what percentage of price to give for the different
customer.
Steps:
➢ Specify a Number for the Condition Table which must be between 501-999.
➢ From the Field catalog select the required key field to have in the Condition table
➢ While maintaining the Condition Record we can set the Validity Periods, with the help of the
Fields Valid On and Valid Toand to get these fields we have to check the fields with Validity
Period in the definition of Condition table.
➢ Select the button Technical View, here the fields these are checked as Key Appears at key
leveland the fields are checked at Footer fieldsappears at Footer Level, while maintaining
Condition Records.
➢ Select the button Local Object for saving the condition table.
➢ If you wanted to add some fields to the list get those from Allow Fields in the main sheet.
Pricing Process
Pricing Procedure
Condition Types
Access Sequence
Condition Table (Key Combination) to Condition Record
Access Sequence:
➢ Access Sequence is a Search Strategywith the help of which the system determines Valid
Condition Records for the Condition Types during sales Document Processing.
➢ For this we have to Place the Required Condition tables in the Access Sequenceand
Assign it to Required Condition Types (PR00…etc).
➢ One Access Sequence can have multiple Condition Tables and if required One Access
Sequence can be used for multiple condition Types.
➢ If we have multiple Tables in an Access Sequence, The Order in which they are placed is
Important generally it’s from Most Specific Combination to Most Generic Combination.
Ex:1.
Customer + Material (Condition Table 999)
(ABCD) + (M10) = 100
PR00
Ex: 2
M10 M10
Path: SPRO→ Basic Functions → Pricing → Pricing Control →Define Access Sequences →
Maintain Access Sequences