Create a relationship type

post

/fscmRestApi/resources/11.13.18.05/hedRelationshipTypes

Request

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: Relationship Indicator
    Maximum Length: 1
    Default Value: false
    The relationship type status. The default value for relationship type is false. If the value is false, the relationship type is inactive and if it's true, it will be active.
  • Title: Object Type Code
    Maximum Length: 30
    The object type code of relationship.
  • Title: Relationship Code
    Maximum Length: 30
    The code of relationship.
  • Title: Relationship Type Code
    Maximum Length: 30
    The code of relationship type.
  • Title: Subject Type Code
    Maximum Length: 30
    The subject type code of relationship.
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 : hedRelationshipTypes-item-response
Type: object
Show Source
  • Title: Relationship Indicator
    Maximum Length: 1
    Default Value: false
    The relationship type status. The default value for relationship type is false. If the value is false, the relationship type is inactive and if it's true, it will be active.
  • Links
  • Title: Object Type Code
    Maximum Length: 30
    The object type code of relationship.
  • Title: Object Type Meaning
    Read Only: true
    Maximum Length: 80
    The object type meaning of relationship. A list of accepted values is defined in the lookup type PARTY_TYPE.
  • Title: Relationship Code
    Maximum Length: 30
    The code of relationship.
  • Title: Relationship Meaning
    Read Only: true
    Maximum Length: 80
    The meaning of relationship. A list of accepted values is defined in the lookup type PARTY_RELATIONS_TYPE.
  • Title: Relationship Type Code
    Maximum Length: 30
    The code of relationship type.
  • Title: Relationship Type ID
    Read Only: true
    The ID of relationship type.
  • Title: Relationship Type Meaning
    Read Only: true
    Maximum Length: 80
    The meaning of relationship type. A list of accepted values is defined in the lookup type HZ_RELATIONSHIP_TYPE.
  • Title: Subject Type Code
    Maximum Length: 30
    The subject type code of relationship.
  • Title: Subject Type Meaning
    Read Only: true
    Maximum Length: 80
    The subject type meaning of relationship. A list of accepted values is defined in the lookup type PARTY_TYPE.
Back to Top