Date post: | 11-Feb-2016 |
Category: |
Documents |
Upload: | andy-zhang |
View: | 18 times |
Download: | 0 times |
Application Operations GuideDocument Version: 1.0 – 2013-09-30
CUSTOMER
SAP Public Budget Formulation 8.1
2CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Document History
Document History
Version Date Change
1.0 2013-09-30 Initial release
SAP Public Budget Formulation 8.1Table of Contents
CUSTOMER© 2013 SAP AG. All Rights Reserved. 3
Table of Contents
1 Getting Started ........................................................................................................................................ 51.1 About This Guide ...................................................................................................................................................... 51.2 Global Definitions ..................................................................................................................................................... 51.3 Important SAP Notes...............................................................................................................................................6
2 Technical System Landscape .................................................................................................................. 72.1 Scenario/Component Matrix .................................................................................................................................. 72.2 Related Documentation .......................................................................................................................................... 7
3 Monitoring of SAP Public Budget Formulation 8.1 ................................................................................ 83.1 Alert Monitoring .......................................................................................................................................................8
3.1.1 Monitoring Installation and Setup ..........................................................................................................83.1.2 Component Specific Monitoring ............................................................................................................8
3.2 Detailed Monitoring and Tools for Problem and Performance Analysis .............................................................93.2.1 Trace and Log Files..................................................................................................................................9
4 Management of SAP Public Budget Formulation 8.1 ........................................................................... 134.1 Software Configuration ......................................................................................................................................... 134.2 Administration Tools ............................................................................................................................................. 134.3 Backup and Restore .............................................................................................................................................. 134.4 Applicaiton Copy .................................................................................................................................................... 144.5 Periodic Tasks ........................................................................................................................................................ 14
4.5.1 Scheduled Periodic Tasks .................................................................................................................... 144.5.2 Required Manual Periodic Tasks .......................................................................................................... 14
4.6 Load Balancing ....................................................................................................................................................... 144.7 User Management ................................................................................................................................................. 15
5 High Availability ..................................................................................................................................... 16
6 Software Change Management ..............................................................................................................176.1 Transport and Change Management ................................................................................................................... 176.2 Development Requests and Development Release Management – ABAP ...................................................... 186.3 Development Requests and Development Release Management – Java ........................................................ 186.4 Template Management ......................................................................................................................................... 186.5 Quality Management and Test Management ...................................................................................................... 186.6 Support Packages and Patch Implementation ................................................................................................... 19
6.6.1 ABAP ....................................................................................................................................................... 196.6.2 Java ......................................................................................................................................................... 19
7 Troubleshooting .................................................................................................................................... 20
8 Support Desk Management ................................................................................................................... 218.1 Remote Support Setup.......................................................................................................................................... 218.2 Problem Message Handover ................................................................................................................................. 21
4CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Table of Contents
9 Appendix ................................................................................................................................................. 229.1 Related Guides ...................................................................................................................................................... 229.2 Related Information .............................................................................................................................................. 22
SAP Public Budget Formulation 8.1Getting Started
CUSTOMER© 2013 SAP AG. All Rights Reserved. 5
1 Getting Started
1.1 About This Guide
CautionThis guide does not replace the daily operations handbook that we recommend customers to create fortheir specific production operations.
Designing, implementing, and running your SAP applications at peak performance 24 hours a day has never beenmore vital for your business success than now.
This guide provides a starting point for managing your SAP applications and maintaining and running themoptimally. 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, meaning that you willsometimes also need other guides such as the Master Guide, Technical Infrastructure Guide, and SAP Library.
Target Groups
Technical consultants
System administrators
Solution consultants
Business process owner
Support specialist
1.2 Global Definitions
SAP Application
An SAP application is an SAP software solution that serves a specific business area such as ERP, CRM, PLM, SRM,and SCM.
Business Scenario
From a microeconomic perspective, a business scenario is a cycle that consists of several differentinterconnected logical processes in time. Typically, a business scenario includes several company departmentsand involves other business partners. From a technical point of view, a business scenario needs at least one SAPapplication (SAP ERP, SAP SCM, or others) for each cycle and possibly other third-party systems. A businessscenario is a unit which can be implemented separately and reflects the customer’s prospective course ofbusiness.
Component
A component is the smallest individual unit considered within the Solution Development Lifecycle; componentsare separately produced, delivered, installed and maintained.
6CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Getting Started
1.3 Important SAP Notes
CautionCheck regularly for updates available for the Application Operations Guide on SAP Service Marketplace athttp://service.sap.com/notes.
Important SAP Notes
SAP NoteNumber
Title
1892741 ABAP Add-on PBFBI 731: Installation, upgrade, CSPs
1909548 SAP Public Budget Formulation 8.1 Solution – Java
SAP Public Budget Formulation 8.1Technical System Landscape
CUSTOMER© 2013 SAP AG. All Rights Reserved. 7
2 Technical System Landscape
2.1 Scenario/Component Matrix
For more information regarding the business scenarios and processes, the system architecture, and requiredsoftware components, see the SAP Public Budget Formulation Master Guide on the SAP Service Marketplace athttp://service.sap.com/instguides.
2.2 Related Documentation
The following table shows where you can find more information about the technical system landscape.
Topic Guide/Tool Quick Link on SAP ServiceMarketplace(http://service.sap.com/<quicklink>)
Application- and Industry-specificComponents such as SAP Financials andSAP Retail
Master Guide instguides
Technology Components such as SAP WebApplication Server
Master Guide instguides
Sizing Quick Sizer Tool sizing
Security Security Map
Application Security Guide
security
instguides
Monitoring with CCMS SAP NetWeaver Library help.sap.com/nw731 Function-Oriented View Solution LifeCycle Management SolutionMonitoring System Monitoringwith CCMS
8CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Monitoring of SAP Public Budget Formulation 8.1
3 Monitoring of SAP Public BudgetFormulation 8.1
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions, including SAP PublicBudget Formulation. The aim of this section is to provide information and documentation to monitor theapplication, by utilizing the Computing Center Management System (CCMS).
You can find more information about the underlying technology in the SAP NetWeaver Administrator’s Guide -Technical Operations Manual in the SAP Library under SAP NetWeaver Library at help.sap.com/nw731System Administration and Maintenance Information Technical Operations for SAP NetWeaver.
3.1 Alert Monitoring
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 torecognize critical situations for SAP Public Budget Formulation as quickly as possible.
3.1.1 Monitoring Installation and Setup
As SAP Public Budget Formulation is powered by SAP NetWeaver 7.31, we recommend that you set up themonitoring infrastructure as described in the SAP Help Portal at help.sap.com/nw731 System Administrationand Maintenance Information Technical Operations for SAP NetWeaver l Administration of SAP NetWeaverSystems and components Administration of Application Server ABAP Monitoring and Administration Tools forApplication Server ABAP.
Proficient knowledge in system monitoring and basic knowledge in SAP NetWeaver is required to compose user-defined monitors. You can obtain additional information about monitoring in SAP Library for SAP NetWeaver athelp.sap.com/nw731 Function-Oriented View Solution Life Cycle Management Solution MonitoringSystem Monitoring with CCMS.
In order to enable the auto-alert mechanism of CCMS, see SAP Note 617547.
3.1.2 Component Specific Monitoring
You can use CCMS to monitor SAP NetWeaver server and the following components:
• SAP NetWeaver BW
• SAP Enterprise Portal
SAP Public Budget Formulation 8.1Monitoring of SAP Public Budget Formulation 8.1
CUSTOMER© 2013 SAP AG. All Rights Reserved. 9
3.1.2.1 SAP NetWeaver Business Warehouse
For SAP NetWeaver Business Information Warehouse (SAP BW), use the CCMS to monitor process chains.
For more information, see SAP Library for SAP NetWeaver at help.sap.com/nw731 Function-Oriented View Business Warehouse Data Warehousing Data Warehouse Management Controlling Data Warehouse
Processes -> Process Chain Process Chain Maintenance Display/Maintenance of Process Chain AttributesBW Monitor in CCMS.
The SAP Public Budget Formulation application uses CCMS Monitor to carry out the process chain monitoring.
Use CCMS Monitoring (transaction RZ20) to enter CCMS Monitor sets and choose SAP BI Monitors BI Monitor Process Chains and select the PBF process chains (/PBFBI/*). In the Process Chains context, process chains
that have run since the last start of the BW system are displayed as monitor objects.
By default, this parameter is set at seven days. This means that the process chain runs from the last seven daysare displayed.
3.1.2.2 SAP Enterprise Portal
For more information about generic SAP NetWeaver logging and tracing, see SAP Library for SAP NetWeaver athelp.sap.com/nw731 System Administration and Maintenance Information Technical Operations for SAPNetWeaver Administration of SAP NetWeaver Systems and components Enterprise Portal (EP/EPC)Technical Operations for Portal Monitoring/Logging and Tracing.
For more information, see Monitoring Portal in SAP Library for NetWeaver at help.sap.com/nw731 Function-Oriented View Solution Life Cycle Management Solution Monitoring System Monitoring with CCMSConfiguring the Monitoring Architecture Monitoring: Configuring Other SAP NetWeaver Components SettingUp GRMG Monitoring of the Portal Infrastructure.
3.2 Detailed Monitoring and Tools for Problem and PerformanceAnalysis
3.2.1 Trace and Log Files
Trace files and log files are essential for analyzing problems. The SAP Public Budget Formulation ABAPcomponent contains standard SAP BI 7.31 objects such as InfoCubes, DSOs, Transformations, Process Chains,and so on. SAP BI 7.31 has a built-in framework to log messages into the application log, which can be viewed inthe Analyze Application Log (transaction SLG1).
The log messages can be viewed by using SAP BW–related objects like BW_PROCESS, BW_XLWB,RSO_REPOSITORY, and so on. All the BW logging objects can be found in the SAP BI 7.31 manual.
By default, only error messages are logged. The setting can be changed in Log Configuration in SAP NetWeaverAdministrator according to your needs to see other message types.
10CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Monitoring of SAP Public Budget Formulation 8.1
SAP Public Budget Formulation uses standard SAP NetWeaver technology for its system logs and traces.
For more information, see Tools in the Technical Operations Manual for SAP NetWeaver in the SAP Library athelp.sap.com/nw731 System Administration and Maintenance Information Technical Operations for SAPNetWeaver Administration of SAP NetWeaver Systems and components Administration of Application ServerABAP Monitoring and Administration Tools for Application Server ABAP.
3.2.1.1 Scenario-Specific Logs and Traces
In addition to the standard SAP BI 7.31 log framework, some scenario-specific logs using specific logging objectsand sub-objects are logged and these extra messages can be viewed in transaction SLG1. All PBF-specific logs willbe found by using Object /PBFBI/PBF.
3.2.1.2 Scenario 1: Reset Public Budget Formulation
3.2.1.2.1 Report Mass Delete
The Mass Delete report /pbfbi/mass_delete_report is executed to reset the PBF system. The use case of thereport is to delete application data usually in a Development, Test, or Training environment. The report willexecute and submit itself in the background to begin a deletion of all PBF data in the delivered BI data sources.
CautionExecution of the report is a data-destructive operation and should not be executed in an active productivebudgeting environment.
A simple selection screen defaults to simulation mode. In simulation mode, nothing is physically deleted.Simulation mode will produce a spool output of datasources that would be deleted if not in simulation mode. It isrecommended to execute the program in sumulation mode first. Uncheck the simulation mode checkbox and thereport will attempt datasource deletion.
Mass Delete checks for the following before execution:
Authorization object /PBFBI/DEL is maintained for the user executing report
Client of execution is not productive
PBF global IMG Budget year is set to 9999 (This action is to confirm system is not actively budgeting anddelete will be performed.)
Open PBF BW locks
If the spool or application log shows errors, the system has to be reset manually from the standard BW RS**transactions; the Application Log is stored under:
Object: /PBFBI/PBF
Subobject: /PBFBI/MASS_DELETE
SAP Public Budget Formulation 8.1Monitoring of SAP Public Budget Formulation 8.1
CUSTOMER© 2013 SAP AG. All Rights Reserved. 11
PBF: Mass Delete Sub Object
3.2.1.3 Scenario 2: Personnel Expenditure Planning
3.2.1.3.1 Personnel Data Maintenance
The audit log can be switched for the following personnel data maintenance:
Job maintenance
Position maintenance
Employee maintenance
The master data changes for the above objects are logged in the DataStore Object /PBFBI/AUD_O01 and/PBFBI/AUD_O02.
3.2.1.3.2 PEP Projection Runs
The projection runs are scheduled as process chains and the execution details can be viewed in the Process chainmaintenance (transaction RSPC) and in the Analyze Application Log (transaction SLG1).
Analyze application log (transaction SLG1)
Object Name: Public Budget Formulation (/PBFBI/PBF)
Sub-Object Name: PBF: Personnel Compensation Planning (/PBFBI/PCP)
3.2.1.3.3 Report Queue Schedule
The /PBFBI/PEP_QUEUE_SCHED report is used to periodically schedule specific projections. The use case is forthe customer to schedule periodic projection reruns that they need on an ongoing basis. Proper use of the reportremoves the need for the customer to remember which rerun projections are to be re entered into the system.The report will append selected projection id into the pooling queue at a specific time in the future whenscheduled. The PBF pooling program will pick up the projections just like with they were entered via the portal UI.
12CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Monitoring of SAP Public Budget Formulation 8.1
Users will use transaction SM37 to schedule report /PBFBI/PEP_QUEUE_SCHED like any other report aftercreating a variant off of the above simple selection screen.
3.2.1.4 Scenario 2: Budget Forms
3.2.1.4.1 Unused Form ID Deletion Report
The /PBFBI/TEXT_DEL_REPORT program will do the following:
Delete all form IDs from the master data which are no longer referenced in any BI objects
Delete texts from table /PBFBI/LINE_TEXT for which the form ID is no longer present in the Form ID masterdata
SAP Public Budget Formulation 8.1Management of SAP Public Budget Formulation 8.1
CUSTOMER© 2013 SAP AG. All Rights Reserved. 13
4 Management of SAP Public BudgetFormulation 8.1
SAP provides you with an infrastructure to help your technical support consultants and system administratorseffectively manage all SAP components and complete all tasks related to technical administration and operation.
You can find more information about the underlying technology in the Technical Operations Manual in the SAPLibrary under SAP NetWeaver.
4.1 Software Configuration
With SAP Public Budget Formulation being an add-on to SAP NetWeaver, no technical configuration is requiredthat is specific to the application. It only uses basis parameters for database, operating system, and ApplicationServer ABAP provided by SAP NetWeaver.
For more information about configuration and its concept, see SAP Library at help.sap.com/nw731 Function-Oriented View Solution Life Cycle Management Customizing.
4.2 Administration Tools
The SAP Public Budget Formulation application is technically based on SAP NetWeaver. For information about therelevant administration tools, see the Technical Operations Manual for SAP NetWeaver 7.31 in SAP Library athelp.sap.com/nw731 System Administration and Maintenance Information.
4.3 Backup and Restore
You need to back up your system landscape regularly to ensure that you can restore and recover it in case offailure.
The backup and restore strategy for your system landscape should not only consider SAP systems but shouldalso be embedded in overall business requirements and incorporate your company’s entire process flow.
In addition, the backup and restore strategy must cover disaster recovery processes such as the loss of a datacenter through fire. It is most important in this context that you ensure that backup devices are not lost togetherwith normal data storage (separation of storage locations).
The backup administration for SAP Public Budget Formulation is based on SAP BW.
For more information about the following topics, see the mentioned section in the Technical Operations Manualfor SAP NetWeaver in SAP Library at help.sap.com/nw731 System Administration and MaintenanceTechnical Operations for SAP NetWeaver Manual:
14CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Management of SAP Public Budget Formulation 8.1
For Backup and Recovery, see Administration of SAP NetWeaver Systems and components AS ABAP(Application Server for ABAP) Management
For High Availability, see General Administration Tasks
4.4 Application Copy
You cannot make a client copy, because SAP Public Budget Formulation is client-independent.
4.5 Periodic Tasks
4.5.1 Scheduled Periodic Tasks
This chapter describes all automatable tasks required to run periodically in order to keep the application runningsmoothly over time. Other tasks may be relevant for certain business scenarios only. It is important that youmonitor the successful execution of these tasks on a regular basis.
For more information about standard background jobs and periodical tasks for SAP NetWeaver components, seethe Technical Operations Manual for SAP NetWeaver in SAP Library at help.sap.com/nw731 SystemAdministration and Maintenance Information Technical Operations for SAP NetWeaver Administration of SAPNetWeaver Systems and components Administration of Application Server ABAP Background Processing.
4.5.2 Required Manual Periodic Tasks
Schedule the Form ID Deletion report mentioned in section 3.2.1.4.1 to delete the unused form IDs. The reportshould ideally be executed when no one is working in the system.
4.6 Load Balancing
The application uses no specific load balancing methods. If necessary, it only applies methods provided by thebasis technology of SAP NetWeaver.
For more information about the load balancing with SAP NetWeaver, see SAP Library at help.sap.com/nw731 System Administration and Maintenance Information Technical Operations for SAP NetWeaver.
SAP Public Budget Formulation 8.1Management of SAP Public Budget Formulation 8.1
CUSTOMER© 2013 SAP AG. All Rights Reserved. 15
4.7 User Management
The application uses the user management tools provided by SAP NetWeaver.
For more information, see SAP Library at help.sap.com/nw731 Function-Oriented View Solution Life CycleManagement Security and User Administration User Administration and Identity Management UserAdministration and Identity Management in ABAP Systems.
16CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1High Availability
5 High Availability
SAP Public Budget Formulation is based on SAP BW. For more information, see SAP Service Marketplace atservice.sap.com/installnw73 Operations.
SAP Public Budget Formulation 8.1Software Change Management
CUSTOMER© 2013 SAP AG. All Rights Reserved. 17
6 Software Change Management
Software Change Management standardizes and automates software distribution, maintenance, and testingprocedures for complex software landscapes and multiple software development platforms. These functionssupport your project teams, development teams, and application support teams.
The goal of Software Change Management is to establish consistent, solution-wide change management thatallows for specific maintenance procedures, global rollouts (including localizations), and open integration withthird-party products.
SAP Public Budget Formulation is based on SAP NetWeaver Application Server ABAP and SAP NetWeaverApplication Server JAVA 7.31. You can find information about the Software Change Management in thecorresponding document section of the Technical Operations Manual for SAP NetWeaver in SAP Library at :
ABAP: help.sap.com/nw731 System Administration and Maintenance Information TechnicalOperations for SAP NetWeaver - Administration of SAP NetWeaver Systems Administration of ApplicationServer ABAP Change and Transport System.
Java help.sap.com/nw731, search for Development Infrastructure to get to this link
Development Infrastructure – Enables and secures the distribution of software changes from thedevelopment environment to the quality assurance and production environment.
Development Request and Development Release Management – Enables customer specific maintenanceprocedures and open integration with third-party products.
Support Packages and SAP Notes Implementation – Provide standardized software distribution andmaintenance procedures.
Release and Upgrade Management – Reduces time, cost, and risk associated with upgrades.
Quality Management and Test Management – Reduce the time, cost, and risk associated with softwarechanges.
Template Management – Enables and secures the rollout of global templates, including localizations.
6.1 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you to organizedevelopment projects in the ABAP Workbench and in Customizing, and then transport the changes between theSAP systems in your system landscape.
For more information, see the Technical Operations Manual for SAP NetWeaver in SAP Library at:
help.sap.com/nw731 System Administration and Maintenance Information Technical Operations forSAP NetWeaver - Administration of SAP NetWeaver Systems and components Administration ofApplication Server ABAP Change and Transport System
help.sap.com/nw731 Function-Oriented View Solution Life Cycle Management Software Logistics Software Change Management Change and Transport System
18CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Software Change Management
6.2 Development Requests and Development ReleaseManagement – ABAP
The transport workflow provides a framework for transporting enhancements or new developments of existingbusiness functions in a system landscape. It provides a direct connection between development and transportadministration. The transport workflow manages the transport process, determines the user for each individualstep 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 usesclearly 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 athelp.sap.com/nw731 System Administration and Maintenance Information Technical Operations for SAPNetWeaver - Administration of SAP NetWeaver Systems Administration of Application Server ABAPChange and Transport System.
6.3 Development Requests and Development ReleaseManagement – Java
The SAP NetWeaver 7.31 Java Development Infrastructure (JDI) is used for customer modifications. The NWDeveloper Studio is used as the Integrated Development Environment (IDE), which connects to the Design TimeRepository (DTR) that serves as the change management system.
6.4 Template Management
You can deploy Customizing settings by using Business Configuration Sets (BC Sets).
6.5 Quality Management and Test Management
You can use the following link to learn about the various possibilities to test your software changes.
help.sap.com/nw731 System Administration and Maintenance Information Technical Operations for SAPNetWeaver - Administration of SAP NetWeaver Systems Administration of Application Server ABAPChange and Transport System Transport Strategy in the CTS TMS Quality Assurance.
SAP Public Budget Formulation 8.1Software Change Management
CUSTOMER© 2013 SAP AG. All Rights Reserved. 19
6.6 Support Packages and Patch Implementation
6.6.1 ABAP
Support Packages for components based on the SAP NetWeaver Application Server ABAP 7.31 are applied usingthe Support Package Manager. For more information, see the Technical Operations Manual for SAP NetWeaver inSAP Library at help.sap.com/nw731 System Administration and Maintenance Information TechnicalOperations for SAP NetWeaver.
Detailed Instructions on applying a Support Package Stack to SAP NetWeaver are given in the Support PackageStack Guide for SAP NetWeaver 7.31. For more information, see the documentation on SAP Service Marketplaceat service.sap.com/maintenancenw73 <SPSxx> Support Package Stack Guide <SPSxx>.
SAP Notes that require code changes for components based on the SAP NetWeaver Application Server ABAP 7.31can be applied using the SAP Note Assistant. For more information, see SAP Library at help.sap.com/nw731Function-Oriented View Solution Life Cycle Management.
6.6.2 Java
Support Packages for components based on the SAP NetWeaver Application Server Java 7.31 are deployed usingthe SUM tool directly into the PBF CE runtime environment. In addition it should be imported into thecorresponding Track using NWDI/CMS WebUI. For more information see the Checking In Software ComponentArchives document:http://help.sap.com/saphelp_nw73/helpdata/en/4d/a65dbb81821f6be10000000a42189b/content.htm.
20CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Troubleshooting
7 Troubleshooting
For general information about troubleshooting, see the Technical Operations Manual for SAP NetWeaver in theSAP Help Portal at http://help.sap.com/nw731 System Administration and Maintenance InformationTechnical Operations for SAP NetWeaver Troubleshooting.
SAP Public Budget Formulation 8.1Support Desk Management
CUSTOMER© 2013 SAP AG. All Rights Reserved. 21
8 Support Desk Management
Support Desk Management enables you to set up an efficient internal support desk for your support organizationthat seamlessly integrates your end users, internal support employees, partners, and SAP Active Global Supportspecialists with an efficient problem resolution procedure.
For support desk management, you need the methodology, management procedures, and tools infrastructure torun your internal support organization efficiently.
8.1 Remote Support Setup
SAP support needs to be able to work remotely for the highest efficiency and availability. Therefore, all requiredsupport tools must be remotely accessible for SAP support, SAP uses the remote connection with SAProuter for aspecific 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 specificsettings or parameters that are necessary. Further assistance is provided in SAP Note 812386.
8.2 Problem Message Handover
For sending problem messages/tickets to SAP, please use the component IS-PS-PBF and provide a detailed andreproducible problem description.
22CUSTOMER© 2013 SAP AG. All Rights Reserved.
SAP Public Budget Formulation 8.1Appendix
9 Appendix
9.1 Related Guides
You can find more information about installation and configuration in the Master Guide.
9.2 Related Information
The following table contains links to information relating to the Application Operations Guide.
Content Quick Link to the SAP Service Marketplace
Master Guide, Installation Guide and Upgrade Guide instguides
ibc
Related SAP Notes notes
Released Platforms platforms
Network Security securityguide
network
Technical Infrastructure ti
SAP Solution Manager solutionmanager
www.sap.com/contactsap
© 2012 SAP AG. All rights reserved.