Clearing Interface Version-11.1 9NT1368
Contents
1. ooceeceeeennnnnsnssssssssssrsssrsssssrrsssrsrnree 2 4 2 1 4 Mapping sub nodes with the corresponding nodes in the External System een 2 9 A Es Maintaining Clearing Msg Group eeesseseesnnnnnnnnnnnnnnrnrnnrnrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrens 2 13 ee AVES A ERAND e E E E E N E E E E aie 2 18 2 3 MESSA E OIDs coop sec osa E E E E E E E E E E 2 21 2 3 1 Viewing the details of Files that were HANded Off ccc cece EEE EEE 2 22 24 PROCESSING BOR Wie INTERFACE arise este protic stnasguseberted on a EE 2 23 2 4 1 INCOMING Message PLOCCSSING cccccccccccceccccce cece ieee cece ee EEE EEE EEE ELLE EEE EEE EEE EEE EEE E GEESE EEE EE daa 2 23 2 4 2 Outgoing Message od ROLL ALY 1 ce 2 23 25 TRIGGERING THE IC CLEARING BATCH PROCESS ce jepscemciinssbncamerssseasiqshiesticesnenrssduhsiviceimarrsiasbartevsuacrtnssbaioies 2 24 ORACLE 1 About this Manual 1 1 Introduction This manual is designed to help acquaint you with the interface between Oracle FLEXCUBE and the relevant clearing networks Placing the cursor on the relevant field and striking the lt F1 gt key on the keyboard can obtain information specific to a particular field 1 2 Audience This manual is intended for the following User User Roles Back office data entry Clerks Input functions for maintenance related to the interface Back office Managers Officers Authorization functions 1 3 Acronyms and Abbreviations Unless a2. Transaction Group BAN KIRO File Mame ABCD TxT Contract Details Product Cust Cust Fey Tan Exchange Cpt Cpty Contract Ref No Code Cust No AcAho Acer Amount Amount Rate Ac Mo Mame poit DD993360011 E CDE Mic HUS23 000001 Pc T a p oo0000000 fex 0NCAFag 36000 CRE fvICHUS23 fo jagd F E B fe OOOCRFSS 3360003 CRE MICHUS23 fo gaii F CT E L Prey OOOICRFSS3360004 CRE fviCHUS23 pom fPcr f2 few De Sn a E a ee are ELLIE F F pa pacar CRE Moa bon pcr B ae ee fonooarFsssae0002 icHus23fooooor pao moO TO B Fe ig Armount Total f 0000 Account Total fi o0000000 a a L L f x The following details will also be available e Network the name of the network to which the file is hand off is triggered e Transaction Group the clearing message group for which the hand off is taking place e File Name The name of the hand off file in ASCII format e Amount Total the sum total of the amount involved in all the transactions that are handed off e Account Total the sum total of all the accounts in the transactions The account number is anumeric value The system will add the account numbers involved in each transaction to display this value On confirmation click the Ok button of the details displayed in the Dispatch screen the upload file gets created in the path specified The system will then move the file from the wip area to the out folder Pri
3. 2 11 ORACLE Condition lf the tag value is null the default value associated with the tag will be used else the value will be translated based on your maintenance in the Translation screen Result If the tag value in the external tag is Dollar during upload the system will translate this value to USD Similarly or hand off USD will get translated to Dollar If the Tag Value is Null the default value GBP will be used Case V If you select the option Null returns Null else translate Condition If the tag value is Null the Tag Value will be retained as Null If the value is present it will be translated Result Since the Tag Value is Dollar it will be translated to USD for upload For hand off the tag value will be translated to Dollar Suppose the Tag Value is Null it will be retained as null Case VI If you select the option Derivation Logic To recall you use a derivation logic if for an external tag there is no corresponding tag in Oracle FLEXCUBE The logic is identified by a unique UDF User Defined Field You will need to map the name of the corresponding UDF to the external tag During handoff the system will associate the value obtained from the derivation logic maintained for the associated UDF Case VII If you select the option System Element The external tag will inherit the value of the system element to which it is mapped Data Type In addition to mapping the Oracle FLEXCUBE tags with
4. that would be used to indicate the beginning of a new record within the ASCII file For instance let us assume that you have specified the following details e Key Start Position 1 e Key Length 3 e Record Separator 210 Consequently while processing data the system will differentiate between one record and the next only after verifying whether the first three characters of the record is three characters in length and is 210 Given below is a sample of how record separators are used to distinguish between details of one contract and another 210 O0O1220 2953690001904 064 55 211 OGOOOOO0S 0400208 715 40004 00000546 l2 O0148se1l0 O0022000 14047 O02 21s QOOOOOO0O000000 e 2000000000 1404204 093860 401TG Q 4EUREUR OOOOO00068699s QOO0000s 0400 225 AKBANE INTERNATIONAL NV 226 MAMAK 235 PATER BLEIJSSTRAAT 57 2536 43486 AM O85 210 OO1220 F2 936900011 21605 211 GOOOOOS 00000208 05 40004 O0000546 l2 O0416610 00022000 d24s62 O02 els QOOO0O00000000 2 2QOQOO0000 1236204 054240501TG f4EUREUR OOOOOO1T1LO1S55 OOOoOo O0000 2245 AKBANK INTERNATIONAL NV 220 DEMIR HOLLAND BY 235 VENRAYSEWEG 120 B 236 5928 RH WENLO 240 BEYOGLU LTD MERSIN T RKEI 210 OOL2Z20 295 59000828 729561 Going by our example in the sample shown above the details from line 1 to line 10 are construed to be details of a single record or contract The details available from line 11 to 21 will be treated as a second record contra
5. Error File Transaction Batch Msg Network FileName Branch Contract Stat Dir geg Group Date Time Cust AcctHo CustNo Count Count A eorom OO wo Roum m ca T b b INTERPeBETOPOOIS T Ph Roum p oecass CO b b nrerPeperoroonsi se fof Merouri fpi pec rsa J h b INTERPABETOPDO sf Peil C e E E E L T E interre pook Disraf T PAI ferou To a You can either choose to view the details of files with a particular status or view the details of all files that were handed off The details of each file within a network will be displayed in a different color depending on its status For instance a file with errors will be displayed in red Double click on a file to view the details of contracts included in it EN Contract Details Dispatch Details File Name BOOK_DISPATCH Contract Details Cust Cust Fey Txn Exchange Cpty Cpty Cust LCF eae Banio CustNo AcNo AcBm Amount Amount Rate Ac No Name Ac No FROCRIAS934200 FIBA Naca NAGAA pa for _Jooo0ooo00o7eeain AIRTE oO00000000706NA A pacas FIBA pacan NAGAA pa o mus Jooooooo0007eeaim AIRTE 0000000000786NA pacas FIBA INATROT NATRA 53 B00 JNoooooo0007eeaim AIRE 0000000000786NA pacas FIBA NATROT NATRA 53 B55 Joonooooo0o7eeaim AATE Jooooon0000706Na pacas FIBA NATROT NATRA 533 B58 Joooooooooo7eeaim AATE ooooon000076na FROCRIAS34200 FIBA Nara NATRA a3 Bs oooooooo0o7eeaim AATE ooooong000706na SCRIAGS34200 FIBA NATROT NATRA paa bss Jt
6. The Oracle FLEXCUBE Clearing Gateway is the common channel for data exchange between Oracle FLEXCUBE and the local clearing networks applicable The ACH Network is an electronic payments network used by individuals businesses financial institutions and government organizations Electronic ACH payments provide better cash management capabilities and lower costs than traditional paper payments Both funds and information may be exchanged between financial institutions on behalf of companies and individuals utilizing electronic payments The ACH Network allows funds to be electronically credited or debited to a Company or individual s deposit account Currently these deposit accounts include checking savings loan and financial institution general ledger accounts The following information can be transmitted through ACH transactions e the name of the account holder e the financial institution s routing number e the account number involved in the transaction e the party initiating the transaction and the amount e the date of the transaction A Data Diagram which illustrates the work flow o Authorizer Originator Receiver EE EEE ee Automated Clearing House ee ey ODFI Originating RDFI Receiving Depository Financial Depository Financial Institution Institution ey A The data exchange of messages will be in the form of ASCII file formats For the interface to function effectively you need to maintain certain basic info
7. fcc area as backup Once in the wip area the contents are resolved and the database gets populated with the actual values Subsequently the details of all the contracts are displayed in the Dispatch Details screen You can invoke the Dispatch Details screen by typing IFCLRBWR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button TA Dispatch Details Dispatch Details Nework MERN Transaction Group BANKGIRO File Mame ue COTAT Contact Details Gusi Cust F r Ten Exchange Cpt Cpt eitle Fasule eau 4c Wo w Am Anvount Amount Raie Ac Ho Mame NOC DD SS3360011 GE z3 pom Fc k P0000000 pacara CRE posa poo rry fo E fer SS PPP BE ne ara piochs CRE PCHUSZ pawo eT fff Bi Y pouch PERE CHUS poi FPT E I BPE w JOOOICRF3sa360007 jeme ficnusz3 pom Fret if f B e a 2 ee a E E E pocas fene Mosa foots TCP Boo i e E e ts E E E _ essa pow Pelf P B pw Amount Total 1 0000 Abtan Total 1 OO00D000 I 4 gt e y x 2 21 ORACLE 2 3 1 Viewing the details of Files that were Handed off You can view the details of all files that were handed off through the Status Browser screen You can invoke the Status Browser screen by typing IFCLRBWR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button PN Status Browser Status M an Processed Working C Dispatch C
8. the Oracle FLEXCUBE tags that belong to it e CONTRACT REF NO e BRANCH_OF_INPUT e CUSTNO e CPTY_NO e CUST_AC_NO Therefore you need to maintain the following mappings CONTRACT NUM CONTRACT REF _NO BRANCH BRANCH _OF_INPUT CUSTOMER CUSTNO o If for an external tag there is no corresponding Oracle FLEXCUBE tag you can use the derivation logic to obtain a value for such tags if required Indicating whether data pertaining to a specific tag should be made Mandatory You have the option of specifying whether the data pertaining to a specific information tag should necessarily be made available in the incoming outgoing message Check the box available under the column head titled Mandatory 2 9 ORACLE Specifying the Default Value You can associate a default value with each information tag While uploading or handing off messages suppose an information tag within the incoming outgoing message does not have a value associated with it the system automatically appends the default value with the particular information tag only if the translation type is set up for it Translation details for the specific Oracle FLEXCUBE and external tag combinations If you have indicated that Value Translation is required for all Oracle FLEXCUBE and external tag combinations this specification will be defaulted to all the tag mappings within the Oracle FLEXCUBE and external node combination However you have the option of changing this
9. the Message Maintenance for a given message type The file level attributes that are maintained will be picked up from File Clearing Message Type These are gt File Name gt File Extension 2 23 ORACLE 2 5 File Path Session Timeout Number of Resends Number of Transactions in a file gt Number of Transaction in a Batch Vv Vv V WV e Contracts pertaining to each product selected from the Product Mapping Clearing Message Type maintenance will be picked up for processing for the Clearing File e The sequence that is followed during the processing is File Header Records FH Message Header Records MH Message Records MR Message Footer Records MF File Trailer Records FF e The following batch totals are assumed for the trailer records Vv Vv V WV WV gt Total for Accounts gt Total of Amounts gt No of Records in the Message e Each record is locked before the data in the record is processed e If the record is locked successfully then the details of the record are passed on to the Business Rule layer to update the record to the dispatch status e Based on the flag passed from the Business layer the message is formatted on the basis of the maintenance done e A preset number of contracts is processed and committed and written to the file based on the maintenance done e After all the contracts are processed the file is moved to the area specified in the maintenance The above processes are
10. the external tags you should also specify the type of data for each tag The Data Type indicates the nature of the data whether it is numeric or a character format The following options are available e CHAR e NUMBER e DATE and e TIME Start Position and Data Length To differentiate the data of one tag from another you will need to indicate the position from where a particular tag begins The length of the data within the tag should also be captured 2 12 ORACLE For instance let us assume that you have specified the following details e Tag 1 gt Start Position 1 gt Data Length 10 e Tag2 gt Start Position 11 gt Data Length 10 As a result while processing data the system will identify the first 10 characters as Tag 1 and the next 10 characters 11 to 20 for Tag 2 Derive Type For an external tag if you choose the translation option as Derivation Logic you have to map it to the corresponding UDF name You would have already maintained the UDF in the Derived UDF Maintenance screen The external tag will get the value based on the logic that you have maintained for the selected UDF All the UDFs that you maintain in Oracle FLEXCUBE will be available in the drop down list You can select the appropriate one from the list System Elements If you need to hand off the system Oracle FLEXCUBE derived values you have to select the translation option System Element Further you are
11. Clearing Interface Version 11 1 INT1368 ORACLE FCUBSV UM 11 1 0 0 0 0 0 August 2010 Oracle Part Number E51575 01 ORACLE FINANCIAL SERVICES ORACLE Document Control Author Documentation Team Group UBPG re Created on October 01 2008 Revision No Final Oe Updated by Documentation Team Reviewed by Development Approved by Software Quality Testing teams Assurance Team Updated on August 06 2010 Reviewed on August 06 Approved on August 06 2010 2010 Clearing Interface 1 Table of Contents ABOUL THIS Ph OP Peer cre rr re rrr rrr cr err rrr rr cr ery rrr rrr rr rrr rr cerry rrr rr cy errr 1 1 1 1 WODE O r E T E E A doc l 1 e AN e A E E E E E E E ER l 1 l3 ACRONYMS AND ABBREVIATIONS css sec ste eesmise sE ne E EE E ES S l 1 R ORG INO E A mc nce ga cee ests ee l 1 1 5 CONVENTIONS USED IN THIS MANUAL aco sisseeteg conttesaserecscceeineies th eeetcenes cette e E l 1 LO GLO AT OPT OON e A E E E ee ede tee 1 2 b RATO DOCOMEN ic ee eee eee ene E A ee 1 3 THE ASCH CLEARING TN TERRE A CB iacssosaressstacesesseseneeiceeessssevesastasuveuevanluesds iaveuseeicessetueceussesanestatesssasaisaiels 2 1 2 1 SUTTON ecstasy geese o ese sa reece AEE A O EE cnc E E OE EAEE 2 1 21 1 Maintaining Clearing Transaction Types ccccseptcsicieaniiuisaiisapisaatadadtaninstsueasnatuntapieaniiaskttensiumteaniendenientts 2 2 2 1 2 Manann oder ved UDT ne me re ee een EARE AEREN 2 3 2 1 3 Maintaining Transaction Type hand off file formats
12. Path Dispatch Grouping By Clearing Message Type v x For message hand off you need to select the network and the clearing message group as mandatory information Additionally you can also specify one or all of the following options for hand off e Single Branch if you want to hand off messages from a specific branch for the selected network and message group combination You can select the branch from the option list available e Single Customer if you want to hand off transactions for a specific customer for the selected network and message group combination choose the name of the customer from the option list provided Transactions involving all the accounts of the selected customer will be handed off e Single Account select this option if you want to hand off transactions involving a specific customer account for the selected network and message group combination You can select the account from the option list provided e Single Contract will hand off details of a specific contract If you select only the network and message group the system will hand off all the contracts irrespective of the branches customers and accounts involved for the selected combination For hand off you should also specify the following File Path You can also specify the path for storing the hand off file When you trigger the process the hand off file will be picked up from the path you specify here If you do no
13. also required to map the external tag with a system element The set of system elements are available in the drop down menu You can select the appropriate element to map to the external tag For instance the clearing network may want you to hand off transactions that were entered in Oracle FLEXCUBE on a specific calendar date System Date the current date as shown in your machine The Oracle FLEXCUBE date may be different from the current system date Therefore you will need to map the external tag say Date to the system element SYSDATE The hand off file will contain the actual date of the transactions Maintaining Clearing Msg Group Transaction types having common attributes should be grouped together into Clearing Message Groups for ease of processing For each clearing message group that you maintain you will need to define a set of uniquely identifying specifications These specifications will determine the parameters for the manner in which contracts also referred to as records are arranged within ASCII files Invoke the Clearing Msg Group Maintenance screen from the Application Browser to group transaction types into clearing message groups You can invoke the Clearing Msg Group Maintenance screen by typing IFDTXNGR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 13 ORACLE 0 Clearing Fsg Group Maintenance em Cleaning Mag Group z rr Netwo
14. also responsible for converting the data formats and tag formats from the Oracle FLEXCUBE standard format to the formats as required by the external systems The above set of processes also translates the fields that require a translation as per the maintenance for the particular interface Triggering the IC Clearing Batch Process The IC Clearing Batch Process is triggered after the IC End of Day batch process has been executed During the Clearing batch process the system picks up all interest liquidation accounting entries for the IC module for an IC bridge account and uploads them as Outgoing Payments in the PC module You can trigger the IC Clearing batch process through the IC Clearing Batch Process screen You can invoke the Clearing Batch Process screen by typing IFICBAT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 24 ORACLE H Clearing Batch Process IC CLEARING BATCH PROCESS In addition to creating Outgoing Payments for all interest liquidation entries this process also handles principal and interest liquidation to CASA accounts 2 25 ORACLE ORACLE Clearing Interface August 2010 Version 11 1 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores CA 94065 U S A Worldwide Inquiries Phone 1 650 506 7000 Fax 1 650 506 7200 www oracle com financial_ services Copyright 2010 Oracle Financ
15. ct and so on 2 15 ORACLE Specifying the Masks and other attributes of the File The File Mask is the nomenclature in which the external system names the ASCII file You will need to capture the corresponding Process File Mask which is the format in which you have named the file in Oracle FLEXCUBE Example File Mask BETOPD04 Process File Mask BETOPD d t d is the date t denotes the time and indicates a running serial number If you check the Use Process File Mask box the external system will name the ASCII file based on the file mask specified for Oracle FLEXCUBE File Extension In addition to specifying the file masks you have to indicate the manner in which each file is to be stored Typically you can store these files with a btc extension However you have the choice of specifying any extension you wish to generate these files in File Path The file path is the directory or area in your system where the ASCII files are to be stored Field Separator You have the option of using delimiters to separate data within a file The options available are e S indicating that a space needs to be used as a delimiter e S T indicating that a tab needs to be used as a delimiter Alternatively you can also choose to have a comma a semi colon a hyphen etc Clearing Message Type Separator To recall in this screen you are grouping clearing transaction message types which share similar attribu
16. e and subsequently writes the calculated value from the length starting position maintained for the particular message group e Starting Position This field indicates the position from which the calculated value has to be written into e Length This indicates the length for the line Example Let us assume that the length of the transaction line is about 300 The line attributes indicated are e Start position 6 e Length of position 5 The calculated value will be 300 and positions 6 to 10 will denote the length of the line Oracle FLEXCUBE automatically writes the calculated value from position 6 to 10 as 00300 Message Handoff For the actual message hand off you have to manually trigger the event from Oracle FLEXCUBE You also need to specify the network and the clearing message group for which the hand off file has to be created This file in ASCII format is eventually handed off by Oracle FLEXCUBE You can trigger the message hand off event through the Dispatch Details screen invoked from the Application Browser You can invoke the Dispatch Details screen by typing IFHFDETS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 2 18 ORACLE HN Dispatch Details Dispatch Details Network D Wisg Group OoOo O P Single Branch Branch E Single Custarnmiet Customer Oooo T P Single Account Account feel M Single Contract Contract cl File
17. e group You will need to specify the process attributes depending upon the process direction that you specify Outgoing attributes If you are maintaining the details of an outgoing message group you have to specify the attributes of the batch hand off file that is sent These include e Include Reject indicates whether the details of the rejected contracts need to be part of the outgoing file e Block Enabled indicates whether the outgoing file needs to be block enabled e Line Length indicate the length of a line within a block e Block Filler specifies the identifier which should be used to identify the block e Block Factor specifies the factor by which the line length should be multiplied This in turn will provide the total number of characters in the block Incoming attributes Automatic Auth if enabled indicates that the incoming file should be automatically authorized upon receipt Transaction Basis specifies the basis on which transactions are grouped in an incoming file The options available are gt Record Based 2 17 ORACLE 2 2 gt Batch Based If the records are batch based you have to capture the Batch Key Start position and the Batch Key Length to uniquely identify the batch Length Attributes e Length Check Required If you have opted for this facility in Clearing Message Type screen and also check this box here the system will calculate the length of the particular lin
18. etween the Local Payments module of Oracle FLEXCUBE to fields that are required by the network A predefined set of Clearing Message Types will be shipped along with the software You can change the default attributes of these message types to suit the requirements of your bank Network ID The Oracle FLEXCUBE Clearing Gateway is a common channel for data exchange between Oracle FLEXCUBE and the local clearing networks applicable The details of the applicable local clearing networks are maintained in Oracle FLEXCUBE You can define the process direction for each of these clearing networks through the Clearing Message Type Maintenance screen You can select the ID assigned to the Network whose tag names need to correspond with those maintained in Oracle FLEXCUBE On selection of the network from the available option list the description gets defaulted alongside Process Direction The format for hand off from Oracle FLEXCUBE is different from the format for upload into Oracle FLEXCUBE Therefore you need to indicate the process direction for which the format is being defined The options are e Incoming for upload into Oracle FLEXCUBE e Outgoing for hand off from Oracle FLEXCUBE Clearing Message Group Type Incoming message uploads formats are defined for a Clearing Message Group When you select the Incoming option the set of Clearing Message Groups supported in Oracle FLEXCUBE are made available to you in the op
19. file level For the Identifier thus derived the subsequent details are picked from the message maintenance Next the system processes each line and populates it into a row type Whenever the beginning of a new contract is found the system inserts the row type into the corresponding table with a particular flag This process goes on till the end of file is reached The following totals will be kept for each file driven by a flag Total for Debits Total for Credits Total for Accounts Total of Amounts No of Records in the Message Vv Y V V WV After processing all the records the file is moved into the fcc area All the status for the contracts uploaded will be changed for booking and these data are processed using a batch function 2 4 2 Outgoing Message Processing While processing outgoing messages the following stages are involved in the creation of Clearing files You will have to specify the File Clearing Message Type that needs to be created On initiation the system first checks if there is any recovery operation is required If required it is handled first For the given clearing message type all products for which the file needs to be created will be picked up from the Product Mapping Clearing Message Type maintenance Since it is possible for the file to have a batch grouped on an account too the system will pick up the corresponding flag for the file The system will select the relevant records from
20. for individual tag mappings by choosing the appropriate translation option from the available list The seven options available are 1 No Translation 2 Translate null returns error 3 Null returns default else no translation Null returns default else translate 4 5 Null returns Null else translate 6 Derivation Logic 7 System Elements If you select any other option apart from No Translation NULL return default else no translation Derivation Logic and System Element you will have to capture the Oracle FLEXCUBE Value and the corresponding External Value in the Translation Values screen A Translation Translation Value Flexcube Value External Value Let us assume that you are maintaining the translation details for an information tag called CCY currency The value of this tag in Oracle FLEXCUBE is USD But the external system uses Dollar for the same 2 10 ORACLE In the Translation Values screen the information that you capture will look as follows Oracle FLEXCUBE Value External Value USD Dollar The example given below illustrates the manner in which the system will behave when you choose any one of the Translation options Example We have specified the following parameters for the External Tag named CCY currency e The Translation Value for gt Oracle FLEXCUBE USD gt External System Dollar e The Default Value is GBP which is the local currency Case If you se
21. he external system specifications and vice versa 2 8 ORACLE 2 1 4 Example Assume that Oracle FLEXCUBE recognizes only USD for US Dollars The external system requires the value of US dollars as Dollar When you upload into Oracle FLEXCUBE if the value of the tag CCY is Dollar it gets translated to USD Likewise during handoff USD gets translated to Dollar However it takes place only if translation is set for the external system and Oracle FLEXCUBE tag combination Mapping sub nodes with the corresponding nodes in the External System As part of the format maintenance you need to ensure that each child tag defined in the External Node corresponds to a pre defined tag in Oracle FLEXCUBE Step After capturing the name of the External Tag of the clearing network identify the corresponding Oracle FLEXCUBE Node Step Il After you select the Oracle FLEXCUBE node the sub nodes child nodes also called child tags linked to the selected node will be displayed in the drop down list available for the Oracle FLEXCUBE Tags You can key in the appropriate external sub node belonging to the External Node specified earlier and map it to the corresponding Oracle FLEXCUBE sub node tag Example Assume that the External Node is 10 and consists of the following tags e RECORD CODE e CONTRACT _NUM e BRANCH e CUSTOMER The corresponding Oracle FLEXCUBE node is PAYMENTS COLLECTIONS and the following are
22. hould be sent within a batch Additionally you can also specify manner in which message transaction types are to be sorted The options available are 1 By Clearing Message Type 2 By Account Number If you select the second option the transactions messages will be sorted by the Account Number involved in the transaction Else the sorting will be based on the transactions themselves For instance assume there are 12 transactions within a file Out of these 12 transactions four involve the same account number and the other eight involve a different account number For the given Clearing Group you have indicated that messages should be sorted as per the Account Number As a result the details of eight messages involving the same account will be listed first and the details of the other four messages will be listed subsequently Restricting specific Clearing Transaction Type from a group A list of all the transaction types you have maintained in the system are displayed in the Available column For each Clearing Group that you define you can choose to restrict or allow specific transaction types in the form of allowed or disallowed lists Indicating the Process Direction and the related attributes A Message Group can be defined to group transaction types maintained for the upload of messages into Oracle FLEXCUBE Incoming or for the hand off of messages from Oracle FLEXCUBE Outgoing You have to indicate the process direction of the messag
23. ial Services Software Limited All rights reserved No part of this work may be reproduced stored in a retrieval system adopted or transmitted in any form or by any means electronic mechanical photographic graphic optic recording or otherwise translated in any language or computer language without the prior written permission of Oracle Financial Services Software Limited Due care has been taken to make this document and accompanying software package as accurate as possible However Oracle Financial Services Software Limited makes no representation or warranties with respect to the contents hereof and shall not be responsible for any loss or damage caused to the user by the direct or indirect use of this document and the accompanying Software System Furthermore Oracle Financial Services Software Limited reserves the right to alter modify or otherwise change in any manner the content hereof without obligation of Oracle Financial Services Software Limited to notify any person of such revision or changes All company and product names are trademarks of the respective companies with which they are associated
24. ify each clearing message group that you define with an appropriate name Additionally you can also specify a brief description to identify the group Specifying the Key Start Position and Key Length The ASCII file consists of multiple lines of messages A unique key identifies each line of data within a message You have to indicate the start position of the key and the length of the key This will help you in identifying the key in the message and subsequently in deciphering the data that follows The key actually denotes an External Node The values that appear after the key are assigned to the external tags as per the format maintained for that external node in the Clearing Message Type Group Details Maintenance screen ORACLE 2 14 Consider the sample shown below OO12 20 7 7295690001904 064 55 OOO0000s 0400208 715 000400000546 OO148s10 00024000 14042 O02 QOOOOQOO0000000 Here 210 211 212 and 213 are the keys or external nodes Each key is used to identify the line of data that follows The external tag values will be picked up from the data as per the specifications in the Clearing Message Type Group Details Maintenance screen Identify the Record Separator The details of each contract are displayed as separate records within an ASCII file To differentiate the details of one contract record from another within the file you will need to identify the key external node
25. l reject the entire contract The rejection logic will filter the contracts within the message that is being handed off During mapping you can map the external tag with the corresponding UDF name Example The external system may have a tag called Account Type A corresponding tag does not exist in Oracle FLEXCUBE Instead Oracle FLEXCUBE has a tag called Account_No Therefore to obtain a value for Account Type you can derive a logic such that if the first character of the Account No is C the Account Type would be Normal else it will be considered as a Special account Therefore when you actually hand off a message the Account Type would be associated with the value Normal or Special as the case may be You can maintain the UDFs in the Derived UDF Maintenance screen You can invoke this screen by typing IFDCLDUD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button S Derived UDF Maintenance Interface Derived UDF Maintenance UDF Name UDF Description UDF Type In coming Out going Derivation Rejection Network al n r Out Rule A Input By Date amp Time Auth By Date amp Time Mog Mo as Authorised i Open 2 3 ORACLE 2 1 3 In this screen you have to specify the following details UDF Name and UDF Description You can specify a unique name to identify the UDF A brief description can al
26. lect the option No Translation the system will not perform any translation As a result if the message involves the tag CCY with value USD both the incoming and the outgoing messages will retain the value USD Case Il If you select the option Translate null returns error Condition The tag value will be translated based on your maintenance in the Translation screen If you fail to send the corresponding value to the system i e if the value of the tag is null an error message will be displayed informing you of the same Suppose you had failed to associate a corresponding Oracle FLEXCUBE value USD for the External Value Dollar in the Translation screen the system would have displayed an error message informing you of the same You would have been allowed to maintain the record only after having maintained the corresponding translation value Case Ill If you select the option Null returns default else no translation Condition lf the tag value is null the system will not translate it However the default value associated with the tag will be used Result As stated earlier the Tag Value associated with the external system is Dollar and the corresponding tag value in Oracle FLEXCUBE is USD Let us assume that the Tag Value associated with the Tag Name CCY is Null In such a case the system will use the default value GBP Case IV If you select the option Null returns default else translate
27. lumns of data when mapped to the corresponding Oracle FLEXCUBE tag The following example will illustrate this concept In the Oracle FLEXCUBE node Cust_Add the following child tags represent the address details e Add e Add2 e Add3 e Add4 The value for each tag is required to upload or handoff the complete customer address details The External Node 211 consists of maintenance required for customer address details It consists of a single tag Address In order for the external system tag Address to hold multiple columns of data from the corresponding Oracle FLEXCUBE tags Add1 Add2 Add3 and Add4 you need to map Address with each of the Oracle FLEXCUBE tags 2 7 ORACLE To achieve this you need to create a new record in the Clearing Msg Type Group Details Maintenance for each mapping for the same combination of e Clearing Network e External Node e Oracle FLEXCUBE Node and e Format Type The external node counter will track each occurrence of the above combination The count starts from one and gets incremented by one for every new record The Format Sequence Number will also get incremented by one for the same combination of Clearing Network Format Type and Oracle FLEXCUBE Node IS Optional On occasion you may need to send additional payment information with an ACH payment by using extended record formats called addenda Addenda may include payment related information such as C
28. nd otherwise specified it shall always refer to Oracle FLEXCUBE system User Defined Fields Automated Clearing House 1 4 Organization This document talks about the maintenance required for data exchange between Oracle FLEXCUBE and the relevant clearing networks This includes the following e Maintaining Clearing Message Types e Maintaining File Formats e Maintaining Clearing Message Groups e Derived and Rejection UDF Maintenance e Message Status Browser The manual also talks about the following processes e Message hand off to the clearing network e Message upload into Oracle FLEXCUBE e Online message processing 1 5 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 Copy Save Fai Delete e oe eo Eid Template Roll over a Hold Authorize sla Liquidate Sign off ae Add row Delete Option List BE bik ORACLE Fal Execute Query Refer the Procedures User Manual for further details about the icons 1 7 Related Documents You can refer to the XML Interface document which outlines the details of the interface mechanism between Oracle FLEXCUBE and an External System 1 3 ORACLE 2 1 2 The ASCII Clearing Interface Introduction The Local Payments module supports the local clearing of payments
29. ool bar and clicking the adjoining arrow button T Clearing Msg Type Group Detail Maintenance Cleaning Mag Type Group details Network Bei al Process Direction f coming Quigoing External Mode fi ls Optional I Date Format RRMMDC Flexcube Nodes PAYWENTS COLLECTIONS E Description AUTOMATED CLEARING HOUSE Number Padding LEFT I en Penn O Alpha Padding fer M Format Type File Header Format Seq Hofi External Node Desc File Header Record External Mode Counter nH Length Check Required Value Translation fe Pie Tire Format HH PRIQDRITY_C ODE F TE FACTO O TMPI2 Jp fFORMAT_c ODE TMP F Input By Dale amp Time External Tags Flexcuba Tags Mand RECORD TPE f IMMELA T E DESTIN id Ho Translalion FILE_ID_MODIFIER ER THPAO g z Mo Translalion Date amp Time biog Mo Default Value Translation DataType Start Pos Len Derwe Type Sys Elrnts Mo Translation r CHAR li ff fi Mo Translation aif HUMBER i 2 l lcHar vila fro Ne Translation c HAR f fo t No Translation JE DATE l24 J TIME al EY MEN E li 4 4 Mo Translation le HAR 34 s mo Translation cHar S E J mo Translalion CHAR fe A Derivation le HAR jpo i DuDF1 J i d d d a a 4 si fz IY Authorised F Open ORACLE 2 4 Through this screen you can establish a mapping b
30. ooooo000078ea1m AATE 0000000000786NA pacaan FIBA NATROT Naa pa fon Joooon000078eain AATE Joooooo00007eeNa Product Code 333CR1 99342000 RIB OHNO OHNN 333 l 2001 l 0000000000786AIF BIRTE 000000000078610 233CRIN9934200 RIBN NAGADT NAGAA 333 jo 000000000078641F IRTE 0000000000786NA x rContracts Ignored Product Cust Cust Fey Txn Exchange Cpty Cpty Cust LCF diate Code Cata AcNo AcBrn Amount Amount Rate Ac No Name Ac No 2330C003933600 OCDK FARTO pne p3 fo po00000000786NA NATRAJ 0000000000786AIR Al es ee es ee ee ee ee eee as ee es ee ee es ee E SEE il ey ee i ee ee ee eee eee w 2 22 ORACLE 2 4 Processing for the Interface The interface can either be Online or in a Batch format For the online mode each contract in Oracle FLEXCUBE will be handed off as a separate file 2 4 1 Incoming Message Processing While processing incoming messages contracts are uploaded using the following process stages You will initiate the process of uploading files The system checks if any recovery operation is required If required it is handled first The file name is logged into the log table before the contents of the file are processed The file name can be used for recovery and reporting After this the entire file is read into memory in chunks The key identifier for the message is derived from the position and the number of characters maintained at the
31. or to moving the file it will retain a copy of the hand off file in the fcc area as backup This marks the successful completion of the hand off process At this stage if you want to cancel the hand off process click on Exit or Cancel button 2 20 ORACLE 2 3 Message Upload Just like the hand off process the upload process too needs to be manually triggered from Oracle FLEXCUBE You can trigger the message upload event through the Incoming Incoming File Details screen invoked from the Application Browser You can invoke the Incoming File Details screen by typing IFINDETS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button E Incoming File Details Incoming Details Network INTERPAY QJ INTERNAL PAYMENT NETWORK Clearing Msg Group HLAYOUT QJ desc File Path ftmpl v x In this screen you need to identify the network and the message group for which the message needs to be uploaded If you do not want to use the file path specified for the Message Group you can enter a different path here This path will take precedence over the one maintained for the Message Group The five folders mentioned earlier will be created in the file path specified in this screen After you trigger the upload process the system will pick up the ASCII file from the in folder and move it to the wip area It retains a copy of the file in the
32. oters batch footers and so on You can maintain a format for each occurrence of a format type within the ASCII file Format Seq No The format of an ASCII file is as shown below 2 6 ORACLE File Header Batch Header l Batch Body Batch Footer File Footer To recall a file can consist of multiple file headers batch headers file footers and so on The sequence number determines the manner in which multiple formats of the same format type appear in the ASCII file Oracle FLEXCUBE automatically sequences these formats for you If you are maintaining more than one file header format for a combination of Clearing Network and Oracle FLEXCUBE Node the sequence number will start with one and get incremented by one for each subsequent file header format External Node Just as the Oracle FLEXCUBE node represents a set of tags grouped together the external node is a unique name for identifying the set of tags belonging to the external system clearing network in this case You will need to map each tag identified by the external node to the corresponding tag belonging to the selected Oracle FLEXCUBE node You can enter a brief description of the external node in the adjacent field External Node Counter Multiple occurrences of the same External Node for a network and format type combination are tracked by means of an external tag counter This is required if a single external tag has to hold multiple co
33. rk id RS al INTERNAL REVENUE SERVICE Clearing Msg Group Li a Group Description IRS Outgoing Message Group Key Start Position Fite Atiributes File Wask TE Usa Process File Mask D FilePath fimpileml Record Separator Session Timeout Hantot Parameters Bateh Count Hando Grouping By Clearing Message Type Process Direction Incoming Incoming Atribuies 3 Automatic Auth T Ouigoing Atripulas Block Enabled Block Filler Length Atributes Length Check Required Available Key Length File Extension hr Process FileMaskjRseere Fiad Separator Clearing Meg Type Separator Resend ouni Massage Court include Reject Tran acilon Basis Batth Key Length Line Length e _ Block Factor Staring Position Length Allowed Description Clearing Meg Types Deseriplon r IRS pie Message Te O Type a a Clearing Msg Troes Indicating the Network ID In the Clearing Networks screen you can maintain the networks Such as INTERPAY and HLAYOUT through which you communicate with other banks and financial institutions for local currency funds transfers You can identify the Network ID for which you are grouping transaction types When you select the relevant Network ID from the available option list the associated description will be defaulted to the adjacent field Identifying the Clearing Message Group You will have to uniquely ident
34. rmation in Oracle FLEXCUBE This includes the following 2 1 ORACLE e Maintaining Clearing Transaction Types e Maintaining Interface hand off file formats for individual transaction types e Maintaining Clearing Transaction Groups for transaction type 2 1 1 Maintaining Clearing Transaction Types A Clearing Transaction Message Type is a Payment Order belonging to a Transfer Category These Clearing Message Types Categories will be specific to the Network example BankGiro etc You can maintain the clearing message Type Category details through the Clearing Message Type maintenance screen You can invoke this screen by typing IFDTXNTY in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button ite Clearing Message Type Maintenance learing Meg Type Maintenance Network INTERPAY INTERPAY NETWORK Clearing Msg Type BANKGIRO Description BANKGIRO DESCR Process Direction Incoming C Outgoing roduct Categories Description Description Reject of Outgoing Goa S Recall of Outgoing Ca Inout By Date Time Auth By Date Time Mod Mo faon 1 DEC 1999 14 24 07 fi e Open P Authorised In this screen you can capture the following attributes about the clearing message Type Category e Network ID a valid network code from a pre defined set of Network Codes For instance you can define a network code called INTERPAY e Clearing Message Type a valid name to identify
35. s and the value will be displayed as 0000000100 Alpha Padding Direction Similarly you have to select the padding character for the alphanumeric fields in Oracle FLEXCUBE You also need to indicate the padding direction for the same Normally for alphanumeric fields you would choose to pad to the right of the actual value Oracle FLEXCUBE Nodes Just like in Oracle FLEXCUBE the clearing network too may have a set of its own Tag definitions Consequently it becomes necessary to maintain a mapping between the information tags within Oracle FLEXCUBE with those required by the clearing network The Oracle FLEXCUBE node represents a set of tags grouped together It is known as the parent node record from which the sub records sub nodes tags are derived for mapping to the external tags Format Type As stated earlier the messages that are handed off and uploaded into Oracle FLEXCUBE are in the ASCII file format An ASCII file consists of the following sections in the order specified 1 File Header Batch Header Batch Body Batch Footer LP amp wD File Footer You can maintain a format for each section of the ASCII file The file header marks the beginning of a file Every batch begins with a batch header and ends with the batch footer The batch body is the actual content of the message that is being handed off or uploaded The file footer marks the end of the file A file can consist of several file headers file fo
36. so be provided in the adjacent field UDF Type Additionally you should also specify the type of the UDF being defined whether you are writing a logic to derive a tag value or for filtering the transactions in a message file based on a rejection criteria Network Specify the network for which you are writing the derivation rejection logic To execute the logic click on the X button If you encounter any error during execution you can view the same by clicking on the E button Make the necessary corrections before you re execute the logic The UDFs defined through this screen will be available in the drop down menu of the Derive Type field in the Clearing Message Type Group Details Maintenance screen This is discussed in the section that follows You can maintain only 25 derived logics UDFs for all the networks that are applicable for data exchange with Oracle FLEXCUBE Likewise you can maintain only one rejection logic per network Maintaining Transaction Type hand off file formats Each network and clearing message type category has a fixed format that needs to be handed off from or uploaded into Oracle FLEXCUBE Therefore you will need to specify the format in which data is to uploaded and handed off You can do this through the Clearing Message Type Group details maintenance screen You can invoke this screen by typing IFDTXNDT in the field at the top right corner of the Application t
37. t specify a path the file will be picked up from the path specified for the selected message group o At the time of implementation of Oracle FLEXCUBE the implementer will create the following five folders in the file path that you specify in the Handoff of Clearing Details screen if not specified the folders will be created in the path maintained for selected message group e in folder e out folder e wip folder work in progress 2 19 ORACLE e fccarea folder for Internal logging e debug folder Handoff Grouping You also have the option of grouping the transactions within the hand off file The following options are available for grouping e By Clearing Message Type if you select this option the transactions will be grouped as batches of different clearing message types that are allowed for the selected clearing message group e By Account Type this option will do the grouping based on the customer accounts involved in the transactions All contracts involving a specific customer account will be grouped under a single batch file After you trigger the hand off process the system will pick up the relevant tag values for all the transactions from the database table and display the contents of the hand off file in the Outgoing Message Browser Dispatch Details screen The contracts that are rejected or have encountered an error will be highlighted in RED WA Dispatch Details Dispatth Details Network i i
38. tes You have the option of differentiating messages within a group with delimiters Session Timeout The session timeout is the maximum time limit that Oracle FLEXCUBE will wait for a response to a request sent to the external system You can indicate in terms of minutes the time within which an outgoing file should be processed by the External System and sent back to Oracle FLEXCUBE Each time the external system fails to send a response to a request sent by Oracle FLEXCUBE within the maximum time limit maintained Oracle FLEXCUBE will recreate the message and send it to the external system again You can maintain a count for the number of times a message can be resent Resend Count An outgoing message can be resent any number of times You have to indicate the resend count in this field As a result all messages for the given Network ID and Clearing Message Group combination can be resent only the specified number of times For instance you have indicated 3 as the resend count A specific message has failed to parse through all three times Since the resend count has been busted you will not be able to send the message one more time The message will be logged as an error message 2 16 ORACLE Specifying the Handoff Parameters Since a single hand off file can have multiple batches you can indicate the number of batches that should be sent in a single file Similarly you have to indicate the number of transactions messages types which s
39. the clearing message type which is to be associated with the Network ID You can also capture a brief description to identify the clearing message type e Process Direction specify whether the payment order which you are defining belongs to the Incoming transfer order or whether it belongs to the Outgoing transfer category e Product Category Product Restriction If the process direction of the transaction type which you are defining is Incoming you will associate existing PC Product Categories with each transaction type Conversely if the process direction is Outgoing you will need to associate existing PC Products with each transaction type You can specify product category product restrictions in the form of allowed lists or disallowed lists 2 2 ORACLE 2 1 2 Maintaining derived UDFs As part of maintenance you have to establish a mapping between the Local Payments module of Oracle FLEXCUBE to fields that are required by the clearing network In other words Oracle FLEXCUBE tags are mapped to the corresponding external system tags Sometimes you may not find a direct relationship between an external system tag and the Oracle FLEXCUBE tags For such tags with no corresponding tags in Oracle FLEXCUBE you can define an UDF User Defined Field and obtain a value by writing derivation logic Likewise you can also write rejection logic If a particular contract in the hand off message satisfies the rejection criteria the system wil
40. tion list provided Select the appropriate Group from the list The format will be applicable to all product categories belonging to the transaction types linked to the selected Message Group Likewise outgoing message hand offs formats are defined for a Clearing Message Type On selection of the Outgoing option all the Clearing Message Types supported in Oracle FLEXCUBE become available in the option list provided The outgoing message forma Oracle FLEXCUBE t being defined will be applicable to all products that fall within the selected Clearing Message Type Number Padding Direction The messages that are uploaded to or handed off from Oracle FLEXCUBE consists of fields of a specific length Most often the maximum field length is not utilized when you capture the actual field values Therefore you need to specify a padding character to fill the gaps You also need to indicate the direction of the padding characters whether you would like to pad to the left of the actual field value or to its right Normally for numeric fields you would choose to pad to the left of the numeric value Example Assume that the length of a numeric field say Amount is 10 and the actual field value is 100 consisting of only 3 digits Further you select 0 zero as the padding character and choose to pad to the left of the field value 2 5 ORACLE lf the message consists of this numeric field Zero will be used to fill the gap
41. ustomer Addresses or Reject Codes While maintaining Clearing Message Group Type maintenance record for addenda you can indicate whether the record is optional or mandatory Check the option box to indicate that the format you are maintained is an optional one Leave the box unchecked to indicate that it is a mandatory record Length check required You have the option to indicate whether you want to calculate the length of each line in the file If you specify that line check is required you can maintain line attributes such as start position and length for the clearing message group in the Clearing Msg Group Maintenance screen explained later in this manual Date and Time Format For date related fields you need to identify the format in which the date value will be sent from and received into Oracle FLEXCUBE By default Oracle FLEXCUBE sends all date fields in RRRRMMDD format Similarly for time related fields you have to identify the format in which the time value is to be sent from and received into Oracle FLEXCUBE For instance you can maintain a format like HHMMSS This format will continue to apply for the entire line of the message format Value Translation For each Oracle FLEXCUBE Node and External Tag combination you have to indicate whether translations should be performed for all tag values associated with the tag names A value translation is required only if the values sent by Oracle FLEXCUBE do not match with t
Download Pdf Manuals
Related Search