Table with list of activity types.

Table with list of activity types.

01 Create or generate
02 Change
03 Display
04 Print, edit messages
05 Lock
06 Delete
07 Activate, generate
08 Display change documents
09 Display prices
10 Post
11 Change number range status
12 Maint.and gen.change document
13 Initialize number levels
14 Field select.:Generate screen
15 Field select.:Assign table
16 Execute
17 Maintain number range object
18 Deliveries from coll. proc.
19 Invoices from coll. proc
20 Transport without translation
21 Transport
22 Enter, Include, Assign
23 Maintain
24 Archive
25 Reload
26 Change customer account group
27 Display totals records
28 Display line items
29 Display saved data
30 Determine
31 Confirm
32 Save
33 Read
34 Write
35 Output
36 Extended maintenance
37 Accept
38 Exercise
39 Check
40 Create in DB
41 Delete in DB
42 Convert to DB
43 Release
44 Flag
45 Allow
46 Merge
47 Borrow
48 Simulate
49 Request
50 Move
51 Initialize
52 Change application start
53 Display application start
54 Display application archive
55 Change application archive
56 Display archive
57 Save archive
58 Display takeover
59 Distribute
60 Import
61 Export
62 Create automatic Ledger
63 Activate
64 Generate
65 Reorganize
66 Refresh
67 Translate
68 Model
69 Discard
70 Administer
71 Analyze
72 Plan
73 Execute Digital Signature
74 Revoke approval
75 Remove
76 Enter
77 Pre-enter
78 Assign
79 Assign Role to Composite Role
80 Print
81 Schedule
82 Supplement
83 Counterconfirm
84 Settle
85 Reverse
86 Rebook
87 Return
88 Exercise
89 Force Posting
90 Copy
91 Reactivate
92 Create from Template
93 Calculate
94 Override
95 Unlock
96 Reject
97 Set
98 Mark for release
99 Generate invoice list
A1 Accrue
A2 Pay
A3 Change status
A4 Resubmit
A5 Display reports
A6 Read with filter
A7 Write with filter
A8 Process mass data
A9 Send
AA Print Again
AB Settle
B1 Display permitted values
B2 Complete Technically
B3 Derive
B8 Execute Again
B9 Post Parked Document
BD Maintain obj. in non-OwnerSys.
BE IMG projection
C1 Maintenance of payment cards
C2 Display of payment cards
C3 Maintenance of manual auth.
C4 Develope Payment Card
C5 Reopen
C8 Confirm change
D1 Copy
D3 Detailed Display
DL Download
DP Delete plan
E0 Save extract
E6 Delete own extracts
E7 Delete external extracts
EP Prioritise extract
FP Change customer field selectn
G1 Maintain Budget
G2 Billing
G3 Maintain Overhead Costs
G4 Maintain Reevaluation
G5 Park
G6 Transfer Budget
G7 Reverse
GL General overview
H1 Deactivate
H2 Activate Logging
H3 Deactivate Logging
KA Activate notice
KI Knock In
KO Knock Out
KS Reverse notice
KU Give notice
L0 All functions
L1 Function range level 1
L2 Function range level 2
LM Change LDAP Mapping
LS Change LDAP Sync. Switch
MA Deactivate mod.assistant
P0 Accept CCMS CSM data
P1 Edit CCMS CSM data
P2 Maintain CCMS CSM methods
P3 Register CCMS CSM remote systm
PA Open Period
PB Close Period
PC Open Consolid. Grp Processing
PD Close Consolid. Unit Processng
PP Set Productively
PU Publish
RS Send to New Recipient
S1 Edit template
S2 Edit specification
SO Edit in Sourcing
SZ Assign Switch Framework Switch
U2 Compare business volumes
U3 Change business volume comp.
U4 Add business volume data
UL Upload
V1 Create version
V2 Change Version
V3 Display Version
V4 Delete Version
V5 Transport Version
V6 Delete Version Header
VE Create an Enhancement ID
VF Expired
W1 Debug
W2 External Start

Display a list of user's password status and lock status.

·       Execute tcode rsusr200  or  Tcode SUIM

·       User-->

      Users By Complex Selection Criteria -->

      By Logon Date and Password change -->        

·      

           Enter a list of user (or) Enter single user name.   

    You will be able to see details as below.

·         

Table USR02 - User Lock value

1. Execute SE16

2. Enter USR02

3. Below are the value and its description:

Value:

0	Not locked
16	Lock
32	Locked by CUA admin (User Admin)
64	Locked by system Administrator
128	Locked due to incorrect logon attempts or too many failed attempts
192	A combination of both. The user is locked by admin and user tries to logon with incorrect passwords and gets locked ( 192 = 64+128)

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.