以下部分英文解释来自oracle官方文档……
Summary
Description
Returns the status of a concurrent request. If the request has already completed, also returns a completion message. FND_CONCURRENT.GET_REQUEST_STATUS returns the "developer" phase and status values that can drive program logic.
Arguments (input)
request_id The request ID of the program to be checked.
application Short name of the application associated with the concurrent program. This parameter is necessary only when the request_id is not specified.
program Short name of the concurrent program (not the executable). This parameter is necessary only when the request_id is not specified. When application and program are provided, the request ID of the last request for this program is returned in request_id.
Arguments (output)
phase The user-friendly request phase from FND_LOOKUPS.
status The user-friendly request status from FND_LOOKUPS.
dev_phase The request phase as a constant string that can be used for program logic comparisons.
dev_status The request status as a constant string that can be used for program logic comparisons.
message The completion message supplied if the request has completed.
Example
In the above example, rphase and rstatus receive the same phase and status values as are displayed on the Concurrent Requests form. The completion text of a completed request
returns in a message. Any developer who wishes to control the flow of a program based on a request's outcome should use the following values to compare the request's phase and status. Possible values for dev_phase and dev_status are listed and described in the following table:
dev_phase | dev_status | Description |
PENDING | NORMAL | Request is waiting for the next available manager. |
PENDING | STANDBY | A constrained request (i.e. incompatible with currently running or actively pending programs) is waiting for the internal concurrent manager to release it. |
PENDING | SCHEDULED | Request is scheduled to start at a future time or date. |
PENDING | PAUSED | Child request is waiting for its Parent request to mark it ready to run. For example, a report in a report set that runs sequentially must wait for a prior report to complete. |
RUNNING | NORMAL | Request is being processed. |
RUNNING | WAITING | Parent request is waiting for its sub-requests to complete. |
RUNNING | RESUMING | Parent request is waiting to restart after its sub-requests have completed. |
RUNNING | TERMINATING | A user has requested to terminate this running request. |
COMPLETE | NORMAL | Request completed successfully. |
COMPLETE | ERROR | Request failed to complete successfully. |
COMPLETE | WARNING | Request completed with warnings. For example, a report is generated successfully but failed to print. |
COMPLETE | CANCELLED | Pending or Inactive request was cancelled. |
COMPLETE | TERMINATED | Running request was terminated. |
INACTIVE | DISABLED | Concurrent program associated with the request is disabled |
INACTIVE | ON_HOLD | Pending request placed on hold. |
INACTIVE | NO_ MANAGER | No manager is defined to run the request. |
INACTIVE | SUSPENDED | This value is included for upward compatibility. It indicates that a user has paused the request at the OS level. |