1. Sap Asap Methodology Steps

INTRODUCTIONThis plan addresses SAP R/3 profiles and authorizations to support. Client Name.’s control objectives as part of the EWMS project. The main deliverables of this plan are:- profiles and authorizations tested and delivered to the production client,- documentation,- documented process for future enhancements,- guidelines for production user-id assignment.Note that since the project’s mandate is to deliver a “vanilla” SAP system, new authorization objects or custom code modifications will not be made (although requirements may be identified for future project phases). The authorizations implemented as a result of this plan will be built off of existing authorization objects and SAP code.Profiles and authorizations development will follow a four stage cycle. These stages are:- Initiation,- Requirements Definition,- Design / Build,- Unit Test.The timing and responsibilities for these stages is outlined in the Gantt chart attached to this plan and fits with the existing project schedule and team organization. Documentation will reside in the R/3 Toolkit, consistent with all other project documentation. For convenience, Microsoft Access is used extensively for ad-hoc reporting on Authorization Objects, Classes, Profiles etc.The purpose of implementing controls in R/3 is to meet business control objectives.

When considering whether a profile is required, there should be at least one specific control objective referenced. An example of a specific control objective might be “to ensure only authorized staff will have access to update employee information”.

Sap Asap Methodology Steps

Another example might be “to ensure the risk of interruptions to the business is minimized.” Some generic examples are included below.