Collaborate 14 Paper: Balancing by 2 Segments

It is a very common requirement to automatically balance by two different segments of the chart of accounts, typically the Legal Entity and some sort of Management Entity (department, line of business, cost center, etc).  Fusion financials allows you to balance by up to three segments, which is always a well received feature.  However at Collaborate you can learn how one company built a custom to do this in EBusiness Suite.  I’m honored to have been asked to Co-present with GE on this topic, they have done some really good work here and I’m sure it will be of great interest to others too.  So come along and join us, you’ll get the specifics of what they did, the details are below:

Session ID: 13941
When: 10 Apr 11:00 AM-12:00 PM
Room: Level 1, Marco Polo – 801
Speakers: Sangeeta Sameer, General Electric (GE),  David Haimes, Oracle Corporation
Abstract: This paper describes the Custom solution that General Electric (GE) implemented in collaboration with Oracle to achieve Balancing by 2 segments in Release 12.1.3 of Oracle E-Business Suite (EBS). GE has the business need to Balance by both the Legal Entity (LE) and Management Entity (ME) segments in the Chart of Accounts. While Fusion Applications allow Balancing by 3 segments, Oracle EBS Applications do not have this Functionality. This paper covers the requirements and solution in detail for 2 Segment Balancing.

11 Responses

  1. Thank you for sharing, David. Is there an attachment to this posting? I can’t seem to find it for some reason.

    Thank you.


  2. Hello David,

    This is very exciting news.

    Have you ever heard of companies customizing the balancing api to also balance journals against the intercompany segment?

    One issue we’re currently facing is many-to-many transactions.
    The client would like to always see a value populated for the interco segment to facilitate eliminations.

    However, both external interfaces and subledgers are creating GL journals that the system categorizes as “many to many”, and uses the default intercompany accounts to balance by LE (interco segment is zero).

    Any help would be appreciated!



  3. Paul,

    For a many to many scenario, how would any system logic inherently know the counterparty without additional external information?

    We did not require the intercompany segment to be populated for many to many transactions. Expectation is that such transactions need to be analyzed and settled.


    • Hi Sangeeta / David,

      It will be really greatful if you share presentation here or send to my email id.


  4. I could e-mail it to you, however I do not have your e-mail id.
    Please note that this is a Custom Solution.


  5. Sangeeta,

    I would also like a copy of the presentation.



  6. Paul and Umakant,

    WordPress does not publish your e-mail address so I could not e-mail. Sometime over the next few weeks, I will write a guest post on this blog and include the paper and slides. Also, David and I will be doing a webinar in June on this topic. More details to follow.



  7. […] very useful feature, maybe I should blog about it (he says, adding it to a long to do list).  My third session was co-presented with Sangeeta Sameer from GE, I have asked Sangeeta to write a guest blog post […]


  8. Hi David,
    I missed the presentation.Could u please share.My mail id



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s