Create a note

post

/crmRestApi/resources/11.13.18.05/opportunities/{OptyNumber}/child/Note

Request

Path Parameters
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: Contact Relationship ID
    The unique identifier of the relationship that is populated when the note is associated with a contact.
  • Title: Corporate Currency Code
    Maximum Length: 15
    The corporate currency code of the note associated with the contact. A list of accepted values is defined in the lookup ZCA_COMMON_CORPORATE_CURRENCY. Review and update the profile option using the Setup and Maintenance work area, Manage Trading Community Common Lookups task.
  • Title: Creator Party ID
    The unique party identifier for the note creator.
  • Title: Currency Conversion Rate Type
    Maximum Length: 30
    The currency conversion rate type associated with the note. A list of accepted values is defined in the lookup ZCA_COMMON_RATE_TYPE. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Common Lookups task.
  • Title: Currency
    Maximum Length: 15
    The currency code associated with the note. A list of accepted values is defined in the lookup ZCA_COMMON_CORPORATE_CURRENCY. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Common Lookups task.
  • Maximum Length: 30
    The system generated number. It can be generated from external system also (user key).
  • Title: Title
    Maximum Length: 500
    The user provided title for the note.
  • Title: Note
    The column which stores the actual note text.
  • Title: Type
    Maximum Length: 30
    The code used to classify a note, as asset or adjustment.
  • Title: Parent Note ID
    The identifier for the parent note.
  • Title: Related Object Type
    Maximum Length: 30
    The code indicating the type of the source object as defined in OBJECTS Metadata, such as Activities, Opportunities, and so on.
  • Title: Related Object
    Maximum Length: 64
    The unique identifier of the source object as defined in OBJECTS Metadata, such as activities, opportunities, and so on.
  • Title: Private
    Maximum Length: 30
    Default Value: INTERNAL
    The code indicating the visibility level of the note, such as internal or external.
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 : opportunities-Note-item-response
Type: object
Show Source
  • Title: Contact Relationship ID
    The unique identifier of the relationship that is populated when the note is associated with a contact.
  • Title: Corporate Currency Code
    Maximum Length: 15
    The corporate currency code of the note associated with the contact. A list of accepted values is defined in the lookup ZCA_COMMON_CORPORATE_CURRENCY. Review and update the profile option using the Setup and Maintenance work area, Manage Trading Community Common Lookups task.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the note record.
  • Title: Creation Date
    Read Only: true
    The date and time when the note record was created.
  • Title: Creator Party ID
    The unique party identifier for the note creator.
  • Title: Currency Conversion Rate Type
    Maximum Length: 30
    The currency conversion rate type associated with the note. A list of accepted values is defined in the lookup ZCA_COMMON_RATE_TYPE. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Common Lookups task.
  • Title: Currency
    Maximum Length: 15
    The currency code associated with the note. A list of accepted values is defined in the lookup ZCA_COMMON_CORPORATE_CURRENCY. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Common Lookups task.
  • Title: Delete Indicator
    Read Only: true
    Indicates whether the note is to be deleted. If the value is Y, then the note has to be deleted. The default value is N.
  • Title: Primary Email
    Read Only: true
    Maximum Length: 320
    The email address of the user who created the note.
  • Title: Primary Address
    Read Only: true
    The formatted address of the user who created the note.
  • Title: Primary Phone
    Read Only: true
    The formatted phone number of the user who created the note.
  • Title: Last Update Date
    Read Only: true
    The date when the note data was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the record.
  • Title: Last Update Login
    Read Only: true
    Maximum Length: 32
    The login of the user who last updated the record.
  • Links
  • Title: Note ID
    Read Only: true
    The unique identifier of a note for the opportunity.
  • Maximum Length: 30
    The system generated number. It can be generated from external system also (user key).
  • Title: Title
    Maximum Length: 500
    The user provided title for the note.
  • Title: Note
    The column which stores the actual note text.
  • Title: Type
    Maximum Length: 30
    The code used to classify a note, as asset or adjustment.
  • Title: Parent Note ID
    The identifier for the parent note.
  • Title: Party ID
    Read Only: true
    The unique Identifier of the party to which the note is associated.
  • Title: Author
    Read Only: true
    Maximum Length: 360
    The name of party associated with the opportunity.
  • Title: Related Object Type
    Maximum Length: 30
    The code indicating the type of the source object as defined in OBJECTS Metadata, such as Activities, Opportunities, and so on.
  • Title: Related Object
    Maximum Length: 64
    The unique identifier of the source object as defined in OBJECTS Metadata, such as activities, opportunities, and so on.
  • Title: Update Indicator
    Read Only: true
    Indicates whether the note can be updated. If the value is Y, then the note can be updated. The default value is N.
  • Title: Private
    Maximum Length: 30
    Default Value: INTERNAL
    The code indicating the visibility level of the note, such as internal or external.
Back to Top

Examples

The following example shows how to create an opportunity by submitting a post request on the REST resource using cURL. For more information about cURL, see Use cURL.

cURL Command

curl -u <username:password> \ -X POST -d @example_request_payload.json https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/opportunities/

Note:

You can create an opportunity with an asset through the POST method. When you create an opportunity with an asset using REST API, the account details are populated from the account related to the asset.

Example of Request Body

The following shows an example of the request body in JSON format.

Content-Type: {
"Name" : "Major Application Upgrade"
}

Example of Response Body

The following shows an example of the response body in JSON format.

Content-Type: {
BudgetAvailableDate: null
BudgetedFlag: false
PrimaryOrganizationId: 204
ChampionFlag: false
CreatedBy: "SALES_ADMIN"
CreationDate: "2015-06-04T03:08:27-07:00"
CurrencyCode: "USD"
SalesMethodId: 100000012430001
SalesStageId: 100000012430007
Name: "Major Application Upgrade"
OptyId: 300100111705686
OptyNumber: "CDRM_332708"
OwnerResourcePartyId: 3807
StatusCode: "OPEN"
PrimaryRevenueId: 300100111705687
SalesMethod: "Standard Sales Process"
SalesStage: "01 - Qualification"
DescriptionText: "Looking for the Right Contacts, Characteristics, Determining the Need, Budget and Sponsor"
AverageDaysAtStage: 30
MaximumDaysInStage: 800
PhaseCd: "QUALIFICATION-DISCOVERY"
QuotaFactor: 3
RcmndWinProb: 0
StageStatusCd: "OPEN"
StgOrder: 1
EffectiveDate: "2015-06-24"
Revenue: 0
WinProb: 0
PartyName1: "Charles Taylor"
DownsideAmount: 0
UpsideAmount: 0
EmailAddress: "firstname_lastname@orcl.com"
ExpectAmount: 0
ForecastOverrideCode: "CRITERIA"
SalesChannelCd: "ZPM_DIRECT_CHANNEL_TYPES"
...
}

Example - Example- Create Multiple Revenue Lines For an Existing Opportunity

The following example shows how to create multiple revenue lines for an existing opportunity.

Example of Request Body

The following shoes an example of the request body in JSON format.

{
  "parts": [
  {
  "id": "part1",
  "path": "opportunities/CDRM_107474/child/ChildRevenue",
  "operation": "create",
  "payload": {
   "ProdGroupId": 999997826071065,
"UnitPrice": 600,
"Quantity": 2
  }
  },
  {
  "id": "part2",
  "path": "opportunities/CDRM_107474/child/ChildRevenue ",
  "operation": "create",
  "payload": {
 "ProdGroupId": 999997826071065,
"UnitPrice": 700,
"Quantity": 3
  }
  }
  ]
}

In the above sample payload, CDRM_107474 is the opty number.

Example of Response Body

The following shows an example of the response body in JSON format.

{
"parts": [
{
"id": "part1",
  "path": "opportunities/CDRM_107474/child/ChildRevenue",
  "operation": "create",
"payload" : {
{
RevnId: 300100111705696
BUOrgId: 204
CommitFlag: false
CostAmount: 0
ResourcePartyId: 100010025532672
DownsideAmount: 0
ExpectAmount: 0
MarginAmount: 0
OptyId: 300100111705686
RevnAmount: 400
RevnAmountCurcyCode: "USD"
UpsideAmount: 0
WinProb: 0
PrimaryFlag: false
...
}
},
},
{
"id": "part2",
"path": "opportunities/CDRM_107474/child/ChildRevenue",
"operation": "create",
"payload" : {
RevnId: 300100111705697
BUOrgId: 204
CommitFlag: false
CostAmount: 0
ResourcePartyId: 100010025532672
DownsideAmount: 0
ExpectAmount: 0
MarginAmount: 0
OptyId: 300100111705686
RevnAmount: 400
RevnAmountCurcyCode: "USD"
UpsideAmount: 0
WinProb: 0
PrimaryFlag: false
...
}
}

...
}
}
]
}

Create an Opportunity With Multiple Revenue Lines

The following example shows how to create a new opportunity with multiple revenue lines.

Example of Request Body

The following shows an example of the request body in JSON format.

Request
{
 "Name": "Pinnacle Server Opportunities",
  "ChildRevenue":
[
  {
 "ProdGroupId": 999997826071065,
"UnitPrice": 100,
"Quantity": 1
},
{
"ProdGroupId": 999997826071065,
 "UnitPrice": 100,
 "Quantity": 1
}
]
}

Example of Response Body

The following shows an example of the response body in JSON format.

{
BudgetAvailableDate: null
BudgetedFlag: false
PrimaryOrganizationId: 204
ChampionFlag: false
CreatedBy: "SALES_ADMIN"
CreationDate: "2015-06-04T03:08:27-07:00"
CurrencyCode: "USD"
SalesMethodId: 100000012430001
SalesStageId: 100000012430007
Name: "Pinnacle Server Opportunities"
OptyId: 300100111705686
OptyNumber: "CDRM_332708"
OwnerResourcePartyId: 3807
StatusCode: "OPEN"
PrimaryRevenueId: 300100111705687
SalesMethod: "Standard Sales Process"
SalesStage: "01 - Qualification"
...
"ChildRevenue": [
    {
      "RevnId": 300100182390421,
      "TargetPartyId": null,
      "CustomerAccountId": null,
      "BUOrgId": 204,
      "Comments": null,
      "CommitFlag": false,
      "OptyEffectiveDate": "2019-12-25",
      "CostAmount": 0,
      "ResourcePartyId": 100010025532672,
      "DownsideAmount": 0,
      "ExpectAmount": 0,
      "MarginAmount": 0,
      "OptyId": 300100182390419,
      "UnitPrice": 100,
      "InventoryItemId": null,
      "InventoryOrgId": null,
      "Quantity": 1,
      "Discount": null,
      "RevnAmount": 100,
      "RevnAmountCurcyCode": "USD",
      "TypeCode": null,
      "UpsideAmount": 100,
      "WinProb": 0,
      "UOMCode": null,
      
     ...
    },
    {
      "RevnId": 300100182390422,
      "TargetPartyId": null,
      "CustomerAccountId": null,
      "BUOrgId": 204,
      "Comments": null,
      "CommitFlag": false,
      "OptyEffectiveDate": "2019-12-25",
      "CostAmount": 0,
      "ResourcePartyId": 100010025532672,
      "DownsideAmount": 0,
      "ExpectAmount": 0,
      "MarginAmount": 0,
      "OptyId": 300100182390419,
      "UnitPrice": 100,
      "InventoryItemId": null,
      "InventoryOrgId": null,
      "Quantity": 1,
      "Discount": null,
      "RevnAmount": 100,
      "RevnAmountCurcyCode": "USD",
      "TypeCode": null,
      "UpsideAmount": 100,
      "WinProb": 0,
      "UOMCode": null,
      
      ...
    }
  ]
}
Back to Top