Case Studies

Finding Why a Workday Adaptive Planning Elimination Posted to the Wrong Fund

Finding Why a Workday Adaptive Planning Elimination Posted to the Wrong Fund

Platform: Workday Adaptive Planning

Scope: internal allocation eliminations in a fund-based planning model

The business problem

Finance reported that eliminations for one fund and one cost centre were landing in a different fund. Two internal allocation accounts were affected, one revenue and one expense. Fund-level reports were wrong for both funds.

Existing architecture

The model eliminates internal allocations through a dedicated elimination cube. Each elimination row has a linked filter that selects the source data, and separate attributes that set where the elimination posts: the account, the cost centre and the fund.

Why it happened

We checked the net zero list sheets and the account setup first. Neither caused the problem.

The cause sat in the elimination cube. On the two rows for this fund, the linked filter pointed to the correct fund, but the destination fund attribute pointed to another fund. The source and the destination are two independent fields, and on these rows they disagreed.

Design decision

We corrected the destination attribute on the two rows and changed nothing else. No formula, loader or account needed to change, so we kept the fix as small as the cause.

Implementation approach

  1. Confirm the exact combinations that post wrongly: fund, account and cost centre.
  2. Rule out the mapping sheets and the account configuration.
  3. Open the elimination rows for the fund and compare the source filter with the destination attributes.
  4. Correct the destination in the sandbox tenant.
  5. Ask the finance owner to validate both accounts before promotion.

Controls and validation

The fix went into the sandbox tenant first. Promotion to production waited on user acceptance testing by the finance owner who reported the issue.

Outcome

The destination attribute was corrected in a controlled test environment. Finance validation and production promotion follow.

Lessons learned

Scope of the outcome

Root cause identified and corrected in a test environment; production deployment not asserted.


EPMLogic | Implementation insight based on an anonymized scenario. Exact operational amounts and client details are intentionally omitted.

Workday Adaptive Planning
Related Insights

More from the architecture desk.

Reconciling Gross Expense Actuals in Workday Adaptive Planning: Scope, Mapping and Currency
Case Studies

Reconciling Gross Expense Actuals in Workday Adaptive Planning: Scope, Mapping and Currency

Platform: Workday Financial Management and Workday Adaptive Planning Scope: gross expense actuals loaded into an expense...

Read more
Planning a Safe Workday Source Change for Personnel Planning
Case Studies

Planning a Safe Workday Source Change for Personnel Planning

Platform: Two Workday tenants and Workday Adaptive Planning Scope: The worker and compensation feed into a...

Read more
Fixing Period-Coverage Gaps in Workday Adaptive Planning Exports for Power BI
Case Studies

Fixing Period-Coverage Gaps in Workday Adaptive Planning Exports for Power BI

Platform: Workday Adaptive Planning and Power BI Scope: outbound exports of expense actuals, forecast and budget...

Read more