|
Yeah, thanks we had already done precisely what you suggested to determine how to reverse the mess... Further investigation shows that MK200 (F18) provides a subfile for entering Held WIP and you can enter pages of records if you desire... But at V3.5.1 the background processor could only handle 4 transactions per tran #... Doh...!!! Our V3.5.2 SP4 World shows us that indeed the problem was recognized and fixed in the higher version... The added a multiple occurrence data structure with a size of 100 at first and later bumped that up to 1000... So it appears in V3.5.2 you can process 1000 records per tran #... Seems a bit extreme but OK... Thanks... G'Day... "Michael Berman" <berman@pacific.net.au> on 07/11/2002 09:04:44 AM Please respond to jbausers-l@midrange.com To: "JBA Users" <jbausers-l@midrange.com> cc: (bcc: Jeff Klipa/Harvard) Subject FW: SYS21 - Held WIP AFI Extract Problem... : (M1) Jeff, Sounds very nasty. At least you can use the duplicate FIP45 records to identify the duplicate Inventory records (INP95/6+?) and fix your Inventory valuation. Good luck finding out what the '71' records are all about. Regards Michael -----Original Message----- From: jbausers-l-admin@midrange.com [mailto:jbausers-l-admin@midrange.com]On Behalf Of Jeff_Klipa/Harvard@harvardind.com Sent: Thursday, 11 July 2002 12:44 AM To: jbausers-l@midrange.com Subject: SYS21 - Held Wip AFI Extract Problem... (M1) Has anyone out there had any experience with the GL Update Flag not being updated in PCP56 when you have more than 2 Held Wip transactions for a particular TRAN # in PCP04...? Our AFI Extract FIPCEXTRACT suddenly quit working recently and we traced it back to some transactions entered from Item Booking where the user pressed F18 to Enter Held Wip Details... The pattern we found indicated that if there were more than 2 Tran Type '71' Held Wip associated with the Tran # then the GL Update Flag in PCP56 would not be updated properly for some of the '71' transactions... This meant that these records would get included in the AFI Extract every time it ran... Populating FIP45 with duplicate transaction #'s every time. Obviously this created a mess in our Inventory valuations and eventually the AFI Extract started failing for some as-yet-undiscovered reason... So this is a huge problem... As a work around we have instructed the data entry people to manually add up the Held Wip Tickets and only enter 1 ticket with the total Held Wip for that Tran #... This seems to have resolved the problem but we're wondering if anyone else had seen this yet... We are still at V3.5.1 so it is highly possible it has been fixed in a more recent version of the code... Any feedback would be appreciated... Thanks, Jeff Klipa Mgr. System Applications & Development Harvard Industries, Inc. jaklipa@harvardind.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/cgi-bin/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/cgi-bin/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.
As an Amazon Associate we earn from qualifying purchases.
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.