Concept: Amendments to Plan Hierarchies
When you amend a plan that's part of a true plan hierarchy, the changes can impact both the parent and child plan. These changes depend on the amendment type. In general, amendments to a child plan can cascade up to the parent, with some exceptions that depend on whether the amendment is balanced or unbalanced.
For virtual plan hierarchies, you can only amend at the child plan or budget level. Amendment behavior is identical to that of plans and budgets not in hierarchies.
In Workday, you can restrict who has the ability to make unbalanced amendments. Assign these users to a segment-based security group on the
Create Unrestricted Budget Amendment (Segmented)
domain security policy. When they amend, they can edit the Balanced Amendment
check box.Amendment Type | True Parent | True Child |
|---|---|---|
Balanced | Amendments to the parent don't impact the child plan. You can increase the parent plan with no impact to the child plan. However, you can't decrease the parent plan amount below the child amount. | Full debit and credit amounts cascade up to amend the parent plan regardless of the amount on the parent. The only exception is when there's a net zero change to the parent.
Example: You amend a child plan with a 10,000 USD debit for Cost Center 1 and a 10,000 USD credit for Cost Center 2 . There’s no change to the parent plan because the amendment is a transfer from one cost center to another. |
Unbalanced | Only increases the difference of the child plan increase, not the full amount of the amendment debit on the child.
Example: You amend a 100,000 EUR child plan with an amendment debit of 60,000 EUR. The original parent plan was 150,000 EUR, so the new parent plan becomes 160,000 EUR. |
|
Approval Routing
You can configure the Budget Amendment Event
business process definition
and security policy to manage approval and routing for amendments to parent and child plans. You configure the order in which approval takes place by editing the definition steps. Example: To ensure that the hierarchy manager can review the amendment before the individual cost center manager, you can use these security groups in this order:
- Cost Center Hierarchy Manager
- Cost Center Manager
Workday routes amendments to plan hierarchies as a single event in the business process. Even though you can route them to different approvers, any actions taken on an amendment at any level impacts the entire hierarchy. These actions include:
- Approvals: To move the plan to an approved state, approve the amendment at all hierarchy levels. If the amendment in the child plan is net zero within the hierarchy, the parent plan doesn’t route for approval.
- Denials: If an amendment is denied at any level, it’s denied at all levels and the plan won't reach an approved state.
- Send backs: If an amendment is sent back for changes at any level, all plans are sent back and any changes at this point are made on all of the plans. These changes then go through the approval process again. Example: If a manager deletes a line on the child amendment, Workday removes that line from the parent amendment as well.