Professional Documents
Culture Documents
2008 SAP AG
Page 1 of 52
2008 SAP AG
Page 2 of 52
1 2 3
3.1 3.2
MANAGEMENT SUMMARY .................................................................... 4 SAP STANDARDS FOR E2E SOLUTION OPERATIONS....................... 5 TECHNICAL REQUIREMENTS OF PROVIDING DOCUMENTATION.... 8
Location and Format of Documentation Content .......................................................... 8 Documentation Language.................................................................................................... 8
4
4.1
4.2 System and Application Landscape................................................................................ 11 4.2.1 Documenting usage of 3rd-party software ................................................................... 12 4.3 4.4 Physical System Landscape ............................................................................................. 13 Solution Definition ............................................................................................................... 14
4.5 Business Scenario and Business Process Documentation...................................... 15 4.5.1 Starting with an SAP delivered business scenario .................................................... 16 4.5.2 Define missing business scenarios, processes and steps ....................................... 17 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 Application Components.................................................................................................... 20 Interface Documentation .................................................................................................... 21 Documentation of Background Jobs .............................................................................. 25 Transactions and User Entry Points ............................................................................... 28 Performance and Volume KPIs......................................................................................... 29 Development object list for Custom Development or Customizing Objects ........ 30 Functional Documentation / Business Background ................................................... 31 Integration and Volume Test Plan Documentation...................................................... 32 Application Operations Guide........................................................................................... 33
5
5.1 5.2 5.3
APPENDIX.............................................................................................. 34
Template: Functional Documentation............................................................................. 34 Template: Test Plan Documentation ............................................................................... 37 Template: Application Operations Guide....................................................................... 49 Solution Documentation for Custom Development Version: 2.0 Page 3 of 52
2008 SAP AG
2008 SAP AG
Page 4 of 52
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. 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 sup 2008 SAP AG Solution Documentation for Custom Development Version: 2.0 Page 5 of 52
2008 SAP AG
Out of this list, this white paper describes the standard Solution Documentation for Custom Development.
2008 SAP AG
Page 7 of 52
2008 SAP AG
Page 8 of 52
Figure 4.1: Set Minimum Documentation Defaults Select a project type. There are multiple project types. The type Implementation Project works fine for documentation of custom code. The corresponding 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 Modification Justification Check service. If you have a high level project description you should upload this into the project description (optional). Minimal required information (see Figure 4.2): Solution Documentation for Custom Development Version: 2.0
2008 SAP AG
Page 9 of 52
Figure 4.2: Project Administration - Header Data Screen 1. Provide a meaningful title to the project. Latest when a project is moving from the implementation phase to the productive phase, it shall be linked to a Solution that should consist of all business scenarios that are running together in a common system landscape. If the Solution is not yet defined when the project is started, you need to leave this field initially blank and fill it later as soon as the Solution is defined. After the project is finalized, you should also copy the project into the Solution. 2. In the Project Management section, select whether the project is led by your organization (customer), by SAP or by a consulting partner (resp. VAR/CBS). Also add a responsible person for this project within your organization (customer) and if the project is not led by your organization also the responsible person for this project within Solution Documentation for Custom Development Version: 2.0
2008 SAP AG
Page 10 of 52
2008 SAP AG
Page 11 of 52
Figure 4.4: System Landscape - Create Custom Product Screen 2008 SAP AG Solution Documentation for Custom Development Version: 2.0 Page 12 of 52
Figure 4.5: System Landscape - Maintain Custom Software Components 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).
Figure 4.6: System Landscape Maintenance - System Creation Wizard Non-SAP systems have to be defined manually the system ID can be chosen freely but needs to be unique in your system landscape. If an installation number does not exist, you can enter any number. .
2008 SAP AG
Page 14 of 52
Figure 4.7: Project Header Data - Mapping to a Solution You can create a new solution in the Solutions view of the SAP Solution Manager Administration work center. Select New and enter the required data (see Figure 4.8).
Figure 4.9: Business Process Repository - Selection of Business Scenarios / Processes After you have selected the matching business scenario(s) and saved them, you get the complete list of associated SAP standard business process and have to delete those that you do not touch within this project. 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.
2008 SAP AG
Page 16 of 52
2008 SAP AG
Page 17 of 52
Figure 4.11: Scenario, process, step, transaction Adding a new business scenario can be simply done 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. To add a business process, you first select the Business Processes sub-node for the scenario where this process belongs to and 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. For adding a business process step, you need to enter a reasonable name into the Step Name column at the Structure tab of the business process. A process step always needs also a logical component to be assigned. You need to have the logical components defined beforehand as explained in section 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. The scope of a business process step shall be the activity that executes a single logical step within the business logic. It is not necessarily the execution 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). Each business process step has to be classified into one of the following categories by setting the matching values in the attributes tab of the business process step. The attributes are maintained via the structure tab of the respective business process (see Figure 4.12). See Table 1 for the meaning of each category. A process step may belong to multiple categories (if it contains multiple coding parts falling into different categories).
2008 SAP AG
Page 18 of 52
Figure 4.12: Classify Business Process Step via Attribute You shall change the step classification from SAP standard to SAP with enhancement whenever you modify the behavior of an SAP business process significantly via implementing a standard enhancement hook (e.g. business add-in).. For modifications of SAP business process steps via real modification of original SAP code, you shall change the step classification from SAP standard to SAP with modification. If the main business activity originally performed by this step has also changed, this shall be reflected in a corresponding adjustment of the step name. In cases where you do not find a well matching original SAP business processes within the BPR, you need to create a completely new business scenario resp. business processes from scratch. Typically, these business processes will also be integrated with the SAP standard. The minimum information required is at least the documentation of that part of the business processes that are realized by the custom code or by SAP modifications as well as all business process steps that are directly linked via standard SAP interfaces. Ideally, you should document the whole business processes where the custom development is integrated. As you will enter both types (customer and SAP steps) manually in this case, it is important to 2008 SAP AG Solution Documentation for Custom Development Version: 2.0 Page 19 of 52
Meaning Business step is fully realized with SAP standard code. Used also in SAP standard business processes. Business step is realized with SAP standard code with implemented custom enhancement (e.g. BADI implementation). Business step is realized with SAP standard code that was modified (i.e. original SAP program code in SAP namespace was changed). Business step is realized by custom code within custom namespace.
Custom development
Table 1: Classification Types of Business Process Steps It is important to understand which of the business processes are essential for your key businesses to work these processes are called 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 setting the attribute Core to them. This can be done via the attribute maintenance of the business process (see Figure 4.13).
2008 SAP AG
Page 20 of 52
2008 SAP AG
Page 21 of 52
Figure 4.15: Interface Scenario Definition After you have saved the interface scenario definition(s), you have to add the list of single interfaces per scenario. This is done within the Structure tab of the respective interface scenario node (see Figure 4.16). You have to define a meaningful name in the Interface column and enter sending and receiving logical components (these may also be identical, e.g. if the custom code calls standard functionality by invoking a BAPI on the same logical component), the technology (selected from the values in the drop-down box), as well as the Type. The Type is synchronous when the sender waits until the receiver has consumed the sent data or asynchronous if the message is just put on a queue for later processing and the sender immediately continues independent of the receivers behavior.
Figure 4.16: Adding an Interface to an Interface Scenario In addition to that, you shall provide details on each interface using the attributes button. Information is required in the Technical Attributes tab and the Document Volume tab. In the Technical Attributes tab at least the Technical object name and the business object name are required as they allow to technically identify the interface within the system. See Figure 4.17 as an example.
2008 SAP AG
Page 22 of 52
Figure 4.17: Enter Technical Interface Name You are encouraged to enter further technical attributes. For the Data Volume tab you shall at least enter estimated average and maximum expected document volumes for one of the offered time frames (hour, day, week, and month). See Figure 4.18 as an example. The more details you are able to provide the better. Required response time shall be entered if your business requires that the sender proceeds within a given time frame (only for synchronous interfaces) or that the receiver is able to start processing within a certain time frame. Entering no required response time means that it is sufficient if the system can handle the total document volume over time without constantly increasing backlog.
2008 SAP AG
Page 23 of 52
Figure 4.18: Enter Interface Document Volume In order to document the usage of the interfaces within the business processes, you have to assign them to the matching connections between business process steps in the respective business process graphic. Without assigning an interface to the connecting line of two business process steps, you just define their logical sequence. For assigning a previously defined interface enter the Graphic tab at the respective business process node and right click on the connection line of the two business process steps you want to add the interface to. In case there is no connection defined yet you need to create one first. After selecting Assign Interface you get a selection of all interface definitions within your project that potentially match. This means that the source and destination logical systems and the interface type must match (see Figure 4.19 as an example).
2008 SAP AG
Page 24 of 52
2008 SAP AG
Page 25 of 52
Figure 4.20: Create New Job Documentation If you create new job documentation, a browser window for the job documentation UI is opened (see Figure 21). The minimum information that shall be entered is the job name (as it can be found in the job scheduler). If you already know that the scheduler will be Redwood Chronacle or the ABAP job scheduler (BC-XBP), you can choose the corresponding scheduler. Otherwise, choose BC-XBP as scheduler. You need to define at least one job step via Add. In the job step details, you have to enter a text description of the executed program, the program type (ABAP report, any external program, 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). If a variant is used, enter the name of the job variant as well and select whether the job runs client specific or not.
2008 SAP AG
Page 26 of 52
Figure 21: Adding Job Step Details In case of a multi-step job, you may add more steps as needed. If possible, also 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 the job aborts, what if it did not start, or if it finishes too late) via the respective tabs,. 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 section 4.12 Functional Documentation / Business Background). 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.
2008 SAP AG
Page 27 of 52
Figure 4.22: Documentation of Transactions / User Entry Points 2008 SAP AG Solution Documentation for Custom Development Version: 2.0 Page 28 of 52
2008 SAP AG
Page 29 of 52
2008 SAP AG
Page 30 of 52
2008 SAP AG
Page 31 of 52
2008 SAP AG
Page 32 of 52
This information shall be documented using the template Application Operations Guide (available in the attachment of this document and for download in the media library for E2E Solution Operations standards at http://service.sap.com/supportstandards) via the same method as described in section 4.12.
2008 SAP AG
Page 33 of 52
5.1
About this Template You use this template to document the business background that led to this custom development. Explain what are the functional business gaps closed by this development. Describe on business process level how this development works logically. The explanation shall refer to the business process and step names that were also used within the business process structures that you have documented within the project in Solution Manager. A description of the functionality is required for all business process steps that are of type Custom development, SAP with enhancement, or SAP modification. For SAP enhancements the implemented SAP enhancement objects (e.g. BADIs) shall be listed. For SAP modifications it shall be explicitly explained which modification free alternatives have been evaluated, why the modification option was chosen in the end and who on customer side has officially signed off the modification. Additionally it has to be documented which preconditions (e.g. certain SAP releases or functionalities) or assumptions are made that have to be met for the developed functionality to work.
Glossary
Here you may provide a glossary for the abbreviations that you use within this document or within the business process / step names (e.g. PR = purchase requisition).
Term
Definition
Explain why this custom development was needed. Which functionality was missing in the existing SAP software?
2008 SAP AG
Page 34 of 52
Explain how the functionality is realized by the custom code on a logical level. The documentation should be structured by business processes using the same names as in the business process structure within the project in SAP Solution Manager. The process step names from the project documentation should be also used within the functional documentation to have a clear relation. You may also export the business process graphics out of SAP Solution Manager and include them as a picture in here.
3.1
Provide the documentation for this business process. Describe step by step for each nonSAP standard step what it does and how it is triggered (user interaction, synchronous/asynchronous communication of predecessor step, background job) respectively how it interacts with its successor(s).
Alternatives evaluated: Explain briefly the alternatives you have taken into account.
Final reason for choosing the modification alternative: Why did you finally decide to implement this modification instead of any other alternative?
2008 SAP AG
Page 35 of 52
3.2
Preconditions / Assumptions
Explain what is required for this development to work (e.g. expected releases or functionalities of SAP products).
2008 SAP AG
Page 36 of 52
About this Template You use this template to document how the testing of this project will be organized. The document is organized as a type of questionnaire. This document contains form elements to simplify the data entry but it requires being in protected mode in order to enable the form entry.
klaus.mustermann@xyz.com
Roles
Role / Area Executive Sponsor Test Project Manager(s) / Test Coordinator(s) Application implementation / operation Technical implementation / operation Business Process Owner(s) Key / Power User(s) Test Case Development Responsible Company Phone e-Mail
2008 SAP AG
Page 37 of 52
Productive system
SID System role Release
Action: In this table please enter the information about each system in the transport landscape. This includes the SID of the upstream 2 - and downstream 3 -systems for each system in the landscape. As soon as the table is completed, it describes the whole transport landscape and the transport routes in the landscape. Example: the table below describes the classical 3-systems landscape DEV 4 -> QAS 5 -> 6 PRD . Here PRD is a downstream-system for QAS and DEV is upstream-system for QAS:
Role in the transport landscape Development system Quality Assurance system Productive system
SID System ID. The name for your SAP system which is unique throughout your organization and must consist of exactly three alphanumeric characters where only uppercase letters are allowed and the first character is a letter (not a digit) 2 Upstream-system means a system where the transports come from 3 Downstream-system means a system where the transports go to 4 DEV development system in a transport landscape 5 QAS quality assurance system in a transport landscape 6 PRD productive system in a transport landscape
2008 SAP AG
Page 38 of 52
Roles, Responsibilities and Workflow Action: Please describe in the column Project, Name and Role who is responsible for
each particular step in the change management and the corresponding role. If they are different for several projects please enter the information for each project in one field using a project short name as a prefix. Example:
Step / Function Perform functional test in DEV Project, Name and Role PSAP_R3 - J.Smith, Test Manager; SCM_SAP - S.John, Test Manager
An exception to the standard transport workflow could be necessary to allow fast reaction to urgent problems in the productive system. Action: Please answer the question:
2008 SAP AG
Page 39 of 52
End User Key User Business Process Owner System Owner (Administrator) Development <Other> Key User Business Process Owner System Owner (Administrator) Development Manager <Other>
Change request Action: Please mark the appropriate field if there is any standard change request form
in use in the company and if there is a change request database storing the requests, which are already processed.
Change Request Form and Database Questions Change request form available? Change request database available? Answers Yes No Yes No
Current Test Strategy Activities distribution Action: Please use the tables below for each test type to describe how the test activities are assigned to organizational units in the company. SAP is interested in the following test types: Unit Test 7 , User Acceptance Test 8 , Customer Development Test 9 , Integration Test 10 ,
Unit Test the lowest level of testing where the program or transaction is tested and evaluated for errors
2008 SAP AG
Page 40 of 52
and Technical System Test 12 . For each activity in each table, please mark the appropriate organizational units (one or more) that are responsible for this particular activity. If there are any comments or additions regarding activities distribution please use the field under the table. In each table for each activity mark at least one responsible organizational unit.
Unit Test Who performs an activity? Every Business Department on their own Central Test organization in each branch Central Test organization corporate wide Central Project IT de- team partment <Other>
11
Activities
to decide what needs to be tested to create test case descriptions to organize testing to execute test to monitor test to evaluate test results
User Acceptance Test represents end-to-end testing from the business perspective. The purpose of that is to prove that initial business requirements were implemented exactly and in accordance to specifications made before 9 Customer Development Test mixture of Unit Test and Integration Test with scope limited to the customers own development 10 Integration Test is accomplished through the execution of predefined business flows, or scenarios, that emulate how the system will run your business. Integration Test starts with the testing of the crossfunctional integration points and ends with the end-to-end testing of critical business processes 11 Regression Test test of critical business processes after a change to ensure that a) any problem has been fixed and that no other previously working functionality has been harmed as a result of the changes and/or b) that newly added features working as designed and have not created any unexpected side effects 12 Technical System Test test aimed to verify the production system environment from a technical standpoint, e.g. to test if the system can be started / stopped properly, if the basis technical infrastructure is working fine and the whole system in conjunction with database and operating system performs well from technical point of view. Among this the following technical tests are usually part of Technical System Test: backup and recovery, system administration, printing and faxing, failure scenarios, disaster recovery
2008 SAP AG
Page 41 of 52
Test Scope
Change type Possible methods projects regular maintenance hot fix process
General regression testing of all core business processes Analysis of changed / new objects and affected application area Evaluation of customizing settings to identfy which processes are configured and therefore most likely used and potentially affected by changes Evaluation of load profile (e.g. EWA 13 , ST14, RBE 14 , etc.) to find the business processes with a high load (meaning that such processes could also be most critical for everyday work) Only new functionality will be tested, usually no Regression Testing Others: <Please enter an additional method here if there is any>
EWA Early Watch Alert RBE - Reverse Business Engineer - a tool used for process-oriented analysis and continual optimization of SAP production systems. Using data from production systems it is possible to analyze how functions in the SAP System are used and identify potential for improvement
14
13
2008 SAP AG
Page 42 of 52
2008 SAP AG
Page 43 of 52
Test Case description Action: Please use the table below to specify what information is included in the standard test case description adopted to use in the company. Information in Test Case description
Information Test Case ID (unique identfier) Name of Project Name of Business Process Owner of Test Case Test Type (e.g. Unit, Integration, Regression) Test System Client Detailed description of preparation activities Detailed description of test procedure Check / Expected Test Results Only for Integration Testing: dependencies on other test cases (predecessor and successor) <Please enter an additional option here if there is any> Available Remarks <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here>
2008 SAP AG
Page 44 of 52
Test KPIs
15
Action: Please mark in the table below what kind of measurements via predefined KPIs you have regarding reliability of the tests.
Test KPIs
Possible measurement General Stability Availability / unplanned downtime Performance No. of short dumps No. of update-errors No. of trouble tickets (per component) Interface throughput <Please enter additional measurementS if there are any> Yes No Remark
<Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here>
15
KPI - key performance indicator - a measurement or metric for evaluating a company's business strategy, performance, or technology. KPI express abstract company objectives in financial or physical units for comparative purposes
2008 SAP AG
Page 45 of 52
Action: Please describe what methods you use to manage the test data (to create it, to store it, to update it, etc.) for testing. Test Data Management
Possible method Microsoft Office Excel spreadsheets Local or central test data databases Paper Automated Test Tools Test data is not managed centrally and is up to a tester <Please enter an additional method if there is any> Yes No Remarks <Please enter your comment here> What kind of databases? <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here>
2008 SAP AG
Page 46 of 52
2008 SAP AG
Page 47 of 52
Tools
Action: Please answer the questions below. Tools
Question Do you use CATT
16
Yes / eCATT
17
No Remark <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here> <Please enter your comment here>
for testing?
Are there any 3rd party tools involved in your current test approach? Are there any tools used for assignment of testers? Are there any tools used for execution of tests and documentation of results? Are there any tools used to follow-up in case of error? Are there any tools used to manage test data?
16 CATT -Computer Aided Test Tool - an SAP tool enabling you to combine and automate business processes as repeatable test procedures 17 eCATT - extended CATT - a successor of SAP CATT which provides more flexibility and functionality. Delivered starting with the basis release 6.20 of the SAP Web AS
2008 SAP AG
Page 48 of 52
About this Template You use this template to document what needs to be known in order to smoothly operate this custom developed component. The major topics to be described are: monitoring, administration, software change management, high availability and troubleshooting. It describes which tasks to be executed and which tools to be used. This document does not replace the Operations Handbook in which the customer respectively the operations organization has documented the concrete tasks, involved parties and interaction procedures. It is rather the basis for defining the Operations Handbook.
Monitoring
Monitoring is the task of retrieving information on the status of a certain component, business process or process step that is relevant for the smooth functionality of your implemented business processes. This section shall be used to describe all tasks and tools that are required to find out about any critical situation that indicates an existing or arising disturbance or failure of an implemented business process.
1.1
Alert Monitoring
Describe here whether integration is available into alert monitoring tools (e.g. SAP CCMS) and which alerts will be propagated. Explain which alerts have to be checked and what is there meaning to the business. Also provide recommendations on thresholds to be defined.
1.2
Error Logs
Document which error logs are used by your components to report error situations and how to filter on them (e.g. application log object names or development locations or error messages). You should also provide a list of all critical error messages with typical reasons and corrective measures.
1.3
Workload Monitoring
Document how the workload produced by the custom development can be identified and measured. For ABAP based components this may be done via the default ABAP workload monitor by providing the filter information to identify the custom components (e.g. namespace prefixes).
1.4
Interface Monitoring
For all interfaces that your custom development components are using document how to monitor it for errors, throughput, delays, queues. If you are using SAP standard interface technologies you just have to explain how to filter for your interfaces within the SAP standard monitors. If possible, explain also if possible how to distinguish the load from your components from others using the same interface (e.g. user names, destinations used).
2008 SAP AG
Page 49 of 52
List all background jobs that your application uses and where to find them. Explain how to identify a successful job run and what to do if a job run has failed (e.g. normal restart, restart with different variant, and separate repair activity). Note that this information can be also provided in the background job documentation within SAP Solution Manager.
This section shall document the tasks required for an administrator. There are regular tasks like starting/stopping, backup, user creation as well as exceptional tasks like adaptation for additional load.
2.1
If your components have to be started separately, explain how to do that and which start and stop sequences have to be followed.
2.2
Technical Configuration
2.3
Which components need to be backed up? Are certain backup sequences or preconditions (e.g. only offline backup) to be met? Explain which components hold business data and what needs to be checked / synched after an incomplete restore.
2.4
Periodic Tasks
Which tasks have to be performed periodically and at which frequency? Besides the background jobs of your application this can be also e.g. manual reorganization or archiving tasks.
2.5
User Management
Explain which system users with which capabilities (e.g. permissions, password not allowed to be changed) are required and where they are maintained. Explain how end users have to be maintained and which permissions are needed for which business functionality.
2.6
Explain how to adapt for higher user or document volume. This includes setting up parallel instances as well as according configuration of the application, interfaces and jobs. For load balancing, describe how users or document processing can be distributed over multiple resources (e.g. instances).
2.7
High Availability
Explain how to setup the landscape for high availability (i.e. without single point of failures for any core business process step). You may refer to available technical HA solutions for technology components but typically it is also required to setup the technical application configuration accordingly. Solution Documentation for Custom Development Version: 2.0
2008 SAP AG
Page 50 of 52
Troubleshooting
Explain which typical problem types exist and how to troubleshoot them (e.g. via a flow chart). Explain which tools to use for troubleshooting (e.g. error logs, perform and analyze traces). Explain which application component to be used to report problems in which area.
2008 SAP AG
Page 51 of 52
2008 SAP AG
Page 52 of 52