APPS - RICE Components

on Sunday, May 30, 2010

The acronym, RICE, stands for Reports, Interfaces, Conversions, and Enhancements (or Extensions).

During a Oracle Applications implementation, additional configuration, design, or programming requirements are necessary to satisfy functional requirements and achieve the desired functionality. The objective during any implementation would be to keep new object development to an absolute minimum. 

RICE objects represent requirements not currently supported within the core functionality of an Oracle Application Module being implemented and thus require additional technical development to satisfy the functional requirement of a organization.

During an Implementation development of RICE components involves

1. Creation of Reports that are not available as standard reports in the oracle apps modules

2. Creation of the Interfaces to external systems.

3. Creation of Conversion programs to transfer data from a legacy system to the new system.

4. Enhancements (or extensions) to the existing system to add additional functionality to existing system without disturbing the core software functionality of the system.

A RICE object has a lifecycle throughout the project that includes approval to develop, functional design specification, technical design specification, coding, testing and implementation. The effort required to complete this development cycle can be significant.

iExpense – Expense Reports for other persons

on Tuesday, May 25, 2010

This feature is called Authorized Delegate.
To have the ability to enter expense reports, withdraw expense reports, etc. for other individuals do the following:

Authorization Preferences (Self-Service Delegate Assignment)
Users can now maintain their own list of authorized delegates in the Expenses Preferences page. An authorized delegate is someone who has the authority to enter expense reports on another user's behalf. This feature existed in previous versions of Internet Expenses as a system administrator task only. The ability for system administrators to define authorized delegates still exists.

Choose Responsibility
Internet Expenses
àNavigate to the Expenses PreferencesàChoose the Authorization Preferences Link

Expenses Entry Delegations
The people in this list can enter expense reports for you. They can also view all of your previously submitted expense reports. Expenses Entry Delegations can be granted by you to another person

Expenses Entry Permissions
You can enter expense reports for the people in this list. You can also view all of their previously submitted expense. Expenses Entry Permissions must be granted to you by the other person (You cannot grant your own Expense Entry Permissions).

OR

Prior to this functionality, Authorized delegate permissions were granted as follows. This functionality still exists.

Choose Responsibility    
System Administrator
àNavigate: SecurityàUseràDefine

Query up the user who is going to be an authorized delegate.

Go to the Securing Attribute regionàAdd a row

Securing Attribute ..: ICX_HR_PERSON_ID
Application ………...…: Self-Service Web Applications
Value …………………….: Choose the employee name from the list of values for the employee for which
…………………………………this user needs to be able to enter expense reports form. Bounce Apache Server
…………………………………and Clear Server Cache if Authorized Delegates are updated using this method.

Payables Transfer to GL

on Thursday, May 20, 2010

In Oracle Applications, modules such as AP, AR, PO, INV ,PA and WIP have concurrent processes that take the information from database structures in which the business activity is stored and inserts it into the GL_INTERFACE table.

List of some of the transferring concurrent programs are:

  • Payables Transfer to General Ledger aka APPPST (AP)
  • Create Journal Entries aka FAPOST(FA)
  • General Ledger Transfer Program ak ARGLTP(AR)
  • AX Transfer to GL akaAXXPSTGL(AX)
  • Interface Burden Cost to GL PADTBC(PA)
    • PRC: Interface Labor Costs to General Ledger PAGGLT(PA)
    • PRC: Interface Usage Costs to General Ledger PASGLT(PA)
    • PRC: Interface Revenue to General Ledger PATTGL(PA)
  • Transfer transactions to GL INCTGL(Inv)
  • Payroll Transfer to GL(PAY)

Journal categories used while AP to GL Transfer

As you know journal categories classifications used to indicate the purpose or nature of your journal entry.Therefore in Payable the categories which are used are Invoices (also called Purchase Invoices), Payments, and All (both Invoices and Payments) and Reconciled Payments (for Payment Clearing and Payment Unclearing Events). More Important the type of journal category you can select depends on the accounting method that you have selected for your set of books.

Doing a Transfer to GL from AP

After you create accounting entries in Payables, submit the Payables Transfer to General Ledger program which send invoice and payment accounting entries to the general ledger interface which is triggered with Journal Import program.

How and what Payables Populates into GL

Except Oracle Fixed Assets module, most of subledger transfer program moved via GL_Interface table. Once you submit the payables transfer to General Ledger program , the data get populates into GL Interface table with accounting information for Payables transactions.

If you use Oracle General Ledger, then Journal Import uses the data in the GL Interface to create journal entries and populates the General Ledger GL_JE_BATCHES, GL_JE_HEADERS,GL_JE_LINES, and GL_IMPORT_REFERENCES tables.

When the Payables Transfer to General Ledger program transfers accounting information to the GL Interface, it always populates the following columns:

  • GL_SL_LINK_ID: value is a unique, sequential number
  • GL_SL_LINK_TABLE: value is APECL for Payables actuals, and APENCL for Payables encumbrances.

When you submit the Payables Transfer to General Ledger program you specify whether you want to transfer accounting information in summary or detail, and you specify the journal category. The parameters you select affect what is transferred to GL Interface columns REFERENCE21–REFERENCE30.

When you transfer in Details

When you do a transfer in details , these information get populated in GL_Interface.

Purchase Invoices
Records for the Purchase Invoices journal category debit the Expense account (including exchange rate variance and invoice price variance accounting entries), and credit the Liability account.

  • Reference21: supplier name
  • Reference22: invoice ID
  • Reference23: distribution line number
  • Reference25: invoice number
  • Reference26: AP Invoices
  • Reference27: set of books ID
  • Reference30: type of account charged: Liability or Expense

Payments
Records for the Payments journal category debit the Liability account,credit the Cash account, and are charged to the Discount, RealizedGain/Loss, Future Payment, and Rounding accounts.

USER_JE_CATEGORY_NAME: Payments
USER_JE_SOURCE_NAME : Payables

  • Reference21: supplier name
  • Reference22: invoice ID
  • Reference23: check ID
  • Reference24: check number
  • Reference25: Paid invoice number
  • Reference26: AP Payments
  • Reference27: set of books ID
  • Reference28: invoice distribution line number
  • Reference29: invoice payment ID
  • Reference30: account charged: Liability, Cash, Discount, Exchange Gain,Exchange Loss, Future Pay, or Rounding

Reconciled Payments
Records for the Reconciled Payments journal category are charged to the Cash Clearing and Reconciliation Accounting accounts. The Payables Transfer to General Ledger program populates GL Interface reference columns with reconciled payment information as follows:

  • Reference21: supplier name
  • Reference23: check ID
  • Reference24: check number
  • Reference26: AP Reconciled Payments
  • Reference27: set of books ID
  • Reference30: account charged: Cash, Cash Clearing, Charges, Errors,Exchange Gain, Exchange Loss, or Rounding

Query for Subledger Transfer to GL

If you want to get details of payments and invoices on the journals transferred to GL, use this to get the result. You can also fine tune with period , currency or clearing company code.

select glcc.segment1 "Company"
, gjjlv.period_name "PERIOD"
, gjb.name "JOURNAL BATCH NAME"
, gjjlv.header_name "JOURNAL SOURCE"
, gjjlv.line_reference_1 "SUPPLIER NAME"
, gjjlv.currency_code "CURRENCY"
, invoice_type_lookup_code "TRANSACTION TYPE"
, gjjlv.line_reference_5 "TRANSACTION NUMBER"
, aia.invoice_date "TRANSACTION DATE"
-- , gjjlv.je_source "SOURCE"
, gjjlv.line_entered_dr "ENTERED DEBIT"
, gjjlv.line_entered_cr "ENTERED CREDIT"
, gjjlv.line_accounted_dr "ACCOUNTED_DEBIT"
, gjjlv.line_accounted_cr "ACCOUNTED_CREDIT"
,glcc.concatenated_segments "CHARGE ACCOUNT"
FROM apps.GL_JE_JOURNAL_LINES_V gjjlv
, gl_je_lines gjl
, ap_ae_lines_all aala
, gl_je_headers gjh
, gl_je_batches gjb
, ap_invoices_all aia
, apps.gl_code_combinations_KFV glcc
, po_vendors pv
WHERE gjl.gl_sl_link_table = 'APECL'
AND gjl.period_name ='NOV-2008'—period
AND gjjlv.currency_code = --currency code
AND gjb.je_batch_id = gjh.je_batch_id
AND gjh.je_header_id = gjl.je_header_id
AND gjh.period_name = gjl.period_name
AND gjh.set_of_books_id = gjl.set_of_books_id
AND glcc.code_combination_id = gjl.code_combination_id
AND gjjlv.je_batch_id = gjh.je_batch_id
AND gjjlv.je_header_id = gjh.je_header_id
AND gjjlv.line_je_line_num = gjl.je_line_num
AND gjh.period_name = gjjlv.period_name
AND gjh.set_of_books_id = gjjlv.set_of_books_id
AND glcc.code_combination_id = gjjlv.line_code_combination_id
AND aala.code_combination_id = gjl.code_combination_id
AND aala.gl_sl_link_id = gjl.gl_sl_link_id
AND aala.reference5 = aia.invoice_num
AND gjh.set_of_books_id = aia.set_of_books_id
AND pv.vendor_id = aia.vendor_id
AND gjjlv.line_reference_1 = pv.vendor_name
ORDER BY aia.invoice

Troubleshooting AP To GL Program

Issue 1 :Why my payments and/or invoices that are not posting to GL and you believe they should post.

Resolution:1) Invoice should not be Hold :Make sure invoices are ready to post. An invoice must be approved and/or have no posting holds in order to be selected for posting. To ensure that your invoices are ready to post, you should run autoapproval and review the hold reports.

  • Invoice Hold Report - displays all hold invoices.
  • Posting Hold Report - only displays invoices with holds that prevent posting.
  • Matching Hold Report - only displays invoices with matching holds.

2) Ensure payments are made. You must insure that all your payment batches have been completed in all sense , they should be either confirmed or canceled.

Make sure period will not close if there are payment batches in a status other than confirmed or canceled.

Issue 2: Sometime transfer AP Transfer to GL takes Longer time?

Resolution :
This should not be a case, if you are experincing the program takes longer check any locks from database side.

Issue 3: Is there any Pre-requisite for AP to Gl transfer?

Resolution:
Yes, Here is the Sequence to follow:

  1. Run Invoice Validation process
  2. then run Payables Accounting Process and you have the option of transferring to GL

You may also submit payables transfers to GL later.

Issue 4: While Transfer why my DFF not populated?

Resolution:
The DFF in the AP Invoice will not get transferred to the GL and this is an Intended functionality till 11i.

A note on Payables Transfer to General Ledger Report

This report has a summary section which gives totals of the accounting entries transferred to the gl interface table.

It has two sections which show exceptions:

  • one section shows accounting entries that could not be transferred because they were in an error status
  • second sectiom shows transferred due to a discrepancy between the accounted account and the account in the general ledger.

R12 GL Setup - Implementation Considerations

on Monday, May 17, 2010

Chart of Accounts

Share the same value set for the balancing segment across charts of accounts

Determine the Number of Legal Entities to Assign in an Accounting Setup based on

ØStatutory and legal requirements for legal entity accounting, such as document sequencing,
…..tax accounting, and intercompany accounting
ØBusiness Needs

Types of Accounting Setups

Accounting Setup with No Legal Entity (LE)

ØCan be used for GL only implementations
ØUsed for a business need where no legal entity is required or management reporting
ØCannot maintain legal entity context in subledger transactions
ØCannot set up Operating Units
ØCannot use Advanced Global Intercompany Accounting System

Accounting Setup with One LE

ØCannot perform lump sum payments across legal entities in AP

Accounting Setup with Multiple Les

ØCannot perform autonomous document sequencing and tax that is unique per legal entity
ØConsider local laws that prohibit commingling transactions with multiple Les

Choosing the Ledger to be the Corporate Representation

Best practice is to choose the primary ledger to be the corporate representation in the local currency:

ØProvides the most detail
ØAllows you to assign a subledger level reporting currency if you want to maintain a detailed
…..additional currency representation

Note:
Secondary Ledgers cannot have subledger level reporting currencies assigned

Legal Entity (LE) Accounting

LE above Ledger

If you require multiple primary ledgers to perform accounting for the same legal entity, you must create dummy legal entities because a legal entity can only be assigned to one accounting setup, not multiple accounting setups

LE = Ledger

If legal entity equals the primary ledger, you may choose not to assign balancing segment values to the legal entity

LE Below Ledger

Legal entities should be represented by one or more balancing segment values

Balancing Segment Value (BSV) Assignment

ØNo BSVs Assigned = All values available for data entry
ØAssign specific BSVs to LEs at any time
ØBehind the scenes, BSVs assigned to LEs are automatically assigned to the ledgers
ØNo BSV validation performed across accounting setups
ØBSV assignment is required for Intercompany Accounting
ØOptionally assign BSVs to the ledger for non-legal entity related transactions, such as
…..management adjustments
ØBefore BSVs can be assigned to the ledger, they must be assigned to LEs first, if used

Reporting Currencies (RC)

ØJournal and Subledger level RCs act like regular ledgers
ØTo automatically populate historical data, run the Create Opening Balance Journals in
…..Reporting Currency program.
ØConversion for subledger sources that uptake SLA are disabled for Subledger Level SLs
ØWhen posting a journal to the PL, journals for the RC will be automatically created/posted in the
…..same batch. Ensure same open periods for source ledger and RC
ØData access set should include same write access to source ledger and Reporting Currencies
…..to prevent posting errors

Subledgers that uptake SLA (Assets, Budget Execution, Cash Management, Cost Management, Inventory, Oracle Loans, Payables, Payroll, Property Manager, Purchasing, and Receivables)

Secondary Ledgers (SL)

ØCan be added at any time with an unlimited number allowed
ØTo populate historical data, use Consolidation (GCS)
ØSecondary Ledgers cannot have Subledger Level RCs assigned
ØCOA Mapping required if COAs are different between the PL and SL. COA Mapping can be used if the
…..COAs are the same except for Subledger Level SLs
ØConversion for subledger sources that uptake SLA are disabled for Subledger Level SLs

APPS in IE8 and Chrome

on Sunday, May 2, 2010

Microsoft Internet Explorer 8 is now certified as a client browser for Oracle E-Business Suite Release 12.

E-Business Suite Release 12.0 Prerequisites
         R12.ATG_PF.A.DELTA.6 (patch 7237006) or later
         Oracle Forms Version 10.1.2.3 or later
         Windows XP Service Pack 2 or 3/Windows Vista Service Pack 1 or 2

E-Business Suite Release 12.1 Prerequisites
         Oracle E-Business Suite 12.1.1
         Windows XP Service Pack 2 or 3/Windows Vista Service Pack 1 or 2

Google Chrome

You will not be able to use google chrome for running oracle applications.Google Chrome is in beta for now.No dynamic apps will run.Even if you install Jinitiator after getting a prompt, it will not be able to launch application.But google will make it available soon.