Difference between pages "DE/Steuerbasis" and "Ecosoft/Bicycle Manufacturer Case Study"

From ADempiere
(Difference between pages)
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Created page with '{{Breadcrumb|DE/Inhaltsverzeichnis|next=DE/Inhaltsverzeichnis}} ''Helfen Sie bitte mit diese Beschreibung zu verbessern und zu ergänzen. Achten Sie aber immer auf die Wahrung …')
 
(Phase II: Purchase Cycle)
 
Line 1: Line 1:
{{Breadcrumb|DE/Inhaltsverzeichnis|next=DE/Inhaltsverzeichnis}}
+
[[Image:bicycle_parts.jpg|right|500px|thumb|Worker lacing a wheel in one of the assembly lines at project site]]
 +
==Title==
 +
Case Study for a complete business cycle that most small and medium size manufacturers should have. ADempiere is being used to improve business process of one the top 3 Bicycle Manufacturer in Thailand.
  
 +
'''''The project is now under implementation by [[Ecosoft]] and due to complete end of 2010''''' --[[User:Kittiu|Kittiu]] 08:25, 20 September 2010 (UTC)
  
''Helfen Sie bitte mit diese Beschreibung zu verbessern und zu ergänzen. Achten Sie aber immer auf die Wahrung der Urheberrechte. Schreiben Sie bitte Ihre Ergänzungen und Anregungen unter den Abschnitt [[#Beiträge|Beiträge]]''
+
'''Remarks:''' Implemented on version 360LTS, Postgresql 8.4, Fedora OS
  
 +
==Industry==
 +
'''Bicycle Manufacturer'''
  
 +
==Geography==
 +
The HQ and Factory of the client is located at outer skirt of Bangkok, Thailand.
  
[[Category:Deutsche_Lokalisierung]]
+
==Company Profile==
[[Category:Manual_de]]
+
The company is founded in 1988 by a group of engineers and bicycle experts. At the beginning, it was a small manufacturer with capacity less than 1,000 sets a month. From there, the company kept on evolving in terms of manufacturing technology and design.
[[Category:German]]
+
  
 +
With the support from customers and suppliers, it is set to become the leading bicycle-parts manufacturer in Thailand reaching a capacity of 30,000 bicycles a month with more than 1,000 items of products to choose from.
  
==Start des Fensters==
+
Its product-line covers almost the entire bicycle, ranging from hubs and chain wheels with cranks to bicycle frames, forks, and handle bars.
  
{{MenuRef|Leistungsanalyse|Einstellungen Buchführung|Allgemeine Steuerverwaltung|Steuerbasis}}
+
==Opportunities==
 +
We see abundance of similar opportunities in Thailand. A lot of small and medium size (SME) companies' requirements are too complicated for standard accounting software. SAP or Oracle's Financials are more suitable but falls beyond most of the SMEs' ''Developing World'' budget. Many share similar pains in the management of their inventory and production processes and integration to the back-office and day-to-day business administration.
  
 +
==Risks==
 +
==Implementation Modules==
 +
The project is divided into 3 parts, each will be dealing with corresponding set of users. After finish each phase, training will be conducted to ensure that user gets familiar with the software. At the end of the last phase, the practicing data will be cleaned, stock item will be counted, unpaid invoice will be uploaded. The system will go live on the 1st day of 2011.
 +
===Phase I: Sales Cycle===
 +
Sales Cycle is the process of selling goods to customer that starts from receiving order from customer, shipping, invoicing, and money collecting as well as making a deposit into the company’s bank account. Existing sales cycle is described as per below which consists of:
 +
*Order and Delivery
 +
*Billing and Collection
 +
*Finance
  
 +
'''Order and Delivery'''
  
 +
[[Image:sales_cycle.jpg]]
  
==Fenster: Steuerbasis==
+
'''Billing and Collection'''
  
 +
[[Image:sales_cycle_2.jpg]]
  
 +
'''Finance'''
  
'''Hilfe:'''
+
[[Image:sales_cycle_3.jpg]]
  
Legt die Bemessungsgrundlage der Steuer fest.  
+
===Phase II: Purchase Cycle===
 +
[[File:Purchase_Cycle.jpg]]
  
 +
===Phase III: Manufacturing===
  
Die Steuerbasis kann auf Preis, Kosten und Menge basieren.
+
==Special Highlights==
 +
During implementation, we have the principle to use the standard ADempiere as much as possible. Anything configurable, will be configured using ADempiere's powerful Application Dictionary. Any necessary customization will be done without touching the core, ensuring future ease of maintenance and compatibility with future release.
  
 +
Many technique without touching core ADempiere will be applied, i.e.,
 +
*[[ModelValidator]]
 +
*[[Script_ModelValidator]]
 +
*[[Script Callout]]
 +
*[[Create your ADempiere customization environment]]
 +
*etc.
  
{{Note|Wenn die hier getätigten Einstellungen für alle Organisationen gelten sollen müssen Sie bei der Anmeldung die Organisation "*" auswählen. Oder wählen Sie beim neu anlegen eines Datensatzes "*" bei der Organisation aus.}}
+
Enhancement and by product that are useful are documented here.
 +
=== Special Functionality ===
 +
*Chart of Account (may be useful for Thai's SME - Manufacturing Industry) [[File:CoA_Thai_SME_manufacturing.xls]]
 +
*Features in customization.jar '''[[Customization for Bicycle Manufacturer Case Study]]'''
  
 +
==Lessons==
 +
===Functional Aspects===
 +
This section is notes on what we found during implementation, and think it is worth listing. It is by no mean, correct, recommending nor the best solution.
 +
*'''Unit Price in Requisition Line (Requisition Window)'''
 +
**Is copied from '''Standard Price''' of the product's price list.
 +
**User who do the requisition can overwrite it, but for PO created using Create PO from Requisition Process, it will not be copied in PO Line. PO Line still use the standard price of the product.
 +
**This also make sense as the requester should not know the price. The overwritten price can be for reference only.
  
 +
===Technical Aspects===
 +
*Super detail [[Installation Guide for AD360, Postgres and Fedora]]
 +
*Workshop for new developer on AD's Basic Technical stuffs, in easy reading format, i.e., How to Install, Reporting (include Jasper), Setup Debugging Environment, How workflow works. [[File:AD_Basic Tech Workshop.pdf]]
 +
*[[Using Jasper Report Form in place of Standard Forms]], i.e., Sales Order, Delivery Note, Receipt, Invoices and etc.
 +
**How ADempiere locate Forms for each document type
 +
**Creating new Jasper Report Form and passing the right parameter
 +
**Number to Text in Jasper Form (Thai Language)
 +
**Registering Jasper Form
 +
*[[Creating New Data Import Window]]
  
 
+
==Project Log==
===Tab: Steuerbasis===
+
*First phase (Sales Cycle) completed, training conducted at client site. --[[User:Kittiu|Kittiu]] 08:08, 20 September 2010 (UTC)
 
+
*Second phase (Purchase Cycle) completed, training conducted at client site. --[[User:Kittiu|Kittiu]] 01:34, 30 October 2010 (UTC)
Tabelle:
+
[[Category:Marketing]]
 
+
[[Category:Projects and Tools]]
[[Image:TTH_Steuerbasis_360LTS.png|800px]]
+
 
+
 
+
 
+
Bei der Neuanlage einer Steuerbasis kann der Mandant und die Organisation ausgewählt werden. Nach der ersten Speicherung ist jedoch keine weitere Änderung des Mandanten oder der Organisation möglich.
+
 
+
 
+
 
+
 
+
{|{| border="1" cellpadding="5" cellspacing="0"
+
|-
+
|-valign="top"
+
!style="background:#efefef;" |'''''Name Original (Englisch)'''''
+
!style="background:#efefef;" |'''''Name Deutsch'''''
+
!style="background:#efefef;" |'''''Beschreibung'''''
+
!style="background:#efefef;" |'''''Hilfe'''''
+
!style="background:#efefef;" |'''''Technische Daten'''''
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|Client
+
|Mandant
+
|Mandant für diese Installation.
+
|Ein "Mandant" ist eine Firma oder eine juristische Person. Sie können keine Daten über Mandanten hinweg verwenden.
+
|AD_Client_ID<br>NUMBER(10)<br>TableDir
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|Organization
+
|Organisation
+
|Organisationseintrag für den Mandanten
+
|Eine "Organisation" ist ein Bereich Ihres Mandanten oder eine juristische Person - z. B. ein Geschäft oder eine Abteilung. Sie können Daten über Organisationen hinweg gemeinsam verwenden
+
|AD_Org_ID<br>NUMBER(10)<br>TableDir
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|Search Key
+
|Suchschlüssel
+
|Suchschlüssel für den Eintrag im erforderlichen Format - muss eindeutig sein.
+
|Der "Suchschlüssel" ermöglicht es, einen bestimmten Eintrag schnell zu finden. Wenn Sie "Suchschlüssel" frei lassen, generiert das System automatisch eine Nummer. Der für die Fallbacknummer verwendete Belegnummernkreis ist im Fenster "Nummernkreis" unter dem Namen Belegnummer_  festgelegt, wobei der Tabellenname jeweils der aktuelle Name der Tabelle ist.
+
|Value<br>NVARCHAR2(40)<br>String
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|Name
+
|Name
+
|Bezeichnung des Eintrags (alphanumerisch).
+
|Der "Name" eines Eintrags wird zusätzlich zum Suchschlüssel als Standardsuchoption verwendet. Der Name kann bis zu 60 Zeichen lang sein.
+
|Name<br>NVARCHAR2(60)<br>String
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|Description
+
|Beschreibung
+
|Optionale kurze Beschreibung für den Eintrag.
+
|Eine "Beschreibung" kann bis zu 255 Zeichen lang sein.
+
|Description<br>NVARCHAR2(255)<br>String
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|Comment/Help
+
|Kommentar/Hilfe
+
|Kommentar oder Hinweis.
+
|"Kommentar/Hilfe" enthält Hinweise, Kommentare oder Hilfestellungen zum Umgang mit dem Posten.
+
|Help<br>NVARCHAR2(2000)<br>Text
+
|-valign="top"
+
|-  
+
 
+
|-valign="top"
+
|Active
+
|Aktiv
+
|Der Eintrag ist im System aktiv.
+
|Es gibt zwei Methoden, den Zugriff auf Einträge des Systems zu sperren: Sie können einen Eintrag löschen oder deaktivieren. Ein deaktivierter Eintrag kann nicht ausgewählt werden, steht aber für Berichte zur Verfügung. Zwei Gründe sprechen für die Deaktivierung und gegen das Löschen von Einträgen: (1) Das System benötigt den Eintrag für Prüfungszwecke. (2) Auf den Eintrag wird in anderen Einträgen verwiesen. Beispielsweise kann ein Geschäftspartner nicht gelöscht werden, wenn Rechnungen für den Eintrag vorhanden sind. Sie deaktivieren also den Geschäftspartner und verhindern so, dass der Eintrag für spätere Einträge verwendet wird
+
|IsActive<br>CHAR(1)<br>YesNo
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|
+
|Basis
+
|Berechnungsgrundlage.
+
|
+
|
+
|-valign="top"
+
|-
+
 
+
|-valign="top"
+
|
+
|Prozent
+
|Prozent des Gesamtbetrags.
+
|Prozent eines Betrags (bis 100).
+
|
+
|-valign="top"
+
|-
+
 
+
|}
+
 
+
 
+
 
+
 
+
==Quellseiten==
+
F1 Hilfe im Fenster Steuerbasis
+
 
+
 
+
 
+
 
+
==Beiträge==
+

Revision as of 18:37, 29 October 2010

Worker lacing a wheel in one of the assembly lines at project site

Title

Case Study for a complete business cycle that most small and medium size manufacturers should have. ADempiere is being used to improve business process of one the top 3 Bicycle Manufacturer in Thailand.

The project is now under implementation by Ecosoft and due to complete end of 2010 --Kittiu 08:25, 20 September 2010 (UTC)

Remarks: Implemented on version 360LTS, Postgresql 8.4, Fedora OS

Industry

Bicycle Manufacturer

Geography

The HQ and Factory of the client is located at outer skirt of Bangkok, Thailand.

Company Profile

The company is founded in 1988 by a group of engineers and bicycle experts. At the beginning, it was a small manufacturer with capacity less than 1,000 sets a month. From there, the company kept on evolving in terms of manufacturing technology and design.

With the support from customers and suppliers, it is set to become the leading bicycle-parts manufacturer in Thailand reaching a capacity of 30,000 bicycles a month with more than 1,000 items of products to choose from.

Its product-line covers almost the entire bicycle, ranging from hubs and chain wheels with cranks to bicycle frames, forks, and handle bars.

Opportunities

We see abundance of similar opportunities in Thailand. A lot of small and medium size (SME) companies' requirements are too complicated for standard accounting software. SAP or Oracle's Financials are more suitable but falls beyond most of the SMEs' Developing World budget. Many share similar pains in the management of their inventory and production processes and integration to the back-office and day-to-day business administration.

Risks

Implementation Modules

The project is divided into 3 parts, each will be dealing with corresponding set of users. After finish each phase, training will be conducted to ensure that user gets familiar with the software. At the end of the last phase, the practicing data will be cleaned, stock item will be counted, unpaid invoice will be uploaded. The system will go live on the 1st day of 2011.

Phase I: Sales Cycle

Sales Cycle is the process of selling goods to customer that starts from receiving order from customer, shipping, invoicing, and money collecting as well as making a deposit into the company’s bank account. Existing sales cycle is described as per below which consists of:

  • Order and Delivery
  • Billing and Collection
  • Finance

Order and Delivery

Sales cycle.jpg

Billing and Collection

Sales cycle 2.jpg

Finance

Sales cycle 3.jpg

Phase II: Purchase Cycle

Purchase Cycle.jpg

Phase III: Manufacturing

Special Highlights

During implementation, we have the principle to use the standard ADempiere as much as possible. Anything configurable, will be configured using ADempiere's powerful Application Dictionary. Any necessary customization will be done without touching the core, ensuring future ease of maintenance and compatibility with future release.

Many technique without touching core ADempiere will be applied, i.e.,

Enhancement and by product that are useful are documented here.

Special Functionality

Lessons

Functional Aspects

This section is notes on what we found during implementation, and think it is worth listing. It is by no mean, correct, recommending nor the best solution.

  • Unit Price in Requisition Line (Requisition Window)
    • Is copied from Standard Price of the product's price list.
    • User who do the requisition can overwrite it, but for PO created using Create PO from Requisition Process, it will not be copied in PO Line. PO Line still use the standard price of the product.
    • This also make sense as the requester should not know the price. The overwritten price can be for reference only.

Technical Aspects

Project Log

  • First phase (Sales Cycle) completed, training conducted at client site. --Kittiu 08:08, 20 September 2010 (UTC)
  • Second phase (Purchase Cycle) completed, training conducted at client site. --Kittiu 01:34, 30 October 2010 (UTC)