Supplier Management

Get Involved. Join the Conversation.


  • Shivani Roy
    How to use REST APIs for supplier payment attributes5.0
    Topic posted November 29, 2019 by Shivani RoyBronze Medal: 1,250+ Points, tagged How-To, Supplier Profile Management, Tip, Web Services 
    How to use REST APIs for supplier payment attributes
    How to retrieve and update payment attributes of suppliers, their addresses or sites using REST

    Suppliers can be created and updated using the suppliers REST API.

    To get or update the payment attributes of suppliers, their addresses or sites, you need to use the external payees REST APIs.

    • Path: Format to be used for the request path:


    • Content Type:application/json

               The content type of request and response is in the json format

    • Parameters

               Following table explains each of the parameters which can be used as part of the REST API call which are relevant to suppliers payment attributes.

               Sample payload is provided as part of this post.                                                                                                                                                                                                                                           

     Body Parameters

    Data Type




    Corresponds to the SupplierPartyId retrieved using Suppliers GET operation.

    Required to retrieve PayeeId corresponding to supplier payment attributes.



    Corresponds to the SupplierPartySiteID retrieved using Supplier Address GET operation.

    Required to retrieve PayeeId corresponding to supplier addresses payment attributes.



    Identifier of a supplier site. Corresponds to SiteId retrieved using Supplier Site GET operation.

    Required to retrieve PayeeId corresponding to supplier sites payment attributes.



    Application-generated identifier of the external payee. Can be retrieved using the External Payee GET operation. Useful for PATCH operation.

    Required to PATCH payment attributes.




    Code/Name of the delivery channel for an external payee.



    Application-generated party number in Procurement.



    Code of a supplier site.



    Priority with which the financial institution or payment system settles payments for an external payee.





    First, second and third text payment message to an external payee.




    Code/Name of the service level for an external payee.



    Indicates whether documents payable for an external payee are prevented from being grouped with other like documents payable for payment.




    Code of an external payee who is responsible for paying regular or express bank charges, such as Payee or Payer. Values are from the IBY_BANK_CHARGE_BEARER lookup.

    Name of an external payee who is responsible for paying regular or express bank charges, such as Payee or Payer.




    Code/Name of the reason for paying an external payee.



    Text field available for entering information about an external payee payment.





    Delivery method that is set on the external payee level. If the Override with Payee Delivery Method Preference option on the payment process profile is turned off, the setting is ignored. Values from the IBY_DELIVERY_METHODS lookup include EMAIL, FAX, and PRINTED.



    Email address at which an external payee receives remittance advice.



    Fax number at which an external payee receives remittance advice.




    Code/Name of the default payment method for an external payee.

    Step 1: Retrieve PayeeId for supplier, address or site level payment records

    PayeeId: This is a unique identifier for the set of payment attributes. It is auto generated individually when a supplier, address or site record is created. You need to use this value to identify a payment record to be updated. PayeeId can be retrieved using the external payee GET operation as shown below. 

    Note:    First you need to run the supplier GET operation to get SupplierId and SupplierPartyId.

    SupplierId will be used to retrieve supplier site and supplier address PayeeId.

    SupplierPartyId will be used to get PayeeId for Supplier payment record.

                 https://<hostname>:<port>/fscmRestApi/resources/latest/suppliers?q=Supplier LIKE <Supplier Name>

    • GET PayeeId for Supplier:

               Run the external payee GET operation to get the PayeeId for a supplier payment record


    • GET PayeeId for Supplier Address:

               Run the supplier address GET operation to get SupplierAddressId


              Run the external payee GET operation to get the PayeeId for a supplier address payment record



    • GET PayeeId for supplier site:

               Run the supplier site GET operation to get SupplierSiteId


               Run the external payee GET operation to get the PayeeId for a supplier site payment record



    Step 2: Update the payment record corresponding to the supplier, address or site using the PATCH operation

    PATCH operation URL: https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees/<PayeeId>

    Sample PATCH Payload

    "PaymentReasonName": "143",
    "PaymentReasonCode": "BE_143",
    "SettlementPriority": "NORMAL",
    "DeliveryChannelCode": "CH_DTACHECK",
    "BankInstructionCodeOne": "NL_N",
    "BankInstructionCodeTwo": "NL_2",
    "ServiceLevelCode": "SDVA",
    "BankChargeBearerCode": "SHA"
    "DeliveryMethod": "EMAIL",

    Points to consider: 

    1.    Important to identify the attributes used in these payloads. As already detailed above:

    • PayeePartyIdentifier represents a supplier
    • PayeePartySiteIdentifier represents a supplier address.
    • SupplierSiteIdentifier represents a supplier site.
    • PayeeID represents a record that has payment information for a supplier, a supplier address or a supplier site.

    2.    As detailed above, a payee row is automatically created for suppliers, supplier addresses or supplier sites, whenever they are created. This implies that you can directly use PATCH operation to update payment attributes for suppliers, their addresses or sites.

    3.    If a user’s access to patch supplier site payment attributes is denied, you need to review the procurement BU access and maintain supplier site privilege for that user.


    Suppliers REST document: Suppliers REST API
    External Payees REST document: External Payees REST API
    External Payee functional and data security document: Doc ID 2540702.1


  • Kelly Cooper
    SCM – Supplier Onboarding: Deep Dive and Best Practices, 2...6
    Topic posted November 14, 2019 by Kelly CooperGold Trophy: 10,000+ Points, tagged FAQ, How-To, Setup, Supplier Communication, Supplier Creation, Supplier Merge, Supplier Registration, Tip 
    SCM – Supplier Onboarding: Deep Dive and Best Practices, 21 November 2019, 9 a.m. PT - Submit Questions

    Submit your questions for the SCM – Supplier Onboarding: Deep Dive and Best Practices session to have them answered during the live event. Post your questions by posting a new comment to this topic.

    Please submit your questions by Wednesday, 20 November 2019.

  • John Binder
    RightFax Fax Integration and Oracle Fusion Cloud1
    Topic posted November 8, 2019 by John Binder, tagged How-To, Supplier Communication, Tip 
    RightFax Fax Integration and Oracle Fusion Cloud
    Looking to see what other customers are using for Fax Capabilities with Oracle Cloud

    Hello Everyone,

    I was doing some research to determine what Oracle supports in terms of Faxing Software.  Our organization is utilizing RightFax and we trying to migrate our Enterprise over to using strictly RightFax.  I noticed that Oracle doesn't support Rightfax and only uses CUPS for Printing and Faxing capabilities.  I wanted to reach out to the community to see if anyone was using software other than CUPS or even RightFax and what the experience has been.  For us our Supply Chain team has a requirement to be able to Fax some suppliers that still require Fax. 

    Thank you,

    John Binder

    Hopefully I chose the right place to put this question. New to the community and still learning.

    Oracle Doc for reference:


    Oracle Cloud 19D
  • Lot
    Broad-Based Black Economic Empowerment (B-BBEE)15.0
    Topic posted November 7, 2019 by Lot, tagged FAQ, How-To, Supplier Registration, Tip, White Paper 
    Broad-Based Black Economic Empowerment (B-BBEE)
    Documentation on how to configure Broad-Based Black Economic Empowerment (B-BBEE)


    Is there a documentation available on how to configure Broad-Based Black Economic Empowerment (B-BBEE)  for South Africa and what Oracle Cloud version is this available?

    Topics Requested:
    -Documentation on how to configure B-BBEE 
    -How to enable  (PPPFA) Scores Report, BBBEE Rating etc)
    -What Oracle CLoud version is this available ?



    Oracle Cloud R13 19C
  • Shivani Roy
    How to configure Supplier Registration Approved Email...25.0
    Topic posted October 30, 2019 by Shivani RoyBronze Medal: 1,250+ Points, tagged Approvals/Notifications, Business Intelligence, Customization, Supplier Registration, Tip 
    How to configure Supplier Registration Approved Email notification using Business Intelligence Publisher template
    Steps to configure Supplier Registration Approved Email notification using Business Intelligence Publisher template.

    Summary: Steps to configure Supplier Registration Approved Email notification using Business Intelligence Publisher template.


    Buying organizations can include additional information to be sent to the supplier by configuring the email notifications using BIP.

    E.g: In the Supplier Registration Approved Email notification, if you want to add a paragraph detailing the organizations quality policies and also want to display additional information dependent upon a supplier registration attribute, then follow the below steps:


    1. In order to configure the BIP template the user should have the role: BI Administrator.
    2. This feature is opt in controlled. You need to enable feature Configure Supplier Registration Approval Decision Notifications with Business Intelligence Publisher.

    Step 1: Create a copy of the template

    Sign in to Oracle Business Intelligence Publisher. In the Suppliers Business Intelligence Catalog, locate the External Supplier Registration Approved FYI Email Report template, and then click Customize. This creates a copy of the template in your Custom folder.



    Step 2: Download and install BI publisher word add-in

    If BI publisher add-in is not installed for word you can download it from the below link:


    Step 3: Download sample data

    Sample data will be required in order to add additional supplier registration attributes to the template. Sample data contains a list of supplier registration attributes along with sample values for these attributes. This when loaded to the template gives you a list of the supplier registration attributes which can be added to the template. Furthermore the sample data is also useful when you want to preview a report for the configuration done.

    To download the sample data follow the below steps:

    Edit the External Supplier Registration Approved Email Data Model available under the Data Models folder.


    Click on the properties from the panel on the left hand side. Download and save the sample.xml


    Note: If the sample data does not contain the required attributes, you can edit the sample.xml file using notepad and manually add the required tag and value combination under the correct mapping set.

    To fetch the correct Tag Name and mapping set, open the data model, Click on the Data Sets from the panel on the left hand side and go to Structure tab. XML Tag Names and their mapping sets are listed here.




    Step 4:  Customizing the copy of the seeded template.

    1. Go to Custom folder> Procurement> Suppliers > External Supplier Registration Approved FYI Email Report template. Click on Edit and download the ExtSuppRegNotifApprovalFYIReport.rtf.
    2. Go to BI publisher tab and load sample.xml saved in Step 3.
    3. Adding text content: Go to the Insert tab, expand ‘Quick Parts’ to see available pre-existing layouts which can be used to configure the template.
      To add text choose BIP Paragraph of Text from the list.
      Add text which is to be displayed in the email.
    4. Adding an attribute from the data model to conditionally display content on the BIP report:
      We can also add conditions on any of the supplier attribute to conditionally display content. Example given below shows how to use DFF attribute to conditionally display content on the email. DFF attribute ATTRIBUTE20 is used in the supplier registration to capture the supplier response to the question on the buying organization’s quality policies.
    • To add a condition click on Conditional Region under BI publisher tab.
    • Under General: Select the required attribute from the Data field list. Select the corresponding data type.
    • Under Condition1: Manually enter the value expected to satisfy the condition.
    • Add the required content to be displayed inside the conditional tags <C><EC> as shown below.


    Step 5:   Viewing a sample report for the customization.

    Note: Temporarily delete the portion highlighted in yellow before viewing a sample. Paste it back after viewing the sample report.

    These tags are references to other folders in the BI and hence will throw error when we try to view a sample report locally.

    Under BI publisher tab click on any of the formats to view a sample report.


    Sample report in the pdf format.



    Step 6: Save the template and upload it back into the BI publisher.

    Under Custom folder> Procurement> Suppliers > External Supplier Registration Approved FYI Email Report, note down the layout name and delete the existing template. Click on Upload to upload the configured template. Please note to use the existing name for layout name. For External Supplier Registration Approved FYI Email Report template the layout name is ExtSuppRegNotifApprovedFyi.



    Once the upload is complete click on View a list on the top right corner and verify that the Default Layout checkbox is checked.



    Other references:


  • Aishwarya Pawar
    Desupport for Oracle B2B Gateway coming in Update 20A, B2B...5.0
    Topic posted August 28, 2019 by Aishwarya PawarGold Medal: 3,500+ Points, tagged Supplier Communication, Supplier Profile Management, Tip 
    Desupport for Oracle B2B Gateway coming in Update 20A, B2B Supplier Site code retained and moved to a new location!
    Oracle B2B Gateway will be desupported in Update 20A. B2B Supplier Site Code will continue to be available.

    Oracle B2B Gateway will no longer be supported as a B2B Communication method starting Update 20A. We do realize that the B2B Site Code attribute will continue to remain significant for some customers, so we have retained it as a supplier profile attribute, and have moved to it to a new location.

    Starting Update 19C, the B2B Site Code field no longer appears only when the B2B Communication Method is selected as Oracle B2B Gateway - Deprecated and in the B2B Communication Method section. Instead it appears in the section above, which is the Identification section and independent of the B2B Communication Method selected.

    Screenshot below provides additional reference.

    We want to encourage you to update the  B2B Communication Method to a value other than Oracle B2B Gateway - Deprecated and migrate your setup to use Collaboration Messaging Framework for all supplier sites enabled for B2B messaging (if you select Collaboration Messaging Framework as your choice).

    Refer to the Customer Connect post: Desupport Notice for Oracle B2B Gateway in Procure-to-Pay B2B Communications in Update 20A for additional details.

  • Ramesh Radhakrishnan
    "Update Supplier Keyword Search Index and Source to...6
    Topic posted June 9, 2019 by Ramesh RadhakrishnanBlack Diamond: 60,000+ Points, tagged Audit, Business Intelligence, FAQ, How-To, Sourcing Programs, Supplier Creation, Tip 
    "Update Supplier Keyword Search Index and Source to Settle Counts Runs In every 30 Minutes and Errors

    "Update Supplier Keyword Search Index and Source to Settle Counts Runs In every 30 Minutes  and Errors and it is not generating any error log. Any pointers about this program how to troubleshoot this program. Also I see below note relevant to this program

    "Update Supplier Keyword Search Index and Source to Settle Counts Runs In every 30 Minutes (Doc ID 2474423.1)
  • Vineet Gangwar
    Supplier Registration email concerns if SSO is enabled65.0
    Topic posted June 4, 2019 by Vineet GangwarBlue Ribbon: 750+ Points, tagged How-To, Public Sector, Security, Setup, Supplier Communication, Supplier Creation, Supplier Registration, Supplier User Account, Tip 
    Supplier Registration email concerns if SSO is enabled
    When SSO is enabled, organisations are suppose to disable the user account related email and this disables the emails for new account creations for supplier as well.

    If SSO is enabled, user account creation emails are generally disabled and this causes a challenge to implement supplier portal. As suppliers do not get communicated about their account creations automatically as soon as the account is created, followings are the possible solutions (and their challenges) which can be suggested to clients (there can be few more but these are based on my understandings of the application):

    1: Once supplier is registered and account is crated, go to security console, change the user category and reset the password to resend the emails to suppliers.

    Challenges - In most of the public (even in private) sectors, this activity is performed by a dedicated team of supplier admins/managers and they are not supposed to have the access of "Security Console" because of organisations security policies. Hence this solution doesn't sound feasible to clients.


    2- Keep notifications enabled and modify the content of user account email. Detail clear cut instructions for employees and suppliers on how they can access the application but again it comes with the risk that employees (new) might miss the instruction and start using it with the credentials provided in email rather that the SSO ones, which is again big concern for organisations.


    These are the 2 possible solutions which I could have thought of based on my understanding of Cloud application. Please feel free to correct me or suggest any alternate solution if you have come across similar requirement.  


    Vineet Gangwar

  • Piyush Singh
    Creating an Existing Party as a Supplier15.0
    Topic posted April 25, 2019 by Piyush SinghGold Trophy: 10,000+ Points, tagged How-To, Import, Supplier Creation, Tip 
    Creating an Existing Party as a Supplier
    How to establish a supplier relationship for an existing party

    In today’s competitive business environment, organizations must continuously strive to optimize business flow efficiency and operate more strategically.  One opportunity is for smarter modeling of trading relationships with key business partners to gain better visibility and business insight into these relationships.  This is achieved in Oracle Cloud by creating multiple relationships with the same company, for example, a banking provider that is also a customer or, a customer that also serves as a strategic supplier providing goods or services.  These represent different business relationships with a single enterprise, which can be managed from both the supplier and customer master by leveraging a single shared party profile record.

    You can establishing a supplier relationship with an existing party either using Data Quality Management or using Supplier Import process. Following is a brief on the usages of these approaches.

    1. Data Quality Management (DQM): DQM is a preventive mechanism empowering users such that they do not create duplicate parties identified as parties with similar names. DQM does not rely on exact match of the name (depending upon the configuration) to list out the potential duplicates therefore is very effective in preventing duplicate parties in the application.
    2. Establishing supplier relationship using supplier import: When user knows the party that he or she has to create as a supplier, then this approach will be more effective. Following this approach, user saves time required to review all the potential matches as well as avoids any mistake in form of picking up incorrect party for supplier relationship establishment.

    *Details on Data Quality Management will be covered in another post.

    If you know the exact party that you want to create as a supplier, use the supplier import capability to achieve the same. Following are the steps you need to follow when creating supplier from an existing party (customer in the example below).

    1. Find the Registry ID of the customer from the Manage Customers task.


    2. Use this Registry ID and the Organization Name to create a supplier relationship for this customer using the supplier import process. Populate the FBDI template for Supplier Import as shown in the screen shot below.


    Points to consider when using Registry ID in the template:

    1. Provide Registry ID only for the import action ‘Create’.
    2. Organization Name must be entered exactly as the Supplier Name. If not, the record will be rejected.
    3. Complete the supplier import process (generate csv > load file to interface > run supplier import job).
    4. After the import process completes successfully, search for this supplier, and review the registry ID along with the Relationships of the supplier.


    Additional reference:

    -          Create Supplier From Existing Party Using Supplier Import: TOI


  • Aishwarya Pawar
    Defining Supplier Bank Accounts: Factor Accounts v/s Account...15.0
    Topic posted March 29, 2019 by Aishwarya PawarGold Medal: 3,500+ Points, tagged FAQ, Supplier Profile Management, Tip 
    Defining Supplier Bank Accounts: Factor Accounts v/s Account Owners
    When to use Factor Accounts and Account Owners

    Bank Accounts can be defined for suppliers at supplier, address or site level. While creating a bank account, you can use several fields to define the bank account such as the Bank, Branch, mark it as a Factor Account or add Account Owners etc.

    This note explains the significance of making a bank account a Factor Account or adding Account Owners. 2 different use cases drive these two functionalities.

    Factor Account: A bank account can be identified as a Factor Account, if the purpose of the bank account is to receive funds that are owed to the supplier, but are being collected on behalf of the supplier by the bank or a third party. The supplier receives payments from the funds collected, minus a commission. Once a bank account is defined as a Factor Account, it will be available to be added to any supplier 's profile. You can select an existing party to be the Factor. In the example below, Factor Tessier Ashpool is an existing party. 

    Once a bank account is made a Factor Account it cannot be updated to no longer be a Factor Account. Similarly, the Factor associated cannot be changed

    Account Owners: As part of the bank account definition, you can add other suppliers to the bank account of the current supplier as joint bank account owners. This is done if a supplier wants to share a bank account with another supplier on a need by basis and is not the same as a Factor Account. The bank account will be available to be added as a bank account for the other supplier on that supplier 's profile.


    A bank account defined as a Factor Account can be added as a Bank Account for any other supplier using the Select and Add action in the Bank Accounts table on the other supplier 's profile (at supplier, address or site level).

    A bank account that contains a supplier as an Account Owner can be added to only that specific supplier using the same Select and Add action as above.

    To illustrate: assuming the 2 bank accounts defined above are for supplier: Acme Corporation, they will be available to be added to supplier: Minuteman Supplies using the Select and Add action as shown below.

    NOTE: Third Party Payments available to be set up at supplier sites have a different functional purpose from Factor Accounts and Account Owners and are payments that you make to a supplier on behalf of another supplier.

    Refer to the following documentation for more details:

    Payments Security