My Oracle Support Banner

CM: Financial Gateway Payment File Format Issues (Doc ID 2195188.1)

Last updated on OCTOBER 01, 2018

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

 
ISSUE:
 
 
The Debtor information is populated as empty tags for payment file using Financial Gateway as stated below when multiple vouchers are processed for payments in a Pay cycle having different GLBUs for each voucher using Layout code SEPA_CT_03.


When these Vouchers are individual processed, the information is getting populated correctly.


For example:
Voucher 1 (1 Voucher Line, 1 Distrib Line) : BU: 30007, GLBU:30007, Bank Cd:BOANL, Bank Account Key: 0001
Voucher 2 (1 Voucher Line, 1 Distrib Line): BU:30237, GLBU:30237, Bank Cd:BOANL, Bank Account Key: 0002


These two vouchers are picked by PayCycle and Dispatched. One single Payment file is generated with Debtor information populated for Voucher 1 but missing in Voucher 2.
When Voucher 2 alone is populated by PayCycle and Dispatched the Debtor information is getting populated.
We believe this issue is due to the code: AE:PMT_DISPATCH -> Section:POPDTLRS -> Step: Step02A->Action:SQL


How can we get the Debtor information populated for both the vouchers, when a single payment file needs to be generated to be dispatched to the bank?


Voucher 1 (Debtor Information)
  
  Convergys CM Netherlands BV
  
  ADDR
  1101 CH
  Amsterdam
  NL
  Haarlerbergpark
  Haarlerbergweg 13-19
  
  NL
  


Voucher 2(Debtor Information - Empty tags)
 
  
  
  ADDR
  
  
 STEPS:
-----------
1. Banking setup for the bank used is Financial Gateway with Layout code SEPA_CT_03.
2. Create 2 vouchers for different AP business unit with 2 different suppliers
3. Run paycycle
4. Dispatch the file to FG
5. View the file.

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
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.