Supplier Management

Get Involved. Join the Conversation.

Comments

  • Jeroen Sprangers

    Okay, thanks for your answer and help.

  • Piyush Singh

    We do not have explicit reasons documented. The rule of thumb is to reject, if during the approval flow, application fails to find approvers to route the request for next approval action.

    Cases like DUNS number duplicate etc. do not lead to the rejection of request upfront. For such cases, supplier creation fails which happens after the registration request is approved.

    Hope this helps.

  • Jeroen Sprangers

    Okay, thanks we will check our approval rules configuration.

     

    Are the limited number of reason for approval failure leading to auto rejection documented somewhere? 

    I can imagine for instance that if the tax payer id or DUNS number is duplicate it errors out. But in the documentation I cannot find what the exact checks are that are being performed and when the result is an error.

  • Piyush Singh

    The mentioned notification is planned for future release (reason you are not getting it now). The notification will communicate the issue in general but will not give exact failure reason.

    Also the reasons for approval failure leading to auto rejection are limited and in general if you have only some requests (not all) getting auto rejected, which is the case for you, the issue has to be with approval rules configuration.

    Hope this helps.

  • Jeroen Sprangers

    Hi,

    Thanks for your answer. Indeed in the Manage Supplier Registration Requests page we are able to filter on rejected requests.

    However if we have located them and click on them to see the details we are not seeing the actual rejection reason.

     

    You described: Going forward, there will be notifications for Supplier Administrators who will receive them when any approval request routing fails. It is Supplier Admins task to evaluate the failure and fix if any issue is identified.

    Is this already in place or is this future use? Currently the Supplier Administrator are not receiving this.

     

    So where can we check what the actual rejection error is? Is there a place where we can see this?

     

  • Ramesh Bomma

    Hi Jeroen,

    Glad that issue is resolved now

    Thanks,
    Ramesh

  • Jeroen Sprangers

    Hi,

    We also logged a SR. It is resolved now. We have set the implementation status to implemented.

    This solved the issue.

  • Jeroen Sprangers

    Hi,

     

    Can you let us know how and where we can see which roles have the Privilege - Maintain Supplier Contact User Account assigned?

  • Piyush Singh

    This issue was tracked internally and development team assisted with a solution.

  • Jeroen Sprangers

    Hi Ramesh,

     

    Thanks for your answer but it does not help us further unfortunately.

    Our user has the following roles:

    • ALL USERS
    • Category Manager
    • Employee
    • Prospective Partner Administrator
    • Sourcing Project Collaborator
    • Supplier Administrator
    • Supplier Bidder
    • Supplier Manager
    • Supplier Self Service Administrator

    But we still do not see the "Create account for this contact" in the Edit Supplier Contact page.

     

     

  • Ramesh Bomma

    Hi Jeroen,

    Checked the security Reference manual

    Privileges granted to duties of the abstract role Supplier Administrator

    Duty Role - Supplier User Account Management Duty
    Description - Manages supplier contacts and their user accounts.
    Privilege - Maintain Supplier Contact User Account

    Hope this helps

    Thanks,
    Ramesh

  • Jeroen Sprangers

    The user has the abstract role Supplier Manager. We have not changed this role.

    I believe by default this role should have this privilege assigned.

     

    Is that correct? If not how can we assign it?

  • Jasper Oskam

    Yes I understand. Thank you for your information. If I may ask one more question: can you autoapprove a notification if a certain assignee has not replied in 48rs? If i need to create another post for that, please let me know. Thank you

  • Piyush Singh

    The region is also secured by Maintain Supplier Contact User Account privilege.Can you confirm that the user accessing the contact has this privilege?

  • Piyush Singh

    Agree, FSM task offers a subset of features supported using BPM but, supports many default setup based upon our analysis. This also offers a much simpler and user friendly solution to meet most of your approval needs.

    The configuration that you do through FSM setup is copied to the BPM only. If there are changes that you need to do to like, escalation policies etc. you can do it in the BPM. But suggest you to utilize the FSM task to configure approval rules and then configure the extra policies using BPM.

    Hope this clarifies.