Purchasing

Get Involved. Join the Conversation.

Posts

  • Boyuan Zhu
    How to Exchange User-Defined cXML Messages via Oracle...5.0
    Topic posted July 29, 2019 by Boyuan ZhuGold Medal: 3,500+ Points, tagged How-To, Orders, Supplier Communication 
    Title:
    How to Exchange User-Defined cXML Messages via Oracle Supplier Network
    Content:

    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.

    1. First, define a new message by going to Manage Collaboration Message Definitions in the Collaboration Messaging Workarea. For the message you want to customize, download the existing transformation file by taking the Export Transformation Package action. You can then customize the transform file as you wish. 
    2. Duplicate the existing cXML message and upload your customized transform file. This is now the message you will be using in the future steps. 
    3. Create a service provider in the Manage Collaboration Service Providers task. If you have different customizations for different trading partners, you will need to create a separate message and service provider for each case.
    4. For the service provider, add a Delivery Method, using the delivery method type as “Web Service”. In the Service Name field, select the Service Name as CollaborationMessageV2.Process. Specify the following: 
      • Endpoint: https://osn.oracle.com/HTTPService/ProcessSOAPCollaborationMessage or https://osn-prod.oracle.com/HTTPService/ProcessSOAPCollaborationMessage.
      • User Name: The Oracle Supplier Network buyer account user name
      • Password: The Oracle Supplier Network buyer account password 
      ​​
    5. Add the message from earlier and use the delivery method you created. Set the status as Active and save. 
    6. Make sure that the correct documents are set up on OSN and that your supplier site is using the new service provider and message. The Collaboration Messaging Framework will transform your message into cXML using your defined mapping before invoking OSN.
    Document:
    Document:
    Document:
    Document:
  • Boyuan Zhu
    How to Exchange Messages through Oracle Supplier Network...35.0
    Topic posted July 29, 2019 by Boyuan ZhuGold Medal: 3,500+ Points, tagged How-To, Orders, Supplier Communication, Web Services 
    Title:
    How to Exchange Messages through Oracle Supplier Network Using a Web Service
    Content:

    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)

    1. In the Manage Collaboration Service Provider task, select the OracleSN or OracleSNTest service provider. 
    2. If you are updating your test pod: 
      1. Select the ORA_B2BMessageTestService delivery method.
      2. Set the endpoint to https://osn.oracle.com/HTTPService/ProcessSOAPCollaborationMessage
      3. User Name: The buyer account user name that was used for the HTTP connection
      4. Password: The buyer account password that was used for the HTTP connection
    3. If you are updating your production pod, follow the same steps in 2, but set the endpoint to https://osn-prod.oracle.com/HTTPService/ProcessSOAPCollaborationMessage
    4. In the Outbound Collaboration Messages tab, change the status of all messages to “Inactive”, then update the Delivery Method from ORA_OracleSNOneWayHTTP to ORA_B2BMessageTestService. Note that this step is not applicable for new customers. 
    5. Change the status of all outbound messages to Active (applicable for all customers).


    Oracle Supplier Network setup (needed for inbound messages)

    1. Login as the buyer to OSN and select Messaging Setup. 
    2. Under Communication Parameters, add a new SOAP Service delivery method 
    3. Specify the endpoint URL for the service that Oracle Supplier Network will invoke to send messages to the Collaboration Messaging Framework. The URL is https://<host>/soa-infra/services/default/CmkCollaborationMessagingInboundServiceComposite/CollaborationMessageServiceV2. Replace <host> with the appropriate values from your test and production pod.
    4. Specify a user name and password for your test and production pods. Note that the user specified here must be a valid Fusion user and must have the Invoke Collaboration Message Inbound Service privilege (CMK_INVOKE_INBOUND_COLLAB_DOC_SERVICE_PRIV) in the respective pod.
    5. Once you have specified the appropriate values, select Submit. The dialog is closed and the Communication Parameters table now shows the newly added delivery method.
    6. In the Transaction Management table, edit the Transactions with “Receive” action – these are the ones that OSN is going to send to Fusion Applications. If you are a new customer setting up OSN for the first time, this table will not have any records. Update the delivery method to the new method you created. 

     

    Document:
    Document:
    Document:
    EditOSN.png (127KB)
  • Swati Gupta
    How to include item attachments on purchasing documents...5.0
    Topic posted August 30, 2019 by Swati GuptaRed Ribbon: 250+ Points, tagged How-To, Orders, Supplier Communication 
    Title:
    How to include item attachments on purchasing documents communicated to suppliers
    Content:

    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).

    Document:
    Document:
    Document:
    Video:
    item_1.png (54KB)
  • Boyuan Zhu
    Purchasing Attachments FAQ74.8
    Topic posted April 21, 2018 by Boyuan ZhuGold Medal: 3,500+ Points, tagged Approvals/Notification, FAQ, Orders, Supplier Communication 
    Title:
    Purchasing Attachments FAQ
    Content:

    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.

  • Ivan Pena
    Desupport Notice for Oracle B2B Gateway in Procure-to-Pay...25.0
    Topic posted August 9, 2019 by Ivan PenaBronze Crown: 15,000+ Points, tagged Agreements, Orders, Payables, Supplier Communication 
    Title:
    Desupport Notice for Oracle B2B Gateway in Procure-to-Pay B2B Communications in Update 20A
    Summary:
    B2B Gateway desupported as communication method for Procure to Pay Flow in Update 20A
    Content:

    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:

    • None
    • Oracle B2B Gateway - Deprecated
    • Collaboration Messaging Framework

    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.

  • Dev Thota
    How to write approval rules for “Outside Processing P...25.0
    Topic posted July 30, 2019 by Dev ThotaGold Trophy: 10,000+ Points, tagged Agreements, Approvals, Approvals/Notification, Approved Supplier List, BI Publisher Reports, Business Intelligence, Create Requisition, FAQ, Financials, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, OTBI, Payables, Public Sector, Requisition Processing, Security, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Web Services, White Paper 
    Title:
    How to write approval rules for “Outside Processing Purchase Order” through BPM?
    Summary:
    How to write approval rules for “Outside Processing Purchase Order” through BPM?
    Content:

    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.

    Version:
    19B
  • Girish Papaiah
    P Card Functionality45.0
    Topic posted January 14, 2019 by Girish PapaiahRed Ribbon: 250+ Points, tagged Financials, Fusion, Orders, Payables, Requisition Processing, Supplier Communication 
    Title:
    P Card Functionality
    Summary:
    What is the current Procurement Card functionality
    Content:

    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

    Version:
    18C
  • Manjula Evans
    Sender E-mail Address for Purchasing Document Communication4.7
    Topic posted September 17, 2016 by Manjula EvansBlue Ribbon: 750+ Points, tagged Agreements, Orders, Setup, Supplier Communication 
    Title:
    Sender E-mail Address for Purchasing Document Communication
    Summary:
    Flexibility to define the e-mail sender for purchasing document e-mails sent to suppliers
    Content:

    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.

  • Dev Thota
    Terminated users are getting removed on requisition even...25.0
    Topic posted September 25, 2019 by Dev ThotaGold Trophy: 10,000+ Points, tagged Agreements, Approvals, Approvals/Notification, Approved Supplier List, BI Publisher Reports, Business Intelligence, Create Requisition, FAQ, Financials, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, OTBI, Payables, Public Sector, Requisition Processing, Security, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Tip, Web Services 
    Title:
    Terminated users are getting removed on requisition even though the user is PO requester and the user is on inactive state
    Summary:
    Terminated users are getting removed on requisition even though the user is PO requester and the user is on inactive state
    Content:

    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.

    Version:
    19C
  • Raju Ch
    Fusion P2P – Oracle Fusion Procure to Pay (P2P) L...5.0
    Topic posted July 22, 2019 by Raju ChGreen Ribbon: 100+ Points, tagged Approvals, Approvals/Notification, BI Publisher Reports, Create Requisition, Financials, Fusion, General Ledger, How-To, Manage Procurement Catalog, Notifications, Orders, OTBI, Payables, Requisition Processing, Setup, Supplier Communication, Supply & Distribution Planning Cloud, Tip, White Paper 
    Title:
    Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow
    Content:
    The P2P cycle comprises of the following steps,
    01. Create Requisitions
    02. Approve Requisitions
    03. Create Purchase Orders
    04. Approve Purchase Orders
    05. Receive Goods
    06. Create Payables invoice with Match PO Lines
    07. Approve Invoice
    08. Invoice Payment to Supplier with Electronic Method
    09. Approve Payments
    10. Verify the Transaction Life Cycle
    11. Transfer Payables data to General Ledger
    12. Transfer Payments data to General Ledger
    13. Verify the Journal Batches
    14. Verify the Notifications in Mail
     

    Please click on the below link for more details:

    Fusion P2P – Oracle Fusion Procure to Pay (P2P) Life Cycle with Functional and Technical flow
    https://oracleapps88.blogspot.com/2019/07/fusion-p2p-oracle-fusion-procure-to-pay.html

     

    Thanks,
    Raju Chinthapatla
    http://OracleApps88.Blogspot.com/
    OracleApps88@Yahoo.com
    (+91) 905 957 4321

    Version:
    R12
    Image: