P. 1
Upg46c Sr2 Unix

Upg46c Sr2 Unix

|Views: 1,800|Likes:
Published by Syed Ahmed

More info:

Published by: Syed Ahmed on May 25, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

11/21/2012

pdf

text

original

Use

If none of the measures described in Problems and Solutions During the Upgrade solves your
problem, contact your SAP Local Support. To enable us to help you as quickly and effectively as
possible, follow the procedure given here.

Procedure

If you encounter problems that are specific to the upgrade, create an error message in the
SAPNet – R/3 Frontend and assign it to the component BC-UPG. Answer the following questions
and put these answers in your SAPNet - R/3 Frontend customer message:

1. For which SAP component do you want to perform the upgrade?

2. Which release are you upgrading from? Which release are you upgrading to?

3. Which operating system version are you using?

4. What was the original release of your SAP System?

5. In which R3up phase does the error occur?

This information is listed at the end of the of the R3up.log file located in the upgrade
directory.

6. Did you have problems with the SAP System before upgrading?

Also provide us with the following logs (if they exist in the upgrade directory) using ftp on the SAP
support server that is closest to you (sapserv) or by fax:

• R3up.log

.ELG or the last file written with the .ELG suffix
and the detailed log file that contains the error message

• For the phases JOB_ or RUN_, we also require

− Last job log of user DDIC written in client 000 (use transaction SM37 to find it)

− Last lines written in the system log of the SAP System (use transaction SM21 to find

them)

− Last short dump written to the system log at the time in question, if one exists (use
transaction ST22 to find this out).

• For transport phases we also require SLOG46D.

For more information about using the SAP support server to transfer files, see SAP Note 40024.

If you are certain that the problem is not an upgrade-specific one but a product-specific one,
assign your error message to the appropriate product-specific component. The following table
gives you information on the different components to which you can assign your message in
SAPNet - R/3 Frontend.

SAP AG

Upgrading to 4.6C Support Release 2: UNIX

April 2001

197

SAP Product

Component in SAPNet – R/3 Frontend

Index Management Server

BC-SRV-TRX

OLTP R/3 System

BC-UPG

R/3 Standalone Gateway

BC-UPG

SAP Add-On

BC-UPG-ADDON

SAP Advanced Planner & Optimizer

APO-BAS

SAP Business Connector

BC-MID-BUS

SAP Business Information Warehouse

BW-SYS

SAP Business-to-Business Procurement

BBP-SAD

SAP Customer Relationship Management

- Communication and Development Station

CRM-MW

- CRM Server

BC-MID-INT-SRV

- Internet Pricing and Configurator (IPC)

CRM-MT-IU-SPE

- Mobile Client

CRM-WBT-IU

- R/3

BC-UPG

SAP DrFuzzy Search Engine

BC-SRV-TRX

SAP Frontend

BC-INS

SAP Internet Transaction Server

BC-FES-ITS

SAP Knowledge Management

KM-KW

SAP R/3 Enterprise

BC-UPG

SAP Strategic Enterprise Management

BC-UPG-ADDON

SAP Web Application Server

BC-UPG

SAP Workplace Server

BC-UPG

SMART Installation

BC-UPG

Upgrading to 4.6C Support Release 2: UNIX

SAP AG

198

April 2001

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->