Trade agreement - use of "asterix" in table-number.

(0) Share

Report

Posted on by Community Member Microsoft Employee

Selling user-definable products where basic product characteristics defines product price and the first 9 digits in the product partnumber. Choices of surface and color and more does not inflict on product price, but does add 6 caracters to the product partnumber (xx-xxx). As manager of trade agreements this means that for each basic prduct I have to enter 96 trade agreement lines in 4 different currencies.

I'd like two parameters in which you 1) Allow use of asterix in table-partnumbers, and 2) define the character to use as an asterix in table-part-numbers.

*This post is locked for comments

All responses (3)

Answers (0)

dolee 11,279 on at

Like (0)

Report

RE: Trade agreement - use of "asterix" in table-number.

Hi Sumborg,

Building on Mariano's suggestion, for each product variant (i.e. ProductId-Size-Surface) external itemId and description can be set. Printed documents can show these external ids/descriptions. Would that be enough?

Then at trade agreement you can set a base price for the Product itself and add additional price for specific combinations when necessary.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Trade agreement - use of "asterix" in table-number.

Unfortunately this is not a viable solution. All products are fully defined with product partnumbers and priced (no correalation). But thank you for looking at my challenge.
Mariano Gracia on at

Like (0)

Report

RE: Trade agreement - use of "asterix" in table-number.

The best way to define product characteristics as surface and color, is to use product dimensions (configuration, color, size...), because doing this way you can define product price at the desired level, by item, wich includes all the different variants related to the product dimensions, or by item and product dimensions. Doing this way, you have 96 different variants and only one item, and this is supported by trade agreement. Using asterix is not supported and you have to do some customizations, but be aware, that it can affect the performance, as using "like" in sql sentences are not the best option for a process that is used frequently, and more when you have a standard alternative