Does re-running allocation create duplicates or over-write existing allocation results?
Daily allocation result readings
The reading (Daily reading) is setup as multiple readings per day allowed.
A unique code(UUID) is generated for a unique combination of
product
disposition
date
Well-ID
A new reading number is generated every time a new unique code is seen for a reading.
What happens when data comes from allocation run results?
Every time a daily allocation result is being saved , a UUID is generated for the combination of (well, date, product, disposition). A check occurs to see if there is any reading with the same UUID.
If there is no reading with this UUID, then a new reading number is generated for this UUID. The daily result is stored alongside a new reading number.
If there is already a reading with this UUID, then that reading is updated with the latest data received (the reading number remains the same).
What happens when readings are manually created through the UI/ bulk upload??
No unique code(UUID) is created while saving an allocation result reading. A check is done for (date+reading_number).
If there is a match, then the existing reading is overwritten.
If there is no match, then a new reading number is created and the data is written to it.
No UUID is created and saved as part of this process.
What happens when readings are integrated/migrated?
Integration today does not provide a UUID along with the reading. It instead sends a reading_number. Anytime a new reading comes through integration without a UUID, a check is done for date+object+reading_number.
if found, then the reading is updated.
If not, then a new reading with a new reading number and randomly generated UUID is added. ( this UUID is not consistent with the one coming from allocations, logic used is different)
Exception scenarios
When the user creates the daily/monthly allocated volume result reading from the UI: Either bulk upload or manual entry.
When a user manually creates a reading from the UI: The reading number generated is “random” and not consistent with the logic used to generate from the allocation module. The same happens when the user bulk uploads the reading.
Since the reading numbers are manually assigned, the relation between “reading number and product + disposition combination “ is not consistent with that used by the allocation module.
This creates the following discrepancies.
The readings generated by the allocation process will not overwrite the existing reading which was manually created.
There would be two daily allocation result readings for the same product+disposition combinations for a well.
When a well for which allocations were already run is removed from one network and added to another and allocations are re-run for the same dates which were already allocated earlier.
This does not end up creating duplicate daily allocated volume results for same product+disposition combination. Instead, the results generated earlier are overwritten by the results created as an outcome of running allocations on the new network.
The new results would also save the “network-name” and “network-version-id” of the most recent network the well has been a part of (the network on which the latest allocation was run).
Related Articles
- What is the difference between Daily Ledger- Tanks, Daily Ledger Wells and Monthly Ledger - Tanks
- What dispositions in Joyn Allocations are locked-in ( not changeable)?
- Do calculated attributes calculate when I use bulk upload?
- How do I update formula meters in a pre-existing allocation network with a new calculation logic?
- Can you load sets of transactional files in multiple open tabs at the same time?
- Why isn't a meter showing up as a volume source?
- How do trigger allocations work?
- Can I run allocations by Purchaser or Production team?
- Why is a reading not showing up in my app?
- How do I configure a network to use downtime and flowing events for allocations?
- Does re-running allocation create duplicates or over-write existing allocation results?
- How do I create a calculation for a reading attribute?
- How do I configure a custom button and associate event readings to it?
- What does the exception found in "Wells Beginning and Ending inventory Mismatch" indicate?
- Can production accountants perform reconciliation at a different temperature/pressure base?