Validate requisition preferences
post
/fscmRestApi/resources/11.13.18.05/requisitionPreferences/{requisitionPreferencesUniqID}/action/validatePreference
Validates the requisition preferences for the requisitioning business unit.
Request
Path Parameters
-
requisitionPreferencesUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Requisition Preferences resource and used to uniquely identify an instance of Requisition Preferences. The client should not generate the hash key value. Instead, the client should query on the Requisition Preferences collection resource in order to navigate to a specific instance of Requisition Preferences to get the hash key.
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:
object
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 request is successful, then this action returns a value of SUCCESS. Otherwise, it returns an error.
Nested Schema : result
Type:
object
Additional Properties Allowed
Show Source
-
object additionalProperties
Additional Properties Allowed: additionalProperties
If the request is successful, then this action returns a value of SUCCESS. Otherwise, it returns an error.
Examples
This example describes how to validate requisition preferences.
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/requisitionPreferences/requisitionPreferencesUniqID/action/validatePreference"
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.
{ "name":"validatePreference", "parameters":[] }
Example Response Body
The following example includes the contents of the response body in JSON format:
{ "result": "SUCCESS" }