FinnOne Connect

Steps For New Message Creation

2007 Nucleus Software Exports Ltd. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means,
electronic or otherwise, including photocopying, reprinting, or recording, for any purpose, without
the express written permission of Nucleus Software Exports Ltd.

TRADEMARKS

The names of all other company, brand, product or service names mentioned herein are the
trademarks or registered trademarks of their respective owners.
 CONTENTS

1. Steps for New Master Creation

2. Steps for New Transaction/Inquiry Creation
 New Master Creation Steps

 For a new Master creation, put proper entries in the following table i.e.
FINAPI_ONLINE_MASTER_INTERFACE.
 The column DATA_GEN_QUERY contains the query which gave us the response in XML
format for newly created master.
 If the new master XML is going to be large in size then also put FTP details in which
the large file should be uploaded in FTP server by putting data in the column
IS_MASTER_LARGE “Y”.
 The master can be done through stateless/stateful ways.If we want to done through
stateful connection then set the parameter SESSION_FLAG as 1 in the table
FINAPI_SEC_MODULE_M. Vice versa should be done for stateless connection.
 For authentication purposes, new master id and the availability time should be
properly inserted in the table FINAPI_SEC_MODULE_MAS_TXN_MAP.

New Transaction/Inquiry Creation Steps

 Create two new tables in the module like LMS/GCD/LENDING in which we want to
retrieve data. The naming convention as follows for the above mentioned tables :-
putanyname_REQ_API :- Normal Table which contains the response ID.
putanyname_REQ_RESPONSE_API :- that table should be a globally temp table &
deleted on commit.
 Create a new temp table in FinnConnect module containing one column of XML type.
 Put proper entries for the newly created transaction/inquiry in the table
FINAPI_ONLINE_TXN_MASTER. Details of the table as follows

Name Null? Type

----------------------------------------- -------- ----------------------------
TRANSACTION_ID NOT NULL NUMBER(20)
TRANSACTION_NAME NOT NULL VARCHAR2(500)
MODULE_ID NOT NULL NUMBER(10)
DATA_REQUEST_XSD NUMBER(10)
DATA_RESPONSE_XSD NUMBER(10)
XMLTYPE_TABLE_NAME NOT NULL VARCHAR2(50)
PARSER_TRIGGER_NAME NOT NULL VARCHAR2(50)
STORED_PROC_TO_CALL NOT NULL VARCHAR2(50)
DATA_GEN_QUERY CLOB
AVAILABLE_FROM DATE
AVAILABLE_TO DATE
COMMIT_REQUIRED VARCHAR2(1)
USER_MODIFIED NOT NULL VARCHAR2(50)
DATE_MODIFIED DATE
NOTE :- Put a new sequential transaction id/inquiry id.
The DATA_GEN_QUERY is responsible for fetching data from the above created globally temp
table & gave us output in XML format.
The XML_TYPE_TABLE_NAME contains the name of the temp table that is created in the
Finnone connect API.
The PARSER_TRIGGER_NAME contains the trigger name for the newly created transactions.
The column STORED_PROC_TO_CALL contains the name of the stored procedure & it will
fetch data from other modules and give a insert in the globally temp table.

SCHEMA REGISTRATION STEPS FOR NEW TRANSACTiON/INQUIRY

 create a new schema & store in the application server.

 Again store in the database too for validation purpose.
 That newly created schema should be mapped to the transaction request/response
schema.
 Now the above temp table created above should be mapped to the transaction
request/response schema.