[NAV2018CU5] Blocked for Invoice = Blocked for Everything

(0) Share

Report

Posted on by Sleepy7

Yesterday, I was explaining a customer how their credit control department can manage customers in NAV.

I showed them the credit limit warning, and of course the possibility to block a customer (for Invoice, Ship or for All).

While doing so, I ran into the following situation (giving customers a random name to keep things clear):

Customer Adrian is blocked for invoice, but customer Brandon is willing to pay for stock that is actually being bought by Adrian.

Then, I try to create a new Sales Order on customer Adrian, with "Bill-to Customer No." Adrian, but this is not possible.

The OnValidate-trigger of "Sell-to Customer No." contains the following code:

(OnValidate-trigger for "Bill-to Customer No." looks similar).

The function CheckBlockedCustOnDocs does the following:

CustBlockedErrorMessage does nothing more than throw the error:

One could say this is by design.

In my opinion, it's perfectly logical in my example to block Brandon for shipments - this whole company might be a buying group with an office the size of a large car.

It would also be perfectly possible to block Adrian for invoicing; this might be a company that always works with a buying group (in which situation making Adrian a Shipment Address is often not sufficient).

Right now, it's not even possible to make an order when either the bill-to or sell-to customer is Blocked for Ship, Invoice or All. To keep things in line with the credit limit functionality, I think it would be more fitting to show a warning when entering an order, or make this a setting in Sales & Receivables Setup.

My customer has already asked me to "fix" this, and I don't like it; there is no easy way around this (without actually modifying code in Table 36). The only decent way I can actually think of is to make a separate "Customer Status" field and catch all related triggers (OnValidates of Bill-to and Sell-to, OnPost for shipments and invoices).

What do you think? Is this a bug?

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Hannes Holst 5,767 on at

Like (0)

Report

Hi,

Have a look for the Credit Warnings instead.

navisionary.com/.../credit-warnings-field-in-the-sales-receivables-setup-table-in-dynamics-nav

When "Blocked" is manually selected, the Orders are blocked. It's more or less the "last option" for a Credit Controller to stop any orders. Please note, when "Blocked = Ship" is selected, it is possible to enter a new Sales Order.

Was this reply helpful? Yes No
Sleepy7 15 on at

Like (0)

Report

[quote user="Hannes Holst"]Please note, when "Blocked = Ship" is selected, it is possible to enter a new Sales Order.[/quote]

This was exactly my point: Unless I'm missing something, it is not >>>

Steps to reproduce:

- run a docker image of NAV2018;

- open customer 10000 in the client;

- Block the client for Shipments;

- Click the new sales order button and tab to the Customer Name field.

Was this reply helpful? Yes No
Hannes Holst 5,767 on at

Like (1)

Report

There is a modification in my current DB which allows it.

Oooops :-)

Let me correct: In NAV-standard, when "Blocked = Ship" is selected, it is possible to enter a Sales Invoice.

Was this reply helpful? Yes No
Hannes Holst 5,767 on at

Like (1)

Report

Here is my change in case you are interested:

Was this reply helpful? Yes No
Sleepy7 15 on at

Like (0)

Report

[quote user="Hannes Holst"]

There is a modification in my current DB which allows it.

Oooops :-)

[/quote] This is why I decided to test on a fresh Docker-image of the version my client uses, just to be sure I didn't "fix" something else :-)

[quote user="Hannes Holst"]Here is my change in case you are interested[/quote] Thanks a lot! The thing is, the client has requested me to work as "clean" as possible - their current NAV 5 implementation installed some fear concerning customizations ;-)

We're planning to switch to extensions real soon (to make an easy upgrade to 365BC in the near future possible), so modifications in standard objects are penalized...

Was this reply helpful? Yes No
Sleepy7 15 on at

Like (0)

Report

Forgot my last line: Actually, the fact that you made this change supports my point :-)

Was this reply helpful? Yes No
Hannes Holst 5,767 on at

Like (0)

Report

Have a look for credit warnings instead:

http://navisionary.com/2011/12/credit-warnings-field-in-the-sales-receivables-setup-table-in-dynamics-nav/

The "Blocked"-option is something like the "last option" for a credit controller to prevent any Sales Orders (or Invoices). To block the creation of a Sales Order makes sense, because a Sales Order results in a Shipment normally.

Because for my current client, approvals are used, the Credit Controller is able to verify orders for such Customers at a later point. Therefor the Blocked-check at this place was not necessary.

Was this reply helpful? Yes No
Sleepy7 15 on at

Like (0)

Report

I understand it works this way now, and "Blocked for Ship" might be more or less useable (if a Credit Controller wants to stop shipment to a customer that crossed some lines), but cannot think of any real world situations where "Blocked for Invoice" would apply.

But I'll write an extension that hides the original field and sets this up a bit more flexible then.

Was this reply helpful? Yes No
Hannes Holst 5,767 on at

Like (0)

Report

[quote user="Sleepy7"]

but cannot think of any real world situations where "Blocked for Invoice" would apply.

[/quote]

Microsoft decided to implement "Blocked = Invoice" with the following background:

In other situations, the customer may have raised objections about an invoice, and the company has decided not to generate new invoices for the customer until the issue has been resolved.

blogs.msdn.microsoft.com/.../nav-design-pattern-of-the-week-blocked-entity

Was this reply helpful? Yes No