gts71 operationsguide en v4

SAP Global Trade Services

Release 7.1

Document Version 4.0 – February 21, 2007

Operation Guide

© Copyright 2006 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. Microsoft®, WINDOWS®, Outlook®, and PowerPoint® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix ® are trademarks of IBM Corporation in USA 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 of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MaxDB is a trademark of MySQL AB, Sweden. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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. Documentation on the SAP Service Marketplace You can find this documentation under the address service.sap.com/instguides.

SAP AG Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Typographic Conventions Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Operation Guide for SAP Global Trade Services

4 February 2007

Contents 1 Getting Started ........................................................................................6

1.1 Global Definitions...........................................................................7 1.2 Important SAP Notes......................................................................8 1.3 History of Changes.........................................................................9

2 Technical System Landscape ..............................................................10 2.1 Graphic Landscape Description..................................................10 2.2 Scenario/Component Matrix ........................................................11 2.3 Related Documentation................................................................12

3 Monitoring of SAP Global Trade Services ..........................................13 3.1 Alert Monitoring with CCMS ........................................................13

3.1.1 Central System Monitoring Architecture................................14 3.1.1.1 System Groups.......................................................................14

3.1.2 Component Alert Monitoring...................................................15 3.1.2.1 SAP NetWeaver 2004s............................................................15 3.1.2.2 SAP GTS 7.1 (SLL-LEG 7.10) .................................................16

3.2 Detailed Monitoring, Problem and Performance Analysis Tools ........................................................................................................16

3.2.1 Component Specific Analysis Tools for SAP SLL-LEG 7.10 ... ...................................................................................................16 3.2.2 Scenario Problem Analysis Tools...........................................18

3.2.2.1 Interfaces ................................................................................18 3.2.2.2 Data Archiving Monitors ........................................................18 3.2.2.3 Specific Problem Analysis Tools ..........................................19 3.2.2.4 Distributed Statistical Records .............................................19 3.2.2.5 Business Packages................................................................19

4 Management of SAP Global Trade Services .......................................20 4.1 Administration Tools of Software Components.........................20 4.2 Starting and Stopping ..................................................................20 4.3 Backup/Restore and Recovery....................................................20 4.4 System Copy.................................................................................21 4.5 Periodical Tasks ...........................................................................22

4.5.1 Scheduled Periodical Tasks for SAP NetWeaver 2004s........22 4.5.2 Required Manual Periodical Tasks for SAP Global Trade Services .................................................................................................22

5 High Availability ....................................................................................23 6 Software Change Management ............................................................24

6.1 Transport and Change Management...........................................24 6.2 Development Requests and Development Release Management ............................................................................................24 6.3 Support Packages and SAP Notes Implementation ..................25

Operation Guide for SAP Global Trade Services

February 2007 5

7 Troubleshooting....................................................................................26 8 Services for SAP Global Trade Services.............................................27 9 Appendix................................................................................................28

9.1 Categories of System Components for Backup and Restore...28 9.2 Related Guides..............................................................................28


6 February 2007

1 Getting Started

This guide does not replace the daily operations handbook that we recommend customers create for their specific production operations.

About this Guide

Designing, implementing, and running your mySAP solution 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 mySAP solutions and keeping them up and running optimally. It contains specific information for various tasks, and lists the tools that you can use to carry them out. It also refers to documentation required for these tasks. You can use this guide only in connection with other guides such as the Master Guide, SAP NetWeaver Technical Operations Manual, and the SAP Library.

The following NetWeaver documentation is specially important and must be used in conjunction with this Operations Guide for SAP Global Trade Services (SAP GTS) as its covers only topics specific to SAP GTS, not general NetWeaver topics:

Document Found At:

Technical Operations Manual for SAP NetWeaver

service.sap.com/netweaver → SAP NetWeaver 2004s - Release-Specific Information → Documentation → Technical Operations Manual

Monitoring Setup Guide for SAP NetWeaver

service.sap.com/netweaver → SAP NetWeaver 2004s - Release-Specific Information → Documentation → Monitoring and Operations → Monitoring

SAP NetWeaver Security Guide

help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → Administrator’s Guide → SAP NetWeaver Security Guide

Solution Life Cycle Management by Key Capability

help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library →SAP NetWeaver by Key Capability → Solution Life Cycle Management

Target Groups

• Technical Consultants

• System Administrators

• Solution Consultants

• Business Process Owner

• Support Specialist


February 2007 7

1.1 Global Definitions mySAP Solution:

A mySAP solution represents a market view of groups of related business scenarios. The delivery of a solution contains mySAP components which are essential for implementing all solution-related business scenarios, processes, and functions. Implementation knowledge ìs included with each solution.

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 with other business partners. From a technical point of view, a business scenario needs at least one mySAP application component (SAP R/3, SAP APO, or others) for each cycle and possibly other third-party systems. A business scenario is a unit which can be implemented separately and reflects the customer’s 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.


8 February 2007

1.2 Important SAP Notes

Check regularly for SAP Notes available for the Operations Guide.

Important SAP Notes

SAP Note Number Title

19227 Get the latest saposcol

209834 CCMS agent technology


February 2007 9

1.3 History of Changes

Make sure you use the current version of the Operation Guide.

The current version of the Operation Guide is at service.sap.com/instguides on SAP Service Marketplace.

The following table provides an overview of the most important changes in prior versions.

Version Important Changes

1.0 First version of document

2.0 Enhanced references to related documentation

3.0 Specified links

4.0 Formally revised


10 February 2007

2 Technical System Landscape 2.1 Graphic Landscape Description

mySAP ERP 2005SAP GTS 7.1

NW2004s

SAP Enterprise PortalPresentation Layer

DBDB

SAPGUI 6.40BSP Web UI Webdynpro

XI ContentSLL-LEG 7.1

SAPGUI 6.40

NW2004s

SAP AP 7.00SAP SLL-LEG 7.10

SAP_APPL 6.00 SP06+

DB

SAP PI Basis 2005_1_700SAP Basis 7.00 SP06+

SAP ABA 7.00 SP06+SAP BW 7.00 BI Content

7.0.2

ABAP Stack JavaStack

requiredfor

ADS

SAP GTS 7.1 Architecture with mySAP ERP 2005

SAP GTS 7.1 Architecture with mySAP ERP 2004

mySAP ERP 2004SAP GTS 7.1

SAP Enterprise PortalPresentation Layer

DBDB

SAPGUI 6.40BSP Web UI Webdynpro

XI ContentSLL-LEG 7.1

SAPGUI 6.40

SAP AP 7.00SAP SLL-LEG 7.10

DB

SAP_APPL 5.00SAP PI 2004_1_500 SP13+

NW2004s

NW2004s

SAP PI Basis 2005_1_700SAP Basis 7.00 SP06+

SAP ABA 7.00 SP06+SAP BW 7.00 BI Content

7.0.2

ABAP Stack JavaStack

requiredfor

ADS


February 2007 11

2.2 Scenario/Component Matrix SAP GTS Business Scenarios Key: X = mandatory (X) = optional

Software Component

SAP Compliance Management

SAP Customs Management

SAP Risk Management - Preference Processing

SAP Risk Management - Letter of Credit

SAP Risk Management - Restitution Handling

SAP Electronic Compliance Reporting

SLL-LEG 7.10 X X X X X X

SAP_AP 700* X X X X X X

SAP NetWeaver ABAP Stack

X X X X X X

SAP NetWeaver Java Stack

X X X X X

SAP NetWeaver Business Intelligence **

(X) (X) (X) (X) (X)

SAP NetWeaver Process Integration (PI) – formerly known as SAP Exchange Infrastructure (XI)

(X) (X)

Business Package for Classification

(X) (X) (X) (X) (X)

Business Package for Compliance Management

(X)

Business Package for Preference Processing

(X)


12 February 2007

2.3 Related Documentation The following table lists where you can find more information about the technical system landscape.

Topic Guide/Tool Quick Link on SAP Service Marketplace (service.sap.com) or Path

Application-specific Components such as

SAP Compliance Management SAP Customs Management SAP Risk Management

SAP Electronic Compliance Reporting

Master Guide instguides

Technology Components such as SAP NetWeaver Application Server

Master Guide instguides

Sizing Quick Sizer Tool sizing

Technical Configuration Technical Infrastructure Guide ti

Scalability Technical Infrastructure Guide ti

High Availability Technical Infrastructure Guide ti

Security Technical Infrastructure Guide ti

security

Operations of NetWeaver usage types

Technical Operations Manual for SAP NetWeaver

service.sap.com/netweaver → SAP NetWeaver 2004s - Release-Specific Information → Documentation → Technical Operations Manual

Monitoring with CCMS SAP NetWeaver Library help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library →SAP NetWeaver by Key Capability → Solution Life Cycle Management → Solution Monitoring → Monitoring in the CCMS


February 2007 13

3 Monitoring of SAP Global Trade Services

Monitoring of SAP NetWeaver is an essential task within the management of mySAP solutions, including SAP GTS. The aim of this section is to provide information and documentation required to configure the Computing Center Management System (CCMS).

For more information on the underlying technology, see the SAP NetWeaver Technical Operations Manual, particularly the section on Monitoring, on SAP Service Marketplace at service.sap.com/netweaver → SAP NetWeaver 2004s Release-Specific Information → Documentation → Technical Operations Manual.

As SAP GTS 7.1 is powered by SAP NetWeaver 2004s, we recommend that you setup the Monitoring Infrastructure as described in the Monitoring Setup Guide for SAP NetWeaver (MSG) at service.sap.com/netweaver → SAP NetWeaver 2004s - Release-Specific Information → Documentation → Monitoring and Operations → Monitoring.

The monitoring setup described in the MSG is the foundation for the following sections and contains all the information relevant to monitoring the SAP NetWeaver components used in SAP GTS 7.1. Proficient knowledge in system monitoring and basic knowledge in SAP NetWeaver is required to compose the user-defined monitors recommended within this guide.

You can retain additional information about Monitoring in SAP NetWeaver Library at help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library →SAP NetWeaver by Key Capability → Solution Life Cycle Management → Solution Monitoring → Monitoring in the CCMS

To build the necessary skills in system monitoring, we recommend the SAP Course ADM106 – Advanced System. For more information on education and workshops, see the information available on SAP Service Marketplace at service.sap.com/monitoring → System Monitoring and Alert Management → Education & Workshops.

3.1 Alert Monitoring with CCMS Proactive, automatic monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides you with the infrastructure and recommendations on how to set up your alert monitoring in CCMS to recognize critical situations for SAP GTS as quickly as possible. In order to enable the auto-alert mechanism of CCMS, see SAP Note 617547. SAP GTS uses the monitoring functions of SAP NetWeaver Application Server ABAP 7.00 which is part of SAP NetWeaver 2004s.

For more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) at service.sap.com/netweaver → SAP NetWeaver 2004s - Release-Specific Information → Documentation → Monitoring and Operations → Monitoring.

To configure alert monitoring with CCMS for SAP GTS 7.1, you must set up a Central Monitoring System (CEN) and connect the components for SAP GTS to this CEN system. For a list of these components and the business scenarios for which they are relevant, see section 2.2 Scenario/Component Matrix.


14 February 2007

Since SAP GTS 7.1 utilizes the complete SAP NetWeaver 2004s stack, you have to apply the Monitoring Setup Guide for SAP NetWeaver (MSG) to the component of SAP GTS, first. In addition to this, you can define special monitors for SAP GTS in the CEN System’s CCMS.

In addition to required monitoring of each component, some additional monitoring objects are designed to monitor cross-component communication and other scenario-specific critical situations.

3.1.1 Central System Monitoring Architecture We recommend that you integrate monitoring SAP GTS 7.1 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 WAS (ABAP) 7.00 SP level 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 help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Solution Life Cycle Management → Solution Monitoring → System Monitoring with CCMS.

The CEN system can be connected to the SAP Soltion Manager 3.2 if the monitoring scenario is configured and used. For more information on SAP Solution Manager, see the information available on SAP Service Marketplace at service.sap.com/solutionmanager.

Systems and applications can be monitored with SAP Agent Technology. There are three different agents available for System Monitoring:

• SAPCCM4X for SAP NetWeaver Application Server (ABAP)

• SAPCCMSR for SAP NetWeaver Application Server (Java), Search & Classification, IPC

• 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 on CCMS agents, see the documentation available on SAP Service Marketplace at service.sap.com/monitoring.

3.1.1.1 System Groups Before creating new monitors for SAP GTS, 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 call the individual functions in the table, choose CCMS → Configuration → Alert Monitor, or go to transaction RZ21. Then choose Technical Infrastructure → Configure Central System → Maintain System Groups, and 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 help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Solution Life Cycle Management by Key Capability → Solution Monitoring →


February 2007 15

Monitoring in the CCMS → The Alert Monitor → Customizing the Alert Monitor → System Groups in the Altert Monitor.

The following table and graphic provide an example of how you can create your system groups.

System Group System

GTS_Systems SAP SLL-LEG 7.10

J2EE_Systems LACWPS SAP WAS 7.00

ExchangeInfrastructure_Systems SAP Exchange Infrastructure

Properties Variant You should also create a properties variant (for example, GTS71_Default) to save your customizing and configuration during the setup of the CEN.

A monitoring properties variant contains the following data:

• Settings for properties

• Method assignments for monitoring tree elements (MTE)

• MTE classes and attribute groups.

Every change made to these settings is assigned to a properties variant.

3.1.2 Component Alert Monitoring SAP GTS 7.1 is based on component SLL-LEG 7.10 for which you can set up monitors using CCMS. This section gives you an overview how SAP GTS could be monitored.

For information on editing or creating monitors and monitor sets, see the Monitoring Setup Guide for SAP NetWeaver (MSG).

3.1.2.1 SAP NetWeaver 2004s SAP NetWeaver 2004s is the integration and application platform for SAP GTS 7.1 with its component SLL-LEG 7.10. Therefore the following SAP NetWeaver components must be integrated into the monitoring infrastructure:

• SAP NetWeaver Application Server (ABAP) 7.00 [for SAP GTS 7.1 and its component SLL-LEG 7.10]

• SAP NetWeaver Application Server (Java) 7.00 [for Adobe Document Server, ADS]

• SAP NetWeaver Usage Type Process Integration (PI)

• SAP NetWeaver Enterprise Portal 7.0

• SAP NetWeaver Business Information Warehouse 7.0 (BI)

For more information and detailed procedures, see the Monitoring Setup Guide for SAP NetWeaver (MSG) and the NetWeaver 2004s Technical Operations Manual.


16 February 2007

3.1.2.2 SAP GTS 7.1 (SLL-LEG 7.10) The component SLL-LEG 7.10 for SAP GTS 7.1 is based on SAP NetWeaver Application Server for ABAP 7.00. You can find information about monitoring the SAP NetWeaver AS for ABAP in the Monitoring Setup Guide for SAP NetWeaver (MSG) and the NetWeaver 2004s Technical Operations Manual.

Prerequisites • Your SAP GTS 7.1 is connected to the CEN and registered as a remote system.

• The SAPCCM4X agent is registered and running for the instance of SAP GTS.

What to Monitor Because your SAP GTS 7.1 is running on SAP NetWeaver Application Server for ABAP 7.00, the primary failure points are within the technical infrastructure.

You can set up additional monitors for specific processes in SAP GTS according to your needs, for example, IDoc monitoring in the communication processes.

3.1.3 Scenario Alert Monitoring An addition to the component alert monitoring for all scenarios of SAP GTS 7.1 monitoring of remote function calls (RFCs) is required.

The scenarios of SAP GTS 7.1 use standard monitoring functions proviced 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 help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Solution Life Cycle Management → Solution Monitoring → System Monitoring with CCMS → The Alert Monitor → Special Monitoring Functions of the Alert Monitor.

The communication process for imports and exports with SAP Customs Management of SAP GTS 7.1 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 help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Application Platform by Key Capability → Connectivity → Components of SAP Communication Technology → Classical SAP Technologies (ABAP) → IDoc Interface/ALE → Administering ALE Functions → Monitoring Message Exchange.

3.2 Detailed Monitoring, Problem and Performance Analysis Tools

3.2.1 Component Specific Analysis Tools for SAP SLL-LEG 7.10

SAP GTS 7.1 with its component SLL-LEG 7.10 is technically based on SAP NetWeaver Application Server Release 7.00.

For information about technical problem analysis (for example, for database, operating system, workload analysis, and so forth), refer to the NetWeaver 2004s Technical Operations Manual.

The Operations Guide for SAP GTS 7.1 covers only differences and additional information specific to the SAP GTS.


February 2007 17

3.2.1.1 Logging and Tracing SAP GTS 7.1 application-specific logging information is written into the application log. The application logs for all scenarios of SAP GTS 7.1 are integrated into the relevant functions to ensure the context information for the application log 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. SAP GTS provides application logs for the following objects:

• /SAPSLL/API_INBOUND - API Inbound Processing

• /SAPSLL/BOM - Bill of Materials (Preference)

• /SAPSLL/BOP - Bill of Product (Restitution)

• /SAPSLL/BP - Business Partner

• /SAPSLL/CUHD - Customs Shipments and Customs Declarations

• /SAPSLL/CUHD_ARCHIVE - Customs Document: Archiving

• /SAPSLL/CUHD_MAP - Mapping of API Interface to Customs Document

• /SAPSLL/CUHD_SYNCH - Synchronization of Document with Feeder System

• /SAPSLL/CUPED - Supplementary Customs Declaration

• /SAPSLL/CUPED_ARCH - Supplementary Customs Declaration: Archiving

• /SAPSLL/CUST - Legal Services

• /SAPSLL/ECC - Electronic Communication

• /SAPSLL/GEN - Generation

• /SAPSLL/IVM - Inventory Management

• /SAPSLL/KMAT - Configurable Materials

• /SAPSLL/LCLIC - Legal Control: License

• /SAPSLL/LLNS - Tariff Number System

• /SAPSLL/PR - Customs Product

• /SAPSLL/PREF - Preference

• /SAPSLL/RES - Restitution

• /SAPSLL/SPL_ARCHIVE - Archiving of the Sanctioned Party List Screening Data

• /SAPSLL/TLC - Customs Value

• /SAPSLL/TSPL - Master Data for Sanctioned Party List Screening

• /SAPSLL/WL - Logistics Integration Worklist

• /SAPSLL/WL_ARCHIVE - Archiving for Logistics Integration Worklist

For more information about the process-integrated application log, see the relevant process and functional documentation for SAP GTS scenarios in SAP Library at help.sap.com → Documentation → xApps → SAP Global Trade Services.

SAP GTS 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 help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP


18 February 2007

NetWeaver → Administration of SAP NetWeaver Systems → AS ABAP (Application Server for ABAP) → Monitoring.

3.2.2 Scenario Problem Analysis Tools The following information applies to all business scenarios of SAP GTS 7.1.

3.2.2.1 Interfaces 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 (MSG) and the NetWeaver 2004s Technical Operations Manual.

3.2.2.2 Data Archiving Monitors You can monitor archiving of objects (documents, audit trails, etc.) independently of SAP GTS, for example in any SAP R/3 or mySAP ERP system. You can access the Archive Information System (AS) for this in transaction SARA and 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)

NetWeaver 2004s Technical Operations Manual at help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP Library → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → General Administration Tasks

→ Data Archiving and

→ Database Administration

The following table lists the fastest growing tables for SAP GTS 7.1. If you integrated your processes into the logistics processes of mySAP Enterprise Resource Planning (mySAP ERP) as your feeder system, you should refer to the listed tables below.

Component Tables

SLL-LEG 7.10 • CDPOS • CDHDR • BALHDR • /SAPSLL/CORREF • /SAPSLL/CUIT • /SAPSLL/CUPEDRI • /SAPSLL/CUSWLD • /SAPSLL/CUSWLF • /SAPSLL/CUSWLQ • /SAPSLL/PRPREF

Feeder System • /SAPSLL/OBJIDX

• /SAPSLL/SSF


February 2007 19

For more information on archiving objects, see the following documentation in SAP Library at help.sap.com → Documentation → SAP xApps → SAP Global Trade Services → System Administration → Archiving Data.

For more information on the periodical tasks required to manage data growth (for example, reorganization of temporary data), refer to section 4.5 Periodical Tasks in this guide.

3.2.2.3 Specific Problem Analysis Tools SAP GTS 7.1 uses the following monitoring functions provided by SAP NetWeaver Application Server ABAP 7.00 in SAP NetWeaver 2004s which are particularly vital for the processes between SAP GTS and the feeder systems.

IDoc Monitoring

The communication to Customs authorities is a vital process for your business. Therefore monitoring the inbound and outbound IDoc processing is important. You can access the IDoc monitoring by using transaction code /SAPSLL/MENU_LEGAL to access the area menu for SAP GTS and choosing System Administration → System Monitoring → IDoc Monitoring. Here you can monitor the following:

• IDoc List Display

You can display all the inbound and outbound IDocs

• IDoc Search

You can search for specific IDocs

• IDoc Statistics

You can call inbound and outbound IDocs that were sent and received during a specific timeframe. You can also see which errors occurred in the IDoc processing.

• 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 help.sap.com → Documentation → xApps → SAP Global Trade Services → System Administration → System Monitoring → Communication between SAP GTS, EDI Converter, and Customs Authorities.

Transactional Remote Function Call Monitoring

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.

3.2.2.4 Distributed Statistical Records For more information on the motivation behind distributed statistical records and how to define and use them, see section Technology in the Monitoring Setup Guide for SAP NetWeaver (MSG) in SAP Service Marketplace at service.sap.com/instguides → SAP NetWeaver → Release 2004s → Operations → Monitoring.

3.2.2.5 Business Packages For more information regarding the analysis and monitoring of Business Packages and SAP Enterprise Portal, see the NetWeaver 2004s Technical Operations Manual.

For information about how to monitor the cache upload of the Business Package for Supplier Collaboration, see SAP Note 749231 at service.sap.com/notes.


20 February 2007

4 Management of SAP Global Trade Services

SAP provides you with an infrastructure that helps your technical support consultants and system administrators to manage all SAP components effectively and carry out all tasks related to middleware technology.

This infrastructure provides:

• A central interface for managing administrative middleware tasks

• Improved problem resolution processes for the entire solution

• Standardized administration of user profiles

For more information about the underlying technology, see the NetWeaver 2004s Technical Operations Manual.

4.1 Administration Tools of Software Components

SAP GTS 7.1 an its component SLL-LEG 7.10 is technically based on SAP NetWeaver. For information on the relevant administration tools, see the NetWeaver 2004s Technical Operations Manual.

4.2 Starting and Stopping SAP GTS 7.1 is an Add-On and therefore complies with the Start and Stop Sequence and Tools of SAP NetWeaver 2004s that SAP GTS is installed on.

For more information, see Starting and Stopping the System in the Technical Operations Manual for SAP NetWeaver in SAP Library at help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → Administration of SAP NetWeaver Systems → AS ABAP (Application Server for ABAP) → Management.

4.3 Backup/Restore and Recovery To ensure that you can restore and recover your system in case of failure, you should back up your system landscape regularly.

The backup and restore procedure for SAP GTS 7.1 as Add-On is identical to the one of SAP NetWeaver 2004s that SAP GTS is installed on.

For more information, see Backup and Recovery in the Technical Operations Manual for SAP NetWeaver in SAP Library at help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → Administration of SAP NetWeaver Systems → AS ABAP (Application Server for ABAP) → Management.

You can also refer to the section High Availability in the Technical Operations Manual for SAP NetWeaver in SAP Library at help.sap.com → Documentation → SAP NetWeaver → SAP


February 2007 21

NetWeaver 2004s → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → General Administration Tasks.

4.4 System Copy For more information on prerequisites, procedures, and limitations for copying components of SAP GTS, see section System Copy in the Technical Operations Manual for SAP NetWeaver in SAP Library at help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → General Administration Tasks or access the document Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 2004s directly on SAP Service Marketplace at service.sap.com/instguides → SAP NetWeaver Release 2004s Installation.


22 February 2007

4.5 Periodical Tasks 4.5.1 Scheduled Periodical Tasks for SAP

NetWeaver 2004s For more information on standard background jobs and periodical tasks for SAP NetWeaver components, see the NetWeaver 2004s Technical Operations Manual.

4.5.2 Required Manual Periodical Tasks for SAP

Global Trade Services SAP Global Trade Services creates log files that 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 promply and to react accordingly.

Also, the following application-specific tasks are relevant for execution of background jobs or require execution in background jobs:

• In the feeder system:

• Check change pointers for master data and transfer changed data from feeder system to SAP GTS

• Creditors – relevant for all scenarios of SAP GTS 7.1

• Debitors – relevant for all scenarios of SAP GTS 7.1

• Material master – relevant for all scenarios of SAP GTS 7.1

• Bill of materials – relevant for Trade Preference Processing in SAP Risk Management of SAP GTS 7.1

• Transfer duty-paid stock for customs warehousing – relevant for Imports and Exports with SAP Customs Management of SAP GTS 7.1

For more information about the periodic tasks in the feeder system for SAP GTS, see section Data Replication in the Scenario Configuration Guides in SAP Service Marketplace at service.sap.com/swdc → Download → Installation and Upgrades → Entry by Application Group → SAP Application Components → SAP Global Trade Services (GTS) → SAP GTS 7.1 → Installation and Upgrade.

• In SAP GTS 7.1:

• Distribute Product Data to Feeder System for Special Customs Procedures – relevant for Imports and Exports with SAP Customs Management of SAP GTS 7.1

For more information, see the documentation in SAP Library at help.sap.com → SAP xApps → SAP Global Trade Services → SAP Customs Management → Master Data.

• Further functions can also be scheduled for background processing but do not require periodical execution. The relevant functional descriptions contain references if background jobs execution of the programs are possible.

For more information, see the documentation in SAP Library at help.sap.com → SAP xApps → SAP Global Trade Services → System Administration → System Monitoring.


February 2007 23

5 High Availability The processes of SAP GTS are based master and transaction data from one or more feeder systems. If a failure on SAP GTS’ component SLL-LEG occurs, all business processes in the feeder system based on action in SAP GTS cannot be performed.

To avoid any inconveniences SAP GTS provides a recovery scenario. If action from SAP GTS is required by the feeder system at a time when SAP GTS is not available, you can configure your system in such a way that

• Either all subsequent processes are blocked until SAP GTS is available again and can perform the tasks needed before continuing the processes in the feeder system, or

• All subsequent processes can be performed without getting a response from SAP GTS and SAP GTS will perform the tasks once the system becomes available again.

• Alternatively, you can allow all subsequent processes to be performed without any checksIf SAP GTS is not available.

We recommend you also refer to the following documentation: • BC SAP High Availability NW 2004s 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.

You can find this document on SAP Service Marketplace at service.sap.com/ha → Media Library→ Documentation → HA Documentation. • Switchover You can find the switchover documentation for SAP Netweaver 2004s on SAP Service Marketplace at service.sap.com/ha → News → Nov 2005.

For information on specific switchover products, contact your hardware and switchover software vendor.

If you have any questions regarding the integration of SAP NetWeaver Application Server with a specific switchover product, contact the Competence Centers of SAP’s hardware partners in Walldorf, Germany.


24 February 2007

6 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 GTS 7.1 and its component SLL-LEG 7.10 are based on SAP NetWeaver Application Server ABAP 7.00 of SAP NetWeaver 2004s. You can find information on the Software Change Management in the according document section for SAP NetWeaver.

The following topics will be covered in the SAP NetWeaver document:

• Transport and Change Management - Enables and secures the distribution of software changes from the development environment to the quality assurance and production environment.

• Development Request and Development Release Management - Enables customer-specific maintenance procedures and open integration with third-party products.

• Template Management - Enables and secures the rollout of global templates, including localizations.

• Quality Management and Test Management - Reduce the time, cost, and risk associated with software changes.

• Support Packages and SAP Notes Implementation - Provide standardized software distribution and maintenance procedures.

• Release and Upgrade Management - Reduces time, cost, and risk associated with upgrades.

6.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 the NetWeaver 2004s Technical Operations Manual.

6.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.



February 2007 25

6.3 Support Packages and SAP Notes Implementation

Information on the Support Packages available for SAP GTS 7.1 can be found on SAP Service Marketplace at service.sap.com/ocs-schedules.

Support Packages for components based on the SAP NetWeaver Application Server ABAP 7.00 are applied using the Support Package Manager.


Detailed Instructions on applying a Support Package Stack to SAP NetWeaver are given in the Support Package Stack Guide for SAP NetWeaver 2004s.

For more information, see the documentation on SAP Service Marketplace at service.sap.com/netweaver → SAP NetWeaver 2004s – Release Specific Information → Documentation → Maintenance → Support Package Stack Guide.

SAP Notes that require code changes for components based on the SAP NetWeaver Application Server ABAP 7.00 can be applied using the SAP Note Assistant.

For more information, see the documentation in SAP Library at help.sap.com under Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Solution Life Cycle Management by Key Capability → Software Life Cycle Management → Software Maintenance → Note Assistant.


26 February 2007

7 Troubleshooting In case of problems, refer to the troubleshooting guide for SAP NetWeaver Application Server. For more information, see SAP Library at help.sap.com → Documentation → SAP NetWeaver → SAP NetWeaver 2004s → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → General Administration Tasks → Troubleshooting for SAP Web Application Server.

The SAP NetWeaver Problem Analysis Guide (PAG) contains the following problem analysis scenarios for the various components of the usage type Application Server:

• Security Problem Analysis Scenarios

• Adobe Document Services Problem Analysis Scenarios

• System Landscape Directory Problem Analysis Scenarios

• Process Monitoring Infrastructure Problem Analysis Scenarios

• SAP Knowledge Warehouse Problem Analysis Scenarios

• Web AS Java

• Change Management Server Problem Analysis Scenarios

• J2EE Engine Problem Analysis Scenarios

• Web Dynpro Java (ESS Scenario) Problem Analysis Scenarios

• Design Time Repository Problem Analysis Scenarios

• SAP Java Connector Problem Analysis Scenarios

If you encounter specific problems in executing processes you need to check the logs in the feeder system and in SAP GTS.

In addition, a troubleshooting section for the communication process between SAP GTS, the converter system and the Customs authorities when processing imports and exports with SAP Customs Management is included in SAP Library for SAP GTS. For more information, see help.sap.com → SAP xApps → SAP Global Trade Services → System Administration for SAP Global Trade Services → System Monitoring.


February 2007 27

8 Services for SAP Global Trade Services SAP GTS offers, for example, the following safeguarding and solution management services to optimize you implementation project:

• 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 SAP recommends you to take for your solution as well as an action plan, which explains how and when these measures can be implemented.

• GoLive Check

The SAP GoingLive Check helps you manage technical risk to ensure optimal performance, availability and maintainability of SAP GTS. 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.

• 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.

• 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 GTS in terms of availability, performance, maintainability and data consistency.

• Volume Test Optimization (VTO) package

With this packacke, 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.

For more information about these services, see SAP Safeguarding on SAP Service Marketplace at service.sap.com/safeguarding.


28 February 2007

9 Appendix 9.1 Categories of System Components for

Backup and Restore Categories of System Components

Category Properties Suggested Methods for Backup and Restore

Examples

I Original application data, standalone system, based on SAP NetWeaver Application Server ABAP 7.00

Data:

- Database and log backup, application log backup (such as job logs in file system)

- Backup of software, configuration, log files

Standalone SAP

R/3

II Original application data, data exchange with other systems, based on SAP NetWeaver Application Server ABAP 7.00

Data:

- Database and log backup, application log backup (such as job logs in file system), data consistency with other systems must be considered

- Backup of software, configuration, log files

SAP R/3

SAP CRM

SAP APO

SAP BW

9.2 Related Guides You can find more information about installation and configuration in the Master Guide.

The following table contains links to information relating to the Operation Guide.

Content Quick Link to the SAP Service Marketplace (service.sap.com)

Master Guide service.sap.com/swdc → Download → Installation and Upgrades → Entry by Application Group → SAP Application Components → SAP Global Trade Services (GTS) → SAP GTS <Release> → Installation and Upgrade.

Related SAP Notes notes

Released platforms platforms

Network security securityguide

network

SAP Solution Manager solutionmanager

gts71 operationsguide en v4

Documents