Companies rely on their supply chain to efficiently meet their demand for goods and services. Managing those suppliers to ensure that they are meeting corporate purchasing targets is critical to the overall suc-cess of the company. The goal of this Solution is to provide manage-ment and buyers with up to date, accurate information on how their suppliers.

How are my suppliers and/or buyers performing against my cost, quality, and timeliness targets?

Supplier Analysis

100% Mobile BI: Desktop, Tablet, Smartphone

SupplierBuyersMaterials & ProductsBusiness UnitAging Buckets based onPromise Date and Receipt Date

Prebuilt Analysis Examples

Overall Quantities & AmountsPurchased & Received% Rec. On Time, Early & LateActual vs. Standard Cost MetricsMetrics over Rejected Receipts

Metrics Examples

Multiple Data Sources

iPad

AT&T 12:34 PM

“ERP is great for transactional pro-cessing and linking operational areas, but it does a terrible job with reporting. Halo BI unlocks the data for users so they can move the business forward.”

Glenn Pinnel, Applications Director, Alpharma

JD EdwardsMRPExcelLegacy Systems and more!

Business IntelligenceHalo

JD Edwards

Supplier Analysis

Halo BI’s supplier scorecard is used to develop a Purchasing Analysis environment from JD Edwards source data. This document describes the ‘out of the box’ features provided in the Halo BI Revenue Solution. Once installed, the template is further customized according your unique installation and their business requirements for analytics.

Supplier Scorecard tracks purchasing activity using Closed Purchase Orders (POs) from F4311 (Purchase Order Details) and PO Receipts from F43121 (Purchase Order Receiver File). The template can leverage the PCDAYL and PCDAYE settings from table F40390 (Item/Supplier Relationship) to define the tolerance for days.

JD Edwards Transaction Data Sources

JD Edwards Transaction Data Sources Sales Reporting Dimensions

Closed Purchased OrdersPurchase Order Receipts

User Defined Control File

Business Unit MasterCompany MasterAddress Book

Item MasterLine Type MasterAddress by Date MasterParent Child Cross ReferenceLine Type MasterItem Master

Item BranchItem Cost MasterItem Supplier

F0005

F0006F0010Address Book

Item MasterLine Type MasterAddress by Date MasterParent Child Cross ReferenceLine Type MasterItem Master

Item BranchItem Cost MasterItem Supplier

Table UtilizedF4311-Pruchase Order DetailsF4311-Pruchase Order Details

Business IntelligenceHalo JD Edwards

Supplier Analysis Technical Overview

Business IntelligenceHalo JD Edwards

Supplier Analysis Technical OverviewDimensions & Attributes

Supplier

Bill To Customer &Ship To Customer

Product

Business Unit

Order Type

Doccument Type

Dimension key is the Address Number from the Address Book, which joins to the Bill To Customer number in the Sales Order tables. Dimension attributes are extracted from the category codes utilized in the Address Book, the geographic location in the Address by Date Master, and the User Defined Control table.

The dimension key is the Short Item Number from the Item Master, which joinsto the Short Item Number in the Sales Order tables. The dimension attributes are extracted from the category codes utilized in the Item Master and the User Defined Control table.

The dimension key is the Business Unit code from the Business Unit Master, which joins to the Business Unit in the Sales Order tables The dimension attributes are extracted from the category codes utilized in the Business Unit Master, Company Master, and the User Defined Control table.

The dimension key is the Document Type key from the Order Types defined in the User Defined Control table, which joins to the Document Type code in the Sales Order tables.

The dimension key is the Order Type key from the Order Types defined in the User Defined Control table, which joins to the Order Type code in the Sales Order tables.

Line Tyoe

Aging Aging buckets defined based upon the promise date and the actual received date. These can be customized according the client requirements. This will show how many orders were received within what time frame, for example: On Time, 1 Week Early, 2 Weeks Early, 1 Week Later, 2 Weeks Late, etc.

TThe dimension key is the Document Type key from the Order Types defined in the User Defined Control table, which joins to the Document Type code in the Sales Order tables.

Time

PO Date The dimension key is the Purchase Order date for both Receivers and Pos. The solution assumes a calendar Time and builds the Time attributes internally, using the dates from the Purchase Order table as the source key. However, the solution can be further fine tuned to extract the Fiscal Calendar table (F0008) from the client’s JDE source system.

The dimension key is for Received Date for Receivers. For Purchase Orders, it is the Purchase Order Date. The solution assumes a calendar Time and builds the Time attributes internally, using the dates from the Purchase Order table as the source key. However, the solution can be further fine tuned to extract the Fiscal Calendar table (F0008) from the client’s JDE source system.

4885 Greencraig Ln. San Diego, CA 92123www.halobi.com | 858.565.4238 | info@halobi.com

Halo Business Intelligence

Contact UsSchedule a demoRead Case Studies

PO Receipts Include:(not limited to)Receipt Line Count

Late Receipt

Numbers of Receipts

Count based upon receipt and original promise dateOn time—Partial Shipment

On Time—Full Shipment

Shipment count of received on time, but qty ordered not qty receivedShipment count received on time and qty ordered = qty received

Early Receipt

Rejected

Shipments received before promised date minus days allowed early

Number of lines with quantity rejected or needed reworkAccepted

Quantity Received

Number of lines with no rejected quantity or rework

Total quantity received

PO Line Count

PO Extended Cost

Number of closed PO lines

Actual extended costPO Standard Extended Cost

Quantity On PO

Standard extended costQuantity Ordered

Actual Cost More Than Standard

Actual Cost Less Than Standard

Line count where actual cost was greater than standard cost

Line count where actual cost was less than standard costActual Cost Equal Standard

Standard Cost Not Available

Count of lines where actual cost was equal to standard cost

Count where standard cost not set up for this itemJD Edwards Lead Time

Calculated Lead Time

Lead time set up in F43090 for this item

Lead time based upon order date and promise date

Measures for CLOSED Pruchase Orders

Late Receipt %

On Time Partial %

Average Actual Cost

Average Standard CostOn Time Full %

Early Receipt %

On Cost %Average Lead Time JDE

Receipt Rejected %

Receipt Accepted %

Average Lead Time Calculated

Quantity Open Cost Under Standard %Cost Over Standard %

Cube Calculations

Business IntelligenceHalo JD Edwards

Supplier Analysis Technical Overview

Halo BI is available through TeamCain For more information, please contact TeamCain at 1.800.861.7628 ext. 246, or email michael_guerin@teamcain.com

re

commended

by

this product is

endorsed and