Documenting Organizational Units within the Project Scope

Use

Which organizational units fall within the scope of your MIC project is defined implicitly in the organizational hierarchy . All organizational units in the organizational hierarchy are automatically in the project scope. In a separate Web application, you can then document for the organizational units in your area of responsibility why those organizational units are included in the project scope. Furthermore, you can document which organizational units you do not want to include in the project scope as well as document the reasons for their exclusion.

Prerequisites

  • In Customizing for MIC , you have defined under Edit Attribute Values the values for the attributeScope Criterion and specified for which attribute values an account group threshold value is relevant (see also the section "Organizational Units in Scope" below).

  • The organizational hierarchy and the account group hierarchy have been created.

  • You have authorization for the task Document Organizational Units in Scope (PERF-SCOPO) .

  • The task is scheduled (see Task Scheduling ).

Features

The documentation of the organizational units falling within the project scope is time-dependent. This means that you can make different settings for different timeframes.

Organizational Units in Scope

For each organizational unit in the organizational hierarchy, you can enter the reasoning behind your decision to include the organizational unit in the project scope. Furthermore, you can select one of the various criteria specified in Customizing. For some criteria, you specify an account group threshold value.

In the BC Set for the IMG activity Edit Attribute Values, SAP delivers the following example values for the attribute Scope Criterion :

  • The criterion Quantitative states that the organizational unit is included in the project scope for quantitative reasons. This could be due to earning a certain amount of revenue, for example. This criterion relates to a threshold value.

  • The criterion Risk states that the organizational unit is liable to certain risks. This criterion does not involve a threshold value.

  • The criterion Aggregation states that an organizational unit is included in the project scope because it is part of a superordinate organizational unit that is relevant. For example, the organizational unit Czech Republic in itself might not be considered relevant, but it belongs to the superordinate organizational unit Eastern Europe , which falls in the project scope for quantitative reasons. This criterion does not involve a threshold value.

Defining Account Group Threshold Values

You can define the threshold values in the Account Group Threshold Values tab page in the Web application Documenting Organizational Units within the Project Scope . In general, only a few account groups in the account group hierarchy are relevant for the project scope.

Example Example

You select the account group Revenues from the account group hierarchy and specify a threshold value of 1,000,000. This means that all organizational units whose last balance sheet shows revenues exceeding 1,000,000 should be included in the project scope.

End of the example.

You define all threshold values in the same currency, which you select from those available in the system. You can use a filter to restrict the currencies displayed in the selection dialog box.

Threshold Value and Actual Value of Last Balance Sheet

If the criterion you select for an organizational unit relates to a threshold value, the Threshold Values tab page appears under In Scope . Here, you can enter the value from the last balance sheet for the account group and its threshold value. You can use the Above Threshold indicator to confirm that the last value from the balance sheet exceeds the threshold value. The system only checks whether the entry you make here is actually correct if you explicitly trigger a consistency check. This means that you can still save the setting even if the status is inconsistent. In this way, you can also set the indicator for an organizational unit that frequently exceeds the value but just did not do so in the last balance sheet.

Example Example

All organizational units that earned revenues exceeding 1,000,000 in the previous year should be included in the project scope. Although the organizational unit USA only earned 980 700 last year, it is included in the project scope because it is of strategic importance and because last year's value falls just below the threshold value.

You can document this example as follows:

End of the example.

  • You enter the threshold value 1,000,000 for the account group Revenues, as described above .

  • You assign the criterion Quantitative to the organizational unit USA .

  • Under Start of the navigation path In Scope Next navigation step Threshold Values, End of the navigation path you establish the relationship between these settings. For the account group Revenue , you enter the value from the last balance sheet. Even if this value falls below the threshold value, you set the Above Threshold indicator for the reasons outlined above.

Organizational Units Outside the Scope

On the Out of Scope tab page, you can list organizational units that you have not included in the organizational hierarchy. Here, you can enter the reasons why you have not included it.