The primary function of 'A/C Allocation. Update' (GLS130) is to execute a previously generated allocation proposal. Upon approval and execution of the proposal in GLS130, the system's first and foremost action is to create the actual general ledger transactions, known as account entries. These entries are grouped into a journal voucher, which formally records the movement of funds from the source account(s) to the target account(s) as defined by the allocation rules.

B. The budget is updated.

This is a potential secondary effect. Budget updates occur if the account entries are posted to accounts that are connected to a budget, but it is not the initial action.

C. Budget allocations are deleted.

This program creates new transactions based on a proposal; it does not delete existing budget allocations. This describes an unrelated or incorrect function.

D. The transactions that are created on all levels are totaled.

Totaling is a calculation step that is part of the process of creating the entries, not the first discrete action that happens upon approval.

1. Infor M3 General Ledger User Guide: In the section describing the Account Allocation workflow, the guide specifies that GLS120 is used to create a proposal, and GLS130 is used to update the general ledger based on that proposal. The update process is explicitly defined as the creation of a journal voucher in the general ledger file (FGLEDG). (Reference: Infor M3 Finance Management - General Ledger User Guide, section on Account Allocations).

2. Infor M3 Core Financials Courseware (University of Applied Sciences, Würzburg-Schweinfurt): Educational materials covering the M3 financial suite detail the period-end closing process. The account allocation step is described as generating a proposal (GLS120) and then executing it (GLS130), which results in the creation of GL transactions to reallocate costs or revenues. (Reference: Module FMS301, Financial Control and Management, Chapter 4: General Ledger Processing).