Page 1 of 1
Loading dimension from SAP BW system?
Posted: Mon Oct 24, 2011 9:22 am
by swati_phadtare
Hi
I want to load "dealer"dimension from BW system to TM1. We have around 4 lacs elements in BW system in a "dealer" dimension (out of which I need only 50000 in TM1). I have created a TI process to load these elements from BW to TM1.
I should only get those dealers in TM1 which starts with "01". How can I put this condition in TI which loads data from BW system?
Kindly Suggest.
Thanks & Regards
Re: Loading dimension from SAP BW system?
Posted: Mon Oct 24, 2011 12:35 pm
by tomok
Well.....you could put in a conditional test in the TI to skip the elements that start with '01' like:
Code: Select all
IF(SUBST(Dealer,1,2)@='01');
ItemSkip;
ENDIF;
but why not just modify your SQL query to exclude those items from the data source? That would be infinitely more efficient than reading through each record in a TI process and selectively ignoring those you don't want.
Re: Loading dimension from SAP BW system?
Posted: Tue Oct 25, 2011 5:17 am
by swati_phadtare
Thanks for your suggestion, but I am not able to put sql condition here as we have to map target dimension with source dimension when we pull data from BW system.
Other thing is when I try ItemReject in TI, process keeps on executing & server hangs.
Is there any other way to achieve this?
Re: Loading dimension from SAP BW system?
Posted: Tue Oct 25, 2011 9:15 am
by qml
First of all, I think the right code for you should be:
Code: Select all
IF(SUBST(Dealer,1,2) @<> '01');
ItemSkip;
ENDIF;
Secondly, when you say "when I try ItemReject in TI, process keeps on executing & server hangs", what do you mean and how have you reached the conclusion that server hangs? I Think it's much more likely that the TI just keeps executing (without the server "hanging"), and, considering your rather large data source, it's nothing surprising it takes time.
The only way to "fix" this is to apply any conditions directly in the query on the Data Source tab to make your data source smaller, like that:
Not sure why you don't want to use this approach.