statement:Original Works，when reproduced, please indicate the article from
The SAP division is tooTechnology Blog ( Bo/guest/Park www.cnblogs.com): Www.cnblogs.com/jiangzhengjun，and indicate the original source of the article in the form of a hyperlink，Otherwise the legal liability will be investigated! Original link: http://www.cnblogs.com/jiangzhengjun/p/4297274.html regardless of the DSO, the data in the table will have the record mode field, the new table and active table of the field is uploaded by the data source, and Chang log is the BW system when activated by the data extracted from the change The original data in log is obtained , and the post-
image, A- image are recorded by
X-image + post -image, and R-image and D-image are recorded by their own image type .
( Note:the data in thepush-mode Delta-queue also comes with a recording mode, which is recorded by the SAP system when the user maintains the data (and different delta proess incremental processing modes, Will cause the delta-queue to have different recording modes for the data to be stored, but do not know whether the pull mode of the Delta-queue is also taken? Need to test The following is the source of the above file data source to test the recording modeCreate a new standard DSO to pump the data from the file into this DSO:
Before activation, the data in new is as follows, when record mode does not have data:
After activation, the data in the active table and change log is as follows:
The record mode in the active table is also empty, only the record mode in the Change Log table has data, and it is a new image, which is automatically set by the system's own comparison data, but the record in the new table and the active The value of mode is provided by the data source itself, but the file data source is not available at this time, so it is empty
Modify the data in the file and then draw:
After pumping to the DSO activation, and then see the active table and change log table data as follows:
Since 500 that record has not been modified, so this time, the change log does not increase the data associated with it from the changes log can be seen in the DSO when activated, the system will take this time to pull up the data and the Change log table in comparison, Then generate the data of the modification process (such as the former image), it is because of the change log table, so the data source of the AIE incremental processing method is not directly pumped into the accumulated type of DSO and cube, but if the intermediate through the standard coverage of DSO, you can then draw the data toThe accumulated type of DSO and Cube
problem leads : Through the DSO key value field default coverage characteristics, the above for modification and new will support very good, if the data in the source of data is physically deleted, then how to let DSO also know? in fact, in transformateion, we can see that the record mode is actually a technical field, so as long as we have a field of record mode in our data, It is also in fact the record mode in the new and active table that can be pumped to the DSO:
Below we add a field such as record mode on the file data source above:
And then add a column of Record to the file.:
Then transformateion do a field mapping, before the mapping needs to change the constant to the direct allocation rule mode:
Before you start transmitting data, the data in the PSA is as follows:
After running the packet, the data in the DSO table is as follows:
at this point, we find that the
N-image (
new image ) unification becomes the
x-image , that is, modifying the result like
Found that there is a missing data in the active table, that is, the data of the
R image is
deleted .
an R image is added to the Chage log, which is the data that was deleted in the active stream. But 1001, 1002 did not change, because the turn of the record mode is a new item and latter, and finally they are regarded as latter that is modified, but the data has not changed, so the log table on these two records do not record any logLet's test it here.a like(Add-on), before you do, you need to re-create another DSO, its Amount field conversion rules need to use the additive type (by default, is covered type, such as the above DSO):
Modify the contents of the file and modify it to
Post-Image：
Before testing, delete all previously pumped data in the PSA in the data source request to run the packet again:
Run DTP to view the active table of the DSO:
After running the packet again with the DTP, the active tablefound amount
cumulative (twice times) :
In the Change Log table, the post-image value is the accumulated value (twice times the value) instead of the value set in the passed-in file:
Modify the file again below, using
a like：
After running the packets and DTP, the new table: the data in the active table becomes
3 times Times：
Change Log table
After you run the packet again with the DTP:
Then modify the file intoR Image：
Running Packets with DTP:
at this time there is no data in active, found
all deleted :
(reason: Because it is the R image, the original intention is to delete the record, so the data in the active table is finally deleted, since it is deleted, the R recoil amount is not important, it is important to delete the corresponding data)
at this time the log table data will not be deleted (because it is a log, it is not directly deleted, it is to record the entire process of data changes), but the final result will be the same as the active table data results, that is, the final cumulative result is required to punch to zero, so finally added the following three recoil, But the recoil is not the value in our file, and how much is the original (that is, the data is deleted):
DSO recording mode record
