2D/3D printers (e.g. Zebra)
SE24 Class Builder
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
It is of great importance to keep the knowledge of SAP Basis experts in the company transparent. One possibility is of course to "look over the shoulder" or to ask the expert directly. However, this is very time-consuming and puts a strain on the expert himself.
INCENTIVES TO CREATE NEW ROLES
The comprehensive analysis provides the pattern and roadmap for the next steps. This also includes the right sizing, the selection of the monitoring concept and the appropriate deployment model, i.e. on-premise, cloud or hybrid cloud. Only with this planning can you ultimately achieve the desired goal - with transparent costs.
Verify that the data file was generated. If it was not created, make sure that the [Page 10] Recreate Data File settings in SPAM settings are enabled. For more information, see Note 70752. ADD_TO_BUFFER In this step, the queue is placed in the transport buffer of your system.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
It is also the task of the SAP basis to identify the skills and resources necessary for them and to ensure their existence at an early stage.
You can also define the roles according to a different scheme.