2ysR015 Document 1080985.1 Troubleshooting AutoAccounting in AutoInvoice (Doc ID 1080995.1) In this Document Purpose. ‘Troubleshooting Steps 1, Troubleshooting AutoAccounting related errors encountered during Import a. Error: Not all AutoAccounting types are defined b, Error: Please complete the offset account assignments Error: Please complete your tax accounting flexfield Error: Please correct the receivable account assignment Error: Please correct the revenue account assianment Error: Please correct the freight account assignment 1) Review Seament Sources a) Seaments Source = Salesreps b) Seament Source = Standard Lines ) Seament Source = Taxes d) Segment Source = Transaction Types e) Segment Source = Sites 2) Validate the Shipping Inventory Organization You are providing in RA INTERFACE DISTRIBUTIONS ALL 4) Check the profile option: AR: Use Invoice Accounting for Credit Memos 5) Check if the GL account exists and is active 6) Verify Accounting Flexfield setting for Enabled and Allow Dynamic Inserts 2) Verify whether the GL account does not violate any cross-validation rules of the seaments, 2, Troubleshooting Unexpected Behavior re, AutoAccounting a, AutoAccounting for invoices from OM is failing if source = Standard Line (Inventory Item| b, Default Value Not Working As Expected . AutoAccounting overrides distributions from RA INTERFACE DISTRIBUTIONS ALL d, Impact of System Parameter: Item Validation Organization (previously Profile Option: OE: Item Validation Oraanization) ce, Impact of RA INTERFACE LINES.OVERRIDE AUTO ACCOUNTING FLAG £, Impact of Cross Validation Rules 1g. Unexpected GL accounts derived for Revenue / Receivables when AutoAccounting is based on Salesreps h, Wrong Revenue Gl distributions when AutoAccounting is based on Salesreps 3. Troubleshooting issues in Imported Transactions in the Transaction Workbench 2. Warning: Rerun AutoAccounting when maintaining Autolnvoice sourced transactions Still have Questions? References Oracle Receivables - Version 11.5.10.0 and later Information in this document applies to any platform. tty Tham_788i¢=1080096.1 hhip/iuppart oracle. comlepmesifacesiDocumentDisply? adit 4312ysR015 Document 1080985.1 Executable: RAXMTR - Autolnvoice Master Program Executable:RAXTRX - Autolnvoice Import Program Form:RAXSUAGL.FMB - Define Automatic Accounting Oracle Receivables (AR): AutoInvoice Information Center > Troubleshooting AutoInvaice for Oracle Receivables Release 11,5 Through 12 > Note 1080995.1 This note was created to facilitate troubleshooting issues regarding AutoAccounting in AutoInvoice. ‘AutoAccounting is a powerful, flexible, and time saving feature that automatically defaults your general ledger ‘Accounting Flexfields during data entry. You can set up AutoAccounting to create Accounting Flexfields that meet your business needs. In Receivables, AutoAccounting is enabled for the following Accounts: ‘Autolnvoice Clearing Bills Receivable Factored Bills Receivable Freight Receivable Remitted Bills Receivable Revenue Tax Unbilled Receivable Unearned Revenue Unpaid Bills Receivable ‘These are discussed in detail in Note 1069052,1, Setting Up AutoAccounting Rules In Receivables. TIP: Check out Note 1904785.1 AutoAccounting Analyzer, a dynamic way to help you identify and resolve AutoAccounting issues. 1. Troubleshooting AutoAccounting related errors encountered during Import a. Error: Not all AutoAccounting types are defined Please review Note 1344503.1, Autolnvoice Error: Not all AutoAccounting types are defined has been successfully replaced, for information on how to troubleshoot this error. : Please complete the offset account assignments Please complete your tax accounting flexfield Please correct the receivable account assignment Please correct the revenue account assignment : Please correct the freight account assignment For specific troubleshooting steps to address these errors, please review the following: 1 hhipe/ieuppart oracle. comlepmesifacesiDocumentDigply’? adc heck out Note 1904785,1 AutoAccounting Analyzer, a dynamic way to help you identify and dgtty7ham_78aid=1080095.12ysR015 Document 1080985.1 resolve AutoAccounting issues. 1) Please complete the offset account assignments (See Note 4368311) 2) Please complete your tax accounting flexfield (See Note 1087263.1) 3) Please correct the receivable account assignment (See Note 1088218.1) 4) Please correct the revenue account assignment (See Note 1088251.1) 5) Please correct the freight account assignment Step 1: If you are getting the error in AutoInvoice, try creating a manual transaction and use the same GL account segments. As you enter each GL account segment in the transaction form, if validation logic fails, the form will raise an error. This will help you in identifying which segments have issues and will assist you in resolving the problem. Step 2: For any of the above errors, the error message might display the Account that is causing the error to be raised. Let's take the following as an example: Please correct the revenue account assignment (03-0000000--0000-00000: 000) ‘A lose look at the accounting segments shows the 3rd segment is missing.You should check the setup of your AutoAccounting via: Respon: 7: Receivables Manager Navigation: Setup > Transactions > AutoAccounting ‘Then query up for Type = Revenue, and review the source for each of the segments. Step 3: Depending on what the source is for the failing segment, you can use the following steps to investigate/troubleshoot further. 1) Review Segment Sources a) Segments Source = Salesreps When a segment of the GL account has to be derived from the GL accounts associated with the Salesrep, then it is pertinent that you associate a Salesrep to your transactions. Check whether the following has been set-up correctly: + Transaction Source Responsibility: Receivables Manager Navigation: Setup > Transactions > Sources Query up the transaction source used for your AutoInvoice import batch, and navigate to the Autolnvoice Options tab, and ensure that the checkbox for Allow Salescredit is checked. hiip:support oracle. com/epmesifacesiDocumertDisplay? ad ct-stto=1dptlyTham_78Aid=1080095.12e015 Document 1080985.1 Cperatng Unt [Vision Operations Loge Entity | Name [TPEATOHSDURCE Type [impoited ich Sauron CGistorerinfirmaton, Accounting formation Invalid Line (BL Dae ina Closed Pariod ‘Grouping Rule [TIP GROUPING RULE crete Cesang 7 Allow Sales Cea Next check the Sales Credit Validation tab, verify what you have setup for Salesperson, how you set it up here impacts what Autolnvoice will expect to see in the RA_INTERFACE_LINES_ALL table (discussed below) hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.12e015 Document 1080985.1 eee Opeatng Unt (ines Options es vane EERTSOIRGE te (led) Customer rfomation Accounting hiraion _OtesIrnetun (Sas Ora Vaal] Sdeqoron Clinier ‘Gales Credit Type © Value oD Sales Credit Amount © Percent + System Options Responsibility: Receivables Manager Navigation: Setup > System > System Options Navigate to the Miscellaneous tab and check if the Require Salesperson checkbox is checked. susan ease iene Perret neces Vases comme IO Ratatat Cant HT Chapt Dae (BRE Sarcesteiey Ssb8R@ eiceontuesa Primal a hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.12ysR015 Document 1080985.1 The combination of the above settings determines the behavior re, Salescredits data in AutoInvoice. Note: Regardless of the combination of settings you define below, if you pass data in RA_INTERFACE_SALESCREDITS. ALL, then AutoInvoice will validate that the data you provided is valid Allow: Require Requirement of Salescredit Salesperson | Salescredit field (in System information an Options) Transaction Source) Checked ‘Checked Mandatory Checked Not Checked | Optional Not Checked ‘Checked Mandatory Not Checked Not Checked | Any data entered will be ignored + GL account associated to Salesrep Responsibility: CRM Resource manager Navigation: Maintain Resources > Resources Ensure that Freight, Receivables and Revenue Accounts associated to the Salesrep have been setup completely. hiip:support oracle. com/epmesifacesiDocumertDisplay? ad ct-stto=1dptlyTham_78Aid=1080095.12e015 Document 1080985.1 ese at eps Enos aan fin in ane Ae Retlie) | ae HBAS) Do [| Saran i se ah tn tr nal Utne “esi re (er) a a er Se ea IR Cpr Skpeotinte —_[Rowntione Teal emp i= fpteanoarean Tins Ting Fe ‘+ Data in RA_INTERFACE_SALESCREDITS_ALL When you have defined AutoAccounting such that some GL account segments, are sourced from Salesreps, make sure that you populate the table RA_INTERFACE_SALESCREDITS for each line in RA_INTERFACE_LINES_ALL so that the proper accounting can be derived, and ensure that the values in INTERFACE_LINE_CONTEXT + INTERFACE_LINE_ATTRIBUTE1-15 match up. This is required when you source segments from Salesreps and is necessary even if your system option Require Salesreps is set to No. + Data in RA_INTERFACE_LINES_ALL If your source is Salesreps, and your Transaction Source setup for Salesperson is: ‘+ Number, then you should be populating RA_INTERFACE_LINES_ALLSALESREP_NUMBER. + Id, then you should be populating RA_INTERFACE_LINES_ALLSALESREP_ID Note: The fields to populate are SALESREP_NUMBER or ‘SALESREP_ID and not PRIMARY_SALESREP_NUMBER or PRIMARY_SALESREP_ID hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 Te282015 Document 105095.4 + Script to find incomplete Salesrep setup for AutoAccounting ‘The following script will pick up all Salesreps that do not have all the GL accounts setup, this could assist you in proactively setting these up to avoid issues in Autolnvoice. SELECT NAME, PERSON, NV (O_CHAR (SL_! 'NULL REV") GL_ID_REV, NVE (TO_CHAR ( HNULL REC') GL_ID_REC, NVz(70_CEAR(GL_ID_PREIGHT), ‘NULL FREIGHT") GL_ID_PREIGHT ACTIVE, sysdate) <= sysdate) AND TIVE, sysdate) >= sysdate)) -AULTS_ALL ay -AULT_SEGMEN’ FROM WHERE s.GL_DEFAULT_1D = a.GL_DE! AND s.CONSTANT is null + Projects Users: Set up a Credit Receiver on a project so that the RA_INTERFACE_SALESCREDITS_ALL table is populated by the ‘Interface Invoices to Receivables’ process. This may require that the 'No Sales Credit’ salesperson be setup as an employee. Setting this up wil allow you to bypass the mandatory salesrep validation when none exists. To complete this setup, go into the Receivables responsibility: NAV Setup/Transactions/Sources Query your batch source, Go to tab Autolnvoice options, Mark allow salescredit. b) Segment Source = Standard Lines When your GL account segments are source from Standard lines, itis pertinent to associate either an Inventory Item or a Memo line to your transaction, so that ‘AutoAccounting can derive the GL account segments, Check whether the following have been setup correctly: + Transaction Source Responsibility: Receivables Manager Navigation: Setup > Transactions > Sources Query up the transaction source used for your AutoInvoice import batch, and navigate to the Other Information tab, how you set up Memo Line Rule and/or Inventory Item here impacts what AutoInvoice will expect to see in RA_INTERFACE_LINES ALL table (discussed below). hnipeieuppartorecle.comiepmesifaces;DocumentDisply? adc2e015 Document 1080985.1 ae Opetng Unt [Visor Greats Lag nity Name [IPBATCHSOURCE ———) Tye [Inst Customer rceation Accoeting hcsion [OMaAimraon Sales Cred Vaidation ©) Transacion Type CVaue 10 Nemo Reason Yale 10 Soreement (Vas 10 None Nemo Line Rule Yas 10 Saks Terry Seament O10 None Inveron tem © Seamer 1 None Uniti Neasue Vale FOBPoint Code == None Freight Caner © Code None Reed Document Humber 10 © None + GL account associated to Inventory Ttem or Memo Line For an Inventory Item Responsibility: Receivables Manager Navigation: Setup > Transactions > Items > Define items Query the item and in the Invoicing Tab check the value in the Sales Account field. hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 ast2ysR015 Document 1080985.1 (homme ft fee Di Ae a tite obs cepa SamDoaebehn a Unie Winns Oem BRL Pete Se Hebe Sa sai mcg cape Steet BEE Foe For a Memo Line Responsibility: Receivables Manager Navigati Setup > Transactions > Memo Lines Make sure that the Revenue Account is populated, nee (perting Unt Namo Coser Tye Tax Glassifcation Tax Product Caegory Unt ListPrice nt hea fon Dprations| noo Revenue Accout Sone mo coun acelin Iroiig Bula Accaurtng Rule Acive Datos (Operations to DsparrientAcoauntsResehisleo Sut Account 0 mice Worth, 1 Year prwow2 F C1 hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 0312ysR015 Document 1080985.1 + Data in RA_INTERFACE_LINES_ALL + If your source is Memo Line, and your Transaction Source setup for Memo Line Rule is: @ Value, then you should be populating RA_INTERFACE_LINES_ALL.MEMO_LINE_NAME © Td, then you should be populating RA_INTERFACE_LINES_ALL.MEMO_LINE_ID + if your source is an Inventory Ttem, and your Transaction Source setup for Inventory Item is: © Segment, then you should be populating RA_INTERFACE_LINES_ALL.MTL_SYSTEM_ITEMS_SEG1-20 (as appropriate) © Id, then you should be populating RA_INTERFACE_LINES_ALL.INVENTORY_ITEM_ID + Script to find incomplete Memo Line or Inventory Item setup for AutoAccounting ‘The following script will pick up Memo Lines that do not have all the Revenue account setup, this could assist you in proactively setting these up to avoid issues in Autolnvoice. "T T.NAME, B.MEMO_LINE NVL(70_CEAR(b.GL_ID_REV), 'NULL REV") GL_ID_REV FROM AR MEMO LINES ALL TL T, AR MEMO LINES ALLE B WHERE b.MENO_LINE_ID = t.MEMO_L AND ((nv1(b.END_DATE, sysd (nvi (b.START_DATE, sysdate) <=sysdate)) AND ».Gh_ID_REV TS NUL, AND EXISTS (SELECT 'x* RA_ACCOUNT_DEFAULT_SEGMENTS = WHERE 9.GL_DEFAUET_ID ~ @.GL_DEFAULT_I AND 8.CONSTANT 18 null AND ABLE_NAME = ‘RA_STD_TRX_LINES'); ‘The following script will pick up Inventory Items from organizations involved in Order Management that do not have the Sales Account setup, this could assist you in proactively setting these up to avoid issues in Autolnvoice. "T ORGANIZATION_1D, DESCRIPTION, TNVENTORY_1” NVz(70_CEAR(SALES_ACCOUNT) , 1D, NULL SALES ACCOUNT") ROY ACTIVE, sysdate) IVE, sysdate) < yedate) AND yysdate}} AND ORGANIZATION_1D IN (SELECT MASTER_ORGANTZATION_ID FROM OF_SYSTRM_PARAMETERS_ALL) AND SALES ACCOUNT IS NULL AND EXISTS (SELECT x" FROM RA, RA 5 WERE s.GL_DEFAULT_ID = 4.GL_DEFAULT_ID s.CONSTANT is null TD_TRK_LINES") tty7ham_7eaid=1080095.1 ast hhipes/iuppart oracle. comlepmesifacesiDocumentDigply’? adits2e015 Document 1080985.1 ORDER BY 1; c) Segment Source = Taxes Error Message: Please complete your tax accounting flexfield When a segment of the GL account has to be derived from the GL accounts associated to ‘Tax, Check that the following has been setup correctly. In Release 12, sourcing from Taxes can come from the following levels: + Tax + Tax Jurisdiction = Tax Rate Please review Note 885225.1, Setting Up Tax Accounting for R12 E-Business Tax (EBTax) for an in-depth discussion of how to setup Tax as a source for AutoAccounting. In Release 11.5, = Tax Code Responsibility: Receivables Manager Navigation: Setup > Tax > Codes Query for the Tax Code being used and verify that in the More tab, under the column account, you have defined a GL account. cme la Te its vat ase cole [to nae Desciion Ton Type Tox oie cst “lst “cst__| eromaxroamns(cst “Exempt | 0.0m 270400 gemt ““Guops | tomaamamrafcnoest “Gast | ctomasmatnfonesr in (uo 250 om i “Fakta | comma. Ta “anne est | 0100 2520.00 anne et “escort ato ao i esco4 Qs 2 lL ~ Account Desetipions nd Use Tax P-No Sub Account He Product Ta (acecronig hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 a82e015 Document 1080985.1 + Location Based Tax First you need to determine you Location Flexfield Structure ity: Receivables Manager Navigation: Setup > System > System Options Navigate to the Tax tab and check the value in Location Flexfield Structure Coenen ‘Adress Vallation Insoice Printing Tov Registation Nunbor Tex Vendor Views Sales Tau Goo Qvonide Ring Opts $i Calculation Level Routing Rule Reporting Currency Frecision Min Accourtble Unit 7 lay Ore Then check which of the segments of your Sales Tax Location Flexfield is associated with the Tax Account. Responsibility: Receivables Manager Navigation: Setup > Financials > Flexfields > Key > Segments Query on Flexfield Title Sales Tax Location Flexfield Find the structure associated to your System Options, in our example (see previous screenshot): State.County.City Click on Segments While positioned on the first record State, click on Flexfield Qualifiers Scroll tll you find the record for name Tax Account, if the Enabled checkbox is checked then this is the segment associated to the Tax Account, otherwise, you may need to do the same steps for the other Flexfield Segments (i.e, County, City) till you identify the segment associated with the Tax Account. hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 rast2ysR015 Document 1080995.1 ‘Aileen Receivables Fevieé Tite Sales Tax Location Flexield | ~ Suuetures ode Tile Desesatin Va Name STATE.CITY St ‘State and ity fields hecome |AR_LOC_FLEX_STATE_CIT = [stare counry.crry state couny.cry Column Value Sat LOCATION_1D_SEGME Wado Ppl BE [site State Displayed Nene Descgtion Enalod || ew ‘oy ce aco {County | Goun ~Coumy tomatic Exemption: Automatic Exemptions wil be created at this evel nthe lace ¥ | Pantal Code [Piotr [st =f = = [ax caone a Aas a] Finally, verify that the Tax Account is setup for this Segment Responsibility: Receivables Manager Navigation: Setup > Tax > Locations In the Find field enter the segment for which Tax Account is enabled, in our example State, click on Find Records for various States will populate, ensure that the Tax Account field is populated with a GL account hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 watDocument 1080985.1 11 000-2520 2101.00 [| 11-000-2520-2102-000 | [Calitoria |ota0n 2a90-73.000 D ‘Do not use jot amo 251 00m Do nat we jot 000 250 000.000 1g ToxAcetDese [Operations Ne Department State Sales and Use Tax PAlabamaN Product ae 4 “Ios ser fan 9999 Sees 98 Tex Accounting d) Segment Source = Transaction Types hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 When a segment of the GL account has to be derived from the GL accounts associated with the Transaction Type, then it is pertinent that you associate the correct Transaction Type to your transactions, and that the GL accounts for the transaction type are defined. Check whether the following has been set-up correctly: ‘+ Transaction Sources Responsibility: Receivables Manager Navigation: Setup > Transactions > Sources Query up the transaction source used for your Autolnvoice import batch, and navigate to the Other Information tab, and your setup for Transaction Type. How you have it setup here impacts what AutoInvoice will expect to see in RA_INTERFACE_LINES_ALL (discussed below) 16912e015 Document 1080985.1 operating Un [Vision Gporaions Lega Entty id Name [TPBATCHSOURCE Tyo [inpatted +] Customer ifrmation Accounting Information Sa adation ‘ranesctan Type Value a Mare Reason’ © Value Agron Value © None Mame Line Rule Vas 1D Sales Tertory © Sogmeni 10 None Iovntery tn © Saget Nora Unie cf Meneure Van 10 FO Point © Code None Freight Camr © Code None Reletes Document Kumber 10 ene + Transaction Type Ensure that you have populated the GL accounts associated to the ‘= Data in RA_LINTERFACE_LINES_ALL If your Transaction Source setup for Transaction Type is: * Value, then you should be populating RA_INTERFACE_LINES_ALL.CUST_TRX_TYPE_NAME * Id, then you should be populating RA_INTERFACE_LINES_ALL.CUST_TRX_TYPE_ID ‘+ Script to find incomplete Transaction type setup for AutoAccounting The following script will pick up transaction types that do not have all the GL hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 19312e015 Document 1080985.1 accounts setup. If you have some AutoAccounting defined to source from ‘Transaction Types, then the incomplete GL account setup could cause issues - this script could assist you in proactively setting these up to avoid issues in AutoInvoice SELECT ORG_ID, NAME, CUST_TRX_TYPE_ID, TYPE, STATUS, POST_T0_GL, ACCOUNTING _AFPZCT_PLAG, NVL(70_CHAR(GL_ID_REC), "NULL REC') gi_id_rec, DECODE (type, "BR", "NOT APPLICABLE", NVL(TO_CHAR(GL_ID_REV), "NULL REV')) gi Ad_xev, DECODE (type, "BR", ‘NOL APPLICABLE", NVL(TO_CHAR(GL_ID_FREIGHT), "NULL FREIGHT") gl_id freight, DECODE (type, "BR", 'NOT APPLICABLE", NVL(TO_CHAR(GL_ID_CLEARING), *NULL CLEARING')) gl_Ad Clearing, DECODE (type, "BR", 'NOT APPLICABLE", NVE(TO_CHAR(GL_ID_TAX), ‘NULL TAK") gid tax, DECODE (type, "BR", 'NOT APPLICABLE", NVL(T0_CHAR(GL_ID_UNBILLED), ‘NULL UNBILL")) gl_id_unbilled, DECODE (type, "BR", 'NOT APPLICABLE", NVL(70_CHAR(GL_ID_UNEARNED), ‘NULL UNEARN")) gl_id_unearned, DECODE (type, "BR" ,NVL(TO_CHAR (GL._TD_UNPATD_REC) , *NULL UNPATDREC'), "NOT APPLICABLE") gi_Ad_unpaidrec, DECODE (type, "BR" , NVL(TO_CHAR (GL._ID_REMEPTANCE) 'NULL REMITTANCE"), "NOT APPLICABLE") gi_Ad_remittance, DECODE (type, "BR' ,NVL(TO_CHAR(GL_ID_FACTOR), ‘NULL FACTOR"), 'NOT APPLICABLE") gl_id_factor, ‘START_DATE, END_DATE FROM RA_CUST_TRX_TYPES_ALL WHERE ((WVL(START_DATE, sysdate) <~ sysdate) AND (NVL(END_DATE, sysdate) >~ sysdate)) AND -NVL(STATUS,'A') = tA AND ((TYBE = 'BR' AND (Gi_XD_REC 18 NULL OR CL_ID_UNPAID_REC IS NULL OR CL_ID_REMITTANCE I$ NULL OR Gu_ID_FACTOR 1S NULL)) oR (2veE © BR! AND (Gi_ID_REC TS NULL OR GL_ID_REV IS NULL OR Gu_ID FREIGHT TS NULL OR GL ID CLEARING TS NULL OR Gu_ID TAX IS NULL OR GID UNBILLED TS NULL OR Gh_ID_UNEARNED 13 NULL))) AND EXISTS (SELECT tx" FROM RA_ACCOUNT_DEFAULTS_ALL a, RA_ACCOUNT_DEFAULT_SEGMENTS 3 WHERE 8.GL_DEFAULT_ID = @.GL_DEFAULT_1D AND 8.CONSTANT i8 null hips:support oracle. comlepmesifacesiDocumertDisplay? ad ci-stato=tdptlyham,_78Aid=1080805.1 wre2e015 Document 1080985.1 AND 8.7ABLE_NAME = 'RA_CUST_TRX_TYPES") ORDER BY 1+ e) Segment Source = Sites + Transaction Sources Responsibility: Receivables Manager Navigation: Setup > Transactions > Sources Query up the transaction source used for your AutoInvoice import batch, and navigate to the Customer Information tab, and check how you have setup Bill To Address and Bill To Customer, how you have it setup here impacts what ‘Autolnvoice will expect to see in RA_INTERFACE_LINES ALL (discussed below) ines perain Uni Vision Operions | Legal Ext Neme TIP BATCH SOURCE Type parted | Bich Souce Audie Opto (stoner mmalan| Accouting iermaten Sold Ta Customer Yalue BillTa Customer © Value Bil To Address © Vale Bil Ta Contact © Yale None Ship Te Customer “Vale 1D None Ship ToAdess Yau 910 © None Shinto Contact Vale 01D None Payment Method Rule “Yale 1D Customer Bank Account Vale 1D + Customer Site Ensure that you have populated the Accounts associated at the Bill To Site level hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 rast2e015 Document 1080985.1 cont tes tpt Tans OWT aa am axe 0) rotenone [EX Shuae a ‘ie tpt [aston nya cy A win et ts areaur Desai ao Paar ROK | raat Bee Cpas tangs orem | ‘rennet rm ra ey Seances nh (ete a ST eg Corts tig matress taut remedies pcs tat et Seeiemstiaasinieaniae Topsiom z + Check that the Site you are using is associated to the same Operating Unit (ORG_ID) as the transaction you are interfacing. 7 Receivables Manager Query up the customer record, drill down to the Account Level and then to the Site Level and ensure the Site is linked to the right operating Unit, (ear tp ce rt cnt a wnat s Cameutome — aewaeneef aewaenlenl + Data in RA_INTERFACE_LINES_ALL + If your Transaction Source setup for © Value, then you should be populating RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_CUSTOMER_REF © Id, then you should be populating RA_INTERFACE_LINES ALL ORIG_SYSTEM_BILL_CUSTOMER_ID + If your Transaction Source setup for Bill To Address © Value, then you should be populating RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_ADDRESS_REF hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 rat2e015 Document 1080985.1 © Id, then you should be populating RA_INTERFACE_LINES_ALL.ORIG_SYSTEM_BILL_ADDRESS_ID ‘+ Script to find incomplete Site setup for AutoAccounting The following script will pick up Customer Sites that do not have all the GL. accounts setup at the Bill To Site. You can limit the rows returned by filtering adding a condition on arty_name, or just checking for a particular GL account, or by processing in batches using a condition like: and rownum < 300 This could assist you in proactively setting these up to avoid issues in Autolnvoice. SELECT cust_acct -ACCOUNT_NUMBER custoner_nunber, substr (party. PARTY_NAME,1,30) customer_nane, substr (loc. ADDRESSI,1,30) address, site uses.CUST_ACCT SITE_ID address id, site uses.LOCATION, site uses.SITE USE ID, site uses. SITE_USE_CODE, nvl(Zo_char(site_uses.Gi_ID REC), ‘NULL REC") gi_id rec, decode (site_uses.SITE_USz_coze, ‘BILL T0",nvi(to char(site uses.GL ID REV), *NULL REV"), ‘DRAWBE" , "NOT APPLICABLE") gl_id rev, Gecode (site_uses.STTE_US®_coDE, ‘RTLE_TO", nv (to_char (site_uses.Gl_ID_PREIGHT), *NULL FREIGHT"), "DRAMEE' , "NOT APPLICABLE") gl_id_freight, Gecode(site_uses.SITS_use_coDe, *BILL_TO", pv (to_char (sit ‘NULL CLEARING"), uses.GL_ID_CLEARING) , ‘DRAWEE" , 'NOT APPLICABLE") gl id clearing, de (site_uses.SITS_US#_coDE, *BILL_TO", nvl(to_char(site_uses.Gb_ID_TAX), SNULL TAX"), ‘DRAWEE' , 'NOT APPLICABLE") gl_id_tax, \de(site_uses.STT=_US#_coze, ‘BILL_TO", avl(to_char(site_uses.GL_ID_UNBILLED), ‘NULL UNBILL'), ‘DRAWEE' , 'NOT APPLICABLE") gl_id unbill, decode (site_uses.SITE_USE_coDe, *BILL_T0", nvl (to_char (site_uses.Gl_ID_UNFARNED) , ‘NULL ONEARN'), ‘DRAWEE' , 'NOT APPLICARLE*) gl id unearn, decode (site_uses.SITE_US#_coDE, ‘BILL 70", ‘NOT APPLICABLE*, “DRAWEE', nv (to_char (site_uses.GL_ID_UNPATD_REC), *NULL UNPAID REC')) gl_id_unpaidrec, decode (site_uses.SITE_USE_CODE, hips:support oracle. comlepmesifacesiDocumertDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 20312e015 Document 1080985.1 *BILL_TO", "NOT APPLICABLE*, "DRAWER" nv (to_char (site_uses.Gh_ID_REMITTANCE) » *NULL REMITTANCE")) gl_id_remittance, decode (site_uses.SITE_USE_coDE, 'BILL_TO", "NOT APPLICABLE', ‘DRAWEE" hvl(to_char(site_uses.Gb_1D_£ACTOR) , ‘NULL FACTOR')) gl_id factor ROM HZ PARTIES PARTY, a PARTY SITES PARTY SITE, a_cUST ACCOUNTS ALL cusT_accT, 2_LOCATIONS Loc, Hz_CUST_ACCT_SITES_ALL ACCT_SITES, HZ_CUST_SITE_USES_ALL STTE_USES WEERE party site.LOCATION_ID = loc.LOCATTON_1D BND party.PARTY_ID = cust_acct.PARTY_ID AND cust_acet.cUST_ACCOUNT_ID = acot_sites.cUST_ACCOUNT_ID AND acot_sites.cUST_ACCT SITZ_ID = site _uses.CUST_ACCT_SITE_ID BND party_site.PARTY_SITZ_ID = acct_sites.PARTY_STTR_1D BND site_uses.STTE_USE_CODE in (‘BILL_T0" , ‘DRANEE") AND site uses.STATUS = ‘A’ BND ((site_uses.STTE_USE_CODE = 'BILI_T0" AND (site_uses.GL_ID_REC TS NULL OR site_uses.GL_ID_REV 8 NULL OR site_uses.GL_ID_FRETGHT T5 NULL OR site _uses.GL_ID_CLEARING I8 NULL OR size_uses.GL_ID_TAX IS NULL OR site_uses.GL_ID_UNBILLED IS NULL OR sive_uses.GL_ID_UNEARNED I NULLI} oR (site_uses.SITE_USE_CODE ~ 'DRAWES" AND (sive_uses.GL_ID_REC 18 NULL OR site_uses.GL_ID_UNPAID_REC IS NULL OR site_uses.GL_ID_REMITTANCE IS NULL OR site_uses.GL_ID_FACTOR IS NULL}}} AND EXISTS (SELECT 'x" FROM RA_ACCOUNT_DEFAULTS_ALL a, RA_ACCOUNT DEFAULT SEGMENTS = WEERE ¢.GL_DEFAULT_ID = a.GL_DEFAULT_ID AND s.CONSTANT is null AND §.TABLE_NAME = "RA STTE_USES"); 2) Validate the Shipping Inventory Organizat n If the Shipping and Selling organizations are different, with each belonging to a different Set of Books each set up with a different Chart of Accounts, you may get an error such as the following, even when your AutoAccounting setup is complete. Please complete your tax accounting flexfield or Please correct the revenue account assignment This issue is manifested because the Chart of Accounts for each set of books hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 20282015 Document 105095.4 has a different number of segments, for example: + Selling Organization GL accounts has 13 segments + Shipping Organization GL accounts has 7 segments Current functionality was not designed to handle this scenario, An enhancement request has been logged for this issue, via Bug 2432013. 3) You are providing data in RA_INTERFACE_DISTRIBUTIONS_ALL You are interfacing data into RA_INTERFACE_DISTRIBUTIONS ALL, and during Import, you are getting the errors such as: EXCEPTION: arp_auto_accounting.do_autoaccounting_internal() (ORA-20000: APP-15482: Please correct the receivable account assignnent Things to check: + If you want AutoAccounting to determine your general ledger accounts you must not enter values in RA_INTERFACE_DISTRIBUTIONS ALL. ‘+ If you want to bypass AutoAccounting, then you need to provide complete information in the distribution table for the ACCOUNT _CLASS distributions you intend to provide. + Ifyou are in a multi-org instance, ensure that you have included the ORG_ID value in the distributions you pass, and that the value is consistent across the interface tables. + Check that the INTERFACE_LINE CONTEXT + INTERFACE_LINE_ATTRIBUTE* values you provide in the RA_INTERFACE_DISTRIBUTIONS ALL table match the values in the corresponding rows in RA_INTERFACE_LINES ALL, so that Autolnvoice can match up the transaction to its proper distributions. 4) Check the profile option: AR: Use Invoice Accounting for Credit Memos. IF you are importing Credit Memos, and you encounter the error: Please correct the ... account assignment, verify whether you would lke the credit memo to use the same GL accounts of the Invoice itis crediting, If yes, then check your setting for the profile option: AR: Use Invoice Accounting for Credit Memos. If the setting is: + Yes, Receivables does not use AutoAccounting to create the default values for these accounts. Instead, credit entries are created using the GL accounts of the invoice or debit memo you are crediting. + No, Receivables will generate GL accounts for the credit memo based ‘on the AutoAccounting setup 5) Chec! if the GL account exists and is active Once all the segments of your GL account have been derived by AutoAccounting, check if it exists and is active. Responsibility: Receivables Manager Navigation: Setup > Financials > Accounting > GL accounts hiip:support oracle. com/epmesifacesiDocumertDisplay? ad ct-stto=1dptlyTham_78Aid=1080095.12e015 Document 1080985.1 Query for Account = 100-1324-0000-000. the GL account segments, for example: Query for 03- ‘The form will display whether the GL account exists, if it is enabled and active. Alternatively, if you want to check whether a particular code_combination_id (ccid) value refers to a valid and active GL account, you can run the following: select enabled_flag, start_date_active, end_date_active fzom Gh_CODE_COMBINATIONS where cade combination id = seeidy 6) Verify Accounting Flexfield setting for Enabled and Allow Dynamic Inserts Considering AutoAccounting will derive and build GL accounts on the demand, you should check whether you allow the Accounting Flexfield to do dynamic inserts. If your business process allows dynamic creation of new code combinations, set the checkbox to Yes. Responsibility: Receivables Manager Navigation: Setup > Financials > Flexfields > Key > Segments. + Query on Flexfield Title Accounting Flexfield + Locate the record for the Accounting Flexfield Structure you are using * check the Enabled and Allow Dynamic Inserts checkbox ‘este (Gna aig Freed te (secon Fra Siutues ie Tie Desigion YiexNore jlEHERDS lcaehwind cote coun ra ay ct OPA s0000NING ROR nawineFie ——_CPMASHRIO VEER pis ca Pee fi Opes Act LANG ACCENT Fr Acoig ex sn Pad cart lage Fetal Dette erate Somer Sparta [Dist] P cussaidate oyna Fez al Gus Y Alon Ojai sats hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 2a2e015 Document 1080985.1 If your business does not allow dynamic inserts, then you need to review why AutoAccounting attempted to generate a code combination that you have not yet set up. If you verify, that the new code combination is valid you need to create the code combination manually to avoid the error next time the same code combination is derived, Responsibility: Receivables Manager Navigation: Setup > Financials > Accounting > GL Accounts ‘Alo geting raed Aloo Posing Pramod fect Datas Account From pisces como Enperse ¥ prsiereooman (ose fromm 0 iwrsvomon Evperse #0 pceoreanomomn ° pss Ewes =| | pr psen ono Enperse 2 70 orswscocmom pr7esrocmon #0 pisosenomam (one toocotom prsspsz0 oma Evperse * ere —— core Daseion (reraton MI, Seate Manae-Pysial enor Als No Su Accom Prost 7) Verify whether the GL account does not segments. Responsibility: System Administrator Navigation: Application > Flexfield > Key > CrossValidation Query for Title = Accounting Flexfield Structure = Provide the Structure you are using Then review the rules and see if the GL Account you are using has segments which fall into the ranges excluded. 2. Troubleshooting Unexpected Behavior re. AutoAccounting a, AutoAccounting for invoices from OM is failing if source = Standard Line (Inventory Item) OM populates the RA_INTERFACE_LINES_ALL.WAREHOUSE_ID with the Shipping Organization Id. This information is used by AutoInvoice to get the accounting information for the inventory item depending from which warehouse it has been shipped. hips:support oracle. comlepmesifacesiDocumertDisplay? ad ci-stato=tdyttyham,_78Aid=1080895.1 2st2ysR015 Document 1080985.1 Check to see if the WAREHOUSE_ID value populated from OM is correct, Then verify the accounting is set for the Inventory item, for more details review Note 1069052.1, Setting Up AutoAccounting Rules In Receivables (2-5 Standard Lines) b. Default Value Not Working As Expected ‘Sometimes, you will not get errors in the GL accounts derived by AutoAccounting, but the segment value derived does not appear to come from the Sources you specificed. Check whether that particular segment was setup to use a default value. Responsibility: Receivables Manager Navigation: Setup > Financials > Flexfields > Key > Segments Query up Title Accounting Flexfield, locate the Code Structure associated to your ‘Accounting Flexfield, click on Segments, then pick any segment and click on Open. This will show you the details of that particular segment, and whether or not this segment has a default value. = oy Fseld gris Aepicaon Gear Fl ocr Ft Ete code Te ces er Nano Jorcesnons sovaul aie AeltngFi Vien Opts Acc ne dint Ente tere dev Porgt_——_ om thse ied Boreas censiny SEGUE __Owmtostnpay BB * vane amp) Deen (ryan Signed embod Column SEGMENT Nurnber 7 Displayed Fret Vaso ‘ue ar enpany Desens Cmrng eta ye [rst De aie Seouty Eales Rane Prams Cispay Sie 2 Lis orvaues (o Descepion Size 25 ‘Window Company concatenated Descipion Si 10 hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.1 2812ysR015 Document 1080985.1 In cases where AutoAccounting fails to derive a segment from the source you specified, it will go back to the Accounting Flexfield setup, and if that segment has a default value, that is what AutoAccounting will use. In the above screenshot, if AutoAccounting fails to find a value for the Company Segment from the sources you specified in the AutoAccounting setup, then it will use the value 01 for the first segment. ¢, AutoAccounting overrides distributions from RA_INTERFACE_DISTRIBUTIONS_ALL You have populated the RA_INTERFACE_DISTRIBUTIONS ALL and expect this to be the data used by AutoInvoice, but instead, AutoAccounting is kicking in and the distributions you interfaced is being ignored. ‘Also review the tips provided in the section You are providing data in RA_INTERFACE_DISTRIBUTIONS_ALL above. 4d. Impact of System Parameter: Item Validation Organization (previously Profile Opti OE: Item Validation Organization) This profile is obsolete in Release 11.5 and has been replaced by a System Parameter setting. Responsibility: Order Management Super User ion: Setup > System Parameters > Values Item Validation Organization Parameter Consider the following setup: + AutoAccounting setup picks up some segments from Standard Line + Your environment is setup with Master and Child inventory organizations + The same Inventory Item exists in both Master and Child organizations, but the Sales Account associated to the item is different for each organization Which GL account will AutoAccounting source segments from, will it use the Sales Account setup in the Master or the Child organization? ‘The Organization you provide in the System Parameter: Item Validation Organization determines from what organization the Inventory Item will be retrieved from. e. Impact of RA_INTERFACE_LINES.OVERRIDE_AUTO_ACCOUNTING_FLAG Setting this flag to Y will not cause Autolnvoice to override AutoAccounting. To better understand this flag, we need to explain a bit of history on why it was created. Oracle Receivables provides a feature Revenue Adjustment, through the Revenue Accounting form (Navigation: Control > Accounting > Revenue Accounting) or Revenue ‘Adjustment API. One of the uses of running Revenue Accounting is to modify the GL accounts derived by AutoAccounting. When this is done, itis typical that subsequent GL distributions created should use the new GL accounts. To better illustrate, let's take an example of an Invoice with Rules, recognizing revenue immediately, The original model distributions using GL accounts generated by AutoAccounting are: hiip:support oracle. com/epmesifacesiDocumertDisplay? ad ct-stto=1dptlyTham_78Aid=1080095.1 212ysR015 Document 1080995.1 Trane atl Lne Line Clase BL Account a -o-1210-co00-000 Founding Distribution ran 77 i overs orem i Uneared Rowe orem Let's change the GL. account for UNEARN Trane Detail Line Line Claes BL Account Receivable (-ou0- 210000-000 Rounding Distituion ov ran7a27 on00-000 i Revenue -oon4se4.9000-000 F (reamed Reone TT = ‘pg conn on eon 00 con 09.000 % ‘a0 co: ron con tap cnt ‘00 con ‘After running Revenue Recognition and querying this transaction in Revenue Accounting, it shows distributions were created using the new GL account: toa mmurt _% cece Accu forse 121100) 10008| Revenue (Overoasu4oums oxo eae a0 4.21100> 10000 Unesmned Revo co ssoburs- 070 oeaue-an0 1.21100 10000 Unesmned Reve Oaoojssaha-000 If run Revenue Accounting to Unschedule all of the Revenue, the distributions created use the new GL account as expected, and this is the behavior when OVERRIDE_AUTO_ACCOUNTING_FLAG = Y: au dora % nea Aecoure tere 121nm|1o00s|unesres Remrue ——_b-amssxloneo oxo Notes: 1, RA_INTERFACE_LINES_ALL.OVERRIDE_AUTO_ACCOUNTING_FLAG = does not cause AutoInvoice to override AutoAccounting at the time the instead it will use the GL accounts from the existing GL distributions. 2. In Release 12, for an invoice with rules, behavior is always as if transaction is created in Receivables. The value of this flag is migrated to RA_CUSTOMER_TRX_LINES_ALL.OVERRIDE_AUTO_ACCOUNTING FLAG and is referenced later on, when Revenue Accounting is done on this transaction, During Revenue Accounting, the code will check to see what the value is in RA_CUSTOMER_TRX_LINES_ALL.OVERRIDE_AUTO_ACCOUNTING_FLAG, when itis 'Y,, AutoAccounting will not be invoked to determine the GL accounts to use, RA_CUSTOMER_TRX_LINES_ALL.OVERRIDE_AUTO_ACCOUNTING_FLAG = Y. f, Impact of Cross Validation Rules Since AutoAccounting handles the determination of which segments of a GL account to retrieve from various sources such as Salesreps, Transaction Types, Sites, Standard Lines and so on, you may encounter issues wherein the complete GL. account cannot be properly assembled because it has violated Cross Validation Rules, gtty7ham_78aid=1080995.1 hnipes/ieuppart oracle. comlepmesifacesiDocumentDigply? adc at2ysR015 hnipes/ieuppart oracle. comlepmesifacesiDocumentDigply? adc Document 1080985.1 Cross-validation (also known as cross-segment validation) controls the combinations of values you can create when you enter values for key flexfields. A cross-validation rule defines whether a value of a particular segment can be combined with specific values of other segments. Cross-validation is different from segment validation, which controls the values you can enter for a particular segment. Cross-validation rules prevent the creation of combinations that should never exist. When you have checked your AutoAccounting setup and validated that sources have been defined correctly, and yet you continue to encounter errors wherein some segments still cannot be derived and the complete GL accounting segments cannot be assembled completely, please check your Cross Validation Rules. Fo rmore information on how Cross Validation works and how to set it up, please review Chapter 5, Using Additional Flexfield Features in the Oracle Applications Flexfields Guide g. Unexpected GL accounts derived for Revenue / Receivables when AutoAccounting is based on Salesreps When you setup AutoAccounting to derive GL accounts from Salesreps for the Receivable and/or Revenue GL accounts, please note the following: + Receivable GL account, is derived from the GL accounts setup for the Salesperson you specify at the Transaction Header level, which you navigate to via Transactions > Transactions, within the transaction form the Salesperson at the header level is defined in the More tab. In the screenshot below, the GL accounts setup for Pat Murphy will be used when deriving the Receivable GL account, eps Cony TS ees von (ATID ts io omnia nt [in Opa Teta = + Revenue GL account, is derived from the GL accounts setup for the Sales Credits that, you specify at the Sales Credits form, which you navigate to via Transactions > Transactions, within the transaction form is a Sales Credits button, as shown in screenshots below. Take note that the Salespersons you specify in the Sales Credits form do not need to match the Salesperson defined at the transaction header level. In the second screenshot, the Revenue GL accounts will be derived from the GL accounts setup for Robin Bates and Marsha Able. gtty7ham_78aid=1080995.1 asst2ysR015 ==] come eos h, Wrong Revenue GL distributions when AutoAccounting is based on Salesreps When AutoAccounting for Revenue is based on Salesreps, and you have multiple Salesreps associated to an invoice, wherein each Salesrep uses different GL account segments, you may encounter an issue where the entire Revenue accounted amount is incorrectly allocated to the first Salesrep. This issue is described in Note 826930.1, Autolnvoice Issue: Accounted Amounts are Wrong when AutoAccounting is Based on Multiple Salesreps 3. Troubleshooting issues in Imported Transactions in the Transaction Workbench a. Warning: Rerun AutoAccounting when maintaining Autoinvoice sourced transactions When a transaction created via AutoInvoice is queried in the transaction workbench, navigating to Line Items invokes a popup window asking: ReRun AutoAccounting? even when no changes have been made to the data. hip:support oracle. comlepmesifacesiDocumentDisplay? ad ct-stato=tdpttyham_78Aid=1080805.12ysR015 Document 1080985.1 This issue is due to leading or trailing spaces in the data uploaded from the RA_INTERFACE_LINES table. To help identify which tables have leading or trailing spaces, and strip these spaces out of the data, Oracle has created a script that you can locate in your environment under the FND_TOP directory: $FND_TOP/sql/afchrchk.sql First, run this script in a Test environment. If you reply N to the question: Automatically fix all errors found (Y/N)? then it will just list the tables that have this issue. If you want to stip the data of leading/trailing spaces, re-run the script an reply with Y to the same question, ‘After verifying that the issue is fixed when querying the transaction in the Transaction workbench, you can promote the fix to your Production instance, To avoid hitting this issue, ensure that the data populated into the interface tables do not contain leading or trailing spaces. | 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. To provide feedback an this note, click on the Rate this document link. If you feel that a Service Request is needed, please be sure to provide the information listed below. + Test to see if the problem can be replicated in the AR transaction workbench Include the AutoInvoice Exception Report if any Include the Autolnvoice Concurrent Process log file (see Note 1079666.1) Enable and include the FND debug log file generated by Autolnvoice (see Note 1079666.1) Include Diagnostics: © Oracle Receivables Autolnvoice Interface Data Collection Test, this would show support what the interface data looks like © Oracle Receivables Autolnvoice Setup Test, this would include file versions and AutoAccounting setup For information on the diagnostic, please review the Diagnostic catalogs: Release 11.5: see Note 179661.1, E-Business Suite Diagnostics 11i Test Catalog Release 12,x: see Note 421245.1, E-Business Suite Diagnostics References for R12 Once you have identified your release, locate the right note for example, in 12.0.6, Note 732187.1, R12.0.6+ : Oracle Receivables Autolnvoice Interface Data Collection Test NOTE: 1067402.1 - Autonvoice Setup for Release 12: A Case Study Using a Simple Script NOTE:1075757.1 - Troubleshooting AutoInvoice for Oracle Receivables Release 11.5 Through 12 NNOTE:1079666,1 - How to Capture a Debug Log or Trace File and Diagnostics for Autolnvoice in 111 and R12 NOTE:1080995.1 - Troubleshooting AutoAccounting in AutoInvoice ‘NOTE: 1087263.1 - Autolnvoice and Transaction Workbench Error: Please complete your tax accounting flexfield hiip:support oracle. com/epmesifacesiDocumertDisplay? ad ct-stto=1dptlyTham_78Aid=1080095.1 ant2ysR015 Document 1080985.1 NOTE:1088218.1 - Autolnvoice & Transaction Workbench Error: Please Correct the Receivable Account Assignment NOTE:179661.1 - E-Business Suite Diagnostics 111 Test Catalog NOTE:421245.1 - E-Business Suite Diagnostics References for R12 NNOTE:436831,1 - Autoinvoice errors: Please complete the offset account assignments NOTE:732187.1 - R12.0.6+ : Oracle Receivables AutoInvoice Interface Data Collection Test NOTE:826930.1 - AutoInvoice Issue: Accounted Amounts Are Wrong When AutoAccounting is Based on Multiple Salesreps NOTE:885225.1 - Setting Up and Troubleshooting Tax Accounting for R12 E-Business Tax (EBTax) and Oracle Receivables NOTE:1088251.1 - Autolnvoice, Transaction Workbench or Invoice API Error: Please correct the revenue account assignment NOTE:1344503.1 - Autolnvoice Error: Not all AutoAccounting types are defined NOTE: 1069052.1 - Setting Up AutoAccounting Rules In Receivables [Video] NOTE: 1904785.1 - Oracle Receivables AutoAccounting Analyzer hiip:support oracle. com/epmesifacesiDocumertDisplay? ad ct-stto=1dptlyTham_78Aid=1080095.1 aia