Detailed Description and Symptoms
After upgrading from version 6.x OAE jobs are no longer going into C-statuses but rather Abort. This can cause issues with conditions set to look for this specific status that are no longer being reflected. You may also not wish jobs that would have gone into C-WARNING to Abort as they now do.
This is expected behaviour in versions 7.1 and 8.0
Any return code other than 0 is going to come back as an aborted status in the GUI. This is no matter what the status is in Oracle Applications. This was to standardize across different applications. As such we no longer use C- statuses for Oracle Applications. The most common way to work around this is to use output scans on your jobs as outlined in the Development Guide Section 2.6.1 Defining Output Scans.
In the job's output file you will often see similar:
Wed Feb 23 13:18:30 EST 2011: Job: 4998572 status:Standby(31)
Wed Feb 23 13:19:18 EST 2011:Job final status: Warning(102)
You can scan for the common text of the Oracle Applications status and change it to a custom status of your own such as WARNING and then take actions upon that via conditions. We would recommend looking for (31)|(102) in the text field as this would catch either the Standby OR Warning status that is thrown. You'll need to look through your output files to determine the exact statuses thrown by OAE that you need to look for. Check All Output and then in Action check Succeed with the Status displayed as WARNING.