EEX 9.0/9.1: ACCOUNTING_DT Is Blank In PS_EX_SHEET_PYMNT And PS_EX_ACCTG_LINE Records For Payroll Reversals Entries After Running Cancel Payments Process (Doc ID 1480180.1)

Last updated on MARCH 16, 2016

Applies to:

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

Symptoms

ISSUE:

Having performed the integration from PeopleSoft Enterprise FSCM Expenses module and PeopleSoft Enterprise HRMS North American Payroll systems, so any Expenses payments are satisfied by Payroll, should a generated Paycheck be reversed/adjusted in Payroll systems, the response from FSCM Expenses side is not the expected one. In such scenarios, the Accounting Date field in the PS_EX_SHEET_PYMNT and PS_EX_ACCTG_LINE is blank when they should be populated for this Payment Cancellation.

In PS_EX_SHEET_PYMNT, the 2 new rows the Cancel Payments process creates, stating that the Payment has been cancelled (PYMNT_SELCT_STATUS equals 'X' - Cancelled), and that a new row is available to be picked up and Published to Payroll again (PYMNT_SELCT_STATUS equals 'N' - Ready for Selection), have the Accounting Date  (ACCOUNTING_DT) field blank.

REPLICATION STEPS:

  - Configure the necessary setup to allow FSCM Expenses integration with the HRMS North American Payroll functionality
  - Create and submit a new Expense Report
  - Approve the submitted Expense Report
  - Run the Stage Payments and Post Liabilities processes against the Expense Report
  - Run the Publish To Payroll process for the Expense Report
  - Make sure that the interface FSCM EX - HRMS NA Payroll is successful for both Service Operations PAYMENT_EXPENSES_REQUEST and PAYMENT_EXPENSES_ACKNOWLEDGE
  - In HRMS Database, configure a new Pay Run, and its Calendar, run all necessary steps to create a Paycheck successfully, and interface to GL
  - In HRMS, make sure the PS_PAY_ISS_STG_PUB record is properly populated, and run the Payment Expenses Notification process
  - Make sure that the interface HRMS NA Payroll - FSCM Expenses is successful for Service Operations PAYMENT_EXPENSES_ISSUE
  - Run the Post Payments process for the Expense Report
  - Log once again into the HRMS Database, and reverse the paycheck just created
  - Create a new Pay Run, its related Calendar, and run all necessary steps to Payroll Calculate and Confirm, and finally the integration to GL
  - In HRMS, make sure the PS_PAY_ISS_STG_PUB record is properly populated, and run the Payment Expenses Notification process
  - Make sure that the interface HRMS NA Payroll - FSCM Expenses is successful for Service Operations PAYMENT_EXPENSES_ISSUE
  - Note that the value stored in Field EX_PYRL_STATUS from Record PS_EX_SHEET_PYMNT is properly having a value of 'F' (Confirmed by Payroll)
  - Launch the Cancel Payments process against that Expense Report
  - Note that the ACCOUNTING_DT Field in PS_EX_SHEET_PYMNT record is empty for the affected Expense Report on the rows where PYMNT_SELCT_STATUS equals 'X' (Cancelled) and 'N' (Ready for selection)
  - Note that the EXCANCEL Accounting Entries in PS_EX_ACCTG_LINE for the Payment Cancellation rows have ACCOUNTING_DT Field blank as well on the affected Expense Report

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

BUSINESS IMPACT:

The problems in the defective codeline are causing the following impacts:

    a.- The Accounting Date field is blank in the PS_EX_SHEET_PYMNT record, which will complicate things when trying to run a new Payment Post once the Expense Report gets paid again.
    b.- The Accounting Date field is blank on the EXCANCEL Accounting Entries in PS_EX_ACCTG_LINE record, which causes problems when trying to interface all that information into the General Ledger via Journal Generator

EXPECTED BEHAVIOR:

The Payments that got reversed in HMRS NA Payroll systems should be accounted as such in the FSCM Expenses module, it is expected that the ACCOUNTING_DT field in populated at all times with the proper value in both PS_EX_SHEET_PYMNT and PS_EX_ACCTG_LINE records for the affected Expense Report transaction.

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