Support packages in status canceled

Hi,
In our test system (SAP Netweaver 7.00 with Oracle 10.2) we got an error upgrading the support packages SAP_APPL 15 to 19. First, we deleted de contents of table PAT01. Now these are in status canceled in transaction SPAM. When we try to
define the queue again, we get the error: No Support Packages found for this selection.
Please, can you help us with this issue?.
Regards.

Hi Arjun,
I'm sorry, but I just finished to check again the table PAT03, and I have found the next entries:
PATCH                SHORT_TEXT                                     STATUS   DELIV_DATE   DELIV_TIME    IMPLE_DATE
SAPKH60015           SP 15 for SAP_APPL 6.00                   ?        07.01.2009       11:01:33          13.02.2012
SAPKH60016           SP 16 for SAP_APPL 6.00                   ?        20.07.2009       08:42:37          13.02.2012
SAPKH60017           SP 17 for SAP_APPL 6.00                   ?        25.02.2010       16:02:29          13.02.2012
SAPKH60018           SP 18 for SAP_APPL 6.00                   ?        13.08.2010       18:49:10          13.02.2012
SAPKH60019           SP 19 for SAP_APPL 6.00                   ?        31.01.2011       15:07:47          13.02.2012
What do you think about to delete them?.
Regards.

Similar Messages

SPAM support packages error

Hi,
I've tried to upgrade CRM 5.0 SR 1 to SR 2, during the operation I had error during the phase TP_IMPORT, the error was an buffer inconsistency. It was impossible to reset the queue during this phase. So I deleted entries in the database table PAT01-PAT02-PAT03, now queue is empty but I've internal error of spam check when I try to reload this package.
In the background, I've the job still running RDDGENOL (triggered RAISE_EXECPTION, and timeout) created by ddic during the SP, who lock tables for SP, I can't stop it.
Furthermore, a dialogue process running with a BDG process waiting for RFC, which is also impossible to cancel.
Any help will be thankful.

hi people,
we have checked for the status of support package in Transaction SPAM traffic signal is still red and in the Phase RUN_SPAU_? it is stuck and even after restarting import it shows clean-up phase is left and it ends with same error mention above
the support package name is SAPKB70014 size is 116266 MB now after restarting the Import the following error message comes
The import was stopped, since an error occurred during the phase
RUN_SPAU_?, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
     -   Error in phase: RUN_SPAU_?
     -   Reason for error: TP_CANNOT_CONNECT_SYSTEM
     -   Return code: 0255
     -   Error message: Could not connect to semaphore server
we run all the phase in background, and even after entering the support package number in transaction SPAU there it is showing
"No objects within selected filter parameteres"
Q.1 Any idea what went wrong and how to fix that?
Q.2 Is there any problem if we run the all four phases of support package in background or it should be run in dialog ?
latest tp & R3trans updated

Import Basis Support Package 7.00 error

Hi All,
I wanted to apply Basis support package 9 for release 7.00 for our solution manager 4.0 system.
When i started, it gave an error in the phase ADDON_CONFLICT? stage.. The message is as below:
Phase ADDON_CONFLICTS_?: Explanation of Errors
Conflicts were found between the Support Packages that you want to
import and the Add-Ons installed in the system. To guarantee the
consistency of your system, the import is interrupted until all Conflict
Resolution Transports (CRTs) for the listed Support Packages are
included in the queue.
To include the CRTs in the queue, proceed as follows:
- Write down the Support Packages and Add-Ons that have conflicts.
- Leave this screen by choosing 'Cancel' (F12).
- Load the CRTs for the Support Packages with conflicts from the SAP
Service Marketplace or request them from your Add-On supplier.
- Define the extended queue again in the Support Package Manager.
- Import the queue. The Support Package Manager executes all steps from
the beginning.
If the problem involves an SAP Add-On, see SAP Note 53902, which tells
you which CRTs resolve the conflicts. Otherwise contact the supplier of
your Add-On for details on how to proceed.
The following contains a table of Support Packages for each Add-On for
which conflicts were detected. The column 'Information on the Conflict
Resolution' specifies how you can resolve a conflict. For more
information, select the corresponding 'Information for the Conflict
Resolution'.
Conflicts Between Add-On ST 400 and Support Packages
Software Component   Release      Support Package        Information on
                                                         Conflict Resolution
SAP_BASIS            700          SAPKB70009             Include CRT
Can anyone guide me how to proceed.
Thanks,
Sailesh K

Hi Shailesh,
You are employing one or more Add-Ons in your system, apply patches regularly and want to know how the consistency of your Add-Ons is guaranteed. The list of Add-Ons installed in your system is stored in table AVERS.
During patch application the SAP Patch Manager (SPAM) checks for conflicts between patches in the queue and the installed Add-Ons. A conflict occurs if an object delivered in a patch is also delivered in an Add-On. If conflicts are detected, SPAM stops processing at step ADDON_CONFLICTS_? and asks the user to load the corresponding CRTs into his system. The attributes of such CRTs match the Add-On id, Add-On release and patch predecessor (i.e. the patch in conflict).
The patch application can only resume if all CRTs are selected in the patch queue. To resolve a conflict SPAM does not check if the conflicting object is contained in a CRT. It suffices that the corresponding CRT has been selected in the patch queue. All conflicts raised by its patch predecessor(s) are then resolved in one go.
CRTs were introduced to protect the consistency of Add-Ons during the application of patches, such as Hot Packages and Legal Change Patches (LCP). There are two types of CRTs:
1. Conflict Resolution Transports (CRT)
A CRT resolves conflicts between one patch and one version of an Add-On including all previous versions. Example:
Consider a system where Add-On IS-X is installed. During the application of patches P1 and P2 SPAM detected conflicts between the patches and the Add-On.
To resolve these conflicts two separate CRTs are required, CRT1 and CRT2. A consistent patch queue looks like this:
    P1
    CRT1
    P2
    CRT2
SPAM will only let you resume the patch application if you redefine the patch queue containing all four patches. You can see the name of the patch for which a CRT resolves a conflict in the "Predecessor" field in the patch queue dialog.
2. Collective Conflict Resolution Transports (CCRT) are similar to CRTs but resolve conflicts between several patches and an Add-On. Example:
Consider the previous example but this time the conflicts between patches P1, P2 and Add-On IS-X are resolved not by two CRTs but by one Collective CRT (CCRT) CCRT1. A consistent patch queue looks like this:
P1
P2
CCRT1
SPAM will only let you resume the patch application if you redefine the patch queue containing all three patches. The CCRT is added at the end of its highest predecessor, here P2. You can see the highest predecessor for a CCRT in field "Valid to patch#" when you scroll the patch queue dialog to the right.
Keep in mind that a CCRT describes a range of patches for which conflicts are resolved, with the lower limit being the predecessor and higher limit the highest predecessor.
Cheers,
Shyam

How to find out version, support package, patchlevel of installed j2ee as

Hello all
We have PI 7.11 installed and I'd like to know what the support package and patchlevel of our installed j2ee application server is. We would like to post-install NWDI and need to know which are the right SCA-Files for us to download.
Can anyone tell me where to find this information? I wasn't able to find it (maybe just didn't see it?)
Thanks in advance
Renaud

Thanks Srikanth for your quick reply
But which "help -> about" are you talking about?
nwa? ConfigTool? Management Console? JSPM? SAPGUI Client? Elsewhere?
From SAPGUI-Client I choose System -> Status and click on details button for SAP System data. Here I see:
SAP_ABA     711     0000
SAP_BASIS     711     0000
PI_BASIS     711     0000
ST-PI     2005_1_710     0003
SAP_BW     711     0000
But this is for ABAP stack only.
In nwa I don't see any HELP -> About
In nwa/sysinfo I don't see any HELP -> About
In Config Tool I can see:
Version: 7.1100.20081120163102.0000
-> is this the j2ee as version including support package and patchlevel info or is this the version of the config tool itself?
In JSPM / SDT in Help -> About I can see:
Client Version 1.4.0
Server Version 1.4.0
Server Port 50418
JSPM Service Version 1.0
JSPM Host Name localhost
JSPM Port 50417
Unfortunately not what I'm searching for as well.
In SAP Management Console in ? -> About I can see:
Version: 7110, 21, 15, 51094
Still not sure where to find the required infos... any other ideas?
Kind regards
Renaud

Support Packages Execution consuming too long time to get complete

Hi,
I installed the SAP Solution Manager 4.0 SR1, I have downloaded the support package stack till june 2007, and applied it. while importing I faced one error XPRA_EXECUTION, Resolved it (by refering sap note:979594) and again click on import. Now it is post 2 and the half day, the execution is still under process. Displaying status as "tp buffer prepared OK". Can anyone tell me how much time it will take to complete.

I have found these errors in tp log can any tell me the solution
WARNING: /usr/sap/trans/tmp/N110531.PRO : cant open
WARNING: : cant open
WARNING: /usr/sap/trans/tmp/N110531.PRO : cant open
WARNING: : cant open
STOP tp_getprots PRO Y 20110531061009
WARNING: /usr/sap/trans/tmp/N110531.PRO : cant open
WARNING: /usr/sap/trans/tmp/N110530.PRO : cant open
WARNING: : cant open
WARNING: : cant open
unable to open the open the files...???

Installing Addon Support package (ST-A/PI)

Hello,
Our Earlywatch report is shouting about needing to upgrade ST-A/PI.
So I've used Maintenance Optimizer to download the package, placed it in EPS/in and un-carred the file.
Then I've then gone to SPAM and tried "Support Package > Load Package > from Application Server"
I've then gone to Display/Define and select component ST-A/PI with the following results:
"No Support Package found for this selection"
I have then tried to Upload from Front End instead of Application Server, with the same results.
I've raised a call with SAP but as usual it's now been 4 days without so much as a change in status so I'm hoping someone on here may have an idea.
Many thanks.

Ok guys, thanks for the replies. I haven't given you enough information.
Let me try fill in some gaps.
The result after I selected Load from App Server is to show me the .PAT file and tell me in the message text that: "OCS file already exists in Inbox. Upload not required"
However, if I select "Display" when "New Support Packages" is selected in SPAM, I see nothing with a note at the bottom stating "No OCS Packages found for this selection"
Maintenance Optimizer seemed to want me to select components I did not want to patch. I had a total of 110 files added to my download basket to download the one file I needed!
That file was titled "Servicetools for other App./Netweaver 04s"
I've already installed the ST-A/PI addon using SAINT. This recommendation is to install Support Package SP02 for ST-A/PI.
The recommendation also appears if I run RTCCTOOL in SA38 as well.
I definitely have the correct permissions to run this and, for the record, I have both the .SAR file and the "uncarred version" sat in EPS/in.
Thanks again.

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 - Portugal

Hello 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

Support Package Manger for EBP/CRM cannot confirm SP ???, 'Package unknown'

I am installing CRM 5.0 SR1 (Windows 32bit/Oracle/NW04s).
I have imported SAP_BASIS SP07 and SP08:
'Queue SAPKB70007 - SAPKB70008 imported successfully according to Standard scen.: Confirm this',
but I cannot confirm (Support Package - Confirm is grayed out). If I start Support Package Manager for EBP/CRM SPAM, I get a window: 'Package is unknown'; after continuing I get an exception 'PATCH_NOT_SPECIFIED'. The status window in SPAM shows:
Software Component: ???
SPAM Status: yellow triangle
Next Action: Confirm
Please help.

I ran into this issue. Upgraded spam from 38 to 42. When I go to env-EBp/CRM, the SPAM Package is unknown error came up
Resolution: go to support package -> import spam/saint update again. It tokk care of the issue. Contuniuing with upgrade.

Import support package

Hi,
I need import package KH60014.SAR. How to import it? I performed unpack this package in /usr/sap/trans directory. After that, I use SPAM t-code. But I can't go to menu option Support Package->Load Packages->From Application Server. Menu "From Application Server" disabled. When I click "display/Change", it appear "OCS package Queue is empty" on status bar.
Please help me!
Thanks
Duypm

As suggested before: Create a new user in client 000 and log on with it before running SPAM/SAINT !
The package KH60014 might have a prerequisite which is not in place.
In transaction SPAM, Mark "New Support Packages" and press "Display".
The new package should appear in the list and you can see if the package has any prerequisite sets.
If you can not find the package iin this way,
you can check if the parameters DIR_TRANS and DIR_EPS_ROOT are correct.
Start transaction SE38, enter program RSPARAM and press F8 twice
(once to run the program and once at the selection screen).
Check the value for DIR_TRANS and DIR_EPS_ROOT.
If you unpacked the package at /usr/sap/trans, then
DIR_TRANS should have the value /usr/sap/trans and
DIR_EPS_ROOT should have the value /usr/sap/trans/EPS.

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

How can I get Support Packages for SAP NSP 2004s?

Hi together,
I have installed the SAP NetWeaver 04s Sneak Preview.
How can I get the support package stacks (SP 6 and SP 7)?
I have only a small OSS-User for 'Freie Berater' (Free Consultants). With that OSS-User it is not possibel to download the the support package stacks SAP Support Portal.
Kind regards, Eva

Hi Daniel,
the sp-level is 5. You can find it via system/status/ in the section 'SAP System data' (klick at the detail-icon).
Web Dynpro for ABAP works with that version. But I would like to have the newest sp-level. Our Web Dynpro teacher gave us some example sources and said that some of them might need sp 6. But I didn't test it.
I have another question: Have you worked in the MARK project a few years ago? There was a collegue named Daniel Kotte.
Kind regards, Eva

Installing support package 16, 17 and 18 for Netwever 7.0 (ECC 6 EHP 3 )

Hi I just want to know if we can directly load SP for Netweaver 7.00. I just went through some doc but they said we can upload SP directyl from SPAM tcode. can we install it from SPAM tcode i have component SAP_BASIS SP 16, 17 and 18. i downloaded SP using Solution manager i am at implementation phase in the same. i am bit confused should i proceed with SPAM ( but i tried upload package option is greyed out there).
any suggestion will be appreciated.
Mani

Hi Mani,
Follow this,
http://help.sap.com/saphelp_nw70/helpdata/EN/a7/a7a932845c11d2b421006094b9ea64/frameset.htm
- 000 client
- modifiable status of client.
- don't use DDIC/SAP*, use a user with full authorization
Question on Appying NW Support Package Stack
Please note that both individual Support Packages and SP Stacks are Non-cumulative. This means that, when you import Support Packages, then you import a gap less series of Support Packages and, if
you use SP Stacks, you also import these without a gap. The only exception is the Support Package for SPAM itself. & Java support packages which comes in SCA format.
Uday, Did you try to copy from what I posted?.. the correct procedure would be to direct to the original link.. not CTRLC & CTRLV!
Regards,
Debasis.
Edited by: Debasis Sahoo on Apr 22, 2009 1:04 PM

Error in xpras when importing support packages in solution manager

Hello,
We are importing support packages in our solution manager and we begun
the process more than two weeks ago and the process is still running.
I have stopped the system and restarted the import again, but it seems
to be the same. The SP queue is:
SAPK-1507EINSTPL
SAPK-1507FINSTPL
SAPK-1507GINSTPL
SAPK-1507HINSTPL
SAPK-1507IINSTPL
SAPK-1507JINSTPL
SAPKB70015
SAPKA70015
SAPKITL426
SAPKIPYJ7F
SAPKW70017
SAPKU50012
SAPKB70016
SAPKA70016
SAPKITL427
SAPKIBIIP9
SAPK-40012INCPRXRPM
SAPK-40013INCPRXRPM
SAPK-40014INCPRXRPM
SAPKNA7012
SAPKNA7013
and there is an error (rc=12) at the method execution step in package SAPKU50012 or in SAPKB70016.
Now, there is an rc 12, but the queue is running, the import queue hasn't cancelled, but it seems to do nothing. The RDDEXECL job log is:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server crosol203 were synchronized
Error Building the ENH TreeObject Type:XHObject Name:EH_FJ_FUBA_PARA_VERS
the job was running for 149.332 seconds and at that moment I stopped the sap system. After restating the system I imported the queue again and now, the process has been running for more than 13500 seconds.
We have checked note number 1142410 and all the modifications were already implemented in the system.
Thanks and best regards,
Ana.

Hello Sunny,
The problem is still happening. I have read and apply all the threads you suggested, nut they didn't resolve the problem:
I have updated the kernel
I have checked table DRSEG and it has no problems.
I don't have any syntax errors so I haven't run the SGEN as I think it doesn't apply.
After changing the kernel I have started the sap system and the job rddexecl has started itself before running again the SPAM and reimporting the queue.
I already have 6 support packages without running the method execution step and I don't know how much time it will consume.
Regards,
Ana

Support Package and Delta/Extractor functionality

Hello Experts,
We have been testing the New GL Totals Delta and Extractor functionalities. Previously when Support Packege 13 was installed, the Delta was bringing incorrect results.
Now we are using Support Pack 15. Now if i post documents in ecc and upload to bi, the Delta is working properly and values match in ecc and bi.
Could you please suggest if there have been any changes or upgradations in the New GL Totals Delta/Extractor functionality between Support Packages 13 and 15.
Thanks and Regards,
Labanya.

Hi,
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895 [original link is broken]
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820 [original link is broken]
thanks,
JituK

How to deal with delta queue when importing Support Package/Kernel Patch

Hi,
From my experience, when importing a Support Package for an installation, the system will issue an error message and get stuck if this Support Package is about to alter the structures used in delta loads.
But I would like to double with you if there is possible that the support packet which is going to alter structure, but no error message. If so, the delta data will be lost.
Do we need to clear down the delta queue every time we import support package?
Anyway, is there anyone have any suggestions or steps regarding this question?
Many Thanks
Jonathan

Hi,
Delta queues during support package upgrade
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820
Effect on BW of R/3 Upgrade
How To Tackle Upgrades to SAP ERP 6.0
/people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
Start with the Why Not the How When You Upgrade to SAP ERP 6.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
Rapid SAP NetWeaver 7.0 BI Technical Upgrade
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
Hope this helps.
Thanks,
JituK

Support packages in status canceled

Similar Messages

Maybe you are looking for