Client Copy help

Hi All,
I'm trying to do a client copy of my 000 client so that I can play around with CUA. When I go to do the local client copy it says :
Target client is productive and protected against
client copy.
Does this mean I can only do client copy on IDES systems? How can I do a client copy on my system? Thanks!

Hi!
Your messages sounds like you tried to overwrite client 000 - mixing source and target?
Don't change settings of client 000 - it's always good to know, where you can find correct, unchanged values (after playing a while and producing a big mess...).
Just choose a 'free' client as target, e.g. 100 (or whatever you like, but not 066).
Regards,
Christian

Similar Messages

Local Client copy - help needed

Hello ,
I have to perform a client copy without data.
Can you please let me know, which profile I should use ?
SAP_ALL All Client-Specific Data w/o Change Documents
SAP_APPL Customizing and Application Data w/o Change Docs
SAP_APPX SAP_APPL w/o Authorization Profiles and Roles
SAP_CUST Customizing
SAP_CUSV Customizing and User Variants
SAP_CUSX Customizing w/o Authorization Profiles and Roles
SAP_PROF Only Authorization Profiles and Roles
SAP_UCSV Customizing, User Master Records and User Variants
SAP_UCUS Customizing and User Master Records
SAP_UONL User Without Authorization Profiles and Roles
SAP_USER User Master Records and Authorization Profiles
Thanks in advance for your help!
I would vote for:
SAP_UCSV Customizing, User Master Records and User Variants
SAP_UCUS Customizing and User Master Records
Daniel
Edited by: Daniel_Bul on Mar 7, 2012 11:22 AM

Hi,
SAP_CUSX would be better if you dont want the same user master data in both the clients otherwise you can go ahead with SAP_UCSV .
Regards,
Nirmal.K

Logical system name to be updated while client copy--URGENT HELP REQUIRED

Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.

Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe

Need Help!! Errors during Local Client Copy

Doing a Local Client Copy and getting these error messages in the log:
Table Name       Component          Package
/1CN/CMFSAPH0FOR                    DDIC Error        (See SE14)
/1CN/CMFSAPH1FDT                    DDIC Error        (See SE14)
/1CN/CMFSAPH1FFX                    DDIC Error        (See SE14)
/1CN/CMFSAPH2TGR                    DDIC Error        (See SE14)
/1CN/CMFSAPH2TRM                    DDIC Error        (See SE14)
/1CN/CMFSAPH3TCT                    DDIC Error        (See SE14)
/1CN/CMFSAPH3TUS                    DDIC Error        (See SE14)
/1CN/CMFSAPH4TFX                    DDIC Error        (See SE14)
/1CN/CMFSAPH4TQU                    DDIC Error        (See SE14)
Then I go to SE14 then put the name of the tables then click CHECK >> DATABASE OBJECT and then as the result I get:
"Table is not created in the database"
If I go down to the database level and look within the Oracle database dba_tables the tables and objects exists within the database but SAP is unable to recognize them. All objects were imported with a Oracle Data Pump dump file and now I just need help in getting SAP to recognize the tables.
Edited by: Adam Gendle on Feb 19, 2010 12:29 AM

Hi,
Its showing inconsistency between ABAP Dictionary and the database.
Have you run Test-Run before performing actual client copy ?
Please check the Consistency of affected Tables.
SE11 -> Display Table -> Utilities -> Database Object -> Check
(check DB Object as well as Run time Object)
Please refer this [SAP Note 686357 - Table pool length incorrect after Unicode conversion|https://service.sap.com/sap/support/notes/686357] to get more information. The relevant solution is mentioned there if the pool tables having inconsistency with VARDATA field.
Also refer SAP Note 1171306 - Error with pooled tables when copying a client.
Regards,
Bhavik G. Shroff

Client copy error (URGENT HELP Required)

Hi all,
We did system copy of production system after that we were asked to do the client copy from 500 as source client but while performing this activity disp + work dispatcher is going in standstill mode and its turning yellow in color.
There is no error in developer trace and other logs.
Please suggest me the solution to resolve this problem as we have to finish this activity by today evening.
Thanks & Regards,
Prashant.

Hi prashant,
u checked the swap memory size.
Check ur disk sapca and also the log file folder. If it is full then
the dispatcher will not start because it can not write the log.
check the path
\usr\sap\sid\instanace\j2ee\cluster\server0\log
check this folder size if this folder size is more then remove the log
files from the archive folder which is a sub directory in log folder
copy the archives files in to a new disk and then delete from the
archive folder. Then try to start the SAP sytem .
Regards,
R.Suganya

Client Copy from BWP to BWT

I had a problem with my List Cube Transaction and for that reason, I had a look at the Infoprovider and also the Data Sources.
When tried to execute the infoproviders in LISTCUBE, the following messages are being displayed in BWT system:
1. Error reading the data of InfoProvider ZIP_RC_01
2. There is still no data source assigned to VirtualProvider ZIP_RC_01
But, when executed the same in BWD, then it is working fine.
I have checked the Data Sources in the R/3 Dev system and the DS has no problem. But, when I check the DS in the R/3 Prod (SS in BWT system), the following error message is displayed in the status bar:
"DataSource Z_IP_RC_DS_1 is not defined in the source system"
I thought, as the system says the Source system is not available, hence the problem in LISTCUBE and thought if we transport the DS again and then replicate in BW, then our problem would be resolved.
But, seems that even though the source system says "PRD300", if I look at SM59 it actually points to our QAS system. It says PRD300 because BWT is a copy down from BWP, and that's the source system we use - in other words the logical name is the same, but the actual servers are different.
In any case, the datasource is transported to our QAS enviroment.
So, once we do a client copy from Prod to Test, even the source systems get copied. If yes, then does it really affect in case of replications and transports???
I am really confused in this part...please explain.
Thanks & Regards

Hi,
It looks like the basis team, or whoever performed the Copy from production to QA box hasn't finished all the necessary Steps :
Main transaction to know:
SSC4 -> To create new client
SCCL -> Client copy within local system
SCC9 -> remote client copy
SCC3 -> display client copy log
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24c4e4ba111d189750000e8322d00/content.htm
http://www.sap-basis-abap.com/bc/client-copy-from-production-to-quality-server-to.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci552257,00.html
Probably sounds like transaction BDLS hasn't been done.

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?
Bob

Hello,
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 fails.

Remote client copy fails.
The error message and info is given below. Help me to proceed.
Client copy
The client copy you started has terminated
Client Copy could not start because of Repository differences
Diagnosis
The table definitions differ between the systems. These differences mean that a copy of the data can cause a data loss and system inconsistencies. Differences occur when further developments were not transported or were copied between different maintenance levels.
Procedure
Transport all the developments of table structures between the systems using the Transport Organizer and bring your system to the same development level.
It is observed that some tables are missing in the target system. How do I copy the table structures to the target system?
Thanks in advance

Hello Ashraf,
There are repository differences between you source and traget system.
If you want to get the list of repository differences, then run a RFC check before you execute remote clinet copy.
You have to then remove these repository differences before you start with the remote client copy.
to remove the difference you have to:
"Transport all the developments of table structures between the systems using the Transport Organizer and bring your system to the same development level" as mentioned above
I would recommend you to go for Export / Import rather than Remote client copy.
There are several advantages of export import method over remote clinet copy
Regards,
Ammey Kesarkar
'Award points for useful info'

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 (0x

Hi 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

Client copy Locked function module

HI,
I'm trying to make a client from client 400 to 420.
The problem is that the function module is locked by the current user (the same running the client copy); Then when It can't deletes the FM it states that it already exists:
"G_GLDB_POSTING_A already exists (include LGIVAU01)"
Afterwards the job gets cancelled due to a system exception ERROR_MESSAGE
The weird part is that it just happens for this client 420. There is also a copy from 400 to 410 and it works without a problem.
Any help would be greatly appreciated.

Hi,
You can check the client copy lock from SCC4 also, but it really matters if your client copy finished or not.
If you still see the client copy lock there then it seems your client copy is not finished properly. Try to login your new client 420 and start deletion using SCC5 and after that you can start/schedule new client copy during weekends.
Regards,
Manish

Error while doing client copy

Hi Gurus,
i have to copy my all data(all modules master data) from client 300 to 900 within the system. i have created a client 900 thru scc4, then logged in 900 with user sap* and passwd "pass".then sccl while scheduling this in background...i am getting a error window which as follows..it says for creation of RFC..
RFC Destination for client copy in systems with financials basis (FINBASIS) component.
The system could not find any suitable RFC destination for processing the client 300.
This note also appears if an RFC destination was found but this does not work.
0 RFC destinations: FINBTR@RPDCLNT300
0 Error text: 900
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 300).
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: 300
4.     Start the client copy again.
what i have to do..?? in which cleint i have to create RFC ..??pls help me out in this situation.
Thanks & Regards,
ACS

SOLUTION:
Login to client 300
Go to sm59, create rfc connection type 3, give the rfc destination : FINBASIS_300
Logon and security--> give user id and password (of any user in client 300)
create any service type of user:(user should be a service user or communication user so as to avoid password lock situation) in 300
Check Test connection: test ---à authorization test.
Login in to new client: 900
Run the tcode: FINB_TR_DEST
Click on new entries:
Give the client: 300 and destination as FINBASIS_300 and save .
Run Tcode: sccl make client copy

SWN_SELSEN not working in test client after client-copy

Hi all,
We are using extended notification without problem until test client was refreshed by client-copy from production client. In test client, report SWN_SELSEN did not generated notification even there are newly generated workflow items. Because of client-copy, I found that tables SWN_NOTIF, SWN_NOTIFTSTMP, SWN_SENDLOG, SWN_TIMESTAMPS are all empty in test client.
Please advise how to make report SWN_SELSEN back to work in test client. Thanks.
<< Additional information >>
(1) Run report SWN_SELSEN_TEST with test Case 5 - Simulate Send Only. After this, some entries were written to above tables. But test on new workflow item, the schedule report SWN_SELSEN still fail to trigger notification.
(2) Run report SWN_SELSEN_TEST with test Case 4 - Send One Message Only. It triggered notifications for all active workflow items and sent out several hundred emails including workflow item created in step 1. However, further test on new workflowitem, the schedule report SWN_SELSEN is still unable to trigger notification.
I think there may be something else missing, like the timestamp of delta. Please help.
Regards,
Donald

Hello,
I've experienced a few cases where stopping SWN_SELSEN and then restarting it helped to fill up SWN_TIMESTAMPS with proper values. How does that table look after you run it?
What is SWN_SELSEN_TEST?
Chck in SLG1 to get an idea of why it's not working. You can also run SWN_SELSEN in the foreground and debug it to see exactly where and why it goes wrong. Also check ST22.
regards
Rick Bakker
hanabi technology

Client Copy between unicode system and non-unicode system

Hello,
we have to build up a new system for japan. It is planned to install a new 4.7Ext200 unicode system and then make a client copy from a non-unicode 4.7Ext200 (language= german, english) system to the unicode system. I don't think that this is possible way, but I can't find information regarding client copies from non-unicode to unicode. I would advice the project to convert the existing non-unicode system to unicode, make a system copy for the new system and then install japan languages. Any information, which can help me.
Regards,
Alexander

Hi,
without conversion client copy is not possible
look at following
Re: Client copy between unicode and Non-unicode
regards,
kaushal

Data migration from one DEV(DE1) system to other DEV(DE2) BW system using client copy or client export import

HI SAP Gurus,
Please find the below details:
SAP NetWeaver 7.3
We have to copy all customized or developed BW objects like master data, DSO's , Infocubes , Reports etc.
We need only the design changes but not the data within the DSO or cubes that exist .
We have tried below procedure:
1) Taken export of DE1 source client 400 with profile SAP_CUST
2) Imported transports generated for above export into DE2 target client 350.
3) Executed transaction SCC3 and performed post processing, post processing was successful . Still we are not able to see DSO's, infocubes ,reports.
Please lets us know what we need to do to fulfill our requirement.
Thanks,
Avadhesh
+ 91 8095226536

Hi Basis,
Please refer to below documentation on how to perform system copy in BI systems
How to System Copy in SAP Business Intelligence System Landscapes (NW2004)
Post processing steps for SAP BW system copy or db copy
BI systems has mostly cross client objects. So client copy with SAP_CUST profile will not serve your purpose.
Hope this helps.
Regards,
Deepak Kori

Procedure to know client size, and client copy.

Dear Experts,
 I am new to client copy process.Please help me in some of my queries.The client which i want to copy is a customizing client (120) in development server.And new client to be created is also on development server itself.
1). How can I know the exact size of the client which i want to copy?
2). Will all the customizing done on the (120) client be copied to the new client created .
3). Will all the profiles and parameters be copied as the source client?
4). And Detailed process from client creation to client copy.
Please help me .
Thanks in Advance
Regards
Akif

Dear Umesh,
 As you told to add the space i did that .And started the client copy but it ended with 4 following errors:-
Table/Object
Component
Error
AGR_HIER
BC-SEC-USR-PFC
Write Error (See System Log)
DSYS_PHCONT_E_CD
PY-XX
Write Error (See System Log)
SOES
BC-SRV-GBT
Write Error (See System Log)
ZFX_BCBNR
DDIC Error (See SE14)
Please suggest what should be done of this errors.
And thx for ur total support.
Regards
Akif

Client Copy help

Similar Messages

Maybe you are looking for