tag:blogger.com,1999:blog-57038492011-12-15T03:06:07.159ZSAP Info BlogSAP Information I find on the way...Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.comBlogger211100tag:blogger.com,1999:blog-5703849.post-1128948866426830122005-10-10T12:52:00.000Z2005-10-10T12:54:26.433ZOCS_GET_INSTALLED_COMPS - run in SM37, select a predefined RFC destination, and look at the table of results.This'll tell you all the version numbers of the installed components in the SAP system.Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1127916495104491462005-09-28T14:06:00.000Z2005-09-28T14:08:15.110ZI tried setting up a job to do this, using a call to the OS like this:"tp import all pf="It's really not that nice, and caused more problems than it was worth.Then I found a standard ABAP that does it properly:TMS_BCI_START_SERVICEJust schedule that every 15 minutes or so.Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1116838688324458272005-05-23T08:35:00.000Z2005-05-23T09:00:52.510ZIt's not easy finding your SAP version these days, there are kernel versions, application versions, add-ins versions etc.SAP R3 4.7 Enterprise comes with two Extension Sets 110 and 200.To check which one you have, the only way I've discovered so far is from these notes.538887: SAP R/3 Enterprise 47x110: Software Architecture/Maintenance Tracks658351: SAP R/3 Enterprise 47x200: Software Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1110803948998899282005-03-14T11:59:00.000Z2005-03-14T12:39:09.000ZWith newer SAP and Oracle, svrmgrl has gone - RIP.To do a select from the underlying tables, you need to use sqlplus.sqlplus "/as sysdba"SQL>SQL>Select * from sapr3.t000;might work, but since R3 version 6.1 the schema owner is supposed to have changed from sapr3 to sapSo on my system I tried this:SQL> select * from sappst.t000;*ERROR at line 1:ORA-00942: table or view does not existSome Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1108634842701316972005-02-17T10:04:00.000Z2005-02-17T10:07:22.703ZIn SPRO you can search the IMG. Today this short dumped on me with:Error when attempting to IMPORT object "P_STRUCTURE_TEXTS".The answer was surprisingly simple - I needed to refresh the text index. This is simply a refresh button on the search dialog box.Only took a couple of minutes too.Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1106752628129191872005-01-26T15:15:00.000Z2005-01-26T15:18:34.346ZSCPL3
BC Sets are a way of saving IMG configuration , saving a whole set of data at a point in time, ready for transporting.
BC stands for Business Component, and this functionality has been available since 4.6C
Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1089639102342323402004-07-12T13:31:00.000Z2004-07-12T13:31:42.343ZRSORADLD
Expensive SQL ABAP, reports data in Moni.
I've not used it, just making a note hereRoberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com2tag:blogger.com,1999:blog-5703849.post-1088419864724837432004-06-28T10:50:00.000Z2004-06-28T10:51:04.726ZHow To Remove Report Variant Protection
If a user has been deleted, and there are report variants protected
against changes by other users, You can use report RSVARENT to reset
this protection flag, before you can maintain the variant.
But be careful, the Select-Options do not require any input, and there
is no Authority check, so You could accidently reset the protection
flags of all report Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1077726355550519472004-02-25T16:25:00.000Z2004-02-25T16:27:57.590ZSM20 - Security Audit Log
Never used this, but looks interesting. Needs activating with the parameter:
rsau/enable
Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1077726188958042552004-02-25T16:23:00.000Z2004-02-25T16:25:11.030ZSAP* Locked
update sapr3.usr02 set uflag ='0' where bname like 'SAP*' and mandt = 'nnn';
This is better than deleting the user and then having to set it up again with the same profiles etc.
Check also OSS note 68048.
It is possible to remove the possibility of SAP* from a system, check RZ10 for profile parameter:
login/no_automatic_user_sapstar
if this has been done then the above won't Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1075368434700946202004-01-29T09:27:00.000Z2004-01-29T09:28:49.340ZRSTPTEST
Having problems with transports, but no access to the operating system!
Run RSTPTEST to check all the connectionsRoberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1075290783984886142004-01-28T11:53:00.000Z2004-01-28T11:54:37.263ZUSR40
This table stores the forbidden passwords.
If you don't want a user to put PASS anywhere in their password, use *PASS*.Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1075222113837747522004-01-27T16:48:00.000Z2004-01-27T16:50:06.843ZRSADRCK2
If you are getting problems with your users addresses, possibly due to dodgy client copies, try report RSADRCK2.
You should run it in test mode first.
It actually has some documentation.
More in OSS Note 503366Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1071504699238137432003-12-15T16:11:00.000Z2003-12-15T16:12:29.716ZSE14
There is an awful lot of stuff in SE14, which should let you manipulate tables from within SAP rather than at database or sapdba level.
It's best to change the values of next and max extents here, rather than in sapdba. The reason is that if the table is busy when you try to apply the change, you can just hit re-execute to try again, and again, and again....; don't worry about all the Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1071163395168831022003-12-11T17:23:00.000Z2003-12-11T17:24:01.576ZOS01
Want to see if your server can ping another address. Run this!Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1070641455237020452003-12-05T16:24:00.000Z2003-12-05T16:24:55.763ZSMW0
Use this transaction to set up and upload a new logo for use on the logon screen.
SSM_CUST
Configure the entries in this table to select the logo you've created, and the sizing options.Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1070463636252067522003-12-03T15:00:00.000Z2003-12-03T15:01:15.000ZRZ11
Change profile parameters on the fly without bouncing the application server.
Watch out for
abap/heap_area_total
abap/heaplimit
ztta/roll_extension
though. OSS Note 610965 says this won't work, use ABAP RSMEMORY instead. But even this doesn't work for abap/heaplimit :-(Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1069863674490854872003-11-26T16:21:00.000Z2003-11-26T16:21:46.170ZSLICENSE
Transaction to view your system's license information. Looks like you can also install a temporary license and lookup your hardware key, much like with then unix commands.Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1069775265573712562003-11-25T15:47:00.000Z2003-11-26T16:23:02.186ZTMSADM User
OSS Note 139854 says that you can generate the TSMADM user:
Generate the user in the system overview of the TMS with Extras -> Reset
user TMSADM.
However, I'm having trouble finding this option in 4.6C !Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1069770546446507862003-11-25T14:29:00.000Z2003-11-25T14:29:36.950ZSE03
Transport Organiser ToolsRoberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0tag:blogger.com,1999:blog-5703849.post-1069686954105153632003-11-24T15:15:00.000Z2003-11-24T15:16:23.716ZAutomatic unlocking after incorrect logon
OSS Note 66533 tells us about the parameter
login/failed_user_auto_unlock = 0
If this is set to 0, then the administrator must manually unlock users who have managed to lock themselves out. This is now the normal setting for most systems
If it is set to 1, then users will automatically be unlocked at midnight. This is an older approach, I'm not sure Roberthttp://www.blogger.com/profile/11107800467793491713noreply@blogger.com0