cancel
Showing results for 
Search instead for 
Did you mean: 

Cost of Goods sold value problem

Former Member
0 Kudos

Dear all,

In a Make To Stock, material use "Moving average" case.

For example

1-Sep: Moving avg = $30

15-Sep: Sales & PGI (A)

30-Sep: Moving avg = $70

30-Sep: Sales & PGI (B)

First of all, I expect the Cost of goods sold for Sales & PGI (A) should be $30, and $70 for (B).

Is that correct?

However, now I have all the Sales & PGI entries created on 30-Sep,

And the posting date is controlled by the Actual GI Date in the Delivery.

And I found that both PGI value became $70!!!

Could anyone explain that to me??? Or could anyone provide me a solution to this?

Many Thanks!

Best regards,

Chris

Accepted Solutions (0)

Answers (2)

Answers (2)

rasikm_waghela
Active Participant
0 Kudos

PLease check this SAP note. I think this will solve your problem

The following example should demonstrate how such prices can come about. The main cause of the steep rise in the price is that a posting, the value of which is externally predefined, results in a stock quantity which is close to zero. Furthermore, goods receipts exist which are valuated with the current moving average price since no external amount is specified.

Example:

Overview:

Quantity Value MAP

(1) Initial stock: 0 items 0.00 $ 200.00 $

(2) GR for 1st purchase order: +1500 items +300,000.00 $

Stock after (2) 1500 items 300,000.00 $ 200.00 $

(3) GR for 2nd purchase order: +1500 items +330,000.00 $

Stock after (3) 3000 items 630,000.00 $ 210.00 $

(4) GI for the delivery: -2849 items -598,290.00 $

Stock after (4) 151 items 31,710.00 $ 210.00 $

(5) Reversl of 150 itms from (1)-150 items -30,000.00 $

Stock after (5) 1 item 1,710.00 $1,710.00 $

(6) Inventory difference +150 items +256,500.00 $

Stock after (6) 151 items +258,210.00 $ 1,710.00 $

(7) Reversl of 150 itms from (1)-150 items -30,000.00 $

Stock after (7) 1 item +228,210.00 $ 228,210.00 $

Detail:

1. In the following, say for material X price control 'V', the moving average price is 200.00 $ and the current entire valuated stock is 0 items.

Assume you have a purchase order of 1500 items at 200.00 $ each. Moreover, 10 partial goods receipts are now posted for each of 150 items for this purchase order, so that material X then has a total stock of 1500 items with a value of 300,000.00 $.

2. Another purchase order now exists of 1500 items at 220.00 $ each. Here also, 10 partial goods receipts are posted for each of 150 items goods receipt. As a consequence, material X now has a total stock of 3000 items with a value of 630,000.00 $. The moving average price is thus 210.00 $.

3. Now let's look at a delivery of 2849 items. This is valuated as follows using the logic of the quantity to be posted * total value / total stock. This leads to a total stock of 150 items with a value of 31,710.00 $. This does not affect the moving average price, and thus remains 210.00 $ also after the posting.

Now consider the following postings:

4. You reverse the first goods receipt under 1. This reversal would valuate the goods receipt of 150 items with a value of 30,000.00 $. As a result Material X after posting has a total stock of 1 item with a value of 1,710.00 $. The moving average price would thus already be 1,710.00 $.

5. There is now an inventory difference of 150 items without entering an external amount. This posting is valuated with the moving average price and leads to a stock quantity of 151 items with a stock value of 258,210.00 $.

6. You now enter another reversal for one of the partial goods receipts cited under 1. This then is valuated again with a price of 200.00 $. This results in the material having a stock of 1 item with a value of 228,210.00 $.

If you now repeat transactions/events 6 and 7, you can imagine that the moving average price grows rather quickly.

Solution

This effect is both from a business and accounting point of view the logical result if there are a lot of goods receipts which have to be valuated with the moving average price and goods issues which in contrast to this are posted with an externally predefined amount.

You can determine tolerance limits for the moving average price variances in Customizing (Transaction: OMC0). Further information can also be found in the R3 guide: MM - Invoice verification and material valuation.

Former Member
0 Kudos

hello, friend.

the system takes the moving average at the time of PGI, not at the time of sales order creation, for creating cost of goods. this is because actual movement of materials is recorded only when PGI has been done.

in your example, in the sales order created when moving average is still 30, VPRS will show 30; at this point, there is still no actual goods movement. however, if you PGI on Sep 30 when moving average was already 70, it will post this latter figure to more accurately reflect cost of goods sold. when you do billing after PGI, you will notice that VPRS will show 70.

regards.

Former Member
0 Kudos

Hi jonathan,

Thanks for your reply.

For my case, actually it is just a back date input.

The actual PGI date is still 15-Sep.

So, is there any way , or is it possible to make the system post the Cost of Goods Sold base on the value @ 15-Sep?? Many Thanks.

Best regards,

Chris

Former Member
0 Kudos

hello again.

yes. you can actually specify the PGI date when doing the transaction. let's say it's 14 october (today) and you wish to do PGI... you can specify PGI date at 15 Sep. this can be done with single documents when doing PGI within VL02N, or collectively when doing the VL06-series of t-codes. this can also be done in shipments.

check with your FI and MM teammates if previous period needs to be open for you to backdate posting. also, you must be conscious of accounting audit policies and issues.

when inside VL01N or VL02N, go to the Goods Movement Tab and enter the date in the field 'act gds mvmt'.

regards.

Edited by: jonathan yap on Oct 14, 2008 9:29 AM

Former Member
0 Kudos

Hi Jonathan,

Yes, I did that to control the posting date already.

However, the posting value can't be controlled by that.

It is still using the current moving average value

Thanks.

Best regards,

Chris