Publish Extensible Flexfield Attributes ESS process Fails With: No Segments found for Context_Code :XXXXXXX and Column_Name :XXXXXXX (Doc ID 2298167.1)

Last updated on SEPTEMBER 05, 2017

Applies to:

Oracle Fusion Order Management Cloud Service - Version 11.1.11.1.0 and later
Oracle Fusion Distributed Order Orchestration - Version 11.1.11.1.0 and later
Information in this document applies to any platform.
***KM Review - Aug 2017 - Checked for Relevance***

Symptoms

Changes have been made to Order Management Extensible FlexFields (EFF) - A context has been deleted.

The issue can be reproduced by executing the following steps:

1. Amend an Order Management Extensible Flexfield by deleting a deployed Context
2. Deploy the EFF - no errors are reported
3. Schedule New Process - Publish Extensible Flexfield Attributes
4. The process fails
5. Support has checked the ESS process log files and this shows an error:

<Aug 23, 2017, 3:19:16,16 PM UTC> <Error> <oracle.as.ess> <ESS-07004> <Execution error for request 29918. Reason: ESS-07033 Job logic indicated a system error occurred while executing an asynchronous java job for request 29918. Job error is: <env:Body xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
 <orafault:Fault xmlns:orafault="http://xmlns.oracle.com/oracleas/schema/oracle-fault-11_0">
   <faultcode>env:Server</faultcode>
   <faultstring>JBO-29115 Unable to construct the error message due to error java.lang.IllegalArgumentException: can't parse argument number: TASK_INSTANCE_ID. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is JBO-. : No Segments found for Context_Code :DiagnosticLabsAdditionalInformation and Column_Name :ATTRIBUTE_CHAR1</faultstring>
   <detail>
     <tns:ServiceErrorMessage xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <tns:code/>
       <tns:message>JBO-29115 Unable to construct the error message due to error java.lang.IllegalArgumentException: can't parse argument number: TASK_INSTANCE_ID. Use the exception stack trace and error code to investigate.>

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