My Oracle Support Banner

EBI 9.2: The Pre-Process & Finalization Program Abends at Step BIIVC000.MAINPROC.WRITELOG (PeopleCode) With Unique Constraint Violation on Table PS_BI_LINE_ERR_TBL if Invoice Contains Multiple Inactive Accounting ChartField Values (Doc ID 3063057.1)

Last updated on DECEMBER 19, 2024

Applies to:

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

Symptoms

It has been detected that the Bill Finalization Process (BIIVC000 AE Program) abends at Step BIIVC000.MAINPROC.WRITELOG (PeopleCode) with a unique constraint violation on Record PS_BI_LINE_ERR_TBL when trying to insert multiple audit errors (BI Error Status 5111 - Inactive ChartField has Value) involving inactive ChartField values contained on the Accounting Revenue Distribution of a Billing Invoice transaction being finalized.

REPLICATION STEPS:

    1.- Log into the FSCM 9.2 Online Application as a Billing User.
    2.- Navigate to: Billing > Maintain Bills > Standard Billing
    3.- Create a new FIN Billing Invoice transaction with the below sample values at the Header - Info 1 tab:
           - Business Unit = US001
           - Bill Type Identifier = MSC
           - Customer ID = USA01
           - Invoice Date = Today's Date
           - Accounting Date = Today's Date
           - Payment Method = Check
    4.- Go to the Line - Info 1 tab, and fill in the below other values:
           - Quantity = 1
           - Unit of Measure = EA
           - Unit Price = 100
    5.- Go to the Accounting Revenue Distribution page, and fill in the following Accounting ChartField values:
           - Account = 100003
           - Operating Unit = CALIF
           - Department ID = 27000
    6.- Save the changes of the Invoice.
    7.- Go back to the Header - Info 1 tab, and change the Bill Status from NEW to RDY.
    8.- Save the changes.
    9.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Design ChartFields > Define Values > Define ChartField Values
    10.- Go to the Department ChartField, and under Set ID SHARE, open Department ID 27000. Then, add a new Effective Date row with 01-01-2024, with a Status of Inactive. Save the changes.
    11.- Navigate to: Set Up Financials/Supply Chain > Common Definitions > Design ChartFields > Define Values > Define ChartField Values
    12.- Go to the Operating Unit ChartField, and under Set ID SHARE, open Operating Unit CALIF. Then, add a new Effective Date row with 01-01-2024, with a Status of Inactive. Save the changes.
    13.- Navigate to: Billing > Generate Invoices > Non-Consolidated > Finalize and Print Invoices
    14.- Create a new Run Control ID for Business Unit US001, and the Invoice ID recently created.
    15.- Click on RUN button, select the BIIVC000 AE Program, and click on OK button.
    16.- Navigate to: PeopleTools > Process Scheduler > Process Monitor
    17.- PROBLEM: Confirm that the BIIVC000 AE Program Process Instance just launched has completed in No Success, with an Error Message obtained.

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 problem.

ERROR MESSAGE:

    " SQL error. Function:  SQLExec

        Error Position:  0

        Return:  805 - ORA-00001: unique constraint (EMDBO.PS_BI_LINE_ERR_TBL) violated

        Statement:  INSERT INTO PS_BI_LINE_ERR_TBL (BUSINESS_UNIT, INVOICE, LINE_SEQ_NUM, ERROR_STATUS_BI, PROCESS_INSTANCE, PRCSTYPE, PRCSNAME) VALUES(:1, :2, :3, :4, :5, :6, :7)

       Original Statement:  INSERT INTO PS_BI_LINE_ERR_TBL (BUSINESS_UNIT, INVOICE, LINE_SEQ_NUM, ERROR_STATUS_BI, PROCESS_INSTANCE, PRCSTYPE, PRCSNAME) VALUES(:1, :2, :3, :4, :5, :6, :7)

          AePcdExecutePeopleCode [191] Exception logged: RC=100.

          GetNextStateRecord [68] Exception logged: RC=3.

      SQL error in Exec. (2,280) BIIVC000.MAINPROC.GBL.default.1900-01-01.WRITELOG.OnExecute  PCPC:4063  Statement:33

          DoStepActions [2148] Exception logged: RC=100.

      Process 297783 ABENDED at Step BIIVC000.MAINPROC.WRITELOG (PeopleCode) -- RC = 8 (108,524) "


Due to this abend, the FIN Billing Invoice transactions affected cannot be finalized, and further processed into generating the needed Accounting Entries, printing, and interfaced into FIN Receivables module. This is preventing the creation of open items in the Customer's Account.

The Bill Finalization Process (BIIVC000 AE Program) should not abend in such a manner, and instead, complete with success, or with a warning message, stating that Billing Error Type 5111 instances were detected, that need correction.

NOTE: In the images/screenshots/examples mentioned and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

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.