Comments

  • 1-6 of 6
  • Sudhir K

    Hi Manish,

    I was able to get filtering issue for 3 of the parameters fixed but 2 of them still have issue. I am attaching the document which has the complete details including the SQL query and the filtering issue we are facing.

    -Sudhir

  • Sudhir K

    Hi Manish,

    Your inputs were very helpful for me to reach the solution. I was able to find that below function is the best way to meet my requirement. I thought I would share with you.

            coalesce(NULL,:vendor_alt_name) IS NULL
        ) OR (
            d.vendor_name_alt IN (
                :vendor_alt_name
            )

    Thank you so much once again.
    -Sudhir

  • Sudhir K

    Hi Manish,

    Thank you for your help. When I remove the LEFT keyword, it is working fine. But the reason I have added the LEFT join is to include in the report the invoices which do not have lines created yet. If I remove this LEFT join how can I make sure that the invoices without the lines are also listed in the report?

     

    -Sudhir

  • Sudhir K

    Thank you Manish,

    I was not able to find a way to make the parameter mandatory on the BI Report. Can you please let me know how to make a parameter mandatory?

    -Sudhir

  • Sudhir K

    Hi Manish,

    Thank you so much for your help on this issue. it works fine except with one issue. When I choose multiple sources from the drop down, I get the attached error. I modified the query a little bit to replace '=' with 'in' but still no luck.

    select * from (  SELECT DISTINCT a.source ,
                      a.invoice_num,
                      a.invoice_date,
                      a.creation_date,
                      b.line_number,
                      b.line_type_lookup_code,
                      b.description "Line Description",
                      b.amount "Line Amount",
                      b.period_name,
                      b.accounting_date
        FROM ap_invoices_all a
             LEFT JOIN ap_invoice_lines_all b ON (a.invoice_id = b.invoice_id)) Z
             where   z.source in nvl(:p_source, z.source)
    ORDER BY invoice_num, line_number
     

  • Sudhir K

    Thank you Ba!

     

    Our partner is suggesting that we utilize the FX revaluation functionality on journal level detail to perform our FX translation in our reporting ledgers.   Are you aware of this being an acceptable way to configure Oracle cloud to address FX translation accounting?