We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

Re: RE:[sap-log-mm] SOD: ME21N - MM01 - MM02

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from elrise on Jul 16 at 11:58 AM
System plus system and do 2 create Vendor
from another away pc.
And the sap can put small gsma in pc out linder doces and plus 2 from them
can protect the error from virus and continue your
1 system countian the other technology.

---------------Original Message---------------
From: Brian Healy
Sent: Tuesday, July 15, 2014 2:10 PM
Subject: SOD: ME21N - MM01 - MM02

This is not necessary in violation of SOD as only one Tcode actually is involved with the purchasing cycle and that is purchase orders maintenance.
There are two other transactions that would be in direct conflict and they are receipts and invoice approval.
That is, purchasing should involve a three-way match - Purchase Order / Goods Receipt / Invoice Payment. Combine any two of the three and you can have embezzlement without collusion.

Brian Healy
NIBCO INC.

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2014 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
elrise  
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Become a blogger at Toolbox.com and share your expertise with the community. Start today.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language