Upload
aamrnadh
View
237
Download
5
Embed Size (px)
Citation preview
Sales Document Controls (VOV8)
1. IN Inquiry (VA11)
2. QT Quotation (VA21)
3. OR Standard Order (VA01)
4. RO Rush Order (VA01)
5. RE Return Order (VA01)
6. RK Invoice Correction (VA01)
7. CS Cash Sale (VA01)
8. CF Consignment Fill up (VA01)
9. CI Consignment Issue (VA01)
10. CONR Consignment Returns (VA01)
11. CP Consignment Pickup (VA01)
12. CR Credit Memo (VA01)
13. DR Debit Memo (VA01)
14. QC Quantity Contract Generally (VA41)
15. WK1 Value Contract Generally (VA41)
16. WK2 Value Contract Generally For Group of Martial (VA41)
17. DS Schedule ling Agreement (VA31)
18. SDF Subsequent Delivery Free of Charge
19. FD Delivery Free of charge.
Process Flow for Sales and Distribution.
INQUIRY (IN) VA11
QUATION (QT) VA21
ORDER (OR) VA01
NOTE : In PGI process system will generate Accounting entry.
Inventory account Dr to Cost of goods sale Cr.
Process flow for THIRD PARTY business Process
TOR
Enterprise Structure:
Company, Company Code, Controlling Area belonging to FI-CO Module, Sales organization, Distribution Channel, Sales office, Sales Group, etc, belongs to SD module, purchasing organization, purchasing group, etc belonging to MM module & so on.....
DELIVERY (VL01N) PICKING
PACKING
PGIINVOICE (VF01)
CUSTOMER
COMPANY (OR) MRP CONTROLLER
PUR.REQU
PUR.ORDER
VENDOR
DELIVERY
INVOICE TO COMPANY
INVOICE TO COUSTOMER
Distribution channels Distribution channels
SALES DOCUMENT
Sales document consists of sales related information.
Ex:-customer related information, Material related Information, Quality terms, Conditions for pricing etc.
Structure of sales document: -
Sales document consists of three parts
1. Header data2. Item data3. Scheduline data.
COMPANY CODE
Sales.Org -1 Domestic
Sales.Org - 2 Export
Header Data (VBAK)
Item line Data (VBAP)
Scheduline Data (VBEP)
Header Data: It is a data which applies to all the line items in the sales document
It consists of Customer master Data, Control Data, and Configuration data.
In control data (Sales org unit, Distribution Channel, Division etc.)
Some parts of configuration data (Pricing procedure determination), Header data will be controlled by document type. The table for header data is VBAK
Item Data: it is a data which is applicable for particular line item in the sales document
Ex: Material Master.
The Source of item data is
(1) Material master(2) CMIR(3) Condition master(4) Some parts of configuration data.
Item data will be controlled by item category
The table for Item Data is VBAP
Schedule line data: It is the data which consists of delivery data and confirmed quantities.
The source of schedule line data is configuration data only. Schedule line data will be controlled by Schedule line category.
The table for Schedule line data is VBEP
Tables for sales document
Sales Document Header Data VBAK
Sales Document Item data VBAE
Sales Document scheduline data VBEP
Header status VBUK
Business data VBKD
Partner data VBPA
Document Flow VBFA
Document Pricing Procedure KONV
Sales Document Types
Document type controls the header data of sales document
Transaction code to create the new document type is VOV8
Path for define new document types
SPRO – SALES AND DISTRIBUTION – SALES – SALES DOCUMENTS – SALES DOCUMENT HEADER—
DEFINE SALES DOCUMENT TYPE.
Every document will have document type link INQUIRY – QUATION—ORDER etc.
Process Flow for Sales and Distribution.
INQUIRY (IN) VA11
QUATION (QT) VA21
ORDER (OR) VA01
DELIVERY (VL01N) PICKING
PACKING
PGIINVOICE (VF01)
SR.NO PROCESS DOCUMENT
T-CODE
1 INQUIRY IN VA112 QUATION QT VA213 ORDER OR VA014 CREDIT MEMEO CR VA015 DEBITMEMO DR VA016 RUSH ORDER RO VA017 CASH SALE CS VA018 RETURN ORDER RE VA019 VALU CONTARCT GENERALLY WK1 VA4110 VALUE CONTRACT MATERIAL SPECIFIC WK2 VA4111 CONSIGNMENT ISSUE CI VA0112 CONSIGNMENT FILL UP CF VA0113 CONSIGNMENT RETURNS CONR VA0114 CONSIGNMENT PICKUP CP VA0115 QUANTITY CONTRACT QC VA3116 SCHEDULING AGREMENT DS VA3117 SUBSEQUENT DELIVERY OF FREE OF
CHARGESDF VA01
18 FREE OF CHARGE FD VA0119 INVOICE CORRECTION RK VA01
Create order VA01
Order type OR
Sales area G100, G1, G1
Sold – party number - 10
While creating sales order we will get ‘Document type is not assigned to sales area’.
Solution:
SPRO – SALES &DISTRIBUTION— SALES— SALES DOCUMENT – SALES DOCUMENT HEADER –
ASSIGN THE SALES AREA TO SALES DOCUMENT TYPE – DOUBLE CLICK ON COMBINE SALES ORGANIZATIONS – THEN COMBINE DISTIBUTION CHANNELS— THEN DOUBLE CLICK ON DIVISIONS –
THEN DOUBLE CLICK ON ASSIGN SALES ORDER TYPES PERMITTED FOR SALES AREAS – SAVE IT
In this configuration we can restrict the document to sales area or distribution channel or division
Again go to VA01 and crate order and do the delivery (VL01N) and invoice (VF01).
INQUIRY (VA11)
Whenever customer inquires about the products we create inquiry document in SAP.
Inquiry document consists of customer details, Material details, Quantity details.
Inquiry document is on internal report,
The way of inquiring can be walk-in, telephone or internet.
Quotation (VA21)
Quotation is a legal document which we send to the customer, whenever customer inquires about our products.
Quotation document consists of customer details, material details, quantity details, valid period, pricing terms and conditions.
ORDER (VA01)
If customer satisfied with our quotation then he will place the order.
Order is a conformation document to deliver the goods to customer. Order consists of customer details, material details, quantity details, valid period, and pricing and validity period.
Whenever we create sales order in SAP in system background perform various activities.
Partner determination, listing exclusion, material determination, free goods, availability check, delivery scheduling dates, credit check ,text determination, output determination, transfer of requirement .
DELIVERY (VL01N)
If order is confirmed and if stock is available then we create a delivery document.In delivery process we have three activities.
1. PICKING2. PACKING 3. PGI(POST GOODS ISSUE)
PICKING it consists of material, quantity, storage location.
PGI (POST GOODS ISSUE)
When you do PGI system will perform background activities.
It updates stocks.
It will generate the inventory accounting document
COST OF GOODS SOLD ACCOUNT DEBIT TO INVENTOTRY ACCOUNTING CREDIT
It updates in LIS.
It updates in due billing
It updates in credit management
After PGI we load the goods and immediately we create the invoice and send the customer.
In INDIA scenario without invoice we cannot send the material.
INVOICE (VF01)
After delivery we create invoice, while creating invoice system will perform background activates.
Accounting document will generate
Customer account debit to revenue account credit.
Profitable analysis document generate.
Cost center document generates.
It updates the document flow,
It updates the LIS.
It updates the credit management.
RETURN ORDER
The below scenario customer will return the goods
Damaged the stock
Defective stock
Expired stocks
Dumping
Whenever customer finds the damage or defective in goods/stocks he will inform to the company, company will send the person to customer place to cross check the goods/stock.
Then employ will cross check the goods and prepare the return notes. Then employ will submit the return notes to sales office .then the user will create the return order w.r.f. to invoice and do the delivery create return invoice.
When we create return invoice the accounting entry is
Revenue account debit to customer account credit. When we create the return invoice amount will detect from the customer outstanding. And stock will be added to return storage location.
RETURN ORDER PROCESS
Create a return order wrf of invoice
Here delivery type LR, Billing type RE,
ERROR: While creating return invoice we will get error, No billing documents were generated
Solution: Go to the change mode of VA02 and remove the billing block.
CREDIT MEMO:
RE
INVOICE
Return Delivery
Return Invoice
We credit memo request if you want deduct the amount from customer outstanding without receiving the goods.
The below scenario we deduct the amount from the customer outstanding without receiving the goods.
1. If goods are totally damaged which are not in the position to take back?2. User mistakenly over charge the previous invoice.3. Secondary sales promotions activities .i.e. Company will ask the customer to give
discount to their customers.The above 1&2 scenario we create credit memo with ref to invoice, third scenario we create credit memo directly. In this process we don’t have delivery process because no goods movement
Accounting entry revenue entry debit to customer account credit (credit memo is nothing but invoice)
DEBIT MEMO REQUEST (DR)
We do debit memo request to add the amount from customer outstanding.
The below scenarios we do the debit memo request.
1. Users mistakenly undercharge the previous invoice.2. Charging interest to customer for late payments
In debit process we don’t have delivery process because there is no goods movement.
In debit memo process accounting entry is
Customer account debit to revenue account credit, debit memo is nothing but invoice
CASH SALE (CS)
Cash sale is also nothing but counter sale, where the customers walk into the outlet /showrooms pick the martial to the counter and pay the cash take the bill and leave the counter.
Here customers are one time customer.
In each sales process we crater the order system will delivery automatically in back ground, in the order itself we take the invoice and give to the customer.
When counter is free then we go to deliveries and do the PGI & INVOICE
When we do the cash sales invoice the accounting entry is
SATTLEMENT ACCOUNT DEBIT TO REVENUE ACCOUNT CREDIT
Shipping condition 10, go to OVL2 and maintain shipping condition
PROCESS FOR CASH SALES
RUSH ORDER (RE)
It is an immediate delivery, if customer is asking to send the material immediately.
We do rush order process.
PROCESS FOR RUSH ORDER
DELIVERY FREE OF CHARGE (FD)
It is the process of sending the samples to customer without charge. There is no accounting document
CASH SALE
INVOCIE
DELIVERY
RUSH ORDER
INVOCIE
DELIVERY
PROCESS FOR DELIVERY FREE OF CHARGE (FD)
ERROR
NO PRICING PROCUDER IS DETERMINED
Go to OVKK and assign the document pricing procedure C
Sales .Org Dis.Chan Division Docu.Procedure Cust. ProceG100 G1 G1 C 1
SUBSEQUENT DELIVERY FREE OF CHARGE (SDF)
It is the process of replacing goods to the customers.
Whenever customer returns the goods either we deduct the amount from customer outstanding or we replace the goods to customer.
If we want to replace the goods we should not create the return order and return invoice process.
SUBSEQUENT DELIVERY FREE OF CHARGE PROCESS
Create a SDF wrf of return order
DELIVERY FREE OF CHARGE
PROFORMA INVOICE
DELIVERY
SDF
RETUN ORDER
RETURN DELIVERY
NO INVOICE
Whenever we create SDF wrf to return order, the return orders items should be rejected, then only system will allow creating SDF(because if we put return order items as rejected then system will not allow to create return invoice)
If user already created return invoice then system will not allow creating SDF, because we cannot reject the return order items.
RESONS FOR REJECTION
If we assign reason for rejection in return order it controls two things,
1. If we assign the reasons for rejection and we create SDF for that return order system will not allow to create return invoice
2. If we create return invoice then system will allow assigning the reasons for rejection and without reason for rejection system will not allow creating SDF.
INVOICE CORRECTION REQUEST (RK)
We use invoice correction request whenever user do some mistakenly in invoice, by using invoice correction request we can either add the amount or deduct the amount from customer outstanding.Invoice correction request will be created always wrf to invoice
Invoice correction
DELIVERY
PROFMA INVOICE
RK
CREDIT MEMO G2
While creating invoice correction request each line item will be copied as two line items in invoice correction request document.
1st line item credit
2nd line item debit
System will allow changing the credit item; we can only change the debit item.
If net value positive customer account in credit.
If net value negative customer account in debit.
QUANTITY CONTRACT (QC)
It is an agreement between company and the customer for supplying the goods of a minimum particular quantity with a particular specific period. Every contract should have mutual benefit, here the benefit to company is assured sales and benefit to customer is less price discount.
PROCESS FOR QUALITY CONTRACT (QC)
VALUE CONTRACT GENERAL (WK1)
QUALITY CONTRACT (QC) VA41
DELIVERY (VL01N)
RELEASE THE ORDER (OR) VA01
INVOICE (VF01)
It is agreement between company and customer for supplying the goods of a particular value with in a specific validity period.
Valid contract general is not specific material it is group of material. The group of material value contract general is created by assortment module
Create assortment module
PATH
Easy access – logistics – sales &distribution – Master data —Products – Value contract – Assortment module – Create (T-Code WSV2) — Module type (6.Value contract module)—Module (give some description- value contract test) – enter valid from and valid to – enter the materials – save it.
Then note the assortment module number
Then go to VA41 – WK1 create value contract – Mention the target value — Mention Assortment module – Enter the material and save it.
Error: - No pricing procedure could be determined
Solution: go to OVKK and maintained document pricing procedure as Y
'G100 G1 G1' 'Y' '1'
Release the order (VA01) process: - create order wrf of contract— click on item selection and select material and enter the quantity then save it.
Then create a delivery and invoice
PROCESS FOR VALUE CONTRACT (WK1)
VALUE CONTRACT (WK1) VA41
DELIVERY (VL01N)
RELEASE THE ORDER (OR) VA01
VALUE CONTRACT SPECIFIC MATERIAL (WK2) TCODE VA41
It is agreement between company and customer for supplying the goods of a particular value and specific material with in a validity period.
Create value contract (WK2) and mention the material and value.
Release the order wrf to WK2 and delivery the material and create invoice.
PROCESS FOR VALUE CONTRACT (WK1)
SCHEDULING AGREEMENT (DS) T- C0DE VA31
It is an agreement between company and customer for supplying the goods of a particular quantity with in a specific validity period with predefined delivery dates.
Schedule line agreement
VALUE CONTRACT (WK2) VA41
DELIVERY (VL01N)
RELEASE THE ORDER (OR) VA01
INVOICE (VF01)
INVOICE (VF01)
05.07.2015(200 qty)
30.07.2015(500 qty)
Delivery VL01N
Invoice VF01
CONSIGNEMT PROCESS
Dumping the stock at customer place and keeping the owner ship with the company. When our customer sale the goods their customer then we rise invoice to our customer and we transfer ownership to our customer.
We do consignment process to move slow moving items and newly launched products into the market.
Benefit to customer for consignment
1. No investment (No Risk)2. Special discount
Consignment is one of the push strategies; consignment process will be further classified in four types.
1. Consignment Fill up 2. Consignment issue3. Consignment returns4. Consignment Pickup
Consignment Fill Up (CF)
Here we supply the goods to customer place keep the ownership with the company.When our management decides to send the goods a consignment basis then management will inform same to customer if customer accepts we do consignment fill up process.When we do consignment fill up process 1. Stock will reduce from unrestricted stock and stock will be added to consignment stock.2. There is no inventory accounting document generated because we are not transferring the
owner ship to customer.3. Consignment fill up process is not relevant for invoice.
CF
VL01N
Performa
Consignment Issue Process (CI)
We do consignment issue when our customer sold the goods to their customer.
When we do deliver the goods in consignment issue process stock will be reduce from consignment stock and we raise the invoice to customer.
1. Why we are doing delivery in consignment issue process? Transfer the owner ship to customer & reduce the stock from the consignment stock.
Consignment Return Process (CONR)
When end customer returns the goods to our customer then we do the consignment return process.
When you do return delivery in consignment returns what will happen?
Stock will be added to consignment stock
Performa
CI
VL01N
Invoice
CONR
VL01N
Invoice
Inventory accounting document generates and the accounting entry
Inventory account debit to cost of goods credit.
Consignment Pickup Process (CP)
If customer returns to take back the consignment stock when we d o consignment pickup process
When we do consignment pickup process stock will be reduce from consignment stock and stock will be added to unrestricted stock.
Consignment pickup process is not relevant for invoice.
Inventory accounting document will not be generated.
Reverse process
Invoice cancellation (VF11)
Reverse PGI (VL09)
Delete Delivery (VL02N)
Delete Order (VA02)
Combined multiple orders into single delivery: - T – CODE (VL10A/VL10C)
VL10A – ENTER – SHIPPING POINT – DELIVERY REQUSTED DATE – SHIFT TO PARTY THEN CLICK AND EXCUTE
THEN SELECT ALL AND CLICK ON BACKGROUND – THEN CLICK ON LOG – SELECT THIS LINE – CLICK ON DOCUMENT – SELECT THE DELIVERY AND CLICK ON DISPLAY DOCUMENT – GOTO CHANGE MODE – DO PICKING AND PGI— DO INVOCIE AND SAVE IT.
Combined multiple Deliveries into single invoice: - T – CODE (VF04)
CP
VL01N
Billing list – select – collective documents /online.
SALES ORDER DOCUMENT CONTROLS
Path for document type controls: SPRO – SALES &DISTRIBUTION – SALES – SALES DOCUMENTS – SALES DOCUMENT HEADER – SALES DOCUMENT TYPES.
Sales Document Category: -
This field controls the function of the sales document
Document Name Document Type CategoryINQUIRY IN AQUATION QT BORDER OR CRUSH ORDER RO CCASH SALES CS CRETURN ORDER RE HCREDIT MEMO REQUEST CR KDEBIT MEMO REQUEST DR LCONSIGNMENT FILLUP CF CCONSIGNMENT ISSUE CI CCONSIGNMENT RETURNS CONR HCONSIGNMENT PICKUP CP CINVOICE CORRECTION RK KVALUE CONTRACT GENERAL WK1 GVALUE CONTRACT SPECIFIC MATERIAL WK2 GQUANTITY CONTRACT QC GSUBSECQENT DELIVERY FREE OF CHARGE SDF IFREE OF DELIVERY FD ISCHEDULINE AGREEMENT DS E
INDICATOR:-
We use only Indicator only for invoice correction (RK), here we maintained indicator as ‘D’
Indicator D controls that each line item from invoice will be copied from two line items in invoice correction request document.
SALES DOCUMENT BLOCK:-
If you maintain this then system will not allow to creating a sales document with that document type.
NUMBER SYSTEMS :-( VN01)
In sales document we have option of both internal number range and external number range.
The T-Code to define the number range is VN01.
ITEM NUMBER INCREMENT:-
This field controls how the line item number incremented in sales document.
SUB ITEM NUMBER INCREMENT:-
This field controls how the sub item number incremented in sales document.
Sub item concept will come below scenarios.
Bill of material (BOM), free goods, material determination, cross sealing.
Bill of material:-
Computer
CPU
MONITOR
KEY BOARD
MOUSE
Material Determination:-
Substituting one material in place of other material due to non availability of stock.
We have stopped manufacturing of the old product and coming out new features of the product.
Free goods:-
It should always with relationship with main item, offering the goods free of cost with the main item
Ex: - if customer purchases X material 100qty, then we will get Y material 20 qty.
Cross selling: - selling the additional products along with main product.
Ex:-selling pouch and blue tooth along with mobile
GENERAL CONTROL
Reference mandatory:
This field controls when any preceding document is required or not for creating a sales documents.
Division:
This field controls how system is respond if header division deviates from the item division
Blank – No Message,
1 – Warning message,
2 – Error message.
Item Division:
If we check this line item division in the sales document will be copied from material master.
If we uncheck this line item division in the sales document will be copied from header division.
Probability:
This field specifies the chances of converting the document into order.
Sap standard says inquiry 30%
Sap standard says quotation 70%
Sap standard says order 100%
Read Info Record:
If check this in sales document then only system will read the CMIR and determine into sales document.
If you uncheck this in sales document system will not read the CMIR in sales document.
Check Purchase order number
If maintained here while creating sales order system will check whether the combination of purchase orders already is exit in previous order or not, if yes system will give warning message.
It will restrict the duplication of orders.
Enter purchase order number
If we check this while crating sales order if PO number is blank then system will take sales order number as PO.
It will help to track the sales orders which we have not received the purchase order from customer.
Committed Date:
If you maintained this in sales document we will get extra field in sales order scheduline data.
Any order which we committed first we will give priority to that customer.
Material Entry Type:
This field controls how the material should be entered in sales document i.e. based on material number or product catalog.
Check credit limit:
This filed will be used in creditmanagemt.
Credit management is the process of managing the credit limits of the customer.
Credit management can be figured two ways.
1. Simple credit management 2. Automatic credit management
If we go for simple credit check then we have to maintain here A, B, or C.
A – Run simple credit check with warning message.
B — Run simple credit check with error message.
C – Run simple credit check with assign delivery block.
If we want to go for automatic credit check then we have to maintain D
Sr.no Simple Credit Auto matic credit
1In simple credit check
we can block the material at order level
In automatic credit check we can block the martial at order,
delivery and PGI level
2In simple there is no
concept of risk categories
In automatic we have three type of risk categories
3
in simple system considers only
receivables while performing the credit
check
In automatic system considers open order values ,open
delivery values, open invoice values
Receivable means invoice is raised but customer is not yet paid.
Credit Group
We use this field only for automatic credit check, this field controls which transaction to block, if customer credit limit exceeds. I.e. order lever, delivery level, PGI level.
TRANSACTION FLOW
Screen Sequence Group
This field controls which screen should displayed while creating sales order.
Ex: contracting page, ordering page.
Display Range
This filed controls whether to display all items or only main item into sales document.
Incompletion procedure:
This procedure consists of list of required fields which user has to enter mandatorily while creating sales order.
If any of required field is missing either system will not allow creating sales order or if system is allow to create sales order status is showing incomplete data.
F Code for overview screen:
This field controls which tab should display while creating sales order by default.
Transaction group:
Transaction group controls T-code of sales document type.
Document pricing procedure
Document pricing procedure is one of the parameter to determine the pricing procedure in sales document.
We assign the sales document pricing procedure to the combination of
Sales area + document pricing procedure + customer pricing procedure
Quotation message
If you maintain this while creating a sales order system checks for this customer is there any open quotation existing or not, if yes system will display the list of the open quotations.
Outline agreement message
If you maintain this while creating a sales order system checks for this customer is there any open contracts existing or not, if yes system will display the list of open contracts.
Status Profile
It is an order released process, after creation of sales order by end user, the order will be sent to authorized persons to cross check and release. After releasing the status only system will allow to create delivery.
Alternate sales document type 1 & 2
This field is will help to shift the sales document one order type to another document type. If user is confusing between any two documents type by using this fields we give solution to the client
Incomplete message
If we check this field while creating sales order if end user is missing any mandatory fields then system will not allow to save the sales document.
If we uncheck this if user is missing the mandatory fields in sales document fields then system will allow to save the sales document.
Variant
Variant will help to control the fields in sales document that is whether to make the fields mandatory or optional or suppress
T-code for variant SHD0
SHIPPING
Delivery type
If you assigned delivery type here then by default system takes while creating delivery.
Standard Delivery type LFReturn Delivery Type LR
Cash sale BVDelivery W/O reference LO
STO delivery type NLSTO returns NLR
Inter Company STO NLCCInter Company STO returns NCR
Immediate Delivery
We use this field only for cash sale and rush order process.
This field will help to create delivery automatically in the background
In this field we can maintain
A – Immediate delivery
X — immediate delivery if quantity is confirmed.
Delivery Block
If we assign delivery block here then order is blocked for delivery, then authorized person has to cross check and release the block then system will allow to create the delivery.
Shipping Conditions
We use this field only in cash sales and rush order.
If you maintained shipping condition in sales document it over rights the customer master an determine the sales document
BILLING
Delivery related/Order related billing type
If you maintain billing type here it will automatically determined while creating billing document
If it is delivery related billing then system will determine billing type from delivery related billing type.
If it is order related billing then system will determine billing type from order related billing type.
Standard billing type F2Cash sale BVReturn order RECredit Memo G2Debit Memo L2Profor Invoice Order related F5Profro Invoice Delivery Related F8Inter Company IVInvoice cancellation S1Returns & Credit Memo invoice cancellation S2
OR, CI, RO is delivery related billing.
RK, CS, RE, CR, DR, CONR is order related billing.
If you maintain here while creating invoice system will determine by default
Billing Block
If you maintain billing block here the order is blocked for billing, the authorized person will cross check and release the billing block, then only system will allow to create billing document.
Normally in standard the below documents will have billing blocks
RE, CONR, CR, DR, RK.
For above five documents in real time authorization person has to release the billing block.
Condition type line items
We have two cost condition types i.e. EK01 &EK02.
We use EK01 if the selling price of the product is totally dependent on cost of the product.
EX: - X — 50,000/-
Selling Price 150 % of cost price.
We use EK02 if cost of the product is statistical which doesn’t have any effect on selling price.
Billing planned type
We have two types of billing plans.
Periodic Billing
When the billing is planned is for periodic i.e. on regular interval.
Ex – Monthly billing.
Milestone billing
When the billing is based on work done. These billings are activity based billing.
Ex – Road Contract, Building construction, Irrigation projects.
In periodic billing we use this for rental contracts and service projects.
Lead time in days
If you maintain lead time days here it overrides the replenishment lead time in material master while performing delivery scheduling.
Systems give first preference to lead time then RLT.
Proposed Delivery Date
If you check this system proposed today’s date as requested delivery date in sales document.
Proposed P.O. Date
If you check this system proposed today’s date as P.O. date in sales document.
ITEM CATEGORY CONTROLS
Item category controls the line item data of the sales document.
The T-code to define item category – VOV7
Path to define ITEM CATEGORIES
SPRO – S&D—SALES – SALES DOCUMETNS – SALES DOCUMENT ITEM – DEFINE ITEM CATEGORIES
Sr.No Document Type ITEM Categories1 IN AFN2 QT AGN3 OR TAN4 RO TAN5 CS BVN6 RE REN7 RK G2N8 CR G2N9 DR L2N
10 CF KBN11 CI KEN12 CONR KRN13 CP KAN14 WK1 WKN15 WK2 WKN16 SDF KLN17 FD KLN18 QC KMN19 DS LPN20 THIRD PARTY TAS21 MTO PROCESS TAK22 IPO PROCESS TAB23 TEXT ITEM TATX
24 STO PROCESS NLN25 STO RETURNS NLRN26 INTER COMPANY STO NLC27 INTERCOMPANY STO RETURNS NCRN
Other special Item categories
Free Goods – TANN
Bill of materials:
Header pricing main item TAQ & Sub item TAE
Main item Computer – TAQ
Mouse – TAE
Key board – TAE
Monitor— TAE
CPU – TAE
Item pricing main item TAP & Sub item TAN
Main item Computer – TAP
Mouse – TAN
Key board – TAN
Monitor— TAN
CPU – TAN
Material determination
Header Pricing main item – TAX
Header Pricing sub item – TAPS
Item Pricing main item – TAPA
Item Pricing sub item – TAN
ITEM CATEGORY CONTROLS
Business data
Item type:
This field specifies whether the material is standard item, text item, value item, and packing item.
Standard Item (BLANK)
It is the item we sell to the customer,
Text item:
It is the item consists of some information and which we deliver to customer but which we never sell.
Ex: broachers, user manual etc.
Value Item:
It is the item which consists of some value but we never sell the goods to customer.
Business Item:
The table for business data VBKD
The business data is a data which copies from into sales document from sales, shipping, billing from customer master.
This field control whether to the item data at item level or not.
If we check this then system will allow to change the data from item level, if you uncheck this system will not allow to change the business data from item level.
Completion Rule
This field controls when the status of the line item should be completed.
INQUIRY (IN) AFN
Completion Rule (A): Item is completed with first reference
If you refer the line item once irrespective of quantity the status of line item will show completed.
QUATION (QT) AGN
Completion Rule (B): Item is completed after fully quantity has been referred
If you referred the total quotation quantity then only system will show the line item status is completed.
Quantity contract (KMN)
Completion Rule (C): Item is completed after target quantity is fully referred.
If you refer the total target quantity then only system will show the status of line item is completed.
Value Contract (WKN)
Completion Rule (E): Item is completed after target value is fully referred.
If we refer the total target value then only system will show the status if line item is completed.
Completion rule is applicable only between sales documents to sales documents only.
I.e. if the target document is also sales document then only it is applicable delivery it is not applicable.
That is the reason it is applicable only in TAN.
Schedule Line allowed:
If you check this then only schedule line tab will be determined into sales document item.
If you uncheck this then schedule line tab will not be determined into sales document.
The below item category schedule line is uncheck.
KMN, G2N, L2N, WKN.
Any item category of schedule line allowed is unchecked then system will consider as target quantity.
If schedule line allowed is checked then system will consider as order quantity.
Special Stock Indicator:
We have two special stock indicators
1. Sales order stock indicator – E2. Consignment stock indicator – W
The below item category will have indicator E
Make to order – TAK E
Individual purchase order— TAB
The below item categories will have indicator W
Consignment issue KEN W
Consignment Returns KRN
MAKE TO ORDER (TAK)
MRP Controller
TOR
In make to order when we manufactures the goods the stock will be reserved for that particular sales order only.
When we delivery make to order process system will consider that particular sales order stock only.
The control is special stock indicator E
INDIVIDUAL PURCHASE ORDER (TAB)
TOR
In IPO process when we do MIGO that stock will be reserved for that particular sales order stock only when we do delivery system will consider that particular sales order stock.
Consignment Issue (CI)
Customer
Company
Production
Finished product
Delivery
Customer
Company MRP Controller
PR
PO
Delivery
Vendor
MIGO
Consignment fills up (CF) Consignment Issue (CI)
Delivery KBN Delivery KEN (W)
Invoice Invoice
Consignment Returns (CONR) Consignment Pick up (CP)
Delivery KRN (W) Delivery KAN
Invoice
When we do delivery in consignment issue, then the stock will be reduced from consignment stock, then when we do delivery then system will consider only consignment stock only. When we do return delivery in consignment process stock will be added only consignment stock only.
Item relevant for delivery
This field is only applicable for text item and value items.
If the text item and value item is relevant for delivery then we will check this field.
Billing Relevance
This field controls whether the item is relevant for billing or not, it is control that it is order related billing or delivery related billing
‘–‘Blank it is not relevant for billing
AGN,AFN,KBN,KAN,WKN,KMN,KLN,TAE,TAPA,TAPS(These all items are not relevant for billing)
‘A’ – TAN, KEN, LPN, TAB, TAK, TAQ, TAX, TANN (These all item categories are delivery related billing)
‘B’ – BVN, REN, KRN (These all items categories are order related billing)
‘C’ – G2N, L2N (These all items categories are order related billing according to the target quantity)
If scheduling line is unchecked then we consider as target quantity
‘D’ – Relevant for Performa invoice
It item category is not relevant for billing if you want to create Performa invoice then maintained billing relevance as ‘D’
KLN, KBN we maintained billing relevance as ‘D’
‘F’ – Order related billing status according to invoice quantity (vendor invoice MIRO)
TAS – we maintained as F
Third party without shipping notification
Invoice
Billing relevance F, TAS
Billing relevance “F” checks that while creating third party billing system checks that MIRO is created or not ,if MIRO is created then only system will allow to create invoice to the customer.
Third party with shipping notification
Company
Customer
P.R
P.O
Vendor
MIRO
Company
P.R
MIGO
Invoice
Billing relevance ‘G’, TAS
Billing relevance ‘G’ checks that while creating third party with shipping notification billing process system checks that MIGO is created or not, without MIGO system will not allow to create invoice to customer.
‘K’ Delivery related billing with partial quantity.
RETURNS
The below item categories will have returns check
REN – H
KRN – H
KAN – H
G2N – K
If you check the returns system identifies that goods are coming back.
System generally revenue account debit to customer account credit.
If any sales document is H&K and its item category is REN, KRN, KAN and G2N then we should have return check.
NOTE: for text material we don’t create material code we will write description in sales order and do the delivery
Q) My document value is showing negative what could be the reason?
A) Check whether your item category returns is check or uncheck.
Q) When I am doing normal process system is generating as revenue account debit to cost of goods credit?
A) Uncheck the item category returns.
Customer
P.O
Vendor
Billing plan type:
If you maintain billing type here then it will be applicable for particular line item in the sales document
Billing Block:
If you maintain here it will be applicable for particular line item in the sales document.
Weight &Volume Relevant:
If you check this system will calculate the weight and determines it into sales document line item.
Credit active
This field controls whether to update the line item value in credit management or not.
If we check this then only the line item value will be updated in credit management
If you uncheck this it will not be updated in credit management.
The below item categories will have credit check.
TAN, LPN, L2N, KEN, TAS, TAB, TAK, TAQ, TAX.
The below item categories will have credit check uncheck.
AFN,AGN,G2N,REN,BVN,KLN,WKN,KMN,TANN,KBN,KRN,KAN,TAE,TAP,TAPS,TAPA.
Determine Cost
This field is perquisite to determine the VPRS condition type into sales document.If you check this then only VPRS condition type will be determined into sales document.
PRICING
This field controls whether the item is relevant for pricing or not. It also controls whether the item is relevant for normal pricing or free goods pricing.
The below item categories are relevant for pricing (X – standard pricing)
AFN,AGN,TAN,BVN,REN,G2N,L2N,KMN,WKN,KEN,KRN,TAS,TAB,TAK,TAQ,TAX,LPN.
The below item categories are not relevant for pricing (-- blank)
KBN, KLN, KAN, TATX, TAPS, TAPA, TAE, TAP.
The below item categories “B” 100% Discount.
TANN.
Any item category if pricing field is ‘X’ then system will determine the prices in sales document pricing.
Any item category if pricing field is ‘—‘blank then system will not determine the prices in to sales document
Any item category if pricing field is ‘B’ then system will be determined the prices in sales document but R100 condition type determines and make the value is ‘0’ZERO.
STATISTICAL VALUE
If we maintain statistical then line item pricing become inactive and it does not have any effect on total document value
General Control
Automatic batch determination:
If we check this system will determine the batch number automatically in sales order
Rounding permitted:
If we check this and the sales order quantity is in decimals then system will round of the quantity decimals nearby number.
Order quantity =1
If you check this system will restrict each line item quantity to one only.
Transaction Flow
Status Profile
If you maintain this system will block the item at item level. And the authorization person has to release the order.
Create P.O.automatic
In third party &IPO process while creating sales order system generates purchase requisition but if you want to create automatic P.O. then we have to check automatic P.O. along with ALE data in sales organization.
We use this only for TAS & TAB only.
Bill of material Configuration
Structure scope
This field controls whether to explore BOM or not, and it also controls whether to control single level BOM or Multi level BOM.
If we want to explore single level BOM maintain ‘A’
If we want to explore multi level BOM maintain ‘B’
We maintain structure scope TAQ & TAP only
Value Contract Material
This field is used only for value contract general item category, because value contract general is not specific for one material, it is a group of materials, and while creating value contract general document we will enter assortment module.
Assortment module consists of group of materials, without any specific material we cannot create document so we pass dummy material from this field to value contract general document.
Contract Release Control
This field controls how system should response, if the release order value exceeds contract value.
I.e. whether to give warning message, error message, no message.
ITEM CATAGORY DETERMINATION
The item category determination based on the below combination
1. Sales document type. 2. Item category group (in material master – sales org -2 we maintained item category )
STANDARD – NORMBOM – ERLA/LUMFTHIRD PARTY – BANSIPO – BANCMTO – 0001
3. Item usage Free goods – FREECross selling – CSELMaterial determination header pricing Header Item – PSHPSub Item – PSELMaterial determination Item pricing Header item – PSA1Sub item – PSA2
4. Higher Level item category (Default item category)
T-Code for item category determination (VOV4) Path
SPRO – SALES &DISTRIBUTION – SALES – SALES DOCUMENT—SALES DOCUMENT ITEM—ASSIGN ITEM CATEGORIES
Sales document typeItem category determination based on sales document type.
ITEM CATEGORY GROUP:
Item category determination only based on item category group (or material group)
We consider item category group, if we want to determine different item category for the same document typeWe use item category group if we want to differentiate the item category material wise.We have item category group in material master sale org – 2
Q. Client requirement is any customer if he purchases slow moving item then system should not update the line item values into credit management. Solution1. Copy the TAN and create new one GTAN and uncheck credit activity.2. Create new item category group go to VOV4 and create new one (COPY NORM AND CREATE
GORM)3. Go to slow moving item material master and maintain item category group as GORM4. In item category determination assign item category
GTAN TO GORMOR+GORM+ -- + -- + GTAN.
Item category determination based on higher level item category
System consider high level item category whenever it is determining item category for sub item.
Manual free goods determination
X TAN
Y
OR OR
NORM NORM
-- --
TAN --
TANN TAN
BOM Header pricing
X TAQ
Y
OR OR
NORM ERLA
-- --
TAQ --
TAE TAQ
BOM Item pricing
X TAP
Y
OR OR
NORM LUMF
-- --
TAP --
TAN TAP
Multi level BOM header pricing
Computer TAQ
CPU
Hard disk
OR OR OR
NORM NORM ERLA
-- -- --
TAE TAQ --
TAE TAE TAQ
Multi level BOM Item pricing
Computer TAP
CPU
Hard disk
OR OR OR
NORM NORM LUMF
-- -- --
TAE TAP --
TAN TAN TAP
Item category determination based on item usage
System considers item usage whenever sub item is automatically determine into the sales document other than BOM
Automatic free goods – FREE
Cross selling – CSEL
Material determination
Header item -- PSHP
Sub item -- PSEL
Item Pricing
Header item -- PSA1
Sub item -- PSA2
System consider the item usage if you want to determine different item category with the same combination of document type and item category group.
Material determination header pricing header item systems consider usage.
X
Y
OR OR
NORM NORM
PSEL PSHP
TAX --
TAPS TAX
Material determination Item pricing header item systems consider usage.
X
Y
OR OR
NORM NORM
PSA1 PSA1
TAPA --
TAN TAPA
Automatic Free goods
X
Y
OR OR
NORM NORM
FREE --
TAN --
TANN TAN
CROSS SELLING
X
Y
OR OR
NORM NORM
CSEL --
TAN --
TAN TAN
System considers item usage automatically.
Item usage can be controlled manually at one place i.e.at CMIR.
Q. Client Requirement is if customer purchase slow moving items the system should not update the value into credit management?
Solution
1. Copy TAN to YTAN (Uncheck credit limit in YTAN)
2. Create new item usage Y100
3. Go to CMIR and maintain item usage Y100
(How to maintain item usage: Go VD51 – select line and click on details – below their you find ITEM USAGE and there you maintain item usage)
Cust 1 Cust2 Cust3
X X X
Y (Y100) Y (Y100) Y (Y100)
Z Z Z
4. Item category determination
OR+NORM+Y100+ --- + YTAN
PATH FOR CREATING NEW ITEM CATEGORY USAGES
SPRO – SALES &DISTRIBUTION – SALES – SALES DOCUMENT— SALES DOCUMENT ITEM—DEFINE ITEM CATEGORY USUAGE
Note
In item category determination we have 11 manual item categories are there. The manually item category will help to change the item category in sales document.
SCHEDULE LINES CATEGORIES
Schedule line data is a data which consists of delivery dates and confirmed quantities.
Schedule line data will be controlled schedule line category
The table for schedule line is VBEP (T-CODE VOV6)
PATH FOR SCHEDULE LINE CATEGORIES
SPRO – SALES &DISTRIBUTION – SALES – SALES DOCUMENT— SCHEDULE LINES – DEFINE SCHEDULE LINE CATEGORIES.
For KMN, WKN, G2N, L2N no schedulines because in these case there is no movement type and no scheduline tab in this case.
SCHEDULE LINES CATEGORY CONTROLS
BUSINESS DATA
Delivery Block:
If you maintain delivery blocks here then it will applicable particular schedule line item
Movement type
Every physically movement of goods required movement type information.
System considers movement type while doing PGI or PGR or delivery document
Movement types controls
1. Inventory accounting document generates.2. Stock up gradation
1. Standard process
Movement type – 601
Schedule line category CP
Effect of 601
Stock will be reduced from unrestricted stocks,
Inventory accounting document generates
COST OF GOODS SOLD ACCOUNT DEBIT TO INVENTORY ACCOUNT CREDIT
2. Reverse PGI (T-Code VL09)
MOVEMENT TYPE 602
Effect of 602
Stock will be added to unrestricted stocks.
Inventory accounting document generates and accounting entry is
ORDER
DELIVERY
INVOICE
PGI or PGRMOVEMENT TYPES GENERATES
Inventory account debit to cost of goods sold credit
3. Scheduline category Movement type: 651Return : DNHere customer returns the goods to us, when goods are damaged
Effect of 651
Stock will be added to return stocks.
Inventory accounting document will not be generated (return stocks are a temporary stock)
4. Scheduline category Movement type: 653 Scheduline category type DNThe customer returns the goods to us if he returns over delivery stock.Effect of 653
Stock will be added to unrestricted stocks
Inventory accounting document is generated and the accounting entry is
Inventory account debit to cost of goods sold credit
5. Scheduline category
Movement type: 655
Scheduline category type DN
The customer returns the goods to us if there is any defective in the goods.
Effect of 655
Stock will be added to quality inspection stocks
Inventory accounting document is generated and the accounting entry is
Inventory account debit to cost of goods sold credit
6. Scheduline category
Movement type: 657
Scheduline category type DN
The customer returns the goods to us if there is any expired stock.
Effect of 657
Stock will be added to blocked stock.
Inventory accounting document is generated and the accounting entry is
Inventory account debit to cost of goods sold credit
Scheduline category E1
Movement type: 631
Scheduline category type E1
Effect of 631
Stock will be reduced from unrestricted stock and Stock will be added to consignment stock.
Inventory accounting document is not generated .because we are not hand overing the ownership to customer.
Scheduline category C1
Movement type: 633
Scheduline category type C1
Effect of 633
Stock will be reduced from consignment stock .Inventory accounting document is generated.
Accounting entry is cost goods sold debit to inventory account debit.
Scheduline category D0
Movement type: 634
Scheduline category type D0
Effect of 634
Stock will be added to consignment stock .Inventory accounting document is generated.
Accounting entry is cost goods sold credit to inventory account credit.
Scheduline category F1
Movement type: 632
Scheduline category type F1
Effect of 632
Stock will be reduced to consignment stock and stock will be added to unresticed.
Inventory accounting document is not generated.
Scheduline category NN
Movement type: 641(TWO STEP PROCESS)
STOCK TRANSFER PROCESS
Scheduline category type NN
Effect of 641
If we do delivery in two step process the Stock will be reduced from supplying plant and stock will be displayed as stock in transit in receiving plant.
Inventory accounting document is generated and the accounting entry is
Stock inward movement debit stock outward movement credit
DELIVERY WITH REFERENCE WITH PO
Scheduline category NN
Supplying plant
Receiving plant Stock in transit
MIGO
Movement type: 647(ONE STEP PROCESS)
STOCK TRANSFER PROCESS
Scheduline category type NN
Effect of 647
If we do delivery in one step process the Stock will be reduced from supplying plant and stock will be added to receiving plant.
Inventory accounting document is generated and the accounting entry is
Stock inward movement debit stock outward movement credit
DELIVERY WITH REFERENCE WITH PO
Scheduline category NR (STOCK RETURN PROCESS)
Movement type: 671(TWO STEP PROCESS)
Movement type: 677(ONE STEP PROCESS)
Scheduline category NE (INTE COMPANY STO)
Movement type: 643(TWO STEP PROCESS)
Movement type: 645(ONE STEP PROCESS)
Scheduline category NC (INTE COMPANY STO RETURNS)
Supplying plant
Receiving plant
Movement type: 672(TWO STEP PROCESS)
Movement type: 675(ONE STEP PROCESS)
Item relevant for delivery
This field controls whether the item is delivery or not.
We have similar field in item category controls also but that one is only for text item and value item.
If standard item is relevant for delivery we should this check.
Any item we want to determine into delivery document and if you do not to reduce the stock. Then check the item relevant for delivery and remove the movement type.
ORDER TYPE (NB)
We use this field only for 3rd party & IPO process (CS&CB)
This field will help to generate the purchase requisition automatically in the background. While creating sales order in 3rd or IPO process.
NB — Purchase requisition (Standard)
Item category
This field we use only for 3rd party and IPO process, for 3rd process we maintain item category as ‘5’ for ipo process we maintain ‘0’
Like sales document MM document will also have item category.
While creating purchase requisition manually the user will enter the item category manually.
But in 3rd party & IPO process we are creating purchase requisition automatically. So we passing the item category information from scheduline category to purchase requisition
Use of Item category (5)
It controls that even if you do MIGO in third party process system will consider as dummy MIGO and stock will not be updated.
For IPO (CB) process we maintain item category as ‘0’
It controls that we do MIGO in IPO process system will consider as actual MIGO and stock will updated.
Account assignment category
This field will be used only for 3rd party &IPO process.
In 3rd party (CS) we maintain it as (1)
In IPO process (CB) we maintain it as (E)
Account assignment category controls whether to generate inventory accounting document at the time of MIGO or PGI
Purchase requisition with delivery scheduling
We use this field only for IPO (CB)
If we check this field then system will send the delivery date information and confirmed quantities information’s from sales order to purchase requisition.
Transfer of requirements / Begin assembly order from SD
This field is one for the perquisite to transfer the sales order requirement to MRP
CP – check & CN – uncheck
The basic difference between for CP&CN
CP— requirement /assembly &Availability is check
CN— requirement /assembly &Availability is uncheck
SCHEDULE LINE CATEGORY DETERMINATION (VOV5)
TAN+PD = CP
TAN+ND=CN
We have a manually schedule line category and this will help to change the a schedule line category manually in sales document
In item category determination we have 11 manually item categories. The manually item category will help to change the item category in sales document.
In scheduline determination system will first checks with
1. Item category +MRP = scheduline 2. Item category +NO MRP = Scheduline
DELIVERY TYPES
Schedule line category determination = item category +MRP type
The structure of delivery document will be divided in two parts. (0VLK)
Path for defining delivery types.
SPRO – LOGISTIC EXCUTION – SHIPPING –DELIVERIES – DEFINE DELIVERY TYPES
Standard delivery type – LF
Return order delivery type – LR
Cash sale delivery type - BV
Delivery Without order reference – LO
STO delivery type – NL
STO return type –NLR
Intercompany STO – NLCC
Intercompany STO returns – NCR
Delivery document controls
Document category
The document category controls the functioning of the document
Document category for ‘LF’ is ‘J’
Document category for ‘LR’ is ‘T’
NUMBER SYSTEM
HEADER DATA (LIKP)
ITEM DATA (LIPS)
Q. While doing return delivery how system is proposing PGR. Where is the control?
A. Delivery document category – T
Internal number range &External Number range
In delivery document we have option internal number range and external number range
Path for number range
SPRO – LOGISTIC EXCUTION – SHIPPING – DELIVERIES-DEFINE NUMBER RANGES FOR DELIVERIES
Item number increment
This filed controls how the line item number incremented in delivery document
ORDER REFRENCE
Order required
This field controls wheather any preceding document is required or not
LF – X SALES ORDER IS REQIRED
NL, NLR, NLCC, NCR – B PURCHASE ORDER IS REQUIRED LO – NO PRECEDING DOCUMENT IS REQUIRED
Default order type (DL)
System consider default order type DL when order not sales order required (LO, NL, NLR, NLCC, NCR)
System considers default order type DL to determine movement type
Q. While creating delivery without order reference how systems determine movement type?
A. Default order type (DL)
Item Requirement
This field controls whether to add new line item in delivery document or not.
If you want to add new line item then maintain requirement as 202,
If you want to restrict new line item then maintain requirement as 201.
Storage location
Storage location rule will help to determine storage location in delivery document.
We have three types of storage location rules
1. MALA2. RETA3. MARE
1. MALA rules says that storage location should be determined based on shipping point/plant/storage condition
2. RETA rule says that storage location should be determined based on plant/situation/storage condition
3. MARE rules says that first checks mala configuration if not then checks reta configuration
Delivery Item category (0VLP)
STO Delivery item category – NLN
STO return delivery item category – NLRN
Intercompany STO delivery item category – NLC
Intercompany STO return delivery item category – NLRN
Material number zero allowed
This field controls whether to allow creating delivery document without material code.
We create delivery without material code only for text items.
Item category statistic group
This field controls whether to update customer sales data into LIS or NOT
Check quantity 0
This field controls how system should response if the quantity in delivery document in zero, that in whether to give error message or warring message or no message.
Check minimum quantity
This field controls how system should respond if the delivery quantity is less than the minimum order quantity. Maintained in material master (sales org -1).i.e. whether to give warning message or error message or no message.
Check over delivery quantity
This field should controls how system respond if the user is increasing delivery quantity is more than the sales order qty. i.e. whether to give error message or warring message or no message.
If you check in customer master (shipping – unlimited tolerance) then this concept will not work
This field will have relationship with over delivery tolerance in customer master.
If you maintain over delivery tolerance % then system will allow increase the quantities in delivery document up to that much percentage. If it exceeds it will warning message or error message or no message.
Availability check off
This filed controls whether to perform availability check or not while creating delivery document.
The below scenarios we have to perform availability check in delivery document.
1. Delivery document with reference to sales order document.2. Increasing the quantity in delivery document.3. Adding new line item in delivery document.
Warehouse Control and Picking1. Relevant for packing :
This field controls whether the item is relevant for picking or not,In standard BVN, KRN, KAN, REN are not relevant for picking.
2. Determine Storage location If we check this and if we maintain storage location rule than system automatically determines storage location in delivery document.
3. Packing controlThis field whether the material must be packed or can be packed or cannot packed.
DELIVERY ITEM CATEGORY DETERMINATION (T-CODE 0184)
In normal scenarios system will copy the item category as it is from order to delivery but some scenarios system will determine newly in delivery document
1. Delivery without order reference.
Delivery type : LO
Item category group : NORM
Item usage : --
Item cat higher level usage: -
Default item category : DLN
2. Adding new line item in delivery
LF + NORM+ - + - = DLN
3. Stock transfer order
NL + NORM+ V + - = NLN (Any delivery create with reference to PO then item category ‘V’)
4. Return Stock transfer order
NL R+ NORM+ V + - = NLRN (Any delivery create with reference to PO then item category ‘V’)
5. Stock transfer order Inter Company
NL CC+ NORM+ V + - = NLC (Any delivery create with reference to PO then item category ‘V’)
6. Stock transfer order Inter Company Returns
NCR+ NORM+ V + - = NCRN (Any delivery create with reference to PO then item category ‘V’)
7. BATCH SPLIT
System will do batch split if the delivery qty is not available in single batch, then we do batch usage.
The item usage is CSHP
LF + NORM+ CSHP + - = TAN
BILLING TYPES
Structure of billing document is divided into two parts
HEADER DATA: VBRK
ITEM DATA : VBRP
STANDARD BILLING TYPES
1. Standard billing type - F22. Return order billing type - RE3. Cash sale - BV4. Credit memo - G25. Debit memo - L26. Intercompany - IV7. Perform invoice order related - F58. Perform invoice delivery related - F89. Invoice cancelation - S1 10. Return order invoice cancelation – S2
HEADER DATA (VBRK)
ITEM DATA (VBRP)
Path for billing document types
SPRO – SALES AND DISTRIBUTION – SALES – BILLING – BILLING DOCUMENT – DEFINE BILLING DOCUMENT TYPES. (VOFA)
Perform invoice is dummy invoice for which there is no accounting document will not be generated.
Number Range internal assignment:
In billing document sap has not given provision for external number range. Because it is a legal requirement than invoice number should be always in a sequence.
Sales document category
This field controls the functioning for the billing document.
F2 – “M” customer account debit to revenue account credit
RE, G2 – “O” revenue account debit to customer account credit
F5, F8 - “U” No accounting document generates
Where the control that system will not is generates accounting document?
Billing document category “U”
Posting Block
If you check this system will not generate accounting document while creating invoice.
The user has to post manually, the T-CODE to release the billing document into accounting collectively VFX3
Statistical
This field controls whether to update the billing document data into LIS or not
Document type
The standard document for accounting document is RV
Negative posting
This field controls whether to allow posting negative invoice values into accounting or not.
Invoice list type
The t-code to create invoice list is VF21 or VF24,
The invoice list type is LR
Relevant for rebate
This field is one of the prerequisite to process rebate
The prerequisite for rebate is
1. Check rebate proactive in sales org 2. Check rebate in customer master 3. Check relevant for rebate in billing type
CANCELATION
Cancellation Billing Type
The cancelation billing type for invoice is S1,
The cancelation billing type for returns or credit memo is S2
Account assignment for pricing
Account determination procedure
The standard account determination procedure KOF100
Account determination procedure will help to determine revenue G/L accounts while posting invoice values into accounting.
Whenever we create invoice in the back ground system generates accounting document and the accounting entry is customer account debit to revenue account credit.
For customer a/c system determines G/L account from reconciliation account.
For revenue account system determines G/L account from account determination procedure.
Document pricing procedure.
This field is one of the parameter to determine the pricing procedure to billing document.
Normally when we create invoice the pricing procedure will be copied from sales order but the below scenarios pricing procedure will be redetermined in invoice.
1. Delivery without order reference 2. STO Performa invoice 3. Intercompany invoice
Account determination reconciliation account
If the client requirement is while creating invoice reconciliation account should not be determined from customer master .it should be determined based on some other combinations like plant and division.
Then we will go for account determination reconciliation account. System gives first preference to this fields.
Account determination in cash settlement
This will be used for only cash sales ‘BV’ billing type. When we create cash sales invoice the accounting entry is
Cash settlement a/c debit to Revenue a/c credit.
For cash settlement account system determines G/L based on account determination cash settlement procedure.
The standard procedure for cash settlement is KOFIAC
The standard procedure for reconciliation account is KOFIAB SPLIT CRITERIA FOR DELIVERIES
1. SHIPPING POINT 2. SHIP TO PARTY3. INCOTERMS4. DELIVERY DATE5. ROUTE
SPLIT CRITERIA FOR INVOICE
1. PAYMENT TERMS2. PAYERS3. BILLING DATES
THE ACTIVITIES SYSTEM PERFORMS WHEN WE CREATE SALES ORDER
1. PARTNER DETERMINATION2. LISTING/EXCULSION3. MATERIAL DETERMIANTION 4. FREE GOODS 5. DELIVERY SCHEDULING6. AVALIBITY CHECK 7. PRICING 8. CREDIT MANAGEMENT 9. TEXT DETERMINATION10. OUTPUT DETERMIANTION11. TRANSFER OF REQUIRMENT
The system perform when we do PGI
1. Stock updates 2. Inventory accounting document generates
I.e. cost of goods sold a/c debit to inventory a/c credit3. It updates document flow4. It updates in LIS5. It updates in credit management 6. It updates in billing due list
The system performs activities when we create invoice
1. Accounting entry generatesI.e. customer account debit to revenue account credit
2. Profitability analysis document generates.
3. Cost center document generates.
4. It updates in document flow.
5. It updates in credit management
6. It updates in LIS
Restricting No. Of line items in invoice
PATH
SPRO - SALES&DISTRIBUTION - BILLING – BILLING DOCUMENT – COUNTRY SPECIFIC FEATURES –MAINTAIN MAX NO .OF BILLING ITEMS.
PRICING
Pricing is based on condition techniques
Condition techniques
It is a process of determining pricing condition records into sales document.
1. Condition Techniques consists of condition records.2. Condition records will be stores in condition tables.3. Condition tables will be placed in access sequence in most specific to most general.4. Access sequence is assigned to condition types.
5. Condition types will be placed on pricing procedure.
Condition Records
Condition records are the master data for pricing; we also call it as condition master (VK11)
Condition Tables (V/03)
Condition tables consist of fields and which will help to store the condition master data.
Customer/Material Most specific
Price list /Material
Material
Most general
Access Sequence:
Access sequence is a search strategy which will search for the valid condition records from most specific to most generally.
Exclusive 12 /Tee shirts (9000/-)
Customer /Material
13/Tee shirts (9000/-)
G1 /Tee shirts - 9800/-
Price list /Material G2/Tee shirts - 9600/-
G3/Tee shirts – 9400/-
G1 (Dealers)/14 – 10000/-
Material G2 (Distributors)/15 -10000/-
G3 (Institutions) /16 – 10000/-
Exclusive check box in accesses sequence
We have this check box in access sequence, if you check this and if the system finds the valid condition records at any of the combination. Then system will come out of the search strategy and determine the price into sales document.
If we uncheck exclusive even if system finds the valid condition record at any of the combination system will not come out the search strategy and system will go and search all the combinations and it will activate last one and deactivated previous one.
T-code to create access sequence V/07.
Condition types
Condition type controls the price components or price elements.
Total price components are base price, discounts, surcharges, excise, tax and rebates
Base value + discounts = Gross value
Gross value +Surcharges = Net value
Net value + Tax = Final price
T-code to create condition types V/06.
Pricing Procedure
Pricing procedure is a procedure which consists of list of condition types which are placed in a sequence.
T-code for pricing procedure V/08
Common T-Code for pricing is VOK0
Pricing procedure determination:
Pricing procedure determine based on Sales area + Document pricing procedure + Customer pricing procedure.
T-Code for pricing procedure determination OVKK
CONFIGURATION FOR BASE PRICE
1. DEFINE CONDITION TABELS (V/03)
PATH
SPRO- SALES AND DISTRIBUTION BASIC FUNCTIONS – PRICING –PRICE CONTROL- DEFINE CONDITION TABELS - CREATE CONDITON TABELS
Condition tables are 3 digits number.
The user defined condition table should be above 500.
SAP standard condition tables are 500and it’s below.
Field catalog
Field catalog consists of allowed field to create condition tables.
Go to field catalog and double click on the field.
After selecting the field click on generate.
If we save condition table in local object then system will not generate request number.
Without request number we cannot transport the condition table from one server to another server
So, we have to save condition table in packages, then system will generates request number,
A package will be provided by basis consultancy.
A package consists of group of enhancement.
In SD module condition table and access sequence will be stored in work bench request
All work bench request are cross clients, cross clients means we do configuration in one server it will updates the server.
Cross clients are also called client independent
If we save condition table in package then only system generates request number.
The name of the condition table starts with ‘A’ and then with number.
Q. if we have mistakenly saved condition table in local object then how to retrieve it back into request number?
A. go to change mode of condition table – main menu – go to – object directory – maintain package – save it
Q.if the field is not available infield catalog as consultant, what will you do?
A. we add the field in allowed fields
2. Defining Access sequence (V/07)
PATH
SPRO- SALES AND DISTRIBUTION- BASIC FUNCTIONS –PRICING-PRICING CONTROL-DEFINE ACCESS SEQUENCE- MAINTAIN ACCESS SEQUENCE.
Access sequence is also cross client i.e. if we create access sequence in one client it automatically updates in other server.
Access sequence is also be stored in workbench request.
GO V/07 – NEW ENTRIES – MENTION SOME ACCESSECE SEQUENCE (GROO) – SELECT ACCESSES SEQUENCE AND DOUBLE CLICK ON ACCESS – CLICK ON NEW ENTRIES – ENTR YOUR TABEL – SELECET TABEL LINE ITEM – CLICK ON FIELDS – AND SAVE IT.
3 Define Condition type (V/06)
PATH
SPRO- SALES AND DISTRIBUTION- BASIC FUNCTIONS –PRICING-PRICING CONTROL-DEFINE CONDITION TYPE- DOUBLE CLICK ON MAINTAIN CONDITION TYPE.
The standard price condition type is PR00
Select the standard price condition type and copy create new condition type (GR00) and assigned your access sequence (GR00).
4. Define and Assign pricing procedure(V/08)
PATH
SPRO- SALES AND DISTRIBUTION- BASIC FUNCTIONS –PRICING-PRICING CONTROL-DEFINE & ASSIGN PRICING PROCEDURE – MAINTAIN PRICING PROCEDURE.
Standard Pricing Procedure RVAA01 copy this one and create new pricing procedure GVAA02 save it.
Then select your pricing procedure and double click on control data. Then go to new entries
Step Condition Type Requirement Account Key10 GR00 2 ERL
Save it.
5. Determine pricing procedure determination(OVKK) Go to OVKK and position and select your sales area + document pricing procedure+ customer pricing procedure and assigned your pricing procedure and condition type.
S.org Distr Division Doc.Pric.pro Cos.pric.pro Pric Pro Con.TypeG100 G1 G1 A 1 GVAA02 GR00
Q. Why we assign condition type in OVKK? OR why we are assigned condition type in pricing procedure determination?
A. if we assign condition type in OVKK then it will display the amount of condition type in line item overview.
We can also change the amount if condition type line item overview
MATIN THE CONDITION RECORDS (VK11)
Go to VK11 and select customer/material combination then enter
Mention customer number and material and give price (10000/-) save it.
Then go back and select price list /material combination then enter
Mention price list (G1) and material (TEE SHIRTS) and give the price (9800/-)
Go back and mention price list (G2) and material (TEE SHIRTS) and give the price (9600/-)
Go back and mention price list (G3) and material (TEE SHIRTS) and give the price (9400/-)
Then go back and select material combination
Tee shirts – 10000/-
DEFINE PRICE LIST
SPRO – SALES&DISTRIBUTION – BASIC FUNCTIONS- PRICING- MAINTIAN PRICE RELEVENT MASTER DATA FIELDS – DEFINE PRICE LIST CATEGORIES FOR CUSTOMERS.
DISCOUNTS
A discount is a deduction which we deduct from customer base value
1. Material Discounts
A discount gives to specific material is known as material discount.
The discount is in quantity based not in percentage based.
The standard condition type material discount is K004.
2. Customer /Material discount
This discount is given for a specific customer for a specific material is known as customer /material discount.
This discount is quantity based not percentage based.
The standard condition type for customer /material discount is K005
3. Customer Discount
This discount is given to the specific customers irrespective of any material is known as customer discount.
This discount is percentage based
The standard condition type for customer discount is K007
4. Price group discount (K020)
This discount is percentage discount.
5. Price group/Material Discount (K032)
This discount is percentage quantity based
As per above scenario we have to create three condition tables (actual we need to create 5 but already we create 2)
Condition type Table1 Material discount Quantity Based G004 7022 Customer /Material Discount Quantity Based G005 7003 Customer Group Percentage Based G007 7034 Price Group Percentage Based G020 7045 Price Group/Material Discount Quantity Based G032 7056 Material Group Quantity Based G029 1. Create tables (703,704,705)2. Create access sequence (G004,G005,G007,G020,G029)3. Create Condition type (G004,G005,G007,G020,G029)4. Assigned the pricing procedure
Go to V/08 and select your pricing procedure GVAA02 and double click on control
Step Condition Type Description From To Man Statis Requ Account Key10 GR00 2 ERL20 Base value 10 30 G004 Material 20 2 ERS
40 G005 Customer/Material 20 2 ERS50 G007 Customer Discount 20 2 ERS60 G020 Price Group 20 2 ERS70 G032 Price Group/Material 20 2 ERS80 Gross Value 20 70
5. Then go to VK11 and maintain condition records for Discount condition type (G004, G005, G007, G020, G032)
6. Then create Sales order and check price.
Configuration for Common discount
Placing the all discount condition table in on access sequence
In stated of SAP, SAP has given separated condition type for the discount conditions,
Ex: K004, K005, K007, K020, K032
In this case if customer is eligible for the all discount, then system will purpose all the discounts, which is loss to the company instated of the we can configure one discount type, one access sequence in which we placed the all the condition tables from most specific to most general.
Here either discount should be quantity based.
1. Create condition table (all ready is no need to create again) 2. Create new access sequence (G030 Common discount) and place the tables in this access
sequence.3. Select K007 and Create condition type G0304. Go to V/08 and select your pricing procedure and place your condition
For discount we should not check in exclusive check in access sequence.
HEADER DISCOUNT
Header discount is a discount which is applicable all the line items in the sales document.
All header discounts should not have any access sequence,
All the header condition should process manually only
HA00 – standard header percentage discount
HB00 – standard header fixed discount
1. Create condition type for Header discounts (V/06)
Go to V/06 – select HA00and create new one GA00
Again select HB00 and create new one GB00
2. Place the pricing procedure Go to V/08 and select your pricing procedure and click on controls, then go to new entries
Step Condition Type Description From to Man Statis Requ Account Key75 GA00 Percentage Discount 20 2 ERS76 GB00 Discount (Value) 20 2 ERS
In sale order go to header data to process header condition and maintain header discount manually then click on activate button then save it.
HB00 is a group condition as well as header condition
Check Header condition in condition type
Check Group condition in condition type
If you check group condition then the group condition amount will be distributed all the line items in the proportional to the value of line item.
If we uncheck group condition the condition type amount will be evenly proportionate to all the line items.
SURCHARGES
Surcharges are added to customer outstanding, surcharge is the amount which we added to customer.
Examples for surcharges:
Freight, Insurance, Packing Charges, Loading Charges.
1. FRIEGHT CHARGES KF00 INCOTERM 1 & INCOTERM 2
2. INSURANCE KFOO INCOTERM 1 & INCOTERM 2
3. PACKING KFOO MATERIAL
4. LOADING KFOO MATERIAL
As per above scenario we have to create 2 condition tables.
1. Create a condition table (V/03)
Inco term 1 & 2 706Inco term 1 707
Packing and insurance we can use condition table of material which we created earlier.
Material discount 702
2. Define access sequence (V/07)We have to create access sequence for fright.Standard access sequence is KF00.Ours is GF00
For packing and insurance we can use material access sequence which we have created before.
Material discount Quantity Based G004 702
3. Define condition type and assigned access sequence . (V/06)
Create your own condition type.
Standard condition type for freight is KF00, Copy the KF00 and create GF00
For Packing copy the K007 and create GPAC and assigned the access sequence G004 (Material) and maintain Plus/Minus (A- Positive)
For Insurance copy the K007 and create GINS and assigned the access sequence G004 (Material) and maintain Plus/Minus (A- Positive).
Then save it.
4. Assigned pricing procedure (V/08)Select your pricing procedure (GVAA02) and assigned surcharges condition types.
StepCondition
Type Description From To Man Statis Requ Account Key10 GR00 2 ERL20 Base value 10 30 G004 Material 20 2 ERS40 G005 Customer/Material 20 2 ERS50 G007 Customer Discount 20 2 ERS60 G020 Price Group 20 2 ERS70 G032 Price Group/Material 20 2 ERS75 GA00 Percentage Discount 20 2 ERS76 GB00 Discount (Value) 20 2 ERS80 Gross Value 20 70 90 GF00 Freight 80 2 ERF
100 GPAC Packing 80 2 EPC110 GINS Insurance 80 2 EIN
120 Net Value 80 110
We need to create account keys for Packing and Insurance.
Path for account keys.
SPRO- SALES AND DISTRIBUTION- BASIC FUNCTIONS- ACCOUNTING ASSIGNMENT AND COSTING-REVENUE ACCOUNT DETERMINATION-DEFINE AND ASSIGN ACCOUNT KEYS.
5. Maintain Condition Records (VK11)Go to VK11 and maintained the freight charges.GF00 – select key combination as INCO TERMS 1 and mention CIF (20/- KG)Save it.NOTE: freight will be calculated on weight based only.Then go back and maintained the price for packing and insurance charges.GPAC and maintained price then go back and GINC and maintained price.Packing and insurance is based on percentage based.
Header freight condition
This header freight condition is used as manually at the header level.
Standard header condition is HD00.
Define condition type
Go to V/06 and copy the HD00 and create your own condition type (GD00).
Here header condition is checked and group condition is unchecked.
Define pricing procedure
Go to V/08 and select your pricing procedure and assigned header freight condition.
UN check Header condition in condition type
Check Group condition in condition type
91 GD00 Header Freight 2 ERF
Header Order Value
This header value is used to change the total document value (total net value)
The standard header order value HM00.
Copy the standard one HM00 and create new one GM00
Check Header condition in condition type
Check Group condition in condition type
Assigned GM00 condition type in your pricing procedure.
92 GM00 Order Value 2 ERL Save it
With help of header value condition either we reduce the net value or increase net value.
TAX
The tax standard condition type is MWST; this condition type is applicable only for Indian clients.
For Indian clients we have JCST & JVAT.
The standard combination for MWST is
1. Departure country/Destination country.2. Departure country /tax classification one for customer.
Create condition table
Departure country/Destination Country(ALAND/LAND1)
708
Departure country/Tax classification of customer709
Create access sequence (V/07)
Copy MWST and create new one GWST
Create condition type (V/06)
Copy MWST and create new one GWST
Assigned the pricing procedure (V/08)
Place the tax after net value.
Maintained a condition records (VK11)
Go to VK11 and mention GWST condition type.
Create new tax code
Go to FTXP and create new tax code
Go to FTXP and mention your country code mention Tax code (G1) – mention some amount in mws (output tax).save it
If you get error here go to OBBG check tax procedure if (TAXD)
Statistical condition type
Any condition type if it is statistical it doesn’t have any effect on net value and it will not be posted in accounting.
1. VPRS: We maintain cost in material master accounting -1 view and that cost will be determine into sales document with the help of VPRS
Step Condition Type Description Statis Sub Total Requ Base for Account Key140 VPRS Cost B 4
2. SKTO (CASH DISCOUNT):
We maintain cash discount percentage in terms of payment and this percentage will be determined into sales document with the help of SKTO condition type.
Step Condition Type Description Statis Requ Base for
150 SKTOCash Discount 9 11
KUMU – CUMMULATION CONDITION
KUMU Condition type will help to cumulate the value of components and display in its mainitem.
4. PI01 (Intercompany Price)
No stock (2) (3)
IV01
Delivery (4)
(1)
CUSTOMER
GTN MUMBAI PLANT
GTN SRILANKA PLANT
PI01
While creating sales order in intercompany sales system determine PI01 condition type which is statistical.
When delivering company is raising invoice to ordering company then system determine IV01 condition type which is not statistical.
5. Free Goods Condition Type
R100 (100% Discount)R100 condition types determine for free goods line item and make the net value as ZERO
Place the R100 condition type in pricing procedure.
Step Condition Type Description Requ Base for Account Key160 R100 100% discount 55 28
R100 condition type will be determined only for those item categories for which pricing is ‘B’.
NRAB Condition Type
NRAB Condition type will be determined in free goods without item generation.
NRAB condition type will be calculated the value of free goods and deduct it from main value.
NRAB – Free goods without item generation.
Step Condition Type Description Requ Base for Account Key170 NRAB Free goods 59 29
6. Condition Type DIFF Condition type DIFF will help the round off the total document value.
7. Rebate condition types
1. Group Rebate – Bo012. Material Rebate – Bo023. Customer Rebate – Bo034. Independent Rebate – Bo06Group rebate is for group of materialsMaterial rebate is for a particular material Customer rebate is irrespective of materials NOTE: Rebate is always customer specific. 8. Condition type EDI1 &EDI2EDI1 – Customer expected price.EDI2 – Customer expected value.9. AMIW – Minimum sales order value & AMIZ- Minimum value of surcharges.
10. EK01 &EK02 COST11. VA00 – Variant value.
CONDITION CONTRLOSAccess Sequence We assign access sequence in condition type.Control data
Condition class.This field controls the type of price component .i.e. whether the condition type is Base price or Discount /Surcharges or Taxes.Base price - BDiscount /Surcharges – ATax - D Rebate – CCost - CAny condition type if condition class is ‘D’, then that value will be shown separately in tax column and that will not be added to net value.Q. Can I have 2 base prices active in a single sales document and where is the control?A. No, control in condition class B.Condition Class ‘C’ Any condition type if we check statistical then that will have two effects.1. The condition type value does not have any effect on total net value.2. The condition type value will not be posted into accounting
But any condition type, if condition class is ‘C’ even if it is statistical we can post it into some G/L accounts with help of accruals.
Q. There is a condition type which is in statistical but I want to post it into some G/L accounts where the control is?
A. Condition Class is C
PLUS/MINUS
This field controls whether to deduct the condition type value or add the condition type value.
If you want to deduct means maintain – X
If you want to add means maintain – A
Calculation Type
This field helps to convert the condition type amount to condition type value.
The calculation type for PR00 is C (Quantity)
The calculation type for K007 is A (Percentage)
The calculation type for KF00 is D (Gross weight)
The calculation type for HB00 is B (Fixed amount)
Condition Category
Condition category is a sub classification of condition class. This field will have relationship with pricing field in copy control.
Pricing Type
Pricing type controls how the pricing should be copied from source document to target document.
(i) Pricing Type – B (Carry out New Pricing)Here manually condition type will not be copied
(ii) Pricing Type – C (Copy manually pricing unchanged and re determine others)(iii) Pricing Type – D (Coping pricing element is unchanged and manually will also be copied)(iv) Pricing Type – G (Copy pricing element unchanged and re determined tax )
If pricing type is G then system identifies which condition in Tax and which condition should be re determined based on condition category ‘D’
(V) Pricing Type – H (Re determined only freight Condition)
If pricing type is ‘H’ system will re determined only freight condition for which condition category ‘F’.
Rounding Role: This field controls whether to perform commercial rounding (or) rounding up (or) rounding down.
In rounding rule 'A', values are always rounded up,
In rounding rule 'B', values are always rounded down
Structure condition
This field is special used for BOM; Structure condition will be used to cumulates the value of component and displays it in main item.
The standard condition type for cumulating is KUMU
EX COMPUTER TAQ 16,000/-
CPU TAE 9,000/-
Monitor 5,000/- 17,000/-
Key board 3000/-
Maintain for comments pricing – X & Statistical - X
GROUP CONDITION
Group condition: if the client’s requirement is considered the total document value or group of material value to propose a discount, then we have to check group condition.
If you check the group condition, the group condition amount will be distributed among all the line items in proportionate to the value of line item
Group condition Routine:
This field controls whether to consider total document value or group material value.
If we want to maintain total document value then maintain routine as 1.
If we want to maintain material values then maintain routine as 3.we use material pricing group field to group of the materials for group condition concept. We have this field is in material master in sales org- 2 view.
Rounding difference comparison
If we check this while distributing the group condition amount all the line items if there is any left out amount, that amount will be added to the largest item in the form of value.
Configuration for group condition (Total document value)
Q .Client requires is if value reaches to 10 lakhs then only, they want to propose 20k discount?
A. Group condition total document value, we have to create condition table with the combination as sales org.
I) create a condition table (713)
Select a field sales org, save it.
ii) Create new access sequence and place the condition table (GGCT)
iii) Create new condition type (GGCT)
iv) Place the condition type in your pricing procedure
V) Maintained condition records for this condition type.
Go to VK11 and enter condition type then mention your sales org, and enter amount 20000/- then select your line item and maintained scales amount 100000/- then save it
vi) Create a sale order and see the results
Configuration for group condition (Group of material)
Q .Client requires is if value reaches to 10 lakhs then only, they want to propose 20k discount?
A. in group condition concept for group of materials, we create condition table with the field material group
I) create a condition table (714 - material price group)
Select a field sales org, save it.
ii) Create new access sequence and place the condition table (GGCM)
iii) Create new condition type (GGCM)
iv) Place the condition type in your pricing procedure
V) Maintained condition records for this condition type.
Go to VK11 and enter condition type then mention your sales org, and enter amount 20000/- then select your line item and maintained scales amount 100000/- then save it
vi) Create a sale order and see the results
CHANGES WHICH CAN BE MADE
Manual entries
This field controls whether to change the condition amount or value manually into sales document or not.
If you want to change then maintain manual entries as BLANK or C
If you don’t want to change then maintain D
Amount/Delete/Value/Calculation type
If manual entry is blank or C, then further we have control, whether to change amount or value or delete or calculation type.
If we check this field then system will allow to change the manually, if we uncheck this field then system will not allow to change manually.
Q. There is a manually condition type which user enters manually but after entering the condition type system should not allow to change the amount or value where is the control?
A. Manually entry is BLANK or C and Amount and value.
Header Condition
Header condition is condition which is applicable all the line items in a sales document.
Header condition will always be processed manually; Header condition does not have accesses sequence
The standard header conditions are
1. HA00 – Header percentage discount 2. HB00 – Header fixed discount3. HD00 – Header freight discount4. HM00 – Header Order value
Sr.No Header Condition Group condition
1Header condition amount will be evenly distributed to all the line items in a sales
document
Group condition condition amount will be distributed in proportionate to the value of the
line item
2 Header condition should always be processed manually
Group condition condition can processed automatically or manually
3 Header Condition does not have access sequence
Group condition can have access sequence
Item Condition Item condition is condition which is applicable to particular line item in sales document.
Master Data Valid from &Valid to Valid from &valid to help to propose the default valid period while maintaining condition records, we can see the result in VK11.Pricing ProcedureThis pricing procedure field is condition type will be used for condition supplement concept
Condition Supplement It is the process of adding one condition record to another condition record.If the main condition record determining then only supplement condition record will be determined into sales document.
Configuration for supplement condition record Q. Client wants to offer 2% additional discount to the customer who are getting maximum price?I) create new condition typeSelect K007 and copy and create a GSUP and assign the access sequence K007.II) Place the supplement condition type in pricing procedure before gross value.
77 GSUP Supplement Condition 20 2 ERS
III) Placing the supplement condition type in pricing procedure III) Create new pricing procedure for supplement condition and place the main condition and supplement condition type.Go to V/08 and create new pricing procedure GSUPLM then select and double click on control, new entries.
Step Condition Type10 GR0020 GS00
Save it.IV) Go to V/06 and select your main condition type (GR00) and assign your supplement pricing procedure (GSUPLM).V) Then go VK11 and select material combination and select line item and click on supplement condition. Condition supplement symbol
Delete from data base This field controls whether the delete data permanently from data or not, only deletion flag.Condition IndexCondition index will help to display or change all the combination of prices in single window, will help to change all the combination of prices in single window.Configuration for condition indexStep-1. Check Index in condition type (Go to V/06 and select your condition and check Condition Index).Path: SPRO – SALES&DISTRIBUTION – BASIC FUNCTIONS – PRICING – MAINTAIN CONDITION INDEX – CLICK ON CREATE MODE – MENTION TABEL NUMBER –Create a condition table in which combination do you want to display the condition index.Select material combination and click on generate.Save it.Then go back and Double click on activation of condition index.Step-2. Check your condition table whether check or not.Step-3. Display the condition Index
Path: Easy Access – Logistics – Sales &Distribution – Master data – Conditions – Select using condition Type – Create – then double click on v/I6 – select the material & Click on continue – Mention material & Click on execute. If you want to see the all the records go to VK11 and Click on customize local layout.
Condition Update Restricting the condition records up to particular quantity (or) value (or) No. of orders.SAP restrict the no. of orders (3)Q. Purpose of condition update?Whenever company lunching new product we use condition update.For condition update we have Info structure (S071).The T-Code to see the info structure (OMO1)
Configuration for condition Update Step 1.Create a new condition type Copy K004 and new one GUUP (Condition Update) c
Conditions update saveit.Step 2.Go to V/08 and select your pricing procedure GVAA02, place your condition in your pricing procedure
33 GUUP Condition Update 20 2 ERS
Step 3.Maintain condition records go to VK11Enter your condition table GUUP and mention material and select line item and double click on additional data and mention max. Condition .base value.Note: - if you maintain condition update only you will get extra three fields in VK11 (order, value, qty,).at a time you can maintain only one field.Step 4. Go to VA01 and see the results.
Reference Condition Type
We use this only intercompany condition types.If pricing for both the condition are same then instead of maintaining condition records, we maintain condition records and that we assign it as reference condition type for other condition type.We have two conditions types for intercompany conditions PI01 &IV01 PI01 – Condition type determines intercompany sales order. IV01 – Condition type determines intercompany invoice.
We maintain condition records for PI01 condition type and that will be applicable to IV01 condition type. Because for IV01 Condition type we maintain reference condition type as PI01 See the results go to V/06 select IV01 NOTE: If you want any reference condition maintained reference application (V- Sales & Distribution) &Maintained reference condition type. Then save it.
Reference application
Without maintaining reference application we cannot proceed in reference condition type.Ex: - If you maintain reference application as (V) then assign reference condition type.
SCALES Scales is nothing but range of quantity /Value in the business where the quantity is going to increase, price should decrease, and discount should be increase for all condition types. Scales means maintaining the prices in the slab system is called scales.
Sr.No From Quantity Amount1 1 10,0002 101 99003 201 98004 301 97005 401 96006 501 9500
Scale Basis This field controls on what basis you want to maintain slab price that based on quantity or value or weight or net value.
Check Value This field controls whether the slab price amount should be increased or decreased.Base price it should be descending order A For discounts it should be in ascending order B
Scale type:We have two types of scale types.1. Normal scale
Normal scale in system directly determines that particulars slab price based on order quantity.Configuration for scales
Go to VK11 – select your condition type – choose material combination – and select line item – and click on scales
Scale Type Scale Quantity Amount1 0 10,0002 101 99003 201 98004 301 97005 401 96006 501 9500
2. Graduated scale.For graduated scale we maintained scale type as D, scale basis CConfiguration for scales
Go to VK11 – select your condition type – choose material combination – and select line item – and click on scales
Scale Type Scale Quantity Amount1 100 10,0002 200 99003 300 98004 400 97005 500 96006 1000 9500
Q. What scenarios system will active multiple base price condition type?A. graduated scale.
Exclusion Any condition type if we check exclusion and if that condition type determines into sales document, then it eliminates below condition type which we have the same requirement Exclusion can be maintained at 2 places.1. Condition type level2. Condition record level
For condition type level (go to V/06 & click on exclusion)
Fro condition records level go to VK12 and select line item &click on details there you find exclusion.
EXCLUSIVE GROUPS
This is the process of grouping multiple condition types in one and making the system to propose the best discount (or) least discount, this concept is called Exclusive Group.
Configuration for exclusive groupSPRO – SALES & DISTRIBUTION – BASIC FUNCTIONS – PRICING – CONDITION EXCLUSION –CONDITION EXCLUSION FOR GROUPS OF CONDITIONS – DOUBLE CLICK ON DEFINE EXCLUSION GROUPS – NEW ENTRIES – CREATE A NEW GROUP (G001) – SAVE IT –THEN GO BACK AND CLICK ON ASSIGN CONDITION TYPES TO THE EXCLUSION GROUPS –
Exclusion Group Condition TypeG001 G004G001 G005G001 G007G001 G020
SAVE IT – THEN GOBACK AND DOUBLE CLICK ON MAINTAIN CONDITION EXCLUSION FOR PRICING PROCEDURES AND SELECT YOUR PRICIGN PROCEDURE – DOUBLE CLICK ON EXCLUSION – NEW ENTRIES.
Sr.No Cpr Procedure ExGR110 A Best condition between the condition types G001
Create the order and see the results
2 nd type
Sr.No Cpr Procedure ExGR110 L Least condition between the condition types G001
Create the order and see the results
EXCLUSION BETWEEN TWO GROUPS
Configuration SPRO – SALES & DISTRIBUTION – BASIC FUNCTIONS – PRICING – CONDITION EXCLUSION –CONDITION EXCLUSION FOR GROUPS OF CONDITIONS – DOUBLE CLICK ON DEFINE EXCLUSION GROUPS – NEW ENTRIES – CREATE A NEW GROUP (G002) – SAVE IT –
THEN GO BACK AND CLICK ON ASSIGN CONDITION TYPES TO THE EXCLUSION GROUPS –
Exclusion Group
ConditionType
G001 G004G001 G005G002 G007G002 G020
SAVE IT – THEN GOBACK AND DOUBLE CLICK ON MAINTAIN CONDITION EXCLUSION FOR PRICING PROCEDURES AND SELECT YOUR PRICIGN PROCEDURE – DOUBLE CLICK ON EXCLUSION – NEW ENTRIES
Sr.No Cpr Procedure ExGR1 ExGR2
10 CBest condition between the two
exclusive groups G001 G002Save it, create the order and see the results
2 nd type
Sr.No Cpr Procedure ExGR1 ExGR2
10 FLeast condition between the two
exclusive groups G001 G002Save it, create the order and see the results
SIXTEEN FIELDS OF PRICING PROCEDURE
Step Count
Condition Type
Description Fr To Man
Required
Statis
Sub Total
Requirment
Calculation
type 1
Base for
Account Key
Accurals
10 GR00 2 ERL
20 Base value 10
30 G004 Material 20 2 ERS
33 GUUP Condition Update
20 2 ERS
40 G005 Customer/Material
20 2 ERS
50 G007 Customer Discount
20 2 ERS
60 G020 Price Group 20 2 ERS
70 G032 Price Group/Material
20 2 ERS
75 GA00 Percentage Discount
20 2 ERS
76 GB00 Discount (Value)
20 2 ERS
77 GSUP Supplement Condition
20 2 ERS
80 Gross Value 20 70
90 GF00 Frieght 80 2 ERF
91 GD00 Header Frieght 2 ERF
92 GM00 Order Value 2 ERL
100 GPAC Packing 80 2 EPC
110 GINS Insurance 80 2 EIN
120 Net Value 80 110
130 GWST 120 10 16 MWS
140 VPRS Cost B 4
150 SKTO Cash Discount 9 11
160 R100 100% discount 55 28
170 NRAB Free Goods 59 29
1. STEP :
Step specific the sequence of the condition types in pricing procedure.Step number also will be used in FROM &TO to determine the base value.
2. COUNTER :We use counter if there is no space between the steps to add one more condition type.If we use counter then we need to use formulas like ALT CTYPE &ALT B TYPE.
3. CONDITION TYPE :It controls the type of Price component & Price element.
4. DESCRIPTION : It will help to describe the condition type in sales document pricing.Description will also used to bifurcate the pricing structure.Ex: Base value, Gross value, Net value, etc.All bifurcations steps are in staticals only, whenever you enter the description you should maintain statical only.
5. FROM :
From the standard base from will help to determine the base value to calculate the “condition type value”.
6. TO :To will help to cumulates the values of multiple steps which are in sequence.Ex: We used TO for gross value, net value, total value.
7. MANUAL :If we check manual for any condition type then that condition type will not determine in sales document automatically, we have to enter by manual. In all header conditions proceed manual only. Q. There is a condition type which is manual but after entering the condition type system should not allow to change the value where the control?A. in condition type controls manual entry uncheck VALUE.
8. REQUIRED:
Any condition type if you check required then system will not allow to save the document if the condition type is missing. In standard base price, sales tax we check.
9. STATISTICAL:
If you check this then condition type value does not effect on the net value, if you check this the condition type value will not be posted into accounting.In standard the below condition types are statistical.VPRS, SKTO, EK01, EK02, PI01, KUMU.Q. There is a condition type which is statistical but still I want to posted it into some G/L accounts, where is the control?A. condition class (C), along with accruals (ERU).10. PRINT:This field controls whether to print the condition type amount or value into the print out.If you want to print maintain X, If you do not want to print maintain blank,If you want print at the condition types at header level then maintain it as S.All header condition type we will maintain printer S.11. SUBTOTAL: Subtotal will be used to storage the values of condition type in some temporary tables and fields for the purpose of further calculations.We do calculations in alternate calculation types and alternate base type.These two are formulasSubtotal for VPRS is BProfit margin = Base value - VPRSThe calculation profit margin we have a standard formula alternate calculation type i.e. 1111 = (KOMP – NETWR) – (KOMP – WAVWR)11 = NET VALUE – SUBTOTAL (B) (VPRS).
Configuration for Profit marginGo to V/08 then select your pricing procedure GVAA02, Double click on controls then new entries.
Step Description Statistical Alternate calculation type250 Profit 11
Sub Total Short Description- No Seprate Subtotal1 KOMP-KZWK12 KOMP-KZWK23 KOMP-KZWK34 KOMP-KZWK45 KOMP-KZWK56 KOMP-KZWK67 KOMP-BONBA(Rebate basis 1)8 KOMP - BRTWR(Preferance Value )9 KOMP -BRTWR (Gross Value)A Carry over price KOMP - CMPRE(Credit Price )B Carry over value KOMP - CMPRE(Credit Price )C KOMP -GKWRT(Statistical Value)
Subtotal will also to be used to update the sales document values into credit management.Subtotal will also to be used to update the billing document value into rebate agreement.The subtotal for credit management is A and Subtotal for rebate agreement is 7.
12. REQUIREMENT Requirement is a condition which system will check every time while determining the condition type in sales document. If the requirement is fulfills then only the condition type will be determined into sales document. If the requirement is not fulfilled then the condition type will not be determined into sales document.1. Standard requirement is “2” and requirement “2” checks that item category pricing field should be “X” or “B”2. The requirement for VPRS is “4”, Requiremnt “4” checks that determine COST FIELD in item category should be check.Determine cost field = EVRWR3. The requirement for SKTO is “9” and requirement “9” checks that the cash discount field in a material master should be check. KOMP-SKTOF = X
4. The requirement for R100 is 55 and requirement 55 checks that the pricing field in item category should be only “B” that is the reason R100 condition determines only for free goods.5. The requirement NRAB is 59 6. The requirement for REBATE condition is 24 and 24 checks that the document should be billing document that is the reason rebate condition type determines only billing documents.7. The requirement for intercompany condition type is 22 & and requirement 22 checks that ordering company & delivering company should be differ.
Q. If stock is there systems consider PR00 and if stock is not there system consider WPRO (it means we place the order third party process). PROO WPRO
Plant Third party process
Required
13. ALTERNATE CALCULATION TYPE
Alternate calculation type is a formula; we use ALTCTYPE (alternative calculation type) if the calculation type is not standard. There is Base value, Amount &Condition value. If you maintain formula ALTCTYPE then no need to maintain condition records. Because system is directly proposing condition value.
14. ALTERNATE BASE VALUE The standard base is “FROM”.Alternate base type is a formula we use alternate base type calculation part of base type if the calculation part of the base type is not standard If you maintain formula in ALTBTYPE then you have to maintain condition records, to convert the base value into condition type value
DIFFERENCE BETWEEN ALT C TYPE &ALT B TYPE
Sr.No ALT C TYPE ALT B TYPE1 We use ALT C
TYPE if the calculation part of the conditon type value is not standard
We use ALT B TYPE if the calculation part of the base value is not standard
2 If you maintained formula in ALT CTYPE then system will calculate and
If you maintained formula in ALT B TYPE then system will calculate and
PROO 900
WPRO 901
KOMP – PSTYV = TAS
KOMP - PSTYV
propocess condiotn value
propose base value
3 If you maintianed formula in ALT C TYPE then no need to maintian conditon records
If you maintained formula in ALT B TYPE then you have to maintian condiotn records to convert the base value into conditon value.
15. ACCOUNT KEY
Account key is one of the parameter to determine revenue G/L accounts while posting invoice values into accounting.
ERB - Rebate sales deduct.ERF - Freight revenueERL - RevenueERS - Sales deductionsERU - accrualsMWS – Sales TaxMW3 – Sales Tax
16. ACCRUALS/ACCRUALS(REBATE) Accrual is a provisional account, which will help to keep some money assign from each transaction to meet further requirement of rebate settlement. Accruals account key is ERU
Q. There is a condition type which is statistical but, I want to post into some G/L account? Where is the control?
Control class “C” along with accruals “ERU”
Q. How pricing procedure determines into sales document?
A. SALES ORG (G100, G1, G1)
1. Document pricing procedure “A”
1000000 /-
6% To Keep 60,000/- for rebate
OVKK
Customer Pricing Procedure “1”
2. Go inside the pricing procedure (V/08).
Step Condition Type Requirement type10 GR00 2
Requirement checks that requirement is fulfilled or not.
3. Then checks the GR00 condition type and access sequence.
Go to V/06 and select GR00 and check access sequence GR00.
4. Then check the access sequence assigned tables.
Go to V/07 select your access sequence and GR00 and find the tables.
5. VK11 and pricing
EXPLANATION Step –1 system will determine the pricing procedure based on sales org, Distribution channel, Division (Sales Area), Document pricing procedure, Customer pricing procedure.Step – 2System will go inside the pricing procedure and check the condition type whether requirement is fulfilled or not, if requirement is fulfilled Step – 3Then system will go to the inside the condition type and take the access sequence.Step – 4Then system will go to the inside the access sequence and take the tablesStep – 5Then system will go to the inside the condition tables and check the valid condition records.If valid condition records exist then system will determine condition records into sales document like that the process goes for all the condition types in pricing procedure.