× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We've been waiting for this fix.  However, Vendor Scheduling will not delete
past due purchase order lines (we use 42/pmp with the option 9 - line
completion to accomplish this), with this fix how do you delete purchase
order lines you no longer want if you cannot use 42/pmp?

Does this fix work with prior vendor scheduled purchase orders or only one
P.O. created after you implement the service pac?

> -----Original Message-----
> From: mslayton@ambrake.com [SMTP:mslayton@ambrake.com]
> Sent: Thursday, February 06, 2003 3:26 PM
> To:   GEAC/JBA System 21 Users
> Subject:      RE: [SYS21] Material Requirement Schedules (Vendor
> Scheduling)
> 
> We are at 352 service Pac 4 Solutions Pac 2.4.  Any new PO's will not let 
> you amend it using 42/pmp.  It tells you that VS Contract Item pending 
> release or print  cannot be amended or completed.  You have to do the 
> vendor release on it. 
> 
> 
> 
> 
> Jeff_Klipa/Harvard@harvardind.com 
> Sent by: jbausers-l-bounces@midrange.com
> 02/06/2003 01:59 PM
> Please respond to
> GEAC/JBA System 21 Users <jbausers-l@midrange.com>
> 
> 
> To
> CN=GEAC/O=JBA System 21 Users <jbausers-l@midrange.com>
> cc
> 
> Subject
> RE: [SYS21] Material Requirement Schedules (Vendor Scheduling)
> 
> 
> 
> 
> 
> 
> Excellent point, Kris...
> You should never amend a PO using 42/PMP if the PO was created using 
> Vendor
> Scheduling...
> At least that's the way it used to be in 3.5.1...
> I don't know if they have "fixed" that limitation in the later releases...
> 
> 
> 
> 
> 
> 
> 
> 
> "Gonyer, Kris-Coining" <gonyer@tmdinc.com> on 02/06/2003 12:55:23 PM
> 
> Please respond to "GEAC/JBA System 21 Users" <jbausers-l@midrange.com>
> 
> 
> 
> To:          'GEAC/JBA System 21 Users'
> <jbausers-l@midrange.com>
> 
> cc:          (bcc: Jeff Klipa/Harvard)
> 
> 
> 
> Subject      RE: [SYS21]   Material Requirement Schedules
> :            (Vendor Scheduling)
> 
> 
> 
> 
> 
> 
> 
> We found this problem a few years back.  In our case for the items in
> question, PMP09 records were missing contract numbers.  As a result,
> whenever a purchase receipt was made against such a line, the contract 
> 'cum
> received' was not updated by the receipt amount.  If I remember correctly,
> users were modifying their schedule orders through order amendment 
> (42/PMP)
> which subsequently wrote PMP09 records without contract numbers.
> 
> -----Original Message-----
> From: Brian.True@trelleborg.com [mailto:Brian.True@trelleborg.com]
> Sent: Thursday, February 06, 2003 8:47 AM
> To: jbausers-l@midrange.com
> Subject: [SYS21] Material Requirement Schedules (Vendor Scheduling)
> 
> 
> We are currently running V5R3 and seem to be having intermittent problems 
> of
> the Purchase Receipt qty not reflecting in the total CUM Receipts.  Does 
> not
> seem to be one item or one vendor.  Sort of scattered across all items. We
> have modified PM010, but nothing to do with cums.  We can see the receipt 
> in
> INP95 and everything looks okay.  Was wondering if anybody else was having
> this kind of problem.  Thanks
> 
> Brian True
> Trelleborg Automotive
> brian.true@trelleborg.com
> 
> 
> 
> 
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list To post a
> message email: JBAUSERS-L@midrange.com To subscribe, unsubscribe, or 
> change
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/jbausers-l
> or email: JBAUSERS-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/jbausers-l.
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
> To post a message email: JBAUSERS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/jbausers-l
> or email: JBAUSERS-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/jbausers-l.
> 
> 
> 
> 
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
> To post a message email: JBAUSERS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/jbausers-l
> or email: JBAUSERS-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/jbausers-l.
> 
> _______________________________________________
> This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
> To post a message email: JBAUSERS-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/jbausers-l
> or email: JBAUSERS-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/jbausers-l.
> 
> 
_________________________________________________________________ 
This electronic mail transmission contains confidential information intended
only for the person(s) and/or organization named. Any use, distribution,
copying or disclosure by or to any other person outside your organization is
strictly prohibited. If you received this transmission in error, please send
an electronic mail message to postmaster@pollak.com so we may instruct you
regarding its disposition.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.