Payables R12 Accounting
Payables R12 Accounting
5. Why don't the R12 Accounting Setup Forms Work Correctly After
RUP2 is Applied?
Cause: Bug 6266435 (Bug 6266435 is unpublished and unavailable on MetaLink.) This
bug causes the internal profile option 'SLA: Setup user mode' to be visible to the
customer and set with a default value = 'Internal'. This profile should not be visible to
customers and should not be set to default value = 'Internal'. The issues reported in this
Note will occur if this profile option is set to value = 'Internal'.
For the permanent fix, apply the latest Rup patch identified in Note 423541.1.
The workaround is as follows:
1. Navigate Responsibility: System Administrator > Profile > System >Query Profile
Name = SLA: Setup User Mode (INTERNAL use only, do not ship)
2. Set Value = Customer at the Site level only.
3. Save the changes.
4. Test the accounting setup issues and verify they are resolved.
See Note.454132.1 for more information.
6. Why does the R12 Create Accounting Program Show All Ledgers
Available?
Cause: The values available in the Ledger LOV for Create Accounting program are
determined by the profile option SLA: Enable Data Access Set Security in Subledger.
If this profile is set to Yes, then user can only submit create accounting for ledgers to
which they have access. Otherwise, user can submit create accounting for all ledgers.
You can assign ledger set to profile GL: Data Access Set to grant user access to one or
more ledgers.
See Note.434136.1 for more information and the recommended solution.
-- Log an SR with Oracle Support requesting a datafix for data already affected by this
bug.
See Note.729124.1 for more information.
10. Why are the Account Derivation Rules Owner Always Oracle and
COA Not Selectable?
Cause: The issue is caused by the following setup: <profile option SLA: Setup User
Mode is incorrect>.
SLA: Setup User Mode%
In the system profile options. It should be set to "Customer" for the chart of accounts to
be enabled, and for the owner to be "user".
-- To implement the solution, please execute the following steps:
1-Navigate into system Administrator.
2- Check the profile option.
SLA: Setup User Mode
3- Set the profile option to customer for the chart of accounts to be enabled, and for the
owner to be "user".
See Note.457086.1 for more information.
11. Why can't I View Draft Accounting from the Invoice Workbench?
Cause: Bug 6160540 The Tools menu item "View Accounting Events" was not getting
enabled in the case of "Draft Accounting".
Monitor Bug 6160540 via Metalink for the patch release.
Workaround: Navigate: Payables Responsibility > Accounting > Subledger Accounting >
Accounting Events
Query up the invoice by number and accounting date > Click View Journal Entries
See Note.461742.1 for more information.
12. Why can't I Create Accounting Final Right After the Create
Accounting Draft?
Cause: Bug 6509381 R12 APXINWKB Unable Create Acctg In Final Mode After Draft
After Patch 6081092
The fix is included in APXINWKB.fmb version 120.496.12000000.72, available in Patch
6609952.
See Note.463311.1 for more information.
13. Why does the Invoice Workbench Show Fully Accounted Invoices
with Status Accounted = No?
Cause: Unpublished Bug 6975868 - SELF ASSESSED TAX DISTRIBUTIONS ARE
NOT REVERSED AFTER CHANGING IT TO SALES TAX
The current code used to determine the accounting status for invoices looks at
distributions in the ap_invoice_distributions_all and the ap_self_assessed_tax_dist_all
table. Data affected by this bug will have out of sync posted flags in these two tables i.e.
Both tables reference the same accounting event that is accounted, but the posted flags
in ap_invoice_distributions_all are correctly set to Y, and the posted flags in the
ap_self_assessed_tax_dist_all table are incorrectly set to N.
The fix is included in the following files:
apetxsrb.pls 120.81.12000000.40
apaprvlb.pls 120.94.12000000.38
apeventb.pls version 120.45.12000000.18.
The fix is available in Patch 6975868 (This patch is available through controlled release.
Please contact support for assistance with obtaining the patch.)
See Note.603740.1 for more information.
14. Why can't a Canceled Invoice with Manual Holds Removed be Fully
Accounted?
Cause: Bug 6669048 - Cannot Fully Account Canceled Invoices Where Hold Exists. The
reason is that the cancel is not creating the invoice canceled event when there are non
postable holds even after releasing the hold manually.
The fix is included in:
1. Patch 6678578 When A New Item Line Is Added The Inclusive Tax Does not Work
Properly (This patch is available through controlled release. Please contact support for
assistance with obtaining the patch.) This patch is needed to allow the next patch to
apply properly
2. Patch 6669048 Cannot Fully Account Canceled Invoices (This patch is available
through controlled release. Please contact support for assistance with obtaining the
patch.)
3. Contact Oracle Support for a datafix for existing transactions.
See Note.554686.1 for more information and the recommended solution.
All Other and Trading Partner Balancing Segment Value : All Other.
This is explained in Bug 6706969 R12: CANNOT ACCOUNT FOR AN
INTERCOMPANY PAYMENT
To implement the solution, execute the following steps:
1.) Go to General Ledger Responsibility
2.) Setup : Financials : Accounting Setup Manager -> Accounting Setups
3.) Search for the legal entity, click on Update Accounting Options
4.) Click on update for 'Intercompany Accounts'
5.) Click on 'Define Relationships' which is already defined
6.) Click on 'Add Another Row'
7.) Enter Transacting Balancing Segment Value : All Other
Trading Partner Legal Entity : Legal Entity where payment is created
Trading Partner Balancing Segment Value : All Other
Click on 'Define Accounts' and enter the debit and credit accounts, apply the settings.
Follow the same steps and define the All Other- All Other rule from the other Legal
Entity too. This is a mandatory setup. Once this is done run the create accounting
program and verify the results.
See Note 558823.1 for more information.
17. Why don't Voided Payments Associated with Canceled Credit Memos
Account?
Cause: Bug 6712649 - Payments For Canceled Credit Memos Will Not Account.
There was an Application Accounting Definition that was not correct and did not
consider the effect of the canceled credit memo.
The fix is included in Patch 6712649 Payments For Canceled Credit Memos Will Not
Account (This patch is available through controlled release. Please contact support for
assistance with obtaining the patch.)
See Note.472374.1 for more information and the recommended solution.
18. Why doesn't the Create Accounting Process Show Data when Run in
Spanish?
Cause: The behavior is caused by using the wrong template, "Informe Programa
Contabilidad de Submayor - Subplantilla" when running the report.
You should use the parent template "Informe Programa Contable de Submayor Standard" instead of the subtemplate.
Bug 6956888 ONDEMAND:CREATE ACCOUNTING PROCESS IS NOT DISPLAYING
INFORMATION IN SPANISH LENG. Not a bug.
Run the Create Accounting report using the parent template "Informe Programa
Contable de Submayor - Standard" instead of the subtemplate.
See Note 565011.1 for more information.
19. Why won't Some Checks Account: This Line Cannot Be Accounted
Until the Accounting Event for the Application Payables that it
References has Been Fully Accounted?
Cause: Bug 6716764 The form allowed a distribution to be created for a specific line,
and then the line number to be changed thus leaving the distribution orphaned. This
allowed invoices to be validated where the sum of the invoice distributions is not equal
to the invoice amount.
When the payment tries to account the query that checks to see if all distributions are
accounted doesn't work properly since the invoice distribution cannot be linked to any
invoice line.
The fix is included in Patch 6785945 Voucher Numbers Disappear After Changing GL
Date. This is for a different issue but it contains the proper fix. (This patch is available
through controlled release. Please contact support for assistance with obtaining the
patch.)
See Note 553469.1 for more information.
20. Why can R12 Validated Invoices be Deleted and thus Create Orphan
Accounting Events?
Cause: Bug 5970846 (This bug is unpublished and unavailable on MetaLink.) This bug
allows validated invoices to be deleted. Validated invoices should NOT be deleted.
See Note.456619.1 for more information and the recommended solution.
21. Why are Some Accounting Transactions Off 0.01 With No Rounding?
Cause: There are two bugs that have affected this:
Bug 6600117 95340 Error When Accounting Some Transactions Off By 0.01 With No
Round
Bug 6614295 Acctg Some Transactions Off 0.01 With No Rndg
The fix is included in Patch 6614371 R12: Code Combination Id=-1 For Canceled
Payment While Create Accounting. This patch is for a different issue but contains the fix
needed to stop this issue for new transactions.
Contact Oracle Support for a datafix for the existing transactions.
See Note.470403.1 for more information.
22. Why does Create Accounting Result in: Total Debits Not Equal To
Total Credits?
Cause: Data corruption caused by Bug 6916207, the tax exchange rate variance
distributions was mistakenly picked up for gain and loss process.
The fix is included in the following file versions:
APXLASET.ldt v.120.40.12000000.14
SQLAPXLAAAD.ldt v.120.55.12000000.24
apimportaad.sql v.120.1.12000000.1
appostimportaad.sql v.120.2.12000000.1
The fix is available in Patch 6916207. (This patch is available through controlled
release. Please contact support for assistance with obtaining the patch.)
See Note 560005.1 for more information.
23. Why are Functional Currency Invoices Created with the Exchange
Rate?
Cause: Bug 6822383 FUNCTIONAL CURRENCY INV GENERATED WITH
EXCHANGE RATE, WHICH SHOULD NOT BE
In the invoice workbench, while changing supplier, the site, invoice currency, payment
currency, exchange rate etc are defaulted. Sometimes after changing supplier the
currency is defaulted but exchange rate are not redefaulted. So this creates a local
24. Why does the Invoice Status Become Blank After Applying a
Prepayment?
Cause: Bug 6822570 CORRECT THE LOGIC IN GET_APPROVAL_STATUS OF THE
INVOICES UTILITY PKG
The fix is included in Patch/115/sql/apinvutb.pls 120.44.12000000.7, available in Patch
6822570. (This patch is available through controlled release. Please contact support for
assistance with obtaining the patch.)
See Note 733006.1 for more information.
Cause: The issue seems to be happening because of the unpublished bug 6906427.
It is not a problem of duplication of the accounting records, rather it is the problem of the
accounted, and validated which in tax terms would be called as frozen records getting
deleted, and then recreated, as a part of the tax calculation.
Now the original records have already been accounted, and the deletion causes a
recalculation, and reaccounting which results in multiple accounting.
The fix for this bug is included in:
$ZX_TOP/forms/US/
ZXTRLLINEDISTUI.fmb 120.170.12000000.31
$ZX_TOP/patch/115/sql/
zxditaxapplipkgb.pls 120.227.12000000.27
zxditaxlndetpkgb.pls 120.82.12000000.11
zxditaxlnpoppkgb.pls 120.66.12000000.10
zxifdtaccsecpvtb.pls 120.33.12000000.2
zxifdtaccsecpvts.pls 120.10.12000000.2
zxmirecdmsrvpvtb.pls 120.89.12000000.12
zxrilnrepsrvpvtb.pls 120.96.12000000.13
zxriovrdetlnpkgb.pls 120.59.12000000.7
zxriovrsumlnpkgb.pls 120.52.12000000.7
zxriovrsumlnpkgs.pls 120.24.12000000.4
The fix for this bug has been included Patch.6906427:R12.ZX.A (This patch is available
through controlled release. Please contact support for assistance with obtaining the
patch.)
See Note 601679.1 for more information.
Performance
1. Why is there a Performance Issue When Running Accounting Program
Xlaaccup?
Cause: Bug 7319264 R12:Performance Issue When Running Accounting Program
XLAACCUP
See Note 733637.1 for the sql in "ap_payment_extract_details_v.xdf " causing the
performance problem.
The fix is included in ap_payment_extract_details_v.xdf 120.7.12000000.8, available
in Patch 7319264. (This patch is available through controlled release. Please contact
support for assistance with obtaining the patch.)
See Note 733637.1 for more information.
Upgrade
1. Why won't an Upgraded Payment Canceled After the Upgrade
Account?
Cause: Bug 6839052 R12 95359 ERROR FOR PAYMENT CANCELED EVENT
CREATED FOR UPGRADED PAYMENT: Payment Cancelation event does not get
accounted for payments that have been upgraded to R12.
The fix is included in patch 6901404 (This patch is available through controlled release.
Please contact support for assistance with obtaining the patch.)
Note: Patch 6901404 fixes multiples issues, including Bug 6839052. See patch readme
for list of other bugs that are fixed with this patch.
See Note.559191.1 for more information and the recommended solution.
Cause: Bug 6014976 (This bug is unpublished and unavailable on MetaLink.) The
upgrade is creating events in R12 for unaccounted events from R11i with
xla_events.event_status_code = N.
Pre-upgrade: Unpublished Bug 6014976 is fixed in apxlaupg.sql version
120.19.12000000.4. Monitor Metalink for the patch release.
Post-upgrade: Log SR with Oracle support requesting datafix for unpublished bug
6014976. @Note to support: Reference datafix from Bug 6497325 when logging datafix
bug with development for this issue.
Note: The Unaccounted Transaction Sweep does work for these upgraded invoices and
payments and can be used to sweep them to the next period if needed.
See Note.461165.1 for more information.