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.

HCM - JDE1 (MOSC)

Year to Date corrections

May 25, 2011 7:13AM edited Apr 25, 2013 9:14AM in HCM - JDE1 (MOSC) 1 commentAnswered

We need to make corrections to our Year to Date adjustments (originally processed through interims YTD dated March 31st).

If we repeat this process using March 31st for additional corrections at this time what are the risks?

Our concern is Year to Date amounts of subsequent payrolls will not be affected, along with excludable wages, etc.

We are considering manual changes to tax history at this point.

Any other suggestions would be appreciated.

Thanks!!

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