RE: [SYS21] Material Requirement Schedules (Vendor Scheduling)

This sounds to me like a get out not a fix, we had a mod made so that the
order lines are checked at the start of a VS run and any lines added without
the VS contract to get stamped with the correct contract number (another
workround) but at least this way any extra lines show on the VS schedule.

-----Original Message-----
From: Gonyer, Kris-Coining [mailto:gonyer@tmdinc.com]
Sent: Thursday, February 06, 2003 9:38 PM
To: 'GEAC/JBA System 21 Users'
Subject: RE: [SYS21] Material Requirement Schedules (Vendor Scheduling)


Yes, I forgot about that.  Schedules pending release can cause an error
message which prohibits order amendment.  There are scenarios I've seen
where schedules pending release do not generate an error message to prevent
an order amendment.  Also, amendments are not prohibited prior to vendor
sourcing or after auto-release.

Kris Gonyer
Toledo Molding & Die, Inc.

-----Original Message-----
From: mslayton@ambrake.com [mailto: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 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.


***************************************************************************
Important - Please read
***************************************************************************

The statements and opinions expressed in this message are those of the author 
and do not necessarily reflect those of the company.

The information contained in this e-mail is confidential. It may also be legally
priveleged. It is intended only for the stated addressee(s) and access to it by
any other person is unauthorised. If you are not an addressee, you must not
disclose, copy, circulate or in any way use or rely on the information contained
in this e-mail. Such unauthorised use may be unlawful. If you have received this
e-mail in error, please inform us immediately at administrator@pattonair.com
and delete it and all copies from your system.

All inbound and outbound e-mails and any attachments are monitored and 
scanned by virus/ content checking software. While showing due care we 
accept no liability, so scan all attachments.