Capture Change in historical data from ISU to BW

Question

Hi all,
When any exceptions (EMMA, Work Item, Work Management Activity) are raised in our ISU system we assign it to different person so that they can start working on it and clear the exceptions. We have custom datasouce build around this process and move all delta exceptions to BW on daily basis.
Inside the custom extractor in SMOD, we determine a particular person(SAP userid) is attached to which Position in HR organizational assignement(Transaction PPOM) and end up reporting total no of exceptions against a team in BW or third party system. Please note that we don't have SAP HR implemented in our company.
Now problem is once data is loaded into BW and after that in future if one person  moves from 1 position to another position in ISU, we can't trigger delta as organisational assgignment is totally different process and not integrated to our custom datasource process.This results in wrong reporting done inside BW and also wrong data records sent out to third party from Infospoke.
Initially I thought of moving master data for userid/position to BW and cross link to this information in update/transfer rule. This will not serve my purpose as during the data load a person is sitting against one position. Once data is loaded, Infospoke is run than this person is moved to different position.
Has someone come across this scenario ?
Cheers,
Prashant

Answer 1

Arun,
1. Your position data in ISU always reflects the same state
<b><i>We don't have any control on that - If there are more exceptions sitting against a position than they might move a person to this position to reduce down the number of exceptions.</i></b>
2. You load the master data along with the transaction data for better reporting
<b><i>Even if you move "Organisation assignement" data as master data to BW - that is not  going to serve the purpose.</i></b>
3. You treat the position information as master and not part of text.
<b><i>That's what we are doing</i></b>
4. You could look at getting something like position ID or something and then <i>reference it to your transaction data coming in from ISU.
<b>When data is loaded into BW first time - an exception is assigned to person "P1" in source system. This person is attached to Position "POS1" in source system  - so inside BW we get correct information first time. We run infospoke and send this information to third party. Now after 4 days person "P1" is moved to "POS2" in source system in organisational assignement. This does not trigger delta as this is not related to our process. Even if you move master data information like "userid & position " to BW, this will have latest information "P1 - POS2" in BW. How is that information going to help us as we have already sent this exception with "P1-POS1" to third party.</i></b>
Cheers,
Prashant