4/1/2021 Document 781997.

Pow Last Login: April 1, 2021 2:22 PM CAT Switch to Cloud Support Echezona (Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates Community

Give Feedback...
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.

Overview of Position Control in Oracle HRMS (Doc ID 781997.1) To Bottom

In this Document Was this document helpful?

Purpose Yes
No
Scope
Details
Document Details
How is Position Control Different to the Standard Position Functionality?
Templates
Type:
BULLETIN
Roles Status:
PUBLISHED
Routing and Approval Last Major
Jul 6, 2019
Update:
Nov 24, 2020
Last Update:
References

Related Products
APPLIES TO: Oracle Human Resources

Oracle Human Resources - Version 11.5.10.0 to +

Information Centers
Information in this document applies to any platform.
Information Center: Oracle E-
Business Suite HRMS / HCM
PURPOSE [1099813.2]

Information Center: Oracle

This document provides an overview of the functionality of Position Control. Fusion - EBS Coexistence
[1527824.2]

SCOPE Information Center: EBS

Human Resources (All
Application Versions)
It is intended for any HRMS user who has not used Position Control before and needs to understand the functionality. [1322119.2]

DETAILS
Document References

Position Control and Budgeting

How is Position Control Different to the Standard Position Functionality? Viewlets [742102.1]

Oracle HRMS Position Control

and Budgeting [224961.1]
Position Control allows you to define and update positions using template screens.
Templates allow you to control which users have access to create and to update positions and also allow you to specify which
fields on the screen are visible, updatable, and mandatory. They also mean that an approval chain can be defined for updates
Recently Viewed
to positions and for the creation of new position.
If you designate an organization as a position control organization, you define and maintain positions for that organization using Reports and Processes for
position transactions. Otherwise, you use the existing position definition window. Budgets in Oracle HRMS
[781237.1]
All users have access to the Define Position screen How to Run Script
Work Structures -> Position -> Description wfmlrdbg.sql and Collect its
But if you have any organizations included in a Position Control organization hierarchy, you will not be able to select them in the Output? [1364300.1]
Organization field LOV. Using Java Web Start with
Oracle E-Business Suite
[2188898.1]
To define or update a position which uses a PC organization you will have to use the Position Transaction screen
Create Accounting For AP
Work Structures -> Position -> Position Transaction Payment Fails With Error:
Here you can only create and update positions with a PC organization. 95353 - Subledger
To use this screen the user must be assigned a role giving access. Accounting was Unable to
Derive an Accounting Code
Combination Using the
If the Organization field LOV does not include the organization you are expecting, check whether the organization is position
Account Derivation Rule
controlled and ensure you are using the correct screen for the organization. [1550238.1]
Journal Import of Budget
data Fails With Error EF02:
Detail Posting Not Allowed
For This Accounting Flexfield
Templates
[1570294.1]
Show More
A Transaction Templates overlays a transaction window. It specifies which fields on the form you can view and change and
which fields are mandatory.

There are 2 types of templates used here - Task Templates and Role Templates.

Task Templates

When you navigate to the Position Transaction screen

Work Structures -> Position -> Position Transaction
You are asked to select a task to perform. The tasks available in the LOV use position transaction Task Templates.

'Create Position' and 'Update Position' are the seeded task templates and these give you the maximum possible permission so
you can view and edit all fields (or attributes) in the form.
You can create additional Task Templates to restrict access to those fields or to make some fields mandatory.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=119797641502802&id=781997.1&displayIndex=19&_afrWindowMode=0&_a… 1/3
4/1/2021 Document 781997.1
Role Templates

Each user involved in Position Transactions will have at least one role.

These roles are defined in the Maintain Roles screen

Transaction Maintenance -> Roles
Each different Role can be given a different Position Transaction Role Template

'Basic Role Position' is the seeded role template and this gives you the maximum possible permission so you can view and edit
all fields (or attributes) in the form.
You can create additional Task Templates to restrict access to those fields or make some fields mandatory.

When a user goes to the Position Transaction screen to create or update a position they will select a task template and they will
also have a role template associated with their role. The application will enforce the most restrictive setting for each attribute.
If a user is approving a transaction then only the role template will be used.

You can define a new template (Task or Role), basing it on existing templates, or combine multiple templates into one.

Roles

HRMS roles determine who can enter and approve data for a given transaction type, such as a position transaction.
A user must have an HRMS role in order to work on a transaction.

Seeded role types include:

HR Manager
Position Control Initiator
Position Control Reviewer
Position Control Approver

The same employee can be associated with more than one role. So he could initiate, review and approve position transactions.
But he may not need the same permissions for each role.
For example
As a 'Position Control Initiator' he will need to be able to enter all the details of a new position so will require a template that
gives access to all attributes;
As a 'Position Control Reviewer' he may only be required to have view-only access to the position attributes.
So you can see that different role templates may be required for different roles.

Each role will be linked with a number of FND Users (or positions if the position hierarchy is used for approval).
And each role can be associated with a position transaction Role Template.

Routing and Approval

Defining the Routing

The approval routing for position transactions can use one of 3 methods:
Supervisor Hierarchy
Position Hierarchy
Routing List

The Supervisor and Position Hierarchy methods are self explanatory.

Routing lists use HRMS roles and can be defined in the Routing Lists screen
Transaction Maintenance -> Routing Lists
A Routing List is simply a sequence of roles, at least one of which must be able to approve. It is possible to select a user for a
role within the sequence, in which case rather than any user in the role being able to progress the transaction it must be that
specific user.

To define the approval routing for Position Transactions for a Business Group or globally you use the Transaction Type Wizard
Transaction Maintenance -> Transaction Type Wizard
The steps guide you easily through the possible selections including your routing method.

Saving and Routing a Position Transaction

When you have entered the position details in the Create or Update position template and you save your changes, the Routing
window pops up.
You can save your work or you can move it into the approval chain.

- To save your transaction without routing it:

Choose Save in Inbox to save the transaction and wait until later to resume work on it.
Choose Save and Continue to save your work and continue entering data in the transaction.
- To route the action to other users for further action, choose Forward.
The application displays the next qualified destination, but you can choose a different one from the list of values.
- To skip the next destination in the routing sequence, choose the arrow button. Continue choosing this button until you see the
desired destination.

The next approver will receive a notification. He can either use the links in that notification, or can go to the Transaction Status
screen
Transaction Maintenance -> Transaction Status
to progress the transaction.
He will also use the Routing window and can route the transaction backwards or forwards or reject the transaction.
If he is an approver then he can approve and apply the transaction.

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=119797641502802&id=781997.1&displayIndex=19&_afrWindowMode=0&_a… 2/3
4/1/2021 Document 781997.1

Rejected Transactions

When a user rejects the transaction using the Routing window, the transaction is returned to the initiator.
When the initiator rejects it, the transaction is terminated.

Approving and Applying

When the 'Approve' checkbox in the Routing window is ticked the transaction is Approved. However it is not yet saved to the
database and in fact the transaction can still be rejected and terminated at this point.
To save the changes to the database the 'Apply' checkbox must be ticked.
It does not have to be applied by the same user that approved the transaction.

The Process Log

The Process Log

Reports and Processes -> Process Log
displays transaction information that may be useful when a transaction errors.

Transaction history

The Transaction Status screen

Transaction Maintenance -> Transaction Status
shows the status of all transactions, their routing history and who currently possesses the transaction.
You can access the Routing window from this screen which means that it is possible to progress a transaction if the user who
possesses the transaction is absent.

Details of the transaction history can also be seen by querying up a position in the Position Transaction screen
Work Structures -> Positions -> Position Transaction
and clicking on
Tools -> Position Transaction History

REFERENCES

NOTE:742102.1 - Position Control and Budgeting Viewlets

NOTE:224961.1 - Oracle HRMS Position Control and Budgeting
Didn't find what you are looking for? Ask in Community...

Related
Products

Oracle E-Business Suite > Human Capital Management > Human Resources > Oracle Human Resources > Orgs,Jobs,Locs,Positions etc > Position Issues

Keywords
APPROVAL; APPROVE; CONTROL; DEFINE POSITION; POSITION HIERARCHY; POSITION TRANSACTION; PROCESS LOG; RECEIVE NOTIFICATION; TRANSACTION HISTORY;
TRANSACTION STATUS

Back to Top
Copyright (c) 2021, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=119797641502802&id=781997.1&displayIndex=19&_afrWindowMode=0&_a… 3/3