For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
As of release 19B, you can exchange user-defined cXML messages with your trading partners via Oracle Supplier Network. You can use this capability to customize your messages to meet your partners' requirements. To send a user-defined cXML message, you need to define a cXML message with custom mapping, create a custom service provider pointing to OSN, and use this service provider and message when setting up trading partners on your supplier sites.
You can now set up Collaborative Messaging Framework to exchange messages with your suppliers through Oracle Supplier Network (OSN) using a web service. Routing messages using a web service simplifies message exchange between Fusion Applications and OSN. Messages will no longer be routed through Oracle B2B and you will not need to do any setup in Oracle B2B. This guide covers the configuration you need to perform in Fusion Applications and OSN to support message exchange using a web service.
Fusion Applications setup (needed for outbound messages)
Oracle Supplier Network setup (needed for inbound messages)
The buyer creates a Purchase Order with an item. The item has a few attachments in the master item page. Once the purchase order is approved, the purchasing documents will get communicated to the supplier via e-mail or electronically. You can automatically include item attachments on the supplier e-mail communication.
1. Login as a buyer. Once logged in, go to Setup and Maintenance -> Manage Attachment Categories task. Search the Category name TO_SUPPLIER. Add ITEM_ENTITY to the attachment.
2. Alternatively, you can go to Setup and Maintenance -> Manage Attachment Entities task. Search for the entity name ITEM_ENTITY. Add TO_SUPPLIER to the attachment categories.
3. Navigate to Setup and Maintenance -> Manage Item Classes task. Edit the Root Item Class.
4. Scroll to the bottom of the basic tab and add 'To Supplier' to this list of Attachment Categories. Save and Close.
5. The list of attachment categories on the Edit Item page should now include 'To Supplier'.
Item attachments of category 'To Supplier' will be now added to purchasing documents communicated to suppliers via e-mail or electronically (B2B).
Customers can upload attachments to their purchasing documents and communicate those attachments to internal approvers and suppliers. Here are the answers to some commonly asked questions.
1. How many attachments can be uploaded to a purchasing document, and how big can they be?
There are no limits on how many files can be uploaded to the document. The maximum size of an uploaded file is 2 GB. This value is controlled by the FND_FILE_UPLOAD_MAX_SIZE profile option on the Manage Administrator Profile Values page. The limit on the total size of uploaded files is determined by the space purchased for the Content Server.
When communicating attachments electronically or over email, there are additional limitations detailed in the answers below.
2. Are there any restrictions on what files can be uploaded?
There are no restrictions on file type.
3. What is the maximum attachment size limit for emails?
The maximum email size (content + attachments) that can be sent by the mail server is 15MB. Any emails exceeding these settings will not be sent. On top of this setting, approval email and supplier communication email sizes are controlled by the additional settings below.
4. What happens when the size limit is exceeded in an approval notification email?
Approval notification emails also respect the MaxSizeOfEmailAttachmentsInKB and MaxNumberOfEmailAttachments properties on the SOA server. The MaxSizeOfEmailAttachmentsInKB property controls the maximum email size and needs to be smaller or equal to the http.maxmessagesize. The default value is 5MB. The MaxNumberOfEmailAttachments property controls the number of attachments in an email and the default value is 10.
Any attachments after 10 attachments or 5MB of total attachments will be attached as a link instead of a file in the notification. This behavior attempts to keep the email size below the maximum size so that the email can be sent. Attachments attached as links will not be visible in the email, but approvers will be able to view the attachment links in the online approval notification.
5. What happens when the size limit is exceeded in a supplier communication email?
Supplier communication emails will also respect the Maximum File Size Megabytes setting on the Configure Procurement Business Function page. The recommended setting is 5MB.
If the total attachment size exceeds this setting, the email will be sent with only the PDF so that the email size is below maximum size. Additionally, a notification will be sent to the buyer indicating that not all attachments were sent to the supplier.
6. Can attachments be sent as separate files in a supplier communication email?
By default, attachments will be sent as a single Zip file in the supplier communication email. Customers who want to send the attachments as separate files can enable the feature Send Purchasing Document Attachments as Separate Files on the Edit Features: Purchasing page. The same size limitations apply to the total size of the separate files.
7. Can attachments be included in electronic communication?
Attachments can be included in the bodies of OAGIS 10.1 purchase order outbound collaboration messages. To enable attachments in electronic communication, set the profile option Include Attachments in Electronic Communication to Yes. The maximum attachment size can be set on the Manage Collaboration Messaging Configuration page, and the default setting is 2MB.
Present Behavior:
When setting up a supplier site in Oracle Procurement Cloud, you have three options for the B2B communication method you want to use to exchange B2B messages with the supplier:
The Oracle B2B Gateway - Deprecated and Collaboration Messaging Framework achieve the same end result, but have different setup and management capabilities. Oracle Collaboration Messaging Framework Cloud provides better capabilities to set up and manage B2B messaging with trading partners, including features such as message configuration and the ability to reprocess messages.
Future Behavior:
Starting in Update 20A, the Oracle B2B Gateway – Deprecated option will be desupported, and it will be removed as an option in a later release.
Effect on Customers:
New Oracle Procurement Cloud implementations must not use the Oracle B2B Gateway - Deprecated option. If you are an existing customers using this B2B communication method, you must migrate your setup to use Collaboration Messaging Framework for all supplier sites enabled for B2B messaging. Refer to the Oracle Supply Chain Collaboration and Visibility Cloud What’s New for Release 19B and the Migrate Oracle B2B Trading Partner Setup to Collaboration Messaging Framework white paper (Doc ID 2564389.1) for details about the migration process.
Hi all,
When we are releasing the work order our requisitions are auto approving and POs are getting created automatically. As per the Oracle, we can't control the approvals of PR so we want to enable the approval flow for the purchase orders(OSP orders). If anyone has any idea on how to create a BPM rule for these kinds of POs please let me know.
We are implementing Oracle Cloud ERP. We need to communicate with our vendors via EDI. I have been told that Cloud ERP has standard electronic communication capabilities with vendors via the Oracle Supplier Network. If we are pure Oracle Cloud ERP environment that seeks to communicate via EDI with non-Oracle vendors, does the Oracle Supplier Network (OSN) support EDI for Cloud Procurement, does an EDI Gateway solution exist for Cloud ERP or does Cloud ERP require an EDI third party integration partner (such as Transcepta).
I was curious to know the end to end solution for Procurement card. I saw a document (Doc ID 1929497.1) on support where it mentions that we can configure the corporate card as Procurement card. Once configured. can this P Card be selected in Req ? Will this P Card info be passed to PO and then to AP? Is the P-Card details only for information purpose or does it drive the payments or any other functionality? Can the P-Card details sent to supplier through the PO Communication?
Also wanted to know the P-Card functionality on how it is integrated with Expenses and AP
You can use the new profile option " Purchase Order E-mail Sender " to select between the Buyer's e-mail address or an automatically generated e-mail address as the sender address for purchasing document communication e-mails.
Using the buyer's e-mail address allows suppliers to reply and communicate directly with the buyer.
Using the automatically generated e-mail address helps in cases where the supplier's e-mail system filters out buyers' e-mails as spam, or if the buyer's role is not clearly defined in your organization.
Hi all,
Terminated users are getting removed on requisition even though the user is PO requester and the user is on the inactive state.
Report Subject Area: Procurement - Purchasing Real Time.
Thanks,
Dev Thota.