My Oracle Support Banner

EEX 9.1: When an Expense Report is Budget Check, the Associated Travel Authorization Is Not Dis-encumberied (Doc ID 2199214.1)

Last updated on MARCH 27, 2019

Applies to:

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

Symptoms

When an expense report is budget check, the associated travel authorization is not dis-encumbered.

Steps:

1. An employee creates and submits a travel authorization for approval with one transaction.
2. The approver opens the travel authorization for approval and budget checks it.
3. The approver approves the travel authorization.
4. The employee creates an expense report using Quick Start: A Travel Authorization.
5. The one row from the travel authorization is pulled into the expense report.
6. Two more transaction rows are added to the expense report.
7. The first row that came from the travel authorization is deleted.
8. The expense report is submitted for approval.
9. The approver opens the expense report for approval and budget checks it.

Actual Result:

The encumbrance from the travel authorization is not released.

Expected Result:

The encumbrance from the travel authorization should be released.

Please see the replication steps document for more details.

NOTE: In the  attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.