Monday, January 27, 2014

Sub-Ledger Accounting


Sub-Ledger Accounting

Sub ledger accounting traditionally had accounting rules spread across multiple Products and Sub ledger applications hence it was Difficult to keep the rules up to date and manage.
And if there used to be any requirement which requires a different Accounting treatment as per different geographies, Regulations  or entity it was extremely difficult to implement and many times the ultimate solution was to implement a customization or pass manual Adjustment entries.
The New Sub Ledger accounting feature of oracle E-business Suite R12 popularly known as SLA addresses such issues through a central accounting rule engine allowing among other things, Superior controller ship of definition of accounting rules.

SLA is a rule based accounting Engine that introduced the ability to define how transactions originating in Sub Ledgers can be Accounted. One of the significant benefits of SLA is the ability to generate multiple accounting representations (IFRS and local GAAP) for a single sub ledger transaction.

Hence in Simple words, Different from 11i where accounting Entries used to get created in respective Sub ledgers and then get transferred to GL, In R12 the Entries get created using SLA for all the Sub ledger applications and then gets transferred to GL. Hence it would be appropriate to say SLA is placed between different Sub ledgers such as AP, AR, CE, PA and General Ledger as mentioned in below. 



Sub Ledger Accounting Gives capability to Massage/ Change the accounting entries which gets generated as part of the Standard Sub Ledger application specific account so as to have the accounting entries posted to the desired accounts to address various geographies or entity specific accounting requirement




Above Example shows how the accounting String (A.B.C.D) generated by SubLedger Applications (Eg: AP, AR, CE) can be altered to A1.B1.C1.D1 to achieve specific Accounting requirement and then can be transferred to general Ledger.


Sunday, January 26, 2014

WebADI Common Errors

WebADI Common Errors

Web ADI Configuration Error    
     BNE_UIX_PHYSICAL_DIRECTORY is not configured.

This error can occur under several conditions:
  • Unable to open WebADI
  • After running Autoconfig on nodes not able to upload files
  • When selecting the 'Desktop Integrator' Responsibility the seeded menu options produces the error
  • After installing Oracle E-Business suite R12 and attempting to create a hierarchy using the create spreadsheet functionality(WebADI)
  • When creating a Layout as Trade Management Administrator
  • When attempting to do an Import inside the activity screen in Marketing Online the error occurs

Some Helpful metalink Notes:

  • WebADI - Web Applications Desktop Integrator BNE_UIX_PHYSICAL_DIRECTORY is not configured Error in Release 11i and R12.x (Doc ID 1312156.1)
  • Error BNE_UIX_PHYSICAL_DIRECTORY Is Not Configured in R12 When Attempting to Use WebADI Spreadsheet to Create Hierarchies (Doc ID 430991.1)
  • WebADI Create Layout In Trade Management Error: "BNE_UIX_PHYSICAL_DIRECTORY is Not Configured." (Doc ID 413289.1)
  • BNE_UIX_PHYSICAL_DIRECTORY Is Not Configured Error (Doc ID 888386.1)