In this step you define objects which protect the CO-PA information system. Each authorization object can consist of up to 10 fields, which you define as you wish. These fields can be the characteristics which have been defined for the operating concern as well as value fields and elements of specific key figure schemes. All the characteristics and value fields which are not specified in the authorization object are allowed.
you can create a number of authorization objects which are linked to one another by selecting up to 10 objects several times. However, it is recommended that you create one authorization object with many fields instead of several with just a few fields. The "AND" relationship between the objects can lead to difficulties when you create authorizations for the individual users. See also "Example for the use of authorization objects".
The system checks the user's authorization before he or she executes a report. If the user lacks authorization for even one object, the system denies access.
You can define a user's authorizations in the Customizing menu under Tools -> Administration -> User maintenance .
The following authorizations are allowed for objects:
The following tables demonstrates how the system checks your entries against an authorization object:
Field content * Y # does not exist
* x x x x
(A,Z) - x - -
X - - - -
# - - x -
: - - - x
You can prevent reports which could slow down your system significantly by creating an authorization object with the characteristics "Customer" and "Product":
1. Customer *
Product 01000000 to 01900000 (or the valid characteristic values)
2. Customer 04500000 to 04800000 (or the valid characteristic
These two authorizations let the user create a list of products for the selected customer and a list of customers for the selected product. However, he or she cannot create a single list of all the customers and products, which would load down your system significantly.
The authorization object consists of the fields "Product" and "Element of the key figure scheme".
An example of how you can use one object instead of two.
A user is supposed to execute two reports: one report on the company 1000 broken down by company codes (which belong to this company), and one report on the company code 0001 broken down by business areas. However, the user is not allowed to execute a report for any random company code.
1st case: You created an object with the fields "Company" and "Company code" and another object with the fields "Company code" and "Business area".
2nd case: You created only one authorization object with the fields "Company", "Company code", and "Business area".
By combining the three fields in the same object, you can achieve greater control than if you create more than one object.
Define your authorization objects for the information system.