EAR 9.2: Automatic Maintenance Program Abends at Step AR_AUTOMNT.ALOG_MT.TAO_INSM When Audit Logging Is Enabled for Event Auto Maintenance and Item With Multiple Lines Is Processed (Doc ID 2973594.1)

Last updated on OCTOBER 02, 2023

Applies to:

Symptoms

The Automatic Maintenance process (AR_AUTOMNT AE Program) abends at Step AR_AUTOMNT.ALOG_MT.TAO_INSM with a unique constrain violation Error Message when trying to insert into Record PS_AR_ITEM_TAOx.

This takes place when there is a Credit Item to be matched against a Debit Item with multiple Lines, and Audit Logging has been enabled for AR Item Auto Maintenance event.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as User ID VP1
    2.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Audit Logging > Enable Audit Logging
    3.- Open Application Name Accounts Receivable
    4.- For the Document Name AR Item, select all available Events (Including Auto Maintenance)
    5.- Navigate to: Set Up Financials/Supply Chain > Product Related > Receivables > Credit/Collections > Automatic Maintenance Methods
    6.- Create a new Automatic Maintenance Method that matches Credit and Debit amounts from Items by Document ID values, and anything remaining within the tolerance, to be written-off
    7.- Navigate to: Set Up Financials/Supply Chain > Business Unit Related > Receivables > Receivables Options
    8.- Open the Set ID SHARE
    9.- Go to the General 2 tab
    10.- Define there the new Automatic Maintenance Method just created
    11.- Navigate to: Accounts Receivable > Pending Items > Online Items > Online Item Entry Group
    12.- Create a first Pending Item Group under Business Unit US001 with a Credit Invoice, (ID CR_ITEM-01), for an amount of say -15,000.00 USD, and place on the Document ID field the value DB-ITEM-01
    13.- Set the Pending Item Group to a Post Action of Batch Standard
    14.- Create a second Pending Item Group under Business Unit US001, this time for a Debit Item, (ID DB-ITEM-01), and divide it into Line #1 with amount 10,000.00 USD, and Line #2 for amount 4,999.90 USD. Place on the Document ID fields for both rows the value of the prior Credit Item (ID CR-ITEM-01)
    15.- Set the second Pending Item Group also to a Post Action of Batch Standard
    16.- Navigate to: Accounts Receivable > Receivables Update > Request Receivables Update
    17.- Create a new Run Control ID for Business Unit US001, and the option of 'Pending Items'
    18.- Launch, and confirm, that AR Update completes successfully
    19.- Navigate to: Accounts Receivable > Customer Accounts > Item Information > View/Update Item Details
    20.- Search for the 3 Items created, open them, and confirm that in Detail 2 tab, the Document ID field is properly populated
              a) Item ID CR-ITEM-01 has Document ID DB-ITEM-01
              b) Item ID DB-ITEM-01 Line Number 1 has Document ID CR-ITEM-01
              c) Item ID DB-ITEM-01 Line Number 2 has Document ID CR-ITEM-01
    21.- Navigate to: Accounts Receivable > Receivables Maintenance > Automatic Maintenance > Request Automatic Maintenance
    22.- Create a new Run Control ID with the below settings:
              a) Run Control ID = OSS
              a) Override Method = (The Automatic Maintenance Method ID previously created)
              a) Anchor BU = US001
              a) Last Activity <= Today
              a) Business Unit = US001
              a) Process Frequency = Always
    23.- Launch the AR_AUTOMNT AE Program
    24.- Navigate to: PeopleTools > Process Scheduler > Process Monitor
    25.- PROBLEM: Find the AR_AUTOMNT AE Program Process Instance in No Success

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.

ERROR MESSAGE:

The Automatic Maintenance process (AR_AUTOMNT AE Program), leaving locked and corrupted both Credit and Debit Items, preventing from being further processed, and getting balanced out for closure, missing as well all needed Accounting Entries to interface within FIN General Ledger module.

Instead, the program should be able to handle the scenario at hand, balancing the Debit against the Credit Items, and write-off the small amount left over, closing both transactions, and generating the needed Accounting Entries to post.

Changes

Cause

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