User`s guide

Note:
In this example, you need not complete the remaining fields (Reference Field, ABAP Type, and
Length). Use these fields to add specific information if the structure of the table is not defined in the
data dictionary.
9.
Click Save; then click Back to return to the "View Cluster Record" screen.
Now that you have entered all of the definitions, you have finished creating your new dictionary entry
in the Cluster Definition tool. The "View Cluster Record " screen appears.
When you create a new report with the Open SQL driver, you can report off your customized ABAP
data cluster by searching for the table named B2SALDO.
Although it takes some time to define each data cluster, keep in mind that once the definition is complete
all users can access the cluster—regardless of whether or not they have ABAP experience.
Defining Security for the Open SQL driver
This section shows how to use the Security Definition Editor to define table-level and row-level security
for specific SAP tables when you access them using the Open SQL driver. The Security Definition Editor
enables you to maintain your current SAP security levels when you deploy the Open SQL driver.
Security Definition Editor overview
When you deploy the Data Access component and distribute the database drivers, you allow SAP users
to access the data stored within your SAP R/3, mySAP ERP, and BW systems. By default, the Open
SQL driver provides an open reporting environment where there are no data access restrictions. (You
can, however, easily reverse this default behavior with the Security Definition Editor's Global Lock
feature, which initially restricts users from accessing all SAP tables.
If you need to deploy a security model that regulates users' access to SAP data, use the Security
Definition Editor (transaction /CRYSTAL/RLS) to restrict data access at the table level and at the row
level. The Security Definition Editor defines security for transparent tables, pool tables, cluster tables,
and tables containing data clusters (for instance, PCL2). The restrictions that you specify are enforced
whenever a user attempts to connect to SAP with the Open SQL driver, whether to design, refresh, or
schedule a Crystal report. Thus, in order to design, refresh, or schedule a Crystal report against R/3,
mySAP ERP or BW, users require access to all of the tables referred to by the report.
Data access restrictions that you define using the Security Definition Editor are applied on a per-client
basis. That is, the restrictions you apply affect all users who access SAP using the same client used
to define the restrictions.
In previous versions of BusinessObjects Enterprise, data access restrictions were client-independent.
To preserve restrictions that you defined using earlier versions of this tool, follow the instructions in
Migrating your existing security model before continuing.
Note:
The Security Definition Editor is provided by the Security Definition Editor transport, which you import
into your SAP system when you set up the Data Access.
2012-03-14610
Integrating Business Applications with Crystal Reports