Create your own text on SAPGUI logon screen

We can add some information on the logon screen, when the user is asked for username and password.
The information shown can be in text format, SAP symbols, SAP icon, and also bitmap graphic. But I still don’t know how to display a bitmap graphic on logon screen 🙂

Go to transaction SE61 and select “General text” in document class.
You can define the language in your own system language (defined in the profile parameter zcsa/system_language).

Create a document with the name “ZLOGIN_SCREEN_INFO”.
Then you can add text as you want.

You can also add SAP icons by selecting menu Insert → Characters → SAP icons.
The complete list of the SAP icons can be shown in report RSTXICON in transaction SE38.

Save the document, and try opening the SAP logon screen. For further information, you can display SAP note 205487.

Could I put my own logo in the SAP initial screen?

Yes. We can change the logo in the right-hand side of the initial screen.
The logo picture can be in any bitmap format, as long as the MIME types in maintained well.
Go to transaction SMW0 and choose “Binary data” option.
Maintain the MIME type (if you’ve not maintained yet) in menu Settings → Maintain MIME types.
Create new MIME type as you wish, with the extension of the bitmap.

For example, if your picture is in JPEG type, you can create type “image/jpeg” with the extension of “*.jpg” and “*.jpeg”.
Then create new object repository, for example Z_SAP_LOGO, and locate your own logo picture.

You still need to put a little customizing in table SSM_CUST to activate your logo.
Go to transaction SM30 and change table SSM_CUST.

Add new entries name of “START_IMAGE” and fill the value with “Z_SAP_LOGO” which is created in SMW0.
Save the table view.
Now, every time you login into SAP, your own logo will appear.

Additionally, you can adjust the logo to the window size automatically, or center it in the right-hand side.
Just put entries of “RESIZE_IMAGE” and fill the value with “YES” (center size) or “NO” (window size) in table SSM_CUST.

Q&A About SAP Spool

Q: How do I restart the spool work process without restarting the SAP application?
A: You can use the transaction SM50. Choose the spool work process then select “proces → cancel without core”.
If you selected “restart after error → yes”, workprocess will be restarted and you will see the the error colon will get a red status.

Q: Can I switch other work processes to spool work processes without restarting the instance?
A: No. The internal structure of spool work processes is different from, for example, dialog work processes. Therefore, if you want to change the number of spool work processes, you must do this in the context of SAP profile maintenance (transaction RZ10) and then restart the instance.

Mail Interface with SMTP Plug-in in SAP

As of SAP Web Application Server 6.10, SMTP (Simple Mail Transfer Protocol) is supported directly by the SAP kernel. This means that it is possible to exchange e-mails between the SAP system and any SMTP-compatible mail server without using additional external components (such as connectors or gateways). You can use any product that meets the SMTP standard as a mail server.

As of SAP Web Application Server 6.20, it is also possible to exchange faxes and text messages (pager/SMS) using SMTP. Faxes and text messages are packed into e-mails for this purpose.

Further explanation can be showed here.

SAP Patch Manager (SPAM)

The SAP Patch Manager (SPAM) is the customer side of the Online Correction Support (OCS). Transaction SPAM lets you efficiently and easily imports SAP-provided support packages into your system.

Depending on the system used or the configuration of your system, you must apply different types of support packages. You can get the support packages in the SAPNet R/3 FrontEnd, the SAPNet Web FrontEnd, or on Collection CDs.

SPAM runs at the SAP transaction level, so that knowledge of the operating system is not required for handling the tool.

SAP now uses the term support package instead of patch.
Note that you can only use this transaction with SAP GUI for Java and SAP GUI for Windows.

The SAP Patch Manager offers you the following functions:

1.	Loading Support Packages
	You can load the Support Packages you need from the SAPNet Web FrontEnd, the SAPNet R/3 FrontEnd, or from Collection CDs into your system.
2.	Importing Support Packages
	a. Restart capability
	When you import a support package into your system, SPAM follows a predefined sequence of steps.
	If the support package process terminates, it can be resumed at a later point in time. Processing restarts at the step that failed.
	b. Displaying the import status in your system

You can find the import status in your system at any time using transaction SPAM. Transaction SPAM is integrated into the SAP upgrade procedure.

The SAP Patch Manager informs you of the status of the step currently being executed in the status bar. If you want to know which steps are executed for which scenario, run the program RSSPAM10.

The following list explains the steps executed by SPAM in the order in which they are performed.
PROLOGUE
In this step, the system checks if you are authorized to import support packages.
CHECK_REQUIREMENTS
In this step, various requirements are checked for importing a support package, for example, the transport control program tp logging on to your system.
DISASSEMBLE
In this step, files from the corresponding EPS parcels are disassembled, or unpacked, and stored in the directory.
ADDTOBUFFER
In this step, the queue is put into the transport buffer of your system.
TEST_IMPORT
In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the support package is imported.
IMPORT_OBJECT_LIST
In this step, the object lists for the support packages in the queue are imported into the system.
OBJECTS_LOCKED_?
In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the support package is imported.
SCHEDULE_RDDIMPDP
In this step, the transport daemon (program RDDIMPDP) is scheduled.
ADDON_CONFLICTS_?
In this step, the system checks if there are conflicts between objects in the queue and installed addons.
SPDD_SPAU_CHECK
In this step, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).
DDIC_IMPORT
In this step, all the ABAP Dictionary objects of the queue are imported.
AUTO_MOD_SPDD
In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.
RUN_SPDD_?
In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.
IMPORT_PROPER
In this step, all the Repository objects and table entries are imported. Then actions such as distribution, conversion, activation and generation occur.
AUTO_MOD_SPAU
In this step, the system checks if modifications can be adjusted automatically.
RUN_SPAU_?
In this step, you are asked to adjust your modifications to the repository objects by calling transaction SPAU.
EPILOGUE
In this step, the import of the support package is ended. The system checks if the queue has been completely processed.