BI - Client copy 000, 001 or neither

After install SAP Netweaver 7.0 BI ABAP+JAVA what shoud we do about client?
In BW we can't have more than one client so I think this is the same for BI. If the system start with two clients (000 and 001), should we do a client copy? If yes, which of them?
Best regards

HI
i think bi client my best suggetion is to take
001

Similar Messages

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

Solution Manager 4.0 client copy

Hi all,
We have installed solution manager 4.0 SP 12. We have also done a client copy from 001 to 100 in order to work exclusively in the client 100. I have also changed the client reference in RSADMINA table and the UME from 001 to 100. Finally, when I wanted to implement Solution Manager Diagnostics, I have run the "Setup Wizard" and it created automatically the RFC destination "WEBADMIN" but with client 001. I tried to check everywhere where the old client is still mentioned in both ABAP and Java parts, but no way. Could you tell me please if I forgot something to do after the client copy? Where can I change definitively the reference of the old client?
Thanks in advance for your action.
Regards,

Did you use client 000 as your source client (001 as the user master)? You should not client copy from source 001 as of solman 4.0.
Reference point 6 of note: 1041351
https://service.sap.com/sap/support/notes/1041351
Thanks.
Edited by: Phil May on Aug 26, 2008 7:07 PM

Local client copy cancelled

hi experts
i installed ECC-6.0 with oracle10.2.0.1.after installation i applied all patches (basis-14,abap-14,bw-16,appl-12fin_basis12)then i scheduled client copy 000 to 101 some time it was canceled the corresponding log is
Client copy from 29.10.2008 11:39:54
System ID............................ KDV
Target client........................ 101
R/3 Release.......................... 700
Basis Support Package...............SAPKB70014
Host................................. KARVY-DEV
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
Test mode (without database update).. R
Start analysis of system 11:39:54
/GC1/CC_EXIT_CLIENT_DELETION executed         0(        0) entries copied
Exit program /GC1/CC_EXIT_CLIENT_DELETION successfully executed 11:40:09
Start of exit /SAPCND/CC_COND_TABLE_MATCH
/SAPCND/CC_COND_TABLE_MATCH executed         0(        0) entries copied
Exit program /SAPCND/CC_COND_TABLE_MATCH successfully executed 11:40:10
Client Copy called in Test mode -> Return.
/SAPCND/CC_GROUP_WS_AA executed         0(        0) entries copied
Exit program /SAPCND/CC_GROUP_WS_AA successfully executed 11:40:10
Start of exit /SAPCND/CC_INCLUDE_TABLES
End of exit /SAPCND/CC_INCLUDE_TABLES
/SAPCND/CC_INCLUDE_TABLES executed       108(        0) entries copied
Exit program /SAPCND/CC_INCLUDE_TABLES successfully executed 11:40:11
ADDR_CLIENTCOPY_SELECT_TABLES executed        26(        0) entries copied
Exit program ADDR_CLIENTCOPY_SELECT_TABLES successfully executed 11:40:12
EFG_FORM_CC_EXIT_BEFORE executed         0(        0) entries copied
Exit program EFG_FORM_CC_EXIT_BEFORE successfully executed 11:40:13
Start of deletion methods for client 101
Table K9RKI48050002 is deleted, not copied
Table K9RKI48050003 is deleted, not copied
Table KX9RABA0000108 is deleted, not copied
Table TABADRH is deleted, not copied
Table TABADRS is deleted, not copied
Table TABADRSF is deleted, not copied
Table TABADRST is deleted, not copied
Table TABADRX is deleted, not copied
Table UCF001C is deleted, not copied
Table UCF001G is deleted, not copied
Table UCF001T is deleted, not copied
Table UCF0020 is deleted, not copied
Table UCF0021 is deleted, not copied
Table UCF0022 is deleted, not copied
Table UCF0023 is deleted, not copied
Table UCF002C is deleted, not copied
Table UCF002T is deleted, not copied
Table UCF0032 is deleted, not copied
Table UCF003C is deleted, not copied
Table UCF003G is deleted, not copied
Table UCF003T is deleted, not copied
Table UCF0040 is deleted, not copied
Table UCF0041 is deleted, not copied
Table UCF0042 is deleted, not copied
Table UCF0043 is deleted, not copied
Table UCF004C is deleted, not copied
Table UCF004T is deleted, not copied
Table UCF1000 is deleted, not copied
Table UCF1001 is deleted, not copied
Table UCF1002 is deleted, not copied
Table UCF2300 is deleted, not copied
Table UCF2301 is deleted, not copied
Table UCF2310 is deleted, not copied
Table UCF2311 is deleted, not copied
Table UCF3000 is deleted, not copied
Table UCF3001 is deleted, not copied
Table UCF3010 is deleted, not copied
Table UCF4000 is deleted, not copied
Table UCF4001 is deleted, not copied
Table UCF4002 is deleted, not copied
Table UCF5000 is deleted, not copied
Table UCF5001 is deleted, not copied
Table UCF5002 is deleted, not copied
Table UCF5010 is deleted, not copied
Table UCF600C is deleted, not copied
Table UCF6010 is deleted, not copied
Table UCF6020 is deleted, not copied
Table UCF6030 is deleted, not copied
Table UCF6050 is deleted, not copied
Table UCF6100 is deleted, not copied
Table UCF6110 is deleted, not copied
Table UCF6120 is deleted, not copied
Table UCF6130 is deleted, not copied
Table UCF6140 is deleted, not copied
Table UCF6150 is deleted, not copied
Table UCF6160 is deleted, not copied
Table UCF6170 is deleted, not copied
Table UCF6180 is deleted, not copied
Table UCF6200 is deleted, not copied
Table UCF620C is deleted, not copied
Table UCF620T is deleted, not copied
Table UCF6210 is deleted, not copied
Table UCF6300 is deleted, not copied
Table UCF6310 is deleted, not copied
Table UCF7100 is deleted, not copied
Table UCF7101 is deleted, not copied
Table UCF7102 is deleted, not copied
Table UCF7110 is deleted, not copied
Table UCF7300 is deleted, not copied
Table UCF7400 is deleted, not copied
Table UCF7410 is deleted, not copied
Table UCF7500 is deleted, not copied
Table UCF900C is deleted, not copied
Table UCF9010 is deleted, not copied
Table UCFE01T is deleted, not copied
Table UCFE020 is deleted, not copied
Table UCFE02T is deleted, not copied
Table UCFE03G is deleted, not copied
Table UCFE03T is deleted, not copied
Table UCFE04G is deleted, not copied
Table UCFE04T is deleted, not copied
Table UCFE050 is deleted, not copied
Table UCFE05G is deleted, not copied
Table UCFE05T is deleted, not copied
Table UCFE060 is deleted, not copied
Table UCFE06G is deleted, not copied
Table UCFE06T is deleted, not copied
Table UCFE070 is deleted, not copied
Table UCFE080 is deleted, not copied
Table UCFE081 is deleted, not copied
Table UCFI00C is deleted, not copied
Table UCFI10T is deleted, not copied
Table UCFI200 is deleted, not copied
Table UCFI210 is deleted, not copied
Table UCFT000 is deleted, not copied
Table UCFT001 is deleted, not copied
Table UCFT002 is deleted, not copied
Table UCFV000 is deleted, not copied
Table UCFV200 is deleted, not copied
Table UCFV201 is deleted, not copied
Table UCFV202 is deleted, not copied
Table UCFV20G is deleted, not copied
Table UCFV21G is deleted, not copied
Table UCFV21T is deleted, not copied
Table UCFV220 is deleted, not copied
Table UCFV22T is deleted, not copied
Table UCI1101 is deleted, not copied
Table UCI1201 is deleted, not copied
Table UCI2100 is deleted, not copied
Table UCL2011 is deleted, not copied
Table UCL201G is deleted, not copied
Table UCL201T is deleted, not copied
Table UCM0010 is deleted, not copied
Table UCM0011 is deleted, not copied
Table UCM0012 is deleted, not copied
Table UCM0013 is deleted, not copied
Table UCM0014 is deleted, not copied
Table UCM0015 is deleted, not copied
Table UCM0016 is deleted, not copied
Table UCM001T is deleted, not copied
Table UCM002C is deleted, not copied
Table UCM002T is deleted, not copied
Table UCM0030 is deleted, not copied
Table UCM0031 is deleted, not copied
Table UCM0032 is deleted, not copied
Table UCM0033 is deleted, not copied
Table UCM003C is deleted, not copied
Table UCM003T is deleted, not copied
Table UCM1000 is deleted, not copied
Table UCM1001 is deleted, not copied
Table UCM100G is deleted, not copied
Table UCM100T is deleted, not copied
Table UCM600C is deleted, not copied
Table UCM600T is deleted, not copied
Table UCMA100 is deleted, not copied
Table UCMA101 is deleted, not copied
Table UCMA10C is deleted, not copied
Table UCMA10T is deleted, not copied
Table UCMI100 is deleted, not copied
Table UCMI10C is deleted, not copied
Table UCMI10T is deleted, not copied
Table UCMI200 is deleted, not copied
Table UCMI210 is deleted, not copied
Table UCMI220 is deleted, not copied
Table UCMT010 is deleted, not copied
Table UCMT01C is deleted, not copied
Table UCMT01T is deleted, not copied
Table UCMT100 is deleted, not copied
Table UCMT10C is deleted, not copied
Table UCMT10T is deleted, not copied
Table UCMV01T is deleted, not copied
Table UCRX01C is deleted, not copied
Table UCRX02G is deleted, not copied
Table UCS0100 is deleted, not copied
Table UCS0102 is deleted, not copied
Table UCS0103 is deleted, not copied
Table UCS0104 is deleted, not copied
Table UCS0105 is deleted, not copied
Table UCS0106 is deleted, not copied
Table UCS0107 is deleted, not copied
Table UCS0108 is deleted, not copied
Table UCS010T is deleted, not copied
Table UCS0110 is deleted, not copied
Table UCS01A0 is deleted, not copied
Table UCS01A1 is deleted, not copied
Table UCS01A2 is deleted, not copied
Table UCS01A3 is deleted, not copied
Table UCS020T is deleted, not copied
Table UCT100G is deleted, not copied
Table UCT100T is deleted, not copied
Table UCT101C is deleted, not copied
Table UCT101T is deleted, not copied
Table UCT2001 is deleted, not copied
Table UCT200G is deleted, not copied
Table UCT200T is deleted, not copied
Table UCT2010 is deleted, not copied
Table UCT2011 is deleted, not copied
Table UCT2012 is deleted, not copied
Table UCT2013 is deleted, not copied
Table UCT2014 is deleted, not copied
Table UCT2015 is deleted, not copied
Table UCT2016 is deleted, not copied
Table UCT3000 is deleted, not copied
Table UCT300G is deleted, not copied
Table UCT4000 is deleted, not copied
Table UCT400G is deleted, not copied
Table UCT8000 is deleted, not copied
Table UCT800G is deleted, not copied
Table UCT8010 is deleted, not copied
Table UCT8011 is deleted, not copied
Table UCT8012 is deleted, not copied
Table UCT8013 is deleted, not copied
Table UCT8014 is deleted, not copied
Table UCT8015 is deleted, not copied
Table UCT8016 is deleted, not copied
Table UCT801G is deleted, not copied
Table UCT801T is deleted, not copied
Table UGMD_BACK is deleted, not copied
FINB_TR_CC_EXIT executed       212(       13) entries copied
Exit program FINB_TR_CC_EXIT successfully executed 11:40:22
Exit program CLIENTCOPY_SELECT_TEXTID_ALL successfully executed 11:40:23
what is the solution for this

Hi,
Ho, what u r planning to do.Did u take online or ofline backup before u applied SP.
If you took better you restore.
One think, did you check the tablespace of your system..
if not chk it?
Regards
MLN

Which client should be use 000 or 001 for Client Copy

Hi,
Which client we can use 000 or 001 for fresh Client Copy.
Also what is the diff. b/w 000 and 001 client and its uses...
Please suggest.

Hi
Always use client 000, except for solution manager systems.
Best regards
550894 - CC-ADMIN: Setting up a new client
Always use client 000 as a template, and never client 001. (A known exception is the SAP Solution Manager.)
Do not copy any application data from client 000 because the consistency of data and the number ranges cannot be guaranteed.
Only client 000 is populated with upgrades, Legal Change Packages, Support Packages, language imports and so on with new Customizing so that it always contains the current sample Customizing. This is why it is also so important that the copy is only carried out after the system is updated. Client 001, on the other hand, is obsolete. It serves only as a sample client and may be deleted at any time.

Client Copy - Which source client 000 or 001?

I have a new SAP Netweaver 2004s SR1 ABAP+JAVA system with the following usage types:
SRM App
SRMLac
AS Java
AS ABAP
DI
MI
All the post-installation steps have been completed (including the CTC template configurations for DI and MI). The Java, DI, and MI have been configured against client 001. Now I want to create a new production client. The J2EE_ADMIN and users associated with DI and MI exist in client 001.
I want to create a new production client 010. Should I copy the users (SAP_USER) from client 001 and the customizing data (SAP_CUST) from client 000? Or, can I copy everything from client 001? There is a lot of conflicting information in the SAP Notes in regard to which source client to use.

You should not use a transport of copies for table USR02. Use client copy profile SAP_USER or SAP_UONL (without authorization profiles and roles).
And you should never copy customizing from client 001 to build up a new client. 001 happens to be a ordinary customer client which does not get supplied with changes SAP delivers after the release date. New SAP Netweaver 2004s installations use client 001 to file the user masters needed for the JAVA part. But this does not change the fact that client 001 is a customer client and should not be used as a template.
For local client copies you could use copy profile SAP_UCUS with source client 000 and source client user master 001 in one step. This has the same result as a client copy with SAP_CUST from 000 and SAP_UONL from 001 (i.e. thet authorization profiles and roles come from 000, when you need them from 001 you can either copy the missing individually or use SAP_ PROF in a separate step).

Client 000, 001 and 066

Hi everyone,
Pretty new to SAP.
I am struggling to find answers to the following questions:
How do you use client 000, 001 and 066?
Apart from initial installation and support (066) can theses clients be used in development, testing and production environements?
Can 000 and 001 be used as working clients or should they only be used as template?
What should their configurations be when using SCC4 for each system inthe landscape: DEV, QA and PROD (and Solution Manager)
From a security point of view, once SAP*, DDIC have been secured should they be any other users (Dialog, System) in these clients?
Sorry quite a few questions but if anyone could give me direction as I am trying to understand if some of our current settings are correct and if not why.
Thank you

Hi Corinne,
Even though it is a very basic question, it is very essential to understand and find an answer to your questions.
Client 000, 001 and 066 are (as you know) standard clients thats pre-built when you install SAP.
"Apart from initial installation and support (066) can theses clients be used in development, testing and production environements?"
Answer: No, they cannot be used for development, testing or production environments. When I say, "they cannot", I mean they are not supposed to be used.
"Can 000 and 001 be used as working clients or should they only be used as template?"
Answer: Client 000 is basically used as working client only when you do support pack upgrade or ABAP load generations (SGEN) and implementing additional languages, etc. Otherwise, client 000 should not be used as a working client. The same applies to client 001. But the only exception with 001 is, with Solution Manager, 001 will be your working client. You will do all configurations and obtain support from SAP through this client. With other Systems like BW and CRM, this client (001) will not be a working client.
"What should their configurations be when using SCC4 for each system inthe landscape: DEV, QA and PROD (and Solution Manager)"
Answer: In the production system - "Changes and Transports for Client-Specific Objects" should be set to "No Changes allowed". "Cross Client Object Changes" should be set to "Changes to Repository and Cross-Client Customizing Allowed". "Protection: Client copier and comparison Tool" must be set to "Protection Level 1: No Overwriting". Same applies to Quality System and Development System. These are by-the-by default settings also when you install the system.
"From a security point of view, once SAP*, DDIC have been secured should they be any other users (Dialog, System) in these clients?"
Answer: Once you install the system, you must first make a copy of DDIC to any user you create in your name or any standard name. Never use DDIC when you do initial settings after the installation.
The following link might be of some help to you.
http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/c8189452c511d182c50000e829fbfe/frameset.htm
Hope this helps.
Thank you.

Transfer Users from Clients 000, 001 & 066 Into CUA

I have CUA setup and currently I have all clients in all systems in CUA except for clients 000, 001 & 066. My first thought is to add these clients to CUA and tranfer users sap* & ddic. It seems to be a good way to make sure the 2 accounts passwords are easily changed and managed across the board. I already have trusts to all of the systems so it would be very easy to bring in these clients without much work. Are there any downsides to bringing in these clients and transferring sap* & ddic?

Hi Robert,
Here is my opinion :
I, personally, do not feel that activating CUA for 000, 001, 066 is a good idea. I would consider other options then CUA to ease 000, 001, 066 maintenance. If, for some reason, I have to use CUA for 000, 001, 066, I would create a specific client in a central CUA for management only these three clients but not the others.
Regards,
Mike

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

Post-install of SSM 4.0 and client-copy

We finished the installation of Sol. Man. 4.0 on a linux/oracle platform. At what point in the post install do we do the client copy of client 000 for data and client 001 for users to a new client? Before, during or after all the img config in 000?
thanks in advance,
Steven McElwee, Duke University
PS- Sap's install docs for SolMan 4.0 leaves much to be desired ...

Well, we had a chicken-and-egg issue here. Let me explain. By default, the SSM 4.0 SR2 install is at SP9, which gave it a somewhat simpler IMG. However, we gave in to the temptation of installing SP11 since this SPs were obtainable without Maintenance Optimizer, which gave us a more complicated IMG which includes, at some point, the client copy as mentioned above. We went through most of the IMG resulting from SP11 until we had Maintenance Optimizer working and then downloaded SP12.
I am in the process of installing the ABAP SP12 packages now and plan tomorrow to deploy the JAVA SP12 .SCA files. The IMG looks better and less confusing at SP12 than at SP11 or SP9. I think this calls for another IMG pass.
The $100 question - which parts of the IMG need to be done in client 000 and which to do in our client 100 (copied from client 000 after SP11 was applied). We are really confused on this point. If anyone can shed some light on this, i would very much appreciate it.
Sincerely,
Steven McElwee, Duke University

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

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

Client copy

hi,
while doing local client copy in ECC6.0 its asking to create an RFC for Financial Basis component

Fine,
So you have to copy the client from 001 , copy the profiles - sap_cust,sap_user.
since u r installed ABAP + JAVA , you have to copy only from 001, this client only have the content of java users eg (j2ee_admin).
You can also chk, if ur login into client 000 , no j2ee_admin user will there.
Regards
MLN

SAP_ALL & SAP_NEW profiles not available in new client after client copy

I am setting up a BI Client and have been following some documentation to do this downloaded from SDN. In the process, i created my client 'client 200' assigned to a logical system then doing client copy from 'client 000' using transaction SCCL. There is a step when i now have to create a user in the new client (client 200 ) where i am supposed to assign the user to profiles SAP_ALL and SAP_NEW. Unfortunately these are not available in my newly set client but in 'client 000' they are available.
Did i make some error in the client copy process or i still need to do something to have the profiles in 'client 200'. Please assist.

There is no issue in rerunning the Client Copy.
But please check what mistake you made in the first one.
Here are the steps.
Create an entry in SCC4.
RZ10 modify parameter login/no_automatic_user_sapstar=0
Check that you have enouf background and dialog processes.
Restart the sap system
then login with SAP* in the Client you made.
Run Sccl and give the Profile SAP_All
Select the source Client as 000
and Source Client user Master as 001
Check tthat you dont select the check box of TEST MODE.
and schedule in backgreond.
Thanks Rishi Abrol

Unable to make the Client Copy

Hi Team ,.
             I am trying to make a client Copy after SCCL transaction is performed when we check the status
in SCC3 it's throwing an error
Error :
Client 200 logon locked
Client Copy probably cancelled
The Client could be the source client of a copy
Reset Lock        Keep Lock      Cancel
Please help
Regards ,
Madhu

I went through this Document
Client copy 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 001.
This note also appears if an RFC destination was found but this does not
work.
o   RFC destination: 001
o   Error text:
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 001).
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: 001
4. Start the client copy again.
SOLUTION:
Login to client 001
Go to sm59, create rfc connection type 3, give the rfc destination : FINBASIS_001
Logon and security--> give user id and password (of any user in client 000)(user should be a service user or communication user so as to avoid password lock situation)
Check Test connection: test ---à authorization test.
Login in to new client: 800
Run the tcode: FINB_TR_DEST
Click on new entries:
Give the client: 001 and destination as FINBASIS_001 and save .
Run Tcode: sccl
Source: 001
Target: 800
Run as background job. Go to sm37 & check the status.

BI - Client copy 000, 001 or neither

Similar Messages

Maybe you are looking for