 | ABAP Performance Tuning - Tips and Tricks (http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_Introduction.asp)
|
 | BASIS and Security Authorization (http://www.thespot4sap.com/Articles/SAP_BC_Security_Components.asp)
|
 | Bus Connector and XML Conversion (http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp)
|
 | Business Warehouse (http://www.thespot4sap.com/Articles/SAP_BW_Introduction.asp)
|
|
|
 | Designing SAP Transactions (http://www.thespot4sap.com/Articles/SAP_Design_Introduction.asp)
|
 | How does the SAP system maintain user authorizations? (http://www.freeitsolutions.com/website/?name=SoD/in/SAP&pageId=39) So we have users on the one hand, and what they can do on the other hand. In SAP the user "can do" things through transactions (create a sales order, issue a billing, etc).
To ensure that a user has the appropriate authorizations when he or she performs an action, users are subject to authorization checks.
The following actions are subject to authorization checks that are performed before the start of a program or table maintenance and which the SAP applications cannot avoid:
· Starting SAP transactions (authorization object S_TCODE)
· Starting reports (authorization object S_PROGRAM)
· Calling RFC function modules (authorization object S_RFC)
· Table maintenance with generic tools (S_TABU_DIS)
Business conflicts between duties that a user can be represented in a duties conflict matrix. Segregation of duties can therefore be enforced using this conflict matrix.
|
 | Integrating XML with SAP Business Connector (http://www.thespot4sap.com/Articles/SAP_XML_BC_Integration_Benefits.asp)
|
 | Integration Using ALE (http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp)
|
 | Lotus Notes Integration (http://www.thespot4sap.com/Articles/SAP_LN_Lotus_Notes_Introduction.asp)
|
 | Mobile Engine (http://www.thespot4sap.com/Articles/SAP_Mobile_Engine_Introduction.asp)
|