Home › Discussions › Questions & Answers › Using Logical Expressions for Multiple Values Parameter Check

Using Logical Expressions for Multiple Values Parameter Check

Avatar photoCustomer July 24, 2023 at 5:07 am

I want to enable the ‘Multiple Values’ checkbox for a parameter so users can input a list of account numbers. What specific criteria must the parameter’s SQL text meet for this checkbox to be available and function correctly?

Viewing 8 reply threads
  • Author
    Replies
    • Support July 26, 2023 at 1:56 am  

      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.

    • Avatar photoCustomer July 27, 2023 at 3:32 am  

      If I implement a parameter using this multiple values feature, how does Blitz Report handle the substitution of the bind variable at runtime?

    • Support July 28, 2023 at 12:14 pm  

      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.

    • Avatar photoCustomer July 29, 2023 at 11:30 pm  

      We need to implement a complex GL Account Analysis report using multiple input parameters. Can Blitz Report handle these complex parameters while still providing formatted Excel output?

    • Support July 31, 2023 at 4:39 am  

      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.

    • Avatar photoCustomer August 1, 2023 at 6:12 pm  

      If we were migrating a Discoverer report that relied heavily on cascading parameters, how easy is it to replicate that functionality?

    • Support August 1, 2023 at 10:06 pm  

      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.

    • Avatar photoCustomer August 3, 2023 at 1:37 am  

      We need to track every time this report definition is modified, including changes to the parameter constraints.

    • Support August 3, 2023 at 7:12 am  

      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.

  • Author
    Replies
Viewing 8 reply threads
  • You must be logged in to reply to this post.

Login with:
Popular Posts
How to track master data changes using Oracle EBS Audit function and Blitz Report™ 123746

Oracle Enterprise Command Center Framework Release 12.2 installation and integration with Oracle EBS 12.2.8 19797

Oracle Discoverer replacement – importing worksheets into Blitz Report™ 14615

How to check if a patch is applied in Oracle EBS 12.2 14387

Oracle Discoverer 11.1.1.7 installation and integration with Oracle EBS R12.1.3 14073

Oracle E-Business Suite 12.2.8 upgrade to version 12.2.9 11965

Oracle E-Business Suite 12.2.7 upgrade to version 12.2.8 9898

Migration to Java Web Start in Oracle EBS 12.2 instance 9890

Securing sensitive data with Oracle VPD 7794

EBS 12.1.3 BI Publisher Excel templates generate XLS instead of XLSX and limit row number to 65,536 6448

Blog Archive
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
Recent Events
2026
2025
2024
2023
2022
2021
2020
2019
2018