View source | Discuss this page | Page history | Printable version   

Projects/Business Partner Set/Functional Specification

Contents

Overview

Purpose

The purpose of this development is to make it easier to define a discount which only applies to a specific sets of business partners, for example all male customers between 19-22 years old.

Scope

References

Design Considerations

Assumptions

Dependencies

No specific functional dependencies.

Constraints

There can be constraints on how many business partners can be imported in one time (100000s of records per import is probably the limit).

We can probably load maximum in the 100000s business partner sets records in the webpos database. See open questions below.

The import file format is assumed to be a csv/text file with one column. We will make it flexible so that it can be defined to which business partner column it will map. Still the single column should match the value in the corresponding business partner record/column to find a business partner.

Functional Requirements

User stories

Sales Admin: define business partner set and import

Sales Admin: link to discounts

Note: the business partner set concept is only used for the logic controlled by the field in discounts and promotions: 'Included Business Partner'.


Bp included discount.png

WebPOS User

Import Logic


Status & Functional requirements based on business processes

Requirement Importance Status Comments
A window, tab and tables to administer the business partner set and its contents. Must have Done (pending feedback) Will be a standard Openbravo window with one main tab (Business Partner Set) and one child tab (business partners by set).
A new table and tab (in discounts and promotions window) to support linking a business partner set to a discount. Must have Done (pending feedback) Standard openbravo tab on a table.
Show a new button and dialog in the business partner set window/tab. Must have Done (pending feedback) The dialog shows the fields to select a file and the import parameters. After clicking OK the process starts and the errors are reported.
The import logic on the server and report back to the client. Must have Done (without using connector framework, pending feedback) The dialog shows the fields to select a file and the import parameters. After clicking OK the process starts and the errors are reported.
Defining the WebPOS client offline tables and logic to load the data (incrementally) Must have Not started Load the data in webpos for offline usage.
Modify WebPOS discounting engine to use the business partner set to check that a BP is eligible for a discount. Must have Not started Use the business partner set in the client side.
Add automated test case to cover webpos discount logic. Must have Not started Use the business partner set in the client side.

User Interface Mockups

See here the BP Set window with the header tab and the business partner child tab, notice the import button next to the attachment button in the toolbar:


Bp set window.png


The import button is enabled when the child tab is activated and one parent record is selected. Clicking the import button shows this popup:


Bp set window popup.png


The link between discounts and business partner set:


Discount bp set window.png

Open Discussion Items

Closed Discussion Items

Retrieved from "http://wiki.openbravo.com/wiki/Projects/Business_Partner_Set/Functional_Specification"

This page has been accessed 1,084 times. This page was last modified on 16 February 2019, at 18:18. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.