G Error Handling

This appendix provides an error handling mechanism to resolve the errors that occur in Agile Product Lifecycle Management (PLM) Integration Pack for Oracle E-Business Suite: Design to Release.

This appendix includes the following section:

• Error Messages and Solutions

G.1 Error Messages and Solutions

Table G-1 shows solutions to error messages that you may encounter.

Table G-1 Error Messages and Solutions

ID	Flow	Error Message	AIA/Agile/Ebiz Business/System	Action to resolve
1	Sync Item and then Create ECO for that Item and add Revision as A and Submit it	You must enter an item revision for revised item <<PartName>> that is greater than or equal to the current revision., Entity Id: RI Message Text: You must enter revisions and effectivity dates in ascending order Cause: A lower revision with a later effectivity date than your revision already exists. Action: Enter an effectivity date for your revision that is later than all other effectivity dates. Cause: A higher revision with an earlier effectivity date than your revision already exists. Action: Enter a revision that is higher than all other revisions.	AIA Business	Revision must be greater than I, since sync Item sync's with INT Rev in Ebiz.
2	Create ECO / Validate ECO	FATAL_ERROR::BINDING_FAULT:: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ValidateEngineeringChangeOrderService' failed due to: Set object error. Error binding the value of parameter P_ECO_OBJ_LIST. An error occurred when binding the value of parameter P_ECO_OBJ_LIST in the apps.INV_EBI_CHANGE_ORDER_PUB.VALIDATE_CHANGE_ORDER_LIST API. Cause: java.sql.SQLException: Inserted value too large for column: "NOT_FOUND"	AIA Business	Usually this error comes when proper site details are not updated in AGILE_SITE_TARGET_MAPPING DVM in AIA. You must make sure that all sites details are present in AGILE_SITE_TARGET_MAPPING DVM.
		Check to ensure that the parameter is a valid IN or IN/OUT parameter of the API. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-17072" to your deployment descriptor (i.e. WebLogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
3	Validate / Create ECO Submit/Release ECO adding child Organization in Site tab without adding Master Organization.	Org Code: <<ChildOrg>> ECO Name: <<ECOName>> Err Msg: Entity Id: ITEM Message Text: This Child Item has no Master Item record in MTL_SYSTEM_ITEMS.	AIA Business	Whenever you add child Organization, make sure to add the Master Organization in the Site tab.
4	Create ECO on BOM assembly and add a blank row in the redlining BOM from Java client and Submit ECO	A Blank row exists in the BOM	AIA Business	Remove any blank row in redlining BOM tab and resubmit the ECO
5	Validate/ Process ECO - Same ECO already exist in EBiz	Org Code: <<Org Code>> ECO Name: <<ECOName>> Err Msg: Entity Id: ECO Message Text: The ECO <<ECOName>> you are trying to create already exists in the organization <<Org Code>>., Entity Id: RI Message Text: This record received an error status since a severe error occured in the ECO <<ECOName>> while checking if the ECO exists., Entity Id: BO Message Text: An error occured while processing business object <<ECOName>> in organization <<Org Code>>. Please check the data in this business object and re-run the import process	AIA Business	Modify the ECO name and resubmit/ re-release them.
6	BOM components having only child organization- Submit/Release ECO	Org Code: <<ChildOrg>> ECO Name: <<ECOName>> Err Msg: Entity Id: ITEM Message Text: This Child Item has no Master Item record in MTL_SYSTEM_ITEMS.	AIA Business	Add the Master Organization also in the child component and Resubmit/release it.
7	Create/Validate ECO	Org Code: <<Org Name>> ECO Name: <<ECOName>> Err Msg: Entity Id: ECO Message Text: The ECO <<ECOName>> you are trying to create already exists in the organization <<Org Name>>., Entity Id: RI Message Text: This record received an error status since a severe error occured in the ECO <<ECOName>> while checking if the ECO exists., Entity Id: BO Message Text: An error occured while processing business object <<ECOName>> in organization <<Org Name>>. Please check the data in this business object and re-run the import process.	AIA Business	ECO already exist in Ebiz.
8	Any flow	ORAMED-01001:[Error in assign operation] Error occurred while assigning to target "$out.property.jca.apps.Username" using expression "$in.property.jca.apps.Username". Possible Fix:Check if source message has right values or source expression is valid. Cause: ORAMED-01008:[Property not found in message][Property "jca.apps.Username" not found in "in" message. Possible Fix:Check source and target expression for valid property name otherwise Contact Oracle Support Services	AIA System	This is due to mis-configuration for a cluster. To resolve: a. Login to the Weblogic console and go to Environment >Clusters>soa_cluster>Configuration>HTTP. b. Set Frontend Host and HTTP Port to your Proxy host and port. Leave HTTPS port empty. c. Save and restart the cluster.
9	Any flow	Exception occurred during invocation of JCA binding": "JCA Binding execute of Reference operation 'GetEngineeringChangeOrderService' failed due to: Parse struct conversion error. An error occurred while parsing XML representing a Java struct. Unable to convert the XSD element P_CHANGE_LST_ITEM whose user defined type is INV_EBI_CHANGE_ID_OBJ to a Java struct. Cause: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 301 seconds BEA1-.	AIA System	This is due to communication lag between AIA and Ebiz. Increase timeout can mitigate this issue. To resolve: a. Log in to the WebLogic console, go to Deployments, expand soa-infra in the table. Find BPELActivityManagerBean under EJBs, then click it. b. On the Configuration tab, set Transaction Timeout to a larger number, like 3600, then save. c. A message may display asking you to create a new Plan. Accept the default settings and save. If you are configuring a cluster, the Plan.xml file must be saved in the $SHARED_LOCATION. d. Repeat step b for BPELDelivery Bean, BPELEngineBean, BPELFinderBean, BPELInstanceManagerBean, BPELProcessManagerBean, and BPELServerManagerBean. e. Restart managed servers.
10	NPR	Error message SOAP Fault from server: request-response conversation has timed out for component=default/SyncItemListAgileReqABCS!1.0*soa_3b7dc357-c617-454c-8b28-8f0fc4bf9245/SyncItemListAgileReqABCS, flowId=260016 Please see the server log to find more detail regarding exact cause of the failure.	AIA System	This is due to communication lag between AIA and Ebiz. Increase timeout can mitigate this issue. To resolve: a. Log in to the WebLogic console, go to Services > Data Sources > SOADataSource. b. On the Configuration > Transaction tab, check Set XA Transaction Timeout' and set 'XA Transaction Timeout' to a larger value, like 3600. Save. c. Log in to EM, right-click SOA > soa_infra. Select SOA Administration > BPEL properties. Go to more BPEL Configuration Properties. Change SyncMaxWaitTime to a larger value, like 1200, then apply. d. Restart AIA.