2.9.1.2 Both Main and Child Lines
This topic describes about the approval breach tracking for both main and child lines.
- If exception transaction is given both at child and main line level
- Email Approval is triggered as per the respective configuration for main and child lines
- Approve/Reject response can be triggered in any of the queues irrespective of each
other
- The first response from either queue is stored and wait for the response from other one
- If same role authorizer gets dual authorization transactions for both main and
child facilities and if both the transactions are approved
- Assume Queue 1 is configured to handle Exception for main line and Queue2 for Exception handling of child line (both for Amount and percentage)
- Email approval is triggered to the all the users (including same role authorizer) attached different queues (Queue1 and Queue 2) for both main and child lines (both amount and percentage)
- Approve/Reject response can be triggered in any of the queues
irrespective of each other
- The first response from either queue is stored and wait for the response from other one
- System considers the Approved/Reject response from both main line (Queue 1) and child line (Queue2) to authorize/reject the utilization transaction
- Assuming the first response received within Queue1 for main line is
Approved.
- System sends and intimation mail to other users in Queue1 about the approval
- Any further response is ignored and removed from the Queue 1
- System waits for other response of other queue (Queue 2) before authorizing the utilization transaction.
- Assuming the first response received within Queue 2 is also
Approved
- System sends an intimation mail to other users in Queue 2 about the approval
- Any further response is ignored and removed from the Queue 2
- Since Queue 2 response is also Approved, system authorizes the utilization transaction in both main and child lines
- If same role authorizer gets dual authorization transactions for both main and
child facilities and if one of the transaction is approved and the other is rejected, then
the entire transaction should be rejected
- Assume Queue 1 is configured to handle Exception for main line and Queue2 for Exception handling of child line (both for Amount and percentage)
- E-mail Approval is triggered to the all the users (including same role authorizer) attached different queues (Queue1 and Queue2) for both main and child lines (both amount and percentage)
- Approve/Reject response can be triggered in any of the queues
irrespective of each other
- The first response from either queue is stored and wait for the response from other one
- System considers the Approved/Reject response from both main line (Queue 1) and child line (Queue2) to authorize/reject the utilization transaction
- Assuming the first response received within Queue 1 for main line is
Approved.
- System sends an intimation mail to other users in Queue 1 about the approval
- Any further response is ignored and removed from the Queue 1
- System waits for other response of other queue (Queue 2) before authorizing the utilization transaction
- Assuming the first response received within Queue 2 is
Reject
- System sends an intimation mail to other users in Queue2 about the rejection
- Any further response sends ignored and removed from the Queue2.
- Since Queue 2 response is Reject, system rejects the utilization transaction in both main and child lines
- When different branches involved in utilization transaction – main line in one branch and child line in a different branch, appropriate branch/category combination configuration is considered
- Email approval is triggered to multiple authorizers (as configured) and subsequent behaviour similar to breach functionality
- If dual authorization of breach transaction pertaining to child and main lines goes to two different users, then the transaction will not get approved till both the transaction are approved. If multiple users are attached to a role configured for receiving email, all of them will get email for dual authorization approval. If one of them approves, then the transaction goes through. However, if one of them rejects, other users will be informed appropriately by E-mail.
Parent topic: Breach Tracking Mechanism