2,051

(114 replies, posted in Reporting)

Are you using the fixes after the release of FA 2.4.3?

The id_ID language uses the iso-8859-1 encoding as listed in the install wizard but is entered as UTF-8 in the .po files and this has now been rectified in my repos. Anyone using the new .mo files should update their lang/installed_languages.inc file as well.

install lang id_ID commit - install .mo file - 100% translated (17 strings left in official repo)
core id_ID lang extension commit - core extension .mo file - 433 strings untranslated still (444 in official repo)

2,053

(4 replies, posted in Translations)

You can add / modify / delete any line in the .po file and re-compile it into a .mo file and use it.

Have just updated the id_ID install language and core language strings in my repos. If you intend to use this, then change the UTF-8 encoding to iso-8859-1 encoding in your lang/installed_languages.inc file as well.

It is best to make mobile themes self sufficient instead of tinkering with the FA core. The FA core can abstract hardcoded constructs in it into the theme where pertinent. Some elements will need different widths / font sizes to accommodate strings in other languages.

Swiftkey for Android auto injects emoicons based on context which will not be suitable for FA.

A mobile/responsive theme is available in some forks which have morphed FA considerably making it difficult to keep updating it when the core changes.

Creating additional user roles can be documented in the wiki with intent and purpose explained.

@joe: The viewport can be added if it does not violate strict browser settings.

All debits are stored as negative numbers in the GL Trial Balance. Your cash balance should be negative (debit) too. When you close the year all P&L entries are summed up and the net Profit or Loss is moved to the balance sheet. If you are referring to the account closure that this happens in, then the contra entry will have to be added to zero out the P&L account and then migrate it (P&L) to the Balance Sheet as a debit.

Since one location sells to another - treat them as different shops - each can make a profit from selling to the other. Alternatively use average costing and let the discount given to each customer vary. The exact acquisition cost will then be factored in the average cost. Anything specific can be treated as a different item for the FA internals with the same description - item_code and stock_id - you can also use manufacturing / assembly and kits. In the inevitable instance, make yourself an extension.

If you wish to track the same item with vastly varying prices, then make it two differently coded items (stock_id). There is nothing wrong with the current algorithm's outcome as the item is still one of a kind.

All data elements go into the appropriate db field in MySQL.
The doctext.inc file should have it's path created before being copied over and edited as needed in the web folder.

If you need professional assistance post your offer in the Job Offers board.

2,059

(3 replies, posted in Reporting)

Setup => Access Setup => Roles => select host

Attached is a set of screenshots for a forex purchase invoice and the corresponding forex converted payment along with their views and GL entries.

At the time of making the Supplier Invoice entry in USD, there is no conversion needed even if the company currency is in SAR except for the GL entries that would get converted in the Purchases account - check the GL entries for the transaction after Purchase Invoice entry.

Again, when making payment in USD from a cheque drawn on a USD denominated bank account, no conversion is needed except for the GL entries on the purchases / stock inventory accounts - check them as well.

You should have an Exchange Variances Account assigned in Setup => System and General Setup that will be used for Balance Sheet, P&L Account and costing / settlement purposes.

Alternatively, if you entered the exchange rate manually, try to logout and login again and then make the Supplier Invoices and the Payments to Suppliers. This is assuming you are plagued with some browser cache - set the browser options to clear cache on exit.

2,062

(6 replies, posted in Setup)

Read the Wiki.

Sales => Customer Transactions => Sales Invoices (Type) => Edit Icon.

Since both Supplier Currency and Purchase Invoice entry are in USD, there is no conversion needed. Make sure you have entered it in USD Amounts too in both cases. Hopefully, if you pay the Supplier from your USD Bank Account, then too there will not be any exchange rate conversion. Only in the Balance Sheet and P&L Account will it reflect in Saudi Riyal after conversion. Make sure your exchange rate is entered preferably a day earlier (may be there might be some glitch there - but no one has complained so far).

2,064

(5 replies, posted in Setup)

Just downloading the charts and overwriting the counterparts in the sql folder is good only for new companies created with them. The old companies created with the erroneous charts must be synched in schema and appropriately migrated to the new one. Just make one company with the en_US-new.sql and compare the schema with your older companies and synch the latter.

PHP 5.4.x should work.
Are you on Windows or Linux?

Study the Apache and FA error logs and enable debug in your config file and see where the problem lies. Check out FA troubleshooting in the FA Wiki.

Enable OpenSSL in your php.ini and restart your webserver.
Do not use the Yahoo exchange rate provider as they have discontinued free service.
All future transactions will be at the exchange rate you have entered.
Your supplier / customer should have their settlement currency entered and your bank account for that currency available.

2,067

(6 replies, posted in Modules Add-on's)

The Slim Framework page has examples.

Nice work.
PHP 5.1.6 (XAMPP 1.7.3 on windows) and 5.3.3 (Debian Squeeze) do not need to remove the comment though.

2,069

(5 replies, posted in Setup)

That chart is probably old and not updated correctly. Take an updated one from the FA24extensions repo depending on if you are using the English or Arabic one.

Read the wiki, search the forum and experience the code - live and learn.

Post your job and bounty offer on the Job Offers board.

1. Inventory report is as on the time of printing - yes, continuous.
2. Enable Barcode in the Preferences. - Yes.
3. "add a call" ??? - each item sold in multiple units should be entered as separate items or use the sales kit / assembly feature.
4. Salesman facility only.
5. Expiry Date / Batch number not in native FA as of now. Some users have built their own extensions and some sell them - search the board.

The FA project is an open source one where everyone can learn and be a developer. The project has nothing to sell and everyone works at their own cost in time. Support employees / FA users to become developers and contribute your fixes / feature sets.

2,071

(5 replies, posted in Setup)

The Retained Earnings Account and the Profit and Loss Account must exist in your chart_master table with the correct chart_type - see the sql/en_US-new.sql file for parallels and adjust your Chart accordingly.

Setup => System and General GL Setup must have the Retained Earnings and the Profit/Loss Year accounts set properly.

2,072

(6 replies, posted in Modules Add-on's)

Not in the official repo. Some commercial implementations are available and the SlimREST_API can be used to design one.

The official pkg when installed probably did not install fully as the file/folder permissions may have been wrong.
What is your platform and versions of PHP/MySQL/Apache?
Have you updated your FA 2.4.3 with the fixes thereafter?

Update your repgen module from the FA24extensions repo.

2,074

(5 replies, posted in Report Bugs here)

@joe: Thanks for the commit.

2,075

(1 replies, posted in Items and Inventory)

Not aware of this "feature" in FA as of now.