Allowing manual entry from Attributes tab on shipment/MR line
Description
Environment
Attachments
- 28 Jun 2014, 10:50 AM
- 11 Jun 2014, 04:09 PM
blocks
relates to
Activity
Carlos Ruiz April 19, 2016 at 2:59 AM
Thanks @Bayu Cahya, I didn't understand what was the issue you were reporting.
But searching for returnedQty in Eclipse brought it.
I opened ticket https://idempiere.atlassian.net/browse/IDEMPIERE-3078#icft=IDEMPIERE-3078 to trace it. Maybe @Deepak Pansheriya can tell us about that non-existing column.
Bayu Cahya February 24, 2016 at 2:37 AM
Hi,
I have checked the test.idempiere.com, and returnedQty column did not exist yet in M_InOutLineMA table definition.
More over, these migration script in i2.0z, postgresql
201407010830_IDEMPIERE-1770.sql
201407010831_IDEMPIERE-1770.sql
201407010832_IDEMPIERE-1770.sql
Did not contains returnedQty.
Is there any further info to clarify about the existence of this column?
Thanks
Carlos Ruiz February 23, 2016 at 4:34 PM
Thanks @Bayu Cahya, refreshed the test site - now must be working again.
Bayu Cahya February 23, 2016 at 11:56 AM
Hola Carlos Antonio Ruiz Gomez,
There are no roles option available while using Superuser and Client System.
Thanks
Carlos Ruiz February 23, 2016 at 11:13 AM
@Bayu Cahya, try with
superuser @ idempiere.com
Bayu Cahya February 23, 2016 at 8:52 AM
Hi Hiep,
If you mean to access test.idempiere.com, I can not access test.idempiere.com.
Log in using System user, goes to Change Password confirmation, and failed to save with message
Could not save changes: : Fill mandatory fields: EMail Address - MUser[0,Name=null,EMailUserID=null]
Hiep Lq February 23, 2016 at 8:40 AM
i see this's closed ticket. so, i think every patch is already merged to core.
try check column returnedQty is already have in demo?
Currently if ship or recieving product with instance ASI (for example serial), have to create multiple shipment or MR lines. This some time hard for user to review document or handling at print format.
Proposing this enhancement.
1. Do not use ASI field on document line
2. Use Attribute tab to populate ASI while locator information can be populated or kept blank.
3. When completing document, if attributes record are presence then those are respected and locator information is updated as needed based on in or out transaction.
4. If ASI are mandatory and not to be auto generated, system throws error when qty and ASI records do not match
5. If ASI are mandatory and can be auto generaed, system respect user entered ASI and generate record for missing ASI.
Please advise or have additional points to be considered.
As per discussion with Hengsin- Migration plan
We need to create migration script which populate ASI from Line to LineMA as currently we have same ASI on Line and LineMA.