«

»

Sep 22 2014

Simplifying the JDE debuglog

VN:F [1.9.22_1171]
Rating: 5.0/5 (2 votes cast)

Simplifying the debuglog

 

The jdedebuglog can look a mess to start with but can be broken down.

SQL statements etc are shown but one handy trait is the fact the BSFNS calls have levels. Much like nested Ifs.

This helps us see what BSFNs were called in our code. Every BSFN is listed but the level helps you see what ones your APPL called within it’s own ER code. BSFNLevel = 1 etc

 

 

Calling Business function BatchOpenOnInitialization from UNKNOWN for JDANTER1. Application Name [P584113], Version [P201I0001] (BSFNLevel = 5)

**********************************************************************************

*** Start dumping data structure for business function BatchOpenOnInitialization

**********************************************************************************

IN->[  1] <Item>: szBatchType                            <type>: STRING           <Value>: [N]

IN->[  2] <Item>: mnBatchNumber                       <type>: MATH_NUMERIC     <Value>: [0]

IN->[  3] <Item>: cPreviousBatchStatus             <type>: CHAR             <Value>: []

IN->[  4] <Item>: cPostOutOfBalance                  <type>: CHAR             <Value>: []

IN->[  5] <Item>: cFLAGSuppressBatchControl       <type>: CHAR             <Value>: [1]

IN->[  6] <Item>: jdBatchDate                             <type>: JDEDATE          <Value>: []

IN->[  7] <Item>: cBatchControlCancelFlag                      <type>: CHAR             <Value>: [1]

**********************************************************************************

*** End dumping data structure for business function BatchOpenOnInitialization

**********************************************************************************

 

The BSFN does what ever it needs to do but if it calls another BSFN then the BSFNLevel flag is increased by 1

 

 

Calling Business function X0010GetNextNumber from UNKNOWN for JDANTER1. Application Name [P584113], Version [P201I0001] (BSFNLevel = 6)

**********************************************************************************

*** Start dumping data structure for business function X0010GetNextNumber

*********************************************************************************

IN->[  1] <Item>: szSystemCode                         <type>: STRING           <Value>: [00]

IN->[  2] <Item>: mnNextNumberingIndexNo          <type>: MATH_NUMERIC     <Value>: [1]

IN->[  3] <Item>: szCompanyKey                        <type>: STRING           <Value>: []

IN->[  4] <Item>: szDocumentType                     <type>: STRING           <Value>: []

IN->[  5] <Item>: mnCentury                               <type>: MATH_NUMERIC     <Value>: [0]

IN->[  6] <Item>: mnFiscalYear1                         <type>: MATH_NUMERIC     <Value>: [0]

IN->[  7] <Item>: szSameAsDocumentType            <type>: STRING           <Value>: []

IN->[  8] <Item>: mnNextNumber001                   <type>: MATH_NUMERIC     <Value>: [0]

**********************************************************************************

*** End dumping data structure for business function X0010GetNextNumber

 

*NB each IN> call will have a resulting OUT> call. Shows what went in and what went out.

 

**********************************************************************************

*** Start dumping data structure for business function X0010GetNextNumber

**********************************************************************************

OUT->[  1] <Item>: szSystemCode                                 <type>: STRING           <Value>: [00]

OUT->[  2] <Item>: mnNextNumberingIndexNo      <type>: MATH_NUMERIC     <Value>: [1]

OUT->[  3] <Item>: szCompanyKey                                <type>: STRING           <Value>: []

OUT->[  4] <Item>: szDocumentType                              <type>: STRING           <Value>: []

OUT->[  5] <Item>: mnCentury                            <type>: MATH_NUMERIC     <Value>: [0]

OUT->[  6] <Item>: mnFiscalYear1                      <type>: MATH_NUMERIC     <Value>: [0]

OUT->[  7] <Item>: szSameAsDocumentType        <type>: STRING           <Value>: []

OUT->[  8] <Item>: mnNextNumber001                  <type>: MATH_NUMERIC     <Value>: [3619]

**********************************************************************************

*** End dumping data structure for business function X0010GetNextNumber

 

Return value is 0 for X0010GetNextNumber. (BSFNLevel = 6)  ( 0  means success, 1/2 = bad)

 

 

This is great because if we want to see what functions were called from within another BSFN the BSFNLevel flag will be 5 or above (*NB starts from 1)

Did our ER code it or did a BSFN we called call it?

Maybe copy this STEP into another file and look at that for simplicity and ease of understanding. Label them A B C etc…?

 

 

What to look for

 

ERROR INFO JDEERR – ID= 43, Error= 420C – b4200310.c, Line= 8546

 

This means E1 generated error 420C in BSFN B4200310 Line 8546

Very helpful

 

Also look for the following test to notify you that a called BSFN ended in error

 

Return value is 2

 

 

Debuglog Simplifying it

Published under the license.

VN:F [1.9.22_1171]
Rating: 5.0/5 (2 votes cast)
Simplifying the JDE debuglog, 5.0 out of 5 based on 2 ratings
(Visited 301 times, 1 visits today)

About the author

John Danter

Keen airsoft enthusiast with over 13yrs JDE development experience

1 comment

  1. David Terborg

    If I can suggest one thing, try JDETrace.
    It’s a brilliant tool.
    You can find it on this link: http://www.patwel.com/downloads/index.htm

    VN:F [1.9.22_1171]
    Rating: 0 (from 0 votes)

Leave a Reply