11835 – Construction Sales Order – Invoice Totals

Version Reported In

Sicon Construction v221.0.37

Detailed Description

A Construction Sales Order has been raised.  The example below has two lines, one for a stock item and one for measured works. It currently doesn’t have an Application, Valuation or Invoice raised against it.

On the Application Details section of the Order you can see this information as per below:

When you raise an Application against the Sales Order, the system automatically links the Application against the Sales Order lines, you can see this within the Application on the Sales Order Lines tab:

This can also be seen on the Construction Sales Order against each line, you can see the Applied for Value.  This is because when you are raising the Application, this is done directly against the Sales Order lines so the system has a link.

If you raise a Valuation against the Application (not using the Populate Outstanding option) and allocate this against the Application, the system will lose the link for the Sales Order line.  This is because the association between the Application and Valuation is on the header level rather than the line level of the Application:

As this link is lost between the Sales Order line and the Valuation, the system can’t display the Invoice Total, when looking at the Sales Order as it doesn’t know what line has been invoiced.  Reminder: the valuation has only been allocated on a ‘header’ level of the Application.

Impact: Low/Medium

• Urgency | Ability to work not affected; inconvenient.
• Impact | All users affected.

Workaround

When entering the Valuation into the system. Use the populate outstanding button on the Valuation:

What this allows you to do is create the Valuation based on the Application lines.  So you can value each line independently and create a link between the Sales Order line, Application line and the Valuation line.

As the valuation now has the link, the Sales Order can show you the Invoiced Value of each line and the total invoiced value.

Development Priority Voting

Please let us know your development priority for this Known Issue by providing us with a star rating based on the below;

1. Not causing any problems – not a priority.
2. It’s annoying, but not causing too many problems – not a priority.
3. Would be nice to be fixed, but not essential – not a high priority.
4. It would be helpful to have this fixed – fairly high priority.
5. Really needs to be fixed as soon as possible – high priority.