My Oracle Support Banner

Endeca : Icx-Iproc Full Load Fails With Invalid Xml - Record Rejected Requisition Line (Doc ID 2233895.1)

Last updated on FEBRUARY 13, 2019

Applies to:

Oracle iProcurement - Version 12.1.3.4 and later
Information in this document applies to any platform.

Symptoms

Version 12.1.3 iProcurement / Endeca

Install Information Discovery 12.1v7 (12,1,3,7)
Run full load for icx-iproc sandbox and it fails with "Invalid XML"

po_lines_requisitions_all.item_description contains character that XML fails.

The values below are generic fictitious values and do not reflect any real case

ERROR

2017-02-02 11:11:11,923 ERROR 201111 [SocketReader] Received error message
from server:
Record rejected: spec REQUISITION_LINE_ID="11111111"
Invalid XML Found: 006 Delivery [4]=,-
2017-02-02 11:11:11,924
ERROR 201111 [SocketReader] Received error message from server: Record
rejected:
spec REQUISITION_LINE_ID="1111111" Invalid XML Found: 005 (CAR053) SCR
<Text Description before strange characters><Strange characters such as &#23;&#11;&#24;&#2;&#17;&#3;&#26;&#25;&#2;&#15;><Additional Text After Strange Characters>

ERROR 201111 [WatchDog_201111] Graph element
[Bulk Add/Replace Records:BULK_ADD_REPLACE_RECORDS_FOR_REQS] failed with
unknown cause.
org.jetel.exception.JetelRuntimeException: Graph element

STEPS

-------------
  Run FullLoadConfig.grf on icx-iproc

Verified DATA :
-------------
po_requisition_lines_all.item_description contains characters in the item description that causes the XML to fail.

* Similar issue is fixed for Po-Proc fixed in <Bug 25473190>.

Fix is needed for icx-iproc

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