Maximo EAM

 View Only
  • 1.  BIRT report scripted source error

    Posted Wed March 24, 2021 02:54 PM
    Hello,

    Im new to Maximo development and BIRT reports and I am trying to import two sources obtained through SQL query. And I get a following error.


    This above is my open method. Fetch method is included in error.

    Full SQL query: SELECT t2.DESCRIPTION, t1.QUANTITY as UVOZ FROM ( SELECT MATERIAL, SUM (QUANTITY) QUANTITY FROM ( select MATERIAL, QUANTITY from maximo.mxzpackgage where TYPE = 'PREJEM' ) GROUP BY MATERIAL ) t1 RIGHT JOIN ( select VALUE, DESCRIPTION, ALNDOMAINID from maximo.ALNDOMAIN where DOMAINID='PACKAGE' ) t2 ON t1.MATERIAL = t2.VALUE

    Any idea what is causing the errors here?

    Kind regards,

    M.

    ------------------------------
    Matija Trost
    ------------------------------


  • 2.  RE: BIRT report scripted source error

    Posted Wed March 24, 2021 02:59 PM
    Edited by Tim Ferrill Wed March 24, 2021 03:02 PM
    I believe error 204 in DB2 is an undefined Object. You may need to alias one of your nested SELECTs:

    SELECT t2.DESCRIPTION, t1.QUANTITY as UVOZ FROM ( SELECT MATERIAL, SUM (QUANTITY) QUANTITY FROM ( select MATERIAL, QUANTITY from maximo.mxzpackgage where TYPE = 'PREJEM' ) GROUP BY MATERIAL ) t1 RIGHT JOIN ( select VALUE, DESCRIPTION, ALNDOMAINID from maximo.ALNDOMAIN where DOMAINID='PACKAGE' ) t2 ON t1.MATERIAL = t2.VALUE

    I also don't recognize the MXZPACKGAGE object. You might make sure that's spelled correctly.

    ------------------------------
    Tim Ferrill
    Solutions Consultant
    Intelligent Technology Solutions
    tferrill@webuildits.com
    www.webuildits.com
    @tferrill/@webuildits
    ------------------------------



  • 3.  RE: BIRT report scripted source error

    Posted Fri March 26, 2021 04:15 AM
    I have done some reading into Maximo BIRT documentation and saw that all of the column names need to have table as a prefix and must not have maximo as a prefix. I have adjusted my code accordingly and that seemed to have solved the 204 error. And yes mxzpackgage is spelled correctly (it was spelled incorrectly when created and this will be corrected in production version). I have also proofed my code before inputing it into BIRT.

    My code however still does not work. Instead I get the following error.


    Updated code for reference (it has been proofed in SQL)



    ------------------------------
    Matija Trost
    ------------------------------



  • 4.  RE: BIRT report scripted source error

    IBM Champion
    Posted Fri March 26, 2021 04:51 AM
    it looks like you may have a different error now.

    The revised error refers to executeQuery cannot be used for an update.
    It looks like that is being executed in a fetch method.

    You should look at the fetch methods.
    if there are multiple fetch methods then you can look at the raw XML and find the element with ID 155 and look at the surrounding text to identify the data set that contains the fetch method.

    ------------------------------
    Mark Robbins
    Support Lead/Technical Design Authority / IBM Champion 2017 & 2018 & 2019 & 2020
    Vetasi Limited
    Bristol
    https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
    ------------------------------



  • 5.  RE: BIRT report scripted source error

    Posted Fri March 26, 2021 04:16 PM
    Matia, 

    Mark is correct.  In the Fecth method for the Data set in which this Open method is modified please show us the code for that.  Likely you have a mismatched row declaration.  Also FYI if you click on the plus sign you will see an expanded set of error info. ;)

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------



  • 6.  RE: BIRT report scripted source error

    Posted Thu March 25, 2021 12:44 PM
    I agree with Tim.  Your 204 error indicates the object is unknown.  Have you tested the SQL with your SQL tool of choice, before popping it into your BIRT tool?  I normally proof my SQL first, then when I get a known data set back I can then begin developing my BIRT report. This approach provides me a positive test response so that when the data does not appear correctly in the BIRT tool I can take steps to diagnose and troubleshoot.

    ------------------------------
    Bradley K. Downing , MBA
    IBM Certified Adv. Deployment Prof. Maximo v7.6.1
    IBM
    Bakersfield CA
    ------------------------------