BW development projects usually take place not in the productive system, but in the development system. Depending on the scope of the project, developments may have to be checked in a quality assurance system, before they are transferred into the productive system. The development system, quality assurance system and productive system form a system landscape.There is a transport system in BW that transfers transport-relevant objects (for example, roles, InfoCubes, InfoSources, DataSources, InfoObjects, InfoPackages, ODS objects, and transfer and update rules) from one system to another.
The objects that you want transport are available in three versions:
Version D - SAP delivered version (valid for Business Content objects)
Version M - modified version
Version A - active version
You can only transport the objects after you have activated them.
To use the transport connection in BW, you have to complete the following requirements: Create a transportable development class in the ABAP Development Workbench (transaction code SE80) (1). Assign this development class to a transport request - when you create the development class, you automatically get a dialog box to this effect (2). At this point, you can create a new transport request or assign one that is already available.
Open the Administrator Workbench and call up the transport request, using the relevant button (3). Choose the objects that you want to transport, from the central window, and drag them with drag and drop to the right-hand window ("Collected Objects"). All new objects have the local development class $TMP by default; before the first transport, assign a transportable development class (4). From this point, the objects are automatically recorded, this means that when changes are made later, only the modified objects in the development class are transported.
Release the individual transport tasks, before you release the transport request. Then release the transport request that is assigned to the development class for transport (5). You do this in the Change and Transport Organizer (CTO), which you call up using the appropriate button.
SAP's Role Concept
The development of the user role concept was based on the idea that employees within a company who have the same tasks may also use the same transactions, Internet links and reports. It makes sure that the individual users are able to see only what they need for the tasks they perform. A role describes the business tasks of its assigned users. If a user is assigned to a user role that is predefined by SAP, the menu designed for his or her task area automatically appears when they log on to the SAP system (for example, transactions, reports and/or Internet links) as well as the authorizations the user needs for his or her work.
SAP distinguishes between single and composite roles. The single roles contain the authorizations that users need to access, for example, the transactions and reports in the user-specific menu. Composite roles consist of several single roles. They do not receive any authorization data themselves, but get the authorizations from the single roles assigned to them. Use composite roles if some of your co-workers need authorizations for several single roles. This means you can assign user groups to one of the SAP composite roles instead of entering the required single roles for each individual user.
Regional sales managers are responsible for planning, organizing and converting the sales strategy.They supervise the sales targets and profitability in the sales department and have an overview of the sales employees and distributors. As well as monitoring the sales activities in general, sales managers can also check cost center activities.
Regional sales managers coordinate the budget and the forecast. They also report on the products and prices. Additionally, they follow the development of customer complaints. The Business Information Warehouse delivers information on the sales pipeline, the sales portfolio, and the budget, by requesting information on sales activities.
From the task of regional sales manager, we derive the activities that can be assigned to this role. The regional sales manager needs, for example, current figures on incoming orders and deliveries, in order to monitor sales activities. The Business Information Warehouse delivers this information in the form of workbooks, which contain different queries. Every role is assigned one or more of these workbooks, which retrieve the required information. Moreover, you can assign R/3 and BW system transactions, MiniApps, Internet and intranet links to a role.
The Profile Generator
Authorizations are summarized into profiles that are directly assigned to the users or to a role. The profile generator is a tool with which the authorization administrator can automatically generate and assign authorization profiles. This simplifies the set up of the authorization environment with the SAP BW implementation guide. Before you create your own roles, you should check SAP's predefined roles for their usability. You can assign the delivered roles directly to the users. To makes changes to the roles, copy the SAP template then make the required changes.
Assigning Users to a Role
The users that you assign are permitted to carry out the transactions of the roles with the corresponding authorizations. The entered transactions are displayed in the SAP Easy Access Menu and in the BEx Browser for the user to see. You can record user's restrictions in the list as follows:
By single entry or by selecting via F4 Help
By multiple selection from a selection list
By choosing 'Org.Management‘
The user names are entered automatically next to the user ID in the second column. In the next two columns you can enter a validity period for the assignment. You can use the relevant pushbuttons to delete or add user IDs.
User Master Comparison
You assign the user to the authorization profile for the role using the user master comparison. Changes to users that are assigned to the role and generating their authorization profiles require a user master comparison. This compares the authorization profiles with the master user records, meaning, profiles that are no longer current are removed from the master user records and the current profiles entered. The status display for 'user comparison' is only green if it is green for the authorization profile. You can also have the user master comparison run automatically when you save the role. To do this, choose Utilities -> Settings from the menu and make the relevant selections for the automatic comparison there. If the option to run an automatic comparison is set when you press save, the process could take a little longer. To carry out the user master comparison, please take note of the information button on the user assignment toolbar.
With the right authorization, a user can carry out certain actions in the Business Information Warehouse. Every authorization refers to an authorization object and defines one or more values for each field in the authorization object. Individual authorizations are brought together into authorization profiles by the system administration with the profile generator. These authorization profiles are assigned to the users in their user master record.
There are preset and open authorizations for the transactions that you assign to the role. You can change the authorization data and then generate an authorization profile with the help of the profile generator. This authorization profile is then entered for the users of the role, when the user master comparison is run. How you set up the authorization check in BW reporting depends on a few conditions. For example, what type of queries are used, how detailed the authorizations are to be checked and how many users there are. The administration for authorizations, roles and user assignments takes place in the role maintenance screen.
An authorization object consists of no more than 10 authorization fields. To define an authorization,specify values for the individual fields in the object. Authorization objetcs can be used as connections between the authorizations, which are checked by the applications, and the given authorizations. You can create as many authorizations as you want for an authorization field, with different values and fields.
The administrator creates authorizations for the authorization objects, which characterize the object fields. There are authorization objects in BW in the Administrator Workbench area and also reporting authorization objects.