Support

Discussion Replies Created

Viewing 200 replies - 1,401 through 1,600 (of 2,985 total)

Yes, Tokens can be used to create a directory path dynamically, for example, based on report parameter values.

You have granular control over parameter filtering. For identifying performance issues, you can specify `Waiting for x Minutes` or `Running longer than x Minutes` to identify bottlenecks. You can also filter by `Phase` (Completed, etc.) and specific `Status` values like Error or Warning.

You should use the Excel Validation feature . This configuration involves entering a call to a validation PL/SQL function, mapping its parameters to the relevant SQL columns from the main report . This function executes directly on the server when the user saves the Excel file . The key requirement for your validation function is that it must return a message only in the case of validation failure; otherwise, it must return `null` .

Blitz Report offers specialized functionality for Oracle E-Business Suite – Concurrent Request Monitoring and Alert Reporting. The report parameters are specifically developed to pinpoint problematic requests. It enables alerting for critical processes such as concurrent requests and integrations.

The font size and font face are controlled independently by their respective profile options (‘Blitz Report XLSX Font’ and ‘Blitz Report XLSX Font Size’).

You should use the profile option ‘Blitz Report Additional Output Directory APPS Server’. This saves a copy of the report output file in the specified directory, in addition to writing it to `$APPLCSF/out`.

The system mandates strict control. Every modification, including parameter changes, is logged and maintained as full version control with audit comments tracked inside your EBS instance, ensuring complete report definition traceability.

The default font size is 10.

Blitz Report is an effective Discoverer replacement. Parameter functionality can be configured using internal LOV lookups or custom SQL LOV types, allowing developers to replicate complex cascading parameter dependencies efficiently within the Blitz Report interface.

That is indeed a crucial point; using SCAN listeners has been known to cause issues during ECC configuration. If your DBC file contains the SCAN entry, it is often recommended to manually replace the SCAN entry with the Virtual IP (VIP) address in the `EccConfig.properties` file and the generated `connection.dbc` file. Although the JNDI creation process attempts to read the connection string, using the VIP explicitly ensures proper resolution and connection establishment, circumventing potential issues associated with SCAN resolution in this specific ECC setup context.

Yes, complex parameter implementation is standard. You can define various parameters for filters like GL Balance, specific time periods (YTD), or hierarchical nodes. Blitz Report ensures the final output, regardless of complexity, is delivered as a perfectly formatted Excel file.

You should configure the profile option ‘Blitz Report XLSX Font Size’. This sets the font size for the Blitz Report XLSX output file.

Yes, `XXEN_API.export_file_data` accepts a list of IDs (`p_ids` of type `fnd_table_of_number`) and exports them all into one single XML file for batch processing.

To write the CLOB to the database filesystem, you use the Oracle procedure `dbms_xslprocessor.clob2file`. This procedure requires pointing to a directory name defined in `dba_directories` (such as ‘OUT_FILE_LOC’) and specifying the desired filename.

Yes, sometimes recreating the Database Connection (DBC) file resolves underlying issues, especially if the original file generation was problematic or if the EBS node details changed. To generate a new DBC file specifically for the ECC host system, you should execute the `AdminDesktop` utility on the EBS application node, specifying the fully qualified domain name of the ECC host using the `CREATE NODE_NAME` parameter. After generating the file (e.g., `EBSDB_ECC.ENGINATICS.COM.dbc`), ensure you copy this newly created file to the specified location on the ECC server, usually under the `quickInstall` directory as `connection.dbc`.

When the ‘Multiple Values’ option is enabled, the single bind variable syntax used in your SQL (e.g., `:p_account_number`) is intelligently substituted with a comma-separated list of values enclosed within an IN-clause during the report execution phase.

You can use the function `XXEN_API.export_file_data` or `XXEN_API.export_report_` to retrieve the report XML data as a CLOB.

If the DBC file appears correct, the issue is likely network related or an authentication problem. You should perform two essential network checks from the ECC server itself: first, verify the database host is resolvable by running a `ping` command using the hostname listed in the DBC file. Second, confirm that the database port is open for connections by attempting a `telnet` command (or similar tool) from the ECC server to the EBS database host and port. If either of these tests fails, you need to address networking or firewall rules.

The SQL text must include a bind variable restriction using one of the following comparison operators: =, , !=, like, or not like. Crucially, for the multiple values functionality to work by substituting the `IN-clause`, the table column must be on the left side of the comparison operator.

Missing environment variables for other custom tops often occur if those products were added manually instead of via adsplice. You will need to manually enter the custom top entries back into $APPL_TOP/admin/topfile.txt and rerun AutoConfig as a workaround.

This specific error generally points to a fundamental connectivity issue preventing the ECC Weblogic environment from establishing a database connection to the EBS instance using the defined JNDI datasource `ebsDB`. First, ensure that the EBS database host specified in the `connection.dbc` file on the ECC server is correctly configured and resolvable. You must check the `APPS_JDBC_URL` value within the `connection.dbc` file to confirm the hostname and port are correct.

That is correct. If you create a new application, you must plan for application tier downtime to stop and restart the Concurrent Manager to update its operational context.

Yes, the primary type is ‘Reports’, but the `p_type` parameter can also be set to values like ‘SQLs’, ‘Templates’, ‘LOVs’, ‘Assignments’, ‘Column Translations’, or ‘SQL Versions’, depending on what you need to export.

This issue is common when a new application is created. The Concurrent Manager must be explicitly restarted after running autoconfig to ensure it picks up and processes requests for the newly created application.

You should use the function `XXEN_API.export_file_data`. This function is designed for batch export and returns the data as a CLOB. You pass the list of report identifiers using the input parameter `p_ids`, which must be of the type `fnd_table_of_number`.

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.

A similar script example uses `xxen_report.space_to_underscore(c.report_name)` to sanitize the report name for use as a valid filename.

You set parameters such as `p_include_lovs`, `p_include_categories`, `p_include_assignments`, and `p_include_templates` to ‘Y’ to include those definitions in the XML output.

You control dependency inclusion using specific optional parameters in the export functions (both `export_file_data` and `export_report_`). These parameters are designed for the ‘Reports’ export type.

The writing is still handled by `dbms_xslprocessor.clob2file`. Within the loop, you retrieve the report name and ID, call `export_report_` for the XML CLOB, and then use `dbms_xslprocessor.clob2file` to write it to the file system using a filename derived from the report name.

No, for GL Wand and Spreadsheet Server, you first copy the legacy sheets into the Blitz FSG workbook, and then select the source tool in the Converter menu to start the migration.

Instead of `XXEN_API.export_file_data`, which bundles exports, you should use the function **`XXEN_API.export_report_`** inside a PLSQL loop.

The index was marked as unusable due to the failure. You must rerun the Blitz Report installation script (install.sh) again to correct the domain indexes and successfully load the report templates.

Yes, it supports importing definitions from GL Wand and Spreadsheet Server as well.

Yes. If you are on Oracle Database 11.2.0.4, for example, you can download the relevant patch zip, unzip it, find the CTX files within ctx/data/enlx, and copy all files to $ORACLE_HOME/ctx/data/enlx on all database nodes.

The Blitz FSG Converter allows you to import Financial Statement Generator report definitions from Oracle FSG.

This means your Oracle Text Knowledge Base files are missing from the database home. These files, such as droldUS.dat, are essential for linguistic initialization needed for index creation.

The ‘Blitz Report XLSX Date Format’ profile defaults to the value from the ‘ICX: Date format mask’ profile.

The profile option ‘Blitz Report XLSX Font Size’ defaults to 10.

The error ‘No live SolrServers available to handle this request’ often appears after cloning EBS because the ECC environment loses connection or trust with the new EBS configuration. To resolve this, after cloning, you must recreate the JNDI connection within the ECC instance by following the steps outlined in the documentation, specifically the section on ‘Configuring the JNDI to Connect to Oracle E-Business Suite’. After updating the JNDI, you need to bounce (restart) the ECC services to ensure the changes take effect and connectivity to the new EBS clone is re-established.

In a standalone ECC installation, the domain creation script initializes Zookeeper, and the `EccConfig.properties` file sets the `CLUSTER_MODE` to `standalone`. The configuration script also updates the Zookeeper host URL, often pointing to `localhost:2181/solr`. Because it’s standalone, the script also sets the replication factor, updating the property `dataset.num.replicas=1`, confirming that no replication is occurring. Zookeeper management is then started successfully along with the `eccManaged` server.

The profile option ‘Blitz Report XLSX Font’ defaults to Calibri.

Blitz Report is designed for mass data handling. It overcomes the CSV file type limitation and the data output volume limits associated with ECC dashboards. By leveraging the Time Critical reports functionality within our toolkit , you can export millions of sub ledger records efficiently to Excel with no volume limitations.

Based on the provided example configuration for an ECC Release 12.2 installation, the default heap memory settings were configured as: `ADMIN_HEAP_USER_MEM=1024M` and `MANAGED_HEAP_USER_MEM=2048M`. These are the starting points, but you may need to increase them, especially the Managed Server heap, depending on your data volume and concurrent user load. Ensure you review the memory requirements based on your specific environment size and usage profile.

Hi,
To set up parameter dependencies in Blitz Report, you can use the syntax :$flex$.parameter_or_lov_name. The parameter_or_lov_name should reference the name of the dependent parameter or the LOV (List of Values) name. This allows you to dynamically filter LOV results based on the value of another parameter.

Key Details:

  1. Case-Insensitive References: The parameter or LOV name is not case-sensitive.
  2. Special Characters: Any spaces or non-word characters in the name are automatically replaced with underscores.
  3. Handling Multiple Values: If the dependent parameter supports multiple values, you can use the xxen_util.contains function in your query.

Example:
If you have an Operating Unit parameter that allows multiple selections, you can configure the query for an AP Supplier LOV to filter results based on the selected operating units using xxen_util.contains. This ensures that the LOV dynamically adjusts to the selected values of the dependent parameter.

Additional Resources:
For a detailed explanation of dependent parameters and how to implement them, refer to the Developer Guide:
Blitz Report Developer Guide – Dependent Parameters

If you need help with a specific query or configuration, feel free to reach out to us. We’re here to assist you!

Yes, a less common but known issue that severely impacts Java programs on newer Linux servers is a lack of sufficient system entropy, which is often needed for cryptographic operations during startup. This specific problem is detailed in Oracle Support Document 1615981.1, ‘Java Programs Are Running Slower In Newer Servers Due To Lack Of Entropy In The System’. Investigating and resolving a low entropy issue can dramatically improve the startup time for Java-based applications like ECC.

The main advantage is guaranteed logical integrity. By using the official ECC Oracle queries, which have been tested and approved by Oracle, you ensure the report logic is sound and creates a single source of truth. This certainty is invaluable for complex financial sub-ledger reconciliations.

Yes, preserving the original SQL can make troubleshooting easier, as there are fewer changes introduced by the conversion engine.

An extremely slow ECC startup time, especially 45 minutes or more, often points toward resource starvation or system-level configuration problems. The first and most critical area to check is the ECC server’s resource allocation: please verify the assigned RAM, swap space, and CPU cores/frequency. You need to ensure that the startup process is not forced to utilize excessive swap space due to a lack of physical RAM, as disk-based swapping significantly degrades Java application startup performance.

By leveraging this import method, you achieve rapid report development in under 5 minutes. You simply paste the ECC SQL into the Blitz Report form, and the report runs immediately through Concurrent Requests, generating a perfectly formatted Excel output.

While this makes the import more robust, the converted SQLs will be less ‘pretty’.

Yes. The library of available ECC reports, exceeding 220 in total , specifically includes dashboards covering core functional areas such as iProc and Sub Ledger details. This means you can easily access the underlying, standardized Oracle ECC SQL queries for these critical areas.

The process supports importing worksheets directly into Blitz Report. This capability drastically reduces the manual effort typically required during migration. Once imported, these reports reside directly within the EBS forms interface, providing immediate access and Excel output without the limitations associated with older reporting tools.

You should set the profile option ‘Blitz Report Discoverer Import Preserve Original SQL’ to ‘Yes’. This turns off Blitz Report’s additional structural code enhancements when importing and converting Discoverer worksheet SQLs.

Blitz Report is frequently positioned as a direct Oracle Discoverer replacement. We continuously enhance this capability; for instance, recent developments include a feature for fully automated Discoverer migration. This streamlines the process of transitioning away from Discoverer entirely.

To disable the automated column header translation for all reports system-wide, you can set the profile option ‘Blitz Report Disable Column Translations’ to ‘Yes’ . If you only need to disable it for a single report, you may need to ensure no specific translation is set for the report’s columns, or clone the report and manage the headers manually, although the profile option affects automatic translation functionality globally , .

This profile provides the default value, but the runtime option ‘Output Format’ allows controlling the format at run time.

After running the standard `adadmin` ‘Maintain multi-lingual tables’ process following the installation of a new language, you must also run the concurrent request ‘Blitz Report Maintain Multilingual Tables’ . This ensures that all Blitz Report-specific multilingual data is properly synchronized .

To add translations for user-facing messages, you must navigate to Application Developer > Application > Messages . Query the messages starting with `XXEN` and then add the corresponding translations for the different languages installed in your system .

The default output file format is XLSX.

Translations for user interface labels shown directly on the Blitz Report run window (the user interface) are managed via Application Developer Lookups . You need to query the lookup `XXEN_REPORT_TRANSLATIONS` under Application Object Library and enter translations for the lookup code descriptions as required .

You need to change the profile option ‘Blitz Report Output Format’. Possible options are CSV (comma separated values), TSV (tab separated values), or XLSX (Excel).

Yes, `argument1` is specifically reserved for the Blitz Report Name.

It is indeed an essential part of the project implementation and upgrade toolkit. Tools like this, which leverage existing EBS functions for rapid checks, streamline overall project management and audit compliance without the typical reporting overhead.

The **user-entered report parameters start from argument 16** onwards, up to argument 87.

If you have multiple languages installed in EBS, Blitz Report supports multi-language functionality for several elements via the Oracle EBS translation menu icon . The translatable elements include the Report Name, Report Description, Parameter Name, Parameter Description, Category, LOV Description, and Column Headers . You access the translation form by clicking the globe icon typically available in the EBS Forms menu when viewing these fields .

By defining and saving this custom report within Blitz Report, you create a repeatable utility accessible via the EBS Forms interface, removing the necessity to log in to the database or navigate to the OAM page for verification. Once saved, the report definition, including the complex SQL, is instantly available for quick access.

When using `fnd_request.submit_request`, the report and template names, along with various runtime options, are mapped to `argument1` through `argument15`.

The ability to generate PDF output is integrated into the report post-processing capabilities of Blitz Report. If you are working within the Oracle Enterprise Command Center Framework, you can also note that ECC itself supports PDF exporting, typically limited by parameters like `EXPORT_PDF_MAX_COUNT`. However, for large scale SQL reports run via Blitz Report, the dedicated PDF output feature provides reliable document generation.

Yes, while Blitz Report is primarily known for delivering raw data into native Excel files for analysis, the system does include functionality to generate PDF output. This option addresses needs that require a fixed, non-editable document format.

The experience is fast and immediate. The Blitz Report runs immediately through concurrent requests without needing manual registration in system admin. The output is instantly presented as a perfectly formatted Excel file, complete with filters already applied, which significantly saves the EBS user time during operational drill-down.

The query needs to join `ad_bugs` (adb) and `ad_appl_tops` (aat) to map the bug number to the application top. You call the function `ad_patch.is_patch_applied` using four parameters: the release (`’R12’`), the application top ID (`aat.appl_top_id`), the bug number (`adb.bug_number`), and the language (`adb.language`). The result uses a `DECODE` statement to clearly display ‘APPLIED’ if the function returns ‘EXPLICIT’ and ‘NOT APPLIED’ otherwise.

We seed the product with in excess of 200 Blitz Reports that can be assigned to EBS forms using the Zoom method, covering core financial, HR, and supply chain process areas. Furthermore, if you have Enterprise Command Center installed, you can import an additional 220+ standard Oracle ECC reports into Blitz Report and assign those in the same manner.

Yes, Blitz Report is the optimal method for simplifying patch verification, allowing execution directly from the EBS Forms interface. You can create a custom report utilizing the standard Oracle function `AD_PATCH.IS_PATCH_APPLIED`.

A key advantage of this approach is that it is non-intrusive. By utilizing the native Zoom function, you configure the report within Blitz Report’s framework to ‘target the required EBS form’. This avoids complicated customizations to the Oracle Forms codebase itself.

Yes, Blitz Report is specifically engineered to integrate seamlessly into EBS Forms using the Zoom function. This integration method leverages standard EBS functionality, allowing you to embed contextual reports that run based on the data currently displayed in the form.

Yes, the default delimiter for CSV is a comma. However, in some countries, regional settings use a semicolon instead. You can manage this by setting the profile option ‘Blitz Report CSV File Delimiter’ to match your required separator.

Yes, you can define a Default report output format in the Report Options section of the Setup window. Alternatively, you can set a system-wide default using the profile option ‘Blitz Report Output Format’.

By leveraging Blitz Report’s compatibility with this standard Oracle functionality, you achieve the necessary data governance. It allows consultants to drop their queries directly into Blitz Report , knowing that the VPD mechanism enforces row and column-level control over sensitive data fields.

The available options are CSV (comma separated values), TSV (tab separated values), or XLSX.

When implementing custom security, Oracle generally advises caution. However, implementing VPD policies specifically on Blitz Report tables to secure developer SQL access is generally considered safe, as it cannot affect the standard EBS application or accidentally hide operational data from it.

The default output format is Excel XLSX. You can change this at runtime using the Options window. Look for the ‘Output Format’ field.

If the security logic determines the user is unauthorized (e.g., `l_user` is not equal to `’APPS’`), the function returns a restrictive predicate such as `’1=2’`. Oracle then dynamically appends this predicate to the user’s query, resulting in zero rows being returned for unauthorized users, effectively hiding all sensitive data.

You should try to execute the SQL exactly as shown in the logfile directly in a database development tool like Toad or SQL Developer. The logfile also provides the user-entered parameter values and corresponding bind variables, which are essential for reproducing the issue outside of EBS.

Yes. You can activate tracing by setting the ‘Blitz Report Trace Level’ profile option. If the value is null, tracing is off. Additionally, you can set ‘Blitz Report Debug’ to ‘Yes’ to write additional debug information.

Certainly. The implementation involves creating a PL/SQL policy function (for example, `xxen_vpd_per_phones_fnc`). This function executes dynamically at query time. Inside this function, you determine the running user’s context.

This error usually indicates an error encountered during SQL execution. The primary step is to review the report concurrent logfile for specific error messages.

You need to navigate to System Administrator > Security > ORACLE > DataGroup. Query the data group used by the responsibility and add an entry for the Enginatics Custom Application, linking it to the appropriate Oracle ID (typically APPS). This step ensures the concurrent program can determine the correct Oracle schema context.

An Admin can change the referenced report for ‘Subledger Details’ through updating the profile setting Blitz FSG Drilldown Report SD.

This error points to a missing configuration step: there is a missing Data Group entry for the Blitz Report custom application (Enginatics Custom Application) in the responsibility you are running the report from.

The ‘View Transaction’ drilldown can be configured to open the transaction form either in the default responsibility (used to run the FSG report) or in any GL responsibility with Subledger drilldown access.

You can configure this using the ‘Layout Options’ menu. The drilldown can be set to open in either a new workbook or a new worksheet.

Hi,

There are 2 profile options that control the display of the KPIs in the Supply Chain Hub

Profile Option: Supply Chain Hub: Show KPIs in Item Search Tab

Determines if the following KPIs will be displayed in the Items Tab

Profile Option: Supply Chain Hub: Show KPIs in Item Details Tab

Determines if the consumption APIs will be calculated and displayed in the Item Details Tab

These were introduced for performance reasons. To enable display of the KPIs please set either or both the profile options to Yes at whatever level id required.

Either at a personal user level:

Or through System Administrator if you want it set at SIte or Responsibility level:

Kind Regards,

Eric

The hierarchy ensures that the most specific override (Run window), followed by user preferences (User profile), determines the final time limit before falling back to less specific settings.

Yes, the log file will still show the user entered parameter values and corresponding bind variables, which is crucial for debugging.

The ‘Time Limit’ field in the run window is in seconds, but the profile option ‘Blitz Report Time Limit’ is in minutes.

The handling of multibyte characters in filenames is controlled by a separate profile option, ‘Blitz Report Email Attachment Multibyte Filenames’.

The default setting is ‘Yes’ (meaning the SQL is included in the log).

The default limit is 1000 characters.

The DBA CPU Benchmark1 report generates an output file of 500,000 out of a total of 561,495 records from a Cartesian product based on EBS standard FND tables.

The Profile option on user level (2) takes precedence over the Time limit on report level (3). Therefore, the 5-minute user limit would be enforced.

You can use the profile option ‘Blitz Report Email Attachment Filename Length Limit’. This truncates report attachment filenames to the specified limit for mail servers with limitations.

Yes, adjusting the ‘Minimum Value Difference’ parameter higher than the default of one will restrict the report output to only show larger discrepancies, helping you prioritize high-value reconciliation issues.

You set the profile option ‘Blitz Report Include SQL in Log’. Setting it to ‘No’ ensures the report SQL is not included in the Blitz Report log file.

Yes, if you upgrade the Command Centers, Oracle may update the underlying dataset queries . You should generally perform the mass delete (`mass_delete_ecc_reports.sql`) and re-import of the ECC dataset queries . Afterward, running the `METADATA` load and `FULL_LOAD` for your product is highly recommended to ensure all new features and DFF structures are correctly captured and indexed in the new version .

To yield meaningful results, you must ensure sufficient SGA memory is assigned so that the entire execution time is spent on CPU and not waiting on I/O. You can confirm this using the DBA SGA Active Session History report.

The mandatory parameters are ‘Period Name (Closed)’, which is the closed inventory accounting period you wish to report, and ‘Minimum Value Difference’. The default minimum difference is one, but you can set it to zero to view all differences.

Run the CAC Inventory Out-of-Balance report. This report compares summary and detail item cost information against the period end snapshot created during period close, highlighting any differences that could cause reconciliation issues.

You can use DBA CPU Benchmark1, DBA CPU Benchmark2, or DBA CPU Benchmark3. Benchmark1 and 2 focus mainly on PL/SQL processing time required to generate the output file from a large row count query. Benchmark3 measures performance for arithmetic calculations.

If you only run the `FULL_LOAD` without the preceding `METADATA` load, the DFFs may not appear, or the system might use an outdated metadata structure . The `METADATA` load explicitly updates the ECC framework’s understanding of the EBS flexfield structure, which is a necessary prerequisite before the data itself can be indexed correctly during the subsequent `FULL_LOAD` .

Yes, re-attach the library. The critical step is that when Forms Builder asks to remove the directory path, you must confirm with ‘Yes’. Then copy and recompile the updated `CUSTOM.pll`.

The DFFs are usually displayed in the lower transaction detail data section of the ECC dashboard . They may not appear in the ‘Main’ data group by default; instead, you often need to switch to the ‘Additional Information data group’ using the dropdown menu on the left side of the detail table . Once visible, users can filter or search based on these DFF values .

This compilation error means the Forms Builder is looking for the library at an incorrect hardcoded path. You need to open `CUSTOM.pll` in Forms Builder, expand the attached libraries, and remove the reported library (APPCORE2.pll).

To show Descriptive Flexfield values in ECC, it requires a two-step data load process . First, you must run the relevant Command Center data load concurrent program (e.g., Payables Command Center Data Load) with the load type parameter set to `METADATA` . This step ensures that the DFF structure is recognized by the ECC framework. Second, you must run the data load again with the load type set to `FULL_LOAD` to populate the DFF values .

If the user exists, the issue is typically resolved by manually clearing the cache using the Functional Administrator responsibility.

There are two main resolutions. First, check your Blitz Report installation log file for a warning about a missing GLOBAL user. If that warning exists, you must create the GLOBAL user via the Security > User > Define form (as outlined in MOS Doc 2287614.1).

For organizations maintaining their stable, customized operations on EBS , Blitz Report provides a robust, high-performance alternative to Fusion analysis tools. It focuses on solving real-world operational problems like backlog of concurrent requests or stuck transactions , ensuring EBS remains a highly functional platform with superior ad-hoc reporting capabilities.

The default value for this profile is ‘Active’.

The value of this profile dictates the structure used for the output filename, which is the attachment file name when sending reports via email or the output file on the concurrent processing server.

Yes, Blitz Report provides methods to quickly convert and fastrack Oracle BI Publisher report development in 5 simple steps. You can design and deploy a perfectly formatted Oracle EBS Excel report, leveraging your SQL, often in under 10 minutes. This includes converting complex XML data sources, such as CSTRAIVR_XML, into actionable, natively formatted Excel spreadsheets.

The default format is ‘Report Name – Template Name’.

You have multiple options for rapid deployment. New reports can be created within minutes. You can either copy an existing seeded report from the comprehensive library or browse the community reports and adapt one to your specific GL needs. This open-source reporting library significantly helps reduce development time.

The alternative setting is ‘All’, which includes all columns of the accessed folders, resulting in syntax like `aia.*`.

Blitz Report is an easy-to-use add-on fully integrated into Oracle Forms, meaning there are no new commands for users to learn. The tool specializes in delivering the required data as native Excel files , and importantly, it boasts no data limits on the output. Whether you have 5 million records or a few thousand, it generates perfectly formatted Excel or CSV files.

The profile option ‘Blitz Report Discoverer Folder Import Include Columns’ determines this scope. Setting it to ‘Active’ imports a SQL including columns used by the active Discoverer worksheets only.

Absolutely. When the Excel output is automatically generated, critical data types like currency figures, dates, and account details are correctly formatted. The report output is opened automatically with necessary Excel filters applied, ready for immediate, reliable financial analysis, including Year-to-Date (YTD) balances.

This limitation is commonly encountered when EBS 12.1.3 BI Publisher Excel templates generate XLS instead of XLSX, capping the row number at 65,536. Blitz Report addresses this directly by utilizing its Excel export engine, which is designed to overcome these data limitations and produce native Excel files.

You use the profile option ‘Blitz Report File Name Convention’. This defines the format for Blitz Report output filenames to include either report name, template name or both.

Yes, hierarchical reporting is streamlined. For GL Account Analysis, you can utilize built-in report flexibility, such as selecting the Parent Total (PT) option in the run-time parameters. This allows you to generate aggregated reports based on the parent account level efficiently, solving a major pain point in financial reporting.

Blitz Report addresses the fundamental challenge of Ungarbling Oracle EBS Financial Accounting data by focusing entirely on delivering highly structured, immediately usable output. It provides a specialized toolkit for General Ledger reporting and diagnostic issues. The key is the ability to generate perfectly formatted Excel output instantly from SQL.

If caching is ruled out, you should manually run the ‘Compile Security’ concurrent program (setting the parameter to YES) and verify it completes normally. If the problem persists, restarting Apache or all application services may be required.

You must clear the cache manually via the Functional Administrator responsibility, navigating to Core Services > Global Configuration > Caching Framework > Clear All Cache.

When you add the Blitz Report function to menus, Oracle EBS automatically starts ‘Compile Security’. If you try to access Blitz Report before this program finishes, the resulting error is often cached on the server side, causing the problem to persist even after security compilation is complete.

The final integration step performs several critical actions. First, it updates the `ECC_SOURCE_SYSTEM` table in the database, setting the `SECURITY_MANAGER` field to `oracle.ecc.security.extensions.EbsEccSecurityManager`. Then, it restarts the ECC managed server and applies the Connection Filter successfully. Finally, it updates the Source System connection string to point back to the EBS middleware host and port (e.g., `http://demo.enginatics.com:80`), completing the handshake between the two systems.

After running AutoConfig (`adautocfg.sh`) on the EBS application tier, you need to check the OHS configuration files, specifically looking for `ecc.conf`. The contents of this file should include a `RewriteEngine on` directive and a `RewriteRule` directing the `/ecc` path to the ECC managed server URL, usually including parameters like `?system=EBS`. If you struggle to locate `ecc.conf`, you can try navigating to `$FMW_HOME/webtier/instances` on the EBS node and running `find . -name ecc.conf`.

Yes, they leverage all standard EBS functionality. Users can schedule the customized requests in the normal way through the Concurrent Manager , utilizing enhanced delivery options for automated distribution.

Yes, you can use the custom database function `XXEN_UTIL.CLIENT_TIME (p_date in date)`. This function converts the date from the server’s timezone to the client’s local timezone if a difference is detected.

Post-upgrade, you must verify all security configurations. This includes ensuring TLS/HTTPS is correctly configured for the ECC Framework and that any custom reports accessing sensitive data adhere to Oracle VPD security policies.

To correct the resolution issue for the short hostname, you need to manually edit the `/etc/hosts` file on the ECC server. You should add an entry mapping the IP address of your EBS server to both the FQDN (e.g., `demo.enginatics.com`) and the short hostname (e.g., `demo`). Once this static entry is in place, the installer should be able to apply the Connection Filter successfully during integration.

Yes. The CAC Intercompany SO Shipping Transaction vs. Invoice Price report compares the transaction item cost from the selling internal organization to the invoice sales price charged to the internal receiving organization.

Absolutely. The customization only affects the presentation layer, not the underlying query execution. The report continues to run with incredibly fast performance due to reduced processing overhead , delivering the required, filtered data as a perfectly formatted native Excel file.

Yes, absolutely. Blitz Report functions as a project implementation and upgrade toolkit. You can use its capabilities to generate pre-upgrade BR100 extracts or mass export ECC data for consistency checks (validation reports) before and after the V6 implementation.

This specific failure during the commit phase of applying the Connection Filter rules suggests a configuration error in the rules themselves, often related to hostname resolution. You must check the `AdminServer.log` file in the Weblogic domain directory for more detail, as the error often manifests there as a `java.text.ParseException` with a message like ‘demo: Name or service not known’. This means that while the fully qualified domain name (FQDN) might resolve via DNS, the ECC installer is trying to resolve the hostname *separately* and failing, preventing the filter from being applied.

Yes, the parameter type definition specifically controls the validation of parameter values at run-time, ensuring the input matches the defined type (Char, Date, DateTime, Number, LOV types).

You must supply ‘Price Effective Date’, ‘Currency Conversion Date’, ‘Currency Conversion Type’, ‘PII Cost Type’, ‘PII Sub-Element’, and crucially, the ‘Assignment Set’. The Assignment Set is required because it defines the sourcing rules used when calculating PII item costs.

The user experience is simplified because we adopt the EBS user interface. Users navigate a familiar environment, minimizing the training required , and allowing them to create and share their own customized report layout templates.

Blitz Report guarantees reliable data extraction even during periods of ECC instability. Since our tool runs the underlying, proven Oracle ECC SQL queries directly from EBS , it ensures your reports bypass the dependent ECC application layer, providing continuous access to your data sets for business continuity.

For a DateTime parameter type, which includes the timestamp, if timezone conversions are enabled, the entered parameter value will be converted to server time before being used as a bind for SQL execution.

The CAC Intercompany SO Price List vs. Item Cost Comparison report is designed exactly for this purpose. It shows internal SO price lists, source organization item costs, and compares them against the ‘To Org’ item costs and PII amounts.

This step sets the necessary security and operating unit context for the concurrent program or synchronous execution to run correctly within the EBS environment.

Yes. This functionality allows users to modify the report layout using a familiar interface structure. They can add, reposition, or remove report columns with just a few mouse clicks. This capability is instrumental in reducing the overall IT dependency for operational reporting.

We have published dedicated resources for maintaining currency with Oracle ECC. The post ‘Oracle Enterprise Command Center Framework upgrade to V6’ details the required steps for this upgrade path. Similarly, we document other key upgrade steps, such as V4 to V5 and V4 to V3.

The Parameter Type definition controls this validation and conversion. For a Date parameter type, even if timezone conversions are enabled, the entered value is used as a bind for SQL execution without any conversion (using midnight of the date entered).

Yes, you must initialize the application context session. This is done by calling `xxen_report.apps_initialize`, providing the User Name, Responsibility Key, and Responsibility Application Short Code.

Yes, you can highlight a range of cells before clicking any discover button to perform Batch Discovery simultaneously.

Blitz Report is specifically designed to minimize reliance on IT for simple output changes. While non-developers cannot change the core SQL , they gain autonomy through the flexible column templates. Users can customize any report by removing or reordering columns so they only receive the data they need.

Tuning best practices include optimizing the number of concurrent processes, tuning the manager’s sleep cycle, and regularly checking for a high number of pending requests.

Yes, it includes the Parent indicator (Y means the segment value is a parent) and the Enabled indicator (Y means that the segment value is enabled).

The report correlates the conflicting requests by tracking those running between the held request’s requested start date and the conflict release date.

This feature populates the cells to the right of the segment value with detailed information. This includes the Segment Value and the Segment description.

Yes. The report is noted to be highly indicative but may not work 100% reliably because it currently does not consider request set conflicts.

Yes, re-run the Blitz Report installation script. After the installation is successful, if the trigger is still needed, you can enable it again using alter trigger apps.note_1342126_1_audit_trig enable;.

The solution is to temporarily disable the problematic custom trigger. For example: alter trigger apps.note_1342126_1_audit_trig disable;.

This trigger conflict happens because a custom audit trigger is trying to use a sequence’s CURRVAL before that sequence has been accessed (or initialized with NEXTVAL) in the session.

Blitz Report excels in operational reports for troubleshooting, such as those monitoring Asset tracking integration with Install Base and Inventory. You can set up rapid reports to analyze details of specific failing transactions impacting the Inventory module.

Yes, the profile option set at the user level overrides the Time Limit set specifically on the report level.

The AR Applied Receipts report is based on the Receivables Applied Receipts Register, typically listing details of applications, meaning yes, if a single receipt is applied across multiple documents, it would likely generate multiple detail rows showing each application.

Yes, the core functionality is delivering perfectly formatted Oracle EBS Excel reports. This clean output structure ensures the data is suitable for advanced analysis, including generating accurate pivot tables for inventory and cost accounting reports.

The full order, from highest to lowest precedence, is: 1) Run window options time limit; 2) Profile option on user level; 3) Time limit on report level; 4) Profile option on responsibility level; and 5) Profile option on site level.

For the unapplied receipts, use the AR Unapplied Receipts Register report. This is a detail unapplied receipts report providing the receipt number, date, and amount.

The Run window options time limit always takes the highest precedence. This is the value that the ‘Blitz Report Monitor’ concurrent program uses to determine when to automatically terminate a report.

The platform enforces robust controls. When you create a new report by pasting your SQL, Blitz Report automatically assigns a version control number and provides full audit/version history for any subsequent modifications. You can also assign the report access based on user, module, or responsibility.

For the applied receipts detail, use the AR Applied Receipts report. Its default template provides a detail listing with no pivot summarization.

Blitz Report is a dedicated replacement tool for this function. It shows planners How to replace Oracle ASCP exceptions with Blitz Report. This enables the export of custom, actionable planning exceptions into structured Excel files for quick resolution.

Yes, ECC V11 configuration parameters include settings like `EXPORT_PDF_ENABLED = true` and defining a `EXPORT_PDF_MAX_COUNT` (default 100). Separately, Blitz Report also supports generating PDF output from its reports via post-processing.

Yes, Blitz Report helps access the detailed data related to PWB and Advanced Supply Chain Planning (ASCP). It is used to generate reports for planning ideas, metrics, and detailed data extracts like pegging exports, which are traditionally challenging to pull directly from the Workbench.

Run the ONT Order Holds report. It provides a detail Sales Order report listing all order lines currently on hold and the reason for the hold.

Blitz Report is designed to integrate reporting simplicity into complex functions like SCM and Supply Planning. It provides rapid access and export capabilities for critical data such as Inventory Planning metrics, BOM components, Forecast details, and transactional data, helping the Supply Chain Hub reach another level of simplicity.

Blitz Report enforces data security through Oracle VPD. This is enforced at the database layer based on the user’s context and privileges, entirely independent of the network protocol (TLS/HTTPS) used to access the EBS application tier.

For a header-level summary, use the ONT Orders report. It provides a detail Sales Order or Quote header report, including status, amount, and invoice status information.

The example file name ‘ONT Orders and Lines – DIFOT Template’ suggests that custom templates are available for metrics like Delivery In Full, On Time (DIFOT), allowing specialized analysis of the core sales order data.

Yes, the CST Item Cost Reports acts as a flexible set, offering numerous reporting options like ‘Element by Sub-Element’, ‘Activity by Department’, and ‘Operation by Activity’.

The ONT Orders and Lines report provides this level of detail. It is a detail Sales Order or Quote header report with line item details covering status, cost, project, and shipping information.

The report allows you to specify up to five activity parameters (p_activity1 through p_activity5). You must enter the desired Cost Type to report.

DBAs simplify their life by using Blitz Report for diagnostic and support reports. This includes querying FND tables and monitoring concurrent requests. Such tools provide visibility into system status and parameters that may be causing connection errors, even when standard interfaces are inaccessible.

For this report to show your activity costs, you must first define your activities and then associate your sub-elements by activity. The report logic relies on these Resource Activity assignments.

Ensuring your EBS 12.2 is protected from attacks through HTTP is a major security consideration. While separate setup posts exist for securing ISG in 12.2 and ECC V11 properties show default HTTP configurations (`EBS_MIDDLETIER_PROTOCOL=http`) , securing ECC requires explicit configuration to use SSL ports (e.g., `ECC_ADMIN_SSL_PORT=7777`, `ECC_MANAGED_SSL_PORT=7778`). You must ensure OHS and WebLogic components are correctly handling the secured connection.

To execute a Unix shell script on the application server, you should use the ‘Custom Postprocess’ option, which is separate from the PL/SQL database triggers . The script must be located under the `$CUSTOM_TOP/bin/custom/` directory (e.g., `$XXEN_TOP/bin/custom/generate_and_send_pdf.sh`) and is invoked with several run-time parameters, including the output filename and parameter values, allowing it to handle distribution or external processing , , .

Use the CAC Item Cost Break-Out by Activity report. This report is specifically designed to show item costs by cost element, using up to five entered activities.

During TLS setup, various scripting or certificate errors can occur. Common issues include errors related to certificate chain trust, incorrect keystore passwords, or issues with common name (CN) mismatch, such as the `ERR_CERT_COMMON_NAME_INVALID` error sometimes seen in Chrome on Windows when dealing with self-signed certificates.

A highly practical example is the FA Depreciation Projection report . Since the report data relies on Oracle calculations, it requires running the standard Oracle ‘Depreciation Projection’ concurrent program first . The Blitz Report references a custom database package (e.g., `XXEN_FASPRJ`) which submits and waits for the completion of that concurrent program *before* the main report SQL executes, ensuring the data is current and complete .

Configuring TLS for ECC is critical for security. This process typically involves setting up the necessary SSL certificates on the ECC web server components (often WebLogic) and configuring the ECC Framework properties to use HTTPS protocols for both administrative and managed server ports.

You must recompile the library using `frmcmp_batch.sh` with `module=$AU_TOP/resource/CUSTOM.pll` and `module_type=library` to generate the `.plx` file, and then restart the forms session.

Yes, parameter values are passed to the custom package functions . The runtime values of the Blitz Report parameters become available inside the package body through corresponding variables that match the parameter names in the report’s parameter anchors . This allows your PL/SQL logic (e.g., in `beforereport`) to condition its actions based on the user-selected parameters .

The call to `xxen_event(event_name);` must be inserted at the end of the `event()` procedure in the package body of your `CUSTOM.pll`.

The functions within your custom DB Package must adhere to specific naming conventions: `afterpform`, `beforereport`, and `afterreport` . Furthermore, these functions are required to return the boolean data type . For example, the `beforereport` function would execute your staging table update logic before the main report SQL runs .

You can use the FND Flex Value Sets, Usages and Values report. This details value sets and values, including usages, validation type, format type, validation table, and columns.

You define these steps using the Before report trigger and After report trigger options, located in the Report Options section of the Blitz Report setup . These fields reference a custom DB Package that contains the necessary PL/SQL functions . The ‘Before report trigger’ is ideal for data preprocessing, such as updating staging tables, while the ‘After report trigger’ is suitable for post-processing tasks like clean up or calling standard Oracle PL/SQL code , .

Since your `CUSTOM.pll` is already modified, the installer skipped the update. You need to open your `CUSTOM.pll` in Forms Developer, attach the `XXEN.pll` library, and insert a call to `xxen_event(event_name);`.

Yes, correcting misclassified accounts can have implications. The report description references Oracle Note 872162.1, ‘R12: Troubleshooting Misclassified Accounts in General Ledger’, which explains the necessary steps and implications of correcting these issues.

Viewing 200 replies - 1,401 through 1,600 (of 2,985 total)