Public Sector Planning and Budgeting provides predefined accounts, such as:
System Members—Parent member that includes members used for date calculations in predefined business rules. You must keep the System Member parent and its members at the top of the Account dimension hierarchy. Do not delete these members or modify their properties.
Unspecified Account—Member used to track data for which this dimension does not apply.
Human Capital Planning Accounts—Parent member that includes the accounts that capture input in the predefined data forms. The parent includes three categories: Assumption Input, HCP Budgeting Assumptions, and Position-Expense.
Revision Properties—Parent member that includes accounts which capture input for budget revisions. Accounts include Revision Approval Status, Posting Date, and Revision Amount.
Segment Information—Parent member that includes a child which is a Smart List for each General Ledger segment or chart field that is part of your compensation allocation definition. If you want to specify allocation rules using segment or chart field values use these Smart Lists.
Segment Descriptions—Parent member that includes a child which is a Smart List for each General Ledger segment or chart field used in compensation allocations. Use these Smart Lists to specify allocation rules using segment or chart field descriptions.
The child members in Segment Information and Segment Descriptions are a sample of segments such as Account, Entity, Fund, Program, Project, and other user-defined dimensions that you may have in your General Ledger chart of accounts. To set up the allocation detail for positions or employees:
Modify the list of child members to match your General Ledger chart of account.
Modify Smart Lists associated with segment members. Smart Lists must include entries for all base members of the corresponding dimensions. For example, the Entity Segment member is associated with a Smart List that contains all base members of the Entity.
Add additional values here to allocate to an even lower level of granularity than code combination or a chart field combination. For example, you can add “performance objective” as an extra allocation field.