1. REST API for Oracle Fusion Cloud Procurement
  2. Tasks
  3. Supplier Negotiations
  4. Collaboration Team Members

Create one team member

post

/fscmRestApi/resources/11.13.18.05/supplierNegotiations/{supplierNegotiationsUniqID}/child/collaborationTeamMembers

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key for the Supplier Negotiations resource and used to uniquely identify an instance of Supplier Negotiations. The client should not generate the hash key value. Instead, the client should query on the Supplier Negotiations collection resource in order to navigate to a specific instance of Supplier Negotiations 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
  • Title: Access
    Maximum Length: 80
    Access for each collaboration team member. Values include Full or View Only. A list of accepted values is defined in the lookup type PON_NEG_COLLAB_TEAM_ACCESS.
  • Title: Access Code
    Maximum Length: 30
    Abbreviation that identifies the access for each collaboration team member. Values include FULL or VIEW_ONLY. A list of accepted values is defined in the lookup type PON_NEG_COLLAB_TEAM_ACCESS.
  • Value that uniquely identifies the collaboration team that the application added to the negotiation.
  • Title: Price Visibility
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then the team member can view price details on the response document when evaluating each response. If false, then cannot view. The default value is true.
  • Title: Supplier Messages
    Maximum Length: 80
    Access to message suppliers for each collaboration team member. Values include No access, Receive only, or Send and receive. A list of accepted values is defined in the lookup type ORA_PON_COLLAB_TEAM_SUPP_MSG.
  • Title: Supplier Messages Code
    Maximum Length: 30
    Abbreviation that identifies the access to message suppliers for each collaboration team member. Values include ORA_NO_ACCESS, ORA_RECEIVE_ONLY, or ORA_SEND_AND_RECEIVE. A list of accepted values is defined in the lookup type ORA_PON_COLLAB_TEAM_SUPP_MSG.
  • Title: Task
    Maximum Length: 4000
    Name of the task that the application assigned to the collaboration team member.
  • Title: Target Date
    Date when the application expects the collaboration team member to finishes the assigned task.
  • Title: Team Member
    Maximum Length: 240
    Name of the collaboration team member that the application added to the negotiation.
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 : supplierNegotiations-collaborationTeamMembers-item-response
Type: object
Show Source
  • Title: Access
    Maximum Length: 80
    Access for each collaboration team member. Values include Full or View Only. A list of accepted values is defined in the lookup type PON_NEG_COLLAB_TEAM_ACCESS.
  • Title: Access Code
    Maximum Length: 30
    Abbreviation that identifies the access for each collaboration team member. Values include FULL or VIEW_ONLY. A list of accepted values is defined in the lookup type PON_NEG_COLLAB_TEAM_ACCESS.
  • Read Only: true
    Maximum Length: 64
    User who created the team member.
  • Read Only: true
    Date and time when the user created the team member.
  • Title: Last Notified Date
    Read Only: true
    Date and time when the application most recently notified the collaboration team member about the collaboration team task.
  • Read Only: true
    Date and time when the user most recently updated the team member.
  • Read Only: true
    Maximum Length: 64
    User who most recently updated the team member.
  • Links
  • Value that uniquely identifies the collaboration team that the application added to the negotiation.
  • Title: Price Visibility
    Maximum Length: 1
    Contains one of the following values: true or false. If true, then the team member can view price details on the response document when evaluating each response. If false, then cannot view. The default value is true.
  • Read Only: true
    Name of the scoring team that a collaboration team member is assigned to.
  • Title: Supplier Messages
    Maximum Length: 80
    Access to message suppliers for each collaboration team member. Values include No access, Receive only, or Send and receive. A list of accepted values is defined in the lookup type ORA_PON_COLLAB_TEAM_SUPP_MSG.
  • Title: Supplier Messages Code
    Maximum Length: 30
    Abbreviation that identifies the access to message suppliers for each collaboration team member. Values include ORA_NO_ACCESS, ORA_RECEIVE_ONLY, or ORA_SEND_AND_RECEIVE. A list of accepted values is defined in the lookup type ORA_PON_COLLAB_TEAM_SUPP_MSG.
  • Read Only: true
    Date when the collaboration team member finishes the assigned task.
  • Title: Task
    Maximum Length: 4000
    Name of the task that the application assigned to the collaboration team member.
  • Title: Target Date
    Date when the application expects the collaboration team member to finishes the assigned task.
  • Title: Team Member
    Maximum Length: 240
    Name of the collaboration team member that the application added to the negotiation.
  • Read Only: true
    Value that uniquely identifies each team member.
Back to Top

Examples

This example describes how to create a collaboration team member.

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/supplierNegotiations/supplierNegotiationsUniqID/child/collaborationTeamMembers"

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. 

{
    "AccessCode": "FULL",
    "PriceVisibilityFlag": true,
    "Access": "Full",
    "TeamMember": "Smith,Cody",
    "TaskName": "Review legal compliance documents",
    "TaskTargetDate": "2019-12-27"
}

Example Response Body

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

{
    "TeamMemberId": 300100179439851,
    "AccessCode": "FULL",
    "PriceVisibilityFlag": true,
    "SupplierMessagesCode": "ORA_SEND_AND_RECEIVE",
    "SupplierMessages": "Send and receive",
    "TaskTargetDate": "2019-12-27",
    "TaskName": "Review legal compliance documents",
    "LastNotifiedDate": null,
    "Access": "Full",
    "TeamMember": "Smith,Cody",
    "PersonId": 100010026863791,
    "TaskCompletionDate": null,
    "CreatedBy": "CVBUYER01",
    "CreationDate": "2019-05-22T22:33:58+00:00",
    "LastUpdateDate": "2019-05-22T22:33:58.235+00:00",
    "LastUpdatedBy": "CVBUYER01",
    "links": [<Do not change anything here>]
}
Back to Top