Support
Discussion Replies Created
The DBA would typically query standard FND tables to verify the setup. For instance, diagnostic queries confirming the configuration of nodes and managers rely on details from tables accessed via the APPS user (e.g., querying `apps.fnd_nodes`) to confirm service mappings and node information.
Yes, this performance issue occurs because the default behavior queries all values. You must enable the ‘Filter Before Display’ setting in the LOV definition.
Yes, you can leverage the native Oracle EBS Audit function to track master data changes. Blitz Report serves as the perfect mechanism to report on and analyze this audit data efficiently, streamlining operations for master data maintenance and compliance teams.
Yes, the report includes a parameter to Show BI Pub & Delivery Options. When enabled, this shows information such as the publisher template, output file, post-processor result, and delivery details (email or FTP information).
You can enable the `Show Parameters Display Values` setting in the alert report. However, note that setting this option to ‘Yes’ could significantly slow down the report execution, so use it judiciously for critical debugging rather than routine monitoring.
For the item-level changes, run the CAC New Standard Item Costs report. This report shows items with recent item cost changes, comparing the new cost against the prior and current frozen costs.
The report parameters are granular. You can monitor key metrics such as `Scheduled or Running` requests, and filter based on elapsed time criteria like `Waiting for x Minutes` or `Running longer than x Minutes` to identify bottlenecks within the new manager’s workload and clear any potential backlog.
The ‘Cost Update Date From’ and ‘Cost Update Date To’ parameters are required, as they define the date range based on the standard cost submission history.
You should utilize the Oracle E-Business Suite – Concurrent Request Monitoring and Alert Reporting tool provided by Blitz Report. This diagnostic report allows filtering by the specific Manager Name.
The process for Creating a custom concurrent manager in Oracle EBS is a standard DBA task. This involves defining the new Concurrent Manager, assigning it a Service Instance, setting up its Workshifts, and associating specific Concurrent Programs with it to control workload execution.
You should run the CAC Standard Cost Update Submissions report. This report shows the Standard Cost Update submissions, detailing the parameters used and the overall inventory and WIP adjustment values.
Use the CAC WIP Jobs Not Eligible for Closing report. This report specifically finds jobs that exceed variance tolerances, have uncompleted assemblies, open requirements, or stuck transactions.
Yes. You must specify ‘Include Scrap Quantities’ and ‘Include Bulk Supply Items’ parameters, which are both required. Setting ‘Include Bulk Supply Items’ to ‘No’ will exclude those types from the component requirements check.
Once the custom query is defined, you can save it within the Blitz Report form for future quick access. It retains the report definition and parameters, turning a complex DBA query into a repeatable, one-click operational tool.
Both ‘Variance Amount Threshold’ (absolute maximum variance allowed) and ‘Variance Percent Threshold’ (based on WIP Job Balance / WIP Costs In) are required parameters.
When integrating this into a script with `dbms_xslprocessor.clob2file`, you can sanitize the report name using a function like `xxen_report.space_to_underscore(c.report_name)` to create a valid filename.
The query uses `AD_PATCH.IS_PATCH_APPLIED` with parameters including the release (`’R12’`), application top ID (`aat.appl_top_id`), bug number (`adb.bug_number`), and language (`adb.language`). This function returns the status, allowing you to use a `DECODE` statement to clearly label the result as ‘APPLIED’ or ‘NOT APPLIED’ for specific bug numbers.
Use the CAC WIP Jobs Eligible for Closing report. This report filters for jobs that have a status of ‘Complete’, do not exceed variance tolerances, and have no open material requirements or stuck interface transactions.
In this scenario, instead of using `export_file_data` for a bundled export, you should use the function `XXEN_API.export_report_` inside a PLSQL loop. This function accepts a single parameter, `p_report_id`, and returns the report XML as a CLOB.
For payment process requests, run the IBY Payment Process Request Details report. This shows details including statuses, paid or rejected documents, amounts, and rejection error messages.
The function does not include a commit. You must explicitly execute a commit from the calling code to finalize the database transaction after a successful import.
Absolutely. Blitz Report is the optimal method for this check, allowing execution directly from the EBS Forms interface, eliminating the need to log in to the database or navigate to the OAM page. You can create a custom report leveraging the Oracle function `AD_PATCH.IS_PATCH_APPLIED`.
Yes, you can use the AP Posted Payment Register report. It offers templates, such as ‘Pivot: Summary by Account’, which is equivalent to the standard report in ‘Summarize Report = Yes’ mode.
If the parameter value is left blank, the corresponding &lexical reference is completely removed before SQL execution, although for a PIVOT clause, leaving the column list blank might cause a syntax error depending on your overall SQL structure.
You should use the function `XXEN_API.import_xml(p_xml in clob)`. It takes the XML data as a CLOB input and returns `null` if the import is successful, or an error message if it fails.
To prevent reconciliation confusion, the invoice and check level amounts are shown only on the last payment record associated with the transaction, and are blank for multiple/duplicate records.
That is the core principle: convert the proven data source to Blitz Report’s engine for superior performance and perfectly formatted Excel output, leveraging the ability to import BI Publisher reports complete with assignments and parameters.
Yes, that is correct. The &gl_period_pivot reference inside the pivot clause will be replaced at execution time by the parameter SQL text, which generates the comma-separated list of periods (e.g., ‘Jan-20’ jan_2020, ‘Feb-20’ feb_2020, …).
You can utilize the pre-built Concurrent Request Monitoring and Alert Reporting tool. This enables immediate checks on running/waiting requests and provides deep diagnostics, including identifying underlying SQL, to pinpoint the source of performance degradation.
Use the AP Invoice Payments report. It provides supplier invoice payment details and includes logic to allow reconciling payment with invoices and checks.
For scheduling this report periodically, use the relative period from/to offset parameters. When the current period changes, these offsets automatically update the included periods when the report re-runs.
You should use the &lexical parameter reference for dynamic pivot tables. The &lexical anchor is highly versatile and is used to insert variable SQL snippets for elements like dynamic columns, ORDER BY, GROUP BY, or, in your case, the dynamic list of periods columns required by the PIVOT clause.
Access control is managed at the report level. Reports can be assigned strictly to specific DBA users or responsibilities. Furthermore, if you implement Oracle VPD policies, those database-level security rules will ensure that sensitive data is only visible to authorized accounts, even if the report is executed.
Yes, users can navigate to File > Info > Enable Content > Advanced Options in Excel and select ‘Trust all documents from this publisher’.
The final step is to migrate to test and/or further instances. This process is simplified because the report definition is self-contained within Blitz Report’s tables. You simply migrate the report definition, speeding up the deployment process without the typical administrative overhead or version challenges.
For a one-time fix, users can simply click the ‘Enable Content’ button. For a permanent solution, especially if your company has strict security policies, your infrastructure team should import the Enginatics Certum Code signing public certificate into the Trusted Publishers certificate store on client machines.
Yes, you can use the ‘Item Number’ parameter to enter a specific item number to review, or leave it blank/null to get all items.
The AP Posted Payment Register report provides this equivalent functionality. It offers pivot templates like ‘Summary by Account’ and ‘Summary by Account, Bank Account, Batch, Payment Currency, Payment Document’.
Blitz Report is engineered for efficiency, featuring reduced processing overhead and generating output at an incredibly fast pace. This optimization is key when running complex diagnostic queries that target high-volume EBS data.
Step four emphasizes quality control: you must test and add version control to the new Blitz Report. This crucial step leverages Blitz Report’s built-in version tracking capabilities , ensuring that even with rapid development, stability is maintained and changes are fully auditable.
The mandatory parameters are ‘Transaction Date From’ and ‘Transaction Date To’, specifying the starting and ending transaction date for the PO Receipt History.
Unfortunately, Oracle no longer supports the Look and Feel options of previous releases after applying certain ATG patches like R12.ATG_PF.C.Delta.5 and higher. If your UIX version upgraded to 12.2.6, Oracle explicitly states that only the ‘Alta Look and Feel’ is supported with JWS; customization with SWAN or SKYROS is not supported. This is a standard consequence of moving to the modern JWS architecture.
Yes, the AP Trial Balance Report Definitions report details the Accounts Payable Trial Balance Report Definitions.
It *may* be used, but the documentation notes that columns such as prior costed quantity, prior cost, and new onhand quantity will have zero or empty values for Standard Cost organizations. The CAC PO Receipt History for Item Costing report may be a better choice for Standard Costing.
To test JWS functionality selectively, you can enable it only for specific application users by configuring profile options at the user level. You must set the profile option ‘Enable Java Web Start’ to ‘Yes’ for the designated test users. This allows your test group to use JWS without immediately impacting the rest of the production user base.
The toolkit includes a comprehensive suite of reports categorized for needs such as Database Health and Tuning reports (including AWR and FND data) and Support and Data Migration reports (including BR100 extracts and alerts for critical processes).
Yes, it is done after the creation of the summary templates (via GL Super User > Setup > Accounts > Summary) is completed.
Resource issues are a common cause of slow startups and timeouts in ECC . You must check the ECC server’s allocated RAM, swap space, and CPU core count/frequency . Insufficient RAM that forces the Java application (Weblogic/Solr) to use excessive swap space during intensive operations will significantly increase execution time and lead to timeouts .
The second step is simply to copy the SQL query from the XML Data Template, for example, a query related to a cost management report like CSTRAIVR. The third step is pasting this SQL into a new Blitz Report definition, effectively eliminating the need to develop, register, and maintain the XML or XSL templates necessary for BI Publisher output.
You need to navigate to the System Administrator responsibility and run the concurrent program ‘Blitz Report Update GL Indexes’.
As per Oracle documentation (Doc ID 2066023.1), you need to set the `ORA_NLS10` environment variable correctly on the database tier and then restart the application and database services to apply the corrected setting.
Yes, it significantly simplifies access. Blitz Report allows the DBA to execute queries directly from the standard EBS forms interface, completely eliminating the need to log into the database separately or navigate to tools like OAM. This dramatically streamlines the diagnostic process.
While the standard concurrent program is designed for `FULL_LOAD` or `INCREMENTAL_LOAD`, performance issues often stem from the sheer size of the initial collection creation . You might attempt running the load with a `METADATA` load type first to ensure the structure is indexed, followed by a constrained `FULL_LOAD` if the data model allows parameter filtering in EBS , . If the error persists even for smaller data sets, the issue points back to a fundamental stability or resource constraint in the ECC environment .
You should use the CAC PO Receipt History for Actual Costing report. It is specifically designed for non-Standard Cost inventory organizations.
The fundamental method is to extract the proven SQL query directly from the existing BI Publisher data source. These reports rely on an underlying data definition (often a Concurrent Program that generates XML). The process involves five simple steps, starting with identifying the underlying SQL.
This sounds like a configuration issue, possibly related to how the nodes are registered or how the forms launcher profile is configured in the load-balanced environment. You need to verify the configuration of the ‘ICX: Forms Launcher’ system profile to ensure it is correctly pointing to the appropriate URL or load balancer endpoint. Additionally, you should run a query against `apps.fnd_nodes` to inspect the registration status (`support_forms` column) and the `webhost` defined for each of your application nodes to identify inconsistencies.
Although the time-out suggests slow communication rather than an outright block, you should ensure that the ECC application components (like the managed server and Solr services) can communicate freely . The connection filters in Weblogic are set up primarily to allow EBS traffic . If running on a cloud platform, verify that the security group rules are not imposing restrictions on internal ports used by Solr and Zookeeper, or that there are no connection filter deny rules active on the Weblogic managed server port (default 7776) .
For optimal performance of the FSG report, you must run a specific concurrent program after the summary templates are created.
These specific Oracle Text errors often occur because the `ORA_NLS10` environment variable is not set correctly on the database tier. Incorrect linguistic settings prevent the necessary CTXSYS procedures from executing properly.
The JWS migration process requires applying several specific patches to your EBS instance, which you must first identify using Oracle Support Document 2188898.1. After preparing the environment, the patches are typically applied using the `adop phase=apply` command, often merged into one application phase. Following the patch application, a crucial step is to run `adadmin` to explicitly regenerate all product JAR files, ensuring you select the FORCE option set to ‘Yes’ when prompted to guarantee complete regeneration. Finally, the entire `adop` cycle must be completed, including the `actualize_all`, `finalize`, and `cutover` phases.
Blitz Report is a revolutionary tool for DBAs because it acts as an organized container for their crucial SQL scripts. By migrating those queries into Blitz Report, the DBA gains a centralized toolkit that provides new possibilities for staying organized, especially when collaborating in a team.
The source materials do not specify a profile for font color, but customization of Excel output generally falls under branding.
This `InterruptedException: Read timed out` error originates deep within the ECC indexing services, often specifically from `oracle.ecc.index.update.metadata.CollectionRegistration.createCollection` . This indicates a timeout occurred during the creation or registration of the Solr collection, which is a key step in initializing the dataset . Such errors are usually symptomatic of a network latency issue, inadequate resource allocation (CPU/RAM), or firewall blocks between the ECC Weblogic managed server and the Solr core components.
The report definition and execution are managed directly within the EBS forms interface by designated users, making it simpler than running raw SQL against the database. It is one of the many reports used by EBS Apps DBAs in their toolkit.
The default hexadecimal code is eaeff5.
You use the profile option ‘Blitz Report XLSX Column Header Color’. The value must be entered as a hexadecimal code (e.g., EAEFF5) for the column header background color in Blitz Report Excel spreadsheets.
Since Blitz Report outputs native Excel files, you can integrate the extracted data directly with visualization features like Excel Bing Maps. This combination turns raw IP and geolocation data into an easily digestible visual report, enhancing your security monitoring capabilities across EBS R12 and 12.2 instances.
Yes, tracking table modifications can be useful for performance context. You can use the DBA Table Modifications report to see the number of rows modified since the last analysis, provided table monitoring is active.
Blitz Report can be utilized for this exact security requirement. It allows you to query the underlying database tables that store session information to find the client’s IP address. Once the IP addresses are obtained via the Blitz Report SQL, the geolocation data can be inferred or derived.
If tuning server load is the goal, CPU is usually prioritized, but if you want to spot other bottlenecks like IO or network waits (e.g., ‘SQL*Net message from dblink’), you should sort the report by ‘elapsed time’ instead of CPU time.
When opening Blitz Report for the very first time, a selection of available reports is displayed automatically.
Focus on the ‘User Io Wait Time’ column. This shows the total elapsed time in seconds from the wait event class ‘User I/O’.
The LOV uses a ‘favourites on top’ sorting feature. Your ‘most frequently used’ reports are listed at the top based on usage history.
Yes, this functionality is controlled by the profile option ‘Blitz Report LOV History Days’. By default, it looks back 365 days. If you set this profile value to zero, the ‘favourites on top’ sorting is switched off, and all reports sort alphabetically instead.
For missing purchase order deliveries into inventory or work in process, you would need to use other reports such as the ‘CAC Missing Material Transactions’ or ‘CAC Missing WIP Transactions’ reports. This is explicitly noted in the description of the Missing Receiving Accounting report.
That is intended behavior. When you subsequently open Blitz Report after the first time, the last report executed will default in the report name field.
When running the report, set the ‘Minimum Transaction Amount’ parameter to zero (0). This ensures you capture all transactions missing receiving accounting entries, regardless of how small the transaction amounts are.
Yes, the actual content width is typically used, provided it remains within the minimum and maximum limits set by the profiles.
Use the CAC Missing Receiving Accounting Transactions report. This report is designed to find receiving transactions where the corresponding accounting entries do not exist, based on a specified transaction date range.
You can continue using automation. The method of Sending files from Linux to Sharepoint online using a python script remains a viable solution for securely transferring Blitz Report Excel/PDF output from the updated Linux application server.
The default minimum column width is 2.
You use the profile option ‘Blitz Report XLSX Min Column Width’. This defines the minimum column width for Blitz Report XLSX output files.
The Blitz Report Upgrade Toolkit includes specialized Support and Data Migration reports for automated BR100 extracts. These reports are invaluable for documenting configurations pre- and post-OS migration.
A temporary client workaround is for users to go to Excel Trust Center Settings and add the download location of the output files to their Trusted Locations list.
The CSI Customer Products Summary report is the imported Oracle standard report for the Installed Base Customer Products Summary.
For a corporate-wide permanent solution, your security team should import the Enginatics Certum Code signing public certificate into the Trusted Publishers certificate store on client machines.
You should use the documented procedures for clearing the Oracle EBS cache in a script. This is a necessary step in EBS R12.1 and R12.2 maintenance to ensure the application tier utilizes the newly configured server environment correctly.
The OS upgrade primarily affects the server side. However, you must verify that server-side Java configurations remain intact. Client-side issues, such as Launching EBS forms with Java Web Start on Mac OS , usually relate to client Java version and local JWS configuration, but server changes can affect the JNLP file generation via the `ICX: Forms Launcher` profile.
Yes, you can run the OKL Termination Quotes report for information on lease termination quotes.
The Blitz Report DBA toolkit provides essential diagnostic reports. Before the upgrade, run AWR reports for a performance baseline , check the configuration of FND_NODES , and verify critical AD/TXK patches using AD_PATCH.IS_PATCH_APPLIED. This simplifies post-upgrade verification.
This is a security feature, often triggered when Protected View is active and the file originates from an untrusted location (your EBS URL). The primary fix is to add the EBS URL to the trusted sites in your Windows Internet Options configuration.
The OKC Contract Lines Summary report is precisely for this. It is useful for developers to see how the Oracle contracts line data is structured and how the link to external objects (e.g., installed base or counters for service contracts) works.
A major OS upgrade requires rigorous compatibility checks across all EBS components (Database, WebLogic, Apache, Java). You must ensure that the specific EBS version (e.g., 12.2.x) and associated database version (e.g., 19c) are fully certified and supported on Oracle Linux 8.
Yes, any view which references Polaris RWB objects starting with XXRX%, such as views using `xxrx_util_pkg.get_parameter_char_value()`, will be expanded regardless of the `p_expand_view_sqls` setting.
This report corresponds to several standard Oracle Reports, including the ‘Elemental Inventory Value Report’ and the ‘All Inventories Value Report’.
The parameter is `p_expand_view_sqls`. It accepts values like ‘none’, ‘all’, or ‘custom’. ‘Custom’ means only views starting with XX% or custom application short names will be expanded.
There is a significant limitation: the report cannot be run historically when including non-costed items. To include non-costed items, the ‘As of Date’ parameter must be left blank (current date), otherwise the underlying Oracle API will error.
You should use the procedure **`xxen_api.import_reporting_workbench`**.
Use the CST Inventory Value – Multi-Organization (Item Costs) report. This report can be used to report inventory value by elemental item cost level and quantity type, and it runs across multiple Inventory Organizations.
Once the custom SQL report is saved in Blitz Report, it can be assigned to the relevant user responsibilities. Users can then either run the report on demand or utilize the enhanced delivery options within the concurrent request mechanism to schedule reports and automatically distribute the resulting Excel files to the entire team via email or shared locations.
Report creation and execution are highly optimized, benefiting from Blitz Report’s reduced processing overhead. The philosophy is to execute proven SQL quickly and deliver the output instantly as native Excel. This ensures that your planners spend less time waiting and more time analyzing the most current horizontal plan or pegging results.
It offers broader support. While Blitz Report can effectively replace Oracle ASCP exception reporting , eliminating the tedious reliance on the Planner Workbench , its application in advanced areas like pegging and horizontal planning demonstrates its full data extraction potential. This allows for deep analysis into supply/demand linkages that standard reports struggle with.
Blitz Report provides the capability to simplify reporting across critical planning areas, specifically addressing the extraction of complex data types like horizontal planning data and detailed pegging exports. By using customized SQL defined within Blitz Report, your planners can bypass the limitations and complexity of standard ASCP interfaces.
Yes, the `xxen_utils.download_file` procedure is included in the `XXEN.pll` library, so you must ensure that this library is attached to your custom form to enable the download functionality.
Yes, you can use the Blitz Report Access Upload feature . This upload utility allows you to maintain the access profile option values in bulk, which is useful when managing a larger number of users or when allowing maintenance by a user who typically would not have access to the System Profile Values form .
The file download is handled by the procedure `xxen_utils.download_file`. This procedure requires the file ID, which is retrieved by calling `xxen_api.report_file_id(l_run_id)`.
It is generally discouraged to create custom read-only responsibilities solely for running Blitz Reports . Blitz Report is designed to operate within the users’ existing application responsibilities . Running reports in separate responsibilities introduces drawbacks like additional navigation steps, increased maintenance, loss of existing session security (e.g., MOAC/Ledger restrictions), and disables the drill-down functionality from Oracle standard forms .
Yes, if you remove the profile option value from the Site level, the Blitz Report menu entry is automatically hidden from the Forms navigation menu for users who do not have a defined value for that profile option . This automated menu entry hiding is handled through the `CUSTOM.pll` . If you wish to hide the menu entry entirely, even from OAF pages, you can run the ‘Blitz Report Update Menu Entries’ concurrent program without a menu entry prompt .
To manually control license assignment for a limited pool of licenses, you must remove the ‘Blitz Report Access’ profile option value from the Site level . You then set up the required access role (e.g., ‘Developer’ or ‘User’) specifically for each individual responsibility or user who is allocated a license . The system automatically assigns licenses based on these user-level or responsibility-level profile values .
If the environment check passes, the issue might be a corrupt definition of the `XXEN_REPORTS` function itself. You can verify its definition by querying `fnd_form_functions_vl` to ensure it is defined as a FORM type under the ‘Enginatics Custom Application’ (XXEN_REPORTS).
The default value is ‘No’ (meaning the editor opens).
That is correct. This inaccuracy is an inherent limitation within Excel’s date handling.
The access to Blitz Report functionality and licenses is primarily controlled by the profile option ‘Blitz Report Access’ , . This profile option determines which users can use the features and, by extension, consume a license . The main roles are ‘Developer’ (for users with SQL skills to create and edit reports, who also see the ‘Setup’ button) or ‘System’ (for users who can also create new uploads) , , . Standard users who only run reports typically consume a license without needing a specific ‘Developer’ setting .
An HTTP status 500 (Internal Server Error) during the application import via `patchEccFiles.pl` suggests the connection was established, but the ECC application itself failed to process the request. This could be due to internal server issues within the ECC Weblogic environment or potentially incorrect proxy settings if an LB is heavily involved. You should check the actual ECC logs for detailed stack traces to diagnose the internal server failure. You might find a shortcut is to try importing the application directly through the ECC UI using the ECC Developer responsibility, as this bypasses the complexities of the command-line script’s network path.
It allows the developer to highlight keywords in the SQL text through double click, instead of immediately opening a new editor window.
Yes, this can happen if the environment context for the custom top holding the Blitz Report form is not set up correctly, or if the application tier was not restarted after running `autoconfig`. You should verify that the `$XXEN_TOP` environment variable is set correctly by navigating to Help > Diagnostics > Examine and checking Block: `$ENVIRONMENT$`, Field: `XXEN_TOP`.
This is not an issue with Blitz Report but a known bug in Microsoft Excel. Excel incorrectly treats 1900 as a leap year, which causes dates within that specific range to be offset by one day. This is detailed in Microsoft’s own documentation.
Yes, you can use the profile option ‘Blitz Report Disable SQL Text Double Click Editor Window’. Setting this to ‘Yes’ disables the default behavior to open the editor window upon double-clicking the SQL text.
If you are running a multi-node EBS environment and the Weblogic ECC components are running, you should also check external firewall settings. If your servers are hosted on a cloud provider like AWS, you must ensure that the security group rules explicitly allow inbound connections to the ECC managed server port (e.g., 7776) and admin server port (e.g., 7775) originating from the EBS application server IP addresses. Even if the Linux firewall is off, cloud-level security rules can still block the traffic required for the import and subsequent data loads.
Yes, if the LB entry in the `/etc/hosts` file on the EBS server (or whichever node is running `patchEccFiles.pl`) is incorrect, removing that entry is the correct solution. Once the LB entry is removed, the import script will correctly resolve the hostname via DNS, pointing to the actual Load Balancer IP, thus allowing the connection to the correct ECC Web Entry URL to proceed successfully. You must restart the services afterward to ensure the changes take effect.
A ‘Connection refused’ error during the application import often indicates that the system is trying to connect to the wrong IP address or the target port is not open or being blocked. In scenarios where a Load Balancer (LB) is involved, a common issue arises if the LB entry is incorrectly defined in the local `/etc/hosts` file on the server running the import. Specifically, if the LB entry in `/etc/hosts` points to a local IP address (like 127.0.0.1) instead of the actual LB IP, the import attempt will connect to the localhost and fail, resulting in a ‘Connection refused’ error.
Correct. Blitz Report is engineered to handle massive data volume exports efficiently, guaranteeing no volume limitations. This capability is critical when reporting on a high volume of assets and related transactions.
When you save your cross-module query within the Blitz Report form, it automatically manages the full version control and audit history of that SQL script. This is essential for consulting teams managing extensions and ensures stable report definitions throughout your operational lifecycle.
The output is highly flexible. Blitz Report allows users to report the data to CSV, native Excel, or other file types. This capability supports diverse functional needs, whether for detailed Excel analysis by the SCM team or for external data ingestion by other systems like Tableau or Power BI.
Yes, you can report additional user-defined material transactions by adding them to the ‘COGS Transaction Types’ parameter, along with the defaulted transaction types.
Yes, that’s a key diagnostic use case. You can design custom SQL within Blitz Report to mirror troubleshooting queries, such as those related to Oracle Asset Tracking Pending Transactions (Doc ID 2423449.1). This allows your operational teams to proactively identify and resolve synchronization issues before they impact the financial or maintenance modules.
The mandatory parameters are the ‘Creation Date From’ and ‘Creation Date To’, which define the date range for the item master creation date.
You must enter the mandatory parameters: ‘Transaction Date From’, ‘Transaction Date To’, the list of ‘COGS Transaction Types’ (defaulted values include COGS Recognition, Sales Order Issue, RMA Receipt, and RMA Return), the ‘Recost Cost Type’, and the ‘Minimum Value Difference’.
Blitz Report is highly effective for this type of integrated SCM reporting. The ability to write straightforward SQL queries that join the necessary tables across Inventory and Install Base allows you to achieve comprehensive asset tracking reports.
You control this using the ‘Include Uncosted Items’ parameter. Set it to ‘Yes’ (which is the default) to display items that are configured to not be costed in your Costing Method Cost Type.
The CAC Recost Cost of Goods Sold report compares the ‘as transacted’ COGS transactions with the hypothetical costs from a specified Recost Cost Type. This comparison helps identify the necessary manual journal entry corrections.
The CAC New Items report is perfect for this. It shows items recently created based on the item master creation date, including various item controls, costs, accounts, and current onhand stock.
The log retention options explicitly define retention for ‘Error/Cancelled,’ ‘Standard,’ and ‘System’ report runs.
The Blitz FSG Converter is designed to import report definitions not only from Oracle FSG but also from third-party tools such as GL Wand and Spreadsheet Server , .
If you leave the profile blank, there is no automated purge of log data for system runs.
While the converter replicates the basic structure, complex calculations defined in the FSG Row Set usually require manual adjustment in the Blitz FSG Excel template after conversion . The logic (e.g., sums, divisions) must be manually inserted into the dedicated calculation column , typically using row sequence numbers (e.g., `+27+22`) or row names (e.g., `+COGS/TRev`) to define the operation .
You set the retention period using the profile option ‘Blitz Report Log Retention Days System’. This specifies the number of days that Blitz Report log data for successful system type report runs is kept.
The Column Set information is mapped primarily to rows 5 through 20 in the converted Blitz FSG Excel template , . Key mappings include: the Column Set’s Column Name maps to the Column Header in Row 9 , the Amount Type (e.g., PTD, YTD) is mapped to rows 10 and 11 , and any defined Offset is calculated using the `br_period_offset` formula in Row 12, unless no offset is defined, in which case it is equated to the Period Name LOV Cell .
It is recommended to use dynamic SQL anchors, such as `n=n`, instead of `nvl(:bind_variable, column_name)` coding for optional parameters to avoid performance issues.
The FSG Converter automatically replicates the FSG structure into the Excel template . The Row Set information is mapped to specific Excel columns . For example, the Row Set’s Account Assignments are mapped to Columns B through F (based on your chart of account segments) . The Line Item description is mapped to Column G, and the Calculations logic is mapped to Column I .
Use the Blitz Report Parameter Bind Variable Validation report. This report checks which bind variables were assigned to which Blitz Report parameter, useful for detecting cases where the same bind variable name is incorrectly used in different parameters.
Yes, the Blitz Report Parameter DFF Table Validation report shows any parameters using the `xxen_util.dff_columns` function which reference an incorrect DFF table name.
A setting of zero switches this ‘favorites on top’ sorting off and sorts all reports alphabetically instead.
Yes, you can run the GL FSG Reports and GL FSG Row Orders reports to review the setup definitions of Financial Statement Generator reports and their row orders.
All custom report development within the toolkit is version tracked. The report delivery is reduced, tracked in your EBS instance, and includes full audit comments with every migration, ensuring complete traceability of SQL logic throughout the project lifecycle.
The default setting is 365 days.
The fourth component is either Time Critical reports or Data management reports , depending on the focus, but both are geared towards mass exporting volume data efficiently, overcoming data limitations and formatting issues associated with CSV files.
The third component is Operational reports. These cover core business processes (R2R, O2C, P2P) and offer robust import functions allowing for the replacement of Discoverer and BI Publisher reports directly within Blitz Report.
The second component covers Support and Data Migration reports. This is where we provide automated BR100 extracts for setup and data migration purposes, along with essential alerts for critical processes like integrations and concurrent requests. This streamlines the initial data gathering phase.
The definition is controlled by the profile option ‘Blitz Report LOV History Days’. This sets the number of days within which Blitz Report identifies a user’s most recently run reports to show them on top of the LOV.
You can use the ‘Additional Segment’ parameter to include extra segments, such as the cost center or balancing segment, in the report output.
Yes, business users can easily modify the report layout by leveraging the folder style template functionality, allowing them to remove or reorder columns so they only receive the data they need.
Yes. Blitz Report excels at handling massive volumes—it is engineered with reduced processing overhead for incredible speed , and maintains no volume limitations. The high-volume extraction capabilities are crucial, especially for ECC administration and data management tasks.
The Blitz Report Toolkit is organized into four key components to manage and export data during EBS projects. The first component is Database Health and Tuning reports, which includes a comprehensive suite of AWR and Foundation (FND) reports for performance baselining and troubleshooting.
Utilize the fully automated Discoverer migration feature of Blitz Report. This allows the importing of existing worksheets, providing a clean path to immediately run them on the modern platform without manual recreation.
The report displays the starting balance, total amount per month, ending total, and Year-to-Date (YTD) balance.
Yes, Blitz Report provides a utility specifically for this purpose under Tools > Resequence parameters . This function automatically assigns new sequence numbers to your parameters, ensuring there is spare room between sequence numbers again, which allows you to easily insert new parameters into the required display order without manual sequence number adjustment conflicts .
Report security is granular in Blitz Report. You can assign the reports specifically to a user, module, site, or responsibility. For fine-grained data restriction (e.g., row-level site access), ensure your Oracle VPD policies are correctly configured.
The GL Balance by Account Hierarchy report is perfect for this requirement. It provides a summary GL report with multiple collapsible/expandable summary levels based on the GL account hierarchy.
You must rerun AutoConfig to ensure the context files and environment setups are correctly generated with all custom application paths.
Precisely. Blitz Report supports the replication of the ECC dashboard views within EBS. By leveraging the standardized Oracle ECC SQL queries , we ensure the output data is consistent with the dashboard metrics, but delivered in a high-quality Excel format for full data extraction.
This loss of environment variables is a known side effect, often if the other custom products were added manually and not originally via adsplice. You must manually re-enter the custom tops entries back into the `$APPL_TOP/admin/topfile.txt` file.
If the parameter type is set to Date, the entered parameter value is used as a bind variable for SQL execution without any timezone conversion, effectively binding to midnight of the date entered . However, if the parameter type is set to DateTime and you have timezone conversions enabled, the entered parameter value *will* be converted to server time before being used as a bind variable for SQL execution .
Blitz Report is praised for its reduced processing overhead and incredibly fast performance, making it suitable for high-volume data extracts. It is explicitly recommended for time-critical reports that handle mass exporting.
Yes, the Excel output file is automatically formatted with filters applied. Our system ensures that critical financial data types (like currency figures in GL Account Analysis reports) are correctly formatted and ready for immediate analysis, a process we call ‘Ungarbling Oracle EBS Financial Accounting’.
The platform is fundamentally focused on SQL to Excel reporting for non-developers. Once the technical report is saved, users access it through the familiar EBS Forms interface, providing parameters easily and receiving a structured Excel output for analysis.
To dynamically default the author’s email based on the current user, the SQL would typically join `FND_USER` with `PER_ALL_PEOPLE_F` using `FND_GLOBAL.USER_ID`. A complex example provided includes checking both the user’s direct email address and their person record email, using `coalesce` to return the first non-null result: `select coalesce(fu.email_address, (select papf.email_address from per_all_people_f papf where fu.employee_id=papf.person_id and sysdate between papf.effective_start_date and papf.effective_end_date)) email from fnd_user fu where fu.user_id=fnd_global.user_id` , .
That’s correct. Blitz Report handles the overflow by creating additional sheets automatically, ensuring comprehensive data capture, provided the total file size does not hit the 4G size limit.
Another key contribution from the Champion program is focused on Scheduling Preventative Maintenance Workload in Oracle EBS. This demonstrates the system’s flexibility in addressing complex operational and technical reporting needs across various EBS modules.
Yes, to simplify report development, several functions can be used in default value definitions without needing to select from `dual` . These functions include standard mathematical and string manipulation functions such as `abs`, `add_months`, `coalesce`, `decode`, `length`, `lower`, `nvl`, `to_char`, `to_date`, and `upper`, among others listed in the source documentation . This provides a cleaner syntax when calculating simple default values.
The standard ECC export limitation is that it often provides only CSV file type reports when exporting data from the dashboards. Blitz Report drastically improves usability by providing the required data as a perfectly formatted, native Excel file. This eliminates the need for manual cleanup.
To set a dynamic default value based on SQL, you define the parameter’s Default Value starting with the keyword `select` . For your requirement, you can use the SQL `select to_char(sysdate, ‘MON-RR’) from dual` . Blitz Report executes this SQL statement at runtime to derive the default value, which is particularly useful for defaulting dates, user IDs, or other session-dependent information .
Yes, the report includes columns indicating the existence of BOMs, Routings, and Sourcing Rules, along with creation details and item lot sizes.
Yes, the function automatically generates column text that uses the DFF’s form left prompt as the column alias, such as `msiv.attribute15 “Invoice UOM”`.
Enforcing additional security restrictions always adds complexity to the underlying SQL execution.
Yes, validated solutions exist, often contributed by industry experts via the Blitz Report Champion program. Specifically, reports for Calculating a WIP Production Job Details Report have been developed to address these manufacturing requirements using the capabilities of Blitz Report.
Data integrity is managed by the underlying EBS database and ISG services. For auditing and verifying data changes resulting from integration activity, you can use Blitz Report alongside the EBS audit function to track master data changes and ensure compliance.
If the output format is XLSX and the data exceeds the maximum row count (which is typically 1,048,576 rows), the data will automatically overflow to additional sheets within the same Excel workbook. The profile ‘Blitz Report XLSX Sheet Row Limit’ defines this maximum.
Many CAC inventory related reports, for example, only use inventory org security by default. The default setting for this profile is ‘No’.
You control this using the ‘Include Uncosted Items’ parameter. It defaults to ‘Yes’ to display items set to not be costed in your Costing Method Cost Type, ensuring a complete review.
The default limit, if not set on the individual report level, is ‘no limit’. This default behavior is also defined by the profile option ‘Blitz Report Row Limit’.
Yes, the configuration details differ between 12.1 and 12.2, particularly concerning the web server structure and security implementation. Separate procedures exist for Configuring TLS/HTTPS for Oracle EBS Integrated SOA Gateway (ISG) in 12.1. Similarly, enabling `mod_plsql` is also version-dependent (11i, 12.1.3, 12.2).
Key parameters include `p_table_name` and `p_table_alias`. It can also take optional parameters like `p_descr_flex_context_code` to restrict to a specific context, or `p_column_name_prefix` to add a prefix like ‘Item: ‘ to the column name aliases.
You must set the profile option ‘Blitz Report Use Ledger Security’ to ‘Yes’. Setting this profile to ‘Yes’ would also restrict by ledger access set.
The mandatory parameters are ‘Creation Date From’ and ‘Creation Date To’, which specify the date range for the item master creation date audit.
Yes, DBAs and support teams use Blitz Report to simplify tasks by running internal diagnostic queries directly from the EBS interface, avoiding manual database logins. You can create custom Blitz Reports to extract configuration values, check FND tables, or analyze application logs quickly, aiding in troubleshooting complex ISG setup issues.
Yes, you can use the Row Limit option available in the Options window. This allows you to restrict the number of rows in the output file.
The CAC New Items report is designed exactly for this. It shows items recently created based on the item master creation date and includes controls, costs, accounts, last transaction details, and current onhand stock.
Yes, you should use the function **`XXEN_UTIL.DFF_COLUMNS`**. This function is designed to return a SQL text snippet suitable for `&lexical` replacement in your report’s extraction SQL.
Configuring TLS/HTTPS for ISG REST services in 12.2 involves detailed steps, typically related to setting up the SSL certificates and enabling HTTPS communication on the required server ports. Proper setup secures data transmission between custom applications and EBS via the REST endpoints.
You can execute this query as APPS: `select decode(ab.bug_number, ‘31764501’,’31764501: ISG Consolidated Patch for 12.2 (20_3_5)’,…, ‘36828728’,’36828728: ISG Consolidated Patch for 12.2 (24_3_5)’ ) ‘ISG Patch’ from ad_bugs ab where ab.bug_number in (‘31764501′,’33168402′,’34766982′,’35629149′,’36828728′) and ab.language=’US’;` This checks for various known ISG patch numbers and returns their descriptive title.
The list of available reports can be restricted further simply by typing the first characters of the desired report name into the report name field.
The search is not case sensitive. You can enter your search terms without worrying about capitalization.
Yes, before calling submission APIs, you must initialize the application context session using `xxen_report.apps_initialize`, providing the user name, responsibility key, and responsibility application short code.
The ISG component is included in the Oracle E-Business installation but requires configuration to be enabled. A critical prerequisite is ensuring you have applied the appropriate ISG Consolidated Patch for your 12.2 version. You should run a specific SQL query against `ad_bugs` to determine which consolidated patch (e.g., 31764501, 35629149, or 36828728 for recent versions) is applied.
The search scope is comprehensive; it includes the report name and description, parameters, SQL definition, and template name and description.
The tuning documentation provides tables listing typical parameter settings based on user concurrency levels, ranging from development instances (11-100 users) up to 1001-2000 users, detailing values for parameters like `processes`, `sessions`, `sga_target`, and `pga_aggregate_target`.
The query `select xxen_util.user_id(‘SYSADMIN’) from dual` returns `0`.
Yes, the full text search is designed to operate like a ‘Google-like search’. It retrieves reports by report name, description, or the underlying SQL. This means you can effectively search by column names accessed by a SQL query.
If Automatic Optimizer Statistics Collection is active, it must be deactivated for EBS by setting the DB parameter `_optimizer_autostats_job=false`. You should instead schedule the concurrent program ‘Gather Schema Statistics’.
Oracle E-Business Suite reporting straight into Excel: 2,900+ ready-made reports, your own SQL, 150+ Excel uploads.