Custom Consolidation
Hi, I have a requirement from business that, want to restrict the roll-up in the entity dimension. for ex: i have Top entity, and all the members underneath are rolling up to Top, but i want to restrict one entity (ex: entity A) not to roll up for particular users which are part of group A. So, when Group A users retrieve the data at Top entity, he/she should see the total number except restricted entity(entity A) and all other can see the total numbers including entity A at Top. is there any way to restrict the roll-ups based on security. Thanks in Advance. any suggestions please, Appreciate your help. Thanks Satish P
Business Rule: Copy data from one cube to another with different cube dimensions
Hello, I have following two cubes in onestream: Volumes Detail All the cube dimensions are the same except for UD1. For volumes, UD1 cube dimension is VintageDim and for detail its FunctionTotal. I am trying to copy data from "Volumes" cube to "Detail" Cube through a Business Rule. I am running this business rule from Data Management Step. The rule runs perfectly but it doesn't copy the data. I don't get any error too. Please can someone help to understand the issue? Public Sub CopyData() Try 'Define the source and target information Dim sourceCube As String = "Volumes" Dim targetCube As String = "Detail" Dim sourceScenario As String = api.Pov.Scenario.Name '1. Pull data from the source cube (Volumes) 'Using a formula to capture the desired data unit Dim sourceDb As DataBuffer = api.Data.GetDataBufferUsingFormula($"Cb#{sourceCube}:S#{sourceScenario}:A#Product_Sales") '2. Convert the data buffer to match the target cube's dimensionality 'This handles the automatic mapping of extended members between the cubes Dim convertedDb As DataBuffer = api.Data.ConvertDataBufferExtendedMembers(targetCube, sourceScenario, sourceDb) '3. Set the converted data into the target cube (Detail) Dim destInfo As ExpressionDestinationInfo = api.Data.GetExpressionDestinationInfo("") api.Data.SetDataBuffer(convertedDb, destInfo) Catch ex As Exception brapi.ErrorLog.LogMessage(si, "EXCEPTION: " & ex.Message) Throw ErrorHandler.LogWrite(si, New XFException(si, ex)) End Try End Sub Thank you
Creating FXRateType by BR
Is there a way to create a FXRateType from a Business rule? FXRate types (average rate, closing rate...) are used to set FX rates in addition to Time, source and destination currencies. In addition to default FXRate types, new ones can be added: Is it possible to create such FXRate types by business rule? Indeed, by business rule (with BRAPI.Finance.MemberAdmin.SaveMemberInfo), we can create a scenario, set parameters, set an existing FXRateType for P&L and for BS, but I've not found how to create a new FXRateType that could be used for this scenario.
Calculation Error "Error processing script: 'A#All = 0 * A#All"
I was running into issues clearing durable data prior to Clearing it so I calculated the data prior to the Clear statement so the data was "calculated", then ran the ClearCalculatedData stmt. It works fine for me, but I have admin access and it works fine for a select few users. But for the majority of users they receive the error "Error processing script: 'A#All = 0 * A#All". I can not easily test in Prod as my hands are tied as far as making security changes. In prod I have other users with the same set of security groups (just pointing to other entity WFs) and they do not receive the error. In our Dev environment I can set up a native user with the exact same security groups as a prod user that fails and I do not receive an error. As for it being an issue with data, I have an entity where 1 user can run it and another can not. And they have the same set of security groups. Does anyone have any thoughts on what is going on? I also thought that the ClearCalculatedData should have been able to clear it (durable data) with the Boolean set to true, but it doesn't. Does anyone have any thought on why the clear does not work w/o calculating the data prior to clearing it? I did see a note about the ClearCalculatedData that the final argument must be true to clkear any data with a storage type Durable. But I'm not exactly sure what this means - can someone clarify that statement for me? This is the code: This is the error:
Monthly vs Quarterly allocation of accounts
Hello, We are trying to automate a simple allocation of specific corporate expense accounts. The accounts allocate to different business based on their contribution to total GP. I currently have two calculations: Account Dynamic Calc - BU GP / Total GP, giving the business GP% UD8 Dynamic Calc - GP% * Corporate Expense Account, giving the expense to be allocated to each BU I run into an issue when data is pulled as either QTD or YTD. As an example, if someone is to pull the data at 2025M3/QTD, it will calculate calculate a separate GP% for the QTD information and complete the calculation. This creates a discrepancy when looking at data monthly vs. quarterly. Instead, I would need it to add together months 1-3 for consistency. (See below table for reference) Is there a way to make a dynamic calculation calculate only at the monthly level and instead aggregate months for other view selections (QTD/YTD)? What is happening What I need Calculation QTD GP * QTD GP% M1 + M2 + M3 MTD M1 M2 M3 Q1 / M3 QTD Q1 / M3 QTD Business GP 100,000 400,000 200,000 700,000 700,000 Total GP 500,000 1,000,000 900,000 2,400,000 4,300,000 GP % 20.0% 40.0% 22.2% 29.2% Corporate Expense 10,000 50,000 20,000 80,000 Allocation 2,000 20,000 4,444 23,333 (29.2% * 80,000) 26,444 (M1 + M2 + M3)While consolidating on Top level getting error in Stored Calc
HI Team, We have created a stored calc and it is working fine at Base and parent entity level, but when we are running at Top entity level and my Time is 2028, at this i am getting below error. could not able to figure it. Can you please help us resolve the issue.
UD8 Dynamic rule to hide derived values. Does anyone have an example of this UD8 calc?
•You can set a text color on the Cubeview (i.e black) so all values show in a single colour, which would override the default grey/black. •You can also use a UD8 dynamic rule to hide derived values in future periods, if necessary.
