Skip to content
This repository was archived by the owner on Oct 19, 2026. It is now read-only.
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

Closed

Description

Why do you need this change?

We need to extend grouping implemented in table 48 "Invt. Posting Buffer" by adding "Business Unit Code" field.

Describe the request

Redesign "Invt. Posting Buffer" to have "Group ID" field as primary key:

    field(1; "Group ID"; Text[1000])
    {
        Caption = 'Primary Key';
        DataClassification = SystemMetadata;
    }

and BuildPrimaryKey procedure

procedure BuildPrimaryKey()
var
    GroupID: Text;
begin
    GroupID := ... ;

    OnBuildPrimaryKey(GroupID, Rec);

    "Group ID" := CopyStr(GroupID, 1, MaxStrLen("Group ID"));

    OnAfterBuildPrimaryKey(Rec);
end;

PS. Code is taken from table 55 "Invoice Posting Buffer"
Internal work item: AB#627048

Activity

  1. AleksandricMarko commented on Mar 20, 2026

    @AleksandricMarko
    Contributor

    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:

    • 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.

  2. grygoryshchakr commented on Mar 26, 2026

    @grygoryshchakr
    Author

    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.

  3. added
    SCMGitHub request for SCM area
    and removed
    missing-infoThe issue misses information that prevents it from completion.
    on Mar 26, 2026
  4. added
    SCMGitHub request for SCM area
    and removed
    FinanceGitHub request for Finance area
    on Sep 7, 2026
  5. AndersLarsenMicrosoft commented on Sep 7, 2026

    @AndersLarsenMicrosoft
    Contributor

    "Invt. Posting Buffer" is in the SCM area

  6. AleksandricMarko commented on Sep 7, 2026

    @AleksandricMarko
    Contributor

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    SCMGitHub request for SCM areaextensibility-enhancementNew feature or request related to extensibility

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions