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.

PeopleTools and Lifecycle Management - PSFT (MOSC)

Any issues using Classic (non-Fluid) on PeopleTools 8.56?

Aug 23, 2017 11:21AM edited Sep 7, 2017 6:15PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 2 commentsAnswered

Hello Community!

Are there any known issues with using the Classic (non-Fluid) interface on PeopleTools 8.6?

We are trying to plan out our upgrades for the next year and I could use some advice. Currently, we are the following versions:

PeopleTools: 8.55.05
Functional Modules:
- Human Resources, Benefits Administration, Talent Acquisition, Time & Labor, Absence Management: 9.2 with PUM 21
- Payroll for North America: 9.2 with PUM 21, we will apply Tax Updates 17B and 17C in a couple of weeks and will keep current with Tax Updates as they are released
- All modules are on Classic (non-Fluid)
Search: SES

Our current plan is:

Upgrade PeopleTools to the latest version (8.56.?) from December to January and at the same time switch to ElasticSearch but stay on Classic.

1

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