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

Contents 1 AD_Module_Dependency_Inst 1.1 Other Info 1.1.1 Check constraints 1.1.2 Indexes 1.1.2.1 Unique 1.2 Columns 1.2.1 AD_Module_Dependency_Inst_ID 1.2.2 Client 1.2.3 Organization 1.2.4 Active 1.2.5 Creation Date 1.2.6 Created By 1.2.7 Updated 1.2.8 Updated By 1.2.9 Module Dependency 1.2.10 Module 1.2.11 Dependent Module 1.2.12 First Version 1.2.13 Last Version 1.2.14 Is Included 1.2.15 Dependant Module Name 1.2.16 Dependency Enforcement 1.2.17 User Editable Enforcement

AD_Module_Dependency_Inst

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

• Name:ADModuleDependencyInst
• Classname:ModuleDependencyInst

This table contains the following columns:

Name	Nullable	Data Type	Description
AD_Module_Dependency_Inst_ID	N	VARCHAR2(32)	Temporary table for updating/installing modules
AD_Client_ID	N	VARCHAR2(32)	Client for this installation.
AD_Org_ID	N	VARCHAR2(32)	Organizational entity within client
Isactive	N	CHAR(1)	A flag indicating whether this record is available for use or de-activated.
Created	N	DATE	The date that this record is completed.
Createdby	N	VARCHAR2(32)	User who created this records
Updated	N	DATE	x not implemented
Updatedby	N	VARCHAR2(32)	User who updated this records
AD_Module_Dependency_ID	N	VARCHAR2(32)	Defines dependencies ammong modules
AD_Module_ID	N	VARCHAR2(32)	Module
AD_Dependent_Module_ID	N	VARCHAR2(32)	Dependent Module
Startversion	N	VARCHAR2(10)	First compatible version
Endversion	Y	VARCHAR2(10)	Last compatible version
Isincluded	N	CHAR(1)	Defines whether it is included or just dependant
Dependant_Module_Name	Y	VARCHAR2(60)	Name of the dependent module
Dependency_Enforcement	N	VARCHAR2(60)	Dependency enforcement defines which are the versions of the dependent module that are compatible with the parent one.
User_Editable_Enforcement	N	CHAR(1)	Defines whether the enforcement can be overwritten by user

Other Info

Check constraints

These are the check constraints for this table:

• AD_MODULE_DEPENDENCY_INST__CHK: ISACTIVE IN ('Y', 'N')
• AD_MODULE_INST_ISINCLUDED_CHK: ISINCLUDED IN ('Y', 'N')

top

Indexes

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

Unique

• AD_MODULE_DEPENDENCY_INST_PK
  • AD_Module_Dependency_Inst_ID

top

Columns

AD_Module_Dependency_Inst_ID

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

• Physical column name: AD_Module_Dependency_Inst_ID
• Property Name: id
• Reference: ID

top

Client

• Physical column name: AD_Client_ID
• Property Name: client
• Reference: TableDir
• Default value: @AD_CLIENT_ID@

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

• Physical column name: AD_Org_ID
• Property Name: organization
• Reference: TableDir
• Default value: @AD_ORG_ID@

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.

• Physical column name: Isactive
• Property Name: active
• Reference: YesNo
• Default value: Y

top

Creation Date

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

• Physical column name: Created
• Property Name: creationDate
• Reference: DateTime
• Default value: SYSDATE

top

Created By

• Physical column name: Createdby
• Property Name: createdBy
• Reference: Search

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

top

Updated

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

• Physical column name: Updated
• Property Name: updated
• Reference: DateTime
• Default value: SYSDATE

top

Updated By

• Physical column name: Updatedby
• Property Name: updatedBy
• Reference: Search

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

top

Module Dependency

Defines dependencies ammong modules

• Physical column name: AD_Module_Dependency_ID
• Property Name: moduleDependency
• Reference: String

top

Module

Indicates the module the element forms part of.

• Physical column name: AD_Module_ID
• Property Name: module
• Reference: String
• This column is part of the table's identifier

top

Dependent Module

It is the Dependent Module for the current dependency.

• Physical column name: AD_Dependent_Module_ID
• Property Name: dependentModule
• Reference: String

top

First Version

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

• Physical column name: Startversion
• Property Name: firstVersion
• Reference: String

top

Last Version

It is the last compatible version to define the dependency.

• Physical column name: Endversion
• Property Name: lastVersion
• Reference: String

top

Is Included

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

• Physical column name: Isincluded
• Property Name: isIncluded
• Reference: YesNo
• Default value: N

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.

• Physical column name: Dependant_Module_Name
• Property Name: dependantModuleName
• Reference: String
• This column is part of the table's identifier

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:

• Major Version (default). The compatible versions are all the minor version within the same major version. If "Last Version" is defined being a different major version than "From Version", "Last Version" defines the highest compatible minor version; if "Last Version" is in the same major version than "From Version" this value is not taken into account. It is the default value.
  
• Minor Version. Defines a strict dependency to the exact minor version. In case no "Last Version" is set, "From Version" is the only compatible version. Other case the compatible versions are all between "From" and "Last Version" values.
  
• None. "From Version" is the only field taken into account, there is no restriction on different major versions.
• Physical column name: Dependency_Enforcement
• Property Name: dependencyEnforcement
• Reference: String
• Default value: MAJOR

top

User Editable Enforcement

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

• Physical column name: User_Editable_Enforcement
• Property Name: userEditableEnforcement
• Reference: YesNo

top