mySAP.com 

Definition

In the mySAP.com substructure, you can analyze and document how you implement your SAP Internet solution in your enterprise. The questions and CI templates contained here focus on the Workplace and the Marketplace. The project documentation stored in this substructure provide guidelines for successfully implementing mySAP.com.

Use

Customer input templates exist for all structure items. Using these templates you can document and analyze the main areas of the mySAP.com substructure. The information you enter here is essential for drawing up your Business Blueprint. The customer input template for the mySAP.com substructure is made up of the following sections:

CI template section for mySAP.com

Content

  1. Requirements/expectations

Construct a bulleted list of requirements and expectations for this structure item. This list should be specific to the customer and reflect their input. Critical points should be clearly visible.

  1. General description

Describe in as much detail as possible how this structure item will be used in the customer’s enterprise. The most important business processes should be described in detail in this section.

  1. Changes to enterprise structure

Describe the effect of this structure item on the customer’s enterprise structure.

  1. Inter-enterprise changes

Describe changes to your enterprise resulting from the implementation of processes involving an electronic marketplace or other companies.

  1. Change Management considerations

Describe all change management activities that are necessary to fully support this area.

  1. Description of improvements

Describe improvements which will result from implementing mySAP.com. Be sure to include any impact on business drivers.

  1. Description of functional deficits

Detail any real or perceived gaps in functionality that have become evident through the business process review sessions. Enter "None apparent" if the customer’s requirements seem to have been fulfilled.

  1. Approach to tackling functional deficits

Address any real or perceived gaps in system functions including workarounds, user exits or ABAP, and so on. Look for the best high-level solution. If no solution is evident, the impact on the customer and the project must be clear, so that the team can decide how best to proceed. Enter "None apparent" if the customer’s requirements seem to have been fulfilled.

  1. Notes on further improvements

Describe future or potential improvements, as well as issues to be clarified in a future SAP release or project phase. Any issues raised in the process review that are outside the current project scope should be recorded here.

  1. Authorization and user roles

Describe your security concept. Don't cover the creation of authorizations in too much detail. Sensitize the team to the system functions and get the process owners to think about access to the system and its data.

  1. System configuration/Customizing

Describe issues of importance to the customer in relation to system configuration. Details are not required, but be sure to address any issues addressed during the review.

  1. Technical considerations

Describe technical considerations for the implementation of your Internet solution. Address areas such as the system infrastructure, Single Sign On, and the SAP Business Connector.

  1. Project-specific information

Enter any project-specific information, which has not been covered in the sections above.