Application Operation Guide SAP™ Supply Network Collaboration Operations Guide

82 Pages·2010·2.97 MB·English

Application Operation Guide
SAP™ Supply Network Collaboration Operations Guide
Release 7.0 (Including SAP Enhancement Package 1)
Target Audience
n Technical Consultants
n System Administrators
n Solution Consultants
n Business Process Owner
n Support Specialist
PUBLIC
Document version: 1.0 ‒ 10/26/2010
SAP AG
Dietmar-Hopp-Allee16
69190Walldorf
Germany
T+49/1805/343434
F+49/1805/343420
www.sap.com
©Copyright2010SAPAG.Allrightsreserved.
SomesoftwareproductsmarketedbySAPAGanditsdistributorscontainproprietarysoftware
componentsofothersoftwarevendors.
Nopartofthispublicationmaybereproducedortransmittedinanyformorforanypurposewithout
theexpresspermissionofSAPAG.Theinformationcontainedhereinmaybechangedwithoutprior
notice.
SomesoftwareproductsmarketedbySAPAGanditsdistributorscontainproprietarysoftware
componentsofothersoftwarevendors.
Microsoft,Windows,Excel,Outlook,andPowerPointareregisteredtrademarksofMicrosoft
Corporation.
IBM,DB2,DB2UniversalDatabase,Systemi,Systemi5,Systemp,Systemp5,Systemx,Systemz,
Systemz10,Systemz9,z10,z9,iSeries,pSeries,xSeries,zSeries,eServer,z/VM,z/OS,i5/OS,S/390,
OS/390,OS/400,AS/400,S/390ParallelEnterpriseServer,PowerVM,PowerArchitecture,POWER6+,
POWER6,POWER5+,POWER5,POWER,OpenPower,PowerPC,BatchPipes,BladeCenter,System
Storage,GPFS,HACMP,RETAIN,DB2Connect,RACF,Redbooks,OS/2,ParallelSysplex,MVS/ESA,
AIX,IntelligentMiner,WebSphere,Netfinity,TivoliandInformixaretrademarksorregistered
trademarksofIBMCorporation.
LinuxistheregisteredtrademarkofLinusTorvaldsintheU.S.andothercountries.
Adobe,theAdobelogo,Acrobat,PostScript,andReaderareeithertrademarksorregisteredtrademarks
ofAdobeSystemsIncorporatedintheUnitedStatesand/orothercountries.
OracleisaregisteredtrademarkofOracleCorporation.
UNIX,X/Open,OSF/1,andMotifareregisteredtrademarksoftheOpenGroup.
Citrix,ICA,ProgramNeighborhood,MetaFrame,WinFrame,VideoFrame,andMultiWinare
trademarksorregisteredtrademarksofCitrixSystems,Inc.
HTML,XML,XHTMLandW3CaretrademarksorregisteredtrademarksofW3C®,WorldWideWeb
Consortium,MassachusettsInstituteofTechnology.
JavaisaregisteredtrademarkofSunMicrosystems,Inc.
JavaScriptisaregisteredtrademarkofSunMicrosystems,Inc.,usedunderlicensefortechnology
inventedandimplementedbyNetscape.
SAP,R/3,xApps,xApp,SAPNetWeaver,Duet,PartnerEdge,ByDesign,SAPBusinessByDesign,and
otherSAPproductsandservicesmentionedhereinaswellastheirrespectivelogosaretrademarksor
registeredtrademarksofSAPAGinGermanyandinseveralothercountriesallovertheworld. All
2/82 PUBLIC 10/26/2010
otherproductandservicenamesmentionedarethetrademarksoftheirrespectivecompanies. Data
containedinthisdocumentservesinformationalpurposesonly. Nationalproductspecifications
mayvary.
Thesematerialsaresubjecttochangewithoutnotice. ThesematerialsareprovidedbySAPAGand
itsaffiliatedcompanies(“SAPGroup”)forinformationalpurposesonly,withoutrepresentationor
warrantyofanykind,andSAPGroupshallnotbeliableforerrorsoromissionswithrespecttothe
materials. TheonlywarrantiesforSAPGroupproductsandservicesarethosethataresetforthinthe
expresswarrantystatementsaccompanyingsuchproductsandservices,ifany. Nothinghereinshould
beconstruedasconstitutinganadditionalwarranty.
Thisdocumentwascreatedusingstylesheet2007-12-10(V7.2)/XSL-FO:V5.1GammaandXSLT
processorSAXON6.5.2fromMichaelKay(http://saxon.sf.net/),XSLTversion1.
Disclaimer
SomecomponentsofthisproductarebasedonJava™. Anycodechangeinthesecomponents
maycauseunpredictableandseveremalfunctionsandisthereforeexpresslyprohibited,asisany
decompilationofthesecomponents.
AnyJava™SourceCodedeliveredwiththisproductisonlytobeusedbySAP’sSupportServices
andmaynotbemodifiedoralteredinanyway.
10/26/2010 PUBLIC 3/82
Typographic Conventions
Example Description
<Example> Anglebracketsindicatethatyoureplacethesewordsorcharacterswith
appropriateentriestomakeentriesinthesystem,forexample,“Enter
your <User Name>”.
Example Arrowsseparatingthepartsofanavigationpath,forexample,menu
Example options
Example Emphasizedwordsorexpressions
Example Wordsorcharactersthatyouenterinthesystemexactlyastheyappear
in the documentation
http://www.sap.coTmextualcross-referencestoaninternetaddress
/example Quicklinksaddedtotheinternetaddressofahomepagetoenablequick
accesstospecificcontentontheWeb
123456 HyperlinktoanSAPNote,forexample,SAPNote123456
Example n Wordsorcharactersquotedfromthescreen. Theseincludefield
labels, screen titles, pushbutton labels, menu names, and menu
options.
n Cross-referencestootherdocumentationorpublishedworks
Example n Outputonthescreenfollowingauseraction,forexample,messages
n Sourcecodeorsyntaxquoteddirectlyfromaprogram
n Fileanddirectorynamesandtheirpaths, namesofvariablesand
parameters,andnamesofinstallation,upgrade,anddatabasetools
EXAMPLE Technical names of system objects. These include report names,
program names, transaction codes, database table names, and key
conceptsofaprogramminglanguagewhentheyaresurroundedby
bodytext,forexample,SELECTandINCLUDE
EXAMPLE Keys on the keyboard
4/82 PUBLIC 10/26/2010
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/instguides.
Thefollowingtableprovidesanoverviewofthemostimportantdocumentchanges.
Version Date Description
1.00 10/26/2010 FirstversionoftheSAPSNC7.0EnhancementPackage1Operations
Guide
10/26/2010 PUBLIC 5/82
Table of Contents
Chapter 1 GettingStarted . . . . . . . . . . . . . . . . . 9
1.1 GlobalDefinitions . . . . . . . . . . . . . . . . 9
1.2 ImportantSAPNotes . . . . . . . . . . . . . . . 10
Chapter 2 TechnicalSystemLandscape . . . . . . . . . . . 13
2.1 Scenario/ComponentMatrix . . . . . . . . . . . . 13
2.2 RelatedDocumentation . . . . . . . . . . . . . . 13
Chapter 3 Monitoring of SAP Supply Network Collaboration (SAP
SNC) . . . . . . . . . . . . . . . . . . . . . 15
3.1 AlertMonitoringwithCCMS . . . . . . . . . . . . 15
3.1.1 CCMSMonitoringInstallationandSetup . . . . . . . 15
3.1.2 Component-SpecificMonitoring . . . . . . . . . . . 17
3.1.2.1 CCMSMonitoringofSAPSNC . . . . . . . . . . . 17
3.1.2.2 CCMSMonitoringofSAPSCMBasis . . . . . . . . . 18
3.1.2.3 CCMSMonitoringoftheInternetGraphicsService . . . . 18
3.1.3 AlertMonitoringofScenarios . . . . . . . . . . . . 19
3.2 Detailed Monitoring and Tools for Problem and Performance
Analysis . . . . . . . . . . . . . . . . . . . . 20
3.2.1 TraceandLogFiles . . . . . . . . . . . . . . . . 20
3.2.1.1 LogObjectsforSAPSupplyNetworkCollaboration . . . . 21
3.2.2 WorkloadMonitors . . . . . . . . . . . . . . . . 26
3.2.3 OtherImportantProblemAnalysisandMonitoringTools . . 27
3.2.3.1 Other Important Problem Analysis and Monitoring Tools: SAP
SNC . . . . . . . . . . . . . . . . . . . . . 27
3.2.4 InterfaceMonitors . . . . . . . . . . . . . . . . 31
3.2.5 DataGrowthandDataArchivingMonitors . . . . . . . 31
6/82 PUBLIC 10/26/2010
3.2.5.1 ArchivingObjectsandDataGrowthinSAPSNC . . . . . 31
3.3 DataConsistency . . . . . . . . . . . . . . . . 33
Chapter 4 ManagementofSAPSNC . . . . . . . . . . . . . 35
4.1 StartingandStopping . . . . . . . . . . . . . . . 35
4.2 SoftwareConfiguration . . . . . . . . . . . . . . 38
4.3 AdministrationTools . . . . . . . . . . . . . . . 39
4.3.1 AdministrationToolsforSAPSupplyNetworkCollaboration 39
4.4 BackupandRestore . . . . . . . . . . . . . . . 39
4.4.1 BackupandRestoreforSAPSCMBasisandSCMBPLUS . . 48
4.4.2 BackupandRestoreforSAPSNC . . . . . . . . . . . 48
4.4.3 BackupandRestoreforSAPInternetGraphicsService(IGS) . 49
4.4.4 BackupandRestore: InformationaboutScenariosusingSAPSNC 50
4.5 ApplicationCopy . . . . . . . . . . . . . . . . 50
4.6 PeriodicTasks . . . . . . . . . . . . . . . . . . 51
4.6.1 ScheduledPeriodicTasks . . . . . . . . . . . . . . 51
4.6.1.1 ScheduledPeriodicTasksforSAPSNC . . . . . . . . . 51
4.6.1.2 Scenario-Specific Scheduled Periodic Tasks: Supplier Managed
Inventory . . . . . . . . . . . . . . . . . . . 55
4.6.1.3 Scenario-SpecificScheduledPeriodicTasks: ReleaseProcessing 57
4.6.1.4 Scenario-Specific Scheduled Periodic Tasks: All Other SNC
Scenarios . . . . . . . . . . . . . . . . . . . 57
4.6.2 RequiredManualPeriodicTasks . . . . . . . . . . . 58
4.7 LoadBalancing . . . . . . . . . . . . . . . . . 60
4.8 UserManagement . . . . . . . . . . . . . . . . 60
4.9 Printing . . . . . . . . . . . . . . . . . . . . 61
Chapter 5 HighAvailability . . . . . . . . . . . . . . . . 63
Chapter 6 SoftwareChangeManagement . . . . . . . . . . 65
6.1 TransportandChangeManagement . . . . . . . . . 66
6.2 DevelopmentRequestsandDevelopmentReleaseManagement 66
6.3 TemplateManagement . . . . . . . . . . . . . . 66
6.4 QualityManagementandTestManagement . . . . . . 66
10/26/2010 PUBLIC 7/82
6.5 SupportPackagesandPatchImplementation . . . . . . 67
6.6 ReleaseandUpgradeManagement . . . . . . . . . . 68
Chapter 7 Troubleshooting . . . . . . . . . . . . . . . . 71
7.1 ToolsforTroubleshooting . . . . . . . . . . . . . 71
7.2 TypicalIssueswiththeWebUserInterface . . . . . . . 72
Chapter 8 SupportDeskManagement . . . . . . . . . . . . 73
8.1 RemoteSupportSetup . . . . . . . . . . . . . . 73
8.2 ProblemMessageHandover . . . . . . . . . . . . . 73
Chapter A Appendix . . . . . . . . . . . . . . . . . . . 75
A.1 Appendix . . . . . . . . . . . . . . . . . . . 75
A.1.1 RelatedGuides . . . . . . . . . . . . . . . . . 75
A.1.2 RelatedInformation . . . . . . . . . . . . . . . 75
Chapter B Reference . . . . . . . . . . . . . . . . . . . 77
B.1 TheMainSAPDocumentationTypes . . . . . . . . . 77
8/82 PUBLIC 10/26/2010
1 Getting Started
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,andrunningyourSAPapplicationsatpeakperformance
24hoursadayhasneverbeenmorevitalforyourbusinesssuccessthannow.
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
alsoprovidesreferencestothedocumentationrequiredforthesetasks, soyouwill
sometimesalsoneedotherguidessuchastheMasterGuideorSAPLibrary.
Note
You can run SAP Supply Network Collaboration (SAP SNC) together with SAP
Event Management or SAP Collaboration Folders (cFolders) if you have the
appropriate licenses. System administration tasks for SAP Event Management
are not covered in this guide. For more information about the various tasks and
toolsthatyoucancarryoutforSAPEventManagement,seetheOperationsGuide
for SAP Event Management and SAP cFolders on SAP Service Marketplace at
http://service.sap.com/instguides.
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. It represents a market view on groups of related
10/26/2010 PUBLIC 9/82
1 Getting Started
1.2 Important SAP Notes
businessscenarios. ThedeliveryofanapplicationcontainsSAPcomponentsthatare
essentialforimplementingallapplication-relatedbusinessscenarios,processes,and
functions. Theimplementationknowledgeisallocatedtogetherwithanapplication.
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 (SAP ERP, SAP SCM, or others) for each cycle and possibly other
third-party systems. A business scenario is a unit which can be implemented
separatelyandreflectsthecustomer’sprospectivecourseofbusiness.
Component:
A component is the smallest individual unit considered within the Solution
Development Lifecycle; components are separately produced, delivered, installed
and maintained.
1.2 Important SAP Notes
Caution
CheckregularlyforupdatesavailablefortheApplicationOperationsGuide.
Important SAP Notes
SAP Note Number Title Comment
605795 Windows Terminal Server -
connection in remote
support
100740 Setting up a PCanywhere -
connection in the SAP
frontend
10/82 PUBLIC 10/26/2010