Migrate pricing condition VK11 by LSMW

[Former Member]

Hi Experts,

How can i make use of standard 070 condition record to upload the price condition to VK11.

e.g

The condition tpe is ZDC1   sales discount

Choose key combination Price List/Merchandise Category

Sales Organization

Distribution Channel

Price List

Document currency

Mdse Category

when I provide the above field in the source file, could you give me some knowledage to do the mapping in the below screen.

I saw a varkey but i don't know how to use it. thanks for your help.

Best Regards,

Keith

[former_member186385 · Accepted solution]

Hi Keith,

VARKEY is determined by system internally and it is not user input field

it is compressed form of Key combinations

For example, your Key combination for maintaining the condition type is

Sales organization

Distribution

Division

and you have entered the values

Sales organization :  IT10

Distribution            : DC

Division                 : D1

system will internally write VARKEY as IT10DCD1

[Former Member · Accepted solution]

Thanks Vermuri sanotsh kumar for your prompt reply.

In your e.g how can i map the sales org, distribution and divison in the screen for field mapping and conversion rule

my problem is that i am not able to map those key fields to the target.

Pls feel free to comment. thx a lot

Keith

[andrea_brusarestelletti · Accepted solution]

Hello,

you have to define in the source file a field VAKEY as concatenation of the key field of the condition table you want to populate. So if you condition table 

Then in the "Field mapping and rule" step, you have to link your VAKEY source field to the VAKEY field in the destination structure.

So if your table is made of the following fields, for instance the first record:

Sales Organization = '1000'

Distribution channel = '99'

Division = 'AB'

Material = '000000000000000001'

your source file should have in the first record the following VAKEY:

VAKEY = '100099AB000000000000000001'.

Bear in mind that the concatenation of the fields must consider their full lenght, so if your material code is for example "MATERIAL01" in the VAKEY you need to place 8 spaces before tha material code to reach the lenght of 18 CHAR.

Anyway you will easily experience this if you run the LSMW in foreground.

Best regards,

Andrea

[Former Member · Accepted solution]

Thx Andrea.

It is so very clear. I have a further question since i'm new to it.

For the value of the KOTABNR (Condition table batch input), coud you teach me to

find the distinct value for different key combination e.g
Sales Orgranzation+Distribution channel+Division_Material.

i found this numeric value used in table KONH but i would like to know the condition table to store the value for each key combination and the way to retrieve this value

Your help is much appreciated.

Best Regards,

Keith

[andrea_brusarestelletti · Accepted solution]

Hello,

in customizing under "Sales and distribution --> Basic functions --> Pricing --> Pricinng control --> Define condition types" under "Maintain condition types" you get the Access sequence assigned to your condition type. Then go back to "Define access sequences" under "Maintain access sequences" and enter with the access sequence assigned to your price condition: highlight it, double-click on the folder "Accesses" and in the column "Tab" you have the list of the condition tables to be filled.

Remember that you have also to populate:

Field KVEWE (Usage of the condition type) = 'A'

Field KAPPL (Apllication) = 'V' (if you are maintaing price in Sales).

Best regards,

Andrea