Support

Yes, you must not modify the Advanced Custom Properties in the Excel output. These are also critical for the report’s proper functioning.

The description does not specify a default, implying that if the profile is left blank, no prefix is added.

The upgrade is the perfect time to use Blitz Report’s fully automated Discoverer migration capability. Migrate all essential Discoverer worksheets into Blitz Report ahead of time, ensuring continuous operational reporting post-upgrade.

The Blitz Report Project Implementation and Upgrade Toolkit is designed specifically to simplify managing EBS projects and upgrades. It provides a ready-made solution for common project tasks such as exporting master data, tracking changes, and creating new operational reports efficiently.

You should configure the profile option ‘Blitz Report Discoverer Import Report Name Prefix’. This sets the prefix for all imported Discoverer reports.

You can prepare and save pre-upgrade comparison reports using Blitz Report, focusing on complex financial areas like GL Account Analysis and YTD balances. These reports can be quickly rerun post-upgrade, delivering immediate, formatted Excel output for easy data verification and pivot table analysis.

No, Blitz Report maintains its high-volume efficiency. There are no volume limitations , allowing you to extract entire planning cycles worth of exceptions without hitting row constraints like those seen in older EBS reporting tools.

Use the Concurrent Request Monitoring and Alert Reporting tool. Configure an alert report filtered by Status (Error; Warning) and Phase (Running, Waiting) with a parameter set for `Running longer than x Minutes` to identify issues with patch application or post-upgrade routines immediately.

For a given invoice line, both the IPV and ERV amounts will be shown on the same row, in separate columns, and these entries have the Type ‘IPV-ERV’.

The CE General Ledger Reconciliation report provides the equivalent functionality.

Use the CAC Invoice Price Variance report. It displays IPV, ERV, and A/P Accrual Write-Off Variances for an entered date range.

The primary benefit is speed, usability, and flexibility. Planners can quickly create custom reports focused on specific exceptions or data fields they require. The output is delivered instantly to Excel for immediate analysis, avoiding the cumbersome PWB interface for bulk data handling. We also support exporting advanced metrics like horizontal planning data and detailed pegging exports.

High `cache` traffic indicates frequent global cache communications, often implying that buffer blocks are being transferred frequently between instances. This may point toward poor data locality or insufficient buffer cache sizing.

You should use the DBA AWR Interconnect Traffic report. This report displays information about interconnect usage by instance in a RAC configuration.

If you need to restore the hidden rows, you simply click the Unhide Zeros button, which will show all rows previously concealed by the Hide Zeros feature .

Blitz Report can be implemented in less than an hour. It requires no additional functional training since it operates using existing EBS commands and follows the standard EBS security framework and concurrent request mechanism.

Yes, major EBS version upgrades (like 12.2.7 to 12.2.8 or 12.2.8 to 12.2.9 ) follow similar technical protocols, requiring careful RUP application, AD/TXK patching, and environmental verification using tools like SQL diagnostic reports.

If the requirement is not met, Blitz Report evaluates the logical expression at run-time and displays an error message, preventing the report from launching a concurrent process.

Yes, while Blitz Report is primarily known for Excel output, it does support options to Generate PDF of Blitz Report™ output. This is achieved through a post-processing step on the report output, providing flexibility for different delivery requirements.

Blitz Report enforces strict change control. Consultants can drop their custom SQL scripts directly into the tool, and the application maintains full version control with audit comments within your EBS instance, guaranteeing traceability for every modification.

Precisely. By leveraging the standardized ECC SQL queries that drive the dashboards , Blitz Report runs those proven queries against the EBS data sources. This ensures the output is assured and, crucially, means there are no data limits on the Excel output, overcoming the fundamental volume limitations of the ECC dashboards themselves.

You should use the Snapshot tool, available under Blitz FSG Tools . The Snapshot tool converts your live Blitz FSG report into static, frozen values by removing all underlying Blitz FSG functions (like `br_balance`) from the workbook . It replaces these functions solely with the returned numerical results, effectively disconnecting the report from Oracle . Critically, it preserves all other standard Excel formulas and formatting within the workbook .

Blitz Report is the ideal tool for ECC administration and data extraction, specifically designed for business users and DBAs supporting ECC dashboards. Our solution focuses on the replication of the ECC dashboard views directly within EBS. This allows for the extraction of the full data set to perfectly formatted Excel reports, unlike the restricted CSV files provided by the dashboard views.

The standard process for creating a new report within Blitz Report eliminates the hassle of registering new concurrent programs and reports with System Administration. For the Zoom integration specifically, you essentially connect the Blitz Report to the target form using standard EBS functionality, typically through personalization or custom development that calls the Blitz Report execution hook with the appropriate parameters derived from the form context.

Blitz Report can indeed be seamlessly integrated into EBS forms using the Zoom functionality. This allows users to drill down from a specific record in an Oracle Forms screen directly to a detailed Blitz Report output, keeping the user experience within EBS.

To disable the SQL Tuning Advisor manually, execute: `exec dbms_auto_task_admin.disable(client_name=>’sql tuning advisor’, operation=>null, window_name=>null);`.

ADDM can be deactivated in non-actively monitored environments by setting `alter system set “_addm_auto_enable”=false`. The DBA AWR reports often provide better, more detailed insights than ADDM into performance bottlenecks.

The invitation is extended to all Oracle EBS professionals who have an interesting, creative solution for Oracle EBS reporting. The process involves submitting your report solution and ideas.

Since Blitz Report honors standard Oracle security policies, you must ensure that VPD policies are correctly applied to the underlying Payroll tables, enforcing row-level and column-level security for the payroll balance data. Additionally, the report itself can be restricted by EBS Responsibility.

No, this limit applies specifically to the LOV size during upload; the report SQL upload is handled by the ‘Upload Large SQL’ functionality.

The Concurrent Manager Load by time Intervals report allows the DBA to understand how the concurrent processing workload distributes throughout the day. This is a more advanced diagnostic tool complementing the standard Concurrent Request Monitoring and Alert Reporting by helping schedule resources more effectively.

You use the profile option ‘Blitz Upload Maximum LOV Size’. This sets the maximum upload list of values size in MB.

Yes, there is a recognized solution for Absence Visualization in Oracle EBS. This type of unique solution demonstrates the creative problem-solving capabilities of the Blitz Report platform for Oracle EBS professionals.

You should set the profile option ‘Blitz Report Template Access’ to ‘Private only’. This allows users to create private templates only.

You can use the DBA DBMS Profiler Data report. This report provides an Excel version of Oracle’s `dbms_profiler` PL/SQL performance analysis.

That is correct. You can refer to example scripts like `mass_import_excel4apps_reports.sql` for how this is scripted.

The Blitz Report form can optionally be assigned to all relevant responsibilities. Access can also be secured by configuration, especially for sensitive data areas like Human Resources, ensuring data integrity while maximizing user reach for Cost Accounting reports.

Blitz Report offers a method for rapid report development in under 5 minutes by utilizing the standardized Oracle ECC SQL queries. This is highly relevant for development or supporting consultants, ensuring the reports use the same foundation logic as the ECC dashboards.

The mass migration of Excel4apps Reports Wand concurrent programs uses the same PLSQL procedure as the BI Publisher import: `xxen_api.import_concurrent_program`.

The default is 100,000 rows, chosen to provide good Excel navigation performance, though it can be increased as required.

You set the profile option ‘Blitz Upload Maximum Rows’. This defines the maximum number of rows in a Blitz Upload Excel sheet.

Blitz Report is fully integrated with the native Oracle E-Business Suite interfaces, specifically built upon and utilizing both Oracle Forms and OAF pages. This architecture gives your users easy and centralized access to both financial and manufacturing information simultaneously, allowing complex costing reports to be defined via SQL.

Yes, Blitz Report is an established reporting software solution providing simple and effective reporting for Oracle EBS Cost Accounting. Its strength lies in its deep integration across the E-Business Suite.

Yes, proper prerequisite configuration is essential. The Blitz Report Discoverer import relies heavily on execution statistics collected by Discoverer, which populate the database table `EUL5_QPP_STATS`. To ensure these statistics are properly collected, you need to verify two critical profile settings in the Discoverer server configuration file (`pref.txt`) under the `[Database]` section: `QPPEnable` must be set to `1` and `QPPCreateNewStats` must also be set to `1`. Furthermore, users must properly exit Discoverer Desktop or Plus using the File>Exit menu to write the history information to the table.

Hi,
The Blitz Report Execution History report already provides this information without requiring you to write SQL queries. Here’s how you can use it effectively to meet your business needs:

Steps to Use Blitz Report Execution History:
Navigate to the Report:

• Open Blitz Report in Oracle EBS.
• Search for the report titled Blitz Report Execution History.

Set the Parameters:

The report provides various parameters to filter the data based on your needs. Here’s a breakdown of key parameters you can use:

1. Report Name:
   Filter the execution history by a specific report name. This is useful when you want to analyze the performance and execution details of a particular report.
2. Category:
   Narrow down the results to reports that belong to a specific category (e.g., Financial, Inventory). This helps focus on relevant reports for your business area.
3. Report Name starts with:
   Retrieve reports whose names start with a specific prefix. This is ideal for analyzing related reports grouped by a naming convention.
4. Submitted by User:
   View reports submitted by a particular user. This is helpful for auditing or tracking activity by a specific individual.
5. Started within Days:
   Fetch reports executed within the last X days. For example, use this to review reports submitted in the past week.
6. Start Date From / Start Date To:
   Define a custom date range to filter reports based on when they were executed. Use this for more precise time-bound analysis.
7. Show Parameters:
   Include the runtime parameters used for each report execution in the output. This provides additional context on how the reports were configured.
8. Running or Errored:
   Filter the results to show only reports that are still running or errored. This is crucial for troubleshooting and resolving issues quickly.
9. Request Id:
   Fetch execution details for a specific report request using its unique ID. Use this when investigating a specific report run.
10. Run Id:
    Retrieve details of a report execution using its unique Run ID. This is useful for pinpointing specific instances.
11. Exclude System Reports:
    Remove system-generated reports from the output, focusing only on reports submitted by users.
12. Exclude Submissions from User:
    Exclude reports submitted by a specific user from the results. This is helpful when reviewing activity while omitting known or irrelevant submissions.

Run the Report:

• Set the desired parameters and run the report.
• The output will include detailed information about each report execution, including execution times, users, responsibilities, and performance metrics.

Analyze the Output:

• Use columns like Execution Time, Rows Processed, and File Size to evaluate performance.
• Look at the Status column to identify failed or long-running reports.
• The Parameters column shows runtime options used for each execution, helping you understand how the reports were configured.

Export for Further Analysis:

• You can export the report results to Excel or a CSV file for more in-depth analysis, sharing, or visualization.

Example Use Cases:

1. Troubleshooting Performance:
   Find reports that took longer than expected by sorting the output by Execution Time or Rows Processed per Second.
2. Audit User Activity:
   Filter the report by a specific user or responsibility to review who ran what and when.
3. Monitor Current Issues:
   Use the Running or Errored filter to identify problematic reports that need immediate attention.

Why Use This Report?
The Blitz Report Execution History is a user-friendly alternative to writing SQL queries. It’s designed to be flexible, intuitive, and provides all the necessary details to manage and monitor Blitz Report execution in your Oracle EBS environment. Let me know if you need guidance on configuring specific parameters!

Yes, consolidation is a key feature, especially when migrating from older tools like Discoverer. Instead of importing individual worksheets, you should use the `xxen_api.import_discoverer_folders` API or the corresponding menu option, ‘Discoverer Folders’. This process consolidates reports by importing only distinct folder or view object combinations. If multiple workbooks share the same foundation, they will be converted into a single Blitz Report with multiple templates representing the different column selections from the original workbooks, greatly simplifying maintenance.

Run the MRP End Assembly Pegging report. This is a detail report for MRP pegging, showing the planner, demand pegged quantity, dates, supply quantity, and supply date for each component.

Yes, you can mix formats, for example: ‘1110-1150;1210;~1111;~1120-1130’.

Yes, Blitz Report integrates with other diagnostic reports, such as the Concurrent Request Monitoring tool, which includes an option to output the active SQL text. This SQL ID can then be rapidly analyzed by other specialized Blitz Reports, such as the DBA AWR SQL Execution Plan History report.

When `SECURE` is enabled, application servers are registered as trusted machines by generating a large random ID number (the server ID) and storing it in both the application server’s DBC file and the database . The `AdminAppServer` utility is specifically used to generate these server IDs and register them with the database server . When the application server connects, the database verifies this ID .

The MRP Exceptions report is a detail report specifically for MRP Exception messages, covering those exact details.

Yes, the script receives the concurrent login credentials via the $FCP_LOGIN variable, which allows external processes to operate within the EBS context.

The workaround, as suggested in the context of this issue, is to keep the `SECURE` parameter value set to OFF for standalone Business Intelligence (BI) tools like Discoverer . This is necessary because Discoverer lacks the server ID mechanism required to be recognized as a trusted machine by the database when `SECURE` is enabled .

You get the full path using $outfile_name. There is also $output_filename for the base filename, and $additional_outfile_name if you defined an additional output directory.

Yes, it is a known issue that if the database security parameter `SECURE` is set to a secure value, Discoverer often fails to work . Oracle Support Document 1574364.1 confirms that while the parameter should be set to `SECURE` in general EBS security notes, setting it as such prevents Discoverer from functioning . Since Discoverer is desupported, Oracle is unlikely to provide a fix .

All user-entered input parameters are passed as variables, starting from $parameter1, $parameter2, and so on, up to $parameter87. You can retrieve the Operating Unit value using the corresponding parameter number.

The default limit is 160 characters.

Yes, for easier, name-based submission, you should use the Blitz Report concurrent program API `XXEN_API.REPORT_SUBMIT_CONCURRENT_` . This procedure allows you to reference the report name, parameter names, and template names by name, instead of relying on the argument’s sequential position . After calling `REPORT_SUBMIT_CONCURRENT_` to initiate the run ID, you use `XXEN_API.SET_PARAMETER_VALUE_` and `XXEN_API.SET_RUNTIME_OPTION` to set the specific values by name , .

Yes, the parameters allow for reporting against a secondary cost type (Cost Type 2).

The limit is intended to avoid errors when running the FNDCPPUR concurrent program.

The CAC Item List Price vs. Item Cost report is designed for this comparison. It compares the item master list price against any cost type (Cost Type 1) and lists the Standard Price (Market Price), Last PO Price, and a converted Last PO Price.

Yes, Migration Tools (Converters) are available to migrate report definitions from Oracle FSG, GL Wand, and Spreadsheet Server to the Blitz FSG solution.

The Drilldown Functionality allows access to detailed information at various levels, including balances, journal entries, and subledger transactions.

The key features include Balance and Detail Reporting to generate comprehensive reports and detailed insights. It also offers Oracle Data Integration, allowing Excel cells to link directly to Oracle data, which can be refreshed for real-time updates.

To resolve this, you may need to locate and temporarily remove the restrictive connection filter rule within the Weblogic Admin Console. In a previous example facing this exact issue, the request completed successfully only after removing a filter rule entry such as `* * 7776 deny`. Once the filter rule is removed or adjusted to allow the necessary communication from the EBS server to the ECC managed server port, you should rerun your Payables Command Center Data Load concurrent program. Remember that after the initial full load completes, you should schedule these programs to run in `INCREMENTAL_LOAD` mode for periodic data updates.

You need to edit the $ORACLE_HOME/bin/frmcmp_batch.sh script. Replace the line TNS_ADMIN=$ORACLE_HOME/network/admin with TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}.

This error is typically due to the TNS_ADMIN variable being incorrectly set in the forms compilation script, preventing it from finding your tnsnames.ora file.

If the user provides a value, Blitz Report inserts the parameter’s WHERE clause immediately before the `1=1` anchor, making it part of the complete WHERE clause. If no value is provided, the anchor remains intact (`WHERE 1=1 AND…`), ensuring the query executes efficiently without filtering.

The mandatory parameter is ‘Cost Type’ (Frozen or Pending).

The `n=n` (e.g., `1=1`) anchor allows unused parameters to be dynamically dropped at run-time. If a user does not enter a value for a parameter, the associated WHERE clause is omitted entirely from the generated SQL, preventing unnecessary parsing and maintaining efficient execution plans.

The DBA SGA Memory Allocation report provides the current SGA memory usage in gigabytes, specifically showing the split between the buffer cache and the shared pool.

That scenario is covered by ‘Based on Rollup No – With BOMS’, which finds make items not set for rollup but where BOMs or routings exist.

The advanced required parameter logic is managed directly within the Blitz Report Setup form, accessible via the ‘Setup’ button on the run window, provided your user profile is set to ‘Developer’ or ‘System’ access . You access this through the ‘Required’ button (which changes to ‘Advanced’ once configured) within the parameter definition section of the report .

There are twelve included reports. Examples include: ‘Based on Rollup Yes – No BOMS’ (finds make items set for rollup but missing BOMs, potentially rolling up to zero cost) and ‘Based on Rollup Yes – Buy Items’ (finds buy items set to be rolled up).

No, only one advanced logical expression can be set up per report . Once an advanced expression is defined, the standard ‘Required’ checkbox becomes visually labeled as ‘Advanced’ to indicate that a complex validation rule is in effect . This single expression must encompass all necessary validation logic for that report.

Run the DBA SGA Buffer Cache Object Usage report. This report shows SGA buffer cache space usage broken down by object names in megabytes.

You need the CAC Cost Rollup Controls Validation report. This report compares item make/buy controls versus costing based on rollup controls to find errors in your cost rollup results.

If the logical expression is not met, Blitz Report displays a default error message . For expressions enforcing at least one parameter entry (like your ‘either-or’ scenario), the default message text is stored in the FND message `XXEN_REPORT_ONE_PARAM_REQUIRED` . You can customize the displayed error message by entering your preferred text directly into the required message field when defining the logical expression .

Yes, this feature allows running BI Publisher report SQLs that rely on PLSQL code to populate data into global temporary tables prior to execution.

An Anchor is a placeholder in the report SQL where dynamic SQL (like a parameter’s WHERE clause) can be inserted at runtime, such as the `1=1` anchor.

In the advanced logical expression, parameters must be referenced by their name (in the installed base language, usually US), prefixed with a colon (`:`) . Any spaces or other non-word characters within the parameter name must be replaced with a single underscore (`_`) . For instance, ‘Customer Name’ becomes `:Customer_Name` .

The setup requires elevated access permissions. The assumption is that the Blitz Report developer responsible for configuration must have Unix and System Administrator access in order to perform the required setup for the postprocessing procedure.

You must run the Blitz Report Parameter Anchor Validation report. This report checks if all parameter anchors exist in the `xxen_report_parameter_anchors` table.

Yes, Blitz Report supports the generation of PDF output. This functionality is achieved using the postprocessing capability available within the Blitz Report framework, allowing the conversion of the primary output file type (typically Excel) into a PDF file.

Blitz Report fundamentally addresses this problem by operating independently of these BI Publisher restrictions. It generates perfectly formatted Excel or CSV files and explicitly states that it has no volume limitations. Whether you need to process 50,000 records or 5 million records, Blitz Report is designed to handle the data output efficiently, thereby bypassing the obsolete 65,536 row constraint.

The Copy Report functionality creates a new definition but does not copy assignments or category assignments. You will need to manually re-assign the new custom report to users or responsibilities.

Yes, this functionality is a powerful addition to the Oracle EBS DBA toolkit. It allows them to quickly execute and save a custom report using the SQL that queries session information, enhancing system security monitoring without having to access the database command line.

Although the documentation does not specify the exact UI location, in principle, ECC datasets are managed through the Command Center configuration interface, which you can access via the ‘ECC Developer’ responsibility , . The dataset key (or equivalent identifier) is needed for the `XXEN_API.IMPORT_ECC_DATASET` API .

You must use the Copy Report feature, found under Setup > Tools. This creates a new, distinct copy of the report that you can safely modify.

The Blitz Report User History report is used for this analysis. It lists all active EBS users with their active responsibilities and Blitz Report execution counts, helping analyze usage within the EBS community.

If `adop fs_clone` is stuck , the DBA should first query `apps.fnd_nodes` to confirm critical service and node configurations are correct and aligned with the patching environment.

No, seeded reports should not be modified. If you change them, those updates will be removed as soon as a new version of Blitz Report is installed.

The workflow is designed for automation. Once the initial steps were completed to set up the report with the map, the map visualization will be refreshed automatically upon the subsequent report runs. This creates a constantly updated security monitoring dashboard right within the familiar Excel interface.

Yes, the example script `mass_import_ecc_reports.sql` is provided to automatically import all available ECC queries into Blitz Report . This simplifies the process, ensuring all underlying data models that power the ECC dashboards are available for detailed reporting through Blitz Report .

While the base security model remains centered on EBS privileges and VPD enforcement , every ECC upgrade (V4, V5, V6, etc.) may introduce new functional security requirements. Essential environmental security includes ensuring all communication is secured by Configuring TLS for Oracle Enterprise Command Center Framework.

ECC dataset queries can be imported using the menu option under Blitz Report Setup > Tools > Import . For mass imports, you should use the PL/SQL API: `XXEN_API.IMPORT_ECC_DATASET`, which takes the `p_dataset_key` as an input parameter . The key benefit here is that once imported, users can access ECC data of unlimited size and in real-time directly within Excel .

Yes, separate configuration documents are needed for older versions. Specific posts detail the required steps for Configuring mod_plsql in EBS 11i and Configuring mod_plsql in EBS 12.1.3. The configuration steps reflect the architectural differences in the Apache web server across EBS releases.

Blitz Report acts as the execution layer, passing the standard EBS user context to the database. Since the VPD policy is linked directly to the underlying table and the database user context, Blitz Report configuration simply needs to ensure the custom SQL targets the correct table. The security is then transparently enforced by Oracle itself.

This is an excellent application of Blitz Report’s visualization capabilities. You start by running a custom Blitz Report designed to find the IP address and inferred geolocation of client logins by querying the relevant EBS tables. This report is functional for Oracle E-Business Suite version 12.2.10 and higher.

Yes, Blitz Report supports Oracle Enterprise Command Center administration and enriched dashboard data export to Excel. This includes the ability to extract data sets and metadata, which is crucial for auditing and confirming configurations post-upgrade.