My Oracle Support Banner

Unable To Set WoNumber Field While POSTing /crmRestApi/resources/11.13.18.05/customerWorkOrders (Doc ID 2964150.1)

Last updated on APRIL 19, 2024

Applies to:

Oracle Fusion B2B Service Cloud Service - Version 11.13.23.04.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.23.04.0 version, Work Orders

Unable to set WoNumber field while POSTing /crmRestApi/resources/11.13.18.05/customerWorkOrders

I do a REST POST of /crmRestApi/resources/11.13.18.05/customerWorkOrders with the foll payload

{
"Title": "WO5 created by REST",
"OwnerTypeCd": "ORA_SVC_CUSTOMER",
"AccountPartyId": "30000000xxxxxx",
  "FieldServiceResourceId": "30000000xxxxxx",
  "WoIntegrationCd": "ORA_WO_INT_SVC",
  "IBAssetId": "10000000xxxxx",
  "WoNumber": "xxxxxx"
}

I get a 400 Bad request response with the following payload

{
  "title": "Bad Request",
  "status": "400",
  "o:errorDetails": [
  {
  "detail": "Reference Number cannot be updated.",
  "o:errorCode": "27008",
  "o:errorPath": "/WoNumber"
  }
  ]
}

WoNumber is the PUID and I should be able to set it to a unique value from an external system. This is how most entities in CRM work, not sure why this is behaving differently. This is a product bug.

Doc Ref: https://docs.oracle.com/en/cloud/saas/sales/faaps/op-customerworkorders-wonumber-get.html
WoNumber: string
Title: Reference Number
Read Only: true
Maximum Length: 30
The alternate unique identifier of the work order. This value is system-generated, and is configured in the work order profile options SVC_WO_NUMBER PREFIX and SVC_WO_NUMBER_FORMAT. The default configuration is WO0000000000.

Business Use Case: Customer uses ServiceMax as an external Field Service system and imports WorkOrders and Charges aka Debriefs (Service Logistics entity) from that system. They need to set the WoNumber as the ServiceMax Work Order Number. Now, I am having to create a custom field, make it indexable and searchable to store this value. But even then, I cannot easily search for the WO from the landing page using the Find box.

ERROR
-----------------------
400 Bad Request

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.