How to setup allocations, if readings start date is not the start of the month?

If transaction data is only loaded for the network objects for part of a month, in this example from July 10, and there are no valid allocations on the network prior to that, two problems are created:

1. You cannot initialize networks on the last date of the month (June 30 in this example) because initialization logic does not allow you to load the ledger inventories for a date which is outside the network’s effective date range.

2. Running allocations for July will overwrite/update inventories for 10th of July and later.

There are two ways to resolve these problems:

Solution 1

1. Create the network with an effective date starting from July 9.

2. Load the network initializing inventories for July 9.

3. Change the start effective date of the network to July 10 so that inventories for July 9 are never overwritten.

• Monthly allocations for the network always run from July 10.

• Inventory updates from July 10 will always consider July 9 ending inventory as the beginning inventory from July 10.

• Even without locking allocations for July, the initialized inventories are safe from being overwritten.

Solution 2

1. Create the network with an effective date of June 30.

2. Initialize ledger on June 30.

3. Run Allocations for the network for the month of July.

4. Since there is no transaction date for the network objects, ledgers carry forward from June 30 to July 9, and the starting inventory for July 10 is equal to the initialized inventory.

5. Monthly allocated volumes are the same as in Solution 1.

• Daily allocations from July 1-9 yield 0 allocated volumes and contribute 0 to the monthly allocated volume.

• Daily allocations from July 10-31 will show appropriate volumes and be aggregated to monthly allocated volume results.

Related Articles