Earnings Conference Call on Tuesday, July 31st 2012 at 4.00 pm IST

The Board of Directors of Hexaware Technologies is scheduled to meet on July 31^st, 2012 to consider the audited results for the quarter ended June 30^th, 2012 (Q2 2012).

The company is hosting an earnings conference call for investors and analysts on the same day to discuss the results.

Details of the conference call are as follows:

Date	July 31st, 2012
Day	Tuesday
Time	4:00 PM IST
Dial-in Access Numbers
Mumbai	Primary Access:+91 22 3065 0539 Secondary Access:+91 22 6629 0539
Hexaware Participants	Atul Nishar– Chairman P. R. Chandrasekar – Vice Chairman & CEO R. V. Ramanan – Executive Director & Head – Global Delivery Prateek Aggarwal – Chief Financial Officer Deependra Chumble– Chief People Officer Sreenivas V– Chief Strategy Officer

Replay Facility*

Playback number: +91 22 3065 1212

When prompted, please enter the Conference ID 32580 followed by #

*The replay facility of the conference call will be available 60 minutes after the call ends and for three days from July 31^st to August 02^nd 2012.

Participants are requested to kindly dial-in 10 minutes in advance.

Thank you!

For further information: please contact – Sreenivas V
[e-mail: sreenivasv@hexaware.com; phone: +91 99401 90091]

More: http://hexaware.com/news/earnings-conference-call-on-tuesday-july-31st-2012-at-4-00-pm-ist-2/

Quality Assurance and Testing Services: Strategy of Oracle BI Testing

This Document gives an overview of OBIEE Testing and commonly used in BI Components while doing validation.

1. Testing in Levels: In a typical OBIEE project, it is advisable to test in multiple areas rather than attempting to test everything at once.

a) The first set of tests can verify the accuracy of the column to column transport of the data between the source and target. This verification is typically done using SQL statements on the source and target databases.

b) The next step is to verify the accuracy of the repository (the .RPD file.) These tests will include testing with appropriate dimensional filters on the metrics and the formula used to compute those metrics. Testers can build two sets of comparable queries within the repository interface.

c) The next step in testing will be to verify the dashboard / reports against comparable queries on repository metrics. In these tests, testers verify dashboard charts / reports against corresponding results from queries they execute on metrics of the repository.

d) Finally, the functional interface tests will cover tests to verify the lookups, performance, ease of use, look and feel etc.

The first three types of tests are performed by testers who can create simple SQL statements.

Structure and organization of test cases:

The choices on test cases naming convention and structure can help organize the test artifacts better and aid a great deal in implementing the overall testing strategy.

For example: If the test cases are grouped based on the nature of the tests, like, source to target verification, RPD metrics tests, functional, security, performance and usability, it would be easier to pick and choose the tests based on the testing context and tester capabilities.

1. User acceptance criteria:
Users typically have an existing legacy mechanism to verify if what is displayed in the new solution makes sense. Testers should dig into this and understand how the end users built the project acceptance criteria. Testers should challenge the assumptions made by the business community in deriving the acceptance criteria. This activity helps get an end user perspective built into the testing efforts from early on.

2. Validating Master Detail Report: 
Master Details linking of views allows you to establish a relationship between two or more views such that one view, called the master view, will drive data changes in one or more other views, called detail views.

3. Time series functions validation: Time series functions provide the ability to compare business performance with previous time periods, allowing you to analyze data that spans multiple time periods.

Time series functions enable comparisons between current sales and sales a year ago, a month ago, and so on.

a. Ago: With ago function we can compare period to period
b. To date: Time series functions enable comparisons between current sales and sales a year ago, a month ago, and so on.
c. Period rolling: The PERIODROLLING function does not have a time series grain; instead, you specify a start and end period in the function.

4. Oracle bi-publisher validation: Oracle BI Publisher known as XML Publisher offers efficient scalable reporting solution available for complex, distributed environments. It provides a central architecture for generation and delivering information to employees', customer and business partners both security and in the right format.

Quality Assurance And Testing Services: OBIEE Validations

Hexaware has developed a variety of accelerators that combine Oracle's technology with Hexaware's functional and technical expertise to effectively meet your business needs. Oracle E-business suite range consists of financials, supply chain, manufacturing, HRMS & CRM.

Source to target validation: Here source is represented by metadata repository and Target represents OBIEE Reports & Dashboards, BI Publishers.

1. Presentation layer object validation:
This is the layer of the logical business model that is accessible for the client through the structure query Language better known as the logical SQL. The presentation is the appropriate layer to set user permissions and to validate user permissions to reports.

2. Categorizing the metrics:
It is important to classify the metrics from multiple perspectives such as, their frequency of use, potential performance impacts, and complexity of calculations involved. Such a classification helps drive priority of testing

3. Dashboard charts and filters criteria:
User interface testing should encompass tests with multiple options in the available filter criteria. OBIEE gives enough drilldown features to verify the underlying data on the clickable components of the charts. Test cases written should be detailed enough to verify data aggregated at various layers.

4. Filter Validation
. Validate the entire filters which are available on report. Example refers below report and its filter
. Example: For Performance Measure filter- Validate filter contents against report requirement and database

Filter types:
Local filters: Filtering the records in the report level.
Global filters: Filtering the records based on user selection in Dashboard.

Dashboard Validation:
When a user selects certain request that need to display the exact results in the dashboard.

5. Data level security:
Data level security validation means user will be able to see only particular data for the given permission
Example: Both the Eastern and Western region Sales Managers will be seeing the same reports but the Data visible to them in the reports will be Eastern and Western region Sales data respectively.

Object Level security: Need to validate whether the particular user is able to access the particular dashboard or folder etc.
Example: For example, users in a particular department can view only the subject areas that belong to their department.

6. Bursting the reports:
Bursting the reports means distributing the reports based on the regions. 
Example: If there are 4 regional reports, validate to burst the reports (based on East, West, South, North regions).

7. Buzz Matrix validation: 
Need to validate the alerts in the Dashboard.

Example: We are running stock market and CEO is very much interested to know today's business weather, has it reached a certain level that which he expects compared to the last week. If the level has reached to a certain level in Dashboard Buzz (Alert), it should raise an alert saying that it has reached the level in such a way the buzz matrix validates.

Marketing Automation in B2B – Separating the Wheat from the Chaff

The B2B landscape in its inherent form is a complex jar of beans primarily because the initial connection needs lots of nurturing with the right mix of appropriate communication to ensure the “best weather” for sales interaction. Marketers not only have to measure outcomes right up to revenue but also find the “sweet spot” for marketing and sales to drum up the right notes.

The year 2009 and the first half of 2010 saw a marked shift towards marketing automation worldwide. All of this has helped channelize information and reach out to prospects better, yet it is pertinent to note the today’s internet savvy prospect is also armed with qualifying information about your brand, your products and your competitors as never before. To get inside the mind of the B2B buyer, marketers not only need to understand his intent from his digital body language but also ensure that automated lead generation processes in place scale up in terms of the following pertinent factors at any point of time.

• Are lead recycling programs in place for not-sales-ready leads?
• Has social media, inbound marketing and marketing automation been integrated seamlessly?
• Is your marketing communication supported by buyer-centric collaterals that help the buyer decide in your favor?
• Has your data been data washed and scrubbed clean?
• Does your web metrics provide actionable information for user profiling and conversion?
• Are sales and marketing on the same latitude to proving your prospect the best buying experience?
• Does your Social media spin influence the markets conversation about your brand effectively?
• Is your opt-in list getting fresh brew in the form of persuasive communication and supporting newsletter value?
• Is your marketing funnel measurable and process definitions flexible to innovation?
• How effective is your conversation model, does it ensure that you are at top of mind when prospects decide to bite the bait?
• Are you able to capitalize on marketing automation’s great benefit – reporting effectively and use it as a strategic tool?
• Does your data-centric marketing plans lead the way for greater customer intelligence since value of data will not be a constant ?

The above are just a few important cogs that can make or break your lead generation wheel. As marketers brace themselves to capitalize on marketing automation to enhance pipeline opportunities, trends all point to an explosive growth in marketing automation adoption. It is highly imperative that automation vendors provide more sophisticated reporting, better sales engagement processes and social media integration.

To help marketing efficiently separate the wheat from the chaff, marketing automation should not just serve as a driver of operational efficiency but more importantly enhance continuity of dialogue with prospects throughout the decision making/buying cycle at all relevant touch points.

Ultimately it is all about the harvest – the pipeline and revenue, the executive leadership would not mind how you do it.