Menu
▾
▴
web-erp-svn
|
From: <dai...@us...> - 2011-03-13 08:28:51
|
Revision: 4509
http://web-erp.svn.sourceforge.net/web-erp/?rev=4509&view=rev
Author: daintree
Date: 2011-03-13 08:28:44 +0000 (Sun, 13 Mar 2011)
Log Message:
-----------
add to contract manual
Modified Paths:
--------------
trunk/doc/Change.log.html
trunk/doc/Manual/ManualContracts.html
Modified: trunk/doc/Change.log.html
===================================================================
--- trunk/doc/Change.log.html 2011-03-13 04:55:32 UTC (rev 4508)
+++ trunk/doc/Change.log.html 2011-03-13 08:28:44 UTC (rev 4509)
@@ -1,5 +1,6 @@
<p><font SIZE=4 COLOR=BLUE><b>webERP Change Log</b></font></p>
<p>
+<p>12/3/11: Tim Now allow space in codes </p>
<p>12/3/11: SelectSalesOrder.php now allows any number of sales orders to be selected and purchase orders placed for the aggregate of items on the selected sales orders</p>
<p>12/3/11: SuppPriceList.php removed a round trip to DB to get currency - fixed function to get pdf to new TCPDF Output </p>
<p>12/3/11: Exson fix all htmlentities to use ENTQUOTES, 'UTF-8' option so other character sets work with it</p>
Modified: trunk/doc/Manual/ManualContracts.html
===================================================================
--- trunk/doc/Manual/ManualContracts.html 2011-03-13 04:55:32 UTC (rev 4508)
+++ trunk/doc/Manual/ManualContracts.html 2011-03-13 08:28:44 UTC (rev 4509)
@@ -1,43 +1,43 @@
<!-- Help Begin: Contracts -->
-<br><br>
+<br /><br />
<a name="Contracts"><font size="+3"><b>Contract Costing</b></font></a>
-<br><br>
+<br /><br />
<font size="+1"><b>Overview</b></font>
-<br><br>
+<br /><br />
The Contracts module allows for construction of costings for specific customer projects where a bill of materials to be taken from inventory for the contract can be defined, together with a costed list of other requirements. By entering a gross profit percentage figure a price can then be arrived at to charge the customer. The contract can then be converted to a quotation. While the contract is at the quotation stage it is possible to modify the stock components and other requirements - the quotation will be updated with the new costing on commital. The quotation can then be resubmitted to the customer.
-<br><br>
+<br /><br />
When a contract is converted to a quotation the system actually creates a manuafactured inventory item with the name of the contract refence and with the description from the contract description.
-<br><br>
+<br /><br />
When (if) the quotation is accepted by the customer, the quotation can be converted to an order in the usual way by modifying the quotation flag from quotation to order. Committing this change then changes the status of the contract to ordered so that changes are no longer allowed. This process also creates a work order so that stock required for the contract can be issued to it. By using the work order issue functionality the stock is reduced and work in progress is increased.
-<br><br>
+<br /><br />
When supplier invoices (accounts payable) are entered there is the option to specify the contract that is to be charged with the cost. The cost of contract charges also goes to the work in progress account (as determined from the stock category record of the contract). Any number of contract charges can be entered against a supplier invoice (or credit note). In entering contract charges there is also the possibility of flagging whether or not the charge was orignially envisaged and costed into the contract or not. Contract charges records are created for each entry.
-<br><br>
+<br /><br />
The original contract costing can be compared against the actual charges against the contract, to see how much was made on the contract. When all charges are entered against the contract it needs the status of the contract to be changed to complete. This process closes the work order and compares the original contract cost against actual costs and takes the value not charged to cost of sales to the usage variances account (based on the stock category of the contract item) and clears the balance that would otherwise be left in work in progress.
-<br><br>
+<br /><br />
<font size="+1"><b>Creating a New Contract</b></font>
-<br><br>
+<br /><br />
From the contract tab of the main menu, select Create Contract. The first step is to select the customer for whom the contract is for.
-<br><br>
+<br /><br />
The contract requires a reference up to 20 characters - without spaces, slashes or inverted commas - that will be used for the contract code. It must be unique from other contracts and also from any existing inventory item codes already in the system. A description of the contract is also required. The description can be any length and is a text field but will be truncated in the stockmaster to X characters when the contract is converted to a quotation. The description in the contract record is retained.
-<br><br>
+<br /><br />
Each contract must also specify the category - the existing inventory categories are displayed to select from but new categories can be created. It is important to realise that the posting for the general ledger is performed based on the general ledger codes set up against the inventory category selected. e.g. charges against the contract will be posted to the work in progress account against this inventory category and the usage variance account of this category will be used for any difference between the contract total cost and the original costing.
-<br><br>
+<br /><br />
The gross profit percentage entered is the factor used based on the cost to arrive at the contract price.
-<br><br>
+<br /><br />
The date that the customer requires the contract to be completed is also specified in the contract. This propogates through to the quotation and order.
-<br><br>
+<br /><br />
If the contract is for a customer that is invoiced in a foriegn currency the currency exchange rate can also be specified - it is defaulted based on the current table of exchange rates at the time the contract is created.
-<br><br>
+<br /><br />
There are two buttons on the contract setup page that allow the stock required for the contract to be specified and the requirments that are not stock items to be recorded.
-<br><br>
+<br /><br />
Entering the bill of materials for the contract is done from a screen that shows a stock selection options - it is possible to choose by stock category or search for individual items by code or description. The list of items matching the criteria entered displays and the quantity of each item required should be entered in the box next to the item. There is no limit to how many items can be selected. Once all the items from stock have been selected there is a button that brings back the contract details (Back to Contract Header). The contract screen will now show the bill of materials as selected and the cost of each together with the quantity of each required extending to the total value of all stock items required for the contract.
-<br><br>
+<br /><br />
Entering the other requirements is more straightforward as a new screen allows entry of descriptions of the other items required, the quantity of the item and the cost per unit of the items. Again, a button to go back to the contract header allows the user to switch back to the contract definition screen which will now show the other requirements listed and extended to arrive at the total cost.
-<br><br>
+<br /><br />
The sum of the cost of the bill of materials together with the total cost of the other requirements is shown as the total contract cost. This cost is used together with the GP % entered to work out the total contract cost. The GP% is the % of the total contract price that is profit - so 1 minus the GP% is % of the total contract price that is the cost. The calculation is therefore - contract total cost divided by (1 - the GP%).
-<br><br>
+<br /><br />
<font size="+1"><b>Selecting A Contract</b></font>
-<br><br>
+<br /><br />
From the Contracts tab of the main menu, Select Contract allows contracts for a specific customer to be selected, or contracts of a specific status. Contracts can have a status of:
<ul>
<li>Setup and defining requirements</li>
@@ -46,24 +46,63 @@
<li>Closed - the contract has been completed and finished - the contract work order is closed so no more stock can be issued to it and no more charges can be made to it. through accounts payable</li>
</ul>
The contracts meeting the criteria specified are displayed with links to perform actions depending on its status. If the contract is quoted already there is a link to select the quotation for printing. If the quotation is ordered then there is a link to issue items to the contract work order. In all cases a link to open the contract definition is available. However, the option to modify the contract definition is disabled once the contract has been ordered by the customer. The contract definition can be modified until the contract quotation is converted to an order. This is done in the ususal way - selecting the quotation then changing the quotation flag from quote to order. When the changes are committed the contract work order is created and the requirements for the work order from the contract bill of materials are copied to a normal manufacturing bill of materials. It is not necessary to venture into the manufacturing functionality of webERP as all this is handled within the contract. Only the work order issues screen which comes up directly from the link on the contract selection screen once the contract is converted to a sales order.
-<br><br>
+<br /><br />
When the contract has been ordered by the customer a link is available to show the actual contract cost in comparison to the originally estimated costs. This screen shows the originally costed components and the other requirements costed into the total contract cost on the left side of the screen. On the right the actual inventory issued to the contract and the actual other costs entered through the supplier invoice entry screen.
-<br><br>
+<br /><br />
<font size="+1"><b>Entering Contract Costs</b></font>
-<br><br>
+<br /><br />
The act of issuing stock items to the contract work order, puts the cost of those items as contract costs. Issues to contract work orders is the same as issuing stock to any other work order. See work orders/manufacturing manual. A link to enter the inventory issued against the contract is provided from the contract selection screen. The general ledger entries created when stock is issued to a contract work order are to debit the work in progress account (from the stock category record of the contract item) and credit stock (from the stock account of the stock category record of the item being issued).
-<br><br>
+<br /><br />
Other contract costs are entered at the time of entering AP invoices or credit notes. There is an option on this screen to enter against a contract - in a similar way to entry against a shipment. It is possible to enter a supplier invoice against any number of contracts. The amount of the supplier invoice (or credit note) that is entered against contracts is posted in the general ledger to work in progress. Contract charges records are also created referring to the supplier invoice. To reverse contract charges, supplier credit notes have the exact opposite entries to supplier invoices.
-<br><br>
+<br /><br />
<font size="+1"><b>Closing Contracts</b></font>
-<br><br>
+<br /><br />
Open contracts continue to show on the contract selection screen until they are closed. When entering supplier invoices and credits they show in the drop down list as options for issuing costs against until they are closed. Open contracts also have entries created in the general ledger for work in progress for all the stock issued to them and other requirements charged against them through accounts payable. When the contract item is invoiced to the customer the stock is reduced by the costed amount of the contract and cost of sales is charged with this amount. This value may not actually be the final cost of the contract and the difference between the actual contract cost and the costed contract cost needs to be processed to usage variances in the general ledger, this is what closing the contract does.
-<br><br>
+<br /><br />
The process of closing the contract, compares the cost of the contract as invoiced to the customer against the costs issued to the contract (in work in progress) and creates a general ledger journal to the usage variance account (from the stock category record of the contract item). If the contract item is already invoiced to the customer and the contract work order as showing that the contract item has not yet been received against the work order then the work order receipt is processed. This receives a finished contract items against the contract work order. This process creates the general ledger postings to Debit the stock account (from the stock category record of the contract item) and credit the work in progress account. The amount of this journal is based on the original contract cost.
-<br><br>
+<br /><br />
At the end of the contract closing process, the contract work order has the contract item received against it and the work order is then closed. In addition the work in progress account is cleared so that all entries for issues of stock and other costs to the contract are contra'd by the receipt of the contract item and any variance posting.
-<br><br>
+<br /><br />
Using the contract closing option from the Contract Costing screen thus avoids any requirement to venture into the manufacturing module at all. Since, (if it has not been done through the manufacturing module - which is checked first) the finished contract item is received against the work order and the contract work order is closed. The status of the contract is also updated to closed.
-<br><br>
+<br /><br />
Once a contract is closed it is no longer possible to issue costs against it either in the form of inventory or other charges. However, it is still possible to inspect the original contract costing and the actual costs that were issued against it. This is done from the contract selection screen - where completed contracts can be specified - the link to the contract costing will show.
+<br /><br />
+<font size="+1"><b>Contract Process Flow Summary</b></font>
+<br /><br />
+The process with contracts is as follows:
+<ul>
+<li>1. Discussion with customer</li>
+<li>2. Create contract costing - with all requirements, both external costs and stock required</li>
+<li>3. Produce the quotation for customer based on the contract costing created</li>
+<li>4. If the quotation is accepted by the customer turn the quotation to a sales order - this initates the contract costing</li>
+<li>5. Issue stock to the contract</li>
+<li>6. Enter supplier invoices against the contract</li>
+<li>7. When the contract has been delivered to the customer, recieve the contract item against the contract work order. If the contract is closed through the contract costing screen, this step happens automatically.</li>
+<li>8. Invoice the contract item to the customer</li>
+<li>9. Complete the contract costing - to take any variances and clear the work in progress account where the variances sit until the contract is closed</li>
+</ul>
+<br /><br />
+<font size="+1"><b>Contract Costing General Ledger Impact Summary</b></font>
+<br /><br />
+When cost is allocated from a supplier invoice, the cost is debited to the work in progress account of the stock category of the contract - credit to creditors control.
+<br /><br />
+When the contract item is received against the contract works order, the entry is :
+DR stock
+<br />CR WIP
+<br />based on the stock category of the contract.
+<br /><br />
+When the contract item is sold then it is like selling any other item
+DR cost of sales - from the COGS GL posting table
+<br />CR stock - from the stock category of the contract item
+<br /><br />
+When you issue stock to a contract the entries are:
+<br /><br />
+DR WIP - from the stock category of the contract item
+<br />CR stock - from the stock category of the issued items
+<br /><br />
+When you close a contract the variance against the consted contract is taken to account - the entries are:
+<br /><br />
+DR/CR WIP of the stock category of the contract item - to clear WIP in relation to the
+<br />DR/CR usage variance of the stock category of the contract item
+
<!-- Help End: Contracts -->
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dai...@us...> - 2011-03-13 08:28:51
|
Revision: 4509
http://web-erp.svn.sourceforge.net/web-erp/?rev=4509&view=rev
Author: daintree
Date: 2011-03-13 08:28:44 +0000 (Sun, 13 Mar 2011)
Log Message:
-----------
add to contract manual
Modified Paths:
--------------
trunk/doc/Change.log.html
trunk/doc/Manual/ManualContracts.html
Modified: trunk/doc/Change.log.html
===================================================================
--- trunk/doc/Change.log.html 2011-03-13 04:55:32 UTC (rev 4508)
+++ trunk/doc/Change.log.html 2011-03-13 08:28:44 UTC (rev 4509)
@@ -1,5 +1,6 @@
<p><font SIZE=4 COLOR=BLUE><b>webERP Change Log</b></font></p>
<p>
+<p>12/3/11: Tim Now allow space in codes </p>
<p>12/3/11: SelectSalesOrder.php now allows any number of sales orders to be selected and purchase orders placed for the aggregate of items on the selected sales orders</p>
<p>12/3/11: SuppPriceList.php removed a round trip to DB to get currency - fixed function to get pdf to new TCPDF Output </p>
<p>12/3/11: Exson fix all htmlentities to use ENTQUOTES, 'UTF-8' option so other character sets work with it</p>
Modified: trunk/doc/Manual/ManualContracts.html
===================================================================
--- trunk/doc/Manual/ManualContracts.html 2011-03-13 04:55:32 UTC (rev 4508)
+++ trunk/doc/Manual/ManualContracts.html 2011-03-13 08:28:44 UTC (rev 4509)
@@ -1,43 +1,43 @@
<!-- Help Begin: Contracts -->
-<br><br>
+<br /><br />
<a name="Contracts"><font size="+3"><b>Contract Costing</b></font></a>
-<br><br>
+<br /><br />
<font size="+1"><b>Overview</b></font>
-<br><br>
+<br /><br />
The Contracts module allows for construction of costings for specific customer projects where a bill of materials to be taken from inventory for the contract can be defined, together with a costed list of other requirements. By entering a gross profit percentage figure a price can then be arrived at to charge the customer. The contract can then be converted to a quotation. While the contract is at the quotation stage it is possible to modify the stock components and other requirements - the quotation will be updated with the new costing on commital. The quotation can then be resubmitted to the customer.
-<br><br>
+<br /><br />
When a contract is converted to a quotation the system actually creates a manuafactured inventory item with the name of the contract refence and with the description from the contract description.
-<br><br>
+<br /><br />
When (if) the quotation is accepted by the customer, the quotation can be converted to an order in the usual way by modifying the quotation flag from quotation to order. Committing this change then changes the status of the contract to ordered so that changes are no longer allowed. This process also creates a work order so that stock required for the contract can be issued to it. By using the work order issue functionality the stock is reduced and work in progress is increased.
-<br><br>
+<br /><br />
When supplier invoices (accounts payable) are entered there is the option to specify the contract that is to be charged with the cost. The cost of contract charges also goes to the work in progress account (as determined from the stock category record of the contract). Any number of contract charges can be entered against a supplier invoice (or credit note). In entering contract charges there is also the possibility of flagging whether or not the charge was orignially envisaged and costed into the contract or not. Contract charges records are created for each entry.
-<br><br>
+<br /><br />
The original contract costing can be compared against the actual charges against the contract, to see how much was made on the contract. When all charges are entered against the contract it needs the status of the contract to be changed to complete. This process closes the work order and compares the original contract cost against actual costs and takes the value not charged to cost of sales to the usage variances account (based on the stock category of the contract item) and clears the balance that would otherwise be left in work in progress.
-<br><br>
+<br /><br />
<font size="+1"><b>Creating a New Contract</b></font>
-<br><br>
+<br /><br />
From the contract tab of the main menu, select Create Contract. The first step is to select the customer for whom the contract is for.
-<br><br>
+<br /><br />
The contract requires a reference up to 20 characters - without spaces, slashes or inverted commas - that will be used for the contract code. It must be unique from other contracts and also from any existing inventory item codes already in the system. A description of the contract is also required. The description can be any length and is a text field but will be truncated in the stockmaster to X characters when the contract is converted to a quotation. The description in the contract record is retained.
-<br><br>
+<br /><br />
Each contract must also specify the category - the existing inventory categories are displayed to select from but new categories can be created. It is important to realise that the posting for the general ledger is performed based on the general ledger codes set up against the inventory category selected. e.g. charges against the contract will be posted to the work in progress account against this inventory category and the usage variance account of this category will be used for any difference between the contract total cost and the original costing.
-<br><br>
+<br /><br />
The gross profit percentage entered is the factor used based on the cost to arrive at the contract price.
-<br><br>
+<br /><br />
The date that the customer requires the contract to be completed is also specified in the contract. This propogates through to the quotation and order.
-<br><br>
+<br /><br />
If the contract is for a customer that is invoiced in a foriegn currency the currency exchange rate can also be specified - it is defaulted based on the current table of exchange rates at the time the contract is created.
-<br><br>
+<br /><br />
There are two buttons on the contract setup page that allow the stock required for the contract to be specified and the requirments that are not stock items to be recorded.
-<br><br>
+<br /><br />
Entering the bill of materials for the contract is done from a screen that shows a stock selection options - it is possible to choose by stock category or search for individual items by code or description. The list of items matching the criteria entered displays and the quantity of each item required should be entered in the box next to the item. There is no limit to how many items can be selected. Once all the items from stock have been selected there is a button that brings back the contract details (Back to Contract Header). The contract screen will now show the bill of materials as selected and the cost of each together with the quantity of each required extending to the total value of all stock items required for the contract.
-<br><br>
+<br /><br />
Entering the other requirements is more straightforward as a new screen allows entry of descriptions of the other items required, the quantity of the item and the cost per unit of the items. Again, a button to go back to the contract header allows the user to switch back to the contract definition screen which will now show the other requirements listed and extended to arrive at the total cost.
-<br><br>
+<br /><br />
The sum of the cost of the bill of materials together with the total cost of the other requirements is shown as the total contract cost. This cost is used together with the GP % entered to work out the total contract cost. The GP% is the % of the total contract price that is profit - so 1 minus the GP% is % of the total contract price that is the cost. The calculation is therefore - contract total cost divided by (1 - the GP%).
-<br><br>
+<br /><br />
<font size="+1"><b>Selecting A Contract</b></font>
-<br><br>
+<br /><br />
From the Contracts tab of the main menu, Select Contract allows contracts for a specific customer to be selected, or contracts of a specific status. Contracts can have a status of:
<ul>
<li>Setup and defining requirements</li>
@@ -46,24 +46,63 @@
<li>Closed - the contract has been completed and finished - the contract work order is closed so no more stock can be issued to it and no more charges can be made to it. through accounts payable</li>
</ul>
The contracts meeting the criteria specified are displayed with links to perform actions depending on its status. If the contract is quoted already there is a link to select the quotation for printing. If the quotation is ordered then there is a link to issue items to the contract work order. In all cases a link to open the contract definition is available. However, the option to modify the contract definition is disabled once the contract has been ordered by the customer. The contract definition can be modified until the contract quotation is converted to an order. This is done in the ususal way - selecting the quotation then changing the quotation flag from quote to order. When the changes are committed the contract work order is created and the requirements for the work order from the contract bill of materials are copied to a normal manufacturing bill of materials. It is not necessary to venture into the manufacturing functionality of webERP as all this is handled within the contract. Only the work order issues screen which comes up directly from the link on the contract selection screen once the contract is converted to a sales order.
-<br><br>
+<br /><br />
When the contract has been ordered by the customer a link is available to show the actual contract cost in comparison to the originally estimated costs. This screen shows the originally costed components and the other requirements costed into the total contract cost on the left side of the screen. On the right the actual inventory issued to the contract and the actual other costs entered through the supplier invoice entry screen.
-<br><br>
+<br /><br />
<font size="+1"><b>Entering Contract Costs</b></font>
-<br><br>
+<br /><br />
The act of issuing stock items to the contract work order, puts the cost of those items as contract costs. Issues to contract work orders is the same as issuing stock to any other work order. See work orders/manufacturing manual. A link to enter the inventory issued against the contract is provided from the contract selection screen. The general ledger entries created when stock is issued to a contract work order are to debit the work in progress account (from the stock category record of the contract item) and credit stock (from the stock account of the stock category record of the item being issued).
-<br><br>
+<br /><br />
Other contract costs are entered at the time of entering AP invoices or credit notes. There is an option on this screen to enter against a contract - in a similar way to entry against a shipment. It is possible to enter a supplier invoice against any number of contracts. The amount of the supplier invoice (or credit note) that is entered against contracts is posted in the general ledger to work in progress. Contract charges records are also created referring to the supplier invoice. To reverse contract charges, supplier credit notes have the exact opposite entries to supplier invoices.
-<br><br>
+<br /><br />
<font size="+1"><b>Closing Contracts</b></font>
-<br><br>
+<br /><br />
Open contracts continue to show on the contract selection screen until they are closed. When entering supplier invoices and credits they show in the drop down list as options for issuing costs against until they are closed. Open contracts also have entries created in the general ledger for work in progress for all the stock issued to them and other requirements charged against them through accounts payable. When the contract item is invoiced to the customer the stock is reduced by the costed amount of the contract and cost of sales is charged with this amount. This value may not actually be the final cost of the contract and the difference between the actual contract cost and the costed contract cost needs to be processed to usage variances in the general ledger, this is what closing the contract does.
-<br><br>
+<br /><br />
The process of closing the contract, compares the cost of the contract as invoiced to the customer against the costs issued to the contract (in work in progress) and creates a general ledger journal to the usage variance account (from the stock category record of the contract item). If the contract item is already invoiced to the customer and the contract work order as showing that the contract item has not yet been received against the work order then the work order receipt is processed. This receives a finished contract items against the contract work order. This process creates the general ledger postings to Debit the stock account (from the stock category record of the contract item) and credit the work in progress account. The amount of this journal is based on the original contract cost.
-<br><br>
+<br /><br />
At the end of the contract closing process, the contract work order has the contract item received against it and the work order is then closed. In addition the work in progress account is cleared so that all entries for issues of stock and other costs to the contract are contra'd by the receipt of the contract item and any variance posting.
-<br><br>
+<br /><br />
Using the contract closing option from the Contract Costing screen thus avoids any requirement to venture into the manufacturing module at all. Since, (if it has not been done through the manufacturing module - which is checked first) the finished contract item is received against the work order and the contract work order is closed. The status of the contract is also updated to closed.
-<br><br>
+<br /><br />
Once a contract is closed it is no longer possible to issue costs against it either in the form of inventory or other charges. However, it is still possible to inspect the original contract costing and the actual costs that were issued against it. This is done from the contract selection screen - where completed contracts can be specified - the link to the contract costing will show.
+<br /><br />
+<font size="+1"><b>Contract Process Flow Summary</b></font>
+<br /><br />
+The process with contracts is as follows:
+<ul>
+<li>1. Discussion with customer</li>
+<li>2. Create contract costing - with all requirements, both external costs and stock required</li>
+<li>3. Produce the quotation for customer based on the contract costing created</li>
+<li>4. If the quotation is accepted by the customer turn the quotation to a sales order - this initates the contract costing</li>
+<li>5. Issue stock to the contract</li>
+<li>6. Enter supplier invoices against the contract</li>
+<li>7. When the contract has been delivered to the customer, recieve the contract item against the contract work order. If the contract is closed through the contract costing screen, this step happens automatically.</li>
+<li>8. Invoice the contract item to the customer</li>
+<li>9. Complete the contract costing - to take any variances and clear the work in progress account where the variances sit until the contract is closed</li>
+</ul>
+<br /><br />
+<font size="+1"><b>Contract Costing General Ledger Impact Summary</b></font>
+<br /><br />
+When cost is allocated from a supplier invoice, the cost is debited to the work in progress account of the stock category of the contract - credit to creditors control.
+<br /><br />
+When the contract item is received against the contract works order, the entry is :
+DR stock
+<br />CR WIP
+<br />based on the stock category of the contract.
+<br /><br />
+When the contract item is sold then it is like selling any other item
+DR cost of sales - from the COGS GL posting table
+<br />CR stock - from the stock category of the contract item
+<br /><br />
+When you issue stock to a contract the entries are:
+<br /><br />
+DR WIP - from the stock category of the contract item
+<br />CR stock - from the stock category of the issued items
+<br /><br />
+When you close a contract the variance against the consted contract is taken to account - the entries are:
+<br /><br />
+DR/CR WIP of the stock category of the contract item - to clear WIP in relation to the
+<br />DR/CR usage variance of the stock category of the contract item
+
<!-- Help End: Contracts -->
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dai...@us...> - 2012-02-04 06:22:00
|
Revision: 4867
http://web-erp.svn.sourceforge.net/web-erp/?rev=4867&view=rev
Author: daintree
Date: 2012-02-04 06:21:54 +0000 (Sat, 04 Feb 2012)
Log Message:
-----------
start on intro to the API
Modified Paths:
--------------
trunk/doc/Change.log
Added Paths:
-----------
trunk/doc/Manual/ManualAPITutorial.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2012-02-04 06:13:15 UTC (rev 4866)
+++ trunk/doc/Change.log 2012-02-04 06:21:54 UTC (rev 4867)
@@ -1,5 +1,6 @@
webERP Change Log
+4/2/12 Phil: Added new API function CreateCreditNote in api_debtortransactions.php
3/2/12 Vitaly:Fixed bug that was not allowing PO lines to be deleted in OrderValue method of PO class was testing using asignment operator not comparison operator
31/1/12 Vitaly: Added DB_escape_string before ItemDescription and SupplierName in GoodsReceived.php to prevent problems with '.
31/1/12 Phil: Stocks.php error on changing a stock category the journal between the stock GL accounts was not working because $NewStockAccount should have been $NewStockAct
Added: trunk/doc/Manual/ManualAPITutorial.html
===================================================================
--- trunk/doc/Manual/ManualAPITutorial.html (rev 0)
+++ trunk/doc/Manual/ManualAPITutorial.html 2012-02-04 06:21:54 UTC (rev 4867)
@@ -0,0 +1,84 @@
+<a name="APITutorial"><font size="+3"><b>Application Programming Interface</b></font></a>
+<br /><br />
+<font size="+2"><b>webERP API - Getting Started</b></font>
+<br /><br />
+The API is an Application Program Interface, that is intended to expose webERP functionality to external programs. There are currently a number of low level functions it exposes to enable external applications to retrieve webERP data and to update or insert webERP data. Unfortunately, some of these functions have the potential to upset the data integrity of webERP so they must be used with great caution.
+<br /><br />
+The API in webERP uses XML-RPC in particular the phpxmlrpc class from Useful Inc originally developed by Edd Dumbill
+<br /><br />
+XML-RPC is a protocl to use XML to make RPC - remote procedure calls.
+<br /><br />
+Simply put the XML-RPC call is XML that contains the method of the remote procedure call together with any parameters and their data types and is sent over http as a POST to the XML-RPC server - the server returns an XML payload containing the results of the call. The parameters sent to the methods can contain arrays and associative arrays of data.
+<br /><br />
+The clever thing about XML-RPC is that it is the simplest protocol around for doing web-services. The newer and MUCH more complex SOAP - Simple Object Access Protocol - is quite involved and complicated. webERP is founded on the KISS principle.
+<br /><br />
+In fact the XML-RPC "Server" in webERP is just the script http://www.yourdomain.com/webERP/api/api_xml-rpc.php
+<br /><br />
+There is no daemon background process running continuously to field calls to the "server" it is just a script that is http posted to by the XML-RPC call sending the XML encoded method to be run together with the necessary parameters to the webERP API - the server script runs the API php functions exposed by the xml-rpc methods and returns the XML-RPC response as an XML payload. The phpxmlrpc class does the packaging converting the PHP variables and arrays to the XML required for the XML-RPC call and also has the functions to convert the XML response into something useable in PHP without having to write the XML parsing routines.
+<br /><br />
+It is worthwhile reading a how-to on XML-RPC with PHP which explains in more detail what is going on as a primer for the concepts.
+<br /><br />
+The beauty of XML-RPC is that the client calling the webERP XML-RPC server and performing native webERP functions can be called from any language (with XML-RPC bindings). I have used Vala, Genie and Python. Python particularly has been very straight forward as it has an xmlrpclib bundled with it. Of course a PHP client is also possible and is demonstrated below.
+<br /><br />
+The API help is actually produced by an xml-rpc call to the API using the system.listMethods method (this is a phpxmlrpc method - not a webERP API method). Aother system xml-rpc method of phpxmlrpc class is used to return the details of each method's parameters required. So the help file not only documents each of the API methods it is itself and illustration of how the API can be used!!
+<br /><br />
+Below is a simple example of how to use the API.
+<br /><br />
+<hr />
+<i>
+echo "<html><head>Test webERP API</head><body>";
+<br /><br />
+//the xmlrpc class can output some funny warnings so make sure notices are turned off
+error_reporting (E_ALL & ~E_NOTICE);
+<br /><br />
+/*you need to include the phpxmlrpc class - see link above - copy the whole directory structure of the class over to your client application from the webERP/xmlrpc directory
+*/
+<br /><br />
+include ("xmlrpc/lib/xmlrpc.inc");
+<br /><br />
+//if your webERP install is on a server at http://www.yourdomain.com/webERP
+$ServerURL = "http://www.yourdomain.com/webERP/api/api_xml-rpc.php";
+$DebugLevel = 0; //Set to 0,1, or 2 with 2 being the highest level of debug info
+<br /><br />
+$Parameters = array();
+<br /><br />
+/*The trap for me was that each parameter needs to be run through xmlrpcval() - to create the necessary xml required for the rpc call
+if one of the parameters required is an array then it needs to be processing into xml for the rpc call through php_xmlrpc_encode()*/
+<br /><br />
+$Parameters['StockID'] = xmlrpcval('DVD-TOPGUN'); //the stockid of the item we wish to know the balance for
+//assuming the demo username and password will work !
+$Parameters['Username'] = xmlrpcval('admin');
+$Parameters['Password'] = xmlrpcval('weberp');
+<br /><br />
+$msg = new xmlrpcmsg("weberp.xmlrpc_GetStockBalance", $Parameters);
+<br /><br />
+$client = new xmlrpc_client($ServerURL);
+$client->setDebug($DebugLevel);
+$response = $client->send($msg);
+$answer = php_xmlrpc_decode($response->value());
+if ($answer[0]!=0){ //then the API returned some errors need to figure out what went wrong
+<br /><br />
+//need to figure out how to return all the error descriptions associated with the codes
+<br /><br />
+} else { //all went well the returned data is in $answer[1]
+//answer will be an array of the locations and quantity on hand for DVD_TOPGUN so we need to run through the array to print out
+for ($i=0; $i < sizeof($answer[1]);$i++) {
+ echo '<br>' . $answer[1][$i]['loccode'] . ' has ' . $answer[1][$i]['quantity'] . ' on hand';
+}
+echo "</body></html>";
+</i>
+<hr />
+<br /><br />
+It is necessary to be logged in to see the API functions manual shows all the functions in the API with a description of the parameters required and what each function does.
+<br /><br />
+To create invoices in webERP you need to use the following methods:
+<br /><br />
+InsertOrderHeader
+InsertOrderLine - potentially multiple times for all the lines on the order then
+InvoiceSalesOrder - to invoice sales orders directly assuming the entire order is delivered - it cannot deal with controlled stock items though. However, it does process invoices in much the same way as standard webERP with updates to the stock quantities dispatched, GL entries and records required to record taxes and sales analysis records.
+<br /><br />
+To create a credit note just a sinlge API call is required:
+<br />
+CreateCreditNote - to create a credit note from some base header data and an array of line items (as an associative array. In the same way as the InvoiceSalesOrder function this does all the same processing as a standard credit note from the interface in webERP.
+<br /><br />
+There are some example scripts on the wiki showing how a number of the API XML-RPC functions are called - these scripts should be put on a web-server outside a webERP installation - all you need to do is edit the config.inc file to give the system your webERP username and password and the URL of your webERP installation you wish to connect to. As always playing with the examples helps to figure out how it all works.
\ No newline at end of file
Property changes on: trunk/doc/Manual/ManualAPITutorial.html
___________________________________________________________________
Added: svn:executable
+ *
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dai...@us...> - 2012-02-04 06:22:00
|
Revision: 4867
http://web-erp.svn.sourceforge.net/web-erp/?rev=4867&view=rev
Author: daintree
Date: 2012-02-04 06:21:54 +0000 (Sat, 04 Feb 2012)
Log Message:
-----------
start on intro to the API
Modified Paths:
--------------
trunk/doc/Change.log
Added Paths:
-----------
trunk/doc/Manual/ManualAPITutorial.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2012-02-04 06:13:15 UTC (rev 4866)
+++ trunk/doc/Change.log 2012-02-04 06:21:54 UTC (rev 4867)
@@ -1,5 +1,6 @@
webERP Change Log
+4/2/12 Phil: Added new API function CreateCreditNote in api_debtortransactions.php
3/2/12 Vitaly:Fixed bug that was not allowing PO lines to be deleted in OrderValue method of PO class was testing using asignment operator not comparison operator
31/1/12 Vitaly: Added DB_escape_string before ItemDescription and SupplierName in GoodsReceived.php to prevent problems with '.
31/1/12 Phil: Stocks.php error on changing a stock category the journal between the stock GL accounts was not working because $NewStockAccount should have been $NewStockAct
Added: trunk/doc/Manual/ManualAPITutorial.html
===================================================================
--- trunk/doc/Manual/ManualAPITutorial.html (rev 0)
+++ trunk/doc/Manual/ManualAPITutorial.html 2012-02-04 06:21:54 UTC (rev 4867)
@@ -0,0 +1,84 @@
+<a name="APITutorial"><font size="+3"><b>Application Programming Interface</b></font></a>
+<br /><br />
+<font size="+2"><b>webERP API - Getting Started</b></font>
+<br /><br />
+The API is an Application Program Interface, that is intended to expose webERP functionality to external programs. There are currently a number of low level functions it exposes to enable external applications to retrieve webERP data and to update or insert webERP data. Unfortunately, some of these functions have the potential to upset the data integrity of webERP so they must be used with great caution.
+<br /><br />
+The API in webERP uses XML-RPC in particular the phpxmlrpc class from Useful Inc originally developed by Edd Dumbill
+<br /><br />
+XML-RPC is a protocl to use XML to make RPC - remote procedure calls.
+<br /><br />
+Simply put the XML-RPC call is XML that contains the method of the remote procedure call together with any parameters and their data types and is sent over http as a POST to the XML-RPC server - the server returns an XML payload containing the results of the call. The parameters sent to the methods can contain arrays and associative arrays of data.
+<br /><br />
+The clever thing about XML-RPC is that it is the simplest protocol around for doing web-services. The newer and MUCH more complex SOAP - Simple Object Access Protocol - is quite involved and complicated. webERP is founded on the KISS principle.
+<br /><br />
+In fact the XML-RPC "Server" in webERP is just the script http://www.yourdomain.com/webERP/api/api_xml-rpc.php
+<br /><br />
+There is no daemon background process running continuously to field calls to the "server" it is just a script that is http posted to by the XML-RPC call sending the XML encoded method to be run together with the necessary parameters to the webERP API - the server script runs the API php functions exposed by the xml-rpc methods and returns the XML-RPC response as an XML payload. The phpxmlrpc class does the packaging converting the PHP variables and arrays to the XML required for the XML-RPC call and also has the functions to convert the XML response into something useable in PHP without having to write the XML parsing routines.
+<br /><br />
+It is worthwhile reading a how-to on XML-RPC with PHP which explains in more detail what is going on as a primer for the concepts.
+<br /><br />
+The beauty of XML-RPC is that the client calling the webERP XML-RPC server and performing native webERP functions can be called from any language (with XML-RPC bindings). I have used Vala, Genie and Python. Python particularly has been very straight forward as it has an xmlrpclib bundled with it. Of course a PHP client is also possible and is demonstrated below.
+<br /><br />
+The API help is actually produced by an xml-rpc call to the API using the system.listMethods method (this is a phpxmlrpc method - not a webERP API method). Aother system xml-rpc method of phpxmlrpc class is used to return the details of each method's parameters required. So the help file not only documents each of the API methods it is itself and illustration of how the API can be used!!
+<br /><br />
+Below is a simple example of how to use the API.
+<br /><br />
+<hr />
+<i>
+echo "<html><head>Test webERP API</head><body>";
+<br /><br />
+//the xmlrpc class can output some funny warnings so make sure notices are turned off
+error_reporting (E_ALL & ~E_NOTICE);
+<br /><br />
+/*you need to include the phpxmlrpc class - see link above - copy the whole directory structure of the class over to your client application from the webERP/xmlrpc directory
+*/
+<br /><br />
+include ("xmlrpc/lib/xmlrpc.inc");
+<br /><br />
+//if your webERP install is on a server at http://www.yourdomain.com/webERP
+$ServerURL = "http://www.yourdomain.com/webERP/api/api_xml-rpc.php";
+$DebugLevel = 0; //Set to 0,1, or 2 with 2 being the highest level of debug info
+<br /><br />
+$Parameters = array();
+<br /><br />
+/*The trap for me was that each parameter needs to be run through xmlrpcval() - to create the necessary xml required for the rpc call
+if one of the parameters required is an array then it needs to be processing into xml for the rpc call through php_xmlrpc_encode()*/
+<br /><br />
+$Parameters['StockID'] = xmlrpcval('DVD-TOPGUN'); //the stockid of the item we wish to know the balance for
+//assuming the demo username and password will work !
+$Parameters['Username'] = xmlrpcval('admin');
+$Parameters['Password'] = xmlrpcval('weberp');
+<br /><br />
+$msg = new xmlrpcmsg("weberp.xmlrpc_GetStockBalance", $Parameters);
+<br /><br />
+$client = new xmlrpc_client($ServerURL);
+$client->setDebug($DebugLevel);
+$response = $client->send($msg);
+$answer = php_xmlrpc_decode($response->value());
+if ($answer[0]!=0){ //then the API returned some errors need to figure out what went wrong
+<br /><br />
+//need to figure out how to return all the error descriptions associated with the codes
+<br /><br />
+} else { //all went well the returned data is in $answer[1]
+//answer will be an array of the locations and quantity on hand for DVD_TOPGUN so we need to run through the array to print out
+for ($i=0; $i < sizeof($answer[1]);$i++) {
+ echo '<br>' . $answer[1][$i]['loccode'] . ' has ' . $answer[1][$i]['quantity'] . ' on hand';
+}
+echo "</body></html>";
+</i>
+<hr />
+<br /><br />
+It is necessary to be logged in to see the API functions manual shows all the functions in the API with a description of the parameters required and what each function does.
+<br /><br />
+To create invoices in webERP you need to use the following methods:
+<br /><br />
+InsertOrderHeader
+InsertOrderLine - potentially multiple times for all the lines on the order then
+InvoiceSalesOrder - to invoice sales orders directly assuming the entire order is delivered - it cannot deal with controlled stock items though. However, it does process invoices in much the same way as standard webERP with updates to the stock quantities dispatched, GL entries and records required to record taxes and sales analysis records.
+<br /><br />
+To create a credit note just a sinlge API call is required:
+<br />
+CreateCreditNote - to create a credit note from some base header data and an array of line items (as an associative array. In the same way as the InvoiceSalesOrder function this does all the same processing as a standard credit note from the interface in webERP.
+<br /><br />
+There are some example scripts on the wiki showing how a number of the API XML-RPC functions are called - these scripts should be put on a web-server outside a webERP installation - all you need to do is edit the config.inc file to give the system your webERP username and password and the URL of your webERP installation you wish to connect to. As always playing with the examples helps to figure out how it all works.
\ No newline at end of file
Property changes on: trunk/doc/Manual/ManualAPITutorial.html
___________________________________________________________________
Added: svn:executable
+ *
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <tim...@us...> - 2012-02-06 14:57:13
|
Revision: 4877
http://web-erp.svn.sourceforge.net/web-erp/?rev=4877&view=rev
Author: tim_schofield
Date: 2012-02-06 14:57:06 +0000 (Mon, 06 Feb 2012)
Log Message:
-----------
Removed FUD as new functions seem consistent with the rest of the API
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualAPITutorial.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2012-02-06 06:47:35 UTC (rev 4876)
+++ trunk/doc/Change.log 2012-02-06 14:57:06 UTC (rev 4877)
@@ -1,5 +1,6 @@
webERP Change Log
+6/2/12 Tim: Removed FUD as new API functions seem consistent with the rest of the API</p>
6/2/12 Phil: Added new API function InsertDebtorReceipt in api_debtortransactions.php
4/2/12 Vitaly: Fixed addTextWrap() in class.pdf.php. The length of the string was not calculated properly, causing long strings to print beyond the cell boundaries.
4/2/12 Phil: Added new API function CreateCreditNote in api_debtortransactions.php
Modified: trunk/doc/Manual/ManualAPITutorial.html
===================================================================
--- trunk/doc/Manual/ManualAPITutorial.html 2012-02-06 06:47:35 UTC (rev 4876)
+++ trunk/doc/Manual/ManualAPITutorial.html 2012-02-06 14:57:06 UTC (rev 4877)
@@ -2,7 +2,7 @@
<br /><br />
<font size="+2"><b>webERP API - Getting Started</b></font>
<br /><br />
-The API is an Application Program Interface, that is intended to expose webERP functionality to external programs. There are currently a number of low level functions it exposes to enable external applications to retrieve webERP data and to update or insert webERP data. Unfortunately, some of these functions have the potential to upset the data integrity of webERP so they must be used with great caution.
+The API is an Application Program Interface, that is intended to expose webERP functionality to external programs. There are currently a number of low level functions it exposes to enable external applications to retrieve webERP data and to update or insert webERP data.
<br /><br />
The API in webERP uses XML-RPC in particular the phpxmlrpc class from Useful Inc originally developed by Edd Dumbill
<br /><br />
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <tim...@us...> - 2012-02-06 14:57:16
|
Revision: 4877
http://web-erp.svn.sourceforge.net/web-erp/?rev=4877&view=rev
Author: tim_schofield
Date: 2012-02-06 14:57:06 +0000 (Mon, 06 Feb 2012)
Log Message:
-----------
Removed FUD as new functions seem consistent with the rest of the API
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualAPITutorial.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2012-02-06 06:47:35 UTC (rev 4876)
+++ trunk/doc/Change.log 2012-02-06 14:57:06 UTC (rev 4877)
@@ -1,5 +1,6 @@
webERP Change Log
+6/2/12 Tim: Removed FUD as new API functions seem consistent with the rest of the API</p>
6/2/12 Phil: Added new API function InsertDebtorReceipt in api_debtortransactions.php
4/2/12 Vitaly: Fixed addTextWrap() in class.pdf.php. The length of the string was not calculated properly, causing long strings to print beyond the cell boundaries.
4/2/12 Phil: Added new API function CreateCreditNote in api_debtortransactions.php
Modified: trunk/doc/Manual/ManualAPITutorial.html
===================================================================
--- trunk/doc/Manual/ManualAPITutorial.html 2012-02-06 06:47:35 UTC (rev 4876)
+++ trunk/doc/Manual/ManualAPITutorial.html 2012-02-06 14:57:06 UTC (rev 4877)
@@ -2,7 +2,7 @@
<br /><br />
<font size="+2"><b>webERP API - Getting Started</b></font>
<br /><br />
-The API is an Application Program Interface, that is intended to expose webERP functionality to external programs. There are currently a number of low level functions it exposes to enable external applications to retrieve webERP data and to update or insert webERP data. Unfortunately, some of these functions have the potential to upset the data integrity of webERP so they must be used with great caution.
+The API is an Application Program Interface, that is intended to expose webERP functionality to external programs. There are currently a number of low level functions it exposes to enable external applications to retrieve webERP data and to update or insert webERP data.
<br /><br />
The API in webERP uses XML-RPC in particular the phpxmlrpc class from Useful Inc originally developed by Edd Dumbill
<br /><br />
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dai...@us...> - 2012-07-18 09:42:32
|
Revision: 5516
http://web-erp.svn.sourceforge.net/web-erp/?rev=5516&view=rev
Author: daintree
Date: 2012-07-18 09:42:26 +0000 (Wed, 18 Jul 2012)
Log Message:
-----------
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualContributors.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2012-07-18 09:38:51 UTC (rev 5515)
+++ trunk/doc/Change.log 2012-07-18 09:42:26 UTC (rev 5516)
@@ -1,5 +1,6 @@
webERP Change Log
+15/7/12 Gilberto Dos Santos Alves: updated pt_BR.utf8 translation
13/7/12 Tim: Fix up the sql where a field was selected twice
10/7/12 Phil: Made purchase order lines look at the purchasing data lead time and set the delivery date of the line to today + the lead time if this is beyond the delivery date specified in the PO header.
9/7/12 Tim/Ricard: Add Z_ChangeSupplierCode.php
Modified: trunk/doc/Manual/ManualContributors.html
===================================================================
--- trunk/doc/Manual/ManualContributors.html 2012-07-18 09:38:51 UTC (rev 5515)
+++ trunk/doc/Manual/ManualContributors.html 2012-07-18 09:42:26 UTC (rev 5516)
@@ -5,200 +5,202 @@
<table width="100%">
<tr>
- <td width="50%" valign="top"><b>Development (sorted by last name)</b><br>
- <br>
- Nicola Asuni (TCPDF)<br>
- <br>
- Shane Barnaby<br>
- <br>
- Klaus Beucher<br>
- <br>
- Chris Bice<br>
- <br>
- Danie Brink<br>
- <br>
- Daffyd Crosby<br>
- <br>
- Phil Daintree<br>
- <br>
- Murray Dancey<br>
- <br>
- Gilles Deacur<br>
- <br>
- Miguel de Benito Delgado (phplot)<br>
- <br>
- Javier de Lorenzo-Cáceres<br>
- <br>
- Janusz Dobrowolski<br>
- <br>
- Edd Dumbill (phpxmlrpc)<br>
- <br>
- Ahmed Fawzy<br>
- <br>
- Tom Fox<br>
- <br>
- Braian Gomez<br>
- <br>
- Paul Harness<br>
- <br>
- Lindsay Harris<br>
- <br>
- David Hawke<br>
- <br>
- Richard Heyes (html.mime.mail)<br>
- <br>
- High-Tech Bridge SA Security Research Lab<br>
- <br>
- Tomáš Horáček (barcodepack)<br>
- <br>
- Hindra Joshua<br>
- <br>
- Alan Jones<br>
- <br>
- Steve Kaill - bugfixes<br>
- <br>
- Nico Kaiser (php-gettext)<br>
- <br>
- CQZ,KE<br>
- <br>
- Mo Kelly - due dates and customer po by sales order line<br>
- <br>
- Meraj Khattak - database diagram<br>
- <br>
- Steve Kitchen<br>
- <br>
- Ditesh Kumar<br>
- <br>
- Felix Lim<br>
- <br>
- David Luo<br>
- <br>
- Wayne McDougall<br>
- <br>
- Greg Morehead<br>
- <br>
- Clay Mokus<br>
- <br>
- Suren Naidu<br>
- <br>
- Hani Naguib<br>
- <br>
- Harold Naparst<br>
- <br>
- Sherif Omar<br>
- <br>
- Simon Peter Otandeka<br>
- <br>
- Afan Ottenheimer (phplot)<br>
- <br>
- Kunshan-Ouhai<br>
- <br>
- Ricardo Pedroso<br>
- <br>
- Jesse Peterson<br>
- <br>
- Kalmer Piiskop<br>
- <br>
- Olivier Plathey (FPDF - from which TCPDF was derived)<br>
- <br>
- Renier du Plessis<br>
- <br>
- Dave Premo (report writer)<br>
- <br>
- Exson Qu<br>
- <br>
- Pak Ricard<br>
- <br>
- Harald Ringehahn<br>
- <br>
- Gunnar Rikardsson<br>
- <br>
- Scott Rosa<br>
- <br>
- Tim Schofield<br>
- <br>
- Jurgen Schopenhouer<br>
- <br>
- Fred Schuettler (aguapop - theme)<br>
- <br>
- Danilo Segan (php-gettext)<br>
- <br>
- Gjergj Sheldija<br>
- <br>
- Matthew Sibson<br>
- <br>
- Vitaliy Shevkunov<br>
- <br>
- Marcos Skambraks<br>
- <br>
- Jake Stride<br>
- <br>
- Matt Taylor<br>
- <br>
- Paul Thursby<br>
- <br>
- Marcos Garcia Trejo<br>
- <br>
- Mark Yeager (MRP)<br>
- <br>
+ <td width="50%" valign="top"><b>Development (sorted by last name)</b><br />
+ <br />
+ Nicola Asuni (TCPDF)<br />
+ <br />
+ Shane Barnaby<br />
+ <br />
+ Klaus Beucher<br />
+ <br />
+ Chris Bice<br />
+ <br />
+ Danie Brink<br />
+ <br />
+ Daffyd Crosby<br />
+ <br />
+ Phil Daintree<br />
+ <br />
+ Murray Dancey<br />
+ <br />
+ Gilles Deacur<br />
+ <br />
+ Miguel de Benito Delgado (phplot)<br />
+ <br />
+ Javier de Lorenzo-Cáceres<br />
+ <br />
+ Janusz Dobrowolski<br />
+ <br />
+ Edd Dumbill (phpxmlrpc)<br />
+ <br />
+ Ahmed Fawzy<br />
+ <br />
+ Tom Fox<br />
+ <br />
+ Braian Gomez<br />
+ <br />
+ Paul Harness<br />
+ <br />
+ Lindsay Harris<br />
+ <br />
+ David Hawke<br />
+ <br />
+ Richard Heyes (html.mime.mail)<br />
+ <br />
+ High-Tech Bridge SA Security Research Lab<br />
+ <br />
+ Tomáš Horáček (barcodepack)<br />
+ <br />
+ Hindra Joshua<br />
+ <br />
+ Alan Jones<br />
+ <br />
+ Steve Kaill - bugfixes<br />
+ <br />
+ Nico Kaiser (php-gettext)<br />
+ <br />
+ CQZ,KE<br />
+ <br />
+ Mo Kelly - due dates and customer po by sales order line<br />
+ <br />
+ Meraj Khattak - database diagram<br />
+ <br />
+ Steve Kitchen<br />
+ <br />
+ Ditesh Kumar<br />
+ <br />
+ Felix Lim<br />
+ <br />
+ David Luo<br />
+ <br />
+ Wayne McDougall<br />
+ <br />
+ Greg Morehead<br />
+ <br />
+ Clay Mokus<br />
+ <br />
+ Suren Naidu<br />
+ <br />
+ Hani Naguib<br />
+ <br />
+ Harold Naparst<br />
+ <br />
+ Sherif Omar<br />
+ <br />
+ Simon Peter Otandeka<br />
+ <br />
+ Afan Ottenheimer (phplot)<br />
+ <br />
+ Kunshan-Ouhai<br />
+ <br />
+ Ricardo Pedroso<br />
+ <br />
+ Jesse Peterson<br />
+ <br />
+ Kalmer Piiskop<br />
+ <br />
+ Olivier Plathey (FPDF - from which TCPDF was derived)<br />
+ <br />
+ Renier du Plessis<br />
+ <br />
+ Dave Premo (report writer)<br />
+ <br />
+ Exson Qu<br />
+ <br />
+ Pak Ricard<br />
+ <br />
+ Harald Ringehahn<br />
+ <br />
+ Gunnar Rikardsson<br />
+ <br />
+ Scott Rosa<br />
+ <br />
+ Tim Schofield<br />
+ <br />
+ Jurgen Schopenhouer<br />
+ <br />
+ Fred Schuettler (aguapop - theme)<br />
+ <br />
+ Danilo Segan (php-gettext)<br />
+ <br />
+ Gjergj Sheldija<br />
+ <br />
+ Matthew Sibson<br />
+ <br />
+ Vitaliy Shevkunov<br />
+ <br />
+ Marcos Skambraks<br />
+ <br />
+ Jake Stride<br />
+ <br />
+ Matt Taylor<br />
+ <br />
+ Paul Thursby<br />
+ <br />
+ Marcos Garcia Trejo<br />
+ <br />
+ Mark Yeager (MRP)<br />
+ <br />
Zhiguo Yuan</td>
- <td valign="top"><b>Translation</b><br>
- <br>
- Billy Chang,劉世琪 - Taiwanese<br>
- <br>
- Csillag Péter Hungarian<br>
- <br>
- Danu Satrio Pratomo Djojosoemarto and his cousin - Indonesian<br>
- <br>
- Janusz Dobrowolski - Polish<br>
- <br>
- James Dupin - French<br>
- <br>
- Matt Elbrecht - Estonian<br>
- <br>
- Igor Felix - Portuguese Brazilian<br>
- <br>
- Karel van der Esch - Dutch<br>
- <br>
- Thiago Figueiredo - Portuguese<br>
- <br>
- Romel Den - Chinese Traditional - UTF-8<br>
- <br>
- Thiago Mansinho de Lima - Portuguese Brazilian<br>
- <br>
- Roberto del Pino - Spanish<br>
- <br>
- Alejandro E Fernández E Spanish (Venezuelan)<br>
- <br>
- Javier de Lorenzo-Cáceres - Spanish<br>
- <br>
- Juan L Grassi - Spanish<br>
- <br>
- Tanya Komarova - Russian<br>
- <br>
- Eddie Molina - Spanish<br>
- <br>
- Exson Qu - Chinese (and Manual)<br>
- <br>
- J. Hernán Ramírez R. - Spanish (Venezuelan)<br>
- <br>
- Harald Ringehahn - German<br>
- <br>
- Manel Sanchez Maulini - Spanish<br>
- <br>
- Melvin Sequera - Spanish<br>
- <br>
- Efren Yevale - Spanish<br>
- <br>
- Carlos F. Castillo - Spanish<br>
- <br>
- Wilson Almeida - Spanish<br>
- <br>
- Carlos Vera - Spanish<br>
- <br>
- Zhiguo Yuan - Chinese<br>
- <br></td>
+ <td valign="top"><b>Translation</b><br />
+ <br />
+ Billy Chang,劉世琪 - Taiwanese<br />
+ <br />
+ Csillag Péter Hungarian<br />
+ <br />
+ Danu Satrio Pratomo Djojosoemarto and his cousin - Indonesian<br />
+ <br />
+ Gilberto Dos Santos Alves - Portuguese (Brazilian)
+ <br />
+ Janusz Dobrowolski - Polish<br />
+ <br />
+ James Dupin - French<br />
+ <br />
+ Matt Elbrecht - Estonian<br />
+ <br />
+ Igor Felix - Portuguese Brazilian<br />
+ <br />
+ Karel van der Esch - Dutch<br />
+ <br />
+ Thiago Figueiredo - Portuguese<br />
+ <br />
+ Romel Den - Chinese Traditional - UTF-8<br />
+ <br />
+ Thiago Mansinho de Lima - Portuguese Brazilian<br />
+ <br />
+ Roberto del Pino - Spanish<br />
+ <br />
+ Alejandro E Fernández E Spanish (Venezuelan)<br />
+ <br />
+ Javier de Lorenzo-Cáceres - Spanish<br />
+ <br />
+ Juan L Grassi - Spanish<br />
+ <br />
+ Tanya Komarova - Russian<br />
+ <br />
+ Eddie Molina - Spanish<br />
+ <br />
+ Exson Qu - Chinese (and Manual)<br />
+ <br />
+ J. Hernán Ramírez R. - Spanish (Venezuelan)<br />
+ <br />
+ Harald Ringehahn - German<br />
+ <br />
+ Manel Sanchez Maulini - Spanish<br />
+ <br />
+ Melvin Sequera - Spanish<br />
+ <br />
+ Efren Yevale - Spanish<br />
+ <br />
+ Carlos F. Castillo - Spanish<br />
+ <br />
+ Wilson Almeida - Spanish<br />
+ <br />
+ Carlos Vera - Spanish<br />
+ <br />
+ Zhiguo Yuan - Chinese<br />
+ <br /></td>
</tr>
</table>
<p>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dai...@us...> - 2012-07-18 09:42:35
|
Revision: 5516
http://web-erp.svn.sourceforge.net/web-erp/?rev=5516&view=rev
Author: daintree
Date: 2012-07-18 09:42:26 +0000 (Wed, 18 Jul 2012)
Log Message:
-----------
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualContributors.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2012-07-18 09:38:51 UTC (rev 5515)
+++ trunk/doc/Change.log 2012-07-18 09:42:26 UTC (rev 5516)
@@ -1,5 +1,6 @@
webERP Change Log
+15/7/12 Gilberto Dos Santos Alves: updated pt_BR.utf8 translation
13/7/12 Tim: Fix up the sql where a field was selected twice
10/7/12 Phil: Made purchase order lines look at the purchasing data lead time and set the delivery date of the line to today + the lead time if this is beyond the delivery date specified in the PO header.
9/7/12 Tim/Ricard: Add Z_ChangeSupplierCode.php
Modified: trunk/doc/Manual/ManualContributors.html
===================================================================
--- trunk/doc/Manual/ManualContributors.html 2012-07-18 09:38:51 UTC (rev 5515)
+++ trunk/doc/Manual/ManualContributors.html 2012-07-18 09:42:26 UTC (rev 5516)
@@ -5,200 +5,202 @@
<table width="100%">
<tr>
- <td width="50%" valign="top"><b>Development (sorted by last name)</b><br>
- <br>
- Nicola Asuni (TCPDF)<br>
- <br>
- Shane Barnaby<br>
- <br>
- Klaus Beucher<br>
- <br>
- Chris Bice<br>
- <br>
- Danie Brink<br>
- <br>
- Daffyd Crosby<br>
- <br>
- Phil Daintree<br>
- <br>
- Murray Dancey<br>
- <br>
- Gilles Deacur<br>
- <br>
- Miguel de Benito Delgado (phplot)<br>
- <br>
- Javier de Lorenzo-Cáceres<br>
- <br>
- Janusz Dobrowolski<br>
- <br>
- Edd Dumbill (phpxmlrpc)<br>
- <br>
- Ahmed Fawzy<br>
- <br>
- Tom Fox<br>
- <br>
- Braian Gomez<br>
- <br>
- Paul Harness<br>
- <br>
- Lindsay Harris<br>
- <br>
- David Hawke<br>
- <br>
- Richard Heyes (html.mime.mail)<br>
- <br>
- High-Tech Bridge SA Security Research Lab<br>
- <br>
- Tomáš Horáček (barcodepack)<br>
- <br>
- Hindra Joshua<br>
- <br>
- Alan Jones<br>
- <br>
- Steve Kaill - bugfixes<br>
- <br>
- Nico Kaiser (php-gettext)<br>
- <br>
- CQZ,KE<br>
- <br>
- Mo Kelly - due dates and customer po by sales order line<br>
- <br>
- Meraj Khattak - database diagram<br>
- <br>
- Steve Kitchen<br>
- <br>
- Ditesh Kumar<br>
- <br>
- Felix Lim<br>
- <br>
- David Luo<br>
- <br>
- Wayne McDougall<br>
- <br>
- Greg Morehead<br>
- <br>
- Clay Mokus<br>
- <br>
- Suren Naidu<br>
- <br>
- Hani Naguib<br>
- <br>
- Harold Naparst<br>
- <br>
- Sherif Omar<br>
- <br>
- Simon Peter Otandeka<br>
- <br>
- Afan Ottenheimer (phplot)<br>
- <br>
- Kunshan-Ouhai<br>
- <br>
- Ricardo Pedroso<br>
- <br>
- Jesse Peterson<br>
- <br>
- Kalmer Piiskop<br>
- <br>
- Olivier Plathey (FPDF - from which TCPDF was derived)<br>
- <br>
- Renier du Plessis<br>
- <br>
- Dave Premo (report writer)<br>
- <br>
- Exson Qu<br>
- <br>
- Pak Ricard<br>
- <br>
- Harald Ringehahn<br>
- <br>
- Gunnar Rikardsson<br>
- <br>
- Scott Rosa<br>
- <br>
- Tim Schofield<br>
- <br>
- Jurgen Schopenhouer<br>
- <br>
- Fred Schuettler (aguapop - theme)<br>
- <br>
- Danilo Segan (php-gettext)<br>
- <br>
- Gjergj Sheldija<br>
- <br>
- Matthew Sibson<br>
- <br>
- Vitaliy Shevkunov<br>
- <br>
- Marcos Skambraks<br>
- <br>
- Jake Stride<br>
- <br>
- Matt Taylor<br>
- <br>
- Paul Thursby<br>
- <br>
- Marcos Garcia Trejo<br>
- <br>
- Mark Yeager (MRP)<br>
- <br>
+ <td width="50%" valign="top"><b>Development (sorted by last name)</b><br />
+ <br />
+ Nicola Asuni (TCPDF)<br />
+ <br />
+ Shane Barnaby<br />
+ <br />
+ Klaus Beucher<br />
+ <br />
+ Chris Bice<br />
+ <br />
+ Danie Brink<br />
+ <br />
+ Daffyd Crosby<br />
+ <br />
+ Phil Daintree<br />
+ <br />
+ Murray Dancey<br />
+ <br />
+ Gilles Deacur<br />
+ <br />
+ Miguel de Benito Delgado (phplot)<br />
+ <br />
+ Javier de Lorenzo-Cáceres<br />
+ <br />
+ Janusz Dobrowolski<br />
+ <br />
+ Edd Dumbill (phpxmlrpc)<br />
+ <br />
+ Ahmed Fawzy<br />
+ <br />
+ Tom Fox<br />
+ <br />
+ Braian Gomez<br />
+ <br />
+ Paul Harness<br />
+ <br />
+ Lindsay Harris<br />
+ <br />
+ David Hawke<br />
+ <br />
+ Richard Heyes (html.mime.mail)<br />
+ <br />
+ High-Tech Bridge SA Security Research Lab<br />
+ <br />
+ Tomáš Horáček (barcodepack)<br />
+ <br />
+ Hindra Joshua<br />
+ <br />
+ Alan Jones<br />
+ <br />
+ Steve Kaill - bugfixes<br />
+ <br />
+ Nico Kaiser (php-gettext)<br />
+ <br />
+ CQZ,KE<br />
+ <br />
+ Mo Kelly - due dates and customer po by sales order line<br />
+ <br />
+ Meraj Khattak - database diagram<br />
+ <br />
+ Steve Kitchen<br />
+ <br />
+ Ditesh Kumar<br />
+ <br />
+ Felix Lim<br />
+ <br />
+ David Luo<br />
+ <br />
+ Wayne McDougall<br />
+ <br />
+ Greg Morehead<br />
+ <br />
+ Clay Mokus<br />
+ <br />
+ Suren Naidu<br />
+ <br />
+ Hani Naguib<br />
+ <br />
+ Harold Naparst<br />
+ <br />
+ Sherif Omar<br />
+ <br />
+ Simon Peter Otandeka<br />
+ <br />
+ Afan Ottenheimer (phplot)<br />
+ <br />
+ Kunshan-Ouhai<br />
+ <br />
+ Ricardo Pedroso<br />
+ <br />
+ Jesse Peterson<br />
+ <br />
+ Kalmer Piiskop<br />
+ <br />
+ Olivier Plathey (FPDF - from which TCPDF was derived)<br />
+ <br />
+ Renier du Plessis<br />
+ <br />
+ Dave Premo (report writer)<br />
+ <br />
+ Exson Qu<br />
+ <br />
+ Pak Ricard<br />
+ <br />
+ Harald Ringehahn<br />
+ <br />
+ Gunnar Rikardsson<br />
+ <br />
+ Scott Rosa<br />
+ <br />
+ Tim Schofield<br />
+ <br />
+ Jurgen Schopenhouer<br />
+ <br />
+ Fred Schuettler (aguapop - theme)<br />
+ <br />
+ Danilo Segan (php-gettext)<br />
+ <br />
+ Gjergj Sheldija<br />
+ <br />
+ Matthew Sibson<br />
+ <br />
+ Vitaliy Shevkunov<br />
+ <br />
+ Marcos Skambraks<br />
+ <br />
+ Jake Stride<br />
+ <br />
+ Matt Taylor<br />
+ <br />
+ Paul Thursby<br />
+ <br />
+ Marcos Garcia Trejo<br />
+ <br />
+ Mark Yeager (MRP)<br />
+ <br />
Zhiguo Yuan</td>
- <td valign="top"><b>Translation</b><br>
- <br>
- Billy Chang,劉世琪 - Taiwanese<br>
- <br>
- Csillag Péter Hungarian<br>
- <br>
- Danu Satrio Pratomo Djojosoemarto and his cousin - Indonesian<br>
- <br>
- Janusz Dobrowolski - Polish<br>
- <br>
- James Dupin - French<br>
- <br>
- Matt Elbrecht - Estonian<br>
- <br>
- Igor Felix - Portuguese Brazilian<br>
- <br>
- Karel van der Esch - Dutch<br>
- <br>
- Thiago Figueiredo - Portuguese<br>
- <br>
- Romel Den - Chinese Traditional - UTF-8<br>
- <br>
- Thiago Mansinho de Lima - Portuguese Brazilian<br>
- <br>
- Roberto del Pino - Spanish<br>
- <br>
- Alejandro E Fernández E Spanish (Venezuelan)<br>
- <br>
- Javier de Lorenzo-Cáceres - Spanish<br>
- <br>
- Juan L Grassi - Spanish<br>
- <br>
- Tanya Komarova - Russian<br>
- <br>
- Eddie Molina - Spanish<br>
- <br>
- Exson Qu - Chinese (and Manual)<br>
- <br>
- J. Hernán Ramírez R. - Spanish (Venezuelan)<br>
- <br>
- Harald Ringehahn - German<br>
- <br>
- Manel Sanchez Maulini - Spanish<br>
- <br>
- Melvin Sequera - Spanish<br>
- <br>
- Efren Yevale - Spanish<br>
- <br>
- Carlos F. Castillo - Spanish<br>
- <br>
- Wilson Almeida - Spanish<br>
- <br>
- Carlos Vera - Spanish<br>
- <br>
- Zhiguo Yuan - Chinese<br>
- <br></td>
+ <td valign="top"><b>Translation</b><br />
+ <br />
+ Billy Chang,劉世琪 - Taiwanese<br />
+ <br />
+ Csillag Péter Hungarian<br />
+ <br />
+ Danu Satrio Pratomo Djojosoemarto and his cousin - Indonesian<br />
+ <br />
+ Gilberto Dos Santos Alves - Portuguese (Brazilian)
+ <br />
+ Janusz Dobrowolski - Polish<br />
+ <br />
+ James Dupin - French<br />
+ <br />
+ Matt Elbrecht - Estonian<br />
+ <br />
+ Igor Felix - Portuguese Brazilian<br />
+ <br />
+ Karel van der Esch - Dutch<br />
+ <br />
+ Thiago Figueiredo - Portuguese<br />
+ <br />
+ Romel Den - Chinese Traditional - UTF-8<br />
+ <br />
+ Thiago Mansinho de Lima - Portuguese Brazilian<br />
+ <br />
+ Roberto del Pino - Spanish<br />
+ <br />
+ Alejandro E Fernández E Spanish (Venezuelan)<br />
+ <br />
+ Javier de Lorenzo-Cáceres - Spanish<br />
+ <br />
+ Juan L Grassi - Spanish<br />
+ <br />
+ Tanya Komarova - Russian<br />
+ <br />
+ Eddie Molina - Spanish<br />
+ <br />
+ Exson Qu - Chinese (and Manual)<br />
+ <br />
+ J. Hernán Ramírez R. - Spanish (Venezuelan)<br />
+ <br />
+ Harald Ringehahn - German<br />
+ <br />
+ Manel Sanchez Maulini - Spanish<br />
+ <br />
+ Melvin Sequera - Spanish<br />
+ <br />
+ Efren Yevale - Spanish<br />
+ <br />
+ Carlos F. Castillo - Spanish<br />
+ <br />
+ Wilson Almeida - Spanish<br />
+ <br />
+ Carlos Vera - Spanish<br />
+ <br />
+ Zhiguo Yuan - Chinese<br />
+ <br /></td>
</tr>
</table>
<p>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
|
From: <dai...@us...> - 2013-05-12 00:55:01
|
Revision: 5931
http://sourceforge.net/p/web-erp/reponame/5931
Author: daintree
Date: 2013-05-12 00:54:58 +0000 (Sun, 12 May 2013)
Log Message:
-----------
Rafael Chacon Spanish translations
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualContributors.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2013-05-12 00:41:11 UTC (rev 5930)
+++ trunk/doc/Change.log 2013-05-12 00:54:58 UTC (rev 5931)
@@ -1,18 +1,21 @@
OwebERP Change Log
-11/5/2013 Exson: Add OffersRecievedResultRecipients group to mailgroups in ugrade4.10-4.11.sql/mysql/upgrade4.10-4.11.sql
-11/5/2013 Exson: Add OffersReceivedRecipients Group, added feature to use mail instead of smtp mail only, fixed the problem that item with single quotation mark cannot be stored and the same date comparison problem.
-11/5/2013 Exson: Add MailSalesReport_csv to scripts and add SalesAnalysisReportRecipients for mailing list in sql/mysql/upgrade4.10-4.11.sql
-11/5/2013 Exson: Make the report can be sent via smtp mail in MailSalesReport_csv.php.
-11/5/2013 Exson: Add Cc and Reply-To feature for mail sent by smtp in DefineTenderClass.php.
-11/5/2013 Exson: Make the offer can be mailed via smtp in DefineOfferClass.php.
-11/5/2013 Exson: Make the tender can be sent by SMTP mail in DefineTenderClass.php.
-10/5/2013 Exson Fixed the Z_CreateCompanyTemplateFile.php to make it workable in windows OS and make it workable via smtp mail.
-10/5/2013 Exson: Fixed the report_runner.php to make it can be sent via smtp.
-10/5/2013 Exson: Modify RecurringSalesOrdersProcess.php to make it can send the order by smtp.
-10/5/2013 Exson Fixed the mail function for PDFChequeListing.php
-10/5/2013 Exson: Add GetMailList function in MiscFunctions.php.
-10/5/2013 Exson: Fixed the unclosed a href tag in MailingGroupMaintenance.php.
-10/5/2013 Exson: Add new feature to main mail list group for mail sending purpose.
+
+
+12/5/13 Rafael Chacón: Spanish translation update
+11/5/13 Exson: Add OffersRecievedResultRecipients group to mailgroups in ugrade4.10-4.11.sql/mysql/upgrade4.10-4.11.sql
+11/5/13 Exson: Add OffersReceivedRecipients Group, added feature to use mail instead of smtp mail only, fixed the problem that item with single quotation mark cannot be stored and the same date comparison problem.
+11/5/13 Exson: Add MailSalesReport_csv to scripts and add SalesAnalysisReportRecipients for mailing list in sql/mysql/upgrade4.10-4.11.sql
+11/5/13 Exson: Make the report can be sent via smtp mail in MailSalesReport_csv.php.
+11/5/13 Exson: Add Cc and Reply-To feature for mail sent by smtp in DefineTenderClass.php.
+11/5/13 Exson: Make the offer can be mailed via smtp in DefineOfferClass.php.
+11/5/13 Exson: Make the tender can be sent by SMTP mail in DefineTenderClass.php.
+10/5/13 Exson Fixed the Z_CreateCompanyTemplateFile.php to make it workable in windows OS and make it workable via smtp mail.
+10/5/13 Exson: Fixed the report_runner.php to make it can be sent via smtp.
+10/5/13 Exson: Modify RecurringSalesOrdersProcess.php to make it can send the order by smtp.
+10/5/13 Exson Fixed the mail function for PDFChequeListing.php
+10/5/13 Exson: Add GetMailList function in MiscFunctions.php.
+10/5/13 Exson: Fixed the unclosed a href tag in MailingGroupMaintenance.php.
+10/5/13 Exson: Add new feature to main mail list group for mail sending purpose.
9/5/13 Exson: Fixed the date hard coded problem in PcAssignCashToTab.php which lead to malfunction for some date format. Report by thumb.
3/5/13 Ricard: new script to change GL account codes Z_ChangeGLAccountCode.php and SQL to upgrade to varchar account codes
2/5/2013 Exson: Fixed strpos error and make the smtp server name more generic when user not use a email address in function of SendmailBySmtp in MiscFunctions.php.
Modified: trunk/doc/Manual/ManualContributors.html
===================================================================
--- trunk/doc/Manual/ManualContributors.html 2013-05-12 00:41:11 UTC (rev 5930)
+++ trunk/doc/Manual/ManualContributors.html 2013-05-12 00:54:58 UTC (rev 5931)
@@ -80,7 +80,7 @@
<br />
David Luo<br />
<br />
- Martha Madjack
+ Martha Madjack<br />
<br />
Wayne McDougall<br />
<br />
@@ -164,6 +164,8 @@
<td valign="top"><b>Translation</b><br />
<br />
+ Rafael Chacón - Spanish<br />
+ <br />
Billy Chang,劉世琪 - Taiwanese<br />
<br />
Csillag Péter Hungarian<br />
|
|
From: <tu...@us...> - 2013-10-19 01:55:16
|
Revision: 6360
http://sourceforge.net/p/web-erp/reponame/6360
Author: turbopt
Date: 2013-10-19 01:55:12 +0000 (Sat, 19 Oct 2013)
Log Message:
-----------
Add bracket to complete closing h3 tag.
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualInventory.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2013-10-18 03:14:14 UTC (rev 6359)
+++ trunk/doc/Change.log 2013-10-19 01:55:12 UTC (rev 6360)
@@ -1,5 +1,6 @@
webERP Change Log
+18/10/13 Paul T: Add bracket to complete closing h3 tag.
15/10/13 Paul T: change variable name from OrderNumber to OrderNo.
11/10/13 Tim: Links for manual internal transfers and supplier payment link to allocations
9/10/13 Exson: commit the fixed "Unable to Locate Purchase Order Number" error when the PO is created by SO interface. Fixed provided by Tim and reported by Merci from webERP forum.
Modified: trunk/doc/Manual/ManualInventory.html
===================================================================
--- trunk/doc/Manual/ManualInventory.html 2013-10-18 03:14:14 UTC (rev 6359)
+++ trunk/doc/Manual/ManualInventory.html 2013-10-19 01:55:12 UTC (rev 6360)
@@ -481,7 +481,7 @@
<ul>
<li>
- <h3><a id="CreateRequest">Create a New Internal Stock Request</a></h3
+ <h3><a id="CreateRequest">Create a New Internal Stock Request</a></h3>
<p>An internal stock request is created in two parts. Firstly the header, which contains the Department that requires the items, the location that you wish the request to be fulfilled from, the date by which you require the items, and any narrative you wish to add to the request.</p>
<p>Secondly the items required are selected and the quantities required are entered.</p>
<p>Once you are happy that you have all the items and quantities enetered, submit the request for authorisation.</p>
|
|
From: <tu...@us...> - 2013-10-19 02:23:57
|
Revision: 6361
http://sourceforge.net/p/web-erp/reponame/6361
Author: turbopt
Date: 2013-10-19 02:23:53 +0000 (Sat, 19 Oct 2013)
Log Message:
-----------
Add missing tr tags, reduced doubled-closing td tags to one, and changed & to & for HTML.
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualSecuritySchema.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2013-10-19 01:55:12 UTC (rev 6360)
+++ trunk/doc/Change.log 2013-10-19 02:23:53 UTC (rev 6361)
@@ -1,7 +1,8 @@
webERP Change Log
-18/10/13 Paul T: Add bracket to complete closing h3 tag.
-15/10/13 Paul T: change variable name from OrderNumber to OrderNo.
+18/10/13 Paul T: ManualSecuritySchema.html, add missing tr tags, reduced doubled-closing td tags to one, and changed & to & for HTML.
+18/10/13 Paul T: ManualInventory.html, add bracket to complete closing h3 tag.
+15/10/13 Paul T: GoodsReceived.php, change variable name from OrderNumber to OrderNo.
11/10/13 Tim: Links for manual internal transfers and supplier payment link to allocations
9/10/13 Exson: commit the fixed "Unable to Locate Purchase Order Number" error when the PO is created by SO interface. Fixed provided by Tim and reported by Merci from webERP forum.
6/10/13 Phil: New script to show a grid of items by preferred supplier for placing purchase orders to the users's default inventory location - orders will be authorised if the user has authority and the auto-authorise config option is enabled.
Modified: trunk/doc/Manual/ManualSecuritySchema.html
===================================================================
--- trunk/doc/Manual/ManualSecuritySchema.html 2013-10-19 01:55:12 UTC (rev 6360)
+++ trunk/doc/Manual/ManualSecuritySchema.html 2013-10-19 02:23:53 UTC (rev 6361)
@@ -1,4 +1,4 @@
-<a id="SecuritySchema"><h1>Security Schema</h1></a>
+<h1><a id="SecuritySchema">Security Schema</a></h1>
<p>
The webERP security scheme consists of the following parts:
</p>
@@ -162,196 +162,193 @@
<h4>Security Tokens: Defaults for webERP version 3.0.5:</h4>
1 - Menu and order entry only<br />
-2 - Inventory, AR & AP inquiries & reports<br />
+2 - Inventory, AR & AP inquiries & reports<br />
3 - AR setup customers, areas, receipts, allocations, credit notes, salesfolk, credit status<br />
-4 - PO Entry, Purchasing data & reorder levels<br />
+4 - PO Entry, Purchasing data & reorder levels<br />
5 - AP Invoice, Credit, Payment entry. Supplier maintenance<br />
6 - Not used<br />
7 - Bank reconciliations<br />
8 - GL Journals, COA, sales/COGS GL postings, terms, cost update, company prefs<br />
9 - Ledger Maintenance and Manufacturing<br />
10 - GL Journals, COA, sales/COGS GL postings, terms, cost update, company prefs<br />
-11 - Pricing & Inventory locations, categories, receiving & adjustments<br />
+11 - Pricing & Inventory locations, categories, receiving & adjustments<br />
12 - No Used<br />
13 - Not Used<br />
14 - Not Used<br />
-15 - User management, System Admin setup & utilities<br />
+15 - User management, System Admin setup & utilities<br />
<h4>PageSecurity values: Defaults for webERP version 3.05:</h4>
<table border="2">
-<tbody><tr><th>Page (script) File Name
-</th><th>PageSecurity value
-</th></tr>
-<tr>
+<tbody>
+<tr><th>Page (script) File Name</th><th>PageSecurity value</th></tr>
+<tr><td>CustomerInquiry.php</td><td>1</td></tr>
+<tr><td>GetStockImage.php</td><td>1</td></tr>
+<tr><td>index.php</td><td>1</td></tr>
+<tr><td>Logout.php</td><td>1</td></tr>
+<tr><td>MailInventoryValuation.php</td><td>1</td></tr>
+<tr><td>PDFStockLocTransfer.php</td><td>1</td></tr>
+<tr><td>PDFStockNegatives.php</td><td>1</td></tr>
+<tr><td>PrintCustTrans.php</td><td>1</td></tr>
+<tr><td>PrintCustTransPortrait.php</td><td>1</td></tr>
+<tr><td>reportwriter/FormMaker.php</td><td>1</td></tr>
+<tr><td>reportwriter/ReportMaker.php</td><td>1</td></tr>
+<tr><td>SelectCompletedOrder.php</td><td>1</td></tr>
+<tr><td>SelectOrderItems.php</td><td>1</td></tr>
+<tr><td>AgedDebtors.php</td><td>2</td></tr>
+<tr><td>AgedSuppliers.php</td><td>2</td></tr>
+<tr><td>BOMInquiry.php</td><td>2</td></tr>
+<tr><td>BOMListing.php</td><td>2</td></tr>
+<tr><td>ConfirmDispatch_Invoice.php</td><td>2</td></tr>
+<tr><td>CustomerTransInquiry.php</td><td>2</td></tr>
+<tr><td>CustWhereAlloc.php</td><td>2</td></tr>
+<tr><td>DebtorsAtPeriodEnd.php</td><td>2</td></tr>
+<tr><td>EmailCustTrans.php</td><td>2</td></tr>
+<tr><td>FTP_RadioBeacon.php</td><td>2</td></tr>
+<tr><td>InventoryPlanning.php</td><td>2</td></tr>
+<tr><td>InventoryValuation.php</td><td>2</td></tr>
+<tr><td>OrderDetails.php</td><td>2</td></tr>
+<tr><td>OutstandingGRNs.php</td><td>2</td></tr>
+<tr><td>PDFCustomerList.php</td><td>2</td></tr>
+<tr><td>PDFLowGP.php</td><td>2</td></tr>
+<tr><td>PDFPriceList.php</td><td>2</td></tr>
+<tr><td>PDFQuotation.php</td><td>2</td></tr>
+<tr><td>PDFStockCheckComparison.php</td><td>2</td></tr>
+<tr><td>PeriodsInquiry.php</td><td>2</td></tr>
+<tr><td>PO_OrderDetails.php</td><td>2</td></tr>
+<tr><td>PO_PDFPurchOrder.php</td><td>2</td></tr>
+<tr><td>PO_SelectOSPurchOrder.php</td><td>2</td></tr>
+<tr><td>PO_SelectPurchOrder.php</td><td>2</td></tr>
+<tr><td>Prices.php</td><td>2</td></tr>
+<tr><td>PrintCustOrder_generic.php</td><td>2</td></tr>
+<tr><td>PrintCustOrder.php</td><td>2</td></tr>
+<tr><td>PrintCustStatements.php</td><td>2</td></tr>
+<tr><td>reportwriter/admin/ReportCreator.php</td><td>2</td></tr>
+<tr><td>SalesAnalReptCols.php</td><td>2</td></tr>
+<tr><td>SalesAnalRepts.php</td><td>2</td></tr>
+<tr><td>SalesAnalysis_UserDefined.php</td><td>2</td></tr>
+<tr><td>SelectCustomer.php</td><td>2</td></tr>
+<tr><td>SelectProduct.php</td><td>2</td></tr>
+<tr><td>SelectRecurringSalesOrder.php</td><td>2</td></tr>
+<tr><td>SelectSalesOrder.php</td><td>2</td></tr>
+<tr><td>SelectSupplier.php</td><td>2</td></tr>
+<tr><td>ShiptsList.php</td><td>2</td></tr>
+<tr><td>StockCheck.php</td><td>2</td></tr>
+<tr><td>StockCostUpdate.php</td><td>2</td></tr>
+<tr><td>StockCounts.php</td><td>2</td></tr>
+<tr><td>StockLocMovements.php</td><td>2</td></tr>
+<tr><td>StockLocStatus.php</td><td>2</td></tr>
+<tr><td>StockMovements.php</td><td>2</td></tr>
+<tr><td>StockQuantityByDate.php</td><td>2</td></tr>
+<tr><td>StockSerialItems.php</td><td>2</td></tr>
+<tr><td>StockStatus.php</td><td>2</td></tr>
+<tr><td>StockUsage.php</td><td>2</td></tr>
+<tr><td>StockUsageGraph.php</td><td>2</td></tr>
+<tr><td>SupplierBalsAtPeriodEnd.php</td><td>2</td></tr>
+<tr><td>SupplierTransInquiry.php</td><td>2</td></tr>
+<tr><td>Tax.php</td><td>2</td></tr>
+<tr><td>WhereUsedInquiry.php</td><td>2</td></tr>
+<tr><td>Z_CheckAllocs.php</td><td>2</td></tr>
+<tr><td>Areas.php</td><td>3</td></tr>
+<tr><td>Credit_Invoice.php</td><td>3</td></tr>
+<tr><td>CreditItemsControlled.php</td><td>3</td></tr>
+<tr><td>CreditStatus.php</td><td>3</td></tr>
+<tr><td>CustomerAllocations.php</td><td>3</td></tr>
+<tr><td>CustomerBranches.php</td><td>3</td></tr>
+<tr><td>CustomerReceipt.php</td><td>3</td></tr>
+<tr><td>Customers.php</td><td>3</td></tr>
+<tr><td>PDFBankingSummary.php</td><td>3</td></tr>
+<tr><td>PDFChequeListing.php</td><td>3</td></tr>
+<tr><td>PDFDeliveryDifferences.php</td><td>3</td></tr>
+<tr><td>PDFDIFOT.php</td><td>3</td></tr>
+<tr><td>PDFOrdersInvoiced.php</td><td>3</td></tr>
+<tr><td>PDFOrderStatus.php</td><td>3</td></tr>
+<tr><td>SalesPeople.php</td><td>3</td></tr>
+<tr><td>SelectCreditItems.php</td><td>3</td></tr>
+<tr><td>StockSerialItemResearch.php</td><td>3</td></tr>
+<tr><td>PO_Header.php</td><td>4</td></tr>
+<tr><td>PO_Items.php</td><td>4</td></tr>
+<tr><td>PurchData.php</td><td>4</td></tr>
+<tr><td>SpecialOrder.php</td><td>4</td></tr>
+<tr><td>StockReorderLevel.php</td><td>4</td></tr>
+<tr><td>Payments.php</td><td>5</td></tr>
+<tr><td>PrintCheque.php</td><td>5</td></tr>
+<tr><td>StockQties_csv.php</td><td>5</td></tr>
+<tr><td>SuppCreditGRNs.php</td><td>5</td></tr>
+<tr><td>SuppInvGRNs.php</td><td>5</td></tr>
+<tr><td>SupplierAllocations.php</td><td>5</td></tr>
+<tr><td>SupplierCredit.php</td><td>5</td></tr>
+<tr><td>SupplierInvoice.php</td><td>5</td></tr>
+<tr><td>Suppliers.php</td><td>5</td></tr>
+<tr><td>SuppPaymentRun.php</td><td>5</td></tr>
+<tr><td>SuppShiptChgs.php</td><td>5</td></tr>
+<tr><td>SuppTransGLAnalysis.php</td><td>5</td></tr>
+<tr><td>SalesGraph.php</td><td>6</td></tr>
+<tr><td>BankMatching.php</td><td>7</td></tr>
+<tr><td>BankReconciliation.php</td><td>7</td></tr>
+<tr><td>GLAccountInquiry.php</td><td>8</td></tr>
+<tr><td>GLBalanceSheet.php</td><td>8</td></tr>
+<tr><td>GLCodesInquiry.php</td><td>8</td></tr>
+<tr><td>GLProfit_Loss.php</td><td>8</td></tr>
+<tr><td>GLTransInquiry.php</td><td>8</td></tr>
+<tr><td>GLTrialBalance.php</td><td>8</td></tr>
+<tr><td>SelectGLAccount.php</td><td>8</td></tr>
+<tr><td>BOMs.php</td><td>9</td></tr>
+<tr><td>Currencies.php</td><td>9</td></tr>
+<tr><td>Z_CreateChartDetails.php</td><td>9</td></tr>
+<tr><td>AccountGroups.php</td><td>10</td></tr>
+<tr><td>AccountSections.php</td><td>10</td></tr>
+<tr><td>BankAccounts.php</td><td>10</td></tr>
+<tr><td>COGSGLPostings.php</td><td>10</td></tr>
+<tr><td>CompanyPreferences.php</td><td>10</td></tr>
+<tr><td>EDIMessageFormat.php</td><td>10</td></tr>
+<tr><td>GLAccounts.php</td><td>10</td></tr>
+<tr><td>GLJournal.php</td><td>10</td></tr>
+<tr><td>PaymentTerms.php</td><td>10</td></tr>
+<tr><td>SalesGLPostings.php</td><td>10</td></tr>
+<tr><td>WorkOrderEntry.php</td><td>10</td></tr>
+<tr><td>WorkOrderIssue.php</td><td>10</td></tr>
+<tr><td>ConfirmDispatchControlled_Invoice.php</td><td>11</td></tr>
+<tr><td>CustEDISetup.php</td><td>11</td></tr>
+<tr><td>DiscountCategories.php</td><td>11</td></tr>
+<tr><td>DiscountMatrix.php</td><td>11</td></tr>
+<tr><td>EDIProcessOrders.php</td><td>11</td></tr>
+<tr><td>FreightCosts.php</td><td>11</td></tr>
+<tr><td>GoodsReceived.php</td><td>11</td></tr>
+<tr><td>GoodsReceivedControlled.php</td><td>11</td></tr>
+<tr><td>Locations.php</td><td>11</td></tr>
+<tr><td>Prices_Customer.php</td><td>11</td></tr>
+<tr><td>ReverseGRN.php</td><td>11</td></tr>
+<tr><td>SalesCategories.php</td><td>11</td></tr>
+<tr><td>ShipmentCosting.php</td><td>11</td></tr>
+<tr><td>Shipments.php</td><td>11</td></tr>
+<tr><td>Shipt_Select.php</td><td>11</td></tr>
+<tr><td>StockAdjustments.php</td><td>11</td></tr>
+<tr><td>StockAdjustmentsControlled.php</td><td>11</td></tr>
+<tr><td>StockCategories.php</td><td>11</td></tr>
+<tr><td>StockLocTransfer.php</td><td>11</td></tr>
+<tr><td>StockLocTransferReceive.php</td><td>11</td></tr>
+<tr><td>Stocks.php</td><td>11</td></tr>
+<tr><td>StockTransferControlled.php</td><td>11</td></tr>
+<tr><td>StockTransfers.php</td><td>11</td></tr>
+<tr><td>TaxAuthorityRates.php</td><td>11</td></tr>
+<tr><td>EDISendInvoices.php</td><td>15</td></tr>
+<tr><td>PaymentMethods.php</td><td>15</td></tr>
+<tr><td>SalesTypes.php</td><td>15</td></tr>
+<tr><td>Shippers.php</td><td>15</td></tr>
+<tr><td>SystemParameters.php</td><td>15</td></tr>
+<tr><td>TaxCategories.php</td><td>15</td></tr>
+<tr><td>TaxProvinces.php</td><td>15</td></tr>
+<tr><td>UnitsOfMeasure.php</td><td>15</td></tr>
+<tr><td>Z_CheckAllocationsFrom.php</td><td>15</td></tr>
+<tr><td>Z_index.php</td><td>15</td></tr>
+<tr><td>Z_MakeNewCompany.php</td><td>15</td></tr>
+<tr><td>Z_poAddLanguage.php</td><td>15</td></tr>
+<tr><td>Z_poAdmin.php</td><td>15</td></tr>
+<tr><td>Z_poEditLangHeader.php</td><td>15</td></tr>
+<tr><td>Z_poEditLangModule.php</td><td>15</td></tr>
+<tr><td>Z_poRebuildDefault.php</td><td>15</td></tr>
+<tr><td>Z_Upgrade_3.01-3.02.php</td><td>15</td></tr>
+<tr><td>Z_Upgrade_3.04-3.05.php</td><td>15</td></tr>
-<td>CustomerInquiry.php</td></td><td>1</td></tr>
-<td>GetStockImage.php</td></td><td>1</td></tr>
-<td>index.php</td></td><td>1</td></tr>
-<td>Logout.php</td></td><td>1</td></tr>
-<td>MailInventoryValuation.php</td></td><td>1</td></tr>
-<td>PDFStockLocTransfer.php</td></td><td>1</td></tr>
-<td>PDFStockNegatives.php</td></td><td>1</td></tr>
-<td>PrintCustTrans.php</td></td><td>1</td></tr>
-<td>PrintCustTransPortrait.php</td></td><td>1</td></tr>
-<td>reportwriter/FormMaker.php</td></td><td>1</td></tr>
-<td>reportwriter/ReportMaker.php</td></td><td>1</td></tr>
-<td>SelectCompletedOrder.php</td></td><td>1</td></tr>
-<td>SelectOrderItems.php</td></td><td>1</td></tr>
-<td>AgedDebtors.php</td></td><td>2</td></tr>
-<td>AgedSuppliers.php</td></td><td>2</td></tr>
-<td>BOMInquiry.php</td></td><td>2</td></tr>
-<td>BOMListing.php</td></td><td>2</td></tr>
-<td>ConfirmDispatch_Invoice.php</td></td><td>2</td></tr>
-<td>CustomerTransInquiry.php</td></td><td>2</td></tr>
-<td>CustWhereAlloc.php</td></td><td>2</td></tr>
-<td>DebtorsAtPeriodEnd.php</td></td><td>2</td></tr>
-<td>EmailCustTrans.php</td></td><td>2</td></tr>
-<td>FTP_RadioBeacon.php</td></td><td>2</td></tr>
-<td>InventoryPlanning.php</td></td><td>2</td></tr>
-<td>InventoryValuation.php</td></td><td>2</td></tr>
-<td>OrderDetails.php</td></td><td>2</td></tr>
-<td>OutstandingGRNs.php</td></td><td>2</td></tr>
-<td>PDFCustomerList.php</td></td><td>2</td></tr>
-<td>PDFLowGP.php</td></td><td>2</td></tr>
-<td>PDFPriceList.php</td></td><td>2</td></tr>
-<td>PDFQuotation.php</td></td><td>2</td></tr>
-<td>PDFStockCheckComparison.php</td></td><td>2</td></tr>
-<td>PeriodsInquiry.php</td></td><td>2</td></tr>
-<td>PO_OrderDetails.php</td></td><td>2</td></tr>
-<td>PO_PDFPurchOrder.php</td></td><td>2</td></tr>
-<td>PO_SelectOSPurchOrder.php</td></td><td>2</td></tr>
-<td>PO_SelectPurchOrder.php</td></td><td>2</td></tr>
-<td>Prices.php</td></td><td>2</td></tr>
-<td>PrintCustOrder_generic.php</td></td><td>2</td></tr>
-<td>PrintCustOrder.php</td></td><td>2</td></tr>
-<td>PrintCustStatements.php</td></td><td>2</td></tr>
-<td>reportwriter/admin/ReportCreator.php</td></td><td>2</td></tr>
-<td>SalesAnalReptCols.php</td></td><td>2</td></tr>
-<td>SalesAnalRepts.php</td></td><td>2</td></tr>
-<td>SalesAnalysis_UserDefined.php</td></td><td>2</td></tr>
-<td>SelectCustomer.php</td></td><td>2</td></tr>
-<td>SelectProduct.php</td></td><td>2</td></tr>
-<td>SelectRecurringSalesOrder.php</td></td><td>2</td></tr>
-<td>SelectSalesOrder.php</td></td><td>2</td></tr>
-<td>SelectSupplier.php</td></td><td>2</td></tr>
-<td>ShiptsList.php</td></td><td>2</td></tr>
-<td>StockCheck.php</td></td><td>2</td></tr>
-<td>StockCostUpdate.php</td></td><td>2</td></tr>
-<td>StockCounts.php</td></td><td>2</td></tr>
-<td>StockLocMovements.php</td></td><td>2</td></tr>
-<td>StockLocStatus.php</td></td><td>2</td></tr>
-<td>StockMovements.php</td></td><td>2</td></tr>
-<td>StockQuantityByDate.php</td></td><td>2</td></tr>
-<td>StockSerialItems.php</td></td><td>2</td></tr>
-<td>StockStatus.php</td></td><td>2</td></tr>
-<td>StockUsage.php</td></td><td>2</td></tr>
-<td>StockUsageGraph.php</td></td><td>2</td></tr>
-<td>SupplierBalsAtPeriodEnd.php</td></td><td>2</td></tr>
-<td>SupplierTransInquiry.php</td></td><td>2</td></tr>
-<td>Tax.php</td></td><td>2</td></tr>
-<td>WhereUsedInquiry.php</td></td><td>2</td></tr>
-<td>Z_CheckAllocs.php</td></td><td>2</td></tr>
-<td>Areas.php</td></td><td>3</td></tr>
-<td>Credit_Invoice.php</td></td><td>3</td></tr>
-<td>CreditItemsControlled.php</td></td><td>3</td></tr>
-<td>CreditStatus.php</td></td><td>3</td></tr>
-<td>CustomerAllocations.php</td></td><td>3</td></tr>
-<td>CustomerBranches.php</td></td><td>3</td></tr>
-<td>CustomerReceipt.php</td></td><td>3</td></tr>
-<td>Customers.php</td></td><td>3</td></tr>
-<td>PDFBankingSummary.php</td></td><td>3</td></tr>
-<td>PDFChequeListing.php</td></td><td>3</td></tr>
-<td>PDFDeliveryDifferences.php</td></td><td>3</td></tr>
-<td>PDFDIFOT.php</td></td><td>3</td></tr>
-<td>PDFOrdersInvoiced.php</td></td><td>3</td></tr>
-<td>PDFOrderStatus.php</td></td><td>3</td></tr>
-<td>SalesPeople.php</td></td><td>3</td></tr>
-<td>SelectCreditItems.php</td></td><td>3</td></tr>
-<td>StockSerialItemResearch.php</td></td><td>3</td></tr>
-<td>PO_Header.php</td></td><td>4</td></tr>
-<td>PO_Items.php</td></td><td>4</td></tr>
-<td>PurchData.php</td></td><td>4</td></tr>
-<td>SpecialOrder.php</td></td><td>4</td></tr>
-<td>StockReorderLevel.php</td></td><td>4</td></tr>
-<td>Payments.php</td></td><td>5</td></tr>
-<td>PrintCheque.php</td></td><td>5</td></tr>
-<td>StockQties_csv.php</td></td><td>5</td></tr>
-<td>SuppCreditGRNs.php</td></td><td>5</td></tr>
-<td>SuppInvGRNs.php</td></td><td>5</td></tr>
-<td>SupplierAllocations.php</td></td><td>5</td></tr>
-<td>SupplierCredit.php</td></td><td>5</td></tr>
-<td>SupplierInvoice.php</td></td><td>5</td></tr>
-<td>Suppliers.php</td></td><td>5</td></tr>
-<td>SuppPaymentRun.php</td></td><td>5</td></tr>
-<td>SuppShiptChgs.php</td></td><td>5</td></tr>
-<td>SuppTransGLAnalysis.php</td></td><td>5</td></tr>
-<td>SalesGraph.php</td></td><td>6</td></tr>
-<td>BankMatching.php</td></td><td>7</td></tr>
-<td>BankReconciliation.php</td></td><td>7</td></tr>
-<td>GLAccountInquiry.php</td></td><td>8</td></tr>
-<td>GLBalanceSheet.php</td></td><td>8</td></tr>
-<td>GLCodesInquiry.php</td></td><td>8</td></tr>
-<td>GLProfit_Loss.php</td></td><td>8</td></tr>
-<td>GLTransInquiry.php</td></td><td>8</td></tr>
-<td>GLTrialBalance.php</td></td><td>8</td></tr>
-<td>SelectGLAccount.php</td></td><td>8</td></tr>
-<td>BOMs.php</td></td><td>9</td></tr>
-<td>Currencies.php</td></td><td>9</td></tr>
-<td>Z_CreateChartDetails.php</td></td><td>9</td></tr>
-<td>AccountGroups.php</td></td><td>10</td></tr>
-<td>AccountSections.php</td></td><td>10</td></tr>
-<td>BankAccounts.php</td></td><td>10</td></tr>
-<td>COGSGLPostings.php</td></td><td>10</td></tr>
-<td>CompanyPreferences.php</td></td><td>10</td></tr>
-<td>EDIMessageFormat.php</td></td><td>10</td></tr>
-<td>GLAccounts.php</td></td><td>10</td></tr>
-<td>GLJournal.php</td></td><td>10</td></tr>
-<td>PaymentTerms.php</td></td><td>10</td></tr>
-<td>SalesGLPostings.php</td></td><td>10</td></tr>
-<td>WorkOrderEntry.php</td></td><td>10</td></tr>
-<td>WorkOrderIssue.php</td></td><td>10</td></tr>
-<td>ConfirmDispatchControlled_Invoice.php</td></td><td>11</td></tr>
-<td>CustEDISetup.php</td></td><td>11</td></tr>
-<td>DiscountCategories.php</td></td><td>11</td></tr>
-<td>DiscountMatrix.php</td></td><td>11</td></tr>
-<td>EDIProcessOrders.php</td></td><td>11</td></tr>
-<td>FreightCosts.php</td></td><td>11</td></tr>
-<td>GoodsReceived.php</td></td><td>11</td></tr>
-<td>GoodsReceivedControlled.php</td></td><td>11</td></tr>
-<td>Locations.php</td></td><td>11</td></tr>
-<td>Prices_Customer.php</td></td><td>11</td></tr>
-<td>ReverseGRN.php</td></td><td>11</td></tr>
-<td>SalesCategories.php</td></td><td>11</td></tr>
-<td>ShipmentCosting.php</td></td><td>11</td></tr>
-<td>Shipments.php</td></td><td>11</td></tr>
-<td>Shipt_Select.php</td></td><td>11</td></tr>
-<td>StockAdjustments.php</td></td><td>11</td></tr>
-<td>StockAdjustmentsControlled.php</td></td><td>11</td></tr>
-<td>StockCategories.php</td></td><td>11</td></tr>
-<td>StockLocTransfer.php</td></td><td>11</td></tr>
-<td>StockLocTransferReceive.php</td></td><td>11</td></tr>
-<td>Stocks.php</td></td><td>11</td></tr>
-<td>StockTransferControlled.php</td></td><td>11</td></tr>
-<td>StockTransfers.php</td></td><td>11</td></tr>
-<td>TaxAuthorityRates.php</td></td><td>11</td></tr>
-<td>EDISendInvoices.php</td></td><td>15</td></tr>
-<td>PaymentMethods.php</td></td><td>15</td></tr>
-<td>SalesTypes.php</td></td><td>15</td></tr>
-<td>Shippers.php</td></td><td>15</td></tr>
-<td>SystemParameters.php</td></td><td>15</td></tr>
-<td>TaxCategories.php</td></td><td>15</td></tr>
-<td>TaxProvinces.php</td></td><td>15</td></tr>
-<td>UnitsOfMeasure.php</td></td><td>15</td></tr>
-<td>Z_CheckAllocationsFrom.php</td></td><td>15</td></tr>
-<td>Z_index.php</td></td><td>15</td></tr>
-<td>Z_MakeNewCompany.php</td></td><td>15</td></tr>
-<td>Z_poAddLanguage.php</td></td><td>15</td></tr>
-<td>Z_poAdmin.php</td></td><td>15</td></tr>
-<td>Z_poEditLangHeader.php</td></td><td>15</td></tr>
-<td>Z_poEditLangModule.php</td></td><td>15</td></tr>
-<td>Z_poRebuildDefault.php</td></td><td>15</td></tr>
-<td>Z_Upgrade_3.01-3.02.php</td></td><td>15</td></tr>
-<td>Z_Upgrade_3.04-3.05.php</td></td><td>15</td></tr>
-
</tbody></table>
|
|
From: <rc...@us...> - 2014-11-29 00:56:02
|
Revision: 7008
http://sourceforge.net/p/web-erp/reponame/7008
Author: rchacon
Date: 2014-11-29 00:55:58 +0000 (Sat, 29 Nov 2014)
Log Message:
-----------
Add Pan Size explanation (thanks to Tim Schofield and Pak Ricard).
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualInventory.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2014-11-25 05:14:06 UTC (rev 7007)
+++ trunk/doc/Change.log 2014-11-29 00:55:58 UTC (rev 7008)
@@ -1,5 +1,6 @@
webERP Change Log
+29/11/14 RChacon: Add Pan Size explanation (thanks to Tim Schofield and Pak Ricard).
24/11/14 RChacon: In PrintCustStatements.php, make translatable the currency name and the transaction type.
24/11/14 RChacon: Spanish translation improvements. Merging "View GL Entries" and "View the GL Entries".
22/11/14 Exson: Fix the qualitytext does not have default value for strict sql mode in Credit_Invoice.php.
Modified: trunk/doc/Manual/ManualInventory.html
===================================================================
--- trunk/doc/Manual/ManualInventory.html 2014-11-25 05:14:06 UTC (rev 7007)
+++ trunk/doc/Manual/ManualInventory.html 2014-11-29 00:55:58 UTC (rev 7008)
@@ -126,7 +126,7 @@
</ul>Entry of the base information is done from the menu, select the inventory tab and click "Add a New Inventory Item".
<p>
- <h3>ItemCode</h3>
+ <h3>Item Code</h3>
<p>A stock code is required for each stock item, this can be any combination of characters up to 20 characters long. The coding structure of stock items should be considered, to ensure that like stock items appear together. Internally the system looks at the code to order stock items in the various look up tables. A systematic approach to naming stock items can save a lot of time later. However, good facilities are available to search. Under supplier purchasing data it is also possible to record the supplier's part number against an item.</p>
@@ -138,16 +138,12 @@
<p>The description translations can be maintained within the same parameters above. The translations that can be maintained are set in the system configuration screen. Any number of translations can be maintained. These translations are used to print on customer invoices if the customer is set up to use one of the languages for which translations are maintained. If not translation is available then the fall back is to the default description.</p>
- <h3>Categories</h3>
+ <h3>Category</h3>
<p>These categories need to be set up first - from the System Setup tab of the menu. In selecting the stock category, be aware that the system uses the category information for analysis and summary reporting as well as identifying accounts for standard cost general ledger integration, if this option is enabled. There is a link to create new stock categories from the stock item entry page.</p>
<p>A stock category is required for all stock items. The stock category is a text field which groups like stock items together. In selecting stock it is often useful to restrict the search to just the category required. A stock category select box shows on the Select Product screen for this purpose.</p>
- <h3>Unit of Measurement</h3>
-
- <p>This field describes how the stock is to be maintained and is self-explanatory. It is a compulsory field. The selection list is maintained in config.php as an array variable. To add or delete other units of measurement the array variable called $InventoryUnits defined in config.php must be edited by the system administrator.</p>
-
<h3>Economic Order Quantity</h3>
<p>This is the quantity that new orders are made or purchased in by default. Currently this is purely for memorandum - in future this will be a critical part of the MRP calculations.</p>
@@ -156,14 +152,20 @@
<p>This field is required for freight calculations. It records the volume of the one of the item as packaged for dispatch. See the section on freight calculations.</p>
- <h3>Packaged Weight</h3>
+ <h3>Packaged Gross Weight</h3>
<p>This field is required for freight calculations. It records the weight of the one of the item as packaged for dispatch. The freight calculation takes the higher of the freight costs based on the total weight of the order and the total volume of the order. Most freight companies use a conversion and charge the higher of the two. See the section on freight calculations.</p>
+ <!--h3>Net Weight</h3>
+
+ <p>...</p-->
+
<h3>Units of Measure</h3>
<p>This field describes how the stock is to be maintained and is self-explanatory. It is a compulsory field, and as such, some values are defined at the time of installation. System administrators may define additional values or modify existing ones via the 'Units of Measure' link found under 'Inventory Setup' on the main 'Setup' page.</p>
+ <p>The selection list is maintained in config.php as an array variable. To add or delete other units of measurement the array variable called $InventoryUnits defined in config.php must be edited by the system administrator.</p>
+
<h3>Current or Obsolete</h3>
<p>If this field is set to obsolete, this indicates that the stock item is no longer used. However, there may be a stock history on invoices and credit notes which are required. The stock item master record is therefore still required. (Deletion is not allowed while stock movements or Sales analysis records exist for the part) However, it will not appear on searches for invoicing, stock items, in addition the item will be flagged as discontinued in stock reports.</p>
@@ -240,6 +242,14 @@
<p>Serialised is a special case of controlled where the batch size is always one. The system will prompt for the serial number of each item of stock being received and stock records will be maintained for all serial numbers separately. Serialised does not have any effect if controlled is not set.</p>
+ <!--h3>Perishable</h3>
+
+ <p>...</p-->
+
+ <h3>Decimal Places for display Quantity</h3>
+
+ <p>Some items of stock require a number of decimal places to be retained and displayed, others do not require any. This field is used throughout the system for invoices, orders and all places where the item quantity is displayed.</p>
+
<h3>Bar Code</h3>
<p>This field is the unique identifying bar code for this item, typically containing the EAN bar code for the item. This field is used in identifying the item in EANCOM edi messages.</p>
@@ -250,11 +260,24 @@
<p>The discount category is a 2 character field and there is no error checking on entries.</p>
- <h3>Decimal Places</h3>
+ <h3>Tax Category</h3>
- <p>Some items of stock require a number of decimal places to be retained and displayed, others do not require any. This field is used throughout the system for invoices, orders and all places where the item quantity is displayed.
+ <!--p>...</p-->
- <h3>Item Properties</h3><!-- Help End: Stocks -->
+ <p>Tax categories are defined by system administrators in Main Menu > Setup > General Setup Options > Tax Category Maintenance.</p>
+
+ <h3>Pan Size</h3>
+
+ <p>This modifier is sometimes called the order multiple. It allows you to create planned orders in even multiples. This is especially useful if you are required by your suppliers to place orders in specific lot sizes. It is also a useful modifier is you have established your own production run sizes. This modifier causes MRP to inflate the required order quantity to an even increment of the pansize value. As with all modifiers you do need to be careful with this modifier as its use could lead to excess inventories.</p>
+
+ <p>In other words if it is most efficient to manufacture an item in batches of 10 then the pan size would be 10, and MRP would calculate demand in batches of 10, so would inflate a demand of 17 to 20.</p>
+
+ <!--h3>Shrinkage Factor</h3>
+
+ <p>Percentage by which an output falls short of the estimated or planned output.</p-->
+
+ <h3>Item Properties</h3>
+<!-- Help End: Stocks -->
<!-- Help Begin: StockCostUpdate -->
<div class="floatright">
|
|
From: <rc...@us...> - 2014-11-29 16:25:17
|
Revision: 7009
http://sourceforge.net/p/web-erp/reponame/7009
Author: rchacon
Date: 2014-11-29 16:25:11 +0000 (Sat, 29 Nov 2014)
Log Message:
-----------
Add Pan Size explanation (thanks to Exson Qu) and other item maintenance explanations.
Modified Paths:
--------------
trunk/doc/Change.log
trunk/doc/Manual/ManualInventory.html
Modified: trunk/doc/Change.log
===================================================================
--- trunk/doc/Change.log 2014-11-29 00:55:58 UTC (rev 7008)
+++ trunk/doc/Change.log 2014-11-29 16:25:11 UTC (rev 7009)
@@ -1,5 +1,6 @@
webERP Change Log
+29/11/14 RChacon: Add Pan Size explanation (thanks to Exson Qu) and other item maintenance explanations.
29/11/14 RChacon: Add Pan Size explanation (thanks to Tim Schofield and Pak Ricard).
24/11/14 RChacon: In PrintCustStatements.php, make translatable the currency name and the transaction type.
24/11/14 RChacon: Spanish translation improvements. Merging "View GL Entries" and "View the GL Entries".
Modified: trunk/doc/Manual/ManualInventory.html
===================================================================
--- trunk/doc/Manual/ManualInventory.html 2014-11-29 00:55:58 UTC (rev 7008)
+++ trunk/doc/Manual/ManualInventory.html 2014-11-29 16:25:11 UTC (rev 7009)
@@ -132,12 +132,18 @@
<p>There is a script that allows for stock codes to be modified retrospectively, the script goes through all the tables necessary, location stocks, bills of material, order details, purchase order details, sales analysis etc to ensure that all history for the new part code follows the change. The script together with all utility scripts is available from Z_index.php (there are no links to this utility menu - due to the dangerous nature of some of the utilities) The stock code change script itself is named, Z_ChangeStockCode.php.</p>
- <h3>Part Descriptions</h3>
+ <h3>Part Descriptions</h3><!--Part Description (short)--><!--Part Description (long)-->
<p>A description of the stock item - can be up to 50 characters long. A description is required for each stock item. This description is used in the look up boxes provided each time the stock item is invoiced, credited or adjusted. There is also the facility to enter long descriptions for each part which show on the screens that customers could access to place orders. This field allows very long descriptions or even features and benefits to be described for the item. The intention for this field is that it could be used for producing a company catalogue or for online ordering by customers who may need more information about a product. It is only the description (short) that displays on invoices and credit notes.</p>
<p>The description translations can be maintained within the same parameters above. The translations that can be maintained are set in the system configuration screen. Any number of translations can be maintained. These translations are used to print on customer invoices if the customer is set up to use one of the languages for which translations are maintained. If not translation is available then the fall back is to the default description.</p>
+ <!--h3>Image File</h3>
+
+ <p>...</p--><!--Restrictions (.jpg)-->
+
+ <!--Suggested content: Where is it used? (e.g. scripts, formulas, etc.)-->
+
<h3>Category</h3>
<p>These categories need to be set up first - from the System Setup tab of the menu. In selecting the stock category, be aware that the system uses the category information for analysis and summary reporting as well as identifying accounts for standard cost general ledger integration, if this option is enabled. There is a link to create new stock categories from the stock item entry page.</p>
@@ -150,26 +156,24 @@
<h3>Packaged Volume</h3>
- <p>This field is required for freight calculations. It records the volume of the one of the item as packaged for dispatch. See the section on freight calculations.</p>
+ <p>This field is required for freight calculations. It records the volume of the one of the item as packaged for dispatch. The freight calculation takes the higher of the freight costs based on the total weight of the order and the total volume of the order. Most freight companies use a conversion and charge the higher of the two. See the section on freight calculations.</p><!--Suggestion: add a link to the freight calculations section.-->
- <h3>Packaged Gross Weight</h3>
+ <h3>Packaged Gross Weight</h3><!--Suggestion: standardise from "Packaged Gross Weight" to "Packaged Weight"-->
- <p>This field is required for freight calculations. It records the weight of the one of the item as packaged for dispatch. The freight calculation takes the higher of the freight costs based on the total weight of the order and the total volume of the order. Most freight companies use a conversion and charge the higher of the two. See the section on freight calculations.</p>
+ <p>This field is required for freight calculations. It records the weight of the one of the item as packaged for dispatch. The freight calculation takes the higher of the freight costs based on the total weight of the order and the total volume of the order. Most freight companies use a conversion and charge the higher of the two. See the section on freight calculations.</p><!--Suggestion: add a link to the freight calculations section.-->
- <!--h3>Net Weight</h3>
+ <h3>Net Weight</h3><!--Question: Is it "net content"? (e.g. net kilograms, net litres, etc.)-->
- <p>...</p-->
+ <p>The weight of the one of the item without the weight of its packaging.</p>
+ <!--Suggested content: Where is it used? (e.g. scripts, formulas, etc.)-->
+
<h3>Units of Measure</h3>
<p>This field describes how the stock is to be maintained and is self-explanatory. It is a compulsory field, and as such, some values are defined at the time of installation. System administrators may define additional values or modify existing ones via the 'Units of Measure' link found under 'Inventory Setup' on the main 'Setup' page.</p>
<p>The selection list is maintained in config.php as an array variable. To add or delete other units of measurement the array variable called $InventoryUnits defined in config.php must be edited by the system administrator.</p>
- <h3>Current or Obsolete</h3>
-
- <p>If this field is set to obsolete, this indicates that the stock item is no longer used. However, there may be a stock history on invoices and credit notes which are required. The stock item master record is therefore still required. (Deletion is not allowed while stock movements or Sales analysis records exist for the part) However, it will not appear on searches for invoicing, stock items, in addition the item will be flagged as discontinued in stock reports.</p>
-
<h3>Make Or Buy</h3>
<p>This field is compulsory and indicates whether the stock item is:</p>
@@ -234,8 +238,12 @@
<p>Once the component fields have been entered hitting the enter information button adds the component to the BOM there and then. When the BOM is complete just navigate to the main menu of other link to the next task. Be careful not to click enter information button on the default component by mistake - the component must be selected from the list first.</p>
- <h3>Controlled</h3>
+ <h3>Current or Obsolete</h3>
+ <p>If this field is set to obsolete, this indicates that the stock item is no longer used. However, there may be a stock history on invoices and credit notes which are required. The stock item master record is therefore still required. (Deletion is not allowed while stock movements or Sales analysis records exist for the part) However, it will not appear on searches for invoicing, stock items, in addition the item will be flagged as discontinued in stock reports.</p>
+
+ <h3>Controlled</h3><!--Batch, Serial or Lot Control-->
+
<p>This field denotes whether the item is to have lot control on it. Lot control is known by several terms including, batch control, bundle control, roll control. In short it allows a reference for each batch of the item to be entered at the time of delivery, transfer, stock check, invoicing etc. When booking in controlled items the batch references and the quantities in each batch must be entered. Many quality control systems that require traceability of raw materials need this functionality to establish what batch of raw material was used in a given work order. Or what roll of cloth was sold to a given customer. Other industries call their lots of product by different names a melt, a cut, a run etc. Every time a transaction involving a controlled item is created, the system will accumulate the quantity from a separate form for selecting the batches (Lot/roll/melt/work order/serial numbers).</p>
<h3>Serialised</h3>
@@ -244,8 +252,10 @@
<!--h3>Perishable</h3>
- <p>...</p-->
+ <!--Suggested content: Definition of Perishable.-->
+ <!--Suggested content: Where is it used? (e.g. scripts, formulas, etc.)-->
+
<h3>Decimal Places for display Quantity</h3>
<p>Some items of stock require a number of decimal places to be retained and displayed, others do not require any. This field is used throughout the system for invoices, orders and all places where the item quantity is displayed.</p>
@@ -262,23 +272,28 @@
<h3>Tax Category</h3>
- <!--p>...</p-->
+ <!--Suggested content: Definition of Tax Category.-->
- <p>Tax categories are defined by system administrators in Main Menu > Setup > General Setup Options > Tax Category Maintenance.</p>
+ <!--Suggested content: Where is it used? (e.g. scripts, formulas, etc.)-->
+ <p>Tax categories are defined by system administrators in <i><u>Main Menu</u></i> > <i><u>Setup</u></i> > <i>General Setup Options</i> > <i><u>Tax Category Maintenance</u></i>.</p>
+
<h3>Pan Size</h3>
- <p>This modifier is sometimes called the order multiple. It allows you to create planned orders in even multiples. This is especially useful if you are required by your suppliers to place orders in specific lot sizes. It is also a useful modifier is you have established your own production run sizes. This modifier causes MRP to inflate the required order quantity to an even increment of the pansize value. As with all modifiers you do need to be careful with this modifier as its use could lead to excess inventories.</p>
+ <p>This modifier is sometimes called the order multiple. It is minimum packing quantity. It allows you to create planned orders in even multiples. This is especially useful if you are required by your suppliers to place orders in specific lot sizes. It is also a useful modifier is you have established your own production run sizes. This modifier causes MRP to inflate the required order quantity to an even increment of the pansize value. As with all modifiers you do need to be careful with this modifier as its use could lead to excess inventories.</p>
- <p>In other words if it is most efficient to manufacture an item in batches of 10 then the pan size would be 10, and MRP would calculate demand in batches of 10, so would inflate a demand of 17 to 20.</p>
+ <p>In other words if it is most efficient to manufacture an item in batches of 10 then the pan size would be 10, and MRP would calculate demand in batches of 10, so would inflate a demand of 17 to 20. For instance, we purchase some chemical materials which is 25 kg/pack. The pansize means you have to purchase at least one pack each time.</p>
- <!--h3>Shrinkage Factor</h3>
+ <h3>Shrinkage Factor</h3>
- <p>Percentage by which an output falls short of the estimated or planned output.</p-->
+ <p>Percentage by which an output falls short of the estimated or planned output.</p>
+ <!--Suggested content: Where is it used? (e.g. scripts, formulas, etc.)-->
+
<h3>Item Properties</h3>
+
<!-- Help End: Stocks -->
- <!-- Help Begin: StockCostUpdate -->
+<!-- Help Begin: StockCostUpdate -->
<div class="floatright">
<a class="minitext" href="#top">⬆ Top</a>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X