Transaction code Description
SAP Business Application Programming Interface (BAPI)
Avantra recently became available in the Google Cloud Marketplace. It is worth mentioning here that we have fully containerized the deployment of Avantra here, so each component runs in a separate container. For the database, we use Cloud SQL.
The application layer is the central component of the SAP R/3 system. This layer is therefore also referred to by SAP as the actual base system. Within the layer there are application servers and a message server.
SM37 Simple Job Selection
Automatic error handling when a job is aborted is desirable and useful in most cases. The conscious processing and consideration of error situations in job chains - also at step level - can help to reduce manual effort. Error situations should be catchable: If they are non-critical elements, the following job can perhaps be started anyway. In the case of critical errors, a new attempt should be made or an alert issued so that an administrator can intervene manually. Simple batch jobs are usually not capable of this. The goal of an automated environment is not to have to react manually to every faulty job.
Before SAP HANA was released, there was no SAP database - you had to install SAP ERP (or the application you were using) on a third-party database, such as Oracle or SQL Server. SAP developed the HANA database to fully leverage the power of SAP's next-generation S/4 software.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
The data is stored unencrypted in RAM.
If you want to have all transaction codes listed, you can have a look at this article.