New Costing Engine

From ADempiere
Revision as of 15:43, 12 June 2013 by Mar cal westf (Talk) (Technical Requirements)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.

Status

In production use

Contributors

e-Evolution

Overview

In business, retail, and accounting, a cost is the value of money that has been used up to produce something, and hence is not available for use anymore. In economics, a cost is an alternative that is given up as a result of a decision. In business, the cost may be one of acquisition, in which case the amount of money expended to acquire it is counted as cost. In this case, money is the input that is gone in order to acquire the thing. This acquisition cost may be the sum of the cost of production as incurred by the original producer, and further costs of transaction as incurred by the acquirer over and above the price paid to the producer. Usually, the price also includes a mark-up for profit over the cost of production.


In accounting, costs are the monetary value of expenditures for supplies, services, labour, products, equipment and other items purchased for use by a business or other accounting entity. It is the amount denoted on invoices as the price and recorded in bookkeeping records as an expense or asset cost basis. [1]

Purpose

Costing Engine Specification

References

Sponsored Development: Libero Costing Engine

Design Considerations

Assumptions

Dependencies

Constraints

  • Only Average PO/Invoice and Standard Costing method are supported

Glossary

Functional Requirements

Functional team

  • Volunteers for analyzing:
  • Result of analysis:

User roles & profiles

Business process definition

User stories

Functional requirements based on business processes

User Interface Mockups

Libero Cost Engine

Acceptance criteria

QA and test cases

Cost Engine/Testing

Development infrastructure

Technical Requirements

Technical team

  • Volunteers for analyzing:
  • Result of analysis:

Data Requirements

Non-Functional Requirements

Open Discussion Items

Closed Discussion Items