Typically, you would not have individuals performing all three functions (create a PO/stock transport order, enter a GR and enter an IR).There should be segregation of duty controls in place to prevent this.
You might want to post something to the SAP security group. You should be able to restrict the creation, maintenance, etc. of STO's to a different group. Perhaps you create a unique purchasing group(s) to add an additional layer of authorization checks when STOs are involved.
?
--- On Mon, 10/4/10, John_Mitchell via sap-log-mm <sap-log-mm@Groups.ITtoolbox.com> wrote:
From: John_Mitchell via sap-log-mm <sap-log-mm@Groups.ITtoolbox.com>
Subject: RE:[sap-log-mm] Separating Inter-company STO creation from normal PO creation
To: "Anna Bosak" email@removed
Date: Monday, October 4, 2010, 5:47 PM
Posted by John_Mitchell
on Oct 4 at 5:46 PM
Mark as helpful
Thank you, all.
In fact, I did create a new document type only for STO's (ZNB), a copy of the NB document type. I have a security role to match, allowing only ZNB document type, but it does not prohibit someone with the role from selecting a normal vendor, and posting both a GR and a IR. It does perform as expected of an STO - create delivery, PGI, etc....
I love a good mystery....
John
---------------Original Message---------------
From: John_Mitchell
Sent: Saturday, October 02, 2010 12:46 PM
Subject: Separating Inter-company STO creation from normal PO creation
> We want to have buyers create normal PO's, but have another group only create inter-company STO's and not normal PO's. Today we are using doc type NB for both PO's and STO's. Anybody have experience with this?
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Related Content White Papers
In the Spotlight  _.____.__ |
Mark as helpful
