Modifying SAP standard roles - best practice

Is there a Best practice How-to guide for configuring SAP BPs roles for client use.  I know I shouldn't change the content delivered by SAP but I'm not quite sure what I should delta link copy into client namespace.
I am implementing MSS.  Do I just delta link copy the Manager role into client namespace or I should make a delta link copy of the My Staff workset then make changes to the workset and assign it to a completely new ClientManager role?
I have the TransportEP6Content how to guide but it doesn't say explicitly what is best parctice.  This doc references 'HowTo Use Business Packages in Enterprise Portal 6.0' but it isn't where it says it is on service marketplace.

  'How to use Busiess Packages in Enterprise Portal 6.0' is available in this link.
Check out for the best practices.
Harini S

Similar Messages

  • Best practice when modifying SAP Standard Development Component

    Hello Experts,
    What is best practice when modifying SAP Standard Development Component (Java Web Dynpro)? Iu2019m looking for the best method to do modifications to SAP Standard DC so that my changes will be kept (or need low maintenance) after a new service package (or EHP) is applied.

      'How to use Busiess Packages in Enterprise Portal 6.0' is available in this link.
    Check out for the best practices.
    Harini S

  • SAP Standard Roles

    Hello everyone.
    What is SAP's best practice for using (customizing) the SAP standard roles? I have always used the standard roles as templates to customize for my customers. Is there a stated SAP best practice for this?
    If I use a standard role, customize it and copy it to the company namespace and the standard role it is customized off of changes, does my customized role change?
    How do release upgrades affect the standard SAP roles?

    Hi Todd,
    If you copy the roles to a your own namespace then they won't be touched during upgrade.
    I can't comment on what happens to standard roles during upgrade as I tend to avoid them.
    There is no accepted best practice around using standard roles, though there is reasonably wide belief that developing your own from the ground up is a better way to develop roles to meet your customers business processes. 
    I find that where standard roles have been used, the end user roles have generally a lot of unused transactions.  Functional & business people see a large list & choose most of them rather than building up from a subset of inscope transactions which are also used for training, BPP's etc.
    There is also the consideration that using standard roles guides you to building in the same way.  That's not to say it is a bad way, just can limit flexibility if you build down to a task level (nasty, nasty, nasty) or higher at a job or function level.

  • Break sap standard role into two sub roles

    i have one SAP standard role. now i want to break this role into two  sub roles. how shall do it.
    please suggest me.
    Edited by: Ramesh Sammiti on Jul 31, 2008 11:00 AM

    Hi Ramesh,
    When you say that you want to split the SAP Standard role into two roles:
    1.Do you mean to say that you want to split the transactions and authorization data of the SAP Standard role into two separate Z* or Y* roles?
    2.Do you want to copy the SAP Standard role into two different Z* or Y* roles and then modify the authorization data according to your company's requirements?
    In the above two scenarios you must copy the SAP Standard role into Z* or Y* roles in PFCG transaction with the appropriate naming convention and make necessary changes in both the transaction data and the authorization data.
    Please be clear which SAP Standard role you are willing to split into roles and i can provide more details.
    Hope this helps.
    Kiran Kandepalli

  • Deletion of SAP standard roles

    I have been asked by the client if we could delete all of the SAP standard roles. I think there are many good reasons not to delete them, but does anyone know what SAP's official recommendation would be to that question and could you point me to the documentation or SAP Note where that recommendations is written?
    So far all I have found is the following documentation( saying that:
    Do not change the delivered standard roles (SAP_), but rather only the copies of these roles (Z_). Otherwise, the standard roles that you have modified will be overwritten by newly delivered standard roles during a later upgrade or release change.
    But it does not say that you should never delete them.

    Christensen Jon Jagd wrote:>
    > The client want's to "clean up" the authorizations concept by deleting all of the unused roles. And all the SAP_* roles are not assigned to any users (and not generated neither).
    I've seen that before, the urge to clean up...... unused roles aren't the worst thing to happen on a system, as long as they're part of the concept.
    Come to think of it. I'd delete them from my test and prod systems to avoid confusion and/or (mis)use, but not from dev. On dev the majority of roles is not assigned to users anyway........
    > But I would like to know if for example "SAP recommends that you do NOT delete system delivered roles".
    I don't think such advice exists. Try to convince the client they should be kept on dev for future reference. Delete them on the other systems to clean up. Everybody happy.
    Edited by: Jurjen Heeck on Feb 12, 2008 10:16 AM

  • SAP standard roles for Mii inside of objects?

    It is our practice to rename SAP standard roles we plan to use "as is" to our company's naming convention.  I am being told by an Mii implementer that Mii uses the standard role names in objects and that by changing these names to our convention, I will create "complications" in their implementation process.  I find this hard to believe, it would be a departure from what (little) I know about SAP and how they handle authorizations and roles.  It also seems to be very limiting when it comes to customization in the future.
    Is this true?  Does Mii name standard roles inside of objects? (These "objects" were not clearly defined to me and I plan on calling a meeting so they may show me examples.)
    Anyone else on Mii have this issue?

    As far as I know, in Mii a user typically needs at least one of these roles:
    You can of course add additional roles with the authorization the different users require using your own naming convention.
    I think this is what the Mii implementer is talking about.
    Good luck!

  • SAP Business One Best-Practice System Setup and Sizing

    <b>SAP Business One Best-Practice System Setup and Sizing</b>
    Get recommendations from SAP and hardware specialists on system setup and sizing
    SAP Business One is a single, affordable, and easy-to-implement solution that integrates the entire business across financials, sales, customers, and operations. With SAP Business One, small businesses can streamline their operations, get instant and complete information, and accelerate profitable growth. SAP Business One is designed for companies with less than 100 employees, less than $75 million in annual revenue, and between 1 and 30 system users, referred to as the SAP Business One sweet spot. The sweet spot covers various industries and micro-verticals which have different requirements when it comes to the use of SAP Business One.
    One of the initial steps during the installation and implementation of SAP Business One is the definition of the system landscape and architecture. Numerous factors affect the system landscape that needs to be created to efficiently run SAP Business One.
    The <a href="">SAP Business One Best-Practice System Setup and Sizing Wiki</a> provides recommendations on how to size and configure the system landscape and architecture for SAP Business One based on best practices.

    For such high volume licenses, you may contact the SAP Local Product Experts.
    You may get their contact info from this site

  • What are the methods to modify SAP standard tables?

    what are the methods to modify SAP standard tables?

    these are the two methods.. but customizing includes we, as a developers do not use.
    generally we use .APPEND structures to modify standard tables.
    note that we need an access key to modify atandard tables.
    we can create an apend structure and add that structure to the standard table at the end.
    note that .append structures should only be added only at the end.
    that is the reason we use .append structures to modify standard we should not include a field in the middle and disturb the original order of the standard table fields as it may effect many objects depending on the standard table.
    but Some standard tables for which there is a LONG datatype field can never be modified.
    the reason is the LONG datatype field should always be there at the end and also .APPEND strutures should always be there at the end. there will be a conflict. so, some standard tables can not be appended.

  • Where-Used List: Modifying SAP standard function module

    We have decided to modify SAP standard function module SD_SCHEDULING. But before that, we need to understand what impact this modification will have in the system. We will also estimate the risks with this modification.
    Therefore, I have taken Where-Used List for this function module. We are aware that this list is not comprehensive.
    Do you know any other way we could use to understand better what impacts this kind of modification may have? My colleagues say that this is the only way.
    Thanks in advance for your help.
    Jarmo Tuominen

    Hi Jarmo,
    Try this
    1). Goto Se16 and check the contents of table 'CROSS'.
    2). Enter 'F' in the first selection screen field
    3). In the NAME field enter the Function module SD_SCHEDULING and execute.
    4). The list will give you where all the FM has been used.
    Kindly note this is almost the same as doing a where used list. The where used list will only work correctly if the 'Update Navigation Index' works correctly in your system. So just to ensure the result of your where used list you can follow the above steps. This does not require the Update Navigation Index.
    Hope this helps

  • SAP Human Capital Best Practice Reports

    Hi friends!!!
    I'm currently working with a client that is looking for a list of SAP Human Capital Best Practice Reports. I'm having difficulty finding a list of SAP HCM best practice reports. Does anyone have a list? Or can you point me in the right direction?
    Thanks in Advance
    Thanks & Regards

    Program Description
    Wage Type Reporter. Returns pay for particular wage types. To submit from new report you will need to create copy and export value to memory.
    Delimit IT1000 and related 1001s. Program will delete any 1001 infotypes whose start date is after the delimit date.
    Extend the end date on delimited records. Very useful when you delimit a bunch of records incorrectly, and need to change the end date.
    Delimit infotypes (IT1001)
    Statutory Maternity Pay(SMP)
    Statutory Sickness History(SSP)
    List all HR transactions and there uses
    Personal work schedule, also accessed via PA20/PA30 infotype 2001
    HR Report to list all logged changes in infotype data for an employee. Uses the PCL4 Audit Cluster.
    HR Report to delete audit data from the PCL4 Audit Cluster
    Delete all info for an employee number, including cluster data and infotypes
    View/Delete records from PCL1 Cluster
    View/Delete records from PCL2 Cluster
    View/Delete records from PCL3 Cluster
    View/Delete records from PCL4 Cluster
    you can find more in the link

  • SAP Standard roles assignment

    I want to assign a SAP standard role SAP_BC_BMT_WFM_ADMIN to a user.
    Since I do not directly assign a SAP standard role to a user,i created a copy of the SAP_BC_BMT_WFM_ADMIN of the role and tried assigning it to the user.
    But when I tried to generate the role I was not able to because all the objects are Inactive.So when i tried to activate the object it is not possible to do so.
    Can anyone provide me a solution for this.

    > But when I tried to generate the role I was not able to because all the objects are Inactive.
    Please try to tell us a bit more about what you see and which messages you get. I had a look at this role in my customers'system and did not see any deactivated objects.

  • Download all roles Individually and list all the SAP standard roles

    Hi ,
    I have two questions .
    1. I want o download all the roles individually in SAP.
    2. I want to list all the SAP standard roles whose profile is generated.
    Can anyone help me . to achieve this

    I am no sure what kind of problem you have faced that requires revert back. Which took 2 days. If it's for mass role revert back then mass role download should work. If it few selective role then change history should help you out.
    Anyway I might pull this out of the topic.
    Even you download mass role in a single file then also if you want then can upload a single role only with 2-3 mins spending on replace function in notepad!!
    Let say you have taken 1000 role in a single file and want to upload a specific role only. Open the file (copy of the file) in a notepad. Now replace(Ctrlh) LOADED_AGRS with nothing. Find(Ctrlf) the role you want to upload. In begining of that line paste LOADED_AGRS
    Above file will upload the specific role only.
    Arpan Paik

  • Failover cluster File Server role best practices

    We recently implemented a Hyper-V Server Core 2012 R2 cluster with the sole purpose to run our server environment.  I started with our file servers and decided to create multiple file servers and put them in a cluster for high
    availability.  So now I have a cluster of VMs, which I have now learned is called a guest cluster, and I added the File Server role to this cluster.  It then struck me that I could have just as easily created the File Server role under my Hyper-V
    Server cluster and removed this extra virtual layer.  
    I'm reaching out to this community to see if there are any best practices on using the File Server role.  Are there any benefits to having a guest cluster provide file shares? Or am I making things overly complicated for no reason?
    Just to be clear, I'm just trying to make a simple Windows file server with folder shares that have security enabled on them for users to access internally. I'm using Hyper-V Core server 2012 R2 on my physical servers and right now I have Windows
    Server Standard 2012 R2 on the VMs in the guest cluster.
    Thanks for any information you can provide.

    Generally with Hyper-V VMs available, we will install all roles into virtual machines as that will be easy for management purpose.
    In your situation the host system is a server core, so it seems that manage file shares with a GUI is much better.
    I cannot find an article specifically regarding "best practices of setting up failover cluster". Here are 2 articles regarding build guest cluster (you have already done) and steps to create a file server cluster. 
    Hyper-V Guest Clustering Step-by-Step Guide
    Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Composite Release Roles Best Practice

    I have a question in regards to best practice for utilizing composite release roles.
    We had an issue recently where Purchasing Doc Type (M_BEST_BSA - BSART), Release Code (M_EINK_FRG - FRGCO) and Release Group (M_EINK_FRG - FRGCO), which are maintained at the task role were over written with blanks when derived from the template role.  The template role has these three fields maintained as blanks.  All other data is consisten from the template role to the task role with the exception of the Organizational Levls (ie Plant, Purchasing Org, Purchasing Group).  We then have a variety of task roles that make up the composite.
    Would it make sense to maintain these three fields as Org Level data at in the task role?
    What are our other options?
    Thanks for your assistance.

    We do have DEV, QA, PRD, Training and Sandbox environments.  Our standard practice is to develop in DEV (200) role out to the other DEV clients and then transport to QA for UAT.  I have come across on occasion where the roles are not consistant across all DEV clients and if development work was completed on a role in DEV that was not consistant with the production role then we would be fubar.  This did occur a few weeks back; however, it was caught in time.
    Chain of events went as follows
    1. Request submitted to remove a plant value
    2. Dev work completed and moved to QA.  Based on screen shots of UAT we can see that the three fields were yellow at this point (blank values)
    3. End user did not recognize the caution flags as they were only looking at org value to ensure plant was removed.
    4. Developer failed to highlight the unmaintained fields
    5. Roles moved to production which halted purchasing teams
    This hole thing is very confusing 
    My only guess was the development work was completed on an old role in the wrong dev client.  But then this opens up another issue.  Why was there an old role as standard practice is to move the new roles to all dev clients once completed.

  • SAP PI conceptual best practice for synchronous scenarios

    <br /><br />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.
    <br /><br />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.
    <br /><br />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.
    <br /><br />Our asynchronous scenarios operate through the SAP PI hub at runtime which builds in resilience and harnesses the benefits of the queue-based approach.
    <br /><br />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.
    <br /><br />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.
    <br /><br />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. 
    <br /><br />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. 
    <br /><br />Queries:
    <br /><br />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.
    <br /><br />I'm curious to understand SAPs intention with these options  -
    <br /><br />- 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? 
    <br /><br />- 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?
    <br /><br />- 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.
    <br /><br />Thanks for any advice, it is much appreciated.
    <br /><br />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.

Maybe you are looking for