SPRO Setting in client copy.

I had Copy client from production to devlopment.
During the process all transection are get copy but while vieving or modifying i come to know that all SPRO master setting is missing in client on devlopment server.
Say my production client is 300 and i had created client on 222.
Kindly help on this issue.

Hi,
That depends upon profile, which were selected in copying.
Regards
Nick Loy

Similar Messages

Setting up a new client. Is "client copy" necessary?

Hi,
I just installed NSP. As I don't want to work in client 000, I have created a new development client 100.
Our internal notes suggest that I must always copy client 000 to client 100. However, this takes up a few hours and chews up another 30G of harddisk space.
This is a freshly installed system just for testing. I am wondering if "client copy" is really a must or just a suggestion. What exactly do I lose if I don't do a client copy?
Thank you in advance for your help.
Peter

Can someone please help me? I still haven't received a good reply on how important it is to do a client copy.
In my test case, I like the base client 000 to have nothing in it. I then would like to set up two totally different companies as two different clients. These companies have nothing in common. I don't see why I really should do a client copy.
Regards,
Peter

Client Copy back-end system

Hi Guys,
We have made a client copy of the back-end system of SRM (SRM 5.0). Only the back-end and not SRM has been copied.
After replication all the master- and customizing data again to SRM from the 'new' back-end I have found an issue with updating the suppliers.
It seems that I can not remove old business partners from SRM with BUPA_TEST_DELETE if these are used already in SC's. However the new copy of the back-end system has completely different suppliers we need to use in SRM. This causes for an inconsistency with the supplier numbers, as we want to keep the R/3 numbers in SRM.
Does anyone has a good idea how to proceed? That is, how can I remove the business partners (suppliers) in SRM which were used before the client copy of R/3, so that I will be able to completely get all the relevant 'new' vendors from the R/3 system after the client copy.
When I execute BUPA_TEST_DELETE it will end up in error saying the suppliers can not be removed. Do I need to archive all the old documents (SC & PO) before I can remove all vendors in SRM, or is there a way to force the removal of all the business partners from before the back-end client copy?
Thx.
Skander

Hi,
I already figured out how to solve the issue.
For anyone who wants to know how to:
-First clear the vendor groups in the vendor hierarchy; do not renove the root node
-Then run BBPGETVD which will get you the new vendors from the back-end; for me only role LF for suppliers.
-Then run BBPUPDVD which will update all the fields for the old business partner numbers in SRM which were used in documents, and replicated from the old back-end system.
In my case I had to play a litlebit with the setting 'only creditors', to update BP numbers which were not suppliers in the new back-end.
After performing these steps everything should be fine.
So it's perfectly possible to make a client copy of only the back-end system without copying SRM (in the classic scenario that is).
Rgds,
Skander

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

Unable to login to IDES system after client copy

Hi guys
the IDES system which i was using was working fine. I was trying CLient copy today morning and was trying to create a new client in the IDES system.
The client copy failed due to a shortdump in the process.
Now i am unable to login to the client 800 as it says the user password is incorrect.
How do i get back my 800 client? is there a way to get back the client 800 or do i have any other optionn to re-set the password without logging on to the client?
i do have access to client 000.
please guide me what should i do? i need the client 800 back and should be able to login too.

hi,
i cannot login to client 800. I need to login first in the client 800 to go to su01 to re-set the password.
I want to login to client 800 which i am unable to do as a result of client copy. So the other option i am looking at is reset the password from client 000.
anyways thanks for your inputs
Hi guys,
any idea?
Edited by: Workflow learner on Jun 2, 2008 10:48 AM

EBP Logical system after client copy

Hi Friends,
We did a client copy for our EBP system from the production system.
Now when I access the system to create invoice, the below error
prompted.
Error message
Error calling META BAPI META_CALCULATE_TAX
Error occurred calling META_BAPI_DISPATCH
In the debug mode for F/M META_BAPI_DISPATCH , I could see the logical system
still pointing to the live system.
So far Basis already changed all the logical system entries.
Hope someone could give some hint to solve the problem
Many thanks
Mike

Dinesh,
We are using SRM Standalone. No sync with backend product categories. In the debug mode I could see the system getting the logical system = "production sys" for business object BUS2205 (invoice).
Belief there is some setting for logical system still need tobe changed.
Hope you could give some hint.
Many thanks.
Mike.

Client copy/Syatem Copy

Hi,
What is the difference between client copy and system copy.
and when client copy is don eall the Logical system names are replcec with the new logical system name in SPRO-G/L Account setings.How to prevent the same.
Thanks,
Venky

not answered

Client Copy SRM from prod to dev -Urgent

We have done the client copy and trying to change the logical system names. We are in the process of changing the SPRO-> Account Assignment -> Define G/L Account for Prod Cat and A/C Assignment Cat
We want to change the source system but it is not enabled even in change mode. Only the G/L Account is enabled for change.
We will have to change in 2 to 3 more places
How do others do when it comes to client copy and change of logical names. Use BDLS or make is it because we have some missing roles hence the field is protected?
Any help/
Thanks

Hi
This is standard SAP functionality. The table which holds the data for
"Define G/L Account for Prod Cat and A/C Assignment Cat" is BBP_DET_ACCOUNT and it holds data in similar manner.
Since other fields except the GL account, are key fields, these are not coming as enabled in change mode. There is no problem with any settings as such.
Since you want to make chnages in 2 to 3 more places(better approach using create template functionality, firstly copy the existing entries and make changes to them and finally, delete the existing extra unrequired entries in the table.
1. Either using the SPRO path
SPRO-> Account Assignment -> Define G/L Account for Prod Cat and A/C Assignment Categories
2. Or using SM30 transaction for the table - BBP_DET_ACCOUNT table
Hope this will definitely help. Do let me know.
Regards
- Atul

R/3 Client Copy : Problem in BI.

Hi All,
Our Basis team have done the R/3 production copy to R/3 quality recently. These has created the problem in my BI development system.
We have a working BI development system which is connected to R/3 Quality as well as R/3 development and all standard data sources were succesfully implemented in BI dev from R/3 Quality previously.
After this Client coply i could not able to see any data source related to R/3 quality in my BI Dev system.
I have checked the RFC connection and it is OK.
I have checked the R/3 Quality also. All my CMOD routines have been removed.
I could not able to see data sources in RSA6 also.
As per my understanding this should not happen after client copy.
I do not want to retrasport all the tasks from R/3 dev to R/3 quality again.
Please suggest .
Regards,
Macwan James.

Hi,
Once you copy/refresh the R/3 Qty with R/3 Prod you loose all Transports and settings, you need to re-import the TRs from R/3 Dev to R/3 Qty. Before that you need to set all settings between BW qty and r/3 qty.
See SAP notes:
How to System Copy in SAP Business Intelligence System Landscapes (NW2004) "Search Document
Note 325470 - Activities after client copy in BW source systems
Note 325525 - Copying and renaming systems in a BW environment
Note 886102 - System Landscape Copy for SAP NetWeaver BW
Note 996238 - Dump 'RFC connection error' after BW system copy
Note 1333302 - Special procedure for BW system copy
SAP NetWeaver - BI Systemcopy Abap "Search Document
Thanks
Reddy

Parallel process Before Remote client copy

i m going to perform remote client copy from production to sandbox how to enable parallel processing before that .
and its is hugh client and i want to do it fast can i start it in Foreground and if yes what parameter i have to set to what value to do it in foreground

Hi,
As far as i know there is no tcode where you can set parallel processing, you can just select remote cleit copy or local client copy this methods have parallel processing .
Regards,
Vamshi.

Cannot Create Client Copy

Hi All;
I am setting up CRM on AIX with DB2, and am in the process of creating my Client 300. I was able to create the client in scc4, logged out of the system and then logged into the new 300 client with SAP*. When I tried using the SCCL to copy from 001 to 300 I get the following error
"A client copy run is currently active" If I click on the check mark, it takes me back to the main screen. If I try to display the client information with SCC4, and select edit, I get
"System error: Unable to lock table/view T000" Message no SV050
A system error occurred in lock administration. The data could not be
locked as requested.
Not finding much help with googling the error, so I am at a loss for now.
Any suggestions would be appreciated.

Dear Les,
I am facing the same error. Could you please pass the solution you have received?
I would appreciate it.
Latest Update:
Ask yourself the following questions:
1. Did you modify any profile parameter before starting client copy?
2. Check whether sappfpar pf=<Instance Profile> check at OS level, this should give you if shared memory is sufficient or not.
3. Are you able to Launch RZ10?
4. Are you seeing errors in SM21 similar to
9:28:52 DIA 002 000 SAPSYS GE F Error setting up the lock table
9:28:52 DIA 002 000 SAPSYS GZ Z > Initialization of Shared Memory enxxmini584#
9:28:52 DIA 002 000 SAPSYS GZ Z > ShmCreate(34, 20480000, SHM_CREATE, ..) rtc=1 enxxmini586#
9:28:52 DIA 002 000 SAPSYS GE I Enqueue: Initialization error
9:28:52 DIA 002 000 SAPSYS GE F Error setting up the lock table
9:28:52 DIA 002 000 SAPSYS GZ Z > Initialization of Shared Memory enxxmini584#
9:28:52 DIA 002 000 SAPSYS GZ Z > ShmCreate(34, 20480000, SHM_CREATE, ..) rtc=1 enxxmini586#
9:28:52 DIA 002 000 SAPSYS GE I Enqueue: Initialization error
9:28:52 DIA 002 000 SAPSYS GI 0 Error calling the central lock handler
9:28:52 DIA 002 000 SAPSYS GI 4 > Dequeue All call failed
9:28:52 DIA 002 000 SAPSYS GE F Error setting up the lock table
9:28:52 DIA 002 000 SAPSYS GZ Z > Initialization of Shared Memory enxxmini584#
9:28:52 DIA 002 000 SAPSYS GZ Z > ShmCreate(34, 20480000, SHM_CREATE, ..) rtc=1 enxxmini586#
9:28:52 DIA 002 000 SAPSYS GE I Enqueue: Initialization error
9:28:52 DIA 002 000 SAPSYS GI 0 Error calling the central lock handler
9:28:52 DIA 002 000 SAPSYS GI 4 > Dequeue All call failed
9:29:18 S-A 000 zdcadm E0 2 Program rslgsend Ended: o.k., SIGINT
I would suggest you taking a good look at the profile parameters changed or go back to your working Instance profile. This should resolve the issue.
Regards,
Ramanathan EKAMBARAM
Edited by: Ekambaram Ramanathan on May 28, 2009 4:49 AM

Unable to do the Local Client Copy

Hi, Experts
I have created a new client, and i have logged on that client and doing the local client copy. When I see the client copy log the client copy got cancelled.
When i check the log i am getting a error saying "The System's Time Zone Cannot be Determined. Enter it Using STZAC."
The time zone maintained in INDIA.
Thanks & Regards

Hello
Perform some checks
Please make sure that SAP time is same as the time on the operating system
Also make sure that u maintain time in the original client i.e the client which u r copying
Also I would recommend that you first delete the new client,then maintain all setting for time zone through the note 667169 and then again try client copy
hope it help
Rohit

Local client copy of 000 after installation fails

I'm trying to install XI. I installed Web AS 6.40 (from the SR1 installation) ABAP stack. Before installing the Java Add-In I need to make a copy of client 000. I login using client 000 and SAP*, goto SCCL and without even getting to the transaction I get the following error message:
"Target client is prodductive and protected against client copy."
(It's message no. TA133) -- I got into SCC4 (like help suggested) and the only users I have are 000 and 066 ("Test EarlyWatch Profiles"). 000 is set to "SAP Reference", not "Productive".
The thing is I never even get to enter the target client; I never get to enter anything in the transaction, it throws me out immediatly.
I managed to get a step further by following these steps:
1. Using SCC4 I created a copy 000 (001)
2. Logged out from 000
3. Logged in using 001 and SAP*/PASS
4. Went to SCC4, deleted the 001 entry and saved (if I don't delete it I get the same error as before)
Then when I went to SCCL (while still logged in with the deleted 001 client) I got the transaction. It put 001 as the target (which is fine by me), I selected a copy profile but and selected 000 as the source -- but when I tried to execute I got the same problem as before.
(I'm sure it's apparent that the whole ABAP world is new to me this is just me trying to install an XI test system in the office.)
What am I missing here?
Thanks,
Alon.

hi alon,
what do you mean with 1) (copy 000 to 001)?
just create a new client in SCC4, make sure that the parameter "client role" isn't set to "productive".
log on as sap*/pass in the new client and use SCCL to make a copy.
kr, achim

Local client copy Error

I have fresh installed ECC 6.0 with HP UX. I want to do local client copy.but it give error
lient copy from 03.02.2009 23:20:18
ystem ID............................ QAS
arget client........................ 900
/3 Release.......................... 700
Basis Support Package...............SAPKB70009
ost................................. quality
tart in background............. .....X
ser................................. SAP*
arameter
ource client........................ 000
ource client user masters............000
opier profile:.......................SAP_ALL
able selection
ustomizing data .....................X
ith application data................ X
nitialize and recreate......... X
hange documents are not copied
est mode (without database update).. R
thanks
Manu

thanks for your reply.I have set my INDIA time in 001
But during client copy it gives system Log
Details Page 2 Line 9 RSLG0001 - SAP Analysis of the Central System Log       1
Time     SAP instance   Type Nr Clt User TCode Program Terminal Package Grp N Text
18:16:23 quality_QAS_00 BTC 008 900 SAP*                        SBAC    BY 4 Database error 24909 at SEL access to ta
Details
Recording at local and central time........................ 05.02.2009 18:16:23
Task...... Process                      User...... Terminal Session TCode Program Cl Problem cl         Package
04523      Background Processor No. 008 SAP*                      1               K SAP Web AS Problem SBAC
Module nam Line SQL functi Table Name
dbrepo     2655 SEL        REPOLOAD
Documentation for system log message BY 4 :
After the attempt to access a database table the database system has
returned an error code which indicates that the operation concerned
could not be performed successfully.
The text of the system log message shows the error number, an
identification of the operation and the name of the table concerned.
The following abbreviations are used for the database operations:
CLC - Closing a database cursor
CRT - Creating a table on the database
DEL - Deleting table entries
EXE - Immediate execution of a database operation
FET - Reading one or several records of a database cursor
INS - Inserting one or several records into a database table
PRE - Executing a PREPARE operation
SEL - Executing a database selection
UPD - Changing one or several records in a database table
echnical details
File Offset RecFm System log type    Grp N variable message data
   1 135000 g     Database SQL Error BY 4 24909 SELREPOLOAD                                   dbrepo 2655
Plesae suggest
RAJ

Local Client Copy Error in Post-Processing

Hello All,
We are facing issues in local client copy on SRM 5.5 system Basis 700 SP19 with Oracle Db. I have ran the same twice. Also performed the update statistics on db.
All the tables are getting copied but the error or warning is occuring in "Post-Processing" phase.
Table Name Component Package
/SAPCND/CC_GROUP_WS_NG AP-PRC-CON Post-Processing Required
Following entires in the file logs are displayed:
Begin of GEN_STATUS Update
Generation of working set structure /1CN/WS_ID_200MOM_TAX started.
No fields in structure /1CN/WS_ID_200MOM_TAX
Postprocessing necessary when upgrade has been completed
Generation of working set structure /1CN/WS_IS_200MOM_TAX started.
No fields in structure /1CN/WS_IS_200MOM_TAX
Postprocessing necessary when upgrade has been completed
Generation of working set structure /1CN/WS_ED_200MOM_TAX started.
No fields in structure /1CN/WS_ED_200MOM_TAX
Postprocessing necessary when upgrade has been completed
Generation of working set structure /1CN/WS_ES_200MOM_TAX started.
No fields in structure /1CN/WS_ES_200MOM_TAX
Postprocessing necessary when upgrade has been completed
Generation of working set structure /1CN/WS_UI_200MOM_TAX started.
No fields in structure /1CN/WS_UI_200MOM_TAX
Postprocessing necessary when upgrade has been completed
Begin of GEN_STATUS Update
Its help says "Postprocessing necessary when upgrade has been completed. For a more detailed description, see the previous message /SAPCND/GENERATOR381.Message no. PU139"
Can anyone guide me the best way forward.
Thanks,
Antarpreet

Hello Gagan,
I am facing the errors in table /SAPCND/CC_GROUP_WS_NG belonging to component AP-PRC-CON. It says post processing required.
The oss note says about component FINB-TR-DERIVATION.
I am not sure whether it is good to run the steps as mentioned in oss note 1235955.
Thanks for your response and look forward to further help.
Regards,
Antarpreet

SPRO Setting in client copy.

Similar Messages

Maybe you are looking for