on 07-22-2008 8:38 AM
Dear all,
At present, we have credit control in sales order. The rule is : once the sales order's amount over 1 dollar, the order will be blocked for credit check. This order has to release credit block manually in VKM4.
Here has a problem, when a sales order has credit released with the status "D", if i check ATP for one item in this order, the credit status will return to "B", it is not match our requirement.
How can the credit status not change when ATP check happen in the sales order?
Thanks in advance!
Hi,
You can prevent new ATP check after release by using this exit :
MV45AFZF
--> Apply this value : CH_CHECK = CON_CHECK_NO.
Also, you can deactivate new credit check if the status is = "D".
In this case, you must use a new routine in credit custo (OVA8) for your credit control area. You find an example of routine in the field "no control" or with Tcode VOFM/requirements/Credit checks.
Regards,
Lionel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I think this is a standard behavior of SAP.
The new credit check if new ATP is in standard program.
New credit check is launch if credit value is changed (greater than old value) and delivery date.
If you run ATP in sales order, it's possible one item change credit value or delivery date. Then, SAP detects new modification in sales order and runs new credit check.
To prevent this, you can change configuration in your auto credit ckeck (OVA8) while using "Nb of days" in "released documents are still unchecked".
Another solution (the best I think) is to use a new requirement in the field "no credit check" (with Tcode VOFM).
Regards,
Lionel
Hi Lionel,
Thanks for your reply. I agree with your point that when i run ATP ,the delivery date in sales order is changed, this execute the credit check.
Now we are using the view ""Nb of days" in "released documents are still unchecked". in OVA8 with 999 days, but this still cannot solve our problem.
And in VOFM, i don't not sure is below field to control this step:
no credit relvant data are changed
IF XVBAK-NETWR LE YVBAK-NETWR.
no credit checks, if old net value not graeter the new net value,
but status are not reset
MOVE CHARX TO BYPASS-SECURITY.
MOVE CHARX TO BYPASS-STATIC_LIMIT.
MOVE CHARX TO BYPASS-DYNAMIC_LIMIT.
MOVE CHARX TO BYPASS-DOCUMENTVALUE.
MOVE CHARX TO BYPASS-CRITICAL_FIELDS.
MOVE CHARX TO BYPASS-REVIEWDATE.
MOVE CHARX TO BYPASS-OPEN_ITEMS.
MOVE CHARX TO BYPASS-OLDEST_OP.
MOVE CHARX TO BYPASS-DUNNING_LEVEL.
MOVE CHARX TO BYPASS-USER1.
MOVE CHARX TO BYPASS-USER2.
MOVE CHARX TO BYPASS-USER3.
EXIT.
ENDIF.
ENDFORM.
Hi Irene,
You can copy this requirement with new code like :
IF yvbuk-cmgst = 'D'.
MOVE CHARX TO BYPASS-SECURITY.
MOVE CHARX TO BYPASS-STATIC_LIMIT.
MOVE CHARX TO BYPASS-DYNAMIC_LIMIT.
MOVE CHARX TO BYPASS-DOCUMENTVALUE.
MOVE CHARX TO BYPASS-CRITICAL_FIELDS.
MOVE CHARX TO BYPASS-REVIEWDATE.
MOVE CHARX TO BYPASS-OPEN_ITEMS.
MOVE CHARX TO BYPASS-OLDEST_OP.
MOVE CHARX TO BYPASS-DUNNING_LEVEL.
MOVE CHARX TO BYPASS-USER1.
MOVE CHARX TO BYPASS-USER2.
MOVE CHARX TO BYPASS-USER3.
MOVE CHARX TO status_reset-STATIC_LIMIT.
MOVE CHARX TO status_reset-DYNAMIC_LIMIT.
MOVE CHARX TO status_reset-DOCUMENTVALUE.
MOVE CHARX TO status_reset-CRITICAL_FIELDS.
MOVE CHARX TO status_reset-REVIEWDATE.
MOVE CHARX TO status_reset-OPEN_ITEMS.
MOVE CHARX TO status_reset-OLDEST_OP.
MOVE CHARX TO status_reset-DUNNING_LEVEL.
MOVE CHARX TO status_reset-USER1.
MOVE CHARX TO status_reset-USER2.
MOVE CHARX TO status_reset-USER3.
EXIT.
ENDIF.
If you are a problem with yvbuk-cmgst, you can use user exit MV45AFZZ to save the credit status (cmgst) into an other field.
This new field is checked in the new requirement.
This requirement deactivates the credit check if the credit status is released. In this case, no credit check is possible in SO.
Regards,
Lionel
Hi Irene,
You can check the last patch with Tcode SPAM.
And click on "Package level" and see for "SAP_APPL".
But, i read the OSS note in details.
Depending on the patch level, it exists an other OSS note 1049901 (correction patch ...29) which deletes the correction in OSS note 898861 (correction patch ...26).
Read carefully these notes.
Regards,
Lionel
Hi Lionel,
Thanks for you reply, and sorry for my delay. I have put the program(from the note) in my system, and give a break for the program, i found it operate when i release credit but not when i run ATP in sales order. So.... i think it is not match my requirement.
Let me check Note 895630 and Note 502930. Thanks!
Hi,
link is there between credit check and ATP check.u go to IMG>sales and distribution>basic functions>availability check and transfer of requirements>Transfer of requirements-->block quantity confirmation in delivery blocks.click on it.Deliveries blocking criteria option will be there.click on it.credit limit block also is there..i think ur problem is due to this field only..in SAP standards it is activated because we have to block the requirements for the customers who have exceeded their credit limits...u please go through this field..it will be helpful to u..
reward points if helpful...
regards..
Yogi...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear all,
I'm not sure if there controled by a use-exit or a program?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
100 | |
11 | |
10 | |
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.