Jump to

• Request
• Response

Delete a revenue plan flexfield

delete

/fscmRestApi/resources/11.13.18.05/contracts/{contractsUniqID}/child/RevenuePlan/{RevenuePlanUniqID}/child/RevenuePlanDescriptiveFlexField/{RevenuePlanDescriptiveFlexFieldUniqID}

Request

Path Parameters

• RevenuePlanDescriptiveFlexFieldUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- BillPlanId and MajorVersion ---for the Revenue Plan Flexfields resource and used to uniquely identify an instance of Revenue Plan Flexfields. The client should not generate the hash key value. Instead, the client should query on the Revenue Plan Flexfields collection resource with a filter on the primary key values in order to navigate to a specific instance of Revenue Plan Flexfields.
  
  For example: RevenuePlanDescriptiveFlexField?q=BillPlanId=<value1>;MajorVersion=<value2>
• RevenuePlanUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- BillPlanId and MajorVersion ---for the Revenue Plans resource and used to uniquely identify an instance of Revenue Plans. The client should not generate the hash key value. Instead, the client should query on the Revenue Plans collection resource with a filter on the primary key values in order to navigate to a specific instance of Revenue Plans.
  
  For example: RevenuePlan?q=BillPlanId=<value1>;MajorVersion=<value2>
• contractsUniqID(required): string
  This is the hash key of the attributes which make up the composite key for the Contracts resource and used to uniquely identify an instance of Contracts. The client should not generate the hash key value. Instead, the client should query on the Contracts collection resource in order to navigate to a specific instance of Contracts to get the hash key.

Header Parameters

• Metadata-Context:
  If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
• REST-Framework-Version:
  The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Default Response

No Content. This task does not return elements in the response body.

Back to Top