Client copy COMPUTE_INT_PLUS_OVERFLOW

Hi Gurus,
I have problem with client copy using SCC9, it wont process 4 tables even after active restart. I got ABAP dump, enyone can help resolving issue ?
Regards
SQL2008R2
Runtime Errors COMPUTE_INT_PLUS_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
caught in
procedure "SCC1_WRITE_FLOW_TABLE" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
In the current program "SAPLSCC1",
using '+' or 'ADD' to add the values 2147451769 and 73609466 resulted in a
value greater than 2147483647 or smaller than -2147483648. This
leads to a whole number overflow.

Here is the right procedure - All explanations are give above .. SAP replied in response to our OSS message . I have added a procedure for more clarity
1. Check the last entry in table CCCFLOW - for the destination client . ( For example MANDT value = 362 when CCopy is run from 100 to 362 client )
2. Make sure the TSTAMP corresponds to the time when the last Client Copy was started .
3. Make Sure NO Client copy is running - Stop / Cancel the Current client . For example if it was run in 10 parallel and 8 have already gotten this dump - the last 2 will also get this dump - so no point in wasting time to let them fail also eventually.
4. Change the value of NBRINS from 2,147,483,469 to 1 in table CCCFLOW for the last entry ( as above )
5. If SE16 is locked for change in the destination client - Do it on DB2 directly - something like this
update sapr3.cccflow set nbrins = 1 where mandt = '362' and tstamp = '20130812213848'
6. Restart the Client Copy and it will work Fine
7. This will result in loss of statistics in the Client Copy output - But when u r copying more than 2 billion lines of data - that is really not important ..
Hope this helps everyone

Similar Messages

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
Selvan

Hi 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

Client Copy from BWP to BWT

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

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

Client copy with configuration data in R/3. Is there any effect on EBP sys

Hi all,
We are using classic scenario. Our client is reorganizing their Org structure for that we need to do client copy with only configuration data.
In this scenario we are uploading the master and transactional data through ALE in order to retain the same number ranges and the same data in EBP system.
My doubt is when we do config steps Define logical system and assign the logical system to the client and define Idoc message types etc... Is it necessary to run BBP_LOCATIONS_GET_ALL job. If yes the same data like Plant and storage location and all master data will override the existing data or not. And what about the open Purchase orders and open goods receipts.
Can you please reply immediately. It is very urgent.
Thanks in advance

waiting online

Unable to log in to newly create client copy

I 'm attempting to create a new client from a newly installed ECC 6.0 IDES system. I go into SCC4 and create a new lient '200' and log off.
I try to log in to client 200 using sap* and pass and get wrong username or password error.
I can see the client listed in scc4, but can't log into it.
Any ideas?
Bob

Hello,
Having the previous question answered helped alot, but I do have another question:
Can I put the client copy on a different drive than the original?
I have SAP installed on the E: drive and would like to place the new copy client on the F: drive, can I do that?
Bob

Remote Client Copy Errors

Dears,
Today I am going to do remote client copy from PRD to QAS.
For it yesterday i scheduled Test run in simulation mode.As i am having two CPU for both Dev and PRD so I scheduled it with 6 Parallel Processes.
But my Test run failed with errors:
Copy Type                   Remote copy
                                  Test Run
Profile                          SAP_ALL
Status                          Ended with Errors
User                             SAP*
Start on                        14.08.2008 / 01:30:54
Last Entry on                14.08.2008 / 05:57:54
Statistics for this Run
- No. of Tables                 30,806 of       30,808
- Deleted Lines                     15
- Copied Lines               72748,776
Warnings and Errors
Table/Object       Component                Error
BKPF                 FI                       Read or Conversion Error
BSIS                   FI                       Read or Conversion Error
Thus showing read or Conversion Error in these two tables.
In System log of source system I also see these error:
ORA-01652 unable to extend temp segment by 2560 in PSAPTEMP
Database Error 1652 at SEL access to table BKPF.
Database Error 1652 at SEL access to table BSIS.
Please suggest how to resolve the issue.
Shivam
Edited by: Shivam Mittal on Aug 14, 2008 6:08 AM

Hello Shivam
How is your remote copy going on?
Did you increase the size of psap temp in order to carryon with the copy?
Your Source system is PRD system.Are you doing this copy while users are using the PRD system.
If not then this may not be result of client copy? or
if no user is logged in in your PRD system,You have to decide if this is due to client copy.
Let me know what corrective measure taken by you to completed the remote client copy?
normally we dont get this dump in the source system but I have psaptemp around 30 GB or more in al my systems so may be this might have not surfaced in my environment.
Thanks
Amit

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 K

Hi 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,
Rohit

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

Remote Client Copy failed

Hi,
I am doing remote client copy from (Development Server - ECD 140) to
our (Sandbox System - E6S 150) and the client copy keeps failing. I get
the below error message. Please advise what is the solution to this
problem? I am also copying the log file of the remote client copy below
Error Message:
Change documents are not copied
3 Tables cannot be converted
Critical differences: Missing tables: 125
Log file of remote client copy below
Target Client
150
Source RFC Dest.:
ECDCLNT140
System Name:
ECD
Client in Source System
140
Copy Type
Remote copy
Profile
SAP_ALL
Status
Cancelled. See Log
User
SAP*
Start on
08.05.2010 / 17:05:18
Last Entry on
08.05.2010 / 17:13:36
Last Action:
RFC DDIC System Comparison
Statistics for this Run
- No. of Tables
0 of     56508
- Copied Lines
0
Warnings and Errors
Table Name
Component
Package
/SAPTRX/EXT_AOT
Table Def. Missing Locally
/SAPTRX/EXT_EE
Table Def. Missing Locally
/SAPTRX/EXT_ETY
Table Def. Missing Locally
/SAPTRX/EXT_EVT
Table Def. Missing Locally
/SAPTRX/EXT_FLD
Table Def. Missing Locally
/SAPTRX/EXT_FLDS
Table Def. Missing Locally
/SAPTRX/EXT_FLDT
Table Def. Missing Locally
/SAPTRX/EXT_PAR
Table Def. Missing Locally
A850
Table Def. Missing Locally
A851
Table Def. Missing Locally
A852
Table Def. Missing Locally
A900
Table Def. Missing Locally
A901
SD-MD-CM
Different Field Names
A902
Table Def. Missing Locally
A903
Table Def. Missing Locally
A904
Table Def. Missing Locally
A909
Table Def. Missing Locally
A910
Table Def. Missing Locally
A911
Table Def. Missing Locally
A912
Table Def. Missing Locally
A933
Table Def. Missing Locally
A935
Table Def. Missing Locally
A942
Table Def. Missing Locally
A943
Table Def. Missing Locally
A944
Table Def. Missing Locally
A945
Table Def. Missing Locally
A946
Table Def. Missing Locally
A947
Table Def. Missing Locally
A948
Table Def. Missing Locally
A949
Table Def. Missing Locally
A952
Table Def. Missing Locally
A953
Table Def. Missing Locally
A954
Table Def. Missing Locally
A955
Table Def. Missing Locally
A956
Table Def. Missing Locally
A957
Table Def. Missing Locally
A958
Table Def. Missing Locally
A961
Table Def. Missing Locally
A962
Table Def. Missing Locally
A963
Table Def. Missing Locally
A964
Table Def. Missing Locally
A965
Table Def. Missing Locally
A966
Table Def. Missing Locally
A967
Table Def. Missing Locally
A981
Table Def. Missing Locally
A982
Table Def. Missing Locally
A983
Table Def. Missing Locally
A984
Table Def. Missing Locally
A985
Table Def. Missing Locally
A986
Table Def. Missing Locally
A987
Table Def. Missing Locally
A999
Table Def. Missing Locally
AFRU
PP-SFC-EXE-CON
Field missing locally
B901
Table Def. Missing Locally
B902
Table Def. Missing Locally
B903
Table Def. Missing Locally
B905
Table Def. Missing Locally
B906
Table Def. Missing Locally
B907
Table Def. Missing Locally
B950
Table Def. Missing Locally
B997
Table Def. Missing Locally
B998
Table Def. Missing Locally
B999
Table Def. Missing Locally
K9RECD1400004
Table Def. Missing Locally
KOTD601
Table Def. Missing Locally
KOTD602
Table Def. Missing Locally
KOTD603
Table Def. Missing Locally
KOTE901
Table Def. Missing Locally
KOTE902
Table Def. Missing Locally
LIKP
LE-SHP
Field missing locally
S001BIW1
LO-LIS-DC
Table has convertible differen
S001BIW2
LO-LIS-DC
Table has convertible differen
Z864DATA
Table Def. Missing Locally
Z864DIRECT
Table Def. Missing Locally
Z864INVOICETYPES
Table Def. Missing Locally
Z864ORDERTYPES
Table Def. Missing Locally
Z864RATES
Table Def. Missing Locally
Z864YENADJUST
Table Def. Missing Locally
ZBJOB_EMAIL
Table Def. Missing Locally
ZCSTMATNRLBL
Table Def. Missing Locally
ZCUSTJULIAN
Table Def. Missing Locally
ZFEDEX_COUNTRY
Table Def. Missing Locally
ZFEDEX_INBOUND
Table Def. Missing Locally
ZFEDEX_OUTBOUND
Table Def. Missing Locally
ZFI_EXCG_CURR
Table Def. Missing Locally
ZGBASE
Table Def. Missing Locally
ZGPRICE
Table Def. Missing Locally
ZHIPVALUES
Table Def. Missing Locally
ZIDOCDSS
Table Def. Missing Locally
ZLABOR_TIME
Table Def. Missing Locally
ZMACH_TIME
Table Def. Missing Locally
ZMM_GIMS_MTART
Table Def. Missing Locally
ZMM_WM_MAP
Table Def. Missing Locally
ZNGK_WORKFLOW
Table Def. Missing Locally
ZPPCRT
Table Def. Missing Locally
ZPPERRORLOG
Table Def. Missing Locally
ZPPEXPIRE
Table Def. Missing Locally
ZPPJOBMAP
Table Def. Missing Locally
ZPPNUM
Table Def. Missing Locally
ZPPWRKMAP
Table Def. Missing Locally
ZPP_COMP
Table Def. Missing Locally
ZPP_EXT_SOP
Table Def. Missing Locally
ZPP_MV_IN
Table Def. Missing Locally
ZPP_MV_OUT
Table Def. Missing Locally
ZPP_OPID_HU
Table Def. Missing Locally
ZPP_SOP_PBCR1
Table Def. Missing Locally
ZPP_SOP_PBCR3
Table Def. Missing Locally
ZPP_SOP_PBCR5
Table Def. Missing Locally
ZQM_CUST_BATCH
Table Def. Missing Locally
ZSD_NAPA
Table Def. Missing Locally
ZSD_PRICE_BLOCK
Table Def. Missing Locally
ZSD_SHPCND
Table Def. Missing Locally
ZSHIPVALUES
Table Def. Missing Locally
ZTABMAINT
Table Def. Missing Locally
ZUPS_COUNTRY
Table Def. Missing Locally
ZUPS_FEDEX_LOG
Table Def. Missing Locally
ZUPS_INBOUND
Table Def. Missing Locally
ZUPS_OUTBOUND
Table Def. Missing Locally
ZWMPACK2LABEL
Table Def. Missing Locally
ZWM_CUST_HU
Table Def. Missing Locally
ZWM_HU_HDR
Table Def. Missing Locally
ZWM_HU_ITEM
Table Def. Missing Locally
ZWM_IB_GR
Table Def. Missing Locally
ZYA1
Table Def. Missing Locally
ZYA2
Table Def. Missing Locally
ZYA3
Table Def. Missing Locally
ZYA5
Table Def. Missing Locally
ZYADDER
Table Def. Missing Locally
ZYATYPES
Table Def. Missing Locally
ZYAVG
Table Def. Missing Locally

I ran the report "RSCLICHK" on the target client and below are the results. There are some table differences. How do i syncronnize the tables so that i can successfully complete the remote client copy? Do i make the table changes on the source system or the target system? I was also told that the table changes will take days to complete. What is the most efficient way to syncronize the tables?
AFRU     Field Missing Local     PP-SFC-EXE-CON     CORU     SAP     TRANSP          Order Confirmations     SAPK-603DDINSAPAPPL
S001BIW1     Convertable     LO-LIS-DC     MCS     SAP     TRANSP          S001BIW1 * SIS: Customer Statistics
S001BIW2     Convertable     LO-LIS-DC     MCS     SAP     TRANSP          S001BIW2 * SIS: Customer statistics
A901     Fields Missing <->     SD-MD-CM     VKOK     VLOVELACE     TRANSP          Sales org./Distr. Chl/Division/Cust.group/PH2/Price grp/Pric
LIKP     Field Missing Local     LE-SHP     VL     SAP     TRANSP          SD Document: Delivery Header Data     SAPK-603DDINSAPAPPL
/SAPTRX/EXT_AOT     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
/SAPTRX/EXT_EE     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
/SAPTRX/EXT_ETY     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
/SAPTRX/EXT_EVT     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
/SAPTRX/EXT_FLD     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
/SAPTRX/EXT_FLDS     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
/SAPTRX/EXT_FLDT     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
/SAPTRX/EXT_PAR     Table Missing Local     SCM-EM     /SAPTRX/ATIF          TRANSP
A850     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A851     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A852     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A900     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A902     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A903     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A904     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A909     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A910     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A911     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A912     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A933     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A935     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A942     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A943     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A944     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A945     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A946     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A947     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A948     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A949     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A952     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A953     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A954     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A955     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A956     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A957     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A958     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A961     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A962     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A963     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A964     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A965     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A966     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A967     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A981     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A982     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A983     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A984     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A985     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A986     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A987     Table Missing Local     SD-MD-CM     VKOK          TRANSP
A999     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B901     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B902     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B903     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B905     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B906     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B907     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B950     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B997     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B998     Table Missing Local     SD-MD-CM     VKOK          TRANSP
B999     Table Missing Local     SD-MD-CM     VKOK          TRANSP
K9RECD1400004     Table Missing Local     CO-PA     KEG0          TRANSP
KOTD601     Table Missing Local     SD-MD-CM     VKOK          TRANSP
KOTD602     Table Missing Local     SD-MD-CM     VKOK          TRANSP
KOTD603     Table Missing Local     SD-MD-CM     VKOK          TRANSP
KOTE901     Table Missing Local     SD-MD-CM     VKOK          TRANSP
KOTE902     Table Missing Local     SD-MD-CM     VKOK          TRANSP
Z864DATA     Table Missing Local          ZDEV          TRANSP
Z864DIRECT     Table Missing Local          ZDEV          TRANSP
Z864INVOICETYPES     Table Missing Local          ZDEV          TRANSP
Z864ORDERTYPES     Table Missing Local          ZDEV          TRANSP
Z864RATES     Table Missing Local          ZDEV          TRANSP
Z864YENADJUST     Table Missing Local          ZDEV          TRANSP
ZBJOB_EMAIL     Table Missing Local          ZDEV          TRANSP
ZCSTMATNRLBL     Table Missing Local          ZDEV          TRANSP
ZCUSTJULIAN     Table Missing Local          ZDEV          TRANSP
ZFEDEX_COUNTRY     Table Missing Local          ZDEV          TRANSP

Remote client copy - scc9

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 Convertible

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

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

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

Client Copy back-end system

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

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

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

Hi Rohan,
Welcome to SDN!
This error means that you're trying to duplicate a record on the DB... check the IDOC number ranges... it might help
Regards
Juan
Please reward with points if helpful

Client copy COMPUTE_INT_PLUS_OVERFLOW

Similar Messages

Maybe you are looking for