Support
Discussion Replies Created
That is correct. Blitz Report functions as a dedicated tool for Oracle Enterprise Command Center administration and enriched data export to Excel, ensuring that DBAs and support consultants can reliably manage and extract all underlying data sets for comprehensive analysis.
You only need to bounce the concurrent managers for them to pick up the corrected binary and resume generating output files.
Run the GL Code Combinations report. This report has a parameter specifically designed for this purpose: ‘Show Misclassified Accounts’.
Yes, Blitz Report can export the underlying, enriched data from the ECC charts and metrics. By leveraging the ECC SQL (or the underlying query logic for your extended dashboards) within a Blitz Report definition, you can export the full data set to Excel, overcoming the volume limitations often associated with native ECC exports.
You must relink the FND binary. Log in as the application owner and execute the command: `adrelink.sh force=y ranlib=n “FND fndcpesr”`.
While creating a new dashboard is possible based on custom datasets, incorporating complex OAF page chart logic directly requires adherence to the ECC data definition structure. However, the foundational data utilized by both the OAF page and the custom ECC dataset would be extracted via similar means.
This is a classic sign that the FND binary responsible for output generation, `$FND_TOP/bin/fndcpesr`, is corrupted or zero bytes, likely following system maintenance. This corruption prevents the output file from being created.
Yes, it is possible to extend existing ECC dashboards with additional data. You can refer to Oracle’s documentation on extending Oracle Enterprise Command Centers for guidance on adding data. Furthermore, it is also possible to create a complete new dashboard entirely based on a custom dataset tailored to your requirements.
The output can be generated to CSV or other file types suitable for direct importing to analytical tools like Tableau or Microsoft Power BI, in addition to native Excel output.
Yes, absolutely. This report fits perfectly into the Blitz Report Toolkit framework, specifically under Operational reports or Support and Data Migration reports. It allows consulting teams to quickly validate data integrity across Install Base and Inventory post-upgrade.
When you copy a report using the ‘Copy Report’ function, the parameter definitions, including the advanced required parameter logic and the parameter SQL text, are copied to the new report . This ensures the stringent validation rules remain in place for the new version .
Yes, you can customize the error message . If you enter a specific message text when setting up the advanced required parameter, that text will be displayed if the logical expression is not met . If no specific message is provided, the system defaults to the FND message `XXEN_REPORT_INSUFFICIENT_PARAM` .
All Blitz Report definitions, including those for complex Asset Tracking SQLs, benefit from full version control and audit history. This ensures that any changes made to the logic for addressing pending transactions are tracked, preventing version challenges and allowing for easy rollback if needed.
Hi,
Thank you for this idea. We discussed with the development team and think that we can introduce such a functionality to provide more flexibility for the users.
This would have certain limitations however, for example not allow the use of value sets for such user defined parameters or conditions.
We will add this to our development list, but cannot give an ETA yet.
We will keep you posted on our progress.
Regards,
Andy
For analysis based on the Work Breakdown Structure (WBS), use the PA Revenue, Cost, Budgets by Work Breakdown Structure report.
Report deployment is immediate. Once the query is developed and saved in Blitz Report, it can be assigned to the relevant user responsibilities or integrated via the Zoom function into an SCM form. This allows the operational team to execute the report instantly, running through the concurrent request mechanism , and receiving the Excel output immediately.
Yes, this Blitz Report has been explicitly extended to pull in additional data points as displayed in the Project Status Inquiry Form.
When referencing parameters in the advanced expression, you must use their name (in the base language, usually US) . This name must be prefixed with a colon (`:`) . Crucially, any spaces or other non-word characters within the parameter name must be replaced with a single underscore (`_`) . For instance, ‘Customer Name’ must be referenced as `:Customer_Name` .
This type of cross-module reporting, particularly linking Install Base and Inventory data for asset tracking, is highly streamlined using Blitz Report. Since Blitz Report uses pure SQL, you can write joins across the necessary SCM tables in Install Base and Inventory to create a comprehensive report that addresses issues like Oracle Asset Tracking Pending Transactions (Doc ID 2423449.1).
Hi,
Looks like Andy had started to reply to your email, but had been side-tracked.
I have updated the report so Days Past Due Low/High and the Balance Due Low/High parameters are now working correctly.
And the error message that you see when opening is due to the default value using the xxen_util.previous_parameter_value function, which does not exist yet in your older Blitz Report version.
So for the time being I have attached a version of the report you can import into Blitz Report which does not reference these newer functions.
Kind Regards,
Eric
You can define this complex requirement by combining your conditions with `AND` and `OR` operators within the logical expression . Assuming your parameters are named ‘Supplier ID’, ‘Supplier Name’, and ‘Supplier Site’, your expression should look like this: `:Supplier_ID is not null or (:Supplier_Name is not null and :Supplier_Site is not null)` . The use of parentheses is important here to group the AND condition correctly .
The ‘Report Level’ parameter controls this. Setting it to ‘Project’ is equivalent to the Project Level report, while setting it to ‘Task’ is equivalent to the Task Level report.
Hi,
If you have Developer access for Blitz Report, you can download the XML definition and import it yourself from the setup window menu > Tools > Import > XML Upload.
It would not harm updating Blitz Report to the latest version thought by the DBAs, as we keep on enhancing the tool and introducing new functionality.
Let me know if the import works for you. The missing restriction was this one btw.: apsa.due_date<=:p_as_of_date.
Regards,
Andy
You should use the PA Revenue, Cost, Budgets by Resources report. It implements the standard Oracle reports ‘MGT: Task – Revenue, Cost, Budgets by Resources’ and ‘MGT: Revenue, Cost, Budgets by Resources (Project Level)’.
Thanks for spotting this.
I’m surprised that we did not recognize this earlier, as I am showing this report in every product demo.
Please download and import the corrected AR Past Due Invoice report and let me know if it resolves the issue.
Thanks and regards,
Andy
Yes, Developers can create, modify, or delete categories and column translations.
This report is built to allow analysis by those attributes, typically leveraging the pivot aggregation layout templates functionality of Blitz Report.
Developers typically have their access profile set at the user level, which allows them to access all reports and the setup window from all login responsibilities.
Yes, there is a technical note on this: To run the report including non-costed items, the ‘As of Date’ parameter must be left blank (current date). The report cannot be run historically when including non-costed items due to a bug in the Oracle API used to populate the costing tables.
They have full access to create, modify, and delete reports of type ‘Standard’. However, they have full access, except uploads, system, and protected reports.
Yes, it corresponds to the standard Oracle reports: ‘Elemental Inventory Value Report’ and ‘All Inventories Value Report’. Templates are provided that match the existing standard Oracle report formats.
You should set the ‘Blitz Report Access’ profile option to ‘Developer’. This is the required setting for users with the SQL skills necessary for creating Blitz Reports.
You should use the CST Inventory Value – Multi-Organization (Item Costs) report. This report can be used to report inventory value by Elemental Item Cost level and Quantity Type.
They should rely on the Concurrent Request Monitoring and Alert Reporting tool. This provides the ability to filter requests running longer than an expected timeframe and extract the active SQL text for immediate performance tuning analysis.
No, using this method secures data access only through the Blitz Report concurrent program.
Yes, the inclusion of the user description can be deactivated globally by setting the profile option ‘Blitz Report Show User Description’ to ‘No’.
The financial reporting capabilities of Blitz Report support complex reports like GL Account Analysis and Simple And Effective Cost Accounting Reporting. Running pre-saved comparison reports ensures you quickly ‘ungarble’ the post-upgrade financial data to verify YTD totals and hierarchical structures.
The default setting is ‘No access’.
You should set this profile option to ‘Full access’ for responsibilities or users who should have access to run Blitz reports on secured data.
Data security is maintained by enforcing Oracle VPD security policies at the database level. Additionally, for ECC, ensuring that your environment is running securely over HTTPS/TLS is critical for protecting data transmission during administration and use.
Hi,
We understand that it is costly going through a full test cycle for smaller bug fixes like this.
In case customers find bugs, we resolve them and make the corrected code immediately available for download on our website, to prevent other customers encountering the same issue again.
Such smaller bugfix releases are showing the date of the code as a subversion on our download page:
When we do major functionality enhancements, we release those as new versions, listing the new functionality, and all included bug fixes up to that date on our changelog page.
In case of this specific multiple values problem, the bug has always been in our code and was just not spotted before.
If you would want to avoid the effort of upgrading Blitz Report to the latest code version, you could instead apply a workaround for this problem, which would be removing the problematic Advanced Required Parameters condition like this:
The only downside of this approach could be that users might accidentally run the item upload without sufficient parameters, which might take a long time, in case you have many inventory items and organizations.
Let us know if this could work for you,
Thanks and regards,
Andy
The function `XXEN_UTIL.USER_NAME` is overloaded to handle both user name (`p_user_name in varchar2`) and user ID (`p_user_id in pls_integer`) inputs. It converts the input to the full description of the user; for instance, ‘SYSADMIN’ is converted to ‘SYSADMIN (System Administrator)’.
No. Report load scripts and XML files generated by choosing ‘Reports’ contain the current report SQL versions only; they do not include previous version SQL history.
Yes, the report automatically looks for hierarchies that might be used with the Open Period Control and Close Period Control Oracle programs, searching for translated values of ‘Close’, ‘Open’, or ‘Period’ in the Hierarchy Name.
You use the profile option ‘Blitz Report VPD Policy Rule’. This allows setting up access to sensitive data protected through Blitz Report VPD policies.
You can rapidly create these reports by leveraging the validated ECC SQLs. Blitz Report supports developing proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes , ensuring fast deployment of new operational reports.
When you close the inventory accounting period, the Period Close Reconciliation Report creates a very useful month-end summary of inventory quantities and balances. This summarized information can be used to create efficient month-end inventory value reports.
You should use a custom Blitz Report that executes the AD_PATCH.IS_PATCH_APPLIED function. This allows you to quickly query the status of all required bug numbers simultaneously directly from the EBS Forms interface, serving as an immediate patch checklist.
Yes, the export function `XXEN_API.export_file_data` supports historical data extraction by setting the parameter `p_type` to ‘SQL Versions’. When using this type, you can further restrict the versions exported based on their creation date using the parameter `p_creation_date`.
You should use the CAC Inventory Periods Not Closed or Summarized report. This report is designed to identify these exact scenarios.
Yes, assignment by operating unit means the user must have access to the assignment operating unit, either via Oracle’s MOAC or the profile ‘MO: Operating Unit’.
For complex infrastructure changes like an ECC upgrade, utilizing the Blitz Report Project Implementation and Upgrade Toolkit is highly recommended. This toolkit provides necessary diagnostic and data migration reports (like BR100 extracts and Database Health/AWR checks) crucial for pre- and post-upgrade validation.
Many CAC inventory related reports only use inventory org security by default. The default value for this profile is ‘No’.
You set the profile option ‘Blitz Report Use Operating Unit Security’ to ‘Yes’. Setting this profile to ‘Yes’ would restrict the report output by the user’s operating unit access.
If cache clearing fails, you should attempt to reset the `ISGDatasource` from the WebLogic admin console. If the problem persists, running the FND SOA Runtime Error report is recommended for investigation.
You can absolutely use Oracle VPD with Blitz Report to control access to sensitive data at the row or column level. Blitz Report provides several objects to manage this, including the lookup `XXEN_REPORT_VPD_POLICY_TABLES` to define the objects to be secured, and concurrent programs like ‘Blitz Report Update VPD Policies’ to activate the policies. However, remember that VPD policies set up this way only secure access through the Blitz Report concurrent program itself, not through direct database access tools.
The most common and easiest solution is to clear the middle tier cache using the Functional Administrator responsibility.
Yes. If you define an additional output directory, you use the ‘Additional Out. Filename’ option to define the naming convention for those files, again using tokens dynamically.
For maximum flexibility and maintainability, it is actually recommended to use `_all` tables and apply security through parameters. Security is implemented by introducing a required parameter, such as ‘Operating Unit’, with a List of Values (LOV) restricted to only the operating units allowed by the current user’s responsibility. This approach allows the database connection to run without having the application user session context fully initialized, making debugging via tools easier.
The ‘Output Filename’ option only defines the name of the file downloaded to the client desktop.
Yes, you can define a custom Unix shell script to be executed after the report completion, typically for tasks like file distribution or transformation. This is configured via the ‘Custom Postprocess’ option found both at the report level and as a runtime option. The script must reside in the `$CUSTOM_TOP/bin/custom/` directory (e.g., `$XXEN_TOP/bin/custom/generate_and_send_pdf.sh`) and is invoked with several run-time parameters, including the report name, request ID, and the path to the output file.
No, the Run window option time limit takes the highest precedence (1), followed by the profile on the user level (2), and then the report level (3). This global profile acts as a fallback for the responsibility and site levels (4 and 5).
Yes. Blitz Report allows the execution of these sophisticated queries directly from the EBS Forms interface. This eliminates the need for DBAs to log directly into the database or navigate to pages like OAM just to run simple checks, streamlining their operational efficiency.
Certainly. 1. The file name downloaded to the client desktop when you open the report. 2. The output file on the concurrent processing server (in `$APPLCSF/out`), which is also the attachment name for Oracle EBS delivery options. 3. An additional output file placed into a specified directory on either the application or database server.
Blitz Report manages up to three different output files, which can potentially have different names.
The triggers can be used for various data pre- and post-processing activities. For example, the ‘Before report trigger’ can be used for activities such as table data updates that must occur before the extraction SQL is run. Conversely, the ‘After report trigger’ can be utilized for post-execution processing, such as calling standard Oracle PL/SQL code or cleaning up temporary data.
That’s where the integrated version control shines. Every modification to the SQL script is tracked, providing a full audit and version history. This prevents duplication and ensures stability by logging who made which change, making it simple to roll back or audit the query logic.
The default value is ‘no limit’.
You should use the ‘Before report trigger’ functionality, which is configured within the Report Options section. This trigger points to a custom DB Package that contains pre- and post-processing functions. The functions used within this package must follow a specific naming convention: `afterpform`, `beforereport`, and `afterreport`, and they must return the boolean data type. In the specific case of the FA Depreciation Projection report, the Blitz Report references a custom package (e.g., `XXEN_FASPRJ`) that submits and waits for the completion of the standard Depreciation Projection program *before* the main report SQL executes.
You would implement the definitive query, for instance, one based on the `dba_tablespace_usage_metrics` table, directly as a Blitz Report. Once saved, this report becomes the ‘official’ standard. By making it a centrally managed Blitz Report, you ensure all teammates are running the most accurate and up-to-date query logic, overcoming issues caused by obsolete scripts that ignore factors like datafile autoextension.
You set the profile option ‘Blitz Report Time Limit in minutes’. This sets the default maximum execution time limit in minutes if not configured on the report level.
Yes, you can use the FA CIP Cost report. It provides CIP Costs Summary/Detail, equivalent to the standard Oracle CIP reports.
Blitz Report allows DBAs to move away from text documents and establish a centralized, organized repository for all their SQL scripts. This is critical for team consistency. When you create a new report in Blitz Report, it is much more convenient to maintain, as you can provide a detailed description and, crucially, benefit from automatic version control.
For customized summarization across manufacturing metrics like Department, Activity, or Operation, you should use the CST Item Cost Reports suite, which offers multiple options like ‘Element by Department’ or ‘Operation by Activity’.
You should use the CST Detailed Item Cost report. This is a detail report that lists each item and the associated costs recognized as part of the total unit cost of producing the item.
Yes, both the GL Account Analysis (Distributions) and the standard GL Account Analysis report show amounts in both transaction currency and ledger currency.
When you use the ‘Copy Report’ function (Tools > Copy Report) to create a new report version, only the report definition itself is duplicated . Neither the existing Assignments nor the Category assignments are carried over to the new copy . You will need to manually re-establish these links for the copied report .
Yes, developers can use the XLA Distribution Links Summary report. It provides a summary of subledger distribution links to help understand which source IDs are populated for which subledger table sources, referencing relevant MOS documents.
The default assignments are loaded automatically during the first installation and during upgrades if the profile option ‘Blitz Report Load Default Assignments during Upgrades’ is set to ‘Yes’ . To hide specific Enginatics reports during a phased rollout while keeping the default assignments, you can simply disable those reports either manually or by executing a SQL script .
The GL Account Analysis (Distributions) report is the most appropriate. It provides a detailed GL transaction report with one line per distribution, including all segments and subledger data, along with VAT tax codes and rates for AR and AP transactions.
Yes, the DBA SGA Target Advice report shows Oracle’s estimation of how resizing the SGA would affect overall database time and I/O.
It refers to both. The licensing model is attractive , starting with the first 30 reports being completely free to use. Furthermore, the technical architecture results in reduced processing overhead, ensuring incredibly fast performance compared to complex reporting methods.
Yes, the Excel output is highly flexible. For instance, if you extract geographically relevant data, that output can be integrated directly with visualization tools like Excel Bing Maps for map-based analysis and visualization. The structured nature of the data allows for seamless use with other BI tools as well, such as Tableau or Microsoft Power BI.
Yes, the description of this report outlines how to check if HugePages are configured using Linux commands (`grep Huge /proc/meminfo`) and provides guidance on configuring `vm.nr_hugepages`. Remember that only SGA allocation benefits from large/huge pages.
No, that’s a key advantage. Unlike conventional EBS tools like BI Publisher, which can enforce a 65,536 row limit due to older XLS formats , Blitz Report explicitly has no volume limitations on its data output. This ensures your FP&A team can extract comprehensive datasets for complex pivot table analysis.
Yes, you should utilize the Assignment function under Tools . This tool allows you to mass-assign multiple reports to a single assignment level . Additionally, you can use the assignment value LOV within this tool to review all existing assignments efficiently . You can also programmatically manage assignments by exporting and importing them using the Assignments export option .
This secondary restriction is managed by the profile option ‘Blitz Report Restrict Assignments by Operating Unit Level’ . If you set this profile option to ‘Yes’, users require access to the assignment operating unit *in addition* to meeting the requirement for the assignment application or request group to access that particular report . This adds an extra level of control often necessary in multi-org environments .
Utilize the Blitz Report financial toolkit, which includes specialized reports for GL Account Analysis and Balance reporting. By running saved, validated reports pre- and post-upgrade, you can quickly verify that complex data like YTD figures and Parent Totals are accurate in the R12.2.12 environment.
The goal is to configure the SGA and PGA aggregate target to use nearly all the physical memory on your server, leaving a few gigabytes for OS-level caching and process memory. Optimal sizing of the buffer cache and shared pool within the SGA is particularly critical.
Access to individual Blitz Reports for standard users can be precisely controlled using several assignment levels . These levels include Site (all users in the system), Application (users with a matching application via their responsibilities), Request Group (users with a responsibility linked to the assignment request group), Responsibility, and individual User inclusion or exclusion . You can also assign access based on the Operating Unit, where users must have access to the assigned OU via MOAC or the ‘MO: Operating Unit’ profile .
Yes, absolutely. Blitz Report delivers the required data as native, perfectly formatted Excel files. Because the data is delivered cleanly, including correct formatting for financial figures and dates , it is immediately suitable for advanced financial analysis using pivot tables.
The DBA SGA+PGA Memory Configuration report is ideal for this. It displays the current SGA and PGA memory configuration in gigabytes, comparing it to the available hardware resources, which is crucial for identifying if you are fully utilizing physical RAM.
It is generally safe to trust the official RUP patching documents regarding pre-patch analysis if you follow the prescribed path. However, for robust internal verification, you can always utilize the Blitz Report mechanism querying AD_PATCH.IS_PATCH_APPLIED to confirm if specific bug numbers were implicitly handled or applied correctly.
The workaround is to manually re-enter the custom tops entries back into the `$APPL_TOP/admin/topfile.txt` file. Then, you must rerun AutoConfig to generate the new environment file and ensure the context file is updated correctly.
While the OPatch version number remains 12 (e.g., OPatch 12.2.0.1.42), it is correctly designed for the Oracle Database 19c version. It is essential to ensure you are using the version that has been recently released and certified for your specific 19c update level.
We cannot definitively state the cause, but this often happens when previous custom products were added manually rather than by running `adsplice`. If `adsplice` doesn’t know about them, it may not correctly maintain those entries.
During the ECC V11 installation and integration , key database parameters must be correctly defined in the configuration files (e.g., `ecc-config.properties`). You must specify the `EBS_DB_URL` using the JDBC thin connection string, ensuring the load balance and failover settings are correctly configured, along with the `EBS_DB_USERNAME` (typically APPS) and `EBS_ECC_USER` (DEVELOPER).
For customers upgrading to R12.2.12, it is crucial to review the detailed Oracle documentation. Specifically, you should consult the R12.1 / R12.2 : Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Documents (Doc ID 1302189.1), which provides comprehensive detail divided into separate product families sections to confirm the impact on your GL, AP, and FAH processes.
Enginatics in How to create a Delivery in Full On Time metric in Oracle E-Business Suite using Blitz Report™ Yes, if configuration or promise dates are subject to changes, you can leverage the Audit capability of Blitz Report, details of which are available on our YouTube channel, to track these modifications and maintain data governance.
Leaving the segment parameter blank or entering ‘%’ will include all possible values for that segment.
Enginatics in How to create a Delivery in Full On Time metric in Oracle E-Business Suite using Blitz Report™ You must define the logic clearly, starting with a strong understanding of your promise date and order date types. You then create and test the revised query containing your DIFOT logic and save it back into the copied Blitz Report. Remember to modify the user template to show only the necessary columns for the KPI output.
Any additional warnings related to XXEN objects in other sections, such as SECTION-26 and SECTION-37, should also be ignored, as they reflect the intended non-online-patching design.
Enginatics in How to create a Delivery in Full On Time metric in Oracle E-Business Suite using Blitz Report™ Blitz Report is an ideal tool for creating complex custom metrics like DIFOT. The methodology starts by utilizing existing components: you should first copy the seeded Order Header and Lines Blitz Report. You then modify this copy and rename it meaningfully, such as ‘ONT DIFOT’.
Precisely. Rerun install.sh. Once complete, you can enable the trigger again using alter trigger apps.note_1342126_1_audit_trig enable;.
If Oracle stores ’10’ with leading zeros as four characters, you must enter ‘0010’. Failure to include all leading zeros will result in data retrieval errors.
The error message is just a warning that these custom tables may not be patched using online patching. This design is fully supported by Oracle for custom code that fulfills ‘minimal’ compliance (note 1577661.1), meaning no action is required on your part to correct this specific warning for XXEN objects.
Setting the output format to TSV (tab-separated-values) is Option 1 for solving this issue, but requires additional client setup to associate the TSV file extension with Excel.
The recommended solution is to temporarily disable the problematic custom trigger. For example: alter trigger apps.note_1342126_1_audit_trig disable;.
This indicates that a custom audit trigger (likely created following Oracle note 1342126.1) is prematurely referencing a sequence’s current value (CURRVAL), causing a conflict during package execution.
No, this message should be ignored. The Blitz Report tables are intentionally designed *not* to have editioning views, as the upgrade process is designed to run on live systems without patch cycle creation and cutover downtime.
You must format the value exactly as configured in Oracle. This ensures the lookup is successful.
The default delimiter is a comma (,).
You should set the profile option ‘Blitz Report CSV File Delimiter’ according to the client’s regional settings. This allows you to specify the delimiting character in Blitz Report CSV output files.
You define the message by navigating to Application Developer > Application > Messages.
Yes, there is a separate profile option, ‘Blitz Report Use Operating Unit Security’, that allows activating or deactivating operating unit security.
The default message is `XXEN_REPORT_EMAIL_BODY`.
You should set the profile option ‘Blitz Report Disable GL Flex Value Security’ to ‘Yes’. This disables the security check which is causing the slowness.
You set the profile option ‘Blitz Report Email Body Message’. The value you enter must be the message name defined in Application Developer, and it must start with `XXEN_REPORT_EMAIL_BODY%`.
Use the FND Profile Option Values report. This shows profile option values on all setup levels, including the user-visible value in addition to the internal system value.
There are three potential output files that can have different names : 1) The file downloaded to the client desktop . 2) The output file stored on the concurrent processing server in `$APPLCSF/out` (which is also used as the email attachment filename for standard Oracle delivery options) . 3) An additional copy placed into a specified directory on either the application or database server .
Yes, if you are experiencing slow performance on GL Balance or GL Account Analysis reports and do not use security rules, you should investigate setting the profile option ‘Blitz Report Disable GL Flex Value Security’.
It also returns `x_row_count` (the number of rows extracted), `x_filename` (the suggested output filename), `x_return_status`, and `x_msg_data`.
Scheduling allows you to run time-consuming reports during off-hours, and it enables output distribution via Oracle’s delivery options, such as sending the output as an email attachment, or to an FTP location.
First, you must call `xxen_report.apps_initialize` to set the session context. Then, you call `xxen_api.create_run_id_` to get a `l_run_id`, set any necessary parameters, and finally call `xxen_api.run_report` using that `l_run_id`.
You need to re-register the underlying PL/SQL function `APPS.AMS_DISCOVERER_PVT.EUL_TRIGGER$POST_SAVE_DOCUMENT` via Discoverer Administrator. You should then validate the function is working. If the function doesn’t appear, the EUL user might require `grant execute any procedure to eul_us`.
You can use the Profile option ‘Blitz Report Additional Output Filename’ or the report-level setting to define a template containing a date format string, but omitting the time component . For example, setting the template to `_` and scheduling the report hourly would ensure that the same file is overwritten multiple times a day, containing the refreshed data .
If submitting manually, you must populate parameters 1 to 87 with values in exactly the same order as they appear on the Blitz Report run window. For example, Parameter3 of the concurrent request must match the third parameter on the run window.
The Discoverer Worksheet import relies on SQL being present in the EBS table `AMS_DISCOVERER_SQL`. This table is updated by a Discoverer trigger called `eul_trigger$post_save_document`.
You use the procedure **`xxen_api.run_report`**. This procedure executes the report query synchronously and returns the Excel output file content in an `x_output_file` parameter of type BLOB.
No, the naming convention for files saved to the additional output directories (APPS or DB server) is defined in the separate field ‘Additional Out. Filename’ , , . This field also supports the same dynamic tokens, allowing you to define a naming structure suitable for interfaces or archival, such as including a date format string (e.g., “) .
That is correct. Once the database link infrastructure (Heterogeneous Services) is configured within the Oracle database, Blitz Report can use standard SQL queries, incorporating the database link syntax (e.g., `@DBLINK_NAME`), to seamlessly integrate the data from the external source directly into your EBS report output. Blitz Report then provides the fast Excel output interface over this consolidated dataset.
First, run the report. Then, navigate to the menu > view > requests > submit a new request > single request. Use the Copy feature to select the request submitted in step 1, update the schedule and delivery options as required, and re-submit it.
That is correct. By default, the SQL is included in both the log file and the XLSX output file.
The location for saving a copy on the database server is defined in the ‘Additional Out. Directory on DB Server’ field, which requires Developer access , . This directory must correspond to a TNS descriptor defined in `dba_directories` . If you also need to save a copy on the application server filesystem, that is configured separately using the ‘Directory on the application server to save a copy…’ field .
Blitz Report explicitly supports accessing external data sources. To integrate data from non-Oracle databases such as Vertica or MySQL, you leverage standard Oracle database capabilities like Database Links. These links rely on underlying infrastructure like Oracle Heterogeneous Services or Oracle Database Gateway to establish connectivity.
To prevent the SQL from appearing on the parameter tab of the XLSX output file, set ‘Blitz Report Include SQL in XLSX Output’ to ‘No’.
The recommended method is to run the Blitz Report once from the Run window, and then copy the submitted concurrent request to schedule it.
You can control SQL visibility using two separate profile options. To exclude the SQL from the log file, set ‘Blitz Report Include SQL in Log’ to ‘No’.
The filename downloaded to the client desktop is defined in the ‘Excel output file name’ field under Report Options . You use tokens enclosed in angle brackets (“) to define the dynamic content . For your requirement, you would use tokens such as “, “, and “ (or “ if you prefer underscores over spaces) , . If you use “, all spaces in the report name are automatically replaced with underscores .
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel Absolutely. Unlike solutions such as BI Publisher, which may restrict output to 65,536 rows, Blitz Report has no volume limitations on the data exported to Excel or CSV. This makes it ideal for extracting complete ECC data sets regardless of size. If you want to test this capability, the Blitz Report software is free to use for your first 30 reports.
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel Yes, Blitz Report provides a dedicated solution for Oracle Enterprise Command Center administration and enriched dashboard data export to Excel. It efficiently extracts the underlying data sets, allowing you to bypass the limited export capabilities sometimes found within the standard ECC interface.
No, the standard SQL entry field through the Oracle Forms interface is limited to 32767 characters . If your extraction SQL, even with the embedded lexical logic, exceeds this limit, you must utilize the ‘Upload Large SQL’ functionality, which can be accessed from the Tools menu in the Blitz Report Setup window . You should ensure the SQL file is encoded correctly, particularly if non-ANSI characters are present.
The DFF utility automatically uses the DFF prompt text as the column header . While you cannot directly edit the output of the utility within the parameter definition, you can use the Column Translations feature in Blitz Report Setup to define multi-language headers . If you need a column-specific number format or translation, you should check ‘Columns’ during export to include this data for migration .
You should place the `&lexical` anchor within the `SELECT` clause, usually followed or preceded by a comma, to correctly delimit the dynamically generated columns from your fixed column list . For instance, `select fu.user_name, fu.email_address, &columns frv.responsibility_name` allows the lexical anchor to inject columns like `fu.user_name, fu.email_address,` followed by your static column . The utility function ensures that the resulting SQL text is formatted correctly for insertion, often including quotation marks for column aliases (e.g., `msiv.attribute1 “Late Demands Penalty”`) .
For developers, even if the Setup window shows all reports, the Run window reports List of Values (LOV) is still restricted by the current responsibility if the relevant profile option is set to ‘Yes’.
The `xxen_util.dff_columns` function requires the `p_table_name` (e.g., ‘mtl_system_items_b’) and the `p_table_alias` (e.g., ‘msiv’) , . By default, if you don’t specify a DFF context code, it generates columns from all contexts, starting with ‘Global Data Elements’ , . Optionally, you can restrict the output by providing the `p_descr_flex_context_code` to show only DFFs for a specific context .
The option to define excluded parameters is part of the template setup in the Blitz Report Setup window. Once set, the visibility changes dynamically upon template selection on the Run window.
You should use the `&lexical` anchor, placing it directly within your `SELECT` clause (e.g., `select &flexfield_columns from mtl_system_items_vl msiv`) . The parameter associated with this anchor must contain SQL that calls the utility function `xxen_util.dff_columns` . This function automatically queries the `fnd_descr_flex_col_usage_vl` dictionary tables to generate the required comma-separated list of DFF columns and their respective column headers (prompts) , .
When a parameter is excluded, it is hidden from the display. If the underlying SQL relies on that parameter having a default or dynamic value when not explicitly input by the user, the parameter logic still executes, but the user interface is cleaner.
The maximum run time limit is enforced by the ‘Blitz Report Monitor’ concurrent program. This automatically cancels reports exceeding the limit to avoid excessive server load.
The time limit is indicated in seconds. However, there is a profile option, ‘Blitz Report Time Limit in minutes’, for setting a default maximum execution time limit in minutes.
Yes, this functionality is available. You can define Excluded parameters for a template during template definition. When that template is selected on the Run window, the excluded parameters are not displayed.
During import, Blitz Report derives parameter types from the underlying items and creates LOVs automatically for the item classes used by the workbook parameters.
The order is: 1. Run window options time limit, 2. Profile option on user level, 3. Time limit on report level, 4. Profile option on responsibility level, and finally, 5. Profile option on site level.
The time limit can be set at multiple levels, and they follow a strict order of precedence. The highest priority is the Run window options time limit.
The Concurrent Program import option allows migration of parameter definitions, LOVs, and request group assignments from any concurrent program. This assists in migrating other reporting technologies, such as Oracle Reports `.rdf` files. Though the SQL typically requires manual transfer, this feature automates the tedious setup of parameters and access controls.
No, successful standard and system report runs have separate log retention profiles: ‘Blitz Report Log Retention Days Standard’ and ‘Blitz Report Log Retention Days System’.
The default value is ‘No’.
When left blank, there is no automated purge of log data.
The source suggests referring to documentation on configuring mod_plsql in your EBS 11i instance.
Setting this profile allows using mod_plsql for establishing server connections from the upload excel to display the LoV values, default values, and perform server side validations.
The retention period is set by ‘Blitz Report Log Retention Days Error’. The actual purging is performed by the Blitz Report Monitor concurrent program.
Absolutely. Blitz Report includes a project implementation and upgrade toolkit specifically designed for managing these challenges. This toolkit offers automated BR100 extracts for setup and data migration, and supports time-critical reports geared towards mass exporting volume data.
You must configure mod_plsql as a replacement for ISG. Then, set the profile option ‘Blitz Upload Use mod_plsql’ to ‘Yes’.
Blitz Report provides full version control and audit comments with every report modification and migration. This structure keeps your DBA reports organized and ensures consistency, especially crucial when working within a team environment. You can save and categorize your custom reports for quick future access.
You can create a custom report in Blitz Report specifically utilizing the AD_PATCH.IS_PATCH_APPLIED function. This allows you to quickly check the status (APPLIED or NOT APPLIED) for specified bug numbers across your application tops without needing to log in separately to the database or run complex SQL manually.
No, any view which references Polaris RWB objects starting with `XXRX%`, such as views using `xxrx_util_pkg.get_parameter_char_value()`, will be expanded regardless of the setting used for the `p_expand_view_sqls` parameter.
Yes, Blitz Report provides a comprehensive suite of AWR and foundation (FND) reports as part of its Database Health and Tuning capabilities. Importantly, the updated DBA AWR Blitz Reports now work with pluggable databases (PDBs), adjusting for how AWR data is stored and accessed in container databases (CDBs).
If the ‘Invoice on Hold’ parameter in the AP Invoices and Lines report is left as its default value of ‘Null’, the hold status is not considered, meaning all invoices (held or unheld) would be retrieved based on other criteria.
Yes, the DBA toolkit includes reports to Find an IP address and geolocation of EBS clients’ logins. This data can be visualized in Excel using tools like Bing Maps for security monitoring.
Yes, the AP Invoice on Hold 11i report provides the same functionality for older systems.
You should use the procedure `xxen_api.import_reporting_workbench`. This process is designed to consolidate different RWB reports based on shared database views into single Blitz Reports.
Blitz Report is ideally suited for this need, offering a way to seamlessly incorporate your custom DBA toolkit, moving beyond text documents. It allows you to execute queries directly from the EBS forms interface, removing the need to navigate to the OAM page or manually log into the database using SQL*Plus.
Blitz Report is the recommended solution for Simplifying DBA tasks. It allows the DBA to centralize all diagnostic queries (AWR, FND, patch checks) and execute them directly from the EBS Forms interface, improving organization and speed.
JED captures journal activity that is both posted and unposted, while JEDP only includes posted journals for the specified date range.
Use the AP Invoice on Hold report. This is based on the Oracle standard Invoice on Hold report (Short Name: APXINROH_XML).
Enginatics in Discover the secret of perfectly formatted Oracle EBS Excel report creation in under 10 minutes Blitz Report incorporates essential development management features, including full version control. This ensures that modifications are automatically tracked with audit and version history, preventing duplication and maintaining a stable codebase even with rapid creation cycles. Furthermore, you can assign parameters for testing and production deployment quickly.
We recommend using slashes (“/”) as date separators and ensuring that you format the dates as text in Excel to prevent automatic conversion based on your regional settings.
Yes, because the hyphen (“-”) serves as a range delimiter in Blitz FSG, you must avoid using it as a date separator.
Enginatics in Discover the secret of perfectly formatted Oracle EBS Excel report creation in under 10 minutes It is entirely feasible, as Blitz Report eliminates the complexities typically associated with BI Publisher and XML formatting. The process involves minimal steps. You simply log on as a developer, open the Blitz Report form, and paste your proven SQL query directly into the tool.
While the core database procedures for cache clearing remain the same, any major OS upgrade, like Upgrading an Oracle E-Business Suite server from Oracle Linux 7 to Oracle Linux 8, requires full regression testing and careful execution of all maintenance scripts to ensure compatibility within the new environment. Cache clearing is a standard post-maintenance step.
Yes, for JED, JEDP, or JEDU balance types, the period parameter functions as a date parameter, accepting date ranges like ’01/01/2007-05/01/2007′.
Utilize the Concurrent Request Monitoring and Alert Reporting tool. This enables immediate identification of requests that are ‘Running longer than x Minutes’ or stuck in a ‘Waiting’ phase, helping diagnose if a non-cleared cache issue or other bottleneck is impacting job execution.
Your DBA team should leverage Blitz Report’s Diagnostic Pack for quick checks. Running the Automatic Workload Repository (AWR) reports before and after the cache clear allows for immediate comparison and analysis of performance changes, even in multitenant databases.
The underlying architecture enforces accountability. When a developer or consultant uses Blitz Report to create or modify a report, it utilizes full version control with audit comments tracked directly in the EBS instance.
Blitz Report supports defining and managing complex parameters. When converting a BI Publisher report, you replicate the core parameter functionality in the Blitz Report setup, allowing users to input criteria before execution. The tool supports assigning parameters with customized List of Values (LOVs).
In Oracle EBS 12.1 and 12.2, the cache is cleared according to documented procedures provided by Oracle. The specific mechanism usually involves calling designated database procedures or executing utility scripts to invalidate and flush the relevant caches, ensuring operational stability.
Once the report logic is defined within Blitz Report, yes. Any report created can be leveraged immediately for features such as seamlessly integrating reports into EBS forms using Zoom , providing users with contextual access to the converted BI Publisher data when reviewing transactions.
Certainly. Regardless of the complexity of the integrated query, Blitz Report delivers the consolidated data immediately as a native, formatted Excel file, which can then be easily utilized by business users or imported into tools like Tableau or Microsoft Power BI.
Use the CAC Number of Item Costs by Cost Type report. This shows the count of item costs by cost type, useful after bulk cost copy operations.
Yes, this functionality is fully compatible with EBS 12.2, as demonstrated in our resources covering connecting to external databases. Blitz Report gives you the flexibility to retrieve data from any database system, provided the necessary Oracle database link setup is in place.
The primary output benefit is the perfectly formatted Excel report creation in under 10 minutes. Additionally, Blitz Report overcomes the painful technical limitation where BI Publisher output in EBS 12.1.3 generates XLS instead of XLSX, capping the rows at 65,536.
Run the INV Default Category Sets report. This lists the Inventory functional areas and their default category sets.
The SQL complexity remains standard. Within your Blitz Report query, you simply reference the external table using the standard database link syntax (e.g., `@DBLINK_NAME`). Blitz Report then executes this integrated query seamlessly, drawing data from both the EBS database and the external Vertica source.
Yes, advanced monitoring reports within the Blitz Report suite (like the Concurrent Request Monitoring tools) can filter requests based on various operational metrics, including the Node where the request ran or the Manager Name processing the request. This provides deep visibility into the execution environment.
You should use the INV Organization Parameters report. This provides a master data view of the organization parameters.
A perfect example is the All Inventories Value Report (CSTRAIVR), which relies on CSTRAIVR_XML. Blitz Report easily converts this report, extracting the data set logic to provide immediate, formatted Excel output, solving the core issues associated with BI Publisher’s complex template requirements.
The Database Link must rely on underlying infrastructure such as Oracle Heterogeneous Services or the Oracle Database Gateway, which often utilize ODBC connectivity to communicate with the external database system. Once this gateway layer is configured in your Oracle EBS reporting instance, the database link can be created.
The focus of Blitz Report is on SQL to Excel reporting for non-developers. Once the report is created and saved, end-users access it through the familiar EBS Forms interface, enter parameters, and receive the complex ASCP data output directly as a clean Excel file.
Blitz Report allows you to essentially ‘fast track’ this development process. You can convert and deploy BI Publisher-based reports in as little as 5 simple steps, primarily by extracting the core SQL logic from the BI Publisher data definition and integrating it directly into the Blitz Report form.
Oracle E-Business Suite reporting straight into Excel: 2,900+ ready-made reports, your own SQL, 150+ Excel uploads.