Error in SCCL on ECC 6.0 system
Hi,
I am trying to copy client 350 from 000.
BD54 and SCC4 completed, the test run shows the below error ,
Error: Table FMATGRED30000001 error in DDIC - Check table with SE14
The data object could not be created: The type FMA TGRED30000001 does not exist
Error: Table FMATGRED30000002 error in DDIC - Check table with SE14
The data object could not be created: The type FMA TGRED30000002 does not exist
I could not find any SAP notes relating to this and I dont have these tables at all in 000 client in SE14 to check or rebuild.
Regards,
Kaustubh.
The Base is ECC 6.0 not yet upgraded to EHP
Anyways SAP has helped solve the problem.
Below is the solution :
3. You can use program ABADRCHECK to analyze the inconsistencies in the derivation. By selecting the checkbox 'DELSTEPS', you can automatically delete the steps recognized as inconsistent. Check the result carefully before you set this parameter. The check should always occur for all clients, that is, the checkbox 'ALLCLNTS' should remain selected.
HOW TO FIX CURRENT CLIENT COPY
(All steps to be performed in target logical system)
1. Decrease workload as much as possible
2. Execute report ABADRCHECK with selected 'DELSTEPS'
(see note 653314 for more details) -- Check point 3 above.
3. Execute TCode FINB_TR_EXEC_AI (Postprocessing of Client Copy) (Please note that any changes done between Client Copy and executing TCode FINB_TR_EXEC_AI will be overwritten!)
4. Result of FINB_TR_EXEC_AI execution
a) Executed with same error DA 300
The workload is still to high, make sure that workload is decreased and repeat steps 1. - 3.
b) Executed without any errors
Consider FINB-TR-DERIVATION part of Client Copy as completed successfully. Note, that status of Client Copy in TCode SCC3 "Post-Processing Required" is final and it's not updated based on successful execution of FINB_TR_EXEC_AI.
Information about final Client Copy status need to be evaluated and kept outside of SAP system. Or optionally, the client can be protected against any further manually triggered post processing procedure (e.g. using TCodes FINB_TR_EXEC_AI, FINB_TR_DISPLAY etc.) using the IMG activity "Complete Postprocessing". It's suggested to do so, when Client Copy is successfully repaired by repetitive execution of post processing procedure.
WHAT TO DO BEFORE NEXT CLIENT COPY
Make sure that there will be no performance issues during Client Copy processing in target logical system.
Similar Messages
-
Error during export of ECC 6.0 system for unicode conversion
We have upgraded a 4.7 system to ECC 6.0 running on MSSQL 2000. We have the latest r3load, and are using the Netweaver 7.0 sapinst to perform the system copy (export) to convert to unicode. Our goal is an exported system which we can use on a clean install once we have de-installed SAP and SQL 2000 and installed MSSQL 2005.
When running the export, the r3szchk finishes and then the next phase runs. But it gets almost all errors (so we are stopping the export).
The export_monitor.log is shown below, and also an example of one of the table logs shown here as well. but its almost as if every table hits the same problem, BSIS, MSEG, EDIDS etc.....
If you look at the ACCTIT.log, it looks like the SQL/stored preocedure error is as follows, but not sure what this means:
check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table T002 with rc 24
Export_Monitor.log
==============
NFO: 2008-08-25 17:30:11
Export Monitor is started.
CONFIG: 2008-08-25 17:30:11
Application options:
dataCodepage=4103
dbType=MSS
exportDirs=S:\ABAP
installDir=C:\Program Files\sapinst_instdir\NW04S\LM\COPY\MSS\EXP\CENTRAL\AS\EXP
jobNum=3
loadArgs=-stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\ED0\SYS\exe\run\R3load.exe
sapinst=
server=
trace=all
tskFiles=yes
CONFIG: 2008-08-25 17:30:11
List of packages with table structure: 'SAP0000'.
CONFIG: 2008-08-25 17:30:11
List of packages with views: 'SAPVIEW'.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'ACCTIT' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'BSIS' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'ACCTIT' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\ACCTIT.STR S:\ABAP\DB\DDLMSS.TPL ACCTIT.TSK MSS -l ACCTIT.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'CMFP' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'BSIS' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\BSIS.STR S:\ABAP\DB\DDLMSS.TPL BSIS.TSK MSS -l BSIS.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'CMFP' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\CMFP.STR S:\ABAP\DB\DDLMSS.TPL CMFP.TSK MSS -l CMFP.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'ACCTIT' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'CMFP' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e CMFP.cmd -datacodepage 4103 -l CMFP.log -stop_on_error
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'BSIS' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e BSIS.cmd -datacodepage 4103 -l BSIS.log -stop_on_error
ERROR: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'ACCTIT' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error' exited with return code 2.
For mode details see 'ACCTIT.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
ERROR: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'CMFP' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e CMFP.cmd -datacodepage 4103 -l CMFP.log -stop_on_error' exited with return code 2.
For mode details see 'CMFP.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
ERROR: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'BSIS' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e BSIS.cmd -datacodepage 4103 -l BSIS.log -stop_on_error' exited with return code 2.
For mode details see 'BSIS.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
etc.....
ACCTIT.log
=========
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: START OF LOG: 20080825191346
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: version R7.00/V1.4
Compiled Aug 18 2008 23:55:23
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\ACCTIT.STR S:\ABAP\DB\DDLMSS.TPL ACCTIT.TSK MSS -l ACCTIT.log
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: job completed
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: END OF LOG: 20080825191346
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: START OF LOG: 20080825191347
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: version R7.00/V1.4
Compiled Aug 18 2008 23:55:23
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error
(DB) INFO: connected to DB
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table T002 with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table CDPOS with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table TACOB with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) INFO: check NameTab widths: Ok.
(DB) INFO: Export without hintfile
(RSCP) INFO: UMGCOMCHAR read check, skip: no data found; probably old SPUMG.
(RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
(RSCP) WARN: UMGCONTAINER has 9 more problems.
(RSCP) WARN: UMGSETTINGS nametab creation: status not available, no table entry.
(RSCP) INFO: Global fallback code page = 0000
(RSCP) INFO: Common character set is 7-bit-ASCII
(RSCP) INFO: Collision resolution method is unexpected !
(RSCP) INFO: R3trans code pages = AskSPUMG
(RSCP) INFO: EXPORT TO ... code pages = AskSPUMG
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_NORM_LOG = 0
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_ALT_LOG = 0
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG = 0
(GSI) INFO: dbname = "ED0ecc6dev "
(GSI) INFO: vname = "MSSQL "
(GSI) INFO: hostname = "ECC6DEV "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "ECC6DEV"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "8x AMD64 Level 6 (Mod 23 Step 6)"
(BEK) ERROR: SAPSYSTEMNAME not in environment
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: END OF LOG: 20080825191348> We will quickly implement the UC as a separate project, not put it off forever.
VERY good decision!
> But as we have single code page, no JAVA integration, no web integration (SOA) etc... the added complexity on our already short timeframe is more than we care to take on at this point.
Happy upgrading!
Our upgrade from 4.7 to ERP 6.0 was one of the smoothest I've made.
Markus -
Error while registering SAP ECC system in UWL systems
hi,
Error while registering SAP ECC system in UWL systems.
Errors:
System R3Production: Thu Nov 27 16:12:05 GMT+05:30 2008
(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:Thu Nov 27 16:12:05 GMT+05:30 2008
(Connector) :com.sap.mw.jco.JCO$Exception:Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=132.147.0.112 SYSNR=00 GWHOST=132.147.0.112 GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '132.147.0.112:sapgw00' not reached
TIME Thu Nov 27 16:12:05 2008
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2823
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 79
ERRNO TEXT A remote host refused an attempted connect operation.
COUNTER 2
Item type retrieval and registration requires a connection to the systems and may take a couple of minutes
For each system, they are generated as the configuration named 'uwl.webflow.<system_alias>' or 'uwl.alert.<system_alias>'.
After configuration changes in the backend system, you must re-register the system.
regards.
Srinivas.Hi,
you can check few things prior proceeding:
Does your connector test after adding your backend system in portal works fine?
Did you define a system alias?
Make sure your SSO is working,
Also check your Jco detination webdynpro tab.
Regards,
Vamshi. -
Error in code page mapping for Source system whil loading the data from ECC
HI Gurus,
I am working in a implementation project, Recently our BI sand box is up, when i am doing my load from 0comp_code_attr it is throwing an error "Error in code page mapping for source system"(This is my first load from ECC).
In details tab it is showing as the data is sent from the source system but the data is not reaching to the PSA.
Please let me know if there are any settings needs to be made.
Many thanks in Advance
JagadeeshHI V,
Thanks for your quick response. I did it but it didn't resolve the issue. since the system id which i am having is 3 digits(LEC) but there it is taking only 2 digits, so i clicked on the button called Propose system ids, it has praposed LE, but the issue is stil there.
Do we need to do any settings in LBWE??
Thanks and Regards
Jagadeesh -
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 -
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 -
System copy errors during ABAP export ECC 5.0
Hi
I'm need to do system system copy for our ECC 5.0 system on Win/ora platform. I have followed the system copy document from SMP. I'm getting the below error while exporting the ABAP schema. Could someone guide me on how to fix this.
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPCLUST.log
=======================
(NT) Error: AABLG: normal NameTab from 20050112230750 younger than alternate NameTab from 20000323230317!
(SYSLOG) INFO: k CQF : AABLG&20000323230317&20050112230750& rscpgdio 47
(RSCP) ERROR: -
3-
(RSCP) ERROR: code: 64 RSCPECALL
(RSCP) ERROR: Altername NameTab too old
(RSCP) ERROR: module: rscpgdio location: 47 line: 3007
(RSCP) ERROR: TSL01: CQF p3: AABLG&20000323230317&20050112230750&
(RSCP) ERROR: -
myCluster (55.20.Exp): 924: received return code 64 from rscpCheckNTTimeStamps.
myCluster (55.20.Exp): 925: suspicious create timestamp of alternate nametab encountered.
myCluster (55.20.Exp): 929: create timestamps of nametab: 20050112230750; alternate nametab: 20000323230317.
myCluster (55.20.Exp): 299: error when retrieving physical nametab for table AABLG.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
======================
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPPOOL.log
===========================
(NT) Error: AT01: normal NameTab from 20050112234859 younger than alternate NameTab from 20011002204708!
(SYSLOG) INFO: k CQF : AT01&20011002204708&20050112234859& rscpgdio 47
(CNVPOOL) Altername NameTab too old AT01&20011002204708&20050112234859& Abort.
(CNVPOOL) conversion failed for row 0 of table VARKEY = 010100
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: environemnt variable "I18N_POOL_WIDTH" is not set. Checks are active.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
=========================
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.log
===========================
(NT) Error: DOKCLU: normal NameTab from 20050112230750 younger than alternate NameTab from 20000323224119!
(SYSLOG) INFO: k CQF : DOKCLU&20000323224119&20050112230750& rscpgdio 47
(RSCP) ERROR: -
3-
(RSCP) ERROR: code: 64 RSCPECALL
(RSCP) ERROR: Altername NameTab too old
(RSCP) ERROR: module: rscpgdio location: 47 line: 3007
(RSCP) ERROR: TSL01: CQF p3: DOKCLU&20000323224119&20050112230750&
(RSCP) ERROR: -
myCluster (55.20.Exp): 924: received return code 64 from rscpCheckNTTimeStamps.
myCluster (55.20.Exp): 925: suspicious create timestamp of alternate nametab encountered.
myCluster (55.20.Exp): 929: create timestamps of nametab: 20050112230750; alternate nametab: 20000323224119.
myCluster (55.20.Exp): 299: error when retrieving physical nametab for table DOKCLU.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
========================
ERROR 2008-12-25 11:32:27
MSC-01015 Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSDIC.log
========================
(EXP) INFO: check for inactive NameTab entries: Ok.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
=======================
Thanks & Regards
JaganC:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPCLUST.log
C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPPOOL.log
C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.log
C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSDIC.log
paste the above logs here.
Thanks
SM -
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 -
Error in installation of ECC 6 Import ABAP
I have got error during installation of ECC 6 on win 2003 and oracle.
"Not all objects are succefully processed. DIAGNOSIS: For detail see output file with invalid objects invalid_objects.txt and log file object_checker.log SOLUTION: Normally it indicates the data load error but in some special case (for example if some objects were created or loaded externally) you can press OK to continue.
Here is invalid_objects.txt
checkObjects=
dbType=ORA
strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
trace=all
tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
package object type action status
SAPDFACT ?N pkey create
and object_checker.log
INFO: 2020-12-31 10:12:55
Object Checker is started.
CONFIG: 2020-12-31 10:12:55
Application options:
checkObjects=
dbType=ORA
strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
trace=all
tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
CONFIG: 2020-12-31 10:12:55
List of packages with table structure: 'SAP0000'.
INFO: 2020-12-31 10:12:55
19 packages found in 'E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA' directories.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'MAPR~ADQ' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (!MSS) index 'MLST~1' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'MLST~1AD' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (!MSS) index 'MLST~2' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'MLST~2AD' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (!MSS) index 'MLST~4' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'MLST~4AD' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'PLMK~ADQ' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES_APP~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES_RB~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES_TI~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOY_CSH~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOY_SEARCH~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'STXH~TDN' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'BBSID~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'BSID~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (DB6) index 'DB6CSTRACE~1' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'KBED~3' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'KBED~4' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'NAST~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S003~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S003BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S003BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S004~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S004BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S004BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S006~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S006BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S006BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S011~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S011BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S011BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S012~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S012BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S012BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S013~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S013BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S013BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S031~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S032~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:13:02 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (DB6) index 'VARIS~DB6' found in STR file for 'SAPAPPL2' package.
TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Data load must be skipped for table 'DBPROPERTIES' from STR file for 'SAPSDIC' package.
TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Data load must be skipped for table 'DDLOG' from STR file for 'SAPSPROT' package.
ERROR: 2020-12-31 10:13:05
1 objects have error/ignore/execute or unknown status in the task lines.
Invalid objects are saved in 'invalid_objects.txt' file.
INFO: 2020-12-31 10:13:05
Object Checker is stopped.
I have not installed any object manually. Also not sure which object did not installed properly? Any idea or suggestion for this?
Thanks
Edited by: Prinesh Patel on Jan 7, 2008 7:35 PMHi Patel,
Thanks for your update.
Regards,
Hari. -
Error : No valid R/3 Back-end system
Hi CRM gurus,
I'm trying to connect SAP CRM 5.0 to SAP ECC 5.0.
When I launch trx R3AS for downloading the first object of the list coming from Best Practise (DNL_CUST_ACGRPB), I am getting the above error: "No valid R/3 Back-end system."
Now the point is that RFCs work smoothly, administration console as well and R/3 view CRMRFCPAR was filled correctly.
Where is the problem? I'm looking into, but without results.
Any suggestions in this issue will be rewarded.
Regards,
AndreAMany thanks Praveen,
I have carried out all the checks in the tables and it seems that everything is fine!.
Creating a RFC Destication for CRM in R/3
Maintain Table CRMRFCPAR and CRMCONSUM?
In Table CRMPAROLTP, Parameter "crm release" should set to your CRM version ( ex 500 for crm 5.0)
Maintain table TBE11, APPI should be NDI(new dimension integration),A yes
I don't really know where the error could lay.
Andrea -
Error opening file in ECC 6.0
Hi,
I am getting error in ECC 6.0 system, with open data set statement.
for the same statement, I am able to work in 4.7 version.
the sy-subrc is always 8 in ECC,
can someone help me here?
ThanksWelcome to SDN,
there may be sevral reasons for that.first yu need to check wether you have aurthurized to acces this file because may be in previous version you were aurthirized but while upgrade the system your user id may assign in some other Role.or may be oone of the reason if sy-subrc eq 8, then the file does not exist on the application server.
ust try with this:
OPEN DATASET <Path / filename> FOR INPUT IN TEXT MODE...
Look At FM : EPS_GET_DIRECTORY_LISTING
For Validation you can use Open dataset Command.
Amit. -
Errors in Pricing replication ECC to CRM 2007.
Hello,
When loading the price customizing from ECC to CRM I run into problems. I have loaded the object DNL_CUST_CNDALL.
When I check the application log in transaction SLG1 (Object COND_EXCHANGE, Subobject CUSTOMIZING), I see the following error messages:
Table PRCC_COND_PPD has been posted in the database with errors
Message no. CND_MAP155
Table PRCC_COND_PP has been posted in the database with errors
Message no. CND_MAP155
Table /SAPCND/CTLISTI has been posted in the database with errors
Message no. CND_MAP155
Table FGDC_COND_P has been posted in the database with errors
Message no. CND_MAP155
Table /SAPCND/T685 has been posted in the database with errors
Message no. CND_MAP155
Table PRCC_COND_CT has been posted in the database with errors
Message no. CND_MAP155
The following error message repeats for several hundred condition types:
Error converting field FIELD_TIMESTAMP into /SAPCND/T685 for condition type BI00.
Message no. CND_MAP181
I have reviewed OSS-notes relevant to these error messages and implemented:
- Note 905554 - Error in the initial download of DNL_CUST_CNDALL
I then loaded DNL_CUST_CNDALL again. This did not solve the issue.
I then checked:
- Note 314588 - Errors during correction of /SAPCND/T685-FIELD_TIMESTAMP
I ran report /SAPCND/RV12N001 for some of my condition tables, for example:
Application: CRM
Usage: PR
Table Number: CUS908
I then got the following error message:
Condition table CNCCRMPRCUS908 has a field with initial name
Message no. /SAPCND/GENERATOR040
I then checked:
- Note 514952 - Download of customer-specific tables
I followed the steps in the note, but with no result.
I can see that the entry in table /SAPCND/T681 for
KAPPL CRM
KVEWE PR
KOTABNR CUS908
is incomplete.
Any help much appreciated.Hi Ashwini
How to download pricng records from ECC to CRM system
I have downloaded objects DNL_CUST_CNDALL, DNL_CUST_PRD
But pricing condition msater data is not showing in CRM system.
Kindly help me in resolving the issue
Best regards
Raghu ram -
Error in Data transfer ECC to APO
Hello Guys,
I'm getting an error in my system when I try to transfer data from ECC to APO system. When I CIF (after generating IM, when I activate it) older data (master data created previously in system), I'm getting a short dump with mesage class 'XC', It says :
Diagnosis
An internal condition was found during the
the system to access a substandard program"
Trigger Location of Runtime Error
Program SAPLCSER
Include LCSERU02
Row 101
Module type (FUNCTION)
Module Name CIF_SER_MESSAGE_SERIALIZE.
But when I create a new data and try to transfer it, it smoothly transfers into APO without any dump or error.
Similarly, when I pull the data in APO with CCR, I get short dump while iterating data:
Category ABAP Programming Error
Runtime Errors DBIF_RSQL_TABLE_UNKNOWN
ABAP Program /SAPAPO/SAPLDM_LC_SQL
Application Component BC-DB-LCA.
The current ABAP program "/SAPAPO/SAPLDM_LC_SQL" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.
A table is referred to in an SAP Open SQL statement that either does not
exist or is unknown to the ABAP Data Dictionary.
The table involved is "/SAPAPO/ORDMAP" or another table accessed in the
statement.
I'm not much aware on LC technology, I have deactivated & activate LC once in LCA10. Also, checked consitency in OM17, it shown no inconsistency. Plus, when checked in OM13, all checks are showing green.
Can you please suggest what needs to be done?
Thanks,
AP.Hi Deepak,
Following is the detail I could see:
Cl. User Function Module Queue Name Destination Date Time
100 SS813794 MCEX_UPDATE_11_QRFC MCEX11 NONE 27.02.2014 05:33:02
100 SS813794 MCEX_UPDATE_11_QRFC MCEX11 NONE 02.03.2014 23:00:35
Status TID Host Tran Program
Transaction recorded AC131B362DEC530F145E0001 IGTBILSA VA01 RSM13000
Transaction recorded AC131B362DEC5313FE630002 IGTBILSA VA01 RSM13000
Both the queues which are seen are while I created a sales order in ECC.
If I further double click, it will take me into FM and after clicking queue name 'MCEX11' I could see:
LUW Information
TransID: AC131B362DEC530F145E0001
LUW-Cnt: 00000001
Thanks,
AP. -
Error during Upgrade of ECC 6.0 to EHP5
Hi,
I'm upgrading our ECC 6.0 system to EHP5 (on SLES 11) using SAPup.
The system check is blaming the os version (please see italic text):
Result of system check:
Window "SDTExecution Intervervention required":
Determined system information:
Type of operating system: Linux X86_64
Version of operating system: 2.11.1
Type of database: SAPDB
Version of database: 7.7.07.034
ERROR: OS version 2.11.1 out of range (too low) Upgrade the operating system at least to version 2.3. before you continue.
WARNING: OS version 2.11.1 out of range (too high) If this version is released for the downward compatible kernel you are using, please ignore this warning. If not, ask SAP for an individual release of your configuration. Do not continue before SAP supports your configuration.
So the ERROR message is wrong, the WARNING is correct. It seems the upgrade tool is expecting a version between 2.3 and 2.9. How can I handle this "wrong" error message?
Best regards,
Christian
Edited by: Christian Janson on Jul 11, 2011 8:24 AMHello,
under the link:
[http://service.sap.com/instguides]
in the left tree select:
--> SAP Business Suite Applications
--> SAP ERP
--> SAP ERP 6.0
--> SAP enhancement packages for SAP ERP 6.0
--> SAP enhancement package 5 for SAP ERP 6.0
i found the following text:
SAP Enhancement Package Installation on top of SAP ERP 6.0
The standard tool to install SAP ERP Enhancement Package 5 on top of SAP ERP 6.0 is the SAP Enhancement Package Installer.
Download the latest versions of the SAP enhancement package installer (SAPehpi) guide and the SAP enhancement package installer tool.
But in the download directory the tool SAPup is mentioned.
So I'm not sure, which tool to use. Sorry.
Regards, Michael -
Asset Accounting in Upgrade from 4.5B to ECC 6.0 system.
Hello
We have recently upgraded from 4.5B system to ECC 6.0 system.This is a Technical Upgrade.
We are getting errors when we post through transaction ASKB-Periodic Asset Posting.
The errors are that Documents cannot be posted as the GL Account for the Depreciation area 20-Cost Depreciation is a Reconciliation account and cannot be posted directly.
Could you please let me know the steps to be taken to ensure that the Asset Accounting is implemented correctly?
Any help in this regard is highly appreciated.
Awaiting your response!!
Regards
ShrutikaHi Shrutika
It appears as is if there is some issue with the configuration of your GL / configuration of GL with AA. Please refer to the following [link|https://www.sdn.sap.com/irj/scn/wiki?path=/display/erpfi/asset+accounting] on this site. This provides you excellent stuff on Asset Accounting.
Regards
Virendra Malik
Maybe you are looking for
-
My Western Digital external hard drive which I use as a Time Machine Backup stopped working. I tried repairing the disk using the Disk Utility program,but got the message that the utility can't repair the disk and to erase and reformat the disk. When
-
Adobe Acrobat Pro X Forms Error
I have created a form using Lifecyle Designer ES2. After I save the form as Reader Extended PDF enabling addition features, I open the form with Reader 9 or Acrobat Pro X and get a message "This operation is not permitted". After clicking "OK" server
-
Hi all i have this query: SELECT VTA.CO_VENDEDOR ,VTA.NB_VENDEDOR ,VTA.CO_CLASE_CLIENTE ,VTA.DE_CLASE_CLIENTE ,VTA.CO_CLIENTE ,VTA.NB_CLIENTE ,VTA.MN_VENDIDO ,NVL(DEV.MN_DEVUELTO,0) MN_DEVUELTO ,VTA.MN_VENDIDO - NVL(DEV.MN_DEVUELTO,0) MN_NETO_VENDIDO
-
Dear CRM guru, We're using the standard BDoc SI_CONTRACT to perform initial download of all utilities contracts from backend IS-U R3 system to CRM system. The BDocs are successfully created and there is no error as shown in SMW01. However, when we ch
-
Cannot Find Symbol Error, please help.
I am brand new to Java, so sorry if this question is obvious, but I keep receiving the following error when i try and compile the following code Circle.java Circle.java:17: cannot find symbol symbol : constructor Point() location: class pointClass.Po