3942006 Newbie

What do you mean by "zeroed out all his commissions and saved"? Do you mean you authorized them fully or something else? What does the existing commission look like in view mode?

Could you be more specific? What are the results and what do you expect the results to be instead? Do you have a manager (team) ASA quota established for the manager on the plan? What are the amounts in the buckets on the schedule? Thanks!

it seems like the voting search app is giving errors.. This problem is known and will be resolved by the end of the week.

Sounds like you have picked the value for "Categorization applies to" which does not match the class-specific quotas you established. Changing the value to "Both Attainment AND Payout" should make the schedule match the categorized quotas you've got and you should get calculations. Here's the description of the two from…

There is currently no partner commission analog to employee managerial commissions. There is an existing enhancement request which you can vote for though: #120330

Thanks for bringing this to our attention. A fix for the issue (153367) is undergoing testing for release in the near future.

The quota attainment of one classification (here New Sales) cannot determine the payout rate of another classification. You can either have each classified quota attainment determine the payout rate of that classification or have an unclassified quota (ie all sales) determine the payout rate of various classifications. If…

Quantity is only considered by the commission calculations if the commission schedule is based on quantity, so Quantity will show 0 on these reports unless you are using a quantity-based schedule. I don't think there is an existing enhancement requesting this functionality so you should contact support to request it if you…

Before attempting to answer, what are you trying to import that the commission system could not be used to calculate? If it is at all possible to avoid importing I would recommend it.

Are these transactions that have been authorized on transactions that receive commission from different categorizations of the same schedule? I think that might be the reason why some invoices appear this way and when some do not. I have filed issue # 135885. Please contact support if you would like to file a case to track…

Could you further explain what you mean by "adding the invoice transaction total"? Thanks!

Is your commission schedule on Quota / Per Period / Semi-Annually? If not, this might suit your needs.

There is already an enchancement request for this functionality. Enhancement 94017. Contact support if you would like to add your company to the enhacement request.

I believe your approach of using custom code to disable the class field on the line is the correct approach. I haven't worked out the exact strategy but I will post again once I have.

There is an existing enhancement request along these lines. Contact support to attach yourself to this enhancement request if you would like. #56601 - Ability to base commissions off of price levels of items As far as "workarounds" go this sounds feasable but you may have difficulty if the price levels change price for…

ASA commission sources from the Sales Order / Return Auth. level so if you create a ASA schedule it can be eligible on either Bookings (SO) or Collections (SO that is billed and paid). If your sales process always goes through a SO using ASA + custom code is a good way to customize your commissions. This only works though…

The Estimated Commission reports show commission calculations based on their source document. For "Sales" commissions this is the invoice, and the "[Estimated] commission amount" is the amount that will be eligible if the whole Invoice is collected. They are shown as dated by their source document. To get a sense of the…

Work on that enhancement (92491) is in progress and currently slated for the Spring 2008 Release.

The reconcile page drives off the statement date field, maybe try adding a day (+) then subtracting it again (-). You might also want to click the history button and inspect the overview of reconcilaition for this account - make sure it's as you expect. If this persists please contact support and file a case so that this…

Thank you for your post! Sounds like a definate quirk to me. It has been entered as issue 114127.

Kathy, thank you for your post. This is being addressed in issue # 107311 and the fix should be released within a week. In the meantime you can either use your other role which you mentioned worked or try sorting the bank reconciliation page by a different column, this may help the page finish loading.

I posted in your other thread... this too is being addressed in issue #106914.

This is being addressed in issue #106914. Please contact customer support if you would like to be notified when a fix is going to be released.

For transaction column fields it may be easier to do this using client-side SuiteScript than using a formula. A validate-line or item/quantity field on-change function that sets this custom field based on the values in the transaction line might be better suited. Issues #1 & #2 are resolved right away and #3 could be…

I don't think there is a way to customize this currently but it would make a nice little enhancement -- contact support to have it filed.

When HTML forms "POST" the properties or style of fields are not submitted, only their values. One way you might be able to satisfy your desire would be to create another checkbox which is hidden and contains the True if your field is disabled and False if it is enabled. Your script could maintain the value of the hidden…

here's a simple script that sets the ASA = to the amount for each line. Hopefully this will be helpful! function validateLine(type) { if (type == 'item') { var amt = parseFloat(nlapiGetCurrentLineItemValue('item', 'amount')); nlapiSetCurrentLineItemValue('item', 'altsalesamt', nlapiFormatCurrency(amt)); } return true; }

Actually after thinking further this may be related to defect 129917.

There were rounding difference issues between the authorize commission page and the individual commission page which may be causing this issue (defect 133777 resolved in 2008 rel 1). In the meantime, if you file a defect with support or ask to be attached to the defect I mentioned, we can try to specifically investigate if…

This defect, which is specific to accounts with the Online Billpay feature, is being handled as defect #135676.