............ 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

Monday, 28 September 2015

Find Misplace Tran ID of Account Transfer-IN (HACXFSOL) Transaction in DOP Finacle

HACXFSOL command is used to transfer one account from one SOL to Home SOL. We have mentioned detail of this command in our previous post. If you don't read this post don't worry, you can read from below link Sometime we forget the Tran ID or Tran ID is not appeared due to server connection error. Here Finacle solution is give remedy to find the Tran ID of Account Transfer-IN Transaction. 

PROCESS OF FIND THE TRAN ID

  • HAFI command is used for this exercise.
  • Menu Shortcut - HAFI
  • GO
  • The following screen will be displayed.



  • SOL ID - 
  • Ref No. - Press "Space button of Key Board" 2 time (as show in screen shoot)

  • Table Short Name - ATT
  • Entered By - User ID of Concern
  • Authorized - Not Authorised
  • GO
  • The following screen will be displayed

  • Please see the Yellow arrow showing the Tran ID as 9251 mentioned in Key Value field.
  • This Tran ID can be verified in HACXFSOL
  • First You can V-View the Tran ID in HACXFSOL as screen shoot given below.

  • Now the details of Tran ID is shown. Once you confirm you can verify this Tran ID.

No comments:

Post a Comment