How to avoid minority interest dividend calculation

Hi,
I have a requirement to avoid dividend postings to minority interest share portion. We want to post 100% of the dividends to the group company. However the current group shareholding is only 75% hence the system is posting 25% of the dividends to the minority share group. The consolidation of investment method used is pooling of interest method.
Please see the attachment for the screen shot, click on this link and click on the download file button to download the screen shot :- http://wikisend.com/download/289316/Minority%20share%20dividends.JPG
Edited by: FICO Consultant on May 5, 2011 2:41 PM
Edited by: FICO Consultant on May 5, 2011 2:42 PM

Hi,
I cannot delete the distribution of dividends in the location of values because the delete button is not enabled for me. I tried to clear the FS item allocated and did the COI but the system still doing the distribution of dividends somehow. Dont know how. Is this the correct place to deactivate this activity?
I went to the activities screen where i can set the default sequences of the CI activities. But i cannot remove the distribution of dividends activity there too.
Here is the screen shot :-
http://wikisend.com/download/520076/cannot%20delete.JPG

Similar Messages

Minority Interest on Ownership Change

Dear All,
How to achieve Minority Interest on Ownership Change in the same financial Year.
For Example: For April Ownership and Minority interest is 60% and 40% respectively and PROFIT is YTD 1000.
On that period, Minority will be calculated at 40% and value would be 400.
Next Period, May month - ownership has been changed to 80% and 20% and profit value is YTD 2000.
In this period, Minority should be calculated on two values, which 40% is on 1000 (april's value) and 20% on 1000 which May's value.
Total would be 400 + 200 = 600
How to achieve this in HFM. If we uncheck ConsolidateYTD in scenario view, then system will calculate minority as per the requirement. But, if we uncheck this, then ZeroviewforAdj and ZeroviewfornonAdj has to be periodic and any adjustment requiered, then only periodic value needs to be inputed. But, data load is happening with YTD values (TB values been loaded with YTD value). Any impact on Flow(P&L) / Balance (Balancesheet) accounts if we use periodic values for adjustment.
If we check ConsolidateYTD, then minority interest will be calculated at that month's minority interest % on YTD value.
If month is april then, 40% on 1000 and if month is may then 20% on 2000 = 400 ( which is not right on profit value).
Also, if we uncheck ConsolidateYTD, and having ZeroviewforAdj and ZeroviewfornonAdj with YTD will not give right figure.
Is any other way to approach or achieve minority interest calculation as shown above.
Kindly share your ideas and approach.
Regards,
Raj-

Hi Raj,
Although the manual mentions that ZeroView and ConsolidateYTD should be aligned, I don't think that Oracle should impose this. The reason is that the combination ConsolidateYTD = No with ZeroView = YTD works alright provided you keep some precautions. To make it clear lets consider this: ZeroView can impact two things:
1. future periods, not having and real data loaded (we can just ignore these periods - why bother consolidating them? so this is no problem).
2. intermediate empty periods, which is the case, when we keep both quarterly and monthly data in the same scenario, then periods intermediate to the quarters are left empty.
In any case, ZeroView impacts periods that you don't want to load data, if data is loaded to the period, there is no issue with calculating the consolidated numbers.
So, our discussion is limited to the second case, where we have quarterly data, intermediate months are zero ConsolidateYTD = No and ZeroView = YTD. Then as soon as you set the right consolidation options, your numbers will consolidate correctly in quarters. Lets say that we have numbers in March with 60% and June 40%. Provided that you also make April and May Active and apply the 40% from April through June, then everything calculates correctly. However, if you apply 60% to April and May and 40% to June or leave Active = No for April and May, then numbers will not calculate correctly.
In fact this is my preferred configuration, and it has never let me down.
-- Kostas

Minority Interest calculation and consolidation

Hi people. i am new to HFM. I am kind of stuck with Minority Interest calculation and the consolidation of it. Now after looking at different posts on the minority interest calculation here , i am still confused if we could use the calculation expression for Minority Interest calculation within Sub Consolidate() or should we include it in Sub Calculate(). Please find below the script that i am working on.
SCRIPT :
Sub Consolidate()
Method=HS.Node.Method("")
PCon=HS.Node.PCon("")
POwn=HS.Node.POwn("")
vMIN=1-HS.Node.POwn("")
PMin=PCon-POwn
Dim strAccount,i
Set DataUnit=HS.OpenDataUnit("")
NumItems=DataUnit.GetNumItems
For i=0 to NumItems-1
Call DataUnit.GetItem(i,strAccount,ICP,Custom1,Custom2,Custom3,Custom4,Data)
If Method="Holding" Then
Call HS.Con("",PCon,"")
End If
If Method="Global" Then
If StrAccount = "281100" Then
Call HS.Con("A#281100",PMin,"PMin")
'Call HS.Con("A#281000",vMIN,"")
Else
Call HS.Con("",POwn,"")
End If
End If
'If HS.Account.IsConsolidated(strAccount) and Data0 Then
'If Data0 Then
'HS.Con "A#"&strAccount,POwn,""
'If StrAccount = "281100" Then
'HS.Con "",PMin,""
'End If
'End If
'End If
Next
End sub
Sub Calculate()
HS.EXP "A#281100 = A#CapitalStock - A#Investments"
End Sub
My Doubts :
1. Is the expression correct for Minority Interest calculation ?
2. If so can we use it in Sub Consolidate() ?
3. Should the Minority Interest consolidate to its parent using PMin ? If so kindly provide the appropriate expression.
Looking forward to some help. Thanks in advance.

Hi,
If I got it correctly, you don't want the A#281100 calculation to happen for your holding company. There is a preferable way to do your consolidation that avoids involving the Calculate() altogether. So scrap your Calculate and write this Consolidate() instead:
Sub Consolidate()
Method=HS.Node.Method("")
PCon=HS.Node.PCon("")
POwn=HS.Node.POwn("")
vMIN=1-HS.Node.POwn("")
PMin=PCon-POwn
Dim strAccount,i
Set DataUnit=HS.OpenDataUnit("")
NumItems=DataUnit.GetNumItems
For i=0 to NumItems-1
Call DataUnit.GetItem(i,strAccount,ICP,Custom1,Custom2,Custom3,Custom4,Data)
If Method="Holding" Then
Call HS.Con("",PCon,"")End If
If Method="Global" Then
If StrAccount = "CapitalStock" Then
Call HS.Con("",POwn,"")
Call HS.Con("A#281100",PMin,"")ElseIf StrAccount = "Investments" Then
Call HS.Con("",POwn,"")
Call HS.Con("A#281100", (-1) * PMin,"")Else
Call HS.Con("",POwn,"")End IfEnd IfNextEnd subWith this code, the minority interest will calculate only for entities using the Global method.
I did not drive you to this solution immediately in order to avoid to confuse you, as well as because this does not address the issue of Calculation() running at many Value levels.
Regards,
--Kostas

Minority Interest Calculation in Consolidation

Hi,
How is Minority Interest Calculation Handled in a Group Company or in Consolidated Balance Sheets. How it can be shown in SAP?
Reagrds

What we did is set up a calc in the calculate subroutine that caculates minority interest and puts it to the elimination company.
If HS.Entity.UD1("")="RETAILCONSELIM" Then
HS.Exp "A#MINORITYINTSUBS=(E#SUSSERCO.A#NETINCOME.W#Periodic"&{All_Top}&"*.1482)"
End IF

Calculation of minority interest in matrix organization structure

Hello-
We are currently implementing sem-bcs and have a matrix organization structure in place. We use company code and profit center as consolidation units. Company code being the currency carrying unit.
We are facing an issue in minority calculation-
Let us take the following example -
Investee A - books equity in pc A
Holding entity B books investments in pc B
The above information were entered in AFD and was also pulled in BCS as RFD..
The first consolidation happens as per our expectations.
For subsequent consolidation, the retained earnings account (additions movement) could have multiple profit centers. The system calculates minority interest correctly for combination of retained earnings addition @ PC A. However for all other combinations (I.e retained earnings for PC other than A), the system treats the entire amount as minority interest (even though that's not the case)..
Kindly advise.
Thanks!

Hi,
Thanks for your reply...
The PC hierarchy is already in place..I maintained Additional Financial Data for the other combinations (of Cons Unit and PC) with 100% share and zero value. The system considered that and calculated minority interest correctly.
I wish to know if the above approach is ok..
Thanks

IFRS requirement , minority interest calculation and accounting for in SAP.

hi ,
We need financial consolidation with full consolidation , equity interest, minority interest as per IFRS requirements along with inter company eliminations
Will it be possible thru ECCS or we need to go to SEM suite.
thanks
KR

Hi,
With Virtual Ledgers in Ecc 5.0 and 6.0 we can customise few things and connected to ECCS module.
If you have BI,SEM modules implemented then it is better to go with Consolidation modules rather than ECCS.
Thanks
G Bharathi

How to avoid Moire Effects (jiggered still pictures) using iM and iDVD.

This is a discussion going on forever and forever in this forum. I had the problem of bad looking slideshows myself, and I am hearing the same tips over and over again that just don't work. This is what I found out on how to avoid moire effects in your still images, when you want to edit a slideshow using iMovie - and I personally think, this explanation makes a lot of sense.
Try it on your own and you will have had the last bad looking still image slidehow on the TV screen ever!! Here we go:
Like everybody here I am talking about the process of creating a slideshow incuding movie strips in iMovie to get as a final result a DVD with menus and such using iDVD.
And the common problem with stills and iMovie 5.02 are the so called jiggered pictures iMovie creates. Call it a moire effect, if you'd like.
Whenever full resolution still images are importet from iPhoto into iMovie, the quality that iMovie will spit out in the end is disgusting. Period. Just disgusting.
It has nothing to do with that iMovie does not display it properly on the Monitor or we are just in preview mode - the results are bad there and will be bad (maybe even worse) on the TV screen.
There is no SIGNIFICANT difference between wether the pictures are imported with KB on or off, whether they are imported as still frames or as video clips using iMovie "import" function. iMovie can treat the color fairly bad, overprocesses the pictures and - worst of all, the moiree effects you will see in the endresult are just very very bad. It is worse when the pictures are panning a lot (KB).. This is true for every picture containing a lot of detail (Trees, Forests, horizontol lines (stairs) etc.) - not so bad for closeup face shots, unless that person is really old
There is no SIGNIFICANT difference on the result by how the iMovie project is fed into iDVD. When the movie is sent to iDVD using the iM command "send to..." the quality is worse (and you let iM render when it asks) than if the movie is dragged into the iDVD window - but again, the difference is not significant. The result will suck. The DVD will also look bad, when the iMovie is exported has high res quicktime first, before imported into iDVD. Again, its slightly better that way, but not significant.
Whenever a slideshow is created in iPhoto and than exported to iDVD (or via being a quicktime movie through iMovie into iDVD) the result will be however stunning. But that totally defeats the purpose of iMovie and the degree of freedom of designing slidehows in a very appealing manner.....
The problem I think lies in how iMovie processes still images. And this is not a bug, but more of a mathematical/programmatical problem. iMovie has to REDUCE THE RESOLUTION of your still. A 2000x3000 pixel image @ 300 dpi(roughly the dimensions of a 6 MP image) has to be downsized to a TV image (NTSC or PAL, whichever) which has a resolution of approximately 480x640. HD is accordingly higher. The amount of pixels has to be reduced. iMovie can do that. NOT GOOD. But it can. The problem starts when the picture is panning around (KB). iMovie makes a let us say 5 second movie @ 30 fps out of one still image. Almost every frame will be slightly different from the previous one due to the used KB effect. So, the routine of iMovie does this downsize calculation for each single frame - and it removes each time different pixels from the still image, due to a slightly different source still image. Got it?
Now, when you look on how moiree effects occur (which is some weired math in it's own) than it makes sense, that we see all this jiggereing in horizontol lines of high res. patterns.
I found that if I reduce the size of each image in Photoshop (or Photoshop Elements) prior to importing it into iMovie, the quality of the final product that iMovie and subsequently iDVD spits out in the end is AMAZING (reduce the dpi to approx. 72, so the image resolution is roughly 480x640). This is not a difficult process, because both programms (PS and PSE) handle BATCH PROCESSING. Just let the Mac work for a couple of hours or so.... its WORTH IT (and don't forget to make copies of the high res originals beforehand... :D).
(before you resize, find out about how to properly resize and rescale an image!!!!)
I am slightly annoyed that I found that out after producing a long long long long and really good slightshow, that is watchable but looks REALLY cheasy and cheap).
I hope this helps out.
Waenni
Mini G4 Mac OS X (10.4.8)

I agree that iMovie's still image quality is embarassingly bad and has many bugs.
Even with no Ken Burns, the sharp images tend to flicker on a TV because iMovie doesn't blur them properly.
And as you very well described, iMovie's Ken Burns produces uneasy zooms/pans because the subpixel rendering is, uh, suboptimal.
iMovie's immortal rendering bug when exporting non-Ken Burns'ed images to iDVD/tape doesn't make things any better.
Yes, bicubically downsampling the input images to 640x480 or adding gaussian blur to the megapixel input images takes care of the flicker and uneasy zooms/pans, but as a side-effect the maximal zoom-ins are then TOO blurry.
The best workaround is to use Photo To Movie's higher quality export setting. It has the best quality rendering engine (I recently compared it to Still Life and FotoMagico). Disclaimer: I'm just a satisfied customer of Photo To Movie.
See also:
http://www.sjoki.uta.fi/~shmhav/SVCDon_aMacintosh.html#slideshow

How to calculate penalty interest on customer

hi sap guru's
how to calculate penalty interest on customer. what type of settings for required to calculate . pls tell me.

Hi Shiva
You have options like Balance interest calculation or item level interest calculation. You can configure the setting as per your requirement and you can charge interest on default customers.
Thanks
Ashok
Assign points for useful answer

How to avoid double-click to click-box

Hello,
until now I did not find a solution for this problem:
I have created a training course for a specific application, and in this coure are some click boxes on which the user should click. On many click boxes should the user click only once but if he double-click the click box, in real application nothing happens. There is only one way to succes the action - one click. But in captivate when the user double-click the click box instead of one click it evaluate as success action (the click box is set only to one click, double-click checkbox is not checked).
So my question is, is there any way how to avoid double-click in cases where the user should click only once? Or in case he double-click the click box to show failure caption?
Many thanks.
Lukas

Hi all
Interesting thread. Unfortunately, what would be needed here is some sort of a widget that would run some internal timer. Sure, you can try multiple Click Boxes and configure one with a Single Click and one with a Double Click. But the problem with that (as I see it) is regardless of what you might try, the Single Click will win out every time. Thus you would need a widget of some sort that would "listen" for a Double Click and respond appropriately.
Tough call... Rick
Click here for Adobe Authorized Captivate and RoboHelp HTML Training
Click here for the SorcerStone Blog
Click here for RoboHelp and Captivate eBooks

Hi how to avoid nested loops in this program to improve the performence

Hi all
How to avoide the nested loops in this programing what is the replacement for the nested loops in this program coding......
LOOP AT itb_ekpo.
    READ TABLE itb_marc WITH KEY
       matnr = itb_ekpo-matnr
       werks = itb_ekpo-werks BINARY SEARCH.
    CHECK sy-subrc = 0.
FAE 26446 fin remplacement
    itb_pca-ebeln = itb_ekpo-ebeln.
    itb_pca-ebelp = itb_ekpo-ebelp.
itb_pca-lifnr = itb_ekko-lifnr.   "-FAE26446
    itb_pca-lifnr = itb_ekpo-lifnr.                         "+FAE26446
    itb_pca-ekgrp = itb_ekpo-ekgrp.                         "+FAE26446
    itb_pca-dispo = itb_ekpo-dispo.                         "+FAE26446
    itb_pca-matnr = itb_ekpo-matnr.
    itb_pca-werks = itb_ekpo-werks.
Recherche du libellé article
    READ TABLE itb_makt
               WITH KEY matnr = itb_ekpo-matnr
                        spras = text-fra
               BINARY SEARCH.
    IF sy-subrc = 0.
      itb_pca-maktx = itb_makt-maktx.
    ELSE.
      READ TABLE itb_makt
                WITH KEY matnr = itb_ekpo-matnr
                         spras = text-ang
                BINARY SEARCH.
      IF sy-subrc = 0.
        itb_pca-maktx = itb_makt-maktx.
      ENDIF.
    ENDIF.
    IF NOT itb_ekpo-bpumn IS INITIAL.
      itb_pca-menge = itb_ekpo-menge * itb_ekpo-bpumz /
                                       itb_ekpo-bpumn.
    ENDIF.
Sélect° ds la table EKES des dates de livraisons et des qtés
en transit
    CLEAR w_temoin_ar.
    CLEAR w_etens.
    LOOP AT itb_ekes
            FROM w_index_ekes.
      IF itb_ekes-ebeln = itb_ekpo-ebeln
      AND itb_ekes-ebelp = itb_ekpo-ebelp.
        IF itb_ekes-ebtyp = text-arn.
          itb_pca-eindt = itb_ekes-eindt.
          w_temoin_ar = 'X'.
        ELSE.
        Si c'est une qté en transit alors on recupere
        la quantité et la date.
          IF itb_ekes-dabmg < itb_ekes-menge.
            itb_pca-qtran = itb_pca-qtran + itb_ekes-menge -
                            itb_ekes-dabmg.
          ENDIF.
          IF itb_ekes-etens > w_etens.
            w_etens = itb_ekes-etens.
            itb_pca-dtran = itb_ekes-eindt.
          ENDIF.
        ENDIF.
      ELSEIF itb_ekes-ebeln > itb_ekpo-ebeln
      OR ( itb_ekes-ebeln = itb_ekpo-ebeln
      AND itb_ekes-ebelp > itb_ekpo-ebelp ).
        w_index_ekes = sy-tabix.
        EXIT.
      ENDIF.
    ENDLOOP.
S'il n'y a pas d'AR alors récupérat° de la date livraison dans EKET.
    LOOP AT itb_eket
            FROM w_index_eket.
      IF itb_eket-ebeln = itb_ekpo-ebeln
      AND itb_eket-ebelp = itb_ekpo-ebelp.
        IF w_temoin_ar IS INITIAL.
          itb_pca-eindt = itb_eket-eindt.
        ENDIF.
        itb_pca-slfdt = itb_eket-slfdt.
      Calcul du portefeuille fournisseur à partir de la
      qté commandée et la qté reçue
        itb_pca-attdu = itb_pca-attdu + itb_eket-menge -
                        itb_eket-wemng.
      Calcul du montant du poste
        itb_pca-netpr = itb_ekpo-netpr * itb_pca-attdu.
        IF itb_ekpo-peinh NE 0.
          itb_pca-netpr = itb_pca-netpr / itb_ekpo-peinh.
        ENDIF.
      Calcul quantité réceptionnée.
        itb_pca-wemng = itb_pca-wemng + itb_eket-wemng.
      Calcul du retard en nombre de jours calendaires
      Le calcul du retard ne doit pas prendre en compte
      le jour de livraison
        ADD 1 TO itb_eket-eindt.
        IF NOT itb_pca-attdu IS INITIAL
        AND    itb_eket-eindt LT sy-datum.
        Calcul du retard en nombre de jours ouvrés
          CLEAR w_retard.
          CALL FUNCTION 'Z_00_BC_WORKDAYS_PER_PERIOD'
               EXPORTING
                    date_deb = itb_eket-eindt
                    date_fin = sy-datum
               IMPORTING
                    jours    = w_retard.
          itb_pca-rtard = itb_pca-rtard + w_retard .
        ENDIF.
      ELSEIF itb_eket-ebeln > itb_ekpo-ebeln
      OR (   itb_eket-ebeln = itb_ekpo-ebeln
      AND    itb_eket-ebelp > itb_ekpo-ebelp ).
        w_index_eket = sy-tabix.
        EXIT.
      ENDIF.
    ENDLOOP.
Recherche de la derniere date de livraison.
    LOOP AT itb_mseg
            FROM w_index_mseg.
      IF itb_mseg-ebeln = itb_ekpo-ebeln
      AND itb_mseg-ebelp = itb_ekpo-ebelp.
        READ TABLE itb_mkpf
                   WITH KEY mblnr = itb_mseg-mblnr
                            mjahr = itb_mseg-mjahr
                   BINARY SEARCH.
        IF sy-subrc = 0.
          IF itb_mkpf-bldat > itb_pca-bldat.
            itb_pca-bldat = itb_mkpf-bldat.
          ENDIF.
        ENDIF.
      ELSEIF itb_mseg-ebeln > itb_ekpo-ebeln
      OR (   itb_mseg-ebeln = itb_ekpo-ebeln
      AND    itb_mseg-ebelp > itb_ekpo-ebelp ).
        w_index_mseg = sy-tabix.
        EXIT.
      ENDIF.
    ENDLOOP.
    APPEND itb_pca.
    CLEAR itb_pca.
FAE26446 suppression parag. suivant
     ELSEIF itb_ekpo-ebeln > itb_ekko-ebeln.
       w_index_ekpo = sy-tabix.
       EXIT.
     ENDIF.
   ENDLOOP.
Fin FAE26446
ENDLOOP.
Thanks in advance for all.....

Hi
these are the performance tips
Instead of using nested Select loops it is often better to use subqueries.
SELECT * FROM SPFLI
INTO TABLE T_SPFLI
WHERE CITYFROM = 'FRANKFURT'
    AND CITYTO = 'NEW YORK'.
SELECT * FROM SFLIGHT AS F
    INTO SFLIGHT_WA
    FOR ALL ENTRIES IN T_SPFLI
    WHERE SEATSOCC < F~SEATSMAX
      AND CARRID = T_SPFLI-CARRID
      AND CONNID = T_SPFLI-CONNID
      AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
The above mentioned code can be even more optimized by using subqueries instead of for all entries.
SELECT * FROM SFLIGHT AS F INTO SFLIGHT_WA
    WHERE SEATSOCC < F~SEATSMAX
      AND EXISTS ( SELECT * FROM SPFLI
                     WHERE CARRID = F~CARRID
                       AND CONNID = F~CONNID
                       AND CITYFROM = 'FRANKFURT'
                       AND CITYTO = 'NEW YORK' )
      AND FLDATE BETWEEN '19990101' AND '19990331'.
ENDSELECT.
<b>Internal Tables</b>
1.     Table operations should be done using explicit work areas rather than via header lines.
2.     Always try to use binary search instead of linear search. But dont forget to sort your internal table before that.
3.     A dynamic key access is slower than a static one, since the key specification must be evaluated at runtime.
4.     A binary search using secondary index takes considerably less time.
5.     LOOP ... WHERE is faster than LOOP/CHECK because LOOP ... WHERE evaluates the specified condition internally.
6.     Modifying selected components using MODIFY itab TRANSPORTING f1 f2.. accelerates the task of updating a line of an internal table.
Point # 2
READ TABLE ITAB INTO WA WITH KEY K = 'X BINARY SEARCH.
IS MUCH FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY K = 'X'.
If TAB has n entries, linear search runs in O( n ) time, whereas binary search takes only O( log2( n ) ).
Point # 3
READ TABLE ITAB INTO WA WITH KEY K = 'X'. IS FASTER THAN USING
READ TABLE ITAB INTO WA WITH KEY (NAME) = 'X'.
Point # 5
LOOP AT ITAB INTO WA WHERE K = 'X'.
ENDLOOP.
The above code is much faster than using
LOOP AT ITAB INTO WA.
CHECK WA-K = 'X'.
ENDLOOP.
Point # 6
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1 TRANSPORTING DATE.
The above code is more optimized as compared to
WA-DATE = SY-DATUM.
MODIFY ITAB FROM WA INDEX 1.
7.     Accessing the table entries directly in a "LOOP ... ASSIGNING ..." accelerates the task of updating a set of lines of an internal table considerably
8.    If collect semantics is required, it is always better to use to COLLECT rather than READ BINARY and then ADD.
9.    "APPEND LINES OF itab1 TO itab2" accelerates the task of appending a table to another table considerably as compared to LOOP-APPEND-ENDLOOP.
10.   DELETE ADJACENT DUPLICATES accelerates the task of deleting duplicate entries considerably as compared to READ-LOOP-DELETE-ENDLOOP.
11.   "DELETE itab FROM ... TO ..." accelerates the task of deleting a sequence of lines considerably as compared to DO -DELETE-ENDDO.
Point # 7
Modifying selected components only makes the program faster as compared to Modifying all lines completely.
e.g,
LOOP AT ITAB ASSIGNING <WA>.
I = SY-TABIX MOD 2.
IF I = 0.
    <WA>-FLAG = 'X'.
ENDIF.
ENDLOOP.
The above code works faster as compared to
LOOP AT ITAB INTO WA.
I = SY-TABIX MOD 2.
IF I = 0.
    WA-FLAG = 'X'.
    MODIFY ITAB FROM WA.
ENDIF.
ENDLOOP.
Point # 8
LOOP AT ITAB1 INTO WA1.
READ TABLE ITAB2 INTO WA2 WITH KEY K = WA1-K BINARY SEARCH.
IF SY-SUBRC = 0.
    ADD: WA1-VAL1 TO WA2-VAL1,
         WA1-VAL2 TO WA2-VAL2.
    MODIFY ITAB2 FROM WA2 INDEX SY-TABIX TRANSPORTING VAL1 VAL2.
ELSE.
    INSERT WA1 INTO ITAB2 INDEX SY-TABIX.
ENDIF.
ENDLOOP.
The above code uses BINARY SEARCH for collect semantics. READ BINARY runs in O( log2(n) ) time. The above piece of code can be more optimized by
LOOP AT ITAB1 INTO WA.
COLLECT WA INTO ITAB2.
ENDLOOP.
SORT ITAB2 BY K.
COLLECT, however, uses a hash algorithm and is therefore independent
of the number of entries (i.e. O(1)) .
Point # 9
APPEND LINES OF ITAB1 TO ITAB2.
This is more optimized as compared to
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 10
DELETE ADJACENT DUPLICATES FROM ITAB COMPARING K.
This is much more optimized as compared to
READ TABLE ITAB INDEX 1 INTO PREV_LINE.
LOOP AT ITAB FROM 2 INTO WA.
IF WA = PREV_LINE.
    DELETE ITAB.
ELSE.
    PREV_LINE = WA.
ENDIF.
ENDLOOP.
Point # 11
DELETE ITAB FROM 450 TO 550.
This is much more optimized as compared to
DO 101 TIMES.
DELETE ITAB INDEX 450.
ENDDO.
12.   Copying internal tables by using ITAB2[ ] = ITAB1[ ] as compared to LOOP-APPEND-ENDLOOP.
13.   Specify the sort key as restrictively as possible to run the program faster.
Point # 12
ITAB2[] = ITAB1[].
This is much more optimized as compared to
REFRESH ITAB2.
LOOP AT ITAB1 INTO WA.
APPEND WA TO ITAB2.
ENDLOOP.
Point # 13
SORT ITAB BY K. makes the program runs faster as compared to SORT ITAB.
Internal Tables         contd
Hashed and Sorted tables
1.     For single read access hashed tables are more optimized as compared to sorted tables.
2.      For partial sequential access sorted tables are more optimized as compared to hashed tables
Hashed And Sorted Tables
Point # 1
Consider the following example where HTAB is a hashed table and STAB is a sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE HTAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
This runs faster for single read access as compared to the following same code for sorted table
DO 250 TIMES.
N = 4 * SY-INDEX.
READ TABLE STAB INTO WA WITH TABLE KEY K = N.
IF SY-SUBRC = 0.
ENDIF.
ENDDO.
Point # 2
Similarly for Partial Sequential access the STAB runs faster as compared to HTAB
LOOP AT STAB INTO WA WHERE K = SUBKEY.
ENDLOOP.
This runs faster as compared to
LOOP AT HTAB INTO WA WHERE K = SUBKEY.
ENDLOOP.
<b>Reward if usefufll</b>

Tip: How to Avoid some tough LV 2009 Build & Run Problems

Hello,
I posted some tips I think may be useful to my fellow LabView 2009 programmers on the MathScript forum here:
http://forums.ni.com/t5/LabVIEW-MathScript-RT-Module/Avoid-MathScipt-Comments-in-EXE-Build-amp-Run-P...
Allthough some of the problems are MathScript related, the post contains information on how to avoid some other LabView 2009 problems as well. I thought this info would be interesting to other than "MathScript programmers":
The post contains information on how to circumvent the following problems:
* "The VI is not Executable. The full development version of LabView is required to fix the errors"
* Avoid that MathScript Comments are included in the EXE !
* Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE
* DSC Reference Problem in LabView 2010 DS1 release
* TagSrv Error "TagSrv.exe: This application has requested the runtime to terminate in an unusual way"
Geir Ove

Hello,
I posted some tips I think may be useful to my fellow LabView 2009 programmers on the MathScript forum here:
http://forums.ni.com/t5/LabVIEW-MathScript-RT-Module/Avoid-MathScipt-Comments-in-EXE-Build-amp-Run-P...
Allthough some of the problems are MathScript related, the post contains information on how to avoid some other LabView 2009 problems as well. I thought this info would be interesting to other than "MathScript programmers":
The post contains information on how to circumvent the following problems:
* "The VI is not Executable. The full development version of LabView is required to fix the errors"
* Avoid that MathScript Comments are included in the EXE !
* Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE
* DSC Reference Problem in LabView 2010 DS1 release
* TagSrv Error "TagSrv.exe: This application has requested the runtime to terminate in an unusual way"
Geir Ove

How to avoid variable declaration dublication in a script?

Hello to everyone!
I have a business rule which calls twice same script. But in this sript there is a variable declaration (MethodOpl).
Rule:
FIX (&CashFlowPlanningMonths, &PlanningYear, {SelScenario}, {SelVersion})
    %Script(name:="Distribution 100",application:="workapp3",plantype:="Plan1");
ENDFIX;
FIX (Jan:Dec, &NextYear, {SelScenario}, {SelVersion})
    %Script(name:="Distribution 100",application:="workapp3",plantype:="Plan1");
ENDFIX;
Script:
VAR MethodOpl = 0;
FIX (@DESCENDANTS("TotalLocations"), "NoAnalytics", @DESCENDANTS("100000"))
AmountByPay(
      IF ( NOT @ISMBR(@LIST("114100","115110","115120","115130")) )
        MethodOpl = "BegBalance"->WorkVersion->"NoFRC"->"DistributionByPay";
        IF ( MethodOpl == #Missing )
           MethodOpl = "NoLocation"->WorkVersion->"BegBalance"->"NoFRC"->"DistributionByPay";
        ENDIF;
        ... (some calculations)
      ENDIF;
ENDFIX;
If I try to validate rule I get error like this:
An error occurred in: Rule:workapp3.Plan1.TestOTN
A validation error was received from the Planning server 'http://ohp:80/HyperionPlanning/servlet/HspAppManagerServlet?appname=workapp3'.
'Error:Переопределение имени переменной [MethodOpl]. Rule workapp3.Plan1.TestOTN'.
Error text can be translated as "Error: Redeclaring variable name [MethodOpl]"
Can you advice me how to avoid second declaration?
May be somehow like this?
#IF !DEFINED(MethodOpl)
VAR MethodOpl;
#ENDIF
MethodOpl = 0;

Try creating a separate script for variable declaration & declare all the variables inside it.Add this script as first statement in the rule
SCRIPT: "Var Declaration"
VAR MethodOpl = 0;
RULE
%Script(name:="Var Declaration",application:="workapp3",plantype:="Plan1");
FIX (&CashFlowPlanningMonths, &PlanningYear, {SelScenario}, {SelVersion})
%Script(name:="Distribution 100",application:="workapp3",plantype:="Plan1");
ENDFIX;
FIX (Jan:Dec, &NextYear, {SelScenario}, {SelVersion})
%Script(name:="Distribution 100",application:="workapp3",plantype:="Plan1");
ENDFIX;
remove the "MethodOpl" variable declaration from the script -"Distribution 100".

SEM-BCS Minority Interest in Income Statement

Hi,
I am using SEM-BCS 4.0. The C/I task calculates Minority Interests in Current period profits.
How can Minority Interest in profit be shown in Income Statement?
Please suggest
Regards,

Hi,
First you have to have an item for minority interest in the income statement.
Then do the following in the customizing workbench:
Consolidation of investments --> Settings --> Appropriation of retained earnings
Select the tab "Net Income" and assign the mentioned item in the section "Minority Interest in Annual Net Income".
Regards
Ignaz

Minority Interest in HFM

Guys
We are using custom logic to calculate minority interest (not using PCON,POWN or PMIN). We are capturing the ownership percentage in certain accounts thru the web forms and using this info in rules to calculate minority interest. This calculation executes at entity currency, at base level entity and translates into USD as part of standard HFM translation.
We are running into issues where minority interest entity belongs to foreign entity (not same as reporting currency entity)
It works fine for P&L but does not work correctly for balance sheet as we have two different rates for these.
Is there any better way to handle this ?
Your feedback is greatly appreciated.

Hi Venkat,
Any particular reason why you are using calculation rules in order to do this? Minority interest as such in my view is a consolidation specific calculation which you normally calculate in the consolidation itself, not so much in the calculation routine. Wirh regards to the ownership percentage and such, this is normally done in the ownership module which is default functionality of HFM. Have you turned consolidation rules on or off?

How to avoid ViewObject or ApplicationModule cache?

I am developing a web application using JSP, EJB (SessionBean) and BC4J.
How to avoid ViewObject or ApplicationModule cache?
Is there any method in Oracle API (oracle.jbo, oracle.jbo.server, ...) to do this?
null

Objects returned from queries against your session are the shared/cached instances and should not be changed. Changes applied directly against these instances will not be reflected in the database.
To apply changes against objects within a transaction and isolate these changes from other thread while they are pending you must use a UnitOfWork. The UnitOfWork will provide you a transactional isolated working copy where changes can be safely made. Then when the UnitOfWork is committed the minimal change-set is calculated and written to the database prior to being merged into the shared cache.
Some useful links into the documentation:
http://download-west.oracle.com/docs/cd/B10464_01/web.904/b10313/undrstdg.htm#1110428
http://download-west.oracle.com/docs/cd/B10464_01/web.904/b10313/xactions.htm#1127587
Doug

How to avoid minority interest dividend calculation

Similar Messages

Maybe you are looking for