Solution Documentation for Custom Development

Size: px
Start display at page:

Download "Solution Documentation for Custom Development"

Transcription

1 Version: 1.0 August 2008 Solution Documentation for Custom Development Active Global Support SAP AG 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 1 of 53

2 1 MANAGEMENT SUMMARY SAP STANDARDS FOR E2E SOLUTION OPERATIONS SOLUTION DOCUMENTATION FOR CUSTOM DEVELOPMENT AT A GLANCE Documentation Content Location and Format of Documentation Content Documentation Language REQUIREMENTS FOR MINIMUM DOCUMENTATION CONTENT Create a Project in SAP Solution Manager System and Application Landscape Physical System Landscape Solution Definition Application Components and Custom Namespaces Business Scenario and Business Process Documentation Interface Documentation Documentation of Background Jobs Transactions and User Entry Points Performance and Volume KPIs Development object list or Customizing Objects Functional Documentation / Business Background Integration and Volume Test Plan Documentation Application Operations Guide SAP AGS SAP Standard Solution Documentation for Custom Page 2 of 53

3 5 APPENDIX Template: Application Components and Namespaces Template: Interface Documentation Template: Job List Template: Performance and Volume KPIs Template: Functional Documentation Template: Test Plan Documentation Template: Application Operations Guide SAP AGS SAP Standard Solution Documentation for Custom Page 3 of 53

4 1 Management Summary With the increasing number of systems and technologies, the complexity of IT solutions is rising. The key to successful landscape planning and operation is an accurate and complete description of the solution landscape itself with all business processes. All reporting is based on this fundamental information. As part of SAP s standards for End-to-End Solution Operations, the standard for Solution Documentation describes in general how customers achieve the required transparency of their SAP solution. For SAP applications, a lot of documentation is already provided by SAP. For functionality developed by customers or third-party software providers, the availability of required documentation is not ensured. Therefore, additional requirements regarding solution documentation exist for such custom developments. This document describes the content of the required documentation as well as tools and formats to be used to deliver it. At least the specification of the development project, a list of all related code objects, and of the required configuration settings have to be available. This helps both customer support organizations and SAP Active Global Support to deliver support for custom developments effectively. This paper starts with a brief overview of the end-to-end solution operations standards. Then it describes the general motivation and basic requirements regarding solution documentation for custom developments in chapter 3. Content of chapter 4 of this document is an explanation of what has to be documented and where to store the information. Finally, the appendix (chapter 5) displays templates which can be utilized for solution documentation of custom developments SAP AGS SAP Standard Solution Documentation for Custom Page 4 of 53

5 2 SAP Standards for E2E Solution Operations Mission-critical operations is a challenge. While the flexibility of SAP-centric solutions rises, customers have to manage complexity, risks, costs, as well as skills and resources efficiently. Customers have to run and incrementally improve the IT solution to ensure stable operation of the solution landscape. This includes the management of availability, performance, process and data transparency, data consistency, IT process compliance, and other tasks. Typically, multiple teams in the customer organization are involved in the fulfillment of these requirements. They belong to the key organizational areas Business Unit and IT. While the names of the organizations may differ from company to company, their function is roughly the same. They run their activities in accordance with the corporate strategy, corporate policies (for example, corporate governance, compliance and security), and the goals of their organizations. Figure 2.1: Organizational model for end-to-end solution operations The different teams specialize in the execution of certain tasks: On the business side, end users use the implemented functionality to run their daily business. Key users provide firstlevel support for their colleagues. Business process champions define how business processes are to be executed. A program management office communicates these requirements to the IT organization, decides on the financing of development and operations, and ensures that the requirements are implemented SAP AGS SAP Standard Solution Documentation for Custom Page 5 of 53

6 On the technical side, the application management team is in direct contact with the business units. It is responsible for implementing the business requirements and providing support for end users. Business process operations covers the monitoring and support of the business applications, their integration, and the automation of jobs. Custom development takes care of adjusting the solution to customer-specific requirements and developments. SAP technical operations is responsible for the general administration of systems and detailed system diagnostics. And the IT infrastructure organization provides the underlying IT infrastructure (network, databases ). Further specialization is possible within these organizations as well. For example, there may be individual experts for different applications within SAP technical operations. Efficient collaboration between these teams is required to optimize the operation of SAPcentric solutions. This becomes even more important if customers engage service providers to execute some of the tasks or even complete processes. Customers have to closely integrate the providers of outtasking and outsourcing services into the operation of their solutions. Key prerequisite for efficient collaboration of the involved groups is the clear definition of processes, responsibilities, service level agreements (SLAs), and key performance indicators (KPIs) to measure the fulfillment of the service levels. Based on the experiences gained by SAP Active Global Support while serving more than 40,000 customers, SAP has defined process standards and best practices, which help customers to set up and run End-to-End (E2E) Solution Operations for their SAP-centric solutions. This covers not only applications from SAP but also applications from independent software vendors (ISVs), original equipment manufacturers (OEMs), and custom code applications integrated into the customer solution. There are 16 standards for solution operations defined by SAP: Incident Management describes the process of incident resolution Exception Handling explains how to define a model and procedures to manage exceptions and error situations during daily business operations Data Integrity avoids data inconsistencies in end-to-end solution landscapes Change Request Management enables efficient and punctual implementation of changes with minimal risks Upgrade guides customers and technology partners through upgrade projects esoa Readiness covers both technical and organizational readiness for enterprise service-oriented architectures (esoa) Root Cause Analysis defines how to perform root cause analysis end-to-end across different support levels and different technologies Change Control Management covers the deployment and the analysis of changes Solution Documentation and Solution Documentation define the required documentation and reporting regarding the customer solution 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 6 of 53

7 Remote Supportability contains five basic requirements that have to be met to optimize the supportability of customer solutions Business Process and Interface Monitoring describes the monitoring and supervision of the mission critical business processes Data Volume Management defines how to manage data growth Job Scheduling Management explains how to manage the planning, scheduling, and monitoring of background jobs Transactional Consistency safeguards data synchronization across applications in distributed system landscapes System Administration describes how to administer SAP technology in order to run a customer solution efficiently System Monitoring covers monitoring and reporting of the technical status of IT solutions Out of this list, this white paper describes the standard Solution Documentation for Custom Development SAP AGS SAP Standard Solution Documentation for Custom Page 7 of 53

8 3 Solution Documentation at a Glance The functionality delivered by standard applications does not always match completely with the requirements of a customer. Therefore, some projects may include the development of additional functionality or the change of existing functionality. These custom developments may be done by customers themselves, by third-party companies, or by SAP Custom Development. 3.1 Documentation Content Supporting such customer developments is often more difficult than the support of standard applications. A standard application is typically used by more customers than a specific custom development. In most cases, there is much more support experience regarding a standard application than there is regarding a custom development. And the risk gets even higher if the people involved in the development project have left the customer or the involved thirdparty company has vanished. Therefore, proper documentation of custom developments is especially important: Which parts of the project are impacted by the custom development? Why has the custom development been done (business background)? Which systems are involved? Are there any dependencies between the custom development and other systems/functions? Which business processes and process steps are changed? What are the transactions or entry points of the custom development? Which interfaces are used to integrate the custom development with standard applications? Which development objects have to be transferred from development to quality assurance and production system? How to operate the custom development? How to set up and execute integration and volume test for the custom development? 3.2 Location and Format of Documentation Content The minimum documentation required for custom development projects shall be stored within the project documentation tools provided in SAP Solution Manager 4.0 located in the customer solution environment. In case of multiple SAP Solution Managers in the customer landscape it is expected that the complete set of minimum documentation is located within the SAP Solution Manager that is also used for managing operations and maintenance tasks for 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 8 of 53

9 the involved system landscape. It is possible to start a project within one SAP Solution Manager during the development phase and later on transfer it to another SAP Solution Manager. In order to ensure the optimal delivery of SAP support services, it is important for SAP to find the minimum documentation in a standardized location and format. On the other hand, this lays the ground for leveraging many operation support functions offered via SAP Solution Manager (e.g. identification of affected custom business process by requested software or customizing change requests). Certain parts of the documentation are required to be stored in structured format for those parts the project documentation in SAP Solution Manager offers dedicated screens and structuring elements that shall be used. For unstructured type of information (textual descriptions), there are special template documents provided that shall be used to provide this information. Which information is expected in which format is explained in chapter Documentation Language It is required that all documentation requested within this document is provided in English. In case where SAP services shall cover this project it is important that SAP support engineers are able to read it. Without additional translation effort, this can only be guaranteed in a 24x7 mode if the documentation is available in English SAP AGS SAP Standard Solution Documentation for Custom Page 9 of 53

10 4 Requirements for Minimum Documentation Content Documentation can be extensive. To keep your focus on the information that is required most importantly, this chapter describes the key documentation for custom developments. You learn how to maintain this documentation within SAP Solution Manager. 4.1 Create a Project in SAP Solution Manager A container is required to collect all documentation regarding your custom development project. In SAP Solution Manager, these containers are called projects. Use transaction SOLAR_PROJECT_ADMIN in SAP Solution Manager to create a project (Project Administration from menu). You will use this ABAP transaction for all documentation tasks described in chapter 4.1 through 4.4). At first, it is just required that you create the Implementation Project and give it a meaningful title. Select the type Implementation Project (there is no special type for development projects but the implementation project type works fine). The solution may not be existing or known at the early project phases. The solution information shall be entered as soon as it is known. The information shall be available and up-to-date at the delivery of the Business Blueprint & Scope Check service. If you have a high level project description, you should upload this into the project description (optional). Figure 1: Project Administration - Header Data Screen 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 10 of 53

11 4.1.1 Definition of Project Keywords For each project, it is possible to define so-called project standards. In order to enable certain classification tasks later on, it is necessary to define a set of keywords that will then be available within your project. Therefore, you go to the Project Standards tab from the project header data screen, go into the sub-tab Keywords and click on the Project Template button. This brings you to the edit mode (see Figure 2). Figure 2: Project Template - Keyword Definition At the end of the keywords list add the additional keywords as shown in Table 1. Keyword CORE_PROC SAP SAP_EXT SAP_MOD CUST Table 1: New Project Keywords Name Core Business Process SAP Standard SAP with Extension SAP with Modification Custom Development Then save the new defined keywords. You have to do this task only for the first project you document as the project template data is available to all projects. As the final step, you need to add the keywords to the project in order to make them available for this special project. This is done by selecting the keywords in the keyword directory (where you have previously added them) and move them over to the project by clicking the double left arrow button. This has to be done for each project that you document SAP AGS SAP Standard Solution Documentation for Custom Page 11 of 53

12 4.2 System and Application Landscape To manage the development project and to operate the custom code later on, it is important to know which applications are concerned. The application landscape contains the list of software product versions involved in this project. The system landscape contains the list of logical components (placeholder for real physical systems independent of the system role like development, quality assurance or production) involved in this project. For understanding the realized business processes, it is essential to have the logical systems defined in the System Landscape tab. It is not required to have real existing systems already available. You can create new logical systems by just referring to the underlying product versions. After the real systems are known, you need to add them also in the System Landscape tab according to their role (see also chapter 4.3 Physical System Landscape). Figure 3: Project Administration - System Landscape Screen The creation of logical systems can be triggered out of the value help for the logical component or via the system landscape management application (transaction SMSY). You can also use existing logical components that have been defined earlier (e.g. during the definition of a solution). The product version information value help that you get for selecting a logical component already contains all available product versions for software delivered by SAP. The information is regularly updated via content updates into your SAP Solution Manager. In cases where a logical component requires additional product versions to be installed for this project, you need to list these product versions within the Additional Product Version De SAP AGS SAP Standard Solution Documentation for Custom Page 12 of 53

13 pendencies chapter within the document Application Components and Namespaces described in chapter 4.5. If you are using other 3 rd party or own software running outside any SAP system, you need to define a custom product version in order to be able to specify it as part of your system landscape. A logical component needs to be defined for each non-sap system as well. As we need to have the complete picture of all systems involved within your project we expect you to create custom product version entries for all such systems (see Figure 4). The product key shall be defined in the customer namespace. If the product uses an own database system this shall be flagged in the components tab. The Technical Instance flag indicates that this product does not provide any business logic but only technical functionality (e.g. a pure UI renderer). Figure 4: System Landscape - Maintain Custom Software Components If your custom product is built using multiple independent software components, you shall enter these as separate Main Instances. You can use these instances later to define business process steps to be executed on them. In case your custom developed solution has inter-company interfaces, you also need to define a logical component for the external endpoint of the interface. For such cases just define any product name that represents the external endpoint (e.g. EXTERNAL VENDOR) SAP AGS SAP Standard Solution Documentation for Custom Page 13 of 53

14 4.3 Physical System Landscape As soon as real physical systems exist on which the solution is running, you need to enter those into the system landscape shown above. In the early project phases, this will usually be development systems while in later stages the productive systems shall be added as well. Therefore, the system list in the system landscape tab offers several system roles. Before you can map physical systems to logical components, the physical systems need to be known to the SAP Solution Manager. The most comfortable and recommended way to make systems know to SAP Solution Manager is via a System Landscape Directory (SLD). Each system shall be registered at an SLD and the SLD connected to SAP Solution Manager (if multiple SLDs are used they can be consolidated into one SLD that is connected to SAP Solution Manager). Each system known to this SLD can directly be found in SAP Solution Manager and can be used via the value help where systems can be entered. If you enter a system for an already defined logical component you will only be offered by a selection of systems that match to the product version defined for the logical component. For non-sap systems, you have to define them manually - it is recommended to also do this in an SLD and to connect it to SAP Solution Manager. If you have not setup an SLD for providing the system information automatically, you may also create system definitions via data retrieval from the transport management system (for ABAP systems) or manually via the creation wizard out of the system landscape management transaction (SMSY Landscape Components right mouse click on Systems Create New System with Assistant) (see Figure 5). Figure 5: System Landscape Maintenance - System Creation Wizard 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 14 of 53

15 4.4 Solution Definition For the minimum documentation of a development project, this chapter is optional and can be skipped. For managing the operational tasks to keep the business processes running smoothly you have to define a so-called Solution within SAP Solution Manager. A solution contains the physical system landscapes as well as the business process definitions to be supported by it. A solution may thus include business processes from multiple projects. A new project also may fit into an already existing solution. In this case you should enter the solution name into the project header (see Figure 6). Figure 6: Project Header Data - Mapping to a Solution For creation of a new solution you can use a wizard in the SAP Solution Manager work center System Landscape Management (transaction SOLMAN_WORKCENTER) under Common Tasks Create Solution (see Figure 7). Figure 7: Solution Manager Work Center - System Landscape Management 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 15 of 53

16 4.5 Application Components and Custom Namespaces Besides the technical description of the product versions, you shall also define at least one custom application component within the application component hierarchy to identify the custom development application. This identification tag can then be reused in many places within SAP Solution Manager (e.g. as an identifier in a problem message to link it to this custom development). The top level component name is the minimum requirement. For complex projects, it may be useful to define sub-components for logically separated software parts as well. The application component hierarchy as well as the list of custom namespaces defined for the custom code shall be documented as a separate document to be uploaded into SAP Solution Manager. You add this and other information (described in the later chapters of this document) to the previously created project via transaction SOLAR01 (for maintaining business blueprint information for a project). If there are multiple projects defined, you can select the project via the menu path Business Blueprint Other Project. As mentioned already in chapter 4.2 System and Application Landscape, you shall document additional product version dependencies. This is necessary if there is more than one product version required to be installed on a certain logical component (typically one or more required Add-ons). The dependencies shall be described in the chapter Additional Product Version Dependencies of the template Application Components and Namespaces. This template is available in the appendix of this document. The documentation shall be uploaded at the project top level node into the Project Documentation tab using the name Application Components and Namespaces (see Figure 8 and Figure 9). Figure 8: Project Documentation in Project Business Blueprint (SOLAR01) 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 16 of 53

17 Figure 9: Upload Documentation File 4.6 Business Scenario and Business Process Documentation It is important that a realized custom development is documented within the context of the business processes where it is included. Business processes that belong to the same business scope shall be grouped into so-called business scenarios. Each business process is always assigned to one business scenario. Multiple business processes of one project may be assigned to the same business scenario. You may either define business scenarios and processes completely by yourself or start with a template scenario/process delivered by SAP. If you define the complete business scenario and business processes yourself from scratch, you can skip chapter Starting with an SAP delivered business scenario template It is very typical that a custom development extends or modifies business processes that are delivered with SAP standard applications. For SAP standard business scenarios and business processes, SAP delivers already a model and documentation inside the SAP business process repository (BPR). For each business process that is involved within your project you should try to find the closest SAP delivered business process model in BPR and copy it into your project documentation (see figure 10). This can be done in the Business Blueprint of your project. The SAP solution maps found under SAP Solution Maps help you to navigate to the suiting business scenarios SAP AGS SAP Standard Solution Documentation for Custom Page 17 of 53

18 Figure 10: Business Process Repository - Selection of Business Scenarios / Processes After you have selected the matching business scenario(s) and saved all SAP business you get the complete list of associated SAP standard business processes and have to delete those that you do not touch within this project (see Figure 11). Figure 11: Structured Documentation of Business Scenarios / Processes in Project 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 18 of 53

19 For each business process, you need to adjust the list of business process steps as well as the association to your logical systems in order to match the business processes that your development project will realize. For each additional logical business step that you realize via own custom software, you shall add an additional business process step in the step list and give it a name that briefly explains the business activity executed within this step Define missing business scenarios, processes and steps Whether you have started using an SAP template or not you may need to add further business scenarios, business processes and business process steps to completely describe your project. It is important that this business process documentation is understandable by somebody from outside who has good knowledge on the SAP business applications but has no knowledge about specific internals of your company (e.g. a service provider operating your system or an SAP support engineer who delivers a support service. Figure 12 provides a generic guideline for defining business scenarios, processes and steps. Besides this, it is important that each software activity that is executed on a separate logical component is also modeled as a separate business process step. If a business process step that is performed externally is important for understanding the whole business process, this step shall be modeled and assigned to a specific external logical component as well. The same is true for steps that are not executed by software but that are important for the process (e.g. a printed document has to be sent via post mail). You can also check out the SAP delivered standard business process templates within the SAP business process repository for many examples showing you the expected documentation granularity. Adding a new business scenario can be simply done in the Business Blueprint by adding a reasonable name into the Structure tab at the Business Scenarios node of the project tree and save it. This will create a new sub-tree under Business Scenarios which you will use for adding business processes SAP AGS SAP Standard Solution Documentation for Custom Page 19 of 53

20 Figure 12: Scenario, process, step, transaction To add a business process, you first select the Business Processes sub-node for the scenario where this process belongs to; add a reasonable name into the Structure tab, and save it. This will create a new sub-node under the Business Processes node with the chosen name. The scope of a business process step shall be the activity that executes a single logical step within the business logic. This is not necessarily the use of a piece of software but may also be the manual execution of some task (e.g. copy a file from a CD shipped via post mail into a special folder for further processing). For adding a business process step, you have to go to the Structure tab of the business process and enter a reasonable name into the in the Step Name column. The process step always needs to be assigned to a logical component. The logical component has to be defined beforehand as explained in chapter 4.2. If your business processes get data from an external system, you should also define this external system as a separate logical component and define a business process step on it. Each business process step has to be classified into one of the categories listed in table 2 by assigning the respective keyword to it (as defined previously in section 4.1.1). The keywords can be entered in the Administration tab of the business step within the sub-tab Keywords. With the Add button you get a selection list with the keywords that are assigned to the project. In this list, you mark the appropriate key word (see Figure 13) SAP AGS SAP Standard Solution Documentation for Custom Page 20 of 53

21 Keyword name / Category SAP Standard SAP with Extension SAP with Modification Custom development Table 2: Classification Types of Business Process Steps Meaning The step is fully realized with SAP standard code. The step is realized with SAP standard code with implemented custom extensions (e.g. BADI implementation). The step is realized with SAP standard code that was modified (i.e. some original SAP program code in the SAP namespace was changed). The step is realized with custom code within the custom namespace. Figure 13: Classify Business Process Step via Keyword Whenever you modify the behavior of an SAP business process significantly via implementing a standard extension hook (e.g. business add-in), you shall change the step classification from SAP standard to SAP with extension. For modifications of SAP business process steps via real modification of original SAP code, you shall change the step classification from SAP to SAP with modification. If the main 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 21 of 53

22 business activity originally performed by this step has also changed, this shall be reflected in a corresponding adjustment of the step name. For most business processes and process steps, there exist templates in the Business Process Repository (BPR) of SAP Solution Manager. Whenever possible, you should use these templates for documenting your enhancements. In case you do not find a well matching SAP business process template, you have to create a new business scenario respectively business process from scratch. The minimum information required is at least which parts of the business process are realized by the custom development or by SAP modifications as well as which business process steps are directly linked via standard SAP interfaces. Ideally, you should document the whole business processes in which the custom development is integrated. As you will enter both types (customer and SAP steps) manually in this case, it is important to change the step class from Custom to SAP (respectively SAP with extension or SAP with modification ) for those steps that are original SAP. It is important to understand which of the business processes are essential for your key businesses to work we call these processes the core business processes. A good indicator for a core business process is that you immediately would loose business or your logistics or production chain would be broken if this process is not available. A typical non core business process would be one that produces statistical data for reporting. You shall identify your core business processes by attaching the keyword Core Business Process to them. This can be done from the Administration tab of the business process in the very same way as the classification for business process steps was done. 4.7 Interface Documentation The next task is to document the SAP interfaces that are used within the business processes. You shall enter at least all interfaces that are used from custom coding. In order to do so, you shall use the Interface Documentation template document available in the appendix of this paper. For each interface, please enter the technology type, technical name and performance and volume KPIs. In order to map the interfaces to the business process steps where they are used, you also need to enter the source and destination step name. 4.8 Documentation of Background Jobs Background jobs are typically used to handle mass data processing without direct interaction with users. You shall document all background jobs used in your project. A background job shall be either entered directly at the business process step which the job realizes or on business process level at the business process that the job is part of. Go to the Job Documentation (see Figure 14) view in the Job Management work center and execute the common task Create Job Documentation (see Figure 15) to create the job documentation. The minimum information that shall be entered is the job name (as it can be found in the job scheduler). If you already know which scheduler is used, you can choose between Redwood Cronacle and the ABAP job scheduler (BC-XBP). If you don t know that yet, choose BC-XBP as scheduler. You need to define at least one job step via Add. In the job step details, you 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 22 of 53

23 have to enter a description text of the executed program, the program type (ABAP report, any external program or shell script or a command defined in the ABAP external command list SM69) and the technical name of the program it executes (e.g. ABAP report, executable program, shell script name). In order to map the job to the business process documentation of the project you need to fill in the job name into the job table within the attached Job List template document available in the appendix of this paper and specify the business process step where this background job is executed. Use the System Landscape tab to specify the logical component where the background job will be executed. If you have already defined a solution into that you have copied the business processes from this project, you should directly enter the business process step within the solution where the job is executed. If available, enter scheduling details, preconditions and limitations (e.g. dependency on other jobs, not in parallel with other jobs), error handling procedures (what to do if job aborts, what if it did not start or finishes too late) via the respective tabs, as well. The detailed description of the business functionality shall be described additionally within the functional documentation document of the business process step where the job is mapped to (see 4.12), Figure 14: Background Job Documentation Overview Screen 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 23 of 53

24 Figure 15: Background Job Detail Documentation Screen In the early phases of the project, you may not have all information ready for the complete background job documentation (e.g. responsible persons for monitoring or error handling may not be defined during the implementation phase). In such cases, you shall add the missing information as soon as they are known. 4.9 Transactions and User Entry Points Business process steps may be invoked by different means. They may be executed automatically by the system as a successor of a previous step (invoked via an interface), they may be executed as a scheduled background job, or an end user invokes them. The interfaces and background jobs have already been documented in the previous sections. This section covers the end user invocations. Therefore you shall document for each business process step which may be invoked manually by an end user the software entry points that the end user can use to do so. Such entry points may be ABAP transactions, WebDynpro applications, Business Server Pages, any URLs, programs etc. For entering this information, the separate tab named Transaction shall be used at business process step level (see Figure 16). If there are multiple possibilities to start the business process step (e.g. multiple transactions that can be used to perform the same business function), you shall enter each of these entry points separately. Select the type of the user entry point, the logical system where it is executed (usually the same that is used for the corresponding business process step) and the technical name of the entry point. The In Scope flag can be used to distinguish entry points that will be handled within this project or not. It is not used for minimum documentation and we recommend only documenting those that are in scope and therefore always mark that checkbox. The Standard radio button allows identifying one entry point that will be automatically executed when the Execute button at the process step in the project tree is clicked. We recommend choosing the one that is supposed to be the most heavily used or most important one SAP AGS SAP Standard Solution Documentation for Custom Page 24 of 53

25 In case you have already assigned a physical system to the logical system, you can chose the technical object name from a value help directly filled from the system otherwise you will get a warning message that the object name cannot be verified. For URLs, you can use placeholders for hostnames and port numbers if those are not yet known (e.g. Figure 16: Documentation of Transactions / User Entry Points 4.10 Performance and Volume KPIs For all core business processes expected volume figures shall be documented. This includes expected number of executions or per time unit, number of documents created, and number of concurrent users. It also includes expectations for maximum and average response times expected for certain business processes or single business process steps. You shall enter the expected volume figures at least for each core business process. If possible you should provide these figures at business process step level. For documenting this information you shall use the Performance and Volume KPIs template available in the appendix of this paper. The completed document has to be uploaded into the Project Documentation tab at the structural element where it belongs to (project, business scenario, business process, process step) Development object list or Customizing Objects All development objects that are newly created or modified within your project shall be documented within the development tab either on business scenario, on business process, or on business process step level. We recommend that you create separate development packages in the customer name space for each logical development. For modified SAP code you shall enter separate transport requests containing exactly the list of modified SAP objects SAP AGS SAP Standard Solution Documentation for Custom Page 25 of 53

26 Note that the Development tab is only available in the Configuration project phase and not in the Business Blueprint phase. From the project maintenance transactions (SOLAR01 for business blueprint and SOLAR02 for configuration) you can always switch to the other one via the menu path Environment Business Blueprint / Configuration. We highly recommend that you specify the packages respectively transport request object lists as closely as possible to the element in the hierarchy tree where the included development objects really belong to. If certain development objects are generic ones used in various steps of a business process or in all business processes of a business scenario, they should be put into a package respectively transport request on business process or business scenario level. The closer you can map development objects to business steps or processes, the more precisely it is possible to tell you which processes or steps may be affected by planned software change. Similar to documenting the development objects, you shall also document the business customizing objects. Therefore the Configuration tab shall be used. The configuration objects should be put into separate BC sets respectively dedicated customizing transport requests. Those BC sets and customizing transport requests shall also be added in the Configuration tab as precisely as possible to the related business process or business process step. In order to add a software package name, a BC set or a transport request you should have a logical system with a physical assignment of the corresponding development system in place. Also the connectivity from the Solution Manager system to this development system should be set up. This allows you directly accessing the object repositories on the development systems and put the references into Solution Manager. We highly recommend that you manage all your transports via a centralized transport management system. This can be setup within the Solution Manager itself or in any other SAP Web Application Server system. If the central transport management system is not part of the solution which is used by your project, then you have to add a logical and physical system into your solution landscape so that you can select the transport requests from there. In case you have no centralized transport management (not recommended) then you can also fetch transport requests from each system within your solution landscape (precondition: the physical systems and their connectivity have been defined in SAP Solution Manager). It is very typical that the list of development objects grows during the development phase. If you already have the packages for the logical units in the beginning you should reuse them to add further developments inside and thus need not change the documentation within the Solution Manager project. You are also not required to add all objects into one single request but you can define multiple transport requests in each development tab SAP AGS SAP Standard Solution Documentation for Custom Page 26 of 53

27 Figure 17: Transport Request Documentation 4.12 Functional Documentation / Business Background In order to understand the functionality that is realized by the custom code development, it is important that you provide additional textual information explaining the following topics: Business background information: What are the business reasons why this project was initiated? Which gaps of the SAP standard solutions have been identified that shall be closed by this project? Keep in mind that this documentation shall be understandable not only by the business persons from the customer but also by people not familiar with the customer s organization. This information shall be documented on project level. Business gaps closed Which gaps of the SAP standard solutions have been identified that shall be closed by this project? If internal organizational preconditions at the customer are necessary to understand the business requirements, these need to be documented as well. This information shall be documented either on project level or per business process scenario, process or step. Functionality What are the functions realized? For business process steps that contain modifications of SAP code, you shall document why this modification is required, which alternative modification-free options have been investigated and when this modification has been signed off by which person. For business process steps with extensions of the SAP standard, you shall explain what the extension functionally does. All this textual information shall be added in the Project Documentation tab at the structural element where it belongs to (project, business scenario, business process, or business process step) (see Figure 18). A Functional Documentation template is available in the appendix of this paper SAP AGS SAP Standard Solution Documentation for Custom Page 27 of 53

28 Figure 18: Add textual documentation 4.13 Integration and Volume Test Plan Documentation It shall be documented within one document on project level how you plan to setup and execute integration and volume tests that cover all business processes and all software components involved in the business processes of the project. You should also document the solution and the system landscape roles to be used for the tests. The technical solution shall be maintained within SAP Solution Manager in the system landscape information (typically as test system role). For the volume tests, you should document how these volume tests will be prepared and executed (e.g. test data preparation, real users with scripts or automated user simulation, ramp-up profile). Also clarify how much load you plan to produce during the tests and how this load is distributed on the business processes. Include also the volume testing of your background jobs in this documentation. Describe how many of those tests with which time interval in between are planned and how you measure the results (have errors occurred, what was the concurrent user number and the corresponding response times, what was the system load over time on each system, how many documents have been processed in which time frame). All information shall be documented using the Test Plan Documentation template available in the appendix of this paper Application Operations Guide The Application Operations Guide has to be provided by the development project team. It contains information on how the developed application can be operated. From the Application Operations Guide an Operations Handbook shall be derived that will be used by the operations team describing the operations tasks that need to be performed during the real operation of the solution. Information to be provided in the Application Operations Guide: 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 28 of 53

29 Monitoring of the application (business process level as well as technical level). How to detect problems respectively avoid critical situations or performance problems. How to monitor data growth. Support tools and troubleshooting guidelines for analyzing problem situations. How to find the root cause of problem situations. How to analyze performance problems. Consistency checking. How to verify data consistency (if replicated data exists). How to safely repair potential data inconsistencies. Management of the application. How to start/stop the complete application. How to change configuration. Administration tools to be used. How to backup and restore the complete solution. Regular tasks to be scheduled and monitored (automated background jobs as well as manual tasks). Scalability and high availability. How to scale up the solution for higher user or data volume. How to setup a high availability scenario. Transport and change management. How perform software changes on the complete solution and how to integrate all components into the one transport order concept. Remote supportability. How to setup safe remote access to all support relevant tools (e.g. special user roles for read only access permission, URLs to support tools). This information shall be documented using the Application Operations Guide template available in the appendix of this paper SAP AGS SAP Standard Solution Documentation for Custom Page 29 of 53

30 5 Appendix 5.1 Template: Application Components and Namespaces About this Template You use this template to document the application component hierarchy for your development. These component names can be used in Solution Manager Service Center to assign incidents to development areas. SAP also maintains an application component hierarchy for all its delivered software components. If your custom development was delivered by SAP custom development your component hierarchy may have already been included within the SAP component hierarchy. Otherwise you have to define it by yourself in the customer name space. Additionally this template shall be used to documents development name spaces that were used to keep all development objects under the same prefix. We recommend to request a name space from SAP (via https://service.sap.com/support Keys & Requests Development Namespaces) instead of using the generally reserved customer name spaces (Z* and Y*). Beside making it more easy for you to distinguish different projects objects doing so it also simplifies the potential need of merging different companies SAP systems. Application components should be typically created per SAP product which they extend and per business scenario. For very simple projects you may define even only one application component. Namespaces are typically created per SAP product. You would typically use just one namespace per SAP product where you develop custom code in. 1. Application Components List all application components that you have defined for your custom development and map it to the associated product, business scenario and eventually business process by filling the table below. If you defined hierarchically structured components then list all elements in the component tree with their mapping. Application Component (e.g. XX-PROJ-ABC)) Related area (project, product, business scenario) (e.g. Project ABC) 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 30 of 53

31 2. Development Namespaces List all namespaces that you have defined for your custom development and map it to the associated product and eventually business scenario and eventually business process by filling the table below. Development Namespace /CFCRMX2/ Related area (project, product, business scenario) (e.g. Project ABC, product CRM) 3. Additional Product Version Dependencies You have already documented the list of logical components and the product versions that they are based on within Solution Manager for your project. In cases where your project requires additional products to be installed on those logical components you need to list these required product versions in the following table. This is necessary because the Solution Manager based landscape model allows only one product version being associated to a logical component. Logical component name Product version name App. Server Type Description why needed 2008 SAP AGS SAP Standard Solution Documentation for Custom Page 31 of 53

SAP Standard Custom Code Management

SAP Standard Custom Code Management May 2009 SAP Standard Custom Code Management Whitepaper Active Global Support SAP AG Page 1 of 50 Table of Content: 1 Management Summary...4 2 SAP Standards for E2E Solution Operations...5 3 Custom Code

More information

Compare & Adjust How to Guide for Compare & Adjust in SAP Solution Manager Application Lifecycle Management

Compare & Adjust How to Guide for Compare & Adjust in SAP Solution Manager Application Lifecycle Management Compare & Adjust How to Guide for Compare & Adjust in SAP Solution Manager Application Lifecycle Management www.sap.com TABLE OF CONTENTS COPYRIGHT... 3 1.0 Motivation... 4 2.0 Method and Prerequisites...

More information

Document Management In SAP Solution Manager Application Lifecycle Management

Document Management In SAP Solution Manager Application Lifecycle Management Document Management In SAP Solution Manager Application Lifecycle Management www.sap.com TABLE OF CONTENTS 1.0 Motivation... 3 2.0 Method and Prerequisites... 4 2.1 Document storage in SAP Solution Manager...

More information

How-To Guide Manual Testing with SAP Solution Manager

How-To Guide Manual Testing with SAP Solution Manager SAP Solution Manager How-To Guide Manual Testing with SAP Solution Manager Applicable Releases: Solution Manager 7.0 EHP1 and above Target groups: Test Engineers, Quality Experts, Technology Consultants,

More information

HP Enterprise Integration module for SAP applications

HP Enterprise Integration module for SAP applications HP Enterprise Integration module for SAP applications Software Version: 2.50 User Guide Document Release Date: May 2009 Software Release Date: May 2009 Legal Notices Warranty The only warranties for HP

More information

Setup Guide Central Monitoring of SAP NetWeaver Proces Integration 7.3 with SAP Solution Manager 7.1. Active Global Support February 2011

Setup Guide Central Monitoring of SAP NetWeaver Proces Integration 7.3 with SAP Solution Manager 7.1. Active Global Support February 2011 Setup Guide Central Monitoring of SAP NetWeaver Proces Integration 7.3 with SAP Solution Manager 7.1 Active Global Support February 2011 Agenda Overview Landscape Setup Recommended Setup SLD/LMDB Synchronization

More information

Application Life-Cycle Management Solution Documentation

Application Life-Cycle Management Solution Documentation Application Life-Cycle Management Solution Documentation Solution Management Application Life-Cycle Management SAP AG Disclaimer This presentation is a preliminary version and not subject to your license

More information

SAP Standard for System Monitoring and Alerting

SAP Standard for System Monitoring and Alerting SAP Standard for E2E Solution Operations Document Version: 1.0 2014-12-12 SAP Solution Manager 7.1 Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These

More information

Solution Manager: What Is It & What Can It Do for Your Business? A Solution Overview written by Ken Asher, Sr. SAP Architect

Solution Manager: What Is It & What Can It Do for Your Business? A Solution Overview written by Ken Asher, Sr. SAP Architect Solution Manager: What Is It & What Can It Do for Your Business? A Solution Overview written by Ken Asher, Sr. SAP Architect Are you considering implementing additional functionality within Solution Manager?

More information

How-To Guide Test Automation Framework

How-To Guide Test Automation Framework SAP Solution Manager How-To Guide Test Automation Framework January 2011 Applicable Releases: SAP Solution Manager 7.1 Target groups: Test Engineers, Quality Experts, Technology Consultants, Application

More information

Introduction to Directory Services

Introduction to Directory Services Introduction to Directory Services Overview This document explains how AirWatch integrates with your organization's existing directory service such as Active Directory, Lotus Domino and Novell e-directory

More information

Kentico CMS 7.0 Intranet Administrator's Guide

Kentico CMS 7.0 Intranet Administrator's Guide Kentico CMS 7.0 Intranet Administrator's Guide 2 Kentico CMS 7.0 Intranet Administrator's Guide Table of Contents Introduction 5... 5 About this guide Getting started 7... 7 Installation... 11 Accessing

More information

Business Process and Interface Monitoring

Business Process and Interface Monitoring SAP Standard for E2E Solution Operations Document Version: 1.0 2015-02-12 SAP Solution Manager 7.1 Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These

More information

Business Process Configuration. Solution Management Application Lifecycle Management

Business Process Configuration. Solution Management Application Lifecycle Management Business Process Configuration Solution Management Application Lifecycle Management Disclaimer This presentation is a preliminary version and not subject to your license agreement or any other agreement

More information

DiskBoss. File & Disk Manager. Version 2.0. Dec 2011. Flexense Ltd. www.flexense.com info@flexense.com. File Integrity Monitor

DiskBoss. File & Disk Manager. Version 2.0. Dec 2011. Flexense Ltd. www.flexense.com info@flexense.com. File Integrity Monitor DiskBoss File & Disk Manager File Integrity Monitor Version 2.0 Dec 2011 www.flexense.com info@flexense.com 1 Product Overview DiskBoss is an automated, rule-based file and disk manager allowing one to

More information

Jet Data Manager 2012 User Guide

Jet Data Manager 2012 User Guide Jet Data Manager 2012 User Guide Welcome This documentation provides descriptions of the concepts and features of the Jet Data Manager and how to use with them. With the Jet Data Manager you can transform

More information

Archive Attender Version 3.5

Archive Attender Version 3.5 Archive Attender Version 3.5 Getting Started Guide Sherpa Software (800) 255-5155 www.sherpasoftware.com Page 1 Under the copyright laws, neither the documentation nor the software can be copied, photocopied,

More information

Migrating from SharePoint 2007 to SharePoint 2013. www.discovertechnologies.com

Migrating from SharePoint 2007 to SharePoint 2013. www.discovertechnologies.com Migrating from SharePoint 2007 to SharePoint 2013 www.discovertechnologies.com Migrating from SharePoint 2007 to SharePoint 2013 SharePoint 2007 provides a great collaboration platform, but as the business

More information

DiskPulse DISK CHANGE MONITOR

DiskPulse DISK CHANGE MONITOR DiskPulse DISK CHANGE MONITOR User Manual Version 7.9 Oct 2015 www.diskpulse.com info@flexense.com 1 1 DiskPulse Overview...3 2 DiskPulse Product Versions...5 3 Using Desktop Product Version...6 3.1 Product

More information

Protecting SQL Server Databases. 1997-2008 Software Pursuits, Inc.

Protecting SQL Server Databases. 1997-2008 Software Pursuits, Inc. Protecting SQL Server Databases 1997-2008 Table of Contents Introduction... 2 Overview of the Backup Process... 2 Configuring SQL Server to Perform Scheduled Backups... 3 Configuring SureSync Relation

More information

Content Management Implementation Guide 5.3 SP1

Content Management Implementation Guide 5.3 SP1 SDL Tridion R5 Content Management Implementation Guide 5.3 SP1 Read this document to implement and learn about the following Content Manager features: Publications Blueprint Publication structure Users

More information

Shavlik Patch for Microsoft System Center

Shavlik Patch for Microsoft System Center Shavlik Patch for Microsoft System Center User s Guide For use with Microsoft System Center Configuration Manager 2012 Copyright and Trademarks Copyright Copyright 2014 Shavlik. All rights reserved. This

More information

11/01/2016. ServiceNow Custom Application Development

11/01/2016. ServiceNow Custom Application Development 11/01/2016 Contents...3 Applications...3 Custom application demonstration... 3 Parts of an application...19 Contextual development environment... 41 Application management... 52 Studio... 59 Service Creator...80

More information

Microsoft Visual Studio Integration Guide

Microsoft Visual Studio Integration Guide Microsoft Visual Studio Integration Guide MKS provides a number of integrations for Integrated Development Environments (IDEs). IDE integrations allow you to access MKS Integrity s workflow and configuration

More information

DataPA OpenAnalytics End User Training

DataPA OpenAnalytics End User Training DataPA OpenAnalytics End User Training DataPA End User Training Lesson 1 Course Overview DataPA Chapter 1 Course Overview Introduction This course covers the skills required to use DataPA OpenAnalytics

More information

Integrating with BarTender Integration Builder

Integrating with BarTender Integration Builder Integrating with BarTender Integration Builder WHITE PAPER Contents Overview 3 Understanding BarTender's Native Integration Platform 4 Integration Builder 4 Administration Console 5 BarTender Integration

More information

Deploying the BIG-IP LTM with the Cacti Open Source Network Monitoring System

Deploying the BIG-IP LTM with the Cacti Open Source Network Monitoring System DEPLOYMENT GUIDE Deploying the BIG-IP LTM with the Cacti Open Source Network Monitoring System Version 1.0 Deploying F5 with Cacti Open Source Network Monitoring System Welcome to the F5 and Cacti deployment

More information

Working with the ERP Integration Service of EMC Documentum Process Services for SAP

Working with the ERP Integration Service of EMC Documentum Process Services for SAP Working with the ERP Integration Service of EMC Documentum Process Services for SAP Applied Technology Abstract EMC Documentum Process Services for SAP is a new product that integrates with EMC Documentum

More information

ThirtySix Software WRITE ONCE. APPROVE ONCE. USE EVERYWHERE. www.thirtysix.net SMARTDOCS 2014.1 SHAREPOINT CONFIGURATION GUIDE THIRTYSIX SOFTWARE

ThirtySix Software WRITE ONCE. APPROVE ONCE. USE EVERYWHERE. www.thirtysix.net SMARTDOCS 2014.1 SHAREPOINT CONFIGURATION GUIDE THIRTYSIX SOFTWARE ThirtySix Software WRITE ONCE. APPROVE ONCE. USE EVERYWHERE. www.thirtysix.net SMARTDOCS 2014.1 SHAREPOINT CONFIGURATION GUIDE THIRTYSIX SOFTWARE UPDATED MAY 2014 Table of Contents Table of Contents...

More information

SQL Server Mirroring. Introduction. Setting up the databases for Mirroring

SQL Server Mirroring. Introduction. Setting up the databases for Mirroring SQL Server Mirroring The purpose of this document is to describe in detail the process of configuring Secret Server and SQL Server 2008 for a high-availability environment using Mirroring. The contents

More information

DocAve 6 SharePoint Migrator

DocAve 6 SharePoint Migrator DocAve 6 SharePoint Migrator User Guide Service Pack 4, Cumulative Update 3 Revision D Issued September 2014 Table of Contents About SharePoint Migration... 5 Complementary Products... 5 Submitting Documentation

More information

CRM Migration Manager 3.1.1 for Microsoft Dynamics CRM. User Guide

CRM Migration Manager 3.1.1 for Microsoft Dynamics CRM. User Guide CRM Migration Manager 3.1.1 for Microsoft Dynamics CRM User Guide Revision D Issued July 2014 Table of Contents About CRM Migration Manager... 4 System Requirements... 5 Operating Systems... 5 Dynamics

More information

Business Process Redesign in SAP Solution Manager Application Lifecycle Management

Business Process Redesign in SAP Solution Manager Application Lifecycle Management Business Process Redesign in SAP Solution Manager Application Lifecycle Management TABLE OF CONTENTS 1 INTRODUCTION... 4 2 GENERAL EXPLANATION... 4 2.1 Projects and Solutions... 4 2.2 Template Project...

More information

Administration Guide for the System Center Cloud Services Process Pack

Administration Guide for the System Center Cloud Services Process Pack Administration Guide for the System Center Cloud Services Process Pack Microsoft Corporation Published: May 7, 2012 Author Kathy Vinatieri Applies To System Center Cloud Services Process Pack This document

More information

IBM Endpoint Manager Version 9.1. Patch Management for Red Hat Enterprise Linux User's Guide

IBM Endpoint Manager Version 9.1. Patch Management for Red Hat Enterprise Linux User's Guide IBM Endpoint Manager Version 9.1 Patch Management for Red Hat Enterprise Linux User's Guide IBM Endpoint Manager Version 9.1 Patch Management for Red Hat Enterprise Linux User's Guide Note Before using

More information

Availability Monitoring using Http Ping

Availability Monitoring using Http Ping Availability Monitoring using Http Ping With SAP Solution Manager 7.1 Introduction: This document describes how you can set up Http Ping metrics to monitor any URL. This is especially useful if you want

More information

Database Studio is the new tool to administrate SAP MaxDB database instances as of version 7.5.

Database Studio is the new tool to administrate SAP MaxDB database instances as of version 7.5. 1 2 3 4 Database Studio is the new tool to administrate SAP MaxDB database instances as of version 7.5. It replaces the previous tools Database Manager GUI and SQL Studio from SAP MaxDB version 7.7 onwards

More information

IBM Business Monitor V8.0 Global monitoring context lab

IBM Business Monitor V8.0 Global monitoring context lab Copyright IBM Corporation 2012 All rights reserved IBM BUSINESS MONITOR 8.0 LAB EXERCISE IBM Business Monitor V8.0 lab What this exercise is about... 2 Lab requirements... 2 What you should be able to

More information

User Manual. Version 3.12. connmove GmbH Version: 3.12. www.connmove.de Seite 1 von 33

User Manual. Version 3.12. connmove GmbH Version: 3.12. www.connmove.de Seite 1 von 33 User Manual Version 3.12 connmove GmbH Version: 3.12 www.connmove.de Seite 1 von 33 Table of Contents Introduction... 4 cmwatcher Blog... 4 System Requirements... 4 Architecture Recommendations... 5 Integration

More information

UNICORN 6.4. Administration and Technical Manual

UNICORN 6.4. Administration and Technical Manual UNICORN 6.4 Administration and Technical Manual Page intentionally left blank Table of Contents Table of Contents 1 Introduction... 1.1 Administrator functions overview... 1.2 Network terms and concepts...

More information

Chapter 3 Application Monitors

Chapter 3 Application Monitors Chapter 3 Application Monitors AppMetrics utilizes application monitors to organize data collection and analysis per application server. An application monitor is defined on the AppMetrics manager computer

More information

Taking Advantage of Active Directory Support in GroupWise 2014

Taking Advantage of Active Directory Support in GroupWise 2014 White Paper Collaboration Taking Advantage of Active Directory Support in GroupWise 2014 Flexibility and interoperability have always been hallmarks for Novell. That s why it should be no surprise that

More information

SAP Standard for Job Scheduling Management

SAP Standard for Job Scheduling Management SAP Standard for E2E Solution Operations Document Version: 1.0 2014-12-12 SAP Solution Manager 7.1 Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These

More information

Connector for Microsoft Dynamics Configuration Guide for Microsoft Dynamics SL

Connector for Microsoft Dynamics Configuration Guide for Microsoft Dynamics SL Microsoft Dynamics Connector for Microsoft Dynamics Configuration Guide for Microsoft Dynamics SL Revised August, 2012 Find updates to this documentation at the following location: http://www.microsoft.com/download/en/details.aspx?id=10381

More information

Database Administration

Database Administration Unified CCE, page 1 Historical Data, page 2 Tool, page 3 Database Sizing Estimator Tool, page 11 Administration & Data Server with Historical Data Server Setup, page 14 Database Size Monitoring, page 15

More information

NetWrix SQL Server Change Reporter

NetWrix SQL Server Change Reporter NetWrix SQL Server Change Reporter Version 2.2 Administrator Guide Contents NetWrix SQL Server Change Reporter Administrator Guide 1. INTRODUCTION... 3 1.1 KEY FEATURES... 3 1.2 LICENSING... 4 1.3 HOW

More information

UNICORN 7.0. Administration and Technical Manual

UNICORN 7.0. Administration and Technical Manual UNICORN 7.0 Administration and Technical Manual Page intentionally left blank Table of Contents Table of Contents 1 Introduction... 1.1 Administrator functions overview... 1.2 Network terms and concepts...

More information

How to Configure Integration between SAP ERP and SAP Cloud for Customer using SAP Process Integration

How to Configure Integration between SAP ERP and SAP Cloud for Customer using SAP Process Integration How to Configure Integration between SAP ERP and SAP Cloud for Customer using SAP Process Integration 1 How-To Guide Document Version: 1411 2014.12.15 How to Configure Integration between SAP ERP and SAP

More information

USERS MANUAL FOR OWL A DOCUMENT REPOSITORY SYSTEM

USERS MANUAL FOR OWL A DOCUMENT REPOSITORY SYSTEM USERS MANUAL FOR OWL A DOCUMENT REPOSITORY SYSTEM User Manual Table of Contents Introducing OWL...3 Starting to use Owl...4 The Logging in page...4 Using the browser...6 Folder structure...6 Title Bar...6

More information

Exclaimer Mail Archiver User Manual

Exclaimer Mail Archiver User Manual User Manual www.exclaimer.com Contents GETTING STARTED... 8 Mail Archiver Overview... 9 Exchange Journaling... 9 Archive Stores... 9 Archiving Policies... 10 Search... 10 Managing Archived Messages...

More information

Project management integrated into Outlook

Project management integrated into Outlook Project management integrated into Outlook InLoox PM 7.x off-line operation An InLoox Whitepaper Published: October 2011 Copyright: 2011 InLoox GmbH. You can find up-to-date information at http://www.inloox.com

More information

WHITEPAPER. Managing Design Changes in Enterprise SBM Installations

WHITEPAPER. Managing Design Changes in Enterprise SBM Installations WHITEPAPER Managing Design Changes in Enterprise SBM Installations By Tom Clement Serena Software, Inc. October 2013 Summary This document explains how to organize your SBM maintenance and development

More information

TANDBERG MANAGEMENT SUITE 10.0

TANDBERG MANAGEMENT SUITE 10.0 TANDBERG MANAGEMENT SUITE 10.0 Installation Manual Getting Started D12786 Rev.16 This document is not to be reproduced in whole or in part without permission in writing from: Contents INTRODUCTION 3 REQUIREMENTS

More information

Best Practice Manual Testing of E2E processes using SAP Solution Manager 7.1 - Test Option 1. Marcus Wefers, ALM Solution Management, AGS, SAP AG

Best Practice Manual Testing of E2E processes using SAP Solution Manager 7.1 - Test Option 1. Marcus Wefers, ALM Solution Management, AGS, SAP AG Best Practice Manual Testing of E2E processes using SAP Solution Manager 7.1 - Test Option 1 Marcus Wefers, ALM Solution Management, AGS, SAP AG Agenda 1. Approaches for manual testing of E2E Business

More information

ALM 271 From End-User Experience Monitoring to Management Dashboards and Reporting Stefan Lahr, SAP Active Global Support September, 2011

ALM 271 From End-User Experience Monitoring to Management Dashboards and Reporting Stefan Lahr, SAP Active Global Support September, 2011 ALM 271 From End-User Experience Monitoring to Management Dashboards and Reporting Stefan Lahr, SAP Active Global Support September, 2011 Disclaimer This presentation outlines our general product direction

More information

Data Consistency Management Overview January 2014. Customer

Data Consistency Management Overview January 2014. Customer Data Consistency Management Overview January 2014 Customer Agenda Motivation SAP Solution Manager as Tool for Data Consistency Management Transactional Correctness (TC) Guided Self Service Data Consistency

More information

Commander. The World's Leading Software for Label, Barcode, RFID & Card Printing

Commander. The World's Leading Software for Label, Barcode, RFID & Card Printing The World's Leading Software for Label, Barcode, RFID & Card Printing Commander Middleware for Automatically Printing in Response to User-Defined Events Contents Overview of How Commander Works 4 Triggers

More information

An Oracle White Paper June, 2014. Strategies for Scalable, Smarter Monitoring using Oracle Enterprise Manager Cloud Control 12c

An Oracle White Paper June, 2014. Strategies for Scalable, Smarter Monitoring using Oracle Enterprise Manager Cloud Control 12c An Oracle White Paper June, 2014 Strategies for Scalable, Smarter Monitoring using Oracle Enterprise Manager Cloud Control 12c Product Overview... 1 Introduction... 1 Laying the Groundwork for Monitoring...

More information

Sophos Mobile Control Administrator guide. Product version: 3

Sophos Mobile Control Administrator guide. Product version: 3 Sophos Mobile Control Administrator guide Product version: 3 Document date: January 2013 Contents 1 About Sophos Mobile Control...4 2 About the Sophos Mobile Control web console...7 3 Key steps for managing

More information

The presentation explains how to create and access the web services using the user interface. WebServices.ppt. Page 1 of 14

The presentation explains how to create and access the web services using the user interface. WebServices.ppt. Page 1 of 14 The presentation explains how to create and access the web services using the user interface. Page 1 of 14 The aim of this presentation is to familiarize you with the processes of creating and accessing

More information

SysPatrol - Server Security Monitor

SysPatrol - Server Security Monitor SysPatrol Server Security Monitor User Manual Version 2.2 Sep 2013 www.flexense.com www.syspatrol.com 1 Product Overview SysPatrol is a server security monitoring solution allowing one to monitor one or

More information

NS DISCOVER 4.0 ADMINISTRATOR S GUIDE. July, 2015. Version 4.0

NS DISCOVER 4.0 ADMINISTRATOR S GUIDE. July, 2015. Version 4.0 NS DISCOVER 4.0 ADMINISTRATOR S GUIDE July, 2015 Version 4.0 TABLE OF CONTENTS 1 General Information... 4 1.1 Objective... 4 1.2 New 4.0 Features Improvements... 4 1.3 Migrating from 3.x to 4.x... 5 2

More information

How to Configure Integration between SAP CRM and SAP Cloud for Customer using SAP Process Integration

How to Configure Integration between SAP CRM and SAP Cloud for Customer using SAP Process Integration How-To Guide Document Version: 1411 2014.12.15 How to Configure Integration between SAP CRM and SAP Cloud for Customer using SAP Process Integration How to Configure Integration between SAP CRM and SAP

More information

Installing and Configuring vcloud Connector

Installing and Configuring vcloud Connector Installing and Configuring vcloud Connector vcloud Connector 2.7.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new

More information

Application. 1.1 About This Tutorial. 1.1.1 Tutorial Requirements. 1.1.2 Provided Files

Application. 1.1 About This Tutorial. 1.1.1 Tutorial Requirements. 1.1.2 Provided Files About This Tutorial 1Creating an End-to-End HL7 Over MLLP Application 1.1 About This Tutorial 1.1.1 Tutorial Requirements 1.1.2 Provided Files This tutorial takes you through the steps of creating an end-to-end

More information

Overview Application Incident Management. David Birkenbach ALM Solution Management August 2011

Overview Application Incident Management. David Birkenbach ALM Solution Management August 2011 Overview Application Incident David Birkenbach ALM Solution August 2011 How the New SAP Solution Manager Supports Business & IT SAP Solution Manager 7.1 provides: Better coverage of the complete customer

More information

How to Configure Integration between SAP ERP and SAP Cloud for Customer using SAP Process Integration

How to Configure Integration between SAP ERP and SAP Cloud for Customer using SAP Process Integration How to Configure Integration between SAP ERP and SAP Cloud for Customer using SAP Process Integration 1 How-To Guide Document Version: 1502 2015.04.13 How to Configure Integration between SAP ERP and SAP

More information

PCVITA Express Migrator for SharePoint (File System) 2011. Table of Contents

PCVITA Express Migrator for SharePoint (File System) 2011. Table of Contents Table of Contents Chapter-1 ---------------------------------------------------------------------------- Page No (2) What is PCVITA Express Migrator for SharePoint (File System)? Migration Supported The

More information

INSTALLATION GUIDE Datapolis Process System v 4.2.0.4294

INSTALLATION GUIDE Datapolis Process System v 4.2.0.4294 Datapolis.com, ul Wiktorska 63, 02-587 Warsaw, Poland tel. (+48 22) 398-37-53; fax. (+ 48 22) 398-37-93, office@datapolis.com INSTALLATION GUIDE Datapolis Process System v 4.2.0.4294 Last modification

More information

SAP Standard for Remote Supportability

SAP Standard for Remote Supportability SAP Standard for E2E Solution Operations Document Version: 1.0 2014-12-12 SAP Solution Manager 7.1 Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These

More information

Back Up and Restore the Project Center and Info Exchange Servers. Newforma Project Center Server

Back Up and Restore the Project Center and Info Exchange Servers. Newforma Project Center Server Back Up and Restore the Project Center and Info Exchange Servers This document outlines backup and restore procedures for Newforma Project Center Server and Newforma Info Exchange Server. This document

More information

Chapter 25 Backup and Restore

Chapter 25 Backup and Restore System 800xA Training Chapter 25 Backup and Restore TABLE OF CONTENTS Chapter 25 Backup and Restore... 1 25.1 General Information... 2 25.1.1 Objectives... 2 25.1.2 Legend... 2 25.1.3 Reference Documentation...

More information

MultiSite Manager. User Guide

MultiSite Manager. User Guide MultiSite Manager User Guide Contents 1. Getting Started... 2 Opening the MultiSite Manager... 2 Navigating MultiSite Manager... 2 2. The All Sites tabs... 3 All Sites... 3 Reports... 4 Licenses... 5 3.

More information

Network Shutdown Module V3 Extension of the User Manual for IBM BladeCenter architecture

Network Shutdown Module V3 Extension of the User Manual for IBM BladeCenter architecture Network Shutdown Module V3 Extension of the User Manual for IBM BladeCenter architecture Network Shutdown Module V3 Extension for IBM BladeCenter Architecture- 34 022 272 XU / AC Contents 1 Introduction...3

More information

RingStor User Manual. Version 2.1 Last Update on September 17th, 2015. RingStor, Inc. 197 Route 18 South, Ste 3000 East Brunswick, NJ 08816.

RingStor User Manual. Version 2.1 Last Update on September 17th, 2015. RingStor, Inc. 197 Route 18 South, Ste 3000 East Brunswick, NJ 08816. RingStor User Manual Version 2.1 Last Update on September 17th, 2015 RingStor, Inc. 197 Route 18 South, Ste 3000 East Brunswick, NJ 08816 Page 1 Table of Contents 1 Overview... 5 1.1 RingStor Data Protection...

More information

NSi Mobile Installation Guide. Version 6.2

NSi Mobile Installation Guide. Version 6.2 NSi Mobile Installation Guide Version 6.2 Revision History Version Date 1.0 October 2, 2012 2.0 September 18, 2013 2 CONTENTS TABLE OF CONTENTS PREFACE... 5 Purpose of this Document... 5 Version Compatibility...

More information

Clustering ExtremeZ-IP 4.1

Clustering ExtremeZ-IP 4.1 Clustering ExtremeZ-IP 4.1 Installing and Configuring ExtremeZ-IP 4.x on a Cluster Version: 1.3 Date: 10/11/05 Product Version: 4.1 Introduction This document provides instructions and background information

More information

Setup Guide for AD FS 3.0 on the Apprenda Platform

Setup Guide for AD FS 3.0 on the Apprenda Platform Setup Guide for AD FS 3.0 on the Apprenda Platform Last Updated for Apprenda 6.0.3 The Apprenda Platform leverages Active Directory Federation Services (AD FS) to support identity federation. AD FS and

More information

IT Service Management in SAP Solution Manager

IT Service Management in SAP Solution Manager Nathan Williams IT Service Management in SAP Solution Manager Bonn Boston Contents at a Glance PART I Introduction 1 An Overview of IT Service Management... 29 2 User Interfaces for SAP ITSM Functions

More information

Parallels Containers for Windows 6.0

Parallels Containers for Windows 6.0 Parallels Containers for Windows 6.0 Upgrade Guide June 11, 2014 Copyright 1999-2014 Parallels IP Holdings GmbH and its affiliates. All rights reserved. Parallels IP Holdings GmbH Vordergasse 59 8200 Schaffhausen

More information

SafeGuard Enterprise upgrade guide. Product version: 6.1

SafeGuard Enterprise upgrade guide. Product version: 6.1 SafeGuard Enterprise upgrade guide Product version: 6.1 Document date: February 2014 Contents 1 About this guide...3 2 Check the system requirements...4 3 Download installers...5 4 About upgrading...6

More information

OutSystems Platform 9.0 SEO Friendly URLs

OutSystems Platform 9.0 SEO Friendly URLs TECHNICAL NOTE OutSystems Platform 9.0 SEO Friendly URLs When your Web applications URLs become too complex, they have impact on end-users reading and most of all fall in rankings of search engines. To

More information

Microsoft Outlook Quick Reference Sheet

Microsoft Outlook Quick Reference Sheet Microsoft Outlook is an incredibly powerful e-mail and personal information management application. Its features and capabilities are extensive. Refer to this handout whenever you require quick reminders

More information

GRAVITYZONE HERE. Deployment Guide VLE Environment

GRAVITYZONE HERE. Deployment Guide VLE Environment GRAVITYZONE HERE Deployment Guide VLE Environment LEGAL NOTICE All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including

More information

VMware Mirage Web Manager Guide

VMware Mirage Web Manager Guide Mirage 5.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document,

More information

Administration GUIDE. Exchange Database idataagent. Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 233

Administration GUIDE. Exchange Database idataagent. Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 233 Administration GUIDE Exchange Database idataagent Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 233 User Guide - Exchange Database idataagent Table of Contents Overview Introduction Key Features

More information

Deploying System Center 2012 R2 Configuration Manager

Deploying System Center 2012 R2 Configuration Manager Deploying System Center 2012 R2 Configuration Manager This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

More information

PCVITA Express Migrator for SharePoint(Exchange Public Folder) 2011. Table of Contents

PCVITA Express Migrator for SharePoint(Exchange Public Folder) 2011. Table of Contents Table of Contents Chapter-1 ------------------------------------------------------------- Page No (2) What is Express Migrator for Exchange Public Folder to SharePoint? Migration Supported The Prominent

More information

Administration guide. Host software WinCCU Installation. Complete gas volume and energy data management

Administration guide. Host software WinCCU Installation. Complete gas volume and energy data management Administration guide Host software WinCCU Installation Complete gas volume and energy data management Contents 1 Introduction... 1 Safety first... 1 Warning... 1 Typographic conventions... 1 Product versioning...

More information

McAfee VirusScan and epolicy Orchestrator Administration Course

McAfee VirusScan and epolicy Orchestrator Administration Course McAfee VirusScan and epolicy Orchestrator Administration Course Intel Security Education Services Administration Course Training The McAfee VirusScan and epolicy Orchestrator Administration course from

More information

Sophos Mobile Control Startup guide. Product version: 3

Sophos Mobile Control Startup guide. Product version: 3 Sophos Mobile Control Startup guide Product version: 3 Document date: January 2013 Contents 1 About this guide...3 2 What are the key steps?...5 3 Log in as a super administrator...6 4 Activate Sophos

More information

Learn more about BI Monitoring

Learn more about BI Monitoring SAP BI Monitoring In todays BI scenarios it is critical to ensure that end users retrieve up-to-date information from the BI solution. This requires sufficient performance and availability of all involved

More information

HDFS Users Guide. Table of contents

HDFS Users Guide. Table of contents Table of contents 1 Purpose...2 2 Overview...2 3 Prerequisites...3 4 Web Interface...3 5 Shell Commands... 3 5.1 DFSAdmin Command...4 6 Secondary NameNode...4 7 Checkpoint Node...5 8 Backup Node...6 9

More information

The Nuts and Bolts of Autodesk Vault Replication Setup

The Nuts and Bolts of Autodesk Vault Replication Setup The Nuts and Bolts of Autodesk Vault Replication Setup James McMullen Autodesk, Inc PL4700-V Has your company decided to move toward a replicated Autodesk Vault software environment? Does your company

More information

Bitrix Site Manager ASP.NET. Installation Guide

Bitrix Site Manager ASP.NET. Installation Guide Bitrix Site Manager ASP.NET Installation Guide Contents Introduction... 4 Chapter 1. Checking for IIS Installation... 5 Chapter 2. Using An Archive File to Install Bitrix Site Manager ASP.NET... 7 Preliminary

More information

ivend Retail Installation Guide Version: 6

ivend Retail Installation Guide Version: 6 Version: 6 July 2013 Table of Contents Typographic Conventions... 4 Purpose... 5 Target Audience... 5 Hardware and Software Requirements... 5 Installation Preparations... 5 ivend Components... 5 Enterprise

More information

Manual. CollabNet Subversion Connector to HP Quality Center. Version 1.2

Manual. CollabNet Subversion Connector to HP Quality Center. Version 1.2 Manual CollabNet Subversion Connector to HP Quality Center Version 1.2 A BOUT THE CONNECTOR About the Connector The CollabNet Subversion Connector to HP Quality Center enables Quality Center users to

More information

BusinessObjects Enterprise XI Release 2 Publishing Guide

BusinessObjects Enterprise XI Release 2 Publishing Guide BusinessObjects Enterprise XI Release 2 Publishing Guide BusinessObjects Enterprise XI Release 2 Publishing Guide Patents Trademarks Copyright Third-party contributors Business Objects owns the following

More information

exchange@pam MS Outlook AddIn version 3.6

exchange@pam MS Outlook AddIn version 3.6 User s Manual for exchange@pam MS Outlook AddIn version 3.6 All Rights Reserved. Including all rights concerning reproduction, copying or any other use or transmission of this document and its contents

More information

Citrix Systems, Inc.

Citrix Systems, Inc. Citrix Password Manager Quick Deployment Guide Install and Use Password Manager on Presentation Server in Under Two Hours Citrix Systems, Inc. Notice The information in this publication is subject to change

More information