conditiontype, record

[Former Member]

Hi SAP Experts,

1. ) In v/06(condition type)--> PR00 > in the bottom , there is Text Determination . What is the effect of this. and hw i have to see the effect. if i change it.

2.) What is the diff b/w VK11 and VK31 condition records.

[Former Member · Accepted solution]

Hi Sabina,

1) for answering ur first question, the text determination procedure and text ID must be assigned to the condition type either in V/06 or text determination at VOTXN (there goto conditions)

If u assign it there, u can be able to enter a text in the condition record at Vk12. After the free goods symbol , there is a button for text will appear. (this will appear only if u assign the text determination procedure and text id to the particular condition type), there u can enter ur text for the condition type. after entering , the tab T will be marked automatically.

2)Regarding VK11 AND VK31, both are almost same, but in VK31, u can enter the records cumulatively.

VK31 is callled condition maintenance screen.

HOpe it is useful.

Reward points if useful..

Regards

[Former Member]

Purpose

The term pricing is used broadly to describe the calculation of prices (for external use by customers or vendors) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, the date - determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records.

The Condition Technique in Pricing

The condition technique refers to the method by which the system determines prices from information stored in condition records. In Sales and Distribution, the various elements used in the condition technique are set up and controlled in Customizing. During sales order processing, the system uses the condition technique to determine a variety of important pricing information. For example, the system automatically determines which gross price the customer should be charged and which discounts and surcharges are relevant given the conditions that apply.

Example of Pricing in the Sales Order

The following figure shows how the condition technique works in the background to produce the pricing information. The diagram shows how the various elements in the condition technique work together.

The system determines the pricing procedure according to information defined in the sales document type and the customer master record.

The pricing procedure defines the valid condition types and the sequence in which they appear in the sales order. In the example, the system takes the first condition type (PR00) in the pricing procedure and begins the search for a valid condition record.

Each condition type in the pricing procedure can have an access sequence assigned to it. In this case, the system uses access sequence PR00. The system checks the accesses until it finds a valid condition record. (Although you cannot see this in the diagram, each access specifies a particular condition table. The table provides the key with which the system searches for records).

In the example, the first access (searching for a customer-specific material price) is unsuccessful. The system moves on to the next access and finds a valid record.

The system determines the price according to information stored in the condition record. If a pricing scale exists, the system calculates the appropriate price. In the example, the sales order item is for 120 pieces of the material. Using the scale price that applies to quantities from 100 pieces and more, the system determines a price of USD 99 per piece.

The system repeats this process for each condition type in the pricing procedure determines a final price.

For further information on the condition technique, see Introduction to the Condition Technique

http://help.sap.com/saphelp_470/helpdata/en/64/7836b39c8911d199aa0000e8a5bd28/content.htm

regards,

Amlan Sarkar

[Former Member]

Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 as condition record from the templates whereas vk11 as simple condition record. In VK11 you can store condition record for more than one condition

type. This means you can have same condition record for different condition types. This feature is given to enhance the system's performance and not to create the duplication of the work for each condition type.

Again system is not allowing storing the record in the vk31 for the condition type pr00 and access sequence pr02.This is because if you see this ac seq contains two accesses 20 and 30 having the same table no. But you see there is the difference between the technical view of it for transferring the data from document field and condition field, so you can not maintain the data at VK31.

VK11 and VK31 both Tcodes functionally is same.

VK11:Maintain the Condition records individually.

VK31:Maintain the condition records groups and its useful to mass change of condition records.

Example:In VK11 we can maintain records for PR00,But in VK31 we can maintain records for PR00,K004,K007 etc at a same time.

Regards,

Rajesh Banka

[Former Member]

To add to the earlier reply, text detemination is for maintaining tests in master data, sales order, delivery, ... so that they automatically flow in subsequent documents.

In order to see its effect, do the text detemination and maintain a text in the material master saying" Handle with Care ". See how it flows in the order, delivery, Invoice etc.

These are very useful for special handling instructions, packing instructions etc.

regds

Jude

[ranjeetrajendra_jain]

Yes Jude i do understand that, however is there a specific reasons its been available here...?

Thanks

[Former Member]

Hi,

VK11 - you can maintain conditino records for a single condition type at once but for more than one material.

VK31 - Offers mass maintainance ie for multiple condition types you can maintain the values. But with VK31 you can only use standard sap conditions and not Z condition types.

regards

sadhu kishore