............ Have a nice day............
USER MENU ID IS UNDEFINED IN FINACLE MIS SERVER   Date of Implementation of "VERY GOOD" Bench Mark for MACPs effect from 25.07.2016   Expected DA from Jan 2017 – 3% or 2% ?    One minute talk time for each Rupee in Airtel Payments Bank   AICPIN for October 2016 : Chances for 5% DA from January 2017   Central Government employees retiring from January 2017 to submit online application   Pre-Budget Views of Govt. Employees for inclusion in the Budget for the Year 2017-18: Confederation i.e. Scrap NPS, Minimum Wage Rs. 26,000 & Fitment Formula etc   On Salary Week, Banks Unlikely to Meet Demand for Extra 1 Lakh Cr   82 per cent ATMs dry because government used that money to pay its own employees   National Anthem Before Movie, Rules Supreme Court. Citizens 'Duty-Bound' To Show Respect    undefined

Tuesday, 19 May 2015

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 "
  • 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 2nd and 3rd 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

No comments:

Post a Comment