RE: Vendor Scheduing and Service Pack 3

["Muir, Betsy" <BMuir@xxxxxxxxxx>]

The source code we received for SP3 has additional changes - they have
created a new logical that using GRN # instead of date (PMP0912L) - PTF
VSV3-0294

        -----Original Message-----
        From:   Jeff_Klipa/Harvard@harvardind.com
[SMTP:Jeff_Klipa/Harvard@harvardind.com]
        Sent:   Friday, November 03, 2000 11:22 AM
        To:     JBAUSERS-L@midrange.com
        Subject:        RE: Vendor Scheduing and Service Pack 3

        As for item 2 (last receipt date is blank) we have found and fixed
this
        problem internally and also reported it to JBA...  Believe it or not
this
        was a Y2K BUG...!!!   ;)

        It does appear that this problem was actually fixed in PTF
P#VSC20002
        (Object) P#VSS20002 (Source) - Service Pack 3.

        Program VS310 - Mod mark - VSV3_0207   KCX 25/02/98 Wrong last
receipt
        information

        If you do not have this PTF or this Mod mark then the following
might apply
        to you...

        If you compare the last receipt date printed on the Schedule with
the
        actual records shown in the PMP09 file you will see that the Century
digit
        is ignored in the calc spec of the VS310 Program when the last
receipt date
        is calculated...  I gave them the exact lines of code where the DATE
        WORK Fields are clearly defined as 6^0 long instead of 7^0 long...
        There is a Y2K bug in the Print Vendor Schedules program VS310...
        This is in standard product for 3.5.1 and 3.5.2B...!!!
        This is the code directly from the OSLVSS3/QRPGSRC source file...

        VS310
        0633.00      C          MOVE *ZEROS    RCDCMP  60 *VSV3_0119 960527
        0634.00      C          MOVE *ZEROS    RCDSV1  60 *VSV3_0119 960527
        0635.00      C          MOVE *ZEROS    RCDSV2  60 *VSV3_0119 960527
        These date work fields are only 6^0 long so the century digit is
being
        lost...
        The fix is simple enough...  just make them 7^0 long and problem
solved...

        However, as we see in their fix in the PTF mentioned above under mod
mark:
        VSV3_0207   KCX 25/02/98 Wrong last receipt information
        Their fix took a far more comprehensive revision to the logic
involved in
        calculating the last receipt information...

        Good luck...






        "Muir, Betsy" <BMuir@newcor.com> on 11/03/2000 10:01:23 AM

        Please respond to JBAUSERS-L@midrange.com
                                                                      
                                                                      
                                                                      
         To:      "'JBAUSERS-L@midrange.com'"                         
                  <JBAUSERS-L@midrange.com>                           
                                                                      
         cc:      (bcc: Jeff Klipa/Harvard)                           
                                                                      
                                                                      
                                                                      
         Subject: RE: Vendor Scheduing and Service Pack 3             
                                                                      






        Hi Michele:
        Here are the problems we are having.  They are significant enough
for us to
        cancel install of SP3 that was scheduled for 11/11.  Our main reason
for
        the
        install is that we are working on a project to "put" our vendor
schedules
        out on a web site for our suppliers (target date for pilot - mid
November)
        and want to make sure we had the latest release of VS in place.
        1.   Vendor schedule detail records created from MRP with status
code 40
        (quantity change) no longer have the purchase order on them (file
VSP45).
        If they are in the firm order range, they are adding the quantity on
to the
        existing purchase order when processed.  The part number we were
testing
        should have 40,000 due on 11/20 but after running vendor scheduling
8 times
        on the item, the purchase order is showing 320,000 due.
        2.   The last receipt date on the vendor schedule print is blank for
all
        300+ items that we vendor schedule. (This was reported to JBA.)
        3.   The cumulative quantity printing on the vendor schedule has a
bug.
        The arrears quantity on an item is causing the cumulative quantity
on the
        next item to be increased by the arrears quantity from the prior
item.
        (This was reported to JBA.)
        I don't think many companies are using vendor scheduling.  There are
no VS
        fixes in the UK fix pack or the US fix pack that we applied to SP3 -
this
        leads me to believe that it hasn't been fully checked/tested in the
install
        base.
        Betsy


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