Prev
Next
Forums Lawson Business Intelligence/Reporting/Crystal

Crystal report links error?

Sort:
You are not authorized to post a reply.
Author
Messages
Milo Tsukroff
Veteran Member
Posts: 47
Veteran Member
10/3/2008 11:03 AM
    Can anyone help out here, or, have you seen this before?  Our reporting department has again found problems with our Crystal Reports reports.  These reports are developed for LBI.  They suddenly find that all of the reports they check on have links that seem to have 'gone wild'.  Even worse, sometimes they see a field ('BUDGET_NBR') in one of our two custom views just disappear, or, the field shows up in the other view which doesn't have that field in the first place.  The reports are wrong in some sections until the reports are fixed manually.

    To fix the problems, the views are removed from the report  in the Database Expert, are then re-added, and then set the  links back up. This also happened to us a year ago, when we were just implementing LBI (our notes from then are sketchy). 

    Our setup:  LBI 9.0.1.10 with WebSphere 6.0.2, Crystal RAS XI SP4, Oracle 10g, LSF9, Apps 9.0.0.2.

    So what's going on here?  Any ideas would be appreciated!
    Chris Martin
    Veteran Member
    Posts: 277
    Veteran Member
    10/6/2008 12:02 PM
      When you say "custom view", I'm assuming you mean a database view? Kind of sounds like somebody made changes to the view being used as the data source.
      Milo Tsukroff
      Veteran Member
      Posts: 47
      Veteran Member
      10/10/2008 7:49 PM
        Checked with the Database gurus.  No changes were made to the custom views. 

        What we've figured out that at this point is that the the underlying data linkage changed due to changes in the G/L levels and how they are configured.  That would not technically damage a report, but, it's the only thing that we changed.  The process created "orphaned" records which definitely threw the reports off.  This may have just possibly caused a glitch with linking.  We are looking at that now. 

        On the other hand, it might have been the anti-virus software .... but the log doesn't go back far enough to prove or disprove that theory.  Oh well.
        You are not authorized to post a reply.