EPS/in directory

Hi everyone!
Does anyone know if it is safe to delete all the files in the EPS/in directory after a support package has been applied?
Might it be any impact by doing that?
Thanks in advance.
Paulo

Hi,
Yes, you can delete the contents of EPS/in after completing/confirming the SP Upgrade. You need to maintain free space for next upgrade in your server rite
Feel free to revert back.
-=-Ragu

Similar Messages

Can we deletete the eps/in directory after the upgrade

Gurus ,
we are in the process of upgrading our support packages through SAINT . we are using ECC6.0 version on Oracle AIX 64 bit .
hence for applying all the add-ons we load it from front end to \eps\in directory via SAINT .
But my doubt is ,
- can we manually delete the eps\in directory after the upgrade is over ? because each add on are around 145 mb . and i fear accumulation of those will cause problem
-How to find the space available in eps\in directory from the GUI ?

Hi,
You can safely delete files from EPS/in after you install them to the system, they will be in the Database so this files are not needed any more. In fact even if they are ther, you won´t see any new SP or Add On using SAINT & SPAM unless you copy new versions to EPS/in directory.

Where can i define the EPS-Inbox Directory???

Hi,
Where can i define the EPS-Inbox Directory???
Regards
Christian

Hi!
Also at AL11, you can display and configure current SAP directories.
Hope this help!
Juan

JSPM uses incorrect EPS inbox directory

Hello,
I have a problem with implementing support packages using JSPM.
JSPM reads the inbox of the local server instead of the global EPS inbox.
I have defined the hostname alias in the hosts file. When I check in RZ10 the DIR_EPS_ROOT points to the global EPS inbox. And when I use transaction SPAM to import the ABAP stack, it reads the correct EPS inbox.
But when I use JSPM it keeps pointing to the local server instead of the global EPS inbox defined in DIR_EPS_ROOT.
Can someone help me with this?
We are using NW04S ABAP+Java running on a WIN 2003 Enterprise server.
Kind regards,
Henk

Hi
These are two different things:
What you are gettin in spam is perfectly ok.
Now in case of JSPM ,it always points to local EPS directory,you cannot use JSPM to deploy components remotely.So nothing is work with it.
You can use SPAM tp patch your abap part and JSPM to patch the java part by putting the sca's in the local EPS directory that is \usr\sap\trans\EPS\in.
In case you have any other querries revert back.
Reward with suitable points:

What is the use of EPS\out in trans directory???

What is the use of EPS\out directory?????

Hi venkatesh,
There was once a transaction called SPADE , which existed in SAP 4.6C, however it doesn't seem to exist right now and I am not sure if there is a new transaction available anymore.
The SPADE transaction was built for creating CRT or Conflict Resolution Transports, check help.sap.com for more details.
When you created a Conflict Resolution Transport its .PAT and .ATT files used to exist in EPS/out directory.
SAP Partners could create their own Add-Ons (their own products that are built around the SAP Server) and provide CRTs to address any conflicts between support packages.
Hope that helps.
Regards,
Siddhesh

Change central download directory for SLM

Hello together,
I configure the MOPZ/ SLM function in my Solman system, everythings works fine (download, implementation and so on).
Now I have a question, is it possible to change the central download directory. At the moment all download files goes to the normal EPS/in directory of my Solman.
Now I want to share a special directory, because there is a problems with the user authorisations in my Unix filesystem (different UID's of the OS Users in my whole landscape). This directory should be different to the current.
Is this possible, to change the download directory???
Bye, M. Haberland.

Hello Marcel,
Please review the following notes which may be able to guide you through this.
1138247 - Maintenance Optimizer: Description about the SLM
1137683 - Maintenance Optimizer: Notes for Software Lifecycle
In addition, please review any notes that are releavant to these two notes.
Also, please review the following URL which will also assist you on configuring MOPZ.
http://service.sap.com/solutionmanager
-> Media Library
-> Technical Papers
-> "How to Configure Maintenance Optimizer (SPS15-17) to Use SLM" for ST
SP15 to SP17, and "How to Configure Maintenance Optimizer (SPS18) to Use
SLM" for ST SP18 and higher.
Hope this helps you out.
Thanks,
Mark

Step to Upgrade service plug-ins the ST-PI and ST-A/PI Plug-Ins

Dear all,
I have to upgrade service plug-ins the ST-PI and ST-A/PI Plug-Ins the current release.
Plug-In     Release
ST-A/PI     01J_ECC500
ST-PI     2005_1_640
After running the report RTCCTOOL the following details are
No.   Missing addon/ transport / note
   Description                 Implementation
1. [Note 69455 ]     Addon ST-A/PI 01L_ECC500
     Description     "Servicetools for Applications Plug-In" for ERP 2004 / ECC 5.00
2. [Note 539977 ]    Addon ST-PI 2008_1_640
     Description     "Solution tools plugin" ST-PI 2008_1_640 Addon for 6.40 / Netweaver 04
                             [Basis tools for services]
3. Note 207223
    Description     Setup of the EarlyWatch Alert service
Please suggest the step by step how to the implemented service and caution to before applying.
Regards,

Hai,
Please download the plug ins and upload them into the /usr/sap/trans/EPS/in.
You can do it from frontend through SAINT tcode, this will automatically uncar the files and place it in the
/usr/sap/trans/EPS/in directory.
Then you have to apply the plugins from SAINT.
http://www.sappoint.com/PHPWebUI/Documents/Applying%20Support%20Pack%20and%20Plug-ins.pdf
You have to do this from 000 client and user with enough authorizations.
http://www.saptechies.com/how-to-implement-support-packagesaddonsplugins/
Regards,
Yoganand.V

Add_to_buffer-error return code-0211 in support packs apply in Sol Man

Hi Experts,
Our Solution manager system installed on Virtual (Db2/Aix). I had updated SPAM 035 from frontend (SPAM)successfully but I'm getting error as 'add_to_buffer' during the basis (700) support packages deployment stage. I had checked STMS configuration,is fine.EPS directory file permissions, is okay.R3trans -d is ended with rc-0000. I had uploaded patches from front end (from my PC). I haven't copied basis patches into EPS/in directory. How can i over come this issue? I have checked ulog and attched here.Please help me on this.
sgbsmp01:smpadm 24> vi ULOG09_3
"ULOG09_3" 25 lines, 3809 characters
smpadm       20090911100056 RFC: tp SHOWPARAMS SMP pf=/usr/sap/trans/bin/TP_DOMA
IN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100056 RFC: tp CONNECT SMP pf=/usr/sap/trans/bin/TP_DOMAIN_
SMP.PFL -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100102 RFC: tp CREATECOFILE SAPKD70035 pf=/usr/sap/trans/bi
n/TP_DOMAIN_SMP.PFL -s SMP -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100103 RFC: tp ADDTOBUFFER SAPKD70035 SMP U1 pf=/usr/sap/tr
ans/bin/TP_DOMAIN_SMP.PFL tag=spam -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100103 RFC: tp MODBUFFER SAPKD70035 SMP pf=/usr/sap/trans/b
in/TP_DOMAIN_SMP.PFL mode=G0,V0,w0 -Dsourcesystems= tag=SPAM -Dtransdir=/usr/sap
/trans (pid=557110)
smpadm       20090911100103 RFC: tp CMD ALL SMP pf=/usr/sap/trans/bin/TP_DOMAIN_
SMP.PFL -Dclientcascade=yes -Drepeatonerror=8 -Dstoponerror=8 -Dsourcesystems= t
ag=spam -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100108 RFC: tp TST ALL SMP pf=/usr/sap/trans/bin/TP_DOMAIN_
SMP.PFL -Dsourcesystems= tag=spam U1 -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100112 RFC: tp IMPORT all SMP pf=/usr/sap/trans/bin/TP_DOMA
IN_SMP.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems
= -Dbuffreset=yes -Dmainimp_proc=1 -Ddictimp_proc=1 -Dbatch_proc=1 -Dstopimmedia
tely=1 -Dactivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=/usr/sap/tr
ans (pid=557110)
smpadm       20090911100403 RFC: tp SHOWPARAMS SMP pf=/usr/sap/trans/bin/TP_DOMA
IN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=557120)
"ULOG09_3" 25 lines, 3809 characters
smpadm       20090911100056 RFC: tp SHOWPARAMS SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=55
7110)
smpadm       20090911100056 RFC: tp CONNECT SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=55711
0)
smpadm       20090911100102 RFC: tp CREATECOFILE SAPKD70035 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -s SMP -Dtransdir=/usr/sa
p/trans (pid=557110)
smpadm       20090911100103 RFC: tp ADDTOBUFFER SAPKD70035 SMP U1 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL tag=spam -Dtransdir
=/usr/sap/trans (pid=557110)
smpadm       20090911100103 RFC: tp MODBUFFER SAPKD70035 SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL mode=G0,V0,w0 -Dsourcesy
stems= tag=SPAM -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100103 RFC: tp CMD ALL SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dclientcascade=yes -Drepeatonerror=8
-Dstoponerror=8 -Dsourcesystems= tag=spam -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100108 RFC: tp TST ALL SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dsourcesystems= tag=spam U1 -Dtransd
ir=/usr/sap/trans (pid=557110)
smpadm       20090911100112 RFC: tp IMPORT all SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dclientcascade=yes -Dstoponerror=
8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dmainimp_proc=1 -Ddictimp_proc=1 -Dbatch_proc=1 -Dstopimmediately=1 -Da
ctivatemerged=yes -Dcheckmasterlang=no tag=spam -Dtransdir=/usr/sap/trans (pid=557110)
smpadm       20090911100403 RFC: tp SHOWPARAMS SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=55
7120)
smpadm       20090911100403 RFC: tp CONNECT SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=55712
0)
smpadm       20090911100408 RFC: tp DELFROMBUFFER SAPKD70035 SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dsourcesystems= tag
=SPAM -Dtransdir=/usr/sap/trans (pid=557120)
smpadm       20090911103746 RFC: tp SHOWPARAMS SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=94
6406)
smpadm       20090911103747 RFC: tp CONNECT SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=94640
6)
smpadm       20090911103754 RFC: tp CREATECOFILE SAPKB70015 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -s SMP -Dtransdir=/usr/sa
p/trans (pid=946406)
smpadm       20090911103808 RFC: tp CREATECOFILE SAPKB70016 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -s SMP -Dtransdir=/usr/sa
p/trans (pid=946406)
smpadm       20090911103823 RFC: tp CREATECOFILE SAPKB70017 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -s SMP -Dtransdir=/usr/sa
p/trans (pid=946406)
smpadm       20090911103839 RFC: tp CREATECOFILE SAPKB70018 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -s SMP -Dtransdir=/usr/sa
p/trans (pid=946406)
smpadm       20090911103848 RFC: tp ADDTOBUFFER SAPKB70015 SMP U1 pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL tag=spam -Dtransdir
=/usr/sap/trans (pid=946406)
smpadm       20090911103944 RFC: tp SHOWPARAMS SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=55
3110)
smpadm       20090911103944 RFC: tp CONNECT SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=55311
0)
smpadm       20090911104050 RFC: tp SHOWPARAMS SMP pf=/usr/sap/trans/bin/TP_DOMAIN_SMP.PFL -Dtransdir=/usr/sap/trans (pid=55
3110)

I contacted SAP marketplace at the same moment I created this message and that really worked.
Thanks to the diligent SAP support I was able to complete the import of the support package.
This also means and that was confirmed by SAP that the usage of function module: OCS_RESET_QUEUE was not the solution of the problem. Basically it means that you need to contact SAP for help in those kind of situations.
Thanks Uday for your response!

SAP Strategy Management 7.0 SSM Component Deployment failed with JSPM

Dear experts,
i have installed a SAP Netweaver CE 7.1 on Windows Server 2003 Enterprise x64 with MS SQL and i wish to install now SAP Strategy Management 7.0 with JSPM Tool.
I have copied the CPMSTRMGMAPC00_0.SCA file on the usr\sap\trans\EPS\in\ directory and the deployment precessus failed with error before the AS JAVA has been restarted.
How can i manage this problem? Any suggestion is welcomed.
Thank you very much.
Best regards,
Pascal.

Any ideas?
Here is the F:\usr\sap\PI7\J71\j2ee\JSPM\log\log_2009_06_15_12_51_48\deploy_2009-06-15_14-56-58.log
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.7.1006]/>
<!NAME[F:\usr\sap\PI7\J71\j2ee\JSPM\log\log_2009_06_15_12_51_48\deploy_2009-06-15_13-07-03.log]/>
<!PATTERN[deploy_2009-06-15_13-07-03.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 15, 2009 1:07:03 PM [Info ]:DC API is trying to connect to 'sap-pi7:57104'
Jun 15, 2009 1:07:03 PM [Info ]:DC API has Connected to 'sap-pi7:57104'
Jun 15, 2009 1:07:03 PM [Path ]:+++++ Starting V A L I D A T E action +++++[ deployerId=2 ]. timerId=7
Jun 15, 2009 1:07:03 PM [Path ]:Selected archives for validation. [ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca
Jun 15, 2009 1:07:03 PM [Debug ]:Got full sdu path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
Jun 15, 2009 1:07:03 PM [Path ]:component version handling rule is UpdateLowerVersionsOnly.[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:deployment workflow strategy is safety deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Path ]:Error strategies[ deployerId=2 ]:
Jun 15, 2009 1:07:03 PM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2009 1:07:03 PM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorSkipDepending'
Jun 15, 2009 1:07:03 PM [Debug ]:deployer initialized successfully:[id:#8, elapsed: 0 ms.].[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Debug ]:Total time:[#8: 0.0 sec].[ deployerId=2 ]
Jun 15, 2009 1:07:03 PM [Info ]:Start validating.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:Validating completed. Preparing the validation result.
Jun 15, 2009 1:07:06 PM [Path ]:
Sorted Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca --> xappscpmsm~strategymanagement.sda'
     Sdu info :name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
          Deploy status is 'Admitted'
     2. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Admitted'
Deployment Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Admitted'
          Time statistics:
          Contained DCs:
          1.1:name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'Admitted'
          1.2:name 'xappscpmsm~strategymanagementactions', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465041', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465041'.
          1.3:name 'xappscpmsm~strategymanagementdoc', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465046', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465046'.
          1.4:name 'xappscpmsm~strategymanagementdic', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465042', software type ('JDDSCHEMA', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465042'.
Jun 15, 2009 1:07:06 PM [Info ]:+++ Validation finished with status 'Success' +++[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:+++++ End V A L I D A T E action +++++[ deployerId=2 ]. Total time:[#7: 3.016 sec]
Jun 15, 2009 1:07:06 PM [Path ]:+++++ Starting D E P L O Y action +++++ [ deployerId=2 ] [ timerId=9]
Jun 15, 2009 1:07:06 PM [Path ]:Selected archives for deployment. [ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca
Jun 15, 2009 1:07:06 PM [Debug ]:Got full sdu path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
Jun 15, 2009 1:07:06 PM [Path ]:component version handling rule is UpdateLowerVersionsOnly.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:deployment workflow strategy is safety deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:Error strategies[ deployerId=2 ]:
Jun 15, 2009 1:07:06 PM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2009 1:07:06 PM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
Jun 15, 2009 1:07:06 PM [Debug ]:deployer initialized successfully:[id:#11, elapsed: 15 ms.].[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Debug ]:Total time:[#11: 0.015 sec].[ deployerId=2 ]
Jun 15, 2009 1:07:06 PM [Path ]:Starting deployment.[ deployerId=2 ]
Jun 15, 2009 1:07:17 PM [Debug ]:clusterRestartTriggered for transactionId:223, clusterEventAction:cluster restart triggered
Jun 15, 2009 1:07:17 PM [Debug ]:Mark transaction '223' as offline phase.
Jun 15, 2009 1:07:17 PM [Info ]:+++ Performing offline deployment. Server is being restarted +++.The timeout for the operation is: 86400 sec.
Jun 15, 2009 1:07:17 PM [Path ]:+++ Wait for server response +++. Elapsed: 0 ms.
Jun 15, 2009 1:07:47 PM [Path ]:+++ Wait for server response +++. Elapsed: 484 ms.
Jun 15, 2009 1:08:19 PM [Path ]:+++ Wait for server response +++. Elapsed: 30484 ms.
Jun 15, 2009 1:08:49 PM [Path ]:+++ Wait for server response +++. Elapsed: 62140 ms.
Jun 15, 2009 1:09:19 PM [Path ]:+++ Wait for server response +++. Elapsed: 92156 ms.
Jun 15, 2009 1:09:49 PM [Path ]:+++ Wait for server response +++. Elapsed: 122171 ms.
Jun 15, 2009 1:10:19 PM [Path ]:+++ Wait for server response +++. Elapsed: 152171 ms.
Jun 15, 2009 1:10:49 PM [Path ]:+++ Wait for server response +++. Elapsed: 182296 ms.
Jun 15, 2009 1:11:20 PM [Path ]:+++ Wait for server response +++. Elapsed: 212905 ms.
Jun 15, 2009 1:12:22 PM [Info ]:Engine is up and running. Wait for engine deployment result.
Jun 15, 2009 1:12:22 PM [Debug ]:DC API will create new CM
Jun 15, 2009 1:12:52 PM [Path ]:+++ Wait for server response +++. Elapsed: 305686 ms.
Jun 15, 2009 1:13:22 PM [Path ]:+++ Wait for server response +++. Elapsed: 335685 ms.
Jun 15, 2009 1:13:53 PM [Path ]:+++ Wait for server response +++. Elapsed: 365701 ms.
Jun 15, 2009 1:14:23 PM [Path ]:+++ Wait for server response +++. Elapsed: 395701 ms.
Jun 15, 2009 1:14:53 PM [Path ]:+++ Wait for server response +++. Elapsed: 425763 ms.
Jun 15, 2009 1:15:24 PM [Path ]:+++ Wait for server response +++. Elapsed: 456856 ms.
Jun 15, 2009 1:15:54 PM [Path ]:+++ Wait for server response +++. Elapsed: 487012 ms.
Jun 15, 2009 1:15:57 PM [Info ]:Engine is up and running. Wait for engine deployment result.
Jun 15, 2009 1:15:57 PM [Info ]:server is online, time:[id:#10, elapsed: 520059 ms.]
Jun 15, 2009 1:15:57 PM [Path ]:Deployment completed. Preparing the deployment result.[ deployerId=2 ]
Jun 15, 2009 1:15:57 PM [Path ]:
Sorted Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca --> xappscpmsm~strategymanagement.sda'
     Sdu info :name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
          Deploy status is 'Aborted'
          Description:'1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
     2. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Aborted'
          Description:'1. Contains Aborted deployment component:
sdu id: sap.com_xappscpmsm~strategymanagement
sdu file path: F:\usr\sap\PI7\J71\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\223\CPMSTRMGMAPC00_0_sca1245064026979\DEPLOYARCHIVES\xappscpmsm~strategymanagement.sda
version status: NEW
deployment status: Aborted
description: 1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
Deployment Items -
     1. Client path '
sap-pi7\sapmnt\trans\EPS\in\CPMSTRMGMAPC00_0.sca'
     Sdu info :name 'CPM_STR_MGM_APC', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '1000.700.0.1.0.20080221071842'
          Deploy status is 'Aborted'
          Description:'1. Contains Aborted deployment component:
sdu id: sap.com_xappscpmsm~strategymanagement
sdu file path: F:\usr\sap\PI7\J71\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\223\CPMSTRMGMAPC00_0_sca1245064026979\DEPLOYARCHIVES\xappscpmsm~strategymanagement.sda
version status: NEW
deployment status: Aborted
description: 1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
          Time statistics:
          Contained DCs:
          1.1:name 'xappscpmsm~strategymanagementdic', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465042'.
          1.2:name 'xappscpmsm~strategymanagementdoc', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465046'.
          1.3:name 'xappscpmsm~strategymanagement', vendor 'sap.com', location 'MAIN_CPMSM70V_D', version '2465295', software type ('J2EE', sub type ''), dependencies :[none]
                    Deploy status is 'Aborted'
          Time statistics( ms ):
               1.deployment : 34906
                    1.1.Notify:Event triggered : 157
                    1.2.Disable LCM deployment : 34656
                         1.2.1.Perform delivery : 34656
                              1.2.1.1.Application Deployer : 34656
                    1.3.Notify Observers : 15
                         1.3.1.Persist in storage : 15
                    1.4.Notify:Event performed : 78
               2.Persist in storage : 16
                    Description:'1. class com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException
           -> class java.lang.NullPointerException'.
          1.4:name 'xappscpmsm~strategymanagementactions', vendor 'sap.com', location 'n/a', version '1', software type ('n/a', sub type ''), dependencies :[none]
                    Deploy status is 'AlreadyDeployed'
                    Description:'1. Already deployed component has version:2465041'.
Jun 15, 2009 1:15:57 PM [Info ]:
Deploy Result Description: Deployment exception occurred during deploy online data. Reason :An error occurred while deploying the deployment item 'sap.com_xappscpmsm~strategymanagement'.; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.com_xappscpmsm~strategymanagement. Cannot deploy it.
[ deployerId=2 ]
Jun 15, 2009 1:15:57 PM [Info ]:+++ Deployment finished with status 'Error' +++.[ deployerId=2 ][#10: 530.465 sec]
Jun 15, 2009 1:15:57 PM [Path ]:+++++ End D E P L O Y action +++++[ deployerId=2 ]. Total time:[#9: 530.465 sec]
Jun 15, 2009 1:15:57 PM [Debug ]:Incorrect client ID. The stub is not connected yet.
Jun 15, 2009 1:15:57 PM [Debug ]:Incorrect client ID. The stub is not connected yet.

Add-on Conflict error while installing add-on LOCIN release 100

Hi experts,
I want to install the add-on for India Localization for IS-Utilities i.e., LOCIN release 100. I have downloaded the add-on and also the CRT(SAPK-10001INLOCINISU) required for the add-on.
we got an error while installing the add-on it is
"OCS package SAPK-10001INLOCINISU does not match the current software component vector"
if we remove the CRT from the queue and start the installation then it will give add-0n conflict error.
Conflicts Between Add-On LOCINISU 100 and Support Packages
Component    Release      Support Package        Information on
                                                  Conflict Resolution
FI-CA        600          SAPK-60004INFICA       Include CRT
                           SAPK-60005INFICA       Include CRT
                           SAPK-60006INFICA       Include CRT
                           SAPK-60007INFICA       Include CRT
                           SAPK-60008INFICA       Include CRT
                           SAPK-60009INFICA       Include CRT
                           SAPK-60010INFICA       Include CRT
Plz tell the solution for this.

Hi,
I had somthng like this recently with SCMEWM....
1. Clear out your EPS/in directory
2. Download the latest version of the add-on and all the patches ===> the latest CRT's will be in the patches.
3. Unpack them and try import again.
Also if you have not seen or read:
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=950513
Mark

Installation of EHP4 - Has anyone got this working

Hi All;
I know that SAP will not like to hear this, but the installation of EPH4 using Solution Manager is a frustrating exercise in futility. I have been trying to install EHP4 for over 2 months now and it keeps failing. I have an open HIGH ticket with SAP and they have moved me forward in the installation process due to Bugs in their tools, but once I get 1 bug resolved I quickly hit another one. SAP Support keeps bouncing me all over the place. I feel like I am dealing with a Beta product rather then a General release solution. Furthermore, SAP's support sense of urgency is completely different then their customer base. I have also had our SAP account manager in to express my frustration and while sympathetic to my situation, he acknowledges there is little he can do.
My latest issue is similar to this link:
Re: EHP4 Error in PREPARE_JSPM_QUEUE
Specifically, I have gotten over the ABAP installation and now I am in the JSPM portion. The installation fails on the PREPARE_JSPM_QUEUE phase with the error:
Here are the last few lines of our PREPARE_JSPM_QUEUE_CSZ_01.LOG file:
Apr 1, 2010 8:56:34 PM [Info]:      com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.connect(AbstractToolConnector.java:729) [Thread[main,5,main]]: Connected to host vmsapdev02 on port 6250.
Apr 1, 2010 8:56:34 PM [Warning]:   com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.discardMsg(AbstractToolConnector.java:775) [Thread[JSPM,5,main]]: Discarding message $com.sap.sdt.sltool.rapi.connector.MsgData@39402772
Apr 1, 2010 8:56:34 PM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:139) [Thread[main,5,main]]: JSPM was started successfully.
Apr 1, 2010 8:56:34 PM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:184) [Thread[main,5,main]]: Trying to log in with user J2EE_ADMIN.
Apr 1, 2010 8:56:34 PM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:190) [Thread[main,5,main]]: JSPM detect non deployable components login request property is set to "true".
Apr 1, 2010 8:56:42 PM [Info]:      com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.login(SAPJupJSPMRapiAdapter.java:199) [Thread[main,5,main]]: JSPM successfully logged in with user J2EE_ADMIN.
Apr 1, 2010 8:56:42 PM [Info]:    com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.connect(SAPJupJSPMRapiAdapter.java:143) [Thread[main,5,main]]: JSPM was connected successfully.
Apr 1, 2010 8:56:42 PM [Info]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createQueueFromStack(SAPJupJSPMRapiAdapter.java:287) [Thread[main,5,main]]: Starting creation of deploy queue from file /usr/sap/trans/EPS/in/SMSDXML_DEV_20100331164248.069.xml.
Apr 1, 2010 8:56:43 PM [Info]: com.sap.sdt.sltool.rapi.connector.AbstractToolConnector.handleMsgClosed(AbstractToolConnector.java:560) [Thread[JSPM,5,main]]: Reporting failed commlink.
Apr 1, 2010 8:56:45 PM [Info]:         com.sap.sdt.jspm.rapi.connector.JSPMConnector.waitForJSPMTermination(JSPMConnector.java:483) [Thread[main,5,main]]: JSPM stopped.
Apr 1, 2010 8:56:45 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Apr 1, 2010 8:56:45 PM [Error]:             com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Stack definition file /usr/sap/trans/EPS/in/SMSDXML_DEV_20100331164248.069.xml contains no applicable SP stacks. For details see SCAN_INBOX*.LOG in current JSPM log directory.
JSPM version is 7.01.5.1.3. Current JSPM log directory is /usr/sap/DEV/DVEBMGS00/j2ee/JSPM/log/log_2010_04_01_20_56_32.
Apr 1, 2010 8:56:45 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:710) [Thread[main,5,main]]: Could not create deploy queue.
Apr 1, 2010 8:56:45 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Apr 1, 2010 8:56:45 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/04/01 20:56:24.
Apr 1, 2010 8:56:45 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/04/01 20:56:45.
Apr 1, 2010 8:56:45 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:21.019.
Apr 1, 2010 8:56:45 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
Here are the last few lines in our SCAN_INBOX_01.LOG file:
EHP4 FOR SAP ERP 6.0 / NW7.01 - EHP4 FOR ERP 6.0_NW701
Mar 23, 2010 11:33:27 AM [Info]: Filtering delivery units from stack /usr/sap/trans/EPS/in/SMSDXML_DEV_20100310200324.828.xml.
Mar 23, 2010 11:33:27 AM [Warning]: Rejected delivery unit for component sap.com/JSPM from the stack.
Mar 23, 2010 11:33:27 AM [Warning]: JSPM will not patch NWDI build component sap.com/SAP_BUILDT, because it does not have any deployable content. See SAP Note 1027362 for more information.
Mar 23, 2010 11:33:27 AM [Warning]: Rejected delivery unit for component sap.com/SAP_BUILDT from the stack.
Mar 23, 2010 11:33:27 AM [Warning]: No patch for SAP KERNEL NONUNICODE LINUX_X86_64 found in support package SAP KERNEL that is located in /usr/sap/trans/EPS/in.
Mar 23, 2010 11:33:27 AM [Warning]: Support package SAP KERNEL that is located in /usr/sap/trans/EPS/in is incomplete. See previous messages.
Mar 23, 2010 11:33:27 AM [Warning]: Rejected delivery unit for component sap.com/SAP KERNEL from the stack.
Mar 23, 2010 11:33:27 AM [Warning]: No patch for SAP KERNEL NONUNICODE LINUX_X86_64 found in support package SAP KERNEL that is located in /usr/sap/trans/EPS/in.
Mar 23, 2010 11:33:27 AM [Warning]: Support package SAP KERNEL that is located in /usr/sap/trans/EPS/in is incomplete. See previous messages.
Mar 23, 2010 11:33:27 AM [Warning]: Rejected delivery unit for component sap.com/SAP KERNEL from the stack.
Mar 23, 2010 11:33:27 AM [Warning]: No patch for SAP KERNEL NONUNICODE LINUX_X86_64 found in support package SAP KERNEL that is located in /usr/sap/trans/EPS/in.
Mar 23, 2010 11:33:27 AM [Warning]: Support package SAP KERNEL that is located in /usr/sap/trans/EPS/in is incomplete. See previous messages.
Mar 23, 2010 11:33:27 AM [Warning]: Rejected delivery unit for component sap.com/SAP KERNEL from the stack.
Mar 23, 2010 11:33:27 AM [Warning]: Support package stack SAP NETWEAVER,SAP ERP,EHP4 FOR SAP ERP 6.0_NW701 SAP EHP1 FOR SAP NETWEAVER 7.0,2005,EHP4 FOR ERP 6.0_NW701 (/usr/sap/trans/EPS/in/SMSDXML_DEV_20100310200324.828.xml) is rejected. Check previous warning messages.
I don't know why we are getting these warning messages since the Kernel files (non-unicode for the ABAP portion) and Unicode for the Java stack are in the /usr/sap/trans/EPS/in subdirectory.
SAP has been in my Solution Manager and confirms everything is setup ok. We have a Linux Red Hat EL 5.0 64 bit Application server that has been successfully upgraded from SAP 4.7 x 110 to SAP ECC 6.0 EHP1.
Our Database server is also Linux Red Hat EL 5.0 64 bit running Oracle 10.2.0.4. Our system is vanillia. We are an IT shop so we lots of knowledgable people in the company and can response to SAP requests quickly (which are slow in coming).
I am also wondering if this warning message is causing any problems. SAP has confirmed that our parameter settings are correct but I wonder since I am getting this message.
Apr 2, 2010 11:37:18 AM [Warning]: Software feature SAP ERP 6.0 : SAP
ECC Server - 16 (08/2009) found in stack definition
file /usr/sap/trans/EPS/in/SMSDXML_DEV_20100331164248.069.xml is
applicable for system SID: DEV and HOST: vmsapdev02, but the current
system is SID: DEV and HOST: vmsapdbdev02. This software feature will
be skipped.

Hi NIraj;
Thank you for the prompt reply. In MOPZ I have selected the NON UNICODE portion of the Kernel. Here is a portion of the XML file. I believe this is the area that specifies the NON UNICODE Kernel upgrade. These files are in the /usr/sap/trans/EPS/in directory. Any other ideas?
<software-component>
    <caption>SAP KERNEL 7.01 64-BIT</caption>
    <ppms-number>01200615320200011147</ppms-number>
    <runtime-type>OS</runtime-type>
    <name>KRNL64NUC</name>
    <version>7.01</version>
    <vendor>sap.com</vendor>
    <support-package>
     <caption>SP055 for SAP KERNEL 7.01 64-BIT</caption>
     <name>SP055</name>
     <vendor>sap.com</vendor>
     <ppms-number>01200615321100059367</ppms-number>
     <sp-level>055</sp-level>
     <patch-level>55</patch-level>
     <archives>
      <os-set os="LINUX_X64">
       <db-set db="DBINDEP">
        <archive-name patch-level="55" os="LINUX_X64" db="DBINDEP">SAPEXE_55-10005922.SAR</archive-name>
       </db-set>
       <db-set db="ORA">
        <archive-name patch-level="55" os="LINUX_X64" db="ORA">SAPEXEDB_55-10005926.SAR</archive-name>
       </db-set>
      </os-set>
     </archives>
    </support-package>
   </software-component>
   <software-component>
    <caption>SAP KERNEL 7.01 64-BIT UNICODE</caption>
    <ppms-number>01200615320200011148</ppms-number>
    <runtime-type>OS</runtime-type>
    <name>KRNL64UC</name>
    <version>7.01</version>
    <vendor>sap.com</vendor>
    <support-package>
     <caption>SP055 for SAP KERNEL 7.01 64-BIT UNICODE</caption>
     <name>SP055</name>
     <vendor>sap.com</vendor>
     <ppms-number>01200615321100059368</ppms-number>
     <sp-level>055</sp-level>
     <patch-level>55</patch-level>
     <archives>
      <os-set os="LINUX_X64">
       <db-set db="DBINDEP">
        <archive-name patch-level="55" os="LINUX_X64" db="DBINDEP">SAPEXE_55-10005984.SAR</archive-name>
       </db-set>
       <db-set db="ORA">
        <archive-name patch-level="55" os="LINUX_X64" db="ORA">SAPEXEDB_55-10005987.SAR</archive-name>
       </db-set>
      </os-set>
     </archives>
    </support-package>
   </software-component>
</sp-feature-stack>

ST-PI upgrade issue in IS_SELECT

I am running PREPARE on a 4.6C (Linux/DB2) > ECC 6.0 upgrade and have recieved the warning that 'Add-on ST-PI is toohigh for this upgrade".
I have downloaded the 'ST-PI 2008_1_710' patches (SAPKITLRE1, SAPKITLRE2, SAPKITLRE3) into /usr/sap/put and used SAPCAR to extract them to the EPS/in box.
While running the the IS_SELECT phase I select the 'upgrade from Saint packages' and the upgrade program indicates that it reads the EPS/in directory but does not find any matching SAINT package.
What is the correct procedure?
I am running SAPup version 7.00/3, build 25.024.

This:
"Looks like 1 important file is missing
2008_1_700 KITLRDG.CAR SAPKITLRDG for 2008 ST-PI Target release
or
2005_1_700 KITLQIG.CAR are to be placed in EPS/in and select
"Upgrade with SAINT Package".
https://service.sap.com/sap/support/notes/1228899
Regards
Srikanth M
Seemed to have worked.
I am again unfortunately stuck with the the same issue with the ST -A/PI add on.
I have a source release of 01M_R3_46C and does not recognize the 01M_ECC600 ,01M_BCO700 , 01M_BCO710 packages I extracted.

Problem to change ST-A/PI to 01K_ECC600 during Prepare to upgrade ERP60

I tried to upgrade ERP2004 to ERP6.0. During in Prepare Phase, it prompt with below screen :
Product update and media decision overview:
Decide about update type and the Add On media kind.
Select the Add-on you want to make or change a decision:
Select no product, if you are finished.
         Add-on Id    Start Rel         Dest Rel       Status                             Note
01)     EA-IPPE    300                 400              INST/UPG WITH STD CD 632429
02)     PI_BASIS   2005_1_640    2005_1_700 INST/UPG WITH STD CD 555060
03)     ST-PI         2005_1_640    2005_1_700   INST/UPG WITH STD CD 539977
04)     P3A          V500               V600            UPG WITH SAINT PACK   1162521
05) X ST-A/PI     01K_ECC500    ?               UNDECIDED                      69455
I tried to change ST-A/PI to 01K_ECC600 with 'UPG SAINT' and I already unzipped the related file for ST-A/PI 01K_ECC600 to \usr\sap\trans. But it returned with "No matching SAINT package for 'ST-A/PI' found.".
Pls advise.
Thanks.
Edward TSo

Hi,
You have to uncar the add-on in /usr/sap/trans/EPS/in directory.
Keep your add-on sar/car file in /usr/sap/trans folder and use following command
cd /usr/sap/trans
SAPCAR -xvf xxxxxxxx.sar
it will automatically unzip the files in /usr/sap/trans/EPS/in directory.
Regards,
Sachin Rane.

Couldnt upgrade the java stack after upgrading the abap to ehp1

Hi
I have upgarded the system to ehp1 but i couldnt continue to upgarde the java stack to 18th patch.The reason is it coudlnt find the file JSPM02P-2-20002796.SCA. I couldnt find this file . i couldnt find only this file JSPM02P_4-20002796.SCA . I tried to put this file in inbox and tried to run the jspm but it is not recognizing this as a valid file and its expecting JSPM02P-2-20002796.SCA. I couldnt find this file can anyone suggest me where i could find this file.
Thanks and Regards
MA.Sreenivasan

When you download the files, be sure to select "Save As File", which next to the "Add to Download Basket" button. Copy that SPStab.xml file to your EPS/in directory. Without that, it won't recognize the files even if they are there.

ECC-600 EHP4 upgrade with VIRSAHR 520 700 - PREP_EXTENSION/ADDON_QCALC

Hi
We are getting following error at phase PREP_EXTENSION/ADDON_QCALC in the ECC 6.0 upgrade:
3 ETN256 You want to install the following add-on components:
3 ETN248 Component: "VIRSAHR" rel. "520_700", Support Package
level: "0" (component type "A")
3 ETN248 Component: "VIRSANH" rel. "520_700", Support Package
level: "0" (component type "A")
2 ETN085X"2. Adding Add-on Installation Queue" " " " " " "
3 ETN262 Calculating queue part for add-on "VIRSAHR" rel. "520_700"
3 ETN490 Use the Add-On installation package "SAPK-523EXINVIRSAHR"
(type &4"AOX") for Add-On &2"VIRSAHR" rel.&3"520_700"
3 ETN245 The following import prerequisites of OCS Package "SAPK-
523EXINVIRSAHR" have not been met:
3 ETN264 In the (alternatively) Requirement set "01":
3WETN491 Required software component "SAP_HR" rel."600" is not installed2WETN543 OCS package "SAPK-523EXINVIRSAHR" does not match the current
software component vector
1 ETN214X."**************************************************"
We have alreacy checked note 1002147, which clearly states that we have to include SAPK-523EXINVIRSAHR in the upgrade. SAP_HR is part of the upgrade.
We have included SAP_HR and other Support Package as per the queue generated by Solution Manager, but we did not include VIRSAHR & VIRSANH Packages until we got to this phase. We then included these support packages in eps\in directory, but we are now getting this error now.
Any ideas?
Regards
Chandu

Hi
This is what the solution provided by SAP Support:
Quote:
we have finally found the problem, it's a bug in the package upload
functionality used by the upgrade. The consequence of this bug is that
Support Packages whose EPS files (.PAT files) have a certain string in
the name, namely the string 0000000 after the _ and before .PAT
extension, are not properly uploaded to the ABAP system and hence are
not visible or known to the upgrade.
This bug will be fixed in the next upgrade tool fix, but in the meantimeyou can use the following workaround:
Check your EPS/in directory after the CAR/SAR Archives of the SPs are
extracted and rename all .PAT and .ATT files, which have a name like
*_0000000.PAT (or *_0000000.ATT), by changing the string 0000000 to
9000000. For example, for the VIRSANH SP SAPK-52302INVIRSANH rename the
file VS30020106486_0000000.PAT to VS30020106486_9000000.PAT
Afterwards, the upgrade will upload the informations about the SP
properly and the SP can be included into the upgrade.
Files:
31/01/2007 07:32 329 VS30020106486_0000000.ATT
31/01/2007 07:32 554,073 VS30020106486_0000000.PAT
If these two files are renamed to e.g.
VS30020106486_9000000.ATT
VS30020106486_9000000.PAT
the affected VIRSANH SP2 is uploaded correctly by the upgrade
functionality and the SP inclusion of the VIRSANH SPs works.
Sorry, as of now I cannot promise you a date when the tool fix will be
available. I have found this bug only today in the evening (german time)and will discuss this with the responsible colleagues tomorrow.
Afterwards, I will know more...
Unquote:
Hope this helps. We have decided against upgrading to 530_700 as it will involve upgrading GRC system and also new version has lot of new functionalities, which we like explore it after the ECC upgrade.
Also, I would not suggest deleting VIRSAHR as all the config and customising done for VIRSAHR will be lost.
Regards
Chandu
Edited by: Chandu Cheeti on Jan 17, 2010 11:19 AM

EPS/in directory

Similar Messages

Maybe you are looking for