EEX 9.2: EXC5600 Report Abends At Step EXC5600.GetData.InsTA1 With Unit Constrain Violation For Cash Advance With Multiple Lines

(Doc ID 2044190.1)

Last updated on MARCH 16, 2016

Applies to:

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

Symptoms

ISSUE:
The Cash Advance by Department BI Publisher Report (EXC5600) ends up in No Success with an Abend at Step EXC5600.GetData.InsTA1 if one of the processed Cash Advance transactions contains multiple lines, with the same or different Cash Advance Source.

REPLICATION STEPS:

   - Log into the FSCM Online Application as User ID VP1
   - Navigate to: Travel and Expenses > Manage Employee Information > Update Profile
   - Open the existing Expenses Profile for Employee ID KU0021
   - At the Organizational Data tab, make sure to place the below settings:
        - GL Unit = US001
        - Department ID = 61000
        - Supervisor ID = KU0005
   - Log into the FSCM Online Application as User ID EXA1
   - Navigate to: Employee Self-Service > Travel and Expense Center > Cash Advance > Create/Modify
   - Define Employee ID KU0021, and click on ADD button
   - Enter all needed values, making sure to create 2 lines for the Cash Advance, each using a different Cash Advance Source
   - Save the Cash Advance transaction (no need to submit at this stage)
   - Navigate to: Travel and Expenses > Manage Accounting > Print Reports > Cash Advances by Dept
   - Create a new Run Control ID with the below options selected:
        - GL Unit = US001
        - Department ID = 61000
   - Launch the Cash Advances by Department BI Publisher report (EXC5600)
   - The process ends in No Success with an Error Message

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:

   " SQL error. Stmt #: 1625  Error Position: 0  Return: 805 - ORA-00001: unique constraint (SYSADM.PS_EX_C5600_TA14) violated
     Failed SQL stmt: INSERT INTO PS_EX_C5600_TA14 (PROCESS_INSTANCE, ADVANCE_ID, EMPLID, NAME50, REFEREN CE_ID, BUSINESS_PURPOSE, DESCR, ADVANCE_SOURCE, ACCOUNT, DESCR1, PROJECT_ID, BUSINESS_UNIT_GL, DEPTI D, MONETARY_AMOUNT, CURRENCY_CD, COUNTER1, DEPTID_RC, DESCR_DEPTID, BUS_UNIT_RC, DESCR_BU, OPERATING _UNIT, PRODUCT, FUND_CODE, CLASS_FLD, PROGRAM_CODE, BUDGET_REF, AFFILIATE, AFFILIATE_INTRA1, AFFILIA TE_INTRA2, CHARTFIELD1, CHARTFIELD2, CHARTFIELD3) SELECT 19839, ADVANCE_ID, EMPLID, NAME, REFERENCE_ ID, BUSINESS_PURPOSE, DESCR, ADVANCE_SOURCE, ACCOUNT, DESCRSHORT, PROJECT_ID, BUSINESS_UNIT_GL, DEPT ID, MONETARY_AMOUNT, CURRENCY_CD, 0, '41000', 'Engineering', 'US001', 'US001 NEW YORK OPERATIONS', O
     Process 19839 ABENDED at Step EXC5600.GetData.InsTA1 (SQL) -- RC = 805 "

BUSINESS IMPACT:

The EXC5600 BI Publisher report (Cash Advance by Department) is unable to be properly generated by the system, and becomes useless for the Employees.

EXPECTED BEHAVIOR:

The Cash Advance by Department BI Publisher report (EXC5600) should be able to handle Cash Advance transactions containing multiple lines, with the same Cash Advance Source, or different ones.
 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms