Differences between XI Support Packages

Hi everyone.
Can anybody tell me what are the differences between different XI support packages.
I have SP09 and i would like to know new features in SP14.
Thanks.

Hi Inigo:)
you may have a look over here:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/084c42ff13b430e10000000a155106/frameset.htm
I'll add this link to the XI FAQ in a moment:)
Regards,
michal

Similar Messages

Difference between HR support packs and EHP.

Can anyone tell me the difference between HR support packs and EHP

Hi Harish,
Enhancement Packages- SAP enhancement packages for SAP ERP are optionally installed software innovations for SAP ERP 6.0. They include functional enhancements, industry specific functionality, and simplifications u2013 for example, to the user interface. With enhancement packages, you can easily adopt ongoing SAP innovations at a lower cost than full upgrades. In addition, enterprise services are delivered with enhancement packages.
Support Pack - If the same or similar bug is reported by multiple clients or end users, then SAP recognizes such bug corrects them and collects all these corrections in one place and adds some enhancements to the earlier version of SAP and then calls this as a SUPPORT PACK. In simple words collection of SAP NOTES is a SUPPORT PACK.
Enhancement packages are not support packages: Support Packages contain corrections and legal changes, SAP enhancement packages new functionality.
Do let me know if I helped you.
Thanks,
Padmaja.

Difference Between A Support User and Super User in CRM

Hi All,
May I know what is the difference between a support user and a super user in CRM?
Please advice, thank

HI Plaban
not sure if you answered your own question here?
Change User - by itself would allow update of address data, user parameters, defaults, etc
Assign Object - as you mentioned roles and profiles.
However, if assigning, I think you need to have both actions: change and assign
I recall (ages ago) that change was only the user details and not the role or profiles. As a result, there were a few threads where people had to update the action for the request type of provisioning would not occur.
This is something you could test
Regards
Colleen

Difference between SAP support releases and SAP support package stacks ?

Hi,
Lets take SAP R3 Enterprise 47x200 (my company) as an example.
Looks like there is SAP R3 Enterprise 47x200 release (from release notes) and SAP R3 Enterprise 47x200 SR1 (support release 1).
And there are support package stacks for this release.
What are the differences/similarities between these two ?
Where can I find some document which explains these things as a whole ?
There is enchancement packages introduced in SAP ERP 6.0, how EHP's relate to those two above ?
thanks
Vilius

Hi
Check this link [https://websmp101.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200615320900001087]
For informations on EHP check this [www.service.sap.com/erp-ehp]
Regards
Uday

Difference between implementation, support & upgradation projects

Hello Friends,
I am new to SAP. Can anyone tell me what are implementation, support & upgradation projects..what are the differences between those projects? what is role of ABAP developer in these projects?
Regards,

Hi,
SAP Implementation: SAP Implementation is the whole of processes that defines a complete method to
implement SAP software in an organization. It is based on best practices and case studies from various
literature sources and presents a collection of processes and products that make up a complete
implementation method to allow any organization to plan and execute the implementation of SAP (ERP)
software.The SAP implementation process is made up out of four main phases, i.e. the project preparation
where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase
where the solution stack is created and training is being performed, a functional development phase and
finally a final preparation phase, when the last tests are being performed before the actual go live.
ABAP Developer Role is to prepare the Technical Specification (based on a Functional Specification given
by a Functional Consultant), build the code, Review the code and finally to prepare the Unit Test Cases.
Sometimes ABAPer may be asked to do a technical research for an optimal solution.
SAP Support: After a go live, the application needs a maintenance/support to resolve the issues/tickets raised by the users when using the application.Ticket is like a request for changes/bug fixing or a request for a new
ABAP Developer Role includes bug fixing/change the existing code due to new requirements/build a new code etc.
SAP Upgrade: SAP Upgrade is nothing but upgrading the software with a superior version which has got more advantages when compared to the earlier version.
ABAP Developer Role is to go through transactions SPAU/SPDD to compare the old and new version of the change and finally need to activate the relevant one.Some times might need to work on SAP notes too.
Hope this helps.
Thanks,
Srinivas

Whats the difference between executing a package from SQL and Visual Studio?

Hi,
We have a package that is currently failing to run when deployed to SQL. This has been tried from a schedule and also executed manually both are failing.
I have tried from Visual studio running on various machines (windows 8, server 2012) and in all cases run perfectly.
I am trying to understand the differences between deploying to SQL and running from VS so maybe I can figure out why this is happening.
I have the following errors when I run from SQL.
DTS_E_PROCESSINPUTFAILED - all errors like this point to the 'Sort' tasks in the script
dts_e_processinputerror not enough storage is available
I have tested in four environments and all fail from SQL but not from VS!
Last night I tried from my laptop and executed the package from SQL - it didn't fail but was still running in the morning so I terminated. Note this takes around 20 mins running from VS! why would it be so quick from VS but fail or take so long on SQL?
The test running at the moment is on a server with dynamic memory currently at 14GB. I decreased SQLs RAM to 4GB and it hasn't failed yet but has been running for two hours. Before changing this the package failed after a short time.
I thought it may have something to do with running from a virtual machine but doesn't explain why it couldn't run locally on my laptop.
All ideas welcome :) Many thanks,
Davina

I will try to address issues one by one
The error doesn't seems to be related to SSISDB configuration mode. It may be because of
Change in package definition (please confirm that the package which you are running on your laptop is the same on your msdb? - reload your SQL package from MSDB in BIDS/SSDT and recreate your source and destination components)
As your error message shows, "not enough memory available" (may be because of multicast) - Usually you can override this error by restarting SQL Server [not an optimal solution but it work & if that work it shows that your package fills
the memory - Keep an eye on task manager]
Make sure that your statics on table are updated [run EXEC sp_updatestastics]
Make sure your indexes are not de-fragmented [run rebuild indexes]
If you are dealing with many rows may be 40000 * 12 (because of multicast) = 4,800,000 rows the try to separate package.
Check your excel file format/column data type is correct
Check user permission who is running the job has required permission on folder/file.
Understand that sort is a blocking transformation and it requires all your data in memory before it sorts. so, if there are large number of rows then your complete memory will be occupied.
Difference between Visual Studio & BIDS/SSDT
Nothing much, other than BIDS runs on 32 bit while jobs on 64 bit (but there run time environment are configurable, though)
There shouldn't be any performance difference until your
package is on network location because transferring data to the network may slow the package. If package runs on SQL Server it uses SQL buffer pool to fetch data via SQL statement and then SSIS works on its own memory allotment.
Hope this will help you to understand and fix the issue.
Glad to help! Please remember to accept the answer if you found it helpful. It will be useful for future readers having same issue.

Difference between prefer-application-packages in weblogic.xml and weblogic-application.xml?

Hi!
When deploying a WAR to WebLogic 10.3.5, what is the difference between the prefer-application-packages element in the files weblogic.xml and weblogic-application.xml?
In my WARs WEB-INF/lib/ I have a JAR that contains classes that are already provided by the container (but older versions).
If I do not use prefer-application-packages then my app gets the classes provided by the container.
If I use prefer-application-packages in weblogic.xml then I get the classes from WAR/WEB-INF/lib which is expected.
But if I use prefer-application-packages in weblogic-application.xml then I get the container versions. Why?
Is there a difference between those two options?
The exact data I use is:
(foo.bar.* is the conflicting package; I add or remove the linex marked with XXXX)
WEB-INF/weblogic.xml :
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app
    xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
    <wls:container-descriptor>
        <wls:show-archived-real-path-enabled>true</wls:show-archived-real-path-enabled>
        <wls:prefer-application-packages> 
            <wls:package-name>foo.bar.*</wls:package-name> 
        </wls:prefer-application-packages> 
        <wls:prefer-application-resources>
            <wls:resource-name>META-INF/services/some....</wls:resource-name>
            <wls:resource-name>META-INF/services/unrelated...</wls:resource-name>
            <wls:resource-name>META-INF/services/stuff...</wls:resource-name>
        </wls:prefer-application-resources>
    </wls:container-descriptor>
    <wls:jsp-descriptor>
        <wls:page-check-seconds>-1</wls:page-check-seconds>
        <wls:precompile>true</wls:precompile>
        <wls:precompile-continue>true</wls:precompile-continue>
        <wls:keepgenerated>true</wls:keepgenerated>
    </wls:jsp-descriptor>
    <wls:session-descriptor>
        <wls:persistent-store-type>replicated_if_clustered</wls:persistent-store-type>
    </wls:session-descriptor>
</wls:weblogic-web-app>
META-INF/weblogic-application.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application
    xmlns="http://xmlns.oracle.com/weblogic/weblogic-application"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.2/weblogic-application.xsd">
    <application-param>
        <param-name>webapp.encoding.default</param-name>
        <param-value>UTF-8</param-value>
    </application-param>
    <xml>
        <parser-factory>
            <saxparser-factory>
                org.apache.xerces.jaxp.SAXParserFactoryImpl
            </saxparser-factory>
            <document-builder-factory>
                org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
            </document-builder-factory>
            <transformer-factory>
                org.apache.xalan.processor.TransformerFactoryImpl
            </transformer-factory>
        </parser-factory>
    </xml>
    <prefer-application-packages>
        <package-name>foo.bar.*</package-name> 
        <package-name>javax.jws.*</package-name>
        <package-name>javax.xml.ws.*</package-name>
        <package-name>org.apache.cxf.*</package-name>
        <package-name>antlr.*</package-name>
        <package-name>org.xmlsoap.schemas.wsdl.*</package-name>
    </prefer-application-packages>
</weblogic-application>

weblogic-application.xml has no meaning in WARs, it is only used in EARs.

Re: Difference between SPS and SP

Hi Guys,
What is the difference between SPS(support package stack) and SP(support package)
Regards,
Anand

Hi Anand:
Take a look at this presentation below, note the differences between ABAP Support Packages (slide 2) and Support Package Stacks (slide 3).
"SAP Support Package Stacks".
https://websmp104.sap-ag.de/~sapidb/011000358700004121632003E
Since the document is available on the SAP Marketplace you'll need an "S" account.
The link below also has useful information:
"Types of Support Packages"
https://websmp207.sap-ag.de/~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=00200797470000066842
Regards,
Francisco Milán.

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

Diff between production support and support

dear sap gurus,
can any one explain about the difference between production support and support
thanks in advance
dreddy

Hi,
Though there are no strict line of difference, it can be put in different perspective.
Production Support: Involving the day to day problem solving like Job monitoring,Job fails,Error entry by end users & their impact,issues involving while data transfer between interfaces ...etc
Support : Could be like a developmental one involving new change requests with configuration change/Code Change & requires testing & user acceptance & then moving to production.
Regards,
Vengat
Reward if found useful

Java - difference between "critical" and "software installer

I would like to push out the latest java updates to out workstations via ZCM patch management, however I am confused be the difference between the update packages available. The machines are windows 7 with ZCM v11.2.0 and already have a (slightly older) JRE installed on them. The ZPM java package labeled as impact type "critical" states the following in the notes:
"All web browsers are required to be shut down in order for Java JRE to be updated successfully"
The ZPM package labeled as impact type "software installer" has nearly identical installation notes, save for no web browser must be not running disclaimer like above.
Since 95% of our user base in the school district is most likely going to be using a web browser at any given time, I would give the success probability of the "critical" option as very low. Is it OK to use the "software installer" impact package? Is it truly not dependent on browsers being closed, or was that an oversight in the notes? What method do any of you use for reliable java updates?

I stopped using ZPM for Java and Flash installs. I actually right an AutoIT script that I deploy out to my laptops via bundle. It closes the browsers, uninstalls older versions of Java, and then installs the latest version I provide. What I found on some of our Java (browsers) based apps, specifically the gradebook and attendance programs, the ZPM deployment would install the latest with the older versions as well. This caused masive issues with after three updates those programs stop working.
I still have some deployment issues where a teacher will have java based failures or a failure to install the latest version correctly. But compaired to what was done before I have cut my failures in half if not more.
Nice thing is I can still view the Patch deployment in Patch Management as this deployment method is in process.
Richard

Difference between support packages&kernels&add ons

can anyone help me out to know the difference b/w sp's,kernels & addons n also the procedure to apply them plz.
thanks in advance:
pcsagar

Hi chandra shekar,
Procedure to apply kernel patch.
1> Down load the latest kernel patch from the link
https://websmp105.sap-ag.de/patches
Down load two file for your kernel
Take #Database independent and other file be according to your database
#Database independent file will be SAPEXE<....>.SAR
File for your database will be SAPEXEDB<....>.SAR
2) Put these files in some location on the server.
3)Take backup of of the existing kernel.
4)stop sap
5)stop oscollector SAPOSCOL
6) Unpack the file using tool SAPCAR
7) COPY the unpacked files to the kernel directory with overwright option
start saposcol and then sap
Check the new version in sm51.
You can check below note for more information.
Note 19466 - Downloading SAP kernel patches
Applying support packages.
Down load the support package from the link
https://websmp105.sap-ag.de/patches
for applying check below links
http://help.sap.com/erp2005_ehp_03/helpdata/EN/a7/a7a932845c11d2b421006094b9ea64/content.htm
ADD-ON same procedure and you use -t-code SAINT
Regards
Ashok

Difference between Crystal Reports Runtime Packages

Post Author: blueyoj
CA Forum: Deployment
Hi,
We develop an application using Microsoft .NET Framework 3.0 and we need to deploy Crystal Report viewer as a part of our setup package. Under Runtime Packages page, I see the following merge modules and MSI.
Crystal Reports 2008 Crystal Reports XI Release 2 Crystal Reports XI Crystal Reports 10 Crystal Reports 9 Crystal Reports for Visual Studio .NET 2005 Crystal Reports for Visual Studio .NET 2003 Crystal Reports for Visual Studio .NET 2002
What is the difference between Crystal Report xx (version) and Crystal Reports for Visual Studio .NET 200x?
If our application should support both 32-bit and 64-bit, does it mean that we need to create two separate setup packages and include proper Crystal Report? I can't find any merge module that supports both.

Babita,
request you to post the same in the BO forums for more relevant answers...
Arun

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.

Difference between service pack and support pack

Hi,
what is the exact difference between service pack and support pack. Are they same?
The version details presnt in integration builder -> help-> inforamtion of my XI server are as follows :
Service pack: 09
Release: 645_VAL_REL
does it mean that the both support package and service package for my XI server are 09?
thanks in adavance
regards
Jagruthi

1. A service pack (in short SP) is a collection of updates, fixes and/or enhancements to a software program delivered in the form of a single installable package. Service packs are usually numbered, and thus shortly referred to as SP1, SP2, etc. It is notable that they may bring, besides bug fixes, entirely new features.
http://help.sap.com/saphelp_nw04/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
Service packs in 2004 and 2004s;
in 2004 - in 2004s
SP12 & < - SP04 http://XI 3.0
SP13 + 14 - SP05 http://PI 7.0
SP15 - SP06
SP16 - SP07
SP17 - SP08
SP18 - SP09 and so on...
2) Support pack -
http://help.sap.com/saphelp_nw04s/helpdata/en/9e/5bc53f3e0f0228e10000000a114084/frameset.htm
For the ABAP parts of usage type PI, this is the implementation of support packages. For the Java parts, the deployment with the Java Support Package Manager (JSPM) is used.
You can find currently available support packages on SAP Service Marketplace at service.sap.com/sp-stacks.
A description of how to apply support packages is available in SAP Note 879289.

Differences between XI Support Packages

Similar Messages

Maybe you are looking for