EAP: SEPA Xml's Are Created with Invalid Characters for Special Characters After Upgrading to PUM 24 (Doc ID 2389488.1)

Last updated on SEPTEMBER 28, 2022

Applies to:

Goal

SEPA xml's are not created correct, using invalid characters after upgrade to PUM 24 on a non-unicode database where SEPA_CHAR_CONV is set to "N" in the setup of the bank integration layout page in Administer Bank Integration..

Customer analysis:

Based on customer's testing and research they have found that the issue with special characters is caused by a change in de PMT_DISPATCH application engine. Customer is using the standard delivered formats SEPA_CT_03, SEPA_DD_02 and a custom defined format SEPA_HM_03. In the PeopleCode in step PMT_DISPATCH.FRMT100.Step3.OnExecute in the "Output to a File" code section Oracle changed in the evaluation "Evaluate PMT_DISP_AET.FORMAT_ID.Value" the When-Other value for the parameter &format from True to False. It seems that this was changed due to Bug 24757749 from PUM image 22. This leads to the fact that for customer used formats the parameter &format resolves to False which causes that the XML files are no longer created in UTF8.

The bug fix from Oracle for <Bug 24757749> is right (When-Other should set False), but this created in the customer opinion another bug that now creates in proper formatted SEPA_CT_03 and SEPA_DD_02 files.
The solution for the newly created bug seems to be simple as only the SEPA_CT_03 and SEPA_DD_02 need to be specified in the When-list (like already done for SEPA_CT and SEPA_DD). HOWEVER as PeopleSoft offers functionality to functionally define custom formats (as they did with SEPA_HM_03) in the customer's opinion the real fix from Oracle should make the switch between UTF8 and default character set controllable through functional configuration instead of this hard-coded format evaluation list.

Solution

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