on 09-13-2011 4:55 PM
We run credit check at delivery. If the customer fails the credit check then the overall status of credit checks of the delivery CMGST gets set to B, the Finance team see the failed delivery in VKM4 and release it or not. Assuming it gets released then CMGST gets set to D.
We also run the credit check again at goods issue if the time elapsed between delivery release and GI exceeds a certain number of days.
If the credit check runs again and fails, you get a message saying you can't do a GI because of credit block, but the delivery status is not reset to B.
Its then impossible for Finance to determine deliveries they need to release again so the GI works.
Is there an OSS note that fixes this?
Hi Mike
PGI is the last stage where credit check happens.
However, the delivery doc is not blocked when the credit check fails at PGI level. The system throws an error message showing the exceeded limit. The delivery status is not updated as there is no block.
IF there is enough credit available, then the PGI can happen as usual without having to goto finance team to release it.
This is standard SAP behaviour.
Hope this clears your point.
Please check Note 441009 - Credit: Check at the time of goods issue
Regards
Madhu
Edited by: Madhu Naidu on Sep 14, 2011 12:45 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
Not sure my post will help but check the reports RVKRED06 and RVKRED09 in SE38/SA38. Check whether you are able to list out the deliveries which are blocked for credit reasons at the goods issue level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
seems to be a critical scenario. am sure that you had maintained the number of days under the Released documents are still unchecked in your OVA8 setting.
according CCA/ RISK Category/ 02 (for Deliveries), you wud have maintained the 5 days & had released the delivery document say on 1st september, meaning the document will not go for a block again if the % deviation is within tolerance for 5 days, if this exceeds & if there is any change delivery will go for a block & hence you cannot do further processing.
Same is the case with CCA/Risk Category/ 03 ( for PGI). now you say that the delivery status is not getting updated, but PGI is not possible, i think this might be because of improper table updation. please have it checked with SAP or check the OSS message that might be available.
a curious question, why do u want to block the shipment to the customer at the delivery level & also at the PGI level, this will be double load for FI team to release the customer for the same value for the same customer & it is not logic as well, you can have the check at both areas only when u have the practice of increasing the delivery qty at the delivery level & do the PGI for the increased delivery qty.
rgds
ilango
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check in FD32 weather that customer is exceeding the credit limit or not,there might been some payments received during that time period.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
in OVA8, did you set the status block flag for the PGI doc credit group or just the reaction?
Regards
Raghu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
for the PG document, the credit group is 03--pls set it up for the CCA+ 03+ risk category in OVA8 and try.
However, now you make me think if this setting doesn't exist..how are you triggering the credit check again at PGI? based on some user exit and calling a standard FM? If so, are you passing the block flag?
Regards
Raghu.
User | Count |
---|---|
98 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.