Re: Auto Invoice Question
- From: senigma13 <senigma13@xxxxxxxxx>
- To: ora-apps-dba@xxxxxxxxxxxxx
- Date: Tue, 16 Jun 2009 13:54:33 -0500
Joe ...you wish to read up the Metalink note 733835.1
Please establsih Goruping Rules in Oracle Receivables before you do your
AutoInvoice.
Please reference the following. You should groups you rinvoices as per your
need. Please check the below: Why is AutoInvoice splitting one order into
two invoices?
*A:
*AutoInvoice uses grouping rules to group invoices, credit memos and debit
memos. Grouping rules contain various transaction attributes (columns in
RA_INTERFACE_LINES_ALL table) that must be identical for the same
transaction.
There are 2 kinds of attributes: mandatory and optional. You can only add or
drop optional attributes. Please see the User's Guide for a listing of all
columns included in the mandatory attributes and all the columns that can be
added as optional attributes.
Check the grouping rule that you are using. You may have defined an optional
attribute that is different for two lines of the same invoice, and is,
therefore, causing a second invoice to be generated. Check both optional and
mandatory attributes of the two lines.
If AutoInvoice is generating one invoice for multiple orders, then you may
not have defined sales order as an optional attribute.
The Grouping Rule that is used by AutoInvoice is attached in your Batch
source :
Navigation: Setup -> Transactions -> Sources -> AutoInvoice tab
Grouping Rule can be checked at:
Navigation: Setup -> Transactions -> AutoInvoice -> Grouping Rule
References:
-- Note
98772.1<https://metalink2.oracle.com/metalink/plsql/showdoc?db=NOT&id=98772.1&blackframe=1>:
How AutoInvoice grouping works
-- Oracle Receivables User Guide, Release 12; Chapter 2, Section: Using
Grouping Rules to Create Transactions
Hope this helps.
Also please try and read up more information in the User's Guid as suggested
above
regards
--
Swarna K Duttagupta
Cell#: 2819245273
e-mail:senigma13@xxxxxxxxx <e-mail%3Asenigma13@xxxxxxxxx>
*****************************************************************************
On 6/16/09, Sweetser, Joe <JSweetser@xxxxxxxx> wrote:
> Forgive my ignorance as I know next to nothing about accounting. My
> situation is this: we have a process where we use Auto Invoice (along
> with other programs) to import external data into our 11.5.9 (I know, I
> know!) E-Biz environment. Some of this data is what they call bulk
> payments - multiple (somewhat related, somewhat unrelated) payments on a
> single invoice for a single vendor. The first time this type of invoice
> comes through it processes correctly on the Financials side. If another
> one comes through from the same vendor with the same invoice, the record
> is rejected due to duplicate invoice number.
>
> It seems to me the way to handle this situation is with line
> items/numbers but I do not see a place to store that information in the
> ap_invoices_interface table. Is there where a flexfield makes sense?
> In other words, use a descriptive flexfield to store each individual
> line number on the invoice. And, if that's the case, is there a way to
> make the Auto Invoice aware of that flexfield? I am not looking for a
> technical answer here, just if I am on the right path to solving this
> issue.
>
> Any/all comments/suggestions/stock tips welcome.
>
> Thanks in advance,
> -joe
>
>
>
Other related posts:
