RE: The AR Company Maintenance program SL005 is terminating abnor mally.

Jeff, we have also moved to 3.5.2B SP3 about 2 weeks ago and the only
difference to what Steve said is both our live and test environments have
these records in FLP060.


Randy Stratton
Director IS
Alsons Corporation
517-439-1411

 -----Original Message-----
From:   Prill, Steve [mailto:sprill@rexairinc.com] 
Sent:   Monday, December 18, 2000 7:17 AM
To:     JBAUSERS-L@midrange.com
Subject:        RE: The AR Company Maintenance program SL005 is terminating
abnor mally.

Jeff,

Did you check the PTF source?  There may be something hard coded.  We moved
to 3.5.2B SP3 two weeks ago.  I do not have the FLP060 records that you
mention in my test environment but they are in my live environment which
leads me to believe that there is a PTF issue.

We would not have come across this in our testing because we only use the SL
app. for the customer master which is heavily modified.

Steve

-----Original Message-----
From: Jeff_Klipa/Harvard@harvardind.com
[mailto:Jeff_Klipa/Harvard@harvardind.com]
Sent: Thursday, December 14, 2000 9:56 AM
To: JBAUSERS-L@midrange.com
Subject: The AR Company Maintenance program SL005 is terminating
abnormally.


We are pretesting 3.5.2B SP3 with UK Fix Pack and Americas Solution Pack.
This program was included in PTF P#SLV30127...   Menu option 2/ASCO...
Accounts Receivable Company Maintenance

It appears that we are missing parameter types SRC1 and SCR2 in the General
Ledger parameter file FLP060. These parameters are associated with new
functionality for ALPHA SEARCH DETAILS.

The uplift for this program added a third screen to define ALPHA SEARCH
DETAILS. The subfile display is built from/using the parameter file FLP060
looking for particular parameter types where PMTP60 = SCR1 and/or SCR2. We
do not have these records in our file. As a result we get an empty subfile
display.  After hitting enter on the thrid screen the program attempts to
read changed records from the empty subfile causing the program to
terminate abnormally.  I have identified the subroutine ASRHDL as the logic
that presents this problem.

We are wondering why these records are missing from the parameters file...
Were they supposed to be installed when the PTF was applied or is there a
M.O.P. or an Alert that we missed somewhere...

Has anyone else experienced this problem...?

Thanks.


+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---