EEX9.2:Unable to Rollover Travel Authorization when Created from Previously Rolled TA Inherits Rollover Status of "C" Completed and should be "N" New (Doc ID 2194516.1)

Last updated on OCTOBER 18, 2016

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

9.2 

Issue
When a user creates a new Travel Authorization (TA) by copying from an existing previously rolled Travel Authorization, the ROLLOVER_STATUS field on the EX_TAUTH_HDR table copies over the value of ‘C’ on the new TA causing the system to believe the new TA has already been rolled over.

Steps:

1) Create budget
2) Create Travel Authorization (TA) and budget check before approval
3) Rollover TA to new budget period, this is a two step process.

   a) via Travel and Expenses>Manage Accounting>Rollover Travel Authorization Select Current Period Radio button and run the process.

   b) then via Travel and Expenses>Manage Accounting>Rollover Travel Authorization select Roll to New Period radio button and run the process

4) Locate a TA that has already been rolled, or roll an existing approved TA.
5) Navigate to: Main Menu > FSCM > Employee Self Service > Travel and Expense Center >Travel Authorizations > Create/Modify
6) Click Add button
7) Beside Quick Start choose the option for “An Existing Authorization”, and then click Go button
8) Select a TA that has previously been rolled over (has a ROLLOVER_STATUS on EX_TAUTH_HDR of ‘C’)
9) Change dates to be in the future, if needed
10) Click Save for Later button (Authorization ID is generated successfully) - Issue also occurs when submitting instead of saving
11) Run SQL to verify rollover status of new TA – Notice the ROLLOVER_STATUS copied over with a value of ‘C’. This status means it has already been rolled even though this is a new TA that has never been approved or rolled.

Expected Results
When a user creates a new Travel Authorization by copying from an existing previously rolled Travel Authorization, the ROLLOVER_STATUS field on the EX_TAUTH_HDR table for the new TA should have a value of ‘N’ since no action for rolling over the TA has been completed.

Actual Results:

Due to this after the new TA has been fully approved it is not available to rollover since the system believes it has already been rolled over.

Please see replication steps document for more details.

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms