Show TOC

Define Dependencies

In this IMG activity, you maintain dependencies. You specify the conditions for overhead calculation, and can use the contents of certain fields in an order, cost center, or a business process. The fields that can be used are provided by the system. For example, you can use a dependency from the plant to determine that a defined overhead is calculated per plant.

To define a particular dependency, select from the usable fields those fields that your overhead is dependent on. The fields you select are saved in a condition table in the system.

A dependency consists of one or more condition tables. To complete the definition of the dependency, specify the condition tables in the order (access order) in which they are to be read. Enter the dependencies defined in this way in your costing sheet. The system determines the valid overhead rates during runtime.

Example

You want to make your overhead percentage dependent on the overhead key in the order, and on the order type.
To do this, you can use standard condition table no. "14" for the overhead key, and no. "36" for the order types.

If you have table no. "14" in first place, and table no. "36" in second place, then the system starts by looking for a percentage during overhead calculation. This percentage is dependent on the order type.

Standard Settings

The SAP standard system contains examples of assignments of dependencies to overheads.

Activities

1. To use the dependencies provided by SAP, proceed as follows:
a) Do not change the table assignments.
b) Change the names of the dependencies according to your requirements.
2. If you require new dependencies with new condition tables, you need to define one or more of your own condition tables , and as described below, corresponding new dependencies.
3. To define new dependencies, proceed as follows:

The system displays an overview of all existing dependencies (access sequences).

a) Choose "New entries" to create a new dependency.
b) Enter an identifier and a name for your dependency.
c) Choose "Accesses"
d) Specify a sequence number, and the condition table whose field contents are to be uesd for calculating overhead.
If more condition tables are to be checked, specify these with correspondingly higher sequence numbers in more rows. This type of condition table listing is an access sequence.
Ensure that the tables are assigned in order, ranging from specific to general criteria.
You can use the exclusive indicator to ensure that the system stops its search for more valid records once it has successfully accessed a table. If you do not set this indicator, the system includes all specified condition tables.
e) Select each row with a condition table, and choose "Fields" to specify fields whose contents are to be used for overhead calculation.
f) Save your entries.
g) In the access sequence overview, choose "Utilities" to generate your dependency.
You can create a dependency without generating it. However, if you use a non-generated dependency in an overhead, the system is not able to determine any valid records for this overhead.

Further Notes

If you process dependencies, change a cross-client table. All changes that you make apply to all clients in your SAP system.