It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by apmuthu
The file includes/hooks.inc has it's last class method default_get_dispatchable_quantity() called only in the page's last function hook_get_dispatchable_quantity().
1. Is this set of functions necessary here?
2. The said method has two consecutive return statements - remove or comment one of them if they should be there for some alternative workaround for a different set of PHP versions.
Install of an extension and activating it for specific companies can be done only from the default company. All other companies can only then enable/disable permissions for it's security sections for appropriate roles for themselves.
The problem is that you are trying to Void it twice - once on successfully Voiding a transaction and since Transaction# is still showing the voided one as a label in the resultant page you may have pressed the Void Transaction again. The Memo field gets cleared but the Transaction# field does not.
@joe: The success message should show the Transaction# that was successfully voided and the Transaction# label in the form should be blanked out on the success page.
There is another issue that appears. When we try to add one more item to a SalesKit, the SalesKit (the one we are adding to) appears in the selection drop down box and we can actually get into a circular binge! If some other SalesKits are chosen then it may be okay and that too only if this current one is not part of the SalesKit we are adding.....This may not really be a problem if the Sales Kit being added to another Sales Kit gets populated by it's constituent items!
If we can replace the primary key id with the stock_id and item_code as a compound primary key in the item_codes table and re-code all the classes and functions to adhere to it, then maybe we can do what you want. It will probably break a few extensions as well!
@joe: good to have.
The $_SESSION['App']->applications array of objects is dumped and attached herein for further coding and ordering the tabs.
Actually the Uniqueness for the said couple of fields is enforced by an index. It could have been the compound primary key in which case your need would be satisfied.
FA for the most part has tables with just one single primary key to make it easy to code record manipulations (select, update,delete).
The fields stock_id and item_code are both generally VARCHAR(20 except a few of the former are CHAR(20) in all tables they are part of. The varied definition is probably an error or some index justification.
grep stock_id sql/en_US-new.sql
`item_code` varchar(20) NOT NULL default '',
`item_code` varchar(20) NOT NULL,
`item_code` varchar(20) NOT NULL default '',
grep item_code sql/en_US-new.sql
`stock_id` varchar(20) NOT NULL default '',
`stock_id` varchar(20) NOT NULL,
`stock_id` char(20) NOT NULL default '',
`stock_id` varchar(20) NOT NULL default '',
`stock_id` char(20) NOT NULL default '',
`stock_id` varchar(20) NOT NULL default '',
`stock_id` char(20) NOT NULL DEFAULT '',
`stock_id` varchar(20) NOT NULL default '',
`stock_id` varchar(20) NOT NULL default '',
`stock_id` varchar(40) default NULL,
`stock_id` char(20) NOT NULL default '',If two branches of a single customer are assigned to different Sales Groups, will your listing appear fine if the new Sales Group filter is in place?
The tag for strike-through here is del (in [ ] and [/ ]).
You're right. The field group_no (Sales Group) is part of the #_cust_branch table and hence there can be only one Sales Group for one branch.
This means that you will also need to have a cust_branch filter if you want to make a report Sales Group - wise.
Update to latest FA 2.4.2+ and see if this issue resolves itself.
The changed files from FA 2.4.1 to FA 2.4.2 (#4 post) and that for fixes thereafter (#12 post) are in the Announcements thread for FA 2.4.2.
@joe: your take?
Then as it is still possible to assign the same branch to more than one sales group, the uniqueness of the requested filter would will cause erroneous sums in the resultant report.
@joe: makes sense?
What happens if a customer is in more than one sales group?
The Hello World module is now extended to be in it's very own tab.
Screenshots too are in the attachment herein.
Must now implement ways to disable and re-enable tabs from within the user interface much like the Use Manufacturing and Use Fixed Assets settings in the Company Setup page.
The tabs are stored in $_SESSION['App']->applications array of objects where the keys will now be:
'orders'
'AP'
'stock'
'manuf'
'assets'
'proj'
'GL'
'hello' <<== newly inserted
'system'What is the standard method of re-ordering the tabs? Some tabs will be missing in the above list if not enabled.
Why not code the Company Setup with the means to enable/disable all standard and registered tabs other than Setup?
Materials are issued from stock / purchases for use in a work order for processing.
They may be in addition to those in the BOM and may be issued multiple times during manufacturing process.
When material is moved from stock for manufacturing they need to move out of the warehouse and hence the stock_moves - only after this can manufacture start / resume.
Refer the Wiki which is quite comprehensive.
@joe: any thoughts?
@joe: I agree.
@boxygen: Zip, upload and paste link to changed files for this "feature" so that it can become an extension someday and be available for reference.
@BraathWaate: Good to rely on core functions like the native get_next_trans_no() in the final fix now committed in my repo.
It is attached herewith.
Either create your own report or manipulate the Excel Report.
Each Sales Kit has a separate item_code of it's own in FA. The Sales invoice will only reflect the individual items and not the Sales Kit name. In fact, the item_codes table has some redundancy in the description of the Sales Kit name (see attachment) that is duplicated for each constituent item in it. This normalisation issue may the cause of it's inability to provide the unique auto numbered item_code to the constituent items of a SalesKit when more than one constituent item exists. As the said table has a separate auto-numbered id field manipulating each entry individually is not hampered when just the id of the record is provided. But when several constituent items are inserted in sequence this will be an issue if the actual item_code is not properly coded into them and the next one is invoked each time.
Wonder which field or what logic distinguishes a SalesKit from a normal item......
@joe: this needs investigation.
@joe: is this desirable in the default FA?
Since a different construct was used in sending the email, it may have been possible that the return from the sending routine is different and that return is what needs to be investigated.
I have updated the mod file with your changes in #2 post.
The job of the function End() is to provide the said notification which comes but in another page. Lines 1037-1038 in the said function in reporting/includes/pdf_report.inc are:
display_notification($this->title . " " . $this->formData['document_number'] . " "
. _("has been sent by email to destination.") . " " . _("Email:") . $emails);Try to replace the 2 submenu_print statements (in the Add and Update sections) in sales/customer_payments.php with the following and provide feedback:
display_note(print_document_link($payment_no."-".$trans_type, _("&Email This Receipt"), true, ST_CUSTPAYMENT, false, "printlink", "", 1),1);You may need to echo "<br>"; to adjust spacing of the links.
Try the fixes in my previous post.
The following at line 100 in sales/customer_payments.php does not work.
display_note(print_document_link($payment_no."-".$trans_type, _("&Email This Receipt"), true, ST_CUSTPAYMENT, false, "printlink", "", 1),1);The following too does not work:
submenu_print(_("&Email This Receipt"), ST_CUSTPAYMENT, $payment_no, null, 1);The above alone does not work even with necessary changes made to use $email in reporting.inc and rep112.php.
Try the consolidated changes for the bleeding edge attached and provide feedback.
$hide_inaccessible_menu_items is for hiding menu items inside the tabs .
The commenting out of the add_application() is for hiding menu tabs at the top.
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.