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

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


CommentsComment

Subscribe to: Post Comments (Atom)
ADD THE FACEBOOK WIDGET CODE HERE