5. Annexure – List of Messages

5.1 Introduction

This chapter lists out the various messages that fold under the purview of the following Gateway services:

• Inbound application integration – used when any external system needs to add, modify or query information within Oracle FLEXCUBE
• Outbound application integration – used when any external system needs to be notified of the various events that occur within Oracle FLEXCUBE.

5.2 Inbound Application Integration – Services

Oracle FLEXCUBE UBS Inbound Application Gateway provides XML based ‘Services’. These services consist of one or more ‘Operations’. These operations can be invoked by any external system to perform the relevant operation in Oracle FLEXCUBE UBS.

This chapter contains the following sections:

• Section 5.2.1, "FCUBSAccService"
• Section 5.2.2, "FCUBSDDService"
• Section 5.2.3, "FCUBSLDService"
• Section 5.2.4, "FCUBSCustomerService"
• Section 5.2.5, "FCUBSTDService"
• Section 5.2.6, "FCUBSIFService"
• Section 5.2.7, "FCUBSInteractionservice"
• Section 5.2.8, "FCUBSICService"
• Section 5.2.9, "FCUBSSTService"
• Section 5.2.10, "FCUBSIAService"
• Section 5.2.11, "FCUBSRTService"

5.2.1 FCUBSAccService

All account operations are logically grouped under a service called 'FCUBSAccService'.

Oracle FLEXCUBE supports the following operations under this service:

• CheckBooKNew
• CheckBookModify
• CheckBookQuery
• CreateTDSim
• QueryGenAdvice
• Create TD CustAcc
• Modify TD CustAcc
• Authorize TD CustAcc
• Delete TD Cust Acc
• Query TDCustAcc
• CreateTDTopUp
• AuthorizeTDTopUp
• DeleteTDTopUp
• ModifyTDTopUp
• CreateVirAcc
• AuthVirAcc
• DeleteVirAcc
• ModifyVirAcc
• CloseVirAcc
• ReopenVirAcc
• QueryVirAcc
• QueryCustAcc

5.2.1.1 CheckBookNew

This is the operation code for creating new Cheque Book in Oracle FLEXCUBE. It involves the following messages:

• CheckBookNew-Req-Full- This is the request message to create new cheque book in Oracle FLEXCUBE UBS. An external system which intends to create a new cheque book has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CheckBookNew -Req-IO- This is the request message to create new cheque book in Oracle FLEXCUBE UBS. An external system which intends to create the cheque book has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a new cheque book.
• CheckBookNew -Res-Full- This is the response message which is sent back to the external system when a new cheque book is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CheckBookNew -Res-PK- This is the response message which is sent back to the external system when anew cheque book is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the cheque book record in the Oracle FLEXCUBE data store.

5.2.1.2 CheckBookModify

This is the operation code for modifying new Cheque Book in Oracle FLEXCUBE. It involves the following messages:

• CheckBookModify-Req-Full- This is the request message to modify a cheque book in Oracle FLEXCUBE UBS. An external system which intends to modify a cheque book has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CheckBookModify-Req-IO- This is the request message to modify a cheque book in Oracle FLEXCUBE UBS. An external system which intends to modify a cheque book has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying a cheque book.
• CheckBookModify -Res-Full- This is the response message which is sent back to the external system when a cheque book is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CheckBookModify -Res-PK- This is the response message which is sent back to the external system when a cheque book is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the cheque book in the Oracle FLEXCUBE data store.

5.2.1.3 CheckBookQuery

This is the operation code for querying new Cheque Book in Oracle FLEXCUBE. It involves the following messages:

• CheckBookQuery-Req-Full- This is the request message to query a cheque book in Oracle FLEXCUBE UBS. An external system which intends to query a cheque book has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CheckBookQuery-Req-IO- This is the request message to query a cheque book in Oracle FLEXCUBE UBS. An external system which intends to query a cheque book has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying a cheque book.
• CheckBookQuery -Res-Full- This is the response message which is sent back to the external system when a cheque book is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CheckBookQuery -Res-PK- This is the response message which is sent back to the external system when a cheque book is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the cheque book in the Oracle FLEXCUBE data store.

5.2.1.4 CreateTDSim

This is the operation code for creating TD simulation in Oracle FLEXCUBE. It involves the following messages:

• CreateTDSim-Req-Full- This is the request message to create TD simulation in Oracle FLEXCUBE UBS. An external system which intends to TD simulation has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateTDSim -Req-IO- This is the request message to create TD simulation in Oracle FLEXCUBE UBS. An external system which intends to TD simulation has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating TD simulation.
• CreateTDSim -Res-Full- This is the response message which is sent back to the external system when a TD simulation is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateTDSim -Res-PK- This is the response message which is sent back to the external system when a TD simulation is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the TD simulation in the Oracle FLEXCUBE data store.

5.2.1.5 QueryGenAdvice

This is the operation code for querying GenAdvice in Oracle FLEXCUBE. It involves the following messages:

• QueryGenAdvice -Req-IO- This is the request message to query GenAdvice in Oracle FLEXCUBE UBS. An external system which intends to query GenAdvice has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying GenAdvice.
• QueryGenAdvice -Res-Full- This is the response message which is sent back to the external system when GenAdvice is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.1.6 Create TDCustAcc

This is the operation code for creating TD in Oracle FLEXCUBE. It involves the following messages:

• CreateTDCustAcc-Req-Full- This is the request message to create TD in Oracle FLEXCUBE UBS. An external system which intends to create TD has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateTDCustAcc -Req-IO- This is the request message to create TD in Oracle FLEXCUBE UBS. An external system which intends to createTD has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a TD.
• CreateTDCustAcc -Res-Full- This is the response message which is sent back to the external system when a TD is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateTDCustAcc -Res-PK- This is the response message which is sent back to the external system when a TD is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the TD creation in the Oracle FLEXCUBE data store.

5.2.1.7 AuthorizeTDCustAcc

This is the operation code for authorizing the TD in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeTDCustAcc-Req-Full- This is the request message to authorize TD in Oracle FLEXCUBE UBS. An external system which intends to authorize a TD has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeTDCustAcc -Req-IO- This is the request message to authorize TD in Oracle FLEXCUBE UBS. An external system which intends to authorize a TD has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating TD simulation.
• AuthorizeTDCustAcc -Res-Full- This is the response message which is sent back to the external system when a TD is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeTDCustAcc -Res-PK- This is the response message which is sent back to the external system when a TD is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the TD authorization in the Oracle FLEXCUBE data store.

5.2.1.8 DeleteTDCustAcc

This is the operation code for deleting a TD in Oracle FLEXCUBE. It involves the following messages:

• DeleteTDCustAcc-Req-Full- This is the request message to delete TD in Oracle FLEXCUBE UBS. An external system which intends to delete a TD has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeleteTDCustAcc -Req-IO- This is the request message to delete TD in Oracle FLEXCUBE UBS. An external system which intends to delete a TD has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating TD simulation.
• DeleteTDCustAcc -Res-Full- This is the response message which is sent back to the external system when a TD is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeleteTDCustAcc -Res-PK- This is the response message which is sent back to the external system when a TD is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the TD deletion in the Oracle FLEXCUBE data store.

5.2.1.9 Query TDCustAcc

This is the operation code for querying TD account in Oracle FLEXCUBE. It involves the following messages:

• QueryTDCustAcc -Req-IO- This is the request message to query a TD account in Oracle FLEXCUBE UBS. An external system which intends to query TD account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying a TD account
• QueryTDCustAcc -Res-Full- This is the response message which is sent back to the external system when TD account is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.1.10 CreateTDTopUp

This is the operation code for doing a top-up of TD in Oracle FLEXCUBE. It involves the following messages:

• CreateTDTopUp-Req-Full- This is the request message to top-up TD account in Oracle FLEXCUBE UBS. An external system which intends to top-up a TD account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateTDTopUp -Req-IO- This is the request message to top-up TD account in Oracle FLEXCUBE UBS. An external system which intends to top-up TD account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for topping up a TD.
• CreateTDTopUp -Res-Full- This is the response message which is sent back to the external system when a TD account is successfully topped-up in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateTDTopUp-Res-PK- This is the response message which is sent back to the external system when a TD account is successfully topped-up in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the top-up in the Oracle FLEXCUBE data store.

5.2.1.11 AuthorizeTDTopUp

This is the operation code for authorizing top-up request of TD in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeTDTopUp-Req-Full- This is the request message to authorize the top-up of TD account in Oracle FLEXCUBE UBS. An external system which intends to authorize the top-up has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeTDTopUp -Req-IO- This is the request message to authorize the top-up of TD account in Oracle FLEXCUBE UBS. An external system which intends to authorize the top-up of TD account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for topping up a TD.
• AuthorizeTDTopUp -Res-Full- This is the response message which is sent back to the external system when a TD account is topped-up is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeTDTopUp -Res-PK- This is the response message which is sent back to the external system when a TD account top-up, is authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the top-up in the Oracle FLEXCUBE data store.

5.2.1.12 DeleteTDTopUp

This is the operation code for deleting top-up request of TD in Oracle FLEXCUBE. It involves the following messages:

• DeleteTDTopUp-Req-Full- This is the request message to delete the top-up of TD account in Oracle FLEXCUBE UBS. An external system which intends to delete the top-up request created has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeleteTDTopUp -Req-IO- This is the request message to delete the top-up of TD account in Oracle FLEXCUBE UBS. An external system which intends to delete the top-up of TD account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for top-up of a TD.
• DeleteTDTopUp -Res-Full- This is the response message which is sent back to the external system when a top-up request is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeleteTDTopUp -Res-PK- This is the response message which is sent back to the external system when a top-up request is deleted from Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the top-up in the Oracle FLEXCUBE data store.

5.2.1.13 ModifyTDTopUp

This is the operation code for modifying account structure in Oracle FLEXCUBE. It involves the following messages:

• ModifyTDTopUp-Req-Full- This is the request message to modify a TD top-up in Oracle FLEXCUBE UBS. An external system which intends to modify a TD top-up has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyTDTopUp-Req-IO- This is the request message to modify a TD top-up in Oracle FLEXCUBE UBS. An external system which intends to modify a TD top-up has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying a TD top-up.
• ModifyTDTopUp -Res-Full- This is the response message which is sent back to the external system when modifying a TD top-up is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyTDTopUP -Res-PK- This is the response message which is sent back to the external system when modifying a TD top-up is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the modifying a TD top-up in the Oracle FLEXCUBE data store.

5.2.1.14 CreateVirAcc

This is the operation code for creating a virtual account in Oracle FLEXCUBE. It involves the following messages:

• CreateVirAcc-Req-Full- This is the request message to create a virtual account in Oracle FLEXCUBE UBS. An external system which intends to create a virtual account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateVirAcc -Req-IO- This is the request message to create a virtual account in Oracle FLEXCUBE UBS. An external system which intends to create a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for opening a virtual account.
• CreateVirAcc -Res-Full- This is the response message which is sent back to the external system when a virtual account is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateVirAcc-Res-PK- This is the response message which is sent back to the external system when a virtual account is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the virtual account opening in the Oracle FLEXCUBE data store.

5.2.1.15 AuthVirAcc

This is the operation code for authorizing the virtual account in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeVirAcc-Req-Full- This is the request message to authorize virtual accounts in Oracle FLEXCUBE UBS. An external system which intends to authorize a virtual account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeVirAcc -Req-IO- This is the request message to authorize a virtual account in Oracle FLEXCUBE UBS. An external system which intends to authorize a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating virtual account simulation.
• AuthorizeVirAcc -Res-Full- This is the response message which is sent back to the external system when a virtual account is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeVirAcc -Res-PK- This is the response message which is sent back to the external system when a virtual account is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the virtual account authorization in the Oracle FLEXCUBE data store.

5.2.1.16 DeleteVirAcc

This is the operation code for deleting a virtual account in Oracle FLEXCUBE. It involves the following messages:

• DeleteVirAcc-Req-Full- This is the request message to delete a virtual account in Oracle FLEXCUBE UBS. An external system which intends to delete a virtual account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeleteVirAcc -Req-IO- This is the request message to delete a virtual account in Oracle FLEXCUBE UBS. An external system which intends to delete a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a virtual account.
• DeleteVirAcc -Res-Full- This is the response message which is sent back to the external system when a virtual account is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeleteVirAcc -Res-PK- This is the response message which is sent back to the external system when a virtual account is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the virtual account deletion in the Oracle FLEXCUBE data store.

5.2.1.17 ModifyVirAcc

This is the operation code for modifying a virtual account in Oracle FLEXCUBE. It involves the following messages:

• ModifyVirAcc-Req-Full- This is the request message to modify a virtual account in Oracle FLEXCUBE UBS. An external system which intends to modify a virtual account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyVirAcc-Req-IO- This is the request message to modify a virtual account in Oracle FLEXCUBE UBS. An external system which intends to modify a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying a virtual account.
• ModifyVirAcc -Res-Full- This is the response message which is sent back to the external system when a virtual account is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyVirAcc -Res-PK- This is the response message which is sent back to the external system when a virtual account is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the virtual account in the Oracle FLEXCUBE data store.

5.2.1.18 CloseVirAcc

This is the operation code for closing a virtual account in Oracle FLEXCUBE. It involves the following messages:

• CloseVirAcc-Req-Full- This is the request message to close a virtual account in Oracle FLEXCUBE UBS. An external system which intends to close a virtual account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CloseVirAcc-Req-IO- This is the request message to close a virtual account in Oracle FLEXCUBE UBS. An external system which intends to close a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for closing a virtual account.
• CloseVirAcc -Res-Full- This is the response message which is sent back to the external system when a virtual account is successfully closed in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CloseVirAcc -Res-PK- This is the response message which is sent back to the external system when a virtual account is successfully closed in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the virtual account in the Oracle FLEXCUBE data store.

5.2.1.19 ReopenVirAcc

This is the operation code for reopening a virtual account in Oracle FLEXCUBE. It involves the following messages:

• ReopenVirAcc-Req-Full- This is the request message to reopen a virtual account in Oracle FLEXCUBE UBS. An external system which intends to reopen a virtual account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ReopenVirAcc-Req-IO- This is the request message to reopen a virtual account in Oracle FLEXCUBE UBS. An external system which intends to reopen a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for reopening a virtual account.
• ReopenVirAcc -Res-Full- This is the response message which is sent back to the external system when a virtual account is successfully reopened in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ReopenVirAcc -Res-PK- This is the response message which is sent back to the external system when a virtual account is successfully reopened in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the virtual account in the Oracle FLEXCUBE data store.

5.2.1.20 QueryVirAcc

This is the operation code for querying a virtual account in Oracle FLEXCUBE. It involves the following messages:

• QueryVirAcc -Req-IO- This is the request message to query a virtual account in Oracle FLEXCUBE UBS. An external system which intends to query a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying virtual account.
• QueryVirAcc -Res-Full- This is the response message which is sent back to the external system when a virtual account is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.1.21 QueryCustAcc

This service is used by external channels to retrieve customer account details from the Oracle FLEXCUBE Universal Banking System:

• QueryCustAcc -Req-IO- This is the request message to query a customer account details in Oracle FLEXCUBE UBS. An external system which intends to query a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying virtual account.
• QueryCustAcc -Res-Full- This is the response message which is sent back to the external system when a customer account is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.2 FCUBSDDService

All the demand draft operations are logically grouped under a service called 'FCUBSDDService'.

Oracle FLEXCUBE supports the following operations under this service:

• CreateTransaction
• QueryDDTransaction

5.2.2.1 CreateTransaction

This is the operation code for creating transaction in Oracle FLEXCUBE. It involves the following messages:

• CreateTransaction-Req-Full- This is the request message to create transaction in Oracle FLEXCUBE UBS. An external system which intends to create transaction has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateTransaction-Req-IO- This is the request message to create transaction in Oracle FLEXCUBE UBS. An external system which intends to create transaction has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a transaction.
• CreateTransaction-Res-Full- This is the response message which is sent back to the external system when transaction is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateTransaction-Res-PK- This is the response message which is sent back to the external system when a transaction is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the transaction record in the Oracle FLEXCUBE data store.

5.2.2.2 QueryDDTransaction

This is the operation code for querying DD Transaction in Oracle FLEXCUBE. It involves the following messages:

• QueryDDTransaction-Req-Full- This is the request message to query DD Transaction in Oracle FLEXCUBE UBS. An external system which intends to query a DD transaction has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• QueryDDTransaction-Req-IO- This is the request message to query DD Transaction in Oracle FLEXCUBE UBS. An external system which intends to query a DD transaction has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying a DD transaction.
• QueryDDTransaction-Res-Full- This is the response message which is sent back to the external system when DD Transaction is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• QueryDDTransaction-Res-PK- This is the response message which is sent back to the external system when DD Transaction is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the DD transaction in the Oracle FLEXCUBE data store.

5.2.3 FCUBSLDService

Corporate deposit operations are logically grouped under a service called 'FCUBSLDService'.

Oracle FLEXCUBE supports the following operations under this service:

• LDActivateSimulate
• DeleteLDSIMContract
• QueryLDSIMContract
• LDVamiCreateSim
• LDVamiQuerySim
• QueryLDPaymentSim
• CreateLDPaymentSim

5.2.3.1 LDActivateSimulate

This is the operation code for activating corporate deposits simulation in Oracle FLEXCUBE. It involves the following messages:

• LDActivateSimulate-Req-Full- This is the request message to activate corporate deposits simulation in Oracle FLEXCUBE UBS. An external system which intends to activate corporate deposits simulation has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• LDActivateSimulate -Req-IO- This is the request message to activate corporate deposits simulation in Oracle FLEXCUBE UBS. An external system which intends to activate corporate deposits simulation has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for activating corporate deposits simulation.
• LDActivateSimulate -Res-Full- This is the response message which is sent back to the external system when corporate deposits simulation is successfully activated in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• LDActivateSimulate -Res-PK- This is the response message which is sent back to the external system when an existing corporate deposits simulation is successfully activated in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the corporate deposits simulation in the Oracle FLEXCUBE data store.

5.2.3.2 DeleteLDSIMContract

This is the operation code for deleting LD simulation contract in Oracle FLEXCUBE. It involves the following messages:

• DeleteLDSIMContract-Req-Full- This is the request message to delete LD simulation contract in Oracle FLEXCUBE UBS. An external system which intends to delete LD simulation contract has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeleteLDSIMContract -Req-IO- This is the request message to delete LD simulation contract in Oracle FLEXCUBE UBS. An external system which intends to delete LD simulation contract has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for deleting LD simulation contract.
• DeleteLDSIMContract -Res-Full- This is the response message which is sent back to the external system when LD simulation contract is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeleteLDSIMContract -Res-PK- This is the response message which is sent back to the external system when an existing LD simulation contract is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the LD simulation contract in the Oracle FLEXCUBE data store.

5.2.3.3 QueryLDSIMContract

This is the operation code for querying LD simulation contract in Oracle FLEXCUBE. It involves the following messages:

• DeleteQueryLDSIMContract -Req-IO- This is the request message to query LD simulation contract in Oracle FLEXCUBE UBS. An external system which intends to query LD simulation contract has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying LD simulation contract.
• DeleteQueryLDSIMContract -Res-Full- This is the response message which is sent back to the external system when LD simulation contract is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.3.4 LDVamiCreateSim

This is the operation code for creating LD VAMI Simulation contract in Oracle FLEXCUBE. It involves the following messages:

• LDVamiCreateSim-Req-Full- This is the request message to create LD VAMI simulation contract in Oracle FLEXCUBE UBS. An external system which intends to create LD VAMI simulation contract has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• LDVamiCreateSim -Req-IO- This is the request message to create LD VAMI simulation contract in Oracle FLEXCUBE UBS. An external system which intends to create LD VAMI simulation contract has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating LD VAMI simulation.
• LDVamiCreateSim -Res-Full- This is the response message which is sent back to the external system when LD VAMI simulation contract is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• LDVamiCreateSim -Res-PK- This is the response message which is sent back to the external system when an LD VAMI simulation contract is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the LD VAMI simulation in the Oracle FLEXCUBE data store.

5.2.3.5 LDVamiQuerySim

This is the operation code for querying LD VAMI Simulation contract in Oracle FLEXCUBE. It involves the following messages:

• LDVamiQuerySim -Req-IO- This is the request message to query LD VAMI simulation contract in Oracle FLEXCUBE UBS. An external system which intends to query LD VAMI simulation contract has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying LD VAMI simulation.
• LDVamiQuerySim -Res-Full- This is the response message which is sent back to the external system when LD VAMI simulation contract is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.3.6 QueryLDPaymentSim

This is the operation code for querying LD Payment Simulation in Oracle FLEXCUBE. It involves the following messages:

• QueryLDPaymentSim -Req-IO- This is the request message to query LD payment simulation in Oracle FLEXCUBE UBS. An external system which intends to query LD payment simulation has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying LD payment simulation.
• QueryLDPaymentSim -Res-Full- This is the response message which is sent back to the external system when LD payment simulation is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.3.7 CreateLDPaymentSim

This is the operation code for creating LD Payment Simulation in Oracle FLEXCUBE. It involves the following messages:

• CreateLDPaymentSim-Req-Full- This is the request message to create LD payment simulation in Oracle FLEXCUBE UBS. An external system which intends to create LD payment simulation has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateLDPaymentSim -Req-IO- This is the request message to create LD payment simulation in Oracle FLEXCUBE UBS. An external system which intends to create LD payment simulation has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating LD payment simulation.
• CreateLDPaymentSim -Res-Full- This is the response message which is sent back to the external system when LD payment simulation is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateLDPaymentSim -Res-PK- This is the response message which is sent back to the external system when an LD payment simulation is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the LD payment simulation in the Oracle FLEXCUBE data store.

5.2.4 FCUBSCustomerService

Customer related operations are logically grouped under a service called 'FCUBSCustomerService'.

Oracle FLEXCUBE supports the following operations under this service:

• AccountStructureNew
• AccountStructureModify
• AccountStructureQuery
• CreateAmtBlk
• ModifyAmtBlk
• CloseAmtBlk
• CreateCustomer.
• ModifyCustomer.
• AuthorizeCustomer.
• QueryCustomer
• CreateClosureData
• AuthorizeClosureData
• ModifyClosureData
• QueryClosureData

5.2.4.1 AccountStructureNew

This is the operation code for creating Account Structure in Oracle FLEXCUBE. It involves the following messages:

• AccountStructureNew-Req-Full- This is the request message to create account structure in Oracle FLEXCUBE UBS. An external system which intends to create account structure has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AccountStructureNew-Req-IO- This is the request message to create account structure in Oracle FLEXCUBE UBS. An external system which intends to create account structure has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating account structure.
• AccountStructureNew -Res-Full- This is the response message which is sent back to the external system when account structure is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AccountStructureNew -Res-PK- This is the response message which is sent back to the external system when a new account structure is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the account structure in the Oracle FLEXCUBE data store.

5.2.4.2 AccountStructureModify

This is the operation code for modifying account structure in Oracle FLEXCUBE. It involves the following messages:

• AccountStructureModify-Req-Full- This is the request message to modify an account structure in Oracle FLEXCUBE UBS. An external system which intends to modify an account structure has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AccountStructureModify-Req-IO- This is the request message to modify an account structure in Oracle FLEXCUBE UBS. An external system which intends to modify an account structure has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying account structure.
• AccountStructureModify -Res-Full- This is the response message which is sent back to the external system when an account structure is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AccountStructureModify -Res-PK- This is the response message which is sent back to the external system when an account structure is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the account structure in the Oracle FLEXCUBE data store.

5.2.4.3 AccountStructureQuery

This is the operation code for querying an account structure in Oracle FLEXCUBE. It involves the following messages:

• AccountStructureQuery-Req-Full- This is the request message to an account structure in Oracle FLEXCUBE UBS. An external system which intends to query an account structure has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AccountStructureQuery -Req-IO- This is the request message to query an account structure in Oracle FLEXCUBE UBS. An external system which intends to query an account structure has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying account structure.
• AccountStructureQuery -Res-Full- This is the response message which is sent back to the external system when an account structure is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AccountStructureQuery -Res-PK- This is the response message which is sent back to the external system when an an account structure is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the account structure in the Oracle FLEXCUBE data store.

5.2.4.4 CreateAmtBlk

This is the operation code for creating an amount block in Oracle FLEXCUBE. It involves the following messages:

• CreateAmtBlk-Req-Full- This is the request message to create amount block in Oracle FLEXCUBE UBS. An external system which intends to create an amount block has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateAmtBlk -Req-IO- This is the request message to create an amount block in Oracle FLEXCUBE UBS. An external system which intends to create an amount block has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating amount block.
• CreateAmtBlk -Res-Full- This is the response message which is sent back to the external system when an amount block is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateAmtBlk-Res-PK- This is the response message which is sent back to the external system when an amount block is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the amount block in the Oracle FLEXCUBE data store.

5.2.4.5 ModifyAmtBlk

This is the operation code for modifying amount block in Oracle FLEXCUBE. It involves the following messages:

• ModifyAmtBlk-Req-Full- This is the request message to modify an amount block in Oracle FLEXCUBE UBS. An external system which intends to modify an amount block has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyAmtBlk-Req-IO- This is the request message to modify an amount block in Oracle FLEXCUBE UBS. An external system which intends to modify an amount block has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying amount block.
• ModifyAmtBlk -Res-Full- This is the response message which is sent back to the external system when an amount block is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyAmtBlk -Res-PK- This is the response message which is sent back to the external system when an amount block is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the amount block in the Oracle FLEXCUBE data store.

5.2.4.6 CloseAmtBlk

This is the operation code for closing amount block in Oracle FLEXCUBE. It involves the following messages:

• CloseAmtBlk-Req-Full- This is the request message to close an amount block in Oracle FLEXCUBE UBS. An external system which intends to close an amount block has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CloseAmtBlk-Req-IO- This is the request message to close an amount block in Oracle FLEXCUBE UBS. An external system which intends to close an amount block has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for closing amount block.
• CloseAmtBlk -Res-Full- This is the response message which is sent back to the external system when an amount block is successfully closed in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CloseAmtBulk -Res-PK- This is the response message which is sent back to the external system when an amount block is successfully closed in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the amount block in the Oracle FLEXCUBE data store.

5.2.4.7 CreateCustomer

This is the operation code for creating a customer record in Oracle FLEXCUBE. It involves the following messages:

• CreateCustomer-Req-Full- This is the request message to create customer record in Oracle FLEXCUBE UBS. An external system which intends to create an amount block has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateCustomer -Req-IO- This is the request message to create customer record in Oracle FLEXCUBE UBS. An external system which intends to create an amount block has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a customer record.
• CreateCustomer -Res-Full- This is the response message which is sent back to the external system when customer record is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateCustomer-Res-PK- This is the response message which is sent back to the external system when a customer record is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the amount block in the Oracle FLEXCUBE data store.

5.2.4.8 ModifyCustomer

This is the operation code for modifying a customer record in Oracle FLEXCUBE. It involves the following messages:

• ModifyCustomer-Req-Full- This is the request message to modify a customer record in Oracle FLEXCUBE UBS. An external system which intends to modify a customer record has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyCustomer-Req-IO- This is the request message to modify customer record in Oracle FLEXCUBE UBS. An external system which intends to modify a customer record has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying a customer record.
• ModifyCustomer -Res-Full- This is the response message which is sent back to the external system when a customer record is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyCustomer -Res-PK- This is the response message which is sent back to the external system when a customer record is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the amount block in the Oracle FLEXCUBE data store.

5.2.4.9 Authorize Customer

This is the operation code for authorizing the customer record in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeCustomer-Req-Full- This is the request message to authorize customer records in Oracle FLEXCUBE UBS. An external system which intends to authorize a record has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeCustomer -Req-IO- This is the request message to authorize customer record in Oracle FLEXCUBE UBS. An external system which intends to authorize a record has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a customer record.
• AuthorizeCustomer -Res-Full- This is the response message which is sent back to the external system when a customer record is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeCustomer -Res-PK- This is the response message which is sent back to the external system when a customer record is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the customer record authorization in the Oracle FLEXCUBE data store.

5.2.4.10 QueryCustomer

This service is used by external channels to query a customer record in Oracle FLEXCUBE:

• QueryClosureData -Req-IO- This is the request message to query a customer record in Oracle FLEXCUBE UBS. An external system which intends to query a customer record has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying a record.
• QueryClosureData -Res-Full- This is the response message which is sent back to the external system when a customer record is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.4.11 CreateClosureData

This is the operation code for creating a record in the ‘Customer Closure Data (STSCUSCL) screen in Oracle FLEXCUBE. It involves the following messages:

• CreateClosureData-Req-Full- This is the request message to create a record in the ‘Customer Closure Data (STSCUSCL) screen in Oracle FLEXCUBE UBS. An external system which intends to create a virtual account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateClosureData -Req-IO- This is the request message to create a record in the ‘Customer Closure Data (STSCUSCL) screen in Oracle FLEXCUBE UBS. An external system which intends to create a virtual account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a record.
• CreateClosureData -Res-Full- This is the response message which is sent back to the external system when a customer record is successfully created in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateClosureData-Res-PK- This is the response message which is sent back to the external system when a customer record is successfully created in the ‘Customer Closure Data (STSCUSCL)’ screen in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of creating a customer record in the Oracle FLEXCUBE data store.

5.2.4.12 AuthorizeClosureData

This is the operation code for authorizing a customer record in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeCustomer-Req-Full- This is the request message to authorize customer records in Oracle FLEXCUBE UBS. An external system which intends to authorize a record has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeClosureData -Req-IO- This is the request message to authorize records in ‘Customer Closure Data (STSCUSCL) screen in Oracle FLEXCUBE UBS. An external system which intends to authorize a record has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating a customer record.
• AuthorizeClosureData -Res-Full- This is the response message which is sent back to the external system when a customer record is successfully authorized in ‘Customer Closure Data (STSCUSCL) screen in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeClosureData -Res-PK- This is the response message which is sent back to the external system when a ‘Customer Closure Data (STSCUSCL) screen is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the customer record authorization in the Oracle FLEXCUBE data store.

5.2.4.13 ModifyClosureData

This is the operation code for modifying a record in the ‘Customer Closure Data (STSCUSCL) screen’ in Oracle FLEXCUBE. Here only the ‘Closure Allowed’ field can be modified. It involves the following messages:

• ModifyClosureData-Req-Full- This is the request message to modify a record in the ‘Customer Closure Data (STSCUSCL) screen’ in Oracle FLEXCUBE UBS. An external system which intends to modify a record has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyClosureData-Req-IO- This is the request message to modify a record in the ‘Customer Closure Data (STSCUSCL) screen’ in Oracle FLEXCUBE UBS. An external system which intends to modify a record has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying a record.
• ModifyClosureData -Res-Full- This is the response message which is sent back to the external system when record is successfully modified in ‘Customer Closure Data (STSCUSCL) screen’ in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyClosureData -Res-PK- This is the response message which is sent back to the external system when a record is successfully modified in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the record in the Oracle FLEXCUBE data store.

5.2.4.14 QueryClosureData

This service is used by external channels to query closure data in the ‘Customer Closure Data (STSCUSCL) screen’ in Oracle FLEXCUBE:

• QueryClosureData -Req-IO- This is the request message to query a customer closure data details in ‘Customer Closure Data (STSCUSCL) screen’ in Oracle FLEXCUBE UBS. An external system which intends to query a customer closure data has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying a record.
• QueryClosureData -Res-Full- This is the response message which is sent back to the external system when a customer closure record is successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.5 FCUBSTDService

TD related operations are logically grouped under a service called 'FCUBSTDService'.

Oracle FLEXCUBE supports the following operations under this service:

• CreateTDRedem
• AuthorizeTDRedem
• DeleteTDRedem
• QueryTDRedem

5.2.5.1 CreateTDRedem

This is the operation code for creating a redemption request of TD in Oracle FLEXCUBE. It involves the following messages:

• CreateTDRedem-Req-Full- This is the request message to redeem TD account in Oracle FLEXCUBE UBS. An external system which intends to redeem a TD account has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateTDRedem -Req-IO- This is the request message to redeem TD account in Oracle FLEXCUBE UBS. An external system which intends to redeem TD account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for redeeming a TD.
• CreateTDRedem -Res-Full- This is the response message which is sent back to the external system when a TD account is successfully redeemed in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateTDRedem -Res-PK- This is the response message which is sent back to the external system when a TD account is successfully redeemed in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the redemption in the Oracle FLEXCUBE data store.

5.2.5.2 AuthorizeTDRedem

This is the operation code for authorizing redemption request of TD in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeTDRedem-Req-Full- This is the request message to authorize the redemption of TD account in Oracle FLEXCUBE UBS. An external system which intends to authorize the redemption has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeTDRedem -Req-IO- This is the request message to authorize the redemption of TD account in Oracle FLEXCUBE UBS. An external system which intends to authorize the redemption of TD account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for redeeming a TD.
• AuthorizeTDRedem -Res-Full- This is the response message which is sent back to the external system when a TD account is redeemed is successfully authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeTDRedem -Res-PK- This is the response message which is sent back to the external system when a TD account redeemed, is authorized in Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the redemption in the Oracle FLEXCUBE data store.

5.2.5.3 DeleteTDRedem

This is the operation code for deleting redemption request of TD in Oracle FLEXCUBE. It involves the following messages:

• DeleteTDRedem-Req-Full- This is the request message to delete the redemption of TD account in Oracle FLEXCUBE UBS. An external system which intends to delete the redemption request created has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeleteTDRedem -Req-IO- This is the request message to delete the redemption of TD account in Oracle FLEXCUBE UBS. An external system which intends to delete the redemption of TD account has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for redeeming a TD.
• DeleteTDRedem -Res-Full- This is the response message which is sent back to the external system when a redemption request is successfully deleted in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeleteTDRedem -Res-PK- This is the response message which is sent back to the external system when a redemption request is deleted from Oracle FLEXCUBE UBS. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the redemption in the Oracle FLEXCUBE data store.

5.2.5.4 QueryTDRedem

This is the operation code for querying TD redemption done in Oracle FLEXCUBE. It involves the following messages:

• QueryTDRedem -Req-IO- This is the request message to query the redemption made to TD account in Oracle FLEXCUBE UBS. An external system which intends to query TD redemption has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying TD redemption.
• QueryTDCustAcc -Res-Full- This is the response message which is sent back to the external system when redemption made to TD account successfully queried in Oracle FLEXCUBE UBS. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.6 FCUBSIFService

Oracle FLEXCUBE supports the following operations under this service:

• CreateExtAccEntries
• ReverseExtAccEntries
• CreateRTLResponse

5.2.6.1 CreateExtAccEntries

This is the operation code is for initiating debit or credit settlement transactions in Oracle FLEXCUBE. It involves the following messages:

• CreateExtAccEntries-Req-Full- This is the request message to create debit or credit settlement transactions in Oracle FLEXCUBE. An external system which intends to create debit or credit settlement transactions has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateExtAccEntries-Req-IO- This is the request message to create debit or credit settlement transactions in Oracle FLEXCUBE. An external system which intends to create debit or credit settlement transactions has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating debit or credit settlement transactions.
• CreateExtAccEntries-Res-Full- This is the response message which is sent back to the external system when a debit or credit settlement transaction is successfully created in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateExtAccEntries-Res-PK- This is the response message which is sent back to the external system when debit or credit settlement transaction is successfully created in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the debit or credit settlement transactions in the Oracle FLEXCUBE data store.

5.2.6.2 ReverseExtAccEntries

This is the operation code is for reversing debit or credit settlement transactions in Oracle FLEXCUBE. It involves the following messages:

• ReverseExtAccEntries-Req-Full- This is the request message to reverse debit or credit settlement transactions in Oracle FLEXCUBE. An external system which intends to reverse debit or credit settlement transactions has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ReverseExtAccEntries-Req-IO- This is the request message to reverse debit or credit settlement transactions in Oracle FLEXCUBE. An external system which intends to reverse debit or credit settlement transactions has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating debit or credit settlement transactions.
• ReverseExtAccEntries-Res-Full- This is the response message which is sent back to the external system when a debit or credit settlement transaction is successfully reverse in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ReverseExtAccEntries-Res-PK- This is the response message which is sent back to the external system when debit or credit settlement transaction is successfully reversed in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the debit or credit settlement transactions in the Oracle FLEXCUBE data store.

5.2.6.3 CreateRTLResponse

Oracle FLEXCUBE supports the following operations under this service:

CreateRTLResponse - This is the operation code is for initiating a response to the RTL Block requested from Oracle FLEXCUBE. It involves the following messages:

• CreateRTLResponse-Req-Full - This is the request message to initiate a response to the RTL Block requested from Oracle FLEXCUBE. An external system which intends to send a response to the RTL Block has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateRTLResponse-Req-IO - This is the request message to initiate a response to the RTL Block requested from Oracle FLEXCUBE. An external system which intends to send a response to the RTL Block has to send the request in the format specified. The format of the message is called 'Input-only', which has only those fields that are actually required to send a response to the RTL Block.
• CreateRTLResponse-Res-Full - This is the response message which is sent back to the external system when a response to the RTL Block is successfully processed in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateRTLResponse-Res-PK - This is the response message which is sent back to the external system when a response to the RTL Block is successfully processed in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the response to the RTL Block in the Oracle FLEXCUBE data store.

5.2.7 FCUBSInteractionservice

Oracle FLEXCUBE supports the following operations under this service:

• CreateSpendClass
• ModifySpendClass
• CloseSpendClass
• ReopenSpendClass
• ModifySpEntryClass

5.2.7.1 CreateSpendClass

This is the operation code for creating spend class in Oracle FLEXCUBE. It involves the following messages:

• CreateSpendClass-Req-Full- This is the request message to create spend class in Oracle FLEXCUBE. An external system which intends to create debit or credit settlement transactions has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateSpendClass-Req-IO- This is the request message to create spend class in Oracle FLEXCUBE. An external system which intends to create spend class has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating spend class.
• CreateSpendClass-Res-Full- This is the response message which is sent back to the external system when a spend class is successfully created in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateSpendClass-Res-PK- This is the response message which is sent back to the external system when spend class is successfully created in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.7.2 ModifySpendClass

This is the operation code for modifying spend class parameters in Oracle FLEXCUBE. It involves the following messages:

• ModifySpendClass-Req-Full- This is the request message to modify spend class parameters in Oracle FLEXCUBE. An external system which intends to modify spend class parameters has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifySpendClass-Req-IO- This is the request message to modify spend class parameters in Oracle FLEXCUBE. An external system which intends to modify spend class parameters has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying spend class parameters.
• ModifySpendClass-Res-Full- This is the response message which is sent back to the external system when spend class parameters are successfully modified in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifySpendClass-Res-PK- This is the response message which is sent back to the external system when spend class parameters are successfully modified in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class parameters in the Oracle FLEXCUBE data store.

5.2.7.3 CloseSpendClass

This is the operation code for closing spend class in Oracle FLEXCUBE.

5.2.7.4 ReopenSpendClass

This is the operation code for reopening spend class parameters in Oracle FLEXCUBE.

5.2.7.5 ModifySpEntryClass

This is the operation code for splitting transactions in Oracle FLEXCUBE.

5.2.8 FCUBSICService

Oracle FLEXCUBE supports the following operations under this service:

• CreatePreclosureFactor
• AuthorizePreclosureFactor
• DeletePreclosureFactor
• ModifyPreclosureFactor
• ClosePreclosureFactor
• ReopenPreclosureFactor
• QueryPreclosureFactor

5.2.8.1 CreatePreclosureFactor

This is the operation code for creating preclosure factor in Oracle FLEXCUBE. It involves the following messages:

• CreatePreclosureFactor-Req-Full- This is the request message to create preclosure factor in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreatePreclosureFactor-Req-IO- This is the request message to create preclosure factor in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating preclosure factor.
• CreatePreclosureFactor-Res-Full- This is the response message which is sent back to the external system when a preclosure factor is successfully created in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreatePreclosureFactor-Res-PK- This is the response message which is sent back to the external system when preclosure factor is successfully created in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.8.2 AuthorizePreclosureFactor

This is the operation code for authorizing Preclosure Factor in Oracle FLEXCUBE. It involves the following messages:

• AuthPreclosureFactor-Req-Full- This is the request message to authorize the Preclosure Factor in Oracle FLEXCUBE. An external system which intends to authorize the Preclosure Factor has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthPreclosureFactor -Req-IO- This is the request message to authorize the Preclosure Factor in Oracle FLEXCUBE. An external system which intends to authorize the Preclosure Factor has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for Preclosure Factor.
• AuthPreclosureFactor -Res-Full- This is the response message which is sent back to the external system when a Preclosure Factor is successfully authorized in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthPreclosureFactor -Res-PK- This is the response message which is sent back to the external system when a Preclosure Factor, is authorized in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of theP2P payment parameters in the Oracle FLEXCUBE data store.

5.2.8.3 DeletePreclosureFactor

This is the operation code for deleting Preclosure Factor in Oracle FLEXCUBE. It involves the following messages:

• DeletePreclosureFactor-Req-Full- This is the request message to delete Preclosure Factor in Oracle FLEXCUBE. An external system which intends to delete Preclosure Factor has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeletePreclosureFactor-Req-IO- This is the request message to delete Preclosure Factor in Oracle FLEXCUBE. An external system which intends to delete a Preclosure Factor has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for closing Preclosure Factor.
• DeletePreclosureFactor-Res-Full- This is the response message which is sent back to the external system when Preclosure Factor is successfully deleted in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeletePreclosureFactor-Res-PK- This is the response message which is sent back to the external system when Preclosure Factor is successfully deleted in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the Preclosure Factor in the Oracle FLEXCUBE data store.

5.2.8.4 ModifyPreclosureFactor

This is the operation code for modifying spend class parameters in Oracle FLEXCUBE. It involves the following messages:

• ModifyPreclosureFactor-Req-Full- This is the request message to modify Preclosure Factor in Oracle FLEXCUBE. An external system which intends to modify Preclosure Factor has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyPreclosureFactor-Req-IO- This is the request message to modify Preclosure Factor in Oracle FLEXCUBE. An external system which intends to modify Preclosure Factor has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying Preclosure Factor.
• ModifyPreclosureFactor-Res-Full- This is the response message which is sent back to the external system when Preclosure Factors are successfully modified in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyPreclosureFactor-Res-PK- This is the response message which is sent back to the external system when Preclosure Factors are successfully modified in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the Preclosure Factor in the Oracle FLEXCUBE data store.

5.2.8.5 ClosePreclosureFactor

This is the operation code for closing preclosure factor in Oracle FLEXCUBE

5.2.8.6 ReopenPreclosureFactor

This is the operation code for reopening preclosure factor in Oracle FLEXCUBE

5.2.8.7 QueryPreclosureFactor

This is the operation code for querying preclosure factor done in Oracle FLEXCUBE. It involves the following messages:

• QueryPreclosureFactor -Req-IO- This is the request message to query the preclosure factor in Oracle FLEXCUBE. An external system which intends to query preclosure factor has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying preclosure factor.
• QueryPreclosureFactor-Res-Full- This is the response message which is sent back to the external system when preclosure factor is successfully queried in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.

5.2.9 FCUBSSTService

Oracle FLEXCUBE supports the following operations under this service:

• CreateAccClasMaint
• AutorizeAccClasMaint
• ModifyAccClasMaint
• DeleteAccClasMaint
• QueryAccClasMaint
• CloseAccClasMaint
• ReopenAccClasMain

5.2.9.1 CreateAccClasMaint

This is the operation code for creating account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• CreateAccClasMaint-Req-Full- This is the request message to create account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateAccClasMaint-Req-IO- This is the request message to create account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating account class maintenance factor.
• CreateAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an account class maintenance is successfully created in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateAccClasMaint-Res-PK- This is the response message which is sent back to the external system when an account class maintenance is successfully created in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.9.2 AuthorizeAccClasMaint

This is the operation code for authorizing account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeAccClasMaint-Req-Full- This is the request message to authorize account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeAccClasMaint-Req-IO- This is the request message to authorize account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating account class maintenance factor.
• AuthorizeAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an account class maintenance is successfully authorized in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeAccClasMaint-Res-PK- This is the response message which is sent back to the external system when an account class maintenance is successfully authorized in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.9.3 ModifyAccClasMaint

This is the operation code for modifying account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• ModifyAccClasMaint-Req-Full- This is the request message to modify account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyAccClasMaint-Req-IO- This is the request message to modify account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying account class maintenance factor.
• ModifyAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an account class maintenance is successfully modified in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyAccClasMaint-Res-PK- This is the response message which is sent back to the external system when an account class maintenance is successfully modified in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.9.4 DeleteAccClasMaint

This is the operation code for deleting account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• DeleteAccClasMaint-Req-Full- This is the request message to delete account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeleteAccClasMaint-Req-IO- This is the request message to delete account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for deleting account class maintenance factor.
• DeleteAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an account class maintenance is successfully deleting in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeleteAccClasMaint-Res-PK- This is the response message which is sent back to the external system when an account class maintenance is successfully deleting in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.9.5 QueryAccClasMaint

This is the operation code for querying account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• QueryAccClasMaint-Req-Full- This is the request message to querying account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• QueryAccClasMaint-Req-IO- This is the request message to querying account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying account class maintenance factor.
• QueryAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an account class maintenance is successfully querying in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• QueryAccClasMaint-Res-PK- This is the response message which is sent back to the external system when an account class maintenance is successfully querying in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.9.6 CloseAccClasMaint

This is the operation code for closing account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• CloseAccClasMaint-Req-Full- This is the request message to closing account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CloseAccClasMaint-Req-IO- This is the request message to closing account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for closing account class maintenance factor.
• CloseAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an account class maintenance is successfully closing in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CloseAccClasMaint-Res-PK- This is the response message which is sent back to the external system when an account class maintenance is successfully closing in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.9.7 ReopenAccClasMain

This is the operation code for reopening account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• ReopenAccClasMaint-Req-Full- This is the request message to reopening account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ReopenAccClasMaint-Req-IO- This is the request message to reopening account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for reopening account class maintenance factor.
• ReopenAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an account class maintenance is successfully reopening in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ReopenAccClasMaint-Res-PK- This is the response message which is sent back to the external system when an account class maintenance is successfully reopening in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.10 FCUBSIAService

Oracle FLEXCUBE supports the following operations under this service:

• CreateIAAccClass
• AuthorizeIAAccClass
• ModifyIAAccClass
• DeleteIAAccClass
• QueryIAAccClass
• CloseIAAccClass
• ReopenIAAccClass

5.2.10.1 CreateIAAccClasMaint

This is the operation code for creating IA account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• CreateIAAccClasMaint-Req-Full- This is the request message to create IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CreateIAAccClasMaint-Req-IO- This is the request message to create IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating IA account class maintenance factor.
• CreateIAAccClasMaint-Res-Full- This is the response message which is sent back to the external system when IA account class maintenance is successfully created in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CreateIAAccClasMaint-Res-PK- This is the response message which is sent back to the external system when IA account class maintenance is successfully created in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.10.2 AuthorizeIAAccClasMaint

This is the operation code for authorizing IA account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• AuthorizeIAAccClasMaint-Req-Full- This is the request message to authorize IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• AuthorizeIAAccClasMaint-Req-IO- This is the request message to authorize IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for creating IA account class maintenance factor.
• AuthorizeIAAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an IA account class maintenance is successfully authorized in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• AuthorizeIAAccClasMaint-Res-PK- This is the response message which is sent back to the external system when IA account class maintenance is successfully authorized in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.10.3 ModifyIAAccClasMaint

This is the operation code for modifying IA account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• ModifyIAAccClasMaint-Req-Full- This is the request message to modify IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ModifyIAAccClasMaint-Req-IO- This is the request message to modify IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for modifying IA account class maintenance factor.
• ModifyIAAccClasMaint-Res-Full- This is the response message which is sent back to the external system when IA account class maintenance is successfully modified in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ModifyIAAccClasMaint-Res-PK- This is the response message which is sent back to the external system when IA account class maintenance is successfully modified in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.10.4 DeleteIAAccClasMaint

This is the operation code for deleting IA account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• DeleteIAAccClasMaint-Req-Full- This is the request message to delete IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• DeleteIAAccClasMaint-Req-IO- This is the request message to delete IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for deleting IA account class maintenance factor.
• DeleteIAAccClasMaint-Res-Full- This is the response message which is sent back to the external system when an IA account class maintenance is successfully deleted in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• DeleteIAAccClasMaint-Res-PK- This is the response message which is sent back to the external system when IA account class maintenance is successfully deleted in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.10.5 QueryIAAccClasMaint

This is the operation code for querying IA account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• QueryIAAccClasMaint-Req-Full- This is the request message to querying IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• QueryIAAccClasMaint-Req-IO- This is the request message to querying IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for querying account class maintenance factor.
• QueryIAAccClasMaint-Res-Full- This is the response message which is sent back to the external system when IA account class maintenance is successfully queried in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• QueryIAAccClasMaint-Res-PK- This is the response message which is sent back to the external system when IA account class maintenance is successfully queried in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.10.6 CloseIAAccClasMaint

This is the operation code for closing IA account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• CloseIAAccClasMaint-Req-Full- This is the request message to closing IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• CloseIAAccClasMaint-Req-IO- This is the request message to closing IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for closing account class maintenance factor.
• CloseIAAccClasMaint-Res-Full- This is the response message which is sent back to the external system when IA account class maintenance is successfully closed in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• CloseIAAccClasMaint-Res-PK- This is the response message which is sent back to the external system when IA account class maintenance is successfully closed in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.10.7 ReopenIAAccClasMain

This is the operation code for reopening IA account class maintenance factor in Oracle FLEXCUBE. It involves the following messages:

• ReopenIAAccClasMaint-Req-Full- This is the request message to reopening IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• ReopenIAAccClasMaint-Req-IO- This is the request message to reopening IA account class maintenance in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for reopening account class maintenance factor.
• ReopenIAAccClasMaint-Res-Full- This is the response message which is sent back to the external system when IA account class maintenance is successfully reopened in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• ReopenIAAccClasMaint-Res-PK- This is the response message which is sent back to the external system when IA account class maintenance is successfully reopened in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.11 FCUBSRTService

Oracle FLEXCUBE supports the following operations under this service:

• UpdateAccPassbook
• IssueAccPassbook
• RePrintAccPassbook

5.2.11.1 UpdateAccPassbook

This is the operation code for updating passbook in Oracle FLEXCUBE. It involves the following messages:

• UpdateAccPassbook-Req-Full- This is the request message to updating passbook in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• UpdateAccPassbook-Req-IO- This is the request message to updating passbook in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for updating passbook.
• UpdateAccPassbook-Res-Full- This is the response message which is sent back to the external system when passbook is successfully updated in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• UpdateAccPassbook-Res-PK- This is the response message which is sent back to the external system when passbook is successfully updated in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.11.2 IssueAccPassbook

This is the operation code for issuing passbook in Oracle FLEXCUBE. It involves the following messages:

• IssueAccPassbook-Req-Full- This is the request message to issuing in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• IssueAccPassbook-Req-IO- This is the request message to issuing passbook in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for closing account class maintenance factor.
• IssueAccPassbook-Res-Full- This is the response message which is sent back to the external system when passbook is successfully issued in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• IssueAccPassbook-Res-PK- This is the response message which is sent back to the external system when passbook is successfully issued in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.

5.2.11.3 RePrintAccPassbook

This is the operation code for reprinting passbook in Oracle FLEXCUBE. It involves the following messages:

• RePrintAccPassbook-Req-Full- This is the request message to reprinting passbook in Oracle FLEXCUBE. An external system has to send the request in the format specified. The format of the message is called 'Full-screen', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE front-end screen.
• RePrintAccPassbook-Req-IO- This is the request message to reprinting passbook in Oracle FLEXCUBE. An external system has to send the request in the specified format. The format of the message is called 'Input-only', which has only those fields that are actually required for reopening account class maintenance factor.
• RePrintAccPassbook-Res-Full- This is the response message which is sent back to the external system when passbook is successfully reprinted in Oracle FLEXCUBE. The format of the message is called 'Full-screen response', which includes all the fields (input fields and the display fields) as in the corresponding Oracle FLEXCUBE screen.
• RePrintAccPassbook-Res-PK- This is the response message which is sent back to the external system when passbook is successfully reprinted in Oracle FLEXCUBE. The format of the message is called 'Primary-Key response', which includes only the primary key fields of the spend class in the Oracle FLEXCUBE data store.