Supplier Management

Get Involved. Join the Conversation.

Comments

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

  • Vikram Agarwal

    Internal User (Buying Organization Employee)

  • Piyush Singh

    Hi Vikram,

    Is Y, in the above example, an internal user (buying organization's employee) or a supplier user?

    Thanks,

    Piyush

  • Vikram Agarwal

    Thanks Piyush for the confirmation

  • Piyush Singh

    Hi Vikram,

    This is the only option available for the mentioned requirement. Regarding post upgrade impact, your changes will not be overwritten by seeded values.

    Thanks,

    Piyush

  • Beth Bleijie

    Thank you so much, Aishwarya and Ramesh,

    I'll dig into those and see how I go.

    Beth

  • Ramesh Bomma

    Hi Beth,

    Below are the two documents which will help

    How Does The Fusion Applications Supplier Import Work? (Doc ID 1323531.1)
    How Does The Import Supplier Process Work Using File Based Loader - An Example For Rel6 Onwards (Doc ID 1556688.1)

    Thanks,
    Ramesh

  • Aishwarya Pawar

    Hi Beth,

    You can use Supplier Import to load suppliers. Let me try to pull up a training you can reference. If not, I can certainly put together some steps for your reference.

    Thanks,

    Aishwarya

  • Hong Gao

    Unfortunately, this is not supported.  Cloud Supplier Portal license provides supplier collaboration on core Fusion Procurement to Pay flows. 

    One alternative to consider is probably to use EBS web services to build own supplier facing application via PAAS.

    Regards,

    Hong

  • Ivan Pena

    Moving to supplier management forum.

    Ivan

  • Hong Gao

    Supplier outbound synchronization service provides a snapshot of the supplier being created/updated.  It also includes diversity data.

    More details on this feature can be found in this whitepaper:

    https://mosemp.us.oracle.com/epmos/faces/DocContentDisplay?_afrLoop=284964727495303&id=2339940.1&_afrWindowMode=0&_adf.ctrl-state=8wc7mtu2x_53

    Regards,

    Hong

  • Prasad Deshpande

    Sure it does help some extent as a workaround for our gap. I was looking for any inbuilt application functionality. Thanks.