View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

Module

This article is protected against manual editing because it is automatically generated from Openbravo meta-data. Learn more about writing and translating such documents.
Back button.png   Back to Application Dictionary


Contents

Introduction

Manages the modules currently installed.

ManualDoc:WD586192D06C14EC182B44CAD34CA4295

Module

This tab manages the installed modules in the application.

ManualDoc:TF53E35A11C564F20BE4082A7B8CFF6B7

Dependency

Lists all the modules that are form part of the dependencies for the module.

ManualDoc:T134DE6BD8CD34FDFB6DC940BF857BC25

Include

For packages and templates the list of included modules is the list of the modules that form part of the package.

ManualDoc:TB30CF79CF71245339E94B4B332BAABF1

DB Prefix

DB Prefixes of the module

ManualDoc:TFD79A6D6DB094BE88F2F0E0333A399B2

Data Package

The Data Package is a grouping mechanism for tables within a module. Openbravo has a java business object for each Table. The java package of the java business object is defined in the Data Package. For example: a module for a crm package with the name: org.crm has packages: - org.crm.order - org.crm.customer

The corresponding tables have then the following setting: - Customer, in the org.crm.customer package, resulting in the java class: org.crm.customer.Customer - SalesOrder, in the org.crm.order package, resulting in the java class: org.crm.order.SalesOrder

ManualDoc:T29021BB9A96244BDA7E8AEBA71ADFB11

Merges

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.

ManualDoc:T40207FE1E4F94FDDA026C37C4E1E1847

Naming Exceptions

The database objects that do not follow the modularity naming rules but are within the module are defined as Exceptions. This is particularly useful to facilitate the migration of all instances to modules. When an object is added to this tab, it will be exported its module instead of to core.

ManualDoc:T39B3DB3BF4C44EE192BE3F6CA69903C0

Translation

Module information can be translated to different languages

ManualDoc:T47F87F1A284B4A7D9FB6ED2D02C5CDA1


Full list of Module window fields and their descriptions is available in the Module Screen Reference.

Back button.png   Back to Application Dictionary

Retrieved from "http://wiki.openbravo.com/wiki/Module"

This page has been accessed 1,662 times. This page was last modified on 3 April 2012, at 10:32. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.