Inter company Transaction

Similar Questions

• "Manage the inter-company Transactions in financial management" on OBE

  Hi all
  
  I apply the 'Intercompany Financial Transactions management' process on Oracle by example (OBE). I want to know the example of how he loaded the data and metadata files related to the main example, I am working on 'Manage intercompany Financial Transactions' so that I can apply the same steps as in the example.
  I searched on OBE, but it is not found.
  
  Thanks in advance
  Best regards
  Ahmed

  Hi, Ahmed.

  Select process.
  Just under the icons of process work-> subject - > approved
  Is a POV toolbar
  Select the first icon just under the work, this should bring up a POV selection box.
  Select actual for scenario
  Select 20xx for the year (the year you have loaded data sheet of)
  Select Jan for the first period (the period that you have loaded data sheet of)
  Select

  Select advanced at the top of the toolbar icon
  Highlight all periodicals click on submit. Click on approve. Click on message.

  This will show all reviews th for the period and year you selected.
  You will need to repeat for each time period and each year you have log data load.

  Don't forget to perform Consolidations for years and periods that you have data loaded.

  G'Luck!
  -David

• Inter company eliminations

  To save the data of ICP, but eliminations shouldn't happen during consolidation.
  
  Kindly help

  This solution will work for this scenario also rhythms in the rule file you wrote a check for the account condition of the plug.

  Varun

• Error loading of the PKI

  I am trying to create a PKI transaction, but when I try to record gives an error that cell does not support intercompany transactions.
  
  Thanks in advance

  I think you're confused with inter-company balances inter-company transactions. Intercompany transactions are entered daily (operations) which are loaded into the module HFM intercompany, that is the place where you try to create transactions. Intercompany balances are one year the amounts are not loaded in the transaction module.

  Varun

• Calculation to Elim in HFM entity such as Elim entities in the enterprise

  I was responsible for the HFM work as business - how can I fill an Elim entity with data [disposal] publishes on real entities during consolidation?  Since there is no data is not loaded in the ElimEntity and the accounts are not marked IsCalculated, I created a custom ElimCalc calculated to try to realize the calculation of uncalculated accounts.

  I tried every iteration elimination consolidate the function within the sub section.  I tried to fill the elim calculate entities through the sub section.  All epic fails.

  Can someone point me in the right direction with this?  I tried to show the client that the data they need is in the dimension of value [disposal] that these data may be attracted to consolidate reports.  However, they want the Elim entity to be part of children of parent in a column of the report rather than have two columns to give the Curr Total entity and the elimination.

  There must be a solution to this and I've exhausted ideas.

  Thanks a lot for this reading and offering suggestions.

  I've done a few times. I highly recommend that you avoid creating entities from the elimination. Do all you can to convince users that they have no need of specific entities of elimination. Use rather a custom size 'data type' to store the values of the elimination.

  To answer your question, however, you can (and should) use Sub consolidate to do this, not to calculate the Sub. The HS. Con function takes the [Total Parent] entity data and writes to the current entity [percentage] and/or [disposal], OR node, node [disposal] any entity brother. This means that you must create elimination entities named 'ParentEntity_Elim '. The rules, to consolidate the Sub would look like this:

  Void Consolidate()

  '************************************************************************************************************************************************************
  ' Consolidate the Routine
  '
  ' 1 of 8 routines default HFM
  ' (Default HFM routines include Calculate, translate, consolidate, Allocate, NoInput, entry, dynamic & Transactions)
  '
  "The following categories of logic are treated here:
  (1) the consolidation of all data on the percentage of Consolidation (PCon) of the node (parent single & child)
  (2) elimination of intercompany transactions
  '
  "When consolidate it Routine runs, it extracts data from the amount '[Parent]' Member, makes him.
  "specified calculations and, by default, writes the result to the Member"[percentage]. "
  "It is also able to write the result to the Value"[disposal]"Member as he does performing intercompany
  "investment in overtime and eliminations of equity."  We can also write the "[share].
  "and"[disposal]"members of the entities of the siblings.
  '
  "Consolidate routine runs when a user highlights a parent entity and selects"peacebuilding. "
  ' ' Consolidate all with data ", or"Consolidate all"option in the right-click or the list of menu items Action menu.
  '
  '************************************************************************************************************************************************************

  sParent HS =. Parent.Member ' get the entity parent of the parent-child node being calculated
  HS = nPCon. Node.PCon("") ' get the property of the account system "[PCon]." By default, it is equal to 1 (= 100%).

  "Pull in the memory of all points of data (records) of the unit of current data.  These data represent all data stored in member account,
  "PIC and the dimensions of the customs.
  Define further HS =. OpenDataUnit("")
  nNumItems = duAll.GetNumItems ' get the number of data points in this unit of data.

  ' Loop through each data point and run the logic within this loop
  For i = 0 To nNumItems - 1
  "Get information about that data point, including labels for the account, PKI, and customs as well as the (dData) value of the data point
  Call duAll.GetItem (i, sAccount, sICP, sCustom1, sCustom2, sCustom3, sCustom4, nData)
  If nData <> 0 Then ' do not consolidate zeros
  Dial the HS. Con ("", nPCon, "") ' apply the PCon property to the data point and write the results to the Member Value '[percentage].
  'Run the logic of elimination for intercompany balances '.
  Call eliminate them (sParent, sAccount, sICP, sCustom1, sCustom2, sCustom3, sCustom4, nData, nPCon)
  End If ' dData <> 0
  Next ' I
  Further = Nothing set

  End Sub ' consolidate

  Void remove (sParent, sAccount, sICP, sCustom1, sCustom2, sCustom3, sCustom4, nData, nPCon)
  '************************************************************************************************************************************************************
  "Eliminating the Routine."
  '
  "Criteria".
  '
  ' This routine assesses each data point that passed to the routine to consolidate and eliminates data points
  "If the following criteria are met:"
  '
  (1) is not a member of PKI "[ICP None]", IE. an intercompany partner has been specified
  (2) the parent of the entity being grouping is an ancestor of the specified PKI
  ' OR
  "The mother of the entity being grouping is included in a geographical hierarchy of"
  (3) the account is reported as "IsICP" in the metadata
  (4) the account has a "PlugAcct" specified in the metadata
  '
  "Computation".
  '
  "He made the elimination with 2 steps:"
  1) multiply by PCon - data point and writes the result to the Value «[disposal]» Member
  (2) multiply the intercompany by PCon data point and writes the result to the Plug account, Member of the value "[disposal],"
  "while other members of the same size
  "Please note that if your application writes the eliminations at an intersection of the particular custom dimension, add the Cx member of the harmonized system. Functions of con.
  '
  '************************************************************************************************************************************************************

  "This subroutine is currently not used and is here only as a placeholder for once when the application starts to run automated inter-company eliminations."

  bCanEliminate = True

  If (HS. Account.IsICP (sAccount) = False) then 'ignore accounts not flaged's PKI
  bCanEliminate = False
  ElseIf (StrComp (PSCI, "[ICP None]", vbTextCompare in) = 0) then ' ignore anything in the [no PIC] member of the dimension of the PKI
  bCanEliminate = False
  ElseIf (HS. Entity.ISDESCENDANT (sParent, PSCI) = False) then 'ignore eliminations if the intercompany partner is not a descendant of the parent of the current entity.
  bCanEliminate = False
  On the other
  sPlug HS =. Account.PlugAcct (sAccount)
  If (sPlug = "") then
  bCanEliminate = False ' ignore the elimination if there is no identified account in the account of the PKI card
  End If ' record = «»

  If bCanEliminate = True Then ' if all criteria is met as a removal should be performed, proceed
  "don't forget that nPCon contains the percentage of consolidation, that most, if not all the time should be 1 (100%).
  Dial the HS. Con ("V #[disposal].") ("E #" sParent & '_Elim',-1 * nPCon, "") ' multiply the amount of PKI-1 and write the value member [disposal].
  Dial the HS. Con ("V #[disposal].") "A #" & sPlug & ".." ("E #" & sParent & "_Elim", nPCon, "") ' write the amount on behalf of making PKI and write as the value member [disposal].
         
  "The following examples show how you might change the destination POV to include a custom dimension intersection.
  "Call HS." Con ("V #[disposal].") (C3 #AutoElim',-1 * nPCon, "") ' multiply the amount of PKI-1 and write the value member [disposal].
  "Call HS." Con ("V #[disposal].") ("C3 #AutoElim.A #" & sPlug, nPCon, "") ' write the amount on behalf of making PKI and write the value member [disposal].
  End If ' bCanEliminate = True

  End Sub ' remove sup

• In what business scenario, it will be useful to use the automatic Offset instead of intercompany method?

  When you use automatic offsets, charge automatically creates the entries of consideration for transactions at time of accounting, but if this isn't the case, then it will be considered as an intercompany transaction.
  

  HI Vivek

  As I mentioned earlier automatic compensation has been used when there is a requirement of the company to make the payment of the common at the centre in 11idays account. However, with a R12 architecture that have different dimensions. I found a few details right to explore this further mentioned below: -.

  If you enable automatic offsets, accounts payable automatically creates distributions in cash, a reduction and profit/loss for each segment of balancing when you create a payment using a common bank account. This ensures that invoices always balance by balancing the segment when paid into a joint account.

  You can use auto compensate in cash and basic accounting. In case of basic books, journal entries compensatory created during the payment, treatment of the distributions of Bill balance directly; in basic accounting books, they balance the compensatory liability entries created when you submit the approval for your bills.

  If you do not enable auto offsets or create a payment using a bank account not regrouped, accounts payable creates distributions of payment using one account of each type. When you distribute an invoice in several segments balancing, the invoice will not balance balancing segment. However, General Ledger can automatically create balancing inter-company entries to receive / pay for transactions which do not correspond to balancing the segment if you have enabled the option balance intercompany journals to your set of books.

  This means inter-company created the journal balanced level GL while the Auto shift is to manipulate the level of AP itself inputs. However with the introduction of the concept of AGIS that concept more to become the good topic for further research. We have still a few limitations with automatic compensation as mentioned below.

  ADJUSTMENTS to BILLS. When a Bill is paid or partially paid, you cannot set any accounting information on the invoice. Accounts payable prevents you discount or inversion of the distribution of the Bill for paid or partially paid invoices because accounts payable has already created payment distributions based on the current invoice posting lines.

  RECONCILIATION ACCOUNTANT. If you enable automatic offsets within accounts payable, you cannot activate the option enable accounting reconciliation of accounts payable or enter the reconciliation accounts in the window of banks. You can always clear the payments using cash management of Oracle. However, accounts payable does create no reconciliation of accounting entries.

  AUTOMATIC WITHHOLDING. You cannot use auto selected tax if you have enabled automatic offsets in Payables.

  If all this becomes the object of choice you and limitation of the company. My recommendation is to use intercompany offset rather then auto as empty this address the variety of business scenarios.

  Thank you

  Pawan

• IC partner not identified in HFM

  Hi guys,.

  I am working in a project, while the IC partners are not identified in the source (not all), then it means that I probably need to load the data into [no PIC].

  In this case, how will you do the eliminations? As far as I know, for HFM works correctly, all transactions of the IC should be loaded to HFM (say, through FDM) with an identified partner (PKI).

  Could you please share your thoughts?

  Thank you!

  Anna

  Given in [no PIC] do not eliminate by default. If you inter-company data, which you know is truly intercompany, but data is not the identity of the correct partner, you can create a fictional entity in the application, installed directly under the highest parent entity, perhaps called 'ICPTemp', beating Pavilion IsICP. So rather than load the inter-company on [no PIC] data, you would map to ICPTemp. This would allow the HFM eliminate all data associated with ICPTemp, since HFM sees it as a PIC entity is valid and applies the same "first common parent" logic, with the first common parent being the last parent in the hierarchy.

  I would also ensure the entity in order to forbid anyone to enter data in this entity, since it exists only for purposes to be a partner to all other entities intercompany.

  -Chris

• Export Type mismatch failed on line 262

  Hi all
  
  I'm loading inter-company data of FDM 9 x to HFM 9 x.
  
  I have configured successfully FM9i-G4 - A.xml FDM IC adapter.
  
  Can someone advice how I should load the data file between firms with the amount of the transaction and the rate of Conversion of Curr? How can I derive from the principal amount on the fly by multiplying Trans Curr Curr Conversion rate?
  
  ======================
  That's what I tried...
  ======================
  
  My import format contains, entity, account, C1 to C4, Trans amount (mapped with the column amount in FDM) and Currency Conversion rate (CCR)
  
  What I do not give the amount of the entity?
  
  I want to calculate the amount of the entity with the following formula: TN = varvalues entity (9) * varvalues (37)
  
  I tried to give the formula AS mapping, but I get the error type mismatch (not the one I mentioned in the subject). I know it's because of varvalues (37) returns a string. I tried to use the Val() or CDBL() function, but they do not work.
  
  Then I delete the map and tried to export data. However, the export fails before you generate the data file and gives the following error: (error log given)
  
  * Start the journal entry for the Runtime Error FDM [2011-03-26-10: 27:05] *.
  -------------------------------------------------------------
  ERROR:
  Code......................................... 13
  Description... Type mismatch
  Online: 262
  Process... clsBlockProcessor.ActExport
  The component... upsWBlockProcessorDM
  Version...................................... 931
  Thread....................................... 7320

  Hello

  I suggest that join you Oracle. There are severe design considerations when you use the HFM - IC adapter, but also bugs in version 9 x. I should know... I have written/discovered them when I worked there.

  That being said... you get this error on line 262 is because it expects a 'Double' value... and FDM is passing as a "string". You will need to change the Action to export the IC card and wrap the value in a statement CDBL().

  Hope this helps...

• Reports of the IC

  When I am trying to generate the report of transactions process IC > > report option (game of football by account) I see a blank report.
  
  Thankx in advance

  Please visit the below mentioned link

  Transaction report empty Inter company

  Concerning
  Nick

• HFM automated Consolidation reviewed does not not as expected

  Hi Experts,

  We have implemented magazines automated consolidations in HFM by specifying a member of nature in our consolidation/elimination subroutine in our rules file.

  We are confident that the bundling rules are correct.  Automated reviews are actually get generated in the value member [eliminated].

  However, for each parent, details of all activities below that parent appear even if the balances are already eliminated by this entity. One would expect the log should be created ONLY to the parent in which the disposal occurs, not all parents above as well.

  Is - it so the automated consolidation newspapers are supposed to work in HFM?   Or does add a refinement to our rule so that the details of the journal fills only the appropriate parent?

  All of these entries appear in a top-level parent, for example, well above the parent where took place the real eliimination (and this happens to all parents on the channel from the one where the elim occurs):

  1. (155000 *-1) S #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #2565110.I #0570.C1 #[None]. C2 #[no]. C3 #[no]. C4 #Adj

  2. (155000 * 1) S #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #2565110.I #0570.C1 #[None]. C2 #[no]. C3 #[no]. C4 #Adj

  3. (-155000 *-1) S #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #2565110.I #0570.C1 #[None]. C2 #[no]. C3 #[no]. C4 #Elim

  4-155000 * 1s #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #2565110.I #0570.C1 #[None]. C2 #[no]. C3 #[no]. C4 #Elim

  5. (155000 *-1) S #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #1519200.I #0502.C1 #[None]. C2 #[no]. C3 #[no]. C4 #[no]

  6. (155000 * 1) S #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #1519200.I #0502.C1 #[None]. C2 #[no]. C3 #[no]. C4 #[no]

  7. (-155000 *-1) S #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #1519200.I #0502.C1 #[None]. C2 #[no]. C3 #[no]. C4 #Elim

  8-155000 * 1s #Actual.Y #2028.P #Jan.W #YTD. E #NA_OPS_W_CORP. NA_OPS. V #[Parent Total]. Has #1519200.I #0502.C1 #[None]. C2 #[no]. C3 #[no]. C4 #Elim

  Here's our elimination rule:

  If (StrComp (ICP, "[ICP None]", vbTextCompare in) = 0) then

  CanEliminate = FALSE

  ElseIf (HS. Account.IsICP (Account) = FALSE) then

  CanEliminate = FALSE

  ElseIf (HS. Node.ISDESCENDANT (HS. PARENT. (Member, ICP,' ') == FALSE)

  CanEliminate = FALSE

  ElseIf (HS. Account.PlugAcct (Account) = "") then

  CanEliminate = FALSE

  End If

  HS = strPlug. Account.PlugAcct (strAccount)

  If CanEliminate then

  HS = dPCon. Node.PCon("")

  Dial the HS. Con ("V #[disposal].") (C4 #Elim',-1 * dPCon, "ELIM")

  Dial the HS. Con ("V #[disposal].") ("C4 #Elim.A #" & strPlug, dPCon, "ELIM")

  END IF

  Thank you

  Mark

  Hello. Because you use the C4 #Elim to separate eliminations, you must update the inter-company data so that it does not eliminate the next time.

  Eric

• Set the consolidation method

  Hello
  
  I would like to ask questions about the consolidation method. I have the hierarchy as follows:
  
  1. the company possessed A company B 70%
  2. the company has owned by company C 45%
  3 company D from B 0.2%
  
  In the hierarchy above, B use full Consol, C will use equivalence (only absorb the Net result) and D will use cost (investment calculate only) method. When making this adjustment in HFM, where should I put % for POWN, PCON and PCTRL? HFM will read the configuration method that I have little matter how much % I place in these 3%?
  
  Appreciate your response.
  
  Thank you
  -Anna

  Hi Anna,.
  HFM knows nothing about consolidation if we configure the applicationsettings to use the logic of consolidation. In this case, if install you a mehthod in the file rules, no code at all, this method rolls not all numbers to the group for entities using this method. Nothing will happen, even intercompany eliminations.

  However, if install you the applicationsettings for not using the logic of consolidation, then HFM 'knows' the default method, which will practically roll all accounts using pcon and will also perform the inter-company eliminations. Note that the behavior of this group by default, can be emulated by a piece of code I've seen availble for several consultants.

  Now in the case using the custom, consolidation rules that the rules can be written in such a way that they can do special things, to the different accounts, customs or even combinations of them (or points of view as we say). And the author of the rule, determines also what will be the requirements of the system accounts pcon, pown etc. for his method works correctly. Usually, normal people give names that are meaningful to the methods they implement, even if the names tell us anything about what is the system requirements of their method. That's why I insist on the existence of the documentation on the methods.

  Kind regards
  Kostas

• Query to determine the GL segment qualifiers

  I need a query to determine which segments GL is the natural account, cost center, balancing, and intercompany segments. Can someone tell me what table and columns are stored these segment qualifiers?
  
  Thanks in advance

  Hello
  11.5.10.2
  FND_SEGMENT_ATTRIBUTE_VALUES is the table where you can check for segment qualifiers.

  Segmenting the type of attribute in 'FA_COST_CTR', GL_ACCOUNT, GL_BALANCING, GL_GLOBAL, INTER-COMPANY, GL_SECONDARY_TRACKING
  and attribute_value should be there.

  Concerning
  Muthu

• Where you see all the eliminations?

  Hi guys,.
  
  Just to be sure... where you can check all the eliminations were made? Value "Elimination"? "Entities" and their peak?
  Please, advice!
  
  Thank you!

  By default, inter-company eliminations are written in the [removal] node children in respect of each of their first common parents.

  -Chris

• PIC of HFM module

  Hi all
  
  I have a doubt. If we use the PKI of HFM module then we need to load the data ONLY in mode MAGAZINE and not last YEAR?
  
  Which method is OK for dealing with the operations of PKI, PKI using or dealing with the same without it.
  
  Do we need to write other rules to use the module in PKI?
  
  Thanks in advance
  Concerning

  In case you load monthly movements of ICP, then you can go for module ICP. In case you load data AACJ IE Inter company balances, then you can not use the PKI.

  Varun

• Members of PIC to order

  Hi all
  
  Is it possible to have a PKI list in numerical or alphabetical order as entities? In the metadata file, I can bring the entities in an alphabetical order and load this to replace. But this does not affect the order of PKI entities.
  All the tips and tricks are well appreciated.
  
  Concerning
  Ender

  Extract the members of dimension inter company and try to arrange in alphabetical order.

  I have not tried this but see if it works or not.

  Varun