Oracle R12 P2P Accounting Troubleshooting Notes - by Dinesh Kumar S

R12: P2P Accounting & Troubleshooting Notes - by Dinesh Kumar S 1


Accounting Entries

Payables (AP) (Oracle Document Reference)


Types of Accounts Account

Type

Description

Liability Accounting statement which tracks how much a person or business owes a creditor.

A common example of a liability is accounts payable. Accounts payable arise when a company purchases goods or services on credit from a

supplier. When the company pays the supplier, the company's accounts

payable is reduced.

Prepayment A prepayment is a type of invoice you enter to pay an advance payment for to a supplier or employee. This account captures this payment

information.

For example, you may need to pay a deposit on a lease, or you may need to pay an employee an advance for travel expenses. You can later apply

the prepayment to one or more invoices or expense reports you receive

from the supplier or employee to offset the amount paid to them.

Types of Prepayment: o Temporary

o Permanent

Temporary:

Temporary prepayments can be applied to invoices or expense reports

you receive.

For example, you use a Temporary prepayment to pay a hotel a catering

deposit. When the hotel's invoice arrives, apply the prepayment to the

invoice to reduce the amount you pay.

Permanent:

Permanent prepayments cannot be applied to invoices.

For example, you use a Permanent prepayment to pay a lease deposit for

which you do not expect to be invoiced.

Bill Payable You can use Bills Payable to control the timing of your payments and, therefore, control your cash flow.

A bill payable, formerly known as a future dated payment, instructs your bank to disburse funds to your supplier's bank on a specific date known

as the maturity date.

Other commonly used terms for this type of payment are notes payable or promissory notes.


Account Type Description

Discount Taken Payables use this account to record the discounts you take on payments.

Use the Discounts Taken and Lost report to identify payments for which you could have taken a discount, but did not.

If you find that you are losing discounts, you can change your system and supplier defaults and modify your payment batch selection

criteria to make sure that you take all valid discounts.

PO Rate Variance

Gain/Loss

Payables use these accounts to record the exchange rate variance gains/losses between your purchase order and invoice.

Payables calculate these amounts during Approval. You can view the distribution amount for these variances in the

Distribution Inquiry window.

Expense Clearing This will be a default liability account for iExpenses expenses reports imported into Oracle Payables.

The Expense Clearing Account field is also available in the Card Program window. If you define the Expense Clearing Account field in

the Card Program window, the value you define there will take

precedence over the value in the Oracle Payables Financial Options

window.

Miscellaneous Enter a Miscellaneous account if you want to use a specific account for miscellaneous charges.

If you leave this value blank, then miscellaneous amounts are prorated across the Item lines and charged to the Item line accounts.

Retainage Retainage represents funds withheld from payment to ensure that the contractor finishes work as agreed.

The buying organization releases these funds only after verifying that the contractor has fulfilled all contractual obligations.

Retainage is also called "retention" or "contractual withholds". With Oracle's Complex Work feature, contract administrator can

negotiate retainage terms with the contractor and capture these as

part of the contract. These terms include Retainage Rate and

Maximum Retainage Amount.

Realized

Gain/Loss

When you pay a foreign currency invoice, if the exchange rate changes between invoice entry and payment, Payables automatically

calculates the realized gain or loss and records it in this account.

If you reconcile your payments, Payables also records a realized gain or loss if there is a difference in the exchange rate between the

payment date and reconciliation date.


Account Type Description

Rounding Payables use this account when you use multiple currencies and the payment currency does not round within the payment currency precision.

For example, if a payment rounds to 100.001 UKS, the payment will be for 100.00 UKS, and the rounding error of .001 will be recorded in this

account.

Freight If you enable the Automatically Create Freight Distribution Payables option, you must enter a freight account.

Payables use this account as the default freight account for an invoice. You can override this account during invoice entry.

Cash Clearing The cash clearing account you associate with a payment document. You use this account if you integrate Oracle Payables with Oracle Cash

Management, or if you generate future dated payment documents.

Oracle Payables credits this account instead of your Asset (Cash) account and debits your Liability account when you post uncleared payments.

Oracle Payables debits this account and credits your Asset (Cash) account once you clear your payments in Oracle Cash Management.

You must enable the Allow Reconciliation Accounting Payables option to be able to enter a cash clearing account for a bank account and payment

document.

Cash Cash Management enables you to reconcile payments you created in Oracle Payables against your bank statements.

You can use Cash Management to: Automatically account for the delay in bank clearing of payments by crediting a cash clearing account when you

issue a payment, and clear the balance with a cash account when you

reconcile the payment.

Bank Charges If you have enabled the Allow Reconciliation Accounting Payables option and you are using Oracle Cash Management to reconcile your payments,

enter the bank charges account you are associating with a bank account.

When you reconcile your invoice payments using Oracle Cash Management, Payables creates accounting entries to record your bank

charges using this account.

The account you enter here defaults to the Bank Charges account field in the GL Accounts region of the Payment Documents window.

Bank Error If you have enabled the Allow Reconciliation Accounting Payables option and you are using Oracle Cash Management to reconcile your payments,

enter the bank errors account you are associating with a bank account.

When you reconcile your invoice payment using Oracle Cash Management, Payables creates accounting entries to record any bank

errors using this account. The account you enter here defaults to the Bank

Errors account field in the GL Accounts region of the Payment Documents

window.


Accounting Setups & Controls Accounting Setups: Payables Accounts are setup & controlled at,

Sno. Setups

1. Financial Options

2. Payable Options

3. Supplier Site

4. Bank Accounts

5. Withholding Tax

6. Invoice

7. ebusinss-Tax

Accounting Derivation Hierarchy:

Since accounts are defined @ multiple levels, the below hierarchy is used to derive the same.


For some accounts the accounting details will be defaulted from Payables Organization Level

setups i.e. how the account should behave or which method should follow they are,

Sno.

Default Account Setup Level

1. Prepayment

Payables Option Accounting Options (tab)

2. Bills Payable

3. Discount

4. Interest

5. Withholding Tax Payables Option Withholding (tab)

Types of Accounts & Setup levels:

Account Type Financial

Options

Payables

Options

Supplier

Site

Bank

Accounts

Withholding

Tax

Invoice eBiz-

Tax

Liability Prepayment Bills Payable Discount

Taken

PO Rate

variance Gain

/ Loss

Expense

Clearing

Miscellaneous Retainage Realized

Gain / Loss

Rounding Fright Tax

Difference

Internet

Expense &

Internet

Liability

Cash & Cash

Clearing

Bank Charges

& Bank Errors


Accounts & Its Qualifiers:

Account Type Segment Qualifier

Liability Liability

Prepayment Asset

Bills Payable Liability

Discount Taken Expense

PO Rate variance Gain Revenue

PO Rate variance Loss Expense

Expense Clearing Expense

Miscellaneous Expense

Retainage Liability

Realized Gain Revenue

Realized Loss Expense

Rounding Expense

Fright Expense

Tax Difference Liability

Internet Expense Expense

Internet Liability Liability

Cash Asset

Cash Clearing Asset

Bank Charges Expense

Bank Errors Expense


Setups Details:

Financial Options:


Payables Option:

Accounting Option:


Currency:


Invoice:


Interest:

Supplier Site:


Bank Account:

Withholding Tax:


Identifying Accounting Events in Payables

Predefined Event Entities:

Application Entity Name Description Gapless Event Processing

Oracle Payables AP Invoices Invoices No

Oracle Payables AP Payments Payments No

Event Classes:

Entity Event Class Name

AP Invoices Credit Memos

AP Invoices Debit Memos

AP Invoices Expense Reports

AP Invoices Invoices

AP Invoices Invoice_Burden

AP Invoices Prepayment Applications

AP Invoices Prepayment Invoices

AP Invoices Prepayments

AP Invoices Prepayment_Burden

AP Invoices Prepay_Application_Burden

AP Invoices Standard Invoices

AP Payments Future Dated Payments

AP Payments Payments

AP Payments Reconciled Payments

AP Payments Refunds


Process Categories:

Below are the payables predefined process categories.

Process Categories

Invoice

Payments

Third Party Merge

Accounting Event Class Options:

For the below even classes accounting entries will be created.

Event Class Process

Category

Default Journal

Category

Balance Type

Burden for Invoices Invoices Purchase Invoices Encumbrance

Burden for Prepayment

Applications

Invoices Purchase Invoices Encumbrance

Burden for Prepayments Invoices Purchase Invoices Encumbrance

Credit Memos Invoices Purchase Invoices Actual and

Encumbrance

Debit Memos Invoices Purchase Invoices Actual and

Encumbrance

Invoices Invoices Purchase Invoices Actual and

Encumbrance

Prepayment Applications Invoices Purchase Invoices Actual and

Encumbrance

Prepayments Invoices Purchase Invoices Actual and

Encumbrance

Future Dated Payments Payments Payments Actual

Payments Payments Payments Actual and

Encumbrance

Reconciled Payments Payments Reconciled Payments Actual and

Encumbrance

Refunds Payments Payments Actual and

Encumbrance

Actual balance is the actual balance available in the account.

Encumbrance is the fund reserved for pre-expenditures such as purchase requisition etc.

(which has not reflected in the actual balance yet).


Payables Accounting Definitions

First lets uderstad types of Accounting Methods and its usage. There are two different types of accounting methods,

Sno. Principal Accounting Method

1. Cash Basis

2. Accrual

Cash basis Accounting Accrual Accounting

Cash-based accounting recognizes

income when money is received.

An expense is recognized when it's

paid.

Accrual-based accounting recognizes

income when goods are shipped or

services are rendered.

An expense is recognized when the

business is obligated to pay it.

Example 1:

Your computer installation business finishes a job in November, and doesn't get paid until three

months later in January.

o Under the cash method, you would record the payment in January.

o Under the accrual method, you would record the income in your November books.

Example 2:

You purchase a new laser printer on credit in May and pay $1,000 for it in July, two months

later.

o Using the cash method, you would record a $1,000 payment for the month of July, the

month when the money is actually paid.

o Under the accrual method, you would record the $1,000 payment in May, when you

take the laser printer and become obligated to pay for it.


Advantages and disadvantages of the accrual method:

While the accrual method shows the ebb and flow of business income and debts more

accurately, it may leave you in the dark as to what cash reserves are available, which

could result in a serious cash flow problem.

For instance, your income ledger may show thousands of dollars in sales, while in reality

your bank account is empty because your customers haven't paid you yet.

Advantages and disadvantages of the cash method:

Though the cash method provides a more accurate picture of how much actual cash

your business has, it may offer a misleading picture of longer-term profitability.

Under the cash method, for instance, your books may show one month to be

spectacularly profitable, when actually sales have been slow and, by coincidence, a lot

of credit customers paid their bills in that month.


Subledger Accounting Components:

There are 5 major components involved,

Oe of the ajor opoets is Subledger Accounting Method (SLAM. This is othig ut the Principal Accounting Methods we discussed above.

Five Subledger Accounting Methods are seeded in the Application.

Application Accounting Definitions Subledger Accounting Methods

Encumbrance Accrual Accrual with Encumbrance Accounting

Encumbrance Cash Cash with Encumbrance Accounting

Accrual Basis Standard Accrual

Cash Basis Standard Cash

When we want budgetary control to be associated with accounting method choose

Encumbrance Accounting.


Subledger Accounting Method (and) Create Accounting:

Accrual Basis:

Event Class

Assignments

Event Type

Assignments

Create

Accounting

Journal Line Definition

Assignments

Credit Memos All Yes Accrual, Credit Memos All

Debit Memos All Yes Accrual, Debit Memos All

Future Dated

Payments

All Yes Accrual, Future Dated

Payments All

Invoices All Yes Accrual, Invoices All

Payments All Yes Accrual, Payments All

Prepayment

Applications

All Yes Accrual, Prepayment

Applications All

Prepayments All Yes Accrual, Prepayments All

Reconciled Payments All Yes Accrual, Reconciled Payments

All

Refunds All Yes Accrual, Refunds All

Cash Basis:

Event Class

Assignments

Event Type

Assignments

Create

Accounting

Journal Line Definition

Assignments

Credit Memos All No

Debit Memos All No

Future Dated

Payments

All Yes Cash, Future Dated Payments

All

Invoices All No

Payments All Yes Cash, Payments All

Prepayment

Applications

All Yes Cash, Prepayment Applications

All

Prepayments All No

Reconciled Payments All Yes Cash, Reconciled Payments All

Refunds All Yes Cash, Refunds All


Lets see hat happes he budgetary control i.e. with Encumbrance Accounting is enabled.

Accrual with Encumbrance:

Event Class

Assignments

Event Type

Assignments

Create

Accounting

Journal Line Definition Assignments

Burden for Invoices All Yes Invoice Burden and Project Encumbrance

ALL

Burden for Prepayment

Applications

All Yes Prepayment Application Burden and

Project Encumbrance ALL

Burden for

Prepayments

All Yes Prepayment Burden and Project

Encumbrance ALL

Credit Memos All Yes Accrual, Credit Memos All; Encumbrance

Credit Memos All; Encumbrance Reversal

for Credit Memo

Debit Memos All Yes Accrual, Debit Memos All; Encumbrance

Debit Memos All; Encumbrance Reversal

for Debit Memos

Future Dated Payments All Yes Accrual, Future Dated Payments All

Invoices All Yes Accrual, Invoices All; Encumbrance for

Invoices; Encumbrance Reversal for

Invoices

Payments All Yes Accrual, Payments All

Prepayment

Applications

All Yes Accrual, Prepayment Applications All;

Encumbrance Reversal for Prepayment

Applications; Encumbrance Prepayment

Applications

Prepayments All Yes Accrual, Prepayments All; Encumbrance

for Prepayments All; Encumbrance

Reversal for Prepayments

Reconciled Payments All Yes Accrual, Reconciled Payments All

Refunds All Yes Accrual, Refunds All


Cash Basis with Encumbrance:

Event Class

Assignments

Event Type

Assignments

Create

Accounting

Journal Line Definition Assignments

Burden for Invoices All Yes Invoice Burden and Project

Encumbrance ALL

Burden for

Prepayment

Applications

All Yes Prepayment Application Burden and

Project Encumbrance ALL

Burden for

Prepayments

All Yes Prepayment Burden and Project

Encumbrance ALL

Credit Memos All Yes Encumbrance Credit Memos All

Debit Memos All Yes Encumbrance Debit Memos All

Future Dated

Payments

All Yes Cash, Future Dated Payments All

Invoices All Yes Encumbrance for Invoices

Payments All Yes Cash, Payments All; Encumbrance

Reversal for Payments

Prepayment

Applications

All Yes Encumbrance Reversal for

Prepayment Applications; Cash,

Prepayment Applications All;

Encumbrance Prepayment

Applications

Prepayments All Yes Encumbrance for Prepayments All

Reconciled Payments All Yes Cash, Reconciled Payments All;

Encumbrance Reversal for Reconciled

Payments

Refunds All Yes Cash, Refunds All; Encumbrance

Reversal for Refunds


Accounting Hits for Payables Event Classes

Accounts Debit Credit Comments

Expense (AP Accrual) Used: During Manual Invoice Creation. Defaulted: AP Accrual is defaulted when

invoice is matched to PO/Receipt for goods

items.

Tax Defined @ Oracle eBiz-Tax & inserted upon invoice validation

Freight Defaulted: he lie type is Freight. Retainage Defaulted: When invoice is matched to

Service Procurement PO/Receipts.

Note** it is Debited when invoice of type

Retainage Release is reated.

Liability Sourced from supplier site. Invoice Price Variance When invoice is matched to PO/Receipts.

Account hit: Price entered in invoice is

different from that specified in PO.

For Inventory items Inventory AP Accrual account defined @ Organization Parameters.

For Expense items Expense AP Accrual Account

Quantity Variance When invoice is matched to PO/Receipts.

Account hit: Quantity entered in invoice is

different from that specified in PO.

For Inventory items Invoice Price Variance defined @ Organization Parameters.

For Expense items PO Charge Account PO Exchange Rate

Variance

When invoice is matched to PO/Receipts.

Account hit: Foreign Currency rate in invoice

Invoice


is different from PO (at the time of creation).

For Inventory items Exchange PO Rate Variance / Loss Account

For Expense items PO Charge Account Tax Variance When invoice is matched to PO/Receipts.

Tax on invoice is different than PO.

Below tax variance can occur,

1. Tax Rate Variance (TRV)

2. Tax Invoice Price Variance (TIPV)

3. Tax Exchange Rate Variance (TERV)

Tax Rate Variance:

The difference b/w invoice price & PO

Distribution due to difference in tax rate.

Tax Invoice Price Variance:

The difference b/w invoice & PO Distribution

price.

For the above variances (TRV & TIPV) the

accounting hit as below,

For Inventory items Invoice Price Variance Account @ Organization Parameters.

For Expense items PO Charge Account

Tax Exchange Rate Variance:

The difference b/w invoice & PO Distribution

exchange rate.

For Inventory items Exchange PO Rate Variance / Loss Account

For Expense items PO Charge Account. Internet Expense During: Whe ioie type Interest is

created on condition that Interest = System

Account.

If prorate across invoice then Original Invoice

Distribution will be debited.

Internet Liability



Prepayment Sourced from supplier site. Liability


Liability Sourced from supplier site. Prepayment Tax Difference Defaulted: When tax applied for invoice >

applied for prepayment.

Tax applied for invoice is < applied for prepayment then, We need to make sure Tax

difference is not credited.

Prepayment

Prepayment

Application


Maturity Date:

In finance, maturity or maturity date refers to the final payment date of a loan or other

financial instrument, at which point the principal (and all remaining interest) is due to be paid.

Maturity Date = Current Date


Liability Cash Clearing Sourced from bank account. Discount Taken Defaulted: When accelerated cash payment

term is made during discount period.

Withholding Tax Created when payment on condition that apply withhold tax during payment time.

Realized Gain / Loss It is hit when foreign currency rate upon

payment is different upon accrual (Invoice).

Maturity Date = Future Date


Liability Withholding Tax Bills Payables Defaulted: From bank account / supplier site

based on options setup @ Payables Options

form.

Payment


On Payment Date


Bills Payables Cash Clearing Discount Taken


Cash Clearing Bank Charger / Bank

Errors

It is used for difference b/w cleared amount and transaction amount.

Cash Management checks the Tolerance

differences parameter to determine whether

the difference is due to charges / errors.

Payment Maturity

Clearing


Create Accounting

Payables (AP) (Oracle Document Reference)


About Create Accounting Why Create Accounting Program?

It picks eligible accounting events and creates sub-ledger journal entries. Also, geerates a report alled Subledger Accounting Program Report to douet

the results.

Methods to create Accounting Events:

Two ways we can generate accounting entries for Payables (AP) module.

1. Using Create Accounting Program

2. Create online Accounting (Either for Single / batch Transactions)

How to view the Generated Accounting Entries?

Generated entries are available as below,

Oracle Apps Forms in View Accounting / View Accounting Entries Window. uit Subledger Accounting Program Report.

Usage of Subledger Accounting Report:

o Lists Successful events and the subledger journal entries created for the events.

o Errors for failed events

What are the documents for which create accounting program can be run in Payables (AP)?

Invoice Payments Invoice Batch Payment Batch

Modes of Creation Accounting program,

Draft Final Final and Post


Can we adjust the Accounting Entries Generated?

Yes, only if the accounting program is run in Draft Mode.

Reports to review accounting information:

Below is the seeded reports used to review accounting entries details,

Journal Entries report Account Analysis report Third Party Balances report Multi period Accounting reports Subledger Period Close Exceptions reports Open Account Balances Listing


Create Accounting Program - Parameters


Parameter Required? Description

Ledger Yes Ledger for which accounting events to be generated.

Ca restrit the aoutig eets ased o profile SLA: Enable Data Access Security

Process Category Optional We can restrict events based on specific process category.

End Date Yes Process only those events


Accrual & Accounting Process


Accounting Entries Flow

Lets ap the aoe proess ith ourret progras,


Accounting Entries Table Hits:

Note**

The link between Sub-ledgers and XLS_Distribution_Links is based on the Source distribution

Type.

Source Distribution type is nothing but the AP Distribution Tables like

AP_INVOICE_DISTRIBUTIONS_ALL, AP_PAYMENT_HIST_DISTS.

Similarly for rest of the modules the distributions are linked.


Period End Closing - Payables

Sno. Activity Details

1 Complete all transactions Invoices & Credits, prepayments, expense reports, Invoice

Imports & payments.

2 Invoice & Payment Batches Approve all un-approved invoices manually (or) submit

program "Payables Approval".

Confirm or Cancel all incomplete payment batches.

3 Future Dated Payments If you use future dated payments, submit the Update

Matured Future Dated Payment Status Program.

This will update the status of matured future dated

payments to Negotiable so you can account for them.

4 Essential Reports Invoice Hold Report: Lists holds applied to an invoice and

for which journal entries & posting cannot be created.

Journal Entries Report: It lists the accounting information

that has been accounted with Error in detail/summary

listing.

5 Unaccounted Transactions Resolve all unaccounted transactions by submitting

report Unaccounted Transactions Report. It lists all transaction with reasons why accounting entries

cannot be generated for the same.

6 Transfer to GL Transfer all accounting entries to GL by submitting

Transfer Journal Entries to GL. 7 Reconciliation Run the below reports to reconcile,

Account Payable Trial Balance Report Posted Invoice Register

Posted payment Register

Bank Statement reconciliation,

Bank Statement Import

Auto Reconciliation Program

(or) Bank Statement Import & AutoReconciliation

8 Sweep Program Ru the progra Unposted Invoice and Payment Sweep. It trasfers all uaouted trasatios fro one accounting period to another. This program will not

forward accounting transactions with errors.


Payables Reconciliation Process Steps:

We can perform below reconciliation activity,

1. Reconcile Payables Transactions

2. Reconcile Accounts Payables Trial Balance (for given period)

3. Reconcile Payable Transactions to GL

Reconcile Payables Transactions Pre-requisites: before executing of the below

reports ross hek Transfer Journal Entries to GL is suitted already.

Run below reports,

Account Payable Trial Balance Report Posted Invoice Register Posted payment Register

Note** run trial balance report for last period

& current period.

Reconcile Accounts Payables Trial Balance

Current Period Trial Balance =

Last Period AP Trial Balance

+ Current Period Posted Invoice Register

- Current Period Posted Payment Register

For example, consider we are closing

accounting period of June month,

June Trial Balance = May Period AP Trial

Balance + June Posted Invoice Register - June Posted Payment Register

Reconcile Payable Transactions to GL Ru the report Account Payables Trial Balance Report. The opare this account balance with GL account balance for current

period.


Create Accounting - Errors & Solutions

There are various stages at which errors might occur, below are the possibilities.

Case 1:

Program Completion Status

Create Accounting Program Success

Create Accounting Report Error

Case 2: Errors during Online Accounting.

Case 3:


Create Accounting Program Error

Case 4: Period Closing Errors

Case 5:


Accounts Payable Trial Balance Report Error

Let see the troubleshooting steps for each cases.


Case Description:


Create Accounting Program Success

Create Accounting Report Error

Possible Errors:

Error Code Error Message

Error 95353 Subledger Accounting was unable to derive an accounting code

combination.

Error 95340 The total debits and the total credits do not balance for this subledger

journal entry

Error 0 The applied-to sources provided for this line are invalid or incomplete.

Error 95311 The segment value for the account code combination specified in line XX

is not assigned to the ledger

Error 95937 There are either non-accountable events existing in the system

Error 95318 The account code combination id &CCID specified for line &LINE_NUM

does not exist.

Error 95325 The GL date &GL_DATE is not in an open or a future enterable period.

-- This line cannot be accounted until the accounting event for the

application Payables that it references has been fully accounted.

-- The log of Accounting Program shows error: The following REVERSAL

events could not be processed.

-- Error: AP_ACCTG_EVENT_SKIPPED

Case 1



Error 95353 Subledger Accounting was unable to derive an accounting code

combination.

Cause:

Mostly this error occurs when a derivation rule does not exists and system is unable to derive a

rule for specific accounts defined @OU level setups. The accounts as below,

Future Dated Payments Discount Account Cash Clearing Account Liability Account Realize Loss Account Exchange Rate & Tax Exchange Rate Variances Tax Difference Account Bank Error Account

Solution:

Check all accounts are setup properly @organization level like Financial Options, Payables

Options, Payables System Setups and Bank Setups



Error 95340 The total debits and the total credits do not balance for this subledger

journal entry

Cause:

For each Event Class & for its type a Journal Line type exists. Each Journal type associated with

conditions to create a balance entry. This error occurs when,

If oracle Code fix Patches not applied Journal Line types not defined properly for Event class & its types. If conditions associated with journal line type is not correct.

Below are some of the event class & its types, for which this error triggered.

Event Class Event Types

Reconcile Payments Payment Cleared

Prepayment Applications Prepayment Applied

Prepayment Applications Prepayment Application Adjusted

Payment Payment Created

Payment Payment Cancelled

Payment Payment Adjusted

Refunds Refunds Recorded

Future Dated Payments Payments Matured

Solution:

Oracle suggested if required patch is applied it resolves most of these balancing issues. The

details of patches as below,

Event Type Solution

Payment Created Patch 10179705 and Patch 10278211

Payment Adjusted Patch 9699315

Payment Matured Patch 7626300:R12.XLA.A

Payment Cancelled Patch 8319065:R12.XLA.A

Prepayment Applied Patch 11772495 and Patch 10173936

Prepayment Adjusted R12.1 Patch 9474821:R12.AP.B

Refund recorded Patch 10623481

Payment Cleared Patch 18964136

Payment Clearing Adjustment Patch 18964136



Error 0 The applied-to sources provided for this line are invalid or incomplete.

Cause:

The error triggers when,

The transaction line may not be applied to a previous transaction (or) The journal line definition is incorrectly defined to support business flow functionality.

Solution:

Oracle provided required code fix patches to resolve these issues. Even applying the patches if the issues exists, cross check the journal line definitions.


Error 95311 The segment value for the account code combination specified in line XX

is not assigned to the ledger

Cause:

There are numerous causes for this error some of them are,

AP_SYSTEM_PARAMETERS columns might contain -1 Value. Create Accounting error while cancelling Invoices. Cash clearing account might not be defined properly (or) the accounting combination

might be restricted using CVR / SR.

The BSV/Company Code segment is not valid for that ledger.


Solution:

When defining a new OU, properly define Organization level setups like Financial Options, Payables Options, payables System Setup and bank account setups.

If secondary ledger is used, cross check whether it is properly mapped with primary ledger.

If any incorrect LE/BSV is used correct it.


Error 95937 There are either non-accountable events existing in the system or events

which could not be processed because no data could be found on

transaction objects.

Cause:

There are events ready for accounting but they are not picked because the subledger extract data is incomplete or invalid.

Due to Code issues. FND_CONNECTION_TAGGING issue.

Solution:

Apply the code fix patch 8744290. To find the transactions/accounting events which may be causing the issue, use the

following query


SELECT xe.application_id ,

xte.entity_code "Transaction Type" ,

xte.source_id_int_1 "Transaction Id",

xte.transaction_number "Transaction Number",

xe.event_id,

xet.event_class_code ,

xe.event_type_code ,

xe.event_status_code ,

xe.process_status_Code ,

xe.budgetary_control_flag

FROM xla_events xe

, xla_transaction_entities_upg xte

, xla_event_types_b xet

WHERE xte.application_id = &P_APPLICATION_ID

and xte.entity_id = xe.entity_id

and xet.application_id = xe.application_id

and xet.event_type_code = xe.event_type_code

and xe.application_id = &P_APPLICATION_ID

and xe.request_id = &P_CREATE_ACCT_REQUEST_ID

and NOT EXISTS

( select 1

from xla_ae_headers xah

where xah.event_id = xe.event_id

and xah.application_id = &P_APPLICATION_ID

);



Error 95318 The account code combination id &CCID specified for line &LINE_NUM

does not exist.

Cause:

Invoices goes to FUND_CHECK_HOLD due to invalid CCID on NONREC_TAX distributions.

Solution:

This is a bug if this exists apply Patch: 9021265:R12.AP.A.


Error 95325 The GL date &GL_DATE is not in an open or a future enterable period.

Cause:

Period was not opened for all ledgers used.

Solution:

Open GL periods for appropriate ledgers.



Error This line cannot be accounted until the accounting event for the

application Payables that it references has been fully accounted.

Cause:

There are many numerous causes for this error, below are the possible ones.

Affected Transactions Cause

Payment Null invoice line number on tax lines

Accounting events not synchronized.

Journal Line Definition not defined properly.

Payment Created/Clearing Accounting ID is not synchronized between

AP_INVOICE_PAYMENTS_ALL & AP_INVOICE_HISTORY_ALL

Invoices Historical data might not be upgraded during migration in

table XLA_DISTRIBUTION_LINKS_TABLE

Payment Adjustment &

Payment Clearing Adjustment

Total credit & debit does not match. Amount entered does not match. Proper events classes & types might not be defined

for account derivation.

Prepayment There might be deferred tax on prepayment invoice


Error The log of Accounting Program shows error: The following REVERSAL

events could not be processed.

When:

Cannot account for Payment Unclearing of a check Cannot account for Invoice Cancellation of an invoice


Cause:

The cause of the current issue is invalid / incorrect data in XLA_TRANSACTION_ENTITIES. The invoice or payment has 2 rows in XLA_TRANSACTION_ENTITIES and PAYMENT

CLEARED event has different entity_id in xla_events than the PAYMENT CREATED and

PAYMENT UNCLEARED events.

Solution:

Apply patch 9651687:R12.XLA.B.


Error Error: AP_ACCTG_EVENT_SKIPPED

Cause:

If any corrupted data in the payments results in failure of "Create Accounting" program. To skip those corrupted data logic is built such that those events would be stamped with

error "AP_ACCTG_EVENT_SKIPPED".

Solution:

Check for the other error in XLA_ACCOUNTING_ERRORS,this would be the actual error which prevents the payment from accounting.So the accounting error

"AP_ACCTG_EVENT_SKIPPED" can be ignored.


Case Description: Errors during Online Accounting.

Cause: For some of the transactions online accounting cannot be done they are prepayment

applications, voided payments etc.

Solution: Ru the Payables Accounting process.

Case Description:


Create Accounting Program Error

Cause: When the Create Accounting Program completes with Error status.

Solution: Review the log files XLAACCUP and XLAACCPB.

Case 2

Case 3


Case Description: Period Closing Errors

Below errors will be triggered while trying to close the period.

Error: APP-SQLAP 10304: You cannot close the period because exceptions exist:

This is the standard message displayed when trying to close the period while not all

transactions been accounted.

Solution: Run the Period Close Exception Report and try to account them.

ORA-20001: APP-XLA-95103: An internal error occurred:

When you have exceptions reported and the unaccounted transactions program spawned by

Sweep program errors out.

Solution: Assign the profile option "Initialization SQL Statement - Custom" to value "begin null;

end;" at the User level

Case 4


Case Description:


Accounts Payable Trial Balance Report Error

Cause: There are many, mentioned few below,

Invalid reference XLA_SRS_SUBLEDGERS in value set attached to segment Report Definition.

Invoices with Voided Payments or Unapplied Prepayments are Reported Incorrectly on the Accounts Payable Trial Balance.

Performance issues with the report.

Solution: Check below patches are applied.

Patch 8340128 Patches 6996476 and 7293021 Patch.9602525:R12.XLA.A.

Case 5


Create Accounting Performance Issues

Issue Description:

Sometimes the program runs for long time to complete (or) runs slowly.

Below bugs been identified for this performance issue.

Bug# Description

Bug 9366101 Create accounting process takes 2 hours of time, of which around 1 hour is

taken to execute the FUN queries. The cause of the poor performance is due

to the lack of the join condition on the LEDGER_ID column.

Bug 9351919 Filters on Application_ID were missing in several queries, and leading/index

hints were also missing.

Solution:

Step 1: Download & apply below patches.

Patch 9366101:R12.FUN.A Patch 9351919:R12.XLA.A.

Step 2: Cross the below files & its versions.

$FUN_TOP/patch/115/sql/funbalpkgb.pls 120.31.12000000.15 $XLA_TOP/patch/115/sql/xlajebal.pkb 120.153.12000000.28


GL Transfer

(SLA GL) (Oracle Document Reference)


Data Corruption Issues during SLA GL Transfer Process:

Once the accounting entries are generated for all transactions in sub-ledgers it has to be

transferred from Sub-ledger to General Ledger.

During the transfer process some data corruption issues might occur some of them are listed

below.

1. Data with negative LEDGER_ID in the General Ledger (GL) tables.

2. Data marked as "Transferred" in SLA but which has not reached GL.

3. Data marked as "Not Transferred" in SLA, but which has reached GL.

4. Multiple posting issues.

5. Data which is in GL but which has been deleted from SLA (This is NOT applicable for 11i

data)

6. Journal Import failing with EP01 error while running the Transfer Journal Entries to GL

program

7. Data accounted in 11i and transferred to GL in R12 which is missing gl sl link id.

Note** Never cancel the Journal Import program.


How to identify data corruption issues in GL Transfer?

Run XLA GL Diagnostics test.

How to check whether Diagnostics test can be performer or not?

It can be performed only when below patches are applied.

for 12.0.x versions: Patch 8513940:R12.XLA.A for 12.1.x versions: Patch 8765953:R12.XLA.B

Steps to run Diagnostics tests:

Navigation: Application Diagnostics Diagnostic (Tab) Follow the below steps,

No lik Select Application ad selet Subledger Accounting. In GL_DIAGNOSTICS group, select the test "XLA GL Diagnostics".

Note** The XLA GL Diagnostics test has to be run for all the ledgers associated to a primary

ledger.

To identify the ledgers use the below query,

SELECT gled.ledger_id as LEDGER_ID

FROM gl_ledger_relationships glr, gl_ledgers gled

WHERE glr.primary_ledger_id = &p_ledger_id -- Put primary ledger id here

AND glr.application_id = 101 AND ((glr.target_ledger_category_code IN ('SECONDARY','ALC')

AND glr.relationship_type_code = 'SUBLEDGER') OR (glr.target_ledger_category_code IN

('PRIMARY')

AND glr.relationship_type_code = 'NONE'))

AND glr.target_ledger_id = gled.ledger_id

AND Nvl(gled.complete_flag,'Y') = 'Y'

GROUP BY gled.ledger_id;


Input Parameters:

Below are the required parameters,

Responsibility ID Ledger Id Application Id Je Source Name Start Date in YYYY-MM-DD

End Date in YYYY-MM-DD

To get the Application id and corresponding je_source_name, run the query below :

SELECT application_id "Application id" ,je_source_name "Je Source"

FROM xla_subledgers;

Note** to avoid perforace issues please ru script Gather Schema Statistics.

Test Output Details:

The output contains below information,

Version of GL TRANSFER Pkg Key Patches GL_LEDGERS GL_LEDGER_RELATIONSHIPS Negative LEDGER_ID in GL Accounted in 11i but Transferred to GL in R12 with Null GL_SL_LINK_ID Marked as Transferred in XLA but NOT in GL Marked as transferred in XLA but REVERSED in GL Data Exists in GL but Its Corresponding Data Is Deleted in XLA Data in GL but Deleted From XLA Showing XLA Reference Columns Marked as Not Transferred in XLA but in GL Multiple Transfer to GL


FAQ: Transfer to GL (Oracle Document Reference)

What are the tables involved in Transfer to GL and GL Posting?

Subledger Tables

XLA_AE_HEADERS

XLA_AE_LINES

XLA_DISTRIBUTION_LINKS

Interface Tables GL_INTERFACE

XLA_GLT_

GL Tables

GL_JE_BATCHES

GL_JE_HEADERS

GL_JE_LINES

GL_IMPORT_TEFERENCES

What are all different modes available to transfer journals from SLA to GL?

Modes Description

ONLINE During Online accounting use Final Post optio for speifi document i.e. invoice etc.

BATCH Submit Create Accounting program with Transfer to GL parameter

as Y. CONCURRENT REQUEST uittig progra Transfer Journal Entries to GL separately / i

standalone mode. This method uses interface table

XLA_GLT_

How to find the transfer status of accounting entries in SLA?

XLA_AE_HEADERS

Column Value

gl_transfer_status_code Y

gl_transfer_date Populated with a date value i.e. not null column

group_id Populated with a group id i.e. not null column


How to find transfer status and differentiate 11i Vs. R12 accounting entries after upgrade?

XLA_AE_HEADERS

Column Value

gl_transfer_status_code Y

gl_transfer_date Populated with a date value i.e. not null column

group_id Populated with a group id i.e. not null column

upg_batch_id Not null column. This indicates 11i data.

How to merge accounting lines in XLA_AE_LINES table?

In Journal Line Type setups, the accounting lines in XLA_AE_LINES tables can be merged.

Navigation: Accounting Setup Subledger Accounting Setup Accounting Methods Builder Journal Entry Setups Define Journal Line types Choose Field Merge Matching Lines. This field can have below options.

Merge Options Description

ALL Lines in XLA_DISTRIBUTION_LINKS (specific Accounting Header)

+

Journal Line Type (Specific like liability etc.) = XLA_AE_LINES Records

DR/CR Lines in XLA_DISTRIBUTION_LINKS (specific Accounting Header)

+

Journal Line Type (Specific like liability etc.)

+

Debit Side Entries = XLA_AE_LINES Records

NO No merging happens.


What are all different setup options to transfer journals in Detail / Summary format?

Tables involved: The journals from XLA tables will be transferred to GL table.

XLA_AE_HEADERS, XLA_AE_LINES GL_JE_HEADERS, GL_JE_LINES

Below are the setup options available which decides whether to Merge the transactions in GL

tables or not.

Subledger Accounting Options: This setup to determine accounting header can be summarized or not.

Journal Line Types: This setup determines whether accounting lines in XLA_AE_LINES can be summarized or not.

Subledger Accounting Option:

Navigation: Accounting Setup Ledger Setup Define Accounting Setups Query for the ledger & Click Update icon.

Go to Subledger Accounting Options, in Primary ledger section click update icon.

etup the field General Ledger Journal Entry Summarization ith oe of the below values, Summarize by GL Period Summarize by GL Date No Summarization

Journal Line Types:

Navigation: Accounting Setup Subledger Accounting Setup Accounting Methods Builder Journal Entry Setups Define Journal Line types Choose Field Transfer to GL. Note** Lines cannot be summarized if the headers are not summarized.


General Ledger Journal Entry

Summarization

JLT- Transfer to GL System Expected Behavior

Summarize(By GL Date or Period) Summary Summarized Level at,

GL_JE_HEADERS GL_JE_LINES

Summarize(By GL Date or Period) Detail Summarized Level at,

GL_JE_HEADERS Detail Level at,

GL_JE_LINES No Summarization Detail Detail Level at,


No Summarization Summary Detail Level at,


Group by GL Period/GL Date Detail / Summary Merged on condition Same

Journal Category & GL Period/

GL Date,

GL_JE_HEADERS

Detail Level at, gl_sl_link_id will

be populated

GL_JE_LINES

How do you link GL Data with SLA Data?

Usig tale GL_IMPORT_REFERENCES. The joi oditio as elo. GL_IMPORT_REFERENCES.gl_sl_link_id => XLA_AE_LINES.gl_sl_link_id

GL_JE_BATCHES.group_id => XLA_AE_HEADERS.group_id


If gl_sl_link_id does not exist in table GL_IMPORT_REFERENCES how relationship is derived

between GL & SLA data?

Usually using REFERENCE Columns i.e. columns from REFERENCE5 to REFERENCE10 in GL_IMPORT_REFERENCES we can able to identify the relationship.

These columns populated with entity_id, event_id, ae_header_id, ae_line_num, accounted_cr, accounted_dr.

Note** But sometimes these REFERENCE columns might not be populated during transfer

process. This happens when the patch 7512923:R12.XLA.A (for R12.0.x) is not applied.

How many group_ids are created during the transfer process when there is a primary ledger

and associated ALC/reporting ledger?

The primary ledger data and associated ALC/reporting ledger data goes into one group_id.

Data from this one group_id can be split across multiple GL Batches based on other criteria, such as je_category/date/period. However, one GL Batch can only be associated

to one group_id.

How many group_ids are created during transfer process when there is a primary ledger and

a secondary ledger?

Two group IDs are created--One for the primary ledger and one for the secondary ledger.

Two journal import processes are spawned in this case, one for each group_id. If there is failure in the journal import for either ledger, the transfer is rolled back for

both ledgers.

Is there a setup to prevent spawning the Journal Import on instances where a third party

(e.g., Peoplesoft) GL is used?

The profile option "Disable Journal Import" (when set to Yes) prevents the GL Transfer from

invoking the Journal Import. The interface table used in this case is GL_INTERFACE. Setting this

profile option is not recommended if you are using Oracle General Ledger. The profile option is

hidden and disabled in the latest code.


When data will be available in XLA_TRIAL_BALANCES table?

When Journal Import program successfully completed, the data will be available in this table.

Note**

Data from XLA_DISTRIBUTION_LINKS is used to populate the XLA_TRIAL_BALANCES table.

It can also be repopulated during a trial balance rebuild using the "Open Account Balances Data Manager" process.


Journal Import Errors (Oracle Document Reference)

Below are the possible stages where we frequently face issues/errors during journal import.

Importing Journals from SLA / Create Accounting. Transfer to GL does not pick rows/fails.

When e ru Journal Import Execution Report the elo errors ight our, Errors like EP01, EF01, EE01, EU02, EC12 etc. Journal Import Execution Report Ends in ERROR but no errors are displayed in output

also data is marked as transferred in SLA

Error 'LEZL0023: Journal Import can only process data from one table at a time'. Error 'ORA-01460: unimplemented or unreasonable conversion requested'. Transfer to GL or Create Accounting concurrent request was cancelled after Journal

Import was spawned.

GL transfer is not picking data when ledger is secondary and is disabled.

Lets ie steps to trouleshoot aoe errors.

Step 1: Get the below details.

Ledger ID Application ID JE Source Start Date & End Date

Use the below query to get the above details.

SELECT application_id, je_source_name

FROM xla_subledgers;


Error: Journal Import Execution Report shows errors like EP01, EF01 etc.

Errors Solution

If the Journal Import Execution Report shows

Period Error

EP01 this date is not in any open or future enterable period.

EP03 this date is not within any period in an open encumbrance year.

EP04 this date is not a business day. EP05 There is no business days in this

period.

Check Period is open if not open it.

If the Journal Import Execution Report shows

Flexfield Errors like

EF01 This Accounting Flexfield is inactive for this accounting date.

EF02 Detail posting not allowed for this Accounting Flexfield.

EF03 Disabled Accounting Flexfield. EF04 this is an invalid Accounting

Flexfield. Check your cross-validation

rules and segment values.

EF05 There is no Accounting Flexfield with this Code Combination ID.

Cross check the account setup i.e. whether

any CVR (Cross validation rule) exists for this.

Error: Journal Import Execution Report Ends in ERROR but no errors are displayed in output also

data is marked as transferred in SLA

Check the Patch 6748312:R12.GL.A is applied, if not apply it.


Error: Journal Import Execution Report shows error 'LEZL0023: Journal Import can only process

data from one table at a time'

Error: Journal Import Execution Report shows error 'ORA-01460: unimplemented or

unreasonable conversion requested'.

Error: Transfer to GL or Create Accounting concurrent request was cancelled after Journal

Import was spawned/ DB got shutdown while running Journal Import But you can

see XLA_AE_Headers. Gl_transfer_status_code='S'

For all aoe errors hek hether the latest Patch 8691650:R12.XLA.A is applied. If not apply it & resubmit the program.

Error: Another common issue seen is GL transfer is not picking data and ledger is secondary

ledger

Secondary ledger is disabled meaning relationship_enabled_flag in gl ledger is 'N'. Because of

this GL Trasfer doest pik seodary ledger data. Execute the below update query to fix the above error.

UPDATE XLA_AE_HEADERS XAH

SET

XAH.GL_TRANSFER_STATUS_CODE = 'NT'

WHERE

XAH.APPLICATION_ID = &p_application_id

AND XAH.LEDGER_ID = &p_ledger_id -- ledger id of secondary ledger which is disabled

AND XAH.GL_TRANSFER_STATUS_CODE = 'N'

AND XAH.ACCOUNTING_ENTRY_STATUS_CODE = 'F'

AND XAH.ACCOUNTING_DATE BETWEEN TO_DATE('&p_start_date','DD-MM-YYYY') AND

TO_DATE('&p_end_date','DD-MM-YYYY')

AND EXISTS ( SELECT 1

FROM XLA_EVENTS XE

WHERE XE.APPLICATION_ID = &p_application_id

AND XE.EVENT_ID = XAH.EVENT_ID

AND XE.EVENT_ID = XAH.EVENT_ID

AND XE.EVENT_STATUS_CODE = 'P'

AND XE.PROCESS_STATUS_CODE = 'P');


FAQs: Journal Entry & Reversal

Journal Entry:

How to Delete a Journal batch (or) How to delete a Unposted Journal batch?

Query for the journal Batch, follow the below steps.

Journals Enter Close the Form Click Review Batch button. Query for the batch. Using delete icon deletes the unposted journal.

In Journal Entry form why Accounting Periods is not getting listed?

The Accounting period LOV lists oly period ith status Open & Future Enterable.

When a Journal batch cannot be Deleted / modified?

Below are the scenarios where journal batch cannot be deleted / modified.

1. Source is frozen

2. Batch has fund reversed or in process of reserving.

3. Batch is Posted (or) in process of posting.

4. Batch is Approved (or) in process of approval.

If the journal batch comes from Sub-Ledgers it should not be updated. Updating the same may

not synchronize the accounting information between Primary ledger & Sub-Ledger.

Alternate Solution: Instead of updating a new journal can be defined & adjusted.


Can I restrict users from entering negative amounts in journal lines?

As of now no standard functionality available, since some of the GL programs allows negative

amounts. Using form personalization we can implement the same.

Can we copy journal entries?

No, we cannot.

Is it possible to hide batch & Headers appearing in journal screen?

No.

Journal Reversing:

Instead of reversing single journal entry, the complete batch is reversed and posted. How this

can be corrected?

If Unposted: Delete the unposted reversal batches.

If Posted: Reverse the Reversal batch and repost them.

In R12, the Unposted Journals can be reversed?

In R12, only posted journals can be reversed.

Why a journal entry with a source setup for automatic reversal was not reversed?

General Ledger automatically submits the AutoReverse program when a period is opened if the profile option, GL: Launch AutoReverse After Open Period, is set to Yes.

If a journal is created after the period has already been opened, then the AutoReverse program will need to be submitted again manually to pick the new entered journals.


Does the reversal program generate separate reversal batches for each journal in a batch that

is reversed?

Yes. When a batch is reversed, General Ledger creates one reversing batch, with one single journal entry, for each journal entry in the reversed batch.

Therefore a single batch with multiple journals generates multiple reversal batches with a single journal.

In R12, why can I not modify an Unposted reversal journal?

This is the default functionality in Release 12, as a reversal should match the original journal.

Using the profile GL: Edit Reverse Journals can be set to allow the modification.


Period Close

(AP)

(Oracle Document Reference)


Payables Period Close: Diagnostics

Script to be used: ap_pclose_detect_pkg.sql

Current Version of Script: 120.13 (Updated on 16-Jul-2014), check for latest & execute.

Purpose of Script:

It allows us to identify the transactions which affects period close with the corrective action suggested resolving the same.

No data is created, updated, or deleted by this script. This will not close the period. It produces a HTML output all errors/problems related to transactions along with

corrective steps to be taken.

Belo is the Wrapper ripts aailale iside ap_pclose_detect_pkg.sql. period_close.sql: This script can be used to submit the validation procedure for a

particular period.

ap_gdf_detect_pkg.sql: To run the AP Data Validation Report and to check for data corruptions and the corresponding GDFs available.

period_close.sql: To validate all invoices, payments, in a specified period for specified operating units.

Steps for Diagnostics:

Step 1: Run the wrapper SQL file "period_close.sql" to submit the detection procedure.

The detection procedure will create an output file of the format AP-PCLOSE-.html

and a log file of the format AP-PCLOSE-.log. Also, it will indicate the location of this

file and the log file.

Step 2: Review the output file to determine if any transactions have any issue, if yes follow the

corrective action steps else it is safe to close the current period.


Examples to execute the script,

Script Usage Script Execution

To check all transactions stopping period close

for a particular period

SQL> BEGIN

ap_pclose_detect_pkg.main_pc(

p_per_name => '',

p_ledger_id => );

END;

To validate all transactions for one of your

operating units

SQL> BEGIN


p_per_name => '',

p_ledger_id => ,

p_org_ids => '');

END;

To run the same validations but including both

org1 and org2

SQL> BEGIN


p_per_name => '',

p_ledger_id => ,

p_org_ids =>

',');

END;

To run the diagnostics along with the AP Data

Validation Report to check for more

corruptions

SQL> BEGIN

ap_gdf_detect_pkg.main_pc(

p_per_name => '',

p_ledger_id => ,

p_master_gdf => 'Y');

END;


Common issues during Period Closing in AP

Error:

APP-SQLAP 10304 Cannot Close Period - No Data On Period Exception Report, No

Unaccounted Transactions

When: While trying to close the period, where exception report display no data.

Cause: There as a issue i pakage AP_PERIOD_CLOSE_PKG hile returig alue. Fix: Apply Path Patch 9509700.

Error:

AP_SWEEP_ACCESS_ERROR/Insufficient Access Error Appears Attempting to Sweep From

Control Payables Period Form

When: User suits Unaccounted Transaction Sweep fro Cotrol payales period for. Cause: Sometimes MOAC Setups is not done properly (or) responsibility does not have access

to all OUs assiged to ledger. Fix: Chek profile MO: Security Profile is set properly & hek for MOAC steps.

Error:

APP-SQLAP-10304 Cannot Close Period And No Data On Period Exception Report.

When: No Exceptions is listed i Period Close Exception Report ut the syste triggers message still some exceptions exists.

Cause: For some invoice lines, distributions might be missing.


Fix:

Revalidate the Invoice & Execute Create Accounting for the same (or) Delete the invoice.

Error:

R12 Orphan Accounting Events Preventing Closing Period in Payables.

When: The Period Close Exception Report errors out eause of Uated Aoutig Errors.

Cause: Due to budgetary issues like fund check hold in invoice etc.

Fix:

Check PSA critical Patch (14563642:R12.PSA.A R12.0 / 14563642:R12.PSA.B R12.1) is applied.

uit Budgetary Control Optimizer Program. This ill lea-up the orphan processed/unprocessed BC Events.

Error:

Cannot Close Period Due To Untransferred Headers, Multiperiod Accounting.

When: Some of the Header information for accounting events is not transferred i.e. Transfer

Journal Entries to GL concurrent program does not pick up the problem XLA headers.

Cause:

Headers might have created before period open (or) Fix: Ru the Complete Multiperiod Accounting program. This program checks,

The GL dates of all incomplete journal entries that have a GL date that is on or before the end GL date specified in the request parameters and completes these entries as

their GL dates fall into open periods.


Please rate this material @ www.planetsource-code.com.

Thank you