on 05-12-2015 11:01 AM
Hi,
We are using Manage Accounts (Customer master) and Manage Materials (Material master) A2X services provided by SAP to pass Customer and Material master data from a non-SAP system to C4C system. It is crucial for us to pass External ID and External System details to C4C. However, there is no provision in these A2X services to pass these details.
Please help us identify how we can pass External ID and External System details to C4C using these A2X services.
Thanks,
Netrey
Hi,
Please have a look at the link below.
Under Manage Object ID. Make sure this web service has been configured in C4C.
Web Service APIs in SAP Cloud for Customer 1502 - February 2015
Regards,
Jannus Botha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I saw that you already answered. In my opinion there are many different approaches to this scenario. In most cases we did not use the object identifier mapping (separate bo) because it is used for the standard ERP and CRM integration services.
In case of A2X services we did in most cases the following:
1. Extending the BO with a custom field “External ID”.
2. Extending both the Manage and the Query A2X services.
3. Fill the External ID when sending the data.
4. Use the Query A2X service to identify the right internal id via the external id field.
All the above can be achieved via key user tools. For more complex scenarios PDI might be required.
This requires an orchestration at a middleware.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Limbach,
I have a similar requirement to pull the data from C4C to an external system. Query Account does not have field External ID. Could you please elaborate what do you mean by "3. Fill the External ID when sending the data."
Do you mean to create a work flow on the extension field using KUT? or move the data to extension field in .xbo using PDI. Which event should I use in this case ?
We don't want to use a separate API like "Query Object Identifier mapping"
The general philosophy behind A2X web services is that the client system calling C4C APIs - has to own that task.
Yes, you can create your 2 extra fields to save the Source System and Source ID, but you have to fill those 2 fields when you create that Account record - either rmanually in the Account UI or in the payload of the web service call.
Save PDI approach as a last resort - you want to simplify your process.
Put the values into the record on creation, and it will be there when you retrieve it.
If it's a locally created Account record, those 2 fields will be blank.
Hi Netrey
I forwarded this to one of our expert consultants. He said that the external ID is part of a separate business object, that's why it's not in the service. He said that for non-SAP integration you will need to do the ID mapping and it's probably easist for you to add your own external ID field then you can extend the service with the new field. He said PDI might not even be needed.
-ginger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.