Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Auto Invoice – Parameter and Profile Options

Posted on May 27th, 2007 by Sanjit Anand ||Email This Post Email This Post

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today

Understanding the profile options and some parameter is essential for autoinvoice execution. Understanding is especially helpful when trouble shooting is required to figure out why and where the processing has failed for certain data scenarios. Here is some informative information for profile Options and parameter required for autoinvoice.

As we know system setup can be done from system options, which is as below.

31

 1.Max Memory (in bytes)
  As marked 1 in above picture. This is memory setting for allocating autoinvoice program for validation. It is recommended to set Value to 3,000,000 Bytes.

2.Log File Message Level

This is at 2 in above picture. This is number represents the amount of detail we wish to display Auto Invoice log file.

  • Message Level 0
    This will gives the following entries in the log file:
    Product Version, Program Name, Auto Invoice Start Time, AutoInvoice Concurrent request Arguments, Error and Warning Messages, AutoInvoice End Time, auto Invoice logical Steps.
  •  Message Level 1
    This gives all of the above entries plus:  Time-Stamped function labels
  •  Message Level 2
    This gives you all of the above entries plus:  Sizes of Allocated Arrays, Dynamic SQL Statements, Number of Rows Updated, Inserted and Deleted
  •  Message Level 3
      This gives you all of the above entries plus: Method IV SQL Array Values.

3. Purge Interface Tables
This is marked 3 in above picture. If this is checked then

  • Purges records that are successfully imported into receivables.

It recommended to avoid getting interface tables filled with data that is no more required

4.AR: Autoinvoice Gather Statistics
Specify whether AutoInvoice process analyzes the interface tables or not

  • Null is taken as Yes
  • This profile should be set to “Yes” if type of data populated in the interface tables changes

5.Number of Instances
This is for Load Balancing.

  • Number of CPU -1
  • Maximum allowed 500

6.AR: Maximum Lines per Autoinvoice worker
This is setting for let worker know how many records need to pick. This setting is more important, if you are loading very huge set of data. If any one is doing conversion, it is essential to check this value.

The default value is 100000,But the optimal value should be 10000.

Hope this will give a fair idea who is going to utilize autoinvoice First time.

Related Posts

Posted in Finance, Oracle Receivable | 3 Comments »Email This Post Email This Post |

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today
3 Responses
  1. Arvinda Says:

    Hi Anand,

    Thx fr the gud job, when time permits, can u do a similar write-up on Lockbox too? Wud b great!

    Rgrds.

  2. anand Says:

    Thanks Arvinda,

    will surly share more information for lockbox as well as netting.

    keep reading ..
    -anand

  3. Alex Reyderman Says:

    Hello Anand,

    Thank you for the guidelines – short and to the point!
    One other thing I wanted to add is the use of indexes. It’s recommended that you define your interface_line_attribute1….? non-unique indexes for all context values that you have defined. This needs to be done on interface tables as well as corresponding base tables. You may also want to defined indexes for link_to and reference_to DFF.

    Thanks,

    Alex

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.