VPMS Web Application

Store cost of sale information in customer invoices, credits and counter sales

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.3
  • Fix Version/s: 1.3
  • Component/s: Customer
  • Labels:
    None

Description

In order to calculate profitability on charges that have a cost base we need to store product costs with customer charges archetypes.

This will require modification to the financial_acts class to include a fixed_cost and a unit_cost attribute and modification of the charging archetypes to include hidden, readOnly fixedCost and unitCost nodes and have this updated during charges entry.

The fixed and unit cost values for act.customerAccount*Item nodes will come from the associated fixed and unit product cost values.

The fixed and unit cost value for act.customerAccountCharges* archetypes will be sum of the their linked act.customerAccount*Item acts values.

Issue Links

This issue Refers To:
OBF-194 Add fixedCost and unitCost attributes to FinancialAct Major Resolved

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tim Anderson added a comment -

Changes applied to:
. archetypes, revision 3045
. vpms, revision 3043

Show
Tim Anderson added a comment - Changes applied to: . archetypes, revision 3045 . vpms, revision 3043
Hide
Permalink
Tim Anderson added a comment -

Fixed invoice unit cost to be the sum of qty * unit cost for all items.
Change applied to vpms, revision 3092.

Show
Tim Anderson added a comment - Fixed invoice unit cost to be the sum of qty * unit cost for all items. Change applied to vpms, revision 3092.
Hide
Permalink
Tony De Keizer added a comment -

Cost of sale values not being stored in financial acts.

Show
Tony De Keizer added a comment - Cost of sale values not being stored in financial acts.
Hide
Permalink
Tim Anderson added a comment -

Fixed price change events weren't being generated preventing the calculation of costs in the parent act.

Fixed in vpms, revision 3229

Show
Tim Anderson added a comment - Fixed price change events weren't being generated preventing the calculation of costs in the parent act. Fixed in vpms, revision 3229

People

Vote (0)
Watch (0)

Dates

  • Due:
    Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4#649-r158309) | Report a problem
Powered by a free Atlassian JIRA open source license for OpenVPMS Ltd. Try JIRA - bug tracking software for your team.