Credit check with MRP block

[Former Member]

When customer exceed the credit limit,system pop up the warning & it blocks the document

But when i go to MD04,blocked order is appeared,In MD02 - Sytem does MRP for that blocked order also

How to stop the planning for blocked order due to credit limit

regards

[Former Member]

Hi,

In this case, I have to tell you that the system is working as designed.

Here you can prevent the creation of the confirmed quantity for the delivery, but transfer of requirement takes place anyway - this is because it is assumed that in most cases a delivery will be made at some point in the future.

If an order is blocked because of the credit check or has a delivery block which has TVLS-SPEBE set then

• the item doesn't get any confirmed quantity

• therefore no subsequent delivery is possible

• BUT the requirements are passed through and you can

see them in md04 and use them for planning purposes (as you already do at the

moment).

This functionality was designed in that way because preventing the confirmation of the order item also prevents the creation of the delivery. This enables you to block an order from SD further actions

until all questions concerning credit limit etc. are cleared, and on the other still to use these requirements for planning purposes.

Summary:

Requirements are always passed for the requested quantity. In customizing for credit management, one can only maintain whether or not you get a confirmed quantity in the sales order (via requirement 101 in

transaction ovb8). It is not possible to prevent the system from passing on requirements to production because any block of this kind will be removed after clearance of credit limit and therefore production should be informed because there might be lead times which have to be be active if the customer is to get the goods on time. If you do not wish to produce at all, you should use the reason for rejection. The purpose of the credit block is not to treat the order as if it were rejected - at least from the point of view of ATP and requirements.

Hope this helps, kind rgs.

[Former Member]

Hi Andrea Drab,

Thanks for your reply.I understand the concept.My customer wants the same

Is there any other ways of preventing the blocked orders from planning or production in std ....or

Is there any std requirement in VOFM or changing 101..................

Regards,

Murali.R

[Former Member]

Any updates please......................

[Former Member]

Hi MUrali,

Maintain reason for rejection in sales order header level for sales.

Regards

Sreenivas

[Former Member]

Dear Murali,

sorry for the late reply.

please see note 744305:

...

The credit lock resets the confirmation in the schedule lines of the

sales order. The request schedule line passes a requirement in spite of

that. This requirement is also processed from the MRP run and the

procurement is triggered. The credit lock does not stop this process.

This system response is intended because in most cases the credit locked

sales order is released and is then to be returned on schedule. Thus the

procurement must be triggered in spite of the credit lock.

With the help of indicator 'Fixed Date & qty' you can pass the confirmed

quantity as requirement. Since the confirmed quantity is 0 due to the

credit lock, also the requirement with quantity 0 is sent. No

procurement is triggered. Refer to Note 547277, point 12.

Hope this solves your problem. Rgs, Andi

[Former Member]

hello my friend ,

Activate the flag( CONF BLOCK) under the path for the delivery block

SPRO>Sales and Distribution>Basic Functions>Availability Check and Transfer of Requirements>Transfer of Requirements> Block Quantity Confirmation In Delivery Blocks>Deliveries: Blocking Reasons/Criteria

by acivating the flag the MRP run will not consider the orders with those delivery blocks

[Former Member]

Hi baskar,

Thanks for your reply.In deliveries:blocking reasons criteria-------there is no field like MRP run

Please confirm

[Former Member]

Hi,

Activate CONF BLOCK field on the mentioned path earlier. As you know Transfer of reqirment under basic functions is about doing settings for MRP run in SD

[Former Member]

Yes Mr.baskar...........CONF has already activated.that CONF block is for not to confirm the order qty.

System transfering to MR regardless of CONF block