ECC6.0 SP upgrade

Hi,
We are trying to do a SP upgrade from SP9 to SP13. Is there any known issues with technical upgrade or is there a place in service market place where I can get info about?
Teresa

Also refer:
[/message/4875558#4875558 [original link is broken];
[http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ddic-activation-error-when-applying-sp13-on-erp-60-ides-2259404]

Similar Messages

ECC6.0 Upgrade and BW Extractors

Hi Experts,
We are doing a Source system upgrade from 4.6c to ECC6.0 just a Technical upgrade. Can you please let me know if we need to delete all the delta queues and re-initialize delta.
Following are the 4.6c Pre- Export Activities in relation BW.
1. Lock the users
2. Clear the entire delta queues in RSA7 (till we achieve - 0 records in BW) and make sure no outbound queues are empty in SMQ1
3. Delete Set -up table data.
4. Reshedule V3 Jobs
5. ReSchedule - BW process chains
After upgrading to ECC6.0
1. SM59 connections with new system.
2. Restore Source System connections in RSA1
3. Replicate DS and Activate Transfer Structure. (In relation to BW: we have done the technical upgrade from 3.x to BI7.0 (but the datasoucre and data flow are still 3.x).
After all Post processing of ECC6.0 Upgrade activities, the source system is only available to users for posting the transaction.
Please let me know if we need to delete all the delta queues and re - initialize delta.
1.We are not installing any new business content extractors from ECC6.0 - Just using same 4.6c extractors and structures.
2.And consider that no users post any transaction after clearing the delta queues in RSA7.
Appreciate your feedback,

Hello Subbu,
There is no need to reinitialize the extractors, the steps you mentioned in your original post are enough, the reason
for these steps is to make sure that there is no data left in sm13, lbwq, ras7, setup tables etc, you need to run the related infopackages twice on the BW side to clear the BW repeat part of the queue in RSA7, if you have a doubt that this was
not done you can goto rsa7, select the queue and on the next screen you can check if there is any data available in the
delta repeat part of the queue.
The reason for the step is that that the upgrade could potentially change an extract structure for a datasource and then if you
have data in the old format it may not be possible to upload it in the old format.
I repeat though there is NO need to delete the current entries in RSA7 and reinitialize.
Best Regards,
Des

ALV Layouts are missing in ECC6 after upgrade

Dear Friends,
we have an issue of missing ALV Layouts in ECC6 after upgrade of ECC6 from 4.7 version
For example, we have a custom table ZRCILOT, data displayed using tocde se16, but when we check layout are missing in ECC6 but the same exist in 4.7 version.
please check the attached screen-shots.
kindly suggest, is there any possibility to retrive it.
Thanks,
Munvar Basha.

Hello
Variants should be preserved by the upgrade...
You could export/import layout using the report from the here under note
Regards
551178 - FAQ ALV Layout
During the upgrade of or when importing Support Packages?
Answer: Layouts created by the customer are retained and you can continue to use them.
643330 - ALV layout: Importing and exporting layouts

Impacts on ECC6 Functional Upgrade

We have just technical upgraded our SAP ERP 4.6 to ECC6 recently, we're soon going to perform the functional upgrade of the ECC6.
I would like to check if the ECC6 functional upgrade will have any impact to our existing BW 3.5 system?
Please advice, thanks.

i dont think, the new plugins will impact your BI system. if you go for the technical upgrade, this may break your source system connection and that time you have to do source system restrore connection.
Other than that, no major impacts would be happened in the BI system.

SAP 4.7 to ECC6 EHP5 Upgrade inc.OGSD - "/ICO/MOC_NEW_GUI" nametab error

Hello all,
I'm currently running a SAP upgrade from 4.72 to ECC6 EhP5 SPS6.
This upgrade include OGSD upgrade from4.72 SP12 to OGSD 6.10 SP5.
Duing phase upgrade phase RUN_RSPTBFIL_DEST, I have the following error message : Could not read nametab "/ICO/MOC_NEW_GUI".
According to OSS note 1377262, I download fix A61000INOGSD.SAR and extract file A-61000INOGSD.SAP in <upgdir>/cofiles (and also in <transdir>/cofiles).
Phase RUN_RSPTBFIL_DEST is still in error when I repeat it.
I note that content of A-61000INOGSD.SAP file is a little bit different regarding my error message:
Inside file:
I 2EETW109 table "/ICO/MOC_NEW_GUI" does not exist in nametab.
My error message:
2EETG011 "[DESTINFO] Could not read nametab""/ICO/MOC_NEW_GUI"
Many thanks for your help & feedback,
Chris

Hello Chris,
we experienced the same issue as you.
After discussion with the SAP Support team, it appears that this migration path is not the good one.
The right procedure is now to upgrade to ECC6 EhP5 with OGSD 6.10 SP0 and then to apply manually the SPs you want on OGSD add-on.
I think they are currently updating the corresponding OSS Notes.
I hope it will help.
Vincent

Runtime Errors SYNTAX_ERROR in SAPLS_CODE_INSPECTOR after the ECC6.0 upgrad

we recently upgraded our development test sandbox from 46C to ECC6.0 using downtime minimized strategy for practice purposes.After a sucessful completion of the upgrade we applied all the support packages successfully upto the latest available. Upon testing we found that everything else works fine except code inspector. Everytime we go to transaction sci we get syntax error
Runtime Errors         SYNTAX_ERROR
Date and Time          08/20/2008 08:26:29
Short text
     Syntax error in program "SAPLS_CODE_INSPECTOR ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLS_CODE_INSPECTOR " in
      include "LS_CODE_INSPECTORTOP " in
     line 11:
     ""SCI_DYNP" must be a flat structure. You cannot use internal tables, s"
     "trings, references, or structures as components. ."
     The include has been created and last changed by:
     Created by: "SAP "
     Last changed by: "CRENSHAWDP "
     Error in the ABAP Application Program
     The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Please eliminate the error by performing a syntax check
     (or an extended program check) on the program "SAPLS_CODE_INSPECTOR ".
     You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
r analysis
The following syntax error was found in the program SAPLS_CODE_INSPECTO
""SCI_DYNP" must be a flat structure. You cannot use internal tables, s
"trings, references, or structures as components. ."
to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
   To save the description, choose "System->List->Save->Local File
2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
    In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
tem environment
SAP-Release 700
Application server... "kiel"
Network address...... "138.254.140.161"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000B7B2ED600"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "kiel"
Database type..... "ORACLE"
Database name..... "UPD"
Database user ID.. "SAPR3"
Terminal................. "D800204486"
Char.set.... "en_US.ISO8859-1"
SAP kernel....... 700
created (date)... "Jun 22 2008 20:58:25"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 166
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 16128
EM...... 8379840
Heap.... 0
Page.... 40960
MM Used. 705904
MM Free. 3481488
r and Transaction
Client.............. 070
User................ "CRENSHAWDP"
Language key........ "E"
Transaction......... "SCI "
Transactions ID..... "48AB59A7D7E00112E10080008AFE8CA1"
Program............. "????????????????????????????????????????"
Screen.............. " "
Screen line......... 0
Information on where terminated
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080820
SY-UZEIT 082629
SY-XPROG
SY-XFORM
Internal notes
    The termination was triggered in function "ab_genprog"
    of the SAP kernel, in line 1551 of the module
     "//bas/700_REL/src/krn/runt/abgen.c#10".
    The internal operation just processed is " ".
    Internal mode was started at 20080820082629.
    Program name.........: "SAPLS_CODE_INSPECTOR ".
    Error message........: ""SCI_DYNP" must be a flat structure. You cannot use
     internal tables, s".
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit      = 2684354560
=> Stack limit     = unlimited
=> Core limit      = unlimited
=> File size limit = unlimited
=> Heap address = 0x11716f260
=> Stack address = 0xfffffffffff2a20
=> Stack low     = 0xfffffffffff2a20
=> Stack high    = 0xffffffffffff710
=> Stack Trace:
#AixStack() at 0x1000a2474
#CTrcStack2() at 0x1000a256c
#rabax_CStackSave__Fv() at 0x1000d0e04
#ab_rabax() at 0x1000cd7e4
#ab_genprog() at 0x100b3d5f8
#newload__FPCcP13TmpSubpoolDirUiPUi() at 0x1002194ac
#ab_LoadProgOrTrfo__FPCcUiPUi() at 0x10021905c
#ab_load() at 0x100218e2c
#ab_LoadMainProg() at 0x100820d6c
#dystartx() at 0x100ade944
#dy_cdiag() at 0x100833174
#ab_ctransaction__Fv() at 0x100ae1ef0
#ab_retdynp__Fi() at 0x100821c98
#ab_dstep() at 0x100821924
#dynpmcal() at 0x100e932e0
#dynppai0() at 0x100e905ec
#dynprctl() at 0x100e99d48
#dynpen00() at 0x100e8cc18
#Thdynpen00() at 0x1000f9ed4
#TskhLoop() at 0x1000fec7c
#ThStart() at 0x100115890
#DpMain() at 0x1017f4b14
#nlsui_main() at 0x1018e2b6c
We contacted SAP OSS about this problem and they suggested that we check our LS_CODE_INSPECTORTOP include in program SAPLS_CODE_INSPECTOR and revert it to the original version. We did that and still are getting this error. Any suggestions how to fix this issue. All advices are welcome.
Thanks.
Kamran

Nope... this is SAP standard code so I will reply to the OSS and wait for them to come back to you.
Regards
Juan

4.7EEx1.10 to ECC6.0 upgrade and Unicode conversion

Hi Experts,
We are going to initiate the upgrade from next month onwards. Subsequently i have started preparing the plan and strategy for the same.
As our current setup is 4.7EEx110/Win 2003 R2-64 bit/Oracle 10.2.0.4.0 (Non unicode). And we have recently migrated on to this setup from WIn2k 32 bit. Also the current hardware is Unicode compatible.
With respect to strategy for achieving this Upgrade and Unicode conversion, i am planning as follows.
Step 1) Perform Unicode conversion on the current landscape (Both Export/import on the same servers)
Step 2) Setup Temporary landscape as part of Dual maintenance strategy and migrate data from the current systems to temporary systems using backup/restore method.
Step 3) Perform the SAP version upgrade on the current landscape and setup transport routes from temporary to current landscape in order to keep it in sync
Step 4) after successful upgrade, decommission the temporary landscape
Please provide your suggestions and valuable advices if there is anything wrong with my strategy and execution plan.
Regards,
Dheeraj

Hi,
Thanks. As i have already referred these notes as i am seeking advise with respect to my upgrade approach.
However i have planned to perform in the following manner.
1) Refresh Sandbox with Prod data and perform Upgrade to ECC6.0 EHP5 & subsequently Unicode conversion on the same server (Since both export & Import has to perform on the same hardware as we have recently migrated on this hardware which is Unicode compatible)
2) Setup temporary landscape for DEv & QAs and establish transport connection to Production system in order to move urgent changes
3) Keep a track of the changes which have transported during upgrade phase so that the same can be implemented in the upgraded systems i.e. Dev & QAS
4) After Sandbox Migration and signoff, we will perform Dev & QAS upgrade & unicode conversion on the same hardware (Note: Since these are running on VMware can we export the data from the upgraded system and import on to a new VM?)
5) Plan for production cutover and Upgrade the Prod system to ECC6.0 Ehp5 and then Unicode conversion. As i am planning to perform upgrade over the weekend and then Unicode conversion activity in the next weekend (Is it a right way?)
My Production setup: DB on one Physical host and CI on separate Virtual host
6) After the stabilization phase, we are planning for OS & DB upgrade as follows:
a) Windows upgrade from 2003 R2 to Windows 2008 R2
b) Oracle Upgrade from 10.2 to 11.2
If anyone thinks that there is anything wrong with my above approach and need changes then please revert.
I have one more doubt as I am going to upgrade 4.7EEx110 (WAS 620, Basis SP64) to ECC6.0 EHp5.As I presume that I can straight away upgrade from the current version to ECC6.0 Ehp5 without installing EHP. Kindly confirm
Thanks

Spool header is getting truncated in SP01 after ECC6.0 upgrade

Hi Experts,
We have recently upgraded our SAP System from 4.6C version to ECC6.0. We are facing some problem with Spool display.
Issue: Column header is truncated in spool list display through SP01 (Applied necessary notes)/ ZSP01(Created based on note 186603). The column header is not getting truncated while executing report in online mode.
Can anybody else got the problem or have any suggestions to rectify this problem?
Rgds,
Vinodkumar

Hello Vinodkumar,
I have seen this problem and the solution was to follow the note 1226758:
Do not forget Call SPAD and choose Settings -> Spool System -> Other. Select
'SP01: Number of Columns for List Display from Format'.
Hope it helps to you.
Best regards,
Rafael

Invoice split and copying problem in JEX invoice after ECC6.0 upgrade

Dear All,
After upgrade from 4.6c to Ecc6.0 I am facing following problem in STO billing document(JEX)
1) system created two billing documents for each line item, even though the correction note 885024 applied maually. In 4.6C the system generates single document for the main FG code.
2) The STO line item contains one FG material and one Returnable Packaging material. The system copies packaging item instead of main FG code. In the 4.6c system, the billing document consists only singe line item.
Hope I had summarized the issue well and waiting for expert guidance...
Regards
Sunil Nair

Hi Sunil,
pls check the following criterias in your materials.
Plant
shipping point
shipping conditions
Transportation grp
Loading grp
Regards
Kedasu

ECC6.0 upgrade issue with IDoc release

Hi experts,
we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
has any one faces such situation in the past? if yes, please throw some light.
Thanks in advance.

Hello,
Iam new to SAP. Thars why i cant understand well to do upgrade,
Then i found out some notes from internet about Upgrade : SAP Note Number 857904 (upgrade from Release 6. To 7.0).
In that notes,
Actually i would like to know about some key words (for example : ASSIGNING, REPLACE, TRANSFER. ) which how to work in the Release 7.0
Always i have some objets in 4.6C.
Ex 01: READ DATASET p_dataset INTO wa_record
Ex 02 : TRANSFER i_crhu TO p_crhd
LOOP AT i_crhd.
*disable controls in crhd
    PERFORM f_disable_crhd.
    TRANSFER i_crhd TO p_crhd.
    IF sy-subrc NE 0.
      MESSAGE a045.        "Error when transfering data to error file
    ENDIF.
ENDLOOP.
CLEAR i_crhd.
CLOSE DATASET p_crhd.
IF sy-subrc NE 0.
    MESSAGE a039.                      "Error at close dataset
ENDIF.
OPEN DATASET v_crhd FOR OUTPUT IN TEXT MODE.
And then i have some FM (ex : WS_UPLOAD , WS_DOWNLOAD)
So I have changed the code for WS_UPLOAD by GUI_UPLOAD
                              and WS_DOWNLOAD by GUI_DOWNLOAD
now my problem is to know about some key word which how to work in ECC6 (for example ASSIGNING, REPLACE, TRANSFER. )
thanks in advance
Rathy

ECC6.0 - upgrade from EHP4 to EHP6 - cross release transports.

Hi Experts
We are planning to upgrade our system from ECC6.0 -EHP4 to EHP6.
Source - ECC6.0-EHP4
Target - ECC6.0-EHP6(Enhancement pack6)
Current ECC version -
SAP_BASIS 701 0014 SAPKB70114 SAP Basis Component
SAP_APPL 604 0013 SAPKH60413 Logistics and Accounting
We would like to know during the project if we can do a transport
between upgraded development ECC6.0 -EHP6 to non upgrade production ECC6.0-EHP4.
We have data from note 1090842 and 1273566.
But last 10 lines of note 1090842 are contradictory wherein on one side it says you can do transports between Releases 7.0*, 7.3* and 7.4* and
on other it says it can be problem if support pack levels are different on same release.(if problem can happen on same release with different pack
level then there are greater chances of issues between different releases).Note 1273566 is clear and suggest no issues exist yet for
technical and logical transports between suggested version 700/701 to >=702
Also below is the extract from SUM guide - (SUM-1.0-SP07)
RECOMMENDATION
We strongly recommend that you perform transports only between systems of the same release or enhancement package level, and where the same business functions are activated. If you do not follow this recommendation, you do so at your own risk regarding potential problems.
Please suggest if we need to create Dual maintainance parallel landscape during the tenure of project where two development system co-exist.One
with current and one with upgraded version and changes need to be done on both in parallel.Support fixes and LTO’s go from non upgraded dev to non upgraded prod.
Thanks

Hello
I won't perform cross version transport even if it can be possible.
As of 7.02 cross version transport are prevented by default with option SP_TRANS_SYNC (see here under note).
The best way is, if possible, to have a manual dual maintenance. All corrections created in the Ehp4 dev should be manually recreated in the Ehp6 dev.
What is usually done is to upgrade at first a copy of production for test/discovery purpose, the aim is to identify most of the regressions/evolutions. This will reduce the time you will have to spend in the migrated dev to adjust your system. You then migrate dev and enter in a freeze period where you reduce activity on legacy Ehp4 system to the minimum (bug correction for prod).
One good thing with the manual reprocessing of changes on the Ehp6 system is that this kind of constraint will help consultants to reduce their activity.
Regards
1742547 - Information about component version check in TMS

ECC6.0 upgrade and BW steps for mapping the new ECC6.0 source system

Hello gurus
We are upgrading from R3 4.6C to ECC6.0. We use BW 7.0 SP 18. We will create the new ECC6.0 source system in BW, replicate metadata and everything. The question is how do we copy or reassign the existing objects pointing to our current 4.6c dev system (transfer rules, transformations, infopackages, process chains) to point to the new ECC6.0 dev system ? As a note, we also need to keep the current 4.6c source system objects until go-live o ECC6.0.
What is the common practice in such a case ? I am sure we are not unique...
A prompt response would be appreciated.
Thank you all.

So the plan is to copy dev R3 and upgrade that - then Q r3 copied and upgrade that - then upgrade directly prod R3?
If so - then if it were me - I would firstly prove all this in a sandbox environment where BW dev points at an upgraded sandbox R3 ecc
ie same logical system
Then once that is proved I would organise downtime of BW development for a few months whilst the d-q-p ecc happens
Then when they copy dev r43 to ecc r3 i would then just point BW dev at the new ecc box and go from there (ie clear the deltas - change the logical system name to the new ecc box - replicate meta data - transtru all the datasources - run the process chains nothign to worry about)
However if you cant afford the down time - you may have to have an alternative transport route - ie copy dev BW to a another dev bw box and have an alternative path to production for issues
Then once everything is upgraded redo the changes through d-q-p to get the transports back in line (thats what we did)

ECC6.0 upgrade

Hello Experts
Need some experts advice on Upgrade Project
We are Planning to upgrade from R/3 4.7 to ECC6.0
As QM consultant, what are the important things(points) to be consider
How interface will work?
How to handle the QI stock, Batch material and GR Production inspection
What are the precaution steps to be followed
Any issues/problem to be expected during upgrade
(I know ,i need to test all the exisiting functionality)
please throw some light......
thanks
Sami

Each SAP system is different, each "module" configuration can be done in a hundred ways, especially the QM area is VERY customizable. I could maybe tell some experiences and describe scenarios but it´s pretty unlikely, that they will match yours; you may or not may see symptoms.
Overall: Our upgrade from 4.7 to ERP 6.0 was the smoothest we´ve done (and we started initially with 2.2D 13 years ago). With the QM we had two small issues resulting in dumps because of program errors.
The best way to test that is to copy your production system and upgrade it.
Markus

SAP ECC6 sr3 upgrade error in executing MSSCONCHECK.SQL script

Hello all,
I am facing this error which is very annoying , I am executing Prepare Upgrade script for ECC6 SR3 from SAP 4.7 Sr2 with windows 2003 server and MSSQL 2005 server as backend. I am facing below error
Enter one of these options [continue] := continue
      SAPup message
SAPup> SQL-scripts must be executed by the NT user account T47VMHOST2\t47adm.
       Check your installation of the integrated security procedure
       on host t47vmhost2 and make sure that a login for the NT user
       T47VMHOST2\t47adm exists with the following rules:
       - user T47VMHOST2\t47adm owns the role System Administrators
       - user T47VMHOST2\t47adm has the default database T47
SAPup> Integrated security installed correctly?
            - "no"
            - "yes"
Enter one of these options [no] := yes
Executing script MSSCONCHECK ...
MSSCONCHECK: Connection check failed for the user specified
      SAPup message
SAPup> Errors were found in the logfile MSSCONCHECK.LOG
       after execution of the script MSSCONCHECK.SQL.
SAPup> SAPup cannot proceed until these errors are fixed.
       Please, examine MSSCONCHECK.LOG, fix reported errors and then call R3UP a
gain
I have done a number of changes in system i checked the SIDadm user is assigned a default DB T47 and has said role assigned allready.
I restarted the system after changes and started the prepare batch file again but with sme probelm again. so can anybody guide me on this. I seen a number of threads but there is no any concrete solution providedby them.
will really appreciate any reply.
Mani

Hello Julia,
i read those note but everything seems normal to me on my PC; it has remote access enabled, t47vmhost2/t47adm is the user configured (although its not a domain configuration (installation) but t47vmhost2 is the computer name. So its kind of local user defined in SQL with said authorization. below is the log from file MSSCONCHECK.LOG
[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections.
I am still stuck in ?
Can you please verify if i am using right DVDs
51033495_1     NW 7.0 SR3 Languages DE,EN,ES,FR,IT,NL
51033494_3     NW 7.0 SR3 Upgrade Export 3 of 3
51033494_2     NW 7.0 SR3 Upgrade Export 2 of 3
51033494_1     NW 7.0 SR3 Upgrade Export 1 of 3
51033512_14     NW 7.0 SR3 Upgrade Master Windows Server on x64 64bit
51033508_8     NW 7.0 SR3 Kernel 7.00 Windows Server on x64 64bit Upg ABAP
Pleas help
Mani

ECC6.0 upgrade CATS Workflow

We are upgrading to ECC6.0 and have noticed our custom workflow does not trigger when doing a CATS2 release and save. We have reviewed and implemented all release notes regarding changes to the Data Entry Profile. As a seperate test, we have created a test profile, and followed the note recommending the use of TS31000006 CATS approval by time administrator en lieu of TS20000459. We have checked all requisite settings regarding Org Assignment, SGR and SAZ, as well as assigning the Pers Admin to the employee record. However, when attempting to save a CATS2 timesheet, we get the message "An error has occurred in the starting of the workflow LR365". On further inspection, we notice that the WF Admin gets error messages regarding WS40001001 "Workflow not Activiated". When we try to activate this, the Task TS40008001 cannot be found, although it is clearly in WS40001001. Is this related to the multi-step WF limitation, or is there some other problem afoot here? We are still stuck with the custom WF not triggering either.

Sometimes you may miss of the defined std task in the WF. Run this FM SWD_WFD_REPLICATE_FROM_9999 to pull the task from client 000.
Regards, IA

SAP R/3 4.6B to ECC6 EHP4 Upgrade

Hello,
We are on SAP R/3 4.6B and are in the process/plan of Upgrading to ECC 6...
Is it possible to directly go to EHP4 in a single downtime..?
I am trying to finf the Source/DVD's from the market place but unable to locate one...
Is it possible or should we go to EHP3 only?
If someone has link/path for the software download , kindly help...
Thanks,
RaHuL...

[http://service.sap.com/swdc|http://service.sap.com/swdc]
- download
- Installations and upgrades
- installations and upgrades - Entry by Application Group
- SAP Application Components
- SAP ERP
- SAP ERP Enhance Package
- EHP4 for SAP ERP 6.0 / NW 7.01
Here you should read the info page carefully.
Download the Master Guide and read it to find out about how to perform the upgrade.
- Installation and Upgrade
- <Database Platform>
There is your media. Please note that it is both Installation and upgrade media
and also both ERP and SRM media
In order to get the kernel etc you have to select (instead of "Installation and Upgrade --> Database Platform")
- SAP EHP1 FOR SAP NETWEAVER 7.0
- Installation and Upgrade
- <Operating System>
- <Database Platform>
There is your media together with installation and upgrade for the Netweaver platform (used when upgrading BI etc).
Please note that you also need the Maintenance Optimizer configured in Solution Manager in order to download
(actually you approve them for download) support packages etc from the Service Marketplace.

ECC6.0 SP upgrade

Similar Messages

Maybe you are looking for