Ecc 6.0 SPDD umodauto.lst

Hi,
We are upgrading from 46c to ecc 6.0. Now we completed the Development upgrade and upgading QA.
We did SPDD during upgrade and we did not get umodauto.lst fine in ../bin directory.
Now I want to know the exact process to get umodauto.lst file and transport request.
We are upgrading QA and here we plan to do SPDD once again and we want to make umodauto.lst available for further upgrades.
pl. suggest up.
In SPDD we did changes and system prompted for transport request.
We did not release TR or tasks in TR.
now tell us how do we do this.

Hi
If you choose strategy downtime-minimized, the ABAP Dictionary objects (tables, data elements, domains, and so on) are adjusted during production operation. If you choose
strategy resource-minimized, they are adjusted during downtime before the ABAP Dictionary is activated. The adjusted objects are collected in a repair that is released to
a transport request. You cannot release this transport request; instead you must flag it for transport in transaction SPDD. Towards the end of the upgrade, SAPup exports the request to the transport directory /usr/sap/trans and registers it for transport in the umodauto.lst file.
Once it registers in umodauto.lst. For the later upgrade boxes -> In PREPARE phase ADJUSTPRP the following screen appears
For automatically maintaining your modification in your ystem during the upgrade transport request from earlier upgrades are searched in the umoauto.lst in directory /usr/sap/trans/bin..
The file could not be read
There are several reason why this may be correct
eg: 'this is your first upgrade' or 'your system is not modified'.
Did you expect a list of transports being found?
->Confirm a list of transports to be included in the upgrade
Select Yes & OK
view umodauto.lst , should list as below eg:
SPDD 700 SIDK100001
Click on Yes to include the transport
Click Yes to stop the ACT_700 phase and check the results of SPDD

Similar Messages

Umodauto.lst in EHPIabap in and not in trans in

Hi all
I finished EHP4 installation on my ERP-development system. I made SPAU and SPDD and marked both transport request as spau and spdd requests.
Usually the file umodauto.lst in \usr\sap\trans\bin got updated with the corresponding transport requests. But in this case not the umodauto.lst in \trans\bin got updated but the umodauto.lst in \usr\sap\EHPI\abap\bin. That's strange because I thought that I do not need the ehpi directory after the upgrade (and I could delete the entire content).
What do I have to do with the umodauto.lst? Do I have to move that from EHPI\abab\bin to \usr\sap\trans\bin?
Thanks in advance for your reply.
Regards
Marco

Hello Marco,
unless you used SAINT, there's no error here: you performed an EHPI install using the ehpi tool on the OS level, which uses the \usr\sap\EHPI\abap\bin to upgrade umodauto.lst file.
Directory \trans\bin is used for EHP1 using SAINT (less common).
But in any cases, if system did not find the TRs for SPDD/SPAU, all you need to do is to move the 'correct' umodauto.lst (the populated one) to the 'correct' \bin directory, then repeat the phase (or re-run SPAU or SPDD t-codes to have your objects adjusted). That's it
Best regards,
Tomas Black

4.0B to ECC 6.0; SPDD in PREPARE or UPGRADE phase?

Hi Gurus,
I am working on an upgrade from R/3 4.0 to ECC 6.0. I worked on pgrades before but am alien 4.0B. BTW, from a Developer perspective:
1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
Helpful Answers will be rewarded

Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM

SPAU SPDD Transport Strategy for following Upgrades

Hello All,
We are doing CUUC from 4.7 NUC to ECC 6 Ehp4 UC
After completing our Upgrade from 4.7 NUC to ECC 6 NUC in the original host, I stopped the Upgrade tool at the point when it asks for SPAU adjustements in Post Processing Step, did the Unicode Conversion in which we built the Target ECC 6 UC System in a separate host (host: ecctemp).
So,
1. The Upgrade Directory and ECC 6 NUC System resides on the first host.2. The Second host(ecctemp) contains only the ECC 6 UC System.
3. We started our SPAU activities in the ECC 6 UC System after CUUC process completed.
4. Now, with SPDD & SPAU activities getting completed. I want the 2 Transports to be used for rest of the Upgrades.
How do I go about this?
1. I cannot run 'SELECT FOR TRANSPORT' or run the commands as per 68678 in the ECC 6 NUC System as thats where I didnot do SPAU.
2. I cannot even run the commands as per 68678 in the host ecctemp, becuase there is no upgrade directory here.

Hi,
You can add SPDD transport on your non-unicode system in umodauto.lst file and take this file to your quality system (also data file and cofile). So, when you will start upgrade on your quality system then upgrade tool will first read this umodauto.lst file and it will prompt you on the screen to has this transport as SPDD transport. And upgrade tool will then import this SPDD request.
For SAPU, you can simply move data file and cofile from your final system to quality system. And once your quality system will be ready after upgrade and UC conversion then you can simple import this transport from STMS. This will solve your issue.
Thanks
Sunny

Problem between DEV and QAS in SPDD and SPAU

Hello,
We adjusted the SPDD in the ACT_UPG and he SPAU in the post processing and everything was right.
When I try to install the QAS I gave the installer both transport but tells me this:
1 ETQ004 USER DECISIONS ABOUT PROCESS OF ADJUSTEMENTS
4 ETQ430 START reading "umodstat.lst" in directory "/usr/sap/trans/EHPI/abap/bin"
3 ETQ433 END   reading "umodstat.lst" in directory "/usr/sap/trans/EHPI/abap/bin"
4 ETQ427 START deciding about "SPDD" in release "701"
4 ETQ500 INFO number of objects in repairs   : "92"
4 ETQ501 INFO number of objects in transports: "82"
4 ETQ430 START reading "umodauto.lst" in directory "/usr/sap/trans/EHPI/abap/bin"
4 ETQ431       "2" entries read
4 ETQ432       read: rc="2"
3 ETQ433 END   reading "umodauto.lst" in directory "/usr/sap/trans/EHPI/abap/bin"
3WETQ498       transport "XXXXXXX" found. It seems NOT(!) to be OK
that in SPDD
3 ETQ438 END   writing entry to "umodauto.imp" in directory "/usr/sap/trans/EHPI/abap/bin"
4 ETQ454       user wants to check the transport result in "SPDD"
2 ETQ504 INFO upgrade will halt for "SPDD" in release "701"
3 ETQ429 END   deciding about "SPDD" in release "701"
4 ETQ427 START deciding about "SPAU" in release "701"
4 ETQ500 INFO number of objects in repairs   : "593"
4 ETQ501 INFO number of objects in transports: "495"
4 ETQ430 START reading "umodauto.lst" in directory "/usr/sap/trans/EHPI/abap/bin"
4 ETQ431       "2" entries read
4 ETQ432       read: rc="2"
3 ETQ433 END   reading "umodauto.lst" in directory "/usr/sap/trans/EHPI/abap/bin"
3WETQ498       transport "XXXXXXXXXX" found. It seems NOT(!) to be OK
that is on SPAU
The system before the migration, were both recreated from a PRD backup so it should be the same.
Please help me with this

Hello Carlos,
this error is mostly related to the second run of an Upgrade (either to QA or PRD systems), when SPAU/SPDD already have a request assigned for them. Please check notes #68678 and #610311.
If this does not help, please list the content of phase PREP_INTEGRATION/ADJUSTPRP (as seen in the sapehpiconsole.log)
Best regards,
Tomas Black

How to handle delta SPDD & SPAU adjustments in the 2nd Upgrade QA & PRD

Dear all,
We have successfully upgraded our development box and we have made the SPDD changes into a single transport requests and also the SPAU requests in a different requests.
Our ABAP team has made the SPDD adjustments comparing the objects with production and QA.
Now when we upgrade our QA box we have included the SPDD & SPAU transports and now we found that we have about 8 extra objects that needs to be modified manually in SPDD phase? out of 79 objects 71 is adjusted my out SPDD transports and it has left out 8 more objects.
These 8 objects were never shown in SPDD phase of our development box.
Can you please suggest us, like how to handle these delta objects, so that we won't phase the same issue when we move to production. (offcourse we will do 2-3 dry runs before going to production)
I have read the below note, but it is for the older version (without shadow instance)
Note 124522 - Importing a modification adjustment in 2nd upgrade
Thanks &
Regards
Senthil

1.If you have choosen strategy resource-minimized, they are adjusted during downtime before the ABAP Dictionary is activated.
copy the cofiles and datafiles in the respective directories. List all the requests in umodauto.lst.
In PREPARE phase ADJUSTPRP the following screen appears
For automatically maintaining your modification in your ystem during the upgrade transport request from earlier upgrades are searched in the umoauto.lst in directory /usr/sap/trans/bin..
The file could not be read
There are several reason why this may be correct
eg: 'this is your first upgrade' or 'your system is not modified'.
Did you expect a list of transports being found?
->Confirm a list of transports to be included in the upgrade
Select Yes & OK
Click on Yes to include the transport
Click Yes to stop the ACT_700 phase and check the results of SPDD
2.You can add additional requests to umodauto.lst
3. Regarding why its how in QA.? Reasons could be
1modification could have been done only in QA
2)Are the DEV and QA are on the same kernel & SP level's

Handling Modification Adjustment in Subsequent System

Hello All,
I am upgrading my Ecc to EHP4 and want the SPDD and SPAU modification to be used in the subsequent System.
I have read the installation document and understood the following.
Pre-reqisite :The CTS should be configured and the trans should be shareble across the dev-qa-prd
FOR SPDD(in the shadow system)
1.) Create a Transport Request
2.) Flag it for transport in the SPDD t-code
3.) After all the corrections are saved in the TASK, release the task.Do not release the teansport request.
FOR SPAU (after the downtime
1.) Create a Transport Request
2.) Flag it for transport in the SPAU t-code
3.) After all the corrections are saved in the TASK, release the task.Do not release the transport request.
So both this request will be registered in the umodauto.lst file under the usr/sap/trans directory.
Regards
Anthony

Hello Sunny
Thank you for the rely.
I have a little confussion.
I just checked the bin directory of the EHPI installation directory for the umodauto.lst and i found this
/usr/sap/EHPI/EHPI/abap/bin
rasupt1:rpdadm 3> more umodauto.lst
SPAU 701 RPDK912052
SPDD 700 RPDK912049
And when i checked the global trans for the umodauto.lst i got the following
/usr/sap/trans/bin
rasupt1:rpdadm 6> more umodauto.lst
SPAU 701 RPDK912052
In the EHPI instalation directory i get both the SPDD and SPAU Transport request, where as in the global trans/bin there is only the entry of the SPAU .
I am confused as to
1.)what file the next installation will be checking
2.) And why the SPDD entry has not appeared in the global trans/bin
If you have some idea .. it will be helpfull
Regards
Anthony

When to apply SPAU changes in succeeding sap servers?

Hi,
We have finished applying patches in our development server and we have some SPAU trnasports generated. Now when we apply the patches in the Test server, when is the right time to import the SPAU transports?
should it be
(a) before the patch?
(b) when SPAU is prompted?
(c) after the patch queue is confirmed?
thanks,
kbas

Hi All,
the correct way to hadle modificaton adjustments is as follows.
1) You are applying SP's in your DEV system.
2) It would stop at SPDD. Now perfrom the SPDD and lock the changes in the SPDD transport request(TR).
3) In the same SPDD screen, click on the button "SELECT FOR TRANSPORT" . The button may change in systen with higher release. It would be "ASSIGN TRANSPORT".
4) Once this button is clicked, assign the transport and click the tick mark. It will ask you the transport is for SP import or upgrade. Click on SP import.
5) Now the intresting part is once this transport is assigned as SPDD here, a file called umodauto.lst will be crreated in the <DIR_TRANS>/tmp directry with an entry for SPDD transport request. Same should be donw wth SPAU tr also.
6) No finish off the SPDD in DEV
7) I n QAS when you will be defining the queue , then you will be prompted to include the adjustment modification request . Now you will have only the option to slect the TR which the SPAM tool would read from the umodauto.lst file. Includue the TR .
8) Your SPDD adjustments will be automatically handled in QAS.
Never import a TR at SPDD phase in a QAS system. This will damage the SPAM tool internally.
SPDD should be hadled or automatically adjusted when it is prompted. If skipped, then the customer modifications will be lost completley and SAP standard will take over. SPAU can be handled after the upgrdae or SP activity. SPAU will incluse repoositary objects .So we can juggle with the versions as version management is present . So nothing is lost.
If you want to know how to handle modifications during the upgrade , check the link
http://scn.sap.com/docs/DOC-44106
i will create one for SP import also shortly.
Cheers,
Varun.

ERROR -- Upgrade interrumped by modification adjustments

Hi Experts,
I´m upgrading 6.00 to EHP4 and it stops and gives the message " interrumped by modification adjustments"
I understand that I have to go to tx SPAU and made the modifications but I dont know how to do this and then how to check to continue.
Regards.

Hi Jorge,
You can do the SPAU after finishing the upgrade as well. You have to take help of your ABAP colleagues to do SPAU.
Also, please make sure that if it is your DEV system and you want to use this SPAU transport in your subsequent system i.e. QA and PRD then choose exit option on EHPI screen and do the SPAU and mark this transport to use in subsequent system. Don't release the transport, EHPI tool will release transport itself and add it in umodauto.lst list. so that in QA and PRD you don't have to SPAU again manually. After SPAU finished run EHPI tool again and select Adjustment completed. And continue.
Also, read text on EHPI screen of this phase.
Thanks
Sunny

Upgrade to ECC 6.0 from 4.7 - When to execute SPDD/SPAU

Hi Expert,
I'm doing technical upgrade from 4.7 to ECC 6.0 and just discover notes that related to activating Add-ons (Business Switch) for DIMP. It seems like some of the switch need to be turn on manually. The question is, should this switch be turned on before SPDD/SPAU or I can run SPDD/SPAU then turn on the switch? I'm raising this question because I notice some of the collective search help that contain customized elementary search help become resetted and the customized search help is not included in the standard search help anymore. Thanks in advance for the answer.
Rgrds,
Abraham

Hi Abraham,
As said by Abdul you can do the SPDD during the phase ACT_700, The SAPup tool stops at this phase and prompts you for the confirmation.
In this phase you have to login to the shadow instance and in the 000 client with DDIC user and create a user as the copy of the DDIC.
use this newly created user for doing the SPDD in the shadow instance.
SPAU can be done once the upgrade is completed with in 14 days with out a developer key after 14 days you need a developer key.
when you carry out further upgrades you can include these 2 requests SPDD and SPAU during the upgrade itself. In this situation if you have any other delta adjustments then you have to do that delta in the shadow instace otherwise you dont need to work again on the SPDD and SPAU for the rest of the systems.
Hope this info is useful.
Thanks,
Venkat.

SPAU / SPDD Transport During Upgrade from 4.6C to ECC 6.0

We are currently upgrading R/3 4.6C to ECC 6.0 SR2. During the DEV upgrade, we performed Dictionary Objects adjustments before ACT 7.00 and SPAU adjustments at the end of the upgrade. All the adjustments are collected in a transport.
I read in another thread that we will have to choose 'SELECT FOR TRANSPORT' button in SPAU and not release it. Then, continue with the upgrade. And in the same thread, it is also mentioned that DDIC object modifications should not be handled through transports.
Now, my question is, if I have collected the SPAU adjustments in a transport and continued with the upgrade without choosing the 'SELECT FOR TRANSPORT' button, can I do it after I complete the upgrade before I continue with QAS upgrade? Will the upgrade still automatically detect the transports and move them? And, my other question is, if DDIC modifications are not supposed to be dealt through transports, how else should they be worked upon?
Your response ASAP will be rewarded properly.
Thank you.

Nick, thank you for the reference. Even though I had gone through this note before, I couldn't apply this note because, this note was refering to "R3up" which, I guess, is no more used. "SAPup" is the program currently in use. Also the location mentioned in the note to execute "R3up" is "//usr/sap/put/exe" but, "SAPup" is located under "//usr/sap/put/bin/". So, I am not sure if there is any new notes refering to this. One other question I have with regards to this note is, one of the arguments for the command R3up is, "REL". For SPDD, the note suggests to use target release. And for SPAU, the note suggest to use the release mentioned in the DDIC activation phase.
In my case, I am upgrading from 4.6D (kernel) to 700 (kernel). The DDIC activation shows ACT_700. So, I am sure I would use "700" as value for "REL" for SPDD. But, am I supposed to use "46D" for SPAU? or should I use "700"?
Thank you.

RFC or BAPI to get ECC CST LST from SAP to third party

Hi Friends,
I want to find out RFC or BAPI to get ECC,CST and LST No. number from SAP system to third party software accourding to Ship to party.Please healp me.

Hi,
Thanks very much for your answer. In fact, table UVERS is empty both on SAP Wharehouse server and Netweaver, but you put me on the right way...
I finally found that table CVERS_REF was enough, but I don't have the version of the component like in the status window...
I doubt also I'm right using the RFC_READ_TABLE, but I don't know yet if a BAPI exists for what I'm looking for.
Regards
François MAESEELE

In ECC 6 upgrade, after completing SPDD and during SAP Downtime error

Table : WWMI and
Activiate the index 01, 02 and 03, receiving the warning message.
"ORA-00955: name is already used by an existing object     "
Details.
sql:
CREATE
INDEX "WWMI~003" ON "WWMI"
("MANDT",
"AKTNR")
PCTFREE 10
INITRANS 002
TABLESPACE PSAPBTABI
STORAGE (INITIAL 0000000016 K
NEXT 0000000080 K
MINEXTENTS 0000000001
MAXEXTENTS UNLIMITED
PCTINCREASE 0000
FREELISTS 001)
ORA-00955: name is already used by an existing object
DDL time(___1): ........29 milliseconds
sql:
DELETE FROM DDSTORAGE WHERE
DBSYSABBR = 'ORA' AND
TABNAME = 'WWMI' AND
INDEXNAME = '003'
DDL time(___2): .........0 milliseconds

Hi,
Could you please give me the phase in which you encounter the error and what doyou mean by after completing SPDD and After SAP Downtime please elobrate.
Regards,
Iqbal

SAP Ides ECC 6.0 Install: Import ABAP - Package SAPDODS Error - ORA-00903

Experts,
Good Morning!
I'm trying to install SAP IDES ECC 6.0 version on a Windows 2008 R2 Server with Oracle 11g DB (11.2).
System Info: 16GM RAM & 600GB Hdd. Prereqs passed.
I'm getting the following error during the Import ABAP phase (16 of 29) in the sapinst log:
"An error occurred while processing option Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. "
Here's the dump of import_monitor.java.log
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.012)
SAP Java Server VM (build 4.1.012 1.6-b03, Oct 21 2011 14:18:45 - 41_REL - optU - windows amd64 - 6 - bas2:161688 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 141, failed 0, total 143.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 141, failed 1, total 143.
Here's the dump of import_monitor.log:
INFO: 2014-07-05 13:42:53
Data codepage 4103 is determined using TOC file 'C:\Target\Export1\DATA\D010TAB.TOC' for package 'D010TAB'.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2014-07-05 13:42:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-05 13:43:21
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-07-05 13:43:21
1 error(s) during processing of packages.
INFO: 2014-07-05 13:43:21
Import Monitor is stopped.
Here's the log of SAPDODS...
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140705134253
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Aug 16 2011 02:26:36
patchinfo (patches.h): (0.098) DB6: correction for R3load PL 91 on HP-UX and SOLARIS (note 1609719)
process id 1488
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/SQLFiles.LST
(SQL) INFO: C:\Target\Export1\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file DODS.SQL
(SQL) INFO: DODS.SQL not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: found C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: Trying to open C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: C:\Target\Export1\DB/ORA/DODS.SQL opened
(DB) ERROR: DDL statement failed
(DROP TABLE "/BI0/APERS_BOD00")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 903 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-00903 occurred at SQL stmt (parse error offset=15)
(DB) ERROR: DDL statement failed
( CREATE TABLE [/BI0/APERS_BOD00] ( [TCTUSERNM] nvarchar(000012) NOT NULL , [TCTOBJVERS] nvarchar(000001) NOT NULL , [TCTSYSID] nvarchar(000010) NOT NULL , [TCTQUACT] nvarchar(000001) NOT NULL , [TCTOBJNM] nvarchar(000040) NOT NULL , [TCTTLOGO] nvarchar(000004) NOT NULL , [RECORDMODE] nvarchar(000001) NOT NULL , [TCTTIMSTMP] nvarchar(000014) NOT NULL ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 903)
error message returned by DbSl:
ORA-00903: invalid table name
(DB) INFO: disconnected from DB
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140705134254
FYI - A retry does not help. Also tried to search for the error on scn, google but haven't been able to find the right solution.
Can you help?
Regards,
Cobain.

Divyanshu - sorry to ask but can you explain why i need to update r3load and r3trans to resolve this error? Just want to understand why I'm doing a correction so I can learn from the same.
Also, can you clarify the file update process:
For R3load:
a) the r3load used by the command is dated 8/16/2011 (location:C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\...)
b) the r3load i have in my db folder is dated 10/23/2011 (location:C:\Final\Installer\BS7i2011_Installation_Master_\DATA_UNITS\BS2011_IM_WINDOWS_X86_64\ORA\UC\...)
Do i replace (a) with (b)?
For R3trans:
How do I update this file?
- Cobain.

Warning codes generated in UCCHECK   - Technical Upgrade - 4.0b to ECC 6.0

Hi SDN'ers ,
I am currently working on Technical Upgrade project from 4.0 b system to ECC 6.0 system . I am facing a
problem relating to the analysis of the warnings displayed whehn we run the UCCHECK for the client inventory by
checking the "Display lines that cannot be analyzed statically" option under the Selection-screen block
"Statements that cannot be analyzed statically" .Based on the warning codes generated during UCCHECK, they can
be classified into 12 different categories given below in the list ( Viz. ABB,MESSAGEG!C,MESSAGEG!D......MESSAGEG!P).The same are given below in the end
I want to know
- Which are the warning codes which need resolution so that the program does not encounter any runtime
errors or during Integration testing ?
- Do all the offset related errors (For example ;variable A = B+offset(length)
or variable A+offset(length) = B ) need resolution so that the program gives no runtime error.
- Also, do all statements where length is calculated using STRLEN also need changes ? I have seen offset length related warnings come under MESSAGEG!M warning code.
The objective of this is to make sure that the upgraded system ECC 6.0 in Australia ,when rolled out to
non-English speaking geographies in APAc such as Malaysia,Japan or China would only need translations and no ABAP Coding effort even when using languages such as Japanese which have double byte characters.
S.No.     Error Code     Message
1     ABB     Syntax Check Aborted
     ABB Total
2     MESSAGEG!C      check at runtime. at runtime.
           statement because of untyped or generic operands. It can only carry out this
          The system could not perform a static convertibility check on the current
     MESSAGEG!C Total
3     MESSAGEG!D      out this check at runtime. It can only carry out this check at runtime.
           to a table line because of untyped or generic operands. It can only carry out
          The system could not perform a static check on convertibility from a work area
     MESSAGEG!D Total
4     MESSAGEG!E      check at runtime. at runtime.
           defined by a "DATA" statement. .
           statement because of untyped or generic operands. It can only carry out this
          Field "ELEMENTN" is unknown. It is neither in one of the specified tables nor
          The system could not perform a static comparability check on the current
     MESSAGEG!E Total
5     MESSAGEG!F      operand "<FELD1>" for the current statement. .
     MESSAGEG!F Total
6     MESSAGEG!G      current statement on incompletely typed operand "<DATA>". .
     MESSAGEG!G Total
7     MESSAGEG!H      for the incompletely typed operand "<S>". . - - - - - - - - -
          The system cannot perform a static check on a character-type field data type
     MESSAGEG!H Total
8     MESSAGEG!I      incompletely-typed operand "<A>" in the current statement. .
          The system cannot perform a static check on a character-type data type for the
     MESSAGEG!I Total
9     MESSAGEG!J      "<%_1_SYSINI>" in the current statement to check whether the operand can be
          The system cannot perform a static check on incompletely-typed operand "VALUE"
     MESSAGEG!J Total
Early response wil be highly appreciated.

Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM

Ecc 6.0 SPDD umodauto.lst

Similar Messages

Maybe you are looking for