Support
Discussion Replies Created
The function **`XXEN_UTIL.USER_ID(p_user_name in varchar2)`** returns the user ID based on the provided user name.
Please run the DBA Parameters report. This report helps validate recommended settings against critical Oracle notes, such as Document 396009.1, ‘Database Initialization Parameters for Oracle E-Business Suite Release 12’.
These settings can be defaulted by the corresponding profile options, such as ‘Blitz Report Additional Output Directory APPS Server’ and ‘Blitz Report Additional Output Directory DB Server’.
You pass `application => ‘XXEN’` and `program => ‘XXEN_REPORT’`.
Blitz Report is designed to work within standard, secure EBS environments. Its execution via Forms and the Concurrent Manager remains unaffected, as it continues to use the standard EBS infrastructure (including JWS where applicable). Securing your communication layers (ECC, ISG, core EBS) is a necessary prerequisite for overall operational security.
Yes, you would use ‘Additional Out. Directory on DB Server’. The list of available directories is fetched from the `dba_directories` table.
When using the Oracle standard concurrent program API, `argument1` through `argument15` are reserved for specifying the report name, template name, and various runtime options (like email or output format). The actual user-entered report parameters start from `argument16` onwards.
Yes, you can use tokens to create a directory path dynamically. For example, `/interface/ _ `. If the resulting directory does not exist, it is automatically created, provided the apps owner has permissions.
For overall execution history, you can use the Blitz Report History report or the Blitz Report Execution Summary report for count and performance summary.
To ensure the functionality is enabled, you must also verify the parameter `ENABLE_EXPORT` is set to `true` in your ECC configuration files.
Enforcing HTTPS protects your EBS 12.2 environment from various security risks associated with unencrypted HTTP traffic. This is part of the larger strategic recommendation to maintain modern security postures, including proper configuration of components like ECC and ISG, which can be vulnerable if left unsecured.
This is configured using the developer-only option ‘Additional Out. Directory on APPS Server’. This saves a copy of the report output file in the specified directory.
Enginatics in Develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes The report execution is fully integrated; the report runs immediately through concurrent requests, and importantly, you do not need to manually register the report in system admin. This seamless integration eliminates administrative overhead and is a core part of the rapid development promise.
The history of deleted reports can be purged completely by running the concurrent program ‘Blitz Report Monitor’ with the parameter ‘Purge delete reports SQL history’ set to ‘Yes’.
The requirement to secure ISG communications is also critical. We provide detailed instructions for configuring TLS/HTTPS for Oracle EBS Integrated SOA Gateway (ISG) in both EBS 12.1 and EBS 12.2 environments. While the goal is the same, the underlying architectural differences between 12.1 and 12.2 may necessitate slightly different steps.
Blitz Report is the superior alternative for high-volume data extraction. By utilizing the underlying ECC SQL logic within a Blitz Report, you avoid the framework’s internal export count restrictions. Blitz Report guarantees no volume limitations on the output and delivers the data as perfectly formatted Excel files.
Configuring TLS/HTTPS for the ECC Framework is essential for security. This process involves specific steps to secure the communication channel, ensuring data integrity and confidentiality between EBS and the ECC components. ECC TLS/HTTPS with EBS configuration references are available in our technical posts.
Enginatics in Develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes Blitz Report fundamentally overcomes the CSV file type limitations and data output limitations associated with ECC dashboards. By running the imported SQL through Blitz Report, the data is delivered as a perfectly formatted Excel output file with filters automatically applied, regardless of data volume. We have reports available across over 220 Oracle ECC areas that can be imported quickly.
The learning curve is minimal. The toolkit is an add-on that resides in standard Oracle Forms, meaning there are no new commands to learn, and it requires virtually no training. Consultants can simply drop their favorite SQL scripts directly into the Blitz Report form and instantly start sharing version-controlled output.
Run the Blitz Report Deletion History report. This report shows deleted Blitz Reports and can be used to recover accidentally deleted reports.
Enginatics in Develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes The benefit is twofold: rapid creation and assured output. Since these queries have been tested and approved by Oracle for their dashboards, incorporating them into Blitz Report guarantees the output aligns with the ECC business logic, effectively creating a single source of truth for both EBS and ECC reports.
Blitz Report follows the Virtual Private Database (VPD) security framework. You can control precisely what tables and data Blitz Report can access by using standard Oracle VPD security policies at the row and column level. This protects sensitive data while still allowing necessary configuration extracts.
Enginatics in Develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes Yes, absolutely. Blitz Report allows for rapid report development, often in under 5 minutes, by directly utilizing the standardized Oracle ECC SQL queries. This method is ideal for consultants and business users needing quick, reliable reports.
Yes, the export limit is a defined configuration parameter within the ECC Framework installation. You need to check the `ecc-config.properties` file. The parameter governing this is `MAX_EXPORT_COUNT`, which is typically set to a limit like 1000 records.
The toolkit incorporates full project management features, including full version control for all custom SQL scripts. When reports are migrated between EBS instances—for instance, from development to testing—the delivery is reduced, version-tracked, and includes full audit comments with every migration. This simplifies the implementation process without version challenges.
Not at all. Blitz Report is an add-on that can be installed in your EBS environment, typically within 15 to 30 minutes. You can test this specific auditing functionality immediately, as the software is free to use for up to your first 30 reports.
Our public documentation of these various upgrade paths demonstrates our ongoing commitment to supporting the EBS platform. This aligns with the strategic view that EBS remains a vital platform for organizations with complex, highly customized operations.
No, the toolkit includes Time Critical reports geared toward mass exporting volume data and an Excel export engine that overcomes the data limitations and formatting issues associated with standard CSV files. It will generate perfectly formatted Excel or CSV files regardless of whether you have 5 million records or a few thousand.
A major advantage is overcoming the data volume issue inherent to Oracle’s default tools. Blitz Report explicitly states there are no volume limitations , unlike solutions like BI Publisher that cap row counts. This ensures you can extract and analyze the full scope of your audit data efficiently, outputted instantly as Excel files ready for analysis.
The Blitz Report Toolkit is specifically designed as an easy-to-use add-on to manage and export critical data during EBS projects and upgrades. It provides automated BR100 extracts for setup configuration and data migration. This eliminates the manual effort traditionally spent capturing configuration details.
The generated reports are provided as perfectly formatted Excel files. These can be shared easily, and Blitz Report itself supports scheduling and alerting capabilities to automatically distribute exception reports to the relevant planners via email.
Yes. The toolkit includes the Database Health and Tuning reports, which encompass a comprehensive suite of AWR and FND reports. This allows your DBAs to quickly and efficiently assess any pre-existing bottleneck processes or user waits in the newly upgraded 12.2.10 environment, ensuring performance is optimized immediately post-migration.
Yes. We offer specialized reports like the ‘Audit Table Changes by Column Report’. This report allows master data teams and operational groups to quickly pinpoint and track precisely which fields were modified, significantly improving the speed and focus of your compliance and data governance operations.
The primary advantage is usability and speed. Blitz Report allows planners to quickly create flexible reports using SQL, focusing only on the specific exceptions or data fields they need, and exporting this data instantly to Excel. It also supports extracting advanced metrics like horizontal planning data and pegging exports for deeper analysis.
This is a frequent challenge addressed by Blitz Report, designed for Master Data Maintenance and governance teams. While the standard Oracle report is indeed unreadable and omits related data (such as the supplier name) , Blitz Report excels by utilizing SQL to retrieve and combine the audit trail with the necessary descriptive attributes, rendering the output clear and contextual in Excel.
Immediate readiness is crucial for project stability. During the upgrade process (like 12.2.9 to 12.2.10), you need reliable tools for validation and performance monitoring. Blitz Report serves as a critical component in your project implementation and upgrade toolkit , helping with data migration validation (BR100 extracts) and monitoring system health via AWR reports.
Yes, Blitz Report provides a direct solution to replace Oracle ASCP exceptions reporting. It transforms the complex data stored in ASCP tables—which cover concepts like supply planning and exceptions—into highly consumable Excel output.
Enginatics maintains a strong commitment to staying up to date with the latest technology. Our team immediately prioritized upgrading our EBS Demo instance from 12.2.9 to 12.2.10 right after the new release was announced. This ensures that our customers can confidently test Blitz Report, which is recognized as the fastest reporting solution for Oracle E-Business Suite, on the most recent software.
Blitz Report provides reduced processing overhead for its reporting. It is specifically used for Time Critical reports and volume data exports , ensuring the generation step is performed quickly before the Python transfer script executes.
Yes. If you run the concurrent request directly before the import, the Blitz Report code attempts to retrieve the program’s largest SQL from the database memory (SGA).
Best practices dictate encrypting or securely storing credentials. Furthermore, you must ensure that the EBS server itself (especially EBS 12.2) is secured via HTTPS/TLS at the application level to protect against network intrusion.
It executes a full text search across the report name and description, parameters, SQL definition, and template name and description.
Yes, the Concurrent Program import option allows migration of parameter definitions, LOVs, and request group assignments for any concurrent program. While the report SQL usually needs to be transferred manually for these technologies, the setup simplifies parameter conversion.
You can monitor the entire concurrent process execution via the Concurrent Request Monitoring and Alert Reporting tool. This tool can identify requests that fail (Status: Error) or stall. If the Python script is part of the concurrent workflow, failures at that stage should be captured, allowing you to email alerts automatically.
The full text search is not case sensitive. For complex logic, you can use brackets to group sub-expressions. For example, you could type `(AP or AR) and Invoice` to refine your results.
The ‘No Data to display’ error can occur if the required security roles have not been properly assigned to the user’s responsibility . Even after a successful data load, users need product-specific roles (e.g., `UMX|FA_M_ECC_ACCESS_ROLE` for Fixed Assets) to access the Command Center functionality and view the data , . You must ensure the necessary UMX assignments were completed using the appropriate role assignment script or method , .
When entering multiple keywords, the search matches all keywords by default. If you want reports matching ‘budget’ OR ‘actual’, you must explicitly combine them with the keyword ‘or’. This search functionality works across the report name, description, parameters, and underlying SQL.
For scheduled delivery, Blitz Report integrates with the Concurrent Manager. Once the report execution is finalized (status Completed), the output file is written to the file system. The Python script, triggered either sequentially or via a separate scheduled process (like a Concurrent Program post-processor), then executes the file transfer logic from Linux.
Yes, for the initial data extraction, you should specify the Load Type as `FULL_LOAD` . While the default log level is typically acceptable, setting the Log Level parameter to ‘Error’ is usually standard for initial runs . Note that the concurrent program short code is `ECCRUNDL` (‘ECC Run Data Load’) .
No. If a parameter value associated with an `&lexical` anchor is left blank, the corresponding reference is removed entirely before SQL execution, which is another aspect of the optimization.
You should check the ECC managed server logs, typically the `ecc.log` file . While the concurrent request shows ‘CANCELLED’ in EBS, the ECC logs may contain detailed stack traces or error messages related to the Solr index update or data processing . If the error points to a ‘Read timed out’ (`java.lang.InterruptedException: Read timed out`), as seen in some logs, it suggests a connectivity or timing issue between ECC components during the heavy collection registration phase .
Blitz Report primarily generates native, formatted Excel files. Additionally, if you require non-Excel formats for archival or legal reasons, Blitz Report also supports generating PDF output. Both Excel and PDF files can be targeted by your Python script for transfer.
After applying the necessary patches and fixes, you would re-run the relevant AD Applied Patches report to confirm the application details.
A highly effective method is using a python script executed on the Linux server. Python offers robust libraries for handling HTTP requests and authentication necessary to interface with modern cloud storage services like SharePoint Online, making it ideal for EBS automation.
Exactly. The `&lexical` parameter reference is far more flexible. It works like lexical parameters in standard SQL*Plus or Oracle Reports, meaning Blitz Report replaces the placeholder completely with the parameter SQL text at run-time. This makes `&lexical` suitable for injecting almost any SQL snippet, including Dynamic tables and columns, ORDER BY clauses, GROUP BY clauses, HINTS, or Complete subselects or EXISTS clauses.
When an ECC Data Load concurrent request ends with a ‘CANCELLED’ status, it suggests an issue that prevents the load from finalizing, often deep within the ECC or database layers . You should refer to Oracle Support Document 2649008.1, which covers similar symptoms . The key action for troubleshooting is checking the database alert log immediately following the failure of the data load request . Errors in the database alert log often provide clues regarding resource contention, connection loss, or specific data handling failures.
The `n=n` anchors (e.g., `1=1`) are specifically WHERE clause SQL anchors. When using these, Blitz Report inserts the associated SQL text *before* the anchor, automatically adding the keyword ‘and’ and a line feed, ensuring valid SQL. However, the `n=n` syntax remains in the run-time SQL, so it can only be used for WHERE clauses.
Yes, for R12.2 environments, you can use the AD Applied Patches R12.2 report, which is designed to check if a specific patch is applied in 12.2.
Developers can use many standard Oracle functions like `to_char`, `to_date`, `sysdate`, `add_months`, `months_between`, etc., without needing a `select … from dual` clause. This applies mainly when setting default values.
The column width is capped at this maximum, but the generated macro template includes code that attempts to set `WrapText = False`.
The recommendation is driven by performance optimization. Blitz Report creates dynamic SQL at run-time, which allows unused parameters to be dropped entirely from the query. This eliminates a frequent source of non-performant SQL, specifically the widespread coding practice of using the inefficient pattern: `column_name=nvl(:bind_variable, column_name)` for optional parameters.
The default maximum column width is 60.
Run the AD Applied Patches report. This report details AD applied patches, patch runs, included bugs, filenames, and actions.
Yes, if timezone conversions are enabled, a ‘Date’ type parameter is used as a bind without any conversion (midnight of the date entered). A ‘DateTime’ type parameter, however, will be converted to server time before execution.
You can refer to the Blitz Report Default Templates report.
You can set the profile option ‘Blitz Report XLSX Max Column Width’. This defines the maximum column width for Blitz Report XLSX output files.
The Blitz Report Column Translations report can be used to review column translations.
Set the profile option ‘Blitz Report Show All Templates’ to ‘No’. If set to ‘Yes’, it shows all templates for all reports on the run window.
Yes, this parameter supports multiple period ranges and lists, including wildcard entries like ‘Jan-0%’ or ‘%-07’ for flexible period matching.
That is correct. You configure the dynamic date logic using the standard Oracle scheduling features available when submitting or copying the concurrent request.
When creating a new report based on an existing one, like copying a seeded report (e.g., Order Header and Lines to create a DIFOT report), the parameters are retained or can be redefined in the new copy, maintaining change control wherever applicable.
The Blitz Report Templates report lists all Blitz Report column or pivot aggregation layout templates.
When using CTD, the Period Name parameter accepts a custom range format, such as ‘Feb-07-Aug-07’. This aggregates movement data across those specific periods.
Key users can significantly simplify parameter creation by leveraging existing definitions. You can choose from any existing parameters already used by standard Oracle Concurrent Programs or the seeded Enginatics Blitz Reports. This saves effort on defining standard LOV validation logic.
For date parameters in scheduled Blitz Reports, you must utilize Oracle’s increment date functionality. This functionality allows the date parameter to adjust dynamically upon each execution of the scheduled concurrent request.
You need to select the CTD (Custom-to-Date) balance type. This type summarizes balances for user-defined period ranges.
Blitz Report parameters are highly flexible. You can define a custom list of values (LOV) by setting the LOV type to ‘custom’ when creating the parameter. The underlying SQL of your report must be written to handle the list of values passed by the parameter, typically using an Oracle `IN` clause.
You can create new custom messages prefixed with `XXEN_REPORT_EMAIL` and then set the profile option ‘Blitz Report Email Subject Message’ to use your custom message.
Once identified, the SQL should be analyzed and corrected, usually by reviewing the execution plan (using reports like DBA SGA SQL Execution Plan History) and ensuring indexes are appropriately used to avoid nonselective reads.
The default email subject is stored in the Oracle FND message XXEN_REPORT_EMAIL_SUBJECT. You can edit this text via Application Developer > Application > Message.
If the number of items processed per second decreases as the total items processed increases, the report indicates that the interface SQLs are most likely using a wrong nonselective index, and corrective action should be taken to fix the SQL.
Oracle’s recommended tool for PL/SQL performance analysis is `DBMS_PROFILER`. You can analyze its output using the DBA DBMS Profiler Data report.
The ‘Cost Type’ parameter is mandatory, requiring you to enter a cost type name.
The INV Item Import Performance report is specifically designed to be an analytical report to predict the performance of inventory item load background processes.
You can include &ROW_COUNT (the number of rows returned), &REPORT_NAME, &DB_NAME, &USER_NAME, and &SITE_NAME. These are replaced when the email is sent.
For routing master data, use the BOM Routings report, which shows bill of material routings with item codes and sequences.
No, if you use a standard bind variable (:bind), you lose the ability to dynamically drop the clause, which is why using anchors is recommended for optional parameters that need dynamic insertion.
The time could be spent on CPU, indicating complex processing or reading massive amounts of data from the buffer cache, or on PL/SQL execution, captured in the ‘Plsql Exec Time’ column. You should also check for network waits if there are database links involved.
Yes, Blitz Report supports placeholders for automated replacement at run-time within the email subject. You can use the placeholder &REQUEST_ID to include the concurrent request number.
Use the optional parameter ‘p_only_zero_costs’ to show assemblies and components with a zero cost. Additionally, ‘p_include_expense_items’ allows you to include or exclude non-asset (not valued) items.
Anchors (like 1=1 or &lexical) act as placeholders. If the user does *not* enter a value for an optional parameter, the corresponding SQL clause is dropped entirely from the query, resulting in a cleaner and faster execution plan.
In the DBA AWR SQL Performance Summary report, examine the ‘IO Row’ column. This represents the average I/O per individual row retrieved. For data extraction SQLs without aggregation, this metric is a good indicator of efficiency.
The nvl pattern is a frequent source of non-performant SQL because it often prevents index usage. Blitz Report avoids this by creating dynamic SQL at run-time.
Yes, the CAC Where Used by Cost Type report provides the single-level bills of materials and related component information. While exploding the bills, you can compare with two cost types and limit the report to only assemblies and component items with a zero item cost.
The BLOB API is generally used for synchronous reporting, suitable for immediate drill-downs or quick previews, but long-running reports are typically submitted asynchronously using the concurrent program API (`report_submit_concurrent_`).
Yes, the `xxen_utils.download_file` procedure is included in the **`XXEN.pll`** library, so you must ensure this library is attached to your custom form to use the functionality.
The default email subject for Blitz Reports is stored in FND message `XXEN_REPORT_EMAIL_SUBJECT`.
Yes, the field can be populated using a SQL statement returning one column containing email addresses.
Yes, the email field supports a comma-separated email list, such as ‘[email protected],[email protected]’.
You can use placeholders for automated replacement at run-time, including `&REPORT_NAME`, `&ROW_COUNT`, `&DB_NAME`, `&USER_NAME`, `&REQUEST_ID`, and `&SITE_NAME`.
It expects the file ID, which you retrieve by calling `xxen_api.report_file_id(l_run_id)`, where `l_run_id` is the ID generated when you initiated the run using `xxen_api.create_run_id_`.
If different email addresses are set up on different levels, the default email on the Blitz Report run window is derived in the following order: first is the Default email setup on report level (1), followed by the Profile option ‘Blitz Report Default Email Address’ (2).
You set the profile option ‘Blitz Report Email Subject Message’. The message name must be defined in Application Developer and start with `XXEN_REPORT_EMAIL_SUBJECT%`.
After running the report using the `XXEN_API.run_report` procedure (which returns the output as a BLOB), you must use the procedure **`xxen_utils.download_file`**.
The command requires the APPS password and the name of the XML file: `$XXEN_TOP/bin/import_xml $APPS_PWD blitz_report_filename.xml`.
Yes, for scripted non-interactive deployments, you can use the Linux command line utility `import_xml`. It is located at `$XXEN_TOP/bin/`.
Standard delivery options generally focus on email or FTP. For transfer to external cloud platforms like SharePoint Online from the Linux server, the typically recommended technical approach is using a custom Python script for automation.
Yes, runtime options such as the template name can be set using the `XXEN_API.SET_RUNTIME_OPTION` procedure . You specify the option name (e.g., `’TEMPLATE_NAME’`) and the desired value . You can even set the value dynamically, for instance, by calling `XXEN_API.DEFAULT_TEMPLATE_` to retrieve the user’s default template for that report before executing .
The most reliable way to identify the correct Form Name and Block Name is through the standard Oracle Forms interface . You navigate to the target form, go to the top menu, and select Help > About Oracle Applications > Current Form . This window provides the necessary Form Name and typically enough context to determine the Block and Item names for parameter referencing .
Yes, while the primary focus is Excel, Blitz Report includes functionality to Generate PDF of Blitz Report™ output, often achieved via a post-processing step, which can then be included in the automated delivery options.
By default, the Excel output’s data sheet name is the same as the report name, but a parameter referencing the `:sheet_name` anchor can override this.
To trigger the file download, the PL/SQL procedure must call `XXEN_UTILS.DOWNLOAD_FILE` . This function requires the file ID, which is retrieved using `XXEN_API.REPORT_FILE_ID(l_run_id)` . Note that to use this functionality within a custom Oracle Form, you must ensure the `XXEN.pll` library is attached to your custom form , as `XXEN_UTILS.DOWNLOAD_FILE` is contained within it .
The PL/SQL logic, typically executed in a `when-button-pressed` trigger on the EBS form, uses the `XXEN_API.CREATE_RUN_ID_` function to start a report instance, followed by conditional calls to `XXEN_API.SET_PARAMETER_VALUE_` , . For instance, you first check if the RFQ Header field is populated (`:rfq_header.rfq_number is not null`) before setting that parameter . Then, a nested condition checks if the line number is available (`:rfq_line.rfq_line_number is not null`) before setting the second parameter value , .
Blitz Report is recognized for delivering high-quality output. It generates reports that result in perfectly formatted Oracle EBS Excel reports , ensuring professional quality even for reports generated and sent automatically via email delivery.
The default is report name only.
The Concurrent Request Monitoring report allows you to filter requests by `Status` (Error or Warning) and check the `Phase`. If the delivery fails, the `Post Processor Result` and `Status` information contained within the delivery options details will indicate the failure reason, allowing the operations team to take immediate action.
When monitoring delivery options, you can view details such as the BI Publisher template used, the final output file name, the post-processor result, and crucial delivery details like the email or FTP information designated for distribution.
You set the profile option ‘Blitz Report XLSX Sheet Header’. This defines the header in Blitz Report XLSX sheets.
When configuring your reports to run as concurrent requests, Blitz Report supports delivery options via its integration layer. For diagnostic visibility, the Concurrent Request Monitoring report specifically includes a parameter to Show BI Pub & Delivery Options.
You can confirm with your DBA team whether Java Web Start is enabled on your system. If JWS is confirmed as *not* enabled, then the DBA will need to assist with the Java configuration necessary for the Forms applications on the workstation.
You’re very welcome! I’m happy to help. Let me know if you have any other questions regarding Blitz Report and ASCP.
Yes, the migration involves specific steps to configure JWS in your EBS 12.2 instance. Documentation related to browser user experience and configuration (Section 6) provides details on the environment changes required for a successful transition to JWS.
Hi, yes, Blitz Report is compatible with ASCP. You can install it on the ASCP/VCP server, and it will function without issues.
Additionally, we provide out-of-the-box MSC reports that can be executed either from the Oracle EBS side by fetching data over a database link or directly on the ASCP server. This flexibility ensures that you can generate reports efficiently based on your specific setup.
Regards, Alex
Yes, absolutely. Blitz Report relies on the stability of the underlying EBS Forms architecture. If a user reports inability to run Blitz Reports, the first step is often diagnosing client-side issues, such as confirming that JWS is enabled and configured correctly on their workstation.
You can reverse the changes using the ‘Undo Expand’ tool, which removes the results of the most recent Expand operation and supports multiple undo levels.
Migrating from the Java Plug-In to JWS is highly recommended by Oracle for EBS 12.2 customers. This shift is critical because JWS allows EBS forms to run in browsers that have ended support for the Netscape Plug-in Application Programming Interface. Without JWS enabled, users on platforms like Mac OS Big Sur and later will face significant issues accessing Forms applications.
Yes, the Multi-Row Expand Option allows you to select multiple rows before executing an Expand operation. Blitz FSG will automatically expand each selected row individually.
The ‘Expand’ feature retrieves all child values in the hierarchy and inserts them. Crucially, it automatically copies all adjacent formulas and content to the new rows created for the child values.
Yes, Blitz Upload uses the Integrated SOA Gateway (ISG) for connectivity, which handles these webservice requests.
Yes, you can set the ‘Blitz Report XLSX Sheet Row Limit’ to a smaller value if you need to avoid the 4G size limit.
The default limit is ‘no limit’.
The default maximum is 0.4 MB.
If the report runs without an explicit limit, the data will overflow to additional sheets at every 1,048,575 rows for XLSX output format.
Yes, you use the profile option ‘Blitz Upload Maximum Request Payload Size’. This sets the maximum payload size for data upload webservice requests in MB.
The FND Concurrent Requests report allows you to monitor running requests, providing the session ID and details of the current operation, which should correlate with the information found in DBA Session Longops.
You should note the SQL_ID from the session and check the DBA SGA Active Session History report to see the sequence of wait events and the module/action associated with the session. You can then use the SQL_ID with the SQL Performance Summary reports to analyze the IO impact.
You must also configure the SMTP Host, SMTP Port, and set ‘Blitz Report Use Advanced Email Delivery’ to ‘Yes’.
The DBA Session Longops report is what you need. It provides the estimated time to completion for long-running sessions, sourcing its data from `gv$session_longops`.
The default setting is ‘No’.
You must set the profile option ‘Blitz Report SMTP use SSL’ to ‘Yes’. This enables SSL for Blitz Report advanced email delivery.
Yes, this is essential for automating migration tasks using shell scripts, as it allows you to interact with the generated XML files outside of the database.
To write the CLOB to the database filesystem, you must use the Oracle procedure `dbms_xslprocessor.clob2file`. This procedure requires three key parameters: the CLOB data, a directory name defined in `dba_directories` (such as ‘OUT_FILE_LOC’), and the desired filename.
Yes, if you create an ad hoc LOV using ‘LOV Custom’, you can click the ‘Save as shared LOV’ button to make it available for other report parameters.
If you want to modify the LOV query only for the current parameter, switch the parameter type to LOV Custom before making modifications. Note that changing a shared LOV affects all parameters referencing it.
The default setting is ‘No’, meaning tracking is enabled.
Exactly. If ‘Validate From List’ is unchecked, the parameter value is not validated against the LOV, and the use of wildcards, such as ‘%’ or ‘_’, is allowed. This behavior is part of how the Parameter Type definition controls validation at run-time.
This behavior is determined by the ‘Validate From List’ setting on the shared List of Values (LOV). If this setting is checked, the parameter validation enforces the selection of one record from the LOV and does not allow the use of wildcards.
This can be useful for development where it might not be desired to keep automated track of the relationship between original and copied reports.
Yes, you can use the profile option ‘Blitz Report Disable Copied From Tracking’. Setting this to ‘Yes’ disables the population of the ‘Copied From’ field when reports are copied.
Yes, for better import performance, it is recommended to create an index on `eul5_documents.doc_name` . The suggested index creation statement is: `create index .xxeul5_documents_n1 on .eul5_documents (doc_name) tablespace apps_ts_tx_idx;` .
If you are not seeing current worksheet SQLs or execution history, it indicates a failure in the mechanism that updates the `AMS_DISCOVERER_SQL` table . This table is updated when a worksheet is saved, triggered by a Discoverer database trigger called `eul_trigger$post_save_document` . If this trigger does not exist or fails to call the underlying PL/SQL function (`AMS_DISCOVERER_PVT.EUL_TRIGGER$POST_SAVE_DOCUMENT`), the SQLs won’t be available for import .
Yes, a viable alternative is to shift the resource-intensive audit reporting load entirely off the production instance . This can be achieved by running your Blitz Reports on an Active Data Guard standby server . Alternatively, you can move the audit data to a dedicated operational data store for reporting purposes .
It is mandatory to test the index creation in a test instance first . DBAs must verify two things: 1) Measure the performance and execution plan of an audit report before and after indexing . 2) Test if the EBS transaction performance for the base tables did not decrease significantly . Indexes on shadow tables require resources for maintenance (insertion/update during transactions) and may slow down production transaction performance .
You need to verify two critical profile settings, typically found in the `[Database]` section or the registry key path `HKEY_CURRENT_USER > Software > Oracle > Discoverer 11 > Database` . The keys `QPPEnable` and `QPPCreateNewStats` must both have their values set to ‘1’ . Additionally, within Discoverer Admin, you must enable ‘Collect Query Statistics’ for all users whose statistics you want to track .
Yes, if you set ‘Display Site Pricing Differences’ to ‘Yes’, the report checks pricing at both the Customer Account and the specified Ship To/Bill To Locations.
The Blitz Report Discoverer import heavily relies on execution statistics stored in the database table `EUL5_QPP_STATS` . To ensure this table is populated, users must properly exit Discoverer Desktop or Plus using the File > Exit menu (not just closing the window) , . For Discoverer Plus and Viewer users, specific settings must be verified in the server configuration file (`pref.txt`) , .
Yes, indexing the `audit_timestamp` column is also highly recommended , . This is because most audit reports restrict data selection based on the transaction time . Creating an index on this column (e.g., `on ap.ap_suppliers_a (audit_timestamp)`) will significantly speed up queries filtered by time range .
No, if you only need the summary, run it in Summary Mode. This displays a summary of Applied Price Lists, List Price, Adjustment Amount, Final Unit Selling Price, Item Cost, and Margin.
Performance optimization for large audit tables is crucial . It is strongly recommended to create indexes on the primary key columns and the `row_key` column of the shadow tables . For example, on `AP_SUPPLIERS_A`, an index on `(vendor_id, row_key)` is beneficial because audit queries often link sequential changes for a single record using the `row_key` .
Yes, Event 10946 should be set in both primary and standby databases, as explained in Oracle documentation, to support this configuration.
Use the QP Customer Pricing Engine Request report. Run it in Detail Mode to get a breakdown of the Price List and Modifier Lines the pricing engine applied, as well as Pricing Attribute and Qualifier Attribute details.
On the Blitz Report setup window, under Report Options, you specify the TNS descriptor of the standby database in the ‘Target Database’ field. This descriptor must be defined in $TNS_ADMIN/tnsnames.ora on the application server.
The QP Price Lists report is the correct master data report for showing the setup details of price lists.
Running reports on a standby database requires Oracle 19c or higher with Active Data Guard licensed and configured. The key database object needed is the xxen_adg database link, which must be created in the primary database APPS schema and point to the standby pluggable database (PDB).
Yes, the QP Pricing Attribute Definitions report lists the Pricing and Qualifiers Attributes defined for use by Advanced Pricing.
For pricing agreements, run the QP Pricing Agreements report. This details the QP Pricing Agreements defined.
The parameter name must be the name in the installed base language (usually US), prefixed with a colon, and with spaces or other non-word characters replaced with a single underscore (e.g., :$flex$.operating_unit).
Precisely. Defining and saving that utility report within Blitz Report allows the DBA to execute it directly from the Forms interface without needing database login or OAM navigation , showcasing the simplicity Blitz Report brings to DBA tasks.
The QP Price Lists report is the comprehensive master data report for showing this setup.
Yes, if the Blitz Report menu entry is hidden (e.g., by running ‘Blitz Report Update Menu Entries’ concurrent program without a menu entry prompt), Blitz Report can still be run exclusively from the Excel icon in the top menu of the Oracle Forms navigation, which is where the custom icon functionality resides . The Form assignment feature is key to enabling access in this scenario .
The default value should start with ‘select’ if it is derived dynamically. An example using concatenation might be: select :$flex$.operating_unit||’ suppliers’ from dual.
Yes, Blitz Report is completely free to use for your first 30 different reports. This complimentary usage tier allows you to conduct a full Proof of Concept (POC) immediately.
In addition to zero concurrent program registration, Blitz Report handles version control automatically for every report definition, preventing duplication and maintaining a stable codebase with audit history. This is essential for maintaining control over custom SQL assets.
To define parameter dependencies in default values, you must use the syntax: :$flex$.parameter_or_lov_name.
The precise action depends on how the assignment is configured . When accessing the report from the Oracle standard form through the custom icon, the report typically launches directly with parameters defaulted as defined in the assignment . If the underlying PL/SQL uses the synchronous `XXEN_API.RUN_REPORT` or a simple `fnd_request.submit_request` call with pre-defined parameters, the report executes immediately , .
The interface is standard Oracle EBS Forms. The tool adopts the EBS user interface to minimize training, ensuring users are immediately familiar with it. It resides in standard Forms, requiring virtually no new commands to learn.
If the Blitz Report should be available on all blocks of the assigned form, and the parameter values being passed are identical regardless of the block, you should leave the Block Restriction empty . If the parameters need to be derived from different item names depending on the current block, you might need separate logic, possibly handled within the PL/SQL execution itself .
All report definitions are centrally managed and exist in a version-tracked Blitz Report table. This provides developers and IT teams with full version control, audit history, and prevents duplication of effort. Every modification is logged with audit comments.
It applies universally. Whether you create a new report in minutes or import a complex BI Publisher report complete with parameters , the key administrative benefit holds true: there are no new concurrent programs to register per report. This dramatically simplifies the maintenance workload for IT teams.
If the custom icon is not appearing after defining the Form Assignment, you must rigorously re-verify your configuration . First, ensure you correctly identified the standard form name using Help > About Oracle Applications . Second, check the Block Restriction field . If you entered a block name (e.g., GL_JE_BATCHES) in this field, the icon will only appear when the user navigates to that specific block . If you intended it to appear globally on the form, ensure the Block Restriction field is empty .
Blitz Report is implemented as an add-on that utilizes the application foundation functions, including the Concurrent Request framework. Instead of registering each individual report as a unique program, Blitz Report leverages its own highly optimized execution engine which is already integrated, allowing it to interpret the saved SQL definition and execute it as a concurrent request seamlessly.
No, this is a core administrative benefit. Once the SQL is pasted and saved in Blitz Report, you do not need to register the report in system admin or deal with the typical hassle of registering new concurrent programs and reports. Blitz Report manages the execution automatically through the concurrent request mechanism.
Yes, this is a core efficiency feature of Blitz Report. A key benefit is the ability to create new operational reports quickly without the hassle of registering new concurrent programs and reports. The report runs immediately through the concurrent requests mechanism, and you do not need to register the report in system admin.
The deployment is designed for speed and minimal overhead. The installation process typically takes less than 15 minutes. Furthermore, we offer a complimentary, 30-minute guided installation with your DBA team to get you started immediately.
The key parameter is `pga_aggregate_target`. For 1001-2000 users, a recommended value is around 20G.
The function is primarily designed to prevent immediate, accidental double-clicks.
No, the tuning documentation specifies that while SGA allocation benefits from large/huge pages, PGA allocation does not benefit from this configuration.
The default setting is ‘Yes’ (meaning the button is disabled).
Yes, a developer can define a Default Value for a parameter. If the value starts with the keyword ‘select’, Blitz Report executes the SQL to derive the default value dynamically instead of using a fixed value. For instance, `select to_char(sysdate, ‘MON-RR’) from dual` to get the current date.
Use the DBA AWR PGA History report. This report shows the history of database PGA size and other relevant statistics, retrieved from `v$pgastat` and displayed in megabytes.
By default, the Run button is disabled after report submission to prevent accidental resubmission. To keep the run button enabled all the time, switch the profile option ‘Blitz Report Disable Run Button after Submission’ to ‘No’.
The system would typically load the most specific default. If you select a template, the Template Parameter Defaults would likely override the general User Parameter Defaults for those specific parameters.
Yes, if there are columns used internally for processing (such as temporary keys) that the user does not need to see, you can check the ‘Hidden’ box in the Upload Columns list . This makes the columns invisible in the Excel file template .
Yes, once a template is selected, you can store default parameter values specifically against that template. Use the menu option Actions > Save Template Parameter Defaults. This ensures that the relevant defaults load when the template is chosen.
You can store your personalized default parameter values using the menu option Actions > Save User Parameter Defaults. These saved values will automatically populate the parameters the next time you open that report.
You should check the ‘Read Only’ box against the `CREATION_DATE` column in the Upload Columns list . Checking ‘Read Only’ prevents the column from being updated . Conversely, checking the ‘Required’ box ensures that records are not marked for processing in the Excel file until all mandatory columns are populated .
The report output, which is provided in an Excel file, can be emailed to the relevant teams automatically to facilitate immediate action. There is also an `Incremental Alert Mode` parameter which ensures the report only shows requests processed since the last scheduled report run, preventing duplicate notifications.
Yes, you can enable the `Show active session SQL Text` parameter, which includes an additional column with the active SQL text. This ID can be further analyzed using other Blitz Reports, such as those included in the DBA AWR SQL Execution Plan History diagnostic package.
To establish a dependency between columns within the Excel upload, you use the syntax `:$column$.column_name` . This differs slightly from the parameter dependency syntax (`:$flex$.`) . For instance, an Item Description LOV might depend on the Item number entered in an adjacent column using `msiv.segment1=:$column$.item` within the LOV query .
If the resulting directory does not exist on the filesystem, it is created. You must ensure that the apps owner has the required permissions for the directory creation.
Oracle E-Business Suite reporting straight into Excel: 2,900+ ready-made reports, your own SQL, 150+ Excel uploads.