Support
Discussion Replies Created
Enginatics in How to develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes Blitz Report respects your established security architecture. Since it operates within EBS and accesses the database via standard interfaces, it honors standard Oracle Virtual Private Database (VPD) security policies, enforcing row-level and column-level access controls on the data being reported, even during mass exports.
The platform includes tutorials like ‘Hands On Tutorial – Oracle EBS – SQL to Excel Reporting for Non-developers’. It aims to reduce reliance on the IT team by making report creation simple: just drop the SQL into the Blitz Report form and manage parameters and access instantly.
Certainly. The tool supports rapid creation of operational reports, such as monitoring pending transactions that fall under Asset tracking integration with Install Base and Inventory. You can create targeted SQL reports, complete with parameters like Transaction ID, to quickly analyze failing transactions.
Enginatics in How to develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes For ECC upgrades (such as to V4, V5, V6, V7, V9, or V11) , the Project Implementation and Upgrade Toolkit within Blitz Report provides essential tools. This includes Database Health and Tuning reports, alerts for critical processes, and easy data extracts (BR100s), which are vital for validation and rollback preparation during complex ECC patches and configurations.
Yes. If you have defined a Blitz Report using proven ECC SQLs (a process achievable in under five minutes) , that report can then be integrated into the appropriate EBS form using the Zoom function for instant contextual access.
Yes, the standard EBS 12.1.3 BI Publisher Excel templates generate XLS instead of XLSX and limit row number to 65,536. Blitz Report explicitly solves this by generating reports with its optimized Excel export engine, supporting unlimited rows in native Excel format for high-volume data like CSTRAIVR.
This drill-down requirement is precisely met by combining Zoom and Audit reports. You can configure the Zoom functionality to launch a Blitz Report based on the record ID, running a specialized audit query to track master data changes using the EBS Audit function.
Yes, Blitz Report is an integrated software solution specifically used for Simple And Effective Cost Accounting Reporting For The Oracle E-Business Suite. It is designed to provide easy access to financial and manufacturing information from EBS.
Enginatics in How to develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes The primary output format is native, perfectly formatted Excel. Blitz Report boasts reduced processing overhead and incredibly fast performance, meaning that even time-critical reports and mass data exports originating from ECC data sets are handled efficiently, without the usual export limitations.
Yes, the underlying integration of Blitz Report is tied to the EBS Forms application structure, which operates regardless of the specific launch method (like JWS or standard browser launch). If users resolve their EBS Forms resolution issues (often addressed via MOS Doc ID 2924556.1) , the Blitz Report integration remains functional within the improved display environment.
Blitz Report provides the necessary speed and detail to manage reporting during period close. It enables you to quickly generate large-volume reports, transforming the time-consuming process of reconciling inventory and cost data into a fast, manageable procedure by delivering immediate, actionable Excel output.
Enginatics in How to develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes Yes, Blitz Report is capable of exporting the enriched dashboard data to Excel. Furthermore, even if you are extending existing ECC dashboards with additional data, Blitz Report can export the underlying Oracle standard ECC data to Excel. This supports granular administration and analysis of ECC data sets.
The end-user interaction is simplified because they execute the report directly from the familiar form interface, eliminating the need to interact with the underlying SQL or understand the report registration process. They simply enter the necessary parameters, and the output is delivered as a formatted Excel file.
If the error persists, it may be cached on the server side. You should clear the cache manually using the Functional Administrator responsibility (Core Services > Global Configuration > Caching Framework > Clear All Cache), and potentially restart Apache or all application services.
Enginatics in How to develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes The speed stems from bypassing the conventional EBS report registration process, which is complex and time-consuming. Blitz Report is already integrated and simply requires pasting the validated ECC SQL into the Blitz Report form. The tool handles version control, parameters, and access assignment instantly.
Enginatics in How to develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes Yes, Blitz Report enables rapid report development using the standardized Oracle ECC SQL queries. You can develop proven EBS reports using Oracle Enterprise Command Center SQLs in under 5 minutes. This capability is highly relevant for developers, supporting consultants, and business users needing reports based on the same logic as the ECC dashboards.
The integration leverages the existing functionality intended for linking application components. By seamlessly integrating reports into EBS forms using Zoom, Blitz Report utilizes built-in EBS mechanisms to pass context from the form’s fields directly to the report’s parameters.
You must manually run the ‘Compile Security’ concurrent program and ensure it completes normally. This program inserts records into fnd_compiled_menu_functions and is required after security profile changes.
Blitz Report is designed as an easy-to-use add-on that resides directly in Oracle Forms. The process for How to add Blitz Report™ to your favorite form involves setting up the necessary integration points within the form structure, often leveraging Oracle’s capabilities for extending the user interface or through methods like Zoom functionality.
This error, related to Multi-Org Access Control (MOAC), means the current security profile setup does not grant access to any operating unit, or the underlying security compilation is outdated.
The parameter description is still displayed in the bottom left message area of the Blitz Report run window.
The default setting is ‘Yes’.
Yes, the profile option ‘Blitz Report Show Tooltip Help’ allows you to enable or disable the display of tooltip help.
The mandatory parameters are ‘Transaction Date From’ and ‘Transaction Date To’, specifying the accrual starting and ending transaction dates.
Yes, run the CAC AP Accrual Reconciliation Summary by Match Type report. This report summarizes the A/P Accrual entries from the Accrual Reconciliation Report tables by operating unit, accrual match type, and inventory organization.
The CST AP and PO Accrual Reconciliation report is the imported concurrent program equivalent.
You must set `QPPEnable = 1` and `QPPCreateNewStats = 1`. This ensures statistics collection is enabled. This update needs to be applied using `applypreferences.sh` and followed by a restart of the Discoverer iAS component.
Blitz Report’s Discoverer import uses information from the table `EUL5_QPP_STATS`, which stores worksheet query execution history. To ensure this table is populated, you need to update the Discoverer server configuration file, `pref.txt`, under the `[Database]` section.
The different workbooks and their selected columns are converted into individual Blitz Report templates under the single imported report. Templates are only created if a combination of folders was used in more than one different worksheet.
The exceeding data will be written to additional sheets.
The ‘Blitz Report XLSX Sheet Row Limit’ defaults to 1,048,576 rows.
Yes, the PLSQL procedure `xxen_api.import_discoverer_folders` is intended for this purpose. This option consolidates different workbooks that access the same folders or view object combinations into single Blitz Reports, simplifying maintenance.
The default setting for the ‘Blitz Report Row Limit’ profile is ‘no limit’. If no limit is set, the system defaults to the XLSX sheet limit.
You can use the Reset button to recover the initial column layout, or the Hide All button to deselect all currently displayed columns.
When expanding, the child values are inserted, and all adjacent formulas and content are automatically copied to the new rows.
Yes, you can use the Ctrl and Shift keys to select groups of columns (multi-select) and move them simultaneously between the ‘Available Columns’ and ‘Displayed Columns’ lists using the arrow buttons. You can also double-click a column to move it.
Yes, you can copy (Tools > Copy Report) the Blitz Upload Example (Interface Table) report to use as a template for creating new uploads using an Interface Table.
In troubleshooting scenarios where the connection filter causes a failure (e.g., blocking the EBS host), a temporary workaround that has proven effective is removing the specific denial rule in the Weblogic Admin console . An example of such a problematic denial rule is: `* * 7776 deny` . Removing this rule allows traffic, but exercise caution as this reduces security; it should only be a temporary measure .
Yes, the Undo Expand functionality supports multiple undo levels. Repeated clicks will step backward through the results of previous Expand operations.
Yes, templates are crucial for specifying the level of reporting (detail or summarized). You use the Aggr. (Aggregation) setting to define calculations like average, count, min, max, or sum for specific data columns.
The history of uploaded data is kept for the number of days defined by the profile option ‘Blitz Upload Data Retention Days’.
They can verify successful login to the core Solr application by navigating to the URL: `[ECC_HOST_PROTOCOL]://[ECC_HOST_NAME]:[ECC_PORT]/core_ecc` . For a non-SSL setup, this would look like `http://ecc.enginatics.com:7776/core_ecc` . Successful access indicates the connection filter is correctly permitting the traffic from the monitoring server’s IP .
The allow rule format specifies the host, target, port, and protocols . For IP 192.0.1.1 on the managed server port (default 7776), the rule should be entered as: `192.0.1.1 * 7776 allow t3 t3s http https` . After adding the rule, ensure you click ‘Save’ and ‘Activate Changes’ in the Weblogic console .
The Blitz Upload History report and the Blitz Upload Data report both show the history of uploaded data.
VPD is relevant across any module handling sensitive data, such as HR (e.g., Absence Visualization reports) , Payroll (e.g., Payroll Balance Listing) , and Financials. Since Blitz Report supports all these areas, proper VPD setup is vital to ensure only authorized personnel access relevant payroll or sensitive employee data.
Templates allow you to define the layout and content of the report output. You can select or deselect columns, adjust their display order, and define a sort order and sort priority.
You should click the ‘Undo Expand’ button. This tool removes the results of the most recent Expand operation.
Blitz Report processes data efficiently and outputs directly to native Excel files. It is specifically used within the project and upgrade toolkit for safely exporting master data, implying a secure handling of high-volume data extracts which are essential for audits and compliance.
To allow external hosts to access the core Solr application, you must configure the Weblogic Connection Filter rules . You need to log into the ECC Weblogic admin console . Navigate to Domain Structure -> `ecc_domain`, then choose Security -> Filter . Here, you must add an explicit allow rule for the monitoring server’s IP address .
Including the balancing segment helps verify the core structural setup, ensuring that the ledger definition correctly aligns with the segment used for legal entity representation.
Yes, the system is designed to leverage existing assets. You can import Discoverer reports complete with their assignments and parameters. This maintains your prior configurations and significantly reduces the manual effort typically required during migration.
The tool supports high compliance standards, relevant for auditing. Furthermore, when running reports, detailed metadata is maintained, and custom reports retain full version control with audit comments with every migration, providing inherent traceability of the reporting asset itself.
While not directly checking against Oracle reserved words, the Blitz Report Parameter Bind Variable Validation report helps check which bind variables were assigned to which Blitz Report parameter, useful if the same bind variable name is incorrectly used in different parameters.
Yes, for focusing purely on the grouping structure, use the GL Ledger Sets report, which shows the GL ledger sets and the ledgers included.
The output is converted into a structure manageable by Blitz Report, leveraging the underlying SQL. Once migrated, the report definition exists as a clean, version-tracked SQL query within the Blitz Report table. This simplifies technical management, as the complexity of the Discoverer folder structure is replaced by simple, manageable SQL reports running via Concurrent Requests.
No, Blitz Report does not override the Oracle security model. It leverages standard EBS security functionalities, such as assigning reports to specific responsibilities. The crucial data access security (VPD) is enforced at the database layer by Oracle itself, ensuring the reporting tool only sees data the user is authorized for.
The automation leverages the underlying capabilities designed for large-scale migrations. You can choose to import Discoverer reports individually using the Blitz Report import menu option, or instead use the mass import API utility for a high-volume process. We even provide suggested scripts for the mass import section to allow for refinement, such as filtering reports by historical usage days.
The GL Ledgers and Legal Entities report is specifically designed as a master data report to show this relationship: ledger set, ledger name, category, currency, legal entity, and balancing segment across all entities.
The automated migration feature drastically simplifies the process of transitioning away from Discoverer entirely. The feature streamlines the process of bringing existing assets over. The technical core involves analyzing and importing the metadata associated with the Discoverer worksheets.
Blitz Report strongly recommends using bind variables for parameterization to avoid performance issues associated with optional parameters coded as `column_name=nvl(:bind_variable, column_name)`. For parameters, always leverage bind variables unless you specifically need to enforce reparsing using the placeholder “.
You can use the DBA SGA SQL Performance Summary report. Set the parameter ‘Literals Duplication Count’ to a value greater than zero to display all SQL statements that are duplicated at least that number of times due to literal usage.
Yes, VPD allows for granularity in security implementation. This includes enforcement at both the row level and column level. When a report is executed via Blitz Report, the underlying database session adheres to the security predicate established by the VPD policy attached to the targeted table.
You can frequently find pre-built versions, such as those demonstrated for asset tracking, directly from the Blitz Report library and import them into your application, bypassing the need to develop the SQL from scratch.
Implementation is streamlined. Blitz Report acts as an add-on residing in Oracle Forms, requiring no new commands for users to learn. You can start designing and running complex cost reports without delay, utilizing the free 30-report tier for initial configuration.
Blitz Report is designed to integrate seamlessly with the native Oracle security architecture, ensuring that VPD policies are respected. You can explicitly control what tables Blitz Report can access by utilizing standard Oracle Virtual Private Database (VPD) security policies.
For matching purposes, the CST COGS Revenue Matching report should be used.
Blitz Report is recognized for its speed and ability to minimize processing overhead. It is designed to run complex SQL efficiently, extracting high-volume data rapidly, such as linking `citd2.instance_id` with `citd.instance_id` and performing outer joins to retrieve comprehensive asset tracking data.
Absolutely. You can control which tables Blitz Report can access by implementing standard Oracle Virtual Private Database (VPD) security policies at both the row and column level. This allows you to securely expose data needed for reporting while enforcing data governance rules. Additionally, Blitz Report provides full version control for all custom SQL scripts used in the reports.
The software is integrated based on Oracle Forms and OAF pages. This deep integration provides you with easy access to both your financial and manufacturing information simultaneously. You can leverage SQL to extract complex cost data and output it immediately to Excel for analysis.
You can categorize the report, for example, under ‘Toolkit – Business Operations’. This categorization ensures a quick search whenever the report is needed. Additionally, access can be assigned directly to specific modules or responsibilities.
Run the CE General Ledger Cash Account Usage report. It details the GL Cash Accounts assigned to bank accounts and their usage, with pivot options by account or bank account.
Yes, Blitz Report is specifically designed as a reporting software solution for Oracle EBS Cost Accounting, providing simple and effective reporting. It is fully integrated with the native Oracle E-Business Suite interfaces.
Based on the documentation history, when the item cost is zero, the Deferred COGS entries are noted as not recorded on the COGS Recognition Transaction Type.
Blitz Report functions as an easy-to-use add-on residing within Oracle forms, specifically designed for EBS project tasks. It helps consulting teams manage critical activities such as exporting master data and tracking data changes. A key benefit is the ability to create new operational reports quickly without the typical hassle of registering new concurrent programs and reports.
When creating these reports in the Blitz Report form, there is no need to register the program with system admin. Blitz Report handles this process internally, providing version control and a version history to ensure reports are not duplicated.
Use the CE Bank Statement and Reconciliation report. This provides equivalent functionality to the Bank Statement Detail Report and includes templates like ‘Bank Statement Detail with Reconciled Trxs’.
The required parameters are ‘Transaction Date From’ and ‘Transaction Date To’, specifying the starting and ending accounting date for the transaction lines.
For the first query, you define the report name and paste the SQL (which targets the ‘PENDING’ status, or uses a parameter for status). For the drill-down report (Query 2), you add a parameter, such as the Transaction ID, configured using an LOV type ‘custom’. This allows users to analyze the details of specific failing transactions.
For transactions ready for reconciliation, run the CE Transactions Available for Reconciliation report. It offers equivalent functionality to the standard ‘Transactions Available for Reconciliation Report’ (CEXAVTRX).
Use the CAC Deferred COGS Out-of-Balance report. This report specifically uses the pre-Create Accounting material accounting entries, meaning you do not need to run Create Accounting beforehand to analyze the data.
Yes, Blitz Report is an excellent solution for complex investigative reporting, specifically for Asset tracking integration with Install Base and Inventory. You can implement a multi-query approach, where one report identifies all ‘PENDING’ transactions and a second, drill-down report provides the failure details.
The required input parameter is `p_dataset_key`.
The CE General Ledger Reconciliation report provides equivalent functionality. It includes templates such as ‘Pivot: Reconciliation Summary’.
If a developer sets that profile to ‘Yes’, only the Run window will show the restricted list based on the current responsibility, even though the Setup window still displays all reports. This lets you check if a report is correctly available under a specific responsibility.
You can use the PLSQL procedure `xxen_api.import_ecc_dataset` to programmatically import ECC dataset queries. This gives users access to ECC data of unlimited size in Excel.
Yes, even if a report is disabled, users with ‘User Admin’, ‘Developer’, or ‘System’ access can still run it.
You should use the ‘Enabled’ setting on the Report Header. Disabling a report removes it from the standard user report list. This is useful during development and testing.
For detailed line and distribution information in 11i, use the AR Transactions and Lines 11i report. This includes special columns for service contracts (OKS) and lease contracts (OKL) data.
No, this report explicitly excludes any entered or incomplete transactions. If you need visibility into those, you should run the AR Incomplete Transactions report.
Your access level is higher. Users having their access profile set to ‘User Admin’, ‘Developer’ or ‘System’ can access all reports in the system, regardless of report assignments. Standard users, however, can see and run reports restricted to their assignments only.
The FND Concurrent Request Conflicts report allows filtering by the requested start date and conflict release date to narrow the scope of the investigation to specific timeframes when the known conflicts occurred.
The AR Transactions and Payments 11i report provides a detail AR customer billing history, including payments.
You should investigate the program’s definition for potential non-standard incompatibility rules or unnecessary locking. The FND Concurrent Program Incompatibilities report can show the defined incompatibilities.
You can implement internal compliance using Blitz Report alongside the EBS Audit functionality. This allows you to track master data changes relevant to the maintenance scheduling setup.
Use the FND Concurrent Request Conflicts report. It lists concurrent requests held by the conflict resolution manager and shows their conflicting/blocking requests that were running at the time of the conflict.
You can use the native EBS Zoom functionality to seamlessly integrate reports into EBS forms. This allows supervisors to access the maintenance schedule report contextually directly from their familiar EBS interface.
Native Excel output ensures perfectly formatted reports , complete with column templates that allow users to customize by removing or reordering columns. This high quality is necessary for complex scheduling and financial analysis (like pivot tables).
Since Blitz Report is a proven Discoverer replacement , you can leverage the fully automated Discoverer migration capability to quickly import any existing maintenance report worksheets into the new system, minimizing disruption.
The same consultant also delivered solutions for Calculating a WIP Production Job Details Report. These reports utilize highly efficient SQL to extract manufacturing and work order data, presenting it clearly in Excel for analysis.
Yes, innovative solutions addressing this exact challenge have been contributed through the Blitz Report Champion program. One notable contribution specifically targets the effective Scheduling Preventative Maintenance Workload in Oracle EBS.
For user parameters, you call `xxen_api.set_parameter_value_` referencing the `l_run_id`. For runtime options (like `TEMPLATE_NAME`, `EMAIL`, or `OUTPUT_FORMAT`), you use the procedure `xxen_api.set_runtime_option`.
The report includes a ‘Concurrency Wait Time’ column, which captures total elapsed time from the ‘Concurrency’ wait event class, such as ‘buffer busy waits’ or ‘enq: TX – index contention’, enabling you to identify SQL suffering from these waits.
For column translations and number formats, you use `p_include_columns`. Be aware that using this option might slow down the export significantly, as the database needs to parse all exported report SQLs to identify column names.
The ‘IO Factor’ indicates how much faster the query would execute if it ran without I/O wait times or unlimited memory. A high factor suggests performance is heavily constrained by IO waits.
If the cache clearing fails, you will need to reboot the relevant containers: OC4J containers for R12.1.3 or Weblogic servers for EBS 12.2.
You control this using specific optional parameters. To include definitions used by the report, you set parameters such as `p_include_lovs`, `p_include_categories`, `p_include_assignments`, and `p_include_templates` to ‘Y’.
You can use the API `xxen_api.report_submit_concurrent_`. This allows referencing the report, parameter, and template names by name or ID instead of relying on argument position. You first call this function to get a `l_run_id`.
If you are using RAC with SCAN listeners, it’s a known issue that they can cause problems during ECC setup . It is recommended to manually replace the SCAN entry with the Virtual IP (VIP) address in both the `EccConfig.properties` file and the generated `connection.dbc` file . This step circumvents potential SCAN resolution issues and ensures the JNDI creation is successful .
After successfully updating the JNDI configuration, you must bounce (restart) the ECC services . Restarting the ECC managed server ensures that the Weblogic domain picks up the updated database connection details and re-establishes the necessary connectivity to the cloned EBS environment, making the Solr servers available again .
This is a common transient issue after redeployment. First, use the Functional Administrator responsibility to clear the cache.
Beyond execution time, look closely at the ‘User Io Wait Time’, ‘Disk IO’, and ‘Buffer IO’ columns. The report also calculates ‘IO Sec Avg’, which is the average IO in MB per second per overall server time, indicating the average IO server load of the individual SQL.
To fix the JNDI connection post-cloning, you must follow the steps detailed under the section ‘Configuring the JNDI to Connect to Oracle E-Business Suite’ in the ECC documentation . This process typically involves regenerating the DBC file specifically for the ECC host system on the EBS application node, copying it to the ECC server as `connection.dbc`, and then running the appropriate configuration script (like `envSetup.sh` option 4) to update the `ebsDB` datasource , .
You define dependencies using the syntax `:$flex$.parameter_or_lov_name`. For example, to inherit the Operating Unit value and add ‘suppliers’, your default value SQL could be: `select :$flex$.operating_unit|| suppliers from dual`. This dependency syntax is used in both LOV queries and default values.
The ‘Cost Type’ parameter is mandatory and accepts one or more cost types you wish to report.
The retention of data in the `xxen_upload_data` table is controlled by the profile option ‘Blitz Upload Data Retention Days’ . The default value for this profile is zero . A setting of zero means that the data is deleted immediately during the upload processing . If set to a non-zero value, the data is kept for that number of days, which is useful primarily for debugging purposes .
The system is designed for ease of use, focusing on EBS SQL to Excel reporting with Blitz Report for non-developers. The integrated Forms interface minimizes the learning curve.
This specific `SolrServerException` often occurs after cloning because the ECC instance loses synchronization or trust with the newly cloned EBS database or configuration, especially if hostnames or database service names changed . To resolve this, you must first clear the ECC configuration details specific to the dataset statistics, which are often tied to the old environment . More importantly, you need to recreate the JNDI connection to the new EBS database .
Yes, you can specify a custom message text directly in the Advanced Required Parameters field. Otherwise, the system defaults to FND message `XXEN_REPORT_INSUFFICIENT_PARAM` or `XXEN_REPORT_ONE_PARAM_REQUIRED` if it detects that at least one parameter entry is required.
Yes, you can use the optional ‘Basis Type’ parameter to filter for specific basis types such as Item, Lot, Res Units, Res Value, or Ttl Value. Note that a bug fix was applied to this report to remove the ‘Cost Type 2’ parameter, relying instead on the Multiple Value functionality for the ‘Cost Type’ parameter for comparisons.
In an API-based upload, the input parameter `action_` receives values like `xxen_upload.action_create` or `xxen_upload.action_update` from the framework . Your custom wrapper procedure must populate the output parameter `status_` with either `xxen_upload.status_error` or `xxen_upload.status_success` based on the processing result . The output parameter `message_` is used to return the descriptive error or success message that appears in the final Excel output .
Parameters are referenced by their names (in the installed base language, usually US), prefixed with a colon (`:`). Any spaces or other non-word characters in the name must be replaced with a single underscore.
Yes, to clean up, you can use the script `mass_delete_discoverer_reports.sql` to remove all previously imported Discoverer reports before attempting a re-import.
Use the ‘Based on Rollup’ optional parameter. Enter ‘Yes’ to get the rolled up items, or ‘No’ to retrieve non-rolled-up (manually maintained) items. You can also filter by ‘Make or Buy’ status.
You must use the Advanced Required Parameters feature, which accepts a logical expression. For your ‘either-or’ requirement, the expression would be entered as: `:Customer_Name is not null or :Account_Number is not null`. This logic is evaluated at run-time, and if the condition is not met, an error message is displayed.
Yes, Blitz Report fully supports running reports that Connect Oracle E-Business Suite to Vertica, MySQL and other non Oracle databases using database links, ensuring continuity for complex, integrated reports.
The key input parameters are `p_workbook_owner_name`, `p_workbook_name`, and `p_worksheet_name`. It also requires `p_eul`, which defaults to ‘eul_us’ if not specified.
The CAC Item Cost & Routing report is what you need. It shows detailed item costs for buy and make items and allows comparison of any two cost types, providing a row-by-row comparison in detail.
It is absolutely critical that both the Error SQL and the Success SQL select the exact same number of columns and in the exact same sequence as your main report SQL extraction query . This is necessary because they are appended dynamically to format the final output correctly , . The SQLs should include human-readable status meanings by using utility functions like `xxen_upload.status_meaning` and `xxen_upload.action_meaning` , .
Yes, you can consolidate reports across all modules, whether it is Simple And Effective Cost Accounting Reporting or replacing Oracle ASCP exceptions. The platform provides a unified tool for all operational reports.
You need to use the procedure **`xxen_api.import_discoverer_worksheet`**.
Yes, you can use the script `mass_delete_polaris_reporting_workbench_reports.sql` to remove all previously imported RWB reports before attempting a re-import.
Be cautious. There are known compatibility issues, such as the ‘No matching authentication protocol’ error, when running Discoverer 11g with Oracle Database 19c. This highlights why replacement is crucial.
You must define the ‘Error SQL’ and ‘Success SQL’ under the Upload SQLs tab , . These SQL snippets are dynamically appended to the main report SQL post-processing . They must query the dedicated Data View (e.g., `xxen_blitz_report_samp_12867_u`) . This view contains the original uploaded data along with the returned status (`xu.status_`) and message (`xu.message_`) for each record .
If the data source contains more than one SQL query, only the largest one is imported, potentially requiring additional manual work to combine the data afterward.
You should use the procedure `xxen_api.import_reporting_workbench`. The import process consolidates different RWB reports that are based on the same database views into single Blitz Reports, with specific column selections imported as templates.
The procedure requires the application short name (`p_application_short_name`) and the concurrent program name (`p_concurrent_program_name`) associated with the BI Publisher report.
The tool translates the parameter requirements, allowing developers to ensure the corresponding Blitz Report uses equivalent parameter setups, potentially leveraging features like custom LOVs for complex inputs. Once migrated, these reports gain features like the ‘Multiple Values’ parameter functionality.
Blitz Report is designed as a direct replacement. The platform features fully automated Discoverer migration capability. The tool focuses on importing the worksheet definitions, which contain the logic (metadata, items, conditions) derived from the Discoverer business areas and folders.
The default setting is ‘No’.
The ‘All Contents’ export includes report definitions and related metadata. To export Blitz Report related profile option values, you should export those separately using the function with `p_type` set to ‘Profile Option Values’, which generates a SQL script that can be run on the destination system.
You can use the PLSQL procedure `xxen_api.import_concurrent_program`. This procedure is specifically used for migrating BI Publisher reports that are registered as the Java executable type `XDODTEXE` (XML Publisher Data Template Executable).
For a comprehensive export of all report metadata, you set the `p_type` parameter in `XXEN_API.export_file_data` to ‘All Contents’. This is typically the recommended option for migration from a test environment to production.
It can be used to store default hidden parameter values against templates.
You should set the profile option ‘Blitz Report Show Hidden Parameters’ to ‘Yes’. This allows Developers to show parameters that have a negative display sequence for debugging purposes.
If EBS cache clearing is required, the standard method involves using specific procedures referenced in Oracle documentation (like that mentioned in ). While Blitz Report specializes in reporting, having diagnostic tools readily available allows for quick identification of cache-related issues before manually executing the required cache-clearing script.
Absolutely. Blitz Report helps by Simplifying DBA tasks. It allows DBAs to quickly execute performance diagnostic queries, including AWR reports (even in multitenant environments), directly from the EBS interface without switching tools or logging in via SQL*Plus.
You should use the function `XXEN_UTIL.USER_ID(p_user_name in varchar2)`. For example, querying `xxen_util.user_id(‘SYSADMIN’)` returns `0`.
You must enter the ‘From Cost Type’ (the source of the download) and the ‘To Cost Type’ (the cost type you plan to upload back into the wizard).
Yes, if you decide that your custom LOV query would be useful for other report parameters, you can easily promote it to a shared LOV . To do this, click on the ‘Save as shared LOV’ button within the LOV definition window .
You can use a custom Blitz Report built around the `AD_PATCH.IS_PATCH_APPLIED` function to check patch status efficiently. This simplifies the verification process for patches like the AD and TXK deltas necessary for upgrades.
Both are used for parameter validation . However, the key limitation of ‘LOV Oracle’ is that you cannot directly edit the underlying LOV query from the Blitz Report form, as the value set must be maintained via the standard Oracle Forms interface . Conversely, ‘LOV Custom’ allows immediate, ad hoc SQL modification directly within the Blitz Report interface .
You should run the following diagnostic query as APPS, ensuring proper formatting: `select support_db D, support_cp C, support_admin A, support_forms F, support_web W, node_name, webhost from apps.fnd_nodes order by node_id;`.
Required columns for the wizard include Org Code, Cost Type, Item Number, Based on Rollup, Lot Size, Mfg Shrinkage, Cost Element, Sub-Element, Basis Type, and Rate or Amount.
To mitigate performance issues with large LOVs, you should check the ‘Filter Before Display’ setting . By default, this setting is unchecked, and Blitz Report queries all possible parameter values in the background upon selecting the report . Checking ‘Filter Before Display’ forces the user to enter a (partial) value before the LOV is displayed, thereby restricting the dataset queried by the form, which significantly improves the initial load time .
The Oracle Item Cost Interface works best for Buy Items. It does not work well with rolled-up costs, so the report excludes items whose costs are based on the cost rollup, ensuring compatibility with the interface.
Yes, complex issues during upgrade phases like applying patches (e.g., patch 28840850) often point to environmental inconsistencies. It is crucial to verify the settings using SQL queries to check the `fnd_nodes` table to confirm service names, webhost, and domain information are correctly defined for the DB, CP, Admin, Forms, and Web components.
Use the CAC Load More4Apps Buy Item Costs report. This report fetches all buy items (based on rollup = No) and approximates the layout needed for the More4Apps Item Cost Wizard.
For tracking historical demand patterns, run the INV Item Demand History report.
A stuck `adop phase=fs_clone` with no errors in the log files can be highly frustrating. General debugging often involves checking critical system components outside the main log, such as ensuring all relevant services and connections are properly configured, and reviewing low-level database or OS logs for silent failures.
The ‘Period Name’ parameter is mandatory, specifying the accounting period you wish to report.
Yes, the report listing indicates that a ‘Default Pivot’ template is available, allowing flexible analysis and summarization of the aging data.
The LOV SQL must include the columns `value` and `description` . It may optionally start with an `id` column . If an `id` column is included in the select clause, the value from this column is used as the parameter’s bind value for the main report execution . If the `id` column is excluded, the value from the `value` column is used for binding the parameter restriction .
Yes, the report includes any Profit in Inventory (PII) amounts. You can specify the ‘PII Cost Type’ and ‘PII Sub-Element’ parameters if needed.
You should select the ‘LOV Custom’ parameter type . This type is specifically used to create an ad hoc LOV based on an SQL statement solely for the validation of the current report parameter . Once selected, you double-click the ‘LOV Query’ field to enter the required SQL statement . This ensures that any modification to this LOV will not impact other reports, unlike shared LOVs of type ‘LOV’ .
It’s important to note a limitation: this report uses the latest material issue quantities stored on the WIP job definition, even if run for a prior period. It does not roll back the component issue quantities for a prior accounting period.
The INV Aging report is the dedicated report for this purpose.
Yes. Use the Blitz Report Parameter Comparison between environments report for parameter differences and the Blitz Report LOV Comparison between environments report for LOV differences.
The CAC WIP Material Relief report is suitable for this. It shows WIP material variances on closed jobs for discrete manufacturing, summarizing by inventory organization, WIP class, and job status.
You must create a specific view (`xxen_reports_v_`) on the remote environment that uses `dbms_lob.substr` to handle large object (LOB) columns like `sql_text_full`, converting them to a shorter string before the comparison.
For that summary reconciliation purpose, run the CAC AP Accrual Reconciliation Summary by Match Type report. It summarizes entries by operating unit, accrual match type, and inventory organization to justify accrual balances.
Use the Blitz Report Comparison between environments report. It shows Blitz Report differences between the local and a remote database server.
Yes, the periodic purging of outdated log records is one of the tasks performed by the Blitz Report Monitor concurrent program.
Yes, reports with special multibyte characters in their name may show an incorrect attachment filename, which is often an Oracle bug related to JavaMail using standard RFC 2231.
No, when left blank, there is no automated purge of log data.
Each template within the CST Uninvoiced Receipts report includes a Pivot that summarizes the accruals by Accrual Account and allows sorting/pivoting by the Pivot/Sort Parameter Value, which includes options like Vendor, Category, or PO/Release Number.
That is the typical flow. You first call `xxen_api.report_submit_concurrent_` to get a run ID, and then use procedures like `xxen_api.set_parameter_value_` and `xxen_api.set_runtime_option` referencing that run ID.
No, the applications operating system must also support multibyte filenames. The default setting is ‘Yes for Linux, No for other OSs e.g. Solaris, AIX’.
You use the profile option ‘Blitz Report Log Retention Days Standard’. This defines the number of days that log data for successful standard report runs is kept.
Yes, the alternative is `xxen_api.report_submit_concurrent_`. This API allows referencing the report, parameter, and template names by name or ID instead of relying on argument position, which improves code readability and maintenance.
The CST Uninvoiced Receipts report provides this functionality. It offers multiple templates to summarize accruals, such as by PO/Release Distributions (the default), PO/Release Shipments, or PO/Release Lines.
If submitting manually, you select the ‘Blitz Report’ concurrent program and must populate arguments 16 onwards with the report parameters. These parameters must be entered in exactly the same order as they appear on the Blitz Report run window. For example, if ‘Operating Unit’ is the third parameter on the form, its value must be entered into Parameter3 of the concurrent request.
Yes, by setting the Return Range parameter to ‘Yes’, the result is formatted as a period range spanning from the offset period to the base period.
You need to set the profile option ‘Blitz Report Email Attachment Multibyte Filenames’ to ‘Yes’. This ensures email attachment filenames are sent including UTF-8 multibyte characters from the Blitz Report name.
The easiest way to schedule the report is to first run it from the Blitz Report run window with all parameters set correctly, and then copy the resulting submitted concurrent request. You navigate to ‘View > Requests’, find the request, use ‘Copy’, update the schedule frequency, and then configure the Oracle standard delivery options. Oracle’s delivery options natively allow the report output to be sent as an email attachment, uploaded to a WebDAV cloud storage, or sent to an FTP location, which is ideal for an outbound interface.
A value of 0 returns the current reference period.
The Oracle standard `fnd_request.submit_request` can be used. Arguments 1 through 15 specify the report name and runtime options (like email, output format, etc.). The actual **user-entered report parameters start from argument 16** onwards.
Certainly. The SQL required, which should be set up as a parameter SQL text, would look similar to this structure: `rctla.last_update_date >= (select fcr0.actual_start_date from fnd_concurrent_requests fcr, fnd_concurrent_requests fcr0 where fcr.request_id = fnd_global.conc_request_id and fcr.parent_request_id = fcr0.request_id)`. This snippet dynamically identifies the current request ID and then looks up its parent request (the previously scheduled job) to retrieve the required `actual_start_date` for filtering.
You should input a positive number (e.g., 3) to return future periods. Conversely, negative numbers (e.g., -1) return past periods.
Yes, you can use the Blitz Report Access Upload to maintain the access profile option.
Yes, a ‘Proxy Error’ encountered when accessing the EBS HTTPS URL (e.g., `https://EBSserver.abc.com:443/ecc`) suggests a problem in how the OHS (Oracle HTTP Server) is configured to handle the request redirection or proxying to the ECC managed server. After running AutoConfig on EBS, you should verify that the OHS configuration file (`ecc.conf`) contains a proper `RewriteRule` directing the `/ecc` path on EBS to the ECC managed server URL, which ensures seamless integration. If AutoConfig ran correctly, but the proxy error persists, you should check the OHS log files and confirm the directory structure for the TLS certificate keystores, which is typically found under `[s_ohs_instance_loc]/config/OHS/[s_ohs_component]/keystores/default`.
Yes, after making your selection and clicking ‘OK’, your choices will be saved and automatically set as the default for future use.
You can restrict your query to records modified since the previous scheduled request run by utilizing a parameterized SQL clause that references the execution history of the concurrent program itself. The core logic involves comparing the record’s modification timestamp (e.g., `rctla.last_update_date`) against the start time of the *previous* request run. The required SQL pattern uses self-referencing joins on `fnd_concurrent_requests` to dynamically retrieve the `actual_start_date` of the last completed parent request.
You should use the function `br_period_offset`. This function returns the period name located a specified number of periods before or after a reference point.
If you remove the profile option value from Site level, the Blitz Report menu entry is automatically hidden from the Forms navigation menu for users who do not have a value set for the profile option.
The ECC WEB ENTRY URL shown during the execution of `patchEccFiles.pl` is expected to point back to the EBS instance, typically showing the EBS middle-tier hostname and port (e.g., `http://demo.enginatics.com:80/ecc`). This is because the EBS application server is initiating the import process and communicating the target URL. The import process uses the EBS instance as the gateway to deploy the zipped application files (like `ap_ecc.zip`) which the EBS server retrieves and sends to the ECC application. Once the files are successfully imported, the resulting summary report should show ‘Success’ for all applications attempted, such as AP, AR, FA, and OKL.
In an Oracle R12 environment, if the selected responsibility’s data access set contains multiple ledgers, all of those ledgers will automatically appear in the Ledger dropdown.
To assign licenses manually, you must ensure that the ‘Blitz Report Access’ value ‘User’ is removed from the site level. Then, set the profile option for each individual responsibility or user as required.
While I don’t have a specific document dedicated solely to self-signed certificates in the context of ECC import here, if you are running EBS with a self-signed certificate, you must ensure that the EBS certificate is correctly imported into the relevant JDK keystores used by the EBS application tier. Skipping the loopback and outbound configuration (Doc ID 1367293.1, section 5.3) often leads to issues during the import stage, as the EBS application tier needs to trust its own hostname and certificate when communicating externally, or in this case, sending the application files to ECC. You might also find helpful information in the blog post about configuring TLS for ECC.
If you select Multiple Responsibilities, the Ledger dropdown dynamically lists all ledgers associated with all the responsibilities you have chosen. If you select only one responsibility, it shows only the ledgers assigned to that one.
Look at the ‘IO Row’ column in the DBA AWR SQL Performance Summary. This shows the average I/O per individual row retrieved. For data extraction queries without aggregation, this metric is a good indicator of efficiency.
Oracle E-Business Suite reporting straight into Excel: 2,900+ ready-made reports, your own SQL, 150+ Excel uploads.