Client-Copy form ecc 6.0 ehp 1 to ecc 6.0 ehp4
Hello Experts,
I would like to copy an entire Client from one system to another but the systems are on different ehp-levels.
The source-system is on ehp1 level while the target-system is on ehp4 level.
Are there any known problems that i should be aware of??
Thanks in advanced
Kalle Eismann
Hello,
I don't this this works. To my mind it's like performnig a client copy between 2 different releases.
The dictionnary should be slightly different so I don't think this works.
Here is a note from SAP about this :
Note 1398718 - CC:INFO-Client copy between different EHP'S
Best regards,
Steve.
Edited by: steve_78 on Sep 26, 2011 2:22 PM
Similar Messages
-
Local client Copy problem using sccl in ECC 6.0- Long time
Hi,
My system ecc6.0 and I am started the client copy form 000 client to 100 client
Now 25 passed but still the copy process not completed .
I am create the client 100 in 000
Then logged into 100
Then start the client copy usuing sccl in background
I am not run the test run
Please check the below logs and suggest.
Regards,
Ravi
Target Client 100
Source Client (incl. Auth.) 000
source Client User Master 000
Copy Type Local Copy
Profile SAP_ALL
Status Processing...
User SAP*
Start on 13.08.2008 / 16:25:57
Last Entry on 13.08.2008 / 17:00:51
Current Action: Post Processing Component
- Last Exit Program /SAPCND/CC_GROUP_WS_NG AP-PRC-CON
Statistics for this Run
- No. of Tables 54569 of 54569
- Deleted Lines 109
- Copied Lines 5101492
Output Sm66 :-
Sort: Server
Server Name No. Type PID Status Reason Sem Start Error CPU Time User Report Action Table
myhost_RD1_00 12 BTC 11391 Running Yes 92662 SAP* SAPLSDNT Sequential Read D010TAB
Client copy from 2008-08-13 16:26:00
System ID............................ RD1
Target client........................ 100
R/3 Release.......................... 700
Basis Support Package...............SAPKB70014
Host................................. myhost
Start in background............. .....X
User................................. SAP*
Parameter
Source client........................ 000
Source client user masters............000
Copier profile:.......................SAP_ALL
Table selection
Customizing data .....................X
With application data................ X
Initialize and recreate......... X
Change documents are not copied
Target client 100
Source client 000
User Name SAP*
SAP Release 700
Profile name SAP_ALL
Total number of tables 54.569
Number of Customizing and syst. tables 34.654
Number of application tables 18.185
Number of local tables (to delete) 1.730
Total number of exit programs 14
Number of selection exits 8
Number of generation exits 1
Number of other exit programs 5hello
It is waiting for some post processing.
Please check the
Note 930816 - Cond. Maint. group not generated after remote client copy.
971707 , 1176933
This will help you.
Thanks
Amit -
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 -
SRM "one-client" installation on ECC 6.0 EhP: Own client needed for SRM?
Hello experts,
i've a question concerning the SRM "one-client" installation on ECC 6.0 EhP4 as Add-On.
Is it possible to use SRM and ERP funtionality in a single client e.g. 001?
Or do we have to use different clients on the system like for SUS?
I haven't found any information regarding this topic in SAP ressources. I'm currently using CG "SAP SRM on One Client in
SAP ERP" Release date 2008 (found on marketplace/srm-inst --> srm7.0); SRM - Technical Basis Configuration (BuildingBlock S00/S03). I'm facing problems while going through the following customizing steps:
Assign logical System to Client [both logicall systems are on the same client (001)] ==> error while trying to reference the second logical sys. because client (001) cannot be used again (own presumption: error message differs)
I've seen that some of you have successfully installed and customized this szenario. If someone could provide me any helpful information or guideline how to proceed in general... would be great...
Best regards,
PATRICKThanks for your reply. I've checked the offline documentation because i've no access to solman.
There is a document which describes the steps for configuring one-client customizing on marketplace.
Link: [SAP SRM 7.0: SAP SRM on One Client with SAP ERP|https://websmp203.sap-ag.de/~sapidb/011000358700001201562009E]
The problem is that its impossible to cofigure the system like it's described in the document.
Let me explain why...
SRM Addon is installed and customizing is done in client 001 (same client as erp)
overview about defined logical systems:
-ONECLNTERP (for ERP is defined)
-ONECLNTEBP (for SRM is defined)
When I try to assign the logical system to client 001 it works for the first entry
for the second log. system it shows up an error message.
-->I assume because client 001 has been already assigned. I cant use client 001 again.
But One-Client szenario schould be possible in a single client or is SAPs One-Client more like One-System with differnet clients for SRM and ERP on the same machine?
Because of the above mentioned problem I assume that it's impossible to run ERP and SRM in the same Client number.
Am I right? Do I have to use two Clients on One System for proper Customizing?
Or if it's possible to use a single client on one machine for both ERP and SRM how is it possible to assign two log. systems to one client number?
I'm totally confused. Any help would be appreciated - any tips/hints/experiences from someone who has customized One-Client?
BR, Patrick -
Hi all,
I did a client copy in ECC IDES with client 800 as source client.As per the logs , copy is successful.The profile usedf is SAP_ALL.After the copy we logged into the new client which was
created and it looked good. Checked the Logs in SCC3 and it said that client copy was finished sucessfully.However now when we go and execute transactions MM01 and VA01, it is giving a error saying
Batch definition level not found.System inconsistency!
Not sure what went wrong, Any suggestions would be Helpful.
Regards,
Chaitanya.hi...
send the full details of ur client copy....
what is ur target client where u did this client copy .. i mean in prod dev -
Client copy in Test mode Fail in sol 7.1
Dear All
We face Problem in Client Copy in Test mode I send secreen short
nainesh
9376998808i also try to client copy form 000 clinet it fail and my job log is
Error: Table AIC_DISTRIBUTE error in DDIC - Check table with SE14
The data object could not be created: The type AIC _DISTRIBUTE does not exist.
Error: Table AIC_REL_SOURCE error in DDIC - Check table with SE14
The data object could not be created: The type AIC _REL_SOURCE does not exist.
Error: Table ARC_TRANS_TCURX error in DDIC - Check table with SE14
The data object could not be created: The type ARC _TRANS_TCURX does not exist.
Error: Table CRMC_TBZ5 error in DDIC - Check table with SE14
The data object could not be created: The type CRM C_TBZ5 does not exist.
Error: Table CSU_JOB_PARAMS error in DDIC - Check table with SE14
The data object could not be created: The type CSU _JOB_PARAMS does not exist.
Error: Table DVM_BOF_PACKS error in DDIC - Check table with SE14
The data object could not be created: The type DVM _BOF_PACKS does not exist.
Error: Table DVM_BOF_RUNS error in DDIC - Check table with SE14
The data object could not be created: The type DVM _BOF_RUNS does not exist.
Error: Table DVM_BOF_STATS error in DDIC - Check table with SE14
The data object could not be created: The type DVM _BOF_STATS does not exist.
Error: Table ESH_ADM_EXCFLDS error in DDIC - Check table with SE14
The data object could not be created: The type ESH _ADM_EXCFLDS does not exist.
Error: Table ESH_URL_EXCFLDS error in DDIC - Check table with SE14
The data object could not be created: The type ESH _URL_EXCFLDS does not exist.
Error: Table FDT_TRANS_Q_0010 error in DDIC - Check table with SE14
The data object could not be created: The type FDT _TRANS_Q_0010 does not exist.
Error: Table FDT_TRANS_Q_0011 error in DDIC - Check table with SE14
The data object could not be created: The type FDT _TRANS_Q_0011 does not exist.
Error: Table ICMON_IFC_TH error in DDIC - Check table with SE14
The data object could not be created: The type ICM ON_IFC_TH does not exist.
Error: Table ICMON_IF_TH error in DDIC - Check table with SE14
The data object could not be created: The type ICM ON_IF_TH does not exist.
Error: Table MSSPPACK error in DDIC - Check table with SE14
The data object could not be created: The type MSS PPACK does not exist.
Error: Table SAML2_USED_ASSRT error in DDIC - Check table with SE14
The data object could not be created: The type SAM L2_USED_ASSRT does not exist.
Error: Table SAPFTP_SERVERS error in DDIC - Check table with SE14
The data object could not be created: The type SAP FTP_SERVERS does not exist.
Error: Table SMDPROPVAL error in DDIC - Check table with SE14
The data object could not be created: The type SMD PROPVAL does not exist.
Error: Table SNWD_EPM_SNAPS error in DDIC - Check table with SE14
The data object could not be created: The type SNW D_EPM_SNAPS does not exist.
Error: Table SWF_UNIT_CONF error in DDIC - Check table with SE14
The data object could not be created: The type SWF _UNIT_CONF does not exist.
Error: Table SWF_UNIT_MON error in DDIC - Check table with SE14
The data object could not be created: The type SWF _UNIT_MON does not exist.
Error: Table T77TMCPIC_URLS error in DDIC - Check table with SE14
The data object could not be created: The type T77 TMCPIC_URLS does not exist.
Error: Table TBDBDLSAARG error in DDIC - Check table with SE14
The data object could not be created: The type TBD BDLSAARG does not exist.
Error: Table TBDBDLSADMIN error in DDIC - Check table with SE14
The data object could not be created: The type TBD BDLSADMIN does not exist.
Error: Table TBDBDLSAKEY error in DDIC - Check table with SE14
nainesh
9376998808 -
Local client copy giving trouble SAP ECC 6.0
Hello All,
I installed SAP ecc 6.0 Implementation version. Then created 100 client as Development and 200 client as Golden client.
Our Functional people are using 100 client for development activities.
Now Functional people need sand box client 300.
Created 300 client by using 000 client, user ddic. Using transaction scc4.
Logged on with 300 client, user sap*, p/w pass. Gone to sccl transaction trying to copy 100 client data to 300 client.
BUT IT IS SHOWING
Runtime Errors TIME_OUT
Date and Time 10.01.2008 11:12:12
Shot dump has not been completely stored ( too big)
Short text -
Time Limit exceeded.
What happened?
The program SAPLSDBI_DYNSQL has exceeded the maximum permitted runtime with out interruption and has therefore been terminated
VIRTUAL MEMORY PROBLEM I AM GETTING, TRY TO GIVE THE SOLUTION FOR SOLVING THE ISSUE.
Regards,
SateeshHi Sateesh,
Increase the number of parallel jobs for the client copy before executing background mode.
Regards,
Tolulope
Edited by: Tolulope OKUSAGA on Jan 19, 2008 12:58 PM -
ECC - APO Integration (Client Copy)
Hello,
What if the source ECC client of APO has a new client(copy) and APO should connect to this new client. Should all master data be re-integrated from the new client? I would need your advise on this since when i was maintaining the publication settings for data to be transferred from APO for the new client, I noticed it warned that the plant i used was from another client.
Thanks.Hi,
In client copies, you copy the "wrong" logical systems too. So you need to review the connectivity settings (logical system, business system group, assigning the right logical system to new client etc) thoroughly.
You once again need to generate and activate the integration models as the original models are referring to the old APO logical system. Please check all background job variants where the field logical system is involved e.g. CCR, RIMODAC2
Also ensure the consistency of live cache to the APO DB (GUID's). Check the mapping tables of master data.
Regards,
Loknath -
Client Copy Error on ECC 6.0
New install of ECC 6.0.
Attempted to perform a client copy of 000 and received the following message:
"Cannot open log:
iscap02sapmnt\trans\log\CC001088.ECC
Message no. TA074
The action you requested writes a log file. However, log file
iscap02\sapmnt\trans\log\CC001088.ECC could not be opened.
System Response
The action was terminated.
Procedure
Contact your system Admininstrator."
Would like to know how to maintain the directory which includes the log file?Anthony, who install this server ? Are you able to login in this OS (remote for example) under user who has an "administrator" permission? You need change the permissions on "sapmnt" folder and for Share on this folder, SAP server works on windows under SAPservice"SID" user account, and as you can see
"The action you requested writes a log file. However, log file
iscap02\sapmnt\trans\log\CC001088.ECC could not be opened"
Try also check only
iscap02 , are you see the "sapmnt" folder? Regards. -
Hi Experts,
While Client copy in Local System , I am facin gthis Error, please anybody help me out.
client copy error:cannot open log:/w2k3-web53/sapmnt/trans/log/cc000007.ecc
Regards,
Amit,Your Error Message is like => cannot open log:/w2k3-web53/sapmnt/trans/log/cc000007.ecc
This means 'w2k3-web53' is your machine name. and your sap system name is 'ECC'.
1) If you are on windows then :
Type '
w2k3-web53\sapmnt' in address bar, this gives you an error and hence you are getting the above mentioned SAP error.
Therefore to get out of this error follow the simple steps=>
I) Create 'sapmnt/trans/log' (recursive) directories anywhere on your machine.
II) Share 'sapmnt' directory over network {right click on directory->properties->sharing} with full access to others.
III) Confirm this by typing '
w2k3-web53\sapmnt' in your address bar. 'CC00000*.ECC' will be created automatically by SAP system while copying.
2) If you are using Linux then:
Create the directories as mentioned above and give full access to directories by using CHMOD command.
Share 'sapmnt' directory if necessary.
Note: Change the protection level of your client in SAP if necessary:
SCC4->EDIT->Double click your client -> then set Protection level at level 0 {No restriction}. -
ECC 6.0 Client Copy - Source Cl User Master?
When completing a client copy I have created the new client using SALE - Logical Systems - Define Logical System
I created a test client 900 (which I would like to build from our golden client 200) I have a couple of questions. From the documentation I am using it indicates that after completing the definition of the new client. we should reset SAP* by adding login/no_automatic_user_sapstar = 0 (which I am familiar with)
rebooted SAP (previously backing up the kernel of course)
Log into new client 900 and create a user to later use for RFC destination configuration. Unfortunately this new client may not yet contain any data so that when I try to create this userid none of the drop downs in SU01 contain data. I was able to create the new user BUT it has no profiles etc... that I can assign.
This is my first question... I think this user should be configured after the client copy??? right?
Last question,
When I run SCCL I want to copy from client 200 to NEWLY created client 900.
So the entry screen should go something like this (please confirm)
Target Client 900
Selected Profile sap_all
Description All client specific data w/o change options
Source Client 200
Source Client User Masters 200
my question also, do I get User Masters from client 200 because there have been HCM table configurations etc... recently applied or do I get this information from client 000, My guess is I would get it from client 200.
sorry for the long message I just wanted to provide background.
mariaSomething else occured to me...
by creating two additional clients in my QAS server and only one instance of SAP is installed ... currently only two clients exist 200 and 600 and they EXIST in all three environments dev, qas and prdn.
BY introducting two clients ONLY in QAS how will I transport items from client 200 DEV to 201 or 202 QAS? Will I need to make changes to stms? if so what?
The purpose of adding these additional clients is to separate testing, training and parallel testing that our PeopleSOft migration project team (migragation of Peoples soft to SAP) for HCM will nedd to .
Maria -
Logical System and Client copy
Hi Gurus ,
I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
Regards
SelvanHi Manjula ,
Below i mentioned the full detail about the error .
RFC destination for client copy in systems with Financials Basis (FINBASIS) component.
The system could not find any suitable RFC destination for processing for client 000. This note also appears if an RFC destination was found but this does not work. o RFC destination: FINBTR@ID3CLNT000 o Error text: Error during the retrieval of the logon data Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection or perform the following steps manually: 1. Create an RFC destination with the target ZK>source client of client copy (in this case 000).
2. Check whether the RFC destination works in transaction SM59. To avoid errors when assigning the password or the authorizations of the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination: - Transaction: FINB_TR_DEST (Destinations for Transport Methods of the Financials Basis) - Client: 000
4. Start the client copy again.
Kindly advice me
selvan -
Unable to log in to newly create client copy
I 'm attempting to create a new client from a newly installed ECC 6.0 IDES system. I go into SCC4 and create a new lient '200' and log off.
I try to log in to client 200 using sap* and pass and get wrong username or password error.
I can see the client listed in scc4, but can't log into it.
Any ideas?
BobHello,
Having the previous question answered helped alot, but I do have another question:
Can I put the client copy on a different drive than the original?
I have SAP installed on the E: drive and would like to place the new copy client on the F: drive, can I do that?
Bob -
Remote Client Copy - Ended in Erros
Hi Friends,
We recently performed a Remote client copy. What we normally do is we restore an latest offline backup of the Prod into an instance built exclusively for performing client copies into our QA system.
So if our actual PROD is ABC ( production ), the replica system is ADC. We restore latest backup onto ADC. Then from ADC we do a client copy onto AQC ( Quality ). We have n number of clients in AQC. When copying into a particular client we are facing this problem of 3 tables not being able to get copied. They are BKPF,LTAK and SOST. It happened twice that the Remote client ended with errors.
It says "Read or conversion error". The detailed error looks like below ;
TAB_COPY_R_CONTINUE LTAK WITH KEY:
I01 0000066362
Read or conversion error system: ADCT500 table: LTAK
ERROR: Internal error when inserting in table: LTAK
Internal error: 1,262,713 65,536 VERIFY_CNT
Process 00001 has copied data 25.02.2010 18:04:16
Read or conversion error system: ADC500 table: BKPF
Process 00002 has copied data 25.02.2010 19:09:00
Start: Recopy errors 25.02.2010 19:09:02
TAB_COPY_R_CONTINUE BKPF WITH KEY:
2100 5100019665 2008
Read or conversion error system: ADC500 table: BKPF
ERROR: Internal error when inserting in table: BKPF
Internal error: 6,948,636 1,777,664 VERIFY_CNT
Read or conversion error system: ADC500 table: LTAK
TAB_COPY_R_CONTINUE SOST WITH KEY:
OTF 34 000000019247
Read or conversion error system: ADC500 table: SOST
ERROR: Internal error when inserting in table: SOST
Internal error: 2,594,254 180,224 VERIFY_CNT
We approached SAP and they asked to do a DB reorg, run update statistics on both source and target and then re run the client copy.
Well DB reorg is a big activity so we just updated the statistics and ran again the "recopying errors" but still it is the same problem.
Can anybody please suggest something. Thank you.
regards
Vinod KHi Friends,
My apologies for coming back to you guys so late. I kind of was lost to find a solution for this.
Hi Sanujit,
The database logs dont indicate anything at all about this error or i am not able to locate them.
Rajesh,
There was a table comparison done for these tables properties in both source and target and everything looked ok and confirmed by the application.
At this moment we have anyway decided to go a fresh client copy again as lot of time has already passed and there would be differences in source and target tables.
But anyway could you please tell me the procedure to transport tables between source and target systems?
Hi Anil,
SAP iS ECC 6.0 and Oracle is 10.2.0.4.0
Thanks again for your time and pateince.
Regards
Vinod K -
Unable to create IDOCs after client copy
I'm unable to create IDOCs after a client copy. I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
Does anyone know what how to fix this. Thank you in advance.
Runtime Error SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
Date and Time 22.10.2007 16:50:51
ShrtText
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLEDI1" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLEDI1" or "LEDI1F09"
"F09_IDOC_INSERT_WITH_NUMBER"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"F09_IDOC_INSERT_WITH_NUMBER"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "auaplxr3q"
Network address.......... "128.197.135.5"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "000B439ED600"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "auaplxr3q"
Database type............ "ORACLE"
Database name............ "Q63"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Mar 22 2007 20:48:46"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "175"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 4189928
Heap..................... 0
Page..................... 0
MM Used.................. 1469352
MM Free.................. 2718056
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "SAPLEDI1" in
"F09_IDOC_INSERT_WITH_NUMBER".
The main program was "SAPMSSY1 ".
The termination occurred in line 108 of the source code of the (Include)
program "LEDI1F09"
of the source code of program "LEDI1F09" (when calling the editor 1080).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
of the (Include) program "LEDI1F09 ".
Source Code Extract
Line
SourceCde
78
perform call_badi tables list_container_insert
79
using control
80
ident.
81
Aufruf des Badi's für das einstreuen neuer Segmente
82
perform call_insert_badi tables list_container_insert
83
using control
84
ident
85
changing maxsegnum.
86
87
free list_container_insert
88
FREE_RETURN = 1.
89
ELSE. " no other IDoc is open in create-mode
90
LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
91
AND DOCNUM EQ IDENT.
92
LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
93
MODIFY LIST_CONTAINER_CREATE.
94
ADD 1 TO MAXSEGNUM.
95
ENDLOOP.
96
if control-mestyp eq c_mestyp.
97
CALL FUNCTION 'FUNCTION_EXISTS'
98
EXPORTING
99
funcname = c_func
100
EXCEPTIONS
101
FUNCTION_NOT_EXIST = 1.
102
IF syst-subrc IS INITIAL. "Anwendungssystem
103
perform call_transform
104
tables list_container_create
105
using control.
106
ENDIF.
107
endif.
>>>>>
INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
109
Aufruf des Badi's für das Anwendungsmapping einzelner Felder
110
perform call_badi tables list_container_create
111
using control
112
ident.
113
perform call_insert_badi tables list_container_create
114
using control
115
ident
116
changing maxsegnum.
117
118
free list_container_create
119
FREE_RETURN = 0.
120
ENDIF.
121
122
insert status records
123
124
SYN_ERROR_IN = ' '.
125
CNTR_STATUS = 0.
126
REFRESH LIST_STATUS.
127
CLEAR LIST_STATUS.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
13 FORM SAPLEDI1 LEDI1F09 108
F09_IDOC_INSERT_WITH_NUMBER
12 FUNCTION SAPLEDI1 LEDI1U19 33
EDI_DOCUMENT_CLOSE_CREATE_TAB
11 FUNCTION SAPLEDIR LEDIRU01 273
IDOC_INBOUND_WRITE_TO_DB
10 FORM SAPLEDIN LEDINF01 457
ONE_IDOC_STORE
9 FUNCTION SAPLEDIN LEDINU05 234
IDOC_INBOUND_ASYNCHRONOUS
8 FORM SAPLEDIN LEDINV05 19
IDOC_INBOUND_ASYNCHRONOUS
7 FORM SAPMSSY1 SAPMSSY1 254
XAB_RUN_DRIVER
6 FUNCTION SAPLSXAB LSXABU01 9
RFC_RUN_XAB_DRIVER
5 FUNCTION SAPLERFC LERFCU01 59
ARFC_EXECUTE
4 FUNCTION SAPLERFC LERFCU02 229
ARFC_DEST_SHIP
3 FORM SAPLERFC LERFCV02 28
ARFC_DEST_SHIP
2 FORM SAPMSSY1 SAPMSSY1 69
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 13 Ty. FORM
Name F09_IDOC_INSERT_WITH_NUMBER
CONTROL-MESTYP
USERCLONE
554544444222222222222222222222
53523CFE5000000000000000000000
C_MESTYP
FIDCCH
444444222222222222222222222222
694338000000000000000000000000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
LIST_STATUS-STAPA2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
C_FUNC
IDOC_TRANSFORM
444455544544542222222222222222
94F3F421E36F2D0000000000000000
SYST-REPID
SAPLEDI1
5454444322222222222222222222222222222222
310C549100000000000000000000000000000000
SY-UNAME
Q63CLNT140
533444533322
1633CE414000
%_DUMMY$$
2222
0000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SYST-SUBRC
0
0000
0000
ALE_IDOC_TO_APL_OK
62
33
62
LIST_CONTAINER_CREATE[]
Table IT_20[9x1068]
FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
Table reference: 14
TABH+ 0(20) = 070000008036F5B8000000000000000000000000
TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
TABH+ 40(16) = 0400002300000CA0000824C401000000
store = 0x070000008036F5B8
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 14 (0x0000000E)
label = 20 (0x00000014)
fill = 9 (0x00000009)
leng = 1068 (0x0000042C)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000048
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x070000008036F610
pghook = 0x07000000802D86D0
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 23 (0x00000017)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LIST_CONTAINER_CREATE
1400000000000511747000000009E1BPADRML 00000002#èXD63 070TST_QA140_1
3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
CONTROL
1400000000000511747640 64 2SAPQ63 LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
G_MAXSYNERR
1
0000
0001
<%_TABLE_EDID4>
ALE_DISPATCH_ERROR
27
33
27
ALE_IDOC_READY_FOR_APL
64
33
64
%_SPACE
2
0
IDENT
0000000000000001
3333333333333333
0000000000000001
ALE_IDOC_TO_APL_ERROR
63
33
63
No. 12 Ty. FUNCTION
Name EDI_DOCUMENT_CLOSE_CREATE_TAB
IDENTIFIER
0000000000000001
3333333333333333
0000000000000001
NO_DEQUEUE
X
5
8
SYN_ACTIVE
Y
5
9
IDOC_CONTROL
1400000000000511747640 64 2SAPQ63 LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
SYNTAX_RETURN
0
0000
0000
INT_EDIDD[]
Table IT_10[9x1062]
FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
Table reference: 9
TABH+ 0(20) = 0700000080284B80070000008028530800000000
TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
TABH+ 40(16) = 0400000900000AA8000824C401000000
store = 0x0700000080284B80
ext1 = 0x0700000080285308
shmId = 0 (0x00000000)
id = 9 (0x00000009)
label = 10 (0x0000000A)
fill = 9 (0x00000009)
leng = 1062 (0x00000426)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000039
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000080320D90
pghook = 0x07000000802E1508
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 17 (0x00000011)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0x07000000802852A8
>>>>> 2nd level extension part <<<<<
tabhBack = 0x0700000080284B30
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
NO_IGNORE
2
0
EDI_IDOC_SYNTAX_ERROR_IN
60
33
60
DOCNUM
0000000000511747
3333333333333333
0000000000511747
EXCLUSIVE
E
4
5
SYNCHRONOUS
S
5
3
APL_TESTIDOC_CHECK_OK
55
33
55
FREE_RETURN
0
0000
0000
INT_EDIDD
1400000000000000001000009E1BPADRML 00000000##XD63 070TST_QA140_17 X00
3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
SUB_INT_ACK_POSITIVE
14
33
14
G_INSERT_OK
2
0
LIST_CONTAINER_INSERT_TMP[]
Table[initial]
LIST_CONTAINER_INSERT_TMP
0000000000000000000000000 00000000##
2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 11 Ty. FUNCTION
Name IDOC_INBOUND_WRITE_TO_DB
PI_DO_HANDLE_ERROR
X
5
8
PI_NO_DEQUEUE
X
5
8
PI_RETURN_DATA_FLAG
X
5
8
PI_RFC_MULTI_CP
0000
3333
0000
PI_STATUS_MESSAGE
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PE_IDOC_NUMBER
0000000000000001
3333333333333333
0000000000000001
PE_INBOUND_PROCESS_DATA
140BAPI 6
3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
PE_STATE_OF_PROCESSING
0
0000
0000
T_DATA_RECORDS[]
Table IT_10[9x1062]
T_LINKED_OBJECTS[]
Table IT_11[0x100]
FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
Table reference: 10
TABH+ 0(20) = 000000000000000007000000802853F000000000
TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
TABH+ 40(16) = 0400000900002BB00010249401000000
store = 0x0000000000000000
ext1 = 0x07000000802853F0
shmId = 0 (0x00000000)
id = 10 (0x0000000A)
label = 11 (0x0000000B)
fill = 0 (0x00000000)
leng = 100 (0x00000064)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000190
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0x0700000080285390
>>>>> 2nd level extension part <<<<<
tabhBack = 0x0700000080285340
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
PC_CONTROL_RECORD
1400000000000000000 30 2 LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
L_STATUS
64
33
64
L_ALE_SUCCESS_MESSAGE
B1 S005 No filters
4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
ST_PREVIOUS_PARTNER_DATA-SYNCHK
X
5
8
C_TRUE
X
5
8
SYST-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
C_ELEMENT_UNPROCESSED_IDOCS
Unprocessed_IDocs
56776667766544667222222222222222
5E02F353354F94F33000000000000000
ST_PREVIOUS_STATE_OF_PROCE
0
0000
0000
ST_INBOUND_PROCESS_DATA-EDIVR2
6
3
6
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
L_SYN_ACTIVE
Y
5
9
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
L_SYNTAX_RETURN
0
0000
0000
%_DUMMY$$
2222
0000
SY-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
No. 10 Ty. FORM
Name ONE_IDOC_STORE
IDOC_NUMBER_IN
0000000000000000
3333333333333333
0000000000000000
STATE_OF_PROCESSING_IN
0
0000
0000
INBOUND_PROCESS_DATA_IN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS[]
Table[initial]
G_LAST_IDOC_NUMBER
0000000000000000
3333333333333333
0000000000000000
SYST-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
CURRENT_CONTROL_RECORD_IN-DOCNUM
0000000000000000
3333333333333333
0000000000000000
CONV_ERROR
2
0
C_TRUE
X
5
8
SY
0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
STATUS_MESSAGE_IN
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_IDOC_SELECT_AND_WRITE_TO_DB
5
3
5
SY-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
STATUS_MESSAGE_IN-STAMID
22222222222222222222
00000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
STATUS_MESSAGE_IN-STAMNO
000
333
000
RET_FLAG
X
5
8
G_RFC_CODEPAGE
0000
3333
0000
RSJOBINFO-JOBSUBRC
0
0000
0000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
SY-LANGU
E
4
5
G_T_DATA_RECORDS[]
Table IT_10[9x1062]
LT_LINKED_OBJECTS[]
Table IT_11[0x100]
CURRENT_CONTROL_RECORD_IN
1400000000000000000 30 2 LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
SWO_%OBJID
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 9 Ty. FUNCTION
Name IDOC_INBOUND_ASYNCHRONOUS
IDOC_CONTROL_REC_40[]
Table IT_3[1x524]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
Table reference: 3
TABH+ 0(20) = 07000000802D876007000000802D449000000000
TABH+ 20(20) = 0000000300000003000000010000020C000000E0
TABH+ 40(16) = 0400000900001FE0000A249001000000
store = 0x07000000802D8760
ext1 = 0x07000000802D4490
shmId = 0 (0x00000000)
id = 3 (0x00000003)
label = 3 (0x00000003)
fill = 1 (0x00000001)
leng = 524 (0x0000020C)
loop = 224 (0x000000E0)
xtyp = TYPE#000136
occu = 10 (0x0000000A)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 0
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000802DB9D8
pghook = 0x0000000000000000
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 10 (0x0000000A)
lineAlloc = 10 (0x0000000A)
store_id = 9 (0x00000009)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0x07000000802D88A0
>>>>> 2nd level extension part <<<<<
tabhBack = 0x07000000802D8710
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
IDOC_DATA_REC_40[]
Table IT_4[9x1063]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
Table reference: 4
TABH+ 0(20) = 07000000802D880807000000802D896000000000
TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
TABH+ 40(16) = 04000009000020500008249001000000
store = 0x07000000802D8808
ext1 = 0x07000000802D8960
shmId = 0 (0x00000000)
id = 4 (0x00000004)
label = 4 (0x00000004)
fill = 9 (0x00000009)
leng = 1063 (0x00000427)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000138
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 0
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000802E1550
pghook = 0x07000000802D8860
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 12 (0x0000000C)
shmIsReadOnly = 0 (0xHi Rohan,
Welcome to SDN!
This error means that you're trying to duplicate a record on the DB... check the IDOC number ranges... it might help
Regards
Juan
Please reward with points if helpful
Maybe you are looking for
-
How can I create a list of addresses from the Junk folder?
I am using TB 24.7 and I have a long list of e-mail addresses in my junk folder. I need to harvest those to add them to my server's black list. How can that be done? Thanks.
-
Using oDATA for BI in Project Server 2013
Hi gang, I am looking to create a BI report that I was able to do quite readily in previous versions of Project Server. I'm trying to create a graph that simply plots resource capacity and work as measures over time, with the resource roles as a fil
-
SQL instance in SAP workstation
Hi Experts, I would to ask regarding the SQL connection of the workstations. After I installed the SAP client in the workstations using the B1_SHR folder from the SAP server, when I opened the SAP in the workstation, the Server available is only MSSQ
-
Elements 10 install problems !
I downloaded the trial version. and it worked fine. then I uninstalled it. I later bought the software at the store. When I use the cd to install it opens the installer then flashes to a sceen that askes me if I want to uninstall elements 10. No I do
-
anyone can tell how to use dos to run Java program? I learn Eclipse few month, so I dont know how to run java in dos. I did follow the install guide to set the PATH like that C:\Program Files\Java\jdk1.5.0_02\bin in "Path" in the User Variables but I