‘Kicking the Tires’ Practical Use Cases for Sub-ledger Accounting in E- Business Suite Rel 12 Hans Kolbe, Celantra Systems Inc.; John Peters, Mohan Iyer Northern CA User Group – OAUG Training Day 2010

Celantra Systems: Celantra Systems provides international program management services with a strong focus on multi-org, inter-company, global compliance and implementation issues. The key element in our approach is the alignment of operational efficiency, legal/tax compliance and management reporting. Our goals are: - Single global structure across country, currency, language, accounting and tax regime - Variations are transparent to operator and business user community - Flexibility for business growth, acquisitions, or other changes in business or legal model - Ease of support and upgrade Former and current clients include Terex, UPS, Xerox, Tektronix, British Telecom, Assa Abloy, Yahoo, Texas Instruments, PPG, Dionex and others. Hans Kolbe has managed and advised software implementation projects for over 15, global projects for over 10 years. His extensive knowledge on Oracle applications is combined with a formal background as a German attorney, trained in international and comparative law. Contact: Phone: + 1 (415)

1. Fundamentals of SLA Functionality 2. Use Case – I/C COGS and Customer Acceptance 3. Investigation (kicking tires): - why PL/SQL, relationship to 11I workflow functionality, - where is the user ability to change the rules? - how to manage multiple rules Topics

Fundamentals of SLA - SLA Functionality applies rules against data in SLA tables - SLA tables are populated by default from Sub- Ledger accounting functions, i.e. COGS workflow, auto-invoice rules, FA rules etc. - Default configuration of Rel 12 SLA rule leaves the result of existing accounting in place and does not change. - This allows 11I configurations and customizations to remain in place unchanged. - This allows gradual move from accounting configurations in sub-ledgers to new SLA accounting functionality.

AP COGS Reclass through SLA John Peters – presentations

Investigation – Questions Did you really use the SLA-Rule Engine? It seems you used PL/SQL. Where in the SLA Rules did you enter the PL/SQL trigger? - What other options did you investigate for this customization? - I/C AP invoice needs to stay un-posted until customer acceptance? What happens at period end? - Where is the I/C markup? In inventory and in-transit?

Investigation – Questions How far can the user change the SLA Rule or configuration? - Change In-Transit Account - Add new parameter (depending on customer, on order type, on ship-to country, on Inco-Terms) - Split AP invoice into standard cost and markup, markup as expense, standard cost as in-transit inventory - Did you consider how to manage multiple rules across multiple sub-ledgers or GL Journals?

Lesson Learnt

Thank you ! Hans Kolbe, Celantra Systems + 1 (415)