cancel
Showing results for 
Search instead for 
Did you mean: 

How to maintain different price

Former Member
0 Kudos

Dear Gurus,

For one matrial how we can maintain differnnt selling price.

For example:

paint as a one material code, and it has 30 differnet shades,

for this they have different selling price,

like same material code with diff shade diff price.

but in SAP how to map it,

Example: Distemper, has 15 shades

Distemper red : 50/kg

Distemper blue: 45/kg

Distemper white: 40/kg

By using Variant configuration we will get the different material codes,

but this they dont want,

now how we will maintain the 30 different prices,

is there any provision in sap,

Please give your valuable inputs.

Regards,

HRISHI

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Maintain the the shades as batch and create a access sequence which should include material, batch and maintain the condition record for that combination.

And add batch no. field in the incompletion log for sales document item

Former Member
0 Kudos

Hi,

This is possible. Pricing for varaints can be done in two ways

1) Using object dependencies (Procedures). The steps are explained below.

-Create a ref. characteristic which will store the price say X (CT04).

-assign this characteristic to your material class (CL02)

-Now define procedure for pricing as follows (CU01).

(i 'm assuming ur charcteristic for distemper color is "COLOR")

$self.X='a' if $self.COLOR='RED',

$self.X='b' if $self.COLOR='BLUE',

$self.X='c' if $self.COLOR='WHITE'.

- Assign this procedure to the configuration profile of your material (CU42).

- Now create condition records for condition type VA00 for your material/sales org/distrib channel combination and maintain price for variants a,b,c defined respectively for red blue and white colors. (VK11)

- Now create sales orders for different colors of distemper and you can see that the system picks different price for each color as maintained in your condition records.

This method is sufficient if you have limited no of variants and new variants will not be added frequently.

2) Using Variant tables. This is required if you have large no of variants and new variants are very frequently introduced.

Please get back to me if you need to use of variant tables for your scenario.

Regards,

Ashok

Former Member
0 Kudos

Dear Ashok,

Thanks for your detail inputs, will map and get back to you.

Thanks & Regards

Hrishi.

Former Member
0 Kudos

Hi,

I forgot to mention this.

When you create the reference characteristic 'X', you have to enter the following in the Additional data tab in CT04.

Table name - SDCOM

Field Name - VKOND

Regards,

Ashok