1. REST API for Oracle Supply Chain Management Cloud
  2. Tasks
  3. Supply Chain Planning
  4. Collaboration Supplier On-Hand Quantities

Create quantities

post

/fscmRestApi/resources/11.13.18.05/collaborationSupplierOnHandQuantities

Request

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
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 : collaborationSupplierOnHandQuantities-item-response
Type: object
Show Source
  • Title: Item Primary UOM Quantity
    Read Only: true
    Quantity of the on-hand inventory for the item in the base unit of measure.
  • Read Only: true
    Maximum Length: 255
    Base unit of measure for the item.
  • Title: Item Primary UOM
    Read Only: true
    Maximum Length: 3
    Abbreviation that identifies the base unit of measure for the item.
  • Read Only: true
    Value that uniquely identifies the collaboration item for the supplier on-hand quantity.
  • Read Only: true
    Maximum Length: 64
    User who created the on-hand quantity.
  • Read Only: true
    Date and time when the user created the on-hand quantity.
  • Read Only: true
    Value that uniquely identifies the inventory item for the supplier on-hand quantity.
  • Title: Item
    Number that identifies the item.
  • Read Only: true
    Date and time when the user most recently updated the on-hand quantity.
  • Read Only: true
    Maximum Length: 32
    Login of the user who most recently updated the on-hand quantity.
  • Links
  • Read Only: true
    Value that uniquely identifies the planning item for the supplier on-hand quantity.
  • Title: Business Unit ID
    Read Only: true
    Value that uniquely identifies the business unit.
  • Title: Procurement BU
    Name of the business unit. The application assigns the supplier to this business unit.
  • Title: Published By
    Read Only: true
    Maximum Length: 255
    User who most recently published the on-hand quantity.
  • Title: Published Date
    Read Only: true
    Date when the on-hand quantity was published.
  • Title: Publish Source
    Read Only: true
    Maximum Length: 80
    Value that indicates the type of user who performed the publish action. Values include Enterprise or Supplier.
  • Read Only: true
    Maximum Length: 64
    Default Value: ORA_VCS_ENTERPRISE_VAL
    Abbreviation that identifies the type of user who performed the publish action. A list of accepted values is defined in the lookup type ORA_VCS_PARTY_ORIGIN. Review and update the values for this attribute using the Setup and Maintenance work area, and the Manage Supply Chain Collaboration Lookups task.
  • Title: Quantity
    Quantity of the on-hand inventory for the item.
  • Read Only: true
    Value that uniquely identifies the supplier in the collaboration order forecast. This supplier sends the shipment. It's a primary key that the application generates when it creates the supplier.
  • Title: Supplier Item
    Number that identifies the item referred to by the supplier.
  • Title: Supplier
    Maximum Length: 255
    Name of the supplier that holds the on-hand inventory for the item.
  • Read Only: true
    Value that uniquely identifies the supplier on-hand quantity.
  • Read Only: true
    Value that uniquely identifies the supplier site. This supplier site holds the on-hand inventory for the item. It's a primary key that the application generates when it creates the supplier site.
  • Title: Supplier Site
    Name of the supplier site that holds the on-hand inventory for the item.
  • Title: UOM
    Unit of measure for the item.
  • Abbreviation that identifies the unit of measure for the item.
Back to Top

Examples

This example describes how to create quantities.

Example cURL Command

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

curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' 
"https://servername/fscmRestApi/resources/version/collaborationSupplierOnHandQuantities"

Example Request Body

The following example includes the contents of the request body in JSON format. 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 creates. 

{
	"SupplierName": "CV_SuppD01",
	"SupplierSiteName": "CV_SuppD01Site1",
	"ItemNumber": "SCC-CNTRDL-01",
	"Quantity": 150,
	"UOMCode": "Ea"
}

Example Response Body

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

{
}
Back to Top