Question:
Hi all,
We have implemented an infocube for time data from SAP HR's Time management module. the problem comes when a user delete a record in SAP R/3 and the record already has been loaded in the infocube in BW. how can i delete this record from de infocube?
We load data once a month and in each load we get the last three months.
please, somebody help me. what do i have to do?
Answer:
hi,
I saw this same issue solved in sales side. we captured this monthly data(in your case 3 months) in other ODS. first we load the data (from R/3) into a ODS then from thre we apply abap and load the data into another ODS from there to cubes. This abap will do a book keeping. that is, it will add minus to the previous months and adds it (key field is date FIScPER).Key fields of first ods ae different from second ODS,but there are difficulties , solved lately with another routine.
reg
DR
Answer:
first we load the data (from R/3) into a ODS then from thre we apply abap and load the data into another ODS from there to cubes.
DR
I use to say that coming from an abap background is the best background for a BW project, but from time to time you have to forget about your abap skills, and thinks more in terms of features in BW !!
1) if your extractor is delta capable, it should handle the deletion itself
2) if your extractor is not, put an ods in the scheme, and perform full loads to the ods, and delta loads from ods to cube ; this scheme will handle your problem itself
Ch
Answer:
CHC,
You mention doing a full load into an ODS and then doing a delta from there. Have you done this yourself? If yes, then I must be missing something.
I tried doing something similar last week but the deleted entry stayed in the ODS. I eventually had to write some abap to compare the new data with the active data and add entries to the new data to reverse any entries that were now deleted.
Answer:
This is a basic concept of delta management by ODS. And yes, I did it myself.
you create doc A in source system,
you full load A in ODS
************************************
you delete A in source system,
you full load in ods
BEFORE activation,
A is present in ACTIVE
A is NOT present in NEW
AFTER activation,
A must be deleted in ACTIVE
to achieve that, the ODS will generate a MINUS entry,
this MINUS entry is also generated in the log table,
in order to send it to the cube
OF course, the KEY of the record will stay in the ODS, but with all amounts set to 0
in the cube, KEY is also there, with first a +amount and then the corresponding -amount to have a total of zero
Ch
Answer:
CHC,
I've just tried it again and it still doesn't work.
Here is an example of what I am getting.
In R/3
PO 1000000 Line item 10
with account assignments
1 A 30 %
2 B 60 %
3 C 10 %
Full load into ODS get the following. (Key of ODS is PO, Item and Seq. No. Acct.Assign )
PO Item Seq. No. Account %
1000000 10 1 A 30
1000000 10 2 B 60
1000000 10 3 C 10
In R/3, delete last account assignment and change percentage for first one.
PO 1000000 Line item 10
with account assignments
1 A 40 %
2 B 60 %
Full load into ODS get the following.
Acitve data
PO Item Seq. No. Account %
1000000 10 1 A 30
1000000 10 2 B 60
1000000 10 3 C 10
New data
PO Item Seq. No. Account %
1000000 10 1 A 40
1000000 10 2 B 60
When I activate the data in the ODS I get
PO Item Seq. No. Account %
1000000 10 1 A 40
1000000 10 2 B 60
1000000 10 3 C 10
Entry for account A has changed as expected but the entry for account C is still there. (In case it makes any difference our BW system is on 30B Patch 16)
Thanks for your help.
Answer:
ok, forgot to mention that the extractor must be the correct type;
I don't remember the exact code from the top of my head, but it must deliver a "after" image or something similar
you are most probably using a standard extractor like 2LIS_02_ITM, which is supposed to handle the delta himself, and therefore is not delivering the right code for 0recordmode when doing a full load, as he assume that you would use its delta capability instead of reinventing the wheel
as a test, redo your scenario, but with a generic extractor, pretty sure it will work fine directly, as it is the case I remember (was before generic extractor had the delta functionality in source system itself) was pretty smooth
Ch
Answer:
The extractor I am using is a generic extractor built on a view of EKKN and EKPO.
Am I missing a setting somewhere?
Answer:
CHC,
Are you there?
Answer:
Normally, an R/3 record gets marked for delete when you delete some thing. So the record still exist however marked with this indicator.
If this is a transaction, a reversal transaction is created to offset the original one.
I think it is best for you to investigate what actually happened to the deleted records in your situation on R/3 side before trying to configure BW ODS & Cube...
good luck
Answer:
what if there are 5 million records? would a full load each time be feasable?