OBN Process Guide

Oracle® Business Network
Process Guide
Release 3.0
Part No. F29166-03
March 2021
Oracle Business Network Process Guide , Release 3.0
Part No. F29166-03
Copyright © 2021, Oracle and/or its affiliates.
Primary Author: Swathi Mathur, Mark Peachey, Preeti Venugopal
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No
other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
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 of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.
com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Send Us Your Comments
Preface
1 Introduction
Overview................................................................................................................................... 1-1
Process Overview...................................................................................................................... 1-1
Environment Information......................................................................................................... 1-2
2 Registering on Oracle Business Network

About Registering Your Company............................................................................................2-1
3 Using Oracle Business Network (OBN)

Using OBN................................................................................................................................. 3-1
4 Updating the Profile

Profile........................................................................................................................................ 4-1
Updating the Company Profile................................................................................................. 4-1
Creating Test Accounts............................................................................................................. 4-2
5 Setting up Messaging
Introduction to Messaging........................................................................................................ 5-1
Identifiers.................................................................................................................................. 5-3
Modifying the Identifiers......................................................................................................... 5-4
Communication Parameters...................................................................................................... 5-5
iii
Managing the Delivery Methods.............................................................................................. 5-5
Transaction Management.......................................................................................................... 5-7
Managing Transaction Types.................................................................................................... 5-7
Sending Documents.................................................................................................................. 5-9
Sending Documents.................................................................................................................. 5-9
Managing Attachments........................................................................................................... 5-10
Uploading Attachments.......................................................................................................... 5-10
6 Trading Partner Management

About Trading Partners............................................................................................................. 6-1
Adding Trading Partners.......................................................................................................... 6-1
Approving Trading Partners..................................................................................................... 6-3
Updating Trading Partners....................................................................................................... 6-3
Deleting Trading Partners......................................................................................................... 6-4
Routing Rules............................................................................................................................ 6-4
Viewing Routing Rules............................................................................................................. 6-5
7 Setting Up Notifications
Setting Up Notification Preferences......................................................................................... 7-1
8 Managing Users
About User Roles....................................................................................................................... 8-1
Adding Users............................................................................................................................. 8-1
Activating, Deactivating, or Removing Users...........................................................................8-1
User Roles.................................................................................................................................. 8-2
9 Testing Outbound and Inbound Messages

About Self-Testing ................................................................................................................... 9-1
Outbound Tests......................................................................................................................... 9-1
Testing Outbound Messages.................................................................................................... 9-2
Download Sample Payloads..................................................................................................... 9-2
Viewing Outbound Messages................................................................................................... 9-2
Inbound Tests............................................................................................................................ 9-3
10 Transaction Monitor
About Transaction Monitor.................................................................................................... 10-1
Viewing Messages................................................................................................................... 10-1
Downloading Messages.......................................................................................................... 10-1
Viewing Transaction Details.................................................................................................. 10-2
iv
11 Setting up Outbound XML Messaging
About Outbound XML Messaging ........................................................................................ 11-1
Process Overview.................................................................................................................... 11-2
Oracle XML Gateway.............................................................................................................. 11-2
XML Document Routing......................................................................................................... 11-3
Oracle Transport Agent--Buyer's System............................................................................... 11-3
Implementation Steps............................................................................................................. 11-4
Setting up OBN....................................................................................................................... 11-4
Setting Up Oracle XML Gateway............................................................................................ 11-5
Setting Up Hub........................................................................................................................ 11-5
Setting Up Trading Partner..................................................................................................... 11-7
Setting Up Purchase Orders or Releases.................................................................................11-8
Setting Up Change Orders...................................................................................................... 11-9
Test and Production Transactions Process........................................................................... 11-10
12 Inbound XML
About Inbound XML Messaging............................................................................................ 12-1
Process Overview.................................................................................................................... 12-2
Supplier Activities................................................................................................................... 12-2
Oracle Business Network Processing..................................................................................... 12-2
Oracle Transport Agent and Workflow APIs (Buyer Company)........................................... 12-3
Oracle XML Gateway (Buyer Company)................................................................................ 12-3
Implementation Steps............................................................................................................. 12-3
Setting Up Oracle XML Gateway............................................................................................ 12-4
Setting Up Trading Partner..................................................................................................... 12-4
Setting Up Advance Ship Notices........................................................................................... 12-5
Setting Up Purchase Order Acknowledgement..................................................................... 12-6
Setting Up Invoices................................................................................................................. 12-6
Setting Up Change Sales Orders............................................................................................. 12-7
13 Punchout
Punchout Using Oracle Business Network............................................................................ 13-1
Punchout Redirect................................................................................................................... 13-2
Setup for Oracle Customers using Buyer Access................................................................... 13-3
Punchout Setup for Trading Partners to an Oracle Customer ...............................................13-7
Data Mapping in Oracle Business Network........................................................................... 13-9
v
14 Pages and Navigation
Pages and Navigation.............................................................................................................. 14-1
vi
Send Us Your Comments
Oracle Business Network Process Guide , Release 3.0

Part No. F29166-03
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 3.0 of the Oracle Business Network Process Guide .
This guide is intended for Information Technology personnel and functional
administrators who are responsible for the administration and maintenance of Oracle
R12 Applications, which includes the Oracle XML Gateway.
About this Guide

This guide provides the implementation steps for connecting your Oracle R12
Applications to the Oracle Business Network for exchanging electronic messages with
your suppliers.
Prerequisites
This guide assumes you have a working knowledge of:
• The Oracle R12 Applications graphical user interface. To learn more about the
Oracle Applications graphical user interface, see the Oracle Applications User's Guide.
• Oracle Business Network. To learn more about the Oracle Business Network, read
the Oracle Business Network User Guide located on the Oracle Business Network Web
site at http://businessnetwork.oracle.com.
See Related Information Sources on page x for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ix
ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit http://www.oracle.
com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=trs if you are hearing impaired.
Structure
1 Introduction
2 Registering on Oracle Business Network
3 Using Oracle Business Network (OBN)
4 Updating the Profile
5 Setting up Messaging
6 Trading Partner Management
7 Setting Up Notifications
8 Managing Users
9 Testing Outbound and Inbound Messages
10 Transaction Monitor
11 Setting up Outbound XML Messaging
12 Inbound XML
13 Punchout
14 Pages and Navigation
Related Information Sources

This guide references a number of documents that you may want to have available:
• Oracle Applications Release R12 Implementation Manual
• Oracle Applications System Administrator's Guide
• Oracle Manufacturing APIs and Open Interfaces Manual
• Oracle Payables User's Guide
• Oracle Purchasing User's Guide
• Oracle Business Network XML Solutions Guide
• Oracle Transport Agent - Installation document
• Oracle XML Gateway User's Guide
• Oracle Purchasing eTechnical Reference Manual, Release R12, available on Oracle My

Support, accessible at http://www.oracle.com/support/ .
x
• For additional reference, go to the Open Applications Group (OAGI) Web site: http:
//www.openapplications.org .
Software Requirements
Whether you are implementing purchase orders, change orders, acknowledgements,
advance ship notices (ASNs), or invoices, the following prerequisites apply:
• Oracle XML Gateway is installed and operational on an Oracle Applications R12
instance.
• Oracle Transport Agent (OTA) is installed and operational on an Oracle

Applications R12 instance.
Do Not Use Database Tools to Modify Oracle E-Business Suite Data

Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data
Browser, database triggers, or any other tool to modify Oracle E-Business Suite data
unless otherwise instructed.
Oracle provides powerful tools you can use to create, store, change, retrieve, and
maintain information in an Oracle database. But if you use Oracle tools such as
SQL*Plus to modify Oracle E-Business Suite data, you risk destroying the integrity of
your data and you lose the ability to audit changes to your data.
Because Oracle E-Business Suite tables are interrelated, any change you make using an
Oracle E-Business Suite form can update many tables at once. But when you modify
Oracle E-Business Suite data using anything other than Oracle E-Business Suite, you
may change a row in one table without making corresponding changes in related tables.
If your tables get out of synchronization with each other, you risk retrieving erroneous
information and you risk unpredictable results throughout Oracle E-Business Suite.
When you use Oracle E-Business Suite to modify your data, Oracle E-Business Suite
automatically checks that your changes are valid. Oracle E-Business Suite also keeps
track of who changes information. If you enter information into database tables using
database tools, you may store invalid information. You also lose the ability to track who
has changed your information because SQL*Plus and other database tools do not keep a
record of changes.
xi
1
Introduction
Overview
The Oracle Business Network (OBN) is a secure cloud-based business-to-business (B2B)
collaboration platform that automates electronic transactions between Oracle
application customer's and their trading partners. Participants on the OBN are only
required to establish their own secure connection to the hub to enable electronic
communication on the platform.
OBN facilitates electronic collaboration between trading partners, and can be used to
exchange business documents, manage the catalog punchout process and enable
transmission of catalog content from suppliers to their customers.
OBN is hosted on the latest Oracle Cloud Infrastructure platform in one of Oracle's
state-of-the-art datacenter's that provides high 365x7x24 availability.
This document serves as a process guide for Oracle customers and their trading
partners to begin communicating with Oracle Business Network.
Process Overview
Oracle customers are required to register on OBN. For Oracle Cloud customers, this
process is streamlined in release 20C so that they can register, get approved and have a
default connection setup processed automatically. EBS and Peoplesoft customers are
still required to initiate a web-based self-registration process on OBN. This request will
be reviewed and approved by the OBN Administrator (OBN Admin). When approved,
they can proceed to set up their communication protocols, identify the transaction types
that they are interested in sending or receiving, and indicate the trading partners with
whom they intend to exchange messages.
Non-Oracle trading partners are typically required to register on OBN by indicating the
name of the Oracle customer on OBN with whom they will be exchanging business
documents. This request will be reviewed and approved by a user with Trading Partner
Administrator (TP Admin) privileges on OBN for the Oracle customer trading partner
Introduction 1-1
account.
Before two trading partners can send electronic messages through the Oracle Business
Network, both parties must agree to the relationship. This process is called trading
partner approval.
Environment Information
You can access Oracle Business Network using http://businessnetwork.oracle.com. OBN
consists of two messaging mode; the OBN Test Hub, that enables customers to perform
end-to-end testing; and the OBN Production Hub that routes live transactions between
trading partners.
The configuration hierarchy settings are:
• Each Oracle customer or their trading partner will have a single OBN account.
• Each account can have multiple users, administered by one or more Trading
Partner (TP) Admin users.
• Each account can define a single set of delivery methods that OBN can use to
transmit documents to the trading partner ERP system.
1-2 Oracle Business Network Process Guide

• Each Delivery Method has separate Test and Production mode settings (to enable
documents to be transmitted to different ERP instances as required).
• Each account can set up a single set of business transactions they can receive from
OBN or send to OBN.
• Each business transaction can be transmitted using different delivery modes

available in the Test and Production hubs.
• Your OBN account provides visibility to transactions processed in each hub

through the Transaction Monitor allowing you to query test and production
messages.
• For optimal performance, Oracle recommends using Apple Safari 11+, Google
Chrome 60+, Microsoft Edge 40+, Mozilla Firefox 52+.
See: Punchout for Punchout configuration settings.
Introduction 1-3
2
Registering on Oracle Business Network
About Registering Your Company

OBN provides a self-registration process for Oracle customers and their trading
partners to register their organization; after registering, Oracle customers and their
trading partners can perform send/receive transactions.
This chapter describes the OBN registration process.
Note: Throughout this guide, buyer or buying organization refers to an

Oracle customer who has deployed any one of these applications -
Oracle Cloud, PeopleSoft or an E-Business Suite application such as
Procurement or Financials. Supplier refers to the buying organization's
trading partner.
Registering as an Oracle Customer

To register your company on OBN, you must be a licensed Oracle Procurement or an
Oracle Financials customer who has deployed any of the following applications: Oracle
Cloud, Oracle E-Business Suite, or Oracle PeopleSoft. When you register as a buying
organization, you can exchange business documents with your trading partners.
EBS and Peoplesoft customers are required to initiate a web-based self-registration
process on OBN. For Oracle Cloud customers, this process is streamlined, so that they
can register, get approved, and have a default connection setup processed
automatically. For more information on how to create an OBN account from Oracle
Cloud, see: How You Configure Predefined Service Providers [https://docs.oracle.
com/en/cloud/saas/supply-chain-management/20c/facmm/collaboration-messaging-
service-providers.html#FACMM3560261]
For EBS and Peoplesoft customers, before you register your company, you must log a
service request (SR) with Oracle Support and obtain the SR number. You require this
number while registering your company. In the Service Request, enter the Problem
Registering on Oracle Business Network 2-1

Summary as OBN Registration Approval Request, (YOUR_COMPANY_NAME).
To register your company as a buying organization, navigate to the Oracle Business
Network [https://businessnetwork.oracle.com] and click the Register as an Oracle
customer link.
Searching for Your Company
On the Registration page, search for your company in the following ways to register it
on OBN:
• Company Search - You can search for your company by specifying the country and
company name. The company name is mandatory. From the type ahead option,
select the company that meets your criteria. Click Continue. The company name
and it's corporate address is displayed. You can enter the contact information,
address, and messaging details.
• Advanced Search - If you do not see your company in the type ahead list, then you
can use the Advanced Search link to find your company. On the Company Search
page, enter the name or the URL to find your company. These fields are mandatory.
A list of all the companies and their URLs matching the search criteria is displayed.
Click Select to register the company on OBN.
• Manual Registration - If you still do not find your company using the Company
Search or Advanced Search options. then you can manually register the company.
When you have selected the company or manually registered, click Continue.
Entering the Registration Information

If your company appears in the type ahead list, then the corporate address is displayed
by default. You cannot edit or update the corporate address. You can however enter
additional addresses for your company.
Enter the following information:
To enter the company contact information:
1. Title: Enter a title.
2. First Name, Middle Name, Last Name: Enter the name of the person is responsible
for managing the account. Additionally, the Oracle Business Network sends any e-
mail communications this contact.
3. E-mail Address: Enter the email address.
4. User Name: Enter a user name for logging in to the Oracle Business Network
account. Oracle recommends using your email address as the user name. The
application verifies the selected user name to ensure that it is unique.
5. Password, Confirm Password: Enter a password, at least 8 characters in length to

authenticate you when logging in to OBN.
Electronic XML documents sent to the OBN must include your user name and
password for authenticating the sender as a valid trading partner registered on
OBN. Trading partners using Oracle applications use the chosen user name and
password in the XML Gateway configuration.
To enter the addresses:

1. You can add multiple addresses in addition to the corporate address.
2. Click Add.
3. Select the Type as Primary.
4. Enter the postal address of the company.
To enter messaging details:

1. You can enter the following information to identify your company on OBN.
2. Identifier Type: OBN allows companies to enter the credentials of their choice for
uniquely identifying themselves on OBN.
Document delivery protocols (containing origin and destination information) uses
the OBN identifier you specify. Most organizations prefer to use their D-U-N-S
number; however, you can specify any relevant Identifier Type.
You can select any of the following identifier types to identify your company:
• Miscellaneous
• D-U-N-S Number
• Telephone Number
• US Federal Tax Identifier
Note: For the identifier type that you select, you must enter a
unique value to identify your company.
• Global Location Number
• Network ID
• Generic
3. Identifier Value: Enter the identifier value that corresponds to the Identifier Type
that you have selected.

4. Enter the Customer Service Identifier and Service Request Number that you have
logged with Oracle Support.
5. Customer Support Identifier (CSI): When you indicate that you are an Oracle
Applications Customer, the application displays the CSI field. You must enter the
CSI number provided by Oracle Support. This is mandatory.
6. Service Request Number: When you indicate that you are an Oracle Applications
customer, the application displays this field. Enter the number of the service request
that you logged with Oracle Support stating problem summary as Oracle Business
Network Registration Approval Request, <YOUR_COMPANY_NAME> in the
service request.
Registration Approval:
After you have completed the registration page, click Continue. If successful, the Oracle
Business Network Terms of Use message appears. Read the terms, select the Accept
check box if you agree to all the terms, and then click Submit.
A confirmation page indicates that your registration has been submitted for review.
A notification will be sent to you indicating that the registration is pending approval.
Approving Oracle Customer registrations
If you are an Oracle Application customer, your registration is reviewed and approved
by the OBN administrator. When the registration has been approved, you receive a
notification that your account has been activated, and you can login to set up your
account.
Once the OBN account is registered, a unique identification number called OBN ID is
generated that can be used to uniquely identify a trading partner on OBN. The format
of OBN ID is OBN-XXX-XXXX. The OBN ID is displayed on the top right hand corner of
the OBN home page, after you login with a valid user name.
Registering as a Trading Partner of an Oracle Customer

To carry out business transactions with an Oracle customer, you must be a registered
trading partner of the Oracle customer on the OBN.
To register as a trading partner, click the Register as a Trading Partner link, provide
your company and contact information.
Your buying organization will provide you with the exact trading partner name they
use on Oracle Business Network. You require this name to complete the registration.
The registration request is sent to the OBN administrator of the buying organization for
review and approval.
Note: It is essential to enter the exact Trading Partner name for the
registration request to be routed to the OBN Administrator

appropriately.
Search for Your Company

You can search for your company in the following ways to register it on OBN:
• Company Search - You can search for your company by specifying the country and
company name. From the type ahead option, select the company that meets your
criteria. The company name and it's corporate address is displayed. You can enter
the contact information, address, and messaging details.
• Advanced Search - If you do not see your company in the type ahead list, then you
can use the Advanced Search option to find your company.
On the Company Search page, enter the name or the URL to find your company.
This is mandatory. A list of all the companies and their URLs matching the search
criteria is displayed. Select the company you want to register on OBN.
• Manual Registration - If you still do not find your company using the Company
Search or Advanced Search options. then you can manually register the company.
• Enter the company contact information, address, and messaging details.
• Your Trading Partner's Name: If you are not an Oracle customer and you are
registering to exchange XML documents electronically with an existing Oracle
applications customer, then you must enter the trading partner name and an alias.
The trading partner name is the name of the Oracle Applications customer who has
registered on OBN.
• Your Trading Partner's Alias: You enter a trading partner (TP) Alias value in this
field. The alias can be a name or a numeric identifier that you define, which is
included in the message envelope for all transactions that you send to OBN. OBN
searches for the TP Alias on each inbound message and uses it to determine the
ultimate receiver of the message.
The TP Alias also enables a cross-reference between the trading partner in your
internal systems. The TP Alias eliminates the need for you to know how the trading
partner has identified themselves on the OBN. This reduces the maintenance of
having to store the exact ID that a trading partner would otherwise require you to
use when sending them a document. The TP Alias that you assign each trading
partner is verified to ensure uniqueness so that the OBN can generate a valid
document route.
When you have selected the company to register, click Continue.

Approving Trading Partner registrations
If you are not an Oracle application customer but a trading partner, your registration is
reviewed and approved by the Oracle customer, for whom you are a supplier.

When the registration has been approved, you receive a notification that your account is
activated, and you can login to set up your account.
Note: Oracle recommends that your company has more than one
Oracle Business Network administrator for easy maintenance activities
and for receiving any alert notifications.
Contacting My Oracle Support

If you are an Oracle customer facing issues with OBN, contact Oracle Support to create
a service request stating your problem. Click the Learn More link on the OBN home
page.
If you are a trading partner, and face issues with OBN, use the Learn More link on the
OBN home page. Alternatively, contact the Oracle customer with whom you are
working, and ask them to log a Service Request with Oracle Support to resolve the
issue.
Forgot User Name/Password

If you have forgotten your user name or password to access OBN, click the Need Help?
link on the OBN home page. You can select the appropriate option to reset either the
user name or the password.
• Use the Click here if you have forgotten your password option to specify the user
name and email ID. You will receive an automated mail with a code.
• Use the Click here if you have forgotten your user name option to specify the
email ID. You will receive an automated mail at the registered email id with your
credentials.
• Use the Click here to reactivate your account option to reset your account. Enter
your user name. An email will be sent to the address on record.

3
Using Oracle Business Network (OBN)
Using OBN
The main page appears when you log in to the Oracle Business Network using the user
name and password that you specified during registration process.
The main page displays the following tabs that you can use to navigate the application.
The tabs are:
• Home
• Profile
• Messaging
• Partners
• Monitor
• Users
• Self-Testing
• Punchout
The Home tab has the following tiles with icons:

• Partners – to manage trading partners (the tile has two icons: Network and
Companies)
• Notification Preferences – to set up alerts and notifications for error messages (the
tile has two icons: Announcements, and Alerts)
• Messaging Setup – to set up the delivery methods
Using Oracle Business Network (OBN) 3-1

• Monitor – to track the sent and received documents and transactions
• Company Profile – to view and update the company profile information
• User Management – to create new users and maintain roles for existing users
Every company registered on OBN is assigned a unique identification number called

OBN ID. The OBN ID is displayed on the top right corner of the page.
Use the Notification Preferences option to register your company administrator for
receiving any business document notifications. This option is available in the list of
values at the top right corner of the page.
The following section provides a brief description of these options:
Profile
The Profile tab has the following sub-tab:
Company Profile: Use this option to view and change the company information
provided during the registration process. You can also create test accounts for your
company.
See Profile, page 4-1for more information.
Messaging
The Messaging tab includes the following sub-tabs:
• Identifiers: You can use this option to make changes to identifier information that
you provided during registration of your company.
• Communication Parameters: You can use this option to add the communication
methods that you intend to use for exchanging documents.
• Transaction Management: You can use this option to select the document types
and formats that your company sends and receives and assign these to a particular
delivery method.
• Send Document: You can use this option for companies to send XML messages
directly from the OBN to your trading partners.
See Setting Up Messaging , page 5-1 for more information.
Partners
You can use the Partners tab to manage your trading partner relationships. The Partners
tab includes the following sub-tabs:
• Pending Approval: Use this option to view if there are any requests for trading

partners that must be approved.
• Your Trading Partners: Use this option to search, and approve trading partner
relationships.
• Add Trading Partner: Use this option to search for, and add trading partners.
See Trading Partner Management, page 6-1 for more information.
Monitor
You can use the Monitor tab to track all documents that have been sent to OBN where
your company is either the sender or the receiver. The subtabs are:
• Sent Messages track all documents that have been sent by your company using
OBN
• Received Messages track all documents that have been sent to your company by
your trading partner using OBN
See Transaction Monitor, page 10-1 for more information.
Users
Use this tab to enable administrators to create new users and assign roles for existing
users.
The User Profile page lets users update their profile information. With the exception of
the user name, users can view and update their first name, middle name, last name, e-
mail address, title, and password.
Note: Documents that are sent to the Oracle Business Network must
include the Oracle Business Network user name and password of one
of your active users to authenticate your documents. Be careful that the
user whose credentials are being used does not inadvertently change
their Oracle Business Network password without changing it in the
destination system so that it appears on payloads being sent to the
Oracle Business Network.
See Managing User Roles, page 8-1 for more information.
Self-Testing
You can use this option to enable users to test their connectivity to OBN by sending or
receiving sample documents using their test systems.
• Outbound Tests option enables users to test their connectivity to OBN by sending
Using Oracle Business Network (OBN) 3-3

sample documents using their test systems.
• Inbound Tests option enables users to test their connectivity to OBN by receiving
sample documents using their test systems.
Connectivity: this page can be used to test whether Oracle Business Network is able to
connect to your ERP to send messages from OBN to ERP.
See Testing Outbound and Inbound Messages, page 9-1 for more information
Notification Preferences
You can use this option to register for notifications whether sent or received. Users can
choose to subscribe or unsubscribe to a particular transaction type.
Users can also view the list of subscribers for a particular transaction type and
document based on their user roles.
Notification Preferences is available as an option in the list of values at the top right
corner of the page.
See Setting Up Notification Preferences, page 7-1 for more information.
Punchout
Punchout is the process by which a buying organization's employees can browse the
contents of a supplier's online catalog of goods/services, select them for purchase and
have them added to a draft requisition. Once submitted and approved, the requisition
will be used to generate a purchase order that is then sent to the supplier to trigger
delivery of the goods/services.
OBN allows trading partners that support Punchout catalogs to store their punchout
definition on OBN. This definition can then be used by Oracle customers who wish to
make it available as a shopping option for their employees. The Oracle customer no
longer needs to maintain the Punchout definition locally in their ERP, and any changes
to the Punchout made by the supplier are automatically used by all Oracle customers
utilizing the OBN definition.
You can use the Punchout tab to set up the details needed for the punchout process.
See Punchout, page 13-7 for more information.

4
Updating the Profile
Profile
The Profile page displays the information that you provided while registering your
company. This includes the address and the contact information of the company. You
can also view the time interval specified for receiving the error notifications.
Updating the Company Profile

Use the Profile tab or the Company Profile tile (with icon) on the OBN Home page to
view or update the company profile information that you provided during the
registration process.
The Company Profile page displays the information that you provided while
registering your company. This includes the OBN ID, URL, contact name, and the
address of the company. You can also view the time interval specified for receiving the
error notifications.
A unique OBN ID is generated when you register your company with OBN. This ID is
used for identifying your company when you transact business with your trading
partners. You cannot update the OBN ID.
To update the company profile information:

1. Click the Profile tab or the Company Profile tile.
2. Click the Edit Profile icon.
3. You can change the URL if required.
4. The corporate address is displayed by default. You cannot updated this address.
Updating the Profile 4-1

Important: If you have manually registered your company, then
you can update the corporate address.
5. In addition to the corporate address, you can enter additional addresses, if required.
• Click Add.
• Select the address type as Primary.
• Enter the address details.
• Click on the appropriate icons in the Action column to edit or delete the
address.
6. The Summary Notification Interval field enables you to choose the interval at
which you want to receive email notifications for errors encountered during
transaction messaging. This notification preference enables you to receive a single
summarized notification or individual notifications of all messaging errors. The
default is Immediate (No Summarization) option. You get the error notification
immediately after the error has occurred.
For more information, see:Setting up Notification Preferences
7. Click Save.
Creating Test Accounts

When you register a company on OBN, you can also create a test account for demo and
testing purposes. By doing so, you eliminate creating multiple accounts in the
production environment.
A user with the administrator role only can create a test account.
Note: Each regular account can have certain relationships or

connections with other trading partners. These connections will also be
available for a test account. However when you create a test account,
the connections from a test account will not be propagated
automatically to the regular account and must be established manually.
When you create a test account, the Profile page displays the list of test accounts with
their OBN ID and its active or inactive status.
Important: All the Production Hubs are disabled for a test account.

To create a test account:
1. Navigate to the Profile tab.
2. Click the Test Accounts tile on the Profile tab.
3. Click Create.
4. Enter the following mandatory test account information:

• Account Name
• Identifier Type
• Identifier Value
• First and Last name
• Email Address
• User Name
• Password
5. Click Submit.
6. Depending on your requirement, you can activate or inactivate a test account. Select
Active or Inactive from the Account Status drop down list.
7. Click Save.
Updating the Profile 4-3

5
Setting up Messaging
Introduction to Messaging
OBN contains a directory of all registered trading partners, and requires that each
trading partner select their unique identifier. This identifier is used by the sending and
receiving parties for any transaction (such as business documents, punchout). Trading
partners can use multiple identifiers for their account, one of which must always be
designated as the primary identifier.
Message Delivery
For each trading partner, OBN requires the details of the destination server; the trading
partner uses the destination server to RECEIVE business transactions from OBN (or
other services). This destination server needs to be configured for trading partners
accounts. A destination server address can be set up for each delivery method
configured by a trading partner. This is used for transmission of different transaction
types. Each delivery method allows for separate URL addresses to be used for the Test
and Production modes supported on OBN.
OBN itself has 2 inbound queues used to process transactions SENT to it from any of
the trading partners with registered accounts on the platform. One of the inbound
queues is for Production mode transactions, the other for those being transmitted in
Test mode. Details of these URLs can be found in the Resources page on the OBN
website.
The OBN inbound queue URLs are a key part of the setup details. Trading partners
configure their local ERP/business application system (to enable electronic business
document delivery to OBN) using the OBN inbound queue URL.
Setting up Messaging 5-1

Message Addressing and Routing
Document Transmission
For any business transaction passed to OBN for delivery, the transmitter or sending
trading partner is required to identify both themselves and the receiving trading
partner in the message payload using these unique OBN identifiers. This is to ensure
that every message can be successfully routed.
Without the use of the unique identifiers on OBN, every trading partner connected to
OBN would be required to establish its own unique map that links the identity they
maintain locally for each trading partner to the identity the trading partner established
for themselves on OBN (usually these will be inconsistent).

Authenticating Messages
Message Authentication
For any business transaction sent to OBN for onward delivery, the sending trading
partner is required to include a secret in the message payload. This secret is ALWAYS
the credentials for one of their user accounts used to log in to OBN. This ensures that
OBN is able to trust that the transaction has been transmitted from the sending trading
partner identified with the From unique identifier.
For any business transaction sent from OBN to a trading partner, OBN will include the
secret in the message payload that is defined for the Delivery Method used for the
Transaction Type of business document being sent. If the transaction being sent is a
punchout request, the secret will be the password defined by the receiving trading
partner in their Punchout Setup. This ensures that the receiving trading partner can
trust that the document/transaction they are receiving has come from OBN.
Messaging Setup
You can use the Messaging Setup page to view and update the account configuration
that is necessary for communicating electronic transactions between your company and
the trading partners. You can enter the information for identifiers, communication
parameters, delivery methods, and transactions. You can use the Send Message function
to manually send messages to the trading partners.
Identifiers
An identifier indicates how a company uniquely identify themselves on the Oracle
Business Network. A number of different identifier types are supported on OBN: D-U-
N-S number, Tax ID, Telephone number, or a Miscellaneous Identifier, and so on. The
Identifiers section enables you to update the primary identifier, or add optional

secondary identifiers for your company. All identifiers are required to be unique on
OBN.
The identifier is used to identify the sending and receiving trading partner. Trading
partners use the defined identifiers in the message header or envelope depending on
the message format.
Tip: Oracle recommends you to use D-U-N-S number for uniqueness.
For identifier usage requirements for specific document types, see: Oracle Business
Network XML Solutions Guide.
Modifying the Identifiers

You can add new, update, or remove the identifiers. You can change the order of the
columns or sort them to meet your requirements.
To add an identifier:
1. Click Add to open the Add New Identifier window.
2. Select the Identifier Type from the list of values.
3. Enter a unique value for the identifier type selected.
4. Click Submit.
To change your primary identifier:

1. Click the Edit icon for the identifier you want to make as your primary identifier.
2. Select Mark as Primary? check box.
Tip: When you change your primary identifier to a new one, the
one previously selected as the primary identifier gets unchecked.
To set this back as primary, you must re-select earlier one and
select check box again.
3. Click Submit.
To delete a identifier:
1. Click the Delete icon against the identifier you wish to delete.
2. A primary identifier cannot be deleted.

Communication Parameters
The Communication Parameters section lets you set up the communication methods
that OBN will use to send/transmit business documents to a trading partner
ERP/business application system.
Oracle Business Network supports the following delivery methods:
• HTTPS URL Connection: You can send business documents to your ERP/business
application system over the internet with OBN using a specified HTTPS URL. It is
required that you use HTTPS for all HTTP-based messaging. For additional
security, you have the option of using the Basic Authentication.
• Oracle XML Transport Agent: This is the standard delivery protocol that Oracle
customers use to communicate with OBN. Each Oracle ERP has a specific URL
format that is set up to enable OBN to send business documents to your Oracle
system.
• Web:You can upload outbound messages and send them to any of your trading
partners using this option. You can retain inbound messages on the OBN and
download the messages at anytime.
• E-mail:You can also use e-mail to send and receive messages on the Oracle Business
Network.
Depending on the selected delivery methods, you are required to enter the URL/email
details for your local system so that OBN can transmit documents to it using the
specified method. For some of the Delivery Methods, additional parameters may be
required.
The Oracle Business Network supports two modes of operation:
• Production mode for routing production transactions.
• Test mode for routing test transactions.
For each Delivery Method, you can provide two sets of parameters that separate routing
of test and production messages. This lets you test the communication and connectivity
before applying them to real transactions.
Managing the Delivery Methods

You can add, edit, or delete the delivery methods in the Communication Parameters
section. You can also sort and reorder the columns using the View option.

To add a delivery method:
1. In the Communication Parameters section, click Add to add a new delivery
method.
2. Select a delivery method from the list of values. Enter the test and production mode
details as applicable.
The details you enter are the URLs of the test and production systems of your
ERP/business application system to which OBN will be connected.
Note: When you have selected type of Delivery Method, it no

longer appears in the list for you to select.
Note: If you are adding a delivery method for a test account, then
the delivery method for the production hub is disabled.
3. Enter the authentication details for each mode of operation for the delivery method.
The details specified must match to the credentials you will be checking for in
your ERP/business application system to authenticate any transactions sent from
OBN.
4. Click Submit.
To edit a delivery method:

1. Select the delivery method.
2. Click the Updateicon.
3. You can change the test and production values for the URL, user name, password,
and enter if the user authentication check is required.
If the Basic Authentication feature has been used, then you can edit the values for
Use Basic Authentication and Basic Authentication Realm, user name, and
password.
4. Click Submit.
To delete a delivery method:

1. Select the delivery method.
2. Click the Delete icon.

Transaction Management
The Transaction Management section lets you choose the document types that your
company intends to support, specify how to deliver each document type, and whether
you will send or receive the document.
For details on the specific transactions that the Oracle Business Network supports, see:
Oracle Business Network XML Solutions Guide.
• Transaction Type: The transaction type specifies the type of the business
transaction being exchanged between trading partners.
• Document Format:The document format identifies whether it is an Open

Applications Group (OAG) or Commerce XML (cXML) document.
• Document Type:The type identifies the exact name of the business transaction for a
certain standard specification.
• Format Version: The version indicates the electronic format specification.
• Action: The action indicates whether the document is being transmitted by OBN to
your ERP/business application system (SEND), or if OBN will be receiving this type
of transaction from your system (RECEIVE).
• Delivery Method: Indicates the method of delivering the documents on both Test
and Production hubs.
Note: Buying organizations are restricted to sending and receiving

OAG documents only, since the supported Procurement applications
that integrate with the Oracle Business Network are certified to connect
using the OAG XML format only. Suppliers have the choice to send or
/receive either OAG or cXML documents. This is enforced by restricting
the Action when cXML document is selected to supplier's direction
only; for example, if a cXML Purchase Order is selected, the only
supported value in the Action list of values is the supplier's direction,
which is Receive.
Managing Transaction Types

You can add, modify or delete the document types that your company intends to
support, specify how to deliver each document type, and whether you will send or
receive the document.

To add a transaction that you will send to OBN:
1. Click Add to open the Add a New Transaction window.
2. Select the document type from the list of values.
3. The values in the Format and Version fields are displayed based on the document
type selected.
4. Select Send for the document. This action depends on the document type selected.
5. Select the delivery method for testing purposes.
6. Select the delivery method on production instance.
Note: You can only select the delivery method from the list of
delivery methods that you have added in the Communication
Parameters section.
7. Click Submit.
Important: It is important to add every supported transaction that

you send, otherwise you risk having incomplete mappings with
trading partners.
To add a transaction that you will receive from OBN:

1. Click Add to open the Add a New Transaction window.
2. Select the document type from the list of values.
3. The values in the Format and Version fields are displayed based on the document
type selected.
4. Select Send for the document. This action depends on the document type selected.
5. Select the delivery method for testing purposes.
6. Select the delivery method on production instance.
Note: You can only select the delivery method from the list of
delivery methods that you have added in the Communication
Parameters section.

7. Click Submit.
Important: It is important to add every supported transaction that

you send, otherwise you risk having incomplete mappings with
trading partners.
To change the transaction type:

1. Select the appropriate transaction.
2. Click the Update icon to change the delivery method on the test and production
hubs.
3. Click Submit.
To delete the transaction type:

1. Select the appropriate transaction type.
2. Click the Delete icon.

When you remove a document type, Oracle Business Network will not accept that
document type from you that you send for routing nor deliver any messages of this
document type to you for the received documents.
Sending Documents
The Send Documents page enables you to send XML documents directly from the
Oracle Business Network site.
The document types with the Action of Send that you added in your Oracle Business
Network account setup under the Transaction Management appear on the Document
Type list.
Sending Documents
You can send XML documents directly from the Oracle Business Network (OBN) site
using the Send Documents tab.
To send documents:
1. Click the Send Documents option in the Messaging tab.
2. Select the hub that you want to route the document.

3. Select the appropriate document type.
4. Select your approved trading partner from the Send To list to whom you want to
send the transaction.
5. Enter a document number to assign any identifier for this transaction delivery for
tracking purposes.
6. Click Choose File to select the file.
7. Click Send Document to execute the delivery over OBN.
Managing Attachments
You can send and receive business documents along with attachments over OBN. You
can attach any type of document, such as jpeg, .doc, .prn, .gif. For example, you can
upload image attachment for trading partners to send a picture of the item they would
like to order. Suppliers can send a scanned copy of the Invoice to their buyers. OBN can
send or receive over the following communication protocols:
• HTTP/HTTPS
• Web
• Oracle XML Transport Agent (OXTA)
Uploading Attachments
Use the Manage Attachment page to send and receive business documents along with
attachments over OBN. You can view the details of the attached files such as the content
ID, content type, file name, and size.
To upload attachments:
1. Click the Manage Attachments link in the Send Documents page.
2. Enter the content ID for identification purposes.
3. Click the Choose File to select the attachment to upload.
4. Click Upload.
5. Click Submit.

To delete attachments:
1. To delete the attachment, click the Delete icon.

6
Trading Partner Management
About Trading Partners

You can use the Trading Partner page to add, find, and select trading partners on the
Oracle Business Network to initiate the exchange of business documents. Identifying
the trading partners is the final setup step before your company can begin processing
transactions over the Oracle Business Network.
You can also use the Trading Partner Management page to set up links between
suppliers and Oracle buying companies' iSupplier Portal sites. Suppliers can manage
their access to several Supplier Portal sites through the OBN, enabling suppliers to
centralize all of their collaboration activities with their Oracle customers. Additionally,
suppliers can request Supplier Portal accounts from those buyer companies that have
registered their site on the OBN.
Trading Partner Management page on the Oracle Business Network includes the
following sub-tabs:
• Pending Approval:You can use this option to view if there are any requests for
trading partners that must be approved.
• Your Trading Partners: You can use this option to search, approve trading partner
relationships. Suppliers can request Supplier Portal accounts.
• Add Trading Partners: You can use this option to add trading partners.
• Routing Rules: You can use this option to specify the communication paths for
transactions with your approved trading partner relationships and broken routes, if
any.
Adding Trading Partners

You can use the Add Trading Partners tab to select a company from the Oracle
Trading Partner Management 6-1

Business Network Trading Partner Directory to establish a relationship.
When you add a trading partner, you must enter the TP Alias that eliminates the need
for you to know how the trading partner has identified themselves on the OBN. This
reduces the maintenance of having to store the exact ID that a trading partner would
otherwise require you to use when sending them a document. The TP Alias that you
assign each trading partner is verified to ensure uniqueness so that the Oracle Business
Network can generate a valid document route.
Because the number of trading partners available on the Oracle Business Network may
be quite large, you can search for companies with the help of wildcard characters using
a % (percent) to represent a string of characters.
To add trading partners:

1. Click the Partner tab or Partner tile.
2. Select the Add Trading Partner tab.
3. Search for the trading partner.
4. Select the trading partner from the list. Click the Add icon.
5. Enter a Trading Partner Alias (TP Alias) for your selection and click Add.
You must enter a TP Alias value in the corresponding input box for all selected
trading partners. The alias can be a name or numeric identifier that you define,
which is included in the message envelope for all transactions that you send to the
Oracle Business Network. OBN finds the TP Alias on each inbound message and
uses that alias to determine the ultimate receiver of the message. The TP Alias
enables a cross-reference between the trading partner in your internal systems and
what the trading partner has registered as on the Oracle Business Network.
When you create a test account, then you must have a unique TP Alias for the test
account too. Since the test account is a subset of a regular account, it cannot have
same the TP Alias. The application generates a unique alias for the test account too.
6. Click Submit.
To invite a Trading Partner:

If you cannot find the trading partner in the list, then you can use the Invite option to
add a new trading partner.
1. Enter the trading partner name.
2. Enter the contact name.
3. Enter the email address of the contact who will receive the messages.

4. Click Submit.
Approving Trading Partners

Both trading partners must agree to a relationship before exchanging electronic
messages. After you add a company from the Oracle Business Network Trading Partner
directory, the company appears in the Your Trading Partners table with a status of
Pending. The account administrator for this trading partner receives an email
notification that indicates that a request has been made to initiate a trading partner
relationship. The account administrator must approve this request before any two
companies can exchange any documents. When your request is approved, the status for
your trading partner changes to Approved, which indicates that you can begin sending
and receiving transactions with them. Additionally, you also receive a notification
about the relationship status.
Similarly, when another trading partner selects your company (by using the Add
feature of the Trading Partner directory), you receive a notification request to review.
Trading partners that initiate the request appear in the Trading Partners Pending
Approval table. The company contact and their e-mail address also appear if you need
to start any dialogue regarding their request.
To approve trading partners:

2. Click the Pending Approval tab.
3. To accept the request, select the Account Type.
4. Enter the Trading Partner Alias.
5. Click Approve.
Updating Trading Partners

You can update the trading partner information such as the alias name so that all of
your outbound messages can correctly reference the destination or receiving trading
partner.
To update trading partners:

2. Click the Your Trading Partner tab.
3. Select the trading partner and click the Action icon.

4. Enter a new alias value.
5. You can also request for iSP account.
6. Click Submit.
Deleting Trading Partners

You can delete the trading partners you are no longer associated with. The trading
partner receives a notification that you have ended the trading partner relationship.
To delete trading partners:

2. Click the Your Trading Partner tab.
3. Select the trading partner and click the Delete icon.
Routing Rules
After your trading partners have been added and approved, and all required account
setup is complete, you can review the routing rules that you have defined. A routing
rule or mapping is generated after transactions, delivery methods, and your trading
partners have been successfully configured. It indicates the path that transactions follow
as they flow from a sender through the Oracle Business Network to the receiver. The
following table shows an example of a routing path for an incoming purchase order
after all configurations are set up correctly.
Sending TP Transaction Document Info Delivery Method
SampleBuyer Purchase Order cXML 1.2.007. HTTP URL

OrderRequest Connection
The Oracle Business Network identifies any of the document routes that are incomplete.
For example, if you have selected to receive a specific transaction that your trading
partner has not set up to send, a routing rule exception is logged.
You can view your routing rule exceptions using the Routing Rules subtab under
Partners tab.
If you do have routing rule exceptions, you may need to take action. However, it often
indicates different transaction capabilities of trading partners. A basic example follows:
• Company A Capabilities: Send OAG Purchase Order

• Company B Capabilities: Receive cXML Purchase Order, Send cXML Invoice
In this case, there would be a valid routing path for the Purchase Order transaction.
However, a routing rule exception would be noted for the Invoice because Company A
does not support that transaction.
Viewing Routing Rules

You can view the valid routes defined with each trading partner. This is a useful tool for
tracking all of your document route maps, with each trading partner, defined on the
To view routing rules:

1. Click the Partner tab or Partner tab.
2. Click the Routing Rules tab.
3. From the Description list, select the appropriate value to view the routing paths for
outbound and inbound messages or routing rules exceptions:
• Routing rules exceptions
• Documents sent to Oracle Business Network
• Documents received from the Oracle Business Network
4. If you have selected the Routing Rules Exception option, then you can search for
the document type, trading partner name, and the instance to view the routing rules
exceptions.
5. If you have selected either the Documents sent to Oracle Business Network, or the
Documents received from the Oracle Business Network option, then you can
search using the instance type to view the routing rules.

7
Setting Up Notifications
Setting Up Notification Preferences

The Notification Preferences section enables users to register for business document
notifications whether sent or received. You can choose to subscribe or unsubscribe to a
particular transaction type.
You can also view the list of subscribers for a particular transaction type and document
depending on the role.
The Notifications section displays the transactions for which a user can subscribe to
receive messaging related notifications for a given transaction such as purchase orders
or invoices. (Only the documents that your company has identified as supporting on
the Transaction Management section are available.) Subscribers receive e-mail
notifications whenever any of their subscribed transactions have any type of processing
error.
Oracle Business Network enables users to receive a summary E-mail notification
regarding all transactions that were sent or received with errors. This enables customers
to avoid reading multiple error notifications regarding messaging transactions carried
out using Oracle Business Network. Customers can select the time interval for which
the error notification emails sent by OBN can be sent, and all generated error messages
can be summarized in a single e-mail.
In the Notifications section, you can view a list of registered transactions, which
includes the Transaction Type (or document name) and the document direction (send or
receive).
What you can do or view depends on your role. A user who has either the Messaging or
the Administrator role can view all users subscribed to each transaction. A user with the
View Messages and Messaging role can:
• View transaction subscriptions.
• Subscribe to or unsubscribe from a transaction notification by clicking on the
Setting Up Notifications 7-1

appropriate icon.
Important: Oracle recommends that companies always have at least

two employees receiving summary notifications for ease of
maintenance. If companies want to designate additional people, or get
messages on a more timely basis, they can adjust parameters in this
section.
Error Notifications
A time interval to summarize all message exception notifications is available in Oracle
Business Network. This is a time saving feature for users for receiving communications
at the specified interval or one summary e-mail per day avoiding clogging of the
mailbox.
Instead of one email per messaging error, users receive error summary emails for the
transactions subscribed by them. The summaries are sent as per the summary
notification interval specified by the trading partner instead of one notification email
per error.
The Company Profile page on the Profile tab has a Summary Notification Interval list of
values. You can select one of the following options:
• Immediate (No Summarization)
• 1 Hour
• 6 Hours
• 12 Hours
• 24 Hours
The default is Immediate (No Summarization). If you select this option, you will
continue to receive individual e-mails for each transaction that has generated errors. If
you select any value in the LOV, that value is set as the time interval at which you will
get the messaging error notification e-mails. The notification preference setting is
specific to each trading partner.
This notification preference allows you to receive a single summarized notification of all
messaging errors by Error Type, Transaction Type, and Hub Instance (TEST/PROD).
Specify the Summary Notification Interval to determine the time period that OBN will
consolidate your messaging notifications. If you prefer not to receive a summary
notification select Immediate (No Summarization), and you will receive one notification
for every message error recorded by Oracle Business Network.
The Notification Summary e-mail contains the following details: Error Type, Error Text,
Error Code, Cause, Remedy, Document Type, Instance Type.

These details must be included only once in the e-mail as these are common for a
particular category of Notification Summary.
A notification summary category is created by grouping Document Type, Error Type
and Instance Type. The error notification e-mail has a Summary Information table that
contains columns such as timestamp, sender, receiver, OBN control number and
document number.
The table consists of details about all the errors that have been encountered for the
particular notification summary category.
Trading partners who are subscribed to the relevant transaction types (such as Purchase
Order, Invoice, Advance Ship Notice etc) can view the following error notification
types:
Error Notification Type Description
ENCODING_FAILURE This error occurs when the document being

sent contains characters that are not supported
by UTF-8.
HTTP_POST_ERROR This notification type is used when the nature

of the HTTP Post error does not make it
eligible for retry.
HTTP_RETRY_ERROR This notification type is used when Oracle

Business Network is not able to post the
document to the receiver and is in retry mode.
HTTP_RETRY_TIMEOUT This notification type is used when OBN has

already attempted the maximum retry
attempts for posting a document and cannot
continue with retrying posting the document.
METADATA_ERROR_TEMPLATE The notification type is used when there is an

error with the document type being sent or
the delivery method selected or trading
partner alias sent along with the message or
due to an internal error.
PACKAGING_ERROR_TEMPLATE The notification type lets the user know that

the document cannot be processed because it
contains an invalid envelope.

SYSTEM_ERROR_TEMPLATE This is a general template used when the
message routing fails due to various reasons
like ROUTING_ERROR, OXTA Errors, SSL
Handshake error etc.
INBOUND_AUTHENTICATION_FAILURE_ The template is used to send an Error

TEMPLATE Notification if the inbound authentication of
an incoming document has failed.
INVALID_DOCUMENT_TEMPLATE This template is used to notify the trading

Partner, when the trading partner tries to send
a document type not supported by OBN.
The following rules govern the error notification process:

• The sender and receiver trading partners may have provided different time
intervals for receiving the notification summary e-mail. Oracle Business Network
takes individual settings into account and sends notifications to each trading
partner accordingly. The notifications are sent to only those users who have
subscribed to that transaction type for receiving notifications.
• For a trading partner, Oracle Business Network groups all errors encountered
during the time interval specified by the trading partner, according to the error
types, document type and instance type. All the error notifications belonging to the
group within the time duration specified are summarized in a single mail.
• When a trading partner changes the notification preference, Oracle Business

Network sends the pending notification summary e-mails to the trading partner.
The start time is the time when the last notification summary e-mail was sent. The
end time is the time the settings have been modified. After the pending notification
summaries have been sent, the new settings come into effect.
• Time Zone information (3 character time zone code) is displayed along with the
timestamp in the notification summaries that are sent to customers. This applies
both to the start time and end time parameters and the Timestamp column in the
table of messaging error summary information table. The database time zone is
used for Oracle Business Network.
• The Messaging Error Summary Information table is sorted according to the Time
Stamp in descending order.
• The messaging error notifications are summarized and sent to an individual user of
a trading partner only when users are subscribed for the particular transaction type.
If users unsubscribe from receiving notifications for a particular transaction type,
new notification errors of that transaction type are not sent to the users. All

notification errors summarized until the time users unsubscribe for the transaction
must be sent when the summary notification interval elapses. If users subscribe to a
new transaction type, all messaging error notifications are summarized from the
point of subscription onwards.
• There is a maximum limit for the number of rows in the details table. If there are
more errors than the row limit of the details table, a note is displayed, requesting
the trading partner to view the Transaction Monitor for the remaining messages.
No separate notifications are sent for the remaining failure messages.
The following summary notification is a sample error message:

Subject: Oracle BN Error: HTTP Post Error
This error occurred on the Oracle BN Test Message Hub for messages containing document
type: PROCESS_PO_007. One or more messages failed to deliver between 2016-07-03 06:20:56
AM CDT and 2016-07-03 06:50:56 AM CDT Oracle BN has recorded failed HTTP Posts for the
following messages. Due to the nature of the failures, no further attempts to post these messages
will be made.

8
Managing Users
About User Roles

The Oracle Business Network allows companies to create multiple user accounts
associated with their company. Users can be assigned different roles to control what
activities they can perform with their account access.
Adding Users
A user with an Administrator role can add new users, assign user roles, remove, and
deactivate users. When you create a new user associated with your company each new
user receives a welcome notification email message. This notification contains the user's
user name and password. After a new user has been added, the user's record appears in
a table on the Users tab. You can view names, email addresses, user names, roles, and
status of the user.
To add users:
1. Click the User Management icon or Users tab.
2. Click Add User in the User Management section.
3. Enter the name, email address, user name, and password.
4. Click Submit.
Activating, Deactivating, or Removing Users

Administrator users can modify users' roles and their status on the Users tab.
Managing Users 8-1

To activate, deactivate, or remove users:
1. Click the User Management icon.
2. Select the user and click Activate, De-Activate, or Remove. The status of the user
changes appropriately.
User Roles
Roles allow companies to restrict their users to specific functions on the Oracle Business
Network. During company registration, the initial user's profile automatically includes
all roles, including Administrator role, which allows them to create additional users and
assign roles to each of them. Every user can have one or more role assignments.
The user roles include:
• Administrator: Full access (Manager access with company profile, and user
administration).
• Manager: Maintains messaging, punchout configurations, iSupplier wallet and

trading partners.
• View Only: Monitors transactions and can view messaging configuration. The view
only role annot make any updates.
Administrator
The Administrator can:
• Add new users and assign them roles.
• Deactivate or remove users.
• Maintain company profile information.
• View business document notifications to which users have subscribed.
One or more users must have the Administrator role. If an Administrator leaves the
organization or is unavailable, the other Administrators can perform the administrator
role.
By default, the initial user is also assigned to be the Company Contact, which can be
changed to any other user who also has the Administrator role.
The following table shows by tab and sub-tab a user with an Administrator role can
access in the Oracle Business Network.

Administrator Access
Tab Subtab Restrictions and Notes
Profile Company Profile None
Profile User Profile None
Messaging Identifiers Full Access
Trading Partners Your Trading Partners None
Trading Partners Add Trading Partners None
Trading Partners Pending Trading Partner None
Trading Partners Routing Rules None
Users User Management None
Manager Role
A user with Manager role can:
• Configure messaging set up and trading partner administration
• Maintain all communication protocol and transaction setup related to the

processing of electronic messages.
The following table shows by tab and sub-tab, a user with Manager role can access in
the Oracle Business Network.
Messaging Role Access
Profile Company Profile Read-only
Messaging Identifiers None
Messaging Communication Parameters None
Managing Users 8-3

Messaging Transaction Management None
Messaging Notifications None
Messaging Send Documents None
Users - No Access
Trading Partners Your Trading Partners None
Monitor Transaction Monitor None
Punchout Buyer Access None
Punchout Supplier Setup None
Punchout Data Mapping None
View Only Role

The user with the View Messages role can query and monitor transactions that are sent
and received with the trading partners. Typically, functional users or administrators
who are responsible for resolving transaction failures for certain types of business
documents require this role. A user with this role can choose to receive error
notifications for specific business documents.
The following table shows by tab and subtab, a user with the View Messages can access
in the Oracle Business Network.
View Messages Access
Profile Company Profile Read-only
Profile User Profile None
Messaging Identifiers Read-only

Messaging Communication Parameters Read-only
Messaging Transaction Management Read-only
Trading Partners YourTrading Partners Limited access
Monitor Transaction Monitor None
Users - No Access
Managing Users 8-5

9
Testing Outbound and Inbound Messages
About Self-Testing
The Oracle Business Network lets trading partners test their connectivity with the
network by sending or receiving test messages using their OBN account. When you
have completed your messaging setup, you can use the Self-Testing tools to verify
whether you can:
• Receive a test transaction (such as a PO if you are a supplier) into your system from
OBN
• Send a transaction to the Oracle Business Network from your source application
You can perform both inbound and outbound message testing without any assistance
from the Oracle Business Network operations team or participation from other trading
partners.
The message testing tools are on the Self-Testing tab. Only users with the Messaging
role can access this tab.
All test message transmission results appear only on the Self-Testing result pages. Test
messages transacted through the Self-Testing tools do not appear in the Transaction
Monitor. The Transaction Monitor logs and reports only actual messages transacted
between trading partners.
Connectivity
The Oracle Business Network lets trading partners test their connectivity with the
network by performing a self-testing. They can test whether the ERP is functional and
whether OBN is able to connect to the ERP systems.
Outbound Tests
The Send Outbound Test page lets you send a test document from the Oracle Business
Testing Outbound and Inbound Messages 9-1

Network to your system. Oracle Business Network sends the test document to you
using the messaging setup and parameters that you have defined in your Oracle
Business Network account for the particular transaction type. All transaction types that
you added in your account with action of Receive are available for sending. A results
page displays the delivery status of all tests to help you verify whether the Oracle
Business Network could make a successful transmission.
Testing Outbound Messages

You can use the Send Test option for testing outbound messages. Oracle Business
Network sends a sample payload. If you have not selected any document types with the
action of Receive in your message setup (Messaging > Transaction Management page),
then no values are available.
To test outbound message:

1. Click on Test Outbound sub tab.
2. Select the Document Type from the list and click Send.
3. Enter the Document Number. This is mandatory
4. You can upload the test document for sending since some companies require
specific values to be included in certain fields to successfully receive a message,
such as identifiers or authentication credentials.
Download Sample Payloads

You can download test payloads and upload it for your test transmission.
Viewing Outbound Messages

You can view all the sent test messages on the View Outbound Test page. The
transmission details are displayed for each test with a time and date stamp. You can
refresh the page by clicking the tab if a final status does not appear as it may take a few
seconds to get a response from your server.
Most test results show a final status of ERROR or SUCCESS. Review the error message
details for help diagnosing delivery errors.
An ERROR indicates that a connection to your server was made but was unable to
process or successfully validate all the payload values. You should also view the logs on
your server for additional details on why your server responded with the error.
A RETRY status appears when the test message sent over HTTP/S cannot establish any
connection, which an incorrect URL or unavailable server may cause. Verify the URL
parameters that you set up on the Messaging > Communication Parameters page or

verify your target server is online.
A SUCCESS status indicates the Oracle Business Network can transmit a document
payload to your system successfully using your delivery method settings for the
specific transaction type. You are now ready to have trading partners begin sending
you test messages for this transaction type over the Oracle Business Network.
Inbound Tests
Inbound self-testing indicates whether you can send messages to the Oracle Business
Network. The only delivery method that the inbound self-testing tool supports is
HTTP/S, which most suppliers use for transacting with the Oracle Business Network.
After you have configured your headers appropriately, you can send a test. The self-test
URL for sending tests to the Network, appears on the Inbound Tests page.
For inbound header requirements that the Oracle Business Network expects, refer to the
Appendix of the Oracle Business Network XML Solutions Guide.
After sending the test message from your source system, use to the Inbound Tests page
to view if the Oracle Business Network successfully received the message. The Oracle
Business Network performs the same inbound validations as done on real transactions,
which includes authentication validation, XML parsing, and verifying required HTTP
Headers or cXML Headers (depending on the XML format). All inbound tests appear in
the Inbound Test Results table and have a status of SUCCESS or FAIL.
You can view the error details for diagnostic purposes. You can click the icon in the
Details column to display a detailed error page with remedy suggestions and the
header values provided in the transmission. If you are sending an OAG XML
transaction, then a HTTP Headers table appears on the detail error page. If you are
sending a cXML transaction, then a cXML Payload Header table appears. Any required
headers that are missing appear on the detail error page.
When you can send test messages to the Oracle Business Network successfully over
HTTP/S, you are ready to begin sending test messages to the Network for routing to
actual trading partners. You must add receiver identifier information to your HTTP
header or cXML payload header, depending on your document format.
For more information, refer to the Oracle Business Network XML Solutions Guide.
Testing Outbound and Inbound Messages 9-3

10
Transaction Monitor
About Transaction Monitor

The Monitor tab lets you track either the status of all documents that your company has
sent to the Oracle Business Network or the status of all documents that a trading
partner has sent to your company. Also, you can download any document that appears
in the Transaction Monitor.
Viewing Messages
You can view messages for the OBN Test Message Hub or the OBN Production
Message Hub by selecting the appropriate instance type from the list of values.
To view messages:
1. Select the appropriate sub tab to view either Sent Messages or Received Messages,
and then click Search.
2. To filter your search results, enter information into any of the search criteria fields.
You can use wildcard characters (%) in the Trading Partner Name and Document
Number fields to locate messages with companies that match a partial name or
number search. You can also search for documents processed during a particular
date range.
Note: When you login as a user for a test account and select the
instance type as Test, then the messages for Production Hub are
disabled.
Downloading Messages
You can use the Transaction Monitor to download documents. If your trading partner is
Transaction Monitor 10-1

sending or receiving a document in a different document format, for example, a buyer
sends an OAG PO to the Oracle Business Network, but the supplier receives the PO in
the cXML format, then there are two different messages stored in this flow. Both trading
partners have the option to download either of the two Purchase Order (PO) formats.
When selecting the transaction for download, if a transformation has occurred, the
Oracle Business Network allows you to choose the document format that you want to
download. You can select either My Document or My Trading Partner's Document.
Accessing both messages can be helpful for resolving data mapping issues between
your trading partners.
To download messages:
1. To download a document, select a transaction and click the Download icon. You
can also download attachments.
Viewing Transaction Details

When Oracle Business Network receives messages, it marks a time stamp on the
document. The time zone reflects the Oracle Business Network server time, not a user
time zone. OBN assigns a unique tracking number, called the Control Number, to each
message. A Document Number appears in the transaction monitor, which may be
populated from the incoming message envelope. You can view additional information
about a transaction by drilling-down on the Control Number. This displays a complete
activity log for the message and shows:
• How (delivery method) and in what form (document type) the message was sent to
• Corresponding information on the delivery to the receiving trading partner.
You can view the detailed error messages that appeared on the main Transaction
Monitor window.
View Message Errors
You can find additional information regarding a message error by selecting the Error
Code from either the Activity Log or the main Transaction Monitor window. This action
displays the full error code text, description of the error, possible causes, and potential
remedies.
Common Errors
Exception cannot reprocess: This error, also known as a Dead message, indicates that
the message body contains syntax errors, and that the Oracle Business Network cannot
process it any further. The XML message is validated when the Oracle Business
Network receives it against either the DTD for the document type or the XML standard
being used. The sender must fix the errors and re-send the message to the Oracle
Business Network.

Exception Processing an HTTP Post: This error indicates that there is a problem
posting to the recipient's HTTPS server. Possible causes include: their server is down,
the URL specified in their HTTP delivery method setup (under Communication
Parameters subtab) is incorrect, or there may be an issue with the trusted certificate
(called when posting to an HTTPS site). If Oracle Business Network encounters issues
when trying to deliver a message though HTTP, it attempts to re-send the message. This
automatic reprocessing continues based on an expanding time interval after each failed
attempt, up to 72 hours. After a certain number of failed attempts, Oracle Business
Network stops trying to deliver the message. If you are unable to diagnose the HTTP
posting error, log a support issue according to the support instructions on the Resources
tab.
Exception pending reprocessing: This error message generally refers to a failed
document route, which occurs when the Oracle Business Network cannot determine a
document route. The error details explain what the missing or bad setup is for either
trading partner. You or your trading partner should correct the setup errors and then
either re-send the message or submit a support issue for that message that Oracle
Business Network Operations should reprocess.
A common cause for a failed route occurs when the sender has not correctly set the
Trading Partner Alias field for their intended receiving trading partner. As the Oracle
Business Network receives each message, it reads the message envelope to authenticate
the sender and verifies that the receiver ID in the envelope matches one of the sender's
TP Alias values for one of their trading partners setup in their Oracle Business Network
account. If a match is not found between the value set in the Destination Trading
Partner Location Code (setup in the sender's XML Gateway) and the TP Alias value (set
in the sender's Oracle Business Network account on the Trading Partners tab), the
Oracle Business Network reports a missing document route when processing the
message. The Transaction Monitor displays a status of Exception; pending reprocessing,
when one trading partner has not correctly set their messaging parameters. After
correcting the appropriate parameters, the Oracle Business Network revalidates the
message route, and if no errors still exist, the Oracle Business Network support team
can reprocess the message to prevent the sender from having to re-send the message.
Transaction Monitor 10-3

11
Setting up Outbound XML Messaging
About Outbound XML Messaging

This chapter describes the process of sending XML documents from the buyer's Oracle
EBS Applications system to the supplier's system through the Oracle Business Network.
Refer to the Peoplesoft or Cloud applications user guides for information on sending
XML documents.
Refer to the following document for information on sending XML documents on Oracle
Cloud using Collaboration Messaging Framework: https://docs.oracle.
com/en/cloud/saas/supply-chain-management/20c/facmm/introduction.
html#FACMM3689192
The major components that are used to send XML messages or documents include the
following:
• The buyer's Oracle Purchasing R12 system, which includes Oracle XML Gateway
and Oracle XML Transport Agent (OTA). In these components, the buyer creates
and records the Process PO (purchase order) and Change PO transactions. Using
these components, a corresponding XML document is generated and transmitted to
The Oracle Transport Agent is used to transfer messages between the buyer and
OBN. It uses HTTPS as the communication protocol to transfer the messages and
the documents.
• Oracle Business Network, the hub that receives the XML documents from the
buyer's system, performs appropriate data transformations, and sends the XML
documents to supplier's system. Hubs are typically used to route documents to and
from trading partners.
You also use OBN to set transaction delivery preferences, test transaction delivery
and exchange production documents with your suppliers
Setting up Outbound XML Messaging 11-1

• The supplier system that receives the XML documents from Oracle Business
Network and records the documents.
Process Overview
When a buyer creates an approved purchase order (PO) in the Oracle Purchasing or any
other ERP system, the system records a new purchase order document. When a buyer
makes changes to an existing purchase order, the recorded change is a revision to the
purchase order document. The system generates XML documents from the data in these
purchase order documents. The documents created in Oracle Purchasing and supported
by the Oracle Business Network are:
• Standard PO
• Change Standard PO
• Release against a Blanket PO
• Change Release against a Blanket PO
Before you can send XML messages, ensure to create a purchase order. For information
how to create purchase orders or make changes to a purchase order, see Oracle
Purchasing Users Guide.
Oracle XML Gateway

Oracle XML Gateway is the product that generates an XML document based on:
• Purchase order (PO) document data in Oracle Applications.
• Document type definitions (DTDs) stored in Oracle Applications.
• Setup in Oracle XML Gateway including optional data mapping.
The buyer uses Oracle XML Gateway to receive the purchase order ID (PO ID) from the
Advanced Queue (AQ). Oracle XML Gateway generates a corresponding XML
document. Additionally, Oracle XML Gateway provides optional data mapping that
enables the buyer to convert certain data in the XML document before transmitting it to
the supplier.
The following table shows the types of XML documents generated for each type of
purchase order (PO) event:

XML Documents for Each Purchasing Event
Oracle Purchasing Event XML Document Generated
Standard PO Process_PO_007
Change to a Standard PO Change_PO_006
Release against a Blanket PO Process_PO_007
Change to a Release against a Blanket PO Change_PO_006
Cancel a Release or Standard PO Change_PO_006
XML Document Routing

A set of message attributes is transmitted with the business (purchase order) XML
document. Collectively, these attributes are the XML Gateway envelope. The
information in the XML Gateway envelope is automatically generated for each XML
document using the setup in Oracle XML Gateway. Values entered in the Trading
Partner Setup window, such as the Source Trading Partner Location Code, are sent as
part of the envelope.
The envelope information allows proper routing and transmission of the XML
document. This information is important for the Oracle Business Network to identify
and authenticate the sender of the XML document, as well as to determine the
appropriate final destination (that is, the supplier). It is also useful for troubleshooting
purposes or to the supplier in receiving the XML document.
For more information about the XML Gateway envelope, refer to the Oracle XML
Gateway User's Guide and Oracle Business Network XML Solutions Guide.
Oracle XML Gateway passes the generated XML document to an Advance Queue (AQ),
after which Oracle Transport Agent obtains the XML document and delivers it to the
Oracle Transport Agent--Buyer's System

Oracle Transport Agent (OTA) offers a message transport layer between two systems.
The key benefit is a guaranteed, one-time delivery of the message over HTTPS, when
both systems are using Oracle Transport Agent. The transport layer (OTA) in the
buyer's Oracle Applications system obtains the XML document from the Advance
Queue from Oracle XML Gateway. When Oracle Transport Agent in the buyer's system
communicates with the transport layer (OTA) on the Oracle Business Network, the

XML document is sent to Oracle Business Network over the internet. HTTPS is used for
secure transmission of documents to the Oracle Business Network.
The Oracle Business Network then determines the appropriate delivery method that the
supplier has chosen and delivers the message. The supplier is responsible for the
necessary setups in its system to enable receiving of XML documents from Oracle
Business Network.
For more information on the XML documents, see Oracle Business Network XML
Solutions Guide.
Implementation Steps
The following sections describe in detail the setup steps required in Oracle Business
Network, Oracle XML Gateway, and the supplier's system to enable the Oracle
Purchasing XML documents to be transmitted from the buyer to the supplier.
• Setting Up Oracle Business Network
• Setting Up Oracle XML Gateway

• Setting Up Hub
• Setting Up Trading Partner Setup
• Test and Production Transaction Processing
Setting up OBN
A buyer sets up the outbound messages in Oracle Business Network for the messages
that the buyer would like to support.
To set up OBN:
1. Navigate to the Messaging Set up and Messaging tab in the Oracle Business
Network to set up the outbound messages.
2. Add the Oracle Applications Group (OAG) Purchase Order and OAG Change
Order as the transactions.
3. Select the appropriate delivery method (Oracle Transport Agent) and the direction
(Send).
Additional Information: No specific setup step is required in Oracle

Purchasing for generating and transmitting purchasing XML
documents. Note, however, that the XML documents are generated

for each supplier and supplier site. Also, the generation and
transmission of XML documents is based on:
• Supplier and supplier site setup in Oracle Purchasing.
• Corresponding trading partner setup for each supplier and

supplier site in the Oracle XML Gateway.
If the buyer uses a multiple organizations installation of Oracle

Applications, then you must perform the corresponding setup in
Oracle XML Gateway for each supplier and supplier site in
different organizations. For information about setting up suppliers
and supplier sites in Oracle Purchasing, see: Oracle Purchasing Users
Guide.
Setting Up Oracle XML Gateway

The setup by the buyer for Oracle XML Gateway includes entering data in the Hub
Definitions window and the Trading Partner Setup window.
Log in to Oracle Applications R12 and choose the XML Gateway responsibility. From
the XML Gateway menu, choose Setup and choose Define Hubs.
Additional Information: If you use multiple organization setup in

Oracle Applications, you should define the XML Gateway
responsibility chosen for the login for the same organization for which
the applicable supplier site is defined.
Using the Oracle XML Gateway, buyers can set up the hub and their trading partners in
the Hub Definitions and the Trading Partner Setup windows.
Navigate to the XML Gateway responsibility and select Setup > Define Hubs.
Setting Up Hub
A hub is an integration point and routes documents to and from trading partners.
Oracle Business Network is an example of a hub.
You must create a hub definition for each environment of the Oracle Business Network,
specifically Oracle Business Network Test hub and Oracle Business Network
Production hub. If you have test and production instances of Oracle Applications R12,
you can define Oracle Business Network Test URL in the test instance and Oracle
Business Network Production URL in the production instance. In this scenario, do all of
your XML testing in the test instance of Oracle Procurement and route transactions to
Oracle Business Network's Test hub. Your production XML transactions should flow

from Oracle Procurement Production to Oracle Business Network's Production hub.
To set up the hub:

1. Use the XML Gateway responsibility.
2. Navigate to Setup > Define Hubs.
3. In the Hub Definitions window, you define the hub and the authorized users who
are conducting business through the hub. The hub users that you enter in this
window appear in the Trading Partner Setup window.
4. Enter the following data that relates to the Oracle Business Network's Test Hub
instance:
• Name: A hub name for the Setup instance, such as Oracle BN Test.
• Protocol Type: The communication protocol associated with the hub being
defined. SelectOTAHS-ATCH from the list.
• Protocol Address: The complete URL (including service or servlet) where the
Transport Agent attempts to post the XML document to the Oracle Business
Network Setup site. This URL information is available on the Resources tab at
the Oracle Business Network site.
In the Hub Users region of the Hub Definitions window, enter information
pertaining to your Oracle Business Network account. You may use any active user
who belongs to your company's Oracle Business Network registration:
• User Name: Oracle Business Network user name.
• Password: Oracle Business Network password.
• Hub Entity Code: An identifier to gain credentials on the Oracle Business

Network. It must be set to your account's primary identifier that you have set
on the Oracle Business Network. It is recommended that you use your DUNS
number as the primary identifier and Hub Entity Code. When XML
transactions are delivered, the Hub Entity Code appears in the XML envelope
information to identify the source of the message.
You can follow the steps listed above for setting up the Oracle Business Network
Production hub definition. You can choose to create this hub definition only in your
Applications R12 production instance. All entries are the same as your test instance,
with the exceptions of Name and Protocol Address. The Protocol Address is the
complete URL for posting to the Oracle BN Production Hub instance. This
information is available on the Resources tab at the Oracle Business Network site.

Additional Information: Hub definition is a one-time setup. If you
change your user name, password, or identifier on the Oracle
Business Network, you must change the hub definitions
accordingly.
Setting Up Trading Partner

The Trading Partner Setup window lets you enable messages for the trading partner
(the supplier) for processing through the Oracle XML Gateway engine. In Oracle XML
Gateway, the term trading partner refers to a supplier at a particular site (address) with
which you exchange messages. Since a given supplier may have several sites, you must
define one trading partner setup in this window for each supplier site. During message
processing by Oracle XML Gateway, trading partner setup data:
• Link a particular address location in Oracle Applications to the trading partner
(supplier) definition in Oracle XML Gateway.
• Provide a means of telling the execution engine which trading partner message map
to use.
• Enable specific transactions for the trading partner (supplier).
• Determine how to deliver the message.
Trading partner setup in Oracle XML Gateway is organization-dependent. This means

that the list of supplier sites is limited to those defined for the organization linked to the
login responsibility. The setup in this window includes identification of the supplier
site, the messages enabled for that site, and the delivery mechanism.
To set up trading partner:

1. Use the Oracle XML Gateway responsibility.
2. From the XML Gateway menu, select Setup > Define Trading Partners.
3. On the Trading Partner Setup window, enter the following details set up your
trading partner:
4. Trading Partner Type: Defines the type of trading partner, such as supplier, buyer,
bank, or internal location. Select the supplier from the list. When you select the
Supplier, the supplier names and supplier sites appear in the Trading Partner Name
and Trading Partner Site lists.
5. Trading Partner Name: Select the appropriate supplier name from the list.

6. Trading Partner Site: Select the applicable supplier site from the list. The list
displays only those supplier sites that are associated with the organization of the
login responsibility.
7. Company Admin Email: Specifies the email address of the supplier administration
contact to receive email messages regarding warnings and errors. Oracle XML
Gateway may initiate these notifications. Enter the email address of the supplier
company's Oracle Business Network Administrator.
Setting Up Purchase Orders or Releases

You use the Oracle XML Gateway to set up the purchase orders. You can enter the
details in the Trading Partner Details region for the new purchase order document.
To set up Purchase Order:

1. In the Trading Partner details region, enter the following information:
• Transaction Type: The standard product short code for the base Oracle
Application. Only Oracle XML Gateway uses these values. This field displays a
list for a combination of the Transaction Type and Transaction Sub Type. Select
the PO outbound message transaction type PO-PRO-OAG-PO-PROCESS-
OUT.
• Transaction Sub Type: A code for a particular transaction that is the default
value based on the Transaction Type. The last letter identifies the direction of
the transaction: I for inbound and O for outbound.
• Standard Code: The default value based on the Transaction Type. It is the code
that was set up in the Define XML Standards window during Oracle XML
Gateway implementation.
• External Transaction Type: The default value based on the Transaction Type. It
is the primary external identifier for the XML message. You defined these
values on the Define Transactions window during Oracle XML Gateway
implementation. You can find these values in the Oracle XML Gateway
envelope.
• External Transaction Sub Type: The default value based on the Transaction
Type. It is the secondary external identifier for the XML message. You defined
this value on the Define Transactions window during Oracle XML Gateway
implementation. You can find these values in the Oracle XML Gateway
envelope.
• Map: Select itg_process_po_006_out.

• Connection/Hub: Specifies the message communication method. From the list,
select the Oracle Business Network name that you previously specified in the
Hub Definitions window. If you are testing transactions, select the Oracle
Business Network Test name. If this is for your production instance or you are
ready to go into production with this trading partner, you should select the
Oracle Business Network Production hub name.
• Protocol Type: Automatically populated when you select the Oracle Business
Network Name. This value comes directly from the Hub Definitions window.
• User Name: From the list, select the user name that you specified in Hub
Definition. It is the same as your account's user name on Oracle Business
Network.
• Password and Protocol Address: Automatically populated when you select a

user name. The values for these fields were entered in the Hub Definitions
window.
• Source Trading Partner Location Code: Automatically populated when you

select a user name. This is the code found in the PARTY_SITE_ID field of the
XML Gateway envelope. This code identifies the source of the message (the
sending organization).
• Destination Trading Partner Location Code: The code for the ultimate
recipient of the XML message and is found in the ATTRIBUTE3 field of the
XML Gateway envelope. The Oracle Business Network needs this code to route
the message to the appropriate trading partner. The value must match the
Trading Partner Alias value in Oracle Business Network that you set for this
trading partner.
• Document Confirmation: The indicator for the confirmation level that the
supplier would like to send. You should accept the field default value of 0
(zero).
• Routing: The address to route the outbound message to another trading partner
when using the Static Routing method. The Routing field should remain empty.
Additional Information: Repeat the setup in the Trading Partner

Setup window in Oracle XML Gateway for each supplier and
supplier site for which the buyer generates and transmits XML
documents.
Setting Up Change Orders

Enter information for the Change PO document in a new line of the Trading Partner

Details region. Enter all information the same as a new purchase order in the preceding
section, except for:
• Transaction Type: Choose the PO Change transaction type PO-POCO-OAG-PO-
Change-Out.
• Map: Choose itg_change_po_006_out.
Test and Production Transactions Process

For each trading partner, it is recommended that you send a series of test transactions
through Oracle Business Network Test Hub to ensure that your trading partner is
receiving and processing the message successfully. When you are ready to move to
production with each trading partner, you should verify that your Applications R12
production instance has defined the trading partner (as the preceding section describes)
and the Connection Hub is set to the Oracle Business Network Production name. This
routes the messages to the Oracle Business Network Production Hub instance.
To send any PO or Change PO XML transactions, verify that the necessary Workflow
processes are running. For more information refer to the Oracle XML Gateway User's
Guide.

12
Inbound XML
About Inbound XML Messaging

This chapter describes the process that sends XML documents from the supplier's
system to the buyer's Oracle Applications system through the Oracle Business Network.
The major components are:
• The supplier's system generates a PO Acknowledgement, an Advance Ship Notice
(ASN), an Invoice, or a Change Sales Order XML message in a supported format of
the Oracle Business Network. The supplier posts the message using their chosen
protocol to the Oracle Business Network.
• Oracle Business Network, the hub that receives the XML documents from the
supplier's system, performs appropriate data transformations, and sends the XML
documents to the buyer's Oracle Applications R12 system using the Oracle
Transport Agent (OTA).
• The Oracle Applications R12 system receives the transaction. Then, the Oracle XML
Gateway records the transaction, and it is processed into the appropriate
application. For example, the Oracle Purchasing Receiving Open Interface processes
an inbound ASN to finalize the transaction.
Important: For limitations regarding inbound ASNs and invoices, refer

to the Oracle Purchasing User's Guide, the Oracle Purchasing R12
Transaction Delivery Guide, and the Oracle Payables User Guide.
When a supplier creates an XML message in its system, it can POST the message to the
Oracle Business Network. The documents that a supplier creates and that the Oracle
Business Network supports are:
• Purchase Order Acknowledgement
Inbound XML 12-1

• Change Sales Order
• Advance Ship Notice
• Invoice
Process Overview
The Process Overview describes the inbound XML messaging activities:
• Supplier Activities
• Oracle Business Network Processing
• Oracle Transport Agent and Workflow APIs
• Oracle XML Gateway
The implementation steps for inbound XML messaging with Oracle Business Network
as follows:
Supplier Activities
When a supplier creates an XML message in its system, it can POST the message to the
Oracle Business Network. The documents that a supplier creates and that the Oracle
Business Network supports are:
• Purchase Order Acknowledgement
• Advance Ship Notice
• Invoice
• Change Sales Order
The supplier is responsible for the necessary setups in its system to ensure that the
appropriate information appears in the XML message structure to comply with Oracle
Business Network. For more information, see the Oracle Business Network XML Solutions
Guide.
Oracle Business Network Processing

The Oracle Business Network determines the appropriate destination (the Oracle
Applications R12 buyer) based on the information and envelope of the message. The
Oracle Business Network performs any required transformations to the message and
then uses Oracle Transport Agent (OTA) to send the message through HTTPS to the

buyer's Oracle Applications R12 system.
Oracle Transport Agent and Workflow APIs (Buyer Company)

The Oracle Transport Agent on the buyer's system obtains the XML document from the
inbound queue. The XML message waits in this inbound queue until a listener in the
Workflow Business Event System detects it. The Workflow Business Event System
controls the movement of data through the inbound process. When the listener detects
the XML message in the inbound queue, it initiates Oracle XML Gateway to continue
the process. The Workflow Listener process must be running.
Oracle XML Gateway (Buyer Company)

Oracle XML Gateway is the product that receives the XML document. Oracle XML
Gateway:
• Calls the XML parser to validate the XML document (message) to see that required
fields are present and in the correct order.
• Performs data mapping (if any) that is set up in Oracle XML Gateway, calls PL/SQL
procedures to further validate the document (for example, to derive correct
document internal identifier fields, such as PO_HEADER_ID, used for storing the
information in the Receiving Open Interface).
• Inserts the data into the appropriate Oracle Applications Receiving or Payables
Open Interface.
If the initial validation finds errors in the XML document, the system rejects the
transaction and sends an e-mail notification to the supplier, to the e-mail address
defined for the supplier in the Trading Partner Setup window. Refer to the appropriate
Oracle Application guides for more information on this validation.
After initial validation, the buying company must process the ASN or invoice through
the appropriate transaction processor to do final validation and insert the appropriate
record into the receiving or payables tables.
Implementation Steps
The following topics describe the setups required to receive inbound XML messages
from the Oracle Business Network.
• Oracle XML Gateway, page 12-4
• Setting Up Trading Partner, page 12-4
• Setting Up Purchase Order Acknowledgement, page 12-6
Inbound XML 12-3

• Setting Up Advance Ship Notices, page 12-5
• Setting Up Invoices, page 12-6
• Setting Up Change Sales Orders, page 12-7
No specific setup step is required in Oracle Purchasing or Oracle Payables for receiving
XML documents. Note, however, that the XML documents are received and processed
at the supplier site level. Thus, the supplier and supplier site must be setup in Oracle
R12 and selected in Oracle XML Gateway.
If the buyer uses a multiple organization installation of Oracle Applications, then you
must perform the corresponding setup in Oracle XML Gateway for each supplier and
supplier site in different organizations. For information about setting up suppliers and
supplier sites in Oracle Purchasing, see: Oracle Purchasing Users Guide.
Setting Up Oracle XML Gateway

The setup by the buyer for Oracle XML Gateway includes entering data in the Hub
Definitions window and the Trading Partner Setup window. Log in to Oracle
Applications and choose the XML Gateway responsibility. From the XML Gateway
menu, select Setup > Define Hubs.
Additional Information: If you use a multiple organization setup in

Oracle Applications, you should define the XML Gateway
responsibility chosen for the login for the same organization for which
you have defined the applicable supplier site (the site to which to
transmit the XML documents).
CHECK THIS
Buyers use Oracle XML Gateway to set up the hub and their trading partners in the
Hub Definitions and the Trading Partner Setup windows.
Use the XML Gateway responsibility and select Setup > Define Hubs.
Setting Up Trading Partner

From the XML Gateway menu, select Setup > Define Trading Partners. In the Trading
Partner Setup window, you can enable messages for the trading partner (the supplier).
This window enables a message to be processed through the Oracle XML Gateway
engine. In Oracle XML Gateway, the term trading partner refers to a supplier at a
particular site (address) with which you exchange messages. Because a given supplier
may have several sites, you must define one trading partner setup in this window for
each supplier site. During message processing by Oracle XML Gateway, trading partner
setup data:

• Link a particular address location in Oracle Applications to the trading partner
(supplier) definition in Oracle XML Gateway.
• Provide a means of telling the execution engine which trading partner message map
to use.
• Enable specific transactions for the trading partner (supplier).
• Determine how to deliver the message.
Multiple Organizations Consideration

Trading partner setup in Oracle XML Gateway is organization-dependent. This means
that the list of supplier sites is limited to those defined for the organization linked to the
login responsibility. The setup in this window includes identification of the supplier
site, the messages enabled for that site, and the delivery mechanism.
If you have already setup a supplier and supplier site for XML messaging (for example,
for outbound purchase orders), then you do not have to enter the header information.
Instead, you should query the existing trading partner record and proceed to the
following Details Information.
• Trading Partner Type: Defines the type of trading partner, such as Supplier,
Customer, Bank, or internal location. Select Supplier from the list. After you select
Supplier, the supplier names and supplier sites appear in the Trading Partner Name
and Trading Partner Site lists.
• Trading Partner Name: Select the appropriate supplier name from the list.
• Trading Partner Site: Select the applicable supplier site from the list. The list
displays only those supplier sites that are associated with the organization of the
login responsibility.
• Company Admin Email: Enter the email address of the supplier company's Oracle
Business Network Administrator. The supplier's administration contact receives
email messages regarding warnings and errors. XML Gateway may initiate these
notifications.
Setting Up Advance Ship Notices

In the Trading Partner Details region, enter the information for the Advance Ship
Notice document:
To set up ASN:
1. Transaction Type: This is standard product short code for the base Oracle
Inbound XML 12-5

Application. You specify the values in the Define Transactions window in Oracle
XML Gateway during Oracle XML Gateway implementation. This field displays a
list for a combination of the and Transaction Sub Type. Select the ASN POS_ASN-
POS_ASN-OAG-POS_ASN-POS_ASN-IN.
2. Map: Select the name of the map created using Oracle XML Gateway Message
Designer from the list. Select POS_ASN from the list. (Although you can customize
this map, Oracle Business Network does not support customization.)
3. Source Trading Partner Location Code: This is a user-defined field. This value
must match the Trading Partner Alias value in Oracle Business Network that you
set for this trading partner.
4. Document Confirmation: You should accept the field default value of 0 (zero).
5. Routing: The Routing field should remain empty.
Additional Information: Repeat the setup in the Trading Partners

Setup window in Oracle XML Gateway for each supplier and
supplier site for which the buyer generates and transmits the XML
documents.
Setting Up Purchase Order Acknowledgement

You enter the details similar to Advance Ship Notice:
• Transaction Type: Select the transaction type PO-ACKPO-OAG-PO-
ACKNOWLEDGE-IN from the list.
• Map: SelectCLN_POACKPO_OAG72_IN.
Setting Up Invoices
Enter information for the invoice document in a new line of the Trading Partner Details
region. All information that you enter is the same as Advance Ship Notice in the
preceding section, except:
• Transaction Type: Select the transaction type AP-INI-OAG-Invoice-Process-In
from the list
• Select171_process_invoice_002.

Setting Up Change Sales Orders
Enter information for the Change Sales Order document in a new line of the Trading
Partner Details region. All information that you enter is the same as the other inbound
transactions defined above, except:
• Transaction Type: Select the transaction type CLN-CHANGESO-OAG-
SALESORDER-CHANGE-IN from the list.
• Map: SelectCLN_CHANGE_SALESORDER_OAG72_IN.
Inbound XML 12-7

13
Punchout
Punchout Using Oracle Business Network

Punchout setup configuration required on Oracle Business Network is detailed in this
chapter. Punchout is the process by which a buying organization's employees can
browse the contents of a supplier's online catalog of goods/services, select these items or
services for purchase, and have them added to a draft Requisition. In order to start
punchout via OBN, you and your trading partner (with whom you wish to do business)
will need to have accounts on Oracle Business Network.
Punchout enables buyers to click a link that goes to a supplier's catalog, search for items
on the supplier's site, and return those items directly to the buyer's shopping cart. The
ability to access remote catalogs using punchout is beneficial to both the supplier and
the buyer. It enables suppliers to maintain and host their own catalog information,
while buyers can search for items from within Oracle iProcurement. The burden of
maintaining the hosted catalog is removed from buying organizations, reducing catalog
maintenance and data storage costs. In addition to the local catalog, punchout provides
a single point of entry to catalog content, regardless of where the content resides.
Remote catalogs are particularly useful for products that are configurable or include
highly variable or dynamic items and pricing. These products are difficult and costly to
maintain in a buyer-hosted (local) catalog. Catalogs with these types of items are better
maintained by the supplier, to ensure the latest content and pricing are available, and to
eliminate inefficiencies (such as purchase order revisions to correct pricing).
With Punchout from Oracle iProcurement to Supplier-Hosted Catalog via Oracle
Business Network, the supplier hosts a cXML catalog at its own site, or Web store, that
the requester in Oracle iProcurement accesses via OBN. Using OBN for the punchout
simplifies the initial setup process, and makes the authentication and maintenance of
the punchout easier. iProcurement requesters have access to a centralized collection of
punchouts. The iProcurement Administrator does not have to configure a punchout for
each supplier, but can simply download the supplier's punchout definition available on
OBN.
Suppliers only have to register on OBN, and define their punchouts on OBN once,
Punchout 13-1
rather than configuring punchout separately for each iProcurement customer. Suppliers
can control the visibility of their punchout definitions by publishing or unpublishing
the punchout on OBN.
Punchout Redirect
When requesters click the punchout link, they are redirected to the supplier site. (The
supplier hosts the catalog at their own site or web store.). Using OBN for the punchout
simplifies the initial setup process, and also the authentication and maintenance of the
punchout. The supplier must set up a punchout from OBN to their site. To set up access
to the supplier site using OBN, the catalog administrator needs to download the
supplier punchout definition from OBN. Downloading the supplier punchout definition
seeds the punchout definition from Oracle iProcurement to the supplier site through
OBN, without requiring the catalog administrator to perform manual setup. In the
illustration:
1. The requester logs in to Oracle iProcurement.
2. From Oracle iProcurement, the requester clicks a link to the supplier site.
3. OBN authenticates the requester, and sends a punchout request to the supplier.
4. The supplier site responds to OBN.

5. OBN forwards the supplier site's response to Oracle iProcurement.
6. Oracle iProcurement redirects the requester's browser to the supplier site for
shopping.
7. When the requester finishes shopping, the supplier site returns the shopping cart
items to Oracle iProcurement via the requester's browser.
8. The requester completes the checkout process, and Oracle iProcurement processes
the order.
Punchout page in Oracle Business Network

Buyer Access: Use this option to choose from the list of published supplier punchout
sites available on Oracle Business Network, and add access to their punchout sites to
start shopping.
Supplier Setup: Use this option to configure the your organisation's punchout details
that will be used by customers to access your company's catalogs. The punchout
URLyou define here is your company portal, that is hosted by you, to be accessed by
your trading partner to shop from your catalog. The password to access your site,
Communication Protocol (either XML or cXML), Company Name, Description, and
Logo that is available on OBN for your trading partners is also defined here. After
providing these details Publish the punchout. Publishing makes the configuration
available and accessible to all trading partners.
Data Mapping: Use this option to define the conversions between Buyer codes and
Supplier codes. For example, a buyer uses the unit of measure (UOM) code EA for Each.
The supplier uses E. The customer can use either OBN or Oracle iProcurement
(specifically, e-Commerce Gateway), to map these codes.
Using thesee options you can configure your company as a buyer company accessing
supplier sites. You can also configure yourself as a supplier for others to access your
website, and view your catalog. The following setup summarizes the configuration
steps to start punchout using Oracle Business Network. Oracle E-Business Suite
Environment is used as an example, for the punchout in the setups steps. The setup is
the same for Self Service Cloud Applications.
Setup for Oracle Customers using Buyer Access

As a buying company, the following list outlines the steps to configure punchout
redirect on Oracle Business Network. Register on Oracle Business Network (OBN).
1. Register on Oracle Business Network (OBN).
2. Define the identifiers for your company.
Punchout 13-3
3. Add access to a Punchout Supplier on OBN.
4. Secure e-Business Suite connectivity to OBN.
5. Configure your e-Business Suite environment.
Register on Oracle Business Network:

1. If your company is already registered, and has an OBN account, then go to the next
step.
2. If you do not have an account on OBN, register your company to create an account.
See Registering with Oracle Business Network, page 7-1 for more information.
3. If you are not sure whether your company has an OBN account, contact your
company administrator.
Define Identifiers for your company:

1. Click the Messaging Setup sub-tab on the left side of the page.
2. In the Identifiers region, click Add to enter a primary identifier.
Note: OBN recommends that you use D-U-N-S number as a

primary identifier.
For the identifier type that you select, you must enter a unique value to identify
your company. This is your company's identifier and would be used to identify and
associate all the messages and transactions sent, or to be received by your company.
You may also opt for other Identifier types such as phone number, tax ID, network
ID, and so on.
See Identifiers, page 5-3 for more information.
3. The primary identifier should be the same as the Buyer Company Identification
used in the Content Zone that is defined in Oracle e-Business Suite.
Add Access to a punchout supplier on OBN or Configure Punchout:

1. Check whether your suppliers have configured their punchout details in OBN by
navigating to the Buyer Access subtab in the Punchout page.
2. Select Add Punchout to see the published list of suppliers already available on
OBN.
3. If the supplier whose online catalog you wish to browse is listed, then add access to
the punchout supplier on OBN.

Secure e-Business Suite Connectivity to OBN:
This step can only be completed with the assistance of the System Administrator for
your e-Business Suite instance. You need to include the OBN URL certificate in the
certificate file (wallet) that will be used in the e-Business Suite system to ensure that the
connection between e-Business Suite and OBN is secure.
Use the following steps include the OBN URL in the certificate file of E-business Suite.
1. Open the https://businessnetwork.oracle.com in the browser. Click the padlock icon
in or near the address bar and then click More Information.
2. Click View Certificate, and in the Details tab, select each level in the Certificate
Hierarchy and then click Export.
3. Save the file as an X.509 Certificate (PEM). Repeat step 2 and step 3 at each level of
the Certificate Hierarchy. See: MyOracle Support (MOS) note ID 1915517.1 for
additional information about certificates.
4. Authenticate the EBS and OBN connection by logging in to e-Business Suite as a

System Administrator.
5. Query the profile option POR: CA Certificate File Name. Note the file location of
the profile option and add the downloaded OBN URL Certificates as mentioned in
the above steps into this file. Now the connection between E-Business Suite and
OBN is properly authenticated.
Configure Your e-Business Suite Environment:

These steps can only be completed with the assistance of the System Administrator for
your EBS instance.
Punchout 13-5
1. Log in to your E-Business Suite test environment that is connected to OBN.
Navigate to eCommerce Gateway Setup > Code Conversions > Define Code
Conversion. Define your UOM and Item Category mappings. While making entries,
define Key1 as (or provide any other name).
2. Log in to your e-Business Suite test environment that is connected to OBN, and
access the iProcurement Catalog Administrator responsibility. Click the Stores tab,
and select the Content Zone sub-tab. Select Create Punchout Content Zone from
the Manage Content Zones dropdown list.
1. Enter a Content Zone Name and Description.
2. Select the source as Exchange.
3. Enter Buyer Company Identification by adding your company's name as

registered on OBN. For example, your company's primary identifier can be D-
U-N-S number.
4. In the Punchout Definition region, provide the following details OBN

Punchout URL.
In the EBS or PeopleSoft or Fusion instance, enter the OBN Punchout URL as
https://osn-prod.oracle.com/punchout/punchoutloginserver in the Punchout
Definition region.
5. User Name and Password: Your company's credentials (user name and
password) used by your company to connect to OBN.
6. In the Punchout Identification region, provide the keywords as required.
7. In the Mapping region, provide Key1 information.

This field is used to set up data mapping in e-Commerce Gateway. In order to
punch out items from catalogs hosted on a supplier site, the following needs to
be completed in e-Commerce gateway.
Data Mapping for UOM and Data Mapping for Item Category.
The field Key1 in the Punchout Content Zone is used to map with e-Commerce
Gateway for which the UOM and Item Category mapping are done. For
example, enter OBN for Key1 in the Content Zone Definition, and use the same
in e-Commerce Gateway. (Navigate to: eCommerce Gateway > Setup > Code
Conversion > Define Code Conversion Values).
8. Enter Content Zone Security as required to control the access to OBN Redirect
Punchout Site.
3. Save the content zone.

4. On the Content Zones tab, click the Download Punchout icon for the content zone
you just created. You should see the list of suppliers whose punchouts you have
accessed from OBN.
5. Create a new store and assign the new content zone to the store.
6. Users now can shop from the nre punchout store in iProcurement which would
redirect to the supplier site via Oracle Business Network.
The buyer access set up steps required for Punchout Redirect are complete.
Punchout Setup for Trading Partners to an Oracle Customer

Your trading partner, requires that you configure the punchout details on a new hosted
service called Oracle Business Network (OBN). Perform the following steps for supplier
configuration on OBN:
1. Register on Oracle Business Network.
2. Setup Punchout Configuration on OBN.
3. Authenticate Connection between OBN and your server.
Register on Oracle Business Network:

1. If your company already has an OBN account, go to the next step.
2. If your company does not have an account, create an OBN account. See Registering
with Oracle Business Network, page 7-1 for more information.
3. If you are not sure whether your company has OBN account, contact your
company's system administrator.
Set up Punchout Configuration on OBN:

1. Navigate to the Messaging tab and add/define the primary identifier. In the
Identifiers region, click Add to add a primary identifier.
Note: OBN recommends that you use the D-U-N-S number as a

primary identifier.
For the identifier type that you select, enter a unique value to identify your
company. This is your company's identifier and is used to identify and associate all
the messages/transactions sent, or to be received by your company. You may also
opt for other Identifier types such as phone number, tax id, network id, and so on.
See Identifiers, page 5-3 for more information.
Punchout 13-7
2. Select the Punchout tab, and then click the Supplier Setup sub-tab. Enter the
information about your Punchout configuration. This is what your customer or
trading partners should use to re-direct their employees to your e-commerce
website from their self-service procurement tool. The configuration details are as
follows:
1. Punchout URL: The URL that your customers or trading partners procurement
tool should use to allow their employees to see your e-commerce website.
2. Password: The password that your customers should use to authenticate

themselves on your server.
3. Communication Protocol: Select the protocol that your server supports (XML /
cXML).
4. User Interface Identification: These fields are used when your customer uses to
look you up, and add your Punchout configuration to their system.
5. Display Name: Enter your company name.
6. Logo URL: Enter the URL for your company logo. This appears next to your
company name, and helps in easy identification of your company in the list.
7. Company Description: Enter details such as the categories / commodities you

offer through your Punchout catalog, or any other useful information about
your company.
Control Availability:
Publish: Select this box if you want your punchout configuration to be published to
your customer.
Test the configuration setup. Click Test Punchout to verify that the punchout
configuration is correct. You get a confirmation message stating that you are
successfully connected to your company's punchout site.This also means that your
trading partners can now start accessing your punchout portal and start shopping.
When the setup steps are completed successfully, inform your trading partner (the
buyer company) that you have done your punchout configuration. Your trading
partner can now access your company's punchout configuration defined in the
above steps from their buyer access subtab on OBN.
3. Authenticate Connection between OBN and Your Server

If your server is using active certificates from any of the supported certifying
agencies, OBN can authenticate the connection with your server. There can be
situations where OBN is unable to authenticate your server's certificates. If this
happens, please click the Contact Us link at the bottom of the page. Provide all the
necessary details that will help the OBN team to add your certificate to the OBN

wallet.
Data Mapping in Oracle Business Network
Overview
Data mapping enables users to define the conversions between Buyer codes and
Supplier codes. For example, a buyer uses the unit of measure (UOM) code EA for Each.
The supplier uses E. Customer can use either OBN or iProcurement (specifically, E-
Commerce Gateway) to map these codes.
Data mapping can be done using the following options:

• OBN looks for Supplier Data Mapping, if any
• OBN looks for Buyer Data Mapping, if any
• Alternatively data mapping can be done in e-Commerce Gateway
Model Mapping Method Mapping Performed
Redirect Punchout – Use OBN to perform data OBN performs the mapping
Punchout from Oracle mapping for codes UOM, before the cart is returned to
iProcurement to Supplier- Currency. You can use e- iProcurement from Supplier
Hosted Catalog via OBN Commerce Gateway as well Site
to perform the data mapping
Create Data Mapping in OBN

The main considerations for buyers and suppliers implementing data mapping include
the following:
• Data mapping is an optional step. Perform the steps detailed later for Punchout to
supplier-hosted catalog using OBN.
• Use this step to map the codes that are used in OBN to the codes you use, if they are
different.
Punchout 13-9
• Data mapping allows OBN to recognize codes that are passed to it by the supplier,
or to send codes to the buying organization that its system recognizes.
• For punchout, the buyer and supplier can use OBN to map the following codes:
• Currency codes
• Unit of Measure (UOM) codes
• If you perform no mapping in OBN, the value is passed as is, from OBN to the
buying organization's system. The buying organization may have set up data
mapping in its system.
It is important to decide on the data mapping type that buyers and suppliers want to
use. Determine which data mapping the buyer and the supplier will need to do.
Setup for OBN Data Mapping

1. Login to Oracle Business Network and navigate to the Punchout tab.
2. From the sub-tab Data Mapping, review any mapping previously created for
Currency and Unit of Measure by selecting the appropriate Mapping Type in the
dropdown. Modify data to map the OBN values to your preferred values to be used
in Punchout Re-Direct. For example, select Unit of Measure as the Mapping Type.
You will see the UOM Description and the OBN standard.
• If you are a trading partner to an Oracle Customer, enter your company
standard UOM against OBN Standard in the My Company to OBN column.
• If you are an Oracle Customer, enter your company standard UOM against
OBN Standard in OBN in the My Company column.
3. Alternatively you can export existing OBN mapping data to a spreadsheet, and it
can be imported back after modification. Click Export Button to export the data into
a spreadsheet and save the file.
4. Modify any required data mapping in the spreadsheet. Click Import, and select the
modified data mapping file.
5. Review the imported data mapping and click Save.

14
Pages and Navigation
Pages and Navigation

This chapter provides the navigation options for using Oracle Business Network.
Use the user name and password that you specified when you registered your company
to access the Home page.
The following table displays the default navigation path for each Oracle Business
Network page used in this guide.
• Text in brackets ([]) indicates a button.
• (I) indicates an icon.
• (T) indicates select a tab.
• (M) indicates select the menu option from the page.
Page Navigator Menu Path
Add User (T) Users > [Add User]
Home > (I) User Management > [Add User]
Add Identifier (T) Messaging > (T) Messaging Setup > [Add]
Add Trading Partner (T) Partners > (T) Add Trading Partners
Add New Delivery Method (T) Messaging > (T) Messaging Setup >
Communication Parameters > [Add]
Pages and Navigation 14-1

Add a New Transaction Type (T) Messaging > (T) Messaging Setup >
Transaction Type > [Add]
Activate/Deactivate User (T) Users > [Activate/Deactivate]
Activity Log page • OBN Production Monitor page > Click the
Control Number link
• OBN Test Monitor page > Click the

Control Number link
Assign Roles (T) Users > [User Roles]
Attachments Send Document page > Manage Attachments

link
Attachment Download (T) Monitor > (I) Download
Buyer Access (T) PunchOut > (T) Buyer Access
Communication Parameters (T) Messaging > (T) Communication

Parameters
Company Profile (T) Profile > (T) Company Profile
Connectivity (T) Self-Testing > (T) Connectivity
Download Sample (T) Self-Testing > (T) Outbound Tests > [Test
Outbound]
Data Mapping (T) Punchout > (T) Data Mapping
iSP Profile (T) Profile > (T) iSP Profile
iSP Wallet (T) Partners > (T) iSP Wallet
Notification Preferences (T) Messaging > (T) Notifications
Oracle Business Network Login http://businessnetwork.oracle.com

Outbound Tests (T) Self-Testing > (T) Outbound Tests
Inbound Tests (T) Self-Testing > (T) Inbound Tests
Monitor (T) Monitor
Pending Approval (T) Partners > (T) Pending Approval
Received Messages (T) Monitor > (T) Received Messages
Resources Any OBN page > Click the Resources link
Registration Oracle Business Network Login page >

Register as a Oracle customer
Oracle Business Network Login page >

Register as a Trading Partner
Routing Rules (T) Partners > (T) Routing Rules
Self-Testing (T) Self-Testing > (T) Self-Testing
Send Document (T) Messaging > (T) Send Document
Sent Messages (T) Monitor > (T) Sent Messages
Supplier Setup (T) PunchOut > (T) Supplier Setup
Terms of Use Registration page > [Continue]
Test Accounts (T) Profile > (T) Test Account
Trading Partner (T) Partners > (T) Your Trading Partners
Trading Partners Requesting Approval (T) Partners > (T) Pending Trading Partners
Transaction Management (T) Messaging > (T) Transaction Management
User Management (T) Users
Your Trading Partners (T) Partners > (T) Your Trading Partners
Pages and Navigation 14-3

OBN Process Guide

Uploaded by

Copyright:

Available Formats

OBN Process Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OBN Process Guide

Uploaded by

Copyright:

Available Formats

Oracle® Business Network

Part No. F29166-03

Copyright © 2021, Oracle and/or its affiliates.

Primary Author: Swathi Mathur, Mark Peachey, Preeti Venugopal

Send Us Your Comments

2 Registering on Oracle Business Network

3 Using Oracle Business Network (OBN)

4 Updating the Profile

6 Trading Partner Management

9 Testing Outbound and Inbound Messages

Oracle Business Network Process Guide , Release 3.0

About this Guide

Access to Oracle Support

Related Information Sources

• Oracle Applications System Administrator's Guide

• Oracle Manufacturing APIs and Open Interfaces Manual

• Oracle Payables User's Guide

• Oracle Purchasing User's Guide

• Oracle Business Network XML Solutions Guide

• Oracle Transport Agent - Installation document

• Oracle XML Gateway User's Guide

• Oracle Purchasing eTechnical Reference Manual, Release R12, available on Oracle My

• Oracle Transport Agent (OTA) is installed and operational on an Oracle

Do Not Use Database Tools to Modify Oracle E-Business Suite Data

1-2 Oracle Business Network Process Guide

• Each business transaction can be transmitted using different delivery modes

• Your OBN account provides visibility to transactions processed in each hub

See: Punchout for Punchout configuration settings.

About Registering Your Company

Note: Throughout this guide, buyer or buying organization refers to an

Registering as an Oracle Customer

Registering on Oracle Business Network 2-1

Entering the Registration Information

3. E-mail Address: Enter the email address.

5. Password, Confirm Password: Enter a password, at least 8 characters in length to

2-2 Oracle Business Network Process Guide

To enter the addresses:

3. Select the Type as Primary.

4. Enter the postal address of the company.

To enter messaging details:

• US Federal Tax Identifier

• Global Location Number

Registering on Oracle Business Network 2-3

Registering as a Trading Partner of an Oracle Customer

2-4 Oracle Business Network Process Guide

Search for Your Company

• Enter the company contact information, address, and messaging details.

When you have selected the company to register, click Continue.

Registering on Oracle Business Network 2-5

Contacting My Oracle Support

Forgot User Name/Password

2-6 Oracle Business Network Process Guide

The Home tab has the following tiles with icons:

• Messaging Setup – to set up the delivery methods

Using Oracle Business Network (OBN) 3-1

• Company Profile – to view and update the company profile information

Every company registered on OBN is assigned a unique identification number called

See Setting Up Messaging , page 5-1 for more information.

3-2 Oracle Business Network Process Guide