Check the SAP(oracle) database version

C:Documents and SettingsAdministrator>set ORACLE_SID=C11

C:Documents and SettingsAdministrator>sqlplus /nolog

SQL*Plus: Release 9.2.0.4.0 - Production on ??? 11? 13 16:53:18 2008

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

SQL> connect / as sysdba
Connected.

SQL> select * from v$version;

BANNER
--------------------------------------------------------------------------------

Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
PL/SQL Release 9.2.0.4.0 - Production
CORE 9.2.0.3.0 Production
TNS for 32-bit Windows: Version 9.2.0.4.0 - Production
NLSRTL Version 9.2.0.4.0 - Production

SQL> 查看全文

ECC 6.0 install error on sap_add_dbccjob step

I am installing ECC 6.0 as ABAP with System Copy method on Windows Server 2003 Standard Edition with MS-SQL Server 2005 as Database Server. I am facing error at the phase "Create SAP stored Procedures" in the step 025 of 220 (sap_add_dbccjob).

Search sdn.sap.com, found a related thread,

Help with CRM 2007 Installation!

https://www.sdn.sap.com/irj/sdn/thread?threadID=800961&tstart=0&messageID=5158006

Try to disable Symantec Endpoint Protection, Worked!

LOAD_TYPE_VERSION_MISMATCH

When we imported a customize structure Z* which append for table RESB to QAS system, it worked; but imported to PRD system, so many users complained they could not run standard SAP programs, like CO13, CO14, CO15 etc.

Check with ST22, found a lot of ABAP runtime errors, LOAD_TYPE_VERSION_MISMATCH.

Search in service.sap.com, found 2 related notes,

Note 713492 - Additional time stamp check in structure administration

Note 1010590 - Structure components with width of more than 65535 bytes

It seams that this causes an memory overflow, and then leads to an error. Based on Note 1010590, the solution was import Support Package SAPKB70012 or higher, or implement the correction instructions. But the copy of PRD, QAS system was not happen the error. So we decided to restart the PRD to try to solve this.

Worked!

codepage 1100 is not released

上周六参加一个SAP培训的讨论会，看见培训用的服务器在英文（EN）登录时报错：codepage 1100 is not release，今天也有群里的朋友问到这个

在SAP找到这个note, Note 144680 - Character set (code page 1100) is not released

哪位朋友相信是手动搞定了这个问题，不知是不是用这个snote？

Why did SAP GUI for Windows 6.40 support end before SAP GUI for Windows 6.20 and 7.10 support does? The Microsoft

As of release 6.40 SAP usually ties the support duration for SAP GUI for Windows releases to the support duration for the development environment used. The reason for this is that we may require corrections from Microsoft for solving an issue in SAP GUI, but Microsoft does not provide us with corrections once support for a development environment is stopped.

• SAP GUI for Windows 6.40 was developed with Visual Studio 2003 which was de-supported by Microsoft on 14th of October 2008. Consequently SAP GUI for Windows 6.40 was also supported until this very day.

• SAP GUI for Windows 7.10 was developed with Visual Studio 2005 which will be de-supported by Microsoft on 31st of March 2011.
  Consequently SAP GUI for Windows 7.10 is supported until this very day.

• SAP GUI for Windows 6.20 is an exception to this rule. It was developed with Visual Studio 98 which is out of maintenance since September 2005. Since we had already announced support for this release to be "longterm" in order to allow customers to reduce their Frontend upgrades SAP GUI for Windows 6.20 is supported until 2010 even though we had to restrict the support (see note 929300).

If you want to know the details, pls check note 147519.

Pidgin 2.5.2 problem

1, If you are a chinese who use QQ, pls reinstall 2.5.1 to recover when you found that the pidgin always crashed when you start QQ;

2, After install 2.5.1, you should downgrade the gta to gtk-runtime-2.12.1-rev-b to repair the QQ display problem.

3, Pidgin support MSN, YAHOO, QQ, SKYPE, GTALK for me.

Pop a Message to specific SAP users

*
* Pop a Message to specific SAP users
*
* How to get a list of all the currently logged on users?
* How to popup an instant message on a user's monitor?
* How to get a specific user's details?
* Usage of 'POPUP_GET_VALUES' function module to get data from user
* without having to write GUI code
*
* Submitted by : SAP Basis, ABAP Programming and Other IMG Stuff
* http://www.sap-img.com
*
REPORT ZPOPUP NO STANDARD PAGE HEADING.
INCLUDE <ICON>.

DATA: BEGIN OF USR_TABL OCCURS 0.
INCLUDE STRUCTURE UINFO.
DATA: END OF USR_TABL.

DATA: L_LENGTH TYPE I,
T_ABAPLIST LIKE ABAPLIST OCCURS 0 WITH HEADER LINE,
BEGIN OF T_USER OCCURS 0,
COUNTER TYPE I,
SELECTION TYPE C,
MANDT LIKE SY-MANDT,
BNAME LIKE SY-UNAME,
NAME_FIRST LIKE V_ADRP_CP-NAME_FIRST,
NAME_LAST LIKE V_ADRP_CP-NAME_LAST,
DEPARTMENT LIKE V_ADRP_CP-DEPARTMENT,
TEL_NUMBER LIKE V_ADRP_CP-TEL_NUMBER,
END OF T_USER,
L_CLIENT LIKE SY-MANDT,
L_USERID LIKE UINFO-BNAME,
L_OPCODE TYPE X,
L_FUNCT_CODE(1) TYPE C,
L_TEST(200) TYPE C.

L_OPCODE = 2.
CALL 'ThUsrInfo' ID 'OPCODE' FIELD L_OPCODE
ID 'TAB' FIELD USR_TABL-*SYS*.

CLEAR T_USER. REFRESH T_USER.
LOOP AT USR_TABL.
T_USER-MANDT = USR_TABL-MANDT.
T_USER-BNAME = USR_TABL-BNAME.
APPEND T_USER.
ENDLOOP.

SORT T_USER.
DELETE ADJACENT DUPLICATES FROM T_USER.
LOOP AT T_USER.
T_USER-COUNTER = SY-TABIX.
SELECT V~NAME_FIRST

V~NAME_LAST
V~DEPARTMENT
V~TEL_NUMBER
INTO (T_USER-NAME_FIRST,
T_USER-NAME_LAST,
T_USER-DEPARTMENT,
T_USER-TEL_NUMBER)
FROM USR21 AS U
JOIN V_ADRP_CP AS V
ON U~PERSNUMBER = V~PERSNUMBER AND
U~ADDRNUMBER = V~ADDRNUMBER
WHERE U~BNAME = T_USER-BNAME.
ENDSELECT.
MODIFY T_USER.
ENDLOOP.
SORT T_USER BY NAME_LAST NAME_FIRST.
PERFORM DISPLAY_LIST.

TOP-OF-PAGE.
PERFORM DISPLAY_MENU.
* End of top-of-page

TOP-OF-PAGE DURING LINE-SELECTION.
PERFORM DISPLAY_MENU.
* End of top-of-page during line-selection


AT LINE-SELECTION.
IF SY-CUROW = 2.
IF SY-CUCOL < 19.
T_USER-SELECTION = 'X'.
MODIFY T_USER TRANSPORTING SELECTION WHERE SELECTION = ''.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 36.
CLEAR T_USER-SELECTION.
MODIFY T_USER TRANSPORTING SELECTION WHERE SELECTION = 'X'.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 50.
PERFORM TRANSFER_SELECTION.
PERFORM POPUP_MSG.
ELSEIF SY-CUCOL < 67.
PERFORM TRANSFER_SELECTION.
SORT T_USER BY NAME_LAST.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 81.
PERFORM TRANSFER_SELECTION.
SORT T_USER BY NAME_FIRST.
PERFORM DISPLAY_LIST.
ELSEIF SY-CUCOL < 93.
PERFORM TRANSFER_SELECTION.
SORT T_USER BY MANDT.
PERFORM DISPLAY_LIST.
ENDIF.
ENDIF.
* End of line-selection

*&---------------------------------------------------------------------*
*& Form DISPLAY_LIST
*&---------------------------------------------------------------------*
FORM DISPLAY_LIST.
SY-LSIND = 0.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
LOOP AT T_USER.
WRITE: / SY-VLINE, T_USER-SELECTION AS CHECKBOX,
SY-VLINE, T_USER-MANDT,
SY-VLINE, T_USER-BNAME,
SY-VLINE, T_USER-NAME_FIRST(15),
SY-VLINE, T_USER-NAME_LAST(15),
SY-VLINE, T_USER-DEPARTMENT(20),
SY-VLINE, T_USER-TEL_NUMBER(20), SY-VLINE.
HIDE: T_USER-COUNTER, T_USER-SELECTION.
ENDLOOP.
FORMAT COLOR OFF.
WRITE: /(108) SY-ULINE.
ENDFORM. " DISPLAY_LIST

*&---------------------------------------------------------------------*
*& Form DISPLAY_MENU
*&---------------------------------------------------------------------*
FORM DISPLAY_MENU.
FORMAT COLOR COL_HEADING HOTSPOT.
WRITE: (91) SY-ULINE,
/ SY-VLINE NO-GAP, (4) ICON_SELECT_ALL NO-GAP, 'Select All',
SY-VLINE NO-GAP, (4) ICON_DESELECT_ALL NO-GAP, 'Deselect All',
SY-VLINE NO-GAP, (4) ICON_SHORT_MESSAGE NO-GAP, 'Send Popup',
SY-VLINE NO-GAP, (4) ICON_SORT_UP NO-GAP, 'Last Name' NO-GAP,
SY-VLINE NO-GAP, (4) ICON_SORT_UP NO-GAP, 'First Name' NO-GAP,
SY-VLINE NO-GAP, (4) ICON_SORT_UP NO-GAP, 'Client' NO-GAP,
SY-VLINE,
/(91) SY-ULINE,
/(108) SY-ULINE.
FORMAT HOTSPOT OFF.

WRITE: / SY-VLINE, ' ',
SY-VLINE, 'Cli',
SY-VLINE, 'User ',
SY-VLINE, 'First Name ',
SY-VLINE, 'Last Name ',
SY-VLINE, 'Department ',
SY-VLINE, 'Telephone ',
SY-VLINE,
/(108) SY-ULINE.
FORMAT COLOR OFF.
ENDFORM. " DISPLAY_MENU

*&---------------------------------------------------------------------*
*& Form TRANSFER_SELECTION
*&---------------------------------------------------------------------*
FORM TRANSFER_SELECTION.
DO.
READ LINE SY-INDEX FIELD VALUE T_USER-SELECTION.
IF SY-SUBRC <> 0.
EXIT.
ENDIF.
MODIFY T_USER TRANSPORTING SELECTION
WHERE COUNTER = T_USER-COUNTER.
ENDDO.
CLEAR T_USER.
ENDFORM. " TRANSFER_SELECTION

*&---------------------------------------------------------------------*
*& Form POPUP_MSG
*&---------------------------------------------------------------------*
FORM POPUP_MSG.
DATA: L_MSG LIKE SM04DIC-POPUPMSG VALUE 'Experimental Message',
L_LEN TYPE I,
L_RET TYPE C.

LOOP AT T_USER WHERE SELECTION = 'X'.
PERFORM GET_MESSAGE CHANGING L_MSG L_RET.
EXIT.
ENDLOOP.
IF L_RET = 'A'. "User cancelled the message
EXIT.
ENDIF.
* Get the message text
L_LEN = STRLEN( L_MSG ).
LOOP AT T_USER WHERE SELECTION = 'X'.
CALL FUNCTION 'TH_POPUP'
EXPORTING
CLIENT = T_USER-MANDT
USER = T_USER-BNAME
MESSAGE = L_MSG
MESSAGE_LEN = L_LENGTH
* CUT_BLANKS = ' '
EXCEPTIONS
USER_NOT_FOUND = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
WRITE: 'User ', T_USER-BNAME, 'not found.'.
ENDIF.
ENDLOOP.
IF SY-SUBRC <> 0.
* Big error! No user has been selected.
MESSAGE ID 'AT' TYPE 'E' NUMBER '315' WITH
'No user selected!'.
EXIT.
ENDIF.
ENDFORM. " POPUP_MSG

*&---------------------------------------------------------------------*
*& Form GET_MESSAGE
*&---------------------------------------------------------------------*
FORM GET_MESSAGE CHANGING P_L_MSG LIKE SM04DIC-POPUPMSG
P_RETURNCODE TYPE C.
DATA: BEGIN OF FIELDS OCCURS 1.
INCLUDE STRUCTURE SVAL.
DATA: END OF FIELDS,
RETURNCODE TYPE C.

FIELDS-TABNAME = 'SM04DIC'.
FIELDS-FIELDNAME = 'POPUPMSG'.
FIELDS-FIELDTEXT = 'Message :'.
CONCATENATE ' - Msg from' SY-UNAME '.' INTO FIELDS-VALUE SEPARATED
BY ' '.
APPEND FIELDS.

CALL FUNCTION 'POPUP_GET_VALUES'
EXPORTING POPUP_TITLE = 'Supply the popup message'

IMPORTING RETURNCODE = P_RETURNCODE
TABLES FIELDS = FIELDS.

IF P_RETURNCODE = 'A'.
EXIT.
ELSE.
READ TABLE FIELDS INDEX 1.
P_L_MSG = FIELDS-VALUE.
ENDIF.
ENDFORM. " GET_MESSAGE

*-- End of Program

SAP Tutor Personal Player

here is a link to download

SAP Tutor Personal Player

https://websmp102.sap-ag.de/~sapidp/011000358700001572552002E 查看全文

Remove developer key from DEVACCESS table.

*&---------------------------------------------------------------------*
*& Report zdeldevkey.
*&
*&---------------------------------------------------------------------*
*& Remove developer key from DEVACCESS table.
*&
*&---------------------------------------------------------------------*

REPORT zdeldevkey.
TABLES: devaccess.

DATA: BEGIN OF i_dev OCCURS 0.
INCLUDE STRUCTURE devaccess.
DATA: END OF i_dev.

DATA: i_sel LIKE devaccess OCCURS 0 WITH HEADER LINE.

DATA: vg_check TYPE c,
vg_lsind LIKE sy-lsind,
vl_index TYPE i,
do_num TYPE i,
vg_num TYPE i.

SELECT-OPTIONS: s_uname FOR devaccess-uname.

If sy-uname <> 'KENLEE'.
exit.
Endif.


START-OF-SELECTION.
SELECT * INTO TABLE i_dev FROM devaccess WHERE uname IN s_uname.

LOOP AT i_dev.
WRITE: / vg_check AS CHECKBOX,
i_dev-uname,
i_dev-accesskey.
do_num = do_num + 1.
ENDLOOP.

SET PF-STATUS 'T001'.
*

AT USER-COMMAND.
CASE sy-ucomm.
WHEN 'DELE'.
PERFORM fm_delete_uname.
ENDCASE.
COMMIT WORK.
*&---------------------------------------------------------------------*
*& Form fm_delete_uname
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM fm_delete_uname .
DATA: vl_tabix LIKE sy-tabix,
vl_read_line LIKE sy-tabix,
vl_ret TYPE c,
vl_page TYPE i.
DATA: vl_check TYPE c.
vl_read_line = 2.
vl_page = 1.

LOOP AT i_dev.
vl_tabix = sy-tabix.
vl_read_line = vl_read_line + 1.

CLEAR vl_check.
READ LINE vl_read_line OF PAGE vl_page
FIELD VALUE vg_check INTO vl_check.

IF vl_check = 'X'.
READ TABLE i_dev INDEX vl_tabix.
MOVE-CORRESPONDING i_dev TO i_sel.
APPEND i_sel.
ENDIF.
ENDLOOP.

CALL FUNCTION 'POPUP_TO_CONFIRM'
EXPORTING
titlebar = '确认'
text_question = '是否确认删除'
IMPORTING
answer = vl_ret
EXCEPTIONS
text_not_found = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

IF vl_ret EQ '1'.
delete DEVACCESS from table i_dev.
commit work.
LOOP AT i_sel.
WRITE: /
i_sel-uname,
i_sel-accesskey.
ENDLOOP.
ELSEIF vl_ret EQ 'A'.
RETURN.
ELSE.
stop.
ENDIF.
ENDFORM. " fm_delete_uname

PS, so many thanks my ABAP workmates Owen Zeng.

 查看全文

Migrate EVA Command View to other machine.

Try to reinstall EVA command view on new machine instead of source machine.

It must to install EVA Command View on new machine(Server A) with local group method, with Domain group method will failled with login error "insufficient privilege", and then add the user to HP Storage Admins as member manually.

Login with the user, and the initial screen with pop the following message, select 'OK' to continue,

"Storage System Managed by Another Agent

Another management agent on server XXXXX at IP address 123.123.134.123 may be actively managing storage system sap_eva.

Only one agent is allowed to manage a storage system at a time.

To disable other management agents, simply click the OK button and management will be redirected to this agent.

Click the Cancel button to leave this page without changing the management agent for this system. "

Migrate log file to new disk

Normal 0 7.8 磅 0 2 false false false EN-US ZH-CN X-NONE MicrosoftInternetExplorer4

1, Shrink log file and backup database;

2, Create new disk for migrate log file;

3, Stop LXQ instance;

4, detach LXQ database;

5, Copy log file to new disk;

6, Attach LXQ database with new log file;

7, Startup LXQ instance and test;

8, Repeat 4-7, resume LXQ log file to original path;

Finished in 30 minutes.

SAP help files (.chm) not displayed correctly

Note 857216

http://support.microsoft.com/kb/896054

REGEDIT4
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftHTMLHelp] 
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftHTMLHelp1.xItssRestrictions]
"MaxAllowedZone"=dword:00000001

Method to start SAP Portal Server When MMC System Nodes Are Missing

自己也写过这个情况的记录，现在因为有朋友也出现这情况，一时找不到自己的文档，还是SDN上找一遍凑个数吧

Added by Swathi Rao Padma , last edited by Craig Cmehil on Sep 26, 2008 (view change) Labels: sap, ep EDIT Add Labels Enter labels to add to this page: Tip: Looking for a label? Just start typing.

Igswd.exe is not working

网上很多都说SAP note 824281有solution, 哪只是说有可能是profile的参数太长了，要改成短的。

其实运行IGS的实际命令是：

IGSP = -mode=all -sysname=＜SID＞ -sysno=＜XX＞

只要将这SID和NO填好即可。

sapcar.exe

C:TEMPsp46c>sapcar
usage:

create a new archive:
SAPCAR -c[vir][f archive] [-P] [-C directory]
[-A filename] [-T filename] [-X filename]
[-p value] [-V] file1 file2 ...

list the contents of an archive:
SAPCAR -t[vs][f archive] [file1 file2....]

extract files from an archive:
SAPCAR -x[v][f archive] [-R directory] [-A filename]
[-V] [file1 file2....]

verify the archive:
SAPCAR -d[v][f archive] [-V] [file1 file2....]

append files to an archive:
SAPCAR -a[v][f archive] file1 [file2....]

merge two archives:
SAPCAR -m[v]f "source target"

check availability of files to be processed:
SAPCAR -l [-A filename][-X filename] [file1 file2...]

other options:
-a : append files to an archive
-A FILE : get names to include from file FILE
-C DIR : change to directory DIR
-e : redirect output from stdout to file sapcar_output
-f FILE : use archive file FILE (default DEFAULT.SAR)
-g : ignore case of of archive names while extracting,
testing or listing archives
-h : do not change permissions of existing directories
during extraction
-i : ignore inaccessible files while creating an archive
-l : check availabilty of files to be processed
-lower : convert filenames to lowercase while extracting
-m : merge two archives
-n : print statistical information
-p octalvalue : set permissions of all files in archive to value
-P : use absolute path-names (use carefully)
-r : do not resolve symbolic links/shortcuts while creating
an archive
-R dir : use dir instead of current directory
-s : do free space check
-T FILE : rename files to be included in FILE
-v : verbosely list files processed
-V : compute or verify checksum (obsolete, always set,
for backward compatibility)
-X FILE : get names to exclude from FILE

examples:
create archive with all files and directories in the current directory
including point files:
SAPCAR -cvf MY.SAR .

create archive with all files and directories in the current directory
without point files:
SAPCAR -cvf MY.SAR *
Note that SAPCAR treats "*" and "?" as wildcard characters. The former
matches any character string, while the latter matches any single
character.

create archive with a complete directory and directory rights:
SAPCAR -cvf MY.SAR dir

create archive with all files of a directory without the directory
itself:
SAPCAR -cvf MY.SAR dir/*
if during extraction with SAPCAR -xvf MY.SAR the directory dir does not
exist it will be created with rights 755

create archive with only the files of a directory
SAPCAR -cvf MY.SAR -C dir .
or better
(cd dir; SAPCAR -cvf ../MY.SAR .)

merge two archives:
SAPCAR -mvf "a source-archive.sar target archive from 27.5.1999.sar"

append files to an archive:
SAPCAR -avf archive.sar file1 file2 file3

extracting/verifying files:
If you try to extract files from an archive that is not a valid SAPCAR
archive according to the version 2 specification SAPCAR assumes an archive
of the old format and automatically invokes the appropriate extraction
routine. If it still cannot handle the archive it will stop execution.
Notice that extracting out of old archives only works with the command
options known to the old CAR application.

using absolute pathnames:
If you create an archive with absolute pathnames the files will be
extracted with exactly these pathnames! SAPCAR does not cut the first
slash like the UNIX tool tar.

specifying a list of archives for extracting/verifying/listing:
You may call SAPCAR with the following command line:
SAPCAR -xvf "ARCHIVE1.SAR ARCHIVE2.SAR"
thereby specifying a list of archives you want to extract. Note
that you have to delimit archive names with "," if at least one
of the archive names you call SAPCAR with contains at least one
whitespace character; e.g.
SAPCAR -xvf "ARCHIVE WITH BLANK.SAR, ARCHIVE.SAR, ARCHIVE2.SAR"

using A, T and X option:
All entries in the specified files are treated relative to the current
working directory unless the entry is an absolute pathname (in this case
the relevant file will be archived with an absolute pathname).
If you want to specify a directory path in these files use the slash ("/")
as path delimiter.

Use the pipe sign ("|") to separate old and new names in a T file when
these names contain whitespaces. If neither the old file name nor the new
one contains any whitespaces you may use whitespaces as delimiter between
old and new name (that means a valid CAR rename file is also a valid SAPCAR
rename file and hence may be given with the -T option).
Note that pattern matching is not supported for entries in -A, -T and -X
files (i.e. "*.cpp" will not result in processing all cpp-files
in the current directory).

Lines starting with "#" as the first non whitespace character will be
ignored by SAPCAR (this also holds true of lines containing only
whitespaces).

If you insert a directory name in the specified file the complete
directory with the directory rights will be included in the archive.

If you specify dir/filename only this file will be included in
the archive. During extraction the directory dir will be created if
it does not exist.

using -C option:
All relative filenames in the command line are treated as relative
to the specified directory.

SAPCAR 2.0, build 410504

C:TEMPsp46c>

If you have a lot of .car files in the folder,which you want to upgrade the kernel, you can run the following command:

C:TEMPsp46c>sapcar.exe -xvf "*.car"

SPAM: QUEUE_NOT_EMPTY ... HELP URGENT

System: 46C/NT4/Ora817

I am trying to import the SPAM update KD40. The import aborts at CHECK_REQUIREMENTS with cause of error QUEUE_NOT_EMPTY. I seard OSS but nothing.

Solution:

delete or remove content of the buffer file in usrsaptransbuffer folder.

How to modify multiple items in the SAP menu

How do you add/remove/modify several items in the SAP menu for particular/all users?

Login to the development client; make sure that changes to repository or cross-client customizing are permitted. Use t-code SE43N and you will see the Area Menu Maintenance screen. The default area menu in SAP is S000, so if you want to change the items in SAP Menu, it is better that you copy the S000 menu, for example copy it to Y000 (Ctrl-F5).(Note by Ken, if u use the copy method, u should be replace the menu setting by t-code: SSM2) SAP screen will ask you which language the copy will be created, choose English; for the development class fill it with one of the default sap development class, exp. ZDEV; and click save. It will prompt you to make a transportable Workbench request.

Copyright by Yogi Gunawan

http://searchsap.techtarget.com/tip/1,289483,sid21_gci928077,00.html

Upgrade Procedure / Support Packages

Upgrade Procedure / Support Packages

During an upgrade or the import of an Support Package, existing objects of the SAP standard are overwritten with the objects redelivered. To help the customer retain the objects modified in a previous release, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of transactions SPAU and SPDD. These transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant supports this process of adopting customer modifications.

In the past, all objects modified by a customer and delivered again by SAP, an IBU or an SAP partner, had to be manually re-modified during an upgrade. Now, modifications are either automatically adopted or the system provides you with an assistant for adjusting your modifications to the newly upgraded configuration.

In general, objects altered using the Modification Assistant can now be automatically accepted into the upgraded system if the modifications undertaken in the original version do not directly overlap those made in the customer version. If collisions occur between the two versions at upgrade (naming collisions, or if SAP has deleted an object modified by a customer), the system offers support during the upgrade, which means that a semi-automatic adjustment is made. In some cases, however, you may still have to manually adjust objects using ABAP Workbench tools.

Objects modified according to the old system used prior to the advent of the Modification Assistant must be manually maintained after an upgrade has been run.

Use transactions SPDD and SPAU during an upgrade to select these objects and modify them manually.

• Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade.

For more information, refer to:

Adjusting ABAP Dictionary Objects

Prerequisites

Procedure

Preparing to Run Transaction SPDD

Transaction SPDD

• Transaction SPAU allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.

Additional information about the modification adjustment procedure using transaction SPAU can be found in Adjusting Repository Objects.

Additional information about the upgrade procedure can be found in:

Upgrading from Release 4.5A or Less

Modifications Made by Several Different People

Adjusting Other SAP Systems

Upgrading the Development System

Upgrading the Production System

Handling Change Requests During Modification Adjustment

Choosing a Change Request for Modifications

Local and Transportable Change Requests

Releasing Tasks at the End of Modification Adjustment

Choosing a Change Request to Transfer Modification Adjustments to Other SAP Systems

Notes (Troubleshooting)

一直对打SP后运行SPDD和SPAU知其然，昨天面试被问到这个问题，汗！完败！这部份HELP出自Changing the SAP Standard(BC),在SPDD或SPAU的界面按F1即可.

Set color to system

1. Alt+F12 -> New Visual Design
Select the General tab. In the Active Theme (top left) window, make sure select System ENJOY. Click on Apply.

From sdn forum, maybe you can find a post said select system dependent, but i test should be select enjoy.

2. Click on the color setting tab or Alt+F12 -> Set Color to System
That will let you choose the color.

ITS WEBGUI in ECC6.0

Copy from: https://www.sdn.sap.com/irj/sdn/thread?threadID=303806

Check if you have activated:
1) With transaction SICF and locate the services by path
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui

2)With Transaction SE80 locate from the menu, Utilities --> Settings-->Internet Transaction Server (Tab)-->Publish (Tab) and set “On Selected
Site” = INTERNAL.
This restricts the publication in the next step to the integrated (internal) ITS.

3)In SE80 only, Locate the Internet Services: SYSTEM and WEBGUI.
Publish these services with the Context Menu -> Publish -> Complete Service

4)Now Browse to http://<server>:<icmport>/sap/bc/gui/sap/its/webgui/! and login to the webgui.

How to disable the User menu?

use sm30 tcode and change the table ssm_cust and change the parameter:

ALL_USER_MENUS_OFF

NO (default), YES or 'X' - Do not Display User Menu on Easy Access Screen (Note 380029)

CUSTOMER_MENU_OFF NO (default), YES or 'X' - Do Not Display Customer Menu on Easy Access Screen (Note 380029)

SAP_MENU_OFF NO (default), YES or 'X' - Do not Display the SAP Menu on the Easy Access Screen (Note 380029)

The other method is use sm30 tcode and change the table users_ssm to determine whether or notusers are allowed to switch between the SAP menu and their user menus.

Apply:

If a user ask you based on the role menus, you can not find any key.

If a user has several roles assigned, then some functions can be repeated in different parts of the role-based user menu.

Types of SAP Support Packages

Get from sap website.

Types of Support Packages

SAP delivers various types of program corrections with Support Packages as part of the software maintenance. Support Packages automatically correct a whole range of errors by downloading corrections into the SAP System. Two categories of Support Packages are available: ABAP Support Packages and Java Support Packages.

ABAP Support Packages

ABAP Support Packages contain corrections and updates for the ABAP components of the SAP system that were performed up to a certain point in time. Each Support Package is based on the previous one. If you want to import Support Package 10, for example, you must also import all previous Support Packages (1-9). To import ABAP Support Packages, you use the Support Package Manager.

All SAP R/3 Releases up to 4.5 are supported by corrections in the form of SAP R/3 Support Packages (formerly Hot Packages) or SAP R/3 HR Support Packages (formerly Legal Change Patches HR) until the end of their maintenance period.

SAP HR Support Packages contain corrections or adjustments due to legal changes for HR functions in SAP R/3. Up to SAP R/3 3.1I (and SAP R/3 4.0B up to LCP HR 53), SAP R/3 HR Support Packages contain corrections for SAP HR as well as the same set of corrections as SAP R/3 Support Packages. As of SAP R/3 4.5B (and SAP R/3 4.0B as of LCP HR 54), the content of the SAP R/3 Support Packages is no longer included in SAP HR Support Packages.

Component Support Packages

ABAP Support Packages are available for all components of mySAP.com, such as SAP Basis, SAP BW, or SAP Advanced Planner and Optimizer (SAP Basis, SAP BW, SAP APO Support Packages).

Add-On Support Packages

Corrections for add-ons, such as industry solutions, strategic development projects or SAP R/3 Plug-Ins, are provided in Add-On Support Packages. For more information on Add-On Support Packages, refer to SAP Note 160168 .

Conflict Resolution Transports (CRT)

CRTs adapt Component Support Packages to add-ons, such as industry solutions (IS components). If an add-on modifies objects in the SAP R/3 Core components, conflicts with SAP R/3 Core Support Packages may arise. A CRT resolves these conflicts. For more information on CRTs, refer to SAP Note 53902.

SPAM/SAINT Updates

SPAM/SAINT Updates extend the functions of the Support Package Manager (Transaction SPAM) and the SAP Add-On Installation Tool (Transaction SAINT).

Java Support Packages

Java Support Packages contain corrections and updates to Java components. They are delivered in the form of Software Component Archives (SCA). Unlike ABAP Support Packages, Java Support Packages always contain the complete version of the Development Components for the application. You therefore need to apply the latest Support Package only. If there are dependencies with other Java Support Packages, these are specified in an SAP Note.

As of SAP NetWeaver 2004s, you can apply Java Support Packages using the Java Support Package Manager (JSPM). For more information on JSPM, refer to the quick link /JSPM.

Java Support Packages are available as of SAP Web Application Server 6.20. For SAP Web Application Server 6.20 and 6.40, you apply Java Support Packages using the Software Deployment Manager (SDM). The SDM is contained in the SAP Web AS installation as of 6.20. For more information on SDM, refer to SAP Note 544244.

Support Package Stacks

A Support Package Stack is a set of Support Packages and patches for a specific product version that must be used in the specific combination.

For more information on Support Package Stacks, refer to the quick link /sp-stacks.

All corrective software packages, for SAP NetWeaver 2004s and SAP Business Suite 2005 and beyond that are delivered after April 2nd, 2007 will ONLY be available via SAP Solution Manager's Maintenance Optimizer.

login/password_expiration_time

4月份因为内部Audit的原因，加强了Security,新增（更改）了部份login parameter
login/password_expiration_time 60
login/no_automatic_user_sapstar 0
login/failed_user_auto_unlock 1

特别要指出没有login/password_expiration_time在profile时SAP取的defaul value是0，当添加后从0改成60然后重启生效，哪么所有Dialog用户被要求改密码；这个参数第一次的从0到60的更改的副作用有点象reset "almost" users'password;而这里为什么说almost user,是因为第一次是0到60，估计绝对大部分用户的password都不符合SAP password policy,所以这里他们都要更改密码，而更改过后，如果你再次改login/password_expiration_time，用户就不要再次更改了，直到password_expiration_time到期。所以有Admin异想天开用它来更新password policy（象密码长度、字符变动）,的确是好注意！我试过从profile再次删掉login/password_expiration_time,让SAP取默认值0，重启生效，同一用户不必更改密码；下一测试添加login/password_expiration_time＝60重启生效，同一用户同样不必更改密码；下一测试更改login/password_expiration_time＝120，同一用户同样不必更改密码；具体测试过程如下

Profile Active value Change password
N/A 0
login/password_expiration_time 60 YES
login/password_expiration_time 120 NO
delete the parameter from profile 0 NO
login/password_expiration_time 20 NO
login/password_expiration_time 60 NO
login/password_expiration_time 120 NO



但如果要避免更改密码，似乎没什么好办法，但也不没有方法，只是不是针对所有用户：
1，前面有提到更改密码只涉及Dialog用户，所以可以将有需要的用户（如大BOSS）变成Service用户；
2，in the table USR02, just set a date far in the future for the field BCDA1 (password last change). For example, if you want to set it so user SMITH does not have to change his password until 2010, you can use the following SQL script : update USR02 set BCDA1 = '20101231' where BNAME='SMITH' Just replace the values for BCDA1 and BNAME with your own values ! This script is for MS SQL Server + R/3 46B and 46C, but the syntax should not be very different for other database systems and R/3 versions.

但从国内的企业应用来看，60天似乎太短了，下一阶段要设成120天；在ECC6 IDES测试过，从60到120，用户不需要更改密码。

相关的表：USR02

另外要说明的是login/failed_user_auto_unlock，明显的是一鸡肋，用户一但发现因密码错误不能登录，他就会不停的试不确定的密码直至被锁，而被锁后，根本不会等第二天自动解锁，他们会直接找Admin.

金山词霸企业版VS谷歌版

不在企业做的朋友多不知道金山词霸居然还有企业版，公司现在一直在用，本着短小精干的精神，想试用一下才20MB大小的谷歌版，结果问题来了！

在PDF文档里居然无法取词，而企业版怎么试也没问题。是跟企业版有冲实呢？还是卖给谷歌一个半残品呢？这是一个謎啊！如果是后者，哪金山太雷人了

slove ‘Lock table overflow' process

出错情况：

用户报称修改QT时出错：‘Lock table overflow';

...

检查日志SM21,

Internal lock administration error
> EqSetCluster(); rtc=16 enxxmenq1905
Lock table overflow
Internal lock administration error
> EqSetCluster(); rtc=16 enxxmenq1905
Lock table overflow
Internal lock administration error
> EqSetCluster(); rtc=16 enxxmenq1905
Lock table overflow
Internal lock administration error

详细日志，

An overflow of the lock table occurred when you were setting the loc
The lock table consists of several individual tables each of which
can overflow individually. The subsequent line indicates which of th
tables has overflowed.
The lock table is contained in the memory of the lock server
(-> enqueue server). Only the total size can be set. This is set
with the profile parameter "enque/table_size" in the instance
profile of the central locking server. Its value is entered in KB.
The setting only becomes effective when the system is restarted.
The default size of the lock table is 4096 KB.
Please note that when increasing the size of the lock table, a disk
requirement of approx. 1.5 x the size of the lock table is necessary
in each case in the global directory for the reporting file and in
the log directory for the backup file.
Before you increase the lock table after an overflow, you should
always check whether the overflow resulted from a program error
or an operating error.

检查profile parameter "enque/table_size"　with RZ10,

Short description: Size of lock table

by this parameter:

Parameter description :

This parameter defines the size of the lock table that is held in
main memory by the enqueue server. The lock table contains all of
the information about which locks are currently held, and by whom.

The size of the lock table limits the maximum number of lock
entries, the maximum number of elementary lock names, and the
maximum number of lock owners.
In the case of an overflow of the lock table, you should check
whether the update server is working correctly, since the lock table
can grow in size very quickly if updates stop. If the cause is not
update problems, you can use this parameter to increase the size of
the lock table.
The Computing Center Management System (CCMS) constantly monitors
the status of the lock table, and issues warnings if the free space
runs short.

The Computing Center Management System (CCMS) constantly monitors
the status of the lock table, and issues warnings if the free space
runs short.
You can view the fill level of the lock tables using the statistics
functions of lock management (transaction SM12 -> Extras ->
Statistics).

实施时考虑过公司的运行情况，将实际大小设成10MB，

enque/table_size = 10000

check LOCK status with SM12,

发现total locks居然达到8K有余，Nr_of_Locks: 8701,有异于平时系统正常运行状态，而绝大部分是一个用户锁定的；

查看用户进程SM50,确认用户在运行CORUAFFW，询问用户运行Tcode：COGI,确认用户在做物料替换时中断了会话，从而导致系统锁定的大批物料而没有释放。

解决方案：end session in SM50.

How to search sofeware which not belong to u?

Sometimes, we want to download the other software which not My Company's Application Components

like as other database of IDES, old version support package.

SAP Software Distribution Center

Search in SAP Software Distribution Center

Advanced Search

Change Search Method to All terms, default Context is restriction, change to no restriction, Max Search Result to 1000, select all the search object object, You will find you want to search. Good luck!

earch Term
Search Method	All terms At least one term Exact Term Phrase	Max Search Result	10 20 50 100 500 1000	Results Per Page	10 30 50
Context	no restriction Installation/Upgrade Maintenance	no restriction Current Software Archive
Search Objects	CD/DVD	Products		Components
	Non-ABAP Support Packages	Product Versions		Component Versions
	ABAP Support Packages

SAP最新的“挤奶”行动

Tcode: USMM

背景资料：

1、业内人士称SAP北亚区高管曾辱骂中国客户

...

太多了，选一则贴上，这里要注意的是：

为了达成这一战略目标，纪秉盟将10亿元任务分解到四个季度，即第一季度的“绝对值指标”是12％、第二季度23％、第三季度是20％，第四季度是45％。

现在是第三季，也有会计说法是第二季，从朋友，顾问，自身得到的体验是，SAP开始大范围的“挤奶”了，而且重点之一是从老客户哪里挤奶，还不能是纸质包装奶，必须是新鲜奶，有得忙了！

SQL error 2812: Could not find stored procedure.doc

起因：是在一台测试服务器上，安装了多个测试Instance，一次在安装Solution Manager时，将其覆盖在ERP上；

现象：一是登录时显示SAP菜单出错，报错START_CALL_SICK，Database inconsistency: Start Transaction SICK.但运行SICK还是出错，注意到"Can't execute sap_check_if_sick".但运行一些模块Tcode似乎没问题；

二是在激活DDIC object时出错，报错SQL error 2812 occured: Could not find stored procedure 'sap_get_object_type'.

设想：可能是错误的安装删除了SQL procedure

在现象二的帮助里，有The stored procedure must be created in the database. To do this, follow the instructions in SAP Note 460268.

Note Language: English Version: 1 Validity: Valid from 14.12.2001
Summary
Symptom
The following error message is displayed in the status bar or written to a
log file when executing a DDIC function:
SQL error 2812: Could not find stored procedure ...
More Terms
MSSPROCS
Cause and Prerequisites
As of Release 6.20, the access to the database for the return of system
catalog data is executed with stored procedures. These are called in
function modules of the SFMSS_S