Creating and Testing Object Dependencies

Object dependencies represent a set of rules that are considered when classifying objects. This means that dependencies and restrictions, for example, are always considered automatically and dynamically.

In SAP classification, object dependencies optimize and automate the classification process, that is, the characteristic value assignment.

• Forbid specific value combinations. Only forklifts with a power of at least 30 kW can have a turbo. If your object, the forklift, has less than 30 kW power, you'll be prohibited from rating it with Turbo.

• Require a characteristic. If forklifts are manufactured at Jungheinrich, the property "The internal term" must be evaluated during classification. This characteristic is otherwise not a required characteristic.

• Set values for characteristics based on other selections. The manufacturer Linde only builds forklifts with automatic transmission. The "Automatic" property is to be selected by the system here.

The following figure shows what the examples above look like inside SAP- System.

How about two more examples? Object dependencies can:

• Require characteristics to be assigned values in a specific sequence. You can prevent users from assigning a country to a forklift until a manufacturer has been assigned.
• Specify default values that depend on a previous valuation. If most, but not all, forklifts manufactured by STILL have a performance of 25 kW, you can use object dependencies to automatically default to 25 kW if STILL is selected. Users can change that setting if necessary, and you can set different default values for other manufacturers.

The following image shows how these object dependencies look in SAP.

The following table summarizes where object dependencies work for managing classes, characteristics, and values.

You can create three types of object dependencies:

• Preconditions
• Selection conditions
• Procedures

The following video introduces these types.

The following table summarizes when to use each type.

One final distinction of object dependencies lies in their scope and regarding usability within a system:

• Global object dependencies are available across the entire system, so they can be used by multiple objects or processes. They can be reused in different contexts wherever the same conditions or procedures are needed. Using global object dependencies promotes consistency and reduces redundancy when you have conditions or procedures that are common and applicable to multiple objects or scenarios.
• Example: Defining a global precondition that ensures user authentication before accessing any resource across a company's intranet portals. This ensures that all applications within the intranet use the same authentication process, maintaining security and consistency.
• Local object dependencies are specific to a particular object or process and are not available for use where in the system. They are not designed for reuse outside the scope of the specific object or process they are tied to. Using local object dependencies when the conditions or procedures are unique to a specific object or scenario allows for more concise and context-specific definitions without affecting other parts of the system.
• Example: Setting a local selection condition that filters data for a quarterly sales report unique to the marketing department. This local dependency is tailored to meet the specific criteria and needs of the marketing team's reporting requirements, without influencing other departments' reports.
  Note

  You'll create and maintain global dependencies centrally, using a special function in the Variant Configuration menu. A global dependency is identified by a name and can be used many times.

  In contrast, you'll define local dependencies for a specific class, characteristic, or characteristic value. A local dependency is identified by an internal number and can't be used again.

Now that you've seen the different types of object dependencies and when to use them, let's look at the syntax you'll use to create them.

The following video introduces the basics. A complete list of operators, expressions, and rules is available at help.sap.com.

A few general rules for creating object dependencies:

• Put character strings used in dependencies in single quote marks ('). Example: COLOR = 'red'
• When you refer to a characteristic or a characteristic value in a dependency, use the language-independent key (name).
• Characteristic names with a hyphen are not beautiful in object dependencies. However, they can be used in object dependencies in which the syntax element SKEY is also used.