Metric Set Development 
You create metric sets to group dimension member combinations for the purpose of data entry. As an Entry and Approval administrator, you can create as many metric sets for a particular PAS model as are necessary for optimal data entry and review.
The underlying PAS model controls the list of periodicity/dimension(s) and the corresponding metrics, and whether data entry is allowed at the input level only or at all dimension levels.
Each metric set has its own workflow tasks. Tasks include the required data entry step and any optional approval steps for monitoring the entered data. You define the total number of steps when setting Entry and Approval defaults, but any given metric set may contain all or a subset of the approval steps. When assigning resources, think not only about the user responsible for the data entry but all the steps in the workflow process.
Features
You can do the following to develop metric sets:
Create metric sets with one metric or multiple metrics.
You can group any number of dimension member combinations in a metric set as long as the metrics have the same dimensionality and periodicity. Conversely, a single metric can be split across multiple metric sets.
There is a limit of 500 members (rows) per metric set if users plan to use the Excel spreadsheet for data entry. Exceeding that number requires that users enter data in the Data Entry screen only. The Historical Data and Future Target Data Excel spreadsheets are also disabled for a metric set exceeding 500 rows.
Maintain metric sets by editing them, releasing them, reassigning a workflow step, deleting them, or resetting them. For more information, see Maintaining Metric Sets.
Example
A metric set is created for the Ecosys Count metric combined with the dimensions Account_Type and Territory. The Account_Type dimension has three members: Distributor, ISV_PM, and SP-Sell. The Territory dimension has four members: Asia, Emerging Channels, Europe, and North America.
If responsibility is divided up by territory, four metric sets might be created, one for each territory. Each territory would then contain all three account types. However, when assigning resources, think not only about the user responsible for the data entry but also all the steps in the workflow process. In this example, if the sales manager for Europe is responsible for all accounts in that territory, but there is a different reviewer for each European account, separate metric sets would be required, one for Europe/Distributor, one for Europe/SISV-PM, and one for Europe/SP-Sell.