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

ERP 2.50:Developers Guide/Database Model/org.openbravo.model.ad.access/AD Module Dependency Inst

ERP 2.50:Developers Guide/Database Model/org.openbravo.model.ad.access

Index

Contents

AD_Module_Dependency_Inst

This temporary table is used to store module dependencies during the update and install processes

This table contains the following columns:

Name Nullable Data Type Description
AD_Module_Dependency_Inst_ID NVARCHAR2(32)Temporary table for updating/installing modules
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_Dependency_ID NVARCHAR2(32)Defines dependencies ammong modules
AD_Module_ID NVARCHAR2(32)Module
AD_Dependent_Module_ID NVARCHAR2(32)Dependent Module
Startversion NVARCHAR2(10)First compatible version
Endversion YVARCHAR2(10)Last compatible version
Isincluded NCHAR(1)Defines whether it is included or just dependant
Dependant_Module_Name YVARCHAR2(60)Name of the dependent module
Dependency_Enforcement NVARCHAR2(60)Dependency enforcement defines which are the versions of the dependent module that are compatible with the parent one.
User_Editable_Enforcement NCHAR(1)Defines whether the enforcement can be overwritten by user

Other Info

Check constraints

These are the check constraints for this table:

top

Indexes

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

Unique

top

Columns

AD_Module_Dependency_Inst_ID

This temporary table is used to store module dependencies during the update and install processes

top

Client

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@)

top

Organization

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'))

top

Active

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.

top

Creation Date

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

top

Created By

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

top

Updated

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

top

Updated By

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

top

Module Dependency

Defines dependencies ammong modules

top

Module

Indicates the module the element forms part of.

top

Dependent Module

It is the Dependent Module for the current dependency.

top

First Version

It is the first compatible version for the dependency, in case last version is blank is will be the only one.

top

Last Version

It is the last compatible version to define the dependency.

top

Is Included

A dependency can include other modules in case it is a dependency for packages.

top

Dependant Module Name

The name of the dependent module is stored here because the dependent module can have been removed. In that case it is still relevant to show the module name to detect a broken dependency.

top

Dependency Enforcement

Dependency enforcement defines which are the versions of the dependent module that are compatible with the parent one.

The values it can contain are:

top

User Editable Enforcement

When a dependency/inclusion is "User Editable Enforcement", the enforcement defined for that dependency can be overwritten at instance level.

top

Retrieved from "http://wiki.openbravo.com/wiki/ERP_2.50:Developers_Guide/Database_Model/org.openbravo.model.ad.access/AD_Module_Dependency_Inst"

This page has been accessed 2,110 times. This page was last modified on 14 June 2011, at 11:03. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.