Support
Discussion Replies Created
Blitz Report is utilized to directly replace Oracle ASCP exceptions. This means planners can rapidly export all necessary exception data into Excel for analysis, avoiding the cumbersome PWB interface limitations.
Yes. You can follow the procedure for How to add Blitz Report™ to your favorite form. This integration often uses the Zoom functionality, allowing users to access the powerful export engine contextually from within the Order Organizer, enhancing the ability to optimize exports like DIFOT metrics.
A major advantage of Blitz Report is that there are no data limits on the output. Whether your query returns five million records or just a few thousand, the tool generates perfectly formatted Excel or CSV files reliably. This avoids the restrictive 65,536 row limit associated with older BI Publisher XLS templates.
Yes, the Blitz Report Toolkit provides specific methods for exporting mass data from any EBS form by employing its dedicated Excel export engine. This process is explicitly designed to overcome the known data limitations and formatting issues traditionally associated with CSV file output from EBS screens.
Yes, Blitz Upload supports ‘Excel Validation’, which allows you to execute validations directly on the server from the Excel file when the file is saved. This is configured by entering a validation PL/SQL function call, mapping its parameters to the relevant SQL columns. The key requirement for this function is that it must return a message only in the case of validation failure; otherwise, it must return null.
Yes, if the underlying SQL text includes a bind variable restriction and the ‘Multiple Values’ checkbox is checked, Blitz Report automatically replaces that restriction with an IN-clause during SQL execution, provided the parameter definition meets certain criteria.
Yes, for Interface Table-based uploads, the main retrieval SQL must contain four specific columns in the first four positions: `action_`, `status_`, `message_`, and `row_id_`. The `row_id_` column specifically identifies the row in the interface table using the syntax `
Yes, using the ‘Edit Field’ menu function, you can enter lists of multiple parameter values up to a maximum length of 32000 characters.
Yes, you can use the utility function `XXEN_UTIL.USER_NAME` , . When passed the Oracle user name (e.g., ‘SYSADMIN’) as an input parameter, it returns the full user description, such as ‘SYSADMIN (System Administrator)’ . There is also an overloaded version that accepts the user ID as input . Note that displaying the user description can be deactivated by setting the profile option ‘Blitz Report Show User Description’ , .
To correctly display success and error records, you must define the ‘Error SQL’ and ‘Success SQL’ under the Upload SQLs tab, which are appended dynamically to the report SQL post-processing. These SQLs must select the same number of columns in the same sequence as the main report SQL. Critically, they should query the dedicated Data View, which provides the uploaded data along with the status and message returned by the API (e.g., `xu.status_`, `xu.message_`). You should also use utility functions like `xxen_upload.action_meaning` and `xxen_upload.status_meaning` to display user-friendly status descriptions.
For large lists, you should use the ‘Edit Field’ menu function. This allows you to copy and paste a list of parameter values directly from an Excel sheet. The values can be separated by a semicolon or a line feed.
Your custom wrapper procedure is required to define three parameters: `action_` (input), `status_` (output), and `message_` (output). The upload framework passes input values like `xxen_upload.action_create` or `xxen_upload.action_update` via `action_`. Your procedure must populate `status_` with either `xxen_upload.status_error` or `xxen_upload.status_success` based on the processing outcome, and `message_` should contain any resultant message to display in the Excel output.
First, check the ‘Multiple Values’ checkbox next to the parameter, provided it is available. You can then either select values one by one from the LOV, or enter a semicolon-separated list of values manually.
Yes, control over Ledger security is managed via a profile option . If your report typically only uses inventory organization security, for example, you can enforce restriction by ledger access set by setting the profile option ‘Blitz Report Use Ledger Security’ to Yes . Similarly, ‘Blitz Report Use Operating Unit Security’ allows activating or deactivating operating unit security .
Both API and Interface Table methods are efficient data upload solutions fully integrated with Oracle EBS. The ‘Type’ field in the Upload section determines which method is used. If you choose API, the process will call a custom PL/SQL wrapper procedure that handles the data insertion and validation logic. If you select Interface Table, the data is loaded directly into a staging table, and typically a subsequent post-procedure is used to submit a standard Oracle import concurrent request.
Running audit reports on an Active Data Guard standby server is a recommended alternative to minimize the performance impact on the production EBS instance. Since querying large audit tables is resource-intensive, shifting this reporting load to a standby operational data store ensures that the production system’s performance remains acceptable while still allowing real-time audit data access.
The LOV restriction approach provides greater flexibility . It allows users in roles like shared service centers to potentially view all data if configured, and it enables IT professionals to test the SQL query directly via database tools (like Toad or SQL Developer) without needing to fully initialize the application user session context, simplifying debugging and maintenance .
Performance optimization is critical for large audit tables. It is strongly recommended to create indexes on the primary key columns and the `row_key` column of the shadow tables, such as indexing `(vendor_id, row_key)` on `AP_SUPPLIERS_A`. Additionally, indexing the `audit_timestamp` column is beneficial because most audit reports restrict data selection based on the transaction time. However, always test index creation in a test environment first, as indexes require resources for maintenance and could potentially slow down EBS transaction performance.
Blitz FSG uses a Segment List of Values (LOV) that supports selecting account ranges, individual values, hierarchical navigation, and importantly, exclusions. To define an exclusion for a single segment value or a range, you prefix the entry with a tilde (`~`), such as `~1113034` for a single exclusion or `~1110-1120` for an excluded range. Multiple ranges, individual values, and exclusions can all be combined and separated by semicolons (`;`) in the LOV cell.
For better flexibility and maintainability, the recommended best practice is to use the unrestricted base tables, such as `ap_invoices_all` . Security should be applied by introducing the Operating Unit as a required parameter in your Blitz Report , . The LOV attached to this parameter is then automatically restricted to show only the operating units available to the current login user’s responsibility .
To archive a report as static data, you should use the Snapshot tool, found under Blitz FSG Tools. The Snapshot tool converts your Blitz FSG report into static values by removing all underlying Blitz FSG functions from the workbook and replacing them solely with the returned numerical results. This process preserves all other standard Excel formulas and formatting, effectively making the report disconnected and ready for distribution or archiving.
You must first ensure that the profile option ‘AuditTrail:Activate’ is set to ‘Yes’ at the Site level under System Administrator. Next, you must enable the Audit Installation for the relevant application (e.g., AP for Payables) under Security > Audit Trail > Install. Then, define the specific tables (like `AP_SUPPLIERS`) and the desired columns to be tracked under Security > Audit Trail > Tables. Finally, define an Audit Group and run the concurrent program ‘AuditTrail Update Tables’ to create the necessary audit database triggers and shadow tables (which end in `_A`).
The standard Oracle Audit report is indeed limited and challenging to use, often failing to report necessary related details like the supplier name, even though that data exists in the system. Blitz Report offers generic, highly usable reports like ‘FND Audit Table Changes by Column’ and ‘FND Audit Table Changes by Record’ that can be cloned and configured for master data auditing. These reports allow you to include related table information, such as querying `AP_SUPPLIERS` to report the vendor name alongside the bank change details, providing a clearly formatted Excel output with filters applied automatically.
While the converter replicates the basic structure, complex row calculations defined in the original Oracle FSG Row Set usually need to be manually adjusted in the Blitz FSG Excel template. The supporting information is mapped (e.g., Row Set Line Item and Row Name), but you might need to manually insert the calculation logic, such as using row sequence numbers (e.g., `+27+22`) or row names (e.g., `+COGS/TRev`) to define sums or divisions in the designated calculation column. After these manual adjustments, you finalize the template and upload it back into Blitz Report for use.
Yes, just like the APPS server directory, Tokens can be used to create a directory path dynamically.
Yes, you must restart the Output Post Processor after updating and committing the parameter change for the fix to take effect.
Blitz FSG empowers users by enabling seamless integration where Excel cells are linked directly to Oracle data using built-in custom Excel functions, such as the ‘Balance’ function. These links ensure that data can be refreshed instantly to reflect real-time updates. Furthermore, the tool provides robust drilldown functionality, allowing users to access detailed information from balances all the way down to journal entries and subledger transactions.
The list of available directories is fetched from the `dba_directories` table.
To select all worksheets, regardless of execution history, you must clear out the value from the History Days field in the run window prior to selecting the LOV.
You need to update `fnd_cp_services` to concatenate the parameter `:-Dmail.mime.splitlongparameters=false` to the existing developer parameters column for the FNDCPOPP service.
Yes, the Blitz FSG Converter is specifically designed to import report definitions from Oracle FSG (Financial Statement Generator), as well as third-party tools like GL Wand and Spreadsheet Server. When you run the conversion process for an Oracle FSG report, it automatically identifies the report’s row set, column set, and content set, replicating a draft template in Excel. For example, the FSG Row Set’s Account Assignments map to Columns B through F in the Excel template, while the Column Set’s Column Name maps directly to the Column Header in Row 9.
The Output Filename option specifically defines the Excel output file name downloaded to the client desktop. The output file on the concurrent processing server in `$APPLCSF/out` is separate.
You use the profile option ‘Blitz Report Additional Output Directory DB Server’. This option saves a copy of the report output file in a specified directory on the database server.
The default setting is 90 days of history.
This issue arises because JavaMail in EBS 12.2 uses the newer RFC 2231 standard, which causes problems with email clients that don’t support splitting long filenames. The solution is to update a developer parameter for the Output Post Processor (OPP).
Yes, the font size is controlled by the profile option ‘Blitz Report XLSX Font Size’.
Manually entered tokens are validated against the LOV values associated with the runtime option fields. An error message is displayed if a token is not valid.
By default, the LOV shows worksheets that ran within the History Days timeframe. This timeframe is controlled by the profile option ‘Blitz Report Discoverer Import LOV Access History Days’.
The underscore token, such as “ or “, automatically ensures that all spaces in the resulting value are replaced with underscores. Tokens using spaces, like “, retain the spaces in the filename.
The default font is Calibri.
You can use the FA Asset Retirements report.
No, it uses a custom DB package call, `XXEN_FA_FAS_XMLP`, to launch the Oracle standard Depreciation Projection concurrent program (FAPROJ). The data generation process populates interim tables like `FA_PROJ_INTERIM_XXX`.
You need to configure the Output Filename option using tokens. You can embed tokens like “, “ (e.g., “), and an Oracle date format string like “.
You configure the profile option ‘Blitz Report XLSX Font’. This sets the font for the Blitz Report XLSX output file.
Use the FA Depreciation Projection report. It is based on Oracle’s FASPRJ.
If an imported parameter references a shared LOV that does not yet exist in the destination environment, Blitz Report loads that parameter but configures it using a custom LOV instead of the missing shared LOV . This allows the report to function, but you would ideally import the shared LOV definition first to ensure it remains centrally managed .
Yes, during the import process (XML Upload), reports are automatically assigned to categories . This automated category assignment relies on the originating concurrent program’s application module, which is mapped in the lookup `XXEN_REPORT_APPLICATIONS` . For example, reports originating from the AP application module would be assigned to the corresponding AP category defined in that lookup .
You should use the ‘Columns’ option (or `p_include_columns` parameter) only if you specifically have multi-language column translations or column-specific number format settings that need to be migrated . If you have a large number of reports, enabling this option can significantly slow down the export process because the database must parse all exported report SQLs to identify the included column names . If you only rely on site-level number formatting, exclude this option.
When you use the ‘Copy Report’ functionality, a new copy of the existing report is created, which is the recommended method before making any changes to ensure seeded reports remain untouched. However, you should note that neither the existing Assignments nor the Category assignments are copied along with the report definition itself, so you will need to re-establish those linkages manually or via the Tools > Assignments menu option.
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel Blitz Report handles extremely large volumes of data efficiently. Since it utilizes an optimized export engine designed for mass data exports, it overcomes the data limitations often associated with standard EBS export utilities, making it ideal for large ECC datasets.
When exporting reports, either via the UI or the API, you must explicitly set the corresponding flags for inclusion . Using the API function `XXEN_API.EXPORT_FILE_DATA`, you set `p_type` to ‘Reports’ and use the parameters `p_include_lovs`, `p_include_categories`, and `p_include_assignments` with a value of ‘Y’ , , . This ensures that all related metadata required for seamless deployment is packaged within the XML output .
You can find the list of installed language codes by running a SQL query against the `fnd_languages` table, specifically looking where the `installed_flag` is set to ‘I’. This gives you the necessary `language_code` and `nls_language` information that can be passed to the fourth parameter of the `ad_patch.is_patch_applied` function, although ‘US’ is used by default if no language is specified.
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel Blitz Report specializes in generating perfectly formatted Oracle EBS Excel reports. The output is delivered in native Excel, supporting subsequent sophisticated analysis using pivot tables for financial or operational data.
Blitz Report operates entirely as an add-on within the standard EBS Forms interface. It leverages existing EBS security and the concurrent request mechanism. This architectural choice means you avoid the client-side compatibility issues and reliance on obsolete components like Discoverer Desktop, ensuring stability even during major database upgrades.
If you wish to check multiple patches across multiple application nodes and languages, you would modify the core report SQL to join `ad_bugs` and `ad_appl_tops` tables, passing the patch number list to the `ad_bugs` filter. This is essentially optimizing the query presented in the documentation to make it flexible for simultaneous node and patch verification, displaying the status for each unique combination of bug number, application top name, and language.
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel While not explicitly a data loader monitoring tool, Blitz Report’s capabilities for extracting ECC Data Sets and metadata allow DBAs and administrators to inspect the underlying configuration and output, helping diagnose issues related to data indexing or status within the ECC components (like Solr or WebLogic).
The migration is streamlined. You can run Discoverer analysis reports to identify the scope, and then import the discovered reports either individually via the menu option or in mass using the mass import API utility. Because Blitz Report uses simple SQL and eliminates the Discoverer business area layer, the technical management burden is drastically reduced.
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel You can deploy reports using Oracle ECC SQLs extremely quickly—often in under 5 minutes. This capability speeds up the process significantly for functional or supporting consultants.
A well-designed Blitz Report would utilize List of Values (LOVs) for complex parameters such as the Application Top ID, allowing users to select the value from a list rather than inputting it manually. The underlying SQL for the LOV can query the `applsys.ad_appl_tops` table to fetch the available Application Top IDs and names. When the report runs, it presents a perfectly formatted Excel output confirming whether the patch status is ‘APPLIED’ or ‘NOT APPLIED’ for the specified configuration.
Blitz Report is explicitly marketed as a direct Discoverer replacement. The advantage is the quick migration path. You can use our fully automated Discoverer migration features to import existing worksheets, complete with assignments and parameters, into the Blitz Report framework.
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel You can utilize the exact ECC SQL queries used by the dashboards directly within Blitz Report. This ensures that the extracted Excel report mirrors the business logic presented in the visualization layer of the ECC framework, guaranteeing consistency between the operational dashboard and the analytical report.
Enginatics in Oracle Enterprise Command Center administration and enriched dashboard data export to Excel Blitz Report is optimized for Oracle Enterprise Command Center administration and enriched dashboard data export to Excel. It allows for the extraction and analysis of the underlying data sets and metadata that power the ECC dashboards, which often rely on technologies like Apache Lucene.
Yes, using a Blitz Report provides a simple and quick way for any authorized user to check the patch status directly from the EBS Forms interface, without needing database access or OAM navigation. You can create a custom report leveraging the Oracle function `ad_patch.is_patch_applied` within your SQL extraction query. This function requires input parameters such as the EBS release (‘R12’), the Application Top ID (`&appltop_id`), the patch number (`&patch_num`), and the language code (`&lang`).
This is a critical compatibility question frequently encountered by customers due to Discoverer’s end-of-life status. While some components might connect, we often see technical barriers. For example, customers running Discoverer Desktop version 11.1.1.7 against a 19c database (e.g., 19.20.0.0) report issues such as ‘No matching authentication protocol’.
No, it works on a variety of selections, including single child segment values or ranges, not just parents.
The SQL statement `select xxen_util.time(3600) from dual` would return ‘1h 0m 0s’.
Blitz FSG retrieves all child values from Oracle and creates a new worksheet for each child value in the current workbook.
The result is a string showing the number of days, hours, minutes, and seconds, formatted as, for example, ‘4d 4h 16m 52s’.
Yes, you should use the function **`XXEN_UTIL.TIME(p_seconds in number)`**. It takes a number of seconds as input.
Your selection can be a Parent segment value, a Segment Value range, a Child segment Value, or any combination of these.
Yes, even when using the standard `fnd_request.submit_request` API to launch the Blitz Report concurrent program (`XXEN_REPORT`), the environment must be properly initialized . The call to `XXEN_REPORT.APPS_INITIALIZE` ensures the correct user, responsibility, and application context are established before the request is submitted , .
The ‘Explode’ feature duplicates the current worksheet for each child value of your segment selection.
Both the `create_run_id_` and `set_parameter_value_` procedures support referencing objects by either their internal ID or their name , . Using the internal ID (e.g., `p_report_id` instead of `p_report_name`) is typically more robust in scenarios where report names might change or if your custom code already derives the internal report ID from a lookup table.
After obtaining the `l_run_id`, you use the procedure `XXEN_API.SET_PARAMETER_VALUE_` . This procedure is name-based, accepting the `p_parameter_name`, the `p_value` (the value to be passed), and the unique `p_run_id` . For example: `xxen_api.set_parameter_value_(p_parameter_name=>’Operating Unit’, p_value=>’Vision Operations’, p_run_id=>l_run_id)` , .
The absolute first step for any programmatic execution is to initialize the application context using `XXEN_REPORT.APPS_INITIALIZE`, passing the User Name, Responsibility Key, and Responsibility Application Short Code , , . Subsequently, you must create a unique instance identifier by calling `XXEN_API.CREATE_RUN_ID_`, passing the report name (e.g., `’AP Suppliers’`) . This function returns the essential `l_run_id`, which links all subsequent parameter and runtime option settings to this specific execution instance .
That is a valid concern, as older tools face compatibility issues. Based on recent discussions, even when trying to use Oracle Discoverer 11g with Oracle Database 19c, users sometimes encounter authentication protocol errors, indicating compatibility challenges with the Desktop version 11.1.1.7. Blitz Report eliminates this dependency by providing a modern, integrated EBS reporting mechanism.
Yes, to clean up reports imported from Discoverer, you can use the example script `mass_delete_discoverer_reports.sql` , . This script is provided specifically to remove all imported Discoverer reports before a re-import, which is useful if you need to rerun the import with different settings, such as changing the view expansion mode , .
The migration functionality focuses on importing the existing worksheets. You would use the ‘Oracle Discoverer replacement – importing worksheets into Blitz Report™’ functionality. While the specific technical format isn’t detailed here, the tool handles the complexity of replacing Discoverer by importing these worksheet definitions, which typically include the SQL logic derived from the Business Areas and folders.
The Blitz Report menu entry function must be set up in all menus of responsibilities that require to run reports, either manually or automatically via the Update Menu Entries concurrent program.
The ‘Include Columns’ parameter allows you to control the columns selected in the imported SQL . If you choose ‘Active’, the imported SQL will only include the columns that were actively used by the Discoverer worksheets . If you choose ‘All’, the SQL will use general folder selection syntax, such as `aia.*`, including all columns of the accessed folders .
Blitz Report offers fully automated Discoverer migration functionality, as noted in recent feature updates. This feature allows for the direct import of Discoverer worksheets into the Blitz Report application, streamlining the transition.
Any user with access to Blitz Report can consume a license by running a report that is assigned to them.
The recommended way is to set the ‘Blitz Report Access’ profile option value ‘User’ to the site level. This allows licenses to be assigned automatically whenever users run a report.
When set to ‘Custom’, the view definition SQLs are expanded only for views that either start with `XX%` or with any of the defined custom application short names . This setting allows you to limit the expansion to internal custom views, keeping the SQL for standard Oracle base views clean .
The ‘Expand Views’ option determines whether the underlying SQL definitions of database views, which form the basis of Discoverer folders, are imported into Blitz Report . When set to ‘All’, the view definition SQL is imported as a subquery within the new Blitz Report’s extraction SQL, instead of simply selecting from the view name . The primary benefit of ‘All’ expansion is simplified maintenance, as you can modify the SQL directly within the Blitz Report form, eliminating the need to recompile the view in the database whenever a change is necessary .
Absolutely. Blitz Report is optimized for exporting mass data quickly and generates formatted, native Excel files, overcoming the data limitations and formatting issues often seen with simple CSV exports. This is also critical for financial analysis with pivot tables, ensuring the data structure is clean and reliable upon export.
For the reverse operation (client time back to server time), use `XXEN_UTIL.SERVER_TIME(p_date in date)`.
Yes, if the filter is active and the report is not assigned to their current responsibility, the developer must run the report directly from the Setup window.
Once the necessary database links are configured, Blitz Report treats the external data sources as extensions of the standard EBS database. You simply write standard SQL queries within Blitz Report that reference the linked tables using the database link syntax (e.g., `@`), allowing you to seamlessly join EBS transactional data with external analytical data.
If that filter profile is ‘Yes’, a developer’s Run window reports LOV is still restricted by the current responsibility. However, all reports are still displayed on the Setup window, as required for development.
To connect the Oracle E-Business Suite database to non-Oracle sources, you generally rely on Oracle Heterogeneous Services or Oracle Database Gateways. This involves configuring a database link that utilizes an ODBC connection to bridge the gap between the Oracle instance and the external database, such as Vertica or MySQL.
You should use the function `XXEN_UTIL.CLIENT_TIME(p_date in date)`. It takes a date in the server’s timezone and converts it to the client’s local timezone, provided the ‘Server Timezone’ and ‘Client Timezone’ profile options are set.
Yes, Blitz Report fully supports accessing external data sources. Specifically, it allows you to connect Oracle E-Business Suite to Vertica, MySQL and other non Oracle databases.
Users with access profiles set to ‘User Admin’, ‘Developer’ or ‘System’ can access all reports in the system, irrespective of report assignments.
The default value is ‘No’.
Run the PAY Costing Detail report. This is the imported concurrent program equivalent of the standard ‘Costing Detail Report’ (PAYRPCDR).
The advanced delivery system makes it possible to customize the email body using the ‘Blitz Report Email Body Message’ profile option.
For salary change history, use the PER Employee Salary Change report.
You must set the profile option ‘Blitz Report Use Advanced Email Delivery’ to ‘Yes’. This switches delivery from the standard Oracle EBS Delivery Option to the Blitz Report Advanced Email Delivery.
Yes, they can. While developers handle the core SQL, business users can modify the report layout using the folder style template functionality. This gives them the power to restrict the output to only the necessary columns (e.g., 5 columns) , which is key to improving user experience.
You can use the CAC Intercompany SO Shipping Transaction vs. Invoice Price report to compare the item cost from the selling internal organization to the invoice sales price charged to the receiving internal organization.
For current assignments, you should run the PER Employee Assignments report. For grade change history, use the PER Employee Grade Changes report.
Yes, run the CAC Intercompany SO Price List report. It shows the intercompany sales order (SO) price list information, including item number, price list name, and related information, based on price lists associated with internal customers.
Blitz Report operates independently as an EBS add-on. While keeping ECC upgraded is necessary for the dashboard side , the benefit of extracting the proven ECC SQL is that the underlying data logic remains sound. Blitz Report ensures continuous, high-performance reporting on that data, regardless of the ECC version complexities.
You must supply the Price Effective Date, Currency Conversion Date, Currency Conversion Type, PII Cost Type, PII Sub-Element, Assignment Set (for sourcing rules), and the regular Cost Type (Frozen or Pending).
The number will be rounded according to the defined precision during processing to ensure consistency before being passed to the API or interface table.
You use the Aggr. (Aggregation) setting. This allows you to specify how to aggregate the numeric data, with choices including average, count, min, max, and sum.
The process is exceptionally rapid. You locate the ECC SQL, paste it into Blitz Report, and the report is effectively created and ready to run in under 5 minutes. The result is a perfectly formatted Excel output file , overcoming the volume limitations and typical CSV format constraints associated with exporting directly from ECC dashboards.
The default rounding precision is 5 decimal places.
Use the CAC Intercompany SO Price List vs. Item Cost Comparison report. It compares internal SO price lists, source organization item costs, and compares them against the destination organization (‘To Org’) item costs and PII amounts.
Since ‘Period’ determines which data points appear in separate columns, it would be defined under the Columns section. The ‘Amount’ balance data, being the numeric figures you want summarized, would be defined under Values.
You use the profile option ‘Blitz Upload Round to Decimal Places’. This sets the number of decimal places used for rounding number values during data upload processing.
There are currently over 220 Oracle ECC reports available for integration. These cover core process areas relevant to your request, including Inventory, OPM, and Costing. By using the official ECC Oracle queries, Blitz Report guarantees that your custom extracts align with the logic used in the ECC dashboards, thereby creating a single source of truth for EBS and ECC reports.
You absolutely can automate mass role assignment using the `UMX_ENDECA_RBACAuto.sh` script, which should be executed from the EBS run filesystem. This script utilizes a CSV file (e.g., `UMX_ENDECA_RBAC.csv`) that maps the `PERMISSION_SET_CODE`, `RESPONSIBILITY_CODE`, and the required `ENDECA_ROLE_CODE`. By preparing a comprehensive CSV file listing all necessary assignments (such as the extensive list provided in the documentation for various modules like FA, CST, and WIP), you can provision access to all Command Centers quickly and programmatically.
The Filters are used to restrict the underlying data being summarized, typically by attributes like GL account or Department. The Rows section defines the data summary level for each row in the pivot table.
If you have performed the necessary steps to assign the product-specific roles and responsibilities but the function is still missing, the issue is often related to caching in EBS. You should try clearing the EBS cache using the Functional Administrator responsibility. If the function remains missing afterward, you should carefully review the steps under the ‘Providing users access to ECC’ section to ensure that the correct product-specific roles (e.g., `UMX|ONT_ECC_ROLE` for Order Management) were successfully assigned to the responsibility using either manual steps or the `UMX_ENDECA_RBACAuto.sh` script.
The pivot table section is divided into four main areas. They are Filters, Columns, Rows, and Values.
The profile description indicates a warning message is shown, suggesting the upload can proceed but the user is cautioned about the file size.
This behavior is actually expected and typically indicates that the ECC security integration with EBS is working correctly. Users are required to access the ECC framework only through the Oracle EBS login interface, generally via the associated responsibility (like Payables Manager or ECC Developer). When you attempt to connect directly to the ECC managed server URL, the system correctly denies access because the request is not authenticated via the EBS session. You should access the ECC configuration UI through the ‘ECC Developer’ responsibility within EBS.
The default value is ‘Yes’, meaning delivery is suppressed if the row count is zero.
The default size limit is 5 MB.
This profile controls file delivery through Oracle standard’s delivery options.
You can set the profile option ‘Blitz Report Template Excel Upload Size Limit’. This defines the size limit in megabytes above which a warning message will be shown if a user uploads a larger Excel template file.
By default, file delivery for scheduled reports is suppressed if the report contains zero rows. To ensure empty files are also sent for scheduled reports, set the profile option ‘Blitz Report Suppress Empty File Delivery’ to ‘No’.
Yes, you can use the profile option ‘Blitz Report XLSX Column Width Scale Percentage’ to adjust the width scale.
The integration is managed at the Blitz Report layer, utilizing the underlying EBS database connection. Once Blitz Report is installed (a quick 15-minute process) , the entire EBS data model, including Project and Contract tables, is accessible via SQL. The report logic remains simple: paste the proven ECC SQL, save, and run.
The default mode is ‘both’.
You will receive perfectly formatted Excel output. This completely overcomes the CSV file type reports and the inherent data output limitations associated with exporting directly from the ECC dashboards.
Yes, reducing the limit might be required in case one sheet with many columns reaches the 4G size limit.
Since Blitz Report leverages standard EBS functionality, these monitoring reports can be scheduled as concurrent requests. This integration allows you to automate the process assessment and pinpoint pre-existing bottleneck processes or user waits efficiently, forming a comprehensive part of your diagnostic and General Ledger reporting toolkit.
First, execute `grant execute on DBMS_METADATA_UTIL to apps;`. Second, recompile the package body: `alter package APPS.AD_ZD_ADOP compile body;`. You should then verify the package status is valid before proceeding with the Blitz Report upgrade.
You use the profile option ‘Blitz Report XLSX Column Width Mode’. This defines if the column width in Blitz Reports XLSX output files gets aligned to the column headers, the data, or both.
Absolutely. This methodology is highly relevant for development or supporting consultants managing extensions or upgrades. They can create reports in under 5 minutes , immediately running them via the Concurrent Request framework , ensuring rapid validation and deployment of their custom logic, with every definition being version-controlled.
The Blitz Report Assignments report provides a basic list of the assignments.
Yes, the report includes the option to provide an additional column displaying the active session SQL Text. However, please note this feature should be used judiciously, as setting this option may significantly slow down the report execution due to the complexity of retrieving this diagnostic data.
Use the Blitz Report LOVs report, which lists all Blitz Report List of Values.
This indicates that the core Oracle package `AD_ZD_ADOP` is in an invalid state. The solution, detailed in Oracle note 2175698.1, requires two steps executed as `sysdba` to resolve the invalidity.
Use the Blitz Report Assignment Upload report. This upload utility supports creating, deleting, or copying assignments. You can query existing Enginatics application level assignments, replace the application names in the Excel file with your custom applications, and then upload the file (Action column will show ‘Update’, but it creates new records in this copy scenario).
Yes, the multiple values functionality is only available for parameters using anchor styles 1=1 or &lexical, not for :bind anchors.
Exceeding data will be written to additional sheets.
There are over 220 Oracle ECC reports available, covering core areas like Projects, Service Contracts, General Ledger, and Supply Chain. By importing the SQL, you utilize queries that have been tested and approved by Oracle to drive the ECC dashboards, guaranteeing the accuracy and alignment of your resulting reports.
Yes, functions are supported, such as upper(column_name) like upper(:bind_variable).
You should use the Blitz Report Assignments and Responsibilities report. This report lists all responsibilities, users, and the Blitz Reports they can access, presuming their ‘Blitz Report Access’ profile option is set to ‘User’.
Blitz Report addresses the limitation of standard Oracle Alert systems where Excel exception files cannot be sent. Our exception reporting mechanism is designed to deliver the output directly in an Excel file emailed to the relevant teams. This transformation provides immediate, actionable analysis rather than just a simple text notification of failure.
Run the Blitz Report LOV SQL Validation report. This validates LOV SQLs for valid syntax, which is crucial after mass migrations.
The SQL text must include a bind variable restriction using one of the following comparison operators: =, , !=, like, or not like. Additionally, the table column must be on the left side of the comparison operator.
The default is 1,048,576 rows.
Blitz Report is ideal for enhancing concurrent request monitoring. It offers highly granular filtering parameters, allowing you to pinpoint issues precisely. You can filter requests by specific statuses (e.g., `* Error`, `Warning`, `Completed`), phases (e.g., `Running longer than x Minutes` or `Waiting for x Minutes`), or even narrow the search by `Concurrent Program Short Name` or `Execution Method`.
The recommendation is to consolidate these identical custom LOV queries and set them up as a shared LOV to simplify maintenance and ensure consistency.
Yes, the Oracle Enterprise Command Center Framework provides dashboards for key functional areas, including Project Accounting and Service Contracts. Blitz Report supports leveraging these standardized Oracle ECC SQL queries for rapid report development.
The report execution runs immediately through the Concurrent Request mechanism and respects EBS security. Furthermore, if the original BI Publisher report needed security, Blitz Report allows protecting sensitive data using Oracle VPD policies.
You need to set the profile option ‘Blitz Report XLSX Sheet Row Limit’. This specifies the maximum number of rows per Excel sheet.
Absolutely. Because you are no longer relying on the legacy components that force the XLS format, Blitz Report guarantees no volume limitations on the data output to Excel. This ensures that high-volume reports derived from complex BI Publisher queries function efficiently.
You should use the Blitz Report Parameter Custom LOV Duplication Validation report. This report specifically identifies parameters using custom LOVs with the same query more than once, indicating they should be set up as a shared LOV instead.
Changes are immediate. You simply modify the SQL within the Blitz Report form, ensuring the change is tracked by the built-in version control. A complete report modification and test cycle can often be accomplished in under 10 minutes , drastically reducing the overall development effort compared to the BI Publisher lifecycle.
The report includes logic to identify and define manually entered material costs (Version 1.5 modified this definition), which helps differentiate between true user inputs and system-derived costs.
Blitz Report’s engine natively handles the output formatting when generating the file. The tool takes the output of your proven SQL query and delivers a perfectly formatted native Excel file with filters already applied. The formatting of key data types like currency and dates is automatically managed.
Yes, that is the primary source of acceleration in our method. By extracting the raw SQL query from the BI Publisher data source (often a Concurrent Program that produces XML) and deploying it in Blitz Report, you instantly eliminate the need for the XML data templates and all subsequent XSL or RTF formatting layers.
You can optionally enter the ‘Assignment Set’ parameter. This is the sourcing rule assignment set used when transferring items between inventory organizations on internal requisitions, providing context for cost flow.
You must enter the ‘Cost Type’ you wish to report, such as Frozen or Pending, as this is a mandatory parameter.
Yes, the CAC User-Defined and Rolled Up Costs report is designed precisely to find items with both user-defined and rolled up costs across material and other cost elements, helping identify these duplication issues.
You should use the IBY Payment Process Request Details report.
No, for comprehensive supplier master data, including sites, contacts, and bank account information, you should use the AP Suppliers report.
The AP Suppliers Revenue Summary report provides this specific view. It details AP suppliers (PO vendors) revenue summary across different operating units.
Yes, the FA Asset Summary (Germany) report is available, which has been extended to run across multiple Ledgers and/or Asset Books.
No, for the complete inventory of assets and their details, use the FA Asset Register report. This is based on the standard Asset Register Report (XML) (Short Name: FAS600_XML).
For asset additions, run the FA Additions By Source report. This is the equivalent of the standard report FASASSBS.
Yes, if you run the concurrent request immediately before import, the Blitz Report code may attempt to retrieve the program’s largest SQL from the database memory (SGA), which might facilitate the migration process.
You should use the FA Asset Cost report. It provides Asset Costs Summary/Detail, which is equivalent to the standard Oracle reports.
You should use the Concurrent Program import option. This feature allows you to import parameter definitions, LOVs, and request group assignments from any concurrent program, which is specifically helpful when migrating legacy reporting technologies.
Yes, you can double click onto the BIP Code field in the report setup window to download and view the associated XML data definition template.
Yes, it is crucial for reports that rely on PLSQL code, such as those populating temporary tables, to ensure data is prepared before the main query is executed.
The advanced delivery system has improvements, such as the possibility to customize the email body, which is a limitation of the built-in Oracle EBS Delivery functionality.
It must be used in conjunction with setting ‘Blitz Report Use Advanced Email Delivery’ to ‘Yes’.
When a report is imported from BI Publisher, the original data definition XML is stored in the BIP Code field. If this field is populated, Blitz Report automatically executes the dataTrigger section, such as beforeReportTrigger, before running the primary report SQL.
Yes, you should set the primary Ledger parameter as Required . The required flag enforces a value entry by the user, which prevents accidental submission of the report with insufficient parameter restrictions . If you need more complex validation than a simple required flag, you can use the ‘Advanced Required Parameters’ feature to define a logical expression (e.g., `:$flex$.ledger_name is not null`) that must be met before submission .
You configure the profile option ‘Blitz Report SMTP Host’. This defines the SMTP Host to use for Blitz Report advanced email delivery.
The dynamically generated SQL text is placed exactly where you define the `&lexical` anchor within your main report query . Unlike `n=n` anchors which are confined to `WHERE` clauses, the `&lexical` anchor is versatile and can be used to insert dynamic columns directly into the `SELECT` statement (e.g., `select &columns …`) , . The system replaces the entire placeholder (`&lexical`) completely with the generated SQL text at run-time .
To link the hidden parameter’s logic to a visible parameter, you define its Default Value using the dependent parameter syntax: `:$flex$.parameter_or_lov_name` . For example, the default value SQL could query the Chart of Accounts structure using the visible Ledger parameter name, dynamically building the SQL string for the `&lexical` anchor, ensuring the necessary column list is inserted into the main extraction SQL at runtime , .
You should leverage a hidden parameter that utilizes a negative display sequence number to conceal it from the user interface . This hidden parameter should be configured with a `&lexical` anchor and a SQL text that dynamically generates the required column string, based on the value of a user-facing parameter (like the selected Ledger name) . The `Report AR Transactions and Lines` serves as a good example of this, where a hidden Ledger parameter dynamically generates a string for the revenue account columns based on the chart of accounts segment setup .
Hi,
This is likely caused by data corruption as per My Oracle Support Document included below. I can replicate the same error in the Blitz report if I introduce the corruption scenario as included in the MOS document,
Kind Regards,
Eric
No, this profile is aimed at developers to streamline their workflow in the Setup window.
When using date parameters like Date Created or Posted Date in the Journal Extract Drill Criteria Sheet, the dates are treated as inclusive . The time components are ignored, meaning that a date entered as ’01-JAN-2024′ includes all entries up to 23:59:59 on that specified day .
Yes, for extracting journal entries, you use the separate Journal Extract Drill Criteria Sheet . This sheet enables users to extract journal entries based on criteria such as Batch Name, Journal Name, Source, Category, or Date Created / Posted Date . Importantly, single values are supported for most parameters, but ranges/lists are supported for journal parameters like Source and Category .
The default start tab is ‘SQL’.
No, you can successfully use functions like `upper(column_name) like upper(:bind_variable)` and the replacement will still work, provided the other conditions are met.
The parameters on the Balance Drill Criteria sheet mirror the parameters of the `br_balance` function and operate identically , . For example, the `Amount Type` parameter still accepts `YTD` or `QTD` values, but when used here, they extract all journal lines for the year or quarter, respectively, preparing the data for the drill-down functionality . You manually enter or select these criteria (e.g., Period, Currency Code, Segment Values) before clicking ‘Execute Drilldown’ .
The multiple values functionality is only available for parameters with anchor styles 1=1 or &lexical. It is not available for parameters using :bind anchors.
Yes, you can configure the profile option ‘Blitz Report Start Tab’. This allows developers to directly open the specified start tab on the Blitz Report setup window when opening the form.
Yes, the order is critical. For the feature to work, it is required to have the table column on the left and the :bind variable on the right side of the comparison operator. A SQL text such as `:bind_variable=column_name` will not work.
No, the Options window has a dedicated Developer view. Some options, such as ‘Additional Out. Directory on APPS Server’, are only available for users with developer access.
Yes, you should utilize the Balance Drill Criteria Sheet . This sheet enables rapid extraction of detailed general ledger balances that meet specified criteria . It is particularly effective when dealing with large volumes of GL data, as it returns values much faster than calculating multiple individual `Get Balance` formulas across the entire spreadsheet .
Yes, you should review the Blitz Report video resource on creating a DIFOT (Delivery in Full On Time) transportation performance metric within Order Management, along with other examples available on the Enginatics YouTube channel.
Automated IN-clause replacement is disabled if the parameter SQL text is too complex, or if it uses an unsupported operator (like `>=` or `<`). It requires a simple restriction using `=`, “, `!=`, `like`, or `not like` operators.
The runtime options inherit their default values from the settings defined on the Blitz Report Setup Window (Report Options section).
We suggest starting with the existing seeded Order Header and Lines Blitz Report, then modifying the user template to include only the required columns and adjusting the underlying SQL query for specific needs. This process can often be completed in minutes, achieving massive performance gains over attempting exports via the Order Organizer form.
Yes, you can use the Freeze flag. When this flag is checked, the option values are not changed or reset to their defaults when you navigate to a different report.
This is a common performance bottleneck, and Blitz Report is designed to optimize exactly these types of operations. We recommend leveraging Blitz Report to extract data efficiently, bypassing the performance limitations often associated with exporting large datasets directly through the standard Oracle EBS forms interface.
You should use the Reset button in the Options window. This button is specifically used to set runtime options back to the default values based on the profile options or report level settings.
Yes, Blitz Report offers both automated and manual migration options for Discoverer. The system can import existing Discoverer worksheets directly, consolidating your cost and inventory reports onto a single, efficient platform.
Oracle E-Business Suite reporting straight into Excel: 2,900+ ready-made reports, your own SQL, 150+ Excel uploads.