My Oracle Support Banner

EAR 9.2: The Credit Card Scheduler Process (AR_CRC_PRCS AE Program) Creates Deposit And Payment Without Bank Details (Doc ID 2484163.1)

Last updated on FEBRUARY 07, 2019

Applies to:

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

Symptoms


ISSUE:

A problem has been detected when AR Update AE Program (AR_UPDATE), places the Payment Group of a Credit Card Worksheet into Posting Errors, with Error Code ACTOB. The Accounting Entries cannot be corrected/deleted/modified, and the Credit Card Worksheet cannot be deleted either.

This has taken place because the External Bank Account being used for the Receivables Business Unit Definition was temporarily set into Inactive Status, and this has allowed the Credit Card Scheduler process (AR_CRC_PRCS AE Program) to generate a Credit Card Deposit, and Payment, without any Bank Information details. As a result, AR Update cannot find the Cash AR Accounting information to balance the Accounting Entries.

REPLICATION STEPS:

    1.- Define an External Bank Account for AR module, and add Collection Method of Credit Card
    2.- Configure a new Credit Card Profile
    3.- Set up at the Receivables Definition Business Unit level, the Credit Card Profile, as well as the Bank Code, and Bank Account
    4.- At the Customer set up level, ensure Payment Method is set to Credit Card, and the Credit Card Profile field is populated correctly
    5.- Define a new Contact Information linked to the Customer ID in question, and configure the Credit Card details accordingly
    6.- Create a new Pending Item Group for the Business Unit, and the Customer at hand, with a new Item transaction, placing the Post Action to Batch Standard
    7.- Launch AR Update to post the Pending Items
    8.- Proceed to set as Inactive the External Bank Account being used
    9.- Launch the Credit Card Scheduler (AR_CRC_PRCS AE Program) for the Receivables Business Unit in question
    10.- ISSUE: Confirm that a Credit Card type Deposit has been created, with Bank information being empty
    11.- ISSUE: Confirm that the related Payment to the Credit Card Deposit has also been generated, but with no Bank information either
    12.- Check the Credit Card Worksheet created for the Item previously created, and review the Credit Card Details
    13.- Proceed to manually approve and settle the Credit Card Payment by entering an Authorization Code
    14.- Set the Credit Card Worksheet in a Post Action of Batch Standard
    15.- Launch AR Update to process the Payments
    16.- ISSUE: Check in the Payment Posting Errors how the Payment Group has been placed in an Error Code of ACTOB

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.

ERROR MESSAGE:

    " Accounting Entries Out of Balance. (6035,4)
      Accounting Entries Out of Balance.
      Action: Verify accounting entry setup. For example, entry type, reason code definitions, item entry types, and automatic entry types. "

ACTUAL RESULT:

The Payment Groups affected cannot be corrected by modifying the Accounting Entries, and the Credit Card Worksheet is also grayed out. Outstanding Items cannot be paid, which affects Customer's Aging.

EXPECTED BEHAVIOR:

The Credit Card Scheduler process (AR_CRC_PRCS AE Program) should have detected that the External Bank Account was in Inactive Status, and should have not created any Credit Card deposit, Payment, nor Worksheet, and issued an informative Message instead, letting the User know the reason why no transaction was being created.

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.