How to track the error code in JDE based on debug log

Hi, debugging  in JDE debug log has been tedious and headache if no rules or steps are followed.
Let 's try below debug log if you are able to track the root cause...

Example :  Error : Account Number 10.2510.STK is invalid  shown in ledger inquiry screen P09200 but this account number can be found in P0901 account master inquiry...

-------------- end of debug log -----------

From the given log, we may find the ERROR INFO which would show the error code on screen..From there, look upward and check if any BSFN or SQL query has caused this error.

From the BSFN ' GetAccountGeneralConstant, we get to see  the BSFN worked fine with return value is 0 meaning these are the symbols  used  in GL constant screen P0000

out >[ 1] cShortAccounSysmbol        [*]

out >[ 2] cLongAccountSymbol         [/]

out >[ 3] cThirdAccountSymbol         [ ]

Those who 's on application support, they would know the cThirdAccountSymbol is supposed to be /  and cLongAccountSymbol is blank... With this setup, ledger inquiry screen requires /10.2510.stk to be input correctly before being able to find the record..

Otherwise, you are required to change the General Ledger Constant as below in order to fix the error :

out >[ 1] cShortAccounSysmbol        [*]

out >[ 2] cLongAccountSymbol         [ ]

out >[ 3] cThirdAccountSymbol         [/ ]

SELECT  *  FROM TDCDTA/F0901  WHERE  ( GMANS = '10.2510.STK' ) 

Exiting DBPerformRequest

No More Data found 

which means it can not find the record 10.2510.STK

Hope that helps...

TQ