Create or revise a negotiation response
post
/fscmRestApi/resources/11.13.18.05/draftSupplierNegotiationResponses/action/CreateNegotiationResponse
Create or revise a supplier response or a surrogate response.
Request
Header Parameters
-
Effective-Of:
This header accepts a string value. The string is a semi-colon separated list of
= . It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers. -
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.
Supported Media Types
- application/vnd.oracle.adf.action+json
Root Schema : schema
Type:
Show Source
object
-
parameters: object
parameters
Additional Properties Allowed: additionalPropertiesValue used to create a response for a negotiation. Required attributes include ProcurementBU, Negotiation, AuctionHeaderID, Supplier, SupplierSite, SupplierContact, Buyer, ResponseIntent, and SourceResponse.
Nested Schema : parameters
Type:
object
Additional Properties Allowed
Show Source
Value used to create a response for a negotiation. Required attributes include ProcurementBU, Negotiation, AuctionHeaderID, Supplier, SupplierSite, SupplierContact, Buyer, ResponseIntent, and SourceResponse.
Response
Supported Media Types
- application/json
- application/vnd.oracle.adf.actionresult+json
Default Response
The following table describes the default response for this task.
Root Schema : schema
Type:
Show Source
object
-
result(required): object
result
Additional Properties Allowed: additionalPropertiesIf the custom action is successful, then it returns a draft response number.
Nested Schema : result
Type:
object
Additional Properties Allowed
Show Source
If the custom action is successful, then it returns a draft response number.
Examples
This example describes how to create or revise a negotiation response.
Example cURL Command
Use the following cURL command to submit a request on the REST resource.
curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/draftSupplierNegotiationResponses/action/CreateNegotiationResponse"
Example Request Body
The following example includes the contents of the request
body in JSON format. You replace the request
payload in the cURL command with the contents of the Example Request Body.
The request payload specifies attribute values that the command will use in the
record that it updates.
{ "parameters": { "AuctionHeaderId"300100546799787", "Negotiation": "40124", "ProcurementBU":"Vision Scotland", "ProcurementBUId":"15567", "Supplier": "Super Computers", "SupplierId":"12737", "SupplierContact":"Harley, Kims", "SupplierContactId":"299954", "SupplierSite":"Edinburg", "SupplierSiteId": "5058", "TermsAcceptedFlag": true } }
Example Response Body
The following example includes the contents of the response body in JSON format:
{ "Response": "188755" }