Data Transfer Process
The following table gives an overview of the DataSource properties that are relevant for transport, BI Content delivery, and BI Content activation.
Classification |
|
Degree of dependency |
Indirectly dependent |
Type of dependency |
Dependency in object key |
Key technology |
GUID |
Active Object |
|
Transport object |
DTPA |
Object key |
DTP name |
Source system reference in data part |
Field SRCTLOGO in primary table: Reference to DataSource key |
Reference to shadow object |
Field DTP_ORIGINAL in primary table |
Primary table |
RSBKDTP |
Import version |
T |
Object versions in primary table |
A | M | T | Pseudo D | Shadow |
Shadow Object |
|
Transport object for delivery |
DTPD |
Object key |
DTP name |
BI Content version reference in data part |
Field SRCTLOGO in primary table: Reference to DataSource key |
Identification for shadow version |
Field DTP_ORIGINAL in primary table is empty and object version is D |
Primary table |
RSBKDTP |
Pseudo D version |
SAP systems: Is created by replicating the corresponding DataSource or by replicating the source system Non-SAP systems: Is created by activating the source system Alternatively: Is created by executing the function module RS_DTPD_AFTER_IMPORT |
Maintenance |
Special Features
When the shadow object is created, the system makes sure that there is only one shadow object for each combination of source, target and transfer method (full/delta). When developing BI Content you should therefore make sure that you do not crate multiple data transfer processes with the same transfer method because these overlap in the delivery.
More Information
Object Dependencies and Consistency
Classification of Source System-Dependent Objects
Enhancements to the BI Versioning Concept