|
An order arrives in the $OM_ORDER_NEW region. |
||||
|
The Routing Logic Module (function blocks) processes the new order. |
||||
|
|
The validation result, based on business logic built into a Query expression, can be: |
|||
|
|
IGNORE_ORDER |
Status |
Based on business logic built into a Query expression. |
|
|
|
|
Action |
The Order item is deleted from both PRT and TADB. |
|
|
|
PENDING_ORDER |
Status |
Not enough information to automatically accept, reject or ignore the order item. |
|
|
|
|
Destination |
$OM_ORNEW_DETN |
|
|
|
|
Action |
Manually rejected |
The Order item is deleted from both PRT and TADB. |
|
|
|
|
Update accepted through $OMX_UPDCOM |
Moves back to $OM_ORDER_NEW |
|
|
ACCEPT_ORDER |
Status |
$OM_ORNEW_RJCT A TADB tracking record exists and has a sequence attribute. |
|
|
|
|
Destination |
$OM_ORNEW_ACPT |
|
|
|
|
Action |
Triggers $OMX_MASTER. |
|
|
|
REJECT_ORDER |
Status |
Based on business logic built into a Query expression. |
|
|
|
|
Destination |
OM_ORNEW_RJCT |
|
|
|
|
Action |
The Order item is deleted from both PRT and TADB. |
|
|
|
POMS routing overview. |
