Process pending

Process Pending actions update budget templates and budget groups after changes are made to budget dimensions, dimension hierarchies, or budget editing configurations. These actions ensure that budget groups, obligations, and budget balances remain synchronized with the latest budget editing definitions and hierarchy structures.

When process pending is required

  • Non-selective budget templates: Process Pending is always required for non-selective templates whenever a hierarchy or budget editing change affects the budget template.
  • Selective budget templates: Process Pending is required when the configured posting dimension has been used in a transaction, when the specific posting dimensions (Accounting Unit, User Dimension 1, and User Dimensions 3 through 10) have not been used, or when changes affect summary-level budget editing.
  • When Process Pending is required, budget groups are not synchronized with hierarchy changes until the pending action is completed.
  • Process Pending aligns the budget template with hierarchy changes so transactions are validated against the updated budget editing information.
  • Process Pending adds eligible dimensions to the template, creates or updates budget groups, and calculates or recalculates related obligations and budget balances.
  • For selective templates, Process Pending creates and initializes budget groups with existing obligations and unreleased transactions. Budget groups not created during processing are created and initialized automatically the first time they are used in a transaction. See Initialize budget groups for selective templates.
  • For scenarios requiring process pending action, refer to the process pending requirements by scenario table. See Process pending actions.

When process pending is not required

  • For selective budget templates, Process Pending is not required when the configured posting dimension (Project, Account, or User Dimension 2) has not been used in a transaction and the changes do not affect summary-level budget editing.
  • In this case:
    • No pending tabs are shown.
    • No Process Pending action is needed.
    • The system directly creates, updates, or removes the budget groups.
    • Users are not interrupted.
  • Because no obligations exist for an unused posting dimension, no recalculation is necessary.
  • Process Pending is skipped for an unused posting dimension in the following scenarios:
    • Select the Include in Budget Edit option.
    • Clear the Include in Budget Edit option.
    • Add posting dimension to a summary dimension with budget identifier, to an enterprise structure or alternate structure used for budget editing.
    • Remove posting dimension from a budget structure or summary dimension with budget identifier.
    • Move posting dimension within a hierarchy.

When an unused dimension is enabled for budget editing, it becomes immediately available for budget validation. When the dimension is subsequently used in a transaction, the system automatically performs budget editing and creates the associated budget group.

When is a dimension considered used

A dimension is considered used when a transaction or budget is created for it. The system tracks this status in the internal Used by a Transaction (UsedByATransaction) field. After the flag is set, the dimension remains marked as used even if the related transaction or budget is later deleted. This status cannot be changed back.