price at batch level is required

[Former Member]

Price at batch level.

The customer requirement is that there is stock available in the inventory against the two different

batches - Old batch 'A' and new batch 'B'.

The price in VK11 would always be maintained for latest batch 'B' which is but obvious.

Sometimes older stock is made available to the customer but the new batch price is being determined.

So the customer now wants that the price in the sales order should be determined on the basis of batch,

not on the basis of material which is happening currently in the system.

Can anybody provide the solution on how to maintain the price at batch level.

[Former Member]

HI,

your requirement we can map for this you need to do automatic batch determination in sale order level for this u need to define classification and assign relevant classification class.

follow the link  http://scn.sap.com/thread/429817

then select batch in key combination

then see result in sale order

Regards

Srinu B

[Former Member]

Thank you all for your replies.

I can add batch in access seq in pricing that is not an issue.But it would be very hectic to maintain the price at batch level instead of material.Moreover, in our system batches are determined in the delivery and not in the order.

The requirement is :-

material of new batch should be sold at 100USD 

and material of older batches to be sold at 90USD?

Dear Shashi, can you elaborate your solution in more details, how to achieve the requirement through your solution.

[former_member182378]

tushar,

Thanks for your post!

Important point is that batch is determined at delivery level (in your business process). Thus to have batch related prices in the transaction data (billing document) the pricing has to be re-determined at billing document level.

The requirement is :-
material of new batch should be sold at 100USD  
and material of older batches to be sold at 90USD?

The requirement indicates there are two types are batches - "New" and "Old"

So two condition records are to be maintained - with values 100USD and 90USD.

During creation of billing document, A piece of code shall ascertain for that material is the batch the new one or not. Depending upon that a field should be populated (with e.g. 1 or 0)

This field shall be included in the condition table, for the determination of condition records.

[shashi_thakur]

Hi Tushar,

If you wish to use Batch based pricing-then I would not suggest adding Batch into the Access Sequence as that would mean more frequent master data changes if there are numerous batches and chances of error increase. An alternate suggestion would be to create a new characteristic 'Price' for the batch class and update the Price for the batch in it-when the batches are being created-or add a logic to populate it automatically when the batch is being saved. The Prices in the Batches can also be uploaded through a custom program and that particular characteristic can be used for Pricing in the Sales Order.

Another question here is, since pricing is based on batches-how do you want to handle the COGS-is it moving average or do you have split valuation activated?

Regards,

Shashi

[former_member182378]

Shashi,

Your post is interesting and well written!

Like tushar, I too would like to know more details of prices inputted in batch (for a material).

More importantly, the option of - creating a condition table with field batch would lead to lot of master data maintenance. Then how is prices inputted for each batch different?

This option too requires lot of data maintenance.

Another question is -

Another question here is, since pricing is based on batches-how do you want to handle the COGS-is it moving average or do you have split valuation activated?

How is price, batch related to COGS? (for this requirement)

[shashi_thakur]

Hi T W,

Thanks for the comment.

Adding of a new characteristic called Price to the Batch Class should be standard. As regards, the difference between the maintenance effort between the condition records for so many batches per material and the maintenance during batch creation itself-it can be done in two ways.

(a) If the finance/pricing department is fairly clear of the pricing formula based on the batch-then the same needs to be put into code in the Exit while saving the Batch.

(b) The alternate option is to have a Z-program wherein the Input is the Price, material and Batches and it updates all the batches with the Price in one go.

We have option (a) implemented in one of the Projects. It works on the basis of the Moving average price in the material master followed by some additional calculations.

The question regarding the COGS was more of a Query and again related to a similar experience I already had on one of the Projects. When we sell something at a different prices one of the reasons is also because the cost has changed. So I was wondering whether the Cost part of the particular batch has already been handled or not. If it has then the same can be ignored.

Regards,

Shashi

[Former Member]

Hello Tushar,

Please check note 24832 which will answer your query. If you change VBAP-CHARG, then system carries out a new pricing  with pricing type G.

Kindly review the note very thoroughly to achieve your requirement.

Let me know in case of any queries.

Regards,

Bhavin Joshi

[Former Member]

Dear tushar chandak,

I'm sure that you must be aware of using Batch as a part of key combination for pricing purpose. For that you need to new condition table with a combination of Sales Org, Distribution Channel, Material No. and Batch No. Assign the same to your Access Sequence and make sure that you need to maintain condition records for each Batch No. and you will be keep doing this practice based on Production Lots which might be hectic job for the one who is maintaining condition records. Thanks.

[former_member182378]

tushar,

How many batches are there per material? (approximately)

New batches of material are made how frequently?

What is the requirement - material of new batch should be sold at 100USD

and material of older batches to be sold at 90USD?

Or for every batch per material, a price has to be maintained?

Extra comment - All the above questions are directed to understand if condition record is maintained at batch / material level, then (approximately) how many records would have to be created / changed (during on going business activities).

[moazzam_ali]

Hi

Why don't you put batch in your condition table and maintain prices batch wise. I hope you are familiar with pricing determination techniques. Add Batch in your condition table, add condition table in your access sequence and assign access sequence to your condition type.

Thank$