There is no way that a transfer of a part between two stock locations within the same site can increase the inventory value of the part.There is no such functionality in the system.It seems a bit odd that you would be able to increase your inventory value just by moving around stuff in the warehouse.
The default value is hard-coded so it cannot be changed by end users. See code snippet from dlgChangePartAvailabilityControl.cs: rbSameToLocation.Checked = true;You would have to go for a customization.
One way would be to go to the ‘Inventory Parts’ window and query for all parts that have the Frequency Class set as “Slow Mover”.Of course this requires that you have run the “Perform ABC, Frequency and Lifecycle Classification” job.The limits for what is to be classified as Slow, Medium or Fast Mover is defined per Asset Class in the basic data window “Inventory Basic Data” on the Asset Class tab.
The easiest way would be to create a Quick Report that selects stock records that have a last_activity_date which is earlier than 365 days ago. Something like this:select <the columns that you want to display>from inventory_part_in_stockwhere last_ACTIVITY_DATE < SYSDATE - 365
I can only agree with Fredrik Stenén. That number of records in the database tables is not a problem in itself. Oracle handles it well. Performance problems usually is an effect of high transactional volumes rather than big basic data tables. Then also it depends on how you have configured the application, if customer is using serial tracking, handling units, certain inventory valuation methods, big product structures etcetera.
Yes, it is correct. It’s only when you want to change to either FIFO or LIFO that you need to issue and re-receive.
Yes, it will work the same way if you start off with Weighted Average per Lot/Batch. No problem.
If a transport task line has reserved stock with the purpose of moving that stock away to another site, then it needs to act as any other demand that causes a decrease of plannable stock on the site. If the transport task is moving stock within the same site then the transport task line will act as both supply and demand so that the balance will be zero and not extra supply will be generated.
Before changing the Inventory Valuation Method from “Standard Cost” to “First In First Out” you need to make sure that there is no current stock quantities of the part. Otherwise you will get an error message saying “Inventory must be empty before changing to First In First Out valuation method”. So if you have any current stock you can use “Issue Inventory Part” or “Count Inventory Part” to make the On Hand Qty = 0. Then you can safely change to FIFO. Finally re-receive the quantities back into stock using “Receive Inventory Part”. If you receive quantities with zero cost while using FIFO cost method, then the zero cost fifo stack records will be treated just like any other cost. So it will happen at a later point that there will be issue transactions with zero cost. It will not be “balanced”.
If both sites belong to the same company, and if you use ‘Move Inventory Part’ or Transport Task to move this stock from site A to site B, then you can configure Cost Bucket Cross Reference data to connect cost bucket belonging to different sites together. Then you should be able to accomplish what you want.
I can actually not recreate the problem when testing the core solution in our internal environments at IFS R&D. I tested “Move Handling Unit” via WADACO as well as via the “normal” UI, and in both cases it works fine.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.