SAP Knowledge Base Article - Public

2747209 - Automatic Account Determination is Not Working While Creating Tickets Using OData Services


You are trying to create new Tickets using OData services and you noticed that the system is not automatically determining the account for the ticket, based on the contact ID you are providing in the payload.


  • SAP Cloud for Customer.

Reproducing the Issue

  1. Create a POST request for the target URL (XXXXXX represents the tenant URL)
  2. Provide the mandatory information and the BuyerMainContactPartyID.
  3. Send the request.
  4. Find the created ticket and see no account has been determined based on the contact ID.


Account populating based on the contact is an UI behavior only. If you check the activity Tickets for Customer Support and go to the Involved Parties section, you can select the Account party role and click on the Maintain Determinations button. There you will see there is no party determination related to the Account based on the contact.


When using OData to create new tickets the Account (BuyerPartyID) needs to be provided in the payload along with the contact ID (BuyerMainContactPartyID).


odata services, service request collection, servicerequestcollection, c4codataapi, create tickets with odata, automatic account determination , KBA , LOD-CRM-SRP , Service Request Processing , LOD-CRM-INT-API , OData API (C4C Only) , How To


SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions