IBM Support

IV68911: BIRT CANNOT RETRIEVE CORRECT DATA IN NON ENGLISH-US LOCALE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When customer builds a report in BIRT Designer and the report
    is not from English-US, the report runs fine on BIRT Designer
    connected directly to the database.
    
    Then customer logs into Tririga and runs the same report using
    a user that is not set in English (in this case, French).
    
    The reports does not run correctly throwing an error.
    
    If the user connects using a English_US user, the same report
    runs just fine from inside Tririga.
    
    Error snippet:
    "There is an error in the report query loading. Can not
    retrieve data to generate the report."
    
    This is a valid platform defect in this scenario where the
    system OrgName field in any BO is not returning the translated
    value in the query.
    

Local fix

  • There maybe 3 work arounds for this.  One is to have 2 reports
    use both the OrgName field of each query when joining in the
    Birt report assuming that the value of the OrgName field in the
    budget record is the same organization record as the value in
    the cstOrgName field of the budget record.  If those 2 fields
    are not referring to the same organization record then this
    work around will not work.  Another work around is to add a
    similar cstOrgName field in the floor record which will have
    the same organization data as of the OrgName field in the
    floor.  Then use both cstOrgName fields in the floor and budget
    record when joining the 2 reports in Birt.  Another work around
    is to join both queries in TRIRIGA that will yield the same
    result sets in Birt instead of joining them in Birt.
    

Problem summary

  •  This issue is due to not returning the localized path value of
    the system OrgName field of any BO which is represented as a
    reference query value in the query engine.
    

Problem conclusion

  • Birt report will now merge results of 2 data sets using "Full
    Outer Join" between "System Organization (OrgName)" field and
    locator field referencing a localized "System Hierarchy Path
    (triPathSY)" field of an Organization business object, when
    report is run by a language user. This is targeted for the
    3.4.1.2 fix pack, and the 1H2015 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV68911

  • Reported component name

    TRI APPLCATION

  • Reported component ID

    5725F26AB

  • Reported release

    340

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-23

  • Closed date

    2015-03-09

  • Last modified date

    2015-03-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • 999
    

Fix information

  • Fixed component name

    TRI APPLCATION

  • Fixed component ID

    5725F26AB

Applicable component levels

  • R341 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHEB3","label":"IBM TRIRIGA Application Platform"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"340","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
30 March 2022