Mass Release to SAP ERP - Service Ticket Action Button

[former_member236588]

Hello all,

We are migrating legacy data (from an external non SAP application) to C4C using the Data Workbench. In this migration we are migrating (importing) Service Requests (Tickets) into C4C. We need to release all these Service Requests (Tickets) to SAP ERP. We have the integration in place between C4C and the SAP ERP system.

However we are looking for a mechanism to mass release this. We do not find this available through the Migration Workbench. It is not feasible to manually open each Service Request and click on the Action - Release to ERP button.

Let me know if there is any way to mass release these tickets/perform this action. Any pointers on this will be appreciated.

Thanks and regards,

Nikhil

[former_member145911]

Hi Nikhil,

You could try a combination of a Workflow Rule and update function of the data workbench.

for e.g. create a simple WF rule with the action ->Release to ERP. Here you may need a KUT extension field that can be set and use that as the condition.

Then using the update function of the data workbench, set a value in your extension field that will trigger your WF rule. The updated tickets will then be automatically released to ERP. Bare in mind, the Release to ERP action will be a header action so the whole ticket will be replicated to ERP if the conditions are met.

Regards

Jameel

[former_member236588]

Thank you for the response Jameel. This approach should work.

[Damo]

Hello,

How does the System release tickets to ERP in mass via the data workbench method? Does it bundle all tickets together in a message? Does it release one by one?

Does ECC/ERP accept if c4c releases the tickets to ERP in a bulk or single message?

Regards

[former_member145911]

Hi,

Not sure the scenario you have in mind but if it's in relation to the overall thread i.e. mass releasing tickets to ERP then this is on a ticket by ticket basis. This is because each WF rule is triggered on conditions being met within an individual ticket rather than a group of tickets. Each ticket would then trigger a single Webservice call and a single Idoc received in ECC per ticket. Of course you have to bare in mind that asking the system to process a bunch of requests will take time and have a performance impact in both C4C and ECC.

Hope that helps.

Regards,

Jameel