View source | Discuss this page | Page history | Printable version   

ERP/2.50/Developers Guide/Database Model/ Module Merge



Modules can merge other ones. This table contains information about the merges. A module should be merged in a new major version and once it is merged it should be kept in all future versions. When there is a module merged, multiple DBPrefixes are allowed to maintain the one originally defined by the module as well as all the ones defined in the merged modules.

This table contains the following columns:

Name Nullable Data Type Description
AD_Module_Merge_ID NVARCHAR2(32)null
AD_Client_ID NVARCHAR2(32)Client for this installation.
AD_Org_ID NVARCHAR2(32)Organizational entity within client
Isactive NCHAR(1)A flag indicating whether this record is available for use or de-activated.
Created NDATEThe date that this record is completed.
Createdby NVARCHAR2(32)User who created this records
Updated NDATEx not implemented
Updatedby NVARCHAR2(32)User who updated this records
AD_Module_ID NVARCHAR2(32)Module
Merged_Module_Uuid NVARCHAR2(32)UUID of the merged module.
Merged_Module_Name NNVARCHAR2(60)Name of the merged module

Other Info

Check constraints

These are the check constraints for this table:



These are the indexes for this table (for each index there is a list of all the columns included within it):







Foreign key column to AD_Client table, (column: AD_Client_ID)

Validation Rule AD_Client Security validation: Clients with user access rights. With the following code:

AD_Client.AD_Client_ID IN (@#User_Client@)



Foreign key column to AD_Org table, (column: AD_Org_ID)

Validation Rule AD_Org Security validation: Organizations of the Client with user acces rights. With the following code:

(@AD_Client_ID@='0' AND AD_Org.AD_Org_ID='0') OR (@AD_Client_ID@!='0' AND ((AD_Org.AD_Client_ID IN (@#User_Client@) AND AD_Org.AD_Org_ID IN (@#User_Org@)) OR AD_Org.AD_Org_ID='0' AND AD_Org.IsSummary='N'))



There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reporting. There are two reasons for de-activating and not deleting records:
(1) The system requires the record for auditing purposes.
(2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are existing invoices for it. By de-activating the Business Partner you prevent it from being used in future transactions.


Creation Date

The Created field indicates the date that this record was created.


Created By

Foreign key column to AD_User table, (column: AD_User_ID)



The Updated field indicates the date that this record was updated.


Updated By

Foreign key column to AD_User table, (column: AD_User_ID)



Foreign key column to AD_Module table, (column: AD_Module_ID)


Merged Module UUID

It is the UUID of the merged module, it is very important to correctly setup this information since it will be internally used to identify the merged module.


Merged Module Name

Name of the merged module. It is used just to make the merged module human readable.


Retrieved from ""

This page has been accessed 2,918 times. This page was last modified on 2 July 2011, at 20:35. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.