Error in SLG1 transaction in CRM system

Hi exports,
We are getting error in application log in SLG1 T.code in CRM system while the system monitoring.
Error Conclusion  :Determinaiton of Component from SCR Failed"
Details are:
  USER   External ID                                    Object Text                                               Programme                                Mode
  DDIC    Collector for None-R/3-Statistic    SAP Global Workload Statistic Collector   SAPLSAPWLN3_COLLECTOR  Batch progra
When double click on error log we are getting message test :
>> Collector for DSR statistics started
TOTAL aggregation of daily data started
Determination of component from SCR failed
Any help is greatly appriciated..
Thank you
Regards,
Ram

Hello
This error message is caused by the SAP_COLLECTOR_FOR_NONE_R3_STAT background job. If you don't have SAPCCMSR agent installed to collect the DSR statistics, you can un-schedule (stop) the background job.
Regards
Joaquin

Similar Messages

  • How to extract Taxonomy data from MDMGX transaction of CRM system

    Hi all,
    I have a requirement on product master where in i have to upload data into MDM as taxonomy table from  MDMGX transaction in CRM system. Is it possible? If yes can anyone guide me the stepwise procedure as i observed it involves the Function Modules like MDM_COMM_CAT_ATTRIBUTES_EXTR.
    Thanks in advance
    Samatha

    Yes,
    You can very well do it. You need to define parameter " Hierarchy ID" in function module for exceptional cases in MDMGX.  This hierarchy ID you can get using Transaction COMM_HIERARCHY in CRM..
    This will solve you requirement....
    Thanks and Regards,
    Shiv

  • Business Content for Bill Up transaction in CRM system

    To all Experts,
    I'm currently working on a project that requires Bill Up transactional data ( Source Table: CMSD_BU ) to flow from CRM to BW system. I'm looking for Business Content that can fulfill this requirement. However, till to date, I couldn't find any information of such Business Content. I'm not sure if such BC exist. Can anyone help if you have experience implement this data flow?
    When searching for the DataSource / Extractor, I found BW Extract Structure CMST_BU_BW and CMST_BU_BW_C in the CRM system. But couldn't find any DataSource for both extract structure. Not sure if we need to install any support pack in order make the BC available in the system. Please help if you have any idea. 
    Thanks in advance.
    Regards,
    Hui Pin

    Hi Shalini,
    The document is replicated from ECC to CRM without any errors.
    For this document I just want to create follow up transaction in CRM.(I dont want to change the document in CRM)
    The follow up transaction is in display mode. this is my problem.
    Hi Rekha:
    I have done following setting in CRM to create follow up transaction in CRM for the document which is replicated from ECC to CRM.
    1)     Defined the Copying Control for Transaction type
    2)     Defined Copying Control for Item categories
    3)     Defined Item category determination when copying
    Thanks in advance,
    Regards,
    -Rahul.

  • Error in inbound q in CRM System

    Hello,
    The data sent from R/3 system to BBP CRM 4.0 has errors for the q R3AD_DNL_COND_A512. ie we are having errors for the conditions table and also for R3AI_CUSTOMER_MAIN q in inbound q of CRM system. R/3 is 4.6c.
    Error in R3AD_DNL_COND_A512 : Status of q is sytem fail and error is <b>"No entry in SMOFRSTAT with this REF_ID!"</b>
    Error in R3AI_CUSTOMER_MAIN :Status of q is sytem fail and error is "<b>Error in Mapping (Details: transaction SMW01)"</b>..
    please help.

    Hi,
    - a prerequisite for downloading conditions is a successful download of the condition customizing. You can check that in transaction CND_MAP_LOG_DISPLAY.
    - for analysing the R3AI_CUSTOMER_MAIN error the inbound queue is of no help. Please analyse the error information for the related bdoc in transaction SMW01.
    (by the was: the correct forum for your question would be "Customer Relationship Management (CRM) - General & Framework " )
    Kind regards,

  • Error in Sales Transaction in CRM 4.0 ?

    Hi All,
    We are working on CRM 4.0 i have created a sales transaction in WEB and  transaction will see in CRM and it is getting downloaded to R/3.
    But when I go back to CRM and check Sales Transaction it is showing me error as "An error has occured in the system XYZCLNT100 while copying the document".
    And i have been check in SMQ1&SMW01 ..in both T codes there is no error ..
    How can i figure out this problem ?
    can anyone help me in this regard?
    Thanks in advance.

    Please look into note 490932 for any issues of this nature
    This note gives an insight into possible error causes during the download or upload of sales transactions between CRM and R/3 and helps you correct these errors. This note is relevant for CRM Release3.0.
    It is also relevant for releases higher than 3.0.
    Other terms
    Download, initial, delta, delta download, SALESDOCUMENT, BUS_TRANS_MSG, event 00501014 501014
    Reason and Prerequisites
    The error causes may be included an incorrect configuration or missing system settings. The note only focuses on the sales transaction-specific configuration of the data exchange, but not on the settings for CRM Middleware in general or for other CRM Server applications.
    Solution
    In CRM Release 3.0, the following sales document items are transferred to the R/3 System:
    Sales items
    Customer return items
    Substitute delivery item
    Credit memo request items
    Debit memo request items
    As a leading system for the order entry, CRM only transfers data to the R/3 System if it is relevant for the logistical subsequent processing (delivery, billing). For this reason, requests for quotations and quotations themselves are not transferred to the R/3 back-end system with the standard delivery. With SAP note 455678, you can use a modification solution to also transfer quotations entered in CRM to the R/3 back-end system.
               Restrictions of note 455678:
    If you are using this solution, you cannot create any sales orders with reference to customer quotations in CRM.
    Mixed document processing (partially customer quotation items and partially sales order items) is not supported in the R/3 System and is therefore not possible during the quotation upload. The solution specified here only performs the upload for documents that consist of quotation items only.
    The quotation items must be defined in the Customizing for copying. This solution does not cover scenarios where the order is generated from the quotation as a result of a status change. Therefore, quotations entered in SAP Internet Sales (in particular) cannot be transferred to the R/3 System.
    Only completion rule 'A' ('Completed with one-time reference') is supported in the R/3 System.
    Sales transaction-specific settings for the data exchange
    1. Basic administrative settings for the replication of sales transactions
    a) The BDoc relevant for the distribution of all transaction types is called BUS_TRANSACTION_MESSAGE. In transaction SMOEAC, the relevant R/3 site must be subscribed to the corresponding publication 'All Business Transactions (MESG)' so that sales documents can be distributed to the R/3 back-end system. (To create a subscription, select the 'Subscription' object type in the 'Object type' selection list in transaction SMOEAC and then select the 'Object -> Create' function from the application menu or the corresponding symbol from the application function bar. The Subscription Wizard, which supports you during the creation of a new subscription, is started as a result.)
    b) Check to see whether the current CRM release has been maintained in the R/3 back-end system in the CRMPAROLTP table. This has to be taken into account in particular after an upgrade. You can maintain the CRMPAROLTP table in transaction SM30 in the R/3 back-end system:
                           Parameter name "CRM_RELEASE"
                           Param. value "30A"
    c) Event 00501014 must be activated in the R/3 back-end system so that the delta download of sales transactions from the R/3 back-end system to CRM works. The event must also be active for the upload of sales transactions from CRM to R/3.
    d) The event is activated automatically after a successful initial download. Call transaction R3AC4 ('Object Class Activation') in CRM and check whether the following entries exist:
                           Object class "BUSPROCESSND"
                           RFC destination <R/3 destination>
                           Select your entry and then choose 'Events by Object Class' (branch to the TBE31 table in the R/3 back-end system). The following entries must exist:
                           Event "00501014"
                           Obj. class "BUSPROCESSND"
                           Function "CRS_SALES_COLLECT_DATA"
                           If you do not see these entries, your initial download was not completed successfully.
    e) In transaction BD97 of your CRM system, the R/3 back-end system must have been maintained as the standard BAPI destination. Check the V_TBDLS view to see whether your R/3 back-end system has been defined as a logical system. A termination message in the SAPLCRM_ DISTRIBUTED_LOCKING program when you call a transaction in CRM indicates the missing destination assignment.
    Refer to notes 597812 and 674487. According to note 597812, the cross-system lock is processed using the RFC destination of the CRM middleware (SMOF_ERPSH table). However, the aforementioned entry in transaction BD97 for the Standard BAPI destination is still used to branch via the document flow to the R/3 system.
    f) In Release 3.1I, you can only have one entry for the RFCDEST field (RFC destination) in the CRMRFCPAR R/3 table.
    2. Definition of sales transaction-related Middleware parameters
    a) If you do not want a BOM explosion to occur for document items in CRM during the transfer to the R/3 back-end system, make the following settings in transaction R3AC6:
                           Key "R3A_SALES"
                           name "NOSTRUCTURE"
                           value "X"
                           This would make sense, for example, if you have already carried out a BOM explosion on the mobile client and if you do not want a new BOM explosion in the R/3 back-end system.
                           Make sure that the assigned item numbers in the sales transaction/sales document are set differently for main items and subitems so that no item numbers are assigned twice after the transfer and the BOM explosion in the R/3 System. The item numbers of the main items must be set identically in CRM and R/3. For more information, see note 496906.
                           Example:
                           CRM sales transaction
                           Pos.Nr.   Item No. Product
                           100 MAT1
                           200 MAT2
                           R/3 order
                           Pos.Nr.   Item No. Material
                           100 MAT1
                           101 Subitem1
                           102 Subitem2
                           103 Subitem3
                           104       ...
                           200 MAT2
                           You can maintain the item number assignment for the transaction types (CRM) or for the sales document types (R/3) in the Customizing.
    b) If a document is created in CRM and transferred to the R/3 back-end system, the warning messages of the transferred R/3 back-end document can also be displayed in the CRM document. In this way, you can recognize, for example, in the CRM document whether the transferred R/3 back-end document is incomplete and has to be postprocessed so that it can be further processed logistically. For this purpose, make the following settings in transaction R3AC6:
                           Key "R3A_SALES"
                           name "COLLECT_WARNINGS"
                           value "X"
    c) When you transfer a CRM document to R/3, you have the following control options with regard to pricing:
                           Key "R3A_SALES"
                           name "PRICINGTYPE"
                           value
                                             'B' = new pricing
                                             or
                                             'C' = copy manual pricecomponents,
                                             redetermine others
                                             or
                                             'G' = Copy price components unchanged,
                                             redetermine taxes (this value is
                                             delivered as a default setting)
    3. Definition of the R/3 dummy division in CRM
                  Note that no division exists in CRM in transactions at header level. In the R/3 order, however, the header division is a mandatory field. Thus, the R/3 dummy division must be maintained in CRM Customizing so that it can be determined during the transfer of a document. Otherwise, the order cannot be transferred to the R/3 back-end system.
                  Customizing path: 'Customer Relationship Management -> Master Data -> Organizational Management -> Division Settings -> Define Use of Division and Dummy Division'.
                  The use of several dummy divisions can be programmed in the CRM_DATAEXCH_AFTER_BAPI_FILL BAdI in the CRM_R3_SALESDOCUMENT_UPLOAD function module.
    Hints for the initial download
    Filter settings
    In transaction R3AC1, you set the filters for the initial/delta download of business objects. In the SALESDOCUMENT business object, you can set the filters for the order download from R/3 to CRM. For successful execution of the initial download, you have to set at least the VBAK-ERDAT filter criterion (document entry date) for the SALESDOCUMENT business object. This filter setting is required for the successful completion of order downloads.
    After you have completed these filter settings, you have to transfer these settings to the R/3 System. Select 'Filter sync.(R/3)'.
    Choose your R/3 System as a source site and check whether you are using the VBAK-ERDAT filter criterion:
    Example:
    Table/Structure Field OP Low
    VBAK ERDAT Greater than <Date>, for example, 20020128
    The date must be entered in the same form as it is stored on the database (YYYYMMDD)!
    The following filter criteria are also available:
    VBAK-AUART Sales document type
    VBAK-SPART Division
    VBAK-VBTYP Sales document category
    VBAK-VKORG Sales organization
    VBAK-VTWEG Distribution channel
    We recommend that you also use sales document numbers (VBAK-VBELN) as a further filter criterion. With this criterion, you can carry out an initial download according to sales document number intervals. The advantage of this filter criterion is that if your initial download terminates due to an error, you can restart the download after correcting the error as of the sales document number for which the error occurred. In this way you avoid having to restart a download for sales documents that have already been replicated.
    Example:
    Table/Structure   Field          OP            Low           High
    VBAK             VBELN          zwisch.        0005000000    0005099999
    Enter the field contents in the same way as it is stored on the R/3 database (leading zeros).
    If you want to use this filter criterion, go to transaction SM30 and make the following entry in the SMOFFILFLD table:
    Object name Table/Structure name Field name
    SALESDOCUMENT VBAK VBELN
    Note 497327 deals with possible filter-specific problems during the delta download that can occur due to missing R/3 back-end entries.
    Block size
    In this context, the block size specifies how many documents are selected in a transaction and transferred to CRM as a BDoc. The block size is defined on the system. The default value may have to be set to a lower value if problems occur (for example, memory overflow during the selection in the R/3 System). If the initial download terminates, check the dump log in the R/3 System (transaction ST22). The TIME_OUT or STORAGE_FREE_FAILED runtime errors indicate that the block size is too large. In this case, reduce the block size and restart the download.  In addition, you can clarify with your Basis Administration whether the rdisp/max_wprun_time kernel parameter is large enough (this avoids a TIME_OUT error).
    Basically, you should only download a few documents during the first download to check whether the system settings are correct. In this way, you can identify possible Customizing errors and correct them before the large load.
    Queue processing during the initial download
    In the case of very large transfer data sets, it may make sense to process the initial download in parallel within one object (object-internal parallel initial download) to complete the initial data transfer faster. Note 350176 describes the corresponding procedure.
    Queue processing during the upload/delta download
    Queues in CRM are defined in the SMOFQFIND table (for example, from CRM to CDB or from CRM to R/3).
    For the BUS_TRANS_MSG BDoc type, the default setting of the queue processing is that all orders for a customer are processed in one queue.
    As an alternative, you can set the queue processing in such a way that each order is processed in a separate queue. As a result, an individual order can no longer block the processing of other orders if an upload problem has occurred.
    If you prefer this queue processing, go to transaction SM30 and make the following change in the SMOFQFIND table:
    Select the BUS_TRANS_MSG BDoc type and change the segment field name from QUEUE_NAME to OBJECT_ID.
    In the same way, you can also set the queues for the delta download in the R/3 back-end system in such a way that each order is processed in a separate queue. If you prefer this queue processing, go to transaction SE16 in the R/3 back-end system and make the following change in the CRMQNAMES table:
    Select the entry for the SALESDOCUMENT object and change the BAPIFLD field from SOLD_TO to DOC_NUMBER (with BAPIOFFSET=3 and BAPIFLDLEN=10). Leave the second entry for the SALESDOCUMENT object (with QOBJPART=SAL_ERR) unchanged.
    In transaction SMQR, check to see whether the queues have been registered or check transaction SMQS to see whether the destinations have been registered because otherwise, the queues are not processed automatically, and this can lead to queue overloads.
    Check the queues regularly.
    Composite SAP Note 504090 covers all notes that solve known problems in the transfer as of Support Package 06 (SP06).
    Document cannot be maintained in online mode
    If you cannot maintain a document, this can have various reasons. Basically, a sales document entered in CRM is locked until the R/3 System has confirmed the update of the order successfully.
    If message CRM_ORDER019 "Document will be distributed - changes are not possible" occurs in CRM, check the queues (transaction SMQ1 and SMQ2). To analyze the data exchange from CRM to R/3, refer to note 431345.
    If message CRM_ORDER013 "Transaction &1 is being processed by user &2" occurs in CRM or if message V1042 "Sales document &1 is currently being processed (by user &2)" occurs in R/3, the document is processed in the other system respectively. To avoid inconsistencies, a cross-system lock is set during the processing of a replicated transaction so that the document cannot be processed simultaneously in two systems.
    Other notes
    Only error-free sales documents are distributed to the R/3 System. If, in R/3, you change a sales document that was originally created in CRM, these changes are not transferred to CRM. That is, you should always make the changes in the original CRM document to ensure the consistency of the document data in both systems. Sales documents entered in the R/3 System are transferred to CRM, but they are locked for processing there. Changes to a document created in R/3 are also transferred to CRM.
    In your settings for the data exchange, also make sure that the document number ranges correspond in both systems. For the successful sales document exchange between the systems, the transaction types and item categories have to be created in exactly the same way in both systems. If these objects do not exist in one system, you have to create them manually.
    In transaction CRMM_BUPA_MAP, you can determine into which R/3 customer number the CRM business partner is converted and vice versa. If you do not receive a conversion for the specified business partner here, this indicates that a transfer problem has not occurred in the sales document but during the business partner download.
    Header Data
    Release Status: Released for Customer
    Released on: 02.05.2006  15:04:13
    Priority: Recommendations/additional info
    Category: Consulting
    Primary Component: CRM-BTX-BF-IF R/3 Interface for Business Transactions

  • Error while fetching data from CRM system to BW

    I am extracting data (BP ID) from CRM system. I have upgraded the BI 7.0 system from patch 12 to patch 14. After upgrading when i execute the infopackage to fetch the data from the CRM system. The request is coming in yellow and is not fetching the data.  Can you suggest what could be the solution.. or where can i find some help..
    Thanks..
    Bhavya

    Hi,
    1 . Do the Data replication in source system
    2. Check the source system connections.
    3. Check the Infopackage status and also che the exact error from tcode RSMO.
    Regards,
    Srini Nookala

  • Create Transaction (of CRM system) as Receiver thru "RSBBS" TCode for query

    Hello,
    My requirement is to Jump to a SAP-CRM transaction from a BEx query.
    Thru TCode : RSBBS, I selected "TRANSACTION" as receiver of a query, then I selected "CROCLNT002" as the source, then in the Report field I gave the SAP-CRM Transaction "crmd_order" and selected OK.
    Then, I tried to execute the query thru Web, On the Context Menu's 'Go To' property, I clicked on the Transaction, It gives me the following errors:
    "No Web server maintained for the presentation of log. system CROCLNT002"
    "Jump target cannot be executed"
    " An error occurred with the report to report interface during the jump"
    Do I need to execute some other steps also in order for this to function smoothly. Thanks to help me in understanding the loop hole.
    Best Regards,
    Sumita

    Sumita,
    This is 'coz your CRM client CR0CLNT002 might be a WINGUI and not a WEBGUI interface. CRM does provide a WEBGUI for its CRM 4.0 or later if you need to be jump to a transaction from Web report.
    You can jump to a WINGUI from a BEx report as an alternative. So you will have to make a choice.
    Doniv

  • Error in Transaction launcher - CRM 5.0 / ECC 6.0

    Hello all,
    I am trying to pull one ECC 6.0 transaction into CRM 5.0 IC webclient through launch transaction.
    When I click the link in the NavBar, I get the logon box for ECC system but after I enter the logon details below error message is getting displayed.
    The transaction call failed
    Reason:: Function module EWB_PROC_CREATE does not exist
    But this FM exists in both CRM and ECC systems.
    Any ideas about this error message?
    Best Regards,
    Nag

    Hi Sudeep,
    Thanks for the reply.
    I am not sure about the EEWB extensions.
    Initially I created a launch transaction using BOR method the path of the ECC logical system is given as below.
    http://ssever:port/sap/bc/gui/sap/its/CRM_CIC_RABOX
    But now I've changed the path as: http://ssever:port/sap/bc/gui/sap/its/CCMP_RABOX
    and it is working now. I am able to pull the transaction from ECC although some other data flow issues are there.
    So looks like there is some issue with the serivce CRM_CIC_RABOX in our system.
    Thanks to all,
    Nag

  • Main optimizer error - There is already a transaction for the system

    Hi Guru's,
       I am trying to download support packs from maintenance optimizer in solution manager system. When i select the logical system it gives the error
    'There is already a transaction for the system of this product version'
    After this error, it does not proceed further.
    There is many maintanence transactions in Maintanence optimizer. Now how to remove all these.
    Any ideas or solutions most welcome.
    Moses

    As Christian has already written, the only problem is that there is already an open Maintenance Transaction for that specific system. Maintenance Optimizer checks that you do not open two different Maintenance Transactions for a system at the same time.
    You only have to withdraw the old Maintenance Transaction to be able to proceed with the new one. Open the old Maintenance Transaction and click "Withdraw" on the bottom of the page. If it is grayed out, you need to go one step backwards, there you can withdraw it.
    Best regards,
    Joachim

  • Error while downloading Contacts from R/3 to CRM system

    Hi All,
    I am trying to download Contacts from R/3 to CRM system.
    Through Initial Download. For this i have set filters through Tcode: R3AC1
    as on KNVP and KNVV for the field VKORG.
    As we have our requirement to download contacts based on or differentiating
    on 'Sales Org".
    We have downloaded our Accounts properly without any errors.
    But for Contacts we are facing issues such as one or more extra
    relationships are getting created between Contacts and Accounts other than
    its original Contacts.
    Means already existing contacts are creating more relationships after
    download.
    But a unique feature is visible for all, All those with false
    contact-account relationships.
    Contact has field value for 'Address type' missing while the same address
    type field is properly added for correct relationships. ( please find attached the screenshot of the same)
    Any pointers in which direction we should proceed for the solution would be
    appreciated.
    Thanks in advance.
    Cheers,
    Sharad

    Dear Vimal,
    Sorry not sure then...
    Sometimes the RFC connection is refused and use to give that particular error messgae due to:
    The old RFC library having version 6.20 automatically converted the
    password into uppercase with a size limit of 8 characters before sending it to the SAP system.
    The RFC library version 6.40 does not perform this conversion any more, because mixed case passwords upto 40 characters are now supported by SAP Basis version 7.00 (eg. NW2004s) and above. 
    So need to use upper case passwords when connecting to an SAP system having version less than 7.00. 
    But this is not valid in this scenario.
    Thanks,
    Atin

  • Error during execution phase of sps10 update in CRM system

    Hi all,
    I am applying SPS10 on my CRM system and getting the following error during the execution phase. The system is running on Windows/MaxDB.
    ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2014/03/10 04:26:51")
    2 ETP301 ----------------------------------------------------------------------
    2 ETP399   processing modeflag 'F'
    2 ETP301 ----------------------------------------------------------------------
    2 ETP330XActivation of Shadownametabs with DDL
    2 ETP301 ----------------------------------------------------------------------
    3 ETP379X04:26:51: activating Nametab "COMC_ATTRIBUTE":
    2 ETP399   >> Name of inactive nametab to read  : DDXTT
    2 ETP399   >> Format of inactive nametab to read: 5.0
    3 ETP355Xstatements:
    3 ETP399 CREATE UNIQUE INDEX "COMC_ATTRIBUTE~UNI" on "COMC_ATTRIBUTE"
    3 ETP399 ("ATTR_ID")
    3 ETP399 
    2WETP000 04:26:51: Retcode 1: error in DDL statement for "COMC_ATTRIBUTE                " - repeat
    2EETP345 04:27:04: Retcode 1: SQL-error "-1452-POS(1) Duplicate secondary key" in DDL statement for
    2EETP345  "COMC_ATTRIBUTE                "
    2 ETP399  --------------- DB-ROLLBACK() ---------------
    2EETP334 04:27:04: error in DDL, nametab for "COMC_ATTRIBUTE" not activated
    2 ETP301 ----------------------------------------------------------------------
    I searched in the service market place for notes which could help me resolve the issue, but could not find any. Please do let me know as to how this issue can be resolve.
    Regards,
    Balaji.P

    Hi Balaji,
    In SAP Note 601757 - Error upgrading from Release 2.0C, 3.0, 3.1, 3.5 to CRM 4.0  
    , I have found the below lines.
    "If you do not execute the report before the upgrade, 'DUPLICATE KEY' errors occur during the upgrade of the COMC_ATTRIBUTE table. Up to now, this was observed in the SHADOW_IMPORT_INC phase. In this case, you must delete the UNI secondary index from the COMC_ATTRIBUTE table manually. You can then continue the upgrade by repeating the phase."
    Regards,
    Rafikul

  • What is the transaction to see the Authorization objects in the CRM system?

    Hello Guys,
    Please let me know transaction code to see the Authorization objects in the CRM System?
    Thanks in advance.
    Regards,
    Vinay

    Hi Nagur,
    With T.Code SU21 you can see the Authorization objects in the CRM System. If you want to see Authorizaion object for a particular Transaction Code then the T.Code is SU24
    Thanks & Regards
    Shiva Vekat

  • Problem in transaction SMQR in CRM system

    I was told there is a problem in an CRM system and that I will see it immediatelly in transaction SMQR.
    As an non CRM specialist I do not know to what pay attention and how to solve the problem. Is there any documentatition
    When entering the transaction SMQR I get :
                       Scheduler Information
    Scheduler Status                   :     Inactv.
    Last Update (Every 2 Minutes)  :         07.05.2009 18:16:21
    Name of AS Group (DEFAULT = All):        DEFAULT
    Number of Entries Displayed              2
    Host ID                            :     sapqrm_QR1_91
    Number of Active Connections             0
    Cl. Queue name               Type Mode Max. Runtime Attempts Pause Destination with LOGON Data
    005 CSA*                      R    D        60         30     300
    005 R3A*                      R    D        60         30     300

    why did you go to SMQR
    first let us know what the problem in CRM is?
    also the information that you have given fom SMQR doesnt point to any problem
    go to SMQ1 and SMQ2 and check if there are any pending queues
    Also let us know what the problem in CRM is?
    Rohit

  • Errors occurred during the extraction datasource of CRM System in Check extractor

    Dear All,
    Please find the below error's while I am extracting data from the data source in CRM.
    RM_QUOTA_ORDER_I: Table SMOXHEAD contains no BDOC name .
    Errors occurred during the extraction in Check extractor.
    Please let me know solution to resolve the issue.
    Thanks
    Regards,
    Sai

    Hi,
    Where your getting this error?
    during info pack load or checking at crm system RSA3?
    if your running your info pack then please run data source at RSA3.
    Seems like your source table may not have any bdocs.
    Where your runing this loads? prod or dev?
    Thanks

  • There is already a transaction for the systems of this product version(MOPZ)

    Hello All,
    I am trying to configure maintenance optimizer in Solution Manager 7.0
    on Windows 2003 server and SQL 2005 server.
    I am configuring this for SAP CRM 2007 server.
    Created the server, database and system in SMSY
    Created Logical Component in TA code SMSY
    SM59 connection for SAP-OSS is OK.
    S-User is assigned to a User.
    Created a solution using TA code solution_manager.
    Defined the product version for the solution created in the TA code
    solution_manager.
    When creating a Maintenance Optimizer transaction, I select the
    product version and its logical component in the Plan Maintenance
    (Phase) and click on Continue to go to Select Files Phase, I get below
    warning:
    Information Procedure 8000000130 Saved
    Warning: Status was reset by system
    Warning: There is already a transaction for the systems of this
    product version
    I cannot get pass this phase.
    I have deleted and recreated the solution, carried out the same
    activity again but its giving the same Warning
    Warning: Status was reset by system
    Warning: There is already a transaction for the systems of this
    product version
    Any help will be appreciated???
    Regards,
    Satish.

    Hello Ragu,
    Thanks for your response.
    As of now, we do not have ChaRM in place. Secondly, we use a single customer number.
    I would like to let you know that in our landscape we have two CRM server, one ECC sever, one SOLMAN7.0 server.
    I tried to configure MOPZ for CRM, ECC, SOLMAN server to download the respective STACKS.
    I was successful in configuring CRM and SOLMAN.
    But  when I tried to configure in ECC, it failed due to RFC erros.
    So I deleted the transaction for the ECC system and deleted the system itself in Solution Manager.
    Reconfigured the Systems in "SMSY", RFC connections are correctly defined to configure MOPZ between SOLMAN7.0 and ECC6.0.
    When I start configuring the MOPZ, I cannot get pass the first phase and this is when I get an error: There is already a transaction for the systems of this product version.
    Please let me know if you need further information.
    Regards,
    Satish.

Maybe you are looking for

  • User Exit / BAdI in ME29N on PO Rejection

    Howzit, Guru's! SAP has done some sweet things with the PO approval in 4.7. But, can anyone tell me whether there are any User Exits or BAdI's in ME29N that I could use to react to the user pressing the <b>Reject</b> button (SY-UCOMM = 'MEREJECT')? I

  • Analyzer Security for SAP BPC 7.5 SP6

    Hi , We have recently installed Analyzer add-in on our excel for Adhoc reporting on SAP BPC 7.5 SP6 But analyzer is not considering the data security restricted for specific region. For eg: If a planner is assinged to EUROPE planning role and when he

  • How to include Serial Numbers in a marketing documents

    Hi, we would like to show the serial number attached to the right item in the Invoice and Delivery documents.  But the serial number columns are always empty in the markleting documents.  My boss don't want to see the serial numbers on a separate rep

  • Need help for showing top results

    Hello everybody, I am a little upset and do not know what to do furthermore. I have grouped data in my crystal report. This data is sorted by turnover values, as it shall. My Problem is that I only want to display the first ten lines within that grou

  • Question mark not working, as well as others- can I work around by programming another key for this symbol

    The question mark-slash key, the semi-colon key, the eject key, don't work at all as a result of getting wet. Can I do a temporary work-around by assigning another key (like the f11 or f12) to use until I get a "proper" fix>(that's a q-mark...)