To adapt existing DataSources to your requirements, you can edit them in this step before transporting them from a test system into a productive system.
In this step, you can also postprocess the application component hierarchy.
DataSource
Transporting DataSources
Select the DataSources that you want to transport from the test system into the productive system and choose Transport. Specify a development class and a transport request so that the DataSources can be transported.
Maintaining DataSources
To maintain a DataSource, select it and choose Maintain DataSource. The following editing options are available:
When scheduling a data request in the BW scheduler, you can enter the selection criteria for the data transfer. For example, you can determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extraction structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
You set this indicator to exclude an extraction structure field from the data transfer. The field is then no longer available in BW when setting the transfer rules or when generating the transfer structure.
Reverse postings are possible for customer-defined key figures. Therefore inversion is only active for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, the data records are interpreted as reverse records in BW.
If you want to carry out a reverse posting for a customer-defined field (key figure), set the Inversion indicator. The value of the key figure is then transferred in inverted form (multiplied by -1) into BW.
You can enhance data by extending the extraction structure for a DataSource by adding fields in append structures.
The Field Only Known in Exit indicator is set for the fields of an append structure; by default these fields are not passed from the field list and selection table to the extractor.
Deselect the Field Only Known in Exit indicator to enable the BW Service API to pass on the field of the append structure to the extractor together with the fields of the delivered extraction structures in the field list and selection table.
Enhancing the extraction structure
If you want to transfer additional information for an existing DataSource from a source system into BW, you first need to give the DataSource extraction structure additional fields. To do this, create an append structure for the extraction structure (seeAdding Append Structures).
Function enhancement
To fill the append structure fields with data, you need to create a customer-specific function module. For information about enhancing the SAP standard with customer-specific function modules, see Enhancing the SAP Standard in SAP Library.
The SAP enhancement RSAP0001 is available for enhancing BW DataSources. This enhancement contains the following enhancement components:
Transaction data |
exit_saplrsap_001 |
Attributes, texts |
exit_saplrsap_002 |
Hierarchies |
exit_saplrsap_004 |
For more information, seeEnhancing DataSources.
As of Release 6.0, the Business Add-In (BAdI) RSU5_SAPI_BADI is available. You can display the BAdI documentation in the BAdI definition or BAdI implementation.
Application Component Hierarchy
NODESNOTCONNECTED is not persistently saved to the database and is therefore not transferred in a particular state to other systems when you transport the application component hierarchy.
Note: Hierarchy nodes created under NODESNOTCONNECTED are lost when you save. After you save, the system only displays those nodes under NODESNOTCONNECTED that were moved to this node with DataSources.
A DataSource is positioned under an application component X. You transfer a new application component hierarchy from BI Content that does not contain application component X. In this application component, the DataSource is automatically placed under the node NODESNOTCONNECTED.
Note: Changes to the application component hierarchy only apply until BI Content is installed again.