Supplier Management

Get Involved. Join the Conversation.

Posts

  • Ashish Gupta
    Incompatibility for supplier ESS jobs3
    Topic posted November 27, 2019 by Ashish GuptaRed Ribbon: 250+ Points, tagged Fusion, Security, Supplier Creation 
    Title:
    Incompatibility for supplier ESS jobs
    Summary:
    Incompatibility for supplier ESS jobs
    Content:

    Hi

    We have a requirement to set incompatibility for Import Supplier and Import Supplier Sites ESS jobs. Please advise if this can be achieved in fusion SaaS.

    Regards

    Ashish

    Version:
    19c
  • Rahul L
    Default Tab settings in Supplier Page35.0
    Topic posted November 25, 2019 by Rahul LGreen Ribbon: 100+ Points, tagged Customization, Fusion, Setup, Supplier Creation 
    Title:
    Default Tab settings in Supplier Page
    Summary:
    Navigate to a particular tab in Supplier Page whenever we open the page
    Content:

    Hi,

    I have created new Tab in Supplier Page and the cursor is getting defaulted to the last opened tab or some times directed to the newly added tab in oracle fusion applications when we open for a particular Supplier.

    I have checked for options in Page Edit mode (Component Properties) but I don't find the Default Tab to be selected in the Properties screen. Any help on this is appreciated. Thank you in advance.

    Attaching the screenshot.

    Version:
    19D (11.13.19.10.0)
    Image:
  • 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 
    Title:
    SCM – Supplier Onboarding: Deep Dive and Best Practices, 21 November 2019, 9 a.m. PT - Submit Questions
    Content:

    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.

  • Mukund Kudrimoti
    Maintain existing supplier numbers2
    Topic posted November 14, 2019 by Mukund KudrimotiRed Ribbon: 250+ Points, tagged Supplier Creation 
    Title:
    Maintain existing supplier numbers
    Summary:
    Maintain existing supplier numbers
    Content:

    Hello,

    We converting suppliers from legacy system in to cloud. Is it possible to maintain the existing supplier numbers while converting and then also use the numbering in cloud for new suppliers created in cloud thereafter.

    Appreciate if anyone has addressed this requirement

    Version:
    19C
  • Anita Chittaki
    Ability to setup a rule where supplier creation /user...15.0
    Topic posted November 12, 2019 by Anita ChittakiGreen Ribbon: 100+ Points, tagged How-To, Setup, Supplier Creation, Supplier User Account 
    Title:
    Ability to setup a rule where supplier creation /user account error notification to be sent only group of user
    Summary:
    Ability to setup a rule where supplier creation/user account error notification to be sent only group of user
    Content:
    we would like to setup a rule where  supplier creation/user creation errors notification to be sent only to supplier Data Management team  orgroup of  users
    Can you let us know whether these error notification rule can be setup/sent only to specific group/users.
    
  • Zemeer Padikkal
    Tax Registration Number4
    Topic posted November 11, 2019 by Zemeer Padikkal, tagged Financials, Payables, Supplier Creation 
    Title:
    Tax Registration Number
    Summary:
    Tax Registration Number usage between Legal Entity and Supplier with Validation
    Content:

    We do need a new option to use the Tax Registration Number used in Legal Entity to Supplier Creation without any duplication inside Suppliers

    We have multiple legal entities
    - As per our business requirement, one legal can be a supplier to other legal entity 
    - when Optin allow duplicate TRN is off, we can't use the same TRN number in Supplier creation because that is used in Legal Entity
    - If we allow duplicate is on - we can create supplier A and Supplier B with same TRN number (We don't want duplicate TRN inside Suppliers)
     

     

  • Ashish Gupta
    Need to know the method to create Supplier using REST API4
    Topic posted November 6, 2019 by Ashish GuptaRed Ribbon: 250+ Points, tagged Supplier Creation, Web Services 
    Title:
    Need to know the method to create Supplier using REST API
    Summary:
    Need to know the method to create Supplier using REST API
    Content:

    Hi

     

    We have a requirement to create end to end supplier including supplier header, supplier address. business classification, sites and site assignments via REST API. We are using version 19c and referred "Create Supplier" REST API. When we tried to create end to end supplier, we get error " The action create is not enabled". 

     

    Please advise if there is any method through which we can achieve the same.

     

    Regards

    Ashish

    Version:
    19c
  • David Wright
    REST API for Payment Attributes For SupplierAnswered3
    Topic posted November 4, 2019 by David Wright, tagged Fusion, How-To, Supplier Creation 
    Title:
    REST API for Payment Attributes For Supplier
    Content:

    Is there a method of updating or entering values for Payment Attributes when creating a Supplier via REST API?  Documentation does not have anything for that section at all. (documentation in question).

    Version:
    19d
  • David Wright
    REST Suppliers Status failure3
    Topic posted November 4, 2019 by David Wright, tagged Fusion, How-To, Supplier Creation 
    Title:
    REST Suppliers Status failure
    Summary:
    Trying to list a Status value on a Supplier POST REST action causes failure
    Content:

    Creating a supplier via REST does not allow Status value to be set. If Status is listed in payload, regardless of value, request fails with status code 400

    Example from documentation with added Status line (https://docs.oracle.com/en/cloud/saas/procurement/19d/fapra/op-suppliers-post.html):
    {
    "Supplier" : "Tall Manufacturing",
    "TaxOrganizationType" : "Corporation",
    "SupplierType" : "Services",
    "BusinessRelationship" : "Prospective",
    "DUNSNumber" : "221134568",
    "OneTimeSupplierFlag" : false,
    "TaxpayerCountry" : "United States",
    "TaxpayerId" : "98-03376373",
    "Status" : "ACTIVE" # IF THIS LINE IS PRESENT, REST POST FAILS with error: "Attribute Status in view object SupplierVO cannot be set."
    }

  • 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