Supplier Management

Get Involved. Join the Conversation.

Posts

  • Prasad Deshpande
    TIN validation during supplier registration8
    Topic posted February 20, 2018 by Prasad DeshpandeBlue Ribbon: 750+ Points, tagged Customization, FAQ, How-To, Sourcing Programs 
    Title:
    TIN validation during supplier registration
    Summary:
    TIN validation during supplier registration
    Content:

    Wanted to know two things if they can be doable during supplier registration

    1. TIN validation. If this can be done via 3rd party integration then more details on that integration should be helpful.

    and

    2. Ability to standardize the Tax ID/SSN prior to match (e.g. appropriate format xx-xxxxxxx or ***-xx-xxxx). I guess this is doable but not sure.

  • Aishwarya Pawar
    Supplier Profile Attachments Listing Report64.8
    Topic last edited April 30, 2019 by Aishwarya PawarGold Medal: 3,500+ Points, tagged Business Intelligence, How-To 
    Title:
    Supplier Profile Attachments Listing Report
    Summary:
    Custom BIP Report displaying supplier profile attachments for recently created suppliers
    Content:

    This BIP report will show supplier profile attachments added to the supplier header for all suppliers created in the last 30 days.

    The attached Deployment Instructions.pdf contains steps for importing the data source and report to your instance.  Also attached is the Supplier Profile Attachments.catalog file that will allow you to import these to your instance.

    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

      

  • 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.
    
  • Shivani Roy
    How to Get Supplier Audit History Using REST API45.0
    Topic last edited November 22, 2019 by Shivani RoyBronze Medal: 1,250+ Points, tagged Audit, How-To, Web Services 
    Title:
    How to Get Supplier Audit History Using REST API
    Summary:
    Oracle Applications Cloud provide public REST APIs you can use to support integration requirements for the common features like roles, users, user requests etc. One of them is the audit report resourc
    Content:

    How to get audit report using the REST API

    REST Service Name: Get Audit Report

    • Rest method: POST

              The user will have to use the REST POST method to post a request to retrieve audit reports response.

    • Path:
      The request path to be added in REST should be in the below format.

               https://<hostname>:<port>/fscmRestApi/fndAuditRESTService/audittrail/getaudithistory

    • Content Type: application/json

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

    • Request Parameters:
      Following table explains each of the query parameters which can be used in the request payload. These correspond to the actual search criteria available on the audit reports page.

    Query Parameter

    Data Type

    Description

    attributeDetailMode

    boolean

    Indicates whether the old and new attribute values are returned. If true, the old and new values are retrieved. If false, the response contains only attribute names, and not old and new values. The default value is false.

    On the audit reports UI this corresponds to ‘Show Attribute Details’ check box.

    businessObjectType

    String

    The fully qualified view object name. In this case it will be "oracle.apps.prc.poz.suppliers.protectedModel.

    core.view.AuditSupplierVO"

    eventType

    String

    A comma-separated list of events you want to search. Valid values are : Object Data Insert, Object Data Update, Object Data Delete, All

    fromDate

    String

    The date from which the audit history is to be retrieved. The format of the date can be yyyy-MM-dd or yyyy-MM-dd HH:mm:ss. You can retrieve audit history for up to one month.

    toDate

    String

    The date up to which the audit report data is to be retrieved. The format of the date can be yyyy-MM-dd or yyyy-MM-dd HH:mm:ss.

    includeChildObjects

    boolean

    Indicates whether to include the child objects in the audit report. The default value is false. The child objects for Supplier will be address, contact, sites, business classifications, product and services, bank accounts.

    includeImpersonator

    boolean

    Indicates whether to include the impersonator name in the audit report. The default value is false.

    product

    String

    A predefined product value provided in the request. It will be ‘Procurement’ in this context.

    user

    String

    The display name of the user who has created or updated the supplier.

    includeAttributes

    boolean

    Indicates whether the audit report includes attribute details that were changed in the specified time period. The default value is true. On the audit reports UI this corresponds to ‘Show Attribute Details’ check box.

    includeExtendedObjectIdentiferColumns

     

    boolean

    Indicates whether to include the context information for the business objects. The default value is false. This corresponds to ‘Show additional object identifier columns’ checkbox in the Audit Reports UI

    timeZone

    String

    The timezone to be used for the specified period of the audit report.

    pageSize

    number

    The number of records displayed in a page, in the audit report.

    pageNumber

    number

    The page number in the audit report you want to view.

    Sample request payload to retrieve all the supplier records which was inserted, updated or deleted in the given date range.

                {

                   "fromDate":"2018-10-15 00:00:00",

                   "toDate":"2018-10-15 23:59:59",

                   "product":"procurement",

                  "businessObjectType":"oracle.apps.prc.poz.suppliers.protectedModel.core.view.AuditSupplierVO",  

                  "includeChildObjects":"true",

                   "includeAttributes":"true",

                   "eventType":"All",

                   "attributeDetailMode":"true",

                   "timeZone":"UTC"

                   }

    • Response Parameters:
      Following table explains each of the response properties returned as part of the REST response. These correspond to the actual attributes in the audit search results table.

    Response property

    Data Type

    Title

    Description

    actionName

    string

    Action Name

    The request method name for which the response is retrieved. Since we are retrieving audit history it will be ‘getAuditHistory’

    auditData

    array

    Audit Data

    The audit data retrieved for the specified criteria. This section contains results similar to the ones fetched in audit reports.

    status

    string

    Status

    The status of the audit report. The valid values are 200-success, 400-Bad request, 401-Authentication error, 403-Authorization error, and 500-Internal server error.

    pageSize

    string

    Page Size

    The number of records displayed per page in the audit report.

    pageNumber

    string

    Page Number

    The number of records displayed per page in the audit report.

    Sample response payload with audit report results for Supplier: Automotive Supplier.

    Updates were made to attributes: Federal reportable and TaxVerificationDate.
    {
        "auditData": [
            {
                "date": "2018-10-15 12:29:00",
                "descriptionInternal": "Supplier:949",
                "userInternalName": "CVBUYER01",
                "attributeDetails": [
                    {
                        "oldValueId": "N",
                        "newValueId": "Y",
                        "attribute": "Federal reportable",
                        "attributeInternalName": "FederalReportableFlag",
                        "newValue": "Yes",
                        "oldValue": "No"
                    },
                    {
                        "attribute": "Verification Date",
                        "attributeInternalName": "TaxVerificationDate",
                        "newValue": "2018-08-02"
                    },
                ],
                "businessObject": "Supplier",
                "qualifiedBusinessObject":
                "oracle.apps.prc.poz.suppliers.protectedModel.core.view.AuditSupplierVO",
                "userName": "Clare Furey",
                "eventType": "Object Data Update",
                "description": "Supplier:Automotive Supplier"
            }
        ],
        "pageSize": "1",
        "status": "SUCCESS",
        "actionName": "getAuditHistory"
    }

     

    You can refer the following document for further details: Common Features in Oracle Applications Cloud R13

  • Hong Gao
    How to include username in new supplier user account email55.0
    Topic posted May 24, 2019 by Hong GaoGold Medal: 3,500+ Points, tagged How-To, Supplier User Account 
    Title:
    How to include username in new supplier user account email
    Summary:
    Steps to include username in the new supplier user account email
    Content:

    When a new supplier user account is created in the application, an email is sent to the new user to reset password and log into the system.  This email, however, does not contain the username information by default.  Buying organization usually determines the username format internally, for example, firstname.lastname@<company domain>.com; this format information is not clear to its supplier users.  You can follow the steps below to include the username information in the email so that supplier user will have the complete account information to access the Supplier Portal application.

    1. Log into the application as an administrator user and go to Security Console > User Categories
    2. Click on the Default user category link, then click on Notifications from the side panel on the left.
    3. Click on Edit button on the upper right corner of the page.
    4. Make sure Enable notifications checkbox is checked for Notification Preferences.
    5. Locate a template name "ORA New Account Template".  This is the template used for the new user account email by default.  Click on the template link to review the details in the dialog.
    6. Uncheck the checkbox for Enabled.  We will disable this default template.
    7. Click Save and Close to dismiss the dialog.
    8. Click on Add Template button.
    9. Provide template name.  Check the Enabled checkbox. Select "New user created" from Event drop down.
    10. For Message Subject and Message, you can reference the details for the same in the "ORA New Account Template", copy the content here and make adjustment as needed.
    11. To include the username information, add the token: ${userLoginId} in the part of the Message that you see fit.
    12. Click Save and Close.
    13. Click Save, and then click Done.

    Emails sent to new supplier users will contain the username information to help user successfully log into Supplier Portal. (See the screenshot for an example email below.)

    image2019-5-21_13-47-34.png?version=1&modificationDate=1558471654000&api=v2

    Please note that since all new users in the application is assigned to Default user category by default, the notification template change above will impact all new users in the application.

    You can reference more details on defining notification template in the following link:

    https://docs.oracle.com/en/cloud/saas/applications-common/19b/faser/managing-implementation-users.html#FASER2253505

  • Kelly Cooper
    SCM – Supplier Onboarding: Deep Dive and Best Practices, 2...6
    Topic posted November 14, 2019 by Sona SrinivasanSilver Medal: 2,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.

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

  • David Wright
    Child fields in request parameter for Get All Suppliers REST...Answered3
    Topic posted November 8, 2019 by David Wright, tagged Business Intelligence, Fusion, How-To 
    Title:
    Child fields in request parameter for Get All Suppliers REST API
    Summary:
    What's the notation for child fields for expanded items in this API
    Content:

    The documentation says "If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. "

    So, if my parameters say 'fields' : 'Alias,AlternateName,Supplier,SupplierId,SupplierNumber,sites.PaymentTerms' then shouldn't sites.PaymentTerms be valid for Suppliers?  However, when I try to use any variation of this (with . or ; or :) it fails with 'URL request parameter fields with value Alias,AlternateName,Supplier,SupplierId,SupplierNumber,sites.PaymentTerms is not valid.'

    Is my notation incorrect, or can I not access child items in such a manner for Supplier?

  • 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