Skip to Content

Which approach to take - Custom iFlow or Custom RFC or both ?

Dear experts,

I have a requirement which is a custom process so it would need some sort of custom integration between the backend ERP system & C4C

What i am confused here, is the approach I should be taking - Do i need a custom iFlow or should I go for point to point integration using RFC or a mix of both is needed - I am puzzled so asking for help. If you can advise the best practice approach here, its highly appreciated.

Requirement - On some event on Service Ticket, I need to trigger an SD document creation in ERP. The C4C ticket will not have any parts or service items on it so the std. release to ERP scenario can not be used here. This SD document creation is required for some specific reason and will always have specific details.

The C4C Ticket & this SD Document should have status integration such that change of status on C4C also changes the status on SD document and vice-versa.

There is no need as such for docflow & PDF posting of SD transaction onto C4C.

Now there are 2 ways in my mind to handle this

1) via RFC Function Modules - Create RFC FM in ERP & expose it as a WEBService, get its WSDL, create Communication scenario & communication arrangement in C4C SDK to consume this web service.

on C4C event, implement the code to invoke this RFC via Webservice consumption which would create rquired SD quote and would return the ERP SD quote ID. Store the id in a custom field on ticket or add to BTDReference node of ticket root.

Do I also need an iFlow in this case ? if yes - what it would do other than authentication between systems ?

2) via custom iFlow -

Create custom idoc & apply the logic in IDocFunction Module to create SD document in ERP. Create custom iflow and map ticket to idoc fields.

Here, I am not clear - how to invoke /trigger this iflow on some event (say a button click) on C4C Ticket. Does this mean I will also need to consume the custom idoc WSDL in C4C to call the idoc FM on Service ticket event ? if yes, then how this is different to option 1 - I mean what the use of having idoc here ?

Kindly let me know if you have done anything similar to this- what should be my approach ?

Thanks & Regards


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Feb 17, 2018 at 11:03 AM

    Solved it myself - Used the standard trigger & std. iflow & tweaked it in ERP & HCI.

    I can confirm that, as of now, is no way to trigger an iflow from C4C in a custom trigger

    Add comment
    10|10000 characters needed characters exceeded

    • is there any option available in newer version? I have similar requirement to call the custom iFlow from C4C. is it possible, if yes, please share the link which could help us

  • Sep 25, 2017 at 10:52 AM


    Here is my experience

    ECC to C4C via HCI, you will get into some details from C4C, basically a query result of standard customer object.

    There is standard WSDL for customer query which u can consume directly in ECC,

    But wanted to go via HCI, for same scenarios.So u followed the below steps in order to achieve this:

    1) Created a custom RFC and it's web service.

    2) Downloaded the WSDL of the web service created in Step 1.

    3) Created a consumer proxy with the WSDL obtained in step 2 so that u can give the end point of the HCI iflow.

    4) Created an iflow in HCI & mapped the source and target WSDLs (ECC WSDL & C4C WSDL) respectively.



    Add comment
    10|10000 characters needed characters exceeded

    • Thanks for your reply.

      Can you shed some light on what will trigger the iflow?

      This is the main question as I have highlighted in option 2. If I am using HCI & created custom iflow to map C4C & ECC WSDL fields - How do I then trigger this iflow ?

      Awaiting a reply.

      Thanks & Regards


  • Sep 26, 2017 at 08:27 AM


    I have a document on it but I can't attached it here ! its more then 1MB

    Can you share the mail id ? or Please go through the Link .



    Add comment
    10|10000 characters needed characters exceeded