Home

Gateway Functions User Manual

1. Input By Authorized By Modification Date Time Date Time Number M authorized M Open In Notification Enroutes Detailed screen you define the following details Branch Specify a branch for which you wish to define a topic If you want to use a single topic for all branches and for a given notification code you can use a wildcard Once you select a Branch Code the corresponding description is displayed Notification Code Select a notification code from the list of notification codes provided You can indicate a wildcard if a single topic needs to be used for all notifications in a branch Topic Queue Name Define a topic or a queue here If you define a topic you can assign multiple notification codes for a branch In case of a queue you can define only one notification code for each branch 3 21 ORACLE 3 8 1 Viewing Summary screen You can view and query the list of notifications enroute using the Notifications Enroutes Summary screen You can invoke this screen by typing GWSNTFEN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Ct Advanced Search 9 Reset Authorization Status Record Status v Branch Code laz Notification Code laz Destination Name az Records perpage 15 y LFirst Previous 4 of 4 LNext Last Go Authorization Status Record Status Branch Code Notification Code D
2. Message Exchange Pattern Queue Request Message InputOnly Default Response Queue 9 Response Message FullScreen v Dead Letter Queue e Register Response Queue Message Id XSD Validation Required External System Queues I I a 1 In Queue Response Queue 4 Fields FTP Parameters Input By Authorized By Modification Date Time Date Time Number WB Authorized M Open The various details required by the External System Detailed screen are described below Specifying External System Details External System Specify a name for the external system This should be the same as the Source in an incoming message Description Specify a brief description for the External System Indicating Correlation Pattern Request You can define a way in which the external system should correlate its request message with the response message You can choose Message ID of a request message as the Correlation ORACLE ID in the response message Alternatively you can choose Correlation ID of a request message and maintain it as the Correlation ID of the corresponding response message Specifying Message Exchange Pattern Request Message You can choose the Request message to be Full Screen or Input Only If you select Full Screen as the request message the response message will also display
3. os ORACLE 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 6 2 2 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 10 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 fie
4. 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 6 2 5 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 includ
5. This is the operation code for querying LD simulation contract in Oracle FLEXCUBE It involves the following messages DeleteQueryLDSIMContract Req 10 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 ple ORACLE 6 2 4 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 lO This
6. which has only those fields that are actually required for amending an FT contract AmendFTContract Res Full This is the response message which is sent back to the external system when FT contract is successfully amended 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 AmendFTContract Res PK This is the response message which is sent back to the external system when an existing FT contract is successfully amended in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the FT contract in the Oracle FLEXCUBE data store on ORACLE 6 2 1 8 QueryFTContract This is the operation code for querying FT contract in Oracle FLEXCUBE It involves the following messages QueryFTcontract Req Full This is the request message to query FT contract in Oracle FLEXCUBE UBS An external system which intends to query FT 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 QueryFTContract Req lO This is the request message to query FT contract in Oracle FLEXCUBE UBS An external system which intends to query FT contract has to send the request in
7. CreateVirAcc Req lO 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 6 2 2 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 aN ORACLE called Full screen which includ
8. Error Handling On Exception Reject On Override Post Upload Status Authorized Purge Days Calendar Allow Deferred Processing Allow EOD with Deferred _ Allow Delete Fields Function ld Preferences Input By Authorized By Modification Date Time Date Time Number E authorized al Open The following details are captured here Source Code Select Source Code from the option list Depending on the source code you select here data is uploaded from that source into Oracle FLEXCUBE Module Code You can choose to upload data from a source directly onto a module in FLEXCUBE Indicate the module into which you would like to upload data from a given source On Override Oracle FLEXCUBE generates override messages in case it encounters any discrepancies during data upload You can choose to do any of the following e Ignore Select this option to ignore such error messages and continue with the upload process a ORACLE 3 2 5 e Put on Hold Select this option to put the record on hold for user intervention later e Reject Select this option to reject the record On Exception In case a serious error occurs during data upload Oracle FLEXCUBE generates an error message You can choose to put the record with the error on hold In such a case choose Put on Hold from the list of options available If you would like to reject the record altogether choose Reject Post Upload Status If
9. Password and Message ID as input Message ID present as part of the header in Request XML is considered as hash External System generates an unique Message ID which is functional mandatory field in the header Create a Message Digest with SHA 512 algorithm The hash created from the previous step and the password in clear text together is encrypted in DESede encryption method Apply Base64 encoding to encrypted value and send to the Oracle FLEXCUBE gateway Incoming Message Browser The messages received from the external system will be displayed in the Incoming Message Browser You can invoke the Incoming Message Browser screen by typing GWDINBRWV in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button gt Incoming Message Browser E New 3 Enter Query Message Reference External System Message Id Correlation Id Message Status Service Name Operation Code Branch FLEXCUBE Reference User ld Their User Id Branch Date Queue Name Server Date Stamp Request Queue Message ld Repair Reason Gateway Messaging View a Message Reference LevelNumber Tagld Tag Name Node Parentld P In the Incoming Message Browser screen you can view the details of the messages received from the external systems You can also view the messages
10. 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 lO 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 call
11. Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen DeleteMt101 Res PK This is the response message which is sent back to the external system when Mt101 message 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 MT101 message in the Oracle FLEXCUBE data store 6 2 1 4 ModifyMt101 This is the operation code for modifying Mt101 message in Oracle FLEXCUBE It involves the following messages ModifyMt101 Req Full This is the request message to modify Mt101 message in Oracle FLEXCUBE UBS An external system which intends to close an MT101 message 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 ModifyMt101 Req lO This is the request message to modify Mt101 message in Oracle FLEXCUBE UBS An external system which intends to modify an MT101 message 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 MT101 message ModifyMt101 Res Full This is the response message which is sent back to the external system when Mt101 message is successfully modified in Oracle FLEX
12. OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results Outgoing Message Browser Once the incoming messages have been processed a response message will be sent to the external systems along with the status of the processed messages The response messages will be displayed in the Outgoing Message Browser You can invoke the Outgoing Message a5 ORACLE Browser screen by typing GWDOTBRW in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button 4 Outgoing Message Browser E New E3 Enter Query Message Reference External System Message ld Correlation ld Message Status Service Name Operation Code Branch FLEXCUBE Reference User ld Their User ld Server Date Stamp Response Queue Message Id Branch Date Queue Name Related Message Reference Repair Reason Gateway Messaging View Message Reference Level Number Tagld Tag Name Node Parentld P In the Outgoing Message Browser screen you can view the details of the messages sent to the external systems You ca
13. 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 oF ORACLE Create TDTopUp 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 6 2 2 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 lO 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 calle
14. as in the corresponding Oracle FLEXCUBE screen CreateMt101 Res PK This is the response message which is sent back to the external system when an Mt101 message 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 MT101 message in the Oracle FLEXCUBE data store 6 2 1 2 AuthorizeMt101 This is the operation code for authorizing MT101 message in Oracle FLEXCUBE It involves the following messages AuthorizeMt101 Req Full This is the request message to authorize Mt101 message in Oracle FLEXCUBE UBS An external system which intends to authorize 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 AuthorizeMt101 Req lO This is the request message to authorize Mt101 message in Oracle FLEXCUBE UBS An external system which intends to authorize MT101 message has to send the request in the specified format The format of the message is called Input only which has only those fields that can be used to query AuthorizeMt101 Res Full This is the response message which is sent back to the external system when Mt101 message is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input
15. e Systems that are not EJB literate i e are not capable establishing a connections with Oracle FLEXCUBE based upon the EJB interface and or e Systems that prefer to use a simple http message based approach without wanting to use SOAP as the standard In this deployment pattern the external system will make an HTTP request to the Oracle FLEXCUBE servlet For this deployment pattern Oracle FLEXCUBE will display a single servlet The actual request will be in the form of an XML message This XML message is embedded into the body of the HTTP request sent to the Oracle FLEXCUBE servlet After the necessary processing is done in Oracle FLEXCUBE based on the request the response is returned to the external system as an XML message which is once again embedded within the body of the response HTTP message The transaction control for the processing will stay with the Oracle FLEXCUBE MDB Based Asynchronous Deployment Pattern The MDB deployment pattern is used in integration scenarios where the external system connecting to Oracle FLEXCUBE wants to connect to Oracle FLEXCUBE using JMS queues This is especially applicable to systems such as the following 2 2 ORACLE 2 3 2 4 2 5 e Systems that prefer to use JMS queues based approach without wanting to wait for the reply Here external system sends messages in XML format to request queue on which an MDB is listening When a message arrives on the queue it is picked up for p
16. 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 6 2 5 2 AccountStructureModify This is the operation code for modifying account structure in Oracle FLEXCUBE lt 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 lO 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 fiel
17. 2 ModifyPTPBen This is the operation code for modifying P2P beneficiary account in Oracle FLEXCUBE It involves the following messages ModifyPTPBen Req Full This is the request message to modify P2P beneficiary account in Oracle FLEXCUBE UBS An external system which intends to modify a P2P beneficiary 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 ModifyPTPBen Req lO This is the request message to modify P2P beneficiary account in Oracle FLEXCUBE UBS An external system which intends to modify an P2P beneficiary 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 P2P beneficiary account ModifyPTPBen Res Full This is the response message which is sent back to the external system when P2P beneficiary 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 ModifyPTPBen Res PK This is the response message which is sent back to the external system when P2P beneficiary account is successfully modified in Oracle FLEXCUBE UBS The format of the message is called
18. Full Screen Response Message You can choose the Response message to be Full Screen or Record Identification Msg Note You can select Record Identification Msg as the response message only if you select In put Only in the request message Specifying Queue Details Default Response Queue You can define a response queue for each of the In Queue s through which the External System will communicate with Oracle FLEXCUBE Define a valid queue name as the Default Response Queue Dead Letter Queue If the messages received are non readable such messages are directed to Dead Letter Queue defined for the external system Note If the Dead Letter Queue is not defined such messages will be redirected to a queue with the name of the request queue appended with _E XSD Validation Required Check this box to indicate if the request message should be validated against its corresponding XSD Register Response Queue Message ID Check this box to indicate if the message ID provided by the Response Queue should be logged when a response message is posted into the queue Specifying External System Queue Details The External System Queues list contains the In Queue and Response Queue lists To add a record to the External System Queues list click add icon To delete a record from the list select the record using its check box and then click delete icon In Queue Spe
19. Oracle FLEXCUBE It involves the following messages e 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 e AuthorizeTDRedem Req lO 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 e 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 e 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
20. Primary Key response which includes only the primary key fields of the P2P beneficiary account in the Oracle FLEXCUBE data store 6 2 7 3 DeletePTPBen This is the operation code for deleting P2P beneficiary account in Oracle FLEXCUBE It involves the following messages DeletePTPBen Req Full This is the request message to delete P2P beneficiary account in Oracle FLEXCUBE UBS An external system which intends to delete P2P beneficiary 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 DeletePTPBen Req lO This is the request message to delete P2P beneficiary account in Oracle FLEXCUBE UBS An external system which intends to delete a P2P beneficiary account has to send the request in the specified format The format of the orar ORACLE message is called Input only which has only those fields that are actually required for closing P2P beneficiary account DeletePTPBen Res Full This is the response message which is sent back to the external system when P2P beneficiary 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 DeletePTPBen Res PK This is the response message
21. The following chart will depict a clear picture of request information that pass on to the various stages that are discussed Change server state to S after Add param HOST to header Send request to HOST Process request build response Reject the request complet e Sync change state toA Change server state to U Send error message Add param POSS to header Send request to a AN Log request additionally in a separate table y Process request build response Update POSS log table Start gt synchronization Response ELCM Impact Replay Complete All requests replaved Incomplete r incomplete y H 4 Replay Routine k When the request comes two ELCM gateways are deployed pointing towards the Host and the POSS The external interface at ELCM will be switched off and the transactions which are initiated through FLEXCUBE will be serviced Services Supported during Outage The following Services are supported during Planned Outage FCUBSFT Service The operations that are supported under FCUBSFT services are e Cancel FT Contract e Create FT Contract FCUBSPC Service The operations that are supported under FCUBSFT services are 7 3 ORACLE 7 3 3 7 3 4 7 3 5
22. e 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 e CreateTDRedem Req lO 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 e 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 e 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 6 2 6 2 AuthorizeTDRedem This is the operation code for authorizing redemption request of TD in
23. includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen at ORACLE LDActivateSimulate Req lO 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 6 2 4 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 requ
24. integration needs The Synchronous Deployment Pattern is classified into the following e Oracle FLEXCUBE EJB Based Synchronous Inbound Application Integration Deployment Pattern e Oracle FLEXCUBE Web Services Based Synchronous Inbound Application Integration Deployment Pattern e Oracle FLEXCUBE HTTP Servlet Based Synchronous Inbound Application Integration Deployment Pattern Asynchronous Deployment Pattern is e Oracle FLEXCUBE MDB Based Asynchronous Inbound Application Integration Deployment Patten EJB Based Synchronous Deployment Pattern The Enterprise Java Beans EJB deployment pattern will be used in integration scenarios where the external system connecting to Oracle FLEXCUBE is EJB literate i e the external system is capable of interacting with Oracle FLEXCUBE based upon the EJB interface In this deployment pattern the external system will use the RMI IIOP protocol to communicate with the Oracle FLEXCUBE EJB In this deployment pattern the EJB displayed by Oracle FLEXCUBE will be a stateless session bean The actual request will be in the form of an XML message After the necessary a ORACLE 2 2 2 2 2 3 2 2 4 processing is done in Oracle FLEXCUBE based on the request the response is returned to the external system as an XML message The transaction control for the processing will stay with the Oracle FLEXCUBE EJB Web Services Based Synchronous Deployment Pattern The web services deploymen
25. 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 6 2 4 5 LDVamiQuerySim This is the operation code for querying LD VAMI Simulation contract in Oracle FLEXCUBE It involves the following messages LDVamiQuerySim Req lO 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 Inp
26. message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen ModifyPTPPrm Res PK This is the response message which is sent back to the external system when P2P payment parameters 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 P2P payment parameters in the Oracle FLEXCUBE data store 6 2 8 3 DeletePTPPrm This is the operation code for deleting P2P payment parameters in Oracle FLEXCUBE It involves the following messages DeletePTPPrm Req Full This is the request message to delete P2P payment parameters in Oracle FLEXCUBE An external system which intends to delete P2P payment 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 DeletePTPPrm Req lO This is the request message to delete P2P payment parameters in Oracle FLEXCUBE An external system which intends to delete a P2P payment 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 closing P2P payment parameters DeletePTPPrm Res Full This is the response message which is sent back t
27. system using the External System Functions Detailed screen You can invoke this screen by typing GWDEXFUN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 4 External System Functions Detailed E New E3 Enter Query External System Description Function Action Service Name Operation Code Input By Authorized By Modification Date Time Date Time Number M Authorized M Open In the above screen you need to specify the following details EA ORACLE 3 2 1 External System Select an external system for which you wish to provide access rights The adjoining option list displays all the external systems you have maintained in the External Systems Detailed screen Function ID Select a Function ID from the list of values by clicking the adjoining option list The function ids are invoked from Gateway Functions Action Select an action for the external system from the option list provided Service Name This displays the service name based on the Function ID and Action you select Operation Code This displays the Operation Code based on the Function ID and Action you select Viewing External System Function Details You can view the access rights details which have already been defined using the External System Functions Summary screen as shown below You can invoke this screen by typing G
28. 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 lO 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 ee ORACLE 6 2 2 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 i
29. 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 lO 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 v
30. 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 6 2 10 FCUBSInteractionservice Oracle FLEXCUBE supports the following operations under this service CreateSpendClass ModifySpendClass CloseSpendClass ReopenSpendClass ModifySpEntryClass 6 2 10 1 CreateSpendClass This is the operation code for creating spend class in Oracle FLEXCUBE It involves the following messages
31. unique id which indicates overrides FUNCTIONID This indicates the Oracle FLEXCUBE Function ID MSGSTAT This indicates whether the transaction is a SUCCESS or FAILURE ADDL This is used to send additional parameters i e parameters not available in Oracle FLEXCUBE 44 ORACLE 4 2 2 4 2 2 1 4 2 2 2 FCUBS BODY The FCUBS_ BODY will contain the actual payload to perform the respective transaction The contents of the payload will vary for each operation The following snapshot shows a sample FCUBS_ BODY of QUERYCUSTACC operation CustAccount Query 10 Type Cust Account 10 FCUBS_BODY FCUBS_BODY will contain additional nodes for error response and warning response A diagrammatic representation of the Error response is as shown below ERRORType O ETE i ECODE ah eed FCUBS ERROR_RESP The error response message will be sent from Oracle FLEXCUBE when errors are raised in a transaction The error response will have another tag ERROR within it ERROR The ERROR node will have tags for error code and error description The ERROR node will be generated for each error raised by FCUBS FCUBS WARNING RESP The warning response message will be sent when overrides are raised in a transaction The Warning response will have another tag WARNING within it ORACLE 4 3 4 3 1 WARNING This node will have tags for warning code
32. you would like to automatically authorize the data that is uploaded into Oracle FLEXCUBE choose the Authorize option here If you would like the record to be put on hold choose this option in this field If you would like the record to be unauthorized choose the Unauthorized option in this field The record will not be authorized automatically on upload You will have to manually authorize the data Purge Days Calendar Specify the days maintained for purging of the data uploaded Allow Deferred Processing Check this option to defer processing of amendment and cancellation uploads Allow EOD with Deferred Check this option to proceed even if the records exist in the deferred processing log If it is unchecked then the EOD process halts until the deferred process log is cleared Allow Delete Check this option to delete the process log Maintaining Function ID Preferences Click Function ID Preferences button in the Upload Source Preferences Maintenance screen Preferences Function Id Preferences HEE E Function Id Status On Exception On Override Proceed With EOD Deleted Allowed Reverse Allowed ja Authorized gt Reject gt Ignore AA a a You can enter the following details ORACLE 3 3 Function Id Specify the function ID The adjoining option list displays all the function Ids maintained in the system Select the appropriate one Sta
33. 7 3 6 7 3 7 7 3 8 7 3 9 e Create PC Contract e Create PC Maint e Close PC Contract e Create PC ClientAgg FCUBSSI Service The operations that are supported under FCUBSSI services are e Create SI Contract e Close SI Contract FCUBSTD Service The operations that are supported under FCUBSTD services are e Create TDAcc e Query TDRedemption FCUBSCL Service The FCUBSCL services support the Save Payment operation FCUBSLD Service The operations that are supported under FCUBSLD services are e Create LD Contract e Create LD Payment FCUBSAcc Service The operations that are supported under FCUBSAcc services are e Create CustAcc e Check Book New FCUBS Customer Service The operations that are supported under FCUBS Customer services are e Create Customer e Modify Customer e Modify CustAcc e Query CustAcc FCUBSIL Service The operations that are supported under FCUBSIL services are e Close ILSweep e Delete ILSweep e Query ILSweep e Modify ILSweep e Create ILSweep is ORACLE 7 3 10 7 3 11 7 3 12 7 3 13 e Close ILGroup e Delete ILGroup e Query ILGroup e Modify ILGroup e Create ILGroup FCUBSLC Service The operations that are supported under FCUBSLC services are e Create LCContract e Modify LCContract FCUBSFX Service The FCUBSFX services support the Create FX Contract operation FCUBSCG Service The FCUBSCG services supp
34. CUBE 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 ModifyMt101 Res PK This is the response message which is sent back to the external system when Mt101 message 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 MT101 message in the Oracle FLEXCUBE data store Note Oracle FLEXCUBE allows modification only before the first authorization 6 2 1 5 QueryMt101 This is the operation code for querying Mt101 message in Oracle FLEXCUBE It involves the following messages QueryMt101 Req Full This is the request message to query Mt101 message in Oracle FLEXCUBE UBS An external system which intends to query an MT101 message 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 QueryMt101 Req lO This is the request message to query Mt101 message in Oracle FLEXCUBE UBS An external system which intends to query an MT101 message 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 an MT101 message ee ORACLE Q
35. CUBSDDS OMVICO coincido ita tataspda 6 14 6 24 PCUBSEDS6MNic Soo isa 6 15 6 2 5 FCUBSCUStOMErSCIVICE sssini ina siriiia eerie diarioen dakai cc naar rra 6 18 6 2 6 FCUBSTDSOViCO cian d 6 24 6 2 7 FCUBSPCSEIViC6 a cecilia es eet etn hiara ans 6 26 6 2 8 FCUBSEXtPCSIVICE a a e a a a a a a a a aaa a Aaa EASA Aias 6 29 6 2 9 FOUBSIF SOMO e a a a a aaa aaraa 6 31 6 2 10 FCUBSInteractionservice ccoooooconnniocccccinnocncccnn nano nc cc nn nan rnc cnn narran 6 32 Planned Outage Support Server occococccccnonccononcnoncnnnnnnnnenonnnnnnanonananananns 7 1 LA INTO UCI it a A A AA A A AR 7 1 7 2 Handling Planned Outages oooooccccninnnnccccnnncccccccnonanonccnnnnnnnn cnica AET 7 1 A A O ET 7 1 Fea Oulage Slate Bini E ee i ea i 7 1 7 2 3 Host Down and POSS Up cocococccccccccnccnconannnnnnnnccnncnncnnncnnnnnnnnn nn nnnnnncnnnnnnnnnnns 7 2 7 2 4 Host Up Start Replay from POSS 2 c ccsceeeeceeceseeceteeteetecneaaeeseeeeesenens 7 2 C25 ELCM lmpact sins se a A ete 7 3 7 3 Services Supported during Outage ooococccinnnoccccnnnoconcccnnnononcconnnanr coca nn nan nc cnn 7 3 C34 SFCUBSFT SOM E a a lali 7 3 132 PCUBSPC Service waist rat ei aia da aia os 7 3 133 FPCEUBSSIESOIVICO i 2 8 yi adaesiseseetits is dade inte sees ean a iaaeaie aes 7 4 1 314 FCUBSTD SEV Oneni or iania dd iia 7 4 130 PFCUBSCL S IViC0iu 8 nis iio innate eal aint 7 4 1 305 PFCUBSLD SOIVICO 3 ati a ar aaa aioe tia geese 7 4 IT FCUBSACCSCFVICG aaa okey E E E
36. 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 b ag ORACLE CreateSpendClass Req lO 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 6 2 10 2 ModifySpendClass This is the operation code for mod
37. Dead Letter Queue e Record Status e Default Response Queue The Result list shows the external systems which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search me ORACLE 3 1 7 3 2 Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results Accessing Services and Operations In a message it is mandatory to maintain a list of Service Names and Operation Codes This information is called Gateway Operations A combination of every such Service Name and Operation Code is mapped to a combination of Function ID and Action Every screen in Oracle FLEXCUBE is linked with a function ID This information is called Gateway Functions You can gain access to an external system using the Gateway Functions The Function IDs mapped in Gateway Functions should be valid Function IDs maintained in Oracle FLEXCUBE Hence for every new Service or Operation being introduced it is important that you provide data in Gateway Operations and Gateway Functions Refer the Message Formats chapter for more information on Services and Operations Defining Access Rights to an External System You can define access rights to an external
38. E data store 6 2 5 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 ModifyAmtBIk CloseAmtBlk CreateCustomer ModifyCustomer AuthorizeCustomer QueryCustomer CreateClosureData AuthorizeClosureData ModifyClosureData 6 2 5 1 QueryClosureDataAccountStructureNew 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 ate ORACLE 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 10 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
39. EE seen eee 7 4 7 3 8 FCUBS Customer SCrviCe sirist erriren artir isie A RAE EE 7 4 13 9 FCUBSIL Srv coca iii is it e tet beat Laas 7 4 13 10 PCUBSEC SEMICON iesire naaa a e aa ieoi ias 7 5 TIT FECUBSEX SOIVICO 0 AA EE E AEA TAE TEE 7 5 13 12 FCUBSCG SM E a a a a a naaa a Sea 7 5 7 3 13 FCUBSSWitCh Service a a a a aa a aaaea 7 5 8 Function ID Glossary ii 8 1 1 1 1 2 1 3 1 4 1 5 1 Preface Introduction This manual is designed to help you quickly get acquainted with the Integration Gateway of Oracle FLEXCUBE It provides an overview to the module and provides information on using the Integration Gateway module of Oracle FLEXCUBE You can further obtain information specific to a particular field by placing the cursor on the relevant field and striking lt F1 gt on the keyboard Audience This manual is intended for the following User User Roles Role Function IT department members responsible Input functions for maintenance related for integration to the gateway IT managers Authorization functions Documentation Accessibility For information about Oracle s commitment to accessibility visit the Oracle Accessibility Program website at http Avww oracle com pls topic lookup ctx acc amp id docacc Acronyms and Abbreviations Abbreviation Description FLEXCUBE FLEXCUBE Universal Banking Solu UBS tion Organization The manual is organized i
40. FO UC 122 A aa aa aak ee ae ee eee eee 4 1 42 Oracle FLEXCUBE Envelope ccccccecceceeeeseeeeencecaeeceeeeeeeeeeeseesececncaeeeeeeeeeeeeess 4 2 4 2 1 PCUBS HEADERS a rial ine itis Gaia alana ates 4 3 42 27 FC UBS BODY ls ie tee Pasi dl hanes a 4 5 4 3 Oracle FLEXCUBE NOTIFICATION cccccceceeeceeeeeeececeeeeeeseeeseaeeeseaeeetsnesenaaees 4 6 4 3 1 FCUBS NOTIFICATION HEADER 2 cccccccceceeeeeeneeeteeneseseseeetseseteeseees 4 6 FLEXML Adapter Message Conversion c ccccccccereeeeeeeeeeeeeeeeneeeeees 5 1 Bids e E RS 5 1 5 2 Inbound FLEXML Adapter oooooooccccccccccccccnccnnonnnononnnnnnnnnnnnnnnnnnnnnn non nnnnnnnnnnnnnannnannnnnes 5 1 5 2 1 Processing Incoming FLEXML Request Message ooococcciccoccccccoccnccccccnnnnos 5 2 5 3 Outbound FLEXML Adapter coccccccccccncnnconoononccnncnnonnncnncnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnannnnnnnnes 5 2 5 3 1 Processing Outbound MeSsages coonococcccnnnnnoncccconananccccnnannnnccnnnann nn ncnann nn 5 2 5 3 2 Mapping FLEXML Format Messages to Gateway Format ooooconinociciccccn ns 5 3 Annexure List of Messages mmmmmononcccccccncccnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnes 6 1 A a A ded dh eee ie beens ase nai ede sane E a aaa ae aaa 6 1 6 2 Inbound Application Integration Services cceceeeeeeeeceeceeeeeeeeeeeeteeteeeeenenaeees 6 1 6 2 1 FCUBSEFTSOV ICO ld ai ono aed ain 6 1 6 2 2 IECUBSACCOSOIVICO escorias casaca E A EANTA A batea 6 5 6 2 3 F
41. ION should be Oracle FLEXCUBE For response messages system will populate the SOURCE of the request message as DESTINATION Refer Service Documentation available under Gateway for details about each message Aee ORACLE 5 1 5 2 5 FLEXML Adapter Message Conversion Introduction FLEXML Adapter is a component which facilities the communication between existing FLEXML enabled systems and newer version of Oracle FLEXCUBE based on Gateways The messages are converted from FLEXML format to Gateway format and vice versa The diagram given below indicates that the adapter acts as a middle layer facilitating the exchange of messages between FLEXML based systems and the Oracle FLEXCUBE database Flexml Enabled External Syst Adapter Gateway The different channels used by the adapter to communicate with the gateway can be categorized as follows e Inbound FLEXML Adapter e Outbound FLEXML Adapter Inbound FLEXML Adapter Inbound FLEXML Adapter provides an XML based interface for the FLEXML enabled external system to communicate with Oracle FLEXCUBE database It converts the messages from FLEXML format to gateway format and invokes GW EJB which handles further processing of the message The following communication mechanisms are available to process the incoming FLEXML messages e EJB Inbound Adapter This is used if the external system is compatible with EJB interface The external
42. K_RES FCUBS_HEADER CREATECUSTACC_IOPK_RES 7 FCUBS_BODY Query Formats For example consider the Operation QUERYCUSTACC The root node of messages under this operation will be as under e QUERYCUSTACC_IOFS_REQ FCUBS_HEADER QUERYCUSTACC_IOFS_REO 7 e QUERYCUSTACC_IOFS_RES FCUBS_HEADER QUERYCUSTACC_IOFS_RES FCUBS_BODY Oracle FLEXCUBE Envelope A standard gateway message in the Oracle FLEXCUBE Envelope contains two main components namely e FCUBS_HEADER This is a node that forms the header of the FCUBS Envelope The tags under the header portion of a message will identify a partner system a service an operation user branch etc These tags are constant across all messages 2 ORACLE e FCUBS_BODY This node contains the actual payload of a message The contents of this node will vary for each message FCUBS_HEADERType FCUBS_HEADER 4 2 1 FCUBS HEADER The tags under FCUBS HEADER have been described below SOURCE This indicates the name of the External system that is the source of the message UBSCOMP This indicates the Oracle FLEXCUBE component of the message whether FCIS or FCUBS MSGID This unique ID identifies each message incoming or outgoing in Oracle FLEXCUBE Every message will have a distinct message ID Ta ORACLE CORRELID This is the id using which any system which has sent a request to FC UBS can correlate to the r
43. OPERATION gt _ lt MESSAGE EXCHANGE PATTERN gt _REQ e lt OPERATION gt _ lt MESSAGE EXCHANGE PATTERN gt _RES e Where e lt OPERATION gt refers to an Oracle FLEXCUBE operation like CREATECUSTACC e lt MESSAGE EXCHANGE PATTERN refers to the request amp response message patterns exchanged The Message Pattern is of the following types FS Full Screen This indicates that the payload will contain all the elements on the corresponding Oracle FLEXCUBE screen 10 Input Only This indicates that the payload will contain the only input elements on the corresponding Oracle FLEXCUBE screen PK Primary Key This indicates that the payload will contain only the Primary Key elements of the corresponding Oracle FLEXCUBE screen lt MESSAGE_EXCHNAGE_PATTERN gt is a combination of message patterns The lt MESSAGE_EXCHNAGE_PATTERN gt available in FLEXCUBE is shown below e FSFS Full Screen Request and Full Screen Response e lIOPK Input Only Request and Primary Key Response e IOFS Input Only Request and Full Screen Response Non Query Formats For example consider the Operation CREATECUSTACC The root node of messages under this operation will be as under e CREATECUSTACC_FSFS_REQ FCUBS_HEADER CREATECUSTACC_FSFS_REO 7 e CREATECUSTACC_FSFS_RES CREATECUSTACC_FSFS_RES 41 ORACLE 4 2 e CREATECUSTACC_IOPK_REQ FCUBS_HEADER FCUBS_BODY CREATECUSTACC_IOPK_REO 7 e CREATECUSTACC_IOP
44. ORACLE Gateway Services User Guide Oracle FLEXCUBE Universal Banking Release 12 0 3 0 0 Part No E53393 01 April 2014 Gateway Services User Guide April 2014 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon East Mumbai Maharashtra 400 063 India Worldwide Inquiries Phone 91 22 6718 3000 Fax 91 22 6718 3001 www oracle com financialservices Copyright 2007 2014 Oracle and or its affiliates All rights reserved Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerou
45. SNTFIN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button a Advanced Search 9 Reset Authorization Status Record Status Branch Code az Notification Code Records perpage 15 y LFirst Previous 4 of 4 Next Last Go Authorization Status Record Status Branch Code Notification Code Authorizai Record St This summary screen can be used to search for notification messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results 3520 ORACLE 3 8 Defining the Notifications Enroutes You can invoke the Notification Enroutes Detailed screen by typing GWDNTFEN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Notifications En route Ej New E3 Enter Query Branch Code Notification Code Description Description Destination Name
46. WSEXFUN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button C Advanced Search 9 Reset Authorization Status X Record Status X External System Function laz Action az Records perpage 15 y First Previous of 1 Next Last External System Function Authoriza Record St This summary screen can be used to search for external system functions which match any of the following criteria e Authorization Status e External System e Record Status e Action e Function ORACLE 3 2 2 3 2 3 The Result list shows the external system functions which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results Defining Access Rights to a User ID For a User ID to access a request message you can individually map each Function ID to a User ID Note You can provide access to functions only if the Function IDs provided in Gateway Func tions are valid Maintaining Upload Source Details Oracle FLEXCUBE facilitates upload of
47. al 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 lO 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 6 2 2 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
48. al channels to query a customer record in Oracle FLEXCUBE QueryClosureData Req 10 This is the request message to query a customer record in Oracle FLEXCUBE UBS An external system which intends to query a customer record oe ORACLE 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 6 2 5 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 lO This is the request message to create a record in the
49. and warning description The WARNING node will be generated for each override raised by FCUBS Oracle FLEXCUBE NOTIFICATION The notification messages are generated in a standard format The notification messages will consist of two main components FCUBS_NOTIF_HEADER This forms the header portion of a notification message This contains a standard set of tags that can identify a notification These tags are constant across all notification messages FCUBS_NOTIF_IDENTIFIER This will identify the maintenance records based on the information provided under this node The contents of this node will vary for each notification A diagrammatic representation of FCUBS NOTIFICATION is as shown below FCUBS_NOTIF_HEADER FCUBS_NOTIF_IDENTIFIER FCUBS_NOTIFICATION FCUBS_NotifHeaderType FCUBS_HOTIF_HEADER FCUBS NOTIFICATION HEADER The tags under FCUBS NOTIFICATION HEADER have been described below SOURCE This indicates the name of the External system or the source of the message MSGID This is the unique reference number generated by Oracle FLEXCUBE NOTIF_REF_NO This unique reference number identifies each notification message generated in Oracle FLEXCUBE ep ORACLE BRANCH This indicates the branch in which notification has been triggered NOTIF_CODE This indicates the code for the notification that has been triggered DESTINATION For incoming messages the DESTINAT
50. bank This adjoining option list displays all valid branches maintained in the system You can choose the appropriate one External System Specify the name of the external system This adjoining option list displays all the external systems maintained in the system You can choose the appropriate one Module Code Specify the module name This adjoining option list displays all the modules maintained in the system You can choose the appropriate one Service Name Specify the service name of the module selected This adjoining option list displays all the service names maintained in the system You can choose the appropriate one Operation code Specify the operation code of the service This adjoining option list displays all valid operation codes maintained in the system You can choose the appropriate one Effective Date Specify the date from which the gateway message maintenance becomes effective Effective date should be equal to or greater than the application date ay ORACLE 4 1 4 Message Formats Introduction Data exchanged between Oracle FLEXCUBE and the external systems will be in the form of XML messages These XML messages are defined in FCUBS in the form of XML Schema Documents XSD and are referred to as FCUBS formats An XML Schema is uniquely identified by its Namespace and its Root Element root node The root node for XSDs of gateway messages will be generated as per the following pattern e lt
51. can be used if the exter nous MDB nal system chooses to com municate only through JMS queues Handoffs from Asynchro FLEXCUBE UBS Recommended Oracle FLEX nous Notify CUBE 2 7 FLEXML Adapter Oracle FLEXCUBE Gateway is the common channel for data exchange between Oracle FLEXCUBE and external systems But older versions of Oracle FLEXCUBE use FLEXML Gateway to interact with the external systems The message or communication format of FLEXML is different from that of the gateway os ORACLE Hence in order to facilitate the exchange of messages between such systems Oracle FLEXCUBE uses a conversion mechanism called the FLEXML Adapter FLEXML Adapter converts messages from FLEXML format to gateway format and vice versa For more details on the conversion mechanism of FLEXML Adapter refer the chapter FLEXML Adapter Message Conversion ES ORACLE 3 1 3 1 2 3 External System Maintenance Defining an External System You need to define an external system that will communicate with the Oracle FLEXCUBE Integration Gateway You can define an external system using the External System Detailed screen You can invoke this screen by typing GWDEXSYS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button External Systems E New Enter Query External System Correlation Pattern External System Request Message ld Description
52. cify the name of the queue from which the messages were received The name of the queue will help identify the external system Note This is required only if an incoming message does not display the source of the message An In Queue is mapped to only one External System a2 ORACLE You can map multiple queues to a source System will allow a source to post messages to multiple queues Response Queue You can define Response Queue for every In Queue This is required only when the External System fails to display the queue name on posting a request message into the In Queue Viewing External System Details The details of previously defined external Systems can be viewed using the External System Summary screen as shown below You can invoke this screen by typing GWSEXSYS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 44 Advanced Search 9 Reset Authorization Status Record Status v External System 23 Default Response Queue laz Dead Letter Queue az Records per page 15 y First _Previous 4 of 4 Next Last Authorization Status Record Status External System Default Response Queue Dead Letter Queue Authoriza Record St This summary screen can be used to search for external systems which match the data specified for any of the following criteria e Authorization Status e External System e
53. cle 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 6 2 2 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
54. count 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 6 2 2 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 Create TDTopUp Req 10 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
55. d 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 6 2 2 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 10 This is the request message to delete the top up of TD account in Oracle FLEXCUBE UBS An external system which intends to delet
56. d for creating debit or credit settlement transactions e 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 p a ORACLE 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 6 2 9 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 10 This is
57. data from an external source The details of the source from which data has to be uploaded need to be maintained in Oracle FLEXCUBE using the Upload Source Maintenance screen You can invoke the Upload Source Maintenance screen by typing CODSORCE in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 4 Upload Source Definition E New Enter Query Source Code Description Base Data From FLEXCUBE F System Authorization Required Input By Authorized By Modification Date Time Date Time Number Wi Authorized M open S9 ORACLE The following details need to be captured here Source Code Specify a code for the for the source from which data has to be uploaded to Oracle FLEXCUBE Description Give a small description for the source code specified Base Data From FLEXCUBE Check this box to indicate if base data has to be uploaded from Oracle FLEXCUBE 3 2 4 Specifying Upload Source Preferences You can set preferences for upload of data from an external source in the Upload Source Preferences Maintenance screen You can invoke the Upload Source Preferences Maintenance screen by typing CODUPLDM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Upload Source Preferences Maintenance E New amp Enter Query Source Code Module Code
58. ds input fields and the display fields as in the corresponding Oracle FLEXCUBE screen AuthPTPBen Res PK This is the response message which is sent back to the external system when a P2P beneficiary account is authorized in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of theP2P beneficiary account in the Oracle FLEXCUBE data store 6 2 7 5 QueryPTPBen This is the operation code for querying P2P beneficiary account done in Oracle FLEXCUBE It involves the following messages QueryPTPBen Req lO This is the request message to query the P2P beneficiary account in Oracle FLEXCUBE UBS An external system which intends to query P2P beneficiary 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 P2P beneficiary account QueryPTPBen Res Full This is the response message which is sent back to the external system when P2P beneficiary 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 6 2 7 6 ClosePTPBen This is the operation code for closing P2P beneficiary account in Oracle FLEXCUBE ae ORACLE 6 2 7 7 ReopenPTPBen This is the operation code for r
59. ds of the spend class parameters in the Oracle FLEXCUBE data store 6 2 10 3 CloseSpendClass This is the operation code for closing spend class in Oracle FLEXCUBE 6 2 10 4 ReopenSpendClass This is the operation code for reopening spend class parameters in Oracle FLEXCUBE 6 2 10 5 ModifySpEntryClass This is the operation code for splitting transactions in Oracle FLEXCUBE 4 ORACLE 7 1 7 2 7 2 1 7 2 2 7 Planned Outage Support Server Introduction Planned Outage Support Server POSS is the data replica of the host server and facilitates the channels to support the database server without any downtime during the planned outages When POSS is active e EOD will not run e Non Channel Interface has to be switched off e ELCM enterprise has to be switched off e Messaging and notification cannot be done A new server state XML is created for which the path is decided based on the entry in the properties file The XML will contain a parameter lt SERVERSTATE gt which can have any of the following values e A Available e S Sleep e U Unavailable e R Replay Gateway EJB will take the request information from the SSB when the full session bean retains the information Handling Planned Outages The various stages of planned outages are described as below Host Up When the request comes from the channel it will reach the Gateway EJB or MDB and the bean check for the state of server If the s
60. ds 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 6 2 5 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 lO This is the request message to query an account structure in Oracle FLEXCUBE UBS An external system which intends to query a
61. e 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 lO 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 Create Customer 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 6 21 ORACLE 6 2 5 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
62. e 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 910 ORACLE 6 2 2 13 ModifyTDTopUp This is the operation code for modifying account structure in Oracle FLEXCUBE lt 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 lO This is the request message to modify a TD top up in Ora
63. ed Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 5 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 lO 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 6 2 6 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 9 24 ORACLE 6 2 6 1 CreateTDRedem This is the operation code for creating a redemption request of TD in Oracle FLEXCUBE It involves the following messages
64. ed Search 9 Reset Branch Message Id Request Queue Message Id Service Name Operation Code User ld Their User ld Branch Date Server Date Stamp Message Status laz FLEXCUBE Reference Message Reference External System Correlation ld at ana ana a a Records per page 15 First _Previous_ of 4 Next Last co External System Message Idi Correlation ld Request Queue Message Id This summary screen can be used to search for incoming messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results Duplicate Message Browser If Oracle FLEXCUBE Integration Gateway identifies a duplicate message it will be sent to the Duplicate Messages Browser You can invoke the Duplicate Message Browser Summary se ORACLE screen by typing GWSPBROW in the field at the top right corner of the App
65. eferenceS ocooconniccccnnnnnnncccccnanannccccnnnannncninnn 3 7 3 2 5 Maintaining Function ID Preferences cccccccccesteeeteeetteeeeeeeneeeeetseanaeenes 3 8 3 3 Gateway Password Generation Logic For External System Authentication 3 9 3 3 1 Password and Message ID as iNPUt oooonncinincinnnninionnnninccconncncnncnnnncnnnnnnos 3 10 3 4 Incoming Message Browser oooonoccccccconooncccccnnncnncnccnnnonnnnncnnno nn nn r naar nn nn ar nnn rn nr nnnnn nn 3 10 3 4 1 Viewing Incoming Message DetallS ooonnoniinnnnnnninnnninnnncononnencccarncncnannn nn 3 12 3 5 Duplicate Message BrowSel ccccccccceceeeeeceeeeeeeeeeeeeeeeeneeeeeetaeeeeeeeiateeeeeenaees 3 12 3 5 1 Querying Duplicate Message BroWS F oooioocicniniiccccnnnnncccccnnonnoncccnnnanann nn 3 14 3 6 Outgoing Message Browser oooonoccccccconoonccccccononncnccnnnnncnnncnano nn TEER rra narran rra nr cnn 3 15 3 6 1 Querying Outgoing Message BroWS F ooninoccccnnncccocncccccconnncnnnnannnnncnnnnnnos 3 18 3 7 Defining Notification Messages ooccononnniccnnnniccccccnnnonccnconnroncnccnnnnn nn rc rana rra 3 18 3 7 1 Viewing Installed Notification Details cccccccescseeeeseeeeeteeeneeeetenenaeeees 3 20 3 8 Defining the Notifications Enroutes 0 20 ececceeeeeeeeeeeeeeeeneeeeeeeeneeeeeeenaeeeeeeenaaes 3 21 3 8 1 Viewing Summary Soroen a arare e Ea A nana nn rra 3 22 3 9 Maintaining MT Task Details erroreen T E EA EATER 3 23 Message Formats conil 4 1 41 IN
66. en Reg Full This is the request message to create P2P beneficiary account in Oracle FLEXCUBE An external system which intends to create P2P beneficiary account has to send the request in the format specified The format of the pigo ORACLE 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 CreatePTPBen Req lO This is the request message to create P2P beneficiary account in Oracle FLEXCUBE UBS An external system which intends to create P2P beneficiary 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 P2P Beneficiary account CreatePTPBen Res Full This is the response message which is sent back to the external system when a P2P beneficiary 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 CreatePTPBen Res PK This is the response message which is sent back to the external system when a P2P beneficiary 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 P2P beneficiary account in the Oracle FLEXCUBE data store 6 2 7
67. eopening P2P beneficiary account in Oracle FLEXCUBE 6 2 8 FCUBSExtPCService Oracle FLEXCUBE supports the following operations under this service CreatePTPPrm ModifyPTPPrm DeletePTPPrm AuthPTPPrm QueryPTPPrm ClosePTPPrm ReopenPTPPrm 6 2 8 1 CreatePTPPrm This is the operation code for creating P2P payment parameters in Oracle FLEXCUBE lt involves the following messages CreatePTPPrm Req Full This is the request message to create P2P payment parameters in Oracle FLEXCUBE An external system which intends to create P2P payment 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 CreatePTPPrm Req lO This is the request message to create P2P payment parameters in Oracle FLEXCUBE An external system which intends to create P2P payment 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 creating P2P payment parameters CreatePTPPrm Res Full This is the response message which is sent back to the external system when a P2P payment parameters 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 O
68. erver state is A Available the bean picks up the JNDI host server details from the properties file and add a parameter to the xml which implies that the request is being served at the host Then the request will be processed at the back end and the response from the back end will reach the bean and then to the endpoint Outage Start Using the restore point the request data will be synchronized from host server to POSS Before the planned outage the server state has to be changed into S Sleep from A to indicate that the server will be down as soon as the synchronization starts During synchronization if any new request comes to the bean the gateway layer will reject the request and a XML error message will be generated Once the synchronization is completed the server state will be changed into U Unavailable which indicates the bean that the host server is down and from then on any request that comes will be processed at POSS q ORACLE 7 2 3 7 2 4 Host Down and POSS Up When the host is down and POSS is up the server state will be U During this time all the requests that reach the bean will be served at POSS The bean picks up the JNDI details of POSS from the properties file establishes a connection and sends the request which will be logged into a table at the backend The log table will have details which will indicate if e the response has been built successfully e the reque
69. ervice All funds transfer operations are logically grouped under a service called FCUBSFTService Oracle FLEXCUBE supports the following operations under this service CreateMt101 AuthorizeMt101 DeleteMt101 ModifyMt101 QueryMt101 CreateFTContract AmendFT Contract QueryFT Contract SummaryQueryProduct a ORACLE 6 2 1 1 CreateMt101 This is the operation code for creating Mt101 message in Oracle FLEXCUBE It involves the following messages CreateMt101 Req Full This is the request message to create Mt101 message in Oracle FLEXCUBE UBS An external system which intends to create Mt101 message 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 CreateMt101 Req 10 This is the request message to create Mt101 message in Oracle FLEXCUBE UBS An external system which intends to create Mt101 message 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 MT101 message CreateMt101 Res Full This is the response message which is sent back to the external system when an Mt101 message 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
70. es all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen Create TDSim 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 6 2 2 5 QueryGenAdvice This is the operation code for querying GenAdvice in Oracle FLEXCUBE It involves the following messages ot ORACLE QueryGenAdvice Req lO 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 6 2 2 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 e
71. es all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen AuthorizeClosureData Req lO 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 os ORACLE 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 6 2 5 13 ModifyClosureData This is the operation code for modifying a record in the Customer Closure Data STSCUSCL screen in Oracle FLEXCUBE Here only the
72. es all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen AuthorizeVirAcc Req 10 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 6 2 2 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 virtu
73. es will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services Contents PLACE a 1 1 A A O a a a a dete 1 1 V2 AUEN CO ir tc tida 1 1 1 3 Documentation AccesSibilitY ooonmncicnnnnnnccccnnnnoncccnnnnonncnnonnnannnnr naar rn rnnnnn rra 1 1 1 4 Acronyms and AbbreviatiONS oooooncccccnnnnnccccnnnconncccnancnnnnncnnnn o nc nn nono nn rr rana nn aran 1 1 ko MOTGMIZ ATION saves cots O ad adsense 1 1 1 6 Related Documents nire i eren aa ie de 1 2 Wt Glossary ORCOS na 1 2 Gateway Functions An Overview ccccccceeeeeeeeeeeeeeeeeeneeeeeeeeeeeeeeeeeeeeenees 2 1 ZU INOdUCION mi id a anida 2 1 2 2 Inbound Application Integration oooonninninnnicnconncnnnnnccnnnnnnnnnnnnnnonnnnnnnnnnnnnnnnnnnnnnnnns 2 1 2 2 1 EJB Based Synchronous Deployment Pattern ooooonniccccnoniocccccnncaoccnccnnnn nos 2 1 2 2 2 Web Services Based Synchronous Deployment Pattern 2 2 2 2 3 HTTP Servlet Based Synchronous Deployment Pattern 2 2 2 2 4 MDB Based Asynchronous Deployment Pattern ccccccsceenteeeeeeenees 2 2 2 3 Outbound Application Integration ccceeeeceeceee cece ce ee cette eee eeeeneaaecaeeeeeeeeetteeteees 2 3 2 4 Responsibilities of Integration Gateway 0 cc ceceeeeeeeeeeeenneeeeeeeenaeeeeeeeneeeeeeeeaaes 2 3 2 5 Deployment of Oracle FLEXCUBE Integration Gateway ooocicninnnnnnnnnnncocnccnnncnnnos 2 3 2 6 Deployment Pattern
74. esponse In the External system maintenance the Correlation Pattern can be configured for each external system It can be maintained that either the MSGID or the CORRELID of the request message is returned back as the CORRELID in the response message Depending on this maintenance Oracle FLEXCUBE will set either the MSGID or the CORRELID of the request message in the response message USERID For request messages this ID is used to submit message requests Oracle FLEXCUBE will process this request using this id For response messages the value of this will be null BRANCH This indicates the Oracle FLEXCUBE Branch Code where the request message needs to be processed If the BRANCH is missing in the header request message will be transmitted and processed in Head Office branch MODULEID This indicates the module ID SERVICE This provides details on the various services of Oracle FLEXCUBE For every incoming message in Oracle FLEXCUBE the service name is mandatory OPERATION This indicates the functional operation SOURCE_OPERATION This indicates the functional operation as registered in Oracle FLEXCUBE SOURCE_USERID This is the User ID with which the request message was invoked from the SOURCE DESTINATION For incoming messages the destination will be Oracle FLEXCUBE For response messages system will populate the SOURCE of the request message as DESTINATION MULTITRIPID This is a
75. est 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 10 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 6 2 4 3 QueryLDSIMContract
76. estination Name Authorizai Record St This summary screen can be used to search for notifications enroute which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh button to refresh the list of results sae ORACLE 3 9 Maintaining MT Task Details Using the Gateway Maintenance Detailed screen you can maintain the basis for creation of MT tasks for Gateway message You can invoke this screen by typing STDGWINT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 4 Gateway Maintenance E New amp Enter Query Gateway Maintenance Branch Code External System Module Code 1 0f 1 Service Name Operation Code Task Initiation Required Effective Date Maker Date Time Checker Date Time Mod No Record Status Authorization Status In this screen you can specify the following details Branch Code Specify the branch code of the
77. f 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 ClosePTPPrm This is the operation code for closing P2P payment parameters in Oracle FLEXCUBE ReopenPTPPrm This is the operation code for reopening P2P payment parameters in Oracle FLEXCUBE FCUBSIFService Oracle FLEXCUBE supports the following operations under this service e CreateExtAccEntries e ReverseExtAccEntries CreateExtAccEntries This is the operation code is for initiating debit or credit settlement transactions in Oracle FLEXCUBE It involves the following messages e 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 e CreateExtAccEntries Req lO 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 require
78. fields and the display fields as in the corresponding Oracle FLEXCUBE screen AuthorizeMt101 Res PK This is the response message which is sent back to the external system when Mt101 message 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 MT101 message in the Oracle FLEXCUBE data store 6 2 1 3 DeleteMt101 This is the operation code for deleting Mt101 message in Oracle FLEXCUBE It involves the following messages DeleteMt101 Req Full This is the request message to delete Mt101 message in Oracle FLEXCUBE UBS An external system which intends to delete MT101 message 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 Ga ORACLE DeleteMt101 Req IlO This is the request message to delete Mt101 message in Oracle FLEXCUBE UBS An external system which intends to delete an MT101 message 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 MT101 message DeleteMt101 Res Full This is the response message which is sent back to the external system when Mt101 message is successfully deleted in Oracle FLEXCUBE UBS The format of the message is called
79. gration of different applications and solutions is a key area in today s systems A variety of specialized applications deployed on disparate platforms and using different infrastructure need to be able to communicate and integrate seamlessly with Oracle FLEXCUBE in order to exchange data The Oracle FLEXCUBE Integration Gateway referred to as Gateway in the rest of the document will cater to these integration needs The integration needs supported by the Gateway can be broadly categorized from the perspective of the Gateway as follows e Inbound application integration used when any external system needs to add modify or query information within Oracle FLEXCUBE e Outbound application integration used when any external system needs to be notified of the various events that occur within Oracle FLEXCUBE Inbound Application Integration Oracle FLEXCUBE Inbound Application Gateway provides XML based interfaces thus enhancing the need to communicate and integrate with the external systems The data exchanged between Oracle FLEXCUBE and the external systems will be in the form of XML messages These XML messages are defined in FCUBS in the form of XML Schema Documents XSD and are referred to as FCUBS formats For more information on FCUBS formats refer the Message Formats chapter in this User Manual FCUBS Inbound Application Integration Gateway uses the Synchronous and Asynchronous Deployment Pattern for addressing the
80. his 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 6 2 5 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 Orac
81. ields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CloseAmtBlk Req lO 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 CloseAmtBIk 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 6 2 5 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 th
82. ifying 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 10 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 fiel
83. in the XML format or the Text format R ORACLE Click Text View button to view the incoming messages in text format as shown below Text View kel Click XML View button to view the Gateway Browser Window screen which displays the messages in XML format 3 Laleway Uroewser Wind lt FCUBS_ENVELOPE gt lt FCUBS_HEADER gt lt SOURCE gt FLEXCUBE lt SOURCE gt lt M5G1D gt 9062070000001662 lt MSG D gt lt CORRELID gt lt CORRELID gt lt USERID gt SAURAVI 4USERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCUBSCustomerService lt SERVICE gt lt OPERATION gt CreateCust lt OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_USERID gt lt SOURCE_USERID gt lt DESTINATION gt SIEBELCRM lt DESTINATION gt lt FCUBS_HEADER gt lt FCUBS_BODY gt lt Qust Static Create Res Fiul gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt C lt CTIPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU99999 lt L ABID gt lt OCATEG gt Individual lt CCATEG gt a ORACLE 3 4 1 3 5 Viewing Incoming Message Details The summary of all messages received from the external system can be viewed using the Incoming Message Browser Summary screen as shown below You can invoke this screen by typing GWSINBRVY in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 44 Advanc
84. ing the Notifications Installed screen oe ORACLE You can invoke the Notifications Installed Detailed screen by typing GWDNTFIN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Notifications Installed E New ES Enter Query Branch Code Branch Name Notification Code Description Input By Authorized By Modification Date Time Date Time Number M Authorized M Open In this screen you need to specify the following details Branch Code Select a branch code for which you wish to assign a notification code Once you select the branch code the corresponding description is displayed Notification Code From the list of values select a notification code you wish to link with the branch This will be used to generate notifications for the entire branch Once you select the notification code the corresponding description is displayed In addition to maintaining a notification code for a given branch you can also specify a topic or a queue to which the notification messages should be sent You can define a topic queue for a given branch and notification code in the Notifications Enroute screen a ORACLE 3 7 1 Viewing Installed Notification Details You can view and query the list of notification messages using the Notifications Installed Summary screen You can invoke this screen by typing GW
85. 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 lO 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 6 2 5 9 Authorize Customer This is the operation code for authorizing the customer record in Oracle FLEXCUBE lt involves the following messages AuthorizeCustomer Req Full Thi
86. ion the database components of the Gateway are deployed as two or more schemas The messaging schema as part of SMS schema in the SMS and or HO instance The business schema s in the various branch schemas in the branch instance s e Single schema deployment of FCUBS In this situation the database components of the Gateway messaging and business are both deployed as part of the single Oracle FLEXCUBE schema oe ORACLE 2 6 Deployment Patterns for Application Integration Business Oracle f Nature of FLEXCUBE Integration Remarks Needs Integration Deployment Pattern Inbound Transac Synchronous FLEXCUBEUBS Recommended tions into Oracle EJB FLEXCUBE FLEXCUBE UBS This can be used if the exter HTTP Servlet nal system cannot communi cate to Oracle FLEXCUBE using EJB FLEXCUBEUBS This can be used if the exter Web Services nal system chooses to com municate only through Web Services Asynchro FLEXCUBE UBS This can be used if the exter nous MDB nal system chooses to com municate only through JMS queues Inbound Queries Synchronous FLEXCUBEUBS Recommended into Oracle FLEX EJB CUBE FLEXCUBEUBS This can be used if the exter In Servlet nal system cannot communi cate to Oracle FLEXCUBE using EJB FLEXCUBE UBS This can be used if the exter Web Services nal system chooses to com municate only through Web Services Asynchro FLEXCUBE UBS This
87. irtual account in the Oracle FLEXCUBE data store ane ORACLE 6 2 2 20 QueryVirAcc This is the operation code for querying a virtual account in Oracle FLEXCUBE It involves the following messages QueryVirAcc Req lO 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 6 2 2 21 QueryCustAcc 6 2 3 6 2 3 1 This service is used by external channels to retrieve customer account details from the Oracle FLEXCUBE Universal Banking System QueryCustAcc Req lO 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 respon
88. lds 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 6 2 2 4 CreateTDSim This is the operation code for creating TD simulation in Oracle FLEXCUBE It involves the following messages Create TDSim 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 lO 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 includ
89. le 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 pag ORACLE 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 6 2 5 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 f
90. lication tool bar and clicking the adjoining arrow button Advanced Search Reset Branch Message Id Request Queue Message Id Service Name Operation Code User ld Their User ld Server Date Stamp Status Message Reference External System Correlation Id 59 60 EA AE Records per page 15 First Previous Of 4 Net Last Message Reference Branch External System Message Id Correlation Id Request Queue Message Id Service Namel Operation Code Click Text View button in the Duplicate Message Browser Summary screen to view the duplicate messages in the text format 4 Duplicate Message Browser Text View ate ORACLE Click XML View button in the Duplicate Message Browser Summary screen to view the duplicate messages in the following format 3 Gateway Urowser Window Microsef internet Laplorer lt FCUBS_ENVELOPE gt lt FCUBS_HEADER gt lt SOURCE gt FLEXCUBE lt SOURCE gt lt M5G D gt 90620 7000000 1 662 lt MSGID gt lt CORRELID gt lt CORRELID gt lt USERID gt SAURAVI lt USERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCUBSCustomerService lt SERVICE gt lt OPERATION gt CreateCust lt OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_USERID gt lt SOURCE_USERID gt lt DESTINATION gt SIEBELCRM lt DESTINATION gt lt FCUBS_HEADER gt lt FCUBS_BODY gt
91. lly required for creating an FT contract CreateFTContract Res Full This is the response message which is sent back to the external system when FT 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 CreateFTContract Res PK This is the response message which is sent back to the external system when an FT 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 FT contract in the Oracle FLEXCUBE data store 6 2 1 7 AmendFTContract This is the operation code for amending FT contract in Oracle FLEXCUBE lt involves the following messages AmendFTContract Req Full This is the request message to amend FT contract in Oracle FLEXCUBE UBS An external system which intends to amend FT 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 AmendFTContract Req lO This is the request message to amend FT contract in Oracle FLEXCUBE UBS An external system which intends to amend FT contract has to send the request in the specified format The format of the message is called Input only
92. lt Qust Static Create Res Ful gt lt CUSTNO gt CUS99999 lt CUSTNO gt lt CTYPE gt CEYCTYPE gt lt SNAME gt NEWCUSTFLEXML1I02 lt SNAME gt lt LIABID gt CU99999 lt ABID gt lt OCATEG gt Individual lt CCATEG gt lt SOUNTRY gt USAUCOLNTRY gt 3 5 1 Querying Duplicate Message Browser You can query the list of duplicate messages using the Duplicate Message Browser Summary screen with functions for search You can invoke this screen by typing ons ORACLE 3 6 GWSPBROW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button C Advanced Search 4 Reset Message Reference Branch External System Message ld Correlation ld H Request Queue Message Id Service Name Operation Code User Id Their User ld Server Date Stamp Status a a Records per page 15 v LFirst Previous 4 of 4 Next Last Go Message Reference Branch External System Message Id Correlation Ic Request Queue Message Id Service Name Operation Codel Us This query screen can be used to search for duplicate messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND
93. ly required for P2P payment parameters AuthPTPPrm Res Full This is the response message which is sent back to the external system when a P2P payment parameters is successfully authorized in Oracle FLEXCUBE The format of the message is called Full screen response which includes Eras ORACLE 6 2 8 5 6 2 8 6 6 2 8 7 6 2 9 6 2 9 1 all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e AuthPTPPrm Res PK This is the response message which is sent back to the external system when a P2P payment parameters 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 QueryPTPPrm This is the operation code for querying P2P payment parameters done in Oracle FLEXCUBE It involves the following messages e QueryPTPPrm Req lO This is the request message to query the P2P payment parameters in Oracle FLEXCUBE An external system which intends to query P2P payment 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 querying P2P payment parameters e QueryPTPPrm Res Full This is the response message which is sent back to the external system when P2P payment parameters is successfully queried in Oracle FLEXCUBE The format o
94. m 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 6 2 6 4 QueryTDRedem This is the operation code for querying TD redemption done in Oracle FLEXCUBE It involves the following messages QueryTDRedem Req lO 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 6 2 7 FCUBSPCService All PC operations are logically grouped under a service called FCUBSPCService Oracle FLEXCUBE supports the following operations under this service CreatePTPBen ModifyPTPBen DeletePTPBen AuthPTPBen QueryPTPBen ClosePTPBen ReopenPTPBen 6 2 7 1 CreatePTPBen This is the operation code for creating P2P beneficiary account in Oracle FLEXCUBE It involves the following messages CreatePTPB
95. n oy ORACLE 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 6 2 5 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 10 T
96. n 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 lO 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 Delete TDCustAcc 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 Delete TDCustAcc 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 6 2 2 9 Query TDCustAcc This is the operation code for querying TD account in Oracle FLEXCUBE It involves the following messages QueryTDCustAcc Req lO This is the request message to query a TD ac
97. n also view the messages in the XML format or the Text format Click Text View button to view the response message in text format as shown below Text View 219 ORACLE Click XML View button to view the response messages in XML format as shown below J Gateway Browser Wind lt FCUBS_ENVELOPE gt lt FCUBS_HEADER gt lt SOURCE gt FLEXCUBE lt SOURCE gt lt M3G 10 gt 9062070000001662 lt M3310 gt lt CORRELID gt lt CORRELID gt lt USERID gt SAURAVI lt GUSERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCUBSCustomerService lt SERVICE gt lt OPERATION gt CreateCust lt OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_OPERATION gt lt SOURCE_USERID gt lt SOURCE_USERID gt lt DESTINATION gt SIEBELCRM lt DESTINATION gt lt FCUBS_HEADER gt lt FCUBS_BODY gt lt Qust Static Create Res Ful gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt CYCTYPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU99999 lt ABID gt lt OCATEG gt Individual lt CCATEG gt RyY gt ant ORACLE 3 6 1 3 7 Querying Outgoing Message Browser You can query the list of outgoing messages using the Outgoing Message Browser Summary screen You can invoke this screen by typing GWSOTBRW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 4 Advanced Search Reset Branch External Sys
98. n the following manner About this Manual gives information on the intended audience It also Shaptera lists the various chapters covered in this User Manual Chapter 2 Gateway Functions An Overview explains the features of this module External System Maintenance explains the maintenance of external ehapters systems and the various processes involved Chapter 4 Message Formats explains the different message formats FLEXML Adapter Message Conversion explains details about the Chapter5 FLEXML Adapter t1 ORACLE 1 6 1 7 Chapter 6 Annexure List of Messages lists all the messages that you encounter p while working with Oracle FLEXCUBE Gateway services Chapter 7 Planned Outage Support Server describes the process of having a p support server to substitute the host server during downtime Chapter 8 Function ID Glossary has alphabetical listing of Function Screen ID s P used in the module with page references for quick navigation Related Documents The Core Entities User Manual The Procedures User Manual The Settlements User Manual The Profit and Charges User Manual Glossary of Icons This User Manual may refer to all or some of the following icons Icon s Function ES Exit Add row E Delete row Paz Option List Ve ORACLE 2 1 2 2 2 2 1 2 Gateway Functions An Overview Introduction Inte
99. nts within Oracle FLEXCUBE to the external system For eg internal events associated with static maintenances or transactions that happen in Oracle FLEXCUBE need to be communicated to the external system FLEXML uses the handoff mechanism to transfer data to the external system whereas Gateway uses notification process for the same Handoff messages contain complete transaction information but notification message contains only the primary key of the transaction Processing Outbound Messages The outbound messages to the external system are processed as follows 1 Outbound adapter receives request notification XML message from the notification queue 2 Notification code is retrieved from the notification message 3 Using XSLT maintenance table and notification code query XSLT handoff XSLT and all the externals system names related to the notification code are retrieved by the adapter 4 Query XSLT is applied to convert GW notification XML message to GW query message and handoff XSLT is applied to convert GW reply to FLEXML format handoff message 5 The handoff queue name is retrieved using external system maintenance 6 The handoff message is logged in table if the value of the property file parameter FXG_MSG_LOG_FLG is Y 7 Handoff XML message is send to each external system 2 ORACLE 5 3 2 Mapping FLEXML Format Messages to Gateway Format FLEXML uses DTDs to define the structure of an XML document whereas Gatewa
100. o the external system when P2P payment parameters 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 DeletePTPPrm Res PK This is the response message which is sent back to the external system when P2P payment parameters 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 P2P beneficiary account in the Oracle FLEXCUBE data store 6 2 8 4 AuthPTPPrm This is the operation code for authorizing P2P payment parameters in Oracle FLEXCUBE It involves the following messages AuthPTPPrm Req Full This is the request message to authorize the P2P payment parameters in Oracle FLEXCUBE 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 AuthPTPPrm Req 10 This is the request message to authorize the P2P payment parameters in Oracle FLEXCUBE An external system which intends to authorize the P2P payment 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 actual
101. ort the Create Stop Payment operation FCUBSSwitch Service The FCUBSSwitch services support the Switch Transaction operation ORACLE 8 Function ID Glossary c GWSEXFUN conocio 3 5 CODSORCE siiisssssinnscsainn 3 6 GWSEXSYS 0 eesssseeeeerssees 3 3 CODUPLDM cocicecccaionicnnnnos 3 7 GWSINBRW sssssseeeeseees 3 12 GWSNTFEN noiis 3 22 G GWSNTFIN eeseseeeeeeee 3 20 GWDEXSYS coccion 3 1 GWSOTBRW oooi 3 18 GWDINBRW cocino 3 10 GWSPBROW 3 13 3 15 GWDNTEEN coccion 3 21 GWDNTEIN ccoo 3 19 S GWDOTBRW ccccccceeee 3 16 STDGWINT c econ 3 23 PI ORACLE
102. racle FLEXCUBE screen CreatePTPPrm Res PK This is the response message which is sent back to the external system when a P2P payment parameters 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 P2P payment parameters in the Oracle FLEXCUBE data store 6 2 8 2 ModifyPTPPrm This is the operation code for modifying P2P payment parameters in Oracle FLEXCUBE lt involves the following messages ModifyPTPPrm Req Full This is the request message to modify P2P payment parameters in Oracle FLEXCUBE An external system which intends to modify a P2P payment 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 ModifyPTPPrm Req lO This is the request message to modify P2P payment parameters in Oracle FLEXCUBE An external system which intends to modify a P2P payment parameters has to send the request in the specified format The format of the pia ORACLE message is called Input only which has only those fields that are actually required for modifying P2P payment parameters ModifyPTPPrm Res Full This is the response message which is sent back to the external system when P2P payment parameters is successfully modified in Oracle FLEXCUBE The format of the
103. reateTDTopUp AuthorizeTDTopUp DeleteTDTopUp ModifyTDTopUp ORACLE CreateVirAcc AuthVirAcc DeleteVirAcc ModifyVirAcc CloseVirAcc ReopenVirAcc QueryVirAcc QueryCustAcc 6 2 2 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 lO 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
104. redemption in the Oracle FLEXCUBE data store 6 2 6 3 DeleteTDRedem This is the operation code for deleting redemption request of TD in Oracle FLEXCUBE It involves the following messages e 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 Ares ORACLE 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 10 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 fro
105. rocessing After the necessary processing is done in Oracle FLEXCUBE based on the request the response is sent to the response queue as an XML message Outbound Application Integration The Outbound Application Integration is also called the Oracle FLEXCUBE Notify Application Integration layer This application layer sends out notification messages to the external system whenever events occur in Oracle FLEXCUBE The notification messages generated by FCUBS on the occurrence of these events will be XML messages These XML messages are defined in FCUBS in the form of XML Schema Documents XSD and are referred to as FCUBS formats For more information on FCUBS formats refer the Message Formats chapter in this module Responsibilities of Integration Gateway The primary responsibilities of Oracle FLEXCUBE Integration Gateway include the following e Authentication e Duplicate recognition e Validation e Routing e Logging of messages Deployment of Oracle FLEXCUBE Integration Gate way Message communication incoming or outgoing from to an external system in Oracle FLEXCUBE will happen only through an Oracle FLEXCUBE Integration Gateway Hence it becomes the first point of contact or last point of contact with the database in message flow The Oracle FLEXCUBE Integration Gateway can be deployed to support both the distributed and single schema deployments of Oracle FLEXCUBE e Distributed deployment of FCUBS In this situat
106. s applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate failsafe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing This software or hardware and documentation may provide access to or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliat
107. s for Application Integration ecceceeeeecceeceeeeeeeeeeeeeeeeees 2 4 27 FLEXME Adapter nica evil Meat tabled alate dearest 2 4 External System Maintenance ccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeenenes 3 1 3 1 Defining an External System oooconnncccccnnnconcccccnononcncnnnnnnnnncnnnnnnnnnnnnnnn nn Ee iaat 3 1 3 1 1 Specifying External System Details 00 cece cette tneeee eee tnneeeeettnaeeeenenae 3 1 3 1 2 Indicating Correlation Pattern oiioiiccnnninicinnnnnonccccconnnnncnccnnnnnn cnn naar 3 1 3 1 3 Specifying Message Exchange Pattern ooooooonnninccinnnniccccccnnonncccccnanancccnnnnn 3 2 3 1 4 Specifying Queue Details ooooooninncccnnoncnccccnnnnonccccnnnnarnc cnn rancia nnnrccrnn 3 2 3 1 5 Specifying External System Queue Details ooonmnioinininnnnnoniccccnnecniccccncnn 3 2 3 1 6 Viewing External System DetallS oooonmniiciinnnniconcccinnmnccccinnnarcccnnnnncccnnnnn 3 3 3 1 7 Accessing Services and Operations ooooiciccinnnociccnnnoconnccccnnnannccnnnnnnnnnrcnnnnnos 3 4 3 2 Defining Access Rights to an External System onnccccnnnnnncccnnnncccccccnnnnanccnnnn nan ncnnnnno 3 4 3 2 1 Viewing External System Function Details ooonmmiocinnnniniinnnnicccccnnnneccccnons 3 5 3 2 2 Defining Access Rights to a User ID oooooniiciinnonicicnnnnniccccnnnncancccnnnnnrrnnnn 3 6 3 23 Maintaining Upload Source Details ooonmiiniinnonidiiinnnnlccccnnnecccnnnerccnns 3 6 3 2 4 Specifying Upload Source Pr
108. s 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 lO 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 6 2 5 10 QueryCustomer This service is used by extern
109. saction 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 6 24 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 CreateL DPaymentSim 6 2 4 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
110. se 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 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 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 10 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 ex
111. st has to be replayed at the host during replay e any error has occurred and oracle SCN The response is sent back to the bean which will send the response to the end point Host Up Start Replay from POSS Once the host is up a REPLAY ROUTINE which is a java routine is carried out which consists of the following steps e The server state will be changed from U to R Replay mode e The replay routine will get the requests from the log table at POSS for which response building has been completed and these will be replayed to the host e The replay routine logs all message logs and places the message onto Oracle AQ on the Host database e Multiple processes equal to the number of locks defined start the request processing based on SCN e Each process will replay the requests on to the host by calling a procedure in the service router e Once a record is replayed the thread updates the log table indicating that the replay of this record is complete When the server state is R and any new request comes to the bean it will execute a DAO to check for records in POSS that need to be replayed to the host If any such record is found the new request is sent to POSS else the server state is changed from R to A When the server state is R the bean also slows down the processing of new requests to ensure there is a switch over back to host ine ORACLE 7 2 5 7 3 7 3 1 7 3 2
112. system invokes the adapter using EJB interface API method e MDB Inbound Adapter This is used if the external system is JMS compatible The external system invokes the adapter by sending message to JMS Queue a ORACLE 5 2 1 5 3 5 3 1 Processing Incoming FLEXML Request Message The inbound adapter processes an incoming request message in FLEXML format as follows 1 Adapter receives the request message in FLEXML format 2 The request message is logged in table if the value of the property file parameter FXG_MSG_LOG_FLG is Y 3 XML message is validated using FLEXML DTD 4 Ifthe message is invalid the adapter generates parser error message in FLEXML format and sends it back to external system If the message is valid the source name service name and operation type is retrieved from the message 5 Based on source name service name and operation type request and reply XSLT file name is retrieved from database 6 XSLT is applied to convert the message from FLEXML format to GW format 7 GW EJB component is invoked which processes the request and replies with a message in gateway format 8 XSLT is applied to convert GW reply message to FLEXML format 9 The reply message is logged in table if the value of the property file parameter FXG_MSG_LOG FLG is Y 10 Reply message in FLEXML format is send back to the external system Outbound FLEXML Adapter An outbound adapter notifies any internal eve
113. t pattern will be used in integration scenarios where the external system connecting to Oracle FLEXCUBE wants to connect using standards based inter operable web services This deployment pattern is especially applicable to systems which meet the following broad guidelines e Systems that are not EJB literate i e such systems are not capable of establishing connections with Oracle FLEXCUBE based upon the EJB interface and or e Systems that prefer to use a standards based approach In this deployment pattern the external system will use the SOAP Simple Object Access Protocol messages to communicate to the Oracle FLEXCUBE web services The services displayed by Oracle FLEXCUBE are of a message based style i e the actual request will be in the form of an XML message but the request will be a payload within the SOAP message After the necessary processing is done in Oracle FLEXCUBE based on the request the response is returned to the external system as an XML message which will be a payload within the response SOAP message The transaction control for the processing will stay with the Oracle FLEXCUBE HTTP Servlet Based Synchronous Deployment Pattern The HTTP servlet deployment pattern will be used in integration scenarios where the external system connecting to Oracle FLEXCUBE wants to connect to Oracle FLEXCUBE using simple HTTP messages This is especially applicable to systems such as the following
114. tem Operation Code Correlation Id User ld Branch Date Message Reference Related Message Reference Service Name Message ld Response Queue Message Id Their User ld Server Date Stamp A Message Status EEE Records per page 15 y First Previous 1 Of 1 Next Last Message Reference Branch Related Message Reference External System Service Name Operation Code Message Id Correlation Id Re This query screen can be used to search for outgoing messages which match the criteria Message Reference Number External System Service Name etc you specify The Result list shows the messages which match your query The search functions available are Advanced Click Advanced to specify queries with logical operators such as AND OR and NOT Reset Click Reset to empty the values in the criteria fields so that you may begin a new search Query After specifying your search criteria click Query to view the list of results which match your search criteria Refresh Click Refresh to refresh the list of results Defining Notification Messages The outgoing message browser also displays the notification messages Every time the database layer receives a notification message it updates the outgoing message browser to display the same At the branch level you can maintain notification codes for each branch You can do this us
115. ternal 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 ss ORACLE 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 6 2 3 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 lO 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 tran
116. the specified format The format of the message is called Input only which has only those fields that are actually required for querying an FT contract QueryFTContract Res Full This is the response message which is sent back to the external system when FT 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 QueryFTContract Res PK This is the response message which is sent back to the external system when FT contract 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 FT contract in the Oracle FLEXCUBE data store 6 2 1 9 SummaryQueryProduct This is the operation code for querying FT summary product in Oracle FLEXCUBE Note For this operation you need to maintain FTVPRMNT as the function for Summa ryQueryProduct operation code in External System Functions GWDEXFUN screen 6 2 2 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 C
117. 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 6 2 2 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 10 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
118. tus Select the status of the record from the drop down list and the available options are e Authorized e Unauthorized e Put On hold On Exception Select the record status in case of any exception while saving from the drop down list and the available options are e Put On Hold e Reject On Override Select the record status in case of any overriding a saved record from the drop down list and the available options are e Put On Hold e Reject e Ignore Proceed With EOD Check this box if you wish to proceed with EOD Deleted Allowed Check this box if deleting is allowed Reverse Allowed Check this box if reversal is allowed Amend Allowed Check this box if amendment is allowed Purge Days Calendar Specify the calendar purge days Allow Deferred Processing Check this box if deferred processing is allowed Allow EOD with Deferred Check this box if EOD with deferred is allowed Gateway Password Generation Logic For External System Authentication This section describes the Encryption information for gateway authentication If Password authentication is required for an external system then check the System Authentication Required check box while maintaining the External System details in CODSORCE os ORACLE 3 3 1 3 4 Once this check box is checked Oracle FLEXCUBE validates for Encrypted password as part of every request sent by the External System The password encryption logic as below
119. ueryMt101 Res Full This is the response message which is sent back to the external system when Mt101 message 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 QueryMt101 Res PK This is the response message which is sent back to the external system when Mt101 message 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 MT101 message in the Oracle FLEXCUBE data store 6 2 1 6 CreateFTContract This is the operation code for creating FT contract in Oracle FLEXCUBE It involves the following messages CreateFTContract Req Full This is the request message to create FT contract in Oracle FLEXCUBE UBS An external system which intends to create FT 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 CreateFTContract Req lO This is the request message to create FT contract in Oracle FLEXCUBE UBS An external system which intends to create FT 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 actua
120. ut 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 6 2 4 6 QueryLDPaymentSim This is the operation code for querying LD Payment Simulation in Oracle FLEXCUBE lt involves the following messages QueryLDPaymentSim Req lO 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 dl ORACLE 6 2 4 7 CreateLDPaymentSim This is the operation code for creating LD Payment Simulation in Oracle FLEXCUBE It involves the follo
121. 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 lO 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 ate ORACLE 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 6 2 2 18 CloseVirAcc This is the operation code for closing a virtual account in Oracle FLEXCUBE It in
122. volves 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 lO 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 6 2 2 19 ReopenVirAcc This is
123. which is sent back to the external system when P2P beneficiary 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 P2P beneficiary account in the Oracle FLEXCUBE data store 6 2 7 4 AuthPTPBen This is the operation code for authorizing P2P beneficiary account in Oracle FLEXCUBE It involves the following messages AuthPTPBen Req Full This is the request message to authorize the P2P beneficiary 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 AuthPTPBen Req lO This is the request message to authorize the P2P beneficiary account in Oracle FLEXCUBE UBS An external system which intends to authorize the P2P beneficiary 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 P2P beneficiary account AuthPTPBen Res Full This is the response message which is sent back to the external system when a P2P beneficiary account is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fiel
124. wing 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 lO 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 FLEXCUB
125. xternal 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 lO 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 6 2 2 7 AuthorizeTDCustAcc This is the operation code for authorizing the TD in Oracle FLEXCUBE It involves the following messages AuthorizeT DCustAcc Req Full This is the request message to authorize TD in Oracle FLEXCUBE UBS An external
126. ys use XSDs for the same Extensible Style Sheet Language XSL an XML based transformation language is used to convert XML documents from one format to another The mapping can be done using any of the following methods e Optional Attribute Map Approach X Path language is used to map between the two XML formats e Mandatory Attribute Map Approach the mandatory attributes in the target XML document are mapped in this case i ORACLE 6 Annexure List of Messages 6 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 6 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 The services supported by the Gateway are listed below FCUBSFT Service FCUBSAccService FCUBSDDService FCUBSLDService FCUBSCustomerService FCUBSTDService FCUBSPCService FCUBSExtPCService FCUBSIF Service FCUBSInteractionService FCUBSSIService 6 2 1 FCUBSFTS

Gateway Functions User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents