Reopen one purchase order
post
/fscmRestApi/resources/11.13.18.05/purchaseOrders/{purchaseOrdersUniqID}/action/reopen
Reopens the purchase order according to the reopen action. Reopen actions include reopen for receiving, reopen for invoicing, reopen, and reopen finally closed. When manually reopening the purchase order, a check for allowable reopen statuses is performed at the purchase order level. Reopen actions roll down to child levels. If a manual reopen action is taken at the purchase order level, it sets the status at the purchase order line and schedule level.
Request
Path Parameters
-
purchaseOrdersUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Purchase Orders resource and used to uniquely identify an instance of Purchase Orders. The client should not generate the hash key value. Instead, the client should query on the Purchase Orders collection resource in order to navigate to a specific instance of Purchase Orders to get the hash key.
Header Parameters
-
Effective-Of: string
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: string
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: string
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
-
reopenAction: string
Value that indicates the reopen action. Valid values include reopenForReceiving, reopenForInvoicing, reopen, or reopenFinallyClosed. This attribute doesn't have a default value.
-
reopenBudgetDate: string
(date)
Value that indicates the date for reinstating previously liquidated funds when reopening a finally closed document subject to budgetary control. If omitted, the fund reservation defaults to the document's budget date.
-
reopenReason: string
Value that indicates the reason for reopening the document. This attribute doesn't have a default value.
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): string
If the request is successful, then this action returns a value of Success.