cancel
Showing results for 
Search instead for 
Did you mean: 

Logic doubling and tripling values in BPC 7 MS

Former Member
0 Kudos

Experts,

We are using BPC 7 MS and SP5, SQL2008 Server, Recently we are encountering the problems of doubling and tripling of numbers when running the Fx trans, Push logic.

To fix this issue we have defined measures=periodic in the scope of the logic, then it is working as expected for single company code but when processing all the company codes it's doubling and tripling the numbers.

Any help will be greatly appriciated! Thanks in Advance

Accepted Solutions (0)

Answers (4)

Answers (4)

sorin_radulescu
Employee
Employee
0 Kudos

You have to schedule lite optimize every 10 minutes and 20 000 records.

That's measn the package will check every 10 minutes if the wb has more than 20 000.

If yes then the package will run and the rows will be move from wb to fac2.

If not then the package will not do anything.

I don't advice to add optimize task at the end of each package.

It can create conflicts when you are running the package in parallel.

Scheduling the lite optimize you will have more than 20000 records for maximum 10 minutes in case if you run a big logic creating a lot of records.

The import it is adding the records into fac2 table which means you should not be worry how many records will be added.

I hope this will help.

Regards

Sorin Radulescu

sorin_radulescu
Employee
Employee
0 Kudos

Currency trabsalation can run many times but this will not create double values.

You can have the currency transalation into Default Logic and aso you can run DM packages this should not have any impact regarding the consistency of data.

What kind of application do you have Periodic or YTD?

I think the problem is here. Because you are tunning the Currency translation for one type of application but actually your application is not that type.

For example into a YTD application

2009.Jan 100

2009. Feb 100

for LC and we want to translate in USD. (let's suppose the Exchange rate is 1.3)

You actaully will insert into database

for USD into signeddata

2009.Jan 120

2009 Feb 120

Which is wrong because in YTD application that's means you will have for 2009.FEB 240

So actaully the FXTrans has to insert 120 and 0 to be able to have the correct result.

This is an example with what can be wrong. Of course may be is something else in your case but you have to understand what you selected and how you insert the values into database.

Just have a look into logic log from Private Publication\Your User\temp and you will find out what is wrong.

I hope this will help.

Regards

Sorin Radulescu

Former Member
0 Kudos

Thank you Sorin!

The problem was fixed by turning off the lite optimization, We have scheduled lite optimization for every 10 min, When we verified the data in sql database, there were two reporting records being generated with same values in WB Table and fact2 table for one LC record.we couldn't findout the root cause of it and we were not able to recreate the problem again.Not sure what happend.

How often can we run lite optimization?

Can we schedule lite optimization while running the data management packages?

Thanks

PatrickFavre
Advisor
Advisor
0 Kudos

Hi,

You can run Lite Optimize when you have reached maximum 20'000 rows in the tblFactWB.... table. We recommend not to have more than this number.

In addition, you can of course add an Administration Task (running lite optimize) on every package that you are using. But, you will then have to edit them in BIDS (business intelligence development studio).

Hope this will be useful.

Kind Regards,

Patrick

Former Member
0 Kudos

Thank you for quick response!

Yes we have included fx trans in default logic, and executed the fx trans by using a Fx restatement package, (In admin console we have created a logic fx trans (Standard , we didn't change anything in the logic)).

Former Member
0 Kudos

Hi,

So, there lies the problem. You are using DM package to run the currency translation. However, it is present in default also. The default logic is executed everytime there is a data send to the database. So, its running twice - once through DM package and again through the default logic. Either you remove fxtrans from default and run it through DM only. Or, you dont use the DM and keep fxtrans in the default.

Hope this helps.

Former Member
0 Kudos

Hi,

Are you running the currency translation through DM? If this is the case, then you need to check whether you have fxtrans included in the default logic or not. If yes, that answers the question.

Hope this helps.