11/28/2017 Document 1083467.

How to Setup AutoInvoice For Optimal Performance (Doc ID 1083467.1)

In this Document

Goal
Solution
Manage Receivables System Options
Manage System Profile Options
Create Indexes
Other Considerations
References
Still Have Questions?
References

APPLIES TO:

Oracle Receivables - Version 11.5.10.2 and later

Information in this document applies to any platform.
Executable:RAXTRX - Autoinvoice Import Program
Executable:RAXMTR - Autoinvoice Master Program

GOAL

The objective of this document is to provide step by step instructions on the setups required in Receivables (AR) in order for
AutoInvoice to perform at an optimal level.

This document assumes that you have already set up the Receivables application and that you are able to successfully import
transactions using AutoInvoice with no errors. Please review Note 1067402.1, AutoInvoice Setup for Release 12: A Case Study
Using a Simple Script, for more details.

This document also assumes that you have run the Oracle Receivables AutoInvoice Setup Test and have this information readily
available. The table below shows the Application Release and applicable note that you can follow to get the diagnostic results.

Application Release Note

11i 204790.1

12.0.3, 12.0.4 419055.1

12.0.6, 12.1.1, 12.1.2,12.2 732189.1

The diagnostic validates and documents the basic setup of AutoInvoice for a given batch source in a given operating unit. It
provides System Option, Batch Source, Grouping Rules, Flexfield information, Pro*C file versions, table indexes and disabled
triggers.

For a complete list of diagnostics available by release, please see:

Note 421245.1, E-Business Suite Diagnostics References for R12

Note 179661.1, E-Business Suite Diagnostics 11i Test Catalog

Additionally You can also run the EBS Oracle Receivables AutoInvoice Analyzer (Doc ID 1523525.1)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_69&id=1083467.1 1/7
11/28/2017 Document 1083467.1

SOLUTION

Performance issues are usually caused by multiple problems. The root cause can be product related, issues can also be due to
hardware constraints, network problems, set up issues or other factors. Properly completing the setup steps shown in this
document can help rule out improper or incomplete setup as a cause for any performance problem you may encounter.

M anage Re ce iv able s Syste m Options

The settings in System Options that impact AutoInvoice are under the Trans and Customers tab.

a. Set Purge Interface Table = Y

The interface tables are not meant to store data beyond processing transactions in AutoInvoice. This setting only
purges data that has been processed. Data resulting in error can still be corrected and re-processed.

b. Set Max Memory (in bytes) = Suggested 3MB (3145728 bytes)

This is the maximum amount of memory used for AutoInvoice validation.

c. Log File Message Level = 0

Setting the log file message level to 0 provides the least detailed debug messages but still includes errors and
warning messages. After you have completed the setup of AutoInvoice, you should need only minimal messages
in the log file.

d. Accounting Flexfield

The Oracle Receivables AutoInvoice Setup Diagnostic Test will show your Accounting Flexfield. You should use a
segment that has already been indexed in the GL_CODE_COMBINATIONS table when your Accounting Flexfield
was created. If you are using concatenated indexes, use the first column of the concatenated index as the tuning
segment.

The indexes on GL_CODE_COMBINATIONS are also included in the AutoInvoice Setup Diagnostic Test. Typically,
the Account Segment will contain the most distinct values of the flexfield and should therefore be used as the
tuning segment. Alternatively, you can choose a segment in your Accounting Flexfield which contains the most
distinct values. You can use a query similar to the following to determine which segment has the most distinct
values.

SELECT COUNT( DISTINCT segment1),

COUNT( DISTINCT segment2),
COUNT( DISTINCT segment3),
COUNT( DISTINCT segment4),
COUNT( DISTINCT segment5)
FROM GL_CODE_COMBINATIONS;

Note: This query assumes you are using 5 segments for your Accounting Flexfield. You should modify the query, as
needed, if your Accounting Flexfield has more (or less) segments.

e. System Items

The Oracle Receivables AutoInvoice Setup Diagnostic Test shows indexes on MTL_SYSTEM_ITEMS_B. You
should use a segment that has already been indexed in the MTL_SYSTEM_ITEMS_B table. If you are
using concatenated indexes, use the first column of the concatenated index as the tuning segment.

Typically, the Item Segment will contain the most distinct values of the flexfield and should therefore be used as
the tuning segment. Alternatively, you can choose a segment in your System Items Flexfield which contains the
most distinct values. You can use a query similar to the following to determine which segment has the most
distinct values.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_69&id=1083467.1 2/7
11/28/2017 Document 1083467.1
SELECT COUNT( DISTINCT segment1),
COUNT( DISTINCT segment2),
COUNT( DISTINCT segment3),
COUNT( DISTINCT segment4),
COUNT( DISTINCT segment5)
FROM MTL_SYSTEM_ITEMS_B;

Note: This query assumes you are using 5 segments for your System Items Flexfield. You should modify the query,
as needed, if your System Items Flexfield has more (or less) segments.

f. Territory

The Oracle Receivables AutoInvoice Setup Diagnostic Test shows indexes on RA_TERRITORIES. You should use a
segment that has already been indexed in the RA_TERRITORIES table. If you are using concatenated indexes, use the
first column of the concatenated index as the tuning segment.

Typically, the Country Segment will contain the most distinct values of the flexfield and should therefore be used as the
tuning segment. Alternatively, you can choose a segment which contains the most distinct values. You can use a
query similar to the following to determine which segment has the most distinct values.

SELECT COUNT( DISTINCT segment1),

COUNT( DISTINCT segment2),
COUNT( DISTINCT segment3),
COUNT( DISTINCT segment4),
COUNT( DISTINCT segment5)
FROM RA_TERRITORIES;

Responsibility: Receivables Manager

Navigation: Setup > System > System Options > Trans and Customers Tab

System Options

M anage Syste m Profile Options

a. AR: AutoInvoice Gather Statistics

The recommended setting is Y (Yes) at the Site level. Setting this profile will gather statistics on the interface and
appropriate application tables before running AutoInvoice.

Responsibility: System Administrator

Navigation: Profile > System
Query: AR: AutoInvoice Gather Statistics

b. AR: Maximum Lines Per AutoInvoice Worker

This profile option should be set if you are running AutoInvoice Master with multiple workers and your transactions
typically have a large number of lines. Setting this profile option will help AutoInvoice determine the maximum number of
lines to assign to an AutoInvoice worker.

For example, if you typically process invoices with approximately 10,000 lines per invoice, then set the value = 10,000. If

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_69&id=1083467.1 3/7
11/28/2017 Document 1083467.1
you are unsure, or if the number of lines per transaction are low or varied, you should not enter a value for this profile
option.

Responsibility: System Administrator

Navigation: Profile > System
Query: AR: Maximum lines per AutoInvoice worker

For additional information, please review Note 1151373.1, How to set "AR: Maximum Lines Per AutoInvoice Worker"
profile option.

c. MO: Operating Unit

This profile option should be set up correctly at the responsibility level. It should point to the Default Operating Unit
associated to the Responsibility you are using to run AutoInvoice.

Responsibility: System Administrator

Navigation: Profile > System
Query: MO: Operating Unit

d. AR: Use Parallel Hints (for Release 12.x only)

This profile option was introduced to improve performance of Automatic Receipts/Remittances/Clearance programs by
allowing multiple workers to run in parallel.

Responsibility: System Administrator

Navigation: Profile > System
Query: AR: Use Parallel Hints

Default value is No.

Cre ate Inde xe s

a. Based On Your Line Transaction Flexfield (LTF)

Please refer to Note 1068344.1, Setting Up Receivables Descriptive Flexfields, for an in-depth look at setting up Descriptive
Flexfields.

NOTE: For optimal performance, the following concatenated indexes should be created as UNIQUE indexes.

This example assumes that you are using a context that has 3 segments of the flexfield enabled. You will need to modify
the queries below to include ALL enabled segments of your LTF.

You should create the indexes using SQLPlus as follows:

SQL> CREATE UNIQUE INDEX AR.XX_RA_CUSTOMER_TRX_U1 ON AR.RA_CUSTOMER_TRX_ALL

(INTERFACE_HEADER_CONTEXT,
INTERFACE_HEADER_ATTRIBUTE1,
INTERFACE_HEADER_ATTRIBUTE2,
INTERFACE_HEADER_ATTRIBUTE3);

SQL> CREATE UNIQUE INDEX AR.XX_RA_CUSTOMER_TRX_LINES_U1 ON AR.RA_CUSTOMER_TRX_LINES_ALL

(INTERFACE_LINE_CONTEXT,
INTERFACE_LINE_ATTRIBUTE1,
INTERFACE_LINE_ATTRIBUTE2,
INTERFACE_LINE_ATTRIBUTE3);

SQL> CREATE UNIQUE INDEX AR.XX_RA_INTERFACE_LINES_U1 ON AR.RA_INTERFACE_LINES_ALL

(INTERFACE_LINE_CONTEXT,
INTERFACE_LINE_ATTRIBUTE1,
INTERFACE_LINE_ATTRIBUTE2,
INTERFACE_LINE_ATTRIBUTE3);

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_69&id=1083467.1 4/7
11/28/2017 Document 1083467.1

You only need to create the following indexes if these tables are being populated with interface data. If you are not using
sales credits or accounting distributions, or if you have set up the application to derive these values, then you do not need
to create these indexes.

SQL> CREATE UNIQUE INDEX AR.XX_RA_INTERFACE_DIST_U1 ON AR.RA_INTERFACE_DISTRIBUTIONS_ALL

(INTERFACE_LINE_CONTEXT,
INTERFACE_LINE_ATTRIBUTE1,
INTERFACE_LINE_ATTRIBUTE2,
INTERFACE_LINE_ATTRIBUTE3);

SQL> CREATE UNIQUE INDEX AR.XX_RA_INT_SALESCRDS_U1 ON AR.RA_INTERFACE_SALESCREDITS_ALL

(INTERFACE_LINE_CONTEXT,
INTERFACE_LINE_ATTRIBUTE1,
INTERFACE_LINE_ATTRIBUTE2,
INTERFACE_LINE_ATTRIBUTE3);

b. Ensure all other required indexes are setup as per Oracle Receivables User's Guide

Othe r Conside rations

1. The purpose of the Line Transaction Flexfield is to uniquely identify transaction lines. Therefore, the indexes should be
created as UNIQUE indexes. However, AutoInvoice does not validate or require a unique LTF. If you receive errors
stating that the indexes cannot be created because of duplicate keys, then you should create non-unique indexes by
removing the UNIQUE constraint from the CREATE INDEX statement. Unique indexes will provide better performance
results.

2. Consider using NOLOGGING for these indexes if ARCHIVING is enabled on your database. NOLOGGING should reduce the
amount of time to create the index and will save space in the redo log files. Indexes created using NOLOGGING are not
archived. Therefore, you should perform a backup after you create the indexes. Your DBA should review and advise
whether NOLOGGING is appropriate for your environment.

3. Certain executables should be incompatible with AutoInvoice so as not to interfere with performance as well as data
integrity. The following executalbes are seeded as incompatible with AutoInvoice, please confirm the following:

Incompatibilities with RAXMTR:

Responsibility: System Administrator

Navigation: Concurrent Program > Define
Query Up Short Name = RAXMTR

Program: Autoinvoice Master Program

Short Name: RAXMTR
Application: Receivables

Click on Incompatibilities button, and setup the following:

Application Name Scope Type
---------------------------------- --------------------------------------- ------- ------
Receivables Archive Restart Set Global
Receivables Purge Set Global
Receivables Archive and Purge Set Global
Receivables Archive Preview Set Global
Receivables Refresh AR Transactions Summary Table Set Global
Receivables Autoinvoice Master Program Program Domain
Projects PRC: Tieback Invoices from Receivables Program Domain
Inventory Create Intercompany AR Invoices Program Global
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_69&id=1083467.1 5/7
11/28/2017 Document 1083467.1
Financials Common Modules Reverse Netting Batch Set Domain
Financials Common Modules Settle Netting Batch Set Domain
Financials Common Modules Submit Netting Batch Set Domain
Financials Common Modules Create Netting Batch Set Domain
Process Manufacturing Financials AR Update Set Global
Asia/Pacific Localizations India - Local Concurrent for Processing Set Domain
Order Lines to AR

Incompatibilities with RAXTRX:

Responsibility: System Administrator

Navigation: Concurrent Program > Define
Query Up RAXTRX

Program: Autoinvoice Import Program

Short Name: RAXTRX
Application: Receivables

Click on Incompatibilities button, and setup the following:

Application Name Scope

Type
---------------------------------- --------------------------------------- ------- -
-----
Receivables Archive Restart Set
Global
Receivables Purge Set
Global
Receivables Archive and Purge Set
Global
Receivables Archive Preview Set
Global
Receivables Refresh AR Transactions Summary Table Set
Global
Projects PRC: Tieback Invoices from Receivables Program
Domain
Projects PRC: Interface Invoices to Receivables Program
Domain
Projects PRC: Interface Intercompany Invoices to Program
Domain
Receivables
Process Manufacturing Financials AR Update Set
Global
Order Management Initialize Credit Summaries Table Program
Global
Collections IEX: Populate UWQ Summary Table Program
Global
Asia/Pacific Localizations India - AR Tax and Freight Defaultation Set
Domain
Grants Accounting GMS: Interface Invoices to Receivables Program
Domain

Re fe re nce s

Additional information for all of the setup steps described in this note can be found in the Oracle Receivables User Guide
(Release 12) pages 2-200, 2-210 through 2-212, 2-238 through 2-241.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_69&id=1083467.1 6/7
11/28/2017 Document 1083467.1

Still Hav e Que stions?

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.

To provide feedback on this note, click on the Rate this document link.

REFERENCES

NOTE:419055.1 - R12.0.[3-4] : Oracle Receivables AutoInvoice Setup Setup Test

NOTE:421245.1 - E-Business Suite Diagnostics References for R12

NOTE:179661.1 - E-Business Suite Diagnostics 11i Test Catalog

NOTE:1523525.1 - EBS Oracle Receivables AutoInvoice Analyzer
NOTE:732189.1 - R12.0.6+ : Oracle Receivables AutoInvoice Setup Setup Test
NOTE:1068344.1 - AutoInvoice Setup: How to Set Up Receivables Descriptive Flexfields [Video]

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_69&id=1083467.1 7/7