Skip to main content

Cost allocation schemas

Access through: Cost allocation > Cost allocation schemas

Cost allocation schemas is part of the cost allocation feature in Snow Optimizer for SAP® Software.

Description​

Cost allocation schemas define the base type of costs and the distribution of costs among cost carriers by using cost carrier hierarchies, cost allocation types, and schema rows.

note

You have to create cost carrier hierarchies before you can create cost allocation schemas .

Before you can use a cost allocation schema in a cost allocation execution, you must activate the cost allocation schema. Upon activation, the cost allocation schema is checked for errors, saved, and marked as ready to use.

Cost allocation types​

Cost allocation types determine the counting base in a cost allocation. The counting base can be users per license type, users only, the CPU time consumed by users, or the dialog steps performed by users. Each cost allocation type can count users aggregated or non-aggregated.

note

When you select an aggregated cost allocation type, you can select the aggregation scheme and the license type hierarchy in the cost allocation execution report.

There are the following cost allocation types:

  • User license type consolidated (aggregated)

    This cost allocation type counts aggregated users per license type.

    note

    This cost allocation type is the most common option because it is equivalent to the SAP named user license model.

  • User license type local (non-aggregated)

    This cost allocation type counts single users per license type on individual data sources.

  • User (aggregated)

    This cost allocation type counts aggregated users and ignores the license types.

  • User (non-aggregated)

    This cost allocation type counts single users on individual data sources and ignores the license types.

  • CPU time consumption (aggregated)

    This cost allocation type counts the consumed CPU time of aggregated users.

  • CPU time consumption (non-aggregated)

    This cost allocation type counts the consumed CPU time of single users on individual data sources.

  • Dialog steps (aggregated)

    This cost allocation type counts the number of performed dialog steps of aggregated users.

  • Dialog steps (non-aggregated)

    This cost allocation type counts the number of performed dialog steps of single users on individual data sources.

note

The CPU time consumption and dialog steps cost allocation types are based on data of the SAP Workload Monitor (transaction ST03N). When you execute a cost allocation, you can select the monthly period for the data.

Schema rows​

Schema rows define the conditions for the cost allocation and the cost carriers to which costs are allocated. Each schema row is valid for one data source type and contains at least one condition and one cost carrier assignment. When you execute cost allocations, the schema rows are processed from top to bottom in the order specified in the cost allocation schema.

Conditions​

Conditions determine the user master data or system data fields that are checked and the condition shapes that are used for checking. If you create more than one condition in a schema row, these conditions are logically combined with AND. If conditions are fulfilled, the costs of the user or aggregation group are allocated to the cost carrier. There are the following options for condition shapes:

  • Fulfilled locally

    note

    This condition shape option is only available if you selected a non-aggregated cost allocation type.

  • Fulfilled on at least one data source

  • Fulfilled on at least one data source, otherwise initial

    note

    This condition shape option is fulfilled if the specified field value exists on one data source while on the other data sources in the exact same field the field value is initial.

  • Fulfilled on all data sources

Cost carrier assignments​

Cost carrier assignments determine the cost carriers and the percentage distribution to the cost carriers.

If you allocate less than 100 percent of the costs to a cost carrier, you can allocate the remaining percent to another cost carrier in the same schema row. Non-allocated costs are automatically transferred to a cost carrier that is called Not allocated. After executing cost allocations, this cost carrier is shown as the lowest position in the cost carrier hierarchy in the cost allocation result.