Important Tables for SAP SD Sales and Distribution:

SAP SD Discussion Forum and Sales/Distribution Tips

Listed here are practical and helpful SAP SD Stuff to assist those supporting the SAP Sales and
Distribution Module. You can find samples of interviews questions, answers and faq as well as many other
tips for the SAP SD module. If you have any SAP Sales and Distribution questions, please feel free to raise
it in the SAP SD forum.

The Sales and Distribution (SD) application component fulfills many of the international requirements that
supports the sales and distribution activities with functions such as pricing and conditions, customer order
processing, delivery monitoring, billing, credit and risk management.

Document Flow in Sales

The sales documents you create are individual documents but they can also form part of a chain of inter-
related documents. For example, you may record a customer’s telephone inquiry in the system. The
customer next requests a quotation, which you then create by referring to the inquiry. The customer later
places an order on the basis of the quotation and you create a sales order with reference to the quotation.
You ship the goods and bill the customer. After delivery of the goods, the customer claims credit for some
damaged goods and you create a free-of-charge delivery with reference to the sales order. The entire chain
of documents – the inquiry, the quotation, the sales order, the delivery, the invoice, and the subsequent
delivery free of charge – creates a document flow or history. The flow of data from one document into
another reduces manual activity and makes problem resolution easier. Inquiry and quotation management
in the Sales Information System help you to plan and control your sales.

The following graphic shows how the various types of sales documents are inter-related and how data
subsequently flows into shipping and billing documents.
Basic Process of how Packing Works
Let's say you want to pack a material shirt_jai in test_pack.
Using MM01, create material type=packaging test_pack
[SPRO]
IMG-Logistics Execution-Shipping-Packing-
Define Packaging Material Types
Let's say JPAC. The settings that I chose:
Plant determ. - Plant is entered manually in handling unit
Pack. matl. cat. - Packaging materials
Generate Dlv. Items - blank
Number assignment - Number range interval 'HU_VEKP'

IMG-Logistics Execution-Shipping-Packing-
Define material group for packaging material
Let's say JGRP
IMG-Logistics Execution-Shipping-Packing-
Define allowed packaging materials
JGRP - JPAC

MM02: Check settings for the materials

First, test_pack
Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP (Note)
Sales:General/Plant -> Packaging Mat. Type: JPAC (Note)
Basic Data 1 -> Material: JMAT
Then, shirt_jai
Sales:General/Plant -> Matl. Grp. Pack. Matls: JGRP
Sales:General/Plant -> Packaging Mat. Type: -
Basic Data 1 -> Material: JMAT

VL01N Outbound Delivery -> Packing

Enter the materials at top and at bottom

The "Packing Process" with an Example

Home » sales and distribution » packing process

The "Packing Process" with an Example

Example:
You created a order for a material(R-1160 - hard disks) for a qty - 120
pieces.

You need to create a delivery and

A)pack 40 pieces each of the material are grouped together into larger
cardboard boxes (PK-100 - shipping/packing material) and
B)these 3 cardboard boxes are put into pallet (PK-095).

Solution:
A)Packing 40 pieces each of material (40 x 3 = 120 pieces)

1)Goto [VL02N] to change the delivery, you already created.

Or you can do the following steps while you are creating a delivery
also.
2)Go to "pack" icon.
3)In the upper section, enter the "packing material" (PK-100)
4)In the lower section, change the "partial quantity" to 40 of material
R-1160.
5)Select both the lines of upper section and lower section and click the
green ok. It generates a shipping unit/handling unit number.
6)Now, select both lines of upper & lower section & click the button
"per part. qty" (New HU per part qty of material)
Check: click "General Overview" icon to see whether it packed 40
pieces of material in 3 cartons.

B)Packing all 3 cartons in one big carton(PK-095)

1) from above screen, click "pack HUs" (pack shipping unit)

2)enter the packaging material (PK-095) in the upper section and
select this line.
3)select 3 lines of PK-100 in lower section since you want to pack them
in PK-095.
4)selecting both lines, click "pack" icon.
5)Now all the 3 cartons(PK-100 with 40 pieces each of material) are
packed in one big carton (PK-095).
Check: "General overview" icon.

Difference between Condition Type

Home » sales and distribution » Condition Type

Difference between Condition Type

Please explain the difference between Ek01 ( Actual Cost) and EK02
Calculated Cost.

These are the condition type that will display the results of the unit
costing for certain type of sales document.

EK01 :
If you use this condition type, the result of unit costing is issued to the
first position on the conditions screen for the item. The value can be
used as a basis for price determination.

EK02:
If you use this condition type, the result of unit costing is simply a
statistical value which you can compare with the price.

Please note the following points :

1) The condition type must have condition category 'Q' (costing).

2) The condition type must agree with the condition type defined for
unit costing in the pricing procedure.

I have a customer who is being offered two discounts ie k007 and

k005, now I want to exclude k007 for the next 2
orders or so? I have set the exclusion indicator for the condition
type,but still the condition is being accepted when I create a sales
order. Am I missing something, how do I do it?
I think u need to change the validity of the condition record for the
condition type K007 defining it not valid for that particular 2 months.
And also the settings of the Requirements as it is correct that it
overrules the exclusion.

Accumulate the amount of condition types in accounting

document

Home » sales and distribution » amount accumulation

Accumulate the amount of condition types in accounting document

To accumulate the amount of condition types in accounting document

without affecting the pricing display in billing document.

As an illustration :-

ZPXX 3500
ZDXX 1000-
ZWXX 500-

(all condition types are shown separately in pricing view)

Journal:
Dr Vendor 2000
Cr Sales 2000 (ZPXX - ZDXX - ZWXX)

One way to do it is :-

Mark the condition types you want to group as statistical and remove
the account assignment key.

Create a subtotal in your pricing procedure that will add them together
and put in the account assignment key for it. This way the individual
components will still display on your pricing screen but FI will only get
one posting.

Creating New Pricing Procedure

Home » sales and distribution » creating new pricing procedure

Creating New Pricing Procedure

What is the transaction code for creating new pricing procedure and
how to attach it to specific plant?

You create PP in spro > Sales and Distribution > Basic Functions >
Pricing > Pricing Control > Define and Assign Pricing Procedures >
Maintain Pricing Procedures

You can't attach PP to specific plant. Pricing Procedure is determined

thru trx OVKK. The defining parameters for pricing procedure
determination are:

1. SalesOrg
2. Distribution Channel
3. Division
4. Document Procedure (defined in Sales doc\Billing doc maintenance)
5. Pricing procedure assigned to customer (defined in customer
master)

Hope this helps.

Sabir

Reg pricing procedure.

1. Use transaction code v/07 to create a access sequence and assign

tables based on which you want to carry on
pricing as accesses.

2. Use transaction code v/06 to define condition type. It can be for

base price, discount, freight etc.,
(Do assign relevant access sequence)

3. Use transaction code v/08 to define pricing procedure.

4. Assign this to your relevant sales area+ dpp+cupp.

While specifying requirement, we can give reqt no.22 which specifies

that plant has to be set. This is generally done for output taxes since
output taxes depend upon the delivering plant. But directly there is no
assignment between plant and pricing procedure.

What is alt cal type & alt base value & Req field in Pricing
Home » sales and distribution » alt cal type & alt base value

What is "alt cal type" & "alt base value" & "Requirement field" in the
Pricing Procedure

Can any one explain exactly what is "alt cal type" & "alt base value"
and also " Requirement field" in the pricing procedure?

The alternate base value is used as the calculation basis only, while
the alternate calculation is used to modify the final value.

For example, imagine you have a condition type ZZ01, with a condition
record maintained (master data) for $100. Now, condition ZZ02 also
exists lower in the schema, but with a rate of 10%. The standard
calculation would result in a final value of $110.

The alternate base value could say, "don't use $100 as the basis -- use
the original price PR00 only, which was $90." Then, the final value
would be $100 + (10% of $90) = $109.

The alternate calculation routine says, "ignore the 10% altogether.

Instead, use an externally calculated 20%." Then, you end up with a
final value of $100 + (20% of $100) = $120.

Put them both together, and you could end up with $100 + (20% of
$90) = $118.

Now once again,

Alternative Calculation Type:

Normally if you want to calculate a value you have to use a calculation

type for determinating the value. This calculation type is either
addition, subtraction or multiplication. Similarly SAP also has got a
default calculation type in the control data of the condition type. There
you have the options of either Qty based , Fixed Amount Based or
Percentage based.

Here what happens is suppose if you define Your condition type that
calculates the base price of a material on Qty based. Then the
calculation will be done based on the quantity of the material. If the
customer orders 10 Nos and you have maintained a unit price of 100
Rs for each material then the value determined is 1000 INR. Similarly if
the discount condition type , you maintain the calculation type as %.
This means if you maintain the value of 10 % in the condition record.
Then this percentage is taken as the calculation type and the
condition value is determined.

In some cases you have to forego the default calculation types and use
the customer specific method for calculating a value. For ex if you are
calculating the Freight charges for a Material . it depends on so many
criteria like, the weight, volume and also the minimum amount etc
etc, in those cases, you forego the default value and then use the
alternative calculation type in calculating the condition value against
the particular condition.

Alternative Condition Base value :

If you have to calculate any value then you have to have a base value
for it. For ex if you want to calculate the discount of 10 % for a
material then you have to have a base value on which this 10% is
calculated. Normally you take the condition value of the base price of
the material to calculate the value.

Now you don't want to take the base value and take other values as
base value which are derived on some formulae. So you create a
routine which will do the mathematical operations in the routine and
derive you a value which is now used as the base value for calculating
the condition value for a particular condition type.

Requirement:
A factor in the condition technique that restricts access to a condition
table. The system only accesses a condition table to determine the
price if the requirement specified has been met.

Example:
The system uses an access sequence to determine the price of a
material. One of the accesses in the sequence contains the
requirement "in foreign currency." The system only uses the table
behind this access if the sales order for which the price must be
calculated is in a foreign currency.

Re-pricing in a Quotation

Home » sales and distribution » re-pricing in a quotation

Pricing date based on Deliv. date, Sales Ord, Billing

How can I, or am I able to find anything on a way of RE-Pricing be done
in a QUOTATION?

You can always 'Update" pricing manually in a quotation the same way
you do in a sales order, either in create or change modes. Menu path
Edit --> New Pricing or press the 'Update pricing' button on the item
conditions tab.

If you are asking how to reprice a quotation when it converts into a

sales order, that can be done with the copy controls of the Item
Category. IMG: Sales & Dist --> Sales --> --> Maintain Copy Control for
Sales Docs --> Sales Doc to Sales Doc (transaction vtaa). Just choose
the combination of documents and the respective item category. The
field you need to be concerned with is "Pricing type".

However, from a business process perspective it makes absolutely NO

sense to reprice a quotation when converting to a sales order. After all,
the entire point of using quotations is to firm up details like pricing
before creating the sales order.

Report to Check the Entered Pricing Condition Price

Home » sales and distribution » entered pricing report

Quantity Based Discounts in Bulk Quantities Sales

You're looking to implement quantity based discounts in 4.6c. You are

trying to sell items in specific bulk quantities, and only give the
discount for specific quantity intervals.

For example, if a customer orders 1 piece, 2 pieces, 3, etc. of part ABC,

the price is $100.

If the customer orders 10 pieces of part ABC, the price is $50.

However, this is not only a standard minimum quantity discount. If the

customer tries to order 11 pieces, 12, 13, etc. it should return $100
again.

The only values for which $50 should apply are 10, 20, 30, etc. -
multiples of the bulk quantity 10.

You have discussed changing your part number to reflect a bulk qty of
10, however you have in house consumption that is allowed to
consume only 1 part at a time. You would vastly prefer to keep one
part number that you order from the supplier, consume internally and
ship externally.

You are fairly certain there is basic functionality that covers this, but
you're just not sure where to start.

Taking your requirements literally. Standard SAP scale pricing will not
do it in that you only want the reduced price to come into effect when
the order quantity is multiple of some bulk factor.

It is agreed with that creating a separate material number is not a

good idea.

You can try this :-

1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box

whatever)
2. Maintain UOM conversion between your base UOM and this new
UOM
3. Configure you bulk pricing condition type by usual means (it should
be a base price rather than discount).
4. Place this new bulk price behind your normal "PR00" price in the
pricing procedure
5. Create a new condition base value routine via VOFM where you
check XKWERT to see if it is a whole number. If it is not then set
XKWERT to zero.
6. Assign this new routine to your bulk price condition in your pricing
procedure in ALT condition base value column.
7. Maintain bulk price conditon record in the Bulk UOM.