RRI to Opportunity transaction on CRM UI

Hi All,
We are using BI 7.0 and CRM 7.0. I have a requirement of jumping from opportunity BI Report to its opportunity screen on CRM UI. I have maintained sender-receiver assignment but it is not working.
Has anyone worked on RRI to CRM transaction (opportunity/Lead). Please suggest with the parameters required for the jump.
Thanks
Santosh

Hello,
Have you been able to resolve this issue?
regards,
Atul Kulkarni

Similar Messages

  • Business Activity details in Opportunity transaction in CRM table.

    Hi
    In which table in CRM can i find data entered in business activity details in opportunity transaction.
    Please advice .
    Thanks,
    Vaishnavi

    look at tables CRMD_OPPORT_H and CRMD_ACTIVITY_H.
    regards.

  • How to get the Relationships data from Opportunity Transaction in CRM

    Hi Friends,
    Could you please let me know the table / class to fetch the relationships data associated with a single(main) opportunity.
    There may be several object types like (activites, sub-opp's..etc) linked to a single  main(source) opportunity.
    I wanted the these fields information from Relationships tab From Opp transaction.
    Source Item No.
    Object Type
    Target Trans/Object
    Description
    Type of Linkage
    Could you please let me know.
    Regards
    Vijay

    Hi Vijay,
    Can you try function module CRM_DOC_FLOW_READ_DB?
    By giving opportunity GUID it will return associated information.
    Kind regards,
    Garcia

  • IPC Pricing in CRM Opportunity transaction

    I am working on a new CRM implementation and we have to price
    products in Opportunty transaction in CRM.
    We have loaded all the pricing procedures and conditions from R/3
    into CRM using middleware. IPC is installed and it is up and
    running. Our basis person
    confirmed that the connection between CRM and IPC server is verified
    using SM59 and it is connected.
    The WEB interface has lots of *.JSP links. How  to verify
    whether the WEb interface provided by our basis is fine.
    I have configured an opportunity transaction in CRM. All the products and
    their pricing procedures are loaded from R/3 into CRM. But still the product
    price is not being calculated in opportunity transaction. Item category is
    determined correctly. But the net value is ZERO and no error message. Before
    we connect we were getting an error message pointing to IPC connectivity
    issue. Now that is resolved but still the price is not being calculated.
    Any additional information on configuring IPC to look into CRM database for
    pricing procedures and conditions records when serving the request from
    opportunity transaction would be of great help.

    We are in CRM 4.0. I know for sure that pricing takes place for opportunity and I have tested the same in IDES and this worked well in my previous project.
    Based on the products entered IPC will provide the price from product master and conditions/pricing procedures. Expected Value will be nothing but the pricing provided by IPC. But the user will have option to manyally enter this or override the system entered value.

  • What is Business Transaction in CRM

    Hi,
    What is Business Transaction in CRM? What is deifference between partner and partner_guid? What is significance? and also product, prodcut_guid?
    Thanks,
    Shashikanth

    Hi Shashikanth,
    Most of the transaction that you carry out in CRM are Business Transaction. E.G. Service Contract, Activities, Lead, Task etc.
    Business Transactions are further divided into Subobject Category, these Subobject Categories are again subdivided into Transaction Type.
    <b>Categorization of CRM Business Transaction based on Subobject Category</b>
    Business Transaction Name      SUBOBJECT CATEGORY
    Activity                     BUS2000126
    Service Contract             BUS2000112
    Lead                             BUS2000108
    Opportunity                     BUS2000111
    Task                         BUS2000125
    Utility contract item             BUS2000147
    Note:
    1. For Example if you want to retrieve all the activities in CRM, pass the OBJECT_TYPE as ‘BUS2000126‘ in CRMD_ORDER_INDEX table.
    2. The Subobject Category can be customized for a business transaction from the transaction SPRO.
    Partner : Partner is a 10 char number used to identify Business Partner in the system.
    PArtner GUID : It is global unique identifier to identify the partner globally.
    As such there is no difference in partner and partner guid, both refer to the same entity in CRM and are unique across the system. Refer the table BUT000.
    Same applies to product and product guid. Refer the table CRMM_PRODUCT.
    <b>Reward points if it helps and close the thread.</b>

  • Follow up transaction in CRM

    Hi All,
    I want to create an Order in CRM with reference to the Standard Order (which is created in ECC and replicated from ECC to CRM).
    When I open the Transaction (which is created in ECC and replicated from ECC to CRM).
    in CRM and clikc on follow up I am not able to create the follow up transaction.
    The follow up transaction is in display mode.
    Can anybody give me inputs in this regard? where is wrong
    Will award the points for the helpful answer.
    Regards,
    -Rahul.

    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.

  • Transaction in CRM

    Hello All,
    Just heard this and wanted to clarify with you all.
    A transaction will have header and Item and at item level Line item.
    On the CRM side we have a Header and Item for a transaction. Is it not mandatory
    for a CRM transaction to have an Item and line item.Is Item level just optional.
    Or what I am saying doesn't make sense at all?
    If for a transaction just Header is needed and nothing why would we need some thing like that?
    All answers nomatter how detail will be rewarded more that helpful.
    cheers,
    Muralidhar Prasad.C

    hi Muralidhar,
    based on my knowledge not all of transaction in CRM need an item.
    for an example item is not needed in transaction Activity and Task.
    i think for SAP has build several ... what a term ... perhaps i call object model in technical that some of them need items and others no need it.
    that's the reason if we start to configure a transaction it is mandatory to set a leading transaction category.
    the transaction category will determine will an item needed or not.
    hopes it helps
    cheers

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

  • Display issues in WebIC when i launch a Transaction from CRM

    Hello All,
    In Web IC 5.0 i am calling  BP transaction from CRM.
    The page displayed to me is SAP easy Access Menu instead of BP .
    I was told that our installation is using new SAP gui service( i am not very sure as i am a functional guy).
    any suggestions please?
    will for sure reward for the solution or even a tip which will lead to resolving the whole issue.
    Thanks
    Amar Reddy

    Hello Amar,
    I've it configured in CRM5.0 like this (see if it can help you - it's working fine for me):
    - My ITS link (at CRMS_IC_CROSS_SYS t-code) is defined like this (see note 917302):
    http://<host>:<port>/sap/bc/gui/sap/its/webgui/!?transaction=IC_LTX&okcode=ICEXECUTE
    - The most important steps of my entty at transaction launcher, is like this:
      Wizard step: Further Technical Details
      Tr. Launcher Type: M BOR Transaction
      Logical System: for CRM Server OWNLOGSYS
      BOR Object Type: BUS1006005 (CRM Business Partner)
      Method Name: Display
      Wizard step: Transaction Parameters
      Parameter: Object key
      Value: //currentCustomer/BP_NUMBER
    Best of lucks,
    Regards,
    Bruno

  • Middleware-Replicating service transaction from CRM to R/3

    Hi Experts
    We are using the transaction SRVO( Service Transaction) in CRM and it has to be replicated to the R/3.
    Can anybody tell me
    1.what is the load object for replicating this transaction ?
    2.Do i need to make any settings in R/3 for the replication ?
    3.Do i need to create one new transaction in R/3. If so where i have to create the transaction ?
    4. What would be the document type category of the replicated transaction ?
    Thanks in advance
    Nadh.
    Message was edited by:
            Nadh R

    Hi Nadh,
    Service transactions are replicated to R/3 as sales order, with sales items only.i.e. item category SRVS.
    You need to maintain the similar settings as you do while replicating a sales order from CRM to R/3.
    1. Create a order type in R/3 with the same name SRVO (Tcode: VOV8)
    2. Create the item categories with the same name as being determined in the service order (Tcode: VOV7) e.g. SRVS
    3. Mainatin item category determination, the way it is maintained in CRM (Tcode: VOV4)
    Other than this, assign an external number range to your order type SRVO which is same as the internal number range of CRM. Ensure that the customer master and product also exist in R/3.
    Before replicating a service order from CRM to R/3, Create a dummy sales order in R/3 (VA01) with order type SRVO (only for checking purpose)and your sales area,put the customer master and material and check if the transaction is complete. If not you will have to first remove the incomplete stuff, than only an order will get replicated error free.
    If you get incompletion items like Plant, shipping point, contact a SD consultant or post another thread.
    Regards,
    Shalini Chauhan

  • Adding field with drop down list to Opportunity transaction

    Hi All,
    I want to add a field from one of the Z table to the opportunity transaction Using EEWB. I have added the field but my problem is that the field should be drop down list with values coming from the Z table.
    Please help me if in case if you have idea or any relevant note or document.
    Thanks in Advance
    Gaurav

    Hi Gaurav,
      Go to your development package with your EEWB extension, look at function group like ZCRM_BTX_EEW_UI* and here you have you screen, your pbo, your pai.
      Modify with the same logic of program demo in your field.
    Regards.
    Manuel

  • Questions about Territory determination in Business transactions in CRM 7.0

    Hi All,
    We are in the process of configuring territory management in our system. I have a couple of questions regarding Territory determination in Business transactions in CRM 7.0.
    1) Territories in business transactinos are determined based on partner function categories: employee and person responsible. If the employee is assigned to multiple territories, which territory is determined for the transaction.
    a) Is it the territory for which he is assigned the 'Default territory' flag'?
    b) What if the employee does not have any territories with the 'Default territory' set?
    2) We have had SAP CRM since the last 6-7 years and recently upgraded to CRM 7.0. When I use the transaction searches in the Web UI using the search parameters 'Territory ID' and 'Territory description' we can't see any old transactions in the search results. We can only see the test transactions that were created after we ran the master data reln. update program CRM_TERRMAN_PROC_REL. Is there another program which updates transactional data relationships similar to the master data one?
    Appreciate your inputs.
    Regards,
    Ramesh Nallabelli

    Hi All,
    We are in the process of configuring territory management in our system. I have a couple of questions regarding Territory determination in Business transactions in CRM 7.0.
    1) Territories in business transactinos are determined based on partner function categories: employee and person responsible. If the employee is assigned to multiple territories, which territory is determined for the transaction.
    a) Is it the territory for which he is assigned the 'Default territory' flag'?
    b) What if the employee does not have any territories with the 'Default territory' set?
    2) We have had SAP CRM since the last 6-7 years and recently upgraded to CRM 7.0. When I use the transaction searches in the Web UI using the search parameters 'Territory ID' and 'Territory description' we can't see any old transactions in the search results. We can only see the test transactions that were created after we ran the master data reln. update program CRM_TERRMAN_PROC_REL. Is there another program which updates transactional data relationships similar to the master data one?
    Appreciate your inputs.
    Regards,
    Ramesh Nallabelli

  • 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

  • Opportunity transaction types in the Dropdonw

    Hi,
    I am not able to see the opportunity transaction types in the Mobile application drop down.
    Can you please suggest me which customization adapter object should i download to CDB for getting this drop donw.
    Regards,
    Karunakar

    Hi Karunakar,
    The Customizing Object for the Opportunities are :
    CRM_DNL_OPPORTH - Header details
    CRM_DNL_OPPTYPE - Sub Types
    CRM_DNL_OPPIPOR - Classes
    CRM_DNL_OBJREF - Links
    For the Transaction Type  : the following customizing is used  : CRM_DNL_OPPORTH - Header details
    Best Regards,
    Vignesh Ravikumar

Maybe you are looking for