Get a sales team member

get

/crmRestApi/resources/11.13.18.05/households/{PartyNumber}/child/SalesTeamMember/{TeamMemberId}

Request

Path Parameters
  • The unique primary identifier for the household party. The profile option HZ_GENERATE_PARTY_NUMBER controls whether the attribute value can be system generated or user-provided during create. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Common Profile Options task. Inactive records can't be updated.
  • The unique identifier of the member of the sales accounts resource team.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
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.

There's no request body for this operation.

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 : households-SalesTeamMember-item-response
Type: object
Show Source
  • Title: Access
    Maximum Length: 30
    The code indicating the level of access granted to the resource as well as managers of the organizations. The possible values are defined in the ZCA_ACCESS_LEVEL lookup. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Standard Lookups task.
  • Title: Assignment Type
    Maximum Length: 30
    Default Value: MANUAL
    The code indicating how the resource is assigned to the sales account team. The possible values are contained in the ZCA_ASSIGNMENT_TYPE lookup.
  • Title: Corporate Currency Code
    Maximum Length: 15
    The corporate currency code associated with the sales team member. 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 record.
  • Title: Creation Date
    Read Only: true
    The date and time when the record was created.
  • Title: Currency Conversion Rate Type
    Maximum Length: 30
    The currency conversion rate type associated with the address. A list of valid values is defined in the lookup ZCA_COMMON_RATE_TYPE. Review and update the profile option using the Setup and Maintenance work area, Manage Currency Profile Options task.
  • Title: Currency Code
    Maximum Length: 15
    The currency code associated with the sales team member of the household object. 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: Archived Date
    The date when the resource is dissociated from the sales account.
  • Title: Last Updated Date
    Read Only: true
    The date and time when the record 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 details of the user who last updated the record.
  • Links
  • Title: Locked
    Maximum Length: 1
    Default Value: false
    Indicates if the automatic territory assignment can be set. If the value is True, then the automatic territory assignment cannot remove the sales account team resource. When a sales account team member is added manually, this flag is defaulted to `Y'.
  • Title: Function
    Maximum Length: 30
    The code indicating the role of a sales team member in the resource team such as Integrator, Executive Sponsor, and Technical Account Manager. A list of accepted values is defined in the lookup FND_LOOKUPS. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Common Lookups task.
  • The number used to implement optimistic locking. This number is incremented every time the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried.
  • Title: Owner
    Default Value: false
    Indicates whether the resource is the owner.
  • The unique identifier of the associated party record for sales team member record.
  • The public identifier of the associated party record.
  • The name of external source system of the associated party record.
  • The unique identifier from external source system of the associated party record.
  • Title: Resource Email
    The email address of the resource.
  • Title: Resource ID
    The unique identifier of the household resource.
  • Title: Resource Name
    Read Only: true
    The name of the sales team member.
  • Read Only: true
    The name of the organization that the sales team member belongs to.
  • Title: Resource Party Number
    The alternate key identifier of the resource that this team member belongs to.
  • Title: Phone
    Read Only: true
    The primary phone number of the sales team member.
  • Title: Role
    Read Only: true
    The names of the roles assigned to the sales team member.
  • Title: Sales Account ID
    The unique identifier for the sales account.
  • Title: Start Date
    The date on which the resource is associated with a sales account.
  • Title: Sales Account Resource ID
    The unique identifier of the member of the sales accounts resource team.
  • Title: User Last Update Date
    The date and time when the record was last updated. This value is different from LAST_UPDATE_DATE if the update originally happened in a different database.
Back to Top

Examples

cURL Command

The following example shows how to get a sales team member by submitting a get request on the REST resource using cURL.

curl -u <username:password> \ -X GET https://servername.fa.us2.oraclecloud.com/crmRestApi/resources/11.13.18.05/households/CDRM_61285/child/SalesTeamMember/100100019286509

Example of Response Body

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

{
    "TeamMemberId": 100100019286509,
    "SalesProfileId": 100100018128609,
    "ResourceId": 100010025532138,
    "AccessLevelCode": "300",
    "LockAssignmentFlag": true,
    "AssignmentTypeCode": "MANUAL",
    "CreationDate": "2014-04-07T02:08:43-07:00",
    "CreatedBy": "DATA_STEWARD_MGR",
    "LastUpdateDate": "2014-04-07T02:08:43-07:00",
    "LastUpdatedBy": "DATA_STEWARD_MGR",
    "StartDateActive": "2014-04-07",
    "ResourcePartyNumber": "100010025532138",
    "ResourceEmailAddress": Tenng.lean@oracle.com
    ...
}
Back to Top