John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool

Introduction
If you’re a SQL guru, don’t read this whitepaper. Don’t email me with your opinion. I already know that you can use correlated
sub-queries, CASE statements, custom views, and all sorts of other tricks to make SQL sit, fetch, and bring you the morning
paper. This whitepaper is not for you … and nobody likes a show-off.

On the other hand, if you are a non-technical end-user of enterprise data and could stand to improve data accessibility, but are
not sure what solution to pursue, then by all means read on.

Keep in mind that this whitepaper is geared towards users of JD Edwards (JDE) ERP software, both World and Enterprise One
(E1). However, the general concepts should be applicable to many ERP packages and data.

The Reporting and Analysis Problem

So, perhaps you manage financial or cost accountants; maybe you’re a controller. If your organization is on the ball, then you’ve
no doubt been asked (i.e. told) to find ways for reducing time spent on transactional activities in favor of more value-added
decision support activities.

Unfortunately, we can’t support decisions without meaningful and ready access to our enterprise data. That’s right, it’s our data.
Our Debits, Credits, and balances don’t belong to IT; they belong to us, the users. Sure, IT owns the hardware, the databases,
the applications, the interfaces, and the rest of the infrastructure. And, truth be told, I’ve met lots of financially savvy and
accommodating IT folk. However, in the final analysis, if your enterprise data is not quickly actionable, then you’ve got problems
… but you already know that.

Now, in the JDE universe, once you sound the Reporting and Analysis alarm, you will likely be greeted with at least one of the
following four solutions, which I will list from easiest to most difficult for a non-technical end-user to leverage.

Canned Reports
You know what I’m talking about – Simple Income Statement, Trial Balance by Account, Open AP Summary, and so on.
These reports are actually programs, written by our friends at JDE, and placed on menus with a big old happy-faced front-end,
known as DREAMWriter to you JDE World folks. This batch version front-end allows regular, non-technical users to control
program logic and format (Processing Options), Data Selection, and Data Sequencing.

These “pushbutton” reports are super-easy to use, hence the nickname. However, the reports are largely static; you get what
you get, and nothing more without development.

Relational Analysis Tools

You’ve got to love SOX; it gave IT and Internal Audit a reason to lock up SQL nice and tight. I’m kidding … of course.

I’m using the term Relational Analysis in referring to those tools that allow you to select records from ERP tables, just like you
would through Microsoft Access. Envision a simple data dump with sorting, totaling, and formatting. You JDE World folks have
likely used World Writer and/or Showcase Strategy, two outstanding tools. JDE E1, on the other hand, is lacking in truly user-
friendly Relational Analysis; both UTB and Data Browser are somewhat limited in their functionality and flexibility.

If only there was a World Writer for E1… If there was, we’d hope it would allow us to perform HAVING clauses and write Totals
to a new file.

Multidimensional Analysis Tools

You’ve heard the terms – Business Intelligence, OLAP, Cubes, Slice-and-Dice, and so on. You also know the players –
Cognos, Hyperion, Cetova, Business Objects, and so on. These Multidimensional Analysis tools are great because a non-
technical end-user can, with a few drags and drops, compile and execute tons of complex SQL to roll-up enterprise data in useful
ways.

866-CETOVA-4 Page 1
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool
Furthermore, good Multidimensional Analysis tools significantly enhance the user experience with standard features and
functionality, such as a GUI, drag-and-drop interface; the ability to perform custom MS Excel-like formatting; and the ability to
create custom row, column, and cell calculation. Remember, Relational Analysis tools merely dump a table’s records; you can’t
simply insert an EBITDA calculation in the midst of SQL-extracted account balance records. This is why Multidimensional
Analysis tools are better equipped to yield push-button pro forma financial statements.

By the way, with regard to FASTR, don’t rush to email me claiming that it is a Multidimensional Analysis tool. Yes, you may
define Column Specifications using Business Unit Master (F0006) Category Codes and Ledger Types, which will perform basic
roll-ups. You can also define Business Unit Structures in JDE World to achieve the same end. However, FASTR is a not GUI
tool, and does not lend itself to any sort of dynamic pivoting. I believe that FASTR, and STAR for that matter, occupy some
green-screened purgatory between SQL and OLAP. That said … these are two excellent tools.

Similarly, with regard to JDE E1, both ERW and Crystal straddle the fence as being primarily data extract tools with some
Multidimensional Analysis capability. Unlike FASTR, ERW and Crystal can operate over any file, as opposed to only the F0902.
However, given their fundamental gaps in ease-of-use, performance, and deployment, these packaged tools do not really
compete with best-of-breed, third-party Multidimensional Analysis tools. On the other hand, in my experience, organizations with
means typically look to replace ERW and Crystal with more efficient solutions.

Custom Development
Good developers are worth their weight in gold, and those good ones tend to be cocky, like fighter pilots ... “If you can think it, I
can program it.” Typically, they can program any reporting requirement and then slap on a DREAMWriter or batch version front-
end to make your life easier. However, this is expensive in terms of man-hours, and at the end of the day, you’re left with just
another narrowly useful pushbutton report.

Choosing the Proper Tools

As if you haven’t already figured it out, your best chance, as a non-technical end-user, to achieve Reporting and Analysis
freedom and independence, is to leverage some combination of Relational and Multidimensional Analysis tools. Now, I write
“combination,” because each genre of tool selects, groups, and presents your ERP data differently, fundamentally dare I say,
than the other; these tools serve distinct purposes.

The remainder of this paper is dedicated to those end-users unsure of when to use what category of Reporting and Analysis tool:
Relational versus Multidimensional. Some clients have asked of me, “Should I use Cetova C-QRY or Cetova C-FAR?” Others
have asked, “Can you write me a World Writer, or should I call the Business Objects consultant?” My goal is to clearly convey to
you the appropriate situational usage of Relational versus Multidimensional Analysis tools.

Data Example
Please use the following simplified versions of the JDE General Ledger Account Balance (F0902), Accounts Payable Ledger
(F0411), and General Ledger (F0911) tables. Please assume zero stored decimals.

Table 1 – JDE ACCOUNT BALANCES (F0902)

TABLE 1 - JDE GL ACCOUNT BALANCES (F0902)
GL Account ID Ledger Type Period 1 Postings Period 2 Postings Period 3 Postings
GBAID GBLT GBAN01 GBAN02 GBAN03
00000001 AA 1010 990 1000
00000001 BA 1000 1000 1000
00000002 AA 1000 1500 2000
00000002 BA 1000 1000 1000
00000003 AA 990 995 1000
00000003 BA 1000 1000 1000
00000004 AA 1000 1000 1000
00000004 BA 1000 1000 1000

866-CETOVA-4 Page 2
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool
Table 2 – JDE AP LEDGER (F0411)
TABLE 2 - JDE AP LEDGER (F0411)
Supplier Number Company GL Class Open Amount
RPAN8 RPCO RPGLC RPAAP
1001 00001 1000
1001 00001 NOTE 1100
1001 00001 TRAD 1200
1001 00001 TRAD 5000
1002 00001 2000
1002 00001 NOTE 2500
1002 00001 TRAD 2900
1001 00100 3000
1001 00100 NOTE 3050
1001 00100 TRAD 3100

Table 3 – JDE GENERAL LEDGER (F0911)

TABLE 3 - JDE GENERAL LEDGER (F0911)
Document Number Document Type Amount Period Number Object
GLDOC GLDCT GLAA GLPN GLOBJ
1001 OV 1500 7 1310
1002 OV 1500 7 1310
1003 IA 2000 7 1310
1004 IG 500- 7 1310
1005 RI 10000 7 1310
1006 JE 500- 7 1320
1007 OV 1000 8 1310
1008 OV 1500 8 1310

As an aside, I highly recommend that, if you regularly work in ERP Reporting Analysis, you make a point of learning the
structures of the database tables most relevant to your function. For you JDE World folks, DREAMWriter P98DDSP is an
excellent resource. The JDE E1 readers should ask your CNC resource to send you table specifications from Table Design Aid
through OMW. Drop me an email (jlambrianakos@cetova.com) if you need any further assistance.

Case One: Variance Reporting

So, your boss drops by one day and asks for a “quick” Q1 Actual versus Budget variance over a range of P&L accounts. In fact,
forget the variance calculation; just show Account ID, AA Amounts, and BA Amounts. Simple! Right?

Well, start at the beginning; look back at Table 1 – JDE GL Account Balances (F0902). See how JDE stores its account
balance data? Do you have any reason to believe that data arranged in this manner lends itself to a “simple” representation as
Account ID, AA Amounts, and BA Amounts? Well you shouldn’t, because it doesn’t.

Now, we all know that FASTR will crank this out, no problem. However, let’s put FASTR aside for a moment, because it was
designed specifically for this table, the F0902, and nothing else.

So what do we do? What solution do we use?

Well, because it’s my job to actually know SQL, I could write the following SQL statement, shown in Figure 1.

FIGURE 1 – JDE F0902 SQL WITH QUERY RESULTS

select a.gbaid as Account_ID,
(select sum(b.gban01+b.gban02+b.gban03) from f0902 b where b.gbaid = a.gbaid and b.gblt = 'AA') as AA_Ledger,
(select sum(b.gban01+b.gban02+b.gban03) from f0902 b where b.gbaid = a.gbaid and b.gblt = 'BA') as BA_Ledger
from f0902 a group by a.gbaid

866-CETOVA-4 Page 3
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool

FIGURE 1 – JDE F0902 QUERY RESULTS

Account ID AA Ledger BA Ledger
00000001 3000 3000
00000002 3500 3000
00000003 2985 3000
00000004 3000 3000

This SQL statement will work anywhere, JDE World DB2 and JDE E1 MS SQL or Oracle. So, why not jot it down and run it
when you need? Well, first off, as previously mentioned, IT and Internal Audit have likely locked down SQL nice and tight.
Furthermore, what will you do when your boss comes back with the subsequent request to include Commitment Ledger (PA
Ledger) Amounts; data selection and sequencing by Company, Business Unit, Object, Subsidiary, Subledger, and Subledger
Type; GL Account Code Description; percentage variance calculations; and so on?

This is where Multidimensional Analysis tools come in handy, when you require horizontal (i.e. side-by-side) representation of
numbers that are stored vertically (i.e. across multiple records). In our previous example, the AA Ledger and BA Ledger Period
Postings are required to appear side-by-side, but are stored across separate table records. Look below, in Table 4 – JDE GL
Account Balances (F0902), AA Ledger records are highlighted Green and BA Ledger records are highlighted Red. Note their
vertically-oriented relationship.

Table 4 – JDE ACCOUNT BALANCES (F0902)

TABLE 4 - JDE GL ACCOUNT BALANCES (F0902)
GL Account ID Ledger Type Period 1 Postings Period 2 Postings Period 3 Postings
GBAID GBLT GBAN01 GBAN02 GBAN03
00000001 AA 1010 990 1000
00000001 BA 1000 1000 1000
00000002 AA 1000 1500 2000
00000002 BA 1000 1000 1000
00000003 AA 990 995 1000
00000003 BA 1000 1000 1000
00000004 AA 1000 1000 1000
00000004 BA 1000 1000 1000

Let’s do another example before moving onto Case Two.

Now, your boss drops by one day and asks for a “quick” comparison of January Actual Labor Expense (Account 6100.100)
across all Companies that booked a Labor Expense. Let’s look below at Table 5 - JDE GL Account Balances (F0902), which
is a differently simplified version of the F0902 Table. Note that the Company 00001 (Green), Company 00050 (Red), and
Company 00100 (Yellow) records are arranged vertically with respect to each other.

Table 5 – JDE ACCOUNT BALANCES (F0902)

TABLE 5 - JDE GL ACCOUNT BALANCES (F0902)
GL Account ID Ledger Type Period 1 Postings Period 2 Postings Period 1 Postings
GBCO GBMCU GBOBJ GBSUB GBAN01
00001 0010101 6100 100 1000
00001 0010102 6100 100 1500
00001 0010103 6100 100 2000
00050 0500101 6100 100 200
00050 0500102 6100 100 300
00050 0500103 6100 100 500
00100 1000101 6100 100 10000
00100 1000102 6100 100 11000

866-CETOVA-4 Page 4
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool

However, the desired results should arrange Company dollars horizontally. See Figure 2 – JDE F0902 Query Results below.

FIGURE 2 – JDE F0902 QUERY RESULTS

FIGURE 2 – JDE F0902 QUERY RESULTS
Account Company 00001 Company 00050 Company 00100
6100.100 4500 1000 21000

So, this is a good indicator for Multidimensional Analysis. Could I write an SQL? Sure. Could the average non-technical end-
user write an SQL? No way. Furthermore, writing that SQL would be arduous because, if you noticed, your boss simply
requested all Companies, which is meaningless to you. You’d first have to run the following separate SQL statement to figure
out which Companies actually have January Actual Labor Expense (Account 6100.100) postings. See Figure 3 – JDE F0902
SQL with Query Results.

FIGURE 3 – JDE F0902 SQL WITH QUERY RESULTS

select distinct GBCO as Company
from F0902
where GBOBJ = ‘6100’ and GBSUB = ‘100’ and GBLT = ‘AA’ and GBAN01 <> 0
order by GBCO

FIGURE 3 – JDE F0902 QUERY RESULTS

Company
00001
00050
00100

Wait! Anyone else know what’s wrong with the above-stated SQL? That SQL tells you if Net Postings for January are not zero;
it makes no indication of offsetting Debits and Credits. So, in reality, you’d have to run the following SQL in Figure 4 over the
JDE General Ledger Account Activity (F0911) table, which is likely a significantly larger table than your F0902.

FIGURE 4 – JDE F0911 SQL

select distinct GLCO as Company
from F0911
where GLOBJ = ‘6100’ and GLSUB = ‘100’ and GLLT = ‘AA’ and GLPN = 1
order by GLCO

One thing I don’t want to do is make any blanket statements in this paper; that’s a surefire way to earn wrath. So, allow me to
reiterate, you can use a Relational Analysis tool for this task, whether that tool is SQL400, IBM Query, MS SQL, or a nifty front-
end like World Writer or Cetova C-QRY. But make no mistake, you will have to gain access to SQL and learn SQL. Or, in the
case of an SQL front-end, like World Writer or C-QRY, you’d better ensure that it supports CASE statements (huh?) and/or sub-
queries (what?), as well as generates a distinct listing of available field values across an entire table; see Figures 3 and 4.

Now, I’ll get back to FASTR for you JDE World folks. As you know, FASTR is a great tool and can generate the results
documented in Case One. FASTR can also leverage Category Codes and other means of Business Unit aggregation.
However, FASTR works only over the F0902 table, and as we will see next in Case Two, your Multidimensional Analysis needs
certainly do not end with the F0902 table. Furthermore, FASTR is cumbersome and relatively inflexible. You ran out of column
space for your 18-month rolling forecast? Too bad. You forgot to run Balance Auditor for your F0911 drill-down? Run it again.
Need a GUI drag-and-drop interface for custom formatting and ease-of-use? Nope – you’re not going to get this.

Again, with regard to JDE E1, and certainly not to bash JDE E1, the reporting alternatives are limited. Both ERW and Crystal
can get you close, if not all the way to your goal. However, using these tools and sharing the fruits of your labor with colleagues
are both rather cumbersome processes.

866-CETOVA-4 Page 5
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool

Case Two: AP Accruals

Here comes your boss again. This time, she asks for a report of all Open AP, by Supplier, by GL Class Code and Company.
Perhaps there is some Balance Sheet reconciliation afoot. Anyway, she wants Supplier Number and summed Open AP figures
in a separate column per distinct GL Class Code and Company combination.

Looking back at Table 2 – JDE AP Ledger (F0411), and taking into account what you [hopefully] learned in Case One, we
should agree that this data request clearly indicates usage of a Multidimensional Analysis tool. See how JDE stores its AP
Ledger data? Let’s look below at Table 6 - JDE AP Ledger (F0411). Note that distinct combinations of Company and GL Class
Code are arranged vertically with respect to each other as follows: Company 00001-GL Class BLANKS in Red, Company 00001-
GL Class ‘NOTE’ in Green, Company 00001-GL Class ‘TRAD’ in Yellow, Company 00100-GL Class BLANKS in Light Blue,
Company 00100-GL Class NOTE in Purple, and Company 00100-GL Class TRAD in Blue.

Table 6 – JDE AP LEDGER (F0411)

TABLE 6 - JDE AP LEDGER (F0411)
Supplier Number Company GL Class Open Amount
RPAN8 RPCO RPGLC RPAAP
1001 00001 1000
1001 00001 NOTE 1100
1001 00001 TRAD 1200
1001 00001 TRAD 5000
1002 00001 2000
1002 00001 NOTE 2500
1002 00001 TRAD 2900
1001 00100 3000
1001 00100 NOTE 3050
1001 00100 TRAD 3100

Once again, I could write the following SQL statement, shown in Figure 5:

FIGURE 5 – JDE F0411 SQL WITH QUERY RESULTS

select a.rpan8 as Address,
(select sum(b.rpaap) from f0411 b where b.rpan8 = a.rpan8 and b.rpaap <> 0 and b.rpglc = '' and rpco = ‘00001’) as 00001_BLANKS,
(select sum(b.rpaap) from f0411 b where b.rpan8 = a.rpan8 and b.rpaap <> 0 and b.rpglc = ‘NOTE’ and rpco = ‘00001’) as 00001_NOTE,
(select sum(b.rpaap) from f0411 b where b.rpan8 = a.rpan8 and b.rpaap <> 0 and b.rpglc = ‘TRAD’ and rpco = ‘00001’) as 00001_TRAD,
(select sum(b.rpaap) from f0411 b where b.rpan8 = a.rpan8 and b.rpaap <> 0 and b.rpglc = '' and rpco = ‘00100’) as 00100_BLANKS,
(select sum(b.rpaap) from f0411 b where b.rpan8 = a.rpan8 and b.rpaap <> 0 and b.rpglc = ‘NOTE’ and rpco = ‘00100’) as 00100_NOTE,
(select sum(b.rpaap) from f0411 b where b.rpan8 = a.rpan8 and b.rpaap <> 0 and b.rpglc = ‘TRAD’ and rpco = ‘00100’) as 00100_TRAD
from f0411 a where a.rpaap <> 0 group by a.rpan8 order by a.rpan8

FIGURE 5 – JDE F0411 QUERY RESULTS

Address 00001_BLANKS 00001_NOTE 00001_TRAD 00100_BLANKS 00100_NOTE 00100_TRAD
1001 1000 1100 6200 3000 3050 3100
1002 2000 2500 2900 0 0 0

Do your eyes hurt yet? How much would they hurt if your Financial AAIs leveraged ten GL Classes across five Companies?

Oh, and don’t forget, to get cracking on the above SQL statement, you’d have to first run the following SQL statement, in Figure
6, just to figure out what distinct combinations of Company and GL Class Code reside in the AP Ledger.

FIGURE 6 – JDE F0411 SQL WITH QUERY RESULTS

select distinct RPCO as Company, RPGLC as GL_Class
from F0411
where RPAAP <> 0
order by RPCO, RPGLC

866-CETOVA-4 Page 6
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool

FIGURE 6 – JDE F0411 QUERY RESULTS

Company GL_Class
00001
00001 NOTE
00001 TRAD
00100
00100 NOTE
00100 TRAD

You JDE World folks can forget FASTR, by the way. As previously stated, it works only over the F0902 table.

With regard to JDE E1, the two aforementioned native applications, namely ERW and Crystal, could accomplish this reporting
task. However, from an ease-of-use, performance, and deployment standpoint, neither ERW nor Crystal can compete with best-
of-breed Multidimensional Analysis solutions.

Let us recap. Why is Multidimensional Analysis preferred over Relational Analysis for the Case Two task?

As stated repeatedly, compare the F0411 data layout (Table 5) of vertically-related GL Class Code values with our desired
output format (Figure 5) of horizontally juxtaposed dollars per GL Class Code. This deliverable requires either a thorough
knowledge of SQL or a SQL front-end supportive of complex underlying code, or, an application specifically designed to
manipulate data in this manner through a non-technical, end-user-oriented front-end. A Multidimensional Analysis solution,
reflective of the latter, is therefore indicated.

Keep in mind that my next whitepaper will discuss must-have Multidimensional Analysis features and functionality, along with
best practices for pre-implementation homework. So, at this point you should know when Multidimensional Analysis is required.
Hopefully, after my next piece, you’ll know what to look for in a tool, and how to max out your investment.

Case Three: Table Dumps and Drill-Backs

We’ve seen two cases in which Multidimensional Analysis is a better fit for the Reporting and Analysis task at hand. Now, let’s
look at a scenario where Relational Analysis is either preferred, or, should be used in tandem with Multidimensional Analysis to
effect an end-to-end solution.

Here comes your boss again. Very simply, she wants a list of every entry to Finished Goods Inventory (Object 1310) and
Inventory Allowance (1320) during the month of July, with a total on Object code and a Grand Total.

Well, this is indeed simple; it’s just a list. Looking back at Table 3 – JDE General Ledger (F0911), and taking into account the
anticipated result, seen below in Figure 7, this is a slam-dunk for a Relational Analysis tool such as World Writer and Cetova C-
QRY.; and it is slam-dunk for several reasons.

First and foremost, the format of the desired output aligns well with the structure of the database table, the F0911. Therefore,
there is absolutely no reason to use a Multidimensional Analysis tool, whose purpose is to present data in more analysis-friendly
formats; it would be like trying to swat a fly with an atomic bomb.

Pop Quiz!
When would you use Multidimensional Analysis to present the requested F0911 data from Case Three?

Think about it … horizontally juxtaposing the vertical …help?!?

866-CETOVA-4 Page 7
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool
If your boss was looking to determine the individual subsystems that impact Inventory, well then she may want to analyze the ins
and outs by Document Type. So, for a single Object code, a side-by-side comparison of amount totals by Document Type would
be useful. See Figure 8.

Second, a tool such as Showcase Strategy or Cetova C-QRY will leverage relatively fewer instructions to yield the same results.
For example, I need once to tell Cetova C-QRY that a subtotal is required every time the Object code changes; just once. By
contrast, if for some reason I used Cetova C-FAR to obtain the results in Figure 7, I would have to code an individual subtotal
instruction for each and every distinct Object code value.

Figure 7 – JDE F0911 QUERY RESULTS

Figure 7 – JDE F0911 QUERY RESULTS
Document Number Document Type Amount Period Number Object
GLDOC GLDCT GLAA GLPN GLOBJ
1001 OV 1500 7 1310
1002 OV 1500 7 1310
1003 IA 2000 7 1310
1004 IG 500- 7 1310
1005 RI 10000 7 1310
Total Object 1310 14500
1006 JE 500- 7 1320
Total Object 1320 500-
Grand Total 14000

Figure 8 – JDE F0911 QUERY RESULTS

Figure 8 – JDE F0911 QUERY RESULTS
Object Code Receipts Adjustments Sales Journal Entries
1310 3000 1500 10000 0
1320 0 0 0 500-
Totals 3000 1500 10000 500-

Let’s expand on this notion a bit by discussing typical drill-back functionality.

Let’s say that you began Case Three with a request for the output in Figure 8, rather than Figure 7. You therefore used a
Multidimensional Analysis tool to aggregate the numbers by Document Type. Well, when your boss sees a manual Journal Entry
to Object code 1320, she may want to drill-back into the detail to see who booked the entry, when, and why. For this, you need
to then dump the F0911 table, i.e. present the results in Figure 7. This is classic drill-back functionality; start with meaningfully
aggregated numbers, and then explore the underlying data, in its native format, to gain insight into the initial aggregates. We
therefore see how Multidimensional Analysis and Relational Analysis tools are used in tandem to effect a total solution. A good
Multidimensional Analysis tool will offer drill-back through some sort of Relational Analysis application.

By the way, drill-back should not be restricted to the table from which you analyzed the initial roll-ups. For example, I may run a
consolidated Balance Sheet over the F0902 via Cetova C-FAR. A good tool, like C-FAR, will enable me to drill-back, to specific
tables per the selected data. So, when hovering over my AP Trade balance, I should be able to drill-back, at some point, to my
F0411, as well as my F0911. Similarly, when hovering over my Inventory balance, I should be able to drill-back, at some point,
to my Cardex (F4111), as well as my F0911.

866-CETOVA-4 Page 8
www.cetova.com
 John Lambrianakos

JD Edwards Reporting and Analysis:

Helping the Non-Technical JDE End-User Choose the Proper Tool

Summary
Thank you for reading, folks; I look forward to getting emails with feedback, comments, suggestions, and so forth.

So, for a non-technical end-user, I’ll set for the following three takeaways.

First, understand how your target ERP data resides within its native database. It is well within the grasp of a non-technical end-
user to obtain a basic understanding of the content and layouts of the tables most relevant to your job function. So, if you’re an
AP Manager in a JDE shop, then by all means, set out to understand how your data is stored in the Supplier Master (F0401), AP
Ledger (F0411), AP Payment Header (F0413), and AP Payment Detail (F0414) tables. Throw in for good measure the Address
Book Master (F0101), General Ledger (F0911), and Tax (F0018) tables; you’re talking about less than ten tables … tops.

Second, per this basic understanding of your data, put forth an educated request for Reporting and Analysis assistance.
Remember, different Reporting and Analysis requirements require different tools. Straight transactional reporting, call it dumping
the contents of your tables, is best accommodated by a Relational Analysis tool, such as SQL or a user-friendly application that
generates SQL, such as Cetova C-QRY or Showcase Strategy. However, more analytical tasks, which require juxtaposing
comparable data elements from disparate records per some user-defined roll-up, require a Multidimensional Analysis tool. This
is especially the case if you intend to comingle row calculations (e.g. Gross Margin, Operating Income, Balance Sheet Ratios,
etc.) among reported data.

Third, in closing, remember that Multidimensional and Relational Analysis tools complement each other; it’s not one or the other.
Let me give one last real-life example. Say you perform segment reporting over JDE account balances, with traditional P&L-
formatted rows, and columns that represent Business Unit roll-ups as segments. This certainly requires a Multidimensional
Analysis tool; there’s no other simple way to roll-up Business Units side-by-side as columns. However, the subsequent drill-back
from balances to transactional activity will be accommodated by a Relational Analysis tool; you’re just dumping the F0911
records associated with the target balances.

Next Whitepaper Preview

After reading this whitepaper, you should now have some idea of when Multidimensional Analysis is the proper fit for your JDE
Reporting and Analysis needs. So, please look forward to my next piece, which will discuss must-have Multidimensional
Analysis functionality, along with best practices for pre-implementation homework. My goal will be to help you maximize your
Multidimensional Analysis ROI.

About the Author

John Lambrianakos (jlambrianakos@cetova.com) is the VP of Marketing and Product Development at Cetova Corp. John has
been working with JD Edwards since 1991, both as a consultant for GL Associates and IBM Global Services, and, in industry as
a Finance Manager at Tiffany & Co. John received his BA in Economics from Vassar College in 1991, and his MBA from the
University of Texas at Austin, McCombs School of Business, in 1995.

866-CETOVA-4 Page 9
www.cetova.com