!--a11y-->
Data Basis 
Defines the data model for consolidation, which consists of the characteristics and key figures with their respective roles for consolidation.
SEM-BCS uses precisely one RFC destination into SAP Business Information Warehouse (SAP BW), over which transaction data for consolidation is transferred. If you do not specify an RFC destination, the system uses the SAP BW system that resides in the SEM system.
The data streams identify the location for storing the transaction data in Consolidation. Data can be read from and written to all data streams.
The following types of data streams are available:
Data Stream |
Required / Optional |
Explanation |
Totals records |
Required |
This data stream primarily defines the data basis. It defines the characteristics and key figures available in the data model. |
Documents |
Optional |
|
Inventory data |
Optional |
For the elimination of interunit profit/loss in inventory |
Supplier data |
Optional |
For the elimination of interunit profit/loss in inventory |
Investments |
Optional |
For consolidation of investments |
Equity |
Optional |
For consolidation of investments |
Result |
Optional |
For consolidation of investments |
Goodwill |
Optional |
For consolidation of investments |
Activity numbers |
Optional |
For consolidation of investments |
Sequence of activities |
Optional |
For consolidation of investments |
You need to generate or assign the following objects to each data stream type:
· A data target
·
A virtual
InfoCube (if you
want to use BW-Reporting; this
does not include the data streams for activity numbers and the activity
sequence)
Internally, the system uses the following:
· InfoCubes for the totals records. Only new records can be added. Only key figures can be updated.
·
ODS objects for
the documents (journal entries) and other data streams. Here you can also
update characteristics (for example, this is needed for reversal
entries).
To the user it does not matter whether the system uses InfoCubes or ODS objects. Once you select the indicator in the data basis for generating a data stream, and save, the system generates either the InfoCube or the ODS object automatically.

This only applies to the optional data streams. Of course, the system cannot generate the InfoCube for the totals records.
For ODS objects, you can display lists of journal entries in the consolidation system (as you can with InfoCubes). To do this, go to the process view of the consolidation workbench and choose Analysis ® List Data.
Before defining
data streams, you need to have created the InfoCube for the totals records.
When doing this, it is beneficial to use as copy templates (a) one of the
InfoCubes
0BCS_C10,
0BCS_C11, or
0BCS_C50, and (b) the InfoObject catalogs 0BCS_CHA01 (characteristics) and
0BCS_KYF01 (key figures). These objects are part of standard SAP Business
Content.
To define the data streams:
...
1. You allocate the InfoCube for totals records to the data basis by entering its name and saving the data basis.
2. You let the system automatically generate the ODS objects (for the other data streams).
...
a. Enter the name or leave the name field empty.
b. Select the indicator Generated.
c. Generation is started when you save the data basis.
3. You should also have the system generate all virtual InfoCubes (including the one for the totals records).
(Follow the same steps as for generating the ODS objects.)
In addition to the
procedure just described, you also can start the generation by choosing the
function
Generate Data Basis. As compared to the procedure described earlier,
this function has this special feature:
This function allows you to generate the data basis even if you have no change authorization or you are currently in display mode. This is often the case in live systems. However, it may be necessary to change Customizing settings in feeder systems. These settings are then transported to the live system. If only the changes in SEM-BCS are transported, and not the referenced objects in the SAP Business Information Warehouse (SAP BW), you need to synchronize the data model of SEM-BCS and SAP BW afterwards. To do this, you use this function.
Defining
data streams
In addition to those already mentioned, you can assign other objects to a data basis:
· You can assign one or more source data bases to a data basis.
·
You can assign an
InfoObject catalog
for characteristics and one for key figures to enable access to other fields
that, although they exist in the SAP Business Information Warehouse (SAP BW),
are not assigned to any data targets being used (see Additional Financial Data).
You use this option to add more fields for attributes or to add an outline of
assets and liabilities. This option also lets you define an external field
catalog for a source data basis.
·
You can assign an
additional
InfoProvider for
MultiCube reporting. F1 Help contains for more information and an
example.
In the data model, at least one field needs to be assigned to each of the following roles:
· Version
· Group currency key
· Consolidation unit
· Consolidation group
· Partner unit
· Item
· Document type
· Posting level
· Time characteristics (fiscal year and period)
· Value in group currency
Each characteristic with the role consolidation unit also requires one or more additional characteristics with one of the following roles:
· Consolidation unit
· Partner unit
· Investee unit (if you want to use consolidation of investments)
· Upper unit (if you want to use consolidation of investments; optional)
· Consolidation group
You may need other characteristics and key figures depending on which consolidation functions you want to use.
Consolidation Function |
Characteristics and Key Figures Required |
Currency translation |
· in general: Local currency and/or transaction currency (in addition to group currency) · for recording temporal translation differences: Translation indicator |
Interunit eliminations and reconciliations |
· for splitting transaction currency: Key figure transaction currency · for elimination of quantities: Key figure quantity |
Allocation |
· for recording sender and receiver objects: Clearing characteristic |
Consolidation of investments |
· Unit of measure · Quantity · Investee unit · Upper unit (if applicable) |
If you use two characteristics with the role consolidation unit, you also can define an ODS object for custom attributes of combinations of consolidation units in the data model.
The system lists the field attributes that exist in the data basis, sorted by fields. You can define whether each individual attribute is available as a selection attribute for single selections. The following factors affect whether you can modify the setting of the Selection Attribute indicator, or whether the system uses a certain presetting.
Factors That Affect Settings of Selection Attributes
Cause |
Effect |
Example |
Attribute is a characteristic created in SAP BW with a reference to another characteristic. |
a) Attribute that references another characteristic is set as a selection attribute: The attribute referencing the derived characteristic can be used as a selection attribute. a) Attribute that references another characteristic is not set as a selection attribute: The attribute referencing the derived characteristic cannot be used as a selection attribute. |
The partner profit center field is based on the reference characteristic profit center. If you use profit center as a selection attribute, this also enables the use of partner profit center as a selection attribute. |
Attribute is a characteristic that is used in the InfoCube as a navigation attribute. |
The attribute that references the derived characteristic is preset as a selection attribute. This setting cannot be changed. |
|
Here you assign additional fields to the data streams for additional financial data. The assignments depend on the data stream:
· Investment, equity: You can select optional fields. Available are all fields with the role subassignment,plus those fields that are contained in the additionally connected InfoObject catalogs. The system adds these fields to the respectively assigned ODS objects when the data streams are generated.
· Goodwill: You can set the Goodwill in Local Currency indicator. You do this on the Settings tab page on the Customizing screen for a consolidation area that belongs to the data basis. After you set this indicator and generate the goodwill ODS object, the system automatically adds further fields to the ODS object that are required for the Goodwill in Local Currency function.
On this tab page, you can define how the system should access the characteristics of your data basis and how to process the entry of values.
·
Authorization
check for characteristic values: Set this indicator to have the system check the
authorization for the characteristic at the level of characteristic values.
For example, this lets you determine that a user is allowed to display or
enter data for a specific consolidation unit. If you do not set this
indicator, you can grant or deny authorizations only for all values of the
characteristic. You can set the authorization check at the characteristic
level for all characteristics contained in the data basis. You use SAP
Authorization Management to define the actual values to be checked during an
access (see
Users and Roles).
For more information, see Authorizations for Master Data.
· Validity Check: You use this to define whether to have the system check the validity of the values that are entered for a given characteristic. You can have the check be dependent on version, time, or combinations of version and time. When you request a validity check, the system only displays and evaluates the data records of the data basis for a given characteristic if they coincide with the selection criterion that was chosen (for example, fiscal year).
This is where you define the texts for the fields in the data basis to be used as column headings in logs, audit trails, and output lists. You can use this function to modify the names of individual fields to better suit the terminology used in your organization or to adjust the lengths of the names.
You have a great degree of freedom in your choice of names. In particular, there are no length restrictions for the names of fields. However, it does not make sense to have the name of a field exceed the output length of its values by more than a few characters. The output length is also displayed to help you determine the name length.
If you make no entries here, the system uses the field names delivered by SAP.
