Search options (Page 103 of 246)

Check the terms of payment choice for such invoices if you find a pattern.

No, just see if you can hide the Sales tab from one of your extensions and make it persist....

@joe: while fixing this check on any alert thresholds to inform the user that the remaining is out of stock.

Hope you had enabled the config variable to allow negative stock.

As long as you have no transactions, the lookup data like customers, suppliers and items can easily be exported and re-imported with the likes of phpMyAdmin / SQLyog. Anyway, goodluck.

You might want to synch your schema at the very least before you start entering transactions.

Take an sql dump of your database (only the structure/schema) without any data and upload it somewhere and paste the link here. Will try to provide the alter statements for the database to synch the schema to the en_US-new.sql standard as in my repo.

You are using the Foxit PDF reader to view PDF documents. Make sure you are using a recent FireFox Browser as it comes with a native PDF viewer so that it shows up in the browser itself. Check your browser Applications linkage options.

Use a local property in your extension application class and code it as:

var $extn_$systypes_array = $systypes_array;
$extn_systypes_array[ST_SALESINVOICE] = _('Donations');

The function gl_options_controls is defined (but not used) differently in the following files (only the second one has the footer in it):

gl/includes/ui/gl_journal_ui.inc
gl/includes/ui/gl_bank_ui.inc

The said function is called in the following files by including the respective file above:

gl/gl_journal.php
gl/gl_bank.php

Let us first start naming global functions uniquely.
The said function may need to be fixed in the file gl/includes/ui/gl_bank_ui.inc and if the function is renamed for uniqueness, then the corresponding function call in gl/gl_bank.php too should be corrected.

The Chart SQL files in sql/*.sql will not be touched by FA. They are used as templates to create a new company only. Hence replacing the them from my repo will not affect anything except that the next company you create will be okay to start with itself.

The backup sqls are the ones that contain your changes and they are created on the fly and are stored in company/#/backup folder. This is the one you will want to correct and synch it's schema and data with the one in my repo - use with care - and then upload and restore therefrom.

Since you do not have any transactions yet, it might be easier to create a new company from the sql in my repo and then incorporate the small changes you have made all over again in it.

What happens if each transaction is posted separately instead of combining all three payments received into one journal transaction - is it okay? If so, then there is GROUP BY / SUM error in the sql used. Post the urls that are affected.

@joe: Needs investigation and fixing.

Each theme is a subfolder in the themes folder. Any theme installed from the pkg repo will be found in the modules folder with a corresponding entry in the installed_extensions.php file. Copy and rename a folder in the themes folder and edit the files there to customise your unique theme.

Setup -> Void Transaction -> Transaction Type: Supplier Credit Note -> Search and choose the one you want and void it.

A Credit Note will have the GL entry(table: gl_trans) type=21 and the Accounts Payable (2100 in en_US-new/demo CoA) with person_type_id=3 and the actual person_id being the id of the supplier. This will also bear an entry in the supp_trans, supp_invoice_items and audit_trail tables as well.

On voiding, the amounts get zeroed out in the supp_invoice_items, supp_trans, gl_trans tables for the specific record(s).

The anatomy of the Void of a Supplier Credit Note is discerned from the diff between the pre and post void backups:

--- fa24_1_pre-void_backup.sql    Mon Oct 23 09:18:59 2017
+++ fa24_1_post-void_backup.sql    Mon Oct 23 09:19:56 2017

-insert  into `1_audit_trail`(`id`,`type`,`trans_no`,`user`,`stamp`,`description`,`fiscal_year`,`gl_date`,`gl_seq`) values 
-  (32,21,1,1,'2017-10-23 09:12:19','',2,'2017-10-23',0);
+insert  into `1_audit_trail`(`id`,`type`,`trans_no`,`user`,`stamp`,`description`,`fiscal_year`,`gl_date`,`gl_seq`) values 
+  (32,21,1,1,'2017-10-23 09:19:10','',2,'2017-10-23',NULL)
+ ,(33,21,1,1,'2017-10-23 09:19:10','Voided.\n',2,'2017-10-23',0);

-insert  into `1_gl_trans`(`counter`,`type`,`type_no`,`tran_date`,`account`,`memo_`,`amount`,`dimension_id`,`dimension2_id`,`person_type_id`,`person_id`) values 
-  (41,21,1,'2017-10-23','2100','',25,0,0,3,'1')
- ,(42,21,1,'2017-10-23','5010','Test Supplier CN',-25,0,0,NULL,NULL);
+insert  into `1_gl_trans`(`counter`,`type`,`type_no`,`tran_date`,`account`,`memo_`,`amount`,`dimension_id`,`dimension2_id`,`person_type_id`,`person_id`) values 
+  (41,21,1,'2017-10-23','2100','',0,0,0,3,'1')
+ ,(42,21,1,'2017-10-23','5010','Test Supplier CN',0,0,0,NULL,NULL);

-insert  into `1_supp_invoice_items`(`id`,`supp_trans_no`,`supp_trans_type`,`gl_code`,`grn_item_id`,`po_detail_item_id`,`stock_id`,`description`,`quantity`,`unit_price`,`unit_tax`,`memo_`,`dimension_id`,`dimension2_id`) values 
-  (2,1,21,'5010',-1,0,'','',0,-25,0,'Test Supplier CN',0,0);
+insert  into `1_supp_invoice_items`(`id`,`supp_trans_no`,`supp_trans_type`,`gl_code`,`grn_item_id`,`po_detail_item_id`,`stock_id`,`description`,`quantity`,`unit_price`,`unit_tax`,`memo_`,`dimension_id`,`dimension2_id`) values 
+ ,(2,1,21,'5010',-1,0,'','',0,0,0,'Test Supplier CN',0,0);

-insert  into `1_supp_trans`(`trans_no`,`type`,`supplier_id`,`reference`,`supp_reference`,`tran_date`,`due_date`,`ov_amount`,`ov_discount`,`ov_gst`,`rate`,`alloc`,`tax_included`) values 
-  (1,21,1,'001/2017','ABC_112','2017-10-23','2017-10-23',-25,0,0,1,0,0);
+insert  into `1_supp_trans`(`trans_no`,`type`,`supplier_id`,`reference`,`supp_reference`,`tran_date`,`due_date`,`ov_amount`,`ov_discount`,`ov_gst`,`rate`,`alloc`,`tax_included`) values 
+ ,(1,21,1,'001/2017','ABC_112','2017-10-23','2017-10-23',0,0,0,1,0,0);
 
+insert  into `1_voided`(`type`,`id`,`date_`,`memo_`) values 
+  (21,1,'2017-10-23','');

The SalesKit circular issue is a bit more complex even if the self choosability of level 1 is implemented..
SalesKit SK1 is created to have some items.
SalesKit SK2 has some items.
SalesKit SK3 has some items and SalesKit1 as part of it.
SalesKit SK3 is now added to be part of SK2.
SalesKit SK1 will now be able to choose SK2 which in turn has SK3 with in turn comprises of SK1 itself!.

A complete self join based tree lookup with multiple 'inheritances' would need to be implemented.

So let us keep it simple even if slightly stupid!