ec-g2
- accounting
- OpenACS
- Accounts Desk
- Accounts Finance
- Accounts Ledger (General Ledger)
- Accounts Payables
- Accounts Payroll
- Accounts Receivables
- Application Neutral Audit (ANA) Logs
- Bulk Upload
- Coding references and open standards
- Customer Service
- ECKS Forms
- ECKS templates
- Ecommerce-2
- Ecommerce-g2
- Ecommerce-g2 development guidelines
- Ecommerce-g2 package list
- Ecommerce-g2 requirements
- Fabrication
- Field Service
- Glossary
- Human Resources
- Inventory Control
- Manufacturing Design
- Online Catalog
- Production
- Reference Data - GIFI
- Reference Data - UNSPSC
- Shipping Tracking
- Spreadsheet
- Supply Chain
- Systems simulator package
- Task: add locales (done)
- ec-g2 contributors
- other non-OpenACS software
No registered users in community XoWiki
in last 20 minutes
SQL-Ledger porting notes
SL puts all AR data in AR table, AP data in AP table, GL data in GL table, with shared portions in acc_trans table.
To maximize usefulness and integration subsystems, consider adding a transaction type to the sql-ledger acc_trans or GL table and the GL relevant AR/AP transactions moved into the GL/acc_trans tables, while leaving the generic AR/AP tables/workflow separate. Reasons:
- reports that depend on the general ledger should work with the COA regardless of data origins and not be concerned about any external AR/AP workflow (since they can greatly vary).
- report code is simplified when all data of one general class are in 1 table.
- Controlling permissions when separating them by AR/AP/GL transactions (as SL does), where GL is given higher level authority, may require modifying a COA and adding extra account transfers to accomplish certain tasks, such as gift certificate purchases. Whereas moving permissions to be based on url allows much more flexibility.
- UPS Worldwide integration http://www.jjayr.com/m/projects/sql-ledger/