SAP GUI Roll Out Best Practice

I was wondering what is the best practice for rolling out a new SAP GUI. My plan is to upgrade our IT Department, and Super Users with the upgraded GUI and see if any errors/problems occur. If I don't have any major issues I would roll out to the User Community after about two/three weeks.
Is this typical practice ? I have heard other Professionals say to just roll the GUI out, and don't worry about testing it ? and I have heard other companies etc.. do a set of testing scripts etc..
Any feedback appreciated. - Thanks.

Hi,
yes I have done it on our company for years.
once new released or new patch of SAPGUI is launched, I will ask my SAP Functional, ABAP and BASIS mates to try it for a month with various report and transaction variation for standard and Z-tcodes, for dialog and background processing, printing, and export and import data.
After my IT-SAP mates feels that SAPGUI is ready to be used, I will launched it to all user in another department and keep to listen any feedback from them regarding this SAPGUI.
hope it help you.
rgds,
Alfonsus Guritno

Similar Messages

SAP ERP roll out to Algeria

Hello Experts,
Does anyone know what country version exists for a SAP ERP roll out to Algeria. I looked aorund the SAP website, and it mentions there is only "installation" pack in Algeria. Whats the difference between a country version and installtion only ? Any information around SAP ERP roll out version to Algeria or localization pack for Algeria will be appreciated.
Many Thanks!
Regards,
Vidhi
Edited by: VidhiG on Sep 5, 2010 10:28 PM

Hi,
first, I would like to explain about the term country used in SAP B1:
SAP Business One is currently available in 39 country* versions, also known as localized versions, each of which is designed to allow you to run your business operations in a particular country. In addition to the generic SAP Business One business logic, features, and functions, country versions also include country-specific functionality that is automatically installed and configured. These country specific functions help companies comply with local legal requirements as well as local business practices.
The term "country" is used for convenience only and does not necessarily infer the existence of a nation state.
I quoted the above statement from this link:
https://websmp108.sap-ag.de/~sapidb/011000358700001296992008
You could see there that country used for algeria is france.
Countries / Regions without localized SAP Business One
Algeria
Version SAP Business One Country Version(s) being shipped and used
France
Rgds,
JimM

SAP BI Cockpits & Dashboards best practice

Here is an overview of the options you have for dashboards, cockpits and scorecards using Web Application Designer, Visual Composer, Java SDK, 3rd Party, SEM- CPM, Portal iViews.. As well as best practices for developing Cockpits by Deepu Sasidharan & Dr. Bjarne Berg called "SAP BI Cockpits & Dashboards best practice: Evaluate and choose the right BI tool to build management cockpits".
Like always, we provide PowerPoints, so that everyone can take the slides they like: http://csc-studentweb.lrc.edu/swp/Berg/articles/Reporting_Analytics_2006_Cockpits_v10.ppt

Dear Berg,
Could you send it to my e-mail, I need to do web quwry to publisb in portal 6.o with BI 7.0, and I dont know how to execute it. Will be help full if cound send me step by step guide. My e-mail is [email protected]
Thanks in advance,
Antony

SAP Global Roll out-MM/WM

hi all.,
1. Working on a SAP Global Roll out project, can anyway educate me on the Pitfalls to avoid specifically in MM and WM configuration.
2. Also what are the areas to concentrate during configuration for Global Roll-out.
I have listed out a few points which i think is relevant, if there are others to be considered, do let me know.
a. Currency conversion between the different countries.
b. Time zone during Period/ Month closing
Much appreciated for your response/s.
Mahesh

Hi, Yogesh
I am sorry, I am not specifically aware of Thailand. While search in SDN, one thread was partially addressing the Thailand related need. But it is not giving much information. You may have a look at the link which I went through
Re: Country specific add ons to ECC 5.0
Regards,
Jagadeesh

SAP CRM V1.2007 Best Practice

Hello,
we are preparing the installation of a new CRM 2007 system and we want to have a good demo system.
We are considering too options;
. SAP CRM IDES
. SAP CRM Best Practice
knwoing that we have an ERP 6.0 IDES system we want to connect to.
The Best Practice seems to have a lot of preconfigured scenarios that will not be available in the IDES system (known as the "SAP all in one").
How can we start the automatic installation of the scenarios (with solution builder) connecting to the ERP IDES system?
Reading the BP Quick guide, it is mentioned that in order to have the full BP installation we need to have a ERP system with another Best Practice package.
Will the pre customized IDES data in ERP be recognized in CRM?
In other words, is the IDES master data, transactional data and organizational structure the same as the Best Practice package one?
Thanks a lot in advance for your help
Benoit

Thanks a lot for your answer Padma Guda,
The difficult bit in this evaluation is that we don't know exactly the
difference between the IDES and the Best Practice. That is to say,
what is the advantage to have a CRM Best Practice connected to an ERP
IDES as opposed to a CRM IDES system connected to a ERP IDES system?
As I mentioned, we already have an ERP IDES installed as back end system.
I believe that if we decide to use the ERP IDES as the ERP back end, we will loose some of the advantage of having an ERP Best practice connected to an CRM best practice e.g. Sales area already mapped and known by the CRM system, ERP master data already available in CRM, transactional data already mapped, pricing data already mapped etc.
Is that righ? Or do we have to do an initial load of ERP in all cases?

Sap hr roll out

Hi Pal,
I have question can some one answer tis please, I am doing a rol out project for one of our client who wants to do the roll out for the new plant.
He has only single company code and four Personnel Areas know we will be creating one more Personnel area under the same company code.
When it comes to time management they are havingnegative time management so can i copy the same to the new plant . if so how to copy .
even for payroll also .... can i copy the all the custom settings which they are having in the existing plant.
Pleasem do let me know this is my first roll out project and i have to handle all alone.
Thnks in advance
sansai

Hi
You can configure most of the tabs while copying the PA/PSA to new one with all groupings. other method is go to table V_001p_all map the all grouping's same as existing to the new PA/PSA.
So that most of the config will be done, but you need to check all the tabs once againg and do the testing.
Good luck
Pavan
Edited by: Pavan Tatavarthy on May 23, 2008 12:23 PM

Rolling Averages - Best Practices

Hi All,
I have a business requirement where I need to arrive at the Overtime % for the employees for the forecast scenario which is the calculation of the immediately preceeding 12 months of Actual Data.
I have written a long BR for each month to do what it is suppose to. I am not sure if that is the best way to do the same.
Any suggestions. I can provide more details if interested.
THanks in advance
Cheers

I assume this is a Planning app with Years and Months in separate dimensions, so you'll have to cross years.
Any reason you wouldn't calculate this dynamically using a member formula on an account? That way, you wouldn't have to run a business rule.
Let me know your dense/sparse settings and post your business rule and we can help more.
- Jake

SAP ASE Best Practice latest update

Hello experts,
just wondering if somebody already reviewed thoroughly latest guide for best practices on SAP Sybase ASE?
I am talking about the document from note 1680803 - SYB: Migration to SAP Adaptive Server Enterprise - Best Practice (former note 1722359 - SYB: Running SAP applications on SAP ASE - Best Practice).
The guide for normal runtime operation was merged with the guide for migration, but there are some contradictory statements.
Apart from that the study case is again designed for server with huge memory and lot of CPU cores (so not so real case normally, I wonder who setup so often such huge servers...), I have found some inconsistencies.
E.g. in part "Reconfigure Engines and Parallel Processing", they talk about to limit ASE engines to 16, but the command configures 32.
alter thread pool syb_default_pool with thread count = 32, idle timeout = 2000
No change to the previous setup for migration. Is this just typo? I understand it should be 16, and then also number of network tasks for normal operation would be 4 (as mentioned in the beginning of guide that normally you set up 1 per 3-4 engnes). If this is not typo, then number of network tasks is wrong as it should be 8.
Also they introduced idle timeout, but only talking about ERP and possible lower value for Solman - does this mean that for BW you keep default value (which if I am not mistaken is 100)? As per ADM540 you should even decrease this timeout when SAP system is sharing server with database - I know that document is old, but is again contradictory, not saying that it is wrong, but not well explained.
If anybody checked new version of guide, please let me know, I think it is bit messed up and is bit difficult to distinguish what you should set up for migration case and what for normal operation case.
Thanks!
Regards,
Matus

Actually, quite a few customers run with that many engines/memory.   In fact, it is difficult these days to even buy a server with less than 128GB of memory and 16 cores/32 threads.    Pretty much the only time we see less is when the install is in a VM.   Interestingly, we had comments from the first version suggesting the numbers were not realistic given the typical size of systems being deployed were much larger....    In addition, in my experience with customers on SAP systems, they were not aware of how much memory was necessary to really support medium to large systems based on the configurations they were attempting.
I am sorry that you feel some of the examples are contradictory. You are correct in pointing out that the text refers to 16 engines and the example configures 32....   So yes, for that specific example, it should have been 16.
Secondly, not having seen ADM540, but I think there is a bit of a problem if they suggest that.   I my opinion (and I have spent a lifetime tuning ASE), the idle timeout for ERP and BW should likely both be 1000+ and 2000 is not unreasonable.   The comment in ADM540 is likely due to if ASE and a NW CI are sharing the same cores - e.g. you have a 4 core box and ASE is running on 2 cores (we will ignore threads for this discussion) and you have 30 NW worker processes - which obviously will need to bump ASE off the cpu in order to run.   This may be fine in a test/dev or even a solution manager system, but bumping ASE off the core is NOT a good thing for a production system. In fact, I would encourage using numactl or similar to fence off the the cores used for ASE from NW worker processes if at all possible.   We have seen cases of overloaded NW installations with multiple CI instances with hundreds of worker processes each starving cpu away from ASE......sooo....I would tend to actually be a bit more than firm on suggesting that 100 is a very bad starting point.   Given the number of client side joins that SAP uses to avoid [DBMS proprietary] temp tables, it is critical that ASE's (or any DBMS) response time be minimized as much as possible.....having ASE yield the core practically as soon as it gets done processing one task (and puts it to sleep pending an IO) just really causes things to run slow.   Think of a typical query that returns 10 rows - say wide enough that each row fills 1 packet.   If the packet transmit time (and client ACK) takes more than 100 microseconds on CPU (almost a given for network interactions...as clock ticks are in nanoseconds and networking is minimally milliseconds - 1000 microseconds), ASE would yield the CPU every time it sent a packet.    When the client wanted the next packet, the OS would have to wake up the ASE process (an interrupted sleep) which is a nasty heavy weight operation.   Hence it is best for ASE to hang out on the CPU until reasonably sure that nothing more is going to happen very soon....and on current cpus...and having it run for 1-2ms (1000-2000 microseconds) shouldn't be a hardship.     If you created a separate thread pool for batch worker processes, then I could see maybe using a lower idle timeout such as 200 or 250......100 is just plain too low in my mind...it is like saying ASE is expecting an odd query every few seconds vs. a steady workload. Basically at that level, there had better be a task in the ASE job queue or one on the way on the network already, or that engine is going to sleep.
While I state that with regards to ADM540 itself, I have not seen the class (perhaps)...one customer did show me the notebook of a class (ASE Sys Admin) they went to and it was really targeted at non-SAP installations more than SAP installations - from a reality/experience aspect.   Part of the issue with the class the customer showed me was it borrowed liberally from the old SY classes as a starting point, but at the point the class was developed there was not a lot of experience with running SAP installations on ASE to really point out the fine tweaking areas such as idle timeout.
However, the document was really aimed primarily at Business Suite vs. BW systems or a Solution Manager install (which are much smaller) - there are a lot of other considerations for BW the guide doesn't get into - although some of the sizing is a better start than the defaults provided by SAPINST
The former runtime guide essentially was just merged in to the Post-Migration Steps section.
May do a quick refresh in the near-future (due to some recent experiences), so if you have other specific examples of the text and SQL not aligning - please let me know.

Benchmark Your Best Practices through the ASUG/SAP Enablement Survey

One of the most frequent questions asked by companies implementing SAP is u201Chow do other companies get their employees ready to use the system?u201D They want to know how similar companies have addressed the most critical success factors for preparing and sustaining their end users for new technology deployment. SAP is consolidating knowledge of best practices used in the market through the ASUG and SAP Enablement Survey.
ASUG and SAP have teamed together to build a survey that will allow respondents to gain insight into how the market is addressing enablement, and how similar companies rate their achievements. All responses are consolidated to provide insight on enablement practices by industry, company size, region, budget allocation, and more. Individual responses remain confidential.
As a respondent you will receive a report outlining the most critical enablement practices implemented by comparable companies. The report provides specific insight about your enablement practice in relation to similar companies. Please take the time to complete this short survey (10-15 minutes) today. Your voice matters and we really appreciate you taking the time and completing the survey.
Click on the link to access the survey:
[ASUG/SAP Enablement Benchmarking and Best Practices Survey|http://www.benchmarking.sap.com/cgi-bin/qwebcorporate.dll?idx=CUX8C2&SHSP1Q2A=ASUG&LNG=0]
Edited by: Claudia Mandelli on Feb 22, 2012 11:53 PM

Hi ,
Please find my answers below:
1. The roles will be created in BW and should automatically appear in BO CMC Authentication SAP roles, if there is a connectivity setup between BO and BW irrespective of the SSO.The roles are transported by the BW security team.
2. Every environement will have a unique connection to the corresponding SAP BW environment.For example SAP BW DEV will be mapped to BO DEV, SAP BW PROD will be mapped to BO PROD.So these settings cannot be migrated through Promotion Management.
3.This authentication can be applied to all tools , the SSO does not depend on the tool ,it depends on the integration between two systems which in this case are BO and SAP BW
As mentioned earlier, after integration all tools can have SSO
You can refer to a lot of help documents on this site which will help you to setup the integration between SAP BW AND SAP BO.
Kind Regards,
Priyanka

Transport Best Practices - Cumulative Transports

Hi All,
    I am looking for a some sort of authoritative guide from SAP on ECC Transport Best Practices, especially around merging/combining/accumulating multiple transports into fewer ones. We are a very large project, but we haven't figured out the CVSs like ChaRm so we still deal with individual transports.
The reason I am asking this is that we some development leads on our project that insist that ALL transports that leave Development system must be imported into Production. They claim this the SAP best practice. An SAP consulting review of our system also left a vague note that "We are orphaning transports". This could mean that 1. either we are not importing all the stuff that leaves Dev system 2. or we are not keeping track of our code changes across all environments. Proponents of "All transports must get to PRD" are interpreting this as "1".
I have my team cumulate transport for subsequent changes into newer transport and only take the newest Transport to Production. The continuous rolling of old Transport into new one using SE01 "Include Objects" options ensures that all changes part of current development are in a single TR. Fewer transports mean fewer housekeeping across all systems, and less chances of something going out of sequence or missed out. This is for Workbench Transports only. I understand Config transports could get a little tricky with rolling in.
If you can't point me to a link, what is your take on "Send everything to Prod" vs. "Combine changes into fewer Transports"? I can't think of any software packaging methodology that suggests putting everything, including some junk/crap, into production build. I have looked at SAP enhancement packs, SPS, and Notes. I haven't found any evidence of SAP including older buggy code in what it releases to its customers.
Thank you all!

Jānis, Christian,
    I think we are all on the same page. Let me clarify my specific scenario a little bit more.
We are about 15 ABAP developers team, for production support. We don't do huge changes. Our code updates are mostly limited to a handful of objects (average 2 - 5). We often have multiple iterations to same objects. For large scale development objects, this approach may not work very well. Those should really utilize SolMan or other CVS tools.
Here is How I have my team putting together final transport.
step 1. Change is done to object X. Transport #1 created and released after standard checks.
step 2. More change is needed for object X. Transport #2 Started. Transport #1 is brought in using SE01 include objects at the main task. Changed objects are in lower tasks. This way, I can tell what was brought over, and what really changed this time. Releases of the Transport #2 inspects all objects and insures all objects from #1 are included in #2, and that there are no other changes between #1 and #2 to any of the objects. This is very easy check mostly from Version History.
Step 3. More changes needed to object X and Y. Transport #3 started. Transport #2 brought in at main task. Same check from Step 2 is done to ensure no other changes exist.
step 4....6. Step 6 ended at Transport #6. All changes verified in QA system.
Only the Transport #6 needs to be sent to Production since previous Transports 1 to 5 were rolled into #6.
Jānis, the deletions will be covered automatically just like standard SAP. No special manual steps needed.
Christian,
   The transport of copies works in similar way. Only thing different is that the Main/cumulative transport is released at very last, possibly after QA tests have been confirmed.
I had thought about doing Copies vs. cumulative. I preferred to go with having Transport in QA already at the time of approval. I would have hard time explaining to our client why a Transport was released out of Dev After all tests were done and signed off.
However, the Copies have advantage that intermediate versions or parallel changes of same objects are easily recognized upfront vs. us having to check each transport before release.
Jānis, the "copies of Transport" also creates extra versions in version history just like manually adding objects in a transport.
My quick analysis between copies and cumulative only came with one different that 'copies' have a different flag/attribute in Table E070. I am sure the flag means something to SAP, but for versioning history, it makes no differences.
Regardless of if I cumulate or not, based on your experiences, have you come across notion that everything that leaves Dev must get to PRD as SAP Best Practice? What would your reply be if someone insists that is the only way to move code to production?

SAP GUI 730 PL8 Installation Problems

Hi all!
We are facing a problem with the following software product:
Information NwSapSetupAdmin.exe:
SAP GUI for Windows 7.30 (Compilation 3)
Component ID: 1460620d-c8bc-44c2-86ec-e632e0986b01
Version: 27625
Latest Patch Level: 8
SAP Automatic Workstation Update
Component ID: 40d11884-3906-4e67-8a96-91035ca09814
Version: 900.42
Latest Patch Level: 45 Version 9.0.45.0
Information SAP Logon:
Release: 730 Final Release
Dateiversion: 7300.3.8.1084
Build: 1478436
Patch-Level: 8
Within the SAP GUI Installation (NwSapSetup.log) the following error occurs:
16:25:13 NwSapsAtlC 1   Executing script action...
16:25:13 NwSapsAtlC 1   Script-action: Checking reboot condition.
16:25:13 NwSapsAtlC 1   Script-action: NwEngine.Context.Reboot = 1
16:25:13 NwSapsAtlC 1E Microsoft VBScript runtime error: Error message: Unknown error 0x800A01B6. Error code 0x800a01b6.
                         Object doesn't support this property or method: 'NwEngine.Context.Args' (Line 4, Col. 5)
                         The setup script contains the error listed above. Please contact your system administrator and provide this information, for example by sending him a screenshot of this message box (Press Alt+PrtScrn to create the screenshot and copy it to the clipboard).
16:25:13 NwSapsAtlC 1E Failed to run script:
                              ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
                           1: NwEngine.Context.Log.Write "Script-action: Checking reboot condition."
                           2:             NwEngine.Context.Log.Write "Script-action: NwEngine.Context.Reboot = " & NwEngine.Context.Reboot
                           3:             If NwEngine.Context.Reboot = 1 Then
                           4:                 If NwEngine.Context.Args("SuppressReboot") <> "" Then
                           5:                     NwEngine.Context.Reboot = 0    'Setting Flag for no Reboot
                           6:                     NwEngine.Context.Log.WriteWarning "Script-action: Reboot suppressed by the user. NwEngine.Context.Reboot = " & NwEngine.Context.Reboot
                           7:                 ElseIf NwEngine.Context.Args("DelayReboot") <> "" Then
                           8:                     NwEngine.Context.Reboot = 1    'Setting Flag for delayed Reboot
                           9:                     NwEngine.Context.Log.WriteWarning "Script-action: Reboot delayed by the user. NwEngine.Context.Reboot = " & NwEngine.Context.Reboot
                          10:                 Else
                          11:                     NwEngine.Context.Reboot = 2    'Setting Flag for immediate Reboot
                          12:                     NwEngine.Context.Log.Write "Script-action: Enforce immediate reboot."
                          13:                 End If
                          14:             End If
                              ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
                         Error message: Unknown error 0x80020101. Error code 0x80020101.
16:25:13 NwSapsAtlC 1E Failed to parse script. Error message: Unknown error 0x80020101. Error code 0x80020101.
16:25:13 NwSapsAtlC 1E While processing Component '$MS System Files' with Id '{F270A214-3AD3-4235-9C74-F4D323B54976}' 1 error(s) have been registered.
16:25:13 NwSapsAtlC 1   CompAct.:Installed Component '$MS System Files' with Id '{F270A214-3AD3-4235-9C74-F4D323B54976}'
With this the NwSapSetup.log ends with:
16:26:23 NwSapSetup 1 Return-Code: 145
In the next logical step within our environment a uninstallation of the SAP GUI gets started:
   Commandline:
'"C:\Program Files (x86)\SAP\SapSetup\Setup\NWSapSetup.exe" /Silent /Uninstall /Package=PEACY'
This operation gets done with:
12:35:47 NwSapSetup 1 Return-Code: 0
After that the installation of the SAP GUI gets started again with:
   Commandline:        '"C:\peacy.sys\source\SAPGUI730PL8\source\setup\NwSapSetup.exe" /noDLG /norestart /Package=PEACY'
Now the Installation gets done with:
12:52:12 NwSapSetup 1 Return-Code: 0
Every first installation of SAP GUI 7.30 PL8 is affected. This is a cross-platform issue (Windows 7 and Windows 8.1). If there was our older package version (SAP GUI 7.30 PL4) installed, the installation of SAP GUI 7.30 PL8 gets done without problems.
Every new client with the SAP GUI 7.30 PL8 assigned or the re-installation of it, and every first installation of the package on a client without SAP GUI leads to the mentioned issue - package gets installed with the mentioned error, afterwards the uninstallation gets started by our environment and finally the installation gets done with the second try. This is not a practicable method for our support staff.
Are there any hints how to resolve this issue. (A upgrade to the newest patch level of SAP GUI is not a practicable solution)
Thanks in advance!
Best regards
Christian

Hello Christian,
For older releases of the SAP GUI client a good approach is to create package for uninstalling old SAP GUI. Depending on the state of the old SAP GUI's you're upgrading those may not be "clean" enough to warrant upgrading in place.
The older GUI's have component's no longer provided with the newer releases so most recommendations are to uninstall completely an do a fresh installation.
I credit Matt Fraser for this information and suggest reading his documentation. The last 4 articles are germane to you're situation. I hope this helps you.
http://scn.sap.com/thread/3620515
http://scn.sap.com/docs/DOC-55477
http://scn.sap.com/docs/DOC-55574
http://scn.sap.com/docs/DOC-55575
http://scn.sap.com/docs/DOC-55633
http://scn.sap.com/docs/DOC-55634
http://scn.sap.com/docs/DOC-55674
Cheers,
Dan Mead

SAP GUI and Win 7 error when attaching a document

I searched Google multiple times for an answer but didn't find one, so I'd like to bring it up in this forum.
I start by saying that mine is a large corporation with centralized application, Windows and security configuration, so I have very little manuvering as far as changing settings.
The problem we run into is as follows:
some users who use a particular (Quality Assurance) module of SAP need to regularly attach documents (typically PDF format) in SAP. The typical size of an attachment is between 3-7 MB.
Those documents are store on a network file share remote to the site. The network latency between the site and the file share location is approx. 6ms (not huge by any means). Users are running Win 7 Enterprise SP1.
Randomly, the attachment download fails in SAP and they have to exit and log back in to SAP to resume. The attachment may fail2-3 times, and then succeed or fail permanently.
Copying the file to a local drive (C:) and then attaching it in SAP always works.
The users report that this was not an issue when they were using WinXP SP3 a few months back.
Again, the problem is random in that it cannot be recreated at will but happens often enough to be more than just an inconvenience.
the Windows event log logs the following message when the attach process fails and SAP freezes:
The program saplogon.exe version 7300.1.2.1080 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: a7c
Start Time: 01cf38c9a86d55ac
Termination Time: 16
Application Path: C:\Program Files\SAP\FrontEnd\SAPgui\saplogon.exe
Report Id: 139b5ba9-a4bd-11e3-8b65-d8d3857a05c5
I'd appreciate any input that would help resolve this issue.
Steve

Besides updating the patch level, the other thing you can try to get more information is turn on or increase the level of tracing within the SAPGUI. You can do this on the workstation in SAP Logon by clicking the little button at the upper left of the window title bar, then in the drop-down choose Options. In the new window that opens go to the Traces folder and have a look through the three different kinds of traces you can turn on. Probably you should turn on SAP Logon Traces to the "Errors" level, and same for SAP GUI Traces (to Level 1: Errors), and under Session Traces pick the options that make sense to you (perhaps "Access Control", "Office Integration", and/or "Security"? You might need to experiment with different options to get the right combination that doesn't overload the trace file with noise; you may not need a Session Trace at all if the error trace on the other two options reveal what's wrong).
You can see under Session Traces what folder the trace files will go to, and open the folder from there. By default it will be C:\Users\<username>\AppData\Local\SAP\SAP GUI\Traces.
Best regards,
Matt

Seaching for Best Practice links that work

Hi,
past few years I have been able to access SAP Best Practices documents like SAP Best Practices SAP Best Practices for CP and Wholesale Industries
(this one still works and guides me to the building block and process overview documents!).
Recently any link I can find to SAP Industry or Baseline Best Practices ends up with a dead link. See for example trying to get from here SAP Best Practices Baseline packages – SAP Help Portal Page
to Localized for Netherlands V1.607 SAP Best Practices package further below on that page, results in screen shot attached. I have seen that in many more examples (different countries, or in Industry Best Practice Packages instead of Country Baseline packages....)
Does any know whether and how SAP redesigned their access to Best Practices documents (Configuration Guides, eCatts, Scenario Process Overviews etc.?
Thanks for your reply.
Thijs

Hi, Thijs,
There is currently a problem with Best Practices on the Help Portal. On the home page of the portal (http://help.sap.com/) there is a message that reads "Stay Tuned - There are temporary problems when accessing some content types, for example PDF documents or Best Practices. We are working on a solution."
Our Wholesale Distribution industry group does not manage the Help Portal pages, so, unfortunately, I don't know the status of the problem or when it might be resolved.
Lynn

Re engineering of existed process / Best Practice (customization)

Hi all of you,
We are implementing SAP ECC 6.0 for one of our clients. Client is asking us to compare their existed business process with Best Practice / standard process and based on the result, asking to prepare a GAP analysis between the existed and best practice for his business.
SAP itself is a best practice in the respective domains / business processes. By implementing SAP ERP, the client will have best practice for his business processes as I know. But thing is, how can I explain to the client that SAP has given the best practice and based on which, client will consider the SAP practice as Best Practice for the business??
Please give me a solution
Regards,
Ramki

f l,
I'm not sure deleting keys from the registry is ever a best practice, however Xcelsius has listings in:
HKEY_CURRENT_USER > Software > Business Objects > Xcelsius
HKEY_LOCAL_MACHINE > SOFTWARE > Business Objects > Suite 12.0 > Xcelsius
The current user folder holds temporary settings, such as how you've modified your interface.
The local machine folder holds more important information.
As always, it's recommended that you backup the registry and/or create a restore point before modifying or deleting any keys.
As for directories, the only directory Xcelsius uses is the one you install to. It also places some install logs in the temp directory, but they have no effect on the application.

Highly Required CRM 5.0 Best practices for CRM Service Module

Dear all,
I have been searching for CRM 5.0 version best practices in Internet quiete a long period, but could not find anywhere.
currently SAP is providing only best practices for SAP CRM 2007 version.
since most of configuration is differing because of Webclient Interface, I request you to refer a source from where I can get the CRM 5.0 Best Practices for Service module.
Your suggestions and help will be highly appreciated.
Best regards
Raghu ram

Hi Srini,
<removed by moderator>
Thank you & Best regards
Raghu ram
Edited by: Raghu Ram on Jul 16, 2009 6:09 AM
Edited by: Raghu Ram on Jul 16, 2009 6:11 AM
Moderator message please review the rules of engagement located here:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/rulesofEngagement
Edited by: Stephen Johannes on Jul 16, 2009 8:12 AM

SAP GUI Roll Out Best Practice

Similar Messages

Maybe you are looking for