Check funds availability.
post
/fscmRestApi/resources/11.13.18.05/purchaseRequisitions/{purchaseRequisitionsUniqID}/action/checkFunds
Checks funds availability against control budgets for all the requisition lines distributions. Funds check can be manual or implicit. Funds check is manual when it's invoked by the user and is implicit when it's performed during the submit operation.
Request
Path Parameters
-
purchaseRequisitionsUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Purchase Requisitions resource and used to uniquely identify an instance of Purchase Requisitions. The client should not generate the hash key value. Instead, the client should query on the Purchase Requisitions collection resource in order to navigate to a specific instance of Purchase Requisitions 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
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): array
result
If the request is successful, then this action returns a value of SUCCESS within the object. Otherwise, this action returns a value of FAILURE or WARNING.
Nested Schema : result
Type:
array
If the request is successful, then this action returns a value of SUCCESS within the object. Otherwise, this action returns a value of FAILURE or WARNING.
Show Source
-
Array of:
object items
Additional Properties Allowed: additionalProperties