Buyer Setup & Approval Escalations

Question

Hello,
Need your help on the below issue:
Today many people who have Standard PO & Blanket Release approval also have the ability to approve a Blanket Purchase Agreement.
As per our business policy, we are separating Blanket Release approval (Materials jobs only) & Blanket Purchase Agreement approval (Sourcing jobs only).
The issue we are having is that the Materials teams are still trying to update & approve Blanket Purchase Agreements and Sourcing is trying to update & approve Blanket Releases.
Because both groups are setup as a Buyer (required even to just view the PO form) Oracle allows updates to documents that there is not approval authority for and as a result the workflow automatically escalates through their supervisor chain - who also does not have approval athority which causes escalation straight to higher authority (Reference the example below)
Are you aware of any way to prevent editing of Releases or BPA's by teams that do not have job authority to approve them? We need to determine a systematic way to prevent these from escalating to upper management because someone has made a modification that should not.
Example
Subject: FYI: No approver was found for Blanket Purchase Agreement 6000016796
To               Strosin, Raphael
Sent               19-JAN-2011 02:44:16
ID               158036687
No Approver was found for Blanket Purchase Agreement 6000016796.
PO Amount:      EUR
Supplier: AMITRONIC OY
Supplier Site: LAHTI 101
Last Approver: Strosin, Raphael
Preparer: Oksanen, Sirpa
Please, find the correct approver and re-submit document for approval.
Purchase Order Lines
Line     Item Number     Rev.     Item Description     UOM     Quantity     Unit Price     Line Amount
1     72509     001     SEALING-EMI, TIIVISTE-EMI 8.9x2.8x4.75mm, L=38cm     Each          13.05     
2     M1037086     000     SEALING-EMI, Fingerstock Gasket, slot mount, one finger 7.874x6.35mm     Each          .12     
Approval Sequence
Sequence     Who     Action     Date     Note
7     Strosin, Raphael               
6     Erneberg, Jan     Forward     19-JAN-2011     
5     Vuola, Juhani     Forward     19-JAN-2011     
4     Matikkala, Mikko     Forward     18-JAN-2011     
3     Oksanen, Sirpa     Forward     18-JAN-2011     
2     Oksanen, Sirpa     Submit     18-JAN-2011     
1     Nadhan, Sendhil     Approve     20-JUL-2009     
0     Nadhan, Sendhil     Submit     20-JUL-2009     
Thanks,
Shilpa.

Answer 1

SP Dash,
I think he has already created 2 approval groups - say BPAGroup and ReleaseGroup.
His problem is that person from BPAGroup has access to modify a release. When he/she does that, since he does not have the Authority to approve, the Release approval goes all the way to somebody high up in the company.
He wants to restrict the access to make changes so this does not happen.
user11303545, a responsibility based personalization will work even if two responsibilities use the same PO screen. The CONTEXT will take care of that. But if you have other concerns, you can certainly use Karthik's suggestion of creating one personalization and adding a check on the buyer's job/position.
Hope this helps,
Sandeep Gandhi
Edited by: Sandeep Gandhi, Independent Consultant on Feb 21, 2011 9:41 AM