Supplier Management

Get Involved. Join the Conversation.

Posts

  • 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

      

  • 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

  • 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
  • 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

     

  • Mukund Kudrimoti
    Details on supplier portal setups25.0
    Topic posted October 15, 2019 by Mukund KudrimotiRed Ribbon: 250+ Points, tagged Payables, Supplier Communication, Supplier Profile Management, Supplier Registration 
    Title:
    Details on supplier portal setups
    Summary:
    Details on supplier portal setups
    Content:

    Hi,

    I was looking for a step by step document on setting up Supplier portal and access in Cloud. Appreciate if someone has any information.

    Regards,

    Mukund

    Version:
    19C
  • ALEXANDER JOSEPH
    Which table stores the tax classification code that is...4
    Topic posted October 10, 2019 by ALEXANDER JOSEPHRed Ribbon: 250+ Points, tagged Supplier Creation, Supplier Profile Management 
    Title:
    Which table stores the tax classification code that is entered at the Supplier profile
    Summary:
    Which table stores the tax classification code that is entered at the Supplier profile
    Content:

    Which table stores the tax classification code that we enter at the Supplier Profile level > Transaction tax>Controls and defaults

    Is there a webservice or API that we can call to get this detail

     

  • PRASHANT MENON
    Not able to Select Roles while Creating User Contact in...1
    Topic posted October 9, 2019 by PRASHANT MENONGreen Ribbon: 100+ Points, tagged Supplier Communication, Supplier Creation, Supplier Profile Management, Supplier Registration, Supplier User Account 
    Title:
    Not able to Select Roles while Creating User Contact in Supplier Contact
    Summary:
    Not able to Select Roles while Creating User Contact in Supplier Contact
    Content:

    Not able to Select Roles while Creating User Contact in Supplier Contact

    “If Manage Supplier User Roles shows that there are no roles, that means there are no roles that can be added for supplier contacts. 

    We will need to add roles here so that roles are available for selection when requesting/creating user accounts for supplier contacts.” 

    Which roles can be added in 'Manage Supplier User Roles'  task, so that it is visible while creating User contact

    Image:
  • Harshith Eshwar Shaila
    In need of a query to track number of emails and related...Answered2
    Topic posted October 9, 2019 by Harshith Eshwar ShailaBronze Medal: 1,250+ Points, tagged Security, Supplier Communication, Supplier Profile Management 
    Title:
    In need of a query to track number of emails and related details sent out to suppliers over a period of time?
    Content:

    Hi all,

    We require a query that we can run in BI publisher to show any emails sent out to suppliers over a period of time?  During testing we unintentionally had emails from POs and Agreements sent out to actual suppliers from development instance, we have manually generated a list of affected suppliers (they were less in number), but it would be helpful to have a query for this issue if it occurs again. 

    We have opened an service request (SR 3-21255360671) for this a well.

    Regards,

    Harshith E S

     

    Version:
    19C (11.13.19.07.0)
  • Rushi Joshi
    Show supplier bank account from supplier address/site on...2
    Topic posted October 7, 2019 by Rushi JoshiSilver Medal: 2,000+ Points, tagged Fusion, How-To, Supplier Profile Management, Supplier User Account 
    Title:
    Show supplier bank account from supplier address/site on supplier portal
    Summary:
    Need to check if it is possible to capture supplier bank account from supplier address or/and supplier site to the supplier profile on supplier portal.
    Content:

    Hello all,

    Currently, I can only see the bank account that is on the supplier header and that is getting captured on the supplier portal (supplier user account).

    Scenario: There are there supplier addresses, sites and contacts(user accounts). Every address is linked with a unique bank account, site and a unique contact(through address). All these three unique bank accounts are also unique with the one on the supplier header(profile).

    Aim: 

    1) To capture bank account on supplier portal from supplier address/site instead of supplier header. Is this achievable? Does it govern by roles/privileges?

    2) If point one is achievable, how can we add security? On the supplier portal, one user account should only be able to view the bank account associated with the address and site assigned to him/her.

    3) If everything above is not possible, can I simply restrict one bank account from supplier header to one contact user account on the supplier portal?

    Thanks,

    Rushi

    Version:
    19C
  • Catherine Hull
    Enabling Supplier Match; Batch Feature35.0
    Topic posted October 6, 2019 by Catherine HullGold Medal: 3,500+ Points, tagged FAQ, How-To, Supplier Creation, Supplier Merge, Supplier Profile Management 
    Title:
    Enabling Supplier Match; Batch Feature
    Summary:
    What is the purpose of the Supplier Match Batch Feature? How to utilize this feature?
    Content:
    What is the purpose of the Supplier Match Batch Feature? How to utilize this feature?

    Under Define Supplier Matching > Manage Enterprise Data Quality Matching Configurations, what is the purpose of Batch: Match Configuration Parameters?

    This question arose, because after following the Oracle setup documentation (all steps of Implementing-Procurement.pdf > Enabling Supplier Match: Explained), I obtained results after defining Real-Time Match Configuration Parameters, BUT I do not know where in the system the Batch Match Configuration Parameters are utilized. Would it be a scheduled process that runs?

     

    The Oracle Implementing Procurement manual does not provide any detail about the purpose of the Batch feature. I have not been able to find additional insight anywhere else.

     

    Thanks, Catherine

    Version:
    Release 13 19B