Get all action not supported

get

/fscmRestApi/resources/11.13.18.05/purchaseOrderLifeCycleDetails

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 purchase order life cycle details according to the primary key.
      Finder Variables
      • POHeaderId; integer; Value that uniquely identifies the purchase order.
    • findByIntent Finds purchase order life cycle details according to intent.
      Finder Variables
      • Intent; string; Value that identifies the intent for accessing the Purchase Order Lifecycle Details resource. Valid values are APUser, POUser, LOBUser, SSPUser and NonAgentUser.
  • 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:
    • OrderNumber; string; Number that uniquely identifies the purchase order in the sold-to legal entity.
    • POHeaderId; integer; Value that uniquely identifies 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 : purchaseOrderLifeCycleDetails
Type: object
Show Source
Nested Schema : Items
Type: array
Title: Items
The items in the collection.
Show Source
Nested Schema : purchaseOrderLifeCycleDetails-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 15
    Code that identifies the purchase order currency.
  • Read Only: true
    Value of the goods and services delivered to the buying organization.
  • Read Only: true
    Value of the goods received by the buying organization, currently in receiving, not delivered or returned.
  • Read Only: true
    Value of goods shipped by the supplier, but yet to be received at the buying organization.
  • Invoices
    Title: Invoices
    The details about supplier invoices that are created against purchase orders, such as matched quantities and amounts and total invoice amounts.
  • Links
  • Read Only: true
    Total amount of the order according to the quantities and prices of the goods and service items specified on the order.
  • Title: Order
    Read Only: true
    Maximum Length: 30
    Number that uniquely identifies the purchase order in the sold-to legal entity.
  • Read Only: true
    Invoiced amount that has been paid.
  • Read Only: true
    Invoiced amount that has been partially paid.
  • Read Only: true
    Value that uniquely identifies the purchase order.
  • Receipts
    Title: Receipts
    The details about receipts and deliveries that are created against purchase orders, such as how many items have been received and when they were received.
  • Schedules
    Title: Schedules
    The details about the purchase order schedule, such as how many items were requested and ordered, as well information regarding how many of those items were shipped, received, and invoiced.
  • Shipments
    Title: Shipments
    The details about shipments that are created against purchase orders, such as how many items have been shipped, when they were shipped, and the carrier and tracking numbers for those shipments.
  • Read Only: true
    Invoiced amount that hasn't been paid.
Nested Schema : Invoices
Type: array
Title: Invoices
The details about supplier invoices that are created against purchase orders, such as matched quantities and amounts and total invoice amounts.
Show Source
Nested Schema : Receipts
Type: array
Title: Receipts
The details about receipts and deliveries that are created against purchase orders, such as how many items have been received and when they were received.
Show Source
Nested Schema : Schedules
Type: array
Title: Schedules
The details about the purchase order schedule, such as how many items were requested and ordered, as well information regarding how many of those items were shipped, received, and invoiced.
Show Source
Nested Schema : Shipments
Type: array
Title: Shipments
The details about shipments that are created against purchase orders, such as how many items have been shipped, when they were shipped, and the carrier and tracking numbers for those shipments.
Show Source
Nested Schema : purchaseOrderLifeCycleDetails-invoices-item-response
Type: object
Show Source
Nested Schema : purchaseOrderLifeCycleDetails-receipts-item-response
Type: object
Show Source
Nested Schema : purchaseOrderLifeCycleDetails-schedules-item-response
Type: object
Show Source
Nested Schema : purchaseOrderLifeCycleDetails-shipments-item-response
Type: object
Show Source
Back to Top