Multiple SetIDs Within a Control Budget Definition

Commitment Control enables you to share budget definitions across SetIDs and business units.

Sharing a Control Budget Definition Across Business Units with Different ChartField SetIDs

Suppose that you have a budget definition for an organization with three business units (US001, US002, and FRA01) and three SetIDs (SHARE, NA000, and EU000):

Business Unit Code	SetID for CC_ORG	SetID for Account	SetID for Departments
US001	SHARE	SHARE	SHARE
US002	SHARE	NA000	SHARE
FRA01	SHARE	EU000	EU000

In the example, one budget definition, with SetID SHARE and ledger group CC_ORG, is shared by all three business units of an organization.

The key ChartFields are the same for all three business units of the organization, but in the Ruleset Keys grid on the Ruleset ChartField page, each Ruleset established requires three rows: one for SetIDs SHARE and NA000, and one for EU000.

If the control ChartField is designated as DeptID, then the ChartField Values grid on the Control ChartField page requires two sets of data: one for SetID SHARE, to be shared by business units US001 and US002, and a second set of data for SetID EU000 to be used by business unit FRA01. If, instead, you designate the control ChartField as Account, you would need to have three sets of data in the ChartField Values grid, one for each of the three SetIDs.

You also perform the same setup in the Budget Entry Offsets and Source Transaction Offsets scroll areas on the Offsets page and the SetIDs for Excluded Account Types and SetIDs for Excluded Accounts scroll areas on the Excluded Accounts page.

Note:

Balancing, or offset, lines are not created on the budget journals but are created during the posting process and are stored in the commitment control activity log.

Sharing a Control Budget Definition Across Business Units with Different SetIDs for Ledger Groups

If you have business units with different SetIDs for ledger groups, then you must define identical Commitment Control ledger groups for each SetID in order to share a control budget definition.

Suppose that business units US001, US002, and FRA01 are sharing SHARE for their Commitment Control SetID, but each uses its own SetID for GL ledger groups. For example, business unit US001 uses SHARE for GL ledger groups, US002 uses NA000, and FRA01 uses EU000. The business units can still share the control budget definition (because all three use SHARE for Commitment Control), as long as you define three different Commitment Control ledger groups, one for each, sharing the same ledger group name and template but having different SetIDs. They do not need to share the exact same ledgers—one ledger group can dispense with the pre-encumbrance ledger, for example, whereas the others include it. In the following example, the ledger group names are all the same, as are the budget, expense, encumbrance, and pre-encumbrance ledger names:

SetID	Ledger Group Name	Ledgers
SHARE	CC_ORG	ORG_BUD, ORG_EXP, ORG_ENC, ORG_PRE
NA000	CC_ORG	ORG_BUD, ORG_EXP, ORG_ENC, ORG_PRE
EU000	CC_ORG	ORG_BUD, ORG_EXP, ORG_ENC