Exam Bundle

The control evaluates the authorized annual allocation while retaining period rules for other budgets. That would verify a different case: A capital purchase can use available annual budget, but budget checking rejects it because funds availability is limited to the current month. It does not verify the required corrective action: Activate the applicable budget control setup and relevant document/source coverage.

The exception report attributes cumulative overages by user and cost center. That would verify a different case: An authorized budget override is used repeatedly on small purchases, but management cannot track the cumulative overage. It does not verify the required corrective action: Activate the applicable budget control setup and relevant document/source coverage.

Budget availability checks separate the two departments' balances despite shared expense main accounts. That would verify a different case: The same amount appears available to two departments because budget control rules omit Department from the tracking dimension set. It does not verify the required corrective action: Activate the applicable budget control setup and relevant document/source coverage.

Budget availability can be checked over a configured time span distinct from the posting month. That explains a separate case: A capital purchase can use available annual budget, but budget checking rejects it because funds availability is limited to the current month. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget control rules can enforce separate available-fund pools for selected dimension combinations. That explains a separate case: A government grant budget must be isolated from an operational budget, but both use one broad budget control rule. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget control tracking scope depends on included financial dimensions and rule combinations. That explains a separate case: The same amount appears available to two departments because budget control rules omit Department from the tracking dimension set. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile budget dimensions to responsibility-center reporting. That safeguard is aimed at a different risk: The same amount appears available to two departments because budget control rules omit Department from the tracking dimension set. It does not most directly prevent recurrence of: Budget control only evaluates transaction sources and dimensions included in its active configuration.

Test an end-to-end requisition-to-invoice lifecycle under budget controls. That safeguard is aimed at a different risk: A purchase order fails budget checking because the commitment is counted against both its requisition and the finalized purchase order. It does not most directly prevent recurrence of: Budget control only evaluates transaction sources and dimensions included in its active configuration.

Reconcile transfers and revisions in budget control calculations. That safeguard is aimed at a different risk: Budget checks return an unexpected amount because budget fund availability excludes budget transfers that were already approved. It does not most directly prevent recurrence of: Budget control only evaluates transaction sources and dimensions included in its active configuration.

Create the intended new-cycle budget planning scenario and controlled initial amounts rather than editing the prior-year approved plan. This fits a DIFFERENT issue within Configure and manage budget planning: One budget plan scenario carries prior-year balances, but new-year departmental plans should start with a clean approved baseline. It does not address the current problem, whose mechanism is: Budget planning processes coordinate distributed contributors through organization hierarchy and workflows.

Set up budget planning allocation rules to distribute the shared amount to approved departments. This fits a DIFFERENT issue within Configure and manage budget planning: A corporate budget plan should allocate a shared facilities amount by headcount, but manual spreadsheet splits are inconsistent. It does not address the current problem, whose mechanism is: Budget planning processes coordinate distributed contributors through organization hierarchy and workflows.

Configure distinct budget planning scenarios for baseline, optimistic and conservative projections. This fits a DIFFERENT issue within Configure and manage budget planning: The planning team needs optimistic and conservative scenarios, but overwrites the base scenario each cycle. It does not address the current problem, whose mechanism is: Budget planning processes coordinate distributed contributors through organization hierarchy and workflows.

A planning roll-up aggregates the division under its new authorized parent without double count. That would verify a different case: A division was reorganized, but budget plan summaries still roll up to its old parent department. It does not verify the required corrective action: Configure a budget planning process with an appropriate organization hierarchy and participant stages.

Allocated plan amounts reconcile to the corporate source and specified percentages. That would verify a different case: A corporate budget plan should allocate a shared facilities amount by headcount, but manual spreadsheet splits are inconsistent. It does not verify the required corrective action: Configure a budget planning process with an appropriate organization hierarchy and participant stages.

The new planning year contains separate baseline values and the prior year's approved plan stays intact. That would verify a different case: One budget plan scenario carries prior-year balances, but new-year departmental plans should start with a clean approved baseline. It does not verify the required corrective action: Configure a budget planning process with an appropriate organization hierarchy and participant stages.

Budget planning workflows govern state transitions separately from data entry. That explains a separate case: A planning workflow advances before the manager reviews the department's numbers because no approval stage exists. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget plans and budget registers are related but separate data/process stages. That explains a separate case: A plan is approved but its values are not reflected in the executable budget register used by budget control. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Budget planning scenarios represent alternative planning measures, not versions to overwrite each other. That explains a separate case: The planning team needs optimistic and conservative scenarios, but overwrites the base scenario each cycle. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile plan approval totals to posted budget register before enforcing controls. That safeguard is aimed at a different risk: A plan is approved but its values are not reflected in the executable budget register used by budget control. It does not most directly prevent recurrence of: Budget planning processes coordinate distributed contributors through organization hierarchy and workflows.

Review hierarchy effective dates before reforecast runs. That safeguard is aimed at a different risk: A division was reorganized, but budget plan summaries still roll up to its old parent department. It does not most directly prevent recurrence of: Budget planning processes coordinate distributed contributors through organization hierarchy and workflows.

Archive approved plans before starting annual planning cycles. That safeguard is aimed at a different risk: One budget plan scenario carries prior-year balances, but new-year departmental plans should start with a clean approved baseline. It does not most directly prevent recurrence of: Budget planning processes coordinate distributed contributors through organization hierarchy and workflows.

Configure disposal transaction posting accounts for gain, loss, proceeds and asset balances. This fits a DIFFERENT issue within Implement and manage fixed assets: An asset disposal gain is posted to the general sales revenue account instead of gain on disposal because its posting profile lacks the transaction mapping. It does not address the current problem, whose mechanism is: Fixed asset groups define classification and default values affecting subsequent asset processing.

Add the missing authorized book mapping and configure its own depreciation attributes. This fits a DIFFERENT issue within Implement and manage fixed assets: A fixed asset depreciates under one book but not under a required second book because the second book is not associated with the asset. It does not address the current problem, whose mechanism is: Fixed asset groups define classification and default values affecting subsequent asset processing.

Configure fixed asset posting profiles for acquisition and relevant asset group/book transactions. This fits a DIFFERENT issue within Implement and manage fixed assets: A newly acquired vehicle posts acquisition cost to an expense account instead of fixed asset cost because posting profiles are incomplete. It does not address the current problem, whose mechanism is: Fixed asset groups define classification and default values affecting subsequent asset processing.

One asset retains related book values with appropriate reporting treatment and no duplicate acquisition. That would verify a different case: An asset must track local and group reporting books, but users create two unrelated asset IDs and the underlying acquisition is duplicated. It does not verify the required corrective action: Create or correct an appropriate fixed asset group and its required default properties.

Asset ownership and balances appear in the proper legal entity after authorized transactions. That would verify a different case: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not verify the required corrective action: Create or correct an appropriate fixed asset group and its required default properties.

Both project and purchase order test acquisitions create the correct asset/book accounting outcomes. That would verify a different case: A company acquires assets using both projects and purchase orders, but some transactions post to unmatched asset groups because default asset fields are missing. It does not verify the required corrective action: Create or correct an appropriate fixed asset group and its required default properties.

Fixed asset identifiers require governed number sequences across the relevant legal entity scope. That explains a separate case: A newly acquired production machine is assigned the wrong fixed asset number sequence and duplicates an existing identifier in a subsidiary. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Fixed asset disposal accounting has specialized transaction types separate from ordinary product revenue. That explains a separate case: An asset disposal gain is posted to the general sales revenue account instead of gain on disposal because its posting profile lacks the transaction mapping. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Fixed asset posting profiles determine the ledger accounts used by asset transaction types. That explains a separate case: A newly acquired vehicle posts acquisition cost to an expense account instead of fixed asset cost because posting profiles are incomplete. The reported finance issue instead requires the more directly applicable cause in the keyed answer.

Reconcile intercompany asset transfers and ownership evidence. That safeguard is aimed at a different risk: An asset was created in the wrong legal entity and finance plans to fix the reporting by editing its name only. It does not most directly prevent recurrence of: Fixed asset groups define classification and default values affecting subsequent asset processing.

Compare planned depreciation under each book to approved accounting policy. That safeguard is aimed at a different risk: Financial statements require straight-line depreciation but a fixed asset book uses reducing-balance method. It does not most directly prevent recurrence of: Fixed asset groups define classification and default values affecting subsequent asset processing.

Test beginning, middle and end-of-month acquisitions. That safeguard is aimed at a different risk: Fixed asset books have the correct depreciation method but no depreciation start convention, producing inconsistent first-month charges. It does not most directly prevent recurrence of: Fixed asset groups define classification and default values affecting subsequent asset processing.