Important tables for sap sd

Important Tables for SAP SD
Sales and Distribution:
Table Description
Customers KNA1 General Data
KNB1 Customer Master – Co. Code Data (payment
method, reconciliation acct)
KNB4 Customer Payment History
KNB5 Customer Master – Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data
(credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Partner Function key
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link
Sales Documents VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document - Header Data
VBKD Sales Document - Business Data
VBUP Item Status
VBAP Sales Document - Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records
SD Delivery DocumeLIPS Delivery Document item data, includes
referencing PO
LIKP Delivery Document Header data
Billing Document VBRK Billing Document Header
VBRP Billing Document Item
SD Shipping Unit VEKP Shipping Unit Item (Content)
VEPO Shipping Unit Header
SD Master Records
———————————————————
Business Partners
XD01/VD01 Create Customer Master Centrally
XD02/VD02 Change Customer Master Centrally
XD04/VD04 Display Changes to the Customer Master Centrally
XD05/VD05 Block or Unblock a Customer

OV50 Display of Changes for Customer
V-07/VD01 Create One-Time Customer (Sales)
V-08/VD01 Create Payer (Centrally)
V-09/VD01 Create Ordering Party (Centrally)
Item Proposal
VA51 Create Item Proposal
VA52 Change Item Proposal
Conditions
VK11 Create Condition
VK12 Change Condition
VK14 Create Condition with Reference
SD Sales Process
———————————————————
Sales Inquiry
VA11 Create Inquiry
VA12 Change Inquiry
VA15 List of Inquiries
Sales Quotation
VA21 Create Quotation
VA22 Change Quotation
VA25 List of Quotations
SDQ1 Expiring Quotations
SDQ2 Expired Quotation
SDQ3 Completed Quotations
V.04 Display Incomplete Quotations
Scheduling Agreement
VA31 Create Scheduling Agreement
VA32 Change Scheduling Agreement
VA35 List of Scheduling Agreements
V.05 Display Incomplete Scheduling Agreements
Contracts
VA41 Create a Contract
VA42 Change a Contract
VA45 List of Contracts
V.06 Display Incomplete Contracts
SDV1 Display Expiring Contracts
SDV2 Display Expired Contracts
SDV3 Display Completed Contracts

Sales Order
VA01 Create a Sales Order
VA02 Change a Sales Order
VA05 List of Sales Orders
V.02 Display Incomplete Sales Orders (Sales Order Error Log)
V.14 Display Blocked Orders
SDO1 Display a List of Orders Within Time Period
Debit Memo Request Processing
VA01 Create a Debit Memo Request
VA02 Change a Debit Memo Request
VA05 List of Debit Memo Requests
V.14 Display Blocked Debit Memo Requests
Credit Memo Request Processing
VA01 Create a Credit Memo Request
VA02 Change a Credit Memo Request
VA05 List of Credit Memo Requests
V.14 Display Blocked Credit Memo Requests
Returns
VA01 Returns Order
VL01N Returns Delivery
VF01 Credit for Returns
Shipping and Transportation
———————————————————
Delivery
VL01N Create Delivery
VL02N Change Outbound Delivery
VL22 Display Delivery Change Documents
VL71 Output from Deliveries
VL10A Process Delivery Due List
Picking
VL06O Sel. Outbound Deliveries for Picking
Post Goods Issue
VL06G Deliveries for Goods Issue
VL09 Cancel Goods Issue for Delivery Note
VL23 Goods Issue (Background)

SD Billing
———————————————————
VF01 Create Billing Document
VF02 Change Billing Document
VF04 Process Billing Due List
VF05 List Billing Documents
VFX3 Release Billing Documents
VF31 Output from Billing
VF11 Cancel Billing Document
VKM1 Blocked SD Documents
VKM2 Released SD Documents
Sales Information System
———————————————————
MCTA SIS: Customer Analysis – Selection
MCTC SIS: Material Analysis – Selection
MCTE SIS: Sales Org. Analysis – Selection
V/LD Execute Pricing Report
SAP SD Transaction codes List
I found a way to know hidden customizing Tcodes.
Before executing customizing task you desire, point it and go to Edit-Display IMG
Activity. Then mark activity.
Go to T.Code se16 and type in CUS_IMGACH table.
Execute.
Paste IMG Activity and run.
You will see Tcode that belongs to IMG Activity.
Where do we maintain "Item Category Usage" at the master level?
Spro --> Sales and Distribution --> Sales --> Sales Documents --> Sales Document Item
--> Define Item Category Usage
Item Category Usage: item category usages which control the usage of an item. Item
category usage controls, for example, the system response if during document processing
an item does not refer to a material but to a text item. Item category usage can also be
maintained via the item categories

In contracts we are creating quantity contract and value contracts in that we only
put the validity period after validity period that contract will close,but customer
want before one month closing the period system should alert with popup box like
this contract is going to close, for this sales manager can follow up the customer for
renual the contract.
Getting a pop-up when the Contract is going to expire is not a Standard SAP thing. For
this you need to do some programming. Instead of this the Std system has a reminder
system where in the open Contracts and Quotaions are popped up when you about to
create a sales order.
This setting is in the Sales order header ,
Goto -- VOV8 --- Quotation and Outline agreement messages
If you want to have different number range for different sales area where the
settings to be done.
Number Rage are use to define what number to be assign to sales document type.
Number range can be assign Internal or external.
In internal number range system automatically assign a number to sales document
according to number range define in system.
In External number range user manually assign number to sales document.
For Assigning Number Range use T-Code VN01
Choose Intervals ---- Define your number range
Task Specifc SD Transaction Codes 1
How to configure tax?
Use the following Tcodes:
OBQ1 --- CONDITION TABLE
OBQ2 --- ACCESS
OBQ3 --- TAX PROCEDURE CAL

OBBG --- ASSIGN COUNTRY TO TAX PROC
OVK3 --- CUSTOMER TAX CATEGORY
OVK4 --- MATERIAL TAX CATEGORY
OVK1 --- TAX DETERMINATION RULES
OVK6 --- ASSIGN DELIVERY PLANTS
and thenVK11 to maintain the condition record for the tax rate.
I raise a sales order and is getting a error stating that "sales area is not defined".
1) At SPRO-->SD-->Sales header-->Assign Sales area to Sales document - Combine
your Sales Organisations, Distribution Channels & Divisons
2) At VOPA-->Assign Partner Determination procedure to your Account Group of
Customer Master you are using.
3) At VOPA--> Assign Partner Functions to your Account Group & Partner
Determination procedure
Steps to create a Vendor Master Data at the client level and how do we extend it to
different company codes?
Follow the following steps:
1. Create a vendor account group OBD3
2. Define no. range for vendor account group XKN1
3. Assign number range to Vendor account group OBAS
4. Define tolerance Group for vendor OBA3
5. Create 2 GL accounts FS00
a) Purchases A/c
b) S. creditors A/c
6. Create Vendor master data XK01
7. change/block vendor master data XK02/XK05
8. Define document type and no. range OBA7
a) KA
b) KG
c) KR
d) KZ *-- Vandna
How to find the strategy group in sap sd?
Menu path for Strategy Group is:
Spro --> Production --> Production Planning --> Demand Management --> Planned
Independent Requirements --> Planning Strategy --> Define Strategy Group.
OPPT -- Maintain Starategy Group

We can see Strategy Group in Material Master Record - MRP 3 - Planning -- Strategy
Group.
10 - For Make to Order
20 - For Make to Stock
SAP SD Tips by: Javier
The most frequently used transaction codes are as follows:
1. VS00 - Master data
2. VC00 - Sales Support
3. VA00 - Sales
4. VL00 - Shipping
5. VT00 - Transportation
6. VF00 - Billing
Others as follows:
At Configuration:
1. VOV8 - Define Sales documents type (header)
2. OVAZ - Assigning Sales area to sales documents type
3. OVAU - Order reasons
4. VOV4 - Assign Item categoreies(Item cat determination)
5. VOV6 - Scedule line categories
6. OVAL - To assign blocks to relevant sales documents type
7. OVLK - Define delivery types
8. V/06 - Pricing
9. V/08 - Maintain pricing procedure
10.OVKP - Pricing proc determination
11.V/07 - Access sequence
Enduser:
1. Customer Master Creation-VD01 and XD01 (for full inclu company code)
VD02 - Change Customer
VD03 - Display Customer
VD04 - Customer Account Changes
VD06 - Flag for Deletion Customer
XD01 - Create Customer
XD02 - Modify Customer
XD03 - Display Customer
2. Create Other material ----MM00
3. VB11- To create material determination condition record

4. CO09- Material availability Overview
5. VL01 - Create outbound delivery with ref sales order
6. VL04 - Collective processing of delivery
7. VA11 - Create Inquiry
VA12 - Change Inquiry
VA13 - Display Inquiry
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
· VA01 - Create Order
· VA02 - Change Order
· VA03 - Display Order
· VA02 - Sales order change
· VA05 - List of sales orders
· VA32 - Scheduling agreement change
· VA42 - Contract change
· VA21 - Create Quotation
· VA22 - Change Quotation
· VA23 - Display Quotation
Billing
· VF02 - Change billing document
· VF11 - Cancel Billing document
· VF04 - Billing due list
· FBL5N - Display Customer invoices by line
· FBL1N - Display Vendor invoices by line
Delivery
· VL02N - Change delivery document
· VL04 - Delivery due list
· VKM5 - List of deliveries
· VL06G - List of outbound deliveries for goods issue
· VL06P - List of outbound deliveries for picking
· VL09 - Cancel goods issue
· VT02N - Change shipment
· VT70 - Output for shipments
General
· VKM3, VKM4 - List of sales documents
· VKM1 - List of blocked SD documents
· VD52 - Material Determination

KONV Conditions for Transaction Data
KONP Conditions for Items
LIKP Delivery Header Data
LIPS Delivery: Item data
VBAK Sales Document: Header Data
VBAP Sales Document: Item Data
VBBE Sales Requirements: Individual Records
VBEH Schedule line history
VBEP Sales Document: Schedule Line Data
VBFA Sales Document Flow
VBLB Sales document: Release order data
VBLK SD Document: Delivery Note Header
VBPA Sales Document: Partner
VBRK Billing: Header Data
VBRP Billing: Item Data
VBUK Sales Document: Header Status and Administrative Data
VBUP Sales Document: Item Status
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)
VEPVG Delivery Due Index
Transaction Action:
J1I2 - Prepare a sales tax register
J1I3 - Create outgoing excise invoices in batches
J1I5 - Update the RG 1 and Part I registers
J1IEX - Incoming Excise Invoices (central transaction)
J1IEX_C - Capture an incoming excise invoice (excise clerk)
J1IEX_P - Post an incoming excise invoice (excise supervisor)
J1IF01 - Create a subcontracting challana

J1IF11 - Change a subcontracting challan
J1IF12 - Display a subcontracting challan
J1IF13 - Complete, reverse, or recredit a subcontracting challan
J1IFQ - Reconcile quantities for subcontracting challans
J1IFR - List subcontracting challans
J1IH - Make a CENVAT adjustment posting
J1IIN - Create an outgoing excise invoice
J1IJ - Assign excise invoices to a delivery for sales from depots
J1INJV - Adjust withholding tax Item
J1INREP - Reprint a withholding tax certificate for a vendor
J1IQ - Year-End Income Tax Depreciation Report
J1IR - Download register data
J1IS - Process an excise invoice (outgoing) for other movements
J1IU - Process exemption forms
J1IW - Verify and post an incoming excise invoice
J1IX - Create an incoming excise invoice (without reference to purchase order)
J2I8 - Transfer excise duty to CENVAT account
J2IU - Remit excise duty fortnightly
J2I9 - Monthly CENVAT return
J1IG - Excise invoice entry at depot
J1IGA - Create additional excise entry at depot
J2I5 - Extract data for excise registers
J2I6 - Print excise registers
Standard SAP SD Reports
Reports in Sales and Distribution modules (LIS-SIS):
Sales summary - VC/2
Display Customer Hierarchy - VDH2
Display Condition record report - V/I6
Pricing Report - V/LD
Create Net Price List - V_NL
List customer material info - VD59
List of sales order - VA05
List of Billing documents - VF05
Inquiries list - VA15
Quotation List - VA25
Incomplete Sales orders - V.02
Backorders - V.15
Outbound Delivery Monitor - VL06o
Incomplete delivery - V_UC
Customer Returns-Analysis - MC+A
Customer Analysis- Sales - MC+E
Customer Analysis- Cr. Memo - MC+I

Deliveries-Due list - VL04
Billing due list - VF04
Incomplete Billing documents - MCV9
Customer Analysis-Basic List - MCTA
Material Analysis(SIS) - MCTC
Sales org analysis - MCTE
Sales org analysis-Invoiced sales - MC+2
Material Analysis-Incoming orders - MC(E
General- List of Outbound deliveries - VL06f
Material Returns-Analysis - MC+M
Material Analysis- Invoiced Sales - MC+Q
Variant configuration Analysis - MC(B
Sales org analysis-Incoming orders - MC(I
Sales org analysis-Returns - MC+Y
Sales office Analysis- Invoiced Sales - MC-E
Sales office Analysis- Returns - MC-A
Shipping point Analysis - MC(U
Shipping point Analysis-Returns - MC-O
Blocked orders - V.14
Order Within time period - SD01
Duplicate Sales orders in period - SDD1
Display Delivery Changes - VL22
SAP Sales and Distribution Frequently Asked Question
Master Data
Q: Some materials have been blocked for procurement and production. Even though
deletion flag is set for a material/plant level, the order can be still entered ( with a
warning message). Is there a way to block such transactions for a material flagged for
deletion?
A: Sales Status field in the sales organization view of the material master may be used to
block any transaction for the material.
Q: We can define our own exchange rate types and use them instead of the defaulted
types, 'M', 'B' and 'G'. How can we overwrite default types in SD?
A: Exchange rate gets copied from the customer master record. Exchange rate types are
to be maintained for the customer in the sales screen of the customer master record.
Shipping

Q: The PL00 condition is fine in delivery. But when we try to print to either the screen or
printer, an error V1032 occurs. Why?
A: In order to use the Packing list PL00 (packing slip in delivery) you must do 'Packing'
in the delivery note (edit->packing)
Q: we have to enter a shipping point while creating a delivery. Is it possible to create
delivery without shipping points?
A: When you are releasing a sales order, choose Sales document -> Subsequent
functions-> Create delivery, then the shipping point will be brought in from the sales
order. In all other scenarios you have to key in the shipping point. The above described
scenario will only work if all items on the sales order are to be shipped from the same
shipping point.
Billing
Q: SAP allows a non-inventory item and an inventory item to be in the same document
till delivery but splits at the time of creation of billing document. Can we combine a non-
inventory item with an inventory item in one invoice? Can we treat it as a value item in
sales order so that it is priced and then make it as a text item in delivery documents so
that it appears in the same invoice and does not split?
A1: Make the non-stock material deliverable, but not pickable. Both items will carry into
the delivery, and therefore appear on the same invoice.
A2: Change the copy rule for orders->invoices and deliveries->invoices to specify that
invoice combination is permitted. However note that for system to create combined
invoices, PO number, payment terms, sales organization, and distribution channel must
be identical. Else undesirable combinations may be created by the system.
Pricing Conditions
Q: It is impossible to price at the material level (matnr) , when a material has a pricing
reference (mvke-pmatn) set up against it in the master data. Pricing always look for the
pref, even if a price is set up against the material and not the pref. How can we price by
material and pref?
A: The field used to look up at the price is defined in Access sequence. You may find a
step with PMATN as material number. If you insert a step with MATNR then the system
will first look for the material, if not found (use the exclusion tick box) it will look for the
pref.

Customizing
Q: We generated a new condition table. Assigned the condition to access sequence.
Created a condition record. Access sequence is assigned to the output type. But when we
create a billing document, output screen comes up blank for the output type. When we
look up Determination Analysis, we get an error "Note 524 Access not made (Initialized
Field)". What else is required to be done?
A: Assign output determination procedure to the header of the document and the output
type.
Q: How can we set up to have the VAT# be accepted in the Ship-To Master File Data
Control screen?
A: IMG->Fin. Acct.->AR and AP ->Customer acct->Master Record -> Prepare to Create
Customer-> Define Acct. Group.
Q: We want to explode Bill of Material automatically at time of Order entry and explode
an Equipment BOM in the sales order. What are the setting required?
A: Use an item category that is configured for bills of material for having a sales BOM to
explode automatically.
Standard SAP item categories are :
TAQ - Pricing and inventory control take place at the BOM header level
TAP - Pricing and inventory control take place at the BOM item level
These can be automatically derived using the item category groups ERLA and LUMF,
respectively.
Q: How can we make the Customer Group 1 (or 2, 3, 4, 5) a mandatory field?
A: Logistic General-> Logistics Basic Data: Business Partners -> Customers -> Control
-> Define account groups and field selection for customer
Choose Customer Acct. GR. (double-click). -> Field Status: Sales data (double click) ->
sales (double click) .Check the radio button against Customer Gr as REQ. ENTRY. Save
the settings to make customer GR entry mandatory .
Q: Is there an user exit to copy the data into planning table?
A: Use user exit MCP20001 and include ZXSOPU01.
Others
Q: We get a report screen: "Goods issue: Problem Log" during the delivery process when
activating Post Goods Issue button. We want to include our own error message to this list
if the selected batch is not on a customer defined table. What is the best way?
A: Try User exit - USEREXIT_SAVE_DOCUMENT_PREPARE

Link Between SAP SD, MM & FI
1. In SAP you will always get integration with other modules. SD will interact with FI,
MM will interact with SD :-
1a. Looking at MM and SD interaction first, take the scenario of a third party order
process. This process uses a purchase order (which is sent to your vendor). Also invoice
verification is used further along the process to check that the invoice you send to your
customer is the same material and quantity as that which the vendor sends to you (but
obviously shipped
directly to your customer).
1b. Billing is an SD function. But SAP needs to know, when processing a customer's
payment, to which GL account the payment has to be processed. For instance payment of
a UK based material would be placed in a different GL account to that of a non-UK based
material. Furthermore, a UK based customer may have a different GL account to that of
an Export customer. This is configured in Account Determination.
2. ABAPers are there to essential do some bespoke development. Your integration, or
interaction, with them would be when specifying the tables, fields, input fields, a simple
process explanation, data mapping (if doing an interface from one system to another)
etc. *-- Shahee
The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material
master of MM.
2. MRP and availibility check related data is also taken from MM although you control
this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the
shipping point determination takes place with the help of the loading group, plant data,
shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area
of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-

1. Whenever you create a delivery with reference to a sales order, goods movement takes
place in the bacgground. eg. In case of standard sales order, you create an outbound
goods delivery to the customer.
Here movement 601 takes place. This movement is configured in MM. Also, this
movement hits some G/L account in FI. Every such movement of good s hits some G/L
account.
2. The accounts posting in FI is done with reference to the billing documents (invoice,
debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between
SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order –
Integration Points Module
•Availability Check - MM
•Credit Check - FI
•Costing - CO/ MM
•Tax Determination - FI
•Transfer of Requirements - PP/ MM
Delivery & Goods Issue –
•Availability Check - MM
•Credit Check - FI
•Reduces stock - MM
•Reduces Inventory $ - FI/ CO
•Requirement Eliminated - PP/ MM
Billing -
•Debit A/R - FI/ CO
•Credit Revenue - FI/ CO
•Updates G/ L - FI/ CO
(Tax, discounts, surcharges, etc.)
•Milestone Billing - PS
Return Delivery & Credit Memo -
•Increases Inventory - MM
•Updates G/ L - FI
•Credit Memo - FI
•Adjustment to A/R - FI
•Reduces Revenue - FI
Tips by: Subha
SD Transaction Code Flow:

Inquiry / Document type IN
Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP
Quotation / QT
Purchase Order PO
Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
Sales Order OR
Delivery LF
Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS
Billing MN
Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
To create a sales order we need purchase order number and custmer number. Before that,
to create a purchase order we need to have material no, vendor no.
To create vendor tcode is
xk01(create), xk02(change) , xk03(display)
Tables are lfa1.
To create custmer tcode is xd01, xd02, xd03.
Table is kna1.
After creating sales order using this no we can create delivery note tcode is vl01.
Why Do We Assign Division to Sales Organisation
In SAP, why do we assign division to Sales organisation not to distribution channel?
In SAP Business Process
Sales Area= Sales Org.+Dist.Channel+Division.
Its Triangular intraction
Sales organization
/
/
Dist.Channel<----------------->Division

Sales Org controls Distribution Channel and Division
Distribution Channel: The channel that is choosen the organization to make their product
reach the end customer.(Network)
Division: Ex: HLL--------> Detergents, Out of Home,Food Products,Health Care
Sectors/Departments
TATA Motars: Trucks/Bus,Cars,Heavy Vechiles Etc...
Please note it is not:
Sales organization
|
|
Dist.Channel
|
|
Division
Division is an Oragaizational Unit.
The Division in the Material Master is not an Organizational Unit that can be used to
maintain related fields. It is a field which is used to uniquely assign a material to a
Division.
How To Do Master Record Mass Maintenance
Which master records mass maintenance can be done?
What do you mean by mass maintenance?
Mass maintainance in MM-
1. Mass Maintainance means to change a master data or transactional data in mass
2. SAP has provided Mass Maintainance for many objects
Examples:Material masters, BOMs, Routings, Workcenters in PP
In MM --> Inforecords, PO,s Preqs etc
To do master record mass maintenance

You can use tcode MASS and then select your Object type or there is few specific mass
maint. Tcode is available like for PO = MEMASSPO etc. but you can use MASS also for
that you need to select the object type for PO
Tips for mass modification:
Use object type BUS1001 and generate. Then you have to know the tables where the field
you want to modify is. Pick the fields in their folder and generate again. Then in
selection pick the materials or use other selection criteria. Generate again.
In the upper side of the screen insert the data and click the button 'carry out a mass
change'.
Save and leave.
Master records mass maintenance can be done:
Material master, info record, vendor, PO, PR, etc.
What do you mean by mass maintenance?
MASS maintenance means - suppose you want to change prticaulr field of material for all
the mateirl of certian plant or all the plant you can do using mass like wise for certian PO
value if you want to cahnge you can use mass.
There a lot of transactions for specific mass changes. MASS is also one of the
transactions among them.
- Mass Change in material master. MM17
- Mass change in BOM. CS20
- Mass change in work center. CA85
- Mass change in Reference opn set. CA95
- Mass change in PRT. CA75
- SU10 Mass changes to User Master.
- SU12 Mass Changes to User Master Records.
- CO44 Mass processing of orders.
- F.80 Mass reversal of documents.
- FOFO Mass release.
- FOVX Mass processing of offers.
- IMAM Mass maintenance of approp.requests.
- KE55 Mass Maintenance PrCtr Master Data.
- XD99 Customer master mass maintenance.
- XK99 Mass maintenance, vendor master.

Serial Number Management In SAP SD
By: Rob
I am following the below step:
1. Serial number profile is created.
2. Assigned sales order procedure (SDAU) and delivery proceedure to serial
number (SDLS).
3. Profile is assigned in material master record
4. Assume there is a stock of 10 quantity without serial number (you can do 561 for
initial stock posting )
5. IQ01 created serial number for all the 10 stock.
6. VA01 created sales order for one quantiy
7. Assigned one serial number for this material
8. Sales order is saved and delivery and PGI is done for the same serial number and
material
9. MMBE stock is reduced with one quantity
10. MB51 if check the material document in serial number TAB i can see a message
that "The material is managed in serial numbers"
So now my question is why I can't see serial number in material document? How
can able to see that? what is the configuration required?
Whatever settings you have maintained is correct. I shall share as to what happens in our
business process.
VA01- Sales order
Vl03 - Delivery
LT03- Transfer Order
After transfer order there is a transaction used ZL02 where in the delivery number is
entered and on executing, a screen pops up asking for the serial number. Here we enter
the serial number maintained for the material and is got from MMBE. And the serial
number is captured for the material.
Pls check for the serial numbers in MMBE and I suppose a program needs to be created
by an ABAPer for the serial number to be fetched and a transaction to be
created and associated with the program.
I need Serial Number Profile tables as soon as possible.
T377P - Serial Number Management Profiles
T377P_T Texts for Serial Number Management Profiles

T377X Documents Allowed for Serial Number Management
T377X_T Texts for Serial Number Management Documents
T5KSN ROE Serial Number
SERI Serial Numbers
EQBS Serial Number Stock Segment
EQSE Serial Number Records
IQ09 - Check Material Serial No
In outbound delivery, post goods issue failed because of serial number, but this
serial number was not assigned to any other material.
Check the serial number and material with IQ03. Serial number is material specific.
When I looked at the IQ03, for the serial no "#162559019S.", I realized that the
status is still remain as EDEL and ESTO.
Supposingly, the status should only has ESTO. Is there a way to remove the status
"EDEL"?
Go to IQ02, do the following steps:
1. Go to edit -> Special serial number function -> manual transaction
2. Choose "to stock"
The status should be ESTO now. Try it.
EDEL status shows that it is assigned to a delivery. Change it by going into IQ02 --> Edit
--> Sp.Serial number Functions --> Manual Transaction and make it 'to stock'
If the serial number has status EDEL ESTO that means the serial number is assigned to
the Delivery, reversal PGI has not been completely performed.
Once you do that then only this will come as ESTO.
Please check your SD document flow if all the documents have been reversed.
Click the Status of Serial Number Master record.
- ESTO status In the warehouse. means .. open..
- EDEL (Assigned in delivery note). According to this status,
transaction 'Goods issues' is not allowed.
- ECUS At customer site

Sales Office Address, Change and Assignment
SAP Functional ==> SD In SAP
Where to change the ADRNR field for a particular sales office?
SPRO --> Enterprise Structure --> Definition --> Sales & Distribution --> Sales Office
--> Define Sales Office. Here go to the address & change the address & the new address
will reflect in the output.
Table in which sales office data is stored.
In which table name address of the sales office (SD ) is stored. Also tell in which
table, description of the sales office is stored.
table TVBUR-vkbur is the sales office
table tvbur it contains a field called address number. ADRNR
take that field(ADRNR) and compare with table ADRC-ADRNR.
in table ADRC you will find name, description, address and all other data.
table TVKBT -- description of sales office.
Assignment of Single sales office to multiple sales organizations.
We have a scenario where we need to Assign single sales office to multiple sales
organizations in CRM. When I am trying to assign sales office to more than one
sales organization 1st assignment between Sales office and Sales Org is getting
deleted, and only the 2nd assignment is available.
At sales office level in Function tab, it is showing only the assigned sales
Organization (only one sales org), how to assign one more sales org to this sales
office here.
The assignments are on the lower node. Which means you will go to Sales office, go to
function TAB and assign multiple sales organizations there.
In the change form click New entry and assign the new sales organization and
distribution channela and division combination.
You can assign as many combinations as needed here.

1. There are 2 version in CRM Org Model.
a) SBIV (Standard Backend Integration Version)
b) EBIV (Enhanced Backend Integration Version)
2. EBIV is used to handle multiple assignments in CRM system.
3. As you know we have 3 Org Units as far as Sales is concerned i.e. Sales Org, Sales
Office, Sales Group.
4. In R/3 there is a standard way to maintain multiple assignments among these org units.
Ex: Sales Group 'X' works (assigned) for 2 Sales Offices 'North' and 'South'
simultaneously.
5. But in CRM this assignment is not as common as in R/3 and is not supported thru
SBIV.
6. If you would like to have these multiple assignments made in R/3 available in CRM as
well you may want to go thru EBIV.
7. Once you run EBIV you cannot go back to SBIV.
8. In EBIV divisions and distribution channels can only be assigned to
sales units (sales organizations, sales offices, and sales groups). If
they are assigned to any other neutral Org Units (Org Units without any
Org Attributes), those assignments would be deleted once you shift from
SBIV to EBIV.
What are the steps to create a sales order?
To create a standard sales order, proceed as follows:
In the initial screen, choose Logistics - Sales and distribution - Sales. Choose Order -
Create (VA01).
Enter the order type and, if necessary, the organizational data.
The values for sales organization, for distribution channel and the division are usually
proposed from user-defined parameters. Entries for the sales office and the sales group
are optional.

The sales areas (sales organization, distribution channel, division) are derived from the
sold-to or ship-to parties. This means that you do not have to enter the sales area when
you create a sales document.
If you do not specify a sales area in the initial screen, the system uses the sold-to or ship-
to parties, which you entered in the overview screen, to derive the sales area.
If there are several sales areas for that particular sold-to or ship-to party, you can choose
the right sales area in the following dialog box.
The system then copies the selected sales area into the entry screen. Choose Enter.
Enter the following data:
- Sold-to party or ship-to party
If you only enter a ship-to party, the system uses this to determine the sold-to party and if
necessary, the sales area. If there are several sold-to parties or sales areas for one ship-to
party, a dialog box appears where you can choose the one you require.
An error message appears in the status bar to inform you if the system is not able to
determine a sold-to party. If you enter a sold-to party that is also a unique ship-to party,
the system automatically copies it as such and informs you in the status bar.
- Customer purchase order number
- Material numbers
- Order quantities for the materials
- Choose Enter.
If, for example, you defined several unloading points or several ship-to parties in the
customer master record of the sold-to party, the system displays the alternatives in a
dialog box. The system can display alternatives for any or all of the following data: –
- Unloading point
- Ship-to party
- Payer
- Bill-to party
Select the valid data from these proposals by positioning the cursor on the line and
choosing Choose.
As soon as you have selected this data, the material data that you have entered is
displayed.
If the system carries out an availability check and finds that there is insufficient stock for
an order item to be delivered on the requested date, it displays a screen on which you can
choose between several delivery proposals. You can find more information about this in

Reactions to the Availability Check in Sales Documents. If you want to enter further data
for the header or items, choose the corresponding menu entry. If you want to change data
for the items, select the items before you choose a menu entry. Enter all necessary data.
Save your document.
Duplicate customer purchase order
If you are facing a problem with duplicate customer purchase order as your company
does not allowed a same customer purchase order with the same sales order type.
You can activated the check for duplicate purchase order with "VOV8".
In the General Control Section, look for the field Check Purchase Order No and put
Default First Date is not Today
When end user created a new sales order with VA01, default First Date wasn't
today, why?
Note:
1. Before today, default First Date was always today.
2. Nobody change system configuration.
Although you mention that nobody change the system configuration, it is very unlikely
that the system will mis-behaved after one day.
Usually, after checking, you will find that someone have actually change the
configuration as it could not be a software bug since you have been using it for quite
sometime without any problems.
The date is control by each Sales Order Type for each Sales Document type whether is it
a
- OR - Standard Order,
- RE - Returns etc.
Verify the Sales order type configuration with the following path:
IMG: Sales and Distribution --> Sales --> Sales Docs --> Sales Doc Hdr --> Define Sales
Doc Types (transaction vov8) will let you control this by sales document type.

There is one field (Lead time in days) which "specify the number of days after the current
date that the proposal for the requested delivery date in the sales document should be".
This should be blank if you want the system to propose current day for delivery date.
SAP SD User Ticket:
Confirm quantity date is next day. I have created a sales order for 6 Tons.I have a
stock of 10 Tons which is not reserved for any Sales order. I mean it is unrestricted
stock. After creating sales order system should show as Doc date for confirming
quantity for dispatch but it is showing the next day in the schedule line. What could
be the reason?
The reason could be there should be processing times configured in the system
like..pick/pack times, transit time. Please check the shipping point and also the route for
different lead times.
The other possibility could be holidays.
First check what the requested delivery date you have put in the order. Next check the
lead times, for that you can go to the schedule line of the item and click on the
Procurement tab.
Check in OVLZ ---> In Pick/pack time wrkdys, any value is maintained there. For
example, if 5 is given in this field, even if stock is available on the same day of order
creation, system will allow to do PGI only after 5 days from the date of order created.
Also go to VOV8, select your sale order type and check the Field "Lead Time in Days".
I'm using service material in my sales order and I need the schedule line to confirm
the quantity always in the actual day (not depending on the delivery date).
T. Code: VOV8
Select your Sales Doc. type and Double-Click.
In Tab: Shipping,
Check Box: Immediate Delivery (press F1 to read more about this functionality).
Note: There are few more settings that you may check:
1. T. Code: OVLZ

Field: Pick/pack time wrkdys whether you have maintained any value. It should have
been blank
2. T. Code: VOV8
Check how many days mentioned in Lead time in Days. If it is mentioned any days,
remove it.
3. T. Code: OVZ9
Checked the Box: Check without RLT .
4. Check in material master MRP2 view how many days are maintained for the fields In-
House production and GR Processing Time.
Auto proposed all the dates when creating Sales Order
How can I make the system auto create all the Sales Order date during creation?
Each Sales Order can have different date proposal settings.
Follows this step to set the default Sales Order Type proposal date:
- Goto VOV8, double click on sales order type.
- Look and tick the fields Propose delivery date and Propose PO date.
After making the necessary IMG changes, you need to input the Delivery Plant field for
each Materials that you want the system to propose the default date.
To change the Materials field Delivery Plant:
Goto MM02, Select the View Sales: Sales Org. Data 1 and fill in the Delivery Plant.
Testing:
Now, try creating a new sales order for the material and SAP will auto proposed all the
dates in the sales order.
Define whether the Material can be used at which Sales and Distribution
process

Here you define how the system responds when entering a sales and distribution
document
with this material in the differenet Sales and Distribution Process Flow..
You can use the material status, for example, to prevent orders from being entered for
parts to be discontinued.
OR
To temporary block the creation of Sales Order for a certain materials.
Set the material status parameters in transaction SM30, Table Views V_TVMS.
Click Maintain and double click into the Materials Status code.
You can set three types of reponse for each Sales and Distribution process :-
1. no dialog
2. warning when entering the document
3. error message (that is, the sales and distribution document cannot be entered on
the basis of the material status)
Assign a Cost Center manually in a Sales Order
(VBAK-KOSTL)
The Cost Center Determination settings is in OVF3 - but there are some cases where the
Cost Center must be exceptionally changed.
If the document category for order type in IMG VOV8 is defined to be "I" which belong
to order type FD - Deliv.Free of Charge, then the field cost center is active for input
during transaction VA01.
Alternatively, you can specify an order reason and assign a cost center to an order
reason.
However the standard SAP works only at the header level though, so it would not work if
cost center is needed on the line item.
The cost center are assign for such business transactions as :

- Free deliveries
- Returns
- Deliveries of advertising materials
You can also make cost center allocation dependent on the order reason, for example:
Order reason: Damage in transit
Order reason: Free sample
Both the IMG settings are done in transaction OVF3, either with/without the order
reason.
Sales and Distribution - Transfer of
Requirements
The MRP department is informed about the quantities and deadlines by
which incoming orders
should be delivered. The system checks the availability of the goods
based on the requested
delivery date of the customer and creates MRP records which contain all
necessary information
for passing on to planning. It ensures that the goods are available in
time for the delivery.
Materials planning transfers the reported requirements and creates
orders or purchase
requisitions from them etc.
For controlling transfer of requirements, you have to carry out the
following steps:
1. Each requirement type has to be allocated to one requirement class
only.
2. The transfer of requirements must be switched on at requirements
class level, the sales
documents at schedule line level.
3. You must define a check group. It is possible to have this check
group proposed for the
initial creation of a material master record.
4. Note that a plant must exist for transfer of requirements to be
carried out at document
item level.
OVZG - Requirement class
It specifies the following points:
- whether an availability check and a transfer of requirements is
carried out for a
transaction (for sales documents, fine tuning using the schedule line
category is possible),

- whether the requirements are relevant for MRP,
- the allocation indicator from the sales view which controls the
settlement of customer
requirements with requirements
- whether an item is to be settled to an auxiliary account assignment,
- the settlement profile,
- the results analysis key.
(Use transaction SM30 for V_* configuration)
OVZH - Requirements type
V_TVEPZ_V - Assignment of requirement type to Transaction
V_TVEP_V - Schedule line category
OVZ2 - Define Checking Group
V_TMVFU - Define the checking group that the system proposes when you
create a new material
master record. You can overwrite the default value for the
checking group in the
material master record.
Explain transfer of requirement? How it works and how to configure?
It specifies the following points:
1. Whether an availability check and a transfer of requirements is carried out for a
transaction (for sales documents, fine tuning using the schedule line category is possible),
2. Whether the requirements are relevant for MRP,
3. The allocation indicator from the sales view which controls the settlement of customer
requirements with requirements,
4. Whether an item is to be settled to an auxiliary account assignment,
5. The settlement profile,
6. The results analysis key.
When a sales order is raised, then the system check for availability of goods. If the
availability of goods is not there, then the system creates a TOR for the supply of goods
to PP. Then PP can do procure or produce the goods. This can be configured by creating
requirement class and requirement type and in the corresponding schedule line category
requirement had to be checked.
The MRP department is informed about the quantities and deadlines by which incoming
orders should be delivered. The system checks the availability of the goods based on the

requested delivery date of the customer and creates MRP records which contain all
necessary information for passing on to planning. It ensures that the goods are available
in time for the delivery.
Materials planning transfers the reported requirements and creates orders or purchase
requisitions from them etc.
The following sections on the transfer of requirements describe how to control the
transfer of requirements.
The transfer of requirements is basically dependent upon the following factors:
- requirements type
- requirement class
- check group
- schedule line category
The transfer of requirements is controlled globally using the requirements class which is
derived from the requirements type for all sales document types.
For the sales document types, fine tuning is also possible at schedule line level. This fine
tuning is described in the section "Defining the procedure for each schedule line
category".
Note that the requirements classes are also used in production so you should coordinate
any changes to the requirements classes with production. The requirements type and,
eventually, requirements class are determined in the strategy group so all changes made
there should also be coordinated with production.
For performing transfer of requirements, you have to carry out the following steps:
1. Each requirement type has to be allocated to one requirement class only.
2. The transfer of requirements must be switched on at requirements class level, the sales
documents at schedule line level.
3. You must define a check group. It is possible to have this check group proposed for the
initial creation of a material master record.
4. Note that a plant must exist for transfer of requirements to be carried out at document
item level.

Requirements transferred to planning are further processed in the module MM. You must,
therefore, coordinate the transfer of requirements with the module MM.
Define Tax Determination Rules
You specify the valid tax types in transaction OVK1. More than one tax type can be
defined for a country by defining the sequence.
The SAP System determines the taxes automatically within pricing.
In the standard SAP R/3 System, the elements of tax calculation are predefined (for
example, tax condition type "MWST" for taxes on sales and purchases).
Assign the plant for Tax Determination in OX10, using the country key, the SAP System
recognizes which tax type is valid for a plant and thus which taxes are relevant when
creating an SD document.
Define the Customer Taxes in OVK3, you will maintain the tax code in Customer
Master.
Define the Material Taxes in OVK4, which will then be maintain in Material Master.
For example :-
MWST GST 0 Tax Exempt
MWST GST 1 Liable for Taxes
Now, you define the Tax Determination in VK12.
VK12 - Domestic Taxes/Export Taxes
Condition Type MWST
Customer Taxes Material Taxes Rate Taxes
0 0 0 %
0 1 0 %
1 0 0 %
1 1 9 %
In this example, if both the Customer Master and Material Master Tax code is 1, Tax will
be included when you create the Sales Order.
Tax Code in Customer Master / Sales Order

How can we maintain the Tax Code (Tax code - which we maintain in MWST
Condtion Records) in Customer Master or in Sales Order?
There are few points which I would like to remind you:
1) MWST is a tax condition which is applied to customer to whom we are selling. The
rate of tax is depend on various parameteres, whether is fully liable for tax or expemted
(in case of Defence Customer)
2) There are few parameteres which we apply tax condition. Whether customer is tax
liable? Whether material is tax exempted?
For example, if you are selling a goods which are free for tax to any customer, put the
Tax Indicator (at MMR as '0'). If your
material is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable
for tax at all (like the case of Indian
Defence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable.
3) Now, at VK11 you need to mainatain your pricning conditions with all the
combinations like:
1 0
1 1
0 1
0 0
4) While maintaining your Material Master Records or Cusotmer Master Records, you
must identify, which are tax liable and which are tax exempeted.
5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must
retrieve a Tax condition record from SAP database only and not entered Manually.
Accordingly, at V/06, the MWST condition Defintions, the field for 'Manual Entries', it
would be marked as - D (Not possible to process Manually).
Due to this setting, normally, you cannot maintain Condition tax code during sales order
processing. And in Cusotmer Master, you can only maintain Tax Indicator and not Tax
Code.
6) In case your client insists for Manual entry of Tax code during Sales Order processing,
you can change the field at point 5) above to C-Manual entry is priority instead of D.
Taxation Explain with an example
I'm assuming that, the country is India and based on its requirement:

Sales tax is a state government revenue. There are two types of sales taxes, Local sales
tax & central sales tax. Local sales tax is intra state whereas CST is inter state.
Example of LST : Point of sale i.e. delivering plant & ship to party are within the same
state. The rates are defined by the respective state governments.
Example of CST : The Delivering plant & Ship to party geographic locations are 2
different states. At the point of sales from one state, the ST goes to that state govt. &
consignment is despatched to the Ship to party. Once that consignment is received at the
ship to party state, sales tax will be levied once the sales is registered there. For this case,
the LST that is applicable by the Ship to party further will not be applicable in all
probability to be captured in SAP.
Stock transfer : This does not attract any sales tax. The consignment is transferred from
one D plant to another D plant irrespective of inter/intra state sales. The invoice that is
accompanied with the consignment thus shall not have any final value. It's a zero value
invoice, but the basic prices needed to be mentioned.
The selling organisations normally needs to register with the sales tax authority of the
respective state to have a warehouse or D plant to avoid the double taxation for their
dealers/distributors.
Now, the pricing procedure that is there in 4.7 is Factory sale with formula-JFACT, in
which the CST condition type is JIN1 & the LST is probably JIN2. There may be
surcharge cond types as well which will calculate the amount on either JIN1 or JIN2.
For config :
1.SPRO > S&D > Basic fn. > Pricing > Pricing control > Define & assign Pric. procedure
> Maintain Pric proc.
2. The tax rates are normally driven from the Tax classification of Customer & Material
access. To do this config, S&D >Basic fn. > Taxes. You need to include the condition
type for country IN in 'Define tax determin rule'.
3. Same path : But go to Tax relevancy of master records where you configure the
condition type & options of rates that will flow to these masters. One needs to understand
here properly as u need to have unique combinations for picking the sales tax rates. I will
try to demonstrate the smallest example. Let's say, the LST rates are 2%,4% & 0%. I will
have two options for material master here. 1 for taxable & 2 for not taxable.
For customer master, I will have 1-LST 2%, 2-LST4% & 3-LST0%. When I create
master records for LST thru VK11 for JIN2, I will chose the access where the
combinations of customer & material tax classifications are available. If this access does
not exist create it under an access sequence. But normally this is standard. The condition
records will look like,

Cust-Tax classi. Material tax claasi. Rate Tax code
1 1 2% A1
2 1 4% A1
3 1 0% A1
Remember, rates are flown from the tax codes. Tax codes can be created thru T code
FTXP. This is normally a FI job
SAP SD: Scheduling Agreement Vs Contract
A schedule agreement contains details of a delivery schedule but a contract just contains
quantity and price information and no details of specific delivery dates
What's the difference between schedulling agreement with normal order?
What's the condition for us to choose schedule line or order?
Both of them contains schedule line, price, quantity.
There are a couple major differences:
(1) - Schedule agreements allow you to have 2 different sets of schedule lines (VBEP-
ABART). Standard SAP you should have two sets of tabs - of schedule lines. One
Forecast & the other JIT. Forecast forwards the schedule lines to planning (seen in
MD04) and JIT passes them to shipping (VL10). They can be identical or different.
Typically these are used for component supplier customers (namely Automotive). The
customer will provide you 4-10 weekly buckets (usually a
Monday date) of future forecast qtys. Also send you 1-2 weeks of individual FIRM ship
dates - which are entered on the JIT. It comes down to the customer not knowing exactly
what they need next week, but they don't want to suprise you with a large order qty,
where your lead times are 5+ days. The forecasted qtys they sent last week should
account for this.
(2) Cumulative Quantities are tracked and influence how the schedule agreement passes
requirements to both forecasting and shipping. These qtys are sometimes requested by the
customer on ASNs. Cumulative qtys reset at year end unless you've got a customer
calendar or you've modified standard SAP userexits to not reset.
Schedule agreements are very nice when the customer sends EDI data (830s = forecast or
862s = JITs). Outside of that they can really cause trouble regarding daily maintenance,
missing requirements, cum qty corrections, year end processing, etc.
One alternative would be to use customer independent requirements - entering the
weekly, monthly forecasting qtys and entering standard sales orders (with or without
multiple schedule lines) to represent the true firm qtys.

Sales Order Mass Change
I am a SAP SD consultant and recently faced with two new terms, mass order
change and ALV , I also need to know about the transaction code.
There is transaction MASS which can be used to carry out mass changes in the sales
order and other objects.
Mass Maintenance: (Use to change multiple fields in multiple documents at the same
time). I have done mass change for customers; and orders should work the same way too.
1) Try t-code [MASS] and select sales orders & execute
2) Choose the table or tables for your selection criteria and also for fields you want to
change.
Then execute. (suppose your selection criteria fields are from "sales order header data"
table and the field you want to change, is in "item data" table)
3) Put in the sales documents(21000000, 21000001) you want to change and also the
items(10) you want to change.
- click on " choose selection fields" button
- From the Pool, move the fields you want to the "select fields" using arrows.
4)From mass maintenace menu, click on "Enter new field values"
-click on "sales order item data" tab and choose the field you want to change.
(for example. I want to change plant for item 10)
-enter the new value (of the plant to be)
-click on "Adopt" and execute
5)In "sales order item data" tab, you see the new value of the plant you entered at the top
and the old values of item 10 are below.
-click on "change field values" button. you see all the old values are changed to new
values.
-save
Note: it will take some time depending on how many records you have.
Check: Go to [SM37] and see the status of the job you are running and once finished,
export the spool file to a spreadsheet.
Before you do mass maintenance, go to the particular table in [se16] and get the results.
Then do the mass maintenance and compare the results with this one. If they match, then
you are good to go.
Note: If you have any user exits that affect the results, ask them to deactivate the
MODCHECKS still you are done with mass maintenance & activate them again.

Is there a way to change the billing date on a ton of sales orders with same old
billing date to a same new billing date?
This can be done using the mass transaction:
Transaction: MASS
Object Type: BUS2032
Tables: SD Document: Business item data
Sel Field: Billing Date (MASSSDHE and MASSSDPO)
- Or you can just select by document numbers (May be more efficient)
Execute - List will be provide for changes
Sel Chg Fld: Billing Date
Set new billing date value in the New Values field
Click on lower billing date column
Click on Carry out a Mass Change button
Click on Save button
Suggestion is to test this on a few orders in your development system to get a feel on how
this works before applying this to any production data. MASS is a very powerful tool.
I have 100000 sales orders whith an incorrect price and I would like to do a massive
condition update with pricing type "B" (Carry out new pricing). Is there a
transaction or program for this?
Go to VA05 execute the report. Select all sales orders you want to update the price, Go to
the Menu EDIT --> MASS Change ---> New Pricing. System will display all the re-
pricing options. Select B. It will re-price all the sales orders.
You can try for one or two order initially check the results and if it is OK, then you can
do for others
Release strategy for Sales order
Is it possible to have release strategy for sales order?
Satish C Jha
As such SAP standard does not provide release strategy for sales orders similar to
purchase orders. However this requirement of your can be satisfied through
authorisation profiles; what I mean to say is that the sale order to be kept incomplete by
the person who does not have the required authorisation & the person with proper
authorisation will complete
it for further processing. This is only one way of meeting your requirement.
Balraj G Saigal

In order to emulate a release strategy similar to purchase orders you can use the status
profile in sales documents (BS02). IMG-Sales and distribution-Sales-Sales documents-
Define and assign status profile.
How to do rebate processing
Rebates Processs in SAP is divided into three components
1) Configuring Rebates
2) Setting Up Rebates
3) Managing rebate agreeeements and payments
Pre-requsiistes- Check the following:
1.The payer partner needs toi have the rebate field checked in the customer master on the
sales area-billing doc tab.
2.The Billing type must be marked as relevant for rebates.
3.The Sales Organisation must be marked as relevant for rebates.
Condition Technique :
Rebates, use the condition technique, but distinguish themselves from pricing in applying
to transactions over time, versus on a transaction basis. Rebates have their wn field
catalog and their own condition table naming convention.So you could have two
condition table "001" one for pricing and one for rebates, which could have different key
fields. You need to use the technical names A001 For pricing and KOTe001 for rebates
when you use the query type using transaction SE 16..
Use create access sequence (AS). Enter 1 in field category for rebate specific. AS after
going thru the right path of maintaining access sequence for rebates.
The big difference between the rebate and the pricing access sequence is that there is no
exclsuion flag available for rebate related AS. This means multiple tables for an access
sequence can be aplied at the same time.
Rebate related condition types are identified by codnition class -C.
After defining and creating condition types for rebated include them in the pricing
proceedure. The requirement should be 24 here which implies that the accruals are
calculated on the basis of invoice/bill.
The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is
calculated. Also, remove the requiremnt 24, if u want to see reabtes at order time.
Now payment of rebates:
Payments can be maunal or in full settlement. When you do manual payments, it defines
how much can be paid out during a partial settlemetn. You use partial settlement only

when rebate agreement is defined for a full year but the paoyouts are supposed to happen
on a monthly, quarterly or anyother specified period.
These accurals are based on sales volume and when they are posted billing is created int
eh follwoing manner. Provision for accruals is debited and Sales revenue is credited.
When rebate credit memo is created
Customer account/ is debited and
Accrual provision account is credited.
Also, please note that when rebates are created without dependent ona material but on
customer/material you need to refer to a material for settlement.
With Compliment: Srini
I have this same problem found in:
http://www.sap-img.com/sap-sd/rebate-process-with-ref-to-so.htm
However, can somebody explain it as I have problem in understanding the link.
What exactly do you wish to know in Rebates? The total outline of the Rebate process or
each and every step in the SAP system?
First of all rebates are more or less discounts which are offered to customers. The rebates
are based on the volume of the business the customer does with you within a specified
time. for eg if the customer agrees for Rs.1 Crore worth of business with u in 1 year, then
you activate your rebate porocess. if at the end of the year the customer DOES achieve
the target u offer him say 2/3/4 % whatever is decided. The rebates are passed on to the
customer in the form of Credit notes.
The rebate can be given to the customer at one time or in installments also.
This is broadly the outline of the rebate process.
R.Sreeram
Note : I recomend you to study the theory part of why rebate and why not a discount.
This will help you understand better.
May be I can help you with rebate process.(IN -IMG)
1. define a rebate agreement type
2. define a condition type group
3. define a condition type and place this condition
Type in the pricing procedure.(REQUIREMENT=24)
ALSO IN THE PROCEDURE- ACCRUAL KEY = ERU
YOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES.

Once you have defined all the 3 and assignment starts.
Assign the agreement type to the condition type group
Assign the cond type group to the condition type.
Condition technique is also used in rebates.
REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND
FOR THE BILLING DOCUMENT.
After having done this please proceed to maintain the condition record for the rebates
(transaction code-vbo1)
Note: if you maintain the requirement coloumn with the requirement as 24 - the rebate
will be affected in the billing document and if you dont give the requirement as 24 your
rebate will be affected in the sales order.
The rebate process is completed when you have created a credit memo to the customer.
The document type for the partial settlement is R3.
Please make sure you open two screens SO THAT YOU CAN COMPARE THE NEW
ENTRIES WHAT EVER YOU'RE DEFINING WITH THAT OF THE STANDARDS or
first you try with the standard condition type boo1, boo2
boo3 boo4.
AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION
ORDER , DELIVERY AND BILLING.
GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE
THE ACCOUNT PARTIALLY.
I hope this will be of any help to you.
Praveen
In a simple way,
1. First you need to create a Rebate agreement.
2. Create condition record for rebate giving the rebate rate and accrual rate.
3. when the rebate relevent billing doc is generated, the rebate and accruals are
determined and posted in a seperate GL account as a noted item - amount to be settled.
Also it gets copied in the rebate agreement.
4. create settlement run using credit memo request and then credit memo to settle this
amount with the customer.
This is what the link says.

Rebate Process with Ref. to SO
If I need to make a rebate for a customer what is the process involved.
I am providing some info on rebates which I know.
Rebate agreemnts is based on agreement types.Conditon records which are created like
B001 and B002 are linked to the rebate agreeements specifying the rebate rate + the
accrual rates.condition records specify the rebate rate and the accrual rates.
Consider an example..
You decided to give a rebate of 3% to a customer whose sales vol is $1000 for a
particular SO
Then the rebate value is $30..
Now when you make the rebate settlement by doiing the Credit memo and you decide to
pay $27, then the accounting will be generated saying 27$ paid towards rebate and 3$ is
the accrual which you owe to the customer
Procedure:
Rebate agreement: Transaction code: VB01
When you go to VB01, choose agreement type 0002 and then in conditions give
Material rebate
1 20
20 30
Now create a sales order with a material say M-11 for SOrg 1000 12 00 with QTY 6
Now check VB03 and see rebate agreemtent it will say Accruals 120 and payments 0
since your rebate is not settled still.
Rebate setllement
Go to VB02 enter ur sales deal no, and change the agreemetn status to B then enter
Shift+F12 and enter the amount to be paid for example u say $80
Then check in rebate payments rebate doc and partial setllemetn since you have not paid
in full.
View the credit memo request
Remove the Billing bloock Go to VA01 and put order type G2 ,,,go to create with ref and
enter ur Sales order no,,,save the doc now...

Then go to VF01 and enter the credit memo reqst no generated...save the doc no and go
to VF02 and say release to accounting
Now the final settlement will be this way
Accruals:120
Accrual reversed:80
Rebate pay:80
Amount payable:40
So the balance 40 is still the accrual
This is an example how a rebate will be processed with ref to a SO with an example.
SAP SD Tips by: Priyam
How to do a rebate agreement for a specific customers
with settings details?
1. Create a condition by copying a a standard condition like BO03 in V/06
2. Assign this condition in the std pricing procedure with acct key as ERB and accural
key as ERU - V/08
3.Create a Rebate Agreement in VBO1 (It is O = Owl and not zero). No will be
generated
choose 003 - Customer rebates, enter the customer code, the validity and check for the
status shld be in Open, click on the conditions enter the percentage and accrual amount.
You also can have scales in this. Also you need to maintain the material for the
settlement
4. Create a sales order for that customer and check the rebate agreement.
5. You can see the rebate condition in the invoice only.
6. Once you have posted the invoices, then go to rebate agrrement no. clicl on verficayion
and it will show the order details.
7. For settlement change the status of the rebate to B - release for the settlement.
8. Credit memo request will b generated copy the no. and go to VA02, remove the blocks
if any and create an invoice (credit memo).this will show u the accrual amount.
9. In both the invoice and the credit memo check the posting - accounting document it
will show u the accrual as negative.
10. Again go to rebate aggreement and check the status it will show you D - Final
settlement of agreement already carried out
Consignment Sales Process in SAP
The consignment process in SAP standard consist of four small processes:

Consignment fillup (send materials to customer consignment).
Here you have a consignment fillup order and a consignment fillup delivery.
Consignment issue (issue materials from customer consignment to the customer).
Here you have a consignment issue order, consignment issue delivery and a consignment
issue invoice. (the flow is very similar to a normal OR flow, but the materials are issued
from the consignment stock instead of plant stock unrestricted).
Consignment return (return materials from customer ownership to customer
consignment).
Here you have a consignment return order, consignment return delivery and a
consignment return invoice. (the flow is very similar to a normal RE flow, but the
materials are returned to the consignment stock instead of plant stock returns).
Consignment pickup (pickup consignment stock and move it to plant stock).
Here you have a consignment pickup order and a consignment pickup delivery.
Note that in consignment fillup and consignment pickup there are no invoices since there
is no change of ownership for the materials.
How to perform a consignment order?
In consignment orders you are allowing the stock to sit in your customer location. Once
he informs that he used the stock you will invoice him. If he returns the stock you will
accept the stock to take it back.
It is defined in 4 steps.
1. Consignment fill up:
Sales document type is KB
Item category KBN
shedule line category E1
In this step, you are not invoicing the customer. document flow is sales order ---- delivery
item category. It will not be relevent for billing and pricing because you are not charging
money for these goods in this step.
In schedule line category, you will set movement type 631 & set for availability check
and TOR.
2. Consignment Issue.
Once the customer informed you that he used all the goods or partial goods then you will
create consignment issue for used goods.

Sales document: KE
Item category: KEN
shedule line category: C0 or C1
Here you are invoicing the customer(because he used the goods). you are assigning the
delivery documnt and billing document to the sales document.
In item category, you are setting relevent for billing, pricing, special stock.
In schedule line category, your setting is 633 movement type, relevent for availability
check & TOR.
3. Consignment Return:
Customer found that some goods are damaged or he not able to sold the goods he want to
send it back. that you are creating this document.
Sales document type: KR
Item category: KRN
Shedule line category: D0
You will assign delivery document and billing to sales document. you will create return
order, return delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.
4. Consignment Pick up:
Even if you create the consignment return the goods are not come to direct to your plant.
For that you need to create consignment pick up. here the owner ship is not changing so
you do not need to create billing.
Assign retrun delivery to sales document type.
Sales document: KA
Item category: KAN
schedule line category: F0 & F1
Your setting item category relevent for returns. any shedule line category relevent for 632
movement type, MRP, availability check, delivery.
Now you check your plant stock. Stock will increase.
Issue free goods to selected Customers
Client wants to issue free goods to selected customers after the said customer buys a
specified quantity of a good during the festive season starting 02 December to mid

January. for example customer A buys 34 cartons of Corn Ice-cream, we offer him
12 free corns. this should then reflect as cost in our accounts. the rest of the system
is already up and running and should not be inconvinienced. How do I set it up?
1.Run trans. VBN2 to first create master record for free goods as follows:
Enter following information in selection screen:
- Free goods type: NA00
- Sales org, distribution channel, customer # and execute.
Now in next screen create the record as follows:
- First select the exclusive button and verify that you are in exclusive view.
(that is if you want exclusive)
- Material#, Min qty - Say 34 cartons. (check in what units you want to manage)
From: 34 cartons
unit of measure:
Free goods: 12 Pcs
Unit of measure: Pcs
Calcualtion type: 1 or try the other options
Deliver control: Blank or any of the other options suitable to you.
Now save and exit.
Now run VA01 for 34 cartons and press enter. The system will automatically propose the
free goods
item at no additional charge. Try higher order qtys and see if the free goods qty are
scaling up.
If not adjust the calculation parameters in the master record screen
It should be transaction VBN1. Sorry for the error.
VBN2 is to change the record. VBN1 creates it.
Kris J
If you want to give free goods to some of the customers than
1. create a customer group say 99 for FREE GOODS
In Free Goods Menu:
2. add a feild catalog for CUSTOMER GROUP
3. create a condition table (free goods) say 555 only for customer group
4. create a sequence say FREE with condition table 555

5. create a condition type say FREE with
6. maintain pricing procedure say ZFREE with condition type FREE
Now assign:
7. Active Free goods Determination or Assign with your sales organisation this procedure
ZFREE
8. Create free goods determination with transaction code /nvbn1 for FREE with Key
Csuomer Group
99 for exclusive
Give customer Group say 99 and from 34 to 34 free 12
Supressing Fields in Sale Order
To make optional / mandatory you can use in IMG - S&D-> Basic > Functions-> Log of
incomplete Procedures => select the fields > from the tables and the system will check
for them (OVA2/VUA2)
To make a filed entry enabled or grey (non-entry allowed):
User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can
be edited together during a modification in ABAP.
If a field has no field name, it cannot be allocated to a group. The usage of the field
groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed
information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be
made, you must make them in this user exit. This FORM routine is called up by the
module FELDAUSWAHL.

With Compliments by: Taner Yuksel
Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our
company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in
MV45AFZZ.
Below is the sample code
IF SCREEN-NAME = 'VBKD-ABSSC'.
AUTHORITY-CHECK OBJECT 'ZMV45AFZZ' ID 'SCRFNAME' FIELD SCREEN-
NAME.
IF sy-subrc = 0.
SCREEN-INPUT = 1.
else.
SCREEN-INPUT = 0.
ENDIF.
endif.
You place the authority check object in authorization profile in the role of the users, who
should have access to the field (in this case it is VBKD-ABSSC), and there assign the
corresponding fields that are to be accessed via this userexit.
Some Light on Batch Determination
On batch determination, the whole process, how it is determined automatically in
the order.
A1) Normaly we use batch determination at delivery level, because at the time of order
material may or may not be created.for this material should be configured with batch and
batch determination should be checked in sales views of material.
A2) Batch Determination during order Creation.
For this you need to maintain a Classes d for you Material. Depending on the
Manufacturing process you can define the characteristics for your material.
Ex: Purity for Medicines, Resistance for Electric Items.
You need to create a class (You might have to create a new class type) which
incorporates the characteristic.

First Create the Characteristic Using Ct04 and then using Cl02 create the Class including
this characteristic.
Then in your material master Classification View Enter this class.
Then Create a Batch for the particular plant and Stor Loc using MSC1N.Give the value of
the characteristics in this batch.
Then go to SPRO ->Logistics General ->Batch Management and maintain the Condition
Technique (Procedure, Strategy Types and assignment to sales docs etc).
Then Create the Batch Determination Record using VCH1.
Difference between Item Proposal and Material
Determination
What is the difference between the item proposal and material determination
product proposal?
Item proposal and product proposal are the same.
Item proposal is the list of materials and order quantities that can be copied into the sales
order from the customer master data.
We use VA51 to create the item proposal. Here we get a number.This number is then
linked to the customer master data in the sales view. This is very commonly used.
Material determination is very closely related to item proposal /product proposal and is
used to swap one material for another in the sales order using the condition technique. I
have not seen Material determination procedures used in the projects I have worked.
SAP Tips by: Prashanth Harish
Item Proposal or Product proposal:
"Item proposal is same as product proposal & SAP uses the two terms interchangeably.
"An item proposal is a list of materials and order quantities that can be copied into the
sales order. Items can also be selected from a list and copied into a sales order."
1) Use transaction [VOV8] to configure the document type ("MS" for product proposal).
2) Use transaction [VA51] to create a proposal.
3) Enter the item proposal on the sales area data (sales tab) of the customer master record.

4) In [VA01] to create a sales order, Select Edit & propose items."
Material determination:
"Material determination uses the condition technique to swap one material for another
when certain conditions apply. Material
determination is triggered by the material entered in the line item of the sales order.
Use transaction [VB11] to create a material determination condition record. And [OV12]
for configuration of material determination.
Material determination is useful when old product is becoming obsolete or a new product
is released by the company at specific date."
Steps for SD Variant Configuration
Some light on Variant Configuration in Detail.
The procedure is as follows:
• Create a Material - KMAT type with Item category (002)
• Create Charateristics in CT04 - Zbike, where in values mention the Color of the
bile like Red, Blue etc
• Create another characteristics in CT04 - ZPrice, where directly go the additional
data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it
will ask for)
• Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in
characteristics tab page.
• Then go to CU41 Configuration profile select the material and enter the
description click on the class assignment ie assign Zbikclass.
• Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other
Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and
save
• Now go back go to extras - Other Dependencies - assignments and assign
relationship ( by default it will come just save)
• Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure
enter in front of 10 write - $self.ZPrice='Blue' and save
• Now go back go to extras - Other Dependencies - assignments and assign
relationship ( by default it will come just save)
• Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure)
- enter variant Red and Blue give the rates accordingly and create the sales
order. *-- Shaik Zaheeruddin
Tell me about variant configaration?
What are the type of questions we can expect in that?

Variant configuration is used where you have a configurable material like computer
(made up of components like processor, monitor, keyboard, mouse etc). These
components are called as characteristics in variant config. Again this will be having
values like processor can be either P4 or P3, monitor can be 15" or 17" etc.
Based on the values selected the variant pricing will happen using the condition type
VA00.
Possible questions you can expect are:
- What is variant configuration?
- What is characteristic?
- What is value?
- What is class?
- What is configuration profile?
- What is dependency and what are the types?
- What is a variant table?
- And the transaction codes for the above.
Number Ranges In Sales Order
This is regarding number ranges defining and assigning tips which you can follow as
below:
Whenever there is a new Sales Org being created, you will be required to maintain
Number Ranges for Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be
maintained externally also if you customize it accordingly.
In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution-->Sales--
>Sales Document Header-->Define Number Ranges for Sales Documents.
Here you provide the system a specific Number range as follows:
Number range Key +Start Number range+ End Number Range+Current Number
For Example: If you want to propose the following Number Range
*1 9000076000 9000076999 0

The Current Number field will be kept zero as you are proposing new number range and
no sales documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should
ensure that it should not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End
Series) is there in the system already, the system will throw a message that Interval
already already exists. So choose a key that is unique, and which is not there in the
system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z
and in any order. For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range
you have already proposed as above.
The Assigning Part is done as follows:
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales
Document type in V0V8.
This can also be reached in IMG by:
Sales & Distribution-->Sales-->Sales Document Header-->Define Sales Document Types
Locate the particular Sales Doc Type, and double click on it to display it configuration.
Here you put the Two Digit Number key in the Field- "Number range External
Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be
maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
What is Debit note and Credit note
What is Debit note and Credit note? What is the purpose? How we create?

1. A transaction that reduces Amounts Receivable from a customer is a credit memo. For
eg. The customer could return damaged goods. A debit memo is a transaction that
reduces Amounts Payable to a vendor because, you send damaged goods back to your
vendor.
2. Credit memo request is a sales document used in complaints processing to request a
credit memo for a customer. If the price calculated for the customer is too high, for
example, because the wrong scale prices were used or a discount was forgotten, you can
create a credit memo request. The credit memo request is blocked for further processing
so that it can be checked. If the request is approved, you can remove the block. The
system uses the credit memo request to create a credit memo.
You can use credit memos in Sales and Distribution (SD) for assigning credit memo
requests to the open invoices and in Financial Accounting (FI) for assigning credit
memos and payments to the open invoices and carry out clearing with them. If you use
both Financial Accounting (FI) and Sales and Distribution (SD), there is a 1:1
relationship between the credit memo request and the credit memo item posted in
Financial Accounting (FI). As soon as you bill the credit memo request together with
other sales orders, or distribute the items of one credit memo request to several billing
documents, the assignment is no longer valid and the system will not process it.
For credit memos, credit memo requests, and payments, you have the following
assignment options:
- Assignment to a single invoice
- Assignment of a partial amount to an invoice
- Assignment to several invoices
When you post credit memos, the payment programme processes them automatically. If
the credit memo is specifically related to a particular open invoice item, the payment
program automatically attempts to offset the credit memo against the open item. If it is
not possible to completely offset the credit memo against an invoice, you can post a debit
memo to the vendor, who is to reimburse the amount. Then you can apply a multilevel
dunning program.
3. Debit memo request is a sales document used in complaints processing to request a
debit memo for a customer. If the prices calculated for the customer were too low, for
example, calculated with the wrong scaled prices, you can create a debit memo request.
The debit memo request can be blocked so that it can be checked. When it has been
approved, you can remove the block. It is like a standard order. The system uses the
debit memo request to create a debit memo.
4. As mentioned above, creating a credit or debit memo request enables you to create
credit or debit memos based on a complaint. For this first create a sales document with
the order type for a credit or debit memo request. You can create the debit or credit
memo requests in the following ways:
– Without reference to an order

– With reference to an existing order
Here you enter which order the complaint refers to.
– With reference to an invoice
Here you enter which invoice the complaint refers to.
In all cases, you specify the value or quantity that should be in the credit or debit memo
5. You can block the credit or debit memo request from being billed in Customizing. Go
to Sales -> Sales Documents -> Sales document header -> Define sales document type
and select the billing block field in the billing section. This request can later be reviewed
along with similar ones, - if necessary, by another department. The request for a credit or
debit memo can then be approved or rejected.
Explain What Is Credit and Debit Memo
1. A transaction that reduces Amounts Receivable from a customer is a
credit memo. For eg. The customer could return damaged goods. A debit memo is a
transaction that reduces Amounts Payable to a vendor because, you send damaged goods
back to your vendor.
2. Credit memo request is a sales document used in complaints processing to request a
credit memo for a customer. If the price calculated for the customer is too high, for
example, because the wrong scale prices were used or a discount was forgotten, you can
create a credit memo request. The credit memo request is blocked for further processing
so that it can be checked. If the request is approved, you can remove the block. The
system uses the credit memo request to create a credit memo.
You can use credit memos in Sales and Distribution (SD) for assigning credit memo
requests to the open invoices and in Financial Accounting (FI) for assigning credit
memos and payments to the open invoices and carry out clearing with them. If you use
both Financial Accounting (FI) and Sales and Distribution (SD), there is a 1:1
relationship between the credit memo request and the credit memo item posted in
Financial Accounting (FI). As soon as you bill the credit memo request together with
other sales orders, or distribute the items of one credit memo request to several billing
documents, the assignment is no longer valid and the system will not process it.
For credit memos, credit memo requests, and payments, you have the following
assignment options:
• Assignment to a single invoice
• Assignment of a partial amount to an invoice
• Assignment to several invoices
When you post credit memos, the payment programmed processes them automatically. If
the credit memo is specifically related to a particular open invoice item, the payment

program automatically attempts to offset the credit memo against the open item. If it is
not possible to completely offset the credit memo against an invoice, you can post a debit
memo to the vendor, who is to reimburse the amount. Then you can apply a multilevel
dunning program.
3. Debit memo request is a sales document used in complaints processing to request a
debit memo for a customer. If the prices calculated for the customer were too low, for
example, calculated with the wrong scaled prices, you can create a debit memo request.
The debit memo request can be blocked so that it can be checked. When it has been
approved, you can remove the block. It is like a standard order. The system uses the debit
memo request to create a debit memo.
4. As mentioned above, creating a credit or debit memo request enables you to create
credit or debit memos based on a complaint. For this first create a sales document with
the order type for a credit or debit memo request. You can create the debit or credit memo
requests in the following ways:
• Without reference to an order
• With reference to an existing order
Here you enter which order the complaint refers to.
• With reference to an invoice
Here you enter which invoice the complaint refers to.
In all cases, you specify the value or quantity that should be in the credit or debit memo.
5. You can block the credit or debit memo request from being billed in Customizing. Go
to Sales -> Sales Documents -> Sales document header -> Define sales document type
and select the billing block field in the billing section. This request can later be reviewed
along with similar ones, - if necessary, by another department. The request for a credit or
debit memo can then be approved or rejected.
Use the same Invoice Script/smartform for Credit/debit memo's
INVOICE
Output type : RD00
ScriptForm Name : RVINVOICE01
Driver Program Name : RVADIN01
smartform name : LB_BIL_INVOICE
Smartform Driver Pgm: RLB_INVOICE

Configure Intercompany Stock Transport Order
Explain STO.
STO is Stock Transport order. It is used for inter company transfer of goods. Plant to
plant transfer and even transferring raw material to Third party contractors (Job Work).
The Process is you create a STO do delivery against the STO and create a Billing
Document against the STO.
How to configure the inter-company Stock Transport Order? - Prassee
Material should exist in both the plants (Delivering & Ordering),
Internal customer should be assigned to the ordering plant ( MM -> Purchasing ->
Purchase Order -> Setup stock transport order -> assign the internal customer to the
ordering plant and assign the Sales area of the internal customer.
Tcode : OMGN
Assign its Sales area to the delivering plant
Assign the document type and Delivery type NB and NLCC

Assign the Supplying plant --> Receiving Plant --> NB
Take the delivering plant and assign the sales area.
Vendor master has to be created and assaign the supply source ( Delivering Plant).
Create a puchase order ME21N ---> Save
Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order
number here and execute.
Select the Delivery creation line and do the back ground process.
Start the log display and see the delivery document number by the documents button
Goto VL02N --> do picking and PGI --> Then do the MIGO with respect to the delivery
document.
Billing (Intercompany pricing conditions should be set).
Inter Company Sales Process
Explain the Inter Company Sales Process.
In SAP sales & distribution module, an intercompany sales occurs when the selling
organization belongs to a different company code than the delivering plant. The
transaction path for accessing intercompany sales billing is:
IMG >> Sales and distribution >> Billing >> Intercompany billing
Let us take an example to understand intercompany sales better. Suppose there are two
company codes namely 1000 and 2000. A customer may place an order for goods in sales
organization belonging to company code 3000. However, the goods may be
manufactured by a delivering plant belonging the company code 1000. A sales order is
created indicating delivering plant of company code 1000. The sales organization then
invoices the customer for the materials purchased. SAP R/3 automatically creates an
intercompany billing document at the same time as the customer’s billing document is
created. This intercompany invoice is sent from the delivering plant to the selling sales
organization.
As a rule of thumb, when dealing with different company codes, one may find a need to
transfer stock between two different company codes. However, if the stock be transferred

within the same company code, there is no need for an intercompany transaction. But in
case the stock is transferred between different company codes, a transfer of value occurs
and is an intercompany sale.
---
In intercompany sales process, no PO will raise.
While creating sales order, if the end user knows there is no stock on their plant, they
request for their sister concern company to deliver these ordered goods to the customer
directly, after delivery they will receive intercompany invoice from the delivering
company code, that’s the reason you enter delivering plant while creating sales order.
Below is the inter-company check list:
Check all your settings once again for creating inter-company billing:
- Material should exist in both plants.
- Stock will be maintained in D-Plant (Delivering).
- Now Plant - R (Receiving) become the customer of Plant-D. So create a dummy
customer in Plant-D's company code and sales area.
- Assign this customer number to Plant -R's details & its selling sales area.
- Maintain the intercomapny billing type (IV) in ur sales doc type (OR).
- Assign the Plant-D to selling sales org+ dbt channel.
- Maintain relevant copy controls between documents.
- Determine pricing procedure for Standard (RVAA01) as well as Intercompany
(ICAA01)
(Note: Dummy customer's CPP, IV doc's DPP along with Delivering plant's sales area)
- Maintain the condition records for Condition type PI01- VK11
(Note: In ICAA01, you won't find any PI01 Ctype, but you'll find IV01-, if you observe
the details of IV01 C.type in V/06, it has the ref Ctype as "PI01" , through which the
condition record of PI01 is shared to IV01 also..)
- Now create VA01, enter the required fields, in delivering plant -enter Plant-D, @ item
level as well as @ header level, and save,
- Create Delivery VL01n, with ref to SO,

- Create Billing VF01 (with ref to DEL)--- observe bill type-F2,
- Create Billing VF01 (with ref to DEL again)--observe the bill type-IV.
Normal Sales Order Cycle Configuration
What are those initial sales order config?
By: Anuradha
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header:
1. Sales Document Type: The sales document types represent the different business
transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type,
always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion
with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine
divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order
Types to required Sales Area. This will minimize selection of Sales Order Type as per
sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to
create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category:
Sales Document Type + Item Category Group + Usage + Higher Level Item Category =
Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if
required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving
Schedule Line: Item Category + MRP Type / No MRP Type.

Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for
Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls
such as Sales Order to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Default Storage Location In Sales Order
Where to maintain settings if we want to make storage location
appear by default at the time of creating the sales order?
There is No storage location determination at Sales order level.. Only we can enter
manually.
Storage location will be determined at Delivery level only..
System does not determine storage location at sales order level. User has to indicate it at
time of creating sales order. The storage location entered in the order item is copied into
the outbound delivery. If no storage location for picking is specified in the order item,
the system determines the storage location when it creates the outbound delivery and
copies it into the delivery item. The system determines the picking location based on a
MALA, RETA, MARA rule defined in the delivery type.
This functionality is not available in the standard SAP. If you want the system to check
the stock at a specific storage location, the storage location has to be entered manually at
item level or you have to go for development so that it will be defaulted under the
specific conditions specified. You have to create a Z-table and maintain the table with
data under which that specific storage location has to be determined.

A userexit has to be used so that it will default the appropriate storage location after
checking the table.
Storage loction determination in Sales order is only possible via a user exit. You cannot
configure storage location into sales order: you need to use user
exit MV45AFZB USEREXIT_SOURCE_DETERMIN
or
You can use userexit_save_document
Userexit_save_document_prepare
or
The relevant forms to be used are:
USEREXIT_MOVE_FIELD_TO_VBAK -- to default in Header.
USEREXIT_MOVE_FIELD_TO_VBAP -- to default in item.
User exit: MV45AFZZ
---
Standard SAP can't determine storage location at sales order level. If required to give
manually. But at deliver it'll determine automatic.
Do the proper settings at Delivery level:
SPRO --> LOGISTICS EXECUTION --> SHIPPING --> PICKING --> DETERMINE
PICKING LOCATION --> Define Rules for Picking Location Determination.
If sales order level by default require, then you have to use user EXIT
Explain The Meaning Of An Open Sales Order
What is an open sales order?
An open sales order is where the order has not been delivered (physical goods).
Open Sales order : I will explain taking an example, suppose there is an order for 100 qty
and against this order, only 50 are being delivered till its delivery date . i.e. it is partially
delivered. then its status will be open . because it is not fully delivered.

Important tables for sap sd

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (18)

Similar a Important tables for sap sd

Similar a Important tables for sap sd (20)

Último

Último (20)

Important tables for sap sd