johndanter
Legendary Poster
Hi List,
I am on a multi company implementation of E1 and we use Row Security to control what a user sees/touches.
I have a problem with R09801 whereby certain users are running R09801 for a 'range' of batches on F0011.
F0011 doesn't have MCU but F0911 does. So the R09801 is flagging the F0011 before trying to process the F0911 and then obviously the F0911 batches isn't posted due to Row Security.
I've looked at the UBE and even if I hard code MCU into the various VERS of R09801 this problem still exists.
Now in an ideal world, they should only be posting batches that belong to their MCU, but how do you guys govern this kind of thing?
Do you have issues with your R09801 posters?
If R09801 updated F0011 AFTER trying to processes the F0911, there may not be an issue. Are there any ESUs to address this?
Thanks
John
I am on a multi company implementation of E1 and we use Row Security to control what a user sees/touches.
I have a problem with R09801 whereby certain users are running R09801 for a 'range' of batches on F0011.
F0011 doesn't have MCU but F0911 does. So the R09801 is flagging the F0011 before trying to process the F0911 and then obviously the F0911 batches isn't posted due to Row Security.
I've looked at the UBE and even if I hard code MCU into the various VERS of R09801 this problem still exists.
Now in an ideal world, they should only be posting batches that belong to their MCU, but how do you guys govern this kind of thing?
Do you have issues with your R09801 posters?
If R09801 updated F0011 AFTER trying to processes the F0911, there may not be an issue. Are there any ESUs to address this?
Thanks
John
Last edited: