For example, Elliott users may have multiple product lines, such as ABC and XYZ. Some customers may become master dealers for the ABC product line, while others may become master dealers for the XYZ product line. In such cases, we can assign the customer type as ABC or XYZ and add price codes for customer type ABC or XYZ accordingly.
However, an issue arises when a customer becomes a master dealer for both the ABC and XYZ product lines. Currently, Elliott only allows one customer type per customer. This enhancement introduces a new table, ARPRCTYP, to store the additional customer types.
While you are not required to use the Primary Customer Type for pricing, keep in mind that multiple areas in Elliott rely on the customer type field and do not interact with the additional customer types in the ARPRCTYP table. This includes, for example, Sales Analysis and Commission Calculation. Currently, the purpose of the ARPRCTYP table is solely to determine pricing based on the Elliott Price Code tables.
The primary purpose of this flag 6 is to improve performance. Setting this flag to "Y" enhances pricing calculation performance, as Elliott does not need to check all customer types defined for the customer. Note: If the product category is less than 3 digits, then we expect the Price Types to preserve the trailing spaces. For example, if the product category is "A"
, any Price Type like "A 01"
or "A 02"
(i.e., "A"
+ 2 spaces + additional characters) is considered a match. However, "A01"
or "A02"
is not considered a match.
On the other hand, setting the flag to "N" provides greater flexibility but may result in slower performance due to additional network I/O required to evaluate all customer types define for this customer. At this time, we cannot quantify the exact performance impact. It is up to your discretion whether to set this flag to "Y" or "N".
The CSV import function always operates in replacement mode. Users should maintain a complete master list of all customers for a particular customer type in Excel, and save it as a CSV file before importing.
Always import the full customer list for the customer type. If you import only a partial list, any customers missing from the CSV file will be deleted from the ARPRCTYP table. For this reason, it is always a good idea to do a pre-interface before performing interface to avoid accidentally deleting records with the import.
000001000003000004
For customer 000001, nothing will happen.For customer 000002, DISTR will be deleted since customer 000002 is not in the CSV fileFor customer 000003, DISTR will be added for customer 000003.For customer 000004, nothing will happen.
Therefore, if the matching customer type used for pricing differs from the primary customer type, it will be printed to the side instead. See the sample report below:
Price Code |
Price Type |
Item |
Price |
Item Price |
Prod Cat |
3 |
DISTR |
DATA-BUS |
17.43 |
40.00 |
ACP |
3 |
DISTR |
DATA-CONTRL |
15.95 |
15.95 |
CVD |
3 |
RETL |
DATA-BUS |
15.69 |
40.00 |
ACP |
3 |
RETL |
DATA-CONTRL |
14.26 |
15.95 |
CVD |
3 |
WHSL |
DATA-BUS |
13.07 |
40.00 |
ACP |
3 |
WHSL |
DATA-CONTRL |
11.96 |
15.95 |
CVD |
3 |
ACP01 |
DATA-BUS |
35.00 |
40.00 |
ACP |
3 |
ACP02 |
DATA-BUS |
30.00 |
40.00 |
ACP |
3 |
ACP03 |
DATA-BUS |
25.00 |
40.00 |
ACP |
3 |
CVD01 |
DATA-CONTRL |
15.5 |
15.95 |
CVD |
3 |
CVD02 |
DATA-CONTRL |
15.00 |
15.95 |
CVD |
3 |
CVD03 |
DATA-CONTRL |
14.75 |
15.95 |
CVD |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000500 |
NWENT |
RETL |
1 |
DATA-BUS |
15.69 |
DATA-CONTRL |
14.26 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
RETL |
DISTR |
1 |
DATA-BUS |
15.69 |
DATA-CONTRL |
14.26 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
SPEC |
DISTR |
1 |
DATA-BUS |
17.43 |
WHSL |
2 |
||||
DISTR |
1 |
DATA-CONTRL |
15.95 |
||
WHSL |
2 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
SPEC |
WHSL |
1 |
DATA-BUS |
13.07 |
DISTR |
2 |
||||
WHSL |
1 |
DATA-CONTRL |
11.96 |
||
DISTR |
2 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
RETL |
WHSL |
1 |
DATA-BUS |
15.69 |
DISTR |
2 |
||||
WHSL |
1 |
DATA-CONTRL |
14.26 |
||
DISTR |
2 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
SPEC |
DISTR |
1 |
DATA-BUS |
13.07 |
WHSL |
2 |
||||
DISTR |
1 |
DATA-CONTRL |
11.96 |
||
WHSL |
2 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
RETL |
DISTR |
1 |
DATA-BUS |
13.07 |
WHSL |
2 |
||||
DISTR |
1 |
DATA-CONTRL |
11.96 |
||
WHSL |
2 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000500 |
NWENT |
ACP01 |
1 |
DATA-BUS |
35 |
CVD02 |
2 |
DATA-CONTRL |
15 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
RETL |
ACP01 |
1 |
DATA-BUS |
15.69 |
CVD02 |
2 |
DATA-CONTRL |
14.26 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
SPEC |
ACP01 |
1 |
DATA-BUS |
35.00 |
ACP02 |
2 |
||||
CVD01 |
1 |
DATA-CONTRL |
15.50 |
||
CVD02 |
2 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
SPEC |
ACP01 |
1 |
DATA-BUS |
30.00 |
ACP02 |
2 |
||||
CVD01 |
1 |
DATA-CONTRL |
15.00 |
||
CVD02 |
2 |
Customer |
Customer Type |
Price Types |
Seq No |
Item |
Price |
000555 |
RETL |
ACP02 |
1 |
DATA-BUS |
15.69 |
ACP03 |
2 |
||||
CVD01 |
1 |
DATA-CONTRL |
14.26 |
||
CVD02 |
2 |