Exception: ORA-31011: XML parsing failed When Selecting GT&C From LoV while Creating IGT Order From BWC or IGT Request From iProcurement. (Doc ID 2888951.1)

Last updated on OCTOBER 06, 2022

Applies to:

Symptoms

When attempting to select GT&C (General Terms & Conditions) from LoV while creating IGT (Intragovernmental Transactions) order, the following error occurs.

ERROR

You have encountered an unexpected error.

Exception Details.
 oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement: select DISTINCT POH.po_header_id,
  POH.igt_document_number,
  POH.clm_document_number,
  HOUTL.name org_name,
  revision_num
from po_headers_all POH,
hr_all_organization_units_tl HOUTL,
po_doc_style_headers PDSH,
po_headers_all_ext_vl ext,
PO_IGT_GTC_SUBGRP_V sub_group
where POH.org_id = :1
AND Nvl(pdsh.clm_flag,'N') = PO_CLM_CLO_UTIL.getCLMStatus
and HOUTL.organization_id = POH.org_id
and HOUTL.language = USERENV('LANG')
and POH.style_id = PDSH.style_id
AND PDSH.igt_flag = 'Y'
and poh.authorization_status = 'APPROVED'
AND poh.igt_status = 'REC'
AND sysdate between POH.start_date AND POH.end_date
AND poh.type_lookup_code = 'CONTRACT'
AND (poh.AGREEMENT_TYPE = 'M'
  OR (poh.AGREEMENT_TYPE = 'S'
  AND NOT EXISTS (SELECT 1
  FROM po_headers_all ord
WHERE ord.clm_source_document_id = poh.po_header_id )) )
AND poh.igt_document_number is not null
AND NVL(poh.order_originating_ind, 'R') = 'R'
AND ext.po_header_id = poh.po_header_id
AND ext.draft_id = -1
AND ext.attr_group_id = (SELECT ego.attr_group_id FROM ego_attr_groups_v ego WHERE ego.ATTR_GROUP_NAME = 'IGT_REQ_AG' AND ego.ATTR_GROUP_TYPE = 'PO_HEADER_EXT_ATTRS')
and sub_group.po_header_id (+) = ext.po_header_id
and sub_group.AGENCY_TYPE(+) = 'Requesting'
AND (PO_CORE_S3.has_group_securing_attributes = 'N'
OR (PO_CORE_S3.has_group_securing_attributes = 'Y'
AND (ext.C_EXT_ATTR9 IN (select column_value from table( po_core_s3.get_accessible_groups))
OR sub_group.GRP_ID IN ( select column_value from table( po_core_s3.get_accessible_groups) )) ) )
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java:912)
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.prepareException(OAPageErrorHandler.java:1232)
at oracle.apps.fnd.framework.webui.OAPageErrorHandler.processErrors(OAPageErrorHandler.java:1497)
at oracle.apps.fnd.framework.webui.OAPageBean.processFormRequest(OAPageBean.java:3811)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:2266)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:611)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:491)
..
## Detail 0 ##
java.sql.SQLException: ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 9
LPX-00216: invalid character 226 (0xE2)
ORA-06512: at "SYS.XMLTYPE", line 5
..


STEPS

1. Navigate to Purchasing superuser responsibility ->Buyer Work Center -> Orders -> IGT Orders.
2. Create TFMS Standard Purchase Orders.
3. From Headers page, Click on GT&C List of Values.
4. Reported exception occurs.

Changes

Cause

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