Information Systems:Markup Classes
Overview
Each item is attached to a Markup Class, which gives the markup percentage by price list.
11/20/15 08:57:51 uniPHARM --Volume test MKRIQ120/LISTCTL
UX - List of Markup Class Percentages VOLUME 1.00
Display Order Field Test Value
DATED By Effect Date Dsc, Price
AND
Limit to: AND
Markup Class Whrs Price List
HHC 13/15
MA=Main Info PU=Purge AU=Audit Trail
CP=Copy
Name WAREHOUSE EFFECT STR EFFECT END PRICE LIST PERCENTAGE
HHC 13/15 *ANY JAN 01 00 DEC 31 50 NON-SH-AB 15.000
HHC 13/15 *ANY JAN 01 00 DEC 31 50 NON-SH-BC 15.000
HHC 13/15 *ANY JAN 01 00 DEC 31 50 SHARE-AB 13.000
HHC 13/15 *ANY JAN 01 00 DEC 31 50 SHARE-BC 13.000
HHC 13/15 *ANY JAN 01 00 DEC 31 50 SHARE-PSC 13.000
HHC 13/15 *ANY JAN 01 00 DEC 31 50 SHARE-PSC1 13.000
HHC 13/15 *ANY JAN 01 00 DEC 31 50 SHARE-YT 13.000
HHC 13/15 *ANY JAN 01 00 DEC 31 50 STAFF 13.000
* END *
F21=Srcn Reset
F3=Exit F5=Refresh F6=Add F12=Previous F24=Srcn Save
We have the item account group, and shareholder and customer percentages as part of the code (instead of just in the description) to make it easier for us to understand. For example, 'HHC 13/15' and 'RX 8/9.193'.
This means that when a percentage changes, we have to move items to a new markup class - we can't just change the percentages.
We can use InfoNet to move an item to a new markup class by expiring one and adding another, or we can use the green screen function if we have to do a lot of changes.
TR - transfer for an individual item will expire the 'from' class, and add the 'to' class. For an entire markup class it will do this for all items; or all items for a particular main supplier.
Timing of markup class changes
Note: This most likely only applies to changes involving the brand/generic markup classes.
Depending on when a change to a markup class takes effect, you may have to "clean up" the customer sales history file (WSCSTSL2P):
Beginning of the month
If the markup class is set to take effect on the 1st of the month, no changes need to be made to the file. However, the program that builds the stats file on a nightly basis still needs to be changed to use the new value.
Any other day of the month
If the markup class is set to take effect on any other day of the month, the program BLDCSTSL2 that runs every night will begin to calculate sales history from the change date (effective start date of the markup class). This has the consequence of excluding all current monthly sales before that date, leading to inaccurate sales history data (pertaining to the sale of brand and generic drugs). Accounting and executive-level management has indicated that this stats file is important in determining amounts when issuing customer rebates, so the file needs to be accurate. The fix comprises the following steps:
- Wait until the next month (month of the markup class effective start date + 1). This is because any changes you make to the file now will just be overridden by the nightly build (which deletes and rebuilds all records for the current month only).
- Make a backup of the current file (WSCSTSL2P). This represents data up to the date the markup class was changed.
- Edit the program that builds the aforementioned file to reflect the new markup class. This is WEBPRDP/BLDCSTSL2 (SQLRPGLE).
- Run the program to rebuild the stats file. The table WSCSTSL2P will now contain sales totals for the time since the markup class was changed.
- Use SQL to merge the data (sum up field/column C2BRAND in both tables) and update WSCSTSL2P. There is a multitude of ways to doing this - be creative but precise i.e. only "play with" the month in question.
- The Customer Sales History Infonet program should now reflect the correct data for that month.