|
Al Mac, Excellent points regarding the security aspects of these transactions. I too was able to do an inter-facility Mass Location Transfer using INV510, but that is only because I have full access to all warehouses and all transactions. Your point is especially important for those of us that are doing testing or evaluating new functionality or new transactions sets. Just because we can do a thing (such as the cross facility mass transfer) does not mean that the normal user would have sufficient security clearance to do the same things. Thanks for the reminder. Frederick C. Davy, CPIM, PMP Business Systems Analyst Interface Solution, Inc. Phone: (315) 592-8101 Fax: (315) 592-8481 e-mail: fcdavy@xxxxxxxxxxxx Al Mac <macwheel99@xxxxxxxxxxx> Sent by: bpcs-l-bounces+fcdavy=sealinfo.com@xxxxxxxxxxxx 06/09/2006 10:05 AM Please respond to "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> To "SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> cc Subject Re: [BPCS-L] Document for Transfer finished good inter warehouse There are a number of settings in BPCS which could block mass transfer, such as SECURITY blocking someone access to one of the two warehouses involved. There may be variations by version of BPCS. There might also be modifications that have changed how BPCS functions. There can be different rules placed in transaction effects, such as copy "T" to another new transaction effect so that company policy can be to use one for transfer within a facility and another for cross facility, whether or not you account for time in transit. There can be a periodic report on who is using what transaction type for what purpose, to catch people using them for unauthorized or inappropriate purposes. This is not foolproof, but it catches some of it ... for example, if company has a rule that all inventory adjustments have a good reason, you can do a count and volume by reason given, to see if the reasons seem reasonable.
I wondered about this response - my test shows that we are able to use the mass transfer program to transfer from one facility to another. As the original questioner said, this leaves you with no documentation and won't work for that need. DRP is a better solution, but not the only one. Dick Bailey MCFA -----Original Message----- From: Frederick C Davy Indah, If your warehouses are associated to other facilities, then you can not use the Mass Location Transfer (INV510) to move the inventory. Mass Location Transfer only works for warehouses associated to the same facility (check the warehouse master INV110 to see what facility code the warehouse is assigned to). If you need to transfer to warehouses at a different facility you should use DRP (Distribution Resource Planning). To accomplish this you must create a DRP Relationship for every item/facility/to/from association that you will be using (items must be master scheduled in MRP140 or DRP140 record). The complete setup for DRP is too involved for this e-mail, and to do it properly you should have your own documentation for DRP to follow. First off, you should check the Systems Parameters for Installed Products to make sure you have DRP installed. If you need further help, contact me at my e-mail address below. Good luck. Frederick C. Davy, CPIM, PMP Business Systems Analyst Interface Solution, Inc. Phone: (315) 592-8101 Fax: (315) 592-8481 e-mail: fcdavy@xxxxxxxxxxxx Indah Hi, I am using BPCS v.6.1.02. My company has several warehouse that its location is separate from manufacturing's location. To transfer finished good inter warehouse, user use Mass Location Transfer. Although this program has control output for transaction, but it can be used by user, because the control output doesn't have document number like Sales Order or Purchase Order, and detail information at there isn't enough. Do you have any idea to solve this problem..? thanks .
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.