Notes about process flow in OWB
The code generated from a process flow definition is in industry standard XML Process Definition Language (XPDL).
You can do that with the OWB - Public Views (metadata). Here below an example for a mapping :
select PACKAGE_NAME,
ALL_IV_PROCESS_ACTIVITIES.PROCESS_NAME,
ALL_IV_PROCESS_ACTIVITIES.ACTIVITY_NAME,
ALL_IV_PROCESS_ACTIVITIES.ACTIVITY_TYPE
from ALL_IV_PROCESS_ACTIVITIES,
ALL_IV_PROCESSES
where ALL_IV_PROCESS_ACTIVITIES.BOUND_OBJECT_NAME = 'NameofTheMapping'
AND ALL_IV_PROCESS_ACTIVITIES.PROCESS_ID = ALL_IV_PROCESSES.PROCESS_ID
ACTIVITY_TYPE | Description |
---|---|
PlSqlMapProcessNoteTag | Mapping |
SUBPROCESS | Sub Process |
ProcedureProcessNoteTag | Procedure |
FunctionProcessNoteTag | Function |
ABAPMapProcessNoteTag | Abap Mapping (batch_mapping) |
You can use the Fork activity to launch multiple, concurrent activities after the completion of an activity.
configuration properties “Use return as Status”:
As a workaround, you can define processflow variable and bind RESULT_CODE parameter of Sql*plus activity to this variable. Then you can define transition from sqlplus activity with custom (“complex”) condition (like PF_VAR_RC=2 etc.).
Create a function which return as Status to return 1, 2 or 3 to direct the process flow into SUCCESS, WARNING or ERROR respectively.