Credit Management for different Sales Order Types

[Former Member]

Hello All,

The problem is related to Credit Management for Sales Order which is explained below with an example -

We have separate Sales Order Types for New Launches (ZNLS) & Normal Depot Sales (ZDPS) but both the Order Types are assigned with same pricing procedure and respective orders will be raised against the same party code.Now automatic credit check is only active for order type ZDPS where the credit limit had been set to Rs.1000. Now Rs,.500 had already been raised using order type ZDPS, then another sales order of Rs. 500 is raised using order type ZNLS.But when a sale order of Rs. 550 is raised using order type ZDPS the sales order is getting blocked, because the system had taken into consideration & added up the Rs. 500 value of ZNLS with previous value of Rs. 500 against order type ZDPS as a result of automatic credit check though it is not active for order type ZNLS.Point to be noted that Credit exposure is also not active for Order Type ZNLS.

How is this taken into consideration & what are the steps need to be configured so that the credit limit check will not get automatically activated for order type ZNLS and only remain active for order type ZDPS despite they are assigned to same pricing procedure and used for invoicing same party code?

Please suggest.

Thanks & Regards

Priyanka Mitra

[Former Member]

This message was moderated.

[Former Member]

Hello All,

Thanks for your suggestions.

Regards

Priyanka Mitra

[Former Member]

Hi All,

Even my client is having similar requirement. I have checked the settigns which you have mentioned above, but unfortunately when it comes to receviables gerenated at the time of accouting document creation. it gets updated in the credit exposure( in Open receviables field in FD32)

How to counter this?

[SmileZhang]

Hi Mitra,

The issue occurs because of the fact that credit check and the

update of the credit values are separate processes which are also

controlled separately by the respective customizing:

1. credit check is controlled by transactions OVAK and OVA8.

According to the attachment, you have already refered to note 18613 to

check the customizing settings.

2. update of the credit values is controlled by VOV7 or OVA7: "credit

acttive" flag. The 'Credit active' setting only affects the credit

update of the SD credit values (open orders, open delivery and open

billing documents). This flag has no control on the credit check. So

if for an order type, there is no credit check in OVAK and OVA8 but

the "credit active" flag is set for the item category, the order will

update the credit values even if no credit check is performed for the

order.

If the flag "credit active" is not set, the system will not update the

open credit values. On the other hand, the system ALWAYS updates the FI

credit value 'Open receivable' when the billing document is transferred

to Accounting. So, although you deactivated the "Credit active" flag in

in OVA7 or VOV7, such an item will increase the 'Open receivables' and

thus the credit limit used when the corresponding billing document is

posted to Accounting.

-

---

If you would like the value from sales order type ZNLS is excluded from credit update, you could consider set the "Credit Active" field as blank in VOV7 for the item category used for ZNLS.

Best regards,

Smile

[Former Member]

Hi Smile,

First of all thanks a lot for your suggestions.With reference to the second point I would like to point out that as {Accounts Receivables - Special Liabilities} + Sales Order Value = Credit Exposure for the respective Order Types.Now I want to know is there any configuration possible by which the Accounts Receivables will not get considered or updated with the saving of any bill against that particular order type?

If yes how to do this ? Please suggest.

Thanks & Regards

Priyanka Mitra

[Former Member]

Hi,

I think the problem is occuring because you are using same pricing procedure. Inside a pricing procedure settings for the netvalue field in the "Sub total" colum we populate A which carries over credit price and updates the credit exposure.

Use exactly identicle pricing procedure for new launch document except this setting "A" against the net value field. See if it works. I think it should work.

Regards,

Shantanu Kunte

[Former Member]

Hello,

Thanks for the suggestions but we have already tried this earlier with no desired result.

Could you please suggest a source code through which the credit exposure is getting updated so that I can consult with the ABAP Consultants to develop any routine or user exit through which we will be able to attain our requirement ?

Looking forward to some valuable suggestions.

Thanks & Regards

Priyanka Mitra

[Former Member]

Hi

Below mentioned user exits are provided by SAP that can be used to design credit checks which are different than the credit checks provided in the standard system.

1) LVKMPTZZ

2) LVKMPFZ1: USER_CREDIT_CHECK1

3) LVKMPFZ2: USER_CREDIT_CHECK2

4) LVKMPFZ3: USER_CREDIT_CHECK3

Following logic could be used in the user exits -

The user exit triggers when the sales order is saved and puts a credit block for a particular sales order type.

Assuming that you want to put a credit limit for a particular sales order type.

Custom table could store the predefined credit limit for a particular sales order type.

When the user exit is triggered (at order save), it would compare the total value of the sales order against the predefined credit limit in the Custom table for that sales order type.

If the value exceeds the credit limit, it would put a credit block on the sales order just like the credit block that is put under normal circumstances when the customer credit limit is exceeded.

You can remove the credit block using VKM3.

Regards

[bcrao]

Hi,

You can write routinue for not to consider for order type ZNLS and include the same in in automatic credit check control - in field- "No credit check"

Thanks

Chidambaram