Supplier Management

Get Involved. Join the Conversation.

Topic

    Vikram Agarwal
    Differentiate between Supplier registered Internally vs...Answered
    Topic posted May 17, 2018 by Vikram AgarwalBlue Ribbon: 750+ Points, tagged Approvals/Notifications 
    303 Views, 3 Comments
    Title:
    Differentiate between Supplier registered Internally vs Externally on Supplier Spend Authorization Approvals
    Summary:
    Differentiate between Supplier registered Internally vs Externally on Supplier Spend Authorization Approvals
    Content:

    Hello,

    By default we are creating suppliers as Prospective supplier. Now at time of promotion to Spend Authorized we would like to follow different approval mechanism for supplier registered internally as compared to external supplier registration.

    I was able to identify "Spend Authorization Request Source" attribute (with values as Manual Request/Registration External/Registration Internal/Registration - Sourcing Invitation/Self Service Procurement/Sourcing Award) which I think we can leverage to meet the requirement. 

    Appreciate any thoughts/idea on how we can achieve the same or if we can use the above attribute.

    Thanks in Advance

    Vikram

    Best Comment

    Piyush Singh

    Hi Vikram,

    Attribute 'Spend Authorization Request Source' helps identify the source of spend authorization request (not the supplier creation source). The source of spend authorization can be manual (which you are using at the moment by manually promoting an existing prospective supplier), as well as various registration flows which when approved trigger a spend authorization request (if registration request is for spend business relationship).

    For your use case this attribute cannot be used, neither do we have other attribute that directly can be used for this use case. 

    I can suggest following at the moment:

    1. If feasible, use Supplier Type attribute to capture the source of prospective supplier creation and based on that you can author approval rules. This does not sound very convincing but you can achieve the results.

    2. We have plans to add DFFs as approval attributes for spend authorization approval task. Once delivered, you can use a DFF to capture the value of creation source and then author approval rules based on that DFF. As mentioned, this is not available right now, but is on our road-map.

    Thanks,

    Piyush

    Comment

     

    • Piyush Singh

      Hi Vikram,

      Attribute 'Spend Authorization Request Source' helps identify the source of spend authorization request (not the supplier creation source). The source of spend authorization can be manual (which you are using at the moment by manually promoting an existing prospective supplier), as well as various registration flows which when approved trigger a spend authorization request (if registration request is for spend business relationship).

      For your use case this attribute cannot be used, neither do we have other attribute that directly can be used for this use case. 

      I can suggest following at the moment:

      1. If feasible, use Supplier Type attribute to capture the source of prospective supplier creation and based on that you can author approval rules. This does not sound very convincing but you can achieve the results.

      2. We have plans to add DFFs as approval attributes for spend authorization approval task. Once delivered, you can use a DFF to capture the value of creation source and then author approval rules based on that DFF. As mentioned, this is not available right now, but is on our road-map.

      Thanks,

      Piyush

      • Vikram Agarwal

        Hi Piyush,

        Thanks for the workaround. Based on above limitation we may now go with following flow

        1) Internal Supplier Registration - By default it will be spend authorized. We can use "Spend Authorization Request Source" with value as "Registration Internal"

        2) External Supplier Registration - By default it will be prospective Supplier. We will use "Spend Authorization Request Source" with value as "Manual"

        Thanks,

        Vikram

    • Piyush Singh

      Sounds great.

      Thanks,

      Piyush