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)

Saturday, May 4, 2013

General Ledger - Sub ledger - Project Accounting Drill Down

General Ledger - Sub ledger - Project Accounting Drill Down

Well This Is Definitely one of the Complicated One!

Not very Often though but you have a Project which involves Project accounting, and you are working on Reports / or Customization which need an integration form Oracle Projects, General Ledger and Sub-ledger Accounting, you need a very good understanding of how various Database tables of these Different Modules Link with each other.

B Below is a query which can be leveraged to Drill Down or Drill up for the data between

GENERAL LEDGER
SUB-LEDGER ACCOUNTING
PROJECT ACCOUNTING


select
GL.NAME,GJH.JE_HEADER_ID,GJH.JE_CATEGORY,GJH.JE_SOURCE,GJH.NAME,GJH.STATUS, GLL.JE_LINE_NUM,GCC.CONCATENATED_SEGMENTS,XAL.ACCOUNTING_CLASS_CODE,PA.PROJECT_ID,PA.SEGMENT1,PA.NAME,PA.PROJECT_TYPE,PT.TASK_ID,PT.TASK_NUMBER,PT.TASK_NAME,PCD.EXPENDITURE_ITEM_ID,
PE.EXPENDITURE_ITEM_DATE ,
PE.TRANSACTION_SOURCE,
PE.EXPENDITURE_ITEM_DATE ,PE.EXPENDITURE_ITEM_DATE
,888
,PCD.*
--,8,GIR.*,8,XAH.*,8,XAL.*,8,XDL.*,8,PCD.*
from
APPS.GL_JE_HEADERS GJH,
APPS.GL_JE_LINES GLL,
APPS.GL_CODE_COMBINATIONS_KFV GCC,
APPS.GL_IMPORT_REFERENCES GIR,
APPS.GL_LEDGERS GL,
APPS.XLA_AE_LINES XAL,
APPS.XLA_AE_HEADERS XAH,
APPS.XLA_DISTRIBUTION_LINKS XDL,
APPS.PA_COST_DISTRIBUTION_LINES_ALL PCD,
APPS.PA_PROJECTS_ALL PA,
APPS.PA_TASKS PT,
APPS.PA_EXPENDITURE_ITEMS_ALL PE,
APPS.PA_TRANSACTION_SOURCES PTS
WHERE 1=1
AND GJH.LEDGER_ID = GL.LEDGER_ID
AND GJH.JE_HEADER_ID = GLL.JE_HEADER_ID
AND GJH.JE_HEADER_ID = GIR.JE_HEADER_ID
AND GLL.CODE_COMBINATION_ID = GCC.CODE_COMBINATION_ID
AND GLL.JE_LINE_NUM = GIR.JE_LINE_NUM
AND GIR.GL_SL_LINK_ID = XAL.GL_SL_LINK_ID
AND XAL.AE_HEADER_ID = XAH.AE_HEADER_ID
AND XAL.AE_HEADER_ID = XDL.AE_HEADER_ID
AND XAL.AE_LINE_NUM = XDL.AE_LINE_NUM
AND XDL.SOURCE_DISTRIBUTION_ID_NUM_1 = PCD.EXPENDITURE_ITEM_ID
AND PCD.EXPENDITURE_ITEM_ID = PE.EXPENDITURE_ITEM_ID
AND PE.TRANSACTION_SOURCE = PTS.TRANSACTION_SOURCE
--AND PE.TRANSACTION_SOURCE LIKE 'PA%'
AND PCD.PROJECT_ID = PA.PROJECT_ID
AND PCD.TASK_ID = PT.TASK_ID
AND PA.PROJECT_ID = PT.PROJECT_ID
AND TRUNC(GJH.CREATION_DATE) > TRUNC(SYSDATE-25)
--AND UPPER(GJH.JE_CATEGORY) LIKE UPPER('PROJECT%')
AND UPPER(GJH.JE_SOURCE) LIKE UPPER('Project Accounting%')

Thursday, April 4, 2013

General Ledger - Accounts Payables Drill Down - Data Base

General Ledger - Accounts Payables Drill Down - Data Base Query


As Part of Regular GL , Accounts Payables Designing and Troubleshooting, It is required to have a good Understanding of the Links between Various General Ledger and Accounts Payables Table involving Sub-ledger accounting tables, Below is a select statement which provides you the link between GENERAL LEDGER, ACCOUNTS PAYABLES AND  SUB-LEDGER ACCOUNTING Data base Tables

select --distinct aia.invoice_num
GL.NAME,GJH.JE_HEADER_ID,GJH.JE_CATEGORY,GJH.JE_SOURCE,GJH.NAME,GJH.STATUS, GLL.JE_LINE_NUM,GCC.CONCATENATED_SEGMENTS,XAH.GL_TRANSFER_STATUS_CODE,XDL.ROUNDING_CLASS_CODE,XDL.APPLIED_TO_ENTITY_CODE
,AIA.INVOICE_ID,AIA.INVOICE_NUM,AIA.INVOICE_AMOUNT,AIL.LINE_NUMBER,AIL.LINE_TYPE_LOOKUP_CODE,AIL.AMOUNT,GL.CURRENCY_CODE "MRC CURRENCY",GLL.ACCOUNTED_DR,GLL.ACCOUNTED_CR
--,8,GIR.*,8,XAH.*,8,XAL.*,8,XDL.*
from
APPS.GL_JE_HEADERS GJH,
APPS.GL_JE_LINES GLL,
APPS.GL_CODE_COMBINATIONS_KFV GCC,
APPS.GL_IMPORT_REFERENCES GIR,
APPS.GL_LEDGERS GL,
APPS.XLA_AE_LINES XAL,
APPS.XLA_AE_HEADERS XAH,
APPS.XLA_DISTRIBUTION_LINKS XDL,
APPS.AP_INVOICE_DISTRIBUTIONS_ALL AID,
APPS.AP_INVOICE_LINES_ALL AIL,
APPS.AP_INVOICES_ALL AIA
WHERE 1=1
AND GJH.LEDGER_ID = GL.LEDGER_ID
AND GJH.JE_HEADER_ID = GLL.JE_HEADER_ID
AND GJH.JE_HEADER_ID = GIR.JE_HEADER_ID
AND GLL.CODE_COMBINATION_ID = GCC.CODE_COMBINATION_ID
AND GLL.JE_LINE_NUM = GIR.JE_LINE_NUM
AND GIR.GL_SL_LINK_ID = XAL.GL_SL_LINK_ID
AND XAL.AE_HEADER_ID = XAH.AE_HEADER_ID
AND XAL.AE_HEADER_ID = XDL.AE_HEADER_ID
AND XAL.AE_LINE_NUM = XDL.AE_LINE_NUM
AND AID.INVOICE_ID = AIA.INVOICE_ID
AND AIL.INVOICE_ID = AIA.INVOICE_ID
AND AIL.INVOICE_ID = AID.INVOICE_ID
AND AIL.LINE_NUMBER = AID.INVOICE_LINE_NUMBER
AND XDL.SOURCE_DISTRIBUTION_ID_NUM_1 = AID.INVOICE_DISTRIBUTION_ID
AND TRUNC(GJH.CREATION_DATE) > TRUNC(SYSDATE-25)
AND UPPER(GJH.JE_SOURCE) LIKE UPPER('Payable%')
AND AIA.INVOICE_NUM LIKE 'EXP360319%'
AND GL.LEDGER_CATEGORY_CODE NOT IN ('ALC','SECONDARY')
order by aia.invoice_num;

Monday, March 4, 2013

General Ledger - Sub-ledger Accounting Dril Down


As Part of regular Designing and Trouble shooting of General Ledger and Subledger Accounting Analysis it is required to have knowledge of Technical Drill Down and Link between GL and Subledger Tables.

Please see the Below mentioned select Statement to Identify relation between various tables for DrillDown from GL To Subledger and Vice Verse.



select
GL.NAME,GJH.JE_HEADER_ID,GJH.JE_CATEGORY,GJH.JE_SOURCE,GJH.NAME,GJH.STATUS, GLL.JE_LINE_NUM,GCC.CONCATENATED_SEGMENTS,XAL.ACCOUNTING_CLASS_CODE,xal.*
,8,GIR.*,8,XAH.*,8,XAL.*,8,XDL.*--,8,PCD.*
from
APPS.GL_JE_HEADERS GJH,
APPS.GL_JE_LINES GLL,
APPS.GL_CODE_COMBINATIONS_KFV GCC,
APPS.GL_IMPORT_REFERENCES GIR,
APPS.GL_LEDGERS GL,
APPS.XLA_AE_LINES XAL,
APPS.XLA_AE_HEADERS XAH,
APPS.XLA_DISTRIBUTION_LINKS XDL
WHERE 1=1
AND GJH.LEDGER_ID = GL.LEDGER_ID
AND GJH.JE_HEADER_ID = GLL.JE_HEADER_ID
AND GJH.JE_HEADER_ID = GIR.JE_HEADER_ID
AND GLL.CODE_COMBINATION_ID = GCC.CODE_COMBINATION_ID
AND GLL.JE_LINE_NUM = GIR.JE_LINE_NUM
AND GIR.GL_SL_LINK_ID = XAL.GL_SL_LINK_ID
AND XAL.AE_HEADER_ID = XAH.AE_HEADER_ID
AND XAL.AE_HEADER_ID = XDL.AE_HEADER_ID
AND XAL.AE_LINE_NUM = XDL.AE_LINE_NUM
--AND XDL.SOURCE_DISTRIBUTION_ID_NUM_1 = PCD.EXPENDITURE_ITEM_ID
--AND TRUNC(GJH.CREATION_DATE) > TRUNC(SYSDATE-10)
--AND GCC.SEGMENT6 != '000'
--AND UPPER(GJH.JE_CATEGORY) LIKE UPPER('PROJECT%')
--AND UPPER(GJH.JE_SOURCE) LIKE UPPER('Project Accounting%')
and gjh.je_header_id = <je header ID>
and gll.je_line_num =<JE LINE NUMBER>


Sunday, December 23, 2012

Accounts Payables Accounting Flow

Accounts Payables Accounting Flow

Below are few of the key concepts about Accounts Payables Accounting. Accounts Payables have multiple Flows which will be elaborated below. Even though the accounting engine has been moved to Sub Ledger accounting in r12, the Core Concepts of Payables accounting remain same.

Standard Accounts Payable Invoice/ Payment Accounting

One of the most commonly seen scenarios in Accounts payables is Standard Invoice and Payment. Below are the accounting entries for them

Standard invoice creation:

               Dr. Expense / Item Expense / Misc. Expense
                              Cr. Supplier / Liability

The “Expense / Item Expense / Misc. Expense” are derived from the Payables Invoice Distribution where as “Supplier / Liability” Account id derived from Supplier’s Site, from the liability account code combination on that particular site. Although the liability account is defaulted from Payables’ Financial Setup, but you can change the account code according to your need. We can even change the liability account code combination on the Invoice Workbench by enabling the Column from Folders option.

Payment of the Standard invoice:

               Dr. Supplier / Liability
                              Cr. Bank / Cash / Cash Clearing

Now comes the payment, the liability account is fetched from the supplier whose invoice is being paid, the cash clearing or cash account is fetched from the bank you select during the payment. This account is defined during the Bank Account Setup.

PREPAYMENTS / ADVANCES:

Prepayment Invoice creation:

Dr.  Prepaid Expense / Advance Paid
               Cr. Supplier / Liability

Prepayment invoice Payment:

               Dr. Supplier / Liability
                              Cr.  Bank / Cash / Cash Clearing

Standard Invoice creation:

               Dr. Expense / Item Expense / Misc. Expense
                              Cr. Supplier / Liability

Prepayment Application to Standard invoice

               Dr. Supplier / Liability
               Cr. Prepaid Expense / Advance Paid

INVOICES with “TRACK AS ASSETS”:

Track as Asset” is a functionality for moving the items from Oracle Payables to Oracle Assets. It is a check box on the Invoice Line TAB and can be enabled on Distribution Line using the Folder View option. When you check this box and run the “Mass Addition Create Report” from Payables, the items on invoice line or distribution line moves to Oracle Assets. 

Invoice creation:

Dr. Asset Clearing
                              Dr. Supplier / Liability

Invoice transferred to oracle Assets:

               Dr. Asset
                              Cr. Asset Clearing

INVOICE with WITHHOLDING TAX

In the Payables invoices with Withholding tax Scenarios, accounting entry for the WHT payables or Liability account is selected from the supplier defined as a Tax Authority. The WHT expense is picked from the WHT setup.
Taking an example of withholding at time of Payment

Invoice Creation:

Dr. Expense / Item Expense / Misc. Expense
                              Cr. Supplier / Liability

Payment with Withholding Tax 

               Dr. Supplier / Liability
                              Cr. Bank / Cash / Cash Clearing
                              Cr. Withholding Tax

WITHHOLDING TAX INVOICE

               Dr. WHT Expense

                              Cr. Withholding Liability

Monday, October 1, 2012

Legal Entity in R12

Legal Entity:
Legal Entity represents a legal company for which Fiscal and Tax reports are prepared. A Legal Entity can Model to an Enterprise, a Designated Legal unit which is recognized by legal authorities in a country. Legal entity is a business entity that is known to exist to the outside world. Internal organizations or divisions are not legal entities themselves, but are just part of it. In the Multi Organization structure various legal entities could share the same ledger. Both legal entities and operating units are associated with the ledger and the relationship between the legal entity and operating unit is derived based on the ledger.
A legal Entity can be associated to Single Ledger, Multiple Legal Entities can be Associated to a Ledger.
A Legal Entity can be defined using two different Navigations.
  • Legal Entity pages of Accounting Setup Manager
  • Legal Entity pages in Legal Entity Configurator

The only difference between the above two is that Balancing Segment Value can be assigned to legal entities using Accounting Setup Manager.

How Legal Entity Is Mapped to Different Functionalities in Oracle Application R12:

  • Accounting Structures --> Legal Entity is mapped to Balancing Segment Values and Ledgers
  • E Business Tax --> Legal entity is used to identify the Jurisdiction and the parties and where they are registered or located to determine the Tax applicability
  • Bank Accounts --> In Oracle Applications R12 Legal Entity is the Owner of the particular bank account be it a Internal or Remittance bank account. And can be used by The Operating Unit which shares the same ledger as that of the Owning Legal entity.
  • Payables and Receivables -->  the Legal Entity is stamped on the transactions and used to identify the Legal Owner for Legal reporting as well as Tax calculation. The transactions exists within an OU and that OU has a ledger which will account the transactions, if a transaction has more than one LE associated with it then a hierarchy of LE derivation is used to default an LE. Ideally The Legal entity is the owner of that transaction.
  • Intercompany Accounts and Intercompany Processing Rules --> Intercompany journals involve balancing segment values that map to different legal entities. These journals are balanced for each legal entity by using their intercompany accounts.

Thursday, August 23, 2012

Application Implementation methodology (AIM) Template list

Application Implementation methodology (AIM) Template list

Application Implementation Method is a proven approach for all the activities required to implement oracle applications. there are eleven processes of implementation.

1. Business Process Architecture [BP] – This phase outlines:

    *
      Existing Business Practices
    *
      Catalog change practices
    *
      Leading practices
    *
      Future practices

BP.010 Define Business and Process StrategyBP.020 Catalog and Analyze Potential Changes
BP.030 Determine Data Gathering Requirements
BP.040 Develop Current Process Model
BP.050 Review Leading Practices
BP.060 Develop High-Level Process Vision

BP.070 Develop High-Level Process Design

BP.080 Develop Future Process Model
BP.090 Document Business Procedure



2. Business Requirement Definition [RD] - This phase explains about the initial baseline questionnaire and gathering of requirements.

RD.010 Identify Current Financial and Operating Structure RD.020 Conduct Current Business Baseline RD.030 Establish Process and Mapping Summary RD.040 Gather Business Volumes and Metrics RD.050 Gather Business Requirements RD.060 Determine Audit and Control Requirements RD.070 Identify Business Availability Requirements RD.080 Identify Reporting and Information Access Requirements

3. Business Requirement Mapping [BR] – In this phase the requirements of business are matched with the standard functionality of the oracle applications.
BR.010 Analyze High-Level GapsBR.020 Prepare mapping environment
BR.030 Map Business requirements
BR.040 Map Business Data
BR.050 Conduct Integration Fit Analysis
BR.060 Create Information Model

BR.070 Create Reporting Fit Analysis

BR.080 Test Business Solutions

BR.090 Confirm Integrated Business Solutions

BR.100 Define Applications Setup
BR.110 Define security Profiles



4. Application and Technical Architecture [TA] – This outlines the infrastructure requirements to implement oracle applications.

TA.010 Define Architecture Requirements and StrategyTA.020 Identify Current Technical Architecture
TA.030 Develop Preliminary Conceptual Architecture
TA.040 Define Application Architecture
TA.050 Define System Availability Strategy
TA.060 Define Reporting and Information Access Strategy

TA.070 Revise Conceptual Architecture

TA.080 Define Application Security Architecture

TA.090 Define Application and Database Server Architecture

TA.100 Define and Propose Architecture Subsystems

TA.110 Define System Capacity Plan

TA.120 Define Platform and Network Architecture

TA.130 Define Application Deployment Plan

TA.140 Assess Performance Risks
TA.150 Define System Management Procedures



5. Build and Module Design [MD] – This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.
MD.010 Define Application Extension StrategyMD.020 Define and estimate application extensions
MD.030 Define design standards
MD.040 Define Build Standards
MD.050 Create Application extensions functional design
MD.060 Design Database extensions

MD.070 Create Application extensions technical design

MD.080 Review functional and Technical designs

MD.090 Prepare Development environment

MD.100 Create Database extensions

MD.110 Create Application extension modules
MD.120 Create Installation routines



6. Data Conversion [CV] – Data Conversion is the process of converting or transferring the data from legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer Master.
CV.010 Define data conversion requirements and strategyCV.020 Define Conversion standards
CV.030 Prepare conversion environment
CV.040 Perform conversion data mapping
CV.050 Define manual conversion procedures
CV.060 Design conversion programs

CV.070 Prepare conversion test plans

CV.080 Develop conversion programs

CV.090 Perform conversion unit tests

CV.100 Perform conversion business objects

CV.110 Perform conversion validation tests

CV.120 Install conversion programs
CV.130 Convert and verify data



7. Documentation [DO] – Documentation prepared per module that includes user guides and implementation manuals.
DO.010 Define documentation requirements and strategyDO.020 Define Documentation standards and procedures
DO.030 Prepare glossary
DO.040 Prepare documentation environment
DO.050 Produce documentation prototypes and templates
DO.060 Publish user reference manual

DO.070 Publish user guide

DO.080 Publish technical reference manual
DO.090 Publish system management guide



8. Business System Testing [TE] – A process of validating the setup’s and functionality by QA(functional consultant) to certify status.
TE.010 Define testing requirements and strategyTE.020 Develop unit test script
TE.030 Develop link test script
TE.040 Develop system test script
TE.050 Develop systems integration test script
TE.060 Prepare testing environments

TE.070 Perform unit test

TE.080 Perform link test

TE.090 perform installation test

TE.100 Prepare key users for testing

TE.110 Perform system test

TE.120 Perform systems integration test
TE.130 Perform Acceptance test



9. Performance Testing [PT] - Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc
PT.010 – Define Performance Testing StrategyPT.020 – Identify Performance Test Scenarios
PT.030 – Identify Performance Test Transaction
PT.040 – Create Performance Test Scripts
PT.050 – Design Performance Test Transaction Programs
PT.060 – Design Performance Test Data

PT.070 – Design Test Database Load Programs

PT.080 – Create Performance Test TransactionPrograms

PT.090 – Create Test Database Load Programs

PT.100 – Construct Performance Test Database

PT.110 – Prepare Performance Test Environment
PT.120 – Execute Performance Test



10. Adoption and Learning [AP] – This phase explains the removal of the legacy system and oracle application roll out enterprise wide.
AP.010 – Define Executive Project StrategyAP.020 – Conduct Initial Project Team Orientation
AP.030 – Develop Project Team Learning Plan
AP.040 – Prepare Project Team Learning Environment
AP.050 – Conduct Project Team Learning Events
AP.060 – Develop Business Unit Managers’Readiness Plan

AP.070 – Develop Project Readiness Roadmap

AP.080 – Develop and Execute CommunicationCampaign

AP.090 – Develop Managers’ Readiness Plan

AP.100 – Identify Business Process Impact onOrganization

AP.110 – Align Human Performance SupportSystems

AP.120 – Align Information Technology Groups

AP.130 – Conduct User Learning Needs Analysis

AP.140 – Develop User Learning Plan

AP.150 – Develop User Learningware

AP.160 – Prepare User Learning Environment

AP.170 – Conduct User Learning Events
AP.180 – Conduct Effectiveness Assessment




11. Production Migration [PM] – The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

PM.010 – Define Transition Strategy

PM.020 – Design Production Support Infrastructure

PM.030 – Develop Transition and Contingency Plan

PM.040 – Prepare Production Environment

PM.050 – Set Up Applications

PM.060 – Implement Production Support Infrastructure

PM.070 – Verify Production Readiness

PM.080 – Begin Production

PM.090 – Measure System Performance

PM.100 – Maintain System

PM.110 – Refine Production System

PM.120 – Decommission Former Systems

PM.130 – Propose Future Business Direction


PM.140 – Propose Future Technical Direction