Академический Документы
Профессиональный Документы
Культура Документы
Disclaimer 1
Introduction 3
Communicating Directly
ly With a Supplier 13
Setting up Communication
nication with Oracle Supplier Network 31
Verifying Communication 51
Setup: Supplier 53
References 54
4. On the General tab, in the B2B Communication section, select the B2B Communication Method:
Collaboration Messaging Framework.
Note: An Trading Partner can be associated with multiple supplier sites. To associate an existing Trading Partner to
a supplier site, skip to step 14 in this section.
9. Add documents that need to be communicated and save changes. For purchase orders add
PROCESS_PO_OUT and for change orders add CHANGE_PO_OUT
CHANGE_PO_OUT.
Note: The status of the document should be set to Active. An Inactive document will not be available for
communication.
13. In the Collaboration Documents section add documents that will enabled for communication.. To do this,
select and add Document: PROCESS_PO_OUT. E Ensure
nsure that field Association Status is set to Enabled.
For change order select document: CHANGE_PO_OUT
CHANGE_PO_OUT.
Note: The status of the message should be set to Active. An Inactive document will not be available for
communication.
13. In the Associated Trading Partnerss section, add row and select Service P
Provider: None .Provide Trading
Partner ID details.
14. In the Collaboration Documents section add the documents that will be communicated. To do this, add and
select document PROCESS_PO_OUT and ensure that field Association Status is set to Enabled. For
change order select document CHANGE_PO_OUT.
9. Provide Service
e Provider Name, Service Provider Partner ID, Service Provider Partner ID Type and
Description.
12. Navigate to Outbound Collaboration Messages tab in Configuration Details section and click Add.
13. Provide message details:
a. Name: This will identify outbound message to be communicated electronically.
b. Select Collaboration Message: OAGIS_10.1_PROCESS_PO_COLLAB_MSG_OUT to enable
purchase order communication, OAGIS_10.1_CHANGE_PO_COLLAB_MSG_OUT to enable
change order communication.
c. Set status to Active.
Note: The status of the message should be set to Active. An Inactive document will not be availabl
available for
communication.
10. In the Associated Collaboration Documents section, add row and select Service Provider:.Test_Outbound
Test_Outbound
Service Provider.
11. Select Trading Partner ID.
12. In the Collaboration Documents for Service Provider section add the documents that will be
communicated. To do this, add and select document PROCESS_PO_OUT and ensure that field
Association Status is set to Enabled. For change order select document CHANGE_
CHANGE_PO_OUT.
The supplier site is now enabled for electronic communication. An information icon next to Communication Method
field in a purchase order indicates that the document will be communicated electronically.
Note: Documents which are undelivered are categorized by the unique pairing of Service Provider and Trading
Partner.. The message administrator can select the document to navigate into the more detailed user interface to
investigate further.
5. To find an undelivered
ed message navigate to Manage Undelivered Collaboration Messages.
6. Filter search by:
a. Document Type: PROCESS_PO_OUT for purchase orders or CHANGE_PO_OUT for change
orders.
b. Select Service Provider: OracleSN for messages communicated to Oracle Supplier Network and
None for messages communicated directly to a supplier
supplier.
c. Provide Trading Partner ID and Partner ID type: These are valu
values that identify a supplier site.
site
7. To reprocess a message:
a. Select message and click Reprocess
Reprocess.
When an undelivered message is selected in the search results region, details of the processing history are also
shown. Each undelivered message is also viewable, and can be opened in a separate page to show all of the
message details.
Administrators also have the ability to review the complete history of all messages, not just the undelivered ones.
The task Manage Collaboration Messaging History gives the administrator the ability to search for messages with
wi a
broader set of status values,
5. Verify that a unique identifier for B2B communication (B2B Supplier Site Code) exists
exists:
a. Click Administration. Then go to Types tab.
b. Verify that the
e identifier B2B Supplier Site Code exists
exists.
c. If the above does not exist, create the new identifier B2B Supplier Site Code
Code.
2
Cloud customers must log an SR with Cloud ops team to perform the required keystore setup. Support will to
request an OWC with Cloud Ops and the customer.
Once the customer has logged into B2B Console, Cloud Ops will take control to enter the keystore path and
password.
7. Verify the host <Company> supports the B2B documents: PROCESS_PO_007 and CHANGE_PO_006
a. In the Partner panel, select the <Company> and go to Documents tab.
b. Add two channels: one for purchase orders, and another for change orders (steps below to be
repeated for each channel):
Note: You should already have both parties (company and trading partner) registered on the Oracle Supplier
Network (OSN). Details for setting up OSN
SN are listed under references.
USERNAME=
USERNAME=<OSN Username>#PASSWORD=<OSN
Password >#DOC_FORMAT=OAG
Password>#DOC_TYPE=<DOC_TYPE>#DOC_FORMAT=OAG
#FORMAT_VERSION=<
#FORMAT_VERSION=<FORMAT_VERSION>#DOC_REF=001
>#DOC_REF=001
#RECEIVER_ID=<
#RECEIVER_ID=<RECEIVER
>#RECEIVER_ID_TYPE=DUNS#SENDER_ID=<SENDER
ID>#RECEIVER_ID_TYPE=DUNS#SENDER_ID= SENDER ID
>#SENDER_ID_TYPE=DUNS
#SENDER_ID_TYPE=DUNS
A description for each of the required input is provided in the table below.
Some of these sho
should
uld be provided by the supplier (Replace the tags with
business specific values).
PASSWORD Your Oracle Supplier Network account password. <OSN Password> <OSN Password>
Document Type name. See valid Oracle Supplier
DOC_TYPE
Network doc types below. PROCESS_PO_007 CHANGE_PO_006
Format version of the document. See valid Oracle
FORMAT_VERSION
Supplier Network format versions below 007 006
Receiving trading partners identifier value, as
RECEIVER_ID registered by the receiver on Oracle Supplier
Network. Should be provided by supplier <Receiver ID> <Receiver ID>
Senders identifier (DUNS, Phone Number etc.), as
SENDER_ID
registered on Oracle Supplier Network. <Sender ID > <Sender ID>
Figure 39: List of parameters required for defining additional transportation header.
Note: For details, refer to Oracle Supplier Network: XML Solutions Guide .
Figure 41: Create agreements with trading partner to start electronic communication.
4. Under General Tab, select Oracle B2B Gateway as B2B Communication Method.
5. Provide B2B Supplier Site Code. This should match the value specified in step 3 of B2B console setup.
setup
7. Verify that all documents that have been configured for the trading partner are available.
5. Verify that a unique identifier for B2B communication (B2B Supplier Site Code) exists
exists:
a. Navigate to Administration > Types.
b. Verify that the ident
identifier B2B Supplier Site Code exists.
c. If the above does not exist, create the new identifier B2B Supplier Site Code
Code.
3
Cloud customers must log an SR with Cloud ops team to perform the required keystore setup. Support will to
request an OWC with Cloud Ops and the customer.
Once the customer has logged into B2B Console, Cloud Ops will take control to ente
enterr the keystore path and
password.
7. Verify the host <Company> supports the B2B documents: PROCESS_PO_007 and CHANGE_P
CHANGE_PO_006
O_006:
a. Navigate to Partners> <Company> > Documents.
b. Add two channels: one forr purchase orders, and another for change orders (steps below to be
repeated for each channel):
c. Password: Provide password that identifies the buying organization in suppliers server.
serve
Verifying Communication
An order for a supplier site that has been configured for B2B communication can be verified through the B2B
console
onsole or the Oracle Supplier Network console
console.
4. In case of errors, a notification is sent to the sender (Buyer named on the PO, in case of purchasing) and
the message
age will be in state: MSG_ERROR
MSG_ERROR.
3. Under OSN Monitor, select Received Messages and search for documents.
Setup: Supplier4
The following setup must be performed by the supplier in Oracle Supplier Network to receive messages in cXML:
1. Login to Oracle Supplier Network as supplier
supplier.
2. Navigate to Messaging > Transaction Management
Management.
3. Add transaction type:
a. Transaction Type: Purchase Order
b. Document Format: cXML
c. Document Type: OrderRequest
d. Action: Receive
e. OSN Test: HTTPS
f. OSN Production: HTTPS
g. Format Version: 1.2.007.
4. And transaction type:
a. Transaction Type: Change Order
b. Document Format: cXML
c. Document Type: OrderRequest
d. Action: Receive
4 This setup indicates additional setup required for cXML communication. For complete OSN setup refer to the OSN guide here.
References
CONNECT W ITH US
blogs.oracle.com/oracle
2017, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
Copyright 201
contents hereof are subject to change without notice. This document is not warranted to be error-free,
error nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations
ob are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any a
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license
licens 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. 0116