Dump "conne_import_wrong_comp_type" during client copy

Hi gurus!!
Last week I tried to run a client copy with SAP_CUST profile but the next dump was generated:
Runtime Error CONNE_IMPORT_WRONG_COMP_TYPE
Exception CX_SY_IMPORT_MISMATCH_ERROR
Error when attempting to IMPORT object "TLINE".
What happened?
This is probably due to an error in the ABAP program.
When attempting to import data, it was discovered that the data type of the stored data was not the same as that specified in the program.
Error analysis
An exception occurred. This exception is dealt with in more detail below. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
was neither caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(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:
When importing the object "TLINE", the component no. 1 in the dataset has a different type from the corresponding component of the target object in the program "SAPLSTXD".
The data type is "N" in the dataset, but "C" in the program.
I checked that the report SAPLSTXD had not been changed and I can't found the reason of the error.
Can anybody help me?
Thank you very much in advanced.
Edorta.

Hi nick
I have already checked the note and executed the corresponding report and it shows an incorrect text filtering with the information extracted from the dump.
I have eliminated this wrong text in STXL and rescheduled the client copy for toningth. Tomorrow we will see the results.
Thank you very much in advanced,
Edorta.

Similar Messages

Error during client copy in GRC 10.0 -Application exit

Hello Experts,
After installing GRC 10.0,as post installation activity ,
we are doing client copy (accordence with the sap note 1505255).
but we are getting 'Application Exit Error' when executing method FDT_BEFORE_EXPORT_C:
any help would be appreciated.
regards,
vinay singh

HI
Can you attach client copy log for analysis.
Regards
Rajan Arora

Error on FMFMOAFNP1000001 table during Client Copy

Dears,
we are trying to run a Remote Parallel CLient copy from FNP-100 to FNQ-200.
The copy fails reporting this error :
"FMFMOAFNP1000001 CA-GTF DDIC Error (See SE14)"
We check both in source and target system and this table does not exist.Is not visible both in SE14 nor SE11.
We run the RFC comparison between the two systems and no DDIC differences are reported.
We try to apply note :
Note 1100875 - Client copy: DDIC error for tables FMFMOAsssmmmnnnn
but tx SNOTE says it's obsolete and cannot be implemented.
What we have to do to perform our client copy ?
regards

Hi Roberto,
Have you find any solution for this? coz we're facing the same error.
rgds,
fafizah.

During client copy tabels missing

hello,
while client copy from production server to quality server , error occured tables missing . plz help me.
regards
mohsin
+919867577675

Hi,
If you perform remote client copy ABAP dictionaty objects are not copied.
So, before you perform such copy ensure that both systems are consistent (SUPPORT PACKS + ALL CONFIG TRANSPORTS MUST BE EQUAL).
Compare in ABAP dictionary (se11) of both systems if the missing tables exist and if they are active.
If there is table on source system and is missing on target : look for transport which contains this table and apply it to target setrver.
Regards,
Wojtek

Application Exit Error during client copy

Hi ,
I have an ECC 6 system with DB2 database.I get an application Exit error while doing a client copy from 000 to 901.I could see all the tables where copied but the error comes in post processing stage.
Application exit error
function module :FIN_TR_CC_EXIT
package :FINB_TRANSPORT_TOOL
Program ended abnormally
I tried to delete the client and recreate it again.But still it gave the same error.I tried deleting the client gain.But the deletion job cancels .
Plz help me

HI
Can you attach client copy log for analysis.
Regards
Rajan Arora

Local Client Copy Error : Completed w. Dictionary Errors

Hi,
I have performed local client copy in the ECC 6.0 system.I mean SAP Netweaver 7.0 EHP1.I have selected source system 100 and target system 200 and profile is SAP_CUST with my User ID in 200 client having SAP_ALL,SAP_NEW.In the SCC3 throws error i,.e, Completed w. Dictionary Errors.The client 200 is newly created in the system.
Target Client             200
Source Client           100
Copy Type               Local Copy
Profile                      SAP_CUST
Status                      Completed w. Dictionary Errors
User                        I998769
Start on                   06.12.2009 / 12:47:59
Last Entry on          06.12.2009 / 14:00:12
Statistics for this Run
- No. of Tables            56872 of     58391
- Deleted Lines           5705995
- Copied Lines            5770444
Warnings and Errors
Table Name             Component          Package
A001                   SD-MD-CM           DDIC Error        (See SE14)
A004                   SD-MD-CM           DDIC Error        (See SE14)
A005                   SD-MD-CM           DDIC Error        (See SE14)
A006                   SD-MD-CM           DDIC Error        (See SE14)
A007                   SD-MD-CM           DDIC Error        (See SE14)
A009                   SD-MD-CM           DDIC Error        (See SE14)
A010                   SD-MD-CM           DDIC Error        (See SE14)
A012                   SD-MD-CM           DDIC Error        (See SE14)
A015                   SD-MD-CM           DDIC Error        (See SE14)
Nearly about 1520 tables are not copied from the source client and there is no dumps for that.Please,find below for the file log information which is highlighted in red color in log.
   Start of post-processing by application exits 13:57:48
   Automatic postprocessing of client 200 was incorrect -> long text
   Post-processing required for FINB_TR_CC_EXIT_TARGET
   Validation/substitution: Programs should be regenerated
   Selected tables           :         58.391
   Copied data in kBytes :      2.933.491
   Deleted data in kBytes :      2.845.416
   Program ended with error or warning, return code: W
   Runtime (seconds)         :          4.333
   End of processing: 14:00:12
Kindly,help me how to resolve the issue and provide relavent notes which is applicable to my error as per the SAP release.

Hi,
We encounter the same problem with different A***-tables. The problem is that these seem to be pooled tables. I had a look at sap note 1248769 and it mentions that the reconstruct-option is only liable for transparent tables. This seems to be right, as the option "Reconstruct" is greyed out in tx SE14 when we try to.
Any other options?
Jan
PS. Sorry for hijacking the thread, but it seems the topic starter is still looking for an answer as well
Edit: Found another SAP Note which seems relevant: 1171306. This note has the following segment in it:
If you still want to remove the inconsistency, you can proceed as described in the following. However, the table must be empty for you to be able to do this (you can check this with the report NROWS: start the report NROWS, enter DVPOOLTEXT for "Table 1" on the selection screen and choose Execute.)
1. Call transaction SE14.
2. Edit DVPOOLTEXT.
3. Delete the database table.
4. Create a database table.
If the pool is not empty and the data is required, it must be unloaded in advance and then read again after you have recreated the table.
Ofcourse we would like to preserve our data in the tables. Let's take a look at an example in our system: Table A017. This table has encountered the DDIC error during client copy. We have performed the following analysis actions on it:
Report NROWS mentions 116.390 entries for table A017.
In SE16 table A017 has 0 entries.
In SE14 I have performed two checks: The runtime object seems ok. When I check database object in SE14 the system returns the following message: "Table is not created in database".
Any tips?
Edited by: Jan Laros on Sep 8, 2010 2:25 PM

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

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,
PG

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.
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.

Audit Issue in QA after system restore and client copy

Hi Experts,
We have an audit issue and need your advise on that.
Our QA system was audited and auditors were looking for the approval tickets on which a user was created. I found that several users that were not created in QA and do not even exist in QA have their change logs in QA showing that user was created.
I researched it and found the steps that Basis and DBA's do when creating a new QA client.
1. Basis export user master and authorizations using SAP_USER profile from the target QA environment.
2. Then DBA's restore the QA Environment from the Production Backup.
3. Basis import back the preserved User master and roles using SAP_USER profile.
But when reading about this profile, I came to understand that change documents ( USH* ) tables are not exported and imported back. So that is why we have change logs in our QA from Production system.
So my question is how to solve this issue, where Auditors look at the change documents in QA and ask for the documentation though in reality these change documents are coming from Production. Should we ask for DBA team to truncate USH tables or is there a client copy profile that saves the change logs that we can export and import back.

Hi,
as you know the USH* tables belong to delivery class L. The tables in this class are never copied during client copy but you don't do client copy. Idea of deleting records from L tables after backup restore does not sound good because you will loose all data. As a workaround you could backup content of tables with delivery class L, export users SAP_USER, restore production backup, import users and import backup for tables with delivery class L. There is around 5000 L tables in ECC. Another approach could be to restore production on different box and do proper client copy to QA system.
Cheers

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

Steps should be taken to make a client copy say from dev to test using BDLS

Some one help to write up on real situation at any client site...by BASIS group
for SRM box..
Say client num in Dev is 100
and we want to copy all that to a test box where the client number is 101...
initially client 100 SRM box is pointing to R/3 say dev box 201
the new R/3 box is 202. And we have to point the 101 to 202. So I am just wondering the steps
taken by BASIS group to build the test env. 101 ---> 202

Hello,
we had experienced some problems during client copy with SRM in our earlier project.
I am not a basis guy but i can give you some hint for yr situation:
- Copy R/3 client 101 to 202 with the profile SAP_ALL
- change the SID with BDLS
- Copy SRM client 100 to 101 with the profile SAP_CUST
- change the SID with BDLS
- Now download the masterdata from R/3 to SRM
SRM client should never be copied with SAP_ALL profile because ,if done so the logical system for product masters is copied that of old client.
This creates total chaos and nothing works.
BR
Dinesh
reward if helps

Client copy question - Overwrite an existent client...?

Hi gurus,
I want to know if there is a problem to do a client copy over on a existent client, this is, now I have to do a client copy from 300 to 400 but the client 400 exists in the system, and I want to know if it´s possible and is any problem to do this or before this I must delete the client 400 and only after that I can do a copy from 300 to 400...?!
Best regards,
João Dimas - Portugal

Hello,
Everything depends on the size of your target client 400.
If this client contains a lot of data I recommend that you first perform a client delete via SCC5.
Otherwise you risk that your client copy will fail (extend problems, undo problems, ...) or will take too long (because data in 400 also needs to be deleted).
Advantage of deleting the client first is that the actual client copy will go much faster (because nothing needs to be deleted anymore).
Deletes during client copy or client delete often take most of the time, because this is done via non optimized SQL statements like (delete from table where mandt = '400').
There are a lot of SAP Notes to optimize client copies and especially client deletes !
Wim

Client copying.

Hi Gurus;
I want to copy a client which has every data except the master data.
which profile should i choose in this case during client copying.
The new client should have user, roles profiles customising changes of the source client but no master data.
Please update.
Thanks and regards

Hello Sandeep,
SAP_APPL for Application data and customizing data
also SAP_USER for User master records and authorization profiles.
If you need to copy customizing data and user master records together u can use SAP_UCSV
regards,
Anand

Client Copy error during client export / RX file is not getting

Hi Experts,
During the client export process of client copy in order to created two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Hi Experts,
During the client export process of client copy in order to create two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Client Copy error during client export / RX file is not getting generated

Hi Experts,
During the client export process of client copy in order to created two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Hi Experts,
During the client export process of client copy in order to create two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Dump "conne_import_wrong_comp_type" during client copy

Similar Messages

Maybe you are looking for