Debbie Hagen

"Send only remaining values" allocation rule

Blog Post created by Debbie Hagen Employee on Oct 8, 2018

Happy Monday everyone!

 

I've come across another topic that I get asked about sometimes in class, lab assist or on AAI that I thought I'd try to clarify for the Apptio Community.  It's related to allocation rules and that option in the From part of your allocation screen.

 

"Send only remaining values" (after other rules run).

 

I've noticed some of you using it when trying to complete your Cost Source to Vendor or Cost Source to OCP allocations with unsatisfactory results and I wanted to clarify what it does and when you might use it.  Before writing this I synced up with one of my super smart people Mark Nealey and he helped me explain it in simple terms.  He can add on or clarify if needed. 

 

First, what the "Send only remaining values (after other values run) does, it says, take whatever is left after ALL of my other rules are applied and send those up. It's the leftover costs that I don't necessarily know how to account for. 

 

Here's how Mark explained it to me:

 

Let's say I owe people 30 dollars.  I know I owe Rhonda Keller $10 and I know I owe Julie Batty $10 but I don't remember who the last $10 goes to.   I would use the "send only remaining values" option to just divide it up into small pieces and give it to everyone else on the planet (or at least on TBM Connect ). 

 

The benefit is that I have a fully allocated model, with no fallout. 

 

The caution:

However, I do want to caution you from applying this option just to get a clean model.   Many people view fallout as a bad thing (which it is, in a way), but what it really is, is the opportunity to understand why those costs are falling out, and work on improving our data or our allocations so we can understand and correct where that cost should actually go.  

 

One other caution I'd offer is that you want to be careful what other allocations you apply when you apply this rule.  For example, if you create 2 outbound allocations, and set them both to "send only remaining rules (after other rules run)"  you'll create a deadlock.  This is because it can't run line 1, until line 2 runs and it can't run line 2 until line 1 runs. Therefore it's deadlocked and can't process either allocation.

 

Finally, don't interpret this blogpost to mean that you shouldn't use this option.  It has it's benefits as long as you understand what it's doing with those leftover costs.  We just want to caution you that we shouldn't use it just to make your model tie out top to bottom/left to right.  Here are two related articles I found useful on this topic. If you've read/posted other related articles or have feedback, feel free to comment.

 

Model Fallout - Friend our Foe? 

Using Ungoverned spend to communicate with TBM customers 

Outcomes