SAP Basis Determination of specific transactions with user assignment using SE16N - SAP Basis

Direkt zum Seiteninhalt
Determination of specific transactions with user assignment using SE16N
Presentation layer (graphical user interface)
By establishing a new role concept and building new roles, the SAP basis has the skills necessary to support new tasks and topics as well as to operate new technology and service forms. The relevant roles are listed below.

The definition, organisational structure as well as the naming of the SAP basis is historically conditioned by previous SAP software versions and components. This also results in the perception of the SAP basis and the related focus of the SAP NetWeaver and the ABAP system core, which is still widely used today. However, the scope of activities has changed significantly in terms of tasks and technology and will continue to change in view of SAP's perspective and product strategy and the changing roles of IT. In order to accommodate this change and to change perceptions both in the overall context of the SAP ecosystem and within its own company, the SAP basis must develop a new self-understanding and establish a marketing for the publication of its own performance. The underlying information can be found in the master thesis in chapters 7.4 and 9.2.
ASSESSMENT OF EXISTING CUSTOMER-SPECIFIC SOLUTIONS
In the case of client settings, you should ensure that the production client is protected against overwriting and that changes are only approved via the transport management system (TMS) to ensure traceability. In the interests of system security, changes to repository and client-independent objects should also not be permitted. The use of eCATT and CATT should also be at least restricted, as allowing them can lead to significant database changes.

Without this provisioning component, adjustments to employee permissions in the respective IT resources would have to be implemented by the relevant system administrators. However, manual provisioning processes are by their very nature a source of errors. If an employee's tasks change, the system administrator should consider all active user accounts when modifying and deleting accounts. A modern IDM system therefore helps companies to keep track of users and their permissions, especially in complex and heterogeneous system landscapes.

The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

Tools that work with status dependencies and then automatically start the next job when its predecessor job has been processed without errors can help here.

A subsequent hypercare phase is at least as understandable as the continuous optimization of your SAP systems, for example through performance analyses.
SAP BASIS
Zurück zum Seiteninhalt