Support
Discussion Replies Created
Blitz Report fully supports accessing external data sources. To achieve integration with non-Oracle platforms like Vertica, MySQL, or even DB2, the technical foundation must be built first using standard Oracle database functionality: the Database Link.
The report creation process is highly simplified. Developers or power users can take their precise SQL queries and integrate them instantly into the Blitz Report application. The system manages the EBS registration overhead automatically, allowing rapid deployment of new supply chain metrics.
Certainly. The system is used for various advanced planning functions. You can create specific reports for ASCP pegging exports, performance metrics (KPIs), and detailed plan explanations beyond just exceptions. This capability extends into other Supply Chain areas like Inventory Planning and Work Orders.
The main advantage lies in the output format and data handling. Blitz Report enables the rapid export of the exception data into a structured Excel format, unlike the traditional PWB exports which may be cumbersome or suffer from data limitations. This ensures that planners can manipulate the data directly in Excel for deeper analysis.
Yes, Blitz Report is specifically promoted as a tool to replace Oracle ASCP exceptions. It allows planners to create custom reports based on the underlying ASCP planning data, providing the flexibility needed for detailed analysis.
Yes, we continuously enhance import capabilities. We are planning to add Polaris RWB import source.
By housing all reports (R2R, O2C, P2P) within the Blitz Report toolkit, you gain centralized management with full version control. You reduce reporting delivery time and ensure consistency, as all reports run through the efficient Concurrent Request framework with perfectly formatted Excel output.
You manage visibility by assigning the report to a specific responsibility or user. Database-level data access control is further enforced automatically by your existing Oracle VPD security policies.
You can import Discoverer reports complete with their existing assignments and parameters. This leverages your previous investment in report logic and speeds up development by eliminating manual administration overheads. Furthermore, security assignment by responsibility is maintained in the new Blitz Report structure.
The profile option ‘Blitz Report Template Excel Upload Size Limit’ defines the threshold for showing a warning message if a user attempts to upload an Excel template file exceeding that size . The default limit is 5 MB . While larger files can be uploaded, exceeding this limit may trigger the warning due to potential impact on performance.
No, Blitz Report overcomes the data constraints inherent in older EBS exports (like the 65,536 row limit in BI Publisher XLS files). Its export engine is designed to handle mass exporting volume data reliably into native Excel format.
Template permissions are controlled by the profile option ‘Blitz Report Template Access’ . You can set this profile to ‘Private and shared’ to allow supervisors to create both private and shared templates . If you set it to ‘Super User’, those users can create private and shared templates AND modify templates owned by others . The ‘Private only’ setting restricts creation to only templates owned by the user, while ‘No Access’ only allows viewing and usage .
Yes, Blitz Report is integrated with modules like Cost Accounting. You can create reports for Simple And Effective Cost Accounting Reporting , and specialized views like GL Account Analysis to help ‘ungarble’ complex financial data.
You can import over 220 ECC SQL queries and have reports ready in under 5 minutes. Since these queries are Oracle-approved for dashboard operation, using them in Blitz Report ensures guaranteed accuracy and establishes a single source of truth for R2R analysis.
Yes, you can suppress duplicate rows directly within the template configuration by checking the ‘Distinct’ option . This flag, when selected, ensures that only unique rows of data are included in the final report output, effectively handling duplicate records resulting from the extraction SQL .
The platform specializes in generating perfectly formatted Oracle EBS Excel reports. This high-quality native Excel output is ideal for performing complex EBS financial analysis with pivot tables, ensuring data integrity and ease of manipulation.
Blitz Report is strategically built to support import functionality from various legacy and embedded Oracle reporting sources, including Discoverer, BI Publisher, and ECC dashboard queries. This capability allows you to rapidly build your operational report suite.
The pivot table section of the template screen is divided into four critical components : 1) Filters are columns used to restrict the overall data displayed in the pivot, often used for high-level entities like Customer or Vendor . 2) Columns define which data points will appear as separate columns in the pivot (e.g., Period or Project) . 3) Rows define the data summary level for each row (the dimension being analyzed) . 4) Values define the numeric data that will be summarized (e.g., Amount) . Note that only columns selected in the ‘Displayed Columns’ list can be used in the Pivot table definition .
Once you have your SQL, you open the Blitz Report form within EBS Forms. You paste the query, define simple parameters (if needed), and save it. The tool instantly registers the report without requiring you to engage with the complex concurrent program definition process.
To make a template the default layout for all users, you must select the ‘Global Default’ checkbox within the template definition screen . This action is typically restricted to users with Developer access or specifically, those authorized with the ‘Super User’ role within the profile option ‘Blitz Report Template Access’ , . The available sharing levels for templates are Site (all users), Responsibility, and individual User .
Clicking the ‘Run’ button launches the process, which generates the Excel output file with drilldown capabilities to Oracle-linked data.
The Hands On Tutorial – Oracle EBS – SQL to Excel Reporting for Non-developers is specifically designed for users like you. Blitz Report aims to bridge the gap, allowing users to move beyond waiting for IT by providing a simplified interface for report creation using SQL.
If set to ‘No’, all reports available to a user (even from responsibilities different from the current login) are displayed.
The default value is ‘Yes’ for users with standard user access.
The Ledger Name is defaulted based on the responsibility from which you are running the report. This selected ledger is then defaulted to the output.
The default behavior for standard users is to enforce this. The profile option ‘Blitz Report Filter Reports by Responsibility’ should be set to ‘Yes’. This filters the LOV of Blitz Reports to records assigned to the user’s current login responsibility only.
First, you must select the Report Name GL Financial Statement and Drilldown (FSG). You should leave the Template Name field blank to ensure the default template is utilized.
You can use the FND Users report, which lists EBS users, their status, responsibility count, and Blitz Report usage.
A new version number is added and stored automatically only for each report SQL update. Other setup modifications, such as changing the report name, description, or parameter settings, are not tracked in the version history.
Yes, the GL Balance by Account Hierarchy report creates collapsible/expandable summary levels based on the GL account hierarchy, which relies on the underlying flex value set definitions, typically configured through rollup groups.
The report extraction SQL must start with either select or with. If you enter the SQL directly through the form, the input is limited to 32767 characters. For queries larger than that limit, you must use the Upload Large SQL functionality from the tools menu.
The multiple values functionality is only available for parameters defined with the anchor styles `1=1` (or `n=n`) or `&lexical` . It is explicitly not supported for parameters defined using the simple `:bind` anchor style .
Hi,
Check and correct the TNS_ADMIN variable setting in frmcmp_batch.sh as per Oracle note 431324.1. Replace:
TNS_ADMIN=$ORACLE_HOME/network/admin
with:
TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}
Update the template file at $ORACLE_HOME/inventory/Templates/bin/frmcmp_batch.sh to make the change persistent for cloned environments. If needed, apply similar corrections to other scripts (frmbld.sh, frmcmp.sh, etc.) and their templates. For EBS R12.2, repeat this for both run and patch file systems.
Please check https://www.enginatics.com/installation-guide/#ORA-12154 for more details.
The FND Rollup Groups report provides this master data view, detailing flex value sets with rollup groups.
The basic steps involve five key actions: 1) You must enter a unique report name and an optional description. 2) You then enter the main extraction SQL query. 3) Next, you define optional parameters along with their corresponding SQL text or WHERE clauses. 4) You must test the report thoroughly by clicking the Run button. 5) Finally, you set up the user access rights (Assignments) to make it available to business users.
No, if you use complex operators such as `>= :bind_variable`, the automated IN-clause replacement is not possible, and consequently, the ‘Multiple Values’ checkbox will not be available for that parameter . This feature is restricted to equality and simple likeness comparisons for clean conversion to an `IN` clause .
Yes, after updating fnd_cp_services and committing the change, you must restart the Output Post Processor for the new setting to take effect.
To create new reports, your profile option Blitz Report Access must be set to either Developer or System. This profile setting is necessary because it makes the Setup button visible on the Blitz Report run window, which opens the setup interface.
A critical requirement for the automatic IN-clause replacement to function is that the parameter SQL text must have the table column name on the left side of the comparison operator and the `:bind` variable on the right side . For example, `column_name = :bind_variable` works, but a structure like `:bind_variable = column_name` will not enable the multiple values functionality .
Yes, ‘Period Name’ is a mandatory parameter to specify the inventory accounting period you wish to report.
You must update the fnd_cp_services table and append the parameter :-Dmail.mime.splitlongparameters=false to the existing developer parameters column for the OPP service.
Yes, Blitz Report automatically supports the conversion to an `IN-clause` (or `NOT IN-clause`) when the user selects the ‘Multiple Values’ checkbox . This automated replacement works for restrictions using the ‘not equal’ operator (`!=` or “), as well as ‘equal’ and ‘like’ operators . During SQL execution, the restriction is replaced with the equivalent `IN-clause` that includes all selected values .
Yes, control over security features like Ledger and Operating Unit is managed through specific profile options , . The profile option ‘Blitz Report Use Ledger Security’ controls activation of ledger security . Many Cost Accounting (CAC) reports, for example, default to using only inventory organization security, but setting this profile to ‘Yes’ would enforce restriction by ledger access set . Conversely, setting it to ‘No’ (or its default value) would deactivate that layer of security.
This typically occurs in Oracle EBS 12.2 because JavaMail uses RFC 2231, which causes issues with some email clients that don’t support splitting long filenames. You need to adjust an Output Post Processor (OPP) developer parameter.
Yes, set the parameter ‘Show Transaction Details’ to ‘Yes’ to display columns such as Event Class, Transaction Type, Transaction ID, and Transaction Date.
To secure data via VPD through Blitz Report, you must set up the specific tables or column names you wish to protect in the lookup `XXEN_REPORT_VPD_POLICY_TABLES` . You navigate to Application Developer > Application > Lookups > Application Object Library, query the lookup type, and enter a unique lookup code for each table or column, including the owner, table, and optional column name as the lookup meaning .
You can absolutely use Oracle Virtual Private Database (VPD) with Blitz Report to control access to sensitive data at the column or row level . VPD policies are set up on the database objects to automatically add restrictions before SQL execution . However, it is important to note that VPD policies implemented this way only secure data access through the Blitz Report concurrent program and not through direct access via database tools or standard Oracle EBS processes .
Yes, the report includes the mandatory parameter ‘Include Lab Batches’, which defaults to ‘No’ but can be set to ‘Yes’ to include laboratory batches.
You should use the CAC OPM WIP Account Value report. This report displays WIP values for process manufacturing, showing the cumulative WIP Valuation accounting entries processed by Create Accounting.
They are often used to populate an &lexical anchor with a SQL text dynamically before the report execution begins.
The key advantage of using the required LOV parameter approach is enhanced flexibility . It allows your developers to test SQL queries directly using database tools without needing to initialize the full application user session context, which simplifies debugging . Furthermore, this method supports use cases like shared service centers, where a specific user might need elevated access to see all data across the system .
The reports generate perfectly formatted Excel or CSV files. The tool’s export engine is designed for mass exports of volume data, ensuring reliability and overcoming limitations like the 65,536 row cap found in older BI Publisher XLS formats.
Report AR Transactions and Lines, for instance, uses a hidden Ledger parameter to dynamically generate a string for the revenue account columns, based on the chart of accounts segment setup.
For maximum flexibility and maintainability, the recommendation is to use the unrestricted base tables, such as `ap_invoices_all` (the `_all` tables), rather than relying on Oracle’s VPD-secured synonyms , . Security is then enforced by making the Operating Unit a required parameter in the Blitz Report . The List of Values (LOV) for this parameter is explicitly limited to include only the operating units accessible through the user’s current login responsibility and security profile .
You can develop proven EBS reports using ECC SQLs in under 5 minutes. This speed is achieved because you bypass the need for traditional concurrent development and deployment processes.
You can define these using Negative display sequence numbers in the parameter setup. This hides the parameter from the user interface.
Yes, the platform supports the replacement and import of legacy tools like Discoverer. Once imported, these reports immediately fall under the Blitz Report’s version control and audit framework.
The migration process tracks changes with full audit comments. This history documents modifications to the SQL query, changes to parameters, assignments (user, module, responsibility), and any custom column templates applied, ensuring complete traceability.
The default message displayed is stored in FND message XXEN_REPORT_ONE_PARAM_REQUIRED (for expressions enforcing at least one entry), or XXEN_REPORT_INSUFFICIENT_PARAM for general insufficient restriction errors. You can also specify a custom message text.
The key differentiation is complexity reduction. With Blitz Report, there is no hassle of registering new concurrent programs and reports with System Administration. The tool provides immediate registration and version control with a unique control number, avoiding duplication and lengthy setup procedures.
Yes, the ‘Filter Before Display’ setting is used for very large LOVs to avoid performance issues. If checked, the user is prompted to enter a partial value before the LOV is displayed, querying a restricted dataset instead of all records.
You reference parameters by their name (in US language), prefixed with a colon, and with spaces replaced by underscores. The expression would be: :Customer_Name is not null or :Account_Number is not null.
The setting is called ‘Validate From List’. If this is checked, validation enforces selection of one record and wildcards are not allowed. If it is unchecked, wildcards are permitted.
No, it is optional. If left blank, the report defaults to using your inventory organization’s AvgRates or Frozen Cost Type, depending on your Costing Method.
Blitz Report is ideally suited for this. Consultants can simply drop their SQL scripts directly into the Blitz Report form. The system automatically handles the deployment, providing full version control with audit comments logged directly within your EBS instance.
That depends on how the parameter LOV is defined. Some LOVs enforce the selection of one particular value, such as an account number, while others allow matching by wildcards like ‘%’ or ‘_’.
You need to use the Advanced Required Parameters feature, which accepts a logical expression to define complex validation logic.
If a resource does not have a cost, the ‘Resource Rate’ column will have a blank or empty value.
For persistence, you must also apply the identical correction to the associated template file located at `$ORACLE_HOME/inventory/Templates/bin/frmcmp_batch.sh`. If you are on EBS R12.2, you must repeat both actions on both the run and patch file systems.
You have two primary options to display the LOV for any parameter. You can either double click directly into the parameter value field, or you can click on the three LOV dots located on the right side of the parameter field.
You need to replace the line `TNS_ADMIN=$ORACLE_HOME/network/admin` with `TNS_ADMIN=${TNS_ADMIN:-$ORACLE_HOME/network/admin}`. This ensures that the existing environment variable for `TNS_ADMIN` is honored if set.
Use the CAC Resources Associated with Overheads Setup report. This report shows resources associated with overheads and specifically identifies any resources without any overhead associations, reporting ‘Missing’ in the first column if no setup exists.
This specific error is known to occur because the `TNS_ADMIN` variable is incorrectly set within the Oracle compilation scripts itself. You must modify the `frmcmp_batch.sh` script, located in `$ORACLE_HOME/bin/`.
Yes, you can use the GL Header Categories Summary report for summarizing journals based on categories.
While the report supports attachments, Oracle documentation references potential errors with attachments during requisition creation in R12.2, which, although not directly related to this report, suggests being mindful of attachment functionality.
The GL Journals report provides this information. It reports on GL batches and journals, including amounts and attachments.
The DBA AWR SQL Performance Summary report provides visibility into ‘Application Wait Time’, which captures total elapsed time in seconds from the wait event class ‘Application’, such as ‘enq: TX – row lock contention’ caused by an uncommitted session’s update blocking another session.
Yes, you can import BI Publisher reports complete with their existing assignments and parameters. This further speeds up the development process by leveraging existing parameter definitions without the administration overheads traditionally required.
No, the Snapshot feature preserves all other Excel formulas and formatting in the file. Only the Blitz FSG functions are targeted.
For analysis involving the Active Session History (ASH), utilize the DBA SGA Blocking Session Summary. While row lock scenarios sometimes involve idle blocking sessions not visible in ASH, this summary helps correlate active blocking events. You can perform further analysis using a pivot in Excel for faster root cause identification.
The final major step is migration. Reports can be seamlessly migrated from the instance they were developed on to test and production instances. This process is straightforward and avoids the version challenges typically associated with deploying traditional EBS concurrent programs, because the report definition is self-contained and version tracked within the Blitz Report framework.
Yes, during import, reports are assigned to categories automatically based on the originating concurrent program’s application module, which is defined by the lookup XXEN_REPORT_APPLICATIONS.
It functions similarly to Excel’s *Paste Values*, but it is designed to remove all Blitz FSG functions from the workbook, replacing them with the current calculated results.
You should primarily use the DBA Blocking Sessions report, which shows the chain of currently blocking and blocked database sessions derived from `v$wait_chains`. This gives you the current lock scenario.
Yes, the default email subject is stored in the FND message `XXEN_REPORT_EMAIL_SUBJECT` . You can modify this message text, or create a new custom message, using placeholders like `&REPORT_NAME` and `&ROW_COUNT` for automated replacement at run-time . If you create a custom message (prefixed with `XXEN_REPORT_EMAIL`), you must update the profile option ‘Blitz Report Email Subject Message’ to point to your new message name .
When exporting reports, you have the option to include Categories in the exported XML file. This allows you to create that category automatically in the destination environment upon import.
The subsequent step is to modify the report within Blitz Report’s simple interface, eliminating the need for cumbersome XML formatting and XSL templates. Blitz Report handles formatting automatically and delivers native Excel output. Crucially, the fourth step involves testing the query and adding full version control to the new Blitz Report definition.
When manually submitting the ‘Blitz Report’ concurrent program, you must populate the report parameters starting from argument 16 onwards . Crucially, the values must be entered in exactly the same order as they appear on the Blitz Report run window . For instance, if ‘Ledger Name’ is the second parameter on the form, its value must be entered into Parameter2 (which corresponds to Argument 17 of the concurrent request) .
The conversion process for BI Publisher reports like CSTRAIVR is simple and quick, often completed in 5 steps. First, you must identify the data source used by the original BI Publisher report (often ending in `_XML` or similar data definitions). Next, you paste the proven SQL query from this data source directly into a new Blitz Report definition.
To create or manage categories, you navigate to the menu Tools > Categories from the Blitz Report Setup window. You can also review existing assignments there.
Other available pivot templates include summaries by Apply Date, Batch, Debit Account, and GL Date. If you select the Default template, you get a detail listing with no pivot summarization.
You should use the ‘Snapshot’ tool under Blitz FSG Tools. This converts your report into static values.
Yes, it organizes the data output. Remember that Blitz Report can also handle very large row counts by automatically overflowing data exceeding 1,048,576 rows to additional sheets, even without a configured Sheet Break.
By default, when using Oracle’s standard delivery options for scheduled Blitz Reports, the system automatically suppresses the delivery of an empty output file (zero rows) , , . If your interface requirements actually demand that empty files *must* be sent, you can override this behavior by setting the profile option ‘Blitz Report Suppress Empty File Delivery’ to ‘No’ , .
Yes, if you have a large number of reports, category assignments help users find the reports they require. Users can pick a Category from the dropdown list on the run window.
It is located in the section defining the Displayed Columns, alongside the ‘Aggr.’ and ‘Sort Order’ settings.
Yes, the report provides a ‘Pivot: Summary by Customer Name’ template. This template summarizes data by Balancing Segment, Receipt Currency, and Customer, with drilldown capabilities to the details.
You should use the AR Applied Receipts report. It is based on the standard Oracle Receivables Applied Receipts Register (Short Name: RXARARRG).
The split is triggered whenever the value in the selected column changes. You would apply the ‘Sheet Break’ option to the Legal Entity column to achieve the desired segmentation.
The easiest and most common way to schedule a Blitz Report is to run it once from the run window with all parameters set correctly, and then navigate to View > Requests to copy that submitted concurrent request . You then update the schedule frequency and configure the Oracle standard delivery options , . These options natively support sending the report output as an email attachment, uploading it to a WebDAV cloud storage location, or sending it to an FTP destination, making it ideal for interface requirements .
When importing a BI Publisher report, the original data definition XML is stored in the BIP Code field. When this field is populated, Blitz Report automatically executes the `dataTrigger` section, such as `beforeReportTrigger`, of the associated XML template before it executes the primary report SQL, supporting reports based on preprocessed data in global temporary tables.
You can use the Sheet Break feature in the template configuration. The Sheet Break function allows you to split the output file into different sheets.
The time limit set in the Run window options takes the highest precedence. The full hierarchy 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.
The Time Limit defines the maximum run time in minutes for the report. If a report exceeds this limit, the Blitz Report Monitor concurrent program automatically cancels it. This prevents excessive server load caused by reports running too long, often due to insufficient parameter restrictions.
To protect reports, you should set the Type field to Protected or System. Reports of this type are visible to users with access profiles set to User Admin or Developer, but they can only be edited by users who have their access profile set to System. This provides an additional layer of protection, especially useful for system functionality like outbound interfaces.
High CPU time suggests the SQL is reading a lot of data, often due to poor indexing or full table scans. You can drill down using the SQL_ID and Plan Hash Value to analyze the execution path using DBA SGA SQL Execution Plan History.
Look primarily at the ‘Cpu Time’ and ‘Buffer IO’ columns; high CPU time often indicates massive amounts of data read from the buffer cache. To target the time window, ensure you filter the report using the snapshot interval parameters corresponding to your morning peak hours.
No, report load scripts and XML files generated by choosing ‘Reports’ contain the **current report SQL versions only**; they do not include previous version SQL history.
Yes, for DFFs, you can use the `XXEN_UTIL.DFF_COLUMNS` function. This function returns a SQL text snippet, such as `msiv.attribute15 “Invoice UOM”,` designed to replace an `&lexical` placeholder like `&flexfield_columns` in your main `SELECT` statement. This ensures the column names use the DFF’s form left prompt as the alias.
Enginatics in Discover the secret of perfectly formatted Oracle EBS Excel report creation in under 10 minutes No, that’s where flexibility for business users comes in. While a business user cannot create reports themselves, they can easily modify the report layout by leveraging the folder style template functionality. They can add, reposition, or remove columns with just a few mouse clicks, ensuring they only receive the data they need, reducing IT dependency significantly.
Enginatics in Discover the secret of perfectly formatted Oracle EBS Excel report creation in under 10 minutes The distribution is immediate and integrated. Since Blitz Report uses the application foundation functions such as concurrent requests and value sets , the report runs immediately through the concurrent request mechanism. You then assign it to the necessary users or responsibilities for testing, potentially securing sensitive data by configuration.
For the Ledger name restriction, you should use an `n=n` anchor (like `1=1`). In the GL Balance pivot example, the main query includes `where 1 = 1 and gl.ledger_id = gb.ledger_id`. The Ledger restriction parameter would insert its clause at the `1=1` position, while the dynamic period list is inserted at `&gl_period_pivot`.
You should run the DBA AWR SQL Performance Summary report. This report retrieves summarized execution statistics, focusing on CPU-intensive SQLs, as the default sorting prioritizes maximizing server load optimization.
Yes, the Report Options section of the Setup window includes the Custom Postprocess field, which provides the same functionality as the runtime option to default a postprocess on the report level.
Yes, when `p_type` is ‘SQL Versions’, you can use the parameter **`p_creation_date`** to restrict the versions exported based on their creation date.
Enginatics in Discover the secret of perfectly formatted Oracle EBS Excel report creation in under 10 minutes Blitz Report handles the final output formatting seamlessly. The Excel output file is automatically generated and formatted with filters applied. This saves the EBS user time by delivering native Excel data immediately, completely eliminating the labor-intensive process of XML or XSL template design required by BI Publisher.
To add a new custom postprocess script name to the runtime options LOV, you must add it to the Oracle lookup XXEN_REPORT_POSTPROCESS_SCRIPT.
Yes, the export mechanism supports historical data. You use the function `XXEN_API.export_file_data` with the parameter `p_type` set to **’SQL Versions’**.
The parameter SQL text needs to generate a comma-separated list of periods, formatted correctly for the PIVOT clause, which typically includes aliases. For instance, if the Period parameter derives the year, the lexical reference might be replaced with: `’Jan-20′ jan_2020, ‘Feb-20’ feb_2020, ‘Mar-20’ mar_2020, …`. The resulting list contains periods from the first of the derived year up to the period indicated in the input parameter.
No, if a user has developer access, all reports are still displayed on the Setup window anyway, as it is required for development.
The script must be placed under the $CUSTOM_TOP/bin/custom/ directory, for instance, `$XXEN_TOP/bin/custom/generate_and_send_pdf.sh`.
Enginatics in Discover the secret of perfectly formatted Oracle EBS Excel report creation in under 10 minutes Yes, this speed is one of Blitz Report’s core benefits. The secret lies in bypassing the complex overheads of traditional reporting tools. The rapid development process typically involves just three main technical steps: pasting your tested SQL query, defining the necessary runtime parameters, and configuring the basic Excel report template.
Dynamic pivot tables require the &lexical parameter reference, as it allows for the insertion of variable SQL snippets, which is necessary for the column list in the PIVOT clause. In the example of GL Balances, the PIVOT clause structure is `pivot(sum(amount) for period_name in (&gl_period_pivot))`.
You define this using the Custom Postprocess runtime option. This option allows a custom shell script to run after report completion, typically used for distribution or output transformation.
The default value for developers is ‘No’.
To force the parameter value to be inserted as literal text (lexical text) instead of a bind variable, you must use the special placeholder “ within the parameter’s SQL text field . This method ensures that the final SQL executed includes the literal value, which can be useful when you purposefully want to enforce reparsing for different parameter values, as illustrated in the Discoverer EUL access example .
No, even if a developer has unrestricted access, they can still check report availability because the Run window reports LOV is still restricted by a current responsibility.
Yes, you can use the same anchor multiple times within a single report SQL definition . For every occurrence of the anchor (e.g., `&group_by_vendor` in both `SELECT` and `GROUP BY`), Blitz Report will insert the corresponding parameter SQL text during runtime . This allows you to maintain consistency across different clauses based on a single parameter input.
Yes, the user description part of the output can be deactivated by setting the profile option **‘Blitz Report Show User Description’** to ‘No’.
Yes, if the user leaves the parameter value blank, the core functionality of the `&lexical` anchor dictates that the corresponding reference is completely removed before the SQL is executed . Therefore, the runtime SQL would simply revert to `group by pha.currency_code`, which is perfectly valid SQL and ensures the intended aggregation occurs without the vendor dimension . This prevents syntax errors and optimizes performance.
The SQL statement `select xxen_util.user_name(0) from dual` returns ‘SYSADMIN (System Administrator)’.
The GL Journals report includes attachments information in its output, allowing you to review batches and journals that have attachments.
For developers, the profile option ‘Blitz Report Filter Reports by Responsibility’ is typically set to ‘No’. This ensures all reports available to the developer are displayed, regardless of the current login responsibility.
You must manually drop and recreate the failing package. Log into SQL*Plus as the APPS user, execute drop package XXEN_UTIL;, and then run the package specification and body scripts (@XXEN_UTIL.pks and @XXEN_UTIL.pkb) from the installer’s SQL directory.
Yes, maintaining a local copy may result in version discrepancies between your file and the Oracle EBS application, which will be highlighted as a warning.
Yes, the overloaded function **`XXEN_UTIL.USER_NAME(p_user_id in pls_integer)`** returns the user name and user description based on the user ID.
If set to ‘No’ (the default), the system will attempt to download and open the report output file (XLSX or CSV) automatically upon program completion.
For modifying structural SQL elements like the `GROUP BY` clause, the `&lexical` anchor is the appropriate tool, as it allows insertion of arbitrary SQL snippets . You should place the anchor, perhaps named `&group_by_vendor`, within your `GROUP BY` clause immediately preceding the mandatory columns, like `group by &group_by_vendor pha.currency_code` . The parameter associated with this anchor would have a SQL text containing the optional column list, such as `pv.vendor_id,` .
This violation happens during recursive SQL execution while attempting to grant privileges during the package compilation process. This requires a manual intervention.
Yes, you can set the profile option ‘Blitz Report Show Log Instead of Output’ to ‘Yes’. This is primarily used for debugging purposes as it opens the logfile automatically instead of the report output upon completion.
The report description references the important Oracle note: ‘R12: Troubleshooting Misclassified Accounts in General Ledger (Doc ID 872162.1)’, which explains the implications of correcting these issues.
If Single Sign-On (SSO) is enabled, and the profile option ‘Blitz Report SSO Enabled’ is set to ‘Yes’ at the Site level, the connection is established automatically upon clicking the Login Button.
The Authentication form will appear, where you must enter your User Name and Password before clicking ‘Submit’.
Run the GL Code Combinations report. It includes the parameter ‘Show Misclassified Accounts’ specifically to identify code combinations with this discrepancy.
You must open the locally stored template file and click on the ‘Login’ button. This action initiates the connection process.
You need to run a mass recompile script as APPS user, executing `alter package [package_name] compile;` and `alter package [package_name] compile body;` for all XXEN packages. After successful compilation, you must then rerun the `frmcmp_batch.sh` command to compile the `XXEN_REPORTS.fmb` form.
Not necessarily the form file itself. This error most commonly indicates that the required database packages (like XXEN_REPORT, XXEN_UTIL, XXEN_API) are in an invalid state, preventing the form compilation from succeeding.
No, to modify another owner’s templates, the user would require the ‘Super User’ access level.
A 504 Gateway Time-out during a heavy data query like this often indicates a resource constraint on the application server rather than the query itself. The solution is to increase the OAFM servers Java Heap Size.
Yes, ‘Private and shared’ is the default setting for this profile.
Yes, the report includes the Advanced Accounting Option based on the `mtl_transaction_flows_v` view.
You should use the profile option ‘Blitz Report Template Access’ set to ‘Private and shared’. This allows users to create both private and shared templates.
No, the report documentation indicates that it has no required parameters.
Reports set to type ‘Protected’ or ‘System’ can only be edited by users with their access profile set to ‘System’.
The CAC Intercompany Relationship Setup report is designed to show the accounts used for the intercompany parameters and relationships across operating units.
To create new Uploads, the ‘Blitz Report Access’ profile option must be set to ‘System’. Only users with System access can assign uploads.
Yes, only users with the ‘System’ profile can run reports of type ‘System’.
The highest level, ‘System’, is required. This grants full access, including uploads, system, and protected reports.
Yes, the procedure includes an output parameter `x_report_id` which returns the ID of the newly created Blitz Report.
The procedure requires the application short name (`p_application_short_name`) and the concurrent program name (`p_concurrent_program_name`) associated with the BI Publisher report.
If you performed a minimal Oracle Linux installation, you may be missing required packages . You should install packages such as `psmisc` (which provides `fuser`) and `bind-utils` (which provides the `host` command) using `yum install psmisc` and `yum install bind-utils` .
A successful application of the Connection Filter is confirmed in the output logs by the explicit message: `Connection Filter is applied sucessfully.. Done.` . Furthermore, the integration step involves updating the `ECC_SOURCE_SYSTEM` table, setting the `SECURITY_MANAGER` to `oracle.ecc.security.extensions.EbsEccSecurityManager`, and updating the source system connection string .
Yes, the segment dropdown displays all available segments for the currently selected ledger, ensuring context is maintained.
Yes, you can use the PLSQL procedure **`xxen_api.import_concurrent_program`**. This procedure is used for migrating BI Publisher reports of the Java executable `XDODTEXE` type.
The dropdown list includes the special ‘Period’ value, which is used specifically for period name discovery within the Blitz FSG tools.
To review the setup of transaction types, use the INV Transaction Types report.
You must manually edit the `/etc/hosts` file on the ECC server . You should add a static 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 correctly configured, the installer should be able to resolve both forms of the hostname, allowing the Connection Filter to be applied successfully .
For category assignment, run the INV Default Category Sets report. This is a master data report that lists Inventory functional areas and their default category sets.
The dropdown list displays all available segments for the currently selected ledger. Each segment is labeled with its name and its corresponding segment number in parentheses (e.g., ‘Company (1)’).
This specific failure, resulting in a `ParseException` related to the short hostname (e.g., ‘demo’), occurs because the ECC installer or Weblogic is attempting to resolve the short hostname separately and is failing, even if the FQDN resolves correctly , . This prevents the necessary Connection Filter rules from being applied . This is a critical point of failure during integration .
Yes, if the parameter type is set to ‘LOV’ or ‘LOV custom’, selecting one of these types automatically controls the validation of parameter values at run-time . This ensures that the user is selecting a valid, pre-defined value based on the LOV query .
Use the INV Item Default Transaction Locators report. This is a master data report that lists Inventory Items and the default locators assigned for various transactions.
Yes, you can use the utility function `XXEN_UTIL.SERVER_TIME` . This function takes a date input and returns the converted server time . For example, `select to_char(xxen_util.server_time(to_date(‘2020.09.03 09:00:00’, ‘YYYY.MM.DD HH24:Mi:Ss’)), ‘YYYY.MM.DD HH24:Mi:Ss’) from dual` can be used to check the resulting server time format .
Proactively, you should analyze any FND patches before application and check if they contain newer versions of files like `AFCPFILB.pls` or `AFCPWFPB.pls` (which relate to `FND_WEBFILE`/`FND_WEBFILEPUB`) and communicate this information to your support team.
If you need the time component and desire server timezone conversion, you must use the ‘DateTime’ parameter type . If timezone conversions are enabled, the entered parameter value is automatically converted to the server time before it is used as a bind variable in the execution SQL .
If persistence issues arise, you should contact support and provide the output of a SQL query that extracts the current version numbers of the `FND_WEBFILE` and `FND_WEBFILEPUB` package bodies from the `dba_source` to help analyze the incompatibility.
The AR Transactions and Lines report provides detailed transaction and line-level data, while the AR European Sales Listing provides a high-level summary aggregated by country and currency.
No, if the parameter type is set to Date, even if timezone conversions are enabled globally, the entered parameter value (e.g., ‘2025-01-01’) is used as a bind variable for SQL execution without any conversion . It is effectively bound as midnight of the date entered .
This occurs because FND patches may overwrite the customized versions of these packages. To resolve this, you must run the ‘Blitz Report Compile fnd_webfile’ concurrent program from the System Administrator responsibility.
You can use the ZX Lines Summary report. This provides a tax lines summary to help understand the different applications, entity codes, and events that generate tax lines.
If you upgrade command centers, you can use the script `mass_delete_ecc_reports.sql` to remove all previously imported ECC Blitz Reports before re-importing Oracle’s latest dataset queries.
The AP Suppliers Revenue Summary report provides the AP suppliers (PO vendors) revenue summary across different operating units.
Use the AR European Sales Listing report. It is a summary report listing sales by country and currency code, including transaction amount/currency and accounted amount/currency.
The required input parameter is the `p_dataset_key` (varchar2), which identifies the specific ECC dataset you wish to import.
For bank branches, you should run the CE Bank Branches report. This report is a repository of all bank branches covering both internal and external bank accounts and indicates usage (Internal, Supplier, Customer).
Yes, the AP Suppliers report provides this master data view. It includes AP suppliers (PO vendors) along with supplier sites, contact information, and bank account details at both the vendor and site levels.
You can use the procedure `xxen_api.import_ecc_dataset`. This allows programmatic importing of ECC dataset queries.
You must rerun the entire Blitz Report installation script after creating the missing default lexer preference to ensure index creation and template loading succeed.
Yes, our Diagnostic Pack reports have been explicitly updated to account for the changes introduced with container databases regarding how AWR data is stored and accessed. You should try these updated reports for solving performance issues in your multitenant databases, ensuring accurate performance metrics are retrieved regardless of the PDB/CDB separation.
Yes, this error is specific to certain 12c multitenant database configurations where the default lexer preference is missing. To resolve this, you need to follow the instructions provided in Oracle note 1994919.1 to create that missing default lexer preference.
You typically consult the Patch Readme associated with the ECC adapter patches for the file manifest . For instance, knowing that `FND_ECC_UTIL_MLS_PVT` is related to the ATG ECC Adapter Patch, you would look up that patch ID (e.g., 30535550 for V5) and confirm the file name, such as `30535550/fnd/patch/115/sql/FNDECCMLSUTB.pls`, which contains the package definition .
Blitz Report is designed to simplify DBA tasks by serving as a dedicated repository for all your performance queries, replacing the need for ‘organized’ text documents. Blitz Report offers a simpler way to work with the AWR, providing immediate reporting functionality integrated within the Oracle EBS environment. We have updated Diagnostic Pack reports specifically for AWR, which streamline the analysis process for you.
If the script finishes without error but imports nothing, it is highly likely that you missed applying the product family consolidated patches . You must apply all necessary patches: the adapter patch, the ATG consolidated patch, and the product family consolidated patches that contain the specific Command Centers you intend to use (e.g., Payables, Receivables) , . Review sections 4 and 6 of Doc ID 2495053.1 carefully to ensure all prerequisites are met .
Absolutely, for exporting multiple reports simultaneously, you should use the more generic function `XXEN_API.export_file_data`. This function accepts a parameter `p_type` set to ‘Reports’ and also takes a collection of report IDs (`p_ids` of type `fnd_table_of_number`) to export multiple definitions into a single consolidated XML CLOB file. This approach is often useful when automating migration tasks using shell scripts or when consolidating related reports for a single deployment batch. You can find detailed examples of how to populate the `l_ids` collection by querying `xxen_reports_v` to gather all the relevant report IDs based on your criteria, such as a name pattern like ‘%test%’, before calling the export function.
Yes, after applying critical EBS patches, especially those affecting core ATG components, you must ensure the changes are active . This means completing the entire `adop` cycle through the `cutover` phase . If you are stuck at the import step, you must start both EBS and ECC services before proceeding with `./patchEccFiles.pl` . The system needs to recognize the newly created packages and functions to proceed with the language conversion logic .
This error, where the system fails to find `FND_ECC_UTIL_MLS_PVT`, confirms that the mandatory ATG ECC Adapter patch is missing or incomplete on your EBS instance , . For example, in ECC V5, the necessary package definition (`FNDECCMLSUTB.pls`) is contained within the patch `30535550: ATG ECC ADAPTER PATCH – V5` . You must apply all mandatory EBS patches specified in Oracle Support Document 2495053.1 , .
Yes, `dbms_xslprocessor.clob2file` is specifically designed to write large object (CLOB) data onto the database filesystem. When you use this procedure, you must point to a pre-defined directory name which is set up in `dba_directories` on the database server. Please ensure that the directory object referenced (e.g., ‘OUT_FILE_LOC’ in the provided examples) exists and the necessary database permissions are granted to the user executing the PL/SQL block to write files to that location.
To export a single report programmatically, you should utilize the function `XXEN_API.export_report_` in the `XXEN_API` package, which takes the report ID as an input parameter. When calling this function, you can specify input parameters like `p_include_lovs` and `p_include_assignments` with a value of ‘Y’ to ensure all related LOVs and assignments are included in the generated XML CLOB. After obtaining the CLOB data containing the report definition and all selected related objects, you can use the standard Oracle procedure `dbms_xslprocessor.clob2file` to write the contents onto the database server filesystem.
The development environment within Blitz Report ensures that all consultant-provided SQL scripts maintain full version control with audit comments tracked directly within the EBS instance, mitigating project risk.
Access to every Blitz Report is controlled by assignment to a specific user, module, site, or responsibility within EBS. Furthermore, data security (row and column access) can be reinforced using Oracle VPD policies.
Oracle E-Business Suite reporting straight into Excel: 2,900+ ready-made reports, your own SQL, 150+ Excel uploads.