Search · Index

General Ledger (accounts-ledger)

Vision Statement

General Ledger provides services to other packages and provides a basic UI for directly managing the ledger and accounts.

 

Requirements

• port from sql-ledger as a base
• able to import sql-ledger database

Implementation Notes

Consider combining/normalizing the AP/AR/GL tables to one GL table to simplify the sql etc. in so far as they are essentially variations on the same table. The separate AP/AR tables will only handle data that are unique to each class of transaction grouping.

The thread on adding history to package parameter changes may help with creating a journaling process that can reverse transactions.

Permissions should be more flexible than found in sql-ledger. See OpenACS threads Creating default group sets for package instances and roles in permissions for related discussion.

 Features

Converted:

• Preliminary data model for Postgresql including preloading chart templates and language translations when installing.
• Num2text in SL, lc_number_to_text in accounts-payables package

Plan summary

Basic general ledger posting via web and service (also callback?), and editing chart templates.  One ledger per package instance.  See sql-ledger's features and What's new pages. 

notes

sql-ledger	package-key  table name
<table_name>	qal_<table_name>

Need to add package_key to data model.

porting notes and guidelines

The locale data has been extracted using a custom program located in the accounts-ledger/info directory of this package. Configuration data is set in convert.tcl. Be sure to remove xml language files in accounts-ledger/catalog/ before running the program.

Any functions dependent on either AP or AR data are moved to those packages. When something is dependent on two or more accounting packages, it is moved into the "full accounting features" accounts-desk package.

Each package has a set of Model-View-Control features and services.  Most any of these packages should provide a basic level of features without requiring other packages. Optional (integrated) features are built into the packages where appropriate.

Table of "critical path" package dependencies

package-key	depends on
accounts-ledger	*contacts, inventory-control
accounts-payables	accounts-ledger
accounts-receivables	accounts-ledger
accounts-desk	accounts-payables, accounts-receivables, accounts-payroll
ref-gifi	none, integrates with accounts-ledger
ref-unspsc	none, integrates with categories
accounts-payroll	accounts-ledger
inventory-control	none
online-catalog	none
shipping-tracking	accounts-ledger

* - Rudimentary contacts will be managed in accounts-ledger, and will be subsequently integrated with contacts package via a package parameter switch. accounts-ledger will not depend on contacts due to the complexity of contacts and the likelihood that contacts will have specific verifiable requirements in various industries in order to meet privacy or security standards etc.  These standards might be difficult to manage in the contacts package. There is no documentation for contacts package that addresses these concerns (20070531).

(see ecommerce G2)

functions and procedures

lc_number_to_text proc is made from the the SL Num2text procedure which has localized cases in the locale directories, and the default Num2text.pm in sql-ledger/SL/

SQL

The Oracle SQL will be added after the PG SQL has settled a bit.

Some of the SQL has been changed to the OpenACS standards. See http://openacs.org/doc/current/eng-standards-plsql.html and http://openacs.org/wiki

for Postgresql:

INT changed to INTEGER
some of the TEXT types were changed to VARCHAR so that they get indexed
FLOAT changed to NUMERIC

These parameters need to be put into their respective packages

   -- this is a 1-row table
   -- it contains all settings that the admin can change from the admin pages
   -- most of the configuration is done using the parameters .ini file
   -- wtem@olywa.net 03-10-2001
   -- the following two tables probably need an additional column to support subsites
   -- in which case it will have multiple rows, one for each instance of ecommerce
   -- since these are really parameters for the instance of ecommerce,
   -- it might be better to move them to ad_parameters
   create table ec_admin_settings (
           -- this is here just so that the insert statement (a page or
           -- so down) can't be executed twice
           admin_setting_id                integer not null primary key,
           -- the following columns are related to shipping costs
           base_shipping_cost              numeric,
           default_shipping_per_item       numeric,
           weight_shipping_cost            numeric,
           add_exp_base_shipping_cost      numeric,
           add_exp_amount_per_item         numeric,
           add_exp_amount_by_weight        numeric,
           -- default template to use if the product isn't assigned to one
           -- (until the admin changes it, it will be 1, which will be
           -- the preloaded template)
           default_template            integer default 1 not null
                           references ec_templates,
           last_modified               timestamptz not null,
           last_modifying_user         integer not null references users,
           modified_ip_address         varchar(20) not null
   );

-- create table ec_admin_settings_audit (
--         admin_setting_id                integer,
--         base_shipping_cost              numeric,
--         default_shipping_per_item       numeric,
--         weight_shipping_cost            numeric,
--         add_exp_base_shipping_cost      numeric,
--         add_exp_amount_per_item         numeric,
--         add_exp_amount_by_weight        numeric,
--         default_template            integer,
--         last_modified               timestamptz,
--         last_modifying_user         integer,
--         modified_ip_address         varchar(20),
--         delete_p                    boolean default 'f'
-- );
--
-- create function ec_admin_settings_audit_tr ()
-- returns opaque as '
-- begin
--         insert into ec_admin_settings_audit (
--         admin_setting_id, base_shipping_cost, default_shipping_per_item,
--         weight_shipping_cost, add_exp_base_shipping_cost,
--         add_exp_amount_per_item, add_exp_amount_by_weight,
--         default_template,
--         last_modified,
--         last_modifying_user, modified_ip_address
--         ) values (
--         old.admin_setting_id, old.base_shipping_cost,
--     old.default_shipping_per_item,
--         old.weight_shipping_cost, old.add_exp_base_shipping_cost,
--         old.add_exp_amount_per_item, old.add_exp_amount_by_weight,
--         old.default_template,
--         old.last_modified,
--         old.last_modifying_user, old.modified_ip_address
--         );
--     return new;
-- end;' language 'plpgsql'
--
-- create trigger ec_admin_settings_audit_tr
-- after update or delete on ec_admin_settings
-- for each row execute procedure ec_admin_settings_audit_tr ();
--
-- -- this is where the ec_amdin_settings insert was
--
--
-- -- put one row into ec_admin_settings so that I don't have to use 0or1row
-- insert into ec_admin_settings (
--         admin_setting_id,
--         default_template,
--         last_modified,
--         last_modifying_user,
--         modified_ip_address
--         ) values (
--         1,
--         1,
--         now(), (select grantee_id
--                     from acs_permissions
--                    where object_id = acs__magic_object_id('security_context_root')
--                      and privilege = 'admin'
--                      limit 1),
--         'none');
--
--

---

Categories: OpenACS (ec-g2)

No comments available

Add comment