Basis Support package level of ECC 6.0

Dear All,
I use SAP Version ECC 6.0 (700 Kernel, 64bit) Database SQL.
My question is what should be the support package level of ECC 6.0? SAP recommends for the latest support package level always. But, whether the latest support package level will be stable?
We are in the blue print stage now, I haven't received any requirement from the fuctionals for the support package upgrade.
We have modules like, SD, MM, FI, FICO, HR, PS and CS.
Anyone worked with these modules who can provide me, the particular components related to these modules with the stable support pack level.
Thanks in Advance,
Abu Sandeep

Hi,
Yes, for a new installation always go for the last support packages.
After going live, NEVER, NEVER apply support packages without qualifying them for YOUR company in a test system. It takes a lot of time to do non regression tests but it is mandatory IMHO.
Regards,
Olivier

Similar Messages

What are the components & support package levels required in 4.7 to extract

Hi All,
In my landscape we have ECC 6.0 and 4.7EE, as of now we are extracting data from ECC 6.0 to BI 7.0.Now we have requirement to extract data from 4.7EE.
Could you please suggest me what are the components & support package levels required in 4.7 to extract data from BI 7.0
i am copying current compnents and support package level below
SAP_BASIS            620        | 0065 | SAPKB62065           | SAP Basis Component                                         |
SAP_ABA              620        | 0065 | SAPKA62065           | Cross-Application Component                                 |
SAP_APPL             470        | 0025 | SAPKH47025           | Logistics and Accounting                                    |
SAP_HR                 470        | 0113 | SAPKE470B3           | Human Resources
ABA_PLUS            | 100        | 0009 | SAPKGPBA09           | PLUGIN ZU ABA_PLUS                                          |
EA-IPPE                  200        | 0013 | SAPKGPIB13           | EA-IPPE 200 : Add-On Installation                           |
PI                   | 2004_1_470 | 0001 | SAPKIPZI51           | R/3 Plug-In (PI) 2004.1 for R/3 Enterpri                    |
PI_BASIS             | 2004_1_620 | 0003 | SAPKIPYI53           | Basis Plug-In (PI_BASIS) 2004_1_620                         |
ST-PI                | 2008_1_620 | 0000 |      -               | SAP Solution Tools Plug-In                                  |
EA-APPL              | 200        | 0007 | SAPKGPAB07           | SAP R/3 Enterprise PLM, SCM, Financials                     |
EA-DFPS              | 200        | 0007 | SAPKGPDB07           | SAP R/3 ENTERPRISE DFPS                                     |
EA-FINSERV           | 200        | 0007 | SAPKGPFB07           | SAP R/3 Enterprise Financial Services                       |
EA-GLTRADE           | 200        | 0007 | SAPKGPGB07           | SAP R/3 Enterprise Global Trade                             |
EA-HR                | 200        | 0011 | SAPKGPHB11           | SAP R/3 Enterprise HR Extension                             |
EA-PS                | 200        | 0007 | SAPKGPPB07           | SAP R/3 Enterprise Public Services                          |
EA-RETAIL            | 200        | 0007 | SAPKGPRB07           | SAP R/3 Enterprise Retail
Thanks & regards
Mani.
Edited by: manohar kumar on Nov 18, 2010 7:36 AM

Hi,
As far as my view there is no such dependancy as our customers are running in same Environemnt (R/3 4.7 EE and BI 7.0) .
Are you facing any problem durng extraction or its just a proactive approarch .
I hope extraction will work with your current landscape.
Regards,

Xi/Pi Support Package Levels

Hi All,
We have a query on Support Package levels in the landscape.
Is it mandatory that XI/PI system Support Packages needs to be in Higher level than the other systems (BI 7.0,ECC 6.0 with EHP4,CRM,SRM etc....) in the Landscape.
Please clarify.
Thanks
Sunayna

Hi Juan ,
Thanks for your quick response.
We heard from one of my Tech leads .So just for confirmation we want to know the same.
Regards
Sunayna

Support package level is not sufficient

Hi,
In IDES server we are using Product version: Ecc 6.0 EHP3,
Here only 10 Support Package level required, but we have 11 package levels.
So those are sufficient.
Still when creating purchase order and sales order, the error is appearing,
"note 1600482: Support package level is not sufficient "
below is attachment of error. I am sharing the Screenshot PFB.
What to do??
I have searched but couldn't find the solution..
Regards
Dewanshu Dutt Mathur

Hello Dewanshu,
The note specifies the following:
If you are not sure whether or not you are using this specific functionality, we strongly recommend that you run the check report included in the related SAP Notes 1600090 and 1601021. The check reports allow you to easily check whether this specific pricing functionality is being used in your system(s).
Also,
it further specifies
If you have any questions regarding this Note, you can contact us by creating a support ticket under the XX-PROJ-IMS-HA component identified above.
So I hope you are creating an OSS message under the component described above.
Regards,
Siddhesh

Support Package Level

Hi:
How can I find a difference between Support Package level 111 and 140 for SAP ECC 6.0.
I would appreciate help.
Thanx

Check
http://service.sap.com/patches
--> SAP Support Packages in Detail
In the new Window you can generate a "side effect report" that will show you implications.
Another way is to click on the name of the support package in the download area and you will see all the notes that are contained in that support package.
Markus

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

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

Error in "Test IMPORT" during applying BASIS Support Package

Hi All,
I'm applying basis support package from SAPKB70014 to SAPKB70018,
now it hangs in Import phase: TEST_IMPORT, there maybe something wrong with the import object.
For detail screenshots, please kindly have a look at URL: http://nickfiles.150m.com/Question_1.html
And for the detail import log, please have a look at http://nickfiles.150m.com/SAPPB70015.html.
I think the root cause is located in:
2EETW165 Function "TMW_TAOAGENT (TMW_TAOINTERFACE|01)" does not fit into the existing function group "(TMW_CLIENT_INTERFACES|06)".
2 ETW167 Please transport the whole function group.
But I do not know how to solve it. Could anyone help me?
Thank you very much.
Best regards,
Nick

Hi Nick,
This is the solution to your Issue..
Note 1156706 - Function TMW_TAOAGENT (TMW_TAOINTERFACE 01) does not fit...
Other SAPnote you can read .. for your help..
Note 42379 - SPAM aborts at step TEST_IMPORT
Note 1092979 - TMW_TAOAGENT: Repairing function group after SAPKB70013
Hope it will solve your issue ....
All teh best !!

Official Support from SAP on Support package levels

I have NW7 Dual stack system. Currently at SP10
Looking for an "official Policy" on supported SP levels from SAP, if it exists already. Please help me by providing a link that information or a document if it exists.
We are working on an ongoing infrastructure support policy for this installation.
Thanks in advance.
Vasu

You can run a certain level of support packages as long as you can live with the "deficiencies" resulting out of that. You can run on the initial installed level if you can deal with the fact, that you will need to apply a LOT of notes in case you run into an error (because of dependent notes because of the low support package level).
There may also be cases where it´s impossible to provide a correction by note (e. g. table changes) and where corrections can only be delivered by support packages.
Last but not least the law may force you to install a certain level (e. g. fiscal year change) to get the newest (and correct) data out of the system for all kinds of changes that may be necessary to comply the law.
Basically you can leave your system on a certain support package as long as you wish but it may become difficult or even impossible to give you a solution if more than an ABAP code correction is necessary.
This is especially true on dual stack systems where a change in the portal may force you to upgrade your complete backend to a certain level because there the ABAP + Java stack must be in sync --> one of the reasons why we totally avoid dual stack installations.
Markus

Java Add-in System Copy - same Java Support Package levels ?

Hi,
I'm looking at performing a standard SAP Netweaver 04 SAP Web Application Server system "refresh" procedure. I plan to copy the production system ( SAP WAS 640 ABAP+Java addin )to an already installed QA system that was installed originally exactly the same as Prod. Both have the same components installed and the ABAP stack Support package levels are identical. What I've found is that the Java Add-in Support package levels vary. Is it possible to perform the system copy "refresh" if the Java components differ. ( Prod J2EE is 640 SP13, QA is SP14 and Adobe & ESS/MSS components differ ).
I've looked through the system copy guides and the NW04 SR1 system copy OSS note 785848, but can't find anything about this situation.
Hopefully someone else out there can tell me if it's possible, without first patching Production to the same levels as the QA system being overwritten.
Regards,
Brian.

Hello,
u can do that w/o applying the patch ..but after doing system copy u have latest SP13 as of u r PRD server instead of SP14 in QA....if required then u can apply it again in QA....SP14.
So if u not got my point then tell me...
thanks..
reward points..

Service Release (SR) - which Support Package Levels?

Hello,
I have a general question in terms of Service Releases of a SAP solution:
Is there an easy way to find out on which Support Package Level (or Support Package Stack) a Service Release (SR) of a SAP Solution (or NetWeaver itself) is based?
Can I get this information in the SAP Service Marketplace?
Example: mySAP <solution> SR1 is based on Support Package Level <nn> of component <comp1> and Support Package Level <nn> of component <comp2>.
Any hint is appriciated.
Thanks!
Heiko

Hi Heiko,
You can find information on the SPS and SR releases/version in the service
market place under NW2004S - Release Specific Information - Support Package
Stacks information. This page will tell you the following;
SPS 11 Calender Week 10, 2007 (delayed) expand/hide
Support Package Stack 11 was planned for calendar week 06 and is postponed until calendar week 10.
Planned Features
Please take a look at this preliminary list with the new features planned for Support Package Stack 11.
SPS 10 November 27th, 2006 expand/hide
Download
Download SP Stack 10
Information sources
SP Stack Guide 10
Release Notes SP Stack 10
SR2 December 4th, 2006 expand/hide
SAP NetWeaver 2004s Support Release 2 (SR2) is a new installation and upgrade version (a new set of DVDs) including corrections (and features) provided with SP Stacks 01 to 09. It is a significant step towards a simpler installation of SAP NetWeaver 2004s up to and including SP Stack 09.
Since SAP NetWeaver 2004s SR2 is based on SP Stack 09 the next SP stack to be applied will be SP Stack 10.
Support Release 2 was planned for calendar week 47 and is postsponed until calendar week 49.
SPS 09 September 5th, 2006 expand/hide
Download
Download SP Stack 09
Information sources
SP Stack Guide 09
Release Notes SP Stack 09
SPS 08 June 27th, 2006 expand/hide
Download
Download SP Stack 08
Information sources
SP Stack Guide 08
Documentation Patches -> SPS 08.
Release Notes SP Stack 08
SPS 07 April 11th, 2006 expand/hide
Download
Download SP Stack 07
Information sources
SP Stack Guide 07
Documentation Patches -> SPS 07.
Release Notes SP Stack 07
SR 1 April 7 th, 2006 expand/hide
SAP NetWeaver 2004s Support Release 1 (SR1) is a new installation and upgrade version (a new set of DVDs) including corrections (and features) provided with SP Stacks 01 to 06. It is a significant step towards a simpler installation of SAP NetWeaver 2004s up to and including SP Stack 06.
Since SAP NetWeaver 2004s SR1 is based on SP Stack 06 the next SP stack to be applied will be SP Stack 07.
Shipment
Please note that since the release of SAP NetWeaver 2004s SR 1 on April 7, 2006, SAP NetWeaver stand-alone customers who order SAP NetWeaver 2004s now receive the SAP NetWeaver 2004s SR1 software package instead. SAP NetWeaver 2004s SR1 will not automatically be shipped to customers who have already received SAP NetWeaver 2004s prior to this date.
SPS 06 Jan 31st, 2006 expand/hide
Download
Download SP Stack 06
Information sources
SP Stack Guide 06
Documentation Patches -> SPS 06.
Release Notes SP Stack 06
SPS 05 Dec 15th, 2005 expand/hide
Java part of Support Package Stack 05 was postsponed to December 15th.
Download
Download SP Stack 05
Information sources
SP Stack Guide 05
Documentation Patches -> SPS 05.
Release Notes SP Stack 05
The interesting bit is that SR1 was released in April; while SPS6 was available in
January. The same goes for SR2; released in December; while SPS9 was
available in September.
There is a gap of 3 months between the SPS was released and the SR is released
I assume that patches that have been released for the SPS are included in the SR
therefor a system that has SPS6 or SPS9 applied is not neccisarily the same as
SR1 or SR2.
Hope this helps...
Kind regards,
Walter

BI support package level?

HI all ,
How to know the SAP BI system support package level .
regards ,
Srinivas .

menu system, choose status. in the middle right you have the box 'sap ssytem data'. hit the detail icon. in the following pop up search for sap_bw. the number in column 'level represent the last support package implemented
M.

Support Package level in FM

Could anyone tell us which is the last level of Support Packages in SAP R/3 Enterprise Public Services ECC 6.0?
Thanks in advance.

Hi,
As far as I know, the latest release is SAPKGPPD11.
Better check with your Basis people...
Best regards,
Shahaf Yaari

Suggested Support Pack Level for ECC 6.0 Upgrade - Target

Hi ,
Can someone give us the suggested support pack level for the ECC 6.0 system after the upgrade.
Our current patch level is:
SAP_ABA     700     0012     SAPKA70012
SAP_BASIS     700     0012     SAPKB70012
PI_BASIS     2005_1_700     0012     SAPKIPYJ7C
ST-PI     2005_1_700     0003     SAPKITLQI3
SAP_BW     700     0014     SAPKW70014
SAP_AP     700     0009     SAPKNA7009
SAP_APPL     600     0010     SAPKH60010
SAP_HR     600     0013     SAPKE60013
EA-IPPE     400     0008     SAPKGPID08
EA-APPL     600     0008     SAPKGPAD08
EA-DFPS     600     0008     SAPKGPDD08
EA-FINSERV     600     0008     SAPKGPFD08
EA-GLTRADE     600     0008     SAPKGPGD08
EA-HR     600     0013     SAPKGPHD13
EA-PS     600     0008     SAPKGPPD08
EA-RETAIL     600     0008     SAPKGPRD08
FINBASIS     600     0008     SAPK-60008INFINBASIS
ECC-DIMP     600     0008     SAPK-60008INECCDIMP
ERECRUIT     600     0008     SAPK-60008INERECRUIT
FI-CA     600     0008     SAPK-60008INFICA
FI-CAX     600     0008     SAPK-60008INFICAX
INSURANCE     600     0008     SAPK-60008ININSURANC
IS-CWM     600     0008     SAPK-60008INISCWM
IS-H     600     0008     SAPK-60008INISH
IS-M     600     0008     SAPK-60008INISM
SEM-BW     600     0008     SAPKGS6008
IS-OIL     600     0008     SAPK-60008INISOIL
IS-PS-CA     600     0008     SAPK-60008INISPSCA
IS-UT     600     0008     SAPK-60008INISUT
LSOFE     600     0008     SAPK-60008INLSOFE
IRMIPM     30B     0005     SAPK-30BI7INIRM
IRMGLB     30B     0005     SAPK-30BG7INIRM
ST-A/PI     01K_ECC600     0000     -
GSCDMC     600     0001     SAPK-60001INGSCDMC
RCMGT     601     0001     SAPK-60101INRCMGT
Thanks
Senthil

Hi Senthil,
of course it is always recommended to use the newest Support Package Stack,
but if your system (your business processes) are working fine, I would recommend you to
import support package only then when you have an error or you want to have a special fiunctionality.
Some customers play support packages into the system only twice a year, because the business processes
should be tested after the sp import.
Kind regards
Imre Takácsi-Nagy
Senior Support Consultant II.
SAP Global Support Center Austria
Netweaver WEB Application Server ABAP / JAVA

Basis Support package level of ECC 6.0

Similar Messages

Maybe you are looking for