As far as I am aware there's only one instance of the relevant DSP, generated from the menu code in NAVSVC, those options are indeed there.
I suspect the issue is because several operations on this DSP have been called with different scope entries, but I do not understand scope and its requirements/limitations enough to work them through.
I was hoping there was some way of unpacking the information held in the uniface data on the browser, to see what scope(s) were in effect, from which I could track the operations and ensure their scopes were in sync.
As I say, at the time the error is being displayed, NO proc is being fired at all, and the most recent DSP to be used in the HOME container is not the one complaining about scope. It fires on running the B_CLOSE code, so it may well be trying to go back to the screen about which it is complaining, but that is conjecture, as I can't track or debug what it is doing.
Regards,
Iain