Reporting _ Paul Vella _ OBI Analytics for JDE.pdf

Best practices for implementing
OBI Apps with JD Edwards

Paul Vella
EPM and BI Practice Lead (Vic)
Red Rock Consulting

The most comprehensive Oracle applications & technology content under one roof

Agenda
•  OBI Applications in a nutshell
•  OBIA and JDE
•  Pitfalls / Gotchas / Lessons Learnt
•  BI Deployment Options
•  Red Rock BI Accelerators


OBI Applications in a nutshell
•  Prebuilt BI solutions
•  Each application covers a specific business area
(Financials, Procurement, Sales, etc)
•  Support different transactional sources (EBS,
JDE, SAP, PeopleSoft and others)
•  ETL routines, configuration files, OBIEE
repository and web catalogue are provided
•  Implementation includes:
o  Configuration phase
o  Customisation phase


OBI Applications and JDE
Sales Call Center Conformed Dimensions
§  Opportunities §  ACD Events §  Customer
§  Quotes §  Rep Activities §  Products
§  Pipeline §  Contact-Rep Snapshot §  Suppliers
Order Management §  Targets and Benchmark §  Cost Centers
§  IVR Navigation History §  Profit Centers
§  Sales Order Lines
§  Sales Schedule Lines §  Internal Organizations
§  Bookings Service §  Plant
§  Pick Lines §  Service Requests §  Customer Contacts
§  Billings §  Activities
§  Backlogs §  Agreements §  GL Accounts
§  Employee
Marketing Workforce §  Sales Reps
§  Campaigns §  Compensation §  Service Reps
§  Responses §  Employee Profile §  Partners
§  Marketing Costs §  Employee Events §  Campaign
Supply Chain §  Offers
Procurement and Spend §  Employee Position
§  Purchase Order Lines §  Order Misses
§  Purchase Requisition Lines §  Supplier Performance Hierarchy
§  Purchase Order Receipts §  Users
§  Inventory Balance
§  Inventory Transactions Projects Modular DW Data Model includes:
§  Expected To Complete
§  Project Profitability ~350 Fact Tables
Financials
§  Receivables ~550 Dimension Tables
Public Sector
§  Payables
§  Benefits ~5,200 prebuilt Metrics
§  General Ledger
§  COGS §  Cases (2,500+ are derived metrics)‫‏‬
§  Incidents
§  Profitability (Customer/Product)
§  Leads
~15,000 Data Elements
4

OBI Applications Architecture
§  Role Based Dashboards
§  Analytic Workflow
Oracle BI
Dashboards by Role Presentation §  Guided Navigation
Services
Reports, Analysis / Analytic
§  Security / Visibility
Workflows §  Alerts & Proactive Delivery
Administration

Metrics / KPIs §  Logical to Physical Abstraction Layer

Metadata
Oracle BI §  Calculations and Metrics Definition
Logical Model / Subject Areas
Server §  Visibility & Personalization
Physical Map §  Dynamic SQL Generation

Data Warehouse /
Data Model §  Abstracted Data Model
Direct §  Conformed Dimensions
Load Process
Access to §  Heterogeneous Database support
DAC

Source
Data Staging Area ETL §  Database specific indexing
Extraction Process
§  Highly Parallel
§  Multistage and Customisable
§  Multi Adapters and Universal Adapters

Oracle SAP R/3 Siebel JDE EssBase
Other
Federated Data Sources
5

Architecture
Informatica + DAC OBIEE

JDE Staging DW DW Answers Reports
tables tables tables
(aggreg
ates)
•  SQL Filters to •  Surrogate key •  Calculate •  Metric-specific •  Report definition
exclude certain generation balances, snapshots filters or logic
• Filters, groupings
records
•  Handle updates vs. •  Aggregation tables •  Organisation of
•  SQL Unions inserts (buckets, etc) dimensions and
metrics into subject
•  Date formatting •  If SCD2 required,
areas
handled here
•  Amount formatting
•  Description
•  Incremental
lookups (for codes,
conditions
etc)


•  Latest OBI Applications release is 7.9.6.3
•  Financial Analytics and Supply Chain and Order
Management Analytics include prebuilt ETL
routines for JDE (only configuration required for
the standard solution to work)
•  Configuration steps are described in the Oracle
BI Applications Configuration Guide
•  If other applications (e.g. Procurement) are to be
implemented, configuration and significant ETL
customisation is required


OBI Analytic Module Availability

Financial Analytics 7.9.6+ (Informatica)

Supply Chain Analytics 7.9.6.2+ (Informatica)

Enhanced Financial Analytics 7.9.6 (Red Rock developed)
- Enhanced GL Reporting
- Fixed Assets
- Projects

Procurement and Spend 7.9.6 (Red Rock developed)
Analytics


OBIA and JDE: customisation
scenarios
Although
the
OBAW
comes
with
many
Reports,
Dashboards
and
Star

Schemas,
you
may
need
to
customise
to
add:
• 
Category
Codes

• 
Data
from
Custom
Sources

• 
Data
From
Custom
Tables

• 
New
Facts,
Dimensions,
Hierarchies

Data
can
come
from
many
sources
• 
Sources
with
exis>ng
adapters
you
can
customise

• 
Sources
with
adapters
but
no
load
rou>ne
(Procurement)

• 
Unsupported
sources
(Universal
Adapter)


OBIA on JDE Gotchas
•  Packed Fields
•  JDE Date format and Number format
•  Capturing Change Data
•  Local Currency Codes
•  Error Handling
•  JDE Schema Information
•  Combining information from different subject areas
•  ETL Scheduling Options
•  Security integration


JDE Packed Fields
JDE stores certain fields with a fixed length (packed)

If these space are not removed, filters and navigations in OBIEE will fail (OBIEE
server automatically trims the spaces).

Recommendation: have a proper strategy in place to remove these fields.
Standard mappings may need to be reviewed as well.


JDE Date Format
Description
•  JDE stores date fields as C-YY-DDD, which is the
century after 1900, the year in that century and
the Julian date within that year
Problem
•  We need an Oracle formatted date, so that
functions like “ago” will work.
Resolution
•  date(1900+(field1/1000),1,1)+val(right(str(field1),3))-1


JDE Date Format
JDE stores dates in Julian format. Need to be converted to Gregorian to store in
the DW. Oracle provides a reusable mapplet for this purpose.

Recommendation: promote the use of existing reusable tools (such as mapplets)
within the development team. Do it early in the project, and encourage people to
create more tools and share with the rest of the team.


JDE Number Format
Description
•  JDE handles floating point numbers(decimals) as integers.
The information about how to interpret this number is stored
in the Metadata tables.
Problem
•  We need decimals for calculations and reporting
Resolution
•  A decimal shift mapplet is provided by Oracle which reads
the number of decimals to be shifted from metadata tables
and converts this integer to an actual meaningful floating
point number in BI Apps.


Capturing Change Data
Description
•  JDE does not reliably store audit information for
master data and transactions.
Problem
•  This makes it difficult to reliably capture change
data that has been added since the Last Update
Date to the warehouse.


Capturing Change Data
Two steps involved:
1.  SDEs
1.  When doing incremental loads, will pick new transactions comparing ‘Last
Updated’ field in JDE to the last extraction date (internal parameter)
2.  SILs
1.  Once the records are in the staging tables, the target tables will get updated
based on a lookup by a unique record identifier.

Recommendation: make sure this logic is defined correctly. Sometimes a mapping may be pulling
information from more than one table (F4301, F4311) and a record should be picked if ANY of the
source tables has changed. These problems may be hard to spot.


Error Handling
Description
•  JDE does not validate all the data that you might
be wanting to capture. i.e. Category Codes
•  DAC is configured to stop when it encounters and
error.
Problem
•  This can cause problems with the DAC which will
stop on the first occurrence of an error.


Error Handling
Standard OBI Apps does NOT perform error handling in ETLs
Informatica Parameter: ‘Stop on errors’ specifies number of non-fatal errors to
allow (reader, writer, dtm errors)
- 0 means it won’t stop.
The standard mappings use:
•  0 for SDE mappings (ETL does not stop)
•  1 for SIL/PLP mappings (ETL stops with 1st non-fatal error)
An alternative need to be considered:
•  Is the standard approach enough for your project needs?
•  Should some records be moved to a ‘rejected’ area and reinjected into
the process after analysis?
•  Trade-off effort/functionality
Recommendation: address this challenge early in the project. Different
stakeholders (sales, procurement, financials) may have different requirements.


JDE Schema Information
Description
•  JDE does not store tables and fields with
meaningful names.
Problem
•  This can make it difficult to build ETL and SQL.
Resolution
•  You need to interrogate the metadata dictionary in order to
find what you are looking for. Useful to maintain detailed
mapping and lineage documentation during the project.


JDE Schema Information
JDE stores information in four schemas
•  Data
•  Control
•  Data Dictionary
•  System

All four required in mappings (for example, Data Dictionary required to identify
number of spaces when performing decimal shifts.)

Recommendation: to simplify how connections are managed, create a database
user with synonyms for tables in all these schemas


Combining information from different
subject areas
In OBIEE 10.1.3.4.1, it’s not easy to combine information from different Subject
Areas into a single request e.g. combining GL data with Purchasing information

Prerequisites:
Conformed dimensions are required to ‘join’ the two worlds (a common Time
dimension, a Purchase Order number, etc)

Alternatives:
•  Design ‘ad hoc’ subject areas which combine information from both
areas. This the recommended approach.
•  There are ways of creating ‘one-off’ reports, based on logical SQL which
combines information from multiple subject areas. Not recommended.
Recommendation: when designing subject areas, think ahead to make sure you
have coverage. Are you planning to combine Sales info with Fixed Assets info?
You may need an ad-hoc subject area for this.


ETL Scheduling Options
Description
•  JDE Scheduler supports defining the batch jobs,
start time and frequency and executes batch jobs
as per the schedule.
Problem
•  JDE Scheduler does not support defining
dependencies and executing batch jobs based
upon the completion of pre-requisite batch jobs
but it can be customised to achieve this.


ETL Scheduling Options
Resolution
•  JDE scheduler can be customised to trigger non-JDE batch
jobs, for example DAC command line utility can be used to
trigger execution plans in OBI Analytics via JDE Scheduler
•  JDE Scheduler can be customised to trigger an Informatica
workflow, for example Data Migration and Integration type
ETL
•  It can also trigger SOA and B2B – Web Services
Integration
•  Multiple Time Zones can catered using multiple Batch
Servers for scheduling jobs
•  Daylight Savings support is available with the JDE
Scheduler


Security Integration
Description
•  Oracle BI Applications for
JD Edwards has no security
integration built in between
JDE and OBIEE
Problem
•  Oracle BI Applications for
JD Edwards has no security
integration built in between
JDE and OBIEE


Resolution
•  Any industry standard LDAP server can be used to store the users and
roles for both the applications
•  Users can use the same account to login into multiple applications,
reducing the need to remember multiple passwords and hence reducing
the password resets
•  Oracle package DBMS_LDAP can be used to retrieve the LDAP roles
into OBIEE in the desired format
•  Same set of Organisation roles can be consumed by JD Edwards and
OBIEE, for example a Procurement Manager who creates a Purchase
Order in JD Edwards can be set up to see the Purchase Order Dashboard
in OBIEE


Resolution
•  Single Sign-On products, for example Oracle Application Server can be
used to integrate JD Edwards and OBIEE, reducing the need for multiple
logins to access different applications, providing a unified interface
experience to business users
•  Users can be classified into Categories like Consumers, Intermediate
Users, Advanced Users and Administrators to associate varying level of
control in both the applications
•  OBIEE ships with a JSR-168 bridging portlet which can used to publish
the reports on portal along with JDE content


Deployment Options
• Standalone Dashboards
• Portal integration via JSR-168/WSRP
• Embedded Directly into JDE


Implementation Lessons Learnt
•  Get involved early in a JDE implementation
–  Set the right Strategy in place, and ensure critical designs go the
right way

•  Involve JDE Functional and Technical experts
–  Will make the most out of your solution
–  Reduces design time for new mappings
–  Creative solutions which may not be spotted by the DW team

•  Start small and iterate
–  If extending the model, gain confidence by addressing a specific
subject area, and building it end-to-end.
–  Do end to end mapping / development (i.e. Don’t try writing all
SDEs first)


OBIA implementation cycle
RAPID APPLICATION DEVELOPMENT
Pilot First Cut Release

PLAN
PLAN PLAN
REVIEW

REVIEW

REVIEW
DESIGN

DESIGN

DESIGN
BUILD
BUILD BUILD

8-10 weeks 8-10 weeks 8-10 weeks

HIGH PERFORMANCE TEAM


When to Buy and When to Build
Buy Build

§ BI
Solu>on
up
and
running
§ If
you
want
a
highly
customizable,

high
performing,
ﬂexible
and
scalable

§ Mainly
for
supported
ERP
source

solu>on.

§ Requirements
are
close
to
vanilla

§ Data
for
BI
does
not
mainly
come

§ No
exis>ng
BI
solu>on
from
supported
ERP
systems

§ Not
sure
what
you
want,
prepared
to
§ Matured
BI
systems
and
long

exploring
op>ons
successful
implementa>on
history

§ Want
to
ﬁne
tune
your
exis>ng
BI
to

beQer
handle/complement
exis>ng

systems


BI Analytics Availability
Human Supply Chain & Procurement
CRM Financials Projects
Resources Order Management & Spend

EBS R12.1.2 NEW NEW NEW NEW NEW

EBS R12.1.1

EBS R12

EBS 11.5.10 Service only

PSFT 9.1 NEW NEW NEW NEW

PSFT 9.0

PSFT 8.9

JDE E1 8.11SP1

JDE E1 8.12 NEW

JDE E1 9.0 NEW

JDE World A9.2

Universal

Siebel 8.1.1

Siebel 8.0 Not Applicable

Siebel 7.8

BI Analytics Accelerators for JDE
Human Supply Chain & Procurement
CRM Financials Projects
Resources Order Management & Spend

EBS R12.1.2 NEW NEW NEW NEW NEW

EBS R12.1.1

EBS R12

EBS 11.5.10 Service only

PSFT 9.1 NEW NEW NEW NEW

PSFT 9.0

PSFT 8.9

JDE E1 8.11SP1 REDROCK REDROCK REDROCK

JDE E1 8.12 REDROCK NEW REDROCK REDROCK

JDE E1 9.0 REDROCK NEW REDROCK REDROCK

JDE World A9.2 REDROCK REDROCK REDROCK

Universal

Siebel 8.1.1

Siebel 8.0 Not Applicable

Siebel 7.8

Red Rock BI Accelerators in Summary

•  JDE Analytics not yet available from Oracle
•  Reduced time to implement
•  Reduced total cost of ownership
•  Reduced project risk by implementing a proven
solution
•  Deliver OBIEE’s full product feature set


Reporting _ Paul Vella _ OBI Analytics for JDE.pdf

More Related Content

What's hot

Similar to Reporting _ Paul Vella _ OBI Analytics for JDE.pdf

More from InSync2011

Reporting _ Paul Vella _ OBI Analytics for JDE.pdf