Skip to main content
Answer

CustomerOrderHandling.CustomerOrder_ManualCreditCheck blockReason

  • October 17, 2025
  • 1 reply
  • 64 views

Forum|alt.badge.img+5

Hi,

 

I tried to call CustomerOrderHandling.CustomerOrder_ManualCreditCheck to see whether the order is blocked by credit reason. But I noticed one thing.

  1. Order in site A, it is not blocked, then BlockReason is “FALSE”

     

  2. Order in site B, it is not blocked, then BlockReason is null.

     

I would like to know both “FALSE” and null means the order is not blocked? Are there any other values will be that? Or how to decide the order is not blocked.

Best answer by Rcoubrou

Look at the customer set up on site B.  Review the credit control group settings for the 2 customers in your example above.   Review credit limit set up on both, are they different?Are the limits blank or 0.00?  There are 3 possibilities for credit check.

  • FALSE: This explicitly indicates that the order is not blocked due to credit reasons.
  • NULL (or empty): This usually also means the order is not blocked, but it may reflect that no credit check was triggered or no block reason was assigned. This can happen due to differences in site configuration, credit control rules, or workflow triggers.

1 reply

Forum|alt.badge.img+11
  • Hero (Customer)
  • Answer
  • October 17, 2025

Look at the customer set up on site B.  Review the credit control group settings for the 2 customers in your example above.   Review credit limit set up on both, are they different?Are the limits blank or 0.00?  There are 3 possibilities for credit check.

  • FALSE: This explicitly indicates that the order is not blocked due to credit reasons.
  • NULL (or empty): This usually also means the order is not blocked, but it may reflect that no credit check was triggered or no block reason was assigned. This can happen due to differences in site configuration, credit control rules, or workflow triggers.