Split posting types "Purchase expenditure un-invoiced" and "Purchase expenditure for product"
In the Cost management/Inventory management, as posting setup used for the purchase process the posting types
(I) Purchase expenditure, un-invoiced (physical) and
(II) Purchase expenditure for product (financial)
are used.
However, the account is used as an offset a...
P&L main account entries for production postings missing
According to the existing production posting setup in the cost management or inventory management, several WIP posting entries including offset accounts are enabled:
- Estimated cost of materials consumed, WIP
- Estimated cost of materials consumed
- Estimated manufactured...
Vendor group default financial dimensions
In the customer group, using menu item SETUP, the possibility to enter default customer financial dimensions is enabled.
However, in the vendor group this is missing.
The idea is to provide this also to the vendor group such that default vendor dimension values are applied t...
Control of financial dimensions in derived books
In the fixed assets module, derived books trigger the same transaction types as defined in the books setup - derived books.
However, the use of financial dimensions is rather incomplete:
In the fixed asset journal, the entered financial dimensions are not applied in the deri...
Allow exchange rate revaluations in another posting layer
For exchange rate revaluations, the same posting layer is used as it is also applied in the original posting entry.
If there are multiple exchange rates applied for various legislations, it is requested to use particular posting layers for each exchange rate policy.
The...
Allow customer invoice corrections/adjustments
In some industries, the final customer invoice amount is finalised just after weighting and quality analysis on the customer's side.
The idea is to allow customer invoice adjustments at least for the net amount, and also on the invoiced quantity.
The idea is to enable an i...
System architecture: General ledger integration as a general User Interface instead of hard-coded business logic
This conceptual idea refers rather to system architecture:
In projects I face regular issues that the posting behaviour of the system is not sufficient.
The ledger integration framework comes from older Axapta versions is seems a bit outdated.
The idea is to replac...
Accounts structure allowed values - activation - validation against draft versions
When an account structure is modified and activated, the allowed values are validated in order to check if there are overlappings with other accounts structures applied for a particular legal entity. This makes sence fo course.
However, if we have a couple of accounts structur...
Allow vendor invoice corrections/adjustments
The vendor invoice amount may be needed to adjust after invoice posting, i.e. after quality evaluation, additional negotiation, or complaint.
The idea is to allow vendor invoice adjustments at least for the net amount, and also on the invoiced quantity.
The idea is to e...
Advanced rule structures: Apply validation on COMPANY level, not only on account structure level
Advanced rule structures are globally defined and linked to account structures via "account rules". This allows the user to assign advanced rules to several accounts structures.
However, in practise advanced rules (cross-dimension validation rules) apply pretty often to ...