Help required on Condition techniques

[Former Member]

I need to modify a legacy code that handles the pricing procedure in SD. I want to get details about the access sequence, condition tables, condition types and how the condition tables are populated.

Please give me some basic ideas so that I can proceed with the coding.

I have a brief idea about the access sequences and condition types and condition tables, but I want to know about the relationship of these concepts with the underlying tables. Suppose in the condition table we will get the condition types and from there we can get the access sequence and hence the condition value. Now in the condition value is let's say ZAC1 , then how we can develop the logic based upon that condition value. I want to know about the significance of this condition value.

In my application (telecom equipment refurbishment system) we have some raw data, like 100%credit,50%credit,25% credit to the customer based upon the condition of the equipment. Now from the condition tables I can get the values like ZAC1,ZAC2,ZAC3 but I am not able to inter relate these conditions with the actual percentage values.

Can anyone explain me the basic steps, so that I can proceed?

Thanks,

Sudipto

[Former Member]

Hi,

See the Following Link.

It would be Helpful.

[Pricing and Conditions |http://help.sap.com/saphelp_470/helpdata/en/64/7836b39c8911d199aa0000e8a5bd28/frameset.htm]

Regards,

Morris Bond.

Reward Points if Helpful.

[Former Member]

U can do it in VOFM

VOK0

[Former Member]

Hi,

pls look into this

Condition Types

T681W Conditions: Usage: Texts

T178T Conditions: Groups for Materials: Texts

T188T Conditions: Groups for Customer Classes: Texts

TVART ABAP/4: Texts of variables in selection conditions

TVKGGT Texts for Customer Condition Groups (Customer Master)

TVSBT Shipping Conditions: Texts

T671T Conditions: Views (Text)

T680MT Condition: Tree Control: Features: Texts?

T680VT Condition: Tree Control: Variants: Texts

T681T Conditions: Fast Entry: Texts

T686B Conditions: Exclusion Indicator: Texts

T681T Conditions: Fast Entry: Texts

T686B Conditions: Exclusion Indicator: Texts

T6B2T Rebates : Group of Allowed Condition Types/Tables : Texts

T683U Conditions: Procedure (Text)

T684T Condition exclusion: Texts

T685T Conditions: Types: Texts

LFMC Vendor master (short texts for condition types)

T688T Condition: Copying Rules for Condition Tables

Condition Tables

KONV Conditions for Transaction Data

KONP Conditions for Items

KOND Conditions (Data)

KONH Conditions (Header)

KONM Conditions

A000 Condition Table for Pricing $

If its useful reward points

[Former Member]

Hi,

U can create condition records through VK11 t-code.

The following tables are used for pricing-condition tables.

A911, A913,KONP.

Relationship: A911-KONP (Condition record no)

Relationship: A913-KONP (Condition record no)

KONP-KBETR for condition price

KONP-KOPOS for access seq

Regards,

vijay

[Former Member]

Hi,

Create conditions (transaction VK31)

Create conditions with reference (transaction VK34)

Change conditions (VK32)

Display conditions (VK33)

1. Choose Logistics Sales and Distribution Master Data.

2. Choose Conditions Selection using condition type Create.

Enter condition type PR00.

Choose Material with release status as a key combination.

You reach the fast entry screen for conditions.

3. Enter data in the Sales organization, Distribution channel, and Material fields.

Enter the pricing data for the material.

The following figure gives an example of the role of a condition record for a material

price.

4. Entry of calculation type:

You determine the calculation type for a condition type in Customizing. This determines

how the system calculates prices, discounts and surcharges for a condition. When

setting up condition records, you can enter a different calculation type than the one in

Customizing. At present all available calculation types are permitted. The field

‘Calculation type’ can however not be accessed if this field is left empty. After the

data release has been printed, if the field has not been completed manually, the proposal

is automatically taken from Customizing. After this it is no longer possible to make

manual changes.

If you use different calculation types for what are otherwise the same conditions (for

example, percentage, as a fixed amount or quantity-dependent), you do not have to

define different condition types in Customizing. You can set a different calculation type

when maintaining the individual condition records.

5. If you want to enter a pricing scale, choose Scales. If you want to change the default validity

period, choose Validity periods.

[Former Member]

thread closed