Thursday, October 1, 2009

How MAC data and mappings gets migrated into the SLA

If you've read any of my previous posts you know that I'm by no means an expert on OPM Cost Accounting. However, for the last two weeks the majority of my time has been spent on becoming an wanna-be expert in this area. Hopefully I can break down what I think I've learned in a way that's understandable and that doesn't reveal my limited accounting knowledge.

In 11.5.10 OPM customers use the MAC to define how transactions and events will be mapped to the subledger and then on to the general ledger. This mapping can be very generic (when sub-event 'X' occurs use account number 'Y') or it can be very specific (when sub-event 'X' occurs in Whse 'A' with a reason code of 'B' and account title 'D' and a GL Item Category of 'C' then use account 'Y'). The question, then, is how does this mapping get migrated into R12?

--Please understand that the following opinion and explanation is based on my personal experience which means it might not be 100% correct--

In order to explain how MAC data gets migrated into SLA I first should explain just a titch about how the SLA works in comparison to the MAC. In MAC you have events, subevents, account titles, and account mapping attributes which you use to define account mappings. These same things exist in R12 they are just re-named so:

  • event = event entity
  • sub-event = event class
  • account titles = journal line types
  • account mapping attributes = sources
  • account mapping = account derivation rules


In release 12 your bottom level is your journal line types and your account derivation rules. A new mapping tool is introduced in 12 and it's called Journal Line Definitions. You use journal line definitions as the place were you select what account derivation rule you want to use to for each journal line type per event class.

Lets take the event class Miscellaneous Transaction as an example. This event class has two journal line types assigned to it, 'INV' (inventory valuation) and 'IVA' (inventory adjustment expense). With a journal line definition you are basically saying when event class miscellaneous transaction occurs for journal line type 'INV' use accounting derivation rule 'X'. Journal line types exist across multiple event classes so the journal line definition allows you use different derivation rules per event class. So, for the event class Batch Material Transactions, I can associate account derivation rule 'A' to journal line type 'INV' through the journal line definition and.


The journal line type will migrate without any problem because it is essentially just a copy of your existing account titles in 11.5.10. Account derivation rules is where OPM users are going to affected. Account derivation rules are created for every unique combination of: account title, set of books, and account segment. My company has a six segment accounting flexfield in R12 after migration I'll haves six account derivation rules per journal line type.

Our accounting flexfield is XX-XX-XXXX-XX-XXX-XXX so my accounting derivation rule (ADR) for journal line type 'INV' will be like this:

  • ADR1 XX
  • ADR2 XX
  • ADR3 XXXX
  • ADR4 XX
  • ADR5 XXX
  • ADR6 XXX


So the one mapping rule in 11.5.10 comes across as 6 different rules in Release 12. Obviously you don't need 6 different rules to define every journal line type every time. But, this post is about how things migrate so I'll have to go over that another time.

I'm a little short on time right now but hopefully this helps explain a little on how the data and account mapping that existed in 11.5.10 gets mapped over the release 12 during migration.

1 comment:

  1. After upgrade from 11i to R12.1,
    We have noticed that the following 12 ADR (for Process Manufacturing Financials) are not copied from oracle to User
    ALC – Allocation
    ALV – Allocation variance
    CAD – Const Adjustment
    Clearing – Clearing Account
    DCOGS – Deferred COGS
    ERA – Exchange rate adjustment
    ICACC – Intercompany Accrual
    ICCOGS – Intercompany COGS
    ICEXP – Intercompany Expenses
    INV_SUB_FROM – Inventory Transfer from
    INV_SUB_TO – Inventory Transfer To
    RPADJ – Retroactive Price Adjustment

    But, following 12 ADR (for Process Manufacturing Financials) are added (which is not available with oracle users at R12.1)
    ACA – Actual Cost Adjustments
    ACR – Accounts Receivable
    ECO – Evolution variance
    ERV – Exchange rate variance
    IVV – Inventory valuation variance
    GOU – Gain on Usage variance
    ICT – Inventory – Inter company
    RND – EFC Rounding Entries
    SAL – Sales
    SNI – Inventory Shipped Not I
    TAX – Tax Payable
    XFR – Inventory Transfer

    Why it happened?

    Regards,

    Mohammed

    ReplyDelete