Defining Intracompany Balancing Rules(AGIS)

-

 Defining Intracompany Balancing Rules

In order to take advantage of the automatic Intercompany balancing during GL posting and SLA Accounting you first need to define the accounts you want us to use.
Intercompany and Intracompany Accounts in R12 are defined in two different Set Up Pages, the Intracompany Balancing Rules are what we had in 11i for Intercompany Accounts (confusing I know) – this is where you will find the rules you had in 11i of you are upgrading from 11i. If you don’t want to take advantage of the Legal Entity Configurator product and define Legal Entities and map them to your accounting structure, you can still go ahead and use the intracompany rules. If you start to map your Legal Entities to Ledgers and/or Balancing Segment Values (BSV) then you will want to be sure you complete the job, so there is no ambiguity in your setup. Consider the example below for BSV 10, 20, 30, 40, 80 and 90 :
Alpha Enterprises
The France Ledger is mapped to the FR LE, so all BSV in that ledger are assumed to be owned by LE France. However the UK Ledger has BSV 10 and 20 mapped to the UK LE, but 80 and 90 are not mapped to anything we have no way to know what LE they are assigned to.
You will be able to set up Intracompany balancing rules
  • Between 10 and 20
  • Between 80 and 90
  • between 30 and 40
You can set up Intercompany Accounts between
  • 10 and 30 or 40
  • 20 and 30 or 40
  • LE France and LE UK
All the above are unambiguous, we know what we are dealing with. The 80 and 90 BSV are in the same ledger with no LE at Ledger or BSV level so we just assume that any transactions between 80 and 90 are intracompany.
We would not allow you to create Intracompany rules between
  • 80 and 10 or 20
  • 90 and 10 or 20
This is because we don’t know if 80 and 90 are in the UK LE or not, if they are then assign those BSV to LE UK too and you’re good to go.
If 80 and 90 aren’t in the UK LE then what LE do they belong to? Once you map them to the to the appropriate LE then you will need to define Intercompany accounts for them

Comments

  1. Unknown1 May 2014 at 01:35

    This comment has been removed by the author.

    ReplyDelete
  2. Unknown16 July 2016 at 00:29

    This comment has been removed by the author.

    ReplyDelete

Post a Comment

Popular posts from this blog

Oracle Purchasing Module Step by Step in R12

-
Image
PURCHASING  All the Purchasing related activity information will be declared in Purchasing              Procure 2 Pay Cycle : Requisition à RFQ à Quotation à Quotation Analysis à Purchasing à Receiving à Invoice  à  Payment à Reconciliation PO-Integration :  PO  is integrated by GL, AP, I Supplier, Procurement, and Project Accounting  PO  Responsibility             Step1: Define  PO  Responsibility                         Nav: System administrator à Security à Responsibility à Define             Step2: Assign  PO  options to the PO Responsibility                 ...
Read more

Sub Ledger Accounting SLA (Complete Functional Information)

-
Image
SubLegder Accounting in R12 SLA Part -1 In these article, we will explore the very basics of SLA and why it exists. Firstly, what exactly does SLA do? SLA is a module which now sits between the SubLedgers like AP/AR etc and the General Ledger. Have a look at this diagram below.  As you will notice, SLA can act as a mediator between the subledgers and Oracle General Ledger. Before we progress, some terminologies of R12 must be revisited. In 11i we had set of books, and in R12 we call them Ledgers. Likewise in R12 we also have secondary ledgers and reporting ledgers. Hence from 11i perspective think of Ledger as Set of Books. As for Subledger, a Subledger is nothing but a module like AP/AR/PO/Inventory etc. In the diagram below, the second scenario is explained whereby let's say that payables module generates a charge account segment combination for an invoice distribution line as A.B.C.D. In such case, if SLA module is not customized, then the very same A.B.C.D ...
Read more

Difference between ATO and PTO in oracle apps

-
Difference between ATO and PTO in oracle apps 1) MAKE TO ORDER: This is based on Customer specification, you make the product and supply it to them. This is applicable for Engineering items or any Product which you can make based on Customer order Example: Engineering Items 2) ASSEMBLE TO ORDER: This is you have items in parts and it needs to be assembled according to customer requirements For example you have Laptop coming with standard configuration of 160GB Hard disk and 1 GB RAM. But there are customer orders coming in asking for 200GB Hard Disk and 2 GB RAM and if you can assemble them to suit Customer Requirement 3) CONFIGURE TO ORDER: This is Configuring the Product itself to suit Customer requirements Example. The Thread Manufacturing unit Machineries are configured. I have seen Laxmi Machine Works in INDIA which manufactures textile Machineries configure the machineries based on No.of spindles 4) PICK TO ORDER: This is same as Computer Example in ATO. But the  differenc...
Read more