|
|
 |
|
|
|
Answers...
|
|
|
|
|
| A: |
BBB stands for
the commonly used acronym "Bookings,
Backlog and Billings". It is a Sales
Order and Revenue Reporting software
solution for Oracle Applications that
converts and simplifies transacted ERP data
into business information, presenting
business users with a fast, easy and
familiar way to access critical BBB
information. Back to
Top
|
|
|
| |
|
|
|
|
| A: |
Due to a lack
of order management reporting in Oracle
E-Business Suite, we have developed
an integrated suite of business
views to provide
what we call BBB Intelligence.
Our solution provides:
- A configurable transaction history
engine that captures changes made to
orders. It essentially turns Order
Management into a sub ledger.
- A suite of summary and detail BBB
report templates and views
for bookings, backlog, shipments,
billings, revenue, cost of goods sold and
sales credits.
- Flexible business views for ad hoc queries,
custom reports and/or data mining tools
like Discoverer.
- Report Templates that are designed for
use with Oracle Discoverer to facilitate
rapid report deployment.
- Report Templates and views provide accurate, real
time and meaningful data.
Back
to Top
|
|
|
| |
|
|
|
|
| A: |
Yes. Our BBBi
solution provides a Booking Transaction
History module which tracks changes to Order Header,
Sales Credit, and Line attributes that
impact order value. It may
be configured to track changes made to ANY
column in these tables.
It comes pre-configured to track changes
that affect order value in
terms of change date and sales credit
allocation. Back to
Top
|
|
| |
|
| |
|
|
|
|
| A: |
BBB
Intelligence is completely written with
native Oracle software development tools:
PL/SQL, Oracle Reports and Oracle Forms.
Thus, it integrates seamlessly within the
Oracle Applications and requires no
additional expertise to support. Your Oracle
Applications IT staff will require no
additional programming knowledge to support
our solution. And, the solution follows the
Oracle CEMLI guidelines for custom
extensions. Back to
Top
|
|
| |
|
| |
|
|
|
|
| A: |
It is
seamlessly integrated within Oracle Order
Management. Forms are accessible
from within your standard menus. Our database views are
available for use with SQL*Plus, or may be used
within custom reports, forms, or programs to
ensure data accuracy, consistency and speed
custom development. Additionally, the views
provide an excellent mechanism for end users
to easily retrieve critical BBB data using
any number of query tools, such as Oracle
Discoverer, Brio or Business Objects. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
The BBBi
solution resides within your applications
database. It is comprised of tables, views,
database functions, procedures and triggers.
At the core of the solution is a layer of
PL/SQL code that dynamically generates the
database objects required to interpret
Oracle transactions and configurations, and
to output the translated data via views,
reports and forms for presentation to the
user. BBBi is registered as an Application
within the Application Object Library. The
solution installs and maintains a number of
AOL objects, such as concurrent programs,
value sets, menus, forms and a custom BBB
application, to seamlessly integrate with your
Oracle Application instance. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
Since Oracle
Order Management does not maintain a sub
ledger like history
of all changes made against a sales order, any
change that is made merely overwrites the
existing data. Thus an order booked on
January 31st for $500, may be modified on
February 7th to reflect an increase in order
value to $1,000. Unfortunately, Oracle will
assign the full $1,000 to January 31st,
instead of properly allocating $500 to
January 31st and $500 to February 7th.
Without a history of changes, it is
impossible to accurately determine net
bookings for a period. Modified bookings
today may impact your bookings reports from
prior periods! It is also impossible to
derive historical values for backlog without
this critical audit trail.
This problem is also true when modifying
sales credits. The credits are merely
overwritten, and all historical credit
allocations are lost. This can lead to much
confusion when trying to calculate bookings
for commissions.
Release 11i & 12 do provide limited change
audit functionality in an Order History
table. However, this data is limited and captured in
such a way that is challenging to extract
into usable financial reports. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
Yes. Our
solution supports both Descriptive
Flexfields and Key Flexfields, providing
filter, grouping and sorting options by
Sales Territory, Item Category, and GL Account,
etc. The output is provided in two formats:
1) As a single string of concatenated
segments, and/or 2) As individually named
segments. This provides maximum flexibility
to the user to access and present their data
in a way that is most meaningful to their
needs. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
Yes. Our
solution provides all currency values in
terms of the functional currency (that is
the currency tied to the Set of Books for
that operating unit). Our views are created
both at the Set of Books and the database
instance level, so they may be restricted to
a Set of Books, or span all data across the
entire instance to facilitate
global reporting requirements. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
Yes. Our
solution easily provides an executive level summary
for Bookings, Shipments, Revenue and/or Backlog
data for any period range all in one report
or as individual reports.
View Example. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
No. We have
rigorously performance tested our solution.
In a simulated production test environment
where we created and/or updated over 1400
orders in one hour, we were unable to detect
an impact on performance. As for space
concerns, our transaction table typically
grows at about 1.1 to 1.3 times the rate of
your order lines table, yet since it
contains significantly fewer columns than
the order lines table, it usually remains
smaller in physical size than the order
lines table. We have never had a transaction
history performance or space issue with our
customers. We've have customers that have
used BBBi since Release 10.5 of E-Business
Suite. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
Our database
views are ideal for use with elaborate
reporting and query tools, like Oracle
Discoverer. These
user friendly reporting utilities support drag and drop
report building with easy to use drill down,
sort, filter, matrix, chart and role
capabilities. They usually provide
spreadsheet like results that can be easily
exported to Excel. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
Our solution
is integrated with Oracle E-Business Suite. If
you are running a web based version of
Oracle, then our solution will be accessible
via the web as well. From a strictly
reporting standpoint, BBB views can be
imported into Oracle Discoverer, which has
both a PC desktop version and a web based
version for access from any web browser. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
No. Our
solution is a real time data transformation
and delivery mechanism that provides ready
to use reports and views upon installation.
It is integrated within your Oracle
Apps instance, providing a layer of logic
that translates your Oracle transactions and
setups into meaningful BBB data. There are
no additional hardware or software
requirements, no complex setups,
configurations or interfaces to build. It's
end user ready!
Depending on your reporting requirements,
BBB Intelligence can replace a data
warehouse, be used to supplement a data
warehouse, or feed a data warehouse. Back
to Top
|
|
| |
|
| |
|
|
|
|
| A: |
Compare
BI solutions Side by Side
Noetix
Views:
Our solution is similar to Noetix in that we
both offer database views that simplify
complex relational database structures into
simple business meaningful views that
end users can easily understand and use
without SQL knowledge.
However, our solution is designed to be a
complete Book to Bill revenue reporting
solution. It provides ready to use reports,
so no other software knowledge is necessary. Where
Noetix provides a broad range of views
spread horizontally across the all the
Applications, we provide a more vertical and
comprehensive focus on Sales Order and
Revenue Data. We also provide Sales Order
Audit History, where we actually capture and
report changes to sales orders in our transaction
table. You can't calculate accurate
historical bookings and backlog without it!
Oracle Discoverer: Discoverer is a query
tool. It requires implementation, SQL
programming and setup by experienced
technical staff. It is often used with
database views, so that end users can access
and run queries. It does not provide any
intelligence as far as how to write, access
or interpret the complex relational
structures that exist in the database. For
this reason, our customers use our
pre-defined BBB views with Discoverer to
provide their end users with a flexible way
to access accurate BBB data. It only takes a
few minutes to import and begin to use our
views with Discoverer.
Business Objects: Business Objects is a
combination of Noetix and Discoverer. It's a
user friendly query tool that also provides general
views for business purposes, but does not
provide comprehensive BBB data or Sales
Order Audit History. Users and IT staff will
typically have to write and/or modify the
base Business Objects views to meet their
requirements.
Essbase: This is a data warehouse with an
OLAP front end. It's a powerful analysis
tool if you plan to build your own
interfaces and logic from Oracle, you don't
need real time data, and you have a large
budget and 6 months or more to deliver a
solution.
Brio: A reporting/query tool that
facilitates building SQL queries using a
GUI, drop and drop front end. It provides no
transformation logic and no Order Audit
History capabilities. Back
to Top
|
|
| |
|
| |
|
|
| |
|
|
|
|
| A: |
Oracle
Applications releases 10.7, 11 and 11i. [12
coming soon!] |
|
| |
|
|
|
|
|
| A: |
No. BBBi is designed to integrate with Oracle
Applications without interfering with any
standard functionality. It reads Oracle base
tables, but it only writes to BBBi custom
tables. BBBi is designed to meet the CEMLI
Custom Extension Coding Standards set forth by
Oracle. It will not impact or violate your
Oracle Support agreement or your ability to
upgrade to future Oracle releases.
|
|
| |
| Top
of Page |
|
|
| |
|
|
|
