Posts

Posts

  • Saravanan Thirunavukkarasu
    R12: Vendor are not receiving PO's2
    Topic posted September 1, 2017 by Saravanan ThirunavukkarasuGold Medal: 3,500+ Points, tagged BI Publisher Reports, Notifications, Orders, Requisition Processing, Supplier Communication in Procurement > Purchasing public
    Title:
    R12: Vendor are not receiving PO's
    Summary:
    553-SPF (Sender Policy Framework) domain authentication
    Content:

    Hi Team,

    Is it possible to change the from email address for the PO's sent to vendors... Vendors are not receiving PO's ...

     

    One of the failure notifications we received contained this…

     

    “The original message was received at Wed, 30 Aug 2017 13:22:13 GMT from cffar77100h17.usdc2.oraclecloud.com [10.46.216.114]

     

       ----- The following addresses had permanent fatal errors ----- <emailadress>

        (reason: 553-SPF (Sender Policy Framework) domain authentication)

     

       ----- Transcript of session follows ----- ... while talking to cluster4.eu.messagelabs.com.:

    >>> DATA

    <<< 553-SPF (Sender Policy Framework) domain authentication <<< 553-fail. Refer to the Troubleshooting page at <<< 553-http://www.symanteccloud.com/troubleshooting for more <<< 553 information. (#5.7.1)

    554 5.0.0 Service unavailable”

  • Jim Van Tongerloo
    B2B PO CommunicationAnswered9
    Topic posted August 3, 2017 by Jim Van TongerlooGold Trophy: 10,000+ Points, tagged How-To, Orders, Setup, Supplier Communication in Procurement > Purchasing public
    Title:
    B2B PO Communication
    Summary:
    Can not configure B2B PO communication
    Content:

    Hi,

    I've been trying to get my approved PO's sent out through B2B communication and I've done all the setup as mentioned on this DOC ID: https://support.oracle.com/epmos/faces/DocumentDisplay?id=1995064.1

    However, they only talk about integration with OSN. I want to simply send the file by e-mail or store it as a file on a location. But those setups are not covered. For example for email protocol, it asks me my email id and host name, I have no idea what to fill in. For File protocol it simply asks for a folder.

    But for both protocols I'm getting the same error:

    Transport error: [MsgCannotBeSent] SMTP message cannot be sent.

    Anyone who has experience with this? I've searched forums and communities but haven't found anything. My next step will be an SR.

    Thanks

    ~Jim

  • Manjula Evans
    Collaborative Messaging Framework4.0
    Topic posted September 17, 2016 by Manjula EvansBronze Medal: 1,250+ Points, tagged Agreements, Orders, Setup, Supplier Communication in Procurement > Purchasing public
    Title:
    Collaborative Messaging Framework
    Summary:
    Use the Collaborative Messaging Framework to manage inbound and outbound messages
    Content:

    Collaboration Messaging Framework (CMK) is a new product in Fusion Applications available from Release 11 that facilitates straightforward B2B communication implementation. It eliminates the need to navigate to Oracle B2B and set up documents, protocols and channels for every supplier site individually. All of this is now achieved inside Fusion applications. CMK provides out of the box integration with Oracle Supplier Network and adds support for the current industry standard OAGIS message version 10.1 in addition to the existing OAGIS Version 7.2.1.

    For more details, refer to the Release Updates in Customer Connect to access all of the Release 11 collateral available for Fusion Procurement.

  • Manjula Evans
    Sender E-mail Address for Purchasing Document Communication4.7
    Topic posted September 17, 2016 by Manjula EvansBronze Medal: 1,250+ Points, tagged Agreements, Orders, Setup, Supplier Communication in Procurement > Purchasing public
    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.