undertand in ght mom se 12

Understanding the HTMomse12 Output for Order Management

An Oracle White Paper

February 2012



Overview ........................................................................................... 3

Introduction ....................................................................................... 3

How to Run ....................................................................................... 3

Reviewing the Output ........................................................................ 4

Section Overviews ......................................................................... 4

Interpreting the Data ...................................................................... 6

Appendix A Column Descriptions ................................................. 11

Appendix B - Reported Warnings / Errors ........................................ 14


Overview

The HTMomse12.sql script output is used to troubleshoot issues specific to a single order. This script will collect

information related to a sales order transaction across multiple products and associated Workflow processes. The script

should be run whenever there are problems related to a sales order transaction, including processes such as Booking,

Picking, Shipping, Invoice Interface, etc.

Script is available via note HTMOMSE Sales Order Diagnostic Script (Doc ID 133464.1). For a list of additional

diagnostic scripts refer to note ORDER MANAGEMENT - DIAGNOSTICS LIBRARY (Doc ID 741642.1).

Introduction

The purpose of this script is to assist in finding and fixing data issues for all phases of an order. It consists of many

sections. What sections are needed is dependent on the phase the order is in. For example if the order is in Entered status,

only header and line information will be available.

This script has several versions and variations. HTMomse11i.sql is for application version 11.5.10 and the current request

Diagnostic: OM Order Information (Reports, Requests > Run Requests > Single Request) are similar to the

HTMomse12.sql. There are variations of format and content between these reports. The main difference of

HTMomse12.sql and Diagnostic: OM Order Information is that HTMomse12 also reports many error and warning

conditions.

The scope of this paper is limited to a general overview and guidelines to interpreting the data as it is related to the Order

Management product.

How to Run

When executing the script in SQL*Plus, a series of parameters must be entered. Whether or not data is printed based on the parameter values depends on the stage of the order. For example if the header and lines have only been entered, Receivables information will not exist. With the exception of identifying the correct order, the values entered for the remaining parameters will impact the runtime performance of the script and the amount of data returned. Unless orders are extremely large, it is recommended to run the script for all order lines and to print all data. The first prompt is the for the order number Please enter Sales Order number:. Once entered, one or more header IDs will be returned. If there is only one ID returned, it is not necessary to enter it before pressing enter at the prompt Please enter HEADER_ID from list above (optional):. In cases of multiple IDs, determine and enter the correct ID based on Order Type and Organization. All of the Line IDs associated with the order will be returned under the section LINE_IDs ASSOCIATED WITH THIS ORDER NUMBER. Unless the order is very large, leave the Line ID prompt Please enter LINE_ID from list above(leave blank for all lines): blank and press Enter. In some cases it is best to enter the appropriate Line ID to limit the amount of data returned.


The following list of prompts determines what additional information is printed. Unless instructed by Oracle Support, always take the default value of Yes. If no data exists for the section, it will be left blank and only the section header is printed. Changing the defaults to N (no) may be necessary when the order is extremely large and issue is not in that section. Example: order with multiple lines, some already invoiced and issue occurs during Order Management Interface, printing Receivables information may not be necessary.

Do you want validation performed on this order (Default=Y):

- Checks the data providing errors and warnings to be reviewed. Some may be resolved by editing the data. Others may require a data fix.

Do you want WorkFlow information printed? (Default=Y): - Includes Workflow data the output. It is recommended to always print this information.

Do you want Pricing information printed? (Default=Y): - Pricing information based on the calculation data is it pertains to the final selling price for the item.

Do you want Purchasing information printed? (Default=Y): - Purchasing data is refers to internally linked purchase orders.

Do you want Receiving information printed? (Default=Y): - Receiving data pertains to RMA when the line(s) have been received into inventory.

Do you want Work In Progress information printed? (Default=Y): - WIP data is included in the output for configured items only.

Do you want Inventory information printed? (Default=Y): - Inventory data is important once the line has been scheduled. It is recommended to always print this information.

Do you want Receivables information printed? (Default=Y): - Receivables data is only available once the lines have been interfaced.

Reviewing the Output

Section Overviews

Script output is logically grouped. Each group consists of the data related to its subject. The following headings do not appear with the script.

Confirmation The first section is a confirmation of the parameters entered. This section also contains the DATABASE IDENTIFICATON. Verify the DB Name is the instance reported with the issue. Parameters match those entered at the script prompts. Listed also are the order header and lines.

Header The Header section consists of selected data from Order Management, workflow, holds, processing messages and pricing adjustments for the order header. The header section consists of: OE_SETS (SET) OE_ORDER_HEADERS (ORD) WORKFLOW ORDER STATUS WORKFLOW ORDER NOTIFICATION INFORMATION (WFN) WORKFLOW ORDER LEVEL ERRORS WORKFLOW ACTIVITY STATUS FOR ORDER ERROR PROCESS GENERIC HOLDS (ORDER AND/OR LINES) HEADER PROCESSING MESSAGES HEADER PRICE ADJUSTMENTS (ADJ)


Line The Line section consists of selected data from Order Management, workflow, holds, processing messages and pricing adjustments for each line. In the case of a configured item, it also contains information for the items options and optional items. OE_ORDER_LINES (LIN) OE_ORDER_LINES_HISTORY (HIL) WORKFLOW LINE STATUS WORKFLOW LINE STATUS ERRORS WORKFLOW ACTIVITY STATUS FOR LINE ERROR PROCESS LINE SPECIFIC HOLDS (LINES ONLY) LINE PROCESSING MESSAGES APPLIED LINE PRICE ADJUSTMENTS (ADJ) UN-APPLIED LINE PRICE ADJUSTMENTS (ADJ). OE_DROP_SHIP_SOURCES (SRC)

Purchasing This data is from Purchasing associated with the order for purchase orders and requisitions.

PO_REQUISITIONS_INTERFACE_ALL (RQI) PO_INTERFACE_ERRORS_ALL (POE) PO_REQUISITION_HEADERS_ALL (RQH) PO_REQUISITION_LINES_ALL (RQL) WORKFLOW REQUISITION APPROVAL STATUS WORKFLOW REQUISITION APPROVAL NOTIFICATIONS WORKFLOW REQUISITION APPROVAL ERRORS PO_HEADERS_INTERFACE (PHI) PO_LINES_INTERFACE (PLI) PO_INTERFACE_ERRORS_ALL (POE) PO_HEADERS_ALL (POH) PO_LINES (POL) WORKFLOW PURCHASE ORDER APPROVAL STATUS WORKFLOW PURCHASE APPROVAL NOTIFICATIONS WORKFLOW PURCHASE APPROVAL ERRORS

Receiving Receiving shipment line and transaction information from Purchasing. RCV_SHIPMENT_LINES (SHL) RCV_TRANSACTIONS (RCV) RCV_TRANSACTIONS_INTERFACE (RTI)

Inventory part 1 Part 1 contains the reservation information made during scheduling or pick release. MTL_SUPPLY (SUP) MTL_RESERVATIONS (RES)

Work In Progress This section is populated with the WIP information for configured models. WIP_JOB_SCHEDULE_INTERFACE (WJS) WIP_INTERFACE_ERRORS (WIE) WIP_DISCRETE_JOBS (WIP) DISCRETE JOB TRANSACTIONS (DJT)

Shipping Execution


The Shipping section contains information of the delivery detail, deliveries and trips. Also included is information for containers, serial numbers and freight cost. WSH_TRIPS (TRP) WSH_TRIP_STOPS (STP) WSH_DELIVERY_LEGS (LEG) WSH_NEW_DELIVERIES (DEL) WSH_DELIVERY_ASSIGNMENTS (ASG) ORGANIZATIONS (ORG) WSH_DELIVERY_DETAILS (DET) WSH_DELIVERY_DETAILS (CONTAINERS) WSH_SERIAL_NUMBERS (WSN) WSH_FREIGHT_COSTS (CST)

Inventory part 2 Inventory part 2 is populated as the item is picked through shipped. MTL_TRANSACTIONS_INTERFACE (MTI) MTL_MATERIAL_TRANSACTIONS_TEMP (TMP) - UNPICKED LINES MTL_MATERIAL_TRANSACTIONS (TRN) - PICKED LINES MTL_UNIT_TRANSACTIONS (UNT) MTL_TXN_REQUEST_LINES_V (MOV) - MOVE TRANSACTIONS

Receivables This section is populated once the line has been fulfilled and interface to Receivables along with selected invoice data. RA_INTERFACE_LINES (RAI) - RECEIVABLES INTERFACE LINES RA_INTERFACE_ERRORS (RAE) - RECEIVABLES INTERFACE ERRORS RA_CUSTOMER_TRX (RAH) - INVOICE HEADERS RA_CUSTOMER_TRX_LINES (RAL) - INVOICE LINES

Interpreting the Data

While HTMomse12 output contains information for other products involved in the order process, as previously noted, this

paper will only cover the areas directly related to the Order Management application. The main focus will be on the

OE_ORDER_HEADERS and OE_ORDER_LINES section.

For a description of each column and where it can viewed on the Sales Order form, see Appendix A.

Understanding OE_ORDER_HEADERS

When the order is created either from the Sales Order form or imported, this section is created.

Figure 1: OE_ORDER_HEADERS (ORD)

There are several conditions to look for:

If the FLOW_CODE = ENTERED, then BK (booked) must be N (no) and OP (open) must be Y (yes).

If the FLOW_CODE = BOOKED, then BK (booked) must be Y (yes) and OP (open) must be Y (yes).

When CN (cancelled) = Y (yes), then OP (open) should be N (no) and FLOW_CODE = CANCELLED.


Understanding OE_ORDER_LINES

This section is populated for each line as it is entered. There will also be additional lines not directly entered by the user.

For items such as PTO (see Figure 2), Line 1.1 is the line entered by the user. Lines 1.1.1, 1.1.2 and 1.1.3 are components

of the item.

Figure 2: OE_ORDER_LINES (LIN)

Example of a Pick-To-Order (PTO) model with non-shippable components. (Note the HTMomse12 output line has been split into multiple screen shots.)

There are many conditions to look for within the line:

If the FLOW_CODE = ENTERED, then BK (booked) must be N (no) and OP (open) must be Y (yes).

If the FLOW_CODE = BOOKED, then BK (booked) must be Y (yes) and OP (open) must be Y (yes).

When CN (cancelled) = Y (yes), then OP (open) should be N (no) and Order Qty (quantity) must be zero.

FLOW_CODE will be equal to CANCELLED.

FLOW_CODE of AWAITING_SHIPPING can only occur when SH (Shippable Item) is Y (yes) and SI (Shipping

Interface) is Y (yes).

If SI (Shipping Interface) is Y (yes), then SH (Shippable Item) must be Y (yes).


ORDER QTY (ordered quantity) cannot be less than RESERV QTY (reserved quantity), SHIPNG QTY (shipping

quantity), SHIPPD QTY (shipped quantity), FULFIL QTY (fulfilled quantity), CANCEL QTY (cancelled quantity) or

INOIV QTY (invoice quantity).

When FLOW_CODE = ENTERED, RESERV QTY (reserved quantity), SHIPNG QTY (shipping quantity),

SHIPPD QTY (shipped quantity), FULFIL QTY (fulfilled quantity) and INOIV QTY (invoice quantity) must be zero.

When FLOW_CODE = BOOKED, SHIPNG QTY (shipping quantity), SHIPPD QTY (shipped quantity), FULFIL

QTY (fulfilled quantity) and INOIV QTY (invoice quantity) must be zero.

When INVOIC INT_STATUS (invoiced interface status) = N (no), then INOIV QTY (invoice quantity) must be

zero.

Either SHIP SET_TYP (Ship Set) or ARRIV SET_TY (Arrive Set) may be populated but not both.

Some conditions require lines to be correctly associated with other lines:

Line numbers are one identifier of associated lines. Examples:

o Lines 1.1 and 1.2 indicates a split line when SPLIT LN_ID is populated.

o Lines 1.1.1 and 1.1.2 point to components of the model in line 1.1.

ATO = Y (yes) indicates this is an Assemble To Order model. In this case ORDERED ITEM for the top line

(such as 1.1, 2.1, etc.) will equal Model.

Models and their structure can be determined both by the LINE and by other columns. The top model entered

will have a value PRT LN_ID while the ATO LN_ID and LINK LN_ID are null.

In the case of an ATO, the ATO LN_ID is populated with the same ID as LINE_ID as well as all of its

components.

LINK LN_ID indicates the sequences of the components. Each ID will point to the previous LINE_ID in the

sequence.

When a line has been split, the original line will have no SPLIT LN_ID but SPLIT BY is populated. For the new

line SPLIT LN_ID will point to the original LINE_ID and SPLIT BY is populated.

SPLIT BY indicates whether a user manually did the split or the application (such as results of a partial shipment).

Line data is also associated with Shipping data. Lines with a value of SH (Shippable Item) equal to Y (yes) once the FLOW

CODE = AWAITING_SHIPPING and SI (Shipping Interface) = Y (yes), at least one corresponding record

WSH_DELIVERY_DETAILS will exist:

WSH_DELIVERY_DETAILS LINE will have the same values as OE_ORDER_LINES.LINE_ID.

There may be multiple WSH_DELIVERY_DETAILS for each OE_ORDER_LINES. The total quantities for all

the associated lines will equal the matching quantities in OE_ORDER_LINES once the delivery has been

interfaced as indicated by WSH_DELIVERY_DETAILS OMI (Order Management Interface) = Y (yes).

Once Shipping data has been interfaced, the lines will progress through to Fulfilled (FF) = Y (yes). Depending if the item is

Invoiceable, it will then be interfaced to Receivables:

INVOIC QTY (Invoiced quantity) will be greater than zero.


Final stage of Lines and Order.

Once each line has progressed to FLOW CODE = CLOSED, OP (open) will equal N (no).

Once all lines have closed or been cancelled, then the Order header is eligible to close. Header will close based on

the time frame specified in the Workflow.

OE_SETS (SET) is listed just before OE_ORDER_HEADERS. The Set information is related to the order lines (SHIP

SET_ID, SHIP SET_TY, LINE SET_ID, LINE SET_TY, ARRIV SET_ID, ARRIV SET_TY and OTHER SETS).

No line within a SET can progress beyond all the other lines in the set based on the Set type. Example, all lines in

a Ship Set must be shipped together. If one line has been cancelled, then the ship set will prevent the remaining

lines from shipping. For a fulfillment set, no lines will progress to invoice.

Look for Shippable and non-shippable items in same Ship Set.

Understanding Workflow

Workflow is associated with both Headers and Lines. It provides detailed information as to the different stages of the order or each line as they progress through it life cycle. Similar information is available from the Sales Order form by going to Tools > Workflow Status from either Order Information tab or the Line Item tab with the cursor on the desired line to be viewed.

Figure 3: Workflow Line Status for an order line.

While the above example is for Lines, reviewing the data is similar for both Header and Lines.

The LIN_ID is unique to Lines only. Multiple entries will match the OE_ORDER_LINES LINE_ID. Listing in sequences the process starting with PROCESS_NAME = ROOT.

The entries in PROCESS_NAME should match the events completed. The last entry indicates the stage the order or line is currently at.

When the last entry in PROCESS_NAME = Ship Line, Manual, the OE_ORDER_LINES FLOW_CODE must be equal to AWAITING_SHIPPING. These settings will remain until Order Management Interface has successfully run indicating Shipping has shipped the item.

Check ERROR_NAME for any errors.

Check RESULT for Force. A Force may indicate the Workflow process has been corrupted.

Validation Warning List

As part of both the OE_ORDER_HEADERS and OE_ORDER_LINES sections is a column named WARNING. This will contain numbers matching error / warning messages listed under Warning List.


Figure 4: Warning List for order lines

For a list of reported warnings / errors, see Appendix B.


Appendix A Column Descriptions

HTMomse12 columns are located on the Sales Order Form OE_ORDER_HEADERS (ORD) is displayed on the Order Information tab.

Column Name Description Navigation

HEADER_ID Header ID

ORD_NUM Order Number Main > Order Number

TYPE_ID Transaction ID

TYPE_NAME Transaction Name Main > Order Type

FLOW_PROCESS WorkFlow Process Tools > Workflow Status

FLOW_CODE Order Header Status Main > Status

BK Booked

OP Open

CN Cancel

SP Partial Shipment Allowed

CUST_ID Customer ID Main > Customer Number

CUST_NAME Customer Main > Customer

SHIP_ID Ship To Location ID

SHIP_TO Ship To Location Main > Ship To Location

BILL_ID Bill To ID

ORD_DATE Order Date Main > Date Ordered

WH_ID Warehouse ID

ORG Warehouse Others > Warehouse

CAT Order Category

PL_ID Price List ID

PL_NAME Price List Main > Price List

PO_NUMBER Purchase Order Number Main > PO Number

STA Ship Tolerance Above Other > Over-ship Tolerance**

STB Ship Tolerance Below Other > Under-ship Tolerance**

OPERATING_UNIT Organization Name Main > Operating Unit**

OE_ORDER_LINES (LIN) is displayed on the Line Items tab

Column Name Description Navigation

LINE Line Number Line Items > Main > Line

LINE_ID Line ID

DELIVERY DETAIL Delivery Detail ID

ITEM ID Item ID

ITEM Item Line Items > Main > Ordered Item

FLOW PROCESS WorkFlow Process Tools > Workflow Status

FLOW CODE Status Line Items > Main > Status

OP Open Flag

BK Booked Flag

SH Shippable Flag

CN Cancelled Flag

VD Visible Demand Flag Line Items > Main > Visible Demand Flag**

SI Shipping Interfaced Flag

FF Fulfilled Flag

ATO Assemble To Order Flag Line Items > Main > ATO

SMC Ship Model Complete Line Items > Shipping > Ship Model Complete Flag**

ORDER QTY Ordered Quantity Line Items > Main > Qty

UOM Unit of Measure Line Items > Main > UOM


SELL PRICE Selling Price Line Items > Main > Unit Selling Price

LIST PRICE List Price Line Items > Main > List Price**

CALC PRICE Calculated Price

RESERV QTY Reserved Quantity Line Items > Shipping > Qty Reserved

SHIPNG QTY Shipping Quantity Line Items > Main > List Price**

SHIPPD QTY Shipped Quantity Line Items > Main > Qty Shipped

FULFIL QTY Fulfilled Quantity

CANCEL QTY Cancelled Quantity Line Items > Main > Qty Cancelled

INVOIC QTY Invoiced Quantity Line Items > Main > Invoiced Quantity**

SCHD ST_CD Scheduled Status Code

WH_ID Warehouse Id

ORG Organization Line Items > Shipping > Warehouse

CREATE DATE Create Date Line Items > Main > Ordered Date**

REQUEST DATE Request Date Line Items > Main > Request Date

SCHED DATE Scheduled Date Line Items > Main > Schedule Ship Date

ACTUAL SHIP_DATE Actual Ship Date Line Items > Shipping > Actual Shipment Date**

LINE TYPE Line Type Line Items > Main > Line Type

LINE CATEG Line Category

ITEM TYPE Item Type Line Items > Main > Item Type**

ORDERED ITEM_ID Ordered Item ID

ORDERED ITEM Ordered Item Line Items > Main > Ordered Item

SOURCE TYPE Source Type Line Items > Shipping > Source Type

PRICE LIST_ID Price List ID

DEMAND CLASS Demand Class Line Items > Shipping > Demand Class**

CFG Option Flag

WH_ID Warehouse ID

PRT LN_ID Top Model Line ID

ATO LN_ID ATO Line Id

LINK LN_ID Link to Line ID

SPLIT BY Split By Line Items > Shipping > Split By

SPLIT LN_ID Split Line ID

CONFIG HD_ID Configuration Header ID

INVOIC INT_STAT Invoice Interface Status Code

STA Ship Tolerance Above Line Items > Shipping > Over-Ship Tolerance**

STB Ship Tolerance Below Line Items > Shipping > Under-Ship Tolerance**

SHIP SET_ID Ship Set ID

SHIP SET_TY Ship Set Type Line Items > Shipping > Ship Set

LINE SET_ID Line Set ID

LINE SET_TY Line Set Type

ARRIV SET_ID Arrival Set ID

ARRIV SET_TY Arrival Set Type Line Items > Shipping > Arrival Set

OTHER SETS Set Type

DISCRETE ORDER_QTY

Discrete Order Quantity

DISCR UOM Discrete Unit of Measure

DISCRETE SHPNG_QTY

Discrete Shipping Quantity

DISCRETE SHPNG_UOM

Discrete Shipping Unit of Measure

DISCRETE Discrete Shipped Quantity


SHIPPD_QTY

DISCRETE FULFLL_QTY

Discrete Fulfilled Quantity

DISCRETE CANCEL_QTY

Discrete Cancelled Quantity

LAST UPD_DATE Last Update Date

TRACK QTY_IND Tracking Quantity Indicator

PRIMARY UOM_COD Primary Unit of Measure Code

DUAL_UOM CONTROL

Dual Unit of Measure Control

SECONDARY DEFAULT_IND

Secondary Default Indicator

SECONDARY UOM_COD

Secondary Unit of Measure Code

Line Items > Main > Secondary UOM**

CHILD LOT_FLAG Child Lot Flag

PARENT_CHILD GEN_FLAG

Parent Child Generation Flag

LOT DIVIS_FLAG Lot Divisible Flag

GRADE CNTRL_FLAG

Grade Control Flag

ONT_PRICING QTY_SOURCE

Order Management Pricing Quantity Source

DUAL_UOM DEV_HGH

Dual Unit of Measure Deviation High

DUAL_UOM DEV_LOW

Dual Unit of Measure Deviation Low

LOT CONTROL Lot Control Code

LOCATION CTRL_CODE

Location Control Code

STATUS CONTROL Lot Status Enabled

SRC_DOC LINE_ID Source Document Line ID

** Columns may not be displayed. To display Go to Folder > Show Field and select.


Appendix B - Reported Warnings / Errors

Order Header: OE_ORDER_HEADERS (ORD) 10. Order_Header has associated lines with OPEN and CANCELLED flags set to Y. 15. Order_Header status is BOOKED but "Book" activity has not been completed. 20. Order_Header status is CLOSED but "Close" activity has not been completed. 21. Order_Header status is CLOSED but exist open lines associated to this header. 22. All associated lines has been closed but Order_Header is not ready to CLOSE. 50. No WorkFlow Process associated to this line. 51. Incorrect WorkFlow Process associated to this Order Header. 52. Incorrect WorkFlow Activity associated to this Order Header. 53. Incorrect WorkFlow Activity Result for this Order Header. 54. Incorrect WorkFlow Activity Status for this Order Header.

Order Lines: OE_ORDER_LINES (LIN) 1. Ordered Quantity is less than Shipped Quantity. 2. Ordered Quantity is less than Fulfilled Quantity. 3. Ordered Quantity is less than Invoiced Quantity. 4. Interface to WSH set to "N" but exist Delivery Details associated to this Order_line. 5. Associated Delivery Details has NOT been interface but Shipped, Fulfilled or Invoiced QTY are updated. 10. Order_Line shows as OPEN but CANCELLED flag is set to Y. 11. Order_Line status ENTERED but Shipped Qty is greater than zero. 12. Order_Line status ENTERED but Fulfilled Qty is greater than zero. 15. Order_Line status BOOKED but "Book" activity has not been completed. 16. Order_Line status BOOKED but Shipped Qty is greater than zero. 17. Order_Line status BOOKED but Fulfilled Qty is greater than zero. 20. Order_Line status AWAITING SHIPPING but Item is set to Non-Shippable. 21. Order_Line status AWAITING SHIPPING but Shipped Qty is greater than zero. 22. Order_Line status AWAITING SHIPPING but Fulfilled Qty is greater than zero. 23. No Delivery Details associated to this Order_line, Interface to WSH is set to "Y". 24. Associated Delivery Details have invalid RELEASED status. 25. Associated Delivery Details have invalid INTERFACE status (Not Shipped but Interfaced to OM or INV). 40. Line status is CLOSED but associated Delivery Details still not interface to OM. 41. Line status is CLOSED but associated Delivery Details still not interface to INVentory. 45. Line status is CANCELLED but associated Delivery Details has been interfaced to OM. 46. Line status is CANCELLED but associated Delivery Details has been interfaced to INVentory. 50. No WorkFlow Process associated to this line. 51. Incorrect WorkFlow Process associated to this line. 52. Incorrect WorkFlow Activity associated to this line. 53. Incorrect WorkFlow Activity Result for this line. 54. Incorrect WorkFlow Activity Status for this line. 55. Order Line status is BOOKED, WorkFlow Activities shows additional activities for this line. 60. Organization_id is Null for this line. 61. Transaction Type is Null for this line.


Understanding the HTMomse12 Otuput for

Order Management

February 2012

Author: Alice Thurmond

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

Copyright 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the

contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other

warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or

fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are

formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and

are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are

trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark licensed through X/Open

Company, Ltd. 0611

undertand in ght mom se 12

Documents