Update one subinventory relationship

patch

/fscmRestApi/resources/11.13.18.05/vmiRelationships/{vmiRelationshipsUniqID}/child/vmiSubinventories/{vmiSubinventoriesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Vendor-Managed Inventory Relationships resource and used to uniquely identify an instance of Vendor-Managed Inventory Relationships. The client should not generate the hash key value. Instead, the client should query on the Vendor-Managed Inventory Relationships collection resource in order to navigate to a specific instance of Vendor-Managed Inventory Relationships to get the hash key.
  • This is the hash key of the attributes which make up the composite key for the Subinventory Relationships resource and used to uniquely identify an instance of Subinventory Relationships. The client should not generate the hash key value. Instead, the client should query on the Subinventory Relationships collection resource in order to navigate to a specific instance of Subinventory Relationships 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.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Min-Max Quantity Source
    Maximum Length: 255
    Value that indicates the source of the minimum and maximum quantities used to manage vendor-managed inventory replenishments. Valid values include Enterprise and Supplier.
  • Title: Min-Max Quantity Source
    Maximum Length: 255
    Value that uniquely identifies the source of the minimum and maximum quantities used to manage vendor-managed inventory replenishments. Valid values include ORA_VCS_MIN_MAX_ORIGIN_ENT and ORA_VCS_MIN_MAX_ORIGIN_SUP.
  • Title: Requisition Requester
    Value that uniquely identifies the requisition requester for the relationship.
  • Title: Requisition Requester
    Maximum Length: 255
    Login that the user used when requesting the requisition for the relationship.
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 : vmiRelationships-vmiSubinventories-item-response
Type: object
Show Source
  • Read Only: true
    Maximum Length: 64
    User who created the vendor-managed inventory relationship.
  • Read Only: true
    Date and time when the user created the vendor-managed inventory relationship.
  • Title: Inventory Planning Owner
    Read Only: true
    Maximum Length: 255
    Value that identifies the inventory planning owner of the vendor-managed inventory replenishments for the relationship. Valid values include Supplier, Enterprise, or Unresolved planning owner.
  • Title: Inventory Planning Owner
    Read Only: true
    Maximum Length: 255
    Abbreviation that identifies the inventory planning owner of the vendor-managed inventory replenishments for the relationship. Valid values include ORA_VCS_INV_OWNER_SUP, ORA_VCS_INV_OWNER_ENT, ORA_VCS_INV_OWNER_NOT_SUPPORT, or ORA_VCS_INV_OWNER_INVALID.
  • Read Only: true
    Date and time when the user most recently updated the vendor-managed inventory relationship.
  • Read Only: true
    Maximum Length: 64
    Login of the user who most recently updated the vendor-managed inventory relationship.
  • Links
  • Title: Min-Max Quantity Source
    Maximum Length: 255
    Value that indicates the source of the minimum and maximum quantities used to manage vendor-managed inventory replenishments. Valid values include Enterprise and Supplier.
  • Title: Min-Max Quantity Source
    Maximum Length: 255
    Value that uniquely identifies the source of the minimum and maximum quantities used to manage vendor-managed inventory replenishments. Valid values include ORA_VCS_MIN_MAX_ORIGIN_ENT and ORA_VCS_MIN_MAX_ORIGIN_SUP.
  • Value that uniquely identifies the relationship.
  • Title: Relationship
    Read Only: true
    Maximum Length: 9
    Number that identifies the relationship.
  • Title: Requisition Requester
    Value that uniquely identifies the requisition requester for the relationship.
  • Title: Requisition Requester
    Maximum Length: 255
    Login that the user used when requesting the requisition for the relationship.
  • Title: Subinventory
    Maximum Length: 10
    Value that uniquely identifies the subinventory of an organization in the relationship. This subinventory is the final destination for the item in the replenishment request.
  • Title: Description
    Read Only: true
    Maximum Length: 50
    Description of the subinventory.
  • Title: Subinventory
    Read Only: true
    Value that uniquely identifies the subinventory.
  • Value that uniquely identifies the subinventory relationship.
Back to Top

Examples

This example describes how to update one subinventory relationship.

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/vmiRelationships/vmiRelationshipsUniqID/child/vmiSubinventories/vmiSubinventoriesUniqID"

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 updates.

{
"MinMaxQuantitySourceCode": "ORA_VCS_MIN_MAX_ORIGIN_ENT"
}

Example Response Body

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

{
    "RelationshipId": 300100176385880,
    "RelationshipNumber": "45002",
    "SubinventoryRelationshipId": 300100176385881,
    "SubinventoryId": 300100152283616,
    "Subinventory": "VMIMFG3-01",
    "SubinventoryDescription": "VMIMFG3 Subinventory 1",
    "InventoryPlanningOwner": "Supplier",
    "InventoryPlanningOwnerCode": "ORA_VCS_INV_OWNER_SUP",
    "MinMaxQuantitySource": "Enterprise",
    "MinMaxQuantitySourceCode": "ORA_VCS_MIN_MAX_ORIGIN_ENT",
    "RequisitionRequesterPersonId": 300100073936640,
    "RequisitionRequesterUserName": "VMI_OPERATIONS",
    "CreatedBy": "SCC_OPERATIONS",
    "CreationDate": "2018-10-24T19:48:49.551+00:00",
    "LastUpdatedBy": "SCC_OPERATIONS",
    "LastUpdateDate": "2018-10-24T20:23:44.011+00:00",
    "links": [
        {
            ...
        },
        {
            ...
        },
        {
            ...
        }
    ]
}
Back to Top