SCM client copy- Problem in CIF

Hi,
Recently we done client copy from production system to test system for both SCM as well as ecc system.
Problem is Master data  is with logical system name of production system in APO.
We defined only logical system names for ECC and SCM client and kept name of buisness system group naming same as production to avoid this problem.
But there is problem in resoure external capacity logical system name is same as production only.
It is not feasible to delete all trasaction data and master data from APO and retransfer.
How can we change logical system name in resource?
I came to know that there  isprogram to convert  logical system name in customization as well as master data?
If this is true can you give name of program in APO as well as ECC if any?
Regards,
Santosh

Hi Santosh ,
Yes there is a report to change the logical system name from resource.
Report name is: /SAPAPO/CHANGE_BSG_RESOURCE for which the program  need be included in your system as per code given in Note 924136 - Change of the LOGQS (BSG) for resources.
This will resolve your requirement...
Regards,
Digambar

Similar Messages

  • R/3 Client Copy : Problem in BI.

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

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

  • Local client Copy problem using sccl in ECC 6.0- Long time

    Hi,
    My system ecc6.0 and I am started the client copy form 000 client to 100 client
    Now 25 passed but still the copy process not completed .
    I am create the client 100 in 000
    Then logged into 100
    Then start the client copy usuing sccl in background
    I am not run the test run
    Please check the below logs and suggest.
    Regards,
    Ravi
    Target Client                100
    Source Client (incl. Auth.)  000
    source Client User Master 000
    Copy Type                    Local Copy
    Profile                      SAP_ALL
    Status                       Processing...
    User                         SAP*
    Start on                     13.08.2008 / 16:25:57
    Last Entry on                13.08.2008 / 17:00:51
    Current Action:              Post Processing        Component
    -  Last Exit Program         /SAPCND/CC_GROUP_WS_NG AP-PRC-CON
    Statistics for this Run
    - No. of Tables                  54569 of     54569
    - Deleted Lines                    109
    - Copied Lines                 5101492
    Output Sm66 :-
    Sort: Server
    Server Name       No. Type PID      Status  Reason Sem Start Error CPU Time   User Report   Action          Table
    myhost_RD1_00 12  BTC     11391 Running            Yes              92662 SAP* SAPLSDNT Sequential Read D010TAB
       Client copy from 2008-08-13 16:26:00
       System ID............................ RD1
       Target client........................ 100
       R/3 Release.......................... 700
         Basis Support Package...............SAPKB70014
       Host.................................  myhost
       Start in background............. .....X
       User................................. SAP*
       Parameter
       Source client........................ 000
       Source client user masters............000
       Copier profile:.......................SAP_ALL
       Table selection
       Customizing data .....................X
       With application data................ X
       Initialize and recreate......... X
       Change documents are not copied
    Target client   100
    Source client   000
    User Name       SAP*
    SAP Release     700
    Profile name    SAP_ALL
    Total number of tables                       54.569
    Number of Customizing and syst. tables       34.654
    Number of application tables                 18.185
    Number of local tables (to delete)            1.730
    Total number of exit programs                    14
    Number of selection exits                         8
    Number of generation exits                        1
    Number of other exit programs                     5

    hello
    It is waiting for some post processing.
    Please check the
    Note 930816 - Cond. Maint. group not generated after remote client copy.
    971707 , 1176933
    This will help you.
    Thanks
    Amit

  • Client Copy Alternative - Hayes Technology

    We are looking at Gold Client from http://www.hayestechnology.com to replace the built in SAP client refresh and hopefully be the cure to all of our SAP client copy problems. I'm wondering if there is another alternative or who the competitors are for Hayes, as I would like to compare costs and functionality. Thanks for the help.

    I have worked with DSM Client Sync of EPI-USE: [www.labs.epiuse.com|http://www.labs.epiuse.com/documents/DSM%20e%20-%20Brochure_06-05-09.pdf], and found it to work pretty well.
    Even had a client that bought a competitor's product replace it with this. What makes it a little different is that it has two suites that is part of DSM - Client Sync for reducing the size and speeding up of client copies, then Object Sync to bring over individual business objects after the fact when needed for refreshes at the business object level.

  • Client copy failed in SCM without livecache

    Hi,
    I am executing client copy on a SCM-EWM system with profile SAP_ALL. Client copy failed with error. How can I find what tables are not being copied?
    The copy fail at post processing steps for this exit program "/SAPAPO/OM_CLNT_COPY_UPLOAD". My SCM system is not using LiveCache.
    How do I confirm the copy is successful?
    -Intan-

    Hi Deepak,
    I found this is error in the client copy logs :
    BEFORE_EXP_ADDRESS3 310 Q43C000004 320                                                                                             
    Exit program BEFORE_EXP_ADDRESS3 successfully executed 10:12:57                                                               
    Exit program BDC_DELETE_SESSION successfully executed 10:12:57                                                                     
    Error: Table /1CN/CPHPHU00001 error in DDIC - Check table with SE14                                                                
    The data object could not be created: The type /1C N/CPHPHU00001 does not exist.                                                  
    Error: Table /1CN/CPHPHU00002 error in DDIC - Check table with SE14                                                                
    The data object could not be created: The type /1C N/CPHPHU00002 does not exist.                                                   
    Error: Table /1CN/CPWPWO00001 error in DDIC - Check table with SE14

  • Derivation Rule Problem After A Client Copy

    Hello,
    Has anyone ever encountered a problem with derivation rules after a client copy is performed? After a client copy, we have "some" FM and GM derivation rules (not all of them) that have to be manually copied from the source to the target client (line by line by line by line). I'm thinking that there has to be a way to prevent this since some rules are fine after the clent copy. Your input would be greatly appreciated.
    Will

    I believe that we have resoved our issue. For the derivation rule values that would never copy, we re-created these again starting in DEV and transported the derivation rules throughout the entire landscape (QAS and PRD). Evidently some derivation rules (and the related values stored in the tables) were created directly in Production. During a client copy the values in the tables for the derivation rules that were created directly in our Production environment would not copy to our QAS environment. Those rules were stored in a table named FMFMOAPRD1000122. Note that PRD is in the table name. After re-creating the rule and transporting it through the landscape, the table was named FMFMOADEV1000152 (for example).

  • SCM / PI Client Copy

    Does anyone have experience not using the preconfigured client (001) in PI or SCM?  We've copied those to 010 to match the productive client number of the rest of our systems.
    Is this a bad idea?  Should we stay with the preconfigured client?  It does say in the installation post steps to do a client copy as well.  Thank you.
    ~TJ

    Hi TJ
    No, think that is absolutely fine.
    We have done that on numerous occasions.
    Copying from client 001 is as good as working in 001.
    The client copy should be fine for 010, which you have done.
    Thanks
    ABhi

  • BI-RFC problems after client copy

    Hi all
    Client copy was done and after that when I tried to load data in BW, it ran for long time and finally showed cancelled in SM37. When I checked the source system in RSA1, it gave two messages.
    1.Incorrect IDoc type ZSAC008 in the ALE definition of the source system RSAR373
    2.Result of the destination check: Password logon no longer possible - too many failed attempts RSAR375.
    In long text of message 1 suggestion was to enter IDoc type ZSAB003. In SM30 for Message Type RSSEND Basic Type ZSAB003 Release field is empty. Is this error because of this?  After client copy is there a way to restore the settings back to how it was set initially in the development server? Basis told ALEREMOTE & BIWREMOTE are not blocked. What is missing here? Thanks a lot in advance. 
    Subin

    There are a few things need to be performed on basis side after copy .
    1. Restore of Logical system.--> check with Baisis team wheather they have performed this action or not after copy.
    2. Check your source system connection, in rs1-- source sytem --check
    3. Change the aleremote or Bwremote passwords.
    4. Try to logon to your sourcesystem ( from SM59 Tcode) Remote logon.
    Hope this helps.
    Regards,
    Reddy
    Edited by: Reddybl on Apr 1, 2010 11:56 AM

  • 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

  • Scm system copy using brbackup

    Hi Gurus,
    I am doing scm system copy using brbackup methos, while checking source, and target system (both running on SUSE 10, Patch Level 3)  I found that both have different kernek patch version.
    Would like to know if this is a problem, pls. find below release information:
    source
    Linux 2.6.16.60-0.66.1-smp #1 SMP Fri May 28 12:10:21 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
    2.6.16.60-0.66.1-smp
    openldap2-client-32bit-2.3.32-0.36.91
    openldap2-client-2.3.32-0.36.91
    target
    Linux 2.6.16.60-0.69.1-smp #1 SMP Fri May 28 12:10:21 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
    2.6.16.60-0.69.1-smp
    openldap2-client-32bit-2.3.32-0.37.1
    openldap2-client-2.3.32-0.37.1
    Any hep, and reply is highly appreciated.
    Thanks
    sahmad

    Potentially not... These are OS patches and you are restoring the database.
    Having said that is is highly recommendable that your environment is consistent. Also check in PAM that the version of OS is supported.
    Regards
    Juan

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

  • 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 (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

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

Maybe you are looking for