About rate tables

• You use a rate table to determine a specific value, a rate, for a particular transaction to be processed with the help of allocation rules.
  The table includes rates for all combinations of factors that might affect the rate, such as particular tasks, account groups, stock items involved, employees participating, etc.

• You can also create distinct rate sets for individual steps in allocation rules by utilizing various rate types for each step. The rate or value obtained from the rate table for every transaction can be referenced in the allocation rule formulas as @Rate and employed as a multiplier, an addend, or a constant.

• You can create one rate table to be used for all projects or multiple tables to be used for different projects.

• If you want to define rates of different types, such as expressed as factors (1.2, 1.0, 0.2), defined as amounts (€1000), or defined as hourly rates (€100 per hour), create a separate rate table for each type.

You fully configure a rate table in four stages by using the following windows:

1. Rate tables (PM204200):
   To create a rate table. Initially, you just create an empty container for a new rate table; later, in another window, you will specify the rates and date ranges.
2. Rate types (PM204100):
   Create rate types by establishing empty containers for them.
   Think of a rate type as a new dimension within the same table.
   Commonly, various rates are used for allocating labour costs, revenues, and expenses.
   At this point, determine the number and types of rate types needed; later, when creating allocation rules, assign different rate types to specific steps of allocation rules, allowing for step-specific rates.
3. Rate lookup rules (PM205000):
   To create sequences, each of which is a set of factors.
   Any combination of the following factors can be specified for a sequence: Project, Project task, Account group, Item, and Employee.
   
4. Rate table maintenance (PM206000):
   To actually specify the rates (with their date ranges) for each sequence or for each combination of particular factors.
   You can define rate codes on the fly to define multiple rates for the same sequence.

For rate tables, sequence include multiple factors that may affect the rates.
You define sequences by using the Rate lookup rules (PM205000) window as follows:

• A sequence determines the factors that influence the rate, such as projects, project tasks, employees, account groups, or items.
  For instance, if tasks are a factor, unique rates can be applied to specific tasks or to certain tasks within particular projects when specific employees work on those tasks.
• The order of numeric identifiers for sequences is crucial, as it determines the sequence in which the system searches for rates. Starting with the first sequence (smallest number), the system compares the factors specified in transactions with those defined by the current sequence. If there is a match, the rate is assigned to the @Rate parameter. If not, the system proceeds to the next sequence (by number). If no matching factors are found for the last sequence, the system follows the selected option for that allocation rule step. Options include: Set @Rate to 1, Set @Rate to 0, Raise error, and Do not allocate.

A rate table may include different sets of sequences for different rate types.

A rate code serves as an extra dimension in a rate table, allowing for simpler configuration. By utilizing rate codes, you can decrease the number of sequences needed for each rate table-rate type pair, making it easier to specify all the necessary different rates.

A rate code serves as an extra dimension in a rate table, allowing for simpler configuration. By utilising rate codes, you can decrease the number of sequences needed for each rate table-rate type pair, making it easier to specify all the necessary different rates.

For example, suppose that you want to define a specific rate for each employee working on a project.
You have two possible ways to create such rates:

• Create as many sequences with the Employee check box selected as there are employees to have a separate rate. In the rate table, enter one rate code for all these sequences.
  For each sequence, select a particular employee and enter the rate.
• Create only one sequences with the Employee check box selected.
  In the rate table, for each employee with a specific rate, enter a separate rate code, select the employee, and enter the rate for this employee.

The total number of code-sequence combinations remains the same for both methods. However, using rate codes allows you to reuse the same sequence for defining multiple rates. It is important to note that even when using different rate codes, combinations of specific factors must be unique within a sequence. When searching for rates, the system will search through all rate codes.

By using the Rate table maintenance (PM206000) window, you can finally fill in the rate table for each rate type that you are going to use in the allocation rules.

• Enter the rates along with the date range when they are effective. On the tabs for various factor types (which show up if defined in the rate lookup rules), provide specific factors like projects, tasks, employees, items, or account groups.

• The rate application condition can be defined using the following rules: When conditions apply to specific projects, items, employees, or account groups, they are connected using OR operators. However, when conditions involve different rate factors, they are connected using AND operators.