4/13/2016 Document 1489381.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=hq9w4i5ml_232&id=1489381.1 1/7

EBS Payables Period Close Analyzer (Doc ID 1489381.1)

In this Document

Main Content

Purpose

Download the Latest Version

Running the Analyzer ­ Configuration / Setup / Execution

Parameters

Run the Analyzer via SQL*Plus

Run the Analyzer as a Concurrent Request

Analyzer & Sample Output

Known Issues & Solutions

Questions, Comments & Feedback

Related Resources

Best Practices for Payables Period Close

EBS Analyzer Bundle Menu Tool

References

APPLIES TO:

Oracle Payables ­ Version 12.0.0 and laterInformation in this document applies to any platform.

MAIN CONTENT

Download the EBS Payables Period Close Analyzer Latest version (200.8)

PURPOSE

Analyzers are designed by Support to proactively assist you to better diagnose and maintain your OracleApplication environments. We welcome and encourage you to share your feedback via the PayablesPeriod Close Analyzer feedback thread in the My Oracle Support Payables Community. Your feedbackshapes the content of existing Analyzers and drives creation of new Analyzers.

The analyzer is a self­service health­check script that helps identify transactions which may stop theperiod close within your Payables application.In addition, you can also run the data validation report to check for data integrity issues in that period. This will help you in resolving the period close show stoppers and keeping your system ready for periodclose without missing any deadlines.

You should always run this script prior to logging a Service Request when you are not able to close theperiod or if you simply want to proactively verify the data integrity of your transactions to keep the

4/13/2016 Document 1489381.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=hq9w4i5ml_232&id=1489381.1 2/7

system ready for period close.

Your application data is not altered in any way when you run this analyzer. This is a non­invasive script ­ the Analyzer does not perform any INSERTs, UPDATEs orDELETEs to your data; it just reports on it.The Analyzer identifies known issues and provides solutions and recommended actions to beperformed 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 recentclone to ensure an expected outcome.

Audience

DBAs and System Administrators ­ run the script and review the outputProduct Specialists and Business Analysts ­ review the outputOther interested parties/end users ­ review output to resolve identified opportunity improvementareasThis script is designed for Oracle Applications Release 12 and requires

APPS Access (SQL*Plus)Filesystem access (apps logfiles) $APPLCSF/ $APPLLOGSYSADMIN access permissions

Benefits

Execute analysis anytime to compare trending from past outputsAnalyzers are also used as data collection tools by Support Engineers

IMPORTANT: In conjunction with the analyzer described in this note, R12.1 customers shouldreview the notes indicated below which describe the Recommended Patch Collections (RPC) forrelated products. The vast majority of the data integrity issues detected by this analyzer could beproactively avoided by applying the RPC's for these products:Doc ID 1397581.1: R12.1: Payables Recommended Patch Collection (AP RPC)Doc ID 1481235.1: R12.1: E­Business Tax Recommended Patch Collection (ZX RPC)Doc ID 1481221.1: R12.1: Payments Recommended Patch Collection (IBY RPC)Doc ID 1481222.1: R12.1: Sub Ledger Accounting (SLA) Recommended Patch Collection (XLA RPC)

Back to Top

DOWNLOAD THE LATEST VERSION

Download the EBS Payables Period Close Analyzer Latest version(200.8)

Analyzers are regularly updated to include newly identified issues and solutions, so we recommendalways using the latest version. To verify the version of a previously downloaded Analyzer:

Unzip the file into a local directory, it contains the package definition fileap_period_close_analyzer.sql as well as a wrapper script (ap_period_close_analyze.sql)which can be used to submit the detection procedures.If you want to run the AP Data Validation Report also to check for data corruptions and the

4/13/2016 Document 1489381.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=hq9w4i5ml_232&id=1489381.1 3/7

corresponding GDFs available, please download:ap_gdf_detect_pkg.zip: This file contains the package definitionfile ap_gdf_detect_pkg.sql.

Execute the analyzer and review the Execution Details section in the generated output HTML file.Alternatively, you can find the analyzer version in the executable package using following sqlstatement:

Select name, text from dba_source Where name in ('AP_PCLOSE_ANALYZER_PKG') and text like '%$Id%';

Want to be notified via email when this document is updated? Check out the Enabling HotTopics section under the Just the Facts tab of Doc ID 793436.2 (My Oracle Support How to Series:How to use Hot Topics Email notification to subscribe to Support Product News, SRs, Bugs, etc. andevents so that you Never Miss an Important Update ­ [VIDEO])

Back to Top

RUNNING THE ANALYZER ­ CONFIGURATION / SETUP / EXECUTION

The Payables Period Close Analyzer can be run via SQL*Plus or as a Concurrent Request.

Parameters

Ledger ID: (REQUIRED) The ledger ID of the Payables period which you are tryingto close.Period Name: (REQUIRED) The period name of the Payables period which you aretrying to close. This is case sensitive and must be an open period for the ledgerspecified.Operating Unit: (OPTIONAL) Any operating unit organization id, in which Payableshas been implemented, can be provided. Transactions to be validated will be limitedto the operating unit(s) specified. Multiple operating units can be provided simply asa comma separated list. When large volumes of data are involved, it is advisable tolimit the amount of data to be validated using this parameter. All operating unitsspecified must be associated with the ledger identified with the p_ledger_idAP Data Validation Report: (OPTIONAL) A yes or no value to indicate if youwould like to run the AP Data Validation Report also to check for more corruptionsand known GDFs available for the particular period, ledger, and operating unitsspecified.Maximum Number of Rows: (DEFAULT of 10) A number value to indicate themaximum number of transactions to display for any particular data validation. Usethis number to control the potential size of the output file if there are validationswhich return many instances.

Run the Analyzer via SQL*Plus

1. Execute the scripts as user APPS to create the package definitions. This is required each time you download a new version of the script.

sqlplus apps/<apps_password>

SQL> @ap_period_close_analyzer.sqlSQL> @ap_gdf_detect_pkg.sql

4/13/2016 Document 1489381.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=hq9w4i5ml_232&id=1489381.1 4/7

2. Run the wrapper script ap_period_close_analyze.sql

To validate all invoices, payments, in a specified period for specified operating units,run ap_pc_analyze.sql as illustrated below. This script will prompt you for the period name, ledger id, operating unit (oroperating units), and option to check whether you want to run the data validationreport also with this to check for data corruptions. Period should be open for which the analyzer is run. Also, the ledger id for whichthe period is closed should be specified. To indicate more than one operating unit,separate values with a comma. If operating unit is left blank the process will runfor all operating units (though this is generally not recommended for performancereasons). If AP Data Validation Report is set to Y, then the process will submit the masterGDF report also. (though this is generally not recommended for performancereasons).

For additional flexibility, the process can also be called without running the wrapperscript as well. The report is run by executing the procedureAP_CLOSE_DETECT_PKG.MAIN_PC with the appropriate parameters. See below fora detailed listing of the procedure's parameters and their usage. Here are someexecution examples:

4/13/2016 Document 1489381.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=hq9w4i5ml_232&id=1489381.1 5/7

SQL> set serveroutput on size 1000000

In order to check all transactions stopping period close for a particular period youcould simply run:

SQL> BEGIN ap_pclose_analyzer_pkg.main_pc(

p_per_name => '<period_name>', p_ledger_id => <ledger_id>);

END; /

To validate all transactions for one of your operating units (org1) you could run:

SQL> BEGIN ap_pclose_analyzer_pkg.main_pc(

p_per_name => '<period_name>', p_ledger_id => <ledger_id>,

p_org_ids => '<org_id>'); END;

/

To run the same validations but including both org1 and org2 you could run:

SQL> BEGIN ap_pclose_analyzer_pkg.main_pc(

p_per_name => '<period_name>', p_ledger_id => <ledger_id>,

p_org_ids => '<org1_id>,<org2_id>'); END;

/

To run the analyzer along with the AP Data Validation Report to check for morecorruptions you could run:

SQL> BEGIN ap_gdf_detect_pkg.main_pc(

p_per_name => '<period_name>', p_ledger_id => <ledger_id>,

p_master_gdf => 'Y'); END;

/

Run the Analyzer as a Concurrent Request

Running the 'Payables Period Close Analyzer' as a concurrent request allowsfunctional users to run the analyzer without needing the APPS user password.

1. Execute the scripts as user APPS to create the package definitions. This is required each time you download a new version of the script.

sqlplus apps/<apps_password>

SQL> @ap_period_close_analyzer.sql

4/13/2016 Document 1489381.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=hq9w4i5ml_232&id=1489381.1 6/7

SQL> @ap_gdf_detect_pkg.sql

2. If you would like to run the Analyzer as a concurrent program so it can be runperiodically or as a concurrent request from concurrent manager, please review DocumentID 1489916.1.

Back to Top

ANALYZER & SAMPLE OUTPUT

The Payables Period Close Analyzer generates an html report output that makes reviewingthe output easy and effective. Where the output is stored is dependent on how the report was run.

AP_PCLOSE_Analyzer_<machine>_<sid>_<date>.htmlAP_PCLOSE_Analyzer_<machine>_<sid>_<date>.log

If the Analyzer is run as a concurrent request:

Navigate to View > Requests and choose the View Output button.To save the output, select File > Save Page As then choose ' Web Page, HTML only' for the'Save as type'.The output is also available on your server at $APPLCSF/$APPLOUT/o<REQUEST_ID>.out and canbe copied & renamed to <meaningful_filename>.html

If the Analyzer is run from SQL*Plus:

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 Payables Period Close Analyzer:

Back to Top

Known Issues & Solutions

See Doc ID 2116869.1 for all known problems with analyzers in general.

Back to Top

QUESTIONS, COMMENTS & FEEDBACK

Still have questions, or suggestions?

Click the button above to provide feedback for the Payables Period Close Analyzer, andoffer suggestions, improvements, or ideas on how to make this proactive script more

4/13/2016 Document 1489381.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl­state=hq9w4i5ml_232&id=1489381.1 7/7

useful.

To search for solutions or post new questions about Payables in general, click here to access thePayables Community on My Oracle Support Community (MOSC).

Back to Top

RELATED RESOURCES

Check out the full list of Oracle E­Business Suite (EBS) Proactive SupportAnalyzers and Tools

Doc ID 1360390.1 R12: Master GDF Diagnostic (MGD) to Validate Data Related to Invoices,Payments, Accounting, Suppliers and EBTax [VIDEO]Doc ID 874903.1 R12: What is a Generic Datafix Patch (GDF) and what GDFs are available forPayables? [VIDEO]Doc ID 1491064.1 Get Proactive Instructional Webcast Series

Best Practices for Payables Period Close

Title Description Recording &PDF

Resolve —BestPractices forE­BusinessSuitePayablesPeriod Close

This one hour webcast will show you how to take advantageof three primary recommendations: Master Generic Datafixes, recommended Patch Collections and Period CloseAnalyzer for corruption / non­corruption issues. Customerswho are involved in the Payables Period Close activities(Technical and Functional) will benefit most from thiswebcast.

Recording |PDF

EBS Analyzer Bundle Menu Tool

The EBS Analyzer Bundle Menu Tool (Doc ID 1939637.1) allows you to provision and maintain all yourAnalyzers. The Analyzer Bundle Menu Tool is a Perl menu system that enables you to easily execute,update and install Analyzers as concurrent programs and assign them to request groups.

The tool is updated monthly to include newly released and updated EBS Analyzers. For a complete list ofEBS Analyzers currently included in the EBS Analyzer Bundle Menu Tool, see the Change Log forBundle Zip section of E­Business Suite Support Analyzer Bundle Menu Tool (Doc ID 1939637.1)

Back to Top

Didn't find what you are looking for?