TDMS ECC Error in System Analysis Phase
Hi SAP Techies,
During TDMS in System Analysis Phase
Package : ERP Initial Package for Time based & Com
Phase : System Analysis
Activity ID : Analyze and Specify 'From-Date'
When I am clicking on Execute Its giving me error "Runtime error SYNTAX_ERROR has occurred".
After seeing the Execution log its telling "Problems with RFC execution " Which RFC it is talking about.
Regards
Punit Maini
Hi Puneet-
There is a OSS note out there on the marketplace that will resolve this.
I cannot find at the moment, but let me know if you cannot find it, I will update it here. Search with keywords like TDMS SYNTAX_error, From_Date
Harmeet
Similar Messages
-
TDMS RFC Error in system analysis phase
HI,
We are facing RFC Error in system analsysis phase. While starting Analyze and specify 'From Date'Hi,
Check if the RFC connections are working fine from central system to all the other systems.
Apart from transaction SM59, You can also check the RFC destinations using activity "Define RFC Settings" (the first activity in the process tree of your package). The RFCs should be correctly defined and synchronized, all the lights should be green.
Additionally, check that the users are assigned the role SAP_TDMS_USER.
Regards,
Rupam -
TDMS - System Analysis Phase completed with errors
Hi All,
We are running TDMS copy, currently running at System Analysis phase, however we encountered status message "completed with error" within sub-step "Generation of Run-Time Objects for Data Transfer". When we checked the tasks, we found below error messages...
Error while generating runtime objects for ZJ_3RFREP_VALFMT_01W
Syntax error in function module /1CADMC/OLC_950000000614930
Error message: Type "DECFLOAT16" is unknown
We tried re-executing the step several times but no success.
Can anybody suggest how to fix the issue. Thanks.
Regards,
PhilipHi experts,
We opened an OSS incident regarding this issue, and SAP responded to exclude the migration object J_3RFREP_VALFMT from the current transfer using the troubleshooter.
However, while we execute the troubleshooter, message prompt "Activity 'Troubleshooting for Migration Objects' execution 0003 in package 9002D, phase 'System Analysis' has been aborted ." appears.
In the Phase Overview of the System Analysis, step "Troubleshooting for Migration Objects" is added, which has an aborted status. Checking the logs of that steps we found below.
Skip Migration Objects from Current Transfer
I EQ J_3RFREP_VALFMT
Destination to the central system is not created yet
We checked all the RFC connections and all seems working fine.
Can anyone share how to fix this or what to check further.
Regards,
Philip -
Read System Analysis Data Error - Sol 10 u5 x86
This morning, smpatch analyze and update via updatemanager will not work, giving this error:
"Read System Analysis Data Error
There is an error in reading system analysis data. Click on "Check for Updates" to restart a system analysis. If the problem persists, report the issue to your sysadmin or Sun."
Is this a temporary problem with the Sun update system computers, or is this something I should worry about?
Updatemanager worked fine yesterday.Never mind. The problem went away.
-
ERROR in ADD-ON conflict phase while upgrading ECC 6.0 system
Hi all,
I am having ECC 6.0 system and am upgrading its SAP-APPL component to 603 patch level 03. I was having SAP-APPL 603 but at patch level 0, i checked for all dependencies and defined the queue in SPAM and it showed all green (OK) for SAP-APPL and so i started but i faced error in add-on coflict phase. It said CRT needed for ADD-ON FICAX release 603. I searched alot but i cant find it on market place. This conflict occured for SAP-APPL 603 patch level 01 it said either include CRT as mentioned above or remove SAP-APPL 60301. Please help me out.The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60301.
The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60302.
The conflict check detected conflicts between the Add-On FI-CAX release 603 and the OCS Package SAPKH60303.
Check the support packs of components FI-CAX on Service Market place, I think FI-CAX is dependant on SAPKH603301 and others so you can check the import condidtions of FI-CAX on service marketplace and update FI-CAX first then only you would be able to update patch of SAPKH60301
Regards
Subhash -
SAP R/3 System analysis before upgrade 4.6C -- SAP ECC 6.0
Hello!
Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
The following functions should be included in this program:
- detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
- comparison against a SAP ERP 6.0 reference system
- extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
- syntax analysis of program code with respect of adjustement need
- quality control of own development
- control of amount of transports within different company areas
- control of user information, such a user type, logon date, etc.
- basic control, whether a sufficient authorization concept is available
- Identification of objects that should be considered for the archiving in oder to decrease the db-size
My question are:
- which tasks can be convered with SAP standard transactions what are the names of the transactions?
- which effort do I investigate for these tasks?
Thank you very much!
regardsDear Thom,
To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.
Need to consider the following things:
For Reports its custom developed program so unless there is any kind of change in requirement from the client regarding the layout nothing needs to be changed I think it will work fine in ECC 6.0 to except few things may needs to be changed..so you need to discuss whether they want the reorts as it is right now or want to change the layout (adding some new info/fields etc) of any report so u need to modify the program for those and estimate accordingly for a medium complexitys Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing) so to modify it will be less than that (depending upon the scope of changes)
Now say for Batch Inputs(interface/Data Migration) using BDC you need to see how many BDCs are there again if the field lengths and layouts are not changing then no need to change anything (except the main thing ..you need to change the obsolete function modules there are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0 there are some new with enhanced functionality so you need to modify the BDCs and many cases it happens that the whole transaction screen changes for process in that case better to develop new BDCs so you have to consider those parameter look into and estimate accordingly modifying a BDC should not take more than 1 PD
Now say for Forms there was no Smart form in 4.6C form printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart form in that case its complete new dev so estimate accordingly a medium complexitys form should take 8 PD (FRSTDSCoding+Unit Testing) you can take it as 10 PD too even if client wants to keep it is as it was in older version you have to redevelop the layout in ECC 6.0 again as form printer is even client dependent maximum you can copy the program associated with that form in the new version too and your effort will be saved again you have to consider if clients wants to change the layout too
Now for enhancement so in that case u need to see individual cases for a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)
One more important thing is that the Unicode Compatibility this needs to be done .needs to change the code (variable name) accordingly .also Version management tool is used for the standard programs
Also pls find the following forums:
Re: Data Migration from 4.6C to ECC 6.0
List of transations supported in SAP 4.6c and not in ECC6.0
Re: Upgradation from 4.6C to ECC 6.0
Re: what's the advantage to upgrade 4.6c to ECC5.0...
RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
Upgrade batch inputs from 4.6C to mySAP ERP 2005
/thread/317225 [original link is broken]
Upgrade from SAP R/3 to ECC 6.0
Hope it will help you.
Thanks,
Atin
<b><b>Reward points if it helps.</b></b> -
Client Copy Error on ECC 6.0 System
Hello,
While doing client copy on ECC 6.0 system for Exp 100 to 110... We have check the log in SCC3 status is " Completed with Dictionary Errors".
Im getting below error...
Target Client
110
Source Client (incl. Auth.)
100
Source Client User Master
100
Copy Type
Local Copy
Profile
SAP_ALL
Status
Completed w. Dictionary Errors
User
SAP*
Start on
02.05.2008 / 12:43:06
Last Entry on
02.05.2008 / 15:15:24
Statistics for this Run
- No. of Tables
52592 of 54109
- Deleted Lines
8938299
- Copied Lines
8935238
Warnings and Errors
Table Name
Component
Package
A001
SD-MD-CM
DDIC Error (See SE14)
A004
SD-MD-CM
DDIC Error (See SE14)
A005
SD-MD-CM
DDIC Error (See SE14)
A006
SD-MD-CM
DDIC Error (See SE14)
A007
SD-MD-CM
DDIC Error (See SE14)
A009
SD-MD-CM
DDIC Error (See SE14)
A010
SD-MD-CM
DDIC Error (See SE14)
A012
SD-MD-CM
DDIC Error (See SE14)
A015
SD-MD-CM
DDIC Error (See SE14)
A016
SD-MD-CM
DDIC Error (See SE14)
A017
SD-MD-CM
DDIC Error (See SE14)
A018
SD-MD-CM
DDIC Error (See SE14)
A019
SD-MD-CM
DDIC Error (See SE14)
A021
SD-MD-CM
DDIC Error (See SE14)
A022
SD-MD-CM
DDIC Error (See SE14)
A023
SD-MD-CM
DDIC Error (See SE14)
A024
SD-MD-CM
DDIC Error (See SE14)
A025
SD-MD-CM
DDIC Error (See SE14)
A026
SD-MD-CM
DDIC Error (See SE14)
A028
SD-MD-CM
DDIC Error (See SE14)
A030
SD-MD-CM
DDIC Error (See SE14)
A032
SD-MD-CM
DDIC Error (See SE14)
A044
SD-MD-CM
DDIC Error (See SE14)
A045
SD-MD-CM
DDIC Error (See SE14)
A046
SD-MD-CM
DDIC Error (See SE14)
A047
SD-MD-CM
DDIC Error (See SE14)
A049
SD-MD-CM
DDIC Error (See SE14)
A051
SD-MD-CM
DDIC Error (See SE14)
A052
SD-MD-CM
DDIC Error (See SE14)
A053
SD-MD-CM
DDIC Error (See SE14)
A054
SD-MD-CM
DDIC Error (See SE14)
A058
SD-MD-CM
DDIC Error (See SE14)
A059
SD-MD-CM
DDIC Error (See SE14)
A060
SD-MD-CM
DDIC Error (See SE14)
A061
SD-MD-CM
DDIC Error (See SE14)
A062
SD-MD-CM
DDIC Error (See SE14)
A063
SD-MD-CM
DDIC Error (See SE14)
A400
IS-H-PA
DDIC Error (See SE14)
A401
IS-H-BD
DDIC Error (See SE14)
AT100
FIN-FSCM-TRM-TM
DDIC Error (See SE14)
AT14
FIN-FSCM-TRM-TM
DDIC Error (See SE14)
ATAB
BC-DWB-DIC-AC
DDIC Error (See SE14)
BC325V00
BC-CTS
DDIC Error (See SE14)
BC325V10
BC-CTS
DDIC Error (See SE14)
BC325X00
BC-CTS
DDIC Error (See SE14)
BC325X01
BC-CTS
DDIC Error (See SE14)
BC325X02
BC-CTS
DDIC Error (See SE14)
BC325X03
BC-CTS
DDIC Error (See SE14)
BC325X04
BC-CTS
DDIC Error (See SE14)
BC325X05
BC-CTS
DDIC Error (See SE14)
BC325X06
BC-CTS
DDIC Error (See SE14)
BC325X07
BC-CTS
DDIC Error (See SE14)
BC325X08
BC-CTS
DDIC Error (See SE14)
BC325X09
BC-CTS
DDIC Error (See SE14)
BC325X10
BC-CTS
DDIC Error (See SE14)
BC325X11
BC-CTS
DDIC Error (See SE14)
BC325X12
BC-CTS
DDIC Error (See SE14)
BC325X13
BC-CTS
DDIC Error (See SE14)
BC325X14
BC-CTS
DDIC Error (See SE14)
BC325X15
BC-CTS
DDIC Error (See SE14)
BC325X16
BC-CTS
DDIC Error (See SE14)
BC325X17
BC-CTS
DDIC Error (See SE14)
BC325X18
BC-CTS
DDIC Error (See SE14)
BC325X19
BC-CTS
DDIC Error (See SE14)
BC325X20
BC-CTS
DDIC Error (See SE14)
BC325X21
BC-CTS
DDIC Error (See SE14)
BC325X22
BC-CTS
DDIC Error (See SE14)
BC325X23
BC-CTS
DDIC Error (See SE14)
BC325X24
BC-CTS
DDIC Error (See SE14)
BC325X25
BC-CTS
DDIC Error (See SE14)
BC325X26
BC-CTS
DDIC Error (See SE14)
BC325X27
BC-CTS
DDIC Error (See SE14)
BC325X28
BC-CTS
DDIC Error (See SE14)
BC325X29
BC-CTS
DDIC Error (See SE14)
BC325X30
BC-CTS
DDIC Error (See SE14)
BC325X31
BC-CTS
DDIC Error (See SE14)
BC325X32
BC-CTS
DDIC Error (See SE14)
BC325X33
BC-CTS
DDIC Error (See SE14)
BC325X34
BC-CTS
DDIC Error (See SE14)
BC325X35
BC-CTS
DDIC Error (See SE14)
BC325X36
BC-CTS
DDIC Error (See SE14)
BC325X37
BC-CTS
DDIC Error (See SE14)
BC325X38
BC-CTS
DDIC Error (See SE14)
BC325X39
BC-CTS
DDIC Error (See SE14)
BC325X40
BC-CTS
DDIC Error (See SE14)
DICS_T150
IS-AD-SSP
DDIC Error (See SE14)
DICS_T150F
IS-AD-SSP
DDIC Error (See SE14)
DICS_T156B
IS-AD-SSP
DDIC Error (See SE14)
DICS_T157B
IS-AD-SSP
DDIC Error (See SE14)
DICS_T157H
IS-AD-SSP
DDIC Error (See SE14)
FB03
FI-FM
DDIC Error (See SE14)
FKKCLEDRI
FI-CA
DDIC Error (See SE14)
FKKCLEGP
FI-CA
DDIC Error (See SE14)
FKKCLEGPI
FI-CA
DDIC Error (See SE14)
FKKCLEVK
FI-CA
DDIC Error (See SE14)
FKKCLEVKI
FI-CA
DDIC Error (See SE14)
FKKCLEZW2I
FI-CA
DDIC Error (See SE14)
FKKCLEZWFI
FI-CA
DDIC Error (See SE14)
FKKNRRANGE
FI-CA-INV
DDIC Error (See SE14)
FKKNUMKR
FI-CA
DDIC Error (See SE14)
FKKVKOPA
FI-CA
DDIC Error (See SE14)
FMVALID
FI-FM
DDIC Error (See SE14)
GB91T
FI-SL-SL
DDIC Error (See SE14)
GLP1
FI-SL-SL
DDIC Error (See SE14)
GLP2
FI-SL-SL
DDIC Error (See SE14)
GLPPC
EC-PCA
DDIC Error (See SE14)
GLS1
FI-SL-SL
DDIC Error (See SE14)
GLS2
FI-LC-LC
DDIC Error (See SE14)
GLSP
FI-SL-SL
DDIC Error (See SE14)
GLSPC
EC-PCA
DDIC Error (See SE14)
GLT1
FI-SL-SL
DDIC Error (See SE14)
GLT2
FI-LC-LC
DDIC Error (See SE14)
GLTP
FI-SL-SL
DDIC Error (See SE14)
ICLUSCNTXT
FS-CM
DDIC Error (See SE14)
INDEXDT
TR
DDIC Error (See SE14)
ISUERDK
IS-U-IN
DDIC Error (See SE14)
ISUNUMKR
IS-U-IN
DDIC Error (See SE14)
JSDTPAER
IS-M
DDIC Error (See SE14)
JVS1
CA-JVA
DDIC Error (See SE14)
KAPOL
SD-MD-CM
DDIC Error (See SE14)
MCLIK
LO-LIS-LIB
DDIC Error (See SE14)
MCLIL
LO-LIS-LIB
DDIC Error (See SE14)
MCLIM
LO-LIS-LIB
DDIC Error (See SE14)
MWCURM
MM-IM
DDIC Error (See SE14)
PYONUMKR
FI-AP-AP-PT
DDIC Error (See SE14)
STXXFILTER
BC-DB-DBI
DDIC Error (See SE14)
T000C
FI-SL-SL
DDIC Error (See SE14)
T001E
FI
DDIC Error (See SE14)
T001F
FI
DDIC Error (See SE14)
T001R
FI
DDIC Error (See SE14)
T001S
FI
DDIC Error (See SE14)
T001T
FI-AR-AR-DU
DDIC Error (See SE14)
T001X
FI
DDIC Error (See SE14)
T001Z
FI
DDIC Error (See SE14)
T003A
FI
DDIC Error (See SE14)
T003M
MM-IM
DDIC Error (See SE14)
T003T
FI
DDIC Error (See SE14)
T004F
FI-AP-AP-PT
DDIC Error (See SE14)
T004G
FI
DDIC Error (See SE14)
T004R
FI-GL-GL
DDIC Error (See SE14)
T004S
FI-GL-GL
DDIC Error (See SE14)
T004T
FI
DDIC Error (See SE14)
T004V
FI
DDIC Error (See SE14)
T004W
FI
DDIC Error (See SE14)
T005B
BC-SRV-ADR
DDIC Error (See SE14)
T005Q
FI
DDIC Error (See SE14)
T005R
FI
DDIC Error (See SE14)
T005X
BC-ABA-LA
DDIC Error (See SE14)
T007B
CA-BK
DDIC Error (See SE14)
T007G
FI-GL-IS
DDIC Error (See SE14)
T007H
FI-GL-IS
DDIC Error (See SE14)
T007S
FI
DDIC Error (See SE14)
T008
FI
DDIC Error (See SE14)
T008T
FI
DDIC Error (See SE14)
T009
BC-SRV-BSF
DDIC Error (See SE14)
T009B
BC-SRV-BSF
DDIC Error (See SE14)
T009C
BC-SRV-BSF
DDIC Error (See SE14)
T009T
BC-SRV-BSF
DDIC Error (See SE14)
T009Y
BC-SRV-BSF
DDIC Error (See SE14)
T010O
FI
DDIC Error (See SE14)
T010P
FI
DDIC Error (See SE14)
T011P
FI-GL-GL
DDIC Error (See SE14)
T011Q
FI-GL-GL
DDIC Error (See SE14)
T011Z
FI-GL-GL
DDIC Error (See SE14)
T012E
FI-BL-MD
DDIC Error (See SE14)
T014N
FI-AR-AR
DDIC Error (See SE14)
T015L
FI-BL-PT
DDIC Error (See SE14)
T015M
CA-BK
DDIC Error (See SE14)
T015W
FI-BL-PT
DDIC Error (See SE14)
T015Z
CA-BK
DDIC Error (See SE14)
T016
FI
DDIC Error (See SE14)
T016T
FI
DDIC Error (See SE14)
T017
PSM-FM-MD
DDIC Error (See SE14)
T018C
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T018D
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T018P
CA-BK
DDIC Error (See SE14)
T021
FI
DDIC Error (See SE14)
T021A
FI
DDIC Error (See SE14)
T021B
FI
DDIC Error (See SE14)
T021C
FI
DDIC Error (See SE14)
T021N
FI
DDIC Error (See SE14)
T021R
FI
DDIC Error (See SE14)
T021T
FI
DDIC Error (See SE14)
T021V
FI
DDIC Error (See SE14)
T021Z
FI
DDIC Error (See SE14)
T027C
MM-PUR
DDIC Error (See SE14)
T027D
MM-PUR
DDIC Error (See SE14)
T028A
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T028B
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T028D
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T028E
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T030
FI
DDIC Error (See SE14)
T030B
FI
DDIC Error (See SE14)
T030C
FI-SL-SL
DDIC Error (See SE14)
T030D
FI
DDIC Error (See SE14)
T030E
FI
DDIC Error (See SE14)
T030F
FI
DDIC Error (See SE14)
T030G
FI
DDIC Error (See SE14)
T030H
FI
DDIC Error (See SE14)
T030HB
FI-GL-IS
DDIC Error (See SE14)
T030I
FI
DDIC Error (See SE14)
T030K
FI
DDIC Error (See SE14)
T030Q
FI
DDIC Error (See SE14)
T030R
FI
DDIC Error (See SE14)
T030S
FI
DDIC Error (See SE14)
T030V
FI
DDIC Error (See SE14)
T031
FI
DDIC Error (See SE14)
T031S
FI
DDIC Error (See SE14)
T031T
FI
DDIC Error (See SE14)
T033E
FI
DDIC Error (See SE14)
T033F
FI
DDIC Error (See SE14)
T033G
FI
DDIC Error (See SE14)
T033I
FI
DDIC Error (See SE14)
T033J
FI
DDIC Error (See SE14)
T033U
FI
DDIC Error (See SE14)
T035V
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T036Q
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T036S
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T037
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T037A
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T037R
TR
DDIC Error (See SE14)
T037S
TR
DDIC Error (See SE14)
T037T
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T038V
FIN-FSCM-CLM-CM-CM
DDIC Error (See SE14)
T040
FI-AR-AR-DU
DDIC Error (See SE14)
T040A
FI-AR-AR-DU
DDIC Error (See SE14)
T040S
FI-AR-AR-DU
DDIC Error (See SE14)
T040T
FI-AR-AR-DU
DDIC Error (See SE14)
T041A
FI
DDIC Error (See SE14)
T041T
FI
DDIC Error (See SE14)
T042
FI-AP-AP-PT
DDIC Error (See SE14)
T042A
FI-AP-AP-PT
DDIC Error (See SE14)
T042D
FI-AP-AP-PT
DDIC Error (See SE14)
T042F
FI-BL-PT
DDIC Error (See SE14)
T042G
FI-AP-AP-PT
DDIC Error (See SE14)
T042H
FI-BL-PT
DDIC Error (See SE14)
T042I
FI-AP-AP-PT
DDIC Error (See SE14)
T042J
FI-AP-AP-PT
DDIC Error (See SE14)
T042K
FI-AP-AP-PT
DDIC Error (See SE14)
T042L
FI-AP-AP-PT
DDIC Error (See SE14)
T042M
FI-AP-AP-PT
DDIC Error (See SE14)
T042N
FI-AP-AP-PT
DDIC Error (See SE14)
T042P
FI-AP-AP-PT
DDIC Error (See SE14)
T042S
FI-AP-AP-PT
DDIC Error (See SE14)
T042V
FI-AP-AP-PT
DDIC Error (See SE14)
T043
FI
DDIC Error (See SE14)
T043G
FI
DDIC Error (See SE14)
T043K
FI
DDIC Error (See SE14)
T043S
FI
DDIC Error (See SE14)
T043T
FI
DDIC Error (See SE14)
T044A
FI
DDIC Error (See SE14)
T044B
FI
DDIC Error (See SE14)
T044E
FI-GL-IS
DDIC Error (See SE14)
T044Z
FI
DDIC Error (See SE14)
T045B
FI-AR-AR
DDIC Error (See SE14)
T045D
FI-AR-AR
DDIC Error (See SE14)
T045E
FI
DDIC Error (See SE14)
T045G
FI-AR-AR
DDIC Error (See SE14)
T045L
FI-AR-AR
DDIC Error (See SE14)
T046
FI
DDIC Error (See SE14)
T046T
FI
DDIC Error (See SE14)
T047
FI
DDIC Error (See SE14)
T047A
FI
DDIC Error (See SE14)
T047B
FI-AR-AR-DU
DDIC Error (See SE14)
T047C
FI-AR-AR-DU
DDIC Error (See SE14)
T047D
FI-AR-AR-DU
DDIC Error (See SE14)
T047E
FI-AR-AR-DU
DDIC Error (See SE14)
T047F
FI-AR-AR-DU
DDIC Error (See SE14)
T047H
FI-AR-AR-DU
DDIC Error (See SE14)
T047M
FI-AR-AR-DU
DDIC Error (See SE14)
T047N
FI-AR-AR-DU
DDIC Error (See SE14)
T047R
FI-AR-AR-DU
DDIC Error (See SE14)
T047S
FI-AR-AR-DU
DDIC Error (See SE14)
T047T
FI-AR-AR-DU
DDIC Error (See SE14)
T048B
FI
DDIC Error (See SE14)
T048I
FI
DDIC Error (See SE14)
T048K
FI
DDIC Error (See SE14)
T048L
FI
DDIC Error (See SE14)
T049C
FI-GL-IS
DDIC Error (See SE14)
T049E
FI-GL-IS
DDIC Error (See SE14)
T049F
FI-GL-IS
DDIC Error (See SE14)
T049L
FI
DDIC Error (See SE14)
T050T
FI
DDIC Error (See SE14)
T052A
FI
DDIC Error (See SE14)
T052R
FI
DDIC Error (See SE14)
T052S
FI
DDIC Error (See SE14)
T052T
FI
DDIC Error (See SE14)
T053
FI
DDIC Error (See SE14)
T053E
FI
DDIC Error (See SE14)
T053V
FI
DDIC Error (See SE14)
T053W
FI
DDIC Error (See SE14)
T054
FI
DDIC Error (See SE14)
T054A
FI
DDIC Error (See SE14)
T054T
FI
DDIC Error (See SE14)
T055G
CA-BK
DDIC Error (See SE14)
T055T
CA-BK
DDIC Error (See SE14)
T056
FI-AR-AR
DDIC Error (See SE14)
T056A
FI-AR-AR
DDIC Error (See SE14)
T056B
FI-AR-AR
DDIC Error (See SE14)
T056D
FI-AR-AR
DDIC Error (See SE14)
T056F
FI-AR-AR
DDIC Error (See SE14)
T056L
FI-AR-AR
DDIC Error (See SE14)
T056S
FI-AR-AR-IN
DDIC Error (See SE14)
T056T
FI-AR-AR
DDIC Error (See SE14)
T056U
FI-AR-AR
DDIC Error (See SE14)
T056X
FI-AR-AR
DDIC Error (See SE14)
T056Y
FI-AR-AR-IN
DDIC Error (See SE14)
T057
FI
DDIC Error (See SE14)
T057T
FI
DDIC Error (See SE14)
T059A
FI
DDIC Error (See SE14)
T059B
FI
DDIC Error (See SE14)
T059F
FI
DDIC Error (See SE14)
T059L
FI-AP-AP
DDIC Error (See SE14)
T059M
FI
DDIC Error (See SE14)
T059T
FI
DDIC Error (See SE14)
T060
FI-AR-AR
DDIC Error (See SE14)
T060A
FI-AR-AR
DDIC Error (See SE14)
T060B
FI-AR-AR
DDIC Error (See SE14)
T060O
FI-AR-AR
DDIC Error (See SE14)
T060S
FI-AR-AR
DDIC Error (See SE14)
T060T
FI-AR-AR
DDIC Error (See SE14)
T060U
FI-AR-AR
DDIC Error (See SE14)
T064S
MM-IM
DDIC Error (See SE14)
T068A
TR
DDIC Error (See SE14)
T068B
TR
DDIC Error (See SE14)
T069
MM-PUR
DDIC Error (See SE14)
T069Q
MM-PUR
DDIC Error (See SE14)
T069T
MM-PUR
DDIC Error (See SE14)
T070
FI
DDIC Error (See SE14)
T071
FI
DDIC Error (See SE14)
T074
FI
DDIC Error (See SE14)
T074A
FI
DDIC Error (See SE14)
T074T
FI
DDIC Error (See SE14)
T077S
FI
DDIC Error (See SE14)
T077T
FI
DDIC Error (See SE14)
T077X
FI
DDIC Error (See SE14)
T077Y
FI
DDIC Error (See SE14)
T077Z
FI
DDIC Error (See SE14)
T078S
FI
DDIC Error (See SE14)
T078W
LO-MD-PL
DDIC Error (See SE14)
T082A
FI-AA-AA
DDIC Error (See SE14)
T082E
FI-AA-AA
DDIC Error (See SE14)
T082S
FI-AA-AA
DDIC Error (See SE14)
T083L
FI-AA-AA
DDIC Error (See SE14)
T083S
FI-AA-AA
DDIC Error (See SE14)
T083T
FI-AA-AA
DDIC Error (See SE14)
T084A
FI-AA-AA
DDIC Error (See SE14)
T086A
FI-AA-IS
DDIC Error (See SE14)
T086T
FI-AA-AA
DDIC Error (See SE14)
T087I
FI-AA-AA
DDIC Error (See SE14)
T087J
FI-AA-AA
DDIC Error (See SE14)
T088
FI-AA-IS
DDIC Error (See SE14)
T089T
FI-AA-AA
DDIC Error (See SE14)
T090I
FI-AA-AA
DDIC Error (See SE14)
T090X
FI-AA-IS
DDIC Error (See SE14)
T090Y
FI-AA-AA
DDIC Error (See SE14)
T092
FI-AA-AA
DDIC Error (See SE14)
T092T
FI-AA-AA
DDIC Error (See SE14)
T093D
FI-AA-AA
DDIC Error (See SE14)
T093F
FI-AA-AA
DDIC Error (See SE14)
T093N
FI-AA-AA
DDIC Error (See SE14)
T093S
FI-AA-AA
DDIC Error (See SE14)
T093U
FI-AA-AA
DDIC Error (See SE14)
T093Y
FI-AA-AA
DDIC Error (See SE14)
T094
FI-AA-AA
DDIC Error (See SE14)
T094C
FI-AA-AA
DDIC Error (See SE14)
T097
FI-AA-AA
DDIC Error (See SE14)
T097T
FI-AA-AA
DDIC Error (See SE14)
T098
FI-AA-AA
DDIC Error (See SE14)
T098T
FI-AA-AA
DDIC Error (See SE14)
T099B
FI-AA-AA
DDIC Error (See SE14)
T099V
FI-AA-AA
DDIC Error (See SE14)
T100C
CA-BK
DDIC Error (See SE14)
T130C
LO-MD-MM
DDIC Error (See SE14)
T130D
LO-MD-MM
DDIC Error (See SE14)
T130G
LO-MD-MM
DDIC Error (See SE14)
T130M
LO-MD-MM
DDIC Error (See SE14)
T130O
LO-MD-MM
DDIC Error (See SE14)
T130P
LO-MD-MM
DDIC Error (See SE14)
T130S
LO-MD-MM
DDIC Error (See SE14)
T131A
LO-MD-MM
DDIC Error (See SE14)
T131T
LO-MD-MM
DDIC Error (See SE14)
T131V
LO-MD-MM
DDIC Error (See SE14)
T131X
LO-MD-MM
DDIC Error (See SE14)
T134W
LO-MD-MM
DDIC Error (See SE14)
T135A
LO-MD-MM
DDIC Error (See SE14)
T136
LO-MD-MM
DDIC Error (See SE14)
T136V
LO-MD-MM
DDIC Error (See SE14)
T138B
LO-MD-MM
DDIC Error (See SE14)
T138M
LO-MD-MM
DDIC Error (See SE14)
T139A
LO-MD-MM
DDIC Error (See SE14)
T139B
LO-MD-MM
DDIC Error (See SE14)
T147
MM-IS-VE
DDIC Error (See SE14)
T147A
MM-IS-VE
DDIC Error (See SE14)
T147C
MM-IS-VE
DDIC Error (See SE14)
T147E
MM-IS-VE
DDIC Error (See SE14)
T147H
MM-IS-VE
DDIC Error (See SE14)
T147K
MM-IS-VE
DDIC Error (See SE14)
T147L
MM-IS-VE
DDIC Error (See SE14)
T147M
MM-IS-VE
DDIC Error (See SE14)
T147N
MM-IS-VE
DDIC Error (See SE14)
T147O
MM-IS-VE
DDIC Error (See SE14)
T148A
LO-MD-MM
DDIC Error (See SE14)
T148B
LO-MD-MM
DDIC Error (See SE14)
T148G
LO-MD-MM
DDIC Error (See SE14)
T148M
LO-MD-MM
DDIC Error (See SE14)
T150
MM-IM
DDIC Error (See SE14)
T150F
MM-IM
DDIC Error (See SE14)
T156B
MM-IM
DDIC Error (See SE14)
T156H
MM-IM
DDIC Error (See SE14)
T156K
MM-IM
DDIC Error (See SE14)
T156N
MM-IM
DDIC Error (See SE14)
T157B
MM-IM
DDIC Error (See SE14)
T157D
MM-IM
DDIC Error (See SE14)
T157E
MM-IM
DDIC Error (See SE14)
T157F
MM-IM
DDIC Error (See SE14)
T157H
MM-IM
DDIC Error (See SE14)
T157N
MM-IM
DDIC Error (See SE14)
T157O
MM-IM
DDIC Error (See SE14)
T157P
MM-IM
DDIC Error (See SE14)
T157Q
MM-IM
DDIC Error (See SE14)
T157R
MM-IM
DDIC Error (See SE14)
T157T
MM-IM
DDIC Error (See SE14)
T158
MM-IM
DDIC Error (See SE14)
T158B
MM-IM
DDIC Error (See SE14)
T158I
MM-IM
DDIC Error (See SE14)
T158N
MM-IM
DDIC Error (See SE14)
T159B
MM-IM
DDIC Error (See SE14)
T159E
MM-IM
DDIC Error (See SE14)
T159G
MM-IM
DDIC Error (See SE14)
T159H
MM-IM
DDIC Error (See SE14)
T159M
MM-IM
DDIC Error (See SE14)
T159N
MM-IM
DDIC Error (See SE14)
T159O
MM-IM
DDIC Error (See SE14)
T159P
MM-IM
DDIC Error (See SE14)
T159Q
MM-IM
DDIC Error (See SE14)
T159R
MM-IM
DDIC Error (See SE14)
T159S
MM-IM
DDIC Error (See SE14)
T159T
MM-IM
DDIC Error (See SE14)
T160
MM-PUR
DDIC Error (See SE14)
T160B
MM-PUR
DDIC Error (See SE14)
T160C
MM-PUR
DDIC Error (See SE14)
T160D
MM-PUR
DDIC Error (See SE14)
T160E
MM-PUR
DDIC Error (See SE14)
T160I
MM-PUR
DDIC Error (See SE14)
T160J
MM-PUR
DDIC Error (See SE14)
T160L
MM-PUR
DDIC Error (See SE14)
T160O
MM-PUR
DDIC Error (See SE14)
T160P
MM-PUR
DDIC Error (See SE14)
T160Q
MM-PUR
DDIC Error (See SE14)
T160R
MM-PUR
DDIC Error (See SE14)
T160S
MM-PUR
DDIC Error (See SE14)
T160T
MM-PUR
DDIC Error (See SE14)
T160V
MM-PUR
DDIC Error (See SE14)
T160W
MM-PUR
DDIC Error (See SE14)
T160X
MM-PUR
DDIC Error (See SE14)
T160Y
MM-PUR
DDIC Error (See SE14)
T161A
MM-PUR
DDIC Error (See SE14)
T161B
MM-PUR
DDIC Error (See SE14)
T161E
MM-PUR
DDIC Error (See SE14)
T161F
MM-PUR
DDIC Error (See SE14)
T161G
MM-PUR
DDIC Error (See SE14)
T161H
MM-PUR
DDIC Error (See SE14)
T161I
MM-PUR
DDIC Error (See SE14)
T161N
MM-PURHello!
I have experienced the same error.
I did a System Copy using ordinary DB backup/restore and after that SAPinst (Additional Software Life-Cycle Tasks).
I found that a unicode conversion program, UMG_POOL_TABLE, was executed at the end of SAPinst.
This program converted some of my pooled tables to Unicode (doubled fieldlength of VARDATA).
Even though I already run UNICODE.
I verified this by executing program RADPROTA, checking for logs starting with TPOCNV* (in found my candidates for next step).
With program RADPOCNV I could "reverse" the converted tables back to the correct length (for example ATAB with unicode you should have 904).
For more info read SAP Note 686357 - "Table pool nametab length incorrect after Unicode migration"
I suggest you check if you have any TPOCNV* logfiles containing any pooltable conversions.
If so check the pool tables in SE14.
If they are inconsistent you can use RADPCONV to correct them.
I guess there is some kind of bug in SAPinst.
Bye,
Lasse
Edited by: Lars Nilsson on May 7, 2008 4:37 PM -
Error when configuring ECC 6.0 system as application server
Hi guys,
I'm new to SDN.
I am having a problem configuring an ECC 6.0 system as an application system. It is correct in the SLD and it is updating the SLD with its information. It is setup as a business system with the correct Integration server. When I go to configure the integration engine I select global configuration and select pull data from SLD. I then get a message stating that the SLD is unavailable at this time. Any ideas? SLDCHECK works fine and comes back with the business system of the application system with no problems.hi
check whether the TECHNICAL and BUSINESS systems are registered properly or not.
check the role of the business system created.
The status of the SLD data supplier bridge should be running,else start the data collection again.(RZ70: SLD LOCAL ADMIN)
regards
kummari
Edited by: kummari on Oct 29, 2008 5:31 AM -
I have a scenario were i need to run the "ERP Initial Package for Time based Reduction" within the same system but different clients.
Is this possibe?
When i reach the step maintain RFC Destination, i maintain all the details and when i save the settings it shows a message "Not all RFC destination is ready for use".The RFC destinations get created in the Central/Control System.But not in the Sender/Receiver Client.
I believe this is because, the RFC name that the TDMS package generates is such that it cannot be run within the same system.
Can someone throw light on this? Is this scenario possible?
Thanks.Hi,
You can run TDMS package on the same system and between different clients. However SAP don't recommend to run TDMS package on the same system.
We tried this scenario, but we faced with the problem that Data Deletion step was very slow. Reason was because there are 2 ways to delete data in receiver system: Array delete and drop insert.
Drop insert is faster way to delete the data from the receiver client. But in this method it first delete data from all clients during the run and restores it back when deletion is completed. But this method you cannot use as receiver and sender both are on same system.
You have to use Array Insert only which is usually very slow as it first select the all the entries in table related to target client and then drop it. So, it is slow.
That is the reason SAP don't recommend to have TDMS run in same system.
Thanks
Sunny -
Severe error(s) occured in phase MAIN_INIT/UCMIG_STATUS_CHK!
Dear team,
We have started Upgrading our existing SAP R/3 x200 system ( Windows 6.1 & oracle 10.2.0.5) to ECC 6.0 EHP5.
All the processes upto 'check' completed without error.
In preprocessing phase we got stuck at phase "MAIN_INIT/UCMIG_STATUS_CHK!" ( As shown bellow).
Severe error(s) occured in phase MAIN_INIT/UCMIG_STATUS_CHK!
Last error code set: The Unicode Conversion Preparations on the startrelease (transaction SPUMG) have not been finished, procedure cannot continue
Trouble Ticket Generation
A trouble ticket and an archive with all relevant log files have been generated. Trouble ticket: "D:\usr\sap\SND\upg\abap\log\SAPup_troubleticket.log" Log archive: "D:\usr\sap\SND\upg\abap\log\SAPup_troubleticket_logs.sar"
We have manually done SPUMG as per note 1051576 (Our system is single code page system)
But error still exist.. Kindly guide.
Regards,
VishalHello Vishal,
Are you doing non-unicode R/3 x200 to unicode ECC 6.0 EHP5 upgrade? If yes, please go through CUUC upgrade document for pre-requisites.
Please take a look at below threads. It can help you.
CUUC - SPUMG Related Quary
http://www.saptechies.com/combined-upgrade-unicode-conversion-cuuc-faq/
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Dec 9, 2011 7:36 PM -
EHP6 - Severe error(s) occurred in phase PREP_INPUT/KX_CPYORG!
Hi All,
We are at the "extraction" stage of our EHP6 upgrade for pre-prod system, this serves as rehearsal for the execution of the same upgrade in production system.
However, SUM is stopped due to below error.
SUM - EXTRACTION phase stops at PREP_INPUT/KX_CPYORG, showing the error message below:
Severe error occurred in phase PREP_INPUT/KX_CPYORG!
Last error code set is: Failed to copy 1 files, check 'KX_CPYORG.LOG' for details
And checking from log, it shows "4EETQ399 Source file 'exe_syb.lst' missing!". This file doesn't exist anywhere in the system. Also, checking from logs of previous EHP6 upgrade in our DEV and QAS systems, this file doesn't exist. And instead of "exe_syb.lst", what has been copied from previous upgrades is 'exe_db6.lst'. We are at HP-UX and DB6.
Logs:
4EETQ399 Source file 'exe_syb.lst' missing!
1 ETQ399 Copied 821 files.
1EETQ399 Last error code set is: Failed to copy 1 files, check 'KX_CPYORG.LOG' for details
1EETQ204 Upgrade phase "KX_CPYORG" aborted with severe errors ("20140721180154")
Please advise how to fix.
Regards,
PhilipHI,
Kindly share 'KX_CPYORG.LOG files for analysis.Meanwhile try to patch the kernel with latest available at SMP and recheck for permissions and ownerships under kernel directory.
Regards,
Gaurav -
Error occured in the phase MOVE NAMETABS while updating patch.
Hi Gurus
When i implementing a SP15 to SP16 in a queue, i got the Dump.
Please help me in this issue.
The import was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Support Package Manager is unable to resolve
without your input.
After you have corrected the cause of the error, continue with the
import by choosing Support Package -> Import queue from the initial
screen of the Support Package Manager.
The following details help you to analyze the problem:
- Error in phase: IMPORT_PROPER
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package ALL, tp step "6", return code 0008
Notes on phase IMPORT_PROPER
In this phase repository objects and table entries are imported. This
phase can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The tp interface could not be called.
o TP_FAILURE: The program tp could not be executed. For more
information on this, see the SLOG or ALOG log file.
o TP_STEP_FAILURE: A tp step could not be executed. To find the cause
of the error, see the appropriate log, such as the import log.
If the cancelation message contains a tp step 6, N or S, the step in
question is independent of the transport request. You can find these
logs under the node Import steps not specific to transport request
in the log overview.
Alternatively, you can find these logs in the following files in the
log directory of your transport directory (usually:
/usr/sap/trans/log):
- tp Step 6: P<YY><MM><DD>.<SID>
- tp Step N: N<YY><MM><DD>.<SID>
- tp Step S: DS<YY><MM><DD>.<SID>
You can display these files using the report RSPUTPRT or by calling
transaction AL11.
A prerequisite of the Support Package Manager is that the Change and
Transport System (CTS) is configured correctly. For more detailed
information, read the online documentation available from Help -> SAP
Library -> mySAP Technology Components -> SAP Web Application Server ->
Change and Transport System .
A list of the most important SAP Notes for Online Correction Support
(OCS) is available in SAP Note 97620, which is updated regularly.
Regards,
GaneshHi jazz,
I want to update the patch SAPKA70016 for SAP_ABA component.
Queue log
System : ISP
tp path : tp
Version and release: 372.04.36 700
Activate inactive nametabs
End date and time : 20081215012202
Ended with return code: ===> 8 <===
TP request log is
START CMDIMPORT ISP L 20081222014354 DDIC usirs254 20081222014354043
STOP CMDIMPORT ISP L 20081222014401 DDIC usirs254 20081222014354043
START DD IMPORT ISP H 20081222014540 DDIC usirs254 20081222014540574
STOP DD IMPORT ISP H 20081222014616 DDIC usirs254 20081222014540574
START DD ACTIVATION ISP A 20081222014617 DDIC usirs254
START tp_getprots ISP J 20081222014617 DDIC usirs254
STOP tp_getprots ISP J 20081222014723 DDIC usirs254
STOP DD ACTIVATION ISP A 20081222014723 DDIC usirs254
START imp all ISP 20081222014723 DDIC usirs254 20081222014723434
INFO: event SAP_IMPORT_START triggered successfully
START DISTRIBUTION OF DD-O ISP S 20081222014723 DDIC usirs254 20081222014723434
START tp_getprots ISP S 20081222014723 DDIC usirs254 20081222014723434
STOP tp_getprots ISP S 20081222014726 DDIC usirs254 20081222014723434
STOP DISTRIBUTION OF DD-O ISP S 20081222014726 DDIC usirs254 20081222014723434
INFO TBATG CONVERSION OF ISP N not needed DDIC usirs254 20081222014723434
START MOVE NAMETABS ISP 6 20081222014726 DDIC usirs254 20081222014723434
START tp_getprots ISP P 20081222014726 DDIC usirs254 20081222014723434
ERROR ALL ISP 6 0008 20081222014743 DDIC usirs254 20081222014723434
STOP tp_getprots ISP P 20081222014747 DDIC usirs254 20081222014723434
STOP MOVE NAMETABS ISP 6 20081222014747 DDIC usirs254 20081222014723434
ERROR: stopping on error 8 during MOVE NAMETABS
START INFORM SAP-SYSTEM OF ISP Q 20081222014747 DDIC usirs254 20081222014723434
START tp_getprots ISP Q 20081222014747 DDIC usirs254 20081222014723434
STOP tp_getprots ISP Q 20081222014748 DDIC usirs254 20081222014723434
STOP INFORM SAP-SYSTEM OF ISP Q 20081222014748 DDIC usirs254 20081222014723434
STOP imp all ISP 0008 20081222014748 DDIC usirs254 20081222014723434
START CMDIMPORT ISP L 20081222015155 DDIC usirs254 20081222015155637
STOP CMDIMPORT ISP L 20081222015158 DDIC usirs254 20081222015155637 -
Hello!
Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
The following functions should be included in this program:
- detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
- comparison against a SAP ERP 6.0 reference system
- extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
- syntax analysis of program code with respect of adjustement need
- quality control of own development
- control of amount of transports within different company areas
- control of user information, such a user type, logon date, etc.
- basic control, whether a sufficient authorization concept is available
- Identification of objects that should be considered for the archiving in oder to decrease the db-size
My question are:
<b>- which tasks can be convered with SAP standard transactions what are the names of the transactions?
- which effort do I investigate for these tasks?</b>
Thank you very much!
regardsDear Thom,
To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.
Need to consider the following things:
For Reports its custom developed program so unless there is any kind of change in requirement from the client regarding the layout nothing needs to be changed I think it will work fine in ECC 6.0 to except few things may needs to be changed..so you need to discuss whether they want the reorts as it is right now or want to change the layout (adding some new info/fields etc) of any report so u need to modify the program for those and estimate accordingly for a medium complexitys Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing) so to modify it will be less than that (depending upon the scope of changes)
Now say for Batch Inputs(interface/Data Migration) using BDC you need to see how many BDCs are there again if the field lengths and layouts are not changing then no need to change anything (except the main thing ..you need to change the obsolete function modules there are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0 there are some new with enhanced functionality so you need to modify the BDCs and many cases it happens that the whole transaction screen changes for process in that case better to develop new BDCs so you have to consider those parameter look into and estimate accordingly modifying a BDC should not take more than 1 PD
Now say for Forms there was no Smart form in 4.6C form printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart form in that case its complete new dev so estimate accordingly a medium complexitys form should take 8 PD (FRSTDSCoding+Unit Testing) you can take it as 10 PD too even if client wants to keep it is as it was in older version you have to redevelop the layout in ECC 6.0 again as form printer is even client dependent maximum you can copy the program associated with that form in the new version too and your effort will be saved again you have to consider if clients wants to change the layout too
Now for enhancement so in that case u need to see individual cases for a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)
One more important thing is that the Unicode Compatibility this needs to be done .needs to change the code (variable name) accordingly .also Version management tool is used for the standard programs
Also pls find the following forums:
Re: Data Migration from 4.6C to ECC 6.0
List of transations supported in SAP 4.6c and not in ECC6.0
Re: Upgradation from 4.6C to ECC 6.0
Re: what's the advantage to upgrade 4.6c to ECC5.0...
RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
Upgrade batch inputs from 4.6C to mySAP ERP 2005
/thread/317225 [original link is broken]
Upgrade from SAP R/3 to ECC 6.0
Hope it will help you.
Thanks,
Atin
<b><b>Reward points if it helps.</b></b> -
4.7 Enterprise install error in catproc.sql phase(RedHat5- Oracle 10.2.0.4)
Hi,
I am installing SAP 4.7 Enterprise on Red Hat 5.3 and Oracle 10.2.0.4. When I install 4.7 Enterpirse I have an error in catproc.sql phase like below: -
ERROR 2009-06-02 18:42:34
CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-955 for defaultdestSQL> Rem bnainani 11/29/00 - specify compatible=8.0 for create_queue_tableSQL> Rem liwong 10/20/00 - add def$_destination.flagSQL> Rem bnainani 11/15/00 - specify compatible=8.0 for queue tableSQL> Rem narora 09/13/00 - add comment on new def$_destination columnsSQL> Rem liwong 09/01/00 - add master w/o quiesce: fixesSQL> Rem liwong 07/12/00 - add total_prop_time_latSQL> Rem liwong 06/29/00 - add total_txn_count, total_prop_timeSQL> Rem liwong 05/17/00 - add_master_db w/o quiesceSQL> Rem jstamos 05/17/00 - add_master_db w/o quiesceSQL> Rem elu 01/24/00 - add column apply_init to def$_destinationSQL> Rem alakshmi 12/02/99 - Bug 979398: Before-row insert trigger onSQL> Rem def$_propagatorSQL> Rem wesmith 10/31/98 - change shape of table def$_pushed_transactionsSQL> Rem jnath 02/23/98 - bug 601972: split anonymous pl/sql blocksSQL> Rem wesmith 01/21/98 - create def$_pushed_transactions table forSQL> Rem server-side RepAPISQL> Rem nbhatt 07/27/97 - change create_queuetable -> create_queue_tableSQL> Rem nbhatt 04/21/97 - change 'TRACKING' in CREATE_QUEUE to 'DEPENDENCYSQL> Rem nbhatt 04/21/97 - change syntax of create_queueSQL> Rem liwong 04/16/97 - Alter view system.AQ$DEF$_AQ{CALL,ERROR}SQL> Rem liwong 04/11/97 - Fixing defaultdest_primary typoSQL> Rem jstamos 04/10/97 - remove unneeded indexesSQL> Rem nbhatt 04/08/97 - change create_qtable to create_queuetableSQL> Rem jstamos 04/04/97 - tighter AQ integrationSQL> Rem liwong 04/02/97 - Add schema_name, package_name in def$_calldestSQL> Rem ato 03/31/97 - create_qtable interface changeSQL> Rem liwong 03/25/97 - remove batch_no from def$_tranorderSQL> Rem liwong 02/24/97 - pctversion --> 0 for def$_aqcall, def$_aqerrorSQL> Rem liwong 02/22/97 - Remove dropping view aq$def$_aqcallSQL> Rem ademers 02/07/97 - Remove constraint def$_calldest_callSQL> Rem liwong 01/11/97 - drop and create aq$def$_aqcall (temporary)SQL> Rem liwong 01/10/97 - Alter view aq$def$_aqcallSQL> Rem liwong 01/07/97 - Alter default value for batch_noSQL> Rem jstamos 12/23/96 - change temp$nclob colSQL> Rem jstamos 11/21/96 - nchar supportSQL> Rem sjain 11/11/96 - Remove dummy buffer # commentSQL> Rem asgoel 11/05/96 - Disable misc_tracking in def$_aqerrorSQL> Rem sjain 11/06/96 - deferror changesSQL> Rem vkrishna 10/28/96 - change STORED IN to STORE AS for lobSQL> Rem sjain 10/02/96 - Aq conversionSQL> Rem sbalaram 09/24/96 - ARPC performance - add foreign key indexSQL> Rem jstamos 09/06/96 - rename temp$lob and temporarily change nclobSQL> Rem sjain 09/03/96 - AQ conversonSQL> Rem ademers 08/02/96 - queue_batch default in def_destinationSQL> Rem ademers 07/29/96 - queue_batch default in def_callSQL> Rem ademers 07/29/96 - queue_batch defaultSQL> Rem jstamos 07/24/96 - add system.temp$lobSQL> Rem sbalaram 07/22/96 - create def$_aqcall and def$_aqerror tablesSQL> Rem jstamos 06/12/96 - LOB support for deferred RPCsSQL> Rem ldoo 06/28/96 - Comment out queue_table from def_tranorderSQL> Rem ademers 05/30/96 - create def_originSQL> Rem ademers 05/28/96 - fix def_destination col namesSQL> Rem ldoo 05/09/96 - New security modelSQL> Rem sjain 05/01/96 - add seq col to def_destinationSQL> Rem ademers 04/29/96 - add batch_no, dep_scn to def_callSQL> Rem jstamos 12/04/95 - 324303: use index to avoid sorting the queueSQL> Rem jstamos 08/17/95 - code review changesSQL> Rem jstamos 08/16/95 - add comments to tablesSQL> Rem wmaimone 01/04/96 - 7.3 mergeSQL> Rem hasun 01/31/95 - Modify tables.<br>SOLUTION: See ora_sql_results.log and the Oracle documentation for details.
Also some error lines in ora_sql_results.log file like below:
Connected to an idle instance.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Disconnected
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error and terminate the SQLPLUS session if the user is not SYS.
DOC> Disconnect and reconnect with AS SYSDBA.
ERROR at line 1:
ORA-01432: public synonym to be dropped does not exist
ERROR at line 1:
ORA-00942: table or view does not exist
DOC> The following PL/SQL block will cause an ORA-20000 error and
DOC> terminate the current SQLPLUS session if the user is not SYS.
DOC> Disconnect and reconnect with AS SYSDBA.
ERROR at line 1:
ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role
name
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
ERROR at line 1:
ORA-04043: object DIANA does not exist
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
ERROR at line 1:
ORA-04043: object SUBPTXT2 does not exist
ERROR at line 1:
ORA-04043: object CREATE_TABLE_COST_COLUMNS does not exist
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
And ora_sql.log file is:
connect / as sysdba ;
SHUTDOWN ABORT;
exit;
Executed successfully.
connect / as sysdba ;
SHUTDOWN IMMEDIATE;
exit;
Executed with error.
connect / as sysdba ;
STARTUP NOMOUNT;
exit;
Executed successfully.
connect / as sysdba ;
CREATE DATABASE MDP CONTROLFILE REUSE MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXLOGHISTORY 1000 MAXDATAFILES 254 MAXINSTANCES 50 NOARCHIVELOG CHARACTER SET UTF8 NATIONAL CHARACTER SET UTF8 DATAFILE '/oracle/MDP/sapdata1/system_1/system.data1' SIZE 350M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M EXTENT MANAGEMENT LOCAL DEFAULT TEMPORARY TABLESPACE PSAPTEMP TEMPFILE '/oracle/MDP/sapdata1/temp_1/temp.data1' SIZE 1750M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M UNDO TABLESPACE PSAPUNDO DATAFILE '/oracle/MDP/sapdata1/undo_1/undo.data1' SIZE 700M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M SYSAUX DATAFILE '/oracle/MDP/sapdata1/sysaux_1/sysaux.data1' SIZE 1000M REUSE AUTOEXTEND ON NEXT 20M MAXSIZE 10000M
LOGFILE GROUP 1 ('/oracle/MDP/origlogA/log_g11m1.dbf',
'/oracle/MDP/mirrlogA/log_g11m2.dbf') SIZE 50M REUSE ,
GROUP 2 ('/oracle/MDP/origlogB/log_g12m1.dbf',
'/oracle/MDP/mirrlogB/log_g12m2.dbf') SIZE 50M REUSE ,
GROUP 3 ('/oracle/MDP/origlogA/log_g13m1.dbf',
'/oracle/MDP/mirrlogA/log_g13m2.dbf') SIZE 50M REUSE ,
GROUP 4 ('/oracle/MDP/origlogB/log_g14m1.dbf',
'/oracle/MDP/mirrlogB/log_g14m2.dbf') SIZE 50M REUSE
exit;
Executed successfully.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catalog.sql
exit;
Executed successfully.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catblock.sql
exit;
Executed successfully.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
connect / as sysdba ;
set newpage 0
set space 0
set pagesize 0
set linesize 32767
set markup HTML off
set heading off
set verify off
set feedback off
set trimspool on
set sqlprompt SQL>
set termout on
set verify off
set echo off
spool ora_query3_tmp0_1.res
SELECT STATUS FROM V$INSTANCE;
spool off
exit;
Executed successfully.
connect / as sysdba ;
@@/oracle/MDP/102_64/rdbms/admin/catproc.sql
exit;
Executed with error.
The errors are like these. How can I correct these errors and continue to installation? Is the oracle version 10.2.0.4 not correct version to install 4.7 enterprise on Red Hat Linux 5.3?
Best regards,Hi Markus,
I found 5 ERROR. There are different lines.
First one:
<fld name="STATUS">
<strval><![CDATA[ERROR]]>
Second one:
CASE (= 'AUTOALLOCATE') RETURN (' AUTOALLOCATE '),
CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtAllocMode
Third one:
CASE (= 'DICTIONARY') RETURN (' DICTIONARY '),
CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtMode
Fourth one:
CASE (= 'AUTOALLOCATE') RETURN (' AUTOALLOCATE '),
CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtAllocMode
Fifth one:
CASE (= 'DICTIONARY') RETURN (' DICTIONARY '),
CASE (DEFAULT) RETURN (' ERROR ' + (tTablespaces.extMgmtMode
Which one will I change to OK? Must all off them change to OK?
Also is this problem about only these oracle error in your oppinion? For example in first line of ora_sql_results.log I have an error like below:
CJS-00084 SQL statement or script failed
Connected to an idle instance.
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
But ORACLE_HOME and ORACLE_SID environment variable are ok. Also I can connect and start and stop database manually. There is no problem about it.
I installed anly Oracle patch 10.2.0.4. I didn't install any oracle interim patch. Should I have install oracle interim patch for Oracle 10.2.0.4?
Best regards, -
Error in the RUN_RSVWSCPY phase
Hello Support,
We are having error in the RUN_RSVWSCPY phase (Shadow system Installation)
In one of the phases RUN_RSVWSCPY , it runs a job in the source system (i.e RPD)
Job Name :RSUG_COPY_SHD_VIEWS
This Job is cancelling with UNCAUGHT EXCEPTION
In the ST22 , it gives me ORA error
i.e ORA -01017 : invalid usename /password ;login denied.
When i checked the dev_w0 of the source system , i found the following error
B Connect to UPGSHD as SAPR3SHD with RPD
C Client NLS settings:
C Connecting as SAPR3SHD/<pwd>@RPD on connection 1 (nls_hdl 0) ... (dbsl 700 030508)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 0x113c62ff0 0x113c7b528 0x113c7add8
C Starting user session (con_hdl=1,svchp=0x1150708e8,srvhp=0x113c7f3a8,usrhp=0x115070278)
C *** ERROR => OCI-call 'OCISessionBegin' failed with rc=1017
[dboci.c 4532]
C *** ERROR => CONNECT failed with sql error '1017'
[dbsloci.c 11145]
B ***LOG BY2=> sql error 1017 performing CON [dbds#1 @ 1044] [dbds 1044 ]
B ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbds#1 @ 1044] [dbds 1044 ]
B ***LOG BY1=> sql error 1017 [dbacds#2 @ 1433] [dbacds 1433 ]
A TH VERBOSE LEVEL FULL
Please help
Regards
AnthonyPlease refer to these link
Error during creating the shadow system
Maybe you are looking for
-
Two weeks ago I wrongly faulted my new Dell 2707WFP monitor for its high contrast and saturation after many failed profiling attempts using the Spyder2Pro with the updated Vista software. I'm still at a loss as to why images are dark and overly satur
-
Export terminated with warnings.
Hi All, Using Oracle 9.2.0.4.0 I did an export from an owner connected as system and the export produces a few errors related to the SYS.LT_EXPORT_PKG package. EXP-00008: ORACLE error 4068 encountered ORA-04068: existing state of packages has been di
-
How can I get iTunes to recognize deauthorization?
I'm trying to deauthorize two old devices so I can Order music on my new computer. I have gone through the process several times and iTunes still days I have 5 devices authorized. How do I get my message through?
-
More trouble with AVCHD (seems a little different from others though)
I am trying to "log and transfer" my video from a Canon Vixia HF200. The video is in AVCHD format. It pulls up in the browser of the Log/Transfer just fine. Then when i add a clip to the queue section the Status thing spins for a second then just fre
-
Existing table compression in oracle 11g
Hi, We have a achema of 45gb in oracle 11g and need to compress the tables as it is rarely used, please can you tell me what are the option available to compress the tables. Thanks