“XML Gateway” responsibility: Define Hubs

Use this form to define the hubs via which XML documents will be sent & received. If you are using Exchange for punching out, then your setup will
look like below

<!--[if !supportLineBreakNewLine]--><!--[endif]-->

 
XML Gateway Responsibility: Define Transactions
Here you indicate, the type of Documents you wish to exchange with your suppliers using XML

<!--[if !supportLineBreakNewLine]--><!--[endif]-->

 
XML Gateway Responsibility: Define Trading Partner
In this screen you will create a record for each Supplier with whom you wish to exchange XML Documents electronically.
For example, if you wish to send XML Purchase Orders to “Go 4 Gold Management Ltd”, then you will create an entry similar to below. The
connection can either be direct or via exchange server.

You will also capture trading party’s DUNS numbers in this screen.
During the implementations you usually use testexchange.oracle.com.
The DUNS number for the supplier also needs to be entered in the EDI Location field against supplier site in Vendor Definition Screen.

The DUNS number for your implementation client needs to be entered in the EDI Location field on Other Details section of Location form for Client
location[lets say your client for which iProc is being implemented is “XX Machine Inc”].
Process PO 007 is an OAG standard that dictates the structure of XML document which your supplier will receive.
For those that do not know, PO007 is nothing but an Approved Purchase Order sent to the supplier. Its format is XML.
To see its structure, on your middle tier, review the dtd file as listed below. $PO_TOP/xml/oag71/003_process_po_007.dtd

Oracle Apps uses XML Gateway to generate the PO-007 file.

<!--[if !supportLineBreakNewLine]--> <!--[endif]-->

How is this PO 007 file generated?
FTP the xgm file to you PC from $PO_TOP/patch/115/xml/US/process_po_007.xgm

Open that file in XML Gateway Message designer

You will notice that message designer reads information from views like  ITG_PO_HEADER_ARCH_V 
[Prior to 11.5.10 it was PO_ECX_HEADER_ARCH_V]
iProcurement uses the XML Gateway engine in conjunction with PO-007 message definition to generate
PO007 XML document.

<!--[if !supportLineBreakNewLine]--> <!--[endif]-->

Configure your Exchange setup
Given that in this setup, we will use Oracle’s exchange server to send PO Documents to supplier, hence we need to enable this Document Type[PO
007] in exchange[for the company implementing iProc]

Logon to exchange.oracle.com or the testexchange

Navigate to Application Setup tab/ Transaction Delivery
Select the document type PROCESS_PO_007 and edit
Set the communication method and click Apply

Your Supplier will have to register on Oracle Exchange Server too.

To begin with, during implementation, each  supplier must register themselves on http://testexchange.oracle.com
Your supplier does the below:-
Clicks on Registration on testexchange, and selects the option to register as an affiliate of your client.
Say your client is “XX Machine Inc”, hence your supplier will search & select “XX Machine Inc”. Supplier will be prompted to enter further details.
Following this, your client will have to approve the request for Supplier’s registration.
Supplier Enables PROCESS_PO_007 for themselves on the Exchange
The sequence of flow for PO 007 in this case is…
XX Machine Inc-->PO 007-->Exchange server-->Supplier

Hence Supplier needs to enable “PO 007” for themselves on the exchange server
For this your Supplier does the below steps:-
Login to the testexchange (i.e. exchange.oracle.com  after testing during goLive).
Clicks on Transaction Delivery under Company Administration
Selects Sales Order Outbound (PROCESS_PO_007) [going out  from Exchange, becoming sales order in Suppliers System]
Under transaction type they select delivery method HTTPS etc
They specify their URL on server which where exchange will post the PO 007 XML doc.... https://inboundpo...
They also need to specify other connection details to their server like port number, userid password etc.
Exchange server will use those credentials to connect  and post the XML PO Document[PO 007]
Note: Oracle Exchange supports various protocols like http,https,smtp . The supplier selects a protocol based on the protocols their server supports.

<!--[if !supportLineBreakNewLine]-->Supplier Enables themselves for PunchOut on the Exchange Server

Oracle supports both cXML ad XML punchouts. Hence the supplier must support one of these two options.
Supplier does the following steps to enable punchouts:-
Logs in to TestExchange Server or the Exchange Server
Clicks on “setup punchout”
Enters their punchout URL, userid password for their iStore.
Select XML or cXML and then clicks on APPLY.
Supplier can then test whether their punchout setup works by punching out to their iStore from testexchange/exchange.

”XX Machine Inc” reviews suppliers Punchout

Client “XX Machine Inc” logs into testexchange or exchange server, and navigates to “Control Punchout Access” and accepts Suppliers Punchout
definition.
 

”XX Machine Inc” makes Oracle EBS aware of the Punchout setup
It is possible that with some suppliers, you would like to Punchout to their iStores via exchange, and for the other suppliers you may like to punchout
directly to their iStore.
I am detailing both the scenario’s below.

Scenario 1 Use the Supplier punchout definition from Exchange

Navigate to Internet iProcurement Catalog Administrator.
<!--[if !supportLineBreakNewLine]--><!--[endif]-->

As in picture above, by downloading[click on download], you will bring into Oracle, all the Punchout Suppliers that are enabled for your business in
exchange.

Scenario 2 Create Supplier punchout definition directly in Oracle Apps eCatalog Mgr

<!--[if !supportLineBreakNewLine]--><!--[endif]--> If  you were not to be using Exchange, then you will have to create the Punchout definition from
scratch in Oracle Apps itself.
For this, click on “Manage Content” in responsibility “Internet iProcurement Catalog Administrator”
Click on create catalog

Select Punchout catalog and click on continue

As in picture above, we select Supplier and Direct Punchout.

Given that you are creating Punchout definition of the supplier from scratch straight in Oracle Apps, you then need to enter information in below
fields like Punchout URL, Encoding Method, password etc.
  

NOTE: As you may have noticed, effectively we are trying to create a punchout definition in Oracle Apps…either by downloading the Supplier’s
punchout definition from exchange or by directly creating the Punchout definition in Oracle Apps.

<!--[if !supportLineBreakNewLine]--> <!--[endif]-->Display the punchout site on iProcurement

Homepage
This will be the last step. You need to define a store that is attached to the punchout catalog definition.

For this Click on create store in responsibility “Internet iProcurement Catalog Administrator”

<!--[if !supportLineBreakNewLine]--> <!--[endif]-->

<!--[if !supportLineBreakNewLine]--> <!--[endif]-->
This finishes the punch-out setup with your Supplier.

<!--[if !supportLineBreakNewLine]--> <!--[endif]-->

Further notes:-
1. Your suppliers punchout basket may contain items with UOMs that are not defined in Oracle Apps inventory module. In this case, you must
navigate to responsibility “eCommerce Gateway” and define those mappings using menu “Code Conversion Values”
2. As per the OAG format, the item category used in punchout baskets is 8 digit UNSPSC code. Effectively UNSPSC code is a global code for item
categories. However in Oracle EBS, we implement Item Categories using Key FlexField for Item Categories. For a 3 segment Item category flexfield
in inventory, your item category may look like AA.BB.CC. This value of AA.BB.CC must be mapped with the UNSPSC codes that your suppliers will
be sending for their item categories. This definition is mapped in the same screen under “eCommerce Gateway”.