Regarding XIF Interface and Sale Transaction in CRM

Hi,
I have done the configuration in CRM system using XIF interface to communicate with other system.
We are in the process of implementing CRM, Product and Partner data has to upload in CRM. We are not using R3 for anything.
When i create a sales transaction using transaction code CRMD_ORDER,System allow me to save/create a business transaction even though i can see the error attached to it and at the same time I can see the BDOC number in SMW01.
But i dont see any relevant OUTBOUND IDOC against the BDOC, evenif i have configured it for external system and I was expecting Outbound IDOC with error status, please correct me if i am wrong.
I am using WE02 and WE05 to see my outbound idoc and i have not found anything here.
Am i missing some step in configuration which is required for converting BDOC to IDOC, Please suggest me.
Steps which i followed to configure the system are
1. Create a suitable RFC destination in the SAP IMG Define Target Systems for RFC Calls .
2. Create a logical system.
3. Create a receiver port (transactional RFC) in SAP IMG Define Port, indicating the RFC destination you created earlier.
4. Create a partner profile, for example, partner type LS with the partner number CRM_XML_BC, in the SAP IMG Maintain Partner Profile Manually.
5. Enter all outbound parameters for the logical system CRM_XML_BC in Create Outbound Parameters in the Outbound Parameters window .
6. Create a site (transaction SMOEAC). To do this, select Object Type Sites and Create Object. Assign your site a suitable name and select Site Type External Interface for IDocs. Assign the partner profile created previously as a Site Attribute.
7. Use object type Subscriptions to maintain a subscription for publication of the object with the predefined site.
8. Create an entry for the new site using XIF customizing transaction CRMXIF_C1 via F4 help (BDoc Type = <objname>, IF Type = 'CRMXIF_*_SAVE_M', Set relevant flag for complete Data and Return). The flag Flag for complete data is only relevant for the objects "order", "business partner", and "business partner relationship". It flags whether only delta changes or the object instance should be transferred completely. The object "business document" is always sent completely, regardless of flag status.
Thanks & Regards,
Manoj Tiwari

Hi Joao,
Thanks alot for your quick reply.
Yes i have selected "post it immediately"  instead of "collect Idoc". should i select "post it immediately"??
About the Outbound parameter i specified everything like message type (crmxif_order_save_m), port , RFC destination of type R3 since we have SRM system, basic type (crmxif_order_save_m01), package and post the idoc immediately.
Here in our distributed environment we are sending data from CRM to SRM, means our target system is SRM.
I have created the Site of site type "External interface for idocs" and give the partner Number of SRM system and created subscription too as part of XIF setup.
Please reply me if i am going wrong in my approach.
Thanks & Regards,
Manoj Tiwari

Similar Messages

  • 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

  • Replication of BP and Sales order from CRM to R/3

    Hello everyone,
    I have a peculiar condition in my hands.The requirement is to replicate 10 business partners from crm to R/3 ,then the next 4 Business partners need not be replicated and then the next three replicated..How do we do this kind of replication....
    One thing more regarding the replication of sales order.When we save a sales order in CRM,is it automatically replicated to R/3 or do we need to release it manually??
    If yes,then if we do not want to replicate the sales order from crm to R/3,then what will we do?
    Consider that all the middleware settings are configured and working fine..
    Puneet

    Hi Bokhal,
    Please consider my answer from your recent thread dealing with apparently the same issue :
    Hi Bhokal,
    For filters in uploads please consider below:
    For Filtering the BP-upload, use the Administration Console
    (tx. SMOEAC) in the corresponding subscription of the "All Business
    Partners (MESG)" publication assigned to the R/3 site.
    Some publications (and the replication objects they are based on) are
    delivered as type "Simple bulk" which does not give you the opportunity
    to assign criteria values for filtering.
    You might have to re-create the publication. To do that:
    1) First delete the subscriptions "All Business Partners (MESG)" and its
    publications & the replication object.
    2) Recreate the replication object as type "Simple intelligent".
    3) Afterwards you can create a new publication via wizard of type
    "Simple intelligent (msg)" assigned to the BDOC-Type BUPA_MAIN. Then,
    you will be able to select some "filter criteria".
    The reason for deleting the "old" publication is, that you
    are not allowed to assign a BDOC-Type to more than one publication.
    4) But please keep in mind that there is no realignment supported. So
    you should only use fields for filtering, which cannot be changed
    afterwards.
    This is the "simple" solution for filtering on fields. This
    will not provide complex filter criteria.
    If you need this, you shall create a filter function in R/3- and/or
    CRM-Inbound and -outbound.
    If you want to keep the control about the upload trigger, you can add an
    additional module in transaction CRMC_BUT_CALL_FU, position > 200000.
    BUPA_MWX_BDOC_BPS_FILL_CENTRAL. Within this new module, you can delete
    all partners within the complex structure that you don't want to upload.
    Hoping that above will be helpful.
    Best regards
    Christophe Sturzel

  • Replication of Sales Office and SAles group into CRM from ECC6

    Hi All,
    recently I added the sales group and sales office into and existing sales are in ECC6.
    1. how can I replicate that sales group and sales office replicate into CRM and Assign to the same sales area
    2, how can replicate a new sales area into CRM?
    3. do I need to do something in Org structure..?
    thanks,
    Ken

    Hello Ken,
    You can download new sales office & sales group using Transaction code CRMC_R3_ORG_GENERATE.
    After executing this transaction you can see new sales office & sales group structure.
    You have to select this new sales office & group rows & generate structure. After that you have to save. While saving you can give the earlier CRM Sales Organization unit.
    You can see new sales office & sles group under earlier sales organization in PPOMA_CRM.
    Best Regards,
    Rajendra Sonawane

  • Process types and Sales Transactions not Sync with SM2.5

    Hi Experts,
    1) We have custom process types for leads, opt and quotations etc.. but the TYPES option is not activated or greyed out when creating any sales transactions from app SM 2.5.
    Please help on this.
    2) With our accounts as a relationships, leads and opportunity are syncing well but not quotations and activities. Is there any settings for that which needs to be activated.
    Thanks for your help.
    Thanks
    VS

    Check out these instructions:  http://support.apple.com/kb/ts5223

  • Replication of Business partner and the Sales document from CRM to R/3

    HI All ,
        I am completely new to this CRM technical , I need some technical document on how can I replicate BP and sales documents from CRM  to R/3 through CRM middleware .
    Please help me out in this regard .
    Regards
    Debasri Sarkar

    Hi Debasri
    It would be best if you try the Best Practices available on [CRM Best Practices|http://help.sap.com/content/bestpractices/crossindustry/bestp_crossindustry_crm.htm]
    Choose the CRM Version you are working on. On the next page that opens up, choose Technical Information-->Building blocks from LHS.
    And you can use the Best practice guide titled CRM Master and Transaction Data Replication there to know more about BP and transaction replication between CRM and ECC.
    Hope this would help You
    Regards
    Rekha Dadwal-Shet

  • Delta replication of Sales Org, Sales Off and Sales Group (ECC to CRM)

    HI All,
    I am struck with the delta of the Sales Area.
    Sales org with 6 Sales Offices and 6 Sales Group were created in the ERP and all this were replicated in to CRM in Initial but now my client wants to add 3 more sales offices with 3 Sales Groups.
    Sales Offices and sales group were maintained in the ERP system and i have created the Sales Offices in CRM but the problem is those sales offices and Sales groups were not reflecting in CRM.
    Newly added Sales Offices and Sales Groups were not replicated in CRM?
    I was trying to assign the ERP Sales Org,Offices, Sales Group  with CRM Sales Org, Office, Sales Group in "Assign SAP CRM Sales Org. to SAP ECC Sales Org.""Assign SAP CRM Sales Offices to SAP ECC Sales Offices" , "Assign SAP CRM Sales Group to SAP ECC Sales Group" but i can not view the ERP Sales groups.
    So what should i do inorder to replicate the newly added Sales off. and Sales Groups in CRM which were created in ERP?
    Thanks and Regards,
    Arun

    Hello Arun,
    You have already created 3 Sales Offices & 3 Sales Group in SAP ECC Enterprise Strurcture.Now you require these new sales offices & sales groups into CRM System.
    For that you use Transaction CRMC_R3_ORG_GENERATE. Here in this transaction you can see your newly created sales offices & sales groups. You have to select these rows & click on "Generate Selected Lines".
    Once you have done with this you can see new rows added with New Organization units for each unique sales Office & sales groups.After this dont forget to SAVE.
    Now You can assign the ERP Sales Offices & Sales Groups to CRM Sales Office & CRM Sales Group.
    Best Regards,
    Rajendra

  • 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

  • Tables of purchase and sales

    please tell me the purchase and sales transaction codes and to this codes name the relevant table these codes are joined up

    Hi.....
      _SALES_
    Sales orders Name Description Uses
    LIKP Shipped Lines header   
    LIPS Shipped Lines detail  
    VBAK Order header Every order (unless archiving)
    VBAP Table fields Every line item (unless archiving)
    VBBE Open sales order line items Great file, but be careful. Contents don't reflect orders that do not affect purchasing (go figure).
    VBEP Schedule line item   
    VBFA Document flow  Let's you move from order to shipping document to invoice.
    VBUK Order status   
    VBUP Line item detail status   
    VBFK Invoicing header   
    VBFP Invoicing detail
    PURCHASE
    Purchasing Name Description Uses
    EINA Purchasing inforecord  by MATNR/LIFNR contains things like vendor material number and access key for EINE 
    EINE Purchasing inforecord detail  Contains minimum purchase, group, currency 
    EKPO Purchase orders   
    EKET Scheduled lines   
    EKES Vendor confirmed lines 
    Sravani.
    Plz reward points if useful.

  • Uaable to create a sales transaction

    Hi,
    I'm trying to create a Sales Transaction for a business partner. But I'm getting a error "No valid sales channel for this business partner. Enter a Sales Channel in the business partner's sales area data."
    I already have entered the Sales Area data.
    Please advice.
    Thanks in advance.
    Sandeep

    Hi All,
    Thanks for your response.
    Well, I had done one basic mistake. The Sales Org did not have the Mobile Sales employee mapped to it. I did that and replicated the org structure to the Mobile Client.
    But now when I try to create the Sales transaction, I get the following error.
    "The combination of sales area and sales transaction type is not valid."
    Please advice.

  • Separate sales and return transaction for POSDM interface to ECC

    Hi experts
    We have a requirement to separate sales and return transaction movement types (251 and 252) for even the same articles.
    Currently, we are using two-step process but the aggregation will combine both sales and return transactions together.
    (For example, if i sell 2 article A and return 1 article A, the system will aggregate to selling only 1 article A with movement type 251.
    But we want to have movement type 251 posting for 2 article A, and movement type 252 posting for 1 article A.)
    Would you have any recommendation in terms of configuration?
    Thanks a lot for that.
    BR
    Dom

    Hi Rashi Gaur,
    Yes, As already explained by Vikrant, You Can create a separate task group for sales and assign that to sales item type (2001) and Create separate task group for returns and assign that to return item type (2801). This can be performed in two-step agregation process. The sales records will be in and returns will be .
    Thanks and Regards,
    Ramesh D

  • Number Range issues with sales orders in CRM and R/3

    Hi,
    We are currently using CRM4.0. I have sales orders created in R/3 and they are replicated into CRM.  These sales orders can only be created in R/3.  I have given them a number range of 0000000001 and 0005899999, however we have reached the number 0005899999 so we increased the internal number range for the sales orders in R/3 to 0009499999, however we forgot to update the number range for the corresponding sales transaction type in CRM so we are getting the following error in CRM:
    +Enter a business transaction number between 0000000001 and 0005899999
    Message no. CRM_ORDERADM_H532
    Diagnosis
    You have attempted to enter a transaction number which is not allowed for the transaction type.
    Procedure
    Enter a number between  &1 and &2. Make sure that you issue a number which has not already been issued.+
    We have now updated the CRM number range to match that in R/3 to 0000000001 and 0009499999 but we are still getting the error above on our existing sales orders in CRM.  I thought that increasing this number range it will remove the error but when I open sales orders in CRM the error is still there. 
    Is there any way to remove this error message?  Any tips or advice would be much appreciated.
    Please note we've already checked the post Re: Number Range Problem and note 427289.
    Kind Regards
    JoJo

    Hi Sirisha,
    The solution depends on the exact issue you are facing.
    The CRM Sales Order is created OK, but you only see the error when you open the Sales Order?
    If this is the case, then you can follow the steps below:
    1. Find the Message ID and Message No for the error message
    2. Use Program - CRM_MESSAGES_DELETE to delete error messages from the error producing Sales Orders.
    Let me know if this is not the issue you are facing.
    Regards,
    Nelson

  • Creation of sales order in CRM and replicating it to Multiple ECC system.

    We have a requirement for creation of sales order in CRM and replicating it to Multiple ECC system.
    We have checked the following standard Adapter objects in transaction R3AC1.
    BUS_TRANS_MSG
    The initial flow contexts does not support target site type as R/3(SMOF_ ERPSITE). So we are not able to replicate the sales order from CRM
    to ECC.
        2. SALESDOCUMENT
    Here the initial flow contexts does not support flow from CRM -> R/3 as we don’t see the target site as CRM.
    Please let us know if the standard sap middleware objects don’t support the sales order flow from CRM to multiple ECC or is there any
    other adapter object we need to use for this.

    Hey Vijay Duvvada,
    I hope you are already referred below sap note  and which explains scope & how to do   -
    1084315 - Consulting: Information about the multiple backend scenario
    1763516 - How-to: Basic Setup of MEP
    As explained by Rohit Sharma data should be start flowing to multiple sites.
    please let me know if it does help.
    Regards,
    Arjun

  • Mutual Changes of sales document in  CRM and ECC

    HI
    1.We have a scenario as we are creating orders in CRM, but want to change the same in ECC. Also whatever changes we do in ECC should flow back to CRM.
    2.Similarly, if we create sales order in ECC, it should be changeable in CRM and the corresponsing changes flow back to ECC.
    I came across following SAP notes for the same.
    1.889051: Scenario A
    2.642944:Interdependent changes
    My question is What is the difference between Scenario A and Interdependent Changes?
    Please help urgently.
    Regards

    Hi D J,
    Check the below link.
    Data Exchange CRM <--> ECC Sales transactions
    Hope this helps.
    Thanks.
    Best Regards,
    Arun Sankar.

  • Creating action in CRM sales transaction to trigger RFC in R/3?

    Hello gurus
    We wish to replicate our contracts from CRM to R/3  but since SAP is not supporting it, I heard that one option that we have is to enable actions in our CRM sales transactions, which when executed will trigger an RFC call to R/3 system and then create same transactioon there as well...
    Could anyone please shed some light as to how this can be done?
    Please advise.
    Regards
    Jai

    Hello,
    I should prefer using the ORDER_SAVE Badi, using a queued RFC to create the dat in the R/3 system.
    Regards,
    Fred

Maybe you are looking for