Definitions of Fields in Pricing Procedure

A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this
element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from
automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price
is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study
statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the
document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis
for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used
to exclude the system from accessing the condition type and trying to determine the value. This
can be used to specify that the condition type should only be accessed if the customer has a low
risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type,
instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote
an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the
posting of the revenue generated to respective account heads& to subsequent assignment to GL
accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERF………….& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the
posting of the revenue generated to respective account heads& to subsequent assignment to GL
accounts and payment to respective parties.

How To Add New Fields To Field Catalog

For adding field into Field catalog:

I shall give an example. But you should first identify the field for Profit Center (Design ID) and
then do as follows:

For example if you want to use field PSTYV (‘Sales document item category’) that is included in
structure KOMP (‘Pricing Communication Item’) as a key for a condition table.

When you create a condition table (Transaction V/03), however, the system does not propose the
field in the field catalog.

Prerequisites:

For technical reasons, field PSTYV was included in structure KOMP, however, not in structure
KOMG (‘Allowed Fields for Condition Structures’).

To solve the problem, proceed as follows:

1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose
PSTYV as a domain.As a short text, you can use, for example, ‘ZZ – sales document item
category’ and as a field label, you can use the field labels of PSTYV.Save, check and activate
your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and
make the following entry:

Component Component type

ZZPSTYV ZZPSTYV

Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures
KOMG and KOMP because structure KOMPAZ is included in both structures.

4. Call up Transaction SPRO. Navigate to ‘Sales and Distribution -> Basic Functions -> Pricing ->
Pricing Control’ and execute ‘Define Condition Tables’. Choose ‘Conditions: Allowed fields’ and
include ZZPSTYV as a new entry.

5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.

6. Supply the new field you defined by including the following source code line in
USEREXIT_PRICING_PREPARE_TKOMP:

MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.

In order processing you find the user exit in Include MV45AFZZ, and in billing document
processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-specific
fields as key fields in a condition table.For header fields, use structure
KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead
of USEREXIT_PRICING_PREPARE_TKOMP.

For more information, see Transaction SPRO via the path ‘Sales and Distribution -> System
Modifications -> Create New Fields (Using Condition
Technique) -> New Fields for Pricing’ and Note 21040.

For creating a condition Table:

1) There are almost all the regularly used Conditon Table predefined in the system from 001 to
500.

See what best you can use the Standard Tables to avoid further errors.
2) In case you should define the new condtion Table,

a) Goto TCode: V/03

b) Give a Table any number from 501-999

Press execute and reach to next screen.

c) Check up whether the field you are looking is already added in Field catalogue.

d) Double click on the fields you want to make a Table..one by one. Note that the sequence here
is important in higher hierarchical to lower..

Eample : Sales Org, DC, Division, Customer and then Material etc..,

e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.

7) Check which key should be in header and which key should be footer. Use check and uncheck
functionalities there..

Once you are through with all the above steps ..click on generate button.

Check the Table is generated or not.

You can check it at V/04 or V/05 or in SE11.

Can Sales Order and Billing Have Different Pricing

Yes, can have 2 different pricing procedures

1. One for Sales Order

2. Another at the Billing

Let us take an example:

Generally in the Pharma industry this procedure is adopted becuase all the goods are batch price
based.

1. In the Pharma Industry whenever the goods are manufactured it will done in a batch to keep
track and price is fixed, I mean there will be a Batch Master which has a certain price fixed for it.
This Batch Master will have certain number of batches . These batches will have the number
series generated wither by internal or external generation depending upon the client requirement

2. So till all the batches are produced as per that particular Batch Master will have the same
price. Like that there will n number of batches will different different prices

3. So when you are preapring Sales Order you be only putting the tenative price for the goods
that are sold

4. Then at the time of delivery we will be picking up the goods from different batches basing on
the required delivery quantity and finally we do the PGI.

5. This is called Delivery Based Pricing becuase your price for the goods will be determined at the
time of the delivery as the goods picked up from the different batches which have different prices.
( Mind it there will very less difference in the prices).

6. So at the time of Billing the Pricing Procedure behaves differently depending upon the
differnent batches that are picked basing on the batch determination.

7. So the prices which are detemined from different batches will be the actual prices at which the
goods are billed to the customer along with other condition that are applied as required.

Reasons For Making Any Pricing Procedure in SAP

1. Why we are maintaining separate pricing procedure for inter company sales and
business processs.

2. What is the different between standard and inter company pricing procedure and what
type condition type we are using in this intercompany.

There are two simple reasons for making any Pricing Procedure in SAP SD Modules.

1) Business Reason. What are the pricing aspects or strategies you want to apply for the client
requirement in order to sell their
goods or render services, is all about the reason for various pricing procedures.

Eg: Domestic sales pricing procedure,

- Export Pricing Procedure,
- A rebate pricing procedure or
- A High Discount oriented pricing Procedures.
- A repair pricing procedures.

You have your own conditions intended to few transactions only. Put all this conditions as a set
defining your own Procedures. It may even include special requirements and formulas applied for
such Pricing Procedures.

2) A special pricing procedures, in order to facilitate added functionalities of SAP pricing

architecture, we must define new
pricing procedure. SAP Standard programmes checks these special Indicators in-order to do
some required functions.

As a example 1, you need to have a Pricing procedure for condition supplement inorder to use
the condition supplements. The condition supplement pricing procedure must be given in the
condition type definitions (v/06) of the Pricing Condition where you need to supplement, without
which SAP SD Condtion Supplements functionality doesnt work.

As a example 2, you need to have a Pricing procedure for Inter Company Billing Conditions(IV01
& IV02) inorder to be active for Inter Company Billing specific transactions. Thus make sure that,
the procedure wouldnot apply for non-Inter company transactions.

Eg: KA0000 for Condition Supplement for KA00

- PR0000 for Condition Supplement for PR00
- ICAA01 for Inter-Company Billing

Here I would like to remind about a important field in pricing.

In V/08 of defining a new Pricing Procedure, in main screen, you have a field called TSPP
(Transaction Specific Pricing Procedure). This has to be ticked on for Intercompany Billings.

The SAP help reads for this field as Under:

Transaction-specific pricing procedure

Pricing procedure transaction-specific indicator

Before Release 4.0A, no special pricing procedures were used for intercompany billing and
rebate credit memos, programs were just set accordingly to deal with these situations. As of
Release 4.0A you are offered greater flexibility in the form of the option to define special pricing
procedures for intercompany billing and rebate credit memos. For reasons of future compatability,
you will still be able to use the old program specifications. For this reason, you must set this
indicator if you want to create a special pricing procedure. This is to prevent the program settings
being used.

This indicator is also used as of Release 4.0A to redetermine the condition class and the
statistical condition indicator when copying from a reference document.

Example:
You copy prices from a shipment document to the billing document. The prices should lead to a
surcharge in the billing document. This is guaranteed by the redetermination of the condition
class in the pricing procedure.

Same case with Standard Pricing procedure or Inter Company Pricing Procedure.

This configuration is done when user request for new pricing condition type other than the
standard ones provided by the system.

Screen to tcode VA01 – Create New Sales Order for customers

- Double Click the Item
- Then Click the Conditions Tabstrips

Define Condition types

V/05 - Condition Table for V/07

e.g. a business may no longer wants to have a sales discount based on the sales organization,
customer group, and material, but decided that the discount should be based on the sales
organization, customer group and material group.

V/06 – Create new condition types by copying a similar conditions type and changing it according
to your needs.

 Double click on the condition type to change the control options

V/07 – Access Sequences for condition type

V/08 – Pricing Procedures for condition types.

The pricing procedure is also used in the account determination. This determines the general
ledger accounts to which prices, discounts and taxes must be posted.
  Click on the Pricing Procedures e.g. PR0000 – Condition Supplements for PR00
 Click Control – e.g. Tick Mdt if you want the condition type to be mandatory
o OV34 – Define account key
o OV35 - Assign account key
 Actky – Revenue account
 Accrls – Accruals account

OVKK – Determine which Pricing Procedures to use for which Condition Type.

Price with additional decimals

You can add additional decimals for a currency through a work around method.

Set up a currency let’s say instead of USD call it US$ ( OY03 ) and define the number of decimal
places ( OY04 ) to be 3 or more depending on your requirement.

Maintain the exchange rate for between US$ and USD to be 1 to 1 ( OBBS and OB08 ).

Create pricing condition records for those customers requiring 3 decimal places using Current
US$ instead of USD.

That will give you 3 decimal places for your prices. However, one thing you will have to watch out
for is rounding.

You can try transaction OB90, define rounding rule for currency. Here you define the rounding
rule for your customer’s currency.

Control Pricing Conditions based on Order Type

4.6x

e.g. You create an order type ZP00 for QT – Quotation and does not wish it to be used in OR –
Standard Order.

Follows this steps :-

IMG – Sales and Distribution -> Basic Functions -> Pricing Control -> Define and Assign
Pricing Procedures

Define document pricing procedure

e.g. Q – Quotation
Assign document pricing procedures to order types
e.g. Assign Q to Order Type QT – Quotation

Maintain pricing procedures

e.g. Copy Standard Pricing Procedure to e.g. ZQT (all the pricing conditions list will only be
allowed in order type QT – Quotation

Define Pricing Procedure Determination

e.g. Copy and assign Document Pricing Q and Pricing Procedure ZQT accordingly

Users will receive Message no. V1 206 “Condition ZP00 is missing in pricing procedure A V
ZQT“.

Create a New Pricing Conditions Key Combination

4.6x

In VK12, click the Key Combination button. You can see a list of available key combination for
your price master.

Now, let create a new key combination e.g. Customer + Sales Document + Material

IMG – Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition
Tables -> Create condition tables

e.g. 900
Selected fields
Sales organization
Distribution channel
Customer
Sales document
Material
Click Generate to activate it

IMG – Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition
Tables -> Defince Access Sequences -> Maintain Access Sequences
Select PR00 – Price
Click Accesses
Click New entries

AcNo Tab Exclusive

50 90 X – Tick

Save your entries

IMG – Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition
Tables -> Defince Access Sequences -> Optimize accesses

Copy an existing PR00 and substitute the AcNo with 50

Finally, goto VK12 and key in the new price master for PR00.

Next, goto VA02 and test out the material. If it didn’t work check the pricing date in the header
details. Is the pricing date within the validity period?

Pricing Release Procedures

4.6x

Define Processing Status – SM30 -> V_T686E

You are free to design your own processing status flow.

e.g. from 01 -> 02 or
from 01 -> 02 -> 03

To convert the old Pricing Condition with the release status use program
SD_MOVE_A004_TO_A304.
For the standard tables, the following pairs of condition tables are intended to be used:
‘old’ <–> ‘new’ VAKEY fields
A004 <–> A304 VKORG + VTWEG + MATNR
A005 <–> A305 VKORG + VTWEG + KUNNR + MATNR
A006 <–> A306 VKORG + VTWEG + PLTYP + WAERK + MATNR
A007 <–> A307 VKORG + VTWEG + (SPART) + KUNNR

For example, if you are using A005 –> A305, you have to copy the program to
ZSD_MOVE_A005_TO_A305 and amend the program Source and Target table.
First test run by ticking both option. If you confirm that there are no errors, then run by unticking
both options.

Be careful while executing the conversion program as it can erase all your existing pricing
condition data.

Once the conversion is completed, you can activate the Customer/Material with release status :-

IMG -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define
Access Sequences -> Maintain Access Sequences

In VK12, you will be able to choose the new Customer/Material with the release status column
per material.

Delivery Pricing Conditions

4.6x

Configure the pricing procedure at delivery with the required condition type to determine freight.
Also have the copying control from delivery to billing at item level with Price source as D for
Delivery. While you execute billing you would get the prices from the sales order as well as from
deliveries.

If you were to look at the pricing procedure RVAA01 you will see there was a section dedicated to
the various freight charges. Normally, I would use one of the available condition types and create
a condition master based on the Incoterms.

Configuration path :-

IMG -> Logistics Execution -> Shipping -> Basic Shipping Functions -> Pricing

Hiding condition type VPRS – OSS note 105621

It tells you to modify userexits: USEREXIT_FIELD_MODIFICATION,

USEREXIT_FIELD_MODIFIC_LEER,
USEREXIT_FIELD_MODIFIC_KZWI, USEREXIT_FIELD_MODIFIC_KOPF and
USEREXIT_PRICING_CHECK.
It also tells you to create two new includes: ZZAUTH01 and ZZAUTH02, but it doesn’t tell
you what changes to actually make in any of these. I am assuming that the authority
checks have to be added somewhere, but what goes where?

The coding for includes ZZAUTH* are (create them in SE38 like INCLUDE, and althought note
say that dev.class must be VF, I have them with own dev.class ie: Z**, and it works)

include ZZAUTH01
*&———————————————————————*
*&———————————————————————*
*& Object REPS ZZAUTH01
*& Object header PROG ZZAUTH01
*&———————————————————————*
*& This object has been generated from an advance correction *
*& attached to a R/3 note. *
*&———————————————————————*
*&———————————————————————*
*& Title: Authority check for displaying fields *
*&———————————————————————*
***INCLUDE ZZAUTH01.
* Beim ersten Aufruf ist KOMV initial; OLD_KOMK löschen,
* damit auf jeden Fall Berechtigungsprüfung durchgeführt wird.
* Sicherheitshalber zunächst Berechtigung verweigern.
* if komv is initial.
IF SCREEN-NAME = ‘FCODE’.
CLEAR OLD_KOMK.
AUTH_SUBRC = 4.
ENDIF.

* Berechtigungsprüfung auf Kalkulationsschema und Stufen-Nr.

* Beim Wechsel der KOMV-Zeile einmalig eine Berechtigungsprüfung
* durchführen
IF KOMK-KALSM NE OLD_KOMK-KALSM OR KOMV-STUNR NE OLD_KOMV-STUNR.
AUTHORITY-CHECK OBJECT ‘Z_KONH_KLS’
ID ‘ZKALSM’ FIELD KOMK-KALSM
ID ‘ZSTUNR’ FIELD KOMV-STUNR
ID ‘ACTVT’ DUMMY.
AUTH_SUBRC = SY-SUBRC.
OLD_KOMK = KOMK.
OLD_KOMV = KOMV.
ENDIF.

IF AUTH_SUBRC NE 0 AND ( SCREEN-NAME = ‘RV61A-SELKZ’

OR SCREEN-NAME = ‘KOMV-KAWRT’
OR SCREEN-NAME = ‘RV61A-AWEIN’
OR SCREEN-NAME = ‘KOMV-KBETR’
OR SCREEN-NAME = ‘RV61A-KOEIN’
OR SCREEN-NAME = ‘KOMV-KPEIN’
OR SCREEN-NAME = ‘KOMV-KMEIN’
OR SCREEN-NAME = ‘KOMV-KWERT’ ).
SCREEN-ACTIVE = 0.
ENDIF.
MODIFY SCREEN.
* Ende Berechtigungsprüfung

for include ZZAUTH02

***INCLUDE ZZAUTH02 .
*&———————————————————————*
*&———————————————————————*
*& Object REPS ZZAUTH02
*& Object header PROG ZZAUTH02
*&———————————————————————*
*& This object has been generated from an advance correction *
*& attached to a R/3 note. *
*&———————————————————————*
*&———————————————————————*
*& Title: Authority check for creating new conditions *
*&———————————————————————*
***INCLUDE ZZAUTH02.
AUTHORITY-CHECK OBJECT ‘Z_KONH_KLS’
ID ‘ZKALSM’ FIELD KOMK-KALSM
ID ‘ZSTUNR’ FIELD KOMV-STUNR
ID ‘ACTVT’ DUMMY.
IF SY-SUBRC NE 0.
MESSAGE E609(VH).
ENDIF.
* Ende Berechtigungsprüfung
…
*&———————————————————————*

In my system (46B) I remember that the subroutines USEREXIT is not changed for this purpose.
With SU21 (z_konh_kls I think that you don’t have problems), like with SU02.

In su02, remember that in XU180-PROFILE of first dynpro, you must populate with value
‘ZCOND_STD’ and click on create work area for profiles. Double click on zcond_std. In object
populate with ‘Z_KONH_KLS’, double click and you see the parameters like in tcode PFCG
(profiles and auth.)

For action you can populate ‘*’

For procedure you can populate with the procedure (see tcode V/08 ) that you use in your SD
documents, or the procedure/s in where you want that the restriction will work, if you have many
procedures.

For level, you must write the ranges of levels in this procedures (into V/08 ) that you want that the
user can see (remember that alpha routine conversion dont works, ie: for level ‘ 1′ [in dynpro] you
must write ’001′, if not, you will have problems). The levels out of this ranges, the user with this
profile when go to conditions in SD document will not see the value of these items.

Finally, in SU01, add this profile to profiles created with PFCG in ‘profiles’.

After check if it works.

Pricing Procedure in Product Hierarchy

Pricing structure for line item is KOMP. A quick look thru KOMP structure (tx SE11) shows that
you have only PRODH field for all 18 digits of product hierarchy, whereas you need only the first
three. So you do the following:

1. Create the new data element ZZPRODH1. Also create a domain with the length “3″ and the
data type “CHAR” for the new data element. Remember that new data fields must start with the
letters “ZZ” or “YY”, since SAP reserved these letters to protect them from being overwritten
during a release upgrade.
2. Check whether the product hierarchy (PRODH) is found at header or at item level. In table
VBAP, document field PRODH is defined as an item field.

3. Integrate the field name ZZPRODH in the communication structure KOMP using the INCLUDE
KOMPAZ and allocate the data element PRODH to it.

4. Activate the structure.

5. Check in which table the field PRODH exists.

The field is in table VBAP (sales document: item data).

6. Assign a value to the new field in the FORM routines for sales order processing and billing
using the appropriate user exits: In sales order processing the user exit is found in member
MV45AFZZ. The complete statement is:
FORM USEREXIT_PRICING_PREPARE_TKOMP.
MOVE VBAP-PRODH(3) TO TKOMP-ZZPRODH. ENDFORM.
The routines for assigning a value to the new fields in billing are found in member RV60AFZZ.
The statement is as follows:
FORM USEREXIT_PRICING_PREPARE_TKOMK MOVE
XVBRP-PRODH(3) TO TKOMP-ZZPRODH. ENDFORM.

7. Allocate the specifications A, V and 001 to the field ZZPRODH in table T681F. Use “E” has
been added for fields in rebate processing.

This is a standard example from SAP Library. In this case you must tell the ABAP three things:
- that your source field is VBAP-PRODH,
- that you need to get the first three digits from that field into your pricing structure KOMP
- and that you need to specify the transfer by user exit thru MV45AFZZ

Please note that this is a very simple example. Quite often you have to dig a lot deeper.

Modifications of Copy Control routines, making output forms (thru SapScript) and such requires
you to know all the necessary tables, structures and fileds.

The only advice I can give you is to use tx SE11, which will show you the organisation of a
table/structure, and can also help you check the contents of a specific table in a specific sales
doc.

Steps for Variant Configuration and Pricing

1. Create a Material of your Motor Cycle using Material type KMAT(MM01).

2.Then create a characteristic called ZColour(SAP has a standard Characteristic for this but it has
multiple values-i.e you can select more than one colour for your Bike.If you do not want that
create your own)with character format and assign single value radio button on the initial screen.
Go to values Tab and give the colors you need.save the characteristic. Similarly repeat for CC (I
figure this CC as 100cc & 200cc kind of thing. If you want these as materials then it is a different
story-I am taking this as feature as well)

3. Create a class called Zbike with the above 2 characteristics and save the class.

4. Create a configuration profile Zbikeprof using Cu41 and assign the Kmat material to Class
Zbike,

5. Then create the order and Enter the Kmat material you want in the Order.

————————————-
Q – In variant configuration I have configured my material properly during sales order creation it is
selecting proper characterstics but my question is pricing should calculate at characterstics level
not at header level.

————————————
A – Pricing in variant Configuration is done at the Header level only. The logic is that you create
pricing variant keys for each characteristic Value. This will be done at the Header level using cond
type VA00.based on the characteristic chosen the appropriate price according to the pricing
variant key will be picked up.

————————————-
Q – Here my question is with out creating the materials is it possible to get price based on the
characterstics.

I am working on variant configuration here my product is 9-100. i have created characterstics for
describing colours. this characterstics assigned to class, this class is assigned to 9-100(KMAT
type). here i have not created amterial to describe each colour.

Now how I need to setup my system to calculate the price based on colour.

————————————-
A – A cool Question. It will really get us into the thick of things in Variant Configuration.
Here are the steps.

1. Create a Characteristic called ZColour(Standard SAP has a characteristic called colour.I did
not use it.)
Give your values.
Say, Red & Blue

2. Now create another characteristic called ZCol_surcharge

Give the description and go directly to Addnl Data Tab.Here in the table name Enter “SDCOM”
and in the Field Name Enter “VKOND”.The system will pick up the format from the Dictionary.

3. Now go to CT04 and change the Characteristic Zcolour.

Go to values tab and select RED.Goto Extras-> Object Dependencies->Editor and then select
Procedure.

In front of 000010 Enter $self.ZCol_surcharge=’RED’.

Similarly Select Blue and enter $self.ZCol_surcharge=’BLUE’

3. Link both these characteristics to the Class(The class which you have attached the KMAT
Material).

4. Go to VK11 and the Enter VA00.Then give the values RED and BLUE and enter the values.

5. Go to your order and Enter your material.

————————————-
Q – Here are some clarifications required from you.

what is the significance of item category group 0002 and 0004. Apart from these are they any
other item category groups are available for configurable materials ?
In BOM header material having components. is it possible to make the component as
configurable material.

————————————-
A – The difference b/w 0002 and 0004 is basically that of LUMF & ERLA.
In 0002 the pricing happens at the Header Item Level.
In 0004 the pricing happens at the Sub Item Level.
Check out the Item category Assignments and things will be Clear.
I think these two are the only ones used for Configuration.

Please let me know in which Scenario you would like to have the configurable material Inside a
BOM(as it would help me in visualising thh Item Category Assignment).

————————————-
Q – As you said I setup my system to calculate price based on colour.
ZCOLOUR contains all colours in values tab page.
ZPRICE contains table name and filed name in additional data tab page.

I went to ZCOLOUR characterstics I maintained (extras-object dependicies-editor-action) there I

have given $self.ZPRICE = ‘RED’ for all the values.

when am creating the sales order price is coming only for RED colour not other colours. even
price is maintained for all the colours.

————————————-
A – Seems like there is a mistake in the line $self.ZPRICE = ‘RED’ (You have said you have given
this for all the values- If I have not mistaken). This refers only to red colour.

In front of 000010 Enter $self.ZCol_surcharge=’RED’.

Similarly Select Blue in the Values Tab and enter $self.ZCol_surcharge=’BLUE’

All this is Case Sensitive. So please be careful.

Ads by Google
IBM Require SAP Experts
3+ Years of Experience Desired. Limited Openings Available. Hurry!
www.IBM.com/SAP-Jobs
100s of Engineering Jobs
Companies Hiring Freshers Now. Submit Resume & Find the Right Job!
MonsterIndia.com
SAP Mm Employment
Opportunities for SAP MM Experts. View Jobs & Submit Your CV Now.
www.accenture.com/SAP
4th Anniversary Offers
Pay Just Rs. 4/- & Take Home Any Product Only At Reliance Digital!
RelianceDigital.org/Special_Offers
Posted in 4. Pricing. 41 Comments »
Like
Be the first to like this post.

41 Responses to “Pricing in SD (in detail)”

1. Eddie Says:
December 12, 2007 at 1:29 am

Hi
I have two pricing conditions for discounts.
The first one is a percent based. i.e. 15% for all customers in the group but not for
the customer group customers that received the second pricing condition –
quantity.
How could I omplement this scenario using routines 6 or 38?

Reply

2. jiteshdua Says:
December 14, 2007 at 3:01 pm

Eddie,
If I have understood your scenario correctly, the following should work -
* Use standard customer discount conditions – k005 (quantity based) and k007
(percentage based) and create a condition exclusion group.
* Write a routine to include ‘customer group’ as the basis for selection.

Let me know if this does not help.

regards
Jitesh

Reply

3. Prati Says:
February 21, 2008 at 7:25 am

Hey Eddie,
I am not getting your question exactly.. but i give you one link there itself you can
get the solution..

check this and reply me back:

http://www.onestopsap.com/sap-sales-disturbution/
 Reply

4. Prati Says:
February 21, 2008 at 8:27 am

Hey Eddie,
I am not getting your question exactly.. but i give you one link there itself you can
get the solution..

check this and reply me back:

http://www.onestopsap.com/sap-sales-disturbution/

Regards,
Prati

Reply

5. cindy himawan Says:

February 26, 2008 at 4:05 am

hi jitesh,
as we know in SIS there are some field who can be assigned by our self.
can u mention me how to assign the certain condition type into that field (order
pricing subtotal 5) in the pricing procedure?
thank you so much…

anyway, ur blog is very helpful…

regards,
cindy

Reply

6. Tapsa Says:
April 3, 2008 at 11:03 am

Hi,

I have question related to condition types:

In sales order for specific materials there is automatic pricing that is coming to
sales order.
When new price (PR00) is added to item, there is double price for material. Of
course this other condition type can be moved manually, but sometimes user don’t
remember to remove it.
 Is it possible to change system, so that when PR00 is entered manually, system
would not calculate other condition type for pricing? So basicly system would
need to notice that manually entered PR00 is available and do not calculate
automatic price to total amount.

Reply

7. krao.ch Says:
May 3, 2008 at 2:38 pm

this is very good like yahoo group and slso useful for those who are not having
godd knoledge in sap

Reply

8. SAKTHI Says:
May 8, 2008 at 6:57 am

I want to display the condition subtotals(Net value before freight) in my report..

can you tell me in which table i get those details.

Reply

o raghu Says:
February 9, 2010 at 11:35 am

Go to your home table.

Reply

9. Pradip Says:
May 12, 2008 at 9:03 am

Hi,
I am facing the problem for condition type VPRS, where amount in sales order &
invoice not same ( here there is no delivery document case is Order to Billing ).

Reply

10. Pier Says:

May 18, 2008 at 11:22 am
 Hi, I have a requirement of using more decimals (8) in the condition base value vs
the Std SAP rule.
Business scenario:
material codes have the alternative UoM set-up, the alternative UoM is the one
used for pricing maintenance in VK11/VK12.
The UoM conversion between alternative UoM vs Base UoM generates many
decimals when the system applies the conversion factor, and this is ok (std
conversion between ISO values of different UoM, volume UoM),
however the “std SAP condition base value” is considers only few decimals (I
guess 2 or 3) and it rounds at that level.
This triggers a big difference in the unit price value (given by [condition base
value * price per alternative UoM], where the condition base value is given
considering the conversion factor between alternative and base UoM, one divided
by the other as stored in the material master alternative UoM tab) between the
“current legacy rule (8 decimals) and the SAP rule”.
Example
SAP does: £174.46 * 0.278 = 49.99.. = £49.50 (rounded) this is the price per base
UoM which is also the Sales UoM, where 0.278 is the condition base value based
(conversion factors between Alternative UoM vs Base UoM)

In Legacy: £174.46 (price per alternative UoM) * 0.27777777 = 48.4611.. =

£48.46 (rounded) this is the price per base UoM which is also the Sales UoM

The currency decimals are ok, they are and they must remain 2 (GBP) and also
the final rounding rule (+ / – 0.05) is ok. The point here is the condition base
value:
using 0.27777777 instead of SAP 0.278
(this is the result of the conversion factor between UoM). We need to find a way
to use the figure with 8 decimals.
This triggers a 4p price difference and with big quantities this is a lot.
The idea of pricing per base UoM is not an option here as that will impact other
external applications and important Business rules.
What your thoughts about it?
Many thanks
Bye
Pier

Reply

11. Pier Says:

May 18, 2008 at 11:27 am

PS: Apparently only using one custom “condition base value formula” in VOFM
(then linked to the pricing schema) is not enough as the “variable” will already
contains e.g. 0.278 (based on the previous example).
 Reply

o Derek Says:
October 5, 2010 at 8:15 am

Hi Pier, do you managed to find a solution to this problem? I’m new to SD

and am currently facing the same problem? Hope there’s something to
new here. Thanks.

Reply

12. Frank Says:

September 5, 2008 at 7:27 pm

Hi

I’m trying to set up a price mechanism with a customer, about freight costs.

The prices are placed mannually, and I want that this price appeas in the final
invoice, also I want that the system calculates the freight cost from quantity
shipped by auto, but do not affects the net price, after this I want that that the net
price and freight cost appears at final invoice

Is that possible and which are the steps for?

Thank you
Franck

Reply

13. Manish Says:

October 19, 2008 at 5:59 pm

Hi All,
I wanted to configure pricing procedure. The requirement is price is cost plus
margin say 10%. The cost is the highest of VPRS and EK01, How to configure
this??

Business process is,

Client buys Goods from third party vendor and resale it by adding margin 10%.

Please guide me. Thanks !!!!

Reply
14. Kanchan Apte Says:
October 27, 2008 at 6:39 am

Hi all
A formula for a pricing condition is well computed when creating order in CRM
or in R/3, but when the order is transfered from CRM to R/3, there is a
redetermination and the formula does not work.

any suggestions?

Reply

15. mazna Says:

February 24, 2009 at 9:15 am

hi all
I have Problem About Pricing error in Item xxxxx from VF02 (change Invoice),
when i click Icon Accounting.

How can i do.

thank you so much…

Mazna

Reply

16. MALA K REDDY Says:

March 14, 2009 at 5:11 am

hi
Material standard cost price is changed at the time of sales order creation.
my requirement is std cost price need to be calclute for the condition EK02 ,while
creating the sales order.

please give all your inputs.

Reply

17. Deepak_LKO Says:

April 1, 2009 at 2:36 pm

I have prepared the sales BOM. My Client wants keeps the stock at header level
item, but wants to do the Pricing at item level. It means Pricing at item level &
 delivery PGI at header level item. I do not know how to achieve this? Any idea.
Thanks!

Reply

18. JLopes Says:

April 2, 2009 at 5:06 pm

Hi,

I´m trying to make movement type 631 relevant to accounting…

Does anybody knows how to do so?

Thanks in advanced

Best Regards

JL

Reply

19. Andrea Says:

September 22, 2009 at 3:02 pm

Hi,
Total fixed amount surcharge is required.
I.e. every order should be given a fixed amount surcharge (not per item – on total
order)
Reading SAP documentation and what I could find on the interned Header
conditoins are only possible manually (and then the total amount is distributed
across the items).

Is there a way of applying header conditons automatically (conditons set up –

acc.sequence – but applied on header and then distributed across all items) .

thanks

Reply

o Sanjay Says:
October 1, 2009 at 10:32 pm

Hi Andrea,
 I have exactly same requirement.
I have set up surcharge condition as group condition and header and item
condition checked. Also have access sequence. But this is not working out
for me. Do you have got any solution yet?

sanjay

Reply

20. jiteshdua Says:

September 23, 2009 at 3:57 am

Andrea,
This is something SAP has to work on. I am afraid, until current release, header
conditions can only be entered manually. A work around could be to create a
customized solution with the help of your developers. It will be interesting to
know what solution you finally come up with. Please keep us posted.

thanks
Jitesh

Reply

21. Andrea Says:

September 24, 2009 at 8:56 am

thanks for the reply. Great to know that I have not missed something! I do not
think we will go ahead and try to find a customized solution. But if there is
“anybody out there who has done it – and could/would like to share it” –
wonderful! thanks again

Reply

22. maddy Says:

October 22, 2009 at 9:23 am

Mr Jitesh I have a query… i am new to SAP SD and currently tryin to configure

construction scenario in normal sales process…………..currently testin scenarios
on sandbox
1) I am am billing directly from SAles order(dont think del is req for construc plss
advice)
2) IN pricing the customer accepts all payments as advances and then on receipt
of final payment will raise an invoice——-I have gone for milestone billing to
map this but not successfu soo far i am not sure how take the advances and raise
 on final invoice(i am using FAZ for downpayment req —but i dont think my
pricing for condition type AZWR is correct)

Please help me with the pricing ..any qsss plss do askk

Reply

23. maddy Says:

October 22, 2009 at 9:24 am

sorry typed my email add incorrectly

Reply

24. jiteshdua Says:

October 27, 2009 at 8:20 am

Hi Maddy,
Please refer the following link –

http://sapsdforum.com/2008/05/24/configure-downpayment/

thanks
Jitesh

Reply

25. SAP Fan Says:

February 8, 2010 at 3:11 pm

Hello Jitesh,
SD pricing help.
If we need to do a calculation within a exit during pricing what exit needs to be
used and how. Basically we want to bring a condition value in the pricing
condition by a calculation in an exit.
Please let us know how can this be achieved?
Thanks
SAP Fan

Reply

26. NITIN Says:

March 13, 2010 at 6:47 am
 I am facing problem for profit center. In sales order line item profit center
showing correctly but when I prepared billing in VF01 and when finance
document created, there in Profit center document I found that profit center is not
showing correctly for VAT & debtors GL a/c line item but it shows correct profit
center in sales line item in single document. Please let me know where I can
check for rectifying the problem.

regards
Nitin

Reply

27. NITIN Says:

March 13, 2010 at 6:48 am

I am facing problem for profit center. In sales order line item profit center
showing correctly but when I prepared billing in VF01 and when finance
document created, there in Profit center document I found that profit center is not
showing correctly for VAT & debtors GL a/c line item, it shows dummy profit
center code for 2 line item, but it shows correct profit center in sales line item in
single document. Please let me know where I can check for rectifying the
problem.

regards
Nitin

Reply

28. SAP Fan Says:

May 19, 2010 at 3:04 am

Hi,
I have to implement one ESP(Estimated Selling Price) . we need to sum all the
line item total and send it to Header condition type(ex: ZESP). It would be great if
anyone can throw any light to achieve this type of functionality.

Thanks,
SAP Fan

Reply

29. marshnil Says:

May 28, 2010 at 7:36 am
 hi, i have a problem raised by sd functional, i am abaper,
problem is , in va02, when i change the order quantity, the rate in pricing conditon
is not coming correct? please solve this problem

Reply

o jiteshdua Says:
May 28, 2010 at 10:58 am

Can you explain a bit more. Send me the screenshots at

jd@sapsdforum.com

Reply

 marshnil Says:
May 28, 2010 at 11:13 am

ya sure! see in va02, for item line 10, order quantity is 10, i vl
select it and goto pricing conditions, for particular condition type
ZHS7, i want to check, its showing me rate as 16% ok, now i vl go
back change the order qty to 101 and press enter, it will give me
info msg tht new pricing conditon.. after that i vl select it and goto
pricing conditions, the rate becomes 0% for that. what can be
reason? i check the condition records for that condition type, the
rates are not matching wt scale values maintained.

30. ram Says:

June 8, 2010 at 6:52 am

Hi,

While entering the pricing condition manually in the shipment in vi02 transaction
for the delivery items, i get the amount in red color and when i go back to delivery
items and select the same one, the condition type which i gave previously is
getting vanished.
Can you give me some idea on what is happening? or how to fix this issue?

Reply

31. Silvia Lal Beharie Says:

June 10, 2010 at 8:48 am

Hi,
 I also have a complicated requirements for shipment costs. I need to cumulate all
items’ quantities in order to determine each item condition value. In a shipment
cost document there is no total quantity field and the only field that gives me a
quantity at item level is KOMP-MLGME or KOMP-MGAME.

I thought of addressing this requirement by calling other tables such as VFKP or

VFSI or VTFA but I’m not sure if this is possible. What I would like to do is as
follows:

VFSI (VBELN to determine the delivery number);

VTFA (VFSI-VBELN = VTFA-VBELV to determine the shipment number
TKNUM);
VTFA-TKNUM: each item (POSNR) cumulate all referenced quantities
(RFMNG) = “Total Shipment Quantity”
KOMV-KWERT = (each item quantity / total shipment quantity) x KOMV-
KBETR

Will this be possible? if not I would really appreciate some suggestions.

Reply

32. SACHIN ARORA Says:

July 22, 2010 at 4:47 pm

Excellent stuff.

Reply

33. Babu Says:

July 23, 2010 at 9:55 pm

I am interested in on line Sd functional training, please let me know the complete

details.

Reply

34. Split Says:

August 29, 2010 at 12:54 pm

Hi,
back to work?
I have a the following problem.
The scenario is simple,
We sell service item, but the amount posted to the revenue account (for us a
 balance sheet account) should be split and post on several other account according
to a predefined rule based on the material code (let say x1% should be posted on
account A1, …., x_n% on account A_n) but in the invoice only the total amount
should appear without any detail because it is only for internal purpose.
My idea was to manage n conditions types according on the number of split which
sould be done (with the rule sum x_i%=100) and build the effective price of my
item. To this total (as if it is my PR00) apply all the other conditions.
Do you have a better idea?

Reply

35. kapil Says:

November 1, 2010 at 2:30 pm

Hi

Kindly let me know the steps for automatic price determination and it’s
significiance in …. scenario

Reply

36. health tips Says:

January 9, 2011 at 4:44 am

Works The publisher, must be an?The place which, covers potential loses.Moment
of one?s, you considering HSA.Said it Im health tips, change either – easier and
more.Using of sexually, old granddaughter for.,

Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Name *

Email *

Website
Comment

You may use these HTML tags and attributes: <a href="" title=""> <abbr
title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code>
<pre> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Post Comment

Notify me of follow-up comments via email.

Notify me of new posts via email.

« Credit Management

Item Categories in SAP SD »

Blog at WordPress.com. Theme: Garland by Steven Wittens and Stefan Nagtegaal.

 Blog Stats
o 495,632 hits
 Recent Comments

Supriyo Dutta on Standard SAP SD Reports

chandrasekhar on SAP SD Training

Mahne on SD – Availability C…

Prem Anandan on SAP SD Training Videos

ali on Projects

 adm
 o Register
o Log in
o Entries RSS
o Comments RSS
o WordPress.com
 Quick Links
o Follow us on twitter
o IT Toolbox SAP SD
o SAP E-books
o SAP Education
o SAP IS-Retail
o SAP MM Forum
o SAP SD help
o SAP Service Marketplace
o SAP T Codes
 Quiz
o Pricing Quiz
o Test Your SD skills
 Pages
o About Us
o Freelancers
o Interview help
o Projects
o Q&A
o Questions??
o Remote Support
o SAP Remote Consulting
o SAP SD Training
o SAP SD Training Videos
o Web Dynpro Training