Consolidation Percentage

When i kick off a consolidation it quickly goes to 97% the it takes about 30 minutes to finish to 100%. What is the percentage measuring? Amount of entities? Its definitely not time.

The documention (below) suggests using statistical accounts for storing the porportions. Although your items may be different, I suggest you execute a report on thes to get the required information.
81110000: This itemu2019s value is always 100%. However, you record this value only for consolidation units that are proportionately consolidated. The actual proportion is derived from the sum of items 81110000 through 81160000. (This sum is used in queries.)
81120000: YTD value of the item = proportion of the prior period u2013 1 (for example, 0.75 u2013 1 = u20130.25 = u201325%)
81130000: YTD value of the item = proportion increase at the beginning of the current period
81140000: YTD value of the item = proportion increase at the end of the current period
81150000: YTD value of the item = proportion decrease at the beginning of the current period
81160000: YTD value of the item = proportion decrease at the end of the current period

Similar Messages

BCS - How to check unit consolidation percentage ?

Dear Gurus,
how can I check in BCS system which is the percentage of apportionment between units ?
I need a list of units with their reciprocal apportionment. Do you know a table or maybe can I check it through customizing ?
Thanks in advance!
Antonio

The documention (below) suggests using statistical accounts for storing the porportions. Although your items may be different, I suggest you execute a report on thes to get the required information.
81110000: This itemu2019s value is always 100%. However, you record this value only for consolidation units that are proportionately consolidated. The actual proportion is derived from the sum of items 81110000 through 81160000. (This sum is used in queries.)
81120000: YTD value of the item = proportion of the prior period u2013 1 (for example, 0.75 u2013 1 = u20130.25 = u201325%)
81130000: YTD value of the item = proportion increase at the beginning of the current period
81140000: YTD value of the item = proportion increase at the end of the current period
81150000: YTD value of the item = proportion decrease at the beginning of the current period
81160000: YTD value of the item = proportion decrease at the end of the current period

Question on simple HFM consolidation rule

Hi All,
Could anyone please explain what does the two funtions below do and how they are linked to each other? These funtions are used in Sub Consolidate example in HFM Manual.
dPCon = HS.Node.PCon("") - I know that this function gets the percent of consolidation from current POV
call HS.Con("",dPCon,"") - But I am not sure about this.
Thanks

Hi
Pcon - retrieves the consolidation percentage
Con function multiplies the value of thr Parent Total member by a specified factor and updates either the Proportion member or the Elimination member of the Value dimmension with the result.
regards
alexander

Multi-Currency Entities

If you have two base entities, one which has euros as their local currency and the other is Indian Rupees, then create a roll-up of these two bases that has a currency of Hong Kong Dollars. This roll-up consolidates with another roll-up to form an entity that has the United States dollar as its currency. Can we see the bases in US dollar?

During a consolidation those base entities would not translate into US dollars. During a consolidation entities only translate into the currency of their parent. You could select each of those entities and the USD member of the Value dimension and run a Force Translate to see them in USD but if you need them in USD consistently then that is really not a good solution because you have to run the Force Translate after every consolidation.
A better solution is to create a separate entity hierarchy with one USD parent, eg. "USDParent" into which all the non-USD entities will directly consolidates. You should then place "USDParent" and your existing entity hierarchy under a common parent entity, eg "AllEntities". This way you can simply run consolidations on "AllEntities" and ensure that you get USD amounts on all entities.
Numbers aggregating to "USDParent" or "AllEntities" would be meaningless so you should prevent aggregating data to those parents through a consolidation rule, active status, or a zero consolidation percentage.

Consolidating a percentage

I have to consolidate an entreprise but the parent enterprise doesn't have the 100% of shares so the consolidation is only for a percentage. How can I do it in Oracle General Ledger?

The 'Bounce' file is a file with a format like BOUNCE34324_3432.aiff that FCP says it needs to play the project. needless to say it doesn't exist anywhere....
<
Ah, you were using Soundtrack Pro. Can't help you there, sorry.
<div class="jive-quote">Why doesn't FCP have a 'copy everything into one folder' option? What do people do who want to put everything on an external drive for working elsewhere do?< </div>
You're not going to like the answer and you may even consider this elitist: We practice new and unknown procedures— orprocedures we have heard are funky, like Media Management—on non-critical projects before risking major stuff.
Arrghhh! It's even worse now. Somehow, FCP has reverted my scratch disks to my internal drive. My project seems to be spread across FOUR drives now and I have no idea where anything is stored.< </div>
That only happens when you trash your prefs and then fail to reset your scratch designations after launching the application again.
You will probably need to manually relink everything until the project is completely restored. Make a copy of the project file. Start Media Manager on the copy of the file and use the Copy function.
You could also try copying the entire Capture and Render folder contents from all of your drives to one drive. Make sure it has adequate room before you start. ONce the folders have been copied, eject the drive and disconnect it. Relink to the copied media. Yes, it's gonna take a while. You decide, is it easier to recapture everything or try to consolidate everything?
bogiesan

How to use POwn, PCon or PMin in Consolidation

Dear all experts ,
Do you know how to differentiate consolidation from one account with another? The condition is :
Assets : PCon
Liabilities : PCon
Account (NCI, Capital Reserve, etc) : POwn
Is this possible? Actually when and how to use PCon, POwn and PMin?
Kindly thanks for your attention

Hi,
In order to do what I have described, you have to set ConsolidationRules = "Y" and implement the code to proportionalize accounts in the Consolidate() section of the rules file. Account types cannot help you, because typically equity accounts (capital, reserve accounts and NCI) are defined as of Liability type. Instead you will either test the Label of each account in the DataUnit or test some UserDefined attribute of the account in order to decide which percentage you will use. Note that an account can be proportionalized more than once, for instance:
If vAccount = "Revenue_Reserves" Then
Call Hs.Con("", vPCon, "")
Call Hs.Con("V#Elimination", -1 * vPCon, "")
Call Hs.Con("I#" & vEntity, vPOwn, "")
Call Hs.Con("A#NCI", vPMin, "")End IfThe above code does the following, only to the Revenue_Reserves account:
1. first it proportionalizes the full amount into +[Proportion]+ (destination is the same account Revenue_Reserves)
2. then it proportionalizes the inverse amount to +[Elimination]+ (destination is the same account Revenue_Reserves)
3. then it proportionalizes the part owned to +[Proportion]+ but using the ICP member representing the calculating entity (destination is the same account Revenue_Reserves)
4. finally proportionalizes to a different account, the NCI using the minority percentage (destination is the NCI account)
--Kostas

Error when running consolidation

Hi,
I am running a legal consolidation with this script logic:
*RUN_PROGRAM CURR_CONVERSION
      CATEGORY = %CATEGORY_SET%
      GROUP = %CONSOLVIEW_SET%
      TID_RA = %TIME_SET%
      RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
*RUN_PROGRAM CONSOLIDATION
          CATEGORY = %CATEGORY_SET%
          GROUP = %CONSOLVIEW_SET%
          TID_RA = %TIME_SET%
*ENDRUN_PROGRAM
However, on executing the package I get an error:
RUN_LOGIC:Accounts not found in application COWNERSHIP
COWNERSHIP is the ownership cube but it does have an account type dimension (called OWNACCOUNT).
Has anyone seen this before?
Thanks,
Arnold

Hi,
Are you maintained data in Ownership application? If yes,check OWNACCOUNT contains data or not?
OWNACCOUNT should be maintained as below:
METHOD        Consolidation Method
PCON             Controlling Percentage
PGROUP        PGROUP
POWN           Ownership Percentage
hope it helps...
regards,
Raju

Different tables used in Consolidation Business Rules

I was going through the documentation of different tables that needs to be maintained for consolidation business rules. I am a little confused and need some clarifications.
These are different tables that needs to be maintained for consolidation -
clcELIM - This table will tell what each source account needs to be divided into what 4 destination accounts.
clcRULES - The RULES will tell how this source account needs to be divided (percentage wise as stored in the OWNERSHIP application) into these 4 destination accounts.
clcMETHOD - This table lists down the different methods (along with their types and description) and its used in the clcRULES table
clcELIMH_- What does this table do and where does it come into picture?
*clcELIM_ - Is this same as clcELIM table mentioned above?
clcRULESH - What does this table do and where does it come into picture?
Also, what am I looking at is what is the sequence in which these tables needs to be defined.
For example -
1. clcELIM has a field called RULE whose details are mentioned in clcRULES.
2. clcRULES has a field called METHOD and I_METHOD whose detailes are mentioend in clcMETHOD.
3. .... I am not sure what other tables do? Please fill in the gaps.
Thanks everyone for their help so far.
Ameya Kulkarni
Edited by: Ameya Kulkarni on Sep 18, 2008 7:19 PM
Edited by: Ameya Kulkarni on Sep 18, 2008 7:21 PM
Edited by: Ameya Kulkarni on Sep 18, 2008 7:21 PM

Great explanation Alwin!
Since I am new to SAP BPC world and to tell the truth, consolidation world as well (I am a planning & forecasting guy), my follow up questions are -
(Sorry if the questions are naive).
So according to what you have explained, clcELIM and clcELIMH work together along with clcMETHOD to define the elimination rules for entities.
What do clcRULES and clcRULESH do?
Also you said that these are the SQL tables (clcELIM, clcRULES, clcELIMH etc.) and its advisable not to configure them directly. So what business rules from the administration side update these tables. I am sure the METHOD administration will update clcMETHOD while RULES administration will update clcRULES and clcRULESH, is that right? what about ELIM and ELIMH.
I am asking these questions since I dont have the system to work on yet but will be getting it on Monday next week. Right now I am trying to grasp as much as I can. So if you can send me some snapshots to amey420 at gmail dot com, that will be really appreciated.
Also you can send me the other documents you were talking about. I will shoot you an email as well.
Thanks a lot for your help.
Ameya Kulkarni

Proportionate Consolidation

Hi,
I am using BPC for financial consolidation and I need to do proportionate consolidation for one entity, say Entity J. What this means is that Entity J is owned 50% by the parent. During the consolidation process, Entity J will upload its full trial balance into BPC but the parent will only aggregate 50% of Entity J's trial balance to the parent entity.
Is aggregating only the proportionate percentage owned of an entity to its parent automatically done in BPC?

Hello Lilia
I appreciate Lilia for posting challenging question , which hardly happens in this forum.
Although I used purchase method, I havenu2019t had opportunity to use proportionate consolidation method (as there was no need in all of my projects). However after going through the new stuff available in SEM 6.0, I think you are right in your conclusions (....earlier reclassifications more simpler and suitable when proportionate share is 50%....)
New innovative way seems to be more technically advanced (unlike in earlier versions proportionate share is maintained at customization level) as it makes use of document type and statistical items to record initial proportionate share as well as subsequent changes.
By the way which version do you use?
Cheers
Ambadas

Joint Venture Associate Consolidation Translation Question

Hi All,
I have two problems with our Joint Venture/Associate Entities and the way they translate/consolidate in HFM which I would appreciate some input on if anyone can help:
1. Our implementation of HFM is YTD and each period that period's ownership percentage is applied to the whole YTD balance of the P&L which doesn't account for period on period ownership changes. I believe I can overcome this by forcing HFM to think periodically with closing/opening balances and the consolidation rules but does anyone have a neat/best practice way of doing this?
2. We have movement tables on our Balance Sheet accounts so the consolidation of the JV/Associate's P&L to the Balance Sheet for the parent works on a YTD movement basis, forming the year's closing balance which rolls forward to the opening balance in the next year. This all happens at the Node at [Proportion] and [Contribution]. I need to find a way to make sure that the consolidated amounts are at the current period's closing rate by adjusting the opening balance. I can't see a way of doing this as I don’t think there is a concept of the <Entity Currency> balance at this level. Any thoughts on this? I can think of some really messy roundabout ways of doing this but am again wondering if anyone has already worked this through and come up with a neat/best practice way.
Thanks in advance for any input!

Hi there,
Do you use the default consolidation rules or you have written your own custom rules?
If it is custom rules then both questions can be easily fixed.
Kind regards,
Thanos

BPC Consolidation Account Dimension - R_ACCT X C_ACCT X O_ACCT X P_ACCT

Hi everyone,
I search for all the forum and I didn't find any explanation about the use of the "standards" accounts on BPC, we are using BPC 7.0 for NW.
Why BPC NW differentiate the dimensions depending on which application are going to be included?
For example BPC NW has four dimensions for the account C_ACCT(consolidation), R_ACCT(rate), P_ACCT(Planning) and O_ACCT(Ownership).
In our consolidation project we have the planning front too so at the end we will have only a group chart of account for both.
Can we maintain only an account dimension or is there a technically requirement to mantain three or more account dimensions?
One for Legal App, one for Ownership App, one for Intercompany Matching App and one for planning?
So we should have to use same dimension, an example the C_ACCT, on all application or we have to use each dimension in their owing application and change them with same data? That's the question.
Could someone explain what would we do in this scenario? Please don't send documentation because on every one we read are saying to use different, but how is the maintenance for that, explain this.
Best Regards
Alexandre

Hello Alexandre,
You cannot use the same account dimension in all these applications, because the Rate and Ownership applications are designed to store currency conversion and ownership related data, so it would make no sense to add a financial chart of account to these applications. You could however use the same CoA between your Consolidation and your ICMatching, the idea to have two different ones is that you only have Intercompany data from some of your accounts and you may also want to use different roll-ups of your account to perform you IC Matching.
Here are the 4 account dimension:
- R_ACCT used in the Rate application, contains type of rates (like "END", "AVG)
- O_ACCT used in the Ownership application, contains method and percentage of consolidations (like "METHOD","PCON","POWN,...)
- C_ACCT used in the consolidation application, containt the financial Char of Account (Balance Sheet, P&L, ...)
- P_ACCT used in the planning application, contains account specific for Planning.
You could share the same CoA between your Consolidaiton and Planning, as long as you can defined a common one that fits both purposes
Marcel

Error on legal consolidation

Hi,
we are using BPC 7.5 and we are trying to run a legal consolidation (SPRUNCONSO). The error we get is
CSD-120: No Entity - Method available
I have searched the forum for this error and found references to the ownership application. We do have one, it has data for the companies and period (plus previous year end) in question. I have checked the consolidation method used against those set-up (standard from Appshell, i.e. 90 and 86) and the rules we have created and it all matches and looks valid.
Our accounts in ownership are
PCON
POWN
PGROUP
METHOD
PMIN
Most of the dimensions used in the ownership cube (category, currency, entity, intco and time) are shared with the consol app, only the account dimension is specific to the ownership cube.
Does anyone have any idea what else I can check?
Thanks,
Arnold

Dear Arnold
I think your problem is to assign the consolidation method to the entity
Into the administrator, define the consolidation method inside the business rule library
for example
90 for Holding
86 for Global
70 for proporcional
etc.
You have to create a input schedule, with the follow row and col
ROW
ENTITY
COL
CONSGROUP
O_ACCT
Afther that you can execute the package /CPMB/OWNERSHIPCALC to calculate the indirect plus direct consolithation percentage
I hope this work for you
Ariel

Legal Consolidation Questions

Any suggestions/comments on this will be appreciated.
1) What is the required structure of the ConsolView (Group/Currency) dimension? The logic results in an error "No Group Available." I put in place all property values described in the BPC Guides. The sprunconversion piece for example will run successfully if restricted to "USD". It fails when the Groups are included. What could i be missing.
2) What data should be loaded to the Ownership Application?
I have a POWN account - to load percentage ownership by entity
I have a Method account - to load Consolidation method by entity
Do I need an "Active Account"? What is this? Does anyone have a sample input template i can look at?
3) Is it possible to have the eliminations occur in designated Elimination Entities - similar to Intercompany eliminations where eliminations are performed in the elimination entity below the first common parent.
thanks,
Agnes

Hi Justyna,
the datasrc on which you enter/load your data has to be type I, so the intial setting was correct. Once you change it to type A the system expects that it needs to calculate the values and that there should be no LC values, so whatever you entered gets deleted.
As to why the package did not post anything, I can only guess. One potential problem is the ownership information, the system will only created posting if the ownership information is correctly maintained.
Regards

ECCS : Proportional consolidation data selection

Hello Guys,
I want to include items into the consolidated statement using proportional consolidation (transcation CX26).
My problem is that with this tool i cannot select any item or apply any restricton to my source data : the standard program proportionally consolidate every items without exception.
Does any one of you have a solution to limit the proportional consolidation only to cetain items/posting level...?
Should I use another consolidation of investment tool to fulfill my requirement?
thank you in advance for your help
best regards
pascal

Hi Sylvie,
That's true: apportionement task will apply to all FS items.
If you want to reduce the apportionement scope, you can try to use a reclassification, which uses percentages, and limit the dataset in the triggering parameters.
Kind regards,
Grégoire

Lega consolidation package error

Hi experts,
We are executing the legal consolidation package and we get next error:
"Accounts and entities do not match data in application OWNERSHIP failed"
We have entered the ownershipdata, but the "ultimate ownership calculation" package did nothing, so we guess that is the problem.
Did it happen to anybody? How can we solve the problem?
Regards.

David and Jorge,
Thanks a lot for your reply.
Yes, we followed the procedure decribed in the How To Paper on NW Consolidation.
I will create the message tomorrow. Strange, that there is still no reply from SAP to your message. It is time to escalate the issue.
Were you able to run calculation of Group Shares (CALCOWN) before execution of the Consolidation Package?
There are various sources of information on the function:
On the help.sap.com
"The calculation of PCTRL in the business rule table is supported as same as itu2019s in BPC5.1, however the automatic calculation scripts of PCTRL (% of control) from investor/investee ownership percentage is not supported in the BPC 7.0 version for NetWeaver, so This means the user mustneed manually input the PCTRL % into the ownership application in order to use it for further calculations."
How To Paper
Step4: Run the pre-delivered DM package u201CCalculate Ultimate Ownershipu201D to calculate the ultimate ownership that how much each consolidation group own on each entity. As a result that write back after calculation, the ultimate ownership is stored under the member u201CI_NONEu201D of IntCo dimension, and POWN, PGROUP, METHOD member has the group-own-entity value
described above.
Traing Materials:
Ultimate ownership is a function for legal consolidation used to perform certain calculations used by he application (primarily in regard to calculating the group share of a subsidiary). This information is needed by the business rule library to
properly consolidate the operations of various subsidiaries in accordance with GAAP.
Customers may decide to also enter the direct and indirect pown values instead of having the system derive them.
The concusion is that we can enter Group POWN data manually. We can execute the function, we get a message "Could not write the transaction data successfully. No data found.' Do you have the same problem?
The second question is whether we need to enter PCTRL?
Best regards,
Mila

Consolidation Percentage

Similar Messages

Maybe you are looking for