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 Quantity and amount sizes of 15 are hardcoded in qty_cells() and amount_cells() functions in includes/ui/ui_input.inc and are visible in the rendered page source code attached.
The outer table is 80% of the browser width and the inner table 90% width of that table. The field's column cell widths dynamically expand but the actual input fields remain the same size.
Also refer:
https://www.tutorialrepublic.com/faq/how-to-expand-select-box-to-its-default-width-on-focus-using-css.php
See if the attached fix is needed for inventory moves.
Yes, that is the way to go for now since currency is on a per customer basis as of FA 2.4.8. Maybe, FA 2.5 can have currency per branch. There exists a default branch bank account but may mix up currencies and exchange rate computations if used for a single customer!
Items & Inventory tab => Items => Item Description is quite big already - textarea.
If you mean Sales tab => Direct Invoice Entry, then the select box will automatically change size based on the theme you are using. There is very little leeway in the css file at:
themes/default/default.css Line 45 to 47:
select {
max-width: 230px;
}@joe: any company specific flag for this for the core?
Just logout after an import and clear all browser cache and then login again - all should be okay.
Maybe some variables used (SESSION cache too) in the plugin / core do not get released after use and the plugin does not initialised variables used properly!
This is a notional exchange rate based calculation and will be in contra in the exchange rate gain/loss account. When the actual transaction is fulfilled in a specific currency other than in the currency of the account, such differences will occur but will vanish when the actual currency of settlement is used.
Contra is the account into which a balancing amount in a transaction goes.
For example, if cash is given by the company to a vendor, then:
Cash Account Credit
Vendor Account Debit (Contra Account)
Salvage value is not handled in FA except if not depreciated after a certain while and a residual value is left in the asset account - book value.
When moving from other accounting systems, make the opening FA Asset Value as the existing written down book value of the asset. This is so that any fresh depreciation can commence from where the old accounting system left off.
Maybe if you have the time, after you have sufficient experience in using the FA Fixed Assets module, you are welcome to fill in the wiki at:
https://frontaccounting.com/fawiki/index.php?n=Help.FixedAssets
Provide screenshot of sample invoice.
TCPDF version used here is v6.3.2 - circa a year ago vintage.
What was sought to be achieved using the new TCPDF version?
Provide info on README.md as to which folder should be overwritten and what checks have been made to integrate with existing FrontAccounting Box report constructs.
HSN is a max of 6 digit number for GST - Harmonized System of Nomenclature.
This is different from HSN for import/export which is 8 digits.
Service Accounting Code (SAC)
Format of HSN is:
https://cdn.mastersindia.co/custom_pages/img/hsn--cod.png
Useful HSN links:
https://cleartax.in/s/gst-hsn-lookup
https://www.mastersindia.co/gst/hsn-code-search/
https://gstportalindia.in/list-of-hsn-code-chapter-wise-updated/ - 98 chapters
Added it to FA24extensions repo at:
https://github.com/apmuthu/FA24extensions/tree/master/Extensions/shipment_tracking
Attached some changes as well.
An additional missing area you need is 526.
All these fixes have already been incorporated in the GitHub for the FA24Exetensions as and when the official en_US-new.sql changed.
The Official Extensions Repo is not yet updated.
Take the latest one from:
https://github.com/apmuthu/FA24extensions/tree/master/Charts/chart_en_IN-general
@joe: update the official extensions from the above link.
Different table prefixes should make them different - is there any query that used a hard coded prefix for this issue?
The CloudMan Wiki page on WinXP compatible programs is available here:
http://cloudman.mnmserve.com:7060/Windows_XP_compatible_last_versions
The current version is attached here.
@joe: can it be safely used in the core?
Treat an item in another location as a different item for now as FA currently just has one cost at a time for each item.
That will work and you will have to manually calculate and place the tax yourself in the Journal entry and apart from tracking/allocation you will also lose native tax reporting in some instances.
Check if some rounding off error got missed out in the computation sequence first. If such occurrences are few and far between, make a compensating Journal Entry for the adjustment each time for now.
If the owner is regularly taking an advance from the firm/company , then create a Current Asset account in the Owner's name. If the owner is regularly financing temporary deficits of the firm/company, then make it a Current Liability Account in the Owner's name.
Fixed Assets is part of FA 2.4.8. HRM is not in the standard FA. Take assistance from where you download your codebase. Without specifying the versions of the WebServer/PHP/MySQL/Platform/FA the community will be hardput to assist you. If you are not techincally self-sufficient, place a bounty in the Job/Offers board and an interested forum user may assist you.
Contact your server service provider.
The design will involve a generic table for all approvals that will be looked up to display a list that is pending approval and record who approved it (with appropriate role permissions) and enable the posting of the record in the appropriate tables. We need to keep in mind that the date of approval should be the document date and all computations for average/cost price, possibly even document reference numbers, etc are created only then after approval.
If all this needs is just a report request form check box without the need for any db changes or even sys_prefs changes, why not.
It is best if it is displayed for a specific customer so that totals do not get messed up for those witout multiple branches.
The reason why this is not implemented is that there are quite a few legacy users and those who use WinXP still in India where unicode in older browsers may not have the rupee font.
If you want, then replace line 508 in the CoA:
`curr_symbol` varchar(10) NOT NULL DEFAULT '',with whatever encoding you want - please note that the one of the first lines has SET NAMES latin1; as the default encoding.
Also change the data in line 521 accordingly for the symbol besides saving the file as UTF-8 encoding text and change the _init/config file with the proper encoding.
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.