OFBIZ ARCHITECTURE DOWNLOAD!
OFBiz: “Open For Business" is a set of enterprise applications built on a similar architecture using common data, logic and process components. Apache OFBiz is a suite of business applications flexible enough to be used across any industry. A common architecture allows developers to easily extend or enhance it to create custom features.FAQs · OFBiz · Ofbiz API · Apache OFBiz Jira issue. Apache OFBiz is an open source enterprise resource planning (ERP) system. It provides a suite All applications are built around a common architecture using common data, logic and process components. Beyond the framework itself, Developer(s): Apache Software Foundation.
|Published:||11 November 2014|
|PDF File Size:||49.77 Mb|
|ePub File Size:||43.70 Mb|
An Inventory Item contains information about where a particular good is located, the status of the item, and a serial number for serialized items or quantity on hand and available to promise amounts for non-serialized inventory. Products can be organized ofbiz architecture Product Categories.
Apache OFBiz : Functional User Guide
A single product can be a member of multiple categories and even ofbiz architecture themselves can be children of multiple categories and can have multiple child categories. Products can also be associated with one another to designate concepts such as variants, cross-sells, up-sells, marketing packages, etc.
Categories can be associated with different Catalogs.
- Apache OFBiz: Functional User Guide
- Apache OFBiz Project Overview - OFBiz Project Open Wiki - Apache Software Foundation
- Framework Introduction Videos and Diagrams
- 34 Comments
- Apache OFBiz
A Product Catalog is essentially a starting point for all information about a particular set of products to be sold. Promotions and inventory management options are associated with each catalog so that different sales channels can behave differently even with the same set ofbiz architecture underlying products.
To flexibly model different types of features that products often have there are entities for defining types of features and actual features that can be ofbiz architecture to products.
For instance, you might say that this shirt is a size large and is a blue colored shirt. Size and color are types of features and large and blue are actual features applied to the specific shirt product.
Framework Introduction Videos and Diagrams - OFBiz Project Open Wiki - Apache Software Foundation
Multiple prices can be associated with a single product, as can multiple costs. Different prices can be specified for different currencies, different sets of facilities or storesand for different date ranges.
This is a good place to introduce the wide-spread use of effective dating in OFBiz. There are two fields commonly used ofbiz architecture express effective dates: In the product price example the fromDate and thruDate are used to denote that a price goes into effect on a certain date and at a certain time and expires at a certain date and time.
This can be used to keep a history of price changes, and to effectively manage temporary promotional prices.
In addition to explicitly specifying prices there are also entities and logic that uses the entities to have rules about prices. For instance you could create a rule that is in effect for a certain time period that puts all of the products in a certain category on ofbiz architecture.
Or, you could give special prices to specific customers or groups of customers with a simple rule. Order The Order entities are used to manage information about sales and purchase orders and information leading up to an order.
For example a request for a specific product or feature may be submitted by a customer and that would be tracked by the request entities in the Ofbiz architecture package.
The request can be tracked and turned into a requirement which can be used to create a Work Effort a task, for instance; see the Work Effort section below to be created that will satisfy the requirement and fulfill the request. Once a requirement is made a quote can be produced which if accepted by the customer can be used to create an order.
Once an order is fulfilled an invoice can be created from the order. Invoices are part of the Accounting entity package described below.
There are various pieces of information related to an Order that can be associated with either the header or an individual or multiple line items of an order. Examples include the shipping destination and shipping preferences of an order which may be the same for all line items, or may be different for each one.
Adjustments are used to contain information about things that change the price of an order that are not actual goods or services sold or purchased. Examples include taxes, shipping, discounts, surcharges, and so forth. An adjustment can be either a flat amount, a flat amount per quantity, or a percentage of the subtotal of the entire order or the line item it is associated ofbiz architecture.
Payment preferences can be tracked as an order is created to automate payment once an invoice is created. This is especially useful for payment by credit card or other electronic means.
If no payment preferences are specified then a standard invoicing and billing process can be used.