E Troubleshooting

This appendix describes common troubleshooting issues and solutions pertaining to Engineering Change Orders (ECOs), installation, Queue Management, Agile, and SAP.

E.1 Engineering Change Order Issues

These are the common ECO issues and solutions:

Issue: In ECO forward flow, after the ECO is processed successfully, the transfer status attribute (flex) in the ECO in Agile is not getting updated.

Solution: Check which flexfield attribute has been enabled corresponding to the change. Ensure that the same attribute has been configured in the AIAConfigurationProperties.xml for that property.

Issue: For the Item Cost Update update flows, the attributes in Agile are not getting updated.

Solution: Check to see if the Multisite Enabled property is set to True or False. Based on this given value, verify that the Cost attributes in AIAConfigurationProperties.xml are correctly set.

For more information about item update, see, Chapter 4, "Process Integration for Item Attribute Update".

E.2 Installation Issues

These are the common installation issues and solutions:

Issue: While installing the Oracle Application Integration Architecture Foundation Pack (Oracle AIA FP) in the Linux box, the deployment of configurations and deploying the pre-built integration did not succeed due to the Service-Oriented Architecture (SOA) server being unable to restart itself automatically using the deployment script given in the Oracle AIA FP.

Solution: To resolve this installation issue:

1. Stop SOA server.
2. Restart the SOA server from this location:

$Middleware_Home\user_projects\domains\soa_domain\bin>.\startManagedWeblogic.sh soa_server1
3. Click Retry in the configuration wizard.

E.3 Queue Management Issues

These are the common queue issue and solutions:

Issue: Once an ECO, Manufacturing Change Order (MCO), or Site Change Order (SCO) has been released in Agile, the Queue does not display any corresponding entry for the change order.

Solution:To resolve this queue issue:

1. Check Agile for assemble-to-order (ATO), which was created on the release of the particular change order. Check the status on the Where Sent tab of the ATO.
2. If it shows a Failure message, this implies that an error occurred while Agile Content Service (ACS) was processing the publishing of the data to the Java Message Service (JMS) destination. The error message is specified in the Transmission Notes column as shown in this screenshot.

Figure E-1 Agile ATO
3. After you make any necessary changes to the transfer order or the destination to correct the problem, reset the destination to attempt delivery again.

Once a destination has failed, no other transfer orders can be sent to that destination until it has been reset.
4. To reset the destination, in Agile Java client, go to Admin, System Settings, Agile Content Service, Destinations.
5. Select the required destination and click Reset.

The Reset icon is next to the Delete icon.

Figure E-2 ACS - Destinations
6. After resetting the destination, test the destination to ensure the test is successful for the destination.

In case it fails, this has to be resolved, mainly by ensuring all the ECO Queue settings are correct and SOA Port specified in the URL is correct.

If the status of the ATO transfer is Success, it implies that the ACS is publishing the data to JMS queue successfully. Therefore you must troubleshoot in the BPEL console.
7. Navigate to the Weblogic EM Console: http://<host name>:<port number>/em
8. Click the Instances tab. Check for the instance of the ProcessBillOfMaterialsListSAPProvABCS for which the error occurred.

Figure E-3 BPEL Console - Instances
9. Click on the Instance Name and go to the Flow link. In the BPEL flow shown, find the element at which the error has occurred and then click on the element to view the Activity Audit trail for more details.

Figure E-4 BPEL Flow

E.4 SAP Issues

When implementing the Agile PLM Integration Pack for SAP: design to Release pre-built integration, you might encounter the following issues.

Issue: When updating SAP Item attributes to Agile, if the Agile application is down or an error occurs in processing the data, then the data cannot be resubmitted to Agile.

Solution: If there is any error in the SAP item attributes update to Agile, an email is sent to the customer or administrator specifying the failure.

To resolve the issue, identify the failed IDOC and resubmit from SAP:

1. Open the error mail that was sent to the customer, user, or administrator.
2. Click on the hyperlink provided on the error mail.
3. Open the BPEL Console and navigate to the instance that was given in the link.
4. Scroll down to the Assign Fault and check the IDOC number that has failed.
5. Navigate to the SAP application and resubmit the IDOC with the item attribute details provided in the email.

Note:

Verify that the Agile application server is up and running before initiating the process.

Issue: If there is an error in CreateBillOfMaterialsListSAPProvABCSImpl with the error description as "javax.xml.rpc.soap.SOAPFaultException: com.sap.mw.jco.JCO$AbapException: (126) ERROR: Terminate processing".

Solution: Perform these steps:

1. Verify the components in the Bill Of Materials (BoM) were created in SAP. If the components are not created, add the components to the affected item and then release the Engineering Change Order (ECO).
2. Verify the components have a valid Item Category, BoM Usage and Effectivity Date.

Issue: If there is an error in UpdateBillOfMaterialsListSAPProvABCSImpl with the error description as "javax.xml.rpc.soap.SOAPFaultException: com.sap.mw.jco.JCO$AbapException: (126) ERROR: Terminate processing"

Solution: Perform these steps:

1. Verify the components in the BoM were created in SAP. If the components are not created, add the components to the affected item and then release the ECO.
2. Verify the components have a valid Item Category, BoM Usage and Effectivity Date.
3. Verify that the components defined while creating the BoM have a unique Find Number in Agile PLM.

Issue: If there is an error in SyncItemListSAPProvABCS with the error description as "Exception during SOAP invoke: com.sap.mw.jco.JCO$AbapException: (126) REVISION_LEVEL_EXISTS: REVISION_LEVEL_EXISTS" even though the process is showing as success.

Solution: This error can be ignored as it is only a check for revision existence for the particular item or material.

Issue: If there is an error in SyncItemListSAPProvABCS or ReserveItemSAPProvABCS with the error description as "Exception during SOAP invoke: java.lang.Exception: BapiError: Enter a material type; nested exception is: javax.xml.rpc.soap.SOAPFaultException: java.lang.Exception: BapiError: Enter a material type"

Solution: Verify the ITEM_PRIMARYCLASSIFICATIONCODE Domain Value Map (DVM) is mapped correctly. If not modify the same and resubmit from the Queue Manager console.

Also verify the REFERENCEMATERIALS is mapped with the corresponding material in SAP.

Issue: If there is an error in SyncItemListSAPProvABCS with the error description as "Exception during SOAP invoke: com.ibi.sap.SapAdapterException: Field: REV_LEVEL_NEW exceeds defined in structure INPUT allowed length 2: ABC; nested exception is: javax.xml.rpc.soap.SOAPFaultException: com.ibi.sap.SapAdapterException: Field: REV_LEVEL_NEW exceeds defined in structure INPUT allowed length 2: ABC"

Solution: Verify the revision level defined for the affected item is 2 characters.

Issue: MediatorMessageProcessingFailed due to timed out exception

Solution: Remove the ECO from the queue with processing state and re-release the ECO from Agile.

E.5 Agile Issues

Issue: Issue in fetching the Part number from SAP using New Part Request (NPR).

Solution: Encrypt the SOA_LOGIN_PASSWORD by using the following command in Agile:

<AgileHome>/agileDomain/bin/encryptpwd.sh and place the encrypted password in the config.properties in NPRpx.jar of Agile.