Get all purchase orders requiring acknowledgment

get

/fscmRestApi/resources/11.13.18.05/purchaseOrderAcknowledgments

Request

Query Parameters
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • Used as a predefined finder to search the collection.

    Format ?finder=<finderName>;<variableName>=<variableValue>,<variableName2>=<variableValue2>

    The following are the available finder names and corresponding finder variables

    • PrimaryKey Finds the purchase order requiring acknowledgment with the specified primary key.
      Finder Variables
      • POHeaderId; integer; Unique identifier of the purchase order requiring acknowledgment.
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
  • This parameter orders a resource collection based on the specified fields. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and "asc" or "desc". Specify "asc" for ascending and "desc" for descending. The default value is "asc". For example, ?orderBy=field1:asc,field2:desc
  • This query parameter defines the where clause. The resource collection will be queried using the provided expressions. The value of this query parameter is one or more expressions. Example: ?q=Deptno>=10 and <= 30;Loc!=NY

    Format: ?q=expression1;expression2

    You can use these queryable attributes to filter this collection resource using the q query parameter:
    • AcknowledgmentDueDate; string; Date on which the application requests the supplier to acknowledge the purchase order.
    • OrderNumber; string; Number that uniquely identifies the purchase order in the sold-to legal entity.
    • POHeaderId; integer; Value that uniquely identifies the purchase order.
    • SoldToLegalEntity; string; Legal entity that's financially responsible for purchases on the purchase order.
    • SoldToLegalEntityId; integer; Value that uniquely identifies the legal entity that's financially responsible for purchases on the purchase order.
  • The resource collection representation will include the "estimated row count" when "?totalResults=true", otherwise the count is not included. The default value is "false".
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.

There's no request body for this operation.

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
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested 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