Oracle WebCenter Content (MOSC)

MOSC Banner

How to proactively identify records in Faulted Status in BPEL?

edited Jun 4, 2013 3:27AM in Oracle WebCenter Content (MOSC) 3 commentsAnswered
 One of the major problems with Invoice Processing in BPEL is to identify the state of records in Cube Instance and handling the problems proactively.
When a image is imported in BPEL from IPM, the intance might get into Faulted state - State 6 in cube_instance. Such instances appear to be valid in BPEL Task List from a user stand point. But in back end, the instance is invalid.
These instances are not recoverable from call backs or invokes. The instance can be in Faulted status for several reasons. Tracking down the reasons might be time consuming . In a day to day processing, such events can be handled proactively by identifying the instances first.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center