Create one lot serial

post

/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub/{OrderKey}/child/lines/{linesUniqID}/child/lotSerials

Request

Path Parameters
  • Value that uniquely identifies the sales order. It can have the following formats.

    - Concatenation of SourceOrderSystem, a colon, and the value of SourceTransactionId. For orders created through the Oracle Fusion Cloud Order Management work area, the SourceTransactionId is same as the HeaderId. For example, if SourceOrderSystem is LEG and SourceTransactionId is R13_Sample_Order, the value of this attribute is LEG:R13_Sample_Order. This format of the OrderKey in the URL always returns the latest version of the sales order. When a draft exists, that becomes the latest version of the sales order. When invoking GET sales order using this OrderKey format, the URLs in the "links" section point to the latest version of the sales order and the corresponding child objects.
    Example: /salesOrdersForOrderHub/LEG:R13_Sample_Order points to the latest version of the order with SourceTransactionId "R13_Sample_Order" in the SourceOrderSystem "LEG".

    - Primary key of the sales order, which is HeaderId. This format of the OrderKey is useful when the order has multiple revisions because it helps in accessing either the older version or the latest version of the order. When there's a draft revision then HeaderId can be used to access the processing order. When invoking GET sales order using this OrderKey format, the URLs in the "links" section also point to that specific version of the sales order and the corresponding child objects. Only the Get operation is supported on older revisions of the order.
    Example: /salesOrdersForOrderHub/12345 points to an order with HeaderId 12345.

    When a q parameter or query finder is used to GET an order that has multiple versions then the latest version has the OrderKey in the format <sourceOrderSystem>:<SourceTransactionId> whereas reference orders have OrderKey in the format of HeaderId.
  • This is the hash key of the attributes which make up the composite key for the Order Lines resource and used to uniquely identify an instance of Order Lines. The client should not generate the hash key value. Instead, the client should query on the Order Lines collection resource in order to navigate to a specific instance of Order Lines to get the hash key.
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.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Contains one of the following values: true or false. If true, then lot and serial lines are deleted during the patch or upsert operation. If false, then lot and serial lines are not deleted. This is a transient attribute. Use this attribute only on an order line that includes an inventory transaction. This attribute does not have a default value.
  • Title: Revision Number
    Maximum Length: 120
    Value that identifies the item revision.
  • Title: From Serial Number
    Maximum Length: 120
    Starting serial number of a range of serial numbers.
  • Title: To Serial Number
    Maximum Length: 120
    Ending serial number of a range of serial numbers.
  • Concatenated segments for the locator flexfields from where the item is shipped from or received into.
  • Locator where the application ships or receives the item.
  • Title: Lot Number
    Maximum Length: 320
    Identifies the quantity for the item.
  • Quantity of lots and serials.
  • Maximum Length: 50
    Value that uniquely identifies the lot and serial. The source application assigns this value.
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 : salesOrdersForOrderHub-lines-lotSerials-item-response
Type: object
Show Source
  • Contains one of the following values: true or false. If true, then lot and serial lines are deleted during the patch or upsert operation. If false, then lot and serial lines are not deleted. This is a transient attribute. Use this attribute only on an order line that includes an inventory transaction. This attribute does not have a default value.
  • Title: Revision Number
    Maximum Length: 120
    Value that identifies the item revision.
  • Title: From Serial Number
    Maximum Length: 120
    Starting serial number of a range of serial numbers.
  • Title: To Serial Number
    Maximum Length: 120
    Ending serial number of a range of serial numbers.
  • Links
  • Concatenated segments for the locator flexfields from where the item is shipped from or received into.
  • Locator where the application ships or receives the item.
  • Title: Lot Number
    Maximum Length: 320
    Identifies the quantity for the item.
  • Read Only: true
    Value that uniquely identifies the lot and serial.
  • Quantity of lots and serials.
  • Read Only: true
    Quantity of the lot for the item or service in the secondary unit of measure. This attribute is applicable when more than one unit of measure is used to measure and track the item.
  • Maximum Length: 50
    Value that uniquely identifies the lot and serial. The source application assigns this value.
Back to Top

Examples

This example describes how to add a lot serial.

Example cURL Command

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

curl -X PATCH -u "username:password" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -d 'request payload'  "https://servername/fscmRestApi/resources/version/salesOrdersForOrderHub/OrderKey/child/lines/linesUniqID/child/lotSerials"

For example, use the following command:

curl -X PATCH -u "username:password" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/salesOrdersForOrderHub/GPR%3AR13_unref_return_lotserial_01/child/lines/{linesUniqID}/child/lotSerials"

Example Request Body

The following example includes the contents of the request body in JSON format to add a new lot serial to an order line in the existing order.

You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it updates.

You can achieve the same result with Create sales orders using the upsert-mode header parameter. Refer to the examples in the Create sales orders section to see how to update child resource in the existing order.

{
               "SourceLotSerialId":"1",
               "ItemRevisionNumber":"1",
               "ItemSerialNumberFrom":"FROM1",
               "ItemSerialNumberTo":"TO1",
               "LocatorId":11,
               "LotNumber":"LOT1"
}

Example Response Body

The following example includes the contents of the response body in JSON format:

{
}
Back to Top