Fellow BW-ers,
I am struggling with a situation with a custom development. In this development, transactional data and characteristics associated with a sales document are loaded to a DSO, and then delta loaded to an infocube. The delta process works quite well for key figures - changes to records in the DSO produce negative key figure values and then positive key figure values for each document. But... changes to characteristics produce somewhat more complicated results. I suspect that I should simply avoid using these transactional characteristics, and instead use them as navigational attributes instead.
As a sample:
Document 1234 , status A, value $100
Loaded to the DSO, then to the infocube, which contains:
Document 1234, Status A, value $100
And then, some days later, the document is changed.
Record 1: Document 1234, Status C, Value $300
Loaded to the DSO, then delta loaded to the infocube, which now contains:
Record 1: Document 1234, Status A, Value $100
Record 2: Document 1234, Status A, Value -$100
Record 3: Document 1234, Status C, Value $300
Is there a way I can avoid reading Records 1 and 2, perhaps using a filter in a Bex query, so as to avoid reading the old Status of Document 1234 ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.