Comments
Agree we would like to use this feature to code our assets according to accounting rules, this works nicely with the feature where you make it a mandatory field depending on what asset transaction type is selected however the only downfall is that it is not available on the main screen or easy to upload on the asset template. Shame as it is a really good feature.
This is a major gap in the approval functionality. The primary objective for getting documents approved is to avoid them being distributed before approval. When approvals are in place and a document (purchase or sales) falls in the criteria, printing/emailing should be blocked until the approval is processed.
Along with this functionality is the need to override a source warehouse for an item so that master planning creates planned orders in the correct warehouse. Currently the only way to do this is to define a source in each warehouse and then to create an item/warehouse coverage for any items where this is an exception. An item default is needed to eliminate the need to create an item coverage for each warehouse where demand could coming from.
While updating your Local Chart Of Accounts, section "Consolidation", we need to manually type the consolidation GL Account (D & Cr).
We should be able to select the Consolidated Chart Of Account in the Consolidation Company, in stead of typing it.
We have already linked to the consolidation API.
I do not agree with this functionality. I would like to suggest that for specific Posting Groups (such Customer, Vendor, Banking, Inventory, Fixed Assets). Once a posting has been done, the system should block you when you are trying to post to another GL account. The problem could raise that your subledgers (example Customer Ledger Entries - AR Aging) doesn't match the GL accounts - Accounts Receivable.
I would suggest to have at least the option in the setup to choose that you want to avoid, to post to multiple posting groups on a customer, vendor, bank, inventory and fixed asset.
The "centralized" gl accounts should also been setup "Direct Posting = No"
In order to guarantee the data compliance