cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with subsequent deltas after converting Full requests to Repair.

Former Member
0 Kudos
40

Hi All,

We are working on changing an existing system from loading from multiple extractors directly to a cube to loading each extractor to its own DSO and then combining the data in a 'consolidated' DSO and then on the the cube.

To avoid downtime in the production system when we do the cut-over we have decided to do full loads of historical data up to Sept 2007 and then do delta loading from then on.

So the steps so far have been:

1) Full load of data to low-level DSO's. to 09 2007.

2) Full load of data to 'consolidated' DSO.

3) Convert Full requests in consolidated DSO to Repair Full Requests (see SAP Note 689964).

4) Initialise Without Data Transfer to the 'consolidated' DSO.

5) Delta Initialise from 10 2007 from the source system to the low-level DSO's.

6) Delta from low-level DSO to consolidated DSO.

My problem is with step 6 - no records are loaded into the consolidated DSO after delta load of data to the low-level DSO - the load process runs correctly but tells me that there was no data available.

Can anybody see if there is a problem with my approach - I thought this was the correct way to convert from full loading to delta loading ?

A Merry Christmas and a Happy New Year to you all

Graham

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Graham,

Your approach sounds fine to me. I think the lower level DSOs have not captured any changed records.

-Bikas

Former Member
0 Kudos

Hi Bikas,

Thanks for replying - I thought that my approach was OK.

I can see the 'new' records in the low-level DSO,s (they are Write-Optimized as we will not report at this level) Before updating to the consolidated DSO I can see that the request is not marked in the 'Data Mart Status' in the requests tab (the 'old' requests are marked 'Request Got from InfoProvider').

I have checked the various 'RS' tables for the DSO's and they look OK.

So I do not understand why this data is not selected for update into the consolidated DSO.

I will try and debug the update to see what is happening.

Regards

Graham

Former Member
0 Kudos

Hi All,

If I create a 'Standard' DSO at the low level and go through the process - it works , the 'new' records are updated to the consolidated DSO.

So the problem must be related to Write-Optimized DSO's.

Anybody come across this before ?

Regards

Graham

Former Member
0 Kudos

Hi,

For Write Optimized datastore objects, we don't have table like active, changelog and new data ..it (Write Optimized datastore objects)has only active table..But in standard DSO we have changelog table to update the changes in records to other data target... but here we have only active table,so only fullupdate is possible to update data to other infoprovider..

Hope it helps.

Regards,

Siva.

Former Member
0 Kudos

Hi Siva,

Thanks for the reply.

I understand that there is only an active table with a write-optimised DSO - but delta processing should still be possible at the request level

(SAP Help on Write-Optimized DataStore Objects http://help.sap.com/saphelp_nw2004s/helpdata/en/b6/de1c42128a5733e10000000a155106/frameset.htm)

Since write-optimized DataStore objects do not have a change log, the system does not create delta (in the sense of a before image and an after image). When you update data into the connected InfoProviders, the system only updates the requests that have not yet been posted.

In my case the 'new' request loaded into the DSO have not been loaded into the connected InfoProvider, so it should be processed.

Regards

Graham

Former Member
0 Kudos

Hi,

Check the below OSS notes

1.916743

2.1085456

Hope it helps.

Regards,

Siva.

Former Member
0 Kudos

Hi Siva,

We are on Support Package 15 so I will import the correction as detailed in Note 1085456

Thanks for the help

Graham

Answers (0)