...
Concept or Term | Definition | Example |
---|---|---|
Party | User, person, organisation or other entity (where entity is not an OFBiz "Entity" but rather entity in the legal sense) implied in at least one process modelled and implemented by OFBiz.
(from HR glossary) In OFBiz a party is a term used to simplify collecting information that used in a common manner by different people and things. The most common party types are people and groups. Both people and groups have contact information. A party is identified by a unique Party Id. Using this id OFBiz can collect and find contact (and other information and processes) for both people and groups in the same way. This is why you will often see Party Id as a field in a form or a filter as you work in OFBiz. | eg : administrator of the website; a company dealing goods and/or services via the website; an OFBiz customer assigned a unique party identifier, etc. |
ERP | An acronym for Enterprise Resource Planning, an ERP is basically a category of software used for managing a business. It is often a package containing several individual, but integrated, applications. Some of those applications might be Accounts Receivable, Accounts Payable, General Ledger, or Point of Sale. | Apache OFBiz, OpenBravo, Odoo |
CRM |
|
|
E-Business |
|
|
E-Commerce | The buying and selling of goods or services over electronic systems. |
|
MRP |
|
|
SCM |
|
|
CMMS/EAM |
|
|
Vendor | Role of a party that sells something with the system |
|
Supplier | Role of a party that something if purchased from |
|
Component | An OFBiz component is a directory used by the OFBiz framework to specify and load application server resources necessary to execute an OFBiz instance. Each OFBiz component must have a unique name (typically the name of the root directory for the component) and a configuration file called: "ofbiz-component.xml". Component resources may include, but are not limited to: webapps, Java source/classes, classpath resources, scripts, entity definitions, entity data files, service definitions, service and entity ECA rules, test suites, and encryption keystores. A component contains applications and/or the lower level tools and definitions needed by applications. A component can be used for self-contained extensions, including applications and logic/data modifications, to the suite of tools and applications that come with OFBiz. |
|
Application | A part of Component (at the user level) beginning with the ~webapp directory. A single component may contain several applications each mounted on a unique URL. Within each component, the "ofbiz-component.xml" file defines the available applications and how those applications shall be mounted on URLs. | Examples: OOTB the Accounting component has three applications: Accounting, AP and AR. |
Agreement | An agreement is a way of recording a business arrangement or contract that your business makes with other conmpanies or individuals | Examples: Customer or Supplier payment terms (eg.30 days to pay), Discounts (e.g products or volome), Commissions, |