Payroll and OTL - EBS (MOSC)

MOSC Banner

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!

12.2.9 Retro Notification Report (Enhanced) - PDF uses tokenised payroll name value set causing issu

edited Jul 2, 2020 12:59PM in Payroll and OTL - EBS (MOSC) 2 commentsAnswered ✓

Hi - We are testing the 12.2 upgrade from 12.1.3.

In our current process, we have a Request set for running all the following retro jobs together.

> Retro Notification Report (Enhanced) - PDF

> Retropay (Enhanced)

> Payroll Messages Report

The shared parameter for these programs is the payroll.

Retro Notification Report (Enhanced) - PDF uses the value set PY_SRS_CC_TOKEN_PAYROLL for payroll parameter, which resolves to 'PAYROLL_ID=||payroll_id' for ID value.

Retropay (Enhanced) uses the value set PY_SRS_PAYROLL for payroll parameter.  The above tokenised value, being used for shared parameter, is throwing an error 'APP-FND-01564: Oracle error 1722 in FDFGVD. Cause: FDFGVD failed due to ORA-01722 Invalid number' on the 'Retropay (Enhanced)' parameters selection.

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center