SAP BASIS or Business Application Software Integrated Solution or SAP NetWeaver is a set of programs and tools that serve as an interface with databases, operating systems, communication protocols, and SAP business applications including SAP FI, SAP CO, and SAP MM, among others. SAP BASIS enables SAP business applications to run and communicate with each other across disparate operating systems and databases. BASIS supports all SAP applications and allows users to monitor both SAP ABAP and Java Stack from one platform.
|Developer Trace||System Log||System Trace|
|When problems arise, Developer Trace stores technical information about those errors.||System Log is referred to have a look at recent logs for application server and CI.||System Trace is used to record internal activities that pertain to SAP systems. This helps identify internal problems.|
SAP BASIS supports a range of standard protocols. They are:
On top of that, SAP BASIS also supports the Unicode format.
- Tools for system monitoring and administration
- Business Server Pages for building online stores and portals
- Utilities for database monitoring and administration
- Resource management
- Transfer Modifications for improved accuracy
- Client–Server architecture and configuration
- GUI designing for customizing the presentation layer in SAP R/3 architecture
- SAP application server monitoring and system log analysis
- Performance tuning and improvement
- Database maintenance and restoration in case of technical disasters
- Solution Manager installations
- Managing SAP R/3 and NetWeaver
- Installing Transport Management Systems
- Creating users, assigning roles, and locking and unlocking users
- Background job scheduling and job monitoring
- Applying support patches and installing add-ons
There are two types of OPS$ user services:
These user services are important as they are created in the SAP system to connect and communicate with databases internally.
RFC or Remote Function Call is a mechanism which is used to communicate and exchange information between SAP systems. There are four types of RFCs. They are:
- Synchronous RFC (sRFC): This RFC executes the system call only when all involved systems are available.
- Asynchronous RFC (aRFC): This RFC executes the invoked function modules only once in the RFC server.
- Transactional RFC (tRFC): This is similar to asynchronous RFC, but in this case a transaction ID is involved to send multiple requests in case of errors.
- Queued RFC (qRFC): This is an extension of tRFC and is used to serialize tRFC calls in a queue.
These are described in detail on SAP community.
To export from tables in the OS level, users need to follow certain steps using the R3trans utility which is implicitly available in SAP.
- Fetch the list of tables to be exported
- Check if the target directory has the required disk space
- Create specific control files for R3trans. These files will be used for exporting purposes
|Support Package||Kernel||SAP Note|
|Support Packages are defined as a bunch of corrections that pertain to transaction ‘SPAM’.||Kernels contain executable files for executing applications when needed.||SAP Notes are implemented to remove errors in single transactions and independent programs.|
No, we cannot install SAP patches when other users are online. This is because Support Manager won’t be able to update the patch in the system. Rather, the patch will be terminated. It is therefore advisable to apply SAP patches on a system when no users have logged in to it.
Parameter tab: Allows administrators to assign T-codes to subordinates
Personalized tab: Required for RFC communication between systems and personal user information
Reference users: Reference users provide one user authorization to other users in case of emergency. GUI login is not possible for reference users.
Service users: Service users are anonymous users. Administrators change passwords for service users. However, it is possible for service users to login to the system multiple times.
Logon groups can be defined by using the transaction code ‘smlg’. Users must create logon groups in the first place and then assign instances to those logon groups.
There are three functional modules that can be used in sequence in BDC to enable the transfer of data within SAP systems. These modules are:
- BDC_OPEN_GROUP: This module is used to specify the name of the client, sessions, and username.
- BDC_INSERT: This module is used to ingest data for transactions.
- BDC_CLOSE_GROUP: This module is used to terminate the batch input session.
The OK code is used in SAP programs to execute functions or modules. OK codes improve execution time and help maintain the modularity of a program.
Business KPIs or Key Performance Indicators indicate the performance of companies at a strategic level. These indicators help businesses steer their course of action to the right track by which they can generate maximum profits.
SAPS or SAP Application Performance Standards are independent hardware units that indicate or describe the performance of a system configuration in any SAP environment.
Learn more about SAPS in SAP HANA Tutorial.
Users can use the transaction code ‘SM51’ to check if a system is Unicode or Non-unicode. Upon opening the application, users can click on the release notes button in the application tool bar to find information about a system being Unicode or Non-unicode.
Basically, there are four types of transport requests in SAP. They are:
- Customizing Request
- Workbench Request
- Transport of Copies
By default, SAP systems are installed in either English or German, though SAP systems are used throughout the world. Therefore, at times it becomes necessary to translate SAP systems to regional languages. But due to language gaps, the translation isn’t seamless all the time. To fill this language gap, a supplementation language is used.
Check out the Intellipaat SAP HANA Course to get a head start in your SAP career!