TM1 Forum

Hi,

I have this issue that I think is related to Feeders, but not sure how to resolve it, please help.

1. Source Forecast cube where user input against Part is done, has Dim call Part, Part elements rollup to Account.
2. Target GL cube where all GL info is kept, has Dim call Account.
3. I am updating GL cube measure "TRANSACTION" with info from Forecast cube measure "NET SALES"
4. PROBLEM => Forecast cube shows 14 Accounts with NET SALES, expecting GL cube to show the same 14 accounts with the correct numbers TRANSACTIONS. Unfortunately, only 10 comes back to TRANSACTIONS correct numbers, the other 4 come back zero. Why?

Here are more detailed info:

1.GL Cube dim (Company, CompanyPlant, Subdepartment, Account Group, Account, Period, Year, Time, Scenario, mMeasures)
2. Forecasts dim (Forecast Version, UOM, Period, Year, Time, Company, Salesperson, Customer, Part, mMeasures)

Please note that Account and Part are sort of Common between them...

3. On the GL cube side, TARGET, NOTE I USE !ACCOUNT
'Forecast - Business Inputs' << GL Cube-Dim 'Scenario' and 'TRANSACTIONS' is Dim measure

['Forecast - Business Inputs','TRANSACTIONS']=N:
DB('Forecasts','Forecast - Business Inputs','All UOM',!Period,!Year,!Time,!Company,'All Salespeople','Total All Customers',!Account,'Net Sales');

4. On the FORECAST cube side, SOURCE, NOTE I USE !PART cause parts rollup to GL Account
'Forecast - Business Inputs' << Forecast cube-Dim 'Forecast Version' and 'Net Sales' is Dim measure

['Forecast - Business Inputs','Net Sales']=>
DB('Finance GL Expenses',!Company,'Total All Plants','Finance DFT 00-00','5',!Part,!Period,!Year,'Total All Time','Forecast - Business Inputs','Transactions');

I thought this is typical application, what did I miss? Please help! Thanks!

Actually I also tried to put Account as an attribute, and use the following, unfortunately still wrong result. Same 4 Account having problems, not zeros, but wrong numbers.

# DB('Finance GL Expenses',!Company,'Total All Plants','Finance DFT 00-00','5-005',Attrs('Part',!Part,'GL Sales #Account'),!Period,!Year,!Time,'Forecast - Business Inputs','Transactions');

Doris

Hi dlau25@gmail.com,

You might want to consider changing you user name to something that is not a mail account, you'll get spam I expect.

Anyway to your problem

You are trying to feed from !Part to !Account.
The elements of part consolidate into account codes.
My feeder should just work!
but
Feeders only action take place at the N level though so although Part_1 may consolidate into Account_1 the feeder will not work since Part_1 does not exist in the account dimension. What you need to do is get your feeder to step up at run time from the N level Part element to the C level account code.

['Forecast - Business Inputs','Net Sales']=>
DB('Finance GL Expenses',!Company,'Total All Plants','Finance DFT 00-00','5',Elpar ('Part',!Part,1),!Period,!Year,'Total All Time','Forecast - Business Inputs','Transactions');

Note the above will only work if you have a single hierarchy in the part dimension and the account code is the immediate parent of part. For these reasons it is usually better (more efficent and more likely to work all the time) to create an attribute that gives the account related to Part.

['Forecast - Business Inputs','Net Sales']=>
DB('Finance GL Expenses',!Company,'Total All Plants','Finance DFT 00-00','5',Attrs ('Part',!Part,'Account'),!Period,!Year,'Total All Time','Forecast - Business Inputs','Transactions');

You do of course need to make sure that the attribute is maintained.

Anyway hope this gives you a steer in the right direction.

Cheers,

Thanks Steve, that fixed my problem, thanks so much. I shall abandon this user id...