Side effects in SAP BW after support package upload

Hello!
I would like to ask whether do You know any side effects executed by installing of a support package (18 and 19) in SAP BW 3.5. If so, should any preventive steps be taken before, to avoid those errors.
Many thanks
RW

Thank You for Your answer.
What I was looking for were all the activities, that are necessary before uploading of a new support package to avoid possible system errors afterwords. As I read on the forum, there are some errors following the SP upgrade like:
- user can not use some program variants any more
- customer exits show error messages, because some tables from the base are changed
- descriptions of new activities in IMG customizing are missing
etc.
Well it seems, that the only thing the user can do is to upload SP patches in the correct order and with an exeption of the last one released.
RW

Similar Messages

Error message ME006 order locked after support package

we went to a new support package this weekend and shortly after we have errors about locked documents error ME006
it is programm RVV50R10C
VL10X
I tried to change the number of tries from 100 to 1000 but had no effect ?
does anybody know how to resolve this ???
kind regards
arthur

Hi
Check SAP Note : 869852
I think it UME is not correctly installed
After upgrading your system to a newer SP, you get one of the following
exceptions when executing the UME WD application:
o java.lang.NoSuchMethodError:
com.sap.security.core.wd.umeuifactory.wdp.I
ExternalUmeUiFactoryCompInterface.hasSimplePermission(Ljava/lang/St
ring;
Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/St
ring;Ljava/lang/String;)Z at
com.sap.security.core.wd.maintaingroup.MaintainGroupComp.afterModel
Init(MaintainGroupComp.java:787)
In order to avoid this error, perform following steps:
- Open the SDM tool and undeploy all components starting with
"tc/sec/ume/wd/..."
- Go to your downloaded SP archives and find the UMEADMIN*.SDA.
Redeploy it.
Regards
Krishna.

Error getting in useradmin after support package issue!!

Hi all ,
We have just upgraded our support package for Bi_JAVA and other.According to our BASIS guy the package installation is through.
But when i checked the portal-----user adminnistration , iam getting the below error.
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NoSuchMethodError: com.sap.tc.webdynpro.services.task.IRequestTask.isUsrLogoffRequest()Z
    at com.sap.portal.pb.PageBuilder.wdDoExit(PageBuilder.java:203)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoExit(InternalPageBuilder.java:169)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doExit(DelegatingComponent.java:112)
    at com.sap.tc.webdynpro.progmodel.controller.Component.exitController(Component.java:255)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.exit(Controller.java:154)
    ... 27 more
See full exception chain for details.
Correction Hints
The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.

Hi
Check SAP Note : 869852
I think it UME is not correctly installed
After upgrading your system to a newer SP, you get one of the following
exceptions when executing the UME WD application:
o java.lang.NoSuchMethodError:
com.sap.security.core.wd.umeuifactory.wdp.I
ExternalUmeUiFactoryCompInterface.hasSimplePermission(Ljava/lang/St
ring;
Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/St
ring;Ljava/lang/String;)Z at
com.sap.security.core.wd.maintaingroup.MaintainGroupComp.afterModel
Init(MaintainGroupComp.java:787)
In order to avoid this error, perform following steps:
- Open the SDM tool and undeploy all components starting with
"tc/sec/ume/wd/..."
- Go to your downloaded SP archives and find the UMEADMIN*.SDA.
Redeploy it.
Regards
Krishna.

Post Processing Steps after Support Package Stack Application

I'm curious if anyone has any guidelines for post processing steps (or pre-processing) when applying Support Package Stacks to their Development Infrastructure (Developmend Workplace and the Central NWDI Server). We have just upgraded a couple of developers local engines and developer studio to SP stack 19 from SP stack 14 and are experiencing some problems. We also applied the J2EE stack and appropriate SCA files to the NWDI server.
After the support packs it looks like our DTR files are gone (when reimporting configuration via Developer Studio the SC's are there but there are no DC's inside of them). Additionally, it looks like we have to manually reimport the newest versions of SAP_BUILDT, SAP_JTECHS, and SAP-JEE. Another thing is that old Local Web Dynpro DC's are now complaining about class path problems and different versions of files. We followed the documentation for applying SP19 exactly as the documentation says for a Java Development Usage type. Is there a checklist or something that anyone has for steps to perform after the application of the support packs?

I think I'm missing something. Now I see the code and DC's inside the DTR. However, when I try to import into NWDS no DC's come in (the software components exist, but no DC's in them). Additionally, the CBS web ui reports that my software components do not contain any DC's even though I see them in the DTR. What things can I look at to determine what I'm missing here?
Thought I'd add some more info..after applying the support packs, we imported the new SAPBUILD, SAP_JTECH, and SAP_jee SCA'S into our track as we required some functionality from the newer build SCA. We also reimported our old archives back into the system by manually checking them in assuming this would fix the problem with us not seeing the source in the NWDS or the DTR. After the import, the CBS no longer sees our custom DC's, but the DTR does (both in active and inactive ws). When importing the dev configuration into the NWDS our custom DC's no longer appear, but SAP's standard SCA's do.
Message was edited by:
Eric Vota

CRM 5.0 - Middleware issues after Support Package installation

Hi experts,
after upgrading the support package (from version 11 to version 17) we are facing a lot of issues.
1. We need to synchronize custom tables from CRM to R/3.
Can you give me an example on how to configure table SMOFQFIND/CRMMAPTAB for inbound queues CRI*?
We know we have to do but we don't know how.
2. We need to synchronize standard tables from R/3 to CRM.
Do you know we have to do some new configuration in SMOFQFIND/CRMMAPTAB table?
With the older version of SP we were'nt asked to configure those tables.
It has worked up to now
Thank you in advance
Emanuele

Hi,
We have the exact the same issue her using the 0DAT variable to restrict to the system date (in the filter process of the APD).
Did anyone resolve this issue?
Thanks,
Fabian

Transports between systems after support package application

Hi gurus, we need to apply a lot of support packages into the development system and I wanna know if in the meantime we need to "freeze" all transports between systems.
This because the systems (DEV - QA - PRD) are in differente support package level. This until we apply the support packages into the others systems
Thanks in advance.
Ronald.

Yes, any transport which is taking SAP standard code from DEV to QA to PRD should not move if the systems in landscape are on different support pack level. Because it can happen that SAP has done some modification to that standard code in new support pack.
However, anything which is isolated Z-development (like some z-output report or smartforms) can proceed.
But, I suggest , stop moving transports until all systems have same support pack level.
G@urav.

SAP Upgrade Assitant Support Package Problem 4.7 to ECC 6

Hi all,
Doing an upgrade from 4.7E to ECC 6. Does anyone know what should be the minimum patch level to start upgrade. Basis and Abap Supp. pack is on level 60. HR is on 61. But after starting prepare, it is giving error in version check phase. It is saying Upgrade Assitant the start release configuration is not supported. SAP_ABA : 620
SAP_APPL : 470
SAP_BASIS : 620
SAP_HR : 470
Infact all the support packages are at this level however the kernel is upgraded to 640 patch level 43.
If anyone has the info please help.. If ignored the upgrade assistant ask VALCHK_INI password which searched is nowhere found.
Kindly help.
Regards,
Valvan

Hello,
Thanks Eric I had already checked and they are above what is the minimum support pack level for eg SAP_BASIS requires minimum 41 support pack level and i have installed 61. Everything is according or more than the prerequisite requirement. Is this is a database version problem. Shall i go to upgrade oracle first as of now i am on 9.2.0.6.
Regards,
Shekhar Kulkarni

Error in Solution Manager Optimizer after support packages

HI all,
after patching my SAP Solution Manager from SP18 to SP25, MOPZ doesn't work because there is this error in web page:
Error when processing your request
What has happened?
The URL http://<fqdn>:<port>/sap/bc/webdynpro/sap/wda_mopz_plan/ was not called due to an error.
Note
■The following error text was processed in the system SLM : CREATE OBJECT: The class \CLASS=/1WDA/L0STANDARD\CLASS=CL_LINK_CHOICE was not found.
■The error occurred on the application server srvslm_SLM_00 and in the work process 0 .
■The termination type was: RABAX_STATE
■The ABAP call stack was:
Method: CREATE_BY_VIEW_ELEMENT of program CL_WDR_VIEW_ELEMENT_ADAPTER===CP
I've found that web dynpro WDC_MOPZ_CORE has a syntax error if a try to generate it.
The error is:
Web Dynpro Comp. / Intf. WDC_MOPZ_CORE,Web Dynpro Component Controller COMPONENTCONTROLLER
Method ADJUST_XML
Method "ADJUST_STACK_XML" is unknown or PROTECTED or PRIVATE.
Here the ABAP codes:
method ADJUST_XML .
DATA lv_editable TYPE abap_bool.
wd_this->mo_controller->crm_adapter->is_editable(
IMPORTING ev_is_editable = lv_editable
CHECK lv_editable eq abap_true.
call method wd_this->mo_xml_manager->adjust_stack_xml.
endmethod.
There are no inactive objects as described in oss notes and I've tried to apply also notes 1548530 & 1485385 but with no luck.
Could you help me ?
Thanks
Maurizio Manera

Hello Mr Manera,
It is a known issue that the activating errors or issues with the objects in the common correction notes happen when the upgrade is done to SP23, notes applied, then upgrade again to SP25 or SP26.
The usual way to deal with this kind of error is running SPAU, letting the note go into an inconsistent state, then applying again the new version of the note. This may require to completely deimplement the common correction notes then implement them again.
Have you tried doing this?
Best regards,
Miguel Ariñ

Batch process is started for DTP's-After Support package upgrate...

Dear All,
we upgraded with SP19 in our BI systems,
After patchs are completed when we run the dtp's either through process chain or normal triggering also dtp is shows still yellow for long time for all the cubes dtps...dso dtp....any dtps....
Message as follwos...
Extraction DataSource XXXXXXXX: 303 Data Records
Prepare for Extraction
Beginning extraction request REQU_D433FLO6MSZEOFHIR1SUOMBSP...
Extraction Completed
Waiting for free batch process...
Batch process started
then it is alwys shows yellow only even there is single records in Datasource...any help please...

Thanks for the quick reply!
We currently only have one of the notes implemented (1277550) and that one does not fix the problem, but it makes the yellow processes turn red (which is what it claims to do in the note description as well).
However, we have days where everything runs fine and we have days where we run into this issue. Therefore it is hard to test and before implementing this one additional note, I was curious whether there was anything else that you guys did to fix the problem. I am glad to hear that those two notes together should take care of the problem. We are implementing it right now.
Thank you!
Dennis

Support package requierement for unicode conversion

We are currently planning a unicode conversion for a SAP 4.7enterprise 1.1 extension version, running under Aix and Oracle, Basis/ABAP SP 35, HR SP20.
According to the conversion guide, we must implement at least Support Pachage 60 for Abap and Basis, no explicit requierement for HR SP level.
I believed that we must applied SAP procedure and exclusively HR Support Package Stack up to 27, which include SP 60 for Basis and Abap and HR 61.
Our HR guys argue there is no indication from SAP that the SUPPORT PACKAGE STACK policy is mandatory and that SAP will provide us with normal support if we run the unicode conversion with SP Basis/ABAP 60, in other word even if we do not respect the support package stack combinaison. Need help on this issue before starting the project

Exterprise 4.7 is Unicode-Compliant,meaning that you can have unicode in 4.7.
If that the case, you should convert to 4.7 Enterprise Ext 2.00 Unicode First.
later only upgrade to ECC 6.0 after 2 years, as you said.
My answer is yes, to your question.
You can download the installation kits at:
http://service.sap.com/swdc
anyway, it is recommended to have the latest SP in your system.
cheers,
Vincent

RSPOR_SETUP = Different ABAP and Java support packages.

Hi all,
We have an ECC 6.0 system with abap+java stacks. When we run the RSPOR_SETUP report we get this error:
Different ABAP and Java support packages. Combination of support packages invalid
And with some more clicking we find this:
6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
   ABAP Support Package:                  13
   Java Support Package:                   0
On the Java stack we see (among others) these components:
sap.com       BI-IBC       7.00 SP12 (1000.7.00.12.0.20070509050058)
sap.com       BI_MMR       7.00 SP12 (1000.7.00.12.0.20070507084106)
sap.com       BI_UDI       7.00 SP12 (1000.7.00.12.0.20070507084125)
sap.com       BI-BASE-S       7.00 SP12 (1000.7.00.12.11.20080324092518)
sap.com       BI-WDALV       7.00 SP12 (1000.7.00.12.1.20071105133039)
sap.com       BI-REPPLAN       7.00 SP12 (1000.7.00.12.3.20080104101916)
So I believe all components are correctly installed.
What are we doing wrong?

Hello.
Please be aware, that report RSPOR_SETUP should NOT be used with a Netweaver 04s system. This report has been replaced by the support desk tool. I request you to run the support desk tool as per note 937697 to check if there are any configuration issues in your system.You can resolve any red traffic lights that might be reported by the tool by following the corresponding actions suggested.
I hope I can be helpful.
Thanks,
Walter Oliveira.

Release-Notes Netweaver04 BW 3.5 Support Package 14 - highest

Hi folks,
Need your help. We plan to move to the highest support package in SAP BW 3.5. At the moment, we have support package 14.
Could someone tell me which the essential modifications are between SP 14 and the newest?
Where can i find the release notes?
thx
pascal

Hi Pascal,
I have sent you a document regarding the SAP NetWeaver 04 Support Package Stack 15 and Higher to your mail id [email protected].
check out the document.
Assign points if it is helpful.
Regards,
Sreedhar

Combination of support packages invalid.

I am getting the following error in RSPOR_SETUP, but according to note 1013369
this stack is supported. This system is a fresh SR2 install , then I applied
SPS12 , then finally applied SAPKW70014.
Is the error referring to the version 11 of the java classes? How did those even get there?
The Systeminfo shows all java components correctly at SPS12....
Status for Step 2 - Create RFC Destination for Portal
   Status 1: Create RFC Destination In J2EE Engine         Okay
   Status 2: Create RFC Destination for Portal             Different ABAP and Java support packages. Combination of support packages invalid.
   Status 3: Maintain Portal Server Settings for Portal    Okay
   Status 4: Maintain Single Sign-On in BI                 Okay
   Status 5: Export BI Certificate into BI                 Okay
   Status 6: Import BI Certificate into Portal             Okay
   Status 7: Create BI Sytem in Portal                     Existence of BI System in Portal cannot be checked automatically.
   Status 8: Configure User Management in Portal           Okay
   Status 9: Export Portal Certificate into Portal         Okay
   Status 10: Import Portal Certificate into BI            Okay
   Status 11: Set Up Repository Manager for BI in Portal   Setup of Repository Manager for BI in Portal cannot be checked automatically.
   Status 12: Maintain User Assignment in Portal           Okay
   Status 13: Import SAP NetWeaver Plug-In into BI         Okay
Entries for Step 2 - Create RFC Destination for Portal
BI Transaction Display and Maintenance of RFC Destinations (SM59)
Create
Name of RFC destination:             (redacted)
Connection type:                     T (TCP/IP connection)
Description of RFC destination:      (redacted)
Technical settings
Activation type:                     Registered Server Program
Program ID:                          (redacted)
Gateway host:                        (redacted)
Gateway service:                     (redacted)
Logon/security
Send SAP Logon Ticket                active
Checks for Step 2 - Create RFC Destination for Portal
1. Check existance of RFC destination
   Check of RFC destination (redacted) with RFC_READ_TCPIP_DESTINATION successful
2. Check RFC destination with RFC Call
   RFC Call RFC_PING, destination (redacted) successful
3. Check Number of registered Processes
   GWY_GET_NO_REG_PROGRAMS
   Number of registered processes:       20
4. Check existance of com.sap.ip.bi Java classes
   RFC Call RSWR_RFC_SERVICE_TEST, destination (redacted) successful
    BI test service for user (redacted) called successfully with parameter RSPOR_SETUP.
5. Check version information of com.sap.ip.bi Java classes
   RFC Call RSWR_RFC_VERSION_INFO_GET, destination (redacted) successful
   com.sap.ip.bi.base.application.par           7.0012.20070801085802.0000
   com.sap.ip.bi.base.par                       7.0012.20070801085802.0000
   com.sap.ip.bi.base.portal.par                7.0012.20070801085802.0000
   com.sap.ip.bi.bics.cmi.par                   7.0012.20070426205038.0000
   com.sap.ip.bi.bics.os.impl.par               7.0011.20070131173855.0000
   com.sap.ip.bi.bics.os.par                    7.0011.20070131173855.0000
   com.sap.ip.bi.bics.par                       7.0012.20070801085802.0000
   com.sap.ip.bi.broadcasting.base.par          7.0012.20070801085802.0000
   com.sap.ip.bi.broadcasting.par               7.0011.20070131173855.0000
   com.sap.ip.bi.conv.backendaccess.par         7.0011.20070131173855.0000
   com.sap.ip.bi.conv.dac.res.bi.os.par         7.0011.20070131173855.0000
   com.sap.ip.bi.conv.dac.res.bi.par            7.0012.20070801085802.0000
   com.sap.ip.bi.conv.dac.res.dll.par           7.0011.20070131173855.0000
   com.sap.ip.bi.conv.dac.res.oqqv.par          7.0012.20070801085802.0000
   com.sap.ip.bi.conv.dac.res.trex.par          7.0011.20070131173855.0000
   com.sap.ip.bi.dataaccessservice.par          7.0012.20070426205038.0000
   com.sap.ip.bi.export.lib.par                 7.0012.20070426205038.0000
   com.sap.ip.bi.export.model.par               7.0012.20070801085802.0000
   com.sap.ip.bi.export.office.par              7.0012.20070801085802.0000
   com.sap.ip.bi.export.printformats.par        7.0012.20070801085802.0000
   com.sap.ip.bi.export.xfa.par                 7.0012.20070801085802.0000
   com.sap.ip.bi.folderpickerpcd.par            7.0012.20070426205038.0000
   com.sap.ip.bi.km.base.par                    7.0012.20070801085802.0000
   com.sap.ip.bi.km.documentmigration.par       7.0012.20070426205038.0000
   com.sap.ip.bi.km.integration.par             7.0012.20070801085802.0000
   com.sap.ip.bi.km.propertyrenderer.par        7.0011.20070201072627.0000
   com.sap.ip.bi.km.repositorymanager.par       7.0012.20070801085802.0000
   com.sap.ip.bi.metadata.par                   7.0012.20070426205038.0000
   com.sap.ip.bi.objectservices.oqqv.par        7.0011.20070201072627.0000
   com.sap.ip.bi.objectservices.par             7.0011.20070201072627.0000
   com.sap.ip.bi.offlinenavigation.par          7.0011.20070201072627.0000
   com.sap.ip.bi.portal.rfc.dispatcher.par      7.0012.20070426205038.0000
   com.sap.ip.bi.portalheartbeat.par            7.0010.20061024165340.0000
   com.sap.ip.bi.portallogger.par               7.0010.20061024165340.0000
   com.sap.ip.bi.portalnavigation.par           7.0011.20070131173855.0000
   com.sap.ip.bi.portalrfc.par                  7.0010.20061024165340.0000
   com.sap.ip.bi.portalrfctest.par              7.0010.20061024165340.0000
   com.sap.ip.bi.ranges.par                     7.0012.20070801085802.0000
   com.sap.ip.bi.repositorymanager.par          7.0010.20061024165340.0000
   com.sap.ip.bi.service.bics.par               7.0012.20070426205038.0000
   com.sap.ip.bi.service.generic.par            7.0012.20070801085802.0000
   com.sap.ip.bi.service.km.os.par              7.0012.20070426205038.0000
   com.sap.ip.bi.service.portal.os.par          7.0010.20061024142635.0000
   com.sap.ip.bi.supportdesk.par                7.0013.20070620182001.0000
   com.sap.ip.bi.web.advancedcontrols.par       7.0012.20070801085802.0000
   com.sap.ip.bi.web.broadcasterstart.par       7.0011.20070201072627.0000
   com.sap.ip.bi.web.composites.par             7.0011.20070201072627.0000
   com.sap.ip.bi.web.dataprovider.par           7.0012.20070801085802.0000
   com.sap.ip.bi.web.deploytime.par             7.0012.20070426205038.0000
   com.sap.ip.bi.web.dialogs.conditions.par     7.0012.20070801085802.0000
   com.sap.ip.bi.web.dialogs.exceptions.par     7.0012.20070801085802.0000
   com.sap.ip.bi.web.dialogs.formula.par        7.0011.20070201072627.0000
   com.sap.ip.bi.web.dialogs.generic.par        7.0011.20070201072627.0000
   com.sap.ip.bi.web.dialogs.opensave.par       7.0012.20070801085802.0000
   com.sap.ip.bi.web.dialogs.selector.par       7.0012.20070801085802.0000
   com.sap.ip.bi.web.dialogs.statistic.par      7.0012.20070801085802.0000
   com.sap.ip.bi.web.dialogs.variablescreen     7.0012.20070801085802.0000
   com.sap.ip.bi.web.dialogsframework.par       7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.analysis.par         7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.bodyattributes.p     7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.broadcastindex.p     7.0011.20070201072627.0000
   com.sap.ip.bi.web.items.buttongroup.par      7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.chart.par            7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.command.par          7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.container.par        7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.contextmenu.par      7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.dataproviderinfo     7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.filter.par           7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.filterpane.par       7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.generic.par          7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.group.par            7.0011.20070201072627.0000
   com.sap.ip.bi.web.items.hierarchfilter.p     7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.htmlattributes.p     7.0011.20070201072627.0000
   com.sap.ip.bi.web.items.infofield.par        7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.inputfield.par       7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.km.par               7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.map.par              7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.menu.par             7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.messageslist.par     7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.mime.par             7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.navigation.par       7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.persistency.par      7.0011.20070201072627.0000
   com.sap.ip.bi.web.items.properties.par       7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.report.par           7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.structural.par       7.0011.20070201072627.0000
   com.sap.ip.bi.web.items.text.par             7.0012.20070801085802.0000
   com.sap.ip.bi.web.items.ticker.par           7.0012.20070426205038.0000
   com.sap.ip.bi.web.items.variables.par        7.0011.20070201072627.0000
   com.sap.ip.bi.web.objectservices.par         7.0011.20070201072627.0000
   com.sap.ip.bi.web.pageexport.par             7.0011.20070201072627.0000
   com.sap.ip.bi.web.portal.deployment.par      7.0011.20070201072627.0000
   com.sap.ip.bi.web.portal.integration.par     7.0012.20070801085802.0000
   com.sap.ip.bi.web.portal.mimes.par           7.0012.20070801085802.0000
   com.sap.ip.bi.web.preexecution.par           7.0012.20070426205038.0000
   com.sap.ip.bi.web.runtime.par                7.0012.20070801085802.0000
   com.sap.ip.bi.web.runtime.scripting.par      7.0012.20070801085802.0000
   com.sap.ip.bi.web.runtime.template.par       7.0012.20070426205038.0000
   com.sap.ip.bi.web.scripting.par              7.0012.20070426205038.0000
   com.sap.ip.bi.web.ui.dragdrop.par            7.0012.20070426205038.0000
   com.sap.ip.bi.web.ui.queryviewactions.pa     7.0012.20070426205038.0000
   com.sap.ip.bi.web.uiframework.par            7.0012.20070426205038.0000
   com.sap.ip.bi.web.uiitem.par                 7.0011.20070201072627.0000
   com.sap.ip.bi.web.unifiedrendering.par       7.0012.20070801085802.0000
   com.sap.ip.bi.webdynpro.alv.pdf.par          7.0011.20070201072627.0000
6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
   ABAP Support Package:                  14
   Java Support Package:                  11

Hi,
I have the same problem. I´ve installed a fresh netweaver SR3, and the patch level is the next,
6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package(SAP BI)
ABAP Support Package:           19
Java Support Package:              16
More thanks

Side effects disabling rsh (SUN OS)

Hello.
For security reason OS administrators want to disable the rsh on all servers.
Can anyone list what are the side effects in SAP systems (tools or transactions which would not work anymore) and which could be a workaround?
Thanks a lot, kind regards,
Dino

AFAIK with newer Solaris 10 installations all remote services are disabled by default and the system works. For a single instance rsh is not needed.
If you configured other rem* commands in SM49 you may need to replace them to use ssh instead.
Markus

What is Plug-in, SUpport Package, Add in and how R3 and BW are interdep

Hello Every One,
Can some one explain me in simple words about the terms, Plug-ins, SUpport Packs, Service Packs, Add-in's, SAP Notes and how R3 and BW are interdependant in the above mentioned terms? Can anyone give a simple example?
regards,
kishore

Hi,
Plug-ins:[/b]
Additional program which enhances the functionality of an existing program. Additional functions which may not be needed or are mutually exclusive are often implemented as plug-ins.
For example ICMAN contains various plug-ins for the various network protocols which it supports (HTTP, SMTP, FTP,...).
The interface between mySAP.com components (for example, SAP APO, SAP BBP, SAP BW, SAP CRM) and one or more SAP R/3 systems.
The SAP R/3 Plug-In unites the plug-ins APO-CIF, CRM-R3A, BW-BCT and B2B-PRO-PI. This simplifies maintenance significantly and guarantees compatibility between the individual mySAP.com components. With SAP R/3 Plug-In, you can use several mySAP.com components simultaneously in a single system. SAP R/3 Plug-In supplies the mySAP.com component transaction data and master data in real time.
Technically, there are two versions of each release of the SAP R/3 Plug-In, a PI version and a PI-A version.
The technical names of the software components are PI and PI_A
SUpport Packs
A set of corrections for serious software errors in the SAP system.
Support Packages are compiled periodically and made available in the SAP Service Marketplace.
Service Packs
A grouping of different services for a quotation.
A service package can be agreed between a service provider and a customer within a service contract or as part of a complex service plan, which can also be additionally agreed in a service contract.
EXAMPLE
A "Winter Car Check" service package containing the following services is agreed in a contract:
Cooling water check
Brake fluid check
Battery inspection
Light inspection
Add-in's
add-ins are enhancements to the standard version of the system. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software
http://help.sap.com/saphelp_erp2004/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
SAP Notes
Documentaion Prepared by SAP for publishing clarity in case of corrections or changes happening to the SAP Software.
R3 and BW are interdependant
Then BW takes the Data from R/3 : so there has to be Support Pluggins which are mapped to the BW server.So the SAP Supported R/3 Versions should be used.
Eg: SAP Stoped the Support for r/3 4.0 series
regards
Happy Tony

Side effects in SAP BW after support package upload

Similar Messages

Maybe you are looking for