Supplier Management

Get Involved. Join the Conversation.

Comments

  • Binayak Mohanty

    Navigation Path:

     

    - Query for Supplier > Address

    2- Create new address 

    3- In additional information tab, i am trying to associate. BU with address

    4- Click on Sites and + sign

    5 - In the Business Unit field, i can not see my new Business Unit

     

  • Binayak Mohanty

    Yes. Supplier Administrator role is added with the specific BU in data access set.

  • Hong Gao

    Could you please share more details such as screenshots so that we can investigate further?

    Thanks,

    Hong

  • Swami Amajala

    Can you check if you have Data Access assigned to Supplier Administrator Role for the BU ?

  • Binayak Mohanty

    Hong,

    Yes. Your suggested action is already complete. I am still getting an issue where i can not see the BU in Supplier site.

  • Ramesh Bomma

    Thank you for Sharing Aishwarya

  • Vikram Agarwal

    Hi Piyush,

    All the PO and Receipt will be created in some other system and from their the data will be interfaced to Oracle Fusion Application. So, we are still in the initial phase to decide whether we would be giving all the supplier access to Supplier Portal.

    Hope this clarifies.

    Regards,

    Vikram 

  • Piyush Singh

    Sounds great.

    Thanks,

    Piyush

  • Piyush Singh

    Can you please explain the reason why supplier users themselves cannot edit the profile from Portal?

    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

  • Vikram Agarwal

    Hi Piyush,

    We have not yet decided from where user is going to update the Supplier Profile. We may opt for Supplier Portal if approvals are not supported for internal changes.

    Regards,

    Vikram

  • 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

  • Piyush Singh

    Hi Vikram,

    Identifying the POC by approval engine and then routing to his or her supervisor automatically is not feasible. The rules need to be authored. Going back to my earlier post, I have an unanswered question: Is this internal user editing supplier profile from Supplier Portal? If so, why?

    Thanks,

    Piyush

  • Vikram Agarwal

    Hi Piyush,

    Thanks for the workaround. We have already though of the solution as suggested by you. Only problem is that we have around 100's of such Y in the organization. Even if we create 100 such condition it will be very difficult to maintain them. 

    What we were thinking was that if approval engine could identify the POC (Y) automatically from DFF and then route it to respective supervisor.

    Regards,

    Vikram

  • Piyush Singh

    So, if Y is an internal user, does he or she get access to Supplier Portal to make changes to the profile? If not, and that the changes are done internally, then please note, the changes will not be routed for approval.

    If Y makes profile change through Portal only, then you can have the information of Y stored in a DFF and use that DFF to write conditions. Your action should be to route using Job Level or Supervisory Hierarchy. 

    Example: Supplier X : DFF is 'POC' and value is Y

    Condition: If POC is equal to Y

    Action: Route using Job Level / Supervisory Hierarchy of a worker (here Y).