This is another implementation of !750 (closed) and !789 (closed)
This depends on erp5!2282 (merged)
The consumptions are not registered as Internal Packing List, without any source/destination _section, and not source.
The only arrow set is the destination, linked to the seller Organisation.
In short, there is not information about the customer on it.
The Internal Packing Line defines the consumption resource with its quantity.
The Software Instance/Slave Instance/Compute Node related to the consumption is linked as aggregate.
Once per day, an Alarm gather all Internal Packing Line without any grouping_reference, and tries to generate a monthly single Sale Packing List per customer.
So, it look for the current item customer.
The Sale Packing List is generate to match the current invoicing process (as generated by the Open Sale Order), with start/stop_date matching the current invoicing period.
A single Sale Packing List Line is monthly created by resource: quantity are accumulated.
There is not aggregate relation.
price is calculated by this alarm.
Used Internal Packing Line get a grouping_reference.
There are 2 processes generating Internal Packing List:
- TioXML files extraction
- monthly consumption (using
Open Internal Order) of every Instance and Compute Node