Skip to Content

Before You Begin

Who Should Use this Document?

This document is intended for technical and business resources who have an interest in the security process for the SAP BPC solution. 

How Should You Use this Document?

This document details the process flow and other related content associated with the process and approvals of managing the
security for SAP BPC content. 

Add a New User

Process Flow

Add_User_Process.png


Initiating and Approving the Request

  1. The business makes a request to have access to either SAP Business Planning and Consolidation (BPC) and/or the EPM Add-In for MS Excel
    1. The user, their manager, a peer, or a content owner may make the request
  2. The request should come through the Enterprise Service Desk (ESD) – there is no formal document or form required
    1. The request, however, should denote the following things, although the content owner(s) may need to provide assistance
      • The environment in BPC the user needs access to
      • Where the user can access data (data access profile)
      • What the user can do (task profile)
      • Often times, the easiest thing might be to communicate whose rights to mirror
      • Enough information to ensure the correct user is being added to the system
  3. The ESD creates a ticket and routes it to the SAP Enterprise Performance Management group.
  4. The BPC Administrator reviews the request and clarifies any questions with the business.
  5. At this point, the BPC Administrator determines whether there are any licenses available to extend.
  6. In addition, the BPC Administrator gains approval from the content owner in the business

Processing the Request

  1. Once all required approvals are obtained, the BPC Administrator proceeds with processing the request
  2. The BPC Administrator creates two new, related tickets:
    1. One to the ESD to assign the new user to the appropriate Active Directory (AD) group for access to the Citrix connection for the EPM Add-In for MS Excel
      • ESD notifies the BPC Administrator that their
        task is complete
    2. One to SAP Security to add the user to the production instance under one of three profiles in the back-end so the BPC Administrator can assign the user to the appropriate rights in the front-end
      • Z1:BPC_GENERAL_ALLUSER – for most all business users
      • Z3:BPC_DEVELOPER – requires above and adds the ability to run ZUJBR (business initiated backup in BPC but not restore
        functionality)
      • Z4:BPC_ADMINISTRATOR – for IT resources who support and develop in the BPC solution
      • SAP Security notifies the BPC Administrator that their task is complete
  3. Once SAP Security adds the user to the back-end, the BPC Administrator can pull the user in to the front-end security in the BPC web administration and assign the user to the appropriate team(s).

Communications and Closing the Request

  1. SAP Security notifies the user of their temporary password, directly
  2. The BPC Administrator notifies the new user that the security request has been completed and provides first time user instructions for changing their temporary password and accessing the content via the web and the EPM Add-In for MS Excel via Citrix
  3. The BPC Administrator will add the user to the appropriate Outlook distribution list:
    1. *SAP_BPC-KeyStakeholders – used to communicate to power users and content owners in the solution
    2. *SAP_BPC-Users – used to communicate to all users from report viewers only to business developers and their managers
  4. The BPC Administrator will update the BPC Security spreadsheet for managing licenses.
  5. The BPC Administrator will close out the original Remedy incident associated with the user’s request for access to SAP BPC / EPM Add-In for MS Excel
  6. SAP Security will close out the Remedy incident associated with adding the user to the back-end of SAP BPC
  7. ESD will close out the Remedy incident associated with adding the user to the AD group



Modify an Existing User

Process Flow

Modify_User_Process.png

Initiating and Approving the Request


  1. The business makes a request to modify access to either SAP Business Planning and Consolidation (BPC) and/or the EPM Add-In for MS Excel
    1. The user, their manager, a peer, or a content owner may make the request
  2. The request should come through the Enterprise Service Desk (ESD) – there is no formal document or form required
    1. The request, however, should denote the following things, although the content owner(s) may need to provide assistance
      • The environment in BPC the user needs access modifications to
      • Modifications related to where the user can access data (data access profile)
      • Modifications related to what the user can do (task profile)
      • Often times, the easiest thing might be to communicate whose rights to mirror
      • Enough information to ensure the correct modification(s) is(are) being made to the system
  3. The ESD creates a ticket and routes it to the SAP Enterprise Performance Management group.
  4. The BPC Administrator reviews the request and clarifies any questions with the business.
  5. The BPC Administrator gains approval from the content owner in the business

Processing the Request


  1. Once all required approvals are obtained, the BPC Administrator proceeds with processing the request
  2. The BPC Administrator possibly creates one new, related ticket:
    1. One to SAP Security to modify the user’s access in the production instance, provided the modification to
      rights in the front-end warrants a change in the back-end.  This is rare, and would typically only happen in a case where a business user is
      changing to/from the Business Developer Role from the General User Role.
      • Z1:BPC_GENERAL_ALLUSER – for most all business users
      • Z3:BPC_DEVELOPER – requires above and adds the ability to run ZUJBR (business initiated backup in BPC but not restore functionality)
      • Z4:BPC_ADMINISTRATOR – for IT resources who support and develop in the BPC solution
      • SAP Security notifies the BPC Administrator that their task is complete
  3. Once SAP Security modifies the user in the back-end, the BPC Administrator can modify the user’s rights in the front-end security in the BPC web administration by modifying the user assignment to the appropriate team(s).

Communications and Closing the Request


  1. The BPC Administrator notifies the user that the security modification has been completed.
  2. The BPC Administrator will modify the user enrollment for the appropriate Outlook distribution list, if necessary:
    1. *SAP_BPC-KeyStakeholders – used to communicate to power users and content owners in the solution
    2. *SAP_BPC-Users – used to communicate to all users from report viewers only to business developers and their managers
  3. The BPC Administrator will update the BPC Security spreadsheet for managing licenses, if necessary.
  4. The BPC Administrator will close out the original Remedy incident associated with the user’s request to modify access to SAP BPC / EPM Add-In for MS Excel
  5. SAP Security will close out the Remedy incident associated with modifying the access for the user in the back-end of SAP BPC

Delete a User

Process Flow

Delete_User_Process.png

Initiating and Approving the Request


  1. The business makes a request to have a user removed from SAP Business Planning and Consolidation (BPC) and/or the EPM Add-In for MS Excel
    1. The user, their manager, a peer, or a content owner may make the request
  2. The request should come through the Enterprise Service Desk (ESD) – there is no formal document or form required
    1. The request, however, should denote the following things, although the content owner(s) may need to provide assistance
      • Enough information to ensure the correct user is being removed from the system
  3. The ESD creates a ticket and routes it to the SAP Enterprise Performance Management group.
  4. The BPC Administrator reviews the request and clarifies any questions with the business.

Processing the Request


  1. Beyond clarifying / confirming the request to remove a user, there are no approvals required.
  2. The BPC Administrator proceeds with processing the request.
  3. The BPC Administrator creates two new, related tickets:
    1. One to the ESD to remove the user from the appropriate Active Directory (AD) group for access to the Citrix connection for the EPM Add-In for MS Excel
      • ESD notifies the BPC Administrator that their task is complete
    2. One to SAP Security to remove or disable (consistent with SAP Security’s current processes) the user from the production instance
      • SAP Security notifies the BPC Administrator that their task is complete
  4. Once SAP Security removes the user from the back-end, the BPC Administrator can confirm that the user has been removed from the front-end security in the BPC web administration.

Communications and Closing the Request


  1. The BPC Administrator will remove the user from the appropriate Outlook distribution list(s):
    1. *SAP_BPC-KeyStakeholders – used to communicate to power users and content owners in the solution
    2. *SAP_BPC-Users – used to communicate to all users from report viewers only to business developers and their managers
  2. The BPC Administrator will update the BPC Security spreadsheet for managing licenses.
  3. The BPC Administrator notifies the Content Owner of the license recovery
  4. The BPC Administrator will close out the original Remedy incident associated with the request to remove the user from SAP BPC / EPM Add-In for MS Excel
  5. SAP Security will close out the Remedy incident associated with removing the user from the back-end of SAP BPC
  6. ESD will close out the Remedy incident associated with removing the user from the AD group


To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply