How VK11 works?

[Former Member]

Hi all,

I have been asked to develop a module program, which performs the tasks of VK11 in more user-friendly manner. For that I would like to know the functionalities of VK11, how it works. How and where can I study this in detail and ofcourse starting from scratch?

Thanks,

Rajan

[Lakshmipathi · Accepted solution]

Any condition type that you want to maintain in VK11 should have been created in V/06.

For this condition type, you should have maintained Access Sequence in V/06. For that Access Sequence, you should have maintained the relevant tables in V/07

Next these condition types will have to be assigned in your pricing procedure in such a way that condition types like pricing, discount etc., should flow from first step number, followed by excise and tax condition types.

Now for the combination you maintained in V/07, you would be maintaining pricing in VK11 and this will flow into your sale order which would then be stored in Table KONV

thanks

G. Lakshmipathi

[former_member648947]

Dear Rajan,

In addition to the information given by Laxmipathi.

VK11 you will see the key combination tab, these are nothing but the tables maintained in the access sequesnce. Here in VK11 for particular combination you maintain the record,

e.g condition type PR00 you select combination customer/material with release status . and maintain some price numerical value.

when in order entry pricing procrdure is determined automatically , in this pricing procedure system will come to PR00 condition type

for PR00 condition type assigned access sequence is PR00 you can check this assignement in V/06 by entering Condition type PR00) and first table in Access sequence PR00 ( Defined in V/07) is customer/Material with release status, thus system finds if there is any value maintainedfor this combination.

It will find the value which you have maintained in VK11 and will show display that in Sales Order.

Hope this gives you Idea about use of VK11. But Please gather your requirements more clearly, as far as I see the VK11 is quite user friendly.

Regards,

Paresh

[Former Member]

GOt the answer

[Former Member]

Hi Rajan

We create Condition master data or more popularly called "Condition record" using transaction code VK11.

Conditions can be Price, Discount/Surcharge, Tax or Freight etc.

We create condition record for thses condition types through t.code VK11. That means Condition master data or Condition record is created for a Condition type (may be Price, Discount/Surcharge, Tax or Freight etc) using VK11 t.code.

In the Condition record, we store value about condition ,like if Price then what is the Price, if Discount then what is the rate of Discount etc.

In the Condition record there is always a validity period specified and the values are valid only for that period.

We can maintain scale in the condition record (quantity dependent, value dependent scale etc.) and there is no limitation to scale. So you can maintain the scale to any level.

We can also maintain an upper limit and Lower limit in the condition record to restrict manual changes to a limit .If you want to change the value in the condition record manually then you can change only within this limit.

Condition record can be maintained on various level, e.g, Material level, Customer/Material level, Customer group/Material level etc. These different levels are defined by a "Condition Table".

The purpose of having a Condition record is that, system should find the value of the different conditions automatically when we create a Sales document.

Finding the values automatically by the system from these condition records is governed by a technique called "Condition technique", for which we need to configure the Condition technique.

First, we create the "Condition table" using the required field from the field catalog or we can use existing Condition table.

Second, we create "Access sequence" and assign the "Condition tables"along with "accesses" to the "Access Sequence".

Third, we define our "Condition type" and assign the "Access sequence" to this "Condition type".

Fourth, we define a "Pricing Procedure" and assign all the "Condition types" required in the proper sequence in the "Pricing Procedure".

Fifth, we define the "Pricing Procedure determination"( Cust Pricing procedure + Doc Pricing procedure + Sales area ) .Assign the value to the respective Customer and to the Document type.

Now, your Condition technique configuration is complete.

But,system to get the value automatically into the condition screen of the Sales document, we need to create condition records for the condition types on various levels required, so that we can store the value of these conditions in the condition records.

To create these condition records for each Condition type, we use transaction code VK11 and they are stored in the table KONV.

Hope, this will help to clarify your requirement.

[Former Member]

Thanks a lot! pradyumna

Rajan