Application of support packages

Hi
I need to know, if I modify the descriptions in the standard product types TRM (Treasury and Risk Management), when applying the Enhancement Packages or Support Packages, these amendments would have any change?.
Thanks for your help
Marco Cubillas
IAM Treasury

Hi Marco
If you add a new Enhancement Package the description of the products do not change. The EHP only adds new fuctionalities and also new products which have to be customizied first before you can use them.
Regards
Juerg
+41794096439

Similar Messages

Solution manager Support Package 19 & 20

Dear Expert,
Recently I installed the solution manager,
But there is one DVD call Support Package 19 & 20,
I'm not sure how to upgrade the package to SLM.
As I knew,
there is a folder call "DATA",
I tried to used SAPCAR tool to decompress it into usr...EPS/in folder.
and the .SPA file use JSPM tool to update it to the SLM system.
but....when i used SAPCAR to decompress , it showed a error message below.
SAPCAR: could not convert from UTF8 string
Can any one helps me ?
And What is the SOP to update SPS 19~20??
Regards
Jack Lee

You can get SolMan SPS19/20/21 from http://service.sap.com/swdc:
Support Packages and Patches - Entry by Application Group
Support Packages and Patches - Entry by Application Group" SAP Technology Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1
Link to SP Stack Application
If you are getting errors from sapcar I'd recommend to first check to get the latest sapcar version and if it does not hep to redownload the file
Nesimi

Support Package in CRM

Hi Experts,
Iam working on some CRM datasource. I would like to know what teh Current support package is intalled in the CRM System.. can anyone explain the steps to view the current support package installed in the system please.
Thanks,
DV

hi Dave,
PI_BASIS, you will see e.g 2005_1_700, means PI 2005.1
http://help.sap.com/saphelp_nw2004s/helpdata/en/3d/ad5d044ebc11d182bf0000e829fbfe/frameset.htm
Software Component Name
SAP_APPL APPL Support Package
SAP_BASIS Basis Support Package
SAP_ABA Application Interface Support Package
SAP_HR HR Support Package
SAP_BW BW Support Package
BBPCRM BBP/EBP and CRM Support Package
hope this helps.

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

What GUI to use web application designer in BI 7.0 without support package

I use BI in my ECC 6.0 system.
I use tried both GUI 7.1 and GUI 6.40 to logon web application designer.
But system display the message please logon to a Netweaver BI 7.x system. System A11 does not have a mimumium version required 7007.
My system seems to be 7000, so what GUI is suitable to use for WAD?
Thanks
Giang

Hi,
It could be problem with either Support package which you are using for BI or Front end patch which you need to install for GUI.
please check with minimal installations and let me know with current support package and FEP you are using.
Regards
Suresh

Undoing changes made by support package application

Hi
Is there a way to undo changes made to repository objects and dictionay objects after you have imported a support package.
Let us consider this with an example. Let us assume that there is a standard SAP report called S1 v1. Which after a support package application and after confirming the queue it becomes S1 v2. Now if for some reason after say 2-3 days we are not comfortable with S1 v2 and want S1 v1 again can we get back the old standard SAP report. If so then how?
Also if there is a change made in a Dictionary object, is there a way to revert these changes on a similar line? Id so then how.
Thanks
Rohan

Hi Lokesh,
If you have maintained versions for perticular report then you can revert it back to the previous version.
Ask your ABAPer for the same.
You can always retrieve the previous version if you have maintained the version.
It is applicable for the dictionary objects too, but you may loose data in case of changing version for database tables.
Regards,
Payal

Embedded BI - System Upgrade, Support Package application and so on

Since Netweaver '04, SAP R/3 and SAP BW/SEM were separated system.
Now, with Netweaver 2004s and the "embedded BI", they are unified on the same installation.
1)The upgrade operations for R/3 and BW are separated or in the same package?
So, support package installation is cumulative?
2)When R/3 is down for upgrade/support pack---> BW is Down?
When BW is down for upgrade/support pack---> R/3 is Down?
3) System crash is cumulative?
Points for every useful answer,
Thank you, Claudio

The whole scenario depends upon if you are using embedded BI or a stand alone BI.
1)The upgrade operations for R/3 and BW are separated or in the same package?
So, support package installation is cumulative?
In either case upgrade operations are separated
2)When R/3 is down for upgrade/support pack---> BW is Down?
When BW is down for upgrade/support pack---> R/3 is Down?
embedded BI - Yes as being on the same instance
stand alone No, upgrade is independent on a technical/application standpoint
3) System crash is cumulative?
embedded BI - Yes
stand alone NO

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.

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

Applying BASIS support package 14 on IDES (DB2 & Windows)

Hi all,
   I am trying to apply BASIS support package on IDES. Currently process is running on IMPORT 2 step. I run in diaglog and it was continuously showing MOVE NAMETABS at the end. and in ST22 I see thousands of dumps being generated and almost all are related to    SYNTAX_ERROR
Short text
    Syntax error in program "SAPLSALC ".
at happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSALI" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSALC " in include "LSALCU65
   " in
line 1:
"Function "SALC_INFO_GET_TREE" not found in Function Library."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLSALI" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Can anyone of you help me on this issue.
AWAITING REPLY
Thanks

>    I am trying to apply BASIS support package on IDES. Currently process is running on IMPORT 2 step. I run in diaglog and it was continuously showing MOVE NAMETABS at the end. and in ST22 I see thousands of dumps being generated and almost all are related to    SYNTAX_ERROR
There are a few known issues with KB70014, those are documented in
Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
Markus

Error in Applying Java support packages through JSPM

Hi All,
While Applying support packages, Package CAF 7.00 SP 13 is through an error
help required.
                   For detailed information see the log file of the Deploy Service.
07/12/05 21:55:26 - ***********************************************************
Dec 5, 2007 9:55:26 PM   Info: End of log messages of the target system.
Dec 5, 2007 9:55:26 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 5, 2007 9:55:26 PM   Error: Aborted: development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0', grouped by software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafUIptn~common..
Reason: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/cafUIptn~common. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Dec 5, 2007 9:55:26 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:28 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:28 PM   Info: Starting: Update: Selected software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0' updates currently deployed software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956''/'0'.
Dec 5, 2007 9:55:28 PM   Error: Aborted: software component 'CAF'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070809092315''/'0':
Failed deployment of SDAs:
development component 'caf/UI/ptn/common'/'sap.com'/'MAIN_APL70VAL_C'/'1497914'/'0' : aborted
Please, look at error logs above for more information!
Dec 5, 2007 9:55:28 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:30 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:30 PM   Info: Starting: Update: Selected software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0' updates currently deployed software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.1.20060302145618''/'0'.
Dec 5, 2007 9:55:30 PM   Error: Aborted: software component 'LM-TOOLS'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.13.0.20070906104634''/'0':
No further description found.
Dec 5, 2007 9:55:30 PM   Info: Starting to save the repository
Dec 5, 2007 9:55:32 PM   Info: Finished saving the repository
Dec 5, 2007 9:55:32 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 5, 2007 9:55:32 PM   Error: -
At least one of the Deployments failed -
Regards,
Prashant.

Hello Prashant.
Check this supporting SAP note 1010640. It will solve your problem.
This is typical problem when you upgrade from < SP8 to higher version.
You need to Undeploy the CAF components from the system using SDM first and then reply the patches from JSPM.
It should go with out errors.
Let us know if this worked.
*Reward points for helpful answer.
Regards,
Prashant P.

What minimum Support Package level is needed in BW 3.5 / 640 to be able to

Hello Experts,
A quick question:
what minimum Support Package level is needed in BW 3.5 / 640 to be able to run the SAPGUI 7.10 (including BW add-ons)?
I am also searching at my end.
<removed_by_moderator>
Read the "Rules of Engagement"
Best Regards
Sachin Bhatt
Edited by: Juan Reyes on Jun 29, 2009 11:15 AM

Hi,
Refer the below link
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=30625
A. FEP stands for Front-End Patch. FEPs are the patches that SAP releases for the BW front-end components of the SAP GUI.
They can be downloaded from the SAP Service Marketplace (SMP login required), browsing to the following locations:
BW 3.5 Addon can be found at Downloads -> SAP Support Packages and Patches -> Entry by Application Group -> SAP Frontend Components -> BI ADDON FOR SAPGUI -> BW 3.5 ADDON FOR SAPGUI 7.10-> Win32.
BW 7.0 Addon can be found at Downloads -> SAP Support Packages and Patches -> Entry by Application Group -> SAP Frontend Components -> BI ADDON FOR SAPGUI -> BI 7.0 ADDON FOR SAPGUI 7.10-> Win32.
Let us know if u have any issues.
Regards,
Ravi

Syntax Error while applying support package stack 8

I get the following short dump while I was applying support package stack 8. I'm at the latest saint version 34
Runtime Errors         SYNTAX_ERROR
Date and Time          23.07.2009 14:09:27
Short text
     Syntax error in program "CL_DYNPRO_PROPERTY_BAG========CP ".
What happened?
     Error in the ABAP application program.
     The current ABAP program "SAPLSCR2" had to be interrupted because it con
     a statement that cannot be executed.
     In the include "CL_DYNPRO_PROPERTY_BAG========CM009 " in the line 176 of
      program "CL_DYNPRO_PROPERTY_BAG========CP " the following syntax
     errors occur:
     "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
     "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
     "PTEXT"."
     Author and last person to change the include are:
     Author "SAP "
     Last changer "SAP "
Error analysis
     The following syntax error was found in the program
      CL_DYNPRO_PROPERTY_BAG========CP :
     "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
     "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
     "PTEXT"."
Trigger Location of Runtime Error
     Program                                 SAPLSCR2
     Include                                 LSCR2U47
     Row                                     31
     Module type                             (FUNCTION)
     Module Name                             RS_SCRP_PROP_ADD_TO_PROP_LIST
1 FUNCTION RS_SCRP_PROP_ADD_TO_PROP_LIST.
2 *"----
3 ""Lokale Schnittstelle:
4 *" IMPORTING
5 *"     REFERENCE(P_TEXTFIELD) TYPE D021S-FNAM OPTIONAL
6 *"     REFERENCE(P_TOOLTIPTEXT_TEXTELEM) TYPE CHAR3 OPTIONAL
7 *"     REFERENCE(P_TOOLTIPTEXT_VARIABLE) TYPE D021S-FNAM OPTIONAL
8 *"     REFERENCE(P_KEEPTAB) TYPE SEU_BOOL OPTIONAL
9 *"     REFERENCE(P_DISABLEIMPLICITLABELS) TYPE SEU_BOOL OPTIONAL
10 *"     REFERENCE(P_BARCODEINPUT) TYPE SEU_BOOL OPTIONAL
11 *" CHANGING
12 *"     REFERENCE(P_PROP_LIST) TYPE PROP_LIST
13 *"----
14
15 data: l_prop type prop_line,
16       l_prop_list type prop_list,
17       l_string type prop_str.
18
19 * Property TextField
20 * -
21
22 if p_textfield is supplied.
23   clear l_prop_list.
24   clear l_prop.
25   l_prop-name   = sprop_c_tag_textfield_name.
26   l_prop-syntax = sprop_c_syntax_content .
27   l_prop-value = p_textfield.
28   append l_prop to l_prop_list.
29 * Zusammensetzen eines Strings der Form
30 * <Name>value_1</Name> ... <Name>value_n</Name>
>>   call method cl_dynpro_property_bag=>fill_prop_list_into_properties
32     exporting
33       prop_list = l_prop_list
34     importing
35       properties = l_string.
36 * Property-Eintrag zusammensetzen
37   clear l_prop.
38   l_prop-name   = sprop_c_tag_textfield.
39   l_prop-type   = sprop_c_type_string.
40   l_prop-syntax = sprop_c_syntax_content .
41   l_prop-value = l_string.
42 * Property-Eintrag in PROP_LIST aufnehmen/ersetzen
43   read table p_prop_list transporting no fields
44       with key name = l_prop-name.
45   if sy-subrc = 0.
46     modify p_prop_list index sy-tabix
47         from l_prop.
48   else.
49     append l_prop to p_prop_list.
50 endif.
Can anyone help me? I now get the same error with executing other transactions as well.

Hi,
Please let us know the component which you are trying to apply. Is it BASIS or ABAP or BW and also let us know the version?
I hope you are applying the BW patch 8, as per SAP's recommendation we need to apply both 8 an 9 patch of BW at the same time. If not we need to apply some notes which you could find in the service market place. Once you apply the notes, you can proceed with the SP application.
Regards,
Varadhu

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

PAT file not shown in Support package manager

Hi All,
We had to create a custom BAPI to achieve an functionality in our product.
We are doing this for the first time.
As a standard procedure we followed the AAK (Assembly Add On ) toolkit to create the deploy-able.
Finally in the consolidation system we could see the following PAT file created in the out directory.
QA70020777848_0000002.PAT
I copied the file to the in directory of the production SAP server where this needs to be deployed.
I ran the transaction SPAM on the server.
Load packages from Application server
QA70020777848_0000002.PAT SAPK-170COINCOMPANY1 @EB\QUpload Already Occurred@ 0004 OCS file already exists in inbox. Upload not required.
IT decompresses the file properly.
Now the problem occurs ahead.
IF i click on the New Support package nothing is shown visible .
Am i missing any steps here.
Regards
Manoj

Got the solution in fact it's not a solution it's just an awareness on how the disks are available in fail-over cluster manager.
1) All the available disks are shown in fail-over cluster manager "storage".
2) While installation it asks us to add available disks for SQL Server then add accordingly. (Ex: E:drive for data files and L:drive for Log files)
3) Once the installation is done you see those disks in MSSQL (SQL Server) group.
Means when you click on Active node it should show you MSSQL (SQL Server) group in which you can find network name, network ip, E: & L: Drives, SQL Server and Agent services.
Note: MSDTC and Quorum are also clustered disks which can reside (Preferably Active Node) in any of the nodes but automatically fail-overs to active node in case of any passive node failures.
Regards,
Kalyan
Grateful to your time and support. Regards, Shiva

Application of support packages

Similar Messages

Maybe you are looking for