Support Package pre-requistis accross different landscapes
I am struggling with which landscape but be patched before another since adding PI 711 into the mix.
I am supporting ECC6 EHP4 with NW701, BI 70 at Netweaver 70, Solution Manager 70 Ehp1 and now PI 71 ehp1.
I have been told PI must lead all other landscapes support package level but with it being at a later version of Netweaver than all other landscapes it is a far comparison or does it already lead them?
My immediate need is to begin planning for a support package project on the ECC6 EHP4 landscape in the fall. Since this landscape was last patch, about one year ago we add the PI landscape.
It is a pretty safe bet I will be struggling with this same question in about 6 months when I start looking at a BI support package project.
Any help that could be provided on this would be most appriciated.
Bill
I think we need to understand more why you feel certain systems need to be patched first or in a certain order
- from what you say there must be technical concerns across more than one product area
Perhaps it could be that --->
Generally systems that interact with one another should be on the same BASIS level and SP stack - the general rule of thumb
Products such as SLD definately have to be on systems with equivalent or higher BASIS version and SP stack than systems
they interact with because the content created for a Netweaver 700 SLD
may not be able to cope data supplier information from a Netweaver EHP1 system (this also raise other concerns regarding
exporting data between SLDs - again equivalency - or higher for target system is recommended, sometimes with SLD lower BASIS version source systems may have limited export options as well)
Products such a Solution Manager also as a rule of thumb have to be on equivalent or higher BASIS version or SP levels
than the systems they interact with
But PI also may have similiar concerns because they manage communication between systems e.g business systems
However lets take say Payroll in ECC without any ESS or Legacy Systems, ALE
- totally standalone payroll system - the only rules that apply there are that it works, has the latest fixes and required legal changes and follows a recommended stack - no BASIS equivalency level between other systems may exist in order for payroll to carry out its purpose
Does this help clarify further ?
Best wishes
Stuart
Similar Messages
-
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. -
Support package is different ,can we tranport objects ?
Hi,
Experts,
I have developed some objects,,Now i need to transport the m from BW DEV to BW Production.
But the support package of our
DEV system is :SAPKW70022
Prod system is : SAPKW70014
1) So, will there be any problem in working f my objects in production.?
Please tell me if there are any points to be taken care.
2) please tell me if there any codes to check the data source are availble Bw production that are tranported from BW dev ?
Regards,
Naresh.Hi,
As per SAP Standards, we have to maintain the same support pactch level to all landscape.
in case if the systems are not in sync with the patch level, Transport may go fail or success( it always deponds if on what objects you are transporting)
so it is always better to have same patch level across all landscape.
Going further if you still want to transport the objects , then after transports check the error it will always be related to the Patch level. so you can upgrade the patch in the target system and then retransport with overwrite option.
Santosh
Edited by: Santhosh Nagaraj on Feb 3, 2010 1:40 PM -
Pre requisites to install BI support package 18
Hi,
We have nw 2004s system.
I would like to know how do we check the pre requisites to install BI support package 18 .
Regards,
RakeshDo I have to check under SAP support packages->SAP support package stacks-->SAP netweaver ??
Thanks,
Rakesh -
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 -
Upgrade Support Package for one Software Component
Dear Experts,
I am new with SAP Basis Administrator and I have new task to upgrade EA-HR software component from release 600 sp30 to release 602 sp9.
Actually, EA-HR component in Development system already in release 602 sp9 while quality and production in release 600 sp30. This is where the problem started, since there is one SAP Note we need to apply that depends on the release version. The consultant wants to do the changes in development and transport it to quality then production. Since the way to apply SAP Note is vary based on EA-HR release version, the consultant wants the release version of EA-HR in all systems to be the same.
I have download support package for EA-HR 602 sp9.
My question is very basis, how to upgrade EA-HR component to release 602 sp9?
Regards
Rian WisandanuEA-HR component in Development system already in release 602 sp9 while quality and production in release 600 sp30
This is a no go... This is why most people call for a development freeze while the system is been patched.
the consultant wants to do the changes in development and transport it to quality then production. Since the way to apply SAP Note is vary based on EA-HR release version, the consultant wants the release version of EA-HR in all systems to be the same
You system is not consistent, transporting data into a system with a different patch set can cause serious problems. You are going to have to tell your consultant that he'll have to wait until the whole landscape is patched to the same level.
Who upgraded the component in DEV??
The note also states that this corrections are available for 600 so there was no need for 602 if you are not planning a EHP upgrade..
EA-HRRXX 600 SAPK-60050INEAHRXX
Maybe you can give us some more info about what are you planning to do with your system patch wise?
Regards
Juan -
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. -
How can I upgrade the support package of MDM 7.1?
It also depends which support pack you are upgrading with.
say
From MDM 7.1 SP06 and up, multiple instances of MDM are supported on the same MDM host machine.
Each instance must be installed separately and requires a different SID and different listening ports.
From MDM 7.1 SP07 and up, MDM can be installed with SSL. This is configured using one of the following
modes: Unencrypted, SSL or Both. The installation type is configurable in the MDM server ini files.
In the Projects preparation phase you must:
1. Adapt all custom applications that use ABAP API, Java API, or CLIX. These programs can be adapted in
advance.
2. Update and test import and syndication maps. This has to be done in the Dev/Test environment.
3. Delete all pre-7.1 ports and maps from the Productive environment. This must be done before any
schema imports are allowed in the 7.1 Productive environment
Please see below link for all your concerns (SMP Login Needed)
https://websmp201.sap-ag.de/~sapidb/011000358700001668502008E
hth
thx
Deep -
Is the ASU Toolbox important for support package implementation?
Dear all,
when I want to implement new support packages there comes the hint with number 1000009 (ASU Toolbox).
Is it important to implement the toolbox or is it optional?Hi,
Its not necessary!!
SAP Exchange Infrastructure (SAP XI) enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other. SAP Exchange Infrastructure is based on an open architecture, uses open standards (in particular those from the XML and Java environments) and offers those services that are essential in a heterogeneous and complex system landscape.
With regard to POS lot of domestic softwares are avilable other than Triversity.
The SAP for Retail solution portfolio includes customer-centric solutions from SAP Triversity, an SAP company. The applications from SAP Triversity focus on the "sell" side of retailing. They enable retailers to deliver a best-in-class customer experience across all channels, while helping them to optimize their operating efficiencies and increase profitability.
You can integrate thirdparty POS system to SAP.
http://www.saptriversity.com/
Bye,
Muralidhara -
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. -
Importing Support Packages - Error during XPRA_EXECUTION
Hello,
Database: Oracle 10.2.0.4
Operation System: Windows Server 2008 X64
I´m facing with an error during an importing of support packages in our Solution Manager Ehp1 system (SPS 20 to SPS 25).
I checked the import logs of the queue and I see in there the following error:
Program terminated (job: RDDEXECL, no.: 02083200)
See job log
Execution of programs after import (XPRA)
End date and time : 20110126020847
Ended with return code: ===> 12 <===
When I checked the job log I see in there this:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server SAPSM were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
I went to ST22 and I see in there that specific short dump which show:
Short text
XSLT: No valid XML source
What happened?
The transformation is not possible since the XML source document cannot
be parsed.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_XSLT_RUNTIME_ERROR', was not
caught in
procedure "TRANSFORM_FROM_XML" "(METHOD)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Either the source document contains invalid XML or it is handled
incorrectly in the ABAP program that called the transformation.
How to correct the error
The most common cause of this error is a conflict between the encoding
specified in the declaration <?xml version="1.0" encoding="..."?> in the
document and the actual encoding of the data.
If the document is held in an ABAP string, the actual encoding is the
system code page. If this does not match the declaration, a parsing
error may occur.
These conflicts are a particular issue when XML documents are produced
in one system and then imported into a system with a different code page
(as strings).
For this reason, XML documents should be held as binary data (X strings)
, if they are extracted from the system or accessed from outside.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"XSLT_BAD_SOURCE_CONTEXT" "CX_XSLT_RUNTIME_ERROR"
"CL_SM_BFR_CONTENT_TRANSPORT===CP" or "CL_SM_BFR_CONTENT_TRANSPORT===CM00E"
"TRANSFORM_FROM_XML"
The exception must either be prevented, caught within proedure
"TRANSFORM_FROM_XML" "(METHOD)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:
Can you help how to correct this situation for I can continue the update of support packages!
Best regards,
João Dimas - PortugalHello William,
Which import logs do you refer?
I pasted in my first message the log of import... that is the unique error that it appeared.
I checked the SLOG:
STOP MOVE NAMETABS SSM 6 20110125215838 SAP_BASIS SAPSM 20110125214839404
START MAIN IMPORT SSM I 20110125215838 SAP_BASIS SAPSM 20110125214839404
STOP MAIN IMPORT SSM I 20110125235752 SAP_BASIS SAPSM 20110125214839404
START TBATG CREATION OF EN SSM n 20110125235752 SAP_BASIS SAPSM 20110125214839404
START tp_getprots SSM Y 20110125235753 SAP_BASIS SAPSM 20110125214839404
WARNING: '\SAPSMsapmnt rans mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
WARNING: '\SAPSMsapmnt rans mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
STOP tp_getprots SSM Y 20110126000148 SAP_BASIS SAPSM 20110125214839404
STOP TBATG CREATION OF EN SSM n 20110126000148 SAP_BASIS SAPSM 20110125214839404
INFO EXECUTION OF STANDAR SSM 9 not needed SAP_BASIS SAPSM 20110125214839404
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all SSM 0004 20110126000149 SAP_BASIS SAPSM 20110125214839404
I also checked the ULOG which has the following records:
APServiceSSM 20110126013719 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=\SAPSMsapmnt rans (pid=5276)
APServiceSSM 20110126020829 RFC: tp SHOWPARAMS SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt rans (pid=5196)
APServiceSSM 20110126020830 RFC: tp CONNECT SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt rans (pid=5196)
APServiceSSM 20110126020831 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -
Any idea what´s happen?!
Kind regards,
João Dimas - Portugal -
Why is Adobe dropping support for pre 3GS phones?!
I think it's a bad decision to drop support for pre 3GS devices. There are still many out there and if support is dropped we're forced to still use the old PFI to reach the complete audience.
It's clear that OpenGL ES 2 offers a lot more fancy stuff than OpenGL ES 1.5 does, but still, things like GPU_VECTOR or sophisticated blending are perfectly doable with OpenGL ES 1.5.
And if a clean implementation is really not possible, Adobe should at least allow to publish for old devices even if this means that not all optimization techniques can be used.
I develop iPhone apps using different technologies and AIR is attractive for me because I can target with one project a big range of different plattforms. If Adobe drops support for old phones, this advantage is heavily shortened!
What is your opinion on the this development?Apple have dropped support for pre-3GS because to pull of the features and performance in iOS 4.3 they had to develop just for the ARM7 chip, and not for the ARM6. They probably have a good sense of the number of people that have the older devices, and think it's ok to not update the software on those devices.
The same may be true for Adobe.
I am trying to find out how to make AIR 2.6 and AIR 2.0 live together in Flash CS5. If I work it out I'll let you know. -
I am getting the following error when I right click on a package in solution explorer and execute using SQL Server 2014:
Project consistency check failed. The following inconsistencies were detected: package.dtsx. has a different ProtectionLevel than the project.
Luckily my solution only has 10 packages. I have verified and re-verified that everyone is set to dontsavesensitive.
I have verified and re-verified that the solution has the protection level to dontsavesensitive.
What on earth is going on here? I am using windows authentication and have no need for the package to save any sensitive information, nor should there be any.
Can someone please help me out here?
The Degenerate DimensionHi MMiligan,
Just as the error message said, the exactly issue is that the package package.dtsx has a different ProtectionLevel property value than the project.
So please double check the value of project ProtectionLevel property, like DontSaveSensitive, then make sure all packages in the project use the same ProtectionLevel value.
If there is still an error message indicated that some packages use a different value, please right-click the indicated package to select View Code, then make sure there is a line like below(the DontSaveSensitive
protection level corresponds to the value of 0):
DTS:ProtectionLevel="0"
The following similar thread is for your reference:
http://stackoverflow.com/questions/18705161/protection-level-changed-mid-project-now-project-wont-build
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support -
SAP ERP6.0 with EHP5 HR support packages have not updated
Hi All,
We have installed a fresh system with SAP ERP 6.0 with EHP5. When we are checked all the components like SAP_BASIS, SAP_ABA, etc... all are on EHP5 level. But HR components ( SAP-HR* and EA-HR* ) are having with out EHP ( All are in reliease 600 and level 64 )
Our HCM consultant wants HR EHP5 functionality. My query is that,
1. Can we upgrade HR components alone ( system is having some 80 components regarding SAP-HR* & EA0HR* ).
2. Is it possible to do from SPAM or any other way around ?
3. Is it compulsory to update all 80 components related HR?
What is the better way to update HR ABAP packages.
Thanks in advance.
Regards,
SreekanthHello Sreekanth,
The 'Central Applications' are EHP5 came with the installation but HR components are not EHP5 only came with 600 release.
- As DatabaseSAP confirmed, only central application components will be at EHP5 and other components need to be upgraded separately.
So, if we want to update HR components only do we need to update through SPAM/SAINT or EHPi tool.
- Please use SAINT/SPAM to upgrade HR components. It's not good idea to upgrade SAP_HR and EA_HR via EHPi tool as runtime is more when compared with SAINT/SPAM. In fact it's lengthy process as you are upgrading only two components.
When we selected EHP5 upgrade through Solution Manager the 'Central Applications' also selected (can not be un select & those are already installed). and there are only HR components 603, 604 and 605 releases are selected automatically but not 601 and 602.
- Though Solman displays central applications components in the list, you can select required components/packages while downloading through download manager. Release 601 and 602 do not exist. Only 603, 604 and 605 are available after release 600.
Note: You need to go through the pre-requisties before upgrading SAP_HR and EA_HR to the latest release. In order to upgrade to latest release, you need to download "Delta Upgrade" package along with others.
Example: You need to download and extract 603 and 604 delta upgrade packages when you are upgrading to 604 from 603.
Hope your query is answered.
Good Luck.
Thanks,
Siva Kumar -
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: 11Hi,
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
Maybe you are looking for
-
Receiving a continuous status error with the FP1600 module.
I have 3 banks of terminals. All three banks use a FP-1600 module as the network interface. All three banks operate when I power the modules. However, after roughly 15min to a half hour, bank number 1 experiences a continuous red blinking status erro
-
Hello, I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment. Iam reading a flat file and trying to write into an XML in the same FTP server I have a 1 to 1 Ma
-
Not Able to Create database objects(Tables, etc) in Oracle 12c
Hello Sir, Recently, I have installed oracle 12c in my PC. And I am able to connect with the ANONYMOUS user and connection name ORCL. But I am not able to create any objects in database like tables creation, it's just showing the error message like-
-
(WWC-40019) web cache connection error
Dear All, I installed Oracle9iAS Release 2 Portal & Wireless installation type on my PC and the Oracle Infrastructure on another PC. When i tried to follow the described steps to shutdown my Oracle9iAS instance and then the Infrastructure instance to
-
hi, i created one form in jsp. it contains some text fields(like empid, name,etc).The same fields are created in Oracle Database also. Now i want to fetch the data from database and compare to the current jsp fields. If it match correctly, i want to