Академический Документы
Профессиональный Документы
Культура Документы
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
What is the suggested setting for the 'Log file message level'?
A: For day-to-day business needs and to improve performance, set this to 0. If AutoInvoice errors out, set the message level to 3 to get detail messages in the log to help debug the problem. Message Level 0 gives the following entries in the log file: Product Version Program Name AutoInvoice Start Time AutoInvoice Concurrent Request Arguments Error and Warning Messages AutoInvoice End Time AutoInvoice Logical Steps Message Level 1 gives you all of the above entries plus: Time- Stamped function labels Message Level 2 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 gives you all of the above entries plus: Method IV SQL Array Values
If the errors are regarding AutoAccounting, message level can be set to 10 or above to get more detailed AutoAccounting messages in the log.
How can a credit memo (from legacy) be applied against an invoice using AutoInvoice?
A: To link a credit memo to an invoice there are 2 options: i) Populate REFERENCE_LINE_ID on RA_INTERFACE_LINES_ALL with the CUSTOMER_TRX_LINE_ID of the invoice. OR ii) Populate REFERENCE_LINE_ATTRIBUTE1 to 15 with the INTERFACE_LINE_ATTRIBUTE1 to 15 of the invoice. You also need to populate REFERENCE_LINE_CONTEXT with INTERFACE_LINE_CONTEXT of the invoice. INTERFACE_LINE_CONTEXT and INTERFACE_LINE_ATTRIBUTE1 to 15 are stored in RA_CUSTOMER_TRX_LINES_ALL. To create an on-account credit (i.e. not linked to an invoice) do not populate REFERENCE_LINE_ID, REFERENCE_LINE_ATTRIBUTES or REFERENCE_LINE_CONTEXT.
you cannot update it manually. Activity is defined as cash applied, credit memo applied, adjustment, posting to GL and, printing.
Once the transactions have been imported successfully into AR using AutoInvoice, how can they be purged from the interface tables?
A: If the system option 'Purge Interface Tables' is set to Yes, data that has been validated and successfully imported in AR will be purged automatically. If the purge option is set to No, you can submit the AutoInvoice Purge Program from the Run AutoInvoice form to purge the interface tables. This program will only purge rows that have been processed successfully. Navigation to check the 'Purge Interface Tables' option: - Menu: Setup>System>System Options - Alternate region 'Trans and customers' - 'Purge Interface Tables' checkbox Navigation to submit the AutoInvoice purge program: - Menu: Interface>AutoInvoice - Request name: AutoInvoice Purge Program
AutoInvoice. This window is read-only, but you can drill down to view errors in more detail, and modify data in these windows.
If the Derive Date box is not checked, AutoInvoice uses the date entered in the Submit Request window.
AutoInvoice is taking too long to run. How can I improve its performance?
A: Although there are many reasons which can contribute towards poor AutoInvoice performance, the most common ones are as follows: a) Indexes have not been defined for the Line Transaction Flexfield on RA_INTERFACE_LINES_ALL b) Custom indexes or triggers: If any custom indexes or triggers have been defined, drop them to see if performance improves. c) Run Gather Schema Statistics from the System Administrator responsibility d) Check the log file message level setting in the Accounts Receivable System Parameters. (Navigation: Setup -> System -> System Options -> Trans and customers tab) If it is set to 3, change it to a lower value. Message level 3 is used when AutoInvoice fails in order to generate a log file with the highest possible level of information.
The Import program (RAXTRX) does not get spawned when I run AutoInvoice. What could be the reason?
A: In this case the Master Program (RAXMTR) may complete without error but will not spawn the Import Program (RAXTRX). The log file for RAXMTR will show the 'No data Found' message. AutoInvoice executes a statement similar to the following to select records for importing: SELECT COUNT(*) FROM RA_INTERFACE_LINES_ALL WHERE NVL(INTERFACE_STATUS, '~') != 'P' AND (REQUEST_ID IS NULL) AND BATCH_SOURCE_NAME = &batch_source_name AND LINK_TO_LINE_ATTRIBUTE1 IS NULL AND LINK_TO_LINE_ATTRIBUTE2 IS NULL . . AND LINK_TO_LINE_ATTRIBUTE15 IS NULL
Please ensure: i) There are records present in the interface table RA_INTERFACE_LINES_ALL to be imported. ii) The column INTERFACE_STATUS and REQUEST_ID must be null
How do you default the batch source on the AutoInvoice submission screen?
A: Go to Concurrent -> Program -> Define Query for Short Name RAXMTR Click on Parameters Go to Batch Source ID Change the default type to Constant Change the Default value to the NAME (not id) of the value you want "Order Entry" (it is case sensitive). Save.
What is the difference between the ATTRIBUTE_CATEGORY and the HEADER ATTRIBUTE_CATEGORY columns in the RA_INTERFACE_LINES_ALL table.?
A: They are for 2 different descriptive flexfields. RA_INTERFACE_LINES_ALL.ATTRIBUTE_CATEGORY and ATTRIBUTE1-15 are used to
store values for the descriptive flexfield, 'Invoice Line Information', which appears at the invoice line level. The value in these columns will be transferred to RA_CUSTOMER_TRX_LINES_ALL.ATTRIBUTE_CATEGORY and ATTRIBUTE115 if the transaction passes validation. RA_INTERFACE_LINES_ALL.HEADER_ATTRIBUTE_CATEGORY and HEADER_ATTRIBUTE1-15 are used to store values for the descriptive flexfield, 'Invoice Information', which appears at the invoice level. The value in these columns will be transferred to RA_CUSTOMER_TRX_ALL.ATTRIBUTE_CATEGORY and ATTRIBUTE1-15 if the transaction passes validation. Since they are descriptive flexfields, you can set them up to store any value.
For Adjustments the table is AR_ADJUSTMENTS Note: You must define a category for every transaction type, payment method, and receivables activity that you have defined. The categories are based on table names. From Release 11i onwards for any new defined Transaction Type or Payment Method, the Document Category is automatically generated with the correct code matching the name. For Types defined on prior releases those do not exist and you need to do this manually. c. Assign the Sequences to the categories Navigation: Application -> Document -> Assign The category you created will be in the list of values as well as the sequence that you defined. iv) Set the profile options in System Administrator: Navigation: Profile -> System Check site and enter Application Oracle Receivables Query the profile Sequential Numbering This should be set to Partially Used or Always Used depending on your setup. Note: Depending on your business requirements you can also choose to set this profile option at responsibility level.) v) Set the "Document Number Generation Level" in Receivables Responsibility Navigation: Setup -> System -> System Options -> Trans and Customers tab Set the option "Document Number Generation Level" to either 'when completed' or 'when saved' that will generate the document sequence for the transaction either when you complete the transaction or save the same respectively.
2) The Tax falls in the jurisdiction defined for the tax code 3) The tax has a default jurisdiction, default rate and default status defined. 4) There are no violation of the rules defined 5) The tax gets calculated when you create a manual invoice.
FREQUENTLY ENCOUNTERED ERRORS: 1. Please Correct Revenue (or Receivable or Freight or Tax) Account Assignment
A: AutoAccounting is used to determine the accounts when the distribution table is not populated. When AutoInvoice rejects a line with this error, it generally prints the account with the missing segment(s). Menu: Setup>Transactions>AutoAccounting Query the account mentioned in the above error and note the setup for that missing segment. If it is based on: i) Transaction Type - Menu: Setup>Transaction>Transaction Types, and verify that all accounts are populated. ii) Salesperson - Menu: Setup>Transactions>Salespersons, and verify that all accounts are populated. iii) Standard Lines - For an Inventory Item Navigate to Menu: Setup>Transactions>Items>Inventory items, and verify that the 'Sales Account' is populated in the 'Invoicing' alternate region. For a Memo Line, Navigate to Setup =>Transactions =>Memo Lines, and make sure that 'Revenue Account' is populated. iv) Taxes Go to Tax Managers Responsibility Go to Taxes and query for your tax. Here go to Tax Accounts and verify all accounts are populated. Additionally the following can be checked: Setup of Cross Validation Rules. Run Cross validation Listing Report in GL to identify the cross validation rule stopping the import of this line.
4. a) Invalid Warehouse ID (WAREHOUSE_ID) b) Unable to derive a gl date for your transaction. Please ensure that your transaction is in a gl period which you have defined
A: When you get both these errors at the same time, please check whether your gl period is open for the date seen in the columns GL_DATE, SHIP_DATE_ACTUAL and SALES_ORDER_DATE in the table RA_INTERFACE_LINES_ALL
Navigation: Setup-->Print-->Remit-to Addresses Set up the default value for the remit to address. i) Go to Setup->Print->Remit-To Addresses. ii) Query up the address that will be the default address iii) Go to the "Receipts From" section of the form. iv) Put the cursor in the Country field and click on the LOV. v) Select the value "Default value" vi) Put cursor in the State field and click on LOV. vii) Select the value "Default value" viii) Save
8. a) Invalid bill to customer id, name ORIG_SYSTEM_BILL_CUSTOMER_ID b) bill to address id must exist in Oracle Receivables and must be assigned to the bill to customer ORIG_SYSTEM_BILL_ADDRESS_ID
A: This can be done by querying up the customer on the customer standard form i) Navigation: Customers > Standard ii) Query up the customer iii) Click on the address in the alternate region iv) Place cursor on the correct address v) Click on the open button, will take you to the business purpose screen vi) Make sure that there is a usage of bill to already set vii) Make sure that at least one of the bill to's is active If this is setup, then please check that the value in the interface table RA_INTERFACE_LINES_ALL for columns ORIG_SYSTEM_BILL_CUSTOMER_ID and ORIG_SYSTEM_BILL_ADDRESS_ID has a value that is seen in columns CUST_ACCT_SITE_ID and CUST_ACCOUNT_ID in the table HZ_CUST_ACCT_SITES_ALL.
9. Invoice lines with the same invoice number have been separated by the grouping process, causing duplicate invoice numbers.
A: Here, AutoInvoice is trying to separate your lines into different invoices due to grouping rule settings. For further details, Please refer to the 3rd question of this FAQ. Why is AutoInvoice splitting one order into two invoices?