Payables Invoices Imported from OIE/iExpenses Has 'Track as Asset' Flag Ticked On Distribution Line Stamped With Expense Account
Last updated on MARCH 08, 2017
Applies to:Oracle Payables - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
The issue was reported on app version 12.1.3, but can affect any R12 version.
For an imported Expense Report invoice whose account type was changed from an asset account to an expense account during expense report audit prior to import to AP, it is found the invoice distribution line has the Track as Asset flag ticked.
Even though the account number itself is correct as per the changes made during audit, it is not expected that the Track as Asset flag should be ticked on the distributions, as the Mass Additions program will pick this line up for transfer to FA.
Additional observation: on the Lines tab, the default distribution account is stamped with the original asset account and the Track as Asset flag is ticked.
Expect that on the invoice distribution line whose account is of type Expense, the Track as Asset flag should not be ticked.
Steps to reproduce
1. iExpenses user submits an expense report where a line is coded to an account with Account Type = Asset.
2. Manager approves expense report and workflow awaits review/approval from Payables auditor.
3. In Oracle Expenses Audit, the Payables auditor updates the expense type to one where the account code has the Account Type = Expense.
4. Run the Expense Report Export program.
5. Once the invoice is created, both the invoice line and distribution have the Track As Asset box selected. The invoice line shows the original account code from the time the expense report was created and the invoice distribution shows the new account code updated during the audit process.
6. Validate the invoice and run Create Accounting.
7. Run Mass Additions Create.
8. Invoice line/distribution has been interfaced to Mass Additions.
Workaround: manually untick the Track as Asset checkbox in the distributions to prevent the lines from getting picked up by Mass Additions. For lines already transferred to FA, delete manually.
Defective functionality: additional work required to clean up mistakenly transferred data.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms