In this Document

Applies to:

Main Content

Download the latest EBS Oracle Receivables AutoAccounting Analyzer version (200.9)

  
 New for Sysadmins/DBA’s! EBS Analyzer Bundle Menu Tool Doc ID 1939637.1 to provision and maintain all your analyzers. Analyzer Bundle Menu Tool is a perl menu system to easily execute, update and install analyzers as concurrent programs/assign to request groups.

Purpose

The EBS Oracle Receivables AutoAccounting Analyzer is a self-service health-check script that reviews AutoAccounting related data, analyzes current configurations and settings for the environment and provides solutions for known issues, feedback and recommendations on best practices. 

Analyzers are designed by Support to proactively assist you to better diagnose and maintain your Oracle Application environments.  Analyzers may also be used as data collection tools by Support Engineers.

NOTE:  This is a non-invasive script - the Analyzer does not perform any INSERTs, UPDATEs or DELETEs to your data; it just reports on it.
The Analyzer identifies known issues and provides solutions and recommended actions to be performed for the specific instance it was run on and can be run at any time.
For production instances, you should first apply any recommended actions or solutions to a recent clone to ensure an expected outcome.

We welcome and encourage you to share your feedback via the EBS Oracle Receivables AutoAccounting Analyzer feedback thread in the My Oracle Support Receivables Community. Your feedback shapes the content of existing Analyzers and drives creation of new Analyzers.

Audience

• DBAs and System Administrators - run the script and review the output
• Product Specialists and Business Analysts - review the output
• Other interested parties/end users - review output to resolve identified opportunity improvement areas
  

Benefits

• Immediate analysis and output of Oracle Receivables AutoAccounting data from a particular environment
• Identifies Receivables system setup and configurations
• Provides recommended actions and best practices
• Runs as a standalone or Concurrent Request
  
• Identifies possible causes for AutoAccounting errors such as:
  • Please complete the offset account assignments
  • Please correct the receivable account assignment
  • Please correct the revenue account assignment
  • APP-AR-42536: This transaction is associated with at least one invalid or end-dated GL account. Please correct the account.
  • APP-AR-11526: Please complete the offset account assignments

Back to Top

Download The Latest Version

Download the latest EBS Oracle Receivables AutoAccounting Analyzer version (200.9)

 

Since Analyzers are regularly updated to include newly identified issues and solutions, we highly recommend always using the latest version.  To verify the version of your currently installed Analyzer:

• Execute the Analyzer via SQL script or concurrent request and review the Execution Details section in the generated output HTML file.
  
• Alternatively, you can find the Analyzer version information in the executable package using the following SQL statement:
  

select name, text from DBA_SOURCE
where name = 'AR_AUTOACC_ANALYZER_PKG'
and text like '%$Id%';

Back to Top

Running The Analyzer - Configuration / Setup / Execution

Parameters

• p_org_id: (Required) Enter Organization ID
• p_account_type_in: (Required) Enter the account type for which you are getting errors: REC, REV or OFFSET, use as follows:
  
  • Revenue (REV)
    
  • Receivable (REC)
    
  • Unearned Revenue (OFFSET)
    
  • Unbilled Receivable (OFFSET)
  • AutoInvoice Clearing (OFFSET)
• p_missing_seg: (Required) Enter a numeric value corresponding to the segment AutoAccounting is unable to derive
• p_where: (Required) Identify where is the error raised, valid options are:
  • AUTOINV - for when the AutoAccounting error is raised in AutoInvoice
  • TRXFORM - for when AutoAccounting error is raised in the Transactions form
• p_customer_trx_id: (Required if p_where = TRXFORM) If you are getting the error in the Transaction form, enter the Customer Trx Id of the transaction raising the error, otherwise pass NULL
  
• p_interface_line_id: (Required if p_where = AUTOINV) If you are getting the error in AutoInvoice, enter the Interface Line Id of the record raising the error, otherwise pass NULL
  

Creating the Package Definition

Run the script ar_autoaccounting_analyzer.sql as user APPS to create the package definition.  This is required each time you download a new version of the script:

sqlplus apps/

SQL> @ar_autoaccounting_analyzer.sql

 

The EBS Oracle Receivables AutoAccounting Analyzer can either be run as a Concurrent Request or via SQL*Plus.  Instructions for both options are listed below:

Running the Analyzer as a Concurrent Request

1. Install the package using the sqlplus.
   
   sqlplus apps/
   SQL> @ar_autoaccounting_analyzer.sql
     
   
   
2. Register the Concurrent Program
   
   After running in sqlplus commands above, define a new Concurrent Program using the FNDLOAD utility:
   
   $ $FND_TOP/bin/FNDLOAD apps/ 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct AR_AUTOACCAZ.ldt CUSTOM_MODE=FORCE UPLOAD_MODE=REPLACE
   
   This will create the concurrent program Oracle Receivables AutoAccounting Analyzer in the Receivables application.
   
   
3. Setup the Request Group
   Note: once the analyzer is set up as part of the Request group, you do not have to do this step each time you download a new version of the analyzer.
   
   You have two options to setting up the request group:
   
   a. Manually:
   Add the new concurrent program = Oracle Receivables AutoAccounting Analyzer
   We recommend adding analyzers to Receivables All request group, but you can add it to another request group if you prefer.
   

   Responsibility: System Administrator
   Navigation: Security > Responsibility > Request > Query the Group name = Receivables All
   In the Requests section, create a new record and enter Type = Program, Name = Oracle Receivables AutoAccounting Analyzer.
   Save your changes.
   
   b. OR via script:
   

   Alternatively, you can run ar_autoaccounting_analyzer_rg.sql to automatically add this analyzer to Request Group = Receivables All
   
   SQLPLUS apps/ @ar_autoaccounting_analyzer_rg.sql
     
   
   
4. After completing the steps above, you can now run the analyzer from the Receivables application.
   
   Responsibility: Receivables Manager
   
   If you added the analyzer to Receivables All, you can run the analyzer via the following navigation:
   Navigation: View > Requests
   Submit a New Request > Single Request > Oracle Receivables AutoAccounting Analyzer
   
   Otherwise, navigate to the menu option that you attached the analyzer to and run from there.
   
   Enter the required parameters:
   
   
   Please note that if run as a concurrent program, the Parameter Names/Values change to provide a list of values (LOV) to make the parameter requirements more user-friendly.
   You will be asked for :
   - Organization Name (instead of Org ID)
   - Segment Name (instead of Segment Number), the list of values shows the segments in sequential order
   - Transaction Number (instead of Customer Trx ID)
     
   
   
   • Organization Name: (Required, LOV provided) Enter Organization Name
   • Account Type with missing segment: (Required, LOV provided) Enter the account type for which you are getting errors: REC, REV or OFFSET, use as follows:
     
     • Revenue (REV)
       
     • Receivable (REC)
       
     • Unearned Revenue (OFFSET)
       
     • Unbilled Receivable (OFFSET)
     • AutoInvoice Clearing (OFFSET)
   • Missing Segment Name: (Required, LOV provided) Pick from list of values the segment name AutoAccounting is unable to derive.
   • Identify where error is raised: (Required, LOV provided) Identify where is the error raised, valid options are:
     • AUTOINV - for when the AutoAccounting error is raised in AutoInvoice
     • TRXFORM - for when AutoAccounting error is raised in the Transactions form
   • Transaction Number: (LOV Provided, if 4th parameter value = TRXFORM) Enter the transaction number of the transaction raising the error, otherwise leave null
   • Interface Line Id: (LOV Provided, if 4th parameter value = AUTOINV) Enter the Interface Line Id of the record raising the error, otherwise leave null
     
   
   Submit
   

 

Back to Top

Running the Analyzer via SQL*Plus

Log into SQL*Plus as the APPS user, SPOOL a meaningful output file name and run the script. 

You can use a simple hard-coded script such as:

begin
   ar_autoacc_analyzer_pkg.main(
     p_org_id => 204,
     p_account_type_in => 'REC',  
     p_missing_seg => 3,
     p_where => 'TRXFORM',
     p_customer_trx_id => 778862,
     p_interface_line_id => NULL );
end;
/

  
or you can run the wrapper provided in the attached .zip file: ar_autoaccounting_analyze.sql, and provide the input parameters as requested.
Following shows the spool generated from running the wrapper in SQL*Plus:

Submitting Oracle Receivables AutoAccounting.
===========================================================================
Enter the org_id for the operating unit. This parameter is required.
===========================================================================

Enter the org_id: 204

===========================================================================
Enter the account type for which you are getting errors, valid values are: REC ( Receivable), REV (Revenue) or OFFSET (for Unearned Revenue, Unbilled Receivable or AutoInvoice Clearing).
===========================================================================

Enter the Account type with missing segment: REV

===========================================================================
Enter number associated to missing segment This parameter is required.
===========================================================================

Enter the Missing segment number: 3

===========================================================================
Location of AutoAccounting error, valid values are: AUTOINV (AutoInvoice) or TRX FORM (Transaction form) This parameter is required.
===========================================================================

Enter the Location of error: AUTOINV

===========================================================================
If location of error = TRXFORM, enter a value for CUSTOMER_TRX_ID, otherwise leave it blank.
===========================================================================

Enter the Customer Trx ID:

===========================================================================
If location of error = AUTOINV, enter interface line ID, otherwise leave it blank.
===========================================================================

Enter the Interface Line ID: 1310691

Files are located on Host : post-rel121.us.oracle.com
Output file :
/usr/tmp/AR_AUTOACC_Analyzer_post-rel121.us.oracle.com_TEST121_2017-03-22_10_13.html
Log file :
/usr/tmp/AR_AUTOACC_Analyzer_post-rel121.us.oracle.com_TEST121_2017-03-22_10_13.log

PL/SQL procedure successfully completed.

  

Back to Top

Analyzer & Sample Output

The EBS Oracle Receivables AutoAccounting Analyzer generates an HTML report output that makes reviewing the output easy.  Where the output is stored is dependent on how the report was run.

         /AR_AUTOACC_Analyzer_machine_SID_YYYY-MM-DD_hh:mm.html (using 24 hour clock)

If the Analyzer is run as a concurrent request:

• Navigate to View > Request and choose the View Output button. 
  
• To save the output locally, select File > Save Page As, and then choose 'Web page, HTML only' for the 'Save as type.' 
  
• The output is also available on your server at $APPLCSF/$APPLOUT/ o.out and can be copied & renamed to AR_AUTOACC_Analyzer_.html

 

If the Analyzer is run from SQL*Plus:

• The output file is created in the same directory it was run from OR the location of your output file will be displayed in the SQL*Plus window after execution.

 

Click the button below to view a sample output of the EBS Oracle Receivables AutoAccounting Analyzer:

 

Known Issues & Solutions

 

Issue	Solution
You run the analyzer as a concurrent program and you are using the MO: Security Profile to allow access to multiple operating units, however, the list of values for Organization Name does not present all the values.	Workaround: Set multi_org_category flag to M manually. Responsibility: System Administration (Take note use System Administration and not System Administrator) Navigation: Concurrent > Programs Enter the following: Application = Receivables Short Name = ARAUTOACC Click on Go Click on Update icon (pencil) to update the details of report Click on Request tab Select Operating Unit Mode = Multiple (M) and save it.
When attempting to select buttons in Internet Explorer, you get an error that says, "To help protect your security, Internet Explorer has restricted this webpage from running scripts or ActiveX controls that could access your computer. Click here for options."	Buttons will not work if you have protection settings for Internet Explorer.  From the Click here for options choices, select "Allow Blocked Content" and say yes to "Are you sure you want to let this file run active content?" You should now be able to use the buttons in the Analyzer output.
When attempting to save the concurrent request output, the file contains only "Authentication failed."	For Internet Explorer, set "Check for newer versions of Stored Pages" to 'Every time I visit the webpage' via Tools > Internet Options > General tab > Browsing History section > Settings.  Re-save the Analyzer output. For FireFox, enter about:config into your URL location box in Firefox, locate the browser.cache.check_doc_frequency and change it to 1.  Re-save the Analyzer output. Workaround Options:  Restart your browser or copy/rename the output from $APPLCSF/$APPLOUT/o.out to /ARAUTOACC_ANALYZER_.html.
Output contains duplicate buttons after saving output created from concurrent request.	To save the output locally, select File > Save Page As, and then choose 'Web page, HTML only' for the 'Save as type.'
When you receive the output via email, buttons are not displayed or the format is incorrect and sections display, “File not found UrlBlockedError.aspx” href="javascript:;" was replaced with href="UrlBlockedError.aspx"	This is an email server issue.  Have the person sending the file either zip it and resend via email or shared space (ftp).  This will prevent the mailing server from modifying the output.

 

Back to Top

Questions, Comments & Feedback

Have questions or suggestions?

Click the button above to ask questions about and/or provide feedback on the EBS Oracle Receivables AutoAccounting Analyzer.  Share your recommendations for enhancements and help us make this Analyzer even more useful!

To search for solutions or post new questions about Receivables in general, visit the Oracle Receivables Community on My Oracle Support Community (MOSC).


Back to Top

Related Resources

Check out the full list of Oracle E-Business Suite (EBS) Proactive Support Analyzers and Tools (Doc ID 1545562.1)

• E-Business Suite Support Analyzer Bundle Menu Tool (Doc ID 1939637.1)
• Oracle Receivables Index of all Information Centers (Doc ID1473872.2)
• Collaborate with industry peers in the Oracle Receivables Community
  

Back to Top