Mapping Separate Organizational Areas 

Use

Companies frequently have separate organizational areas that should also have separate areas in Dispute Case Processing. This means that employees in one area normally do not have access to the dispute cases in other areas. Using Customizing and the authorization concept, there are various ways that you can reflect this.

Procedure

Map Authorizations in One Records Management System (RMS)

You can manage the different areas in one RMS, and within this RMS, reflect the different areas using separate element types and case types.

·        In the authorization objects of the component SAP Records Management, you can assign authorizations per element type.

·        In the component Case Management, you can assign authorizations per case type.

If you create different element types and case types for the different areas, you can use the authorizations to control which of these areas a user can access.

However, the following element types are exceptions to the procedure described:

·         In the element types of SAP business objects added to the dispute case automatically from Process Integration with Accounts Receivable, Process Integration requires that exactly one element type is used for each business object type and logical accounting system. For more information, see the Implementation Guide (IMG) of Dispute Case Processing, under SAP Financial Supply Chain Management ® SAP Dispute Management ® Create Element Type.

You cannot create different element types for different organizational areas for these business object types if the business object type and the logical accounting system are the same. However, you can protect the business object data for SAP business objects from unauthorized access via the authorization protection of the business object concerned.

·         For the element type for dispute cases (in the standard system this is the element type UDM_SPS_CASE), due to the authorization protection you do not necessarily have to create a separate element type for each organizational area. This is because for the dispute case, you can use the authorization objects of the component Case Management to control which activities a user can carry out for each case type.

Map Authorizations in Several Records Management Systems (RMS)

You can set up different Records Management systems for the different areas. In the SAP Records Management component, you can use the authorization object S_SRMSY_CL to control whether a user is to have access to the data of a Records Management system.

The authorization objects of the Case Management component also allow you indirectly to assign authorizations dependent on the Records Management system: In Case Management, you can assign authorizations to the user dependent on the case type. Each case type is assigned to exactly one Records Management system in Customizing.

As described under Creating a Records Management System (RMS), SAP recommends that you use only one Records Management system for SAP Dispute Management. The alternative with several Records Management systems is possible but is not advisable in most cases.

Examples

You manage several company codes in Accounting. The employee of one company code should not have access to the dispute cases of other company codes.

As described above, this can be reflected in two different ways:

Authorizations in One Records Management System

       1.      Create different case types that belong to one Records Management system for the different company codes.

       2.      In the Customizing of the default values for creating dispute cases in Accounts Receivable, assign different case types to the company codes.

       3.      Create different element types for the various company codes – apart from the exceptions mentioned above.

       4.      Limit the authorizations of a user to certain case types and element types. This controls in which company codes a user can access dispute cases.

Authorizations in Several Records Management Systems

       5.      Create different Records Management systems for the different company codes. This means that you manage different case types for the different Records Management systems.

       6.      In the Customizing of the default values for creating dispute cases in Accounts Receivable, assign the case type from the relevant Records Management system to the company codes.

       7.      Limit the authorizations of a user to certain Records Management systems and case types. This controls in which company codes a user can access dispute cases.

As already mentioned, the second procedure is possible, but only useful in a few cases (see also Creating a Records Management System (RMS).