My Oracle Support Banner

EAP 9.2: The 1099 Report Process Abends At Step AP_APY1099.BD200.Step130 With A Unique Constrain Violation On Record PS_WTHD_TO_SND_DTL (Doc ID 2502160.1)

Last updated on JANUARY 15, 2020

Applies to:

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

Symptoms

ISSUE:

When running the 1099 PSJob (AP_1099) for the 2018 Fiscal Year, after having applied the 1099 2018 Update, the process goes to No Success at Step AP_APY1099.BD200.Step130 (SQL) due to a unique constrain violation when inserting transaction data into Table PS_WTHD_TO_SND_DTL.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a Payables User
    2.- Navigate to: Suppliers > 1099/Global Withholding > 1099 Reports > Withhold 1099 Report Job
    3.- Create a new Run Control ID
    4.- Launch the AP_1099 PSJob
    5.- Confirm that AP_APY1099 AE Program completed in No Success

ERROR MESSAGE:

    " File: /vob/peopletools/src/psappeng/aedebug.hSQL error. Stmt #: 1725  Error Position: 0  Return: 805 - ORA-00001: unique constraint (SYSADM.PS_WTHD_TO_SND_DTL) violated
      Failed SQL stmt: INSERT INTO PS_WTHD_TO_SND_DTL (...
      Process 123456789 ABENDED at Step AP_APY1099.BD200.Step130 (SQL) -- RC = 805 (108,524) "

ACTUAL RESULTS:

The 1099 Tax Season completes by Thursday January 31st 2019, and the Copy B report needs to be provided to the IRS Tax Authorities, with this abend, the report cannot be submitted.

EXPECTED BEHAVIOR:

The delivered 1099 process (AP_APY1099 AE Program) should be able to handle all Supplier's scenarios, and generate the proper report information without any abends.

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


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