Using Relational UD Connect Sources (JDBC) 

Aggregated Reading and Quantity Restriction

In order to keep the data mass that is generated during UD Connect access to a JDBC data source as small as possible, each select statement generated by the JDBC adapter receives a group by clause that uses all recognized characteristics. The recognized key figures are aggregated. What is recognized as a key figure or characteristic and which methods are used for aggregation depends on the properties of the associated InfoObjects modeled in SAP BW for this access.

The amount of extracted data is not restricted. To prevent exceeding the storage limitations of the J2EE server, packages with around 6,000 records are transferred to the calling ABAP module.

Use of Multiple Database Objects as UD Connect Source Object

Currently only one database object (table, view) can be used for a UD Connect Source. The JDBC scenario does not support joins. However, if multiple objects are used in the form of a join, a database view should be created that provides this join and this object is to be used as a UD Connect source object.

The view offers more benefits:

·        The database user selected from SAP BW for access is only permitted to access these objects.

·        Using the view, you can run type conversions that cannot be made by the adapter (generation of the ABAP data type DATS, TIMS etc.)