diff --git a/db/ddlutils/data/AD_COLUMN.xml b/db/ddlutils/data/AD_COLUMN.xml index d0149870a2..5f67a3726f 100644 --- a/db/ddlutils/data/AD_COLUMN.xml +++ b/db/ddlutils/data/AD_COLUMN.xml @@ -217,8 +217,8 @@ There are two reasons for de-activating and not deleting records: - - + + @@ -260,7 +260,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -660,7 +660,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -1303,7 +1303,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -1831,7 +1831,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -4279,7 +4279,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -4558,7 +4558,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -5152,7 +5152,7 @@ There are two reasons for de-activating and not deleting records: If you leave the search key empty, the system automatically creates a numeric number. The document sequence used for this fallback number is defined in the "Maintain Sequence" window with the name "DocumentNo_", where TableName is the actual name of the table (e.g. C_Order).]]> - + @@ -5269,7 +5269,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -5924,7 +5924,7 @@ If the document type of your document has no automatic document sequence defined - + @@ -6468,7 +6468,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -6621,7 +6621,7 @@ If the document type of your document has no automatic document sequence defined - + @@ -7123,7 +7123,7 @@ If you leave the search key empty, the system automatically creates a numeric nu - + @@ -7140,7 +7140,7 @@ If you leave the search key empty, the system automatically creates a numeric nu - + - + @@ -7534,7 +7534,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -8127,7 +8127,7 @@ There are two reasons for de-activating and not deleting records: (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -8244,7 +8244,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -8277,7 +8277,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -8421,7 +8421,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -8499,7 +8499,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -8683,7 +8683,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -9108,7 +9108,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -9395,7 +9395,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -9500,7 +9500,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -9931,7 +9931,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -9963,7 +9963,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -10044,7 +10044,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -10082,7 +10082,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -10912,10 +10912,10 @@ Examples:
@Name@>J
Strings may be in single quotes (optional)]]>
- + - + - + @@ -11315,7 +11315,7 @@ If the document type of your document has no automatic document sequence defined - + @@ -11981,7 +11981,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -12157,7 +12157,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -12489,8 +12489,8 @@ There are two reasons for de-activating and not deleting records: - - + + @@ -12576,7 +12576,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -13101,7 +13101,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -13413,7 +13413,7 @@ There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -13481,7 +13481,7 @@ If you leave the search key empty, the system automatically creates a numeric nu - + @@ -13923,10 +13923,10 @@ Strings may be in single quotes (optional)]]> - + - + @@ -13945,13 +13945,13 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -14240,7 +14240,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15287,7 +15287,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15575,7 +15575,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15996,7 +15996,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -16119,7 +16119,7 @@ If you leave the search key empty, the system automatically creates a numeric nu - + @@ -16420,7 +16420,7 @@ There are two reasons for de-activating and not deleting records: If the document type of your document has no automatic document sequence defined, the field is empty if you create a new document. This is for documents which usually have an external number (like vendor invoice). If you leave the field empty, the system will generate a document number for you. The document sequence used for this fallback number is defined in the "Maintain Sequence" window with the name "DocumentNo_", where TableName is the actual name of the table (e.g. C_Order).]]> - + @@ -16464,7 +16464,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -16526,7 +16526,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -16619,7 +16619,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -16953,7 +16953,7 @@ There are two reasons for de-activating and not deleting records: - + diff --git a/db/ddlutils/data/AD_ELEMENT.xml b/db/ddlutils/data/AD_ELEMENT.xml index 7f87f1dfa3..ca776eefdf 100644 --- a/db/ddlutils/data/AD_ELEMENT.xml +++ b/db/ddlutils/data/AD_ELEMENT.xml @@ -61,7 +61,7 @@ - + @@ -95,7 +95,7 @@ - + @@ -2002,7 +2002,7 @@ Asset - create Project Asset transactions - ability to issue material]]> - + @@ -2034,7 +2034,7 @@ If the pattern for your language is not correct, please create a Adempiere suppo - + diff --git a/db/ddlutils/data/AD_FIELD.xml b/db/ddlutils/data/AD_FIELD.xml index 85d8e237a6..1f139db78d 100644 --- a/db/ddlutils/data/AD_FIELD.xml +++ b/db/ddlutils/data/AD_FIELD.xml @@ -345,7 +345,7 @@ There are two reasons for de-activating and not deleting records: (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -419,7 +419,7 @@ Strings may be in single quotes (optional)]]> - + @@ -684,7 +684,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -1155,7 +1155,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -1425,7 +1425,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -1961,7 +1961,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -4029,7 +4029,7 @@ There are two reasons for de-activating and not deleting records: - + ". @@ -4376,7 +4376,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -4627,7 +4627,7 @@ If you leave the search key empty, the system automatically creates a numeric nu - + @@ -4856,7 +4856,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -5153,7 +5153,7 @@ If you leave the search key empty, the system automatically creates a numeric nu - + - + - + @@ -6183,7 +6183,7 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -6577,7 +6577,7 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -7044,7 +7044,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -7247,7 +7247,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -7469,10 +7469,10 @@ There are two reasons for de-activating and not deleting records: - - - - + + + + @@ -7578,7 +7578,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -7658,7 +7658,7 @@ There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -7697,9 +7697,9 @@ There are two reasons for de-activating and not deleting records: (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - - - + + + @@ -7822,7 +7822,7 @@ If you leave the search key empty, the system automatically creates a numeric nu - + @@ -7856,7 +7856,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -7874,7 +7874,7 @@ There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -8408,7 +8408,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -8549,7 +8549,7 @@ There are two reasons for de-activating and not deleting records: - + - + - - + + ". @@ -9449,7 +9449,7 @@ If the document type of your document has no automatic document sequence defined - + @@ -9556,7 +9556,7 @@ There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -9577,7 +9577,7 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -10045,10 +10045,10 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -10120,8 +10120,8 @@ If you leave the search key empty, the system automatically creates a numeric nu - - + + @@ -10174,7 +10174,7 @@ If the document type of your document has no automatic document sequence defined - + @@ -10529,8 +10529,8 @@ There are two reasons for de-activating and not deleting records: - - + + @@ -11151,7 +11151,7 @@ If the document type of your document has no automatic document sequence defined - + @@ -11171,7 +11171,7 @@ If the document type of your document has no automatic document sequence defined - + @@ -11555,7 +11555,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -11770,7 +11770,7 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -11931,8 +11931,8 @@ There are two reasons for de-activating and not deleting records: (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - - + + @@ -12038,7 +12038,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -12093,7 +12093,7 @@ The callout is a Java class implementing org.compiere.model.Callout and a method - + @@ -12253,7 +12253,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -12578,7 +12578,7 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -12963,7 +12963,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -13404,7 +13404,7 @@ If you create a new Organization, you may supply a Organization Type. If you se - + @@ -14729,7 +14729,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -14884,7 +14884,7 @@ There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -14967,7 +14967,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -14975,7 +14975,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15262,7 +15262,7 @@ There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.]]> - + @@ -15274,7 +15274,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15327,7 +15327,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15567,7 +15567,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15578,10 +15578,10 @@ There are two reasons for de-activating and not deleting records: - + - + @@ -15780,7 +15780,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -15861,7 +15861,7 @@ There are two reasons for de-activating and not deleting records: - + @@ -16153,10 +16153,10 @@ There are two reasons for de-activating and not deleting records: - + - + diff --git a/db/ddlutils/data/AD_PRINTFORMATITEM.xml b/db/ddlutils/data/AD_PRINTFORMATITEM.xml index da4939bbb4..11ed3babe0 100644 --- a/db/ddlutils/data/AD_PRINTFORMATITEM.xml +++ b/db/ddlutils/data/AD_PRINTFORMATITEM.xml @@ -545,8 +545,8 @@ - - + + @@ -1186,8 +1186,8 @@ - - + + @@ -1214,8 +1214,8 @@ - - + + diff --git a/db/ddlutils/data/AD_REF_LIST.xml b/db/ddlutils/data/AD_REF_LIST.xml index 9dd3f4afd7..d0dc987f8b 100644 --- a/db/ddlutils/data/AD_REF_LIST.xml +++ b/db/ddlutils/data/AD_REF_LIST.xml @@ -86,7 +86,7 @@ - + @@ -399,8 +399,8 @@ - - + + @@ -774,7 +774,7 @@ - + diff --git a/migration/i2.0/oracle/201402261230_IDEMPIERE-1599.sql b/migration/i2.0/oracle/201402261230_IDEMPIERE-1599.sql new file mode 100644 index 0000000000..2cc47d9509 --- /dev/null +++ b/migration/i2.0/oracle/201402261230_IDEMPIERE-1599.sql @@ -0,0 +1,50 @@ +SET SQLBLANKLINES ON +SET DEFINE OFF + +-- Feb 26, 2014 11:50:10 AM SGT +-- IDEMPIERE-1599 Correct naming for acct wildcard dimensions +UPDATE AD_Ref_List SET Description='User Element List 1', Name='User Element List 1',Updated=TO_DATE('2014-02-26 11:50:10','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=282 +; + +-- Feb 26, 2014 11:50:32 AM SGT +UPDATE AD_Ref_List SET Description='User Element List 2', Name='User Element List 2',Updated=TO_DATE('2014-02-26 11:50:32','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=283 +; + +-- Feb 26, 2014 11:50:54 AM SGT +UPDATE AD_Ref_List SET Name='User Column 1',Updated=TO_DATE('2014-02-26 11:50:54','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=796 +; + +-- Feb 26, 2014 11:51:00 AM SGT +UPDATE AD_Ref_List SET Name='User Column 2',Updated=TO_DATE('2014-02-26 11:51:00','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=797 +; + +-- Feb 26, 2014 11:51:46 AM SGT +UPDATE AD_Ref_List SET Description='User Column 1',Updated=TO_DATE('2014-02-26 11:51:46','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=796 +; + +-- Feb 26, 2014 11:51:48 AM SGT +UPDATE AD_Ref_List SET Description='User Column 2',Updated=TO_DATE('2014-02-26 11:51:48','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=797 +; + +-- Feb 26, 2014 11:52:30 AM SGT +UPDATE AD_Ref_List SET Description='User Element List 1', Name='User Element List 1',Updated=TO_DATE('2014-02-26 11:52:30','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53430 +; + +-- Feb 26, 2014 11:52:38 AM SGT +UPDATE AD_Ref_List SET Name='User Element List 2',Updated=TO_DATE('2014-02-26 11:52:38','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53431 +; + +-- Feb 26, 2014 11:52:49 AM SGT +UPDATE AD_Ref_List SET Description='User Column 1', Name='User Column 1',Updated=TO_DATE('2014-02-26 11:52:49','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53432 +; + +-- Feb 26, 2014 11:52:52 AM SGT +UPDATE AD_Ref_List SET Name='User Column 2',Updated=TO_DATE('2014-02-26 11:52:52','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53433 +; + +-- Feb 26, 2014 11:52:54 AM SGT +UPDATE AD_Ref_List SET Description='User Column 2',Updated=TO_DATE('2014-02-26 11:52:54','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53433 +; + +SELECT register_migration_script('201402261230_IDEMPIERE-1599.sql') FROM dual +; \ No newline at end of file diff --git a/migration/i2.0/postgresql/201402261230_IDEMPIERE-1599.sql b/migration/i2.0/postgresql/201402261230_IDEMPIERE-1599.sql new file mode 100644 index 0000000000..3043725d3d --- /dev/null +++ b/migration/i2.0/postgresql/201402261230_IDEMPIERE-1599.sql @@ -0,0 +1,47 @@ +-- Feb 26, 2014 11:50:10 AM SGT +-- IDEMPIERE-1599 Correct naming for acct wildcard dimensions +UPDATE AD_Ref_List SET Description='User Element List 1', Name='User Element List 1',Updated=TO_TIMESTAMP('2014-02-26 11:50:10','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=282 +; + +-- Feb 26, 2014 11:50:32 AM SGT +UPDATE AD_Ref_List SET Description='User Element List 2', Name='User Element List 2',Updated=TO_TIMESTAMP('2014-02-26 11:50:32','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=283 +; + +-- Feb 26, 2014 11:50:54 AM SGT +UPDATE AD_Ref_List SET Name='User Column 1',Updated=TO_TIMESTAMP('2014-02-26 11:50:54','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=796 +; + +-- Feb 26, 2014 11:51:00 AM SGT +UPDATE AD_Ref_List SET Name='User Column 2',Updated=TO_TIMESTAMP('2014-02-26 11:51:00','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=797 +; + +-- Feb 26, 2014 11:51:46 AM SGT +UPDATE AD_Ref_List SET Description='User Column 1',Updated=TO_TIMESTAMP('2014-02-26 11:51:46','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=796 +; + +-- Feb 26, 2014 11:51:48 AM SGT +UPDATE AD_Ref_List SET Description='User Column 2',Updated=TO_TIMESTAMP('2014-02-26 11:51:48','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=797 +; + +-- Feb 26, 2014 11:52:30 AM SGT +UPDATE AD_Ref_List SET Description='User Element List 1', Name='User Element List 1',Updated=TO_TIMESTAMP('2014-02-26 11:52:30','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53430 +; + +-- Feb 26, 2014 11:52:38 AM SGT +UPDATE AD_Ref_List SET Name='User Element List 2',Updated=TO_TIMESTAMP('2014-02-26 11:52:38','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53431 +; + +-- Feb 26, 2014 11:52:49 AM SGT +UPDATE AD_Ref_List SET Description='User Column 1', Name='User Column 1',Updated=TO_TIMESTAMP('2014-02-26 11:52:49','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53432 +; + +-- Feb 26, 2014 11:52:52 AM SGT +UPDATE AD_Ref_List SET Name='User Column 2',Updated=TO_TIMESTAMP('2014-02-26 11:52:52','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53433 +; + +-- Feb 26, 2014 11:52:54 AM SGT +UPDATE AD_Ref_List SET Description='User Column 2',Updated=TO_TIMESTAMP('2014-02-26 11:52:54','YYYY-MM-DD HH24:MI:SS'),UpdatedBy=100 WHERE AD_Ref_List_ID=53433 +; + +SELECT register_migration_script('201402261230_IDEMPIERE-1599.sql') FROM dual +; \ No newline at end of file