My Oracle Support Banner

EEX 9.2: Fluid Travel Authorization Line Reimbursement Code Gets Incorrectly Populated if Payment Type Prepaid Is Being Used on Prior Rows (Doc ID 2810640.1)

Last updated on OCTOBER 06, 2021

Applies to:

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

Symptoms


A problem has been detected with the Fluid Travel Authorization entry component, where the system is incorrectly populating the Reimbursement Code value of the created lines, (Record Field PS_EX_TAUTH_LINE.REIMBURSEMENT_CD), disregarding the selected Payment Type (Field EXPEND_MTHD) for each of the entered lines.

Those Travel Authorization Lines using a Payment Type of Employee (and hence reimbursable via payment), get defaulted a Reimbursement Code value of 'Prepaid', which means no payment is to be issued for the transaction at hand, while those Lines using a Prepaid Payment Type get defaulted the Reimbursement Code value of 'Reimbursable', for which a payment is to be issued by the company.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as an Expenses User
    2.- Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Payment Information > Payment Type
    3.- Open the existing Payment Types:
              a) Payment Type PPD, and ensure that the Reimbursement Recipient is set to Prepaid radio-button
              b) Payment Type CSH, and ensure that the Reimbursement Recipient is set to Employee radio-button
    4.- Navigate to the Employee Self-Service Fluid Homepage
    5.- Click on the Travel Authorizations Tile
    6.- Click on the Add Travel Authorizations button
    7.- Define the Travel Authorization Header required fields, (Such as Business Purpose, Description, Comments, Billing Type, From and To Travel fields, as well as From and To Date fields)
    8.- Manually add a new Line into the Travel Authorization, choose an Expense Type, and define the Description and Amount fields
    9.- Click on the Details button at the line level
    10.- In the Line Detail page, select the Payment Type PPD (For a Prepaid transaction)
    11.- Click on Done button
    12.- Manually add a second new Line into the Travel Authorization, choose a different Expense Type, and define the Description and Amount fields
    13.- Click on the Details button at the line level
    14.- In the Line Detail page, select the Payment Type CSH (For an Employee Payment transaction)
    15.- Click on Done button
    16.- Save the Travel Authorization at this stage
    17.- ISSUE: Query Record PS_EX_TAUTH_LINE, and check the value from Field REIMBURSEMENT_CD on both Travel Authorization Lines, to confirm they are incorrect:
              a) TA Line #1 using Payment Type ‘Prepaid Expenditures’ (EXPEND_MTHD = ‘PPD’) gets a Reimbursement Code of ‘R’ (REIMBURSEMENT_CD = ‘Reimbursable’)
              b) TA Line #2 using Payment Type ‘Cash’ (EXPEND_MTHD = ‘CSH’, which is Employee type of payment) gets a Reimbursement Code of ‘Prepaid’ (REIMBURSEMENT_CD = ‘P’)

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

As the system incorrectly stores the Reimbursement Code values at the Travel Authorization Line level, when the transaction gets defaulted into an Expense Report, the system will ignore those lines that should get reimbursed to the Employee, and instead set as eligible for payment those transaction line amounts that have already been prepaid. The Company will be issuing wrong payment amounts to the Employees, over/under-paying what is duly owed.

The system should set the Travel Authorization Line Reimbursable Code value (Record Field PS_EX_TAUTH_LINE.REIMBURSABLE_CD) in sync with the Payment Type value selected for each line (PS_EX_TAUTH_LINE.EXPEND_MTHD). Therefore, if Payment Type Prepaid is chosen, then the line will have the equivalent for Reimbursement Code ('P'), but if a Payment Type of Employee is selected, then its Reimbursement Code should be set to 'R'.

NOTE: In the images/screenshots/examples mentioned and/or 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.