Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0009052 | Openbravo ERP | 06. Material requirement planning (MRP) | public | 2009-05-15 16:46 | 2009-07-21 00:00 |
|
Reporter | mtaal | |
Assigned To | rafaroda | |
Priority | urgent | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | duplicate | |
Platform | | OS | 5 | OS Version | |
Product Version | pi | |
Target Version | pi | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0009052: MRP: Default value in database and application dictionary differ, they need to be the same |
Description | See the following remarks:
Column MaterialMgmtShipmentInOutLine.Movement Quantity: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column MaterialMgmtInternalMovementLine.Movement Quantity: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column ProductBOM.BOM Quantity: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
|
Steps To Reproduce | |
Proposed Solution | |
Additional Information | |
Tags | 250mp2 |
Relationships | duplicate of | feature request | 0009968 | | new | iciordia | Support default values in AD fields | blocks | defect | 0008900 | pi | closed | mtaal | Inconsistencies between database default values and application dictionary default values |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2009-05-15 16:46 | mtaal | New Issue | |
2009-05-15 16:46 | mtaal | Assigned To | => rafaroda |
2009-05-15 16:46 | mtaal | Regression testing | => No |
2009-05-15 16:53 | mtaal | Relationship added | related to 0008900 |
2009-05-15 16:55 | mtaal | Relationship replaced | blocks 0008900 |
2009-05-15 16:57 | mtaal | Tag Attached: 250mp2 | |
2009-05-15 16:57 | mtaal | Priority | normal => urgent |
2009-05-15 18:05 | rafaroda | Status | new => scheduled |
2009-05-15 18:06 | rafaroda | Assigned To | rafaroda => mtaal |
2009-05-15 19:08 | mtaal | Note Added: 0016396 | |
2009-05-15 19:08 | mtaal | Assigned To | mtaal => rafaroda |
2009-07-17 06:44 | harikrishnan | Note Added: 0018340 | |
2009-07-20 16:11 | rafaroda | Relationship added | duplicate of 0009968 |
2009-07-20 16:11 | rafaroda | Status | scheduled => closed |
2009-07-20 16:11 | rafaroda | Note Added: 0018427 | |
2009-07-20 16:11 | rafaroda | Duplicate ID | 0 => 9968 |
2009-07-20 16:11 | rafaroda | Resolution | open => duplicate |
2009-07-21 00:00 | anonymous | sf_bug_id | 0 => 2824522 |
2016-01-04 18:14 | shuehner | Relationship added | blocks 0031817 |
Notes |
|
(0016396)
|
mtaal
|
2009-05-15 19:08
|
|
Hi Rafa,
I can't really say anything about the default values for data in the MRP tables. Someone knowledgeable on MaterialRequirementsPlanning should take on this one imo.
gr. Martin |
|
|
|
Discussion for "MaterialMgmtShipmentInOutLine.Movement Quantity":
Their is no Inconsistency in table structure and value in the DB column definitions.
only in the structure src-db/database/model/tables/M_INOUTLINE.xml the set default value for this field is '0' in xml as well in the DB.
<column name="MOVEMENTQTY" primaryKey="false" required="true" type="DECIMAL" autoIncrement="false">
<default><![CDATA[0]]></default>
<onCreateDefault/>
</column>
We should not confuse the column properties in the ad_column (its not about structure...its about data)
In the src-db/database/sourcedata/AD_Column the default value is "1"
<AD_COLUMN>
<!--3540--> <AD_COLUMN_ID><![CDATA[3540]]></AD_COLUMN_ID>
<!--3540--> <AD_CLIENT_ID><![CDATA[0]]></AD_CLIENT_ID>
<!--3540--> <AD_ORG_ID><![CDATA[0]]></AD_ORG_ID>
<!--3540--> <ISACTIVE><![CDATA[Y]]></ISACTIVE>
<!--3540--> <NAME><![CDATA[Movement Quantity]]></NAME>
<!--3540--> <DESCRIPTION><![CDATA[The number of items being moved from one location to another.]]></DESCRIPTION>
<!--3540--> <HELP><![CDATA[The Movement Quantity indicates the quantity of a product that has been moved.]]></HELP>
<!--3540--> <COLUMNNAME><![CDATA[MovementQty]]></COLUMNNAME>
<!--3540--> <AD_TABLE_ID><![CDATA[320]]></AD_TABLE_ID>
<!--3540--> <AD_REFERENCE_ID><![CDATA[29]]></AD_REFERENCE_ID>
<!--3540--> <FIELDLENGTH><![CDATA[10]]></FIELDLENGTH>
<!--3540--> <DEFAULTVALUE><![CDATA[1]]></DEFAULTVALUE>
we do agree the default value is 1 here. as far my concern it seems ok.
If you want default 1 in the DB, we have to fix it in the structure(src-db/database/model/tables/M_INOUTLINE.xml)
Thanks
hari |
|
|
|
This issue will be addressed by feature request 0009968 |
|