1. REST API for Oracle Fusion Cloud Procurement
  2. Tasks
  3. Procurement Approved Supplier List Entries

Update one approved supplier list entry

patch

/fscmRestApi/resources/11.13.18.05/procurementApprovedSupplierListEntries/{procurementApprovedSupplierListEntriesUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Procurement Approved Supplier List Entries resource and used to uniquely identify an instance of Procurement Approved Supplier List Entries. The client should not generate the hash key value. Instead, the client should query on the Procurement Approved Supplier List Entries collection resource in order to navigate to a specific instance of Procurement Approved Supplier List Entries to get the hash key.
Header Parameters
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • 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
  • Status identifier of the approved supplier list entry.
  • Maximum Length: 240
    Comments entered for the approved supplier list entry.
  • Title: Country of Origin
    Maximum Length: 80
    Country from which goods are exported.
  • Maximum Length: 2
    Code that indicates the country from which goods are exported.
  • DFF
  • Title: Disabled
    Maximum Length: 1
    Mark indicating that the approved supplier list entry is no longer in use.
  • Title: Fixed Lot Multiple
    Incremental quantity that must be used on purchase orders sourced from the approved supplier list entry.
  • Title: Minimum Order Quantity
    Identifies the minimum quantity that can be purchased from the supplier on purchase orders sourced from the approved supplier list entry.
  • Title: Supplier Item
    Maximum Length: 300
    Identifies the supplier item number.
  • Title: Purchasing UOM
    Maximum Length: 25
    Unit of measure used on purchase orders sourced from the approved supplier list entry.
  • Maximum Length: 3
    Code that indicates the unit of measure used on purchase orders sourced from the approved supplier list entry.
  • Date when the approved supplier list entry needs to be evaluated. This is generally used as a reminder for approving or recertifying the supplier for the specific item or category.
  • Title: Status
    Maximum Length: 25
    Approval status of the approved supplier list entry, representing whether the supplier is certified to supply the item or group of items.
Nested Schema : DFF
Type: array
Show Source
Nested Schema : procurementApprovedSupplierListEntries-DFF-item-patch-request
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 : procurementApprovedSupplierListEntries-item-response
Type: object
Show Source
  • Read Only: true
    Date on which the approved supplier list entry was created.
  • Unique identifier of the approved supplier list entry.
  • Read Only: true
    Code that identifies if the approved supplier list entry is used by a ship-to organization or by all ship-to organizations serviced by the procurement business unit.
  • Status identifier of the approved supplier list entry.
  • Maximum Length: 240
    Comments entered for the approved supplier list entry.
  • Title: Country of Origin
    Maximum Length: 80
    Country from which goods are exported.
  • Maximum Length: 2
    Code that indicates the country from which goods are exported.
  • DFF
  • Title: Disabled
    Maximum Length: 1
    Mark indicating that the approved supplier list entry is no longer in use.
  • Title: Fixed Lot Multiple
    Incremental quantity that must be used on purchase orders sourced from the approved supplier list entry.
  • Title: Item
    Maximum Length: 300
    Anything that a business makes, purchases, or sells, including components, subassemblies, finished products, or supplies.
  • Value that uniquely identifies the item on the approved supplier list entry.
  • Links
  • Title: Minimum Order Quantity
    Identifies the minimum quantity that can be purchased from the supplier on purchase orders sourced from the approved supplier list entry.
  • Title: Supplier Item
    Maximum Length: 300
    Identifies the supplier item number.
  • Title: Procurement BU
    Maximum Length: 240
    Business unit that manages and owns the purchasing document.
  • Value that uniquely identifies the business unit that manages and owns the approved supplier list entry.
  • Title: Purchasing UOM
    Maximum Length: 25
    Unit of measure used on purchase orders sourced from the approved supplier list entry.
  • Maximum Length: 3
    Code that indicates the unit of measure used on purchase orders sourced from the approved supplier list entry.
  • Date when the approved supplier list entry needs to be evaluated. This is generally used as a reminder for approving or recertifying the supplier for the specific item or category.
  • Title: Scope
    Read Only: true
    Maximum Length: 255
    Identifies if the approved supplier list entry is used by a ship-to organization or by all ship-to organizations serviced by the procurement business unit.
  • Title: Ship-to Organization
    Maximum Length: 240
    Name of the inventory organization to which the supplier should ship the goods.
  • Default Value: -1
    Value that uniquely identifies the inventory organization that receives the item.
  • Title: Status
    Maximum Length: 25
    Approval status of the approved supplier list entry, representing whether the supplier is certified to supply the item or group of items.
  • Title: Supplier
    Maximum Length: 360
    Organization or individual that provides goods or services to the buying organization for payment, bound by a contractual obligation.
  • Value that uniquely identifies the supplier who fulfills the order.
  • Title: Supplier Site
    Maximum Length: 240
    Entity that models how the buying organization conducts business with the supplier.
  • Value that uniquely identifies the location that the supplier uses to fulfill the order.
Nested Schema : DFF
Type: array
Show Source
Nested Schema : procurementApprovedSupplierListEntries-DFF-item-response
Type: object
Show Source
Links
DFF
Parameters:
  • procurementApprovedSupplierListEntriesUniqID: $request.path.procurementApprovedSupplierListEntriesUniqID
Back to Top

Examples

These examples describe how to update approved supplier list entries.

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/procurementApprovedSupplierListEntries/procurementApprovedSupplierListEntriesUniqID"

Example 1: Disable One Approved Supplier List Entry

This example describes how to disable one approved supplier list entry.

Example 1 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/procurementApprovedSupplierListEntries/801"

Example 1 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.
{
  "Status": "Approved",
  "PrimaryVendorItem": null,
  "ReviewDueDate": null,
  "DisableFlag": true,
  "Comments": null
}

Example 1 Response Body

The following example includes the contents of the response body in JSON format:
{
  "AslId": 2241,
  "ProcurementBUId": 204,
  "ProcurementBU": "Vision Operations",
  "AslScopeCode": "SHIP_TO_ORG",
  "Scope": "Ship-to Organization",
  "ShipToOrganizationId": 911,
  "ShipToOrganization": "Vision Germany",
  "Item": "f50010",
  "ItemId": 4774,
  "Supplier": "First Software",
  "SupplierId": 9,
  "SupplierSite": "DÜSSELDORF",
  "SupplierSiteId": 356,
  "PrimaryVendorItem": null,
  "Status": "Approved",
  "AslStatusId": 2,
  "ReviewDueDate": null,
  "DisableFlag": true,
  "Comments": null,
  "AslCreationDate": "2003-07-03T21:42:31-05:00"
}

Example 2: Update Multiple Approved Supplier List Entries

This example describes how to update multiple approved supplier list entries.

Example 2 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.
{
  "parts": [
    {
      "id": "part0",
      "path": "/procurementApprovedSupplierListEntries/300100561868624",
      "operation": "update",
      "payload": {
        "Status": "New",
        "PrimaryVendorItem": "Supplier Item 1",
        "ReviewDueDate": "2022-10-28",
        "DisableFlag": false,
        "Comments": "Comments 1",
        "PurchasingUOM": "Each",
        "CountryOfOrigin": null,
        "MinimumOrderQuantity": null,
        "FixedLotMultiple": 7
      }
    },
    {
      "id": "part1",
      "path": "/procurementApprovedSupplierListEntries/300100562870593",
      "operation": "update",
      "payload": {
        "Status": "New",
        "PrimaryVendorItem": "Supplier Item 2",
        "ReviewDueDate": "2022-10-29",
        "DisableFlag": false,
        "Comments": "Comments 2",
        "PurchasingUOM": null,
        "CountryOfOrigin": "United States",
        "MinimumOrderQuantity": null,
        "FixedLotMultiple": 7
      }
    }
  ]
}

Example 2 Response Body

The following example includes the contents of the response body in JSON format:
{
  "parts": [
    {
      "id": "part0",
      "path": "https://servername/fscmRestApi/resources/version/procurementApprovedSupplierListEntries/300100561868624",
      "operation": "update",
      "preconditionSucceeded": true,
      "payload": {
        "AslId": 300100561868624,
        "ProcurementBUId": 204,
        "ProcurementBU": "Vision Operations",
        "AslScopeCode": "SHIP_TO_ORG",
        "Scope": "Ship-to Organization",
        "ShipToOrganizationId": 204,
        "ShipToOrganization": "Vision Operations",
        "Item": "RCV-100",
        "ItemId": 663907,
        "Supplier": " Big Computers",
        "SupplierId": 12,
        "SupplierSite": null,
        "SupplierSiteId": null,
        "PrimaryVendorItem": "Supplier Item 1",
        "Status": "New",
        "AslStatusId": 1,
        "ReviewDueDate": "2022-10-28",
        "DisableFlag": false,
        "Comments": "Comments 1",
        "AslCreationDate": "2022-09-27T06:39:42.002-05:00",
        "PurchasingUOMCode": "EA",
        "PurchasingUOM": "Each",
        "CountryOfOriginCode": null,
        "CountryOfOrigin": null,
        "MinimumOrderQuantity": null,
        "FixedLotMultiple": 7
      }
    },
    {
      "id": "part1",
      "path": "https://servername/fscmRestApi/resources/version/procurementApprovedSupplierListEntries/300100562870593",
      "operation": "update",
      "preconditionSucceeded": true,
      "payload": {
        "AslId": 300100562870593,
        "ProcurementBUId": 204,
        "ProcurementBU": "Vision Operations",
        "AslScopeCode": "SHIP_TO_ORG",
        "Scope": "Ship-to Organization",
        "ShipToOrganizationId": 204,
        "ShipToOrganization": "Vision Operations",
        "Item": "RCV-100",
        "ItemId": 663907,
        "Supplier": " Big Computers",
        "SupplierId": 12,
        "SupplierSite": " Big Computers Austin",
        "SupplierSiteId": 2444,
        "PrimaryVendorItem": "Supplier Item 2",
        "Status": "New",
        "AslStatusId": 1,
        "ReviewDueDate": "2022-10-29",
        "DisableFlag": false,
        "Comments": "Comments 2",
        "AslCreationDate": "2022-10-16T23:13:18.002-05:00",
        "PurchasingUOMCode": null,
        "PurchasingUOM": null,
        "CountryOfOriginCode": "US",
        "CountryOfOrigin": "United States",
        "MinimumOrderQuantity": null,
        "FixedLotMultiple": 7
      }
    }
  ]
}
Back to Top