Duplicate one purchase order
post
/fscmRestApi/resources/11.13.18.05/purchaseOrders/{purchaseOrdersUniqID}/action/duplicate
Duplicates a purchase order, including its header, lines, schedules, distributions, contract terms, and attachments. This action fetches the original purchase order, sets default values for it, and generates a new purchase order upon successful validation. If the user opts to copy attachments and contract terms, and they're present in the original document, the procedure duplicates these terms and attachments based on the specified input parameters.
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:
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
-
copyAttachments: string
Value that indicates whether to copy original purchase order attachments or not. Valid values include yes or no. The default value is no.
-
copyContractTerms: string
Value that indicates whether to copy original purchase order contract terms with existing clauses, copy original contract terms and update clauses with latest versions, or don't copy contract terms when duplicating a purchase order. Valid values include existingClauses, latestClauseVersions, or no. The default value is no.
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, this action returns a value of SUCCESS along with the unique identifier of the created purchase order. Otherwise, it returns an error.
Nested Schema : result
Type:
object
Additional Properties Allowed
Show Source
If the request is successful, this action returns a value of SUCCESS along with the unique identifier of the created purchase order. Otherwise, it returns an error.