1. REST API for Oracle Fusion Cloud SCM
  2. Tasks
  3. Inventory Management
  4. Completed Transactions in Inventory
  5. Lots in Completed Transactions

Get one lot

get

/fscmRestApi/resources/11.13.18.05/inventoryCompletedTransactions/{TransactionId}/child/lots/{lotsUniqID}

Request

Path Parameters
  • Value that uniquely identifies the transaction.
  • This is the hash key of the attributes which make up the composite key for the Lots in Completed Transactions resource and used to uniquely identify an instance of Lots in Completed Transactions. The client should not generate the hash key value. Instead, the client should query on the Lots in Completed Transactions collection resource in order to navigate to a specific instance of Lots in Completed Transactions to get the hash key.
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 : inventoryCompletedTransactions-lots-item-response
Type: object
Show Source
Nested Schema : Flexfields for Lot Attributes
Type: array
Title: Flexfields for Lot Attributes
The Flexfields for Lot Attributes resource manages the descriptive flexfields that modifies lot attributes. Use this resource only when the item is under lot control.
Show Source
Nested Schema : Serials in Lots in Completed Transactions
Type: array
Title: Serials in Lots in Completed Transactions
The Serials in Lots in Completed Transactions resource gets serial details for inventory transactions when the item is under both lot and serial control. The details include serial number, and so on.
Show Source
Nested Schema : Flexfields for Lots
Type: array
Title: Flexfields for Lots
The Flexfields for Lots resource manages the descriptive flexfields that modifies lots. Use this resource only when the item is under lot control.
Show Source
Nested Schema : inventoryCompletedTransactions-lots-lotAttributeDFFs-item-response
Type: object
Show Source
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name that references a lot attribute when the item is under lot control.
  • Title: Context Value
    Descriptive flexfield context display value that references a lot attribute when the item is under lot control.
  • Links
  • Title: Lot
    Maximum Length: 80
    Number that references the lot of the inventory item when the item is under lot control.
  • Value that uniquely identifies the completed transaction when the item is under lot control.
Nested Schema : inventoryCompletedTransactions-lots-lotSerials-item-response
Type: object
Show Source
Nested Schema : Flexfields for Serial Attributes
Type: array
Title: Flexfields for Serial Attributes
The Flexfields for Serial Attributes resource manages the descriptive flexfields that modifies serial attributes. Use this resource only when the item is under serial control.
Show Source
Nested Schema : Flexfields for Serials
Type: array
Title: Flexfields for Serials
The Flexfields for Serials resource manages the descriptive flexfields that modifies serials. Use this resource only when the item is under serial control.
Show Source
Nested Schema : inventoryCompletedTransactions-lots-lotSerials-serialAttributeDFFs-item-response
Type: object
Show Source
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name that references a serial attribute. This value is applicable when the item is under serial control.
  • Title: Context Value
    Descriptive flexfield context display value that references a serial attribute. This value is applicable when the item is under serial control.
  • Links
  • Title: Serial Number
    Maximum Length: 80
    Serial number of the inventory item that references the serial in a lot. This value is applicable when the item is under serial control.
  • Value that uniquely identifies the completed transaction. This value is applicable when the item is under serial control.
Nested Schema : inventoryCompletedTransactions-lots-lotSerials-serialStandardDFFs-item-response
Type: object
Show Source
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name that references the serial. This value is applicable when the item is under serial control.
  • Title: Context Value
    Descriptive flexfield context display value that references the serial. This value is applicable when the item is under serial control.
  • Links
  • Title: Serial Number
    Maximum Length: 80
    Serial number of the inventory item that references the serial in a lot. This value is applicable when the item is under serial control.
  • Value that uniquely identifies completed transaction. This value is applicable when the item is under serial control.
Nested Schema : inventoryCompletedTransactions-lots-lotStandardDFFs-item-response
Type: object
Show Source
  • Title: Context Value
    Maximum Length: 30
    Descriptive flexfield context name that references the lot. This value is applicable when the item is under lot control.
  • Title: Context Value
    Descriptive flexfield context display value that references the lot. This value is applicable when the item is under lot control.
  • Links
  • Title: Lot
    Maximum Length: 80
    Number that references the lot of the inventory item when the item is under lot control.
  • Value that uniquely identifies the completed transaction when the item is under lot control.
Links
lotAttributeDFFs
Parameters:
  • TransactionId: $request.path.TransactionId
  • lotsUniqID: $request.path.lotsUniqID
The Flexfields for Lot Attributes resource manages the descriptive flexfields that modifies lot attributes. Use this resource only when the item is under lot control.
lotSerials
Parameters:
  • TransactionId: $request.path.TransactionId
  • lotsUniqID: $request.path.lotsUniqID
The Serials in Lots in Completed Transactions resource gets serial details for inventory transactions when the item is under both lot and serial control. The details include serial number, and so on.
lotStandardDFFs
Parameters:
  • TransactionId: $request.path.TransactionId
  • lotsUniqID: $request.path.lotsUniqID
The Flexfields for Lots resource manages the descriptive flexfields that modifies lots. Use this resource only when the item is under lot control.
Back to Top

Examples

This example describes how to get one lot.

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/inventoryCompletedTransactions/TransactionId/child/lots/LotNumber"

For example, the following command gets one lot where the lot number is KKLO3:

curl -u username:password "https://servername/fscmRestApi/resources/version/inventoryCompletedTransactions/TransactionId/child/lots/KKLO3"

Example Response Body

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

{
    "LotNumber": "KKLO3",
    "ParentLot": null,
    "TransactionQuantity": 1,
    "Status": null,
    "StatusId": 1,
    "SupplierLotNumber": null,
    "GradeCode": null,
    "OriginationTypeCode": 3,
    "OriginationType": null,
    "OriginationDate": null,
    "RetestDate": null,
    "ExpirationActionCode": null,
    "ExpirationAction": null,
    "ExpirationActionDate": null,
    "HoldDate": null,
    "MaturityDate": null,
    "Reason": null,
    "ReasonId": null}
Back to Top