Get one schedule

get

/fscmRestApi/resources/11.13.18.05/purchaseOrderSchedulesForLandedCosts/{POLineLocationId}

Request

Path Parameters
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • 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
  • 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
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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 : purchaseOrderSchedulesForLandedCosts-item-response
Type: object
Show Source
Nested Schema : Shipment Details
Type: array
Title: Shipment Details
The Shipment Details resource gets the information of shipments associated with the purchase order schedule.
Show Source
Nested Schema : Trade Operation Details
Type: array
Title: Trade Operation Details
The Trade Operation Details resource gets the information of the trade operation charges created for the purchase order schedule.
Show Source
Nested Schema : purchaseOrderSchedulesForLandedCosts-shipmentDetails-item-response
Type: object
Show Source
Nested Schema : purchaseOrderSchedulesForLandedCosts-tradeOperationDetails-item-response
Type: object
Show Source
  • Title: Charge Line Number
    Read Only: true
    Number that identifies the trade operation charge line.
  • Title: Charge Line Status Meaning
    Read Only: true
    Maximum Length: 80
    Abbreviation that uniquely identifies the status of the charge line. Valid values include Allocated, Allocated with Warning, Allocation in Error, Cancelled, Draft Allocation, Incomplete, New, Pending Association, Ready for Allocation, and Requires Reallocation.
  • Links
  • Title: Charge Name
    Read Only: true
    Maximum Length: 80
    Charge name for which the estimates and actual amounts are entered.
  • Title: Charge BU Functional Currency
    Read Only: true
    Maximum Length: 15
    Functional currency of the charge business unit.
  • Title: Actual Amount
    Read Only: true
    Total actual amount incurred on the trade operation.
  • Title: Estimated Amount
    Read Only: true
    Total estimated amount incurred on the trade operation.
  • Title: Trade Operation ID
    Read Only: true
    Value that uniquely identifies the trade operation.
  • Title: Name
    Read Only: true
    Maximum Length: 80
    Name of the trade operation to which the charge line belongs.
  • Title: Number
    Read Only: true
    Maximum Length: 40
    Number that identifies the trade operation to which the charge line belongs.
Back to Top

Examples

This example describes how to get one schedule.

Example cURL Command

Use the following cURL command to submit a request on the REST resource:

curl -u username:password "https://servername/fscmRestApi/resources/version/purchaseOrderSchedulesForLandedCosts/POLineLocationId"

For example, the following command gets one schedule where the purchase order line location identifier is 300100088814877:

curl -u username:password "https://servername/fscmRestApi/resources/version/purchaseOrderSchedulesForLandedCost/300100088814877"

Example Response Body

The following shows an example of the response body in JSON format.

{
"AssociatedCharges": "With Charges",
"Buyer": "Furey,Clare",
"BuyerId": 100010026863783,
"LandedCostPOScheduleId": 84021,
"DeliveredToInventoryOrg": "V1",
"DeliveredToInventoryOrgId": 204,
"DestinationType": "Inventory",
"NeedByDate": "2020-12-31",
"OrderedQuantityInPrimaryUOM": 6,
"POApprovalDate": "2015-12-14",
"POLineLocationId": 300100088814877,
"ProcurementBU": "Vision Corporation",
"ProcurementBUId": 204,
"ProfitCenterBU": "Vision Corporation",
"ProfitCenterBUId": 204,
"PromisedDate": null,
"PurchaseOrderDescription": "Crank Shaft",
"PurchaseOrderFunctionalCurrencyAmount": 3000,
"PurchaseOrderCurrency": "US Dollar",
"PurchaseOrderCurrencyCode": "USD",
"PurchaseOrderHeaderId": 300100088814874,
"PurchaseOrderItemNumber": "CM-CRS-SD7",
"PurchaseOrderLineNumber": "1",
"PurchaseOrderLineId": 300100088814876,
"PurchaseOrderNumber": "VOP1003796",
"PurchaseOrderScheduleNumber": "1",
"RequisitioningBU": "Vision Corporation",
"RequisitioningBUId": 204,
"ShipToLocation": "V1 Ship Site A",
"ShipToLocationId": 20795,
"Supplier": "ZOKC_PODEL_PARTYMERGE_SUPPLIER1",
"SupplierId": 300100087618588,
"SupplierSite": "ZOKCPODS3SITE3",
"SupplierSiteId": 300100087618605,
"TaxExclusivePOPrice": 3000,
"UnitOfMeasure": "Each",
"UnitOfMeasureCode": "Ea",
"links": 
...
}
Back to Top