You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 19, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 19, 2026. It is now read-only.
Redesign "Invt. Posting Buffer" similar to "Invoice Posting Buffer" #29858
meaningful_justification: The request lacks meaningful justification. While you mention needing to extend grouping by adding 'Business Unit Code' field, the description doesn't explain WHY this grouping is needed or what business problem it solves. Please provide: (1) A specific business scenario or technical intent that requires Business Unit Code in the grouping logic, (2) The current technical limitation or problem this change addresses, (3) What functionality or capability this enables for your extension. For example, explain whether this is needed for multi-company reporting, legal compliance, financial consolidation, or another specific use case.
Please update the issue with the missing details. We'll automatically re-analyze once updated.
We have an extension that allows multiple legal entities to operate within a single BC company, using the standard Business Units functionality.
For this to work correctly, every financial transaction (G/L Entry) must be tagged with the appropriate Business Unit. This ensures the general ledger accurately reflects activity per legal entity.
We extended the Invoice Posting Buffer with a Business Unit Code field. Amounts are now correctly aggregated by Business Unit before posting, so each resulting G/L Entry carries the right BU.
We need to apply the same logic to the Inventory Posting Buffer (Invt. Posting Buffer) - amounts must be aggregated by Business Unit before posting to ensure inventory-related G/L Entries are also correctly tagged.
Hi Roman Grygoryshchak (@grygoryshchakr),
Thank you for submitting this request.
After reviewing it, we have classified it as a small feature request and added it to our backlog for consideration (Slice 627048: [ALAppExtensions #29858]Redesign "Invt. Posting Buffer" similar to "Invoice Posting Buffer").
At this time, it is not among our highest-priority items, so we cannot commit to an implementation timeline.
Please also note that backlog inclusion does not guarantee delivery. As we continue to evaluate priorities, there is a possibility that the request may ultimately not be accepted for implementation.
We will keep the request under review and will notify you of any decision or status change as soon as it becomes available.
Thank you for your understanding
Activity
AleksandricMarko commentedon Mar 20, 2026
Hi Roman Grygoryshchak (@grygoryshchakr),
Thanks for submitting this extensibility request. To help us process it efficiently, please update the issue to include the required information.
📚 Extensibility Guidelines
Missing Information:
Please update the issue with the missing details. We'll automatically re-analyze once updated.
grygoryshchakr commentedon Mar 26, 2026
Hi,
We have an extension that allows multiple legal entities to operate within a single BC company, using the standard Business Units functionality.
For this to work correctly, every financial transaction (G/L Entry) must be tagged with the appropriate Business Unit. This ensures the general ledger accurately reflects activity per legal entity.
We extended the Invoice Posting Buffer with a Business Unit Code field. Amounts are now correctly aggregated by Business Unit before posting, so each resulting G/L Entry carries the right BU.
We need to apply the same logic to the Inventory Posting Buffer (Invt. Posting Buffer) - amounts must be aggregated by Business Unit before posting to ensure inventory-related G/L Entries are also correctly tagged.
Regards, Roman.
AndersLarsenMicrosoft commentedon Sep 7, 2026
"Invt. Posting Buffer" is in the SCM area
AleksandricMarko commentedon Sep 7, 2026
Hi Roman Grygoryshchak (@grygoryshchakr),
Thank you for submitting this request.
After reviewing it, we have classified it as a small feature request and added it to our backlog for consideration (Slice 627048: [ALAppExtensions #29858]Redesign "Invt. Posting Buffer" similar to "Invoice Posting Buffer").
At this time, it is not among our highest-priority items, so we cannot commit to an implementation timeline.
Please also note that backlog inclusion does not guarantee delivery. As we continue to evaluate priorities, there is a possibility that the request may ultimately not be accepted for implementation.
We will keep the request under review and will notify you of any decision or status change as soon as it becomes available.
Thank you for your understanding