Best practice SAP landscape

Hello all,
I would like to know if there is some kind of best practice regarding SAP landscape in a big company.
For example is it recommended to have in the landscape a SAP Quality Assurance System open for customizing (transaction SCC4) so that quick customizing tests are performed at any moment, instead of customizing in Development system and then transports in QaS. (this can be very frustrating because for solving and testing an issue it's possible that numerous customizing tasks and reset of customzing is neccessary) ?
How SAP compliant would this solution be?
Thank you very much for your help!
Daniel Nicula

Hmmm, I do not know exactly if the question can be posed here in GRC related threads.
But it seemed to me that it is somehow connected.
Anyway, I agree with you that final customizing should be done in DEV and then transported in QAS.
What i am not sure is if it is against SAP recommendations to have a QAS opened for customizing and try all the solutions for an issue. And in the end when you are sure of what you want to do and to obtain, then you do the customizing also in DEV and follow the normal transport route.
Which can be the risks in case you have a QAS opened for customizing?
Thank you.

Similar Messages

Question about Best Practices - Redwood Landscape/Object Naming Conventions

Having reviewed documentation and posts, I find that there is not that much information available in regards to best practices for the Redwood Scheduler in a SAP environment. We are running the free version.
1) The job scheduling for SAP reference book (SAP Press) recommends multiple Redwood installations and using export/import to move jobs and other redwood objects from say DEV->QAS->PROD. Presentations from the help.sap.com Web Site show the Redwood Scheduler linked to Solution Manager and handling job submissions for DEV-QAS-PROD. Point and Shoot (just be careful where you aim!) functionality is described as an advantage for the product. There is a SAP note (#895253) on making Redwood highly available. I am open to comments inputs and suggestions on this issue based on SAP client experiences.
2) Related to 1), I have not seen much documentation on Redwood object naming conventions. I am interested in hearing how SAP clients have dealt with Redwood object naming (i.e. applications, job streams, scripts, events, locks). To date, I have seen in a presentation where customer objects are named starting with Z_. I like to include the object type in the name (e.g. EVT - Event, CHN - Job Chain, SCR - Script, LCK - Lock) keeping in mind the character length limitation of 30 characters. I also have an associated issue with Event naming given that we have 4 environments (DEV, QA, Staging, PROD). Assuming that we are not about to have one installation per environment, then we need to include the environment in the event name. The downside here is that we lose transportability for the job stream. We need to modify the job chain to wait for a different event name when running in a different environment. Comments?

Hi Paul,
As suggested in book u2018job scheduling for SAP from SAPu2019 press it is better to have multiple instances of Cronacle version (at least 2 u2013 one for development & quality and other separate one for production. This will have no confusion).
Regarding transporting / replicating of the object definitions - it is really easy to import and export the objects like Events, Job Chain, Script, Locks etc. Also it is very easy and less time consuming to create a fresh in each system. Only complicated job chains creation can be time consuming.
In normal cases the testing for background jobs mostly happens only in SAP quality instance and then the final scheduling in production. So it is very much possible to just export the verified script / job chain form Cronacle quality instance and import the same in Cronacle production instance (use of Cronacle shell is really recommended for fast processing)
Regarding OSS note 895253 u2013 yes it is highly recommended to keep your central repository, processing server and licencing information on highly available clustered environment. This is very much required as Redwood Cronacle acts as central job scheduler in your SAP landscape (with OEM version).
As you have confirmed, you are using OEM and hence you have only one process server.
Regarding the conventions for names, it is recommended to create a centrally accessible naming convention document and then follow it. For example in my company we are using the naming convention for the jobs as Z_AAU_MM_ZCHGSTA2_AU01_LSV where A is for APAC region, AU is for Australia (country), MM is for Materials management and then ZCHGSTA2_AU01_LSV is the free text as provided by batch job requester.
For other Redwood Cronacle specific objects also you can derive naming conventions based on SAP instances like if you want all the related scripts / job chains to be stored in one application, its name can be APPL_<logical name of the instance>.
So in a nutshell, it is highly recommend
Also the integration of SAP solution manager with redwood is to receive monitoring and alerting data and to pass the Redwood Cronacle information to SAP SOL MAN to create single point of control. You can find information on the purpose of XAL and XMW interfaces in Cronacle help (F1).
Hope this answers your queries. Please write if you need some more information / help in this regard.
Best regards,
Vithal

Best Practice SAP HealthCare Portal

Hi SAP Team,
I have a following questions about the SAP HealthCare integration with SAP Portal, What is the best practice for implementation in these case? Its necessary to develop the application using webdynpro or Now I available the SAP Portal Business Package for these solution?
Best Regards
Roberto

I am also search on net & found some links & files about it, it found this PPT file on this topic, hope this will helps you.
http://net.educause.edu/ir/library/powerpoint/EDU03146.pps
[healthcare technology|http://www.nx3corp.com/]

Best Practiced SAP Netweaver Portal

Hi All,
We are trying to determine what should be the breaking point between what the portal dev team handles and what becomes SAP Securities responsibility. We are thinking that security should take it over when assigning IViews to Roles and then Roles to Groups and lastly groups to users. This is a very high view and welcome as much detailed information as you can provide.
Thanks,
Mary Sims

Hi Mary,
I fully agree with John. Portal roles are used to build up navigation. Therefor they define, what a user would see (if he/she would have read permission).
The mapping between user groups and portal roles, the assignment of users to roles and the setting of read permissions on certain iViews (pages) or folders in KM is a different thing. This is a security issue and should be done by security department.
We face this responsibility discussion in all our portal projects. You just have to rethink the word 'role', which normally isn't used for structuring content. This helps clearing up things. But at the end of the day, its an organizational discussion which depends on your internal organization.
At least, I made the experience, that it's best if you assign portal roles to portal groups but use the groups for setting the access control list - not the roles.
Maybe another cent,
Carsten

Best Practice SAP connection

Hello All
I am just starting creating reports with CR2008 connected to SAP ECC 6.0. I am suffering some performance issues when trying to create a report on tables VBAK, VBAP and LIPS. Report performance is extremely slow. I have a few questions on this:
1. Can anyone point me to some documentation that would help me set up SAP and CR2008 for improved performance when reporting directly on tables.
2. Performance wise Is it better to report on an Classic Infoset rather than directly on a table in CR2008
Any other tips would be greatly appreciated.
Thanks
Phillip

RFC Statement
Function module name
Source IP Address         192.168.3.220
Source Server             cham-vm1_CV1_00
Destination IP Address
Destination Server
Client/Server             Client
Conversation ID
RFC Trace Rec. Status     2
Sent Bytes                0
Received Bytes            0
Total Sent Bytes
Total Received Bytes
ABAP program name         %_T002S0
RFC Time                           0
Function module name      /CRYSTAL/OSQL_EXECUTE_INTERNAL
Source IP Address
Source Server             cham-vm1_CV1_00
Destination IP Address    192.168.3.220
Destination Server
Client/Server
Conversation ID
RFC Trace Rec. Status     5
Sent Bytes                0
Received Bytes            12.166
Total Sent Bytes
Total Received Bytes
ABAP program name
RFC Time                  364328.935

Best Practice SAP HANA Unify tables

I have 2 tables from differents systems With The same structure . We need unify. It´s possible Do It with Calculate View, and after the start this analytics and anothers Calculate View ?.
Same Name, and different Schema
Thanks

I have 2 tables from differents systems With The same structure . We need unify. It´s possible Do It with Calculate View, and after the start this analytics and anothers Calculate View ?.
Same Name, and different Schema
Thanks

SLD Best Practices

Hi
From where can I get the best practices related to SLD?
My XI system Landscape contains following systems.
Sandbox
Development
Quality
Production
I am considering following options:
Individual SLD for each system.
One SLD for Sandbox, Second for Development and Quality and Third for Production.
One for Sandbox, Development and Quality and Second for Production.
I have some advantages and disadvantages in my mind regarding each approach however I would request forum to please share their experiences.
Further to this there is Solution Manager also in the system which has its own SLD. Should that be utilized or should that be kept aloof from the XI system.

Hi,
My opinion, one SLD for each environment is good.
Just go thru following links -
SLD
Central SLD vs SLD for each XI instance
SLD best practices
SAP NW 2004(s) SOLMAN/SLD/SLM best practice
SLD best practices
Check how to guides from service.sap.com.
Hope this helps..
Regards,
Moorthy

Diff Between Best Practices & Business Packages

Dear Master
Can u give a brief difference between
Best Practices & Business Packages?
thankx

Hi,
Best Practices : SAP Best Practices provide a toolset that helps IT and functional project team members to quickly deploy functionality in SAP solutions - from SAP NetWeaver, to core SAP applications. This toolset comprises a mix of step-by-step instructions, preconfiguration, sample master data, code samples (where applicable) and end-user training - organized by technical or business scenarios that you might want to implement in your landscape.
http://help.sap.com/content/bestpractices/crossindustry/bestp_based_netweaver.htm
Business Packages : The SAP NetWeaver Portal offers a state-of-the-art portal solution. However, to make a portal useful to all the people it seeks to serve, it must not only provide general portal capabilities, but also content designed specifically to serve users in various industries and business areas.
SAP provides such pre-assembled content bundled as business packages for completing business tasks. In essence, the business packages provide out-of-the-box portal applications that can be easily modified to suit a customer's needs.
http://www.sdn.sap.com/irj/sdn/contentportfolio
Hope this helps.
Cheers!
Sandeep Tudumu

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

Best Practice - HCM service

Hi,
    The ESS latest package was uploaded initially into the portal. This package consists of mostly the Webdynpro iviews.
    Later it was decided to use the Best practice, so it is uploaded. Now all the services provided in the Best practice is available in one common folder, except for the ESS. The iviews available in this Best practice are mostly the transaction iviews.
    My query is that, why the HCM (ESS) services are not there under the best practice folder? Is it due to the already uploaded ESS package? What should i do to avail the HCM services of the best practice?
It's urgent. plz help. All useful answers will be rewarded.

Thanks Bharathwaj for the reply. Here is the link.
https://websmp104.sap-ag.de/swdc
In the website "SAP Software Distribution Center" select the category "Download" -> "Installations & Upgrades" -> "Entry by Application Group" then select "SAP Best Practices" -> "SAP BP PORTALS".
In this the EP V2.60 version was downloaded.

Goods return best practice

Hi,
Kindly help me out in following senario
I raise a purchase order for 100 qty of goods at $2. I do a MIGO and receive all the quantity in to my Inspection stock (QM is activated). 80 items are OK and 20 not. So 80 of them are transfer posted to unrestricted stock and rejected 20 is transfer posted to restricted stock.
My question is what is the best practice SAP business process I need to follow in order to
1) return the rejected 20 back to the vendor and then
2) replace them with another 20 items from the same vendor?
3) what reports can I run to see the goods return information in SAP?

To answer the question :
1) return the rejected 20 back to the vendor and then
You can go to MIGO transaction, and choose "return delivery", and state the amount of money that will be returned
2) replace them with another 20 items from the same vendor?
Basically you can do several good receipts to a purchase order. So after you return delivery do a good receipt with reference to the same PO number
3) what reports can I run to see the goods return information in SAP?
What kind of reports do you want? if you want to see the material for each material document number, report using MB51 would be the best option. Either way, you can create a custom report for more specific kind of report
Hope it helps

BASELINE PACKAGE V 5.600 best practice,preconfigured smartforms isfor free?

Hello i want install in the system of my customer the BASELINE PACKAGE V 5.600 because i need preconfigured smartforms.
I have a question. if i use the user id of my customer in servicemarketplace the customer have to pay BASELINE PACKAGE V 5.6000 or IS FOR FREE??
here is described the package: http://www.scribd.com/doc/6120793/SAP-Best-Practices-Whatsnew-V5600-En
here the path on servicemarketplace:
Installations and Upgrades
Installations and Upgrades -> SAP Best Practices -> SAP BP BASELINE PACKAGE -> SAP BP BASELINE -> Package I -> BASELINE PACKAGE - V1.- V5.600
Thanks a lot!!

Hi,
If you are able to download it directly then i dont think it is a paid consulting.
Prior to providing the service, SAP mentions that it would be a paid service & asks for your approval. If you give the approval, then only it processes further.
If you are not prompted with any such information, then please go ahead & download.
Best regards,
Prashant

BPC Best Practices: Sales Planning (BP2)

Im trying to follow these instructions:
1. Log on to Interface for Excel.
To do so start the SAP BPC Launch Page from your desktop icon or via the Start menu of your desktop, then in the Programs folder choose SAP -> Business Planning and Consolidation.
2. On the SAP BPC Launch Page, choose Interface for Excel. In the dialog box, select the AppSet SAP_BP_Planning and the Application Sales_Planning.
My problem is that in my BPC Launch Page (at step 2) I don't have these options:
AppSet: SAP_BP_Planning
Application: Sales_Planning
These are the options that I have:
AppSet: ApShell (in the combo box)
Application: (nothing in the combo box)
Can anyone figure it out why i dont have those options (SAP_BP_Planning, Sales_Planning) ?
Thanks

The version I have is BPC 7.5 SP4 with SQL Server 2005
Im new at this, I installed this software in a Windows Server 2003 Virtual Machine and now im trying to learn how to use this software. I have downloaded the configuration guide and those steps are there. This is the only one step that i couldn't follow:
3 Prerequisites
Before you start installing this BPC scenario, you must install prerequisite scenarios. For more information, see the BPC prerequisite matrix (Prerequisites_Matrix_[xx]_EN_JP.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example, BPC refers to the SAP Best Practices SAP BusinessObjects Planning and Consolidation 7.5: Prerequisites_Matrix_BPC_EN_JP.xls). This document can be found on the SAP Best Practices documentation DVD in the folder \BPC_JP\Documentation\.
I couldn't find that file in the Best Practices folder (50101040)
Thanks

Best Practice of using ERM (Role Expert) in Landscape

Hello,
Can anyone tell me what is the best practice (choice) of using ERM in the SAP landscape?
1. Creating a role in DEV system using ERM and using SAP standard transport process to transport role to QAS and PRD systems.
OR
2. Creating a role in all systems in ladscape (DEV, QAS and PRD).
Please share if you have any best practice implementation scenarios.
Appreciate for the help.
Thanks
Harry.

Harry,
The best practice is to follow Option 1. You should never directly create a role in Prod system. This is what SAP recommends as well.
Alpesh

SAP PI conceptual best practice for synchronous scenarios

Hi,
 Apologies for the length of this post but I'm sure this is an area most of you have thought about in your journey with SAP PI.
 We have recently upgraded our SAP PI system from 7.0 to 7.1 and I'd like to document best practice guidelines for our internal development team to follow.
I'd be grateful for any feedback related to my thoughts below which may help to consolidate my knowledge to date.
 Prior to the upgrade we have implemented a number of synchronous and asynchronous scenarios using SAP PI as the hub at runtime using the Integration Directory configuration.
No interfaces to date are exposes directly from our backend systems using transaction SOAMANAGER.
 Our asynchronous scenarios operate through the SAP PI hub at runtime which builds in resilience and harnesses the benefits of the queue-based approach.
 My queries relate to the implementation of synchronous scenarios where there is no mapping or routing requirement. Perhaps it's best that I outline my experience/thoughts on the 3 options and summarise my queries/concerns that people may be able to advise upon afterwards.
 1) Use SAP PI Integration Directory. I appreciate going through SAP PI at runtime is not necessary and adds latency to the process but the monitoring capability in transaction SXMB_MONI provide full access for audit purposes and we have implemented alerting running hourly so all process errors are raised and we handle accordingly. In our SAP PI Production system we have a full record of sync messages recorded while these don't show in the backend system as we don't have propogation turned on. When we first looked at this, the reduction in speed seemed to be outweighed by the quality of the monitoring/alerting given none of the processes are particularly intensive and don't require instant responses. We have some inbound interfaces called by two sender systems so we have the overhead of maintaing the Integration Repository/Directory design/configuration twice for these systems but the nice thing is SXMB_MONI shows which system sent the message. Extra work but seemingly for improved visibility of the process. I'm not suggesting this is the correct long term approach but states where we are currently.
 2) Use the Advanced Adapter Engine. I've heard mixed reviews about this functionaslity, there areh obvious improvements in speed by avoiding the ABAP stack on the SAP PI server at runtime, but some people have complained about the lack of SXMB_MONI support. I don't know if this is still the case as we're at SAP PI 7.1 EHP1 but I plan to test and evaluate once Basis have set up the pre-requisite RFC etc.
 3) Use the backend system's SOAP runtime and SOAMANAGER. Using this option I can still model inbound interfaces in SAP PI but expose these using transaction SOAMANAGER in the backend ABAP system. [I would have tested out the direct P2P connection option but our backend systems are still at Netweaver 7.0 and this option is not supported until 7.1 so that's out for now.] The clear benefits of exposing the service directly from the backend system is obviously performance which in some of our planned processes would be desirable. My understanding is that the logging/tracing options in SOAMANAGER have to be switched on while you investigate so there is no automatic recording of interface detail for retrospective review.
 Queries:
 I have the feeling that there is no clear cut answer to which of the options you select from above but the decision should be based upon the requirements.
 I'm curious to understand SAPs intention with these options -
 - For synchronous scenarios is it assumed that the client should always handle errors therefore the lack of monitoring should be less of a concern and option 3 desirable when no mapping/routing is required?
 - Not only does option 3 offer the best performance, but the generated WSDL is ready once built for any further system to implement thereby offering the maximum benefit of SOA, therefore should we always use option 3 whenever possible?
 - Is it intended that the AAE runtime should be used when available but only for asynchronous scenarios or those requiring SAP PI functionality like mapping/routing otherwise customers should use option 3? I accept there are some areas of functionality not yet supported with the AAE so that would be another factor.
 Thanks for any advice, it is much appreciated.
 Alan
Edited by: Alan Cecchini on Aug 19, 2010 11:48 AM
Edited by: Alan Cecchini on Aug 19, 2010 11:50 AM
Edited by: Alan Cecchini on Aug 20, 2010 12:11 PM

Hi Aaron,
I was hoping for a better more concrete answer to my questions.
I've had discussion with a number of experienced SAP developers and read many articles.
There is no definitive paper that sets out the best approach here but I have gleaned the following key points:
- Make interfaces asynchronous whenever possible to reduce system dependencies and improve the user experience (e.g. by eliminating wait times when they are not essential, such as by sending them an email with confirmation details rather than waiting for the server to respond)
- It is the responsibility of the client to handle errors in synchronous scenarios hence monitoring lost through P-P services compared to the details information in transaction SXMB_MONI for PI services is not such a big issue. You can always turn on monitoring in SOAMANAGER to trace errors if need be.
- Choice of integration technique varies considerably by release level (for PI and Netweaver) so system landscape will be a significant factor. For example, we have some systems on Netweaver 7.0 and other on 7.1. As you need 7.1 for direction connection PI services we'd rather wait until all systems are at the higher level than have mixed usage in our landscape - it is already complex enough.
- We've not tried the AAE option in a Production scenarios yet but this is only really important for high volume interfaces, something that is not a concern at the moment. Obviously cumulative performance may be an issue in time so we plan to start looking at AAE soon.
Hope these comments may be useful.
Alan

Best practice SAP landscape

Similar Messages

Maybe you are looking for