Queary regarding Client Copy
Hi Experts,
I have a scenario where in my Source Systems runs on HP-UX,Oracle10G and ECC 6.0 and my Target Systems runs on Windows 2003,Oracle 10G and ECC 6.0 except OS all the SAP and DB versions and Patches are same.
Could you please tell me can i able to do remote client copy( i am sure with client export/import we can do)? does any body done the same before.
Please suggest me on this
Thanks,
Laxman
As far as i remember Remote Client Copies between different OS is possible... essentially a client copy is a HUGE transport and as far as the SAP versions are the same it should be ok. (please correct me if I'm wrong)
Read
http://help.sap.com/saphelp_nw04s/helpdata/en/69/c24c4e4ba111d189750000e8322d00/frameset.htm
and
http://help.sap.com/saphelp_nw04s/helpdata/en/69/c24c684ba111d189750000e8322d00/frameset.htm
Regards
Juan
Similar Messages
-
Regarding client copy and authorizations
hi,
i had installed SAP BW 3.5 on my system.it is a fresh installation.now the probelm is that iam unable to open the administration workbench screen which is the most important of all the BW screens available.when i type the relevant tcode , it is saying "screen cannot be opened on 000 client".so i created one more client 070 (by copying client). and when i log on using 070 client , it is saying you are not authorized to use that screen.
any suggestions?had i missed something in the installation?
regards,
raviHi Ravi,
The procedure to delete is as below.
1. Log on to the client to be deleted.
2. Execute SCC5.
3. Check the delete entry from T000.
4. Schedule in the background.
Since you said you have deleted already , may be you have not checked the delete entry fron table T000.
In this case Go to table T000 and delete the entries.
After that create a client as below.
A local client copy copies between clients within the same R/3 System.
Both a local and remote client copy must be initiated from the target client using the following steps:
1. To create an entry for the target client in the client maintenance table, choose SCC4
2. Log on to the target client as SAP* with the initial password PASS.
3. Perform the client copy using SCCL.
4. Select the data to be copied using a profile.
5. Assign the source client for Customizing data, application data, and user master records.
6. Begin the client copy.
7. As copying is a lengthy process, use background processing.
8. To ensure data consistency, you may not logon to the target client during a client copy.
9. Lock the users in source client.
Regards,
Bapujee naidu -
Client Copy and System Restore query
Dear All,
I have few major doubt regarding client copy and system restor.
1. In my Quality system there are 2 clients: 100 and 200.In my PRD there is only 1 client 300(other than the standard default clients). My doubt is during remote client copy with SAP_ALL profile from PRD to QUA why the space increases only in MB.
I have been asked the same question by my management. They are saying PRD is 300GB and QUA is 220GB then why the space increases in MB though all data is copied in client 200(QUA) from client300(PRD)
2. If I delete client why the space is released in MB. Because according to them it should be in GBs.
3. Now my third query is I have to restore PRD backup in QUA.So I said that this requires same <SID> and Same sapce in the sapdatafiles(OS is HP-UX 11.31 and DB is Oracle 10g).So I have to explain them why these two things are contradary to each other. In case of client copy space required is only in MB and in case of System restore of PRD in QUA sapce require is in GBs.
Your suggestions will be highly obliged.
Regards,
PG1. In my Quality system there are 2 clients: 100 and 200.In my PRD there is only 1 client 300(other than the standard default clients). My doubt is during remote client copy with SAP_ALL profile from PRD to QUA why the space increases only in MB.
Response > Because during client copy your customizing and other objects are copied.
The database structures,tables etc are already present.
2. If I delete client why the space is released in MB. Because according to them it should be in GBs.
Response > Since client deletion is not same as deleting database /customizing tables .If you delete complete dataspaces/tables then there will be sizeable difference.Similar logic as Response 1
3. Now my third query is I have to restore PRD backup in QUA.So I said that this requires same <SID> and Same sapce in the sapdatafiles(OS is HP-UX 11.31 and DB is Oracle 10g).So I have to explain them why these two things are contradary to each other. In case of client copy space required is only in MB and in case of System restore of PRD in QUA sapce require is in GBs.
Response > Since in a system copy you will copy data files (which includes tables,and all otehr strucutres ) hence the size required will be similar to PRD. -
Client Copy Using Client Export/Import
Hi Everyone,
This is regarding Client Copy Using Client Export/Import Method. We have two system Production and Development system. Iam planning to do a client copy from from PRD to DEV. I know most of the steps to perform Client Copy.I have some doubhts So if some one can please help me out i would really appreciate it.
!) I want to know which user should be used to perfrom Client Export ?
2) I want to know know which user to be used to perform Client delete?
3) Is there any particular USER who is recommended to perform Client Copy or any USER can do it?
4) After the Client Delete Procedure thorugh SCC5 ..to get back the client space we do Reorganization ? can anyone plzz tell me what are the tables that i need to reorganize or if anyone can provide me the steps for Reorganization i would be really thankful.
Waiting For your Replies
Best RegardsHi Mohammed,
1)I want to know which user should be used to perfrom Client Export ?
You can use your personal defined on the system UserID.
2) I want to know know which user to be used to perform Client delete?
Same as above, just make sure you have an account on the client and you log on to the right client
3) Is there any particular USER who is recommended to perform Client Copy or any USER can do it?
I am not aware that you should use a particular user. I have been doing copies/deletions with my UserID, as system administrator.
4) After the Client Delete Procedure thorugh SCC5 ..to get back the client space we do Reorganization ? can anyone plzz tell me what are the tables that i need to reorganize or if anyone can provide me the steps for Reorganization i would be really thankful.
Reorganization ( I personally) use SAPDBA tool. However -if you use ORACLE, there are other alternatives as well. What is your DB vendor? I will append more info in a bit.
Rgds,
Loukas -
Logical System and Client copy
Hi Gurus ,
I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
Regards
SelvanHi Manjula ,
Below i mentioned the full detail about the error .
RFC destination for client copy in systems with Financials Basis (FINBASIS) component.
The system could not find any suitable RFC destination for processing for client 000. This note also appears if an RFC destination was found but this does not work. o RFC destination: FINBTR@ID3CLNT000 o Error text: Error during the retrieval of the logon data Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection or perform the following steps manually: 1. Create an RFC destination with the target ZK>source client of client copy (in this case 000).
2. Check whether the RFC destination works in transaction SM59. To avoid errors when assigning the password or the authorizations of the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination: - Transaction: FINB_TR_DEST (Destinations for Transport Methods of the Financials Basis) - Client: 000
4. Start the client copy again.
Kindly advice me
selvan -
Remote Client Copy - Ended in Erros
Hi Friends,
We recently performed a Remote client copy. What we normally do is we restore an latest offline backup of the Prod into an instance built exclusively for performing client copies into our QA system.
So if our actual PROD is ABC ( production ), the replica system is ADC. We restore latest backup onto ADC. Then from ADC we do a client copy onto AQC ( Quality ). We have n number of clients in AQC. When copying into a particular client we are facing this problem of 3 tables not being able to get copied. They are BKPF,LTAK and SOST. It happened twice that the Remote client ended with errors.
It says "Read or conversion error". The detailed error looks like below ;
TAB_COPY_R_CONTINUE LTAK WITH KEY:
I01 0000066362
Read or conversion error system: ADCT500 table: LTAK
ERROR: Internal error when inserting in table: LTAK
Internal error: 1,262,713 65,536 VERIFY_CNT
Process 00001 has copied data 25.02.2010 18:04:16
Read or conversion error system: ADC500 table: BKPF
Process 00002 has copied data 25.02.2010 19:09:00
Start: Recopy errors 25.02.2010 19:09:02
TAB_COPY_R_CONTINUE BKPF WITH KEY:
2100 5100019665 2008
Read or conversion error system: ADC500 table: BKPF
ERROR: Internal error when inserting in table: BKPF
Internal error: 6,948,636 1,777,664 VERIFY_CNT
Read or conversion error system: ADC500 table: LTAK
TAB_COPY_R_CONTINUE SOST WITH KEY:
OTF 34 000000019247
Read or conversion error system: ADC500 table: SOST
ERROR: Internal error when inserting in table: SOST
Internal error: 2,594,254 180,224 VERIFY_CNT
We approached SAP and they asked to do a DB reorg, run update statistics on both source and target and then re run the client copy.
Well DB reorg is a big activity so we just updated the statistics and ran again the "recopying errors" but still it is the same problem.
Can anybody please suggest something. Thank you.
regards
Vinod KHi Friends,
My apologies for coming back to you guys so late. I kind of was lost to find a solution for this.
Hi Sanujit,
The database logs dont indicate anything at all about this error or i am not able to locate them.
Rajesh,
There was a table comparison done for these tables properties in both source and target and everything looked ok and confirmed by the application.
At this moment we have anyway decided to go a fresh client copy again as lot of time has already passed and there would be differences in source and target tables.
But anyway could you please tell me the procedure to transport tables between source and target systems?
Hi Anil,
SAP iS ECC 6.0 and Oracle is 10.2.0.4.0
Thanks again for your time and pateince.
Regards
Vinod K -
Remote client copy performance
Hello experts,
I need an opinion on following possibilities that could speed up remote client copy:
Increasing maximum number of processes for parallel processing in dialog mode?
Increasing the update processes?
Decreasing the undo retention from default 900 seconds to 600 seconds (Oracle) ?
Increase the number of redo log files?
An opinion or any other insights would be highly appreciated.
Thank you,
RohitWell, the answer is maybe.
You did not supply any information about your run and your system, how can we give you good advice? Any of your proposals might speed up the copy process, but we cannot tell (well decreasing the undo retention and changing the update work processes will not change much). If your hardware (cpu/disk/network) is not exhausted, then increase the number of parallel processes.
Besides that these notes contain good hints regarding copy speedup:
[489690 - CC INFO: Copying large production clients|https://service.sap.com/sap/support/notes/489690]
[446485 - CC-ADMIN: Special copying options|https://service.sap.com/sap/support/notes/446485]
Cheers Michael -
Hi All
am performing remote client copy through scc9, created RFC & tested connection,
this server is not in the transport landscape.
when i execute scc9 and select profile SAP_ALL from target system (Production server) it runs for 5-7 mins and ends with message as "The client copy you started has terminated Tables cannot be converted.
should the users on Production server to be locked.
here is the logs in SCC3:
Client in Source System 500
Copy Type Remote copy
Profile SAP_ALL
Status Cancelled. See Log
User MODI_SUPER
Start on 31.08.2009 / 16:47:19
Last Entry on 31.08.2009 / 16:50:00
Last Action: RFC DDIC System Comparison
Statistics for this Run
- No. of Tables 0 of 53521
- Copied Lines 0
Warnings and Errors
Table Name Component Package
A543 Table Def. Missing Locally
A544 Table Def. Missing Locally
A800 Table Def. Missing Locally
A950 Table Def. Missing Locally
A960 Table Def. Missing Locally
A961 Table Def. Missing Locally
ZCOM Table Def. Missing Locally
ZCSKS Field missing locally
ZEMAIL Table has Incompatible Fields
ZLR_DTL Field missing locally
ZMM_RGP_SLNO Different Field Names
ZPM_CALIBRATION Field missing locally
ZSDD Table not ConvertibleHi Ashun8
Please not be in rush as your SD & MM consultant need to testing some scenarior on sandbox.
As being Basis expert! you should have many comprisions including patch level on both server before initiate the Remote Client Copy.
I will prefer to do the system copy instead the Remote Client copy without downtime on PRD server.
Regards
Anwer Waseem
SAP NetWeaver Basis -
Remote client copy (SCC9) runs a very long time!
remote client copy (SCC9) runs a very long time!
how to do it quickly process?
(eg use imp and exp-oracle tool, as it can be done to understand what the SAP data has been copied and are now in a different location, for Developers)scn001 wrote:
remote client copy (SCC9) runs a very long time!
> how to do it quickly process?
> (eg use imp and exp-oracle tool, as it can be done to understand what the SAP data has been copied and are now in a different location, for Developers)
Hi,
You can export the client, as well but it will take long time too, depended to your client size. Please note that client copy operation should be performed by standard SAP client management tools, such as client export/import or remote copy.
Ask this question to SAP support first. Technically, you can choose many ways to copy a SAP client, but as far as I know that SAP will not support you (such as errors you faced during the client export/import or the problems related by the copy operation), if you use any other 3rd party tool while for the client copy purposes.
Best regards,
Orkun Gedik
Edited by: Orkun Gedik on Jun 30, 2011 10:57 AM -
Remote client copy fails.
The error message and info is given below. Help me to proceed.
Client copy
The client copy you started has terminated
Client Copy could not start because of Repository differences
Diagnosis
The table definitions differ between the systems. These differences mean that a copy of the data can cause a data loss and system inconsistencies. Differences occur when further developments were not transported or were copied between different maintenance levels.
Procedure
Transport all the developments of table structures between the systems using the Transport Organizer and bring your system to the same development level.
It is observed that some tables are missing in the target system. How do I copy the table structures to the target system?
Thanks in advanceHello Ashraf,
There are repository differences between you source and traget system.
If you want to get the list of repository differences, then run a RFC check before you execute remote clinet copy.
You have to then remove these repository differences before you start with the remote client copy.
to remove the difference you have to:
"Transport all the developments of table structures between the systems using the Transport Organizer and bring your system to the same development level" as mentioned above
I would recommend you to go for Export / Import rather than Remote client copy.
There are several advantages of export import method over remote clinet copy
Regards,
Ammey Kesarkar
<i>'Award points for useful info'</i> -
Logical system name to be updated while client copy--URGENT HELP REQUIRED
Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe -
Unable to create IDOCs after client copy
I'm unable to create IDOCs after a client copy. I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
Does anyone know what how to fix this. Thank you in advance.
Runtime Error SAPSQL_ARRAY_INSERT_DUPREC
Except. CX_SY_OPEN_SQL_DB
Date and Time 22.10.2007 16:50:51
ShrtText
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLEDI1" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLEDI1" or "LEDI1F09"
"F09_IDOC_INSERT_WITH_NUMBER"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"F09_IDOC_INSERT_WITH_NUMBER"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "auaplxr3q"
Network address.......... "128.197.135.5"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "000B439ED600"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "auaplxr3q"
Database type............ "ORACLE"
Database name............ "Q63"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Mar 22 2007 20:48:46"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "175"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 4189928
Heap..................... 0
Page..................... 0
MM Used.................. 1469352
MM Free.................. 2718056
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "SAPLEDI1" in
"F09_IDOC_INSERT_WITH_NUMBER".
The main program was "SAPMSSY1 ".
The termination occurred in line 108 of the source code of the (Include)
program "LEDI1F09"
of the source code of program "LEDI1F09" (when calling the editor 1080).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
of the (Include) program "LEDI1F09 ".
Source Code Extract
Line
SourceCde
78
perform call_badi tables list_container_insert
79
using control
80
ident.
81
Aufruf des Badi's für das einstreuen neuer Segmente
82
perform call_insert_badi tables list_container_insert
83
using control
84
ident
85
changing maxsegnum.
86
87
free list_container_insert
88
FREE_RETURN = 1.
89
ELSE. " no other IDoc is open in create-mode
90
LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
91
AND DOCNUM EQ IDENT.
92
LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
93
MODIFY LIST_CONTAINER_CREATE.
94
ADD 1 TO MAXSEGNUM.
95
ENDLOOP.
96
if control-mestyp eq c_mestyp.
97
CALL FUNCTION 'FUNCTION_EXISTS'
98
EXPORTING
99
funcname = c_func
100
EXCEPTIONS
101
FUNCTION_NOT_EXIST = 1.
102
IF syst-subrc IS INITIAL. "Anwendungssystem
103
perform call_transform
104
tables list_container_create
105
using control.
106
ENDIF.
107
endif.
>>>>>
INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
109
Aufruf des Badi's für das Anwendungsmapping einzelner Felder
110
perform call_badi tables list_container_create
111
using control
112
ident.
113
perform call_insert_badi tables list_container_create
114
using control
115
ident
116
changing maxsegnum.
117
118
free list_container_create
119
FREE_RETURN = 0.
120
ENDIF.
121
122
insert status records
123
124
SYN_ERROR_IN = ' '.
125
CNTR_STATUS = 0.
126
REFRESH LIST_STATUS.
127
CLEAR LIST_STATUS.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
13 FORM SAPLEDI1 LEDI1F09 108
F09_IDOC_INSERT_WITH_NUMBER
12 FUNCTION SAPLEDI1 LEDI1U19 33
EDI_DOCUMENT_CLOSE_CREATE_TAB
11 FUNCTION SAPLEDIR LEDIRU01 273
IDOC_INBOUND_WRITE_TO_DB
10 FORM SAPLEDIN LEDINF01 457
ONE_IDOC_STORE
9 FUNCTION SAPLEDIN LEDINU05 234
IDOC_INBOUND_ASYNCHRONOUS
8 FORM SAPLEDIN LEDINV05 19
IDOC_INBOUND_ASYNCHRONOUS
7 FORM SAPMSSY1 SAPMSSY1 254
XAB_RUN_DRIVER
6 FUNCTION SAPLSXAB LSXABU01 9
RFC_RUN_XAB_DRIVER
5 FUNCTION SAPLERFC LERFCU01 59
ARFC_EXECUTE
4 FUNCTION SAPLERFC LERFCU02 229
ARFC_DEST_SHIP
3 FORM SAPLERFC LERFCV02 28
ARFC_DEST_SHIP
2 FORM SAPMSSY1 SAPMSSY1 69
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30
%_RFC_START
Chosen variables
Name
Val.
No. 13 Ty. FORM
Name F09_IDOC_INSERT_WITH_NUMBER
CONTROL-MESTYP
USERCLONE
554544444222222222222222222222
53523CFE5000000000000000000000
C_MESTYP
FIDCCH
444444222222222222222222222222
694338000000000000000000000000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
LIST_STATUS-STAPA2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
C_FUNC
IDOC_TRANSFORM
444455544544542222222222222222
94F3F421E36F2D0000000000000000
SYST-REPID
SAPLEDI1
5454444322222222222222222222222222222222
310C549100000000000000000000000000000000
SY-UNAME
Q63CLNT140
533444533322
1633CE414000
%_DUMMY$$
2222
0000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SYST-SUBRC
0
0000
0000
ALE_IDOC_TO_APL_OK
62
33
62
LIST_CONTAINER_CREATE[]
Table IT_20[9x1068]
FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
Table reference: 14
TABH+ 0(20) = 070000008036F5B8000000000000000000000000
TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
TABH+ 40(16) = 0400002300000CA0000824C401000000
store = 0x070000008036F5B8
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 14 (0x0000000E)
label = 20 (0x00000014)
fill = 9 (0x00000009)
leng = 1068 (0x0000042C)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000048
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x070000008036F610
pghook = 0x07000000802D86D0
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 23 (0x00000017)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LIST_CONTAINER_CREATE
1400000000000511747000000009E1BPADRML 00000002#èXD63 070TST_QA140_1
3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
CONTROL
1400000000000511747640 64 2SAPQ63 LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
G_MAXSYNERR
1
0000
0001
<%_TABLE_EDID4>
ALE_DISPATCH_ERROR
27
33
27
ALE_IDOC_READY_FOR_APL
64
33
64
%_SPACE
2
0
IDENT
0000000000000001
3333333333333333
0000000000000001
ALE_IDOC_TO_APL_ERROR
63
33
63
No. 12 Ty. FUNCTION
Name EDI_DOCUMENT_CLOSE_CREATE_TAB
IDENTIFIER
0000000000000001
3333333333333333
0000000000000001
NO_DEQUEUE
X
5
8
SYN_ACTIVE
Y
5
9
IDOC_CONTROL
1400000000000511747640 64 2SAPQ63 LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
SYNTAX_RETURN
0
0000
0000
INT_EDIDD[]
Table IT_10[9x1062]
FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
Table reference: 9
TABH+ 0(20) = 0700000080284B80070000008028530800000000
TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
TABH+ 40(16) = 0400000900000AA8000824C401000000
store = 0x0700000080284B80
ext1 = 0x0700000080285308
shmId = 0 (0x00000000)
id = 9 (0x00000009)
label = 10 (0x0000000A)
fill = 9 (0x00000009)
leng = 1062 (0x00000426)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000039
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000080320D90
pghook = 0x07000000802E1508
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 17 (0x00000011)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0x07000000802852A8
>>>>> 2nd level extension part <<<<<
tabhBack = 0x0700000080284B30
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
NO_IGNORE
2
0
EDI_IDOC_SYNTAX_ERROR_IN
60
33
60
DOCNUM
0000000000511747
3333333333333333
0000000000511747
EXCLUSIVE
E
4
5
SYNCHRONOUS
S
5
3
APL_TESTIDOC_CHECK_OK
55
33
55
FREE_RETURN
0
0000
0000
INT_EDIDD
1400000000000000001000009E1BPADRML 00000000##XD63 070TST_QA140_17 X00
3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
SUB_INT_ACK_POSITIVE
14
33
14
G_INSERT_OK
2
0
LIST_CONTAINER_INSERT_TMP[]
Table[initial]
LIST_CONTAINER_INSERT_TMP
0000000000000000000000000 00000000##
2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 11 Ty. FUNCTION
Name IDOC_INBOUND_WRITE_TO_DB
PI_DO_HANDLE_ERROR
X
5
8
PI_NO_DEQUEUE
X
5
8
PI_RETURN_DATA_FLAG
X
5
8
PI_RFC_MULTI_CP
0000
3333
0000
PI_STATUS_MESSAGE
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PE_IDOC_NUMBER
0000000000000001
3333333333333333
0000000000000001
PE_INBOUND_PROCESS_DATA
140BAPI 6
3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
PE_STATE_OF_PROCESSING
0
0000
0000
T_DATA_RECORDS[]
Table IT_10[9x1062]
T_LINKED_OBJECTS[]
Table IT_11[0x100]
FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
Table reference: 10
TABH+ 0(20) = 000000000000000007000000802853F000000000
TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
TABH+ 40(16) = 0400000900002BB00010249401000000
store = 0x0000000000000000
ext1 = 0x07000000802853F0
shmId = 0 (0x00000000)
id = 10 (0x0000000A)
label = 11 (0x0000000B)
fill = 0 (0x00000000)
leng = 100 (0x00000064)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000190
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
store_id = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0x0700000080285390
>>>>> 2nd level extension part <<<<<
tabhBack = 0x0700000080285340
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
PC_CONTROL_RECORD
1400000000000000000 30 2 LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
L_STATUS
64
33
64
L_ALE_SUCCESS_MESSAGE
B1 S005 No filters
4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
ST_PREVIOUS_PARTNER_DATA-SYNCHK
X
5
8
C_TRUE
X
5
8
SYST-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
C_ELEMENT_UNPROCESSED_IDOCS
Unprocessed_IDocs
56776667766544667222222222222222
5E02F353354F94F33000000000000000
ST_PREVIOUS_STATE_OF_PROCE
0
0000
0000
ST_INBOUND_PROCESS_DATA-EDIVR2
6
3
6
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
L_SYN_ACTIVE
Y
5
9
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
L_SYNTAX_RETURN
0
0000
0000
%_DUMMY$$
2222
0000
SY-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
No. 10 Ty. FORM
Name ONE_IDOC_STORE
IDOC_NUMBER_IN
0000000000000000
3333333333333333
0000000000000000
STATE_OF_PROCESSING_IN
0
0000
0000
INBOUND_PROCESS_DATA_IN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS[]
Table[initial]
G_LAST_IDOC_NUMBER
0000000000000000
3333333333333333
0000000000000000
SYST-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
CURRENT_CONTROL_RECORD_IN-DOCNUM
0000000000000000
3333333333333333
0000000000000000
CONV_ERROR
2
0
C_TRUE
X
5
8
SY
0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
STATUS_MESSAGE_IN
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_IDOC_SELECT_AND_WRITE_TO_DB
5
3
5
SY-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
STATUS_MESSAGE_IN-STAMID
22222222222222222222
00000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
STATUS_MESSAGE_IN-STAMNO
000
333
000
RET_FLAG
X
5
8
G_RFC_CODEPAGE
0000
3333
0000
RSJOBINFO-JOBSUBRC
0
0000
0000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
SY-LANGU
E
4
5
G_T_DATA_RECORDS[]
Table IT_10[9x1062]
LT_LINKED_OBJECTS[]
Table IT_11[0x100]
CURRENT_CONTROL_RECORD_IN
1400000000000000000 30 2 LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
SWO_%OBJID
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 9 Ty. FUNCTION
Name IDOC_INBOUND_ASYNCHRONOUS
IDOC_CONTROL_REC_40[]
Table IT_3[1x524]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
Table reference: 3
TABH+ 0(20) = 07000000802D876007000000802D449000000000
TABH+ 20(20) = 0000000300000003000000010000020C000000E0
TABH+ 40(16) = 0400000900001FE0000A249001000000
store = 0x07000000802D8760
ext1 = 0x07000000802D4490
shmId = 0 (0x00000000)
id = 3 (0x00000003)
label = 3 (0x00000003)
fill = 1 (0x00000001)
leng = 524 (0x0000020C)
loop = 224 (0x000000E0)
xtyp = TYPE#000136
occu = 10 (0x0000000A)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 0
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000802DB9D8
pghook = 0x0000000000000000
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 10 (0x0000000A)
lineAlloc = 10 (0x0000000A)
store_id = 9 (0x00000009)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0x07000000802D88A0
>>>>> 2nd level extension part <<<<<
tabhBack = 0x07000000802D8710
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
IDOC_DATA_REC_40[]
Table IT_4[9x1063]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
Table reference: 4
TABH+ 0(20) = 07000000802D880807000000802D896000000000
TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
TABH+ 40(16) = 04000009000020500008249001000000
store = 0x07000000802D8808
ext1 = 0x07000000802D8960
shmId = 0 (0x00000000)
id = 4 (0x00000004)
label = 4 (0x00000004)
fill = 9 (0x00000009)
leng = 1063 (0x00000427)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000138
occu = 8 (0x00000008)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 0
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000802E1550
pghook = 0x07000000802D8860
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 12 (0x0000000C)
shmIsReadOnly = 0 (0xHi Rohan,
Welcome to SDN!
This error means that you're trying to duplicate a record on the DB... check the IDOC number ranges... it might help
Regards
Juan
Please reward with points if helpful -
Hi,
I have performed a remoted client copy of ECP300 to ECQ system using
SAP_ALL Profile and the client copied successfully. After the client
copy some users are complainting that not all data moved over or there
are some major differences. I know the client copy finished but the
users are saying the client copy is not a exact copy of ECP.Are there
any functional or abap post configuration that needs to happen after
this remote client copy? From the client copy logs, it seem like all
the tables got copied over. Please advise as this is very critical.
I have attached 2 issues reported by users and the client copy log with
details. I have also attached the data dictionary differences of the 2
system ECP and ECQ using SCC9 --> RFC SYSTEM COMPARISON.
Target Client 220
Source Client (incl. Auth.) 265
Source Client User Master 265
Copy Type Local Copy
Profile SAP_ALL
Status Successfully Completed
User SAP*
Start on 01/07/2011 / 23:16:01
Last Entry on 01/08/2011 / 03:53:31
Statistics for this Run
- No. of Tables 56787 of 56787
- Number of Exceptions 1
- Deleted Lines 11478
- Copied Lines 152345539
/ISDFPS/CS_EXLST Field Missing Remote IS-DFS-MM /ISDFPS/MM_CS SAP TRANSP Exception List: Overwritten Purchase Requisitions SAPKGED04G
/SAPMP/GT_FDE_T1 Table Missing Remote IS-MP /SAPMP/FAST_DATA_ENTRY_GEN_APP SAP TRANSP IMG: Fast Entry in Trading Contract General Settings SAPK-603DDINECCDIMP
/SAPMP/GT_FDE_T2 Table Missing Remote IS-MP /SAPMP/FAST_DATA_ENTRY_GEN_APP SAP TRANSP Fast Entry in Trading Contract: Transfer from Info Record SAPK-603DDINECCDIMP
AD01DLI Field Missing Remote PS-REV AD01 SAP TRANSP Dynamic items (DI)
ADPIC_MIGO_SET Table Missing Remote IS-AD-MPN ADPIC SAP TRANSP Customizing Settings for MIGO SAPK-603DDINECCDIMP
ADPIC_MIGO_USR Table Missing Remote IS-AD-MPN ADPIC SAP TRANSP Customizing Settings for MIGO SAPK-603DDINECCDIMP
MPDCD Field Missing Remote IS-AD-MPD AD_MPD SAP TRANSP MPD: OBSOLETE - Counter Data for Maintenance Document Items SAPK-603DDINECCDIMP
MPDCUST_DATA_FLG Table Missing Remote IS-AD-MPD AD_MPD SAP TRANSP Customising table to store the data container flag SAPK-603DDINECCDIMP
MPDCUST_EFFT_DOC Table Missing Remote IS-AD-MPD AD_MPD SAP TRANSP Customising table to store effectivity data for documents SAPK-603DDINECCDIMP
MPDCUST_EFFT_TO Table Missing Remote IS-AD-MPD AD_MPD SAP TRANSP Cust. table to store effectivity data from technical objects SAPK-603DDINECCDIMP
MPDCYCLE Table Missing Remote IS-AD-MPD AD_MPD SAP TRANSP MPD: Cycle Data for Maintenance Document Items SAPK-603DDINECCDIMP
MPDEFFECT Table Missing Remote IS-AD-MPD AD_MPD SAP TRANSP MPD effectivity data SAPK-603DDINECCDIMP
MPDITEM Table Missing Remote IS-AD-MPD AD_MPD SAP TRANSP Maintenance Plan Items SAPK-603DDINECCDIMP
MPDPSD Field Missing Remote IS-AD-MPD AD_MPD SAP TRANSP MPD: MPD and MP header data SAPK-603DDINECCDIMP
ADMPN_RBA_CGRP Table Missing Remote IS-AD-MPN AD_MPN_RBA_DDIC SAP TRANSP Check Groups for APO ATP SAPK-603DDINECCDIMP
TMCNV Convertible -> Local CA-GTF-TS BMG SAP TRANSP Data on Material Numbers Conversion
CRFH Field Missing Remote PP-BD-PRT CF SAP TRANSP CIM production resource/tool master data
CKIS Field Missing Remote CO-PC-PCP CK SAP TRANSP Items Unit Costing/Itemization Product Costing
KALM Field Missing Remote CO-PC-PCP CK SAP TRANSP Costing Run: Costing Objects
KEKO Field Missing Remote CO-PC-PCP CK SAP TRANSP Product Costing - Header Data
MLCR Field Missing Remote CO-PC-ACT CKML SAP TRANSP Material Ledger Document: Currencies and Values
VSAFKO_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Order header data for PP orders
VSAFPO_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Order items in PP orders
VSAFVC_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Operation in order
VSAUFK_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Order master data SAPK-603DDINSAPAPPL
VSFPLT_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Billing schedule: Dates
VSPLAF_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Planned order
VSRESB_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Reservation/Dependent requirements
VSRSADD_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Additional fields for reservation
VSVBAK_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Sales document: Header data
VSVBAP_CN Field Missing Remote PS-SIM CNVS SAP TRANSP Version: Sales document: Item data
RSADD Field Missing Remote PS-MAT CN_MAT SAP TRANSP Additional fields for reservation
TCNTM05 Field Missing Remote PS-ST-OPR-NET CN_NET_OPR SAP TRANSP Assignment Components to Groups
AFKO Field Missing Remote PP-SFC CO SAP TRANSP Order header data PP orders
AFPO Field Missing Remote PP-SFC CO SAP TRANSP Order item
AFVC Field Missing Remote PP-SFC CO SAP TRANSP Operation within an order SAPK-603DDINSAPAPPL
AFFW Field Missing Remote PP-SFC-EXE-CON CORU SAP TRANSP Goods Movements with Errors from Confirmations
AFRU Field Missing Remote PP-SFC-EXE-CON CORU SAP TRANSP Order Confirmations SAPK-603DDINSAPAPPL
AFRV Field Missing Remote PP-SFC-EXE-CON CORU SAP TRANSP Confirmation pool
PLPO Field Missing Remote PP-BD-RTG CP SAP TRANSP Task list - operation/activity
STPO Field Missing Remote LO-MD-BOM CS SAP TRANSP BOM item
T414 Field Missing Remote LO-MD-BOM CS SAP TRANSP Explosion Types
CJITO_02 Table Missing Remote IS-A-JIT DI_JITOUT SAP TRANSP Customizing Table for Definition of Tolerances SAPK-603DDINECCDIMP
CJITO_02T Table Missing Remote IS-A-JIT DI_JITOUT SAP TRANSP Text Table to Define the Tolerances SAPK-603DDINECCDIMP
JITOCO Field Missing Remote IS-A-JIT DI_JITOUT SAP TRANSP Call Components JIT Outbound SAPK-603DDINECCDIMP
S2L_GLOBAL_DATA Field Missing Remote IS-A-S2L DI_S2L SAP TRANSP User-specific Save for Global Settings SAPK-603DDINECCDIMP
LFA1 Field Missing Remote FI FBASCORE SAP TRANSP Vendor Master (General Section)
KNKK Field Missing Remote FI-AR-AR FBD SAP TRANSP Customer master credit management: Control area data
VIMI01 Field Missing Remote RE FVVI SAP TRANSP Rental unit - Master data
VIOB01 Field Missing Remote RE FVVI SAP TRANSP Business entities
VIOB02 Field Missing Remote RE FVVI SAP TRANSP Property master data
VIOB03 Field Missing Remote RE FVVI SAP TRANSP Real estate building master
VIOB27 Field Missing Remote RE FVVI SAP TRANSP Relationship between properties and buildings
VIOB38 Field Missing Remote RE FVVI SAP TRANSP Relationship between Real Estate objects and SAP-PS
PEG_TXPT Field Missing Remote IS-AD-GPD GPD SAP TRANSP Pegging: Record of intransit stock in cross plant transfers SAPKGES01G
VEKP Field Missing Remote LO-HU-BF HANDLING_UNITS SAP TRANSP Handling Unit - Header Table
EQUI Field Missing Remote PM-EQM-EQ IEQM SAP TRANSP Equipment master data SAPK-603DDINSAPAPPL
EQUZ Field Missing Remote PM-EQM-EQ IEQM SAP TRANSP Equipment time segment
MHIO Field Missing Remote PM-PRM-TL IPRM SAP TRANSP Call Object from Maintenance Order
MHIS Field Missing Remote PM-PRM-TL IPRM SAP TRANSP Maintenance plan history
EQBS Field Missing Remote LO-MD-SN IQSM SAP TRANSP Serial Number Stock Segment
OBJK Field Missing Remote LO-MD-SN IQSM SAP TRANSP Plant Maintenance Object List SAPK-603DDINSAPAPPL
SER01 Field Missing Remote LO-MD-SN IQSM SAP TRANSP Document Header for Serial Numbers for Delivery
SER02 Field Missing Remote LO-MD-SN IQSM SAP TRANSP Document Header for Serial Nos for Maint.Contract (SD Order)
T377X Field Missing Remote LO-MD-SN IQSM SAP TRANSP Documents Allowed for Serial Number Management
CJIT01 Field Missing Remote IS-A-JIT ISAUTO_JIT SAP TRANSP JIT: Call Control SAPK-603DDINECCDIMP
VLCADDCUST Table Missing Remote IS-A-VMS ISAUTO_VLC SAP TRANSP VELO: Table for VMS additional end customer SAPK-603DDINECCDIMP
AFIH Field Missing Remote PM-WOC-MO IWO1 SAP TRANSP Maintenance order header
AUFM Field Missing Remote PM-WOC-MO IWO1 SAP TRANSP Goods movements for order
AUFK Field Missing Remote CO-OM-OPA KAUF SAP TRANSP Order master data SAPK-603DDINSAPAPPL
CEZP Field Missing Remote CO-PC-OBJ-PER KKPK SAP TRANSP Reporting Points Line Items
CPZP Field Missing Remote CO-PC-OBJ-PER KKPK SAP TRANSP Reporting Points - Periodic Totals Values
PABHD Field Missing Remote PP-KAB LAPA SAP TRANSP JIT call header record
PABIT Field Missing Remote PP-KAB LAPA SAP TRANSP JIT call items
LTAK Field Missing Remote LE-WM LVS SAP TRANSP WM transfer order header
ASMD Field Missing Remote MM-SRV MASB SAP TRANSP Service Master: Basic Data
CHVW Field Missing Remote MM-IM MB SAP TRANSP Table CHVW for Batch Where-Used List
ISEG Field Missing Remote MM-IM MB SAP TRANSP Physical Inventory Document Items
MKPF Field Missing Remote MM-IM MB SAP TRANSP Header: Material Document
MSEG Field Missing Remote MM-IM MB SAP TRANSP Document Segment: Material
RESB Field Missing Remote MM-IM MB SAP TRANSP Reservation/dependent requirements SAPK-603DDINSAPAPPL
MCIPMIS Field Missing Remote PM-IS-REP MCI SAP TRANSP PMIS: Master data characteristics for PMIS before image
MDTB Field Missing Remote PP-MRP-BD MD SAP TRANSP MRP Table
PLAF Field Missing Remote PP-MRP-BD MD SAP TRANSP Planned order
PKHD Field Missing Remote PP-KAB MD05 SAP TRANSP Control Cycle SAPK-603DDINSAPAPPL
TPK02 Field Missing Remote PP-KAB MD05 SAP TRANSP Key for Controlling Control Cycle: External Replenishment SAPK-603DDINSAPAPPL
T459K Field Missing Remote PP-MP-DEM MDPB SAP TRANSP Control table for customer requirements
EBAN Field Missing Remote MM-PUR ME SAP TRANSP Purchase Requisition SAPK-603DDINSAPAPPL
EKBE Field Missing Remote MM-PUR ME SAP TRANSP History per Purchasing Document
EKBEH Field Missing Remote MM-PUR ME SAP TRANSP Removed PO History Records
EKEK Field Missing Remote MM-PUR ME SAP TRANSP Header Data for Scheduling Agreement Releases
EKES Field Missing Remote MM-PUR ME SAP TRANSP Vendor Confirmations
EKET Field Missing Remote MM-PUR ME SAP TRANSP Scheduling Agreement Schedule Lines
EKKO Field Missing Remote MM-PUR ME SAP TRANSP Purchasing Document Header
EKPO Field Missing Remote MM-PUR ME SAP TRANSP Purchasing Document Item
EKRS Field Missing Remote MM-PUR ME SAP TRANSP ERS Procedure: Goods (Merchandise) Movements to be Invoiced
MARA Field Missing Remote LO-MD-MM MG SAP TRANSP General Material Data
MARC Field Missing Remote LO-MD-MM MG SAP TRANSP Plant Data for Material SAPK-603DDINSAPAPPL
MARM Field Missing Remote LO-MD-MM MG SAP TRANSP Units of Measure for Material
MCH1 Field Missing Remote LO-MD-MM MG SAP TRANSP Batches (if Batch Management Cross-Plant)
MCHA Field Missing Remote LO-MD-MM MG SAP TRANSP Batches
MVKE Field Missing Remote LO-MD-MM MG SAP TRANSP Sales Data for Material
T130F Field Missing Remote LO-MD-MM MG SAP TRANSP Field attributes
T134 Field Missing Remote LO-MD-MM MG SAP TRANSP Material Types
MVRA Field Missing Remote LO-MD-MM MGVERS SAP TRANSP Cross-version fields for MARA SAPKGES01G
MVRC Field Missing Remote LO-MD-MM MGVERS SAP TRANSP Cross-version fields for MARC SAPKGES01G
MVRM Field Missing Remote LO-MD-MM MGVERS SAP TRANSP Units of Measure for Material SAPKGES01G
MVVE Field Missing Remote LO-MD-MM MGVERS SAP TRANSP Sales Data for Material SAPKGES01G
MILL_T399X Field Missing Remote IS-MP-PP MILL_PP SAP TRANSP Parameters for Partitioning Order - Order Type SAPK-603DDINECCDIMP
ESLH Field Missing Remote MM-SRV ML SAP TRANSP Service Package Header Data
ESLL Field Missing Remote MM-SRV ML SAP TRANSP Lines of Service Package
RSEG Field Missing Remote MM-IV MRM SAP TRANSP Document Item: Incoming Invoice SAPK-603DDINSAPAPPL
ADRC Field Missing Remote BC-SRV-ADR SZAD SAP TRANSP Addresses (Business Address Services)
VBAK Field Missing Remote SD-SLS VA SAP TRANSP Sales Document: Header Data SAPK-603DDINSAPAPPL
VBAP Field Missing Remote SD-SLS VA SAP TRANSP Sales Document: Item Data SAPK-603DDINSAPAPPL
VBEP Field Missing Remote SD-SLS VA SAP TRANSP Sales Document: Schedule Line Data
VBKD Field Missing Remote SD-SLS VA SAP TRANSP Sales Document: Business Data SAPK-603DDINSAPAPPL
CHVW_INC Field Missing Remote LO-BM VB SAP TRANSP Batch Where-Used List- N:M Assignment for Order
VBRK Field Missing Remote SD-BIL VF SAP TRANSP Billing Document: Header Data SAPK-603DDINSAPAPPL
VBRP Field Missing Remote SD-BIL VF SAP TRANSP Billing Document: Item Data SAPK-603DDINSAPAPPL
KONDH Field Missing Remote SD-MD-CM VKON SAP TRANSP Conditions: Batch Strategy - Data Division
LIKP Field Missing Remote LE-SHP VL SAP TRANSP SD Document: Delivery Header Data SAPK-603DDINSAPAPPL
LIPS Field Missing Remote LE-SHP VL SAP TRANSP SD document: Delivery: Item data SAPK-603DDINSAPAPPL
VALW Field Missing Remote LE-SHP VL SAP TRANSP Delivery Plan: Definition of Route Schedule
KNVV Field Missing Remote LO-MD-BP-CM VS SAP TRANSP Customer Master Sales Data
KNA1 Field Missing Remote LO-MD-BP-CM VSCORE SAP TRANSP General Data in Customer Master
FPLA Field Missing Remote SD-BF VZ SAP TRANSP Billing Plan
FPLT Field Missing Remote SD-BF VZ SAP TRANSP Billing Plan: Dates
TFPLT Field Missing Remote SD-BF VZ SAP TRANSP Date Type for Billing Plan Type
VBSK Field Missing Remote SD-BF VZ SAP TRANSP Collective Processing for a Sales Document Header
VBUK Field Missing Remote SD-BF VZ SAP TRANSP Sales Document: Header Status and Administrative Data
VBUP Field Missing Remote SD-BF VZ SAP TRANSP Sales Document: Item Status
WBHI Field Missing Remote LO WB2B_DDIC SAP TRANSP Trading Contract: Item Data
LFM1 Field Missing Remote LO-MD-BP-VM WLIF SAP TRANSP Vendor master record purchasing organization data
LFM2 Field Missing Remote LO-MD-BP-VM WLIF SAP TRANSP Vendor Master Record: Purchasing Data
ZPPWRKMAP Convertible -> Local BC ZDEV PTANAKI TRANSP PP-012: Work Center Mapping ECDK901192Hi,
What is the volume of data you copied. Also have you followed the best practice of minimal/no activity in the source client.
The dictionary differences seems to be becuase of some SPs not applied in your ECP system yet
Regards,
Sanujit -
Client copy Locked function module
HI,
I'm trying to make a client from client 400 to 420.
The problem is that the function module is locked by the current user (the same running the client copy); Then when It can't deletes the FM it states that it already exists:
"G_GLDB_POSTING_A already exists (include LGIVAU01)"
Afterwards the job gets cancelled due to a system exception ERROR_MESSAGE
The weird part is that it just happens for this client 420. There is also a copy from 400 to 410 and it works without a problem.
Any help would be greatly appreciated.Hi,
You can check the client copy lock from SCC4 also, but it really matters if your client copy finished or not.
If you still see the client copy lock there then it seems your client copy is not finished properly. Try to login your new client 420 and start deletion using SCC5 and after that you can start/schedule new client copy during weekends.
Regards,
Manish -
Dear All,
I am trying to do Remote client copy from Production to Dev system (two system landscape).Below is my hardware configuration of DEV and PRD system :
SAP - R/3 4.7(NU) , O/S - AIX , DB - ORACLE 9
PRD SYSTEM :
DATABASE Server
CPU - 2 (375 MHZ)
RAM - 3 GB
APPLICATION server
CPU - 2 (375 MHZ)
RAM - 2 GB
Database size of the Prd system is around 95 GB
DEV SYSTEM
CPU - 2 (375 MHZ)
RAM - 2 GB
I am doing test run first so that i can see if any errors come and also to estimate downtime of the PRD Server(as SAP recommends that no user should be login in target and source client while doing client copy).
From the last 24 hrs. it has just completed 2500 tables only. total tables are 27500 something(Non - Unicode system).Its running very slow....
Is there any way to improve the speed of Remote client copy ?
Else I am planing to do Export - Import of client.
Is there any way to estimate downtime of PRD Server while taking Export of client like In how much time Export of Source client will be completed....
Thanks & Regards,
RohitHi Rajesh,
>
. Make sure that it has the same permissions as /usr/sap/trans directory.
>
Do I need to share that directory too
> by default it will be "/usr/sap/trans".
>
> After Export you should revert it to default...
>
I want to go for the process you suggested.
I have a question for this;
1. My DEV server is the domain controller and when I login to my PRD server and run the command df -k (it shows /usr/sap/trans directory mounted to DEV server).
So if I change the location trans directory through STMS (system overview DEV-->Transport tool) will it get updated for PRD or I need to restart the machine DEV or PRD. do I need to do anything else like mounting etc so that PRD server can access the same to save the export file when I will be taking the export of PRD client.
Regards
Rohit
Maybe you are looking for
-
Changing the directory Structure of Jsp and web.xml files
Hi, I am using the JDeveloper 11g preview. Can any one tell me how to change the Jsp and web.xml files ( not in WEB-INF directory of the application) to another directory. Thanks in Advance Gopal
-
I reinstalled windows and wiped out everything. Is there any way to retrieve my library or at least my purchases??
-
Why is iTunes not showing all iPhone Apps to update?
When checking for updates for my purchased apps in iTunes I sometimes have a few to download - no problem there. My wife uses the same PC/iTunes but with her own Apple-ID. She can sign in and do the same. Every now and then there are available update
-
Will Logic 7.0.1 run on OS 10.4.6 or OS 10.4.8?
Hello all, I started a thread last night on this subject but I don't think I worded it correctly. Will Logic 7.0.1 run on OS 10.4.6 and above? I'm running 10.3.9 now with great results but need to upgrade my OS due to daisy chaining my Presonus FireP
-
IMac is freezing during start-up from OS X installation disk
My iMac 27" is freezing during re-installation of the complete machine from Leopard OS X installation disk. The machine ends up (also in safe mode) with a screen showing something like "horse steps in the snow" as shown in both pictures, which can be