XPRA error unprocessed BDocs

Hi All - I am upgrading from CRM2007 to 7.0 and I am facing a issue in XPRA_UPG phase where there are unprocessed BDocs. I used transaction smw03 to display them, but I am not sure how to process them or delete them.
A2PE/SAPCND/CUSTOMIZING 212 Generation for application "CRM", Usage "BO" and table "SAP12132" failed
A2PECND_MAST 299 Generation interrupted; process mBDocs first (see description)"CND_M_SUP"
A2PE/SAPCND/GENERATOR 215 Generation was prevented by an object.
A2PE/SAPCND/CUSTOMIZING 212 Generation for application "CRM", Usage "PR" and table "SAP12132" failed
A2PECND_MAST 299 Generation interrupted; process mBDocs first (see description)"CND_M_SUP"
A2PE/SAPCND/GENERATOR 215 Generation was prevented by an object.
Any input will be appriciated.
Regards,
K

Hi,
Have you got the answer to this question? I am also getting this error while upgrading CRM2007 to CRM7.0 in XPRAS_UPG phase.
CURRENTPHASE XPRAS_UPG
1PEPU203X> Messages extracted from log file "SAPR701WD1.CMS" <
  Long text:
    Cause
      During the upgrade, a message relevant for postprocessing was written
      to a log file. This message is not dealt with until the end of the
      entire upgrade. The upgrade continues.
    System Response
      The upgrade stops in phase CHK_POSTUP. To create the reference to the
      original log file, this message is generated by R3up.
    What to do
      Note the messages following this message and proceed according to the
      instructions.
A2PECND_MAST 271 Error when generating table "CMBCCPSAP12130": Incompatible change (Description)
  Long text:
    Cause
      You have tried to generate a CDB table. By doing so, the already
      existing table has been changed in such a way that the corresponding
      synchronization BDoc has been made incompatible. The incompatible
      change could lead to data loss, and is therefore only possible with the
      help of the CND_MAST_GEN_TRANSFER_OBJECTS report. This report should be
      executed online.
    System Response
      Generation of the CDB table is terminated.
    What to do
      Inform your system administrator.
    Tasks for system administration
      Check whether the table, and therefore, also the BDoc may be made
      incompatible. If this is the case, execute this with the
      CND_MAST_GEN_TRANSFER_OBJECTS report.
A2PECND_MAST 271 Error when generating table "CMBCCPSAP12131": Incompatible change (Description)
  Long text: see above
A2PECND_MAST 271 Error when generating table "CMBCCPSAP12132": Incompatible change (Description)
  Long text: see above

Similar Messages

  • EhP4 installation ABAP+Java addin. XPRAS Errors in SAPR-603DWINEARETAIL

    Chaps, 
    I am in the downtime phase of this EhP4 installation and the Java is running fine.  I am getting this error with the ABAP in file XPRASUPG.ELG:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR-603DWINEARETAIL.PDS
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    A3EEFDT_TRANSPORT 125 BRF+: <<< *** BEGIN: Content from Application Component  "LO-MD-MM"  *** >>>
    A3EEFDT_TRANSPORT 025 BRF+: <<< BEGIN: Messages for IDs (&2"46F4B99CF7CF0C0BE10000000A4248A4"/&3" ")  &1"Function RS_PROCESS_PRICAT_K003" >>>
    A3EEFDT_CORE 065 Name "RS_PROCESS_PRICAT_K003" has already been used
    A3EEFDT_TRANSPORT 026 BRF+: <<< END  : Messages for IDs (&2"46F4B99CF7CF0C0BE10000000A4248A4"/&3" ")  &1"Function RS_PROCESS_PRICAT_K003" >>>
    A3EEFDT_TRANSPORT 025 BRF+: <<< BEGIN: Messages for IDs (&2"46FF585C33511112E10000000A4248A4"/&3" ")  &1"Function RS_MAP_CIN_TO_PRICAT" >>>
    A3EEFDT_CORE 065 Name "RS_MAP_CIN_TO_PRICAT" has already been used
    A3EEFDT_TRANSPORT 026 BRF+: <<< END  : Messages for IDs (&2"46FF585C33511112E10000000A4248A4"/&3" ")  &1"Function RS_MAP_CIN_TO_PRICAT" >>>
    A3EEFDT_TRANSPORT 126 BRF+: <<< *** END  : Content from Application Component  "LO-MD-MM"  *** >>>
    A3EEFDT_TRANSPORT 034 BRF+: Object activation failed (step: "Check" )
    2EEPU133 Errors occurred during post-handling "FDT_AFTER_IMPORT" for "FDT0001" "T"
    Any suggestions?
    Regards,
    Graham

    Hi,
    In the end I ran out of patience and decided to ignore the error to get it through to the end. Later, SAP responded as follows:
    "The issue depends on a deleted function and a new function with the samename within one application. With note 1263261 the problem should be
    solved. Maybe you also have to install note 1301695 after it."
    I hope this helps,
    Regards,
    Graham

  • Error CHARVAL_MSG  Bdocs

    I am having some errors in smw01 on CHARVAL_MSG Bdocs ,
    the error states :
    SMW3  Technical error occured: Service , BDoc type OBJCHARACTERIS, Message Object already subscribed. Bulk
    SMO8 Service that caused the error: CRM_CHARVAL_MSG_MSA
    Error overview :
    BDoc State     E01
    BDoc State Description     Technical error (incomplete)
    BDoc Type (Generation Name)     CHARVAL_MSG
    Flow Context     MO1
    Flow Context Description     mBDoc Notification
    Send date     05.04.2007
    Queue name     CSACHARVAL457EE6B4DE
    DDIC type of classic part of BDoc     /1CRMG0/CHARVAL_MSG
    DDIC type of extension part of BDoc     CRMT_MKTPROF_MBDOC_CHARVAL_TAB
    BDoc Message Identifier     4614FE01FA40202C00000000A7690A0E
    Root ID     457EE6B4DE8E006800000000A7690B0B
    Can anybody help me on how to resolve this issue or can anybody explain where I should start in order to verify what caused the error ?

    Hi Wim,
    Currently I am facing the same issue, could you please let me know how you resolve the issue.
    Regards,
    Harish.

  • Inbound qRFC Error/unwanted BDoc's on SolMan

    Hello,
    I experience the problem described in Note 1960627 - Inbound qRFC Error/unwanted BDoc's on Solution Manager System.
    I would like to deactivate the creation of the BDoc's in SMW3_00 but am at a loss here: How do I actually do it?
    Best Regards and thanks for your help in this !
    Thorsten

    Please check dumps in ST22 and for the mentioned job in SM37 (RDDEXECL).
    Markus

  • XPRA error.

    the error has occured during the upgrade and it goes like this....
    LIST OF ERRORS AND RETURN CODES  *******
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700HEC.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700XD3.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700ZE5.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700WE4.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700ZEA.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700WE3.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700WE5.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700WE6.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700WE2.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700ZE2.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    2EEOL555 Object type '"BUS20370"' could not be generated
      Long text:
        Cause
          The object type could not be activated.
        What to do
          Select the function 'Check' in the object type and correct the error
          found. Then try to activate the object type again.
    2EEOL555 Object type '"BUS20350"' could not be generated
      Long text: see above
    2EEOL555 Object type '"BUS20310"' could not be generated
      Long text: see above
    2EEOL555 Object type '"BUS20300"' could not be generated
      Long text: see above
    2EEOL555 Object type '"BUS20310"' could not be generated
      Long text: see above
    2EEOL555 Object type '"BUS20360"' could not be generated
      Long text: see above
    2EEPU133 Errors occurred during post-handling "SWO_OBJTYPE_AFTER_IMPORT" for "SOBJ" "L"
      Long text:
        Cause
          During the upgrade, import post-processing &V#& was performed for
          object &V#& &V#&. Errors were reported.
        System Response
          The upgrade is interrupted.
        What to do
          You will find the error messages for post-processing &V#& directly
          before this message. First read these error messages and the respective
          long texts. You will find further information there on correcting the
          errors.
          If this information is not sufficient, look for error notes in the
          SAPNet - R/3 Front End. Keywords you can use for the search are
          the name of post-processing &V#& or
          the message numbers of the preceding error messages. The message number
          appears in the header of the long text display.
          If you enter a problem message for the error, enter the following
          information:
          the name of post-processing &V#&
          the message numbers of the preceding error messages
          the components in which the error occurred
    2EEPU136 The errors affect the following components:
      Long text:
        Cause
          During the upgrade or import of a transport request, errors occurred
          which affect particular components of the SAP System.
          The following messages list the components in which the errors
          occurred.
        System Response
          The upgrade or import of the transport request is interrupted.
        What to do
          Read the preceding error messages and their long texts for more
          information on correcting the errors.
    2EEPU137    "BC-DWB-TOO-BOB" ("Business Object Builder")
      Long text:
        Cause
          During the upgrade or import of a transport request, errors occurred in
          the component
             &V#& (&V#&).
        System Response
          The upgrade or import of the transport request is interrupted.
        What to do
          Read the preceding error messages and their long texts for more
          information on correcting the errors.
    1 ETP111 exit code           : "8"
    >>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
    XPRAs are application reports that run at the end of an upgrade.
    Most XPRA reports have a report documentation that explains what
    the report does and how errors can be corrected.
    Call transaction se38 in the SAP system, enter the report name,
    select 'Documentation' and click the 'Display' button.
    >>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700ZE7.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700ZE8.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700ZE9.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700ZE1.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1 ETP111 exit code           : "0"
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    XPRA ERRORS and RETURN CODE in SAPR700WE1.YBA
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1AETR012XProgram terminated (job: "RDDEXECL", no.: "01202800")
      Long text:
        Cause
          Program "&V#&", which was started in the background, was terminated
          abnormally.
        System Response
          The system created a job log for the terminated program.
        What to do
          Proceed as follows:
          Log onto the system in which the program was executed. The system is
          specified at the beginning of the transport log.
          Then call transaction SM37 to display the job log.
          Enter "&V#&" as job name and "DDIC" as user name.
          Restrict the starting date to the starting date specified in the
          transport log.
          For the other selection criteria, select only jobs with the status
          "cancelled". Then press <LS>Execute</>.
          A list of the jobs satisfying the selection criteria is displayed.
          You can display the log by pressing <LS>Job log</>.
          If the list contains several jobs, you can select the job with the ID "
          &V#&" with <LS>Display</> -> <LS>Job details</> or define further
          details for the selection criteria in the initial screen of transaction
          SM37.
          If the ABAP processor reports cancellation, double-clicking on the
          corresponding message in the job log branches to the display of the
          corresponding short dump.
    1AEPU320 See job log"RDDEXECL""01202800""YBA"
    1 ETP111 exit code           : "12"
    >>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
    XPRAs are application reports that run at the end of an upgrade.
    Most XPRA reports have a report documentation that explains what
    the report does and how errors can be corrected.
    Call transaction se38 in the SAP system, enter the report name,
    select 'Documentation' and click the 'Display' button.
    >>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
    please help out if someone else has faced this problem earlier.

    I got the same error when upgrading from 4.6c to ECC6
    In SM37 I found that job RDDEXECL is cancelled. Job log gives that
    The following syntax error occurred in program "SAPLSNR3 " in include "LSN
    "The type "BADI_NUMBER_GET_NEXT" is unknown."
    This can be solved by activating Enhancement Sport: BADI_NUMBER_GET_NEXT in txn SE18. Info can be found in OSS note 980194.

  • Upgrade with XPRA ERRORS message at xpras_upg

    Hi,all
       I am upgrading sap ERP 4.72 (win2Ksql2K_sp3) to ECC6(win2003sql2K+sp4). Prepare is sucess.When the upgrade process is running xpras_upg,I got error message below.
    XPRA ERRORS and RETURN CODE in SAPR700ZE1.PRD
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    A2EESMMSS_ANALYZE 000 SQL error "446": "Cannot resolve collation conflict for concatenatio" "n operation." " "
    2EEPU133 Errors occurred during post-handling "MSS_SDBP_AFTER_IMP" for "SDBP" "L"
      Long text:
        Cause
          During the upgrade, import post-processing &V#& was performed for
          object &V#& &V#&. Errors were reported.
        System Response
          The upgrade is interrupted.
        What to do
          You will find the error messages for post-processing &V#& directly
          before this message. First read these error messages and the respective
          long texts. You will find further information there on correcting the
          errors.
          If this information is not sufficient, look for error notes in the
          SAPNet - R/3 Front End. Keywords you can use for the search are
          the name of post-processing &V#& or
          the message numbers of the preceding error messages. The message number
          appears in the header of the long text display.
          If you enter a problem message for the error, enter the following
          information:
          the name of post-processing &V#&
          the message numbers of the preceding error messages
          the components in which the error occurred
    2EEPU136 The errors affect the following components:
      Long text:
        Cause
          During the upgrade or import of a transport request, errors occurred
          which affect particular components of the SAP System.
          The following messages list the components in which the errors
          occurred.
        System Response
          The upgrade or import of the transport request is interrupted.
        What to do
          Read the preceding error messages and their long texts for more
          information on correcting the errors.
    2EEPU137    "BC-DB-MSS" ("Microsoft SQL Server")
      Long text:
        Cause
          During the upgrade or import of a transport request, errors occurred in
          the component
             "BC-DB-MSS" ("Microsoft SQL Server").
        System Response
          The upgrade or import of the transport request is interrupted.
        What to do
          Read the preceding error messages and their long texts for more
          information on correcting the errors.
    1 ETP111 exit code           : "8"
    >>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
    XPRAs are application reports that run at the end of an upgrade.
    Most XPRA reports have a report documentation that explains what
    the report does and how errors can be corrected.
    Call transaction se38 in the SAP system, enter the report name,
    select 'Documentation' and click the 'Display' button.
    >>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
    I have searched  in sap notes and SDN,but no help to me.
    Can give me solution?
    Thanks a lot.

    Sorry,I have solved this problem.
    The version of  my sql is sql2k with sp3 before,but sp3 only support CP850_BIN. After sp3,microsoft support CP850_BIN2 and BIN.
    The default installation of the sql2k sp4 software from sap is supported CP850_BIN2 .
    So,the versionof  the sql server is BIN,and database is BIN in my ERP 4.72. Then I install sql2k with sp4 with BIN2,and database is BIN.
    I must change the BIN&BIN2 with instcoll.exe.
    More information,please read note 505906,600027.
    Thanks.
    Wensent Lee

  • Mapping error in BDOCS

    Hi Experts
    Daily we have BDOCS with Bdoc state description "Mapping error" and following errormessage  "Processing of document with Guid DEE4C70ABC20D1F18A4900101825B820 is canceled" and " Validation error occurred: Module CRM_DOWNLOAD_BTMBDOC_VAL, BDoc type BUS_TRANS_MSG.
    When we reproces the Bdoc it works and the error dissapears.
    The errormessage is not very informative so we don't know what the original error is and we would like to avoid the reprocessing of the BDOCS.
    Do you know the rootcause and how to avoid these errors?
    best regards
    Jørgen Jensen

    Please check the following OSS note and implement the corrections that are suggested.
    SAP Note 629016 - Automatic restart of BUS_TRANS_MSG

  • Specify card type error in Bdocs

    Hi,
    We need to download customers from ECC to CRM , when executed , there is no error captured in SMQ2.
    But the BDocs are generated in  SMW01 and found  R1561 error with error u2018Specify a card typeu2019.
    Can anyone suggest what needs to be done to fix this problem?
    Thanks & Regards,
    Shwetha.

    Hello Swetha,
    Can you pls share what exactly you have done to resolve the issue?
    Thanks & Regards
    Sreedhar

  • Error- Update Bdoc status failed- R3AD_Accounting

    Hi ,
    We are trying to replicate service order from CRM to r/3, after saving a service order in SMW01 it shows error "No r/3 upload"
    In SMQ2 there is a queue R3AD_Accounting with status SYSFAIL stuck with the error message "Update BDoc status failed - BDoc not found"
    In R3AC1 the object Accounting does not have any entries for tables or initial flow context.
    Please let me know where we can maintain the entries for this Adapter object-Accounting.
    Regards
    Prathiba

    Try releasing the queue, might be a temporary problem.
    If not, check out the lockings in transactions sm13 (or sm12: I'm not sure).
    Michael.

  • Error in BDOC while uploading the pricing condition record to ECC from CRM

    Hi all,
    I have created a condition record for ECC pricing condition type (I have maintained all settings required for maintaining ECC condition type in CRM 7.0) in CRM 7.0. But theis condition record is not uploaded to ECC. I have checked BDOC, it is showing with error status for BDOC type "CND_M_SUP". The errors are as below.
    1. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
    Message no. CND_MAST064
    2. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
    Message no. CND_MAST064
    3. Service that caused the error: CND_MAST_INT_DEEP_MB_TO_SBDOC
    Message no. SMO8047Diagnosis
    A service caused/ reported an error.
    Can some one help me in fixing this issue  please.
    Thanks in advance,
    JM
    Edited by: JM on Sep 7, 2010 4:46 PM

    Hi,
    sBDOCs are not used in ECC to CRM or CRM to ECC data replication scenario. You can either ignore the error or disable mobile bridge.
    Regards
    Prasenjit

  • Error in Bdoc '....Editing was terminated'

    Hi All,
             I am replicating the BP from CRM to ECC using BDoc type 'Bupa_main' when the BP
    is saved under some role.
    When I save the BP , the Bdoc shows in error 'Partially send, receivers have errors'.
    After reprocessing the Bdoc in transaction SMW01, 1 entry is created in KNA1 and CRMKUNNR,
    but no BP is created. The error list  in transaction SMW01 is shown as
         Messages for business partner 0100000252:     XR     100
         ....Editing was terminated     FB     13
    I checked in ST22, there are no runtime errors.
    I tried CRMM_BUPA_MAP, there I get the message as
    '005     4AF79F489B97018: Object is in status Running'
    And there are no queues in SMQ1 or SMQ2.
    Any idea why it is happening or how to solve it?

    Hi Aditya,
    The problem is mainly because of some user exits in your system.
    So, if its possible, deactivate all the user exists from table : TBE24 and TPS34 in your system and try again.
    And also check in the ECC system - CRMRFCPAR table field SEND_XML is set to "X". If both CRM and ECC are unicode system, then the SEND_XML field in the CRMRFCPAR table in the R/3 system should be set to "X"..
    Also refer the following notes  :
    928974
    788871
    621470
    1049761
    Hope the above information would help you to solve the issue.
    Best Regards,
    Vignesh Ravikumar

  • Execution of programs after import (XPRA) error during transports

    Hi Experts
    I am applying the support stack level from 18 to 19. On applying the ABAP support pack i am getting the error.  (Ehp1- support pack)
       Execution of programs after import (XPRA)
       Transport request   : SAPKNA7013
       System              : RIS
       tp path             : tp
       Version and release: 372.04.40 701
       Post-import methods for change/transport request: SAPKNA7013
          on the application server: mel-srv-sap1
       Post-import method ENHS_AFTER_IMPORT started for ENHS L, date and time: 20090820182438
       Post-processing for ENHS /SAPCND/CONFIGURATION was already performed successfully earlier
       Post-processing for ENHS /SAPCND/GEN_AFTER_IMPORT was already performed successfully earlier
       Post-import method ENHS_AFTER_IMPORT completed for ENHS L, date and time: 20090820182438
       Post-import method ENHO_AFTER_IMPORT started for ENHO L, date and time: 20090820182438
       Post-processing for ENHO PRT_CONFIGURATION_EXIT was already performed successfully earlier
       Post-processing for ENHO REF_AFTER_IMPORT_EXT was already performed successfully earlier
       Post-processing for ENHO REF_CONFIGURATION_EXIT was already performed successfully earlier
       Post-processing for ENHO TTE_CONFIGURATION_EXIT was already performed successfully earlier
       Post-import method ENHO_AFTER_IMPORT completed for ENHO L, date and time: 20090820182438
       Post-import method /SAPCND/TRN_AFTER_IMPORT_OW started for CTAP L, date and time: 20090820182438
       Transport: Execution of method /SAPCND/TRN_AFTER_IMPORT_OW
       Mass activation off
       Transport: Execution of method /SAPCND/TRN_AFTER_IMPORT_O_OW
       End of processing of condition tables for order SAPKNA7013, time 18:24:38
    Program terminated (job: RDDEXECL, no.: 18243800)
       See job log
    Execution of programs after import (XPRA)
    End date and time : 20090820182453
    Ended with return code:  ===> 12 <===
    When i click on the job log i get the following details:
    Job log overview for job:    RDDEXECL / 18245300
    Date       Time     Message text
    20.08.2009 18:24:53 Job started
    20.08.2009 18:24:53 Step 001 started (program RDDEXECL, variant , user ID DDIC)
    20.08.2009 18:24:53 All DB buffers of application server mel-srv-sap1 were synchronized
    20.08.2009 18:24:53 ABAP/4 processor: SYNTAX_ERROR
    20.08.2009 18:24:53 Job cancelled
    Please help me to resolve the issue. Thanks in advance.
    Thanks & Regards

    Hello Folks,
                       Thank you all for your help. I apologize for the delay. Apparently SAP had a few SAP notes to suggest for my issue and once the notes were implemented, the problem got resolved. Here are the notes for your reference:
    1114409
    1113718
    1059837
    1055217
    Regards,
    Prashant

  • E08 error in BDoc

    Hi,
    We are  trying to maintain relationships for a BP through adapter object "BUPA_REL".
    When executed , there is error in SMQ2 with Error in Mapping (Details: transaction SMW01).
    Have checked in SMW01 and found E08 errors with error u2018Partner number 000000XXXXX is already assigned to a contact partner relationshipu2019.
    Can anyone suggest what needs to be done to fix this problem?
    Thanks & Regards,
    Shwetha.

    Hi,
    We are  trying to maintain relationships for a BP through adapter object "CUSTOMER_REL".
    When executed , there is error in SMQ2 with Error in Mapping (Details: transaction SMW01).
    Have checked in SMW01 and found E08 errors with error u2018Partner number 000000XXXXX is already assigned to a contact partner relationshipu2019.
    Can anyone suggest what needs to be done to fix this problem?
    Thanks & Regards,
    Shwetha.

  • Credit card error in bdoc for ecc to crm

    I am getting an error R11 144, No credit card details found, when an ECC customer master record has a credit card on it and it is flowing to CRM 7.  If you have encountered this error, how did you fix it?  I have searched with no success.

    I believe I may be getting the R11 144 error after I get a R1 561 because the card doesn't load into crm, so when doing a delete or change to the customer in ECC, the system looks for a card in CRM to delete and there isn't one.  So how to get rid of the R1 561 error then?  It is not an auth object issue as I have seen in some responses.  The card number and card type are not getting loaded into the bdco, but the expiration date is. I have logged a ticket with SAP but just keep going back and forth with them.  Hoping someone has been through this before.  Thanks.

  • Error in BDocs:SMOH_REPLICATION_WRAPPER_MSG

    Hi
    When I am downloading customer data to CRM, following errors are being displayed.
    although customer is replicated completely, but following error message is displayed in smw01
    1) Service that caused the error: SMOH_REPLICATION_WRAPPER_MSG
    2) Could not determine module name: BUPA_MAIN GENKEY: REP_GET_RECIPIENT
    Please help me in solving this, I am a bit stuck.
    Thanx in advance.
    Cheers
    Hitsm

    Hi Hitesh,
    Execute Transaction: GENSTATUS
    From the left panel double click on the record with red traffic light and then select all the records selected in right panel, click on Generate/Check.
    Once this is successfully done.
    Try to download the object.
    Best Regards,
    Pratik Patel
    <b>Reward with Points!</b>

Maybe you are looking for