Support package is different ,can we tranport objects ?

Hi,
Experts,
I have developed some objects,,Now i need to transport the m from BW DEV to BW Production.
But the support package of our
DEV system is :SAPKW70022
Prod system is : SAPKW70014
1) So, will there be any problem in working f my objects in production.?
Please tell me if there are any points to be taken care.
2) please tell me if there any codes to check the data source are availble Bw production that are tranported from BW dev ?
Regards,
Naresh.

Hi,
As per SAP Standards, we have to maintain the same support pactch level to all landscape.
in case if the systems are not in sync with the patch level, Transport may go fail or success( it always deponds if on what objects you are transporting)
so it is always better to have same patch level across all landscape.
Going further if you still want to transport the objects , then after transports check the error it will always be related to the Patch level. so you can upgrade the patch in the target system and then retransport with overwrite option.
Santosh
Edited by: Santhosh Nagaraj on Feb 3, 2010 1:40 PM

Similar Messages

Error message when trying to add signature. An error has occurred that may be fixed by installing the latest version of the Japanese Language Support package.

Error message when trying to add signature. An error has occurred that may be fixed by installing the latest version of the Japanese Language Support package. How can I fix this?
Thanks
[email protected]

What is your operating system? Reader version?

EHP and Support packages

Hello,
Im going through this document;
Master Guide ; SAP Enhancement Package 5 for SAP ERP 6.0 Powered by SAP NetWeaver
Using SAP Enhancement Package 5 for SAP ERP 6.0 and SAP NetWeaver 7 including Enhancement Package 2
Im having a point to clarify;
SAP enhancement packages have Support Packages of their own that are equivalent to the Support Package versions of the underlying SAP system.
We highly recommend installing the enhancement package in combination with the latest available Support Package stack. This approach reduces installation, modification adjustment, and testing effort. Using this strategy, you can install SAP enhancement packages as a normal maintenance activity together with Support Package stacks.
Whats meant by ;
SAP enhancement packages have Support Packages of their own that are equivalent to the Support Package versions of the underlying SAP system.
We highly recommend installing the enhancement package in combination with the latest available Support Package stack.
Can you help me to clarify this with an example
regards,
Zerandib

Hi,
Let me give you some basic example to make this statement clear.
We should first of all distinguish between the terms upgrade and update.
UPGRADE means from one Major release level to Another Major Release. Eg: R/3 46C to ECC 6.0
UPDATE means it can be either support package for installed components or Enhancement Packages for existing component.
Instead of upgrading the the entire RELEASE SAP has come up with EHP updates. This give you all major new changes without
doing a complete release upgrade. Also Downtime is reduced.
Consider this component
SAP_HR     470     0010     SAPKE47010      R/3 Enterprise 4.7 system
If this is upgraded to EHP 5 then the naming convention becomes
SAP_HR     605     0043     SAPKE60543      ECC 6.0 with EHP 5
Just like how we have support packages for each component. WE have support packs for the enhancement packages too.
More information can be pbtained in the below link
http://service.sap.com/erp-ehp
Refer to this SAP notes for further understanding.
1484460 EHP5 for SAP ERP 6.0 SP Stacks - Release & Information Note
1064635 SAP ERP Enhancement Packages: SP Stacks Release Info Note
1298878 Installation of SAP Enhancement Package 5 on SAP ERP 6.0
774615    Support Package levels of ERP/ECC installations/upgrades
I hope I was able to clarify your questions.
Regards,
Naveen.
Edited by: Naveen Kumar on Feb 29, 2012 10:41 AM

RSPOR_SETUP = Different ABAP and Java support packages.

Hi all,
We have an ECC 6.0 system with abap+java stacks. When we run the RSPOR_SETUP report we get this error:
Different ABAP and Java support packages. Combination of support packages invalid
And with some more clicking we find this:
6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
   ABAP Support Package:                  13
   Java Support Package:                   0
On the Java stack we see (among others) these components:
sap.com       BI-IBC       7.00 SP12 (1000.7.00.12.0.20070509050058)
sap.com       BI_MMR       7.00 SP12 (1000.7.00.12.0.20070507084106)
sap.com       BI_UDI       7.00 SP12 (1000.7.00.12.0.20070507084125)
sap.com       BI-BASE-S       7.00 SP12 (1000.7.00.12.11.20080324092518)
sap.com       BI-WDALV       7.00 SP12 (1000.7.00.12.1.20071105133039)
sap.com       BI-REPPLAN       7.00 SP12 (1000.7.00.12.3.20080104101916)
So I believe all components are correctly installed.
What are we doing wrong?

Hello.
Please be aware, that report RSPOR_SETUP should NOT be used with a Netweaver 04s system. This report has been replaced by the support desk tool. I request you to run the support desk tool as per note 937697 to check if there are any configuration issues in your system.You can resolve any red traffic lights that might be reported by the tool by following the corresponding actions suggested.
I hope I can be helpful.
Thanks,
Walter Oliveira.

Objects for deletion included in support package are not deleted

Hi experts,
How can i create a support package using Add-on Assembly Kit that deletes several objects?
This is the case:
We have DEV, QA and PROD systems. The objects are deleted on DEV and the transports are released. The transports are automatically imported on QA and the objects are deleted -checked they are gone. A support package of the product is created on QA including the transports that delete the objects. The SP is released successfully and imported on PROD successfully. The objects that should be deleted still exist on PROD. I've checked the logs for errors - no errors found.
Do you have any idea what could be the reason?
Best regards,
Petar

Note number 1581093.
As mentioned in the symptom. Version 2 of the note is created to extend the functionality provided in the Version 1. Version 3 of the note is created to correct the error in Version 2.
Information from SPAM
SAP_HR 600 0054 SAPKE60054 Human Resources
How can I find the information required if neeed?
WHen I try to reset the implementation I get the message
No correction instructions implemented for SAP
Note 0001581093
Edited by: Wojciech Walczak ITMAXI.COM on May 25, 2011 12:00 PM

Object list contained into Support Packages

We need to know wich objects are contained into the Support Packages we are thinking to apply.
They sare Aba, Basis and Appl rel 46C, from 36 to 48.
Where is possible to obtain a list like that ?
Regards

Hi Mauro,
All this information you require is available using your service marketplace user. If you're a registered SAP service user, as you must be, being a customer with an installation of R/3 version 4.6C. Have you ever logged in to the marketplace before?
If not, be sure to log in as soon as possible, the address is http://service.sap.com.
There is the quick-link http://service.sap.com/swdc where you automatically reach the SoftWare Distribution Center area. There you can navigate to the Download->Support Packages and Patches->Search for (...) and enter the names of the Packages if you know them, or through the My Company's Application Components link, and navigate to the relevant components, in your case SAP R/3->4.6C->(...).
There you can download them, browse the list of notes each of them contains, browse the list of objects contained, or browse the release information of the packages.
Hope this helps.
Best Regards,
Daniel.

Can't Find SAPKD70021 - SPAM Update Tool Support Package

Hi, All:
     We now need patch SPAM support package 21 - SAPKD70021. But now from http://service.sap.com/swdc , we can only find patch 22 - 24. There's no patch 21, but our currently patch level is 20.
     Do we the only one meet the problem?
     Anyone can help? Thanks!
B.R.
H.D

Hi,
       you can directly update the latest one..ie., 24
Regards
Umesh K

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

Hi all - how can i see the history of support package

hi have install new support package .
and now i want to view the history of the sp , where can i see it ?
eyal

Hai,
if you want to see the history of support package for JAVA (Web AS JAVA),
Goto the URL : <b>http://<host name>:<http port of Java stack>/</b> --> select System Information --> Show all components --> it will display all Java SP's that you have deployed in your J2EE engine.
regards,
Gopinathan.

Can't install CC apps. Created a support package 40-83419-223817072013.

Purchased CC today on the annual plan.
Tried to install one of the applications.
Can't complete the install / update of Application Manager.
At one point was getting error code "A12E1".
Followed various guidelines in user forums and finally got "Installer failed to initialize. Please download Adobe Support Advisor to detect the problem."
Have an old version of Application Manager installed, but it won't execute and a file: "F:Adobe Application Manager"
(I don't want any Adobe files on my C: drive if I can avoid it.)
Now I have a new file: "F:Adobe Application Manager 7.0"
Got Adobe Support Advisor running. It told me "Inspection could not identify any issues. Please contact Adobe Support for further assistance."
Created a support package with token number: 40-83419-223817072013.
Running Windows 7 with all fixes in place.
What next?

Hi Mr. Gibson,
Welcome to the Community!
Please try these Steps and let me know if it works:
1. Disable UAC, check it here http://windows.microsoft.com/en-in/windows-vista/turn-user-account-control-on-or-off
2. Disable the Startup Items and Services, check it here http://helpx.adobe.com/x-productkb/global/disable-startup-items-services-windows.html
3. Enabling the hidden Admin user in Window 7 64-bit, check it here http://www.howtogeek.com/howto/windows-vista/enable-the-hidden-administrator-account-on-wi ndows-vista/
Run the installer again in the Hidden Admin in Windows 7.
Thanks!
Ankit

I can't find any support package for Solution Manager 4.0

I can't find any support package for solution manager at
Support Packages and Patches - > SAP Technology Components
SAP Technology Components
GATEWAY
JAVA LOG VIEWER
SAPCAR
SAP EXCHANGE CONNECTOR
SAP CR CONTENT
SAPROUTER
SAPSECULIB
SAPSSOEXT
I'm searching it at a wrong place?

You´re at the right place - but your user doesn´t seem to have permissions to download them.
You have a license for Solution Manager?
Markus

0FC_PAY in which support package Can I find it?

Hello gurus!
I need the 0FC_PAY datasource, for ISU , but I dont know in which support package can I find it?
Somebody can helpme please
Thanks a lot

When logged onto ECC, go to menu option System > Status... In the section SAP System Data the component version field should provide you with the Enhancement Package, or EHP, level that you're at.
To find the BI Content version, while in the System: Status screen, click on the magnifying glass next to the Component Version field. There should be a component called BI_CONT. That needs to have a minimum release of 704. The level, which is irrelevant for what you're looking for, is the Support Package level for that component.

Support Package pre-requistis accross different landscapes

I am struggling with which landscape but be patched before another since adding PI 711 into the mix.
I am supporting ECC6 EHP4 with NW701, BI 70 at Netweaver 70, Solution Manager 70 Ehp1 and now PI 71 ehp1.
I have been told PI must lead all other landscapes support package level but with it being at a later version of Netweaver than all other landscapes it is a far comparison or does it already lead them?
My immediate need is to begin planning for a support package project on the ECC6 EHP4 landscape in the fall. Since this landscape was last patch, about one year ago we add the PI landscape.
It is a pretty safe bet I will be struggling with this same question in about 6 months when I start looking at a BI support package project.
Any help that could be provided on this would be most appriciated.
Bill

I think we need to understand more why you feel certain systems need to be patched first or in a certain order
- from what you say there must be technical concerns across more than one product area
Perhaps it could be that --->
Generally systems that interact with one another should be on the same BASIS level and SP stack - the general rule of thumb
Products such as SLD definately have to be on systems with equivalent or higher BASIS version and SP stack than systems
they interact with because the content created for a Netweaver 700 SLD
may not be able to cope data supplier information from a Netweaver EHP1 system (this also raise other concerns regarding
exporting data between SLDs - again equivalency - or higher for target system is recommended, sometimes with SLD lower BASIS version source systems may have limited export options as well)
Products such a Solution Manager also as a rule of thumb have to be on equivalent or higher BASIS version or SP levels
than the systems they interact with
But PI also may have similiar concerns because they manage communication between systems e.g business systems
However lets take say Payroll in ECC without any ESS or Legacy Systems, ALE
- totally standalone payroll system - the only rules that apply there are that it works, has the latest fixes and required legal changes and follows a recommended stack - no BASIS equivalency level between other systems may exist in order for payroll to carry out its purpose
Does this help clarify further ?
Best wishes
Stuart

Regarding Support package influence

hi gurus,
I have two questions to ask.
1.whether standard element lists like screen attributes,Fields,tables,Dataelements,Domains attributes
differ due to support package different in SAP systems. Please confirm.
2.using FM RS_GET_ALL_INCLUDES to fetch includes for SAPMF02K program.
It lists programs like this
   1) OIU_CM========================P,
   2) OIU_COMMON====================S
   But i cant see this code in SE80/SE38 Why.
Can somebody shed light on this.
Regards
Ambichan

Hi prince,
1. 1.whether standard element lists like screen attributes,Fields,tables,Dataelements,Domains attributes
differ due to support package different in SAP systems. Please confirm.
No, they will won't differ.
Bcos one object in one package, will not be there in another package.
regards,
amit m.

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

Support package is different ,can we tranport objects ?

Similar Messages

Maybe you are looking for