Recompiling all reports after an import of support packages

Hi everyone!
Is there a way to recompile all reports after an import of support packages?
The goal is to avoid the system from compiling every report when it is being first accessed after the import of support packages.
Thanks in advance for any help.
Kind regards,
Paulo

Hi,
Please run the Tcode SGEN. This will solve your purpose.
Please note that while using the SGEN, please select the components which you have patched for the object generation.
This link may be helpful for you.
http://www.sap-img.com/bc036.htm
With Regards,
Saurabh
Edited by: Saurabh.Arora on May 20, 2009 9:09 AM

Similar Messages

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

Is the ASU Toolbox important for support package implementation?

Dear all,
when I want to implement new support packages there comes the hint with number 1000009 (ASU Toolbox).
Is it important to implement the toolbox or is it optional?

Hi,
Its not necessary!!
SAP Exchange Infrastructure (SAP XI) enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other. SAP Exchange Infrastructure is based on an open architecture, uses open standards (in particular those from the XML and Java environments) and offers those services that are essential in a heterogeneous and complex system landscape.
With regard to POS lot of domestic softwares are avilable other than Triversity.
The SAP for Retail solution portfolio includes customer-centric solutions from SAP Triversity, an SAP company. The applications from SAP Triversity focus on the "sell" side of retailing. They enable retailers to deliver a best-in-class customer experience across all channels, while helping them to optimize their operating efficiencies and increase profitability.
You can integrate thirdparty POS system to SAP.
http://www.saptriversity.com/
Bye,
Muralidhara

Support package stacks: Do we need to import all SP in the stack?

Hi all.
We are about to import Support Package Stack 13 into our ERP 6.0 system. The SPS includes a lot of support packages for software components such as IS-OIL, IS-UT and other IS-* components.
These components are inactive in our system, and are not used. However, I know that the recommendation is to import the complete stack.
I am therefore having some doubts if it is wise to import the IS-* related support packages.
Please advise.
Regards,
Thomas

Thank you for your feedback.
However, I would like to ask if the only argument is to follow SAP recommendation? What risks are we running if we do not implement the IS component support packages?
As the IS-* components are not active, I don't see how not importing these support packages will cause "inconsistence" in the system. Also, it would reduce the total number of support packages that needs to be included.
I am generally positive to following SAP's recommendations, but in this case we are are in a situation where we need to lift the SAP system from SPS 8 to SPS 13 in one operation. That includes a massive amount of support packages, and possibly a lot more time than the timeframe we have available.
Regards,
Thomas

Import Support Packages and note 1540729

Hello to All,
In the start of the import for SAPKH60019 and SAPKH60020, note 1540729 must be applied using ASU Toolbox. I have followed the steps for ST-PI 2008_1_* SP 04 of the note. In step 8, I have loaded the XML file using Tr. /ASU/START, following note 1000009. My problem is, what to do now. How and when I must execute the "Security Manual Follow-Up Steps" in /ASU/START?
Thanks in advance for your help.
Eduardo Barrios

Hello,
Thanks for your help. My doubt about when, appears because note 1540729, says:
" We recommend that you execute the report in conjunction with importing the
Support Package because you cannot activate the XSRF protection at a later
time with the support of the ASU Toolbox described in the following
section."
It seems that it means, during the import of SP, not after the import.
Regards
Eduardo

Importing Support Packages - Error during XPRA_EXECUTION

Hello,
Database: Oracle 10.2.0.4
Operation System: Windows Server 2008 X64
I´m facing with an error during an importing of support packages in our Solution Manager Ehp1 system (SPS 20 to SPS 25).
I checked the import logs of the queue and I see in there the following error:
Program terminated (job: RDDEXECL, no.: 02083200)
   See job log
Execution of programs after import (XPRA)
End date and time : 20110126020847
Ended with return code: ===> 12 <===
When I checked the job log I see in there this:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server SAPSM were synchronized
Internal session terminated with a runtime error (see ST22)
Job cancelled
I went to ST22 and I see in there that specific short dump which show:
Short text
    XSLT: No valid XML source
What happened?
    The transformation is not possible since the XML source document cannot
    be parsed.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator.
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_XSLT_RUNTIME_ERROR', was not
     caught in
    procedure "TRANSFORM_FROM_XML" "(METHOD)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Either the source document contains invalid XML or it is handled
    incorrectly in the ABAP program that called the transformation.
How to correct the error
    The most common cause of this error is a conflict between the encoding
    specified in the declaration <?xml version="1.0" encoding="..."?> in the
     document and the actual encoding of the data.
    If the document is held in an ABAP string, the actual encoding is the
    system code page. If this does not match the declaration, a parsing
    error may occur.
    These conflicts are a particular issue when XML documents are produced
    in one system and then imported into a system with a different code page
     (as strings).
    For this reason, XML documents should be held as binary data (X strings)
    , if they are extracted from the system or accessed from outside.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "XSLT_BAD_SOURCE_CONTEXT" "CX_XSLT_RUNTIME_ERROR"
    "CL_SM_BFR_CONTENT_TRANSPORT===CP" or "CL_SM_BFR_CONTENT_TRANSPORT===CM00E"
    "TRANSFORM_FROM_XML"
    The exception must either be prevented, caught within proedure
    "TRANSFORM_FROM_XML" "(METHOD)", or its possible occurrence must be declared in
     the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
Can you help how to correct this situation for I can continue the update of support packages!
Best regards,
João Dimas - Portugal

Hello William,
Which import logs do you refer?
I pasted in my first message the log of import... that is the unique error that it appeared.
I checked the SLOG:
STOP MOVE NAMETABS        SSM 6      20110125215838              SAP_BASIS    SAPSM 20110125214839404
START MAIN IMPORT          SSM I      20110125215838              SAP_BASIS    SAPSM 20110125214839404
STOP MAIN IMPORT          SSM I      20110125235752              SAP_BASIS    SAPSM 20110125214839404
START TBATG CREATION OF EN SSM n      20110125235752              SAP_BASIS    SAPSM 20110125214839404
START tp_getprots          SSM Y      20110125235753              SAP_BASIS    SAPSM 20110125214839404
WARNING: '\SAPSMsapmnt     rans     mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
WARNING: '\SAPSMsapmnt     rans     mpN110126.SSM' : cant open
(tpfsnam.c:504)
WARNING: '' : cant open
(tpfsnam.c:584)
STOP tp_getprots          SSM Y      20110126000148              SAP_BASIS    SAPSM 20110125214839404
STOP TBATG CREATION OF EN SSM n      20110126000148              SAP_BASIS    SAPSM 20110125214839404
INFO EXECUTION OF STANDAR SSM 9      not needed                  SAP_BASIS    SAPSM 20110125214839404
INFO: event SAP_IMPORT_STOP triggered successfully
STOP imp all              SSM   0004 20110126000149              SAP_BASIS    SAPSM 20110125214839404
I also checked the ULOG which has the following records:
APServiceSSM 20110126013719 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=\SAPSMsapmnt     rans (pid=5276)
APServiceSSM 20110126020829 RFC: tp SHOWPARAMS SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt     rans (pid=5196)
APServiceSSM 20110126020830 RFC: tp CONNECT SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dtransdir=\SAPSMsapmnt     rans (pid=5196)
APServiceSSM 20110126020831 RFC: tp XPA ALL SSM pf=\SAPSMsapmnt     rans inTP_DOMAIN_SSM.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -
Any idea what´s happen?!
Kind regards,
João Dimas - Portugal

How to deal with delta queue when importing Support Package/Kernel Patch

Hi,
From my experience, when importing a Support Package for an installation, the system will issue an error message and get stuck if this Support Package is about to alter the structures used in delta loads.
But I would like to double with you if there is possible that the support packet which is going to alter structure, but no error message. If so, the delta data will be lost.
Do we need to clear down the delta queue every time we import support package?
Anyway, is there anyone have any suggestions or steps regarding this question?
Many Thanks
Jonathan

Hi,
Delta queues during support package upgrade
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820
Effect on BW of R/3 Upgrade
How To Tackle Upgrades to SAP ERP 6.0
/people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
Start with the Why Not the How When You Upgrade to SAP ERP 6.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
Rapid SAP NetWeaver 7.0 BI Technical Upgrade
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
Hope this helps.
Thanks,
JituK

System shutdown during support package import

We were importing a BASIS support package in our system. Then for other reasons the system shutdown in the IMPOR_PROPER phase so...the system now is corrupted.
We try to launch the import of support package again from SAP GUI but we can not, a dump is generated everytime.
Are there a posibility of launch the import from operating system to finalice the aplication of package?what are the commands to do that?
We try to avoid the recovery from backup
Regards

Hi,
I don't think it is possible other than backup restore.
But already you are at worst case..i will suggest you to check the data in PAT01 and PAT03 tables at database level.
And delete all the contents from those tables then retry to login.
*Open a support message
Regards,
Nick Loy

Error getting in useradmin after support package issue!!

Hi all ,
We have just upgraded our support package for Bi_JAVA and other.According to our BASIS guy the package installation is through.
But when i checked the portal-----user adminnistration , iam getting the below error.
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NoSuchMethodError: com.sap.tc.webdynpro.services.task.IRequestTask.isUsrLogoffRequest()Z
    at com.sap.portal.pb.PageBuilder.wdDoExit(PageBuilder.java:203)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoExit(InternalPageBuilder.java:169)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doExit(DelegatingComponent.java:112)
    at com.sap.tc.webdynpro.progmodel.controller.Component.exitController(Component.java:255)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.exit(Controller.java:154)
    ... 27 more
See full exception chain for details.
Correction Hints
The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.
If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.

Hi
Check SAP Note : 869852
I think it UME is not correctly installed
After upgrading your system to a newer SP, you get one of the following
exceptions when executing the UME WD application:
o java.lang.NoSuchMethodError:
com.sap.security.core.wd.umeuifactory.wdp.I
ExternalUmeUiFactoryCompInterface.hasSimplePermission(Ljava/lang/St
ring;
Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/St
ring;Ljava/lang/String;)Z at
com.sap.security.core.wd.maintaingroup.MaintainGroupComp.afterModel
Init(MaintainGroupComp.java:787)
In order to avoid this error, perform following steps:
- Open the SDM tool and undeploy all components starting with
"tc/sec/ume/wd/..."
- Go to your downloaded SP archives and find the UMEADMIN*.SDA.
Redeploy it.
Regards
Krishna.

InfoObjects Key disappeared after BW support packages applied

Hi.
We have a serious problem, after we applied BW support packages (7.0110) all our infoobjects that are created as text only, no master data, are only displaying the text. The objects key is empty. Do anybody have a solution for this?
Koos.

Hi.
We have found a work around for the problerm for know and here it is:
5.1.3 Optimizing detail object syntaxFor queries on BI universes that include only the key and medium name detail objects of adimension, it is possible to modify the generated syntax of the objects to improve queryperformance, due to some internal details of the OLAP BAPI interface.To modify the syntax:
1.Open the universe in Designer.
2.Double click the key detail object you want to modify.
3.In the Select text box on the "Definition" tab of the "Edit Properties" dialog box, changethe syntax to refer to the NAME attribute of the SAP characteristic.For example, for the objectL01 Customer Key , change the generated select syntax:[Z_CUSTOM].[LEVEL01].[[2Z_CUSTOM]].[Value] to refer to the NAME attribute:[Z_CUSTOM].[LEVEL01].[NAME]4.ClickOKto save the changes.5.Follow the same steps for the name object. Change the syntax to refer to theDESCRIPTION attribute of the SAP characteristic.

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

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 !!

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

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 to implement support packages with BW connected to R/3??

Hello!
We use a BW system togehther with our ECC6. So we have activated Datasources in LBWE.
Every time, when I import a support package, there is a warning regardin LBWE an data to process.
Our workaround is to stop the updater in sm13, empty the queues and start the support packages.
The problem is: The updater is needed for the supportpackage too, so we have to activate it again...
Has anyone a "best practise" for this scenario???
Thanks
Juergen

Hi Dirk!
Thanks for the notes, yes, I know them...
Fine theorie...
The problem is:
Note that this processing must take place during system downtime because otherwise the different objects will be immediately filled with data again.
We are working worldwide and we have no real downtime, if the system is running...
So, we used the way to stop the updater to be shure to get no new objects...
Juergen

Recompiling all reports after an import of support packages

Similar Messages

Maybe you are looking for