Supplier Management

Get Involved. Join the Conversation.

Posts

  • Sammy Bagchi
    Hide 'Announcement' on supplier portal login pageAnswered10
    Topic posted September 21, 2018 by Sammy BagchiBlue Ribbon: 750+ Points, tagged Supplier Communication, Supplier Profile Management, Supplier Registration 
    Title:
    Hide 'Announcement' on supplier portal login page
    Summary:
    Can we hide the announcement section that is displayed for the regular login under supplier portal login?
    Content:

    Can we hide the announcement section that is displayed for the regular login under supplier portal login?

    We are going live with supplier portal for our P2P process and noticed that the announcement section which is targeted for internal audience is displayed under the supplier portal login as well.

    Any trick or tips to hide it?

    We are on R13/18B Sep update.

    Sammy

    Image:
  • 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 
    Title:
    How to use REST APIs for supplier payment attributes
    Summary:
    How to retrieve and update payment attributes of suppliers, their addresses or sites using REST
    Content:

    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:

               https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees

    • 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

    Description

    PayeePartyIdentifier

    Integer

    Corresponds to the SupplierPartyId retrieved using Suppliers GET operation.

    Required to retrieve PayeeId corresponding to supplier payment attributes.

    PayeePartySiteIdentifier

    Integer

    Corresponds to the SupplierPartySiteID retrieved using Supplier Address GET operation.

    Required to retrieve PayeeId corresponding to supplier addresses payment attributes.

    SupplierSiteIdentifier

    Integer

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

    Required to retrieve PayeeId corresponding to supplier sites payment attributes.

    PayeeId

    Integer

    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.

    DeliveryChannelCode

    DeliveryChannelName               

    String

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

    SupplierNumber

    String

    Application-generated party number in Procurement.

    SupplierSiteCode

    String

    Code of a supplier site.

    SettlementPriority

    String

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

    PaymentTextMessageOne

    PaymentTextMessageTwo

    PaymentTextMessageThree

    String

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

    ServiceLevelCode

    ServiceLevelName

    String

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

    PayEachDocumentAloneOption

    String

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

    BankChargeBearerCode

    BankChargeBearerName

    String

    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.

    PaymentReasonCode

    PaymentReasonName

    String

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

    PaymentReasonComments 

    String

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

    DeliveryMethod

     

     

    String

    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

    String

    Email address at which an external payee receives remittance advice.

    Fax

    String

    Fax number at which an external payee receives remittance advice.

    DefaultPaymentMethodCode

    DefaultPaymentMethodName

    String

    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

               https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees?finder=ExternalPayeeSearch;Intent=Supplier,PayeePartyIdentifier=<SupplierPartyId>

    • GET PayeeId for Supplier Address:

               Run the supplier address GET operation to get SupplierAddressId

               https://<hostname>:<port>/fscmRestApi/resources/latest/suppliers/<SupplierId>/child/addresses

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

              https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees?

              finder=ExternalPayeeSearch;Intent=Supplier,PayeePartyIdentifier=<SupplierPartyId>&q=PayeePartySiteIdentifier=<SupplierAddressId>

    • GET PayeeId for supplier site:

               Run the supplier site GET operation to get SupplierSiteId

               https://<hostname>:<port>/fscmRestApi/resources/latest/suppliers/<SupplierId>/child/sites

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

               https://<hostname>:<port>/fscmRestApi/resources/latest/paymentsExternalPayees?

               finder=ExternalPayeeSearch;Intent=Supplier,PayeePartyIdentifier=<SupplierPartyId>,SupplierSiteIdentifier=<SupplierSiteId>

    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",
    "Email":"alex@hotmail.com"
    }

    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.

    References:

    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

      

  • Aishwarya Pawar
    Adding site assignments to a supplier site.5.0
    Topic last edited November 20, 2019 by Aishwarya PawarGold Medal: 3,500+ Points, tagged How-To, Supplier Profile Management 
    Title:
    Adding site assignments to a supplier site.
    Summary:
    How do I successfully add site assignments to a supplier site
    Content:

    A supplier site is always created in the context of a Procurement BU. This association allows Procurement BU to set terms, controls, and policies which govern how procure to pay transactions are executed between its Client BUs and the supplier.

    A supplier site can have one or more site assignments and site assignments indicate which Client BUs can transact with the site in question.

    Creating site assignments is a crucial step for suppliers to be able to transact with the buying organization. For example, a supplier cannot be specified on a purchase order if a site and site assignment in the correct Procurement BU and Client BU respectively are not defined on the supplier profile.

    It is mandatory to specify a Client BU on a site assignment as shown in the screenshot below:

    If for some reason your Client BU is not available to be selected, you will need to verify the following:

    1. A service provider - client relationship exists between the Procurement BU of the supplier site and the Client BU you want to use on the supplier site assignment.

    NOTE: To view the relationship, navigate to the Manage Business Unit task in Setup and Maintenance and look for the Client BU.  Access the Manage Service Providers action and confirm that the Procurement BU is listed under Procurement Service Providers as shown in the screenshots below.

        

    2. The Client BU has either a Requisitioning or Payables Invoicing business function.

    NOTE: To view the business functions assigned to the Client BU, access the Assign Business Functions action as shown in the screenshot below and verify that the Client BU has one of the functions listed above.

       

    3. The Procurement BU and Client BU are active.

  • Sandeep Kumar
    How to enable Audit to supplier portal1
    Topic posted November 15, 2019 by Sandeep KumarSilver Medal: 2,000+ Points, tagged Supplier Profile Management, Supplier Registration, Supplier User Account 
    Title:
    How to enable Audit to supplier portal
    Content:

    How to enable Audit to the supplier portal attributes

  • William Knowles
    Supplier Portal User Guide/Manual3
    Topic posted April 17, 2017 by William KnowlesSilver Medal: 2,000+ Points, tagged Setup, Supplier Profile Management, Supplier User Account 
    Title:
    Supplier Portal User Guide/Manual
    Summary:
    Supplier Portal User Guide/Manual
    Content:

    We are planning to roll-out our Supplier Portal to our top preferred/approved suppliers.  Has anyone created a Supplier Portal guide/manual that can be sent to suppliers for learning or training purposes?  Since the layout in Fusion is globally uniform I was hoping that I would not have to start from scratch on developing the guide?  Would any customers be willing to share their guide or portions of their guide?

  • Jayaganesh Alagirisamy
    Masking Supplier Tax Payer ID45.0
    Topic posted June 19, 2019 by Jayaganesh AlagirisamyBlue Ribbon: 750+ Points, tagged Fusion, Supplier Creation, Supplier Merge, Supplier Profile Management, Supplier Registration, Supplier User Account 
    Title:
    Masking Supplier Tax Payer ID
    Summary:
    We would want to mask the Supplier Taxpayer ID across Organization types
    Content:

    Hi,

     

    The business would want to have their suppliers tax payer id masked, but it is only possible to mask if the Organization type is "Individual". Please refer the below metalink. Masking Supplier Tax Identifiers PII Data (Doc ID 2330050.1)

    My question is if the supplier renders a different kind of service irrespective of the tax organization type, then is it possible to mask the Taxpayer ID across suppliers? Please let me know if you have any workaround for the same. 

    Thanks,

    Jay.

  • Amy Chan
    Unique key of supplier2
    Topic posted December 11, 2018 by Amy ChanSilver Medal: 2,000+ Points, tagged Financials, Supplier Creation, Supplier Merge, Supplier Profile Management, Supplier Registration, Supplier User Account 
    Title:
    Unique key of supplier
    Summary:
    Unique key of supplier
    Content:

    I have a question for unique key of supplier. I want to create "HP" as a supplier name and the country is "US" for US legal entity. Later when we rollout to "UK"  and we need to create another "HP" supplier with country "UK" and system prompt up an error message.

    Would anyone share with me for such case?

     

  • Dave Dengate
    Displaying Unmasked Bank Account12
    Topic posted April 3, 2017 by Dave DengateBlue Ribbon: 750+ Points, tagged Public Sector, Supplier Creation, Supplier Profile Management 
    Title:
    Displaying Unmasked Bank Account
    Summary:
    When Maintaining Bank Accounts we need to see the full Bank Account number
    Content:

    There are occasions when our Account Payable's manager need to see the full bank account number to ensure we are creating duplicates or allocating the wrong Bank Account to a Supplier.

    Is there a way within Fusion where the full Bank Account Number (I.e. 12345678, not xxxx5678) can be displayed.?

  • Sivaraj Shanmugham
    Scheduling Supplier Audit report3
    Topic posted October 21, 2019 by Sivaraj ShanmughamRed Ribbon: 250+ Points, tagged Audit, Supplier Creation, Supplier Profile Management 
    Title:
    Scheduling Supplier Audit report
    Summary:
    Looking for an automated way to send the Supplier Audit report to Finance
    Content:

    Currently users are running the audit report from Tools menu. Team is asking if there is a way to schedule this report to run on a weekly basis and deliver the report output to one or more users. 

    Thanks, Siva

     

  • Sem van Donk
    Taxpayer ID on address level2
    Topic posted October 21, 2019 by Sem van Donk, tagged Supplier Creation, Supplier Profile Management, Supplier Registration, White Paper 
    Title:
    Taxpayer ID on address level
    Summary:
    Taxpayer ID on address level
    Content:

    Hi Community,

    We are having some issues with storing the Taxpayer ID which is required for certain reports of tax authorities on the profile level, and would like to know if there are users with experience where different addresses in the supplier model have their own Taxpayer ID. 

    The situation:

    We are buying products at different companies throughout Europe. Some organizations that we do business with have multiple locations, for example 1 per country, while operating in 3 different countries. For these locations, the supplier makes use of different VAT registration and do business with the particular business unit (from our side) in the corresponding countries (Supplier X, address NL --> business unit NL). From our perspective, as a client of this specific supplier operating in three countries, we see the different supplier locations as 1 main supplier, with whom, as a global company we do business with, meaning price agreements on a global scale and specific services services, eventhough this supplier has different registrations and tax details for the various locations. Long story short, to be able to help the procurement department, we would like to be able to see in one glimpse, what we, eventhough from different business units, buy as a company from this supplier. Which is why we want to store the different locations/addresses underneath one supplier profile. 

    In the below overview you see a table of the sketched situation;

    PartyID

    Profile

    Taxpayer ID

    Address

    VAT-number (connected to address)

    Site

    X

    Company X

     

    Address NL

    NL122225B01

    Procurement BU from NL

     

     

     

     

     

    Procurement BU from BE

         

    Address PL

    DE1225552

    Procurement BU from PL

       

    55445554

    Address ESP

    ES111125556

    Procurement BU from ES

     

    Now the problem arises, for the supplier data we need to provide in the system, we have the ability to store tax related matters on different levels. However, not all tax details can be stored everywhere, we have VAT registrations on Address level (per location) and Taxpayer ID is forced to profile level (1 for all locations) for the SII VAT filling report in Spain. 

     

    The case:

    For the, in the table above, mentioned supplier, the Spanish tax authorities wants us to provide a different tax ID next to the existing VAT registration in the VAT filing, or near real time VAT reporting (SII). In Oracle we can enable this reporting and filing by filling the Taxpayer ID (only possible on profile level for SII reporting as per an oracle whitepaper https://cloud.oracle.com/opc/saas/datasheets/online-vat-spain-topical-essay.pdf). If this would be a single requirement from only Spain, storing this Taxpayer ID on profile level would not be an issue. However, if in the given example, Polish tax authorities are going to raise the same tax requirement, we are not able to store this on the profile level of the same supplier (addresses in Poland and also Spain) as there will already be a Tax Payer ID stored.

    We can ofcourse create seperate suppliers for the countries in which we forsee any kind of potential Taxpayer ID requirement arising, however, due to reporting of spend at grouped suppliers, we do not want to do so. Seperating a supplier based on country to be able to store the Taxpayer ID on profile level will make the business reporting for total spend a lot more cumbersome and time consuming.

    Is there anyone with a simular issue, and has a solution on how to handle this, ideally we would like to store the Taxpayer ID on address level, where VAT registrations are stored as well, at the moment, for the SII reporting, this is not possible as mentioned here; https://cloud.oracle.com/opc/saas/datasheets/online-vat-spain-topical-essay.pdf. (attached) And as confirmed by Oracle support in a Service Request.

    Thanks,

    Regards,

    Sem

    Version:
    19C