Skip to main content

Hello community,

I have a question about inventory valuation method of Weighted Average, in IFS when we receipt 3 stock in inventory with 3 different price in different dates like :

 First receipt in 6/12 : 1 qty 100 $

Second receipt in 6/13  : 1 qty 150 $

Third receipt 6/14 : 1 qty 200 $

After creating 3 receipts of inventory we want to issue 1 qty stock from inventory in creation date of 6/16 but then change the applied date to 6/13.

When we issue the stock the part cost in 6/16 is 150, but I want when I modify the date applied to 6/13 the part unit cost of issued stock become 125 $ = (100+150)/2 .

Is there any feature in IFS to update Weighted Average unit cost after changing applied date?

Thanks

hi @Mohsen ,

You can try if the Calculate and Cascade Weighted Average Actual Cost function is giving you the expected results. 

Regards,
Dinudu Kankanamge. 

hi @Mohsen ,

You can try if the Calculate and Cascade Weighted Average Actual Cost function is giving you the expected results. 

Regards,
Dinudu Kankanamge. 

Hi @Dinidu Udana ,

I tried the function that you have replied but it didn’t work for my case and I read the help and and I realized that this function is only for Shop Orders.

It would be very helpful if you have any other solution for this situation, Thank you.

Hi @Mohsen ,

It seems for Cascade Update of Cost on Inventory Transactions, If the valuation method on receiving site allows cascade updates, a new cascade will be triggered for the received part from the receipt transaction and onwards.

You can read more about the current capabilities of  Cascade Update of Cost on Inventory Transactions on IFS Clod documentation: IFS Cloud Documentation

Hope this helps. 

Regards,
Dinudu. 

 

Hello;

If you are going to update a specific period, exceed in PL SQL. You can do it with script.

 

update trcost_unit_cost a set a.UNIT_COST= ...

where a.COMPANY= ...

and a.CONTRACT = ...

and a.YEAR = ...

and a.PERIOD = ....

and a.PART_NO = ....

 

NOTE:

Write appropriate parameters instead of ...

In order to update the value of the transaction performed on 6/16 to use the Weighted Average value that existed on the 6/13, there would need to be at a minimum a place (table) in which all previous WA values by date are stored, which there is not.

Reply


Terms & ConditionsCookie settings