Get a position
/hcmRestApi/resources/11.13.18.05/positionsLov/{positionsLovUniqID}
Request
-
positionsLovUniqID(required): string
This is the hash key of the attributes which make up the composite key--- PositionId, EffectiveStartDate and EffectiveEndDate ---for the Positions List of Values resource and used to uniquely identify an instance of Positions List of Values. The client should not generate the hash key value. Instead, the client should query on the Positions List of Values collection resource with a filter on the primary key values in order to navigate to a specific instance of Positions List of Values.
For example: positionsLov?q=PositionId=<value1>;EffectiveStartDate=<value2>;EffectiveEndDate=<value3>
-
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).
-
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 TopResponse
- application/json
Default Response
-
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.
object
-
ActiveStatus: string
Title:
Status
Read Only:true
Maximum Length:30
Status of the position such as active or inactive. -
BusinessUnitId: integer
(int64)
Read Only:
true
Unique identifier of the mandatory business unit for the position. -
DepartmentId: integer
(int64)
Read Only:
true
Unique identifier of the mandatory department for the position. -
DepartmentName: string
Title:
Department
Read Only:true
Maximum Length:240
Name of the department associated with the position. -
EffectiveEndDate: string
(date)
Title:
Effective End Date
Read Only:true
Date at the end of the period within which the position is effective. -
EffectiveStartDate: string
(date)
Title:
Effective Start Date
Read Only:true
Date at the beginning of the period within which the position is effective. -
HiringStatus: string
Title:
Hiring Status
Read Only:true
Maximum Length:80
Hiring status of the position such as proposed, frozen, or approved. -
JobCode: string
Title:
Job Code
Read Only:true
Maximum Length:30
Code of the job associated with the position. -
JobId: integer
(int64)
Read Only:
true
Unique identifier of the mandatory job for the position. -
JobName: string
Title:
Job
Read Only:true
Maximum Length:240
Name of the job associated with the position. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
LocationId: integer
(int64)
Read Only:
true
Unique identifier of the location for the position. -
PositionCode: string
Title:
Code
Read Only:true
Maximum Length:30
Unique code for the position within the business unit. -
PositionId: integer
(int64)
Read Only:
true
Unique identifier attribute for the position. -
PositionName: string
Title:
Name
Read Only:true
Maximum Length:240
Name of the position.
array
Links
object
-
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.
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Examples
The following examples show how to retrieve a position by submitting a GET request on the REST resource using cURL.
Use a Query Parameter
In this example, the query parameter PositionId
is used to retrieve a position. The following is an example of the cURL command.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4""-X GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/positionsLov?q=PositionId=300100173148294"
Example of Response Header
The following is an example of the response header.
Status: 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": [ { "PositionId": 300100173148294, "EffectiveStartDate": "1951-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "P0000001_300100003141378", "PositionName": ".Net Developer-1", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 300100173139372, "JobCode": "J0000001", "JobName": ".Net Developer Level-1", "DepartmentId": 300100173147421, "DepartmentName": "LV & MV Cluster 2 - Mastertech-GROUP/SHRELMC2MA", "LocationId": null, "BusinessUnitId": 300100003141378, "links": [2] { ...} ] }
Use Finders
Example 1
In this example, the finder findByWord
is used with the finder variables SearchTerms
and FilterAttributes
to retrieve the positions that match the specified criteria. The following is an example of the cURL command.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4""-X GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/positionsLov?finder=findByWord;SearchTerms=POS,FilterAttributes=PositionName PositionCode"
Example of Response Header
The following is an example of the response header.
Status: 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": [ { "PositionId": 3950, "EffectiveStartDate": "2000-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "POSCD3950", "PositionName": "1001.Operations Vice President", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 8, "JobCode": "JOBCD8", "JobName": "VP300.Vice President", "DepartmentId": 3645, "DepartmentName": "Vision Electric", "LocationId": 11523, "BusinessUnitId": 202, "links": [2] }, { "PositionId": 3504, "EffectiveStartDate": "2002-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "POSCD3504", "PositionName": "1010.Senior Marketing Manager", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 1649, "JobCode": "JOBCD1649", "JobName": "MM100.Marketing Manager", "DepartmentId": 498, "DepartmentName": "Vision ADB", "LocationId": 208, "BusinessUnitId": 202, "links": [2] }, { "PositionId": 3954, "EffectiveStartDate": "2000-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "POSCD3954", "PositionName": "1031.Corporate Accounting Manager", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 16, "JobCode": "JOBCD16", "JobName": "MGR500.Manager", "DepartmentId": 3645, "DepartmentName": "Vision Electric", "LocationId": 11523, "BusinessUnitId": 202, "links": [2] { ...} ] }
Example 2
In this example, the finder findByPositionId
is used with the finder variable PositionId
to retrieve the positions that match the specified criteria. The following is an example of the cURL command.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4""-X GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/positionsLov?finder=findByPositionId;PositionId=3953"
Example of Response Header
The following is an example of the response header.
Status: 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": [ { "PositionId": 3953, "EffectiveStartDate": "2000-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "POSCD3953", "PositionName": "1501.Resource Planner", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 124, "JobCode": "JOBCD124", "JobName": "PLN500.Planner", "DepartmentId": 3645, "DepartmentName": "Vision Electric", "LocationId": 11523, "BusinessUnitId": 202, "links": [2] { ...} ] }
Example 3
In this example, the finder findByPositionAttr
is used with the finder variable BusinessUnitId
to retrieve the positions that match the specified criteria. The following is an example of the cURL command.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4""-X GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/positionsLov?finder=findByPositionAttr;BusinessUnitId=202"
Example of Response Header
The following is an example of the response header.
Status: 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": [ { "PositionId": 3951, "EffectiveStartDate": "2000-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "POSCD3951", "PositionName": "1300.Customer Service Administrator", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 724, "JobCode": "JOBCD724", "JobName": "FS300.Field Service Administrator", "DepartmentId": 3645, "DepartmentName": "Vision Electric", "LocationId": 11523, "BusinessUnitId": 202, "links": [2] }, { "PositionId": 3953, "EffectiveStartDate": "2000-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "POSCD3953", "PositionName": "1501.Resource Planner", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 124, "JobCode": "JOBCD124", "JobName": "PLN500.Planner", "DepartmentId": 3645, "DepartmentName": "Vision Electric", "LocationId": 11523, "BusinessUnitId": 202, "links": [2] }, { "PositionId": 3952, "EffectiveStartDate": "2000-01-01", "EffectiveEndDate": "4712-12-31", "PositionCode": "POSCD3952", "PositionName": "2001.Materials Manager", "ActiveStatus": "A", "HiringStatus": "APPROVED", "JobId": 16, "JobCode": "JOBCD16", "JobName": "MGR500.Manager", "DepartmentId": 3645, "DepartmentName": "Vision Electric", "LocationId": 11523, "BusinessUnitId": 202, "links": [2] { ...} ] }