elindholm
edited for content
We've debated endlessly on this board whether it is possible to combine a trade exception with a player in order to bring over a larger-salaried player. Some of us thought it was possbile as long as the new player fit under the salaries, not requiring the 25% fudge factor. Others thought maybe it wasn't possible even then.
I e-mailed Larry Coon a couple of weeks ago and he finally responded. My questions are in blue, his answers are in red.
Can a $3 million trade exception be combined with a $1 million player to bring in a $4 million player? This would not violate the "only one exception per trade" rule.
You can't combine two trade exceptions like that. There's no such thing as an "only one exception per trade" rule, as it's common to use multiple exceptions in the same trade -- for example, a team could receive two players, one with the assigned player exception, the other with the minimum salary exception. What can't be done is using two exceptions on one player, and in your example, two exceptions (two distinct trade exceptions) are being used.
However, some of us are confused about the rule stating that a non-simultaneous trade can involve only one player being moved out. If the trade that originally created the (so-called) trade exception moved out one player (say, the Suns' Joe Johnson), then wouldn't moving out a second player (the $1 million guy, say, the Suns' Leandro Barbosa) to "complete" the trade violate the condition?
No -- the key is "aggregation," which is the term the league uses to denote combining the salaries of multiple players at the same time for trade purposes. A trade that involves aggregation cannot give rise to a non-simultaneous trade.
So basically he's saying that, no, you can't combine a trade exception with a player in order to bring over a larger salary, but the reasons aren't exactly as we understood them.
Unfortunately this means we can forget about using the Johnson exception to bring a player with a large-ish salary in the middle of the year. Whatever is left of the exception ($3.5 million or so, I think) is it. The Suns can combine players in a trade according the usual fudge-factor rules, but that's a different situation.
I e-mailed Larry Coon a couple of weeks ago and he finally responded. My questions are in blue, his answers are in red.
Can a $3 million trade exception be combined with a $1 million player to bring in a $4 million player? This would not violate the "only one exception per trade" rule.
You can't combine two trade exceptions like that. There's no such thing as an "only one exception per trade" rule, as it's common to use multiple exceptions in the same trade -- for example, a team could receive two players, one with the assigned player exception, the other with the minimum salary exception. What can't be done is using two exceptions on one player, and in your example, two exceptions (two distinct trade exceptions) are being used.
However, some of us are confused about the rule stating that a non-simultaneous trade can involve only one player being moved out. If the trade that originally created the (so-called) trade exception moved out one player (say, the Suns' Joe Johnson), then wouldn't moving out a second player (the $1 million guy, say, the Suns' Leandro Barbosa) to "complete" the trade violate the condition?
No -- the key is "aggregation," which is the term the league uses to denote combining the salaries of multiple players at the same time for trade purposes. A trade that involves aggregation cannot give rise to a non-simultaneous trade.
So basically he's saying that, no, you can't combine a trade exception with a player in order to bring over a larger salary, but the reasons aren't exactly as we understood them.
Unfortunately this means we can forget about using the Johnson exception to bring a player with a large-ish salary in the middle of the year. Whatever is left of the exception ($3.5 million or so, I think) is it. The Suns can combine players in a trade according the usual fudge-factor rules, but that's a different situation.