Home

Gateway Functions User Manual

1. 6 2 7 3 EmbargoAuth This is the operation code for authorizing an Embargo transaction in Oracle FLEXCUBE It involves the following messages e Embargo Auth Reg This is the request message to authorize an Embargo transaction in Oracle FLEXCUBE UBS An external system which intends to authorize an Embargo 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 authorizing an Embargo transaction Embargo Auth Res Full This is the response message which will be sent back to the external system when an Embargo transaction is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e Embargo Auth Res PK This is the response message which will be sent back to the external system when an Embargo transaction 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 an Embargo transaction record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e Embargo Auth Flt This XML message indicates the error response generated by Oracle FLEXCUBE when
2. Cl Allow Deferred Processing Allow EOD with Deferred O Allow Delete Input By Authorized By Modification Authorized Date Time Date Time Number 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 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 Put on Hold is selected then during the request message creation the system creates a hold contract however you can modify this contract 3 8 ORACLE 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 you would like to
3. QueryCheckTax Req Full MSG This is the request message to query Check Tax Parameter An external system which intends to query Check Tax Parameter 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 QueryCheckTax Req lO MSG This is the request message to query Check Tax Parameter An external system which intends to query Check Tax Parameter has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryCheckTax Res Full MSG This is the response message which is sent back to the external system when Check Tax Parameter is queried 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 QueryCheckTax Res PK MSG This is the response message which is sent back to the external system when Check Tax Parameter is queried The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store 6 2 13 FCUBSICService All the operations that can be performed on Interest and Charges module are logically grouped under a service called FCUBSICService Oracle FLEXCUBE supports the following ope
4. e QuerySTTrnTax Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query a transaction tax fails due to any functional error 6 2 8 9 CloseSTTrnTax This is the operation code for closing a transaction tax in Oracle FLEXCUBE It involves the following messages e CloseSTTrnTax Req This is the request message to close a transaction tax in Oracle FLEXCUBE UBS An external system which intends to close the transaction tax 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 transaction tax e CloseSTTrnTax Res Full This is the response message which will be sent back to the external system when a transaction tax is successfully closed in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CloseSTTrnTax Res PK This is the response message which will be sent back to the external system when a transaction tax 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 transaction tax record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External s
5. e ReopenSecCode Req Full This is the request message to reopen a record An external system which intends to reopen 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 6 30 ORACLE fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e ReopenSecCode Req lO This is the request message to reopen a record An external system which intends to reopen a record has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ReopenSecCode Res Full This is the response message which is sent back to the external system when a record is reopened 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 ReopenSecCode Res PK This is the response message which is sent back to the external system when a record is reopened The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 6 CreateCGProductMaint This is the operation code to create a CG product maintenance It involves the following messages e CreateCGProductMaint Req Full This is the request message to create a CG product maintenance An
6. which includes only the primary key fields of the error code maintenance record in the Oracle FLEXCUBE data store 6 40 ORACLE 6 2 6 28 Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e ReopenCGRejErrCdMaint Reopen Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to reopen error code maintenance fails due to any functional error QueryCGRejErrCdMaint This is the operation code for querying error code maintenance in Oracle FLEXCUBE It involves the following messages 6 2 6 29 e QueryCGRejErrCdMaint Query Reg This is the request message to error code maintenance in Oracle FLEXCUBE UBS An external system which intends to query the error code maintenance 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 quering a cheque correspondence QueryCGRejErrCdMaint Query Res Full This is the response message which will be sent back to the external system when error code maintenance is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryCGRejErrCdMaint Query Res PK This is the response message whic
7. This is the request message to close beneficiary details An external system which intends to close beneficiary details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CloseBeneficiaryMaintenance Res Full This is the response message which is sent back to the external system when beneficiary details are closed 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 CloseBeneficiaryMaintenance Res PK This is the response message which is sent back to the external system when beneficiary details are closed The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store BeneficiaryMaintenanceRpn This is the operation code to close beneficiary details It involves the following messages 6 2 11 9 e ReopenBeneficiaryMaintenance Req Full This is the request message to reopen beneficiary details An external system which intends to reopen beneficiary details 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 ReopenBeneficiaryMaintenance Req
8. which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 3 ModifySecCode This is the operation code to modify a record in the sector code maintenance It involves the following messages e ModifySecCode Req Full This is the request message to modify a record 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 e ModifySecCode Req lO This is the request message to modify a record 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 Input only which has only those fields that can be used to query e ModifySecCode Res Full This is the response message which is sent back to the external system when a record is modified 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 CreateSecCode Res PK This is the response message which is sent back to the external system when a record is modified The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 4 QuerySecC
9. 7 PLANNED OUTAGE SUPPORT SERVER ssccccssssscsssssccessssccssssccccsssccsessscccscsscccessaccsesscescessacscessseces 7 1 7 1 INTRODUCTION 3 ccesed sy acsSabes Sesansencahec stew sdae des edataiossheee wele acs E A ERE E AENEA Geese sabagceseneeavsuheeeueieeoes 7 1 7 2 HANDLING PLANNED OUTAGES viici a ioe ae E aE E RE NOE Eae E A E AERE NEE R E aE 7 1 Tezi OSE UP wa sieciscuccsdtesssteceacevds deste sks a EE EA E EATA ETE A EEE i 7 1 1 2 2 Out ge Statt ssis i A E E E E A E E A E E E AN 7 1 7 2 3 Host Down and POSS Op recresen a ae ENa RE E R EEEE EA EE A 7 2 7 2 4 Host Up Start Replay froin POSS ceccvscescsesivsucetectes cssceseessstensvbnedassesies E A 7 2 7 255 EEL OCM AMP GC ba coseiescsatavasvodssioestes tes eentdetagendebvaanedaosaleliysesuceieeivacngussiperedses sdesineveeubeaswgengencntcnts NASENNE 7 3 7 3 SERVICES SUPPORTED DURING OUTAGE ccccesssssesececeesesssaesecececsesseaeceeecessenseaesesececeeseaeseeeeeeeesssnsaeeeeseeenes 7 3 7 3 1 PCUBSETD SCF VICE EEA E ANAE EEE EN EAEE NEEE EE E NE ENE E E 7 3 7 3 2 FEUDS P C Ne E eaa a aaa a a E a e E E Ea EO ee aSa Eaa S ENAUT 7 4 7 3 3 FCUBSSI Servi Enese aeania i a aiea O ai ea aa e iaaea AE onion 7 4 7 3 4 FCUBSID Se E e e ai a a E a O E EEO Ea EAAS ENASI 7 4 7 3 5 PF CUBSCE S Cv iC zeinera iae i a a aie a A eai aea aa e iaae o AE ONASIN 7 4 7 3 6 FCUBSLD Service soeren a i a E a A E E eE a Eea AO ENANOS 7 4 7 3 7 EP CUBSAGGC Servite sivivcsctecctesscdsliesennccndscndshdeteoncvbe
10. EmbargoMaint Delete Res PK This is the response message which will be sent back to the external system when Embargo maintenance 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 Embargo maintenance record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key EmbargoMaint Delete Flit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to delete Embargo maintenance fails due to any functional error QueryEmbargoMaint This is the operation code for querying Embargo maintenance in Oracle FLEXCUBE It involves the following messages e EmbargoMaint Query Reqg This is the request message to query Embargo maintenance in Oracle FLEXCUBE UBS An external system which intends to query Embargo maintenance 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 Embargo maintenance e EmbardoMaint Query Res Full This is the response message which will be sent back to the external system when Embargo maintenance is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input f
11. FLEXCUBE data store QueryFunding This is the operation code to query an online funding It involves the following messages QueryPCFunding Req Full MSG This is the request message to query an online funding An external system which intends to query an online funding 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 QueryPCFunding Req IO MSG This is the request message to query an online funding An external system which intends to query an online funding has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryPCFunding Res Full MSG This is the response message which is sent back to the external system when an online funding is done 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 QueryPCFunding Res PK MSG This is the response message which is sent back to the external system when an online funding is done The format of the message is called 6 77 ORACLE Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store 6 2 12 FCUBSCAService 6 2 12 1 CreateCheckTax ModifyChe
12. Record Status Default Response Queue 3 3 ORACLE 3 1 2 3 2 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 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 system using the Extern
13. Res PK This is the response message which is sent back to the external system when extension request for CB contract is modified 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 108 ORACLE 6 1 ORACLE 6 1 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 server state is A Available the bean picks up the JNDI
14. Res PK This is the response message which is sent back to the external system when a collection service agreement is done 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 QueryCollAgreement This is the operation code to query coll agreement It involves the following messages QueryCollAgreement Req Full This is the request message to query a collection service agreement An external system which intends to query a collection service agreement 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 QueryCollAgreement Req lO This is the request message to query a collection service agreement An external system which intends to query a collection service agreement has 6 85 ORACLE 6 2 15 6 to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryCollAgreement Res Full This is the response message which is sent back to the external system when a collection service agreement is done 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 FLEX
15. Screen Glossary The following table lists the function id and the function description of the screens covered as part of this User Manual Function ID Function Description CODSORCE Upload Source Maintenance CODUPLDM Upload Source Preferences Maintenance GWDEXFUN External System Functions Detailed GWDEXSYS External System Maintenance GWDINBRW Incoming Message Browser Detail GWDNTFEN Notifications Enroute Maintenance GWDNTFIN Notifications Installed Detailed GWDOTBRW Outgoing Message Browser GWSEXFUN External System Functions Summary GWSEXSYS External System Summary GWSINBRW_ Incoming Message Browser GWSNTFIN Notifications Installed Summary GWSOTBRW Outgoing Message Browser GWSPBROW Duplicate Message Browser Summary STDGWINT Gateway Maintenance 8 1 ORACLE ORACLE Gateway Services May 2013 Version 11 3 1 0 0LA 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 2013 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 sys
16. closure record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBGCLOON_NEW Res Full This is the response message which is sent back to the external system when a new CB operation closure record is created 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 CBGCLOON_NEW Res PK This is the response message which is sent back to the external system when a new CB operation closure record is created 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 CBDAGMON_ NEW This is the operation code is to create a new CB agreemert It involves the following messages CBDAGMON_NEW Regq Full This is the request message to create a new CB agreement An external system which intends to save payment details 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 CBDAGMON_NEW Req lO This is the request message to create a new CB agreement An external system which intends to save pa
17. external system when clearing retention exception is closed The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 18 ReopenDocException This is the operation code to reopen new clearing retention exception maintenance It involves the following messages e ReopenDocException Req Full This is the request message to reopen clearing retention exception maintenance An external system which intends to reopen clearing retention exception maintenance 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 ReopenDocException Req lO This is the request message to reopen clearing retention exception maintenance An external system which intends to reopen clearing retention exception maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ReopenDocException Res Full This is the response message which is sent back to the external system when clearing retention exception is reopened 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 R
18. which has only those fields that are actually required for quering a cheque correspondence e QueryChequeCorrespondence Query Res Full This is the response message which will be sent back to the external system when a cheque correspondence account is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 38 ORACLE 6 2 6 24 e QueryChequeCorrespondence Query Res PK This is the response message which will be sent back to the external system when a cheque correspondence 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 correspondence record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key QueryChequeCorrespondence Query Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query a cheque correspondence fails due to any functional error ModifyChequeCorrespondence This is the operation code for modifying a cheque correspondence account in Oracle FLEXCUBE It involves the following messages 6 2 6 25 ModifyChequeCorrespondence Modify Reqg This is the request messa
19. 2 DEFINING ACCESS RIGHTS TO AN EXTERNAL SYSTEM c cccesssscecseseeeecseccececaceecsesaeeecsnsaeesssesecseaeeeeneneees 3 4 3 2 1 Viewing External System Function Details ccccsccesceessessseesseeecesecesecesecesecsecacecseeeseeeseeeaeeseeeeeenaees 3 5 3 2 2 Definirig Access Rights 10 QU SET ID oirinn nE E EE E E 3 7 3 2 3 Maintaining Upload Source Details c cccescceccceseesseeseesseeseeseeeeeceecesecsecsecsaecasecseeeseeeseesseeeeeeseseaees 3 7 3 2 4 Specifying Upload Source Preferences ccssccscesssessseeseeescessceecusecusecaaecaaeesaeeseeeaeeeeeeseeseeeeaeenaeenaeeaas 3 8 3 3 GATEWAY PASSWORD GENERATION LOGIC FOR EXTERNAL SYSTEM AUTHENTICATION 0 cccsseceeeeeeees 3 9 3 3 1 Password and Message ID GS input cccccccccesccesscesecesecesecseeseeeseeeeeesseeseeeecsecesecaecaecsaeeneesaeeeaeees 3 9 3 4 INCOMING MESSAGE BROWSER ssssssceceesseceseeceeceesaeeecsesaeceseeeecsesuececsesaececeaeecessaeeecsesaeeeceesaeeeseaeeeesges 3 11 3 4 1 Viewing Incoming Message Details 1 cccccsccesseeseessesseeeecesecesecesecseceaecaaeeaeeeseeeseeseeeeeeeeeeseenaeenee 3 13 3 5 DUPLICATE MESSAGE BROWSER ccssssscecsessececseccececsaeeecsesaececseeeceesuececseasececsaeecessaeeecsesaeeecsesaeeeesesessenas 3 14 3 3 1 Querying Duplicate Message BrowSer ccccccccsccesscesecesecuseeeeesseeseeseeeseeeeeeseceseceaecaesaeeaaeenseeneees 3 16 3 6 OUTGOING MESSAGE BOWSER cccssssscecsessecessnsceceesaececssa
20. Based Synchronous Deployment Patter n cccccccccesscecesscessseceseceescecuseceeacecuseceeaeeceaeeesaee 2 2 2 23 HTTP Servlet Based Synchronous Deployment Pattern ccccscccscceeesecessceenseceeseecuseceeaeecsaeceeaeecnaeeesaee 2 2 2 2 4 MDB Based Asynchronous Deployment Pattern c ccscceesceseseceensecessceenceceeeeeaeeceseeeeatecsaeeeeaeecsaeeesaes 2 2 23 OUTBOUND APPLICATION INTEGRATION ccccssececeessececssseececsececsesuececseceecessaeeeceesaececsenaeeeseaeeessesaeeeeneneees 2 3 2 4 RESPONSIBILITIES OF INTEGRATION GATEWAY ccccssscecssscecessececsesuececseneeceesuceecsesaececensaeesseaseeceesaeeesneneees 2 3 25 DEPLOYMENT OF ORACLE FLEXCUBE INTEGRATION GATEWAY cccccssssecesseeeeceeaeeecensaeeesseeecseaeeesssneees 2 3 2 6 DEPLOYMENT PATTERNS FOR APPLICATION INTEGRATION ss cccssssececsecceceeseeeeceeaececeneaeessseeeceeaeeeeseneees 2 3 2 7 FLEXML ADAPTER coc co 2 ech sy ies ooetiort asst ea eE coteeek yi ae E E 2 5 3 EXTERNAL SYSTEM MAINTENANCE cccssssscssssccccssscccsssssccssssscccesscccsecssccscsssscccessnscceessscessssscecessnee 3 1 3 1 IDEFINING AN EXTERNAL SYSTEM vocna one ioen r rrer E ines EEEE EE E EEA EEE A EEEE EK EEEE 3 1 3 1 1 Viewing External System Details ccccssciessneccvecsscviesecsersovecenaavasseessseoscusvtertoveetoanevseteabecsteesteuvivesneteets 3 3 3 1 2 Accessing Services ANd Operation cc scceccseceesseeeesscesscesecusecesecusecaeecaeecaeesaeesaeeeeeeeeeeesesenseeeaeeaeage 3 4 3
21. CreateCollDetails Res PK This is the response message which is sent back to the external system when new collection details are created 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 AmendCollDetails This is the operation code to amend collection details It involves the following messages e AmendCollDetails Req Full This is the request message to amend service details An external system which intends to amend service details 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 AmendeCollDetails Req lO This is the request message to amend service details An external system which intends to amend service details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query AmendeCollDetails Res Full This is the response message which is sent back to the external system when service details are maintained 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 AmendeCollDetails Res PK This is the response message which
22. Exchange Pattern Queue Request Message InputOnly v Default Response Queue e Response Message Full Screen w Dead Letter Queue e O XSD Validation Required C Register Response Queue Message Id External System Queues 7 l m In Queue Response Queue Fields FTP Parameters DOC504 Authorized By Modification Authorized Date Time Date Time The various details required by the External System Detailed screen are described below 3 1 1 1 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 3 1 ORACLE 3 1 1 2 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 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 3 1 1 3 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 Full Screen Response Message You can choose the Response message to be Full Screen
23. FLEXCUBE screen CreateManStatChanglnp Res PK This is the response message which is sent back to the external system when manual status is changed The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store CreateDCMaster This is the operation code for creating a card in Oracle FLEXCUBE It involves the following messages e CreateDCMaster Req This is the request message to create a card in Oracle FLEXCUBE UBS An external system which intends to create a card 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 card e CreateDCMaster Res Full This is the response message which will be sent back to the external system when a card is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CreateDCMaster Res PK This is the response message which will be sent back to the external system when a card 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 card record in the Oracle FLEXCUBE data store 6 53 ORACLE 6 2 8 13 e CreateDCMaster Flt This XML
24. 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 If the 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_FLGQ is Y 10 Reply message in FLEXML format is send back to the external system Outbound FLEXML Adapter An outbound adapter notifies any internal events 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
25. Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CBDDLMNT_ EXECUTEQUERY Res PK This is the response message which is sent back to the external system when query for CB document is queried 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 CBDDLMNT_ MODIFY This is the operation code is to modify CB document location record It involves the following messages 6 2 17 26 CBDDLMNT_MODIFY Req Full This is the request message to modify CB document location record An external system which intends to save payment details 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 CBDDLMNT_MODIFY Req lO This is the request message to modify CB document location record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDDLMNT_MODIFY Res Full This is the response message which is sent back to the external system when CB document location record is modified The format of the message is called Full screen resp
26. GWDINBRW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Incoming Message Browser Message Reference External System Message Id Correlation Id Message Status Service Name Operation Code Branch FLEXCUBE Reference User Id Their User Id Branch Date Queue Name Server Date Stamp Request Queue Message Id Repair Reason XML View Text View Gateway Messaging View m Message Reference Level Tag Name Node Parent id iO 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 in the XML format or the Text format Click Text View button to view the incoming messages in text format as shown below 3 11 ORACLE Text View Click XML View button to view the Gateway Browser Window screen which displays the messages in XML format e Gateway Browser Window Microsoft Internet Explorer lt FCUBS_ENVELOPE gt lt FCUBS_HEADER gt lt SOURCE gt FLEXCUBE lt SOURCE gt lt MSGID gt 9062070000001652 lt MSGID gt lt CORRELID gt lt CORRELID gt lt USERID gt SAURAV1 lt USERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCUBSCustomerSeryice lt SERVICE gt lt OPERATION gt CreateCust lt OPERAT
27. Id Request Queue Message Id Service Name Operation Code 3 14 ORACLE Click Text View button in the Duplicate Message Browser Summary screen to view the duplicate messages in the text format Duplicate Message Browser Text View Click XML View button in the Duplicate Message Browser Summary screen to view the duplicate messages in the following format Gateway Browser Window Microsoft Internet Explorer lt FCUBS_ENVELOPE gt lt FCUBS_HEADER gt lt SOURCE gt FLEXCUBE lt SOURCE gt lt MSG D gt 9062070000001652 lt MSG D gt lt CORRELID gt lt CORRELID gt lt USERID gt SAURAV1 lt USERID gt lt BRANCH gt PCU lt BRANCH gt lt SERVICE gt FCUBSCustomerService lt SERV ICE 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 Cust Static Create Res Full gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt C lt CTYPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU99999 lt LIABID gt lt CCATEG gt Individual lt CCATEG gt lt COUNTRY gt USA lt ICOUNTRY gt 4 Local intranet 3 15 ORACLE 3 5 1 Querying Duplicate Message Browser You can query the list of duplicate messages using the Duplicate Message Browser Summary screen with functions
28. Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store DeleteFunding This is the operation code to delete an online funding It involves the following messages 6 2 11 24 DeletePCFunding Req Full MSG This is the request message to delete an online funding An external system which intends to delete an online funding 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 DeletePCFunding Req IO MSG This is the request message to delete an online funding An external system which intends to delete an online funding has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query DeletePCFunding Res Full MSG This is the response message which is sent back to the external system when an online funding is done 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 DeletePCFunding Res PK MSG This is the response message which is sent back to the external system when an online funding is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle
29. 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 QueryDisbursementDetails Res PK This is the response message which is sent back to the external system when disbursement details are queried 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 16 13 DeleteDisbursement This operation is used to delete the loan disbursement Details It involves the following messages e DeleteDisbursementDetails Req Full This is the request message to delete disbursement details An external system which intends to save disbursement details has to send the request in the format specified The format of the message is called Full 6 92 ORACLE 6 2 16 14 screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen DeleteDisbursementDetails Req lO This is the request message to delete disbursement details An external system which intends to save disbursement details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save DeleteDisbursementDetails Res Full This is the response message which is sent back to the external system when
30. This is the request message to modify city code maintenance in Oracle FLEXCUBE UBS An external system which intends to city code maintenance 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 Embargo maintenance ModifyCityCode Res Full This is the response message which will be sent back to the external system when city code maintenance is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen ModifyCityCode Res PK This is the response message which will be sent back to the external system when city code maintenance is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which 6 61 ORACLE 6 2 8 33 includes only the primary key fields of city code maintenance record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key ModifyCityCode Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to modify city code maintenance fails due to any functional error CloseCityCode This is the operation code for closing city code mai
31. This is the request message to reopen a payment and collection beneficiary An external system which intends to reopen a payment and collection beneficiary has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ReopenPCBeneficiary Res Full MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done 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 ReopenPCBeneficiary Res PK MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done The format of 6 69 ORACLE the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store 6 2 11 5 BeneficiaryMaintenanceNew This is the operation code for creating a beneficiary in Oracle FLEXCUBE It involves the following messages e NewBeneficiaryMaintenance Req This is the request message to create a beneficiary in Oracle FLEXCUBE UBS An external system which intends to create a beneficiary 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 beneficiary e NewBene
32. all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryClInfoResponseDetails Res PK This is the response message which is sent back to the external system when loan account information are maintained 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 91 ORACLE 6 2 16 11 CreateDisbursement This operation is used to save a disbursement event in Oracle FLEXCUBE It involves the following messages e CreateDisbursementDetails Req Full This is the request message to create disbursement details An external system which intends to save disbursement details 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 CreateDisbursementDetails Req lO This is the request message to create disbursement details An external system which intends to create disbursement details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save e CreateDisbursementDetails Res Full This is the response message which is sent back to the external system when disbursement details are maintained The format of the message is c
33. 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 System 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 system invokes the adapter using EJB interface API method 5 1 ORACLE 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 5 2 1 Processing Incoming FLEXML Request Message 5 3 The inbound adapter processes an incoming request message in FLEXML format as follows 1 Adapter receives the request message in
34. 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 3 24 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 OPERATION gt lt MESSAGE EXCHANGE PATTERN gt _REQ e lt OPERATION gt lt MESSAGE EXCHANGE PATTERN gt _RES Where e lt OPERATIONS refers to an Oracle FLEXCUBE operation like CREATECUSTACC e lt MESSAGE_EXCHANGE_PATTERNSs refers to the request amp response message patterns ex
35. 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 3 3 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 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 3 3 1 Password and Message ID as input Message ID present as part of the header in Request XM
36. back to the external system when interest adjustment is done 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 79 ORACLE 6 2 13 2 ModifyinterestAdjustment This is the operation code to modify interest adjustment for branch account product and next liquidation date combination It involves the following messages e ModifylnterestAdjustment Reg Full MSG This is the request message to modify interest adjustment An external system which intends to modify interest adjustment 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 ModifylnterestAdjustment Reg IO MSG This is the request message to modify interest adjustment An external system which intends to modify interest adjustment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ModifylnterestAdjustment Res Full MSG This is the response message which is sent back to the external system when interest adjustment is modified 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 scre
37. book in the Oracle FLEXCUBE data store 6 2 2 4 CheckBookAuthorise This is the operation code for authorising cheque book details for a customer account in Oracle FLEXCUBE It involves the following messages e CheckBookAuthorise Req Full This is the request message to authorise cheque book details for a customer account in Oracle FLEXCUBE UBS An external system which intends to authorise 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 e CheckBookAuthorise Req lO This is the request message to authorise cheque book details for a customer account in Oracle FLEXCUBE UBS An external system which intends to authorise 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 authorising cheque book e CheckBookAuthorise Res Full This is the response message which is sent back to the external system when cheque book details for a customer account is successfully authorised 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 CheckBookAuthorise Res PK This is the response message which is sent bac
38. called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen ModifyStopPaymentsReversal Req IO This is the request message to modify the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to modify the details for reversing stop payments 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 the details for reversing stop payments ModifyStopPaymentsReversal Res Full This is the response message which is sent back to the external system when the details for reversing stop payments are 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 ModifyStopPaymentsReversal Res PK This is the response message which is sent back to the external system when the details for reversing stop payments are 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 stop payments reversal record in the Oracle FLEXCUBE data store 6 9 ORACLE 6 2 2 9 AuthoriseStopPaymentsReversal This is the operation code for authorizing the details for reversing stop
39. code to create extend release for Uncollected funds for account It involves the following messages e CreateExtendOrRelease Req Full This is the request message to create extend release for Uncollected funds for account An external system which intends to create extend release for Uncollected funds for 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 CreateExtendOrRelease Req lO This is the request message to create extend release for Uncollected funds for account An external system which intends to create extend release for Uncollected funds for account has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CreateExtendOrRelease Res Full This is the response message which is sent back to the external system when the extension release of uncollected funds for account is 6 39 ORACLE 6 2 6 26 created 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 CreateExtendOrRelease Res PK This is the response message which is sent back to the external system when the extension release of uncollected funds for account is crea
40. contains only the primary key of the transaction 5 3 1 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 5 2 ORACLE 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 5 3 2 Mapping FLEXML Format Messages to Gateway Format FLEXML uses DTDs to define the structure of an XML document whereas Gateways 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 docume
41. corporate deposits simulation in Oracle FLEXCUBE UBS An external system which intends to activate corporate deposits simulation has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen LDActivateSimulate Req 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 FL
42. corresponding Oracle FLEXCUBE screen e 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 9 AmountBlocksNew This is the operation code for creating a new amount block in Oracle FLEXCUBE It involves the following messages e AmountBlocksNew Req Full This is the request message to create a new amount block in Oracle FLEXCUBE UBS An external system which intends to create a new 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 e AmountBlocksNew Req lO This is the request message to create a new amount block in Oracle FLEXCUBE UBS An external system which intends to create a new 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 an amount block e AmountBlocksNew Res Full This is the response message which is sent back to the external system when a new amount block is successfully created in Oracle FLEXCUBE UBS The format of th
43. delete CB contract An external system which intends to save payment details 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 CBDTRONL_DELETE Req lO This is the request message to delete CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDTRONL_DELETE Res Full This is the response message which is sent back to the external system when CB contract is deleted 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 CBDTRONL_DELETE Res PK This is the response message which is sent back to the external system when CB contract is deleted 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 CBDTRONL_ AUTH This is the operation code is to authorize CB contract It involves the following messages CBDTRONL_AUTH Regq Full This is the request message to authorize CB contract An external system which intends to save payment details has to send the request
44. disbursement details are maintained 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 DeleteDisbursementDetails Res PK This is the response message which is sent back to the external system when disbursement details are maintained 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 ReverseDisbursement This operation is used to reverse the loan disbursement It involves the following messages ReverseDisbursementDetails Req Full This is the request message to reverse disbursement details An external system which intends to reverse disbursement details 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 ReverseDisbursementDetails Req lO This is the request message to reverse disbursement details An external system which intends to reverse disbursement details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save ReverseDisbursementDetails Res Full This is the response message which is sent back to the external system
45. external system when CB location code is modified 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 CBDPRMNT_ EXECUTEQUERY This is the operation code is to query for CB location code It involves the following messages 6 2 17 33 CBDPRMNT_ EXECUTEQUERY Req Full This is the request message to query for CB location code An external system which intends to save payment details 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 CBDPRMNT_ EXECUTEQUERY Req lO This is the request message to query for CB location code An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDPRMNT_ EXECUTEQUERY Res Full This is the response message which is sent back to the external system when query for CB location code is queried 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 CBDPRMNT_EXECUTEQUERY Res PK This is the response message which is sent back to the external system wh
46. external system which intends to delete an External Service has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e DeleteCExtService Res Full This is the response message which is sent back to the external system when an External Service is deleted 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 57 ORACLE 6 2 8 23 e DeleteCExtService Res PK This is the response message which is sent back to the external system when an External Service is deleted The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store QueryCExtService This is the operation code to query an External Service It involves the following messages 6 2 8 24 e QueryCExtService Req Full This is the request message to query an External Service An external system which intends to query an External Service 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 QueryCExtService Req lO This is the request message to query an External Service An external system which in
47. fields of the record in the Oracle FLEXCUBE data store QueryDocException This is the operation code to query new clearing retention exception maintenance It involves the following messages QueryDocException Req Full This is the request message to query clearing retention exception maintenance An external system which intends to query clearing retention exception maintenance 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 QueryDocException Req lO This is the request message to query clearing retention exception maintenance An external system which intends to query clearing retention exception maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryDocException Res Full This is the response message which is sent back to the external system when clearing retention exception is queried 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 QueryDocException Res PK This is the response message which is sent back to the external system when clearing retention exception is queried The format of the message is called Primar
48. for search You can invoke this screen by typing GWSPBROW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Duplicate Message Browser Summary Message Reference H Branch External System a Message Id Correlation Id Request Queue Message Id Service Name GE Operation Code User Id a Their User Id Server Date Stamp Status Media Queue Name Q Search Advanced Search Reset Records per page Id 4 of 1 LI oO Message Reference Branch External System Message Id Correlation Id Request Queue Message Id Service Name Operation Code 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 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 3 16 ORACLE 3 6 Outgoing Message Bowser Once the incoming messages have been processe
49. format specified The format of the message is called Input only which has only those fields that can be used to query ReopenPmtAgreement Res Full MSG This is the response message which is sent back to the external system when a payment agreement is done 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 ReopenPmtAgreement Res PK MSG This is the response message which is sent back to the external system when a payment agreement is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store QueryPmtAgreement This is the operation code to query a payment agreement It involves the following messages e QueryPmtAgreement Req Full MSG This is the request message to query a payment agreement An external system which intends to query a payment agreement 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 QueryPmtAgreement Req lO MSG This is the request message to query a payment agreement An external system which intends to query a payment agreement has to send the request in the format specified The format of the message is called Input only
50. 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 FA 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 request has to be replayed at the host during replay e any error has occ
51. is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 8 2 ModifyAccClasMaint This is the operation code to Modify an account class It involves the following messages e ModifyAccClasMaint Req Full This is the request message to modify an account class An external system which intends to modify an account class 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 ModifyAccClasMaint Req lO This is the request message to modify an account class An external system which intends to modify an account class has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ModifyAccClasMaint Res Full This is the response message which is sent back to the external system when an account class is modified 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 ModifyAccClasMaint Res PK This is the response message which is sent back to the external system when an account class is modified The format of the message is called Primary Key response which includes only the p
52. is sent back to the external system when service details are maintained 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 86 ORACLE 6 2 15 8 QueryCollDetails This is the operation code to query collection details It involves the following messages QueryCollDetails Req Full This is the request message to query service details An external system which intends to query service details 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 QueryCollDetails Req lO This is the request message to query service details An external system which intends to query service details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryCollDetails Res Full This is the response message which is sent back to the external system when service details are maintained 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 QueryCollDetails Res PK This is the response message which is sent back to the external system when ser
53. is the response message which is sent back to the external system when an extension request for CB contract is queried 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 CBDRQMNT_MODIFY This is the operation code is to modify extension request for CB contract It involves the following messages e CBDRQMNT_ MODIFY Req Full This is the request message to modify extension request for CB contract An external system which intends to save payment details 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 CBDRQMNT_ MODIFY Req IO This is the request message to modify extension request for CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDRQMNT_ MODIFY Res Full This is the response message which is sent back to the external system when extension request for CB contract is modified 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 CBDRQMNT_ MODIFY
54. lO This is the request message to reopen beneficiary details An external system which intends to reopen beneficiary details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ReopenBeneficiaryMaintenance Res Full This is the response message which is sent back to the external system when beneficiary details are reopened 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 ReopenBeneficiaryMaintenance Res PK This is the response message which is sent back to the external system when beneficiary details are reopened The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store BeneficiaryMaintenanceExq This is the operation code to query beneficiary details It involves the following messages e QueryBeneficiaryMaint Req Full This is the request message to query a beneficiary details An external system which intends to query beneficiary details 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 QueryBeneficiaryMaint Req lO This is the reques
55. 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 6 20 ORACLE simulation contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying LD VAMI simulation e 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 It involves the following messages e 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 e 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 resp
56. message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create a card fails due to any functional error ModDCMaster This is the operation code to Modify card details It involves the following messages 6 2 8 14 e ModifyDCMaster Req Full This is the request message to modify card details An external system which intends to modify card detailshas 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 ModifyDCMaster Req lO This is the request message to modify card details An external system which intends to modify card details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifyDCMaster Res Full This is the response message which is sent back to the external system when card details are modified 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 ModifyDCMaster Res PK This is the response message which is sent back to the external system when card details are modified The format of the message is called Primary Key response which includes only the primary key fields of the reco
57. of the message is called Input only which has only those fields that can be used to query CreatePCBeneficiary Res Full MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done 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 CreatePCBeneficiary Res PK MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ModifyPCBeneficiary This is the operation code to modify a payment and collection beneficiary It involves the following messages ModifyPCBeneficiary Req Full MSG This is the request message to modify a payment and collection beneficiary An external system which intends to modify a payment and collection beneficiary 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 ModifyPCBeneficiary Reg IO MSG This is the request message to modify a payment and collection beneficiary An external system which intends to modify a payment and 6 68 ORACLE 6
58. or Record Identification Msg You can select Record Identification Msg as the response message only if you select Input Only in the request message 3 1 1 4 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 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 3 1 1 5 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 Specify the name of the queue from which the messages were received The name of the queue will help identif
59. request message sent by the external system for closure of a stop payment parameter record An external system which intends to close a stop payment parameter 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 screen CloseStopPaymentsParameter Req PK This is the request message sent by the external system for closure of a stop payment parameter record An external system which intends to close the stop payment parameter record has to send the request in the format specified The format of the message is called Primary Key which includes only the primary key fields of the record CloseStopPaymentsParameter Res Full This is the response message which is sent back to the external system when a stop payment parameter record is successfully closed in Oracle FLEXCUBE The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CloseStopPaymentsParameter Res PK This is the response message which is sent back to the external system when a stop payment parameter record is successfully closed in Oracle FLEXCUBE The format of the message is called Primary Key response which includes only the primary key fields of the record ModifyStopPaymentsParameter Modi
60. sent back to the external system when a clearing service point is successfully reopened in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e ReopenClgServicePoint Reopen Res PK This is the response message which will be sent back to the external system when a clearing service point 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 clearing service point record in the Oracle FLEXCUBE data store Note This response will be sent if the resoonse Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e ReopenClgServicePoint Reopen Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to reopen a clearing service point fails due to any functional error 6 2 6 23 QueryChequeCorrespondence This is the operation code for querying a cheque correspondence account in Oracle FLEXCUBE It involves the following messages e QueryChequeCorrespondence Query Req This is the request message to query a cheque correspondence in Oracle FLEXCUBE UBS An external system which intends to query the cheque correspondence has to send the request in the specified format The format of the message is called Input only
61. the display fields as in the corresponding Oracle FLEXCUBE screen e CloselnterestAdjustment Res PK MSG This is the response message which is sent back to the external system when interest adjustment is closed 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 13 4 ReopeninterestAdjustment This is the operation code to re open interest adjustment for branch account product and next liquidation date combination It involves the following messages e ReopeninterestAdjustment Reg Full MSG This is the request message to reopen interest adjustment An external system which intends to close interest adjustment 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 6 80 ORACLE 6 2 13 5 ReopenInterestAdjustment Req lO MSG This is the request message to close interest adjustment An external system which intends to reopen interest adjustment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ReopeninterestAdjustment Res Full MSG This is the response message which is sent back to the external system when interest adjustment is reopened The format of
62. 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 e 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 6 2 ORACLE screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e DeleteMt101 Req lO 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 e 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 Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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 whi
63. the format specified The format of the message is called Input only which has only those fields that can be used to query e QueryCollectionCheque Res Full This is the response message which is sent back to the external system when a collection cheque transaction is queried 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 QueryCollectionCheque Res PK This is the response message which is sent back to the external system when a collection cheque transaction is queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store ReverseCollectionCheque This is the operation code to reverse a collection cheque transaction It involves the following messages e ReverseCollectionCheque Reqg Full This is the request message to reverse a collection cheque transaction An external system which intends to collection cheque 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 e ReverseCollectionCheque Req lO This is the request message to reverse collection cheque transaction An external system which intends to reverse collec
64. transaction has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying a DD transaction e 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 e 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 2 4 FCUBSLDService Corporate deposit operations are logically grouped under a service called FCUBSLDService 6 18 ORACLE Oracle e e e e e e FLEXCUBE supports the following operations under this service LDActivate Simulate DeleteLDSIMContract QueryLDS IMContract LDVamiCreateSim LDVamiQuerySim QueryLDPaymentSim CreateLDPaymentSim 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
65. which has only those fields that can be used to query QueryPmtAgreement Res Full MSG This is the response message which is sent back to the external system when a payment agreement is done 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 QueryPmtAgreement Res PK MSG This is the response message which is sent back to the external system when a payment agreement is done The format of the message is 6 73 ORACLE called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store 6 2 11 15 AmendPmtMode This is the operation code to amend a payment mode It involves the following messages e AmendPmtMode Reg Full MSG This is the request message to amend a payment mode An external system which intends to amend a payment mode 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 AmendPmtMode Reqg lO MSG This is the request message to amend a payment mode An external system which intends to amend a payment mode has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to amend e AmendPmtMode Res Full M
66. which has only those fields that can be used to query AmountBlocksQuery Res Full This is the response message which is sent back to the external system when an amount block 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 AmountBlocksQuery Res PK This is the response message which is sent back to the external system when an amount block 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 amount block record in the Oracle FLEXCUBE data store AmountBlocksClose This is the operation code for closing an amount block in Oracle FLEXCUBE It involves the following messages AmountBlocksClose Req Full This is the request message to close an amount block in Oracle FLEXCUBE UBS An external system which intends to close an amount block has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen AmountBlocksClose 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 6 27 ORACLE to send the request in the spec
67. 1 2 AuthorizeMt101 This is the operation code for authorizing MT101 message in Oracle FLEXCUBE It involves the following messages e 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 e 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 e 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 fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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
68. 2 1 2 Gateway Functions An Overview Introduction Integration 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 Synchron
69. 2 11 3 collection beneficiary has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifyPCBeneficiary Res Full MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done 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 ModifyPCBeneficiary Res PK MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ClosePCBeneficiary This is the operation code to close a payment and collection beneficiary It involves the following messages 6 2 11 4 ClosePCBeneficiary Req Full MSG This is the request message to close a payment and collection beneficiary An external system which intends to close a payment and collection beneficiary 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 ClosePCBeneficiary Req IO MSG This is the request message to close a payment and coll
70. An external system which intends to reopen the details for reversing stop payments 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 the details for reversing stop payments ReopenStopPaymentsReversal Res Full This is the response message which is sent back to the external system when the details for reversing stop payments are 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 ReopenStopPaymentsReversal Res PK This is the response message which is sent back to the external system when the details for reversing stop payments are 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 stop payments reversal record in the Oracle FLEXCUBE data store QueryStopPaymentsReversal This is the operation code for querying the details for reversing stop payments for an individual cheque in Oracle FLEXCUBE It involves the following messages 6 2 2 13 QueryStopPaymentsReversal Req Full This is the request message to query the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to query has to send the request in the forma
71. An external system which intends to close CG product maintenance 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 CloseCGProductMaint Req lO This is the request message to close a CG product maintenance An external system which intends to modify CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CloseCGProductMaint Res Full This is the response message which is sent back to the external system when a CG product maintenance is closed 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 CloseCGProductMaint Res PK This is the response message which is sent back to the external system when a CG product maintenance is closed The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 9 ReopenCGProductMaint This is the operation code to reopen a CG product maintenance It involves the following messages e ReopenCGProductMaint Req Full This is the request message to reopen a CG product maintenance An external s
72. CBGPMTON_NEW Req lO This is the request message to create a protest for CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save e CBGPMTON_NEW Res Full This is the response message which is sent back to the external system when a protest for CB contract is created 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 CBGPMTON_NEW Res PK This is the response message which is sent back to the external system when a protest for CB contract is created 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 17 8 CBGPROON NEW This is the operation code is to create a protest for CB contract It involves the following messages e CBGPROON_NEW Regq Full This is the request message to create a protest for CB contract An external system which intends to save payment details 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 CBGPROON_NEW Req lO This is the req
73. CONVERSION ccssssssssrsssssssnsesssssssesssssnsesssssnsesssssnsessssnsessesensesseees 5 1 5 1 TONU y LO D OL C4 H COIN AAEE 5 1 5 2 INBOUND FLEXML ADAPTER c cccccccsssessscecececeesesesececececseseseceeececeesasesecececeesaaeceeececseseaaeseceeeeeeneasaeeeeecs 5 1 3 2 1 Processing Incoming FLEXML Request Message csccccccccsscesssecssscesssecseceeseecnseceeseecsseseeeseesaeensaes 5 2 5 3 OUTBOUND FLEXML ADAPTER cccceessssececececsessecececececesuseeseeececsessaaeceeececeeaascecececeensaeaesecseeeneneaeeeeecs 5 2 dol Processing Outbound Messages cccceessessceeecesecesecesecsecseesseeseeeaeeeseeseeeseeesecesecaeceaecaaeeaaeeaaeeasees 5 2 5 3 2 Mapping FLEXML Format Messages to Gateway Format sssoseessesessesesseresrereereerreresrrrresrsreerreee 5 3 6 ANNEXURE LIST OF MESSAGES eeeessesesssesessseessocecssoceessecescseesseoeesseceesseesescoeessocecssoceessecessseesssosessecessse 6 1 6 1 INTRODUCTION ciriisene reais nE E VS RES A EE AE ROE E E OA R AA EER 6 1 6 2 INBOUND APPLICATION INTEGRATION SERVICES cccccsesssscecececeeseeaeceeececsesseaesesecsesesenseaeseeeeeesessaseeeees 6 1 6 2 1 P GCUBSETS Crvie EE EEE EENE AE R AE E AAE A E AAEE non Sinbad ees 6 1 6 2 2 F CU BSAGCS CFV 1CG inicien i cone a E aaaeeeaa Taa aa a cabs ban aba E aaO 6 5 6 2 3 P CUBS DDS rV 1G a i a a a E a a a E Ea ae a E atk E EE we oe RE 6 17 6 2 4 PF CUBSLDS CIV 1C 6 ok vdcsvsiencitssscdstcnsenecondscndshanseencoeesucdsbe
74. CUBE screen QueryCollAgreement Res PK This is the response message which is sent back to the external system when a collection service agreement is done 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 CreateCollDetails This is the operation code to create collection details It involves the following messages 6 2 15 7 CreateCollDetails Req Full This is the request message to create new collection details An external system which intends to create new collection details 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 CreateCollDetails Req lO This is the request message to create new collection details An external system which intends to create new collection details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CreateCollDetails Res Full This is the response message which is sent back to the external system when new collection details are created 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
75. CityCode This is the operation code for querying city code maintenance in Oracle FLEXCUBE It involves the following messages QueryCityCode Reg This is the request message to query city code maintenance in Oracle FLEXCUBE UBS An external system which intends to city code maintenance 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 Embargo maintenance QueryCityCode Res Full This is the response message which will be sent back to the external system when city code maintenance is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryCityCode Res PK This is the response message which will be sent back to the external system when city code maintenance 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 city code maintenance record in the Oracle FLEXCUBE data store 6 62 ORACLE Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e QueryCityCode Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to q
76. Deployment Pattern The web services deployment 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 Serviet 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 ap
77. E data store 6 2 8 4 QueryAccClasMaint This is the operation code to query an account class It involves the following messages e QueryAccClasMaint Req Full This is the request message to query an account class An external system which intends to query an account class 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 QueryAccClasMaint Req lO This is the request message to query an account class An external system which intends to query an account class has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e QueryAccClasMaint Res Full This is the response message which is sent back to the external system when an account class is queried 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 QueryAccClasMaint Res PK This is the response message which is sent back to the external system when an account class is queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 8 5 AuthAccClasMaint This is the operation code for aut
78. EXCUBE 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 e FCUBS_BODY This node contains the actual payload of a message The contents of this node will vary for each message 4 2 ORACLE 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 4 3 ORACLE CORRELID This is the id using which any system which has sent a request to FC UBS can correlate to the response 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
79. EXCUBE 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 e DeleteLDSIMContract Req Full This is the request message to delete LD simulation contract in Oracle FLEXCUBE UBS An external system which intends to delete LD simulation contract has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e DeleteLDSIMContract Req IO This is the request message to delete LD simulation contract in Oracle FLEXCUBE UBS An external system which intends to delete LD simulation contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for deleting LD simulation contract e 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 6 19 ORACLE includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e DeleteLDSIMContract Res PK This is the response message which is sent back to the external system when an existing LD simulation co
80. Embargo Query Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query an Embargo transaction fails due to any functional error 6 2 7 5 EmbargoDelete This is the operation code for deleting an Embargo transaction in Oracle FLEXCUBE It involves the following messages e Embargo Delete Req This is the request message to deleting an Embargo transaction in Oracle FLEXCUBE UBS An external system which intends to delete an Embargo 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 deleting an Embargo transaction e Embargo Delete Res Full This is the response message which will be sent back to the external system when an Embargo transaction is successfully deleting in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e Embargo Delete Res PK This is the response message which will be sent back to the external system when an Embargo transaction 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 an Embargo transaction record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message
81. Exchange Pattern in the Gateway External system maintenance in set as Primary Key e Embargo Delete Flit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to delete an Embargo transaction fails due to any functional error 6 2 7 6 NewEmbargoMaint This is the operation code for creating an Embargo maintenance in Oracle FLEXCUBE It involves the following messages e EmbargoMaint New Reg This is the request message to create an Embargo maintenance in Oracle FLEXCUBE UBS An external system which intends to create Embargo maintenance 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 Embargo maintenance e EmbargoMaint New Res Full This is the response message which will be sent back to the external system when Embargo maintenance is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e EmbargoMaint New Res PkK This is the response message which will be sent back to the external system when Embargo maintenance 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 an Embargo maintenance record in the O
82. FLEXCUBE It involves the following messages Embargo Modify Req This is the request message to modify an Embargo transaction in Oracle FLEXCUBE UBS An external system which intends to modify an Embargo 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 modifying an Embargo transaction Embargo Modify Res Full This is the response message which will be sent back to the external system when an Embargo transaction is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 43 ORACLE e Embargo Modify Res PK This is the response message which will be sent back to the external system when an Embargo transaction 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 an Embargo transaction record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e Embargo Modify Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to modify an Embargo transaction fails due to any functional error
83. Gateway Services Oracle FLEXCUBE Universal Banking Release 11 3 1 0 0LA May 2013 Oracle Part Number E51536 01 ORACLE FINANCIAL SERVICES ORACLE Gateway Services Table of Contents 1 ABOUT THIS MANDA Livsssscccsiccisisssecssicscescssvscescesescsitesnacosssseasosscsescbesesnsdesieassdesssesdsseassessuacesescbadssosansssavacaseese 1 1 1 1 INTRODUCTION carer eae ca his vecedece var Selves Spek ee Ab AG eee Aad cede al EAS 1 1 1 2 AUDIENCE se sods Sess ie a aei a A E a feed ep Ag badedeves ag chsct bet duct A E EEEE E S 1 1 1 3 ACRONYMS AND ABBREVIATIONS creeeren a i a E E EER AEREA E A O AAE NERE A 1 1 1 4 ORGANIZATION srca e E Oa epeteiatadeleveeasdessteactl A E a E EER E S 1 1 1 5 CONVENTIONS USED IN THIS MANUAL cccscccesssscecsessececssscececsececsesuececsesseceesaesecsesaeeecsesaeessaeeecsesaeceeseaaees 1 1 1 6 GLOSSARY OF ICONS 2503 code sives Jessi e a EE a eedep EE a E a O a EERE hee 1 2 2 GATEWAY FUNCTIONS AN OVERVIEW esessssessosecsseceesseceseseessooeesseceesseceesoecssocecsseoeessecessseesssoeesseseesse 2 1 2 1 INTRODUCTION woosscssesdeevesgccencadsecesesnecagessdgs eaa aa ea E a EE A Oop Aaa Aa aaa E o SEE ESEA aR E E 2 1 2 2 INBOUND APPLICATION INTEGRATION ccccsccessesceceessececenseeeecsececseauececseaaececsaeeeceesaeeecsesaeeesaeeecseaeeseneaaees 2 1 2 2 1 EJB Based Synchronous Deployment Pattern cccccccssecessceenseceeneeensecesscecusecseneecaeceeaeecsseceeneecnaeeesaes 2 1 2 22 Web Services
84. ION 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 Cust Static Create Res Full gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt C lt CTYPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU99999 lt LIABID gt lt CCATEG gt Individual lt CCATEG gt lt COUNTRY gt USA lt COUNTRY gt zl BB vocal intranet Z 3 12 ORACLE 3 4 1 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 GWSINBRW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button incoming Message Browser Message Reference Branch External System la Message Id Correlation Id H Request Queue Message Id Service Name z3 Operation Code User Id Their User Id Branch Date Server Date Stamp AEA Message Status FLEXCUBE Reference Q Search Advanced Search Reset Records per page oO Message Reference Branch External System Message Id Correlation Id Request Queue Message Id Service Name Operation Code This summary screen can be used to s
85. L 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 3 9 ORACLE Example A Sample Java Code To Do The Encryption Is Given Below import java security MessageDigest import java util Arrays import javax crypto Cipher import javax crypto spec lvParameterSpec import javax crypto spec SecretKeySpec import org apache commons codec binary Base64 txtPass PASSWORD msgid MESID MessageDigest mDigest MessageDigest getInstance SHA 512 byte digestSeed mDigest digest msgid getBytes byte seedEncArray Arrays copyOf digestSeed 24 Cipher cipher Cipher getInstance DESede CBC PKCS5Padding SecretKeySpec skspec new SecretKeySpec seedEncArray DESede IvParameterSpec iv new IvParameterSpec new byte 8 cipher init Cipher ENCRYPT_MODE skspec iv byte finalByteArray cipher doFinal txtPass String finalValue new String Base64 encodeBase6 4 finalByteArray 3 10 ORACLE 3 4 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
86. LE 6 2 15 1 CreateCollAgreement AmendCollAgreement CloseCollAgreement ReopenCollAgreement QueryCollAgreement CreateCollDetails AmendCollDetails QueryCollDetails CreateCollAgreement This is the operation code to create coll agreement It involves the following messages 6 2 15 2 CreateCollAgreement Req Full This is the request message to create new collection service agreement An external system which intends to create new collection service agreement 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 CreateCollAgreement Req IO This is the request message to create new collection service agreement An external system which intends to create new collection service agreement has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CreateCollAgreement Res Full This is the response message which is sent back to the external system when new collection service agreement is done 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 CreateCollAgreement Res PK This is the response message which is sent back to the external system w
87. Modify Res Full This is the response message which is sent back to the external system when an existing amount block is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen AmountBlocksModify Res PK This is the response message which is sent back to the external system when an existing 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 record in the Oracle FLEXCUBE data store AmountBlocksQuery This is the operation code for querying an amount block in Oracle FLEXCUBE It involves the following messages 6 2 5 12 AmountBlocksQuery Req Full This is the request message to query on an amount block in Oracle FLEXCUBE UBS An external system which intends to query 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 AmountBlocksQuery Req lO This is the request message to query on an amount block in Oracle FLEXCUBE UBS An external system which intends to query amount block has to send the request in the specified format The format of the message is called Input only
88. RY Reg Full This is the request message to execute query a CB contract An external system which intends to save payment details 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 CBDTRONL_EXECUTEQUERY Req lO This is the request message to execute query a CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDTRONL_EXECUTEQUERY Res Full This is the response message which is sent back to the external system when query a CB contract is executed 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 CBDTRONL_EXECUTEQUERY Res PK This is the response message which is sent back to the external system when query a CB contract is executed 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 CBDTRONL DELETE This is the operation code is to delete CB contract It involves the following messages 6 2 17 4 CBDTRONL_DELETE Req Full This is the request message to
89. Res Full MSG This is the response message which is sent back to the external system when interest adjustment is authorized 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 81 ORACLE e AuthorizelnterestAdjustment Res PK MSG This is the response message which is sent back to the external system when interest adjustment is authorized The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 13 7 DeletelInterestAdjustment This is the operation code to delete interest adjustment for branch account product and next liquidation date combination It involves the following messages e DeletelnterestAdjustment Req Full MSG This is the request message to delete interest adjustment An external system which intends to delete interest adjustment 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 DeletelnterestAdjustment Req IO MSG This is the request message to delete interest adjustment An external system which intends to delete interest adjustment has to send the request in the format specified The format of the message is called Input onl
90. Res PK This is the response message which is sent back to the external system when CB location code is created 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 CBDLOMNT_ EXECUTEQUERY This is the operation code is to query for CB location code It involves the following messages 6 2 17 31 CBDLOMNT_ EXECUTEQUERY Req Full This is the request message to query for CB location code An external system which intends to save payment details 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 CBDLOMNT_ EXECUTEQUERY Recq lO This is the request message to query for CB location code An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDLOMNT_ EXECUTEQUERY Res Full This is the response message which is sent back to the external system when query for CB location code is queried 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 CBDLOMNT_ EXECUTEQUERY Res PK This is the r
91. SG This is the response message which is sent back to the external system when a payment mode is amended 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 AmendPmtMode Res PK MSG This is the response message which is sent back to the external system when a payment mode is amended The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store 6 2 11 16 QueryPmtMode This is the operation code to query a payment mode It involves the following messages e QueryPmtMode Req Full MSG This is the request message to query a payment mode An external system which intends to query a payment mode 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 QueryPmtMode Reqg lO MSG This is the request message to query a payment mode An external system which intends to query a payment mode has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e QueryPmtMode Res Full MSG This is the response message which is sent back to the external system when a payment mode is querie
92. 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 102 ORACLE 6 2 17 22 CBDNRMNT_EXECUTEQUERY Res PK This is the response message which is sent back to the external system when query for CB notary code is queried 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 CBDNRMNT_ MODIFY This is the operation code is to modify CB notary code record It involves the following messages 6 2 17 23 CBDNRMNT_ MODIFY Req Full This is the request message to modify CB notary code record An external system which intends to save payment details 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 CBDNRMNT__ MODIFY Req lO This is the request message to modify CB notary code record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDNRMNT_ MODIFY Res Full This is the response message which is sent back to the external system when CB notary code record is modified The f
93. 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 QueryLoan accountDetails Res PK This is the response message which is sent back to the external system when loan account details are maintained 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 CreateVami This operation is used to save a Value dated Amendment in Oracle FLEXCUBE It involves the following messages SaveVami Req Full This is the request message to save value dated amendment An external system which intends to save value dated amendment details 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 SaveVami Req lO This is the request message to save value dated amendment An external system which intends to save value dated amendment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save SaveVami Res Full This is the response message which is sent back to the external system when value dated amendment details are maintained The format of the message is c
94. This is the request message to create a payment agreement An external system which intends to create a payment agreement has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CreatePmtAgreement Res Full MSG This is the response message which is sent back to the external system when a payment agreement is done 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 CreatePmtAgreement Res PK MSG This is the response message which is sent back to the external system when a payment agreement is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ModifyPmtAgreement This is the operation code to modify a payment agreement It involves the following messages 6 2 11 12 ModifyPmtAgreement Req Full MSG This is the request message to modify a payment agreement An external system which intends to modify a payment agreement 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 ModifyPmtAgreement Req IO MSG This is the request message to modify a payment agre
95. This operation creates a Customer Category Maintenance in Oracle FLEXCUBE An external system which intends to create a customer category has to send the request in the format specified 6 2 8 40 ModifyCustCatMaint This operation modifies a Customer Category Maintenance in Oracle FLEXCUBE An external system which intends to modify a customer category has to send the request in the format specified 6 2 8 41 QueryCustCatMaint This operation queries a Customer Category Maintenance in Oracle FLEXCUBE An external system which intends to query a customer category has to send the request in the format specified 6 2 9 FCUBSPARQRYService All the operations that are exposed as part of the Integrated parity services are logically grouped under a service called FCUBSPARQRYService Oracle FLEXCUBE supports the following operations under this service e QueryParityMismatch Message to query the parity mismatch 6 2 10 FCUBSTDService All the operations that can be performed on a Term Deposit account are logically grouped under a service called FCUBSTDService Oracle FLEXCUBE supports the following operations under this service e ModifyTDAcc e CreateTDAcc e QueryTDAcc e QueryTDEndorHist e CreateFraction e AuthorizeFraction e ModifyFraction e QueryFraction e DeleteFraction e CreatePrepmntReq e ModifyPrepmntReq e QueryPrepmntReq e SavePrePmntReq e TDRedemSave e QueryTDPrintcert e Create TDpayin e Reve
96. ack to the external system when a record is created The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 2 CloseSecCode This is the operation code to close a record in the sector code maintenance It involves the following messages CloseSecCode Req Full This is the request message to close a record An external system which intends to close 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 CloseSecCode Req lO This is the request message to close a record An external system which intends to close a record has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CloseSecCode Res Full This is the response message which is sent back to the external system when a record is closed 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 CloseSecCode Res PK This is the response message which is sent back to the external system when a record is closed The format of the message is called Primary 6 29 ORACLE Key response
97. act extension request is created 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 CBDRQMNT_EXECUTEQUERY This is the operation code is to query extension request for CB contract It involves the following messages 6 107 ORACLE 6 2 17 35 CBDRQMNT_ EXECUTEQUERY Regq Full This is the request message to query extension request for CB contract An external system which intends to save payment details 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 CBDRQMNT_ EXECUTEQUERY Req lO This is the request message to query extension request for CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDRQMNT_ EXECUTEQUERY Res Full This is the response message which is sent back to the external system when an extension request for CB contract is queried contract is created 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 CBDRQMNT_ EXECUTEQUERY Res PK This
98. aeceseeeeceesaececsesaececsueeecessaeeecsesaeesceesaeesesseeessgas 3 17 3 6 1 Querying Outgoing Message BrowSer cccccccccsscessceseceecuseesseesseeseeseceeeeeeecesecesecesesaecaeeaaeeaeeeaeees 3 19 3 7 DEFINING NOTIFICATION MESSAGES 0 ccsssseceesesceceesseeecsesaececeeeeceesuececsesaececsneeceesaeeecsesaeeeseeseeeessesessenas 3 19 3 7 1 Viewing Installed Notification Details cccccccccscseesseesesscesecesecesecesecaeeeaeeeseeeeeeeeeeneeeseeesecnaeenaeeats 3 20 3 8 DEFINING THE NOTIFICATIONS ENROUTES csecccceessscecesssececeececeeuececsesaececseneecseaeeeceesaeeeseeaeenssneseesenas 3 22 3 8 1 Viewing SUMMATY STEH orses sirine ae ne rsa EEE EE REENE EPEE ENE EEEE NOE EE EEE ERE ERE Ri 3 22 3 9 MAINTAINING MT TASK DETAILS 0 cccesssecessscceceeseeeeceenaececeeeeceesuececsenaececaaeecsesaeeeceesaeesenneeeeneseeeeseaes 3 23 4 MESSAGE FORMATS sssssssssssssssssscesoasscsscsssessscosesessesseesseseasssaseacssascsedesesseesssesesessauscbeasbescesasesssesbsbeesoasseaceseses 4 1 4 1 INTRODUCTION 4 esne E E E E E eee 4 1 4 2 ORACLE FLEXCUBE ENVELOPE rere aerer EE EEEE EERE KER EEEE EE REER EE N E 4 2 4 2 1 FCUBS HEADER iine E A A EEE E EE 4 3 4 2 2 PE CUBS BODY ie E E EE ouecdejneteeuenneneene 4 5 4 3 ORACLE FLEXCUBE NOTIFICATION 0 0 cccccccccecccecessessesececececsessnaececececsesseaecesececeeseaaeeeeeceeeessasaeseeees 4 6 4 3 1 FCUBS NOTIFICATION HEADER mirino E E NE EN ANS 4 7 1 1 ORACLE 5 FLEXML ADAPTER MESSAGE
99. age arrives on the queue it is picked up for processing 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 Gateway 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 Distribu
100. age is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CheckBookDelete Res PK This is the response message which is sent back to the external system when cheque book details for a customer account are 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 cheque book record in the Oracle FLEXCUBE data store 6 2 2 6 CheckDetailsQuery This is the operation code for querying the details of a cheque leaf in Oracle FLEXCUBE It involves the following messages e CheckDetailsQuery Req Full This is the request message to query on cheque leaf details in Oracle FLEXCUBE UBS An external system which intends to query 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 CheckDetailsQuery Req lO This is the request message to query on cheque leaf details in Oracle FLEXCUBE UBS An external system which intends to query 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 e CheckDetailsQuery Res Full This is the response message which is sent back to the external system when chequ
101. aintenance An external system which intends to query CG product maintenance 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 QueryCGProductMaint Req lO This is the request message to query a CG product maintenance An external system which intends to query CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryCGProductMaint Res Full This is the response message which is sent back to the external system when a CG product maintenance is queried 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 QueryCGProductMaint Res PK This is the response message which is sent back to the external system when a CG product maintenance is queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store CreateChkProtContract This is the operation code to create a cheque protest transaction It involves the following messages 6 2 6 12 e CreateChkProtContract Req Full This is the request message to create a cheque protest tra
102. al 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 3 4 ORACLE 3 2 1 External System Functions Detailed External System Description Function Action Service Name Operation Code Input By Authorized By Modification Authorized Date Time Date Time Number Open In the above screen you need to specify the following details 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 GWSEXFUN in the field at the top right corner of the Appl
103. al system when a collection service agreement is done 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 84 ORACLE 6 2 15 3 CloseCollAgreement This is the operation code to close coll agreement It involves the following messages 6 2 15 4 CloseCollAgreement Req Full This is the request message to close a collection service agreement An external system which intends to close a collection service agreement 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 CloseCollAgreement Req lO This is the request message to close a collection service agreement An external system which intends to close a collection service agreement has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CloseCollAgreement Res Full This is the response message which is sent back to the external system when a collection service agreement is done 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 CloseCollAgreement Res PK This is the respo
104. al system which intends to modify CG product maintenance 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 ModifyCGProductMaint Req lO This is the request message to modify a CG product maintenance An external system which intends to modify CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ModifyCGProductMaint Res Full This is the response message which is sent back to the external system when a CG product maintenance is modified The format of the 6 31 ORACLE 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 ModifyCGProductMaint Res PK This is the response message which is sent back to the external system when a CG product maintenance is modified The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 8 CloseCGProductMaint This is the operation code to close a CG product maintenance It involves the following messages e CloseCGProductMaint Req Full This is the request message to close a CG product maintenance
105. alled Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CreateDisbursementDetails Res PK This is the response message which is sent back to the external system when disbursement details are maintained 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 16 12 QueryDisbursement This operation is used to query the complete loan disbursement Details It involves the following messages e QueryDisbursementDetails Req Full This is the request message query the disbursement details An external system which intends to query the disbursement details 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 QueryDisbursementDetails Req lO This is the request message to query the disbursement details An external system which intends to query the disbursement details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save e QueryDisbursementDetails Res Full This is the response message which is sent back to the external system when disbursement details are queried
106. alled Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen SaveVami Res PK This is the response message which is sent back to the external system when value dated amendment details are maintained The format of the message 6 90 ORACLE 6 2 16 9 is called Primary Key response which includes only the primary key fields of the cheque book record in the Oracle FLEXCUBE data store QueryProduct This operation is used to query the complete details of the Product It involves the following messages 6 2 16 10 QueryProduct Req Full This is the request message to query details of a product An external system which intends to query product details 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 QueryProduct Req lO This is the request message to query details of a product An external system which intends to query product details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryProduct Res Full This is the response message which is sent back to the external system when product details are maintained The format of the message is called Full screen re
107. ateDocException Req Full This is the request message to create a new clearing retention exception maintenance An external system which intends to create new clearing retention exception maintenance 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 CreateDocException Req lO This is the request message to create a new clearing retention exception maintenance An external system which intends to create new clearing retention exception maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CreateDocException Res Full This is the response message which is sent back to the external system when new clearing retention exception is created The format of the 6 34 ORACLE 6 2 6 15 message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CreateDocException Res PK This is the response message which is sent back to the external system when new clearing retention exception is created The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store ModifyDocExce
108. ation The following snapshot shows a sample FCUBS_BODY of QUERYCUSTACC operation CustAccount Query lO Type Cust Account l0 se sins a cn ns Ll FCUBS_BODY will contain additional nodes for error response and warning response A diagrammatic representation of the Error response is as shown below ERRORType FCUBS_ERROR_RESP EH H ERROR 1 00 ERRORDETAILSType FECODE mo l ml 4 2 2 1 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 4 5 ORACLE 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 4 2 2 2 FCUBS WARNING RESP 4 3 The warning response message will be sent when overrides are raised in a transaction The Warning response will have another tag WARNING within it WARNING This node will have tags for warning code 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
109. ay fields as in the corresponding Oracle FLEXCUBE screen CBDDSMNT_ EXECUTEQUERY Res PK This is the response message which is sent back to the external system when contract is created 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 CBDDSMNT_ MODIFY This is the operation code is to modify the document status record It involves the following messages 6 2 17 29 CBDDSMNT_MODIFY Req Full This is the request message to modify the document status record An external system which intends to save payment details 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 CBDDSMNT_MODIFY Req lO This is the request message to modify the document status record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDDSMNT_MODIFY Res Full This is the response message which is sent back to the external system when the document status record is modified The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the correspon
110. back to the external system when the details for reversing stop payments are successfully authorised in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the stop payments reversal record in the Oracle FLEXCUBE data store CloseStopPaymentsReversal This is the operation code for closing the details for reversing stop payments for an individual cheque in Oracle FLEXCUBE It involves the following messages e CloseStopPaymentsReversal Req Full This is the request message to close the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to close the details for reversing stop payments 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 CloseStopPaymentsReversal Req lO This is the request message to close the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to close the details for reversing stop payments 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 the details for reversing stop payments CloseStopPaymentsReversal Res Full This is the response message which is sent back to the external syst
111. be sent back to the external system when a clearing service point 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 clearing service point record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e ClgServicePoint Modify Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to modify a clearing service point fails due to any functional error 6 2 6 21 CloseClgServicePoint This is the operation code for closing a clearing service point account in Oracle FLEXCUBE It involves the following messages e CloseClgServicePoint Close Req This is the request message to close a clearing service point account in Oracle FLEXCUBE UBS An external system which intends to close the clearing service point 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 clearing service point e CloseClgServicePoint Close Res Full This is the response message which will be sent back to the external system when a clearing service point is successfully closed in Oracle FLEXCUBE UBS The format of the message is called Full screen response will 6 37 ORACLE inc
112. ch 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 e 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 e 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 e ModifyMt101 Res Full 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 Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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 fo
113. ch is sent back to the external system when an LD payment simulation is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of the LD payment simulation in the Oracle FLEXCUBE data store 6 2 5 FCUBSCustomerService Customer related operations are logically grouped under a service called FCUBSCustomerService Oracle FLEXCUBE supports the following operations under this service 6 21 ORACLE CreateCustomer ModifyCustomer QueryCustomer CloseCustomer ReopenCustomer AccountStructureNew AccountStructureModify AccountStructureQuery AmountBlocksNew AmountBlocksModify AmountBlocksQuery AmountBlocksClose 6 2 5 1 CreateCustomer This is the operation code for creating a new customer in Oracle FLEXCUBE It involves the following messages Cust Static Create Req This is the request message to create a new customer in Oracle FLEXCUBE UBS An external system which intends to create a new customer 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 Cust Static Create Req Full This is the request message to create a new customer in Oracle FLEXCUBE UBS An external system which intends to create a new customer has to send the request in the format specified The format of the message is called Full scre
114. changed The Message Pattern is of the following types gt FS Full Screen This indicates that the payload will contain all the elements on the corresponding Oracle FLEXCUBE screen gt 10 Input Only This indicates that the payload will contain the only input elements on the corresponding Oracle FLEXCUBE screen gt PK Primary Key This indicates that the payload will contain only the Primary Key elements of the corresponding Oracle FLEXCUBE screen lt MESSAGE_EXCHNAGE_PATTERNs is a combination of message patterns The lt MESSAGE_EXCHNAGE_PATTERN3 gt available in FLEXCUBE is shown below e FSFS Full Screen Request and Full Screen Response e OPK Input Only Request and Primary Key Response e OFS Input Only Request and Full Screen Response Non Query Formats Example Consider the Operation CREATECUSTACC The root node of messages under this operation will be as under e CREATECUSTACC_FSFS_REQ CREATECUSTACC _FSFS_REQ e CREATECUSTACC_FSFS_RES 4 1 ORACLE FCUBS_HEADER CREATECUSTACC _FSFS_RES e CREATECUSTACC_IOPK_REQ CREATECUSTACC _IOPK_REO gt e CREATECUSTACC_IOPK_RES CREATECUSTACC _IOPK_RES Query Formats Example Consider the Operation QUERYCUSTACC The root node of messages under this operation will be as under e QUERYCUSTACC_IOFS_REQ QUERYCUSTACC IOFS_REO e QUERYCUSTACC_IOFS_RES FCUBS_HEADER QUERYCUSTACC _IOFS_RES 4 2 Oracle FL
115. cified 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 QueryDCMaster Req lO This is the request message to query card details An external system which intends to query card details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e QueryDCMaster Res Full This is the response message which is sent back to the external system when card details are queried 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 QueryDCMaster Res PK This is the response message which is sent back to the external system when card details are queried The format of the message is called 6 55 ORACLE Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 8 18 NewCExtService This is the operation code for creating an External Service in Oracle FLEXCUBE It involves the following messages e CExtService New Req This is the request message to create a new external service in Oracle FLEXCUBE UBS An external system which intends to create a new external service has to send the request in the specified format The format of the
116. ckTax QueryCheckTax CreateCheckTax This is the operation code to create Check Tax Parameter It involves the following messages 6 2 12 2 CreateCheckTax Req Full MSG This is the request message to create Check Tax Parameter An external system which intends to create Check Tax Parameter 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 CreateCheckTax Req lO MSG This is the request message to create Check Tax Parameter An external system which intends to create Check Tax Parameter has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CreateCheckTax Res Full MSG This is the response message which is sent back to the external system when Check Tax Parameter is done 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 CreateCheckTax Res PK MSG This is the response message which is sent back to the external system when Check Tax Parameter is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ModifyCheckTax This is the operation code to mo
117. cle FLEXCUBE UBS An external system which intends to create city code maintenance 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 Embargo maintenance CreateCityCode Res Full This is the response message which will be sent back to the external system when city code maintenance is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CreateCityCode Res PK This is the response message which will be sent back to the external system when city code maintenance 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 an city code maintenance record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key CreateCityCode Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create city code maintenance fails due to any functional error ModifyCityCode This is the operation code for modifying city code maintenance in Oracle FLEXCUBE It involves the following messages ModifyCityCode Reg
118. creen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen NewCBrandMaintenance Res PK This is the response message which will be sent back to the external system when a brand 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 card record in the Oracle FLEXCUBE data store NewCBrandMaintenance Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create a brand fails due to any functional error ModCBrandMaint This is the operation code to Modify brand details It involves the following messages e ModifyCBrandMaintenance Req Full This is the request message to modify brand details An external system which intends to modify brand detailshas to send the request in the format specified The format of the message is called Full screen which includes 6 58 ORACLE 6 2 8 26 all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen ModifyCBrandMaintenance Req lO This is the request message to modify brand details An external system which intends to modify brand details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifyCBrandMain
119. d 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 ModifyLoan accountDetails Res PK This is the response message which is sent back to the external system when loan account details are maintained 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 CreateAccount This is the operation code is to save loan account details It involves the following messages SaveLoan accountDetails Req Full This is the request message to save loan account details An external system which intends to save loan account details 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 6 89 ORACLE 6 2 16 7 SaveLoan accountDetails Req lO This is the request message to save loan account details An external system which intends to save loan account details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save SaveLoan accountDetails Res Full This is the response message which is sent back to the external system when loan account details are mainta
120. d 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 QueryPmtMode Res PK MSG This is the response message which is sent back to the external system when a payment mode is queried The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store 6 2 11 17 PmtAuthorize This is the operation code to authorize a payment It involves the following messages e AuthorizePmt Reqg Full MSG This is the request message to authorize a payment An external system which intends to authorize a payment 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 6 74 ORACLE 6 2 11 18 AuthorizePmt Req lO MSG This is the request message to authorize a payment An external system which intends to authorize a payment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to authorize AuthorizePmt Res Full MSG This is the response message which is sent back to the external system when a payment is authorized The format of the message is called Full screen response which includes al
121. d 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 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 Outgoing Message Browser Message Reference External System Message Id Correlation Id Message Status Service Name Operation Code Branch FLEXCUBE Reference User Id Their User Id Server Date Stamp Response Queue Message Id Branch Date Queue Name Related Message Reference Repair Reason Text view xme view Gateway Messaging View L JI In the Outgoing Message Browser screen you can view the details of the messages sent to the external systems You can also view the messages in the XML format or the Text format 3 17 ORACLE Click Text View button to view the response message in text format as shown below Text View E Gateway Browser Window Microsoft Internet Explorer lt FCUBS_ENVELOPE gt lt FCUBS_HEADER gt lt SOURCE gt FLEXCUBE lt SOURCE gt lt MSGID gt 9062070000001652 lt MSGID gt lt CORRELID gt lt CORRELID gt lt USERID gt SAURAV1 lt USERID g
122. d is successfully re opened in Oracle FLEXCUBE The format of the message is called Primary Key response which includes only the primary key fields of the record 6 13 ORACLE 6 2 2 18 CreateTDSim This is the operation code for creating TD simulation in Oracle FLEXCUBE It involves the following messages e CreateTDSim Reqg 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 e CreateTDSim Res Full This is the response message which is sent back to the external system when a TD simulation is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CreateTDSim Res PK This is the response message which is sent back to the external system when a TD
123. dicates the error response generated by Oracle FLEXCUBE when the processing of request to create a new customer account CustAcc Static Create Req fails due to any functional error DeleteCustAcc This is the operation code for Deleting a new Savings Current account in Oracle FLEXCUBE It involves the following messages CustAcc Static Delete Req This is the request message to Delete a new customer account in Oracle FLEXCUBE UBS An external system which intends to Delete a customer 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 Deleting a customer CustAcc Static Delete Req Full This is the request message to Delete a customer account in Oracle FLEXCUBE UBS An external system which intends to Delete a 6 15 ORACLE 6 2 2 24 customer account has to send the request in the format specified The format of the message is called Full screen which is includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CustAcc Static Delete Res Full This is the response message which will be sent back to the external system when a customer account is successfully deleted The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen If the requ
124. dify Check Tax Parameter It involves the following messages 6 2 12 3 ModifyCheckTax Req Full MSG This is the request message to modify Check Tax Parameter An external system which intends to modify Check Tax Parameter 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 ModifyCheckTax Req IO MSG This is the request message to modify Check Tax Parameter An external system which intends to modify Check Tax Parameter has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifyCheckTax Res Full MSG This is the response message which is sent back to the external system when Check Tax Parameter is done 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 ModifyCheckTax Res PK MSG This is the response message which is sent back to the external system when Check Tax Parameter is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store QueryCheckTax This is the operation code to query Check Tax Parameter It involves the following messages 6 78 ORACLE
125. ding Oracle FLEXCUBE screen AmendPmtExtention Res PK MSG This is the response message which is sent back to the external system when a payment extension is amended The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store QueryPmtExt This is the operation code to query a payment extention It involves the following messages QueryPmtExtention Req Full MSG This is the request message to query a payment extension An external system which intends to query a payment extension 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 QueryPmtExtention Req IO MSG This is the request message to query a payment extension An external system which intends to query a payment extension has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryPmtExtention Res Full MSG This is the response message which is sent back to the external system when a payment extension is queried 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 QueryPmtExtention Res PK MSG This is the
126. ding Oracle FLEXCUBE screen CBDDSMNT_MODIFY Res PK This is the response message which is sent back to the external system when the document status record is modified 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 CBDLOMNT_ NEW This is the operation code is to create CB location code It involves the following messages 6 105 ORACLE 6 2 17 30 CBDLOMNT_ NEW Regq Full This is the request message to create CB location code An external system which intends to save payment details 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 CBDLOMNT_ NEW Req IO This is the request message to create CB location code An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDLOMNT_ NEW Res Full This is the response message which is sent back to the external system when CB location code is created 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 CBDLOMNT_ NEW
127. e CBDCCMNT_EXECUTEQUERY Res Full This is the response message which is sent back to the external system when collection center record is queried 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 CBDCCMNT_EXECUTEQUERY Res PK This is the response message which is sent back to the external system when collection center record is queried 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 CBDCCMNT_ MODIFY This is the operation code is to modify collection center record It involves the following messages e CBDCCMNT_MODIFY Req Full This is the request message to modify collection center record An external system which intends to save payment details 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 CBDCCMNT_MODIFY Req lO This is the request message to to modify collection center record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDCCMNT_MODIFY R
128. e Authorization Status A Authorized U Unauthorized Record Status C Closed O Open Ea 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 3 21 ORACLE 3 8 3 8 1 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 Enroute Detailed Branch Code Notification Code az Description Description E Destination Name Input By Authorized By Modification Authorized ei Date Time Date Time Number 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 notificati
129. e CB contract It involves the following messages e CBDTRONL_NEW Reg Full This is the request message to create CB contract An external system which intends to save payment details 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 CBDTRONL_NEW Req lIO This is the request message to create CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDTRONL_NEW Res Full This is the response message which is sent back to the external system when contract is created 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 CBDTRONL_NEW Res PK This is the response message which is sent back to the external system when contract is created The format of the message is called Primary 6 94 ORACLE 6 2 17 2 Key response which includes only the primary key fields of the cheque book record in the Oracle FLEXCUBE data store CBDTRONL_ EXECUTEQUERY This is the operation code is to query CB contract It involves the following messages 6 2 17 3 CBDTRONL_EXECUTEQUE
130. e leaf details are 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 e CheckDetailsQuery Res PK This is the response message which is sent back to the external system when cheque leaf details are 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 leaf record in the Oracle FLEXCUBE data store 6 8 ORACLE 6 2 2 7 CreateStopPaymentsReversal This is the operation code for creating the details for reversing stop payments for an individual cheque in Oracle FLEXCUBE It involves the following messages CreateStopPaymentsReversal Req Full This is the request message to create the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to create the details for reversing stop payments 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 CreateStopPaymentsReversal Req IO This is the request message to create the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to create the details for reversing stop payments has t
131. e maintained 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 DeletePaymentDetails Res PK This is the response message which is sent back to the external system when payment details are maintained The format of the message is 6 88 ORACLE 6 2 16 4 called Primary Key response which includes only the primary key fields of the cheque book record in the Oracle FLEXCUBE data store ReversePayment This is the operation code is to reverse payment details It involves the following messages 6 2 16 5 ReversePaymentDetails Req Full This is the request message to reverse payment details An external system which intends to reverse payment details 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 ReversePaymentDetails Req IO This is the request message to reverse payment details An external system which intends to reverse payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to reverse ReversePaymentDetails Res Full This is the response message which is sent back to the external system when payment details are maintain
132. e 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 AmountBlocksNew Res PK This is the response message which is sent back to the external system when a new 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 record in the Oracle FLEXCUBE data store 6 2 5 10 AmountBlocksModify This is the operation code for modifying an existing amount block in Oracle FLEXCUBE It involves the following messages 6 26 ORACLE 6 2 5 11 AmountBlocksModify Req Full This is the request message to modify an existing amount block in Oracle FLEXCUBE UBS An external system which intends to modify an existing 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 AmountBlocksModify Req lO This is the request message to modify an existing amount block in Oracle FLEXCUBE UBS An external system which intends to modify an existing 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 an amount block AmountBlocks
133. e to delete card details An external system which intends to delete card details 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 DeleteDCMaster Req lO This is the request message to delete card details An external system which intends to delete card details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query DeleteDCMaster Res Full This is the response message which is sent back to the external system when card details are deleted 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 DeleteDCMaster Res PK This is the response message which is sent back to the external system when card details are deleted The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store QueryDCMaster This is the operation code to query card details It involves the following messages e QueryDCMaster Req Full This is the request message to query a card details An external system which intends to query card details has to send the request in the format spe
134. earch 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 3 13 ORACLE 3 5 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 screen by typing GWSPBROW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Duplicate Message Browser Summary Message Reference Branch External System a Message Id Correlation Id Request Queue Message Id Service Name a Operation Code User Id H Their User Id Server Date Stamp Status eB lB Media Queue Name Q Search Advanced Search Reset Records per page Iq 4 4 of 1 L oO Message Reference Branch External System Message Id Correlation
135. ection beneficiary An external system which intends to close a payment and collection beneficiary has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ClosePCBeneficiary Res Full MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done 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 ClosePCBeneficiary Res PK MSG This is the response message which is sent back to the external system when a payment and collection beneficiary is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ReopenPCBeneficiary This is the operation code to reopen a payment and collection beneficiary It involves the following messages ReopenPBeneficiary Req Full MSG This is the request message to reopen a payment and collection beneficiary An external system which intends to reopen a payment and collection beneficiary 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 ReopenPCBeneficiary Req IO MSG
136. ed 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 ReversePaymentDetails Res PK This is the response message which is sent back to the external system when payment details are maintained 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 ModifyAccount This is the operation code is to modify loan account details It involves the following messages 6 2 16 6 ModifyLoan accountDetails Req Full This is the request message to modify loan account details An external system which intends to modify loan account details 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 ModifyLoan accountDetails Req lO This is the request message to modify loan account details An external system which intends to modify loan account details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to modify ModifyLoan accountDetails Res Full This is the response message which is sent back to the external system when loan account details are maintaine
137. elds as in the corresponding Oracle FLEXCUBE screen CustAcc Static Modify Res PK MSG This is the response message which will be sent back to the external system when a customer account is successfully Modified in Oracle 6 16 ORACLE FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields 6 2 2 26 AuthorizeCustAcc This is the operation code to authorize a customer account It involves the following messages e CustAcc Static Authorize Req Full MSG This is the request message to Authorize a customer account in Oracle FLEXCUBE UBS An external system which intends to authorize a customer account has to send the request in the specified format 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 CustAcc Static Authorize Req MSG This is the request message to Authorize a customer account in Oracle FLEXCUBE UBS An external system which intends to authorize a customer account has to send the request in the specified format The format of the message is called Input only which has only those fields which are authorized e CustAcc Static Authorize Res Full MSG This is the response message which will be sent back to the external system when a customer account is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Fu
138. elds and the display fields as in the corresponding Oracle FLEXCUBE screen e 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 6 4 ORACLE includes only the primary key fields of the FT contract in the Oracle FLEXCUBE data store 6 2 1 8 QueryFTContract This is the operation code for querying FT contract in Oracle FLEXCUBE It involves the following messages e QueryFTcontract Reqg 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 e 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 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 e 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 messa
139. em when the details for reversing stop payments are 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 CloseStopPaymentsReversal Res PK This is the response message which is sent back to the external system when the details for reversing stop payments are 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 stop payments reversal record in the Oracle FLEXCUBE data store 6 10 ORACLE 6 2 2 11 ReopenStopPaymentsReversal This is the operation code for reopening the details for reversing stop payments for an individual cheque in Oracle FLEXCUBE It involves the following messages 6 2 2 12 ReopenStopPaymentsReversal Req Full This is the request message to reopen the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to reopen the details for reversing stop payments 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 ReopenStopPaymentsReversal Req lO This is the request message to reopen the details for reversing stop payments in Oracle FLEXCUBE UBS
140. ement An external system which intends to modify a payment agreement has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifyPmtAgreement Res Full MSG This is the response message which is sent back to the external system when a payment agreement is done 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 ModifyPmtAgreement Res PK MSG This is the response message which is sent back to the external system when a payment agreement is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ClosePmtAgreement This is the operation code to close a payment agreement It involves the following messages ClosePmtAgreement Req Full MSG This is the request message to close a payment agreement An external system which intends to close a payment agreement 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 6 72 ORACLE 6 2 11 13 ClosePmtAgreement Req O MSG This is the request message to close a payment agreement An external system which intends to cl
141. en e ModifylnterestAdjustment Res PK MSG This is the response message which is sent back to the external system when interest adjustment is modified 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 13 3 CloselnterestAdjustment This is the operation code to close interest adjustment for branch account product and next liquidation date combination It involves the following messages e CloselnterestAdjustment Reg Full MSG This is the request message to close interest adjustment An external system which intends to close interest adjustment 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 CloselnterestAdjustment Reg IO MSG This is the request message to close interest adjustment An external system which intends to close interest adjustment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CloselnterestAdjustment Res Full MSG This is the response message which is sent back to the external system when interest adjustment is closed The format of the message is called Full screen response which includes all the fields input fields and
142. en which is includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen Cust Static Create Res Full This is the response message which will be sent back to the external system when a new customer is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen Note If the request message is in full screen format then response will be in this format only Cust Static Create Res PK This is the response message which will be sent back to the external system when a new customer 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 customer record in the Oracle FLEXCUBE data store Note This response will be sent if the resoonse Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key Cust Static Create Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request for creating a new customer Cust Static Create Req fails due to any functional error 6 2 5 2 ModifyCustomer This is the operation code for modifying the details of an existing customer in Oracle FLEXCUBE It involves the following messages Cust Static Modi
143. en query for CB location code is queried 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 CBDRQMNT_NEW This is the operation code is to create extension request for CB contract It involves the following messages 6 2 17 34 CBDRQMNT_ NEW Reg Full This is the request message to create extension request for CB contract An external system which intends to save payment details 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 CBDRQMNT_ NEW Req IO This is the request message to create extension request for CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDRQMNT_ NEW Res Full This is the response message which is sent back to the external system when CB contract extension request is created 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 CBDRQMNT_ NEW Res PK This is the response message which is sent back to the external system when CB contr
144. eopenDocException Res PK This is the response message which is sent back to the external system when clearing retention exception is reopened The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 19 CreateClgServicePoint This is the operation code for creating a clearing service point account in Oracle FLEXCUBE It involves the following messages e ClgServicePoint Create Req This is the request message to create a clearing service point account in Oracle FLEXCUBE UBS An external system which intends to create the clearing service point 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 clearing service point 6 36 ORACLE e ClgServicePoint Create Res Full This is the response message which will be sent back to the external system when a clearing service point is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e ClgServicePoint Create Res PK This is the response message which will be sent back to the external system when a clearing service point is successfully created in Oracle FLEXCUBE UBS The format of the message is called Primary Key resp
145. ernal system when interest adjustment is queried 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 QueryInterestAdjustment Res PK MSG This is the response message which is sent back to the external system when interest adjustment is queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store AuthorizelnterestAdjustment This is the operation code to query interest adjustment for branch account product and next liquidation date combination It involves the following messages AuthorizelnterestAdjustment Req Full MSG This is the request message to authorize interest adjustment An external system which intends to authorize interest adjustment 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 AuthorizelnterestAdjustment Reqg lIO MSG This is the request message to authorize interest adjustment An external system which intends to authorize interest adjustment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query AuthorizelnterestAdjustment
146. es Full This is the response message which is sent back to the external system when collection type record is queried 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 CBDCLMNT_EXECUTEQUERY Res PK This is the response message which is sent back to the external system when collection type record is queried 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 CBDCLMNT MODIFY This is the operation code is to modify collection type record It involves the following messages e CBDCLMNT_MODIFY Req Full This is the request message to modify collection type record An external system which intends to save payment details has to send the request 6 101 ORACLE 6 2 17 20 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 CBDCLMNT_MODIFY Req lO This is the request message to modify collection type record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDCLMNT_MODIFY Res Full This i
147. es Full This is the response message which is sent back to the external system when collection center record is modified 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 100 ORACLE 6 2 17 17 CBDCCMNT_MODIFY Res PK This is the response message which is sent back to the external system when collection center record is modified 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 CBDCLMNT NEW This is the operation code is to create a new collection type record It involves the following messages 6 2 17 18 CBDCLMNT_NEW Reg Full This is the request message to create a new collection type record An external system which intends to save payment details 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 CBDCLMNT_NEW Req lO This is the request message to create a new collection type record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDCLMNT_NEW R
148. es Full This is the response message which is sent back to the external system when a new collection type record is created 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 CBDCLMNT_NEW Res PK This is the response message which is sent back to the external system when a new collection type record is created 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 CBDCLMNT EXECUTEQUERY This is the operation code is to query for collection type record It involves the following messages 6 2 17 19 CBDCLMNT_EXECUTEQUERY Regq Full This is the request message to query for collection type record An external system which intends to save payment details 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 CBDCLMNT_EXECUTEQUERY Req lO This is the request message to query for collection type record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDCLMNT_EXECUTEQUERY R
149. es the following messages e 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 e CheckBookModify Req lO 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 e 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 6 6 ORACLE fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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 CheckBo
150. esdencetdstsasheesuensomesucdsbeesesesendsovasbeeseoncvbesusiedeeiuee 6 18 6 2 5 FRCUBSCUuStOMErS r VIC cccccccccccccccccccccecesecccececececececececececececececececececececececececececececeeececececececececececeseds 6 21 6 2 6 PCUBSCGS CHV 1 C6 visivicsisicecsitesccdstcasesectndssndsveeseeeseeesuedsbeesdencetdstuasdoeseoecodessedsteesesesdndsovasveesooesetesusiedeedess 6 28 6 2 7 PF CUBSCOPeS CrviGes iicssiceceitescndeiitscvecctessuasteesscwcotesaedsteasooucetds code deesooncvte sands beasoousetdsovasbecseswcedesusieieetede 6 42 6 2 8 FP CUBSS TS GRICE vcscdcsicasieecstesiedsteasenecondssndsbeeseensotesuedsbeasdencetdstwasboesececodesaudsbeesesesendsovdsbeesooesobesusdedeeeuee 6 48 6 2 9 FO UBSPARORYS rviCe prenesenie eE AE EEEE ANAA ER ETE EAE a S Ro OREORE 6 64 6 2410 PCUBS PDS Cri Ce mereen eii nEn EEEE EE A E EEA EEE EEN AE 6 64 6 2 11 P CUBS PCS CrV1CO Creer a a a E A aa E eA aaa E a EE N EE Aa eE AS 6 67 O212 FKCUBSCASETVICE senene e A A E EE EEA NEEE 6 78 62413 PP CUBSICS rVICE is csscnccactiandeedscancdactaaitens a a a e a a e 6 79 6214 FCUBSIES eVI Enseres Ea E A E A ERA EE E E EAE KEES 6 82 62 13 BPCUBSUPSCrVICE sscccicaciondencscandtactaamenacsieasacsesbavevedseatods tbavessensatecdesbundvacsoanseaedioetesassoasccnestorsvadebeseeeie 6 83 62 16 POCUBS CESCrVICE cscccicsxicncustacacccactieatenacneatecacsbuenacsiseneadedisatensdveatecaesdenesadaoanscacsioetesesuoetocdesbuesecebenedecton 6 87 62 417 PFOCUBS CBSOVICE oened a a a E a E E a EE 6 93
151. esponse message which is sent back to the external system when query for CB location code is queried 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 CBDLOMNT_ MODIFY This is the operation code is to modify CB location code It involves the following messages CBDLOMNT_ MODIFY Req Full This is the request message to modify CB location code An external system which intends to save payment details 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 CBDLOMNT_ MODIFY Req lO This is the request message to modify CB location code An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDLOMNT_ MODIFY Res Full This is the response message which is sent back to the external system when CB location code is modified The format of the message is called 6 106 ORACLE 6 2 17 32 Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CBDLOMNT_ MODIFY Res PK This is the response message which is sent back to the
152. essage to modify beneficiary details An external system which intends to modify beneficiary details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ModifyBeneficiaryMaintenance Res Full This is the response message which is sent back to the external system when beneficiary details are modified 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 ModifyBeneficiaryMaintenance Res PK This is the response message which is sent back to the external system when beneficiary details are modified The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 11 7 BeneficiaryMaintenanceCls This is the operation code to close beneficiary details It involves the following messages e CloseBeneficiaryMaintenance Req Full This is the request message to close beneficiary details An external system which intends to close beneficiary details 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 6 70 ORACLE 6 2 11 8 e CloseBeneficiaryMaintenance Req lO
153. est message is in full screen format then response will be in this format only CustAcc Static Delete Res PK This is the response message which will be sent back to the external system when a customer account is successfully deleted The format of the message is called Primary Key response which includes only the primary key fields of the customer account record in the Oracle FLEXCUBE data store This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key CustAcc Static Delete Req Flit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to Delete a customer account CustAcc Static Delete Req fails due to any functional error QueryCustAcc This is the operation code for querying a Savings Current account in Oracle FLEXCUBE It involves the following messages 6 2 2 25 e CustAcc Static Query Req This is the request message to query on a customer account in Oracle FLEXCUBE UBS An external system which intends to query 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 CustAcc Static Query Res This is the response message which will be sent back to the external system when a customer account is successfully queried upon in Oracle FLEXCUBE UBS The format of the message includes all the field
154. external system which intends to create CG product maintenance 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 CreateCGProductMaint Req lO This is the request message to create a CG product maintenance An external system which intends to create CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CreateCGProductMaint Res Full This is the response message which is sent back to the external system when a CG product maintenance is created 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 CreateCGProductMaint Res PK This is the response message which is sent back to the external system when a CG product maintenance is created The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 7 ModifyCGProductMaint This is the operation code to modify a CG product maintenance It involves the following messages e ModifyCGProductMaint Req Full This is the request message to modify a CG product maintenance An extern
155. f the account structure in the Oracle FLEXCUBE data store 6 2 5 7 AccountStructureModify This is the operation code for modifying account structure in Oracle FLEXCUBE It involves the following messages e 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 e 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 fields that are actually required for modifying account structure e 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 e AccountStructureModify Res PK This is the response message which is sent back to the external system when an account st
156. ficiaryMaintenance Res Full This is the response message which will be sent back to the external system when a beneficiary is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e NewBeneficiaryMaintenance Res PK This is the response message which will be sent back to the external system when a beneficiary 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 card record in the Oracle FLEXCUBE data store e NewBeneficiaryMaintenance FIt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create a beneficiary fails due to any functional error 6 2 11 6 BeneficiaryMaintenanceMod This is the operation code to Modify beneficiary details It involves the following messages e ModifyBeneficiaryMaintenance Req Full This is the request message to modify beneficiary details An external system which intends to modify beneficiary detailshas 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 ModifyBeneficiaryMaintenance Req lO This is the request m
157. fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e CreatelLSweep Reqg lO MSG This is the request message to create account structure for sweep for sweep An external system which intends to create account structure for sweep has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CreatelLSweep Res Full MSG This is the response message which is sent back to the external system when account structure for sweep is done 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 82 ORACLE 6 2 14 2 CreatelLSweep Res PK MSG This is the response message which is sent back to the external system when account structure for sweep is done 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 ModifyiLSweep This is the operation code to modify account structure for sweep for branch account product and next liquidation date combination It involves the following messages 6 2 14 3 ModifylLSweep Req Full MSG This is the request message to modify account structure for sweep An external system which intends to modify account structure for sweep has to send the
158. format specified The format of the message is called Input only which has only those fields that can be used to save CBDAGMON_EXECUTEQUERY Res Full This is the response message which is sent back to the external system when CB agreement is queried 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 CBDAGMON_EXECUTEQUERY Res PK This is the response message which is sent back to the external system when CB agreement is queried 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 CBDAGMON MODIFY This is the operation code is to modify CB agreement It involves the following messages 6 2 17 14 CBDAGMON_MODIFVY Req Full This is the request message to modify CB agreement An external system which intends to save payment details 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 CBDAGMON_MODIFY Req lO This is the request message to modify CB agreement An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only
159. fy Reg This is the request message to modify the details of a customer in Oracle FLEXCUBE UBS An external system which intends to modify the customer 6 22 ORACLE details 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 modified for a customer e Cust Static Modify Res Full This is the response message which will be sent back to the external system when the details of a customer are modified successfully in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e Cust Static Modify Res PK This is the response message which will be sent back to the external system when the details of a customer are modified successfully 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 in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e Cust Static Modify Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to modify an existing customer Cust Static Modify Req fails due to any functional error 6 2 5 3 QueryCustomer This is the opera
160. fyStopPaymentsParameter Req Full This is the request message sent by the external system for modification of a stop payment parameter record An external system which intends to modify a stop payment parameter 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 screen ModifyStopPaymentsParameter Req PK This is the request message sent by the external system for modification of a stop payment parameter record An external system which intends to modify the stop payment parameter record has to send the request in the format specified The format of the message is called Primary Key which includes only the primary key fields of the record 6 12 ORACLE 6 2 2 16 6 2 2 17 ModifyStopPaymentsParameter Res Full This is the response message which is sent back to the external system when a stop payment parameter record is successfully modified in Oracle FLEXCUBE The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen ModifyStopPaymentsParameter Res PK This is the response message which is sent back to the external system when a stop payment parameter record is successfully modified in Oracle FLEXCUBE The format of the message is called Primary Key respon
161. ge is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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 2 FCUBSAccService All account operations are logically grouped under a service called FCUBSAccService Oracle FLEXCUBE supports the following operations under this service e CheckBooKNew e CheckBookModify e CheckBookQuery e CheckBookAuthorise e CheckBookDelete e CheckDetailsQuery e CreateStopPaymentsReversal e ModifyStopPaymentsReversal e AuthoriseStopPaymentsReversal e CloseStopPaymentsReversal e ReopenStopPaymentsReversal e QueryStopPaymentsReversal e CreateStopPaymentsParameter e ModifyStopPaymentsParameter e CloseStopPaymentsParameter e ReopenStopPaymentsParameter e QueryStopPaymentsParameter e StopPaymentsNew 6 5 ORACLE CreateTDSim QueryGenAdvice QueryPreLiquid Querycustaccbal CreateCustAcc QueryCustAcc ModifyCustAcc AuthorizeCustAcc CloseCustAcc 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 t
162. ge to modify a cheque correspondence in Oracle FLEXCUBE UBS An external system which intends to modify the cheque correspondence 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 correspondence ModifyChequeCorrespondence Modify Res Full This is the response message which will be sent back to the external system when a cheque correspondence account is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen ChequeCorrespondence Query Res PkK This is the response message which will be sent back to the external system when a cheque correspondence 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 correspondence record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key ChequeCorrespondence Query Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to modify a cheque correspondence fails due to any functional error CreateExtendOrRelease This is the operation
163. h intends to delete account structure for sweep 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 DeletelLSweep Req lO MSG This is the request message to delete account structure for sweep An external system which intends to delete account structure for sweep has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query DeletelLSweep Res Full MSG This is the response message which is sent back to the external system when account structure for sweep is deleted 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 DeletelLSweep Res PK MSG This is the response message which is sent back to the external system when account structure for sweep is deleted 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 15 FCUBSUPService All the operations that can be performed on Utility Payments module are logically grouped under a service called FCUBSUPService Oracle FLEXCUBE supports the following operation codes under this service 6 83 ORAC
164. h is sent back to the external system when a payment extension is authorized The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ModifyFunding This is the operation code to modify a online funding It involves the following messages 6 2 11 22 ModifyPCFunding Req Full MSG This is the request message to modify an online funding An external system which intends to modify an online funding 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 ModifyPCFunding Req IO MSG This is the request message to modify an online funding An external system which intends to modify an online funding has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifyPCFunding Res Full MSG This is the response message which is sent back to the external system when an online funding is done 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 ModifyPCFunding Res PK MSG This is the response message which is sent back to the external system when an online funding is done The fo
165. h will be sent back to the external system when error code maintenance 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 correspondence record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key QueryCGRejErrCdMaint Query Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query a cheque correspondence fails due to any functional error CreateCollectionCheque This is the operation code to create a new collection cheque transaction It involves the following messages e CreateCollectionCheque Req Full This is the request message to create a new collection cheque transaction An external system which intends to create a collection cheque 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 e CreateCollectionCheque Req lO This is the request message to create a new collection cheque transaction An external system which intends to create a record has to send the request in the format specified The format of the message is called Input only which has onl
166. hat are discussed Add param HOST to header Send request to Change server state to S after g S aft Sync change state to A complet request J Process request build response Change server state to U Reject the Send request to Poss Log request message Send error Start gt synchronization additionally in a separate table Process request build response Update POSS log table Response Replay Complete All Add param requests POSS to header replaved Incomplete ane r incomplete i fi Replay Routine ie 7 2 5 ELCM Impact 7 3 7 3 1 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 Cancel FT Contract 7 3 ORACLE 7 3 2 7 3 3 7 3 4 7 3 5 7 3 6 7 3 7 7 3 8 e Create FT Contract FCUBSPC Service The operations that are supported under FCUBSFT services are e Create PC Contract e Create PC Maint e Close PC Contract e Create PC ClientAgg FCUBSSI Ser
167. he corresponding Oracle FLEXCUBE screen e QueryCBrandMaint Res PkK This is the response message which is sent back to the external system when brand details are queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store QueryTrnCost This is the operation code to query the transaction cost It involves the following message 6 60 ORACLE 6 2 8 31 ST QueryTransactionCostDisplay Req Full MSG This is the request message to query on transaction cost An external system which intends to query the transaction cost 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 ST QueryTransactionCostDisplay Res Full MSG This is the resoonse message which will be sent back to the external system when a transaction cost 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 CreateCityCode This is the operation code for creating city code maintenance in Oracle FLEXCUBE It involves the following messages 6 2 8 32 CreateCityCode Reg This is the request message to create city code maintenance in Ora
168. he details of an existing customer in Oracle FLEXCUBE It involves the following messages e Cust Static Close Req This is the request message to close the details of a customer in Oracle FLEXCUBE UBS An external system which intends to close the customer details 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 closed for a customer e Cust Static Close Res Full This is the response message which will be sent back to the external system when the details of a customer are closed successfully in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 23 ORACLE e Cust Static Close Res PK This is the response message which will be sent back to the external system when the details of a customer are closed successfully 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 in the Oracle FLEXCUBE data store e Cust Static Close Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to close an existing customer Cust Static Modify Req fails due to any functional error 6 2 5 5 ReopenCustomer This is the operation code for reopening the details
169. he error response generated by Oracle FLEXCUBE when the processing of request to modify a Term Deposit fails due to any functional error Create TDAcc This is the operation code for creating a Term Deposit account in Oracle FLEXCUBE It involves the following messages 6 2 10 3 TD Account Create Req This is the request message to create a Term Deposit TD account in Oracle FLEXCUBE UBS An external system which intends to create the 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 a TD TD Account Create Res Full This is the response message which will be sent back to the external system when a Term Deposit TD account is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen TD Account Create Res PK This is the response message which will be sent back to the external system when a Term Deposit 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 record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key TD Ro
170. he message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CBDDLMNT_ NEW Res PK This is the response message which is sent back to the external system when CB document location record is created 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 CBDDLMNT_EXECUTEQUERY This is the operation code is to query for CB document It involves the following messages e CBDDLMNT_EXECUTEQUERY Regq Full This is the request message to query for CB document An external system which intends to save payment details has to send the request in the format specified The format of the message is called Full screen which 6 103 ORACLE 6 2 17 25 includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CBDDLMNT_EXECUTEQUERY Req lO This is the request message to query for CB document An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDDLMNT_ EXECUTEQUERY Res Full This is the response message which is sent back to the external system when query for CB document is queried The format of the message is called
171. he message is called Primary Key response which includes only the primary key fields of the record ReopenStopPaymentsParameter ReopenStopPaymentsParameter Req Full This is the request message sent by the external system for re opening of a stop payment parameter record An external system which intends to re open a stop payment parameter 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 screen ReopenStopPaymentsParameter Req PK This is the request message sent by the external system for re opening of a stop payment parameter record An external system which intends to re open the stop payment parameter record has to send the request in the format specified The format of the message is called Primary Key which includes only the primary key fields of the record ReopenStopPaymentsParameter Res Full This is the response message which is sent back to the external system when a stop payment parameter record is successfully re opened 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 ReopenStopPaymentsParameter Res PK This is the response message which is sent back to the external system when a stop payment parameter recor
172. he 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 LDVamiCreateSim Req lO This is the request message to create LD VAMI simulation contract in Oracle FLEXCUBE UBS An external system which intends to create LD VAMI simulation contract has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for creating LD VAMI simulation e 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 e LDVamiQuerySim Req
173. hen new collection service agreement is done 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 AmendCollAgreement This is the operation code to amend coll agreement It involves the following messages AmendCollAgreement Req Full This is the request message to amend a collection service agreement An external system which intends to amend a collection service agreement 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 AmendeCollAgreement Req lO This is the request message to amend a collection service agreement An external system which intends to amend a collection service agreement has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query AmendeCollAgreement Res Full This is the response message which is sent back to the external system when a collection service agreement is done 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 AmendeCollAgreement Res PK This is the response message which is sent back to the extern
174. hich includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CBDDSMNT_ NEW Res PK This is the response message which is sent back to the external system when the document status record is created 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 CBDDSMNT_EXECUTEQUERY This is the operation code is to create CB contract It involves the following messages 6 2 17 28 CBDDSMNT_ EXECUTEQUERY Req Full This is the request message to create CB contract An external system which intends to save payment details 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 CBDDSMNT_ EXECUTEQUERY Req lO This is the request message to create CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDDSMNT_ EXECUTEQUERY Res Full This is the response message which is sent back to the external system when contract is created The format of the message is called Full screen response which includes all the fields input fields and the displ
175. his is the request message to close an External Service An external system which intends to close an External Service has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CloseCExtService Res Full This is the response message which is sent back to the external system when an External Service is closed 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 CloseCExtService Res PK This is the response message which is sent back to the external system when an External Service is closed The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store DeleteCExtService This is the operation code to delete an External Service It involves the following messages e DeleteCExtService Req Full This is the request message to delete an External Service An external system which intends to delete an External Service 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 DeleteCExtService Req lO This is the request message to delete an External Service An
176. his is the request message to create an Embargo transaction in Oracle FLEXCUBE UBS An external system which intends to create an Embargo 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 an Embargo transaction Embargo New Res Full This is the response message which will be sent back to the external system when an Embargo transaction is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen Embargo New Res PK This is the response message which will be sent back to the external system when an Embargo 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 an Embargo transaction record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key Embargo New Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create an Embargo transaction fails due to any functional error 6 2 7 2 EmbargoModify This is the operation code for modifying an Embargo transaction in Oracle
177. horizing an account class in Oracle FLEXCUBE It involves the following messages e AccClasMaint Auth Req This is the request message to authorize an account class in Oracle FLEXCUBE UBS An external system which intends to authorize an account 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 authorizing an account class e AccClasMaint Auth Res Full This is the response message which will be sent back to the external system when an account class is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e AccClasMaint Auth Res PK This is the response message which will be sent back to the external system when an account class 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 an account class record in the Oracle FLEXCUBE data store 6 50 ORACLE Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e AccClasMaint Auth Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to authorize an account class fails d
178. ication tool bar and clicking the adjoining arrow button 3 5 ORACLE External System Function Summary Authorization Status Record Status External System Function Action Q Search Advanced Search Reset Records per page Iq 414 of 4 PII Record Status C Closed O Open 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 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 3 6 ORACLE 3 2 2 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 You can provide access to functions only if the Function IDs provided in Gateway Functions are valid 3 2 3 Maintaining Upload Source Details Oracle FLEXCUBE facilitates upload of data from an external source The details of the source from which data has to be up
179. 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_NOTIFICATION FCUBS_HOTIF_HEADER 4 6 ORACLE 4 3 1 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 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 DESTINATION 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 4 7 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
180. ields and the display fields as in the corresponding Oracle FLEXCUBE screen e EmbargoMaint Query Res PK This is the response message which will be sent back to the external system when Embargo maintenance 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 Embargo maintenance record in the Oracle FLEXCUBE data store 6 47 ORACLE Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e EmbargoMaint Query Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query Embargo maintenance fails 6 2 7 11 6 2 8 due to any functional error QueryTransactionCodes This is the message for querying transaction code FCUBSSTService All the operations that can be performed on a customer are logically grouped under a service called FCUBSSTService Oracle FLEXCUBE supports the following operations under this service CreateAccClasMaint ModifyAccClasMaint DeleteAccClasMaint QueryAccClasMaint AuthAccClasMaint CreateSTTrnTax ModifySTTrnTax QuerySTTrnTax CloseSTTrnTax ReopenSTTrnTax CreateManStatChangInp CreateDCMaster ModDCMaster AuthDCMaster CloseDCMaster DeleteDCMaster QueryDC Master NewCExtService ModCExtService AuthCExtService CloseCExtService DeleteCExtService QueryCEx
181. ified format The format of the message is called Input only which has only those fields that are actually required for closing an amount block AmountBlocksClose 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 AmountBlocksClose 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 record in the Oracle FLEXCUBE data store 6 2 6 FCUBSCGService All the operations that can be performed on clearing are logically grouped under a service called FCUBSCGService Oracle FLEXCUBE supports the following operations under this service CreateSecCode CloseSecCode ModifySecCode QuerySecCode ReopenSecCode CreateChkProtContract ReverseChkProtContract QueryChkProtTxn CreateCGProductMaint ModifyCGProductMaint CloseCGProductMaint ReopenCGProductMaint QueryCGProductMaint CreateDocType ModifyDocType QueryDocType CloseDocType ReopenDocT ype CreateDocException ModifyDocException QueryDocException CloseDocException ReopenDocException CreateClgServicePo
182. imary Key response which includes only the primary key fields of Embargo maintenance record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e EmbargoMaint Modify Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to modify Embargo maintenance fails due to any functional error 6 2 7 8 AuthEmbargoMaint This is the operation code for authorizing Embargo maintenance in Oracle FLEXCUBE It involves the following messages e EmbargoMaint Auth Reg This is the request message to authorize Embargo maintenance in Oracle FLEXCUBE UBS An external system which intends to authorize Embargo maintenance 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 authorizing Embargo maintenance e EmbardoMaint Auth Res Full This is the response message which will be sent back to the external system when Embargo maintenance is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e EmbargoMaint Auth Res PK This is the response message which will be sent back to the external system when Embargo ma
183. 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 6 95 ORACLE 6 2 17 5 CBDTRONL_AUTH Req lO This is the request message to authorize CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDTRONL_AUTH Res Full This is the response message which is sent back to the external system when CB contract is authorized 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 CBDTRONL_AUTH Res PK This is the response message which is sent back to the external system when CB contract is authorized 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 CBDTRONL MODIFY This is the operation code is to modify CB contract It involves the following messages 6 2 17 6 CBDTRONL_MODIFY Regq Full This is the request message to modify CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called F
184. in the corresponding Oracle FLEXCUBE front end screen e ModifyCExtService Req lO This is the request message to modify External service An external system which intends to modify External service has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ModifyCExtService Res Full This is the response message which is sent back to the external system when External service is modified 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 ModifyCExtService Res PK This is the response message which is sent back to the external system when External service is modified The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 8 20 AuthCExtService This is the operation code for authorizing an External Service in Oracle FLEXCUBE It involves the following messages e CExtService Auth Reg This is the request message to authorize an External Service in Oracle FLEXCUBE UBS An external system which intends to authorize an External Service has to send the request in the specified format The format of the message is 6 56 ORACLE 6 2 8 21 called Input only which has only those fields that are actually required for a
185. ined 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 SaveLoan accountDetails Res PK This is the response message which is sent back to the external system when loan account details are maintained 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 QueryAccount This is the operation code is to query loan account details It involves the following messages 6 2 16 8 QueryLoan accountDetails Req Full This is the request message to query loan account details An external system which intends to query loan account details 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 QueryLoan accountDetails Req lO This is the request message to query loan account details An external system which intends to query loan account details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryLoan accountDetails Res Full This is the response message which is sent back to the external system when loan account details are maintained
186. int ModifyClgServicePoint CloseClgServicePoint ReopenClgServicePoint QueryChequeCorrespondence 6 28 ORACLE ModifyChequeCorrespondence CreateExtendOrRelease CloseCGRejErrCdMaint ReopenCGRejErrCdMaint QueryCGRejErrCdMaint CreateCollectionCheque QueryCollectionCheque ReverseCollectionCheque QueryTrnCost 6 2 6 1 CreateSecCode This is the operation code to create a new record in the sector code maintenance It involves the following messages CreateSecCode Req Full This is the request message to create a new record An external system which intends to create 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 CreateSecCode Req lO This is the request message to create a new record An external system which intends to create a record has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CreateSecCode Res Full This is the response message which is sent back to the external system when a record is created 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 CreateSecCode Res PK This is the response message which is sent b
187. intenance 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 Embargo maintenance record in the Oracle FLEXCUBE data store 6 46 ORACLE Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e EmbargoMaint Auth Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to authorize Embargo maintenance fails due to any functional error 6 2 7 9 DeleteEmbargoMaint This is the operation code for deleting Embargo maintenance in Oracle FLEXCUBE It involves the following messages 6 2 7 10 e EmbargoMaint Delete Reg This is the request message to deleting Embargo maintenance in Oracle FLEXCUBE UBS An external system which intends to delete Embargo maintenance 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 Embargo maintenance EmbargoMaint Delete Res Full This is the response message which will be sent back to the external system when Embargo maintenance is successfully deleting in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen
188. ion beneficiary are logically grouped under a service called FCUBSUPService Oracle FLEXCUBE supports the following operations under this service e CreatePCBeneficiary e ModifyPCBeneficiary e ClosePCBeneficiary e ReopenPCBeneficiary e BeneficiaryMaintenanceNew e BeneficiaryMaintenanceMod e BeneficiaryMaintenanceCls e BeneficiaryMaintenanceRpn e BeneficiaryMaintenanceExq e CreatePmtAgreement 6 67 ORACLE 6 2 11 1 ModifyPmtAgreement ClosePmtAgreement ReopenPmtAgreement QueryPmtAgreement AmendPmtMode QueryPmtMode PmtAuthorize AmendPmtExt QueryPmtExt PmtExtAuthorize ModifyFunding AuthorizeFunding DeleteFunding QueryFunding CreatePCBeneficiary This is the operation code to create a payment and collection beneficiary It involves the following messages 6 2 11 2 CreatePCBeneficiary Req Full MSG This is the request message to create a payment and collection beneficiary An external system which intends to create a payment and collection beneficiary 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 CreatePCBeneficiary Req lO MSG This is the request message to create a payment and collection beneficiary An external system which intends to create a payment and collection beneficiary has to send the request in the format specified The format
189. is sent back to the external system when payment details are maintained 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 SavePaymentDetails Res PK This is the response message which is sent back to the external system when payment details are maintained 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 DeletePayment This is the operation code is to delete payment details It involves the following messages DeletePaymentDetails Req Full This is the request message to delete payment details An external system which intends to delete payment details 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 DeletePaymentDetails Req lO This is the request message to delete payment details An external system which intends to delete payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to delete DeletePaymentDetails Res Full This is the response message which is sent back to the external system when payment details ar
190. 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 e 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 e 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 actually required for creating an FT contract e 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 correspondi
191. k to the external system when cheque book details for a customer account is successfully authorised in Oracle FLEXCUBE UBS The format of the message is called Primary Key 6 7 ORACLE response which includes only the primary key fields of the cheque book record in the Oracle FLEXCUBE data store 6 2 2 5 CheckBookDelete This is the operation code for deleting cheque book details for a customer account in Oracle FLEXCUBE It involves the following messages e CheckBookDelete Reg Full This is the request message to delete cheque book details for a customer account in Oracle FLEXCUBE UBS An external system which intends to delete 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 e CheckBookDelete Req lO This is the request message to delete cheque book details for a customer account in Oracle FLEXCUBE UBS An external system which intends to delete 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 deleting cheque book e CheckBookDelete Res Full This is the response message which is sent back to the external system when cheque book details for a customer account is successfully deleted in Oracle FLEXCUBE UBS The format of the mess
192. l system maintenance in set as Primary Key e TD Account Query Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query a Term Deposit fails due to any functional error 6 2 10 4 QueryTDEndorHist This is the operation code for querying the endorsement history details 6 2 10 5 CreateFraction This is the operation code for creating a fraction through gateway 6 2 10 6 Authorize Fraction This is the operation code for authorizing a fraction through gateway The fraction created can be authorized using this service 6 2 10 7 Modify Fraction This is the operation code for modification of fraction through gateway Only unconfirmed fractions can be reopened and modified 6 2 10 8 Query Fraction This is the operation code for querying a Fraction account in Oracle FLEXCUBE The fraction created can be queried through this operation 6 2 10 9 Delete Fraction This is the operation code for deleting a Fraction account in Oracle FLEXCUBE before authorizing 6 2 10 10 Create Prepmnt Req This is the operation code for creating a prepayment request in Oracle FLEXCUBE 6 2 10 11 Modify Prepmnt Req This is the operation code for modification of prepayment request in Oracle FLEXCUBE 6 66 ORACLE 6 2 10 12 Query Prepmnt Reg This is the operation code for query of prepayment request in Oracle FLEXCUBE 6 2 10 13 TDRedemSave This is the operation code for saving of redemp
193. l the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen AuthorizePmt Res PK MSG This is the response message which is sent back to the external system when a payment is authorized The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store AmendPmtExt This is the operation code to amend a payment extension It involves the following messages 6 2 11 19 AmendPmitExtention Req Full MSG This is the request message to amend a payment extension An external system which intends to amend a payment extension 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 AmendPmtExtention Req IO MSG This is the request message to amend a payment extension An external system which intends to amend a payment extension has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to amend AmendPmitExtention Res Full MSG This is the response message which is sent back to the external system when a payment extension is amended The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the correspon
194. 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 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 3 23 ORACLE e Gateway Maintenance Gateway Maintenance Branch Code External System Module Code 10f1 mi Senicename Operation Code Task Initiation Required Efectve Date L Maker Date Time Mod No Checker Date Time Record Status Authorization Status In this screen you can specify the following details Branch Code Specify the branch code of the 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
195. ll be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key ReopenSTTrnTax Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to reopened a transaction tax fails due to any functional error CreateManStatChangInp This is the operation code to change manual status for a customer account It involves the following messages 6 2 8 12 e CreateManStatChanglnp Req Full This is the request message to change manual status for an account An external system which intends to change manual status 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 CreateManStatChanglnp Req lO This is the request message to change manual status for an account An external system which intends to change manual status for an account has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CreateManStatChanglnp Res Full This is the response message which is sent back to the external system when manual status is changed 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
196. ll screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CustAcc Static Authorize Res PK MSG This is the response message which will be sent back to the external system when a customer 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 6 2 2 27 CloseCustAcc This is the operation code to close a customer account It involves the following messages e CustAcc Static Close Req Full MSG This is the request message to close a customer account in Oracle FLEXCUBE UBS An external system which intends to close a customer account has to send the request in the specified format 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 CustAcc Static Close Req MSG This is the request message to close a customer account in Oracle FLEXCUBE UBS An external system which intends to close a customer account has to send the request in the specified format The format of the message is called Input only which has only those fields which are closed e CustAcc Static Close Res Full MSG This is the response message which will be sent back to the external system when a customer account is successfully closed in Oracle FLEXCUBE UBS The f
197. llover Create Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create a Term Deposit fails due to any functional error QueryTDAcc This is the operation code for querying a Term Deposit account in Oracle FLEXCUBE It involves the following messages 6 65 ORACLE e TD Account Query Req This is the request message to query a Term Deposit TD account in Oracle FLEXCUBE UBS An external system which intends to modify the 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 modifying a TD e TD Account Query Res Full This is the response message which will be sent back to the external system when a Term Deposit TD account is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e TD Account Query Res PK This is the response message which will be sent back to the external system when a Term Deposit TD 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 TD record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway Externa
198. lly required for creating a customer CustAcc Static Create Req Full This is the request message to create a new customer account in Oracle FLEXCUBE UBS An external system which intends to create a new customer account has to send the request in the format specified The format of the message is called Full screen which is includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CustAcc Static Create Res Full This is the response message which will be sent back to the external system when a new customer account is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen Note If the request message is in full screen format then response will be in this format only CustAcc Static Create Res PK This is the response message which will be sent back to the external system when a new customer 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 customer account record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key CustAcc Static Create Req Flit This XML message in
199. loaded 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 UpLoad Source Definition Source Code Description C Base Data From FLEXCUBE O System Authorization Required Number Input By Authorized By Modification Authorized Exit Date Time Date Time Open 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 7 ORACLE 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 SourceCode sa Module Code az Error Handling On Exception Reject On Override Ignore v bhaca k Post Upload Status Authorized Purge Days Calendar aaa
200. ludes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CloseClgServicePoint Close Res PK This is the response message which will be sent back to the external system when a clearing service point 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 clearing service point record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e CloseClgServicePoint Close Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to close a clearing service point fails due to any functional error 6 2 6 22 ReopenClgServicePoint This is the operation code for reopening a clearing service point account in Oracle FLEXCUBE It involves the following messages e ReopenClgServicePoint Reopen Req This is the request message to reopen a clearing service point account in Oracle FLEXCUBE UBS An external system which intends to reopen the clearing service point 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 reopen a clearing service point e ReopenClgServicePoint Reopen Res Full This is the response message which will be
201. message is called Input only which has only those fields that are actually required for creating a new External service e CExtService New Res Full This is the response message which will be sent back to the external system when a new External service is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CExtService New Res PK This is the response message which will be sent back to the external system when a new External service 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 a new External service record in the Oracle FLEXCUBE data store e CExtService New Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create a new External service fails due to any functional error 6 2 8 19 ModCExtService This is the operation code to Modify External service It involves the following messages e ModifyCExtService Req Full This is the request message to modify External service An external system which intends to modify External service 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
202. message is called 6 59 ORACLE 6 2 8 28 Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CloseCBrandMaintenance Res PkK This is the response message which is sent back to the external system when brand details are deleted The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store DeleteCBrandMaint This is the operation code to delete brand details It involves the following messages 6 2 8 29 e DeleteCBrandMaintenance Req Full This is the request message to delete brand details An external system which intends to delete brand details 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 DeleteCBrandMaintenance Req lO This is the request message to delete brand details An external system which intends to delete brand details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query DeleteCBrandMaintenance Res Full This is the response message which is sent back to the external system when brand details are deleted The format of the message is called Full screen respon
203. n Oracle FLEXCUBE It involves the following messages e AccountStructureNew Req Full This is the request message to create account structure in Oracle FLEXCUBE UBS An external system which intends to create account structure has to send the request in the format specified The format of the message is called Full screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen e AccountStructureNew Req lO 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 e AccountStructureNew Res Full This is the response message which is sent back to the external system when account structure is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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 6 24 ORACLE includes only the primary key fields o
204. nal system 6 11 ORACLE 6 2 2 14 6 2 2 15 which intends to create the stop payment parameter 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 screen CreateStopPaymentsParameter Req PK This is the request message sent by the external system for creation of a new stop payment parameter record An external system which intends to create the stop payment parameter record has to send the request in the format specified The format of the message is called Primary Key which includes only the primary key fields of the record CreateStopPaymentsParameter Res Full This is the response message which is sent back to the external system when a stop payment parameter record 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 CreateStopPaymentsParameter Res PK This is the response message which is sent back to the external system when a stop payment parameter record 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 record CloseStopPaymentsParameter CloseStopPaymentsParameter Req Full This is the
205. ng Oracle FLEXCUBE screen e 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 It involves the following messages e 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 e 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 which has only those fields that are actually required for amending an FT contract e 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 fi
206. nous FLEXCUBE UBS This can be used if the external MDB system chooses to communicate only through JMS queues Handoffs from Asynchronous FLEXCUBE UBS Recommended Oracle FLEXCUBE Notify 2 4 ORACLE 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 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 2 5 ORACLE 3 1 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 GWDEXSYS9 in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button External System Maintenance External System Correlation Pattern External System Request Messageld Description Message
207. nsaction An external system which intends to create cheque protest 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 e CreateChkProtContract Req lO This is the request message to create a cheque protest transaction An external system which intends to create CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CreateChkProtContract Res Full This is the response message which is sent back to the external system when a cheque protested transaction is created 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 CreateChkProtContract Res PK This is the response message which is sent back to the external system when a cheque protested transaction is created The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store ReverseChkProtContract This is the operation code to reverse a cheque protest transaction It involves the following messages e ReverseChkProtContract Req Full This is the request message to re
208. nse message which is sent back to the external system when a collection service agreement is done 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 ReopenCollAgreement This is the operation code to reopen coll agreement It involves the following messages 6 2 15 5 ReopenCollAgreement Req Full This is the request message to reopen a collection service agreement An external system which intends to reopen a collection service agreement 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 ReopenCollAgreement Req lO This is the request message to reopen a collection service agreement An external system which intends to reopen a collection service agreement has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ReopenCollAgreement Res Full This is the response message which is sent back to the external system when a collection service agreement is done 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 ReopenCollAgreement
209. nt are mapped in this case 5 3 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 6 2 Inbound Application Integration 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 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 FCUBSFTService FCUBSAccService FCUBSDDService FCUBSLDService FCUBSCustomerService FCUBSCGService FCUBSPARQRYService FCUBSSTService FCUBSPCService FCUBSILService FCUBSTDService FCUBSCLService FCUBSCBService FCUBSUPService 6 2 1 FCUBSFTService All funds transfer operations are logically grouped under a service called FCUBSFT Service Oracle FLEXCUBE supports the following operations under this service CreateMt101 AuthorizeMt101 DeleteMt101 ModifyMt101 QueryMt101 CreateFT Contract AmendFT Contract QueryFTContract 6 1 ORACLE 6 2 1 1 CreateMt101 This is the operation code for crea
210. ntenance Res PK This is the response message which will be sent back to the external system when Brand details are successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of brand details record in the Oracle FLEXCUBE data store e AuthCBrandMaintenance FIt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to authorize brand details fails due to any functional error CloseCBrandMaint This is the operation code to close brand details It involves the following messages e CloseCBrandMaintenance Req Full This is the request message to close brand details An external system which intends to close brand details 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 CloseCBrandMaintenance Req lO This is the request message to close brand details An external system which intends to close brand details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CloseCBrandMaintenance Res Full This is the response message which is sent back to the external system when brand details are closed The format of the
211. ntenance in Oracle FLEXCUBE It involves the following messages 6 2 8 34 CloseCityCode Req This is the request message to close city code maintenance in Oracle FLEXCUBE UBS An external system which intends to city code maintenance 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 Embargo maintenance CloseCityCode Res Full This is the response message which will be sent back to the external system when city code maintenance is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CloseCityCode Res PK This is the response message which will be sent back to the external system when city code maintenance 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 city code maintenance record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key CloseCityCode Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to close city code maintenance fails due to any functional error Query
212. ntract 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 This is the operation code for querying LD simulation contract in Oracle FLEXCUBE It involves the following messages e DeleteQueryLDSIMContract Req lO 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 e 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 6 2 4 4 LDVamiCreateSim This is the operation code for creating LD VAMI Simulation contract in Oracle FLEXCUBE It involves the following messages e 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 t
213. o 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 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 involv
214. o 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 the details for reversing stop payments CreateStopPaymentsReversal Res Full This is the response message which is sent back to the external system when the details for reversing stop payments are 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 CreateStopPaymentsReversal Res PK This is the response message which is sent back to the external system when the details for reversing stop payments are 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 stop payments reversal record in the Oracle FLEXCUBE data store 6 2 2 8 ModifyStopPaymentsReversal This is the operation code for modifying the existing details for reversing stop payments for an individual cheque in Oracle FLEXCUBE It involves the following messages ModifyStopPaymentsReversal Req Full This is the request message to modify the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to modify the details for reversing stop payments has to send the request in the format specified The format of the message is
215. ode This is the operation code to query a record in the sector code maintenance It involves the following messages e QuerySecCode Regq Full This is the request message to query a record An external system which intends to query 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 e QerySecCode Req lO This is the request message to query a record An external system which intends to create a record has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e QuerySecCode Res Full This is the response message which is sent back to the external system when a record is queried 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 QuerySecCode Res PkK This is the response message which is sent back to the external system when a record is queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 6 5 ReopenSecCode This is the operation code to reopen a new record in the sector code maintenance It involves the following messages
216. of an existing customer in Oracle FLEXCUBE It involves the following messages e Cust Static Reopen Req This is the request message to reopen the details of a customer in Oracle FLEXCUBE UBS An external system which intends to reopen the customer details 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 reopened for a customer e Cust Static Reopen Res Full This is the response message which will be sent back to the external system when the details of a customer are reopened successfully in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e Cust Static Reopen Res PK This is the response message which will be sent back to the external system when the details of a customer are reopened successfully 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 in the Oracle FLEXCUBE data store e Cust Static Reopen Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to reopen an existing customer Cust Static Modify Req fails due to any functional error 6 2 5 6 AccountStructureNew This is the operation code for creating Account Structure i
217. okQuery This is the operation code for querying new Cheque Book in Oracle FLEXCUBE It involves the following messages e 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 e CheckBookQuery Req lO 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 e CheckBookQuery Res Full This is the response message which is sent back to the external system when a cheque book is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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
218. on Description FLEXCUBE UBS FLEXCUBE Universal Banking Solution Organization The manual is organized in the following manner Chapter 1 About this Manual gives information on the intended audience It also lists the various chapters covered in this User Manual Chapter 2 Gateway Functions An Overview explains the features of this module Chapter 3 External System Maintenance explains the maintenance of external systems and the various processes involved Chapter 4 Message Formats explains the different message formats Chapter 5 FLEXML Adapter Message Conversion explains details about the FLEXML Adapter Conventions Used in this Manual Important information is preceded with the symbol 1 1 ORACLE 1 6 Glossary of Icons This User Manual may refer to all or some of the following icons Icons Function New fs Copy Save pai Delete G Unlock Print amp Close Re open p Reverse pR Template S Roll over M Hold E Authorize re Liquidate Bg exit Sign off Help Add row Delete row ai Option List e Confirm ORACLE Icons Function 9 Enter Query ae Execute Query Refer the Procedures User Manual for further details about the icons ORACLE ORACLE ORACLE 2 1 2 2 2
219. on 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 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 3 22 ORACLE 3 9 Notifications Enroute Summary Authorization Status Record Status Branch Code H Notification Code Destination Name Q Search Advanced Search Reset Records per page 14 4 4 of 4L oO Authorization Status Record Status Branch Code Notification Code Destination Name Authorization Status A Authorized U Unauthorized Record Status C Closed O Open 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
220. onse which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen 6 2 4 7 CreateLDPaymentSim This is the operation code for creating LD Payment Simulation in Oracle FLEXCUBE It involves the following messages e 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 e 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 e 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 e CreateLDPaymentSim Res PK This is the response message whi
221. onse which includes only the primary key fields of the clearing service point record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e ClgServicePoint Create Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create a clearing service point fails due to any functional error 6 2 6 20 ModifyClqServicePoint This is the operation code for modifying a clearing service point account in Oracle FLEXCUBE It involves the following messages e ClgServicePoint Modify Req This is the request message to modify a clearing service point account in Oracle FLEXCUBE UBS An external system which intends to modify the clearing service point 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 clearing service point e ClgServicePoint Modify Res Full This is the response message which will be sent back to the external system when a clearing service point is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e ClgServicePoint Modify Res PK This is the response message which will
222. onse which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CBDDLMNT_MODIFY Res PK This is the response message which is sent back to the external system when CB document location record is modified 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 CBDDSMNT_ NEW This is the operation code is to create the document status record It involves the following messages CBDDSMNT_ NEW Req Full This is the request message to create the document status record An external system which intends to save payment details 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 CBDDSMNT_ NEW Reg lO This is the request message to create the document status record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDDSMNT_ NEW Res Full This is the response message which is sent back to the external system when the document status record is created The format of the message 6 104 ORACLE 6 2 17 27 is called Full screen response w
223. onse Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key CloseCGRejErrCdMaint Close Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to close a error code maintenance fails due to any functional error ReopenCGRejErrCdMaint This is the operation code for reopening error code maintenance in Oracle FLEXCUBE It involves the following messages e ReopenCGRejErrCdMaint Reopen Reg This is the request message to reopen error code maintenance in Oracle FLEXCUBE UBS An external system which intends to reopen the error code maintenance 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 reopen a clearing service point e ReopenCGRejErrCdMaint Reopen Res Full This is the response message which will be sent back to the external system when a error code maintenance is successfully reopened in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e ReopenCGRejErrCdMaint Reopen Res PkK This is the response message which will be sent back to the external system when error code maintenance is successfully reopened in Oracle FLEXCUBE UBS The format of the message is called Primary Key response
224. or response generated by Oracle FLEXCUBE when the processing of request to modify a transaction tax fails due to any functional error 6 51 ORACLE 6 2 8 8 QuerySTTrnTax This is the operation code for querying a transaction tax in Oracle FLEXCUBE It involves the following messages e QuerySTTrnTax Req This is the request message to query a transaction tax in Oracle FLEXCUBE UBS An external system which intends to query the transaction tax 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 transaction tax e QuerySTTrnTax Res Full This is the response message which will be sent back to the external system when a transaction tax is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e QuerySTTrnTax Res PK This is the response message which will be sent back to the external system when a transaction tax 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 transaction tax record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key
225. ormat 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 CBDNRMNT_ MODIFY Res PK This is the response message which is sent back to the external system when CB notary code record is modified 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 CBDDLMNT_ NEW This is the operation code is to create a new CB document location record It involves the following messages 6 2 17 24 CBDDLMNT_ NEW Req Full This is the request message to create a new CB document location record An external system which intends to save payment details 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 CBDDLMNT_ NEW Req lO This is the request message to create a new CB document location record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDDLMNT_ NEW Res Full This is the response message which is sent back to the external system when CB document location record is created The format of t
226. ormat 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 CustAcc Static Close Res PK MSG This is the response message which will be sent back to the external system when a customer 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 6 2 3 FCUBSDDService All the demand draft operations are logically grouped under a service called FCUBSDDService Oracle FLEXCUBE supports the following operations under this service e CreateTransaction 6 17 ORACLE e QueryDDTransaction 6 2 3 1 CreateTransaction This is the operation code for creating transaction in Oracle FLEXCUBE It involves the following messages e 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 e CreateTransaction Req lO 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 i
227. ose a payment agreement has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ClosePmtAgreement Res Full MSG This is the response message which is sent back to the external system when a payment agreement is done 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 ClosePmtAgreement Res PK MSG This is the response message which is sent back to the external system when a payment agreement is done The format of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store ReopenPmtAgreement This is the operation code to reopen a payment agreement It involves the following messages 6 2 11 14 ReopenPmtAgreement Req Full MSG This is the request message to reopen a payment agreement An external system which intends to reopen a payment agreement 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 ReopenPmtAgreement Req IO MSG This is the request message to reopen a payment agreement An external system which intends to reopen a payment agreement has to send the request in the
228. ous and Asynchronous Deployment Pattern for addressing the 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 2 1 ORACLE 2 2 2 2 2 3 2 2 4 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 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
229. payments for an individual cheque in Oracle FLEXCUBE It involves the following messages 6 2 2 10 AuthoriseStopPaymentsReversal Req Full This is the request message to authorise the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to authorise the details for reversing stop payments 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 AuthoriseStopPaymentsReversal Req lO This is the request message to authorise the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to authorise the details for reversing stop payments 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 authorising the details for reversing stop payments AuthoriseStopPaymentsReversal Res Full This is the response message which is sent back to the external system when the details for reversing stop payments are successfully authorised 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 AuthoriseStopPaymentsReversal Res PK This is the response message which is sent
230. plicable to systems such as the following 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 2 2 ORACLE 2 3 2 4 2 5 2 6 This is especially applicable to systems such as the following 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 mess
231. ption This is the operation code to modify clearing retention exception maintenance It involves the following messages 6 2 6 16 ModifyDocException Req Full This is the request message to modify clearing retention exception maintenance An external system which intends to modify clearing retention exception maintenance 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 ModifyDocException Req lO This is the request message to modify clearing retention exception maintenance An external system which intends to modify clearing retention exception maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifyDocException Res Full This is the response message which is sent back to the external system when clearing retention exception is modified 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 ModifyDocException Res PK This is the response message which is sent back to the external system when clearing retention exception is modified The format of the message is called Primary Key response which includes only the primary key
232. racle FLEXCUBE data store 6 45 ORACLE Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e EmbargoMaint New Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to create Embargo maintenance fails due to any functional error 6 2 7 7 ModifyEmbargoMaint This is the operation code for modifying Embargo maintenance in Oracle FLEXCUBE It involves the following messages e EmbargoMaint Modify Req This is the request message to modify Embargo maintenance in Oracle FLEXCUBE UBS An external system which intends to modify Embargo maintenance 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 Embargo maintenance EmbargoMaint Modify Res Full This is the response message which will be sent back to the external system when Embargo maintenance is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e EmbargoMaint Modify Res PK This is the response message which will be sent back to the external system when Embargo maintenance is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Pr
233. ranslate 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 affiliates 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
234. ration codes under this service 6 2 13 1 CreatelnterestAdjustment ModifylnterestAdjustment CloselnterestAdjustment ReopenInterestAdjustment QuerylnterestAdjustment CreatelnterestAdjustment This is the operation code to create interest adjustment for branch account product and next liquidation date combination It involves the following messages CreatelnterestAdjustment Req Full MSG This is the request message to create interest adjustment An external system which intends to create interest adjustment 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 CreatelnterestAdjustment Req lIO MSG This is the request message to create interest adjustment An external system which intends to create interest adjustment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CreatelnterestAdjustment Res Full MSG This is the response message which is sent back to the external system when interest adjustment is done 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 CreatelnterestAdjustment Res PK MSG This is the response message which is sent
235. rd in the Oracle FLEXCUBE data store AuthDCMaster This is the operation code for authorizing card details in Oracle FLEXCUBE It involves the following messages 6 2 8 15 e AuthDCMaster Req This is the request message to authorize card details in Oracle FLEXCUBE UBS An external system which intends to authorize card details 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 authorizing card details AuthDCMaster Res Full This is the response message which will be sent back to the external system when Card details are successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen AuthDCMaster Res PK This is the response message which will be sent back to the external system when Card details are successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which includes only the primary key fields of card details record in the Oracle FLEXCUBE data store e AuthDCMaster Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to authorize card details fails due to any functional error CloseDCMaster This is the operation code to close card details It in
236. 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 ModifylLSweep Req lO MSG This is the request message to modify account structure for sweep An external system which intends to modify account structure for sweep has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ModifylLSweep Res Full MSG This is the response message which is sent back to the external system when account structure for sweep is modified 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 ModifylLSweep Res PK MSG This is the response message which is sent back to the external system when account structure for sweep is modified 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 DeletelLSweep This is the operation code to delete account structure for sweep for branch account product and next liquidation date combination It involves the following messages DeletelLSweep Req Full MSG This is the request message to delete account structure for sweep An external system whic
237. responding Oracle FLEXCUBE front end screen CBDTRONL_REVERSE Req lO This is the request message to reverse CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDTRONL_REVERSE Res Full This is the response message which is sent back to the external system when CB contract is reversed 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 CBDTRONL_REVERSE Res PK This is the response message which is sent back to the external system when CB contract is reversed The format of the message is called 6 96 ORACLE Primary Key response which includes only the primary key fields of the cheque book record in the Oracle FLEXCUBE data store 6 2 17 7 CBGPMTON NEW This is the operation code is to create a protest for CB contract It involves the following messages e CBGPMTON_NEW Reg Full This is the request message to create a protest for CB contract An external system which intends to save payment details 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
238. response message which is sent back to the external system when a payment extension is queried The format of the message is 6 75 ORACLE 6 2 11 20 called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store PmtExtAuthorize This is the operation code to authorize a payment extension It involves the following messages 6 2 11 21 AuthorizePmtExt Req Full MSG This is the request message to authorize a payment extension An external system which intends to authorize a payment extension 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 AuthorizePmtExt Req lO MSG This is the request message to authorize a payment extension An external system which intends to authorize a payment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to authorize AuthorizePmtExt Res Full MSG This is the response message which is sent back to the external system when a payment extension is authorized 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 AuthorizePmtExt Res PK MSG This is the response message whic
239. rimary key fields of the record in the Oracle FLEXCUBE data store 6 2 8 3 DeleteAccClasMaint This is the operation code to delete an account class It involves the following messages e DeleteAccClasMaint Req Full This is the request message to delete an account class An external system which intends to delete an account class 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 6 49 ORACLE e DeleteAccClasMaint Req lO This is the request message to delete an account class An external system which intends to delete an account class has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e DeleteAccClasMaint Res Full This is the response message which is sent back to the external system when an account class is deleted 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 DeleteAccClasMaint Res PK This is the response message which is sent back to the external system when an account class is deleted The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUB
240. ription Input By Authorized By Modification Authorized Date Time Date Time Number 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 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 GWSNTFIN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 3 20 ORACLE Notifications Installed Summary Authorization Status v Record Status v Branch Code aZ Notification Code zz Q Search Advanced Search Reset Records per page 1 14 4 4 of 1 I Im Autonzaton Situs Pecora Status Branch Code Notcaton Cod
241. rmat of the message is called Primary Key response which includes only the primary key fields in the Oracle FLEXCUBE data store AuthorizeFunding This is the operation code to authorize an online funding It involves the following messages AuthPCFunding Req Full MSG This is the request message to authorize an online beneficiary An external system which intends to authorize an online beneficiary 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 6 76 ORACLE 6 2 11 23 AuthPCFunding Req IO MSG This is the request message to authorize an online beneficiary An external system which intends to authorize an online beneficiary has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query AuthPCFunding Res Full MSG This is the response message which is sent back to the external system when an online beneficiary is done 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 AuthPCFunding Res PK MSG This is the response message which is sent back to the external system when an online funding is done The format of the message is called
242. rmat 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 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 e 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 e 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 6 3 ORACLE 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 e QueryMt101 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 e QueryMt101 Res PK This
243. rror response generated by Oracle FLEXCUBE when the processing of request to reopen city code maintenance fails due to any functional error 6 2 8 36 NewPassbookLog NewPassbookLog Req Full MSG This is the request message sent by the external system for creation of a new passbook log An external system which intends to create a new passbook log 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 screen 6 2 8 37 AuthPassbookLog AuthPassbookLog Req Full MSG This is the request message sent by the external system for authorization of a passbook log An external system which intends to authorize a passbook log 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 screen 6 2 8 38 DeletePassbookLog DeletePassbookLog Req Full MSG This is the request message sent by the external system for deletion of a passbook log An external system which intends to delete a passbook log 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 screen 6 63 ORACLE 6 2 8 39 CreateCustCatMaint
244. rse TDPayin e Authorize TDAcc e CloseTDAcc 6 64 ORACLE 6 2 10 1 DeleteTDAcc ModifyTDAcc This is the operation code for modifying a Term Deposit account in Oracle FLEXCUBE It involves the following messages 6 2 10 2 TD Account Modify Req This is the request message to modify a Term Deposit TD account in Oracle FLEXCUBE UBS An external system which intends to modify the 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 modifying a TD TD Account Modify Res Full This is the response message which will be sent back to the external system when a Term Deposit TD account is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen TD Account Modify Res PK This is the response message which will be sent back to the external system when a Term Deposit TD 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 TD record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key TD Rollover Modify Flt This XML message indicates t
245. ructure 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 25 ORACLE 6 2 5 8 AccountStructureQuery This is the operation code for querying an account structure in Oracle FLEXCUBE It involves the following messages e 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 e AccountStructureQuery Reg lO This is the request message to query an account structure in Oracle FLEXCUBE UBS An external system which intends to query an account structure has to send the request in the specified format The format of the message is called Input only which has only those fields that are actually required for querying account structure e 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
246. ryPaymentDetails Res Full This is the response message which is sent back to the external system when payment details are maintained 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 QueryPaymentDetails Res PK This is the response message which is sent back to the external system when payment details are maintained 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 CreatePayment This is the operation code is to save payment details It involves the following messages 6 2 16 3 SavePaymentDetails Req Full This is the request message to save payment details An external system which intends to save payment details 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 SavePaymentDetails Req lO This is the request message to save payment details An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save SavePaymentDetails Res Full This is the response message which
247. s input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CustAcc Static Query Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query on a customer account CustAcc Static Query Req fails due to any functional error ModifyCustAcc This is the operation code to modify a customer account It involves the following messages e CustAcc Static Modify Reg Full MSG This is the request message to Modify a customer account in Oracle FLEXCUBE UBS An external system which intends to modify a customer account has to send the request in the specified format 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 CustAcc Static Modify Req MSG This is the request message to Modify a customer account in Oracle FLEXCUBE UBS An external system which intends to modify a customer account has to send the request in the specified format The format of the message is called Input only which has only those fields which are modified CustAcc Static Modify Res Full MSG This is the response message which will be sent back to the external system when a customer 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 fi
248. s called Input only which has only those fields that are actually required for creating a transaction e CreateTransaction Res Full This is the response message which is sent back to the external system when transaction is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e 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 e 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 e 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
249. s the response message which is sent back to the external system when collection type record is modified 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 CBDCLMNT_MODIFY Res PK This is the response message which is sent back to the external system when collection type record is modified 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 CBDNRMNT_ NEW This is the operation code is to create CB notary code record It involves the following messages 6 2 17 21 CBDNRMNT_NEW Req Full This is the request message to create CB notary code record An external system which intends to save payment details 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 CBDNRMNT_NEW Req lO This is the request message to create CB notary code record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDNRMNT_NEW Res Full This is the response message which is sent back to the ex
250. sage to create an extension for CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBGEXTON_NEW Res Full This is the response message which is sent back to the external system when CB contract extension is created 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 CBGEXTON_NEW Res PK This is the response message which is sent back to the external system when CB contract extension is created 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 CBGCLOON NEW This is the operation code is to create a new CB operation closure record It involves the following messages 6 2 17 11 CBGCLOON_NEW Req Full This is the request message to create a new CB operation closure record An external system which intends to save payment details 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 CBGCLOON_NEW Req lO This is the request message to create a new CB operation
251. se which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen DeleteCBrandMaintenance Res PkK This is the response message which is sent back to the external system when brand details are deleted The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store QueryCBrandMaint This is the operation code to query brand details It involves the following messages 6 2 8 30 e QueryCBrandMaint Req Full This is the request message to query a brand details An external system which intends to query brand details 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 QueryCBrandMaint Req lO This is the request message to query brand details An external system which intends to query brand details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e QueryCBrandMaint Res Full This is the response message which is sent back to the external system when brand details are queried The format of the message is called Full screen response which includes all the fields input fields and the display fields as in t
252. se which includes only the primary key fields of the record QueryStopPaymentsParameter QueryStopPaymentsParameter Req Full This is the request message sent by the external system for querying a stop payment parameter record An external system which intends to query a stop payment parameter 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 screen QueryStopPaymentsParameter Req PK This is the request message sent by the external system for querying a stop payment parameter record An external system which intends to query the stop payment parameter record has to send the request in the format specified The format of the message is called Primary Key which includes only the primary key fields of the record QueryStopPaymentsParameter Res Full This is the response message which is sent back to the external system when a stop payment parameter record is successfully queried in Oracle FLEXCUBE The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryStopPaymentsParameter Res PK This is the response message which is sent back to the external system when a stop payment parameter record is successfully queried in Oracle FLEXCUBE The format of t
253. 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 19 QueryGenAdvice This is the operation code for querying GenAdvice in Oracle FLEXCUBE It involves the following messages e 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 e 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 20 QueryPreLiquid This is the operation code for querying the account details before liquidation It involves the following messages It involves the following messages e Cust Account PreLig Req This is the request message to query the details of interest commission due for liquidation on the request date An external system which intends to query the details of account has to send the request in the format specified e Cust Accoun
254. sponse which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen QueryProduct Res PK This is the response message which is sent back to the external system when product details are maintained 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 QueryClinfo This operation is used to query the loan information in Oracle FLEXCUBE It involves the following messages e QueryCllnfoResponseDetails Req Full This is the request message to query loan information An external system which intends to query loan information 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 QueryClinfoResponseDetails Req IO This is the request message to query loan information An external system which intends to query loan information has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryCllnfoResponseDetails Res Full This is the response message which is sent back to the external system when loan account information are maintained The format of the message is called Full screen response which includes
255. ssage Reference Branch Related Message Reference External System Service Name Operation Code Message Id Correlation Id A iv 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 3 19 ORACLE 3 7 1 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 using the Notifications Installed screen 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 Detailed Branch Code Branch Name Notification Code Desc
256. ssing of request to create a transaction tax fails due to any functional error 6 2 8 7 ModifySTTrnTax This is the operation code for modifying a transaction tax in Oracle FLEXCUBE It involves the following messages e ModifySTTrnTax Req This is the request message to modify a transaction tax in Oracle FLEXCUBE UBS An external system which intends to modify the transaction tax 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 transaction tax e ModifySTTrnTax Res Full This is the response message which will be sent back to the external system when a transaction tax is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e ModifySTTrnTax Res PK This is the response message which will be sent back to the external system when a transaction tax 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 transaction tax record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e ModifySTTrnTax Fit This XML message indicates the err
257. suedsbeeteoucetdsoedssacsuonsssesucdstdesosecebdsovbssecdeoscubesusesstesstees 7 4 7 3 8 PE GCUBS Customer SCr vie eeen a e E a aa EEE 7 4 7 3 9 PF GU BSI SCr E EE EET EA EEE EET EE 7 5 LIAO FCUBSEC Service srs eae a a EEE oa O E E AE EE EEE 7 5 7 3 11 PF GUBSEX SC a E A EE EE AE A E E EEA EE AE E E E 7 5 Tad FCUBSCO SErviCE ssir sna e EEE a A EE EEE 7 5 aA FCUBSSWwiteh Service srusen a EOE a a a E E EE ERE 7 5 Si SCREEN GLOSSARY si sisisccssscccssessosssssdedecsssessscendcesssevdscesnesdedosacesssgeeedseesssvsesonecedudecesesdvenssedeesdsesdobsocsedessense 8 1 8 1 FUNCTION TDD TTS Fees cee scbed eeesissenee ioc ceeeesadees a net eee 6 voted donee des sane a e E este dela E 8 1 1 2 ORACLE ORACLE ORACLE 1 1 1 2 1 3 1 4 1 5 1 About this Manual 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 for Input functions for maintenance related to the integration gateway IT managers Authorization functions Acronyms and Abbreviations Abbreviati
258. t 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 Cust Static Create Res Full gt lt CUSTNO gt CU99999 lt CUSTNO gt lt CTYPE gt C lt CTYPE gt lt SNAME gt NEWCUSTFLEXML102 lt SNAME gt lt LIABID gt CU99999 lt LIABID gt lt CCATEG gt Individual lt CCATEG gt lt COUNTRY gt USA lt COUNTRY gt zl E vocal intranet Z 3 18 ORACLE 3 6 1 Querying Outgoing Message Browser 3 7 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 Outgoing Message Browser Message Reference a Branch z Related Message Reference ae External System a Service Name a Operation Code H Message Id az Correlation Id Response Queue Message Id z User ld a Their User Id az Branch Date E Server Date Stamp E Message Status az Media l Q Search Advanced Search _ Reset Records per page 14 4 4 of 1 bibl O Me
259. t PreLig Res FULL This is the response message which is sent back to the external system when querying the details of account before liquidation The format of the message is called Full screen response which includes all the fields input fields and the display fields 6 2 2 21 Querycustaccbal This is the operation code for querying the account balance based on the indicator received It involves the following messages 6 14 ORACLE It involves the following messages 6 2 2 22 CA CustAcc Bal Query Req This is the request message to query the account balance An external system which intends to query the balance of account has to send the request in the format specified CA CustAcc Bal Query Res This is the response message which is sent back to the external system when querying the balance of account based on the indicator sent The format of the message is called Full screen response which includes all the fields input fields and the display fields CreateCustAcc This is the operation code for creating a new Savings Current account in Oracle FLEXCUBE It involves the following messages 6 2 2 23 CustAcc Static Create Reg This is the request message to create a new customer account in Oracle FLEXCUBE UBS An external system which intends to create a new customer 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 actua
260. t message to query beneficiary details An external system which intends to query beneficiary details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e QueryBeneficiaryMaint Res Full This is the response message which is sent back to the external system when beneficiary details are queried 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 QueryBeneficiaryMaint Res PK This is the response message which is sent back to the external system when beneficiary details are queried The format of the message is 6 71 ORACLE 6 2 11 10 called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store CreatePmtAgreement This is the operation code to create a payment agreement It involves the following messages 6 2 11 11 CreatePmtAgreement Req Full MSG This is the request message to create a payment and collection agreement An external system which intends to create a payment agreement 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 CreatePmtAgreement Req IO MSG
261. t 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 QueryStopPaymentsReversal Req lO This is the request message to query the details for reversing stop payments in Oracle FLEXCUBE UBS An external system which intends to query 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 QueryStopPaymentsReversal Res Full This is the response message which is sent back to the external system when the details for reversing stop payments are 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 QueryStopPaymentsReversal Res PK This is the response message which is sent back to the external system when the details for reversing stop payments are 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 stop payments reversal record in the Oracle FLEXCUBE data store CreateStopPaymentsParameter CreateStopPaymentsParameter Req Full This is the request message sent by the external system for creation of a new stop payment parameter record An exter
262. tService NewCBrandMaint ModCBrandMaint AuthCBrandMaint CloseCBrandMaint DeleteCBrandMaint QueryCBrandMaint CreateCustCatMaint 6 48 ORACLE e ModifyCustCatMaint e QueryCustCatMaint 6 2 8 1 CreateAccClasMaint This is the operation code to create a new account class It involves the following messages e CreateAccClasMaint Req Full This is the request message to create a new account class An external system which intends to create an account class 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 CreateAccClasMaint Req lO This is the request message to create a new account class An external system which intends to create an account class has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CreateAccClasMaint Res Full This is the response message which is sent back to the external system when an account class is created The format of the message is called Full screen response which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CreateAccClasMaint Res PK This is the response message which is sent back to the external system when an account class is created The format of the message
263. ted The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store CloseCGRejErrCdMaint This is the operation code for closing error code maintenance in Oracle FLEXCUBE It involves the following messages 6 2 6 27 e CloseCGRejErrCdMaint Close Req This is the request message to close error code maintenance in Oracle FLEXCUBE UBS An external system which intends to close the error code maintenance 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 clearing service point CloseCGRejErrCdMaint Close Res Full This is the response message which will be sent back to the external system when error code maintenance is successfully closed in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CloseCGRejErrCdMaint Close Res PK This is the response message which will be sent back to the external system when error code maintenance 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 error code maintenance record in the Oracle FLEXCUBE data store Note This response will be sent if the resp
264. ted deployment of FCUBS In this situation the database components of the Gateway are deployed as two or more schemas gt The messaging schema as part of SMS schema in the SMS and or HO instance gt 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 Deployment Patterns for Application Integration Business Nature of Oracle Remarks Integration Needs Integration FLEXCUBE Deployment Pattern 2 3 ORACLE Inbound Transactions into Oracle FLEXCUBE Synchronous FLEXCUBE UBS EJB Recommended FLEXCUBE UBS HTTP Servlet This can be used if the external system cannot communicate to Oracle FLEXCUBE using EJB FLEXCUBE UBS Web Services This can be used if the external system chooses to communicate only through Web Services Asynchronous FLEXCUBE UBS This can be used if the external MDB system chooses to communicate only through JMS queues Inbound Queries Synchronous FLEXCUBE UBS Recommended into Oracle EJB FLEXCUBE FLEXCUBE UBS This can be used if the external In Servlet system cannot communicate to Oracle FLEXCUBE using EJB FLEXCUBE UBS This can be used if the external Web Services system chooses to communicate only through Web Services Asynchro
265. tem 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 dangerous 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 t
266. tenance Res Full This is the response message which is sent back to the external system when brand details are modified 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 ModifyCBrandMaintenance Res PK This is the response message which is sent back to the external system when brand details are modified The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store AuthCBrandMaint This is the operation code for authorizing brand details in Oracle FLEXCUBE It involves the following messages 6 2 8 27 e AuthCBrandMaintenance Req This is the request message to authorize brand details in Oracle FLEXCUBE UBS An external system which intends to authorize brand details 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 authorizing brand details AuthCBrandMaintenance Res Full This is the response message which will be sent back to the external system when Brand details are successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e AuthCBrandMai
267. tends to query an External Service has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryCExtService Res Full This is the response message which is sent back to the external system when an External Service is queried 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 QueryCExtService Res PK This is the response message which is sent back to the external system when an External Service is queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store NewCBrandMaint This is the operation code for creating a brand in Oracle FLEXCUBE It involves the following messages 6 2 8 25 e NewCBrandMaintenance Req This is the request message to create a brand in Oracle FLEXCUBE UBS An external system which intends to create a brand 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 brand NewCBrandMaintenance Res Full This is the response message which will be sent back to the external system when a brand is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full s
268. ternal system when CB notary code record is created 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 CBDNRMNT_NEW Res PK This is the response message which is sent back to the external system when CB notary code record is created 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 CBDNRMNT_EXECUTEQUERY This is the operation code is to query for CB notary code It involves the following messages CBDNRMNT_EXECUTEQUERY Regq Full This is the request message to query for CB notary code An external system which intends to save payment details 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 CBDNRMNT_EXECUTEQUERY Req lO This is the request message to query for CB notary code An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDNRMNT_EXECUTEQUERY Res Full This is the response message which is sent back to the external system when query for CB notary code is queried
269. 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 ReopeninterestAdjustment Res PK MSG This is the response message which is sent back to the external system when interest adjustment is reopened 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 QuerylnterestAdjustment This is the operation code to query interest adjustment for branch account product and next liquidation date combination It involves the following messages 6 2 13 6 QuerylnterestAdjustment Req Full MSG This is the request message to query interest adjustment An external system which intends to query interest adjustment 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 QueryInterestAdjustment Reqg lO MSG This is the request message to query interest adjustment An external system which intends to reopen interest adjustment has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QuerylnterestAdjustment Res Full MSG This is the response message which is sent back to the ext
270. the processing of request to authorize an Embargo transaction fails due to any functional error 6 2 7 4 EmbargoQuery This is the operation code for querying an Embargo transaction in Oracle FLEXCUBE It involves the following messages e Embargo Query Reg This is the request message to query an Embargo transaction in Oracle FLEXCUBE UBS An external system which intends to query an Embargo 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 an Embargo transaction e Embargo Query Res Full This is the response message which will be sent back to the external system when an Embargo transaction is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e Embargo Query Res PK This is the response message which will be sent back to the external system when an Embargo transaction is successfully queried in Oracle FLEXCUBE UBS The format of the message is called Primary Key response which 6 44 ORACLE includes only the primary key fields of an Embargo transaction record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e
271. 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 unique id which indicates overrides FUNCTIONID This indicates the Oracle FLEXCUBE Function ID 4 4 ORACLE 4 2 2 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 FCUBS BODY The FCUBS_BODY will contain the actual payload to perform the respective transaction The contents of the payload will vary for each oper
272. those fields that can be used to save CBDAGMON_MODIFVY Res Full This is the response message which is sent back to the external system when CB agreement is modified 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 CBDAGMON_MODIFVY Res PK This is the response message which is sent back to the external system when CB agreement is modified 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 CBDCCMNT NEW This is the operation code is to create a new collection center record It involves the following messages CBDCCMNT_NEW Req Full This is the request message to create a new collection center record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Full screen which 6 99 ORACLE 6 2 17 15 includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CBDCCMNT_NEW Req lO This is the request message to create a new collection center record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be
273. ting Mt101 message in Oracle FLEXCUBE It involves the following messages e 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 e CreateMt101 Req lO 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 e 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 as in the corresponding Oracle FLEXCUBE screen e 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
274. tion cheque transaction has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ReverseCollectionCheque Res Full This is the response message which is sent back to the external system when a collection cheque transaction is reversed 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 ReverseCollectionCheque Res PK This is the response message which is sent back to the external system when a collection cheque transaction is reversed The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 2 7 FCUBSCoreServices All the operations that can be performed on a customer are logically grouped under a service called FCUBSCoreServices Oracle FLEXCUBE supports the following operations under this service e ConversionRate To Convert the Rate Based on the Maintenance e EmbargoNew 6 42 ORACLE EmbargoModify EmbargoAuth EmbargoQuery EmbargoDelete NewEmbargoMaint ModifyEmbargoMaint AuthEmbargoMaint DeleteEmbargoMaint QueryEmbargoMaint QueryTrnCost 6 2 7 1 EmbargoNew This is the operation code for creating an Embargo transaction in Oracle FLEXCUBE It involves the following messages Embargo New Regq T
275. tion code for querying the details of an existing customer in Oracle FLEXCUBE It involves the following messages e Cust Static Query Req This is the request message to query the details of a customer in Oracle FLEXCUBE UBS An external system which intends to query the customer details 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 queried for a customer e Cust Static Query Res Full This is the response message which will be sent back to the external system when the details of a customer are queried successfully in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e Cust Static Query Res PK This is the response message which will be sent back to the external system when the details of a customer are queried successfully 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 in the Oracle FLEXCUBE data store e Cust Static Query Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to query an existing customer Cust Static Modify Req fails due to any functional error 6 2 5 4 CloseCustomer This is the operation code for closing t
276. tion preclosure in Oracle FLEXCUBE 6 2 10 14 QueryTDPrint Cert This is the operation code for printing of TD certificate in Oracle FLEXCUBE The custody status of TD account gets changed every time the Td certificate is printed 6 2 10 15 Create TDpayin This is the operation code for creation of pay in to TD account in Oracle FLEXCUBE The combination of payin modes like Account Gl internal instrument internal cheque and cheque can be used However the Cheque payin can t be combined with any other modes 6 2 10 16 Reverse TDPayin This is the operation code for reversal of pay in made to TD account in Oracle FLEXCUBE The reversal of pay in is supported through payin modes like Account GL internal cheque internal instruments But the reversal of pay in through cheque is not supported 6 2 10 17 Authorize TDAcc This operation is for authorizing the TD account The request is sent from the external system to authorize the TD account 6 2 10 18 Close TDAcc This operation is for closing the TD account The request is sent from the external system to close the TD account This request is possible only on the same day of booking a TD 6 2 10 19 Delete TDAcc This operation is for deleting the TD account The request is sent from the external system to delete the TD account This request is possible only for unauthorized TD s 6 2 11 FCUBSPCService All the operations that can be performed on collections payments and collect
277. ue to any functional error 6 2 8 6 CreateST TrnTax This is the operation code for creating a transaction tax in Oracle FLEXCUBE It involves the following messages e CreateSTTrnTax Req This is the request message to create a transaction tax in Oracle FLEXCUBE UBS An external system which intends to create the transaction tax 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 tax e CreateSTTrnTax Res Full This is the response message which will be sent back to the external system when a transaction tax is successfully created in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e CreateSTTrnTax Res PK This is the response message which will be sent back to the external system when a transaction tax 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 tax record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e CreateSTTrnTax Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the proce
278. uery city code maintenance fails due to any functional error 6 2 8 35 ReopenCityCode This is the operation code for Reopening city code maintenance in Oracle FLEXCUBE It involves the following messages e ReopenCityCode Reg This is the request message to reopen city code maintenance in Oracle FLEXCUBE UBS An external system which intends to city code maintenance 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 Embargo maintenance e ReopenCityCode Res Full This is the response message which will be sent back to the external system when city code maintenance is successfully modified in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen e ReopenCityCode Res PK This is the response message which will be sent back to the external system when city code maintenance 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 city code maintenance record in the Oracle FLEXCUBE data store Note This response will be sent if the response Message Exchange Pattern in the Gateway External system maintenance in set as Primary Key e ReopenCityCode Flt This XML message indicates the e
279. uest message to create a protest for CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save e CBGPROON_NEW Res Full This is the response message which is sent back to the external system when a protest for CB contract is created 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 CBGPROON_NEW Res PK This is the response message which is sent back to the external system when a protest for CB contract is created 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 17 9 CBGEXTON NEW This is the operation code is to create an extension for CB contract It involves the following messages e CBGEXTON_NEW Reg Full This is the request message to create an extension for CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Full screen which 6 97 ORACLE 6 2 17 10 includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CBGEXTON_NEW Req lO This is the request mes
280. ull screen which includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE front end screen CBDTRONL_MODIFY Req lO This is the request message to modify CB contract An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDTRONL_MODIFY Res Full This is the response message which is sent back to the external system when CB contract is modified 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 CBDTRONL_MODIFY Res PK This is the response message which is sent back to the external system when CB contract is modified 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 CBDTRONL REVERSE This is the operation code is to reverse CB contract It involves the following messages e CBDTRONL_REVERSE Req Full This is the request message to reverse CB contract An external system which intends to save payment details 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 cor
281. urred 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 arecord 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 7 2 ORACLE The following chart will depict a clear picture of request information that pass on to the various stages t
282. used to save CBDCCMNT_NEW Res Full This is the response message which is sent back to the external system when a new collection center record is created 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 CBDCCMNT_NEW Res PK This is the response message which is sent back to the external system when a new collection center record is created 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 CBDCCMNT EXECUTEQUERY This is the operation code is to query collection center record It involves the following messages 6 2 17 16 CBDCCMNT_EXECUTEQUERY Req Full This is the request message to query collection center record An external system which intends to save payment details 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 CBDCCMNT_EXECUTEQUERY Req lO This is the request message to query collection center record An external system which intends to save payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to sav
283. uthorizing an External Service CExtService Auth Res Full This is the response message which will be sent back to the external system when an External Service is successfully authorized in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen CExtService Auth Res PK This is the response message which will be sent back to the external system when an External Service 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 an External Service record in the Oracle FLEXCUBE data store CExtService Auth Flt This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to authorize an External Service fails due to any functional error CloseCExtService This is the operation code to close an External Service It involves the following messages 6 2 8 22 e CloseCExtService Req Full This is the request message to close an External Service An external system which intends to close an External Service 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 CloseCExtService Req lO T
284. verse a cheque protest transaction An external system which intends to reverse cheque protest 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 6 33 ORACLE 6 2 6 13 e ReverseChkProtContract Req lO This is the request message to reverse a cheque protest transaction An external system which intends to reverse CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query ReverseChkProtContract Res Full This is the response message which is sent back to the external system when a cheque protested transaction is reversed 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 ReverseChkProtContract Res PK This is the response message which is sent back to the external system when a cheque protested transaction is reversed The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store QueryChgProtTxn This is the operation code to reverse a cheque protest transaction It involves the following messages 6 2 6 14 e Quer
285. vice 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 FCUBS lt Acc 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 7 4 ORACLE 7 3 9 FCUBSIL Service The operations that are supported under FCUBSIL services are Close ILSweep Delete ILSweep Query ILSweep Modify ILSweep Create ILSweep Close ILGroup Delete ILGroup Query ILGroup Modify ILGroup Create ILGroup 7 3 10 FCUBSLC Service The operations that are supported under FCUBSLC services are Create LCContract Modify LCContract 7 3 11 FCUBSFX Service The FCUBSFX services support the Create FX Contract operation 7 3 12 FCUBSCG Service The FCUBSCG services support the Create Stop Payment operation 7 3 13 FCUBSSwitch Service The FCUBSSwitch services support the Switch Transaction operation 7 5 ORACLE 8 1 Function ID List 8
286. vice details are maintained 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 16 FCUBSCLService All the operations that can be performed on Retail Lending module are logically grouped under a service called FCUBSCLService Oracle FLEXCUBE supports the following operation codes under this service 6 2 16 1 QueryPayment CreatePayment DeletePayment ReversePayment ModifyAccount CreateAccount QueryAccount CreateVami QueryProduct QueryCllnfo CreateDisbursement QueryDisbursement DeleteDisbursement ReverseDisbursement QueryPayment This is the operation code is to query payment details It involves the following messages QueryPaymentDetails Req Full This is the request message to query payment details An external system which intends to query payment details 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 6 87 ORACLE 6 2 16 2 QueryPaymentDetails Req IO This is the request message to query payment details An external system which intends to query payment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query Que
287. volves the following messages e CloseDCMaster Req Full This is the request message to close card details An external system which intends to close card details 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 6 54 ORACLE 6 2 8 16 e CloseDCMaster Req lO This is the request message to close card details An external system which intends to close card details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query CloseDCMaster Res Full This is the response message which is sent back to the external system when card details are closed 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 CloseDCMaster Res PK This is the response message which is sent back to the external system when card details are deleted The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store DeleteDCMaster This is the operation code to delete card details It involves the following messages 6 2 8 17 e DeleteDCMaster Req Full This is the request messag
288. when disbursement details are maintained 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 ReverseDisbursementDetails Res PK This is the response message which is sent back to the external system when disbursement details are maintained 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 17 FCUBSCBService All the operations that can be performed on collection bills module are logically grouped under a service called FCUBSCBService Oracle FLEXCUBE supports the following operations under this service CBDTRONL_NEW CBDTRONL_EXECUTEQUERY CBDTRONL_DELETE CBDTRONL_AUTH CBDTRONL_MODIFY CBDTRONL_REVERSE CBGPMTON_NEW CBGPROON_NEW CBGEXTON_NEW 6 93 ORACLE 6 2 17 1 CBGCLOON_NEW CBDAGMON_NEW CBDAGMON_EXECUTEQUERY CBDAGMON_MODIFY CBDCCMNT_NEW CBDCCMNT_EXECUTEQUERY CBDCCMNT_MODIFY CBDCLMNT_NEW CBDCLMNT_EXECUTEQUERY CBDCLMNT_MODIFY CBDNRMNT_NEW CBDNRMNT_ EXECUTEQUERY CBDNRMNT_ MODIFY CBDDLMNT_ NEW CBDDLMNT_ EXECUTEQUERY CBDDLMNT_MODIFY CBDDSMNT_ NEW CBDDSMNT_ EXECUTEQUERY CBDDSMNT_MODIFY CBDLOMNT_ NEW CBDLOMNT_ EXECUTEQUERY CBDLOMNT_ MODIFY CBDPRMNT_ EXECUTEQUERY CBDRQMNT_ NEW CBDRQMNT_ EXECUTEQUERY CBDRQMNT_ MODIFY CBDTRONL NEW This is the operation code is to create th
289. y which has only those fields that can be used to query e DeletelnterestAdjustment Res Full MSG This is the response message which is sent back to the external system when interest adjustment is deleted 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 DeletelnterestAdjustment Res PK MSG This is the response message which is sent back to the external system when interest adjustment is deleted 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 14 FCUBSILService All the operations that can be performed on Integrated LM module are logically grouped under a service called FCUBSILServic Oracle FLEXCUBE supports the following operation codes under this service e CreatelLSweep e DeletelLSweep e ModifylLSweep 6 2 14 1 CreatelLSweep This is the operation code to create account structure for sweep for branch account product and next liquidation date combination It involves the following messages e CreatelLSweep Req Full MSG This is the request message to create account structure for sweep An external system which intends to create account structure for sweep has to send the request in the format specified The format of the message is called Full screen which includes all the
290. y Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store LEXCUBE data store 6 35 ORACLE 6 2 6 17 CloseDocException This is the operation code to close new clearing retention exception maintenance It involves the following messages e CloseDocException Req Full This is the request message to close clearing retention exception maintenance An external system which intends to close clearing retention exception maintenance 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 CloseDocException Req lO This is the request message to close clearing retention exception maintenance An external system which intends to close clearing retention exception maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e CloseDocException Res Full This is the response message which is sent back to the external system when clearing retention exception is closed 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 CloseDocException Res PK This is the response message which is sent back to the
291. y the external system 3 2 ORACLE 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 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 3 1 1 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 GWSEXSY S in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button External System Summary Authorization Status External System Dead Letter Queue Records per page nlla e 41 2 gt I mi Authorization Status Record Status External System Default Response Queue Dead Letter Queue 222200 Authorization Status A Authorized U Unauthorized Record Status C Closed O Open Record Status Default Response Queue Q Search Advanced Search Reset This summary screen can be used to search for external systems which match the data specified for any of the following criteria Authorization Status External System Dead Letter Queue
292. y those fields that can be used to query e CreateCollectionCheque Res Full This is the response message which is sent back to the external system when a collection cheque transaction is created 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 CreateCollectionCheque Res PK This is the response message which is sent back to the external system when a collection cheque transaction is created The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 41 ORACLE 6 2 6 30 QueryCollectionCheque This is the operation code to query a collection cheque transaction It involves the following messages 6 2 6 31 e QueryCollectionCheque Req Full This is the request message to query a collection cheque transaction An external system which intends to query a collection cheque 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 e QueryCollectionCheque Req lO This is the request message to query a collection cheque transaction An external system which intends to create a collection cheque transaction has to send the request in
293. yChqgProtTxn Req Full This is the request message to query a cheque protest transaction An external system which intends to query cheque protest 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 QueryChqProtTxn Req lO This is the request message to query a cheque protest transaction An external system which intends to query CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query QueryChaqProtTxn Res Full This is the response message which is sent back to the external system when a cheque protested transaction is queried 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 QueryChaqProtTxn Res PK This is the response message which is sent back to the external system when a cheque protested transaction is queried The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store CreateDocException This is the operation code to create new clearing retention exception maintenance It involves the following messages e Cre
294. yment details has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to save CBDAGMON_NEW Res Full This is the response message which is sent back to the external system when a new CB agreement is created 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 98 ORACLE 6 2 17 12 CBDAGMON_NEW Res PK This is the response message which is sent back to the external system when a new CB agreement is created 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 CBDAGMON_EXECUTEQUERY This is the operation code is to query CB agreement It involves the following messages 6 2 17 13 CBDAGMON_EXECUTEQUERY Req Full This is the request message to query CB agreement An external system which intends to save payment details 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 CBDAGMON_EXECUTEQUERY Req lO This is the request message to query CB agreement An external system which intends to save payment details has to send the request in the
295. ystem maintenance in set as Primary Key e CloseSTTrnTax Fit This XML message indicates the error response generated by Oracle FLEXCUBE when the processing of request to close a transaction tax fails due to any functional error 6 2 8 10 ReopenSTIrnTax This is the operation code for reopening a transaction tax in Oracle FLEXCUBE It involves the following messages e ReopenSTTrnTax Req This is the request message to close a transaction tax in Oracle FLEXCUBE UBS An external system which intends to reopen the transaction tax 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 transaction tax 6 52 ORACLE 6 2 8 11 ReopenSTTrnTax Res Full This is the response message which will be sent back to the external system when a transaction tax is successfully reopened in Oracle FLEXCUBE UBS The format of the message is called Full screen response will includes all the fields input fields and the display fields as in the corresponding Oracle FLEXCUBE screen ReopenSTTrnTax Res PkK This is the response message which will be sent back to the external system when a transaction tax 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 transaction tax record in the Oracle FLEXCUBE data store Note This response wi
296. ystem which intends to reopen CG product maintenance 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 ReopenCGProductMaint Req lO This is the request message to reopen a CG product maintenance An external system which intends to reopen CG product maintenance has to send the request in the format specified The format of the message is called Input only which has only those fields that can be used to query e ReopenCGProductMaint Res Full This is the response message which is sent back to the external system when a CG product maintenance is reopened 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 ReopenCGProductMaint Res PK This is the response message which is sent back to the external system when a CG product maintenance is reopened The format of the message is called Primary Key response which includes only the primary key fields of the record in the Oracle FLEXCUBE data store 6 32 ORACLE 6 2 6 10 QueryCGProductMaint This is the operation code to query a CG product maintenance It involves the following messages 6 2 6 11 e QueryCGProductMaint Req Full This is the request message to query a CG product m

Gateway Functions User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents