Planning & Design
Creation of documentation
SAP Basis is structured as a classic three-tier model. It contains the following components:
Test of EDI data transmission In the transaction WE05 all incoming and outgoing messages and IDocs as well as the status of the IDocs are displayed. If the order data is correctly entered and the partner profile is correctly configured, the IDoc is listed as successfully processed.
High sense of responsibility
The main benefit of the implementation of the above recommendations lies in the creation and documentation of the innovative power of the SAP basis. Through consistent research and testing, the SAP basis is enabled to assume its role as an innovation driver. It also creates an attractive and exciting working environment for employees. By being involved in projects in a timely manner, project success will be promoted and will contribute to company success in the medium and long term. One possible consequence of the constant overuse of the employees is the reorientation of the employees and the associated loss of knowledge. This can also lead to the complete basic activity being carried out by external partners, to which a dependency relationship then arises.
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
It is possible to specify a trace level for each rule in the ACL file to monitor each communication channel individually. It can be used with SNC without any further configuration. The use of the file is controlled by the gw/acl_file parameter by simply setting it to the appropriate file name. Use of external programmes If an external programme wants to communicate with your SAP system, it must first register at the gateway. The programmes which this is approved are controlled by the reginfo ACL file. This defines rules that allow or prohibit certain programmes. The syntax of the file allows you to define not only the name of the programme, but also the host on which the programme runs and hosts that can use and exit the programme. The gw/reg_info parameter must be set to use this file. In addition, there is the ACL file secinfo, which allows to configure which users can start an external programme. This defines rules that allow certain usernames from the SAP system to use certain external programmes. In addition, you can also define the hosts on which these programmes will run. For example, it is possible to allow a user to run the programme "BSP" on the host "XYZ", but not on the host "ABC". This file is controlled by the gw/sec_info parameter. Using the gateway as a proxy Since the gateway of your SAP system can also serve as a proxy server, the prxyinfo ACLDatei should also be activated via the gw/prxy_info parameter. Suppose you have 3 SAP systems in your network: SRC, TRG and PRX. If SRC cannot communicate directly with TRG, but both with PRX it would be possible to use the gateway of the PRX system as a proxy server, i.e. to communicate via it. So, in order to prevent this from happening to everyone, this property should be urgently restricted. As with the other ACL files, rules are defined which hosts can communicate with which hosts via the gateway. The syntax of the different ACL files may vary depending on the release level. It is therefore advisable to read them in the appropriate SAP documentation before activating the ACL files. You can also find more support for using ACL files in the SAP Community Wiki.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
In order to explain the relationship between TREX and SAP Solution Manager, I would like to ask you a question first.
If you are running a multi-system landscape with a common transport directory, it is convenient to enable this option only in the first system you are inserting support packages into, and to disable it in the following systems.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.