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