Jump to

• Request
• Response
• Examples

Get an organization payment method

get

/hcmRestApi/resources/11.13.18.05/organizationPaymentMethodsLOV/{organizationPaymentMethodsLOVUniqID}

Request

Path Parameters

• organizationPaymentMethodsLOVUniqID(required): string
  This is the hash key of the attributes which make up the composite key for the Organization Payment Methods List of Values resource and used to uniquely identify an instance of Organization Payment Methods List of Values. The client should not generate the hash key value. Instead, the client should query on the Organization Payment Methods List of Values collection resource in order to navigate to a specific instance of Organization Payment Methods List of Values to get the hash key.

Query Parameters

• dependency: string
  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>
• expand: string
  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).
• fields: string
  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
• links: string
  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
  
• onlyData: boolean
  The resource item payload will be filtered in order to contain only data (no links section, for example).

Header Parameters

• Effective-Of:
  This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
• Metadata-Context:
  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".
• REST-Framework-Version:
  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

• application/json

Default Response

The following table describes the default response for this task.

Headers

• Metadata-Context:
  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".
• REST-Framework-Version:
  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 : organizationPaymentMethodsLOV-item-response

Type: object

Show Source

• BaseOrgPayMethodName: string
  Title: Base Name

  Read Only: true

  Maximum Length: 80

  Code that uniquely identifies the organization payment method for the legislative data group.
• Category: string
  Title: Payment Category

  Maximum Length: 2

  Category of the payment method, such as cash, check, or electronic file transfer.
• CurrencyCode: string
  Title: Currency

  Read Only: true

  Maximum Length: 15

  Code that identifies the currency used in payroll calculations, payments, and balances.
• EffectiveEndDate: string (date)
  Title: Effective End Date

  Read Only: true

  Last date in a date range during which an organization payment method is available for processing.
• EffectiveStartDate: string (date)
  Title: Effective Start Date

  Read Only: true

  First date in a date range during which an organization payment method is available for processing.
• LegislationCode: string
  Read Only: true

  Maximum Length: 30

  Code for the legislation, such as GB or US, associated with the organization payment method.
• LegislativeDataGroupId: integer (int64)
  Read Only: true

  Legislative data group associated with the organization payment method.
• links: array Links
  Title: Links

  The link relations associated with the resource instance.
• OrgPaymentMethodId: integer (int32)
  Title: Organization Payment Method ID

  Read Only: true

  Unique identifier used to retrieve the organization payment method.
• OrgPaymentMethodName: string
  Title: Organization Payment Method Name

  Read Only: true

  Maximum Length: 80

  Name of the organization payment method that determines the payment source and payment type.
• PaymentTypeName: string
  Title: Payment Type

  Maximum Length: 80

  Name of the payment method, such as cash, check, or direct deposit.

{
    "type":"object",
    "properties":{
        "CurrencyCode":{
            "title":"Currency",
            "maxLength":15,
            "type":"string",
            "description":"Code that identifies the currency used in payroll calculations, payments, and balances.",
            "nullable":true,
            "readOnly":true,
            "x-queryable":true
        },
        "LegislativeDataGroupId":{
            "type":"integer",
            "description":"Legislative data group associated with the organization payment method.",
            "format":"int64",
            "nullable":false,
            "readOnly":true,
            "x-hints":{
                "precision":18
            },
            "x-queryable":true
        },
        "LegislationCode":{
            "maxLength":30,
            "type":"string",
            "description":"Code for the legislation, such as GB or US, associated with the organization payment method.",
            "nullable":false,
            "readOnly":true,
            "x-queryable":true
        },
        "Category":{
            "title":"Payment Category",
            "maxLength":2,
            "type":"string",
            "description":"Category of the payment method, such as cash, check, or electronic file transfer.",
            "nullable":false,
            "x-queryable":true
        },
        "EffectiveEndDate":{
            "title":"Effective End Date",
            "type":"string",
            "description":"Last date in a date range during which an organization payment method is available for processing.",
            "format":"date",
            "nullable":false,
            "readOnly":true,
            "x-queryable":true
        },
        "PaymentTypeName":{
            "title":"Payment Type",
            "maxLength":80,
            "type":"string",
            "description":"Name of the payment method, such as cash, check, or direct deposit.",
            "nullable":false,
            "x-hints":{
                "controlType":"choice"
            },
            "x-queryable":true
        },
        "links":{
            "title":"Links",
            "type":"array",
            "description":"The link relations associated with the resource instance.",
            "items":{
                "$ref":"#/components/schemas/link"
            }
        },
        "BaseOrgPayMethodName":{
            "title":"Base Name",
            "maxLength":80,
            "type":"string",
            "description":"Code that uniquely identifies the organization payment method for the legislative data group.",
            "nullable":false,
            "readOnly":true,
            "x-queryable":true
        },
        "EffectiveStartDate":{
            "title":"Effective Start Date",
            "type":"string",
            "description":"First date in a date range during which an organization payment method is available for processing.",
            "format":"date",
            "nullable":false,
            "readOnly":true,
            "x-queryable":true
        },
        "OrgPaymentMethodId":{
            "title":"Organization Payment Method ID",
            "type":"integer",
            "description":"Unique identifier used to retrieve the organization payment method.",
            "format":"int32",
            "nullable":false,
            "readOnly":true,
            "x-hints":{
                "precision":9
            },
            "x-queryable":true
        },
        "OrgPaymentMethodName":{
            "title":"Organization Payment Method Name",
            "maxLength":80,
            "type":"string",
            "description":"Name of the organization payment method that determines the payment source and payment type.",
            "nullable":false,
            "readOnly":true,
            "x-hints":{
                "controlType":"choice"
            },
            "x-queryable":true
        }
    }
}

Nested Schema : Links

Type: array

Title: Links

The link relations associated with the resource instance.

Show Source

• Array of: object link

{
    "title":"Links",
    "type":"array",
    "description":"The link relations associated with the resource instance.",
    "items":{
        "$ref":"#/components/schemas/link"
    }
}

Nested Schema : link

Type: object

Show Source

• href: string
  Title: hyperlink reference

  The URI to the related resource.
• kind: string
  Title: kind

  Allowed Values: [ "collection", "item", "describe", "other" ]

  The kind of the related resource.
• name: string
  Title: name

  The name of the link to the related resource.
• properties: object properties
• rel: string
  Title: relation

  Allowed Values: [ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]

  The name of the relation to the resource instance. Example: self.

{
    "type":"object",
    "properties":{
        "kind":{
            "title":"kind",
            "type":"string",
            "description":"The kind of the related resource.",
            "enum":[
                "collection",
                "item",
                "describe",
                "other"
            ]
        },
        "rel":{
            "title":"relation",
            "type":"string",
            "description":"The name of the relation to the resource instance.  Example: self.",
            "enum":[
                "self",
                "lov",
                "parent",
                "canonical",
                "child",
                "enclosure",
                "action",
                "custom"
            ]
        },
        "name":{
            "title":"name",
            "type":"string",
            "description":"The name of the link to the related resource."
        },
        "href":{
            "title":"hyperlink reference",
            "type":"string",
            "description":"The URI to the related resource."
        },
        "properties":{
            "type":"object",
            "properties":{
                "changeIndicator":{
                    "type":"string",
                    "description":"Change indicator or the ETag value of the resource instance."
                }
            }
        }
    }
}

Nested Schema : properties

Type: object

Show Source

• changeIndicator: string
  Change indicator or the ETag value of the resource instance.

{
    "type":"object",
    "properties":{
        "changeIndicator":{
            "type":"string",
            "description":"Change indicator or the ETag value of the resource instance."
        }
    }
}

Back to Top

Examples

Get organization payment methods using AssignmentNumber

This example shows how to retrieve organization payment methods by submitting a GET request on the REST resource using cURL. Use the findByAssignmentnumber finder to retrieve the organization payment methods by assignment number of a person.

curl -i -u "<username>:<password>" -H -X GET https://<hostname>:<portno>/hcmRestApi/resources/11.13.18.05/organizationPaymentMethodsLOV?finder=findByAssignmentNumber;AssignmentNumber=<AssignmentNumber>

Example of Response Header

The following is an example of the response header.

HTTP/1.1 200 OK                     
Content-Type : application/vnd.oracle.adf.resourceitem+json

Example of Response Body

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

{
  "items": [
    {
      "BaseOrgPayMethodName": "ZHRX-AU-CDRM-LDG001-Cheque",
      "OrgPaymentMethodId": 300100031625185,
      "OrgPaymentMethodName": "ZHRX-AU-CDRM-LDG001-Cheque",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2000-01-01",
      "PaymentTypeName": "Check",
      "Category": "CH",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": []
    },
    {
      "BaseOrgPayMethodName": "ZHRX-AU-CDRM-LDG001-Direct Deposit",
      "OrgPaymentMethodId": 300100031625188,
      "OrgPaymentMethodName": "ZHRX-AU-CDRM-LDG001-Direct Deposit",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2000-01-01",
      "PaymentTypeName": "EFT",
      "Category": "MT",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": []
    },
    {
      "BaseOrgPayMethodName": "ZHRX-AU-LDG001-OPM1-Cheque",
      "OrgPaymentMethodId": 300100016881652,
      "OrgPaymentMethodName": "ZHRX-AU-LDG001-OPM1-Cheque",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2000-01-01",
      "PaymentTypeName": "Check",
      "Category": "CH",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": []
    },
    {
      "BaseOrgPayMethodName": "ZHRX-AU-LDG001-OPM1-DirectDebit",
      "OrgPaymentMethodId": 300100016881657,
      "OrgPaymentMethodName": "ZHRX-AU-LDG001-OPM1-DirectDebit",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2010-01-01",
      "PaymentTypeName": "EFT",
      "Category": "MT",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": [
         {...
             }
       ]
}

Get organization payment methods as of effective date

This example shows how to revieve organization payment methods as of an effective date by submitting a GET request on the REST resource using cURL.

curl -i -u "<username>:<password>" -H "effectiveDate=2020-01-01" -X GET https://<hostname>:<portno>/hcmRestApi/resources/11.13.18.05/organizationPaymentMethodsLOV?q=OrgPaymentMethodName=SMBHAV1"

Example of Response Header

The following is an example of the response header.

HTTP/1.1 200 OK                     
Content-Type : application/vnd.oracle.adf.resourceitem+json

Example of Response Body

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

{
  "items": [
    {
      "BaseOrgPayMethodName": "ZHRX-AU-CDRM-LDG001-Cheque",
      "OrgPaymentMethodId": 300100031625185,
      "OrgPaymentMethodName": "ZHRX-AU-CDRM-LDG001-Cheque",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2000-01-01",
      "PaymentTypeName": "Check",
      "Category": "CH",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": []
    },
    {
      "BaseOrgPayMethodName": "ZHRX-AU-CDRM-LDG001-Direct Deposit",
      "OrgPaymentMethodId": 300100031625188,
      "OrgPaymentMethodName": "ZHRX-AU-CDRM-LDG001-Direct Deposit",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2000-01-01",
      "PaymentTypeName": "EFT",
      "Category": "MT",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": []
    },
    {
      "BaseOrgPayMethodName": "ZHRX-AU-LDG001-OPM1-Cheque",
      "OrgPaymentMethodId": 300100016881652,
      "OrgPaymentMethodName": "ZHRX-AU-LDG001-OPM1-Cheque",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2000-01-01",
      "PaymentTypeName": "Check",
      "Category": "CH",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": []
    },
    {
      "BaseOrgPayMethodName": "ZHRX-AU-LDG001-OPM1-DirectDebit",
      "OrgPaymentMethodId": 300100016881657,
      "OrgPaymentMethodName": "ZHRX-AU-LDG001-OPM1-DirectDebit",
      "CurrencyCode": "AUD",
      "EffectiveEndDate": "4712-12-31",
      "EffectiveStartDate": "2010-01-01",
      "PaymentTypeName": "EFT",
      "Category": "MT",
      "LegislationCode": "AU",
      "LegislativeDataGroupId": 300100001794627,
      "links": [
         {...
             }
  ]
}

Back to Top