ER: - Ability To Maintain PO Approval Limits Based On Supplier (Doc ID 3053895.1)

Last updated on OCTOBER 17, 2024

Applies to:

Goal

Enhancement Request:

Question: Describe how the current product functionality is insufficient.
Answer: Business requirement is to apply PO approval limits not (just) based by user role but also based on Supplier, i.e. each Supplier should have PO approval limits.

Question: Provide a detailed description of the Enhancement Request.
Answer: Business requirement is to apply PO approval limits not (just) based by user role but also based on Supplier, i.e. each Supplier should have PO approval limits.

Attempted PoC on SUPS_CFA_EXT - added CFA field 'Supplier PO Limit' to the Supplier entity. Attempted to build a custom validation query but seems MFCS does not support grouping functions, i.e. couldn't SUM all order lines in the ORDLOC table to get the total PO amount.

Supplier approval limit should be also based on a time dimension. Setting the PO approvals per Supplier/week level to allow tracking how much PO's have been ordered from a Supplier during the week.

Requirement is to provide ability to configure PO approvals by Supplier, either by enhancing the validation capabilities (e.g. to be able to SUM the order amount) or by creating a new framework for Supplier-level approval amounts.

Question: Describe how this Enhancement will benefit your business.
Answer: Business requirement is to apply PO approval limits not (just) based by user role but also based on Supplier, i.e. each Supplier should have PO approval limits. This is standard business process.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.