Page 1 of 6

">

Troubleshooting Remit To Address in Oracle Receivables [ID 1101855.1]

Modified 01-OCT-2010 Type TROUBLESHOOTING Status PUBLISHED

In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
1. Setup and Usage of Remit-To Address in Oracle Receivables
2. Troubleshooting Remit-To Address Issues and Errors on Transactions
a. Error: Cannot Get Remit To Address
i. Identify The Customer Bill-To Address
ii. Identify the Operating Unit on the Transaction
iii. Check your Remit-To Address Setup
b. Can I Use Additional Factors to Default the Remit-To Address?
c. Remit-To Address is not Defaulting
d. Unable to Delete Obsolete Remit-To Address
e. Remit-To Address Does Not Include All Address Segments
f. Remit-To Bugs and Other Common Errors
3. Troubleshooting Printing Related Remit-To Address Issues and Errors
a. Remit-To Address is Not Printing, No Errors
b. Remit-To address Errors with MSG-43749: There is no remit to address defined for country and state
c. Is it possible to highlight the Remit-To Address when printing?
4. Descriptive Flexfields on Remit-To Addresses
5. Still Have Questions?

Applies to:

Oracle Receivables - Version: 11.5.10.0 to 12.1.2 - Release: 11.5.10 to 12.1

Oracle Trading Community - Version: 11.5.10 to 12.1.3 [Release: 11.5 to 12.1]
Oracle General Ledger - Version: 12.1.1 and later [Release: 12.1 and later]
Information in this document applies to any platform.
Executable:RAXTRX - Autoinvoice Import Program
Form:ARXTWMAI.FMB - Transactions
Report:ARXSGPO.RDF - Print Statements
Report:ARDLP.RDF - Dunning Letter Print

Purpose

Oracle Receivables (AR): AutoInvoice Information Center > Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 > 1101855.1

The purpose of this note is to explain steps in diagnosing and troubleshooting Remit To Address issues that occur in Oracle Receivables. This note is primarily
focused on presentations that occur in the AR Transaction Workbench and AutoInvoice related to the use of the Remit To Address but some solutions may be
applicable to Order Management and other modules in the Order-to-Cash flow.

For more on setting up Remit-To Addresses see Note 1101666.1 How to Setup a Remit-To Address in Release 12 Oracle Receivables

For AutoInvoice, this note should be used in conjunction with the following two articles:
Note 1067402.1, AutoInvoice Setup for Release 12: A Case Study Using a Simple Script
Note 1075757.1, Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12

Last Review Date

September 16, 2010

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in
troubleshooting.

Troubleshooting Details

1. Setup and Usage of Remit-To Address in Oracle Receivables

Define remit-to addresses to let your customers know where to send payment for their invoices. Receivables uses the addresses that you define in the Remit To
Addresses window to provide default remit-to information when you enter transactions. Remit-To Addresses are also printed on invoices and optionally printed on
Statements and Dunning Letters (Based upon the selections in the System Options window for AR).

If you use AutoInvoice but have not defined a remit-to address that can be derived for a specific bill-to address, AutoInvoice will reject all invoices for which it could
not determine a remit-to address with the following message in the AutoInvoice Import Execution report:

Errors: 1) Cannot get remit to address

If you do not wish to set up a remit-to address for each location, you can set up one remit-to address with a default assignment. Receivables will then use this
address for all locations or for any locations for which you do not have specific location assignments. This ensures that AutoInvoice will not reject invoices because it
could not determine a remit-to address.

For more on setting up Remit-To Addresses in Oracle Receivables including step-by-step instructions and screenshots, refer to Note 1101666.1, How to Setup a
Remit-To Address in Release 12 Oracle Receivables.

2. Troubleshooting Remit-To Address Issues and Errors on Transactions

a. Error: Cannot Get Remit To Address

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=TROUBLE... 3/9/2011
 Page 2 of 6

This is the most common error reported for Remit-To Addresses. The steps below outline how you can determine what value should be used and also
how to fix this problem.

Alternate Error Presentations:

WARNING: No default remit-to address found

WARNING: No default remit-to address (country) found

i. Identify The Customer Bill-To Address

The Remit-to Address is derived based upon the customer Bill-To Address. You should therefore begin troubleshooting by identifying the Bill To
Address (State, Postal Code and Country)

ii. Identify the Operating Unit on the Transaction

For a Manual Invoice, this can be found by looking at the list of values on the Transaction Source as shown below:

For AutoInvoice this can be found

Responsibility: Receivables Manager
Navigation: Control > AutoInvoice > Interface Lines

As shown above the Operating Unit field will be displayed. If AutoInvoice failed with an error, query this form for any rows where the "Errors Exist"
checkbox is checked. This will return a listing of all rejected records. Find the row that is showing a rejection reason of 'Cannot Get Remit To Address'
and take note of the operating unit displayed for that row.

iii. Check your Remit-To Address Setup

Note 1101666.1 explains in detail how to set up a Remit-To Address.

Open the Remit-To Address form as shown below

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=TROUBLE... 3/9/2011
 Page 3 of 6

Responsibility: Receivables Manager

Navigation: Setup > Pring > Remit To Address

Find the row or rows associated to your Operating Unit and check to see if the bill to address is covered by the "Receitps From" definition.

The most common cause of an error in deriving a Remit-To address is in this "Receipts From" mapping. A best practice to avoid problems is to set a
default remit-to address for all countries where you transact. This allows you to avoid errors during AutoInvoice and transaction entry. In the example
above we have defined this California address as the default for all Canadian bill-to addresses.

Note: You can derive an alternate remit-to address with a more narrow definition. For example, if you have a default for the United States with a
New York address but then have a California address that is mapped to a specific Postal Code range, the system will use the California address
ahead of the default address for any address in the from/to postal code range

In this example the Invoice had a Florida address but tthe Receipts From shows no combination that includes this Florida Address. Assuming the Row
above with the New York address also does not cover this Florida addess we can fix this defaulting issue by modifying the "Receipts From" to include
the Bill To address from the Invoice.

b. Can I Use Additional Factors to Default the Remit-To Address?

At this time the only factors available to derive remit-to address are Geography and Operating Unit.

Enhancement Request 6006313 was logged to request the ability to derive remit-to using transaction type

Enhancement Request 4676489 was logged to request that factors other than geography be made available to derive Remit-To

c. Remit-To Address is not Defaulting

Refer to section 2a and verify that the address is properly mapped in the 'Receipt From' setup.

d. Unable to Delete Obsolete Remit-To Address

Receivables does not allow for a remit-to address to be deleted. It is suggested that instead of deleting an address, the Receipt From values under the
address simply be deleted.

e. Remit-To Address Does Not Include All Address Segments

ARXSURMT.fmb , Remit to Address Form has Record group State based on the following query:

select state_code, description

from ar_remit_to_state
where country = :loc.country

Ar_remit_to_state is a view based on hz_locations table. Data is populated in this table as customer addresses are created thus if you have not yet
defined customers the LOV will not show the segments as available for selection.

For more on configuring geographies in R12 refer to Note 554492.1 Setting Up Geography Hierarchy And Address Validation in Release 12

f. Remit-To Bugs and Other Common Errors

Row Release Error String or Presentation Cause Recommended Fix*

1 12.0 When using Multiple Org's in AR, if a transaction type is entered for operating unit "A" and then Bug Recommended Patch:
subsequently changed to a transaction type associated with operating unit "B", the Remit-To address is not 8642210 12.0 Patch 9451008
being updated to reflect this change. Remit To 12.1 Patch 9343518
Address not Fixed File: ARXTWMAI.pld 12.0:
properly 120.163.12000000.72
refreshed 12.1: 120.180.12010000.46

2 12.0 Re-display the remit-to address details, the following error message is displayed: Bug Recommended Patch:
8522000 12.0: patch 8331653
No HZ_CUST_ACCT_SITES was found for ID XXXX Fixed
File: HzPuiAccountSiteAMImpl.java
120.22.12000000.3
12.1Patch 8522000
Fixed File:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=TROUBLE... 3/9/2011
 Page 4 of 6

HzPuiAccountSiteAMImpl.java
120.25.12010000.2

Fix is included in 12.0.6 and 12.1.2

forward

3 12.0 iSetup is creating duplicate Remit-To addresses instead of updating existing records Bug Patch 6729003
6729003 See also Note 550257.1

4 12.0 AR_DEPOSIT_API is not Defaulting the correct remit-to address via the Bill To Location Bug Recommended Patch:
9451008 Patch 9451008
Fixed File: ARXDEPLB.pls
12.0.6
120.11.12000000.4
12.1
120.12.12010000.3

5 12.0 REP-0069: Internal error Remit-To Define remit to address and/or

Address default remit-to
REP-57054: In-process job terminated:Terminated with error: was not
defined and
invoice print
REP-1419: MSG-00100: DEBUG: BeforeReport_Trigger + was
attempted

6 12.0 Query a transaction returns: Remit-To Review/correct setup.

address not
ORA-01422: exact fetch returns more than requested number of rows properly
defined
ORA-06512: at "APPS.ARP_TRX_DEFAULTS_3", line 1463

Debug log showed:

selecting the default remit to address.

EXCEPTION: arp_trx_defaults_3.get_default_remit_to()

EXCEPTION: arp_trx_defaults_3.get_remit_to_address()

---------- Parameters for arp_trx_defaults_3.get_remit_to_address() ----------

p_match_state : NJ

p_match_country : US

p_match_postal_code : 07095

p_match_address_id :

p_match_site_use_id :

EXCEPTION: arp_trx_defaults_3.get_remit_to_default()

7 11.5 - When printing a specific credit memo, it errors with the following: The zip Make sure a valid range is defined
12.1 code for this for the zip code on the transaction.
MSG-43749: There is no remit to address defined for country US and state XX. credit memo
was not 1. Setup\Print\Remit-To Address --
included in > Add a range for zip code 09136
REP-1419: 'remit_to_control_idformula': PL/SQL program aborted. any of the (this problem zip code in this
existing example) which is the zip for the
remit-to credit memo.
ranges. 2. A new line can be added, or you
can alter the existing range for the
that state to include the new zip
code

Alternately you can set a default to

be used to avoid this issue.

8 11.5 - APP-FND-00676 The flexfield routine FDFGDC cannot read the default Incorrect Customer form and Remit-To
12.1 setup of address form share a common
reference field specified for this descriptive flexfield descriptive foundation. Enhancement
flexfield for 3100593 was logged to split these
Customer apart. Until this is fixed it is
Form suggested that the DFF not be
used on the Reference Field for the
Address InformationDFF

9 11.5 Remit-to Address Does Not Exist In The List of Values. Data Perform the following steps to
Corruption resolve this issue: Verify Issue
of unknown 1.) select address_ id
State/Country combination already exists. origin (rare from ra_remit_tos_all
occurrence) where country = 'DEFAULT'
and state = 'DEFAULT';

APP-AR-96282 Error: Invalid value for party_site_id 2.) Select address1, address2,
address3, city, state
from ra_addresses_all
where address_id =
'&address_id_step1';

If query 2 returns no rows then

corruption exists. Contact Support
for assistance

10 11.5 Entering new Remit-To address returns: Corrupt 1. Rebuild the domain indexes
domain associated to the form as
APP-AR-96282: Error: The following SQL error occurred: index described in Note 165115.1
ORA-29861: domain index is marked LAODING/FAILED/UNUSABLE
HZ_CUST_ACCT_SITES_ALL_T1
HZ_LOCATIONS_N15
HZ_STAGE_PARTY_SITES_T1

11 11.5 Opening Remit-To Form from OM returns: Item 1. Order Management

Validation Responsibility, N: Setup > System
ORA-06550: line 1, column 7: Organization Parameters > Values

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=TROUBLE... 3/9/2011
 Page 5 of 6

PLS-00905: object APPS.ARP_STAX_165 is invalid is not set. 2. Select the 'Generic Parameters'
ORA-06550: line 1, column 7: Category.
PL/SQL: Statement ignored 3. Pick your org into 'Item
ORA-06512: at "APPS.ARP_STAX", line 371 Validation Organization'
4. Save your work.

12 11.5 ORA-06550: line 1, column 7: ARP_STAX set parameter

PLS-00905: object APPS.ARP_STAX_5749 is invalid package for plsql_native_library_dir and bounce
ORA-06550: line 1, column 7: this ORG_ID the DB to take effect
PL/SQL: Statement ignored was in
ORA-06512: at "APPS.ARP_STAX", line 371 status
FRM-40735: WHEN-NEW-FORM-INSTANCE trigger raised unhandled exception ORA-06550. invalid.

Tried to compile ARP_STAX_5749 package and got the following error message:

PLS-00920: parameter plsql_native_library_dir is not set.

13 11.5 APP-AR-96282 Error:Value for Party_site_number must be unique. The profile This is ER: 3297103: 'GENERATE
HZ: PARTY SITE NUMBER' IS
Generate 'NO',SITE NUMBER IS
Party Site COUNTED BY AUTO.
Number is
'No' Workaround
----------
The remit-
to-address 1. Go into the responsibility:
does not System Administrator
have the 2. Create a new responsibility to
field to enter have the privileges to create the
the site remit-to-address setup
number in 3. Assign that responsibility to the
that case user in charged to do that
must be
generated or

1. Go into the responsibility: system

Administrator
2. Navigate to Profile \ System
3. Put the profiles
HZ: Generate Contact Number
HZ: Generate Party Number
HZ: Generate Party Site Number
in Yes, for the User designated to
create the remit-to-address or a
Dummy user that will do that

14 11.5 Rep-1401: 'C_Remit_To_Concatenateformula' Ora-01403: No Data Found Remit-To Setup Remit-To Address as per
Address Note 1101666.1
and/or
Default not
defined

*Note that the patch recommendation is for the latest released version of the file and not necessarily the version that included the fix. For example,
if version 46 is the fixed file, the recommended patch may contain version 72 of the fixed file. This fix will include the bug fix referenced here as well
as any other bug fix released since the bug was resolved.

3. Troubleshooting Printing Related Remit-To Address Issues and Errors

a. Remit-To Address is Not Printing, No Errors

By default the system should print the remit-to address from the invoice when printing statements, dunning and invoices. If this does not print verify the
following:

1) Check in Setup -> System -> System options, Alternate Region- Miscellaneous if the Print Remit to Address flag is checked
2) Verify that the invoice has a remit-to address defind

b. Remit-To address Errors with MSG-43749: There is no remit to address defined for country and state

This problem has been reported when the default value contains postal codes. Removing the postal code has proven to remedy this symptom.

c. Is it possible to highlight the Remit-To Address when printing?

In BPA, you can select "Bold" or "Regular" for the content item value.

Hence, you can duplicate the default template and make the remit to address as "Bold". It is even possible to make BOLD only a part of the Remit-To
address.
Instead of using BPA content item 'Remit To Address Formatted', use each individual content item such as 'Remit Address 1', 'Remit Address 2' etc.

4. Descriptive Flexfields on Remit-To Addresses

The top zone of the Remit-To Address form displays the "Address Information" DFF. This is by design. This allows one to see additional address info for the current
address displayed. The "Receipts From" zone is where the "Remit Address Information" DFF is available

5. Still Have Questions?

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support
Receivables Community.

If you find that you require assistance after completing the steps outlined in this note please provide the following information to expedite resolution of your issue:

1) Can you create a manual invoice in AR with this customer Bill To address?
2) Can you replicate this at will ?
3) Do you have any research findings that would help us in understanding or troubleshooting this issue? If yes what?
4) Did this work before? If so what has changed?

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=TROUBLE... 3/9/2011
 Page 6 of 6

5) If this is AutoInvoice related, provide the AutoInvoice Data Collection Test Diagnostic and Setup diagnostic applicable for your release. Refer to Note 1079666.1
for the latest instructions.

Note: This article along with Note 1075757.1, Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 and the auxiliary notes referenced
within attempt to guide you to resolution of most known issues with AutoInvoice and Transaction Workbench Remit-To Address issues..

Related

Products

Oracle E-Business Suite > Financial Management > Credit to Cash > Oracle Receivables

Oracle E-Business Suite > Master Data Management > Customer > Oracle Trading Community

Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger

Back to top

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=TROUBLE... 3/9/2011