Scribd Logo
Upload

Welcome to Scribd!

  • 77 views

    Finacle Support Connect - Vol 22 PDF

    Uploaded by

    Ajay Nonia

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Finacle Support Connect - Vol 22 PDF

    Uploaded by

    Ajay Nonia
    77 views2 pages

    Original Title

    Finacle Support Connect- Vol 22.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    77 views2 pages

    Finacle Support Connect - Vol 22 PDF

    Uploaded by

    Ajay Nonia

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    Finacle Support Connect | Knowledge Series March 2021 | Vol.

    22

    Finacle Support brings you this fortnightly knowledge bulletin to augment your problem-solving capability. There is more to it. Every edition
    is put together with utmost diligence to ensure that best practices and known resolutions are shared. In this edition you will find the following
    articles:
    • Customer Transactions During Inward Reject
    • Relevance of PRPM Parameter CUST_ASSIST_MNU_PRF_FILTRATION
    • UREX Command in Finacle Scripting
    • Webinar Announcement: Best Practices on Finacle Year-End Processes
    So let’s start reading!
    Customer Transactions During Inward Reject
    Product: Finacle Core Banking Version: 10.x onwards
    The parameter Route Reject Transaction through A/c is maintained in the HICZCM menu. The
    corresponding backend flag is inw_rej_cust_tran_flg in the IZH table.
    The parameter indicates whether the bank wishes to create customer transactions for inward
    rejection.
    If the inw_rej_cust_tran_flg is set to Y, then there will be a debit transaction for the original inward
    and credit transaction indicating that the instrument is rejected. This is required by customers to
    know that a cheque is being presented and has been returned for some reason.
    If the flag is set to N (default behavior), then there will not be any explicit transactions in the customer account. However, debit and credit
    would take place in accounts defined at the zone level.
    • If the CHARGE EVENT ID is defined at the zone level, then the transactions for rejected charges will be created as part of the closure process.

    Relevance of PRPM Parameter CUST_ASSIST_MNU_PRF_FILTRATION


    Product: Finacle Online Banking Version: 11.0.x and 11.2.x
    If we are linking the Customer Assist menu profile to a bank user, then they are confined to menus
    that are available in the linked Customer Assist menu profile and will not be able to view or serve
    users with other menus.
    E.g. If the RUSER menu profile is linked to a bank user, then they will be able to able to view only
    the related menus of RUSER during customer assist login, and will not be able to view the menus
    linked to the end user which are not part of the RUSER profile.
    To overcome the above restriction, the PRPM parameter CUST_ASSIST_MNU_PRF_FILTRATION can be used.
    If the Value is set to N, the application will allow the bank user to view all the menus linked to the end users.
    If the Value is set to Y, the application will check for the Customer Assist menu profile linked to the bank user, and will display only the
    associated menus.

    Page 1 of 2
    Finacle Support Connect | Knowledge Series March 2021 | Vol. 22

    UREX Command in Finacle Scripting


    Product: Finacle Core Banking
    We have been frequently calling SYSTEM(“some command”) in the script files. This executes a com
    file or shell script and process some commands. The com file completes execution and control
    returns back to the calling script. But it cannot pass back information to the script which could have
    been used for further processing in the script.
    This limitation of SYSTEM command can be overcome by using the UREX functionality of script. This
    can do all the things that the SYSTEM command does, and additionally returns information to the
    calling script in repos.class variables.
    Syntax:
    sv_r = UREX( param1, param2, param3 )
    Param1 = com file name with path. This will be executed when the UREX command is executed.
    Param2 = A file name which is to be created in the com file and “repos.class variables = values” to be dumped into this file. These will be
    made available to the script on completion of com file execution from UREX. Also, this file will be deleted once control comes back to calling
    script.
    Param3 = arguments to the com file. Typically multiple arguments should be passed with a separator like “^” and is to be spli t inside the
    com file.
    UREX command has return value sv_r, which will be 0 in case of successful execution of com file and non-zero value for failures.
    Sample script: Sample Com:
    sv_z = urhk_B2k_PID("") #!/bin/sh
    BANCS.INPUT.PID = BANCS.OUTPARAM.PID solId=`echo $2`
    BANCS.INPUT.comfile = c=$solId
    "/INSTALLERS/GSUK/BE/Finacle/FC/app/cust/UKBANK/INFENG/com/Urex_test.com" d="BANCS.OUTPUT.inputStr=\""
    BANCS.INPUT.out_file = BANCS.STDIN.userId + "_" + BANCS.INPUT.PID + ".txt" e="\""
    BANCS.INPUT.argsToCom = BANCS.STDIN.mySolId
    sv_r = UREX(BANCS.INPUT.comfile, BANCS.INPUT.out_file, BANCS.INPUT.argsToCom) echo $d$c$e > $1
    print(sv_r)
    PRINT(BANCS.OUTPUT.inputStr)
    Note:
    i. BANCS.OUTPUT.inputStr value assigned in com file will be accessible in the calling script
    ii. UREX can be used only for foreground processing of commands or com file
    Webinar Announcement:
    Best Practices on Finacle Year-End Processes
    Finacle Core Banking Support Team is hosting a webinar on Year-End Processes in Finacle. This session is aimed at discussing the best
    practices that can be followed for year-end processing. Please feel free to share the best practices you follow. We would like this session to
    be interactive and more collaborative.

    Click here to register today!


    Date: Tuesday, March 16, 2021

    Time: 2:00 PM to 3:00 PM IST

    Hope you like this edition. Is there anything that you’d like to see in the forthcoming series? We’d love to hear from you!
    Write to us at [email protected]

    External – Confidential Finacle Digital Communication Services Copyright © 2021 EdgeVerve Systems Limited
    To unsubscribe, please click here

    Page 2 of 2

    You might also like