26. Support 24x7

Oracle FLEXCUBE is available on a 24x7 basis for two broad channels Web service & Web Branch. During EOD batch process, transactions are tanked and then get processed after the batch is completed.

This document details about the 24x7 support feature in FCUBS.

This chapter contains the following topics:

• Section 26.1, "Gateway Messaging"
• Section 26.2, "Web Branch"
• Section 26.3, "Batch Processing "
• Section 26.4, "Processing Different Categories During EOD"

26.1 Gateway Messaging

Oracle FLEXCUBE processes the following channel transactions, 24x7:

• FLEXCUBE UBS - Gateway - Web service
  • Customer (New, Modify, Close)
  • Customer Account (New, Modify, Close)
  • Fund Transfer
  • Payment & Collections
  • Consumer Loans

All new requests for maintenance functions or online functions when the branch available status is ‘No’ are accepted at the Gateway messaging layer. The Gateway messaging layer does not route the transaction requests during the Date Change Window.

26.2 Web Branch

Oracle FLEXCUBE processes the following channel transactions, 24x7:

• FLEXCUBE UBS - Retail Web Branch UI
  • Retail Teller
  • Instruments
  • Clearing
  • Utility Payments
  • Retail Loan

26.3 Batch Processing

Every day while processing a channel transaction, system checks for the branch availability status. The system displays the Branch Available status. If the status is ‘Yes’, it indicates that the branch can accept transactions for the day and if the status is ‘No’ , then it indicates that the transactions will be accepted but it will be in effect only from the next business day.

Accordingly accounting entries will be passed checking the following, for tanking branch transactions:

• The Branch Available Status
• The Branch date and host date i.e. entries will be tanked if branch date is ahead of host date

When the Branch Available status is ‘NO’ or if branch date is ahead of host date, then the transactions will be tanked. These transactions will be untanked by the BOD program which runs post date change i.e. POSTDTCH.

The branch available status can be changed from Yes to No in two ways.

• Auto
  • At the start of EOTI if the branch available status is not ‘No’.
  • At the start of ICEOD if the branch available status is not ‘No’.
  • At the start of EOFI if the branch available status is not ‘No’.
  • Drop of End of Transaction Input
  • System Date Change

• Manual
  • Manual – Scheduling and Execution as EOD batch.

IC EOD Process

The account resolution during IC EOD process excludes accounts that are with account creation status as Tanked.

Drop - End of Transaction Input (EOTI)

If the branch is not available during the Drop End Of Transaction Input, system automatically resets the Branch available status to ‘Yes’. Also all the tanked transactions and accounting entries are released.

All transactions that are tanked would be released with tanked status as No and advices and payment messages if suppressed would be generated.

For the process that started when the branch available status was Yes, then the Status change to ‘No’ cannot be changed till the completion of the process. This is applicable for DE Batch upload process.

26.4 Processing Different Categories During EOD

During EOD batch process, the categories like maintenance and financial transaction process are explained below.

26.4.0.1 Processing Maintenance

The maintenance process includes:

• New Customer Creation
• Customer Amendment
• Customer Closure
• New Account Creation
• Account Amendment
• Account Closure

Creating Customers

While creating customer if the branch available status is no, then the creation date gets set to next branch working date. The customer details report requests are accepted and the processing of the same starts only during the next branch available status. The report would include the customer creation date also.

Creating Customer Accounts

The customer account creation requests are processed with the tanked status as ‘Yes’ if the branch is not available for transaction and these accounts are not considered for Interest & Charges calculation process

After the branch is available after the date change process, tanked status gets changed to ‘No’ and initiation entries of term deposit that are tanked are released with transaction date moved to next working date.

Processing TD Account Creation

The Term Deposit creation requests are processed with the tanked status as ‘Yes’ if the branch is not available for transaction. If the customer account is displaying as tanked, it indicates that the customer account creation request was processed when the branch available status is No or when branch date was ahead of host date.

The process when the TD account creation is received when the branch is unavailable or when branch date is ahead of host date is as follows:

• The TD account creation would be accepted with transaction status as Tanked.
• The initiation accounting entries will be posted as tanked entries.

The Term Deposit accounts that are in tanked status will not be considered for Interest & Charges calculation process.

After the branch available status is changed to ‘Yes’ then:

• The TD account tanked status will set to No.
• The Initiation entries of term deposit that are tanked would be released with transaction date moved to next working date.

Processing TD Account Redemption

The Term Deposit Redemption Transactions are processed partially if the branch is not available for transaction or when branch date is ahead of host date. Partial Redemption of the account is processed even after branch available status is ‘No’ or branch date is ahead of host date

• For TD redemption by Transfer to Savings, TD redemption by Transfer to GL, the RT Transaction done for moving the available funds will get tanked.
• For TD redemption By Bankers Cheque, the Instrument Transaction done for Issuing the BC will get tanked.

After the branch available status is changed to ‘Yes’ then:

• The transaction status of the TD Redemption Transaction will be changed to Active.

The tanked accounting entries if any would be un-tanked by the batch process.

Processing Account Closure

The Close out Withdrawal Transaction is not allowed if the branch is not available for transaction or when branch date is ahead of host date.

26.4.0.2 Processing transactions:

The transaction process includes:

• Payments and Collections
• Retail Loan
• Fund Transfer
• Retail Teller
• Instruments
• Standing Instructions
• Clearing
• Utility Payments

Processing Funds Transfer

The fund transfer requests are processed with tanked status if the branch is not available for the transactions assuming that the FT Product cut-off time is maintained such that the cut-off time is past for the FT transaction when the Branch available status is changed to No.

The process when the FT transaction is received when the branch is unavailable is as follows:

• The FT transaction would be accepted with tanked status as Yes.
• There would be no change in the debit & credit value date derivation which currently takes in to consideration the value date spreads and cut-off time maintained in FT - Value Date Spread maintenance.
• There would be no change in the derivation of the following processing dates –
  • Messaging Date
  • Accounting Entry Date
  • Rate Date

• If the Messaging Date of the FT transaction is derived as the application date then the message generation would be suppressed and the message will be generated once the branch available status changes to ‘Yes’
• Accounting entries would be posted with tanked status if the accounting date derived is as of the application date.
• Advices associated with FT transaction events if any would be suppressed and generated once the branch available status changes to ‘Yes’

After the branch available status is changed to ‘Yes’ after the business date change then

• The tanked status of the FT transaction would be set to No
• The tanked accounting entries if any would be un-tanked by the existing batch process for releasing the accounting entries.
• Advices of the FT transaction if suppressed would be generated.
• If the payment message generation for FT transaction was suppressed, the same would be generated during the transaction release.

The following FT operation requests when the branch available status is No would be accepted and the processing would be deferred till the branch available status is yes. The requests would be tanked at the FC UBS Gateway messaging layer.

• Cancellation of FT Transaction
• Amendment of FT transaction
• Liquidate FT transaction
• Reversal of FT transaction

Processing Payments and Collection

The PC requests are processed with the tanked status as ‘Yes’ if the branch is not available for transaction assuming that the PC Product cut-off time is maintained such that the cut-off time is past for the PC transaction when the Branch available status is changed to No.

If the PC request is received past the cut-off time maintained at the product/customer level, the activation date would be moved to next working date with the other processing dates resolved based on the activation date keeping as same. For Debit Liquidation - DRLQ event and Credit Liquidation - CRLQ event dates derived is application date, then the accounting entries are posted with tanked status.

For a book transfer, if the dispatch date derived is the application date then the offset transaction is generated and processed. The offset transaction accounting entries as part of DRLQ event and CRLQ event are posted with tanked status if the accounting entry date derived is the application date. After the branch status is available, then the tanked accounting entries if any would be un-tanked by the existing batch process for releasing the tanked accounting entries.

The following PC operation requests when the branch available status is No would be accepted and the processing would be deferred till the branch available status is yes. The requests would be tanked at the FC UBS Gateway messaging layer.

• Amendment of PC transaction
• Reject/Recall of PC Transaction
• Approval of Incoming collection
• Reversal of PC transaction
• Re-dispatch of Outgoing collection
• PC periodic instruction setup transaction

Processing Retail Teller Transactions

The retail teller transactions are processed with the tanked status as ‘Yes’ if the branch is not available for transaction. During the RT transaction query, the transaction can be viewed as tanked, if the RT transaction is tanked and that the request was processed when the branch available status is No or when branch date was ahead of host date.

The process when the RT transaction is received when the branch is unavailable or when branch date is ahead of host date is as follows:

• The RT transaction would be accepted with transaction status as Tanked.
• The accounting entries would be posted with tanked status.
• Message and advices of an RT transaction are suppressed.

After the branch available status is changed to ‘Yes’ then

• The transaction status of the RT transaction will be changed to Active.
• The tanked accounting entries if any would be un-tanked by the batch process for releasing the tanked accounting entries.
• The messages and the advices associated with the RT transaction that were suppressed are also generated.
• The transaction date of the RT transaction will remain unchanged during the process of un-tanking.

Processing Clearing Transactions

The clearing transactions are processed with the tanked status as ‘Yes’ if the branch is not available for transaction. During the clearing transaction query, the transaction can be viewed as tanked, if the CG transaction is tanked and that the request was processed when the branch available status is No or when branch date was ahead of host date.

The process when the clearing transaction is received when the branch is unavailable or when branch date is ahead of host date is as follows:

• The Clearing transaction would be accepted with transaction status as Tanked.
• The accounting entries would be posted with tanked status.

After the branch available status is changed to ‘Yes’ then:

• The transaction status of the Clearing transaction will be changed to Active.
• The tanked accounting entries if any would be un-tanked by the batch process for releasing the tanked accounting entries.

Processing Instrument Transactions

The instrument transactions are processed with the tanked status as ‘Yes’ if the branch is not available for transaction. During the DD transaction query, the transaction can be viewed as tanked, if the DD transaction is tanked and that the request was processed when the branch available status is No or when branch date was ahead of host date.

The process when the instrument transaction is received when the branch is unavailable or when branch date is ahead of host date is as follows:

• The instrument transaction would be accepted with transaction status as Tanked.
• The accounting entries would be posted with tanked status.

After the branch available status is changed to ‘Yes’ then:

• The transaction status of the Instrument transaction will be changed to Active.
• The tanked accounting entries if any would be un-tanked by the batch process for releasing the tanked accounting entries.

Processing Standing Instructions

The standing instructions are processed with the tanked status as ‘Yes’ if the branch is not available for transaction. During the standing instruction query, the instruction can be viewed as tanked, if it is tanked and that the request processed when the branch available status is ‘No’ or when branch date was ahead of host date.

When the instruction is received while the branch is unavailable, then the process is as follows:

• The instruction is accepted with transaction status as ‘Tanked’.
• Accounting entries are posted with the status ‘Tanked’.

Once the branch status is ‘Available’, then the following process is applicable:

• The transaction status of the instruction is changed to ‘Un-tanked’
• A batch process releases the tanked accounting entries
• For all instructions whose booking date is the same as the Application date, the ‘Date Change BOD Batch’ of that date updates the status to ‘Un-tanked’.
• The transaction date of the instruction remains the same after un-tanking.

Processing Utility Payment Transactions

The utility payment transactions are processed with the tanked status as ‘Yes’ if the branch is not available for transaction. During the UP transaction Query, the transaction can be viewed as tanked, if the UP transaction is tanked and that the request was processed when the branch available status is No or when branch date was ahead of host date.

The process when the utility transaction is received when the branch is unavailable or when branch date is ahead of host date is as follows:

• The UP transaction would be accepted with transaction status as Tanked.
• The accounting entries would be posted with tanked status.

After the branch available status is changed to ‘Yes’ then:

• The transaction status of the UP transaction will be changed to Active.
• The tanked accounting entries if any would be un-tanked by the batch process for releasing the tanked accounting entries.

The different categories which get processed during the End of the Day batch run are explained in the table below:

Maintenance/Transactions	Branch Status – Not Available	Branch Status – Available (After date change)
Customer/Account Creation	The process is tanked till the branch available sta­tus is yes. Initiation accounting entries will be posted as tanked entries.	TD account status is changed from tanked to un-tanked. Initiation accounting entries are un-tanked and released with transaction date moved to next work­ing date.
TD Account Redemption	Processed partially	Transaction status is un-tanked and accounting entries if any would be un-tanked
Account Closure	Not Allowed	Processed normally
Funds Transfer	Transaction/Accounting entries would be posted with tanked status.	Transaction/Accounting entries are un-tanked and processed.
Payments and Col­lection	Transaction/Accounting entries would be posted with tanked status.	Transaction/Accounting entries are un-tanked and processed.
Retail Teller Trans­actions	Transaction/Accounting entries would be posted with tanked status.	Transaction/Accounting entries are un-tanked and processed.
Clearing Transac­tions	Transaction/Accounting entries would be posted with tanked status.	Transaction/Accounting entries are un-tanked and processed.
Instrument Trans­actions	Transaction/Accounting entries would be posted with tanked status.	Transaction/Accounting entries are un-tanked and processed.
Utility Payment Transactions	Transaction/Accounting entries would be posted with tanked status.	Transaction/Accounting entries are un-tanked and processed.