MagicBuzz | Pfiou !
Je viens de terminer les évolutions du site de GEMSE 
Et la doc (in barbarian english  )
Code :
- General Electric Medical Systems Europe Accessories Web Site
- Table of contents:
- I. Prices calculation 3
- A) Description 3
- B) When ordering 3
- C) When navigating in catalog 4
- II. Product visibility 6
- III. ?Our promotions? category 7
- I. Prices calculation
- This section does not describe ?promotional prices? calculation. It will be added in future document update, when process will be finalized.
- All prices found in database are converted ?on the fly? to EURO currency, to be able to compare them together. Round rule is: We add 0.5 to all amounts, and we truncate to unit. For currency with cents, we multiply per 100, then we round the amount, and then we divide it by 100. This is the standard round rule for currency.
- A) Description
- In GE structure, there are five prices types.
- 1) Customer prices ? Contracted prices, digressive and localized by customer
- 2) Scale prices ? Decrease, localized by ?scale of price code?
- 3) Column prices ? Decrease, non-localized
- 4) Standard prices ? Non-decrease, localized by establishment
- 5) Corporate prices ? Non-decrease, non-localized
- All of these prices are stocked in Web database as below:
- They are separated in three tables.
- GENcts contains customer prices (type 1)
- GENtac contains scale prices and column prices (types 2 and 3)
- GENtas contains standard prices and corporate prices (types 4 and 5)
- B) When ordering
- In order process, all prices are retrieved and calculated by Microsoft Commerce Server 2.0 pipeline. It uses VBS Script ?price.vbs? that contains all functions used for managing prices. Process in these functions is described below:
- When a customer adds a product to his cart, we get price as this:
- - We try to find prices in this order: 1, 2, 3, 4 and 5 corresponding to user?s profile and quantity chosen.
- - When prices are found for any category, we get lower price from applicable prices.
- - When an applicable price is found, we don?t try to find another price type.
- Example:
- Customer A adds 50 units of product P in his cart. He hasn?t negotiated price with GE, but he is subject to scale of price. He lives in country C so he depends from establishment E.
- We look for contract (price type 1) in GENcts. As we don?t find any one, we try to find a price type 2 in GENtac.
- We find 3 different prices for this product and applicable scale of price:
- From 1 unit: 24 ?/SU
- From 30 units: 25 ?/SU
- 60 units and more: 20 ?/SU
- Only the two first prices are applicable. The lower one is 24?/SU from 1 unit. We use this one.
- As we already found a usable price for this product, we don?t try to find other types of price.
- C) When navigating in catalog
- For catalog price managing process, a ASP file ?x_calc_price.asp? is used. It is a copy of ?price.vbs? file (see paragraph ?B) When Ordering? for more details), plus a new function for displaying digressive prices, described below:
- - When customer navigates in catalog, we use the same process that the one used to add a product to the cart with quantity settled to 1.
- - But in ?product details? page, we display all digressive prices by quantity.
- For this, we get all applicable prices from all five types of price, ordered by price type, ascending, and then price value, ascending. So, we get price from each line when quantity is lower than precedent.
- Example:
- For user U and product P, we have these applicable prices:
- Type 5:
- 25 ?
- Type 4:
- 28 ?
- Type 3:
- 27 ? from 5 units
- 26 ? from 30 units
- Type 2:
- 20 ? from 8 units
- 18 ? from 25 units
- Type 1:
- 16 ? from 50 units
- 14 ? from 60 units
- Query returns values:
- TYPE QUANTITY PRICE
- 1 60 14
- 1 50 16
- 2 25 18
- 2 8 20
- 3 30 26
- 3 5 27
- 4 1 28
- 5 1 25
- When parsing results, we get only prices where quantity is lower than previous one. So we display this (array is filled from bottom):
- From To Price
- 1 4 28 ?
- 5 7 27 ?
- 8 24 20 ?
- 25 49 18 ?
- 50 59 16 ?
- 60 +¥ 14 ?
- II. Product visibility
- GE sells products that some countries are not allowed to buy. Furthermore GE?s catalog contains non-sellable products.
- These permissions are stocked in database in two tables:
- - GENpro: A binary flag ?pro_cntdstb? indicates which countries can access or no to the product.
- - GENbit: Associate countries to a bit position in ?pro_cntdstb? binary flag.
- When a user is logged, we know what country he comes from. So we just have to verify if the bit corresponding to his country is set to ?1? for the product he is looking to.
- When user is not logged, we can?t know what products he can see and what products he can?t see. So we display only products that all countries can see.
- III. ?Our promotions? category
- A new section in ?Accessories corner? had been added to advertise about promotions.
- This is not the real promotion function that is described below: this is a products list with a unique price used to sell at low price for diestock (end series)
- A new table ?TABOURPROMO? has been added in database to manage products that are in promotion.
- In the ?Promotion? page, we just have to get all products that are in this new table.
- But as products that are in promotion are old products, they were unable to be imported from GENERIX as this. So a new ?product life status? has been created in GENERIX, and import now gets also codblocage = ?15?. Update all import SQL Queries (PRMREQ table) to add this filter.
- These products don?t have specific treatments when used outside ?promotion? category. They are simple products, with a unique price and are managed in catalog as other products.
- Note: TABOURPROMO is all managed in the manager. Import doesn?t provide information about promotion. As this is a new administration interface, don?t forget to update permissions for each admin users.
|
ct vraiment très intéressant  |
![[:yaisse2]](https://forum-images.hardware.fr/images/perso/yaisse2.gif "[:yaisse2]")
