As I don't know the rest of your application design, this is a shot into the blue, but have you tried setting the DEFAULT schema just like it is in the original procedure?
Could be that the object from the error message is actually present in another schema...
- Lars