Error After client copy

Hi all,
I did a client copy in ECC IDES  with client 800 as source client.As per the logs , copy is successful.The profile usedf is SAP_ALL.After the copy we logged into the new client which was
created and it looked good. Checked the Logs in SCC3 and it said that client copy was finished sucessfully.However now when we go and execute transactions  MM01 and VA01, it is  giving a error  saying 
Batch definition level not found.System inconsistency!
Not sure what went wrong,  Any suggestions would be Helpful.
Regards,
Chaitanya.

hi...
    send the full details of ur client copy....
   what is ur target client where u did this client copy .. i mean in prod dev

Similar Messages

  • AFAB: Runtime Error after client copy.

    Hi all,
    I'm having a problem with the transaction code AFAB (post client copy). After client copy from PRD to DEV, I'm encountering this runtime error "SAPSQL_ARRAY_INSERT_DUPREC -   The ABAP/4 Open SQL array insert results in duplicate database records." whenever I tried to perform AFAB. Test run was executed successfully but I cannot complete the actual background processing.
    I have try with other asset (in the same client) and encounter the same problem. Likewise, I have successfully completed the depre. if I try the same and other asset (in a different client on the same server).
    I've check the number range in FBN1 and have verified that the range is correct.
    Any advice as to how I can solve this problem?
    Thank you.
    Regards.
    p/s: if there is duplication, how do I find where the duplication is located and how do I remove this duplication?
    p/s 2: the standard SQL that is having this problem is "INSERT COBK  FROM TABLE COBK_INS."
    Edited by: Sek Yao Ooi on Aug 5, 2010 5:21 AM

    Solution obtain from snote-83731 ; thanks to SAP-Marketplace's support.
    Issue solved.

  • Data Load Error after Client copy on Source System

    We did a client copy to our QAS source system.  After that was complete, I tried to do a couple of full data loads.  But they fail.  The only errors I see are on the source system when I try to manual update the Idocs.  They are:
    EDI: Partner Profile not available
    Entry in inbound table not found
    Is there a step I need to take after the client copy and before the loads?  I have a feeling that I'm forgeting something.
    Thanks,
    Chris

    Hi Chris,
    Check the following.
    1> Go to WE20 check whether you are able to see two logical system in "Partner Type LS" one for Source and one for Myself.
    2> If you say Yes for <1> then check in both the logical system, in the classification tab, partner status should be 'active'.
    3> Check you have used REMOTE USER in main and in Outbound and inbound Parameters "Post Processing Permitted tab " for each Message type.
    4> go to out bound message type and check the "Receiver port" pointing to correct RFC destination for both ( Source and Myself logical system).
    If your answer is no for <1> then perform all the steps.
    Hope this will help you.
    Suneel

  • SAP* not authorized after Client copy

    Dear All,
    Here's the scenario:
    1. Created a new logical system for a new Quality client 230.
    2. Created the new client 220
    3. scheduled a test remote client copy from the new client, source Production. (Successful)
    4. Scheduled the actual client copy to run last night.
    5. Today morning, I'm logging into the new client with SAP*, it prompted me to change password.
    6. I want to look for the client copy logs (SCC3), but getting "not authorized"
    7. Checked all other transactions, all giving "not authorized" error
    Any help would be appreciated. Thanks in advance.

    Dear Reza,
    Better to go for Client Export Import process . This is what SAP reccomends for coping clients  between
    different systems ( Like from Production to Quality ) as the remote client copy has many
    disadvantages..
    For this 1 ) you should get the downtime of production system and do the client export process .
    SCC8 . See the logs at scc3 .
    2) Copy the datafile and cofile to the Source system
    3) Import it usting stms_import .
    Monitor the logs as the logs will be grown massive and make sure enough space is there.
    4) After client copy , go for post processing ( scc7 ) .
    Hope you are clear and feel free to get back if any doubts.
    Regards,
    Nibu

  • TCURM in target client empty after Client Copy

    Hi Experts,
    Has anyone encountered situation whereby TCURM does not contain a record for the target client after Client Copy process is completed? Is this a feature or bug?
    Regards

    Hi ,  I  user the exclude tables option to exclude some tables.
    but I have another problem:  the client copy still failed.  I get these  informations:
    table/object   component                         error
    ANLU           FI-AA-AA                   Field missing locally
    C905            SD-MD-CM                Different Field Names
    IMPTT          PM-EQM-SF-MPC      Field missing locally
    how can i finish my client copy ?   can you give me the solution
    thanks very much

  • Error in client copy - EFG_FORM_CC_EXIT_AFTER

    Hi,
    I am getting the following error while doing client copy,
    it has copied all the tables , but at the end it gives message,
    ===============================================
    Target Client           500
    Source Client           000
    Copy Type               Local Copy
    Profile                 SAP_CUST
    Status                  Successfully Completed
    User                    SAP*
    Start on                26.09.2007 / 01:48:17
    Last Entry on           26.09.2007 / 02:56:00
    Statistics for this Run
    - No. of Tables             53644 of     53644
    - Deleted Lines                 2
    - Copied Lines            5090006
    arnings and Errors
    Table Name              Component  Package
    EFG_FORM_CC_EXIT_AFTER  CA-GTF-PWB Program Exit has Syntax Errors
    EFG_FORM_CC_EXIT_BEFORE CA-GTF-PWB Program Exit has Syntax Errors
    ============================================================
    please advice.
    regards,
    SM

    Hi Shark,
    Your client copy seems to be ended with just warnings. As mentioned, please correct those 2 forms in the source system and try to import to target client. Discuss with apps member whether they need these 2 mentioned forms. If they don`t need it ,you can ignore the warnings.
    Perform post processing after client copy.
    regards,
    Vinodh.

  • 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

  • After Client copy - No Authroization Issue

    Dear All,
    Good Day,
    We copied Production data to Quality system through Transport management System. We checked those data copied successfully. After client copy, login in Quality also done successfully
    But unable to run any transaction. no authroization error occur for all the transaction for all the user id.
    "You are not authorized to use transaction XXXX"
    Kindly advice me to resolved this issue.
    Best Regards,
    KSK

    Was security transported down? Can you log into the system as SAP*? If so, check to make sure that all the roles and user masters where copied. You can also run st01 to do an authorization check.

  • Background jobs pointing to old client after client copy

    Hello
    We have recently completed system refresh from PROD system to TEST system.
    We have created new client in new TEST system. Background jobs are copied properly from old client to new client.
    But all these jobs are pointing to old client only. We have deleted old client.
    Hence all these jobs get cancelled.
    How shall I change the client of all the jobs from old to new one.
    -Nandu More

    Please check the thread:
    Error in Background Jobs After Client Copy
    Check some of the TBT* tables.

  • Unable to find product categories after client copy

    Hi all,
    We have copied  clients from an existing ones for both SRM and ECC. After client copy we have followed standard procedure after client copy i.e.
    Run transcation BDLS
    created new RFC connections
    changed attributes using the Attributes replace report
    created new distributon model
    maintained CRM parameters
    maintained new site attributes in SMOEAC transaction
    maintained entries in table TWPURLSVR
    however , when i try to create a shopping cart,  I cannot see any product category. The extended attributes for product category point to new ECC client becuse we have run the attributes replace report.
    however in the product category table , COMM_CATEGORY , the product categories listed are all for the old ECC client
    When i tried to load the Object DNL_CUST_PROD1 using transaction R3AS in SRM and tried to pull from new ECC client , it is in runing status for a long time and new categories with new ECC backend reference are not being replicated in the SRM.
    Can you tell me why this could be happening ? How can i get the product categories from new ECC backend into my client?
    Regards,
    Mangesh

    problem solved
    i was using wrong parameters in BDLS

  • Change Myself system in RSA1 trx after client copy

    Hi,
    I have installed SCM 2007 system.
    As post-processing step i have configured myself system in RSA1 trx in the 001 client.
    Now, i want to perform client copy and use that new client 100 as Prod client. What are the steps required to change myself system to point to the new client?
    Please help.
    Regards,
    Chintan

    HI,
    As logical systems are used to define you can use BDLS to convert them after client copy.
    Go through :Note 325470,325525.
    Thanks.

  • Error message: no valid initialization after client copy

    Hi,
    We recently did a client copy of our quality BW and R/3 systems from preproduction. In the 'new' clients we have problems with the delta process for 2LIS_13_VDITM. We get an error message that there was no valid initialization in the system, where in fact a valid initialization has taken place (everything from preprodcution was copied).
    The source systems setting where corrected using BDLS, but the entries in R/3 tables roosprmsf / roosprmsc were still pointing to the old system. This has now been corrected.
    One problem remains. There is no entry for 2LIS_13_VDITM in table RSSDLINIT. I suspect that this causes the error message. Can anybody confirm this ? Is there a standard way to add the correct entry (with the package number of the init package) in table RSSDLINIT or realign table RSSDLINIT with table roosprmsf in R/3 ?
    Thanks in advance !

    Hi,
    After system copy. You will ahve delet your whole data and reload every thing.
    In case you are getting dump when you double click infopacakge then delete your data source entry in RSA7 in source system and then go for fresh init load and then continue with delta load. Before goign for fresh init load you will have to first delet the init load entry.
    This must help
    Regards,
    Rohini
    Message was edited by: Rohini Garg

  • Error FDBL020 after client copy

    Hello Friends !
    After a client copy i having a problem in DEV that do not allowed archiving :
    in transaction FS10N, when i am trying do execute appear the error: No data read for fiscal year 2006 (error FDBL020), i tried applying the note 302263 (deleting the attributes of programs)but the attributes has been deleted. Anybody know a solution ?
    This problem not occur in QAS.
    Thank´s a lot..
    Claudenir

    hi...
        send the full details of ur client copy....
       what is ur target client where u did this client copy .. i mean in prod dev

  • 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

  • PI 7.0 ABAP Proxy Wrong Namespace after Client copy

    Hello,
    i am looking for an PI expert because we have some problems with a standard ABAP proxy interface.
    We use the FSCM Module and we send Credit Commitment Notification from a SAP ECC 6.0 to PI 7.0.
    We use the Interface CreditCommitmentNotification_Out and it works fine on the Development System (D46). But on the integration system (Q46) it doesn't work. The Q46 is build up from our production system (P46) by a system/client copy.
    We get the error:
    The payload include a wrong namespace for the proxy interface.
    wrong: xmlns:prx="urn:sap.com:proxy:P46:/1SAI/TAS7DF374ECCA722B654BFE:700:2007/10/04"
    correct: xmlns:prx="urn:sap.com:proxy:Q46:/1SAI/TAS7DF374ECCA722B654BFE:700:2007/10/04"
    I dont know why we get the wrong namespace. I check the transaction SICF, SPROXY and SXMB_ADM  and compare it with the customizing on our development system. I didnt find any gap.
    Please help me if you have some ideas what is wrong on our system.
    Regards
    Jürgen 8-))

    Hi,
    We experience the same problem after an upgrade from ECC 5.0 to 6.0
    How did you solve this?
    Ron

Maybe you are looking for

  • How to delete photos from iPhone but not iPhoto?

    iPhone 5S on iOS 8.1.2 with over 6,000 pictures, brand new Macbook Pro on 10.10.1 Yosemite. All my photos are synched to iPhoto, and I want to delete the photos from my iPhone to clear up storage. My main concern is not losing the photos in iPhoto th

  • Unable to install MS-Office 2011 Update 14.1.4 on 10.6.8

    Hello, I've got some trouble installing the actual available Update 14.1.4 for my Office 2011-Home and Student Editon. When I try to install I receive the Error-Message "Office 2011 14.1.4 cannot be installed on this volume. For this Software, Mac-OS

  • Getting empty namespace (xmlns="") in output of XSLT

    Hi, I am trying to copy data from an input XML to output using XSLT in ESB 10.1.3.4. But empty namespaces are getting added to some tags. Input: <Root> <Node> <Parent1> <Child1> <Child2> <Child3> </Parent1> <Parent2> <Child1> <Child2> <Child3> </Pare

  • BPM Career

    Hi, I took training in Oracle BPM and looking for job now. I am doing a pilot project to get more understanding. I need some guidence from industry experinced BPM people. I may have some basic stupid questions. I do not want to post the questions on

  • Is Content Aware available in PSE10?

    Is Content Aware Available in Photoshop Elements 10 Message title was edited by: Brett N