USR02 SAP Table - Logon Data

Field	Data Element	Data Type	length	Checktable	Description
MANDT	MANDT	CLNT	000003	*	Client
BNAME	XUBNAME	CHAR	000012		User
BCODE	XUCODE	RAW	000008		Initial password
GLTGV	XUGLTGV	DATS	000008		Valid from
GLTGB	XUGLTGB	DATS	000008		Valid through
USTYP	XUUSTYP	CHAR	000001		User Type
CLASS	XUCLASS	CHAR	000012	USGRP	User group
LOCNT	XULOCNT	INT1	000003		Number of failed logon attempts
UFLAG	XUUFLAG	INT1	000003		User Lock Status
ACCNT	XUACCNT	CHAR	000012		Account number
ANAME	XUANAME	CHAR	000012		Creator of User Master Record
ERDAT	XUERDAT	DATS	000008		Creation Date of User Master
TRDAT	XULDATE	DATS	000008		Last Logon Date
LTIME	XULTIME	TIMS	000006		Last Logon Time
OCOD1	XUCODE	RAW	000008		Initial password
BCDA1	XUBCDAT	DATS	000008		Date of Last Password Change
CODV1	XUCODEVERS	CHAR	000001		Password Code Vers.
OCOD2	XUCODE	RAW	000008		Initial password
BCDA2	XUBCDAT	DATS	000008		Date of Last Password Change
CODV2	XUCODEVERS	CHAR	000001		Password Code Vers.
OCOD3	XUCODE	RAW	000008		Initial password
BCDA3	XUBCDAT	DATS	000008		Date of Last Password Change
CODV3	XUCODEVERS	CHAR	000001		Password Code Vers.
OCOD4	XUCODE	RAW	000008		Initial password
BCDA4	XUBCDAT	DATS	000008		Date of Last Password Change
CODV4	XUCODEVERS	CHAR	000001		Password Code Vers.
OCOD5	XUCODE	RAW	000008		Initial password
BCDA5	XUBCDAT	DATS	000008		Date of Last Password Change
CODV5	XUCODEVERS	CHAR	000001		Password Code Vers.
VERSN	XUVERSION	CHAR	000003
CODVN	XUCODEVER2	CHAR	000001		Password Code Vers.
TZONE	TZNZONE	CHAR	000006	TTZZ	Time Zone
PASSCODE	PWD_SHA1	RAW	000020		Password Hash Val.(SAH1, 160 Bit)
PWDCHGDATE	XUBCDAT	DATS	000008		Date of Last Password Change
PWDHISTORY	XUPWDHIST	INT1	000003		External Password History(USRPWDHISTORY)
PWDLGNDATE	XULPDAT	DATS	000008		Date of Last Password Logon
PWDSETDATE	XUSPDAT	DATS	000008		Date: Password Reset by Administrator
PWDINITIAL	XUPWDINIT	INT1	000003		Indicator: Password Is Initial
PWDLOCKDATE	XUPLDAT	DATS	000008		Date: Password Lock
PWDSALTEDHASH	PWD_HASH_STRING	CHAR	000255		Password Hash Value

SAP GUI Logon Pad Backup and Restore.

Backing and Restoring SAP Logon Pad entries from one system to another system.

The paths for Windows XP/Vista/7 are as follows:

• Windows XP: C:\Documents and Settings\<username>\Application Data\SAP\Common
• Windows Vista/7: C:\Users\<username>\AppData\Roaming\SAP\Common

• If you install SAP GUI for Windows ≥ 7.20 the first time on a client:
• After having installed SAP GUI, you start SAP Logon for the first time. The saplogon.ini file will be automatically created in the Common directory mentioned above. Use SAP Logon to create the necessary entries. Your configuration will be saved in the corresponding newly created configuration file(s).

• If you upgrade an existing SAP GUI for Windows to release ≥ 7.20:
  • After having upgraded the SAP GUI, you start SAP Logon for the first time. SAP Logon will now search for the default saplogon.ini and sapshortcut.ini files used in the former SAP Logon release in the known locations: the SAP GUI installation or the Windows directory.
  • SAP Logon will then copy the existing saplogon.ini and sapshortcut.ini files to the Common folder, so that the former configuration details can be used again with the upgraded SAP GUI. The old versions of the *.ini files used with previous SAP GUI releases will remain in the former locations to allow going back to older SAP GUI releases, if this should ever be required. However, note that entries you added in SAP Logon as of SAP GUI for Windows 7.20 will not be added to the *.ini files in the old locations.

Standard Background Jobs in SAP

In SAP, a few jobs are scheduled to run periodically , to make system stable.

Following is the list of some important SAP background jobs which has to run periodically.

Job Name	Program	Frequency
SAP_COLLECTOR_FOR_PERFMONITOR	RSCOLL00	Hourly
SAP_REORG_JOBS_<CLIENT>	RSBTCDEL	Daily
SAP_REORG_SPOOL_<CLIENT>	RSPO0041	Daily
SAP_REORG_BATCHINPUTL_<CLIENT>	RSBDCREO	Daily
SAP_REORG_ABAPDUMPS	RSSNAPDL	Daily
SAP_COLLECTOR_FOR_JOBSTATISTIC	RSBPCOLL	Daily
SAP_REORG_TEMSE_CHECK_<CLIENT>	RSTSOO20	Weekly
SAP_REORG_JOBSTATISTIC	RSBPSTDE	Monthly
SAP_REORG_IDOC_<CLIENT>	RBDCPCLR	Monthly
DBA_CHECKOPT..*	RSDBAJOB	Weekly
DBA_ANALYZETAB..*	RSDBAJOB	Weekly

What are SAP Notes? Where do I can find them? How to use it?

SAP notes are part of SAP service portal. In simple terms, it is SAP'sKnowledge Base that specifically addresses known issues in SAP system. It is continually updated as SAP customers report issues in SAP system and SAP releases note with detailed instructions on how to fix / address the issue.

In single word , SAP Note is the correction / solution provided by SAP . Some notes we can deploy directly using transaction SNOTE. http://service.sap.com/notes

Where can I find the Sap Notes?

The SAP Notes are an online documents published by SAP AG on Marketplace https://service.sap.com

After you login with your S-user you can search for a sap note by clicking onHelp&Support and the click on tab Search for Sap Notes or from SAP system in transaction SNOTE:

How to implement SAP notes?

The Sap Notes can be implemented with SAP Note Assistant. The SAP Note Assistant is called with the sap transaction SNOTE. The SAP Note Assistant is part of the standard system since Basis release 6.10. In earlier releases, you can import it as an additional software component, as an add-on with transaction SAINT. To implement the SAP Note into your system, select the note on the initial screen of the Note Assistant and choose Implement Note.

SAP Notes are implemented with the Note Assistant in the following steps:

1.         You have to localize the required SAP Notes on the SAP Service Marketplace, for example, by searching for keywords or selecting the SAP Note number

2.        You can then load these SAP Notes to the development system with the Sap Note Assistant.

3.        The SAP Notes are checked by the Note Assistant . It checks whether the release named in the SAP Note and the Support Package level is correct, whether the SAP Note requires other SAP Notes before it can be implemented.

4.       The SAP Note is implemented by pressing the import button. This creates a transport request.

5.        The result of implementing the SAP Note is tested in  the development system.

6.       If this test is successful, the transport request is imported to the quality assurance system.

7.        If there are no problem then the transport request is imported to the production system.

The Sap Note Assistant is very important important because:

·           Automatically implement SAP Notes which handle ABAP source code corrections .

·           Handle dependencies with other SAP Notes, Support Packages, and modifications

·           Display all SAP Notes implemented in the system

·           Correct only a single bug, not a replacement for Support Packages

Very important:

   1. Sap Notes cannot change ABAP Dictionary objects

   2. Changes to SAP objects that are introduced using the SAP Note Assistant do not require an SSCR key.

  3. Sap Notes should be implemented in the test system first and after transported into quality and productive system.

SAP Basis Consultant?

Basis, the engine powering SAP’s R/3 and ECC solutions, provides system administrators the tools to keep the SAP environment alive and healthy. And like a preeminent automotive service center, our Basis mechanics are adept at finely tuning the engine to maximize your benefit output. Our skills include transport management, system monitoring, backup and recovery, hot/support pack upgrades, kernel upgrades, system refreshes/copies, user/role administration, and disaster recovery services. 

Every SAP system needs infrastructure administration. And whether it’s R/3 or ECC, SAP calls that “Basis”. With the proliferation of offshore Basis services, and the introduction of NetWeaver, it’s easy to get confused as to what a Basis Consultant really does. Basis Consultants do everything you need to keep the SAP engine running smoothly. This includes:

§   “Tier 1” support services: The most straightforward, and commoditized services, this includesmonitoring the system and insuring that all programs are running. If something gets stuck in a processing queue, it’s up to them to clear the blockage.

§  “Tier 2” support services: When a problem occurs, it’s one thing to fix the symptom (i.e. unblock the queue), it requires additional expertise to reconcile why it went wrong, and fix the real cause. In other words, “Tier 1” administrators turn to “Tier 2” consultants to perform root cause analysis. Tier 2 experts understand what each part of the system does, and how these parts interconnect. They can both trace a problem in one part to the cause in another, and tune each part to make your system run smoother.

§  “Tier 3” support services: Whether fixing a problem or improving the system, when it’s time to dig into the underlying ABAP code that drives SAP, this requires Tier 3 services. While not necessarily programmers themselves, these experts have dealt with enough code to know what should happen, and identify and fix what is happening. As a result of their prowess, these consultants affect technical upgrades, assist in new installations, and are the ultimate problem solvers in case of disaster recovery.

What are the functions of SAPOSCOL ?

• What is SAPOSCOL ?

SAPOSCOL is an operating system collector. It is a standalone program that runs in operating system background.

• What are the functions of SAPOSCOL ?

SAPOSCOL collects data about operating system resources like

ü  CPU Utilization

ü  Usage of Physical Memory

ü  Usage of Virtual Memory

ü  Usage of filesytems

ü  Usage of Physical disks

ü  Usage of running processes

SAPOSCOL runs exactly once per host and runs independently of the sap system.

By default, SAPOSCOL collects data every 10seconds and records it. It also records the hourly average statistics for the last 24hours in shared memory. This data will be fetched by background job “SAP_COLLECTOR_FOR_PERFORMANCE” and writes it to the MONI performance database table.