You are on page 1of 56

Operations Guide SAP BusinessObjects Global Trade Services 10.

0 Operations Guide
Target Audience ejd~ Technical Consultants ejd~ System Administrators ejd~ Solution Consultants ejd~ Business Process Owner ejd~ Support Specialist

PUBLIC ejdr"/Kg<G&{([u<]P(3wbMb49CTmb

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disclaimer

Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way.

2/56

PUBLIC

2010-12-13

Typographic Conventions

Example
<Example>

Description

Example Example Example


Example

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 5 Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. 5 Cross-references to other documentation or published works 5 Output on the screen following a user action, for example, messages 5 Source code or syntax quoted directly from a program 5 File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

2010-12-13

PUBLIC

3/56

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/swdc SAP Installations and Upgrades Installations and Upgrades - Entry by Application Group SAP Solutions for Governance, Risk and Compliance SAP Global Trade Services <Release> Installation and Upgrade . The following table provides an overview of the most important document changes.
Version Date Description

1.0

2010-12-13

Initial Version

4/56

PUBLIC

2010-12-13

Table of Contents

Chapter 1 1.1 1.2 Chapter 2 2.1 2.2 Chapter 3 3.1 3.1.1 3.1.2 3.1.3 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.3 Chapter 4 Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.6.1

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Global Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Scenario/Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Monitoring of SAP BusinessObjects Global Trade Services . . . . . . . . . . . Alert Monitoring with CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central System Monitoring Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCMS Monitoring Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . Component-Specific Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detailed Monitoring and Tools for Problem and Performance Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workload Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Growth and Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific Problem Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 14 15 16 16 21 21 23 24 24 25 26

Logging On and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Management of SAP Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 31 31 32 33 34 35 35

2010-12-13

PUBLIC

5/56

5.6.2 5.7 5.8 5.9 Chapter 6 Chapter 7 7.1 7.2 7.3 7.4 7.5 Chapter 8 Chapter 9 9.1 9.2 9.3 9.3.1 9.3.2 9.3.3 9.3.4 9.3.5 Chapter A A.1 A.1.1 A.1.2 Chapter B B.1

Required Manual Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35 36 37 37

High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Development Requests and Development Release Management . . . . . . . . . . . Quality Management and Test Management . . . . . . . . . . . . . . . . . . . . . . . . . . Support Packages and Patch Implementation . . . . . . . . . . . . . . . . . . . . . . . . . Release and Upgrade Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 41 42 42 42 43

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Services for SAP BusinessObjects Trade Services . . . . . . . . . . . . . . . . . . . . . . . . Solution Management Assessment (SMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . GoingLive Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Early Watch Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Integration Check (TIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Volume Test Optimization (VTO) package . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 47 47 47 47 48 48 48 48 49 49 49 49

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

6/56

PUBLIC

2010-12-13

1 1.1

Getting Started Global Definitions

1 Getting Started

CAUTION

This guide does not replace the daily operations handbook that we recommend customers create for their specific production operations. Designing, implementing, and running your SAP applications at peak performance 24 hours a day has never been more vital for your business success than now. This guide provides a starting point for managing your SAP applications and maintaining and running them optimally. It contains specific information for various tasks and lists the tools that you can use to implement them. This guide also provides references to the documentation required for these tasks, so you need other guides such as the Master Guide, Technical Infrastructure Guide, Technical Operations Manual for SAP NetWeaver and SAP Library.

1.1 Global Definitions


SAP Application:

An SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM, SRM, SCM, or Global Trade Services. The delivery of an application contains SAP components, which are essential for implementing all application-related business scenarios, processes, and functions.
Business Scenario:

From a microeconomic perspective, a business scenario is a cycle, which consists of several different interconnected logical processes in time. Typically, a business scenario includes several company departments and involves other business partners. From a technical point of view, a business scenario needs at least one SAP application for each cycle and possibly other third-party systems. A business scenario is a unit, which can be implemented separately and reflects the customers prospective course of business.
Component:

A component is the smallest individual unit considered within the Solution Development Lifecycle; components are separately produced, delivered, installed, and maintained.

2010-12-13

PUBLIC

7/56

1 1.2

Getting Started Important SAP Notes

1.2 Important SAP Notes


CAUTION

Check regularly for updates of the Application Operations Guide.


Important SAP Notes SAP Note Number Title

30289 19227 209834

SAProuter documentation Get the latest saposcol CCMS agent technology

8/56

PUBLIC

2010-12-13

2 2.1

Technical System Landscape Scenario/Component Matrix

2 Technical System Landscape

2.1 Scenario/Component Matrix


This section provides an overview of which product area of SAP BusinessObjects Global Trade Services uses which software unit. All product areas of the software component SLL-LEG are optional depending on the business needs. For the latest component version and patch level requirements, see http://service.sap.com/scl.
Business Scenarios X = mandatory; (X) = optional; = not part of the business scenario Software Component Compliance Management Customs Management Preference Processing Letter of Credit Restitution Handling Electronic Compliance Reporting

SLL-LEG 900 SLL-PI 900_* SAP_AP 700 SAP NetWeaver ABAP Stack SAP NetWeaver Java Stack for Adobe Document Server (ADS) SAP Interactive Forms software by Adobe AP Pricing Engine of SAP NetWeaver Application Server for ABAP SAP NetWeaver Search and Classification (TREX)

X X X X

X X X X

X X X X

X X X X

X X X X

X (X) X X

(X)

(X)

(X)

(X)

(X)

(X)

2010-12-13

PUBLIC

9/56

2 2.2

Technical System Landscape Related Documentation Business Scenarios X = mandatory; (X) = optional; = not part of the business scenario

Software Component

Compliance Management

Customs Management

Preference Processing

Letter of Credit

Restitution Handling

Electronic Compliance Reporting

SAP NetWeaver Business Intelligence * SAP NetWeaver BI Content BI_CONT 7.03 Content Lifecycle Management POA_SBC_100 _702 Converter Software (Third Party Software) Business package GRC_POR 1000 as prerequisite for using the application user roles in SAP NetWeaver Portal Adobe Acrobat Reader

(X)

(X)

(X)

(X)

(X)

(X)

(X)

(X)

(X)

(X)

(x)

(x)

(x)

(x)

(x)

(x)

(x)

(X)

(X)

(X)

(X)

(X)

* PI_BASIS 2005_1_700 of SAP NetWeaver is a prerequisite for using SAP NetWeaver Business Intelligence The ABAP component of Content Lifecycle Management (CLM) is POASBC POA Shared Business Components. For more information about the software units of CLM, see the Master Guide for the application.

2.2 Related Documentation


For more information about the technical system landscape, see the following table:

10/56

PUBLIC

2010-12-13

2 2.2 Topic

Technical System Landscape Related Documentation Guide/Tool Location

Application-specific areas such as the following: a* Compliance Management a* Customs Management a* Preference Processing a* Letter of Credit a* Restitution Electronic a* Compliance Reportingl Technology Components such as SAP NetWeaver Application Server Sizing Technical Configuration Scalability High Availability Security

Master Guide

SAP Installations and Upgrades Installations and Upgrades - Entry by Application Group SAP Solutions for Governance, Risk and Compliance SAP Global Trade Services <Release> Installation and Upgrade
http://service.sap.com/swdc

Master Guide for SAP NetWeaver Quick Sizer Tool Technical Infrastructure Guide Security Map SAP BusinessObjects Global Trade Services Security Guide SAP NetWeaver Security Guide

http://service.sap.com/instguides

http://service.sap.com/sizing http://service.sap.com/installnw70

1- Planning

Technical Infrastructure Guide


http://service.sap.com/security

SAP Installations and Upgrades Installations and Upgrades - Entry by Application Group SAP Solutions for Governance, Risk and Compliance SAP Global Trade Services <Release> Installation and Upgrade
http://service.sap.com/swdc http://service.sap.com/security http://help.sap.com/nw70

Security in Detail System Administration

or

Security Guide Operations of NetWeaver usage types Monitoring with CCMS


http://help.sap.com/nw70 System Administration Technical Operations Manual Technical Operations Manual http://help.sap.com/nw70 Functional View SAP SAP NetWeaver NetWeaver by Key Capability Solution Life Cycle Management Library Solution Monitoring Monitoring in the CCMS

2010-12-13

PUBLIC

11/56

This page is left blank for documents that are printed on both sides.

Monitoring of SAP BusinessObjects Global Trade Services

3 Monitoring of SAP BusinessObjects Global Trade Services

Within the management of SAP Technology, monitoring is an essential task. A section has therefore been devoted solely to this subject. The aim of this section is to provide information and documentation to monitor SAP BusinessObjects Global Trade Service 10.0, for example by utilizing the Computing Center Management System (CCMS) and create a user-defined monitor set reflecting a customer-specific system landscape for SAP BusinessObjects Global Trade Services. For more information about the underlying technology, see the SAP NetWeaver Administrators Guide - Technical Operations Manual, particularly the section on Monitoring, in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual . As SAP BusinessObjects Global Trade Service 10.0 is powered by SAP NetWeaver 7.0 including Enhancement Package 22, we recommend that you set up the monitoring infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver at service.sap.com/operationsnw70 Monitoring . The monitoring setup described in the Monitoring Setup Guide (MSG) for SAP NetWeaver is the foundation for the following sections and contains all the information relevant to monitor the SAP NetWeaver components used in SAP BusinessObjects Global Trade Service 10.0. Proficient knowledge in system monitoring and basic knowledge in SAP NetWeaver is required to set up and manage userdefined monitors recommended within this guide.
NOTE

To build the necessary skills in system monitoring, we recommend the SAP courses and e-learning on that topic. For more information, see the information available on SAP Service Marketplace at service.sap.com/monitoring System Monitoring and Alert Management Education & Workshops Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions, including Content Lifecycle Management (CLM). The aim of this section is to provide information and documentation to monitor CLM, for example by utilizing the Computing Center Management System (CCMS) and NetWeaver ABAP monitoring tools.

2010-12-13

PUBLIC

13/56

3 3.1

Monitoring of SAP BusinessObjects Global Trade Services Alert Monitoring with CCMS RECOMMENDATION

Since Content Lifecycle Management is powered by SAP NetWeaver 7.02 and higher, we recommend that you set up the monitoring infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at http://service.sap.com/instguides. By default, CCMS monitoring capabilities are restricted to the local system and as CLM involves interactions with more than one system in a typical landscape, it could be beneficial to monitor other systems through CCMS from central CLM system. In this case, CLM, as the central monitoring system, can be configured to link CCMS monitoring from application systems. Since currently CLM only communicates with ABAP-based systems, RFC connection type can be used to enable monitoring across multiple systems. For more information about configuring the central monitoring system, see SAP Help Portal at http://help.sap.com SAP NetWeaver .

3.1 Alert Monitoring with CCMS


Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides you with the infrastructure and recommendations needed to set up your alert monitoring in CCMS to recognize critical situations for SAP BusinessObjects Global Trade Services as quickly as possible. For more information, see the Monitoring Setup Guide for SAP NetWeaver at http://service.sap.com/operationsnw70 Monitoring . To configure alert monitoring with CCMS for SAP BusinessObjects Global Trade Service 10.0, you must set up a Central Monitoring System (CEN) and connect the components for SAP BusinessObjects Global Trade Service to this CEN system. For a list of these components and the business scenarios for which they are relevant, see the section for Scenario/Component Matrix in this guide. Since SAP BusinessObjects Global Trade Service 10.0 utilizes the complete stack of SAP NetWeaver 7.0 including Enhancement Package 2, you have to apply the Monitoring Setup Guide for SAP NetWeaver to the component of SAP BusinessObjects Global Trade Service, first. In addition to this, you can define special monitors for SAP BusinessObjects Global Trade Service in the CEN Systems CCMS. You can access the Monitoring templates for SAP BusinessObjects Global Trade Services, called SAP BusinessObjects Global Trade Services using transaction RZ20 (see section Alert Monitoring for SAP BusinessObjects Global Trade Services in this guide for full details). In addition to this, you can define special monitors in the CEN systems CCMS for your own needs. There are also some additional monitoring objects designed to monitor cross-component communication and other scenario-specific critical situations.

14/56

PUBLIC

2010-12-13

3 3.1

Monitoring of SAP BusinessObjects Global Trade Services Alert Monitoring with CCMS

3.1.1 Central System Monitoring Architecture


We recommend that you integrate monitoring SAP BusinessObjects Global Trade Service into your existing Central Monitoring System (CEN) to monitor different SAP systems in a computing center environment. The administration effort is significantly lower if a centralized system monitoring is used rather than monitoring each system separately. The CEN should have the same SP level or higher as the highest available SAP NetWeaver Application Server (ABAP) SP level of SAP NetWeaver 7.0 including Enhancement Package 2 within the system landscape. For detailed instructions on how to set up a CEN system, see Configuring the Monitoring Architecture in SAP NetWeaver documentation in SAP Library at https://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Management Solution Monitoring Monitoring in the CCMS . The CEN system can be connected to the SAP Solution Manager if the monitoring scenario is configured and used. For more information about SAP Solution Manager, see the information available on SAP Service Marketplace at http://service.sap.com/solutionmanager . Systems and applications can be monitored with SAP Agent Technology. There are three different agents available for System Monitoring: L7 SAPCCM4X for SAP NetWeaver Application Server (ABAP) L7 SAPCCMSR for SAP NetWeaver Application Server (Java) with Adobe Document Server (ADS), Search & Classification (TREX), Internet Pricing and Configurator (IPC) for using Transaction Tax Engine (TTE) in customs duty calculation L7 CCMSPING for availability monitoring from CEN A fourth agent, SAPOSCOL, monitors the operating system data for each host from the CEN system. For more information about CCMS agents, see the documentation available on SAP Service Marketplace at https:://service.sap.com/monitoring Monitoring in Detail CCMS Agents: Features, Installation and Usage .
System Groups

Before creating new monitors for SAP BusinessObjects Global Trade Service, we recommend that you first maintain the system groups in transaction RZ21. A system group consists of a series of systems that you wish to display together in the CCMS monitoring architecture. You can specify a system group when you are defining a monitor the monitor then contains all systems that belong to the system group. Definitions of system groups are stored in the CCMS System Component Repository (SCR). The SCR is a component that maps to one or more SAP systems. To set up the system groups, go to transaction RZ21 and choose Technical Infrastructure Configure Central System Maintain System Groups . Here, you can also expand the tree to display the groups that have already been defined. For detailed instructions on how to maintain system groups, see Maintaining System Groups in SAP NetWeaver documentation in SAP Library at http://help.sap.com/nw70 Functional View SAP

2010-12-13

PUBLIC

15/56

3 3.1

Monitoring of SAP BusinessObjects Global Trade Services Alert Monitoring with CCMS

NetWeaver by Key Capability Solution Monitoring Monitoring in the CCMS Alert Monitor System Groups in the Alert Monitor .
EXAMPLE

The Alert Monitor Customizing the

The following table shows how you can create your system group:
System Group System

GTS_Systems SAP SLL-LEG 900 J2EE_Systems LACWPS SAP NetWeaver Application Server 702 XI_Systems SAP NetWeaver Process Integration (SAP NetWeaver PI, formerly Exchange Infrastructure, XI)
Properties Variant

You should also create a properties variant (for example, SLLLEG900_Default) to save your Customizing and configuration during the setup of the CEN. A monitoring properties variant contains the following data: i" Settings for properties i" Method assignments for monitoring tree elements (MTE) i" MTE classes and attribute groups. Every change made to these settings is assigned to a properties variant.

3.1.2 CCMS Monitoring Installation and Setup


For using the application-specific alert monitors for SAP BusinessObjects Global Trade Services 10.0, see SAP Note 1296394. With this SAP Note, you can install the application-specific monitors, called SAP GRC Global Trade Services, by using the XML file that is attached to this SAP Note. To enable the auto-alert mechanism of CCMS, see SAP Note 617547.
RECOMMENDATION

We recommend the usage of SAP NetWeaver for Central Monitoring.

3.1.3 Component-Specific Monitoring


One approach for monitoring an SAP BusinessObjects Global Trade Service 10.0 landscape is to monitor each component separately in the CEN system. The other approach is to monitor across components based on a business scenario. This section gives you an overview of how each component for running SAP BusinessObjects Global Trade Services could be monitored using CCMS. Which components need to be monitored depends on the scenarios and application areas you implemented for SAP BusinessObjects Global Trade Services. SAP BusinessObjects Global Trade Services is based on component SLL-LEG 900 for which you can set up monitors using CCMS.

16/56

PUBLIC

2010-12-13

3 3.1

Monitoring of SAP BusinessObjects Global Trade Services Alert Monitoring with CCMS NOTE

This monitoring set for SAP BusinessObjects Global Trade Services includes component-related monitors such as for the application component SLL-LEG 900 of SAP BusinessObjects Global Trade Services as well as for the logistics processes in the feeder system that are channeled through the plug-in for further processing in SAP BusinessObjects Global Trade Services. These monitors are not delivered by SAP but can be created in the CEN system. All Monitoring Tree Elements (MTE) used for these monitors are based on the default monitoring templates delivered by SAP. For information about editing or creating monitors and monitor sets, see the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at service.sap.com/operationsnw70 Monitoring.
Alert Monitoring for SAP NetWeaver

SAP NetWeaver 7.0 including Enhancement Package 2 is the integration and application platform for SAP BusinessObjects Global Trade Service 10.0, therefore the following SAP NetWeaver components must be integrated into the monitoring infrastructure: T`!J SAP NetWeaver Application Server (ABAP) [for SAP BusinessObjects Global Trade Service 10.0 and its component SLL-LEG 900] T`!J SAP NetWeaver Application Server (Java) [for the use of Adobe Document Server (ADS) for printing in SAP BusinessObjects Global Trade Service 10.0 or for running SAP NetWeaver Portal to use the application user roles] T`!J SAP NetWeaver Search and Classification (TREX) T`!J SAP NetWeaver Usage Type Process Integration (PI) T`!J SAP NetWeaver Business Intelligence (BI) For more information and detailed procedures, see the Monitoring Setup Guide and the Technical Operations Manual for SAP NetWeaver.
Alert Monitoring for SAP BusinessObjects Global Trade Services

The component SLL-LEG 900 for SAP BusinessObjects Global Trade Service 10.0 is based on SAP NetWeaver Application Server for ABAP. You can find information about monitoring the SAP NetWeaver AS for ABAP in the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at http://service.sap.com/operationsnw70 Monitoring and the Technical Operations Manual in SAP Library at http://help.sap.com/nw70 System Administration . What to Monitor The primary failure points of SAP BusinessObjects Global Trade Services 10.0 are within the technical infrastructure. Application-specific alert monitoring is available for component SLL-LEG 900 as well as the dependent plug-in component of SAP BusinessObjects Global Trade Services in the feeder system SAP ERP, SLL_PI 900_<SAP ERP Release>. You can set up additional monitors for specific processes in SAP BusinessObjects Global Trade Service according to your needs, for example, IDoc monitoring in the communication processes.

2010-12-13

PUBLIC

17/56

3 3.1

Monitoring of SAP BusinessObjects Global Trade Services Alert Monitoring with CCMS

Prerequisites Your SAP BusinessObjects Global Trade Service 10.0 is connected to the CEN and registered as a remote system. The SAPCCM4X agent is registered and running for the instance of SAP BusinessObjects Global Trade Service. Procedure 1. Go to transaction RZ20 and select the monitor SAP BusinessObjects Global Trade Services. 2. On the top level, you can choose between the following monitoring areas: Availability The availability monitor allows you to monitor RFC connections between connected systems in a system landscape. This monitor uses the standard SAP NetWeaver monitor for checking the RFC connection. You must have set up the RFC destination to the connected system before you can use the monitor. You can use this monitor in both components, SLL-LEG 900 for SAP BusinessObjects Global Trade Services as well as the corresponding plug-in in the feeder system SLL-PI_900_<release>. Logging The logging monitor collection that you can use for SLL-LEG 900 comprises virtual monitors the following log objects that you can use. Note that the logging subtree in this monitor only contains information if the system has logged error messages. With successful operations in the system, only the logging summary node is shown in the monitor.
CCMS Monitor Log Object
/SAPSLL/ BOM

Sub-Object
/SAPSLL/ BOM_R3

Description

Minimum Severity*

Communication with Feeder Systems

/SAPSLL/ BP /SAPSLL/ ECC

/SAPSLL/ BP_DISTR /SAPSLL/ MAT_R3

Communication with Authorities Operational Error

/SAPSLL/ ECC

/SAPSLL/ ECC_IN /SAPSLL/ ECC_OUT

/SAPSLL/ TREX /SAPSLL/ TREX_LOAD

/SAPSLL/ TSPL_STERMS

Bill of Material Transfer from Feeder System (SAP ERP) Business Partner Distribution Product from Feeder System (SAP ERP) ECC: Inbound Processing ECC: Outbound Processing SAPGTS: Generating Comparison Index for SAP TREX SLL: Legal Control: SPL: SPL Index

Error

Error Error Error Error Error

* Minimum severity level at which log entries influence the monitor. To enable the auto-alert mechanism of CCMS, see SAP Note 617547. The monitoring sets from CCMS monitoring in RZ20 can help analyze most critical bottlenecks; however, the following table points to some problem-oriented scenarios and a recommended tracking mechanism for CLM:

18/56

PUBLIC

2010-12-13

3 3.1

Monitoring of SAP BusinessObjects Global Trade Services Alert Monitoring with CCMS Problem Possible Causes Recommended Monitoring

CLM Scenario/Activity

Extraction of content from application system

RFC connection failure, Check system trace file system failure, no (ST01)/ SM59 / SMT1 for authorization for RFC calls trusted connections. CLM log in SLG1 Extraction in progress for Large amount of content Check background task in a long time SM37 and CCMS CLM monitor Validation errors Content in incorrect SLG1 application log for format CLM Importing content from a Exception occurred Malformed content or SLG1 application log for CLM package (zip) tempered content format CLM Time out Package size is too big Check CCMS memory or buffer sizes to free resources, increase time out limits for profile parameters, but usually cannot be resolved Exporting CLM content to Exception occurred Content was changed after SLG1 or check status of a package (zip) including in package content group Time out Content size is too big Remove huge attachments, split package into two smaller packages Deploy Content Exception occurred Incompatible system for SLG1 application log for application deployment of CLM, system trace file content, RFC connection (ST01), SMT1 for trusted failure, system failure, no connections authorization for RFC calls, no trusted system Deployment takes too Large amount of content SM37 or CCMS for CLM long deployment and polling results background job Non-recognized status in Failure on application Check target application deployment log deployment system, ST22, for any exceptions, authorization failures No deployment possible Existing deployment on Check DB locks in SM12 target system already on (table /POA/ going S_CLM_DEPLKEY)
Alert Monitoring for Content Lifecycle Management in SAP BusinessObjects Global Trade Services

Exception Occurred

Existing CCMS monitoring sets can be used to monitor various resources, objects, and performance. For example, SAP CCMS monitor template, which can be used to monitor system, database, and background processing for the application server where CLM is running. CLM provides monitoring set Content Lifecycle Management Monitor Set and monitors for CLM-relevant background jobs and CLM-

2010-12-13

PUBLIC

19/56

3 3.1

Monitoring of SAP BusinessObjects Global Trade Services Alert Monitoring with CCMS

relevant system resources as part of this set. This can be accessed in NetWeaver ABAP system using CCMS transaction RZ20. The following existing monitors within RZ20 can be used by CLM to monitor critical conditions: Background Processing For extraction and deployment scenarios in CLM, background jobs are created for a content group. CCMS view for background processing under Content Lifecycle Management Monitor Set can be used to retrieve statistics such as a list of long-running background jobs, number of free or occupied work processes, and any CLM job that was stopped abruptly.
NOTE

Transaction SM37 can be used to monitor background jobs initiated by CLM. Database Monitoring A connection RDBMS with the system where CLM is installed and being used can be monitored using database monitor within CCMS. Operating System Monitoring Operating system monitoring capabilities within CCMS administration workplace are used to analyze CPU, memory, paging, disks, file system, and their corresponding health statuses. Dialog Overview Using dialog monitoring in RZ20, the response time for dialog, network time, and number of currently logged-in users can be observed. For CLM, it is important to observe Web Dynpro ABAP-related attributes such as date transferred, session timeouts, and number of roundtrips against CLM Web Dynpro application - /POA/WD_CLM. This view is also part of the delivered CLM-specific Content Lifecycle Management Monitor Set.
Alert Monitoring for Scenarios

An addition to the component alert monitoring for all scenarios of SAP BusinessObjects Global Trade Service 10.0 monitoring of remote function calls (RFCs) is required. The scenarios of SAP BusinessObjects Global Trade Service 10.0 use standard monitoring functions provided by SAP NetWeaver to perform alert monitoring on RFCs. For more information, see Monitoring qRFC and tRFC Calls in SAP NetWeaver documentation in SAP Library at http:// help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Management Solution Monitoring Monitoring in the CCMS The Alert Monitor Special Monitoring Functions of the Alert Monitor . The communication process for importing and exporting goods with Customs Management of SAP BusinessObjects Global Trade Service 10.0 also requires IDoc alert monitoring for which it uses standard alert monitoring of SAP NetWeaver. For more information, see Central Monitoring Using ALE CCMS Monitor in SAP NetWeaver documentation in SAP Library at http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services

20/56

PUBLIC

2010-12-13

3 3.2

Monitoring of SAP BusinessObjects Global Trade Services Detailed Monitoring and Tools for Problem and Performance Analysis

Connectivity Interface/ALE

Components of SAP Communication Technology Administration Administering ALE Functions

Classical SAP Technologies (ABAP) Monitoring Message Exchange

IDoc

3.2 Detailed Monitoring and Tools for Problem and Performance Analysis
SAP BusinessObjects Global Trade Service 10.0 with its component SLL-LEG 900 is technically based on SAP NetWeaver Application Server (AS) of SAP NetWeaver 7.0 including Enhancement Package 2 For information about technical problem analysis, for example for database, operating system, workload analysis, and so on, refer to the Technical Operations Manual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual . The Operation Guide for SAP BusinessObjects Global Trade Service 10.0 covers only differences and additional information specific to the SAP BusinessObjects Global Trade Service.

3.2.1 Trace and Log Files


Logging and tracing for SAP BusinessObjects Global Trade Service 10.0 with its ABAP component SLLLEG 900 is done in the application log. The application logs for all scenarios of SAP BusinessObjects Global Trade Service 10.0 are integrated into the relevant functions for the individual business processes content and can be accessed within the individual functions. To select application logs from a single point of entry, the standard transaction SLG1 can be utilized that is provided by SAP NetWeaver. Each log has the attributes Object and Sub-object. These attributes identify the application that wrote the log. You can find the objects and sub-objects of SAP BusinessObjects Global Trade Service by selecting software component SLL-LEG and object /SAPSLL/ * with all assigned sub-objects.
Application logs for the following objects and their sub-objects Application Log Name
/SAPSLL/API_INBOUND /SAPSLL/BOM /SAPSLL/BOP /SAPSLL/BP /SAPSLL/CUC /SAPSLL/CUHD /SAPSLL/CUHD_ARCHIVE /SAPSLL/CUHD_MAP /SAPSLL/CUHD_SPL /SAPSLL/CUHD_SYNCH /SAPSLL/CUPED /SAPSLL/CUPED_ARCH

Description

API Inbound Processing Bill of Materials (Preference) Bill of Product (Restitution) Business Partner Customs Code Lists Customs Shipments and Customs Declarations (Documents for Customs Management) Customs Document: Archiving Mapping of API Interface to Customs Document Document SPL screening (scenario B2/C2) Synchronization of Document with Feeder System Supplementary Customs Declaration Supplementary Customs Declaration: Archiving

2010-12-13

PUBLIC

21/56

3 3.2

Monitoring of SAP BusinessObjects Global Trade Services Detailed Monitoring and Tools for Problem and Performance Analysis Description

Application Log Name


/SAPSLL/CUST /SAPSLL/ECC /SAPSLL/GEN /SAPSLL/IVM /SAPSLL/KMAT /SAPSLL/LCLIC /SAPSLL/LLNS /SAPSLL/PR /SAPSLL/PREF /SAPSLL/RES /SAPSLL/REX /SAPSLL/SPL_ARCHIVE /SAPSLL/TLC /SAPSLL/TREX /SAPSLL/TSPL /SAPSLL/WL /SAPSLL/WL_ARCHIVE

Legal Services Electronic Communication Generation Inventory Management Configurable Materials Legal Control: License Tariff Number System Customs Product Preference Restitution Reexport Archiving of the Sanctioned Party List Screening Data Customs Value Sanctioned Party List Screening with TREX Master Data for Sanctioned Party List Screening Logistics Integration Worklist Archiving for Logistics Integration Worklist

For more information about the process-integrated application log, see the relevant process and functional documentation for SAP BusinessObjects Global Trade Service scenarios in SAP Library at http://help.sap.com/grc Global Trade Services <Release> Application Help <Language> . SAP BusinessObjects Global Trade Service uses standard SAP NetWeaver technology for its system logs and traces. For more information, see section Tools in the Technical Operations Manual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Monitoring . Content Lifecycle Management Logs CLM writes logs during various activities at runtime; these can be used by administrators for auditing and monitoring purposes. EG". Application Log: Every CLM operation and corresponding steps carried out during that operation are recorded in the application log: Transaction SLG1, object: /POA/CLM The application log includes detailed information about error messages and sequential flow with respect to CLM technical processing. This object includes the following subobjects or categories: EG"A PACKAGE: Use this subobject to monitor and analyze the logs specific to CLM packages (all steps performed under Manage Packages function on CLM UI) EG"A CHECKPOINT: All actions performed under Manage Content Groups function in CLM are recorded for analysis under this application log subobject

22/56

PUBLIC

2010-12-13

3 3.2

Monitoring of SAP BusinessObjects Global Trade Services Detailed Monitoring and Tools for Problem and Performance Analysis

QE^V DEPLOYMENT: Application logs related to deployment step from CLM are recorded under this subobject QE^V TECHNICAL: Additional technical log details are recorded under this subobject. QE^9 Deployment Log: This is available on CLM UI. It displays statuses and messages for deployments from CLM to the application. The deployment log provides details of application-specific messages per deployment system and per content group. QE^9 Change Log or Change History: For all actions that can be carried out in CLM UI, such as editing, deployment, import, and export. CLM logs the change history using the change documents function of ABAP. CLM change logging is enabled for packages and content groups and related tables. This can be seen in CLM UI with View History function. QE^9 Customizing object or Table Logging: All Customizing, control, and system database tables defined in CLM are enabled for logging. Analysis of this logging can be done using SCU3 transaction in NetWeaver ABAP system if logging is switched on. Content Lifecycle Management (CLM) does not provide any special tracing and log files facility as this can be easily obtained from the NetWeaver ABAP framework. It is essential to collect trace and log files for RFC calls. CLM carries out critical operations through RFC protocol to extract and deploy the contents onto application systems. Important Log and Trace Files for CLM
Component Content File Path

System Trace Analysis RFC, HTTP, DB SQL Performance Trace and Analysis RFC, HTTP, DB

Transaction ST01 Transaction ST05

3.2.2 Interface Monitors


Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP. For more information, see the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at http://service.sap.com//operationsnw70 Monitoring Monitoring Setup Guide for NW 7.0 SP Stack <SPS Number> and the Technical Operations Manual at http://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Administration Connectivity . Content Lifecycle Management (CLM) communicates with application system using RFC. For certain intensive operations, such as content extraction, interface monitors could be used to analyze the time spent on each RFC call.
Interface Detailed Description Technology Used

You configure APIs and RFC functions in Customizing for Content Lifecycle ABAP Web Dynpro Management under Maintain System Registry API Groups . application uses these calls and

RFC

2010-12-13

PUBLIC

23/56

3 3.2

Monitoring of SAP BusinessObjects Global Trade Services Detailed Monitoring and Tools for Problem and Performance Analysis Detailed Description

Interface

Technology Used

/POA/CLM_WD

interfaces at runtime ABAP Web Dynpro application is accessed using HTTP

HTTP

3.2.3 Workload Monitors


A default workload collector as part of CCMS monitoring and workload monitor through transaction ST03N can be used to observe the workload records at application server level.
Component Monitor Detailed Description Prerequisites

Workload Monitor Transaction ST03N

Detailed analysis of workload of application servers

The transport workflow provides a framework for transporting enhancements or new developments of existing business functions in a system landscape. It is an efficient method of transporting a selected number of requests into a group of transport targets, and uses clearly defined approval steps to ensure the quality of your target systems. For more information, see the Technical Operations Manual on SAP Help Portal at http://help.sap.com SAP NetWeaver .

3.2.4 Data Growth and Data Archiving Monitors


You can monitor archiving of objects, such as documents or audit trails, independently of SAP BusinessObjects Global Trade Service, for example in any SAP ERP system. You can access the Archive Information System (AS) for this in transaction SARA and by choosing Archive Explorer. From here, you can select the archived objects you want to display. For more information, see the following documentation available on SAP Library:
Monitor Documentation

Data Archiving Monitor (SAR_SHOW_MONITOR) Database Monitoring (ST04, DB02)

Technical Operations Manual in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual General Administration Tasks and one of the following options Data Archiving 4" Database Administration 4"

The following table lists the fastest growing tables for SAP BusinessObjects Global Trade Service 10.0. If you integrated your processes into the logistics processes of SAP ERP as your feeder system, you should also refer to the feeder system tables listed below.

24/56

PUBLIC

2010-12-13

3 3.2

Monitoring of SAP BusinessObjects Global Trade Services Detailed Monitoring and Tools for Problem and Performance Analysis Table
CDPOS CDHDR BALHDR /SAPSLL/CORREF /SAPSLL/CUIT /SAPSLL/CUPEDRI /SAPSLL/CUSWLD /SAPSLL/CUSWLF /SAPSLL/CUSWLQ /SAPSLL/PRPREF

Component

SLL-LEG 900

Feeder System

/SAPSLL/OBJIDX /SAPSLL/SSF

Component

Monitor Detailed Description

Prerequisites

CLM DB tables ST05

Observe critical operations and tables Switch the trace on before performing that take more time along with their hit costly operations, such as extracting and miss ratio content groups

Some of the intensive database tables that can be viewed during critical long-running operations: L-v /POA/D_CLM_CP02 CLM Content group and Entity relationship L-v /POA/D_CLM_DPLR Table for storing entity processing messages L-v /POA/D_CLM_ENT01 CLM Entity Table L-v /POA/D_CLM_ENT02 CLM Entity Fields value Table L-v /POA/D_CLM_ENT03 CLM Entity Entity Relationship L-v /POA/D_CLM_ENT10 CLM Entity Raw Data Extract Table For more information about archiving objects, see the following documentation in SAP Library at http://help.sap.com/grc Global Trade Services <Release> Application Help <Language> System Administration Archiving Data . For information about periodic tasks required to contain data growth (that is, to reorganize temporary data), see Periodic Tasks in this guide.

3.2.5 Specific Problem Analysis Tools


SAP BusinessObjects Global Trade Service 10.0 uses the following monitoring functions provided by SAP NetWeaver Application Server ABAP in SAP NetWeaver 7.0 including Enhancement Package 2, which are particularly vital for the processes in SAP BusinessObjects Global Trade Service.
IDoc Monitoring

For communicating with the feeder system or the converter software, you can monitor transactional remote function calls (tRFC) using transaction sm58. There, you can display the tRFCs that were sent

2010-12-13

PUBLIC

25/56

3 3.3

Monitoring of SAP BusinessObjects Global Trade Services Data Consistency

asynchronously and determine whether any errors occurred. Then choose System Administration System Communication IDoc Monitoring to monitor the following: DY@9 IDoc List Display You can display all the inbound and outbound IDocs DY@9 IDoc Search You can search for specific IDocs DY@9 IDoc Statistics You can call inbound and outbound IDocs that were sent and received during a specific time frame. You can also see which errors occurred in the IDoc processing. DY@9 IDoc Status Monitoring You can display the status of IDocs that still have to be processed. For more information about the communication process with the authorities, see the documentation in SAP Library at http://help.sap.com/grc Global Trade Services <Release> Application Help <Language> System Administration System Monitoring Communication between SAP GTS, EDI Converter, and Customs Authorities .
Transactional Remote Function Call Monitoring

For communicating with the feeder system or the converter software, you can monitor transactional remote function calls (tRFC) using transaction sm58. There, you can display the tRFCs that were sent asynchronously and determine whether any errors occurred.
Distributed Statistical Records

For more information about the motivation behind distributed statistical records and how to define and use them, see section Technology in the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at http://service.sap.com/operationsnw70 Monitoring Monitoring Setup Guide (CEN 7.0 EHP<#> SP Stack <#>) .

3.3 Data Consistency


SAP BusinessObjects Global Trade Service 10.0 only consists of one application component. Thus data inconsistency and data storage errors between different components cannot occur. Content Lifecycle Management (CLM) is used as a repository containing application content. The content in the CLM repository can be added either by extraction from various application systems or by importing a new vendor-delivered package. During these operations CLM always loads the data first and performs validations on top of such content to report functional inconsistencies. If there are abrupt blockages, such as connection timeout, it can result in differences between the data maintained in CLM and data present in other sources.

26/56

PUBLIC

2010-12-13

3 3.3

Monitoring of SAP BusinessObjects Global Trade Services Data Consistency RECOMMENDATION

In this scenario, we recommend rerunning the operation as there is no impact of this operation on any business function in CLM.

2010-12-13

PUBLIC

27/56

This page is left blank for documents that are printed on both sides.

Logging On and Load Balancing

4 Logging On and Load Balancing

2010-12-13

PUBLIC

29/56

This page is left blank for documents that are printed on both sides.

5 5.1

Management of SAP Application Starting and Stopping

5 Management of SAP Application

SAP provides you with an infrastructure to help your technical support consultants and system administrators effectively manage all SAP components and complete all tasks related to technical administration and operation. This infrastructure provides the following: }HM A central interface for managing administrative middleware tasks }HM Improved problem resolution processes for the entire solution }HM Standardized administration of user profiles For more information about the underlying technology, see the Technical Operations Manual of SAP NetWeaver 7.0 including Enhancement Package 2.

5.1 Starting and Stopping


SAP BusinessObjects Global Trade Service 10.0 is an add-on and therefore complies with the Start and Stop Sequence and Tools of SAP NetWeaver 7.0 including Enhancement Package 2, on which SAP BusinessObjects Global Trade Service is installed. For more information, see Starting and Stopping the System in the Technical Operations Manual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS ABAP (Applicatoin Server for ABAP) Management . For the list of components required for each scenario, see Software Component Matrix in this guide. Refer to Troubleshooting in this guide for analyzing problems if a component does not start properly.

5.2 Software Configuration


This chapter explains which components or scenarios used by this application are configurable and which tools are available for adjusting.
Application configuration tools Configuration Tool (s) Description

Customizing

SAP Solution Manager

You can access the Customizing in the application system with transaction code SPRO. The Customizing is the standard SAP tool for ABAP-based systems used for component Customizing. SAP Solution Manager is the standard tool for process- and scenario-based configuration. For more information, see SAP Note 1230438.

2010-12-13

PUBLIC

31/56

5 5.3

Management of SAP Application Administration Tools

Note that SAP BusinessObjects Global Trade Service only requires the configuration of the business scenarios and processes. With SAP BusinessObjects Global Trade Service being an add-on to SAP NetWeaver, no technical configuration is required that is specific to SAP BusinessObjects Global Trade Service. It only uses basis parameters for database, operating system, and Application Server ABAP provided by SAP NetWeaver. For more information about configuration and its concept, see SAP Library at http:// help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Customizing .

5.3 Administration Tools


SAP BusinessObjects Global Trade Service 10.0 and its component SLL-LEG 900 are technically based on SAP NetWeaver. For information about the relevant administration tools, see the Technical Operations Manual for SAP NetWeaver 7.0 in SAP Library at http://help.sap.com/nw70 System Administration . Content Lifecycle Management Administrator/Developer Utilities CLM provides utilities for testing purposes, which are intended for administrators and developer user groups. Application API Adapter testing: Since CLM calls the RFC function modules while communicating with application systems, it expects a certain format and interface for these API/RFC function modules. Moreover, an appropriate system setup is also required via system registry configuration where new application systems and their APIs are registered. For more information, see Customizing for Content Lifecycle Management under Maintain System Registry. In actual scenarios or for productive usage; before you run CLM with system registry settings, it is advisable to run the test adapter utility using transaction /POA/CLM_API_TESTER. You need to provide the system registry ID. The transaction checks API interfaces and also performs a test run for extraction and deployment operations. Cleaning up the CLM database: If you are running CLM for test purposes or on a test system, and you find CLM database tables increasing in size over time; you can use transaction /POA/ CLM_CLEANUP to delete the CLM-specific database tables.
NOTE

This program completely deletes all CLM data and does not allow any preferences to be set for specific entry deletion from CLM database tables. Hence it is intended to be used for cleaning up garbage or unused data from the test CLM system only.

32/56

PUBLIC

2010-12-13

5 5.4

Management of SAP Application Backup and Restore

5.4 Backup and Restore


You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure. The backup and restore procedure for SAP BusinessObjects Global Trade Service 10.0 as add-on is identical to the one of SAP NetWeaver 7.0 including Enhancement Package 2 on which SAP BusinessObjects Global Trade Service is installed. For more information about the following topics see the mentioned section in the Technical Operations Manual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual : $" For Backup and Recovery, see Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Administration Backup and Recovery $" For High Availability, see section General Administration Tasks The backup and restore strategy for applications consists of two parts: $" Backup and restore coverage for each component (see table below) $" Cross-system data dependencies and handling The backup and restore strategy for your system landscape should not only consider SAP systems but should also be embedded in overall business requirements and incorporate your companys entire process flow. In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data center through fire. It is most important in this context that you ensure that backup devices are not lost together with normal data storage (separation of storage locations).
Categories of System Components Category Properties Suggested Methods for Backup and Restore Examples

II

IX

Only software, no configuration or application data Only software and configuration information, no application data Original application data, data exchange with other systems, data not managed by a DBMS

$" No backup, new installation in case of a recovery or $" Initial software backup after installation and upgrade $" Backup of log files $" Backup after changes have been applied or $" No backup, new installation and configuration in case of a recovery $" Backup of log files

BDOC modeler

SAP Gateway Comm. Station SAP Business Connector SAP IPC (2.0C)

Data $" Application specific file system backup, data consistency with other systems must be considered $" Backup of software, configuration, log files

2010-12-13

PUBLIC

33/56

5 5.5

Management of SAP Application Application Copy

Categories of System Components

Category Properties

Suggested Methods for Backup and Restore

Examples

XI

Original Data ; SAP ERP application Database and log backup, application log ; ; SAP Customer data, data backup (such as job logs in file system), data Relationship exchange with consistency with other systems must be Management (SAP other systems, considered CRM) based on SAP ; Backup of software, configuration, log files ; SAP NetWeaver NetWeaver Business Intelligence Application (SAP NetWeaver BI) Server
Categories Data to be backed up Application Data

Component

SLL-LEG 900

XI

SLL_PI 900_<SAP ERP Release> SAP NetWeaver TREX SAP NetWeaver ADS
Categories of System Components

IX I II

; Database and log backup ; File system backup (full and/or incremental) Database and log backup File system backup File system backup

; Original ; Replicated

Original Original

Category Properties

Suggested Methods for Backup and Restore

Examples

VIII

Original Data: Standalone application ; Database and log backup, application log backup (such SAP R/3 data, as job logs in file system) standalone ; Backup of software, configuration log files system based on SAP WebAS

The following table lists the CLM components relevant for backup and recovery:
Component Data to be Backed Up
POASBC

Backup Method/Tool

Recommended Backup Frequency

Application database tables, logs

Database and log backup Yearly

5.5 Application Copy


For more information about prerequisites, procedures, and limitations for copying components of SAP BusinessObjects Global Trade Service, see section System Copy in the Technical Operations Manual for SAP NetWeaver in SAP Library at httP://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems Administration Background Processing .

34/56

PUBLIC

2010-12-13

5 5.6

Management of SAP Application Periodic Tasks

5.6 Periodic Tasks 5.6.1 Scheduled Periodic Tasks


For more information about standard background jobs and periodical tasks for SAP NetWeaver components, see the Technical Operations Manual for SAP NetWeaver in SAP Library at http:// help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems Administration Background Processing . CLM uses background jobs for the execution of some operations at runtime. The following table gives an overview of the exact programs that are scheduled in the background and the frequency at which these are executed. Scheduled periodic tasks for Content Lifecycle Management:
Program Name/Task TaskScheduling Tool Recommended Frequency Detailed Description

/POA/ R_CLM_DEPLOY_RESULTS_POLL

Automatic 10 minutes: This can be changed in Customizing for Content Lifecycle Management under Maintain Technical Settings

Used to retrieve the deployment results of application content from target application systems. For more information, see Content Group Deployment in SAP Library documentation under Content Lifecycle Management Content Group and Package Management Content Group Deployment .

Other background tasks in Content Lifecycle Management that are scheduled to run immediately:
Program Name/Task Task-Scheduling Tool Recommended Frequency Detailed Description

/POA/R_CLM_EXTRACT Automatic /POA/R_CLM_DEPLOY Automatic

Immediately when the operation is triggered Immediately when the operation is triggered

Background task during content group extraction Background task for content group upload and deployment

5.6.2 Required Manual Periodic Tasks


This chapter describes all manual tasks required to run periodically to keep the application running smoothly over time. A manual task needs a person to for each execution in comparison to the scheduled tasks listed above which can be automated using a task scheduler program. It is important that you monitor the successful execution of these tasks on a regular basis. SAP BusinessObjects Global Trade Service creates log files to identify problems. You need to check the log files on a regular basis, for example, to detect blocked documents. This enables you to identify problems promptly and to react accordingly. Also, the following application-specific tasks are relevant for execution of background jobs or require execution in background jobs:

2010-12-13

PUBLIC

35/56

5 5.7

Management of SAP Application Load Balancing

oZEK In the feeder system: oZEKh Check change pointers for master data and transfer changed data from feeder system to SAP BusinessObjects Global Trade Service oZEKa Creditors relevant for all scenarios in the application oZEKa Debitors relevant for all scenarios in the application oZEKa Material master relevant for all scenarios in the application oZEKa Bill of materials relevant for Trade Preference Processing and Legal Control of the application oZEKh Transfer duty-paid stock for customs warehousing relevant for Imports and Exports with Customs Management of the application For more information about the periodic tasks in the feeder system for SAP BusinessObjects Global Trade Service, see section Data Replication in the Configuration Guides on SAP Service Marketplace at http://service.sap.com/swdc SAP Installations and Upgrades Installations and Upgrades - Entry by Application Group SAP Solutions for Governance, Risk and Compliance SAP Global Trade Services <Release> Installation and Upgrade . oZEK In SAP BusinessObjects Global Trade Service oZEKh Distribute Product Data to Feeder System for Special Customs Procedures relevant for imports and exports with Customs Management of the application http://help.sap.com/grc Global Trade Services <Release> Application Help <Language> Customs Management Master Data . oZEKh Further functions can also be scheduled for background processing but do not require periodical execution. The relevant functional descriptions contain references if execution of the programs using background jobs is possible. For more information, see the documentation in SAP Library at http://help.sap.com/grc Global Trade Services <Release> Application Help <Language> System Administration System Monitoring .

5.7 Load Balancing


SAP BusinessObjects Global Trade Service uses no specific load balancing methods for its one component SLL-LEG. If necessary, it only applies methods provided by the basis technology of SAP NetWeaver. For more information about the load balancing with SAP NetWeaver, see SAP Library at http:// help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems . As a web-based application, the basis for logon and load balancing in Content Lifecycle Management is a high availability landscape setup together with a load balanced network setup.

36/56

PUBLIC

2010-12-13

5 5.8

Management of SAP Application User Management

For more information about network load balancing, see the Technical Infrastructure Guide for SAP NetWeaver on SAP Service Marketplace at http://service.sap.com/instguides. A load-balanced network using SAP Web Dispatcher together with logon groups in the SAP NetWeaver systems can be used to redirect certain users to specific application servers.

5.8 User Management


SAP BusinessObjects Global Trade Service uses the user management tools provided by SAP NetWeaver. For more information, see http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Identity Management Identity Management of the Application Server ABAP . All scenarios and components in Content Lifecycle Management use the user management functions provided by NetWeaver. For more information about user administration and authentication, see the application security guide on SAP Service Marketplace at http://service.sap.com/securityguide.

5.9 Printing
SAP BusinessObjects Global Trade Service uses the SAP NetWeaver technology for printing. For more information about printing, see SAP Library at http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability System Management SAP Printing Guide (BC-CCM-PRN) .

2010-12-13

PUBLIC

37/56

This page is left blank for documents that are printed on both sides.

High Availability

6 High Availability

The processes of SAP BusinessObjects Global Trade Service are based on master and transaction data from one or more feeder systems. If a failure on SAP BusinessObjects Global Trade Service component SLL-LEG occurs, all business processes in the feeder system based on action in SAP BusinessObjects Global Trade Service cannot be performed. To avoid any inconveniences SAP BusinessObjects Global Trade Service provides a recovery scenario. In SAP Compliance Management, for example, the discontinuation of the logistics processes in the feeder systems depends on customizing settings for each area within SAP Compliance Management. If action from SAP BusinessObjects Global Trade Service is required by the feeder system at a time when SAP BusinessObjects Global Trade Service is not available, you can configure your system in such a way that one of the following options holds true: Dr# Either all subsequent processes are blocked until SAP BusinessObjects Global Trade Service is available again and can perform the tasks needed before continuing the processes in the feeder system. Dr# All subsequent processes can be performed without getting a response from SAP BusinessObjects Global Trade Service and SAP BusinessObjects Global Trade Service will perform the tasks once the system becomes available again. Dr# Alternatively, you can allow all subsequent processes to be performed without any checks if SAP BusinessObjects Global Trade Service is not available. The main framework of Content Lifecycle Management is based in SAP NetWeaver. If the software component for CLM becomes unavailable, all business scenario concerning CLM stop working. Unavailability of CLM does not break any other software components or application functions.
Component Detailed Description HA Setup Description

POASBC - POA Shared Business Components 1.0

CLM is part of the POASBC Software component

For more information about high availability and switchover, see the Technical Operations Manual on SAP Help Portal at http://help.sap.com SAP NetWeaver .

NOTE

We recommend you also refer to the following documentation: Dr# BC SAP High Availability for SAP NetWeaver 7.0 including Enhancement Package 2 This document provides a general discussion and sound introduction to the topic of high availability for the SAP NetWeaver Application Server. It is part of the standard SAP documentation package delivered with SAP NetWeaver Application Server. It deals comprehensively with safeguarding SAP NetWeaver Application Server system operation.

2010-12-13

PUBLIC

39/56

High Availability

You can find this document on SAP Service Marketplace at http://service.sap.com/ha Media Library Documentation HA Documentation . .$ Switchover For information about switchover, see on SAP Service Marketplace the infrastructure information at http://service.sap.com/installnw70 1- Planning Technical Infrastructure Guide High Availability Support for Failover Clustering (HA) Switchover Units and in the installation information at http://service.sap.com/installnw70 2- Installation - SAP NetWeaver Systems SAP NetWeaver 7.0 incl. EHP2 - Installation Guides

40/56

PUBLIC

2010-12-13

7 7.1

Software Change Management Transport and Change Management

7 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams. The goal of Software Change Management is to establish consistent, solution-wide change management that allows for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products. SAP BusinessObjects Global Trade Service 10.0 and its component SLL-LEG 900 are based on SAP NetWeaver Application Server ABAP of SAP NetWeaver 7.0 including Enhancement Package 2. You can find information about the Software Change Management in the according document section of the Technical Operations Manual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Software Logistics. The following topics are covered in the SAP NetWeaver document: 7Z Transport and Change Management - Enables and secures the distribution of software changes from the development environment to the quality assurance and production environment. 7Z Development Request and Development Release Management - Enables customer-specific maintenance procedures and open integration with third-party products. 7Z Support Packages and SAP Notes Implementation - Provide standardized software distribution and maintenance procedures. 7Z Release and Upgrade Management - Reduces time, cost, and risk associated with upgrades. 7Z Quality Management and Test Management - Reduce the time, cost, and risk associated with software changes. 7Z Template Management - Enables and secures the rollout of global templates, including localizations.

7.1 Transport and Change Management


SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems in your system landscape. For more information, see Technical Operations Manual for SAP NetWeaver in SAP Library at http:// help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Software Logistics. Change and Transport System .

2010-12-13

PUBLIC

41/56

7 7.2

Software Change Management Development Requests and Development Release Management

7.2 Development Requests and Development Release Management


The transport workflow provides a framework for transporting enhancements or new developments of existing business functions in a system landscape. It provides a direct connection between development and transport administration. The transport workflow manages the transport process, determines the user for each individual step automatically, and then displays an interface that they can use to perform the task directly. It is an efficient method of transporting a selected number of requests into a group of transport targets, and uses clearly defined approval steps to ensure the quality of your target systems. For more information, see the Technical Operations Manual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Software Logistics. Releasing Software Changes and Quality Management .

7.3 Quality Management and Test Management


You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP). For more information, see the documentation in SAP Library at http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Testing .

7.4 Support Packages and Patch Implementation


Information about the Support Packages (SPs) available for SAP BusinessObjects Global Trade Service 10.0 can be found in the Release Information on SAP Service Marketplace at http:// service.sap.com/ocs-schedules . Support Packages for components based on the SAP NetWeaver Application Server ABAP are applied using the Support Package Manager. For more information, see the Technical Operations Manual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 <SPSxx> Support Package Stack Guide <SPSxx> . SAP Notes that require code changes for components based on the SAP NetWeaver Application Server ABAP can be applied using the SAP Note Assistant. For more information, see the documentation in SAP Library at http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability Software Lifecycle Management Note Assistant .

42/56

PUBLIC

2010-12-13

7 7.5

Software Change Management Release and Upgrade Management

7.5 Release and Upgrade Management


You can check which components are installed in your system by logging on to your SAP BusinessObjects Global Trade Services and selecting from the menu options System Status . For more information about release and upgrade options or plans for SAP BusinessObjects Global Trade Services, see http://service.sap.com/pam .

2010-12-13

PUBLIC

43/56

This page is left blank for documents that are printed on both sides.

Troubleshooting

8 Troubleshooting

In case of problems, refer to the troubleshooting guide for SAP NetWeaver Application Server. For more information, see SAP Library at http://help.sap.com/nw70 System Administration Technical Operations Manual General Administration Tasks Troubleshooting for SAP Web Application Server . The SAP NetWeaver Problem Analysis Guide contains the following problem analysis scenarios for the various components of the usage type Application Server. Pe Security Problem Analysis Scenarios Pe Adobe Document Services Problem Analysis Scenarios Pe System Landscape Directory Problem Analysis Scenarios Pe Process Monitoring Infrastructure Problem Analysis Scenarios Pe SAP Knowledge Warehouse Problem Analysis Scenarios Pe Web AS Java Pe Change Management Server Problem Analysis Scenarios Pe J2EE Engine Problem Analysis Scenarios Pe Web Dynpro Java (ESS Scenario) Problem Analysis Scenarios Pe Design Time Repository Problem Analysis Scenarios Pe SAP Java Connector Problem Analysis Scenarios For more information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types, see the SAP NetWeaver Problem Analysis Guide (PAG) in SAP Library at http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability SAP NetWeaver PAG Usage Type Application Server ABAP . If you encounter specific problems in executing processes you need to check the logs in the feeder system and in SAP BusinessObjects Global Trade Service. If no monitoring information is displayed in the CCMS Alert Monitor with transaction RZ20 of the central monitoring system, see CCMS Monitoring Infrastructure Problem Analysis Guide (PAG). In addition, a troubleshooting section for the communication process between SAP BusinessObjects Global Trade Service, the converter system, and the Customs authorities when processing imports and exports with Customs Management is included in SAP Library for SAP BusinessObjects Global Trade Service. For more information, see SAP Library at http://help.sap.com/grc Global Trade Services <Release> Application Help <Language> System Administration System Monitoring .

2010-12-13

PUBLIC

45/56

This page is left blank for documents that are printed on both sides.

9 9.1

Support Desk Management Remote Support Setup

9 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure. For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently.

9.1 Remote Support Setup


SAP support needs to be able to work remotely for highest efficiency and availability. For this support, SAP uses the remote connection with SAProuter for a specific problem that you log by creating a customer message in the SAP Support Portal. For information about SAProuter, see SAP Note 486688 and the SAP Notes this SAP Note refers to for specific settings or parameters that are necessary. Further assistance provides SAP Note 812386

9.2 Problem Message Handover


For sending problem messages/tickets to SAP use components SLL-LEG* and provide a detailed and reproducible problem description.

9.3 Services for SAP BusinessObjects Trade Services


SAP BusinessObjects Global Trade Service offers, for example, the following safeguarding and solution management services to optimize you implementation project: For more information about these services, see SAP Safeguarding on SAP Service Marketplace at http://service.sap.com/safeguarding .

9.3.1 Solution Management Assessment (SMA)


The SAP Solution Management Assessment maps your solution landscape and your core business processes. It identifies weak points and the impact they have on your core business processes. A list is then generated containing the measures we recommend you to take for your solution as well as an action plan, which explains how and when these measures can be implemented.

2010-12-13

PUBLIC

47/56

9 9.3

Support Desk Management Services for SAP BusinessObjects Trade Services

9.3.2 GoingLive Check


The SAP GoingLive Check helps you manage technical risk to ensure optimal performance, availability, and maintainability of SAP BusinessObjects Global Trade Service. You can use it during a new implementation or when you experience a significant increase of data and user volume. It proactively analyzes your core business processes within your solution landscape to guide you to a smooth start of production and technically robust operations afterwards.

9.3.3 Early Watch Service


The SAP EarlyWatch Check analyzes the components of your SAP solution, your operating system, and database to determine how to optimize performance and keep your total cost of ownership to a minimum.

9.3.4 Technical Integration Check (TIC)


The technical integration check safeguards your implementation project from complications due to integration issues. It looks at the critical interfaces in your core business processes and makes sure they meet the requirements of SAP BusinessObjects Global Trade Service in terms of availability, performance, maintainability, and data consistency.

9.3.5 Volume Test Optimization (VTO) package


With this package, SAP provides help and guidance to optimize your test procedure and administration during the volume and stress test phase of a project. This service provides recommendations on how to improve your current test environment and how to effectively use latest SAP test technologies.

48/56

PUBLIC

2010-12-13

A A.1

Appendix Appendix

A Appendix

A.1 Appendix A.1.1 Related Guides


For more information about installation and configuration, see the Master Guide. The following table contains links to information relating to the Operation Guide:
Content Quick Link to the SAP Service Marketplace at http://service.sap.com

Master Guide

SAP Installations and Upgrades Installations and Upgrades - Entry by Application Group SAP Solutions for Governance, Risk and Compliance SAP Global Trade Services <Release> Installation and Upgrade
/swdc /notes /platform /securityguide or /network /solutionmanager

Relates SAP Notes Released Platforms Network Security SAP Solution Manager

A.1.2 Related Information


The following table contains links to information relating to the Solution Operation Guide.
Content Quick Link on SAP Service Marketplace
http://service.sap.com/instguides http://service.sap.com/notes http://service.sap.com/platforms http://service.sap.com/securityguide http://service.sap.com/network http://service.sap.com/ti http://service.sap.com/solutionmanager

Master Guide, Installation Guide and Upgrade Guide Related SAP Notes Released Platforms Network Security Network Security Technical Infrastructure SAP Solution Manager

2010-12-13

PUBLIC

49/56

This page is left blank for documents that are printed on both sides.

B B.1

Reference The Main SAP Documentation Types

B Reference

B.1 The Main SAP Documentation Types


The following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software.

:5OM^l $}%-sDocumentation Types in the Software Life Cycle Cross-Phase Documentation

SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many glossary entries in English and German. : Target group: : Relevant for all target groups : Current version: : On SAP Help Portal at http://help.sap.com Additional Information Glossary (direct access) or Terminology (as terminology CD) : In the SAP system in transaction STERM SAP Library is a collection of documentation for SAP software covering functions and processes. : Target group:

2010-12-13

PUBLIC

51/56

B B.1

Reference The Main SAP Documentation Types

::t@Q Consultants ::t@Q System administrators ::t@Q Project teams for implementations or upgrades ::t@> Current version: ::t@Q On SAP Help Portal at http://help.sap.com (also available as documentation DVD) The security guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for SAP NetWeaver. This document contains general guidelines and suggestions. SAP applications have a security guide of their own. ::t@> Target group: ::t@Q System administrators ::t@Q Technology consultants ::t@Q Solution consultants ::t@> Current version: ::t@Q On SAP Service Marketplace at http://service.sap.com/securityguide
Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable units for each business or IT scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also provides references to other documents, such as installation guides, the technical infrastructure guide and SAP Notes. ::t@> Target group: ::t@Q Technology consultants ::t@Q Project teams for implementations ::t@> Current version: ::t@Q On SAP Service Marketplace at http://service.sap.com/instguides The installation guide describes the technical implementation of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. ::t@> Target group: ::t@Q Technology consultants ::t@Q Project teams for implementations ::t@> Current version: ::t@Q On SAP Service Marketplace at http://service.sap.com/instguides Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle platform. One of its main functions is the configuration of business and IT scenarios. It contains Customizing activities, transactions, and so on, as well as documentation. ::t@> Target group: ::t@Q Technology consultants

52/56

PUBLIC

2010-12-13

B B.1

Reference The Main SAP Documentation Types

,? Solution consultants ,? Project teams for implementations ,P Current version: ,? In SAP Solution Manager The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The Customizing activities and their documentation are structured from a functional perspective. (In order to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager, which refers to the relevant Customizing activities in the individual SAP systems, is used.) ,P Target group: ,? Solution consultants ,? Project teams for implementations or upgrades ,P Current version: ,? In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver, and precedes the solution operations guide. The manual refers users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/restore, master data maintenance, transports, and tests. ,P Target group: ,? System administrators ,P Current version: ,? On SAP Service Marketplace at http://service.sap.com/instguides The solution operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks. ,P Target group: ,? System administrators ,? Technology consultants ,? Solution consultants ,P Current version: ,? On SAP Service Marketplace at http://service.sap.com/instguides
Upgrade

The upgrade master guide is the starting point for upgrading the business and IT scenarios of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the upgrade guides and SAP Notes. ,P Target group: ,? Technology consultants

2010-12-13

PUBLIC

53/56

B B.1

Reference The Main SAP Documentation Types

NwG Project teams for upgrades Nw( Current version: NwG On SAP Service Marketplace at http://service.sap.com/instguides The upgrade guide describes the technical upgrade of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. Nw( Target group: NwG Technology consultants NwG Project teams for upgrades Nw( Current version: NwG On SAP Service Marketplace at http://service.sap.com/instguides Release notes are documents that contain short descriptions of new features in a particular release or changes to existing features since the previous release. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG). Nw( Target group: NwG Consultants NwG Project teams for upgrades Nw( Current version: NwG On SAP Service Marketplace at http://service.sap.com/releasenotes NwG In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

54/56

PUBLIC

2010-12-13

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.