Support

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

You must execute `alter trigger apps.note_1342126_1_audit_trig disable;`, rerun the `install.sh` script, and then re-enable it afterwards using `alter trigger apps.note_1342126_1_audit_trig enable;`.

Hi,

For audit purposes like this, we can generate Blitz Report in pdf format using third party tools, such as libreoffice (license free), but this would require an installation and configuration of that tool on the server side, as explained in the following blog:
https://www.enginatics.com/blog/blitz-report/generate-pdf-blitz-report/

Hi,

Oracle EBS Forms unfortunately has a limitation to a maximum of 32k characters, and this SQL is larger.
To edit such large SQLs, you can double-click on the sql text to download it, modify, and then upload the large SQL again.

Regards,
Andy

Hi,

1) Does it show ‘LOV FRM-41830 List of values contains no entries?
2) Does it happen in other instances after the Blitz Upgrade?
3) Could you please ask your DBA to send the upgrade log files zip?

Regards,
Alex

Hi,

To schedule reports, you would need to have the Blitz Report concurrent program assigned to the request group of your current responsibility.
This can be done either manually for individual request groups, or you can use the recommended method and run the Blitz Report Update Menu Entries concurrent program to automatically add the Blitz Report function and concurrent program to all active responsibilities.
If you would like to make Blitz Report only available for a limited number of users, you can control the Blitz Report usage through the Blitz Report Access profile option.

Thanks and regards,
Andy

Hi,

I’m not sure if I fully understood your first question, but I think the answer is yes, you can re-use an existing file that you have previously saved on your computer for multiple uploads.
The upload code identifies the created or changed rows based on the first Action column in the spreadsheet, which needs to show either Create or Update for the records to be processed.

And the Autofill button would trigger the dependency validation and population for all rows, even after copying and pasting records. Such validations would usually only be executed when entering a single record manually.
If you do a PO Requisition creation, for example, you could copy and paste a list of inventory item numbers into the Item field and click on the Autofill button to populate the dependent fields

Let me know if you would like to schedule a quick call to review the functionality together.

Regards,
Andy

Hi,

You don’t need to change the SQL, and the users could even select or re-order the columns themselves by creating their own templates.
With Developer access, you could also create a template and define it as default for all users:

Let me know if that works for you, or we can have a quick call to review it together.
And we are still working on the performance fix for this upload btw..

Regards,
Andy

We have enhanced our installation script as discussed, so that it would no longer update the Blitz Report Access profile option setup during upgrades.
If you uncheck the Updatable flag on Site level, this change would be persistent next time you will apply an upgrade.

Regards,
Andy

Hi Richard

You may need to set the Blitz Report Access profile option to the ‘System’ for your and other EBS super users.

It should not be required to disable uploads additionally as they are not available for users by default.
Please refer to the following developer guide section.

“The upload functionality has additional security and the Upload button is inactive by default even for developers. To upload data, users or developers require assignments created by someone having the Blitz Report Access profile option set to the highest level ‘System’. Only users users with System access can modify and or run any of the uploads, or create assignments for them. Unlike reports, Enginatics does not provide seeded assignments for uploads, and customers would need to assign the uploads as required.
Users with access profile set to ‘User Admin’, ‘Developer’ or ‘System’ can access all reports in the system, irrespective of report assignments, and can run them, depending on report type and access profile as shown above. Uploads can only be done if there are assignments for them, or by users with an access profile of ‘System’.”

Regards,
Alex

This specific trigger, often created during an investigation (per Oracle note 1342126.1), is prematurely referencing the sequence’s current value (`CURRVAL`) before it has been initialized in the current session. This trigger should ideally be removed after the investigation, but if still required, it must be temporarily disabled.

That is absolutely right. For users on EBS 12.2 and later, Oracle recommends migrating from the Java Plug-In to the Java Web Start (JWS) technology. This shift allows Forms to run in browsers that have ended support for the older Netscape Plug-in API and ensures stability, which is vital for Forms-based tools like Blitz Report.

Hi,

Can you please let the user know to update the excel trust center settings explained in the link below?

https://www.enginatics.com/blitz-report-developer-guide/#excel_trust_center

Thanks and Kind Regards,
Piyush Khandelwal

Hi,

This error shows up as your 3.2.5 Blitz Report version does not work with the new FSG report yet.
To use this new functionality, we would need to upgrade to the latest Blitz Report code version first.
Would you request this from the Clarmont/DSP team, or how would the upgrade process work?

Regards,
Andy

Hi,

Yes, you can either hide the Parameters tab in Excel, or completely delete it, and then upload the Excel file as a template and the generated file would also have the tab hidden or removed.

Regards,
Andy

We can not use the conc manager incompatibility on program level, as every blitz report runs under the same concurrent program name.

We could however achieve incompatibility on report level by creating a concurrent manager for one specific blitz report only with only one process and then using the Request Type to run that report only on the new single process manager.

What would be the reason to prevent users from running the same report in parallel?

It would be good to learn from your requirement as reports are usually read only and it would not harm running them in parallel (other than possible performance impact).

Unfortunately, the current Blitz Report version does not have this functionality yet.

We have had this on our todo list for a while already and will definitely build it in the future, but as there are many code dependencies, it is not a quick development.

The only possibility to create different worksheets with Blitz Report right now would be using the Sheet Break functionality on the Template screen.

So as a workaround for now, you might be able to use a union all query and break up the data by a column value, but this has the limitation that the column names would need to be the same across the different datasets.

Regards,

Andy

Thank you for noticing this.

We’ll investigate and get back to you with the results.

I have extended the “INV Material Account Distribution Detail” Blitz report to include the SLA Account and Account Description and SLA Entered/Accounted amounts. The updated version can be downloaded from the Enginatics library (https://www.enginatics.com/reports/inv-material-account-distribution-detail/) and imported into your instances.

Due to resource constraints, we will review and update any additional reports on a customer driven basis so we can prioritize our workload. Please let me know if you come across any other reports that are causing immediate concerns and I will add them to my task list to modify.

This issue happens when a patch overwrites our customizations in FND_WEBFILE or FND_WEBFILEPUB.

If a customer is reluctant to upgrade Blitz in most cases it may be enough to rerun install.sh from the already downloaded older Blitz installation pack.

However sometimes new versions of the packages are included in the patches, so we add them to the latest Blitz releases.

So when you analyze the patch impact, you may want to check if the patch delivers AFCPFILB.pls and AFCPWFPB.pls.

Thank you,

Alex

The centralization within Blitz Report helps tremendously. It is much more convenient to maintain your reports in Blitz Report because it allows you to provide a detailed description, ownership information, and critically, it offers version control. Every alteration to the SQL logic is tracked automatically.

I asked my colleagues, and they confirmed that the VBA code which we use for the Blitz upload functionality would not work in the online Excel version.

I remember that your company looked at Blitz Report around 4 years ago and we have introduced a lot of functionality meanwhile that could be interesting for you.

Regards,

Andy

Is it possible for you to try searching from System Administrator > Concurrent > Requests?

Thank you,

Alex

I just had a quick look and the error is due to our code not considering different flexfield contexts correctly.

The correction is a small change, but we would need to provide an update to the xxem_msc package, which we will include in a new Blitz Report deployment file.

The creation of a new deployment file will probably take until Monday, as there are dependencies.

You can confirm that this would resolve the problem by removing the default ‘Yes’ from the ‘Show Item Descriptive Attributes’ parameter in attached report.

Not sure if you saw my chat message: To run, modify or assign the uploads, you would need to have your Blitz Report Access profile option set to ‘System’ instead of ‘Developer’

We use this for additional security, as you might not want to give full access to the upload functionality to all your developers.

Precisely. You eliminate the need for complicated XML formatting and the technical hurdles associated with forcing BI Publisher templates to generate XLSX output. You simply define the required SQL, and Blitz Report outputs the perfectly formatted data directly to Excel.

Yes, these AWR reports are generally compatible with PDBs. You typically need to ensure AWR autoflush is enabled within the PDB by executing: `alter session set container=PDB1;` followed by `alter system set awr_pdb_autoflush_enabled=true;`.

You can use the ‘Session Type’ parameter to restrict the output specifically to foreground, background, or all server processes. This helps focus the analysis on user-facing bottlenecks.

If the user does not enter a value for the parameter, none of the associated conditional SQL texts with matching values will be inserted into the extraction SQL . The primary mechanism for dynamic SQL, whether using the `n=n` or `&lexical` anchor, ensures that if a parameter value is left blank, the corresponding reference (or clause) is removed before SQL execution . This maintains query efficiency by preventing the execution of unnecessary conditional logic.

The default warning period is 14 days.

The seeded report ‘FND Concurrent Requests’ serves as an excellent reference, as it explicitly uses the Matching Value functionality to insert different WHERE clauses for parameters like ‘Phase’ and ‘Status’ . It dynamically selects the most appropriate SQL text to achieve better performance based on the specific parameter value provided by the user at runtime .

Yes, the Matching Value field supports the use of wildcard characters . If you use wildcards and the user’s entered parameter value matches multiple defined matching values for the same anchor, Blitz Report applies a rule of precedence. It inserts the SQL text associated with the best match, which is defined as the matching value entry with the longest string length .

Yes, this setup requires multiple entries for the same parameter name, each with a different matching value or anchor . To manage the display on the run window, only one of those entries should have a defined Display Sequence, Parameter Type, and List of Values (LOV) setup . The other entries, used purely for defining conditional SQL injection via matching values, should have their display sequence left blank .

Since Blitz Report maintains full version control and an audit trail of the report’s SQL definition within the EBS instance , sharing and collaborating on the underlying logic becomes straightforward and traceable.

You can achieve this conditional logic efficiently using the Matching Value feature within the parameter definition . You would create two separate entries for the ‘Process Type’ parameter name: one entry defined with a Matching Value of ‘ORDER’ and its corresponding SQL text, and a second entry with a Matching Value of ‘RETURN’ and its corresponding, distinct SQL text. Blitz Report’s runtime SQL generation logic ensures that only the SQL text associated with the matching value entered by the user is dynamically inserted into the main report SQL .

The migration process can be simplified. Blitz Report is positioned as the primary Oracle Discoverer replacement, offering automated migration of worksheets , allowing them to benefit from the direct access to the ECC data model via optimized SQL.

The DBA toolkit includes specialized reports for Database Health and Tuning. Specifically, access to updated AWR reports is critical for diagnosing performance regressions in multitenant environments post-upgrade.

Run the DIS Discoverer and Blitz Report Users report. It tracks user adoption by showing the monthly execution counts of Discoverer worksheets and Blitz Reports per user.

When consolidating via ‘Discoverer Folders’, the different workbooks and their respective selected columns are converted into Blitz Report templates associated with the consolidated report . If a folder combination was used by just one worksheet, the imported Blitz Report name will be ‘Workbook Name: Sheet Name’ to aid recognition .

The report leverages an active trigger function, `eul_trigger$post_save_document`, which writes each worksheet’s SQL query to the table `ams_discoverer_sql`.

Use the DIS Worksheet SQLs report. This report retrieves Discoverer worksheet SQL queries.

If the report runs in XLSX output format, Blitz Report automatically removes the =” and ” characters from the data, ensuring the data displays correctly without the formatting characters.

Yes, the Offset parameter allows you to retrieve future or past periods by specifying a positive or negative numerical offset value. A negative offset retrieves past periods, such as -1 for the previous period.

The period names returned are Ledger-specific, meaning they follow the calendar of the selected ledger.

You can quickly download and review the data definition XML template . This is achieved by double-clicking onto the BIP Code field within the Blitz Report setup window , . This action initiates a download of the associated XML file, allowing you to confirm the `dataTrigger` section logic .

You should use the function `br_period_from_date`. This function returns the accounting period name corresponding to the specified date.

You can use the Blitz Report functionality developed for DBAs to run custom queries utilizing AD_PATCH.IS_PATCH_APPLIED directly from EBS forms, providing quick verification of patch status related to any compatibility fixes.

Yes, Blitz Report fully supports leveraging this logic using the BIP Code field in the report header . When you populate this field with the BI Publisher data definition code, Blitz Report is configured to execute the dataTrigger section (e.g., `beforeReportTrigger`) of the associated data definition XML template . This allows the GTT to be populated by the pre-processing logic, and your Blitz Report SQL can then extract the data directly from the GTT .

You can restrict the query to records modified since the previous scheduled request run by using a specific parameter SQL logic that references the concurrent request history. An example uses the request’s actual start date from the previous run.

This lack of compatibility emphasizes the urgency of finding a reliable replacement. Blitz Report is positioned as the primary Oracle Discoverer replacement, offering fully automated migration features to quickly convert your existing reports, thereby eliminating dependencies on deprecated tools and ensuring continuous reporting capabilities.

The compatibility of older tools like Discoverer 11g with the security and network changes introduced in Oracle Database 19c is problematic. The error ‘No matching authentication protocol’ strongly suggests that the older client libraries or authentication methods used by Discoverer 11.1.1.7 are no longer compatible or enabled by default in your 19c database instance.

Yes, if the time limit feature is not used, a longer schedule, such as daily, can be set up. This still ensures the other essential cleanup and administrative actions are performed.

Yes, it performs several critical cleanup tasks. These include marking terminated or error report runs as *complete*, purging outdated log data and SQL history, and removing inactive users from the Blitz Report license user table.

You can use the profile option ‘Blitz Report Email Attachment Size Limit (bytes)’. This sets the maximum attachment size for Blitz Reports sent via email.

This is a known database bug, Oracle bug 25203656, impacting 12.1.0.2. You can resolve the issue either by applying the corresponding patch 25203656, or by setting a database parameter as a workaround.

You must ensure JWS is enabled and properly configured for your 12.2 instance. If forms are not launching, confirm the value of the `ICX: Forms Launcher` system profile and verify the configuration of the EBS nodes by querying `apps.fnd_nodes`.

The Polaris RWB import API, `IMPORT_REPORTING_WORKBENCH`, includes the parameter `p_expand_view_sqls` . This parameter accepts values like ‘none’, ‘all’, or ‘custom’ . Setting it to ‘custom’ ensures expansion only for views starting with `XX%` or custom application short names . Views referencing Polaris RWB objects starting with `XXRX%` will be expanded regardless of this setting .

Yes, you can configure the profile option ‘Blitz Report Row Limit’. This sets the default limit for the maximum number of rows returned by Blitz Report if it is not set up on the individual report level.

Yes, the Polaris Reporting Workbench import process is designed to consolidate reports based on the underlying database views . If multiple RWB reports are based on the same views, they are consolidated into a single Blitz Report . The RWB report-specific column selections are then imported as individual Blitz Report templates associated with the consolidated report .

Yes, custom BI Publisher reports are imported using the PL/SQL procedure `XXEN_API.IMPORT_CONCURRENT_PROGRAM` . This function requires the `p_application_short_name` and `p_concurrent_program_name` as parameters . You can use the example script `mass_import_bi_publisher_reports.sql` to import all custom BI Publisher reports where the data source starts with `XX%` . This same `IMPORT_CONCURRENT_PROGRAM` API is also used for migrating Excel4apps Reports Wand reports .

In NOARCHIVELOG mode, the DBA Archive / Redo Log Rate report calculates the approximate redo rate based on the number of log switches per hour and the log file size.

You must confirm that your ECC environment is properly secured and configured for HTTPS/TLS communication. Errors related to common name invalidity (`ERR_CERT_COMMON_NAME_INVALID`) or general access issues indicate a configuration problem with the SSL certificates or the WebLogic ports (e.g., `ECC_MANAGED_SSL_PORT`).

Yes, utilize a rapid verification method by creating a Blitz Report query based on the AD_PATCH.IS_PATCH_APPLIED database function. This allows the DBA to specify the bug number, application top ID, and language to quickly confirm the ‘APPLIED’ status.

While Blitz Report supports standard bind parameters similar to other reporting solutions, using anchors for dynamic SQL is generally recommended to avoid performance issues associated with coding conditional logic like `nvl(:bind_variable, column_name)` for optional inputs. If you do use simple bind variables, be aware that certain words are reserved by Oracle and cannot be used as bind variable names; you can find a list of these reserved words by querying `v$reserved_words` where `reserved = ‘Y’` or `res_semi = ‘Y’`.

ECC upgrades require meticulous attention to prerequisite patches. You must reference the specific list of required patches provided in the V9 documentation. For example, the upgrade notes might reference critical patches like `34215413` related to the Supply Chain Management (SCM) online help.

The primary limitation of the `n=n` anchor is that it can only be used for injecting additional `WHERE` clauses, because the syntax `1=1` must remain in the run-time SQL. In contrast, the `&lexical` anchor offers much greater flexibility, capable of adding any required SQL snippet, such as dynamic tables, `ORDER BY` clauses, or even full subselects, making it suitable for structural changes beyond just filtering.

Use the PA Project Budget report. This report focuses on Standard Project Budgets and has been extended to display the actuals matching the budget line data points.

Blitz Report intelligently manages this process: it only inserts the parameterized `WHERE` clause into the main extraction SQL at runtime if the user actually enters a value for that specific parameter. If the user provides a value, the corresponding `WHERE` clause is injected at the position of the `1=1` anchor. If no value is provided, the original `where 1=1` clause remains, and no additional filtering is applied, ensuring high performance.

The recommended method for handling optional parameters in `WHERE` clauses, specifically to avoid potential performance problems associated with coding like `nvl(:bind_variable, column_name)`, is to use the `n=n` anchor. Your main report SQL should include the clause `where 1 = 1` which serves as the anchor point. The parameter setup then defines the SQL text for the restriction (e.g., `upper(hp.party_name) like upper(:customer_name)`) and specifies the `n=n` anchor.

If you enter variations that do not match Oracle’s format (like ‘JAN-2007’ instead of ‘Jan-07’), it will result in no data being returned.

You configure the submission of the standard Oracle import concurrent request using the Post Procedure feature . Under the Upload setup tab, you define a post procedure that is executed after the primary upload processing is complete, typically responsible for submitting the subsequent concurrent request that consumes the data from the interface table , .

For API based uploads, the SQL requirements are slightly simpler, requiring only the first three columns . The SQL must contain `action_`, `status_`, and `message_` columns in the first three positions . The format is typically `null action_, null status_, null message_` . The `row_id_` column is not mandatory in this scenario .

The `row_id_` column must explicitly identify the row in the underlying interface table . You derive it using the syntax: `

For Interface Table based uploads, your main extraction SQL is required to contain four specific columns in the first four positions , . These columns must be: `action_`, `status_`, `message_`, and `row_id_` , . You typically initialize these columns with `null` values, for example: `null action_, null status_, null message_,

Prerequisites include using Oracle database 19c or higher, Active Data Guard licensing, and configuring DML Redirection.

You use the profile option ‘Blitz Report Target Database’. This allows specifying a standby database for report execution.

Absolutely. Blitz Report is part of the project implementation and upgrade toolkit. It allows consulting and support teams to run quick validation reports, leveraging the capability to mass export volume data from the ECC data sets to Excel for comparison and integrity checks.

The result is a string showing the number of days, hours, minutes, and seconds. For example, 361,012 seconds converts to ‘4d 4h 16m 52s’.

Yes, you should use the function `XXEN_UTIL.TIME(p_seconds in number)`. It takes the number of seconds as input.

Yes, the multiple values functionality is only available for parameters using anchor styles `1=1` or `&lexical`, not for `:bind` anchors.

You use the profile option ‘Blitz Report XLSX Orientation’. This sets the page layout orientation for Blitz Report XLSX output files.

Use the Blitz Report Parameter Anchor Validation report. It checks if all parameter anchors exist in the `xxen_report_parameter_anchors` table, ensuring correct linkage.

That limitation is explicitly overcome by Blitz Report. The system has no volume limitations , making it ideal for mass exporting volume data like full Payables ledger details, a task categorized under the Data Management component of our toolkit.

Blitz Report supports reporting across external data sources. Provided you maintain or establish the necessary Oracle Database Gateways or database links (for sources like Vertica, MySQL) , your reports migrating from Discoverer can continue leveraging this cross-database connectivity.

The default setting is ‘No’.

Yes, consultants can utilize their existing SQL scripts immediately. They simply drop them directly into the Blitz Report form, eliminating the need for registering new concurrent programs and initiating version control automatically.

Yes, you can use the profile option ‘Blitz Report Discoverer Import Literals as Binds’. When set to ‘Yes’, Blitz Report automatically replaces literals with binds during Discoverer import.

The tool allows you to quickly convert and fast-track Oracle BI Publisher report development. Developers essentially transfer the core SQL data logic from the XML Data Definition into a Blitz Report, rapidly achieving perfectly formatted Excel output without wrestling with BI Publisher templates.

The report parameters are highly granular, designed specifically to pinpoint problematic requests. You can filter based on status (e.g., `* Error;Warning, etc`), phase (e.g., `Completed, etc`), or execution time (e.g., `Running longer than x Minutes` or `Waiting for x Minutes`). Furthermore, you can include detailed metadata like the `Execution Method` or narrow down the selection by `Concurrent Program Short Name`.

You control this using the `p_expand_custom_view_sqls` parameter. Options include ‘All’ (for full expansion), ‘Custom’ (for views starting with XX% or custom application short names), or ‘none’.

You must connect as APPS and execute `drop package XXEN_UTIL;`, followed by running the package specification and body scripts (`@XXEN_UTIL.pks` and `@XXEN_UTIL.pkb`) from the installer’s SQL directory.

Yes, you use the PLSQL procedure **`xxen_api.import_discoverer_folders`**. This option consolidates different workbooks that access the same folders into single Blitz Reports.

Access control is built-in. Reports can be assigned to a specific user, module, site, or responsibility. Furthermore, report output files respect the standard Oracle Virtual Private Database (VPD) security policies to protect sensitive financial data.

No. One of the primary benefits is agility. Blitz Report allows consultants with their favorite SQL scripts to drop them directly into the tool and start generating reports immediately, avoiding the lengthy process of registering new concurrent programs.

New reports can be created extremely quickly. For instance, Blitz Report is a dedicated reporting solution for Oracle EBS Cost Accounting. A developer can create a perfectly formatted Excel report based on a simple SQL query, complete with parameters and version control, often in under 10 minutes.

If you have configured the EBS Audit capability to track changes to critical fields like the promise date (setup parameters), Blitz Report can report on those changes. It allows rapid generation of comprehensive reports showing who changed what and when, critical for maintaining data integrity and speeding up operations.

You can modify this setting via Tools > LOVs, where the LOV is defined, or if it is a custom LOV, within the parameter definition itself.

Blitz Report is designed to work seamlessly with the technical output of the EBS audit function. It allows Master Data Maintenance (MDM) teams and support consultants to run complex SQL queries against the audit tables easily, presenting the changes in a clear, formatted Excel file.

When checked, ‘Filter Before Display’ prompts the user to enter a partial value *before* the LOV attempts to display, forcing the form to query only a restricted dataset, thereby avoiding the slow initial load time.