Information Systems:Markup Classes - Revision history

Norwinu: /* Timing of markup class changes */

2016-07-12T20:33:11Z

Timing of markup class changes

Norwinu: /* Beginning of the month */

2016-07-12T20:31:39Z

Beginning of the month

Norwinu: /* Beginning of the month */

2016-07-12T20:30:36Z

Beginning of the month

Norwinu: /* Timing of markup class changes */

2016-07-12T16:38:42Z

Timing of markup class changes

Norwinu: /* Timing of markup class changes */

2016-07-12T16:38:16Z

Timing of markup class changes

Norwinu: /* Any other day of the month */

2016-07-12T16:37:01Z

Any other day of the month

Norwinu: /* Any other day of the month */

2016-07-12T16:36:38Z

Any other day of the month

Norwinu: /* Any other day of the month */

2016-07-12T16:36:21Z

Any other day of the month

Norwinu: /* Any other day of the month */

2016-07-12T16:31:57Z

Any other day of the month

Norwinu at 16:31, 12 July 2016

2016-07-12T16:31:36Z

@@ Line 37: / Line 37: @@
 '''''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 make a very important change to the customer sales history file (WSCSTSL2P):
+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====
@@ Line 43: / Line 43: @@
 ====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 start date of the change (effective start date). 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:
+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).

@@ Line 40: / Line 40: @@
 ====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 still [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History#Markup_class_changes|needs to be changed]] to use the new value.
+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 [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History#Markup_class_changes|needs to be changed]] to use the new value.
 ====Any other day of the month====

@@ Line 40: / Line 40: @@
 ====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.
+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 still [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History#Markup_class_changes|needs to be changed]] to use the new value.
 ====Any other day of the month====

@@ Line 37: / Line 37: @@
 '''''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, an important change to the customer sales history file (WSCSTSL2P) may need to be made:
+Depending on when a change to a markup class takes effect, you may have to make a very important change to the customer sales history file (WSCSTSL2P):
 ====Beginning of the month====

@@ Line 35: / Line 35: @@
 =Timing of markup class changes=
-'''''Note: This most likely only applies to changes involving the brand/generic markup classes.''''
+'''''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, an important change to the customer sales history file (WSCSTSL2P) may need to be made:

@@ Line 48: / Line 48: @@
 # [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History#Markup_class_changes|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 of doing this - be creative but precise i.e. only "play with" the month in question.
+# 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 [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History|Customer Sales History]] Infonet program should now reflect the correct data for that month.

@@ Line 42: / Line 42: @@
 ====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 start date of the change (effective start date). This will effectively exclude all current monthly sales before that date, leading to inaccurate sales history data. 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:
+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 start date of the change (effective start date). 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 will just be overridden by the nightly build (which deletes and rebuilds all records for the current month only).
+# 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.
-# [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History#Markup_class_changes|Edit the program]] that builds the aforementioned file (WEBPRDP/BLDCSTSL2;SQLRPGLE) to reflect the new markup class.
+# [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History#Markup_class_changes|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.
+# 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.
-# Merge the data (sum up field/column C2BRAND in both tables) and update WSCSTSL2P.
+# Use SQL to merge the data (sum up field/column C2BRAND in both tables) and update WSCSTSL2P. There is a multitude of ways of doing this - be creative but precise i.e. only ''play with'' the month in question.
 # The [[Information_Systems:IN-CUSTSLS_-_Customer_Sales_History|Customer Sales History]] Infonet program should now reflect the correct data for that month.