PATTAR Completes AutoAccounting Error Code=1: Problem Determining Invoice Type (Doc ID 108051.1)

Last updated on AUGUST 01, 2016

Applies to:

Oracle Projects - Version 11.5.10.0 to 12.2.3 [Release 11.5.10 to 12.2]
Oracle Project Billing - Version 11.5.10.2 to 12.2.3 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
Executable:PATTAR - PRC: Interface Invoices to Receivables
Executable:PAXARTRX - IMP: Create Invoice Organization Transaction Types

Symptoms

When interfacing invoices from Projects (PA) to Receivables (AR), the PRC: Interface Invoices to Receivables process (PATTAR), completes with an error while determining Invoice Type. Your Debug Log file looks similar to the following:
-----------------------------------------------
AutoAccounting returned 4 code combination IDs
Current system time is: 28-APR-100 at 13:42:35
Transferring all I for project ID=1000. AutoAccounting error code=1
Current system time is: 28-APR-100 at 13:42:35
Using Invoice Organization Level for determining Invoice Type
Current system time is: 28-APR-100 at 13:42:35
ORA-01403: no data found

Using Invoice Organization Level for determining Invoice Type
pattlp: pattop() returned error
Error occurred while transferring project with ID 1000.
pattat: pattlp() returned error
pattra main: pattat() returned error while transferring invoices.
-----------------------------------------------

You have previously run the process: IMP: Create Invoice Organization Transaction Types (PAXARTRX)to create invoice types in AR without error or exception. You have also gone through steps 1 to 8 in Note: 1041009.6 and ensured all steps were properly completed.

You may be adding PA functionality to an existing install or this problem may be surfacing now when the process worked previously.

You are employing a User Defined Flexfield (DFF) in the transaction type screen (RAXSUCTT) that populates RA_CUST_TRX_TYPES.ATTRIBUTE1. After creating the transaction types (PAXTRARX). You navigate to the transaction type screen (RAXSUCTT) and query through the PA types (PA Invoices, PA invoice, Projects Invoice PA Credit Memo etc.). You note the value populated in the DFF you defined is not from your previously defined lookup set.

If you make changes to this transaction type but do not change the DFF value and attempt to save, you MAY receive a message that an invalid value is entered.

Cause

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