Buyer Work Center - File Upload - IProcurement Catalog Upload Errors - "unexpected Purchasing Document Open Interface Error" (Doc ID 1907651.1)

Last updated on NOVEMBER 14, 2016

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

iProcurement Catalog Upload Errors - "unexpected Purchasing Document Open Interface error"

While uploading catalog items into GBPA in iProcurement or Buyer Work Center -  using Catalog Upload functionality, upload is failing with below error message,

Error:

icx.icatalog.loader.CatalogElementProcessorBase 2 truncate.begin
icx.icatalog.loader.CatalogElementProcessorBase 1 truncatedValue = ICX_CAT_UNKNOWN_PDOI_ERR
icx.icatalog.loader.CatalogElementProcessorBase 2 validateMaxLength.end
icx.icatalog.loader.CatalogElementProcessorBase 1 isValid = true
icx.icatalog.loader.CatalogElementProcessorBase 1 valLength with encoding = 24
icx.icatalog.loader.CatalogElementProcessorBase 1 encoding = UTF8
icx.icatalog.loader.CatalogElementProcessorBase 1 maxLength = 4000
icx.icatalog.loader.CatalogElementProcessorBase 1 value = ICX_CAT_UNKNOWN_PDOI_ERR
icx.icatalog.loader.CatalogElementProcessorBase 2 validateMaxLength.begin
icx.icatalog.loader.CatalogElementProcessorBase 1 validate = true
icx.icatalog.loader.CatalogElementProcessorBase 1 encoding = UTF8
icx.icatalog.loader.CatalogElementProcessorBase 1 truncateLength = 4000
icx.icatalog.loader.CatalogElementProcessorBase 1 value = ICX_CAT_UNKNOWN_PDOI_ERR
icx.icatalog.loader.CatalogElementProcessorBase 2 truncate.begin
icx.icatalog.loader.sql.CatalogLoaderSql 1 encoding = UTF8
icx.icatalog.loader.sql.CatalogLoaderSql 1 maxLength = 4000
icx.icatalog.loader.sql.CatalogLoaderSql 1 value = ICX_CAT_UNKNOWN_PDOI_ERR
icx.icatalog.loader.sql.CatalogLoaderSql 1 idx = 1
icx.icatalog.loader.sql.CatalogLoaderSql 2 setString.begin
icx.icatalog.loader.sql.CatalogLoaderSql 1 Session ID = 3164535
icx.icatalog.loader.sql.CatalogLoaderSql 1 System Failure Message = java.lang.Exception
at oracle.apps.icx.icatalog.loader.processors.DataRootElementProcessor.catalogProcess(DataRootElementProcessor.java:426)
at oracle.apps.icx.icatalog.loader.processors.DataRootElementProcessor.process(DataRootElementProcessor.java:79)
at oracle.apps.icx.icatalog.loader.handlers.DataRootLineHandler.endDocument(DataRootLineHandler.java:140)
at oracle.apps.icx.icatalog.loader.handlers.ItemLineHandler.endDocument(ItemLineHandler.java:499)
at oracle.apps.icx.icatalog.loader.parsers.DataTXTParser.parse(DataTXTParser.java:96)
at oracle.apps.icx.icatalog.loader.CatalogTXTLoaderBase.processJob(CatalogTXTLoaderBase.java:42)
at oracle.apps.icx.icatalog.loader.CatalogLoaderBase.service(CatalogLoaderBase.java:141)
at oracle.apps.icx.icatalog.loader.LoadRequest.start(LoadRequest.java:151)
at oracle.apps.icx.icatalog.loader.LoadRequest.runProgram(LoadRequest.java:49)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)

 

Start of subprogram.
ORA-22160: element at index [1] does not exist in Package po.plsql.PO_PDOI_PVT. Procedure start_process.110;SQLERRM = ORA-22160: element at index [1] does not exist
End of subprogram.
Start of subprogram.
ORA-22160: element at index [1] does not exist in Package po.plsql.PO_PDOI_MAINPROC_PVT. Procedure process.30;SQLERRM = ORA-22160: element at index [1] does not exist
ORA-22160: element at index [1] does not exist in Package po.plsql.PO_PDOI_MAINPROC_PVT. Procedure process_lines.20;SQLERRM = ORA-22160: element at index [1] does not exist
ORA-22160: element at index [1] does not exist in Package po.plsql.PO_PDOI_MAINPROC_PVT. Procedure process_lines_add.40;SQLERRM = ORA-22160: element at index [1] does not exist
ORA-22160: element at index [1] does not exist in Package po.plsql.PO_PDOI_LINE_PROCESS_PVT. Procedure default_lines.100;SQLERRM = ORA-22160: element at index [1] does not exist
End of subprogram.
p_ship_to_org_id_tbl(8) = 101
p_ship_to_org_id_tbl(7) = 101


Replication Steps:
The issue can be reproduced at will with the following steps:
1. Upload Lines via the Buyer Work Center - BWC - using the File Upload option
2. Find that the lines are not uploaded - and there is no error message given when using - View Upload Errors

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms