Record acknowledgment for the purchase agreement.
patch
/fscmRestApi/resources/11.13.18.05/purchaseAgreementAcknowledgments/{purchaseAgreementAcknowledgmentsUniqID}
Request
Path Parameters
-
purchaseAgreementAcknowledgmentsUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Purchase Agreement Acknowledgments resource and used to uniquely identify an instance of Purchase Agreement Acknowledgments. The client should not generate the hash key value. Instead, the client should query on the Purchase Agreement Acknowledgments collection resource in order to navigate to a specific instance of Purchase Agreement Acknowledgments 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/json
Root Schema : schema
Type:
Show Source
object-
AcknowledgmentNote: string
Title:
Acknowledgment NoteMaximum Length:4000Note with details regarding the acknowledgment, required if the agreement is being rejected. -
AcknowledgmentResponse: string
Title:
Acknowledgment ResponseMaximum Length:25Acknowledgment response for the purchase agreement. Values are ACCEPT when the agreement is accepted or REJECT when the agreement is rejected. -
lines: array
Lines
Title:
LinesAcknowledgment response at the line level are recorded. -
SupplierAgreement: string
Title:
Supplier AgreementMaximum Length:25Number that indicates the supplier document number.
Nested Schema : Lines
Type:
arrayTitle:
LinesAcknowledgment response at the line level are recorded.
Show Source
Nested Schema : schema
Type:
Show Source
object-
AgreementHeaderId: integer
(int64)
Value that uniquely identifies the purchase agreement.
-
RejectionReason: string
Title:
Rejection ReasonMaximum Length:240Reason for rejecting the line. -
Response: string
Title:
ResponseMaximum Length:25Acknowledgment response for the line. Values include ACCEPT when the line is accepted, or REJECT when the line is rejected.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
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.
Root Schema : purchaseAgreementAcknowledgments-item-response
Type:
Show Source
object-
AcknowledgmentDueDate: string
(date)
Title:
Acknowledgment Due DateRead Only:trueDate on which the application requests the supplier to acknowledge the purchase agreement. -
AcknowledgmentNote: string
Title:
Acknowledgment NoteMaximum Length:4000Note with details regarding the acknowledgment, required if the agreement is being rejected. -
AcknowledgmentResponse: string
Title:
Acknowledgment ResponseMaximum Length:25Acknowledgment response for the purchase agreement. Values are ACCEPT when the agreement is accepted or REJECT when the agreement is rejected. -
AcknowledgmentWithinDays: number
Title:
Acknowledge Within DaysRead Only:trueNumber of days the supplier can decide to accept or reject the purchase agreement. -
AgreementHeaderId: integer
(int64)
Read Only:
trueValue that uniquely identifies the purchase agreement. -
AgreementNumber: string
Title:
AgreementRead Only:trueMaximum Length:30Number that uniquely identifies the purchase agreement in the procurement business unit. -
ChangeOrderNumber: string
Title:
Change OrderRead Only:trueMaximum Length:80Number that uniquely identifies the change order for a document. -
lines: array
Lines
Title:
LinesAcknowledgment response at the line level are recorded. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
ProcurementBU: string
Title:
Procurement BURead Only:trueMaximum Length:240Business unit that manages and owns the purchase agreement. -
ProcurementBUId: integer
(int64)
Read Only:
trueValue that uniquely identifies the procurement business unit. -
RequiredAcknowledgment: string
Title:
Required AcknowledgmentRead Only:trueMaximum Length:80Acknowledgment from the supplier. Possible values include: Document and Line: The supplier must acknowledge both the header and line of the purchase agreement. Document: The supplier must acknowledge the header of the purchase agreement. None: The purchase agreement doesn't require acknowledgment. -
RequiredAcknowledgmentCode: string
Read Only:
trueMaximum Length:1Abbreviation identifying the acknowledgment required from the supplier for the purchase agreement. Values include:Y: Document and Line, D: Document, and N: None. -
SupplierAgreement: string
Title:
Supplier AgreementMaximum Length:25Number that indicates the supplier document number.
Nested Schema : Lines
Type:
arrayTitle:
LinesAcknowledgment response at the line level are recorded.
Show Source
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : purchaseAgreementAcknowledgments-lines-item-response
Type:
Show Source
object-
AgreementHeaderId: integer
(int64)
Value that uniquely identifies the purchase agreement.
-
AgreementLineId: integer
(int64)
Read Only:
trueValue that uniquely identifies the purchase agreement line. -
LineNumber: number
Title:
LineRead Only:trueValue that uniquely identifies the purchase order or agreement line. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
RejectionReason: string
Title:
Rejection ReasonMaximum Length:240Reason for rejecting the line. -
Response: string
Title:
ResponseMaximum Length:25Acknowledgment response for the line. Values include ACCEPT when the line is accepted, or REJECT when the line is rejected.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Links
- lines
-
Parameters:
- purchaseAgreementAcknowledgmentsUniqID:
$request.path.purchaseAgreementAcknowledgmentsUniqID
Acknowledgment response at the line level are recorded. - purchaseAgreementAcknowledgmentsUniqID: