Translation Worklist and Support Package application

Can anyone explain me what'll happen with a published Translation Worklist when I apply a SP? Will it lose the translated texts?
Do the worklist keep the translated texts or they are loaded from the objects every time? If the second is the right, they'll be lost when I rewrite the objects, correct?
Thanks for any help.

Hi Denis,
> Where the translated texts are stored? They are stored only until we publish the
> translation and then if we re-activate the worklist they are reloaded from the
> objects?
That's exactly what I would think for different reasons, but it's not that hard just to test it, isn't it?!
Best regards
Detlev

Similar Messages

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

Install Kernel Patch and Support Package

Hi Gurus.
How can I update the kernel patch and support package in solution manager?
What patchs i have to download In the service.sap.com ?
best Regards
luis

Hi Luis,
Yopu must already have checked this info at Inst Guides..
else...The Post installation steps in the installation guide contain the procedure for application of latest support packs procedure.
https://websmp204.sap-ag.de/instguides
The following SAP notes can also be referred : 212876
Information of how to download a kernel can be obtained from 19466.
Details of Patches and their release schedules can be obtained as always at
https://websmp104.sap-ag.de/ocs-schedules
Hopefully it Helps in your quest.
Br,
Sri

OSS and Support Packages

Hi all,
Is ther any difference between the OSS and support packages?
Plz explain for this one.
regatrds
vijay

Hi,
IMPORTANT DIFFERENCE
Support packages provide a bundle of fixes in electronic form that are imported into the SAP system. These Support packages must be imported in order (starting with the very first one) and they cannot be skipped. All fixes within a Support package must be imported together, there is no ability to pick and choose the fixes.
The second form of fixes that SAP provides is via OSS notes that pertain to specific problems. These notes must be manually applied to the system, as these fixes are generally not available in electronic form at the time the note is published. Care must be taken to ensure that the note is entered correctly otherwise new problems may occur, or the existing problem is not corrected.
A Support package may contain fixes that also exist as individual notes, but many times they contain fixes that are only provided in Support packages. SAPs strategy for providing intra-release fixes is through Support packages and the use of individual notes is decreasing.
I hope this information could help you.
Note: Points always encourage me to reply !!

Portal Translation Worklist and XML

We have been using XML files to upload our Portal Content (iViews, Pages, Worksets, Roles, etc...) and have been very successful with this process. We have run into an issue trying to use an XML file to create a Portal Translation Worklist, because the example given in the document below is very limited).
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207a2141-c870-2910-e080-90c920b24f47
Has anyone been able to accomplish creating a Portal Translation Worklist using the XML Import method?
Thanks,
Ashley

Hi Pater,
Did you translate your content also, please try doing that.
Follow below procedure,
1.Go to 'Translation worklist Coordination' ->Portal Content and right click your folder and Select New->Translation Worklist
2.This will create the Translation Worklist to which you can add your PCD objects for translation.
3. Go to your folder containing your iView, right click and 'Add Object to Translation Worklist'
4.After you have added all the object you want to translate, click 'Generate Translation Data' button at the top on the Translation Worklist screen.
5.Click the 'Release for Translation' button in the scrren that appears.
6.click Close in the screen that appears.
7. Go to 'Worklist Translation' link.
8.Search for your worklist you just created using the search box.
9.Select the worklist from the result list.
10.At the bottom of the screen select the Source Language and Target languages from the dropdowns
11.clieck 'Load for Translation'
12.Choose whiever texts you want to translate and enter the 'Translated Text' in the box for the target text.
13.After you are done with all the translations, click close.
14.Save All and Close
15.You'l go back to the previous screen again. There select your translation worklist and click 'Mark as Translated'
16.Go back to the 'Translation Worklist Coordination' link and open your translation worklist from your folder.
17.Click 'Publish Translation' button.
Thanks.
Sushil

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

Question about OSS Notes, Archiving and Support Packages

Hello,
does anyone know if all the OOS notes related to archiving programs corrections (category like "performances", "program error", "advance developments",
"legal functions", "corrections of legal functions", "problem", "exit added", "special developments"...) are all automatically appllied on SAP when a support packages is installed?
Thank you
Best regards
Fabio

Looks like the only requirement is Vcenter and Vsphere 4 client. So version 4.0 and up is supported.
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/5.1/device_support/table/sdt.html
ANM 5.2 and 5.1 includes a plug-in that allows you to integrate ANM into a VMware virtual data center environment. VMware is a third-party product for creating and managing virtual data centers. Using VMware vSphere Client, you can access ANM functionality and manage the ACE real servers that provide load-balancing services for the virtual machines in your virtual data center.
To use the ANM 5.2/5.1 plug-in, you must use VMware vCenter Server and VMware vSphere Client 4.
For more information about using ANM in a VMware virtual data center environment, see the User Guide for the Cisco Application Networking Manager 5.2/5.1.

Upgrading the BI Content to 7.03 and Support package 14 in BI client

Hi Experts,
My Production system is having BI content 7.03 and the support package is 1. I wish to import the support package upto 14 as soon as possible for my requirement.
Can anyone please answer my below questions..
1. What steps should be followed ?
2. What should be taken care of ?
3. What downtime should I take ? Should it be for R/3 and BI both ?
4. Should I clear the queues in RSA7 before upgrading the content ?
If some point is left, please write it so that it can be considered in my case.
Your help at the earliest will be appreciated.
Thanks in advance.
Regards,
Romil

Note 1000822 - Overview: Notes for the add-ons BI_CONT and BI_CONT_XT
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/c0994772-53d7-2a10-7eb3-a8cee3cf5c35 [original link is broken]
https://websmp208.sap-ag.de/swdc
Colin

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.

Language install and Support Packages

We have installed some new languages in our system and are now re-applying the support packages as required.
In SMLT when re-importing the support packages, a pop-up box with the option to 'Overwrite' or 'Do Not Overwrite' repaired texts comes up. We are debating the pros and cons of these options. There is no list telling us specifically which texts have been repaired so that we can evaluate (ie, a SPAU list).
Does anyone have feedback on which is the preferable option?

HI,
I am facing the same problem and I tried restarting the import.
But the same error occurs again.
Please find the error below:
Error when importing language data
tp message:
A tool used by tp broke down
The tp program was called as follows:
POSTLANGUAGEIMPORT
SAPK-603DFINSAPAPPL
Q18
U6
pf=/usr/sap/trans.Q18/bin/TP_DOMAIN_M36.PFL
-Dpostlanguageimportvector='V'
-Dctc=0
-Dclientcascade=yes
-Dtransdir=/usr/sap/trans.Q18
tp output:
This is tp version 380.07.32 (release 721, unicode enabled)
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter SERIAL is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter SERIAL is no longer used.
Warning: Parameter DBLIBPATH is no longer used.
Warning: Parameter DBSWPATH is no longer used.
ERROR: stopping on error 16 during POSTLANGUAGE IMPORT
stopping on error 16 during POSTLANGUAGE IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 16
WARNS: Highest tp internal warning was: 0118
standard output from tp and from tools called by tp:
This is /usr/sap/Q18/SYS/exe/run/R3trans version 6.24 (release 721 - 23.05.13 - 20:13:04 ).
unicode enabled version
1AETW042 unexpected EOF after "242810271" bytes.
2EETW000 Please contact the SAP support.
exiting ...
/usr/sap/Q18/SYS/exe/run/R3trans finished (0016).
Any help would be much appreciated.
Regards,
Gowtham

Spam/saint update and support package

Hi,
our solution manger server is crashed long back.Now i installed the solution manager in seperate server.
solution manager iam getting SPAM/SIANT version as 7.00/0.20 and in development/production SPAM/SAINT version in 7.00/0.23.
as per check in service market place under SPAM/SAINT update 700 iam getting SPAM/SAINT update version 700 iam got the message as to import Support Packages SAPKH60008 and SAPKGPAD08. Please advice.
*in solution manager support package is
SAPKB70008
SAPKA70008
SAPKIPYJ78
SAPKITLQI2
SAPKW70008
SAPKNA7005
SAPKU50005
SAPK-40005INCPRXRPM
SAPKITL416
SAPK-15074INSTPL
SAPKITLOG3*
*in dev/produ system support package is
SAPKB70011
SAPKA70011
SAPKIPYJ7B
SAPKITLQI3
SAPKW70012
SAPKNA7008
SAPKE60015
SAPKH60008
SAPKGPID08
SAPKGPGD08
SAPKGPRD08
SAPK-60008INFINBASIS
SAPKGPPD08
SAPKGPFD08
SAPKGPHD15
SAPKGPDD08*
please advice me in service.marketplace>downloads>support packages and from where i will get packages as in dev/production system.
Regards,
Asif

Hi Asif,
How to get particular support package from service market place .
EX:SAPKB70011
If you want to download the patch SAPKB70011:
Service Market Please --> Downloads --> SAP Support Packages --> Search for Support Package and Patches.
At the search field, enter SAPKB7001* it will give you all the support package from SAPKB70010 to SAPKB70019 if available.
You can add the required patch to your download manager.
Thanks & Regards,
Nagendra.

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

Netweaver developer studio and support package

we use JDI and netweaver developer studio for webdynpro development. when we upgrade satellite systems to latest sp, what should we do with developer's pc (j2ee engine and developer studio)? if we upgrade them to the same latest sp as in development satellite system, we will be compatible with development, but what about production system support? production will still be at the current old sp version. do we need another developer pc to support the current development on current sp?
Thanks
Jane

HI,
Its better to maintain WAS.NWDS and JDI on same SP level to avoid conflicts between different SPacks.
Recently there is a blog on the same on SP levels.
/people/marion.schlotte/blog/2005/10/25/jdi-software-vs-jdi-content
hope this helps you ..
Refer this note 790922 will be able to help you
Regards,
RK
Message was edited by: Ramakrishna Venkat
Message was edited by: Ramakrishna Venkat

Plug-Ins and Support Packages

Hi Expert,
Can somebody please provide me the detail matrix for _plugins & support packages_ for connecting the PI , SRM, APO & SolMan source systems to the SAP-BI 7.01 .
Thanks Alot
Mohammed

Hi All
We need matrix for BI7.04 & service pack 2 as same below link
https://websmp207.sap-ag.de/~sapdownload/011000358700007362962004E/func_corresp.htm
Thanks & Regards
Anuj

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

Translation Worklist and Support Package application

Similar Messages

Maybe you are looking for