RE: Purchase Order Class Code & Vendor Scheduling SP3 bug -- SYSTEM21

After several testing runs we were able to isolate the problem to the VS203
vendor scheduling program (10/VSP).  I've modified the program as follows.
The ITCL03 is 2 alpha and ORDC02 is 1 zoned numeric - it doesn't seem to be
happy to have a MOVEL into it.  This is 3.5.2b SP 2 code.

Columns . . . :    1  71           Browse
OSLVSS3/QRPGSRC 
 SEU==>
VS203 
 FMT C
.....CL0N01N02N03Factor1+++OpcdeFactor2+++ResultLenDHHiLoEqComments++++ 
1997.00      C                     Z-ADDL#IDAT    ORDT02

1997.01 /E   C           ITCL03    IFEQ '1'               
1997.02 /E   C                     Z-ADD1         ORDC02  
1997.03 /E   C                     ENDIF                  
1997.04 /E   C           ITCL03    IFEQ '5'               
1997.05 /E   C                     Z-ADD5         ORDC02  
1997.06 /E   C                     ENDIF                  
1998.00 /E   C*                    MOVELITCL03    ORDC02

1999.00      C** VSV3_U107---------MOVEL*BLANKS
DICD02----------------------- 

Watch for another major SP3 problem with the Schedule Maintenance program
(VS090 - 4/VSM).  There is a major bug if you have status 99 records coming
in from MRP and you maintain the schedule.  SP2 version of VS090 used to
delete the status 99 records (but they are needed to update the purchase
order files in VS203).  SP3 fix doesn't load them to the subfile, but the
update subroutine reads through VSP45 and assumes that all records were
loaded into the subfile.  Here's a simple example of what happens:

Record 1 is status 99 for 0 quantity on 12/4
Record 2 is status 40 for 2000 quantity on 12/11
Record 3 is status 40 for 2000 quantity on 12/18

The subfile will only show records 2 & 3.  If you change the quantity on
record 2 to 3000, the resulting update to VSP45 is:

Record 1 is now status 30 with 3000 quantity 
Record 2 is status 40 for 2000 quantity - no change
Record 3 is status 40 for 2000 quantity

Betsy Muir
Newcor, Inc.


        -----Original Message-----
        From:   Tim Randall [SMTP:TRandall@centura.co.uk]
        Sent:   Friday, November 17, 2000 3:21 AM
        To:     'JBAUSERS-L@midrange.com'
        Subject:        RE: Purchase Order Class Code

        Betsy

        Yes we've had this problem too - The GEAC UK support team in
Mancheater are
        looking at this for us but as yet we've not got an answer or fix - I
will
        let you know when we start making some progress !!

        We're on v3.5.2 sp3

        Tim Randall
        Centura Foods Ltd
          
        -----Original Message-----
        From: Muir, Betsy [mailto:BMuir@newcor.com]
        Sent: 15 November 2000 16:57
        To: 'JBAUSERS-L@midrange.com'
        Subject: Purchase Order Class Code


        This message has been successfully virus checked by the Centura
Foods Mail
        system. 

        Has anyone had a problem with the Order Class Code in the Purchase
Order
        Header getting set to a -1 (1 = stock order, 5 = non-stock, 6 =
service).
        We have a bunch of records where this field is a -1 on orders that
were
        created from vendor scheduling.  I've search through all the
programs in
        vendor scheduling, purchasing, inventory, MPS/MRP and can't find
where this
        is getting updated to the negative number.  The purchase order
extract
        programs in the MRP run (MR019, MR020) only select open purchase
orders
        where the ORDC02 = 1.  This is causing us to buy a bunch of raw
material
        that is already on order but not being extracted during the MRP run.

        Any comments would be appreciated.

        Thanks,
        Betsy Muir
        Newcor, Inc.


        +---
        | 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 email, its content and any files transmitted with it are
confidential
        and intended solely for the use of the individual(s) to whom it is
        addressed.
        If you are not the intended recipient, be advised that you have
received
        this email in error and that any use, dissemination, forwarding,
printing,
        or copying of this email is strictly prohibited.
        This email, its contents and any files transmitted with it have been
        prepared using information believed by the author to be reliable and
        accurate, but Centura Foods Ltd. makes no warranty as to accuracy or
        completeness. In particular Centura Foods Ltd. does not accept
        responsibility for changes made to this email or related files after
it
        was sent. Any opinions expressed in this email and any related
documents
        are those of the author and do not necessarily reflect the opinions
of
        Centura Foods Ltd. or its associated companies.

        If you have received this email in error please notify the Centura
Foods
        Systems HelpDesk by telephone on +44 (0) 1606 830 737.
        
===========================================================================


        +---
        | 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.
+---