Rate table details

Details work together to calculate the charge the rate table returns. Each detail calculates part of the charge, and the details also serve as decision nodes that determine the path to take when calculating a charge.

Each detail is based on a selected business object property used to determine the path to take. For example, a detail for a Building Permits rate table might use the Work Type property of the application object to calculate fees differently for new construction, remodeling, demolition, and so on.

Details can be nested to any depth, with each level using a different property. So after choosing the correct work type, the Building Permits rate table in our example might move on to calculate a charge based on the square footage of the proposed construction. When details are nested, you can choose how the values returned by the parent and child details will be combined, such as adding them together, subtracting the child value from the parent value, or ignoring the parent value.

Usually only one node is processed in each branch of the rate table tree, but certain types of Billing details are handled differently.

See Special rules for Billing details.

There are some important differences between Billing and CDR details, so the processes are described separately. Note also the difference between creating a new detail and adding to an existing one. When you add a detail to a node that doesn't have any details, you can select both the property you want to use and a specific value. If the node already has one or more details, you can select a different value of the same property.