|
Jeff, Thank you. I haven't fully digested what you said as I haven't had my morning coffee yet. This work order thing can be annoying. Can't wait to see your bill :o) Mon -----Original Message----- From: system21-request@xxxxxxxxxxxx [mailto:system21-request@xxxxxxxxxxxx] Sent: Friday, January 16, 2004 2:01 AM To: system21@xxxxxxxxxxxx Subject: SYSTEM21 Digest, Vol 2, Issue 10 Send SYSTEM21 mailing list submissions to system21@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/system21 or, via email, send a message with subject or body 'help' to system21-request@xxxxxxxxxxxx You can reach the person managing the list at system21-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of SYSTEM21 digest..." Today's Topics: 1. RE: [SYSTEM21] JBA - INVENTORY MANAGEMENT : LOT CONTROL (DAhKow@xxxxxxxxxxxxx) 2. FW: Work Order booking (mon.ferriols@xxxxxxxxxxxxxx) 3. Aurora (anony952@xxxxxxxxxxxx) 4. RE: [SYSTEM21] FW: Work Order booking (Jeff Klipa) 5. RE: [SYSTEM21] FW: Work Order booking (welchj@xxxxxxxx) ---------------------------------------------------------------------- message: 1 date: Thu, 15 Jan 2004 11:56:12 +0400 from: DAhKow@xxxxxxxxxxxxx subject: RE: [SYSTEM21] JBA - INVENTORY MANAGEMENT : LOT CONTROL We are using a software called GOLD from a french / finnish company called Aldata. Web Site : www.gold-solutions.com The software has a version which also runs on Unix/Oracle. Richard_Caldicott@xxxxxxxxxxxxxxx Sent by: system21-bounces@xxxxxxxxxxxx 01/14/04 07:10 PM Please respond to System 21 Users <system21@xxxxxxxxxxxx> To System 21 Users <system21@xxxxxxxxxxxx> cc Subject RE: [SYSTEM21] JBA - INVENTORY MANAGEMENT : LOT CONTROL Just out of interest, which warehouse system have you gone with? Richard DAhKow@xxxxxxxxxxxxx Sent by: system21-bounces+richard_caldicott=tandybrands.com@xxxxxxxxxxxx 01/14/2004 12:46 AM Please respond to System 21 Users To: System 21 Users <system21@xxxxxxxxxxxx> cc: Subject: RE: [SYSTEM21] JBA - INVENTORY MANAGEMENT : LOT CONTROL Jeff, I work with Guy and as he is not in the office this mornig, I'll try to give you some of the why's of this required change. We have using lot control in one of our -numerous- companies. This company is a dealer in pharmaceutical products (drugs, equipment etc...) . In our initial set-up a few years ago, lot control was one of their requirements, to follow-up all those lot/batch numbers and expiry dates. Now we are going to soon implement a warehouse management software (NOT JBA ) for that company. There are obviously some issues there. Purchase and Sales orders will originate from JBA and will be interfaced down to the warehousing software. Similarly Receipts & despatches in the warehouse must be fed back to JBA. If you say that using lot control in JBA is a pain, imagine keeping the two systems at par on a lot basis! Therefore the decision is to track lot numbers & expiry dates only in the warehousing system. Updating to & fro will certainly be a lot easier. Fortunately we haven't any bespoke mods related to lot & batches. And similarly to what you suggested, we were thinking about just clearing INP80 records for that company, set back the lot-control flag to 'N' -all this using SQL statements- while verifying that INP80 & INP60 records were in balance before. We wanted to know therefore whether this was a safe approach and if there was any implications. We will certainly do some tests here, as we do have a test company that we can play with. Doing -ve adjustments to set back qties to zero, change the lot control flag, and doing receipts to reinstate qties, would be difficult to do here due to the large number of items and limited time availaible for that exercise, though this would be the safest route. "Jeff Klipa" <jklipa@xxxxxxxxxxx> Sent by: system21-bounces@xxxxxxxxxxxx 01/13/04 05:53 PM Please respond to System 21 Users <system21@xxxxxxxxxxxx> To system21@xxxxxxxxxxxx cc Subject RE: [SYSTEM21] JBA - INVENTORY MANAGEMENT : LOT CONTROL Guy, First, let me say that you'll be happier using 'N' instead of 'L' or 'B'... Using Lot Control within JBA is certainly more challenging for the people reporting the inventory movements. I would always recommend NOT using Lot Control if you don't absolutely have to. That being said, it should be far less painless to go from Lot Control "ON" to Lot Control "OFF"...!!! Second, I cannot give you the "full implications" of this change... I strongly suggest that you contact your GEAC support team if you have a current maintenance contract. I'll tell you what I think I know. Any bespoke (custom) code you have in place should be reviewed to determine if there will be any impact there. Also, if you are doing any bar code scanning there may be an impact there as well. If you have a test environment you should definitely take full advantage of it in this case... Alternatively, you could nominate and change a few "test" parts at a time to see what impact this will have on the data flow and on the people in the operation... You have the luxury of making this switch gradually if you so choose. You don't have to change all the parts at once but you could. The file that holds the lot balances, INP80, will need to be dealt with for sure. You will want to remove the record from INP80 for all parts where you change lot control flag to "N"... You must be sure that the integrity of the stockroom balance in INP60 is preserved. I am not sure if there are any other database considerations so I welcome any other comments... Once the database changes are made your reporting of all inventory movements becomes much easier... Just out of curiosity, what kind of commodity do you manufacture...? Furthermore, why would you have been using lot control in the past and suddenly not need to any more? Good luck. ----Original Message Follows---- From: GGenevieve@xxxxxxxxxxxxx Reply-To: System 21 Users <system21@xxxxxxxxxxxx> To: jbausers-l@xxxxxxxxxxxx Subject: [SYSTEM21] JBA - INVENTORY MANAGEMENT : LOT CONTROL Date: Tue, 13 Jan 2004 16:23:06 +0400 Hello All We have been using Lot Control 'L' & Batch control 'B'. We now want to change back to 'N'. Can anyone tell if this is possible & what are the full implications? Regards, Guy Alain _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. _________________________________________________________________ Rethink your business approach for the new year with the helpful tips here. http://special.msn.com/bcentral/prep04.armx _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. _______________________________________________ This is the System 21 Users (SYSTEM21) mailing list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. ------------------------------ message: 2 date: Thu, 15 Jan 2004 16:39:47 +0800 from: mon.ferriols@xxxxxxxxxxxxxx subject: [SYSTEM21] FW: Work Order booking > -----Original Message----- > From: mon.ferriols@xxxxxxxxxxxxxx > Sent: Thursday, January 15, 2004 4:10 PM > To: System21-Request (E-mail) > Subject: Work Order booking > > Guys, > > Am new to Work Order bookings, please help. We used 12/PCM to book a work > order and got an error message "lot number does not exist at previous > countpoint". What causes this and how would one go about correcting it? > Thanks in advance. > > Mon Ferriols > Data Management & Control > Ionics EMS, Inc. - Plant7 > * (49) 545-9751 > * mon.ferriols@xxxxxxxxxxxxxx > * www.ionicsgroup.com > > "ERP is not just computers and software, but PEOPLE, PROCESSES and > FUNCTIONS." > ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ------------------------------ message: 3 date: Thu, 15 Jan 2004 05:51:17 -0500 from: anony952@xxxxxxxxxxxx subject: [SYSTEM21] Aurora Hi Does anyone know if there is a way to take system21 user profiles into aurora without having to create new users? __________________________________________________________________ New! Unlimited Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Act now to get a personalized email address! Netscape. Just the Net You Need. ------------------------------ message: 4 date: Thu, 15 Jan 2004 14:21:30 +0000 from: "Jeff Klipa" <jklipa@xxxxxxxxxxx> subject: RE: [SYSTEM21] FW: Work Order booking Mon, SELMSG STRING('Lot number does') MSGF(OSLD3/MSMSGF) Select/Display Message Utility Message File . . OSLD3/MSMSGF String . . LOT NUMBER DOES Message File Text . . Manufacturing Message file Msg ID Sev Msg (Abbreviated) UMJ0216 0 Lot number does not exist at previous countpoint The error message is UMJ0216 as shown above... I don't think this error message could be any more misleading or erroneous. The following comments are based on V3.5.1 code. It is used in Display File MG200FT conditioned by indicator 27. Work order/Operator Booking It is used in Display File MG240FT conditioned by indicator 24. Subcontractor Receipts Entry It is used in Display File MK240FT conditioned by indicator 69. Item/Operator Booking Let's focus on MK200 since you're booking Work Orders... The file is PCP30 (Production Activity Control) and there is a field in that file that must be marked with a specific flag or it will trigger indicator 27 on and cause the error... IMVI30 1 A Inventory Movement Indicator This error is issued only when F17 is pressed and the following condition is true:... In the following code segment if you press F17 and IMVI30 <> '1' then you get the error. 0954.00 * 0955.00 * Must be an Inventory Movement Activity Code. 0956.00 * 0957.00 B03 C IMVI30 IFNE '1' 0958.00 B04 C *INKQ IFEQ *ON 0959.00 C MOVE *ON *IN27 Those are the raw facts... Assuming your code is similar to V3.5.1... What it really means is that the ACTIVITY code you're using to book this movement is not an Inventory Movement Activity Code... Choose a different code... Or if you are dead set on using whatever code you're trying to use you could change the PCP30 Master file flag to a '1'... You can do that using 26/MDU Maintain Activity Control MJ010 01 - Your Company User JKLIPA 1/15/04 9:15:56 Production Activity Control Maintenance Activity Type....? SCRAP Scrap at Operation Reporting Type...? 34 SCRAP AT AN OPERATION Display Sequence.... 134 Activity Indicators Report Type Ind. Employee No......... 3 Optional 3 Employee Hours...... 3 Optional 3 Item No............. 1 Mandatory 1 Operation........... 1 Mandatory 1 Work Station........ 3 Optional 3 Work Station Hours.. 3 Optional 3 Department.......... 3 Optional 3 Quantities.......... 1 Mandatory 1 Shift............... 3 Optional 3 Work Order.......... 3 Optional 3 Inventory Movement.. 1 <<<<<<<--------Here's the flag... Efficiency.......... 1 I'll send you my bill... Thanks. ----Original Message Follows---- From: mon.ferriols@xxxxxxxxxxxxxx Reply-To: System 21 Users <system21@xxxxxxxxxxxx> To: "System21 (E-mail)" <system21@xxxxxxxxxxxx> Subject: [SYSTEM21] FW: Work Order booking Date: Thu, 15 Jan 2004 16:39:47 +0800 > -----Original Message----- > From: mon.ferriols@xxxxxxxxxxxxxx > Sent: Thursday, January 15, 2004 4:10 PM > To: System21-Request (E-mail) > Subject: Work Order booking > > Guys, > > Am new to Work Order bookings, please help. We used 12/PCM to book a work > order and got an error message "lot number does not exist at previous > countpoint". What causes this and how would one go about correcting it? > Thanks in advance. > > Mon Ferriols > Data Management & Control > Ionics EMS, Inc. - Plant7 > * (49) 545-9751 > * mon.ferriols@xxxxxxxxxxxxxx > * www.ionicsgroup.com > > "ERP is not just computers and software, but PEOPLE, PROCESSES and > FUNCTIONS." > ########################################### _________________________________________________________________ Rethink your business approach for the new year with the helpful tips here. http://special.msn.com/bcentral/prep04.armx ------------------------------ message: 5 date: Thu, 15 Jan 2004 09:21:38 -0600 (CST) from: welchj@xxxxxxxx subject: RE: [SYSTEM21] FW: Work Order booking On many systems the library in the command would be... SELMSG STRING('Lot number does') MSGF(OSLPDD3/MSMSGF) Jack _______________________________________________ > Mon, > > SELMSG STRING('Lot number does') MSGF(OSLD3/MSMSGF) > Select/Display Message Utility > > Message File . . OSLD3/MSMSGF String . . LOT NUMBER DOES > Message File Text . . Manufacturing Message file > Msg ID Sev Msg (Abbreviated) > UMJ0216 0 Lot number does not exist at previous countpoint > > The error message is UMJ0216 as shown above... > I don't think this error message could be any more misleading or > erroneous. > > The following comments are based on V3.5.1 code. > > It is used in Display File MG200FT conditioned by indicator 27. Work > order/Operator Booking > It is used in Display File MG240FT conditioned by indicator 24. > Subcontractor Receipts Entry > It is used in Display File MK240FT conditioned by indicator 69. > Item/Operator Booking > > Let's focus on MK200 since you're booking Work Orders... > > The file is PCP30 (Production Activity Control) and there is a field in > that > file that must be marked with a specific flag or it will trigger indicator > 27 on and cause the error... > IMVI30 1 A Inventory Movement Indicator > > This error is issued only when F17 is pressed and the following condition > is > true:... > In the following code segment if you press F17 and IMVI30 <> '1' then you > get the error. > 0954.00 * > 0955.00 * Must be an Inventory Movement Activity Code. > 0956.00 * > 0957.00 B03 C IMVI30 IFNE '1' > 0958.00 B04 C *INKQ IFEQ *ON > 0959.00 C MOVE *ON *IN27 > > > Those are the raw facts... Assuming your code is similar to V3.5.1... > > What it really means is that the ACTIVITY code you're using to book this > movement is not an Inventory Movement Activity Code... Choose a different > code... > > Or if you are dead set on using whatever code you're trying to use you > could > change the PCP30 Master file flag to a '1'... You can do that using > 26/MDU > Maintain Activity Control > > MJ010 01 - Your Company User JKLIPA > 1/15/04 > > 9:15:56 > Production Activity Control Maintenance > > Activity Type....? SCRAP Scrap at Operation > Reporting Type...? 34 SCRAP AT AN OPERATION > > Display Sequence.... 134 > Activity Indicators Report Type Ind. > Employee No......... 3 Optional 3 > Employee Hours...... 3 Optional 3 > Item No............. 1 Mandatory 1 > Operation........... 1 Mandatory 1 > Work Station........ 3 Optional 3 > Work Station Hours.. 3 Optional 3 > Department.......... 3 Optional 3 > Quantities.......... 1 Mandatory 1 > Shift............... 3 Optional 3 > Work Order.......... 3 Optional 3 > Inventory Movement.. 1 <<<<<<<--------Here's the flag... > Efficiency.......... 1 > > I'll send you my bill... > > Thanks. > > > > > > ----Original Message Follows---- > From: mon.ferriols@xxxxxxxxxxxxxx > Reply-To: System 21 Users <system21@xxxxxxxxxxxx> > To: "System21 (E-mail)" <system21@xxxxxxxxxxxx> > Subject: [SYSTEM21] FW: Work Order booking > Date: Thu, 15 Jan 2004 16:39:47 +0800 > > > > > -----Original Message----- > > From: mon.ferriols@xxxxxxxxxxxxxx > > Sent: Thursday, January 15, 2004 4:10 PM > > To: System21-Request (E-mail) > > Subject: Work Order booking > > > > Guys, > > > > Am new to Work Order bookings, please help. We used 12/PCM to book a > work > > order and got an error message "lot number does not exist at previous > > countpoint". What causes this and how would one go about correcting it? > > Thanks in advance. > > > > Mon Ferriols > > Data Management & Control > > Ionics EMS, Inc. - Plant7 > > * (49) 545-9751 > > * mon.ferriols@xxxxxxxxxxxxxx > > * www.ionicsgroup.com > > > > "ERP is not just computers and software, but PEOPLE, PROCESSES and > > FUNCTIONS." > > > ########################################### > > _________________________________________________________________ > Rethink your business approach for the new year with the helpful tips > here. > http://special.msn.com/bcentral/prep04.armx > > _______________________________________________ > This is the System 21 Users (SYSTEM21) mailing list > To post a message email: SYSTEM21@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/system21 > or email: SYSTEM21-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/system21. > > ------------------------------ _______________________________________________ This is the System 21 Users (SYSTEM21) digest list To post a message email: SYSTEM21@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/system21 or email: SYSTEM21-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/system21. End of SYSTEM21 Digest, Vol 2, Issue 10 *************************************** ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/
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.