INAU mode to IHLD Mode
- rabiul516
- Topic Author
- Visitor
Thanking you all
Please Log in or Create an account to join the conversation.
- gm.saran
- Offline
- Elite Member
- Posts: 203
- Thank you received: 29
Please Log in or Create an account to join the conversation.
- rabiul516
- Topic Author
- Visitor
Thanks
Please Log in or Create an account to join the conversation.
- kartsnek
- Visitor
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
FUNDS.TRANSFER can be put on hold only during first input, manually setting back from NAU or live is not allowed due to file dependencies (during COB-unauth-processing the NAU records are deleted and newly generated as HLD using OFS). Don't change the setting in PGM.FILE !
Please Log in or Create an account to join the conversation.
- Nash21979
- Offline
- Premium Member
- Posts: 106
- Thank you received: 3
we noticed that FTs that are not authorised during COB are not changed to IHLD. They keep the INAU status with old processing date. As far as I can recall, this functionality was working.
Is there any setting we need to modify so that they are moved to IHLD.
Regards,
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
If all check if .NOH is set in PGM.FILE for FUNDS.TRANSFER and if the job UNAUTH.PROCESSING is executed at all.
If both are OK you should contact Temenos.
If only some few there might be another reason depending on type of FT or when they are created or ...
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1185
- Thank you received: 157
I hit that problem recently; all I can say that in R13 it also works this way - FTs are not converted to IHLD. We haven't contacted Temenos since it fits our tasks.
P.S., Could be connected to having NS (Non-stop) module...
Cheers
VK
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
The following is applicable for fully NS applications
Non-Stop processing allows full transaction processing (i.e. input, authorise, delete, reverse) whilst the close of business processing is running. In the case of securities there may be some specific restrictions (e.g. on the day of a bond coupon payment for the security it may not be possible to do the transaction non-stop)
There is NO restriction on modifying/reversing/deleting existing contracts
There is NO restriction on back-values / forward values etc
There is no impact on transactions in an unauthorised state (e.g. INAU, RNA) before the COB started ; i.e. they will be left in the same state.
There is NO processing for these contracts to move them to HLD
Please Log in or Create an account to join the conversation.
- VK
- Offline
- Platinum Member
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
- Posts: 1185
- Thank you received: 157
RECORD.STATUS......... IHLD
CURR.NO............... 1
INPUTTER.............. 1213_EOD.UNAUTH.PROCESSING
Cheers
VK
Please Log in or Create an account to join the conversation.
- jpb
- Offline
- Moderator
- retired . . . ¯\_(ツ)_/¯
- Posts: 2859
- Thank you received: 649
For New Contracts Only
New contracts can be entered, amended and authorised
Back value transactions are not allowed. Contracts which were not authorised before the COB will be moved to HLD during the COB process, but new contracts will NOT be affected
Quotes are from User Guide "Non Stop Processing", there is also a list of fully and 'partial' NS enabled applications.
Please Log in or Create an account to join the conversation.