Record acknowledgment for the purchase order

patch

/fscmRestApi/resources/11.13.18.05/purchaseOrderAcknowledgments/{POHeaderId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Header Parameters
  • 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".
  • 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
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Acknowledgment Note
    Maximum Length: 4000
    Note with details regarding the acknowledgment, required if the order is being rejected.
  • Title: Acknowledgment Response
    Maximum Length: 1
    Acknowledgment response for the purchase order. Values are ACCEPT when the order is accepted or REJECT when the order is rejected.
  • Schedules
    Title: Schedules
    Acknowledgment response at the schedule level are recorded.
  • Title: Supplier Order
    Maximum Length: 25
    Number that identifies the document that the supplier created for the purchase order.
Nested Schema : Schedules
Type: array
Title: Schedules
Acknowledgment response at the schedule level are recorded.
Show Source
Nested Schema : schema
Type: object
Show Source
  • Title: Rejection Reason
    Maximum Length: 240
    Reason for rejecting the schedule.
  • Title: Response
    Maximum Length: 1
    Acknowledgment response for the schedule. Values include ACCEPT when the schedule is accepted or REJECT when the schedule is rejected.
  • Title: Supplier Order Line
    Maximum Length: 25
    Number or text that the supplier uses to identify a purchase order schedule.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • 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".
  • 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.
Body ()
Root Schema : purchaseOrderAcknowledgments-item-response
Type: object
Show Source
  • Title: Acknowledgment Due Date
    Read Only: true
    Date on which the application requests the supplier to acknowledge the purchase order.
  • Title: Acknowledgment Note
    Maximum Length: 4000
    Note with details regarding the acknowledgment, required if the order is being rejected.
  • Title: Acknowledgment Response
    Maximum Length: 1
    Acknowledgment response for the purchase order. Values are ACCEPT when the order is accepted or REJECT when the order is rejected.
  • Title: Acknowledge Within Days
    Read Only: true
    Number of days the supplier can decide to accept or reject the purchase order.
  • Title: Change Order
    Read Only: true
    Maximum Length: 80
    Number that uniquely identifies the change order for a document.
  • Links
  • Title: Order
    Read Only: true
    Maximum Length: 30
    Number that uniquely identifies the purchase order in the sold-to legal entity.
  • Read Only: true
    Value that uniquely identifies the purchase order.
  • Title: Required Acknowledgment
    Read Only: true
    Maximum Length: 80
    The application requires an acknowledgment from the supplier. Possible values include Document and Schedule: The supplier must acknowledge both the header and schedule of the purchase order. Document: Supplier must acknowledge the header of the purchase order. None: Purchase order doesn't require acknowledgment.
  • Read Only: true
    Maximum Length: 1
    Abbreviation identifying the acknowledgment required from the supplier for the purchase order. Values include:Y: Document and Schedule, D: Document, and N: None.
  • Schedules
    Title: Schedules
    Acknowledgment response at the schedule level are recorded.
  • Title: Sold-to Legal Entity
    Read Only: true
    Maximum Length: 240
    Legal entity that's financially responsible for purchases on the purchase order.
  • Read Only: true
    Value that uniquely identifies the legal entity that's financially responsible for purchases on the purchase order.
  • Title: Supplier Order
    Maximum Length: 25
    Number that identifies the document that the supplier created for the purchase order.
Nested Schema : Schedules
Type: array
Title: Schedules
Acknowledgment response at the schedule level are recorded.
Show Source
Nested Schema : purchaseOrderAcknowledgments-schedules-item-response
Type: object
Show Source
Back to Top