Reporting Paul Vella Obi Analytics For Jdepdf4306 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
o
Configuration phase
Customisation phase
OBI Applications and JDE

Sales
Opportunities
Quotes
Pipeline
Order Management
Sales Order Lines
Sales Schedule Lines
Bookings
Pick Lines
Billings
Backlogs
Marketing
Campaigns
Responses
Marketing Costs
Supply Chain
Purchase Order Lines

Purchase Requisition Lines
Purchase Order Receipts
Inventory Balance
Inventory Transactions
Financials
Receivables
Payables
General Ledger
COGS
Profitability (Customer/Product)
Call Center
ACD Events
Rep Activities
Contact-Rep Snapshot
Targets and Benchmark
IVR Navigation History
Service
Service Requests
Activities
Agreements
Workforce
Compensation
Employee Profile
Employee Events
Procurement and Spend

Order Misses
Supplier Performance
Projects
Expected To Complete
Project Profitability
Public Sector
Benefits
Cases
Incidents
Leads
Conformed Dimensions
Customer
Products
Suppliers
Cost Centers
Profit Centers
Internal Organizations
Plant
Customer Contacts
GL Accounts
Employee
Sales Reps
Service Reps
Partners
Campaign
Offers
Employee Position
Hierarchy
Users
Modular DW Data Model includes:
~350 Fact Tables
~550 Dimension Tables
~5,200 prebuilt Metrics
(2,500+ are derived metrics)
~15,000 Data Elements
OBI Applications Architecture

Dashboards by Role
Oracle BI
Presentation
Services
Role Based Dashboards

Analytic Workflow
Guided Navigation
Security / Visibility
Alerts & Proactive Delivery
Oracle BI
Server
Logical to Physical Abstraction Layer

Calculations and Metrics Definition
Visibility & Personalization
Dynamic SQL Generation
Abstracted Data Model

Conformed Dimensions
Heterogeneous Database support
Database specific indexing
Logical Model / Subject Areas

Physical Map
Metadata
Metrics / KPIs
Data Warehouse /
Data Model
Direct
Access to
Source
Data
Load Process
Staging Area
ETL
DAC
Administration
Reports, Analysis / Analytic

Workflows
Extraction Process
Oracle SAP R/3
Siebel
JDE
EssBase
Federated Data Sources

5
Highly Parallel
Multistage and Customisable
Multi Adapters and Universal Adapters
Other
Architecture
Informatica + DAC
JDE
Staging
tables
SQL Filters to
exclude certain
records
SQL Unions
Date formatting
Amount formatting
Incremental
conditions
OBIEE
DW
tables
DW
tables
(aggreg
ates)
Answers
Surrogate key
generation
Calculate
balances, snapshots
Metric-specific
filters or logic
Handle updates vs.

inserts
Aggregation tables
(buckets, etc)
Organisation of
dimensions and
metrics into subject
areas
If SCD2 required,
handled here
Reports
Report definition
Filters, groupings
Description
lookups (for codes,
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

- Enhanced GL Reporting
- Fixed Assets
- Projects
7.9.6 (Red Rock developed)
Procurement and Spend

Analytics
7.9.6 (Red Rock developed)
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.

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.

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 wont 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.

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 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, its 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.

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.

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. Dont try writing all
SDEs first)
OBIA implementation cycle

RAPID APPLICATION DEVELOPMENT
First Cut
BUILD
8-10 weeks
BUILD
8-10 weeks
REVIEW
PLAN
DESIGN
REVIEW
PLAN
DESIGN
REVIEW
PLAN
Release
DESIGN
Pilot
BUILD
8-10 weeks
HIGH PERFORMANCE TEAM
When to Buy and When to Build

Buy
Build
BI Solu>on up and running

Mainly for supported ERP source
Requirements are close to vanilla
If you want a highly customizable,

high performing, exible and scalable
solu>on.
No exis>ng BI solu>on
Data for BI does not mainly come

from supported ERP systems
Not sure what you want, prepared to

exploring op>ons
Matured BI systems and long

successful implementa>on history
Want to ne tune your exis>ng BI to
beQer handle/complement exis>ng
systems

BI Analytics Availability
CRM
EBS R12.1.2
Financials
Human
Resources
Supply Chain &

Order Management
Procurement
& Spend
Projects
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
EBS R12.1.1
EBS R12
EBS 11.5.10
PSFT 9.1
Service only
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
Siebel 7.8
Not Applicable
BI Analytics Accelerators for JDE

CRM
EBS R12.1.2
Financials
Human
Resources
Supply Chain &

Order Management
Procurement
& Spend
Projects
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
NEW
REDROCK
REDROCK
EBS R12.1.1
EBS R12
EBS 11.5.10
PSFT 9.1
Service only
PSFT 9.0
PSFT 8.9
JDE E1 8.11SP1
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
Siebel 7.8
Not Applicable
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 OBIEEs full product feature set

Reporting Paul Vella Obi Analytics For Jdepdf4306 PDF

Cargado por

Información del documento

Descripción original:

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Reporting Paul Vella Obi Analytics For Jdepdf4306 PDF

Cargado por

Copyright:

Formatos disponibles

Best practices for implementing

OBI Apps with JD Edwards

OBI Applications in a nutshell

OBI Applications and JDE

Purchase Order Lines

Procurement and Spend

OBI Applications Architecture

Role Based Dashboards

Logical to Physical Abstraction Layer

Abstracted Data Model

Logical Model / Subject Areas

Reports, Analysis / Analytic

Oracle SAP R/3

Federated Data Sources

Handle updates vs.

OBI Applications and JDE

OBI Applications and JDE

Supply Chain Analytics

Enhanced Financial Analytics

7.9.6 (Red Rock developed)

Procurement and Spend

7.9.6 (Red Rock developed)

OBIA and JDE: customisation

Data can come from many sources

OBIA on JDE Gotchas

JDE Packed Fields

JDE Date Format

JDE Date Format

Recommendation: promote the use of existing reusable tools (such as mapplets)

JDE Number Format

Capturing Change Data

Capturing Change Data

JDE Schema Information

JDE Schema Information

Recommendation: to simplify how connections are managed, create a database

Combining information from different

ETL Scheduling Options

ETL Scheduling Options

Oracle package DBMS_LDAP can be used to retrieve the LDAP roles

Same set of Organisation roles can be consumed by JD Edwards and

Single Sign-On products, for example Oracle Application Server can be

Users can be classified into Categories like Consumers, Intermediate

Implementation Lessons Learnt

Involve JDE Functional and Technical experts

Start small and iterate

OBIA implementation cycle

HIGH PERFORMANCE TEAM

When to Buy and When to Build

BI Solu>on up and running

If you want a highly customizable,

Data for BI does not mainly come

Not sure what you want, prepared to

Matured BI systems and long

Supply Chain &

JDE World A9.2

BI Analytics Accelerators for JDE

Supply Chain &

JDE World A9.2

Red Rock BI Accelerators in Summary

JDE Analytics not yet available from Oracle

También podría gustarte