Content Browser: Object Relationships   

Technical Name: 0BCT_CB_1

Technical Data

DataSource Type

Transactional Data (Transaction Data)

Application Component

0BCT_CB

Available as from OLTP Release

BI Content 3.5.2 Add-On

Delivery with

BI Content 3.5.2 Add-On

RemoteCube-Capable

No

Delta Compatible

No

Archivable

No

Verifiable

No

Prerequisites

None.

Use

This DataSource provides transactions that represent relationships between Business Information Warehouse objects.

Delta Update

The extractor supports only the “full update” mode of extraction.

Fields of Origin for the Extract Structure

Fields in the Extract Structure

Description of the Field in the Extract Structure

Table of Origin

Field in the Table of Origin

CB_DS

DataSource

RSOLTPSOURCE

OLTPSOURCE

CB_IP

InfoProvider

RSDCUBE, RSDCHABAS, RSDODSO, RSQISET

CB_IPT

InfoProvider Type

Not Applicable

CB_IS

InfoSource

RSISOSMAP

ISOURCE

CB_OV

Object Version (A or D)

Not Applicable

CB_RFLD

Role Menu Folder

AGR_HIER

OBJECT_ID

CB_SRCSYS

OLTP Source System – not available in current release

Not Applicable

CB_VQ

View / Query

RSZWVIEW, RSRREPDIR

VIEWID, COMPID

CB_VQT

View / Query Type (View or Query)

Not Applicable

CB_WT

Workbook / Template

RSRWBINDEX

WORKBOOKID

CB_WTT

Workbook / Template Type (Workbook / Template)

Not Applicable

CB_IPDIR

Flag: Query To InfoProvider Direct Relationship

Not Applicable

Not Applicable

Particular Features of the Extractor

This extractor uses function module extraction. The underlying extraction process involves many steps. The resulting data delivered by the extractor represents the relationships between various objects. The following properties apply to the resulting data:

     It represents objects that deal with transactional data. Therefore, for example, a Text DataSource will not be included, unless the target Characteristic uses flexible update.

     The relationship between Workbooks or Templates and their source View or Query is represented. If the source is a view, the indirect relationship to the query is also stored

     The relationship between an InfoProvider and all Views/Queries that use it (directly, or via another InfoProvider such as a MultiProvider) is stored

     The relationship between an InfoSource and an InfoProvider is stored.

     The relationship between an InfoSource and DataSource is stored.

Therefore, it is possible to list all the DataSources that feed a Query using this data, but not all the Queries that use a DataSource (only those queries built directly on an InfoProvider whose InfoSource is connected to the given DataSource are available).