Skip to Content
author's profile photo Former Member
Former Member

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 12, 2005 at 08:00 AM

    Do you have any errors?

    Use transaction bd87 to look for the idocs (possibly with status '3').

    Do you get an error in the bdoc? What messages are given in the bdoc receiver log?

    If you cannot find the idocs, use transactions ST22 (short-dumps), smq1/smq2, sm21(system log) to look for any failures during the mapping/transfer.

    Michael.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 12, 2005 at 07:28 PM

    I've done this myself and you seem to be getting it right. The only thing you didn't specify were your outbound parameters.

    You have the option to group IDocs before sending them, instead of sending them immediatly. It's a pretty basic error but I don't know what kind of experience you have, so please don't feel insulted.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.