Plugin: Budgetary Control

• Maintainer: Red1 (talk) - RED1.org
• Sponsor: SYSNOVA
• Copyright red1 (the novelty of the technical specifications are the original idea of the author(s) stated in later details.)
• Current Version: 1.0 ALPHA
• License: GPLv2 - Free as in Freedom not Free Lunch
• Price: (to be determined later for commercial users only)
• Guide:

Introduction

• THIS IS A WORK IN PROGRESS - EARLY RELEASE DUE END MARCH.
• Any work stated here can be reused by other projects as long as the licensing, credits and link-back to this source are provided at its web-page header or main footer.

GENERAL SPECIFICATIONS

• The Budgetary Control Module shall be made in accordance to published international standards and well structured in an OSGi plugin user environment
• The plugins shall be backward compatible and not impact any core processes unless explicitly specified.

STATUTORY SPECIFICATIONS

• The module shall allow compliance and auditing requirements by statutory law and bodies. It shall be made adaptable in most countries via a locale selection.

TECHNICAL SPECIFICATIONS

Design of Plugin

• This module should be only for a single specific purpose. Any further purposes shall be made in another set of plugins and they should be equal citizens with no interdependency unless explicitly specified.
• The module shall not modify core models such as Accounting Schema. This is possible because the plugin is self aware that it is for Budgetary usage. Uninstalling it shall remove such awareness naturally. Thus a checkbox to CheckBudget is not needed anywhere.
• The module shall not be specific to any document. This is achievable with lesser code in a single Document-Event validator that checks for Trxn status rather than DocType. This can be in another plugin
• A base plugin can be the building of the Budgetary Control/Lines containing no processing logic.
• Processing logic be in a separate plugin for easier maintenance and deployment as well as variety of settings.

Design of Master Input

• Input should be in an Accountant-friendly environment such as the use of a spreadsheet.
• The template should be defined and documented for use with http://wiki.idempiere.org/en/NF001_ImportCSV

ACCOUNTING SPECIFICATIONS

• The budgetary amounts are stored in the Budget accounting type which was designed in Compiere ERP (1999-2006).
• The accounting event dimensions are also designed in Compiere ERP (1999-2006):
  • Accounts ID,
  • Product,
  • BPartner,
  • Sales Region,
  • Period,
  • Org and
  • 2 other user defined elements
  • Project
  • Campaign
  • Activity

REFERENCES

• INC.COM
• BBRT.ORG/Forecasting Budget