If you have landed in this page directly, you may have to check out the introduction “ADempiere Implementation and Customization – Learning Plan” post, for continuity.
1. The starting point for any person who would like to start with ADempiere Implementation and Customization would be to install ADempiere. There are a plenty of articles written already by many others and available in adempiere wiki, documentation on the installation procedure, with good screen shots. I would not re write that here. You can also google for the same to find one.
2. Start using ADempiere:
This is a very important step for any person who would like to start off on ADempiere usage, development, administration or customization. You have to explore each and every menu item, windows, forms, tabs and fields within. Am sure you will be a great User and Good Administrator if you would just explore the whole application for 1 month, for atleast 2 hours daily. Understand the Windows, Adminsitration Options available using the System user (<username: System passowrd: System > — case sensitive) as well the GardenAdemin user (username: GardenAdmin password: GardenAdmin)
The best way to explore the windows is to start with the Menu folders in the follwoing order.
Quote to Invoice, Requisition to Invoice, Material Management, Open Items, Partner Relations, Performance Management, System and then others.
The above sequence would give a first time user a beter exposure to some concepts/ items within Adempiere so that the flow of exploring helps you understand them easily.
Each time you explore a new window, try to understand what are the all fields available on the window, how they are logical grouped into field groups, how selection of one drop down effects the values or layout of the window. What happens when you save the window. How the various tabs and the inner content is related to data on the other tabs within the same window. What kind of errors you come across when you trying use some windows or entering some data. Also observe the fields which are only read only. Also observe the fields which get filled in automatically. relate each field to some other field in another tab or window, logically to understand the whole purpose of that window.
There are also important buttons at the bottom of most of the documents, which have the name “Prepare/ Complete/ Close”, “Posted/ Not Posted”. just play around with all the buttons and fields and draw your own conclusions of the effects of their actions. Yoou will for sure learn what exactly each of those fields mean, and their significance , behavior in the coming tutorials.
Now, understand how the windows are organised within ADempiere. For Example take “Sales Order” window
Sales Order window had got three tabs within it: Order Header, Order Line, Order Tax. Each Tab has got many details wwithin arranged as fields of various types: text, dropdown, search field etc. The records of data in each Tab are related to the other records in the other tab. You can see the related data by selecting the record in one tab and then chosing the other tab (use Grid View for better correlation).
Developer Tip: Each Tab is created based on One physical database table within ADempiere. Each Field within the tab is a Column in the table. So each tab is nothing but a database Table and data entered in to these fields in these tabs are just insertions of rows in the database table. For Example: Order Header tab is for the database table: C_Order.
Tabs can also have fields which may not represent any physical database column but yet exist on the tab. Such Fields can be virtual columns whose values are calculations based on other fields, which are called virtual columns.
Sometimes when you enter a value into a field, you notice many other calues get changed within that window. For Example when you select Business Partner on a Sales Order, you can see the values in the other fields: “Location, Contact Person, Invoice Location etc” are filled automatically. These values are filled automatically using small scipts called callouts. These callouts can be considered as event actions. Whenever you the change the value of a field in a window which has a callout defined on it, the callout script is executed to make changes in the other fields within the same window. More details about callouts in the next chapters.
continued ….
Happy reading.
- Sunil Savaram
Tags: ADempiere Callouts, ADempiere customization, ADempiere implementation, ADempiere Windows
I like this site very much.
This is such a outstanding website.
And it is not like other money orientating web, the info here is truly important.
I am definitely bookmarking it as well as sharin it with my friends.