Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Payroll and OTL - EBS (MOSC)

Announcements for Payroll and OTL can now be found in the Announcements - Payroll and OTL - EBS (MOSC) subcategory. Follow to be sure you don't miss a thing!

Entry Level Approval for OTL Timecards

Dec 12, 2019 1:28PM edited Jan 27, 2020 4:25PM in Payroll and OTL - EBS (MOSC) 2 commentsAnswered ✓

Issue is somewhat akin to the one raised in , with requirement to route approvals based on project type (capitalised vs. non) and a custom role.

If the project is capitalised, approval should go to custom role, if present; otherwise to project manager.
If the project is non-cap/expensed, approval goes to HR supervisory chain.

For example, a timecard with three lines:

Proj 'A' [Capitalised Mtce, w/Project Manager as Key Member]
Proj 'B' [Non-Cap Admin, w/Project Manager]
Proj 'C' [Capitalised Labour, w/Custom Role ("XX Leader") as key member]

First line should go to person designated as project manager of project 'A'.

Tagged:

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month