Trouble Shooting

This chapter covers the following topics:

Trouble Shooting

Price Protection, which is modeled using existing Oracle applications functionality, functions smoothly if you closely follow the setup steps described in Chapter 2 of this guide. If you set up Price Protection incorrectly, then some of the concurrent programs will not process the data and the execution process will not function properly. You must correct an erroneus data setup and rerun the processes.

Use the checkpoints provided in this chapter to verify that the application is processing the data correctly.

SOA Scenarios

Type Scenario Impact How to Know Solution
Technical ECX agent listeners are down If the ECX Inbound and transaction listeners are down, then the XML feed is not processed. The feed stays pending. They can be monitored by the Workflow Administrator. Web Applications > Workflow Manager > Service Components 1 Procedure for Verification - XML Gateway Bring the listeners up
Technical Concurrent manager down The ECX listeners submit concurrent program requests to process feed. The XML feed is stuck in pending. They can be monitored by the Workflow Administrator, Web Applications > Workflow Manager > Service Components Bring the concurrent manager up
Technical Concurrent manager down If the Cost Update program was submitted, then it will hang as it uses the concurrent manager.   Bring concurrent manager up
Technical Inventory Transaction Manager (concurrent program name: Process Transaction Interface) not scheduled in the instance. Cost Update program hangs as it depends on the inventory transaction manager to complete   Schedule inventory transaction manager
Technical Cost manager not scheduled Item cost updates will not be accounted   Schedule cost manager
Technical Concurrent manager down - initiate process not scheduled. Approved transactions will not become active Transactions hanging in approved state Bring up concurrent manager and schedule job
Technical AME not set up and default approver profile value not set Transactions cannot be submitted for internal approval UI displays error message Setup required
Technical Oracle implements profile options not set up or set to No UI will display errors. It is mandatory in phase 1 that they are set to Yes UI error messages They should be set to Yes for phase 1
Functional Outbound process failure (XMLGW) Notifications are not sent to trading partner or ECX system administrator They can be monitored by the workflow administrator, Web Applications > Transaction Monitory. Resubmit possible Resubmit
Functional OAG compliance failure Trading partner receives notification. Transaction not accepted (I.e. not pushed to interface or base tables)   Trading partner has to take action and resend.
Functional DTD Compliance failure ECX System Administrator gets notification (from profile option). Transaction not accepted (I.e. not pushed to interface or base tables)   System administrator must resolve error and receive corrected feed from partner
Functional Business validation error while processing feed ECX system administrator receives notification (from profile option). Transaction is accepted but not processed. (I.e. pushed to interface tables but NOT to base tables)   System administrator must resolve error and submit concurrent program to import data from interface to base tables.
Functional Transaction cannot be submited for internal approval If both the AME setup and default approver profiles are not set, then this issue occurs   Set up at minimum one of the two profiles
Functional Outbound communication for supplier site is always as WebADI Trade profile is NOT set up. In this scenario, the communication mechanism defaults to WebADI   Set up trade profile with correct communication mechanism
Functional Users not receiving notification email or messages in message center with pending approval transactions If workflow is not set up or working properly, then email notifications and message center messages are not sent.   Ensure workflow is set up properly