Query data using two different Odata services sap c4c

[former_member589941]

Hi Team,

We have a requirement to fetch data from two different Odata services. i, e fetch the ticket details based on the Email ID.

To do this , first, fetch the business partner ID based on the Email ID using 'Customer' Odata Service then pass this business partner ID as 'Process Party ID' in 'service ticket; Odata Service which would fetch the service ticket details, ideally we would need to trigger these 2 services twice from external system, however our requirement is to trigger the odata service once and fetch the ticket details based on the Email ID.

so please suggest how can we achieve this ?

Shall we create a custom BO with action and in Action, write a piece of logic to Query data based on the email ID then pass this Email id to "Service Ticket QueryByElements".

and trigger this BO action with help of "Function Import".

does that work fine or is there any other alternatives with which we can achieve this functionality.

Thank you so much,

[former_member185414]

Please post entire details as a new question

[former_member590830]

I am currently serving SAP S/4 Hana Cloud. I can't create a purchase order now. The relative API for the purchase order is: <app:workspace> <atom:title type="text">Data</atom:title> <app:collection sap:content-version="1" href="A_PurchaseOrder"> <atom:title type="text">A_PurchaseOrder</atom:title> <sap:member-title>A_PurchaseOrderType</sap:member-title> </app:collection> <app:collection sap:content-version="1" href="A_PurchaseOrderItem"> <atom:title type="text">A_PurchaseOrderItem</atom:title> <sap:member-title>A_PurchaseOrderItemType</sap:member-title> </app:collection> <app:collection sap:content-version="1" href="A_PurchaseOrderScheduleLine"> <atom:title type="text">A_PurchaseOrderScheduleLine</atom:title> <sap:member-title>A_PurchaseOrderScheduleLineType</sap:member-title> </app:collection> <app:collection sap:content-version="1" href="A_PurOrdAccountAssignment"> <atom:title type="text">A_PurOrdAccountAssignment</atom:title> <sap:member-title>A_PurOrdAccountAssignmentType</sap:member-title> </app:collection> <app:collection sap:content-version="1" href="A_PurOrdPricingElement"> <atom:title type="text">A_PurOrdPricingElement</atom:title> <sap:member-title>A_PurOrdPricingElementType</sap:member-title> </app:collection> </app:workspace> I don't know why this is not about system configuration, because I am using a communication scenario provided by SAP S/4 Hana Cloud. The scene number is 0053. It may be that the CDS view in this communication scenario is not equipped with ODATA service.

[former_member185414]

I would give a general perseptive as I am not sure about C4C working.

If you have ruled out the possibility of creating a new service (bec. here you can write whatever logic you need), then your idea will work.

Just copy the standard methods which derive first the BP Id and then the Ticket details and wrap them together.

Also, I am not sure but if it's possible in C4C then use OData extensibiliy concepts.

[former_member589941]

hi ankit,

thank you so much for the response,

In C4C, the way the services and the methods have been mapped is some what different unlike on Prem SAP CRM , so this seems to be not possible.

However i have created custom BO with custom Odata service to fetch these details, but facing a lots of issues.

[former_member185414]

Ok... What kind of issues are you encountering, you can ask in forum and we can help.