From: webERP D. <web...@li...> - 2013-07-08 04:41:37
|
*Dear all:* I've received a question about the shipments from webERP Chinese community: It's from scripts SuppCreditGRN.php. Following is the error message: Unfortunately the shipment that this purchase order line item was allocated to has been closed - if you add this item to the transaction then no shipments will not be updated. If you wish to allocate the order line item to a different shipment the order must be modified first I think it should be 'no shipments will be updated' instead of 'no shipments will not be updated'. And it seems that we should create another shipment instead of modifying the order. Any comments is highly appreciated! Thanks and best regards! Exson -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/shipments-error-message-clarify-tp4656574.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |
From: webERP D. <web...@li...> - 2013-07-08 04:55:48
|
Dear all: Since this shipments maybe closed and the scripts function is to issue a credit not. Is it a bug? Thanks and best regards! Exson -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/shipments-error-message-clarify-tp4656574p4656575.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |
From: webERP D. <web...@li...> - 2013-07-08 04:57:46
|
Yes you are correct - the message looks as though a "not" has crept in unnecessarily - the user is trying to allocate an order line to a closed shipment - a new shipment is required as you say. Would be better if this was just not possible. Phil Ph: +64 (0)275 567890 Skype: daintree http://www.logicworks.co.nz On 08 July 2013 at 16:41 webERP Developers <web...@li...> wrote: > *Dear all:* > > I've received a question about the shipments from webERP Chinese > community: It's from scripts SuppCreditGRN.php. Following is the error > message: > > Unfortunately the shipment that this purchase order line item was > allocated to has been closed - if you add this item to the transaction then > no shipments will not be updated. If you wish to allocate the order line > item to a different shipment the order must be modified first > > I think it should be 'no shipments will be updated' instead of 'no > shipments will not be updated'. And it seems that we should create another > shipment instead of modifying the order. > > Any comments is highly appreciated! > > Thanks and best regards! > > Exson > |
From: webERP D. <web...@li...> - 2013-07-08 05:29:10
|
*Hi, Phil: * Thank you for your prompt reply. It seems that the logic is not right here. If we credit the supplier, the shipments records should also be revised to reflect the new situation even the shipment has been closed. Thanks and best regards! Exson -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/shipments-error-message-clarify-tp4656574p4656577.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |
From: webERP D. <web...@li...> - 2013-07-08 05:41:18
|
Well the stock could well have all long gone - and it would not be appropriate to revalue current stock if the credit relates to a shipment where most of the stock which has long since been consumed. However, is some situations you may wish to recalculate the shipment costs for the remaining stock items... happy if you want to code it as an option. Phil On 08 July 2013 at 17:28 webERP Developers <web...@li...> wrote: > *Hi, Phil: > * > Thank you for your prompt reply. > > It seems that the logic is not right here. If we credit the > supplier, the shipments records should also be revised to reflect the new > situation even the shipment has been closed. > > Thanks and best regards! > > Exson > > > > -- > View this message in context: > http://weberp-accounting.1478800.n4.nabble.com/shipments-error-message-clarify-tp4656574p4656577.html > Sent from the web-ERP-developers mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers Phil Ph: +64 (0)275 567890 Skype: daintree http://www.logicworks.co.nz |
From: webERP D. <web...@li...> - 2013-07-08 06:02:02
|
*Hi, Phil:* Thank you very much! I'd like to code it but I'm not familiar with the business logic. Would you like to explain a little about it? Then I'll find some time to complete it. Best regards! Exson -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/shipments-error-message-clarify-tp4656574p4656579.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |
From: webERP D. <web...@li...> - 2013-07-08 09:23:07
|
It was many years ago I wrote this logic and I am old :-( Sorry I just can't remember Exson. Phil Phil Daintree Logic Works Ltd - +64 (0)275 567890 http://www.logicworks.co.nz skype:daintree On 08/07/13 18:01, webERP Developers wrote: > *Hi, Phil:* > > Thank you very much! > > I'd like to code it but I'm not familiar with the business logic. > Would you like to explain a little about it? Then I'll find some time to > complete it. > > Best regards! > > Exson > > > > -- > View this message in context: http://weberp-accounting.1478800.n4.nabble.com/shipments-error-message-clarify-tp4656574p4656579.html > Sent from the web-ERP-developers mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > |