Get a relationship

get

/crmRestApi/resources/11.13.18.05/contacts/{PartyNumber}/child/Relationship/{RelationshipRecId}

Request

Path Parameters
  • The alternate key identifier for the contact 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 relationship record.
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 : contacts-Relationship-item-response
Type: object
Show Source
  • Title: Backward Role
    Read Only: true
    The backward relationship code used to describe relationships. For example, SUPPLIER_OF.
  • Title: Comments
    Maximum Length: 2000
    User comments for the relationship.
  • Default Value: 0
    The unique identifier of the conflict. This number is used by mobile or portable applications that consume the web service.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the relationship record.
  • Title: Created by Application
    Maximum Length: 30
    Default Value: HZ_WS
    The application module that created the relationship record. The default value for CreatedByModule is HZ_WS for all Web service based creation. A list of accepted values is defined in the lookup type HZ_CREATED_BY_MODULES. Review and update the value for this attribute using the Setup and Maintenance task work area, Manage Trading Community Common Lookups task.
  • Title: Creation Date
    Read Only: true
    The date and time when the relationship record was created.
  • Title: Dependent Indicator
    Maximum Length: 1
    Default Value: N
    Indicates whether one party is a dependent on another.
  • Read Only: true
    Maximum Length: 30
    The record validated by DIRECTION_CODE lookup type. P for Parent, C for Child, and N for Not Directional.
  • Title: To Date
    The date when the relationship ends.
  • Title: Head of Household Indicator
    Maximum Length: 1
    Default Value: N
    Indicates whether a person is the head of the household that he belongs to.
  • Title: Influence Level
    The sales contact's influence in a buying relationship. Sample values are Inner Circle, Political structure, None.
  • Maximum Length: 100
    The definition of the job name.
  • Maximum Length: 900
    The definition of the job package.
  • Title: Last Updated Date
    Read Only: true
    The date and time when the relationship data was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the relationship record.
  • Title: Last Update Login
    Read Only: true
    Maximum Length: 32
    The session login associated to the user who last updated the relationship record.
  • Links
  • The primary key identifier of the contact, in this relationship. One of ObjectPartyId, ObjectPartyNumber and ObjectSourceSystem along with ObjectSourceSystemReferenceValue combination is used to identify the contact party of the relationship.
  • Title: Object Party Name
    Read Only: true
    Maximum Length: 360
    The name of the object party of the relationship.
  • Title: Object Registry ID
    Maximum Length: 30
    The unique alternate identifier for the relationship of the contact party. One of ObjectPartyId, ObjectPartyNumber and ObjectSourceSystem along with ObjectSourceSystemReferenceValue combination is used to identify the object party of the relationship.
  • Title: Object Source System
    The name of external source system for the contact party in the relationship, which are defined by an admin as part of system setup. One of ObjectPartyId, ObjectPartyNumber and ObjectSourceSystem along with ObjectSourceSystemReferenceValue combination is used to identify the object party of the relationship. A list of accepted values should be pre-defined in the lookup type HZ_ORIG_SYSTEMS_VL. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Source Systems task.
  • Title: Object Source System Reference
    The unique identifier from external source system for the relationship of the contact party. One of ObjectPartyId, ObjectPartyNumber and ObjectSourceSystem along with ObjectSourceSystemReferenceValue combination is used to identify the contact party of the relationship.
  • Maximum Length: 30
    The source table name of the object party in this relationship.
  • Maximum Length: 30
    The object type of the contact.
  • Maximum Length: 30
    The usage code of object party in the relationship.
  • The number used to implement locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to determine whether another session has updated the row.
  • Read Only: true
    The attribute is used to implement optimistic locking. This number is incremented every time that 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 last queried.
  • Read Only: true
    The number to implement optimistic locking. This number is incremented every time that 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.
  • Read Only: true
    The unique identifier of the party.
  • Read Only: true
    The alternate unique identifier of the party.
  • Title: Ownership Percentage
    The percentage of the child entity owned by the parent entity.
  • Maximum Length: 10
    Default Value: false
    Indicates whether this contact person is primary contact for the customer. Accepted values are Y and N. Default value is N.
  • Maximum Length: 10
    Default Value: false
    Indicates whether this customer is primary customer for the contact. Accepted values are Y and N. Default value is N.
  • Title: Relationship Code
    Maximum Length: 30
    The code indicating whether the relationship is a forward or a backward relationship. A list of accepted relationship values is defined in the lookup PARTY_RELATIONS_TYPE. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Relationship Lookups.
  • Read Only: true
    The unique identifier of the relationship.
  • The unique identifier of the relationship record.
  • The name of external source system for the relationship, which are defined by an Admin as part of system setup.
  • The unique identifier of the relationship from the external source system.
  • Title: Relationship Type
    Maximum Length: 30
    The type of relationship of a contact party, such as CUSTOMER_SUPPLIER. A list of accepted relationship type values is defined in the lookup HZ_RELATIONSHIP_TYPE. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Relationship Lookups task.
  • The unique identifier of the request.
  • Title: Role
    The role between the subject and object party.
  • Read Only: true
    Maximum Length: 255
    Default Value: HZ_PARTIES
    The name of the table that holds the record data and is referenced to manage source system reference.
  • Title: From Date
    Date on which this relationship becomes active.
  • Read Only: true
    Maximum Length: 1
    Default Value: A
    The status of the relationship. Indicates if this is an active or inactive relationship. The values A indicate an active relationship and I an inactive relationship. This is an internal column and user is not expected to pass in a value. A list of accepted values is defined in the lookup HZ_STATUS. Review and update the values for this attribute using the Setup and Maintenance work area, Manage Standard Lookups task.
  • The primary key identifier of the subject in this relationship. One of SubjectPartyId, SubjectPartyNumber and SubjectSourceSystem along with SubjectSourceSystemReferenceValue combination is used to identify the subject party of the relationship.
  • Title: Subject Party Name
    Read Only: true
    Maximum Length: 360
    The name of the subject party.
  • Title: Subject Registry ID
    Maximum Length: 30
    The alternate unique identifier for the subject party of the relationship. One of SubjectPartyId, SubjectPartyNumber and SubjectSourceSystem along with SubjectSourceSystemReferenceValue combination is used to identify the subject party of the relationship.
  • Title: Subject Source System
    The name of external source system for the subject party in the relationship, which are defined by an Admin as part of system setup. One of SubjectPartyId, SubjectPartyNumber and SubjectSourceSystem along with SubjectSourceSystemReferenceValue combination is used to identify the subject party of the relationship. A list of accepted values should be predefined in the lookup type HZ_ORIG_SYSTEMS_VL. Review and update the value for this attribute using the Setup and Maintenance work area, Manage Trading Community Source Systems task.
  • Title: Subject Source System Reference
    The unique identifier from external source system for the subject party in the relationship. One of SubjectPartyId, SubjectPartyNumber and SubjectSourceSystem along with SubjectSourceSystemReferenceValue combination is used to identify the subject party of the relationship.
  • Maximum Length: 30
    The source table of the subject.
  • Maximum Length: 30
    The subject type of the contact.
  • Maximum Length: 30
    The usage code of subject party in the contact.
Back to Top

Examples

The following example shows how to get a relationship by submitting a GET request on the REST resource using 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/contacts/CDRM_2336/child/Relationship/300100091049193

Example of Response Body

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

  "RelationshipId": 300100091049194,
  "RelationshipRecId": 300100091049193,
  "ObjectVersionNumber": 1,
  "RelationshipSourceSystem": null,
  "RelationshipSourceSystemReferenceValue": null,
  "ObjectPartyId": 300100010638186,
  "SubjectPartyId": 300100010649305,
  "RelationshipType": "CONTACT",
  "RelationshipCode": "CONTACT_OF",
  "StartDate": "2016-07-24",
  "EndDate": "4712-12-31",
  "CreatedByModule": "HZ_WS",
  "Comments": null,
  "Status": "A",
  "CreatedBy": "SALES_ADMIN",
  "CreationDate": "2016-07-24T23:32:38-07:00",
  "LastUpdateDate": "2016-07-24T23:32:39-07:00",
  "LastUpdateLogin": "386E82567D981A32E053B80AF40A72B9",
  "LastUpdatedBy": "SALES_ADMIN",
  "DirectionCode": "P",
  "DependentFlag": "N",
  "PercentageOwnership": null,
  "SubjectPartyNumber": "CDRM_2336",
  "PartyId": 300100010649305,
  "ObjectVersionNumber1": 20,
  "SubjectSourceSystem": null,
  "SubjectSourceSystemReferenceValue": null,
  "ObjectSourceSystem": null,
  "ObjectSourceSystemReferenceValue": null,
  "ObjectPartyNumber": "CDRM_2310",
  "PartyId1": 300100010638186,
  "ObjectVersionNumber2": 2,
  "SubjectTableName": "HZ_PARTIES",
  "SubjectType": "PERSON",
  "SubjectUsageCode": null,
  "ObjectTableName": "HZ_PARTIES",
  "ObjectType": "ORGANIZATION",
  "ObjectUsageCode": null,
  "HeadOfHouseholdFlag": "N",
  "RequestId": null,
  "JobDefinitionName": null,
  "JobDefinitionPackage": null,
  "SSROwnerTableName": "HZ_PARTIES",
  "SubjectPartyName": "John Wilson",
  "ObjectPartyName": "WS_SA530201205237378312",
  "Role": "CONTACTORG",
  "InfluenceLevel": null,
  "BackwardRole": "ORGWITHCONTACT",
...
}
Back to Top