 |
The user can use this option to
manually
create/start an entry in the routing system. Once the
information
in block 1 has been entered and <COMMIT>ed, the data in
blocks 2
and 3 are copied from the default request information as created in {GROU-1} and
<COMMIT>ed.
The ITS defined routing processes will be created/started by the
programs automatically into this option. The main purpose of
this option
will be to query the routing process stages.
A Routing Request can only be deleted after the Route has completed all
the steps.
This is the main entry of a request in the routing system. For every record in this block, multiple records may exist in blocks 2 and 3.
| Field | Type & Length |
Description |
|---|---|---|
| Routing Request Type | A4 | Enter the routing entry type. A <LoV> may be used to select a valid type as defined in {GROU-1}, TAB - Entry Types. |
| System ID | A1 | Enter system ID. A <LoV> may be used to select a valid ID code linked to the request type in {GROU-1}, TAB - Entry Types. |
| Request Entry Number | N12 | The number of new requests will be created on <COMMIT>ed. |
| Activating Entity | A1 | (E)mail or (U)ser |
| Responsible Entity | A1 | (E)mail, (U)ser or (B)atch |
| Request Start Date | DD-MON-YYYY | A date in the
future will still start
the process immediately but will have an impact on any timeouts set in
{GROU-1}, TAB -
User Routing Sequences. If a route is kicked off between the start and end times {GCS-1} as setup with SOD 'WH' being set to 'Y' {GCS2-11} for the start and end times to display, this route will kick off as setup on {GROU-1}. If a route is kicked off outside of the start and end times, the sequence set up on {GROU-1} will only kick off between those times, therefore the due date will only be calculated once the start time has begun. |
|
The detail of the routing request number, queried in block 1, will be displayed. This is a query only block.
| Field | Type & Length |
Description |
|---|---|---|
| Routing Entry Number | N12 | The number of new requests will be created on <COMMIT>ed. |
| Sequence Number | N3 | Enter routing sequence (step) number. |
| User/Email/Batch | A1 | Enter (U)ser Code or (E)mail. Batch is used for background processing. |
| User Code / Email | A60 | Depending on the code used at
User/Email/Batch enter a user code or email address. |
| Person Type | A1 | The Person Type of the Person Responsible for completing this sequence. |
| Person Number | A20 | The Person Number of the Person Responsible for completing this sequence. |
| Number of parallel
paths Expected Completed |
N3 N3 |
The number of parallel paths expected. The number of parallel paths already completed. |
| Transaction Date | DD-MON-YYYY | The date on which the request was created. |
| Outcome | A4 | The Code of the outcome that was assigned to this sequence (step). |
| Due Date | DD-MON-YYYY | The due date calculated from the days given to complete the request and the transaction date. |
This is a query only block. It is used to query the detail of the message/s sent.
| Field | Type & Length |
Description |
|---|---|---|
| Line Number | N6 | The line number. |
| Instruction | A80 | The instructions/comments/information.that appear in the Email sent by this sequence or on the Approval for the sequence in the iEnabler |
| Character | A12 | A general character field. |
| Number | N17.3 | A general numeric field. |
| Date | DD-MON-YYYY | A general date field. |
|
| Processing Rules |
|
|---|---|
| Functionality exists for an automated email notification to be generated, when the responsible person for the Routing Number / Sequence Number is updated, where Routing Type System ID = ‘P’, advising the new responsible person of each application they are now responsible to action. The Responsible person may be updated per Routing Type {GROU-2} or in Bulk {GROU-9}. Routing Type ‘KERP’ is used for the generation of this notification. |
| Date | System Version | By Whom | Job | Description |
|---|---|---|---|---|
| 25-Jan-2007 | v01.0.0.0 | Amanda Nell | t134851 | New manual format. |
| 12-Mar-2008 | v01.0.0.0 | Vaughn Dumas | t134851 | System owner proofread. |
| 15-Jun-2008 | v01.0.0.1 | Amanda Nell | t150627 | Apply Language Editing. |
| 19-Jul-2010 | v02.0.0.0 | Frans Pelser | t161974 | Layout change |
| 24-Oct-2011 | v02.0.0.1 | Innocent Mutyavaviri | t177278 | Add Routing Entry Number |
| 26-Jul-2012 | v03.0.0.0 | Frans Pelser | t178590 | Refer to GMAIN-4 |
| 23-Apr-2020 | v04.1.0.0 | Nomhle Lubisi | t239665 | Updated processing rules |
| 11-Dec-2020 | v04.1.0.1 | Kerrylee Naidoo | t247360 | Update information with due date rules |
