Validation on execution of HISCOD with SET ID and restriction of menu access after HISCOD before date change

1. Some SOLs habituated in leaving the office without execution of HISCOD as a result of which CPC had executed HISCOD in SET ID
2. This causes skipping of validations at HISCOD and  HSCOD getting failed during date change / HSCOLD
3. And some SOLs doing transaction after execution of HISCOD and leaving without clearing. This resulted in failure of HSCOD / HSCOLD 

Unblocking the transactions will cause issues during closures and interest posting :-

• Hence it is necessary  to stop running HISCOD in SET ID to avoid  skipping of validations and not allowing SOLs to do transactions after execution of HISCOD and before date change (HSCOD)

• Patches meant for these two validations were already  deployed in productions  

• From today onwards, CPC  will not be allowed to run HISCOD in SET ID and  SOLs will not access CTM,HTM, CXFER and HXFER during period between HISCOD and HSCOD. Incremental patch for restriction of all transaction menus  after HISCOD before date change is under consideration by Infosys

• Please educate the CPCs and SOLs in this regard

Restriction of using transaction menus before SOL date change after initiation of HISCOD

• There are instances where unverified transactions exist even after execution HISCOD which results in failure of sol change of date during EOD. 
• This is because of doing transactions at the time of execution of HISCOD

• To prevent this,  HTM, CTM, HXFER, CXFER  menus are restricted for access after HISCOD initiation and before completion of HSCOD i.e., SOL date change

• If the user is trying to use any of these 4 menus, user will get the following error

“Menu option is blocked as HISCOD is submitted for this SOL. After SOL date change this menu is available for the user”

• It has been requested  to Infosys to include all other transaction menus for restricting the access between HISCOD and HSCOD execution​

Steps to know the EOD blocking validation report in DOP Finacle

The following are the important steps to know the EOD bloking validation reports in the DOP Finacle they are mentioned below

1. Invoke HFTI and check for the Entered status Transactions and post the same.

   2.  Invoke the menu HFTI and check for the Posted Status and verify the same.

 

3. Invoke the menu HMICZ  and inquire on non closed zones. Close the zone after posting the inward cheques.

4. Invoke the menu HICHB/HIMC and inruire on unverified inventory transactions and verify the same in HICHB/HIMC respectively,

5. Invoke the menu HFINRPT and go to page number 3 and click on the report EOD Blocking Validation Report submit and then check in HPR report. If there are any blockings then clear the unverified transactions.

6. Invoke the menu HAFI and check for not authorized records and verify the same.

7. Invoke the menu HTV for bulk verification of transactions.

Issues in EOD and corrective actions in DOP Finacle

Issues in EOD and corrective actions in DOP Finacle

• Generally after clearing al the blocking validation we will perform EOD(End Of Day) in DOP Finacle.
• EOD in DOP Finacle is of three steps

1. HSCOD
2. HSOLCOP
3. HSCOLD

HSCOD:- 

• This is the first step in EOD operation which includes the following SOL Status they are

1. PRECODDONE
2. CHANGE OF DATE INITIATED
3. SOL DATE CHANGED
4. POSTCOD DONE

HSOLCOP

• This is the second step in EOD operation which includes the SOL Status as

1. SOL CLOSURE BATCH JOB DONE

HSCOLD

• This is the third and final step in EOD operation which include the SOL Status as 

1. SOL CLOSURE DONE

• For all steps EOD event status should be "EOD EVENT NOT IN PROGRESS" then only the concerned step is completed successfully.
• But we will face some of the techincal issues while performing the said three steps and corrective measures are mentioned below

Issues faced in First step of EOD and corrective action  at Office level:

Based on SOL status Inquiry report ( Menus- HSSI / EODMON) as detailed below, correction action to be taken as noted against each

SOL Status	Closure status	EOD event Status	Action to be done by Supervisor / System Admin / EOD user
PRECOD DONE	Failed	EOD event not in progress	(1) Check for pending transactions in HFTI ( transactions), HAFI ( Account opening), HIMC ( Inventory authorisation), HICHB ( Inventory - Issue of cheque book), HMICZ (Inward clearing zone) and clear  them (2) Alternatively, Invoke HPR menu with the same user who  executed HSCOD and check for validation report to know the blocking validations or failure reason  (3) After clearing pending transaction, EOD user has to rerun HSCOD
PRECOD DONE / POSTCOD DONE		SCOD running for unusual  time	Report the matter to CPC
DATE CHANGED		EOD event not in progress	Rerun HSCOD with tick mark at "Run only post date batch jobs"

  

Issues faced in 2^nd and 3^rd step of EOD execution and corrective action  at CPC level:

Based on SOL status Inquiry report  ( Menus- HSSI / EODMON)as detailed below, correction action to be taken as noted against each

SOL Status	EOD event Status	Action to be done by CPC
PRECOD DONE / POSTCOD DONE	SCOD running for unusual time	Report the matter to  EOD support team of Infosys with EODMON screenshot of respective office
POSTCOD DONE / SOL CLOSURE BATCH JOB DONE	SOLCOP running for unusual time	Report the matter to  EOD support team of Infosys with EODMON screenshot of respective office
SOL CLOSURE BATCH JOB DONE	Failed	Check HPR  of EOD user for failure report. CPC can rerun HSCOLD and regenearate failure report. If any  unverified transaction exist, report to  EOD Support team of Infosys / CEPT for unblocking
SOL CLOSURE BATCH JOB DONE	Failed	Check HPR  of EOD user for failure report.  If failure is because of not executing of PSSCD / any other batch job, report the matter to EOD support team of Infosys
SOL CLOSURE BATCH JOB DONE	EOD event not in progress and Not running HSCOLD	Check HPR  of EOD user for failure report.  If failure is because of " Processes logged on with previous date". Use HSAC
SOL CLOSURE BATCH JOB DONE /   SOL CLOSURE DONE	SCOLD running for longer time	Report the matter to  EOD support team of Infosys with EODMON screenshot of respective office