[
https://issues.apache.org/jira/browse/OFBIZ-7714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15688935#comment-15688935
]
Swapnil Shah commented on OFBIZ-7714:
-------------------------------------
I am not sure if the requirements are interpreted in the true sense in which it
was described. Here is the real time business case if that can help to put
things in perspective:
"A buyer is the person who is responsible for negotiating with suppliers on
various terms related to products like pricing, discounts, delivery schedule,
credit backs, lot sizing etc. While negotiating with suppliers, there are
various data points need to be referred e.g. Terms/Quotes offered/negotiated
from other or same suppliers in past, current inventory status, selling prices,
future contracts, current contracts expiry etc. As essentially buyer is
authorized person to initiate or place the formal agreement into system which
later can be Approved by higher authorities before making them to come into
effect. Role of 'Accounting' users in this process is limited to just referring
such agreements in order to reconcile invoices and payments to any given
supplier". (Please note that Buyer has all the valid permission and authority
to CRUD the "Purchase Agreements" here without necessarily having all other
permissions available to a typical Accounting users as specified in description
of ticket earlier).
In order to support above business processes, Catalog app looked more apt place
to be in over other applications as buyers generally have prior permission to
access and refer all relevant details without necessarily jumping around across
modules with all the necessarily permissions. I am not sure about the original
intent of having 'Agreements' tab available under Catalog app but whatever may
be the reason, 'Agreement' view could have been leveraged here to enable this
requirement.
Currently the requirement over this ticket is just for supporting pricing
agreements but later can be extended for other eligible types based on logged
in user's roles.
> Introduce a quick way for adding Purchase Price agreements with Suppliers for
> any specific product from Catalog
> ---------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-7714
> URL: https://issues.apache.org/jira/browse/OFBIZ-7714
> Project: OFBiz
> Issue Type: New Feature
> Components: product
> Affects Versions: 14.12.01, 15.12.01
> Reporter: Swapnil Shah
> Assignee: Swapnil Shah
> Attachments: PPA.png
>
>
> Currently new pricing agreements creation takes user to Accounting app where
> it is quite an long and arduous process. And many a times a buyer or
> procurement users doesn't have direct accounting permission in case quick
> pricing agreement needs to be placed with Supplier for specific product(s).
> We can provide a quick option from Catalog >> Product >> Agreement screen
> over "Purchase" section that could unfold as follows:
> # Have a 'Create Price Agreement' link/button on the 'Purchases' Panel and
> hitting this link could ask user to enter following very basic parameters:
> #- Party Id From (Default it to facility's owner party id)
> #- Party Id To (show list of suppliers like we show at the time of Purchase
> Order entry screen)
> #- From Date (default it to show as now() timestamp)
> #- Through Date
> #- Description
> #- Price
> #- Currency
> #- Supplier Product Id
> # Upon successful submission of above details system should create Agreement
> and AgreementItem & SupplierProduct between Supplier and organization by
> passing following default values:
> #- Role Type Id From = 'Internal Organization'
> #- Role Type Id To = ''Supplier"
> #- Agreement Type Id = 'Purchase'
> #- Agreement Item Type Id = 'Pricing'
> #- Product Id= '<ProductId on screen>'
> Please refer to attached screenshot for reference placeholder
> !PPA.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
