My Oracle Support Banner

R12: AP/IBY: Transaction Code Missing in Payment Format Output Using a NACHA Template. Instead of 622 or 623 the Output Shows Just the 6 with the Next Two Characters Blank. (Doc ID 2960599.1)

Last updated on JULY 10, 2023

Applies to:

Oracle Payments - Version 12.0.0 and later
Oracle Payables - Version 12.0.0 and later
Information in this document applies to any platform.

Symptoms

When generating a NACHA (National Automated Clearing House Association) file one of the payments is missing the Transaction Code (normally 22 or 23).
The transaction code is the 2nd and 3rd character on the "6" record.

A file output with a missing transaction code may looks like:

101xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
522xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
623xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
623xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
623xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
6  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
623xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
822xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
900xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

To submit a Payment Process Request (PPR):

  1. From a Payables Responsibility go to Payments -> Entry -> Payments Manager
  2. Click on "Submit a Single Payment Process Request"
  3. Fill out the information and click submit

To add an account type to a supplier bank account:

  1. From a Payables Responsibility go to Suppliers -> Entry
  2. Pull up the supplier
  3. Click on "Banking Details"
  4. Query up the site
  5. Click on the update icon on the bank account
  6. Click on "Show Bank Account Details"
  7. Populate the "Account Type" field
  8. Click apply

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


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