Stored procedure inserts 2 columns into a table with 3 columns that are not null, with no defaults on the table
Someone else figured it out. In production, there is a trigger on the view that was not in place in testing.

2 of us didn't think to look for a trigger on a view. Mystery solved.