ssolberg
VIP Member
Although we've used JDE for years, we have never really had a need to "lock down" Batch approvals and posting. Recently I was asked to look more into how it operates and I'm having a bear of a time figuring it out. I've read the documentation and also the KG doc wfn-03-0002 about it and I still don't seem to have it and I've even tried it in a test environment. So hopefully someone can clear the cobwebs for me...
As an example, I have 5 people:
BOSS (the dept mgr)
FRED
SHARON
BOB
NEWBIE
We want the BOSS to be able to Approve anybody's batches but FRED, SHARON, BOB, and NEWBIE cannot approve any batches. BOSS can post anybody's batches.
FRED, SHARON, and BOB can post their batches once they have been approved by BOSS but they should only be able to post their own batches. NEWBIE can never post anything.
How should such a thing be setup? And where does the *ALL option come into play. I'm well versed in Action Code Security (and other securities) but this seems "backwards" and potentially lots of table maintenance to get everyone setup correctly?
As an example, I have 5 people:
BOSS (the dept mgr)
FRED
SHARON
BOB
NEWBIE
We want the BOSS to be able to Approve anybody's batches but FRED, SHARON, BOB, and NEWBIE cannot approve any batches. BOSS can post anybody's batches.
FRED, SHARON, and BOB can post their batches once they have been approved by BOSS but they should only be able to post their own batches. NEWBIE can never post anything.
How should such a thing be setup? And where does the *ALL option come into play. I'm well versed in Action Code Security (and other securities) but this seems "backwards" and potentially lots of table maintenance to get everyone setup correctly?