XLA-95103

Unable to Validate Invoice due to CANT FUNDS CHECK hold and XLA-95103 An internal error occurred in Routine get_sla_notupgraded_flag [ID 464776.1]

Applies to:

Oracle Payables - Version 12.0.0 to 12.0.6 [Release 12.0]
Information in this document applies to any platform.
APXINWKB - Invoice Workbench
APPRVL - Invoice Validation

Symptoms

Join our growing Oracle Payables Community and learn from your peers and Oracle on how to address your unique issues in AP.

When attempting to validate the invoice the following error occurs:

    === === ===
    XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
    An internal error has occurred in the program XLA_00200_AAD_S_000011_BC_PKG.EventClass_105.
    User-Defined Exception.
    Error in get_sla_notupgraded_flag function
    === === ===

CANT FUNDS CHECK hold is placed for the involved invoice

Changes

Upgraded to R12.0.3 using Patch 6141000- Oracle E-Business Suite 12.0.3 Release Update Pack (RUP3)

Cause

Issue discussed in Bug: BUG 6523742 - CANNOT FUNDS CHECK AP, PO, IPROC and base bug 6415646 - R12 AFTER APPLY PREPAYMENT, VALIDATE INVOICE, GETTING CANT FUNDS CHECK HOLD.

The AP fix was created under Bug 6504975 - REMOVE HARDCODING OF 1109 ENCUMBRANCE_TYPE_ID FROM VIEWS and the fixed file versions were:

ap patch/115/xdf ap_extract_invoice_dtls_bc_v.xdf 120.3.12000000.4
ap patch/115/xdf ap_invoice_extract_details_v.xdf 120.6.12000000.6
ap patch/115/xdf ap_prepayapp_extract_details_v.xdf 120.5.12000000.4
ap patch/115/xdf ap_prepayapp_extract_dtls_bc_v.xdf 120.2.12000000.3

Solution

To implement the solution, please execute the following steps:

1) Apply Patch 6504975:R12.AP.A - REMOVE HARDCODING OF 1109 ENCUMBRANCE_TYPE_ID FROM VIEWS to upgrade the following file versions:

ap patch/115/xdf ap_extract_invoice_dtls_bc_v.xdf version 120.3.12000000.4
ap patch/115/xdf ap_invoice_extract_details_v.xdf version 120.6.12000000.6
ap patch/115/xdf ap_prepayapp_extract_details_v.xdf version 120.5.12000000.4
ap patch/115/xdf ap_prepayapp_extract_dtls_bc_v.xdf version 120.2.12000000.3

2) Retest the issue.

Workaround:
The profile option PSA: R12 Upgrade Date should be changed to the new format: MM/DD/YYYY HH24:MI:SS

The code in PSA_BC_XLA_PVT is expecting the correct format.
These changes were done recently for NLS compliance.
The existing customers should therefore manually change the format of the profile.

Please set the profile value in the format: MM/DD/YYYY HH24:MI:SS to know the date run the following:
select Fnd_Profile.Value_Wnps('PSA_R12_UPGRADE_DATE') from dual;

If you are not able update the profile then in application developer query for the profile option
and enable for update and then change the format accordingly.