ECC 6.0 Client copy
Hi all
Recently i Loded my system with SAP ECC 6.0 IDES. But Country Setting Screen, Tax procedures ( TAXINN, TAXINJ) are not activated. and also i am facing problem in activating New GL function.
If any body know the solution please share with me .
Thanks
Venkat.P
Hello
This is the issue with improper installation.
Request the basis to delete the client and re do afresh.
Reg
*assign points if useful
Similar Messages
-
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 -
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 -
Unable to find product categories after client copy
Hi all,
We have copied clients from an existing ones for both SRM and ECC. After client copy we have followed standard procedure after client copy i.e.
Run transcation BDLS
created new RFC connections
changed attributes using the Attributes replace report
created new distributon model
maintained CRM parameters
maintained new site attributes in SMOEAC transaction
maintained entries in table TWPURLSVR
however , when i try to create a shopping cart, I cannot see any product category. The extended attributes for product category point to new ECC client becuse we have run the attributes replace report.
however in the product category table , COMM_CATEGORY , the product categories listed are all for the old ECC client
When i tried to load the Object DNL_CUST_PROD1 using transaction R3AS in SRM and tried to pull from new ECC client , it is in runing status for a long time and new categories with new ECC backend reference are not being replicated in the SRM.
Can you tell me why this could be happening ? How can i get the product categories from new ECC backend into my client?
Regards,
Mangeshproblem solved
i was using wrong parameters in BDLS -
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 -
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 -
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. -
Client copy error:cannot open log:/w2k3-web53/sapmnt/trans/log/cc000007.ecc
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}. -
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 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 EismannHello,
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 -
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 -
Audit Issue in QA after system restore and client copy
Hi Experts,
We have an audit issue and need your advise on that.
Our QA system was audited and auditors were looking for the approval tickets on which a user was created. I found that several users that were not created in QA and do not even exist in QA have their change logs in QA showing that user was created.
I researched it and found the steps that Basis and DBA's do when creating a new QA client.
1. Basis export user master and authorizations using SAP_USER profile from the target QA environment.
2. Then DBA's restore the QA Environment from the Production Backup.
3. Basis import back the preserved User master and roles using SAP_USER profile.
But when reading about this profile, I came to understand that change documents ( USH* ) tables are not exported and imported back. So that is why we have change logs in our QA from Production system.
So my question is how to solve this issue, where Auditors look at the change documents in QA and ask for the documentation though in reality these change documents are coming from Production. Should we ask for DBA team to truncate USH tables or is there a client copy profile that saves the change logs that we can export and import back.Hi,
as you know the USH* tables belong to delivery class L. The tables in this class are never copied during client copy but you don't do client copy. Idea of deleting records from L tables after backup restore does not sound good because you will loose all data. As a workaround you could backup content of tables with delivery class L, export users SAP_USER, restore production backup, import users and import backup for tables with delivery class L. There is around 5000 L tables in ECC. Another approach could be to restore production on different box and do proper client copy to QA system.
Cheers -
BDLS or BDLSS after Client copy
Hi all,
I am currently working on two systems ..SRM and ECC 6.0.In SRM and ECC.We have 2 clients 100(Development) and 120(Customizing) in both the systems.We recently did a client copy of production to our development clients and I have one confusion regarding the LOGICLA SYSTEM UPDATE which is one of the madatory steps post client copy.
For the LOGICAL SYSTEM UPDATE,do we need to run the transaction BDLS or BDLSS??What is the difference between these 2 transactins?Also what are the advantages /disadvantages?
My BASIS guy told me that during our client copy,BDLS was automatically run.Surprisingly,although BDLS was run,the logical system entries are not yet updated!
Please advise.Hello,
You need to run BDLSS, which has enhanced functionalities of BDLS. Check the following link out:
[Conversion of Logical Systems|http://help.sap.com/saphelp_NW04s/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/frameset.htm]
For your question related the difference between BDLS and BDLSS, from the above link:
As of NetWeaver 6.20, SAP provides the option to convert logical systems using a new transaction that is more transparent and easier to use. Transaction BDLS has been used for this purpose until now. This transaction remains unchanged, and is enhanced by the new transaction BDLSS. In contrast to BDLS, in BDLSS logical systems can also be converted remotely in all partner systems.
Regards,
Shival
Maybe you are looking for
-
Hi, I've just rented a movie, which claims its going to take 14 hours to download. Its still at it after 1 hour. To make matters worse, the 48 hours it gives you to watch it has already started and charged me an hour. There was a message to say I cou
-
Resizing a table in Adobe form J_3R_INV1_CONTEXT
Hi, I'm quite new with Abobe forms and stuck with a task. It might seem simple, but though in this J_3R_INV1_CONTEXT form. There's a table (containing 13 columns) on the second page, and cc 1 cm is cut from it's right side, during printing. I can't m
-
After I did the security update to 10.5.1, the Dock process has started acting strangely on my MacBook. About once every 10 seconds or so, the Dock suddenly takes >50% of the CPU which causes the system to hickup and sometimes causes audio or video t
-
I am facing issue with respect to renaming a file under project explorer. Steps: 1. Open a Project 2. Add a VI with file name as "DeInitialize" 3. Right Click and select Rename 4. File Dialog opens to enter new name 5. Enter "Deinitialize" (Only chan
-
In-App purchases from App made with Flash?
Hey everyone! So basicly I'm working on this game project and I've got a distributor in Germany who requests me to implement an in-App purchase within this game I've developed in Flash CS5.5. In the developer section at apple's website I can't get in