|
One of our client is on BPCS V4.0.05CD using typical module in finance, distribution and manufacturing areas. They were puurely working in the local environment (both purchase and sales wise) so there was no need for them to use MLT. What ever one-off requirement was there, they convered these to the local currency and then booked. They even defined their vendors with their own local currency. Over the years, this one-off requirement increased and they kept on converting these in the the local currency and then booking them. However, now they realised the use of MLT so they purchased this new module to be added on top of the live and runnign BPCS. The questions that arise are: How would BPCS deal with the new currencies for these different vendors? Do they simply revise the vendors's currency and start booking in the foreign currency? If yes, what would happen to the historical data? If no and we need to define these vendors once again with new currencies, how do we relate their balances (before and after the MLT induction)? Or there is some third way? Plsu, what other traps could be there? Their main area that is being affected right now is Purchase - though we can expect down the line that if there could be a sales scenario like this as well. We asked helpline and they said it's not an helpline issue (though true) and somebody suggested we need to prototype - but how and on what basis? Any ideas, any suggestions, any advice is more than welcome! Has anyone come across this situation? Thanks in advance. Best regards, HJ +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.