===========================================================================

NEW AND CHANGED FEATURES IN THIS PRODUCT

===========================================================================
Feature Name:
XML Purchase Order Outbound - sending purchase orders in cXML format

Brief Description:
Buyers can now send new Purchase Orders (Standard or Release) to suppliers using
the cXML format.

Support for Change PO is not yet available.

The cXML PO can be sent directly to the seller where it can be received through
their existing cXML port. Thus suppliers will not have to establish a separate
port for processing cXML PO’s sent from customers running Oracle Procurement.

However suppliers will have to update their parser in order to process the
Oracle cXML messages correctly as key tags in the payload envelope details will
be updated to reflect that the cXML message originated from Oracle and not via
the Ariba Supplier Network.

It is also worth noting that the cXML format only supports purchase order
headers and lines and thus Oracle PO’s have to be converted from the more
sophisticated header-line-shipment model.

The cXML message conforms to the cXML standard described in the cXML User’s
Guide v 1.2.007

===========================================================================
NEW AND CHANGED MODULES IN THIS PRODUCT
===========================================================================

Name Description New or Changed

1. CXML_OrderRequest.xgm New purchase order from New.
buyer to supplier; does
not support change PO.
Supports T&C and
Attachments too.

===========================================================================
NEW AND CHANGED SETUP STEPS IN THIS PRODUCT
===========================================================================
Feature Name:
XML Purchase Order Outbound - sending purchase orders in cXML format

1. Install OWF.G (patch #2728236)

2. Install 11.5.9+ XML PO patch (patch # 2819417)
3. Install CXML PO FAILING: ECX_ERRMSG=DTD NOT FOUND FOR MAP ID: 117 patch
(patch # 3202575) if you are on a multi-node system.
For cXML documents, the format is always MIME enabled and follows the cXML
protocol.

4. Profile Option setup

The following system Profile Options are used to define the Buyer’s domain &
identity that will be passed to all suppliers set up for cXML purchase orders.
When the supplier receives the document, they will use the domain and identity
to determine the exact identity of the buyer who has sent the purchase order.

Profile Option Name: PO: cXML From Domain

Internal Name: PO_CXML_FROM_DOMAIN
Usage: Indicates buyer's "domain" in the XML doc sent.
Since Oracle does not currently have any means to
administer the identities of buyers within a specific
‘Oracle Buyer’ cXML domain (and thus guarantee the
uniqueness of the domain-identity pair), no value is
seeded for the cXML From Domain. Buyers should set this
profile option to a value that will uniquely identify
their domain, such as “Oracle eBS - <company name>”

Profile Option Name: PO: cXML From Identity

Internal name: PO_CXML_FROM_IDENTITY
Usage: Indicates the Buyer's "identity" in the XML doc sent.
As per the Domain tag, no value is seeded. Buyers should
set this profile option to a value that will uniquely
identify them within their domain, such as “<company
name>”

5. Supplier Shared Secret setup

To authenticate the cXML purchase order, each supplier will provide a buyer with
a username (domain+identity) and password that need to be included in the cXML
purchase order message.

The XML Gateway trading partner set up form is used to set up these values for
each cXML supplier.

cXML To Domain: Username field

cXML To Identity: Source Location Code field
Shared Secret: Password field

6. XML Gateway Configuration

The following set up must be completed in XML Gateway in order to send cXML
purchase order documents to suppliers:
a) Transaction Type: PO
b) Transaction Subtype: PRO
c) Standard: OAG
d) External Transaction Type: Order
e) External Transaction Subtype: Request
f) Direction: OUT
g) Map: Order Request
7. Other
The following field values are preseeded:
User Agent: "Oracle E-Business Suite Oracle Purchasing 11.5.9"
- this indicates to the supplier that the received document
originated from a trading partner running Oracle and not via
the Ariba Supplier Network.
Deployment Mode: "production"

============================================================================
UPGRADE CONSIDERATIONS FOR THIS PRODUCT
============================================================================
No upgrade issues.