Prev
Next
Forums Financial Management Lawson S3 Financials

Two Questions:

 2 Replies
 0 Subscribed to this topic
 43 Subscribed to this forum
Sort:
Author
Messages
Eric Haugen
Basic Member
Posts: 13
Basic Member
7/3/2009 1:17 AM
    Thanks to anyone thhat can anser two questions I have, Someone posted:

    07/01/2009 05:04 PM EditEditQuoteQuoteReplyReplyAlertAlert 
    I would appreciate any help anyone may provide on these two problems. I'm working on a brand new apps 9.0 upgrade (we are already on Env 9). Things are going well except:

    A Lawson client on this board has previously reported a problem with workfile(s) going to the wrong (previous) productline directory post upgade (files were going to prod80 instead of prod90 for example) post upgrade. Even though they deleted and re-added the jobdefs and had checked that WRKFLOPTS which was pointed to PROD90. 

    In our case (and thiers), the csv was still writing to PROD80.  WRKFLOPTS in PGMDEF was pointing to PROD90 and the job step is pointing to productline PROD90 (no csv overides at the jobstep level). We had dumped/modified/reimported the WRKFLOPTs to point to PROD90. Verified that there is no jobstep override (I dumped the jobwrkdef(sp)) and there was none. The client previously reported what sounds like the same problem on this site did not post if/how this was corrected (other than deleting the jobdef and creating a jobdef using a new job name). if they used the same jobname, the file still went to PROD80). How can that be?

    I've been researching this looking at GEN tables and can't figure out why this is occuring. 

    The other Lawson client on this site had reported:

     "We have deleted the jobdef going to the wrong directory and re-added jobdef using the same name and it still goes to the wrong directory. If we create a job with a new name it goes to the correct directory".

    Does anyone know how this can happen? It seems like the jobstep file csv atribs are being cached/copird/shadowed somehow.

    Second problem:

    We've found that with the apps upgrade to 9.0, csv date formats are now showing as blank (or null) when they have been zeros bfore (00000000 or 00/00/0000". This just recently started happening after a recent 9.0 Env CTP was applied.  Lawson says thon the KB that this is a 9.0 change and ther is no workaround. Anyone else having these problems?

    Any help on these issues would be greatly appreciated.
    Ben Coonfield
    Veteran Member
    Posts: 146
    Veteran Member
    7/3/2009 10:27 AM
      We have seen problem #1 too, and have worked around it although I still don't understand exactly why this is happening. One additional symptom that seems to be directly related are job failures with "Bad File Status 9 009". This symptom started occurring when we removed the old productline directory, which also contains the old work directory. Presumably when a job tried to read or write a work file in the wrong directory, which no longer exists, it failed with the Bad File Status. Before the old work directory was deleted the job would probably succeed.

      In retrospect, I wish we had waited another month before deleting the old productline directory.

      When the problem occurs, we have been deleting the job, running jobinteg, and adding it back again. I don't know if jobinteg helped any but it was recommended by support.

      It seems that there may be some relationship between this issue and old print files still in the system from before the upgrade. The last thing we did was to run deljobhst to remove print files and other references to jobs run prior to the upgrade. I haven't heard of any recurrences of this problem since we did that.
      Jimmy Chiu
      Veteran Member
      Posts: 641
      Veteran Member
      7/3/2009 1:07 PM
        what programs are doing this?